Container exits because su-exec/gosu is missing

I'm getting the following log output with the latest-alpine and 6.1-alpine image:
[2021-06-27 21:24:56,924] <docker-entrypoint> INFO - Running recursive 'chown' on Docker overlay2 storage is **really** slow. This may take a bit.
[2021-06-27 21:24:56,989] <docker-entrypoint> ERROR - su-exec/gosu NOT FOUND. Run state is invalid. Exiting.

The ubuntu images are working
OS/distribution version (command for your OS may differ):
Distributor ID: Ubuntu
Description:    Ubuntu 19.10
Release:        19.10
Codename:       eoan

Docker version:
Docker version 19.03.13, build cd8016b6bc

Labels from container:

com.docker.compose.config-hash
c2561f16611bec0ec28bce26feb14069b0036b17fb9d9e7d584356a053956cc9

com.docker.compose.container-number
1

com.docker.compose.oneoff
False

com.docker.compose.project
unifi2

com.docker.compose.project.config_files
docker-compose.yml

com.docker.compose.project.working_dir
/home/jacob/docker/unifi2

com.docker.compose.service
app

com.docker.compose.version
1.25.5

org.opencontainers.image.created
2021-06-17T22:04:42.589Z

org.opencontainers.image.description
UniFi Controller

org.opencontainers.image.licenses
Apache-2.0

org.opencontainers.image.revision
0c477380b006eef531fb91f49aab06d6fe903cf0

org.opencontainers.image.source
https://github.com/goofball222/unifi

org.opencontainers.image.title
UniFi Controller

org.opencontainers.image.url
https://github.com/goofball222/unifi

org.opencontainers.image.vendor
The Goofball -<EMAIL_ADDRESS>

org.opencontainers.image.version
6.1.71-Alpine

I just tested on Ubuntu 20.04.2 with all current updates, running the latest Docker version 20.10.7, build f0df350, and I'm unable to reproduce this with the latest-alpine, 6.1-alpine, or 6.3-alpine-beta images.
I went ahead and re-ran the GH build actions for 5.14, 6.0, 6.1, and the 6.2 images just in case there was a something off with an Alpine package during the 2021-06-17 build that has been fixed. Please grab the latest build of the image and try again. Beyond that all I can recommend is updating your Docker host environment to the latest LTS/stable versions of Ubuntu and Docker.

Closing, no response. Assume fixed/non-issue now.

This is still an issue with 6.4-alpine

I was unable to reproduce it with 6.4-alpine, when I tried. I upgraded from Ubuntu 18.04 to 20.04 in the meantime though, so maybe that's the underlying cause here?


Google no longer sending refresh_token?

I'm getting 500 errors trying to authenticate from Google+ and when I look into the code, I see we're getting a KeyError in oauth2.py at:
if response.status == 200:
value = json.loads(data)
access_token = value['access_token']
-->        refresh_token = value['refresh_token']
When I inspect 'value', there's no 'refresh_token' in the response, or in the 'data' that generates 'value'.

Looks like google changed the way they do things so now the refresh token only comes if you request offline access and then only the first time. So i changed the code to not rely on having the refresh token, since most of our apps probably won't want that anyways.


Fix systemd service unit for docker >= 17.03

Starting with docker 17.03, docker daemon has to be run using dockerd binary instead of docker daemon.
This PR should support all versions.

ci check this

ci check this

ci check this

Hi. I don't know how to re-run pipelines.
Failures seems completely unrelated to my pull request.
Can I do something to help ?

@max-k re-kicking CI manually, sorry for the delay.

Hi, CI tests passed but they are still marked as failed.

Can you add this line in PR description or somewhere .
docker daemon is not supported on Linux. Please run dockerd directly
when i searched for this error i didn't get any results related to kubespray , so i had to do the fix .
now when i tried to create the PR i saw this , if i had saw this earlier it would have saved me some amount of time .

Can this merge request be merged soon ?

waiting on this as well

@mattymo @rsmitty do you know when this will be merged ?


TopNavigation fixed to top

💬 Question
For theming support, I presume we should be using TopNavigation instead of React Navigation StackNavigator Header.

Is it possible to fix the position of TopNavigation to the top and not allow it to be scrolled away?

Or if 1 cannot be done, is it possible to use StackNavigator header but let it use UI Kitten theme colors instead?

UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
5.0.0

I presume we should be using TopNavigation instead of React Navigation StackNavigator Header.

Use screenOptions to disable native headers.
<Stack.Navigator screenOptions={{ headerShown: false }} />
Then you may render TopNaviation where needed.

Is it possible to fix the position of TopNavigation to the top and not allow it to be scrolled away?

It will be fixed until it's rendered in scrollable container.

Sorry for the silly question. Placed the TopNavigation inside a KeyboardAvoiding ScrollView.
This is perfect, thanks!


When submitting test, got error with empty function

NVIM v0.3.8
reproduce procedure:

open question 1, two sum question.
submitting with blank function
got error below.

or

open question 1, two sum question.
submitting with return [0,1]
got error below.

But it shows no error with the right code.
The error is:
Error detected while processing function <SNR>120_CheckRunCodeTask[19]..<SNR>120_ShowRunResultInPreview[15]..<SNR>120_FormatResult[32]..<SNR>120_FormatSection:

line    4:
E714: List required

Hi,
I ran the procedure on my computer but didn't reproduce this error. I tried both in C++ and Python and found that they returned a list of strings.
Could you provide more information, such as the code that you used?

The Python code that I used for two sum:
class Solution(object):
    def twoSum(self, nums, target):
       print('1,2,3')

And I got:
# Two Sum

## State
  - Finished

## Runtime
  - 32 ms

## Standard Output
    1,2,3

### Input
    [2,7,11,15]
    9

### Actual Answer
    []

### Expected Answer
    [0,1]

Hi, @ianding1
On my side, I used javascript to submit to code.
var twoSum = function(nums, target) {
  return [0, 1];
};

The result output
{'passed': 4, 'runtime_percentile': v:null, 'answer': [], 'title': 'Two Sum', 'state': 'Wrong Answer', 'testcase': ['[3,2,4]', '6'], 'runtime': 'N/A', 'stdout': '[0,1]', 'total': 29, 'expected_answer': []
, 'error': []}

The stdout is a string, so if I call this:
    call extend(output, s:FormatSection('Standard Output', result['stdout'], 2))

It will show the error by @crokobit mentioned.
It seems because my return value is an array.

Please try updating to the latest version.
Related commit: b5c55f41299e511b0e4076b03215a0

Fixed. Thank you

Nice work @motephyr @ianding1  :) That's the opensource spirit. 🍻


Update upload-artifact GHA to v4

Issue #, if available: n/a
Description of changes:
Version 1 and 2 of the upload-artifact, and download-artifact GHAs have been deprecated. This PR updates the actions used for ion-test-driver's report uploads to version 4.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Failure of MacOS gcc build and test is due to gcc-11 being removed in latest macos runner images, and is addressed in #353.

Appears that the branch name for ion-tests changed.. which is what is causing ion-test-driver to fail. Added a commit here to force it in the ion-c workflow, but I'll follow up with a PR to ion-test-driver to default to main instead of master.


jQuery Deferred Object Updates

I fixed the issue reported in http://forums.bridge.net/forum/bridge-net-pro/bugs/575-jquery-deferred along with a spelling mistake.  I also added generic type support to the deferred object so that it would be easier to consume in c# code.

Hi @erdomke,
Thanks for the awesome pull-request, and for signing the CLA. We are reviewing the pr and there shouldn't be a problem with merging into the upcoming Bridge 1.9.0 releases.

Hi @erdomke,
Thank you for contributing. The Pull Request has been merged.

#15


Analysis Server --lsp can't handle extension methods

dartanalyzer version 2.6.0-edge.2c3f0fc359fda017565a5f23df7800a797f4c295

