Failed to activate the omnisharp-atom package

[Enter steps to reproduce:]

...
...

Atom: 1.34.0 x64
Electron: 2.0.16
OS: "openSUSE Tumbleweed"
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:516:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9344:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (/usr/share/atom/resources/app/static/<embedded>:11:2921267)
    at measure (/usr/share/atom/resources/app/static/<embedded>:11:2920679)
    at Package.measure (/usr/share/atom/resources/app/static/<embedded>:11:2918310)
    at activationPromise.activationPromise.Promise (/usr/share/atom/resources/app/static/<embedded>:11:2920539)
    at new Promise (<anonymous>)
    at Package.activate (/usr/share/atom/resources/app/static/<embedded>:11:2920482)
    at PackageManager.activatePackage (/usr/share/atom/resources/app/static/<embedded>:11:382681)
    at config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:382297)
    at Config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:332481)
    at PackageManager.activatePackages (/usr/share/atom/resources/app/static/<embedded>:11:382247)
    at PackageManager.activate (/usr/share/atom/resources/app/static/<embedded>:11:381865)
    at t.loadState.then (/usr/share/atom/resources/app/static/<embedded>:1:660921)
    at <anonymous>

Commands

Non-Core Packages
omnisharp-atom 0.31.2
platformio-ide-terminal 2.9.1

Same happened to me on Windows 10

Also happens on Macos Mojave.

Same issue here, tryna script for Unity.

Same here

Also on gnu/linux ubuntu 18.04

Also happened on MacOS High Sierra.

An issue on macOS Mojave (10.14.4)

FYI progress for this exists in this thread.
You can get the package to install properly making the following changes to C:\Users\<name>\.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:
Line 140
var grammars = atom.grammars;
to
var grammars = atom.grammars.textmateRegistry || atom.grammars;
Line 145
Change atom.grammars to just grammars
However I still couldn't get the OmniSharp server connection working after that (I'm guessing because of this). It looks like this repository has been depricated in favor of VS Code. Try a different package or switch IDEs.

Thanks @samgovier, this removed the error, but I can't get the completion to work: it just disappeared. What could I do with this?

[Enter steps to reproduce:]

...
...

Atom: 1.41.0 x64
Electron: 4.2.7
OS: Microsoft Windows 10 Home Single Language
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:516:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9342:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:3313556)
    at measure (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:3312968)
    at Package.measure (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:3310578)
    at activationPromise.activationPromise.Promise (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:3312828)
    at new Promise (<anonymous>)
    at Package.activate (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:3312771)
    at PackageManager.activatePackage (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:382554)
    at ~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:940004
    at r (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:11:934610)
    at n (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:14:1128190)
    at ChildProcess.o.process.on.e (~/AppData/Local/atom/app-1.41.0/resources/app/static/<embedded>:14:1128396)
    at ChildProcess.emit (events.js:182:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)

Commands
  4x -2:32.2.0 core:backspace (input.hidden-input)
     -2:26.2.0 editor:newline (input.hidden-input)
     -2:23.1.0 core:backspace (input.hidden-input)
  2x -2:20.9.0 editor:newline (input.hidden-input)
     -1:55.4.0 core:backspace (input.hidden-input)
     -1:54.1.0 editor:newline (input.hidden-input)
     -1:38.8.0 core:backspace (input.hidden-input)
     -1:36.8.0 autocomplete-plus:confirm (input.hidden-input)
     -1:36.7.0 snippets:expand (atom-text-editor.editor.is-focused.autocomplete-active)
     -1:35.3.0 core:undo (input.hidden-input)
  8x -1:33.9.0 core:backspace (input.hidden-input)
     -1:23.7.0 core:select-all (input.hidden-input)
  6x -1:22.8.0 core:backspace (input.hidden-input)
  2x -1:16.6.0 editor:newline (input.hidden-input)
  2x -1:08.3.0 core:backspace (input.hidden-input)
  2x -1:01.9.0 editor:newline (input.hidden-input)

Non-Core Packages
autocomplete-plus-async 0.22.0
language-asp 1.1.1
language-aspx 0.5.0
omnisharp-atom 0.31.2
teletype 0.13.4

Also happened on macOS Cataline (10.15.1).

Even with the edited file, the error still goes :
`atom.grammars.startIdForScope is not a function
TypeError: atom.grammars.startIdForScope is not a function
at grammarCb (C:\Users\artpn.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:145:35)
at arrayEach (C:\Users\artpn.atom\packages\omnisharp-atom\node_modules\lodash\lodash.js:516:11)
at forEach (C:\Users\artpn.atom\packages\omnisharp-atom\node_modules\lodash\lodash.js:9342:14)
at OmniSharpAtom.activate (C:\Users\artpn.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:153:30)
at Package.activateNow (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3313556)
at measure (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3312968)
at Package.measure (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3310578)
at activationPromise.activationPromise.Promise (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3312828)
at new Promise ()
at Package.activate (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3312771)
at PackageManager.activatePackage (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:382554)
at o.forEach.e (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:377720)
at Array.forEach ()
at disabledPackagesSubscription.disabledPackagesSubscription.config.onDidChange (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:377704)
at emitter.on (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:334755)
at Function.simpleDispatch (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:1211909)
at Emitter.emit (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:1213350)
at Config.emitChangeEvent (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:337243)
at Config.setRawValue (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:334483)
at Config.set (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:330277)
at Config.removeAtKeyPath (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:332300)
at Package.enable (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:3310363)
at PackageManager.enablePackage (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:11:375418)
at HTMLButtonElement.enablementButtonClickHandler (C:\Users\artpn\AppData\Local\atom\app-1.41.0\resources\app\static<embedded>:14:2603767)
The error was thrown from the omnisharp-atom package. This issue has already been reported.
`

Same here in Ubuntu 18.04.3
[Enter steps to reproduce:]

...
...

Atom: 1.43.0 x64
Electron: 4.2.7
OS: Ubuntu 18.04.3
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:516:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9342:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (/usr/share/atom/resources/app/static/<embedded>:11:3209961)
    at measure (/usr/share/atom/resources/app/static/<embedded>:11:3209373)
    at Package.measure (/usr/share/atom/resources/app/static/<embedded>:11:3206983)
    at activationPromise.activationPromise.Promise (/usr/share/atom/resources/app/static/<embedded>:11:3209233)
    at new Promise (<anonymous>)
    at Package.activate (/usr/share/atom/resources/app/static/<embedded>:11:3209176)
    at PackageManager.activatePackage (/usr/share/atom/resources/app/static/<embedded>:11:382452)
    at config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:382068)
    at Config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:331716)
    at PackageManager.activatePackages (/usr/share/atom/resources/app/static/<embedded>:11:382018)
    at PackageManager.activate (/usr/share/atom/resources/app/static/<embedded>:11:381568)
    at t.loadState.then (/usr/share/atom/resources/app/static/<embedded>:1:715031)

Commands

Non-Core Packages
autocomplete-unity 0.1.3
busy-signal 2.0.1
intentions 1.1.5
linter 2.3.1
linter-ui-default 1.8.1
omnisharp-atom 0.31.2

Failed to acitvate the omnisharp-atom package.
omnisharp-atom 0,31.2
windows 10
atom 1.4.3 x64
TypeError: atom.grammars.startIdForScope is not a function
at grammarCb (C:\Users\home.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:145:35)
at arrayEach (C:\Users\home.atom\packages\omnisharp-atom\node_modules\lodash\lodash.js:516:11)
at forEach (C:\Users\home.atom\packages\omnisharp-atom\node_modules\lodash\lodash.js:9342:14)
at OmniSharpAtom.activate (C:\Users\home.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:153:30)
at Package.activateNow (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:3317257)
at measure (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:3316669)
at Package.measure (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:3314279)
at activationPromise.activationPromise.Promise (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:3316529)
at new Promise ()
at Package.activate (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:3316472)
at PackageManager.activatePackage (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:382452)
at C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:941017
at r (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:11:935623)
at n (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:14:1124557)
at ChildProcess.o.process.on.e (C:\Users\home\AppData\Local\atom\app-1.43.0\resources\app\static<embedded>:14:1124763)
at ChildProcess.emit (events.js:182:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)

Atom: 1.44.0 x64
Electron: 4.2.12
OS: "Manjaro Linux"
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/usr/lib/atom/node_modules/markdown-preview/node_modules/lodash/lodash.js:516:11)
    at forEach (/usr/lib/atom/node_modules/markdown-preview/node_modules/lodash/lodash.js:9344:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (/usr/lib/atom/src/package.js:241:27)
    at measure (/usr/lib/atom/src/package.js:210:27)
    at Package.measure (/usr/lib/atom/src/package.js:81:19)
    at activationPromise.Promise (/usr/lib/atom/src/package.js:204:14)
    at new Promise (<anonymous>)
    at Package.activate (/usr/lib/atom/src/package.js:202:32)
    at PackageManager.activatePackage (/usr/lib/atom/src/package-manager.js:790:36)
    at config.transactAsync (/usr/lib/atom/src/package-manager.js:765:30)
    at Config.transactAsync (/usr/lib/atom/src/config.js:925:22)
    at PackageManager.activatePackages (/usr/lib/atom/src/package-manager.js:763:17)
    at PackageManager.activate (/usr/lib/atom/src/package-manager.js:740:44)
    at loadStatePromise.loadState.then (/usr/lib/atom/src/atom-environment.js:1017:21)

Commands

Non-Core Packages
atom-beautify 0.33.4
git-plus 8.7.1
gpp-compiler 3.0.7
omnisharp-atom 0.31.2

[Enter steps to reproduce:]

...
...

Atom: 1.45.0 x64
Electron: 4.2.7
OS: Linux Mint
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:516:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9342:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (/usr/share/atom/resources/app/static/<embedded>:11:3219604)
    at measure (/usr/share/atom/resources/app/static/<embedded>:11:3219016)
    at Package.measure (/usr/share/atom/resources/app/static/<embedded>:11:3216626)
    at activationPromise.activationPromise.Promise (/usr/share/atom/resources/app/static/<embedded>:11:3218876)
    at new Promise (<anonymous>)
    at Package.activate (/usr/share/atom/resources/app/static/<embedded>:11:3218819)
    at PackageManager.activatePackage (/usr/share/atom/resources/app/static/<embedded>:11:382452)
    at config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:382068)
    at Config.transactAsync (/usr/share/atom/resources/app/static/<embedded>:11:331716)
    at PackageManager.activatePackages (/usr/share/atom/resources/app/static/<embedded>:11:382018)
    at PackageManager.activate (/usr/share/atom/resources/app/static/<embedded>:11:381568)
    at t.loadState.then (/usr/share/atom/resources/app/static/<embedded>:1:717298)

