Update index.html

Pull request description
Update to reflect new update date for Aquifer_RechargeDischargeAreas.

Not sure if more action is required on my part, but I just updated the last updated date on the web page for Aquifers.

if that is all you wanted to change then this looks great. 👍 thanks!


Remove Amazon Genomics CLI from docs

Describe the bug
Amazon Genomics CLI has been shuttered and links in the docs to it are dead. I believe this is a documentation only ticket (no code specific to AGC is in the CLI).

To Reproduce

Visit https://docs.dockstore.org/en/stable/advanced-topics/wes/wes-cwl-agc-tutorial.html?highlight=amazon genomics cli
Click links to https://aws.github.io/amazon-genomics-cli and see they 404

Expected behavior
No dead links, remove the demo that uses AGC, which is no longer supported
Additional context
Docs Revision b652684a.
[Domain] - https://dockstore.org
Webservice

1.15.3

UI

2.12.3

Deploy

1.15.0

┆Issue is synchronized with this Jira Story
┆Fix Versions: Dockstore 1.16
┆Issue Number: DOCK-2543
┆Sprint: Backlog
┆Issue Type: Story

The wacky part is that our WesLauncher is largely(?) tested with AGC. That said, it should (?) be usable with other WES implementations.


refactor: Refactor ChainStreamPoller

Fixes #1053
This PR turned out a bit larger than I wanted it to be, but I don't think it makes much sense to split it into several ones.
Here's what changed:

TransportErrorKind::recoverable marked as deprecated, because there already is a more advanced is_retry_err method. The deprecation message suggests using it, or RetryBackoffLayer for HTTP.
Retries were removed from PollerBuilder and ChainStreamPoller. The logic there was pretty basic and it wouldn't solve most problems that can realistically occur. IMHO, recovering belongs to the transport domain; otherwise, there will be one recovery implementation per client user, and a good solution is already present in the project - RetryBackoffLayer. I guess something like this is needed for WebSocket as well.
ChainPollerStream was split into two parts. One handles initialization (works like a tiny builder), and one actually stores the stream state. It allowed us to get rid of NO_BLOCK_NUMBER used as a placeholder.
Dedicated error type was added to simplify implementation.
Finally, batches are now requested via JSON RPC batch request instead of sequential single requests.

@mattsse could you please take a look?

ah sorry, thanks for the ping, will check in a bit

GM @mattsse
Sorry for pinging again; do you think anything else should be done in the scope of this PR?

