[BUG] Runtime Error in AppContent Component: useUser Hook Fails with AWS Amplify Authenticator

Describe the bug
When running the application, an error occurs within the <AppContent> component related to AWS Amplify's authentication. Specifically, the error seems to originate from the usage of the useUser hook, causing the component tree to fail and triggering the ErrorBoundary. This prevents the application from rendering correctly and interrupts the user experience.
Error message:
The above error occurred in the <AppContent> component:

AppContent@http://localhost:5173/src/components/AppContent.tsx:38:20
AuthenticatorInternal@http://localhost:5173/node_modules/.vite/deps/@aws-amplify_ui-react.js?v=53795d0e:38959:31
AuthenticatorProvider@http://localhost:5173/node_modules/.vite/deps/@aws-amplify_ui-react.js?v=53795d0e:16899:31
Authenticator@http://localhost:5173/node_modules/.vite/deps/@aws-amplify_ui-react.js?v=53795d0e:38993:18
AuthAmplify@http://localhost:5173/src/components/AuthAmplify.tsx:23:21
AuthenticatorProvider@http://localhost:5173/node_modules/.vite/deps/@aws-amplify_ui-react.js?v=53795d0e:16899:31
ErrorBoundary@http://localhost:5173/node_modules/.vite/deps/react-error-boundary.js?v=53795d0e:18:5
App@http://localhost:5173/src/App.tsx:39:23
RenderedRoute@http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=51795d0e:4037:7
RenderErrorBoundary@http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=51795d0e:3994:5
DataRoutes@http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=51795d0e:5156:7
Router@http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=51795d0e:4423:7
RouterProvider@http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=51795d0e:4971:7

React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary.

To Reproduce

Ensure project is up to date with the bec3aee4e63e5137a17ea5ed97b7ac5d38e4d3b1 PR.
Clear node_modules
Run npm i in /frontend
Run npm run dev
When started the application should show the error page

Screenshots

Additional context

Potential Causes Investigated:

Context Misconfiguration: Ensured that all necessary context providers, such as AuthProvider, are correctly wrapping the component tree.
Hook Implementation: Reviewed the useUser hook to confirm it properly consumes context without missing providers.
AWS Amplify Configuration: Verified that Amplify is correctly initialized with the appropriate configuration files.

Steps already taken:

Verified that AWS Amplify is correctly configured and initialized in the project.
Ensured that all context providers required by useUser are properly set up in the component hierarchy.
Updated all dependencies to their latest versions to rule out compatibility issues.
Attempted to isolate the issue by simplifying the AppContent component, but the error persists.

Tried npm ci && npm run dev with HEAD commit, but not reproduced.

Here's another section of the error:

It's worth noting that this happens after I have authenticated myself.
Things I've tried:

Generated another package-lock.json
Cleared browser cookies
Tried multiple browsers just to make sure

I am confused since my fork is a 1:1 with this project with the exception of the additions of https://github.com/aws-samples/bedrock-claude-chat/commit/bec3aee4e63e5137a17ea5ed97b7ac5d38e4d3b1. I think it's also worth noting that this is happening in local development, I have not pushed it to the cloudformation stack. However, before I updated to https://github.com/aws-samples/bedrock-claude-chat/commit/bec3aee4e63e5137a17ea5ed97b7ac5d38e4d3b1 I can start the frontend with no problems at all.
Any suggestions are welcome.
Thank you in advance.

Still it's not been reproduced. I'll keep this issue open.

@axelpina Could you please show the API response obtained by useConversationApi().getConversations() ?
https://github.com/aws-samples/bedrock-claude-chat/blob/bec3aee4e63e5137a17ea5ed97b7ac5d38e4d3b1/frontend/src/hooks/useConversationApi.ts#L23-L27

Response:
import { useSWRConfig } from "/node_modules/.vite/deps/swr.js?v=06194052";
import useHttp from "/src/hooks/useHttp.ts";
const useConversationApi = () => {
  const http = useHttp();
  const { mutate } = useSWRConfig();
  const updateTitle = (conversationId, title) => {
    return http.patch(`conversation/${conversationId}/title`, {
      newTitle: title
    });
  };
  return {
    getConversations: () => {
      return http.get("conversations", {
        keepPreviousData: true
      });
    },
    getConversation: (conversationId) => {
      return http.get(
        !conversationId ? null : `conversation/${conversationId}`,
        {
          keepPreviousData: true
        }
      );
    },
    postMessage: (input) => {
      return http.post("conversation", {
        ...input
      });
    },
    getRelatedDocuments: (input) => {
      return http.post(
        "conversation/related-documents",
        {
          ...input
        }
      );
    },
    deleteConversation: (conversationId) => {
      return http.delete(`conversation/${conversationId}`);
    },
    clearConversations: () => {
      return http.delete("conversations");
    },
    updateTitle,
    updateTitleWithGeneratedTitle: async (conversationId) => {
      const res = await http.getOnce(`conversation/${conversationId}/proposed-title`);
      return updateTitle(conversationId, res.data.title);
    },
    mutateConversations: (conversations, options) => {
      return mutate("conversations", conversations, options);
    }
  };
};
export default useConversationApi;

//# sourceMappingURL=data:application/json;base64,[encoded data, 4612 characters]

@axelpina Sorry, what I wanted to see was the backend response to a GET request to the following API:
GET https://xxxxxxxx.execute-api.ap-northeast-1.amazonaws.com/conversations

Here's a response from the GET in https://xxxxxxxx.execute-api.ap-northeast-1.amazonaws.com/conversations:

@statefb I apologize for diverting this ticket, but I wanted to avoid opening a new one as my question is specific to starting the backend for development and testing. After exporting the required environment variables, the backend starts without issue. However, when I start the frontend, I am unable to access Claude. Additionally I am unable to visualize my bots as well.
# export TABLE_NAME=BedrockChatStack-DatabaseConversationTablexxxxxx
# export ACCOUNT=xxxxx
# export REGION=us-east-1
# export BEDROCK_REGION=us-east-1
# export DOCUMENT_BUCKET=bedrockchatstack-documentbucketxxxxx
# export LARGE_MESSAGE_BUCKET=bedrockchatstack-largemessagebucketxxxxx
# export USER_POOL_ID=us-east-1_xxxxx
# export CLIENT_ID=xxxxxxxxxxxxxxxxxxxxxxx

Need clarification on using the backend for local development.
Thank you in advance.


It would be nice to include a keymaps dictionary

Something like this would be extremely useful to learn the key combinations.
https://github.com/liuchengxu/vim-which-key#configuration

Great idea. Please create a PR 🙏


ReGaHss: Error: SetVar(): SetValue() failed: m_val.ivt = 16

Hello Jens,
Since an upgrade to RaspberryMatic <IP_ADDRESS>71022 a script to detect open windows doesn't work any more.  This script was working fine for more than a year so far. In the log file the following error message is shown each time when the script is executed:
Oct 31 17:15:00 homematic-raspi local0.err ReGaHss: Error: SetVar(): SetValue() failed: m_val.ivt = 16 pszVar =9369$0%10511$0%10677$0%10621$0%11108$0%12351$0%16381$0%17796$0%17851$0%13143$0 [iseDOMdpVar.h:62]
Let me know if you need further data for debugging this.
Thanks a lot in advance.
Best regards,
Ewald

Please provide the script

Here we go:
detect_open_windows.txt
Thanks for your swift action!

Can you give some details in which line of your script the error output occurs?

Not yet. Since there is no single step debugging mode (I am aware of), it will take time to narrow this down. Let me try ..

Narrowing down succeeded by deleting parts of the script until the error message disappeared:
The error is generated by line 123:
OpenWindowArr.Variable(newString);
newString is this string:
9369$0%10511$0%10677$0%10621$0%11108$0%12351$0%16381$0%17796$0%17851$0%13143$0
Hope this helps.
BR
Ewald

And what kind of string should that be? what does that mean actually?

The string is encoding for each window the time when it has been opened. The delimiter between the windows is a ‚%´. The script is not originated by me, but just adapted to my needs. Interesting is that the log error message is containing the value of newString. The script was working for a CCU1 and for Raspberrymatic until the last release.

Usually the script is invoked every 5 minutes if there is any open window.

@FUEL4EP Can you please check that your "OpenWindowArr" Systemvariable is correctly set to "Zeichenkette" and not to some other type. Perhaps also try to recreate this system variable.

Hello Jens,
Indeed the type of the system variable "OpenWindowArr" was wrong. Setting it to 'Zeichenkette' fixed my problem. Thanks for your great 'razor-sharp' analysis and help.
We can close this issue.
Best regards,
Ewald


[BUG] Generate Rolltable with Filters

Module Version: v2.0.31
I've been trying to get the Spell Scroll generation with a random spell but can't seem to get it to work.
I then tried to create a rolltable with filters but got the error saying no compendium was found.
It does work when I generate a rolltable without filters so the compendium is working properly
My compendium:

After Right clicking I get this menu and the "BRT Generate rolltable." works perfectly fine:

The last option to generate with filters gives me this error:

I also have issues with the Spell Scroll generation but I don't get error messages with that one, it just doesn't do anything

Should  be finally fixed on 2.0.32

This remains as an issue.

Strange i was sure was solved... i will check out with that compendium


[bug] Shell variable expansion doesn't work in task commands

Describe the bug
Shell variable expansion is broken in task command strings

Steps to reproduce

Create a new project with this moon.yml:

tasks:
  build:
    command: echo $SHELL
    options:
      shell: true

moon r build
See literally $SHELL printed, not the value of the environment variable

Can work around by doing this
tasks:
  build:
-   command: echo $USER
+   command: sh -c "echo $USER"
    options:
      shell: true

Expected behavior
As a user I want to be able to just copypaste my shell scripts into YAML multiline string and expect it to work

Screenshots

Environment
moon 1.8.1, tried on macOS 12.6 and debian 12

  System:
    OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (2) x64 Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz
    Memory: 1.03 GB / 3.83 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    npm: 8.19.4 - /usr/local/bin/npm
  Managers:
    Apt: 2.6.1 - /usr/bin/apt
    Cargo: 1.70.0 - ~/.cargo/bin/cargo
  Utilities:
    Git: 2.39.2 - /usr/bin/git
  Languages:
    Bash: 5.2.15 - /usr/bin/bash
    Perl: 5.36.0 - /usr/bin/perl
    Rust: 1.70.0 - /root/.cargo/bin/rustc

Additional context
There is a similar issue about nested execution https://github.com/moonrepo/moon/issues/889, but it's not even filed as a bug

@ilyasotkov shell: true wraps the command with bash -c so this is weird. Does --log trace reveal what command is actually running?