Commands

Non-Core Packages
atom-beautify 0.33.4
busy-signal 2.0.1
file-icons 2.1.40
git-plus 8.7.1
gpp-compiler 3.0.7
Hydrogen 2.14.1
ide-csharp 0.6.2
intentions 1.1.5
linter 2.3.1
linter-ui-default 1.8.1
omnisharp-atom 0.31.2
platformio-ide-terminal 2.10.0

similar issue on the macOS BigSur is there a different package for C# ?

I'm also getting the same error. For anyone else reading this, please take a good look at the latest commit made on the omnisharp-atom repository: It was waaaaaay back on 13 April 2017 lol
And the latest forked commit is by Techcraft7 on 24 September 2020, see this pull request for more information.
With that being said, omnisharp-atom needs more contributors, so if anyone wants to help out, please do so! :)
[Enter steps to reproduce:]

Install the plugin
Nothing else needs to be done

Atom: 1.57.0 x64
Electron: 9.4.4
OS: Ubuntu 20.04.2
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:530:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9410:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (<embedded>:11:3388858)
    at <embedded>:11:3388270
    at Package.measure (<embedded>:11:3385848)
    at <embedded>:11:3388130
    at new Promise (<anonymous>:null:null)
    at Package.activate (<embedded>:11:3388073)
    at PackageManager.activatePackage (<embedded>:11:385497)
    at <embedded>:11:914488
    at r (<embedded>:11:909094)
    at n (<embedded>:14:1190909)
    at <embedded>:14:1191063
    at Socket.<anonymous> (<embedded>:14:1189665)
    at Socket.emit (events.js:228:7)
    at Pipe.<anonymous> (net.js:664:12)

Commands

Non-Core Packages
omnisharp-atom 0.31.2

[Enter steps to reproduce:]

...
...

Atom: 1.58.0 x64
Electron: 9.4.4
OS: Microsoft Windows 10 Pro
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:530:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9410:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3508863)
    at ~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3508275
    at Package.measure (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3505853)
    at ~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3508135
    at new Promise (<anonymous>)
    at Package.activate (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3508078)
    at PackageManager.activatePackage (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:385612)
    at ~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:915033
    at r (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:909639)
    at n (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:14:1194945)
    at ChildProcess.<anonymous> (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:14:1195151)
    at ChildProcess.emit (events.js:223:5)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)

Commands

Non-Core Packages
busy-signal 2.0.1
intentions 2.1.1
kite 0.206.0
linter 3.4.0
linter-ui-default 3.4.1
omnisharp-atom 0.31.2

[Enter steps to reproduce:]

...
...

Atom: 1.58.0 x64
Electron: 9.4.4
OS: "Arch Linux"
Thrown From: omnisharp-atom package 0.31.2
Stack Trace
Failed to activate the omnisharp-atom package
At atom.grammars.startIdForScope is not a function

TypeError: atom.grammars.startIdForScope is not a function
    at grammarCb (/packages/omnisharp-atom/dist/omnisharp-atom.js:145:35)
    at arrayEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:530:11)
    at forEach (/packages/omnisharp-atom/node_modules/lodash/lodash.js:9410:14)
    at OmniSharpAtom.activate (/packages/omnisharp-atom/dist/omnisharp-atom.js:153:30)
    at Package.activateNow (/usr/lib/atom/src/package.js:242:27)
    at /usr/lib/atom/src/package.js:211:27
    at Package.measure (/usr/lib/atom/src/package.js:82:19)
    at /usr/lib/atom/src/package.js:205:14
    at new Promise (<anonymous>)
    at Package.activate (/usr/lib/atom/src/package.js:203:32)
    at PackageManager.activatePackage (/usr/lib/atom/src/package-manager.js:800:36)
    at /usr/lib/atom/node_modules/settings-view/lib/package-manager.js:477:29
    at exit (/usr/lib/atom/node_modules/settings-view/lib/package-manager.js:114:16)
    at triggerExitCallback (/usr/lib/atom/src/buffered-process.js:280:9)
    at /usr/lib/atom/src/buffered-process.js:301:9
    at Socket.<anonymous> (/usr/lib/atom/src/buffered-process.js:169:7)
    at Socket.emit (events.js:228:7)
    at Pipe.<anonymous> (net.js:664:12)

Commands
     -9:46.1.0 editor:newline (input.hidden-input)
     -9:41.6.0 autocomplete-plus:confirm (input.hidden-input)
     -9:39.1.0 editor:delete-to-beginning-of-word (input.hidden-input)
  6x -9:37 core:undo (input.hidden-input)
     -7:29.6.0 editor:delete-to-beginning-of-word (input.hidden-input)
  2x -7:27.1.0 core:backspace (input.hidden-input)
     -6:37.3.0 editor:delete-to-beginning-of-word (input.hidden-input)
  2x -6:26.3.0 core:backspace (input.hidden-input)
     -4:41.6.0 editor:delete-to-beginning-of-word (input.hidden-input)

Non-Core Packages
omnisharp-atom 0.31.2
vim-mode-plus 1.36.6

FYI progress for this exists in this thread. You can get the package to install properly making the following changes to C:\Users\<name>\.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:
Line 140
var grammars = atom.grammars; to var grammars = atom.grammars.textmateRegistry || atom.grammars;
Line 145
Change atom.grammars to just grammars
However I still couldn't get the OmniSharp server connection working after that (I'm guessing because of this). It looks like this repository has been depricated in favor of VS Code. Try a different package or switch IDEs.

This helps me.

Also happened on LMDE 4. ;.;

FYI progress for this exists in this thread. You can get the package to install properly making the following changes to C:\Users\<name>\.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:
Line 140
var grammars = atom.grammars; to var grammars = atom.grammars.textmateRegistry || atom.grammars;
Line 145
Change atom.grammars to just grammars
However I still couldn't get the OmniSharp server connection working after that (I'm guessing because of this). It looks like this repository has been depricated in favor of VS Code. Try a different package or switch IDEs.

this totally fixed the issue. why not make a pull request?

FYI progress for this exists in this thread. You can get the package to install properly making the following changes to C:\Users\<name>\.atom\packages\omnisharp-atom\dist\omnisharp-atom.js:
Line 140
var grammars = atom.grammars; to var grammars = atom.grammars.textmateRegistry || atom.grammars;
Line 145
Change atom.grammars to just grammars
However I still couldn't get the OmniSharp server connection working after that (I'm guessing because of this). It looks like this repository has been depricated in favor of VS Code. Try a different package or switch IDEs.

(2022) Worked for me on Mac OSX  Monterey 12.6


make definition of Deployment clear

Before:
a Kubernetes Deployment is an object that can represent an application running on your cluster.
After:
Kubernetes Deployment is a controller build upon the basic objects. It can represent an application running on your cluster.
Evidence:
kubernetes-objects

In addition, Kubernetes contains a number of higher-level abstractions called Controllers. Controllers > build upon the basic objects, and provide additional functionality and convenience features. They
include:

ReplicaSet
Deployment
StatefulSet
DaemonSet
Job

/assign @jimangel


Many publications not found at Google scholar (some of which have been found before)

Citation -2 instead for actual citation for many entries, which have been correctly found before, including:
DDP:EMSE17
DABW:STTT17
CBA:OOPSLA17
DL:iFM16
HNTS:ISoLA16
MTS+:ICSE16
...
Entries still not found:
MKR+:ICSE16

Seems that they changed the site again. It should be solved with a new regex for the entries and citations.


Some tutorials don't compile

I started experimenting with K framework and found that some of the tutorials don't compile.
I'm using Version 3.5.2 downloaded from https://github.com/kframework/k/releases on Windows 7.
> cd tutorial\1_k\1_lambda\lesson_2
> kompile lambda.k
[Error] Critical: Found two modules with the same name: SUBSTITUTION
        Source: File: C:\Programs\K\include\modules\substitution.k
        Location: (158,1,298,9)

> cd tutorial\1_k\5_types\lesson_9.5
> kompile lambda.k
[Error] Critical: Found two modules with the same name: SUBSTITUTION
        Source: File: C:\Programs\K\include\modules\substitution.k
        Location: (158,1,298,9)

Probably would be easy to have a script that tries to compile all the samples/tutorials and see which ones fail.

