composer require fails with Undefined index: controllers_base_namespace

composer require always fails because of an Undefined index: controllers_base_namespace.
> composer require sentry/sentry-laravel
# [...]
Writing lock file
Generating optimized autoload files
composer/package-versions-deprecated: Generating version class...
composer/package-versions-deprecated: ...done generating version class
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   ErrorException

  Undefined index: controllers_base_namespace

  at vendor/sentry/sentry-laravel/src/Sentry/Laravel/ServiceProvider.php:111
    107|     protected function configureAndRegisterClient(): void
    108|     {
    109|         $userConfig = $this->getUserConfig();
    110|
  > 111|         Integration::setControllersBaseNamespace($userConfig['controllers_base_namespace']);
    112|
    113|         $this->app->bind(ClientBuilderInterface::class, function () {
    114|             $basePath = base_path();
    115|             $userConfig = $this->getUserConfig();

      +9 vendor frames
  10  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Installation failed, reverting ./composer.json to its original content.

This error is caused by a newly introduced configuration param. The package should handle this even if its just an php notice, but apparently during composer it will cause a hard error.
Only option is to downgrade composer require sentry/sentry-laravel:2.0. I thought I could simply add the newly introduction config option and upgrade, but this doesn't work because the configuration is allowlisted. This won't let me upgrade with the config option already added.

This should of course never happen, I'm sorry it still did! Working on a fix for this.

2.1.1 was just released which should fix the issue 😄


Add twitter card

looks good to me - it would be really really really cool if we could dynamically generate twitter:image, such that if we are only showing one ayah, just use the url for the retina image for that ayah.

Do we have an official twitter account? If not I can make it just let me know ikhwa.

@muhsinali all the ones we should have are taken... so i will file with twitter a claim. Especially @quran_com

@ahmedre I agree, it'd be cool to dynamically generate them. Where are the retina images?

http://quran.com/images/ayat_retina/{sura}_{ayah}.png
ex:
http://quran.com/images/ayat_retina/1_1.png
http://quran.com/images/ayat_retina/2_14.png
if these are too wide, can probably generate less wide ones.

@ahmedre i think social media auto adjusts it.

closing for now


Generate unique workqueue names.

This changes the names we give workqueues in genreconciler to avoid collisions when multiple reconcilers in a single process use the same generated reconciler base.
There are a few examples of this in serving, both route and configuration have collisions.  Right now I think this mainly affects metrics published by the workqueues, but I noticed this leveraging the same for resource lock naming.

/lgtm
/approve


Parameter that triggers the action to only output the commands, not execute them

For debugging parameters and similar stuff it would be nice to have a "dry run" option.

How does Fastlane in general and other plugins handle "dry run"?


Styles are not generated when using @container query

Environment
System:

OS: macOS 13.4.1
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 77.75 MB / 8.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
pnpm: 8.4.0 - ~/Library/pnpm/pnpm

npmPackages:

styled-components: 6.0.6 => 5.2.1

Reproduction
For container div
.container {   container-type: inline-size; }
For child div
.child {   background: red;   @container (max-width: 300px) {     width: 200px;   }   @container (min-width: 301px) {     width: 300px;   }
Steps to reproduce
NA
Expected Behavior
CSS style with width property is generated
Actual Behavior
CSS style with width property is not generated

Can reproduce this issue using<EMAIL_ADDRESS>

Any news on this one?

Anything we can do to get this fixed?

seems related to https://github.com/styled-components/styled-components/issues/3911

Hi, same issue, I've installed styled-components 5.3.11 and seeing the same issue. It would be super useful to get an estimation regarding a fix for this issue 🙏


[SPFX ListCommandSet] _onListViewStateChanged event will never trigger if it is in grouped list view and this group has only one item

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx 1.19 version  (I tried to create a helloworld list commandset with 1.20, it never load in new list UI...)
Node.js version
etc

Describe the bug / error
I guess this issue maybe related with #9944
We have a spfx list command set with a customized button
Like this screenshot

This week we suddenly find it doesn't work (button doesn't show) in grouped list view when there is only one item in this group

For example, if there is only one pending item in "Approve/Reject" view, then our customized button will never appear.
I debugged the code and find _onListViewStateChanged event will never trigger if there is only one row in group on grouped list view.

I saw there is closed similar issue #7794 but that one is not for new list UI.
Steps to reproduce

Create a list view commandset extension as https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api said (why this sample page still use the deprecated public onListViewUpdated(event: IListViewCommandSetListViewUpdatedParameters): void method as example?)
Run this spfx extension on a list which has grouped list view (You can just enable approval on this list, then you will get "approve/reject items" view which group by approval status
You will find that the "Command One" button will never appear if you have only item in the group

Expected behavior
The _onListViewStateChanged event in List View CommandSet Extension should work as expected in grouped list view

We're seeing issues with this as well. This seemed to be fixed / working for a while and then noticed this week it stopped working

@reedpamsft something on the list experiences with SPFx

@VesaJuvonen @wuxiaojun514 @Feets20   thanks!  Feets20 reported this on the other thread and we're looking into it.

@VesaJuvonen @wuxiaojun514 @Feets20  we have a fix for this which will roll out with new client builds in January; eta the week of the 13th.  Emphasis on "estimated", though.  The first build of a new year is often delayed.


ScheduledTask: Delay parameter applicability

Details of the scenario you tried and the problem that is occurring
According to documentation:

Delay | Write | String | Specifies a delay to the start of the trigger. The delay is a static delay before the task is executed. Can only be used in combination with ScheduleType OnEvent.

Is there a specific reason why Delay is only applicable to OnEvent ScheduleType?
Because while creating task in GUI, this parameter is applicable to every ScheduleType except OnIdle (where it is disabled, for obvious reasons) and On a schedule (where it is replaced by RandomDelay)
In my experience creating tasks with ScheduleType = AtStartup and AtLogon is a very common scenario, but setting delay for such tasks is currently not supported by the dsc resource.
Suggested solution to the issue
Delay parameter has to be applicable to ScheduleTypes AtStartup, AtLogon and other types to match behavior of GUI Task Scheduler editor.

Hi @SDedik - sorry about the delay in looking at this. I've unfortunately not had time to keep on top of these.
It is possible the reason this wasn't implemented was earlier versions of the PowerShell cmdlets/objects may not have supported it.
But if it supported by the cmdlets then we can implement it - just need a PR. I will try and get to it if no one else does.


Bug Fixes & Improvements

Fixed

Low Quality output image.
Release Camera and Microphone access when close camera screen.

Added

Close Button on camera screen, Default it is visible but can hide it with isHideCloseButton to true in configuration.
Open camera screen with single lens when user tap on a lens list.

Updated

Package implementation guide.
Example Project
README.md

Thank you so much

You're welcome @dokind


Document: Add MaxACPower hybrid battery setting

We need to document the new feature introduced in this PR: https://github.com/evcc-io/evcc/pull/16609

Short descriptions is available at all hybrid inverters with this setting.
Features was described in the last blogpost https://docs.evcc.io/blog/2024/11/22/highlights-charts-stats#hybridwechselrichter-mit-beschränkter-ac-leistung


Revert previous change

The system is still buggy (I think robotname is not determined by CLI flags) so I'll just revert the change to previous function (even though doesn't align with readme). Probably related to how environment registration works.

ok


[CLI] Init support for creating swift projects

Fixes #1670
Updates the CLI to support a new --swift flag. When set, init will generate a swift project instead of an objective-c one.
I also added tests for react-native-cli. Covers most code paths, but not all.
FYI for anyone that wants to try this out: You need to follow https://github.com/facebook/react-native/blob/master/react-native-cli/CONTRIBUTING.md to get your environment setup properly.

Thanks for this!  With my few comments, I was able to start up a Swift project successfully.
:bird:

Thanks for the feedback. I will make the suggested changes. I also need to make some updates now that android generator has dropped. Should have this ready for review again in a couple days.

PR should be ready to go. Only thing blocking this now is broken CI, which seems to be an issue across the board. Issue here: https://github.com/facebook/react-native/issues/2939
@mkonicek could you review this PR for me?

Any movement on this?  Really looking forward to an officially sanctioned way to start these projects.

I just got CI passing now. Just waiting for a review.
@brentvatne any help on getting this one merged? I know the FB guys are not using Swift so they may not consider this a priority.

I'll try this out tonight @nsimmons!

Scratch that, on the plane tomorrow night ;)

What do you think @brentvatne? I've been using this to generate my own Swift projects, but it gets a little hairy since it's seems based on 0.8.0 react and quite a lot has changed in terms of file structure.

cc @foghina on generator stuff, I'm not familiar with it.

@nsimmons sorry for the long turnaround – your diff is pretty big. Would be awesome if you could split it into several chunks: unit tests for react-native-cli, swift boilerplate

Generator stuff looks legit. Agree with @frantic on splitting react-native-cli stuff into a separate PR, doesn't seem related.

I removed the react-native-cli changes. I will create a new PR to add tests for the current version of the CLI.
I still need to rewrite the bridging header generation code in pure JS, and this branch currently depends on #3272 to work properly. I will rebase once that PR is merged.

@nsimmons feel free to assign your react-native-cli tests PR directly to me or @martinbigio

There was some issue with GitHub where only Collaborators could assign tasks, but GitHub recently made some big updates to how orgs work. I believe it is now possible to add Collaborators (perhaps with read-only access) without adding them to your organization. (cc @vjeux @jamesgpearce -- you can get to the new GitHub org config through https://github.com/orgs/facebook/migration).

I'm on vacation till next week, sorry for the delay. Once I am back home I will wrap this PR up and create the PR for CLI tests.

@nsimmons be aware that we're moving to a more extensible and tested cli. When you update the code please add the new code to private-cli instead. The entry point might not be local-cli/cli.js within a week :)

Rebased the PR. Taking a look at the new cli code under private-cli. I will move my changes there.
private-cli does look much better by the way!

react-native init AwesomeProject --swift
still build object-c project
react-native  version is 0.1.7

Any updates on this?

@foghina would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

Nice that the new bot kindly reminds us about the PR :)
Was there a consensus whether we want this in RN by default? We're planning on designing a solution for writing CLI plugins (cc @grabbou). It will still take a while.
This is a big PR though, should we wait and make it a plugin once it's possible?

A plugin could be good -- IIRC Swift is an explicit non-goal?

Yeah, 1477 files sound a lot. I think given the fact most of (if not all) RN code is in Obj-c, support for Swift could go as a separate (community-driven) plugin.

OK let's close this PR. @nsimmons are you fine with that? There'll be a post in the React Native Community group once it's possible to write plugins for the CLI: https://www.facebook.com/groups/react.native.community/

Fine by me!

:+1: Thanks for looking @nsimmons.


yarn create slate-theme fails on node dependency conflict

Problem
yarn create slate-theme fails on node dependency conflict #595
Development $ yarn create slate-theme shopify-project
yarn create v1.7.0
[1/4] 🔍  Resolving packages...
⠁ (node:98211) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - create-slate-theme
[#########################################################################################] 136/136
Creating a new Slate theme in: /Users/uho/Development/shopify-slate.
Cloning theme from a git repo: https://github.com/shopify/starter-theme.git
Installing theme dependencies...
yarn install v1.7.0
[1/4] 🔍  Resolving packages...
⠁ (node:98219) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[2/4] 🚚  Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=4 <=9".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
(node:98212) UnhandledPromiseRejectionWarning: Error: Command failed: yarnpkg
    at makeError (/Users/uho/.config/yarn/global/node_modules/execa/index.js:169:9)
    at Promise.all.then.arr (/Users/uho/.config/yarn/global/node_modules/execa/index.js:274:16)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:98212) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:98212) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 4.04s.

shopify-project $ yarn install
yarn install v1.7.0
[1/4] 🔍  Resolving packages...
⠁ (node:98197) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[2/4] 🚚  Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=4 <=9".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Replication steps
More Information
Any additional information which might be helpful.

workaround with --ignore-engines

wow these tools and documentation are bad and hard to use

https://localhost:8080 renders error
Cannot GET /

Hi @kryali, you've stated two separate issues here. For the first, can you run node -v and let us know what version of Node you're currently running?
As for Cannot GET/, I'll redirect you to this comment that has already addressed this. We are looking into ways we can address the confusion around this, but for now realize that what you're seeing is normal if accessing localhost directly.

Hey @chrisberthe, appreciate the help. Here is my node version below.
node -v
v10.2.1

Agree that the documentation could be much better here.

Could you test with the current 8.11.2 LTS version and see if that solves the issue and report back?

Is there a handy way to change node versions? Don't know a whole lot about node version management, sorry.

Have a look at nvm @kryali

things look good on 8.11.2
Development $ node --version
v8.11.2
Development $ yarn create slate-theme shopify-project
yarn create v1.7.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 📃  Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - create-slate-theme
[########################################################################################################################################] 136/136
Creating a new Slate theme in: /Users/uho/Development/shopify-project.
Cloning theme from a git repo: https://github.com/shopify/starter-theme.git
Installing theme dependencies...
yarn install v1.7.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "@shopify/slate-tools ><EMAIL_ADDRESS>has unmet peer dependency "babel-core@6".
warning "@shopify/slate-tools ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@shopify/slate-tools ><EMAIL_ADDRESS>has incorrect peer dependency "webpack@^3 || ^2 || ^2.2.0-rc.0 || ^2.1.0-beta.0 || ^1.13.2".
warning "@shopify/slate-tools ><EMAIL_ADDRESS>has incorrect peer dependency "webpack@1 || ^2.1.0-beta || ^2.2.0-rc.0".
warning "babel-preset-shopify > react-hot-loader ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0-beta || ^16.0.0".
warning "babel-preset-shopify > react-hot-loader ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0-beta || ^16.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency "eslint@<5 >=4.7.1".
warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency "eslint@^3 || ^4".
warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0".
warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4.0.0".
warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "eslint-plugin-shopify ><EMAIL_ADDRESS>has unmet peer dependency "typescript@*".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "stylelint-config-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^9.0.0".
warning "stylelint-config-shopify ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^9.0.0".
[4/4] 📃  Building fresh packages...
✨  Done in 13.60s.
✨  Done in 16.21s.
Development $

Just tried this on v10.4.1, doesn't seem to be an issue anymore?


Ignore synthetic key presses

This PR discards "synthetic" winit keypresses, as discussed in the issue #4513.

Closes https://github.com/emilk/egui/issues/4513

Thanks!

Needs cargo fmt

done


Allow for a "missing image" image setting

If an imagespec references an imagefield that does not have a file, this will raise a ValueError exception.
This can cause entire gallery pages or the admin to err even if the issue is just with a single model
I propose a setting: IMAGEKIT_MISSING_IMAGE which would be a str URL, or a callable (not sure what if any args it would take, maybe the original imagespec - or the model instance?)
This would then be the URL used for ie, model_instance.thumbnail_imagespec.url
a callable would allow something like the use of http://placehold.it

Can you try the latest version from the develop branch? No error should be thrown.

As far as IMAGEKIT_MISSING_IMAGE goes, something like that was suggested by @albrnick in #13. I can see why you'd want it, but I think that ultimately it would end up introducing confusion into the API. (Are specs that use IMAGEKIT_MISSING_IMAGE still falsy, etc.)
The other thing is that the current behavior is very much in the vein of ImageField. (Or at least it should be! If you're still getting an error, that's a problem!) Providing default images for ImageSpecs and ProcessedImageFields can be done with exactly the same code you'd use for an ImageField; so you can use the same templates and template tags.
So I think that that's probably a feature we won't be adding. (Sorry!)

Ah. You don't actually have to catch the error, you could just do something like this:
@property
def whatever(self):
    return self.thumbnail.url if self.thumbnail else 'default.jpg'

A template tag might be nicer though.

Hm…what admin template are you using? The most recent built-in one looks like this:
{% if thumbnail %}

{% endif %}

So if there's no image, it shouldn't show anything (or raise an exception).

yes - I had copied the original template snippet into the project...
Using the current template and all is well


Create Footer

Footer is missing in the website. Can I add footer please?

Footer is missing in the website. Can I add footer please?

hey @RiyaGupta89 footer is already added by another contributor. Sorry I am closing this issue


How can we run a unit test with a normally hydrate frontend?

Today I tried to setup a new playground with cargo-leptos (with the template).
I tried to add the test  from the counter example, but somehow it fails to find any div.
I have seen a comment regarding client side tests in main.rs. Do I need to add a main there?
BTW There are some imports missing on the Counter test example. Should I open a PR for that one?

Today I tried to setup a new playground with cargo-leptos (with the template).
I tried to add the test from the counter example, but somehow it fails to find any div.

Could you share a reproduction repo?

BTW There are some imports missing on the Counter test example. Should I open a PR for that one?

Yes, please!

Thanks for the quick reply.
I pushed a minimal reproducer to
https://github.com/eiswind/hello-leptos/blob/main/tests/mod.rs
The console.log shows that the div does not seem to be mounted at all.
Hope you can make something of it.
For the counter test example, I opened
https://github.com/leptos-rs/leptos/pull/588

Ahhh okay here's a good one. It's simply because, if you run this with wasm-pack test, Leptos has neither the ssr (server-side rendering of HTML) nor hydrate (rendering in browser after SSR) features enabled, so the Leptos rendering does nothing.
If you run this was wasm-pack test --features=hydrate it works as expected.
I'd also note that cargo-leptos comes with integrated Playwright testing. You can find the tests in end2end and run them with cargo leptos end-to-end. Playwright is a pretty polished testing experience for e2e testing, although you do need to write the tests in JavaScript.

OH! Thanks for helping me out with that one. It's working ! :)


Approved Client App - Does it require MS Authenticator to be installed

We established a CA Policy with "approved Client App" settings.
Now the users getting a prompt to install MS Authenticator and Register the device.
Is this a requirement if we're using the "approved client app" control?

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

ID: 0073f5a8-daf6-7f14-127f-e0c9d80af78d
Version Independent ID: d6d0afdf-3619-ca03-718b-a40bfd07bab9
Content: Azure Active Directory Conditional Access settings reference
Content Source: articles/active-directory/conditional-access/technical-reference.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

Intune App protection uses authenticator as a broker app on iOS devices and Intune company portal as a broker app on Android devices. A broker app is required for app protection to work. Please see here for more information: https://docs.microsoft.com/en-us/intune/app-based-conditional-access-intune

@pedrr Thanks for your feedback! We will investigate and update as appropriate.

Thanks @gpartridge2004! @pedrr do you have anymore questions in regards to this?

@pedrr Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day tomorrow. Please reopen this git issue if you have anymore concerns. Thanks


Externalized RDS config to a new resource

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2916/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/410/


leetcode-sliding window median

Problem Link
https://leetcode.com/problems/sliding-window-median/
Coding platform
Leetcode
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

Additional context (OPTIONAL)
Would like to submit the solution for c++

please assign this to me under crosswoc

Go for it @pri1311

I want to solve it in python
Please assign me this issue as a part of Cross Woc

can i work on it in C++

@arbazalam01 C++ is not open for this issue.

@abhinav5481 This issue is open for C and C++. In which language you want to code?

I would like to code in C. Please assign it to me.

Sure @abhinav5481 Go for it :)

Hi @Nivedita967
Can I do this in C++?

I would like to code in C. Please assign it to me.

Hi @Nivedita967
Can I do this in C++?

C++ is done for this issue.


fix: video renderer Argument or IndexOutOfRangeException crashes

Fixes #333
Fixes #332
The try...catch(ArgumentOutOfRangeException) { } variant killed performance instantly with Duke Nukem II.
Sound stopped, video stopped, everthing stopped forever.
Tested successfully on:

Hero Quest
Duke Nukem II
Cadaver intro

I think there may be an underlying problem/bug here, if adding a catch has any effect on performance.
In my measurements of a release build with catch statement, I get an average of 2.0-2.1 milliseconds per frame. Without the catch statement it's also between 2.0 and 2.1 milliseconds.
In a debug build I do see a very slight difference where catch is 0.05-0.1 milliseconds per frame slower. Of course this only means the delay loop has to wait a little bit less.
If the exception is thrown more than twice during the start of the game, this also indicates a different problem, because as far as I see it only switches resolution twice.


[v4] MatchProvider.render() fails to return valid react element

Taking v4.0.0-2 for a spin after checking out the website. But I keep running into this error:

I thought that perhaps one of my components were what was causing the issue but I went through all of them and could not find any reason in my components but still same error. So then I removed <Navbar /> component and all <Match /> components  except for the first one that uses the pattern '/' and it worked. But As soon as I add one more to the mix it fails. So I thought okay what If I add another  that renders the same HomeContainer component. Again it still failed to render.
Heres the code that fails:
import React from 'react';
import Router from 'react-router/BrowserRouter'
import Match from 'react-router/Match'
import Miss from 'react-router/Miss'
// other components...

render(
  (
    <Provider store={store}>
      <Router>
        <Navbar isAuthenticated={true}/>

        <Match exactly pattern='/' component={HomeContainer}/>
        <Match pattern='/:username' component={ProfileContainer} />
        <Match pattern='/:username/:repo' component={RepoContainer} />
        <Match pattern='studio' component={StudioContainer} />
        <Miss component={NotFound} />
      </Router>
    </Provider>
  ), document.getElementById('app')
);

This code below works:
import React from 'react';
import Router from 'react-router/BrowserRouter'
import Match from 'react-router/Match'
import Miss from 'react-router/Miss'
// other components...

render(
  (
    <Provider store={store}>
      <Router>
        <Match exactly pattern='/' component={HomeContainer}/>
      </Router>
    </Provider>
  ), document.getElementById('app')
);

This code also fails:
import React from 'react';
import Router from 'react-router/BrowserRouter'
import Match from 'react-router/Match'
import Miss from 'react-router/Miss'
// other components...

render(
  (
    <Provider store={store}>
      <Router>
        <Match exactly pattern='/' component={HomeContainer}/>
        <Match pattern='/lol' component={HomeContainer} />
      </Router>
    </Provider>
  ), document.getElementById('app')
);

I've tried to follow along with the website but can't seem to find a fix.

The router needs to have just one child. Try wrapping the children with a div like so  -
  <Router>
    <div>
      <Match exactly pattern='/' component={HomeContainer}/>
      <Match pattern='/lol' component={HomeContainer} />
    </div>
  </Router>

@threepointone thank you!

I just run into this, the docs seem to suggest (incorrectly) that multiple children can be there:
https://react-router-website-xvufzcovng.now.sh/quick-start
(also, there is an overflow: hidden on one of the top wrapper elements, so the docs are not scrollable)

This is fixed in #3849. Whenever Ryan can update the site, it'll have a <div> wrapper.

Indeed, this isn't obvious at all, especially given the claim that "if you know React you can use React Router". Regular React components don't have this restriction. Any chance it could be lifted, perhaps just by adding the  automatically if it isn't there?

Another related pitfall: if you have a container component whose render method is merely:
render = () => (this.props.children)

@aaugustin It's definitely a deviation from React's DOM components, which all (I think?) accept multiple children. But it's actually not uncommon for compound components. In fact, there even exists a special method, React.Children.only, specifically for the case of compound components that only accept a single child. I'm going to amend the code to use it here so people aren't surprised.

@mjackson https://github.com/yahoo/react-intl/blob/master/src/components/provider.js#L173

@aaugustin How can you do the props.chidren method you mentioned in v4?

For example:
class GATracking extends React.Component {

    static propTypes = {
        children: PropTypes.node.isRequired,
    }

    static contextTypes = {
        location: locationPropType.isRequired,
    }

    componentDidUpdate(prevProps, prevState, prevContext) {
        const {location} = this.context
        if (location !== prevContext.location) {
            // Set the tracker to the current page so it is set for other events
            // See: https://developers.google.com/analytics/devguides/collection/analyticsjs/single-page-applications
            typeof window.ga === 'function' && window.ga('set', 'page', location.pathname + location.search)
            // Signal page view
            typeof window.ga === 'function' && window.ga('send', 'pageview')
        }
    }

    render() {
        return this.props.children
    }
}


fix bug that fails during file creation

Codecov Report

Merging #33 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #33      +/-   ##
=========================================
+ Coverage   87.69%   87.7%   +<.01%
=========================================
  Files          24      24
  Lines        1243    1244       +1
=========================================
+ Hits         1090    1091       +1
  Misses        153     153

Impacted Files
Coverage Δ

atcodertools/tools/envgen.py
63.35% <100%> (+0.28%)
: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 5e31736...ee484b8. Read the comment docs.


libimobiledevice: update all packages

Description of changes
Closes #342738 #342736 #342731 #342728
Closes #342729
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

Make sure the commit messages follow master/pkgs/README.md#commit-conventions

Most of the version strings are too long to fit in the title (or is the limitation a neovim highlighting thing?)

How did commits from other authors get in here? Did I mess up my rebasing?

Make sure the commit messages follow master/pkgs/README.md#commit-conventions

Fixed!

Messed up rebasing I believe, apologies! I'll re-open the PR shortly


doc: add templates

copied from https://github.com/kubernetes-csi/csi-driver-smb
Does this PR introduce a user-facing change?:

none

Does this really help us in this repo?

Ignore the optional pull jobs, they don't work yet.


Pin Python version in setup python workflow step

Since we export PYTHONPATH in cmd.exec, Python version should be the same to be able to run aws_clean.py that uses boto3 library.

Merging with no approvals to avoid failed builds


⚠ Processors has degraded performance

In 13bc321, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 79 ms

Resolved: Processors performance has improved in 34ef3ff.


feat(storage): seperate trivial-move picker

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
as title

Reduce misuse of MinOverlapping Picker
Reduce the complexity from MinOverlappingPicker based on the trivial-move feature.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

https://github.com/risingwavelabs/risingwave/issues/11785

You can update the branch to pass ci test


Prettier - Does override config work?

Summarize the question
Seems like Prettier config doesn't respect overrides. Or I'm doing smth wrong here?
Context

Specifications

Package version: 3.1.3
Node version: 12.20.1
OS name & version: Mac OS 10.14.4

Overrides are always the second argument, the first being reserved for other config options (which Foundry's prettier config currently doesn't have). Try adding an empty object as the first argument:
module.exports = require('@sumup/foundry/prettier')({}, {
	trailingComma: 'none'
});

Overrides are always the second argument, the first being reserved for other config options (which Foundry's prettier config currently doesn't have). Try adding an empty object as the first argument:
module.exports = require('@sumup/foundry/prettier')({}, {
	trailingComma: 'none'
});

thanks a lot! missed this completely :(

thanks a lot! missed this completely :(


Move the DAO creator into javascript

Description (what needs to be done) / Expected Behavior
Move the DAO creator from that script version to something inside of javascript code, because it's not reliable to send the api call and get a response.
Acceptance Criteria
DAO creator works fully as expected, and it glitches less often.
Supporting information (Figma link, notes, etc)
When finished, please add Link to the PR or completed Figma / design asset, as a comment to the ticket.

Related to #741


ssl_version issue while deploying through Docker-Compose up -d

I am deploying flowise by following all the guide using the url https://docs.flowiseai.com/configuration/deployment/aws#setup
Got an error regarding ssl_version while running docker-compose up -d,

This issue is solved when i used the commands
"pip uninstall docker"
"pip install docker==6.1.3"
"pip3 install docker-compose"
Then again I run the command docker-compose up -d
Now i got new error, which is saying Not supported URL scheme http+docker


[BasicsLayoutCodelab][Step 4]: Deprecated feature usage

Hi,
In Basics Layouts in compose codelab step 4, TextFieldDefaults.textFieldColors is being used but is currently deprecated, I think TextFieldDefaults.colors should be used instead, as is being done in the code snippet of the same codelab. I attach the image:

Fixed, thanks @asensiodev


[suggestion] Importing module 'gdown' at Boosting.py file

While experimenting with deepface in Google Colab, I ran into a problem when the function build_gbm() (at deepface > basemodels > Boosting.py) was called. The error message shown was NameError: name 'gdown' is not defined.
When manually adding import gdown at the beginning of the Boosting.py file, the function is called without further problems.

you're right. I fixed in in this next version and it will be released just in few minutes.

upgrade to 0.0.49 :) thank you.


Pacing disappeared - Again

Hi!
The fix you launched in 0.4.6 was great! But my pacing disappeared again. I noticed though that Budget Rows Progress Bars showing pacing works now (it also stopped working when I started the #352 issue).
I can attach some printscreens if needed :)
Thank you very very much!

@signorecello Please post some screen shots. What browser are you using? Pacing is showing up for me so I'm not sure where to start. Make sure your settings didn't change with the upgrade.

Thank you very much :) I was using Opera, but I tried also with Chrome and it was still gone...
Thank you for the fix and for such kind work for all ynabers!

@signorecello Are you still having this issue? If not, please feel free to close this issue :D

It works on version 0.5! Thank you very much :) (sorry for the delay, I was AFK for some days!)

