chore: update patches for rn upgrade #trivial

This PR resolves []
Description

Updates patches whose version numbers changed with the react native upgrade to stop warnings.
PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

update patches for rn upgrade - Brian

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (update patches for rn upgrade - Brian)

  Generated by :no_entry_sign: dangerJS against cb53468366a50b1545b1e65cdd6dba9d3e89db0c


Include support total in getvalueforname

getvalueforname presently returns the amount in the claim, without adding amounts from supports with the same claimid.

See https://github.com/lbryio/lbrycrd/pull/30


Ability to export the raw values so that one can make plots for eg. grants in the format of whatever is required

Can do, its a popular request. Lets chat about the security before implementing though

yes but just one gene at a time


feat: link jest config types on npx ts-jest:init

Summary
See #2735
Test plan

[x] Extended existing tests

Does this PR introduce a breaking change?

[x] No

Solves #2735

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 94.403%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
1011

Relevant Lines:
1037

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 94.403%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
1011

Relevant Lines:
1037

💛  - Coveralls


Refactor uTP and clean up async/await

This PR refactors uTP into its own folder, which has been requested numerous times.
It also cleans up a lot of await calls and runs the send talkreq in a tokio::spawn
It also corrects the finalization packet response type

Is this PR part of https://github.com/ethereum/trin/pull/84 ?

Is this PR part of #84 ? For someone who is new to uTP, I would like to see more documented source code as described here.

The only part of the PR what was in #84 was the refactor, but I thought I would take it out cause it is easier to review and would probably get in quicker.
Plus there is two other changes I wanted to make

👍🏻 👍🏻 for shrinking the PR size of #84 by splitting this out

I'm happy to get this merged ASAP, no blocker from me to address all of the comments. I understand this is meant to be just a slight refactor PR, we can refactor it more in the next iterations.

With that, I will get it merged later today, ty for taking the time to review it. Sounds like a plan.


Ollama crashes the Radeon display driver

What is the issue?
Hello Guys,
I have a system with ryzen 3700x and rx6800. With ollama v3.9 in windows is working and never faced any issue. But with ollama v3.10 in windows was breaking my display driver, whenever I try to use any bigger model like mistral-nemo:12b or even smaller models also crashes.
OS
Windows
GPU
AMD
CPU
AMD
Ollama version
3.10

Hi @muntakim1 do you have the logs by chance? https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md

I had to reinstall windows to get rid of the broken driver. Now using with the same driver with ollama v3.9 no issues.
Driver version: adrenaline edition v24.8.1


Strelka?

We have some troubles with Strelka:
INFO: Scanning reference genome
ERROR: BAM headers and reference fasta disagree on chromosome: 'HLA-A*01'
at [strelkapath]/lib/Utils.pm line 44.
Utils::errorX('BAM headers and reference fasta disagree on chromosome: \'HLA...') called at [strelkapath]/bin/configureStrelkaWorkflow.pl line 348
[samplepath]/VCtest/Strelka/work/f2/449eaaca699612fbf6ba007597c407/.command.run.1: line 90: 23332 Terminated              nxf_trace "$pid" .command.trace

We are currently using the latest UPPMAX available module version wich is 1.0.15.
Illumina took over Strelka development: https://github.com/Illumina/strelka
I do think it's a good idea to update our Strelka version to 2.7.1 (and ask UPPMAX to do the same).
What do you think ?

https://groups.google.com/forum/#!topic/strelka-discuss/sQvXiuS6Q18


When removing the only one people, people.ttl is removed

When removing the only one people (last remaining member  in people.ttl),

then people.ttl and people.ttl.acl are removed,
and the address book structure is incomplete and not usable anymore.

Uncaught (in promise) Error: Fetcher: <https://alain.localhost:8443/Contacts/people.ttl> Not Found

Fake error due to other changes


possible bug: Array | string

TypeScript Version:  2.1.4
Code

const _ = require('lodash');

export function appendFile($lines: string | Array<string>) : Observable<any> {

    let lines : Array<string> = _.flattenDeep([$lines]);

}

Expected behavior:
This should compile as far as I know.
Actual behavior:
I get this compile error:
lib/queue-proto.ts(84,9): error TS2322: Type '(string | string[])[]' is not assignable to type 'string | string[]'.
  Type '(string | string[])[]' is not assignable to type 'string[]'.
    Type 'string | string[]' is not assignable to type 'string'.
      Type 'string[]' is not assignable to type 'string'.

What's the definition of flattenDeep ?

I don't know about the d.ts but it should always return an array
https://lodash.com/docs/4.17.3#flattenDeep

Well, the definition of flattenDeep is of importance, of course.
The definition which I found is
flattenDeep<T>(array: ListOfRecursiveArraysOrValues<T>): T[]

where
interface ListOfRecursiveArraysOrValues<T> extends List<T|RecursiveArray<T>> {}
interface RecursiveArray<T> extends Array<T|RecursiveArray<T>> {}

What version of lodash's d.ts are you using? With 4.14, I wrote this in the test file for DefinitelyTyped':
        let $lines: string | string[];
        let lines = _.flattenDeep([$lines]);

And lines has the expected type (string | string[])[].

Ok so what you guys are saying is that it should be
let $lines: string | string[];
instead of
let $lines: string | Array<string>;
I am new to TS

No, string[] and Array<string> are synonyms, so that shouldn't make a difference. I think the problem is that your version of lodash's d.ts is wrong. How did you obtain it? How do you reference it? Can you find its definition of flattenDeep and post it here?
If you are new to TypeScript, then Stack Overflow is a good place to ask questions for help. If you're not sure something is a bug, you might start there since the Typescript issue tracker is only for bugs and proposals.

Sure, that could be it:
// tsconfig.json
{
  "compilerOptions": {
    "types": ["node","lodash","rxjs"],
    "typeRoots": [ "node_modules/@types"],
    "compileOnSave": true,
    "target": "es2017",
    "module": "commonjs",
    "noImplicitAny": false,
    "removeComments": true,
    "preserveConstEnums": true,
    "allowJs": true,
    "allowUnreachableCode": true,
    "lib": ["es2015", "dom"]
  },
  "include": [
    "./**/*.ts"
  ],
  "exclude": [
    "node_modules"
  ]
}

//package.json
  "dependencies": {
    "colors": "^1.1.2",
    "debug": "^2.5.2",
    "live-mutex": "latest",
    "lodash": "^4.17.2",
    "replace-line": "latest",
    "rxjs": "^5.0.2",
    "uuid": "^3.0.1"
  },
  "devDependencies": {
    "@types/core-js": "^0.9.35",
    "@types/lodash": "^4.14.48",
    "@types/node": "^7.0.0",
    "async": "^2.1.4",
    "lockfile": "^1.0.3",
    "mkdirp": "^0.5.1",
    "proper-lockfile": "^2.0.0",
    "rimraf": "^2.5.4",
    "suman": "github:oresoftware/suman#dev"
  }

probably something there that's not right

Everything there looks ok.
Can you look in<EMAIL_ADDRESS>and find the definition of flattenDeep?

sure thing here we go
this is what it looks like:
   //_.flattenDeep
    interface LoDashStatic {
        /**
         * Recursively flattens a nested array.
         *
         * @param array The array to recursively flatten.
         * @return Returns the new flattened array.
         */
        flattenDeep<T>(array: ListOfRecursiveArraysOrValues<T>): T[];
    }

any word on this bird? I don't know the answer and am still wondering why this is, given the d.ts above.

The snippet above looks ok, and is identical to the DefinitelyTyped version that I tried with no success. I also tried exactly your code with the latest typescript compiler and couldn't reproduce the error. Can you npm install typescript@next and try with that?
My repro looked like this:
buglodash/
  index.js
  package.json
  tsconfig.json

Then I did
$ cd buglodash
$ npm install
$ tsc-latest # this is my link to the latest typescript build on my machine

The only error I got was error TS2304: Cannot find name 'Observable', so I change the return type to void and that compiled with no problems.

Yeah tried using typescript@next and I get the same errors - could I share my project with you?
if you clone this
https://github.com/ORESoftware/observable-persistent-queue
and run npm install && tsc
you should see these errors:
lib/handle-priority.ts(24,5): error TS2322: Type '{}' is not assignable to type 'IPriorityInternal'.
  Property 'first' is missing in type '{}'.
lib/helpers.ts(203,9): error TS2322: Type '(string | string[])[]' is not assignable to type 'string[]'.
  Type 'string | string[]' is not assignable to type 'string'.
    Type 'string[]' is not assignable to type 'string'.
lib/queue-proto.ts(86,9): error TS2322: Type '(string | string[])[]' is not assignable to type 'string | string[]'.
  Type '(string | string[])[]' is not assignable to type 'string[]'.
    Type 'string | string[]' is not assignable to type 'string'.
      Type 'string[]' is not assignable to type 'string'.