@grosu we added a note to the readme about this, but people keep getting tripped up. I think we need to release a K 3.6 so that people who just try out K by downloading the latest release and then running the tutorial don't run into this problem. I still want to release a K 4.0 when we finish the KORE translation, but we should probably do a short term fix in case that doesn't happen for a while yet.

@egonelbre in response to your question, we kind of screwed up the tutorial in this release because it was part of our transition away from using Maude internally, and so you actually have to specify an extra option to get it to work. You can run kompile --backend java lambda.k or you can download the unstable version if you'd rather, which should be just as functional, and actually performs faster on many examples.

@dwightguth sure, these things happen occasionally :). Thanks for the tip.

Is there any reason to not release 3.6? Any drawback that you an think of?  @dwightguth , @cos , @andreistefanescu ?  If not, then I think we should release 3.6 asap.

We should release 3.6.

Since nobody complained,  let's release.
@dwightguth can you please release?
@pdaian can you please make sure that kweb also works?

I think we can close this issue.


fix: Update Docusaurus

Signed-off-by: ErikQQY<EMAIL_ADDRESS>

@ErikQQY this kind of PR is actually not very useful for us. Closed here..


fix: k8s-gateway issue with pihole aka DNS loop

It's annoying to add every record manually via terraform. I need to find a way how to fix dns loop so I can use k8s-gateway again.

Fixed by moving to nextdns.


Move Allure screenshot attachment

Moving to Allure screenshot attaching inside the screenshot try/catch block
If there is an exception saving a screenshot it should not try and add a file that does not exist to the Allure report.

Makes sense. Thank you!


Improve reason output when chart-testing fails

For example, current reason when no OC cluster is available is:
Error waiting for process: exit status 1
Need to make sure error message provides a good indication of the underlying problem.

IBM were seeing this message today and were complaining it did not tell them anything. They were running the quay image using docker.
When David ran their chart he saw the same message and difficult to know what the problem was. David then ran the same chart but using the command line version and this came out before the report:
Error: execution error at (ibm-object-storage-plugin/templates/flex-driver-sa.yaml:3:61): License must be accepted by setting license key to true
Deleting release 'ibm-object-storage-plugin-mng7o4fjcq'...
Error: uninstall: Release not loaded: ibm-object-storage-plugin-mng7o4fjcq: release: not found
Error deleting Helm release: Error waiting for process: exit status 1

Suddenly we had something to work with and David found the issue.

The output of external commands such as helm and kubectl which are
executed during the chart-testing check was being streamed to
Stdout, the same destination the report is streamed to and has been
silenced in #106:
func (h Helm) Test(namespace string, release string) error {
	_, err := h.RunProcessAndCaptureOutput("helm", "test", release, "--namespace", namespace, h.extraArgs)
	return err
}

func (h Helm) DeleteRelease(namespace string, release string) {
	_, _ = h.RunProcessAndCaptureOutput("helm", "uninstall", release, "--namespace", namespace, h.extraArgs)
}

It is likely the output should be captured together with an error, if
one is produced, and propagated to user.


Drop and move marker

Hello,
There is a way to move/marker and get the lat/lng ?
Thanks

I recommend having a look at the marker options example. You will notice that the @move event emits the position for you to use.
The update for this I'm working on now will change the event name to be more consistent with the Google Maps docs, but for now I think you want @move.

Alright what I need thanks :)

The move event does not fired on my code, also in marker options example

Thanks for finding this. Problem solved. Surprised it hasn't been complained about before 🤔
Check it's working on your side @kossa and then close this if it's good.
The next version will have much better support in this area.

I confirm it works fine


add Contribution guidelines, per GitHub Community

https://github.com/enlitepro/enlite-monolog/community

additional resources:

https://github.com/blog/1184-contributing-guidelines
https://help.github.com/articles/setting-guidelines-for-repository-contributors/

closing due to inactivity


Refactor Gelato web3 function deployment script for redstone oracles

What was the problem?
This PR resolves #210
How was it solved?
Update as specified
How was it tested?
cd web3-functions/redstone
cp .env.example .env
yarn
yarn w3f:test

@Incede If it helps, I was able to achieve the same functionality by updating the following:
web3-functions/redstone/package.json:
  "dependencies": {
    "@redstone-finance/evm-connector": "^0.6.2",
    "ethers": "^5.7.2",
    "redstone-protocol": "^1.0.5"
  }

web3-functions/redstone/index.ts:
    case REDSTONE_PRIMARY_PROD:
      wrappedOracle = WrapperBuilder.wrap(oracle).usingDataService({
        dataServiceId: REDSTONE_PRIMARY_PROD,
        uniqueSignersCount: 2,
        dataPackagesIds: dataFeedIdsString,
      });
      break;

    case REDSTONE_MAIN_DEMO:
      wrappedOracle = WrapperBuilder.wrap(oracle).usingDataService({
        dataServiceId: REDSTONE_MAIN_DEMO,
        uniqueSignersCount: 1,
        dataPackagesIds: dataFeedIdsString,
      });

@Incede If it helps, I was able to achieve the same functionality by updating the following and the hardcoded GW values can also be removed:
web3-functions/redstone/package.json:
  "dependencies": {
    "@redstone-finance/evm-connector": "^0.6.2",
    "ethers": "^5.7.2",
    "redstone-protocol": "^1.0.5"
  }

web3-functions/redstone/index.ts:
    case REDSTONE_PRIMARY_PROD:
      wrappedOracle = WrapperBuilder.wrap(oracle).usingDataService({
        dataServiceId: REDSTONE_PRIMARY_PROD,
        uniqueSignersCount: 2,
        dataPackagesIds: dataFeedIdsString,
      });
      break;

    case REDSTONE_MAIN_DEMO:
      wrappedOracle = WrapperBuilder.wrap(oracle).usingDataService({
        dataServiceId: REDSTONE_MAIN_DEMO,
        uniqueSignersCount: 1,
        dataPackagesIds: dataFeedIdsString,
      });

redstone-protocol is deprecated. We could use @redstone-finance/protocol.
Nice, as you already tested the functionality, I'd take that disablePayloadsDryRun is redundant and can be safely removed.


Remove the navbar on the left

There wasn't really much point to the navigation bar on the left because the hierarchy of this project is pretty straightforward:

home

model 1
model 2
model 3
...

Giving each model a separate entry in the navigation bar would become very cluttered because we have about 30 model pages and the aim is to go even higher. For comparison, R with data science has 30 pages and I don't see how they could have fit more.
So, this PR removes the navigation bar on the left and replaces it with a navigation bar on top. The bar on the top has only one button: "TuringModels" which brings the user back to the homepage.

Great, will you merge it as v2.0? Should we add a badge pointing to the docs, next to the build badge?
We can probably also remove the old Travis related files, but that's a detail.
Thanks for all your work!

Great, will you merge it as v2.0? Should we add a badge pointing to the docs, next to the build badge?
We can probably also remove the old Travis related files, but that's a detail.
Thanks for all your work!

Great, will you merge it as v2.0? Should we add a badge pointing to the docs, next to the build badge?

Yes, that could be nice. I'll add it :+1:
I plan to merge #56 as v2.0. After this layout change, I'm almost there. There are still some scripts in scripts/10 and scripts/12 which I need to convert to make them consistent with the other scripts.

We can probably also remove the old Travis related files, but that's a detail.

Will do :+1:

Thanks for all your work!

Thanks!

Great, will you merge it as v2.0? Should we add a badge pointing to the docs, next to the build badge?

Yes, that could be nice. I'll add it :+1:
I plan to merge #56 as v2.0. After this layout change, I'm almost there. There are still some scripts in scripts/10 and scripts/12 which I need to convert to make them consistent with the other scripts.

We can probably also remove the old Travis related files, but that's a detail.

Will do :+1:

Thanks for all your work!

Thanks!

Once you're done I wonder if I should rework StatisticalRethinkingTuring to work off identical formulated models.

Once you're done I wonder if I should rework StatisticalRethinkingTuring to work off identical formulated models.

Once you're done I wonder if I should rework StatisticalRethinkingTuring to work off identical formulated models.

Once you're done I wonder if I should rework StatisticalRethinkingTuring to work off identical formulated models.

Yeah, that sounds laborious. I plan to be ready for v2 by the end of this week. After that, I hope to find time to add more new models and also plot the prior or something for each model. We are not bounded by space as much as McElreath was in the book. Do the models in https://github.com/StatisticalRethinkingJulia/StatisticalRethinkingTuring.jl overlap much with the models in this project?

Yeah, that sounds laborious. I plan to be ready for v2 by the end of this week. After that, I hope to find time to add more new models and also plot the prior or something for each model. We are not bounded by space as much as McElreath was in the book. Do the models in https://github.com/StatisticalRethinkingJulia/StatisticalRethinkingTuring.jl overlap much with the models in this project?

The models are the same models. SR primarily uses quap (early part of the book) and mcmc results to explain modeling approaches (based on the objectives for the model).

The models are the same models. SR primarily uses quap (early part of the book) and mcmc results to explain modeling approaches (based on the objectives for the model).


[Event Change Request] - CalculateRoutingLine.Codeunit.al - OnBeforeCalcRoutingLineBack

We like to request the following event change:
Object: CalculateRoutingLine.Codeunit.al
ToDo: add var to CalculateEndDate
Where is the event placed:
local procedure CalcRoutingLineBack(CalculateEndDate: Boolean)
var
    ...