No worries! I'm going to go ahead and close this issue!


zarf-docker-registry image pull timeout when using ipvs mode in kube-proxy

Environment
Device and OS: AWS EC2 instance with Ubuntu 20.04
App version: 0.22.2
Kubernetes distro being used: kURL with kubeadm
Other:
Steps to reproduce

Create a cluster with kURL and kubeadm
Run zarf init

Expected result
Command succeeds and Zarf is initialized in the cluster.
Actual Result
The following message repeats until the init run timesout
Deployment is not ready: zarf/zarf-docker-registry. 0 out of 1 expected pods are ready
Visual Proof (screenshots, videos, text, etc)
output of kubectl -n zarf get events
LAST SEEN   TYPE      REASON                  OBJECT                                       MESSAGE
16m         Normal    Scheduled               pod/injector                                 Successfully assigned zarf/injector to ip-10-0-19-38
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-009" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-012" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-013" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-015" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "stage1" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-022" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-021" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-004" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-020" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 (combined from similar events): MountVolume.SetUp failed for volume "zarf-payload-021" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-007" : failed to sync configmap cache: timed out waiting for the condition
16m         Warning   FailedMount             pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-017" : failed to sync configmap cache: timed out waiting for the condition
16m         Normal    Pulled                  pod/injector                                 Container image "proxy.replicated.com/proxy/knime-hub/registry.hubdev.knime.com/knime-hub/knime-search-sync-service:1.1.0-beta-20220817-144934-000073-d98cd41" already present on machine
16m         Normal    Created                 pod/injector                                 Created container init-injector
16m         Normal    Started                 pod/injector                                 Started container init-injector
16m         Normal    Pulled                  pod/injector                                 Container image "proxy.replicated.com/proxy/knime-hub/registry.hubdev.knime.com/knime-hub/knime-search-sync-service:1.1.0-beta-20220817-144934-000073-d98cd41" already present on machine
16m         Normal    Scheduled               pod/zarf-docker-registry-697f679ffb-4znk8    Successfully assigned zarf/zarf-docker-registry-697f679ffb-4znk8 to ip-10-0-19-38
13m         Normal    Pulling                 pod/zarf-docker-registry-697f679ffb-4znk8    Pulling image "<IP_ADDRESS>:16693/library/registry:2.8.1"
10m         Warning   Failed                  pod/zarf-docker-registry-697f679ffb-4znk8    Failed to pull image "<IP_ADDRESS>:16693/library/registry:2.8.1": rpc error: code = Unknown desc = failed to pull and unpack image "<IP_ADDRESS>:16693/library/registry:2.8.1": failed to resolve reference "<IP_ADDRESS>:16693/library/registry:2.8.1": failed to do request: Head "http://<IP_ADDRESS>:16693/v2/library/registry/manifests/2.8.1": dial tcp <IP_ADDRESS>:16693: i/o timeout
12m         Warning   Failed                  pod/zarf-docker-registry-697f679ffb-4znk8    Error: ErrImagePull
65s         Normal    BackOff                 pod/zarf-docker-registry-697f679ffb-4znk8    Back-off pulling image "<IP_ADDRESS>:16693/library/registry:2.8.1"
12m         Warning   Failed                  pod/zarf-docker-registry-697f679ffb-4znk8    Error: ImagePullBackOff
16m         Normal    SuccessfulCreate        replicaset/zarf-docker-registry-697f679ffb   Created pod: zarf-docker-registry-697f679ffb-4znk8
16m         Normal    WaitForFirstConsumer    persistentvolumeclaim/zarf-docker-registry   waiting for first consumer to be created before binding
16m         Normal    ScalingReplicaSet       deployment/zarf-docker-registry              Scaled up replica set zarf-docker-registry-697f679ffb to 1
16m         Normal    ExternalProvisioning    persistentvolumeclaim/zarf-docker-registry   waiting for a volume to be created, either by external provisioner "openebs.io/local" or manually created by system administrator
16m         Normal    Provisioning            persistentvolumeclaim/zarf-docker-registry   External provisioner is provisioning volume for claim "zarf/zarf-docker-registry"
16m         Normal    ProvisioningSucceeded   persistentvolumeclaim/zarf-docker-registry   Successfully provisioned volume pvc-0a37dfb5-5c35-4911-ad6c-f9ff1549c7fa

