Multi-cluster app is loading every template and version before bringing up apps page

Version - 2.2 master 1/30
Steps to reproduce (least amount of steps as possible):

Add a catalog that has lots of templates
Go to Multi-Cluster Apps page

Result:  Page looks like it hangs because it's loading every single app and every single template of the app before bringing up the App page.  So it consistently looks like it's broken.  Please load page same way we load the page in the Projects section.

Version: Master 2.2 (2/1/19)
Confirmed fix. Now when you load the MC Apps page it will launch instantly; inspected http and I don't see us trying to load all the catalogs. Now this loading is only happening when we launch catalog apps, as expected and performance here is decent. I smoke tested this area and tried to narrow down catalogs by category/catalog and all at once and my browser did not hang too long.
The performance is now the same as when we launch catalog apps at the project level.


Support referencing matched tokens

The idea is to handle generic cases that are needed if we want replaCy to be an option for rule-based GEC.
Here is a snippet of a match_dict with examples of this
{
    "lt-example": {
        "patterns": [
            {
                "LOWER": {
                    "IN": [
                        "have",
                        "has"
                    ]
                }
            },
            {
                "TAG": {
                    "IN": [
                        "VBD",
                        "VBP",
                        "VB"
                    ]
                }
            },
            {
                "TAG": {
                    "NOT_IN": [
                        "VBG"
                    ]
                }
            }
        ],
        "suggestions": [
            [
                {
                    "REF": 0
                },
                {
                    "REF": 1,
                    "INFLECTION": "VBG"
                },
                {
                    "REF": 2
                }
            ]
        ]
    },
    "extract-revenge": {
        "patterns": [
            {
                "LEMMA": "extract",
                "TEMPLATE_ID": 1
            },
            {
                "LOWER": "revenge"
            }
        ],
        "suggestions": [
            [
                {
                    "TEXT": "exact",
                    "FROM_TEMPLATE_ID": 1
                },
                {
                    "REF": 1
                }
            ]
        ],
        "message": "Possible agreement error -- use past participle here"
    }
}

That first pattern is my attempt to translate to replaCy the following LT pattern:
<pattern>
 <token regexp="yes">has|have</token>
 <marker>
   <token postag="VBD|VBP|VB" postag_regexp="yes">
     <exception postag="VBN|NN:U.*|JJ.*|RB" postag_regexp="yes"/>
   </token>
 </marker>
 <token><exception postag="VBG"/></token>
</pattern>
<message>
  Possible agreement error -- use past participle here:
  <suggestion><match no="2" postag="VBN"/></suggestion>.
</message>

The second pattern is an attempt to redo the extract revenge pattern using this proposed syntax. I am not saying we'd want that change (it doesn't produce a minimal diff).

This would also allow us to handle this inclusivity match


[0.12.0.x] update COPYRIGHT_YEAR

As https://github.com/dashpay/dash/pull/849 is WIP I'll split this out

ack :)


Refresh writing policies in Go

[ ] 01-intro-go.md
[ ] 02-scaffold.md
[ ] 03-policy-settings.md
[ ] 04-validation.md
[ ] 05-e2e-tests.md
[ ] 06-logging.md
[ ] 07-automate.md
[ ] 08-distribute.md
[ ] 09-validation-with-queries.md

Some relevant discussion from the Kubernetes Slack to take account of: https://kubernetes.slack.com/archives/C01T3GTC3L7/p1701969036914439


Theme css not loading - default is loading instead

I've followed the theme instructions to create a theme called nova:
app/assets/stylesheets/pageflow/themes:
nova/variables.scss
nova.scss
default.scss
The default.scss is for added plugins:

pageflow-linkmap-page (+ pageflow-external-links)
pageflow-text-page

The css and css.gz files exist after deploy, which includes precompile.

The theme is set to nova for all accounts:

However, the site pulls in the default css on preview:

I've deleted the Rails-generated application.scss.
variables.scss is rather simple:
$theme-name: "nova";

// Set font faces
@font-face {
  font-family: Graphik;
  font-weight: normal;
  font-style: normal;
  src: font-url('GraphikCondensed-Medium-Web.woff')  format("woff"),
        font-url('GraphikCondensed-Medium-Web.woff2')  format("woff2");
}

@font-face {
  font-family: Graphik;
  font-weight: bold;
  font-style: normal;
  src: font-url('GraphikCondensed-Bold-Web.woff')  format("woff"),
        font-url('GraphikCondensed-Bold-Web.woff2')  format("woff2");
}

@font-face {
  font-family: Graphik;
  font-weight: normal;
  font-style: italic;
  src: font-url('Graphik-RegularItalic-Web.woff')  format("woff"),
        font-url('Graphik-RegularItalic-Web.woff2')  format("woff2");
}

// $main-color: #e84d2c;
// $main-color-dark: #b14a08;
// $standard-font: "SourceSansPro";

// For a full list of available variables see:
//
//   http://codevise.github.io/pageflow/theme/master/
//

$page-background-color: #005689;
$page-shadow-color: #005689;
$standard-font: "Graphik";
$standard-font-size: 18px;

Thanks for your assistance.

The theme configured in the "Edit account" form is only used for new entries. Maybe the entry you are looking at was created before you changed the default theme in the account? To change the theme of an existing entry, you have to enable the "Editor theme selection" feature flag and go to "Title and Options > Appearance > Theme" inside the editor.

Ah, ok. It now pulls in nova.....css, and it sees the font declarations, but the variables don't seem to be having any effect - the font is still SourceSansPro

Hard to tell. Are you seeing any mentions of Graphik in the generated stylesheet? $standard-font should be the right variable to set. Do you import variables before pageflow/themes/default/base?

It was an order thing. I'm used to the cascade and putting overrides later. Thanks.


Capstone Project

In this project, I completed the following parts:

Use semantic HTML tags.
Apply best practices in HTML code.
Use CSS selectors correctly.
Use the CSS box model.
Use Flexbox to place elements on the page.
Use images and backgrounds to enhance the look of a website.
Demonstrate ability to create UIs adaptable to different screen sizes using media queries.
Use GitHub Pages to deploy web pages.
Apply JavaScript best practices and language style guides in code.
Use JavaScript to manipulate DOM elements.
Use JavaScript events.
Use objects to store and access data.

@MozamelJawad, Great job on putting in a lot of effort into this project! However, during the review process, I noticed that you made a new commit, which is not recommended. It's best to ensure that all updates and changes are made before requesting a review. This helps maintain a clear and organized review process.


Fix: delete api check of voxelization on 200

Thanks for your contribution and we appreciate it a lot.
1. Motivation
Modify voxelization api gtest abort supported platform
2. Modification
Voxelization do not support 200 platforms

此修改已在通过其他pr合入。


modular interface-based installation configurations

NeuroConv has many dependencies that are specific to particular data formats. We have been working on how to make imports modular. This works right now, but we might end up with a problem where different libraries have conflicting dependencies, so it would not be possible to install all of them. Therefore, I think it is also important to make installation modular. Currently, we have a few different installation options. You can run:
pip install neuroconv
for the minimal dependencies and
pip install neuroconv[full]
for the full dependencies. I propose a solution where you can specify modalities during install and pip will know to install the dependencies specifically for those modalities, e.g.:
pip install neuroconv[openephys]
would install the minimum plus pyopenephys. A user would also be able to specify multiple dependencies, e.g.:
pip install neuroconv[spikeglx,kilosort,phy,deeplabcut]
and the environment would be set up with the necessary libraries for those data sources.
In order to accomplish this, we will need to formally define the requirements of each type of source data. One way we can do this is to have requirements.txt files in each data type directory. For instance:
neuroconv/src/neuroconv/datainterfaces/behavior/deeplabcut/requirements.txt would be:
dlc2nwb>=0.2

The setup.py file would use glob to iterate through all of the datainterface modules and create a extra_requires dict for each source data type.

Another approach could be to still only have one file at the top level (say, extra_requires.json or extra_requires.pkl) and what is saved within is a dictionary of format keywords and list of specific dependencies as values.
Main benefit would be readability as it would make it really easy to compare at a glance the dependencies across each formats - with the above approach I'd have to open separate tabs for each file on the web interface (on top of having to navigate down to each file), or similarly open each file separately (again, after navigating) on my local clone.

I would rather not use pickle files. Not transparent to users and no version control. json is much better than pickle for this.
neo uses a dict in the setup.py file: https://github.com/NeuralEnsemble/python-neo/blob/50abfbce832edb1c0f8364ac34c8a6442e1a3edf/setup.py#L10-L18
I think I would still prefer the individual requirements.txt files. I know this is more work, but I'd like to go for more of a plugin style architecture where DataInterfaces can be contributed without altering any of the core files.