lib/queue.ts(396,18): error TS2339: Property 'connect' does not exist on type 'Observable<{}>'.
lib/sed.ts(26,11): error TS2322: Type '(string | string[])[]' is not assignable to type 'string[]'.
  Type 'string | string[]' is not assignable to type 'string'.
    Type 'string[]' is not assignable to type 'string'.

2 of those errors relate to the question at hand

@sandersn

What version of lodash's d.ts are you using? With 4.14, I wrote this in the test file for DefinitelyTyped':
   let $lines: string | string[];
   let lines = _.flattenDeep([$lines]);

And lines has the expected type (string | string[])[].

The expected type should have been string[].
I tried the latest version 4.14.63 of @types/lodash with TS 2.4.2-insiders.20170630.
import * as _ from 'lodash';
let a = _.flattenDeep([1,2,[3]]);

a should be of type number[], but it's  (number | number[])[].
So these typings are definitely wrong. Please reopen the issue. Although I'm not sure whether TS's type system is capable enough to fix this.

@thorn0 this is indeed a limitation of the Typescript compiler. It doesn't like infinite types (most type systems don't!). The incorrect behaviour is what you get when it infers to an infinite type. If lodash used type alias syntax instead of interface RecursiveArray<T> extends Array<T|RecursiveArray<T>> {}, you'd see the error upfront instead of getting a weird error later.
The best fix that I can think of is to give flatten, flattenDeep and flattenDepth the same type: function flatten<T>(xs: T[][]): T[]. This is how flow behaves given the current lodash definitions.
This is a limitation of the type system that is unlikely to be fixed, so the correct workaround would be to open a PR on DefinitelyTyped. I'll leave this issue closed.


ctrl+h does not show shortcuts for individual views

No matter which window I have selected, pressing ctrl+h returns only Keyboard shortcuts for ClusterManualGUI. So I cannot find a way, for example, to see the shortcut keys for scaling the waveform view.

press h instead to see the shortcuts for a given window

Aha, well, it must be said - that would be a useful thing to have correct
in the documentation ;)
I have proposed a PR to the documentation fixing this and adding some other
things.
On Wed, Aug 26, 2015 at 12:14 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

press h instead to see the shortcuts for a given window
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/629#issuecomment-134950739.


Added sync load option

Summary
Added an option to bypass calling Taplytics.init if it has already been initialized through Taplytics synchronous loading.

Hi @jsalaber, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
For more information, see README.md.


Feature/path from environment

Needed path from environment variables. I want to support mostly the following use cases

Programs that want to set configuration location using environment variables.
Tests where changing the file location is required. This can be done using mock.

Small documentation updates.

@acederberg @heliocastro Here is also a code pointer to where that ValueError is, unexpectedly, raised.
https://github.com/acederberg/pydantic-settings-yaml/blob/feature/path-from-environment/yaml_settings_pydantic/__init__.py#L242
At least as of today it points to the correct line of code.


re-handled trace name for visualizer

+ trace in visualizer should now reflect the actual trace name rather than "Iteration{n}"
I.e. Uploading tcAbstractServerTrace.json should say tcAbstractServerTrace in the visualizer.


access_loggers: use new-style names

Modifies the well-known-names of the built-in access loggers to
use the same name as the extension build system.
(This is the first in a series, but I expect whatever changes may be
requested here will apply to all the rest, so I'm going to hold the others
back.)
Risk Level: low, previous name is still accepted
Testing: added test to prove factory accepts old names
Docs Changes: updated names
Release Notes: updated
Deprecated: old names are logged as deprecated
Signed-off-by: Stephan Zuercher<EMAIL_ADDRESS>

@kyessenov do you mind taking a look?

@zuercher After https://github.com/envoyproxy/envoy/pull/9618, getAndCheckFactory uses the type URL in the config as the first lookup to pick an extension. That means the name field in the config proto becomes optional. Can you check that is indeed the case by setting it to something random? I haven't tested the access log extensions, only the HTTP extensions. There might be a difference depending how the factory is selected.

It's correct that with typed_config the name is ignored. Mostly I'm undertaking this change to unify the build extension and config names for v2 in the short term. The top of each protobuf doc currently emits an extension name that isn't necessarily the correct one to use with config.

LGTM. I agree we need this to support untyped configs in the short term, for consistency with the rest of the extensions. I can do a follow-up to assign random optional names to extensions later, once we feel that the world has moved on to v3 and 1.13.

So can we move forward with this?


Add tags to drives

What would you like to be added:
I would like to add tags to log drives and add tags to them. This way, I can tag, filter and export drives as 'business' or 'personal' (or any other tag).
Why is this needed:
A detailed drive log will be used for tax filing and company administration.
Additional context:

Duplicate of #505


🐛 useCameraFormat and native code disagree on maxFps

What's happening?
On an iPhone SE 2nd Gen, using the example app, vision camera seems to return a format with a maxFps of 60. However, the native code throws an error.
format, as selected by the example app:
 LOG  {   "minFps": 3,   "videoWidth": 3840,   "minISO": 22,   "photoHeight": 2160,   "maxFps": 60,   "fieldOfView": 65.70668029785156,   "videoHeight": 2160,   "autoFocusSystem": "phase-detection",   "supportsVideoHdr": false,   "supportsPhotoHdr": false,   "photoWidth": 3840,   "supportsDepthCapture": false,   "maxISO": 880,   "pixelFormats": [     "yuv",     "yuv",     "rgb"   ],   "maxZoom": 129.125,   "videoStabilizationModes": [     "auto",     "cinematic",     "off",     "standard"   ] }
Reproduceable Code
Reproduceable with the example app.

Relevant log output
VisionCamera.onError(_:): Invoking onError(): The given format cannot run at 60 FPS! Make sure your FPS is lower than `format.maxFps` but higher than `format.minFps`.

Camera Device
{
  "isMultiCam": false,
  "formats": [],
  "minZoom": 1,
  "maxZoom": 16,
  "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "name": "Back Camera",
  "hasFlash": true,
  "minExposure": -8,
  "minFocusDistance": 10,
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "full",
  "position": "back",
  "supportsFocus": true,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsRawCapture": false,
  "supportsLowLightBoost": false,
  "maxExposure": 8,
  "hasTorch": true
}

Device
iPhone SE 2nd Gen (iOS 17.3)
VisionCamera Version
3.8.2, 3.9.0-beta.3
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I'm commenting this on pretty much every issue now: Why does everyone simply ignore the logs?
What you put there is not a log, it is an error. I need to see the logs to see what format got selected, if it got applied, etc.
If you choose to ignore giving me that information I cannot help you.


Document new Timing Manager and Scheduler updates

Will resolve:

#100

@codecubepi here is the source for the diagram of the timing manager: timing_manager_diagram_source.pptx

This may be an issue on my end, but when I click on the "Sensor Feedback" article after building the html, there is only this amount of content on the page:

Furthermore, when ı click on another tutorial in the sidebar, such as the VSI tutorial. The Sensor Feedback tutorial link just disappears:

@Known4225 I think you can resolve this issue by deleting the build output folder (or whatever it is called, I cannot remember) from your PC and having sphinx rebuild it.

@elsevers @Known4225
Okay, it looks like this branch/PR are superceded by #112 , so I'm going to close this. Ryan, could you make sure that all the changes requested by Professor Severson are also applied in your branch?

@codecubepi, @Known4225, I think we have a mistake here in how the PRs are set up. #112 should be trying to merge user/known4225/tm-tutorials into user/codecubepi/tm-sched-updates, so that reviewers on #112 only have to review the tutorial documentation. (i.e., both PRs should be relevant)

Switched #112 to merge into user/codecubepi/tm-sched-updates

@noguchi-takahiro, can you please try this tutorial out on your AMDC (while running the latest AMDC-Firmware on the develop branch).
To do this, build the docs at tutorials/timing-manager/index.md

When I build the docs on this branch, I am getting several warnings related to the timing manager tutorial:
D:\WorkingCopies\docs.amdc.dev\source\getting-started\tutorials\timing-manager\index.md:48: WARNING: 'myst' reference target not found: /getting-started/tutorials/vsi/index.md#template-task-h-file
D:\WorkingCopies\docs.amdc.dev\source\getting-started\tutorials\timing-manager\index.md:200: WARNING: 'myst' reference target not found: /getting-started/tutorials/vsi/index.md#template-task-h-file
D:\WorkingCopies\docs.amdc.dev\source\getting-started\tutorials\timing-manager\index.md:240: WARNING: 'myst' reference target not found: /getting-started/tutorials/profiling-tasks/index.md#step-4-profile-the-vsi-control-code

Let's sort these out

I have not seen these warnings:


Clearing album art

Hello,
After an album art is set on an AppleTV, there is no way of clearing it. Maybe i am overlooking something, but i read through the code and it doesn't look like it.
I tried passing an empty string, undefined, null and false to device.setAlbumArt, with no luck.
Am i missing something obvious, or is there no way to clear the artwork?