@milesj I guess it's an issue with single quotes (instead of double) wrapped around the command, which makes it a string literal and disables shell expansions.
[DEBUG 02:28:03] moon_process::command_inspector  Running command /bin/bash -c 'sh -c '\''echo $SHELL'\'''  env_vars={"MOON_PROJECT_SOURCE": "apps/my-app", "MOON_CACHE_DIR": "/workspace/.moon/cache", "MOON_TARGET": "my-app:build", "MOON_PROJECT_RUNFILE": "/workspace/.moon/cache/states/my-app/runfile.json", "MOON_PROJECT_ID": "my-app", "MOON_WORKSPACE_ROOT": "/workspace", "MOON_PROJECT_ROOT": "/workspace/apps/my-app", "MOON_TOOLCHAIN_DIR": "/root/.proto", "MOON_WORKING_DIR": "/workspace"} working_dir=/workspace/apps/my-app
/bin/bash

Yeah that's weird. Let me dig into further.


Binary instruction translation error

My code is as follows:

discovered by chance，There is a problem with windbg executing this statement (xchg r8d, eax)。
so,I compiled this code and tested it using windbg and ttd。
The windbg compilation instruction is wrong but executed correctly

But unfortunately, ttd is simulated through instructions, so the operation error

I hope it can be repaired successfully
This is a compressed package of asm, exe, pdb, run files
Debug.zip

Thanks for reporting this, I wasn't watching for issues reported here. We filed a bug for this in March to the Visual Studio team: https://developercommunity.visualstudio.com/t/MSDIS-is-incorrectly-decoding-some-xchg/10573512?port=1025&fsid=77f913aa-873a-4fa4-ad64-eea268d1ca7f&ref=native&refTime=1727618403552&refUserId=4ea9033d-505a-48ee-844e-5353eccf40ef
Maybe you could upvote this?


Standardise IERS routines API and conventions

Increase the consistency between the different conventions and function names. The following conventions should be implemented:

[ ] IERS 1996
[ ] IERS 2003
[ ] IERS 2010

For each convention, the following quantities should be computable:

Earth Rotation Angle
Frame Bias
Mean obliquity of the ecliptic
Precession angles (for both 3-angles and 4-angles rotations)
Precession matrix
Nutation in longitude and obliquity
Nutation matrix
Greenwich Mean Sidereal Time (GMST)
Greenwich Apparent Sidereal Time (GAST)
ITRF to GCRF rotation matrix

Moved to IERSConventions.jl.


[Feature Request] installation by npm/go

Why are they gone?
Has there a specific issue?

@jjangga0214 with the rewrite in dart using pub to install is just much easier. The npm install was made to make a go binary easier to install


Add type alias for accessing Versioned enum

I believe it would be desirable to provide an alias such as:
pub type AnyVersion<T> = <T as obake::Versioned>::Versioned;

reasoning:

less eye-sore
"reads" better, making it easier for new users to understand
removes redundancy of typing out "Versioned" twice, which honestly took me all of 5 minutes to get sick of :P

Willing to PR such a change but didn't want to so without first seeing if it's desirable. Name is just the first thing I thought of and ultimately not important if you have one in mind.

Absolutely great idea, just added with my most recent commit. Will merge your PR and then publish a new version.


add immediateFailedFuture utility method

Codecov Report

Merging #198 into master will not impact coverage by -0.02%.

@@             Coverage Diff              @@
##             master     #198      +/-   ##
============================================
- Coverage     70.04%   70.02%   -0.02%
  Complexity      460      460
============================================
  Files            64       65       +1
  Lines          2420     2422       +2
  Branches        260      260
============================================
+ Hits           1695     1696       +1
- Misses          631      633       +2
+ Partials         94       93       -1

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/com/google/api/gax/grpc/RpcFutures.java
0% <ø> (ø)
0 <ø> (?)

...e/api/gax/bundling/ThresholdBundlingForwarder.java
87.5% <ø> (+3.12%)
4% <ø> (ø)
:x:

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 a0f5b1b...c22e2d5. Read the comment docs.

LGTM after the doc issues are fixed


show child assets in the asset page

Description
This PR introduces a new section to the asset page to list all the child assets of a given asset.
Look & Feel

[X] I agree to contribute to the project under Apache 2 License.
[X] To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

I see you circumvented the internal API as it doesn't support this. I remember you talking about that. Maybe add a comment on the why. It's a good thing that the internal API gets called before for the parent asset, which will help with auth protection. This does matter.

Finally, I adapted the internal API to return the children (at least, the those of the first level).


Worn player/mob skulls rendered in first person view, blocking vision

Player skulls and mob skulls are shown being worn in first person, view completely blocked and can't see past the head when worn.
Mod version: 2.1.2-mc1.18.2 (Forge)
Ender dragon head being worn:

Skeleton head being worn:

Player skull being worn:

You have a conflicting other mod installed that changes the player model or armor rendering.


Should dependency injection be used here?

I implemented a play 2.5 app with phantom a few months ago with very similar approach of this project. When going to production, I realized that I have to maintain a separate configuration file to specify the clusters and keyspaces. So I created a service with a trait and a Singleton class with play Configuration injection, and then initialize the contactpoint with settings from play configuration files. Then controllers can inject the service when needed. However, the service code is kind of ugly since extends AppDatabase(Defaults.Connector) cannot be done in a class. Is there an elegant way of doing this?

Added this in https://github.com/outworkers/phantom-activator-template/pull/9


[DOCs] Update kNN classification and unsupervised docs with metrics

Description

Info about new supported distances has been added

@Mergifyio backport rls/2021.6-rls


question using components to wrap html fields

Hi All,
First of all I am quite new to ReactJS so don't blame me for it ;-)
I am wrapping common fields into separate component classes for re-using them throughout my SPA.
For example i created a separate component for a dropdown field which loads data from a remote server.
Now this works fine, but using the react-stepzilla library the validation does not work.
<SubjectField required defaultValue={this.state.subject} **ref="subject"** className="form-control" />
If i move the actual dom code from the SubjectField (wrapper) into the 'root' file it works fine. It seems that the _grabUserInput function cannot get hold of the 'ref' property in the custom component class.
Can you please help guiding me in the right direction ?
Thank you so much in advance!
Thijs
PS. btw did I mention this is a great library? ;-)

found it.


Sass precompiler does not work with abide form error class