@mattsse this PR got a bit stale :)
If this functionality is not something alloy will benefit from, I can close the PR (though I've promised to ship some currently lacking tests that depend on this functionality), but I would prefer not to leave it hanging.

@DaniPopes @gakonst Sorry for pinging, but I'm unsure how to proceed with this PR.

I'll close this PR as stale. If you think it's worth merging, I'm happy to re-open and resolve merge conflicts.


Fixed issue #9971

Issue Reference
fixed issue #9971

Checked and Found that the issue has been fixed and  working fine. Please check the video for reference.
Video
https://github.com/bagisto/bagisto/assets/92721837/245635e7-ae36-4909-bfc7-1c4c88979090

This PR is raised from the master branch and the issue not fixed properly so I am closing this PR
New PR raised for this issue - https://github.com/bagisto/bagisto/pull/9977


Jesse: Watch timetofixdubai.com

Jesse requests the watch of the watch_keyword timetofixdubai\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Mast in Charcoal HQ


Ensure the default improver works in all cases

See this https://github.com/nexB/vulnerablecode/pull/664/files#r845773962
The current implementation does not work for the NVD data because there are no affected package yet, default improver should handle all the cases.

Fixed in #693


Make dataCy mandatory on inputs

I want to merge this change because...
dataCy tags are used for cypress e2e tests.
Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Changes are mentioned in the changelog.

After discussion we choose to change the approach of assigning test markers -> #757


unixPB: Remove OpenSSL 1.0.2r playbook

OpenJ9 no longer requires this as we fetch
the latest version during the builds.
Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>
Checklist

[ ] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

I suppose. We (OpenJ9) have been cloning the latest openssl code in the build for a long time. I guess we would have to see if there were any releases built without having the source pulled and what the likelihood is we would ever need to rebuild that version.
@pshipton may have a better idea or an opinion.
Also cc @sxa since he is reviewing the sibling PR.
Looking at the Git history, the playbook was first committed on Apr 18, 2019 and the OpenSSL clone script was first committed to the jdk11 extensions repo on Dec 6, 2018. Also, the openjdk-build linux.sh added the check for 1.0.2r on Apr 9, 2019. Given the extensions change was the first one to go in, I would say that this will never be needed.

I think the likelihood of having to rebuild such an old release is extremely low. The OpenJ9 project has no expectations that older builds can be re-built after the following release comes out. I don't know that anything keeps track of the test SHAs matching each release, maybe that has been tracked at AdoptOpenJDK? Otherwise we can't test a rebuild. If there is desire to rebuilt old releases, it makes more sense to me that tags or SHAs are recorded for the playbooks, rather than trying to keep the head stream in shape to build any release.


Incompatible version constraints on async

I am trying to get my flutter_gallery app to work
When I run pub get or pub upgrade
Resolving dependencies... (19.3s)
Incompatible version constraints on async:

flutter_gallery depends on version 2.0.6
pub itself depends on version >=1.8.0 <2.0.0

When I run flutter analyze
Running "flutter packages get" in flutter_gallery...
Package file has no versions that match 2.3.6 derived from:

flutter_driver 0.0.0 depends on version 2.3.6
flutter_gallery depends on version 2.3.7
pub get failed (1)

Can someone help me resolve these ?

I'm getting same issue ...

@KeshavAdityaRP , @Raymond69 do you get the same results from running flutter update-packages ?

@jonahwilliams Unfortunately yes ...

What about flutter update-packages --force-upgrade
I believe this is supposed to update constraints in pubspec.yaml, not only load the latest version within these constraints.

Got the same issue ..

What Flutter version are you using? (flutter -v)
Have you tried with latest dev channel, or only beta channel. I remember having issues with async as well recently but it's fixed for me.

Flutter 0.1.5 • channel beta • https://github.com/flutter/flutter.git
Framework • revision 3ea4d06340 (3 weeks ago) • 2018-02-22 11:12:39 -0800
Engine • revision ead227f118
Tools • Dart 2.0.0-dev.28.0.flutter-0b4f01f759

I think you should try dev channel. flutter channel dev flutter doctor flutter update-packages --force-upgrade

@KeshavAdityaRP Do you still see this on current builds? We were having some issues with old packages back in March.


Use more Rust like interfaces for Config

Just some small changes
For gbdt::config::Config,

a ConfigBuilder (following the builder pattern) that has a build() method to create a Config() object is more Rust like.
The to_string() method is not necessary if you implement Display.
The config.set_loss function takes str rather than an enum.

Are you open to PRs?

Thanks! I’d happy to merge PRs!


Suggestion/Question regarding the update script

I've only recently noticed that the update script will update to the master branch of the theme instead an official release version.
My suggestion/question would be that maybe the script should update the latest release tag instead. The "question" part is whether grabbing the master branch is the intended effect of the update script. I've seen a few issues now that are generally related to unknowingly using the master branch (and thus running into bugs) that probably could've been avoided by only upgrading on an official release.
See gcushen/hugo-academic/issues/614 and gcushen/hugo-academic/issues/1638 as examples of improper use of the master branch.

See https://sourcethemes.com/academic/docs/update/ . The official recommended approach that is documented on the site is to upgrade to a specific version.
The purpose of the update script in the Kickstart repo is to display any new commits from the master branch and provide the option to install those commits. Its primary purpose is for the repo maintainers to use rather than site admins, although site admins may find it useful if they wish to use the bleeding edge version.

Gotcha. Thanks for the clarification.

It might be worth mentioning this clarification in the documentation. Looking back on it, the info box seems to suggest that the script is for official use rather being an alternative to the process detailed.


"fig run" should support port forwarding

+1

+1

Anyone +1-ing now, this has been implemented in https://github.com/docker/fig/pull/485 and is scheduled for the next (1.1) release.

@thaJeztah Thanks. Yep but any ETA for release?

Don't know, perhaps one of the maintainers can give an eta, otherwise just be patient :)

@ColCh see #729

@dnephin ver bump will be great :+1:

+1

A release candidate for fig (now docker-compose) was just released;
https://github.com/docker/fig/releases/tag/1.1.0-rc1
Make sure to read the release-notes and README for the changes involved in the rebranding to compose

The syntax is:
$ docker run --service-ports SERVICE

@aanand Do you mean docker-compose run --service-ports SERVICE ?

@iMerica Oops, yes.


WIP OAuth2 Support

Description
Update API to support OAuth Server-to-Server client credentials approach to Authentication.
Related Issue
#155
Motivation and Context
Updates library to prepare for removal of deprecated JWT solution.
How Has This Been Tested?
Update existing unit tests, and added new ones.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.

Wow, thank you @bstopp !!!  @francoisledroff  is out this week, but will review when he is back.

@francoisledroff  - I don't know why the integration tests are failing. Its saying NPE, which indicates it can't find the fallback properties file. The actions should have all the necessary properties defined to successfully run these checks.
I don't have the information necessary to run the IT tests offline. I'm not sure if this is something you can do, to check the updates and make sure it wasn't something i introduced?

I went ahead and updated all the plugins and dependencies to latest releases.
I'll be going back and adding more tests over the next couple of days while folks find time to review.

@bstopp the IT tests are leveraging GH secrets only available on the main remote repo.
If you push your change against a remote branch and update your PR accordingly,
the IT test should run (using the  deprecated JWT authentication)


CVAE Encoder Output and Decoder Input Shapes Don't Match

The encoder-decoder network doesn't need to be symmetric


[BUG] Cannot instantiate postgresql 9.6 instance

General information

OS: Linux
Hypervisor: KVM
Did you run crc setup before starting it (Yes/No)? Yes

CRC version
# Put `crc version` output here
version: 1.0.0-rc.0+34371d3
OpenShift version: 4.2.0-0.nightly-2019-09-26-192831 (embedded in binary)

CRC status
# Put `crc status` output here
CRC VM:          Running
OpenShift:       Running (v4.2.0-0.nightly-2019-09-26-192831)
Disk Usage:      17.83GB of 32.2GB (Inside the CRC VM)
Cache Usage:     15.95GB
Cache Directory: /home/phantomjinx/.crc/cache

CRC config
# Put `crc config view` output here
- cpus                                  : 4
- memory                                : 12288

Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
NAME=Fedora
VERSION="29 (Twenty Nine)"
ID=fedora
VERSION_ID=29
VERSION_CODENAME=""
PLATFORM_ID="platform:f29"
PRETTY_NAME="Fedora 29 (Twenty Nine)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:29"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=29
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=29
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"

# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

Steps to reproduce

Create project
Open console, go to +Add & select Database
Select Postgresql
Click Instantiate Template

Expected
New instance of postgresql database pod should be running
Actual

Pod fails to start and is listed and 'unschedulable'
Clicking on pod's events show '0/1 nodes are available: 1 Insufficient memory.'
Single master node reports resources as:

status:
  capacity:
    cpu: '4'
    hugepages-1Gi: '0'
    hugepages-2Mi: '0'
    memory: 7778264Ki
    pods: '250'
  allocatable:
    cpu: 3500m
    hugepages-1Gi: '0'
    hugepages-2Mi: '0'
    memory: 7163864Ki
    pods: '250'

Logs
Nothing in logs pertaining to postgresql or 'insufficent memory'
You can start crc with crc start --log-level debug to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.

Can you try crc delete && crc config set memory 16000 && crc start and try again to create your postgresql instance?

That seemed to do the trick. Curious why 12GB was not enough memory, especially as docs require only 8GB?

@phantomjinx so I also tried something below and able to make it work with 8GB only, did you also have other workloads on that cluster?
Postgresql template suppose to have maximum memory limit 512Mi and this amount of memory should be available by default until you have other workload is running.
$ oc get template  postgresql-persistent -n openshift -o yaml | grep -n2 -i memory
135-          resources:
136-            limits:
137:              memory: ${MEMORY_LIMIT}
138-          securityContext:
139-            capabilities: {}
--
163-  status: {}
164-parameters:
165:- description: Maximum amount of memory the container can use.
166:  displayName: Memory Limit
167:  name: MEMORY_LIMIT
168-  required: true
169-  value: 512Mi

$ oc new-project testdb
$ oc new-app postgresql-persistent
$ oc get all
NAME                      READY   STATUS      RESTARTS   AGE
pod/postgresql-1-deploy   0/1     Completed   0          46m
pod/postgresql-1-v9mmx    1/1     Running     0          45m

NAME                                 DESIRED   CURRENT   READY   AGE
replicationcontroller/postgresql-1   1         1         1       46m

NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
service/postgresql   ClusterIP   <IP_ADDRESS>   <none>        5432/TCP   46m

NAME                                            REVISION   DESIRED   CURRENT   TRIGGERED BY
deploymentconfig.apps.openshift.io/postgresql   1          1         1         config,image(postgresql:10)

$ oc get pods postgresql-1-v9mmx -o=json | jq '.spec.containers[0].resources'
{
  "limits": {
    "memory": "512Mi"
  },
  "requests": {
    "memory": "512Mi"
  }
}

@praveenkumar can you confirm the DiskUsage on your end with crc status ?

@gbraad Disk space is enough for running only the posgresql container.
$ ./crc status
CRC VM:          Running
OpenShift:       Running (v4.2.0-rc.1)
Disk Usage:      11.88GB of 32.2GB (Inside the CRC VM)
Cache Usage:     10.95GB
Cache Directory: /home/prkumar/.crc/cache

Disk Usage:      17.83GB of 32.2GB (Inside the CRC VM)

Disk Usage:      11.88GB of 32.2GB (Inside the CRC VM)

The reporter surely had more running or stored inside the VM.

@phantomjinx please describe the other workload or images that might be there and after this can you run the test on a new CRC instance? (removing the previous one)

Originally I had begun to install syndesis which has

syndesis-db (based on image of postgresql)
oauth-proxy
prometheus
syndesis-operator

So naturally, that failed to bring up the syndesis-db due to postgresql
Tried to bring up postgesql 9.6 image on its own & that failed
Cleared out the project several times and tried postgresql on its own & failed
Deleted crc entirely and upped mem to 16GB & works
Syndesis is not big & shkuld no way have resulted in insufficient memory especially when nothing else is running.
Maybe crc did not like the 12GB memoey setting?
Wonder if (this)[https://github.com/kubernetes/kubernetes/issues/45237] might have had a bearing?

Syndesis runs prometheus which is know to need more than the default 8GB assignment.
So you hadn't tried Postgresql by itself on a new instance of CRC with the default assignment of 8GB of memory, right?
The issue you refer to is from a long time ago. If so, this would certainly have been reported more than once.

That is does but having installed evrrything now with 16GB of memory, everything comes up fine.
Just to higlight:
I never ran crc with the default 8GB. I ran into problems with 12GB.
I deleted everything in the project and ran only postgresql & it still would not execute.
On 11 October 2019 16:20:10 BST, Gerard Braad<EMAIL_ADDRESS>wrote:

Syndesis runs prometheus which is know to need more than the default
8GB assignment.
So you hadn't tried Postgresql by itself on a new instance of CRC with
the default assignment of 8GB of memory, right?
The issue you refer to is from a long time ago. If so, this would
certainly have been reported more than once.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/code-ready/crc/issues/706#issuecomment-541108241

--
P. G. Richardson

Ty-Carreg Barn, Penyrheol, Pontypool, Torfaen. UK
01495 762483
<EMAIL_ADDRESS>

I deleted everything in the project and ran only postgresql & it still would not execute.

Not sure about what remained behind or caused the scheduler to not see the freed resources. This is more of an issue with OpenShift itself and would appreciate if you reported it there also.
Not sure why, but we are able to schedule postgresql with 8GB :-/

I will mark the issue as closed as you are able to run the actual container,
Resources might be contrained, but this is documented on how to solve and also discussed in other issues to see what can be done to lower the memory usage, however these involve discussions with the OpenShift team.


Permission.Notification crash in IOS

koltin: v2.0.10
compose: v1.6.11
calf: v0.5.3
In android works well, but in ios when I call
`
val notificationStatePermission = rememberPermissionState(
permission = Permission.Notification,
onPermissionResult = { isGranted ->
    }
)

`
It throws an exception. ( I already added NSUserNotificationsUsageDescription)
Uncaught Kotlin exception: kotlin.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied
Am I doing wrong something?

Thanks for reporting this issue, I'm checking it.

I used this solution temporarily.
In summary: I used  MainScope().launch(Dispatchers.Main.immediate)
@Stable
internal actual class MutablePermissionState(
    actual override val permission: Permission,
    private val onPermissionResult: (Boolean) -> Unit,
) : PermissionState {
    actual constructor(
        permission: Permission,
    ) : this(permission, {})

    actual override var status: PermissionStatus by mutableStateOf(PermissionStatus.Denied(false))

    private val permissionDelegate: PermissionHelper = getIOSPermission(permission)

    init {
        refreshPermissionStatus()
    }

    actual override fun launchPermissionRequest() {
        permissionDelegate.launchPermissionRequest(
            onPermissionResult = { isGranted: Boolean ->
                onPermissionResult(isGranted)
                // Update status on the main thread
                updateStatus { refreshPermissionStatus() }
            }
        )
    }

    actual override fun openAppSettings() {
        val settingsUrl = NSURL.URLWithString(UIApplicationOpenSettingsURLString) ?: return
        UIApplication.sharedApplication.openURL(settingsUrl)
    }

    internal actual fun refreshPermissionStatus() {
        permissionDelegate.getPermissionStatus { status: PermissionStatus ->
            // Ensure status update is on the main thread
            updateStatus { this.status = status }
        }
    }

    private fun updateStatus(action: () -> Unit) {
        // Use the main dispatcher to ensure Compose state is updated correctly
        MainScope().launch(Dispatchers.Main.immediate) {
            action()
        }
    }
}


fix partition-logic

fix partition-logic

Codecov Report
Patch coverage has no change and project coverage change: -0.37 :warning:

Comparison is base (3d9d942) 30.55% compared to head (fd34608) 30.19%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1284      +/-   ##
==========================================
- Coverage   30.55%   30.19%   -0.37%
==========================================
  Files         338       29     -309
  Lines       39102     2305   -36797
  Branches    11614     1327   -10287
==========================================
- Hits        11948      696   -11252
+ Misses      26896     1609   -25287
+ Partials      258        0     -258

Flag
Coverage Δ

adapter
?

admin-domain-service
?

backoffice-domain-service
?

config-deployer-service
14.62% <ø> (-0.04%)
:arrow_down:

devportal-domain-service
?

idp-domain-service
80.10% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 311 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Map viz: Clarify to users that the "Other" category is dynamic

When there are more than 8 categories (SCORE S. mansoni randomized controlled trial-->Occupation is an excellent example that I didn't know about during implementation/testing) in the overlay variable, the back end will calculate the top 7 individual categories, and then lump everything else remaining into "Other".
We need to have some UX discussions how best to communicate this to users.  They may see "Other" as an actual database-stored value in the same or other studies.

I moved this to web-eda, but we can move it again, if we decide to handle this on the backend.

I'm closing this ticket. We have decided that Other should NOT be dynamic. This ticket will change the variable constraints to prevent high cardinality variables from being used on the map: https://github.com/VEuPathDB/EdaNewIssues/issues/596


Proper Means of Specifying Duplicate Timepoints

Is there a recommended way for specifying duplicate time points to eJTK?  Should they just be identically labelled?  I couldn't find anything in the documentation on this.  Thanks very much!

Hi,
The algorithm will automatically mod 24 the data, so you can leave them
different or make them the same depending on preference.
Thank you for brining this to my attention. I will update the README.
Alan
On Sunday, September 18, 2016, Alec Crowell<EMAIL_ADDRESS>wrote:

Is there a recommended way for specifying duplicate time points to eJTK?
Should they just be identically labelled? I couldn't find anything in the
documentation on this. Thanks very much!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alanlhutchison/empirical-JTK_CYCLE-with-asymmetry/issues/4,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADeP_PMCj-rPXQaUKgeKgCXYlxd69hGoks5qrVtGgaJpZM4J_7pu
.

--
Alan L Hutchison
Ph.D. Biophysics
MD Candidate
Pritzker School of Medicine
University of Chicago


🔍 Radix feature parity tracking

Remaining primitives until feature parity
In progress:

#20
#48
#89
#76
#87

todo:

[ ] Aspect Ratio
[ ] Context Menu
[ ] Form
[ ] Hover Card
[ ] Menubar
[ ] Navigation Menu
[ ] Scroll Area
[ ] Toast

Thank you for this! TBH I feel we can skip Aspect Ratio, since aspect-ratio has really nice browser support.

I'm going to close this issue and create separate ones!


Create a list of XMTP allowed chains for Smart Contract Wallets

We have settled on this list to start. Will need to verify that all these RPC urls support archival queries that specify a block number.
{
"1": "https://eth.llamarpc.com/",
"10": "https://rpc.ankr.com/optimism",
"137": "https://polygon.llamarpc.com/",
"324": "https://mainnet.era.zksync.io/",
"8453": "https://base.llamarpc.com/",
"42161": "https://arbitrum.llamarpc.com/",
"59144": "https://linea-rpc.publicnode.com/"
}


Don't persist the npm cache across CI tests.

Hopefully this will fix the greenkeeper issues.

Hopefully fixes #496

r+


New Task - Export "paper" catalog

As a user, I want to export my catalog project to a mostly "publication-ready" format. Minimally, this should include the following data levels:

All taxon names, relationships, combinations (text from "Browse nomenclature"?)
All asserted distributions for the OTUs linked to those taxon names.
All sources from taxon names, relationships, and asserted distributions

This exported catalog could include soft validation warnings (see issue: #1450 )
When exported, it should be assigned a "version" and always be available for reference as a snapshot of the catalog.
Something like this ZooKeys paper may be a good starting point:
https://doi.org/10.3897/zookeys.920.39128

Would also be nice if we could also dump data associated with the OTU tied to the nomenclature (i.e., biological associations, type data, and asserted distributions).

Root ID would be any of the families in our project. For example: https://sfg.taxonworks.org/tasks/nomenclature/browse?taxon_name_id=447962

All these features exist in the current implementation.  Closing for new issues highlighting individual issues.


Pinned foldl dependency does not conform with playground-common's one

When attempting to use plutus-extra in a project, cabal throws an error:
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: playground-common-<IP_ADDRESS> (user goal)
[__1] trying: foldl-1.4.11 (dependency of playground-common)
[__2] next goal: plutus-extra (user goal)
[__2] rejecting: plutus-extra-1.0 (conflict: foldl==1.4.11, plutus-extra =>
foldl^>=1.4.12)
[__2] fail (backjumping, conflict set: foldl, plutus-extra)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: foldl, plutus-extra, playground-common

It seems that pinned foldl in plutus-extra is expecting higher foldl version than required by playground-common.

This is quite surprising. According to cabal freeze, our overall dependencies include foldl-1.4.12. What Plutus revision is that project using? Does it differ from 289ac956a33c14fe1d75d6c0a6d6100f96a7d22c?

Yes, it was a problem with a project trying to depend on plutus-extra. It was using older Plutus, thus the incompatibility. Closing the issue then.


fix: small fixes around input DA variables

Description
Issue: https://github.com/terraform-ibm-modules/terraform-ibm-icd-elasticsearch/issues/297

[ ] existing_kms_key_crn is currently in the required list but should be moved to optiona
[ ] move use_existing_resource_group next to resource_group_name in ui (on required).
[ ] elser_model_type -> this is only applicable if plan is platinum (not for enterprise). At minumum indicate it in the description of the variable.
[ ] skip_es_sm_auth_policy -> use full service name when they are not obvious to typical end-user (skip_elastic_search_secret_manager_auth_policy or skip_elastic_search_to_secret_manager_auth_policy)
[ ] existing_db_instance_crn -> use elastic_search instead of db for consistency in naming.
[ ] skip_iam_authorization_policy and skip_es_sm_auth_policy are inconsistent in term of naming.
[ ] group related inputs together in ui - eg: all kms related input together.

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

   "Result": {
        	            	│         "errors": [
        	            	│             {
        	            	│                 "code": "zone_used_by_rule",
        	            	│                 "message": "The network zone '53e58ce8397c1fbc6b61497b734effa5' is referenced by one or more rules and cannot be deleted."
        	            	│

rerunning

/run pipeline

@akocbek what happened to this one? Is it good to go? If so, can you update the release notes section of the PR description and get pipeline passing please?

/run pipeline

/run pipeline

created new PR https://github.com/terraform-ibm-modules/terraform-ibm-icd-elasticsearch/pull/374


Add Docker support

Thanks for your contribution @hgw8 , closing this MR since the code has been refactored and docker-compose support added.


show multicast "connections"

Not sure if this should be the case, but I have two clusters running with three instances of multicast running on each.  None of the containers show that these containers have "discovered each other" on the network, although they have when you open the terminal to view the messages.   Should there not be connections or some indication that they are in a 'multicast group' between the containers listed here?  The host view does show connections.

multicast is UDP; scope only shows TCP connections.


Adjust order of properties

A very minor patch, but my style guide requires that components properties are sorted alphabetically. Because these two are not, I need to patch my components every time I re-generate Panda components.

I think this is a good style guide to follow.


Slide push to Slide Over

Hi, loving this plugin. Wonder if  possible to slide over the slideout.js menu without pushing the panel.  Similar to screenshot.

I wish to get the same idea.


Support for embedding Twitter threads

The embedding of single tweets is great, but there doesn't seem to be a way to render an entire thread. Thoughts?
One option: support for embedding threads a la thread reader.
[Twitter link](https://twitter.com/tannerc/thread/1539248244823404544)
or with an attribute.
[Twitter link|thread](https://twitter.com/tannerc/status/1539248240159334406)

Yes, this would be great. Unfortunately, the first-party Twitter embed does not support showing entire threads. I haven't been able to find any alternative that could easily do this, but I'll keep my eyes open.


Yup, I am experiencing the same thing still in version 1.36.1

Yup, I am experiencing the same thing still in version 1.36.1
Originally posted by @sts24 in https://github.com/microsoft/vscode-css-languageservice/issues/152#issuecomment-517778554

Please, don't create another the same ticket if already exist.
Instead put thumb up in there or type more information
We need to respect the time of the VSCode programmers team


SEPG Automated Release - v1.2.1

SEPG Details
Release Build Link: http://sou-jenkins2.swinfra.net:8080/job/Auto-Release/47/
Build Token: github.com/CAFapi/opensuse-java17-images/main/75bb01fd6ada49b2b575532b3ae03ee04a348618
Versioning Behaviour: Roll on to next minor
Artifacts For Release
Docker

cafapi/opensuse-jdk17:1.2.1 (Static Tag)
cafapi/opensuse-jdk17:1.2 (Dynamic Tag)
cafapi/opensuse-jdk17:1 (Dynamic Tag)
cafapi/opensuse-jdk17:latest (Dynamic Tag)
cafapi/opensuse-jre17:1.2.1 (Static Tag)
cafapi/opensuse-jre17:1.2 (Dynamic Tag)
cafapi/opensuse-jre17:1 (Dynamic Tag)
cafapi/opensuse-jre17:latest (Dynamic Tag)

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here


Appstudio update test-component-pac-acht

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-acht-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
17 seconds
init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
36 seconds
inspect-image

✅ Succeeded
33 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
13 seconds
show-summary

Pipelines as Code CI/test-component-pac-acht-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
17 seconds
init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
36 seconds
inspect-image

✅ Succeeded
33 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
34 seconds
sbom-json-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
13 seconds
show-summary

Pipelines as Code CI/test-component-pac-acht-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
32 seconds
build-container

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
52 seconds
clamav-scan

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
13 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
9 seconds
show-summary

✅ Succeeded
7 seconds
show-sbom

Pipelines as Code CI/test-component-pac-acht-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
32 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
15 seconds
inspect-image

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
52 seconds
clamav-scan

✅ Succeeded
13 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
9 seconds
show-summary

✅ Succeeded
7 seconds
show-sbom


Controlling the version when installing as package?

Cookbook version
6.0.2
Chef-client version
12.19.36
Platform Details
Ubuntu 14.04
Scenario:
Upgrade nginx package version. After the package has been installed for the first time on the node (whether it be manually or with chef), the version of the package is fixed and there is no way to upgrade it anymore using this cookbook without manual intervention.
Steps to Reproduce:

include_recipe 'chef_nginx' without setting any attribute - the distro version of nginx would be installed, in my case 1.4.6.
set node.default['nginx']['repo_source'] = 'nginx' and run the recipe on the same node again.

Expected Result:
nginx package would be upgraded, either by the version specified by node['nginx']['version'], or by installing the version available from the new source.
Actual Result:
The nginx repository is added as a source, but the package is not installed, leading to this:
nginx:
  Installed: 1.4.6-1ubuntu3.7
  Candidate: 1.12.0-1~trusty
  Version table:
     1.12.0-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.10.3-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.10.2-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.10.1-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.10.0-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.8.1-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
     1.8.0-1~trusty 0
        500 http://nginx.org/packages/ubuntu/ trusty/nginx amd64 Packages
 *** 1.4.6-1ubuntu3.7 0
        500 http://eu-central-1a.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1.4.6-1ubuntu3 0
        500 http://eu-central-1a.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

also, going into chef-shell to check the version I see this:
chef (12.19.36)> node['nginx']['version']
 => "1.4.6"

I realize that node['nginx']['version'] is used only for source installation, but I really don't understand why? what control does this cookbook give me over the nginx installation on my nodes if I cannot perform package upgrades?

Upgrades are not a scenario for this cookbook. In general we shy away from upgrades in Chef recipes since that would cause outages as nodes automatically upgrades and restarted nginx when a new version became available. It's a scary thing to do. If you want to specify an upgrade to a specific version once the repo is setup that's pretty easy to do in a simple wrapper cookbook. Just use the package resource.


remove unique name validation

Remove unique name validation from probe configuration's name field, since duplicate configuration names can be used to unify their results in charts.

removed in 51e5db5


What about the future of Bot Composer ?

Hello everyone, i was wondering about Bot Composer support of Microsoft's new technologies from Azure Cognitive Services For Language and bot composer's future as a whole.
While searching answers i saw two comments that made me hesitant :

https://learn.microsoft.com/en-us/azure/cognitive-services/language-service/conversational-language-understanding/how-to/migrate-from-luis?tabs=luis-portal in this article where João Carlos Santos said as of 12/05/22 "there are no plans to integrate CLU in Bot Composer as LUIS was" in the comments
https://github.com/microsoft/BotFramework-Composer/issues/9400 in this issue where Dewain27 said as of 10/18/22 "CLU guidance will be coming in the months ahead"

Is the situation of Bot Composer update clearer now and if yes, is the project on standby (as João said in the article) or not ?
Thank you.

Also interested in knowing this. It seems like it may be deprecated in favor of power virtual agents.

Hello, sorry for the delay in responding.
The Bot Framework composer is in released state and continues to get production support in terms of bug fixes and security updates.  We do not have plans to introduce additional features and capabilities currently.
Given the composer is extensible and customers can provide their own recognizers, it's feasible that you might consume CLU within your composer bot, however we do not have plans for more native integration than that.
As @CharlieEvert mentioned, we do have ongoing investments to bring the richness of the Bot Framework Composer into Power Virtual Agents; the first iteration of which is in preview today.

Good to know, thank you !

Thank you for sharing the update.


ngx-admin is not working in IE 11 and Mac Safari

I am not able to resolve IE11 and Mac Safari browser display issues. Can you please let me know the solution to resolve this problem.
When I see Online demo (https://akveo.com/ngx-admin/pages/dashboard) in IE 11, Demo is working fine but when I download the same demo from Github and run the demo, it's not working in IE and Mac Safari browser.
I have also added polyfills.ts file with require configuration.
Steps to reproduce:

Download ngx-admin from github (https://github.com/akveo/ngx-admin)
Run Command "npm install"
"ng serve"
Run your localhost URL in Chrome and IE 11 (Not IE edge)
Demo is not working in IE11 and Safari, it's working in Chrome and firefox.

Please help me resolved this problem.
Thanks,

Screenshot.

For Angular 8, "ng serve" generate a single build which is not compatible with IE11 (not sure about Safari). This is by design and workarounds are explained here.

Thanks @baloglu! Closed as answered


Failed to launch the browser process!

I get this error when I start my next app with yarn dev
error - Error: Failed to launch the browser process! spawn C:\Program Files (x86)\Google\Chrome\Application\chrome.exe ENOENT

I have chrome installed on my system but its, not in the path printed in the error. It is in the 64bit folder. C:\Program Files\Google\Chrome\Application
My ENV

Node <IP_ADDRESS>
Next 12.1.0
chrome-aws-lambda 1.6.3
Windows

same problem here. I used the following steps

yarn create next-app –typescript
yarn add next-api-og-image chrome-aws-lambda
Create github repo and push
added file pages/api/ogimage/index.js with code pasted from https://github.com/neg4n/next-api-og-image/blob/main/example/pages/api/basic.js
Create Vercel app and deploy
When i visit the url i see the generic Next home page
When i visit /api/ogimage,
Then it fails with 500 error and logs say

[GET] /api/ogimage
11:06:35:54
2022-05-23T15:06:40.106Z	6ea5bf36-a40a-4c0a-998e-891d7abd8541	ERROR	Error: Failed to launch the browser process!
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
    at onClose (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:197:20)
    at Interface.<anonymous> (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:187:68)
    at Interface.emit (node:events:532:35)
    at Interface.close (node:readline:586:8)
    at Socket.onend (node:readline:277:10)
    at Socket.emit (node:events:532:35)
    at endReadableNT (node:internal/streams/readable:1346:12)

same problem here. I used the following steps

yarn create next-app –typescript
yarn add next-api-og-image chrome-aws-lambda
Create github repo and push
added file pages/api/ogimage/index.js with code pasted from https://github.com/neg4n/next-api-og-image/blob/main/example/pages/api/basic.js
Create Vercel app and deploy
When i visit the url i see the generic Next home page
When i visit /api/ogimage,
Then it fails with 500 error and logs say

[GET] /api/ogimage
11:06:35:54
2022-05-23T15:06:40.106Z	6ea5bf36-a40a-4c0a-998e-891d7abd8541	ERROR	Error: Failed to launch the browser process!
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
    at onClose (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:197:20)
    at Interface.<anonymous> (/var/task/node_modules/puppeteer-core/lib/cjs/puppeteer/node/BrowserRunner.js:187:68)
    at Interface.emit (node:events:532:35)
    at Interface.close (node:readline:586:8)
    at Socket.onend (node:readline:277:10)
    at Socket.emit (node:events:532:35)
    at endReadableNT (node:internal/streams/readable:1346:12)

@linojon I think your Problem is a different one. If you are using Node 16.x on Vercel try version 14.x. Because not all versions of chrome-aws-lambda support version 16

I have chrome installed on my system but its, not in the path printed in the error.

It's due to the following code:
https://github.com/neg4n/next-api-og-image/blob/7bdcfa5a12dacfec505833fb797898f2d919777b/src/index.ts#L206-L215
Fortunately, this code only takes effect when in the development environment.

Hey folks! Sorry for late response.

@linojon I think your Problem is a different one. If you are using Node 16.x on Vercel try version 14.x. Because not all versions of chrome-aws-lambda support version 16

Thanks @Sumis34 for pointing this out. I'll add it to the README.md in section that describes alternative chrome-aws-lambda setup 🚀

I get this error when I start my next app with yarn dev
error - Error: Failed to launch the browser process! spawn C:\Program Files (x86)\Google\Chrome\Application\chrome.exe ENOENT

I have chrome installed on my system but its, not in the path printed in the error. It is in the 64bit folder. C:\Program Files\Google\Chrome\Application
My ENV

Node <IP_ADDRESS>
Next 12.1.0
chrome-aws-lambda 1.6.3
Windows

Thanks for reporting this. I'll add support for Windows 64bit path 🤟🏻
Cheers, Igor

https://github.com/neg4n/next-api-og-image/releases/tag/4.2.1


GreasedLine - first commit

@RaananW Finally it's here!

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13840/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13840/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13840/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13840/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13840/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13840/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13840/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13840/merge#BCU1XR#0

Great PR! I will perform a review tomorrow.
Note: you should also remove the comments that are not needed (like some commented imports).

Awesome !!!! I will do a pass right after @Popov72 and @RaananW :-)

Note that you forgot a few comments:

You must click on the "Load more..." button ;)

60 more... What? 😂😂

This is getting pretty close !!! @Popov72 I ll do a final pass once you ll be all good with the latest iteration :-)

I'm waiting for the official "go" from @RolandCsibrei, to make sure there are no further updates planned.

Can not wait :-)

friendly ping @RolandCsibrei :)

@Popov72 I'll go trough my code today again and will give you a go if everything is working on Windows/MAC/WebGL/WebGPU tomorrow.

@Popov72 let's give it a try! thank you!

@Popov72 Hello, I've fixed the remaining issues. Can you check it please?

Almost there!
cc @carolhmj so she can review her remaining open conversations.

@carolhmj Hello! Can you please resolve the conversations? Thank you!

@carolhmj  Hello! I've resolved the two remaining conversations with you as they were only nits. Hope you don't mind.

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13840/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13840/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

You should avoid using red colors in the visualization test, because it's the color we use to show differences between the reference image and the rendering :)

Thanks! Neverending story... :-)
On Tue, Jun 20, 2023, 11:22 AM Popov72 @.***> wrote:

You should avoid using red colors in the visualization test, because it's
the color we use to show differences between the reference image and the
rendering :)
—
Reply to this email directly, view it on GitHub
https://github.com/BabylonJS/Babylon.js/pull/13840#issuecomment-1598423880,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYKGHJ2UBXWUIXQVZIWDMTXMFTV3ANCNFSM6AAAAAAX4W6TCE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13840/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Please fix formatting and it will merge automatically :)

Please fix formatting and it will merge automatically :)

Already did it ;-) Sorry...

@deltakosh
auto-merge was automatically disabled [2 minutes ago]
Head branch was pushed to by a user without write access
(https://github.com/BabylonJS/Babylon.js/pull/13840#event-9581204978)
;-(
Head branch was pushed to by a user without write access

Congratulations by the way! This is a fantastic PR!

Thanks a lot!

Congrats!
For your first PR it's quite an achievement!

@Popov72 Thank you! and thank you! ;-)


Update README.md

Added some instructions to address #22 issues.

Is this still an issue on Terminus 3 @cleverington?

Hopefully, this issue has been resolved in Terminus 3.


Exit with a non-zero exit code when operations fail.

presto-admin should adhere to the convention that a failure results in a
non-zero exit code. presto-admin runs stuff on potentially many hosts, and
actions can fail on some hosts but not others. This change takes the approach
that in order to exit with an exit code of zero, every action taken against
every host must succeed.
A quick tour of the changes:
Because of the way fabric works, we see failures as SystemExit, which we were previously catching and ignoring. We now stick the exception into the per-host results dictionary. The dictionary maps hosts to exceptions. If none of the hosts have an exception, we exit with an exit code of zero, otherwise we exit with an exit code of one.
In order to propagate failure information correctly, I needed to update a bunch of decorators to return the result of the wrapped function. I wrote most of 'em wrong in the first place, so mea culpa on that one :-)
In the tests, there are a number of places where we were invoking presto-admin and parsing error output. Because pa now exits with a non-zero exit code on error, I had to update the tests so that we don't raise an error when pa exits with a non-zero exit code.
Separated into 2 commits for easy reviewing, will squash before pushing as they need to go in together. If you look at the individual commits, the change to docker_cluster.py in 9491aba is spurious and I undid it in ade1c03

looks good


bypass

just keeps showing looks like this page isn't allowed when i try to open it

I'm not entirely sure what you're saying, but this Securly blocked page is on the chrome-extension: scheme (i.e. protocol) instead of the https: scheme. When the Securly blocked page is on the chrome-extension: scheme, it usually means it detects "unsafe" code from either a policy-enforced guideline or a native Securly-enforced guideline.


Task "libresCreateSymlinkedBundles" does not appear run on all modules in a project

I have a multi-module KMP project with 2+ modules containing Compose Multiplatform UI composables - and ideally - each module containing its own resources. I have the Libres plugin applied and configured for each Gradle module, and cocoapods-native configured for each module as well.
I have a shared module that is the top-level logic for the app, and then it depends on other compose multiplatform modules.
When building for iOS, I'm able to see the Libres auto generation running for each module:
> Task :shared:libresGenerateImages UP-TO-DATE
> Task :shared:libresGenerateIosBundle UP-TO-DATE
> Task :shared:libresGenerateStrings UP-TO-DATE
> Task :shared:libresGenerateResources UP-TO-DATE
> Task :screenOne:libresGenerateImages UP-TO-DATE
> Task :screenOne:libresGenerateIosBundle UP-TO-DATE
> Task :screenOne:libresGenerateStrings UP-TO-DATE
> Task :screenOne:libresGenerateResources UP-TO-DATE

And in fact, the Libres.bundle directory ends up in the generated folder for each module. However, the symlinks task only runs once:
> Task :shared:compileKotlinIosSimulatorArm64 UP-TO-DATE
> Task :shared:libresCreateSymlinkedBundles
> Task :shared:linkPodDebugFrameworkIosSimulatorArm64 UP-TO-DATE

It's possible I do not have my screenOne module configured correctly, though it is almost identical to the shared module.
In looking through the plugin code, my operating theory is that the exportedProjects parameter of this method is an empty list for the screenOne module, though I can't quite figure out why. But if it's an empty list, then the symlinks would not in fact be created for the project.
internal fun createBundlesSymLinks(rootProject: Project, exportedProjects: List<Project>) {
    val rootBundlesDir = Path(rootProject.buildDir.absolutePath, appleBundlesDirectory)
    val rootBundleName = rootProject.appleBundleName
    val rootBundle = Path(rootProject.buildDir.absolutePath, appleBundlesDirectory, "${rootBundleName}.bundle")
    if (!Files.exists(rootBundle)) Files.createDirectories(rootBundle)
    exportedProjects.forEach { rootBundlesDir.addSymlinkToBundle(it) }
}

Is there any workaround?

I'm a bit of an iOS n00b, so it's entirely possible I'm not doing things in an idiomatic way in this regard.
I'm used to Android, where each module can have its own resources. I realize "modules" may not be the right term for iOS.
Either way I just need each sub module to create a symlink of the generated bundle directory up to the root build bundle directory. It looks like the library should do that but again it's only running once. Any tips?


Integration tests for docker-compose

We need tests to ensure changes are able to generate packages and that running docker-compose doesn't fail on these changes.
If anyone is interested in working on this that would be great!

I would love to work on this issue, would you please just guide me to what should i do?
I'm thinking of writing a test in js which forks docker compose up, and checking it's exit code.
Will this be fine or should I do something else?
PS. I'm new to this project but want to contribute to this awesome initiative..

The rest of the tests are running in Docker in Circle, but since these would be testing that docker-compose itself works, you'll need to use a VM executor: https://circleci.com/docs/2.0/executor-types/
The test could probably be as simple as

checkout
npm install in all the places
run docker-compose up -d
run something that verifies all the things are up and didn't crash (maybe curl some endpoints and check the output of docker ps to make sure everything's still alive).

After some digginig, I guess, I could use remote docker command for the same
https://circleci.com/docs/2.0/building-docker-images/
Thoughts? If building docker fails, test will fail..

Yep, those docs are a better example than the link I found, especially the last example. If building the containers fails CI should fail, but I think maybe that should be a separate step, since building containers to push to Docker Hub for production deployment is different than spinning up docker-compose and making sure everything can still talk to everything else.

Yeah, we want two things really:

Docker images should build without fail
They should be able to be started with docker-compose and have a working running instance (ideally we'd curl against it to at least give it a litmus check that the server started)

Also @nveenjain thank you for coming by and pitching in!

@toddself do you have Circle access? 1. Docker iamges should build without fail is what this script is for, and my thought was that it should be run on each merge to master and git tag. We'd need a Docker Hub service account credentials added in Circle for that to work.

@zacanger I can give it a shot in the am!

I'm thinking of creating a new build job
  build:
    docker:
      - image: circleci/node:latest
      - image: circleci/postgres:latest
    steps:
      - checkout
      - setup_remote_docker
      - run: npm install
      - run:
          name: Docker compose up
          command: |
            set -ex
            docker-compose up -d

Should i send request to every app after we do docker-compose, also if I'm doing anything wrong, please tell, I've not quite familiar with CircleCI...

I don't think you need the postgres container in there -- the docker compose command should cause a postgres container to be spun up automatically.
@zacanger if it requires putting secret creds into circle-ci that could be a problem -- or we would only have to let that test run on master since even if you have creds in the "secure env variables" section, they still need to be decrypted when passed on the command line which can cause cred leakage :(

Good point. I opened a new issue #291 about this so I don't hijack this issue.


Pod view changes

[Title: describe the change in one sentence]
Add Volume list to Pod view
Add Volume mounts and livenessProbe details to container section
fixes some parts of #173

@joaquimrocha tested and it is perfect now, thanks


Python RuntimeWarning: overflow encountered in long_scalars   if self.max_big_small_squared < big*small**2:

Hi guys!
I am trying to solve a pretty large optimization problem using Python 3.6.5, CVXPY 1.0  and the solver is MOSEK. I'm running it on Windows 7. When I run the code I get this warning:
C:\Users\User\Anaconda3\lib\site-packages\cvxpy\problems\problem.py:614: RuntimeWarning: overflow encountered in long_scalars   if self.max_big_small_squared < bigsmall**2:
C:\Users\User\Anaconda3\lib\site-packages\cvxpy\problems\problem.py:615: RuntimeWarning: overflow encountered in long_scalars  self.max_big_small_squared = bigsmall**2
Does anyone know where could be the problem? If any other information on my code are needed, let me know.

I've run into this. big_small is a NumPy int32 (or maybe it's a NumPy int and I was on a 32 bit platform, I forget), and big_small**2 is larger than 2^31. The fix is to ensure that big_small is either a Python int or at least a NumPy int64.


APIDoc

Im really new to this all, i found this package, and as it says its ok suggestions, i will give one even if im not sure if it fits.
Could api-generator have some support for running https://github.com/mpociot/laravel-apidoc-generator ?
im with laravel 5.6, and starting on this, and im thinking of use this 2 packages to help me build some nice apis! :)

@JDias Currently we're not planning to invest much time into this package. But you can use it to generate API Controllers, then add your own comments on top of methods, and then generate Docs.

Thanks, that is my actual plan!
i was sharing cause maybe would be simple to add some "support" for it as guidance for newcomers like me. (i will probably start to envolve the generated files later, was just sharing an ideia) :)
Regards!


fix: Fixed MSI build version inconsistency

When I ran the gh action to build my app there's a version inconsistency in the artifact.
The build version is 0.3.0-1 but then somewhere the msi builder changes it to <IP_ADDRESS> and then when the gh action finishes the build, it looks for the file with the version 0.3.0-1 but it can't find it, because the file is under the name of <IP_ADDRESS>.
Running candle for "main.wxs"
     Running light to produce path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_<IP_ADDRESS>_x64_en-US.msi
    Bundling path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_<IP_ADDRESS>_x64_en-US.msi.zip
    Finished 1 bundle at:
+        path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_<IP_ADDRESS>_x64_en-US.msi
        path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_<IP_ADDRESS>_x64_en-US.msi.zip (updater)

    Finished 1 updater signature at:
        path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_<IP_ADDRESS>_x64_en-US.msi.zip.sig

Looking for artifacts in:
-path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_0.3.0-1_x64_en-US.msi
path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_0.3.0-1_x64_en-US.msi.zip
path\to\project\src-tauri\target\release\bundle\msi\Packager By Waypoint_0.3.0-1_x64_en-US.msi.zip.sig
path\to\project\src-tauri\target\release\bundle\nsis\Packager By Waypoint_0.3.0-1_x64-setup.exe
path\to\project\src-tauri\target\release\bundle\nsis\Packager By Waypoint_0.3.0-1_x64-setup.nsis.zip
path\to\project\src-tauri\target\release\bundle\nsis\Packager By Waypoint_0.3.0-1_x64-setup.nsis.zip.sig

Hi, thanks for contributing. A few things before we can merge this:

We normally require all commits to be signed, but it's not enforced in this repo yet.
versions can also look like 0.3.0+1 so please add that too while you're at it :)
please run pnpm build and commit the dist js files. without it your changes won't be applied
lastly, add a changefile similar to https://github.com/tauri-apps/tauri-action/blob/dev/.changes/fix-member-globs.md

Thanks again :)

