CLI not working on version 1.13.2

No valid exports main found for '/Users/victor/Desktop/test/node_modules/extract-files'
I get this error when I run npx graphql-codegen init

I think this was fixed in: https://github.com/dotansimha/graphql-code-generator/pull/3869
@VictorArowo can you please share a reproduction? I'm not sure why the error is config from extract-files...

It is npx @graphql-codegen/cli init. Not npx grapgql-codegen init

Error still persists with 1.13.2 and 1.13.3, but it works fine on 1.13.1.
@ardatan I don't think the command is the problem, since it works fine on 1.13.1

Seems the module extract-files used by apollo-upload-client was causing my issues. It probably has to do with change sintroduced in<EMAIL_ADDRESS>(https://github.com/jaydenseric/extract-files/releases/tag/v8.0.0).
Updated to NodeJS 13.13.0 and now everything works as expected.

I suddenly got this issue today. It worked just yesterday.

@tanduong can you please share a reproduction?

Thank @dotansimha for the response. I tried to reproduce but this is the best I got. Here is some of the commands:
> node -v
v10.15.3

> nvm use 13
Now using node v13.2.0 (npm v6.13.1)

> npx graphql-codegen
No valid exports main found for '/Users/tanduong/Code/nab-clone/node_modules/extract-files'

> rm -rf node_modules/

> npm i

...

> npx graphql-codegen
  ✔ Parse configuration
  ✔ Generate outputs

It seems delete node_modules and reinstall works. Here is my repo: https://github.com/tanduong/nab

I guess it's related to NodeJS version, as @farcasmihai91 found. So if you are changing your NodeJS version, you must reinstall deps in order to get this working.

Still having this issue
    "@graphql-codegen/cli": "^1.15.4",     "@graphql-codegen/introspection": "^1.15.4",     "@graphql-codegen/typescript": "^1.15.4",     "@graphql-codegen/typescript-apollo-angular": "^1.15.4",     "@graphql-codegen/typescript-operations": "^1.15.4",      "graphql": "^14.6.0",     "graphql-tag": "^2.10.3",     "graphql-toolkit": "^0.7.5",

Please avoid using this character ^ in package.json. That causes installing incompatible versions. We strongly recommend to use exact version.

Please avoid using this character ^ in package.json. That might cause having incompatible versions installed in the same project. So we recommend to use exact version.
Also graphql-toolkit has been deprecated, you can migrate to new graphql-tools instead :)
https://www.graphql-tools.com/docs/migration-from-toolkit

i'll give it a shot

I have tried deleting my node_modules folder and reinstalled with the following versions. Still having issues.
node v13.3.0
npm 6.13.1

    "@graphql-codegen/cli": "1.15.4",
    "@graphql-codegen/introspection": "1.15.4",
    "@graphql-codegen/typescript": "1.15.4",
    "@graphql-codegen/typescript-apollo-angular": "1.15.4",
    "@graphql-codegen/typescript-operations": "1.15.4",
    "graphql": "^14.6.0",
    "graphql-client": "^2.0.1",
    "graphql-tag": "^2.10.3",
    "graphql-tools": "^6.0.11",
    "apollo-angular": "^1.9.1",
    "apollo-angular-link-http": "^1.10.0",
    "apollo-cache-inmemory": "^1.6.6",
    "apollo-client": "^2.6.10",
    "apollo-link": "^1.2.14",
    "apollo-link-ws": "^1.0.20",
    "apollo-server-express": "^2.11.0",
    "apollo-utilities": "^1.3.4",

I see so please submit an issue by following the instruction on the template;
https://github.com/dotansimha/graphql-code-generator/issues/new?template=bug_report.md


The message received was unexpected or badly formatted

Error: error sending request for url (https://simplify.jobs/p/00a35a10-6b8b-4640-bb31-4b667138f90c/Full-Stack-Software-Intern): error trying to connect: The message received was unexpected or badly formatted. (os error -2146893018)
To replicate, create a Client using the default ClientBuilder and make a get request to https://simplify.jobs/p/00a35a10-6b8b-4640-bb31-4b667138f90c/Full-Stack-Software-Intern without changing anything. It should return an Error.
Do not add any features.

Have you tried searching for that error code? It looks like a Windows TLS error.

Yes I have searched for that issue but I don't really understand what to do based on what I've found. After all, I am able to open this website just fine on web browsers.

I have also had this issue. It seems to work fine with other request libraries (I tried ureq)

This a TLS error on Windows. Without significantly more details showing reqwest is doing it wrong, there's nothing we can do.

When I use reqwest to post file to https service face the same problem on window server 2012rc. How can I solve it?

Same problem here.
Solved by

enabling rustls-tls feature
calling builder method use_rustls_tls() when building client (See https://docs.rs/reqwest/latest/reqwest/tls/index.html)

Same problem here.
Solved by

enabling rustls-tls feature
calling builder method use_rustls_tls() when building client (See https://docs.rs/reqwest/latest/reqwest/tls/index.html)

help a lot!


Add nofollow flag to footer social links

Description
Add nofollow flag to footer social links to support https://teamds.atlassian.net/browse/DSPL-24.
Motivation and Context

Screenshots (if appropriate)
Upgrade notes (if appropriate)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue) labeled with bug
[x] New feature (non-breaking change which adds functionality) labeled with enhancement
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code standards of this project.
[ ] My change requires updating the documentation. I have updated the documentation accordingly.

Codecov Report

Merging #490 (ad1b645) into main (aeb56b0) will increase coverage by 0.09%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #490      +/-   ##
============================================
+ Coverage     65.31%   65.41%   +0.09%
- Complexity      144      145       +1
============================================
  Files            28       28
  Lines           346      347       +1
  Branches         29       29
============================================
+ Hits            226      227       +1
  Misses          104      104
  Partials         16       16

Impacted Files
Coverage Δ

...e/components/models/SingleSocialLinkComponent.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or a supporter signed this repo up for Open Collective. This pull request adds backers and sponsors from your Open Collective https://opencollective.com/autokeras ❤
It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets
P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).
Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

Pull Request Test Coverage Report for Build 1074

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.2%) to 93.852%

Files with Coverage Reduction
New Missed Lines
%

autokeras/nn/model_trainer.py
1
92.57%

autokeras/net_transformer.py
1
94.05%

autokeras/nn/graph.py
2
96.8%

autokeras/nn/layer_transformer.py
4
96.08%

Totals

Change from base Build 1072:
-0.2%

Covered Lines:
2809

Relevant Lines:
2993

💛  - Coveralls