I'm running with --lsp. Any time I have an extension in my file, the analysis server won't analyze it. I get "Invalid file path" errors. Removing the extension causes it to start working, but then adding it back and it stops working.
The SDK at this commit generally has extension methods enabled. dartanalyzer CLI works correctly on this file.
Here is the instrumentation log:
1570039610328:Ver:1547748735539124457393:unknown:unknown:1.27.3:2.6.0-edge.2c3f0fc359fda017565a5f23df7800a797f4c295
1570039610482:Req:{"method"::"initialize","jsonrpc"::"2.0","id"::1,"params"::{"rootUri"::"file::///usr/local/google/home/nbosch/projects/dart_repro","initializationOptions"::{"onlyAnalyzeProjectsWithOpenFiles"::true},"capabilities"::{"workspace"::{"applyEdit"::true},"textDocument"::{"completion"::{"completionItem"::{"snippetSupport"::false}},"synchronization"::{"willSaveWaitUntil"::false,"willSave"::false,"didSave"::false},"codeAction"::{"codeActionLiteralSupport"::{"codeActionKind"::{"valueSet"::["quickfix","refactor","source"]}}},"signatureHelp"::{"dynamicRegistration"::false},"definition"::{"dynamicRegistration"::false}}},"processId"::30422,"trace"::"off"}}
1570039610622:Res:{"id"::1,"jsonrpc"::"2.0","result"::{"capabilities"::{"textDocumentSync"::{"openClose"::true,"change"::2,"willSave"::false,"willSaveWaitUntil"::false},"hoverProvider"::true,"completionProvider"::{"resolveProvider"::true,"triggerCharacters"::[".","=","(","$"]},"signatureHelpProvider"::{"triggerCharacters"::[]},"definitionProvider"::true,"implementationProvider"::true,"referencesProvider"::true,"documentHighlightProvider"::true,"documentSymbolProvider"::true,"workspaceSymbolProvider"::true,"codeActionProvider"::{"codeActionKinds"::["source","source.organizeImports","source.sortMembers","quickfix"]},"documentFormattingProvider"::true,"documentRangeFormattingProvider"::false,"documentOnTypeFormattingProvider"::{"firstTriggerCharacter"::"}","moreTriggerCharacter"::[";"]},"renameProvider"::true,"foldingRangeProvider"::true,"executeCommandProvider"::{"commands"::["edit.sortMembers","edit.organizeImports","edit.sendWorkspaceEdit","refactor.perform"]},"workspace"::{"workspaceFolders"::{"supported"::true,"changeNotifications"::true}}}}}
1570039610632:Req:{"method"::"initialized","jsonrpc"::"2.0","params"::{}}
1570039610654:Req:{"method"::"textDocument/didOpen","jsonrpc"::"2.0","params"::{"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart","version"::1,"languageId"::"dart","text"::"void main() {\n  'Foo'.doStuff();\n}\n\nextension Foo on String {\n  void doStuff() {\n    print(this);\n  }\n}"}}}
1570039613247:Req:{"method"::"textDocument/documentHighlight","jsonrpc"::"2.0","id"::2,"params"::{"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"},"position"::{"character"::5,"line"::4}}}
1570039613273:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039614226:Res:{"id"::2,"jsonrpc"::"2.0","error"::{"code"::-32003,"message"::"Invalid file path","data"::"/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"}}
1570039614705:Res:{"method"::"textDocument/publishDiagnostics","params"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/foo.dart","diagnostics"::[]},"jsonrpc"::"2.0"}
1570039614714:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039667444:Req:{"method"::"textDocument/definition","jsonrpc"::"2.0","id"::3,"params"::{"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"},"position"::{"character"::8,"line"::1}}}
1570039667447:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039667481:Res:{"id"::3,"jsonrpc"::"2.0","error"::{"code"::-32003,"message"::"Invalid file path","data"::"/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"}}
1570039667485:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039802079:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart~:add
1570039802092:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart~:remove
1570039802093:Res:{"method"::"textDocument/publishDiagnostics","params"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart~","diagnostics"::[]},"jsonrpc"::"2.0"}
1570039802093:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart:modify
1570039802094:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039802154:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039802198:Req:{"method"::"textDocument/didChange","jsonrpc"::"2.0","params"::{"contentChanges"::[{"range"::{"end"::{"character"::1,"line"::8},"start"::{"character"::1,"line"::2}},"text"::"","rangeLength"::69}],"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart","version"::2}}}
1570039802203:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039802393:Res:{"method"::"textDocument/publishDiagnostics","params"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart","diagnostics"::[{"range"::{"start"::{"line"::1,"character"::8},"end"::{"line"::1,"character"::15}},"severity"::1,"code"::"undefined_method","source"::"dart","message"::"The method 'doStuff' isn't defined for the class 'String'.\nTry correcting the name to the name of an existing method, or defining a method named 'doStuff'."}]},"jsonrpc"::"2.0"}
1570039802399:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039804307:Req:{"method"::"textDocument/didChange","jsonrpc"::"2.0","params"::{"contentChanges"::[{"range"::{"end"::{"character"::1,"line"::2},"start"::{"character"::1,"line"::2}},"text"::"\n\nextension Foo on String {\n  void doStuff() {\n    print(this);\n  }\n}","rangeLength"::0}],"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart","version"::3}}}
1570039804308:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039804354:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart:modify
1570039804389:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039856311:Req:{"method"::"textDocument/documentHighlight","jsonrpc"::"2.0","id"::4,"params"::{"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"},"position"::{"character"::0,"line"::1}}}
1570039856312:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039856368:Res:{"id"::4,"jsonrpc"::"2.0","error"::{"code"::-32003,"message"::"Invalid file path","data"::"/usr/local/google/home/nbosch/projects/dart_repro/web/main.dart"}}
1570039856371:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039857103:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:add
1570039857104:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:remove
1570039857116:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:add
1570039857116:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:remove
1570039861922:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:add
1570039861924:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/.git/index.lock:remove
1570039863807:Req:{"method"::"textDocument/didOpen","jsonrpc"::"2.0","params"::{"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml","version"::1,"languageId"::"yaml","text"::"name:: dart_repro\n\nenvironment::\n  sdk:: \">=2.3.0 <3.0.0\"\n\ndependencies::\n  js:: any\n\ndev_dependencies::\n  build_runner:: any\n  build_web_compilers:: any"}}}
1570039863808:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039863811:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039867697:Req:{"method"::"textDocument/didChange","jsonrpc"::"2.0","params"::{"contentChanges"::[{"range"::{"end"::{"character"::13,"line"::3},"start"::{"character"::12,"line"::3}},"text"::"6","rangeLength"::1}],"textDocument"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml","version"::2}}}
1570039867698:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039867700:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}
1570039867857:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml~:add
1570039867900:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml~:remove
1570039867901:Res:{"method"::"textDocument/publishDiagnostics","params"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml~","diagnostics"::[]},"jsonrpc"::"2.0"}
1570039867901:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml:modify
1570039867957:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::true},"jsonrpc"::"2.0"}
1570039870286:Watch:/usr/local/google/home/nbosch/projects/dart_repro:/usr/local/google/home/nbosch/projects/dart_repro/pubspec.yaml:modify
1570039870549:Res:{"method"::"textDocument/publishDiagnostics","params"::{"uri"::"file::///usr/local/google/home/nbosch/projects/dart_repro/foo.dart","diagnostics"::[]},"jsonrpc"::"2.0"}
1570039870553:Res:{"method"::"$/analyzerStatus","params"::{"isAnalyzing"::false},"jsonrpc"::"2.0"}

Even more confusing, depending on the content of the extension it can start working.
Doesn't work, see above:
void main() {
  'Foo'.doStuff();
}

extension Foo on String {
  void doStuff() {
    print(this);
  }
}

Adding 1 throw statement makes it work:
void main() {
  'Foo'.doStuff();
}

extension Foo on String {
  void doStuff() {
    print(this);
    throw 'sad';
  }
}

Removing the throw brings the behavior back to what it was.

I don't see the same behavior running in IntelliJ with a build from this morning. I'm not sure what the important difference is. @DanTup Any ideas?

We had an issue where extension methods weren't mapped onto a valid SymbolKind. The fix for that is here:
https://github.com/dart-lang/sdk/commit/3cffdaa01e654b7929efac376282891c82977c7b
What I can't explain though, is why you get this weird error, since I got the error:
[Error - 8:05:15 AM] Request textDocument/documentSymbol failed.
  Message: An error occurred while handling textDocument/documentSymbol request
  Code: -32001
[Error - 8:05:15 AM] An error occurred while handling textDocument/documentSymbol request: kind is required but was not provided
#0      new DocumentSymbol (package:analysis_server/lsp_protocol/protocol_generated.dart:5775:7)
#1      DocumentSymbolHandler._asDocumentSymbol (package:analysis_server/src/lsp/handlers/handler_document_symbols.dart:80:16)
#2      DocumentSymbolHandler._getSymbols.<anonymous closure> (package:analysis_server/src/lsp/handlers/handler_document_symbols.dart:130:32)

But also - I can't reproduce with the latest nightly (which includes the fix). But the hash given above looks like it should already include the fix. @natebosch - could you try on the nightly from https://gsdview.appspot.com/dart-archive/channels/be/raw/latest/sdk/ just to ensure we're on the exact same version? (and ensure you're not running the server from source or something that might affect that - the hash in the log matches what you gave, but I think that's just the SDK version and wouldn't reflect if you were running from source or an older snapshot).

I installed the nightly - dartanalyzer version 2.6.0-edge.c1f691c7973fdd9d31179097b6e7ff2b3b1d2931 and it does not repro.
I also can't repro on dartanalyzer version 2.6.0-dev.5.0.
I also did a fresh local build by removing the out directory and then tools/build.py --mode release --arch x64 create_sdk. It's version dartanalyzer version 2.6.0-edge.2c3f0fc359fda017565a5f23df7800a797f4c295. The problem no longer repros there either.
I had this very consistently reproducible before, but I guess we'll need to chalk it up to something strange in my local build? Or maybe there is some difference around the summary cache where after I had it working with another SDK it no longer is broken on the original one?
Either way, if I can't get it to show up again I don't think we can diagnose.

I had this very consistently reproducible before, but I guess we'll need to chalk it up to something strange in my local build?

I'm not very familiar with building the SDK locally (I tend to use nightlies and run the server from source), but is it possible you might have had a stale analysis_server snapshot file?

Or maybe there is some difference around the summary cache where after I had it working with another SDK it no longer is broken on the original one?

I'm not familiar with what this is, though the bug linked above was directly in the server implementation code (it seems like the same issue, though why it would generate the error it did still puzzles me).
If you see it again let me know and we'll go from there.


Fix greeting

Issue
Closes #612
What is the change?
Provide a small description in points of what did you change
fixes navbar, navbar now shows greeting when user is logged in
Is Development Tested?

[ ] Yes
[x] No

Before / After Change Screenshots
Before :

After :

There is Linting error

linting is failing due to module.export in utlils.js

even in the index.html page, this in console giving  the error that module is not defined
This export is for testing setup in my opinion as this file is not used anywhere as module

There is Linting error

linting is failing due to module.export in utlils.js

even in the index.html page, this in console giving the error that module is not defined
This export is for testing setup in my opinion as this file is not used anywhere as module

yes, but due to index.test.js file I have fixed that issue in my PR which I will raise today


Feature Request: Persisting the Hover Editor preview when click into the Hover preview

When I need to edit a note in the Hover Editor preview I need to click the Pin icon  for the Hover Preview to persist, otherwise when I click into the window to edit the note the Hover Preview will disappear.

This is not the case for the Hover Editor used in the body of a note where it persist for editing without having to pin the preview window first.

Have you tried using the right arrow key (keyboard) to enter the note instead?

Thanks I didn't know that. Would you consider supporting mouse as well?

Implemented in 0.1.32.  Enjoy!


ZEPPELIN-3737. Wrap JobManager page related stuff into class JobManagerService

What is this PR for?
This is refactoring PR which move all JobManager page related stuff into class JobManagerService.
What type of PR is it?
[Refactoring]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3737

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge if no more comments


Intermittent linting

I have a local folder with 3 **free SQLRPGLE source members.  One lints fine.  The second never linted.  The third did at first, but stopped.
How do I determine what's keeping it from linting?

Huh! There is an RPGLE language tools output channel. You could check there. I may use this as an excuse to log more information to it.

@Justin-E-Taylor Does the outline view work for each of them? Or does it only work for the one?

Later today I will add additional logging. In the meantime, feel free to share code here or with me privately and I can also look at those later today.

@Justin-E-Taylor 0.6.8 is out with additional logging.

The two files that lint load the outline relatively quick.  The source that won't lint takes a very long time, but the outline does load (ofc, it's 2-4x the size of the other source files).
Here's the message from the RPGLE language tools log:

Error linting source_file_path_here: Cannot read property 'type' of undefined
TypeError: Cannot read property 'type' of undefined
at Function.getErrors (c:\Users\justin.vscode\extensions\halcyontechltd.vscode-rpgle-0.6.9\dist\extension.js:1:10163)
at e.refreshDiagnostics (c:\Users\justin.vscode\extensions\halcyontechltd.vscode-rpgle-0.6.9\dist\extension.js:1:55041)
at runMicrotasks (:null:null)
at processTicksAndRejections (internal/process/task_queues.js:93:5)