Okay nevermind. After looking how itunes does this using wireshark it turns out that i can pass an empty buffer to setAlbumArt with content type image/none.
Thanks for this nice library.


flutter_map >=6.0.0 depends on logger ^2.0.1 and stacked_generator >=0.6.5 depends on logger ^1.1.0, flutter_map >=6.0.0 is incompatible with stacked_generator >=0.6.5.

Describe the bug
flutter_map >=6.0.0 depends on logger ^2.0.1 and stacked_generator >=0.6.5 depends on logger ^1.1.0, flutter_map >=6.0.0 is incompatible with stacked_generator >=0.6.5.
To reproduce
updatee pubspec.yaml
Expected behavior
No response
Screenshots
No response
Additional Context
No response

Plus one here. The logger had a major version update so we should expect more and more libraries using this new version, which as a result would break any app that uses the latest stacked_generator.

Thanks for filing the issue.
Any chance either of you can update it?

Should that be done inside this project? I tried to find the logger reference inside stacked repo, but couldn't find anything..

It's in the stacked_generator, but I know generators are really hard to work with so we might have to tackle that ourselves.
It will be a breaking change for all other Stacked users, but I think it's time to do it.

Hi @MirzaCickusic, please try the prerelease and let me know if you have any problems.

thanks @ferrarafer
Looks good on my end (Y)
I updated to the latest logger without any issues!


fix jekyll 4.0 cache mismatch errors

Jekyll 4.0 introduced a new caching mechanism to the LiquidRenderer class. This remembers the paths of any files passed to convert and the rendered output.
The issue here is that Jekyll-Paginate-V2 sets the name of all Jekyll::PaginateV2::Generator::PaginationPage instances to index.html. Meaning every pagination page gets rendered to the result of the first paginated page.
This patch simply assigns some fields the Page instance, such that it appears to have the same file name as the file to which it's written to (in the _site directory).

@mohkale Can you post the before and after screenshots of a verbose build (build with --verbose switch) for a test-site to be certain of this patch..

Kay, will get on it soon.

@ashmaroli I've attached to this the before and after log and also a zip of the site.
The site has two collections (foo & bar) each of which has 2 index pages contents/foo.markdown, contents/bar.markdown. If you build as it is, in the _site directory foo/index.html will have the exact same contents as bar/index.html (because bar was rendered first and the liquid cache doesn't see the two as distinct from each other).

@mohkale The before and after diff shows:
-          Rendering: .html
-   Pre-Render Hooks: .html
-   Rendering Liquid: .html
-   Rendering Markup: .html
-   Rendering Layout: .html
+          Rendering: bar/.html
+   Pre-Render Hooks: bar/.html
+   Rendering Liquid: bar/.html
+   Rendering Markup: bar/.html
+   Rendering Layout: bar/.html
       Layout source: site
-          Rendering: .html
-   Pre-Render Hooks: .html
-   Rendering Liquid: .html
-   Rendering Markup: .html
-   Rendering Layout: .html
+          Rendering: foo/.html
+   Pre-Render Hooks: foo/.html
+   Rendering Liquid: foo/.html
+   Rendering Markup: foo/.html
+   Rendering Layout: foo/.html

foo/.html and bar/.html still don't look right to me..

@ashmaroli could you clarify what you mean? do you mean the filename (index.html) should also be included.

Yes. Or some other unique name.

I'm planning to switch from jekyll to hugo, so I'm not sure when (or if) I'll get back round to trying to fix this. If someone wants to try to do so, feel free 😄.

hi, I'll give it a shot :smile:
Thanks for your work!


change color when visited and add icon to all external links

AB#1442

It would be nice to add some description to the PR and share images of the diff if the changes are visual in nature,

It would probably be good to add a brief overview to the PR description, since ADO links will not be usable by the open-source community.


MVP of Virtual Machines

Document (or maybe do some shell scripting) of an minimum viable product (MVP) of usage of Virtual Machines (not necessarily on tails)

I already have an MVP of documentation for this feature. Just need to move to this repository later.

Turns out I actually commited the file. Now just added reference to the readme.
For an future issue, maybe I should add reference about using LXC also with GUI (not just CLI), so an user could run an entire application either via conteiner or virtual machine (stronger sandboxing). Here some comments on the topic https://discuss.linuxcontainers.org/t/howto-gui-in-virtual-machines-vms/9223


不能识别出jsx的react文件，其中jsx格式的语言显示不正确。javascript react才是正确的，需要手动选择

VSCode Version: Code 1.5.1 (07d663dc1bd848161edf4cd4ce30cce410d3d877, 2016-09-08T21:33:49.307Z)
OS Version: Windows_NT ia32 10.0.10240

"files.associations": {
"*.jsx": "react"
},
Steps to Reproduce:
1.打开一个jsx文件
2.其格式显示为jsx，但理想情况应该显示成 javascript react
3.可是配置files.associations为react却显示为纯文本

@txiaocao Can you please update the issue title and steps to reproduce in english?

Google Translate:
Title:
Can not identify jsx too react file format in which language jsx displayed incorrectly. javascript react is correct, you need to manually select
Steps to Reproduce:

Open a js file
The format appears as jsx, but ideally it should be displayed as javascript react
Configure files.associations to react, but it appears as plain text

The first step should probably read jsx and not js.
BTW, maybe the team should mention English-only issues in the contribution guidelines?

@glen-84 May be we should. A lot gets lost during translation too. And it does make the job of the inbox tracker easier when we need to sort through sound 30 to 40 new issues every day :)

@txiaocao Without any file associations, when I open a jsx file, the language mode in the bottom right corner shows "Javascript React"
Are you working on a js file or a jsx file?
Is this a problem in the new update or did you have the same issue in 1.4.0 as well?

I am closing this due to insufficient information of the issue.

@txiaocao Also if you want to associate a file for react you should use "javascriptreact" not "react"
"files.associations": {
        "*.jsx":"javascriptreact"
    }

Thanks! use "javascriptreact" is right...
I try "react","jsx","Javascript React","babel","javascript(babel)" is wrong...
if display is  real field,It's good


Can't open file /tmp/vL3FrhY/30

If I leave a vim window open for a long time, there seems to be a /tmp/.../ directory that gets removed that vim-syntastic wants to use:
syntastic: error: exception running system('bash -n DaosTestMulti.sh'): Vim(let):E484: Can't open file /tmp/vL3FrhY/29
syntastic: error: exception running system('shellcheck -f gcc DaosTestMulti.sh'): Vim(let):E484: Can't open file /tmp/vL3FrhY/30

If I simply recreate the directory (mkdir -p /tmp/vL3FrhY/) vim-syntasic starts working again.
I wonder if ensuring that this assumed-to-be-present directory is actually present is possible.

Fair enough.
Thanks for the clarification.


Payments to other nodes using keysend in Split Payments (splitpayments) plugin?

Currently you can split percentage of incoming payments to other LNBits wallets. Haven't looked too much into architecture of LNBits so far, but would it be possible to add paying to other nodes using keysend too?

We do not currently support keysend, but are open to PR


remove unused rule from grammar

in order to make it easier to explore jhipster/jhipster-core#89

I'm not quite sure about that... Let me test it first.

I try to give a proof why the removed second rule was redundant.
First rule is:
JDLComment? space* com:Comment? space* JDLComment? space* f:FIELDNAME space t:type space* vl:validationList? space* com2:Comment? space* ","? space* JDLComment? space* fdl:fieldDeclList

Removed second rule was:
com:Comment? space* f:FIELDNAME space t:type space* vl:validationList

Let's compare rules from the beginning to the end:

the first rule has extra JDLComment? space* - empty string fits that
common part com:Comment? space*
the first rule has extra JDLComment? space* - empty string fits that
common part f:FIELDNAME space t:type space*
the first rule has vl:validationList? and the second rule had vl:validationList - this second part of the rule matches the first part of the rule
the first rule has extra space* com2:Comment? space* ","? space* JDLComment? space* - empty string fits that
first rule has extra fdl:fieldDeclList - it can be empty because of the third rule of the fieldDeclList: ""

And npm test was successful after removing the second rule.
And my JDL worked identically after removing the second rule.

Did you try with only one field in the entity?

Just tested, yes works. It's also covered by npm test, for example entity B from test added by you yesterday.

Closed as it was removed in 94705f4


Change main docs from hpke-js to @hpke/core.

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

Project coverage is 89.31%. Comparing base (031bafb) to head (53fd109).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #436      +/-   ##
==========================================
- Coverage   89.56%   89.31%   -0.26%
==========================================
  Files          58       58
  Lines        4380     4380
  Branches      412      411       -1
==========================================
- Hits         3923     3912      -11
- Misses        456      467      +11
  Partials        1        1

