Add How To Use LLMs For Speaker Diarization(using gpt-4 and whisper API)

Hi,
I hope this message finds you well. I have made valuable contributions to the project by adding a new notebook titled 'How To Use LLMs For Speaker Diarization'. This notebook is designed to be a comprehensive guide for Conversational Speaker Diarization using OpenAI AI Language Models(gpt-4) and OpenAI Whisper.

Hi @ted-at-openai,
Would you be able to review this PR please? =)

Hi @ElmiraGhorbani! Thank you for your pull request and for contributing to the cookbook.
After reviewing your changes, we have decided not to merge them at this time. Although we appreciate your time and effort, these notebooks do not fully align with the cookbook's existing content. Here are some high-level thoughts:

Using GPT-4 to split a transcript into speakers is a good idea. However, it may not require a whole notebook, and calling it diarization is a bit misleading.
The other notebook in your commit, "How to summarize long text inputs," appears incomplete. The topic is relevant and important. To make a more robust submission, you could provide additional information about your approach, why it is effective, how it compares to other methods, and include a more guided walkthrough.

Thank you again for your time and effort!


[Feature]: Support tc39 "import attributes"

🚀 Feature Proposal
I've seen from previous issues that Jest support for import assertions was already added when the proposal was at tc39 stage 3, but that this was reverted/removed again in Feb 2023 as the proposal had been demoted back to stage 2.
Right after this, in March 2023 (more than 1 year back);  the proposal went back to stage 3 with a few design changes (keyword assert changed to with), and the of the name of the proposed feature has changed from "import assertions" to "import attributes".
Old proposal
New proposal
Import attributes are now supported in:

TypeScript (since v5.3).
Bundlers (Tested: WebPack - requires some configuration).
Certain browsers (latest) natively (Tested: chromium).
NodeJS LTS natively (experimental) (Tested 20.11.1).

Our developer team could have written future-proof ECMAScript code, utilizing this upcoming feature - we currently only need it to work with TypeScript and WebPack; but unfortunately it breaks the Jest tests.
When will you add support for import attributes?
Jest is currently our only obstacle...
Motivation
Jest should support the complete ECMAScript module import specs
Example
No response
Pitch
Jest should support the complete ECMAScript module import specs

How are they "not supported"? What breaks? https://github.com/jestjs/jest/issues/14345 seems to suggest that the user is already able to use them since tests go through babel.
Does this work? Are you using the native ESM support?
import './file.json' with {type: "json"}?

@fregante: The import with the "import attribute" is in a file that's currently not having any tests.
The test run currently fails when generating coverage for untested files.
This is the error message I get:
STACK: SyntaxError: /my-project/src/target.ts: Support for the experimental syntax 'importAttributes' isn't currently enabled (1:45):

> 1 | import settings from "./settings.json" with { type: "json" };

Add @babel/plugin-syntax-import-attributes (https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-attributes) to the 'plugins' section of your Babel config to enable parsing.

If you already added the plugin for this syntax to your config, it's possible that your config isn't being loaded.
You can re-run Babel with the BABEL_SHOW_CONFIG_FOR environment variable to show the loaded configuration:
        npx cross-env BABEL_SHOW_CONFIG_FOR=/my-project/src/target.ts <your build command>