@Justin-E-Taylor Any way you're able to share that source that's not working with me?

I'm afraid I can't share the source, even privately.  Sorry.

@Justin-E-Taylor No problem. Your best bet is to try to recreate it in a new source and then pass it on. I am going to close this until then, but please re-open if you recreate it!


[1.21 patchouli-snapshot] Modes.json won't build a usable patchouli book in 1.21

LaserIO version
1.9.1
Minecraft Version
1.21
(Neo)Forge Version
21.0.24-beta
Modpack & Version
ATM10
Do you have optifine installed?
No
Describe the issue
modes.json causes empty book
Steps to reproduce
with patchouli from @MrBysco 's 1.21 fork, targeting neoforge 21.0.24 instead of 21.0.42, might be the issue there????
Expected behaviour
Patchouli should be able to load
Screenshots
Bugged screenshot

bugged partial fix

Expected state

Log files
latest.log
debug.log
excerpt gist
Additional information
adding #1 to the modes.json item: field gets the book to generate, but the modes page for the cards show the wrong mode in the nbt data... modes.json I used
 {
  "name": "Modes",
  "sortnum": 1,
  "category": "laserio:mechanics",
  "icon": "laserio:textures/gui/buttons/modestocker.png",
  "pages": [
    {
      "type": "patchouli:text",
      "text": "Modes determine what a card fundamentally does. The following pages define each mode type currently available.$(br2)Each type of card (Item/Fluid/Energy) supports the the following three modes. Item cards are used as an example.$(br2)Redstone cards will support a different set of modes."
    },
    {
      "type": "patchouli:spotlight",
      "item": "laserio:card_item{channel:0b,exact:0b,inv:{Items:[],Size:2},itemextractamt:1b,itemextractspeed:20,mode:0b,priority:0s,regulate:0b,roundRobin:0,sneaky:-1b}",
      "text": "Insert Mode cards are a validate destination for objects being extracted by Extract Mode cards.$(br2)Stock mode cards will attempt to pull from Insert Mode cards."
    },
    {
      "type": "patchouli:spotlight",
      "item": "laserio:card_item#1{channel:0b,exact:0b,inv:{Items:[],Size:2},itemextractamt:1b,itemextractspeed:20,mode:1b,priority:0s,regulate:0b,roundRobin:0,sneaky:-1b}",
      "text": "Extract Mode cards attempt to remove objects from their adjacent block. Items, for example, will be removed from an adjacent chest and sent to an insert card."
    },
    {
      "type": "patchouli:spotlight",
      "item": "laserio:card_item#1{channel:0b,exact:0b,inv:{Items:[],Size:2},itemextractamt:1b,itemextractspeed:20,mode:2b,priority:0s,regulate:0b,roundRobin:0,sneaky:-1b}",
      "text": "Stock Mode cards attempt to find the designated items in their filter, and pull them from other Insert Nodes in the same network.$(br2)Stock mode cards require a filter set to Allow."
    },
    {
      "type": "patchouli:spotlight",
      "item": "laserio:card_item#1{channel:0b,exact:0b,inv:{Items:[],Size:2},itemextractamt:1b,itemextractspeed:20,mode:3b,priority:0s,regulate:0b,roundRobin:0,sneaky:-1b}",
      "text": "Sensor cards do not move objects around, but instead look at an adjacent inventory, and will emit a redstone signal on the redstone channel if the inventory matches the filter.$(br2)Sensor mode cards require a filter."
    }
  ]
}

I have personally have forked a copy of patchouli that has a prerelease 1.21-snapshot jar that is a copy of what i was using to test the book

You're reporting an issue for an unfinished port to 1.21 that can change at any time?


feat: add brand color

I'd like to suggest to include a "brand" color as part of the installation instructions because it's a useful pattern that will help the shadcn ecosystem grow into fully reusable page layouts and without devs needing to modify to tweak for their site's brand colors. Layouts can be fully copied over.
The word "accent" is taken already, so went with "brand".

This allow use of a color such as text-brand-400 and all variants from text-brand-50 through text-brand-950.
Devs can configure their own brand color for links or various aspects of a design.
When copying a layout from a generator (v0, etc) into their project, the layout and all components will automatically use their brand color without modifications needed.

Documenting this would establish a useful pattern, for v0 and other AI to be trained on.

If it would be possible then can you assign me to this issue I want to resolve this

I forgot to link to the PR I made for shadcn-svelte: https://github.com/huntabyte/shadcn-svelte/pull/332/files

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Reader doesn't read Calculated Columns (formulas for Tables/Excel 365 or 2019)

To reproduce:

Prerequisite: Excel 365 or Excel 2019.
Run the program ZDEMO_EXCEL47 and save the file on the frontend. Open this file and you see (notice the Calculated Formula =[@Airfare]+100):

Run the program ZDEMO_EXCEL37 to read (using ZCL_EXCEL_READER_2007) and display the file above, this produces:

ZCL_EXCEL_READER_2007 currently doesn't support the feature Calculated Columns.

@sandraros where can I find demo 47 and 37? I don't see them in the demos folder... I am trying to find an example of how to include totals in the workbook without having to code formulas?

hi, demos have been moved to https://github.com/abap2xlsx/demos

Thank you, @larshp

Does anybody got a solution already?

Does anybody got a solution already?

If there was a solution already, this issue would be closed (and a pull request with code would have been proposed and merged).


misleading error message

https://github.com/rspec/rspec-mocks/blob/v3.5.0.beta1/lib/rspec/mocks/message_expectation.rb#L117 raises an error when and_wrap_original is called on a pure double.  However, the error message refers to and_call_original, not and_wrap_original, which leads to confusion when you are not calling and_call_original at all.
There was a time that and_wrap_original was not documented and not part of the officially supported API, and at that time, this message would have been a very reasonable choice.  However, and_wrap_original is now documented and public, so the error message should refer to it.

Yep.  Want to work up a PR improving the error message?

Sure.  I just didn't want to make this change without agreement for the rspec team--I was anticipating more of a debate.
Here are my thoughts: The fact that and_call_original calls and_wrap_original is an implementation detail that users may not care about.  So in order to provide the right error message, we need to know whether and_wrap_original was called directly or via and_call_original.  There are 2 ways we could do that:

pass an extra arg to and_wrap_original--for instance, a Symbol with the name of the calling method.  If nil, then it was called directly.  However, because it is a documented method, that makes it part of a public interface, so we may even need to create a separate private method for this.
Catch the error sooner by duplicating the raise in and_call_original.  Less DRY in terms of both code and performance (it's running the same check twice).

Does the core team have any strong preferences about which approach to take?

Yep, extract it to a private method with an argument, we can't/don't want to change the public method signature.

@JonRowe PR is in #1063

Thanks :heart:


Call other Command from Command

Some form of call another command within the active command?
Or set the next command in front of ">"?

I am not sure what you mean. Do you have an example?

I have utility command serving as a "parameters builder" for a more complex command (on RootCommand).
Soon after 'build' would expose the command to run directly.

If I understand this correctly, you want the output of one command to be the input of another command.
For now, there is a workaround for this. I added an example named ParametersCommand where you can execute param build to build parameters and param execute that uses the same way of building parameters.
What it does is to have a method exposed (CreateParameters) that can be used by several commands.
This can also be used if you have commands that overlap and you do not want to have duplicate code.
Please get back to me if this soles you problem, and if not. A suggestion on how it should work would be great.


{ACR} Fix "Message: The subscription '00000000-0000-0000-0000-000000000000' could not be found." test error by waiting for operation

Related command
az acr connected-registry delete
Description
Fix "Message: The subscription '00000000-0000-0000-0000-000000000000' could not be found." test error by waiting for delete operation to finish. Addressing these two issues https://github.com/Azure/azure-cli/pull/18853#discussion_r1810260089 and https://github.com/Azure/azure-cli/pull/18611#discussion_r1810284183 following this solution https://github.com/Azure/azure-cli/pull/17185. Previous PR https://github.com/Azure/azure-cli/pull/30195
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

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

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

please resolve the style check issue: https://dev.azure.com/azclitools/public/_build/results?buildId=203331&view=logs&j=36dd4138-4d53-5e46-00d9-e5cd9744be05&t=1cf3879c-0a42-5ccd-7693-7a4781d739d8&l=94

@bebound Could you please help to review this PR as well?

@bebound Could you please help to review this PR as well?

LGTM, need to trigger batch CI as well.

/azp run

@yanzhudd, I fixed the style issue. Tried to rerun the tests, but its stuck at "Waiting for status to be reported". Also how do I trigger a batch CI, not sure if I have permission to do that

/azp run

I've push this pr to https://github.com/Azure/azure-cli/tree/nguyenma/fixTrack2SDKBug and the batched CI is triggered.


SAK-45866 - Deal with java.time.LocalDateTime

Hey @ottenhoff and @ern - Feel free to suggest that I move some of the code in LTIAdminTool into the service as a new method.  I could add a method that took LocalDateTime and a TimeZone - but it just did not feel that it added much.


an onLoad event can be useful

A nice new feature suggestion: why don't automatically handle an onLoad event property (an event handler function) that can be called when the spinner load it's contents?
This can help developers to take actions when loading is finished.

The spinner isn't responsible for doing the loading, so I'm not sure how that would work. The parent component should be responsible for managing state around whatever is being loaded.
Am I misunderstanding?

You are right, this can be handled on the top level. My fault!
Thanks


[#3188] feat(core): Clean user,group and role entity in RelationalGarbageCollector

What changes were proposed in this pull request?
support clean user, group and role entity in RelationalGarbageCollector
Why are the changes needed?
Fix: #3188
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
ut

@qqqttt123 could you help to review this when you free, thx

@qqqttt123
Do you have any additional comments on the matter? I'm okay with it.


[UMBRELLA] Kubectl independence: testing

Part of #114.
Improve Kubectl independence by improving testing.
Currently, kubectl is tested against kubernetes and kubernetes is tested using kubectl. This tight coupling prevents kubectl from being tested quickly and adequately.
The goal of this issue is to track the steps and improvements that can be done to test kubectl independently from Kubernetes (or at least improve that state).

Key component of testing: #87

/remove-lifecycle stale

/remove-lifecycle rotten

/sig cli
/area kubectl

/remove-lifecycle rotten


eio-posix-1.1 fails to build on macOS ventura 13.6.7

error: builder for '/nix/store/zpssmmd2cifm4xlsyksnx04vmskx0iwi-eio_posix-1.1.drv' failed with exit code 1;
       last 20 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/2giwhf2h39bchbz2h8gmyydk0xzyqivh-eio-1.1.tbz
       > source root is eio-1.1
       > setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file eio-1.1/tests/trace.md
       > Running phase: patchPhase
       > Running phase: configurePhase
       > patching script interpreter paths in .
       > Running phase: buildPhase
       > File "lib_eio_posix/dune", line 9, characters 9-24:
       > 9 |   (names eio_posix_stubs))
       >              ^^^^^^^^^^^^^^^
       > (cd _build/default/lib_eio_posix && /nix/store/iyk4jyp5aqmrp6mq5mlvirjdijhrdbna-clang-wrapper-16.0.6/bin/cc -O2 -fno-strict-aliasing -fwrapv -pthread -D_FILE_OFFSET_BITS=64 -fdiagnostics-color=always -D_LARGEFILE64_SOURCE -g -I /nix/store/6sc7asvwvwqicyczhsiyhhaqgkwd81a3-ocaml-base-compiler-5.1.1/lib/ocaml -I /nix/store/6sc7asvwvwqicyczhsiyhhaqgkwd81a3-ocaml-base-compiler-5.1.1/lib/ocaml/runtime_events -I /nix/store/6sc7asvwvwqicyczhsiyhhaqgkwd81a3-ocaml-base-compiler-5.1.1/lib/ocaml/threads -I /nix/store/6sc7asvwvwqicyczhsiyhhaqgkwd81a3-ocaml-base-compiler-5.1.1/lib/ocaml/unix -I /nix/store/6z4nynxml3hm47rjlrivncpbyp75rwcc-bigstringaf-0.9.1/lib/ocaml/5.1.1/site-lib/bigstringaf -I /nix/store/77pxgjv7ndrhm11wij2pwmnw1l37cl68-iomux-0.3/lib/ocaml/5.1.1/site-lib/iomux -I /nix/store/9nhfnqlcx5wc4749whcpjjfgh9ljip07-optint-0.3.0/lib/ocaml/5.1.1/site-lib/optint -I /nix/store/f9y9cimmydclqbvh5nsym0n329nn9cmv-lwt-dllist-1.0.1/lib/ocaml/5.1.1/site-lib/lwt-dllist -I /nix/store/fbd6i566p0s915i4c4p16sa2pdnpfkk3-seq-base/lib/ocaml/5.1.1/site-lib/seq -I /nix/store/h7rl940vdrv7ghz5f7iq2mv5b7g3ypkg-eio-1.1/lib/ocaml/5.1.1/site-lib/eio -I /nix/store/h7rl940vdrv7ghz5f7iq2mv5b7g3ypkg-eio-1.1/lib/ocaml/5.1.1/site-lib/eio/core -I /nix/store/h7rl940vdrv7ghz5f7iq2mv5b7g3ypkg-eio-1.1/lib/ocaml/5.1.1/site-lib/eio/runtime_events -I /nix/store/h7rl940vdrv7ghz5f7iq2mv5b7g3ypkg-eio-1.1/lib/ocaml/5.1.1/site-lib/eio/unix -I /nix/store/h7rl940vdrv7ghz5f7iq2mv5b7g3ypkg-eio-1.1/lib/ocaml/5.1.1/site-lib/eio/utils -I /nix/store/hylnp4rnal9mfk80lgyyk24hgi7a861v-thread-table-1.0.0/lib/ocaml/5.1.1/site-lib/thread-table -I /nix/store/jh6j1kg1vk1w4pxm18ljgkfc1zjfpp5x-mtime-2.0.0/lib/ocaml/5.1.1/site-lib/mtime -I /nix/store/jh6j1kg1vk1w4pxm18ljgkfc1zjfpp5x-mtime-2.0.0/lib/ocaml/5.1.1/site-lib/mtime/clock/os -I /nix/store/l8g8g5mxgvwbn7rxcgw0l1qv26rv464a-cstruct-6.2.0/lib/ocaml/5.1.1/site-lib/cstruct -I /nix/store/mj0ri949k37ar70192vzghhdfyf3r520-psq-0.2.1/lib/ocaml/5.1.1/site-lib/psq -I /nix/store/qikgfx8jqhhnyih7k3qhka1hn3vm9scp-fmt-0.9.0/lib/ocaml/5.1.1/site-lib/fmt -I /nix/store/rwnkfah6ckvg65sizrvks7m7v8azy5jj-hmap-0.8.1/lib/ocaml/5.1.1/site-lib/hmap -I /nix/store/ynq5inhfj63d1ds9ifhdsi1297ndllzz-domain-local-await-1.0.1/lib/ocaml/5.1.1/site-lib/domain-local-await -I ../lib_eio/unix/include -o eio_posix_stubs.o -c eio_posix_stubs.c)
       > eio_posix_stubs.c:133:7: error: call to undeclared function 'preadv'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
       >   r = preadv(Int_val(v_fd), iov, n_bufs, offset);
       >       ^
       > eio_posix_stubs.c:150:7: error: call to undeclared function 'pwritev'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
       >   r = pwritev(Int_val(v_fd), iov, n_bufs, offset);
       >       ^
       > 2 errors generated.
       >
       For full logs, run 'nix-store -l /nix/store/zpssmmd2cifm4xlsyksnx04vmskx0iwi-eio_posix-1.1.drv'.
error: 1 dependencies of derivation '/nix/store/36z756dqwgjgk4nsbrlfdzxnpbnz94yg-eio_main-1.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/sfyqcshn69716iaij95zlmi92h41yfb2-forester-4.1.0.drv' failed to build

To Reproduce
Run nix build on https://git.sr.ht/~jonsterling/ocaml-forester/commit/e9bd3a5a784e8fe1a34928d85ef0188e3ea41947
Expected behavior
Build succeeds
Environment

macOS Ventura 13.6.7
Version of the code:

   "opam-nix": {
     "locked": {
       "lastModified":<PHONE_NUMBER>,
       "narHash": "sha256-UOJNCbqvxABD56JZtZkv3C9ufdqrs7/Ep4AKkCHgPuo=",
       "owner": "tweag",
       "repo": "opam-nix",
       "rev": "1d3cbd6d3f247db77cb581c88c9a1d72e4acad60",
       "type": "github"
     },
...
   },

Build does succeed on at least macOS Sonoma 14.5

Hey! I don't have a macOS machine with this OS version, so can't reproduce. Can you check if this builds locally with just opam, without opam-nix? I feel like it could just be broken there.

I managed to build it fine with native opam/dune

Ok, thanks! I've got a VM with the right macOS version now, will fix

Hey! I can't seem to repro :(
$ git clone https://git.sr.ht/~jonsterling/ocaml-forester
$ cd ocaml-forester
$ git checkout e9bd3a5a784e8fe1a34928d85ef0188e3ea41947
HEAD is now at e9bd3a5 upgrade menhir
$ nix build
trace: warning: `overrideScope'` (from `lib.makeScope`) has been renamed to `overrideScope`.
trace: warning: `overrideScope'` (from `lib.makeScope`) has been renamed to `overrideScope`.
trace: warning: `overrideScope'` (from `lib.makeScope`) has been renamed to `overrideScope`.
$ ./result/bin/forester --version
4.1.0
$ sw_vers
ProductName:		macOS
ProductVersion:		13.6
BuildVersion:		22G120

All I got during the build is some warnings about unused variables.

Strange, running
$ nix build github:tweag/opam-nix#eio_posix.latest

succeeds, but even after running nix flake update, the build of ocaml-forester fails with the same error.

Oh, are you running on Apple silicon (aarch64) or Intel (x86_64)?

It's an intel machine.

Similar issue?
       > /nix/store/j645h2bcqjww615dfkka4v4q1nyyy5m1-cctools-port-973.0.1/libexec/as/x86_64/as: this system assembler is deprecated. Please migrate to the clang integrated assembler (`as -q').
       > Undefined symbols for architecture x86_64:
       >   "_preadv", referenced from:
       >       _caml_eio_posix_preadv in libeio_posix_stubs.a(eio_posix_stubs.o)
       >      (maybe you meant: _caml_eio_posix_preadv)
       >   "_pwritev", referenced from:
       >       _caml_eio_posix_pwritev in libeio_posix_stubs.a(eio_posix_stubs.o)
       >      (maybe you meant: _caml_eio_posix_pwritev)
       > ld: symbol(s) not found for architecture x86_64
       > clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
       > File "caml_startup", line 1:
       > Error: Error during linking (exit code 1)
       >
       For full logs, run 'nix log /nix/store/xdgsaz5j39zl7n74w53by20r3h2zmyld-forester-4.3.1.drv'.

in
~/learn/forest> sw_vers
ProductName:		macOS
ProductVersion:		14.7
BuildVersion:		23H124


Add Installation Instructions to README about building from .tar.gz

I was having issues building the latest version of musikcube available on the AUR (0.96.10-1), so I had to install it from an older version (I knew 0.96.8 worked on my other machine so I used that) by downloading the .tar.gz file in the Releases tab on this Github repo.
The installation of it was not mentioned specifically anywhere and the generic .tar.gz installation instructions were not identical so I was wondering if specific instructions can be added to the Installation Guide page.
Here's what worked for me:
tar -xzf musikcube-0.96.8.tar.gz
cd musikcube-0.96.8/
cmake .
make .
sudo make install .
On other forums, the instructions are similar but they don't have the cmake . step.
Information about my machine:
Kernel: 5.15.11-arch2-1
Shell: bash 5.1.12

Thanks, I can add these instructions to the wiki, but can you tell me about the build issues you experienced with 0.96.10? What failed? I have an Arch installation and it seems fine.

@clangen Here is a Gist of all the output from installing it via yay

Build instructions on the wiki have been updated as requested.
I took a look at your build logs, and it seems yay is trying to build 0.96.7 -- you can see the version number in the output:
/home/hussein/.cache/yay/musikcube/src/musikcube-0.96.7/src/plugins/httpdatastream/LruDiskCache.cpp:305:21: error: base operand of '->' is not a pointer
  305 |         return entry->id == id;
      |                     ^~

This particular issue was fixed as part of 0.96.10.
> yay -Ss musikcube
aur/musikcube-git 0.96.7.r5.g00cf3eb5-1 (+2 0.00)
    a terminal-based cross-platform music player, audio engine, metadata indexer, and server
aur/musikcube 0.96.10-1 (+17 1.21)
    A terminal-based cross-platform music player, audio engine, metadata indexer, and server

I think perhaps you tried to install musikcube-git instead of musikcube -- could these be the case? Note that I don't maintain either of these ports, and it looks like musikcube-git is a bit out of date.

I don't believe I was installing musikcube, not musikcube-git, as you can see on Line 16 of the Gist. Either way, I can see on the musikcube AUR package page that the version has been updated today so that should no longer be an issue for other people.
Also thanks for including the cmake -G "Unix Makefiles" . in the build instructions page since when I just typed cmake . no audio drivers were detected, so I actually had to redo my install. Just a note for any future readers here if you also have that issue.
Closing this issue now since the original ask is now resolved.


Update the TryGetJointPose docs to accurately describe the set of inputs

These functions only work if you pass in the specific Handedness.Left or Handedness.Right. They should be documented as such.
https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4175

/azp run mrtk_docs

IMO ideally we should have a pure enum Handedness { Left, Right }, and then a enum HandednessFlags {...} with mask bits where it makes sense. I.e. use the strict left/right enum when either one or the other is expected (which is the majority of cases), and the flag where any combination is possible. That should avoid a lot of the current confusion when Handedness.Both etc. don't work.


fixes: python -m build fails

python -m build fails with:

running check
error: The docutils package is needed.

since check.restructuredtext is set to 1 in setup.cfg, setuptools with require docutils. I think this is needed to parse the structured text README.
That dependency needs to be specify in pyproject.toml file. It is recommended practice to have a pyproject.toml file anyway. https://packaging.python.org/en/latest/guides/modernize-setup-py-project/#should-pyproject-toml-be-added

@arenevier does it make sense to add a CI with this command ``python -m build`? I want to make sure that we don't break it.

@ggrossetie : good idea. Instead of adding a new CI step,  I added two new targets to tox. One to build the source distribution (the one currently failing). And one to build binary distribution (which is not currently broken).

Just to be sure, the two new targets do not run on the CI? If not, I think we should run them to make sure that a future pull request won't break them.

Also, I just noticed that we don't have a tox environment for Pillow 10.x

Also, I just noticed that we don't have a tox environment for Pillow 10.x

I can make a new PR to add it. And maybe python 3.12. I will wait for this one to be merged first, otherwise there will be merge conflicts.

Just to be sure, the two new targets do not run on the CI? If not, I think we should run them to make sure that a future pull request won't break them.

Fixed. They run now with the latest commit of the branch.

Awesome, thanks 🎉


CSS files are not bundled for self-contained build (multiple CSS files are loaded for each library)

Expected Behavior
One CSS file for the whole self-contained build should be loaded, based on the theme selected.
Current Behavior
Multiple CSS files (per library) are loaded separately by the browser, causing some performance degragation.
Steps to reproduce the issue

Build & serve the sample app self-contained
Check network trace to see, that more than one CSS file is loaded

Context

OS/Platform: Windows
Node.js Version: 10.11.0
npm Version: 6.4.1
Browser (if relevant): Chrome Dev.
Other information: Tested on 1.59.0

Affected components

[x] ui5-builder
[ ] ui5-server
[ ] ui5-cli
[ ] ui5-fs
[ ] ui5-project
[ ] ui5-logger

CSS bundling might not only be helpful in terms of performance, but also in regards to enabling caching mechanisms.
Currently its seems as that there is no straight-forward way of caching and invalidating resources files with a self-contained  build. With a self-contained build, the core resource files can not be invalidated using a cachebuster concept as it was formally possible when UI5 Core resources were being loaded from a CDN.
If the tooling would allow to produce CSS bundles, a hash or version could be attached to the file name sap-ui-custom.x234dff.css and on-demand updating of invalide CSS resources files would be possible.


Integrate into HTML

Is there a way to load this on my existing HTML page that runs the player, instead of in another Javascript application, similar to this:
    <video id="my-video" class="video-js" controls preload="auto" width="1280" height="720" poster="MY_VIDEO_POSTER.jpg" data-setup="{}">
      <source src="playlist.m3u8" type="application/x-mpegURL" />

        To view this video please enable JavaScript, and consider upgrading to a web browser that <a href="https://videojs.com/html5-video-support/" target="_b$

    </video>

@qome sorry for such a late response, check the examples javascript here: https://github.com/spodlecki/videojs-event-tracking/blob/master/examples/base.js


Windows VS Code extension starts emulator failure, wrong config path

Instructions
Hi, the command of starting emulator in Windows VS Code Cadence extension is failing because the config path is not correct.
Problem
The auto-generated command for starting the emulator from the current vs code workspace is:
flow project start-emulator --config-path=/c:/<ProjectPath>/flow.json --verbose

Notice that there is a leading / in the config-path argument, causing this command to fail. The correct command should be
flow project start-emulator --config-path=c:/<ProjectPath>/flow.json --verbose

Steps to Reproduce
Acceptance Criteria
Context
I am trying to fix that just on my computer, I am not an expert so I don't know whether the same change can be applied to other systems like Linux/MacOS

Any progress on this issue? I have facing the same problems on WIndows.

Some development scripts can only be run on Mac. I would try to work it out once I get a Mac machine.

I have worked on a temporary solution for Windows users. It requires building from source. Below are the steps :-

Make sure to uninstall all previous versions of the extensions from VS Code.
Clone vscode-cadence extension from onflow/vscode-cadence
Run npm install inside the root directory of the cloned project
Go to ./src/config.ts file and change line 42 inside readLocalConfig() function from this.configPath = configFile.path to this.configPath = configFile.path.slice(1)
Run npm run package in Ubuntu WSL Terminal. This will create an out folder inside the project directory and a .vsix file.
Run code --install-extension <absolute/path/to/above/created/.vsix/file>. This should be run in Powershell or Windows terminal.

I hope this helps Windows users while @hellohanchen works on fixing this issue. 😃


How to check if a table exists in Azure.Data.Tables?

Library name and version
Azure.Data.Tables @ 12.5.0
Query/Question
So I'm working my way through the migration guide like a good person...
My Microsoft.Azure.Cosmos.Table reporting code (reads, not writes) absolutely requires that I check to see if the table in question exists or not, and makes decisions on that.  I do not want to blindly create-table-if-not-exist.
However, I can't see the equivalent of this method https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.table.cloudtable.exists?view=azure-dotnet in Azure.Data.Tables.
How to do it?
If the response is: "you can't", then I will have to create a ticket for this to be added, because I can't migrate my code to your new package without it.
[Note: create-table-if-not-exist is obviously a good thing, but only for my data-writing code, and not for my data-reading code.]
Environment
.NET 6
Windows 10
Visual Studio 2022

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @Bellarmine-Head  - Could you describe a bit more about the scenario where your application needs to check that a table exists? What does it do after it obtains that information?

Thanks for the context. The omission of a dedicated Exists method was an intentional omission. The main reason is that in encourages racy code. For example, the result of Exists is only valid at the instant in time it was checked. If code wants to check for existence before attempting to manipulate data in the table, it should instead just attempt to manipulate the data and handle failures for when the table does not exist.
That said, it is possible to check if a table exists in a less direct way, using the TableServiceClient.Query method. You can find a sample of querying for tables here.
For this specific scenario, it might look like the following:
bool exists = false;
await foreach(var tbl in service.QueryAsync(t => t.Name == "mytable"))
{
    exists = true;
}

Thanks @christothes
I understand the reasons for the omission.  That's fine, just as long as it's called out in the migration guide... which you will now instigate.  Thx.


Work In Progress: hugolib: Add page search, i.e. related content

Several attempts have been started to fix #98 --  all of them have failed for some reason. It is a hard problem to solve, and I think the main reason for failure has been the bottom-up-approach, i.e. we have started with the hardest problem: Solving Sherlock's last case.
The reason I'm picking up this ball again now is this Twitter thread:
https://twitter.com/scott_lowe/status/898398437527363585
Using intersect and keywords in page params work reasonably well, but it is quadratic and will be slow to unusable for larger sites.
So, instead of solving the hardest problem, I have started on this PR by outlining an interface:
type PageSearcher interface {
	Search(args ...interface{}) (Pages, error)
	SearchIndex(index string, args ...interface{}) (Pages, error)
	Similar(p *Page) (Pages, error)
	SimilarIndex(index string, p *Page) (Pages, error)
}

Naming suggestions welcomed.
The idea is that a user defines a set of indexes in config.toml:
indexes:
  - param: keywords
    weight: 1
 - param: tags
    weight: 3

Then we lazily build some sort of index from that, and then you can do fast searches like:
{{ .Site.RegularPages.Similar . }}

{{ .Site.RegularPages.Search "hugo" }}

{{ .Site.RegularPages.SearchIndex "keywords" "hugo" | limit 10 }}

I have not thought to hard about what the "default search" would look like above (default i.e. first index, all indexes?)

/cc @spf13 @moorereason @anthonyfok @digitalcraftsman and all of you ...

@spf13 @onedrawingperday @moorereason @budparr @digitalcraftsman @rdwatters
I'm close to wrapping this up (there is still some work to do), and I'm pretty pleased with the result. I'm getting some very sensible "similar output" on my blog with a not very thought out tags/keywords setup. And it is surprisingly fast (see timings below).
We will probably revisit the underlying algorithms, but we should aim to get the API right, so I wanted to be clear about how that currently looks, so people can object/suggest:
type PageSearcher interface {
	Search(args ...interface{}) (Pages, error)
	SearchIndex(index string, args ...interface{}) (Pages, error)
	Similar(doc index.Document) (Pages, error)
	SimilarIndex(index string, doc index.Document) (Pages, error)
}

Used in a template:
{{ $similar := .Site.RegularPages.Similar . | first 5 }}

See this commit on my blog:
https://github.com/bep/bepsays.com/commit/28e07cdc4ff9596ee3deb99888e4a31a8bb5b1ab
Without similar.html partial in single.html:
▶ hugo
Started building sites ...
Built site for language nn:
0 of 3 drafts rendered
0 future content
0 of 1 expired rendered
122 regular pages created
28 other pages created
0 non-page files copied
68 paginator pages created
19 tags created
0 series created
Built site for language en:
0 of 4 drafts rendered
0 future content
0 expired content
27 regular pages created
13 other pages created
0 non-page files copied
18 paginator pages created
0 series created
5 tags created
total in 271 ms

With  similar.html partial in single.html:
▶ hugo
Started building sites ...
Built site for language nn:
0 of 3 drafts rendered
0 future content
0 of 1 expired rendered
122 regular pages created
28 other pages created
0 non-page files copied
68 paginator pages created
19 tags created
0 series created
Built site for language en:
0 of 4 drafts rendered
0 future content
0 expired content
27 regular pages created
13 other pages created
0 non-page files copied
18 paginator pages created
5 tags created
0 series created
total in 283 ms

I also tested it on the @lowescott who's tweet jump started this.
As is
Started building sites ...
Built site for language en:
0 draft content
0 future content
0 expired content
1891 regular pages created
468 other pages created
0 non-page files copied
0 paginator pages created
217 tags created
14 categories created
total in 1609 ms

With new related posts in single:
 ▶ hugo
    Started building sites ...
    Built site for language en:
    0 draft content
    0 future content
    0 expired content
    1891 regular pages created
    468 other pages created
    0 non-page files copied
    0 paginator pages created
    217 tags created
    14 categories created
    total in 2081 ms

And finally the old version that used intersect on tags:
    ▶ hugo
    Started building sites ...
    Built site for language en:
    0 draft content
    0 future content
    0 expired content
    1891 regular pages created
    468 other pages created
    0 non-page files copied
    0 paginator pages created
    217 tags created
    14 categories created
    total in 9286 ms
    ```

Very cool.
Pardon the ignorance. Is this pulling specifically from tags, all taxonomies, or the full page index?

@rdwatters I suggest you read the first post.

Apologies @bep; arrived here from an email thread.

Naming suggestions welcomed.

How about the following?
1. {{ .Site.RegularPages.Related . }}
2. {{ .Site.RegularPages.Find "hugo" }}
3. {{ .Site.RegularPages.RelatedTo "keywords" "hugo" | limit 10 }}

I'm not committed to number 2.
This is a really awesome feature. Thanks!

@budparr with my latest commit this should be close to feature complete.
Put something like this in your config (either on site or language level):
[searchIndexes]
[searchIndexes.keywords]
weight=20
[searchIndexes.tags]
weight=10

Note on the above:

Currently only string and string slice Param support (and only values in the Param map, but that is more or less all of the page front matter)
Weight is "higher is better"

@rdwatters I will sleep on the naming thing.

My only concern with the API is that we leave room for a simhash-style feature similar to what was proposed in https://github.com/bbalet/gorelated.  It's not clear to me how much simhash would slow down a site build, but I'd like to leave the door upon to adding the feature later.
As to naming convention, I would think that "similar" fits more with a simhash solution while "related" would lend itself to attribute/tag comparisons.  X is related to Y because they both have tag "foo."  X is similar to Z because their content is similar.

@moorereason that was my thought about the current naming. This first version will support Param of string, []string and time -- one could assume that we could add the Content field as an index in the future. The smash and similar will have a runtime cost, but my biggest concern is the fact that it has to somehow be language contextual to be really effective, and then we're building and maintaining a search engine. But my big point with this exercise is to cover the "90% use case" (or whatever) first.

@budparr if you're interested in testing this, I have added date support, so now the config looks like this:
[[searchIndexes]]
name = "keywords"
weight = 200
[[searchIndexes]]
name  = "tags"
weight = 100
[[searchIndexes]]
name  = "date"
weight = 10
pattern = "2006"

The above enables pages from the same year (or month if you change the pattern to 200601) to be "more similar". This of course, for smaller data sets, creates some matches that are only related by date, so I guess some kind of configurable threshold will be needed.

And now it looks like this:
search]
threshold = 1
[[search.indices]]
name = "keywords"
weight = 200
[[search.indices]]
name  = "tags"
weight = 100
[[search.indices]]
name  = "date"
weight = 1
pattern = "2006"

@bep Related may be a better name than Search.
As you said, Search gives the impression of a more "google search" like feature. When I first saw the title for this PR I assumed you would add a "native" search support so users could add a Page Search to their websites.
With related it would look like this, which on first glance makes it clear that these settings are for related (content).
[related]
threshold = 1
[[related.indices]]
name = "keywords"
weight = 200
[[related.indices]]
name  = "tags"
weight = 100
[[related.indices]]
name  = "date"
weight = 1
pattern = "2006"

Just my 2ct. 😄

@kevingimbel yea, you may be right -- but then we have the problem getting both a verb and a noun to work:
type pageRelater interface {
	Related(args ...interface{}) (Pages, error)
	RelatedIndex(index string, args ...interface{}) (Pages, error)
	RelatedTo(doc index.Document) (Pages, error)
	RelatedToIndex(index string, doc index.Document) (Pages, error)
}

Hmm ... FindRelatives...

Hi @bep I'm running a simple case of this with your latest and getting the error can't evaluate field Related in type hugolib.Pages. Very likely I just don't understand the interface, but copying from above (using Related, not Search).
Aside from the error, I'd want to clarify my understanding of the feature and ask a question:
This is how I think this works: The name key in config can be assigned to any parameter, and the index looks through all pages that match the parameter with matching values.
Like this:
[related]
threshold = 1
[[related.indices]]
name = "someparam"
weight = 200

These would match:
/content/post/one.md -> param.someparam: [foo]
/content/author/bill.md -> param.someparam: [foo]

My question is: Would it be possible for the keyword to match something else, like .File.Path
I ask because the way I often use related content is one-sided:
/content/post/one.md -> param.authors: [/author/bill.md, /author/bob.md]
/content/author/bill.md
/content/author/bob.md

Then in my template, I query the authors param where it intersects  with .File.Path.
Hope that makes sense. If this is too off-topic, no worries. I don't want to distract you from getting this out.

@budparr your problem running this indicates that you have a "wrong" Hugo version. Your other question I dont't understand, but I suspect it to be slightly off topic.

I had the right version, but was using Similar instead of Related, thank you. I suppose you're right about the other - was just thinking out loud.

@budparr I have added one more config option, it now looks like this:
[related]

# Only include matches >= threshold, a normalized rank between 0 and 100.
threshold = 1

# To get stable "See also" sections we, by default, exclude newer related pages.
includeNewer = false

[[related.indices]]
name = "keywords"
weight = 200
[[related.indices]]
name  = "tags"
weight = 100
[[related.indices]]
name  = "date"
weight = 1
pattern = "2006"

The final interface looks like this:
type pageRelater interface {

	// Template example:
	// {{ $related := .RegularPages.Related . }}
	Related(doc related.Document) (Pages, error)

	// Template example:
	// {{ $related := .RegularPages.RelatedIndices . "tags" "date" }}
	RelatedIndices(doc related.Document, indices ...interface{}) (Pages, error)

	// Template example:
	// {{ $related := .RegularPages.RelatedTo ( keyVals "tags" "hugo", "rocks")  ( keyVals "date" .Date ) }}
	RelatedTo(args ...types.KeyValues) (Pages, error)
}


Make multimic2 compile

This commit gets multimic2 to compile. It tries to change as little else
about it as possible other than to get it to compile. (It's not tested
in any other way).
Co-authored-by:markww

Don't feel obligated to pull this into your branch if you don't want. (Or also you can, if you do want). This is just another way I can think of to help get you up and running with auth logic.

@markww @bgogul This now just makes new files rather than modifying Marks. This PR is the base for #187 and #197. If you don't want me to merge this in, I can also just delete these files and make the base of #187 main. Let me know what you want me to do.

@markww @bgogul This now just makes new files rather than modifying Marks. This PR is the base for #187 and #197. If you don't want me to merge this in, I can also just delete these files and make the base of #187 main. Let me know what you want me to do.

Is my understanding that this just makes a copy of the multimic directly and #187 and #197 use them? If so, let us drop this PR and continue the discussion on the dependent PRs? Are the other PRs ready for review? Or, were you planning to make it testable with your may, will, allowedUsage changes?

Is my understanding that this just makes a copy of the multimic directly and #187 and #197 use them? If so, let us drop this PR and continue the discussion on the dependent PRs? Are the other PRs ready for review? Or, were you planning to make it testable with your may, will, allowedUsage changes?

It changes multimic to get it to compile. OK I can drop it, though. 187 should be ready for review. I can maybe just make  tests out of the queries to make it more incremental.

Yeah, I think that this can just be dropped. I'm going to close this so it's out of the PR view, but leave the backing branch intact so it can be restored if we want it.


Added AnnotatedTarget

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 17 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1106

Relevant Lines:
1106

💛  - Coveralls


added clarification about groups created in admin center

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4806

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @scanum, for your information
Thank you

@LolaJacobsen PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

I'm checking with PM Kyle Blevins.

From Kyle: "I can confirm the part about how to change visibility of a group in Outlook. I'm now aware of the state a group is in when created from the Teams Admin Center though, so can't confirm that part."
I'm checking with PM Roshin Ramesan.

From PM Harsh Chandra: "Per @nomorephones we don't allow creation of groups from the Teams admin center. We only allow the creation of teams.


Add #cloud-config header to all overlay files

because kairos-agent config command ignores those files because of the missing header. That command is supposed to print all the config that is taken into account from kairos-agent and immucore and all.
Currently it ignore those files the same way it ignores them when running kairos-agent manual-install et al. Adding the header will make the kairos-agent respect those files, essentially with no effect since none of these files set any installation options.
The only useful result will be that kairos-agent config will print the full config making it easier for the user to see the full merged yaml that results from all the available config files.

We'll do this instead: https://github.com/kairos-io/packages/pull/1060
We will remove that directory from the directories scanned by the kairos-agent and we'll document it. That directory should only be used for stage definitions.


Center Placeholder

Hey,
Please merge this pull request on or after 1st October during Hacktoberfest.
Thanks.

Hey,
Please review this pr and merge it. Thanks!

Hey even after successful merge my pr count in hacktoberfest didn't go up. Why?


[Feature Request]: Add multiple documents in a single commit, for perfromance

Describe the problem
I am inserting 44k documents (with precomputed embeddings) to chromadb using a single .add() call. I assumed this would be a lot faster than adding them one by one, but, looking at the code, I think chromadb just loops over them and executes an SQLite transaction per document, and I think this is what makes it slow.
I did some timings with my data. On a powerful computer, into an in-memory database (Client()), the insertion takes 6 minutes. On a persistent database, I didn't wait for it to finish with the default settings; however I did get it to finish in 15 minutes by running this code before the insertion. This is, of course, wildly unsafe, but since I'm creating the database in this script, I'm fine just rerunning it if it fails.
client._sysdb._conn_pool.connect().execute("pragma journal_mode = off")
client._sysdb._conn_pool.connect().execute("pragma temp_store = memory")
client._sysdb._conn_pool.connect().execute("pragma synchronous = off")
client._sysdb._conn_pool.connect().execute("pragma locking_mode = exclusive")

Profiling shows that most time is spent in SQLite, which is perhaps not surprising.
Here's how I add my documents:
snippets: Iterable[Snippet]

collection.add(
    ids=[s.hash for s in snippets],
    documents=[s.text for s in snippets],
    metadatas=[_Metadata.from_snippet(s).to_dict() for s in snippets],
    embeddings=[s.embedding.tolist() for s in snippets],
    )

My ids are sha256 hex strings, i.e. 64 character long strings. The documents are a few hundred bytes long. Metadata contains a short string (filename) and a start offset (int). The embeddings 1536-dimension float vectors.
Describe the proposed solution
Do all the inserts in a single transaction instead of each in a separate one.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
chromadb 0.4.2, chroma-hnswlib 0.7.1

@HammadB any thoughts here?

Yep! This is something thats been on my mind, @levand had the first pass of the sqlite code transact per entry but it is worth us profiling the difference and figuring out a batching scheme.

I'm also experiencing the same issue, I used a similar strategy to add to the collection. In my case, I had 50k records and the execution takes about 18 minutes.  I did some digging around and noticed that the document part in _update_metadata was consuming most of the time. If the block below is commented it takes 70 seconds. To have it running in a similar time frame without commenting any code, it suffices calling the add without providing the documents kwarg.
https://github.com/chroma-core/chroma/blob/126ba134a852060c886ea59471ca463e0b134349/chromadb/segment/impl/metadata/sqlite.py#L238-L247

useful note! thank you @Alexandre27 cc @HammadB

@jeffchuber and @HammadB, you did a great job with the abstraction layer on top of the DB (sqlite). Would you be interested in a pgsql impl?

@tazarov single-node Chroma is intended to be very lightweight which is why we chose sqlite (for now). distributed chroma, which we are working out, will have a lot more firepower. I think we are reticent to make the API surface too large including adding more db impls. Is there a specific reason you think it may be good to add it?

Only in the context of scaling it out :). Noticed a few community questions regarding scaling the Chroma, so I thought this might be a good fit, but I get your point about a single node needing to be lightweight.
From where I stand, such additional DB impls don't even need to be part of the core but rather drop-ins (e.g. via deps install + config)

@tazarov we think that postgres would have some improvement, yes, however we would run into other limitations and would increase the support burden on the team. For applications where speed and scale are important, those should use distributed Chroma (which people will be able to run themselves and/or run locally).

Addressed in #959


Mutation table Spanner impl

Requires grpc v1.28.0 which clashes with etcd

Blocked on https://github.com/googleapis/google-cloud-go/issues/2195

Thanks for your comments!
As a high level observation, there are parts of this API that I'm less than 100% pleased with, but because they are part of the storage layer API contract, I can't change them here.
The objective of this PR is to get a spanner implementation working. Once that's in place, we can go back and do a better review of the API contracts as a separate work item.


Hide CDB Wishlist

Various would-be-nice for HIDE-CDB

[ ] cdb diff merge & show changes / reset change in editor
[ ] resize columns and save in props
[ ] add comment for each Flag
[ ] allow custom icon (tile) per sheet for display in navigation bar
[x] right click -> move to (separator) for fast moving of lines
[ ] improve search : search whole body & search if collapsed (generate "X results" tiny line)
[ ] Properties-in-Properties needs a bit of margin-left
[x] copy same cdb clipboard data on several lines
[x] add comment for a column
[x] fold/unfold groups and save in props
[x] using an Unique Identifier on a sub sheet (list) does not work (error on input) -- References to it could be displayed with contextual information (path)
[x] handle propagation of id renames / structural changes to prefabs (with resolve cache)
[x] allow copy/paste from sheets (multiline values)

allow custom icon (tile) per sheet for display in navigation bar
is already possible through custom CSS


Changed openapi ID regexp pattern according to validator

openapi validator needs ID regexp pattern without "/" at the start and at the end.

[x] depends on: https://github.com/ManageIQ/manageiq-api-common/pull/79

cc @abellotti

@abellotti please review

LGTM!! Thanks @slemrmartin for this fix. 👍

@bdunne please merge


fix: Generic static This.

Attempt to fix https://github.com/Vincit/objection.js/issues/2531.
Should probably be extended to be used in all static This inferences.

I am not sure what additional context to give apart from the issue #2531 that is already linked.
It seems like this fix is/was needed in order to have the changes from #2399 (which has been reverted).

This looks reasonable. @max-kahnt-keylight could you follow up with another PR to use the same approach in all static this inferences?

💚 Very much appreciated that you are getting back to this even though the issue currently doesn't haunt me personally.
I created https://github.com/Vincit/objection.js/pull/2700 now. I am not sure if I will be able to test it reasonably and push its finalization, but I think it definitely makes sense to have this in all such places 👍🏼


Solr instance auto restarting in solr cloud mode

Hi,
I am running solr cloud with 6 solr instances having version solr5.2.1  and 3 zookeeper (3.4.7)
I have 2 questions regarding solr cloud :

How can i run solr cloud on port 80 smooothly, i have tried to run it but when i restart it gives me some exception , after doing some work  i found that " ps aux | grep solr"  its showing me the - -DSTOP.PORT= -920 , -920 port is nothing actually it was picking from script -1000 on solr port

e.g.  -Djetty.port=8983 -DSTOP.PORT=7983
anyone help me how to fix and start solr cloud on port 80.

I have found some weird problem, every morning betweem 3 to 3:30 am my solr instance restarted automatically even no traffic pointed on them, no indexing is running on them.
solr : 16G RAM and 10G heap size.
Zookeeper servers are fine.

solr.log :
INFO  - 2016-05-31 03:38:07.584; [   ] org.eclipse.jetty.util.log.Log; Logging initialized @261ms
INFO  - 2016-05-31 03:38:07.732; [   ] org.eclipse.jetty.server.Server; jetty-9.2.10.v20150310
WARN  - 2016-05-31 03:38:07.750; [   ] org.eclipse.jetty.server.handler.RequestLogHandler; !RequestLog
INFO  - 2016-05-31 03:38:07.753; [   ] org.eclipse.jetty.server.NCSARequestLog; Opened /mnt/vol1/solr-5.2.1/server/logs/request.log
INFO  - 2016-05-31 03:38:07.755; [   ] org.eclipse.jetty.deploy.providers.ScanningAppProvider; Deployment monitor [file:/mnt/vol1/solr-5.2.1/server/contexts/] at interval 0
INFO  - 2016-05-31 03:38:08.066; [   ] org.eclipse.jetty.webapp.StandardDescriptorProcessor; NO JSP Support for /solr, did not find org.apache.jasper.servlet.JspServlet
WARN  - 2016-05-31 03:38:08.085; [   ] org.eclipse.jetty.security.ConstraintSecurityHandler; ServletContext@o.e.j.w.WebAppContext@55f3ddb1{/solr,file:/mnt/vol1/solr-5.2.1/server/solr-webapp/webapp/,STARTING}{/solr.war} has uncovered http methods for path: /
INFO  - 2016-05-31 03:38:08.105; [   ] org.apache.solr.servlet.SolrDispatchFilter; SolrDispatchFilter.init()WebAppClassLoader=1047503754@3e6fa38a
INFO  - 2016-05-31 03:38:08.117; [   ] org.apache.solr.core.SolrResourceLoader; JNDI not configured for solr (NoInitialContextEx)
INFO  - 2016-05-31 03:38:08.117; [   ] org.apache.solr.core.SolrResourceLoader; using system property solr.solr.home: /home/test/solr/server/solr
gc log:
OpenJDK 64-Bit Server VM (25.77-b03) for linux-amd64 JRE (1.8.0_77-b03), built on Mar 25 2016 00:42:26 by "mockbuild" with gcc 4.4.7 20120313 (Red Hat 4.4.7-16)
Memory: 4k page, physical 16333628k(13548580k free), swap 2097148k(2097148k free)
CommandLine flags: -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+CMSScavengeBeforeRemark -XX:ConcGCThreads=4 -XX:InitialHeapSize=10737418240 -XX:MaxHeapSize=10737418240 -XX:MaxTenuringThreshold=8 -XX:NewRatio=3 -XX:OldPLABSize=16 -XX:ParallelGCThreads=4 -XX:+ParallelRefProcEnabled -XX:PretenureSizeThreshold=67108864 -XX:+PrintGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:ThreadStackSize=256 -XX:+UseCMSInitiatingOccupancyOnly -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
2016-05-31T03:38:07.586+0530: 0.265: Total time for which application threads were stopped: 0.0002140 seconds, Stopping threads took: 0.0000460 seconds
2016-05-31T03:38:07.741+0530: 0.420: Total time for which application threads were stopped: 0.0001655 seconds, Stopping threads took: 0.0000257 seconds
2016-05-31T03:38:07.789+0530: 0.468: Total time for which application threads were stopped: 0.0002245 seconds, Stopping threads took: 0.0000462 seconds
2016-05-31T03:38:07.800+0530: 0.479: Total time for which application threads were stopped: 0.0002235 seconds, Stopping threads took: 0.0000525 seconds

Hi, this doesn't seem to be related to SolrNet, or is it?

Agree with you , posted in the wrong topic


Links do not fit on a mobile

On a narrow screen the links: web, blog and old - should be vertical not horizontal.

Hi @xparagon i would love to take a look at this

Thanks @mirsahib - but no Pull request so I changed to this:


Add paginated fetching to withdraw link table

We had a severe bug in the Withdraw Extension that prevented us from using the UI. In our app, we handle many different users, and each user will eventually receive an LNURLw link. With thousands of links in the database, it was not very efficient to load all the links simultaneously. Many times we received a "502 Bad Gateway" error because the response took too long. This caused a significant chain reaction because our LNBits instance was completely down afterward, requiring us to reset with a backup to get things running again.
By implementing a paginated loading of the table, this issue would not occur anymore, and the Withdraw plugin would load much faster initially as well.

hey, can you rebase and solve conflicts, there is now linting, ci and tests in the repo
you can pull latest main and run
poetry install
npm install

and then run
make

for formatting and
poetry run pytest
``` for tests

Issue is poetry is not working in my environment. I have already noted this in another issue: https://github.com/lnbits/lnbits/issues/2568
For the current project I get the following error:
Installing dependencies from lock file

Package operations: 69 installs, 0 updates, 0 removals

  - Installing coincurve (18.0.0): Failed

  ChefBuildError

  Backend subprocess exited when trying to invoke build_wheel

  Traceback (most recent call last):
    File "/usr/local/Cellar/poetry/1.8.3_2/libexec/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 373, in <module>
      main()
    File "/usr/local/Cellar/poetry/1.8.3_2/libexec/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 357, in main
      json_out["return_val"] = hook(**hook_input["kwargs"])
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/Cellar/poetry/1.8.3_2/libexec/lib/python3.12/site-packages/pyproject_hooks/_in_process/_in_process.py", line 271, in build_wheel
      return _build_backend().build_wheel(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 415, in build_wheel
      return self._build_with_temp_dir(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 397, in _build_with_temp_dir
      self.run_setup()
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 497, in run_setup
      super().run_setup(setup_script=setup_script)
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/build_meta.py", line 313, in run_setup
      exec(code, locals())
    File "<string>", line 266, in <module>
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/__init__.py", line 103, in setup
      return distutils.core.setup(**attrs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 171, in setup
      ok = dist.parse_command_line()
           ^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 478, in parse_command_line
      args = self._parse_command_opts(parser, args)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/dist.py", line 876, in _parse_command_opts
      nargs = _Distribution._parse_command_opts(self, parser, args)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/private/var/folders/lz/t1dpdjjj5718xrcnhm_nnyv00000gn/T/tmp_hlk3_gx/.venv/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 543, in _parse_command_opts
      if not issubclass(cmd_class, Command):
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  TypeError: issubclass() arg 1 must be a class

  at /usr/local/Cellar/poetry/1.8.3_2/libexec/lib/python3.12/site-packages/poetry/installation/chef.py:164 in _prepare
      160│
      161│                 error = ChefBuildError("\n\n".join(message_parts))
      162│
      163│             if error is not None:
    → 164│                 raise error from None
      165│
      166│             return path
      167│
      168│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:

Note: This error originates from the build backend, and is likely not a problem with poetry but with coincurve (18.0.0) not supporting PEP 517 builds. You can verify this by running 'pip wheel --no-cache-dir --use-pep517 "coincurve (==18.0.0)"'.

Any other idea how I could execute the linter and check if everything is formatted?

Have moved this to a new PR (https://github.com/lnbits/withdraw/pull/41) in order to get the lint checks in the PR. Still cannot build with poetry but with the lints from the PR I was able to fix the issue.


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d33ix2z64ma54m
Region: us-east-1
Step: Domain activation
Status: Failed
Note:
Issue/question
I am trying to add a custom domain managed by a third-party DNS provider. I have followed all the steps in the documentation but in the last step (the domain activation) is throwing an error. The thing is that the the third partu DNS provider takes around 2 days in creating the registration in their DNS, and when I retry it is still not successful. Is there anything that I have to do besides that? Should the DNS provider take less time so it can be successful? I would highly appreciate it.
Error message
One or more aliases specified for the distribution includes an incorrectly configured DNS record that points to another CloudFront distribution. You must update the DNS record to correct the problem. For more information, see https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-restrictions

That error message sounds like you (or someone) had this domain configured with Cloudfront. Does https://github.com/aws-amplify/amplify-console/issues/512#issuecomment-639892355 help?

Yes, that was very helpful.  Thank you very much and I do apologize for the long answer. The third party provider took a while and a was not sure. Thanks again for the quick reply!


pass log_level in HostData

Feature or Problem
This passes log_level to providers. See https://github.com/wasmCloud/weld/pull/148 for context
Related Issues
https://github.com/wasmCloud/weld/pull/148
Release Information
v0.63.0, since this is technically a breaking change. See below.
Consumer Impact
See the testing section of https://github.com/wasmCloud/weld/pull/148. Notice that after this change, RUST_LOG is ignored.
Note: I find it odd that the source field is called structured_log_level, and that Elixir logging is controlled via mix environment without structured logging enabled. I propose we make this a breaking change: rename this field to just log_level, proxy it through to providers, and also respect it when structured logging is not enabled
Testing
Manual Verification
See testing section of https://github.com/wasmCloud/weld/pull/148

After talking with @thomastaylor312, he agreed that renaming to log_level for elixir logs for consistency makes sense. Does anyone disagree? He also proposed that we remain backwards-compatible for a time™ and continue to parse the old env var name, as well as the new name (WASMCLOUD_LOG_LEVEL)

@connorsmith256 I like the idea of using log_level and the backwards compatible logic, just output a warning if people use the old one so that they get a notice to update


proof of concept for streaming messages in nlu training

**DRAFT FOR DISCUSSION PURPOSES **:

proof of concept for #8407
The implementation is pretty rough and just to theoretically test some of the bigger risks (such as, could diet be trained from a stream of messages)
implemented for CountVectorsFeaturizer, Spacy Featurizer, CRF, and DietClassifier
main training data object (with unfeaturized messages) stays in memory right now, as so many parts of the codebase use it that way
features can be successively built and stored on disc (right now just pickling a list of features per message, ultimately a safer and more sophisticated structure should be chosen)
messages can be joined with features on the fly and consumed as a Generator. For the matching I am using a fingerprint of the message that is just based on the following attributes of the message: text, intent, response, action name, action text, and intent response key. I think this way the fingerprint would be invariant across processing steps and across runs.
keras.Sequence can be used to hide the generator, but there are probably better abstractions available. Possibly also some multiprocessing here to fill a batch queue in a second thread or so.
Chunking directories are just based on the component name right now, and if some component requests a message stream, the latest chunking dir will be used
tested with memory profiling on multiwoz, for details see below
shuffling is implemented by: using smallish chunks and randomizing chunk reading order + reading multiple chunks at once and then shuffling the acumulated again

notes

I think the methods of many components could really benefit from taking a more message centric perspective. So many of components' methods operate on collections of messages. That makes the functions more complex, harder to understand, and harder to reuse. Was able to throw out a lot of code in the CountVectorFeaturizer by focusing more on messages
RasaModelData seems a bit like a parallel world to the TrainingData class. I think there are many parallel implementations of the same logic on these classes, such as splitting training data according to some labels. I am not sure this intermediate RasaModelData class is really necessary. It seems all that's needed is some logic to arrange messages in a certain way and to turn a bunch of them into tensors.

I ran some mem profilings on multiwoz dataset with roughly 55k nlu sentences. I compared the current main branch with my branch here. It saves memory all around, but the effect is very much dependent on the specific component. It's the least pronounced for the crf in this case as that model is building up the entire dataset internally itself.
config
I think most of it pretty standard, added the crf features here to get text_dense_features from the spacy vectors in
language: en

pipeline:
  - name: "SpacyNLP"
  - name: "SpacyTokenizer"
  - name: "SpacyFeaturizer"
  - name: "CountVectorsFeaturizer"
  - name: "CRFEntityExtractor"
    max_iterations: 1
    features: [
    ["pos", "pos2"],
    [
      "bias",
      "prefix5",
      "prefix2",
      "suffix5",
      "suffix3",
      "suffix2",
      "pos",
      "pos2",
      "digit",
      "text_dense_features"
    ],
    ["pos", "pos2"],
    ]
    L1_c: 0.01,
    L2_c: 0.05
  - name: "DIETClassifier"
    entity_recognition: False
    epochs: 1
    batch_size: 64

Results
main

this branch

Memory:

For each model jumps to about 2.5 GB when loading spacy model and tokenizing all the messages
During crf data accumulation:

main: jumps and hovers at around 5.5 to 6GB
this branch: slow increase from 2.5 to about 4.5GB

During crf training:

main: peak memory usage at about 7.5 GB
this branch: peak memory usage at about 6 GB

During Diet training

main: constant memory consumption of around 4.3 GB
this branch: memory consumption of around 2-2.2 GB

Time:

main: ~1600s
this branch: ~1850s
Maybe a minute of that goes to CRF training or before that, both of them end at similar times at around 1000s
The rest seems to be attributable to DIET training
I think this is mostly expected as 1) the current implementation for the keras sequence is very rough, and 2) caching on disc is fundamentally a trade off between memory and time

How about showing this to Daksh / Vova? I'd be interested in their feedback. I think your prototype seems very promising! 💯

I'd be interested in their thoughts aswell

With splitting (reusing) the generators inside the crf the consumption is again 500mb lower. Timing isn't really comparable as I was doing a lot of other stuff while profiling.

How does changing the MSG_PER_CHUNK affect the memory usage?

How does changing the MSG_PER_CHUNK affect the memory usage?

The larger the chunk the more memory is used. At the extreme you could have a chunk that is the size of the dataset even for a big dataset.
The features in this particular setup for 55k messages are about 2GB in memory. So 512 messages are about 20MB.
For the shuffling I am currently using 3 random chunks. So that would make 60mb when using shuffling.
Both the size and number of chunks when shuffling is adjustable.


deconstructing computers deletes their container contents

Description
id computer will delete id cards

Will be fixed by #32308

real


Play button not working, forward and backward working fine

I was getting an infinite loop of browsers with a 404 code saying the requested resource is not found. I changed the Spotify polling interval to 0 which solved that issue in the short term, but this occurs again any time I hit the shuffle this occurs again in addition to the play/ pause not working, but skip works fine.

I havent heard this issue before.
What AudioBand version are you on? (go in Settings -> About (top right) and it should show there.
Do you have Spotify Premium?

@NiP-24

I ended up removing it and trying on a different computer, and it worked fine.
Still trying to replicate the issue, but it seems to only occur on that specific machine.

From: Senne Van Rompaey @.>
Sent: Monday, May 30, 2022 8:30:09 AM
To: AudioBand/AudioBand @.>
Cc: Nick Palya @.>; Mention @.>
Subject: [EXTERNAL] Re: [AudioBand/AudioBand] Play button not working, forward and backward working fine (Issue #66)
@NiP-24https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNiP-24&data=05|01|nipalya%40crimson.ua.edu|a64c4967bc50468100df08da4240850c|2a00728ef0d040b4a4e8ce433f3fbca7|0|0|637895142127275113|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=iOfscyje3nDNaLhlxViIjpgCAnOZDkSzuGpF8ET3v5M%3D&reserved=0 any updates?
—
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAudioBand%2FAudioBand%2Fissues%2F66%23issuecomment-1141163298&data=05|01|nipalya%40crimson.ua.edu|a64c4967bc50468100df08da4240850c|2a00728ef0d040b4a4e8ce433f3fbca7|0|0|637895142127275113|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=eANHhLQX5qwE2IYdCnCJ2TDEicgiS9DeUIEkbt%2F%2FYEY%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWMLBGYWSAJATKRFF2FG323VMS7GDANCNFSM5WJVUW5Q&data=05|01|nipalya%40crimson.ua.edu|a64c4967bc50468100df08da4240850c|2a00728ef0d040b4a4e8ce433f3fbca7|0|0|637895142127275113|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HYJ8Myrz6T6dGzSf7jNB4R5X8pcIJd4S7zqEaunEJAM%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

odd, Im going to close this due to unable to recreate and possibly an external app causes the bug, if you do ever get the error again feel free to re-open or make a new issue!


Windows build failing due to bin/ in start and prod section

Fix windows build by using cross-env to support cross environment path separators

little change :)


Update Certificate Authority

The certificate needs these authorities in order to verify against root ca 66. See https://crl.gds.disa.mil/.

added intermediary and issuers for ca 66

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 647dc31b519c59a64ffb9688973bd3ca904e1e44