output of kubectl -n zarf get all
NAME                                        READY   STATUS             RESTARTS   AGE
pod/injector                                1/1     Running            0          18m
pod/zarf-docker-registry-697f679ffb-4znk8   0/1     ImagePullBackOff   0          18m

NAME                           TYPE       CLUSTER-IP   EXTERNAL-IP   PORT(S)          AGE
service/zarf-docker-registry   NodePort   <IP_ADDRESS>   <none>        5000:31999/TCP   18m
service/zarf-injector          NodePort   <IP_ADDRESS>   <none>        5000:16693/TCP   19m

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/zarf-docker-registry   0/1     1            0           18m

NAME                                              DESIRED   CURRENT   READY   AGE
replicaset.apps/zarf-docker-registry-697f679ffb   1         1         0       18m

Severity/Priority
Blocked on install
Additional Context
Problem is probably that the localhost:<nodeport> cannot be reached with ipvs and the image pull runs into a timeout, see https://github.com/kubernetes/kubernetes/issues/96879
Workaround can be to use iptables for kube-proxy mode but I cannot change this mode in my cluster.

Yeah we dig into this a couple months ago on slack and hadn't found any production clusters running with ipvs at the time. Interestingly kubeadm doesn't do ipvs either by default--it had to be changed by Kurl, which is actually a giant bash script in the end.
This link might show how to switch back to the result iptables mode: https://stackoverflow.com/a/56443345
Since kurl is supposed to work in disconnected envs, it might be worth looking into how they are binding images to their registry, which I haven't personally done yet.
On mobile, but a couple of other links:
https://twitter.com/badcodeonly/status/1557785947311325185?s=46&t=4qMoSgCSI5ZW5kp2TPpiNg
https://kubernetes.slack.com/archives/C03B6BJAUJ3/p1660253727280689?thread_ts=1660052266.064169&channel=C03B6BJAUJ3&message_ts=1660253727.280689