Also, ignore the failed real world tests for now, that was my bad. If you pull the latest dev branch it should be fixed though.


Add new merge script

The new merge script has the following features:

Default behavior: Merge in tuned kernels for previously tuned sizes only if the efficiency has improved. This also removes unused kernels

e.g. python avoid-regressions.py  asm_full  incremental_logic_dir  output_dir

Old behavior: Merge in tuned kernels for previously tuned sizes regardless of improvements in efficiency

e.g. python avoid-regressions.py  asm_full  incremental_logic_dir  output_dir  true
Recommended usage: Use the first option always. Only use the 2nd option if you're working on a GPU with lower peak performance than another GPU with the same architecture, i.e. MI50 vs. MI60 tuning

@amdkila does the new merge script preserve leading dimension info in logic yaml? Because old script reduces 8-tuple problem key to 4-tuple upon merge.

@rosenrodt It doesn't, but I can change that if needed. From my understanding, kernel selection ignores leading dimensions. So that's why it's ok for the old merge script wiping out the leading dimensions. For that reason, I decided to intentionally do the same with the new script.

@amdkila Given the fact that LDs have good amount of impact on kernel selection, the Tensile client's behavior might change in the future. Especially given the Tensile's ability to tune for strided batched gemms (though with limited support). Erasing the strides/LDs info for now may be OK, but will probably come back and bite us in the future.