See https://babeljs.io/docs/configuration#print-effective-configs for more info.

    at constructor (/my-project/node_modules/@babel/parser/lib/index.js:353:19)
    at Parser.raise (/my-project/node_modules/@babel/parser/lib/index.js:3277:19)
    at Parser.expectPlugin (/my-project/node_modules/@babel/parser/lib/index.js:3305:16)
    at Parser.expectImportAttributesPlugin (/my-project/node_modules/@babel/parser/lib/index.js:10729:12)
    at Parser.maybeParseImportAttributes (/my-project/node_modules/@babel/parser/lib/index.js:13792:16)
    at Parser.parseImportSourceAndAttributes (/my-project/node_modules/@babel/parser/lib/index.js:13702:10)
    at Parser.parseImportSpecifiersAndAfter (/my-project/node_modules/@babel/parser/lib/index.js:13696:17)
    at Parser.parseImport (/my-project/node_modules/@babel/parser/lib/index.js:13687:17)
    at Parser.parseStatementContent (/my-project/node_modules/@babel/parser/lib/index.js:12347:27)
    at Parser.parseStatementLike (/my-project/node_modules/@babel/parser/lib/index.js:12239:17)
    at Parser.parseModuleItem (/my-project/node_modules/@babel/parser/lib/index.js:12216:17)
    at Parser.parseBlockOrModuleBlockBody (/my-project/node_modules/@babel/parser/lib/index.js:12796:36)
    at Parser.parseBlockBody (/my-project/node_modules/@babel/parser/lib/index.js:12789:10)
    at Parser.parseProgram (/my-project/node_modules/@babel/parser/lib/index.js:12116:10)
    at Parser.parseTopLevel (/my-project/node_modules/@babel/parser/lib/index.js:12106:25)
    at Parser.parse (/my-project/node_modules/@babel/parser/lib/index.js:13905:10)
    at parse (/my-project/node_modules/@babel/parser/lib/index.js:13947:38)
    at parser (/my-project/node_modules/@babel/core/lib/parser/index.js:41:34)
    at parser.next (<anonymous>)
    at normalizeFile (/my-project/node_modules/@babel/core/lib/transformation/normalize-file.js:64:37)
    at normalizeFile.next (<anonymous>)
    at run (/my-project/node_modules/@babel/core/lib/transformation/index.js:21:50)
    at run.next (<anonymous>)
    at transform (/my-project/node_modules/@babel/core/lib/transform.js:22:33)
    at transform.next (<anonymous>)
    at evaluateSync (/my-project/node_modules/gensync/index.js:251:28)
    at sync (/my-project/node_modules/gensync/index.js:89:14)
    at stopHiding - secret - don't use this - v1 (/my-project/node_modules/@babel/core/lib/errors/rewrite-stack-trace.js:47:12)
    at transformSync (/my-project/node_modules/@babel/core/lib/transform.js:42:76)
    at ScriptTransformer._instrumentFile (/my-project/node_modules/@jest/transform/build/ScriptTransformer.js:389:46)
    at ScriptTransformer._buildTransformResult (/my-project/node_modules/@jest/transform/build/ScriptTransformer.js:491:33)
    at ScriptTransformer.transformSourceAsync (/my-project/node_modules/@jest/transform/build/ScriptTransformer.js:608:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async generateEmptyCoverage (/my-project/node_modules/@jest/reporters/build/generateEmptyCoverage.js:127:20)

Yep, that's a babel error, not a Jest/Node one. Just follow the instructions it provides.

I'm not using babel, and my project has no (direct) dependencies to any babel packages.
I relate only to the jest packages; -the babel packages are dependencies of jest packages.
As stated by jest in the information written to the terminal along with the error message (see complete content below):

"Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration."

I don't use babel, and don't have any babel configuration file; and I think I should not have to add one just to make jest work with import attributes. It looks like things would have worked if the @babel/plugin-syntax-import-attributes was added to the babel configuration (see info below).
Proposal: The @babel/plugin-syntax-import-attributes plugin should be included in Jests babel configuration by default to ensure coverage reporting works even for code using "import attributes".
Additional info: I have now written a test for a module that uses "import attributes".
The test execution actually works without no error; but when adding the --coverage parameter the error is thrown.
This is the complete informational content written to the terminal when the test fails (I did not include everything in my previous post).
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when
Jest is not configured to support such syntax.

Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

By default "node_modules" folder is ignored by transformers.

Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

Add @babel/plugin-syntax-import-attributes (https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-attributes) to the 'plugins' section of your Babel config to enable parsing.

    If you already added the plugin for this syntax to your config, it's possible that your config isn't being loaded.
    You can re-run Babel with the BABEL_SHOW_CONFIG_FOR environment variable to show the loaded configuration:
        npx cross-env BABEL_SHOW_CONFIG_FOR=D:\_Git\Adra.Reference.App\src\Adra.Reference.App\src\climate\climate-environment-loader.ts <your build command>
    See https://babeljs.io/docs/configuration#print-effective-configs for more info.

I have the same problem. Jest works perfectly with import assert. However, with coverage, the error occurs. I'm using ts-jest.
NODE_OPTIONS=--experimental-vm-modules jest --coverage
SyntaxError: /swagger.ts: Support for the experimental syntax 'importAttributes' isn't currently enabled (1:47):
> 1 | import packageJson from './package.json' with { type: 'json' };

@josundt;
Even using ts-jest, I see that the use of babel is fixed in the source.

@fregante What's happening here?

Jest uses https://github.com/nicolo-ribaudo/babel-preset-current-node-syntax to know which Babel plugins to enable. If somebody can submit a PR to that repo for import attributes, I can release a new version.

I just filed https://github.com/nicolo-ribaudo/babel-preset-current-node-syntax/issues/9 which I guess is pretty much the issue equivalent of what @nicolo-ribaudo requested above 😀

I published a new minor version of the Babel plugin, this should work now.

Running into a similar problem, but we use the @babel/plugin-syntax-import-assertions plugin.
What is interesting to me, is that if I configure the coverage to not target where to collect (removing collectCoverageFrom) it seems to collect on only the files jest touched when it executed. Since the jest runner tranformed them, it collects properly. It is only the files that jest didn't touch that cause that cause the failure.
So my hack workaround is to not specify collectCoverageFrom (resulting in artificially high metrics)
@nicolo-ribaudo does your version to the attributes plugin have to be applied to assertions? How do you get babel to use your version as part of the coverage transform? Just yarn adding and getting your new minor version didn't seem to work.

Make sure to dedupe afterwards so Jest picks up the correct version of the preset

Make sure to dedupe afterwards so Jest picks up the correct version of the preset

This is cool to know, and it did indicate it did it -- but it still fails after jest has executed when attempting to collect coverage on files that jest didn't specifically transform. My current understanding is that when jest runs it will use my transform to apply the .babelrc that I have defined, and everything works. But when code coverage has to run and it hits fits that jest didn't transform, that however it is attempting to transform there does not use the transform I have defined and is relying on something else that uses this preset?
Right now my devDependencies look like this:
    "devDependencies": {         "@babel/core": "^7.22.5",         "@babel/eslint-parser": "^7.22.5",         "@babel/plugin-syntax-import-assertions": "^7.24.7",         "@babel/plugin-syntax-import-attributes": "^7.24.7",         "@babel/plugin-transform-runtime": "^7.24.7",         "@babel/preset-env": "^7.25.3",         "@babel/runtime": "^7.25.0",         "babel-jest": "^29.6.1",         "babel-plugin-transform-amd-to-commonjs": "^1.6.0",         "babel-plugin-transform-import-meta": "^2.2.1",         "babel-preset-current-node-syntax": "^1.1.0",         "cross-env": "^7.0.3",         "eslint": "^8.42.0",         "eslint-config-airbnb-base": "^15.0.0",         "eslint-config-prettier": "^8.8.0",         "eslint-plugin-import": "^2.27.5",         "eslint-plugin-jest": "^27.2.3",         "eslint-plugin-n": "^16.3.1",         "eslint-plugin-only-warn": "^1.1.0",         "eslint-plugin-prettier": "^4.2.1",         "jest": "^29.7.0",         "jest-junit": "^16.0.0",         "prettier": "^2.8.8"     },
And I have run dedupe which did indicate it replaced the old babel-preset-current-node-syntax with this new one that should include the fix. Perhaps I am missing obvious?

Workaround until this is properly fixed:
Replace:
import defs from './file.json' with {type: 'json'}

With:
const defs = (await import('./file.json', { with: { type: 'json' } })).default;


[Bug]:  Doc's : On entering an search keyword and clicking on "Enter" key the user is lead Appsmith Introduction page

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When the user navigates to global search, enters any widget name as a keyword, and clicks on the "Enter" key the user navigated to the Appsmith introduction page rather than to the respective page details the
Steps To Reproduce

Navigate to Application
Click on Global search
Add  widget name as keyword
click on "Enter" from the keyboard
and observe

Environment
Production
Version
Cloud

This issue has now been resolved


add Unitary Fund

Launch Blog inspired by Helium Grants: https://medium.com/@wjzeng/the-unitary-fund-get-2-000-for-your-open-source-quantum-computing-project-d4b4c76ba177

🎉


Testnet 4.1: Can't sync, cyclic reboots

Description
Node can't sync. The status displays 1 block and after about 30 minutes the docker container restarts

Coda client status
Coda daemon status
-----------------------------------

Global number of accounts:       1026
Block height:                    1
Max observed block length:       218
Local uptime:                    13m19s
Ledger Merkle root:              jxqupp5oGcqRuEFGaq9oTtJYBdMdtgHodLoxuMk7xt4m8gBUnNx
Protocol state hash:             3NLVs8hfDhTvzEcjXurQdGKS1ykj6GcYKS1gXdHcNM1MorkbBEBX
Chain id:                        ef95774fb2ed657da61bfc40a8a148a9c9a202476b539aaf915e6cd81d1ef268
Git SHA-1:                       [DIRTY]757342b6cef510f13cb5ad2fbad97518d6df45df
Configuration directory:         /root/.coda-config
Peers:                           55 (<IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:50054 <IP_ADDRESS>:10505 <IP_ADDRESS>:8302 <IP_ADDRESS>:10504 <IP_ADDRESS>:10509 <IP_ADDRESS>:10511 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:59942 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10513 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10503 <IP_ADDRESS>:8302 <IP_ADDRESS>:10401 <IP_ADDRESS>:10501 <IP_ADDRESS>:10512 <IP_ADDRESS>:10515 <IP_ADDRESS>:8302 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:10514 <IP_ADDRESS>:48956 <IP_ADDRESS>:10506 <IP_ADDRESS>:8302 <IP_ADDRESS>:10502 <IP_ADDRESS>:8302 <IP_ADDRESS>:60254 <IP_ADDRESS>:8302 <IP_ADDRESS>:10516 <IP_ADDRESS>:10508 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:8302 <IP_ADDRESS>:59064 <IP_ADDRESS>:10507 <IP_ADDRESS>:10001 <IP_ADDRESS>:8302 <IP_ADDRESS>:56702 <IP_ADDRESS>:10510)
User_commands sent:              0
SNARK worker:                    None
SNARK work fee:                  25000000
Sync status:                     Catchup
Block producers running:         1 (B62qp6PvbR69ip9a1ZRy47ryGqVSWVrWJ19fhPVDJBZ6x2S8AKyL5Lc)
Best tip consensus time:         epoch=0, slot=0
Next block will be produced in:  in 3.037h
Consensus time now:              epoch=0, slot=690
Consensus mechanism:             proof_of_stake
Consensus configuration:
        Delta:                     0
        k:                         290
        Slots per epoch:           7140
        Slot duration:             3m
        Epoch duration:            14d21h
        Genesis state timestamp:   2020-11-18 07:11:20.000000Z
        Acceptable network delay:  3m

Addresses and ports:
        External IP:    <IP_ADDRESS>
        Bind IP:        <IP_ADDRESS>
        Libp2p PeerID:  12D3KooWNnFoeFFRRD7cTC5iegyeM3AobSPK3RUtob1WoA7pBZwn
        Libp2p port:    8302
        Client port:    8301

Environment
Git SHA-1: [DIRTY]757342b6cef510f13cb5ad2fbad97518d6df45df
Host OS: Ubuntu 20.04
Using containerization: docker
CPU: i7 9500
RAM: 16 GB

Steps to reproduce

Forwarded ports on my router: 8302, 8303\TCP
Run docker container

cd; docker run --name mina -d \
--restart always \
-p 8301-8305:8301-8305 \
-p <IP_ADDRESS>:3085:3085 \
-v $(pwd)/keys:/root/keys:ro \
-v $(pwd)/coda-config:/root/.coda-config \
-v $(pwd)/peers.txt:/root/peers.txt \
--env CODA_PRIVKEY_PASS='12345' \
minaprotocol/mina-daemon-baked:4.1-turbo-pickles-mina757342b-auto811bf26 daemon \
-block-producer-key /root/keys/my-wallet \
-peer-list-file /root/peers.txt \
-insecure-rest-server \
-log-level Info

LOGS
https://drive.google.com/drive/folders/1A-lSR-FVeG2mNwfZH61wl0JfIBXTLtoj?usp=sharing

Same issue without docker
LOGS
https://drive.google.com/file/d/1LD-k3u4MBYmW96UMXggUX9KNTL6bgn_7/view?usp=sharing
https://drive.google.com/file/d/1u1b4ehC06UAaHs1nHTgz87KMpUvlaUAp/view?usp=sharing

Also seeing a lot of RPC call error for "get_transition_chain" so it seemingly can't get what it needs

If this is helpful ^^

Likely not the cause but seeing a large amount of gossiped snark work, which is rejected. Not sure if this is detrimental to the performance of the node during catchup?
Rejecting gossiped snark work $stmt, statement not referenced

Suspect this was already fixed in the new version

Thanks @c29r3 for reporting this!  This should be fixed in the latest version.  If you see this again on the latest please reopen the issue so investigate.  Much appreciated!


Implemented strftime() and time() Starlark functions

Codecov Report

Merging #3 into master will increase coverage by 1.45%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
+ Coverage   78.56%   80.02%   +1.45%
==========================================
  Files           9       10       +1
  Lines        1185      881     -304
==========================================
- Hits          931      705     -226
+ Misses        201      122      -79
- Partials       53       54       +1

Impacted Files
Coverage Δ

generator/blueprint/funcs.go
77.77% <77.77%> (ø)

generator/blueprint/starlark.go
78.88% <100.00%> (+1.89%)
:arrow_up:

gitgetter/getter.go
80.95% <0.00%> (-1.85%)
:arrow_down:

markup/lex.go
96.13% <0.00%> (-1.05%)
:arrow_down:

markup/parser.go
78.86% <0.00%> (+0.54%)
:arrow_up:

gitgetter/url.go
84.37% <0.00%> (+0.62%)
:arrow_up:

internal/manifest/generator.go
82.85% <0.00%> (+1.66%)
:arrow_up:

generator/blueprint/parser.go
69.59% <0.00%> (+2.45%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dfaa89e...540b73e. Read the comment docs.


improved docs

This is not an improvement. Suspect that this is related to trying to game the system for Hacktoberfest?


Pending claimable gfpay

Hi. I have pending claimable token but i cant click on claim button. Please help

@bubucakcak99 Thanks for posting the issue.
Your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support :Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

@bubucakcak99
That's the browser glitch.
Try refreshing the page. If it doesn't help, close this tab, open new browser tab, and navigate to https://albedo.link/


0.6.9 release

Codecov Report

Merging #3035 (90eee94) into main (31bd1f1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3035   +/-   ##
=======================================
  Coverage   81.95%   81.95%
=======================================
  Files          55       55
  Lines        6030     6030
=======================================
  Hits         4942     4942
  Misses       1088     1088

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Missing README.md

@ElvishJerricco you have moved package into subfolder but README.md stays in repo root and yet it's listed in servant-router/servant-router.cabal as extra-source-files.
I guess it's better be fixed.
BTW what was the motivation of that move?

Example warning from stack:
Warning: File listed in .stack-work/downloaded/kiJN60liVunn/servant-router/servant-router.cabal file does not exist: README.md

I should probably just put a README in that directory that points at the GitHub, since that's the only way you'll see the examples.
The move was because I wanted to distinguish the library package from the examples and from the Nix setup. Having the library be the root would have meant polluting it with all these other files. Pure cosmetic.


coreference_resolution：

when process data in preprocess_raw_data.py of the coreference_resolution in coreference_resolution:
raw = {d[0]: '\t'.join(d[1]) for d in raw}
seems should be:
raw = {d: '\t'.join(raw[d]) for d in raw}

I also encounter the same problem, looking forward to the authors' answer.

Thanks for pointing out the issue. Sorry that there exists some inconsistency in our processing codes.
We've fixed the problem according to your advice. Thanks!


just curious

any reason you are not using php-tmdb/laravel and algolia/algoliasearch-laravel
also it would be great if you can implement tmdb authentication

I think there is no reason to use the algoliasearch-laravel package if i use laravel scout :)
But the api package looks good and i'll write it on my todo list.
I don't have much experience with the tmdb api. Can I read the tmdb data from the user when he is authenticated? Possibly i can add this option with multiuser :)


Sass Error - excluding symbolic link index.js & lib\index.js

The sass installation has the following response:
C:\Dev>npm install sass
npm WARN excluding symbolic link index.js -> lib/sass.js
npm WARN excluding symbolic link lib\index.js -> sass.js
<EMAIL_ADDRESS>C:\Dev
`--<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No license field.
C:\Dev>npm install -g sass
npm WARN excluding symbolic link index.js -> lib/sass.js
npm WARN excluding symbolic link lib\index.js -> sass.js
C:\Users\Zoltán\AppData\Roaming\npm
`--<EMAIL_ADDRESS>After the installation I tried to check the version:
C:\Dev>sass -v
'sass' is not recognized as an internal or external command,
operable program or batch file.
Could you please advise?

C:\

I see your problem there.  Try wiping and installing Linux.
Also, #262

This also happens on my ubuntu machine it is not windows related ...


Error Message for Registering

Is your feature request related to a problem? Please describe.
When registering for the app. If the username is taken, the email is already used, and/or the password is not hard enough the registration will not be submitted. The loading button just resets to register. The server currently responses with a 400.
Describe the solution you'd like
Have a message appear on the screen telling the user which field they need to fix and why.
Describe alternatives you've considered
If multiple error messages cannot be displayed based on which field the user needs to fix. Then a blank message like "please check the username and password" would work as well.

PR78 closed this issue.


Add bypass superhosting pls

Can you add bypass https://www.superhosting.bg/ this ddos protection its very important. Thank you!

You dont need to bypass this
Check This Link!!!
Method: GET
https://check-host.net/check-report/75fe475k2e5

Solution: https://docs.python.org/kolm


ISSUE#23 : SEARCH PLAYLIST FEATURE

On clicking the song already in the playlist it scrolls down to that particular song and highlights it in green.

I have made the requested changes.

Merged in  5c33bf6


Add Tablestore VectorStore

This PR adds the TablestoreVectorStore to the list of VectorStores to be instrumented by LangChain

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.66%. Comparing base (25e1f1e) to head (7dc8c24).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1278      +/-   ##
==========================================
- Coverage   79.67%   79.66%   -0.02%
==========================================
  Files         201      201
  Lines       22173    22174       +1
  Branches     3519     3519
==========================================
- Hits        17667    17664       -3
- Misses       3356     3359       +3
- Partials     1150     1151       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Refactor] small improvements for grading instruction details component