Still cannot make when package name is scoped (on Windows)

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.2.0
Electron version
v28.1.0
Operating system
Windows 10 (version 22H2)
Last known working Electron Forge version
No response
Expected behavior
npm run male should run without error even when the name in the package.json is scoped e.g. like @cwellsx/apis
Actual behavior
[STARTED] Making distributables
*** appName is @cwellsx-apis
[STARTED] Making a squirrel distributable for win32/x64
[FAILED] ENOENT: no such file or directory, open<EMAIL_ADDRESS>[FAILED] ENOENT: no such file or directory, open<EMAIL_ADDRESS>
An unhandled rejection has occurred inside Forge:
Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>
Steps to reproduce
First lines of package.json looks like this
{
  "name": "@cwellsx/apis",
  "productName": "",
  "version": "1.0.0",

Additional information
This was supposedly fix here I still see this problem:

Make / Package should work with scoped package names #1745
This comment implies that they too still have this problem

I looked at the fix/commit linked to that issue, it seems to be mostly this:
const appName = filenamify(forgeConfig.packagerConfig.name || packageJSON.productName || packageJSON.name, { replacement: '-' });

I edited the<EMAIL_ADDRESS>to log the result of that line of code:
                const packageJSON = await (0, read_package_json_1.readMutatedPackageJson)(dir, forgeConfig);
                const appName = (0, filenamify_1.default)(forgeConfig.packagerConfig.name || packageJSON.productName || packageJSON.name, { replacement: '-' });
                console.log(`*** appName is ${appName}`)

As shown in the Actual behaviour above, that line of code is running as expected and filenameifying the name.
However the make still fails.
I don't know how you tested your fix but, given the package.json you attached, perhaps you only tested it on linux.

Also seeing this.

this may be helpful:
Problem when name in package.json includes @ (monorepos) · Issue #8248 · electron-userland/electron-builder, https://github.com/electron-userland/electron-builder/issues/8248


Share to meeting in stage view sample

Executed build pipeline: https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/3779646685
Status:

Executed build pipeline again: https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/3788668817


Don't exit with error code 1 if pin of formula exists

[X] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[X] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[X] ran brew update and can still reproduce the problem?
[X] ran brew doctor, fixed all issues and can still reproduce the problem?
[X] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Wanted to get my system up to date.
What happened (include command output)

Command output

alex@Alexander-MacBookPro:~$ brew update; brew upgrade; echo Exit code: $?
Updated Homebrew from 755123d2c to 5abce1b51.
Updated 3 taps (homebrew/cask-versions, homebrew/core and homebrew/cask).
==> Updated Formulae
terragrunt ✔   ammonite-repl  angular-cli    cocoapods      helmfile       istioctl       lxc            presto         typescript     yarn
Error: Not upgrading 1 pinned package:
terragrunt 0.19.3
==> No packages to upgrade
Exit code: 1

What you expected to happen
It should have exit with a code of 0, as it's not an error. A user set a
pin and brew is now behaving as expected; it updated a formula, but
not the installed package.
If there were other formulae that have been updated and all went well, then
this exit code "1" sending a wrong information.
Step-by-step reproduction instructions (by running brew commands)
brew pin $some-package
# wait for some-package to be updated
brew update
brew upgrade

It is an error as we did not upgrade anything despite there being outdated passand you ran brew upgrade. Homebrew considers the command-line status codes part of our API so to change this would be a breaking change. Passing on this, sorry.

Well, but OTOH it behaved exactly as expected - all the packages that could be upgraded were upgraded.
But yes, I guess that fixing/changing this might have a lot of consequences that aren't so easy to foresee.


Add template references to other transformed values of the same row

Possible syntax (look at tr):
tables:
  - name: users
    rules:
      login:
        username: {}
      preferences:
        template:
          format: '{"some_complex_json": {"field": "{{tr.login}}"}}'

Tera allows also tr["login"].
The name tr means "transformed row". We can use tr_row or transformed_row instead (it might be too long).
We can also use just row, but what if in the future we decide to use the values of the original row too?

@akirill0v, what do you think?

It is great idea! My suggestion for naming is:
prev.login - original field value
final.login - finally transformed value (after all pipelines processing)

I started to work on this - https://github.com/datanymizer/datanymizer/pull/41

It is ready.


[Codegen 100] Unify findComponentConfig return statement

Summary

[Codegen 100] Create a createComponentConfig function in the parser-commons.js file. It takes the foundConfig and the commandTypeNames as parameters and returns the component config object. Extract the return statements (Flow TS) and use those implementations in that function.

Part of Issue https://github.com/facebook/react-native/issues/34872
In case I should already add better typing I can update the PR while clarifying the type definitions.
Changelog
[INTERNAL] [CHANGED] - Move the return statement of findComponentConfig to parsers-commons.js merging Flow and TS implementation.
Test Plan
yarn lint && yarn run flow && yarn test react-native-codegen

@marcocaldera Please note that there is a conflict with the main branch, could you try to rebase and resolve? Thanks!


fix: kv:key get

The api for fetching a kv value, unlike every other cloudflare api, returns just the raw value as a string (as opposed to the FetchResult-style json). However, our fetch utility tries to convert every api response to json before parsing it further. This leads to bugs like https://github.com/cloudflare/wrangler2/issues/359. The fix is to special case 'raw' requests to simply send the text through.
Fixes https://github.com/cloudflare/wrangler2/issues/359.

@petebacondarwin does this look like a good approach?

I redid the approach as discussed, would like a fresh set of eyes before I land it.


Need to provide additional args to InferenceClient

I'm using huggingface.chatCompletion and need to be able to provide some cookies to the InferenceClient. I don't see a way to pass that in via create(), which is where the client is instantiated. I also looked at the huggingface_hub implementation, but didn't see a way to set it via module member or environment variable.
The approach I landed on was adding a module-level client_args dictionary, similar to huggingface.api_key and .prompt_builder, and passing anything defined in there when the client is instantiated. If that makes sense and you want to support this, I'm happy to open a PR. Or if you see issues or have suggestions to improve, let me know.

Hello @dylan-stark,
Currently there is no way to customize the InferenceClient.
If you want to can create a PR with a recommendation on how to add those.

Hi @philschmid. I opened PR #45. It's working well for me in practice. If there are some changes you'd recommend, I'm happy to make them.

Hi @philschmid. I opened PR #45. It's working well for me in practice. If there are some changes you'd recommend, I'm happy to make them.


append shortcut

Hello
How to add shortcuts to existing shortcuts?
Default shortcuts are removed when I set the shortcut.

Hello @Mohammad99k
At this time, this is not possible.
When adding new shortcuts, the existing shortcuts are removed.

I hope you add this option
thank you


Spinlock improvements

test and test-and-set
pause instruction for gnuc (TODO: other platforms)

Failures are because std::atomic_flag::test isn't available...could just use std::atomic<bool>


Setting locale from AsyncStorage (or some other storage)

Hi I have this code in my index.js
import React, { Component } from 'react';
import { AsyncStorage } from 'react-native';
import { Container, Text } from 'native-base';
import { Root } from './config/router';
import I18n from 'react-native-i18n';
import ReactNativeI18n from 'react-native-i18n'
import en from './shared/assets/i18n/en';
import ko from './shared/assets/i18n/ko';

const deviceLocale = ReactNativeI18n.locale;
const prefix = 'ov_';

I18n.fallbacks = true;
I18n.defaultLocale = 'en';
I18n.locale = 'ko';
console.log('set languages');

_setLanguage(); // TODO: still not working for Android

// I18n.locale = deviceLocale;
I18n.translations = {
  en: en,
  ko: ko
}

async function _setLanguage() {
  try {
    var languageSaved = await AsyncStorage.getItem(prefix + 'language');
    if (!languageSaved) {
      // if not found, then get the device language
      languageSaved = deviceLocale;
    }
    I18n.locale = languageSaved;
    console.log('got language: '+languageSaved);
  } catch (error) {
    console.log('did not find saved language,, it will just proceed with deviceLocale');
  }
  return new Promise((resolve, reject) => resolve());
}

class App extends Component {
  constructor() {
    super();
  }

  render() {
    return (
      <Root />
    );
  }
}

export default App;

This seems working with iOS after user changes the language from the App and restarting the app. However, in Android it doesn't work, because I18n.locale = XXX is done after the application is in running state. Any help? I'm very newbie to React native..

It seems to be working for me. We use realm in our project.
`
// src/helpers/Translator
import I18n from 'react-native-i18n';
import en from '../locales/en';
import nb from '../locales/nb';
I18n.fallbacks = true;
I18n.translations = {
en,
nb
};
I18n.locale = getUserPreferableLocale();
function getUserPreferableLocale(){
let lang = realm.objects('SettingsItem').filtered('key = "app_language"')[0];
//if is not set in db, set to default 'en'
if(!lang) {
lang = 'en';
}
return lang
}
export default I18n;`
And then I use it in components:
import I18n from './helpers/Translator'; //.... <Text style={styles.subHeader}>{I18n.t('greeting')}</Text>

@anrus i think that has no issue because the storage returns synchronously.

Used realm as well. Problem was accessing the AsyncStorage was just too slow when app launched. Realm seems extremly fast. Thanks for the tip @anrus


fix: get nic interface only, not whole string.

provided by: https://askubuntu.com/questions/1085789/default-route-interface-name

CI failures are unrelated and already being worked on in #13137.


wasm-pack tutorial out of date #174

Link to old issue
Issue Opened by @mgattozzi
This was brought up in the example repo and the code has been updated there but we need to also update the code in the tutorial here.
mgattozzi/wasm-add#1 (comment)
@adityac8 said they would do this and update the book here.

The wasm-pack tutorial moved into the wasm-pack repo, please refile this issue there if it is still relevant.


storage:change configuration storage.max-key-size default value from 4096 to 8192

What problem does this PR solve?
Issue Number: close #11241
Problem Summary:
Create a table from tidb-server successfully, but insert data failed if it has the length over 4096.  Set the default value of storage.max-key-size to 8192 and It insert data successfully.
What is changed and how it works?
What's Changed:
Change the default value of storage.max-key-size from 4k to 8k.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test

Side effects
Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with None.

/run-test

/run-test

/run-test

/run-test

@TonsnakeLin You have to use git commit -s --amend to modify your last commit message to contain close #11241 and add a signoff.

Should change the value in test_serde_custom_tikv_config and tests/integrations/config/test-custom.toml.
https://github.com/tikv/tikv/blob/999ca556005ed5c3b7ccbceb511806a5da365c45/tests/integrations/config/mod.rs#L615

got it！

/run-test

/run-test

/run-test

@youjiali1995 @sticnarf please review or approve, thanks

Please change https://github.com/tikv/tikv/blob/225bbdd70ea128040827a9a45d18c8518315ff12/tests/integrations/config/test-custom.toml#L83 to a different value and also change the related tests. Otherwise, we cannot verify the config can be customized successfully.

Should change the value in test_serde_custom_tikv_config and tests/integrations/config/test-custom.toml.
https://github.com/tikv/tikv/blob/999ca556005ed5c3b7ccbceb511806a5da365c45/tests/integrations/config/mod.rs#L615

Looks that this comment is still not addressed?

/merge


PotreeConverter.exe - Entry Point Not Found Error

Hello,
I can't seem to get the newest converter (1.3) to run.  I get this error when I run PotreeConverter.exe

I humbly admit my technical ignorance, but I never had this issue on previous iterations, which still seem to work.  Thanks!

Hi,
According to this source it may be because you have an old version of the VC++ redestributable installed: http://www.tuniac.org/forum/viewtopic.php?t=102
Try to install the redistributable from here: https://www.microsoft.com/de-de/download/details.aspx?id=48145
Let me know if it works!

Yes, that worked!  Thank you.
Just crushed a test point cloud out in 5 minutes (145m points to 41m).  Love the new EDL setting, it really helps define the objects!

Great! Send me a link when you're putting something online!


Configure host name for the local dev server

Expected Behaviour
Have a configuration option to modify default host name the local development server runs on. Today it is always localhost.
Should work for both aio app run and aio app dev.
Similar to the HOST env var in create React script https://create-react-app.dev/docs/advanced-configuration/.
Actual Behaviour
Local dev server always runs on localhost with no option to change that.
Reproduce Scenario (including but not limited to)
Run aio app run or aio app dev and observe your static content served from https://localhost:PORT.
Steps to Reproduce
See above.
Platform and Version
All platforms.
Sample Code that illustrates the problem
N/A
Logs taken while reproducing problem
N/A

PR https://github.com/adobe/aio-cli-plugin-app-dev/pull/90


Permission denied error after latest update #113

Hey mate,
For, https://github.com/linuxserver/docker-radarr/issues/113, could you re-fire the build for radarr-sma:nightly please?
Thanks mate.

Triggered, give it a little time to build


Fix property of mountTarget

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

This aligns the spec to the actual response. Address an issue users have been having with the GO SDK.
Updates mountTarget proeprty to correct type and add missing fields to mountTargetProperties that are in the response.

@audunn, can you please have the code owner review this change since it's a bug fix?

@akning-ms , this is a bug fix for GO SDK and @ArcturusZhang signed off on this. Please force merge this PR.


Move docs folder

Solves issue #495
Moved documentation from inside cornflow-server folder to root folder.
Updated documentation.
Changed documentation theme.

@pchtsp do you want to review the docs/source/main/install.rst file?
I'm going to keep working on updating the rest of the documentation, but I would like to know if you miss something on the installation part of the documentation.


[Select] Add animation support when position="popper"

Hi there,
I am using the Select component and trying to apply animations with framer-motion. But unfortunately, exit animations are not working since there is no forceMount prop that I should use, unlike other components that do have this prop.
Hope to see this prop eventually on the Select component aswell. Thanks a lot.

Hey @gino yes you are correct this is something we didn't have time to do yet and we wanted to prioritise releasing the positioning update as it was a longstanding issue. We will look at adding this soon.

Hi @benoitgrelard,
Any updates on this?
I find it weird all other components supports the exit animation but not Select. But in my case I'm just using Tailwind with CSS animations (data-[state=open]:animate-fadeIn data-[state=closed]:animate-fadeOut).

Could you please tell me if there is an understanding when it will be possible to adjust the unmounted animation in the Select component? data-state=closed also doesn't work

+1
I really need it

+1

Any updates on this?
I wasted half of my day to get this working. Just now discovered that it is not supported.

Any updates?


Need validation on adding/removing users on the user management page

When you add a new user there's no indication if it failed or not. Same with removing.

Is this resolved now? If not, let's chat.

There is no visual indicator that something went wrong. It shouldn't be too hard to add though.


Lyric support

This is my start-to-finish feature request #349; I believe I have done it in a similar way to LebreSpot.
Currently what I have done is implement the API request and a very rough UI for it. Many improvements are needed for the UI, but currently, there is a new button at the bottom left that redirects you to a page called lyrics when you click it.
I want to implement time-synced lyrics, which shouldn't be too hard.
I would say its about 50% complete.

This looks great, I would also think we should have a right click to lyrics too? Maybe that's too much? I'm also fine with not having the time syncing with the lyrics which I think might be difficult to render properly and cause CPU cycles?

I think having it just as a toggle button makes more sense?

Yeah that could be a nice alternative to having the line highlighted and listening for the playback location. We could just click and seek to the location defined by the lyric at that time. We would need to make sure that the lyric displayed is always connected with the current song being played. Otherwise you might see a lyrics screen for another song? I think that could be okay, we just need to make sure that clicking on the lines will only seek if the song being played is that same song.

Looks close!

Clicking on the line to select the timestamp it seems to work well
The text seems a little bit small maybe we could try with text medium rather than text small
It would be nice to have some title of the song along with the artist and album at the top of the page so there's at least some indication as to where the lyrics are coming from

Other than that, I think it's ready to go.

@jacksongoode I could do a similar thing to what we have ATM with the album view.

I added caching and better formatting with the titles so I think this is all read for review.

Hello, I undid your changes to the client file as you removed the deserialization part, which made it impossible to get any songs. Also, I'm pretty sure the way you cached does essentially the same thing as the load_cached function. Do correct me if I'm wrong.
Other than that I think this is looking very good, I will add some of the song information and change the lyrics icon (that was just a placeholder).

I just reverted the methods that we didn't need.
One nice thing I think would be if the user clicked on the Show lyrics button, it would actually toggle the lyrics as opposed to showing them. This could be introduced here if you feel like you have a good sense of how to do it, or we can add it in another PR. It just seemed redundant to have the lyrics button do nothing if you're already on the lyrics page. It seems intuitive that it should be a toggle.

Ok I will have a look into this tomorrow!

I can't quite figure out how to do it. I need to have AppState as a lens for the button to see the history of navigation, and I can't figure out how to implement that without causing many errors or rewriting a lot of the code.
So maybe it's a good idea to open up a separate issue for it.

@SO9010 I just figured out a simple way of doing it. I'll merge once the builds work.


lnd 0.11.1: allow custom macaroon to be used instead of requiring all subserver macaroons

Addresses the problem described in https://github.com/lightninglabs/loop/issues/299.
This PR adds two functionalities:

Allow one custom macaroon to be specified (by providing CustomMacaroonPath instead of MacaroonDir in NewLndServices) instead of needing to have all lnd macaroons in the same directory. This allows users to use the admin.macaroon or a custom baked one.
To make it easy to get a "macaroon recipe" for all required subservers, a new helper function MacaroonRecipe is added. This requires the lnrpc.Lightning.ListPermissions RPC which was only added in lnd v0.11.1.

NOTE: This PR is against the lnd-11-1 branch as it requires a compile-time dependency to that version. This code can also be used with older lnd versions but then the MacaroonRecipe function will throw an error.

Thanks for all the good input, I addressed all comments.
As mentioned, this bumps the requirement for lnd to v0.11.1-beta and is therefore on its own branch. But after merging this, I'll cherry pick the commits 3b8f3521, e9d23751 and bc071235 to master and create a new tag. That way we can use the easier macaroon usage without needing to update lnd necessarily.


working with own API

Is langchain supporting our own api interaction or currently only the ones in examples?

the issue is still relevant


[Java] serialize to output stream is limited to 2GB

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Version: 0.4.1
OS: Windows
JDK: 21
Component(s)
Java
Minimal reproduce step
public static void main(String[] args) throws Exception {
	Fury fury = Fury.builder().requireClassRegistration(false).build();
	try (OutputStream output = new BufferedOutputStream(Files.newOutputStream(Files.createTempFile(null, null)))) {
		fury.serialize(output, new BigObj());
	}
}

static public class BigObj {
	public byte[] b1 = new byte[Integer.MAX_VALUE/2];
	public byte[] b2 = new byte[Integer.MAX_VALUE/2];
}

What did you expect to see?
I was hoping to get a file with<PHONE_NUMBER> bytes, all zero.
What did you see instead?
Exception in thread "main" java.lang.NegativeArraySizeException: -2147483510
	at io.fury.memory.MemoryBuffer.ensure(MemoryBuffer.java:1980)
	at io.fury.memory.MemoryBuffer.writePrimitiveArrayWithSizeEmbedded(MemoryBuffer.java:1946)
	at io.fury.serializer.ArraySerializers$ByteArraySerializer.write(ArraySerializers.java:290)

Anything Else?
I think when providing an OutputStream to the serialize method the intermediate MemoryBuffer should behave like the buffer inside the BufferedOutputStream. When the buffer is full it should flush its content to the underlying OutputStream in order to free up its bytes.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Fury need to go back in the buffer to update some header in some situations. In such cases, flush ahead is not possible. In the long run, we may be able to streaming write if we provide options to disable such look back.
But could you share which cases you need to serialize such big object? It's rare in a production environment, and protobuf don't support it too

We have quite large files on disk and can not use protobuf because of the 2GB limitation. Thats why we where looking for alternatives: fast serialization with cross-language support. I feel in the future if we store machine learning embeddings in a column based style to a file, the 2GB limit will be a problem quite a lot.

We have quite large files on disk and can not use protobuf because of the 2GB limitation. Thats why we where looking for alternatives: fast serialization with cross-language support. I feel in the future if we store machine learning embeddings in a column based style to a file, the 2GB limit will be a problem quite a lot.

This is interesting, if embeddings are storaged, we may need larger limitation. Could we split a big object into some small objects for serialization. I mean, you can serialize like this:
Fury fury = xxx;
OutputStream stream = xxx;
fury.serialize(stream, o1);
fury.serialize(stream, o2);
fury.serialize(stream, o3);

Then for deserializaion, you can:
Fury fury = xxx;
FuryInputStream stream = xxx;
Object o1 = fury.deserialize(stream);
Object o2 = fury.deserialize(stream);
Object o3 = fury.deserialize(stream);

If we can't split an object graph into multiple serialization, then we do need to support larger size limit

In our case we have a file with meta information and embeddings of several millions images. All the embeddings are stored in column-based styles for fast access and distance calculations. The embeddings are around 1000 dimensions, which means we can only store 2 million images in one file otherwise just the embeddings alone are to large for fury.

Why not split this file intom smaller files

It is just a hassle, right now the meta information of all images are stored in row-based styles. Then the embeddings information of all the images are in column based. I see three options with the current fury implementation:

Store meta information and embeddings in seperate files, and split the embeddings file in smaller files to cirumvent the 2GB limit
Keep everything in one file, but creates additional files if its breaks the 2GB barrier
Store everything in row-based format and split the files

For 2 and 3 we would need to keep track how big the file already is to make a sensable split (not splitting the meta data or embedding of an image into two files). Finding a good splitting point for option 1 is more straight forwards since the number of embeddings fitting into one file can be calculated in advanced. Ideal memory allocation and ordering of data would need more consideration, if data is stored in multiple files.


Move checklist listener management to helper to prevent duplicate events

Background
As it stands now, making multiple instances of <LexicalCheckListPlugin> (e.g. with two editors on one page) will instantiate separate instances of let listenersCount = 0 and therefore both (or all) of the editors will separately register document-level event listeners for click and pointerDown.
Repro
Make an even number of editors in one page, each with the checklist plugin. An even number of listeners are registered on the document. When a checkbox is clicked an even number of handeClicks are fired and the checkbox is toggled an even number of times. From a user's perspective the box does not change on click.
Notes
Does the fix make sense and work? This was the best fix I found but happy to implement a different way if preferable.

Thank you!


Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 7bcad4ad-f730-4c1b-a6eb-0fba236b0abe

Issue

I have moved my lamps from a Lightify and a Hue v2 bridge to deCONZ, unfortunately the hoobs log file always says that there are already devices. I took both old bridges out of the network and removed all lamps separately.
I also deleted the accessories folder, no success.
I tried the whole thing on two different homebrideges.
Thank you for your help
Log Messages

Debug Files

[Hue] Initializing Hue platform...
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] homebrige-hue v0.11.46, node v12.16.1, homebridge v0.4.50
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] warning: not using recommended node version v7.0.0 LTS
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] warning: not using recommended homebridge version v0.4.22
[Homebridge] [3/21/2020, 1:13:46 PM] Loading 0 accessories...
[Homebridge] [3/21/2020, 1:13:46 PM] Load homebridge-mi-airpurifier.MiAirPurifierPlatform
[Homebridge] [3/21/2020, 1:13:46 PM] API launched
[Homebridge] [3/21/2020, 1:13:46 PM] [Ferseher im Büro] is running on port 42758.
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] npm registry: status 404 Not Found
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: dresden elektronik deCONZ gateway v2.5.75, api v1.16.0
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: warning: not using recommended deCONZ gateway version undefined
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Daylight: set homekit sunrise from undefined to Sat Mar 21 2020 06:34:01
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Daylight: set homekit sunset from undefined to Sat Mar 21 2020 18:48:31
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Daylight: set homekit light level from 0.0001 lux to 100000 lux
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: 12 accessories
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] masked debug info dumped to /hoobs/etc/homebrige-hue.json.gz
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Initializing platform accessory "Conbee2-Hue".
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: 2 services
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Initializing platform accessory "WZ Fernseher".
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Initializing platform accessory "Configuration tool".
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 7bcad4ad-f730-4c1b-a6eb-0fba236b0abe
at Bridge.Accessory.addBridgedAccessory (/hoobs/node_modules/@hoobs/hap/lib/Accessory.js:268:13)
at Server. (/hoobs/node_modules/@hoobs/homebridge/lib/server.js:380:26)
at /hoobs/node_modules/@hoobs/hap/lib/util/once.js:16:19
at /hoobs/node_modules/@hoobs/hue/lib/HuePlatform.js:293:5
at Function.then (/hoobs/node_modules/deferred/_ext.js:65:13)
at Deferred._settle (/hoobs/node_modules/deferred/deferred.js:93:26)
at Deferred.resolve (/hoobs/node_modules/deferred/deferred.js:138:15)
at Function. (/hoobs/node_modules/deferred/ext/promise/catch.js:29:4)
at Deferred._settle (/hoobs/node_modules/deferred/deferred.js:93:26)
at Deferred.resolve (/hoobs/node_modules/deferred/deferred.js:138:15)