This PR should be good to go. Now there isn't a need to merge the base file into incremental logic, and all solutions are removed as expected


[BACKLOG-1965] Creating a NamedCluster with empty name corrupts metastore

@e-cuellar cherry-pick from master for review


Website redesign

[X] Replace Open Life Science by OLS
[X] Add facilitators in cohort syllabus
[x] Restructure team, community pages

[X] Rename "Community" page to "People"
[X] Make a "Community" page and add the team members
[x] Add roles

[X] Restructure partners and sponsors

[X] Split partners into supporters and partners
[X] Create a dedicated page for partners

[x] Restructure about and index page

[X] Expand role descriptions in the about page
[X] Move program description to the about page
[X] Add cohort table
[X] Remove team from the about page
[x] Redo and add Emmy's picture to index page
[x] Move the Cohort table to the index page
[x] Move everything starting "Projects" in the index page to about page

[X] Restructure navbar

[x] Create a "Policies" drop down menu
Move Code of Conduct to policy GitHub repo and link to it from the navbar (FOR ANOTHER PR)

[X] Add new page skeletons

clicked about, excited for the new page, no big problems!


CI should use node 14

@tylerbutler is this mostly done?  Looks like all the pipeline/github action already uses version 14.
Only the devcontainer still have 12 as the default, right?  Anything else missing?