Checklist

[x] I tested all changes and all related features with different users (student, tutor, editor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Client: I followed the coding and design guidelines.
[x] Client: I added multiple screenshots/screencasts of my UI changes
[x] Client: I translated all newly inserted strings into English and German.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.

Motivation and Context

This PR aims refactoring for grading-instruction-details-component. Currently, reset button for grading criteria title and grading instruction does not work if it is newly added by user. Because, I was comparing the backup exercise and the current exercise, so if the object is not part of backup exercise, reset did not work. To fix, I just initialize with default title and grading instruction if user wants to reset changes for newly added grading criteria or grading instruction. In addition, I added tooltip for reset/delete/plus button in the form.
I also changed some strings to keep consistency.
Description

Steps for Testing

P.S. To display the grading instruction in this form, you need to use the grading instruction as a feedback during the assessment at least once, probably we will provide this mode even if the grading instruction is not associated with the feedback. However, its not scope of this PR.

Log in to Artemis
Navigate to Course Administration
Create/Find exercise.
Go to edit view. Switch Grading Instructions.
Hover the buttons for grading instructions, you should see the tooltip.
Add new grading criterion/grading instruction, change something then click the reset button, it should display default text.
Change title for newly added grading criteria then click small reset button, it should display only 'Criterion Title' placeholder for input area.

Test Coverage

nothing changed.
Screenshots

Small suggestion: I would remove the word "here". It's unnecessary in my opinion and also isn't a part of the wording in the other buttons. The hover box would also get smaller and the design/wording would be consistent with the other buttons.

@canyelten ah sure... will do!!


Create a test for: heptio/contour

Details: https://github.com/heptio/contour

Moved on and no longer required


Middleware does not work for a filter

The problem is even deeper than i've described in the caption. Lets say i have this code:
const get = Picker.filter(function(req, res) {
  return req.method == 'GET';
});
const post = Picker.filter(function(req, res) {
  return req.method == 'POST';
});

// Hello there, you have no documentation provided about custom middleware, but it's ok, i can use google
const someMiddleware = (req, res, next) => {
  console.log('see this on any route, lol');
  next();
}

// i would use the middleware only for POST requests, so i suppose i should write this way:
post.middleware(someMiddleware);

// no, u didn't get it, i even expect the middleware is gonna be run only for this route: /api/items/
// just notice: why did u splited out the params from the req object? The Express does not, so it makes some mess, when i want to assign some URL/HEADER/BODY encoded parameters to some local variable, but the word "params" is already busy
post.route('/api/items/', callback);

// and lets say i want to provide some SEO markup for google/tweeter/blablaElse bots with this one:
const seo = Picker.filter(function(req, res) {
  return req.method == 'GET';
});

seo.get('/', seoCallback);

Ok, what do we have? Unexpected behavior for a normal mind flow:
'see this on any route, lol' - u will see this on every request, does not metter, did u come to '/', or '/api/items' with POST header. Filter also does not make effect on a decision to launch or not to launch a middleware. So all code above makes absolutly NO sense! You can not validate some header encoded parameter, with redirect on fail or next() on success, in middleware for specific route of a specific filter.

Don't get me wrong and I'm sorry if I'm too hard. But it peaces me off, when I'm understanding, that your code applies multer for EVERY ROUTE in the app!!!


Instructions details

Will this document be updated with more details about the enumeration privileges? May be step by step navigation be very useful here.

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

ID: db30a5c4-452c-02ae-b610-018e2bb042fb
Version Independent ID: 459aa1c1-fd5f-f6e1-3244-6bfbb2abd67f
Content: Add B2B collaboration users to Azure Active Directory without an invitation
Content Source: articles/active-directory/active-directory-b2b-add-user-without-invite.md
Service: active-directory
GitHub Login: @twooley
Microsoft Alias: twooley

@vaananth Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@vaananth Hello. This article has been significantly updated. Please review the updates and let us know if you have additional questions. I'm closing this issue for now. Thanks!

#please-close

@vaananth We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Configure auto-registered agent environments.

Add ability to configure agent.auto.register.environments in /var/lib/go-agent/config/autoregister.properties with an AGENT_ENVIRONMENTS environment variable.

@jfklingler, can you please sign the CLA? It's a legal requirement, and only a one-time task!
Your change looks good. I will push a version out soon after the CLA is signed. Thank you very much!
I'm also curious about how you're using this, in case you want to share. Thanks.

I see that this was opened in April. Sorry. :( I didn't see it till now.

No worries. CLA is signed. I'm using this in a CoreOS cluster for our
builds and deployments. I needed the environment so the agents targeted to
different hosts use the proper Go environment.
On Tue, May 26, 2015 at 12:07 PM, Aravind SV<EMAIL_ADDRESS>wrote:

I see that this was opened in April. Sorry. :( I didn't see it till now.
—
Reply to this email directly or view it on GitHub
https://github.com/gocd/gocd-docker/pull/2#issuecomment-105605033.

--
Thanks,
John Klingler
<EMAIL_ADDRESS>

Cool! Thanks again, for the change. I'll push a new version soon.

Done. https://registry.hub.docker.com/u/gocd/gocd-agent/


Feature: TUI/CLI for debugging chess-ray/chess-server

As a user, I want to play chess from the command line by entering my movements with the keyboard, and submitting them with Enter. I want to see the gradual progression of the game with some visual feedback on the console.
As a developer, I want to support dumping/loading game state so that I have a way to test scenario-based logic.

It's more practical at this time to create a simple REPL that can be used for debugging chess-ray. Ideally, we want to have it receive debugging information over the network to intercept debugging information, as well as being able to query when RayTiles are not behaving.


Not able to run in Mac  ( v10.9.3 )

Another option is to right click the .app and press Open. This for some reason allows you to skip the security check.

Yet another option is to remove extended attributes on the .app file:
xattr -rc Android\ Design\ Preview.app
WARNING: Don't do this for untrusted apps.


[feature request] Qserve + int8_kv_cache

Hi, Thanks for integrating the Qserve.
I’ve been interested in Qserve and really wanted to use it on TensorRT-LLM for speed.
This week, your team integrated it. I tested Llama-3-8B-Instruct + Qserve on OpenLLM based lmeval and it worked well. (less than 2% avg accuracy drop compared to fp16)
However, it seems it doesn’t work with int8_kv_cache yet, so we are implementing this feature. can you check it?
We will create PR and test it. If possible, we want to share our test results.

@lkm2835
Thanks for your interest to contribute to TensorRT-LLM!
@byshiue  for vis.


Filenames containing backtick are not escaped properly

Although unlikely, it's valid for a filename to contain a backtick, which would result in an invalid go file.
I have a fix in https://github.com/nkovacs/go.rice/tree/filename-quote, but it depends on #93 for tests.

Another (even more unlikely) issue: it's possible for a filename to contain a newline, which will break the // {{.Filename}} part, since the generated code will look like this:
		ChildFiles:  []*embedded.EmbeddedFile{
			filec, // new
line
			filed, // test1.txt
			filee, // test2.txt

		},

I'd be happy to take that as a PR!

Thanks, I've merged it.


Touchpad zoom broken in v5

Touchpad support for zooming seems to have been lost in the current d3 v5.
Example in v4 where touchpad zoom is working:
https://jsfiddle.net/zshktfp9/2/
Example in v5 where touchpad zoom is no longer working:
https://jsfiddle.net/zshktfp9/4/
The zoom code I am using is simple. I tested on mac in safari and chrome and on windows in chrome, the same break in functionality between v4 and v5 happened on all.
 var zoom = d3.zoom()         .scaleExtent([1, 10])         .on("zoom", function() { grp.attr("transform", d3.event.transform) });     svg.call(zoom);

That does indeed work. If I have to, I can use this to stay on current versions. Still seems weird that the issue is happening for me and coworkers but no one else.

Had the same issue.
Ofc zoom.filter(() => !d3.event.button) has fixed it

How would this play with https://github.com/d3/d3-zoom/pull/213 ?

Is there plans to patch this to 1.x.x? Seems like it's only fixed in v2, so v1 is broken


[WIP]Custom conflicts for DataSync

This is a very (very) rough implementation of custom conflicts in DataSync, need some serious feedback on this before we go ahead with this :smile:
What is this?
This PR adds the ability for checking custom fields for conflicts and resolving conflicts as well. Similar to what's in Offix conflict-server.
What's done?
A ConflictEngine interface which could be used to create custom Conflict Engines, not cleanly incorporated into the workflow yet, I am thinking of something like passing a custom conflict engine class to createDataSyncMongoDbProvider but I doubt it's optimal because I cannot see any way to extend this other than basic stuff like the engine used by default
What's left?

[ ] Finalize approach while optimising for extensiblity
[ ] Writing tests
[ ] Writing documentation

/cc @wtrocki It would be awesome if you could provide some example usecases for this (and possibly cases where this would completely break), it would definitely help me to drive the approach in a better direction

Looks good so far. I would love to get your opinion about next state - we also need ability to fetch base (I send link to datasync repository that had that implemented) as current production conflict implementation is only client side

we also need ability to fetch base (I send link to datasync repository that had that implemented) as current production conflict implementation is only client side

Definitely! I am will keep that in mind as well

I think we need:

yourself spending another day thinking about this
have call to decide if conflicts and deltasync are separate or together.

If I add now deltasync my create queries will require timestamp but that is only required for conflicts, which is very confusing. We need to clear this as soon as possible.
Technical capabilities will follow - at first this needs to make sense from the functionality point of view

Branch is stale now, going to push prototype for this in the coming days


Crash while shift-clicking on a station from the train tab.

The mod LTN Manager (0.4.17) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event LtnManager::on_gui_click (ID 1)
LuaEntity belongs to surface Morozko (index 10) but a LuaEntity belonging to surface Nauvis Orbit (index 2) was expected.
stack traceback:
[C]: in function 'zoom_to_world'
LtnManager/scripts/gui/actions.lua:91: in function 'func'
LtnManager/scripts/gui/index.lua:81: in function 'dispatch'
LtnManager/control.lua:127: in function 'handle_gui_event'
LtnManager/control.lua:136: in function <LtnManager/control.lua:133>

Ah this may be unsolvable for me then.  I will leave this open for now and will fix this particular error soon but I may just have to ignore shift-clicking when not on the same surface.  Ill do some more digging soon.

If I satellite view another surface, then shift click a station on that same surface, it brings up that station in map mode, not satellite mode. No crash.
If I satellite view another surface, then shift click a station on some other surface, I crash.

That is what I expected would happen.  For now just avoid shift-clicking stations on another surface without satellite viewing the appropriate station first.  I plan to look into raiguard's suggestion to interface with space exploration soon, but I can't give a timetable for when I will be able to do that.

With the current update (0.4.21) I get a different error now on this.
Since you closed #218, I guess here is more appropriate to continue this?
Error while running event LtnManager::on_gui_click (ID 1)
__LtnManager__/scripts/gui/actions.lua:94: attempt to call global 'remote_call' (a nil value)
stack traceback:
	__LtnManager__/scripts/gui/actions.lua:94: in function 'func'
	__LtnManager__/scripts/gui/index.lua:81: in function 'dispatch'
	__LtnManager__/control.lua:127: in function 'handle_gui_event'
	__LtnManager__/control.lua:136: in function <__LtnManager__/control.lua:133>

I have Space Exploration installed and satellite view is unlocked. Shift+clicking on a train station on a different surface leads to this error, regardless of whether I already am in satellite view or not.

Now this:
The mod LTN Manager (0.4.22) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event LtnManager::on_gui_click (ID 1)
Unknown interface: space-exloration
stack traceback:
	[C]: in function 'call'
	__LtnManager__/scripts/gui/actions.lua:99: in function 'func'
	__LtnManager__/scripts/gui/index.lua:81: in function 'dispatch'
	__LtnManager__/control.lua:127: in function 'handle_gui_event'
	__LtnManager__/control.lua:136: in function <__LtnManager__/control.lua:133>

Thank you for catching these, please redownload 0.4.22

Now it doesn't cause an error anymore, but it simply closes the LTN Manager GUI and then nothing happens. (no changing of surface or view location)
Same for already being in satellite, map or normal view.

Interesting, if it no longer crashes I'll leave this alone for now, but will ask on the Space Exploration discord soon how I should handle this.

The problem is that surface.name does not map 1:1 to zone_name.
I'll look into how to properly get the zone name later and make a PR if I can figure it out.


bower install 0.5.3, different bower.json?

Hey, I was debugging a friend's project and for some reason when downloading impress.js#0.5.3 through bower, it doesn't seem to get the right bower.json file. The bower.json lacks a main property, where the latest version (0.5.3) does have it in the bower.json.
any ideas what could be going wrong? I fixed it by specifically installing bower with the latest commit SHA:
bower install 'git@github.com:bartaz/impress.js.git#efc184947a9b58ca30ad391146700513fd23a30c'

I wasn't the one adding bower support and bower.json file.
It may be connected to the fact that version 0.5.3 (as released on GitHub with repo tag https://github.com/bartaz/impress.js/tree/0.5.3) doesn't have bower file at all, it was added later on.

That makes sense, thanks for responding.
In any case, if anyone else has this issue, the easiest way is to simply install the master branch like so:
bower install impress.js#master

This issue will be closed once the version 0.6.0 is released.

Closing as a duplicate of #512 (see bullet points).


sanitycheck: make verbose output fit screen

Split verbose test results into two lines to make it fit into screen.
Example output:

 35/776 em_starterkit_em7d        kernel.memory_protection                           PASSED (build)
                                  tests/kernel/mem_protect/stackprot
 36/776 em_starterkit_em7d        kernel.memory_protection.userspace                 PASSED (build)
                                  tests/kernel/mem_protect/userspace
 37/776 em_starterkit_em7d        kernel.mutex                                       PASSED (build)
                                  tests/kernel/mutex/mutex_api
 38/776 em_starterkit_em7d        kernel.message_queue                               PASSED (build)
                                  tests/kernel/msgq/msgq_api

PS: On one hand it's indeed better to fit in a standard width. On the other hand it'll be more difficult to grep the results.

the results are stored in an xml and csv file already, why do you want to be grepping the raw output?

the results are stored in an xml and csv file already, why do you want to be grepping the raw output?

I meant grepping interactively, not in any automation.
The XML results output is not formatted and basically unreadable (and undiff-able). I recently started post-processing it with xmllint (I might try to implement this inside sanitycheck later) which makes it  massively more readable but it's still not as readable because it's much more verbose as it includes all individual ztests and potentially very long failure messages. The XML file is unsurprisingly good for machine parsing and not as "user friendly" as glancing at the -v log. Nothing wrong about any of that - the right tool for each job.
It's been a long time since I looked at any CSV file but I remember them being also and unsurprisingly meant for machines not humans. Again nothing wrong about that.
Anyway grep -A1 FAIL etc. should be enough to adjust after this change, sorry for the digression.

It's been a long time since I looked at any CSV file,...

Just found why by chance in my notes: --testcase-report includes the (non-deterministic) handler_time.


Embeddind into Servlet API

Hi,
I would like to add Java-WebSocket server into OSGi's HTTP Service. The way todo that is:
httpService.registerServlet("/websocket", new WebSocketServer()), params, null);
However, WebSocketServer must be a javax.servlet.Servlet class.
Do you provides an implementation of this or is there a way to wrap WebSocketServer into a servlet class?
Regards,
Davi

Hello @davibaldin,
no, we do not provide such an implementation.
Maybe take a look at the WebSocketServlet class of Jetty (https://github.com/eclipse/jetty.project/blob/master/jetty-websocket/websocket-servlet/src/main/java/org/eclipse/jetty/websocket/servlet/WebSocketServlet.java).
Best regards,
Marcel

Hello @davibaldin,
is this question answered for you?
Best regards,
Marcel

Hi Marcel, you’ve drived to Jetty, however I’ve no lucky yet.
Davi

On 25 Apr 2019, at 12:32, Marcel Prestel<EMAIL_ADDRESS>wrote:
Hello @davibaldin,
is this question answered for you?
Best regards,
Marcel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


When i upload a image and image uploaded successfully. Now i want to upload another image without clicking on cross icon on top right.

Hi, I am trying to upload another image when my first image uploaded successfully but it is not allowing me to upload another image until i  am not clearing image preview by clicking on cross icon on top right side.

Hi,
you can reference the component in code and call deleteAll() function to clear the files uploaded previously.
// reference the image uploader instance in code   @ViewChild('imageInput') imageInput: ImageUploadComponent; this.imageInput.deleteAll();
 // set the identifier in the markup <image-upload #imageInput"  </image-upload>


[camera] camera plugin crashing app when taking picture in android

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
when taking picture multiple time and disposing the controller when its not needed it crashes the app
Expected results
app should be crashed it should show image
Actual results
app keeps crashing
Code sample
Code sample

import 'package:camera/camera.dart';
import 'package:flutter/material.dart';
late final List<CameraDescription> cameras;
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  try {
    WidgetsFlutterBinding.ensureInitialized();
    cameras = await availableCameras();
  } on CameraException catch (e) {
    cameras = [];
    _logError(e.code, e.description);
  }

  SystemChrome.setPreferredOrientations(
      [DeviceOrientation.portraitUp, DeviceOrientation.portraitDown]);
  runApp(MyApp(

  ));
}

class MyApp extends StatelessWidget {

  const MyApp({super.key, });

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(

      home: CameraScreen(

      ),
    );
  }
}
enum EditorState {
  idle,
  edit,
}

class CameraScreen extends StatefulWidget {

  const CameraScreen(
      {super.key});

  @override
  State<CameraScreen> createState() => _CameraScreenState();
}

class _CameraScreenState extends State<CameraScreen>
    with WidgetsBindingObserver {
  late CameraController? controller;
  late final CameraFileRepository cameraService;
  final GlobalKey<ExtendedImageEditorState> editorKey =
      GlobalKey<ExtendedImageEditorState>();
  late File? image;

  bool backCamera = true;

  EditorState editorstate = EditorState.idle;

  @override
  void initState() {

    WidgetsBinding.instance.addObserver(this);
    cameraService = CameraFileRepository();

    controller = cameras.isEmpty
        ? null
        : CameraController(cameras[0], ResolutionPreset.max);

    controller?.initialize().then((value) {
      setState(() {});
    });

    super.initState();
  }

  @override
  void didChangeAppLifecycleState(AppLifecycleState state) {
    if (controller == null) {
      return;
    }
    // App state changed before we got the chance to initialize.
    if (!controller!.value.isInitialized) {
      return;
    }
    if (state == AppLifecycleState.inactive) {
      controller?.dispose();
    } else if (state == AppLifecycleState.resumed) {
      final newcontroller = CameraController(cameras[0], ResolutionPreset.max);

      newcontroller.initialize().then((value) {
        setState(() {
          image = null;

          controller = newcontroller;
        });
      });
    } else if (state == AppLifecycleState.hidden) {
      controller?.dispose();
    } else {
      controller?.dispose();
    }
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    controller?.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(

      body: Column(
        children: [

          if (image == null)
            Expanded(
                child: controller == null
                    ? const Center(
                        child: Text("Camera is not available"),
                      )
                    : !controller!.value.isInitialized
                        ? Container()
                        : CameraPreview(controller!)),
          if (image == null)
           IconButton(
icon:Icon(Icons.camera),
              onTap: (
                  ) async {
               final newimage =
                  await cameraService.takePicture(controller: controller);
CameraController? nController;
if(newimage!=null){
   nController = controller;
setState((){
        image = newimage;
controller=null;
 nController?.dispose();

});

              },
            ),

        ],
      ),
    );
  }
}
class CameraFileRepository {

  Future<XFile?> takePicture({required CameraController? controller}) async {
    final CameraController? cameraController = controller;
    cameraController?.setExposureMode(ExposureMode.locked);
    cameraController?.setFocusMode(FocusMode.locked);
    if (cameraController == null || !cameraController.value.isInitialized) {
      return null;
    }

    try {
      final XFile file = await cameraController.takePicture();

      return file;
    } on CameraException {
      return null;
    }
  }}

Error log

Log
W/libc    ( 6258): Access denied finding property "vendor.camera.aux.packagelist"
W/CameraManagerGlobal( 6258): ignore the torch status update of camera: 4
W/libc    ( 6258): Access denied finding property "vendor.camera.aux.packagelist"
W/CameraManagerGlobal( 6258): ignore the torch status update of camera: 5
E/CameraManagerGlobal( 6258): Camera 5 is not available. Ignore physical camera status change
D/CameraDevice-JV-0( 6258): close: X
I/Camera  ( 6258): open | onClosed
I/Camera  ( 6258): closeCaptureSession
D/BufferQueueConsumer( 6258): [ImageReader-1920x1080f21m1-6258-0](id:187200000004,api:0,p:-1,c:6258) disconnect
D/BufferQueueConsumer( 6258): [ImageReader-1280x720f23m1-6258-1](id:187200000005,api:0,p:-1,c:6258) disconnect
D/BufferQueueConsumer( 6258): [SurfaceTexture-0-6258-0](id:187200000003,api:0,p:-1,c:6258) disconnect
E/AndroidRuntime( 6258): FATAL EXCEPTION: CameraBackground
E/AndroidRuntime( 6258): Process: com.enzipe.imagetotext, PID: 6258
E/AndroidRuntime( 6258): java.lang.NullPointerException: Attempt to invoke virtual method 'void android.hardware.camera2.CameraCaptureSession.close()' on a null object reference
E/AndroidRuntime( 6258): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:1227)
E/AndroidRuntime( 6258): 	at io.flutter.plugins.camera.Camera$1.onClosed(Camera.java:347)
E/AndroidRuntime( 6258): 	at android.hardware.camera2.impl.CameraDeviceImpl$5.run(CameraDeviceImpl.java:247)
E/AndroidRuntime( 6258): 	at android.os.Handler.handleCallback(Handler.java:942)
E/AndroidRuntime( 6258): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 6258): 	at android.os.Looper.loopOnce(Looper.java:211)
E/AndroidRuntime( 6258): 	at android.os.Looper.loop(Looper.java:300)
E/AndroidRuntime( 6258): 	at android.os.HandlerThread.run(HandlerThread.java:67)
W/CameraDevice-JV-0( 6258): Device error received, code 4, frame number 68, request ID 5, subseq ID 0
W/CameraDevice-JV-0( 6258): Device error received, code 3, frame number 69, request ID 5, subseq ID 0
W/CameraDevice-JV-0( 6258): Device error received, code 3, frame number 70, request ID 5, subseq ID 0
W/CameraDevice-JV-0( 6258): Device error received, code 3, frame number 71, request ID 5, subseq ID 0
W/CameraDevice-JV-0( 6258): Device error received, code 3, frame number 72, request ID 5, subseq ID 0
W/CameraDevice-JV-0( 6258): Device error received, code 3, frame number 73, request ID 8, subseq ID 0
W/OOMEventManagerFK( 6258): Failed to mkdir /data/miuilog/stability/memleak/heapdump/
W/CameraBackgroun( 6258): type=1400 audit(0.0:124513): avc: denied { search } for name="miuilog" dev="dm-40" ino=621517 scontext=u:r:untrusted_app:s0:c48,c259,c512,c768 tcontext=u:object_r:data_log_file:s0 tclass=dir permissive=0 app=com.enzipe.imagetotext
W/CameraBackgroun( 6258): type=1400 audit(0.0:124514): avc: denied { search } for name="miuilog" dev="dm-40" ino=621517 scontext=u:r:untrusted_app:s0:c48,c259,c512,c768 tcontext=u:object_r:data_log_file:s0 tclass=dir permissive=0 app=com.enzipe.imagetotext
W/CameraBackgroun( 6258): type=1400 audit(0.0:124515): avc: denied { search } for name="miuilog" dev="dm-40" ino=621517 scontext=u:r:untrusted_app:s0:c48,c259,c512,c768 tcontext=u:object_r:data_log_file:s0 tclass=dir permissive=0 app=com.enzipe.imagetotext
W/CameraBackgroun( 6258): type=1400 audit(0.0:124516): avc: denied { search } for name="miuilog" dev="dm-40" ino=621517 scontext=u:r:untrusted_app:s0:c48,c259,c512,c768 tcontext=u:object_r:data_log_file:s0 tclass=dir permissive=0 app=com.enzipe.imagetotext
W/CameraBackgroun( 6258): type=1400 audit(0.0:124517): avc: denied { search } for name="miuilog" dev="dm-40" ino=621517 scontext=u:r:untrusted_app:s0:c48,c259,c512,c768 tcontext=u:object_r:data_log_file:s0 tclass=dir permissive=0 app=com.enzipe.imagetotext
W/ipe.imagetotext( 6258): Attempt to remove non-JNI local reference, dumping thread
3
E/gralloc4( 6258): Empty SMPTE 2094-40 data
I/Process ( 6258): Process is going to kill itself!
I/Process ( 6258): java.lang.Exception
I/Process ( 6258): 	at android.os.Process.killProcess(Process.java:1330)
I/Process ( 6258): 	at com.android.internal.os.RuntimeInit$KillApplicationHandler.uncaughtException(RuntimeInit.java:202)
I/Process ( 6258): 	at com.google.firebase.crashlytics.internal.common.CrashlyticsUncaughtExceptionHandler.uncaughtException(CrashlyticsUncaughtExceptionHandler.java:62)
I/Process ( 6258): 	at org.chromium.base.JavaExceptionReporter.uncaughtException(chromium-TrichromeWebViewGoogle6432.aab-stable-584516333:17)
I/Process ( 6258): 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1073)
I/Process ( 6258): 	at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
I/Process ( 6258): 	at java.lang.Thread.dispatchUncaughtException(Thread.java:2306)
I/Process ( 6258): Sending signal. PID: 6258 SIG: 9
Lost connection to device.