[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] homebrige-hue v0.11.46, node v12.16.1, homebridge v0.4.50
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: dresden elektronik deCONZ gateway v2.5.75, api v1.16.0

You're running a (too) old version of homebridge-hue against a (too) new version of deCONZ.
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] npm registry: status 404 Not Found
[Homebridge] [3/21/2020, 1:13:46 PM] [Hue] Conbee2-Hue: warning: not using recommended deCONZ gateway version undefined

It's beyond me why the hoobs people think it a good idea to mutilate homebridge-hue and break the version checks.  Please contact them on how to upgrade homebridge-hue in hoobs.

Thank you very much. That's it.
i have turned a hoobs installation into a normal homebridge installation and it works.
it should not be HOOBS but HIOOBS called Homebridge issues out of the box :)


Refactor Kafka User v2 to v3

a new version (v3) of Kafka User v2 has appeared on the Instaclustr API v2 doc.
The endpoint of Kafka User v2 has been changed, the structure has been changed as well. I think our operator should be adjusted for these new changes.
Just in case, I asked in the team-customerplatform about the need to use a new endpoint, but my guess is it's better to use the Current version.

Got a response:

Kafka team added userV3 and deprecated userV2
https://instaclustr.redoc.ly/Deprecated/tag/Apache-Kafka-User
userV3 is recommended while userV2 is still usable

