Set SDK version for perf. counters telemetry.

Fix naming for app % Processor Time.
Set SDK version for Azure Web App counters telemetry.

Tweak and :shipit:


Added possibility to set debug and verbose mode using an environment variable

Added possibility to set debug and verbose mode using an environment variable solving #54

Coverage remained the same at 100.0% when pulling 5eba00ad049d230dade5c5c30ac0650eb99becaf on phawrylak:feature/54-environment-variables into 90a5fceb679d9543b181eec555ba28fd907c3195 on SharePoint:dev.

Nice @phawrylak!

Closing due to inactivity


zsh tab completion

As a developer, I want to have zsh tab completion so that I don’t need to lookup options and available commands as I type
NOTE: This can follow the current oc completions command as an example.
Tasks:
Add issues for completion for missing commands
Subtask of #163

See: https://github.com/redhat-developer/ocdev/issues/163 bash + zsh completion has been added :+1:


Migrate assert output to log buffer

The new code for the assert output may want to use %li instead of %lu since the builtin fallback printf implementation doesn't support %u. The introduced limitation seems reasonable given this page:
https://en.cppreference.com/w/c/preprocessor/line


Disable promise.loading?

I want to be able to disable the loading state of a promise, but passing false as its value doesn't seem to work - the loading toast is still shown.
toast.promise(myPromise, {
  loading: false,
  success: 'Success`,
  error: 'Error'
});

How can I disable the loading state?
thx

Same applies to the success and error states actually 😏

Seems unnecessary since you can try and catch the promise and call toast based on it

Well of course (and that is what I am doing), but if that's the general way of thinking, then you could argue that toast.promise() is also unnecessary 😏

Well of course (and that is what I am doing), but if that's the general way of thinking, then you could argue that toast.promise() is also unnecessary 😏

Not really, the whole idea of toast.promise is that it modifies the current promise to some new state after the loading is complete. It's a shortcut to getting a toast id and manually modifying it. So it's pretty useful. Using a try and catch for your case is simple enough and doesn't add any complexity to the code

Well of course (and that is what I am doing), but if that's the general way of thinking, then you could argue that toast.promise() is also unnecessary 😏

Out of curiosity - what's your use case for a promise toasting without a loading state?


[Feature]: Ability to set settings, like OpenAI API key, on a per project basis

Feature Request
Basically, I'd like to split personal & work settings.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Gotcha, yeah I don't want to store it in the project file, but it could be stored in the UI and assocated with a project file... somehow.

Something like profiles maybe? Profile A -> associated with Projects 1, 2, 3. Profile B -> associated with Projects 4,5,6.


[crashtracker] Send pid to the receiver

What does this PR do?
Sends the PID to the receiver from the crashing process
Motivation
Currently, we use getppid, which only works because the receiver is the child of the crashing process.  If we want to have a sidecar receiver, we'll need to know the actual pid.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
Attention: Patch coverage is 3.70370% with 26 lines in your changes missing coverage. Please review.

Project coverage is 69.58%. Comparing base (718e036) to head (3be83ab).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #483      +/-   ##
==========================================
- Coverage   69.64%   69.58%   -0.07%
==========================================
  Files         199      199
  Lines       26634    26659      +25
==========================================
+ Hits        18549    18550       +1
- Misses       8085     8109      +24

Components
Coverage Δ

crashtracker
17.11% <3.70%> (-0.29%)
:arrow_down:

datadog-alloc
98.76% <ø> (ø)

data-pipeline
51.30% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
85.97% <ø> (ø)

ddcommon-ffi
74.15% <ø> (ø)

ddtelemetry
56.11% <ø> (ø)

ipc
84.61% <ø> (ø)

profiling
79.14% <ø> (ø)

profiling-ffi
59.53% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
36.28% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
54.98% <ø> (ø)

trace-mini-agent
69.36% <ø> (ø)

trace-normalization
97.79% <ø> (ø)

trace-obfuscation
95.74% <ø> (ø)

trace-protobuf
24.52% <ø> (ø)

trace-utils
90.80% <ø> (ø)


[TC_AUTHOR_SUMAC_2] Course Data Researchers unable to log into Superset

Users with these roles should be able to login to Superset and see their course data: Course Admin, Course Staff, Limited Staff, Course Data Researcher
This works for all of these roles except for Course Data Researcher -- Superset doesn't allow login for this user type.
Note for testing: if you're changing a user's roles, you'll need to log them out completely from Open edX and log back in to fully test the role change.

@pomegranited - Thank you for catching! After chatting with Sara and Brian about this, I think this is actually OK for the time being. We'll see if the community ends up needing broader access for the role, but for this release we've decided to err on the side of restricting this user's access to embedded dashboards only for now. I can add a note to the testing spreadsheet, so that I can remember to update the wording on this test for future releases!


3.x compatible

Basic updates to run plugin with Mautic 3.x

Is this PR ready for testing @indorock?

Closing this in favor of bringing it up to date for Mautic 4


Day310

Resolves #633.

Pull Request Test Coverage Report for Build 1182

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1188:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

Pull Request Test Coverage Report for Build 1190

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1188:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


[fuzz] Refactored tcp health checker impl test

Signed-off-by: Zach Reyes<EMAIL_ADDRESS>Commit Message: Refactored tcp health checker impl test
Additional Description: For use in fuzzing
Risk Level: Low
Testing:
Docs Changes:
Release Notes:

/assign @asraa


VimTex Inverse Search

Hi, I found your repo by googling and was trying to use your VimTex settings.
After setting the SumatraPDF Inverse Search, when using it, I got:
Error detected while processing command line:
E492: Not an editor command: PackerLoad vimtex
E492: Not an editor command: VimtexInverseSearch 93 'PATH_TO_TEX_FILE\test.tex'

Are you using the settings under Windows?

It works correctly on my end.
Are you using packer.nvim? The errors seem to suggest packer.nvim and vimtex is not loaded or is not present.
cmd /c start /min nvim --headless -c "PackerLoad vimtex" -c "VimtexInverseSearch %l '%f'"
-c "PackerLoad vimtex" is only necessary if you are lazy loading vimtex using packer. If not, cmd /c start /min nvim --headless -c "VimtexInverseSearch %l '%f'" should work.

I'm using Packer through the distribution NvChad.
I can do :PackerLoad vimtex in neovim.
But if I run cmd /c start /min nvim --headless -c "PackerLoad vimtex" in the cmd, it will give me the above error.

I think NvChad lazy loads packer as well, hence the error.

Yeah, I mean, even doing cmd /c start /min nvim --headless -c "PackerLoad vimtex" is wrong... It should work even if Packer is lazy loaded?

No it won't work, packer,nvim will be loaded on VimEnter event, which does not happen with --headless iirc.
You can try init.lua try removing this line in your config, to always load packer. It should work then.

I think NvChad lazy loads packer as well, hence the error.

I misunderstood this. Now I see, since Packer is also lazy loaded, the command will not work...
I'll try your suggestions. Thank you!

https://github.com/NvChad/NvChad/issues/841
Add an issue here. If commenting that line, it will be revoked everytime the NvChad is updated.

cmd /c start /min nvim --headless -c "packadd packer.nvim" -c "PackerLoad vimtex" -c "VimtexInverseSearch %l '%f'"

Does this work by any chance?

Nope.
even cmd /c start /min nvim --headless -c "packadd packer.nvim" -c "PackerLoad vimtex" is not working.

Solution in https://github.com/NvChad/NvChad/issues/841, closing.


10 ** 10 is long in python 2

Fix #634
I have tested it on a windows machine and it works, of course.

Codecov Report

Merging #635 into master will increase coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #635      +/-   ##
==========================================
+ Coverage   71.55%   71.56%   +<.01%
==========================================
  Files         135      135
  Lines       12753    12753
==========================================
+ Hits         9126     9127       +1
+ Misses       3627     3626       -1

Impacted Files
Coverage Δ

prompt_toolkit/layout/menus.py
30.88% <ø> (ø)
:arrow_up:

prompt_toolkit/layout/controls.py
76.43% <0%> (ø)
:arrow_up:

prompt_toolkit/layout/containers.py
64.87% <100%> (ø)
:arrow_up:

prompt_toolkit/eventloop/async_generator.py
85.07% <0%> (+1.49%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks, @randy3k!


Bug : Standardize Promise Handling

standardize Promise Handling
await sgMail
      .send(message)
      .then((response) => console.log("Email sent!"))
      .catch((error) => console.log(error.message))

    res.render("result", { pos: p, eng: e, mea: m, rel: r, acc: a

In our codebase, there is a mix of using await and then/catch for handling promises. We need to standardize the approach to improve code consistency and maintainability.
Plan:

[ ] Removing promise then/catch
[ ] Adding ' try/catch` blocks for error handling

I am excited to work on this @Aryainguz  Can you assign me this for SWOC24?

Great observation and thought @mathanraj0601 go ahead and feel free to reach out for any help!

That's great @Aryainguz

Hey @Aryainguz  🌟 I've submitted a PR for the task mentioned . While diving into the issue, I spotted some opportunities to enhance the code for better readability and error handling. So, I've create  another issue or those improvements.
Could you kindly assign me to the linked issue (#29 ) ? I'm eager to kickstart the work and contribute to the project!


How do I get a prediction?

How do I get a prediction for an image with the config and weight data found in the README.md

Check out https://github.com/braun-steven/DAFNe/blob/b13912041a263904cf26ca5f3468c6bc64ce800c/tools/demo/demo.py


False-Positive: dotnet: System.Texts.Encodings.Web

PURL of wrongly matched component
<EMAIL_ADDRESS>Depscan findings
Traceback (most recent call last):
File "depscan\cli.py", line 1086, in
File "depscan\cli.py", line 872, in main
File "depscan\lib\license.py", line 53, in bulk_lookup
TypeError: 'NoneType' object is not iterable
[26600] Failed to execute script 'cli' due to unhandled exception!
It did find the following CVE's:
CVE-2023-36049
CVE-2024-21319
CVE-2023-36558
CVE-2024-0057
CVE-2024-0056

This can be reproduces by creating a .csproj file with the following contents and then running depscan:
<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">   <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />   <PropertyGroup>     <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>     <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>     <ProjectGuid>{10499679-6863-4C9A-A6DE-D4A41AD61A63}</ProjectGuid>     <OutputType>WinExe</OutputType>     <RootNamespace>test4</RootNamespace>     <AssemblyName>test4</AssemblyName>     <TargetFrameworkVersion>v4.7.2</TargetFrameworkVersion>     <FileAlignment>512</FileAlignment>     <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>     <Deterministic>true</Deterministic>   </PropertyGroup>   <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">     <PlatformTarget>AnyCPU</PlatformTarget>     <DebugSymbols>true</DebugSymbols>     <DebugType>full</DebugType>     <Optimize>false</Optimize>     <OutputPath>bin\Debug\</OutputPath>     <DefineConstants>DEBUG;TRACE</DefineConstants>     <ErrorReport>prompt</ErrorReport>     <WarningLevel>4</WarningLevel>   </PropertyGroup>   <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">     <PlatformTarget>AnyCPU</PlatformTarget>     <DebugType>pdbonly</DebugType>     <Optimize>true</Optimize>     <OutputPath>bin\Release\</OutputPath>     <DefineConstants>TRACE</DefineConstants>     <ErrorReport>prompt</ErrorReport>     <WarningLevel>4</WarningLevel>   </PropertyGroup>   <ItemGroup>     <Reference Include="System" />     <Reference Include="System.Core" />     <Reference Include="System.Numerics" />     <Reference Include="System.Text.Encodings.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51, processorArchitecture=MSIL">       <SpecificVersion>False</SpecificVersion>       <HintPath>M:\WinTree versies\LB_NET\LatestBuild\System.Text.Encodings.Web.dll</HintPath>     </Reference>     <Reference Include="System.Xml.Linq" />     <Reference Include="System.Data.DataSetExtensions" />     <Reference Include="Microsoft.CSharp" />     <Reference Include="System.Data" />     <Reference Include="System.Deployment" />     <Reference Include="System.Drawing" />     <Reference Include="System.Net.Http" />     <Reference Include="System.Windows.Forms" />     <Reference Include="System.Xml" />   </ItemGroup>   <ItemGroup>     <Compile Include="Form1.cs">       <SubType>Form</SubType>     </Compile>     <Compile Include="Form1.Designer.cs">       <DependentUpon>Form1.cs</DependentUpon>     </Compile>     <Compile Include="Program.cs" />     <Compile Include="Properties\AssemblyInfo.cs" />     <EmbeddedResource Include="Properties\Resources.resx">       <Generator>ResXFileCodeGenerator</Generator>       <LastGenOutput>Resources.Designer.cs</LastGenOutput>       <SubType>Designer</SubType>     </EmbeddedResource>     <Compile Include="Properties\Resources.Designer.cs">       <AutoGen>True</AutoGen>       <DependentUpon>Resources.resx</DependentUpon>     </Compile>     <None Include="Properties\Settings.settings">       <Generator>SettingsSingleFileGenerator</Generator>       <LastGenOutput>Settings.Designer.cs</LastGenOutput>     </None>     <Compile Include="Properties\Settings.Designer.cs">       <AutoGen>True</AutoGen>       <DependentUpon>Settings.settings</DependentUpon>       <DesignTimeSharedInput>True</DesignTimeSharedInput>     </Compile>   </ItemGroup>   <ItemGroup>     <None Include="App.config" />   </ItemGroup>   <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /> </Project>
If you need anymore information please do not hesitate to ask

@Geertkok1, do you get the findings without the license check? You can try by unsetting FETCH_LICENSE environment variable.

With 5.3.5, I don't get any results. Could you confirm, if this is a false negative (where you are expecting some CVEs to be reported) or a false positive (where incorrect CVEs were reported)
Could you try with the latest and using --purl argument as shown and report?
python depscan/cli.py --purl<EMAIL_ADDRESS>--reports-dir /tmp/reports

██████╗ ███████╗██████╗ ███████╗ ██████╗ █████╗ ███╗   ██╗
██╔══██╗██╔════╝██╔══██╗██╔════╝██╔════╝██╔══██╗████╗  ██║
██║  ██║█████╗  ██████╔╝███████╗██║     ███████║██╔██╗ ██║
██║  ██║██╔══╝  ██╔═══╝ ╚════██║██║     ██╔══██║██║╚██╗██║
██████╔╝███████╗██║     ███████║╚██████╗██║  ██║██║ ╚████║
╚═════╝ ╚══════╝╚═╝     ╚══════╝ ╚═════╝╚═╝  ╚═╝╚═╝  ╚═══╝

INFO [2024-05-31 10:30:14,570] About to download the vulnerability database from ghcr.io/appthreat/vdbgz:v5. This might take a while ...
INFO [2024-05-31 10:32:16,107] Performing regular scan for /Volumes/Work/owasp/dep-scan using plugin nuget
╭────────────── Recommendation ───────────────╮
│ ✅ No package requires immediate attention. │
╰─────────────────────────────────────────────╯

With 5.3.5, I don't get any results. Could you confirm, if this is a false negative (where you are expecting some CVEs to be reported) or a false positive (where incorrect CVEs were reported)
Could you try with the latest and using --purl argument as shown and report?
python depscan/cli.py --purl<EMAIL_ADDRESS>--reports-dir /tmp/reports

██████╗ ███████╗██████╗ ███████╗ ██████╗ █████╗ ███╗   ██╗
██╔══██╗██╔════╝██╔══██╗██╔════╝██╔════╝██╔══██╗████╗  ██║
██║  ██║█████╗  ██████╔╝███████╗██║     ███████║██╔██╗ ██║
██║  ██║██╔══╝  ██╔═══╝ ╚════██║██║     ██╔══██║██║╚██╗██║
██████╔╝███████╗██║     ███████║╚██████╗██║  ██║██║ ╚████║
╚═════╝ ╚══════╝╚═╝     ╚══════╝ ╚═════╝╚═╝  ╚═╝╚═╝  ╚═══╝

INFO [2024-05-31 10:30:14,570] About to download the vulnerability database from ghcr.io/appthreat/vdbgz:v5. This might take a while ...
INFO [2024-05-31 10:32:16,107] Performing regular scan for /Volumes/Work/owasp/dep-scan using plugin nuget
╭────────────── Recommendation ───────────────╮
│ ✅ No package requires immediate attention. │
╰─────────────────────────────────────────────╯

Hello @prabhu ,
I can confirm that is was a false-positive. The dotnet team confirmed that the CVE's were not applicable to this package.
We were using a depscan binary but it seems that those are note updated anymore(If I could make a suggestion: Make a note of that in the readme of this project) Because of that we did not know that we were using a old version of depscan. If I use the most recent version it works without issue and does not detect the CVE.
So this problem is solved by updating depscan.

Thank you for confirming. Yes, the single application binaries are no longer available. Best to use the container image or the pypi package.


feat(front): update strapi 3.1.0 to 3.1.3

Hi.
I upgrade strapi to their latest version: at least 3.1.3. I have issues with other repositories I can't reproduce with yours.
Enjoy :)

Thanks @Kazdan1994 for this.


Stuck at low clocks randomly with RX580 in Asus GL702ZC

Hi,
With ROCm 1.8 my laptop randomly loses ability to change to higher p-states, requiring shutting down the machine completely and turning it back on. Hot reboots do not work.
The amdgpu drivers in kernel ubuntu kernel 4.13 work fine.
Here is the dmesg output when trying to run a OpenCL application:
[ 4826.610906] amdgpu: [powerplay] Failed to notify smc display settings! [ 5212.480671] amdgpu: [powerplay] Failed to notify smc display settings! [ 5822.865839] amdgpu: [powerplay] Failed to notify smc display settings! [ 6194.342332] amdgpu: [powerplay] Failed to notify smc display settings! [ 6804.910781] amdgpu: [powerplay] Failed to notify smc display settings! [26414.119861] amdgpu: [powerplay] Failed to start pm status log! [26414.985049] amdgpu: [powerplay] Failed to start pm status log! [26420.344579] amdgpu: [powerplay] Failed to start pm status log! [26421.024833] amdgpu: [powerplay] Failed to start pm status log!

Hi @nioroso-x3
Do you still see the issue in ROCm 2.0?


Would nix-eval-jobs work well for this plugin?

I just found out about nix-eval-jobs, which is a streaming evaluator. Do you suppose this plugin could be adapted to work with it?

Yea, this looks really cool! Definitely worth a look I think.


Fix #75


Improved UI, Added Scroll to Top Button and Enhance User Navigation

Pull Request Format
PR Title Improved UI, Added Scroll to Top Button and Enhance User Navigation
Issue #98 :
Type of PR

Add X in the box to specify the improvement type.
[X] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): ___________

Description
1 Made some minor css changes
2 Implemented a scroll-to-top arrow button for better navigation throughout the page.
3 The button appears when the user scrolls down and allows smooth scrolling back to the top.
4 Adjusted layout to ensure compatibility with existing design and responsiveness.
5  Updated style.css and script.js to integrate the new functionality without affecting other components of the page.
Checklist

Add X in the box to specify.
[X] I have performed a self-review of my code.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional Context
[Provide any additional context about the changes, such as specific challenges you faced or decisions you made. This can help reviewers understand the rationale behind your changes.]
Thank you for reviewing my pull request!

@swaraj-das thank you for valuable feedback. and also can you please add gssoc and hacktoberfest label
thank you


Break up large function

Reduce the size of generate_gh_matrix by breaking it up just a little.
Add some tests for the plugin to cover changes and some other misses.

minimal runtime changes, mostly tests, yolo, merging.


First step towards async: locks and atomics

This doesn't add any async functionality yet but does make the library threadsafe (AFAIK) as long as you don't use any LibPQ.libpq_c functions directly.
Note that almost all libpq functions return C_NULL/0/"" on a closed connection or cleared result or null pointer, so there shouldn't be any segfaults in those situations, just nonsense results.

I'm not really awake enough to be reviewing for race conditions, as I said.


Remove port 80 from network requirements page

https://docs.resin.io/reference/OS/network/2.x/#network-requirements
This applied to pubnub (which we no longer user) and for quite some time now even pubnub was working over https, so port 80 was not needed

Duplicate of https://github.com/resin-io/docs/issues/814


[Vuetify] Multiple instances of Vue detected

Version
1.0.0-beta.29
Reproduction link
https://github.com/begueradj/bugs/tree/master/nuxtVuetifyJest
Steps to reproduce
const localVue = createLocalVue()
localVue.use(Vuetify)

What is expected?
I expect my test to pass without any error or warning messages.
What is actually happening?
The test passes but I receive this nasty red message:
^[[999D  console.error node_modules/vuetify/dist/vuetify.js:25038
    [Vuetify] Multiple instances of Vue detected
    See https://github.com/vuetifyjs/vuetify/issues/4068

    If you're seeing "$attrs is readonly", it's caused by this

The documentation clearly recommends to use localVue.use(Vuetify) so please do not suggest me to Vue.use(Vuetify) unless  if you are a superman with valid reasons able to convince me.

I am using Jest   Nuxt   Vuetify. You can try my github repository provided in the above link.
Billal Begueradj.

Please see this comment in Vuetify—https://github.com/vuetifyjs/vuetify/issues/4068#issuecomment-422406319

I tried what that comments suggests:
Vue.use(Vuetify)
const localVue = createLocalVue()
localVue.use(Vuetify)

Still getting the exact same error.
Thank you @eddyerburgh

I had the same error, and for me, it was just as it says:
vuetify.js:53625 [Vuetify] Multiple instances of Vue detected
See https://github.com/vuetifyjs/vuetify/issues/4068
If you're seeing "$attrs is readonly", it's caused by this
I searched in my components code and realized I have vuetify called and vue inside components, and that was causing the error what I did is took those lines out and now I have only calling the vue from my vue.js file and the error was gone.
Good Luck 👍

https://github.com/vuetifyjs/vuetify/issues/4964#issuecomment-747066049

提醒各位开发者：如果你的项目在开发模式下没问题，但是在生产模式下产生问题，请检查下你的构建器版本，
在vite5 + vue@^2 +vuetify@v2-stable的搭配下，项目在生产和开发模式下都可以正常运行，
但是升级到 vite6 之后，开发模式正常，但是生产模式就会出现该问题，在vite6稳定之前，最好不要去轻易尝试


Update Ingress from extension to networking

Signed-off-by: Maysun J Faisal<EMAIL_ADDRESS>Please specify the area for this PR
registry deploy
What does does this PR do / why we need it:
Extension Ingress has been deprecated and needs to be updated to networking ingress
Before the update:
$ helm install devfile-registry ./deploy/chart/devfile-registry --set global.ingress.domain="<IP_ADDRESS>.nip.io" --set devfileIndex.image=maysunfaisal/devfile-index --set devfileIndex.tag=latest
W0930 15:05:47.476253   89145 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W0930 15:05:48.593295   89145 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp <IP_ADDRESS>:443: connect: connection refused

$ helm install devfile-registry ./deploy/chart/devfile-registry --set global.ingress.domain="<IP_ADDRESS>.nip.io" --set devfileIndex.image=maysunfaisal/devfile-index --set devfileIndex.tag=latest
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Ingress" in version "extensions/v1beta1"

After the update:
$ helm install devfile-registry ./deploy/chart/devfile-registry --set global.ingress.domain="<IP_ADDRESS>.nip.io" --set devfileIndex.image=maysunfaisal/devfile-index --set devfileIndex.tag=latest
NAME: devfile-registry
LAST DEPLOYED: Fri Oct  1 13:06:02 2021
NAMESPACE: maysun
STATUS: deployed
REVISION: 1
TEST SUITE: None

NAME                                         CLASS     HOSTS                                         ADDRESS        PORTS     AGE
ingress.networking.k8s.io/devfile-registry   <none>    devfile-registry-maysun.<IP_ADDRESS>.nip.io   <IP_ADDRESS>   80        75s

$ curl http://devfile-registry-maysun.<IP_ADDRESS>.nip.io/health
{"message":"the server is up and running"}

Which issue(s) this PR fixes:
N/A
PR acceptance criteria:

[ ] Test (WIP)

[ ] Documentation (WIP)

How to test changes / Special notes to the reviewer:
Use the chart 😄

@johnmcollier I'll update the operator as well FYI


Getting 400 Bad Request: Failed to validate Route Service Signature if I use 2 instances of go-router

I am using x509 header forward routing service. This service is working fine if I use one instance of go-router.
When I use 2 instances (for HA) of go-router with ELB & try to hit the app which is binded with above routing service after some time I am getting following error:
400 Bad Request: Failed to validate Route Service Signature
Due to this I am not able to use multiple instances of go-router.
Can you please help me on this.
Thanks in advance.

@lordcf - were you able to look at the Gorouter logs at /var/vcap/sys/log/gorouter/access.log and /var/vcap/sys/log/gorouter/gorouter.err.log on both the router VMs to confirm if it is the same router that throws the error.
You also mention that you get the error after sometime, does that mean it works and throws the error periodically?
Regards,
Shubha

I am running one script which continuously hitting the app. Which giving following output:
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World                                                 [31/1866]
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
Then I checked  gorouter.log for both router instances. Getting following logs on routers:
On router_z2/1 Getting following logs:
$tail -n 1000 -f /var/vcap/sys/log/gorouter/gorouter.log
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.3081446,"message":"signature-validation-failed[1974/1974]"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:51+0000] {"log_level":1,"timestamp":1523962731.3081582,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.9345953,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.2880185}}
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.9346254,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:51+0000] {"log_level":1,"timestamp":1523962731.9346368,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.1080248,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.4650784}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.1080523,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:52+0000] {"log_level":1,"timestamp":1523962732.1080642,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.6301277,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.9841387}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.630157,"message":"signature-validation-failed","source":"
vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:52+0000] {"log_level":1,"timestamp":1523962732.630168,"message":"status","source":"vcap.gorouter.proxy",
"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:53+0000] {"log_level":3,"timestamp":1523962733.0145087,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962527.3669732}}
[2018-04-17 10:58:53+0000] {"log_level":3,"timestamp":1523962733.0145411,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:53+0000] {"log_level":1,"timestamp":1523962733.014553,"message":"status","source":"vcap.gorouter.proxy",
"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
On router_z2/0 Getting following logs
$tail -n 1000 -f /var/vcap/sys/log/gorouter/gorouter.log
[2018-04-17 10:56:37+0000] {"log_level":1,"timestamp":1523962597.7871513,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:37+0000] {"log_level":1,"timestamp":1523962597.965601,"message":"route-service-response","source":"vcap.
gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.c
om:5000","status-code":400}}
[2018-04-17 10:56:38+0000] {"log_level":1,"timestamp":1523962598.492648,"message":"route-service-response","source":"vcap.
gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.c
om:5000","status-code":400}}
[2018-04-17 10:56:38+0000] {"log_level":1,"timestamp":1523962598.6675248,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:39+0000] {"log_level":1,"timestamp":1523962599.2959225,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:39+0000] {"log_level":1,"timestamp":1523962599.4766629,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:46+0000] {"log_level":1,"timestamp":1523962606.7415078,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:56:46+0000] {"log_level":1,"timestamp":1523962606.7416146,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:57:16+0000] {"log_level":1,"timestamp":1523962636.741596,"message":"start-pruning-routes","source":"vcap.go
router.registry","data":{}}
[2018-04-17 10:57:16+0000] {"log_level":1,"timestamp":1523962636.7416914,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:57:46+0000] {"log_level":1,"timestamp":1523962666.7415857,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:57:46+0000] {"log_level":1,"timestamp":1523962666.7417994,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:58:16+0000] {"log_level":1,"timestamp":1523962696.7416,"message":"start-pruning-routes","source":"vcap.goro
uter.registry","data":{}}
[2018-04-17 10:58:16+0000] {"log_level":1,"timestamp":1523962696.74176,"message":"finished-pruning-routes","source":"vcap.
gorouter.registry","data":{}}
[2018-04-17 10:58:46+0000] {"log_level":1,"timestamp":1523962726.7415729,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:58:46+0000] {"log_level":1,"timestamp":1523962726.7417629,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:59:16+0000] {"log_level":1,"timestamp":1523962756.7415736,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:59:16+0000] {"log_level":1,"timestamp":1523962756.7417715,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:59:46+0000] {"log_level":1,"timestamp":1523962786.7415724,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:59:46+0000] {"log_level":1,"timestamp":1523962786.741773,"message":"finished-pruning-routes","source":"vcap
.gorouter.registry","data":{}}

I am running one script which continuously hitting the app. Which giving following output:
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World                                                 [31/1866]
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World
683  Universal time: Tue 2018-04-17 10:57:12 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:13 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| Hello World
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
684  Universal time: Tue 2018-04-17 10:57:14 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:15 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| Hello World
685  Universal time: Tue 2018-04-17 10:57:16 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:16 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| Hello World
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
686  Universal time: Tue 2018-04-17 10:57:17 UTC ||| 400 Bad Request: Failed to validate Route Service Signature
**Then I checked  gorouter.log for both router instances. Getting following logs on routers:
On router_z2/1 Getting following logs:
$tail -n 1000 -f /var/vcap/sys/log/gorouter/gorouter.log
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.3081446,"message":"signature-validation-failed[1974/1974]"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:51+0000] {"log_level":1,"timestamp":1523962731.3081582,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.9345953,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.2880185}}
[2018-04-17 10:58:51+0000] {"log_level":3,"timestamp":1523962731.9346254,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:51+0000] {"log_level":1,"timestamp":1523962731.9346368,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.1080248,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.4650784}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.1080523,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:52+0000] {"log_level":1,"timestamp":1523962732.1080642,"message":"status","source":"vcap.gorouter.proxy"
,"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.6301277,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962526.9841387}}
[2018-04-17 10:58:52+0000] {"log_level":3,"timestamp":1523962732.630157,"message":"signature-validation-failed","source":"
vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:52+0000] {"log_level":1,"timestamp":1523962732.630168,"message":"status","source":"vcap.gorouter.proxy",
"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
[2018-04-17 10:58:53+0000] {"log_level":3,"timestamp":1523962733.0145087,"message":"proxy-route-service-timeout","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired","forwarded-url":"http://hello1.apps.cf.my-domain
ymotors.com/","request-time":1523962527.3669732}}
[2018-04-17 10:58:53+0000] {"log_level":3,"timestamp":1523962733.0145411,"message":"signature-validation-failed","source":
"vcap.gorouter.proxy","data":{"error":"route service request expired"}}
[2018-04-17 10:58:53+0000] {"log_level":1,"timestamp":1523962733.014553,"message":"status","source":"vcap.gorouter.proxy",
"data":{"body":"400 Bad Request: Failed to validate Route Service Signature"}}
On router_z2/0 Getting following logs
$tail -n 1000 -f /var/vcap/sys/log/gorouter/gorouter.log
[2018-04-17 10:56:37+0000] {"log_level":1,"timestamp":1523962597.7871513,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:37+0000] {"log_level":1,"timestamp":1523962597.965601,"message":"route-service-response","source":"vcap.
gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.c
om:5000","status-code":400}}
[2018-04-17 10:56:38+0000] {"log_level":1,"timestamp":1523962598.492648,"message":"route-service-response","source":"vcap.
gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.c
om:5000","status-code":400}}
[2018-04-17 10:56:38+0000] {"log_level":1,"timestamp":1523962598.6675248,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:39+0000] {"log_level":1,"timestamp":1523962599.2959225,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:39+0000] {"log_level":1,"timestamp":1523962599.4766629,"message":"route-service-response","source":"vcap
.gorouter.proxy","data":{"endpoint":"https://.eu-west-1.elb.amazonaws.
com:5000","status-code":400}}
[2018-04-17 10:56:46+0000] {"log_level":1,"timestamp":1523962606.7415078,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:56:46+0000] {"log_level":1,"timestamp":1523962606.7416146,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:57:16+0000] {"log_level":1,"timestamp":1523962636.741596,"message":"start-pruning-routes","source":"vcap.go
router.registry","data":{}}
[2018-04-17 10:57:16+0000] {"log_level":1,"timestamp":1523962636.7416914,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:57:46+0000] {"log_level":1,"timestamp":1523962666.7415857,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:57:46+0000] {"log_level":1,"timestamp":1523962666.7417994,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:58:16+0000] {"log_level":1,"timestamp":1523962696.7416,"message":"start-pruning-routes","source":"vcap.goro
uter.registry","data":{}}
[2018-04-17 10:58:16+0000] {"log_level":1,"timestamp":1523962696.74176,"message":"finished-pruning-routes","source":"vcap.
gorouter.registry","data":{}}
[2018-04-17 10:58:46+0000] {"log_level":1,"timestamp":1523962726.7415729,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:58:46+0000] {"log_level":1,"timestamp":1523962726.7417629,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:59:16+0000] {"log_level":1,"timestamp":1523962756.7415736,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:59:16+0000] {"log_level":1,"timestamp":1523962756.7417715,"message":"finished-pruning-routes","source":"vca
p.gorouter.registry","data":{}}
[2018-04-17 10:59:46+0000] {"log_level":1,"timestamp":1523962786.7415724,"message":"start-pruning-routes","source":"vcap.g
orouter.registry","data":{}}
[2018-04-17 10:59:46+0000] {"log_level":1,"timestamp":1523962786.741773,"message":"finished-pruning-routes","source":"vcap
.gorouter.registry","data":{}}
----------------------------------------------------------------------------------------------------------------**

When do it gives "proxy-route-service-timeout" error?

@cf-gitbot What should I do please help me.

Hi @lordcf,
We have documented timeout behavior here: https://docs.cloudfoundry.org/services/route-services.html#service-instance-responsibilities under Headers>Timeouts. Also look at the explanation for X-CF-Proxy-Signature under Headers.
The signature validation errors we are seeing in the logs seem to indicate that the Gorouter is unable to validate the X-Cf-Proxy-Signature header. This might happen if

The header contains the originally requested URL and a timestamp. When this header is present, the Gorouter will reject the request if the requested URL does not match that in the header, or if a timeout has expired.
If the route service forwards the request to a URL different from the originally requested one, and the URL resolves to a route for an application on Cloud Foundry, the route must not have a bound route service or the request will be rejected, as the requested URL will not match the one in the X-CF-Proxy-Signature header.

The concern here seems to be one Gorouter instance, and other Gorouter seems to be working as expected. One way of validating this, is to bosh ssh into the router instance that is working fine, and killing the gorouter process, such that all requests go through the Gorouter through which requests are failing, and we have less noise in the system. From looking at the logs, it seems like one gorouter is not receiving the response from the route service, Is there a reason this might be the case in your environment?
Please feel free to ping us also in #routing channel on Cloud Foundry Slack.

@shubhaat
I checked this. But it's not an issue with one gorouter instance. When I stopped process of gorouter A then gorouter B works fine and not giving any issue. Same when I do vice versa. But when I keen both goruter processes running I am facing the issue.
Please let me know what should I check.
Thanks in advance.

I got a root cause of this. Actually system time (UTC) was not same of both routers. There was 4 minutes difference between them. Due to which it was giving time out error when I use 2 routers simultaneously. For now I fixed this manually by making system time of one router similar to other one. And it's working fine.
But actually this should not happen. As we give ntp server in bosh-deployments.
I can see following servers on both router in /var/vcap/bosh/etc/ntpserver file:
0.pool.ntp.org 1.pool.ntp.org
Looks like these servers are not responding. due to which time is not synced with ntp.
Can you please suggest the ntp servers which will work

Those NTP servers are provided as an example, I believe. You probably should find out what ntp servers you can use on your infrastructure. You mentioned an ELB so I assume you're on AWS. Their NTP server is <IP_ADDRESS>  according to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html

It looks like your problem has resolved. We are closing due to age, but feel free to reopen if you still run into problems.


Updating documentation for nbclassic

Update readthedocs documentation WIP.
Work TBD:

[ ] Update homepage outline of documentation
[ ] Update development faq
[ ] Delete that documentation which is not applicable to nbclassic(?)

@RRosio Please confirm when you'd like me to review this PR.
As discussed, you could add a page/section which highlights things people migrating form notebook to nbclassic should know or care about;
For example, https://github.com/jupyter/nbclassic/issues/140 depends https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator/pull/141. Once https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator/pull/141 will be merged and released, users will need to run the following command to activate the extension
pip install jupyter_nbextensions_configurator
jupyter nbextension install --sys-prefix --py jupyter_nbextensions_configurator --overwrite
jupyter nbextension enable --sys-prefix --py jupyter_nbextensions_configurator
jupyter serverextension install --sys-prefix --py jupyter_nbextensions_configurator --overwrite
jupyter serverextension enable --sys-prefix --py jupyter_nbextensions_configurator

I did some reordering of sections here for readability and added a section for known issues. The Test Downstream job is failing but I opened another PR with a minimal change and it was still failing which leads me to think that the fail is not related to the changes in the PR.


immortalized legend ahri

Can you pls add 3 form of immortalized legend ahri separately?

Can you pls add 3 form of immortalized legend ahri separately?

maybe not. refer to https://github.com/hydy100/R3nzSkin/issues/7#issuecomment-2183859268

If you think it's fine, you can go ahead and close this issue again.

quick question i was wondering if it's doable to fix dawnbringer riven? iirc the server sends the assets or something so idk

Work perfectly, thank you man!


move framework service providers from delevoper space to framework space

service providers in app/ServiceProviders should be in lib/Framework/ServiceProviders
This change will (with other changes) allow us to move the framework base into a more-easily updated PHP package

Fixed with PR #385


chore: fix clippy warning

Minor fix for a clippy warning I've been seeing.

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

Project coverage is 77.95%. Comparing base (9c42903) to head (5773435).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2831   +/-   ##
=======================================
  Coverage   77.94%   77.95%
=======================================
  Files         229      229
  Lines       70147    70147
  Branches    70147    70147
=======================================
+ Hits        54679    54685    +6
+ Misses      12393    12385    -8
- Partials     3075     3077    +2

Flag
Coverage Δ

unittests
77.95% <100.00%> (+<0.01%)
:arrow_up:

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

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


Some questions about the rotation of kernels

Hello,
There are some questions that confused me for weeks and I cannot solve them on my own, hope you guys can help me:

how the kernel rotate over the sphere, in which direction? (by the way, is there any gif to see or understand that?)
How many times does the filter rotate?
I know that the output of s2convolution is a signal on SO(3), but why? how to visualize or explain that?

Thanks, a lot!


exposed clock noise functions

exposed clock noise functions for tudatpy

Hey, thanks for adding all this! If I understand correctly, this is to be used with this: https://github.com/tudat-team/tudat/tree/feature/clock_noise_models right?
I think this is also code that can be merged soon, but we need to resolve one thing: the proper inclusion/finding of FFTW3

Yes indeed (I sent you the messages on slack). Linking fftw3 was quite easy, it requires specifying the path to the library in cmake. Lethal it could be included as a necessary package in the environment.yalm? You know best On 11 Dec 2023, at 11:56, DominicDirkx @.***> wrote:
Hey, thanks for adding all this! If I understand correctly, this is to be used with this: https://github.com/tudat-team/tudat/tree/feature/clock_noise_models right?
I think this is also code that can be merged soon, but we need to resolve one thing: the proper inclusion/finding of FFTW3
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Implement block memory allocator

First real code for libcanard :)
I implemented the memory block allocator, or at least how I think it should behave. This is my first try at doing that kind of things so let me know if anything is wrong.

Great start, Antoine. :)
I didn't actually ran the code, so my input is based solely on eyeing the sources.
API functions
The design document explicitly lists the functions that shall be exposed to the library's user. We can go back and review them if necessary, although I don't think it is necessary - the defined function set covers all features of the library.
The problem I identified with this PR is that it exposes functions and data structures that are internal to the library through the library's header (namely, CanardPoolAllocatorBlock, CanardPoolAllocator, canardInitPoolAllocator, canardAllocateBlock, canardFreeBlock). They are supposed to be hidden, so as to not pollute the API.
On the other hand, if the internals are completely hidden from the user, the unit tests will have to gain access to them using some other ways. I can propose two solutions off the top of my head:

Include canard.c as a header into every source file with unit tests. There should be nothing wrong with this approach, although I realize that it's a bit unusual.
Create a second header file for library-internal definitions, like canard_internal.h, and put all of the internal type and macro definitions there. Define a macro for use instead of static for internal functions, say CANARD_INTERNAL, and set it to static for release builds, and empty value for testing builds.

I prefer the first solution because it's much simpler and much less intrusive.
Coding style
A few corrections:

Braces go on the new line.
Pointer star goes to the type name, not to the identifier: int* foo.
We have agreed to use C99, which means that we can write cleaner code: variables can be defined in the place of first use and declared const (example of the problem); we can use // comments instead of strictly /* */.

Declaring variables in the beginning of the block is generally a bad idea, because such style is prone to using variables uninitialized. There's a section dedicated to this problem in the style guide (MISRA goes into further detail here).

I am against including canard.c, because it will require linker-tweaking to avoid multiple definitions of the same symbol (one per inclusion). It could also hide problems such as missing headers in canard.c (if they are included in the test file before it). I prefer the canard_internals.h approach.
I will do the changes you suggest regarding style.

PR updated with your suggestions.

Nice.
Next time I'd suggest to either configure your IDE to handle formatting automatically (here's config for Eclipse: ftp://pkir.net/zubax_style_formatter.xml), or use uncrustify as described here. Currently there are still some inconsistencies in pointer stars and brace placement.
As for API - in order to enforce internal linkage, static must be placed in front of both definition and declaration, unless declaration comes after. So internal functions in canard.c should also be prepended with CANARD_INTERNAL.

Oh nice did not know about uncrustify, applied it :+1:
Also added static qualifier to declarations.


fix editor ruler color

Hello Sarah, great theme!
Just a tiny fix for those of us who use editor.rulers setting for keeping track of line lengths.
The ruler now uses the same blue as the indentation lines, instead of the standard grayish color.
Before:

After:

Thanks!

thank you!


The model web link has expired

The model connection has expired, can you re-upload the pre-trained model

The model connection has expired, can you re-upload the pre-trained model

Hi,
I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive.
What's the error reported when you downloaded it?

When I click on this link, an error will be reported
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月1日(星期天) 凌晨2:03
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
The model connection has expired, can you re-upload the pre-trained model
Hi,
I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive.
What's the error reported when you downloaded it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open.
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月1日(星期天) 凌晨2:03
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
The model connection has expired, can you re-upload the pre-trained model
Hi,
I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive.
What's the error reported when you downloaded it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open.
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

Hi,
The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via :
pip install --upgrade --no-cache-dir gdown.
If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem.

Thank you very much for your reply, I have solved the problem！！
Then, I have another question. You said in git that you only need 17ms to process a 4k image using a 3090 graphics card, but it takes me 8s under the same configuration. Moreover, if I process a 4000*8000 panorama, the memory will be exceeded. Have you MEET this problem, or do you have any better suggestions
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月3日(星期二) 中午1:57
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open.
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Hi,
The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via :
pip install --upgrade --no-cache-dir gdown.
If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Thank you very much for your reply, I have solved the problem！！ Then, I have another question. You said in git that you only need 17ms to process a 4k image using a 3090 graphics card, but it takes me 8s under the same configuration. Moreover, if I process a 40008000 panorama, the memory will be exceeded. Have you MEET this problem, or do you have any better suggestions
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 中午1:57 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open. … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Hi, The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via : pip install --upgrade --no-cache-dir gdown. If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.*>

No, I haven't meet this problem. How do you test it, through our code or other implementation?

I run your demo_test.py this program
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月3日(星期二) 下午3:16
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
Thank you very much for your reply, I have solved the problem！！ Then, I have another question. You said in git that you only need 17ms to process a 4k image using a 3090 graphics card, but it takes me 8s under the same configuration. Moreover, if I process a 40008000 panorama, the memory will be exceeded. Have you MEET this problem, or do you have any better suggestions
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 中午1:57 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open. … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Hi, The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via : pip install --upgrade --no-cache-dir gdown. If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.*>
No, I haven't meet this problem. How do you test it, through our code or other implementation?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I run your demo_test.py this program
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 下午3:16 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) Thank you very much for your reply, I have solved the problem！！ Then, I have another question. You said in git that you only need 17ms to process a 4k image using a 3090 graphics card, but it takes me 8s under the same configuration. Moreover, if I process a 40008000 panorama, the memory will be exceeded. Have you MEET this problem, or do you have any better suggestions … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 中午1:57 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open. … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Hi, The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via : pip install --upgrade --no-cache-dir gdown. If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> No, I haven't meet this problem. How do you test it, through our code or other implementation? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.**>

I guess you may just test one image and calculate the run time of the whole code processing, including model loading. We do statistics by testing 500 images and calculate the average time for model processing (see here).

Thanks, I'm trying it out, thanks for your reply
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月3日(星期二) 下午3:25
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
I run your demo_test.py this program
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 下午3:16 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) Thank you very much for your reply, I have solved the problem！！ Then, I have another question. You said in git that you only need 17ms to process a 4k image using a 3090 graphics card, but it takes me 8s under the same configuration. Moreover, if I process a 40008000 panorama, the memory will be exceeded. Have you MEET this problem, or do you have any better suggestions … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月3日(星期二) 中午1:57 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open. … ------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Hi, The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via : pip install --upgrade --no-cache-dir gdown. If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> No, I haven't meet this problem. How do you test it, through our code or other implementation? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.**>
I guess you may just test one image and calculate the run time of the whole code processing, including model loading. We do statistics by testing 500 images and calculate the average time for model processing (see here).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello, I am encountering this problem now. After the moiré removal operation, the color of the picture will change. What do you think is the cause of this problem?
------------------ 原始邮件 ------------------
发件人:                                                                                "CVMI-Lab/UHDM"                                                                                @.>;
发送时间: 2023年1月3日(星期二) 中午1:57
@.>;
<EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13)
When I use gdown to download, it will report such an error. I think it should be a problem that you don't have permission to open.
…
------------------ 原始邮件 ------------------ 发件人: "CVMI-Lab/UHDM" @.>; 发送时间: 2023年1月1日(星期天) 凌晨2:03 @.><EMAIL_ADDRESS>主题: Re: [CVMI-Lab/UHDM] The model web link has expired (Issue #13) The model connection has expired, can you re-upload the pre-trained model Hi, I have checked the checkpoint just now and found I can still download it via "gdown" in the bash script or mannully downloading from google drive. What's the error reported when you downloaded it? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Hi,
The problem seems to be from gdown side (see this issue). At this moment, I suggest you firstly upgrade the gdown via :
pip install --upgrade --no-cache-dir gdown.
If this cannot work, I suggest you download it directly from google drive. I will try to find a way to fix this problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

It is caused by the inconsistent color style in training pairs. For moire images, it contains not only moire artifact but also degraded color style. So the model has also learnt to modify the color style.


Future of the "inmemory" setup

I would like to discuss the future of the inmemory setup. Currently there seem to be two main differences between the two setups:

inmemory is using deployment instead of stateful set
inmemory is using emptyDir as a storage instead of PersistentVolumeClaim

Note: inmemory is actually not in memory as the name might siggest. It is still using disk but not persistent volume.
The problem from my perspective is that the inmemory setup is using significantly different setup from the stateful set and makes all changes more complicated. And its usability is currently anyway bad since it cannot for example scale up.
My suggestion would be to:

Remove the inmemory part completely.

or

Keep it, but change it to stateful set so that it is exactly the same as the stateful set deployment apart from using emptyDir as a storage. This would make it easier to maintain it and support it while adding features for the users (such as scaling up). We would also need one less image.

WDYT?

I understand @ppatierno finds/has found the inmemory image useful for testing and demos and such like. However, while it may be useful for those purposes, it's not clear to me that it should be a part of enmasse/barnabas. Assuming that is indeed the case then I would suggest we remove it from this repo and let it live somewhere else.

I agree with the second approach by @scholzj

@ppatierno Great, thanks. I think that would make few things easier. I will have a look at it.


Need some guide/help to start contributing (build/debug)

I would like to start contributing,
but im having trouble importing this project to dota workshoptools
currently im copying it to game\dota_addons
it does seem to start, but i cannot use  dota_launch_custom_game to launch it
i see a bunch of entries in gitignore
are there any assets i need to copy over that are required?
any help would be appreciated :)

Hello!
This github wasn't set up properly initially - it was just made as a kind of backup, should anything happen to my local files.
My updates to it were never consistent, and over time, they grew even more sparse.
Recently, many people have expressed the desire to help here, so, with the next IMBA patch, i will be adding all the necessary files to run it locally on your machine, as well as making it easier to contribute.
Thank you very much for being interested in helping! :)
Best regards

alright, im currently using a decompressed vpk to develop (not that easy..) are you managing to debug this somehow using eclipse LDT? having trouble with the set up..
i see you merged my pull request already ( pudge fix ) , feeling hopeful now :)
ill try and stick to specific bug-hunting for now until the git repo is complete (just ask if you need help setting things up)

debugging is done through vconsole 2, its all you need. also it shows on game screen with red text if there are errors.

Please check if the files are OK for you now. Thanks!


Spec workflow passing + Lint errors fixed + codeclimate error

Checklist

[ ✅] I have read the Contribution & Best practices Guide.
[ ✅] My branch is up-to-date with the upstream master branch.
[✅ ] The tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works(if appropriate).
[ ✅] I have added necessary documentation (if appropriate).

Short description of what this resolves/which issues does this fix?:

Changes proposed in this pull request:

Updated Linter, Spec, and CodeQL workflows are successful with the next upstream merge. CodeClimate javascript runs look good from the CodeClimate dashboard and GitHub dashboard. Successful merge.


Represent coinbase inputs explicitly and download blocks.

Represent and parse coinbase inputs explicitly, then follow on with some code that tests this on the live network:

Adds a FindBlocks request / BlockHeaderHashes response;
Adds code to the connect stub that blindly downloads blocks;
Streamlines the peer connection logic to connect to multiple peers concurrently when trying to increase the size of the peer set.

Closes #241 by incorporation.

Closes #236.

Rebased onto main to pick up #246.


Make the sample deployment work on OpenShift out of the box

These values are necessary when running on OpenShift. They are copied from upstream openshift profile.

/retest

/lgtm


Way to exclude resource by name pattern

When helm is using a secret driver does kubexport have any way to exclude it without excluding all secrets?
Currently I'm simply doing
 rm -rf **/Secret.sh.helm.release*

Hi @sstarcher
Have you tried with the Secret's type?
# allows to exclude single instances with certain field values
kindByField:
    Service:
      - field: [ metadata, name ]
        # the value is compared to the string representation of the actual kind value
        values: [ exclude-me-1, exclude-me-2 ]

To do that I would risk excluding all secrets right and if I'm trying to use something like metadata.name these values change
name: sh.helm.release.v1.xx-xxx-xx-xx.v20.
Does the values support a regex or wild card or prefix?

I may be able to use a label reference as it seems helm creates all of it's secrets with
-l owner=helm

check here: https://github.com/bakito/kubexporter/blob/main/config.yaml#L54-L57
this excludes all secrets of type 'helm.sh/release' and 'helm.sh/release.v1'

Ah thank you I did not realize they had a type field now I understand.


Rewrite loops to avoid for in and for of

For in and for of are not necessary.
Object.keys(obj).forEach((key) => obj[key]...));
may look slightly uglier than for in, but it's safer and potentially more efficient as it avoids traversing any properties that aren't the object's own.
For of loops can be substituted by forEach loops, which is more intuitive in the long run because it's more consistent with functional programming (ex: map, reduce, filter, etc.).

solved


Assertion Failed: Attempting to inject an unknown injection: 'service:notification-messages'

Error: Assertion Failed: Attempting to inject an unknown injection: 'service:notification-messages'
Code:
initializer/inject-notifications.js
export function initialize( application ) {
  ['controller', 'component', 'route'].forEach(injectionTarget => {
    application.inject(injectionTarget, 'notifications', 'notification-messages:service');
  });
}

export default {
  name: 'inject-notifications',
  initialize
};

Ember - 3.26.1
"ember-cli-notifications": "^6.3.4",

According to https://github.com/mansona/ember-cli-notifications/issues/257#issuecomment-823407763 the docs https://ember-cli-notifications.netlify.app/  needs to be updated ?

The docs reflect the expected service name by now 👍


Release 2.16.2

Release 2.16.2
iOS

Fix Xendit OVO redirection

Android

Allow 0 amounts
Allow 3DS for Google Pay
Fixed showPaymentMethod for cards and aligned with iOS

@EvansPie Reminder to bump the package.json


RN > 0.47 Support

googleapiavailabilitybridge/ReactNativeGooglePlayServicesPackage.java:18: error: method does not override or implement a method from a supertype
@Override
As result of RN 0.47, this error is coming. Can we please get fix.

Do you mean > ?

Yes, I meant >. Sorry typo

https://github.com/UCSD/react-native-google-api-availability-bridge/pull/5


Issue 39914: Switch Java 14 to "tested"

Technically, we'll still run with JDK 12.x and Tomcat 7.0.x, but these are messages we show when someone runs with a totally unsupported version. I don't want to encourage "upgrading" to JDK 12.x or Tomcat 7.0.x at this point.

Meant to target 20.3-SNAPSHOT. Will redo.


I can't use session with PDO mysql database in Codeigniter 3

it give me this error:
A Database Error Occurred
Error Number: 1064
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE id = '6b618ef793bc26b7f3de713e86b54c19508a44af'' at line 2
SELECT data WHERE id = '6b618ef793bc26b7f3de713e86b54c19508a44af'
Filename: libraries/Session/drivers/Session_database_driver.php
Line Number: 166
PDO configuration in database config file:
$db['default'] = array(
'dsn'	=> 'mysql:host=localhost;dbname=MyDatabase',
'hostname' => 'localhost',
'username' => 'root',
'password' => 'myPassW0rd',
'database' => '',
'dbdriver' => 'pdo',
'dbprefix' => '',
'pconnect' => FALSE,
'db_debug' => (ENVIRONMENT !== 'production'),
'cache_on' => FALSE,
'cachedir' => '',
'char_set' => 'utf8',
'dbcollat' => 'utf8_general_ci',
'swap_pre' => '',
'encrypt' => FALSE,
'compress' => FALSE,
'stricton' => FALSE,
'failover' => array(),
'save_queries' => TRUE
);
Server version: 5.5.47-0ubuntu<IP_ADDRESS> - (Ubuntu)

Sorry i was rush, this mistake was in the session-config in config.php file. so i have to add
_$config['sess_use_database']	= FALSE;
$config['sess_table_name'] = 'ci_sessions';_
to the $config

Yes, you did rush it.
But no, you should NOT add any lines to the config files that don't exist yet. If you actually read the documentation, you'd know that.


Organization Manager cannot add new operation system

In GitLab by @jasonpagetas on Jul 10, 2024, 06:08
When trying to create a new operating system a manager cannot add a operating system "403 Forbidden"
permissions include add operating system

added 2m of time spent

In GitLab by @jasonpagetas on Jul 10, 2024, 06:08
marked this issue as related to #74

In GitLab by @jasonpagetas on Jul 10, 2024, 06:20
user is not currently part of a team. This issue may be resolved when this is fixed

this is a feature not a bug. an organization manager must be assigned the permission like any other user.

In GitLab by @jasonpagetas on Jul 10, 2024, 06:20
marked this issue as related to #109


feat(etag): export RETAINED_304_HEADERS

In this PR, I've done:

Export RETAINED_304_HEADERS to make adding the retained header value easy.
Add the test for retained headers.
Refactor the tests. Removed beforeEach since the scope is not clear.

The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun denoify to generate files for Deno
[x] bun run format:fix && bun run lint:fix to format the code

Hey @usualoma !
Can you review this one?

@usualoma Sorry for pinging again. Could you review this?

@yusukebe Sorry I'm late, I think it's good!

@usualoma Thanks! Shipping this.


Pharos version upgrade check

Fixes #597
Performs an upgrade check when using the up subcommand and notifies if a newer version of pharos is available.

Now it's in excon and run as a phase.

How does this work in air-gapped environment?

Should pretty much fail silently unless you specify a PHAROS_UPGRADE_CHECK_URL that is reachable.

Should pretty much fail silently unless you specify a PHAROS_UPGRADE_CHECK_URL that is reachable.

How long it will wait for connection?

Defined by EXCON_OPEN_TIMEOUT if the air-gapping solution would be something that just hangs forever.


Concurrent complex UNLESS CONFLICT queries can spuriously raise ConstraintViolationError

If we, in two concurrent transactions, do:
FOR name IN {'name'} UNION (
    SELECT (
        INSERT Counter {
            name := name,
            value := 1,
        } UNLESS CONFLICT ON .name
        ELSE (
            UPDATE Counter
            SET { value := .value + 1 }
        )
    ).value
)

we spuriously generate a ConstraintViolationError, instead of a TransactionSerializationError (which can be automatically retried).
The issue is with UNLESS CONFLICTs that use "conflict CTEs" to determine whether to suppress the INSERT, rather than relying on ON CONFLICT to do it. Both queries start with a snapshot of an empty table, and so both try to do the INSERT; without there being an ON CONFLICT, postgres raises a constraint violation instead of failing to serialize the transaction.
Unfortunately, it is necessary in cases like this to not specify ON CONFLICT, because we depend on the lack of ON CONFLICT to cause an error if a single query tries to insert two conflicting objects (for example, if the query above because FOR name IN {'foo', 'foo'}). See https://github.com/edgedb/edgedb/issues/2193 for a detailed discussion of this issue.
Some possible approaches to this issue include:

Implement the "FILTER" strategy discussed in #2193
Stick with the "ERROR" approach, but implement it by explicitly detecting and raising an error on constraint violations. This will probably be able to build on some of the machinery being built for https://github.com/edgedb/edgedb/issues/2845
Retry on (some?) ConstraintViolationErrors

Alright I think we're good here.


Dockerfile: Add new dependency

SDK version 1.9.1 requres the installed libxshmfence1 package as a dependency.

LGTM! :+1:


command 'vscode-project-manager.addProject' not found

command 'vscode-project-manager.addCategory' not found
when i click the add project/add category button

thanks for your information. i will look soon to solve that problem.

+1

@hihahihahoho
I currently update the extension to version 1.0.2. So you can update the extesion and let me know if its now fixed.


Add version as service context

Please merge this PR. This is something a lot of projects can benefit from.

I have forked this repo and am going to be maintaining it moving forward. I just merged some of the useful PRs from this repository and made a new release. I'd really appreciate it if we can have new issues and PRs created on the new fork. Thanks!
https://github.com/asahasrabuddhe/zapdriver


goog.reflect.objectProperty returning wrong name

A disclaimer: I'm new to Closure Compiler and I know nothing about Closure Library, but I stumbled upon this StackOverflow question. It seemed like using goog.reflect.objectProperty would help me solve my problem, where I need to have a particular property name available as a string in the code. Why, you might ask? Well, because I have access to the setInterval function that can only accept string, so I need to know what to call it with.
I cannot include Closure Library in what I'm working at, but it seems it's enough to do
var goog = { reflect: { objectProperty: function(name, obj) { return name; } } };
in the code to make it work. I'm not sure how it works, but I suppose this function is hard-coded in the compiler even without loading the library itself.
Enough with the background.
java -jar closure-compiler-v20201006.jar --js a.js -O ADVANCED --language_in ECMASCRIPT3 --language_out ECMASCRIPT3

This doesn't work with this code in a.js:
var goog = { reflect: { objectProperty: function(name, obj) { return name; } } };

var CoolNamespace = {
    fun: function() {
        alert('it worked');
    }
};

CoolNamespace.fun();
setTimeout(goog.reflect.objectProperty('CoolNamespace', this) + '.' + goog.reflect.objectProperty('fun', CoolNamespace) + '()', 1000);

because it returns:
var a={a:function(){alert("it worked")}};a.a();setTimeout("b.a()",1E3);

which is obviously wrong. We should get a.a() in the string.
What's even more funny to me is what happens when you delete this line from the source:
CoolNamespace.fun();

Then the resulting code is:
setTimeout("b.a()",1E3);

I kinda know what happens here, but I feel that this is still wrong: I might say I got a wrong thing out of goog.reflect.objectProperty call, because there is no b or a anywhere.
As I said, I'm very new to all this, but I hope this is real issue and not me misunderstanding something I don't fully comprehend yet.

First, why pass a string to setTimeout? I don't know if you have some unusual requirement or actually are using some other function, but setTimeout(() => CoolNamespace.fun(), 1000); both seems more readable and doesn't require any Closure Compiler magic.
Second, the underlying issue is that Closure Compiler sometimes gets confused by referencing global variables off of the global object (like https://github.com/google/closure-compiler/issues/2162). So Closure Compiler doesn't connect goog.reflect.objectProperty('CoolNamespace', this) with the global variable CoolNamespace.
I'll leave this open so we can talk about this at the next bug triage meeting.
I suspect it's probably a bug but also there is probably an easier way to do what you want.

As I wrote, I have setTimeout and setInterval that can only accept strings, no functions. I don't have a choice but to jump through hoops here.

I'd suggest exporting the functions you want to call instead of using reflection (https://developers.google.com/closure/compiler/docs/externs-and-exports#purpose-of-exports).
That works around this issue with reflection & global variables, and might even allow Closure Compiler to better optimizer your code e.g. by replacing CoolNamespace.someFn with a single variable.

Yes, you guessed it. But externs/exports won't really work for me, since I want the code to be compiled. For now, this is my workaround:
/**
 * @param {*} obj
 * @return {string}
 */
var __objectToString__ = function(obj) {};

This is added to externs. Now, when I want to use setTimeout, I call it like this:
app.setTimeout(__objectToString__(CoolNamespace.fun) + '()', 1000);

And after compilation, when it gets replaced with something like __objectToString__(a.b), I can use regular expression to replace it with 'a.b'.
It's ugly, I know, but I feel it's the best way to do it for me for now, if I want to have my code minified as much as possible.


Instantly crashes on docker

Describe the bug
Crashes
To Reproduce
Steps to reproduce the behavior:
Ran docker run -it -p 6789:6789 -v $(pwd):/home/src mageai/mageai /app/run_app.sh mage start demo_project
Like it says on the docs.
This is what I get:
Execute command: mage start new
WARNING:traitlets:Message signing is disabled.  This is insecure and not recommended!
WARNING:traitlets:Message signing is disabled.  This is insecure and not recommended!
/app/run_app.sh: line 39:     7 Illegal instruction     (core dumped) "$@"

And then it quits.
If I run it directly, I.E
docker run -it -p 6789:6789 -v $(pwd):/home/src mageai/mageai mage start demo_project
I just get
WARNING:traitlets:Message signing is disabled.  This is insecure and not recommended!
WARNING:traitlets:Message signing is disabled.  This is insecure and not recommended!

And then it quits.
No further logs, tried the debug env variables and nothing
Expected behavior
server to start
Desktop (please complete the following information):

OS: Kubuntu
Version: Latest ([0.8.80])

Additional context
Tried different folders, not mounting at all, different names, nothing.

Hi @AsafMah , AsafMahDo you have other OS to test with? This could be an issue on the OS you use.

I have same issue.
uname -a

Linux xxx 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux

I have same issue on production server
Linux  5.15.0-70-generic #77-Ubuntu SMP

@santieb do you know what version you were on and what version you upgraded to?

From version 1.7 more or less
I share the slack thread where there is more context
https://mageai.slack.com/archives/C03HTTWFEKE/p1685711026489529

Same here using 0.9.5 on Ubuntu on Xeon physical machine

same problem , testing for the first time , but i cant get it work , im not using a VM , and i using a fresh install of debian
Linux homelab01 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 GNU/Linux

I have the same problem too:
 docker run -it -p 6789:6789 -v $(pwd):/home/src mageai/mageai   /app/run_app.sh mage start demo_project Execute command: mage start demo_project /app/run_app.sh: line 53:     7 Illegal instruction     (core dumped) "$@"
Linux srv 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Here is one solution from a user:
https://github.com/mage-ai/mage-ai/issues/2900#issuecomment-1663172937

Root cause: https://github.com/mage-ai/mage-ai/issues/3775
Solution: https://github.com/mage-ai/mage-ai/issues/3775#issuecomment-1896613315


Could not connect to Twilio: Connect failed

When trying to connect to Twilio under a new setup, I get "Connect failed". I've browsed around and this is different then the undefined error listed elsewhere. I've tried a LIVE and Test ID, neither seem to be working.
Generating my own token through the website and pasting it in solves the problem, but I would like a solution that could generate it's own token.
Browser: Chrome & Firefox
OS: OSX
Steps to reproduce:

brew install node
cp .env.example .env
Set variables
npm install
node .
Connect to a channel

 Screenshot attached

This was caused by the fact that the env variables did not match the README file. I've made a PR to fix this issue. https://github.com/TwilioDevEd/video-quickstart-node/pull/27


New colors are not generated when file name stay the same, but file itself changes.

wal 3.2.1
New colors are not generated when file name stay the same, but file itself changes.

Take image file run wal on it
Change the file but keep filename same
Run wal on it again,

wallpaper is changing but color schemes are from First file.

I've been aware of this for a while. The issue is fixing this in a performant way.

performant way ? Is there a method or something that I can run after to force pywall to recalculate the colors on the file? I belive this is some kind of "caching" inside pywall.

For me this is huge issue. I have keys binded to light and dark versions of terminal based on colorschemes that pywall produced. I was beleving that after I will just simply change files itself and I would have easy modificable system for managing themes for console.

Fixed.

@dylanaraps  Brilliant thank you!, when the new version of pywall will be avaliable on AUR packages for arch with that fix ?

Hi I'm still getting this issue using 3.3.0 version =


Using inav and betaflight running in 1 googles

hi, im using betaflight for my fpv quadcopter, 3 of them working great,
but i have one question....
i see the font for the inav and betaflight its different,? right/
so, can i running betaflight font (which already insert it into googles mmc)
in case use it with INAV too?
or i have to replace the font in the google, everytime i change my betaflight quadcopter to my inav fixed wing?
thanks before

You can have fonts per FC type on the SD Card, please see here: https://github.com/fpv-wtf/msp-osd#fc-specific-font-file-names


Add @ConsumseJson to contents API.

TBD.

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

It looks good.

Client will receive 415 response.

Would you add a test that verifies the status? It is a simple test but will be helpful to detect regressions in the future.

@ikhoon nim, i make a new commit to apply your comments.
I discovered something in the process.
When the Content-Type is not configured for each client, the default Content-Type may differ.
the values may differ!
dogma.client don't configure Content-Type. thus value is null.
curl configure application/x-form-urlencoded as default. thus value is application/x-form/urlencoded.
aiohttp.ClientSession() in python configure text/plain as default. thus value is text/plain.
Since the Dogma client defaults to a null Content-Type, it always will receive 400 response.
Therefore, to properly test this, I used parameterized tests to vary the Content-Type.