Thanks for the answer.
Based on my search, kurl uses the cluster IP from the registry service for pulling the images (e.g. <IP_ADDRESS>/image:tag). To circumvent the TLS issues, kurl creates a certificate for the registry from the kubernetes CA (/etc/kubernetes/pki/ca.crt) and mounts it to the registry pod and config.
 tls:
    certificate: /etc/pki/registry.crt
    key: /etc/pki/registry.key

In addition, an entry has to added to the containerd config.toml:
[plugins."io.containerd.grpc.v1.cri".registry.configs."<IP_ADDRESS>".tls]
  ca_file = "/etc/kubernetes/pki/ca.crt"

Not sure if the cluster ip can ever change but it looks a bit more volatile then the localhost solution.
No guarantee that I got everything right, since I'm not that knowledgeable in that field.
If there can nothing done here about ipvs, this issue can probably be closed.

ClusterIP is an interesting choice because it would be more volatile. We also were trying to avoid modifying containerd or TLS trust because those require a dangerous RW daemonset to accomplish this. There has been someone discussion around allowing an option to use this pattern in combination with enforced TLS.  Something like:

Modify the hosts file on each node (or point to some DNS resolver) to use some custom DNS, i.e. registery.zarf.internal
Use TLS with the trust being placed either in the containerd config for the system trust root for CAs