Logs
Logs
flutter --verbose create
[   +9 ms] executing: sw_vers -productName
[  +25 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +17 ms] Exit code 0 from: sw_vers -productVersion
[        ] 13.4.1
[        ] executing: sw_vers -buildVersion
[  +17 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 22F770820d
[        ] executing: uname -m
[   +5 ms] Exit code 0 from: uname -m
[        ] x86_64
[   +6 ms] executing: sysctl hw.optional.arm64
[   +6 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[ +107 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +47 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'LegacyCanvasKitRemover' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[ +118 ms] "flutter create" took 187ms.
[   +4 ms] No option specified for the output directory.
           Create a new Flutter project.

           If run on a project that already exists, this will repair the project, recreating any files that are missing.

           Global options:
           -h, --help                  Print this usage information.
           -v, --verbose               Noisy logging, including all shell commands executed.
                                       If used with "--help", shows hidden options. If used with "flutter doctor", shows additional diagnostic information. (Use "-vv" to force
verbose
                                       logging in those cases.)
           -d, --device-id             Target device id or name (prefixes allowed).
               --version               Reports the version of this tool.
               --suppress-analytics    Suppress analytics reporting for the current CLI invocation.
               --disable-telemetry     Disable telemetry reporting each time a flutter or dart command runs, until it is re-enabled.
               --enable-telemetry      Enable telemetry reporting each time a flutter or dart command runs.

           Usage: flutter create <output directory>
           -h, --help                   Print this usage information.
               --[no-]pub               Whether to run "flutter pub get" after the project has been created.
                                        (defaults to on)
               --[no-]offline           When "flutter pub get" is run by the create command, this indicates whether to run it in offline mode or not. In offline mode, it will need
to have
                                        all dependencies already available in the pub cache to succeed.
               --[no-]overwrite         When performing operations, overwrite existing files.
               --description            The description to use for your new Flutter project. This string ends up in the pubspec.yaml file.
                                        (defaults to "A new Flutter project.")
               --org                    The organization responsible for your new Flutter project, in reverse domain name notation. This string is used in Java package names and
as prefix in
                                        the iOS bundle identifier.
                                        (defaults to "com.example")
               --project-name           The project name for this new Flutter project. This must be a valid dart package name.
           -i, --ios-language           The language to use for iOS-specific code, either Objective-C (legacy) or Swift (recommended).
                                        [objc, swift (default)]
           -a, --android-language       The language to use for Android-specific code, either Java (legacy) or Kotlin (recommended).
                                        [java, kotlin (default)]
               --platforms              The platforms supported by this project. Platform folders (e.g. android/) will be generated in the target project. This argument only works
when
                                        "--template" is set to app or plugin. When adding platforms to a plugin project, the pubspec.yaml will be updated with the requested
platform. Adding
                                        desktop platforms requires the corresponding desktop config setting to be enabled.
                                        [ios (default), android (default), windows (default), linux (default), macos (default), web (default)]
           -t, --template=<type>        Specify the type of project to create.

                     [app]              (default) Generate a Flutter application.
                     [module]           Generate a project to add a Flutter module to an existing Android or iOS application.
                     [package]          Generate a shareable Flutter project containing modular Dart code.
                     [plugin]           Generate a shareable Flutter project containing an API in Dart code with a platform-specific implementation through method channels for
Android, iOS,
                                        Linux, macOS, Windows, web, or any combination of these.
                     [plugin_ffi]       Generate a shareable Flutter project containing an API in Dart code with a platform-specific implementation through dart:ffi for Android,
iOS, Linux,
                                        macOS, Windows, or any combination of these.
                     [skeleton]         Generate a List View / Detail View Flutter application that follows community best practices.

           -s, --sample=<id>            Specifies the Flutter code sample to use as the "main.dart" for an application. Implies "--template=app". The value should be the sample ID
of the
                                        desired sample from the API documentation website (https://api.flutter.dev/). An example can be found at:
                                        https://api.flutter.dev/flutter/widgets/SingleChildScrollView-class.html
           -e, --[no-]empty             Specifies creating using an application template with a main.dart that is minimal, including no comments, as a starting point for a new
application.
                                        Implies "--template=app".
               --list-samples=<path>    Specifies a JSON output file for a listing of Flutter code samples that can be created with "--sample".

           Run "flutter help" to see global options.
[  +10 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      CreateBase.validateOutputDirectoryArg (package:flutter_tools/src/commands/create_base.dart:185:7)
           #2      CreateCommand.runCommand (package:flutter_tools/src/commands/create.dart:192:5)
           #3      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1616:12)
           <asynchronous suspension>
           #4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
           <asynchronous suspension>
           #5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
           <asynchronous suspension>
           #8      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
           <asynchronous suspension>
           #10     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)
           <asynchronous suspension>
           #11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #12     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[ +275 ms] ensureAnalyticsSent: 266ms
[        ] Running 0 shutdown hooks
[        ] Shutdown hooks complete
[   +1 ms] exiting with code 2

Flutter Doctor output
Doctor output
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.2, on macOS 13.4.1 22F770820d darwin-x64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.81.1)
[✓] Connected device (3 available)
[✓] Network resources

Hi @alihassan143. Thanks for filing this. Trying to reproduce this with the modified code sample below, but I can't reproduce the crash at all. Can you try with this as well to see if it reproduces? Also, does this reproduce all the time or the issue only occur in some instances?
Code Sample

import 'dart:io';

import 'package:camera/camera.dart';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

late final List<CameraDescription> cameras;
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  try {
    WidgetsFlutterBinding.ensureInitialized();
    cameras = await availableCameras();
  } on CameraException catch (e) {
    cameras = [];
    // _logError(e.code, e.description);
  }

  SystemChrome.setPreferredOrientations(
      [DeviceOrientation.portraitUp, DeviceOrientation.portraitDown]);
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({
    super.key,
  });

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: CameraScreen(),
    );
  }
}

enum EditorState {
  idle,
  edit,
}

class CameraScreen extends StatefulWidget {
  const CameraScreen({super.key});

  @override
  State<CameraScreen> createState() => _CameraScreenState();
}

class _CameraScreenState extends State<CameraScreen>
    with WidgetsBindingObserver {
  late CameraController? controller;
  late final CameraFileRepository cameraService;
  late XFile? image;

  bool backCamera = true;

  EditorState editorstate = EditorState.idle;

  @override
  void initState() {
    WidgetsBinding.instance.addObserver(this);
    cameraService = CameraFileRepository();

    controller = cameras.isEmpty
        ? null
        : CameraController(cameras[0], ResolutionPreset.max);

    controller?.initialize().then((value) {
      setState(() {});
    });

    super.initState();
  }

  @override
  void didChangeAppLifecycleState(AppLifecycleState state) {
    if (controller == null) {
      return;
    }
    // App state changed before we got the chance to initialize.
    if (!controller!.value.isInitialized) {
      return;
    }
    if (state == AppLifecycleState.inactive) {
      controller?.dispose();
    } else if (state == AppLifecycleState.resumed) {
      final newcontroller = CameraController(cameras[0], ResolutionPreset.max);

      newcontroller.initialize().then((value) {
        setState(() {
          image = null;

          controller = newcontroller;
        });
      });
    } else if (state == AppLifecycleState.hidden) {
      controller?.dispose();
    } else {
      controller?.dispose();
    }
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    controller?.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        children: [
          // if (image == null)
          Expanded(
              child: controller == null
                  ? const Center(
                      child: Text("Camera is not available"),
                    )
                  : !controller!.value.isInitialized
                      ? Container()
                      : CameraPreview(controller!)),
          // if (image == null)
          IconButton(
              icon: Icon(Icons.camera),
              onPressed: () async {
                final newimage =
                    await cameraService.takePicture(controller: controller);
                CameraController? nController;
                if (newimage != null) {
                  nController = controller;
                  setState(() {
                    image = newimage;
                    controller = null;
                    nController?.dispose();
                  });
                }
                ;
              })
        ],
      ),
    );
  }
}