Received a reply from the team-customerplatform member Long Hoang:

Kafka team added userV3 and deprecated userV2
https://instaclustr.redoc.ly/Deprecated/tag/Apache-Kafka-User
userV3 is recommended while userV2 is still usable

ref https://github.com/instaclustr/operator/pull/583


Can this be used to hide that USB debugging is enabled?

I have noticed quite a few apps are now checking if USB debugging is enabled and refusing to run if it is.  Someone said this could be used to hide that and allow them to run without having to disable USB the debugging setting but I couldn't find any instructions on how to do so.

They're probably talking about changing the props related to ADB/USB Debugging. If USB debugging is enabled, the following three props are set to adb:
persist.sys.usb.config
sys.usb.config
sys.usb.state
But if USB debugging is disabled they are all removed, which suggest that if you use the module to delete those props you'll remove the possibility for apps to detect if USB debugging is enabled. But, you'll also effectively disable USB debugging... It's exactly the same thing as if you'd go into Developer options and disable the toggle.
To keep the option enabled but hidden from apps you'd have to use more advanced stuff (Riru/Xposed/EdXposed/LSPosed).
Once the next Magisk release is here I've been playing with the idea to maybe lookig into zygisk and implement this kind of stuff into the module, but that's not going to happen anytime soon.

Unfortunately I can and have done all that with tasker (by running the command "settings put global adb_enabled 0" as root, then setting it back when the app is not running) but I was hoping there was a way to hide it without disabling it as the only xposed module I found for doing so doesn't work with the app in question.

@nl255 To me, the Tasker way of doing it sounds like the simplest way... Is it that important to keep USB debugging enabled?


[Feature Request]: Teachability should be able to delete or update memories

Is your feature request related to a problem? Please describe.
i was wondering if there have been plans to make the teachability module forget things, as its sometimes hallucinating new memories that break the consistency of the responses
for example it might sometimes hallucinate a feature of saturn chat that we dont have (like voicechat which is not going to be supported), and that is saved to memory. after this we cant "delete" that wrong memory and the agent goes off rails every so often when this bad memory is retrieved, another usecases come to mind but just wanted to know if this "delete memory" feature has been a though about
Describe the solution you'd like
another usecase is "update memory" sometimes a question-answer pair in teachability can have appended or more up to date information
Additional context
No response

related: #150


Charts Padding Issue

Hello, do you have any suggestion why this happened and can you suggest where I should look for the padding for this chart. I have spent some time, tried to change some values but nothing worked.
Thank you.

I fixed, problem was frame/bound :)


RED-45: Reference base Docker images via digest

So that we can have confidence our base images aren't being changed without our
knowledge, reference them by digest instead of tag (as tags are not immutable).
Also, add a comment detailing the tag the digest corresponds to.

Merging with red master because the failure there is unrelated (gcc8 failing to build naxsi/nginx)


Application crash on "failed ID -> Try again"

Bug Description
If the ID creation failed, user gets dialogue with three options: "Try again", "Contact support", "Cancel". If user selects "Try again" application crashes.
Steps to Reproduce
In attempt to create new ID, make creation with Notabene failed.
Wile waiting for ID to be valid (pending validation), just wait while observing Accounts page.
After the dialogue appears select "Try again".
Expected Result
Create ID flow should be reinitiated.
Actual Result
Application crashes.
https://user-images.githubusercontent.com/98821384/175103379-c0332998-627a-4303-9cbe-d342dfe1f6d4.mp4
Versions

Software Version: Testnet app 3.0.0 (50)
OS: iOS 15.5
Mobile device, if applicable: iPhone SE

I've managed to find the cause for this issue, and several other similar issues that boil down to the same problem: Once an identity is deemed invalid we remove related accounts from out database. Our database objects are what are called "live objects" so they auto update when the database changes, but if you try to access them after they are removed the app crashes. The crash you are seeing is a result of this. There are ways to mitigate this by verifying that objects have not been removed before access, but doing this in every case is a very big task. I would worry that implementing it would break more things than it fixes, so it might be worth pushing this issue until after 3.0.0.

Yep, agreed. Let's wait.

Other related issues in jira.


Update main.ts to config/lodash.merge setup & update main config for development

To sync with changes made to https://github.com/obewds/vite-vue-ts-compo-pkg-starter:

[x] Run obsolete and update:

Run the obsolete command to check for packages to updates:
npm obsolete

You can either update dependencies manually (copy/paste from npm obsolete into ./package.json), or if things are all clear to update and you want to do it all at once programmatically, use:
npm update --save

[x] Remove obewds.tw.config.json:

Remove the file obewds.tw.config.json if it exists (especially if it has ...colors.info or ...colors.caution classes)

[x] Install a new obewds.tw.config.json file from the dependency package for it:

npm explore @obewds/obewds-tw-config -- npm run install:config

[x] Find and replace in new obewds.tw.config.json file:

Find rose replace with pink
Find blue replace with cyan
Find violet replace with orange
Find green replace with lime

[x] Install these packages:

npm install lodash --save-dev

npm install @types/lodash.merge --save-dev

[x] Change the file ./src/main.ts:

From this:
// import tw from '../obewds.tw.config.json'

const app = createApp(App)

// app.provide('tw', tw)

To this:
// import merge from 'lodash/merge'
// import { ObewdsTwConfig } from '@obewds/obewds-tw-config'
// import appTwConfig from '../obewds.tw.config.json'

const app = createApp(App)

// const tw = Object.keys( appTwConfig ).length > 0 ? merge( ObewdsTwConfig, appTwConfig ) : ObewdsTwConfig
// app.provide('tw', tw)

And this is an active version without comments. What happens here, is the user config is merged with the default config with the user one being the dominant and outputted. Otherwise if no content is found in the user config, then the output default to just the default config:
import merge from 'lodash/merge'
import { ObewdsTwConfig } from '@obewds/obewds-tw-config'
import appTwConfig from '../obewds.tw.config.json'

const app = createApp(App)

const tw = Object.keys( appTwConfig ).length > 0 ? merge( ObewdsTwConfig, appTwConfig ) : ObewdsTwConfig
app.provide('tw', tw)

issue was resolved


Tracking issue for kage MVP