@tylerbutler is this mostly done?  Looks like all the pipeline/github action already uses version 14.
Only the devcontainer still have 12 as the default, right?  Anything else missing?

Yeah, I think the pipelines are all done now.


Subcription

hello
I need some helps to implement subscription.
I try to find absinthe lib for flutter multiplatforms but I don't find anything.
Now, I'm trying to implement my need with gql-dart lib to do something like that:
void waitConfirmations(
    String address, {
    onResult,
    onError,
    onCancel,
    onStart,
    onAbort,
  }) {
    String host =
        Uri.parse(endpoint!).host + ':' + Uri.parse(endpoint!).port.toString();

    AbsintheSocket _socket =
        AbsintheSocket('ws://' + host + '/socket/websocket');

    final String operation =
        """subscription { transactionConfirmed(address: "$address") { nbConfirmations } }""";

    Observer _observer = Observer(
      onAbort: onAbort,
      onCancel: onCancel,
      onError: onError,
      onResult: onResult,
      onStart: onStart,
    );

    Notifier notifier =
        _socket.send(GqlRequest(operation: operation), 'notifierKey');
    notifier.observe(_observer);
  }

Could you confirm this is possible with Link ?
Thank you

just for info, here the method in js
waitConfirmations: function (address, endpoint, handler) {
     const host = new URL(endpoint).host
     const absintheSocket = withAbsintheSocket.create(
       new Socket(`ws://${host}/socket`)
     );

     const operation = `
       subscription {
         transactionConfirmed(address: "${address}") {
           nbConfirmations
         }
       }
       `
     const notifier = withAbsintheSocket.send(absintheSocket, { operation })

     return withAbsintheSocket.observe(absintheSocket, notifier, {
       onAbort: console.log("abort"),
       onError: function (err) {
         throw err
       },
       onStart: console.log("open"),
       onResult: function (result) {
         if (result.data.transactionConfirmed) {
           return handler(result.data.transactionConfirmed.nbConfirmations)
         }

         throw result
       }
     })
   }