class CameraFileRepository {
  Future<XFile?> takePicture({required CameraController? controller}) async {
    final CameraController? cameraController = controller;
    cameraController?.setExposureMode(ExposureMode.locked);
    cameraController?.setFocusMode(FocusMode.locked);
    if (cameraController == null || !cameraController.value.isInitialized) {
      return null;
    }

    try {
      final XFile file = await cameraController.takePicture();

      return file;
    } on CameraException {
      return null;
    }
  }
}

@dam-ease  kindly run on real device with android 12 or later than open camera screen multiple time and take a picture  it will happen some time not every instance

Hi @alihassan143. Just tried reproducing on a physical Android device (Android 12) and I opened camera multiple times, and captured images but didn't reproduce the crash. It'd be helpful if you share recordings and observe the times at which the crash reproduces so it helps us move this issue further.
Thank you!


help request: How to support multiple ports for the ApisixUpstream

Description
I want to  define  multiple ports for the ApisixUpstream ,
I refer to the documentation
https://apisix.apache.org/zh/docs/ingress-controller/1.4.0/concepts/apisix_upstream/
when I create  my ApisixUpstream use  kubectl apply -f  test-up.yaml,
it make a err like this:
apisixupstream.apisix.apache.org/xsgrpc-service unchanged
error: error validating "test-up.yaml": error validating data: ValidationError(Service.spec): unknown field "portLevelSettings" in io.k8s.api.core.v1.ServiceSpec; if you choose to ignore these errors, turn validation off with --validate=false
this is my  test-up.yaml  file:
apiVersion: apisix.apache.org/v2beta3
kind: ApisixUpstream
metadata:
  name: xsgrpc-service
  namespace: test-arch
