Having trouble performing plugin release

I'm currently having issues releasing the plugin.  Here's an excerpt from slack...

21:01 < sag47> kohsuke: I'm having trouble releasing a plugin.  My GitHub username is samrocketman and my jenkins-ci.org ID is sag47.  I have added my credentials to ~/.m2/settings.xml from this article
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
21:02 < sag47> kohsuke: Do I have the capability to release if I'm able to be a contributor for a plugin?  If not, what do I need to do in order to be able to release?
21:02 < sag47> kohsuke: I have taken over maintaining this as it was previously abandoned.
21:03 < sag47> kohsuke: Plugin in question: https://github.com/jenkinsci/slack-plugin

I'll be working through this and keep any followers for the next release updated via this issue.

Big thanks to talios on IRC for helping me sort out most of my issues.  All that remain is my authorization issue listed above.

Here's the error message I encounter.
^_^[sam@blaster:~/git/github/slack-plugin]$ mvn release:prepare release:perform -Dusername=... -Dpassword=...
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jenkins-ci.plugins:slack:hpi:1.7-SNAPSHOT
[WARNING] 'parent.relativePath' points at org.jenkins-ci.plugins:slack instead of org.jenkins-ci.plugins:plugin, please verify your project structure @ line 14, column 13
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Slack Notification Plugin 1.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.2.1:prepare (default-cli) @ slack ---
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
[INFO] Executing: /bin/sh -c cd /home/sam/git/github/slack-plugin && git status
[INFO] Working directory: /home/sam/git/github/slack-plugin
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "Slack Notification Plugin"? (org.jenkins-ci.plugins:slack) 1.7: :
What is SCM release tag or label for "Slack Notification Plugin"? (org.jenkins-ci.plugins:slack) slack-1.7: :
What is the new development version for "Slack Notification Plugin"? (org.jenkins-ci.plugins:slack) 1.8-SNAPSHOT: :
[INFO] Transforming 'Slack Notification Plugin'...
[INFO] Not generating release POMs
[INFO] Executing goals 'clean verify'...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.575 s
[INFO] Finished at: 2015-02-09T21:03:42-05:00
[INFO] Final Memory: 16M/134M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project slack: Execution default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prep
are failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare: java.lang.NoSuchMethodError: org.apache.maven.settings.Settings.getRuntimeInfo()L
org/apache/maven/settings/RuntimeInfo;
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.apache.maven.plugins:maven-release-plugin:2.2.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/sam/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.2.1/maven-release-plugin-2.2.1.jar
[ERROR] urls[1] = file:/home/sam/.m2/repository/org/apache/maven/release/maven-release-manager/2.2.1/maven-release-manager-2.2.1.jar
[ERROR] urls[2] = file:/home/sam/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[3] = file:/home/sam/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar
[ERROR] urls[4] = file:/home/sam/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[5] = file:/home/sam/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[6] = file:/home/sam/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[7] = file:/home/sam/.m2/repository/org/apache/maven/shared/maven-invoker/2.0.9/maven-invoker-2.0.9.jar
[ERROR] urls[8] = file:/home/sam/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[9] = file:/home/sam/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar
[ERROR] urls[10] = file:/home/sam/.m2/repository/commons-logging/commons-logging/1.0/commons-logging-1.0.jar
[ERROR] urls[11] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-providers-standard/1.5/maven-scm-providers-standard-1.5.pom
[ERROR] urls[12] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-accurev/1.5/maven-scm-provider-accurev-1.5.jar
[ERROR] urls[13] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-bazaar/1.5/maven-scm-provider-bazaar-1.5.jar
[ERROR] urls[14] = file:/home/sam/.m2/repository/regexp/regexp/1.3/regexp-1.3.jar
[ERROR] urls[15] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-clearcase/1.5/maven-scm-provider-clearcase-1.5.jar
[ERROR] urls[16] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvsexe/1.5/maven-scm-provider-cvsexe-1.5.jar
[ERROR] urls[17] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.5/maven-scm-provider-cvs-commons-1.5.jar
[ERROR] urls[18] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvsjava/1.5/maven-scm-provider-cvsjava-1.5.jar
[ERROR] urls[19] = file:/home/sam/.m2/repository/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar
[ERROR] urls[20] = file:/home/sam/.m2/repository/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar
[ERROR] urls[21] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-gitexe/1.5/maven-scm-provider-gitexe-1.5.jar
[ERROR] urls[22] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-git-commons/1.5/maven-scm-provider-git-commons-1.5.jar
[ERROR] urls[23] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-hg/1.5/maven-scm-provider-hg-1.5.jar
[ERROR] urls[24] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-perforce/1.5/maven-scm-provider-perforce-1.5.jar
[ERROR] urls[25] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-starteam/1.5/maven-scm-provider-starteam-1.5.jar
[ERROR] urls[26] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-svnexe/1.5/maven-scm-provider-svnexe-1.5.jar
[ERROR] urls[27] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-synergy/1.5/maven-scm-provider-synergy-1.5.jar
[ERROR] urls[28] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-vss/1.5/maven-scm-provider-vss-1.5.jar
[ERROR] urls[29] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-tfs/1.5/maven-scm-provider-tfs-1.5.jar
[ERROR] urls[30] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-manager-plexus/1.5/maven-scm-manager-plexus-1.5.jar
[ERROR] urls[31] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-provider-svn-commons/1.5/maven-scm-provider-svn-commons-1.5.jar
[ERROR] urls[32] = file:/home/sam/.m2/repository/jaxen/jaxen/1.1-beta-8/jaxen-1.1-beta-8.jar
[ERROR] urls[33] = file:/home/sam/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar
[ERROR] urls[34] = file:/home/sam/.m2/repository/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.jar
[ERROR] urls[35] = file:/home/sam/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.jar
[ERROR] urls[36] = file:/home/sam/.m2/repository/org/apache/maven/scm/maven-scm-api/1.5/maven-scm-api-1.5.jar
[ERROR] urls[37] = file:/home/sam/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[38] = file:/home/sam/.m2/repository/org/jdom/jdom/1.1/jdom-1.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[project>org.jenkins-ci.plugins:slack:1.7-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
O_O[sam@blaster:~/git/github/slack-plugin]$

I'm attempting to release.
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform

I get a more specific error Return code is: 401, ReasonPhrase: Unauthorized..  I'll have a more specific error message when I get home.

It seems a large number of developers are having this issue.  On the Jenkins Dev mailing list there are half a dozen or so people raising the issue.  I'll release when I'm able again.

https://groups.google.com/forum/#!topic/jenkinsci-dev/shPgezYr_xk
https://groups.google.com/forum/#!topic/jenkinsci-dev/x36Si5Gc8sI
https://groups.google.com/forum/#!topic/jenkinsci-dev/ftfibR23v5Y

An infrastructure issue has been opened.  https://issues.jenkins-ci.org/browse/INFRA-240

Looks like it was resolved!
https://issues.jenkins-ci.org/browse/INFRA-240

It was resolved :D I'll be doing the plugin release soon.

The plugin has been released.  I don't see it in the update center yet.  It might be delayed before it appears.  I've asked about it in IRC.

I have confirmed in IRC that there is a delay of a few hours.

I'll close this when I confirm the release is available in the Jenkins plugin manager.

http://repo.jenkins-ci.org/webapp/search/artifact/?4&q=slack

Thanks a bunch! Pumped for this :+1:

After reviewing twitter tweets of plugin releases and comparing the release times in artifactory there appears to be a 6-9h delay between the publish in Artifactory and the release actually being available.  I'll check it out tomorrow and see if it is actually released.

Thanks Sam! Good job!

I have verified that Slack Plugin 1.7 is available.  I have configured a Jenkins instance with the 1.2 plugin.  I upgraded to 1.7 with no issues.  Marking this as resolved.


Update MD file on new branch 2017-11-10_14-24-12

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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.


style: create dashboard UI

Create design for a dashboard UI.

The UI should include:

Checkpoint logo on top left
A progress bar to show how much an instance is sync with current and total block number
An input to type the API address of the instance
Social links
A form to query data (similar than on https://hub.snapshot.org/graphql)
A section with the results of the query

Hello guys,
Can i be assigned this task?

@DennohKim Thank you but actually this is not relevant anymore we don't need it. Closing this issue.


Use django's fixtures system to add initial data to the system

Currently the system doesn't come with any initial data. This makes it a necessity to create the data required to test certain functionality. Which in turn slows down development. I suggest adding initial dummy data that resembles the live site's data. Both in terms of quantity and quality.
Django has a builtin mechanism to accomplish such a task called fixtures. So fulfilling this issue is mostly generating data on a clean install and exporting the data using django's fixtures.

Also see #28

On hold until the new system is stablized


Upgrade org.mockito:mockito-errorprone 3.11.2 -> 3.12.0

This PR contains the following updates:

Package
Update
Change

org.mockito:mockito-errorprone
minor
3.11.2 -> 3.12.0

Release Notes

mockito/mockito
v3.12.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
3.12.0

2021-08-19 - 31 commit(s) by EugeneLesnov, Lars Vogel, Logan Rosen, Rafael Winterhalter, Rob Pridham, Tim van der Lippe, dependabot[bot], saurabh7248
Add checks for sealed types (#2392)
Bump versions.bytebuddy from 1.11.10 to 1.11.12 (#2388)
Bump versions.bytebuddy from 1.11.9 to 1.11.10 (#2387)
Bump versions.errorprone from 2.8.0 to 2.8.1 (#2386)
Update StaticMockTest to use unified verify method (#2385)
Reorder InjectMock Javadoc to fit the order of injection (#2383)
Bump core-ktx from 1.5.0 to 1.6.0 (#2382)
Bump google-java-format from 1.10.0 to 1.11.0 (#2381)
Downgrade Android gradle plugin (#2380)
Applied @CheckReturnValue to some classes (#2379)
how to solve gradle sync failed after 'Add basic Android instrumented and unit tests' (#2378)
Bump junit from 1.1.2 to 1.1.3 (#2377)
Bump appcompat from 1.3.0 to 1.3.1 (#2376)
Bump kotlin-gradle-plugin from 1.5.20 to 1.5.21 (#2374)
Bump material from 1.3.0 to 1.4.0 (#2373)
Bump espresso-core from 3.3.0 to 3.4.0 (#2372)
Fixes #2331 (#2369)
Fix typo in exception (#2368)
Bump versions.bytebuddy from 1.11.8 to 1.11.9 (#2367)
Bump versions.errorprone from 2.7.1 to 2.8.0 (#2365)
Bump versions.bytebuddy from 1.11.7 to 1.11.8 (#2361)
Basic Android instrumented and unit tests (closes #2341) (#2360)
Bump versions.bytebuddy from 1.11.6 to 1.11.7 (#2359)
Bump kotlin-stdlib from 1.5.20 to 1.5.21 (#2356)
Bump kotlinx-coroutines-core from 1.5.1 to 1.5.1-native-mt (#2354)
Bump kotlinx-coroutines-core from 1.5.0-native-mt to 1.5.1 (#2353)
Bump versions.bytebuddy from 1.11.5 to 1.11.6 (#2351)
Bump gradle-errorprone-plugin from 2.0.1 to 2.0.2 (#2347)
Bump kotlin-stdlib from 1.5.10 to 1.5.20 (#2343)
Bump versions.bytebuddy from 1.11.3 to 1.11.5 (#2337)
Bump assertj-core from 3.20.1 to 3.20.2 (#2336)
Spy doesn't forward hashcode/equals to actual object (#2331)
Fixes #2311 (#2320)

[ ] If you want to rebase/retry this PR, check this box.

Suggested commit message:
Upgrade mockito-errorprone 3.11.2 -> 3.12.0

See:
- https://github.com/mockito/mockito/releases/tag/v3.12.0
- https://github.com/mockito/mockito/compare/v3.11.2...v3.12.0


It's just better

You can add new domains without deleting certificates of the old, bug fixes, code formatting.

Thank you for this very extensive pull request! I like the changes you’ve added but I would ask you not to rename init-letsencrypt.sh to cerbot.sh. If you change this back, I’d be happy to do a final review and merge your PR.

I renamed certbot.sh to init-letsencryp.sht and made some other improvements & fixes.

I’m merging it in the dev branch so I can give it another try before merging it back in master :)


[WIP]Add OnMarkerCreated,OnMarkerDeletting,etc callbacks

#29
Add listed callback methods in android side MapRenderer.cs that provides chance of customize marker.

OnMarkerCreating
OnMarkerCreated
OnMarkerDeleting
OnMarkerDeleted

👍

Hi @milena23 ,
I released Xamarin.Forms.GoogleMaps v2.3.0-beta1 that includes this PR.
https://www.nuget.org/packages/Xamarin.Forms.GoogleMaps/2.3.0-beta1


Does not build today - duplicate definition

I get this fatal build warning today:
; caught WARNING:
;   Duplicate definition for 5FUN found in one file.
;   See also:
;     The ANSI Standard, Section <IP_ADDRESS>

This commit: https://github.com/gmasching/sucle/commit/70837ab74070dc1197aec0145c064a66e768ee5b
Comments out the other definitions of 5fun, but it also adds other code as well.
So this particular error should be fixed, but the other new code may not build.


Support writing integration documentation in markdown

Fixes #4011

@timabbott, @showell, ready for review.

This seems to not work for me?

Also, maybe we should just auto-detect based on which file exists, rather than needing to configure the filename doc.md?

This seems to not work for me?

Oops. I think I removed the check for existence of help_content. Fixed.

Also, maybe we should just auto-detect based on which file exists, rather than needing to configure the filename doc.md?

Done.
Pushing in a bit.

@timabbott, fixed now. Please review.

Everything looks good except the last commit, which isn't translated faithfully.  E.g. HTML escape sequences aren't correctly replaced with the corresponding character:

Can you fix that?  A good technique is to compare side-by-side the docs on chat.zulip.org with on your branch, so you can easily look for formatting differences.

FYI @umairwaheed I just merged the fix for #4293, which will merge conflict with this a bit.

@timabbott, updated. Please review.

Merged, thanks @umairwaheed!


User/ole

:white_check_mark: Build TheIdServer 2.0.0-user-ole1-0005 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/657c2ef6fc by @aguacongas)


library not supporting format date

Describe the bug
i have a json schema and instance
{
    "properties": {
        "recordingMethod": {
            "type": "string",
            "format": "date"
        }
    }
}

{
    "recordingMethod": "5"
}

Expected behavior
It should show error message
String '5' does not validate against format 'date'. but it is getting validated True

Could you post the code you're using to run the validation, please?  I suspect it's not validating format, which is an annotation by default.
Please see the documentation for validating formats.

Which options have you chosen when validating?  Please see the options documentation.

I have checked with all option but It validated true but it should fail.
you can too try in playground with below schema and instance.
Schema
{
    "properties": {
        "recordingMethod": {
            "type": "string",
            "format": "date"
        }
    }
}

Instance
{
    "recordingMethod": "5"
}

I tried in in the playground when you first reported it.  There is no bug here.
Without format validation:

With format validation:

thank you , now it is working as expected.


Category fixes

Fix an issue where lump categorization could put everything into the default category instead of not using categories.
Also fix https://github.com/TypeStrong/typedoc/issues/991 by splicing the category tag from the comment when the category is resolved.

Hmm, I think because that would involve changing a runtime argument, it would require an entire new test description in https://github.com/TypeStrong/typedoc/blob/master/src/test/converter.test.ts. What do you think, worth adding?

Ah, that's true. In that case, we'll hold off on testing that until we get some test helpers to help with different configs.


composer install on server and it reset all the changes in vendor folder..no publish command?

hi i install the plugin and it creates all the changes in the vendor folder and it works like a charm.
after that i just commit the code on bitbucket it said no change because vendor folder is in the gitingore so i push the code and run composer install on the server it was the original code and i have no changes in my site.
so is there a way to vendor publish etc so I get all the controller/views/models in the original laravel directory as like when we run vendor publish for the laravel markdown emails it copy all the views into laravel default views folder and we can change according to our needs.
please GUID
thanks

only views can be overwritten with usual laravel vendor publish command.
For using your own controllers, you can use a custom routes file to point to other controllers, just change the path to the routes file from the admin settings


Animation not working only when release build

As you can see, there is nothing special to block animation-related actions on my proguard file.
Interestingly, the transition wont work on product-release mode.
I know there is lack of information, but when i enable debugging, then animation will work fine again. (sadly cannot provide any helpful debugging information/log/ect..)
# Add project specific ProGuard rules here.
# You can control the set of applied configuration files using the
# proguardFiles setting in build.gradle.
#
# For more details, see
#   http://developer.android.com/guide/developing/tools/proguard.html

# If your project uses WebView with JS, uncomment the following
# and specify the fully qualified class name to the JavaScript interface
# class:
#-keepclassmembers class fqcn.of.javascript.interface.for.webview {
#   public *;
#}
-keepclassmembers enum * { *; }
# Uncomment this to preserve the line number information for
# debugging stack traces.
#-keepattributes SourceFile,LineNumberTable

# If you keep the line number information, uncomment this to
# hide the original source file name.
#-renamesourcefileattribute SourceFile

app.gradle

    buildTypes {
        release {
            manifestPlaceholders = [enableCrashReporting: "true"]
            shrinkResources true
            zipAlignEnabled true
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            signingConfig signingConfigs.release
        }
        debug {
//            applicationIdSuffix '.debug'
            versionNameSuffix '-DEBUG'
            manifestPlaceholders = [enableCrashReporting: "false"]
            minifyEnabled false
            zipAlignEnabled true
            debuggable true
            signingConfig signingConfigs.debug
        }
    }

    flavorDimensions "version"
    productFlavors {
        dev {
            dimension "version"
            buildConfigField "String", "APP_FLAVOR", "\"dev\""
            manifestPlaceholders = [appLabel: "β SWING"]
        }
        product {
            dimension "version"
            buildConfigField "String", "APP_FLAVOR", "\"product\""
            manifestPlaceholders = [appLabel: "SWING"]
        }
    }

-> turns out to be
only works when debuggable true -> which is not recommanded for release flavor

Hello.
could you please verify that if you specify minifyEnabled true for debug build this stops working for the debug builds as well. this will mean proguard is removing something important.
I will not be able to help you figure out the reason without sharing the code using transitions which stops working for you

        release {
            manifestPlaceholders = [enableCrashReporting: "true"]
/*            shrinkResources true
            zipAlignEnabled true
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'*/
            signingConfig signingConfigs.release
        }

Works for release if proguard related lines are muted

this library works with proguard, I tested it, and there were no other issues created for this issue during all the years library exists. so probably the issue is not directly in the library. and I will not be able to help you without seeing the code you have for not working animation


how do i make cuda work?

git clone code from branch main,
this is cuda home:

i have export env:
export ORT_DYLIB_PATH=/opt/app/models/onnxruntime/lib/libonnxruntime.so.1.20.0
export CUDA_HOME=/opt/app/cuda/
export LD_LIBRARY_PATH=$CUDA_HOME/lib64:$LD_LIBRARY_PATH
export PATH=$CUDA_HOME/bin:$PATH

Run the YOLO example explicitly with --cuda to use CUDA，but the result used cpu:
cargo run -r --example yolo -- --model /opt/app/models/v8-m-dyn.onnx --source /opt/app/models/assets/test.mp4 --cuda

ONNX Runtime 1.20.0 requires a CUDA version higher than 11.8. Please try upgrading CUDA.

ONNX Runtime 1.20.0 requires a CUDA version higher than 11.8. Please try upgrading CUDA.

Now use ONNX Runtime 1.19.2, the result is still CPU:

This could be a mismatch issue between CUDA, CUDA driver, and ONNX Runtime versions. Check your CUDA driver version to see what version of CUDA it supports, and ensure that your CUDA is available. You can also look into the minimum supported CUDA version for ONNX Runtime 1.19.x.

This could be a mismatch issue between CUDA, CUDA driver, and ONNX Runtime versions. Check your CUDA driver version to see what version of CUDA it supports, and ensure that your CUDA is available. You can also look into the minimum supported CUDA version for ONNX Runtime 1.19.x.

ok, thank u, let me check.
Last may I ask how to see the tracing log:

Try this:
fn main() -> anyhow::Result<()> {
    tracing_subscriber::fmt()
        .with_max_level(tracing::Level::Debug)  // log level
        .init();

    // codes
}

You'd better upgrade your CUDA version to 12.x.

Try this:
fn main() -> anyhow::Result<()> {
    tracing_subscriber::fmt()
        .with_max_level(tracing::Level::Debug)  // log level
        .init();

    // codes
}

You'd better upgrade your CUDA version to 12.x.

ok, thank u

cuda 12.2 + libonnxruntime.so.1.19.2
#### nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Tue_Aug_15_22:02:13_PDT_2023
Cuda compilation tools, release 12.2, V12.2.140
Build cuda_12.2.r12.2/compiler.33191640_0

#### echo $ORT_DYLIB_PATH
/opt/temp/onnxruntime-linux-x64-1.19.2/lib/libonnxruntime.so.1.19.2

tracing log:
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.38s
     Running `target/debug/examples/yolo --model /opt/temp/v8-m-dyn.onnx --source /opt/temp/test.mp4 --cuda`
2024-11-21T08:46:10.185956Z  INFO YOLO-new:OrtEngine-new: ort: Loaded ONNX Runtime dylib with version '1.19.2'
2024-11-21T08:46:10.203487Z DEBUG YOLO-new:OrtEngine-new: ort::environment: Environment created env_ptr="0x55c16b74c2a0"
2024-11-21T08:46:10.203624Z  WARN YOLO-new:OrtEngine-new: usls::core::ort_engine: ❌ CUDA initialization failed, Using cpu
2024-11-21T08:46:10.204007Z DEBUG ort::environment: Session Options {  execution_mode:0 execution_order:DEFAULT enable_profiling:0 optimized_model_filepath:"" enable_mem_pattern:1 enable_mem_reuse:1 enable_cpu_mem_arena:1 profile_file_prefix:onnxruntime_profile_ session_logid: session_log_severity_level:-1 session_log_verbosity_level:0 max_num_graph_transformation_steps:10 graph_optimization_level:3 intra_op_param:OrtThreadPoolParams { thread_pool_size: 0 auto_set_affinity: 0 allow_spinning: 1 dynamic_block_base_: 0 stack_size: 0 affinity_str:  set_denormal_as_zero: 0 } inter_op_param:OrtThreadPoolParams { thread_pool_size: 0 auto_set_affinity: 0 allow_spinning: 1 dynamic_block_base_: 0 stack_size: 0 affinity_str:  set_denormal_as_zero: 0 } use_per_session_threads:1 thread_pool_allow_spinning:1 use_deterministic_compute:0 config_options: {  } }
2024-11-21T08:46:10.204066Z DEBUG ort::environment: Flush-to-zero and denormal-as-zero are off
2024-11-21T08:46:10.204125Z DEBUG ort::environment: Creating and using per session threadpools since use_per_session_threads_ is true
2024-11-21T08:46:10.204162Z DEBUG ort::environment: Dynamic block base set to 0
2024-11-21T08:46:10.314694Z DEBUG ort::environment: Initializing session.
2024-11-21T08:46:10.314761Z DEBUG ort::environment: Adding default CPU execution provider.

As you can see from the log that usls::core::ort_engine: ❌ CUDA initialization failed, is there any more detailed information?
fn build_cuda(builder: &SessionBuilder, device_id: usize) -> Result<()> {
    let ep = ort::CUDAExecutionProvider::default().with_device_id(device_id as i32);
    if ep.is_available()? && ep.register(builder).is_ok() {
        Ok(())
    } else {
        anyhow::bail!("{CROSS_MARK} CUDA initialization failed")
    }
}

Your ONNXRuntime library binaries might be incorrect: onnxruntime-linux-x64-1.19.2; you should use the one with -gpu, such as onnxruntime-linux-x64-gpu-1.19.2.
Yours:
#### echo $ORT_DYLIB_PATH
/opt/temp/onnxruntime-linux-x64-1.19.2/lib/libonnxruntime.so.1.19.2

Your ONNXRuntime library binaries might be incorrect: onnxruntime-linux-x64-1.19.2; you should use the one with -gpu, such as onnxruntime-linux-x64-gpu-1.19.2.
Yours:
#### echo $ORT_DYLIB_PATH
/opt/temp/onnxruntime-linux-x64-1.19.2/lib/libonnxruntime.so.1.19.2

A Segmentation Fault error occurs when using onnxruntime-linux-x64-gpu-1.19.2, and generated a core dump file that size is nearly 6GB

Try this two version onnxruntime 1.19.0, onnxruntime 1.20.0
Use CUDA >= 12.0. at least > 11.7
Make sure CUDA is working fine on your machine.
@phial3


Automated cherry pick of #7729: optimized cachedimages sync

Cherry pick of #7729 on release/3.3.
#7729: optimized cachedimages sync

/lgtm
/approve


[11.x] Add middleware to stack before sending the request

Backstory
See my comment.
Problem
The problem is that we currently do not initialise the middleware before sending the request which causes an issue further described in https://github.com/laravel/framework/issues/51980.
Http::globalRequestMiddleware(fn ($request) => $request->withHeader(
    'User-Agent', 'Example Application/1.0'
));

Solution
We should always first add the middleware to the stack and then build any follow-up handler.
This now causes our middleware to be initialised at the right time and the user-agent is now correctly set when listening to the RequestSending event.

No tests.

No tests.

I'll write some tests today. :-)


CubeCon EU + Cloud Native Con 24

Kairos should have a presentation at CubeCon!
https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/
Maybe more relevant: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/co-located-events/kubernetes-on-edge-day/

no luck unfortunately


How to push a subscriber based on clientid？ I only see topic push？

Environment

OS: macos
Erlang/OTP: 20
EMQ: 2.2

Description
I want  push a subscriber based on clientid? but I cann't see the interface? sos
A description of the issue

curl -v --basic -u admin:public -d "qos=1&retain=0&topic=hello&message=sd1234&clientid=localhost_bench_sub_1_3885104127" -k http://<IP_ADDRESS>:8080/mqtt/publish

@hahafeixiu  publish topic $client/

@hahafeixiu
You can get the solution at http://www.emqtt.com/docs/v2/rest.html#id18


[FEATURE] API Gateway

When we were using Micro, it provided an API gateway. It would be nice to have this as a standalone or programmable tool for go-micro once more. Maybe by taking the existing code from Micro. Looking for people who are actively interested in the previous Micro API who want to contribute something.

Micro used to be a powerful tool for me, I can help to bring it back into go-micro.

We've been discussing integrating Gomu into Go Micro in #2220. I'm currently also looking into providing an API gateway in Gomu. Perhaps it would be a wise decision to start integrating Gomu in Go Micro before we're all building stuff that might be difficult to combine?

My experiences with Micro tell me that the single binary approach can often be limiting or too opinionated where people need to add their own integrations. For now I'd like to treat the CLI and the API as two separate things here. The ability for someone to just go get a simple API is fine but it's more likely someone would like to import and build it themselves to include any sort of plugins or additional functionality. So we should keep that in mind and learn from the pitfalls of Micro.

There's already an api package with a HTTP server. Wouldn't this suffice as an API gateway, or do you have other ideas?

I think right now it's too difficult to use. It was a collection of packages created out of the micro api. Let's say I go back to micro v2. You can see how that was used here https://github.com/micro/micro/blob/5f6095b0e09b644efb24b58f87b1dda4244e2e8c/api/api.go. So I think finding a way to make it easy to use without having to piece it all together would be useful e.g I have a cmd/api that basically just copies over what the micro api did and lets me run it out of the box or
import "github.com/asim/go-micro/api"

gw := api.NewAPI()
gw.Register(Endpoint)
gw.Run()

What most people are looking for is a http/json endpoint for their grpc based service and they ideally want to run it in the same process. They might also not want to expose the entire service but a subset of the api. So being able to just register those endpoints is useful. It might mean the current API interface just needs some work to add Run.


more refactoring of API examples and required c++ adjustments

In preparation to drop manual dynamic dispatching in put
This PR is a set of minor API example refactoring changes

Travis finally is green, windows was OK before


Allow ember-es6_template 0.5.x

It allows sprockets 4.0.0.beta.
All changes of ember-es6_template are here:
https://github.com/tricknotes/ember-es6_template/compare/v0.4.3...v0.5.1

The test about assets:precompile is failing:

Sprockets::FileNotFound: couldn't find file 'ember/loader' with type 'application/ecmascript-6+module'
/home/travis/build/emberjs/ember-rails/app/assets/javascripts/ember-rails/application.module.es6:1

ref: https://travis-ci.org/emberjs/ember-rails/jobs/113466614
It is failed on Rails 4.0 & 4.1 (3.2 & 4.2 work fine).
I'm now investigating :eyes:

This seems to be the issue i get when trying to install emberjs-rails on Rails 5 - look at #526
I hope you can fix this really. I don't want to fix emberjs manually.

Closing in favor of https://github.com/emberjs/ember-rails/pull/540


Bump to 0.22.2

Keeping dependencies up-to-date. The release was on Jun 2.
Additionally removing myself from OWNERS file.

/hold
while I agree that we should look at upgrading to v0.22, it might cause problems for users wanting to use newer configuration fields because prometheus-operator isn't on par for all of them:

https://github.com/prometheus-operator/prometheus-operator/issues/4174
https://github.com/prometheus-operator/prometheus-operator/issues/4078

Alertmanager 0.22 is backward compatible, so it doesn't prevent upgrades. Yes, we won't support those new features due to limitations in prometheus-operator, but imho that shouldn't stop us from upgrading a component when it is possible.

/close
closing for obvious reasons ;)


Add feature to show last synchronization time

This closes #384.

Are tests really needed here? It might be complicated to parse the synchronization time back from the dialog title. And how should we know if the sync time is correct (sync might have been completed one or two seconds before our reference time)?


Documentation - we need an KF 1.1 on GCP overview page

I've been getting quite some questions from different channels asking about various questions.
I think current documentation only explained how to deploy Kubeflow 1.1, but it doesn't touch topics below:

Where is kfctl?
Why did we stop using kfctl?
What is Anthos Service Mesh? Can we replace it with istio? How much does it cost? (I couldn't find related documentation)
What is cloud config connector? Why do we use it? https://cloud.google.com/config-connector/docs/overview

These are pretty much all I have in mind right now, there's probably more

/cc @jlewi @8bitmp3
What do you think?

Overview or FAQ?

💯👍!
@Bobgy

What is Anthos Service Mesh?

I can share some of my writing (from May 2020) that we can shorten and include in the @Bobgy @jlewi 's proposed KF 1.1 on GCP Overview/FAQ. I put this together earlier this year to figure out how these GCP parts are related to each other:

"Anthos Service Mesh provides operational control and insights over a service mesh—a network of microservices that make up the applications and the interactions between them. It enables users to get a uniform observability into the workloads, so that they can make informed decisions on routing traffic, security and encryption policy enforcement, and other rule configurations."
"Anthos Service Mesh is a network for services that manages interactions across all services. It uses a distribution of Istio—an open-source implementation of the service mesh infrastructure layer.
...
"Anthos is a broad product suite that helps bridge the worlds of on-prem and cloud-based infrastructure."
"Anthos helps you move applications to the cloud-native world with improved workflow management and reduced operational complexity. You can move workloads from on-prem to the cloud and manage the infrastructure with a consistent set of policies and tools.

@Bobgy

Can we replace it with istio? How much does it cost? (I couldn't find related documentation)

Some of this should also help—especially the Istio on GKE and Anthose Service Mesh distinction:

"For each of Google Cloud's fully-managed solutions, such as Google Kubernetes Engine (GKE) and Istio on GKE, Anthos has equivalent platforms for the on-prem, multi-cloud, and hybrid cloud world:

Fully-managed by Google Cloud
For on-prem, multi-cloud, hybrid cloud

Kubernetes Engine (GKE)
Anthos GKE (On-Prem, for AWS/Azure)

Istio on GKE
Anthos Service Mesh (on GKE)

"Anthos GKE and Anthos Service Mesh are built on open-source Kubernetes and Istio."
"These technologies provide solutions for modern infrastructure and application development challenges by:
"- Decoupling of applications for modularity > with Kubernetes and Istio."
"- Providing scalable configuration management > with Istio."

This may be helpful in the Istio docs on KF:

"Starting from v1.5 as of Q1 2020, the Istio components in the Control Plane—Pilot, Galley, and Citadel—were consolidated into istiod.

I think it's a very valid question as to why with GCP there appears to be a slow tie in with Anthos with these GCP blueprints. It would make sense to offer Istio as an alternative if possible as there are costs I understand with the Anthos route and many users may not want to pay for this.

@jlewi Do you have context why we chose Anthos Service Mesh as builtin support for Kubeflow?
My understanding is an open source istio 1.4 should be functioning the same if users prefer istio.

For cloud config connector and management cluster,
my answer is, that's the Google Cloud opinionated way of declarative cloud resources management. You can use yaml files that can be processed by kustomize to define GCP resources.
Things like providing built-in workload identity bindings as manifest are powered by this new ability.

I too don't understand the requirement for adding in the Anthos Service Mesh as an abstraction layer over istio -- when the user is looking to deploy Kubeflow solely on GCP (not multi-cloud or on-prem).
@8bitmp3

I can share some of my writing ...

Yes, that explains what the Anthos Service Mesh is but it doesn't explain a) why its explicitly needed in a default Kubeflow GCP deployment and b) the transition to the Anthos abstraction layer.

Some of this should also help...

Again, sure, there are many product offerings which can replace open sourced solutions. Ie, for example, Argo can be replaced by another vendor workflow manager.
Another concern would be incurred cost by running the Anthos Service Mesh. As I understand it, it's not inexpensive in comparison to some other GCP services.

I agree with @connorlwilkes.
@Bobgy

my answer is, that's the Google Cloud opinionated way of declarative cloud resources management. You can use yaml files that can be processed by kustomize to define GCP resources.

I'd say Kustomize is increasing in popularity across Kubernetes deployments (vs Helm). Definable YAML files isn't something unique to GCP resource management.
The concerns here are:

The decision to include Anthos Service Mesh as the default deployment for Kubeflow on GCP -- without having provided context or an explanation.
Should Anthos Service Mesh really be the default deployment option for GCP versus open source istio?

Keep in mind Anthos isn't the cheapest*. Not all use may want to include Anthos in their deployment, and may be offput by the effort required to reintegrate open source istio.

https://cloud.google.com/anthos/pricing

For clarification, Anthos Service Mesh is literally managed istio. It's not an abstraction on top.
Therefore, you can replace it with istio, if you got that working, we'd welcome contribution to provide istio as an option.

On GCP we use ACM because it is the recommended way of running ISTIO on GCP. If you want to deploy and run OSS ISTiO instead you are welcome to do so.

Hi all! I've updated with quick answers I drafted in the first comment: https://github.com/kubeflow/gcp-blueprints/issues/123#issue-678249292.
Feel free to let me know if there are further questions.

I would put OSS ISTIO into the bring your own infrastructure bucket.
#53 is tracking installing on existing clusters. I think in this case users would be responsible for setting up a cluster with ISTIO and then continuing to install KF ontop of it.

/priority p1


Proposal for create-react-app, monaco-editor  and sql languages bootstrap repo

Please check out the very basic demo app that aims to showcase monaco-sql-languages and also be a lightweight starting point for CRA-based projects with monaco editor and  monaco-sql-languages support configured
https://github.com/SlickSql/monaco-sql-languages-demo
Just in case you have any interest to collaborate!

@shabalin Thanks for your suggestion,  I think this is a good idea, maybe you can submit a PR that adds a CRA case below README.md Example.


Add commit, branch name, and PR syntax to README

As a developer, I want a guideline for branch names, commit messages, and pull request descriptions
Some suggestions:

We can standardize feature branch names to something like feature/#-issue_title where # is the related issue number and issue_title is the issue title in snake_case
We can keep urgent bug fix branch names to hotfix/description for when there is no related issue
Keep commit messages to present tense, imperative eg. "update README with commit message guideline" (reason)

@tedspare @JDziewonski98 Added guidelines in the repo wiki! Let me know if anything needs to be changed (hopefully I won't need Grammarly lol) https://github.com/hack4impact-mcgill/mu-map/wiki/Code-contribution-guidelines


Paint point increase problem

Some accounts always give 0 PX for painting (no idea why), but this is not only in the script, but even if you paint directly in the game. If you are experiencing this error, I recommend you temporarily remove the problem session

Bro creat a bot for that airdrop it will be end in 20th dec it started at
26nov
https://t.me/YuliGoBot/app?startapp=F775GZ
On Sun, 1 Dec, 2024, 12:03 am Dellenoam, @.***> wrote:

Some accounts always give 0 PX for painting (no idea why), but this is not
only in the script, but even if you paint directly in the game. If you are
experiencing this error, I recommend you temporarily remove the problem
session
—
Reply to this email directly, view it on GitHub
https://github.com/Dellenoam/NotPixelBot/issues/15#issuecomment-2509135549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3QKTHNCZ2X3LNK2ANSVHBD2DIAHTAVCNFSM6AAAAABSYX5PWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGEZTKNJUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


meson: 0.63.0 → 0.63.1

Description of changes
https://github.com/mesonbuild/meson/compare/0.63.0...0.63.1

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

systemd builds.


Future directions in client development

TODO @me: elaborate

Dev call: related to https://github.com/fedimint/fedimint/issues/4287#issuecomment-1937819112, storing JSON instead of Decodable would also be nice


#ref 1987 allowing user to define AddressResolver

@gkorland Mostly LGTM! But a test would help users to understand how to use it.

Looks really close to what we reached in https://github.com/xetorthio/jedis/pull/1942, I was planning on adding a similar thing but for the whole socket. @gkorland would such a change be better, or do you think we need this one as well?

@mina-asham Compared to working on whole Socket, IMO, this PR is closer to both of our expectation.
I said that a custom object to create/connect a socket could be enough.
And you did not prefer to expose socket directly.
I think this PR sets a very good balance on both of our expectations and plans. So, for the time being, we can skip the idea of whole socket and support UDS based on this one. WDYT?
@gkorland ?

@mina-asham Compared to working on whole Socket, IMO, this PR is closer to both of our expectation.
I said that a custom object to create/connect a socket could be enough.
And you did not prefer to expose socket directly.
I think this PR sets a very good balance on both of our expectations and plans. So, for the time being, we can skip the idea of whole socket and support UDS based on this one. WDYT?
@gkorland ?

Happy to do it here, but I don't see how you can support UDS socket, without supporting some sort of socket factory here, am I missing something?

@mina-asham Before answering that, what were you planning to do in #1942 with whole socket? Was it with or without some socket factory?

@mina-asham Before answering that, what were you planning to do in #1942 with whole socket? Was it with or without some socket factory?

Apologies for the uber late reply, here is what I (roughly) intended to do:

Similar to @gkorland commit here, allow passing a SocketFactory in the constructor and propagate as appropriate
Extract this code into a DefaultSocketFactory

https://github.com/xetorthio/jedis/pull/2036#issuecomment-517267028

Happy to do it here, but I don't see how you can support UDS socket, without supporting some sort of socket factory here, am I missing something?

I thought, by socket factory, you meant something like AFUNIXSocket. But it seems you actually meant something like DefaultSocketFactory. Isn't it?

#2036 (comment)

Happy to do it here, but I don't see how you can support UDS socket, without supporting some sort of socket factory here, am I missing something?

I thought, by socket factory, you meant something like AFUNIXSocket. But it seems you actually meant something like DefaultSocketFactory. Isn't it?

Yeah, the Connection class needs to be able to re-create the sockets when they fail, so we cannot supply it with the socket directly. The only way I can see it happening in that case is to supply a JedisSocketFactory interface that has a default implementation covering the current content of the Connection.connect method. This would enable any user to supply any kind of socket creation logic if they need to (e.g. a UDS socket)

@mina-asham agree adding JedisSocketFactory can be the right solution here for both FRs.

@mina-asham Okay, I understand now. As I've mentioned in my previous comment, I was a bit misdirected.

@gkorland @mina-asham any update?

@sazzad16 I was under the impression that we are abandoning my PR for @gkorland's here. @gkorland  tell me if you want me to pick it up instead of you?

Resolved by #2151


Issue events on pulls: update the pulls table

Instead of accidentally creating records in our issues table for pull requests, let's re-introduce the code from #58 (removed in #110)
But make the "update the pull from this GH response" a bit more tolerant of missing fields.
CC @MooreGuy

Why add it back in? You didn't explain why?

Ah, okay, I see, thanks. Yeah, we talked about a few ways we can make this happen. :+1: for this change

This is still happening:
mysql> select count(*) from pulls join issues using (number, repo);
+----------+
| count(*) |
+----------+
|      308 |
+----------+
1 row in set (0.03 sec)


checkRoomJoin() cannot get inviteeList sometimes

Run npm run doctor or wechaty run doctor(for docker user), paste output here
><EMAIL_ADDRESS>doctor /Users/lijiarui/Documents/git/wechaty
> npm run check-node-version && ts-node bin/doctor

><EMAIL_ADDRESS>check-node-version /Users/lijiarui/Documents/git/wechaty
> check-node-version --node ">= 6.9"

node: v7.0.0
npm: v4.0.5

  #### Wechaty Doctor

  1. Wechaty version: #git[7faecd6 0.7.32]
  2. Darwin x64 version 14.5.0 memory 831/16384 MB
  3. Docker: false
  4. Node version: v7.0.0
  5. Tcp IPC TEST: PASS

Expected behavior
emit  room-join event when someone joins the room
Actual behavior
Sometimes, when someone joins the room, we cannot emit room-join event.
Paste the full output logs here with WECHATY_LOG=silly set
SILL Room member({ name: ffc94c25-eda9-91fa-9d80-558d101bd88e })
SILL Room member() check ffc94c25-eda9-91fa-9d80-558d101bd88e from nameMap: {"@e479472340ee83f01aa28c6ce787e8306cb283e14aa0c78aca54a7206b7769bb":"琦琦","@74fc244e14625a45d8f3cd1801e97fe9":"f9a5bf05-871b-6462-22f1-02a93743c975","@819ba74d359cb71202d8ada32f12042f":"9bd02793-1142-e4c5-86f6-2242fc7927ab"}
...
SILL PuppetWebFirer fireRoomJoin() reject() inviteeContactList: , inviterContact: 你

The log showed nameMap isn't updated with the newcomer(ffc94c25-eda9-91fa-9d80-558d101bd88e) of the room when room-joined event failed to emitted.
Trying to find the reason...
First, I suggest changing
catch(e => {
      log.silly('PuppetWebFirer', 'fireRoomJoin() reject() inviteeContactList: %s, inviterContact: %s'
                            , inviteeContactList.map((c: Contact) => c.name()).join(',')
                            , inviter
      )

to log.warn() when  await retryPromise({ max: max, backoff: backoff }, async (attempt: number) => { catch exception.

same at my wechaty.. any workaround yet?

When someone is invited to the group, we can see the invitation message first, which could trigger our room-join event.
However, the rawObj of that contact will come later, means that we might can not get the rawObj when we fire the event.
To fix this, we can check the rawObj before fire the event. if there's no rawObj yet, we hold the event and check it later(like after 10 seconds)

This is because when someone joins the room by scanning QR code, it will add a blank by wechat.
I have fix this bug on #651

Great to hear that problem had already been fixed.
It would be more professional if you could close the related issue right after you fixed it.
Anyway, thanks!


Semantic Release?

Got linked to this by @janl and it looks like it would be pretty great.
https://github.com/boennemann/semantic-release/

I kind of like the idea of automating the release process, although the 'release on every push' approach sounds a bit radical at first.

configure your CI server to release only on the production/deploy/release branch and push your code there in certain intervals

In this case which commit message will be taken to generate the release number?
I'm not familiar with the Angular's git commit message convention or any other, but I'm wondering how we're going to employ that convention across possibly completely random contributors?

configure your CI server to release only on the production/deploy/release branch and push your code there in certain intervals
In this case which commit message will be taken to generate the release number?

The most significant, a breaking change commit message will bump the major version number, a feature commit message will bump the minor version number and a fix message will bump the patch version. If you have a feature and a fix, you get a new minor version number.

I'm not familiar with the Angular's git commit message convention or any other, but I'm wondering how we're going to employ that convention across possibly completely random contributors?

We handle this with a clear CONTRIBUTING.md that explains the format. Angular’s is pretty straightforward, but semantic-release is built so you can hook indoor own commit message analysers, if you like a different flavour. A little more legwork required, but doable. You will, however, have to conform to a specific format, a PR-analyse robot could auto-flag non-matching commit messages.
If you have any more questions, ping me or @boennemann :)

Thanks for putting this up for discussion @mikeal :+1:
@simov

In this case which commit message will be taken to generate the release number?
It's not using the latest commit message, but every message since the last release (or all if no release yet). So if you decide to go for a publish-branch workflow it would take all changes into account and then go with the highest increase type (major, minor, patch, null) it can find.

I can totally understand why you're worried about contributors adhering to this certain style, but I think the fact that Angular successfully applied it to all their projects shows that it's doable.
As @janl said you have to communicate e.g. via CONTRIBUTING.md and ask your contributors to rewrite some messages at times. You could also rebase the changes onto master and rewrite the messages to match the style yourself, but that should be an exception.

All in all it certainly takes some time until everyone is accustomed to this, but I think given how good the changelog that comes out of it is and the other easements semantic-release gives you it's worth it.
Also semantic-release offers a verification hook that runs directly before the actual publish happens and we're currently using it for breaking change detection (Runs the testsuite of the latest release against the current versions and sees if it breaks) ourselves, but you can come up with a lot more heuristics. A few ideas: release a new version only if at least x days have passed since the last one, don't release if coverage drops below a certain threshold, check dependencies for nodesecurity vulnerabilities and don't release if something is up, only release if every commit follows the commit conventions etc.
If there is something unclear or you need features I'm here for you :)


When hiding / opening contacts. In a hidden chat, Unhide climbs

On a non-hidden chat, Unhide climbs.

pending on #48

Implementation changed


extension upload error

Hello,
I used this workflow to upload chrome web store extension, but i got this error Can't upload extension. Enabling 2 step verification on your account is required for security purposes. Please visit https://www.google.com/landing/2step to set it up..
The yaml config file on here.
Can you help me get more information to solve this problem?

I don't know why before using this workflow do not need two step verification.
And now i set the two step verification, everything is working fine.

Hi! Thanks for the usage of my actions and I'm happy to hear you have already solved the issue. Recently Google started to enforce 2-step verification for Chrome Web Store accounts. More details here: https://developer.chrome.com/blog/policy-update-2sv/


fix: remove invalid breakpoints

Issue #, if available:
Description of changes:

only create breakpoint hook with valid breakpoint sizes

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #661 (e7d54aa) into main (15af102) will increase coverage by 0.19%.
The diff coverage is 100.00%.

:exclamation: Current head e7d54aa differs from pull request most recent head c8b9d76. Consider uploading reports for the commit c8b9d76 to get more accurate results

@@            Coverage Diff             @@
##             main     #661      +/-   ##
==========================================
+ Coverage   90.52%   90.72%   +0.19%
==========================================
  Files          98       98
  Lines        3685     3686       +1
  Branches      990      991       +1
==========================================
+ Hits         3336     3344       +8
+ Misses        324      317       -7
  Partials       25       25

Impacted Files
Coverage Δ

packages/codegen-ui/lib/utils/breakpoint-utils.ts
100.00% <100.00%> (+63.63%)
:arrow_up:

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 15af102...c8b9d76. Read the comment docs.


nixos/networkd: add wait-online options

Expose a few options to configure systemd-networkd-wait-online.service. Tested locally.

@ofborg test systemd-networkd systemd-networdk-dhcpserver

might it make sense to split the options into two sections, one that applies to all interfaces and one that applies to individual interfaces? the acme module uses this scheme for configuring certificate properties and seems possibly useful here, eg to configure that a wired interface should be online quickly while a wireless one may take a while.

I don't know, I think I'd be willing to add that complexity if there was any indication that anyone is actually using the per-interface units. By default nothing depends on them.
I think a variety of use cases for them is already covered by systemd.network's RequiredForOnline and RequiredFamilyForOnline options.

Added release notes.

As for explicitly specifying a list of interfaces, I personally mark interfaces managed otherwise, or not managed at all as unmanaged for networkd, instead of setting that, but I can understand people just might want to explicitly hardcode a list.

It seems like making a device Unmanaged is not enough to make systemd-networkd-wait-online ignore it. In my case, networkctl reports
12 wg42     wireguard routable    unmanaged

and succeeds even if my other interfaces are no-carrier, unless I add wg42 to ignoredInterfaces.


Make incremental compilation the default.

Rather anticlimactic :)
Fixes #5915

One funny side effect is that some of our tests fail because they assert rebuilds that are unnecessary with incremental compilation :)


Made Changes in Login and Signup Page

Please assign this issue to me

Please assign this issue to me

In this issue, two contributors are already working. If you can propose a more attractive solution than the existing ones, please go ahead. OR you can create a new issue.

ok

@priyanshu-gupta07 create another issue

Please assign this issue to me

hey, @Gyanthakur  can i work on 404 error pages!!!

hey, @Gyanthakur can i work on 404 error pages!!!

@Kedarnath-Rothe assign to you 404

@Gyanthakur i will try for another issue to but can u take a look at my pr for issue#2

@Gyanthakur i will try for another issue to but can u take a look at my pr for issue#2

create another issue


fix(deps): update kubernetes packages to v0.30.3

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/api
require
patch
v0.30.2 -> v0.30.3

k8s.io/apiextensions-apiserver
require
patch
v0.30.2 -> v0.30.3

k8s.io/apimachinery
require
patch
v0.30.2 -> v0.30.3

k8s.io/cli-runtime
require
patch
v0.30.2 -> v0.30.3

k8s.io/client-go
require
patch
v0.30.2 -> v0.30.3

k8s.io/kubectl
require
patch
v0.30.2 -> v0.30.3

Release Notes

kubernetes/api (k8s.io/api)
v0.30.3
Compare Source

kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.30.3
Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)
v0.30.3
Compare Source

kubernetes/cli-runtime (k8s.io/cli-runtime)
v0.30.3
Compare Source

kubernetes/client-go (k8s.io/client-go)
v0.30.3
Compare Source

kubernetes/kubectl (k8s.io/kubectl)
v0.30.3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated

Details:

Package
Change

k8s.io/apiserver
v0.30.2 -> v0.30.3

k8s.io/component-base
v0.30.2 -> v0.30.3


simple-list fix

fixes https://github.com/nymag/clay-kiln/issues/632

Coverage decreased (-3.1%) to 75.362% when pulling<PHONE_NUMBER>c83eddca286c0ca7f622c1891c82b7 on simplelist-fix into 7982f6ba31498b6898969e8436fd7f1a96af1338 on master.

:+1:


maven protobuf plugin not work properly

I checked out master branch and executed "mvn clean install -DskipTests",  it failed to build with following error:

[ERROR] Failed to execute goal com.github.os72:protoc-jar-maven-plugin:<IP_ADDRESS>:run (generate-sources) on project parquet-protobuf: Error extracting protoc for version 3.5.1: Unsupported platform: protoc-3.5.1-linux-x86_64.exe -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :parquet-protobuf

After I updated the plugin version as same as protobuf version, it pass the build.

--- a/parquet-protobuf/pom.xml
+++ b/parquet-protobuf/pom.xml
@@ -159,7 +159,7 @@
       <plugin>
         <groupId>com.github.os72</groupId>
         <artifactId>protoc-jar-maven-plugin</artifactId>
-        <version><IP_ADDRESS></version>
+        <version>3.5.1</version>
         <executions>
           <execution>
             <id>generate-sources</id>

Do we need to set this version to ${protobuf.version}?
Reporter: Junjie Chen / @chenjunjiedada
Assignee: Gabor Szadovszky / @gszadovszky
Note: This issue was originally created as PARQUET-1493. Please see the migration documentation for further details.

Junjie Chen / @chenjunjiedada:
Hi @gszadovszky
I just tried <IP_ADDRESS>, still failed.  I'm using ubuntu18.04. (uname output: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux)

[INFO] Apache Parquet Protobuf ............................ FAILURE [ 30.834 s]
[INFO] Apache Parquet Scala ............................... SKIPPED
[INFO] Apache Parquet Scrooge ............................. SKIPPED
[INFO] Apache Parquet Hadoop Bundle ....................... SKIPPED
[INFO] Apache Parquet Hive ................................ SKIPPED
[INFO] Apache Parquet Hive Binding Parent ................. SKIPPED
[INFO] Apache Parquet Hive Binding Interface .............. SKIPPED
[INFO] Apache Parquet Hive 0.10 Binding ................... SKIPPED
[INFO] Apache Parquet Hive 0.12 Binding ................... SKIPPED
[INFO] Apache Parquet Hive Binding Factory ................ SKIPPED
[INFO] Apache Parquet Hive Binding Bundle ................. SKIPPED
[INFO] Apache Parquet Hive Storage Handler ................ SKIPPED
[INFO] Apache Parquet Hive Bundle ......................... SKIPPED
[INFO] Apache Parquet Tools ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:10 min
[INFO] Finished at: 2019-01-17T05:08:43+08:00
[INFO] Final Memory: 115M/1593M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.os72:protoc-jar-maven-plugin:<IP_ADDRESS>:run (generate-sources) on project parquet-protobuf: Error extracting protoc for version 3.5.1: Unsupported platform: protoc-3.5.1-linux-x86_64.exe -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :parquet-protobuf

Gabor Szadovszky / @gszadovszky:
@chenjunjiedada,
What environment do you have? Is linux-x86_64 correct?
I'm using Linux Mint 19.1 and it works fine. Travis builds also succeed after this change.
The version number of the plugin and the protobuf version number are not in a tight relation. It should work fine as is.
The latest plugin version is <IP_ADDRESS>. Could you please try upgrading if it fixes your problem?

Gabor Szadovszky / @gszadovszky:
Since it turned out the issue is at the plugin side I'm closing this one.

Gabor Szadovszky / @gszadovszky:
We have also hit by this issue in our internal environment so I've looked into the bug report of the plugin. It seems I was to fast closing this issue as even the plugin has the bug we still need to upgrade to the version where it is fixed. Also it seems safer to use protocArtifact instead of protocVersion to be 100% sure that the actual maven settings takes place when downloading the binaries.

Junjie Chen / @chenjunjiedada:
Thanks
I open a issue there: https://github.com/os72/protoc-jar-maven-plugin/issues/68

Gabor Szadovszky / @gszadovszky:
Hi @chenjunjiedada,
So far, you are the only one who has issues with this plugin. Instead of downgrading the plugin globally, I would suggest to use the plugin version which works for you as a workaround and file an issue for the plugin at https://github.com/os72/protoc-jar-maven-plugin/issues. Let's see, if they can say something.
(Maybe, you'd like to execute the maven command with -X and -e so you'll get some more info.)
Keep this issue open until we know more about the problem.


Exclude variables and functions decorated with HiddenAttribute from tab completion

Steps to reproduce
(not really a bug, but the form kinda fits better. I'll fix the labels)
Some (admittedly edge case) scenarios require declaring a global function or variable containing implementation detail for a larger system. For example, in VSCode's shell integration script and several things in PowerShellEditorServices.
Usually when this is required, a prefix is added to reduce the probability of a naming conflict, but it's still possible to end up in completion results.
[System.Management.Automation.Hidden()] $global:__testing = 'found'

function __testing { [System.Management.Automation.Hidden()] param() }

(TabExpansion2 -inputScript ($s = '$__t') -cursorColumn $s.Length).CompletionMatches
(TabExpansion2 -inputScript ($s = '__t') -cursorColumn $s.Length).CompletionMatches

Expected behavior
No results

Actual behavior
CompletionText ListItemText ResultType ToolTip
-------------- ------------ ---------- -------
$__testing     __testing      Variable [string]$__testing
__testing      __testing       Command …

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

We already handle DontShow so should do HiddenAttribute too.

Is this perhaps not a case of order of execution?

@SeeminglyScience -- Thank you for this feature request.  The WG has reviewed this request and finds it would be very useful include and accepts this request.


FFmepg: Transcode will result in endless ffmpeg process

Describe the bug
Do transcode according to guide: https://ossrs.net/lts/zh-cn/docs/v4/doc/sample-ffmpeg.
If I start a ffmpeg transcode srs process and set the output to same srs process. It will result in endless ffmpeg process being triggered until the system's memory or cpu power exhausted.
Version
SRS 6 or maybe any SRS version support transcode
To Reproduce
Steps to reproduce the behavior:

start srs process: ./objs/srs -c conf/ffmpeg.transcode.conf
publish a rtmp stream: ffmpeg -re -stream_loop -1 -i test.mp4 -vcodec h264 -profile:v baseline -acodec copy  -f flv rtmp://localhost/live/livestream
wait and monitor the ffmpeg processes, or check the srs log.
the ffmpeg processes will be started to do transcode and republish the transcoded stream to same srs process, which will trigger another ffmpeg process to do another transcode, dead endless loops.
e.g. live/livestream_ff will trigger live/livestream_ff_ff;
live/livestream_ff_ff will trigger live/livestream_ff_ff_ff;
... endless;

Expected behavior
the tutorial https://ossrs.net/lts/zh-cn/docs/v4/doc/sample-ffmpeg update, maybe remind the user don't sent the output to same srs process.
Or
refactor the transcode feature, let it only accept certain streams [app]/[stream].

Duplicated to #3516


feat: clamp workspace search to root of current repo

Previously, it was possible for axoproject to reach outside the root of the current repository and find things in the parent repository. This caused problems for our tests, where we might find multiple workspaces and end up preferring cargo-dist itself over the repo we're trying to run tests on.

Good call, done.


Use of other plugin in callback

I'm getting "MissingPluginException(No implementation found for method getAll on channel plugins.flutter.io/shared_preferences)"
In AndroidManifest file
android:name="${applicationName}"
In pub.spec
sdk: '>=2.12.0 <3.0.0'
background_locator: ^1.6.6
I have followed
https://github.com/rekabhq/background_locator/wiki/Use-other-plugins-in-callback
Anyone can help

Ok so if anyone has this problem, follow this for shared_preference and this  for path_provider.


Router: Store returns to initialState on loading different page

I am using the react-router-dom v4 module for my project.
If I add items to my store, they appear in the view. However, if I switch to a different page/ route and return to my page, the items are gone. The state is back at the initialState.
This is my structure:
Router > Switch > Route
  Lane(using the Provider)
    Rooms(using connect, actions)

What am I missing here? Why is it not saving the updates in the store?

You may need to bump your Provider up in the tree to be above the Router.

Thanks for the reply, that's exactly what helped to fix the issue. I wrapped the Provider around the Router:
<Provider>
    <AppRouter />
</Provider>

The full source code(how i implemented the fix) can be found in the close for this issue:
vincentrohde/iot_app#55


convert the ikey part to lowercase in Telemetry name

Issue:
in the backend sdk, the telemetry name sending out will convert the ikey part to lowercase, but the fronend java script will not.
Impacts:

then there will be some inconsistent if both frontend/backend are uses.

and for microsoft internal users, who sending data to Xpert, this difference will causing the creation of 2 different source node, one is in lowercase, and another is not.

Fix
Add  tolower case in file
\ApplicationInsights-JS\JavaScript\JavaScriptSDK\TelemetryContext.ts, line 205

if (!doNotSendItem) {
    this._fixDepricatedValues(envelope);

    if (envelope.name === Telemetry.Metric.envelopeType ||
        this.sample.isSampledIn(envelope)) {
       // Add toLowerCase() in this line
        var iKeyNoDashes = this._config.instrumentationKey().replace(/-/g, "").toLowerCase();
        envelope.name = envelope.name.replace("{0}", iKeyNoDashes);
        this._sender.send(envelope);
    } else {
        _InternalLogging.throwInternal(LoggingSeverity.WARNING, _InternalMessageId.TelemetrySampledAndNotSent,
            "Telemetry is sampled and not sent to the AI service.", { SampleRate: this.sample.sampleRate }, true);
    }
}

Could you send a pull request with the proposed fix?

@XiaoliangHuang, please reactivate if this is still required.


Proper JSX support in the code editor

Try something like this.

+1. It looks ugly :)

Looks like it doesn’t help much :-(

I’ve tried these, all of them don’t work:

https://github.com/timbur/codemirror-jsx/blob/master/jsx.js
https://github.com/rarous/brackets-jsx/blob/master/main.js
https://gist.github.com/jquense/265b46c740da4d20a718
https://github.com/codemirror/CodeMirror/pull/3605

The best I could achieve so far:

Much better than it was. Thanks :+1:

Have you tried https://github.com/antimatter15/codemirror-jsx?
And https://github.com/codemirror/CodeMirror/issues/3122 is still open, we might get something useful from there later.

They highlight most of the JSX in one color:

But we can apply the same hack with hiding error.

I’m closing it until CodeMirror has proper support.

@sapegin @mik01aj Just pinging you that CodeMirror has proper support as of https://github.com/codemirror/CodeMirror/commit/b3f9487046e37facd64196380ebdd8639efc57b5

@petetnt Cooooooool! Thanks!

Oh yeah forgot to add that https://github.com/codemirror/CodeMirror/issues/3745 tracks the issues the mode still might have (it has gotten some great updates in the past few days too)


Merge with "openinsurance.io" / OPIN

https://openinsurance.io: We (Baloise) are already a member of the OPIN community.
Fouad Husseini just recently suggested to merge into the openinsurance.io movement.

Our understanding of "open-insurance" is pretty straight forward

open in the sense of "open-source": hence all recommendations for "open source projects", especially the legal ones regarding IP, should be met
using meritocratic leadership within the individual activities
and doing this as transparent and vendor neutral as possible

Currently "https://open-insurance.org" is simply serving as a lightweight umbrella and "single point of information" gathered (by Baloise Group) around the general open-source movements that recently got our attention: both on insurance company level as well as on a meta / association / initiative level.
We'd really like to see that these principles and ideas align with those behind https://openinsurance.io
In addition to that our idea would be to "use / join / create" industry working groups (e.g. at the Eclipse Foundation; but we're also open for alternatives) that foster these principles. Rather than reinventing the wheel we'd simply like to live by these by many members widely accepted and  industry-proven guidelines and bylaws.

Items 1, 2, and 3 are agreeable principles. OPIN's vision was clearly articulated that open source is the preferred way in developing the concept, standards and framework for Open Insurance.
It is also important to discuss and agree on the multi-faceted aspects involved in creating an industry standard including promoting the concept, design of the common API standard, developer resources, education, training, community building, working groups, legal entity, jurisdiction, governing principles etc.
The whitepaper of OPIN provides an overview for many of these aspects centered around the setup of a non-for-profit foundation.
It is important to have clarity and consensus of what the short, medium and long term objectives are.


Better Reporting from Bluepill

When Bluepill is done running the tests, it generates a single JUnit report that is used by CI systems to determine what happened. This is typically called TEST-FinalReport.xml or something like that.
We have had many problems with reporting and I'm coming to realize that partly it's because we are conflating two distinct uses and trying to fit them in the same JUnit report. Namely, developers care only about the final status, did all the tests pass? If a test failed, why did it fail? JUnit is the ideal format for this, and it should only contain the final status. If we had to retry a test in order to get it to pass, that's fine. Still passed.
The other use is trying to understand which tests are taking too long, which ones are flaky, etc. I think for this we should generate a second report, probably in Chrome's Trace Event Format. This file should be easy to generate because it just contains events.
I think this will also take care of #238, which we haven't moved because there is no good place in JUnit to fit this information.
I would ❤ to hear feedback from the community on whether this is a good idea and if someone wants to get involved and implement it, it seems like it wouldn't be hard to do.

Hi @ob, IMHO we should have 1 final file in junit format with merged results. If you could look at this fastlane plugin. This does an amazing job of merging the junit retries into one 1 report.
As for us QA guys who want to do more detailed analysis, we could leave an additional folder with all individual junit files like, junit.xml, 1.xml (1st retry), 2.xml (2nd retry) and so on.

Agreed we can make the reporting better.

There is some work ongoing from the other team to generate summaries for failed, retried and crashed tests
The work in 1 won't fix #238, we still need a consolidated report to show all the tests done
For our case, we are running tests using parallel "worker simulators". The test sequence does not matter, i.e. no tests would block other tests. I am not sure a trace event plot would help much.


Running away from team mates

i tested the bot and my cell run away from the team mates 1 morre issue to fix
if you test you will see
edit:I like this bot but i still prefer the human mode :3

This bot isn't meant to be played in team mode.

ok


fix: comment about sprite

The 'Draw a red square' comment does not fit this example because this source code shows SDL sprite usage.

Thanks for the fix!


FEAT/added pickle and cleaned target prediction text

Added pickle for the model. I put the pickle dumps and load in the same place, but the load will need to go in the API later for use, along with some formatting text.

Nice work! will have the API setup soon for the pickle load


Hyperparameter setting

Hello, author! Can the parameter be set using tart.sh? The data I reproduced were much more skewed than those in the paper, especially at HuffPost. The 1-shot of 20newsgroup is similar, and the 5-shot is also slightly off. Other data sets also have some biases
10-shot
0.6716720322668552,20newsgroup,0.98,,[],False,,2,../data/20news.json,20newsgroup,0.1,bilstm,False,1,0.001,0.001,,train,7,8,5,10,False,reuters_False_data.json,20,,25,result/5-way_1-shot_20newsgroup_result.csv,False,3,1,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
5-shot
0.7930320369005204,20newsgroup,0.98,,[],False,,2,../data/20news.json,20newsgroup,0.1,bilstm,False,1,0.001,0.001,,train,7,8,5,10,False,reuters_False_data.json,20,,25,result/5-way_5-shot_20newsgroup_result.csv,False,3,5,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
1-shot
0.39820801581442355,0.08724249734104635,huffpost,0.98,,[],False,,2,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.001,0.001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/5-way_1-shot_huffpost_result.csv,False,3,1,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
5-shot
0.5700000269412995,0.07295171397582322,huffpost,0.98,,[],False,,2,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.001,0.001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/5-way_5-shot_huffpost_result.csv,False,3,5,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec

If your question is whether you can modify the parameters in the tart.sh, then the answer is yes, you can modify the training parameters in the tart.sh.
Did you complete the whole training process? From the results, it seems that the model has not converged. The training process adopts an early stop strategy, so you need to wait until the training is complete before you can test the model.

Thank you for you reply. Yeah， I finish my training process. I find the lr is 1e-4 in paper, but is 1e-3 in tart.sh, I try to adopt it. But HuffPost also has a gap of about 8%  between paper results and mine.
huffpost,5,5,0.6065440267622471,0.07793038303663903,huffpost,0.98,,[],False,,0,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.0001,0.0001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/result.csv,False,2023,5,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
huffpost,5,5,0.622424027711153,0.07208093032779118,huffpost,0.98,,[],False,,3,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.0001,0.0001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/result.csv,False,23,5,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
huffpost,5,5,0.601120027512312,0.07660408752546764,huffpost,0.98,,[],False,,2,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.0001,0.0001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/result.csv,False,3,5,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
huffpost,5,1,0.4164080185294151,0.08415848390306922,huffpost,0.98,,[],False,,3,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.0001,0.0001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/result.csv,False,23,1,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
huffpost,5,1,0.4134400177299976,0.09202907724314832,huffpost,0.98,,[],False,,2,../data/huffpost.json,huffpost,0.1,bilstm,False,1,0.0001,0.0001,,train,16,20,5,10,False,reuters_False_data.json,20,,25,result/result.csv,False,3,1,,1000,100,1000,,100,5,../pretrain_wordvec/wiki.en.vec,../pretrain_wordvec
re
and my Hyperparameter following
python ../src/main.py
--cuda=$cuda
--way 5
--shot 5
--query 25
--mode train
--dataset=$dataset
--data_path=$data_path
--n_train_class=$n_train_class
--n_val_class=$n_val_class
--n_test_class=$n_test_class
--embedding bilstm
--train_episodes 100
--k 1
--lr_g 1e-4
--lr_d 1e-4
--Comments "huffpost"
--patience 20
--seed 3\
python ../src/main.py
--cuda=$cuda
--way 5
--shot 1
--query 25
--mode train
--dataset=$dataset
--data_path=$data_path
--n_train_class=$n_train_class
--n_val_class=$n_val_class
--n_test_class=$n_test_class
--embedding bilstm
--train_episodes 100
--k 1
--lr_g 1e-4
--lr_d 1e-4
--Comments "huffpost"
--patience 20
--seed 3\

May I see the outputs of the last several episodes? Once it finished training, you should see "End of training. Restore the best weights". Then it will start evaluate the performance with the testing dataset.

5-shot task
2023-08-07 12:48:45.603522, ep 28, val   acc: 0.6202 ± 0.0584, train stats G_grad: 0.2615, clf_grad: 0.1108
---------------ep:29 acc:0.6704000294208526-----------
2023-08-07 12:48:51.198213, ep 29, val   acc: 0.6303 ± 0.0526, train stats G_grad: 0.2363, clf_grad: 0.1077
---------------ep:30 acc:0.7841600334644317-----------
2023-08-07 12:48:57.627295, ep 30, train acc: 0.6763 ± 0.0754
2023-08-07 12:49:04.887994, ep 30, val   acc: 0.6158 ± 0.0597, train stats G_grad: 0.1636, clf_grad: 0.0858
2023-08-07 12:49:04.888127, End of training. Restore the best weights
2023-08-07 12:50:16.307526, test acc mean  0.6210, test std  0.0773

On our server, it typically takes about 60 epochs to converge on the huffpost dataset. If you keep the same batch size and the lr rate, it should produce the similar results. Did you utilize the same environment? I‘m not sure if a different version of pytorch would cause this problem.

We just uploaded the pre-trained weights for better reproduce. Hope this helps.

We just uploaded the pre-trained weights for better reproduce. Hope this helps.

Thank you for uploaded the pre-trained weights, where is the link

It's on the Readme page, next to dataset info.
On Wed, Dec 6, 2023 at 4:52 AM 高云龙 @.***> wrote:

We just uploaded the pre-trained weights for better reproduce. Hope this
helps.
Thank you for uploaded the pre-trained weights, where is the link
—
Reply to this email directly, view it on GitHub
https://github.com/slei109/TART/issues/1#issuecomment-1842812790, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKHMT74CHDPR7IKAFWDZMT3YIBS7XAVCNFSM6AAAAAA3FS7SNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSHAYTENZZGA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


PDF export fails

Chrome gives an ERR_INVALID_RESPONSE after waiting like 30 secs. Do you have any idea?
(It used to work. I have mPDF)

Can't really help without code example.

Okay. It seems to be rather a webserver problem, it occurs if generating the PDF keeps long but the connection is closed to avoid DDoS or whatever. set_time_limit ( ) should help.

I was having the same issue (ERR_INVALID_RESPONSE on Chrome, and File Not Found on Firefox).
The problem is that I was using some unlikely chars in the filename (white spaces, accented chars, ...).
It's important to use an UNIX / WEB standardized filename to avoid this problem.


typo update spark connnector version compatibility instructions

Proposed changes
Issue Number: close #xxx
Since version 1.0,  The keysType attribute is added to the return value of /api/<db>/<table>/_schema API.
Therefore, the spark connector version 1.0.1 is not compatible with doris version 1.0 and later.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Enable smart contract addresses in contacts store

Right now, we're checking that an entered contact has a valid G... address. We should update this add function so it can check for and allow contacts with smart contract C... addresses.

Hi @ElliotFriend please i will like to work on this issue when the OD hack begins

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello, I am Manuel, a process engineer and web3 developer. I have participated in Starknet Bootcamps and am an Elite winner of Speedrunstark. I have a high capacity to solve problems. I am a member of the DojoCoding community.
I hope this issue is assigned to me. I am available to work immediately to achieve what is required in the shortest time possible.
How I plan on tackling this issue
To address the requirements of the issue, I will:

Update the add function in the contacts store to accept and validate smart contract addresses that start with "C...".
Modify the existing validation logic to check for both standard G... addresses and the new C... addresses.
Ensure that the input format for smart contract addresses adheres to any relevant standards or patterns.
Test the updated add function to verify that it correctly accepts valid smart contract addresses and rejects invalid ones.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a SC developer
How I plan on tackling this issue
I can work on this

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i'm a solidity and cairo smart contract  developer with over 2 years experience and believe i have the skill set for the task and i am also very good with smart contract testing

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
GM, I am Sagar Rana, a smart contract developer and full stack engineer. I have 3 years of experience building robust full stack applications and over a year of writing smart contracts. You can see my projects and contributions to some major repos on my GitHub profile. The tech stack I use mainly includes Solidity, Rust, JavaScript and Typescript. I am also contributing to the Starknet and Rust ecosystems and building on Cairo and Rust languages. I am interested in contributing to projects like this to learn more about these technologies and help make these projects better. Please assign me as I would be really glad to be a contributor in this project! :)
How I plan on tackling this issue
Hi @ElliotFriend, I would approach this issue like this:

We can add an extra check in the add function to check for both valid Ed25519 public keys and Smart Contract addresses. Here's the relevant code for the C...address checking:

const isValidContractAddress = StrKey.isValidContract(contact.address);

The if condition has to be changed now to be isValidEd25519PublicKey || isValidContractAddress so that either of the two being true will successfully execute the function.

Tasks:

[ ] Implement the C... contract checking logic

ETA: 5 Hours

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
hello i am Shantel, a blockchain developer .and technical writer ,i have a high capacity to tackle issues. i hope this issue is assigned to me , i am avalaible to work
How I plan on tackling this issue
i will approach the problem with the following:

Update Validation Logic: Modify the existing validation function for contact addresses to include checks for both G... and C... addresses.
Identify Address Types: Ensure the function can differentiate between a regular G... address and a smart contract C... address, validating the format appropriately.
Adjust Add Function: Update the add function to allow the entry of C... addresses, ensuring it calls the modified validation logic.
Test Functionality: Test the updated function to ensure it correctly accepts both types of addresses without errors.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I  am  a  blockchain developer with experience in smart contract integration,
How I plan on tackling this issue
To tackle the issue, I would:
Examine the existing address validation logic for G... addresses.
Determine the criteria for validating C... addresses, ensuring they conform to the expected format.
Modify the add function to include a check for both G... and C... addresses, allowing valid C... addresses to be accepted.
Implement tests to ensure both types of addresses are validated correctly without breaking existing functionality.
Update any relevant documentation to reflect the changes in address validation.

Hi @ElliotFriend, sorry for the late follow up.
I have understood what I need to do for this issue, but I have a few questions:

Since there's no function to check for C... addresses in the stellar-base package, I would have to create a custom function for it. From what I can see in the isValidEd25519PublicKey definition in the node_modules, these are the criteria for the C... address:

length === 56
address[0] === "C"

Should I write the custom function in src/lib/utils/devHelpers.js or somewhere else?

PS.: Please accept my friend request on Discord (I am kxizen on Discord) so that we can have faster communications :)


Add and expose basic audit

While looking at http://localhost:5000/overview/?sort=annexed_files_in_wt_count-desc&page=5 I saw that e.g. https://github.com/OpenNeuroDerivatives/ds003242-fmriprep.git has no metadata for it, but cloning it locally showed that it has lots of annexed files in the tree etc.  So something did happen which prevented populating its record with metadata.  It would probably hard to impossible to figure out what has happened.
I think we might better right away establish basic audit for our entries.  Let's

create a table with model along the

id: int
url_id: int (external key from URL)
datetime: db.DateTime
success: bool
message: str

for the tasks of clone, update, get basic info, extract metadata - record that it happened or errored out, storing error out detail in message
add endpoint for /audit for a given url to just return json list of those records
add column audit with count of audit messages and URL which would lead to that /audit endpoint (we might improve it later on, first just want to see all)

I think it is a good idea to add the audit feature.
For the particular example of https://github.com/OpenNeuroDerivatives/ds003242-fmriprep.git, I am able to see the the metalad_core metadata listed. Do you mean some other URL instead?

The monitoring service collects and logs information of each execution of a task in a database file. This information of each execution includes the following.

The task that is executed
The arguments used in the execution
The date and time the task is received by the worker
The date and time the task is started by the worker
The date and time the task is completed by the worker
The result of the execution or the exception resulted with traceback
If the task has been retried
How many times the task has been retried if retried has been issued

From the arguments used in the execution, we can find out exactly which dataset URL is involved in a task execution that involves a dataset URL. From a logged exception with traceback, we can find out exact how a task fails. The logging of time in various aspects of running a task in the Celery worker by the monitoring services is more than fulfilling the intents of the originally proposed audit system. All the logged information regarding executing/executed tasks are also available through the API of the monitoring service at /api/tasks
Because of the aforementioned properties of the monitoring service, I think the monitoring service fulfills the goal of this issue and this issue should be closed as complete.
Note: The monitoring service offers many other features beyond what is mentioned, such as monitoring Celery workers in the cluster and changing the properties of these workers. For more information, please check out its official documentation.

another use-case I just ran into and wanted to discover what is happening is the ds000105 (may be other openneuro datasets). https://registry.datalad.org/overview/?query=ds000105+openneuro&sort=update-desc  . We have bids_dataset extractor available for https://datasets.datalad.org/openfmri/ds000105/.git but not for the original one on github: https://github.com/OpenNeuroDatasets/ds000105.git . Requires checking what is happening but it is likely we do not even have that anywhere available anywhere?

At this point, we can no longer find how the bids_dataset was executed for https://github.com/OpenNeuroDatasets/ds000105.git because DL-Registry last updated it on
2023-10-22T05:01:57+0000 and Flower only has info on the 100,000 most recently executed tasks.
I asked a question on Flower's repo https://github.com/mher/flower/discussions/1382.
The task info we are looking for is available through Flower's API (https://flower.readthedocs.io/en/latest/api.html#get--api-tasks and https://flower.readthedocs.io/en/latest/api.html#get--api-task-info-(.*)). We may have to retrieve the info we need through the API, and save it to our own database.

Per @yarikoptic a quick solution for now is:

[ ] Ensure errors of execution of tasks are logged with traceback.
[ ] Have all the logs saved in a file instead of just on the container log
[ ] Make sure the log file is in a bind mount directory of the host system


add authorization token

#75

This completes ticket #26.

Run gofmt on this and then I'll merge it.

done.
On Thu, Feb 25, 2016 at 3:55 PM, Don Brower<EMAIL_ADDRESS>wrote:

Run gofmt on this and then I'll merge it.
—
Reply to this email directly or view it on GitHub
https://github.com/ndlib/bendo/pull/92#issuecomment-188982008.


apache-fpm (and probably apache-cgi) webserver_type don't work on windows

Describe the bug
Ooops. We never tested apache-fpm on Windows, (and don't have automated tests yet). And we probably weren't planning on automated tests on Windows for apache-fpm :(
Basically, we generate a username in apache's envvars directory, and it comes out to be uid_0, but we don't have uid_0 in /etc/passwd.
To Reproduce
Try running any project with apache-fpm for the webserver type on Windows. It doesn't work.
Additional context
This can be fixed by just adding uid_0 and gid_0 to the /etc/passwd and /etc/group file, I think.

Just confirming what you've already said here. I'm getting this error after doing ddev config and setting it to apache-cgi or apache-fpm.
Failed to start test2: web service health check timed out: labels map[com.ddev.site-name:test2 com.docker.compose.service:web] timed out without becoming healthy, status=unhealthy

@Outdoorsman Would love to have you test the artifacts for #1111 in https://circleci.com/gh/drud/ddev/3537#artifacts/containers/0

@rfay I installed .exe file in Windows from above and got this error...
#1: PHP Warning: igbinary_unserialize_header: unsupported version: "O:44"..., should begin with a binary version header of "\x00\x00\x00\x01" or "\x00\x00\x00\x02" in /var/www/html/example.com/typo3_src-6.2.31/typo3/sysext/core/Classes/Cache/Frontend/VariableFrontend.php line 99

Do you have some post-start steps in your config.yaml? Please comment them out for now if you would, and do a ddev rm and a ddev start again.

Wait a minute. TYPO3 6.2? We haven't ever deliberately supported anything before TYPO3 8... ???

Oops, yes this was in config.yaml. I did a ddev remove and ddev start again and got the same error.
hooks:
  post-start:
  - exec: sudo apt-get remove --yes php-igbinary

This may just be a TYPO3 6.2 issue as you're pointing out. My personal reason for needing Apache is because I can't get TYPO3 4.5 or 6.2 to run in Nginx and I have ton of these to update still.

Can you point me to some step-by-step instructions on how to do a simple 6.2 project? Maybe you could do one and see if you have this problem on a plain vanilla TYPO3 6.2. Push it to github or give me a tarball? I'll give it a try. But I don't have that much expertise with TYPO3 in general, and certainly not with old versions.


Issue in Search Bar with Thunder Client

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.57
OS Version: Mac OS 11.4

Steps to Reproduce:

Install Thunder Client Ext. (https://github.com/rangav/thunder-client-support)
Create New Request
Add Header Name
Open Search Bar and Paste anything

https://user-images.githubusercontent.com/47683556/122523741-fa3b5000-d034-11eb-8192-c3821a2291d0.mov

/causedByExtension
Please report this on the extension repo. If the extension author believes the problem lies within VS Code (e.g. a regression on a recent release) they should raise an issue here.

This is vscode bug - #127881