Calling azurite from a Linux docker container

I have azurite installed on Windows with the https endpoints enabled.
I have 2 services that are calling azurite: the first is on the local machine the second is inside a linux docker container.
Since the docker service can not call <IP_ADDRESS>, but it has to call 'host.docker.internal' the SSL certificate is not valid. I tried to generate a self-signed certificate with subject name 'host.docker.internal' and the IP <IP_ADDRESS> without success.
I tried also localhost & host.docker.internal: no luck.
With 'http' everything work, but I can not use 'http', I have to use 'https'.

@DrEight
Would you please share what's the detail error you have get?
And if the server and client are on different machine, has the root cert that used to sign the Azurite cert , been added to trust root of the client machine?

@blueww
It seems that azurite works if there is only the dns=<IP_ADDRESS>  specified.
For example if I generate a certificate with: mkcert <IP_ADDRESS> host.docker.internal, it does not even works on the local machine.
I tried also to generate a certificate with: 'mkcert localhost' and it does not work locally. ( I changed the connection string accordingly ) .
For reference to register the certificate as trusted I use:
Windows/Linux :  certutil -addstore -enterprise -f "Root" .\<IP_ADDRESS>+1.pem

@DrEight
For "host.docker.internal" on local machine, you can generated cert with "mkcert host.docker.internal", then start Azurite with parameter "--cert host.docker.internal.pem --key host.docker.internal-key.pem".
(The cert should have "Subject Alternative Name" like "DNS Name=host.docker.internal")
To add the root cert to another machine, please add the root cert of the generated *.pem file to the trust root of the client machine.

@blueww
My problem is that, the certificate does not work on the local machine. I'm searching for a certificate that works in both scenarios

The cert works on my machine with above step.
If the cert still not work, please share the step you set up Azurite, which include command to

mkcert
start Azurite
connection String
host file
Please hide any credentail.

So these are the steps I did :

I created the certificate with the command: mkcert host.docker.internal
I added the certificate to the root store : certutil -addstore -enterprise -f "Root" .\host.docker.internal.pem
I started azurite with the command :  azurite --cert c:\azurite\host.docker.internal.pem --key c:\azurite\host.docker.internal-key.pem --oauth basic --silent
I started the Azure Storage Explorer and I added the certificate host.docker.internal.pem then I restarted the Explorer.
I've tried to connect to Azurite with the connection string: DefaultEndpointsProtocol=https;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=https://<IP_ADDRESS>:10010/devstoreaccount1;QueueEndpoint=https://<IP_ADDRESS>:10001/devstoreaccount1

I received the exception : Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://<IP_ADDRESS>:10010/devstoreaccount1?comp=list&include=metadata failed, reason: connect ECONNREFUSED <IP_ADDRESS>:10010",
"stack": "FetchError: request to https://<IP_ADDRESS>:10010/devstoreaccount1?comp=list&include=metadata failed, reason: connect ECONNREFUSED <IP_ADDRESS>:10010\n    at ClientRequest. (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\node-fetch\lib\index.js:1483:11)\n    at ClientRequest.emit (events.js:315:20)\n    at TLSSocket.socketErrorListener (_http_client.js:469:9)\n    at TLSSocket.emit (events.js:315:20)\n    at emitErrorNT (internal/streams/destroy.js:106:8)\n    at emitErrorCloseNT (internal/streams/destroy.js:74:3)\n    at processTicksAndRejections (internal/process/task_queues.js:80:21)",
"type": "system",
"errno": "ECONNREFUSED",
"code": "ECONNREFUSED"
}
I didn't test the certificate inside docker, but I suppose it would work, but remember that I'm looking for a certificate that works in both scenarios.

@DrEight
The connection string you use will connect to Azurite with "<IP_ADDRESS>" as "BlobEndpoint=https://<IP_ADDRESS>:10000/devstoreaccount1"
But the cert is on DNS name "host.docker.internal"
So the cert DNS name is not aligned with the Uri you use to connect to Azurite. this will make the connection fail.

I've already tried what you suggest. The problem I've seen is that when you map 'host.docker.internal' to <IP_ADDRESS> the docker container inherit the setting from the host machine and it stop to call externally.

@DrEight
Do you map 'host.docker.internal' to <IP_ADDRESS> in host file?
Normally you don't need to change host file manually for that.
When you start azurite with docker, you should already can use the host.docker.internal hostname to connect to your Docker host from inside a Docker container.
See more details in https://docs.docker.com/desktop/windows/networking/

@blueww
the hosts is already mapped to 'my ip' -> host.docker.internal by default. This setting is added by the docker setup.
it is not mapped <IP_ADDRESS> -> host.docker.internal.
I guess that this is done for a good reason and I can not force who will use my container to introduce this change on the host machine.

@DrEight
If you still fail, would you please check:

you can connect Azurite in docker with "http" successfully with "BlobEndpoint=http://host.docker.internal:10000/devstoreaccount1"
the cert is on DNS name "host.docker.internal"
you connect to Azurite on same machine, and use "BlobEndpoint=https://host.docker.internal:10000/devstoreaccount1"
The cert  root (not the cert itself) if in trust root  of the client machine.
And please also share the command you use to start azurite (you should have updated it with my sample).

If still fail, would you please share the failure error message (hide credential if any)
The before failure reason should already fixed if you follow my sample.

@DrEight
I will close the issue as not get any responds from you for a long time.
Feel free to contact us again if need any further support on Azurite.


Update the repo, so it builds with modern Bazel and can be worked on

Update Bazel to 7.1.1 and use Bazelisk to launch it
Update 3rd party Bazel dependencies
Move to GitHub Actions from Travis
Update to Scala 3
Update Scala 3rd party dependencies
Update Maven publishing to be like our Play Routes Compiler CLI
Add Bazel formatting and linting with buildifier

This is a rather broad PR, so I wouldn't be surprised if there's something off.
I also imagine that I won't get the Travis -> GitHub Actions move right on the first try, so there'll probably be some more commits flowing in to this PR while I get that working.

@coreywoodfield you don't show up in the reviewers drop down, but your review would be appreciated.


Inconsistent handling of payload claim data types

When passing in a Time object as the value of the exp claim, if the key of the payload is a string it raises a JWT::InvalidPayload error. When using the symbol as the key, it does not raise the error.
When the exp claim key is a string
exp_payload = { 'exp' => Time.now }
token = JWT.encode exp_payload, 'asdf'
# => JWT::InvalidPayload: exp claim must be an integer

When the exp claim key is a symbol
exp_payload = { exp: Time.now }
token = JWT.encode exp_payload, 'asdf'
# => "eyJhbGciOiJIUzI1NiJ9.eyJleHAiOiIyMDE4LTA5LTA3IDEzOjA3OjU0ICswMTAwIn0.9PxmdZFISuVXQQTDA6bw4vavK428o0R1WvcIZ5np6Lg"

Symbol and string keys in the payload should be handle in a consistent way.

Hi @jamesstonehill,
thanks for the detailed report. Can you specify your ruby-jwt version you're using?

@excpt yeah, sorry I should have included that in the report. I'm using the latest release, 2.1.0.

@excpt yeah this is fixed in the current master.


Use the xacml/saml2 XSD

