CSS improvements

Don't escape HTML when decoding (fixes #44)
Don't load remote stylesheets (aligns with upstream MJML functionality)
Upgrade to css-inline v0.11.0 (and pin to v0.11.x to prevent any more API issues)

@FelixSchwarz I'm trying to upgrade to css-inline v0.11.0 to take advantage of performance improvements added in v0.10.x, but it requires using the keep_link_tags and keep_style_tags arguments, which older versions of css-inline don't support. 0.8.3 is the latest version that supports Python 3.6, so we're getting "unexpected keyword argument" errors when trying to use it in the 3.6 tests. Not sure how you'd like to handle this.

Btw, I’d be curious how much the update improves performance in your scenario - I have very few benchmarks so it would be cool to learn about real life effect of all that performance changes :)

@Stranger6667 Just to consider all options, how feasible would it be to add back support for Python v3.6 to css-inline?

@caseyjhol Supporting Python 3.6 requires downgrading pyo3 to 0.15.2 which does not support Python 3.11 and the number of bugfixes between the current pyo3 version and that one is quite big. It does not feel reasonable for css-inline to downgrade that much, but I guess, generally, pyo3==0.15.2 should be compatible with the current binding's implementation. I.e. it could be a fork / different branch that could use older pyo3 and released under a different name on PyPI (e.g. css-inline-py36) and used as a conditional dependency for Python 3.6 only.

0.8.3 is the latest version that supports Python 3.6, so we're getting "unexpected keyword argument" errors when trying to use it in the 3.6 tests. Not sure how you'd like to handle this.

I think we can make a point that css inlining is only support for Python >= 3.7. We are still using mjml in production with Python 3.6 - probably until RHEL 7 support ends and I can justify spending on mjml-python more easily if we can use mjml in our infrastructure.
However we don't need css inlining for the Python 3.6 deployment, so this PR seems like a good reason to raise that requirement. I would release the next version as 0.10.0 as this is kind of a breaking change for Python 3.6 users but everyone needs to upgrade at some point.

That makes sense to me (to lock CSS support to Python 3.7). If we get someone requesting Python 3.6 CSS inlining support, we can reconsider a different approach.
If we want to be really granular about it, we could release my CSS fixes in v0.9.2 (so Python 3.6 users could still use that version for CSS support). And then we could follow-up with a css-inline upgrade in v0.10.0.

@FelixSchwarz Any thoughts here? These are the last items preventing from moving forward with a prototype for some users. Thanks!

Your branch contains some "wip-like" commits. I tried to extract the meaningful changes but I'm always getting some test failures locally. May I ask you to rebase/squash your commits on top of the latest main? I don't have any objections to code, so this just about getting your changes to apply (and a cleaned-up commit history).

Sure - can clean those up now.

Thank you. Are there more features you would like to add or should we just release version 0.10?


Added ValFadeev/rundeck-nomad-plugin to README.md

This one is on the rundeck plugin list:
Thanks!

@jippi would you mind merging this one? Please let me know in case of any concerns. Thanks! :)

nice! extremely useful tool - could use that internally too - thank you!


[5.5] Set up loop variable correctly on all Traversable objects

The $loop variable within Blade's @foreach is not filled correctly if the object given implements \Traversable but not \Countable. The reason is that the stack size is not determined properly. This leads to unexpected behaviour using i.e. $loop->last.
This commit fixes the $loop variable so it works correctly with all \Traversable stacks (like \DatePeriod). It won't break any existing features as it just extends the functionality.

We don't merge nested ternarys.


Concept Creation for Multi-Wallet Provider Integration and BYOW Connection in SSI Issuance Flow

This feature was created by the network service committee to ensure that the scope is planned for 24.08.
Description:
The purpose of this ticket is to conceptualize and evaluate the necessary modifications to the Self-Sovereign Identity (SSI) issuance flow to facilitate the support of multiple wallet providers and the option for users to bring their own wallet (BYOW). The focus is on maintaining a customer-centric design throughout the process, ensuring that the user experience is intuitive and efficient. This includes the creation of a customer journey map that details the user's interaction with the SSI system and the integration of wallet-to-wallet communication, which is an essential component of the credential issuance flow.
Possible Impacted Products:

portal
registration
OSP/CoreServiceProvider
issuance component
gaia-x clearinghouse (?)
EDC

Acceptance Criteria:

Customer Journey Map Development:

Construct a detailed customer journey map that captures the user experience with the current SSI issuance process, highlighting interactions with wallet providers.
Identify points within the journey where users can choose different wallet providers or connect their own wallet.

Conceptual Framework:

Design a conceptual framework that enables users to select from multiple wallet providers or connect their own wallet during the SSI issuance process.
The framework must prioritize ease of use and a clear, straightforward selection process for the user.

Technical Assessment:

Evaluate the existing technical infrastructure to understand the implications of integrating multiple wallet providers and BYOW capabilities.
Identify technical requirements and any potential challenges that may arise from wallet-to-wallet communication.

Impact Analysis:

Analyze how the new multi-wallet provider and BYOW features will affect existing systems and user processes.
Formulate a change management strategy to address any impacts identified.

Documentation:

Produce comprehensive documentation of the new concept, including visual aids like diagrams and flowcharts, and detailed descriptions of user interfaces.
Documentation should be clear and accessible to stakeholders with varying levels of technical expertise.

Regulatory Compliance and Security Assessment:

Verify that the new concept adheres to applicable regulations and industry standards.
Perform a security assessment to ensure that the integration of multiple wallet providers and BYOW does not compromise security.

Deliverables:

Customer Journey Map
Conceptual Framework Documentation
Technical Assessment Report
Impact Analysis Document
Comprehensive Documentation Package
Compliance and Security Assessment Report

Timeline:

A detailed timeline will be established following the initial concept and assessment phase.

Resources Required:

Access to existing SSI issuance flow systems and documentation
User data for customer journey mapping
....
....

Risks and Mitigations:

Risk: Integration of multiple wallet providers and BYOW may introduce complexity and user confusion.

Mitigation: Focus on a user-centric design approach and conduct extensive user testing to refine the interface and flow.

Risk: Potential security vulnerabilities with wallet-to-wallet communication.

Mitigation: Implement robust security protocols and conduct thorough security assessments.

Additional Notes:

The design process should be iterative, with continuous user feedback shaping the evolution of the concept.
Collaboration with UX/UI designers is essential to ensure the interface and user interactions are optimized for a positive user experience.
Regular updates and review sessions with stakeholders will be critical to maintain alignment and transparency.

@jjeroch : Please add label "ssi" as soon as it is created as it is also relevant for SSI Expert group

Hello @jjeroch , @jjeroch
Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

[ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
[ ] Please check whether the status (backlog, work in progress ...) is set correctly
[ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
[ ] Please comment on the current status of the feature
[ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much.
Stephan


Autocomlete doesn't work

Hello. I don't understand why autocompletion doesn't work.
Project based on Yii2 php-framework.
php:
php -v
PHP 7.1.0 (cli) (built: Dec  2 2016 11:32:42) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.1.0-dev, Copyright (c) 1998-2016 Zend Technologies

VS Code:
1.11.2 (1.11.2)

PHP IntelliSense:
1.1.5

No errors in developer console (trimmed):

No errors in VS Code output:
[Info  - 11:49:26 AM] 2240 files total
[Info  - 11:49:26 AM] Indexing project for definitions and static references
Parsing file: ...
[Info  - 11:49:29 AM] Indexing project for dynamic references
Parsing file: ...
[Info  - 11:49:32 AM] 23 Packages
[Info  - 11:49:32 AM] Restored baibaratsky/php-mailgun:1.2.0 from cache
[Info  - 11:49:32 AM] Restored cebe/markdown:1.1.0 from cache
[Info  - 11:49:32 AM] Restored ezyang/htmlpurifier:4.6.0 from cache
[Info  - 11:49:32 AM] Restored fzaninotto/faker:1.5.0 from cache
[Info  - 11:49:32 AM] Restored guzzlehttp/guzzle:6.0.2 from cache
[Info  - 11:49:32 AM] Restored guzzlehttp/promises:1.0.1 from cache
[Info  - 11:49:32 AM] Restored guzzlehttp/psr7:1.1.0 from cache
[Info  - 11:49:32 AM] Restored kotchuprik/yii2-fotorama-widget:1.0 from cache
[Info  - 11:49:32 AM] Restored phpspec/php-diff:1.0.2 from cache
[Info  - 11:49:32 AM] Restored psr/http-message:1.0 from cache
[Info  - 11:49:32 AM] Restored swiftmailer/swiftmailer:5.4.1 from cache
[Info  - 11:49:32 AM] Restored twig/twig:1.18.2 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2:2.0.5 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-bootstrap:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-codeception:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-composer:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-debug:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-faker:2.0.3 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-gii:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-jui:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-redis:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-swiftmailer:2.0.4 from cache
[Info  - 11:49:32 AM] Restored yiisoft/yii2-twig:2.0.4 from cache
[Info  - 11:49:32 AM] All 2240 PHP files parsed in 6 seconds. 158 MiB allocated.

"Go to Definition" works fine.
"Hover" works fine.
"Format code" works fine.
"Find all symbols" works fine.
"Find all References" works fine.
"Workspace symbol search" works fine.
PHP extesnsions:
brew search php71
homebrew/php/php71 ✔           homebrew/php/php71-grpc        homebrew/php/php71-msgpack     homebrew/php/php71-stats
homebrew/php/php71-amqp        homebrew/php/php71-hprose      homebrew/php/php71-mustache    homebrew/php/php71-swoole
homebrew/php/php71-apcu        homebrew/php/php71-igbinary    homebrew/php/php71-oauth       homebrew/php/php71-tidy
homebrew/php/php71-apcu-bc     homebrew/php/php71-imagick     homebrew/php/php71-opcache     homebrew/php/php71-timecop
homebrew/php/php71-ast         homebrew/php/php71-intl ✔      homebrew/php/php71-pcntl       homebrew/php/php71-timezonedb
homebrew/php/php71-blitz       homebrew/php/php71-libsodium   homebrew/php/php71-pdo-dblib   homebrew/php/php71-uuid
homebrew/php/php71-couchbase   homebrew/php/php71-lua         homebrew/php/php71-pdo-pgsql   homebrew/php/php71-uv
homebrew/php/php71-ds          homebrew/php/php71-lz4         homebrew/php/php71-phalcon     homebrew/php/php71-v8js
homebrew/php/php71-ev          homebrew/php/php71-lzf         homebrew/php/php71-pspell      homebrew/php/php71-xdebug
homebrew/php/php71-event       homebrew/php/php71-mailparse   homebrew/php/php71-rdkafka     homebrew/php/php71-xxtea
homebrew/php/php71-gearman     homebrew/php/php71-maxminddb   homebrew/php/php71-redis       homebrew/php/php71-yac
homebrew/php/php71-geoip       homebrew/php/php71-mcrypt ✔    homebrew/php/php71-ref         homebrew/php/php71-yaml
homebrew/php/php71-geos        homebrew/php/php71-mecab       homebrew/php/php71-snmp
homebrew/php/php71-gmagick     homebrew/php/php71-memcached   homebrew/php/php71-solr
homebrew/php/php71-gmp         homebrew/php/php71-mongodb     homebrew/php/php71-ssh2

Is the code inside a namespace?

Yes it is

Does it still happen with the latest version? Should be fixed

for all vendor packages i see warnings:
Could not compute cache key for PACKAGE_NAME
Log:
php-language-server.log.zip

@sluchznak does autocompletion work

autocompletion doesn't work

I have the same error in neovim
[Warning] Could not compute cache key for psr/cache

Same here. For me, nothing (completion, go to, hover ...) actually works. And no logs/error in consoles.


080223 cm

Codecov Report

Merging #316 (9688e1e) into develop (c649a95) will decrease coverage by 0.22%.
 Consider uploading reports for the commit 223daae to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #316      +/-   ##
===========================================
- Coverage    52.84%   52.63%   -0.22%
===========================================
  Files           12       12
  Lines         2373     2470      +97
===========================================
+ Hits          1254     1300      +46
- Misses        1119     1170      +51

Files Changed
Coverage Δ

R/Figures.R
0.00% <0.00%> (ø)

R/ResultFlagsDependent.R
40.20% <0.00%> (-12.09%)
:arrow_down:

R/Tables.R
74.46% <ø> (ø)

R/Utilities.R
86.12% <ø> (+1.73%)
:arrow_up:

R/GenerateRefTables.R
84.61% <86.04%> (+0.26%)
:arrow_up:

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


I have tried to research everything for like 3 days and I was still only able to run jvm with the multiplatform gradle config please help

Hey, can you share the gradle file you're using? I'll also add a few examples to show how to do js/jvm/multiplatform setups.

Hey, can you share the gradle file you're using? I'll also add a few examples to show how to do js/jvm/multiplatform setups.

plugins {
    kotlin("multiplatform") version "1.9.0"
    application
}

group = "de.xyndra"
version = "1.0.0"

repositories {
    mavenCentral()
    maven {
        url = uri("https://maven.pkg.jetbrains.space/public/p/compose/dev")
    }
}

kotlin {

    jvm {
        withJava()
        compilations.all {
            kotlinOptions {
                jvmTarget = "17"
            }
        }
    }

    js {
        browser()
    }

    val doodleVersion = "0.9.2" // <--- Latest Doodle version

    sourceSets {
        val commonMain by getting {
            dependencies {
                implementation ("io.nacular.doodle:core:$doodleVersion")
                implementation ("io.nacular.doodle:controls:$doodleVersion" )
            }
        }

        val jsMain by getting {
            dependencies {
                implementation(kotlin("stdlib-js"))
                implementation ("io.nacular.doodle:browser:$doodleVersion")
            }
        }

        val jvmMain by getting {
            dependencies {
                val osName = System.getProperty("os.name")
                val targetOs = when {
                    osName == "Mac OS X"       -> "macos"
                    osName.startsWith("Win"  ) -> "windows"
                    osName.startsWith("Linux") -> "linux"
                    else                       -> error("Unsupported OS: $osName")
                }

                val osArch = System.getProperty("os.arch")
                val targetArch = when (osArch) {
                    "x86_64", "amd64" -> "x64"
                    "aarch64"         -> "arm64"
                    else              -> error("Unsupported arch: $osArch")
                }

                val target = "$targetOs-$targetArch"

                implementation ("io.nacular.doodle:desktop-jvm-$target:$doodleVersion") // Desktop apps are tied to specific platforms
            }
        }
    }
}

application {
    mainClass.set("de.xyndra.application.LauncherKt")
}

@pusolito

Thanks for sharing. I'll take a look.

The issue is you're missing the following in your js block:
    js {
        browser()
        binaries.executable() // <--------------
    }

I had to change the multiplatform version to 1.9.10 as well but now it seems to compile, however I'm still working on implementing it


Test Issue for using GitHub

This is submission of a test issue in GitHub.  Does GitHub allow attachment of documents?

You can attach a picture or a link:
https://help.github.com/articles/issue-attachments/

You can upload a picture or attach a link: https://help.github.com/articles/issue-attachments/
From: ericrcaz<EMAIL_ADDRESS>Sent: February 4, 2015 3:47 PM
To: Wireless-Innovation-Forum/Transceiver-Next
Subject: [Transceiver-Next] Test Issue for using GitHub (#1)
This is submission of a test issue in GitHub. Does GitHub allow attachment of documents?
—
Reply to this email directly or view it on GitHub https://github.com/Wireless-Innovation-Forum/Transceiver-Next/issues/1 .  https://github.com/notifications/beacon/ABia24ZVhIxWWHcCEkm3zeOJaXhpAX_Hks5noqbYgaJpZM4Db6QZ.gif

Note that issues can be opened and closed without intervention by the work group. I am not sure if this can be fixed

Yes, that could be a problem, I may have been able to close since I was the initiator of the issue,

And I can reopen because I am an admin
From: ericrcaz<EMAIL_ADDRESS>Sent: February 4, 2015 4:12 PM
To: Wireless-Innovation-Forum/Transceiver-Next
Cc: LeePucker
Subject: Re: [Transceiver-Next] Test Issue for using GitHub (#1)
Yes, that could be a problem, I may have been able to close since I was the initiator of the issue,
—
Reply to this email directly or view it on GitHub https://github.com/Wireless-Innovation-Forum/Transceiver-Next/issues/1#issuecomment-72969056 .  https://github.com/notifications/beacon/ABia2-nT8KYL6wnzuj-ZOLTq2jZalHHTks5noqzQgaJpZM4Db6QZ.gif

See Permissions level
https://help.github.com/articles/permission-levels-for-an-organization-repository/
I believe if rights are set to "read access team" the user would have sufficient permissions to submit and review comments.

Try to edit now
From: ericrcaz<EMAIL_ADDRESS>Sent: February 4, 2015 4:19 PM
To: Wireless-Innovation-Forum/Transceiver-Next
Cc: LeePucker
Subject: Re: [Transceiver-Next] Test Issue for using GitHub (#1)
See Permissions level
https://help.github.com/articles/permission-levels-for-an-organization-repository/
I believe if rights are set to "read access team" the user would have sufficient permissions to submit and review comments.
—
Reply to this email directly or view it on GitHub https://github.com/Wireless-Innovation-Forum/Transceiver-Next/issues/1#issuecomment-72969835 .  https://github.com/notifications/beacon/ABia29TAjtle5ZoqAw2eOzZMoaTasmFVks5noq5egaJpZM4Db6QZ.gif

I still see the see the ability to close comment


Non-blocking discovery in get_chromecasts

Integrate non-blocking discovery into get_chromecast methods.
It might make sense for these to be separate functions, but since we've included the blocking argument anyway, I went ahead with this implementation.

It looks good, ok to merge when lint issues resolved (see travis).
I wonder if it's time for a PyChromecast 1.0 release in which we will also clean up the discovery methods. Especially all the filter stuff for discovery is out of scope for the project.

At least on the non-blocking front, I know get_device_status is still performing IO on the main thread when a Chromecast object is initialized. I'd like to get that corrected first.
I agree the filtering makes more sense as downstream logic. I think get_chromecasts_as_dict might be worth removing as well for the same reasons.
https://github.com/balloob/pychromecast/blob/master/pychromecast/dial.py#L38

I agree. They were contributions in the beginning of my open source career
when I wasn't that good at saying no yet
On Tue, Dec 13, 2016, 09:03 Adam Mills<EMAIL_ADDRESS>wrote:

At least on the non-blocking front, I know get_device_status is still
performing IO on the main thread when a Chromecast object is initialized.
I'd like to get that corrected first.
I agree the filtering makes more sense as downstream logic. I think
get_chromecasts_as_dict might be worth removing as well for the same
reasons.
https://github.com/balloob/pychromecast/blob/master/pychromecast/dial.py#L38
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/balloob/pychromecast/pull/136#issuecomment-266797113,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYJ2stOrxfn0buyZPibfMAfz4msMQhkks5rHs_fgaJpZM4LL9GL
.

FYI, contrary to my last post, as long as downstream fetches Chromecasts with the get_chromecasts method, the blocking IO in the Chromecast __init__ function happens in the internal_callback before calling the main callback, so it should be good.


1030 rotate debug camera with middle mouse button hold instead of key toggle

Description
Added a hold function to allow using the debug_camera holding a button as well as a toggle.
Added the input bindings to use the debug_camera on the cubosurfers sample.
Checklist

[ ] Self-review changes.
[ ] Evaluate impact on the documentation.
[ ] Ensure test coverage.
[ ] Write new samples.
[ ] Add entry to the changelog's unreleased section.

Not sure what is the guideline to merge the changes made on main

You should rebase on main, e.g.: git fetch origin; git rebase origin/main; git push --force-with-lease


Please specify why node NodeNotAvailableToDeploy when creating contract

Some deployments fail with error NodeNotAvailableToDeploy which is not descriptive of what might cause the deployment to fail, so I suggest a more informative error message of the failure cause

For node contracts, if you receive a NodeNotAvailableToDeploy error, it could mean one of the following:

The node’s power is down.
The node is rented, and you are not the rent contract owner.
The node is dedicated, and you are trying to deploy without renting the node first.

For rent contracts, possible reasons for the error are:

The node’s power is down.
The node is rented.

What about handling this from the client side?
For node contracts, the client error message could say node is down, rented, or dedicated. For rent contracts, the client error message could say node is down or has active deployments. Is this approach workable?
If this is not enough, we can reuse other errors type like NodeHasActiveContracts, NodeHasRentContract, so from tfchain side:

If node power is down the error returned is NodeNotAvailableToDeploy
If node is rented the error returned is NodeHasRentContract
If node has active deployments the error returned NodeHasActiveContracts

About the update to the client, we added a default value to the filter AvailableFor so that the FilterNodes would only return nodes the user can use to deploy, so the NodeNotAvailableToDeploy error in this case would show only in case the node is down which the filter makes sure to filter too, I think this solves the problem
and if otherwise the user used specific nodeID without using the filter it would be obvious that the node is not available so can use another node

@Eslam-Nawara So this can be closed if no changes required from chain side? Also note that "node (status) is down" is not same as "node's (power) is down".

Node is down: Node status unknown due to an network/ software/ hardware issue or power outage.
Node's power is down: not so obvious but this mean that node has entered a low power state and can be woken up on demand.

Yes, I think this change is no longer needed since the nodes returned from the filter will be guaranteed to be powered on and available for the user to deploy


Add DAU support for 1 master node of Redis cluster

Motivation

It's a feature that all IM applications will use
It's performant to implement if there is only one master Redis server. We can implement the feature without sending extra requests to Redis by just adding Hyperloglog support in try_add_online_user_with_ttl.lua

Limitation
We only support the feature if there is only one master Redis node
And we always recommend developers analyzing any user behavior via logs because they can acquire any data that want from logs with the best performance. (And that's what turms-data, based on Flink, will do for developers in the future)
Note
we save the DAU data in two places:

Logs. So developers can collect distributed statistics logs if they want.
MongoDB. So we can just give users more features out of the box without performance loss (because we save data daily).

Declined. We should always recommend developers analyzing any kind of user behavior via logs and won't provide a fallback solution to waste our time and energic, especially fallback solutions will make users rely on not-recommended solutions and hinder their apps from migrating to the recommended solutions in the future.


doc: install pyocd using pip2

pyocd does not exist as a python 3 module, use pip2 to install it.
Fixes #5699

Codecov Report

Merging #6003 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6003   +/-   ##
=======================================
  Coverage   52.51%   52.51%
=======================================
  Files         406      406
  Lines       39683    39683
  Branches     7715     7715
=======================================
  Hits        20839    20839
  Misses      15663    15663
  Partials     3181     3181

Continue to review full report at Codecov.

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

Should we just give the command line to install pyOCD without requirements-2 file?

Should we just give the command line to install pyOCD without requirements-2 file?

we could, but based on experience, some other module might be needed later which will lead to us being out of sync with the packages that need to be installed. better to have them in one place.

https://github.com/mbedmicro/pyOCD/issues/208


add nodejs minishift images in language mapping

partly https://github.com/openshift/odo/issues/2129

•  Syncing files to the component  ...
[odo]  ✗  Syncing files to the component [125ms]
[odo]  ✗  unable to upgrade connection: container not found ("dotnet-app-app")

/retest

/retest

/approve

/lgtm


Version check for extensions is broken with Symphony 2.6.10

After updating to Symphony 2.6.10, the extensions page is crowded with: requires Symphony 2.6. Obviously the version check doesn't work as advertised.
These complaints occur for all extensions that have min="2.6.x" or min="2.6.0" or min="2.6" requirement, in short words: Mimimum version is "2-6-something". All other extensions work fine in my case.
Examples:

fine: Members ( <release version="1.5.2" date="2016-06-23" min="2.4.0" max="2.x.x">)
fine: Remote Datasource ( <release version="2.2.1" date="2015-12-01" min="2.4" max="2.6.x">)
complaining: Select Box Link Field (<release version="1.33" date="2015-02-23" min="2.6.0">)
complaining: Email Newsletter Manager ( <release version="3.3.0" date="2016-11-03" min="2.6" max="2.6.x">)

If I am not mistaken, the issue is in line 968 of /symphony/lib/toolkit/class.extensionmanager.php:
$current_symphony_version = preg_replace(array('/dev/i', '/-?beta\.?\d/i', '/-?rc\.?\d/i', '/.0/i'), '', $

Shouldn't the last dot be escaped, like so:
$current_symphony_version = preg_replace(array('/dev/i', '/-?beta\.?\d/i', '/-?rc\.?\d/i', '/\.0/i'), '', $

@brendo? @nitriques?

We may do well to start to reach outside of our circle for this, composer/semver.

But we need a bugfix first for the 2.6.x line, don't we?

But we need a bugfix first for the 2.6.x line, don't we?

We can, but our handling still won't be as robust as a package that's sole purpose is to do this.
The issue right now is that we've never had a patch version greater than 9. The line highlighted above attempts to 'normalise' the version by removing dev, beta, rc and replacing it with nothing. eg.
2.6.7dev => 2.6.7
2.5.1-rc.1 => 2.5.1

This falls down right now because it also attempts to normalise versions:
2.5.0 => 2.5
2.6.10 => 2.6.10

I'm not quite sure how this is affecting the remaining logic.

But we need a bugfix first for the 2.6.x line, don't we?

This features has been fixed several times already, either within the core or within the extensions (all of them). It never worked reliably. Using a dedicated and tested package for this task sounds like a good idea to me.

I understand your concerns. But won't this take some time? Isn't this something for 2.7, because it might as well introduce new issues?

Yes, raising the version number sounds appropriate. I'm not sure if manual fixing would be faster (at least if you don't want it to break again soon).

Am 18.01.2017 um 10:48 schrieb michael-e<EMAIL_ADDRESS>I understand your concerns. But won't this take some time? Isn't this something for 2.7, because it might as well introduce new issues?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

My fix above doesn't work correctly. The regex expression in question should be:
/\.0(\.0)?$/i

Then we get:
2.0.0     ->  2
2.0.1     ->  2.0.1
2.0.10    ->  2.0.10
2.1.0     ->  2.1
2.1.1     ->  2.1.1
2.1.10    ->  2.1.10
2.10.0    ->  2.10
2.10.1    ->  2.10.1
2.10.10.  ->  2.10.10

I simply try do fix a regex mistake. With this fix version 2.6.10 stays 2.6.10 instead of becoming 2.6. So it would be a simple solution for the stable 2.6 branch, and we could release 2.6.11 rather fast. (The 2.7 branch already has lots of new stuff.)
This doesn't mean that I am against the composer package. But on the first hand I am pro a stable and production-ready 2.6 branch.

@michael-e I can confirm this to work!

Yeah thanks @michael-e I'll fix this ASAP.

2.6.10 also broke a couple of things on the getsymphony.com website.

I can send a pull request for this "extension version check issue" if you agree that my solution just fixes a faulty regex (so it shouldn't make anything worse). Just tell me to which branch I should send it.

The old regex — designed to strip .0 from version numbers — was /.0/i. (The i modifier ist useless here.) The dot matches any alphanumeric character or number, so the expression will match the 10 in 2.6.10 (resulting in 2.6.). My solution simply assumes that the desired output in this case is 2.6. See https://github.com/symphonycms/symphony-2/issues/2641#issuecomment-273440454

Please go ahead and submit against the 2.6.x branch. Thanks Michael.


A11y: VoiceOver reads variant properties twice and outputs metadata

In the product detail page, if you’re using VoiceOver and VO + Arrows to navigate individual content, the variant selectors are read twice. If you pause after, it will also read out what I assume is a string of metadata.
Bonus in video: Peek at the Image Gallery
{panel:bgColor=#deebff}
Also affects CMS Extensions
{panel}

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39111
[created from NEXT-39111, comment 505533]

[public]

Status Change: Open

This issue is ready for implementation.
[created from NEXT-39111, comment 510209]


Initial support for groovy

Thanks, but I only merge functionality that I use myself, so that I can support it: I'm not trying to make this config something that will work for everyone. Feel free to add groovy support in your fork, or in your init-local.el.


Add "doctype plist"

Hey i just thought that would be a good addition to the doctypes
doctype plist

into
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

Also could fix the problem that when you write two different doctypes beside each other they end up on the same line they need to be on two different lines

Please feel free to submit a pull request to https://github.com/pugjs/doctypes


Migrate to asto 0.4

@Sammers21 the latest version of asto is 0.13 now: https://github.com/artipie/asto/tree/0.13.2

@0crat assign @Sammers21

@0crat assign @Sammers21  (here)

@g4s8 The job #14 assigned to @sammers21/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; we should be aware that @sammers21/z is on vacation; this ticket may be delayed; there will be no monetary reward for this job

It is strongly discouraged to assign jobs to their creators, see §19: -15 point(s) just awarded to @g4s8/z

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @g4s8/z

Bug was reported, see §29: +15 point(s) just awarded to @sammers21/z

@sammers21/z this job was assigned to you 6days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@Sammers21 fixed in #21

Order was finished: +30 point(s) just awarded to @sammers21/z

@g4s8/z everybody who has role DEV is banned at #14; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)


Editor secuirty page (work in progress)

Initial Security page in Editor.

Looks good :)
Can you had a screenshot to the PR?

/cf-test

https://g.codefresh.io/public/accounts/soluto/builds/5c30ef1be9274f30a66a334a

/cf-test

also react-editable-json-tree

docker build should pass now..


[no-use-before-declare] Breaks with aliased imports

Not sure what's technically going on in the linter, but resolve is definitely not used before it's defined.

looks like a bug. we don't have many tests for aliases in binding patterns like that.

@blakeembrey You're seeing the problem because tslint thinks that your { resolve as resolveURL } is you trying to use the resolve you imported in the next line. However, I can only seem to duplicate the behavior when I import things from the same module twice. If you don't mind, can you post the full text of your import statements?

@JKillian Thanks, I figured. Here's the source: https://github.com/typings/cli/blob/master/src/lib/dependencies.ts#L8-L9.

Thanks @blakeembrey. I'm checking into this in more detail, to find out if it's something we need to fix or if it's a TypeScript bug: https://github.com/Microsoft/TypeScript/issues/5551

:+1: on getting this fixed from @ShadowManu, who also encountered this issue.

import * as React from 'react';
import ReactTestUtils = React.addons.TestUtils;

This is also broken ^^

in TSLint 5.0, no-use-before-declare uses the compiler's implementation of that check. going to close this as external, let me know if it pops up again. if it persists, it's likely a compiler bug.


Suggestions for the README

Please add to the README file:

A quick description of what is aetos, one paragraph can be enough
A link to the binary for downloading

totally agree


Upgrade to Node.js v6.9.3

PTAL

Actually 6.9.4 was just released. Can you spin that?

PR has the change for 6.9.4.


Parse Error: Invalid header value char

const fetch = require('node-fetch');

fetch('https://secure.runescape.com/m=hiscore_oldschool/index_lite.ws?player=magnaboy');

Fails with this error:
 FetchError: request to https://secure.runescape.com/m=hiscore_oldschool/index_lite.ws?player=magnaboy failed, reason: Parse Error: Invalid header value char
     at ClientRequest.<anonymous> (C:\project\node_modules\node-fetch\lib\index.js:1455:11)
     at ClientRequest.emit (events.js:315:20)
     at TLSSocket.socketOnData (_http_client.js:514:9)
     at TLSSocket.emit (events.js:315:20)
     at addChunk (_stream_readable.js:302:12)
     at readableAddChunk (_stream_readable.js:278:9)
     at TLSSocket.Readable.push (_stream_readable.js:217:10)
     at TLSWrap.onStreamRead (internal/stream_base_commons.js:186:23)

I tried to call this API with the exact same headers in other programming languages, in curl, wget and in all browsers - and it works in everything except nodejs, that I can find. Is it possible anyone can shed some light on this and if its possibly a problem in nodejs?
I've exhausted the depth of my ability to debug this error, and don't know how I should proceed. I reported it to the website owners but it doesnt seem practical or any priority at all for them to fix the root cause of whichever http header causes this.

The offending header, formatted with xxd:
00000b5e: 4d61 782d 4167 653d 3930 300d 0a3c 2053 6574 2d43 6f6f 6b69 653a 205f 5f5f  Max-Age=900..< Set-Cookie: ___
00000b7c: 7574 6d76 624b 5075 6d4c 4d4f 5a3d 415a 7a0d 0a3c 2020 2020 2058 4b70 4f4b  utmvbKPumLMOZ=AZz..<     XKpOK
00000b9a: 616c 473a 2059 7468 3b20 7061 7468 3d2f 3b20 4d61 782d 4167 653d 3930 300d  alG: Yth; path=/; Max-Age=900.
00000bb8: 0a3c 2058 2d43 444e 3a20 496e 6361 7073 756c 610d 0a3c 2054 7261 6e73 6665  .< X-CDN: Incapsula..< Transfe

The header on the last line starts with < X-CDN: and that's simply illegal; http-parser is right to reject it.
Other parsers may be more lenient but that's on them. Trying to make something meaningful out of garbage is a recipe for security issues.

sorry for necromancing the conversation, we're hitting a similar issue.
But, @bnoordhuis are you sure that output (you've formatted with xxd) is not curl's verbose output? Curl displays server response prefixed with <   just for display purposes.


libcublas-dev should depend on cuda-crt-dev_*

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [111]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Just to be sure, purposely taking out any one of cuda-cudart-dev and cuda-crt-dev failed the compilation of test.c

This PR resolves issue #8


coursier breaks on usages of ${packaging.type}

Example of how it looks in the console:
[error]     Caught java.io.IOException: Server returned HTTP response code: 400 for URL: MY_PRIVATE_REPO/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type} (Server returned HTTP response code: 400 for URL: MY_PRIVATE_REPO/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}) while downloading MY_PRIVATE_REPO/javax/ws/rs/javax.ws.rs-api/2.1/javax.ws.rs-api-2.1.${packaging.type}
[error] (update) coursier.ResolutionException: 1 download error

As clearly seen, coursier tries to actually use the "${packaging.type}" text in URL. I must acknowledge that the problem is indeed very ugly. It's present in sbt as well, though the following work-around works there: https://github.com/sbt/sbt/issues/3618#issuecomment-334896668
With coursier, it doesn't, at least in version 1.0.3.
Thoughts? Maybe coursier should resolve the ${} thing to a variable (sounds like a dangerous approach though). Maybe it should allow ${packaging.type} specifically, maybe falling back to "jar" as default value? The latter would be ideal of course, at least to users who do not fully understand wtf that is, like me. Thoughts?

@vn971 Do you have a small reproduction? The examples of https://github.com/sbt/sbt/issues/3618 seems fine with sbt-coursier 1.1.0-M7.

@alexarchambault I'll look into it. Currently at work, but I'll try to look from home.

Closing for now, re-open if you have a repro or consistently run into that with the latest version of coursier.


Realm crash (EXC_BAD_ACCESS) when writing while device is Locked.

My application writes location updates into the default Realm on iOS, Objective-C, 9.2.1, Realm 0.98.3
If the app is in the foreground, or background from pressing the home button, writes work as expected.
Once the device is locked, either by pressing the lock button or the device self locking- the next write crashes at in: inline void SharedGroup::commit_and_continue_as_read() at line 966- do_commit().
I'm not using Realm encryption nor iOS disk encryption.
The app crashes on iPhone 6, iPad mini (1st gen) and iPad Pro (haven't tested others) and it does not crash in the Simulator set to Locked.
I had this issue a few months ago and was able to resolve it by setting NSFileProtectionNone against all files in the Realm path at startup.  Now, I have to set NSFileProtectionNone before every write otherwise I see the crash.  This seems like a lot of overhead and I'm wondering if there is a better approach.
This is what I call to clear the protection:
NSString *pathToRealmFile = [RLMRealmConfiguration defaultConfiguration].path;
    NSArray *allRealmRelatedFiles = @[
                                      pathToRealmFile,
                                      [pathToRealmFile<EMAIL_ADDRESS>                                      [pathToRealmFile<EMAIL_ADDRESS>                                      [pathToRealmFile<EMAIL_ADDRESS>                                      [pathToRealmFile<EMAIL_ADDRESS>                                      ];
    for (NSString *path in allRealmRelatedFiles) {
        NSError *error = nil;
        //
        [[NSFileManager defaultManager] setAttributes:@{NSFileProtectionKey: NSFileProtectionNone} ofItemAtPath:path error:&error];
        if (error) {
            NSLog(@"Error clearing protection on %@", path);
        }
    }

Any ideas are much appreciated.
Chuck-

The problem here is that the auxiliary files are not guaranteed to exist all the time. They might be deleted. If that happens and they are recreated, then you would need to set the file attributes again. But there are no hooks for that. As a workaround, I'd recommend to set the attribute for the directory where the Realm is stored. If there are other files in there, which would better make use of the encryption, then you can move the Realm files into another directory as a workaround by setting the default configuration's path.

See https://github.com/realm/realm-cocoa/issues/3224 for reference.


Crash Log

XivAlexander_20220715_205529_564.log

I'm having the same problem. https://i.imgur.com/vmQWkfl.png

I ve the same issue

I ve the same issue

Same issue here
XivAlexander_20220723_123929_577.log

Hey guys
this is a new error caused when your ff client isnt running with admin permissions. Doing this fixed it for me but leads to things like discord overlays not working

I am seeing the same issue, now constantly. At least 1 crash every hour up to about every 15 min. I do run FFXIV in admin mode too, that makes no difference
XivAlexander_20220728_022951_739.log
.

Hey guys
this is a new error caused when your ff client isnt running with admin permissions. Doing this fixed it for me but leads to things like discord overlays not working

No, I run it in admin mode for other reason and still this has been happening.

Bump because this is ongoing and I always run in admin mode

Went on textools , disabled Bibo+ , launched the game , used bibo+ on penumbra , game crashed with same errors while browsing my glamour plates. Disabled penumbra , still crashes . Re-enabled Bibo+ on textools , all works. Even using penumbra on top of the bibo+ from textools works , no crashes. I dont run the game in admin.


Error in rendering Chords - end of chords messed up

JSFiddle reproduces issue at https://jsfiddle.net/9m5e7wm9/2/
This chord looks funny. It isn't in the right place, and the ends are strange. What can I do?

Thank you for reporting this bug. It's fixed in version 1.6.2.

You RULE!
On Wednesday, July 22, 2015, nic.girault<EMAIL_ADDRESS>wrote:

Closed #10 https://github.com/nicgirault/circosJS/issues/10.
—
Reply to this email directly or view it on GitHub
https://github.com/nicgirault/circosJS/issues/10#event-361952492.

--
Russell Jurney twitter.com/rjurney<EMAIL_ADDRESS>datasyndrome.com


Review Rollbar dashboard to analyze errors and create task to tackle them

We have a lot of errors reported in: https://rollbar.com/decentraland/World/
We need to review all of them and create a plan to fix or remove them from that list.
This will help us to discover current unseen issues but also to be more proactive when a new issue appears.

@marcosnc In light of the latest error metric improvements, this is still necessary?


Implement PostGenesisDepositHandler

PR Description
Implements PostGenesisDepositHandler which (Captain Obvious here) deals with deposit events after genesis.

Had a good time with @cemozerr in NY Bogart office on my way to Denver. Deposit proof generation came up, and although it looks complicated, it is not.
One approach to generating inclusion proofs for the deposit tree, after genesis, is to just put all trusted deposits into one merkle tree, and limit the view to a given count ("viewLimit") when calculating the proof. This way you can use a single merkle tree to build proofs from, even if you go back and forth between states with different deposit counts.
Modified artemis code:
https://gist.github.com/protolambda/06c47e3e3579812e2f9422136111aa50
Now @cemozerr can look into testing and continue with other open issues, can't wait for a testnet :+1:


Gemm kernel does not exist

Hello, I was using MIOpen as an external library when implementing my own program. But below error occurs when I call the convolution forward API. I tried to link the miopengemm to the program, but it still doesn't work. Anyone got any clue? Thanks in advance!
ROCmSoftwarePlatform/MIOpen/src/gemm.cpp:329: looking for gemm kernel (does not exist): miopenConvolutionFwdAlgoGEMM, tC0_tA0_tB0_colMaj1_m65536_n32_k75_lda65536_ldb75_ldc65536_ws0_f32

@doody1986 Do you have miopengemm installed on your system, as noted in the Prerequisites section of the  README

@dagamayank
I did install that, and the output is as below. Thanks a lot !
miopenStatus_t miopenCreateTensorDescriptor(miopenTensorDescriptor_t *){
tensorDesc = 0x6572695720646e61
}
miopenStatus_t miopenCreateTensorDescriptor(miopenTensorDescriptor_t *){
tensorDesc = 0x30363237
}
miopenStatus_t miopenCreateConvolutionDescriptor(miopenConvolutionDescriptor_t *){
convDesc = 0
}
miopenStatus_t miopenCreateTensorDescriptor(miopenTensorDescriptor_t *){
tensorDesc = 0x303632
}
miopenStatus_t miopenSet4dTensorDescriptor(miopenTensorDescriptor_t, miopenDataType_t, int, int, int, int){
tensorDesc =
dataType = 1
n = 100
c = 3
h = 256
w = 256
}
miopenStatus_t miopenInitConvolutionDescriptor(miopenConvolutionDescriptor_t, miopenConvolutionMode_t, int, int, int, int, int, int){
convDesc = 0, 0, 1, 1, 1, 1,
mode = 0
pad_h = 2
pad_w = 2
u = 1
v = 1
dilation_h = 1
dilation_w = 1
}
miopenStatus_t miopenSet4dTensorDescriptor(miopenTensorDescriptor_t, miopenDataType_t, int, int, int, int){
tensorDesc =
dataType = 1
n = 32
c = 3
h = 5
w = 5
}
miopenStatus_t miopenSet4dTensorDescriptor(miopenTensorDescriptor_t, miopenDataType_t, int, int, int, int){
tensorDesc =
dataType = 1
n = 100
c = 32
h = 256
w = 256
}
miopenStatus_t miopenConvolutionForwardGetWorkSpaceSize(miopenHandle_t, const miopenTensorDescriptor_t, const miopenTensorDescriptor_t, const miopenConvolutionDescriptor_t, const miopenTensorDescriptor_t, size_t *){
wDesc = 32, 3, 5, 5
yDesc = 100, 32, 256, 256
convDesc = 2, 2, 1, 1, 1, 1,
workSpaceSize = 3159602
}
miopenStatus_t miopenConvolutionBackwardWeightsGetWorkSpaceSize(miopenHandle_t, const miopenTensorDescriptor_t, const miopenTensorDescriptor_t, const miopenConvolutionDescriptor_t, const miopenTensorDescriptor_t, size_t *){
dyDesc = 100, 32, 256, 256
xDesc = 100, 3, 256, 256
convDesc = 2, 2, 1, 1, 1, 1,
dwDesc = 32, 3, 5, 5
workSpaceSize = 14416760
}
miopenStatus_t miopenConvolutionBackwardDataGetWorkSpaceSize(miopenHandle_t, const miopenTensorDescriptor_t, const miopenTensorDescriptor_t, const miopenConvolutionDescriptor_t, const miopenTensorDescriptor_t, size_t *){
dyDesc = 100, 32, 256, 256
wDesc = 32, 3, 5, 5
convDesc = 2, 2, 1, 1, 1, 1,
dxDesc = 100, 3, 256, 256
workSpaceSize = 0
}
miopenStatus_t miopenConvolutionForward(miopenHandle_t, const void *, const miopenTensorDescriptor_t, const void *, const miopenTensorDescriptor_t, const void *, const miopenConvolutionDescriptor_t, miopenConvFwdAlgorithm_t, const void *, const miopenTensorDescriptor_t, void *, void *, size_t){
alpha = 0x7f55c0a81138
xDesc = 100, 3, 256, 256
x = 0x22010a7000
wDesc = 32, 3, 5, 5
w = 0x226e6ab000
convDesc = 2, 2, 1, 1, 1, 1,
algo = 0
beta = 0x7f55c0a82a34
yDesc = 100, 32, 256, 256
y = 0x220a6a9000
workSpace = 0x226e6b3000
workSpaceSize = 19660800
}
MIOpen Error: /home/yifan/dev/src/github.com/ROCmSoftwarePlatform/MIOpen/src/gemm.cpp:329: looking for gemm kernel (does not exist): miopenConvolutionFwdAlgoGEMM, tC0_tA0_tB0_colMaj1_m65536_n32_k75_lda65536_ldb75_ldc65536_ws0_f32

How did you install miopengemm? The above convolution is working fine on my end.

@dagamayank
I just used "sudo apt-get install miopengemm. Is that all right?

@dagamayank
I tried to build an MIOpen library with miopengemm instead of using the one installed, but it still doesn't work.

@doody1986
You have to run  miopenFindConvolutionForwardAlgorithm(...) prior to miopenConvolutionForward.
In your log above it looks like you're not doing this. The Find type functions will create and compile multiple kernels, and then run each one once to find the fastest one. The miopenConvolutionForward function then just tries to load the kernel, but fails because the kernel was not yet created/compiled.

Thanks a lot! That explains a lot. I thought it would work when I hard-coded the algorithm in my code

@patflick Thanks for catching that. I also added a wiki page to clarify a bit about MIOpen Convolutions.


False Positive UnnecessaryApply

Expected Behavior
No UnnecessaryApply is reported
Observed Behavior
UnnecessaryApply is reported
Steps to Reproduce
val view = FrameLayout(context).apply {
    background = ColorDrawable(ContextCompat.getColor(context, R.color.white))
}

Context
Since I'm using the return value, the apply isn't unnecessary.
Your Environment

Version of detekt used: 1.0.0-RC10
Version of Gradle used (if applicable): 4.10.2
Operating System and version: Various

Just tested that rule and got plenty of different false positives too.
                        .selectAll(MoviesTable.ALL_TABLE_COLUMNS)
                        .apply {
                            if (!genre.isNullOrEmpty()) {
                                where(MoviesTable.GENRES + " LIKE ?", "%$genre%")
                            }
                        }
                        .orderBy("RANDOM()")

or
    val databaseAdapter: DatabaseAdapter by lazy {
        DatabaseAdapter(this).apply {
            try {
                open()
            } catch (e: SQLiteException) {
                logError(TAG, e) { "Error with database" }
            }
        }
    }

Some more:
private val staticCirclePaint = Paint().apply { isAntiAlias = true }
fun setColor(color: Int) = apply { initialColor = color }

Another:
private val requestedInterval by lazy {
    MutableLiveData<Int>().apply { value = UsageFragment.INTERVAL_DAY }
}

I like the rule but it needs some additional constraints.
Having the same issue with
val itemAnimator = DefaultItemAnimator().apply { supportsChangeAnimations = false }

Yeah, I resided to replace .apply with .also in these places, because in these single cases I'm not too lazy to write the additional it. and wanted to keep notified about the real issue cases, but certainly, this is an arbitrary "workaround".

I chose to suppress it and added a todo to follow up on the ticket. More work, though.

On Nov 21, 2018, at 9:13 AM, Thomas Keller<EMAIL_ADDRESS>wrote:
Yeah, I resided to replace .apply with .also in these places, because in these single cases I'm not too lazy to write the additional it. and wanted to keep notified about the real issue cases, but certainly, this is an arbitrary "workaround".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Happening to us as well.
override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? =
        inflater.inflate(productDetailsR.layout.fragment_product_details_tab, container, false).apply {
            containerView = this
        }

Is there any way we could change that rule? Do you think that this rule would make more sense when using apply and not using the result of it?
So detekt complains about:
questionHeaderSortByLabel.apply {
  contentDescription = resources.getString(R.string.ada_qna_sorted_by, sortedByValue)
}

but not about:
val content = Intent().apply {
  putExtra("", 1)
}

This should be a blocker regarding 1.0.0


Goodscents Indexing

goodscents/behavior.csv is indexed by TGSC.ID instead of CID. TGSC.ID does not appear in goodscents/molecules.csv

TSGC.ID is linked to CID by identifiers.csv.  This allow the full GoodScents data to be included even in those cases where a CID could not be obtained for a given structure.  In other words, an inner join of identifiers and behavior will retain those GoodScents entries that have a CID, which can then be looked up in molecules.csv.

I know there is some harmonization that needs to be done next week.

I did three joins to get a molecule, odor table.
6157 rows in behavior_sparse.csv. I join with identifiers.csv on the "TGSC ID".
I then join this table with molecules.csv on "CID".
oddly, after the (inner) join, I am left with only 5702 rows... so some "TGSC ID" in behaviors.csv is not in identifiers.csv. 😢

Fixed in #176


Fix/responses modal error handling

Summary | Résumé
A start on updating the dialog error handling and error messages. The error message content still needs approved/updated by design.
Test instructions | Instructions pour tester la modification
Open each dialog and test the error messages
Unresolved questions / Out of scope | Questions non résolues ou hors sujet
More error handling for less frequent errors
Would be nice if the Report API returned a list of invalid form names, similar to the Confirm API. (future todo for me probably)

Still refactoring and adding languages strings. I'll close this for now


Contract updates for mainnet

[x] Upgradable proxy, contract
[x] Add fields for badge uri and schemaUID in events Struct
[x] bug: attendee count bug, fix attendee double count
[x] audit contract for other possible bugs

completed in #36


Bug: Github oauth未正常工作

Describe the bug
Github oauth未正常工作，无法正确的绑定到用户
Steps to reproduce
如下面的截图所配置，然后按照正常的流程走即可出现
Expected behavior
成功绑定用户
Screenshots

Versions

OS: CentOS 7.9.2009 x86_64
Platform: onebot
Node version: v14.19.0
Koishi version: 4.6.1

Additional context
https://user-images.githubusercontent.com/43847794/165428566-1a26a4ce-e09f-436c-8cea-0778d58d21ae.mp4

@MaikoTan 这个 issue 大概是怎么回事？

@MaikoTan 这个 issue 大概是怎么回事？

Idk, with the latest version now (5.0.2) I can only reproduce the error codes 422 and 408 in authorizing phase. (But I still am not able to make it work either, maybe not the same issue)
I would read some GitHub documents and investigate this issue later.

https://github.com/koishijs/koishi-plugin-github/blob/44b5845c7db9a5cd0e06d6e9bc0337cfb4830102/src/server.ts#L120-L130
Looks like the code here requests the URL with query parameter instead of HTTP body, is it expected?

Looks like the code here requests the URL with query parameter instead of HTTP body, is it expected?

I think I'm doing what the documentation says.
https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps#2-users-are-redirected-back-to-your-site-by-github

As for my experience, if config.redirect is misconfigured, the api would be likely to return a 4xx error. Also, there seems not to be any configuration check here.

我也遇到了，无论是配置了 config.redirect 还是使用默认，都会出现如上问题，且最终绑定不成功

遇到同样问题

2024-07-21 01:32:59 [W] github Error: Unprocessable Entity
at [cordis.invoke] (/koishi/node_modules/@cordisjs/plugin-http/lib/index.cjs:335:23)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Proxy.request (/koishi/node_modules/koishi-plugin-github/lib/index.js:77:20)
at async Command. (/koishi/node_modules/koishi-plugin-github/lib/command.js:68:28)
at async Array. (/koishi/node_modules/@koishijs/core/lib/index.cjs:1121:14)
at async Command.execute (/koishi/node_modules/@koishijs/core/lib/index.cjs:1135:22)
at async /koishi/node_modules/@koishijs/core/lib/index.cjs:2154:22
at async Proxy.withScope (/koishi/node_modules/@koishijs/core/lib/index.cjs:2057:22)
at async next (/koishi/node_modules/@koishijs/core/lib/index.cjs:860:16)
at async next (/koishi/node_modules/@koishijs/core/lib/index.cjs:860:16)


[BUG] Invoke-PnPSiteTemplate messing up / and \ in current nightly

Category

[x] Bug

Describe the bug
Invoke-PnPSiteTemplate -Path "./tmp/pages/de/Page.xml" fails with "Object reference not set to an instance of an object." in Version  2.2.104-nightly when PageName in Page.xml is "folder1/folder2/Page.aspx" contains more than one subfolder. I guess this is the problem, slash and backslah messed up:

Even if correct in XML

Expected behavior
No Error, as using just one subfolder, like ./tmp/pages/Page.xml with PageName in Page.xml is "folder1/Page.aspx"
Environment details (development & target environment)

PNP version: 2.2.104-nightly
OS: Windows 11
PSVersion: 7.3.8
PSEdition: Core

hi @reply-jens , thanks for opening the issue.
Could you please open it here instead: https://github.com/pnp/pnpframework/issues ?
PnP PowerShell consumes the provisioning engine, the actual logic resides in the above mentioned repo. Will be closing it here.


python310Packages.gcal-sync: 0.9.0 -> 0.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.gcal-sync is: "Python library for syncing Google Calendar to local storage"
meta.homepage for python310Packages.gcal-sync is: "https://github.com/allenporter/gcal_sync"
meta.changelog for python310Packages.gcal-sync is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.1 with grep in /nix/store/4ygc39w058shjxmsiimjwzxssmyjqqca-python3.10-gcal-sync-0.9.1
found 0.9.1 in filename of file in /nix/store/4ygc39w058shjxmsiimjwzxssmyjqqca-python3.10-gcal-sync-0.9.1

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

5 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.google
python310Packages.gcal-sync
python39Packages.gcal-sync

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4ygc39w058shjxmsiimjwzxssmyjqqca-python3.10-gcal-sync-0.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4ygc39w058shjxmsiimjwzxssmyjqqca-python3.10-gcal-sync-0.9.1
ls -la /nix/store/4ygc39w058shjxmsiimjwzxssmyjqqca-python3.10-gcal-sync-0.9.1/bin

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

3 packages built:

home-assistant-component-tests.google
python310Packages.gcal-sync
python39Packages.gcal-sync

Maintainer pings
cc @dotlambda for testing.

addressed by https://github.com/NixOS/nixpkgs/pull/178315


Pushing getting started changes to live

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/resources/design/framework/submitting.md
:warning:Warning

Details

msteams-platform/concepts/cards-actions.md
:warning:Warning

Details

msteams-platform/includes/get-started/step1-prepare-for-dev.md
:warning:Warning

Details

msteams-platform/includes/get-started/step1-intro.md
:warning:Warning

Details

msteams-platform/TOC.yml

[Warning] Invalid file link:(~/resources/dev-preview/developer-preview-intro).
[Warning] Invalid file link:(~/resources/design/framework/search).
[Warning] Invalid file link:(~/resources/resource-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-test).
[Warning] Invalid file link:(~/resources/general/cross-domain).
[Warning] Invalid file link:(~/concepts/activity-feed).
[Warning] Invalid file link:(~/concepts/bots/bots-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-context).
[Warning] Invalid file link:(~/concepts/tabs/tabs-content).
[Warning] Invalid file link:(~/resources/design/components/color).
[Warning] Invalid file link:(~/concepts/cards-actions).
[Warning] Invalid file link:(~/scenarios/scenarios).
[Warning] Invalid file link:(~/resources/design/framework/apps).
[Warning] Invalid file link:(~/concepts/outgoingwebhook).
[Warning] Invalid file link:(~/concepts/connectors).
[Warning] Invalid file link:(~/resources/design/resources).
[Warning] Invalid file link:(~/resources/design/framework/submitting).
[Warning] Invalid file link:(~/resources/design/framework/basics).
[Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
[Warning] Invalid file link:(~/samples/code-samples).
[Warning] Invalid file link:(~/concepts/bots/bots-notifications).
[Warning] Invalid file link:(~/resources/schema/manifest-schema).
[Warning] Invalid file link:(~/concepts/apps/apps-package).
[Warning] Invalid file link:(~/get-started/get-started-tenant).
[Warning] Invalid file link:(~/resources/design/overview).
[Warning] Invalid file link:(~/resources/design/framework/cards).
[Warning] Invalid file link:(~/resources/design/framework/tabs).
[Warning] Invalid file link:(~/resources/dev-preview/developer-preview).
[Warning] Invalid file link:(~/resources/design/framework/bots).
[Warning] Invalid file link:(~/concepts/concepts-overview).
[Warning] Invalid file link:(~/troubleshoot/faq).
[Warning] Invalid file link:(~/scenarios/bots-personal-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
[Warning] Invalid file link:(~/concepts/bots/bots-menus).
[Warning] Invalid file link:(~/get-started/get-started).
[Warning] Invalid file link:(~/concepts/bots/bots-create).
[Warning] Invalid file link:(~/get-started/get-started-nodejs).
[Warning] Invalid file link:(~/resources/design/components/fields).
[Warning] Invalid file link:(~/resources/design/framework/activity-feed).
[Warning] Invalid file link:(~/resources/design/framework/messaging-extensions).
[Warning] Invalid file link:(~/scenarios/bots-channel-conversations).
[Warning] Invalid file link:(~/publishing/apps-publish).
[Warning] Invalid file link:(~/resources/dev-preview/developer-preview-features).
[Warning] Invalid file link:(~/resources/general/rate-limit).
[Warning] Invalid file link:(~/resources/design/components/typography).
[Warning] Invalid file link:(~/resources/microsoft-graph).
[Warning] Invalid file link:(~/publishing/office-store-guidance).
[Warning] Invalid file link:(~/concepts/apps/apps-overview).
[Warning] Invalid file link:(~/concepts/deep-links).
[Warning] Invalid file link:(~/resources/design/components/buttons).
[Warning] Invalid file link:(~/resources/design/components/dialogs).
[Warning] Invalid file link:(~/resources/general/requirements).
[Warning] Invalid file link:(~/concepts/authentication).
[Warning] Invalid file link:(~/publishing/office-store-checklist).
[Warning] Invalid file link:(~/concepts/messaging-extensions).
[Warning] Invalid file link:(~/.general/general-overview).
[Warning] Invalid file link:(~/overview).
[Warning] Invalid file link:(~/resources/design/components/themes).
[Warning] Invalid file link:(~/resources/general/debug).
[Warning] Invalid file link:(~/get-started/get-started-app-studio).
[Warning] Invalid file link:(~/feedback).
[Warning] Invalid file link:(~/troubleshoot/troubleshoot).
[Warning] Invalid file link:(~/concepts/bots/bots-cards).
[Warning] Invalid file link:(~/concepts/tabs/tabs-static).
[Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
[Warning] Invalid file link:(~/concepts/apps/apps-upload).
[Warning] Invalid file link:(~/concepts/bots/bots-context).

msteams-platform/resources/design/framework/submitting.md

Line 130: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 194: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).

msteams-platform/concepts/cards-actions.md

Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).

msteams-platform/includes/get-started/step1-prepare-for-dev.md

Line 10: [Warning] Invalid file link:(~/get-started/get-started-tenant).
Line 15: [Warning] Invalid file link:(~/get-started/get-started-tenant).

msteams-platform/includes/get-started/step1-intro.md

Line 3: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 5: [Warning] Invalid file link:(~/get-started/get-started-app-studio).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support execOverrides on NpmSetupTask

We have recently upgraded from the old mooworks gulp and node plugins to the latest single "repo" version.
In our old setup, we liked to squelch NPM, Node, and Gulp tasks unless they failed with the following:
hideNonFailingOutput = {
        ignoreExitValue = true
        def execRunner = null
        execOverrides {
            execRunner = it
            it.standardOutput = new ByteArrayOutputStream()
            it.errorOutput = it.standardOutput
        }
        doLast {
            if (result.exitValue != 0) {
                println(execRunner.standardOutput.toString())
                throw new GradleException("exec failed; see output above")
            }
        }
    }

build.gradle
npmSetup {
       configure hideNonFailingOutput
    }

In the newest version, when I try to run gradle npmSetup, the following error occurs:
> Could not find method execOverrides() for arguments [build_13tmtfk6heqf6fa4c13hvdop7$_run_closure3$_closure30$_closure39@1c0d19ca] on task ':webclient:npmSetup' of type com.moowork.gradle.node.npm.NpmSetupTask.

When I look at the current source I see that NpmSetupTask uses an internal NpmExecRunner (https://github.com/srs/gradle-node-plugin/blob/master/src/main/groovy/com/moowork/gradle/node/npm/NpmSetupTask.groovy#L83), but does not provide a way to configure that ExecRunner other than passing args.
Was this functionality or capability removed for a reason?  If not, would it be possible to add back in a way to configure execOverrides on an NpmSetupTask (so these could be passed internally to the NpmExecRunner or configured)?

That was not an intentional removal. Will add that back in. Marking this as a bug.

Could you provide a complete example of this?

@srs I'm confused what you mean by complete example?
My original post shows how we are trying to provide execOverrides for the npmSetup task.  However, npmSetup no longer exposes or supports execOverrides configuration.  We are doing this so we can squelch NPM output which we don't need in our gradle output unless an error occurs.
Something as simple as:
npmSetup {
   execOverrides {

   }
}

should cause the error since execOverrides is not defined anymore on the NpmSetupTask.
Error output:
* What went wrong:
A problem occurred evaluating project ':webclient'.
> Could not find method execOverrides() for arguments [build_89gbdgndlf88e5p5k8082bhzi$_run_closure3$_closure28$_closure37@11336498] on task ':webclient:npmSetup' of type com.moowork.gradle.node.npm.NpmSetupTask.

Oh, sorry. Misunderstood the original issue. Will create a simple example of this and then fix it for NpmSetupTask and all the other tasks.


ERC721AURIStorage extension?

Any plan to add ERC721URIStorage counterpart for ERC721A?

Nope.
Please override your tokenURI to construct return the URI on the fly.


Observable is deprecated:

https://github.com/PacktPublishing/Angular-Projects-Second-Edition/blob/main/Chapter04/src/app/app.component.ts uses deprecated "available", and gets the following message:
(property) SwUpdate.available: Observable
Emits an UpdateAvailableEvent event whenever a new app version is available.
@deprecated
Use versionUpdates instead.
The of behavior available can be rebuild by filtering for the VersionReadyEvent:
import {filter, map} from 'rxjs/operators';
// ...
const updatesAvailable = swUpdate.versionUpdates.pipe(
filter((evt): evt is VersionReadyEvent => evt.type === 'VERSION_READY'),
map(evt => ({
type: 'UPDATE_AVAILABLE',
current: evt.currentVersion,
available: evt.latestVersion,
})));
I'm trying to figure out how to add the snackbar and other actions but don't have it yet. Ideas?! Thx!

 It has been deprecated in Angular 13 along with the activated property as indicated in the official Angular Docs website https://angular.io/guide/deprecations#angularservice-worker. I guess that you can still use it though because it has not been removed.

The Angular framework usually makes a deprecation announcement and keeps the feature for some versions before removing it completely.

Does it work at all in your case?

Thank you @bampakoa for the solution


Support grace notes

Fixed by 0548b336b63e625876ab2842ef1f4ede81646412 and b2fc2a717158d63daa176dd2d66cffe8ad35589a.  Although accidentals are not displayed nor are they supported in chords, tuplets and broken rhythm pairs.  This is enough for my purposes I think.


How to correctly capture DockerException?

I am not sure to understand how to correctly capture the errors of some python-on-whales calls.
A specific example:
docker = DockerClient(compose_files=['docker-compose.yml'])
docker.compose.up(detach=True)

The docker-compose.yml contains an error (in this case an external network is missing). The output I get is this:
Error response from daemon: network factory-net not found
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/wuthrich/codes/DemoFactory/OpenFactory/venv/openfact/lib/python3.10/site-packages/python_on_whales/components/compose/cli_wrapper.py", line 1017, in up
    run(full_cmd, capture_stdout=quiet, capture_stderr=quiet)
  File "/home/wuthrich/codes/DemoFactory/OpenFactory/venv/openfact/lib/python3.10/site-packages/python_on_whales/utils.py", line 194, in run
    raise DockerException(
python_on_whales.exceptions.DockerException: The docker command executed was `/bin/docker --file docker-compose up --detach`.
It returned with code 1
The content of stdout can be found above the stacktrace (it wasn't captured).
The content of stderr can be found above the stacktrace (it wasn't captured).

The error I am interested in catching is Error response from daemon: network factory-net not found.
How would I do this?
A try except clause doesn't seem to work here.
try:
    docker.compose.up(detach=True)
except DockerException as err:
    print(err)

which results in
The docker command executed was `/bin/docker --file docker-compose up --detach`.
It returned with code 1
The content of stdout can be found above the stacktrace (it wasn't captured).
The content of stderr can be found above the stacktrace (it wasn't captured).

The error message I am interested in can't be find in the raised DockerException as neither stdout nor stderr were captured (they both return None). I guess the message Error response from daemon: network factory-net not found should be either in stdout or stderr.
Do I have to configure somehow my DockerClient in order the stdout and stderr get captured? Or how do I access the error response from the Docker daemon?

Well, this is tricky, and definitly an area where Python-on-whales could be improved. To enable TTY by default, we must avoid capturing any output. This is because the docker client can detect if stdout and stderr are TTY and changes the output accordingly. You can disable TTY, but it's still not captured from the python side at the moment.
You could try contextlib.redirect_stdout and contextlib.redirect_stderr with tty=False, but i'm not even sure that would work.
The right solution would be to make the subprocess believe it's using a TTY while we grab the output, with something like https://docs.python.org/fr/3/library/pty.html for example, but that's a lot of work, and may not be a good fit for this simple codebase.
You can try to experiment with subprocess directly, without python-on-whales. If you manage to do what you want feel free to post it here, that might help us find a better long term solution for this package.

I see. We will experiment with subprocess directly.

Indeed I wish they would return different error codes depending on the error type, then we wouldn't have to parse logs to see what kind of error it was. I raised an issue a while ago but it didn't get much traction.


FooDB

The latest FooDB database has IUPAC, INCHIKEY, INCHI and SMILES equivalent identifiers for chemical compounds. there are no equivalent identifiers for nutrients.
sadly, previous versions of the data had better equivalent identifiers.
the INCHIKEY is currently used by the parser to normalize the nodes and has a 0% success rate. look into using another equivalent identifier in the FooDB data that is more successful.
an example failure is: INCHIKEY:1S/C15H24/c1-11-7-8-13-12(2)6-5-9-15(3,4)14(13)10-11/h6,10,13-14H,5,7-9H2,1-4H3

It will be easier to track down with more information: For a few failing chemicals, what are the inchikeys (as above), but also, what is the chemical name?  It would be especially good if some of these were simple things like water or fructose or glutamate, which I expect should appear in the data.

Oh, I think the problem is that the identifier above is not an inchikey.  It's an inchi.   An inchikey is something more like:
AXVVJQZAKNNTPN-UHFFFAOYSA-N

I think foodb needs to be looked at.  It's using ChemicalSubstance and incorrect identifiers.  We might need to work on babel first to get the id's for foods to work better.


doesn't work with mmd 9.32

the latest version of the plugin installer doesn't work with mmd 9.32 I cannot install the installer to get and use MMDUtility. will there be an update soon?

It's unofficial because I forked to the latest version, but I tried to fix it.
I hope the official one will respond someday.
https://github.com/PTOM76/MMDPluginInstallManager

i tried unsuccessfully to install it into 9.26 is there a later version that works.


enable persistent uefi state support#170

Does it mean every VM need an extra 12 MB storage to persist uefi? Or is this configure at vm level as well?

Does it mean every VM need an extra 12 MB storage to persist uefi? Or is this configure at vm level as well?

This PR here is just the base config for the cluster. It has to be enable at the vm level to be in effect (and create that state PVC). You do that in the VM domain spec like this:
        firmware:
          bootloader:
            efi:
              persistent: true

Which btw currently breaks cloneing - you cant clone a VM with persistet state.

this now also add observability to ACM support#135

LGMT


Update the preview page title to include the word "Preview"

Code is in handlers/handle,admin,pages,preview.php
It just calls CBPage::render($model);
There is a title property on some pages (that is deprecated). We could alter the title before rendering, but some pages may not support the title property.
This sort of leads us to a place where this whole concept of pages might be in a state of flux. We want something simpler and I'm debating with myself about whether it will every be a good idea to fix this issue.


Gnome Nautilus not recognizing hardware keys for SFTP.

Describe the bug
I utilize a Yubikey 5 to connect ssh and sftp. While I am able to connect via command line, nautilus gives me "permission denied" errors.
Steps To Reproduce
Steps to reproduce the behavior:

Launch Nautilus.
Try to connect to sftp://ip
Get a permission error.

Expected behavior
Nautilus uses gnupg agent's ssh support.
Additional context
I use this for Yubikey ssh support:
services.udev.packages = [ pkgs.yubikey-personalization ];

programs.gnupg.agent = {
	enable = true;
	enableSSHSupport = true;
};

Possible related Stackoverflow question and Debian discussion with a fix
Also I am using Sway, not Gnome.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.1, NixOS, 24.05 (Uakari), 24.05.20240319.b06025f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/store/zaza7mgggz4m5h6z18kajabf4wciaj47-source

Add a :+1: reaction to issues you find important.

please test it with services.yubikey-agent.enable = true;

have you logged out and logged in after setting it? If so have you tried ssh-add -K?

I have the same issue but with an openpgp smartcard not with a YubiKey. THis does not seem to be Yubikey related.


Spec for Formatted Copying

Summary of the Pull Request
This is the spec that goes into what we do with HTML copy once we set the default copy behavior to plain text.

References
#4191

PR Checklist

[ ] Closes #xxx
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

I have a strong distaste for changing our default because of a handful of applications that lack "paste plain text" as an option. It's not a hill I'm willing to die on, but look:

people say they want plain text, they can have it (via a couple steps)
pasting into a terminal already strips HTML/RTF
pasting into a rich document preserves rich formatting
pasting into a spreadsheet auto-strips html/rtf
pasting into a preformatted code block or code editor auto-strips html/rtf
people are going to be stuck in the mid 1900s forever, and we just look like we simply don't support html copy (because nobody's going to read our json file, let's be honest)

I have a strong distaste for changing our default because of a handful of applications that lack "paste plain text" as an option. It's not a hill I'm willing to die on, but look:

people say they want plain text, they can have it (via a couple steps)
pasting into a terminal already strips HTML/RTF
pasting into a rich document preserves rich formatting
pasting into a spreadsheet auto-strips html/rtf
pasting into a preformatted code block or code editor auto-strips html/rtf
people are going to be stuck in the mid 1900s forever, and we just look like we simply don't support html copy (because nobody's going to read our json file, let's be honest)

That seems fair. So then the keybinding arg would default to "true" or "rtf, html, plain"? (this should be in the spec)

(also maybe worth adding to the spec)
I was wondering "what if somebody wants to just copy a specific aspect of the formatting like the font size/family?". I feel that the main annoyance with html copy is the following scenario:

I'll have a dark background color but acrylic tuned to make it legible
I then copy it to MSFT Word
since acrylic can't be copied over (and that's just impossible to do) it may no longer be legible
But if that's the case, and all I really wanted was the font family, then that should be something we allow as a part of #2131 later. For now, the user would just have to paste with the current formatting, then tweak to make it look better, which I feel is fair.

I am strongly of the opinion that our default should be plain text copy. The votes were overwhelming towards plain text and other terminal emulators behave in this way (including conhost). We cannot guarantee that the receiving application will give you the ability to format your pasted text (Microsoft Teams for example).
To address your concern about discoverability, if it's a global setting, it would be easy to find in a settings UI. We could also ship either the key binding or the global setting inside settings.json.

We could always support true == ["html", "rtf", "plain"], so the user could specify both? though the naming might be confusing then

I really like this. So then the following two keybindings would be deserialized to be the same thing:
{"command": {"action": "copy", "formats": ["html","rtf","plain"]}, "keys": "ctrl+a"}

and
{"command": {"action": "copy", "formats": true}, "keys": "ctrl+a"}

I'd really love if we could have the "default" in userDefaults.json (the one that's created for new settings files) that includes all of ["html", "rtf", "plain"] by default, with a note that the user can remove whatever formats they want. That way, it's immensly more discoverable that those are options, and that they're trivial to opt out of.

Also agree (this should go in the spec)

I addressed @zadjii-msft's nits as well as added @carlos-zamora's comment to the Future Considerations section. :)

I addressed @zadjii-msft's nits as well as added @carlos-zamora's comment to the Future Considerations section. :)

The main thing holding me back is still that the GitHub issues aren't linked. That makes things like this easier to track.


RuntimeError: Error(s) in loading state_dict for CifarResNeXt:

When I try to run test.py , I got this:
Traceback (most recent call last):
  File "/home/ubuntu/bigdisk/part1/resnext.pytorch/test.py", line 114, in <module>
    test()
  File "/home/ubuntu/bigdisk/part1/resnext.pytorch/test.py", line 79, in test
    net.load_state_dict(loaded_state_dict)
  File "/home/ubuntu/anaconda3/envs/resnext/lib/python2.7/site-packages/torch/nn/modules/module.py", line 845, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for CifarResNeXt:
	Missing key(s) in state_dict: "conv_1_3x3.weight", "bn_1.running_var", "bn_1.bias", "bn_1.weight", "bn_1.running_mean", "stage_1.stage_1_bottleneck_0.conv_reduce.weight", "stage_1.stage_1_bottleneck_0.bn_reduce.running_var", "stage_1.stage_1_bottleneck_0.bn_reduce.bias", "stage_1.stage_1_bottleneck_0.bn_reduce.weight", "stage_1.stage_1_bottleneck_0.bn_reduce.running_mean", "stage_1.stage_1_bottleneck_0.conv_conv.weight", "stage_1.stage_1_bottleneck_0.bn.running_var", "stage_1.stage_1_bottleneck_0.bn.bias", "stage_1.stage_1_bottleneck_0.bn.weight", "stage_1.stage_1_bottleneck_0.bn.running_mean", "stage_1.stage_1_bottleneck_0.conv_expand.weight", "stage_1.stage_1_bottleneck_0.bn_expand.running_var", "stage_1.stage_1_bottleneck_0.bn_expand.bias", "stage_1.stage_1_bottleneck_0.bn_expand.weight", "stage_1.stage_1_bottleneck_0.bn_expand.running_mean", "stage_1.stage_1_bottleneck_0.shortcut.shortcut_conv.weight", "stage_1.stage_1_bottleneck_0.shortcut.shortcut_bn.running_var", "stage_1.stage_1_bottleneck_0.shortcut.shortcut_bn.bias", "stage_1.stage_1_bottleneck_0.shortcut.shortcut_bn.weight", "stage_1.stage_1_bottleneck_0.shortcut.shortcut_bn.running_mean", "stage_1.stage_1_bottleneck_1.conv_reduce.weight", "stage_1.stage_1_bottleneck_1.bn_reduce.running_var", "stage_1.stage_1_bottleneck_1.bn_reduce.bias", "stage_1.stage_1_bottleneck_1.bn_reduce.weight", "stage_1.stage_1_bottleneck_1.bn_reduce.running_mean", "stage_1.stage_1_bottleneck_1.conv_conv.weight", "stage_1.stage_1_bottleneck_1.bn.running_var", "stage_1.stage_1_bottleneck_1.bn.bias", "stage_1.stage_1_bottleneck_1.bn.weight", "stage_1.stage_1_bottleneck_1.bn.running_mean", "stage_1.stage_1_bottleneck_1.conv_expand.weight", "stage_1.stage_1_bottleneck_1.bn_expand.running_var", "stage_1.stage_1_bottleneck_1.bn_expand.bias", "stage_1.stage_1_bottleneck_1.bn_expand.weight", "stage_1.stage_1_bottleneck_1.bn_expand.running_mean", "stage_1.stage_1_bottleneck_2.conv_reduce.weight", "stage_1.stage_1_bottleneck_2.bn_reduce.running_var", "stage_1.stage_1_bottleneck_2.bn_reduce.bias", "stage_1.stage_1_bottleneck_2.bn_reduce.weight", "stage_1.stage_1_bottleneck_2.bn_reduce.running_mean", "stage_1.stage_1_bottleneck_2.conv_conv.weight", "stage_1.stage_1_bottleneck_2.bn.running_var", "stage_1.stage_1_bottleneck_2.bn.bias", "stage_1.stage_1_bottleneck_2.bn.weight", "stage_1.stage_1_bottleneck_2.bn.running_mean", "stage_1.stage_1_bottleneck_2.conv_expand.weight", "stage_1.stage_1_bottleneck_2.bn_expand.running_var", "stage_1.stage_1_bottleneck_2.bn_expand.bias", "stage_1.stage_1_bottleneck_2.bn_expand.weight", "stage_1.stage_1_bottleneck_2.bn_expand.running_mean", "stage_2.stage_2_bottleneck_0.conv_reduce.weight", "stage_2.stage_2_bottleneck_0.bn_reduce.running_var", "stage_2.stage_2_bottleneck_0.bn_reduce.bias", "stage_2.stage_2_bottleneck_0.bn_reduce.weight", "stage_2.stage_2_bottleneck_0.bn_reduce.running_mean", "stage_2.stage_2_bottleneck_0.conv_conv.weight", "stage_2.stage_2_bottleneck_0.bn.running_var", "stage_2.stage_2_bottleneck_0.bn.bias", "stage_2.stage_2_bottleneck_0.bn.weight", "stage_2.stage_2_bottleneck_0.bn.running_mean", "stage_2.stage_2_bottleneck_0.conv_expand.weight", "stage_2.stage_2_bottleneck_0.bn_expand.running_var", "stage_2.stage_2_bottleneck_0.bn_expand.bias", "stage_2.stage_2_bottleneck_0.bn_expand.weight", "stage_2.stage_2_bottleneck_0.bn_expand.running_mean", "stage_2.stage_2_bottleneck_0.shortcut.shortcut_conv.weight", "stage_2.stage_2_bottleneck_0.shortcut.shortcut_bn.running_var", "stage_2.stage_2_bottleneck_0.shortcut.shortcut_bn.bias", "stage_2.stage_2_bottleneck_0.shortcut.shortcut_bn.weight", "stage_2.stage_2_bottleneck_0.shortcut.shortcut_bn.running_mean", "stage_2.stage_2_bottleneck_1.conv_reduce.weight", "stage_2.stage_2_bottleneck_1.bn_reduce.running_var", "stage_2.stage_2_bottleneck_1.bn_reduce.bias", "stage_2.stage_2_bottleneck_1.bn_reduce.weight", "stage_2.stage_2_bottleneck_1.bn_reduce.running_mean", "stage_2.stage_2_bottleneck_1.conv_conv.weight", "stage_2.stage_2_bottleneck_1.bn.running_var", "stage_2.stage_2_bottleneck_1.bn.bias", "stage_2.stage_2_bottleneck_1.bn.weight", "stage_2.stage_2_bottleneck_1.bn.running_mean", "stage_2.stage_2_bottleneck_1.conv_expand.weight", "stage_2.stage_2_bottleneck_1.bn_expand.running_var", "stage_2.stage_2_bottleneck_1.bn_expand.bias", "stage_2.stage_2_bottleneck_1.bn_expand.weight", "stage_2.stage_2_bottleneck_1.bn_expand.running_mean", "stage_2.stage_2_bottleneck_2.conv_reduce.weight", "stage_2.stage_2_bottleneck_2.bn_reduce.running_var", "stage_2.stage_2_bottleneck_2.bn_reduce.bias", "stage_2.stage_2_bottleneck_2.bn_reduce.weight", "stage_2.stage_2_bottleneck_2.bn_reduce.running_mean", "stage_2.stage_2_bottleneck_2.conv_conv.weight", "stage_2.stage_2_bottleneck_2.bn.running_var", "stage_2.stage_2_bottleneck_2.bn.bias", "stage_2.stage_2_bottleneck_2.bn.weight", "stage_2.stage_2_bottleneck_2.bn.running_mean", "stage_2.stage_2_bottleneck_2.conv_expand.weight", "stage_2.stage_2_bottleneck_2.bn_expand.running_var", "stage_2.stage_2_bottleneck_2.bn_expand.bias", "stage_2.stage_2_bottleneck_2.bn_expand.weight", "stage_2.stage_2_bottleneck_2.bn_expand.running_mean", "stage_3.stage_3_bottleneck_0.conv_reduce.weight", "stage_3.stage_3_bottleneck_0.bn_reduce.running_var", "stage_3.stage_3_bottleneck_0.bn_reduce.bias", "stage_3.stage_3_bottleneck_0.bn_reduce.weight", "stage_3.stage_3_bottleneck_0.bn_reduce.running_mean", "stage_3.stage_3_bottleneck_0.conv_conv.weight", "stage_3.stage_3_bottleneck_0.bn.running_var", "stage_3.stage_3_bottleneck_0.bn.bias", "stage_3.stage_3_bottleneck_0.bn.weight", "stage_3.stage_3_bottleneck_0.bn.running_mean", "stage_3.stage_3_bottleneck_0.conv_expand.weight", "stage_3.stage_3_bottleneck_0.bn_expand.running_var", "stage_3.stage_3_bottleneck_0.bn_expand.bias", "stage_3.stage_3_bottleneck_0.bn_expand.weight", "stage_3.stage_3_bottleneck_0.bn_expand.running_mean", "stage_3.stage_3_bottleneck_0.shortcut.shortcut_conv.weight", "stage_3.stage_3_bottleneck_0.shortcut.shortcut_bn.running_var", "stage_3.stage_3_bottleneck_0.shortcut.shortcut_bn.bias", "stage_3.stage_3_bottleneck_0.shortcut.shortcut_bn.weight", "stage_3.stage_3_bottleneck_0.shortcut.shortcut_bn.running_mean", "stage_3.stage_3_bottleneck_1.conv_reduce.weight", "stage_3.stage_3_bottleneck_1.bn_reduce.running_var", "stage_3.stage_3_bottleneck_1.bn_reduce.bias", "stage_3.stage_3_bottleneck_1.bn_reduce.weight", "stage_3.stage_3_bottleneck_1.bn_reduce.running_mean", "stage_3.stage_3_bottleneck_1.conv_conv.weight", "stage_3.stage_3_bottleneck_1.bn.running_var", "stage_3.stage_3_bottleneck_1.bn.bias", "stage_3.stage_3_bottleneck_1.bn.weight", "stage_3.stage_3_bottleneck_1.bn.running_mean", "stage_3.stage_3_bottleneck_1.conv_expand.weight", "stage_3.stage_3_bottleneck_1.bn_expand.running_var", "stage_3.stage_3_bottleneck_1.bn_expand.bias", "stage_3.stage_3_bottleneck_1.bn_expand.weight", "stage_3.stage_3_bottleneck_1.bn_expand.running_mean", "stage_3.stage_3_bottleneck_2.conv_reduce.weight", "stage_3.stage_3_bottleneck_2.bn_reduce.running_var", "stage_3.stage_3_bottleneck_2.bn_reduce.bias", "stage_3.stage_3_bottleneck_2.bn_reduce.weight", "stage_3.stage_3_bottleneck_2.bn_reduce.running_mean", "stage_3.stage_3_bottleneck_2.conv_conv.weight", "stage_3.stage_3_bottleneck_2.bn.running_var", "stage_3.stage_3_bottleneck_2.bn.bias", "stage_3.stage_3_bottleneck_2.bn.weight", "stage_3.stage_3_bottleneck_2.bn.running_mean", "stage_3.stage_3_bottleneck_2.conv_expand.weight", "stage_3.stage_3_bottleneck_2.bn_expand.running_var", "stage_3.stage_3_bottleneck_2.bn_expand.bias", "stage_3.stage_3_bottleneck_2.bn_expand.weight", "stage_3.stage_3_bottleneck_2.bn_expand.running_mean", "classifier.bias", "classifier.weight".

Process finished with exit code 1

Hey! I have fixed the problem. It turns out that the code to make it compatible with old pytorch weights has made it incompatible with the new ones. Thanks for pointing it out :)


Remove references to archive-primary.cloudera.com

archive-primary.cloudera.com has not usable by external users for a few months now.

Closing in favour of another one


kops Karpenter Documentation Change

Is an existing page relevant?
https://karpenter.sh/preview/getting-started-with-kops/#create-a-cluster
What karpenter features are relevant?
kops integration
How should the docs be improved?
The docs should have the section about "New Cluster" implementation of Karpenter removed because Karpenter does not have a flag for --instance-manager.
Documentation Reference:
https://karpenter.sh/preview/getting-started-with-kops/#create-a-cluster
Error Log:
Error: unknown flag: --instance-manager

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

I assume you meant that kOps does not have the flag --instance-manager.
The flag is not visible unless you enable the Karpenter feature flag. Also make sure that your kops version is new enough. There has been a lot of fixes in karpenter/kops lately, so recommend using a snapshot version if you can.

IIUC from @olemarkus's comment we can close. Feel free to reopen if I'm wrong.

The feature flag was enabled by exporting the env variable KOPS_FEATURE_FLAGS=Karpenter. I set the flag, ran the following...
kops create cluster --name <DNS> --cloud aws --networking=amazonvpc --zones=us-east-1a --master-count=1 --yes --state=s3://<endpoint> --instance-manager=karpenter
and then the following error was returned...
Error: unknown flag: --instance-manager
Am I missing a step?

You need 1.24. I recommend using the CI version as it contains a host of fixes for karpenter: https://kops.sigs.k8s.io/contributing/test_versions/

So, this deploys on version1.24, but I can't interface with the cluster via kubectl? I haven't got any warnings or errors on my output logs and I've exported the kubeconfig like so...
./kops export kubeconfig <dns_name>.com
error I got back when running a
kubectl get no
Unable to connect to the server: dial tcp <ip_addr>: i/o timeout
and when running an update to set configs I get...
Error: error listing nodes in cluster: Get "https://api.<dns_name>.com/api/v1/nodes": dial tcp <ip_addr>:443: i/o timeout
Am I missing something in the configuration steps, I followed the instructions on the link you sent and everything seems to be deployed from my AWS console, just unable to run the kubectl CLI commands against the master node

You can check the logs of the unit called kops-configuration.
Feel free to drop by slack if you need help with this.

I think I may have just gotten it back up. I think it just took a while to propagate on the Route53 side of things. I will still join the Slack though just in case if I have anymore issues later down the road.


teleport-if-outside-border feature issue

Spark link
https://spark.lucko.me/atZIGA3bI4
Expected behavior
To teleport the player back to spawn or back in the world border when teleporting outside the world border.
Observed/Actual behavior
When I used a ender pearl outside the border it just displayed this weird void rendering issue: https://gyazo.com/5e815cbae89ad3cd59f0c894ad87fdc4
Steps/models to reproduce

Enable: teleport-if-outside-border in purpur.yml
Throw a ender pearl outside the world border, while not an operator

Purpur version
git-purpur-1732 1.19
Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
This worked back in 1.18 but sadly not 1.19.

https://user-images.githubusercontent.com/43185817/180669176-67ac4d6a-1abb-4345-bd43-63445be656f6.mp4
Could not reproduce.

javaw_P9eoRZ0P7j.mp4
Could not reproduce.

Where you not oped? It'll let you bypass as a op

javaw_P9eoRZ0P7j.mp4
Could not reproduce.

Were you not oped? It'll let you bypass as a op

I was not op'd. You can see I attempted to run the /op command and got an error, as well as the /lp command which states I have not set any permissions.

javaw_P9eoRZ0P7j.mp4
Could not reproduce.

Were you not oped? It'll let you bypass as a op

I was not op'd. You can see I attempted to run the /op command and got an error, as well as the /lp command which states I have not set any permissions.

Whoops, missed that, thanks for your time!