Flag
Coverage Δ

unittests
89.31% <ø> (-0.26%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Generify Repository Name

When looking for a Polybar plugin to control music playback in chrome with, I scrolled across this multiple times without opening it. The naming suggests that this only works with Spotify, while your code actually is quite generic.
Wouldn't it be good to change the repository name to something like polybar-playerctl? Furthermore, the names of example modules in the readme (and in the hooks in get_spotify_status.sh) would need to be updated.
Edit: Just noticed you mentioned this in one of your commits. I think you should :)

I'm really sorry that I wasn't able to attend to this issue. I agree that most of the traffic comes from Google searches and just renaming should maintain the traffic. However, I think I'll rename it when I've added a bit more features to the module and post it like a new release.
And hence, please keep opening issues for new features. Currently, I'm a little busy but I assure you I'll get back to this issue soon.

I'm really sorry that I wasn't able to attend to this issue. I agree that most of the traffic comes from Google searches and just renaming should maintain the traffic. However, I think I'll rename it when I've added a bit more features to the module and post it like a new release.
And hence, please keep opening issues for new features. Currently, I'm a little busy but I assure you I'll get back to this issue soon.

No Problem. Talking about the big picture it would also be great to describe configuration without moving text. I simply adjusted it to my liking for that but i think most people might be distracted by the movement in the polybar (specially when paired with non-monospace fonts resulting in varying width)

No Problem. Talking about the big picture it would also be great to describe configuration without moving text. I simply adjusted it to my liking for that but i think most people might be distracted by the movement in the polybar (specially when paired with non-monospace fonts resulting in varying width)

I have been using a modified version of this repo in such a way that it's not specific to spotify. It assumes playerctld is running.
However, there's a bug to which I haven't been able to figure out a solution:
Steps to reproduce

Play player A
Play player B (both players will be playing at the same time)
Pause player c

Expected behavior

Play/pause icon should be ▶
Metadata about player A should be displayed

Actual behavior

Play/pause icon should be ▶
Metadata about player A should be displayed

I tried to fix this by using playerctl's --follow flag but without success. I'm still trying to play with it to find a solution.

@fuadsaud Can you please open a separate issue?

@fuadsaud Can you please open a separate issue?

@fuadsaud @PrayagS any update on this? would love to make this module as part of my dotfiles generator once it supports more than spotify 😸


Option to export markdown with references to images instead of embedding them as base64

It would be nice to have an option to export markdown files with images as references to files instead of embedding them in the document as base 64. This might be similar to how "figure export" example extracts and stores files