Having separate requirements.txt files also allows for the option to install these options via `pip install -r path/to/requirements.txt

I really favor having a centralized place to list all the dependencies. I think that is easier for maintainers to get an overall sense of how the dependencies relate to each others easier to modify and test. It does not seem a big cost to me for developers to go and modify the centralized file -which is the only non sub-module file that should be modified- after they have done a change. Maybe I am missing something.
More importantly, I think that the centralized approach is more in line with where packing is going in the python community. My feeling is that since PEP 621 the goal is to replace both setup.py and requirements.txt with a single specification in the toml file (this remove some problems that existed for build specification that you can read here). So, the community wants to move away from setup.py and requierements.txt. The standard way of specifying extra-dependencies in the toml file is in this link and you can see this is centralized. As an example of this trend the popular poetry library uses the toml file for package configuration and adds the extras in the centralized fashion.
What I see in #100 is that following the approach with multiple requirements.txt files is causing us to add further machinery to the setup.py but the latter is falling out of favor in the community. While the toml standard supports dynamically building the metadata (i.e. what we are doing with setup in #100 to add the extras during the build) it is not clear to me that we will able to export this approach cleanly or easy to toml if it does fulfill its role of becoming the standard and we want to migrate later.
If want still want to go the distributed approach as @bendichter is proposing I propose a gradual approach to this change.
First we should migrate to the new standard toml approach with a centralized specification of extras and then, only after that, we should a the dynamically build specification with files distributed across the sub-packages. I also think this will be easier to review in PRs as first we will be introducing the testing for multiple installations and a more fine-grained specifications of the dependencies and then their dynamic construction in another PR. Right now #100 is doing the two at the same time which I think is too big of a change and you can see that in the diff.

The first is that I envisioned this as sort of a plugin architecture where contributions of new modality DataInterfaces required no modifications to core or packaging code. This would make PRs more modular and it would enable us (and others) to create a DataInterface in a separate directory, importing base classes from NeuroConv, but never needing to make any modifications to the NeuroConv library at all.

Thank you, I understand what you mean by plug-in now. They can develop things independently and plug-back seamlessly if they want to. With the current approach they will copy the data interface to the appropriate place and have to modify any dependency that they added.

The second reason is that it enables running pip install -r path/to/requirements.txt on any DataInterface requirements file. I'm not sure if this feature would ever be needed though since you could always just run pip install .[modality].

Yep, I think we offer the same functionality with the  pip install .[modality].

I do love the pyproject.toml and it's nice to see more people advocating it. I'd be more than happy to swap other parts of the setup into there!

Another example in a plugin library:
https://github.com/imageio/imageio/blob/master/setup.py

I do believe this was closed by #98 and others from around that time


Support Azure AD auth for Cosmos DB

Description
Updated the bindings/azure/cosmosdb and state/azure/cosmosdb components to support auth via Azure AD.
If masterKey is present in the metadata, that's used first. Otherwise, it tries authenticating using Azure AD, including using a service principal (azureClientId and azureClientSecret), a certificate, or MSI.
Issue reference
See #1103
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[ ] Created/updated tests

I cannot do this because I do not have access to the Azure account used by dapr developers

[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@ItalyPaleAle happy to see it, please fix CI.

@daixiang0 the failed CI is not due to this PR, as I did not touch MQTT. Not sure if it's a previous commit that caused the error or just some flakiness in the test.

For this case, you can re-commit to trigger CI re-run :)

@CodeMonkeyLeet I was thinking this could be tracked as part of the umbrella issue #1103. Do you want me to create a separate issue for each one?

@CodeMonkeyLeet I was thinking this could be tracked as part of the umbrella issue #1103. Do you want me to create a separate issue for each one?

#1103 tracks the general issue to be fixed in dapr/components-contrib, I'm asking for an issue in dapr/docs (or better yet, the documentation PR in dapr/docs) per:

[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

The PR template includes this item because Dapr would like the documentation to be up-to-date with the new features included in each release (in this case, the ability to use Azure AD auth with the CosmosDB) and that's at the granularity of what has been merged into the release.

Sorry I missed the part where you were referring to docs. I will open an issue.


Migration stuff

I tried my best, but, god, VSCode is weird and unnatural. I used Eclipse instead (installed for this purpose), except Eclipse provides literally nothing in debugging or lints to help. I tried to make this as error-free as possible, but something probably snuck in. This was painful. I apologize in advance for any debugging work you have to do because of this.
1st commit

Delete 5 unneeded files

2nd commit (will probably fuck up everything maybe)

I had to add the .settings for it to even try to build (sorry about the .classpath change)
Updated the Android Studio and Xtext gradle plugins
Updated buildTools 26.0.2 -> 29.0.3
Updated org.eclipse.xtend:org.eclipse.xtend.lib 2.9.2 -> 2.21.0 (changelog)
Updated gradle wrapper to 6.4

3rd commit

Migrated support libraries to AndroidX (had to do this manually, so check to see if done correctly via build test)

4th commit

Migrated Glide 3.x to 4.x the best I could, here's documentation in case something went wrong (https://github.com/bumptech/glide/releases, https://bumptech.github.io/glide/doc/migrating.html)

Thank you so much for going to the effort, and sorry that it was painful. I hope that after the teething problems, you will get to experience the simpler (and in my opinion, beautiful) code that Xtendroid provides.

PS: if you need assistance or would like to chat to ask questions about the code or setup, feel fee to get in touch with me, I would be happy to assist. Details here: https://tobykurien.com/contact/

I am getting the following compile error (using openJDK 13.0.1):
* What went wrong:
A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
   > 'java.util.List com.android.build.gradle.api.BaseVariant.getOutputs()'

@tobykurien The .iml files and local.properties are automatically generated on everyone's computers when they open a project, so they aren't needed in Git.
The sample local.properties isn't exactly accurate, I think. It would look more like this:
## This file must *NOT* be checked into Version Control Systems,
# as it contains information specific to your local configuration.
#
# Location of the SDK. This is only used by Gradle.
# For customization when using a Version Control System, please read the
# header note.
#SUN-SAT MONTH DAY HH:MM:SS TIMEZONE YYYY
sdk.dir=C\:\\Users\\Sample\\AppData\\Local\\Android\\Sdk

I am getting the following compile error (using openJDK 13.0.1):
* What went wrong:
A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
   > 'java.util.List com.android.build.gradle.api.BaseVariant.getOutputs()'

Yeah, that's an issue I've been getting. It seems to be an issue with a dependency or plugin: https://github.com/JakeWharton/butterknife/issues/1130
https://medium.com/@ErikJhordanRey/migrate-to-new-android-plugin-for-gradle-3-6790e79c5f3f

There's no butterknife in this project, however I can tell you that this is the reason I kept using older Gradle and gradle plugin versions. This is the kind of error that happens when the gradle version and plugin version don't match. Try going back to older versions of gradle till it works

PS: I get past that error if I revert the gradle version. Then I end up with:
Could not resolve com.google.guava:guava:27.1-jre.
     Required by:
         project : > com.android.tools.build:gradle:3.6.3 > com.android.tools.analytics-library:crash:26.6.3
         project : > com.android.tools.build:gradle:3.6.3 > com.android.tools.lint:lint-gradle-api:26.6.3
         project : > com.android.tools.build:gradle:3.6.3 > com.android.tools.build:gradle-api:3.6.3
         project : > com.android.tools.build:gradle:3.6.3 > androidx.databinding:databinding-compiler-common:3.6.3
         project : > com.android.tools.build:gradle:3.6.3 > com.android.tools.build:builder:3.6.3 > com.android.tools:common:26.6.3
         project : > com.android.tools.build:gradle:3.6.3 > com.android.tools.build:builder:3.6.3 > com.android.tools.analytics-library:tracker:26.6.3

I would suggest upgrading one item at a time and compile, to make sure it still works, before upgrading the next item.

I cut out the second commit.

To test your changes, you can run ./gradlew assembleDebug from the command line in the project root directory.  This will ensure that you are testing the build configuration independent of any Eclipse or other IDE settings/issues.
If you do that, you'll see now that there's a new error, which may be related to the AndroidX stuff: AAPT: Attribute "actionBarSize" already defined with incompatible format. I think you can see now why I stuck with older versions that work :-) I'm not sure that there is any benefit to upgrading to AndroidX at this stage.

@tobykurien Oh god ok lol. I'll just do the deletion and glide updates then.

@tobykurien I couldn't even update Glide to 4, Studio was just throwing around all sorts of whack errors from things being wrongly undefined to other weird stuff. If you'd like to update Glide to 4 yourself (it's worth it though), here's the migration guide and the changelog (version 4.10.0 and up is AndroidX, so use 4.9.0).


The recommendation with Patches is confusing

The page (https://learn.microsoft.com/en-us/power-platform/alm/solution-layers-alm) mentions that "Using patches isn't recommended"

however, the page (https://learn.microsoft.com/en-us/power-platform/alm/form-alm#creating-a-new-form-and-making-customizations-using-patches-and-upgrades) lists a health ALM scenario with patches:

Are we supposed to leverage patches or not, is the dilemma, as these 2 articles listed above appear contradictory?

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

ID: 872daafd-cde6-ad76-fe9a-b44d5819d1e8
Version Independent ID: 3954ffcb-7d55-18f5-d3b9-0a01a0a53f92
Content: Maintaining healthy model-driven app form ALM with Power Apps - Power Platform
Content Source: power-platform/alm/form-alm.md
Service: power-platform
Sub-service: alm
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @davins-msft. This issue has been assigned to the doc author for review.


Various settings

We need a way to change a few compilation settings (for example to dump typed ASTs) or to feed specific arguments onto the command-line of the running program.
What we can do is adding a simple settings button next to the run button, which contains a text input and a few checkboxes. These would be used to insert some command-line flags for the compiler or the program.

Here is how the menu currently looks like:

light theme:

dark theme:

There are obviously a few more settings that would be nice to have, and the output tab is not yet designed to output those new dumps.


fix: remove traditional validation rule param types

Description
Fixes #6489
To add declare(strict_types=1). See #8072
There is no guarantee that a string will be passed, so declaring strict types may result in a TypeError.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

I don't see much point in thinking too much about @param.
The traditional validation rules assumed strings. They were originally designed to validate POST data, so the values are all strings. null is for when the key of the array data to validate is missing.
I don't want the traditional rules to be used and would like to remove them, but I am not sure if apps migrated from older CIs will not have any problems when switching to the strict rules..

Added docs.

Fair enough. This is basically a "pre-deprecation" change required so we can enact strict types.


<EMAIL_ADDRESS><EMAIL_ADDRESS>

we try rebuild robotjs with<EMAIL_ADDRESS><EMAIL_ADDRESS>is error

Fixed in 0.6.9!


Compiling grey-cuckoo on Guest VM (OSX 10.13)

Grey-cuckoo builds but no executable is created.
Without it every time I kextload mac-a-mal.kext the VM reboots.
Any help ?

There are a kext and a MachO binary would be compiled. Please notice mac-a-mal.kext was tested successfully on macOS <= 10.12. I will try on 10.13 soon and let you know. Btw, it would be great if you create this separate ticket on mac-a-mal.


Add OD javascript-client to dolphin-js

As a first step, the OD sources need to be copied into a special folder within the dolphin-js repository. The build and tests have to be put under control of gulp.

Build is working again, dolphin-js tests are ok.
So far OD tests run only locally. There is a compiler error for the test sources on the build server that I cannot reproduce locally. Will take care of that as part of #164


Change API updates

Describe the feature
Based on a request by the Kraken team, the following updates will need to be done

No API calls should be forced to be done on the hour or half hour
All data should be retrieved at most every 5 minutes. Current consumption data will not follow this process and continue as it does today
If an update fails, then it should update the following minute. If it fails again, then it should update 2 minutes after and so on
Update API client to set user agent to bottlecapdave-homeassistant-octopusenergy

Expected behaviour
See above
Use Case
N/A
Confirmation

[X] By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
[X] I am willing/able to help contribute to the solution of this feature

This has now been released as part of v9.2.0


added ansi escapes to highlight key parts of CLI session

This PR adds bold styling to the dream> prompt and to the outputs section. It also numbers each file that is outputted in preparation for a new feature that will allow users to refer back to previous outputs, use them as inputs, or recover their prompt settings. Only tested on Linux, but hopefully works on Mac and Windows too. Not dependent on readline library.

Thanks for testing! The same code was inadvertently left in another PR that I just merged, so I'll close this one.


feat(dpg): generate  comment

add LowLevelExampleComposer as the implementation of composing examples
insert the composing logic in LowLevelClientWriter
split comments generation for HLC protocol method and LLC, do not generate  for HLC protocol methods
for mock values, use default value, and then fallback to hard code one
add <...> around string-ish values to prompt for user input

resolve #2286
Description
Add your description here!
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

Preview PR on azure-sdk-for-net: https://github.com/Azure/azure-sdk-for-net/pull/29236
Also, the links to preview docs sites are listedin the PR.

Wow DPG really have long xml documents...

list of changes since last update:

share example composer between methods generation
preserve client path in library


Update z2ui5_cl_xml_view.clas.abap

Change on Element proportion_zoom_strategy. Added property zoomLevel
Reason: Gantt Chart with Container ToolBar: Toolbar has the feature zoomlevel and can now be forwarded to the axis

thank you! 🙏


Add a documentation note on troubleshooting slow inititalization

I ran into this issue, where I needed to remove the cache after a scope decrease.  A friend who tried Flow for the first time this week complained about Flow hanging before he figured out to exclude
node_modules.  I also noticed a few "Hang" tickets when I was searching for how to clear the cache.  Hope this helps mitigate that.

Oh.
So I was experimenting with the all=true because my friend complained about the comment flag in his files (I was trying to convince him to use Flow). I created this Doc PR when I discovered that the cache clear helped on a scope down grade.
Doh.
You can't really ignore node_modules, can you?  Obviously, this PR should NOT be merged.
Is it useful to mention that clearing the cache can help recover from a failed attempt to use --all?  If so, I'm happy to update the docs somewhere for that.
Otherwise, I'm just closing this.  Sorry for the noise.


[flutter_releases] Flutter Dev 2.2.0-10.1.pre Framework Cherrypicks

Scheduled Cherrypicks

[x] Engine cherrypicks

https://github.com/flutter/engine/pull/25595
https://github.com/flutter/engine/pull/25603 <- actual engine hash

[x] Crash reporter may be unable to report crashes in current RC branch

https://github.com/flutter/flutter/issues/80383
https://github.com/flutter/flutter/commit/b7214a9a43963a9c832793dd7831cbc3246c88c4

Known Pre-Submit Failures

Framework tests misc - https://github.com/flutter/flutter/issues/80463 this test will be fixed once this release is published to dev.

module_test_ios is failing with an add to app host runtime codesigning crash:
codesign_crash.txt
Exception Type:        EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes:       0x0000000000000032, 0x0000000107614000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace CODESIGNING, Code 0x2

The top of the log says This bot does not support codesigning
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8849863879990991456/+/steps/run_module_test_ios/0/stdout


partd serialization compatibility with pandas 1.3.0

I just noticed this type of failure cropping up on upstream tests.  This is an issue with partd -- I've opened up an issue over there https://github.com/dask/partd/issues/48

(just a note about the title: it's not a pyarrow issue, but a pandas compatibility issue ;))

I triggered a run here https://github.com/dask/dask/runs/2282926066 since the partd PR merged!

Ah, I'm checking things in https://github.com/dask/dask/pull/7534 too

https://github.com/dask/partd/pull/49 resolved the serialization issue we were encountering in the upstream build. I've opened up an issue for releasing partd over at https://github.com/dask/partd/issues/51

Good to close on this then I think.


Feature request: integrate vcf2maf

Hi there,
what is your opinion on integrating a vcf2maf tool such as this tool from MSKCC ?
I think in regard to many downstream applications that nowadays use maf tools as an input it would be a compelling option to include...
Curious what you think,
leiendeckerlu

Thanks for the suggestion and starting this discussion. In general, we're happy to make it easier to produce other standard file formats if they're useful. It sounds like this tool would be most useful integrated with the VEP portion of the pipeline since it uses it as input:
https://github.com/chapmanb/bcbio-nextgen/blob/8e2859ed80d501008e27fab493bf0f1871e922d5/bcbio/variation/effects.py#L118
The tool itself is present in bioconda, but looks like it might need some tweaking to not double call VEPand work directly from the output of bcbio.
It sounds like the first step would be to understand what it takes to convert the bcbio VEP VCF into a useful maf output, and then determine how that could fit into bcbio.
Hope this helps as a starting point and happy to help as you explore this. Thanks again.

Thanks for the very valuable background information how vcf2maf might work best with bcbio.
I will look into this and keep you posted on my progress.

I wrote some rough Python code which does the same conversions as vcf2maf without having to run it.
Some of the bits are tricky because frameshifts for example need to be called Frame_Shift_Ins or Frame_Shift_Del depending on whether there is an insertion or a deletion. I also put the various conversions in a YAML file for easier changes (in case someone finds it useful: https://gist.github.com/lbeltrame/27c21e4879e78f88ac568f3d10354836 - licensed under CC0; note Frame_Shift_ due to the reasons above).
I did this mainly because I don't well understand the code in vcf2maf (I was and am still not very good at Perl).


FEAT-#3043: allow pandas.DataFrame to be passed into merge and join functions

Signed-off-by: Anatoly Myachev<EMAIL_ADDRESS>
What do these changes do?

[ ] commit message follows format outlined here
[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[x] Resolves #3043
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date
[ ] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

@anmyachev what's the status of this PR?

I think @devin-petersohn was specifically against mixing Modin and pandas in that way, even though it's a "low hanging fruit" optimization in this case.
I feel that this should be better addressed by implementing https://github.com/modin-project/modin/issues/4605 and allowing the end user to easily "force" Modin to wrap certain pandas dataframe in this specific "small df" QueryCompiler.

@pyrito for now, this most likely will not be merged, @vnlitvinov is right.
By the way, I have an interesting case, which may not be very relevant to this task, but still.
This call works for pandas, but fails for modin because modin tries to initialize ray on the worker (if I remember correctly).
In this case, the following change helps: pd.Series... -> pandas.Series. However, this is more like a short-term workaround than a general solution. What can we do here?
import modin.pandas as pd

def agg_func(x):
    return int(pd.Series.count(x) > 0)

res = some_df.pivot_table(..., agg_func=agg_func)

@pyrito for now, this most likely will not be merged, @vnlitvinov is right.
By the way, I have an interesting case, which may not be very relevant to this task, but still.
This call works for pandas, but fails for modin because modin tries to initialize ray on the worker (if I remember correctly).
In this case, the following change helps: pd.Series... -> pandas.Series. However, this is more like a short-term workaround than a general solution. What can we do here?

import modin.pandas as pd

def agg_func(x):

    return int(pd.Series.count(x) > 0)

res = some_df.pivot_table(..., agg_func=agg_func)

@anmyachev this fails since the function is running on a ray worker - maybe we can wrap deployed functions with a function that just imports pandas as pd, so if the user tries to use pd inside an apply function (for example) it's scope will have pandas instead of Modin, and it'll work?

maybe we can wrap deployed functions with a function that just imports pandas as pd, so if the user tries to use pd inside an apply function (for example) it's scope will have pandas instead of Modin, and it'll work?

@pyrito for now, this most likely will not be merged, @vnlitvinov is right.
By the way, I have an interesting case, which may not be very relevant to this task, but still.
This call works for pandas, but fails for modin because modin tries to initialize ray on the worker (if I remember correctly).
In this case, the following change helps: pd.Series... -> pandas.Series. However, this is more like a short-term workaround than a general solution. What can we do here?
import modin.pandas as pd

def agg_func(x):

    return int(pd.Series.count(x) > 0)

res = some_df.pivot_table(..., agg_func=agg_func)

@anmyachev this fails since the function is running on a ray worker - maybe we can wrap deployed functions with a function that just imports pandas as pd, so if the user tries to use pd inside an apply function (for example) it's scope will have pandas instead of Modin, and it'll work?

The following example doesn't work.
def agg_func(x):

    return int(pandas.Series.count(x) > 0)

def wrapper(x):
    import pandas as pd
    return agg_func(x)

res = some_df.pivot_table(..., agg_func=wrapper)

if I understand correctly, pandas.Series type is determined when agg_func is defined, and not when it is called, so it will not work to redefine the scope.

@anmyachev We could modify the scope and replace modin.pandas with pandas by modifying the globals dict (although I'm not sure if we want to get into this level of meta-programming?)

We need to first decide on an approach.


Helping with maintaining the crate

Thanks for the wonderful crate.  As downstream users of this crate, some of the maintainers of the georust organization (incl. me) wanted to check if you need a hand with the maintenance of this crate.  We should be able to do our best with keeping the deps. up-to-date, esp. with yanked / vulnerable ones, but hopefully also help with improving the efficiency / adding useful functionalities to the crate.
If you are up for it, we would also be very happy to add this crate to the georust organization (which I believe you are already a part of) and make you the main author / admin, along with a couple of maintainers to help with keeping the crate updated.  Otherwise, if you wish to keep the crate as is, you may add a couple of us as maintainers here to help you (pls. see cc-ed contacts below).  Happy to help and apologies if the request sounds overbearing as that is definitely not the intention.
cc: @michaelkirk @urschrei

Thanks for reaching out!
I'm definitely not up to standards in regards to maintenance and would welcome if this crate could still be maintained and kept in a good shape!
I would welcome an inclusion into the georust organization and think it's a nice fit.
Unfortunately, I can't really promise any help with that. rstar has always been just a hobby project of mine for which finding motivation to work on became really hard once software development became my day job. But enough of that, I'll look into the mandatory steps that are involved in moving a repository.
Thanks again. This would mean a lot to me and hopefully also help all other downstream users.

I have initiated the transfer and given the core team access to the repository. I think someone of georust needs to approve of these changes?
Other than that I'm unsure how you handle uploads to crates.io . Please let me know if you have an idea on how to handle that.

Thanks @Stoeoef!

I'm definitely not up to standards in regards to maintenance and would welcome if this crate could still be maintained and kept in a good shape!
...
Unfortunately, I can't really promise any help with that. rstar has always been just a hobby project of mine for which finding motivation to work on became really hard once software development became my day job.

Even though rstar started as a hobby project for you, lots of people's work (including mine) now depends on it. So, firstly, thank you and congratulations on picking useful hobbies. =)
It's totally normal that circumstances change and that you might not have time nor energy. Sometimes it's temporary, sometimes it's permanent. I hope that one of the values that the georust community provides is an amount of resilience to the ebb and flow of "real life".
anyway, down to business:

I have initiated the transfer and given the core team access to the repository. I think someone of georust needs to approve of these changes?

Looks like someone has accepted. Welcome to your new home georust/rstar!

Other than that I'm unsure how you handle uploads to crates.io . Please let me know if you have an idea on how to handle that.

If you're not planning on actively doing releases, my preference is that you add 1 or 2 active user owners to crates.io I'm willing and available to do releases, but I confess I might not be the best fit since, as of yet, I've done very little work with the rstar internals. I'm just a user.
cd rstar
cargo owner --add michaelkirk

There are likely other folks willing/available who are more familiar with the crate - I'll leave it to them to volunteer.
Additionally, we always have a "team" owner for our crates. To that end, I've created the @georust/rstar-publishers team, you can add it like this:
cd rstar
cargo owner --add github:georust:rstar-publishers

See https://github.com/georust/meta/blob/master/GUIDELINES.md#crate-publishing-teams for the rationale of team/owners if you're aren't familiar.
Feel free to ask any questions!

Thanks @Stoeoef for accepting our offer!  will do our best to help you keep this crate up-to-date.
@michaelkirk Thanks for doing the ground work and creating the rstar-publishers team.   Pls. feel free to add me to the group;  I hope to provide a helping hand, and have a reasonable understanding of the algo. / heuristics used in the crate.

Pls. feel free to add me to the group

Done!

$ cargo owner --add github:georust:rstar-publishers
Updating crates.io index
error: failed to invite owners to crate rstar: api errors (status 200 OK): only members of a team can add it as an owner

I guess I need to be part of that group to be able to join. I have requested that access. In the meantime, I've added you (@urschrei  @rmanoka ) to the owner list, so you should be able to run that command on your own if you want to.

I guess I need to be part of that group to be able to join. I have requested that access.

Approved!

No worries – my ownership assignment worked and rstar-publishers is now an owner.

I think this issue can be closed now. Thank you @Stoeoef!


darwin with node v0.11

I don't know if this is the right place, however I just run:
npm install -g node-sass

and I get this:
 ~/workspace/tmp ∫ npm install node-sass -g
/Users/andrea/.npm-local/bin/node-sass -> /Users/andrea/.npm-local/lib/node_modules/node-sass/bin/node-sass

><EMAIL_ADDRESS>install /Users/andrea/.npm-local/lib/node_modules/node-sass
> node scripts/install.js

Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v2.1.1/darwin-x64-node-0.11/binding.node

The installation went ahead and everything seem fine.

Node 0.11 is unstable node.js branch, which is now superseded by 0.12 branch.
We do not provide binaries for unstable versions of node.js.
Solution: upgrade to node.js v0.12 (stable) or downgrade to v0.10.x (stable) version.
https://nodejs.org/


HEAD of develop crashes with UFS-GOCART

The HEAD of develop (aecee0c) crashes when running UFS-GOCART with the following stack trace information:
  0: pe=00000 FAIL at line=00104    BaseProfiler.F90                         <Timer ioserver is not a fresh self start>
  0: forrtl: severe (174): SIGSEGV, segmentation fault occurred
  0: Image              PC                Routine            Line        Source
  0: ufs_model<PHONE_NUMBER>D62ADA  Unknown               Unknown  Unknown
  0: libpthread-2.17.s  00002B4E21A245D0  Unknown               Unknown  Unknown
  0: libMAPL.profiler.  00002B4E1D599A4D  mapl_advancedmete          93  AdvancedMeter.F90
  0: libMAPL.profiler.  00002B4E1D60EC61  mapl_baseprofiler         145  BaseProfiler.F90
  0: libMAPL.pfio.so    00002B4E1750D1EA  pfio_abstractserv         228  AbstractServer.F90
  0: libMAPL.pfio.so    00002B4E17630C1B  pfio_serverthread        1092  ServerThread.F90
  0: libMAPL.pfio.so    00002B4E1744F6B2  pfio_messagevisit          87  MessageVisitor.F90
  0: libMAPL.pfio.so    00002B4E1744CEBD  pfio_abstractmess         112  AbstractMessage.F90
  0: libMAPL.pfio.so    00002B4E174C5622  pfio_simplesocket         105  SimpleSocket.F90
  0: libMAPL.pfio.so    00002B4E17664F3B  pfio_clientthread         413  ClientThread.F90
  0: libMAPL.pfio.so    00002B4E17690DC6  pfio_clientmanage         353  ClientManager.F90
  0: libMAPL.base.so    00002B4E15FFF3F6  mapl_extdatagridc        1529  MAPL_ExtDataGridCompMod.F90

@weiyuan-jiang please give this high priority.    Even if it means we have to block off the timers for now.

ok. @tclune

@weiyuan-jiang I should add - you may need to work with @bena-nasa or @WilliamJamieson to replicate for the UFS environment.   But I'm hoping it can be replicated in GEOS when using the "local" o-server.

I saw the problem even without running the program

@bena-nasa , would you help me to test this branch to see if I fixed this issue? Thanks a lot.  hotfix/wjiang/profiler_cleanup

@weiyuan-jiang - I've tested your branch with UFS-GOCART and it crashed with the same error message. The stack trace is identical to the previously reported one.

OK. Thanks. I will keep looking

Can you show me the run_cmd in gcm_run.j ?  For example, mine looks like
$GEOSBIN/esma_mpirun -np  200 ./GEOSgcm.x --npes_model 96 --nodes_output_server 2 --logging_config 'logging.yaml'

@weiyuan-jiang   UFS is not using GEOS scripts.       And in particular they are not using command line options and are thus using the "internal" server.

@rmontuoro , I have made more changes. Would you please try again? https://github.com/GEOS-ESM/MAPL/tree/hotfix/wjiang/profiler_cleanup  , Hopefully,  this crash would be fixed this time.

We have disabled the feature that was causing this latest crash and gotten that to develop of MAPL. I'm pulling now and will do a double check that we get a clean exit and the other issues (the point source placement code and the issue with output variables with a "." in the name in History) still appear to be resolved.

The current develop branch (deddd75) works with UFS-GOCART. Issue #723 remains open.

@rmontuoro .  How do you build your FMS library? is it static ( libfms_r4.a and libfms_r8.a) or dynamic ( libfms_r4.so and libfms_r8.so).  My question is not related to this issue though.

@weiyuan-jiang @rmontuoro Has this been fixed in the latest MAPL?

@mathomp4 - Yes. This issue can be closed.


Rename influx-tools to influx_tools

match naming scheme of all other peers: influx_inspect, influx_stress.. etc.

Fixed in #10008


Add broken test for tool param inheritance

Hi @nuwang, I noticed something odd where if I put 'docker_enabled: true' in a tool's destination parameters it would come up in the destination parameters for other tools.  I could add this to the inheritance test case.

@cat-bro This should fix it: https://github.com/usegalaxy-au/total-perspective-vortex/commit/f834947a958ca73c8d13f27a3632ac8b2267c1ef


Live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

MPI/mpi-one-sided-communications-functions.md
:white_check_mark:Succeeded
View

MPI/mpi-win-allocate-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-all-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-local-all-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-flush-local-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-lock-all-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-sync-function.md
:white_check_mark:Succeeded
View

MPI/mpi-win-unlock-all-function.md
:white_check_mark:Succeeded
View

MPI/toc.yml
:white_check_mark:Succeeded
View

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.


Feature Request: Artisan command to register a new release

It would be nice with a new artisan command sentry:release which would call the Sentry API and notify Sentry about a new release (as recommended by the Sentry docs.
This would be really helpfull for usage in CI/CD tools like Laravel Envoyer.

Hi @bilfeldt,
Yes that would be very nice but we already have great language independent tooling for this: https://docs.sentry.io/product/cli/.
That's we are not going to add an artisan command to create releases and deploys because Sentry CLI handles that like a dream.
The CLI tool is also a single portable binary which should make it easy to use in CI (for example using the docker containers in GitHub Actions) / CD tools like Envoyer (possibly installing it through NPM when running Laravel Mix).
(see also: https://github.com/getsentry/sentry-laravel/issues/190)


Faster edit-readme

#2671
Test on
https://github.com/yakov116/refined-github

Perfect! Follows https://github.com/sindresorhus/refined-github/issues/3084#issuecomment-683345700


Change uib-typeahead to typeahead

@msemenistyi Why? This is not a valid change, as we've just introduced prefixes.

@pkozlowski-opensource Here are options to the right of examples:

What version were these prefixes introduced in? I was fighting to get it working for an hour looking at uib-typeahead examples

0.14.0. If you need older docs, you can use the dropdown on the top of the page to change to the version you're currently working.

@Foxandxss thanks


Default batch size too high

As pointed out in passing in #15 the batch size of 500 breaks (initial) indexing for me. The job payload simply is so big that it causes "argument list too long" when the jobs are passed to a command run (due to executeIsolated being true, for good reasons) as a shell command.
For me it works with 150, but that could be different depending on the shell in use and other factors.
I'd suggest to use a rather "conservative" (low) default and suggest to try and raise it if needed.

With https://github.com/Flowpack/jobqueue-common/pull/26 merged, this should no longer be an issue, provided a (yet unreleased) version of flowpack/jobqueue-common is used.


Add rust-version field to bevy_mikktspace

bevy_mikktspace documents that it requires at least Rust 1.52.1.
https://github.com/bevyengine/bevy/blob/ff8a9b2a64d4d34ceb359edbf80298dcd5f9c9fb/crates/bevy_mikktspace/README.md?plain=1#L13
This should be codified by adding the rust-version field to Cargo.toml.

Bonus points if you also check if any other crates do not specify a rust-version. :) (Most should say rust-version.workspace = true!)

bevy_mikktspace is using the 2021 Rust edition. This makes it's minimum supported version Rust 1.56.0.

Bonus points if you also check if any other crates do not specify a rust-version. :) (Most should say rust-version.workspace = true!)

Turns out workspace-inherited properties are quite incompatible with our compile fail tests. If that were fixed, a lot of duplicated metadata could be merged...


workaround bootloader-shared var init bug

Workaround for https://github.com/luxonis/depthai-bootloader-shared/issues/4

Manually init class success and char array so that both are in a valid and known state as
compared to them being in a random and/or non-null terminated state
After a related PR in depthai-bootloader-shared is merged, these workarounds should be removed

"The Matrix" has spoken - some minor style issues regarding ifs & comments

Yes, I will always put a space after if. I need a tool to fix these for me. Vscode is occassionaly not correcting the format; seems to be when I don't specifically press the semicolon key, or when pasting. I found more vscode settings to better cover those cases. Hopefully will get yet better formatting moving forward.
i have force pushed


make the suppression work on minor version change

General Guidelines
~- [ ] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).~
Command Guidelines
~- [ ] Each command and parameter has a meaningful description.~
~- [ ] Each new command has a test.~
(see Authoring Command Modules)

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3509   +/-   ##
=======================================
  Coverage   71.35%   71.35%
=======================================
  Files         419      419
  Lines       26047    26047
  Branches     3943     3943
=======================================
  Hits        18585    18585
  Misses       6305     6305
  Partials     1157     1157

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 119ba95...3a263ca. Read the comment docs.

@derekbekoe, please review and merge it


fix https://github.com/elves/elvish/issues/1220

if j>len(name){
	break
}

Check if j is greater than name's length

This PR patches up the panic but it doesn't address the underlying correctness issue.
The underlying issue is that the code here assumes that
for i, r := range s { ... }

Is always a lossless way to split a string, and all the rs, when concatenated together, will form s. This is only true if s is a valid UTF-8 string; if there is anything that can't be decoded as UTF-8, the iteration will advance by one byte with r = 0xFFFD (whose length is not 1 when converted to a string, which explains the panic). OS paths are not guaranteed to be valid UTF-8 strings, and the reproduction in #1220 is essentially constructing a non-UTF-8 string.
The fix should be changing the glob package to treat strings as byte sequences instead of rune sequences.

This PR patches up the panic but it doesn't address the underlying correctness issue.
The underlying issue is that the code here assumes that
for i, r := range s { ... }

Is always a lossless way to split a string, and all the rs, when concatenated together, will form s. This is only true if s is a valid UTF-8 string; if there is anything that can't be decoded as UTF-8, the iteration will advance by one byte with r = 0xFFFD (whose length is not 1 when converted to a string, which explains the panic). OS paths are not guaranteed to be valid UTF-8 strings, and the reproduction in #1220 is essentially constructing a non-UTF-8 string.
The fix should be changing the glob package to treat strings as byte sequences instead of rune sequences.

@mrlzh, See also the description of the two ways to iterate over a string. @xiaq is correct that Elvish cannot assume path names are valid UTF-8 strings. But since the glob/wildcard characters are single byte ASCII characters that doesn't matter. It is sufficient to process the path name one byte at at time. If the byte is a wildcard (e.g., *) it is treated specially; otherwise, the byte is a literal that has to match the corresponding byte in any expansion.

@mrlzh, See also the description of the two ways to iterate over a string. @xiaq is correct that Elvish cannot assume path names are valid UTF-8 strings. But since the glob/wildcard characters are single byte ASCII characters that doesn't matter. It is sufficient to process the path name one byte at at time. If the byte is a wildcard (e.g., *) it is treated specially; otherwise, the byte is a literal that has to match the corresponding byte in any expansion.

The bug is now fixed in e061b657cbd1621f420d5f85d6626d4bea7864bb, closing.


images

Description

Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
(paste your output here)

Output of docker info:
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

I assume this was opened by mistake


Bump carbon.kernel.version to 4.10.2

$Subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7772469396

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7772469396
Status: cancelled

This build will fail since scim version is not bumped. Please refer to https://github.com/wso2/product-is/pull/19386

Closed since already done with: https://github.com/wso2/product-is/pull/19386


fix prompt

fix

Completion lost prompt
Original input is lost when canceling

Modified by referring to https://github.com/junegunn/fzf/blob/master/shell/key-bindings.zsh#L102

Thank  you again!


quickstart script fails to authenticate despite credentials being valid

What happened?
I tried installing upbound and the aws provider following the quickstart guide and the bucket creation fails with the following error:
  Warning  CannotConnectToProvider          3m9s (x2305 over 18m)  managed/s3.aws.upbound.io/v1beta1, kind=bucket  (combined from similar events): cannot get terraform setup: cannot get the caller identity: GetCallerIdentity query failed: GetCallerIdentity query failed: operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: badc1359-cb3b-4eae-bf92-0bde87b43a46, api error InvalidClientTokenId: The security token included in the request is invalid.

Obviously the most likely explanation is that my creds are bad but I have really tried to demonstrate as much as possible that this is not the case. I wonder if somehow they're the wrong type of credential if that's even a thing. I don't know much about AWS IAM.
Before and after running the script (I also tried to follow the quickstart guide's steps myself) I tested the credentials by listing, creating and then deleting an s3 bucket using the CLI. So I know they're valid and haven't expired. I guess you'll have to take my word for it that I'm using the same ones I tested!
How can we reproduce it?
$ aws s3api list-buckets --region us-east-1
$ aws s3api create-bucket --bucket luke-test-48e592d0c --region us-east-1
$ aws s3api delete-bucket --bucket luke-test-48e592d0c --region us-east-1
$ kind create cluster # note that it used kindest/node:v1.25.3
$ wget "https://raw.githubusercontent.com/upbound/provider-aws/main/docs/quickstart.sh"
$ vim quickstart.sh # edited the version to use v0.21.0 but also tried the hardcoded v0.17.0
$ chmod +x quickstart.sh && ./quickstart.sh
 (paste the creds that were used in earlier step; eventually observe timeout waiting for bucket to create)
$ kubectl describe buckets
...snip...
Events:
  Type     Reason                           Age                     From                                            Message
  ----     ------                           ----                    ----                                            -------
  Warning  CannotConnectToProvider          24m                     managed/s3.aws.upbound.io/v1beta1, kind=bucket  cannot get terraform setup: cannot get the caller identity: GetCallerIdentity query failed: GetCallerIdentity query failed: operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: 941f7081-0287-4c25-9b85-ff3e813add03, api error InvalidClientTokenId: The security token included in the request is invalid.
$ aws s3api list-buckets --region us-east-1 # just to prove token didn't expire
$ aws s3api create-bucket --bucket luke-test-48e592d0c --region us-east-1
$ aws s3api delete-bucket --bucket luke-test-48e592d0c --region us-east-1

My credentials have admin access to a sandbox account my team has access to (it's my employer's account).
What environment did it happen in?

Universal Crossplane Version:

$ up uxp --version
v0.15.0

Provider Version:

$ kubectl get pkgrev
NAME                                                           HEALTHY   REVISION   IMAGE                                          STATE    DEP-FOUND   DEP-INSTALLED   AGE
providerrevision.pkg.crossplane.io/provider-aws-c49e1af5e48d   True      1          xpkg.upbound.io/upbound/provider-aws:v0.21.0   Active                               29m

Other relevant bits:
$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"archive", BuildDate:"2022-11-10T22:18:49Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-10-25T19:35:11Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}
$ docker version
Client:
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.19.2
 Git commit:        baeda1f82a
 Built:             Thu Oct 27 21:30:31 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.19.2
  Git commit:<PHONE_NUMBER>
  Built:            Thu Oct 27 21:29:34 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.6.10
  GitCommit:        770bd0108c32f3fb5c73ae1264f7e503fe7b2661.m
 runc:
  Version:          1.1.4
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
$ kind --version
kind version 0.17.0
$ uname -a
Linux legion 6.0.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 16 Nov 2022 17:01:17 +0000 x86_64 GNU/Linux
$ head -1 /etc/os-release
NAME="Arch Linux"
$ kubectl get providerconfigs.aws.upbound.io default -o json | jq .spec
{
  "credentials": {
    "secretRef": {
      "key": "creds",
      "name": "aws-secret",
      "namespace": "upbound-system"
    },
    "source": "Secret"
  }
}
$ kubectl get secrets -n upbound-system
NAME                                         TYPE                 DATA   AGE
aws-secret                                   Opaque               1      35m
sh.helm.release.v1.universal-crossplane.v1   helm.sh/release.v1   1      36m
uxp-ca                                       Opaque               3      36m
xgql-tls                                     Opaque               3      36m
$ kubectl get secret aws-secret -n upbound-system -o yaml
apiVersion: v1
data:
  creds: <REDACTED>
kind: Secret
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: <REDACTED>
  creationTimestamp: "2022-11-24T15:40:02Z"
  name: aws-secret
  namespace: upbound-system
  resourceVersion: "2168"
  uid: dafe57ef-b995-487c-ba37-21101c86bae5
type: Opaque

I was hoping I'd find some logs in the provider's controller pod but there was nothing.

Incidentally, I'm running into the same issue except I'm running it against localstack. I've confirmed it's not an issue with localstack as I'm able to create a bucket against it when using crossplane-contrib/provider-aws.

i have since re-run the above steps using kindest/node:v1.22.15 just in case 1.25 was too new. i tried aws provider v0.21.0 and v.18.0. same results.

@lukebond thanks a lot for the report!
I tried on my side and can confirm that it is not working. Currently, I am having another issue than yours but I will go over it and get all fixed.

@lukebond I think we are having different problems, and mine was actually due to the wrong provider version, which you've already fixed on your side.
Unfortunately, I cannot reproduce the error you're having but checking the error message, one possibility could be the lack of permissions to get caller identity. You can double-check that with the following:
aws sts get-caller-identity

If that works fine, then I would suggest focusing on the error message, i.e. this blog post could be helpful.

it wasn't the permissions on getting the caller identity, but your blog post link did help me. the issue was that i wasn't specifying the session token, and perhaps my org is set up in such a way that it's required. this diff on the quickstart script got it working for me:
$ diff quickstart.sh*
4c4
< read -p "AWS access_key_id: " aws_access_key; read -sp "AWS secret_access_key: " aws_secret_key; export AWS_KEY=$aws_access_key; export AWS_SECRET=$aws_secret_key; printf "\n"
---
> read -p "AWS access_key_id: " aws_access_key; read -sp "AWS secret_access_key: " aws_secret_key; printf "\n"; read -sp "AWS session_token: " aws_session_token; export AWS_KEY=$aws_access_key; export AWS_SECRET=$aws_secret_key; export AWS_SESSION_TOKEN=$aws_session_token; printf "\n"
36c36
<     $(printf "[default]\n    aws_access_key_id = %s\n    aws_secret_access_key = %s" "${AWS_KEY}" "${AWS_SECRET}")
---
>     $(printf "[default]\n    aws_access_key_id = %s\n    aws_secret_access_key = %s\n    aws_session_token = %s" "${AWS_KEY}" "${AWS_SECRET}" "${AWS_SESSION_TOKEN}")

thanks for the tip, @turkenh!


MediaPlayer Error: Unknown (1) -2147483648

What version of Streaming-Meda-Cordova-Plugin are you using?
What version of Cordova are you using?
What devices are affected?
Please describe the issue in detail, with relevant code samples
What did you expect to happen?
What actually happened?

I am facing same issue. android version 10 and am using localhost url


feat: add commit date to tagged-version details

Add commit date to the list of tagged-version details

Coverage remained the same at 100.0% when pulling 7f9ec9ae09cdfaeb4c81928a41cda1ed3c7d84db on feature/add-tag-dates into cd88316d6976ce8878a90a1a6d4eb326d16a4d68 on master.

Coverage remained the same at 100.0% when pulling 7f9ec9ae09cdfaeb4c81928a41cda1ed3c7d84db on feature/add-tag-dates into cd88316d6976ce8878a90a1a6d4eb326d16a4d68 on master.


Different results in RITUAL and AVISC

Hi, thanks for the great work. For MME-Hallucination dataset, why the reported result in RITUAL and AVISC so different? Thanks!

Hi @zifuwan,
Thanks for your interest in our work!
These two works have slightly different codebases and their hyperparameters (such as seed and alpha) are different.
While we set the random seed to 42 as default for most of the results, for MME-Hallucination, we averaged the results across runs, each with a different randomly selected seed (e.g., 42, 10, 25 for AvisC and 42, 5, 16 for RITUAL).
Also note that since MME-Hallucination benchmark only contains a few hundreds of images, total scores on this benchmark vary a lot with small variations.
Please let me know if you have further questions. I am happy to answer!

Thanks for the reply!


Reset Password not working?

When I choose reset password, just hangs with circular wait

Try a second time and the e-mail gets sent.
BUt "YOu can now sign in with new password" should give a continue link.


Cant disable anonymous access after enabling

Issue description
Cant disable anonymous access after enabling
Steps to Reproduce

Enable anonymous access
Test anonymous access
Try to disable anonymous access

Expected Behaviour
disable anonymous access
Actual Behaviour
settin gs saves "sucessifly" after unchecking, but keep enabled after f5
Environment Information

Operating System: CentOS Linux release 7.6.1810 (Core)
Streama version: streama-1.6.1
Container Version (If Applicable): OpenVZ

I actually cant reproduce this.. please try again in the new release

https://github.com/streamaserver/streama/releases/tag/v1.6.2

@CardealRusso Can you solved? Because I know how solve...


Add keepResources property to GitRepo creation and edit.

Summary
Fixes #8455
Occurred changes and/or fixed issues

Add a checkbox to toggle boolean value of  value.spec.keepResources
Field is updatable via YAML as well.

Technical notes summary
Related Fleet work:

Issue: https://github.com/rancher/fleet/issues/680
PR: https://github.com/rancher/fleet/pull/1382

Areas or cases that should be tested

Ensure that Backend is using latest rancher head with the commit with PR: https://github.com/rancher/fleet/pull/1382
Navigate to Continuous Delivery > Git Repos
Click on Add Repository or Edit Existing repository
There is a new section Resource Handling which allows to set the field.
It can also be set via YAML.

Areas which could experience regressions

GitRepo creation and edit

Screenshot/Video

@Shavindra Has the backend for this been added? If not, we should not merge, otherwise we're exposing UI that does not have the required backend support.


The process is not exiting while it throws an connection error

The process is not exiting while it throws an connection error.

pull requests welcome

Actually it was a problem with imap npm module you are using. It is fixed now, You have to change the version of imap to ^0.8.18.(Should be at least this version) I am making a pull request.

As mentioned in #18, you don't actually need to change the value listed in package.json for the imap library to get the latest patch version, you just need to reinstall this package and the semver hat ^ will cause it to automatically pull the latest patch version.


MaxIncomingStreams does not reflect closed streams

I've run into an issue possibly related to #2709 that I've been able to reproduce using the following gist, adapted from the gist linked in the issue. If I remove the reading/writing bits and just close the stream (from both sides), the MAX_STREAMS update doesn't seem to be communicated, I'm not able to create any new streams and it blocks.
In this edited gist I've removed the binary.{Read,Write} and just closed the stream from both sides and added a bit of logging. I set MaxIncomingStreams to 2 and after two initiated (and closed) streams... it just gets stuck.
https://gist.github.com/kokes/15324dce93a41fff61cbbf101bc45590
$ go run repro.go
10:03:16 repro2.go:42: TAP ENTER TO SEND THE NEXT NUMBER TO THE CLIENT

10:03:17 repro2.go:62: closed a stream from the server side
10:03:17 repro2.go:42: TAP ENTER TO SEND THE NEXT NUMBER TO THE CLIENT
10:03:17 repro2.go:94: closed a stream from the client side

10:03:17 repro2.go:62: closed a stream from the server side
10:03:17 repro2.go:42: TAP ENTER TO SEND THE NEXT NUMBER TO THE CLIENT
10:03:17 repro2.go:94: closed a stream from the client side

10:03:51 repro2.go:50: timeout: no recent network activity
exit status 1

Am I using it wrong or does the information not get through over the wire?
Thanks!

I don't have the time to debug your code, but you'll need to call Close (or reset the stream) from both sides.

That's the idea, I explicitly close it from both sides, but upon further investigation, there are other issues at play.
I further simplified the code to just this (+ logging)
// server goroutine
for {
    stream, err := session.OpenStreamSync(context.Background())
    if err != nil {
        log.Fatal(err)
    }

    if err := stream.Close(); err != nil {
        log.Printf("problem closing stream: %v", err)
    }
}
// client goroutine
for {
    stream, err := session.AcceptStream(context.Background())
    if err != nil {
        log.Fatalf("client (during AcceptStream): %v", err)
    }

    if err := stream.Close(); err != nil {
        log.Fatalf("a problem closing the stream from the client side: %v", err)
    }
}

And the odd thing is that no matter how much time I wait after opening that bidi stream... the client only accepts it after it's closed by the server, which could mess up the concurrent connection counter.
$ go run maxs.go
07:59:00 maxs.go:20: starting up
07:59:01 maxs.go:43: server: opened a stream: 1
07:59:02 maxs.go:50: server: closed a stream: 1
07:59:02 maxs.go:43: server: opened a stream: 5
07:59:02 maxs.go:76: client: accepted a stream: 1
07:59:02 maxs.go:81: client: closed a stream: 1
07:59:03 maxs.go:50: server: closed a stream: 5
07:59:03 maxs.go:76: client: accepted a stream: 5
07:59:03 maxs.go:81: client: closed a stream: 5
07:59:33 maxs.go:41: timeout: no recent network activity

However, if I add a stream.Write([]byte{1,2,3}) to the server side after opening the bidi stream, it suddenly reorders to the way I'd expect (server open, client accept, client closes, server closes). And just like before - both sides close the stream yet AcceptStream blocks after two stream have come and gone.
$ go run maxs.go
08:04:17 maxs.go:20: starting up
08:04:18 maxs.go:43: server: opened a stream: 1
08:04:18 maxs.go:76: client: accepted a stream: 1
08:04:18 maxs.go:81: client: closed a stream: 1
08:04:19 maxs.go:50: server: closed a stream: 1
08:04:19 maxs.go:43: server: opened a stream: 5
08:04:19 maxs.go:76: client: accepted a stream: 5
08:04:19 maxs.go:81: client: closed a stream: 5
08:04:20 maxs.go:50: server: closed a stream: 5
08:04:50 maxs.go:74: client (during AcceptStream): timeout: no recent network activity

(Also the timeout is from the other side.)

That makes sense, opening a stream doesn’t send anything on the wire. Only when you write to the stream will your peer learn that you’ve opened a stream.

But even in the first case (when no data got exchanged) did the peer learn that - when the server closed it. So proper accounting should lead to the fact that there were zero concurrent connections in the end. But that was not the case.
To close the loop: if I add writing to the server, it still doesn't help (as noted above), but if I drain the stream from the client side (io.Copy(io.Discard, stream)), it all starts working and the concurrent stream accounting kicks in and allows new streams to be created.
So it's not the existence of the stream that doesn't get communicated - we clearly see from the logs that both sides agree two streams - 1 and 5 - are in play. It's the server's Close() that's not understood by the client unless 1) servers sends some data, 2) client reads them all.

I'll dig into the code a bit if I have time, but it seems like the Close packet is at the end of some read queue on the client, which doesn't get read unless I read the data first.

Yes, you have to read the EOF, or alternatively reset the stream. If you don’t read the EOF, quic-go still has to keep the stream around, as might read from the stream later.

I finally see where the confusion on my part comes from. The Close() method on the client side is to close the io.Writer as it's from the SendStream interface, it does not close the stream itself. Seems counterintuitive for a bidirectional stream to have a Close() method that only closes one side of the pipe... This feels like it's just CancelWrite. Close() should (in my opinion) call CancelRead and CancelWrite as the stream is closing down.
Anywho, CancelRead (with Close right after) on the client side does what I need - it closes the Stream properly and releases all resources tied to it, even if I didn't read until EOF.

I've just discovered this bug whilst investigating the cause of unexpected too many open streams errors.  The idiomatic Go approach is:
  f, err := foo.Open(...)
  if err != nil { return err }
  defer f.Close()

Streams are not well documented as is and requiring an additional f.CancelRead(something) is not at all obvious - especially since CancelRead() is documented as an "abort" operation, rather than a normal "close".  An additional wrinkle is that CancelRead requires a StreamErrorCode argument and there don't appear to be any such codes defined.  NoError seems an obvious choice but it is (non-obviously) a TransportErrorCode, rather than a StreamErrorCode.
In my case, I am reading all the data from the stream, but by knowing how many bytes to read, rather than reading to EOF - there's no indication that the latter behaviour is required.
As with @kokes, updating my code to defer func() { f.CancelRead(0); f.Close() }() seems to have worked around this bug.

Closing this issue, since there doesn't seem to be anything that needs to be resolved.
The non-obvious behavior called out here is now documented on quic-go.net.


Update INTEGER_TOO_LARGE error message

What
Updates the error message displayed when an number is entered that is too big for the system to handle
How to test

Check out the branch
Enter a large number into any of the numeric fields (greater than 10 digits)
Submit the form
Verify that the following message is displayed

The maximum value allowed is<PHONE_NUMBER>. Please correct your answer.
Who can test
Anybody except @weapdiv-david

Any reason why we can't just update the default error message rather than the customizable ones? It would just be a single change then, rather than the same thing ten times?

I've done it this way as the default error messages are deliberately terse in order to encourage authors to over-ride them.  I do hwever think that it might be better to override error messages once within the schema instead of on each response.  This is a larger question then, around schema design and system functionality which I think should be discussed post MCI.

OK lets merge this then, I've already added a tech debt backlog item for the error messages so we'll discuss then 👍

Rebased


supports giving higher priority to intra-domain invocation

What is the purpose of the change
supports giving higher priority to intra-domain invocation
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

同区域的会优先调用
解决问题:夸机房访问
使用方式
- @Reference(check = false, interfaceClass = CommentService.class,parameters = {Constants.CONSUMER_REGION,"c4"})
private CommentService commentService;
- @Service(parameters = {Constants.PROVIDER_REGION, "c4"})
public class CommentServiceImpl implements CommentService
c4 可以用 ${area} 根据部署脚本替换

理论上不同机房的服务应该注册在不同的注册中心分区，比如 zk 的不同集群，或者 Nacos 不同的命名空间，而不是通过负载均衡实现同机房的优先。
另外，这不是一个通用的负载均衡策略，不应该放到 Dubbo 的官方仓库中的核心链路中，而是扩展 LoadBalance 实现你自己定制的负载均衡策略。


Remove appArmorProfile from CronJob helm template

The condition is reversed, and fixing it breaks CI.
See https://github.com/cilium/cilium/pull/33077
Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

Fixes: #34145
Fix appArmorProfile condition for CronJob helm template

/test

@rolinh thanks for enabling automerge. However, the CI is failing (probably for unrelated reason). How to move forward?

/ci-clustermesh

@sathieu, not sure but agree, it's probably a flake. I re-triggered the failing test, let's see if that suffices.

@sathieu, not sure but agree, it's probably a flake. I re-triggered the failing test, let's see if that suffices.

CI is still failing. I rebased...

@rolinh I ended up removing completely the appArmorProfile. This was breaking CI (probably a kind known issue).
Please review again 🙏 .

/test

Please review again
@rolinh blocking on this, in case you want to have another look

@julianwiedmann There are some CI failures, but I don't understand the problem. Maybe a flaky test?


The RegExp that matches the vendorName is more restricted than it should

The vendorField could follow the schema provided by the specification (https://tools.ietf.org/html/rfc6838#section-4.2), so the RegExp that extracts it from the accept header should be fixed to allow other characters than alphanumeric:
https://github.com/p-meier/hapi-api-version/blob/5c5b57fbaebaba8e6969aa0236a3cc1d30f7c297/index.js#L37

If you'd like to PR an update for this please feel free, otherwise I'll add support in the next week or two. I think ideally the regex would look like
/^vnd.[^\s\.]+\.v[0-9]+$/

Would this solve your needs?

Thanks for you answer.
That RegExp would be enough for me, although I'd use a different one, to adhere to the specification.
A different issue, that I've found when running the tests is that some of them look incorrect:
For instance, this one shouldn't throw an Error:
https://github.com/p-meier/hapi-api-version/blob/5c5b57fbaebaba8e6969aa0236a3cc1d30f7c297/test/index.js#L196


honor crash handler override variable in tests

Scope & Purpose
Honor value of variable ARANGODB_OVERRIDE_CRASH_HANDLER in our tests, too

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)
[x] The behavior change can be verified via automatic tests

Testing & Verification
This change is already covered by existing tests, such as scripts/unittest recovery.
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10201/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10203/

http://<IP_ADDRESS>:8080/job/arangodb-ANY-jslint/7042/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10205/

http://jenkins.arangodb.biz:8080/job/arangodb-ANY-windows-matrix/1161/


Feature request: dual (edge) layers

I'd like to have a layer where the tiles are placed on edges instead of cells, for placing doors, bars, and thin walls that are still grid aligned.
This is a little tricky because there are 2x as many edges as cells (if you ignore an off-by-one of the border), so it isn't just an offset layer for mouse coords and rendering. However, it could be modeled internally as two layers, where one is offset vertically by half a cell and the other is offset horizontally, but drawing paints to both simultaneously so that it feels to the artist as if it is a single edge layer.

You could have a Tile layer with a smaller grid than the Tileset acctual grid (eg. a layer of 8px grid with a tileset of 16px). Would it work for you?

Good point!
A tile layer with a smaller grid works if the tools can be set for that layer to mask out every other tile, like masking the black tiles on a checkerboard.
That way the regular tools and pattern rules will only write to the legal locations on that layer (edges) and not to the centers and corners that are being ignored. This sounds like the easiest implementation strategy; an "edge" layer is really just a higher resolution later that refuses to write to cells where (x + y) & 1 != 0.
[Note that this is also an alternative and pretty elegant way of implementing hex grids, which map 1:1 to white checkerboard tiles.]

I actually might have a much simpler solution for your case: I already support internal offsetX/Y for each layers (because of level resizing issues with various grid sizes). Basically, just having 8px offset on a 16px grid should do the job, right?

Yes, if there are two offset layers [internally] and I can draw to them simultaneously using the tools, that's perfect!
In the Tiled editor I tried approximating this with two separate offset layers and it was too difficult for artists to use effectively. They had to switch active layer for vertical vs. horizontal details and kept getting confused and drawing on the wrong one, and fill commands & patterns didn't work properly of course.

No, in my suggestion you have 1 layer with the normal 16px grid, and one with with the grid offset-ed by 8px.
With the future changes implied by #32 (freely positioned tiles), it will possible for me to add a Snap to grid borders mode, giving you what you're looking for :)


savageresponses - Instagram Bridge failed with error 0

Error message: Cannot write the cache... Do you have the right permissions ?
Query string: action=display&bridge=Instagram&u=savageresponses&media_type=all&format=Atom

Contact instance admin, something wrong with his/her server.

thank you fix
Bachelor of Science (B.Sc) Computer Science
Ahmadu Bello University, Zaria
On Mon, 22 Apr 2019 at 09:53, Eugene Molotov<EMAIL_ADDRESS>wrote:

Contact instance admin, something wrong with his/her server.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RSS-Bridge/rss-bridge/issues/1112#issuecomment-485367679,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADNOLJ4I4OYYDFMFMY2QALDPRV4ITANCNFSM4HHOJXIQ
.


Cannot open KAP on MacOS 12

**macOS version:12.0.1
**Kap version:Kap-3.4.2

Press Control key while clicking on the app.

Thank you for the report, closing this as a duplicate of #1046.


❓ [Question] Partitioning for unsupported operations

❓ Question
As far as I understand Torch-TensorRT performs a partitioning step when unsupported operations are encountered. Then, graph uses generated TensorRT engine(s) for supported partition(s) and falls back to TorchScript JIT anywhere else. I can observe this behavior from generated graphs in general. However, I receive errors with specific blocks in which I couldn't understand why such blocks are problematic.
For instance, for the following (example) block:
"""block(for+cond)"""
retval=[]
for slice in x: # x: torch.Tensor
    if slice.sum() > 0: # any cond. dep. on tensor/slice
        retval.append(slice + 100)
    else:
        retval.append(slice + 50)
"""block(for+cond)"""

I receive a RuntimeError: [Error thrown at core/partitioning/shape_analysis.cpp:167] Expected ivalues_maps.count(input) to be true but got false on torch_tensorrt.compile(...):
Traceback (most recent call last):
  File "/home/burak/test.py", line 36, in <module>
    net_trt = torch_tensorrt.compile(net, **net_specs)
  File "/home/burak/miniconda3/envs/convert/lib/python3.10/site-packages/torch_tensorrt/_compile.py", line 125, in compile
    return torch_tensorrt.ts.compile(
  File "/home/burak/miniconda3/envs/convert/lib/python3.10/site-packages/torch_tensorrt/ts/_compiler.py", line 136, in compile
    compiled_cpp_mod = _C.compile_graph(module._c, _parse_compile_spec(spec))
RuntimeError: [Error thrown at core/partitioning/shape_analysis.cpp:167] Expected ivalues_maps.count(input) to be true but got false
Could not find torch::jit::Value* slice.1 produced from %slice.1 : Tensor = aten::select(%158, %6, %19) # /home/burak/test.py:20:8 in lowering graph for mini graph input.

What you have already tried
I have tried this behavior with the following example script:
import torch
import torch_tensorrt
torch_tensorrt.logging.set_reportable_log_level(torch_tensorrt.logging.Level.Info)

class Net(torch.nn.Module):
    def __init__(self):
        super().__init__()

        self.conv0 = torch.nn.Conv2d(3, 8, kernel_size=3)
        self.relu = torch.nn.ReLU(inplace=True)
        self.conv1 = torch.nn.Conv2d(8, 16, kernel_size=3)

    def forward(self, x):
        x = self.conv0(x)
        x = self.relu(x)
        x = self.conv1(x)

        """block(for+cond)"""
        retval=[]
        for slice in x:
            if slice.sum() > 0: # any cond. dep. on tensor/slice
                retval.append(slice + 100)
            else:
                retval.append(slice + 50)
        """block(for+cond)"""

        return retval

net = Net().eval().cuda()

net_specs = {
    'inputs': [torch_tensorrt.Input(shape=[1, 3, 224, 224], dtype=torch.float32)],
    'enabled_precisions': {torch.float32, torch.half},
}

net_trt = torch_tensorrt.compile(net, **net_specs)
print(net_trt.graph)

I receive the following RuntimeError (full output, info log-level):
INFO: [Torch-TensorRT] - ir was set to default, using TorchScript as ir
INFO: [Torch-TensorRT] - Module was provided as a torch.nn.Module, trying to script the module with torch.jit.script. In the event of a failure please preconvert your module to TorchScript
INFO: [Torch-TensorRT] - Lowered Graph: graph(%x.1 : Tensor):
  %self.conv0.weight.1 : Float(8, 3, 3, 3, strides=[27, 9, 3, 1], requires_grad=0, device=cuda:0) = prim::Constant[value=<Tensor>]()
  %self.conv0.bias.1 : Float(8, strides=[1], requires_grad=0, device=cuda:0) = prim::Constant[value= 0.1437  0.0745  0.1127  0.1185  0.1406  0.1445 -0.0802  0.0562 [ CUDAFloatType{8} ]]()
  %self.conv1.weight.1 : Float(16, 8, 3, 3, strides=[72, 9, 3, 1], requires_grad=0, device=cuda:0) = prim::Constant[value=<Tensor>]()
  %self.conv1.bias.1 : Float(16, strides=[1], requires_grad=0, device=cuda:0) = prim::Constant[value=<Tensor>]()
  %9 : int = prim::Constant[value=1]()
  %8 : NoneType = prim::Constant()
  %7 : bool = prim::Constant[value=1]() # /home/burak/test.py:20:8
  %6 : int = prim::Constant[value=0]() # /home/burak/test.py:21:29
  %5 : int = prim::Constant[value=100]() # /home/burak/test.py:22:38
  %4 : int = prim::Constant[value=50]() # /home/burak/test.py:24:38
  %3 : int[] = prim::Constant[value=[1, 1]]()
  %2 : int[] = prim::Constant[value=[0, 0]]()
  %153 : bool = prim::Constant[value=0]()
  %154 : int[] = prim::Constant[value=[0, 0]]()
  %155 : Tensor = aten::_convolution(%x.1, %self.conv0.weight.1, %self.conv0.bias.1, %3, %2, %3, %153, %154, %9, %153, %153, %153, %153)
  %17 : Tensor[] = prim::ListConstruct()
  %137 : Tensor = aten::relu(%155) # /home/burak/miniconda3/envs/convert/lib/python3.10/site-packages/torch/nn/functional.py:1455:17
  %156 : bool = prim::Constant[value=0]()
  %157 : int[] = prim::Constant[value=[0, 0]]()
  %158 : Tensor = aten::_convolution(%137, %self.conv1.weight.1, %self.conv1.bias.1, %3, %2, %3, %156, %157, %9, %156, %156, %156, %156)
  %144 : int = aten::len(%158) # /home/burak/test.py:20:8
   = prim::Loop(%144, %7) # /home/burak/test.py:20:8
    block0(%19 : int):
      %slice.1 : Tensor = aten::select(%158, %6, %19) # /home/burak/test.py:20:8
      %123 : Tensor = aten::sum(%slice.1, %8) # /home/burak/test.py:21:15
      %125 : Tensor = aten::gt(%123, %6) # /home/burak/test.py:21:15
      %126 : bool = aten::Bool(%125) # /home/burak/test.py:21:15
       = prim::If(%126) # /home/burak/test.py:21:12
        block0():
          %24 : Tensor = aten::add(%slice.1, %5, %9) # /home/burak/test.py:22:30
          %25 : Tensor[] = aten::append(%17, %24) # /home/burak/test.py:22:16
          -> ()
        block1():
          %26 : Tensor = aten::add(%slice.1, %4, %9) # /home/burak/test.py:24:30
          %27 : Tensor[] = aten::append(%17, %26) # /home/burak/test.py:24:16
          -> ()
      -> (%7)
  return (%17)

INFO: [Torch-TensorRT] - Method requested cannot be compiled end to end by Torch-TensorRT.TorchScript.
Unsupported operators listed below:
  - aten::Bool.Tensor(Tensor a) -> bool
  - aten::len.Tensor(Tensor t) -> int

Traceback (most recent call last):
  File "/home/burak/test.py", line 36, in <module>
    net_trt = torch_tensorrt.compile(net, **net_specs)
  File "/home/burak/miniconda3/envs/convert/lib/python3.10/site-packages/torch_tensorrt/_compile.py", line 125, in compile
    return torch_tensorrt.ts.compile(
  File "/home/burak/miniconda3/envs/convert/lib/python3.10/site-packages/torch_tensorrt/ts/_compiler.py", line 136, in compile
    compiled_cpp_mod = _C.compile_graph(module._c, _parse_compile_spec(spec))
RuntimeError: [Error thrown at core/partitioning/shape_analysis.cpp:167] Expected ivalues_maps.count(input) to be true but got false
Could not find torch::jit::Value* slice.1 produced from %slice.1 : Tensor = aten::select(%158, %6, %19) # /home/burak/test.py:20:8 in lowering graph for mini graph input.

I have also experimented with the following three blocks:
"""block(none)"""
retval=x # no partitioning
"""block(none)"""

"""block(for)"""
retval=[]
for slice in x:
    retval.append(slice)
"""block(for)"""

"""block(cond)"""
if x.sum() > 0: # any cond. dep. on tensor
    retval = x + 100
else:
    retval = x + 50
"""block(cond)"""

I haven't received any errors with these. It also seems that torch.jit.script(...) generates a valid graph with all tested blocks (including block(for+cond)) but the problem is at the partitioning step.
I couldn't understand why block(for+cond) is problematic. Any comments or suggestions? Thanks in advance!
Environment

Build information about Torch-TensorRT can be found by turning on debug messages

Torch-TensorRT Version (e.g. 1.0.0): 1.3.0
PyTorch Version (e.g., 1.0): 1.13.1
CPU Architecture: x86_64
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, libtorch, source): pip
Build command you used (if compiling from source):
Are you using local sources or building from archives:
Python version: 3.9.15
CUDA version: 11.7
GPU models and configuration: NVIDIA GeForce RTX 3070 (Laptop)
Any other relevant information:

Additional context

Any ideas?


Building on OSX

Hi Dave, I'm trying to fix the OSX build issue and I have gotten it to build again using the sequence of command in the readme. As long as the user do brew install openssl first.
So this builds but I still get these things regarding boosts dynamic library when trying to run the binary
dyld: Library not loaded: libboost_log.dylib
  Referenced from: /usr/local/bin/drachtio
  Reason: image not found

right now if i just do this:
 find bin.v2/libs | grep .dylib | awk '{system("ln -s $PWD/" $1 " /usr/local/lib")}' (symlinking those dylibs to /usr/local/lib)
in the deps/boost folder that will take care of the above message and I think maybe make install boost will do it too
Should that just be chained in somewhere at the end? or there is actually another problem?
Cheers
Andrew

Thanks so much for working on this.  Ideally, I would love to link with the static libs for boost, like we do on linux.  I ran into a bunch of problems on osx trying to do that, but I am certain there must be a way.
In any case, your changes look like a big step forward so I am going to merge them


Update README.md, fixed package URL

Using correct package installation URL, explicit note that we're pulling from Prefrontal Cortex branch
See PR #672
cc @hybridherbst

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks – this is fixed by now. Next time, please sign the CLA so that your PR can be accepted.


PostgreSQL 12 ERROR:  column "relhasoids" does not exist

PostgreSQL 12.1
Error SQL:

ERROR:  column "relhasoids" does not exist
LINE 1: SELECT relhasoids FROM pg_catalog.pg_class WHERE relname='us...
               ^
In operator:

SELECT relhasoids FROM pg_catalog.pg_class WHERE relname='user'
			AND relnamespace = (SELECT oid FROM pg_catalog.pg_namespace WHERE nspname='usersm')

cause:
https://stackoverflow.com/questions/58461178/how-to-fix-error-column-c-relhasoids-does-not-exist-in-postgres
solution commited:
https://github.com/phppgadmin/phppgadmin/pull/81/commits/418b7e1a4433fc71bd202604e9fd389f2acd1510
Can you fix it please?

Should be fixed with new PhpPgAdmin (#4)

@denisorlov @wapmorgan Please see my comment: https://github.com/dockage/phppgadmin/pull/4#issuecomment-630602949

A simpler explanation for future Googlers.
TLD
This occurs when you're most likely reviewing a table made from v12+ but reviewing it in a psql/ Postgres client that is below that version (v11-).
Solution is to ensure your client is at least 12+.
Root Cause
OIDs column types are no longer special columns in v12+, hence the break
Reference Site


[Definition] Dont updated bundled with when 100% unnecessary

\c @indirect @andremedeiros

This makes sense to me. :ship:

LGTM :shipit:


Add Windows support

While the code should in theory work on Windows without issue, I haven't actually tested it yet, and the build system may need to be tweaked slightly in order to accommodate.
I do not have a Windows machine to test on however, so I may need to ask somebody else to test it for me, or make use of Github actions.

Note for this item: vcpkg may be useful for installing dependencies for the project.


[Network] az network application-gateway waf-policy managed-rule rule-set: Expose server error to user to give more intuitive hint message

Description

Fix https://github.com/Azure/azure-cli/issues/15019
Testing Guide

History Notes

[Network] az network application-gateway waf-policy managed-rule rule-set add: Expose server error to user to give more intuitive hint message.
[Network] az network application-gateway waf-policy managed-rule rule-set update: Support to change rule set type version.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Network

/azp run


I can't run the projects

No puedo ejecutar los juegos de prueba, es extraño el año pasado funcionaba bien con la anterior versión, ahora no arranca ni en la 4.0.2.  o  4.1.0.

Please check that C:\Program Files\Java\jre1.8.0_321 contains a valid JDK installation.

Sounds like you're trying to build with a JRE instead of a JDK? I haven't used Bladecoder, but your JAVA_HOME may be messed up or IDE settings are pointing to the wrong path if applicable. If you use Adoptium, or most non-Oracle JDKs, it should offer to set it for you during installation. Note that Gradle 6.7.1 requires Java 15 or older (if you wanted to use 17, you could probably change it to Gradle 7.4.2 - or whatever the latest is at the time of reading - somehow).

As @Frosty-J said, you have installed a JRE instead of a JDK. You need to uninstall the JRE and install the JDK. JDK 1.8 should works well.

Ya funciona, Ese era el error, gracias. Instale el Java JDK 8

Glad to hear. I reckon we can close this issue now.


Version 2.0

We can consider new version based on slightly modified base available here: https://gist.github.com/KaQuMiQ/49ca4c268e87b004a3364d8a1dfe0ce6
It allows failure and dynamic parameters usage during function application. However it brings a lot of concepts that are not necessarily required for original purpose of Aegithalos which is represented by AegithalosCocoa package.

Version 2.0 was implemented without failing mutations, we might consider adding failing mutations later on as separate type.