Currently when generating the css abide will not generate correct css
"[data-abide]" .error small.error, "[data-abide]" .error span.error, "[data-abide]" span.error, "[data-abide]" small.error {
the correct css should look like
[data-abide] .error small.error, [data-abide] .error span.error, [data-abide] span.error, [data-abide] small.error {

We tested this in Libsass 3.3.0 and Ruby Sass 3.4.20 yesterday, and both compilers rendered [data-abide] without quotes.
I believe the issue was related to a bug in Libsass that's been fixed in more recent versions. Since Foundation 5.5, our recommendation has been to always use the latest versions of Libsass or Ruby Sass.


Fix issue 1160 to support pc.link work well without setting href

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

New Feature Submission:

[x] Does your submission pass the tests?
[x] Have you linted your code locally prior to submission?

Changes To Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

This PR is to solve this issue

https://github.com/pynecone-io/pynecone/issues/1160

After team discussion, we decided to bring the following PR (#1173) as a fix for that the issue #1160.


NOT POINTING ON CORRECT WINNING ON INDEX

Hello, good day. Thank you so much for making this cool project.
I do have encounter an issue when it is built in PRODUCTION or when it is DEPLOYED. In my local machine it is working fine, no issues, but when it is deployed it is not pointing on the correct wining index. When I checked the console log, no errors found also.
I tried to change the view from desktop into a mobile view, it fixed the issue, and when I switched it back to desktop view, it also fixed the issue but it should not be like this, right? I don't if this is only a css issue or what.
Please see video

Hello. Please check the prizeIndex prop. Make sure it sets a correct prize item index.

Yes I have set it correctly. I did add some logs also just to check if the prizeIndex was right, and it is right.
I tried this scenario, I have set the prizeIndex to 5 for both local and production, and I noticed that they have different inline style on the   tag, local is left:503.5, production is 1127.5.

Got you. Can I take a look on your production site? You may just send a link to it. I need it because first I gotta reproduce this issue to say anything about it.On 20 Feb 2023, at 9:07 p.m., Jay Andrade @.***> wrote:
Yes I have set it correctly. I did add some logs also just to check if the prizeIndex was right, and it is right.
I tried this scenario, I have set the prizeIndex to 5 for both local and production, and I noticed that they have different inline style on the   tag, local is left:503.5, production is 1127.5.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

And also it’d be amazing if you provide your component where described the roulette logic. This is the most important part.On 20 Feb 2023, at 9:07 p.m., Jay Andrade @.***> wrote:
Yes I have set it correctly. I did add some logs also just to check if the prizeIndex was right, and it is right.
I tried this scenario, I have set the prizeIndex to 5 for both local and production, and I noticed that they have different inline style on the   tag, local is left:503.5, production is 1127.5.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

I think I know now why it has a different inline style left prizeindex offset. I am using tab panels, so upon loading the page, it (RoulettePro) will be rendered, but it is hidden since it is not the default, so the width is different. I have replicated it now on my local machine. I selected another default tab panel and then reloaded the page, and when I selected that panel with the Roulette Pro and clicked the spin button, it had a different width, not the same as the default tab panel with the Roulette Pro in it.
So what I am going to do now is make it re-render every time I select this tab with Roulette Pro.

This issue is now resolved.
For those developers who will be facing this kind of issue when implementing it on a tab panels, you can fix it by applying the lazy loading principle. Just load the component when it is really needed.

Good job 👍You’re a master. Feel free to open a new issue if you have any questions. Have a good one.On 21 Feb 2023, at 2:58 a.m., Jay Andrade @.***> wrote:
Closed #24 as completed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Me and a friend had same issue and its still in the open issues(fixed it so he should close it later) for us the roulete was off by 200-300px when it first rendered. then if we moved the tab width or height ever so slightly it would re-render and fix it self and work perfectly after that. For us the problem was in the css. I still dont know what triggered it but we just rolled back and it works now


[video_player] no display frames of video when stream video url with no sound channel on iOS device

Hi, I am having an issue. When I am streaming a video with no sound channel, but player no display frames of video on iOS.
Please help me, how to fix it.
Thank all

Hi @TahaTesser,
Thank you for supporting me immediately.
I have upgraded to the newest version of Flutter 2.5.2 and using the newest version of the video player package. I try again with video NO SOUND and found out that, the video player was still in a loading state until I disconnect my device's wifi network and connect again.
This is recorded video screen
https://youtu.be/0LRuvA2O6cc
Flutter doctor -v
✓] Flutter (Channel stable, 2.5.2, on macOS 11.5.2 20G95 darwin-x64, locale en-US)
• Flutter version 2.5.2 at /Users/balua/Documents/flutter_stable
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 3595343e20 (7 days ago), 2021-09-30 12:58:18 -0700
• Engine revision 6ac856380f
• Dart version 2.14.3
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/balua/Library/Android/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.5.1, Build version 12E507
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 46.0.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] VS Code (version 1.60.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.27.0
[✓] Connected device (2 available)
• Du’s iPhone (mobile) • 08736d9b61bdf10837aa9ad957a22fdab4083430 • ios            • iOS 13.4.1 17E262
• Chrome (web)         • chrome                                   • web-javascript • Google Chrome 94.0.4606.71
! Error: Ha Hai is not connected. Xcode will continue when Ha Hai is connected. (code -13)
! Doctor found issues in 1 category.


Please add conversion system from imperial to metric

Please make the bot convert imperial to metric automatically when it spots a certain pattern in the text.
Like the regex pattern of (\d{1,}'\d{1,}"), or other connotations of imperial.

May I suggest (\d+'\d+\") instead? 😅

What about ([1-9]'[1-9][0-9]?")


Connectivity Test: AKS Cluster failing node-to-node-encryption

Bug report

General Information
This result occurs on 3 different agent versions: v1.12.10, v1.4.3, v1.15.0 (nightly release)

Cilium CLI version (run cilium version)
v0.15.12
Orchestration system version in use (e.g. kubectl version, ...)
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.1", GitCommit:"4c9411232e10168d7b050c49a1b59f6df9d7ea4b", GitTreeState:"clean", BuildDate:"2023-04-14T13:21:19Z", GoVersion:"go1.20.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.10", GitCommit:"b8609d4dd75c5d6fba4a5eaa63a5507cb39a6e99", GitTreeState:"clean", BuildDate:"2023-10-23T16:10:33Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}
Platform / infrastructure information (e.g. AWS / Azure / GCP, image / kernel versions)
AKS
Link to relevant artifacts (policies, deployments scripts, ...)
Generate and upload a system zip: cilium sysdump
cilium-sysdump-20231110-093605.zip

How to reproduce the issue

instruction 1
cilium connectivity test --test node-to-node-encryption -d -v
Result:
[-] Scenario [node-to-node-encryption/node-to-node-encryption]
🐛 node-to-node-encryption test running in sanity mode, expecting unencrypted packets
🐛 Running /bin/sh -c ip -o route get <IP_ADDRESS> from <IP_ADDRESS> iif lo | grep -oE 'dev [^ ]' | cut -d' ' -f2
🐛 Running in bg: tcpdump -i eth0 --immediate-mode -w /tmp/node-to-node-encryption-host-netns-zh6p2.pcap src host <IP_ADDRESS> and icmp and dst host <IP_ADDRESS>
[.] Action [node-to-node-encryption/node-to-node-encryption/ping-ipv4: cilium-test/client-c4bfddc44-24nrv (<IP_ADDRESS>) -> cilium-test/host-netns-jm8gf (<IP_ADDRESS>:0)]
🐛 Executing command [ping -c 1 -W 2 -w 10 <IP_ADDRESS>]
❌ Expected to see unencrypted packets, but none found. This check might be broken
📄 No flows recorded for peer cilium-test/client-c4bfddc44-24nrv during action ping-ipv4
📄 No flows recorded for peer cilium-test/host-netns-jm8gf during action ping-ipv4
🐛 Running /bin/sh -c ip -o route get <IP_ADDRESS> from <IP_ADDRESS> | grep -oE 'dev [^ ]' | cut -d' ' -f2
🐛 Running in bg: tcpdump -i eth0 --immediate-mode -w /tmp/node-to-node-encryption-host-netns-zh6p2.pcap src host <IP_ADDRESS> and icmp and dst host <IP_ADDRESS>
🐛 Running /bin/sh -c ip -o route get <IP_ADDRESS> from <IP_ADDRESS> | grep -oE 'dev [^ ]' | cut -d' ' -f2
🐛 Running in bg: tcpdump -i eth0 --immediate-mode -w /tmp/node-to-node-encryption-host-netns-jm8gf.pcap src host <IP_ADDRESS> and icmp and dst host <IP_ADDRESS>
[.] Action [node-to-node-encryption/node-to-node-encryption/ping-ipv4: cilium-test/host-netns-zh6p2 (<IP_ADDRESS>) -> cilium-test/host-netns-jm8gf (<IP_ADDRESS>:0)]
🐛 Executing command [ping -c 1 -W 2 -w 10 <IP_ADDRESS>]
🐛 Running /bin/sh -c ip -o route get <IP_ADDRESS> from <IP_ADDRESS> | grep -oE 'dev [^ ]' | cut -d' ' -f2
🐛 Running in bg: tcpdump -i eth0 --immediate-mode -w /tmp/node-to-node-encryption-host-netns-zh6p2.pcap src host <IP_ADDRESS> and tcp and dst host <IP_ADDRESS>
[.] Action [node-to-node-encryption/node-to-node-encryption/curl-ipv4: cilium-test/host-netns-zh6p2 (<IP_ADDRESS>) -> cilium-test/echo-other-node-64b998965-6d7pm (<IP_ADDRESS>:8080)]
🐛 Executing command [curl -w %{local_ip}:%{local_port} -> %{remote_ip}:%{remote_port} = %{response_code} --silent --fail --show-error --output /dev/null --connect-timeout 2 --max-time 10 http://<IP_ADDRESS>:8080]
🐛 Finalizing Test node-to-node-encryption

Features Enabled/General system information:
🐛 Detected features:
🐛   cidr-match-nodes: Disabled
🐛   cilium-network-policy: Enabled
🐛   cni-chaining: Disabled:none
🐛   enable-envoy-config: Disabled
🐛   enable-gateway-api: Disabled
🐛   enable-ipv4-egress-gateway: Disabled
🐛   encryption-node: Disabled
🐛   encryption-pod: Disabled:disabled
🐛   endpoint-routes: Enabled
🐛   flavor: Enabled:aks
🐛   health-checking: Disabled
🐛   host-firewall: Disabled
🐛   host-port: Enabled
🐛   icmp-policy: Enabled
🐛   ingress-controller: Disabled
🐛   ipv4: Enabled
🐛   ipv6: Disabled
🐛   k8s-network-policy: Enabled
🐛   kpr-external-ips: Enabled
🐛   kpr-graceful-termination: Enabled
🐛   kpr-hostport: Enabled
🐛   kpr-mode: Enabled:Strict
🐛   kpr-nodeport: Enabled
🐛   kpr-session-affinity: Enabled
🐛   kpr-socket-lb: Enabled
🐛   l7-proxy: Disabled
🐛   monitor-aggregation: Enabled:medium
🐛   mutual-auth-spiffe: Disabled
🐛   node-without-cilium: Disabled
🐛   secret-backend-k8s: Disabled
🐛   tunnel: Disabled:vxlan
🐛   wireguard-encapsulate: Disabled
ℹ  Monitor aggregation detected, will skip some flow validation steps
ℹ  Skipping tests that require a node Without Cilium
🐛 Validating Deployments...
⌛ [ciliumnightly-816c6c11] Waiting for deployment cilium-test/client to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for deployment cilium-test/client2 to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for deployment cilium-test/echo-same-node to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for deployment cilium-test/echo-other-node to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for CiliumEndpoint for pod cilium-test/client-c4bfddc44-24nrv to appear...
⌛ [ciliumnightly-816c6c11] Waiting for CiliumEndpoint for pod cilium-test/client2-5c6c769648-c6jzw to appear...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client-c4bfddc44-24nrv to reach DNS server on cilium-test/echo-same-node-5988bfdbc-m7xqx pod...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client2-5c6c769648-c6jzw to reach DNS server on cilium-test/echo-same-node-5988bfdbc-m7xqx pod...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client-c4bfddc44-24nrv to reach DNS server on cilium-test/echo-other-node-64b998965-6d7pm pod...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client2-5c6c769648-c6jzw to reach DNS server on cilium-test/echo-other-node-64b998965-6d7pm pod...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client-c4bfddc44-24nrv to reach default/kubernetes service...
⌛ [ciliumnightly-816c6c11] Waiting for pod cilium-test/client2-5c6c769648-c6jzw to reach default/kubernetes service...
⌛ [ciliumnightly-816c6c11] Waiting for CiliumEndpoint for pod cilium-test/echo-other-node-64b998965-6d7pm to appear...
⌛ [ciliumnightly-816c6c11] Waiting for CiliumEndpoint for pod cilium-test/echo-same-node-5988bfdbc-m7xqx to appear...
⌛ [ciliumnightly-816c6c11] Waiting for Service cilium-test/echo-other-node to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for Service cilium-test/echo-other-node to be synchronized by Cilium pod kube-system/cilium-rxbwp
⌛ [ciliumnightly-816c6c11] Waiting for Service cilium-test/echo-same-node to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for Service cilium-test/echo-same-node to be synchronized by Cilium pod kube-system/cilium-rxbwp
⌛ [ciliumnightly-816c6c11] Waiting for NodePort <IP_ADDRESS>:31195 (cilium-test/echo-same-node) to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for NodePort <IP_ADDRESS>:30233 (cilium-test/echo-other-node) to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for NodePort <IP_ADDRESS>:30233 (cilium-test/echo-other-node) to become ready...
⌛ [ciliumnightly-816c6c11] Waiting for NodePort <IP_ADDRESS>:31195 (cilium-test/echo-same-node) to become ready...
ℹ  Skipping IPCache check
🔭 Enabling Hubble telescope...
⚠  Unable to contact Hubble Relay, disabling Hubble telescope and flow validation: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:4245: connect: connection refused"
ℹ  Expose Relay locally with:
cilium hubble enable
cilium hubble port-forward&
ℹ  Cilium version: 1.15.0
🐛 Registered connectivity tests:
🐛   <Test no-policies, 8 scenarios, 0 CNPs, expectFunc >
🐛   <Test no-policies-extra, 2 scenarios, 0 CNPs, expectFunc >
🐛   <Test allow-all-except-world, 5 scenarios, 1 CNPs, expectFunc >
🐛   <Test client-ingress, 1 scenarios, 1 CNPs, expectFunc 0x2752380>
🐛   <Test client-ingress-knp, 1 scenarios, 0 CNPs, expectFunc 0x27525a0>
🐛   <Test allow-all-with-metrics-check, 1 scenarios, 0 CNPs, expectFunc 0x27516a0>
🐛   <Test all-ingress-deny, 2 scenarios, 1 CNPs, expectFunc 0x2751380>
🐛   <Test all-ingress-deny-knp, 2 scenarios, 0 CNPs, expectFunc 0x2750d40>
🐛   <Test all-egress-deny, 2 scenarios, 1 CNPs, expectFunc 0x27527c0>
🐛   <Test all-egress-deny-knp, 2 scenarios, 0 CNPs, expectFunc 0x27528a0>
🐛   <Test all-entities-deny, 2 scenarios, 1 CNPs, expectFunc 0x2752980>
🐛   <Test cluster-entity, 1 scenarios, 1 CNPs, expectFunc 0x2752a60>
🐛   <Test host-entity, 1 scenarios, 1 CNPs, expectFunc 0x2752c20>
🐛   <Test echo-ingress, 1 scenarios, 1 CNPs, expectFunc 0x2752d00>
🐛   <Test echo-ingress-knp, 1 scenarios, 0 CNPs, expectFunc 0x27531c0>
🐛   <Test client-ingress-icmp, 1 scenarios, 1 CNPs, expectFunc 0x2753420>
🐛   <Test client-egress, 1 scenarios, 1 CNPs, expectFunc >
🐛   <Test client-egress-knp, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test client-egress-expression, 1 scenarios, 1 CNPs, expectFunc >
🐛   <Test client-egress-expression-knp, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test client-with-service-account-egress-to-echo, 1 scenarios, 1 CNPs, expectFunc >
🐛   <Test client-egress-to-echo-service-account, 1 scenarios, 1 CNPs, expectFunc 0x2753640>
🐛   <Test to-entities-world, 1 scenarios, 1 CNPs, expectFunc 0x27537e0>
🐛   <Test to-cidr-external, 1 scenarios, 1 CNPs, expectFunc 0x2750980>
🐛   <Test to-cidr-external-knp, 1 scenarios, 0 CNPs, expectFunc 0x2750720>
🐛   <Test echo-ingress-from-other-client-deny, 3 scenarios, 3 CNPs, expectFunc 0x2753a40>
🐛   <Test client-ingress-from-other-client-icmp-deny, 2 scenarios, 3 CNPs, expectFunc 0x2753ca0>
🐛   <Test client-egress-to-echo-deny, 2 scenarios, 3 CNPs, expectFunc 0x2753f00>
🐛   <Test client-ingress-to-echo-named-port-deny, 2 scenarios, 3 CNPs, expectFunc 0x2754180>
🐛   <Test client-egress-to-echo-expression-deny, 2 scenarios, 3 CNPs, expectFunc 0x27543e0>
🐛   <Test client-with-service-account-egress-to-echo-deny, 2 scenarios, 3 CNPs, expectFunc 0x2754640>
🐛   <Test client-egress-to-echo-service-account-deny, 1 scenarios, 3 CNPs, expectFunc 0x27548a0>
🐛   <Test client-egress-to-cidr-deny, 1 scenarios, 2 CNPs, expectFunc 0x27500e0>
🐛   <Test client-egress-to-cidr-deny-default, 1 scenarios, 1 CNPs, expectFunc 0x274fd40>
🐛   <Test health, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test north-south-loadbalancing, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test pod-to-pod-encryption, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test node-to-node-encryption, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test egress-gateway-excluded-cidrs, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test pod-to-node-cidrpolicy, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test north-south-loadbalancing-with-l7-policy, 1 scenarios, 1 CNPs, expectFunc >
🐛   <Test echo-ingress-l7, 1 scenarios, 1 CNPs, expectFunc 0x2754a40>
🐛   <Test echo-ingress-l7-named-port, 1 scenarios, 1 CNPs, expectFunc 0x2754d80>
🐛   <Test client-egress-l7-method, 2 scenarios, 2 CNPs, expectFunc 0x27550c0>
🐛   <Test client-egress-l7, 2 scenarios, 2 CNPs, expectFunc 0x274f6e0>
🐛   <Test client-egress-l7-named-port, 2 scenarios, 2 CNPs, expectFunc 0x274f1a0>
🐛   <Test client-egress-l7-tls-deny-without-headers, 1 scenarios, 1 CNPs, expectFunc 0x27553e0>
🐛   <Test client-egress-l7-tls-headers, 1 scenarios, 1 CNPs, expectFunc 0x27554c0>
🐛   <Test client-egress-l7-set-header, 2 scenarios, 1 CNPs, expectFunc 0x27555a0>
🐛   <Test echo-ingress-auth-always-fail, 1 scenarios, 1 CNPs, expectFunc 0x27557e0>
🐛   <Test echo-ingress-mutual-auth-spiffe, 1 scenarios, 1 CNPs, expectFunc >
🐛   <Test pod-to-ingress-service, 1 scenarios, 0 CNPs, expectFunc >
🐛   <Test pod-to-ingress-service-deny-all, 1 scenarios, 1 CNPs, expectFunc 0x27558c0>
🐛   <Test pod-to-ingress-service-allow-ingress-identity, 1 scenarios, 2 CNPs, expectFunc >
🐛   <Test dns-only, 2 scenarios, 1 CNPs, expectFunc 0x27559a0>
🐛   <Test to-fqdns, 2 scenarios, 1 CNPs, expectFunc 0x274e9c0>

We are having the same issue on a vanilla installation of k8s with kubespray (v2.23.1) and cilium deployed with helm(v 1.14.3)  on baremetal.

@jpayne3506 Thanks for the detailed report. I managed to reproduce your issue, which seems to be specific to Azure CNI Powered by Cilium because, differently to what happens normally in native routing configurations, pod to node traffic gets masquerated. In any case, that error is a sanity check of that specific connectivity test, and it is safe to ignore as no encryption is enabled in the cluster.
@kolovo Your issue seems a different one, although possibly related. Could you please provide the output of cilium connectivity test --test node-to-node-encryption -d -v and the sysdump for further investigation?


Using named targetPort to match backend pod

In helm and templates, using a named Service targetPort to match backend Pod. This will make the transition from running as root (port 80, 443) much easier as the Service will be able to target newly created Pods running as non-root (port 8080, 8443) without downtime during the rolling deployment.
No tests as this relate only to documentation.

Thanks!


Proposed edits with respect to number of lines and samples

I found that my problem regarding the issue https://github.com/leiyangleon/autoRIFT/issues/31 was due to having two Sentinel-1 adjacent reference images and having one secondary images. The code doesn't take into account the overlap between the number of lines and samples. I found out that the overlap is based on which of the reference or the secondary images have less number of samples and lines. These also match the dimensions of reference.slc.full and secondary.slc.full which are used on the testautoRIFT_ISCE.py.
Hence, I'm proposing edits to possibly resolved the issue.

@bjmarfito thanks for trying. However, at the stage of running autoRIFT, the two images should be exactly coregistered, namely having exact same number of lines/samples. The coregistration of the two should happen in the ISCE processing, not just simply truncating the number of lines/samples by autoRIFT. Otherwise, they are not guaranteed to have exact same viewing geometry. For that reason, it is not recommended to use different number of reference and secondary. Please use the same number of reference and secondary images which are also overlapping; if some image is not overlapping with the others, it is not helpful to include it anyway.

Thank you @leiyangleon for clarifying this out. I'll just follow your recommendation for now.
I'll close this PR.

@leiyangleon, I was just wondering why the slc.full files are not used instead as inputs to the lines and samples for the Geogrid module?

@bjmarfito src.full files or the associated .xml files do not contain the satellite orbit and viewing geometry information that are necessary for mapping between radar coordinates and the DEM coordinates.

@bjmarfito src.full files or the associated .xml files do not contain the satellite orbit and viewing geometry information that are necessary for mapping between radar coordinates and the DEM coordinates.

I get it now. Thank you @leiyangleon.


199 | Binary Tree Right Side View | C++

Binary Tree Right Side View -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign me to this issue! I want to work on it!

Hey, I would like to contribute to this issue. Please assign it to me.


Same interface for variance and expect.

Coverage increased (+0.005%) to 98.777% when pulling d1b117cff927db5dbc7759b6e138091d9012c7d4 on variance into 1687f9fde01ef134474a7539fcdc4dc453c3c178 on master.


Unable to add to HACS

The option to select repository is no longer there and will not install as a integration.

You can add it manually by putting in the repository link to get a custom add on

These are my only options

this does not get installed with hacs lol


Service Unavailable error on MacOSX

Unable to connect from the MacOSX host.
Using DockerToolbox-1.9.0c
Every command fails with a Service Unavailable error.
$ docker-machine --version
docker-machine version 0.5.0 (04cfa58)
$ docker images
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.21/images/json: Service Unavailable
$ docker-machine ls
NAME                     ACTIVE   DRIVER       STATE     URL                         SWARM
machine1                 *        virtualbox   Running   tcp://<IP_ADDRESS>:2376
I can ssh in the machine : Docker is ok.
docker-machine ssh machine1
...
Boot2Docker version 1.9.0, build master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015
Docker version 1.9.0, build 76d6bc9
docker@homebyme:~$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
hello-world         latest              0a6ba66e537a        4 weeks ago         960 B

Closed as duplicate of #2282


problem while using python3

hi ,
i'm trying to connect the Mindwave Mobile 2 with my laptop running ubuntu 18.04 and use with python3 however i get an error message
Discovered Mindwave Mobile...
Traceback (most recent call last):
  File "read_mindwave_mobile.py", line 12, in <module>
    dataPoint = mindwaveDataPointReader.readNextDataPoint()
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveDataPointReader.py", line 20, in readNextDataPoint
    self._putNextDataPointsInQueue()
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveDataPointReader.py", line 30, in _putNextDataPointsInQueue
    dataPoints = self._readDataPointsFromOnePacket()
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveDataPointReader.py", line 34, in _readDataPointsFromOnePacket
    self._goToStartOfNextPacket()
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveDataPointReader.py", line 46, in _goToStartOfNextPacket
    byte = self._mindwaveMobileRawReader.getByte()
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveMobileRawReader.py", line 74, in getByte
    self._ensureMoreBytesCanBeRead(100);
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveMobileRawReader.py", line 79, in _ensureMoreBytesCanBeRead
    self._readMoreBytesIntoBuffer(amountOfBytes)
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveMobileRawReader.py", line 56, in _readMoreBytesIntoBuffer
    newBytes = self._readBytesFromMindwaveMobile(amountOfBytes)
  File "/home/revanth/python-mindwave-mobile/mindwavemobile/MindwaveMobileRawReader.py", line 65, in _readBytesFromMindwaveMobile
    receivedBytes += self.mindwaveMobileSocket.recv(missingBytes)
TypeError: must be str, not bytes

however i get no such error message when i execute with python2.
new to python so sorry if silly problem

I'm getting the same error as well. Someone please help

In python 3, bytes and str instances cannot be used together with operators (like > or +).  With a byte string you can decode via .decode() but utf-8 does not work

These updates got my code working for python 3.
MindwaveMobileRawReader.py
def _readBytesFromMindwaveMobile(self, amountOfBytes):
    # receivedBytes = ""
    receivedBytes = b''

def _getNextByte(self):
    # nextByte = ord(self._buffer[self._bufferPosition])
    nextByte = self._buffer[self._bufferPosition]

def _getNextBytes(self, amountOfBytes):
    # nextBytes = list(map(ord, self._buffer[self._bufferPosition: self._bufferPosition + amountOfBytes]))
    nextBytes = list(self._buffer[self._bufferPosition: self._bufferPosition + amountOfBytes])

@BioMycoBit seems great, would you be willing to make a pull request out of it?

Thanks!
I have tried it and it works, I have tested only the sample code. I will try other cases as well a let you know if any issues are present

@BioMycoBit seems great, would you be willing to make a pull request out of it?

@robintibor see pull request.  https://github.com/robintibor/python-mindwave-mobile/pulls

Amazing thanks @BioMycoBit


Add --txpool.locals Vec address to txpool cli args

Describe the feature
Very similar to https://github.com/paradigmxyz/reth/issues/5520
but this time it should treat the given Addresses as local
--txpool.locals value
Comma separated accounts to treat as locals
cc @Blaeaea
Additional context
No response

I take this :)

hey @Blaeaea are you working on this or can I open this up?

hey @Blaeaea are you working on this or can I open this up?

hey, yes i'am working on this :)


Word filter does not work for thread titles

http://bubblebbs.cafe/threads/325
cum is not wordfiltered in the title (yellow area)

Thank you so much for testing this @MaiKawakami! I have resolved this issue thanks to you reporting it.
I cannot pay you but please take this cookie :cookie:


wip meta file

Solution
a .meta file containing information related to displaying in the launcher:

description, opportunity to display controls
image, for flavour, displayed on fullscreen background when game is hovered, and in miniature when not.

I tried running it on windows and the app crashed when I tried to launch the game.
"thread 'Compute Task Pool (13)' panicked at 'called Result::unwrap() on an Err value: Os { code: 267, kind: NotADirectory, message: "The directory name is invalid." }', src\core.rs:24:48"
I think that windows doesn't like that the executable is not a directory.


fix: types for ts5.6

What kind of change does this PR introduce?
fixes https://github.com/webpack/webpack/pull/18751/
fixes https://github.com/webpack/webpack/issues/18748
Did you add tests for your changes?
No
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
No

@alexander-akait Hi, sorry to ping you. 😅
This PR is required for the upgrade of TS, could you share when you are expecting to release this fix?

@devjiwonchoi Hi, release will be this week, maybe tomorrow, want to finish some perf prs

Thanks for your quick response! :)


WIP: kittengrad

The Kittengrad Transactor Network Draft to sketch out next phase implementation.

One thing that may be illuminating is comparing our protocol to existing transaction mining/validation/witnessing approaches -- I think with this piece in particular comparative analysis is very useful. It would also help us think about the steps between this BCP0 and a staked approach.

High-level questions for a new blockchain design:

Which resource(s), if you have enough of it, allows you to control the network with high probability. Or, which network(s), if infiltrated allows you to control the greater network?

Are there already nefarious organizations that control vast amounts of the chosen resource? E.g. IP addresses, starting a new blockchain that's compatible with existing Bitcoin mining equipment.

How does it ensure penalties for bad behaviors? (May be a long list of bad behaviors and penalty mechanisms.)

What are typical sequences of API calls which applications built on top of this will use? E.g. API calls for two parties doing a Bitcoin transaction.

What are typical sequences of API calls, for types of attacks that this blockchain aims to mitigate? E.g. a Bitcoin double spend attempt between two parties.

What particular scaling tradeoffs / decisions are we aiming for from day-1? (Maximizing bulk throughput speed, supporting huge volume of artifacts, cost of making huge number of artifacts available on the network, cost of actually distributing a huge number of artifacts through out the network, dozens of other design tradeoffs.) Think CAP, but extended to dozens of choices. Unlikely IMO that big changes to these decisions can be effectively patched in later.

Advanced - what social or economic factors make the blockchain grow stronger (instead of more vulnerable) as it grows and becomes more valuable?

Advanced - As the relative cost and availability of resources such as network bandwidth, cpu speed, storage speed, etc. change over the years, how do these relative changes between resources affect the blockchain in the long term?

Yeah, I think these are (good!) mostly "phase 3" questions except for

What are typical sequences of API calls which applications built on top of this will use? E.g. API calls for two parties doing a Bitcoin transaction.

and

What particular scaling tradeoffs / decisions are we aiming for from day-1? (Maximizing bulk throughput speed, supporting huge volume of artifacts, cost of making huge number of artifacts available on the network, cost of actually distributing a huge number of artifacts through out the network, dozens of other design tradeoffs.) Think CAP, but extended to dozens of choices. Unlikely IMO that big changes to these decisions can be effectively patched in later.

Yeah, agreed.

What are typical sequences of API calls which applications built on top of this will use? E.g. API calls for two parties doing a Bitcoin transaction.

Well, we need more experience with the system in order to observe actual usage patterns. Typically, when we ingest a new artefact we have two inserts (entity + artefact) followed by an update for the creation cell. After ingestion, we can expect isolate updates on some chain.

What particular scaling tradeoffs / decisions are we aiming for from day-1

I think we want to be maximizing throughput initially, hence the focus on block commit chaining.

One more, somewhat higher level question: it seems like we will definitely need a few network level features:

NAT traversal
Peer discovery
Multicast/peer routing
Health checks
Join notificaitons

Netty doesn't really provide any of these out of the box (other than multicast, potentially) so we would have to use 3rd party libs or roll our own. It's worth considering that libp2p provides all of these capabilities and is under rapid development; it's also kind of nice for the consensus layer and the datastore (IPFS) to have similar and compatible capabilities.

We don't have to use netty or even scala for the implementation; I have been considering libp2p as well.
Until we open up the transactor membership for external transactors we don't have to deal with NAT traversal.  When we open up we'll be in the peculiar situation of desiring internal routing between transactors in the private network, which is potentially tricky to solve.

Yeah, we will want to form an overlay network with internal routing. I think the libp2p model will support this.

The Kittengrad architecture replaces the Copycat cluster with a peer-to-peer network of transactors, who independently accept and propagate transactions and synchronize with the generation of new blocks.

I am extremely skeptical this will work, because:
Transactors must be canonical over some set, to avoid collision based DoS (initiated by either clients or transactors).
Thus, transactors should be FT or BFT clusters themselves.

updateChain may require handoff protocol if clients are talking to non-canonical transactors.
Each CanonicalRef can only modified (via updateChain) by a single transactor within a given block. This needs to be enforced at the application/client level to avoid merging blocks. This should also be enforced in the BCP0 layer, to stop malicious transactors.
This is how the interface should be modified to allow for CanonicalRef binding to a given transactor:
insertCanonical(data) : (TxID, CanonicalREF, [ImpliedTransactorID])
updateChain(CanonicalRef, [ImpliedTransactorID], data) : TxID
handoffCanonical(CanonicalRef, [ImpliedTransactorID], newTransactorID) : TxID
At the BCP layer, only if the Tx describing the handoff is successful will later attempts to update a given CanonicalRef from the ‘newTransactorID’ succeed.
handoffCanonical is stored in blocks to prevent attacks from malicious transactors.

Transactors putting up a bond to be canonical over a subset of CanonicalRefs might make sense here.
If you wait until later, you're going to be storing nonsense data (attacker spam) in the blocks.
This relates back to the conversation we had at MIT regarding there actually being three different networks, IIRC. Trusted/Institutional transactors, public transactors, and I've forgotten the third one, I think it might have been a decentralized storage network.
Am I correct in assuming that transactors are each managing their own CRDT, which then gets merged into an ordered BCP0 block?
I am (still) confused about the relationship between BCP0, a blockchain and CRDTs. The blocks in a blockchain provide a canonical ordered view of history and (depending on the implementation) simply looking at the last block can provide a conflict free snapshot. But it seems to me in the model that you're describing end-user-clients themselves realize a conflict free canonical ordering based on a set of user specified parameters that allow them to resolve conflicts in the RDT generated by BCP0, since it's trivial for an attacker to generate conflicting updateChain messages.
it is also possible to virtualize canonical transactors, in much the same way nodes are virtualized in Cassandra. (https://docs.datastax.com/en/cassandra/2.2/cassandra/architecture/archDataDistributeVnodesUsing.html)

Hey @AFDudley , a couple of quick comments as you are raising interesting issues for long term view of the mediachain.

Transactors must be canonical over some set, to avoid collision based DoS (initiated by either clients or transactors).
Thus, transactors should be FT or BFT clusters themselves.

We are not partitioning the canonical space at this phase, although this is something we are considering in the long term. Nonetheless, the idea of having interconnected BFT clusters of transactors operated by independent stakeholders is part of our large scale world-view.
As an aside, I think you are taking the doc out of context a bit.
The kittengrad design is more concerned with implementing the initial cluster if you like, as we intend it to be the first step towards the large scale architecture and it suffices to be simply FT (not BFT).
We want to iterate and build so that we can grow the system organically.

updateChain may require handoff protocol if clients are talking to non-canonical transactors.

We don't have the notion of canonical transactors as we don't have partitioning at this level, so there is noeed for a handoff protocol (yet).

Each CanonicalRef can only modified (via updateChain) by a single transactor within a given block
...

This is not true -- we allow for concurrent update transactions and we have two alternatives in order to resolve conflicts: either through invalidation (strict writes) or by delayed writes which allows merging of concurrent updates.

I am (still) confused about the relationship between BCP0, a blockchain and CRDTs.

The blockchain provides an ordered canonical view for the state of the world up to the last commited block.
At any given moment there are pending transactions, asssuming the system is under some write load.
BCP0 is tasked with synchronizing the transactors to commit the next block by packaging pending transactions.
The CRDT part comes in the management of the worklog of pending transactions, if we go forward with a delayed write implementation. We can treat pending transactions as a mapping of canonical to partially ordered sets of updates, which commute modulo transactor-relative order. The commute space is simply the space of possible interleavings preserving transactor partial order

@vyzo Thanks for clarifying. I should have said earlier the document is good and easy to read which is appreciated in this space.

The kittengrad design is more concerned with implementing the initial cluster if you like, as we intend it to be the first step towards the large scale architecture and it suffices to be simply FT (not BFT).

For me this was the major lesson learned from BigChainDB: It's very difficult to apply BFT to a FT system after the fact. So, I generally spec out a full BFT system and then work back to FT. This issue will appear in some of my following comments.

This is not true -- we allow for concurrent update transactions and we have two alternatives in order to resolve conflicts: either through invalidation (strict writes) or by delayed writes which allows merging of concurrent updates.

Can you please explain how either of these strategies is viable in an adversarial environment? Invalidation can be DoS vector, depending on how transactions are priced.
Merges either require a centralized authority, or you're basically recreating normal FT DB write contention and in the process destroying the validity of the transaction receipts generated by the transactors and provided to the clients. (If I am misunderstanding and these receipts are never generated, or if that's what you mean by 'delayed write', apologies. 😄 )

The CRDT part comes in the management of the worklog of pending transactions, if we go forward with a delayed write implementation. We can treat pending transactions as a mapping of canonical to partially ordered sets of updates, which commute modulo transactor-relative order. The commute space is simply the space of possible interleavings preserving transaction partial order

I don't understand how this make sense in the FT context as opposed to the BFT context. If it's FT we can assert the pending transactions will never be write-contentious and thus we need no logic to resolve ordering. But if it's BFT we should assume a significant percentage of transactions will be write-contentious and created at the greatest inconvenience to the transactors. (Which goes back to my point about designing BFT first, normally in FT you can punt write-contention issues to the application/user but in BFT we cannot do this because they are adversarial.)
If what you mean by "delayed write" is that transaction receipts are only generated from BCP0 and not transactors, this all makes a lot of sense... I guess you could also update for both and then clients would need to understand that the transactor receipt is not final and the BCP0 receipt is.

For me this was the major lesson learned from BigChainDB: It's very difficult to apply BFT to a FT system after the fact.

Thanks for the advice. We have already put some thought on the system, but we need to flesh out the stake model and potential coin (as transaction fuel) semantics.

Can you please explain how either of these strategies is viable in an adversarial environment? Invalidation can be DoS vector, depending on how transactions are priced.

Transaction invalidation is more vulnerable to denial of service by spamming the system, as it is a form of optimistic concurrency. However concurrent transactions must really be within the window of transaction propagation in order to conflict and cause degradation.
Delayed writes ensure liveness in the sense that good transactions keep making progress, but I think we have a bigger problem if we are getting spam-attacked.

If what you mean by "delayed write" is that transaction receipts are only generated from BCP0 and not transactors, this all makes a lot of sense... I guess you could also update for both and then clients would need to understand that the transactor receipt is not final and the BCP0 receipt is.

Yeah, clients receive confirmation through the block commit protocol (which is run by the transactors).

[...]we need to flesh out the stake model and potential coin (as transaction fuel) semantics.

I think using Tendermint/Atom from within libp2p will go a long way toward simplifying the design and implementation of your stake model and coin. It's worth investigating if Sia could be integrated at this layer as well.

Delayed writes ensure liveness in the sense that good transactions keep making progress, but I think we have a bigger problem if we are getting spam-attacked.

If there is a coin involved on a public network, attacks will happen. The financial incentives work both ways.

I think using Tendermint/Atom from within libp2p will go a long way toward simplifying the design and implementation of your stake model and coin. It's worth investigating if Sia could be integrated at this layer as well.

Yeah, we are actively considering using golang and libp2p for the kittengrad implementation.

If there is a coin involved on a public network, attacks will happen. The financial incentives work both ways.

So true, sadly.

Added Radical Kittengrad draft for the new direction we are considering.

Merging in for reference purposes; work in this direction is currently suspended.


Names shown as revoked

What is this issue about? Should revoked names disappear without a label or should user be able to remove revoked names by himself or wallet should automatically claim revoked names back? cc: @CedrikNikita

Current version of wallet doesn't have such problems. Feel free to reopen this issue, if it will pop up again.


Roll engine 9daf5c8d213a..be69b07cc454 (9 commits)

https://github.com/flutter/engine/compare/9daf5c8d213a...be69b07cc454
git log 9daf5c8d213a..be69b07cc454 --no-merges --oneline
be69b07cc Roll src/third_party/skia d2fa2eb59f2d..487132b82826 (1 commits) (flutter/engine#7314)
732ea7669 Allow dynamic patches without a patch number. (flutter/engine#7309)
20ee4e3e9 Revert "Only reject gestures to embedded UIViews when the framework says so. (#7307)" (flutter/engine#7313)
28e152f7e Roll src/third_party/skia cae020ae5f5f..d2fa2eb59f2d (3 commits) (flutter/engine#7312)
7c65290da Roll src/third_party/skia 31c1bf89657f..cae020ae5f5f (1 commits) (flutter/engine#7311)
180d8a7d9 Roll src/third_party/skia f6e963ef91c2..31c1bf89657f (1 commits) (flutter/engine#7310)
cc9c6702d Only reject gestures to embedded UIViews when the framework says so. (flutter/engine#7307)
2fb2b2729 Roll src/third_party/skia 3605fde88b2a..f6e963ef91c2 (1 commits) (flutter/engine#7306)
220ea0e1e Roll version of Dart to d1817ddc91fd3aea061647b2e21860c47a5a5180 (flutter/engine#7286)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.

@liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5091931216412672 , https://cirrus-ci.com/task/6358568611610624 , https://cirrus-ci.com/task/5232668704768000 , https://cirrus-ci.com/task/4951193728057344

Commit queue failed; closing this roll.


Migrate to Travis-ci.com

https://devops.stackexchange.com/questions/1201/whats-the-difference-between-travis-ci-org-and-travis-ci-com
Via this, it seems like travis-ci.org will be deprecated on December 31, 2020. So this probably needs to be migrated sooner or later to travis-ci.com

Hi @danielcliu,
thanks for pointing this out! I took care of this in #88.


Linux and GitHub Actions

I landed here because there are multiple related issues like this one
I am using the helaili/jekyll-action@v2 GitHub Action to deploy the site and I am getting this error:
 Dependency Error: Yikes! It looks like you don't have jekyll_picture_tag or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. If you've run Jekyll with `bundle exec`, ensure that you have included the jekyll_picture_tag gem in your Gemfile as well. The full error message from Ruby is: 'Could not open library 'glib-2.0.so.0': Error loading shared library glib-2.0.so.0: No such file or directory. Could not open library 'libglib-2.0.so.0': Error loading shared library libglib-2.0.so.0: No such file or directory' If you run into trouble, you can find helpful resources at jekyllrb.com/help/!

Locally (Windows 10), it is working perfectly, but I am not sure why I have this error in GitHub.
I tried to install glib-2.0 and/or libvips with no success.
I am using the latest version of all dependencies.

Hi @JavierSegoviaCordoba,
You can see the github action we use for ruby-vips here:
https://github.com/libvips/ruby-vips/blob/master/.github/workflows/test.yml
And it (obviously) works. Does that help?
I would open an issue on helaili/jekyll-action@v2 if you can't get it going.

Indeed I tried like 3 or 4 Jekyll actions, same issue. I am going to try your setup now to check if it works.

It doesn't work for me, I will file an issue in the helaili action, but, strangely, all actions for deploying Jekyll sites to GitHub pages are failing with the same issue.

I pinged the repo and reran the action:
https://github.com/libvips/ruby-vips/runs/2887946268?check_suite_focus=true
It seems to work.

Yeah, maybe a problem with helaili docker installation thank you for your help, I am going to close this issue.


Lock issue when there is no recipes left

.lock file appears when there is no recipes to be executed

Resolved with workers patch


Fix string error

The documented code is obv. not working without the additional escape chararcter since the string ends too early

Thanks for your contribution! Because this PR is old, we will bring your change forward and close this PR. Thanks again!


Add first version of german translations

Would be cool if someone could proof-read this.

My German is not that good, but it seems fine to me :) I understood everything which is a good thing.
Thanks a lot. I merge it like that and if you find someone to review it you can still send some fixes later on.


[Feature Request] Per-project configuration

Now, gptcommit uses a global configuration, including API keys, prompts, etc. Is it possible to have per-project configurations?
For example, with a per-project prompt, I can have only titles for some projects, or I can add some specific characters in the messages, for example, some emojis.
One solution I can think of is to have a configuration file ./.gptcommit/config.toml, which overwrites the global one.
It is also helpful for us to use different API keys and track their usage for different projects.

Solving this in #54

Fixed in v0.1.17. See README or executable's help for usage of the gptcommit config --local flag


Allow const autoloading a chance to act

(I've had more time to investigate #25 this morning and I think I've come up with a solution that will work in all cases.)
Particularly, Rails const autoloading.
In a Rails app where you have models defined under app/models, these constants are loaded as they are referenced... but only when explicitly mentioned or you const_get them (essentially the same action).
When dry-core uses const_defined?, it will not attempt to autoload this constant, and therefore it will not be defined. This causes the ClassBuilder to build a new anonymous class, which is the incorrect behaviour.
The correct behaviour would be to at least attempt to get the constant -- which triggers autoloading -- before checking if it is defined. If the constant is unable to be const_get'd, then we ignore that error and carry on as usual.

The test in this PR is flaky -- it runs by itself, but not as a part of the whole test suite. I haven't quite gotten to the bottom of that and some help would be greatly appreciated.

I'm OK with this change, assuming test issues can be resolved.

This is a slippery slope, FWIW. ROM caches classes and its cache must be flushed in order things to work. Things are getting more complicated when AS reloads only some i.e. changed files, I don't think it can ever be made reliable. Of course, I might be wrong and there is a way. :) This particular change shouldn't break anything but I'll need to test it against real code anyway.

@flash-gordon rom-rails needs to handle things like flushing caches, we can't build our gems in a way that will work with rails OOTB (I'm sure you know this). It would be good to at least report an issue in rom-rails and make a list of things rom-rails needs to do in order to make code reloading work.

I've updated the test to use a before block with module_eval to define the autoloading and that seems to have fixed the flakiness :)


Apply UpdateMetadata to line drawing

Description:
Apply UpdateMetadata to the line drawing.
When users draw lines, the users start drawing by mouse down, then when mouse up, a line is completed.

While drawing a line, use UpdateMetadata to send raw points directly to the peers.
When the line drawing is completed, sample raw points then add them to the document as a line.
When painting lines using points, apply Bezier Curve to the sampled points.

Currently, during line drawing, the line is wobbly because it is painted by sampling points and changing it to a bezier curve.
Why:

We can provide a smoother line drawing experience.

tldraw 를 지원하기 때문에 이슈를 닫습니다.


Redirect to Login page again and again

Screenshot from 2020-07-29 13-56-46

I couldn't create any external-app, course, assessment its keep on redirecting login page,
Sometimes it asks to enable cookies, I did manually too.

@lbjay Can you please help me in this out.
Thanks-


⚠ Orpheus has degraded performance

In c10a772, Orpheus ($OPS) experienced degraded performance:

HTTP code: 504
Response time: 21062 ms

Resolved: Orpheus performance has improved in c776693.


most content missing from large svg

Running svgo on http://www.jirka.org/nlin-sierpinski-mbx.svg kills everything in the picture.

I cannot reproduce with svgo 2.0.2. @TrySound maybe this is also fixed?

Thanks. Looks like all works. I will look into performance later.

I was excited to hear that it is fixed.  However,, I just tried it with newly installed svgo version 2.1.0 and it still totally kills the picture, I get a mostly empty picture:
➤ svgo -i nlin-sierpinski-mbx.svg -o test.svg
nlin-sierpinski-mbx.svg:
Done in 24112 ms!
2583.887 KiB - 99.5% = 13.275 KiB
Not sure what other difference for me.  I'm running on linux, Ubuntu 20.10 to be precise.  Installed through npm.

Hmm, this broke again in 2.1.0 it seems @TrySound
Microsoft Windows [Version 10.0.19042.844]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\xmr\Desktop>node -v
v14.15.5

C:\Users\xmr\Desktop>curl -sL http://www.jirka.org/nlin-sierpinski-mbx.svg>1.svg

C:\Users\xmr\Desktop>svgo 1.svg -o 2.svg

1.svg:
Done in 38192 ms!
2583.887 KiB - 99.5% = 13.275 KiB

C:\Users\xmr\Desktop>npm i -g<EMAIL_ADDRESS>C:\Users\xmr\AppData\Roaming\npm\svgo -> C:\Users\xmr\AppData\Roaming\npm\node_modules\svgo\bin\svgo
+<EMAIL_ADDRESS>added 1 package from 1 contributor, removed 1 package and updated 1 package in 2.9s

C:\Users\xmr\Desktop>svgo 1.svg -o 2.svg

1.svg:
Done in 145807 ms!
2583.887 KiB - 92.3% = 199.252 KiB

Better reopen the issue and add this SVG to the tests

Correction, 2.0.3 also works fine. So, it seems it's something in https://github.com/svg/svgo/compare/v2.0.3...v2.1.0

@TrySound it seems that enabling the convertStyleToAttrs fixes the issue here :S

Heh, interesting

It's not easy to fix this permanently without new style engine which would be able to compute attributes and all styles.
Though yeah enabling convertStyleToAttrs in your case would fix the issue.

Tested to try with convertStyleToAttrs, though it took me quite a while to figure out how to do that since --enable/--disable seem to be gone from cli and if I use the snippet for config to use the extendDefaultPlugins doesn't seem to work for me: I get "Error: Cannot find module 'svgo'".  Finally, just stuck the full module list from the readme in there, and added 'convertStyleToAttrs' to the module list (added it at the end), and was still not getting it to work.  Still got the mostly empty output.
Got it to work by sticking convertStyleToAttrs just in front of the convertPathData plugin.  But I get a slightly different size so I am assuming I still have not figured out how to simply enable the plugin, and I must have disabled something else or not the right order.
➤ svgo  -i nlin-sierpinski-mbx.svg -o test.svg
nlin-sierpinski-mbx.svg:
Done in 197581 ms!
2583.887 KiB - 92.2% = 200.956 KiB

To extend default plugins you need to install svgo locally. I guess we can do better. Will think about it.

Fixed the image here https://github.com/svg/svgo/commit/79dbb4bf6e7464e946d838ade0aa23c7189762f7 ad here https://github.com/svg/svgo/commit/7901588a9f18d6ef476389405a73cd7fe42ed179. Will release today or tomorrow.

Fixed in 2.2.0


Clarify pronunciation of hlarp

Kind of like "larp" but with a light "h" sound.
Seriously though, if you have a better name...

I love it.

Maybe we should just call it hlatools ?

Can we pronounce it h'latools, soft h

I like the Lovecraftian direction we're going.

I was trying to draw a reference to 'harp' 's ... just noticed that HlaTools is taken.


Support configuring per-feature pkg-config names

In GStreamer the GL library was split from one big pkg-config file into separate ones per platform (EGL, X11, Wayland) plus the main one (GL).
For backwards compatibility in the crate for gstreamer-gl-x11-sys (for example) it would be needed to depend on gstreamer-gl-1.0 for versions < 1.18 and on gstreamer-gl-x11-1.0 for versions >= 1.18.
Similarly gstreamer-gl-x11 would have to depend on the gstreamer-gl-sys crate (with "x11" feature) for < 1.18 and on gstreamer-gl-x11-sys (without any features) for >= 1.18.
I don't think either of this can currently be expressed.

Indeed I don't think it's currently possible.
Ideally it would be nice to re-use the existing feature versions if possible but I'm not sure how to properly express all that. :\

See also https://gitlab.freedesktop.org/gstreamer/gstreamer-rs-sys/-/merge_requests/65 for the relevant MR

Ideally it would be nice to re-use the existing feature versions if possible but I'm not sure how to properly express all that. :\

Maybe
feature-versions = { v1_14 = "gstreamer-gl-1.0/1.14", v1_18 = "gstreamer-gl-egl-1.0/1.18" }

?

A bit magic but I suppose it could work as crate names are not supposed to contain /.
A more explicit version way could be:
gst_gl = { v1_14 = { name = "gstreamer-gl-1.0", version = "1.14"} , v1_18 = { name = "gstreamer-gl-egl-1.0", version = "1.18" }}

A bit magic but I suppose it could work as crate names are not supposed to contain /.

pkg-config names, not crate names

Right.
Which version do you prefer? I think I'd vote for the second following the good old "explicit is better than implicit" principle.

I agree

Let's go for that then.
Unfortunately I'm pretty busy these days so I'm afraid I won't have time to work on this any time soon. But if you have some time I'm happy to merge and release a patch adding this feature.

Same, updating the bindings used up a lot of my spare time for this week. I'll do the hack I did for the stable version of the bindings for now then.

A more explicit version way could be:
gst_gl = { v1_14 = { name = "gstreamer-gl-1.0", version = "1.14"} , v1_18 = { name = "gstreamer-gl-egl-1.0", version = "1.18" }}

This is not coherent with the existing syntax for feature version:
gstreamer = { name = "gstreamer-1.0", version = "1.0", feature-versions = { v1_2 = "1.2", v1_4 = "1.4", v1_6 = "1.6" }}
So we could either use the same pattern and introduce feature-names :
gst_gl = { name = "gstreamer-gl-1.0", version = "1.14" , feature-versions = {v1_18 = "1.18" }, feature-names = { v1_18 = "gstreamer-gl-egl-1.0" }}
That split the versioning information, so it may be best to merge them all together as suggested above:
gst_gl = { v1_14 = { name = "gstreamer-gl-1.0", version = "1.14"} , v1_18 = { name = "gstreamer-gl-egl-1.0", version = "1.18" }}
This syntax is more coherent and could be easily extended to override more fields later if needed.
But that would be a config syntax break, assuming we stop supporting the current syntax.
The new syntax would also be more verbose, as something currently wrote using
[package.metadata.system-deps.gstreamer_1_0]
name = "gstreamer-1.0"
version = "1.8"

[package.metadata.system-deps.gstreamer_1_0.feature-versions]
v1_10 = "1.10"
v1_12 = "1.12"

will have to be written using
[package.metadata.system-deps.gstreamer_1_0]
name = "gstreamer-1.0"
version = "1.8"

[package.metadata.system-deps.gstreamer_1_0.v1_10]
version = "1.10"
[package.metadata.system-deps.gstreamer_1_0.v1_12]
version = "1.12"

But as most of this is generated anyways maybe it's not that bad.
@sdroege : what do you think?

Seems nicely clean to me.
But things like

[package.metadata.system-deps.gstreamer_1_0.v1_12]
version = "1.12"

could also be omitted in theory. We could define that a v1_12 automatically maps to 1.12 as requirement unless otherwise specified. That way you could specify all features via an array.

Default feature -> version sounds like a good idea. But I think I'd still remove the existing feature-versions to not have 3 way to deal with those (the default, version field in a version specific dict and feature-versions).
The default will likely cover the existing usage so porting will be a simple matter of remove feature-versions.

Sounds good to me, thanks :)

I'll do the hack I did for the stable version of the bindings for now then.

@sdroege : which hack is that? I don't see any use of gstreamer-gl-egl in gstreamer-rs-sys.

Yes, that's the hack. The .gir files are merged into GstGL-1.0.gir and only gstreamer-gl-1.0 is used. There are WIP MRs on gstreamer-sys and gstreamer-rs that switch to the separate ones.

I just released 2.0.0 with this change.


Not Forwading Massages

NOT FORWARDING MASSAGES
IN LOGS EVERYTHING IS FINE BUT NOT SENDING MASSAGES ANYMORE
NEED A REVIEW PLEASE

Past week i've installed a couple of Dockers and working perfectly

I've tried everything, but the app still isn't working. I've checked the logs, rebuilt the app, and even used Docker, but nothing seems to be fixing the issue.

Seems related to this error: Phone migrated to 4   into start log, The app try too reach the server <IP_ADDRESS>:443 but in my api telegram I have a different server set, In case how can I change/modify it?


Contributing guidelines

It would be great to have contributing guidelines and development requirements for creating pull requests.

Feel free to write some based on what you've learned/assumed from your PR. I don't have the time to author some myself at the moment


Skip TCPIP device discovery if target_ip is specified

Simply assumes that the given device exists.
If it doesn't exist, TCP connect would fail later anyway, currently in depthai-core:
RuntimeError: Failed to connect to device, error message: X_LINK_COMMUNICATION_NOT_OPEN

speeds up a little the bootup time when a given IP is specified, skipping UDP discovery ping.
fixes a problem connecting to devices behind NAT, for cases where UDP broadcast forwarding is not possible (which is the case for most routers).

@themarpe Not sure about merging this, if the work being done on device_search_improvements would improve this process, but it would be a quick solution for when we'll upgrade the bootloader/FW that configures the gateway/route, allowing to connect to devices behind NAT.
Also will need only TCP port 11490 to be forwarded in the router, not also UDP 11491.
For reference, Luxonis Community Discord discussion starting here.

I think this can be merged for now.
In device_search_improvements specifying name/path when connecting will result in not repinging the device, but a unicast UDP is also a possibility to do if MXID is inteded to be received.

But do test on booting from BL -> APP, as the IP is carried onwards when searching again for device and waiting for it.
Just so that it doesn't have the sideeffect of reconnecting immidiatelly

For "correct/same" connecting behavior, I think we should modify that this still does device discovery, but using an UDP unicast instead, to be able to traverse to a different LAN network. Thoughts @alex-luxonis ?

Superseeded by #42


Image issue while posting blog

Describe the bug

Blog doesn't get posted unless I attach an image. If I don't attach image then it gives internal server error.

When I do attach an image it doesn't show in the blog.

To Reproduce
Steps to reproduce the behavior:

Login
Publish blog without attaching any image
See error
Then try to publish one with image
See error

Expected behavior

Post should be published even if image is not attached.
If image is attached, it should show up in the blog

Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

Yes, I checked this and found that image is not saved in the database. That's why it's not showing

/assign

Yes, I checked this and found that image is not saved in the database. That's why it's not showing

Even after saving in the database it is not showing, the ejs template does not have a section for the image.

Yes, I checked this and found that image is not saved in the database. That's why it's not showing

Even after saving in the database it is not showing, the ejs template does not have a section for the image.

Yes, you have to create a section for it too


Add zhejiang network option

Add zhejiang network option: use with --network zhejiang
Closes #5070

:tada: This PR is included in v1.6.0 :tada:


fix(deps): pass prefix value to KMS DA

Description

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

Test failed with  tests.go:371: Error deploying configuration Gen AI - Databases for Elasticsearch: cloudant read error: get project config. Unrelated to changes in this Pr, so re-running..

/run pipeline

:tada: This PR is included in version 0.3.3 :tada:
The release is available on:

GitHub release
v0.3.3

Your semantic-release bot :package::rocket:


SCIM User pagination doesn't function correctly

Describe the issue:
SCIM user pagination doesn't function as expected.
How to reproduce:

Create 7 new users. There will be 8 total users in the user store including admin.
paginate the users such that one page gets 3 users.
REQUEST: {{base_url}}/scim2/Users?count={count}&startIndex={startIndex}&attributes=username

startIndex = 1, count = 3 --> return user 1, 2 ,3

startIndex = 4, count = 3 --> return user 2, 3, 4

startIndex = 7, count = 3 --> return user 5, 6, 7

startIndex = 10, count = 3 --> return user 8

Expected behavior:
startIndex = 1, count = 3 --> return user 1, 2, 3
startIndex = 4, count = 3 --> return user 4, 5, 6
startIndex = 1, count = 3 --> return user 7, 8
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.11.0-Beta 3 snapshot
OS: Linux
Database: H2
Userstore: LDAP

The issue is not reproducible with 5.11.0-beta5 pack hence closing the issue.


Key and Value reverse at have default values.

In GitLab by @wknet123 on Sep 21, 2017, 17:26

In GitLab by @liyanq528 on Nov 8, 2019, 07:37
fixed by pull request #403

In GitLab by @sokril on Nov 8, 2019, 08:11
closed

In GitLab by @sokril on Nov 8, 2019, 08:11
assigned to @liyanq528


Is there a debug mode for FGMachine and FGLab?

Howdy. I think I've got things set up properly but my jobs keep dying immediately after launch. Is there a debug mode I can enable? What about log files? Thanks much and apologies if I've missed obvious answers to these questions!
Cheers,
Yannick

There's no debug mode or log files, but for FGLab/FGMachine you can tee stdout and stderr to save the outputs into a log file. This can help diagnose what's going, but it seems like you would want to do debugging/logging with the jobs you are running first.


exiv2: fix CVE-2019-20421

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/78760
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Nitpick: 0ebeec91.


musicRating.10s.sh doesn't work if the script path contains a space?

Here's the error I get when I click on the musicRating bitbat:
Your script path /Users/***/Library/Application Support/BitBar plugins/musicRating.10s.sh has a space in it, which BitBar does not support Play/Pause/Next/Previous buttons will not work.
It does work when I move it to something like /Users/***/Desktop/BitBarPlugins
But this seems like it should be an easy fix to allow us to keep it in a folder with a space?

This will be fixed as part of the rewrite - see #607


Ability to take off mods from traders weapons and sell them after

General information:
Issue is for:
SPT-AKI 3.5.8 and earlier
Expected result:
After giving us an error that we cannot place items in traders slots, should return us back to main menu and remove any non-existing mods from our stash
Actual result:
Nothing happened and we are being let through to do our trickery
Description
This lets you sell mods from the weapons traders are selling or bartering, letting you take off almost every mod although it should've been fixed. Tested multiple times on previous versions of SPT-AKI 3.5.2 and the latest version without any mods and clean profile.
How to reproduce:
Notice that some of the steps are unnecessary under some unknown to me circumstances. But this is the one of quite a few ways to gather mods.

 Too bad! Click "Ok" and head back to main menu while dismissing our weapon preset
Get to post raid menu where you insure your items
Click on "Character" and you should have everything in your sorting table!
Dump all of the mods from sorting table into your equipped backpack
Get back into post-raid menu and start the raid
After getting into raid, extract and return to your stash
Now you're free to sell everything

Log files:
Server: Included as attachment
BepinEx: Included as attachment
Client: Included as attachment
Profile which was used:
https://codepaste.sp-tarkov.com/?eac28891ecc1a5fc#7iWj7hSvGfHACGex2rxuaQ8ik2RfoPFDPqXEs5DBJ5av
Media:
Here's a part of a whole demonstration on how it looks like when reproducing:

Attachments

server-2023-06-30-14.log (78 KiB)
BepInEx_LogOutput.log (37 KiB)
2023.06.30_9-04-53_<IP_ADDRESS>.23399 errors.log (54 KiB)

Originally written by Ghost

I'm able to reproduce, for some reason spt has the removed items move into the sorting container. Will work on a fix and upload a testing version soon.

Originally written by chomp

Let me know when the hotfix is live!

Originally written by Ghost

Fix is up: https://dev.sp-tarkov.com/attachments/e4cbd2a9-f1f7-4b96-b2b7-95696c6c803f

Originally written by chomp

Thanks for the fix, we can close this now

Originally written by Ghost


⚠ Fetchers has degraded performance

In d8d32dd, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 338 ms

Resolved: Fetchers performance has improved in e8ffb6c.


Change initial card state button to use "Find Out More"

We've been back and forth about this button. Looking at the latest UX review, this needs to be changed but it could be done in a separate issue.
Change the blue button text

Currently, the idea was to change it to “Find Out More,” with screen reader text saying “Find out more about X”
One other suggestion from the DUX team is “More Details” with screen reader text saying “More X Details”
Overall, this makes for more succinct button text

We need to test how the screenreader reads the content.
Originally posted by @jonespm in https://github.com/tl-its-umich-edu/canvas-app-explorer/pull/143#discussion_r854322526

I think the exact solution to use here is still under discussion. The latest feedback from Jeff as part of reviewing #158 was
"Need to 'lightly' label the tiny drop-down arrow in the lower right corner. Smaller text that removes ambiguity as to what that arrow does - 'More Info'? 'Tool Details'?" Currently the aria-label says "Learn More" and "Close Learn More".


Update pubspec.yaml

update the repository field

@osa1 - It doesn't look like I have permission to merge PRs here (which is fine, but if this lgtm you'll need to do the merge).


fix: Upgrade tf for testing

To address this problem: https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/622#issuecomment-888879621
Upgrading our tf version for testing!

@alldoami I couldn't clone your branch, I upgraded locally and figured it out  to fix the remaining failing tests:
For SCIM integration test failures:

Somehow because of the change in the behavior of datasources in 0.13 and the previous failed tests the role AAD_PROVISIONER was never destroyed. It should be dropped in the Acceptance Tests Snowflake Account manually. The reason it's not a random role name is because snowflake only expects a set of roles with a specific name

For the current datasources the behavior has changed with 0.13 so to pass these tests the direct dependency should be added:

materialized_views_acceptance_test.go => Add depends_on = [snowflake_materialized_view.v] in the data block
schemas_acceptance_test.go => Add depends_on = [snowflake_schema.s] in the data block
tables_acceptance_test.go => Add depends_on = [snowflake_table.t] in the data block
views_acceptance_test.go => Add depends_on = [snowflake_view.v] in the data block
system_generate_scim_access_token_acceptance_test.go => Add depends_on = [snowflake_scim_integration.azured] in the data block


Cannot use cds-icon with direction inside an angular button with .btn style

Describe the bug
I tried using an icon to use cds-icon but then the direction is not working when inside a button. Whatever I use the icon direction is not changed. It seems you cannot use directions when inside a button. If I move the icon outside the button, then the direction works. Using 5.1.1
How to reproduce
<button class="btn">
    <cds-icon shape="angle" direction="down"></cds-icon>
</button>

Expected behavior
The direction to work
Versions
Clarity project:

[x] Clarity Core
[x] Clarity Angular/UI

Clarity version:

[ ] v3.x
[ ] v4.x
[x] v5.x

Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
Angular 11
Additional notes
You cannot have cds-icon inside a button as this css has priority:
.btn-group>.btn cds-icon, .btn-group>.btn clr-icon, .btn cds-icon, .btn clr-icon {
    transform: translate3d(0,-.1rem,0);
}

over:
:host([direction="down"]) {
    transform: rotate(180deg);
}

In v4 the css was different and had priority (higher specificity):
clr-icon[dir=down] svg, clr-icon[shape$=" down"] svg {
    transform: rotate(180deg);
}

The 'flip' property has the same issue and also doesn't work when cds-icon is inside a button.

@rbirkgit
Thanks for reporting this issue! There is a PR out for it now.

Great!


touchup: increase edge label width for layout

Could use the average-width to try and balance using too much space vs using too little space, but it doesn't seem like a big deal to use too much space, whereas labels still overlapping basically forfeits a lot of the value of trying to avoid overlap.
Related #569
Description of changes

Additional context

Looks better imo and extra space doesn't seem bad - here are some before/after pics:
climate-change

cars-going-too-fast


Shopify integration

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #305
Test URLs:

Before: https://main--moleculardevices--hlxsites.hlx.page/products/assay-kits/igg-quantification-assays/valitatiter#ordering-options

After: https://shopify-integration--moleculardevices--hlxsites.hlx.page/products/assay-kits/igg-quantification-assays/valitatiter#ordering-options

Before: https://main--moleculardevices--hlxsites.hlx.page/products/assay-kits/gpcrs/catchpoint-cgmp-fluorescent-assay-kit#ordering-options

After: https://shopify-integration--moleculardevices--hlxsites.hlx.page/products/assay-kits/gpcrs/catchpoint-cgmp-fluorescent-assay-kit#ordering-options

Before: https://main--moleculardevices--hlxsites.hlx.page/products/assay-kits/igg-quantification-assays/clonedetect#ordering-options

After: https://shopify-integration--moleculardevices--hlxsites.hlx.page/products/assay-kits/igg-quantification-assays/clonedetect#ordering-options

Note: As confirmed via Slack by @kapildhiman: Store feature will only work in subdomains of http://moleculardevices.com

Hi @lydiapuric  can't see add to cart button option in the order tab. I am checking in US zone.


Enable using directive IntelliSense auto-completion.

Allow identical @using directives in the primary document. This means that if a user types @using System twice in the primary document (i.e. Index.cshtml) then we'll generate that using statement twice; this enables proper C# IntelliSense to light up on both using statements and allows auto-completion to work because there's no more magical distinction logic for Razor code that is in the current document.
Prior to this change if you had two identical using statements in the same document one would be in no-mans land mapped to nothing (not C#, not HTML) and the other would be mapped to C#; the second a user differentiated the two statements (i.e. adding a .) we'd distinctify the using statements resulting in an invalid completion.
Updated integration test to reflect new using ordering.
Added new integration test showing how using directives are not de-duplicated in the primary document.

Most controversial part of this PR:

This PR has an end-user impact where they will now receive the normal C# warning about having duplicate using. I treated this prior behavior more as a bug because we threw away the first using directive instance which impacted editing and in general was a silly thing to correct for the user.

#1255

Looks good. Should probably add a code gen test to show what error/warning gets generated.

Done, added using directive integration test. Only added an integration test to latest Mvc extensions because it's really just testing the compilation aspect of our new Razor feature.