Updater ISSUE in Windows Installer .msi

The updater on Windows instead of running the installation, the Windows Installer window appears with the arguments.
Image (Displayed in italian):

Can you please provide more info about your tauri version and the updater plugin version?

[-] Packages
- tauri [RUST]: 2.0.0-beta.22
- tauri-build [RUST]: 2.0.0-beta.17
- wry [RUST]: 0.40.1
- tao [RUST]: 0.28.0
- @tauri-apps/api [NPM]: 2.0.0-beta.13
- @tauri-apps/cli [NPM]: 2.0.0-beta.20
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
- framework: React
- bundler: Vite
I'm using the latest version in beta of Tauri (Updater, Shell ...)

The same ISSUE also appears in executable installer and shows msiexec.exe with instruction of parameters and arguments.

same problem

YES, this is the problem using the latest version of Tauri Updater plugin. The problem is the lack of running the installer with the argument: /quite, /passive ... as it was in version 1v of Tauri now removed in the configurations.

Same problem.
https://discord.com/channels/616186924390023171/731495028677148753/1250023043649110089

@tauri-apps/plugin-updater npm package version: 2.0.0-beta.5

tauri-plugin-updater rust package version: 2.0.0-beta.7

I can give any other information needed.

Wait in the updater plugin configuration, is the windows configuration still there or not?
In the repository documentation there are only endpoints and pubkey.

Yeah, it's right there.

if I run this command I get the same error window.
msiexec src-tauri\target\release\bundle\msi\***_x64_en-US.msi /passive
If I use the /i paramter before the msi file path the problem is solved.
msiexec /i src-tauri\target\release\bundle\msi\***_x64_en-US.msi /passive

Yeah, if everyone need parse this command to update is not really good.

Wait in the updater plugin configuration, is the windows configuration still there or not?
In the repository documentation there are only endpoints and pubkey.
I found something here: https://github.com/tauri-apps/plugins-workspace/blob/v2/plugins/updater/tests/app-updater/tauri.conf.json

I didn't write this part (plugins->updater->windows) in the configuration because the default value is /quiet. Should I write it?

Wait in the updater plugin configuration, is the windows configuration still there or not?
In the repository documentation there are only endpoints and pubkey.
I found something here: https://github.com/tauri-apps/plugins-workspace/blob/v2/plugins/updater/tests/app-updater/tauri.conf.json

I didn't write this part (plugins->updater->windows) in the configuration because the default value is /quiet. Should I write it?

I don't know if this works but in the documentation doesn't say anything about windows argument.

Thanks for all the reports :) This is a consequence from https://github.com/tauri-apps/plugins-workspace/pull/1054, i assume only the nsis updater was tested in that PR because conceptually it can't work with msi installers. The PR changed the updater to call the updater bundles directly instead of going through powershell but .msi files are not executable by themselves so we must use msiexec again to install the msi.

So before I fix this, should I only use NSIS for my Tauri application to use the updater functionality (.exe Current to .exe New)?

I have a question:

How to change in .exe installer instead of Windows Installer (.msi) in Github Action workflow with Tauri Action?

Assuming the exe installer is already being uploaded you can add updaterJsonPreferNsis: true to the tauri-action step to make the action prefer the exe installer in latest.json.

This is my workflow:
name: "Publish"

on:
  push:
    branches:
      - main

  workflow_dispatch:

jobs:
  publish-tauri:
    permissions:
      contents: write
    strategy:
      fail-fast: false
      matrix:
        include:
          - platform: "macos-latest"
            args: "--target aarch64-apple-darwin"
          - platform: "macos-latest"
            args: "--target x86_64-apple-darwin"
          - platform: "ubuntu-22.04"
            args: ""
          - platform: "windows-latest"
            args: ""

    runs-on: ${{ matrix.platform }}
    steps:
      - uses: actions/checkout@v4

      - name: setup node
        uses: actions/setup-node@v4
        with:
          node-version: lts/*

      - name: install Rust stable
        uses: dtolnay/rust-toolchain@stable
        with:
          targets: ${{ matrix.platform == 'macos-latest' && 'aarch64-apple-darwin,x86_64-apple-darwin' || '' }}

      - name: Rust cache
        uses: swatinem/rust-cache@v2
        with:
          workspaces: './src-tauri -> target'

      - name: install dependencies (ubuntu only)
        if: matrix.platform == 'ubuntu-22.04'
        run: |
          sudo apt-get update
          sudo apt-get install -y libwebkit2gtk-4.1-dev libappindicator3-dev librsvg2-dev patchelf

      - name: install frontend dependencies
        run: npm install

      - uses: tauri-apps/tauri-action@v0
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
          TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
        with:
          tagName: v__VERSION__
          releaseName: "TextPad32 (TP32) v__VERSION__"
          releaseBody: "See the assets to download this version and install."
          releaseDraft: false
          prerelease: false
          args: ${{ matrix.args }}

Where can i add updaterJsonPreferNsis: true?

      - uses: tauri-apps/tauri-action@v0
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
          TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
        with:
          tagName: v__VERSION__
          releaseName: "TextPad32 (TP32) v__VERSION__"
          releaseBody: "See the assets to download this version and install."
          releaseDraft: false
          prerelease: false
          args: ${{ matrix.args }}
          updaterJsonPreferNsis: true # <---

      - uses: tauri-apps/tauri-action@v0
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          TAURI_SIGNING_PRIVATE_KEY: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY }}
          TAURI_SIGNING_PRIVATE_KEY_PASSWORD: ${{ secrets.TAURI_SIGNING_PRIVATE_KEY_PASSWORD }}
        with:
          tagName: v__VERSION__
          releaseName: "TextPad32 (TP32) v__VERSION__"
          releaseBody: "See the assets to download this version and install."
          releaseDraft: false
          prerelease: false
          args: ${{ matrix.args }}
          updaterJsonPreferNsis: true # <---

Thank you. 👍

Thanks for all the reports :) This is a consequence from https://github.com/tauri-apps/plugins-workspace/pull/1054, i assume only the nsis updater was tested in that PR because conceptually it can't work with msi installers. The PR changed the updater to call the updater bundles directly instead of going through powershell but .msi files are not executable by themselves so we must use msiexec again to install the msi.

I did test it, it worked just fine on my machine, guess it's not on every machine

I think the problem was more related to passing /ARGS flag to the .msi which is not supported by msiexec, anyways I opened #1454 to fix that and to also use msiexec directly which should be more resilient

To be honest, those built-in associations are not very reliable, open powershell here breaks if there's ' in the path (a game I played has it in the folder name Don't Starve Togther 😂) (this is fixed in powershell 7 and windows terminal)

Hmm I still am having issues. It says "success" but the update isn't applied.


How to set default time range

Hi Cheng. I am wondering that can I set the default start time and end time at the very first rendering.  For example, I want the timeline displaying the experiments I ran last week. So that I can set the time range from start_time_last_week to end_time_last_week.
Also, I want to support user to define the start time and end time by using date picker.

Does your component support this feature? Thank you!

No for now because d3Timeline will calculate the startTIme and endTime in data, and the time range will be [startTime, endTime], when you change data, the range will be changed. If there is no data (data is a blank array), the default range is [startOfYear, new Date()].
I think that you want is to be able to change the display area ? If it's that, I can add this feature later.

Yes. Exactly! What I want is user can set the display area by picking the dates they want. It will be great If you have time to add it as soon as possible. Thanks again!


[feature request] bracket open/close highlighting

I'm not sure if this is already possible, but I couldn't find a method to do it. But if not then there should be a feature that when your text cursor is on a bracket, it shows you where that bracket opens/closes.

I'm not sure if this is already possible, but I couldn't find a method to do it. But if not then there should be a feature that when your text cursor is on a bracket, it shows you where that bracket opens/closes.

The bracketmatch plugin should provide that.

Thank you, seems to be what I'm looking for.


Set-TargetResource is not working if we change the default values in AccountPolicy DSCResource

Hi Team,
I am trying to update Password policies using AccountPolicy resource. But if i change the default value in the parameter it fails. Example Minimum_Password_Length from 12 to 16 . When the values match the default values in Password Policy my configuration succeeds(Obviously). Please find the configuration below.
WINDOWS SERVER 2012 R2
    Import-DscResource -ModuleName SecurityPolicyDsc

    Node "localhost"
    {

        AccountPolicy Account-Policy #ResourceName
        {
            Name = "PasswordPolicies"
            Maximum_Password_Age = 45
            Minimum_Password_Age = 1
            Minimum_Password_Length = 16
            Account_lockout_duration = '600'
            Account_lockout_threshold = '5'
            Password_must_meet_complexity_requirements = 'Enabled'
            Reset_account_lockout_counter_after = '60'
            Store_passwords_using_reversible_encryption = 'Disabled'
        }
    }

    }

    CIS-AC-POL -OutputPath c:\dsc\
    Start-DscConfiguration -Path c:\dsc\ -Wait -Force -Verbose -debug

The above configuration fails with the below log.
PS C:\Windows\system32> C:\Users\Administrator\Documents\Account.ps1

    Directory: C:\dsc

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       11/18/2017   9:21 PM           2584 localhost.mof
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalCon
figurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer IP-0A000174 with user sid S-1-5-21-4016039557-2088680779-57283892-500.
VERBOSE: [IP-0A000174]: LCM:  [ Start  Set      ]
VERBOSE: [IP-0A000174]: LCM:  [ Start  Resource ]  [[AccountPolicy]Account-Policy]
VERBOSE: [IP-0A000174]: LCM:  [ Start  Test     ]  [[AccountPolicy]Account-Policy]
VERBOSE: [IP-0A000174]:                            [[AccountPolicy]Account-Policy] Testing AccountPolicy: Maximum_Password_Age
VERBOSE: [IP-0A000174]:                            [[AccountPolicy]Account-Policy] Current policy: 42 Desired policy: 45
VERBOSE: [IP-0A000174]: LCM:  [ End    Test     ]  [[AccountPolicy]Account-Policy]  in 0.3120 seconds.
VERBOSE: [IP-0A000174]: LCM:  [ Start  Set      ]  [[AccountPolicy]Account-Policy]
DEBUG: [IP-0A000174]:                            [[AccountPolicy]Account-Policy] Temp inf C:\Windows\TEMP\SecurityPolicy.inf
VERBOSE: [IP-0A000174]:                            [[AccountPolicy]Account-Policy] Testing AccountPolicy: Maximum_Password_Age
VERBOSE: [IP-0A000174]:                            [[AccountPolicy]Account-Policy] Current policy: 42 Desired policy: 45
VERBOSE: [IP-0A000174]: LCM:  [ End    Set      ]  [[AccountPolicy]Account-Policy]  in 1.6380 seconds.
PowerShell DSC resource MSFT_AccountPolicy  failed to execute Set-TargetResource functionality with error message: Failed to update Account
Policy Maximum_Password_Age,Minimum_Password_Age,Minimum_Password_Length. Refer to %windir%\security\logs\scesrv.log for details.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

VERBOSE: [IP-0A000174]: LCM:  [ End    Set      ]
The SendConfigurationApply function did not succeed.
    + CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MI RESULT 1
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 2.915 seconds```

DSCConfigurationStatus:

```PS C:\Users\Administrator\Documents> $Status.ResourcesNotInDesiredState

ConfigurationName    : CIS-AC-POL
DependsOn            :
ModuleName           : SecurityPolicyDsc
ModuleVersion        : <IP_ADDRESS>
PsDscRunAsCredential :
ResourceId           : [AccountPolicy]Account-Policy
SourceInfo           : C:\Users\Administrator\Documents\Account.ps1::7::9::AccountPolicy
DurationInSeconds    : 1.544
Error                : {
                           "Exception":  {
                                             "Message":  "PowerShell DSC resource MSFT_AccountPolicy  failed to
                       execute Set-TargetResource functionality with error message: Failed to update Account Policy
                       Maximum_Password_Age. Refer to %windir%\\security\\logs\\scesrv.log for details. ",
                                             "Data":  {

                                                      },
                                             "InnerException":  {
                                                                    "ErrorRecord":  "Failed to update Account Policy
                       Maximum_Password_Age. Refer to %windir%\\security\\logs\\scesrv.log for details.",
                                                                    "WasThrownFromThrowStatement":  true,
                                                                    "Message":  "Failed to update Account Policy
                       Maximum_Password_Age. Refer to %windir%\\security\\logs\\scesrv.log for details.",
                                                                    "Data":
                       "System.Collections.ListDictionaryInternal",
                                                                    "InnerException":
                       "System.Management.Automation.RuntimeException: Failed to update Account Policy
                       Maximum_Password_Age. Refer to %windir%\\security\\logs\\scesrv.log for details.",
                                                                    "TargetSite":
                       "System.Collections.ObjectModel.Collection`1[System.Management.Automation.PSObject]
                       Invoke(System.Collections.IEnumerable)",
                                                                    "StackTrace":  "   at
                       System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)\r\n   at
                       System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean
                       performSyncInvoke)\r\n   at
                       System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace
                       rsToUse, Boolean isSync)\r\n   at
                       System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1
                       input, PSDataCollection`1 output, PSInvocationSettings settings)\r\n   at
                       System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input,
                       PSDataCollection`1 output, PSInvocationSettings settings)\r\n   at
                       System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
                       settings)\r\n   at Microsoft.PowerShell.DesiredStateConfiguration.Internal.ResourceProviderAdapt
                       er.ExecuteCommand(PowerShell powerShell, ResourceModuleInfo resInfo, String operationCmd,
                       List`1 acceptedProperties, CimInstance nonResourcePropeties, CimInstance resourceConfiguration,
                       LCMDebugMode debugMode, PSInvocationSettings pSInvocationSettings, UInt32\u0026
                       resultStatusHandle, Collection`1\u0026 result, ErrorRecord\u0026 errorRecord, PSModuleInfo
                       localRunSpaceModuleInfo)",
                                                                    "HelpLink":  null,
                                                                    "Source":  "System.Management.Automation",
                                                                    "HResult":  -2146233087
                                                                },
                                             "TargetSite":  null,
                                             "StackTrace":  null,
                                             "HelpLink":  null,
                                             "Source":  null,
                                             "HResult":  -2146233079
                                         },
                           "TargetObject":  null,
                           "CategoryInfo":  {
                                                "Category":  7,
                                                "Activity":  "",
                                                "Reason":  "InvalidOperationException",
                                                "TargetName":  "",
                                                "TargetType":  ""
                                            },
                           "FullyQualifiedErrorId":  "ProviderOperationExecutionFailure",
                           "ErrorDetails":  null,
                           "InvocationInfo":  null,
                           "ScriptStackTrace":  null,
                           "PipelineIterationInfo":  [

                                                     ]
                       }
FinalState           :
InDesiredState       : False
InitialState         :
InstanceName         : Account-Policy
RebootRequested      : False
ResourceName         : AccountPolicy
StartDate            : 11/18/2017 9:35:45 PM
PSComputerName       :

Hi @ppandiya the minimum password length allowed by the OS is 14 characters.  This is documented here - https://technet.microsoft.com/en-us/library/hh994560(v=ws.11).aspx

Would be good if the documentation was updated with this information. Labeling this as help wanted so that someone in the community can run with this.

@johlju do you think it's feasible to document each and every setting?  There is a link on the readme that explains each setting.  If the setting is applied in the GUI it also explains it.  To me it makes more sense to add a validate set for that parameter

Validate set is good.  Looking at this, maybe the problem is that the link is in a section header that is equal "size" of the resource name. It feels that the resource only have one parameter Name.
Maybe it possible to change it to something like this? Other resource modules use this format.

SecurityOption
For explanation of below settings, please consult Security Policy Reference.

[String] Name (Key): Name of security option configuration. This is not used during the configuration process but needed
to ensure the resource configuration instance is unique.
[String] Accounts_Administrator_account_status (Write): Please see above link for description and possible values.
[String] Accounts_Block_Microsoft_accounts (Write): Please see above link for description and possible values.
[String] Accounts_Administrator_account_status (Write): Please see above link for description. { Enabled | Disabled }

Yeah I like that. It does look more professional.

@johlju
I'm seeing this same issue in the SecurityOption DSC, where options that need to be changed are erroring out with the same error.
Having RTFM, I see that the option of 'Enabled' is valid.  I have also confirmed that it's defined in SecurityOptionData.psd1 and MSFT_SecurityOption.schema.mof as a valid option.
DSC Configuration Fragment:
Configuration HardeningV2 {
    Import-DscResource -ModuleName @{ModuleName = 'SecurityPolicyDsc'; RequiredVersion = '<IP_ADDRESS>'}
    Node localhost {
        SecurityOption SecurityPolicy
        {
            Name = 'SecurityPolicy'
            Devices_Restrict_floppy_access_to_locally_logged_on_user_only = 'Enabled'
        }
    }
}

Verbose Output Fragment:
VERBOSE: [SERVER02]: LCM:  [ End    Set      ]  [[SecurityOption]SecurityPolicy]  in 36.8800 seconds.
PowerShell DSC resource MSFT_SecurityOption  failed to execute Set-TargetResource functionality with error message:
Failed to update security option Devices_Restrict_floppy_access_to_locally_logged_on_user_only. Refer to
%windir%\security\logs\scesrv.log for details.
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

$env:TEMP\SecEdit-Output.txt:

The data is invalid.

The task has completed with an error.
See log %windir%\security\logs\scesrv.log for detail info.

$env:TEMP\securityOptionsToAdd.inf:
[Unicode]
Unicode=yes
[Version]
signature="$CHICAGO$"
Revision=1

[Registry Values]
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateFloppies=1,"1"

$env:TEMP\SecurityPolicy.inf Fragment:
[Unicode]
Unicode=yes
[System Access]
[Event Audit]
[Version]
signature="$CHICAGO$"
Revision=1
[Registry Values]
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateFloppies=1,"0"
[Privilege Rights]

I think this is being addressed in #112
@aydeisen can you confirm your PR fixes this problem? Or are you seeing more problems despite the PR you submitted?

I made the edits in response to issue #112 however, I wasn't able to figure out how to validate some of the more free-form parameters.  I've contributed what I could to help with this issue, but I personally wouldn't consider #112 fully resolved until all parameters have validation attributes

Thanks, I will leave open to be reviewed.

I am also facing the same issue trying to update Security options policies using Security option resource.  if i change the  value in the parameter it fails. Example Accounts: Rename administrator account  .
WINDOWS 7

@manoj2994 are you saying you are trying to rename the administrator account to "WINDOWS 7"?

@manoj2994 are you saying you are trying to rename the administrator account to "WINDOWS 7"?

Yes


Add calculation of config at execution time

It seems like it fixes issue #3

PR #1! Thanks!

Oh, you can make the PR to my repo instead of your fork.

Sure, wrong manipulation


How do you made firebase auth loaded before router start checking?

I'm using different version with the ones in this repo. I'm using Vue.js 2 and Firebase 4.
I'm having same problem with this guy here
Because Firebase login doing async request, so when my router start checking, firebase.auth().currentUser return null, therefore the page will redirect to Auth Page, but then the async request completed and it redirect back to old page.
1. I visit chat page at #/chat
2. It redirect to #/login
3. Firebase async request completed, and it returns that I'm logged in.
4. Automatic redirect back to #/chat

Currently, my code:
import fbApp from './firebase'

fbApp.init()

var router = Router({
  routes: [
    {
      path: '/login',
      name: 'Login',
      component: Login
    },
    {
      path: '/chat',
      name: 'Chat',
      component: Chat,
      meta: {
        requiresAuth: true,
      }
    }
  ]
})

router.beforeEach((to, from, next) => {
  if (to.matched.some(record => record.meta.requiresAuth)) {
    if (!fbApp.app.auth().currentUser) {
      next({
        path: '/login',
        query: {
          redirect: to.fullPath,
        },
      });
    } else {
      next();
    }
  } else {
    next();
  }
});

new Vue({
  el: '#app',
  router,
  template: '<App/>',
  components: { App }
})

firebase/index.ts
const fbApp = {
    app: null,
    user: {
        logged: false,
        id: null,
        name: null,
        email: null,
        photoURL: null
    },

    init() {
        const config = {
        }
        this.app = firebase.initializeApp(config)

        this.app.auth().onAuthStateChanged(user => {
            if (user) {
                // This will redirect to #/chat page
                this._onLoggedIn(user)
            }
        })
    }
}

IMO, it's doing the same thing as you. But why yours works, but mine?
Could you please help me to explain?
Thanks in advance.

Hi, it would take me some time to debug it even if I had all of your code.
I would suggest putting a callback to the Auth api inside your beforeEach. When you get the result from the Auth api, you can invoke next.

Closing due to inactivity, and I'm not keeping this sample app up to date.


INTERFACE_LIBRARY targets may only have whitelisted properties.  The   property "IMPORTED_RELEASE_LOCATION" is not allowed

update cmake

I changed  cmake/external.cmake 13 line. so I fixed it
get_target_property(__LOCATION ${target} IMPORTED_RELEASE_LOCATION)

to
get_target_property(__LOCATION ${target} IMPORTED_LOCATION_RELEASE)

INFO /ros_ws/src/ct_icp/install/Ceres/lib/libceres.so.2.0.0
CMake Error at cmake/external.cmake:13 (get_target_property):
INTERFACE_LIBRARY targets may only have whitelisted properties.  The
property "IMPORTED_LOCATION_RELEASE" is not allowed.
Call Stack (most recent call first):
CMakeLists.txt:51 (include)
INFO /ros_ws/src/ct_icp/install/yaml-cpp/lib/libyaml-cpp.so.0.6.3
CMake Error at cmake/external.cmake:13 (get_target_property):
INTERFACE_LIBRARY targets may only have whitelisted properties.  The
property "IMPORTED_LOCATION_RELEASE" is not allowed.
Call Stack (most recent call first):
CMakeLists.txt:51 (include)

Updating cmake to version 3.20.5 solves this issue :)


Assorted bugfixes

First I was going to just rename --auto to --minimal but given that --auto lets you do --auto --storage-backend=zfs --storage-create-device=/dev/sda, it's really not minimal.

Ah thanks, yes i didn't spot that initially as it hadn't changed. Yep makes sense.

@stgraber looks like there's a problem parsing --auto as tests failing with:
"Error: Configuration flags require --auto"

Oops, that should do it.

Testsuite passed


Revert "chore(deps): bump helm/kind-action from 1.7.0 to 1.8.0"

Reverts kedacore/keda#4838
After this bump, the smoke tests on ARM64 are failing: https://github.com/kedacore/keda/actions/runs/5743980509/job/15570101840
Something looks wrong with kind version

/skip-e2e


Build fixes

Always compile generated java files
Include uglify-js in package.json deps as its required for js maker

Handled by a newer commit.


Old DLSS version in current build

Could we get an update to get DLSS 3.5 instead of DLSS 3.0.
From my limited knowledge it should be an easy update.

Thank you for the suggestion! Great minds think alike - this feature was upgraded with our latest releases (0.5/2024.3.0). You can find more info here: https://www.nvidia.com/en-us/geforce/news/rtx-remix-dlss-3-5-ray-reconstruction/


feat: add best practices policies in CEL expressions

Related Issue(s)
#891

Description
This PR includes the conversion of Kubernetes best practices policies to Kyverno CEL policies. Conversions of other validate policies will be addressed in separate pull requests.
Policies converted in this PR:

[ ] check-deprecated-apis
[x] disallow-cri-sock-mount
[x] disallow-default-namespace
[x] disallow-empty-ingress-host
[x] disallow-helm-tiller
[x] disallow-latest-tag
[x] require-drop-all
[x] require-drop-cap-net-raw
[x] require-labels
[x] require-pod-requests-limits
[x] require-probes
[x] require-ro-rootfs
[x] restrict-image-registries
[x] restrict-node-port
[x] restrict-service-external-ips

Checklist

[x] I have read the policy contribution guidelines.
[ ] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
[ ] I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

It would be better to add a new line at the end of each file.

I've added them, the warnings are not present now

Whenever this PR is ready for final review, please resolve all comments and remove it from draft mode.

Sure. I'm waiting to make adjustments in the PR based on feedback from @MariamFahmy98 in the comments

There are some flake tests:

require-drop-all:

l.go:53: | 11:28:28 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Operation cannot be fulfilled on clusterpolicies.kyverno.io "drop-all-capabilities": the object has been modified; please apply your changes to the latest version and try again
    l.go:53: | 11:28:28 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Patch "https://<IP_ADDRESS>:39511/apis/kyverno.io/v1/clusterpolicies/drop-all-capabilities": context deadline exceeded
    l.go:53: | 11:28:28 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Patch "https://<IP_ADDRESS>:39511/apis/kyverno.io/v1/clusterpolicies/drop-all-capabilities": context deadline exceeded

restrict-image-registries:l.go:53: | 11:24:11 | restrict-image-registries | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ restrict-image-registries
   === ERROR
   Operation cannot be fulfilled on clusterpolicies.kyverno.io "restrict-image-registries": the object has been modified; please apply your changes to the latest version and try again
l.go:53: | 11:24:14 | restrict-image-registries | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ restrict-image-registries
   === ERROR
   Operation cannot be fulfilled on clusterpolicies.kyverno.io "restrict-image-registries": the object has been modified; please apply your changes to the latest version and try again
l.go:53: | 11:24:15 | restrict-image-registries | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ restrict-image-registries
   === ERROR
   Patch "https://<IP_ADDRESS>:39511/apis/kyverno.io/v1/clusterpolicies/restrict-image-registries": context deadline exceeded
l.go:53: | 11:24:15 | restrict-image-registries | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ restrict-image-registries
   === ERROR
   Patch "https://<IP_ADDRESS>:39511/apis/kyverno.io/v1/clusterpolicies/restrict-image-registries": context deadline exceeded

3. require-run-as-non-root-user: same error
4. disallow-host-namespaces: same error

It seems that the issue arises when we patch the policy. Could you please have a look?

CEL policies cause a lot of noise in the CI. If we check the past CI runs, we see that there's always a chainsaw test for a CEL policy failing due to the error you have mentioned. It is happening on versions 1.25 and 1.26 specifically. CEL flaky tests don't seem to occur on version 1.27 and above for some reason, I haven't observed any such failures recently.
I tried the following steps to reproduce it:

Create a version 1.26 kind cluster

~/my-space/policies$ kind create cluster --image kindest/node:v1.26.14 --config ./.github/kind.yml

Install latest kyverno

~/my-space/policies$ kubectl create -f https://github.com/kyverno/kyverno/raw/main/config/install-latest-testing.yaml

Run chainsaw test for require-drop-all policy

~/my-space/policies/best-practices-cel/require-drop-all$ chainsaw test
Version: (devel)
Loading default configuration...
- Using test file: chainsaw-test
- TestDirs [.]
- SkipDelete false
- FailFast false
- ReportFormat ''
- ReportName 'chainsaw-report'
- Namespace ''
- FullName false
- IncludeTestRegex ''
- ExcludeTestRegex ''
- ApplyTimeout 5s
- AssertTimeout 30s
- CleanupTimeout 30s
- DeleteTimeout 15s
- ErrorTimeout 30s
- ExecTimeout 5s
- NoCluster false
Loading tests...
- require-drop-all (.chainsaw-test)
Loading values...
Running tests...
=== RUN   chainsaw
=== PAUSE chainsaw
=== CONT  chainsaw
=== RUN   chainsaw/require-drop-all
=== PAUSE chainsaw/require-drop-all
=== CONT  chainsaw/require-drop-all
    | 06:45:49 | require-drop-all | @setup   | CREATE    | OK    | v1/Namespace @ chainsaw-unified-longhorn
    | 06:45:49 | require-drop-all | step-01  | TRY       | RUN   |
    | 06:45:49 | require-drop-all | step-01  | APPLY     | RUN   | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:50 | require-drop-all | step-01  | CREATE    | OK    | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:50 | require-drop-all | step-01  | APPLY     | DONE  | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:50 | require-drop-all | step-01  | PATCH     | RUN   | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:52 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Operation cannot be fulfilled on clusterpolicies.kyverno.io "drop-all-capabilities": the object has been modified; please apply your changes to the latest version and try again
    | 06:45:54 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Operation cannot be fulfilled on clusterpolicies.kyverno.io "drop-all-capabilities": the object has been modified; please apply your changes to the latest version and try again
    | 06:45:55 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Patch "https://<IP_ADDRESS>:43343/apis/kyverno.io/v1/clusterpolicies/drop-all-capabilities": context deadline exceeded
    | 06:45:55 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Patch "https://<IP_ADDRESS>:43343/apis/kyverno.io/v1/clusterpolicies/drop-all-capabilities": context deadline exceeded
    | 06:45:55 | require-drop-all | step-01  | TRY       | DONE  |
    | 06:45:55 | require-drop-all | @cleanup | DELETE    | RUN   | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:55 | require-drop-all | @cleanup | DELETE    | OK    | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:55 | require-drop-all | @cleanup | DELETE    | DONE  | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
    | 06:45:55 | require-drop-all | @cleanup | DELETE    | RUN   | v1/Namespace @ chainsaw-unified-longhorn
    | 06:45:55 | require-drop-all | @cleanup | DELETE    | OK    | v1/Namespace @ chainsaw-unified-longhorn
    | 06:46:00 | require-drop-all | @cleanup | DELETE    | DONE  | v1/Namespace @ chainsaw-unified-longhorn
--- FAIL: chainsaw (0.00s)
    --- FAIL: chainsaw/require-drop-all (11.16s)
FAIL
Tests Summary...
- Passed  tests 0
- Failed  tests 1
- Skipped tests 0
Done with failures.
Error: some tests failed

Logs from the admission controller:
2024-04-29T06:45:50Z    INFO    setup.cluster-policy    logging/controller.go:45        resource added  {"type": "ClusterPolicy", "name": "drop-all-capabilities"}
2024-04-29T06:45:51Z    LEVEL(-2)       klog    rest/request.go:697     Waited for 1.048965431s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/kyverno.io/v1beta1
2024-04-29T06:45:53Z    LEVEL(-2)       klog    rest/request.go:697     Waited for 1.04967128s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1
2024-04-29T06:45:55Z    INFO    setup.cluster-policy    logging/controller.go:68        resource deleted        {"type": "ClusterPolicy", "name": "drop-all-capabilities"}
2024-04-29T06:45:55Z    LEVEL(-2)       klog    rest/request.go:697     Waited for 1.008841763s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/node.k8s.io/v1
2024-04-29T06:45:56Z    ERROR   webhooks.policy.validate        handlers/error.go:12    an error has occurred   {"gvk": "kyverno.io/v1, Kind=ClusterPolicy", "gvr": {"group":"kyverno.io","version":"v1","resource":"clusterpolicies"}, "namespace": "", "name": "drop-all-capabilities", "operation": "UPDATE", "uid": "1eb28bc8-51c1-476d-ac2c-3e12be7d3ee0", "user": {"username":"kubernetes-admin","groups":["system:masters","system:authenticated"]}, "url": "/policyvalidate?timeout=10s", "error": "write tcp <IP_ADDRESS>:9443-><IP_ADDRESS>:54374: write: broken pipe"}
2024-04-29T06:45:56Z    INFO    webhooks.server logging/log.go:182      2024/04/29 06:45:56 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:88)

It seems like the problem is client-side throttling.
The troubleshooting guide suggests increasing clientRateLimitBurst and clientRateLimitQPS. I set both flags to 120 and kept running the same test. The test passed 14 out of 20 times. Without the flags set, the test passed 4 out of 20 times.
I ran the same test on a kind 1.29.2 cluster without the flags set, and it didn't fail even once after 20 times.
However, I still got this error:
=== ERROR
        Operation cannot be fulfilled on clusterpolicies.kyverno.io "drop-all-capabilities": the object has been modified; please apply your changes to the latest version and try again
    | 08:09:14 | require-drop-all | step-01  | PATCH     | ERROR | kyverno.io/v1/ClusterPolicy @ drop-all-capabilities
        === ERROR
        Operation cannot be fulfilled on clusterpolicies.kyverno.io "drop-all-capabilities": the object has been modified; please apply your changes to the latest version and try again

But there was no error saying: context deadline exceeded
I'm not sure why this problem consistently occurs specifically on versions 1.25 and 1.26.
Anything we can do about it?

@Chandan-DK - Could you please check the failed tests?

@Chandan-DK - Could you please check the failed tests?

Sure, I will send a fix. The tests fail due to chainsaw templating. @eddycharly recently bumped the chainsaw version and it causes this issue.
The solution is to set spec.template to false in the chainsaw test file (https://github.com/kyverno/policies/pull/1029/files#diff-d4f62d0006ca20570a1672eb23621e9dd77120edb09b685c50f0cda968f34753R9)

@Chandan-DK - Could you please check the failed tests?

Sure, I will send a fix. The tests fail due to chainsaw templating. @eddycharly recently bumped the chainsaw version and it causes this issue. The solution is to set spec.template to false in the chainsaw test file (https://github.com/kyverno/policies/pull/1029/files#diff-d4f62d0006ca20570a1672eb23621e9dd77120edb09b685c50f0cda968f34753R9)

Thank you!


reference an example into Kraken-js site

@samsel I'll start working on this.

:+1:

Ref: Detailed setup instructions like this.
https://github.com/krakenjs/kraken-example-with-specialization
We can add a reference to this link from kraken wiki.

@samsel sounds good - will keep you updated.

Definitely keen to see this - i'd love to use this in a new project, just can't seem to work out how to configure the krakenjs side.

I was just going to create an issue for this :D glad to see someone is ahead of the game. I'm trying to grasp kraken and not entirely familiar with how to start integrating react-engine with kraken-js. It would be great if something could be put together and put within the /examples directory :)

:+1:

also eager to see this example


feat: Added PodmanRunner to the codebase

@ivotron can you please review this?

@ivotron I've commented out the test


Add nnunet model (ensemble and fold_all)

As per the nnunet retraining master issue (axondeepseg #771), I will upload the nnunet model. We will include the 5 folds from the cross-validation as well as the fold_all light model.

Done in https://github.com/axondeepseg/default-BF-model/releases/tag/r20240405


用netcoreapp2.1 搭建页面遇到 InvalidOperationException 问题-Encounter InvalidOperationException problems with netcoreapp2.1 building pages

新手在学 ASP.NET Core用 netcoreapp2.1 搭建不含model 的页面 在布局时 用 <partial name="" /> 遇到个问题 用这个时一直报“An unhandled exception occurred while processing the request.
InvalidOperationException: The model item passed into the ViewDataDictionary is of type 'CmsAspCore.Pages.IndexModel', but this ViewDataDictionary instance requires a model item of type 'CmsAspCore.Pages.NavigationModel'.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewDataDictionary.EnsureCompatible(object value)”不知道是哪里的问 求教 谢谢 Image:77713-6.pngindex页面 Image:77714-2.png_Layout页面 Image:77715-3.png嵌套页面 Naviga Image:77716-5.png
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/600820/用netcoreapp21-搭建页面遇到-invalidoperationexception-问题.html
VSTS ticketId: 915807
These are the original issue comments:
Visual Studio Feedback System on 6/10/2019, 11:12 PM (28 days ago): We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Visual Studio Feedback System on 6/11/2019, 01:48 AM (28 days ago): Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at:  https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2017#faq . In case you need answers to common questions or need assisted support, be sure to use  https://visualstudio.microsoft.com/vs/support/ . We'll keep you posted on any updates to this feedback.
Jane Wu [MSFT] on 6/11/2019, 07:26 PM (28 days ago): Translated from Bing:Beginner is learning ASP.NET CoreUse netcoreapp2.1 to build pages that do not contain model in the <partial name=""""></partial> layout with a problem encountered when using this has been reported "An unhandled exception occurred while processing the request.  Invalidoperationexception:the model item passed into the ViewDataDictionary are of type ' CmsAspCore.Pages.IndexModel ', but This ViewDataDictionary instance requires a model item of type ' CmsAspCore.Pages.NavigationModel '.Microsoft.AspNetCore.Mvc.ViewFeatures.ViewDataDictionary.EnsureCompatible (object value) " I don't know where to ask for advice.Index page_Layout pageNested pages Naviga
These are the original issue solutions:
(no solutions)

Hi. It looks like this is a question about how to use ASP.NET Core. While we do our best to look through all the issues filed here, to get a faster response we suggest posting your questions to StackOverflow using the asp.net-core-mvc tag.

The error you're receiving actually tells exactly what the problem is. It indicates and error in your page, and you should make sure you pass a proper type parameter as an input. For questions like this, StackOverflow is a great place to start with, as you'll get your questions answered quickly.

我也遇到同样的问题，不知道解决没有？


refactor the view_my_scores method in grades_controller.rb

Sub-Issue of #2 for easier division of work, please see that issue for description.
This issue is focused on the view_my_scores method in the grades_cointroller.

Simply the view method now.


Add WW3 recipe

[ ] Closes #56

Recipe is running:

Ill report back after this finishes.

pre-commit.ci autofix

Got some strange errors during the first two runs:
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/gcsfs/retry.py", line 104, in validate_response
    raise HttpError({"code": status, "message": msg})  # text-like
gcsfs.retry.HttpError: Request range not satisfiable, 416

@leap-stc/data-management-devs look familiar to anyone?
If seems to fail in the rechunk stage

hmmm repeat runs also fail, but all with slightly different errors.
Wondering if we are running out of memory?

dataflow job

Perhaps we should use dataflow prime for the ingestion as well?

Added dataflow prime to the config for this job. But its late and ill check on this tomorrow.

That did not seemed to have helped. Any clues that I might have missed @cisaacstern ?

Still fails...I have extended the year range to exclude that there is something wrong with these two particular files we downloaded previously.

Debugging this with @cisaacstern and he noticed that the files are heavily compressed (3Gb vs 17GB!), which might overwhelm our our workers memory.
Trying to deactivate prime and use a big machine for testing now.

pre-commit.ci autofix

So I have done some more investigation on this case. See this gist.
Just deployed another version that incorporates lessons learned here: https://github.com/leap-stc/data-management/pull/57/commits/5672faa754c697142e357f1b9ae1f7c4fd97eb50
Lets see how that fares...

@cisaacstern it seems like we are running into some issues with the new schema validation for this recipe.
If you have a minute could you look into this? Does the current way we set up this repo not conform to the schema? Or is there some other problem?

I am very sorry for the long delay here. I have started working on this again as an example for our new (to be announced) structure of data management here: https://github.com/leap-stc/ww3_feedstock.

Superseeded by https://github.com/leap-stc/wavewatch3_feedstock


Local file backend example with rancher api

Hello, could You help me with an example how to use it? It fails with the following error every time.
docker run --rm -ti --name rancher-backup --label io.rancher.container.create_agent=true --label io.rancher.container.agent.role=environment -e BACKUP_DUPLICITY_url=file:// -e DEBUG=true webcenter/rancher-backup

Tried it with local file backend (file://, with and without rancher api by label and also manually).
Output:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-backup-dir: applying...
[fix-attrs.d] 01-backup-dir: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-welcome.sh: executing...

                                                           .                           `.
                                                          -d+                          +d.
                 `......................................  yms........----------.       hms
                :hdddddddddddddddddddddddddddddddddddddd:`dmmdddddddddmmmmmmmmddo     `hmm`
              `ommmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm-:mmmmmmmmmmmmmmmmmmmmmmm-.::+hmmm-
             .ymmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmd /mmmmmmmmmmmmmmmmmmmmmmm-+mmmmmmm/
            :hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmh``/ooooooshmmmmmmmmmmmmmm-:oooooo/
           /dmmmdmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmhssssssssydmmmmmmmmmmmmmm-
          ommdy//mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm-
          -so-  :mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmdsmmmmmmmmmmmmmm-
                :mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm+:mmmmmmmmmmmmmm-
                :mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm/:mmmmmmmmmmmmmm-
                :mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm/:mmmmmmmmmmmmmm-
                :mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm+`sdmmmmmmmmmmdo
                :mmmmmmmmmmmmmd+--------------------------:smmmmmm+..----------`
                :mmmmmmmmmmmmmo                            `mmmmmmmmmmmmmd
                :mmmmmmmmmmmmmo                            `mmmmmmmmmmmmmd
                :mmmmmmmmmmmmmo                            `mmmmmmmmmmmmmd
                :mmmmmmmmmmmmmo                            `mmmmmmmmmmmmmd
                .hmmmmmmmmmmmd/                             ymmmmmmmmmmmms
                 `````````````                               ````````````

                Name: rancher-backup
                Site: https://github.com/disaster37/rancher-backup
                Image Author: Sebastien LANGOUREAUX<EMAIL_ADDRESS>                Image support: https://github.com/disaster37/rancher-backup/issues
                Rancher: http://rancher.com
                Try Rancher: https://try.rancher.com/

      For french people, you can visit my blog http://blog.webcenter.fr about Docker and Rancher

      .ooooooo+:`     /ooo-    /ooo:    +oo   -/osyso+- `+oo:    +oo: +ooooooooo`ooooooo+:`
      -mmmhyydmmh-   -mmmmh`   smmmm:   dmm``sdmdyosdmdo`dmmo    hmmo dmmmyyyyyy.mmmhyydmmh-
      -mmm/  -mmmo  `ymdhmmo   smmmmd/  dmm`ymmm-   /mdm.dmmo    hmmo dmmh      -mmm/  -mmmo
      -mmms//ymmh-  +mmo:mmm-  smmsmmm/ dmd`mmmy    `--.`dmmhssssmmmo dmmdoooo+ -mmms//smmh-
      -mmmddmmm/`  .mmd.`ymmh` smm-/mmm:hmd`mmms        `dmmdyyyymmmo dmmdhhhhy -mmmddmmm+`
      -mmm+.smmh` `ymmdhhhmmmo smm- /dmdmmm`hmmd`   `sss-dmmo    hmmo dmmh      -mmm+.smmh.
      -mmm/ `ymmh/smmy////ommm-smm-  :dmmmm`-hmmy/::smmh`dmmo    hmmo dmmd/////+.mmm/ `ymmh+-
      .hhh/  `ohhhhhh.     yhhsshd-   :hhhh` .+yhdddhy+``hhh+    yhh+ yhhhhhhhhd.hhh/  `ohhd:
       ```      ````        ``` ``      ```     `..``     ``      ``   ````````` ```
       Community ^_^

[cont-init.d] 00-welcome.sh: exited 0.
[cont-init.d] 01-gen-confd-config.sh: executing...
[cont-init.d] 01-gen-confd-config.sh: exited 0.
[cont-init.d] 02-init-confd.sh: executing...
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Backend set to env
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Starting confd
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Backend nodes set to
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Target config /etc/services.d/cron/run out of sync
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Target config /etc/services.d/cron/run has been updated
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO /opt/backup/config/rancher-backup.yml has UID 1000 should be 1001
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO /opt/backup/config/rancher-backup.yml has GID 101 should be 1001
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO /opt/backup/config/rancher-backup.yml has mode -rw-rw---- should be -rw-r--r--
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO /opt/backup/config/rancher-backup.yml has md5sum 32fe12c98e31ab98e7c88502b8a9d60a should be 1459472ffbdc484bbfdc14aba9945f39
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Target config /opt/backup/config/rancher-backup.yml out of sync
2017-05-12T18:36:23Z 7667028be8f6 /opt/confd/bin/confd[341]: INFO Target config /opt/backup/config/rancher-backup.yml has been updated
[cont-init.d] 02-init-confd.sh: exited 0.
[cont-init.d] 04-run-backup.sh: executing...
2017-05-12 18:36:24,027 - DEBUG - Index settings : mariadb:
  regex: "mariadb"
  template: "mariadb.yml"
elasticsearch:
  regex: "elasticsearch"
  template: "elasticsearch.yml"
mongodb:
  regex: "mongo"
  template: "mongodb.yml"
mysql:
  regex: "mysql"
  template: "mysql.yml"
postgresql:
  regex: "postgres"
  template: "postgresql.yml"

2017-05-12 18:36:24,032 - DEBUG - return: {'rancher': {'api': {'url': None, 'secret': None, 'key': None}, 'db': {'user': 'rancher', 'host': None, 'port': 3306, 'name': 'rancher'}}, 'cron': {'schedule': '0 0 0 * * *'}, 'module': {'rancher-db': True, 'stack': True, 'databases': True}, 'duplicity': {'target-path': '/', 'url': 'file://', 'full-if-older-than': '7D', 'remove-all-but-n-full': 3, 'remove-all-inc-of-but-n-full': 1, 'volsize': 200, 'options': None, 'source-path': '/backup'}}
2017-05-12 18:36:24,032 - ERROR - Somthing wrong on your config file:
[cont-init.d] 04-run-backup.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Each time with different options I get the same error
2017-05-12 18:36:24,032 - ERROR - Somthing wrong on your config file:

Also rancher api seems not to be detected by label?

docker run --rm -ti --name rancher-backup --label io.rancher.container.create_agent=true --label io.rancher.container.agent.role=environment -e BACKUP_DUPLICITY_url=file:// -e BACKUP_DUPLICITY_target-path=/mnt -e BACKUP_RANCHER_db_host=<IP_ADDRESS> -e DEBUG=true webcenter/rancher-backup

On develop branch, now it display more usefull information when somethink wrong.
I don't realy know how rancher and when rancher grab the label. Maybee you need to lauch container by rancher UI or rancher-compose to use io.rancher label.

Test with latest version from rancher catalog webcenter/rancher-backup:2.0.0-2 looks better, but no local file in the host directory.
Output hangs with the following lines:
2017-07-14 11:31:59,562 - INFO - Save the Rancher setting for stack ipsec in /backup/rancher/ipsec
2017-07-14 11:31:59,563 - DEBUG - Create directory '/backup/rancher/ipsec'
2017-07-14 11:31:59,563 - INFO - Save the Rancher setting for stack healthcheck in /backup/rancher/healthcheck
2017-07-14 11:31:59,563 - DEBUG - Create directory '/backup/rancher/healthcheck'
2017-07-14 11:31:59,564 - INFO - Save the Rancher setting for stack scheduler in /backup/rancher/scheduler
2017-07-14 11:31:59,564 - DEBUG - Create directory '/backup/rancher/scheduler'
2017-07-14 11:31:59,564 - INFO - Save the Rancher setting for stack network-services in /backup/rancher/network-services
2017-07-14 11:31:59,565 - DEBUG - Create directory '/backup/rancher/network-services'
2017-07-14 11:31:59,565 - INFO - Save the Rancher setting for stack pxc in /backup/rancher/pxc
2017-07-14 11:31:59,565 - DEBUG - Create directory '/backup/rancher/pxc'
2017-07-14 11:31:59,566 - INFO - Save the Rancher setting for stack rancher-backup in /backup/rancher/rancher-backup
2017-07-14 11:31:59,566 - DEBUG - Create directory '/backup/rancher/rancher-backup'
2017-07-14 11:31:59,566 - INFO - The exporting of stack if finished
2017-07-14 11:31:59,566 - INFO - Start to dump Rancher database...
2017-07-14 11:31:59,566 - INFO - Dumping the Rancher database 'cattle' in '/backup/rancher/database'
2017-07-14 11:31:59,567 - DEBUG - Create directory '/backup/rancher/database'
2017-07-14 11:31:59,567 - DEBUG - Command to exec : docker pull mysql:latest
2017-07-14 11:32:01,325 - DEBUG - Results : latest: Pulling from library/mysql
Digest: sha256:d178dffba8d81afedc251498e227607934636e06228ac63d58b72f9e9ec271a6
Status: Image is up to date for mysql:latest

2017-07-14 11:32:01,325 - DEBUG - Command to exec : docker run --rm -v /backup/rancher/database:/backup/rancher/database -e 'MYSQL_PWD=cattle' mysql:latest sh -c 'mysqldump -h <IP_ADDRESS> -P 13306 -u cattle cattle > /backup/rancher/database/cattle.dump'

A mysqlbackup file is written inside of the container with a file size of ~153kb (fresh rancher server install). But shouldn't the mysqlbackup process(es) stopp after backup finished?

Read rancehr credentials fails, but config params (rancher db params) working fine.
2017-07-14 11:17:25,123 - INFO - Can't grab Rancher database settings from API, try to grab it from config file
2017-07-14 11:17:25,123 - INFO - Start to initialize Duplicity...

That should be backup destination path at the host.
2017-07-14 11:31:57,537 - INFO - Backup target path: /var/tmp/rancher
2017-07-14 11:31:57,537 - INFO - Backend to receive remote backup: file://

But backups of stacks and rancher database seems to work inside of the container:
/opt/backup # ls -lh /backup/rancher/
total 0
drwxr-xr-x    2 backup   docker         6 Jul 14 11:31 database
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 healthcheck
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 ipsec
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 network-services
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 pxc
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 rancher-backup
drwxr-xr-x    2 backup   docker        59 Jul 14 11:31 scheduler

/opt/backup # ls -lh /data/rancher/database/
total 152
-rw-r--r--    1 root     root      151.3K Jul 14 11:32 cattle.dump

So maybe I just havae to upgrade the stack and add volumes with the host directory

Hum, I have fix a kind of bug in rancher-compose (the volume name between docker container and duplicity container is not the same (typo error).
I will update it on my rancher catalog.
And the error about read Rancher credential is a kind of limitation on how we get access to API. To read the credential, you need to generate Admin Api key and use it. The environment Api key haven't the right to read credential.

No news, so I consider is closed. You can reopen it if needed.


Unifi: (Docker / Unpoller / Prometheus / Grafana)

Hi,
Im trying to set this up using Prometheus and im running into an issue:
When loading unpoller container im getting the following syntax error in the logs which puts the container in a constant reboot loop
[ERROR] env unmarshal: UP_POLLER_DEBUG: strconv.ParseBool: parsing "\"false\"": invalid syntax
[INFO] Loading Configuration File: /etc/unifi-poller/up.conf
[ERROR] env unmarshal: UP_POLLER_DEBUG: strconv.ParseBool: parsing "\"false\"": invalid syntax
[INFO] Loading Configuration File: /etc/unifi-poller/up.conf
[ERROR] env unmarshal: UP_POLLER_DEBUG: strconv.ParseBool: parsing "\"false\"": invalid syntax
[INFO] Loading Configuration File: /etc/unifi-poller/up.conf
[ERROR] env unmarshal: UP_POLLER_DEBUG: strconv.ParseBool: parsing "\"false\"": invalid syntax
[INFO] Loading Configuration File: /etc/unifi-poller/up.conf

Im used the https://raw.githubusercontent.com/unpoller/unpoller/master/examples/up.conf.example file as a base and have tweaked it accordingly for my setup.
I've validated the syntax against a TOML validator and it passes.

Seems like you're passing in an env variable with quotes in it. Docker compose is bad about that. :(


S3 upload options

I want to set cache-control headers for my S3 file uploads. There is an on_uploader hook that seems like it would be useful for this, only the arguments modified by the hook aren't passed through to the add_file method (unless I'm mistaken).
Basically, I want to get a cache_control: 'public, max-age=1234567890' argument into this line:
camaleon-cms/app/uploaders/camaleon_cms_aws_uploader.rb:56

Added!
Sample: http://camaleon.tuzitio.com/documentation/category/40756-uncategorized/custom-aws-params.html
Test using git version.

Thank you! It works perfectly, but there is an error in the documentation in the link above.
args[:aws_file_upload_settings] should be args[:aws_settings][:aws_file_upload_settings]
and
args[:aws_file_read_settings] should be args[:aws_settings][:aws_file_read_settings]

you are right, updated!

I spoke too soon. Uploading works fine, but when I tried to delete the file I got a NoMethodError on s3_file.cache_control I haven't figured out how to fix it yet.

I updated
http://camaleon.tuzitio.com/documentation/category/40756-uncategorized/custom-aws-params.html
The problem was because the CMS is using the summary object for optimizations and to get the real object you need to use like this:
data[:cache_control] = (s3_file.is_a?(Aws::S3::ObjectSummary) ? s3_file.object : s3_file).cache_control

That did it, thanks!


feat(stylekit): make inputs fullwidth only with a class

This applies to input, date, number, and selector elements.
Input margins have been normalized as well.
Documentation
Input
Modifying classes
Stylekit brings some modifying classes to extend the default behavior of the input control.

CSS class
Description

.fullwidth
Fill the entire width of the container. This class is also available for number, date, and selector controls.

Default Layout
By design, inputs are laid out inline so you can do things like this in markdown:
Enter your name: <|input|>

And get this as a result.

But if you want the input to display as a block-level element and fill the width of its container, you can give it the fullwidth class name (described above).

This can be useful for more complex multifield forms and layouts.
The exact same goes for number, date, and selector controls.
Date
Modifying classes
Stylekit brings some modifying classes to extend the default behavior of the date control.

CSS class
Description

.fullwidth
Fill the entire width of the container. This class is also available for input, number, and selector controls.

Default Layout
date controls are displayed as inline elements by default, just like input controls. Please refer to input documentation for more details.
Number
Modifying classes
Stylekit brings some modifying classes to extend the default behavior of the number control.

CSS class
Description

.fullwidth
Fill the entire width of the container. This class is also available for date, number, and selector controls.

Default Layout
number controls are displayed as inline elements by default, just like input controls. Please refer to input documentation for more details.
Selector
Modifying classes
Stylekit brings some modifying classes to extend the default behavior of the selector control.

CSS class
Description

.fullwidth
Fill the entire width of the container. This class is also available for input, number, and date controls.

Default Layout
selector dropdown controls are displayed as inline elements by default, just like input controls. Please refer to input documentation for more details.

Ready to merge @FabienLelaquais  👍


⚠ ClamAV has degraded performance

In 1fbd13e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 295 ms

Resolved: ClamAV performance has improved in f78279e.


Global class in lua, for debug, etc

Should use the regular C debug for proper logging to file when needed.

Added debugging to the C logger

Not needed a master file yet, but is an easy add later.


52 settings view

Everything except for the switch related to notifications should be done. Going to device permissions settings has not been tested properly. The switch doesn't change color as we wanted but that can be fixed later.
The name of the settings file was changed due to conflicting import file that is needed for going to device settings.

Everything looks good! Going to device permissions works properly and with little additions the saved choices in the settings are now displayed correctly (excluding notifications like agreed).


go.nvim code conflicts with latest nvim-treesitter code

Please have a  look https://github.com/nvim-treesitter/nvim-treesitter/issues/5910#issuecomment-1895464469 .

Hey guys I upgraded to the new Treesitter  re-write branch main and the same issue but had a different error.
The new branch has changed the setup call from using require("nvim-treesitter.configs").setup to now simply require("nvim-treesitter").setup.
This was a quick fix as I only have to change the require in ~/.local/share/nvim/lazy/go.nvim/lua/go/ts/utils.lua:12 line 12, but I'm not sure how you would handle this for both branches until main is released as 1.0.
Error message:
Error executing vim.schedule lua callback: ....local/share/nvim/lazy/go.nvim/lua/go/ts/textobjects.lua:12: module 'nvim-treesitter.configs' not found:
        no field package.preload['nvim-treesitter.configs']
cache_loader: module nvim-treesitter.configs not found
cache_loader_lib: module nvim-treesitter.configs not found
        no file './nvim-treesitter/configs.lua'
        no file '/opt/homebrew/share/luajit-2.1/nvim-treesitter/configs.lua'
        no file '/usr/local/share/lua/5.1/nvim-treesitter/configs.lua'
        no file '/usr/local/share/lua/5.1/nvim-treesitter/configs/init.lua'
        no file '/opt/homebrew/share/lua/5.1/nvim-treesitter/configs.lua'
        no file '/opt/homebrew/share/lua/5.1/nvim-treesitter/configs/init.lua'
        no file './nvim-treesitter/configs.so'
        no file '/usr/local/lib/lua/5.1/nvim-treesitter/configs.so'
        no file '/opt/homebrew/lib/lua/5.1/nvim-treesitter/configs.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file './nvim-treesitter.so'
        no file '/usr/local/lib/lua/5.1/nvim-treesitter.so'
        no file '/opt/homebrew/lib/lua/5.1/nvim-treesitter.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        ....local/share/nvim/lazy/go.nvim/lua/go/ts/textobjects.lua:12: in function 'setup'
        .../michael.dakin/.local/share/nvim/lazy/go.nvim/lua/go.lua:224: in function ''
        vim/_editor.lua: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

Master vs Main README

I had the same issue, it occurred suddenly without any changes to configuration or updating packages at all.
Treesitter just freezed after first interaction with it.
I tried to update everything, but that didn't helped.
Then when i uninstalled ray-x/go.nvim plugin, and installed it back fresh, everything started working again.
I am using folke/lazy.nvim


Holding CTRL + S will delete everything in file

If you hold  Ctrl + S  it will delete everything in the file and save it.

Closing this out since more details were never provided, please comment if you are still experiencing it in Atom 1.0+


THREE.WebGPURenderer: WebGPU is not available, running under WebGL2 backend.

Hello
I'm running Three js demo on ios and I'm getting this error. I need help fixing this. I haven't seen this error in older version of the library.
There are also errors like:
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736
WebGPU: Unknown feature name 12
WebGPU: Unknown feature name 327736

Is it because I use some unsupported Three js feature or it is something inside of react-native-webgpu library?
I'm running demo on iPhone 12.

Could you share a reproduction? that would be useful.

@wcandillon It is reproduced on some devices and not reproduced on others.
I tried to investigate what is happening.
There is an error somewhere in Three js init code:
https://github.com/mrdoob/three.js/blob/3e54130c1d40595c544ff33308de8c6a9311b130/src/renderers/webgpu/WebGPUBackend.js#L20
But I couldn't find a reason of this. If I tested requestAdapter call, requestDevice call and context.configure it works for me fine.
But then I couldn't render with this context using Three js.

@wcandillon I think I found the solution. Either I have the incompatible Three JS version or something else. The solution to fix the error is below:
  const ref = useCanvasEffect(async () => {
    // We have to requestAdapter
    const adapter = await navigator.gpu.requestAdapter();
    if (!adapter) {
      throw new Error("No adapter");
    }
    // We have to request the Device
    const device = await adapter.requestDevice();
    const context = ref.current!.getContext("webgpu")!;
    if (!context) {
      console.error("No context");
      return;
    }

    const canvas = context.canvas as HTMLCanvasElement;
    canvas.width = canvas.clientWidth * PixelRatio.get();
    canvas.height = canvas.clientHeight * PixelRatio.get();

    // We don't use makeWebGPURenderer but instead we pass device to WebGPURenderer
    renderer = new THREE.WebGPURenderer({
      antialias : true,
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-expect-error
      // import ReactNativeCanvas from makeWebGPURenderer.js
      canvas: new ReactNativeCanvas(context.canvas),
      context,
      // Pass the device
      device,
    });
    await renderer.init();

   ... rest of the code
});

I tested both iOS and Android and this fix works on both platform. So I'm closing the issue.


Can't reproduce the accuracy with pre-trained Large Scale Word Language Model (gbw dataset)

Description
Can't reproduce the same accuracy with pre-trained Large Scale Word Language Model based on gbw dataset, following the guideline.
The accuracy given in tutorial is:
[1] LSTM-2048-512 (Test PPL 43.62)
What I got is:
Best validation loss 9.40, val ppl 12130.84
Best test loss 9.42, test ppl 12303.21
@eric-haibin-lin
Error Message
BigRNN(
  (embedding): HybridSequential(
    (0): Embedding(793471 -> 512, float32)
    (1): Dropout(p = 0.1, axes=())
  )
  (encoder): HybridSequentialRNNCell(
  (0): LSTMPCell(512 -> 8192 -> 512)
  (1): DropoutCell(rate=0.1, axes=())
  )
  (decoder): Dense(512 -> 793471, linear)
)
Vocab(size=793471, unk="<unk>", reserved="['<pad>', '<eos>']")
Best validation loss 9.40, val ppl 12130.84
Best test loss 9.42, test ppl 12303.21

To Reproduce
Run the script awd_lstm.py with MXNet master branch.
Steps to reproduce
python awd_lstm.py
What have you tried to solve it?
None
Environment
We recommend using our script for collecting the diagnositc information. Run the following command and paste the outputs below:
curl --retry 10 -s https://raw.githubusercontent.com/dmlc/gluon-nlp/master/tools/diagnose.py | python

# paste outputs here
----------Python Info----------
Version      : 3.7.5
Compiler     : GCC 7.3.0
Build        : ('default', 'Oct 25 2019 15:51:11')
Arch         : ('64bit', '')
------------Pip Info-----------
Version      : 19.3.1
Directory    : /home/ciyong/miniconda3/lib/python3.7/site-packages/pip
----------MXNet Info-----------
Version      : 2.0.0
Directory    : /tmp/mxnet/incubator-mxnet/python/mxnet
Num GPUs     : 0
Hashtag not found. Not installed from pre-built package.
----------System Info----------
Platform     : Linux-3.10.0-957.el7.x86_64-x86_64-with-centos-7.6.1810-Core
system       : Linux
node         : mlt2-clx094
release      : 3.10.0-957.el7.x86_64
version      : #1 SMP Thu Nov 8 23:39:32 UTC 2018
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                112
On-line CPU(s) list:   0-111
Thread(s) per core:    2
Core(s) per socket:    28
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 85
Model name:            Intel(R) Xeon(R) Platinum 8280L CPU @ 2.70GHz
Stepping:              7
CPU MHz:               3310.070
CPU max MHz:           4000.0000
CPU min MHz:           1000.0000
BogoMIPS:              5400.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              1024K
L3 cache:              39424K
NUMA node0 CPU(s):     0-27,56-83
NUMA node1 CPU(s):     28-55,84-111
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni spec_ctrl intel_stibp flush_l1d arch_capabilities
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0103 sec, LOAD: 2.1315 sec.
Timing for GluonNLP GitHub: https://github.com/dmlc/gluon-nlp, DNS: 0.0013 sec, LOAD: 1.9952 sec.
Timing for GluonNLP: http://gluon-nlp.mxnet.io, DNS: 0.0066 sec, LOAD: 2.3918 sec.
Timing for D2L: http://d2l.ai, DNS: 0.1313 sec, LOAD: 0.5946 sec.
Timing for D2L (zh-cn): http://zh.d2l.ai, DNS: 0.0058 sec, LOAD: 0.7973 sec.
Timing for FashionMNIST: https://repo.mxnet.io/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 5.7738 sec, LOAD: 2.1621 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0015 sec, LOAD: 11.5346 sec.
Error open Conda: https://repo.continuum.io/pkgs/free/, HTTP Error 403: Forbidden, DNS finished in 0.010091543197631836 sec.

@ciyongch have you tried mxnet 1.6?

@ciyongch have you tried mxnet 1.6?

Tried with both mxnet 1.6.0 and mxnet-cu90 1.6.0, got same/similar accuracy as my previous results.
It's probably due to the incorrect pre-trained params download from S3 server, can you help to check that?
1) mxnet 1.6.0
----------MXNet Info-----------
Version      : 1.6.0
Directory    : /home/ciyong/miniconda3/envs/mx_release/lib/python3.6/site-packages/mxnet
Num GPUs     : 0
Commit Hash   : 6eec9da55c5096079355d1f1a5fa58dcf35d6752

1.1) output
BigRNN(
  (embedding): HybridSequential(
    (0): Embedding(793471 -> 512, float32)
    (1): Dropout(p = 0.1, axes=())
  )
  (encoder): HybridSequentialRNNCell(
  (0): LSTMPCell(512 -> 8192 -> 512)
  (1): DropoutCell(rate=0.1, axes=())
  )
  (decoder): Dense(512 -> 793471, linear)
)
Vocab(size=793471, unk="<unk>", reserved="['<pad>', '<eos>']")
Best validation loss 9.40, val ppl 12130.84
Best test loss 9.42, test ppl 12303.21

2) mxnet-cu90 1.6.0
----------MXNet Info-----------
Version      : 1.6.0
Directory    : /home/ciyong/miniconda3/envs/mxnet_gpu/lib/python3.6/site-packages/mxnet
Num GPUs     : 1
Commit Hash   : 6eec9da55c5096079355d1f1a5fa58dcf35d6752

2.1) output
BigRNN(
  (embedding): HybridSequential(
    (0): Embedding(793471 -> 512, float32)
    (1): Dropout(p = 0.1, axes=())
  )
  (encoder): HybridSequentialRNNCell(
  (0): LSTMPCell(512 -> 8192 -> 512)
  (1): DropoutCell(rate=0.1, axes=())
  )
  (decoder): Dense(512 -> 793471, linear)
)
Vocab(size=793471, unk="<unk>", reserved="['<pad>', '<eos>']")
Best validation loss 9.41, val ppl 12194.26
Best test loss 9.42, test ppl 12366.94

@ciyongch any update after using the original vocab from the pre-trained model?

@eric-haibin-lin After switching to GBW vocab, I got the better result as below, but there's run-to-run variance, not sure if it's related to the data loader.
(Gluon) Best validation loss 3.92, val ppl 50.46
(Gluon) Best test loss 3.92, test ppl 50.30

Given that most of the recent demand is on transformer based models, we probably won't be able to get to this soon. @ciyongch let me know your use case if you still need this.

Hi @szha, it's ok to close it now, sorry for forgetting close it.


docs/tutorial: fix typos

Fixes to some typos that made the rendered document difficult to understand for me.

@akavel merged! Thank you for the fixes!


Add gap between Console and Edit button.

Goodness Squad https://github.com/oVirt/ovirt-web-ui/issues/380

This change is

Thanks, @rludva !


[stable/redis] fix sentinel restart problems

Is this a new chart
no
What this PR does / why we need it:
Which issue this PR fixes
This is a renewal of PR#19464 that was closed due to inactivity after sucessfully passing the automatic test bed. It seems to exists some interest of this PR, that's why I resend this updated PR.
About the reason of my changes:
I tried to test HA of the redis cluster and the sentinel-conform functionality of our services that uses the redis/sentinel cluster. To perform failover functionality as in real time, I just deleted slave or the master pod and found some abnormalities.
sentinel on master pod doesn't startup, if only setinel container on master pod is restarted (commit 911d2d6)
Interestingly, the redis chart creates a non-symmetrically set of pods: There is one "master" pod that own initially the redis master node and (optionally) several "slave" pods that owns initially a set of redis (and sentinel) nodes in slave mode. As long as the master node is kept untouched, scaling up/down slave pods and even recreating of suddently deleted slave pods work as intended (at least at first glance), because new slave pods can contact a redis via master service. Only if the master pod is created, it has the problem to determine, if it is the first pod of a new cluster (initial cluster startup) or if there are some remains of a running cluster, that lost its master pod. To address this problem, sameersbn added in commit 1adb31c (Chart version 8.0.16) some lines that tries to ask some sentinel for its list of sentinel IPs and add them directly to sentinel.conf. That works perfectly at pod fresh creation (non existing sentinel.conf and thus start with a copy of some template sentinel.conf) but lead to a persisting "error in sentinal configuration at line 21" (line number may vary), if the sentinal container is restarted only - you can easily simulate this by attaching to the sentinel container running on the pod of the master service and kill the sentinel process by typing "kill 1" - K8s will immediately restart the pod in-place (without wiping the folders) and thus, the code from sameersbn will append the well-known setinals a second time (there are still in sentinel.conf from the formerly running sentinel process) and lead to duplicate lines that makes the sentinel process to issue the configuration error instead of starting up. One solution would be to start always with a fresh sentinal.conf but it is worth to preserve the sentinel.conf whenever possible as it contains always the most current state of all sentinel cluster nodes. That's why I changed the code of sameersbn in that way that it is executed only if there is no former well-known sentinel node list found in sentinel.conf.
reset sentinel list after master pod has gone (commit 9be66eb)
While I dealt with the problems of 1. and the article https://redis.io/topics/sentinel, I hit on the notice "Sentinels never forget already seen Sentinels". In a statically configured environment this has no implications if nodes will be restarted/recreated having the former IP addresses. on k8s however, every pod (even after in-place updates or partial container restarts) will get always a new IP address. This leads the known sentinel list in sentinel.conf become larger and larger. Worse, at some point, the K8s cluster will recycle unused IP addresses and if some foreign redis/sentinal cluster gets such an IP address, two independent clusters will (at least partially) get unified and this leads to unexpected results. I observed such a problem on our K8s cluster running several environments/stages of our microservice architecture and thus multiple redis clusters in different K8s namespaces and could not explain at that time, why some sentinels reported redis nodes from an foreign redis cluster.
The fix is simple: just before start of the sentinel I fork a shell that is waiting 120s (fix, enough time to give sentinel to get familiar to each other), then ask the (newly started) sentinel on master pod for all known sentinels, followed by resetting all returned sentinels and the sentinel on master pod. That should work, since at this time all sentinel should follow the same master redis node from which they can acquire the current setinel list.
reset sentinel after helm upgrade (Commit baa5b79)
Finally, the IP address problem decribed in 2. also ocurs while upgrading the helm chart, because pods are potentially are rebuild. Since it it is not ensured, that the master service pod is recreated and the whole upgrade doesn't take more than 120s, I added a job that is a hook of helm chart install/upgrade event and executes the same procedure as mentioned in 2. (reset all sentinals)
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

For this reason, I am interested in if these changes will break the backward compatibility. In case these changes are a major change too we would like to avoid merge it.

I don't expect any problems regarding backward compatibility since no new features are introduced but only bugs of the HA node creation process in the case of node/pod failure are solved and neither additional configuration values were added nor changed.

ping

Sorry, we missed the notification about this PR, we are going to re-review it. Thanks!

Hi again,
Given the stable deprecation timeline, this Bitnami maintained Helm chart is now located at bitnami/charts. Please visit the bitnami/charts GitHub repository to create Issues or PRs.
In this issue we tried to explain more carefully the reasons and motivations behind this transition, please don’t hesitate to add a comment in this issue if you have any question related to the migration itself.
I am sorry for the noise, we didn't realize about that before.

/ok-to-test

ping


NPE is thrown when a consumer consumes a partitioned topic with struct schema

Describe the bug
NPE is thrown when a consumer consumes a partitioned topic (which doesn't have any registered schema) with struct schema.
Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
	at org.apache.pulsar.client.impl.ConsumerBuilderImpl.subscribe(ConsumerBuilderImpl.java:89)
	... 29 more
Caused by: java.lang.NullPointerException
	at org.apache.pulsar.client.impl.PulsarClientImpl.preProcessSchemaBeforeSubscribe(PulsarClientImpl.java:749)
	at org.apache.pulsar.client.impl.PulsarClientImpl.singleTopicSubscribeAsync(PulsarClientImpl.java:332)
	at org.apache.pulsar.client.impl.PulsarClientImpl.subscribeAsync(PulsarClientImpl.java:324)
	at org.apache.pulsar.client.impl.ConsumerBuilderImpl.subscribeAsync(ConsumerBuilderImpl.java:107)
	... 30 more

@congbobo184 please take a look this issue.

what are the steps for the recurrence of this problem and
./pulsar-admin topics create-partitioned-topic -p 3 persistent://public/default/test-npe3

 PulsarClient client = PulsarClient.builder().serviceUrl("pulsar://<IP_ADDRESS>:6650").build();
        Consumer<MessageProcess> consumer = client
                .newConsumer(Schema.AVRO(MessageProcess.class))
                .topic("persistent://public/default/test-npe3")
                .subscriptionName("test")
                .subscribe();
        while (true) {
            Message<MessageProcess> message = consumer.receive();
            consumer.acknowledge(message);

        }

I did not reproduce it in this way.

@congbobo184 I think I made a mistake in the description I provided. The exception was thrown when I use AUTO_CONSUME schema.

OK, I will reproduce this and fix the bug


Automatic HTTPS failed when using TLS-SNI-01

1. What version of Caddy are you running (caddy -version)?
Caddy 0.9.3
2. What are you trying to do?
Use Caddy with multiple domains with automatic HTTPS.
3. What is your entire Caddyfile?
:80 {

        gzip
        proxy / localhost:81 {
            transparent
        }
        log /path/to/logs/access.log

}

domain.xyza {
        gzip
        proxy / localhost:81 {
            header_upstream Host {host}
            header_upstream X-Real-IP {remote}
            header_upstream X-Forwarded-For {remote}
            header_upstream X-Forwarded-Proto http
        }
        log /path/to/logs/access.log
}

(config for other domains is the same as the one for domain.xyza, except the domain name)
4.  What did you expect to see?
Caddy to automatically grab SSL certs for all of my domains from Let's encrypt, and starts using it.
6. What did you see instead (give full error messages and/or log)?
Activating privacy features...2016/12/19 21:52:46 [INFO][example.com] acme: Obtaining bundled SAN certificate
2016/12/19 21:52:46 [INFO][example.com] acme: Trying to solve HTTP-01
2016/12/19 21:52:47 [INFO][example.com] Served key authentication
2016/12/19 21:52:48 [INFO][example.com] The server validated our request
2016/12/19 21:52:48 [INFO][example.com] acme: Validations succeeded; requesting certificates
2016/12/19 21:52:49 [INFO] acme: Requesting issuer cert from https://acme-v01.api.letsencrypt.org/acme/issuer-cert
2016/12/19 21:52:49 [INFO][example.com] Server responded with a certificate.
2016/12/19 21:52:49 [INFO][random-domain.xyza] acme: Obtaining bundled SAN certificate
2016/12/19 21:52:49 [INFO][random-domain.xyza] acme: Trying to solve TLS-SNI-01
2016/12/19 21:52:56 [random-domain.xyza] failed to get certificate: acme: Error 400 - urn:acme:error:connection - Failed to connect to x.x.x.x:443 for TLS-SNI-01 challenge

Caddy successfully retrieves SSL certs for domains with HTTP-01. However, at some point when obtaining the certificates it randomly switches to TLS-SNI-01 which fails, because it apparently cannot connect to port 443.
Not sure why it's not using HTTP-01 verification for all domains. Restarting Caddy helps, at least until it switches back to TLS-SNI-01 verification. I had to verify approximately 50 domains, and needed to restart Caddy at least 10 times.
Port 443 is not blocked and works just fine, because after Caddy successfully verified all domains (using HTTP-01), it started serving websites via HTTPS without a problem.

Unfortunately, I cannot reproduce this behavior with what you've given here. I just tried your configuration with my own domain and it works just fine.

Thanks for checking it out. I tried to reproduce the issue on another server, but couldn't get TLS-SNI-01 to fail. I guess it's a problem with the configuration of the first server, but oddly enough, SSL works without a problem, after the certs were successfully requested.


Support S2I and CNB when using Tekton for CICD

https://github.com/konveyor/move2kube/blob/d2b0fc1ee2f02fd6788ed3f122dadffb23c62097/internal/apiresource/pipeline.go#L148-L151

S2I and CNB can be achieved using customization, since each company has different ways of using them.


Implement load lanes opcodes for wasm

Tested using a simple wat file while we're still setting up the testsuite

the failure in CI is
Running: ../../../product-mini/platforms/linux/build/iwasm --heap-size=0 --repl --stack-size=10485760 /tmp/tmpersehdkx.aot
module is ....'(module
    (rec (type $f1 (func)) (type (struct (field (ref $f1)))))
    (rec (type $f2 (func)) (type (struct (field (ref $f1)))))
    (func $f (type $f2))
    (global (ref $f1) (ref.func $f))
  )'
exception is ....'type mismatch'
Writing WAST module to '/tmp/tmp_0kh_4j_.wast'
Compiling WASM to '/tmp/tmpg5mpng73.wasm'
Running: spec/interpreter/wasm -u -d /tmp/tmp_0kh_4j_.wast -o /tmp/tmpg5mpng73.wasm
Compiling '/tmp/tmpg5mpng73.wasm' to '/tmp/tmpersehdkx.aot'

@wenyongh I don't think it's related to my PR in any way, if you agree can we merge?

the failure in CI is
Running: ../../../product-mini/platforms/linux/build/iwasm --heap-size=0 --repl --stack-size=10485760 /tmp/tmpersehdkx.aot
module is ....'(module
    (rec (type $f1 (func)) (type (struct (field (ref $f1)))))
    (rec (type $f2 (func)) (type (struct (field (ref $f1)))))
    (func $f (type $f2))
    (global (ref $f1) (ref.func $f))
  )'
exception is ....'type mismatch'
Writing WAST module to '/tmp/tmp_0kh_4j_.wast'
Compiling WASM to '/tmp/tmpg5mpng73.wasm'
Running: spec/interpreter/wasm -u -d /tmp/tmp_0kh_4j_.wast -o /tmp/tmpg5mpng73.wasm
Compiling '/tmp/tmpg5mpng73.wasm' to '/tmp/tmpersehdkx.aot'

@wenyongh I don't think it's related to my PR in any way, if you agree can we merge?

Yes, please merge. BTW, I re-ran the CI.


Revision number increased when editing tags

Our implementation will only increase revision count if the content or license changed, maybe the user touched the content. Anyway, we should be reproduced it first.


fallback support factoryBean  2021.x branch

Describe what this PR does / why we need it
https://github.com/alibaba/spring-cloud-alibaba/pull/3135#issuecomment-1436418739
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

LGTM


Java Imports Optimizer

IntelliJ has a custom process for running optimize imports action.
This process can be triggerred as a pre-commit action. The problem arises when IntelliJ imports optimizer behaves differently comparing to what Java formatting plugin can do.
As a solution I'm adding a hook for optimize imports action. Dprint core is language agnostic and does not support a special message like "optimize imports". Therefore, I'm invoking plain format action assuming that underlying formatter will do imports optimization on it's own.
Open question: should I add a checkbox to the IJ plugin settings which will enable/disable Imports optimizer?

Hey @ryan-rushton ! Would you mind to take a look at thus proposal?

CC @FireFry

Can do! Will check it out today.


DgrmJS dispatch events, developers can use these events to implement their own logic, for example, make a JSON description of the workflow?

From your write up, it says
https://medium.com/codex/javascript-svg-diagram-editor-which-weighs-6-5-less-than-bootstrap-open-source-library-b753feaaf835
DgrmJS dispatch events, like ‘shape is selected’ or ‘shape is connecting to another shape’.
Developers can use these events to implement their own logic, for example, make a JSON description of the workflow.
Can please help to give an sample code on how to use these events?
Can please help to give an sample code on how to implement own logic to generate json description of the workflow?

Thanks for your interest in the dgrm.

how to use these events?

It is old article, now there are no events.
For json serialization please see
https://github.com/AlexeyBoiko/DgrmJS/blob/main/src/diagram/dgrm-serialization.js
Please note: source code in this repo is different from https://app.dgrm.net/ .
app.dgrm.net has pro features like "undo/redo".


GoDoc overview info

Objective
The overview documentation page is too sparse.
Acceptance Criteria

The landing page for GoDoc contains information about the project
The new Golang doc site for this package is more useful: https://pkg.go.dev/github.com/newrelic/newrelic-client-go?tab=subdirectories

Resolved by #188


Failed to open file: /tmp/.gln1VlUe (deleted)

Description of your problem
Spyder keeps querying for a non-existent temporary file
[0217/012305.088782:WARNING:stack_trace_posix.cc(648)] Failed to open file: /tmp/.gln1VlUe (deleted)
What steps will reproduce the problem?

Install python 3.6.3
Install spyder in a virtual environment using pew or venv
Start spyder

What is the expected output? What do you see instead?
Spyder launches, just reporting the error since I couldn't find any mention of this in the closed issues or on the google group.
Please provide any additional information below
Versions and main components

Spyder Version: 3.2.6
Python Version: 3.6.3
Qt Version: 5.9.1
PyQt Version: PyQt 5.10
Operating system: Ubuntu 17.10

Dependencies
IPython >=4.0    :  6.2.1 (OK)
cython >=0.21    :  None (NOK)
jedi >=0.9.0     :  0.11.1 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.14.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
psutil >=0.3     :  5.4.3 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.8.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
sphinx >=0.6.6   :  1.7.0 (OK)
sympy >=0.7.3    :  1.1.1 (OK)

Thanks for reporting. As you state, I can't find any issues that appear to be similar. However, from your description, it sounds like you're installing Spyder via the "expert" method using pip or your distribution's Python, but as our readme, install instructions and documentation states, due to limited resources and the many potential pip-falls of that approach, we are unable to provide individual support for installation-related problems (as this appears to be), and recommend you install the Anaconda distribution instead.
You can try resolving this by reinstalling, manually creating the file, or restting Spyder's configuration with spyder --reset. Also, please try the steps listed in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve the great majority of Spyder installation issues.
If you complete all of that and have reason to believe it is related to Spyder itself and not your installation, then please post the information requested in the guide here. Otherwise, or if we can confirm it is an installation issue, this issue will be closed after one week (7 days). Thanks, and best of luck!

Fortunately it doesn't interfere with using spyder. I did try both I tried modifying the source code in the MainWindow class to eliminate temp file loading but it didn't alleviate the problem.  I've also tried the suggested troubleshooting steps in the Troubleshooting guide First Aid/CPR sections to no luck. If I can figure out a fix/modification on my own I will post. Otherwise is there any additional information I should post for future reference?

Thanks for the followup

is there any additional information I should post for future reference?

I'm still unclear on exactly what specific symptoms you're experiencing. In what form are you receiving the above error message—in a "Report Error" dialog, in a warning popup, in the console or how? Is that the exact and complete message? At what point in Spyder startup does it occur? Does it only happen in a virtual environment? Do you see any pertinent output when running with spyder --debug or setting the environment variable SPYDER_DEBUG=3 and then running Spyder from the same command prompt, as the guide suggests?
If you could describe your circumstances in more detail, and post the remaining information listed under the relevant subsection of the guide, that would be helpful as well. It still seems likely to have something to do with your specific pip manual install, but this should hopefully at least help us narrow that down or not, and if you have a proper fix then we would be glad to review a PR if it really is an issue on the Spyder side. Thanks.

Sorry about that, I thought I included everything under the troubleshooting guide in my initial post.
(spyder) ➜  ~ export SPYDER_DEBUG=3
(spyder) ➜  ~ spyder3
Start of MainWindow constructor
End of MainWindow constructor
*** Start of MainWindow setup ***
  ..core actions
  ..toolbars
  ..tools
  ..sift?
  ..plugin: internal console
    ..internal console: initializing
  ..plugin: working directory
Loading help...
**[0218/115843.159710:WARNING:stack_trace_posix.cc(648)] Failed to open file: /tmp/.glRW0ytz (deleted)**
  Error: No such file or directory
Loading outline explorer...
Loading editor...
Introspection Plugin Loaded: rope
Introspection Plugin Loaded: jedi
Introspection Plugin Loaded: fallback
setfocusto: <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7fb39831c5e8>
current_changed: 0 <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7fb39831c5e8><PHONE_NUMBER>72296
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7fb398264b88> to queue
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7fb398264ca8> to queue
  ..widgets
Loading file explorer...
Loading history plugin...
Loading online help...
Loading project explorer...
Loading namespace browser...
Loading IPython console...
Updating queue:
    started: 0
    pending: 2
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7fb398264b88>
Updating queue:
    started: 1
    pending: 1
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7fb398264ca8>
Setting up main window...
Updating queue:
    started: 0
    pending: 0
Updating queue:
    started: 0
    pending: 0
Setting up window...
*** End of MainWindow setup ***
Call to 'close_threads'
Initialized fallback
setfocusto: <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7fb39825e828>
current_changed: 0 <spyder.widgets.sourcecode.codeeditor.CodeEditor object at 0x7fb39825e828><PHONE_NUMBER>94632
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7fb3d49ffca8> to queue
Added thread <spyder.widgets.editor.AnalysisThread object at 0x7fb3d4a011f8> to queue
Updating queue:
    started: 0
    pending: 2
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7fb3d49ffca8>
Updating queue:
    started: 1
    pending: 1
===>starting: <spyder.widgets.editor.AnalysisThread object at 0x7fb3d4a011f8>
Updating queue:
    started: 1
    pending: 0
Updating queue:
    started: 0
    pending: 0
Initialized jedi
Initialized rope

Sorry for the delay following up. I can't be sure precisely what causes this, though likely a more experienced hand here does, but I'm surprised that spyder --reset doesn't fix it. It can be isolated to something between the start of loading the help plugin and the start of loading the outline explorer, possibly in the Help class (in spyder/plugins/help.py) __init__ method (or possibly its register_plugins method), if you'd like to look. However, it seems system specific and is only a warning, so I'm not sure I'd worry about it too much...

Closing because of lack of response.

It doesn't seem related to Spyder.

Just a note, googling for the same error I ended up here.
In my case it has nothing to do with Spyder, in my case it was an issue on the PyQt5 side and opengl version installed by mesa which was in conflict with the one installed by the nvidia drivers.
Removing the affected files fixed the issue for me.

Thanks for letting us know @epifanio!

Just a note, googling for the same error I ended up here.
In my case it has nothing to do with Spyder, in my case it was an issue on the PyQt5 side and opengl version installed by mesa which was in conflict with the one installed by the nvidia drivers.
Removing the affected files fixed the issue for me.

I encounter the exact same problem. Could you describe the detail 'removing the affected files xxx'  for me? I appreciate it if you can offer any help.