Not sure if that is possible, have a look at this websocket lib that is used by gql_websocket_link https://github.com/gql-dart/gql/blob/master/links/gql_websocket_link/pubspec.yaml#L14

Thank you for help
I saw this but I don’t find how to use this to use subscriptions

Reading the docs for absinthe, it is a GraphQL server library and according to the docs it works with Apollo client.
So this lib should work as well, is there any specific error you are facing?

I have not specific error… I confess I don’t know how to write the code 😫

You can use the websocket link with Ferry client, have a look at the docs https://ferrygraphql.com/
Also we have  a Discord channel for support https://discord.gg/G3JGkBY
If there is a specific thing that is not working you can open an issue for it.


Refactor storage setup

With the new file upload implementation, we can simplify the storage configuration. Without pre-signed URLs and by passing everything through the API, we can simplify:

the Docker network setup for offline use
ECS instruction on open ports (no need for 9000): https://github.com/WorldBank-Transport/Rural-Road-Accessibility#setting-up-deployment
the analysisProcess environment variables (storagehost + port)

cc @danielfdsilva

@olafveerman This was refactored, right?


Better handling for when AddAWSMessageBus is invoked multiple times?

Describe the feature
When AddAWSMessageBus is invoked multiple times, previous IMessageConfiguration configurations are overwritten/lost. Specifically, the subscriber mappings.
https://github.com/awslabs/aws-dotnet-messaging/blob/main/src/AWS.Messaging/Configuration/MessageBusBuilder.cs#L311
Use Case
I'm attempting to register message handlers within various sub modules/assemblies, instead of needing to have the top most dependency responsible for all the registration.
Proposed Solution
Various ways this may be addressed...
Option 1: Merge in existing configuration (subscriber mappings) with new configuration on subsequent calls.
Option 2: A separate API for adding message handlers (separate from AddAWSMessageBus).
Option 3: Decide this is unsupported and make it more clear. Perhaps a runtime check to know if it has already been configured.
Other Information
No response
Acknowledgements

[X] I may be able to implement this feature request
[X] This feature might incur a breaking change

AWS.Messaging (or related) package versions
AWS.Messaging 0.9.1
Targeted .NET Platform
.NET 8
Operating System and version
AmazonLinux

Needs review with the team.

Hi @brendonparker, we have discussed this issue internally and we believe that Option 1 is the best option. We appreciate it if you could submit a PR that would implement Option 1 as that will help us prioritize this issue, review it and get it merged in. Thanks in advance!

There are a few different ways of accomplishing Option 1.

Store MessageConfiguration in a static variable, so it can be re-used across calls to AddAWSMessageBus.

I've created a branch/PR to this end as it is the simplest approach.