this is a feature I am really interested too.
I had similar experiences to @Tendo33, after pdf-to-md conversions images are lost and substituted with an html comment of <!-- image -->`. Where are you seeing base64 images? I can easily add another step after it to remove them from the md and put them in a separate file...

@Tendo33 @cenit @uninstall-your-browser this feature is already supported, you can configure the pipeline to extract pictures, and change arguments to the export_to_markdown() method. Please refer to this post.

I was interested in them being references to files rather than embedded base64 blobs

@uninstall-your-browser we will put file references for images on our TODO list and work on it soon.

@pwab indeed, we have to add this functionality to all other backends (apart from PDF), I'll look into it


Change delivery information on all products

[ ] It says (your product info goes here) remove this and remove the European delivery
[ ] Instead, put:  All orders out of the GTA are subject to shipping fees @
[ ] I want to use Canada post, fed ex, and UPS as possible shipping companies customers can choose who they want to ship with
----Customer must be able to calculate how much their shipping cost will be

This data comes from the Home section of contentful


Adding test coverage for getters/setters currently untested.

Just adding some additional coverage, a little at a time. Getters/Setters are easy to test, so why not :)

Coverage increased (+2.6%) to 99.228% when pulling bf1513433f59ede1515e77449581ab41461b20cf on jmauerhan:tests into 2d19c68f5cc8b414936aff8a236fe9578f42e57b on ramsey:master.

Coverage increased (+2.6%) to 99.228% when pulling bf1513433f59ede1515e77449581ab41461b20cf on jmauerhan:tests into 2d19c68f5cc8b414936aff8a236fe9578f42e57b on ramsey:master.

Coverage increased (+2.6%) to 99.228% when pulling bf1513433f59ede1515e77449581ab41461b20cf on jmauerhan:tests into 2d19c68f5cc8b414936aff8a236fe9578f42e57b on ramsey:master.

Coverage increased (+2.6%) to 99.228% when pulling 02fc392d84ae8eb3bf50ad769aa5e8da97f20b28 on jmauerhan:tests into 2d19c68f5cc8b414936aff8a236fe9578f42e57b on ramsey:master.

Thanks!


Command For Bagisto Publish

Info

There should be a command like php artisan bagisto:publish --all --force something like this so that we can avoid using php artisan vendor:publish --all --force because most of the time we don't wont to publish all providers.
Even --all also not needed just --force.
In installation also we can change that. So that we don't need to rely on.

@jitendra-webkul and @ghermans,
I have started working on this.

@devansh-webkul
Thanks, now this enhancement is implemented. so I am closing this enhancement.
And I have attached a screenshot Here, for future reference.


Formatting Changes

There is a major amount of minor formatting changes that will need to be dealt with in the documents throughout the site
GitHub has changed their styling in Markdown as per this document
Because of this, there will need to be updates to a lot of the MD files on the site.

Fixed by #4


[Bug]: reflection_with_llm not working as summary_method

Describe the bug
"summary_method": "reflection_with_llm" not working when using Azure OpenAI gpt-4o model
Steps to reproduce
I am running the following example locally on vscode using Azure OpenAI gpt-4o model.
https://learn.deeplearning.ai/courses/ai-agentic-design-patterns-with-autogen/lesson/4/reflection-and-blogpost-writing
I do not get anything under the Context.
Model Used
gpt-4o (Azure OpenAI)
Expected Behavior
Obtaining a json file of reviews' summaries and the reviewers
Screenshots and logs

Additional Information
No response

Without access to the notebook we can't comment. Can you take a look at the carry over documentation: https://microsoft.github.io/autogen/0.2/docs/tutorial/conversation-patterns#sequential-chats

I changed the "system" to "user", and the summary method works.


Discussion: Add Feature Management platform

What

We have come to the point where we need some kind of way to communicate with the app cross-release
For things like: #3202 or #3333
So I'm suggesting that we add some kind of feature management platform to smoothie
This allows to:

kill/shutdown (Ask for ratings when something goes wrong)
test different versions A/B testing (Donation campaigns, other UI)
release features without publishing a new version
Test features for a fraction of users

I've heard about unleash  a while ago and it looks really good from outside but we should compare some alternatives before doing something like that

I cannot be helpful on this subject.


pkg: webpack, @anansi/webpack-config, @testing-library/react-hooks

Codecov Report

Merging #1890 (cda0229) into master (707eff1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1890   +/-   ##
=======================================
  Coverage   98.56%   98.56%
=======================================
  Files         101      101
  Lines        1885     1885
  Branches      393      393
=======================================
  Hits         1858     1858
  Misses         13       13
  Partials       14       14

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


FormBuilder validation message does not show for TextCheckboxGroupField

TextCheckboxGroupField is a CompositeField used by elemental
FormSchema validation messages from inline submit do not show the red message

IMHO impact is more than low. Finding elements to associate or link is not feasible without title/name.

I've done a little more investigation, the issue here is really whether the noHolder props is passed the field rendered by formbuilder which causes the message (validation message) to not be rendered - https://github.com/silverstripe/silverstripe-admin/blob/2/client/src/components/FieldHolder/FieldHolder.js#L183.
So this isn't a bug, it's a feature.
I've resolve this for elemental in this PR by removing the noHolder prop for the Title field and updating CSS so it still looks as it did before
I've close this issue


Issues with interrogative sentences when using ljspeech model

Hello,
Here are some issues with interrogative sentences:

"May I take your order?" - sounds like a standard declarative sentence.

"Where do you live?"  - sounds like a standard declarative sentence and adds stress on the word "you".

"Did you finish your homework on time?" - sounds like a question, but the intonation in incorrect.

Can you give me some guidelines on how to train matcha to overcome these issues?
Thanks a lot

Hi @orenstuf,
The LJ Speech checkpoint is only trained on LJ Speech corpus. Being a read speech corpus it doesn't really have a lot of variation or interrogative sentences for the model to learn.
The only mitigation for this will be to improve the dataset. Or try fine-tuning the model to your voice. Record 20 such sentences and fine-tune and see if the model learns something from it.
Regards,
Shivam


get construct args from raw script and contract class

could scryptlib support read contract construct args from raw script with contract class?

support by this pr https://github.com/sCrypt-Inc/scryptlib/pull/98


Unable to connect using MacOS Monterey

I have created a config.yaml file in the library folder, but when I run the command:
idasen-controller --config "/Library/Application Support/idasen-controller/config.yaml"
I receive the error:
Scanning - Desk D8-7D-63-0D-91-32 Not Found
config.yaml looks like this:
mac_address: D8-7D-63-0D-91-32
stand_height: 1040
sit_height: 683
height_tolerance: 2.0
scan_timeout: 5
connection_timeout: 10
movement_timeout: 30
adapter_name: hci0
server_address": "<IP_ADDRESS>"
server_port: 9123

Someone noted that on on MacOS you cannot use the MAC address and instead you must use the UUID found with when running idasen-controller --scan. Have you tried that?

Yes, I did. I've connected the desk using BlueUtility, and then tried to run the scan.
The returned message is: Found 0 devices using hci0

Have you connected using the UUID rather than the mac address? The config you posted above is using the mac address.

How do you propose I get the UUID of the desk without installing XCode?
idasen-controller --scan does not return the UUID as listed in your documentation, rather only 'found 0 devices'.

I propose that as the owner of a Mac that you are in a better position than me to find that out 😆
But more seriously I don't know why the --scan function doesn't return anything. You could try using the bleak library directly to see if that returns anything:
import asyncio
from bleak import BleakScanner

async def main():
    devices = await BleakScanner.discover()
    for d in devices:
        print(d)

asyncio.run(main())

https://bleak.readthedocs.io/en/latest/scanning.html

I can confirm the issue.
Using bluetillity I found my desks UUID and tried connecting to it using
Idasen-controller --mac-address <UUID>
The script says it can't find a desk under that mac address.
Using the real mac address doesn't work either.
It works perfectly on windows & linux but not on macOS

Thanks for the info. Would you be able to run the code snippet I posted above? I want to know if this is a problem with the idasen controller code or if its also in the bleak library.

Yes I ran the code and got absolutely no output.
After adding some print() statements I got to see my prints but no discovered devices.
I think the issue is with bleak and not your usage of it.

After some searching around on the bleak repo I found many (many!) comments about macOS 12.
There are workaround but nothing really usable in the context of a CLI.
I think you can close this because it is evident that the issue is with bleak and it won't be fixed in the near future.
References:
comment
issue
comment

Ah yeh I was just poking around those comments. It seems to be an issue with scanning though and the idasen controller code does a scan before connecting even if you provide a UUID/mac address.
I can't remember why so maybe we can drop that and it will work.
Could you try running something like this example code to connect to the desk without scanning https://github.com/hbldh/bleak/blob/develop/examples/get_services.py

I tried the code with the UUID & Mac address. Unfortunately neither worked.
I also tried it with the desk actively searching (holding the bt button for 3 seconds) and without.

That is a shame but I've just pushed a version without the preconnection scanning anyway. I think I assumed there was some benefit to already having the BLEDevice object but looking at the bleak code all it does is immediately extract the address string from it 🤦♂

RC3 is looking really good!
It doesn't solve this issues but it's overall a good performance improvement.
Do you have a timeline for the full release?

Just released it as 1.0.8, I was mostly doing the rcs as I often break the packages when uploading 😆
Still using this issue to track the mac os 12 bug. It seems like most people are raising that scanning does not work, but I'm unsure if that also means that other people are having connection issues. I think that might be worth raising on the Bleak repo at least to ask for clarification.

Sounds good. I submitted a feedback to apple regarding the general issue that bluetooth over cli seems to get no permissions even when terminal is allowed bluetooth access.
Let's hope for the best!

Same issue here - neither using "get_services.py" with the UUID provided by Bluetility nor "idasen-controller --scan" works for me. I tried using "Remote Desk Control" from the Appstore and this app was able to connect.
Would be happy if we could get feedback from apple or Bleak for this.

Apple responded to my feedback. It's in German but basically they believe that issue to be fixed in macOS 12.3 Beta 4.
I currently have no way to check this because I need my Mac as stable as possible but if someone want's to try it out and give us feedback, that would be highly appreciated.
Copy of the mail in German:

Hallo Vincent,
vielen Dank für deine Geduld und deinen Feedback-Bericht. Wir glauben, dass dieses Problem mit den Updates für macOS behoben wurde.
Bitte überprüfe das Problem mit macOS 12.3 Beta 4 und aktualisiere deinen Feedback-Bericht mit deinen Ergebnissen. Melde dich dazu bei Feedback-Assistent-Website an an oder verwende die Feedback-Assistent-App. Bitte schließe diesen Bericht, wenn sich das Problem erledigt hat, oder gib uns Bescheid, wenn es weiterhin ein Problem für dich ist.

Today I found the time to update my Mac to the latest beta. The version I'm now running it the RC1 of 12.3
It works! 💯
Here's a quick screenshot of my terminal on 12.3:

"Searching" means that I pressed the BT button on the controller for 3 seconds (led flashes quickly).

Ah nice, thank you for confirming! I will update the readme and close this issue soon.

Updated README


separate bootstrap from the core package.

@mohammedzamakhan Do you want to review this pull request. I think there was a plan to have separate git repo for templates.
Also we can think of monorepo the way angular, material2 are doing it. May be this PR is step in that direction.

@aitboudad can you please consider using git-cz to commit files it generates better commit messages.

@divyakumarjain Yes I think this is the step towards our goal of monorepo.
Eventually we can have all bootstrap templates in this repo
https://github.com/formly-js/ng2-formly-templates-bootstrap

Hi
I would prefer to keep it in the same repo (like angular does), at least right now we can keep it as it is until we achieve v1.0 WDYT ?


Minimum font size.

How do I set a minimum font size?
E.g h1 max font size must be 50px. This is easy to do.
But I cant find a way to set h1 minimum font size to 40px.
I also can't set multiple breakpoints to try and override this.

hey, you can use Cal() function:-
h1{
font-size: calc(4vw + 4vh + 2vmin);
}
If it is helpful let me know.

You don't need to set a minimum size, the whole idea of RFS is to automatically calculate how it rescales. Have a look at https://css-tricks.com/using-a-mixin-to-take-the-math-out-of-responsive-font-sizes/, so you can find out how it works.


Spidering Sources: We get a SSL error from 1610 publisher

FetchError: request to https://onlinebooking.1610.org.uk/OpenActive/ failed, reason: write EPROTO<PHONE_NUMBER>58048:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../deps/openssl/openssl/ssl/statem/statem_lib.c:1929:

Works in Firefox for me, so need to look into

TLS 1.0 only! That probably explains that.

And in code:

import tls from 'tls';
tls.DEFAULT_MIN_VERSION = 'TLSv1';

Todo - add a new Settings option for this, and make sure the tls.DEFAULT_MIN_VERSION = Settings.xxxx is run somewhere on startup. This needs to be done for both spider-data-catalog.js and download-raw.js

 Harvest data from sources that only support certain SSL versions


AttributeError: SelfSupDeformableDETR: SelfSupDeformableDETRHead: 'ContrastiveLoss' object has no attribute 'use_sigmoid'

When I use the configuration "configs selfsup doormaple_detr. py" for training, some errors occur:
Traceback (most recent call last):
File "/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py", line 69, in build_from_cfg
return obj_cls(**args)
File "/nas/xxxx/mmdet/aligndet/code/AlignDet/models/detectors/selfsup_detector.py", line 33, in init
self.online_backbone = build_detector(backbone)
File "/opt/conda/lib/python3.7/site-packages/mmdet/models/builder.py", line 59, in build_detector
cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))
File "/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py", line 237, in build
return self.build_func(*args, **kwargs, registry=self)
File "/opt/conda/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 27, in build_model_from_cfg
return build_from_cfg(cfg, registry, default_args)
File "/opt/conda/lib/python3.7/site-packages/mmcv/utils/registry.py", line 72, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
AttributeError: SelfSupDeformableDETR: SelfSupDeformableDETRHead: 'ContrastiveLoss' object has no attribute 'use_sigmoid'
please help me, thank you!

This should be a bug caused when I made the open-source code. Unfortunately, I don't have GPU resources for debugging right now. I will fix this problem as soon as possible (about two weeks).
Also, this should be a minor bug, I would appreciate it if you could create a PR.

I really want to fix it, but I wonder when you train selfsup_deformable_detr, the loss_cls is ContrastiveLoss like fcos or CrossEntropyLoss like detr？the latter?
If loss_cls is CrossEntropyLoss, I also need the file<EMAIL_ADDRESS>is that true?
It's a really nice work, but when used in detr, it not so cute (a little complicated) beacause it need to do cluster using supervised pre-trained backbones.

I really want to fix it, but I wonder when you train selfsup_deformable_detr, the loss_cls is ContrastiveLoss like fcos or CrossEntropyLoss like detr？the latter? If loss_cls is CrossEntropyLoss, I also need the file<EMAIL_ADDRESS>is that true? It's a really nice work, but when used in detr, it not so cute (a little complicated) beacause it need to do cluster using supervised pre-trained backbones.

You can refer to DETR pre-training config, the training loss is combined with cross-entropy loss and contrastive loss. We admit that DETR-like methods do need this specific operation since the final loss should be aligned with the Hungarian Algorithm, where the bipartite matching needs class information, which is designed by DETR itself.
It doesn't look elegant and neat when we pre-train DETR, that's the truth, but we show better performance than other more complicated methods (e.g., UP-DETR) with a simple cluster-based trick.
The backbone can be either supervised pre-trained or self-supervised pre-trained, we also provide the checkpoints for SwAV backbone (a self-supervised backbone) for DETR pre-training and fine-tuning.
How to design a more simple and elegant pre-training for DETR is indeed an open question, and I am very happy to discuss it with you.

thanks for your reply. I really like to find good pre-train method for DETR series for it's the SOTA method in detection.

thanks for your reply. I really like to find good pre-train method for DETR series for it's the SOTA method in detection.

Good luck and success in advance.

I'm just the finder, you're the creator of good methods, so I really wish you success. :)


add a --with-toolset=xxx command-line parameter to bootstrap.bat

per the "bootstrap.bat broken for MinGW since 1.55" thread on boost-devel.

@danieljames should this PR be closed?  It is targeting the wrong branch, and I'm not sure if the solution is valid.

Closing in favor of #170.


[FLINK-32748] WriteSinkFunction::cleanFile need close write automaticly

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
the pr is to improve file object manage
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @reswqa have a review plz

would open a new pr to fix these


Transfer repo to Cake.Contrib org

@Roemer any issues with that?
@gep13 if there is no response here i'll transfer it

@pitermarx sounds like a plan. As I mentioned on Twitter, I can add @Roemer to the Cake-Contrib Organisation as well, with full access rights to the repository, in the same way that they might have here under your repository.

Fine for me.

@pitermarx @Roemer this has now been completed.
@Roemer I have invited you to join the Cake-Contrib Organisation, with admin rights to this repository.  Do you have a Twitter account, and an email that I can use to invite you to a Slack Team?  These are two mechanisms that we use to keep in touch with addin maintainers.
Thanks


bugfix: Native test are running on JVM mode

Driven by: #122

let's wait for ci

Is this fix applicable for 1.11 branch too?


Create version 0.1.12

Thanks for merging my proposed changes.  Can you please create a released version that can be pulled down via npm?

Published as v0.1.12

Thanks!


Fixing fastrtps installation [6487]

Fixes #751
To test this PR:

Revert changes in this PR
Install fastrtps in a local directory: mkdir build && cd build && cmake ../ -DCMAKE_INSTALL_PREFIX=install/ && make install
Navigate to the source directory of one of the examples, for instance the HelloWorld, and build it: mkdir build && cd build && cmake -DCMAKE_PREFIX_PATH=<dir>/install .. && make

You should get errors about include files not being found.
Repeat the same steps with changes in this PR. You should now be able to build the HelloWorld.

OK, then I am going to merge this and not wait for the tests, as this PR changes cmake only.


Database not being setup properly on init

using docker image, i'm seeing the following error
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/local/lib/python3.4/threading.py", line 911, in _bootstrap_inner
self.run()
File "/usr/src/app/homeassistant/components/recorder.py", line 185, in run
self._setup_connection()
File "/usr/src/app/homeassistant/components/recorder.py", line 349, in _setup_connection
""")
sqlite3.OperationalError: unable to open database file
different runs have different results sometimes it gets through recorder steps 1,2,3 before encountering the error

My configuration was using VirtualBox running docker and I was mounting my windows home directory through to the boot2docker machine and then mounting that as a volume inside the container.
when I moved the files to a directory local to the boot2docker image and restarted it worked without issues


Fix subscribedResources in install/helm

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@howardjohn PTAL

@Nino-K: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
02424055053579cc8ed292529c13c750e5002594
link
/test integ-pilot-k8s-tests_istio

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. I understand the commands that are listed here.

/cherrpick release-1.4

@Nino-K: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
02424055053579cc8ed292529c13c750e5002594
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
02424055053579cc8ed292529c13c750e5002594
link
/test integ-security-k8s-tests_istio

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. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

/test integ-security-k8s-tests_istio


no authentication is required to access the api and use any type of http method (get, post, delete) only get should be accessible without authentication

fixed with this commit

fixed with this commit


Added loading screen before load

@RocketChat/core

Closes #303

Shows loading animation while app is working out if a server exists. This stops the server input screen from being shown briefly after launching.

Very awesome, thanks for the pull request!

You are making my day today taking care of two of my personal annoyances with the current version of the app. Thank you!

Thank you so much @alexbrazier!


build-release-tarball: Generate a signed tag with --tag.

The version in the built tarball is based on the local tags; when
building official tarballs, we want them to be tagged with the right
commit prior to being built, so they report as the specific version.
Create a tag prior to building, to make sure cache-zulip-git-version
finds the version we want.
This also builds a signed tag object, not a lightweight tag.
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I don't think I've used the option to have build-release-tarball create a tag (I always create it manually), but what key would be using for signing signed tags?

It’s controlled by the tag.gpgSign Git configuration variable (documentation).
There’s also the question of which key we want to use, which is maybe what you meant.

I've dropped the pieces that generate a signed tag, as those need more discussion.  Based on this czo conversation, I've added a heuristic that anything that looks like a formal release needs to have --tag set -- as well as a third commit which double-checks the version file that is produced.  I think the third commit is unnecessary given the other two (I can't imagine how it would fail), but certainly can't hurt.


No kernel for grammar Ruby found

Hi,
The title says it all: I'm trying unsuccessfully to use a Ruby kernel with Hydrogen.
From a terminal the iruby command works fine and the Atom console doesn't report any errors regarding this problem.
I tried googling this issue but I'm kind of stuck not even knowing where to start troubleshooting.
Any guidance would be much appreciated.

OK I finally found a solution to this problem referenced here: https://github.com/nteract/jupyter-paths/issues/27


Can not use “@” to import a scss file when the file include a mixin method

Describe the bug
// helloWorld.vue

<template>

</template>

// @/assets/mixin.scss
@mixin bg($url) {
  background: url($url) center no-repeat;
  background-size: 100% 100%;
}

// vite error
  Error: expected ")".
    ╷
  3 │   background: url(../assets/$url) center no-repeat;
    │                   ^
    ╵
    src/assets/mixin.scss 3:19         @import
    src/components/HelloWorld.vue 2:9  root stylesheet

Yes In the style of Vue file, an SCSS file is introduced. If the file does not contain @ mixin method, you can use @/assets/style/mixin.scss The introduction of SCSS; If the @ mixin method is included in the modified file and "@" is used, the above error will be received.
But when I using ../assets/mixin.scss, it is normal
Reproduction
https://stackblitz.com/edit/vitejs-vite-nhc6le?file=src%2Fcomponents%2FHelloWorld.vue
System Info
System:
    OS: Windows 11
  Binaries:
    Node: 14.18.0
    Yarn: 1.22.4
    npm: 6.14.15
  Browsers:
    Chrome: 95.0.4638.69
  npmPackages:
    @vitejs/plugin-vue: ^2.0.0
    vite: ^2.7.2

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Closing as it is organized into #7651.


Subscription with payment afterwards

Our customer wants to use subscription based product delivery.
I’ve noticed that the so called “first payment amount” will only be used when a customer subscribes to a trial. That’s not really a problem in our case, since customers in my country have the legal right to cancel any subscription within 14 days of subscribing. Since products will be delivered as soon as a customer subscribes, I want to make sure that at least one order is paid should the customer decide that they don’t want the subscription within 14 days. How would I implement the described situation?
I also want the customers to get their first real bill (not the initial first payment amount payment) after a month. It’s custom in my country to pay afterwards.
Simply said: I subscribe today, I get my products within a few days and pay about a month after I initially subscribed. Then going forward this repeats, so first I get my products then afterwards i get my bill.
Maybe a tricky question, but maybe not.

Hi again @evertjanMlbrgn,

I’ve noticed that the so called “first payment amount” will only be used when a customer subscribes to a trial.

Yes. I've it on my todo list to write some documentation regarding the "first payment amount".

Since products will be delivered as soon as a customer subscribes, I want to make sure that at least one order is paid should the customer decide that they don’t want the subscription within 14 days. How would I implement the described situation?

I am not sure if I understand the issue here. Why don't you just start a subscription without trial? Then the subscription's price will be due on the first payment and you don't have to check for a paid order.

I also want the customers to get their first real bill (not the initial first payment amount payment) after a month. It’s custom in my country to pay afterwards.

That sounds like you want to use 'metered billing' or at least a variant of it. Another user asked about metered billing already. Take a look at the answer I gave here.

You can implement metered billing by configuring the order_item_preprocessors in your cashier_plans config. A MeteredBillingPreprocessor could look something like the following:
use Laravel\Cashier\Order\BaseOrderItemPreprocessor;
use Laravel\Cashier\Order\OrderItem;
use Laravel\Cashier\Order\OrderItemCollection;

class MeteredBillingPreprocessor extends BaseOrderItemPreprocessor
{
    /**
     * @param  \Laravel\Cashier\Order\OrderItemCollection  $items
     * @return \Laravel\Cashier\Order\OrderItemCollection
     */
    public function handle(OrderItemCollection $items)
    {
        // You can add, remove or modify order items here.
        // Each order item relates to 1 line on the invoice.

        // For metered billing, you typically:
        // 1. fetch metered data from within your app
        // 2. apply it to the order items
        // 3. if necessary, notify the meters that the costs were incurred/reset the meters

        $owner = $items->owners()->first();

        $meters = $owner->getMeters();
        $meterItems = $meters->map(function ($meter) {
            return OrderItem::make([
                'process_at' => now(),
                'description' => $meter->description,
                'currency' => $meter->currency,
                'unit_price' => $meter->unit_price,
                'quantity' => $meter->quantity,
                'tax_percentage' => $this->tax_percentage,
            ]);
        });

        $items = $items->concat($meterItems);

        $owner->resetMeters(); // optionally put this in a separate ResetMetersPreprocessor right after the PersistOrderItemsPreprocessor

        return $items;
    }
}

Please keep in mind that, currently, adding preprocessors to the first payment is not supported. Therefore, you may still need to reimburse the user for any overpaid amount during the first billing cycle. Additionally, scheduling the payment at the end of a cycle is not mandatory for metered billing, and it's not currently possible with Laravel-Cashier-Mollie. Nonetheless, you can still use metered billing by asking users to pay a fixed upfront amount and adding the metered component to the invoice for the next billing cycle. We're actively working on ways to make these processes easier in the next versions of our package.
Originally posted by @Naoray in https://github.com/mollie/laravel-cashier-mollie/issues/151#issuecomment-1432726192

Note: You might be able to get away with not refunding but instead enable a one month trial.

Thanks for your reply, my customer changed his mind and wants to bill immediately without a trial, just like you suggested.


Compilation error on GCC-13.

I'm encountering a CMake error when I try to compile this repository from the source using GCC-13. Compilation works when using GCC-12 CC=gcc-12 CXX=g++-12 cmake ... I attached part of the error logs below. I know CUDA 12.1 does not support GCC-13 officially and it's a pretty new release but I'm filling this issue just as a reference for people with the same problem.

Hi @luigifcruz
kindly check the online documentation for CUDA Toolkit 12.2 system requirements.
https://docs.nvidia.com/cuda/archive/12.2.2/cuda-installation-guide-linux/index.html#system-requirements
The recommendation is to use GCC version 11.4
Based on my humble experience with CUDA and as you mentioned. we can use GCC version 12.x to satisfy the NVCC (Nvidia CUDA Compiler) requirements.
Kindly check the following link:
https://docs.nvidia.com/cuda/archive/12.2.2/cuda-installation-guide-linux/index.html#host-compiler-support-policy
Please let me know if you need any additional information.

Thank you @ichergui . Moving to close as not planned to fix in Holoscan SDK.


HDDS-6219. Switch to RATIS ReplicationType from STAND_ALONE in our tests.

What changes were proposed in this pull request?
Changing the bulk of our tests that are still based on the STAND_ALONE replication type for writes, that we do not use anymore in general for writes. (Though some clients still support writing with it)
One thing remains after this, the TestContainerMapper class, that is a problematic one, as its assertions can not be simply translated to assertions against the RATIS client. Probably that is a more involved thing to change the whole test, or find out what assertions we can safely make. I will create a separate JIRA to track that one test.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6219
How was this patch tested?
Run the integration tests set a couple of times during dealing with some of the issues, the last run failed only the TestContainerMapper, which I have reverted to still use the STAND_ALONE replication type. To track that I have created HDDS-6222.

Thank you for the review @adoroszlai I merged the PR.


Populate select items from query

I have read the doucmentation and i still think i am missing something
I want the values in my dropdown to simply be the returned values from one column in my SQL, i thought it would just do that without adding any additional code, but that doesnt seem to happen. What am i supposed to put in value?

It will be a part of the upcoming release: https://github.com/VolkovLabs/volkovlabs-form-panel/pull/254


cant add my own teachablemachine.withgoogle.com models

when i try to add my own model i have this error? what it might be?
[ERROR:flutter/runtime/dart_isolate.cc(993)] Unhandled exception: E/flutter ( 6540): RangeError (index): Invalid value: Only valid value is 0: 1 E/flutter ( 6540): #0      List.[] (dart:core-patch/growable_array.dart:183:60) E/flutter ( 6540): #1      Classifier.predict (package:object_detection/tflite/classifier.dart:118:65) E/flutter ( 6540): #2      IsolateUtils.entryPoint (package:object_detection/utils/isolate_utils.dart:45:51)

@assanbayev Can you please share the reproducible code and corresponding error log. At first glance from what you have shared it looks like a local error with your code and might not be related to the plugin.

Closing this as the error doesn't seem to be due to the plugin, please feel to reopen if required.


I found 10 structures on multiplayer, and it said no world seed found.

I found 10 structures. I even cleared data and found another 10 with no luck (all 20 structures I found were shipwrecks).
I was wondering whether my version of SeedCrackerX was broken. I went on a new single player world (1.19.2) and teleported myself to liftable structures and SeedCrackerX found the correct seed.
Am I doing it wrong?
Is there something I should do that's different on multiplayer?
Info that might be useful: The server had Anti-Xray on diamonds (Displayed as stone when not in close range) and no other ore (Maybe netherite but I never tried)
The server is on 1.19

Some servers change structure generation to protect themselves against seed cracking. Usually it gets real nasty to crack those and the mod cant do it

Some servers change structure generation to protect themselves against seed cracking. Usually it gets real nasty to crack those and the mod cant do it

That's what I was thinking.
The server is simplyvannila.co
Is this server known for using custom seed gen?


[Regression] - V2 - Contributor Console - Not able to contact company admin

Prerequisite

Create CLA group with CCLA enabled
Add github repository for the CLA group

Steps to Follow

Login to Github as corporate contributor
Navigate to the repository used in prerequisite
Create PR
CLA check fails
Click on CLA NOT SIGNED
Contributor is redirected to Contributor Console
Click on Proceed as a Corporate Contributor
Select Company that has not signed CLA for the project
Click Proceed
Click No
Click Contact Company Admin
Observed that request failed

Verified that the issue is fixed


RescheduleLazy should be only allowed in DetachedCoroutine

Search before asking

[x] I searched the issues and found no similar issues.

What happened + What you expected to happen
By the design, the RescheduleLazy  should be only launched by RescheduleLazy ::start method, which will co_await the RescheduleLazy itself in a DetachedCoroutine. However, currently we can co_await a RescheduleLazy actually like the discussion mentions https://github.com/alibaba/async_simple/discussions/162:
SimpleExecutor e;

Lazy<void> bar() {}

Lazy<void> foo() {
    co_await bar.via(&e); // Not allowed
}

This is confusing. We need to ban such uses explicitly.
Reproduction way
Anything else
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

https://github.com/alibaba/async_simple/blob/aa1d71804778f5d1dda71f628dd4e40725ae42ea/async_simple/coro/test/LazyTest.cpp#L359


[PLANNER-575] war+ear plugins: upgrade plexus-archiver to 3.0.3 to support JDK9

+1 (We might want to add a comment to indicate why we're adding the workaround, so it's clear when we can delete the workaround once we upgrade to a newer jar/war/ear plugin version.


In file "Reference-Guide-For-Quantum-Computing-A-Microsoft-Garage-Project/3-Quantum_Hardware_Systems/1-Natural_Qubits.ipynb"

Thank you all for this project.
Just FYI:
In file "Reference-Guide-For-Quantum-Computing-A-Microsoft-Garage-Project/3-Quantum_Hardware_Systems/1-Natural_Qubits.ipynb"
First paragraph of "3.1 Natural Qubits":

In Stern-Gerlach experiment they fired "Silver atoms" but not hydrogen atoms.
They fired silver atoms "through an inhomogeneous magnetic field" but not uniform magnetic field.

Thank you,
Best Regards.

--


How to open link in external browser instead of in-app (instagram)?

hello everyone, I have a problem with redirecting instagram to my website, instagram and facebook open the links through their own webview. causing my website in flutter not to open correctly in IOS. Is there a way to use this package to detect the user agent and redirect Safari? something like this: https://stackoverflow.com/questions/50212683/how-to-open-link-in-external-browser-instead-of-in-app-instagram

Hi, I do not think this package will solve your issue. There is no sure way to know that web is in in-app browser. I personally dislike in-app browsers too. But this is something you need to convince devs of Instagram to stop using.


feat: polish some bugs (#7)

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[ ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ ] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description
This adds some polish to a few bugs found during play. Mainly updating some dice calculations.

Character Sheet Info Roll20 Internal Use only.


实现用于比赛的submit分支

TODOs
Repo management

[x] Add test suits
[x] Add test script and CI
[x] Modify Makefile so that it compiles and produces kernel-qemu and sbi-qemu
[x] #24

Kernel design

[x] #18
[x] #19
[x] #20
[x] #21
[x] #22
[x] #23

初赛目标已完成


SAK-44549 - Update references to morpheus-default/tool.css in tool markup

Formerly this "in tool" markup pointed at /library/skin/default/tool.css - the 404 was harmless unless the tool was not inlined into the portal markup (i.e. in an iframe).

@adrianfish Could you check to see if this will cause heartburn in trinity?  It is a simple fix - just as easy to do post-trinity merge or pre-trinity merge.   If it does not collide with anything in the trinity branch, it would be nice to put this in quickly and move along.

I am going to close this pull request and revisit it after 23.


Improve form error messages

Current error messages aren't descriptive and users may be confused.

Also note that the bar style and the border style are wrong.

IE magic ✨  Will try to fix that too


It still seems to work with webpack 3, did something break?

If you released changes that broke webpack 3 compatibility, that is a major version bump, not a bug fix.  Everyone is using ^ in their package.json by default, so you may be breaking legacy apps by making breaking changes without using semver.

I also wondered about the Webpack v4.0.0 requirement in the readme but no visible major bump. So is it required to use Webpack 4 to use the latest version of file loader?

Loader works find with webpack@3 and webpack@4. What is problem?

That the README says it requires a minimum of Webpack 4.

@renestalder see, feel free to send PR, readme is misleading


Push only button event

I want to turn the LED on by pressing the button and then when I want to turn the LED off then I press the button again. That means I do not want to handle the release state. The LED will be on unless I press the button again to turn it off. Currently when I use the "watch" method then it listens to both press and release. The LED is on when I press the button and is off when I release the button. Is there a way to achieve this in onoff?

The value argument passed to the watch callback can be used to determine if the button was pressed or released. If value is 1 the button was pressed. If value is 0 the button was released. So if you're only interested in handling button press events then check to see if value is 1 in the watch callback. If it is, the button was pressed.

Great I achieved it using a legacy(but still amazing) logic :).
`let counter = 0;
button.watch((error, value) => {
if (value === 0 && counter >= 1) {
led.writeSync(0);
counter--;
return;
}
if (value === 0 && counter <= 0) {
    led.writeSync(1);
    counter++;
    return;
}

});`

Ok, good to hear.


Updated 400 status code on failed validation tests

Fixed failed validation tests after updating 406 status codes to 400.

We should be using HttpStatus codes for this kind of thing (they're easier to refactor), but maybe slip that in next time: https://docs.python.org/3/library/http.html#http-status-codes


diceware: 0.9.6 -> 0.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/diceware/versions.
meta.description for diceware is: "Generates passphrases by concatenating words randomly picked from wordlists"
meta.homepage for diceware is: "https://github.com/ulif/diceware"
meta.changelog for diceware is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10/bin/diceware had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10/bin/.diceware-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.10 with grep in /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10
found 0.10 in filename of file in /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10

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

6 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
diceware
python310Packages.diceware
python39Packages.diceware

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10 \
  --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 diceware https://github.com/r-ryantm/nixpkgs/archive/32fe1c49110fef42a5c6b8c5ffbab5ed980abaf0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10
ls -la /nix/store/pirhpwfcbmxqkgarzxjrkwmjgg600f1j-python3.9-diceware-0.10/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.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

diceware (python39Packages.diceware)
python310Packages.diceware

Maintainer pings
cc @asymmetric for testing.

@ofborg eval


Update conda-build-all mechanism to be aware of which python versions each recipe supports

Not all packages in omnia support python 3.x versions, so we will need to build some sort of infrastructure that tracks which versions of python are supported by each package and only builds these versions.

I'm not sure that this is actually required. Those packages just simply fail to build, and don't get deployed.

I'm going to close this--our current infrastructure seems to work fine for building and uploading any package that builds successfully.  We will revisit this when we reach omnia 1.1 and py3K support.


Trying to make a fix to get_posts, how can I figure out iphone endpoints?

Get posts is broken when you are logged in (at least with a session file).
As attested to here:
https://github.com/instaloader/instaloader/issues/2319
I remember when get_comments was broken the author switched to an iPhone endpoint, and posted the gist of the code here:
https://gist.github.com/aandergr/35ad3881e726e2be8925cf09e719a68b
I'm having trouble figuring out the endpoint for posts of users however.
So far I'm trying variants like:
f"api/v1/users/{user.userid}/posts/"
or
f"api/v1/users/{user.userid}/info/posts/"
inspired by the iPhone structs in the source code and especially
f"api/v1/media/{post.mediaid}/comments/"
From the temporary (gist) solution he posted.
However, I am getting 404s.
Is there an API reference? I'm having trouble finding it if there is.

https://www.instagram.com/api/v1/feed/user/{user.userid}/

Get posts is broken when you are logged in (at least with a session file).
As attested to here: #2319
I remember when get_comments was broken the author switched to an iPhone endpoint, and posted the gist of the code here: https://gist.github.com/aandergr/35ad3881e726e2be8925cf09e719a68b
I'm having trouble figuring out the endpoint for posts of users however. So far I'm trying variants like: f"api/v1/users/{user.userid}/posts/" or f"api/v1/users/{user.userid}/info/posts/"
inspired by the iPhone structs in the source code and especially f"api/v1/media/{post.mediaid}/comments/" From the temporary (gist) solution he posted.
However, I am getting 404s.
Is there an API reference? I'm having trouble finding it if there is.

Hi, I answered at https://github.com/instaloader/instaloader/issues/2319. You can check and comment. I hope your problem will be solved.

I tried it on an Android Emulator, too bad the app uses certificate pinning and my knowledge on the work around is a bit limited, I know it is possible but takes install of other tooling which was quite a lot of steps.


chore(kai): update deploy configurations

Current dependencies on/for this PR:

main

PR #2605   👈

PR #2606

This comment was auto-generated by Graphite.

⏳ This pull request is set to merge as part of a Graphite merge job
Job ID: cPVzYW2K0Oln4nuti1US.
See details on graphite.dev


caddy: 2.6.4 -> 2.7.2

Diff: https://github.com/caddyserver/caddy/compare/v2.6.4...v2.7.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

I'll mark this as draft until https://github.com/caddyserver/caddy/issues/5671 is resolved and the fix released.
Thank you

Thanks @emilylange :) I've just pushed the patched release of caddy.

ofborg seems to be failing with
 > (finished: must succeed: curl --fail -v 'http://localhost/example.html' 2>&1 | sed -n -e "s/^< [Ee][Tt][Aa][Gg]: *//p", in 0.05 seconds)
       > webserver: must succeed: curl --fail --silent --show-error -o /dev/null -w "%{http_code}" --head -H 'If-None-Match: ' http://localhost/example.html
       > (finished: must succeed: curl --fail --silent --show-error -o /dev/null -w "%{http_code}" --head -H 'If-None-Match: ' http://localhost/example.html, in 0.02 seconds)
       > Test "check ETag if serving Nix store paths" failed with error: "HTTP code is 200, expected 304"
       > cleanup
       > kill machine (pid 8)
       > webserver # qemu-kvm: terminating on signal 15 from pid 6 (/nix/store/jhflvwr40xbb0xr6jx4311icp9cym1fp-python3-3.10.12/bin/python3.10)
       > (finished: cleanup, in 0.02 seconds)
       > kill vlan (pid 7)
       For full logs, run 'nix log /nix/store/j2p46rvjq0xyx4cnid13qbggsvrv0smc-vm-test-run-caddy.drv'.

I'm not the one who wrote that test, I just saw this and thought outlining it might help.

Caddy 2.7.2 has been released (diff)
Seems like 2.7 is having a bit of a rocky launch, may be best to hold off updating for a bit until it stabilizes.

The VM test fails because Caddy no longer emits an etag for files with unix time 0 or 1, specifically implemented for nix environments.
See https://github.com/caddyserver/caddy/pull/5550, https://github.com/caddyserver/caddy/pull/5547 and https://github.com/NixOS/nixpkgs/pull/222354
I'd argue in favor of removing our etag subtest for now, and I'll try (no promises though) to reimplement it, including a test for the new etag override, some time in the future.

Happy to remove it for now.

Caddy 2.7.3 has been released (diff)

Closing in favour of @emilylange's updated PR


Vendor Link does not work

http://www.cecropiasolutions.com/ is loading endless

Link seems to be working, but thank you