This is the tracking issue for kage MVP. Below are the requirements to achieve our first goal of making kage compatible with age.
API requirements
The requirements are divided into 3 sections - AgeFile, AgeKey, and Age Client. Once all the requirements are complete we will be able to generate age keys and use those keys to encrypt and decrypt data.
AgeFile

[x] Implement methods to parse AgeHeader
[x] Implement methods to write AgeHeader
[x] Implement methods to parse AgeBody
[x] Implement methods to write AgeBody
[x] Implement methods to parse AgeFile
[x] Implement methods to write AgeFile

AgeKey

[x] Implement methods to parse AgePublicKey
[x] Implement methods to write AgePublicKey
[x] Implement methods to parse AgePrivateKey
[x] Implement methods to write AgePrivateKey
[x] Implement methods to parse AgeKey
[x] Implement methods to write AgeKey

Age Client

[x] Implement methods to parse and generate X25519 recipients
[x] Implement crypto methods for X25519 recipients
[x] Implement methods to parse and generate X25519 identity
[x] Implement crypto methods for X25519 identity
[x] Implement a method that takes plaintext and a list of recipients and returns an AgeFile object
[x] Implement a method that takes an AgeFile and an identity and returns the decrypted data
[ ] Implement convenience methods for library users
[ ] Document public API

Final validation

[ ] Pass all tests from the C2SP/CCTV age test suite

Could you clarify a bit the following points:

[ ]  Implement a method that takes plaintext and a list of recipients and returns an AgeFile object
[ ] Implement a method that takes an AgeFile and an identity and returns the decrypted data

So, the AgeFile includes a body: ByteArray, should contain plaintext or encrypted data?
Also related, IMO AgeFile#body should be an InputStream, otherwise we'll have to copy the entire blob to memory? But this would also mean that equals and hashCode could not be implemented for AgeFile.

[ ] Implement methods to parse AgeKey
[ ] Implement methods to write AgeKey

These seem to already be implemented. Is there something missing? Maybe a test for AgeKey write?

Hey @simao
For AgeKey, you're correct. It is already implemented, I'll write the missing test and mark that as complete.
For AgeFile, I believe your point around copying the whole blob in memory is valid. My initial idea was that AgeFile should contain the encrypted data at first. We can then have a decrypt extension method on it. That would still be possible with an InputStream, but we won't be able to use AgeFile inside collections like a HashMap or a Set. Since we can get by without an AgeFile for now, I think we should give it a bit more thought on this before moving forward. What do you think?

I can't think of any cases where putting an AgeFile in a collection that disallows duplicate items is a necessity, so I'm fine with changing the API to use an InputStream.

I can see the convenience of putting AgeFiles in a collection, however, I think as a library, kage should signal to the API user that this can cause problems and not make this easy. It's might be OK with a file of say, 10Mb in memory, but if the user is reading hundreds of those files, they should not put them into a collection and pass it around. So I think there also a case to be made that a library should not make this easier.
In any case, I think it's fine to leave it for now, just wanted to point it out.

Yeah agreed.
What do you think would be the API methods required for kage? What would make sense for android-password-store?
We currently have:
public fun encrypt(recipients: List<Recipient>, plainText: InputStream): AgeFile
public fun decryptStream(identities: List<Identity>, srcStream: InputStream, dstStream: OutputStream)
public fun decrypt(identities: List<Identity>, ageFile: AgeFile): InputStream
public fun decrypt(identity: Identity, ageFile: AgeFile): InputStream

I guess we'd need to expose the methods to write/parse AgeKeyFile, generate Identities/Recipients? What else?

Yeah agreed.
What do you think would be the API methods required for kage? What would make sense for android-password-store?
We currently have:
public fun encrypt(recipients: List<Recipient>, plainText: InputStream): AgeFile
public fun decryptStream(identities: List<Identity>, srcStream: InputStream, dstStream: OutputStream)
public fun decrypt(identities: List<Identity>, ageFile: AgeFile): InputStream
public fun decrypt(identity: Identity, ageFile: AgeFile): InputStream

I guess we'd need to expose the methods to write/parse AgeKeyFile, generate Identities/Recipients? What else?

You can review the usages of PGPainless here to get a feel for what we'll need. Broadly speaking we'd want the following abilities

Parse a ByteArray to a strongly typed Key
Get a unique identifier from the Key type, akin to a user ID
Encrypt a plaintext InputStream and write it into a destination OutputStream
Decrypt a ciphertext InputStream and write it into a destination OutputStream
Convert a stringly-typed user ID into a strongly typed Identifier

The age test suite is available in an easily parseable format here, we should run kage against it. The reference Go implementation for the same is here.

I think some of these things are going to be a bit tricky to implement.