spec:
  portLevelSettings:
  - port: 50051
    scheme: grpc
  - port: 80
    scheme: http
  timeout:
    connect: 1s
    read: 3s
    send: 3s

---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: xsgrpc
  name: xsgrpc-service
spec:
  portLevelSettings:
  - name: http
    port: 80
    targetPort: 30080
  - name: grpc
    port: 50051
    targetPort: 30051
  selector:
    app: xsgrpc

my apisix ingress controller version is : 1.4
Environment

APISIX version (run apisix version):2.13.2
Operating system (run uname -a):
OpenResty / Nginx version (run openresty -V or nginx -V):
etcd version, if relevant (run curl http://<IP_ADDRESS>:9090/v1/server_info):
APISIX Dashboard version, if relevant:
Plugin runner version, for issues related to plugin runners:
LuaRocks version, for installation issues (run luarocks --version):

Obviously, you just wrote the spec of the service wrong
I see you closed this issue, presumably the issue should have been resolved


Add a list of allowed permissions in Harbour. JB#56092

I believe this paragraph could get a mention on permissions: https://docs.sailfishos.org/Develop/Apps/Harbour/#validating-your-app

I believe this paragraph could get a mention on permissions: https://docs.sailfishos.org/Develop/Apps/Harbour/#validating-your-app

done


⚠ Bofrost.de has degraded performance

In d663547, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1104 ms

Resolved: Bofrost.de performance has improved in fd703c0.


Feature/arbitrary state

Creates an arbitrary state given an input complex vector using controlled rotations and phases. Like PR #34 but without using a defgate. Optimizations and other feedback appreciated!

While this currently works, the gate count grows at an insane rate. I am trying to implement it in another way to reduce this count. Until then, any high level suggestions to reduce gate count are welcome, though in-depth code review is probably too early.

@ncrubin It actually turned out that the methods in the utils folder were too inefficient in the number of gates they generated. I'm removing them from this specific PR, since they're not needed for the new way of generating arbitrary states. I'm going to break up the method and clean up documentation for the new file. Sorry for the inconvenience!

@ncrubin I've made revisions as per your code review. Let me know what you think!

@ncrubin I've made the small changes you've suggested to unitary_operatory.py

Merged!


File Filter still not working

Hi @NBprojekt
Some time ago I've sent you a PR #15 because the check was not correct to see if a file filter is set or not.
However, it's still not working.
I've a running action here with gource-action: https://github.com/BoundfoxStudios/community-project/blob/develop/.github/workflows/repository-visualization.yml
As you can see in the debug log, the filter it recognized: https://github.com/BoundfoxStudios/community-project/actions/runs/4288063582/jobs/7469624333#step:4:53

Unfortunately, the .meta files are still visible in the output video.
I've also tried different syntaxes in the yaml file for setting the filter:
gource_file_filter: \.meta$
gource_file_filter: '\.meta$'
gource_file_filter: meta$

If I run gource locally with: gource --file-filter "\.meta$" --key --seconds-per-day 0.5 --auto-skip-seconds 0.1 I don't see the .meta files in the output.
Any idea what can be wrong?

https://github.com/utensils/Envisaged/issues/14 ok, it may be that the version from the base image is simply too old for that filter.

@NBprojekt would be really nice if you could update gource somehow. The base image itself is now 3 years old (see https://hub.docker.com/r/utensils/opengl).
Note to self: According to https://github.com/acaudwell/Gource#requirements "Gource's display is rendered using OpenGL and requires a 3D accelerated video card to run.".
Google only found https://hub.docker.com/r/nvidia/opengl as the only maintained image. Unfortunately (for this project), only Ubuntu and CentOS are available. No alpine.

@NBprojekt would be really nice if you could update gource somehow. The base image itself is now 3 years old (see https://hub.docker.com/r/utensils/opengl).
Note to self: According to https://github.com/acaudwell/Gource#requirements "Gource's display is rendered using OpenGL and requires a 3D accelerated video card to run.".
Google only found https://hub.docker.com/r/nvidia/opengl as the only maintained image. Unfortunately (for this project), only Ubuntu and CentOS are available. No alpine.

@koppor If you want to use the latest one, check out https://github.com/BoundfoxStudios/action-gource
I've updated all the base images required to use the latest gource version.

For the googlers: A more recent opengl image is https://github.com/boundfoxstudios/docker-opengl
@ManuelRauber Thank you for the reply and your work. I am trying it out now (https://github.com/JabRef/jabref/pull/10056).

@ManuelRauber Sorry for my inactivity lately.
Will update the image and check if the filter work then properly.


Removed deprecated keywords

A well done drawing, who made it?

Have you confirmed this works? I tried making the same change a while back and it broke everything for some reason.


[FX-5061] Migrate ButtonControlLabel component

FX-5061
Description
Migrate ButtonControlLabel component, therefore ButtonCheckbox and ButtonRadio will also be migrated

[x] Storybook Visual tests will be fixed in separate tickets
[x] Cypress Visual tests will be fixed in separate tickets

How to test

Temploy

Development checks

N/A Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
N/A Annotate all props in component with documentation
N/A Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests (visual tests included)

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


Update all pypi.python.org URLs to pypi.org

For details on the new PyPI, see the blog post:
https://pythoninsider.blogspot.ca/2018/04/new-pypi-launched-legacy-pypi-shutting.html

Coverage remained the same at 92.045% when pulling a2a8199f0308e88ebd1de72faa62527a8caea6f4 on jdufresne:pypi into 9696733fd170cba28016c0a8a044c69a1853fdbe on django-import-export:master.


Script for code coverage

@kwehmeyer This PR contains:

code_coverage.jl
Update to Project.toml in test directory
Add lcov.info to .gitignore

Codecov Report

Merging #41 (05bcb5d) into master (d41e52b) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #41   +/-   ##
======================================
  Coverage    4.22%   4.22%
======================================
  Files          22      22
  Lines         568     568
======================================
  Hits           24      24
  Misses        544     544

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d41e52b...05bcb5d. Read the comment docs.


chore: fix copyright year in footer

Super tiny fix.
(The challenge was announced on Jan 1, 2024)

thanks! ive added you to the org so if you want to make any  other  changes or  improvements  big  or small feel free!  👍


feat:support stripe payment provider

https://github.com/casdoor/casdoor/issues/2023

https://github.com/casdoor/casdoor/assets/54203997/2cda0df3-b9b1-40df-91ab-5f71b5d2e147


Release prep

@SimonGreenhill Two major changes that I would need you to review:

Many additions to the orthography profile. Please confirm or comment on the changes if I have introduced any errors. Mostly educated guesses, following your comments in the issue (closes #1 )
Added all the authors of the 2008 and 2024 paper as authors. Any other Contributors that should be added? (closes #2 )

Once we have fixed this, I will prepare the Zenodo release (v1.0 or v0.1?)

Thanks! I have fixed the remaining issues and will merge/release now.


Keep cluster_view_listener shared pointer in lambda to avoid heap-use-after-free problem

Keep cluster_view_listener shared pointer in lambda to avoid heap-use-after-free problem when the view listener is destroyed.
fixes #854

Windows test PASSed.

I pushed your branch to my fork and ran the nightly-Ubuntu-i386 job there: https://github.com/yemreinci/hazelcast-cpp-client/actions/runs/791329404. Still memory errors.
cluster_view_listener and event_handler (transitively)  hold a raw reference to ClientContext. Connection holds a raw reference to an io_context which is owned by the client. By putting a shared_ptr to them in a free thread we are letting them live past the life of the client, and that again causes dangling pointers to be dereferenced.
I have sent an alternative solution: #858

Linux test PASSed.

Closing in favor of https://github.com/hazelcast/hazelcast-cpp-client/pull/858.


Screenshot of Github webhook permissions is out of date

E.g https://buildkite.com/macstadium/vmkite-images/settings/setup/github
New ones look like this:

Thanks @lox! Will update 👌🏻

@lox looks like this has been updated 🎉 Closing this for now, but if you find it needs updating again you're welcome to re-open 😊


Allows changing the rate of speech

Exposes piper's "--length_scale" argument as a "SpeakingRate" float inside "PiperConfiguration", editing this value lets you change the rate of speech. Lower values are faster, higher values are slower.

Let me know if you have any questions or remarks!
Some comments incase these are the things preventing you from accepting this pull request:

The use of String.Replace(..) is because even if i ask for "1.00" format its giving me "1,00" format (with a comma instead of dot) which gets interpreted as "0" so piper blurts out the whole text in like 2 milliseconds, but if i just replace comma with dot it works as it should. This could very well be related to windows settings in regards to language and/or region, seeing how in some parts of the world comma is used for decimals and in other parts of the world the dot is used instead, i wouldn't be surprised if .NET actually uses the OS settings to decide how to turn floats into strings, but that causes an issue here because piper clearly does not look at that OS stuff and only accepts dots. If you have a better way to enforce dots then use that, i only managed to get it working with String.Replace(..)

I know its pretty bizarre that a lower value means higher speed, but that's just what piper gives us, cant really find any "range" for that number so it would be unsafe to "flip" it somehow, because we cant tell what sort of numbers other people would be expecting to be able to use. On top of that based on my testing 0-0.99 is actually a lot bigger range then 1.01-5.00 seems to be (where 5 is just some arbitrary number i picked as "max"). This is also why i added the summary for the variable, because lower value for faster voice is just weird, so it makes sense to inform users of that quirk.

For what its worth i really don't care about any sort of credit, if you don't want me listed as contributor for ~2 lines of code (like im pretty sure Github will do) i 100% understand that, but then please just copy the code over manually, not exposing this functionality of piper in PiperSharp is a shame.


[Docker Desktop] Image vulnerability scanning on Desktop

Tell us about your request
Scan images for vulnerabilities to ensure they are checked against an aggregated set of Common Vulnerabilities and Exposures (CVEs).
Which service(s) is this request for?
Docker Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Desktop told us they care about security and running things locally means using your own compute making it cheaper when doing smaller or personal projects. To support this we could add scanning in desktop to support:

Scan container images for Common Vulnerabilities and Exposures (CVEs)
List by severity the software vulnerabilities that were discovered, based on the Common Vulnerabilities and Exposures (CVEs) database

Are you currently working around this issue?
N/A
Additional context
N/A
Attachments
N/A

while i'd really like to see this feature built-in into Docker Desktop , i'm not really sure about ressource consumption of that feature.
solution like trivy from aquasec could be interesting to add as an opt-in feature.
depending on this integration this could also lead to higher disk usage.
Might worth a try in an edge release , but yes definitely worth the feature 👍

Alternatively, while this doesn't "use your own compute", Desktop could dish out to Hub as well to perform the scanning. ref: https://github.com/docker/roadmap/issues/18

Dupe of https://github.com/docker/roadmap/issues/95 - closing :)


KubeOne join for worker nodes

What feature would you like to be added?
If a KubeOne user don’t use machine-controller (e.g. bare-metal, edge deployment, Ansible) instead of executing several commands on a worker a command like kubeone join  would make the installation easier.
kubeone joinwill installs all dependencies and and execute kubeadm join command. Only one cmd is required to join a worker node.

As we discussed offline. We will not implement a dedicated join command, instead we will use a StaticWorkers API field.


Add debug helpers generated

Description
This PR add debug helpers generated files. It is divided from #4942 .
Original, it is used to enhance handshake state tests. It might be used for other purpose with some improvements, also.
In this PR, we add functions for translating enum values into string. That can reduce test fail due to enum value change.
Status
IN DEVELOPMENT
Requires Backporting
NO
Migrations
NO

Rebased and resolve conflict

Note that we now generate files from cmake (see #4514). Could you add cmake generation to this PR? (Alternatively perhaps someone could follow it up with a PR to add cmake generation.)

Rebased and fix feedback

Rebase is needed.

Rebased and fix conflict

@mprse , just fix a CI fails, please re-review.
@daverodgman , I did not find your comments . Do you left comments ? Github show me you reviewed this PR.

I have reviewed the updates - LGTM


Implement Item

This implements Item.
Because the Item interface deliberately doesn't expose the underlying magic numbers, it's necessary to keep track of whether the age and pickup time were set through the api or not. This allows vanilla behavior to be preserved in the case where the magic number is set some other way (e.g. a forge mod, /summon, etc)

I like it.

Fix what @kenzierocks and myself commented on above @Aaron1011 and conflicts.

@Zidane this looks good now, can it be merged?


Question's about sources

@miurla, What's the reason for using 5 sources? Why not use more? Is it for cost reason? Accuracy reason? Will there be more sources in future? Perplexity with pro search mode provides 16 sources, and Morphic is fully Open-source, so i thought maybe it can have 16 sources too? What's the plans to make Morphic search results more relevant, accurate, and up to date? Is it ok to be asking this here? 🙂

@miurla If you can't answer those, then no worries! 🙂 my main question is, why does Morphic research use 10 sources and normal Morphic uses 5?


Add ClockSystem

Requires #147
Resolves #144
This adds ClockSystem - a system that turns Drake Simulator's time into ROS Clock messages, and a convenience method AddClockPublisher (add_clock_publisher in Python) which adds the system and a publisher to a DiagramBuilder<double>.
I updated the iiwa_manipulator and multirobot examples to use the new system.

This change is

Drake's convention[1] is to have the "Add..." kinds of functions (which create an instance an wire it up in a DiagramBuilder) be static member functions on the class itself, akin to a factory function.  In our experience, that's a lot easier for people to find, and helps make it clear exactly what's going on.  I don't know if drake-ros wants to match that particular convention, but in any case I thought I'd mention it.
[1] For example:

https://drake.mit.edu/doxygen_cxx/classdrake_1_1systems_1_1lcm_1_1_lcm_scope_system.html#ad6fc9bbde61e385e95afbc2ec0e80201
https://drake.mit.edu/doxygen_cxx/classdrake_1_1geometry_1_1_meshcat_visualizer.html#a737291fe2f178eb125c8e9cb746af966

Work in progress, I'll open this for review once I've cleaned up CI and addressed the comments.

drake_ros_core/src/module_py.cc line 110 at r5 (raw file):
Previously, EricCousineau-TRI (Eric Cousineau) wrote…
nit This alias should be listed at declaration scope of translation unit (i.e., inside namespace, not function)

Done

drake_ros_core/src/drake_ros_core/__init__.py line 76 at r5 (raw file):
Previously, EricCousineau-TRI (Eric Cousineau) wrote…
nit (pre-existing) Can you do case-sensitive alpha-sorting here?

Done

drake_ros_tf2/CMakeLists.txt line 86 at r5 (raw file):
Previously, EricCousineau-TRI (Eric Cousineau) wrote…
I'm very concerned about calling ament CMake macros with leading underscores.
Can this (and related change below) be split into a separate PR?
Or is it still necessary?

Looks like that rule is not required anymore.

drake_ros_viz/CMakeLists.txt line 90 at r5 (raw file):
Previously, EricCousineau-TRI (Eric Cousineau) wrote…
Same as above.

Looks like that rule is not required anymore.

 I have requested a couple updates, but things look quite good overall. Thanks for iterating on this.

Reviewed 2 of 2 files at r11, 1 of 1 files at r15, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @EricCousineau-TRI and @sloretz)

drake_ros/drake_ros/core/qos_pybind.h line 23 at r15 (raw file):
Previously, EricCousineau-TRI (Eric Cousineau) wrote…
Agreed, these statements should be removed from this header.
drake_ros/core/clock_system.cc line 6 at r15 (raw file):

using drake_ros_core::ClockSystem;
using drake_ros_core::RosPublisherSystem;

Nit: Please update to the non-legacy namespace spelling of drake_ros::core.
Code quote:
using drake_ros_core::ClockSystem;
using drake_ros_core::RosPublisherSystem;

Done !


How-to for accessing sql server with FDW

Related to https://github.com/PostgREST/postgrest/issues/1214.
Using sql server with docker and creating an FDW is actually simple to show.

I've used tds_fdw before and it worked pretty good. We could add this as a how-to and allow users to extrapolate for other dbs. Or of course if contributions come for other dbs later that would be highly welcomed.


Slurm integration python2/3 confusion

The slurm integration scripts in plugins/SLURM-Integration are launched via the ufm-{prolog,epilog}.sh scripts which launch them by running python3. However the python scripts themselves contain the shebang path /usr/bin/python, which depending on the system setup, can still point to the old python 2.x interpreter. Can you please fix so that python 2.x is not used by accident e.g. when testing?
ufm_sdk_3.0/plugins/SLURM-Integration$ git grep usr/bin/python
ufm_slurm_base.py:#!/usr/bin/python
ufm_slurm_epilog.py:#!/usr/bin/python
ufm_slurm_prolog.py:#!/usr/bin/python
ufm_slurm_utils.py:#!/usr/bin/python

I agree with the assessment of @jabl, can we fix this please? In addition, python files that are not meant to be executed directly should probably not be executable (like ufm_slurm_utils.py), nor have a shebang at all (ufm_slurm_base.py and ufm_slurm_utils.py).
@anasbadaha @mike-dubman


New command: enable site classification

Enable site classification

command: graph siteclassification enable -c|--classifications <classifications> -d|--defaultClassification <defaultClassification> --usageGuidelinesUrl [usageGuidelinesUrl]
classifications: comma-separated list of classifications to enable in the tenant
defaultClassifications: classification to use by default
usageGuidelinesUrl: URL with additional information that should be displayed when choosing the classification for the given site
requires connection to the Microsoft Graph (#10)

For more information see the Enable-PnPSiteClassification cmdlet

More than happy to pick this one up.

W00t! All yours! 🚀

Hey @appieschot, are you still working on this command?

And we'll do a retry; happy to pick this one up :)

All yours!

Do you want to implement a -disable: flag on this method to disable site classifications, or do you want to have an additional command called disable site classification (as testing the creation without the option to delete is a bit weird)? If it is an additional command I would love to pick it up in the same PR.
Additionally we do have a property called GuestUsageGuidelinesUrl in the directorysettings. We could leverage that as in this same method as well.

Let's use a separate command for disable. If we don't have an issue for it, let's create one.
Good idea to include GuestUsageGuidelinesUrl 👍

@ypcode that would definitely make sense, do you have the command synced to your repo? I have the command implemented as well but do also need the tests and documentation :). You can find my implementation on: https://github.com/appieschot/office365-cli/tree/feature/enable-site-classification

Let me make sure it is, I will do it tonight

Here is the current state of this future PR : . As I said, the docs and testing are not done, will do it after being back from vacation after September, 10th.
I didn't check yours @appieschot , but maybe  we can have some sort of sync in each other PRs.
Will be more active soon :)
Cheers,
Yannick

@ypcode i just wrote my tests, but have a slightly different implementation than yours. I did use the PowerShell code sample, but will consolidate with your implementation to ease integration in the next release. The set requires one additional property (DefaultValue) as when enabling it, it requires the default value for usageGuidelinesUrl when it is not specified


fix: cleanup pg_wal as well before initializing a PVC

Closes #6264

E2e: https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/12160146785

E2E: https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/12162857497

/ok-to-merge green tests


Testnet v0.5.0-alpha

Description
Testnet v0.0.5
Items

10 minute block times to improve sync speed when demoing galaxy
Increase the number of validators
In v0.0.5 or v0.0.6, adapt https://explorecosmos.network/ to our needs

Sorry @faddat I got the semantic versioning guidelines wrong for our product. We should be on Testnet v0.5.0-alpha moving toward Testnet v0.6.0-alpha.

See https://semver.org/

Also.. can you add #18 to the list of requirements above? And let's make them checkboxes so that we can check them off as they are complete.  Thank you.


Update to native flux support with renovate configuration

See:
github.com/renovatebot /renovate/issues/5984
github.com/renovatebot/renovate/releases/tag/31.35.0
github.com/onedr0p/home-ops/commit/36ebe592e70ba61eeeb22cf26413263a5cb72081

#371 completed.