begin
    IsHandled := false;
    OnBeforeCalcRoutingLineBack(ProdOrderRoutingLine, CalculateEndDate, IsHandled);
    if IsHandled then
        exit;

    CalendarEntry.SetRange(Date, 0D, ProdOrderRoutingLine."Ending Date");

    ProdEndingTime := ProdOrderRoutingLine."Ending Time";
    ProdEndingDate := ProdOrderRoutingLine."Ending Date";
    ...
end;

Event Code:
[IntegrationEvent(false, false)]
local procedure OnBeforeCalcRoutingLineBack(var ProdOrderRoutingLine: Record "Prod. Order Routing Line"; var CalculateEndDate: Boolean; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Reverse attribute

Change reverse attribute to be "vertrev" and "horzrev", because having a single "reverse" key is confusing

Coming in V1


Month and Week views date picker fix

Month and Week views date picker fix
Description of PR...
Changes made

selecting a date on the month view did not work
selecting a date on the week view did not work

PR Template Checklist

[x ] Fixes Bug
[ ] Feature solution
[ ] Other

Please mark which issue is solved

Close #

This would close issues https://github.com/DNNCommunity/DNN.Events/issues/200 and #194 I believe.

Nice catch!  Just 2 other bugs reported to go... and we can start looking at making improvements.
You deserve a badge here for the first PR in probably a year!  You can't imagine how thankful everyone is to see some activity here.  Everyone should be blasting this PR with a THANK YOU!!!  this is 100% volunteer effort you got to LOVE IT!!!    LONG LIVE DotNetNuke!!! :)

The current PR handles several unrelated issues in 1 PR.
Is it possible to split the PR into several distinct ones, each referencing a single issue? So that testing & verification * PR merging can be done on a granular issue-level?


Fix error case in Windows layer cleanup

ForceRemoveAll has special logic on Windows for cleaning up a Windows
snapshotter directory. The logic was missing proper handling for an
error case that can be returned in some cases.
This fixes the CI failure seen in #5326.
Signed-off-by: Kevin Parsons<EMAIL_ADDRESS>

@TBBle FYI in case you are interested

Oh weird, I thought I tested that case, and it silently succeeded for me. Perhaps this case is different on Windows 10 20H2 (where I tested it) vs RS5 on CI.
Either way, seems reasonable to me.

close/reopen to trigger CI

@containerd/committers Can someone take a look?


Retry on different servers when possible

Fixes #385

This change is

closing since this has been stale for a while and since we're going to implement this at the OkHttp level rather than at the Feign level.


Error when reading  document

Our worker created excel document with mistake. He accidentally put some value in last column(XFD1) . After that tried download this doc with help of class ZCL_EXCEL_READER_2007. It was cause of dump CONVT_NO_NUMBER. Next Row trigger exception in METHOD LOAD_WORKSHEET:
lv_index = lv_max_col_s.

Code review  show that variable lv_max_col_s was defined in next snip:
fill_struct_from_attributes(
 EXPORTING
     ip_element = lo_ixml_row_elem
 CHANGING
    cp_structure = ls_row ).
SPLIT ls_row-spans AT ':' INTO lv_min_col_s lv_max_col_s.

In order to this code work write ls_row-spans must have view - digit:digit, but in our case it have value - 1:1 16384:16384.

Please provide a sample file.

Attemption to download this simple file sample.xlsx propogate error.

Maybe anybody encounter this problem?

Issue reproduced by creating an Excel sheet with only 3 cells A1, KAU1 and XFD1 filled, the file xl\worksheets\sheet1.xml contains spans="1:1 7483:7483 16384:16384" as you can see here:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<worksheet xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main" ...>
    <dimension ref="A1:XFD1" />
    <sheetViews>
        <sheetView tabSelected="1" topLeftCell="XEJ1" workbookViewId="0">
            <selection activeCell="XFD1" sqref="XFD1" />
        </sheetView>
    </sheetViews>
    <sheetFormatPr defaultRowHeight="15" x14ac:dyDescent="0.25" />
    <sheetData>
        <row r="1" spans="1:1 7483:7483 16384:16384" x14ac:dyDescent="0.25">
            <c r="A1">
                <v>1</v>
            </c>
            <c r="KAU1">
                <v>1</v>
            </c>
            <c r="XFD1">
                <v>1</v>
            </c>
        </row>
    </sheetData>
    <pageMargins left="0.7" right="0.7" top="0.75" bottom="0.75" header="0.3" footer="0.3" />
    <pageSetup paperSize="9" orientation="portrait" r:id="rId1" />
</worksheet>

Workaround to be tested:

Replace these 2 declarations https://github.com/sapmentors/abap2xlsx/blob/3167c6a8f26ca21b353a8b342c2d9a62acfa3b15/src/zcl_excel_reader_2007.clas.abap#L2358-L2359
with        lv_max_col_s                TYPE c LENGTH 11,     "for use with SPANS element
        lv_min_col_s                TYPE c LENGTH 11,     "for use with SPANS element
        lt_multiple_spans           TYPE TABLE OF string,
        lv_dummy                    TYPE string,

And replace this code https://github.com/sapmentors/abap2xlsx/blob/3167c6a8f26ca21b353a8b342c2d9a62acfa3b15/src/zcl_excel_reader_2007.clas.abap#L2473-L2478
with    fill_struct_from_attributes( EXPORTING
                                   ip_element = lo_ixml_row_elem
                                 CHANGING
                                   cp_structure = ls_row ).
    SPLIT ls_row-spans AT ' ' INTO TABLE lt_multiple_spans.
    READ TABLE lt_multiple_spans INDEX 1 INTO lv_min_col_s.
    DESCRIBE TABLE lt_multiple_spans.
    READ TABLE lt_multiple_spans INDEX sy-tfill INTO lv_max_col_s.
    SPLIT lv_min_col_s AT ':' INTO lv_min_col_s lv_dummy.
    SPLIT lv_max_col_s AT ':' INTO lv_dummy lv_max_col_s.


upd(goverlay): 1.0 -> 1.1.1

I have canceled my branch.. it has canceled all my PR ...

Here the control file generated :
Package: goverlay
Version: 1.1.1-pacstall1
Architecture: amd64
Section: Pacstall
Priority: optional
Build-Depends: git, libglu1-mesa-dev, qt6-base-dev
Conflicts: goverlay-bin
Replace: goverlay-bin
Maintainer: Xdavius<EMAIL_ADDRESS>Description: A GUI to help manage Vulkan/OpenGL overlays
Installed-Size: 4193

Hi. Thank you for replying.
In fact, I have tested on my side. Uninstalling fpc-src uninstall goverlay. But I don't want this comportement... Because it's not an execution dependency, just a build one.
If you know the way to avoid this problem... (Not tested to declare empty depends, I don't know if it will do the trick...)
For your question, goverlay-bin is the binary provided by upstream. At this moment, it is still in qt5 version 1.0.
This one is qt6 and rebuilt from source. The distributions aren't totally compatible with it, making the use of qt6ct for exemple for the theme.
Originally, goverlay-bin was named goverlay, but was a bin. So I have updated the name of the package.
And goverlay is from source as it must be.
I will continue to maintain both, but -bin will be left on 1.0 version for a while.
Waiting for Noble to see If I can update without problems.

Hi. Thank you for replying.
In fact, I have tested on my side. Uninstalling fpc-src uninstall goverlay. But I don't want this comportement... Because it's not an execution dependency, just a build one.
If you know the way to avoid this problem... (Not tested to declare empty depends, I don't know if it will do the trick...)
For your question, goverlay-bin is the binary provided by upstream. At this moment, it is still in qt5 version 1.0.
This one is qt6 and rebuilt from source. The distributions aren't totally compatible with it, making the use of qt6ct for exemple for the theme.
Originally, goverlay-bin was named goverlay, but was a bin. So I have updated the name of the package.
And goverlay is from source as it must be.
I will continue to maintain both, but -bin will be left on 1.0 version for a while.
Waiting for Noble to see If I can update without problems.

@Elsie19 I think it's good now.

@oklopfer possible to merge ? or miss something ?

This needs to be updated to the 5.0.0 spec

This needs to be updated to the 5.0.0 spec

use goverlay-bin until I do the changes here. Have to test with v5.

There are merge conflicts now.


[$500] IOU - In online split bill, merchant "split bill with (participants)id" turned to "request"

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to https://staging.new.expensify.com/
Tap on a group chat
Tap plus icon---Split bill
Enter an amount
Tap show more and note "request" is shown under "merchant"
Tap split amount
Tap split bill created
Tap show more and note "request" is shown under "merchant"
Navigate to group chat
Turn off mobile data
Perform step 3-step 7
Tap show more and note "split bill with (participants) mail id " is shown under "merchant"section
Turn on mobile data
Note the merchant section

Expected Result:
In both offline and online, the merchant section in split bill detail page must show the same message.
Actual Result:
In offline, under group chat split bill detail page, the merchant section displays "split bill with (participants) mail id " and it is changed to "request" when user turns on mobile data.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/f110054a-fd8d-452f-b357-7a2624e40232
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0124dadd69db8eb9e9
Upwork Job ID:<PHONE_NUMBER>791814656
Last Price Increase: 2023-11-24

Could be related to https://github.com/Expensify/App/issues/31781


Making vue-color work with v-model.

Changing the event to 'input' will make the component work with v-model.

Adding yarn.lock

Docs:
https://vuejs.org/v2/guide/components.html#Form-Input-Components-using-Custom-Events
This way, when using the component, it's possible to only use v-model without @change-color="onChange".

I just ran into an issue where it doesn't update the parent anymore. This might not be complete yet. Pls don't merge.

This change broke my application that was written with @change-color.  The change is not a bad idea, but it is a breaking change, so according to SemVer, it should have been released along with an update to the major version number, not just a patch number.


fix: Update OrgInviteUsersForm.tsx

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description
Changed case in invite organisation form

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change.

Fixes #8896

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] New and existing unit tests pass locally with my changes

@Nikhil-Nandagopal hey can you review this?

@Nikhil-Nandagopal hey can you merge this please?

@Nikhil-Nandagopal please can you reopen this pr and merge it?


just some requests cuz idk where to put requests

a command to make people have the same commands as hosts like /hostpower @[username]
would be useful to play with my friend and for more people too probably
spawnable apparatus

a command to make people have the same commands as hosts like /hostpower @[username]
so do you mean like being able to say in genereal its not allowed to execute host commands, but for a specified person it is using that command you stated? I thought about adding something similiar

the spawnable apparatus i will have to look into, i guess it doesnt clarify as a scrap item so it could have similar issues to the gun part with the spawning stuff

ye basically that's what i mean

like you have hostpowers as host,and your friend is a nonhost,so you do /hostpower [@username] to make him able to use the same powers as you

i have implemented that in a first version, will have to test it tho.
If you want to test it you can download the ChatCommands.dll from the sourcecode and manually put it into the BepInEx/plugins folder

from here:
https://github.com/Toemmsen96/ChatCommands/blob/master/ChatCommands.dll

should work even if the nonhost doesnt have the most recent version

ight,i'll test it later with my friend tho

btw, would apparatus and beehive be possible ? or spawning circuit bees (so it also spawns a beehive w/the bees)

i will look into it but not right now, it may take a while since i suspect it will be quite a bit more complicated.
I do have some exams soon, and i need to study, so yeah i cant promise anything atm

ah its fine

oh yeah, and a small warning if you are testing, i think /enemies and /getscrap dont work as a nonhost right now, i will have to fix that. everything else should work as a nonhost i believe, but i guess there can always be a bug or something

Would also be great if we could /tp p=-36,-13,217 for a location

Would also be great if we could /tp p=-36,-13,217 for a location

Might add this together with a command for getting your location

added it in 1.1.8

Would also be great if we could /tp p=-36,-13,217 for a location

Never mind, i added it to the spawning functions, instead of the tp function 😅

I will probably update it so the tp function uses the same p= functionality for the position


bug: make export respect context

Several of the methods from cli-runtime's genericclioptions package
expect for the AddFlags() method to be called first. Calling AddFlags()
first should allow us to remove some options and rely on cli-runtime to
handle cluster/namespace/context/auth/etc for us.
Fixes #67

Running through the different configuration scenarios.
Defaults
$ ./crane export
INFO[0000] adding resource: configmaps to the list of GVRs to be extracted
INFO[0000] adding resource: serviceaccounts to the list of GVRs to be extracted
INFO[0000] adding resource: services to the list of GVRs to be extracted
INFO[0000] adding resource: secrets to the list of GVRs to be extracted
INFO[0000] adding resource: endpoints to the list of GVRs to be extracted
INFO[0003] adding resource: endpointslices to the list of GVRs to be extracted
W1222 16:37:53.098729 1795742 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
INFO[0003] Writing objects of resource: configmaps to the output directory
INFO[0003] Writing objects of resource: serviceaccounts to the output directory
INFO[0003] Writing objects of resource: services to the output directory
INFO[0003] Writing objects of resource: secrets to the output directory
INFO[0003] Writing objects of resource: endpoints to the output directory
INFO[0003] Writing objects of resource: endpointslices to the output directory

$ tree -a export
export
├── failures
│   └── default
└── resources
    └── default
        ├── ConfigMap_default_kube-root-ca.crt.yaml
        ├── Endpoints_default_kubernetes.yaml
        ├── EndpointSlice_default_kubernetes.yaml
        ├── Secret_default_default-token-xjsz4.yaml
        ├── ServiceAccount_default_default.yaml
        └── Service_default_kubernetes.yaml

4 directories, 6 files

Only command line
$ ./crane export --export-dir export2
INFO[0000] adding resource: serviceaccounts to the list of GVRs to be extracted
INFO[0000] adding resource: services to the list of GVRs to be extracted
INFO[0000] adding resource: configmaps to the list of GVRs to be extracted
INFO[0000] adding resource: endpoints to the list of GVRs to be extracted
INFO[0000] adding resource: secrets to the list of GVRs to be extracted
INFO[0003] adding resource: endpointslices to the list of GVRs to be extracted
W1222 16:41:43.571251 1799365 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
INFO[0003] Writing objects of resource: serviceaccounts to the output directory
INFO[0003] Writing objects of resource: services to the output directory
INFO[0003] Writing objects of resource: configmaps to the output directory
INFO[0003] Writing objects of resource: endpoints to the output directory
INFO[0003] Writing objects of resource: secrets to the output directory
INFO[0003] Writing objects of resource: endpointslices to the output directory

$ ./crane export --namespace foo --export-dir export2
W1222 16:47:22.352651 1804556 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

$ ./crane export --context bar --export-dir export2
Error: invalid configuration: context was not found for specified context: bar

$ tree -a export2
export2
├── failures
│   ├── default
│   └── foo
└── resources
    ├── default
    │   ├── ConfigMap_default_kube-root-ca.crt.yaml
    │   ├── Endpoints_default_kubernetes.yaml
    │   ├── EndpointSlice_default_kubernetes.yaml
    │   ├── Secret_default_default-token-xjsz4.yaml
    │   ├── ServiceAccount_default_default.yaml
    │   └── Service_default_kubernetes.yaml
    └── foo

6 directories, 6 files

Only flags-file
$ cat craneConfig.yaml
context: kind-src
namespace: guestbook
export-dir: export3

$ ./crane export --flags-file craneConfig.yaml
INFO[0000] Using config file: craneConfig.yaml
INFO[0000] adding resource: services to the list of GVRs to be extracted
INFO[0000] adding resource: configmaps to the list of GVRs to be extracted
INFO[0000] adding resource: pods to the list of GVRs to be extracted
INFO[0000] adding resource: secrets to the list of GVRs to be extracted
INFO[0000] adding resource: endpoints to the list of GVRs to be extracted
INFO[0000] adding resource: serviceaccounts to the list of GVRs to be extracted
INFO[0000] adding resource: deployments to the list of GVRs to be extracted
INFO[0001] adding resource: replicasets to the list of GVRs to be extracted
INFO[0003] adding resource: endpointslices to the list of GVRs to be extracted
W1222 16:52:51.372073 1810072 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
INFO[0003] Writing objects of resource: services to the output directory
INFO[0003] Writing objects of resource: configmaps to the output directory
INFO[0003] Writing objects of resource: pods to the output directory
INFO[0003] Writing objects of resource: secrets to the output directory
INFO[0003] Writing objects of resource: endpoints to the output directory
INFO[0003] Writing objects of resource: serviceaccounts to the output directory
INFO[0003] Writing objects of resource: deployments to the output directory
INFO[0003] Writing objects of resource: replicasets to the output directory
INFO[0003] Writing objects of resource: endpointslices to the output directory

$ tree -a export3
export3
├── failures
│   └── guestbook
└── resources
    └── guestbook
        ├── ConfigMap_guestbook_kube-root-ca.crt.yaml
        ├── Deployment_guestbook_frontend.yaml
        ├── Deployment_guestbook_redis-master.yaml
        ├── Deployment_guestbook_redis-slave.yaml
        ├── Endpoints_guestbook_frontend.yaml
        ├── Endpoints_guestbook_redis-master.yaml
        ├── Endpoints_guestbook_redis-slave.yaml
        ├── EndpointSlice_guestbook_frontend-jt6lp.yaml
        ├── EndpointSlice_guestbook_redis-master-4jddk.yaml
        ├── EndpointSlice_guestbook_redis-slave-7tqvp.yaml
        ├── Pod_guestbook_frontend-5fd859dcf6-gpzfw.yaml
        ├── Pod_guestbook_frontend-5fd859dcf6-knp9m.yaml
        ├── Pod_guestbook_frontend-5fd859dcf6-qn2rv.yaml
        ├── Pod_guestbook_redis-master-55d9747c6c-vgzg7.yaml
        ├── Pod_guestbook_redis-slave-5c6b4c5b47-ppcqs.yaml
        ├── Pod_guestbook_redis-slave-5c6b4c5b47-shchm.yaml
        ├── ReplicaSet_guestbook_frontend-5fd859dcf6.yaml
        ├── ReplicaSet_guestbook_redis-master-55d9747c6c.yaml
        ├── ReplicaSet_guestbook_redis-slave-5c6b4c5b47.yaml
        ├── Secret_guestbook_default-token-qrvsm.yaml
        ├── ServiceAccount_guestbook_default.yaml
        ├── Service_guestbook_frontend.yaml
        ├── Service_guestbook_redis-master.yaml
        └── Service_guestbook_redis-slave.yaml

4 directories, 24 files

Combination
$ kubectl config current-context
kind-dest

$ cat craneConfig.yaml
# context: kind-src
namespace: guestbook
export-dir: export3

$ ./crane export --flags-file craneConfig.yaml --export-dir export4
INFO[0000] Using config file: craneConfig.yaml
INFO[0000] adding resource: configmaps to the list of GVRs to be extracted
INFO[0000] adding resource: serviceaccounts to the list of GVRs to be extracted
INFO[0000] adding resource: secrets to the list of GVRs to be extracted
W1222 16:55:19.571931 1812602 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
INFO[0003] Writing objects of resource: configmaps to the output directory
INFO[0003] Writing objects of resource: serviceaccounts to the output directory
INFO[0003] Writing objects of resource: secrets to the output directory

$ ./crane export --flags-file craneConfig.yaml --export-dir export4 --namespace foo
INFO[0000] Using config file: craneConfig.yaml
W1222 16:55:42.541886 1812953 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

$ tree -a export4
export4
├── failures
│   ├── foo
│   └── guestbook
└── resources
    ├── foo
    └── guestbook
        ├── ConfigMap_guestbook_kube-root-ca.crt.yaml
        ├── Secret_guestbook_default-token-d5qpj.yaml
        └── ServiceAccount_guestbook_default.yaml

6 directories, 3 files

This matches my expectations for behavior.


Typos

Why:
Closes [no open issue]
What's being changed:

typo line 93
typo line 110

Check off the following:

[x] For workflow changes, I have verified the Actions workflows function as expected.
[x] For content changes, I have reviewed the style guide.

Duplicate of #35


chore(deps): update common-dev-assets digest to 3e70ea2

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d8a541e -> 3e70ea2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Wrong file name when downloading file, always getting 'document' as file name

I'm uploading a file my-filename.pdf with
const { fileMetadata, error: uploadError } = await storage.upload({
  file,
  name: file.name,
  bucketId: `myBucket`,
})

And then I'm retrieving the file as follow:
const getFileUrl = async (): Promise<void> => {
  const { presignedUrl, error } = await storage.getPresignedUrl({
    fileId: data?.profile?.file?.id,
  })

  if (!error) {
    window.open(presignedUrl?.url, '_blank')?.focus()
  }
}

When opening the file in a new window and downloading the file, the name of the file is always document.fileExtension. I'd expect the file name to be used instead of document

Which version of hasura-storage are you running?

I have "@nhost/nextjs": "^1.0.11" and "@nhost/react": "^0.5.1",

@dbarrosop Is this the info you where asking for?

no, not exactly, I was wondering about the server itself. If you are running it in your dev machine you can probably check the container image with docker ps. If you are consuming it via nhost's cloud you can reach out to me via discord and I can check it for you.

So I'm using
nhost/hasura-storage:sha-623f285 and minio/minio:RELEASE.2021-09-24T00-24-24Z

Ok, thanks. Are you using the nhost cli? If yes, we are releasing a new version of the cli that will update hasura-storage later today so I will ask you to test after that as I couldn't reproduce the issue with that version. If you are running it somehow else let me know and I can provide you with instructions to update hasura-storage.

Hi @dbarrosop,
After upgrading to V.06.6 I can confirm that the problem is solved.
Thank you

Hi @dbarrosop,
I'd like to know if this has been pushed to production. In local I have Nhost CLI version v0.6.8 and I'm running I have nhost/hasura-storage:0.1.5 and minio/minio:RELEASE.2021-09-24T00-24-24Z.
Even though in local I now have the correct file name, in production I'm still getting document as file name.
Thanks.

It's been done for most applications but we held off for some "old" users of hasura-storage. If you ping me on discord or let me know your subdomain I can make sure your application is up to date.

We just decided to upgrade the remaining apps so yours should be too. Let me know if it is working now. Thanks!


data file

where is file /data/?

batchloader takes path to .txt file with data as argument. this file should contain sentences row by row split by new line symbol.
something like
This new development in Harry's character may be a disappointment to those readers who enjoyed his old vindictive ways, but it also reinforces the position of pro-Potter people who do not see beneath the surface appearance of the characters and plots.
A nondisclosure clause in the final settlement (the band is back on Elektra) prevents Ulrich, an irrepressible motormouth, from providing any juicy contractual details.
When you're 18 or 19 years old, you have that gang mentality in your band.
Now you have Black Sabbath and Kiss tribute albums.
I was the one who sat down and copied them.
I grew up in as open an upbringing as you can imagine.
I'd wake up at 7:30, go downstairs, and the front door would be open - 600 beers in the kitchen and living room and nobody in the house.
Like the death penalty.
The human spark gets put to the wayside.
Perception has no meaning.
The thoughts need not bear any obvious relationship to the idea, but they should not be in opposition to it.

I have't added data folder in order to not upload huge files on github and not to lock model on single dataset


Is it possible to cache admin access token  ?

Hello
As far as I see both original repo and this fork are creating access token each time Keycloak API is invoked.
Can you please explain if it is possible to cache token somehow and refresh when token is expired to reduce Keycloak API load.

@ievgenii-shepeliuk Why did you close this? This important functionality is not implemented. Can we please reopen this?

@goldsam if you need this functionality the best way to achieve it with the project in it's current state is to use the Func<string> getToken constructor when initializing the KeycloakClient and have that function cache/refresh the token.
Unfortunately I am quite busy with other projects right now, but if you are able to write a function that can handle the token refreshes then I'd be happy to integrate it into this project.


Remove non-frameworks

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

I think it's slightly misleading to include non-frameworks and example repos. The non-frameworks cover a very different space of frontend web dev

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Tools also seems misleading.
Maybe just frontend JavaScript?
So generic it can't be wrong?

Maybe just frontend JavaScript?
So generic it can't be wrong?

I think that's a great idea! Could you update this PR to make those changes? Once updated I'll approve and get it merged in ASAP!

NullVoxPopuli:patch-1

https://github.com/github/explore

Hi @NullVoxPopuli! This PR has been stale for a while and we can't ship it as is. I'm going to close if for now, but if you're interested in getting this change in, please re-open it and see my teammate @kenyonj's suggestion above.
Thank you! We appreciate you contributing to Explore ✨


Windows Key + V (Clipboard History) doesn't work when CTRL and ALT keys are flipped

Microsoft PowerToys version
0.57.2
Running as admin

[ ] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce

Use PowerToys Keyboard Manager to remap CTRL and ALT
Copy a text into clipboard
Use Windows Key + V to paste item from clipboard
Select item from Clipboard

✔ Expected Behavior
Clipboard Item to be pasted
❌ Actual Behavior
After step 4 clipboard item will not be pasted
Other Software
No response

/dup #14556


Database error when drilling to detail on a bar chart with an X-axis column of type other than datetime

Pretty specific bug I found when testing 2.1.0 (rc2 is the first time I'm trying out DRILL_TO_DETAIL).

Version 2.1.0rc2 (edit: persists in 4.0.0rc1)
GENERIC_CHART_AXES and DRILL_TO_DETAIL flags enabled
Bar chart v2
X-axis variable is of type varchar or date that has been set to temporal in the Edit Dataset UI
Trying to drill to detail by the x-axis variable or "All" results in error message Arithmetic overflow error converting expression to data type datetime

My backend is SQL Server, thus that specific error message.
My guess is that there's an operation to cast an X-axis variable to datetime when charting if that variable is marked as temporal, but this breaks at the drilling?
My workaround: I changed the variable in the database to be datetime and then I could drill successfully.  But that's a little misleading since my variable does not have that resolution, this data field is only precise to the date level.

@sfirke it looks like drilling isn't enabled on that dash/instance. Is anyone able to say if this is still an issue in 3.x now that GENERIC_CHART_AXES is on by default there, or in 4.0 now that the FF is gone?

@rusackas oops, the public user can't drill on that chart -- but I can.  Confirming that this persists in 4.0.0rc1:

This one's hitting my stale range... not sure if there are any takers on picking this one up :/


Added additional regex pattern !devops

Added additional regex pattern of !devops so that one needs to type less.

Looks good. Thanks!


Remove glob package

We don't use a lot of the features of glob, so let's remove it in favor of a leaner approach using regex.
It's failing on windows and I have no idea why and don't own a windows machine 🤦🏼♂
(Ignore some of the commits in here, I forgot to create the new branch before I started working)

Ran the benchmark against 198K files yesterday, quite great results. Not that the recursive readdir function does not have all features glob has, but our use case is very simple: read pages/**/* and exclude anything that doesn't match pageExtensions (default is jsx and js).


Training model pipeline failing with KeyError

The way the API and pipeline are designed right now:

A user inserts their dataset rows and when saved to the database the training model pipeline is triggered.
If everything is successful the trained model is saved in the user's filesystem.

Here there's a possibility that the pipeline will fail with a KeyError because the given target when creating a model doesn't exist in the training dataset (a user's fault). The thing is though that a trained model isn't produced and the dataset rows are saved in the database. The user can't delete them from the SDK or API and if they insert new and correct ones, it's going to cause a chaos with all the metrics calculations due to columns mismatches.
Suggested solutions:

Save the dataset rows in the database, train the model and if it fails (Raising a KeyError exception), delete the saved dataset rows from the database so the user can start fresh. OR
Before the dataset rows are saved in the database, check if the target exists in the dataset provided by the user.

Checking for the appropriate column before the model training solves the KeyError, but in case of small training datasets (probably mistakenly inserted by the user) we can get a few other errors (like ValueError) that prevent the completion of the training and leave us with a similar problem to what we tackled in this issue.

@sinnec at the above example there is an one-row training dataset. I think that in such cases we should also capture it before even starting to save this data and raise an error. An one-row dataset is not considered a training dataset.
Maybe a solution could be to check the length of the given dataset and also to check if the given target column has more than one unique values.

@stavrostheocharis  Training datasets above what length are acceptable, since the second ValueError (The one with ROC AUC) is occuring even for small datasets of 5 rows with different targets. Should it be something like len(training_dataset) >= 100 or something?

I think that more than 2 in could be ok. Maybe at your test dataset you have in all y values the same value (this would be a problem)


3489 add numbered ia

Issue #: /bcgov/entity#3489
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Ah dang... you have conflicts to resolve before we can merge.


K8SPXC-851: handle replication password change

Update password for replication channel if replication password changed

Test name
Status

big-data
passed

scaling
passed

haproxy
passed

storage
passed

scheduled-backup
passed

upgrade-haproxy
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

self-healing-advanced
passed

affinity
passed

smart-update
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/269422bc3c4d4d0e643afb79e074ed5643c99a15
image: perconalab/percona-xtradb-cluster-operator:PR-981-269422bc

Test name
Status

scheduled-backup
passed

scaling
passed

upgrade-haproxy
passed

haproxy
passed

big-data
passed

recreate
passed

storage
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

self-healing-chaos
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

self-healing-advanced
passed

smart-update
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
failed

operator-self-healing
passed

operator-self-healing-chaos
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/7d97b5300e3b4fc60c5e353d4b7a7404cc396fd6
image: perconalab/percona-xtradb-cluster-operator:PR-981-7d97b530

Test name
Status

upgrade-haproxy
passed

scaling
passed

scheduled-backup
passed

storage
passed

big-data
passed

recreate
passed

haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

self-healing-chaos
passed

demand-backup
passed

limits
passed

self-healing-advanced
passed

smart-update
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

upgrade-consistency
passed

operator-self-healing-chaos
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/39ffe24406084ed213e0936b5b80d5b47696b85f
image: perconalab/percona-xtradb-cluster-operator:PR-981-39ffe244

Test name
Status

storage
passed

scheduled-backup
passed

big-data
passed

haproxy
passed

recreate
passed

scaling
passed

upgrade-haproxy
passed

self-healing
passed

scaling-proxysql
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

self-healing-chaos
passed

demand-backup
passed

self-healing-advanced
passed

smart-update
passed

limits
passed

monitoring-2-0
passed

self-healing-advanced-chaos
passed

affinity
passed

one-pod
passed

pitr
passed

auto-tuning
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

operator-self-healing-chaos
passed

upgrade-consistency
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/043982e255d2b7d3feeca179f934f85909875ef2
image: perconalab/percona-xtradb-cluster-operator:PR-981-043982e2

Test name
Status

upgrade-haproxy
passed

big-data
passed

scheduled-backup
failed

scaling
passed

storage
passed

haproxy
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

self-healing-chaos
passed

monitoring-2-0
passed

demand-backup
passed

self-healing-advanced
passed

smart-update
passed

affinity
passed

one-pod
passed

auto-tuning
passed

self-healing-advanced-chaos
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

operator-self-healing
passed

upgrade-consistency
passed

operator-self-healing-chaos
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/b5e3af797730379afd1bfb0bfdac83daf44b3470
image: perconalab/percona-xtradb-cluster-operator:PR-981-b5e3af79

Test name
Status

scaling
passed

upgrade-haproxy
passed

scaling-proxysql
passed

security-context
passed

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

recreate
passed

haproxy
passed

big-data
passed

restore-to-encrypted-cluster
passed

init-deploy
passed

demand-backup
passed

limits
passed

pitr
passed

monitoring-2-0
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/b5e3af797730379afd1bfb0bfdac83daf44b3470
image: perconalab/percona-xtradb-cluster-operator:PR-981-b5e3af79

Test name
Status

storage
passed

upgrade-haproxy
passed

haproxy
passed

recreate
passed

scaling
passed

scheduled-backup
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

self-healing-chaos
passed

limits
passed

monitoring-2-0
passed

demand-backup
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

smart-update
passed

self-healing-advanced-chaos
passed

auto-tuning
passed

pitr
passed

operator-self-healing
passed

proxysql-sidecar-res-limits
passed

users
passed

operator-self-healing-chaos
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/981/commits/7dfeb4d285400eaa5849049e988eff904bdab8ae
image: perconalab/percona-xtradb-cluster-operator:PR-981-7dfeb4d2


Aomp post 13-0.2 reported to crash on out of memory

Reported out of band by Devito a week ago, creating a ticket to help avoid it getting lost. Quoting from the slack channel,
Devito observed spurious segfaults while running a sequence of tests. This appears to be due to exhausting host memory, and since it's not swapping out, I'd bet on pinned memory buffers allocated by the openmp runtime for the comms
DEVITO_PLATFORM=amdgpuX DEVITO_ARCH=aomp DEVITO_LANGUAGE=openmp pytest test_gpu_common.py::TestStreaming::test_streaming_complete
shows a significant increase in host memory consumption (~1 GB after each Operator run), despite being a tiny test
memory allocated and freed as expected
#pragma omp target enter data map(to: u[0:u_vec->size[0]][0:u_vec->size[1]][0:u_vec->size[2]])
#pragma omp target enter data map(to: va[0:va_vec->size[0]][0:va_vec->size[1]][0:va_vec->size[2]])
#pragma omp target enter data map(to: vb[0:vb_vec->size[0]][0:vb_vec->size[1]][0:vb_vec->size[2]])
and (deallocations):
#pragma omp target update from(u[0:u_vec->size[0]][0:u_vec->size[1]][0:u_vec->size[2]])
#pragma omp target exit data map(release: u[0:u_vec->size[0]][0:u_vec->size[1]][0:u_vec->size[2]]) if(devicerm)
#pragma omp target exit data map(delete: va[0:va_vec->size[0]][0:va_vec->size[1]][0:va_vec->size[2]]) if(devicerm && (va_vec->size[0] != 0) && (va_vec->size[1] != 0) && (va_vec->size[2] != 0))
#pragma omp target exit data map(delete: vb[0:vb_vec->size[0]][0:vb_vec->size[1]][0:vb_vec->size[2]]) if(devicerm && (vb_vec->size[0] != 0) && (vb_vec->size[1] != 0) && (vb_vec->size[2] != 0))
htop confirmed crash upon memory exhaustion
13.0-3 leaks too (!)
so I'm reverting to 13.0-2 for the time being, I will wait for news...
I think the easiest thing for you to do is to run pytest test_adjoint.py test_gpu_common.py with AOMP offloading enabled and see for yourself. You'll see a massive and steady increase in unswappable, host memory consumption

@estewart08 this would be a good thing to not be broken on the 14 proposal

Initial testing shows passing for me with 13.0-2, 13.0-6 and 14.0-0 with 64 GB system memory and a gfx906.
devito sha: 5848cf3d0d0854b158cbd3245df30ef52ad24146

closing this old issue..


OpenTimelineIO AAF Adapter Removal Tasks

The following tasks need to be resolved before AAF Adapter can safely be removed from OpenTimelineIO.
Please let me know if there are any other blocking issues to add to this task list.
The pull request to remove the AAF Adapter from OTIO is here
https://github.com/AcademySoftwareFoundation/OpenTimelineIO/pull/1348
Blocking Tasks

[x] Fix test coverage lost in OTIO due to the AAF adapter https://github.com/AcademySoftwareFoundation/OpenTimelineIO/commit/913f540538b33ba98a40cab614312c07d08a8e20
[x] Enable EasyCLA enforcement if possible
[x] Enable Developer Certificate of Origin (DCO)  enforcement
[x] Enable pull request reviews settings in repository
[x] Enable CodeCov CI and pull request reports
[x] Enable Dependabot
[ ] Create / Verify PyPi package publishing works
[ ] Create PyPi package alias for OTIO https://github.com/AcademySoftwareFoundation/OpenTimelineIO/issues/1386
[ ] Linking docs to OTIO strategy and publishing
[x] Add Code of Conduct and Contributing docs
[x] Fix CI pip install OTIO URL
[x] Fix Badge path in Readme
[x] Add issue and pull request templates

Possible Blocking Tasks

[ ] Migrate OTIO AAF Adapter Issues or link
[ ] Migrate OTIO AAF Adapter Pull Requests?
[ ] What OTIO version do we test against? multiple?
[ ] Any additional docs need to move/remove from OTIO?
[x] Improve front page README

Regarding CLA and DCO, none of the repositories in the OpenTimelineIO organization have them enabled. I personally think it's fine, but obviously I'm not a member of the TSC so that's just my personal opinion.
CodeCov and Dependabot are really easy to enable. See https://docs.codecov.com/docs/github-2-getting-a-codecov-account-and-uploading-coverage and https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates (I think you might have to actually enable Dependabot in the repo settings).
I can help with some of these and the packaging/build side of things too.

@jminor said he was going to look into the CLA stuff.
Thanks @JeanChristopheMorinPerso , I have DCO and CodeCov working in my fork.
The annoying thing with CodeCov at the moment is pytest is running against a installed wheel and CodeCov doesn't like the file paths if you do that. Trying to think of the best approach to deal with this. pip install -e . works fine, but I like the idea of running the test against the wheels like you helped me do in my repos. pytest-cov doesn't seem have many options help do that.

Maybe https://docs.codecov.com/docs/fixing-paths?

That looks like it might work, I'll give it a try!

I think this can be closed, no? @markreidvfx


Remove vendor

This removes the vendor directory and only depends on mod.go to pull
down the dependencies.
I'm not 100% what a combined go modules and vendor dir does (maybe do
you? If so just close this PR).

go.mod + vendor just makes the build compatible with non-module-aware versions of Go, go mod vendor builds vendor/ based on the contents of modules.
Now that modules have been around for a while, I think it's fine to delete the vendor/ dir.


[Devops] Fix the default configuration of iotagent-lwm2m ports

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Firmware update does not run with these default ports.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

in file /ansible-dojot/roles/iotagent-lwm2m/defaults/main.yaml

in file /ansible-dojot/inventories/example_local/group_vars/all/dojot.yaml

Note:

If the file_server_http_port variable is set to 30008:

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683
2021-08-24 15:10:54,741 INFO FirmwareUpdateObject - This device suppots the firmware update protocol: COAP
2021-08-24 15:10:54,765 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (75.0,-44.0).
2021-08-24 15:10:54,765 INFO LeshanClient - Starting Leshan client ...
2021-08-24 15:10:54,803 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:35754
2021-08-24 15:10:54,804 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-08-24 15:10:54,804 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-08-24 15:10:54,845 INFO RegistrationEngine - Registered with location '/rd/nKRdHtbZtR'.
2021-08-24 15:11:26,030 INFO FirmwareUpdateObject - Write on Device Resource /5/0/1 value LwM2mSingleResource [id=1, value=coap://<IP_ADDRESS>:5693/admin-49a7c794-2aca-47de-8259-0de0d7f50c76.hex, type=STRING]

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683 -protocols http
2021-08-24 15:08:46,423 INFO FirmwareUpdateObject - This device suppots the  firmware update protocol: HTTP
2021-08-24 15:08:46,448 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (-89.0,75.0).
2021-08-24 15:08:46,448 INFO LeshanClient - Starting Leshan client ...
2021-08-24 15:08:46,485 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:49547
2021-08-24 15:08:46,486 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-08-24 15:08:46,486 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-08-24 15:08:46,663 INFO RegistrationEngine - Registered with location '/rd/JbVYhBx0bG'.
2021-08-24 15:08:59,359 INFO FirmwareUpdateObject - Write on Device Resource /5/0/1 value LwM2mSingleResource [id=1, value=http://<IP_ADDRESS>:30008/admin-49a7c794-2aca-47de-8259-0de0d7f50c76.hex, type=STRING]

If the file_server_http_port variable is set to 30006:

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683
2021-08-24 15:01:18,088 INFO FirmwareUpdateObject - This device suppots the firmware update protocol: COAP
2021-08-24 15:01:18,110 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (-69.0,-108.0).
2021-08-24 15:01:18,111 INFO LeshanClient - Starting Leshan client ...
2021-08-24 15:01:18,152 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:39891
2021-08-24 15:01:18,153 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-08-24 15:01:18,153 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-08-24 15:01:18,196 INFO RegistrationEngine - Registered with location '/rd/Durfxj0pZX'.
2021-08-24 15:01:25,480 INFO FirmwareUpdateObject - Write on Device Resource /5/0/1 value LwM2mSingleResource [id=1, value=coap://<IP_ADDRESS>:5693/admin-2a00c450-6231-4f82-bd67-f90ab89ded23.hex, type=STRING]

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683 -protocols http
2021-08-24 15:03:15,918 INFO FirmwareUpdateObject - This device suppots the  firmware update protocol: HTTP
2021-08-24 15:03:15,942 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (-66.0,-105.0).
2021-08-24 15:03:15,942 INFO LeshanClient - Starting Leshan client ...
2021-08-24 15:03:15,981 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:51468
2021-08-24 15:03:15,982 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-08-24 15:03:15,982 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-08-24 15:03:16,033 INFO RegistrationEngine - Registered with location '/rd/2pD5RP6Q4V'.
2021-08-24 15:03:41,716 INFO FirmwareUpdateObject - Write on Device Resource /5/0/1 value LwM2mSingleResource [id=1, value=http://<IP_ADDRESS>:30006/admin-49a7c794-2aca-47de-8259-0de0d7f50c76.hex, type=STRING]

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Version: 0.7.0-rc.3
Environment: kubernetes
Operating system: Ubuntu 18.04

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

This issue will be tested in the next baseline.

Test OK

protocol COAP

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683

2021-12-14 09:32:03,383 INFO FirmwareUpdateObject - This device suppots the firmware update protocol: COAP
2021-12-14 09:32:03,414 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (1.0,-145.0).
2021-12-14 09:32:03,415 INFO LeshanClient - Starting Leshan client ...
2021-12-14 09:32:03,464 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:36337
2021-12-14 09:32:03,464 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-12-14 09:32:03,465 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:32:03,568 INFO RegistrationEngine - Registered with location '/rd/c1xpT8wAIv'.
2021-12-14 09:32:03,569 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...
2021-12-14 09:32:04,266 INFO MyDevice - Read on Device Resource 3
2021-12-14 09:32:04,515 INFO FirmwareUpdateObject - Read on Device Resource /5/0/8
2021-12-14 09:32:04,516 INFO FirmwareUpdateObject - Device Resource /5/0/8 value: {0=0}
2021-12-14 09:32:04,594 INFO FirmwareUpdateObject - Read on Device Resource /5/0/3
2021-12-14 09:32:04,594 INFO FirmwareUpdateObject - Device Resource /5/0/3 value: 0
2021-12-14 09:32:04,620 INFO FirmwareUpdateObject - Read on Device Resource /5/0/5
2021-12-14 09:32:04,620 INFO FirmwareUpdateObject - Device Resource /5/0/5 value: 0
2021-12-14 09:32:30,571 INFO RegistrationEngine - Trying to update registration to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:32:30,585 INFO RegistrationEngine - Registration update succeed.
2021-12-14 09:32:30,585 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...
2021-12-14 09:32:57,587 INFO RegistrationEngine - Trying to update registration to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:32:57,600 INFO RegistrationEngine - Registration update succeed.
2021-12-14 09:32:57,601 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...

protocol HTTP

java -jar target/leshan-client-demo-1.0.0-M10-jar-with-dependencies.jar -n unsecure-client-endpoint-0 -u kei.dojot.com.br:5683 -protocols http
2021-12-14 09:36:30,428 INFO FirmwareUpdateObject - This device suppots the  firmware update protocol: HTTP
2021-12-14 09:36:30,452 INFO LeshanClientDemo - Press 'w','a','s','d' to change reported Location (13.0,102.0).
2021-12-14 09:36:30,452 INFO LeshanClient - Starting Leshan client ...
2021-12-14 09:36:30,498 INFO CaliforniumEndpointsManager - New endpoint created for server coap://<IP_ADDRESS>:5683 at coap://<IP_ADDRESS>:60812
2021-12-14 09:36:30,499 INFO LeshanClient - Leshan client[endpoint:unsecure-client-endpoint-0] started.
2021-12-14 09:36:30,500 INFO RegistrationEngine - Trying to register to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:36:30,581 INFO RegistrationEngine - Registered with location '/rd/nPX9zX9Vs8'.
2021-12-14 09:36:30,581 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...
2021-12-14 09:36:30,725 INFO MyDevice - Read on Device Resource 3
2021-12-14 09:36:30,748 INFO FirmwareUpdateObject - Read on Device Resource /5/0/8
2021-12-14 09:36:30,749 INFO FirmwareUpdateObject - Device Resource /5/0/8 value: {0=2}
2021-12-14 09:36:30,761 INFO FirmwareUpdateObject - Read on Device Resource /5/0/3
2021-12-14 09:36:30,762 INFO FirmwareUpdateObject - Device Resource /5/0/3 value: 0
2021-12-14 09:36:30,779 INFO FirmwareUpdateObject - Read on Device Resource /5/0/5
2021-12-14 09:36:30,779 INFO FirmwareUpdateObject - Device Resource /5/0/5 value: 0
2021-12-14 09:36:57,582 INFO RegistrationEngine - Trying to update registration to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:36:57,597 INFO RegistrationEngine - Registration update succeed.
2021-12-14 09:36:57,597 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...
2021-12-14 09:37:24,599 INFO RegistrationEngine - Trying to update registration to coap://<IP_ADDRESS>:5683 ...
2021-12-14 09:37:24,615 INFO RegistrationEngine - Registration update succeed.
2021-12-14 09:37:24,616 INFO RegistrationEngine - Next registration update to coap://<IP_ADDRESS>:5683 in 27s...


Add an application for plain multi-message signatures

At the moment we define MapMessageToScalarAsHash without really linking it to anything, suggesting it as a good default for encoding messages. Instead, I suggest that we explicitly define a 'plain multi-message signature' application, requiring that all messages are UTF-8 strings, and using this encoding rule for each. It could have a simple header value identifying the application, for instance BbsUtf8TextSignature2023 (the name needs work).
Implementations could also choose to support a simple API for this signature application, something like: PlainMultiSign(SK, messages: [String]) and PlainMultiVerify(Sig, PK, messages).

Not opposed to this, just to make sure i get it, you mean defining an API that will use the core operations?? To make it more explicit how MapMessageToScalarAsHash is to be used?? So something like what bls-sigs or h2c does?

Closing as completed through #282


Missing instruction on how to contribute

I would love to contribute data for the following devices. Is it possible to come up with a guide on how to collect the needed data?

Xiaomi Mijia Temperature and Humidity sensor (the round one without air pressure)
Xiaomi Mijia Button (round)
Xiaomi Mijia Motion Detection

Best I can do atm is say use the existing Aqara ones as a guide. https://github.com/dmulcahey/zha-device-handlers/blob/009409765e375797aa75a1e7301ff386413961ae/zhaquirks/xiaomi/aqara_body_sensor.py#L100 Those comments are directly from HA when you pair a device. Grab those lines and use the rest as a guide. I’ll try to create some docs soon...