Move the MessageConfiguration down into some intermediate state, and then combine it at runtime (when resolving IMessageConfiguration using the pattern that @ashishdhingra outlined above by resolving all registrations and combining them.
Total rehaul of MessageConfiguration to contruct based purely off of what is registered in the service collection. Hopefully I'm articulating that well enough. For example, the code would .AddSingleton<PublisherMapping> multiple times, rather than adding it to the in memory MessageConfiguration. Then at runtime resolve all registered PublisherMappings. So use the DI Container as the pool of registrations, rather than adding them to a list within the MessageConfiguration


Distinguish "real updates" from "cleaning up duplicates"

Low priority because duplicate (but good) records are extremely rare.

Closed due to the lack of any real impact.


VW MQB: Volkswagen T-Roc Mk1

Volkswagen T-Roc Mk1
Covers all worldwide versions of the T-Roc sub-compact crossover SUV, including the T-Roc R and T-Roc Cabriolet. Averaged some mild wheelbase and mass variance between the versions for simplicity.

[x] added to CARS
[x] added to RELEASES
[x] test route added to test_models.py
[x] route with openpilot: 0cd0b7f7e31a3853|2021-11-18--00-38-32

Thanks AGAIN to community member Saber422!

The test route is 12 segments long, but the segment 1 rlogs are MIA, athena can't see them at all. If we can make use of this test route, great, if not, we can go back to the user.

All logs are completely uploaded. (0cd0b7f7e31a3853|2021-11-18--00-38-32)
Thank you!


Do not clear fault leds during warm reboot

This commit has some changes in clear-all-fault-leds.sh script
to work in such a way that the script exits successfully without
resetting any fault leds whenever there is a graceful/force
warm reboot request. As during the warm reboot the chassis power
isn't turned off and so the data about fault leds should not be reset.
Test:
Tested on the following cases.

During a Graceful warm reboot request => Expected not to reset any
fault leds and exit successfully.
During a Force warm reboot request => Expected not to reset any fault
leds and exit successfully.
During a reset-reload => Expected not to reset any fault leds.
During a host hard reboot => Expected to reset fault leds and exit
successfully.

The test runs as expected for all the mentioned 4 cases.
Journal log:
May 09 09:47:46 ever10bmc systemd[1]: Starting Clears all fault LED to true and remove critical associations...
May 09 09:47:46 ever10bmc systemd[1]: Starting Set the Asserted property of all the LED groups to false...
May 09 09:47:46 ever10bmc obmc-clear-all-fault-leds-and-remove-crit-association[1457]: Inside clear-all-faults-led.sh file
May 09 09:47:46 ever10bmc systemd[1]: Starting Clear the Volatile PNOR partitions in host0 if Enabled...
May 09 09:47:46 ever10bmc systemd[1]: Starting Updates symlinks for active PNOR version...
May 09 09:47:46 ever10bmc systemd[1]: Starting CFAM reset...
May 09 09:47:46 ever10bmc systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
May 09 09:47:46 ever10bmc systemd[1]: Stopped Stop instructions for host0.
May 09 09:47:46 ever10bmc systemd[1]: Stopped target Stop Host0 (Pre).
May 09 09:47:46 ever10bmc obmc-clear-all-fault-leds-and-remove-crit-association[1457]: Current chassis power state is ,
"xyz.openbmc_project.State.Chassis.PowerState.On". EXIT clear-all-fault-leds.sh SCRIPT SUCCESSFULLY WITHOUT DOING ANY FAULT LED RESET.
May 09 09:47:46 ever10bmc systemd[1]: op-reset-host-clear.service: Deactivated successfully.
May 09 09:47:48 ever10bmc vpd-manager[669]: Setting GPIO: presence-cable-card11 to 1
May 09 09:47:48 ever10bmc systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
May 09 09:47:48 ever10bmc systemd[1]: Finished Clears all fault LED to true and remove critical associations.
May 09 09:47:48 ever10bmc kernel: at24 26-0051: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
Signed-off-by: Priyanga Ramasamy<EMAIL_ADDRESS>

Also fix the CI issues.

Please ask Reed to pull that commit from Patrick in so that he can better track it with upstream.
The commit from Patrick is merged by Reed and I have rebased this PR on the latest 1020.


Added functionality to close palette when clicking outside

Palette closes when clicked outside now

This can be done for all activities, what do you say @llaske ?

Hmmm. I was wrong, the "standard" behavior for the Sugar UI palette is to stay open until closed or until another one is open.
So I can't accept the PR.

I understand, thanks for mentioning, I'll close this PR.


Add parameters for Shared Drive uploads

Adds ability to upload data to Shared Drives correctly

I'm not super familiar with the API options but this looks good to me


Add support to import predeclared langlibs manually for testable packages

Purpose

$Subject.

Fixes #25990
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[x] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@chiranSachintha, as discussed offline let's check if we can unify the behaviour of predeclared imports and the user having to specify the imports in both the source and the tests.

Changed logic to define predeclared imports compilation unit wise.


Problem with connect to Janus server

I installed Ubuntu 20 on VMWare and got the Janus server from https://github.com/meetecho/janus-gateway and installed it with all the required dependencies. I have run the client code with Visual Studio 2019 and Qt 5.15.
I ran the Janus server program from the following path:
/opt/janus/bin/janus
For communicating with the Janus server, enter the server address is:
ws://<IP_ADDRESS>: 8088/ws
After hitting the Connect button in the Janus server terminal message
01
"[ERR] [transports / janus_http.c: janus_http_handler: 1436] Invalid url/ws"
Is displayed and the connection is not established.

I installed Ubuntu 20 on VMWare and got the Janus server from https://github.com/meetecho/janus-gateway and installed it with all the required dependencies. I have run the client code with Visual Studio 2019 and Qt 5.15. I ran the Janus server program from the following path: /opt/janus/bin/janus For communicating with the Janus server, enter the server address is: ws://<IP_ADDRESS>: 8088/ws After hitting the Connect button in the Janus server terminal message 01 "[ERR] [transports / janus_http.c: janus_http_handler: 1436] Invalid url/ws" Is displayed and the connection is not established.

I used the following address to set up the server:
https://www.codetd.com/en/article/1302334
And the connection problem with the server was solved.


Download ACF Pro release using Composer

Downloading ACF Pro release using directly via HTTP is obsolete (https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/). This PR fixes this by using Composer to download ACF Pro release.

Could you verify this method by downloading 6.2.7 again?

Verified, the results are identical.

Then it is release-time ✈

We're only interested in the stubs for development/phpstan/CI pipelines, but after 27fa6e4 the stubs package have hard requirement of wpengine/advanced-custom-fields-pro package too.
  Problem 1
    - Root composer.json requires php-stubs/acf-pro-stubs ^6.3 -> satisfiable by php-stubs/acf-pro-stubs[v6.3.0, ..., v6.3.8].
    - php-stubs/acf-pro-stubs[v6.3.0, ..., v6.3.8] require wpengine/advanced-custom-fields-pro 6.3.8 -> could not be found in any version, there may be a typo in the package name.

Thanks for the heads up! Functional releases coming ASAP.

Recent releases are outside the default branch ⚠

@szepeviktor @todeveni Please check if the latest release works for you https://github.com/php-stubs/acf-pro-stubs/releases/tag/v6.3.10

@juhojama Red ALERT: published auth.json
🚨

@szepeviktor @todeveni Please check if the latest release works for you https://github.com/php-stubs/acf-pro-stubs/releases/tag/v6.3.10

Bumping acf-pro-stubs in composer.json from ^6.2 to ^6.3 and updating works now. Thanks.
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 4 updates, 0 removals
  - Upgrading php-stubs/acf-pro-stubs (v6.2.7 => v6.3.10)


Implemented a test function

Add the package only as devDependencies for execute .ts file with one command.
Create the command on package.json test that execute the test.ts file in the src folder

LGTM @erikwski, thanks for this!

@pietrodev07 i'm looking for implement the possibility of log infinite parameter like the console.log.
If you get in touch with me you can find me on Telegram at @Erik247

@pietrodev07 i'm looking for implement the possibility of log infinite parameter like the console.log.
If you want to get in touch with me you can find me on Telegram at @Erik247

Good idea!


Could not merge query string and form data in PUT/PATCH request

If we have the PUT request just like
http://localhost:5000/api/products/5D18B427-FF94-4D34-9C5A-D5312E407EB5

and form-data
{
	"name": "sample product 123",
	"desc": "This is sample project 12345",
	"price": "1200",
	"imageUrl": "http://samplepicture.img"
}

We would like to have a JSON object in the downstream service like
{
	"id": "5D18B427-FF94-4D34-9C5A-D5312E407EB5",
	"name": "sample product 123",
	"desc": "This is sample project 12345",
	"price": "1200",
	"imageUrl": "http://samplepicture.img"
}

Then, we always get the object with id is null
Solution: we would like to merge the query string and form data in PUT/PATCH requests
And, also Delete cannot work well becasue it always wants us to put into form-data. We would like to pass like DELETE http://localhost:5000/api/products/5D18B427-FF94-4D34-9C5A-D5312E407EB5
#ref https://github.com/vietnam-devs/coolstore-microservices/issues/48

Fixed with 0.5.0


defaultLocale and browser local setting those are not working.

https://stackblitz.com/edit/nuxt-starter-rstvii?file=app.vue
Look, I set defaultLocale as ko
But fromNow doesn't return time with ko locale.
And it also doesn't reflect browser locale setting.

https://stackblitz.com/edit/nuxt-starter-rstvii?file=app.vue
Look, I set defaultLocale as ko But fromNow doesn't return time with ko locale.
And it also doesn't reflect browser locale setting.

You are only setting the locale for that one line in the component, you need to set it in your nuxt config if it you want it global, or have a composable return it w/ that locale

@acidjazz
Thanks for quick response!
I am not sure what I unserstand correctly.

"you need to set it in your nuxt config if it you want it global"
-> I set it as "ko" in nuxt.config.ts , you can check it in the link. So I expect
This codeuseDayjs()('2023-01-01').fromNow() returns "10 달 전"
But it returns 10 months ago. It isn't ko locale.. Isn't it?

"have a composable return it w/ that locale"
I am not sure how I can make code as you said.

@quroom i did not see you set it up in your nuxt config, looking into this now..

fixed in https://github.com/fumeapp/dayjs/releases/tag/v2.1.7

@acidjazz
  dayjs: {
    locales: ['ko', 'en'],
    plugins: ['relativeTime', 'utc', 'timezone'],
    defaultLocale: 'ko',
    defaultTimezone: 'America/New_York',
  },

I added this code in nuxt.config.ts
defaultLocale: 'ko',

Isn't it for setting defaultLocale?
If it isn't, could you make it correct?


Generate CSV for 3.6.0 release

Generated CSV for 3.6.0
Updated CSV manually with necessary fields after comparing it with 3.5.0
Makefile: Added install and uninstall targets to test the CSV locally through the command line
Tested the changes locally on test cluster by deploying the 3.6.0 CSV

Still need to determine if / when we can push the new csv - 3.6.0 to quay - with the use of a dev channel. Let's touch base on this later today.


[Feature Request] Ability to set security on items within Azure DevOps (pipelines, variable groups, etc)

It would be a huge help if there was a way to manage security on specific item types using the cli extensions.
For example, when I create a variable group it would be great if I could add/remove groups to that group.  We do this to allow teams to manage variable groups that are specific to their part of the solution

@ravensorb - As of now, you can create a set of variables within a single variable group. Could you tell me where this is failing for your requirement? Can't you create multiple variable groups for the various teams and then associate just the requisite variables in the corresponding variable groups to any pipeline run?


Way to disable the right-click and also panning abilities.

Hi, first, thanks for this amazing mapping capability.    The app allows the user to click on a specific building (a marker) and then the app displays data about the building.  I want to be able to disable the panning capability as well as the right-click, as there is no functionality in the app to add new markers, but I cannot disable this in the map.  Also, since the map is for information only, I would like to disable the panning feature.  Thanks.

not unreasonable suggestions. I have added the ability to specify these via the commands. The example below will turn on and off panning, zooming, and the right click
[{"id":"b4f06c7e.25303","type":"inject","z":"d511095d.512808","name":"","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"hide":false,"x":110,"y":1460,"wires":[["420581ae.b91da"]]},{"id":"420581ae.b91da","type":"function","z":"d511095d.512808","name":"Lock map","func":"msg = { \n    payload: {\n        command: {\n            panlock: msg.payload, \n            zoomlock: msg.payload,\n            hiderightclick: msg.payload\n        }\n    }\n};\nreturn msg;","outputs":1,"noerr":0,"x":280,"y":1460,"wires":[["9bea779a.ac91a8"]]},{"id":"563ffb23.e1c7a4","type":"inject","z":"d511095d.512808","name":"","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"hide":false,"x":110,"y":1500,"wires":[["420581ae.b91da"]]}]


python311Packages.spylls: init at 0.1.5

Description of changes
Pure Python spell-checker, (almost) full port of Hunspell
https://github.com/zverok/spylls
https://github.com/zverok/spylls/blob/master/CHANGELOG.rst

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/107

@sikmir @Aleksanaa @natsukium


ARC: logging: Print exception info independent of CONFIG_LOG

Some applications turn logging off. It makes impossible to get information about exceptions if it occures.
In this PR exception dump is printed anyway independent on CONFIG_LOG. Also ARC_EXCEPTION_DEBUG added to default board configs in addition to nsim

It looks like that we need to switch to ARC_EXEPTION_DUMP here as well: https://github.com/zephyrproject-rtos/zephyr/blob/main/arch/arc/core/fault.c#L107C3-L338

I'm not sure about this. In this RP we turn on only notification about exception occurs. Replacing LOG_ERR to ARC_EXEPTION_DUMP at this part will cause to generate a lot of extra logs. If we need such logs, we should turn on LOG explicitly.

Needs rebase


[DevTools Docs Feedback]fody&webview2

Hello, when I use fody to package, I cannot package the webview2-related dll files into a single executable file, and after I package it, the webview2 program cannot be used in the program, and there is no error report directly.
When i double-clicking the event My program cannot call webview2.
I have tried to embed the necessary program directly into the program and then package it, but the result is that an error is reported directly.
I have read a lot of relevant information, but there is no corresponding solution

does anyone have an answer for me?

Thank you for reaching out. This question is specific to the WebView2 product, not its documentation. Therefore, could you please open a new issue for this over on the dedicated WebView2Feedback repository?
Here is the link: https://github.com/MicrosoftEdge/WebView2Feedback/issues/new
Thanks for your understanding.


Ensure pandas DataFrame column names are treated as strings in type error message

Closes https://github.com/dmlc/xgboost/issues/4480
If the DataFrame column names aren't strings, constructing the error message here will yield an error:
File "/databricks/python/lib/python3.6/site-packages/shap/explainers/tree.py", line 172, in shap_values
    X = xgboost.DMatrix(X)
  File "/databricks/python/lib/python3.6/site-packages/xgboost/core.py", line 384, in __init__
    feature_types)
  File "/databricks/python/lib/python3.6/site-packages/xgboost/core.py", line 241, in _maybe_pandas_data
    raise ValueError(msg + ', '.join(bad_fields))