The SAML service we use (eHerkenning) uses the xacml/saml profile (http://docs.oasis-open.org/xacml/xacml-saml-profile/v2.0/xacml-saml-profile-v2.0.html). In our implementation I replaced the XSDs with the saml/xacml ones, like I did below. However, I can understand if the preference would be to implement this otherwise. By making it configurable for example.
I can make a PR that would make the XSDs configurable, if that is something that would be preferred. I figured I discuss it before putting any effort into it.

Thanks for the quick replies (on all PRs). I'll close this PR for now and will re-make a PR where I create something which can plugin to the existing code.

Thanks for the quick replies (on all PRs). I'll close this PR for now and will re-make a PR where I create something which can plugin to the existing code.


Rolling weapons from Token Action HUD ignores minion group upgrades

Hi,
I'm not sure if this is a problem on the StarWarsFFG system side, or an issue with the Token Action HUD module, so I'm posting this here.
Rolling weapons or combat skills for minion groups works fine and automatically upgrades dice according to the group size - as long as it is done from the character sheet.
Rolling combat skills (e.g. ranged heavy) from the Token Action HUD also works as expected.
Rolling weapons directly from the Token Action HUD however does not upgrade the dice.

You probably want to contact the Token Action HUD developer, as it definitely an issue with that module.

Filed, thanks.
https://github.com/espositos/fvtt-tokenactionhud/issues/186


Why isn't there the GraphQL playground instead of GraphiQL?

Hello @basvandriel!
GraphQL Playground is being deprecated (https://github.com/graphql/graphql-playground/issues/1143) and GraphiQL will soon have all the features of GraphQL Playground and even more.
If you want to still use GraphQL Playground you can override the GraphQL view and use a custom template.

Closing this issue, please let me know if my answer above isn't clear enough and feel free to join our Discord if you need more!
Thanks!


Remove logging component content

Stop logging component full content.
https://jira.dev.bbc.co.uk/browse/CONNPOL-3060

@zygotic99, can I get you to review this one as you raised the ticket?

Looks fine to me :cake:


Add retry logic in exporters

OT SDKs are not responsible for handling retrying, exporters need to have this logic
https://github.com/open-telemetry/opentelemetry-specification/issues/509

Already using storage to retry


Add CommonJS Build

Feature Request: Add CommonJS Build
Describe the problem
The current build of the library only supports ECMAScript (ES) module format, which makes it difficult for developers who use CommonJS in their projects to use this library.
Describe the solution you'd like
I would like to request the addition of a CommonJS build to the library. This will allow developers who use CommonJS to easily use this library in their projects.
Describe alternatives you've considered
One alternative solution would be to manually transpile the library using Babel or a similar tool. However, this can be time-consuming and error-prone. Having a CommonJS build as part of the library will make it easier and more convenient for developers to use it.
Additional context
I'm trying to use this in a serverless function on a platform that only supports CommonJS for the moment. Making this library unfortunately not easily usable at the moment.
Related: https://stackoverflow.com/a/63121798/4820655

Hi again @JaneX8! Agreed, we should support CommonJS.
I tried to when I first started working on this library, but gave up as I couldn't get the two working and I couldn't think of any reason why we'd want to support CommonJS going forward, but yours is a good reason.
I'd welcome a PR for this if you want to tackle this. A few relevant pointers:

We have many JS repos on this organisation as you can tell, so we try to factor out as much as we can to avoid duplication. In this particular case, all of our projects inherit their TS config from: https://github.com/relaycorp/shared-config/blob/master/tsconfig.json
Unlike this repo, most of our JS repos actually output CJS and ESM. Here's an example, which I think could be a good starting point: https://github.com/relaycorp/relaynet-core-js/blob/29fff4ed46350e06f2db85c581b633e2b63cccc1/package.json#L20-L22.
Packages like relaynet-core-js don't actually support ESM because the package.json file lacks the appropriate changes. This is the part I never managed to get to work: For some reason, I always end up with a config that supports either CJS or ESM, but not both. I'm sure I'm doing something wrong, but I don't know what exactly.


Notebooks - actions menu goes off the screen

On the notebooks tab, click on a notebook's vertical ellipsis. The dango menu will go off the screen. This happens for both list view (which is the more egregious offender) and for the grid (if there is an element near the edge of the screen).

Side note:
~1200px is the width at which the signout button goes off screen.

FWIW: 1200px is the width at which we decided the page should wrap rather than start to degrade. We based this on data on the screen widths of Firecloud users.


Glitches on rendering a canvas based off on SVG

Hi,
It is great to see that version 0.5.0 already includes support for SVGs. Thank you! From my initial testing, I noticed two artifacts when trying to use the 0.5.0-alpha1 drop. Please look at the following sample:
http://plnkr.co/edit/mDH2WxYo4k6PIY6zFEGO

Image generated is somewhat blurry

In some cases, I see the text elements in the SVG duplicated (seems to be related to the size of the container)

Thanks!

Duplicate image sounds like bug in DocumentFragment, I will try create a patch.

there is a fix for this bug
Test it
https://github.com/niklasvh/html2canvas/issues/541


⚠ Minecraft has degraded performance

In 398e9b1, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1464 ms

Resolved: Minecraft performance has improved in b2413fc.


Modify the authorized key signature process when the pre-rotation fea…

TLDR: Modify the authorized key signature process when the pre-rotation feature is enabled. Commited keys must be used directly in the next log entry.
Hi everyone,
During IIW 39b, I talked to Stephen Curran and Patrick St-Louis about a potential issue I see with key pre-rotation as it is stated now in the specification. There is a case that an attacker could create a malicious version of the DID Document because the commited updateKey is only enforced AFTER the publication of the log entry. Normally in the key pre-rotation concept, if you commit to nextKeyHashes, you must use it to sign the next log entry.
But the security risk is extremely low right now because you need to fulfill those two conditions:

The Attacker must have compromised the current updateKey (theft or PQC)
The Attacker must known the public key behind the nextKeyHashes (theft or data leak)

Even if the risk is low, i would propose to fix the pre-rotation concept now. better safe than sorry :)
We will need to also adapt the examples and I would argue to jump to version 0.5, as it is a breaking change.

The text you have added is how I was originally thinking about it. Maybe I had made assumptions about the specification that weren't true. The current implementation in trustdidweb-ts requires ANY changes to the DID to be authorized by the currently active updateKeys which is what it seems like this PR is adding for pre-rotation keys.. am I missing something?

If you want a secure linked list of hashes, you will need to sign a new did log entry with the previous updateKey. If you don't "link" the entries with the previous entry, anyone could just create a new did log entry with a new updateKey and sign the entry with that same key.
The difference with pre-rotation keys, is that you commit to a new key with NextKeyHash. When you create a new did log entry, you need to sign with the new commited updateKey to use the full potential of pre-roration keys.
tldr: without pre-roration keys, you need to link with the signature of the previous updateKey. If you use pre-rotation keys, you link the did log entries with the nextKeyHashes and must use the current commited updateKey to generate the signature.

That is very confusing — I didn’t really understand the change based on the PR.   I think I now get the idea (questions, summary below), but I think it will take a bigger update to the specification to make it clear.
I think the core idea of what you are saying is that because of the pre-commitment, there is no need to wait until after “updateKeys” published to use them — we can sign the record with a key from the list in the current record.
I don’t think it really reduces the threat significantly. From what you had above, we now have:

The Attacker must known the public key behind the nextKeyHashes (theft or data leak)
The Attacker must known the public key behind the nextKeyHashes key (theft or PQC)

That is only a slight variation on the risk that is motivating the change.
Is the following an accurate description of your proposal:
No Prerotation:

First entry is signed by a key in the first record “updateKeys” list.
Subsequent entries are signed by a key in the active “updateKeys” list.
An “updateKeys” list is active after the log entry it is in is written, through to when another “updateKeys” record is written (e.g., the new list becomes active).

Preotation:

There must by an “updateKeys” and “nextKeys” list in every record.
All entries are signed by a key in the  “updateKeys” list of the current record.
All of the keys in each “updateKeys” list MUST be in the active “nextKeys” list.
A “nextKeys” list is active after the log entry it is in is written, through to when another “nextKeys” record is written (e.g., the new list becomes active).

Question — In your scheme, is it a requirement that the “updateKeys” and “nextKeys” list are in every record (first bullet above), or can multiple records be signed by keys in the same “updateKeys” list?

Thanks for clarifying my description, yes it is accurate.
For your question, most other technical specification of pre-rotation I have seen forces the concept of updateKeys and nextKeys in each record. It is more secure because it closes the gap where attackers could compromise the current updateKey and sign a new log entry.
The main protection  that people want from pre-rotation keys is that even if the updatekey is compromised, the attacker cannot create a new log entry. And since the nextKeyHash is a hash, it is also more resistant to theorical PQC attacks.
I would recommend to force updateKey and nextKey in each record for security and simplicity.

Decided to adapt the pre-rotation text with the global understanding discussed during the last meeting: https://hackmd.io/k4cIK9vQSlaeg2pdHE51IQ.

I am still struggling to grok this so I have made diagrams to understand the process proposed AFTER this change has been accepted. Please correct me if I'm misunderstanding things. Of note: In the third image you see what I was concerned about  on the call which is the unused key c which is likely not an issue..

I am still struggling to grok this so I have made diagrams to understand the process proposed AFTER this change has been accepted. Please correct me if I'm misunderstanding things. Of note: In the third image you see what I was concerned about on the call which is the unused key c which is likely not an issue..

The issue was that prerotation in version 1 was not working like you illustrated it. It should have worked like that but did not in the end.
To get the current prerotation version 1 you have to take the black arrows of version 0 and replace those in version 1.
My goal is to rewrite the prerotation parts to get to the actual version 1 you draw.
And Version 2 is the case when prerotation is enabled at a later stage and the green arrow is not necessary, as the transition starts after the first nextKeyHashes is set.

@swcurran @brianorwhatever I added some clarifications in the specification. It should reflect pre-rotation version 1 and version 2 when pre-rotation is activated at a later stage from Brian's diagram.

@bj-ms -- I note that you didn't bump the version or add to the log.  Do you want to do that, or hold off?  I think that there should be at least a note in the version about the change.
We have at least two more things that need to go in that will bump the version -- the DID Method name change (#132 ) and updating the Witness proof handling (#135).
We could hold off on merging this until all three are ready and then merge them together such that the version number is preserved.  We also want to capture the v0.4 spec, as was done for the v0.3.
Thoughts?

@bj-ms -- I note that you didn't bump the version or add to the log. Do you want to do that, or hold off? I think that there should be at least a note in the version about the change.
We have at least two more things that need to go in that will bump the version -- the DID Method name change (#132 ) and updating the Witness proof handling (#135).
We could hold off on merging this until all three are ready and then merge them one immediately after the other such that we only change the version number once. We also want to capture the v0.4 spec, as was done for the v0.3.
Thoughts?

Good point, I will add to the log and bump to 0.5 and lets merge the name change and the new witness mechanism in a single version bump to 0.5
Once we have all changes in 0.5, we can prepare for 1.0

@bj-ms -- can you please resolve the conflicts?  Sorry about that, but I think the "landing page" changes that were put in as #137 are helpful.  Thanks!


Custom config?

How can I use pretty-quick with a custom eslint-prettier (.eslintrc) config?
My commits code is different than my development environment... :sweat_smile:

This would require prettier-eslint support, so I'll close this as a duplicate of #22.


Modify setting serveur

Hi,
I can not find the solution to remove the default IP address and put the one I need instead.
I found the 2 places where it was written <IP_ADDRESS>:6060 as well as the name Host name but once the modifications made, I always have the same value to the IP address

Here:
https://github.com/tinode/tindroid/blob/master/app/src/main/res/values/strings.xml#L39

In general, you can always use GiHub search. It works well:
https://github.com/tinode/tindroid/search?q=<IP_ADDRESS>%3A6060&unscoped_q=<IP_ADDRESS>%3A6060

I modified the strings.xml file :
    <string name="settings_host_name">Serveur Test</string>
    <string name="settings_use_tls">Use TLS</string>
    <string name="settings_wire_transport">Wire transport</string>
    <string name="settings_host_name_summary">Change server address</string>
    <string name="settings_use_tls_summary">Use secure connection</string>
    <string name="settings_wire_transport_summary">Select wire transport</string>
    <string name="default_host_name"><IP_ADDRESS>:6060</string>

I have however modified in the file strings.xml and moreover one finds the information in the cache.java:
    // public static String sHost = "api.tinode.co"; // remote host
    public static final String HOST_NAME = "<IP_ADDRESS>:6060"; // local host

sorry, by creating a new virtual smartphone, I have the right address.
So I have a concern for cache. How do I clear the cache of a virtual smartphone?

Just change it.

For information changes on for example replace "Host name" by server are well taken into account but not the IP address
For the IP address to be taken into account, I am forced to delete the virtual smartphone and recreate it.
thank you for your help


[Tests-Only] Write HTTP API tests for user's endpoints

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  7

Clones added
============
- pkg/server/http/svc_test.go  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  7

Clones added
============
- pkg/server/http/svc_test.go  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  7

Clones added
============
- pkg/server/http/svc_test.go  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  7

Clones added
============
- pkg/server/http/svc_test.go  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  10

Clones added
============
- pkg/server/http/svc_test.go  21

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  12

Clones added
============
- pkg/server/http/svc_test.go  24

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test.go  24

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test_groups.go  12
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test_groups.go  11
- pkg/server/http/svc_test.go  31

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test_groups.go  12
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test_groups.go  11
- pkg/server/http/svc_test.go  31

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test_groups.go  12
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test_groups.go  11
- pkg/server/http/svc_test.go  31

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_groups_test.go  12
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_groups_test.go  11
- pkg/server/http/svc_test.go  31

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test.go  23

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  15

Clones added
============
- pkg/server/http/svc_test.go  23

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  16

Clones added
============
- pkg/server/http/svc_test.go  47

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  17

Clones added
============
- pkg/server/http/svc_test.go  47

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  17

Clones added
============
- pkg/server/http/svc_test.go  47

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  17

Clones added
============
- pkg/server/http/svc_test.go  47

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- pkg/server/http/svc_test.go  17

Clones added
============
- pkg/server/http/svc_test.go  47

See the complete overview on Codacy


No Tooltip for journal button on home page, also no tooltip on some toolbar buttons in journal page.

Tooltip is very essential part in Sugarlabs because it is used mostly by childrens. So, It would be easy for them to read tooltip and know what the button will do.

I would like to work on this issue.

Tooltips are not so essential because it can't be displayed on touch screens.
Plus Help button give an explanation of each element of the UI.
BTW, sure you could propose a PR to fix tooltips where there missing.

can i take this issue?

@hetanthakkar1 sure.

Fixed in https://github.com/llaske/sugarizer/pull/995


Wrap text on Blog page

Oops. The text breaks free to the right of the page, expanding it horizontally.

Er, not it doesn't.

It does for me as well. :P

hmmmmmmmmmmmmmmmmmmmmm

Whoops.
Anyway, I fixed it on this commit (how do you reference commits O.O)
https://github.com/OpenSprites/OpenSprites/commit/8676fca570516dd69abc3c0fb2d592170e6c021e

@Rumanti I think you figured it out :P
You just paste the link and GitHub does the rest


Context menu to highlight text and spot it

Fixes #6

Store highlighted text  when SPOT context menu is selected -->in local storage
Retrieve strored highlighted text and query it to find top 3 related songs on spotify
Notify using chrome notifications to indicate that search results are ready
reset local storagevalue  to  null

Hey @saiflakhani, let me know what you think!

@saiflakhani I think I'm gonna go ahead and merge it, for now! Let me know your thoughts regardless hehe

Hey! This is great!
Sorry I've been really busy this past week.
The notification doesn't seem to pop up for me though. Is there something I'm missing?

@saiflakhani haha no problem! Are you able to view the notifications? If not, I believe there is some configuration/permissions required within your browser settings.
And, yes!! Will push the code for the add functionality in a bit. Post which, all that will remain is some thorough testing :P


How to render object data instead of index data?

As you can read in the title, this is not a bug, but i need a representation of my data without launching update_index.
Is it possible?
If so (i hope that), The documentation is incomplete

class LocationSerializer(HaystackSerializer):

class Meta:
    # The `index_classes` attribute is a list of which search indexes
    # we want to include in the search.
    index_classes = [LocationIndex]

    # The `fields` contains all the fields we want to include.
    # NOTE: Make sure you don't confuse these with model attributes. These
    # fields belong to the search index!
    fields = [
        "text", "address", "city", "zip_code", "autocomplete"
    ]

Hi,
You can use the HaystackSerializerMixin which will render the instance's database object. Note that this will perform a query to the database.

Thank you @rhblind,
Unfortunately i see this error:

'BlogEntry' object has no attribute 'searchindex'

where BlogEntry is the model associated with one of my search_indexes
`class BlogAndFaqEntryHaystackSerializer(HaystackSerializerMixin,
HaystackSerializer):
class Meta:
    # The `index_classes` attribute is a list of which search indexes
    # we want to include in the search.
    index_classes = [BlogEntry,FaqEntry]

    # The `fields` contains all the fields we want to include.
    # NOTE: Make sure you don't confuse these with model attributes. These
    # fields belong to the search index!
    ##### Inheriting from HaystackSerializerMixin, I have to insert model attributes?? Is it right? ####
    fields = [
        #"text",
        "title", "city",
        "publication_start", "location",
    ]`

Inheriting from HaystackSerializerMixin, I have to insert model attributes?? Is it right?
Any help is appreciated

Hi, sorry for delayed response!
No, the fields class attribute should contain fields from your HaystackIndex class. They are used in order to construct the query.
The drf-haystack library is written to serialize haystack indices, so if you just want to render your database object, you probably should just use a normal django rest framework view.
The HaystackSerializerMixin class mentioned above just replaces the obj attribute with instance.object in the to_representation() method. It's really just a hack/convenience in order to do filtering using Haystack and serialize the database representation of that object. It will cause you to hit the database.
Once you have your instance.object object, you are free to return whatever data you wish from this method.
If this is not what you're asking for, then I'm afraid I don't really understand what your're asking for?


adds check_suite trigger, pins go version

Pre-submission checklist:
Updates the verify GitHub Action on this repo adding a check_suite trigger and also pins the version of go used to run the check to ^1.19.5 when running the go program that checks the correctness of the landscape.yml file.
Post merge this we should then see a verfy step in PRs that checks the landscape.yml file
cc @jeefy

So cool that the check ran, less so the error at https://github.com/cncf/landscape/actions/runs/4046710815/jobs/6959841605#step:3:12
Also DCO!


[query] return 0 if there was at least one valid number

What this PR does / why we need it:
PromQL compatibility fix.
When running instant queries PromQL returns "0" in place of NaN if there was at least one valid number in a range. Otherwise, it returns "NaN". That is the fix for M3 query to behave in the same way.
Special notes for your reviewer:
I'll change base branch to master when depending PR will be merged.
Does this PR introduce a user-facing and/or backwards incompatible change?:
NONE

Does this PR require updating code package or user-facing documentation?:
NONE

I think this will clash with https://github.com/m3db/m3/pull/2390. Maybe there is a way to solve this at a deeper layer than the rendering of the output?


[Compute] Fix #26185: az sig update: Fix issues that is_soft_delete_enabled may not exist

Related command

az sig update
Description

Issue - Close: #26185
Testing Guide

History Notes

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

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

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

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Compute

LGTM

approved!


add new variable VM_VMSERVICESCRAPEDEFAULT_ENFORCEENDPOINTSLICES

to use endpointslices instead of endpoints as discovery role for VMServiceScrape when generate scrape config for VMAgent.
address https://github.com/VictoriaMetrics/operator/issues/1162

Thanks for helping with this, By when we can expect this change released? :)

Thanks for helping with this, By when we can expect this change released? :)

I'd say roughly early next month, but that depends on @f41gh7

Thanks for helping with this, By when we can expect this change released? :)