* [Get a unique identifier from the Key type, akin to a user ID](https://github.com/android-password-store/Android-Password-Store/blob/ade73fd5bc38e8e1f1a4ab3b44132da63f2f7982/crypto-pgpainless/src/main/kotlin/app/passwordstore/crypto/KeyUtils.kt#L33-L42)

Age doesn't have a KeyID, maybe we could use the public key as KeyId? Or a checksum of the public key?

Parse a ByteArray to a strongly typed Key

We have fun parse(reader: BufferedReader): AgeKeyFile, you mean having fun parse(reader: ByteArray): AgeKeyFile ?

* [Encrypt a plaintext InputStream and write it into a destination OutputStream](https://github.com/android-password-store/Android-Password-Store/blob/ade73fd5bc38e8e1f1a4ab3b44132da63f2f7982/crypto-pgpainless/src/main/kotlin/app/passwordstore/crypto/PGPainlessCryptoHandler.kt#L64-L105)

* [Decrypt a ciphertext InputStream and write it into a destination OutputStream](https://github.com/android-password-store/Android-Password-Store/blob/ade73fd5bc38e8e1f1a4ab3b44132da63f2f7982/crypto-pgpainless/src/main/kotlin/app/passwordstore/crypto/PGPainlessCryptoHandler.kt#L33-L62)

These we already have, I think, Age.encryptStream and Age.decryptStream ?

* [Convert a stringly-typed user ID into a strongly typed Identifier](https://github.com/android-password-store/Android-Password-Store/blob/ade73fd5bc38e8e1f1a4ab3b44132da63f2f7982/crypto-pgpainless/src/main/kotlin/app/passwordstore/crypto/GpgIdentifier.kt)

We don't have a GpgIdentifier in Age, how is this used, would this be the equivalent of a public key?

I think some of these things are going to be a bit tricky to implement.

Get a unique identifier from the Key type, akin to a user ID

Age doesn't have a KeyID, maybe we could use the public key as KeyId? Or a checksum of the public key?

Public key should be fine.

Parse a ByteArray to a strongly typed Key

We have fun parse(reader: BufferedReader): AgeKeyFile, you mean having fun parse(reader: ByteArray): AgeKeyFile ?

Correct.

Encrypt a plaintext InputStream and write it into a destination OutputStream
Decrypt a ciphertext InputStream and write it into a destination OutputStream

These we already have, I think, Age.encryptStream and Age.decryptStream ?

Yep, that's covered.

Convert a stringly-typed user ID into a strongly typed Identifier

We don't have a GpgIdentifier in Age, how is this used, would this be the equivalent of a public key?

It's used to parse the .gpg-id file into a list of key IDs so the crypto layer knows what keys it should use. I'll probably just implement it app-side to begin with and upstream it into kage when it's sufficiently robust.

I've raised #110 which takes the parsing code added earlier and dynamically generates tests from it. It has uncovered a bunch of missing and incorrect things that we should be looking into.

Armor might be more work than I anticipated, the Go implementation uses separate readers and writers for armored streams which probably means a fair bit of duplicated code if we follow the same approach. @simao any ideas on this? Armor is the last major hurdle for the interoperability tests.

Hi folks! Thank you for building kage and for running the test suite.
If you don’t implement armoring, you’re welcome to just skip those tests. The suite is designed such that each vector tests exactly one thing, and all armored vectors test the armoring implementation, so you’re not missing out on coverage.

@FiloSottile thanks that is good to know!
@msfjarvis I will try to take some time to see what we can do to implement armoring, I'd like to have it in kage!

Hey, I'd really like to see this project make progress so that https://github.com/android-password-store/Android-Password-Store/issues/2061 gets unblocked. Unfortunately I don't have any Kotlin experience (and don't really trust myself to implement cryptography code).
However, I'd be willing to sponsor this. I won't be able to pay a full Software Engineer salary, but I'd be happy to throw in some 3-digit USD amount for the main contributor(s) if this gets done¹. I'm sure that's not going to be a huge influence and money probably isn't the thing that's missing here, but I still hope that it might help with motivation to work on this. I do hope I'm not offending anyone by this offer.
If there are any tasks that can be done with programming experience but no Kotlin specific knowledge I'd also be happy to look into those myself.
¹ GitHub Sponsorship, Paypal, KoFi, SEPA bank transfer or bug bounty type platforms would all work for me

Hey @Patagonicus, thanks a lot for offering the money, but as you mentioned, money isn't what we're missing here. I'll try to spend some time with Kage and see if we can reach a 0.x beta version or something along those lines.

Yeah not a money probably, it's a time problem. I'll also try to carve some time for this but the next few weeks are busy

@simao @Skrilltrax Hi, I am willing to contribute some time. That said, I am new to Kotlin, and kage, so if there's any low-hanging fruit I can work on, please let me know.
Cheers.

With #124 being merged we now pass the age specification's test suite, barring two. We'll try to resolve them over the coming weeks and tag an initial 0.1 release.

I believe I made a mistake during the rebase of the PR, and we actually do fully pass the test suite. I'll fix it on GitHub in a bit.

v0.1.0 of kage is now available on Maven Central: https://central.sonatype.com/artifact/com.github.android-password-store/kage
I'll update the README in a few hours.


Added accepted responses for deleting session (fix for Issue #17)

Fix for Issue #17
Signed-off-by: Haligowska, Emilia<EMAIL_ADDRESS>

+1

This PR was approved at the OPENRMC-DM meeting.


Fallback layer avoid calling SetComputeRoot32BitConstants with no data

If AccelerationStructuresEntries is empty, don't call SetComputeRoot32BitConstants
Fixes a crash on Intel Iris Xe graphics when using the Fallback Layer without using any bound acceleration structures due to the call SetComputeRoot32BitConstants crashing due to not checking if pSrcData was null. Spec indicates this parameter is required, so a branch is added to avoid the call.

Thank you for the fix!


[BEAM-2844] Introduces PCollectionView.get()

https://issues.apache.org/jira/browse/BEAM-2844
Supports it for DoFn in the various DoFnRunner's and DoFnTester. Support in CombineFn remains.
Introduces a category tag UsesImplicitSideInputs, currently excluded in Dataflow runner - that will be fixed in a follow-up PR after service-side changes, and the category will be removed.
R: @lukecwik

retest this please

Additional R: @kennknowles
Note that @SideInput parameters are not in scope for this PR. My plan is:

Explicit wiring, but access via .get() - in DoFn: this PR and followup PRs after Dataflow worker changes
Same for CombineFn
Support for @SideInput fields and parameters for automatic wiring
somewhere in parallel with the above: simplification of APIs that used to require wiring but now wouldn't (e.g. deprecating CombineWithContext, DynamicDestinations.getSideInputs() etc)

Coverage increased (+0.02%) to 69.706% when pulling 90ddc0d1171b3850d55e9ddbbee45abe48ba4086 on jkff:side-input into 2e9b728a823518b254950fb0cdf06c3e09050020 on apache:master.

Run Dataflow ValidatesRunner

Run Flink ValidatesRunner

Run Spark ValidatesRunner

Run Dataflow ValidatesRunner

Coverage increased (+0.04%) to 69.485% when pulling 2b7b6939227e3e105feee6eddf1d6c943c40815a on jkff:side-input into 5a995e6c370310f3eb48817bed9ee8592ea0ba1e on apache:master.

Please also open a JIRA about adding a get method to StateSpec which provides the Bag/Value/...State out of it and deprecating the other contexts.

On your high-level comment: I decided to go for option 3 but improve error reporting - see changes in PCollectionViews. I can't think of a reliable way to find which PCollectionView's inside a closure will actually be accessed; and there might be PCollectionView's captured not in the closure itself but transitively through its member variables etc. - this also rules out option 2. I think good error messages are the only feasible way.
I added error checking for ParDo test for accessing from StartBundle/FinishBundle.
Deprecation of the methods you indicated will follow as part of the parent JIRA, but shouldn't be done in this PR until Dataflow runner supports UsesImplicitSideInputs.
Note that, since I changed PCollectionView interface, I had to add a serialVersionUID matching the old value to SimplePCollectionView - otherwise mismatch of runners-core-construction jars between the pipeline and the worker image caused it to fail with NonSerializableException's about this class.
Filed https://issues.apache.org/jira/browse/BEAM-2950 about state.

Coverage increased (+0.008%) to 69.521% when pulling 7a10c2a10d76c4f7de0eefdc5be2b07b9c08a1fe on jkff:side-input into 8e391d94f7a4ddc0dbbc7ec54d42df5b6cb7903c on apache:master.

Please do not conflate this to also be the model for StateSpec.

I'm going to close this because it's no longer likely to be the right way to go.
See http://s.apache.org/context-fn


Remove unused sort for segmenta meta list

https://github.com/quickwit-inc/tantivy/blob/02174d26af50af2cf8b9f7592c35e90aae14de70/src/indexer/segment_updater.rs#L415-L423
The segment_metas method is only used in the above method, but it's re-sorted in the method as following.  So the original sort by segment id can be removed to make it little more efficient.
https://github.com/quickwit-inc/tantivy/blob/02174d26af50af2cf8b9f7592c35e90aae14de70/src/indexer/segment_updater.rs#L438

Codecov Report

Merging #1218 (e81d240) into main (02174d2) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1218      +/-   ##
==========================================
- Coverage   94.05%   94.04%   -0.01%
==========================================
  Files         205      205
  Lines       34514    34547      +33
==========================================
+ Hits        32463    32491      +28
- Misses       2051     2056       +5

Impacted Files
Coverage Δ

src/indexer/segment_register.rs
85.00% <100.00%> (-0.30%)
:arrow_down:

src/postings/mod.rs
98.41% <100.00%> (+0.05%)
:arrow_up:

src/core/segment_id.rs
64.00% <0.00%> (-12.00%)
:arrow_down:

src/directory/file_watcher.rs
96.69% <0.00%> (-3.31%)
:arrow_down:

src/fastfield/reader.rs
94.06% <0.00%> (-0.85%)
:arrow_down:

src/functional_test.rs
0.00% <0.00%> (ø)

src/positions/reader.rs
100.00% <0.00%> (ø)

src/reader/pool.rs
91.83% <0.00%> (+0.62%)
:arrow_up:

src/indexer/segment_updater.rs
94.97% <0.00%> (+1.03%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Added support for listening to reaction events on messages and executing periodic tasks.

Added support for listening to reaction events on messages.
For ex.
@on_reaction('+1'):
def work(message):
pass
Added support for executing periodic tasks using 'schedule'.
For ex.
@schedule("every 2 minutes")
def two_minute_task():
pass

Nice commit !!! Great @prathyush !!

@prathyush Thanks for the new features! Can you also add tests for them? Take a look at test_functional.py about the current tests.

@lins05 will make the necessary changes and send out a patch. It will take sometime though.

@prathyush what's the status on this? i had been really looking forward to this getting pulled in. haha.

I've been meaning to do it for sometime now. Hopefully I'll have something by this weekend.

Would be great, @prathyush ! I've been wanting to use the schedule for quite some time now :)

:tumbleweed:

Closed due to inactivity.


df: memory: Locking must be hierarchical

Current implementation of MemoryLockNetworkContext is such that it locks all parent inputs and the input itself.
What it should do is look at the parents and let descendants of a parent all operate on descendant Input items at the same time, but not let anyone operate on that parent item until all the operations working on descendant Inputs have completed.
Effectively, all operations working on the descendant Intputs "share" the lock on that parent they descend from.
https://github.com/intel/dffml/blob/2c671985d3aef0886554397c729aa2b667884be1/dffml/df/memory.py#L466-L492

Working on Alice contributing docs... thought about it and we could have overlays which work in tandem with Union/Lock/Export/SystemContext style type annotation extras on definitions which we could then inspect on apply by having the Python @op decorator use the extras to add some metadata which says at a minimum: on overlay apply we modify the dataflow having overlays applied to it purly based on dataflow.flow inspection at time of apply (still TODO on best practice methodologies around ordering overlay applications)

Flip mode


Update injecting-values.md: mention other jsonnet import options

This PR adds a small note to to the injecting values doc to mention the other ways that Jsonnet can import data. As someone new (or rather, very lapsed) to jsonnet, I didn't realize these other options were available when they would've been a better fit.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Implement a method to deserialize SDK coins

Cosmos SDK stringifies native coins in a different format as cw-asset does. Whereas cw_asset::Asset strinfigifies to:
cw20:{address}:{amount}
native:{denom}:{amount}

SDK stringifies coins to:
{amount}{denom}

There should be a method AssetUnchecked::from_sdk_str to construct an AssetUnchecked::Native instance from the such strings.

implemented in https://github.com/mars-protocol/cw-asset/commit/286bb3c1451f414c790a426c774a98236d7a9679


Sending speech to text input

Dear @OvidijusParsiunas

Can not send the text to speech input (send icon not clickable) .. only clickable when i add another character.
doesnt work here nor in a local running setup.
https://deepchat.dev/docs/speech/#speechToText
Can you help?

Hi @FranzHell.
This issue has been fixed in the Deep Chat dev packages and will be part of our next release.
Due to my current work obligations and the next release being really big, it will take some time for it to go, hence I would recommend you to use our dev packages in the meanwhile. They are called deep-chat-dev and deep-chat-react-dev and behave just like the main packages except their names are different. They also contain a few property name changes, such as the request property is changed to connect and stream is moved to the connect object. All of the current/old properties will still keep working as usual except you will see warnings in the console for their deprecation and get a few TypeScript warnings which you can ignore.
Let me know if this helps.
Thanks!


Add new Performance/RegexpMatch cop

In Ruby 2.4, String#match? and Regexp#match? have been added.
https://www.ruby-lang.org/en/news/2016/12/25/ruby-2-4-0-released/
https://bugs.ruby-lang.org/issues/8110
The methods are faster than match.
Because the methods avoid creating a MatchData object or saving backref.
So, when MatchData is not used, use match? instead of match.
This cop suggests using match? method.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

Check the commit message. :-)

Check the commit message. :-)

🙀 I fixed it.

@rrosenblum Thanks for your suggestion!
I added descriotion and test forSymbol#match?.


python312Packages.croniter: 3.0.3 -> 6.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.croniter is: Library to iterate over datetime object with cron like format
meta.homepage for python312Packages.croniter is: https://github.com/kiorky/croniter
meta.changelog for python312Packages.croniter is: https://github.com/kiorky/croniter/blob/5.0.1/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.0.1 with grep in /nix/store/3710ddqwkc76vwpm5f0vaj25mcks98vq-python3.12-croniter-5.0.1
found 5.0.1 in filename of file in /nix/store/3710ddqwkc76vwpm5f0vaj25mcks98vq-python3.12-croniter-5.0.1

Rebuild report (if merged into master) (click to expand)

26 total rebuild path(s)

26 package rebuild(s)

First fifty rebuilds by attrpath

apache-airflow
archivebox
buildbot
buildbot-full
buildbot-ui
buildbotPackages.buildbot
buildbotPackages.buildbot-full
buildbotPackages.buildbot-ui
devtoolbox
home-assistant-component-tests.utility_meter
home-assistant-component-tests.xiaomi_miio
home-assistant-custom-components.xiaomi_miot
mailman-web
python311Packages.aiocron
python311Packages.croniter
python311Packages.django-q
python311Packages.hikari-crescent
python311Packages.python-miio
python312Packages.aiocron
python312Packages.croniter
python312Packages.django-q
python312Packages.hikari-crescent
python312Packages.python-miio
safeeyes
unifi-protect-backup

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3710ddqwkc76vwpm5f0vaj25mcks98vq-python3.12-croniter-5.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.croniter https://github.com/r-ryantm/nixpkgs/archive/84d24d726e888d97da6dd708ba1c3802104e0ae7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/84d24d726e888d97da6dd708ba1c3802104e0ae7#python312Packages.croniter

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3710ddqwkc76vwpm5f0vaj25mcks98vq-python3.12-croniter-5.0.1
ls -la /nix/store/3710ddqwkc76vwpm5f0vaj25mcks98vq-python3.12-croniter-5.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:fast_forward: 4 packages marked as broken and skipped:

python311Packages.django-q
python311Packages.django-q.dist
python312Packages.django-q
python312Packages.django-q.dist

:white_check_mark: 30 packages built:

buildbot
buildbot-full
buildbot-ui
buildbot.dist
devtoolbox
home-assistant-component-tests.utility_meter
home-assistant-component-tests.xiaomi_miio
home-assistant-custom-components.xiaomi_miot
mailman-web
mailman-web.dist
python311Packages.aiocron
python311Packages.aiocron.dist
python311Packages.croniter
python311Packages.croniter.dist
python311Packages.hikari-crescent
python311Packages.hikari-crescent.dist
python311Packages.python-miio
python311Packages.python-miio.dist
python312Packages.aiocron
python312Packages.aiocron.dist
python312Packages.croniter
python312Packages.croniter.dist
python312Packages.hikari-crescent
python312Packages.hikari-crescent.dist
python312Packages.python-miio
python312Packages.python-miio.dist
safeeyes
safeeyes.dist
unifi-protect-backup
unifi-protect-backup.dist

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.croniter is: Library to iterate over datetime object with cron like format
meta.homepage for python312Packages.croniter is: https://github.com/kiorky/croniter
meta.changelog for python312Packages.croniter is: https://github.com/kiorky/croniter/blob/6.0.0/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.0.0 with grep in /nix/store/wg9316cpq81624bd1lqhnw2w1b2kjl17-python3.12-croniter-6.0.0
found 6.0.0 in filename of file in /nix/store/wg9316cpq81624bd1lqhnw2w1b2kjl17-python3.12-croniter-6.0.0

Rebuild report (if merged into master) (click to expand)

25 total rebuild path(s)

25 package rebuild(s)

First fifty rebuilds by attrpath

apache-airflow
archivebox
buildbot
buildbot-full
buildbot-ui
buildbotPackages.buildbot
buildbotPackages.buildbot-full
buildbotPackages.buildbot-ui
devtoolbox
home-assistant-component-tests.xiaomi_miio
home-assistant-custom-components.xiaomi_miot
mailman-web
python312Packages.aiocron
python312Packages.croniter
python312Packages.django-q2
python312Packages.hikari-crescent
python312Packages.python-miio
python313Packages.aiocron
python313Packages.croniter
python313Packages.django-q2
python313Packages.hikari-crescent
python313Packages.python-miio
safeeyes
unifi-protect-backup

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/wg9316cpq81624bd1lqhnw2w1b2kjl17-python3.12-croniter-6.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.croniter https://github.com/r-ryantm/nixpkgs/archive/5c165277e629e5f0f9bf26eba488b7e2ecd7965b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5c165277e629e5f0f9bf26eba488b7e2ecd7965b#python312Packages.croniter

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wg9316cpq81624bd1lqhnw2w1b2kjl17-python3.12-croniter-6.0.0
ls -la /nix/store/wg9316cpq81624bd1lqhnw2w1b2kjl17-python3.12-croniter-6.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:x: 2 packages failed to build:

python313Packages.python-miio
python313Packages.python-miio.dist

:white_check_mark: 31 packages built:

buildbot
buildbot-full
buildbot-ui
buildbot.dist
devtoolbox
home-assistant-component-tests.xiaomi_miio
home-assistant-custom-components.xiaomi_miot
mailman-web
mailman-web.dist
python312Packages.aiocron
python312Packages.aiocron.dist
python312Packages.croniter
python312Packages.croniter.dist
python312Packages.django-q2
python312Packages.django-q2.dist
python312Packages.hikari-crescent
python312Packages.hikari-crescent.dist
python312Packages.python-miio
python312Packages.python-miio.dist
python313Packages.aiocron
python313Packages.aiocron.dist
python313Packages.croniter
python313Packages.croniter.dist
python313Packages.django-q2
python313Packages.django-q2.dist
python313Packages.hikari-crescent
python313Packages.hikari-crescent.dist
safeeyes
safeeyes.dist
unifi-protect-backup
unifi-protect-backup.dist

Maintainer pings

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


getter to create JSON representation of discrete column

Given a column mapped to a discrete category (e.g. "Diagnosis"), create a complete, schema compliant JSON object of all annotations we have made for this column.
Example from our documentation
  "group": {
    "Annotations": {
      "IsAbout": {
        "TermURL": "bg:diagnosis",
        "Label": "Diagnosis"
      },
      "Levels": {
        "PD": {
          "TermURL": "snomed:49049000",
          "Label": "Parkinson's disease"
        },
        "CTRL": {
          "TermURL": "purl:NCIT_C94342",
          "Label": "Healthy Control"
        }
      }
    }
  }

assume that

the column was mapped to a discrete category (has entry in state.columnToCategoryMapping)
valueMapping is incomplete
all other data are BIDS or schema-compliant

TODO

[ ] combine our annotations and existing annotations
[ ] provide human readable labels (from hard-coded for now)
[ ] provide unit tests

Data to grab

isAbout

state.columnToCategoryMap for the "Label"
state.categories[<categoryName>].identifier for the IRI / TermURL

Levels (in the annotations section)

state.dataDictionary.annotated[<columnName>].valueMap for the TermURL
state.categoricalOptions[<categoryName>] and then somehow find the right term (getter?)

blocked by Seb lack of time

After conferring with @surchs today, the task here is only to make changes for the existing identifiers and labels found in store.state.categoricalOptions and not others used outside of the annotation tool in NeuroBagel just yet.


fix(sdk): don't create package.json when running "prisma generate"

Don't create package.json when running npx prisma generate.
This logic is located on the code path where @prisma/client is going to be installed, so npm will generate the missing package.json file automatically.  Our implementation, though, doesn't always finding the existing package.json file and makes it possible to accidentally create new spurious ones in the project subfolders, which, in turn, might lead to installing packages or possibly even generating the Prisma Client in the wrong location. It's better to just remove this logic and let the package manager handle this correctly.
Possibly/partially related:

https://github.com/prisma/prisma/issues/9553#issuecomment-984761359
https://github.com/prisma/prisma/issues/9553#issuecomment-984837589
https://github.com/prisma/prisma/discussions/10488

so npm will generate the missing package.json file automatically.

Is that indeed so? Also when there is a package.json in the parent folder?

@janpio

Is that indeed so? Also when there is a package.json in the parent folder?

If there's a package.json in the current or any of the parent directories, it will use that. If there's no package.json anywhere up the tree, npm will create it in the current directory. It may be even more complex than that, especially with npm workspaces, I'm not sure about the details.
From the user perspective, you can run npm install <something> in any subdirectory no matter how many levels deep into the project and it will "just work". Or you can run it outside of an existing package, and npm will create both package.json and package-lock.json in the current directory.

So right now (with the code still in place) this would prevent npm install from using an existing package.json that is more than 1 level up from where you run the command, and create a new one in the execution location instead.
And if there is no package.json at all, with this change merged, the behavior will still be the exact same as npm install (and equivalent yarn etc) automatically creates a package.json?

Generally, yes. A few notes though:

So right now (with the code still in place) this would prevent npm install from using an existing package.json that is more than 1 level up from where you run the command, and create a new one in the execution location instead.

Interestingly, it doesn't necessarily prevent the automatic installation of @prisma/client from using the correct package.json, because we run npm install @prisma/client in the directory of schema.prisma as the current working directory. But it still can break in corner cases depending on the project directories layout, and will definitely cause problems when the user runs npm install <something> in that directory or its subdirectories manually.

And if there is no package.json at all, with this change merged, the behavior will still be the exact same as npm install (and equivalent yarn etc) automatically creates a package.json?

Yes, I've just double-checked this with npm and Yarn. The only difference seems to be that the package.json they automatically create is super minimal and doesn't have anything but dependencies specified. Is there any specific reason it would be important to Prisma for the project to have a well-formed package.json file with name, version and stuff, or can we safely conclude it's not our concern as long as the package manager is fine with it?

Is there any specific reason it would be important to Prisma for the project to have a well-formed package.json file with name, version and stuff, or can we safely conclude it's not our concern as long as the package manager is fine with it?

Difficult statement to make. I think we modelled the created file after what npm init -y creates.


Replace double quote character in DHCP client ID. Issue #10295

[ ] Redmine Issue: https://redmine.pfsense.org/issues/10295
[ ] Ready for review

The following is allowed by the webgui in a static mapping: Client Identifier: 32" Sony Trinitron
That creates a configuration that cannot be loaded:
host s_lan_0 {
        hardware ethernet 01:02:03:04:05:06;
        option dhcp-client-identifier "32" Sony Trinitron";
    option host-name "32-Sony";
    option domain-name-servers <IP_ADDRESS>;
}

This fix replaces the double quote character with '&quot';
There is no issue with other special characters (',./!@#$%^&*()~)

Does escaping the double quote as \" work? That seems like a better choice if it does.

It works with \" too
Replaced


eBPF for Windows should work with the version of LLVM that ships with Visual Studio

Microsoft Visual Studio ships with a version of LLVM (17.0.3). eBPF for Windows should work with this version and ideally our documentation / scripts should be updated to use this version instead of the older 11.0.1 version.
The reason for adopting this version is that it has the support and backing of the Microsoft Visual Studio team and will be supported long term, unlike LLVM 11.0.1 which is unsupported.

This looks like a duplicate of issue #1111

Blocked on verifier issue for branch folding.

@Alan-Jowett can you confirm if this is a duplicate of #1111

Cilium commit where verification fails today: https://github.com/cilium/cilium/commit/611dc2c0a4e0d9a5539f8ada5270148e176c4ebd

Is it possible to share pre-compiled ELF files that are failing? We can then work with the verifier team to get to the root cause and get it fixed.

Fixed


Docker tag for 0.10.0?

0.10.0 doesn’t seem to have a corresponding Docker tag. See here. Is this deliberate or an oversight?

Sorry, this was an oversight, but an image for 0.11 is now available. Would you still need an image for 0.10 for any purpose?

No, I have already moved to 0.11.

Same thing now with 0.12.0. (Although it is still so fresh this time that maybe it just takes a while to show up?)

For some reason Docker release job failed, probably because of recent GitHub incident

That one's failing too, not sure why. Also now I remember I need the parent swiftwasm 5.5 to be updated too, that's running right now here https://github.com/swiftwasm/swiftwasm-docker/actions/runs/1513668833

swiftwasm looks fine now, but carton’s latest attempt still seems to have failed.

Thanks, I'm aware of that. I can't build an x86_64 image manually, as I currently only have access to M1 hardware. Will need some time to get that GHA workflow investigated and fixed.

An image for carton 0.12.1 is now available on GHCR.

Thanks for the notification! 👍


Propagate context in sync endpoints of async server

Fixes https://github.com/grpc/grpc/issues/37881

@denik  can you add a unit test for the change.

@sourabhsinghs @sreenithi I've added a couple of tests, please take a look. A few more can be added in this manner.


As a user, I should be able to specify if a field is not printed on the packaging

On the website we use the hyphen (-) to tell that the value is not on the product. For example, it is really useful to tell that there is no fiber value printed on the packaging: in some case that does not mean there is no fiber, but only that the producer didn't print it.
See https://github.com/openfoodfacts/openfoodfacts-server/issues/1938
Originally posted by @CharlesNepote in https://github.com/openfoodfacts/smooth-app/issues/2138#issuecomment-1149180607

@monsieurtanuki is this possible now

@M123-dev I don't think we can.


"Cannot find module" error

Got the error:
"Uncaught Error: Cannot find module "/project$1.0.0/plugins/components/sc-controller/index.js" from "/$/marko-widgets/lib"
Tried deleting the cache and verifed that sc-controller/index.js was included in browser.json for the page. I could see that sc-controller/index.js was included in the page, but it could not be properly referenced.
With help from @patrick-steele-idem, the root cause was having multiple versions of lasso in the project. Once the versions were synced, the error went away and the page behaved correctly.

Doing some cleanup.


Donations: Bitcoin QR code contains email address

The QR code for your Bitcoin donations is encoded with your email address, rather than a bitcoin address.

I thought it's violating the Bitcoin policy to reuse addresses?
Can't you send it using email? I just updated it a minute ago, please re-scan :laughing:
So, what do I do? Leave the email address or Bitcoin?

https://en.bitcoin.it/wiki/Address_reuse

Yes, many people would argue you should not be re-using addresses. For small donations I don't really see the issue.
The technically correct way to do it would be to set-up a HD wallet which would generate a new address on request for each new payment.
Unfortunately I can't just email over some Bitcoin - they need to be sent to a bitcoin address...

Alright. I will re-encode it in few minutes.

Updated, thanks.

Nobody could use my email for sending Bitcoins or it depends on the provider?

Almost there! I can see from the message you have encoded the address you are using is 1AUpmkNSYfKpAUcs5Rz7pPvguRmZU5nPvP - and I've sent you a donation to that address.
What you really want to encode into the QRCode is simply 'bitcoin:1AUpmkNSYfKpAUcs5Rz7pPvguRmZU5nPvP' and also link it as a<href="bitcoin:1AUpmkNSYfKpAUcs5Rz7pPvguRmZU5nPvP">
If you do that, anyone who scans the qr code with a mobile bitcoin wallet, or click the link on a mobile or desktop PC with a wallet installed will be able to send you a donation. It is not possible for anyone to send bitcoin to an email address (without the use of a third party provider - which kinda defeats the point of bitcoin!).
You can get a qr code from somewhere like http://numberfacts.com/1AUpmkNSYfKpAUcs5Rz7pPvguRmZU5nPvP
You can view the donations you have received on a 'block explorer' website such as https://tradeblock.com/bitcoin/address/1AUpmkNSYfKpAUcs5Rz7pPvguRmZU5nPvP
It will show as 'unconfirmed' until a 'block' has been mined containing the transaction, but after that you can send it on to someone else, or another address you own.
If you are new to bitcoin, the key thing to remember is if you lose the private keys to your wallet then you will never be able to access your bitcoins, and if someone else gets hold of the private keys to your wallet they will be able to take your bitcoins from you. So make sure you have a backup somewhere safe :)

Thank you for your donation.
In case I use a provider, than I shouldn't worry about saving my account data?
Will my provider let me use the same Bitcoin address again? It seems that new address is regenerated again (for my wallet default).
I will try to use a link in few moments and ask you to verify it (if it's done correctly).
Yes, I'm new to Bitcoins.

Alright, I've updated the QR code.

Yes, that looks great. If you are using a 'web wallet' from someone like Coinbase or Circle then you don't need to worry about backing up your wallet so long as you trust the service you are using. However you are of course at the mercy of the third party. If they get hacked, or go bust, or the owner decides to run off with your cash you have little recourse.

Understood. Thanks!


Made partsOf variadic with implicit compose for convenience

It seems to be really common to write partsOf([ ... ]), so why not have that
pattern implicit.

Codecov Report

Merging #207 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #207   +/-   ##
=======================================
  Coverage   99.88%   99.88%
=======================================
  Files           1        1
  Lines        1702     1702
=======================================
  Hits         1700     1700
  Misses          2        2

Impacted Files
Coverage Δ

dist/partial.lenses.cjs.js
99.88% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Restrict automatic found Python versions to the supported versions

This enables Python 3 to automatically be found when version 2 is in
the path too.

The patch has been superseded by the update to the new CMake FindPython module.


Cant install Intel HAXM

I've tried to install/run Intel HAXM via Android Studio but I'm getting a persistent error with it failing to run as "the system cannot find the batch label specified - in_exit9009". I've tried installing HAXM via Android Studio and downloading the installer itself from Intel, but still no luck. Below is the screenshot of the issue.
It seems like the issue might be due to my user profile having a space between it, but if so, how do I fix this issue? Thank you in advance.

Laptop Specs
i5 9300H
16GB Ram
Windows 11

Thanks for your feedback. Could you find the installation log file haxm_install-*.log in %TEMP% folder for further analysis after you run HAXM installer?

Faced the same issue today , I tried my level best by disabling hyper v but it doesn't work.  It's better to run your flutter app on real device using USB debugging . Using real device is good enough compare to running the app on a emulator. I will share the video of how to run our flutter app on a real device.
https://youtu.be/BymD9pxtVwY -> Youtube link for running flutter app on a real device.

i have some issue, log like this:
@wcwang
Version: 7.6.5
Output folder: C:\Program Files\Intel\HAXM
Extract: checktool.exe... 100%
Execute: C:\Program Files\Intel\HAXM\checktool.exe --verbose
CPU vendor          *  GenuineIntel
Intel64 supported   *  Yes
VMX supported       -  No
VMX enabled         -  No
EPT supported       -  No
NX supported        *  Yes
NX enabled          *  Yes
Hyper-V disabled    -  No
OS version          *  Windows 10.0.22000
OS architecture     *  x86_64
Guest unoccupied    *  Yes. 0 guest(s)
The system requirements are not satisfied.

Could you run below command in an elevated Command Prompt first and then restart Windows?
> bcdedit /set hypervisorlaunchtype off
After trying to install HAXM again, you may refer to the wiki page for further information according to the new log. Thanks.

i also received same error .then i downloaded haxm from github intel source... i installed it with run as administrator permission. it installed

i also received same error .then i downloaded haxm from github intel source... i installed it with run as administrator permission. it installed

This Works For Me


[Feature] Changes sync with design team

This PR implements a lot of changes request by the design team. More are coming.
Included in this PR:

Color fixes
Risk detail adjustments
ENAButton tap state in dark mode
Localization text updates
Non-breakable space for tracing history
Font type fixes
Minor UI alignment and spacing updates
Discard button on reset settings
Cell shadow on home screen when switching between light and dark
Close button when switching between light and dark mode
Title on privacy policy and terms in app information
Tap states for cells on home screen and card in submission flow
Accessibility improvements
DynamicTableViewController adjustments (fixes booby trap, variable safe area spacing on risk detail)
Risk legend spacings and icon for light and dark mode
Translucent navigation bar in settings and app navigation for large title

Thanks @melloskitten for your review:

The images are suppose to disappear
The TAN field will be adjusted to the latest accessibility requirements by breaking into multiple lines
"Positiv" is not resized correctly only when chaning the text font size whilst on that screen using the accessibility inspector. In every other case it should work as expected.


add Qonto as adopter

Signed-off-by: Thomas Labarussias<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Add Qonto as adopter
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@Issif: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Issif
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 06ffa27147a531875ed24f5f4a2c01d4caa0a1c8

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.30.0