TypeError: sequence item 0: expected str instance, int found

This simply ensures it's a string.

Thanks!


Opentasks/dmfs crashes when termux-app/termux 0.31 is installed

The chrash occures when trying to edit a task. With version 0.30 everything is fine. There is also an error report at the termux-app/termux project.

Here is the link to termux.
https://github.com/termux/termux-app/issues/68

Please give a more detailed error description. What exactly do you do to trigger the crash?
How does it crash? Can you provide any stack trace or log?

Hello
The termux developer has provided a new version already, but it is not online in the fdroid store for now. I respond to you after i have tried out the new version.
The problem occurs right after installing termux. After that when i am trying to edit a task entry opentasks crashes.
Sadly i cannot provide you any logs.
Thanks in advance

Hello
The problem is gone with version 0.32 of Termux.
Happy easter!!


Option to designate format in the request

According to the imgix API documentation, you can get the exif data by utilizing the fm modifier. Unfortunately, that doesn't seem to be supported within imgix-rails. Adding the fm option would be helpful.

Here's what I've done to use fm to grab webp-format images:
ix_image_url(self.image.key, IMAGE_SIZES_IX[size.to_sym]) + '&fm=webp'
In mimi_types.rb:
IMAGE_SIZES_IX = {xl: { w: 1000, h: 1000 }, large: { w: 500, h: 500 }

To add to what @abrambailey said, you can also pass in fm directly as a parameter:
<%= ix_image_url('unsplash/bridge.jpg', {fm:'json'}) %>

Using the ix_image_url function will generate a URL whose response body would contain the exif data. This would be preferred over using ix_image_tag which would wrap the same URL in an <img> tag.
I'm going to close this issue as it is fairly old, but feel free to comment back if any further questions arise.


Add a URL to 'You Might Not Need Redux'

You Might Not Need Redux
This article sufficiently states why you might not need Redux from the creator itself. Adding this to the documentation will help those people who are not able to decide whether they need Redux or not.
Not sure if it is the correct place for the link, please suggest.

It's done. Looks like [force-push] caused some trouble. (https://github.com/reactjs/redux/pull/1995/files/d4948a4d7550fce27dd973f67ca5cede3f141d03)
The files have been changed.

Thanks!


Nest camera video corruption only when go2rtc and camera on same network

Video corruption is occurring on all of my Nest camera feeds but only if the system running go2rtc is on the same network as the Nest cameras. Issue occurs on multiple hosts running go2rtc (Mac laptop, 2 x RPis with Ubuntu and Linux VM) and with all of the Nest camera feeds.
The video corruption issue goes away if running go2rtc on a machine that is not on the same network as the cameras. Have tested with a GCP VM and my laptop. Debug logs from go2rtc are identical in both passing and failing case. No issues with RTSP streams from standard IP cameras and no issues with displaying the camera feeds through Google Home app when on the local network.
Fails every time, happy to collect additional logs or provide remote access to debug. Fails on v1.8.5 and master branch.
log:
  level: debug
  streams: debug
  webrtc: debug

webrtc:
  listen: ":8555"

streams:
nest-doorbell:
    - nest:?<redacted>

Update I'm able to reproduce the issue using: ffplay -fflags nobuffer -flags low_delay -rtsp_transport tcp "rtsp://localhost:8554/nest-backyard"
Enabling the reorder queue makes the issue go away: ffplay  -flags low_delay -rtsp_transport tcp -reorder_queue_size 10 "rtsp://localhost:8554/nest-backyard"
Is there a similar setting that can be used for the RTC streams?

@peterguy04 unfortunately we decided to focus on the commercial space and abandoned working with Nest cameras for the foreseable future. I'm happy to test potential fixes though since it's easy to reproduce the issue on our end.

Unfortunately I don't use Nest and can't fix this issue

@AlexxIT  i arnt sure if it helps or even makes any sense  but I've figured out that this is only happening when frigate is running. This can be on a different device anywhere on the network or on the same device as each other. They dont even have to be linked in the frigate config
i am testing now with frigate and the separate go2rtc container and if i stop frigate, the streams are good, start frigate and its bad.
@clasoncj were you running frigate by any chance aswell ?

I was able to reproduce running the go2rtc binary natively on the host (not
even using docker), our use case didn't involve Frigate. No other video
sinks were active when the issue was reproduced on our machines.
My hypothesis is the sink is reading from the queue before the data is
ready which is why setting the reorder_queue_buffer fixed the issue. I
wouldn't be surprised if system load impacting other timing could cause
different behavior.
I also had the idea to try and request a new keyframe but unfortunately
abandoned our efforts before I was able to code a patch to test.
On Thu, Apr 25, 2024 at 12:15 PM peterguy04 @.***>
wrote:

@AlexxIT https://github.com/AlexxIT i arnt sure if it helps or even
makes any sense but I've figured out that this is only happening when
frigate is running. This can be on a different device anywhere on the
network or on the same device as each other. They dont even have to be
linked in the frigate config
i am testing now with frigate and the separate go2rtc container and if i
stop frigate, the streams are good, start frigate and its bad.
@clasoncj https://github.com/clasoncj were you running frigate by any
chance aswell ?
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/937#issuecomment-2077779865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWGZCHTRPTVL7QTAGQAXWDY7E24JAVCNFSM6AAAAABDC3YXLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXG43TSOBWGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Unfortunately I don't use Nest and can't fix this issue

@AlexxIT I can give you wireguard access to a RPi4 host running Ubuntu configured to use one of my Nest cameras if you're interested in debugging. Issue shows up consistently.

I deleted my original post because after further testing ,I still had issues, the image did appear cleaner but did freeze alot which also caused a few artifacts.

Remote debugging of such problems is very time consuming. Because it depends on the network environment only.

I can confirm the same behavior. Observed wither via direct Nest integration or via Home Assistant -> Google SDM integration