I'd say roughly early next month, but that depends on @f41gh7

It would be great if you could help in releasing this faster. @Haleygo @f41gh7

Issue was fixed at v0.50.0 release


Pregenerate all tables

At the moment we generate Muls, Coefs and LS_tbl using the next part of code:
void grasshoper_encrypt(Block *block, Key *key)
{
  //TODO: remove it with autogenerating for tables
  static int generate = 1;
  if (generate)
  {
    generate_mul_tbl ();
    generate_coef_tbl ();
    generate_LS_tbl ();
    generate = 0;
  }

As I understand all these 3 tables may be pregenerate before the whole program.  We should do it and save it instead of S, invS and lin tables (see config.h).
@Krym4s @kolobabka, am I right or these tables can't be pregenerated as I thought?

Maybe @pavel-collab...

@pavel-collab is volunteer.

I need to check source code this week before solve the problem. Will do it this week. As I understood only possible way to generate random bytes array during the build step is to use a META programming. One possible option, that I have found for now is https://clck.ru/366Vk9 But it need to use boost lib.

Here is no any reason to use meta programming (also we use C language)
This issue is not about random array generating (moreover this problem can't be solved using meta programming at all). Here we have the problem that we generate the SAME tables every time we run the program (see functions generate_mul_tbl (), generate_coef_tbl (), generate_LS_tbl ())

@Exactlywb could you send me a link to some documentation to the source. I need to clearly understand the idea of this thee existing matrixes to make generation script and also for article. If you have no one, I will need more explanation.

Lack of documentation is the feature of our project


Update primitive-types crate

- ancient rand dependency

Actually, it seems that it gives like ~20% performance hit during block import
Probably due to https://github.com/paritytech/parity-common/pull/317
And primitive-types/libc feature is explicitly used in sp-core
@ordian ^^^

with primitive-types/libc
import block/Wasm       time:   [4.5876 s 4.6357 s 4.7006 s]
import block/Native     time:   [2.5677 s 2.6154 s 2.6846 s]

without primitive-types/libc:
import block/Wasm       time:   [4.7306 s 4.8279 s 4.9466 s]
                        change: [+3.1825% +5.5383% +7.6266%] (p = 0.00 < 0.05)
                        Performance has regressed.

import block/Native     time:   [2.7783 s 2.8249 s 2.8624 s]
                        change: [+2.5561% +6.1032% +9.7396%] (p = 0.00 < 0.05)
                        Performance has regressed.

Actually, it seems that it gives like ~5% performance hit during block import
Probably due to paritytech/parity-common#317
And primitive-types/libc feature is explicitly used in sp-core
@ordian ^^^

I opened https://github.com/rust-lang/rust/issues/69024.
We haven't published a new version of fixed-hash and if you think the libc feature removal should be reverted, we still can do it.

We haven't published a new version of fixed-hash and if you think the libc feature removal should be reverted, we still can do it.

Yeah, the fact that it is not published probably unblocks this pr.
Performance issues still should be addressed though - I've benched against just latest parity-common, but we'll figure out later.


feat: analytics

Closes #1063.
Requires merging https://github.com/ipfs-shipyard/ipfs-webui/pull/1136.

This adds Analytics to IPFS Desktop using our Countly setup. This PR, in pair with the one on IPFS Web UI repository, make a seamless integration between both Countly setups: we share the device id and the consents so we know on both sides what we can and can't send.
For this to work, I just created some wrappers around the logging functions to allow to send an event with it. If it has an event (withAnalytics), we log the event to Countly.
Also, created a logger.start function that allows us to measure, log and track time of certain actions, such as starting and stopping the daemon.
Please ignore CI failures...

@olizilla the requested changes were made:

We now track sessions on Web UI as we did.
We now provide the list of the events we track to Web UI so they can be shown to the user.
And I also moved the feature enabling/disabling tracking to Web UI (when the user clicks to toggle options).

@olizilla after we talked, I tried moving all the logic to Web UI side to keep the countly id and such the same so there wouldn't be any problems. Although, that way, since the Web UI sometimes reloads (when the daemon stops and starts) or due to other reasons (user forced reload, we updated the files list), we won't be able to capture all events. Some of them are quite important such as daemon's starting time.
Although, I found out we could actually merge the old ID data with the new: https://github.com/ipfs-shipyard/ipfs-webui/pull/1136/commits/d20980f495e64ac187f5ca5bb629c3fd86876606.
Waiting for a review now :)


[Bug]: Error coming from `npm install

Please confirm that you have:

[x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
Hi everyone,
Please, could you help me?
I have an error after press enter in TypeScrip step during Shopify App setup using remix:
Your project name?
✔  ar-app-shop-eco-v5
?  Get started building your app:
✔  Start with Remix (recommended)
?  For your Remix template, which language do you want?
✔  TypeScript
Useful information:
1- I updated Node to 18.16.0
2- Node is working fine with my other React projects.
Thank you very much!

Actual behavior
With problem during setup Shopify App with CLI and using remix
Verbose output
...
Reproduction steps

Operating System
Mac OS Monterey
Shopify CLI version (check your project's package.json if you're not sure)
3.66.1
Shell
No response
Node version (run node -v if you're not sure)
v18.16.0
What language and version are you using in your application?
Node

@etienne-ditchlabs is correct, you need to have at least version 18.20.
I'll close this issue since the solution is clear and is not a CLI issue :)


Videos in channel search aren't marked as watched

When I searching a channel's videos, YouTube Center doesn't display the "Watched" overlay on the search results. It works fine on the Videos page of the channel.
I'm using Google Chrome 44.0.2403.125 m and YouTube Center Development Build version 531.

but why is there an option to enable or disable watched videos through the script, when it is already enabled from youtube itself

For me the ability to manually mark a video as watched is gone.
The "three dots" you hover over to mark a video as 'watched' are visible at first... up until you hover over them. At that point they disappear and you cannot mark the video as 'watched'. Move the cursor away from them - they reappear.


Will it be available on Android?

Just curious to know, will it be available on Android too? If that happens, that would be really helpful for many of us :)

Hi, thanks for the question. Please see https://github.com/lrettig/react-native-stripe/issues/8. I have no plans for Android at this time but would welcome a PR!


Support all GNU's human_readable arguments

Hello!
Is there any plan to support from_block_size and to_block_size as they appear in the GNU code of human-readable?
https://github.com/coreutils/gnulib/blob/master/lib/human.c#L153

@matan1008 thanks for your issue.
There was not a plan, but I don't see a reason not to support. Are you interested in sending a PR? Or maybe detailing the requirements as test cases.


Android RippleActivator causing Detached DOM nodes

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When using the android version of serve, clicking through an app with click events leaves Detached DOM Nodes for all of the elements that RippleActivator should be listening to.  Just navigating between pages is enough to recreate the issue usually, but clicking on some of these elements creates it.

Can confirm with our app that running ?ionicplatform=ios removed the detached nodes.  It's possible *ngIf exacerbates the problem.  These nodes are building up in our app that is a kiosk and making it impossible for us to deploy our ionic 2 app.  We tried:
IonicModule.forRoot(AppComponent, {
			swipeBackEnabled: false,
			pageTransition: projectConfig.pageTransition,
			platforms: {
				android: {
					activator: 'highlight'
				}
			}
		}

But that did not seem to change RippleActivator from attaching events.  At this point, finding a way to disable the activator would work in the interim as the leak is fixed.
Expected behavior:
Navigating between pages should correctly remove listeners from elements to avoid detached DOM nodes.

Thanks for using Ionic, we will look into this.

Thanks @jgw96.  Due to timing for launching our app, is there a known way that should disable RippleActivator from attaching listeners?  We weren't able to get that to happen using activator: 'highlight' or 'none'.  In the meantime, we've resorted to removing the functionality from the ionic src before building, which obviously isn't a great long term strategy!

There is a commit pending for approval that fixes a lot of memory leaks, including this one!