Enhancing Dark mode of Contact-Us page

Is your feature request related to a problem? Please describe.
The background color of the input fields on the Contact Us page in dark mode is not interacting with the rest of the website. I wish to work on this problem.
Describe the solution you'd like
I'll make the background color of the input fields on the Contact-Us page in dark mode more interactive.I would carry it out in line with the website's user interface.
https://github.com/SurajPratap10/Imagine_AI/assets/127978268/0ff51f04-e9f8-4e2b-b7f0-8c51dcfd5093

Assigned @akankshachanana1

I would like to contribute, kindly assign me.

I would like to contribute, kindly assign me.

You can't ask for assign in someone else's PR as it's their job. See @pandeydeekshaa these are the steps to contribute ⭐

Raise a unique issue by yourself
Then I will assign that issue to you
Then you can raise the PR
Later if the PR is fine then I will merge it

Ok sir
Thank you
On Wed, 14 Jun, 2023, 20:46 Suraj Pratap, @.***> wrote:

I would like to contribute, kindly assign me.
You can't ask for assign in someone else's PR as it's their job. See
@pandeydeekshaa https://github.com/pandeydeekshaa these are the steps
to contribute ⭐

Raise a unique issue by yourself
Then I will assign that issue to you
Then you can raise the PR
Later if the PR is fine then I will merge it

—
Reply to this email directly, view it on GitHub
https://github.com/SurajPratap10/Imagine_AI/issues/299#issuecomment-1591449958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3KMNQ7PRJM6PCINVRRAEHTXLHIUJANCNFSM6AAAAAAZCHAEVE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Disclaimer:
This message was sent from Vellore Institute of Technology.
The contents of this email may contain legally protected confidential or
privileged information of “Vellore Institute of Technology”.  If you are
not the intended recipient, you should not disseminate, distribute or copy
this e-mail. Please notify the sender immediately and destroy all copies of
this message and any attachments. If you have received this email in error,
please promptly notify the sender by reply email and delete the original
email and any backup copies without reading them.


Jobs processing order in cluster mode

Hi folks!
I have a problem with the clustering mode. As you can see at the screenshot jobs has been running 1st, 3rd, 2nd, 4th, but not in sequential order.
There are 2 node processes. Job working time is 1 second.

Hey, can you show what settings you are using on your limiters? That way I can try to reproduce it.
Thank you

Also, are the 2 node processes running on the same computer or different ones? How much time apart are you scheduling those jobs? It's possible for the time on those 2 instances to be off by a few 100ms, or network latency to cause job 3 to be received by the Redis server before job 2.

I have 2 docker containers with node processes. That 4 jobs has been sent in less than 1 second (you can see it on the screenshot). Redis is also running inside a docker container. All containers are local (docker-compose)
// limiter
const limiter = new Bottleneck({
  maxConcurrent: 2,
  datastore: 'redis',
  clearDatastore: false,
  clientOptions: { /* redis options */ },
})

// bottleneck function
fn(): Promise<void> {
  return new Promise<void>((resolve) => {
    setTimeout(() => {
      return resolve();
    }, 1000);
  });
}

// function call
await limiter.schedule(() => fn());

Thank you for the information. I'll be working on it this week. I'll keep you updated.

How are the jobs distributed? Is it

Like this (A):

Node process 1: Job 1, Job 2
Node process 2: Job 3, Job 4

Or like this (B):

Node process 1: Job 1, Job 3
Node process 2: Job 2, Job 4

From the Readme:

Queued jobs are NOT stored on Redis. They are local to each limiter. Exiting the Node.js process will lose those jobs. This is because Bottleneck has no way to propagate the JS code to run a job across a different Node.js process than the one it originated on. Bottleneck doesn't keep track of the queue contents of the limiters on a cluster for performance and reliability reasons.

Due to the above, functionality relying on the queue length happen purely locally:

Bottleneck guarantees that jobs will be run in the order they were queued on the same limiter. Another limiter on the cluster might run a job queued later before ours runs.

You must work around these limitations in your application code if they are an issue to you.

The current design guarantees reliability and lets clients (limiters) come and go. Your application can scale up or down, and clients can be disconnected without issues.

Bottleneck guarantees that jobs are run in order separately for each limiter.
So for case A:

Bottleneck guarantees:

job 1 will run before job 2
job 3 will run before job 4

But anything else is possible, ex: job 3 or job 4 could run before job 2 or job 1, etc.

And for case B:

Bottleneck guarantees:

job 1 will run before job 3
job 2 will run before job 4

But anything else is possible, ex: job 2 or job 4 could run before job 3 or job 1, etc.

Bottleneck guarantees that jobs are run in order separately for each limiter.

OK, got it. It does not matter in the most projects, I think.
But the order is critical for in my case. How can I reach this behavior? Could you give me a hint? Cause I didn't find any js/ts module (queue/mutex) that limits the number of requests per time to the external endpoint (in my case) totally in N separate node processes. And the main condition is to support horizontal scale. What do you think?
For example, when I have 3 node processes it must be only 5 requests per second to the external web service (endpoint).


ci: fix data plan fetch commit action

Summary

Fix Data Plan Fetch Commit Action

:tada: This PR is included in version 0.11.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support for Jenkins integration

Add support for Jenkins integration (I think we can use gem jenkins)

What are we looking to do here?  Just create a project?  Run tests on a project?


EAP 2019.2 Issues

Getting these to errors when just using the app. Not Fatal, just annoying.

https://pastebin.com/tE6u1EGc
https://pastebin.com/u60sBkK8

Environment
IntelliJ IDEA 2019.2 EAP (Ultimate Edition)
Build #IU-192.5118.30, built on June 13, 2019
IntelliJ IDEA EAP User
Expiration date: July 13, 2019
Runtime version: 11.0.3+12-b304.2 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.5
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 8
Registry: bigger.font.in.project.view=true, ide.mac.allowDarkWindowDecorations=true, git.explicit.commit.renames.prohibit.multiple.calls=false, ide.tree.ui.experimental=false, ide.balloon.shadow.size=0
Non-Bundled Plugins: Lombook Plugin, io.ktor.intellij.plugin, com.chrisrm.idea.MaterialThemeUI, io.acari.DDLCTheme

https://pastebin.com/fd7gGCuU


API Gateway Alert Threshold

💡 Summary
Set the trigger for the alert to execute after xx number of instances of the alert.
Motivation and context
This will reduce the number of email sent to the helpdesk
Acceptance criteria
How do we know when this work is done?

[ ] One alert will trigger after xx number of occurrences.

I wrote the alert to trigger when the percentage of api calls returning a 5xx status, exceeds 5%.


NuGet/DotNet: Support authenticated package sources

The NuGet.Config configuration file supports adding multiple package sources (See: #2189).
These package sources may require authentication which is described here.
<packageSourceCredentials>
    <Contoso>
        <add key="Username"<EMAIL_ADDRESS>/>
        <add key="Password" value="..." />
    </Contoso>
    <Test_x0020_Source>
        <add key="Username" value="user" />
        <add key="Password" value="..." />
    </Test_x0020_Source>
</packageSourceCredentials>

These credentials should be used in order to resolve the dependencies of NuGet packages from the authenticated package sources.

@MarcelBochtler have you tested this to be fixed with https://github.com/oss-review-toolkit/ort/pull/6209?

@sschuberth this is supported on the nuget-inspector side and tested extensively there.


Refactor restoration tests with replica failure and add one

longhorn/longhorn#6905
The behavior requested in longhorn/longhorn#2103 was already added with the inclusion of the allow-volume-creation-with-degraded-availability setting. This PR adds a test with that setting on and confirms volume restoration completes. Because it is so similar to a couple of other tests, it refactors all three tests to use the same base functionality.

test_single_replica_unschedulable_restore_failure (new) results
test_rebuild_with_restoration results
test_single_replica_restore_failure results
test_single_replica_unschedulable_restore_failure (new) backport to 1.5.x results

We should theoretically be able to backport all the way to v1.4.x, since the setting has been around that long. Haven't confirmed yet.

@mergify backport v1.5.x


Compatibility with mod_pagespeed

It seems polymer is NOT compatible with mod_pagespeed (or its specific configurations).
e.g. https://github.com/Polymer/polymer-tutorial/blob/master/step-1/index.html is displayed like:

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


Suspended + Sound put windows apps into "Not Responding" state

This one I can actually easily recreate with a test!  Yes, this code is slop but it's just a test file I hack away at when I find something I need to test outside the confines of my very complicated game code.  The actual preproduction would probably be a lot simplier.
This one is easy -- is you suspend_sync() and then play a sound (it might take one or two) eventually a windows application will fall into "not responding" and lock up.  No processor time, BTW, just it locks up.  Could be some interaction with winit.  I found this on the rc.5 branch.
`use winit::{event::*, event_loop::{ControlFlow, EventLoop}, window::{Window, WindowBuilder}};
use web_audio_api::{context::{BaseAudioContext, AudioContext}, node::{AudioNode, AudioScheduledSourceNode, PanningModelType, DistanceModelType}};
use std::f32::consts::PI;
use std::time::Instant;
pub async fn run() {
env_logger::init();
let event_loop = EventLoop::new();
let window =
    WindowBuilder::new()
        .with_title("blech")
        .with_inner_size(winit::dpi::LogicalSize::new(1024.0, 768.0))
        .with_resizable(false)
        .build(&event_loop).unwrap();

// the audio context
let ctx = AudioContext::default();

// run the window loop
event_loop.run(move |event, _, control_flow| {
    match event {
        Event::WindowEvent {
            ref event,
            window_id,
        } if window_id == window.id() => {
            match event {
                WindowEvent::MouseInput {
                    button,
                    state,
                    ..
                } => {
                    if *state==ElementState::Pressed {
                        println!("sound");

                        ctx.suspend_sync();

                        let length = ctx.sample_rate() as usize;
                        let sample_rate = ctx.sample_rate();
                        let mut src = ctx.create_buffer_source();
                        let flat_wave = vec![1.0; length];
                        let mut buffer = ctx.create_buffer(1, length, sample_rate);
                        buffer.copy_to_channel(&flat_wave, 0);

                        src.set_buffer(buffer.clone());
                        src.set_loop(true);

                        let gain = ctx.create_gain();
                        gain.gain().set_value(1.0);

                        src.connect(&gain);
                        gain.connect(&ctx.destination());
                        src.start();

                    }
                },
                WindowEvent::CloseRequested => *control_flow = ControlFlow::Exit,
                _ => {}
            }
        }
        Event::RedrawRequested(window_id) if window_id == window.id() => {
        }
        Event::RedrawEventsCleared => {
            window.request_redraw();
        }
        _ => {}
    }
});

}`

Hi @ggadwa. Thanks for another report, I really appreciate it.
I don't have a Windows machine laying around here so I can't run your code, but I can think of a possible cause.
Our library may block the control thread when the render thread cannot handle control messages fast enough. Control messages are actions like "add a new node", "start a node", "change a param value" etc.
The queue size of control messages is 256 items so in normal operations we can handle that many messages per render block (typically run every 3 milliseconds or so).
When the context is suspended, this may become an issue because we will block indefinitely after 256 new messages as the render thread handles zero messages in suspended state.
We don't use an unbounded (infinite size) channel because it can cause (de)allocations in the render thread which is a no go for latency considerations.
Now looking at your example code, it does not really seem like you are emitting this many control messages so maybe there is something else going on. Anyway I would like to rule out this scenario. So if you are okay with it, I will push a new branch (you know the drill) and I'm happy to hear the output.

I have pushed a branch called feature/crash-on-full-channel, it would be very helpful if you could run your code with it

Here you go!
[2024-04-17T19:33:04Z INFO  web_audio_api::io::cpal] Audio Output Host: cpal Wasapi
[2024-04-17T19:33:04Z INFO  web_audio_api::io::cpal] Output device: Ok("Speakers / Headphones (Realtek Audio)")
[2024-04-17T19:33:04Z DEBUG web_audio_api::io::cpal] Attempt output stream with preferred config: StreamConfig { channels: 2, sample_rate: SampleRate(48000), buffer_size: Fixed(128) }
[2024-04-17T19:33:04Z INFO  web_audio_api::render::thread] Entering garbage collector thread
[2024-04-17T19:33:04Z DEBUG web_audio_api::io::cpal] Output stream set up successfully
[2024-04-17T19:33:04Z DEBUG web_audio_api::events] Entering event thread
click
before suspend_sync
[2024-04-17T19:33:06Z DEBUG web_audio_api::context::online] suspend_sync called
[2024-04-17T19:33:06Z DEBUG web_audio_api::context::online] Supending audio graph, waiting for signal..
[2024-04-17T19:33:06Z DEBUG web_audio_api::context::online] Supended audio graph. Suspending audio stream..
[2024-04-17T19:33:06Z DEBUG web_audio_api::context::online] Supended audio stream
after suspend_sync
before make sound
after make sound
click
before suspend_sync
[2024-04-17T19:33:08Z DEBUG web_audio_api::context::online] suspend_sync called
[2024-04-17T19:33:08Z DEBUG web_audio_api::context::online] Supending audio graph, waiting for signal..
error: process didn't exit successfully: target\release\webaudio_test.exe (exit code: 0xcfffffff)
NOTES: I added the log items so you could see where it was.  It obviously goes into the suspend_sync on the 2nd click and never comes out again (the error is when I kill the app because it's frozen.)
So: (1) suspend (2) play sound (3) suspend (freeze)
So it is suspending an already suspended context, but that should probably be a no-op.

Ahh I see, we do not handle double suspend properly and end up blocking. This should be an easy fix (hopefully this week)

I know you know this, but while you are at it, make sure double resumes are no-ops, too, just in case!
Again, thanks for this great library.  When my game enters beta you can have a beta key!

double resumes are no-ops

Thanks for the nudge. And I would be very interested in seeing your final product


Support color expressions

@rof-ableton @sbs-ableton
... like color: hsla(320, 100% 75%, 0.3); in CSS.  This is probably not the final version. Color functions like this can easily be resolved inside of the StyleMatchTree builder (as it is done here), but expressions like url('') wouldn't have enough context.  Those can only be resolved probably in the StyleSet (at lookup time?), but for this we would need to change the PropertyMap representation (which already works in terms of QVariant).  But maybe this is a second step?  What do you think?

As we talked about, we would also like to have a hsb and hsba function, similar to https://github.com/AbletonAppDev/appearance/blob/master/sass/Live/_color_functions.sass#L35

I'm closing this PR for now, because I'll reorganize the approach completely!


feat(Meter): new component

🔗 Linked issue
None
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[X] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This is a rework of #708. It creates a <meter> tag and supercharges it with reactive elements. It follows the same principles of #697:

Uses min and max values.
Props and slots for a percent indicator, and a label.
Meter Grouping

📝 Checklist

[ ] I have linked an issue or discussion.
[X] I have updated the documentation accordingly.

🗒 Notes
As with the <progress> element, I decided to use the <meter> element for semantic reasons, instead of just shoving <div> and call it a day. This also means it uses targeted CSS selectors for WebKit/Blink and Gecko/Quantum, which adds some development overhead for the sake of consistency.

Asking for review to @benjamincanac mostly because Vercel doesn't want to deploy and I can't see how to fix (at least the CI passes)

Welp, I give up until I can see the errors and make the proper fixes.

Found the culprit, it was a link pointing to the #697

@DarkGhostHunter I've updated the PR a bit, I just have a weird visual on the MeterGroup with the rounded:

@DarkGhostHunter I've made all the changes I wanted, I'll wait for you to review before I merge!

@DarkGhostHunter I've made all the changes I wanted, I'll wait for you to review before I merge!

I'm AFK but I don't see anything weird on the changes, apart from some new code to keep it up to date.

@DarkGhostHunter FYI https://github.com/nuxt/ui/commit/18e8d28272efbf89abb5eaedbffcd6b7705b22c1

@DarkGhostHunter FYI https://github.com/nuxt/ui/commit/18e8d28272efbf89abb5eaedbffcd6b7705b22c1

Its fine.


Failed to load resource: the server responded with a status of 403 ()

hi, please help me Leonardo.
"Failed to load resource: the server responded with a status of 403 ()" https://passport.e-com.plus/v1/1199/identify.json
i can't verify my identify with passport of e-com, it's out of mine how way i try to test and find the solution for the ecommerce, please have a check bro. so sad that you denied how the way payment could working, because my country use different currency, please help me verify thanks

Hey, the 403 status only means the customer was not found by specified email address, then you should sign up on Storefront checkout:

You may set en_us (or your local language) and currency at content/settings.json on your deploy, if you want to use a custom language you may purpose addition here or just customize your Storefront deploy.

To complete checkout you must have apps installed for shipping and payment, directly on Store API applications resource or from our dashboard at https://app.e-com.plus/#/apps .
We don't have specific apps for your country yet (almost all are BR only), global solution for payment is PayPal, you may use it and configure your account, or you can use Pagamento personalizado (custom payment) and Frete personalizado (custom shipping), and configure it manually.

If you want to integrate another shipping/payment method (and considering you have Node.js skills), give a try at https://github.com/ecomplus/application-starter , this app https://github.com/ecomplus/app-mandabem may be an example for shipping method, and this https://github.com/ecomplus/app-pagarme for payment, both created from Application Starter.

i'm going to do i18n translate to vietnamese, and looking on it, thanks anyway @leomp12

@harumuki looks great! :+1:
If you want give a try with https://github.com/ecomplus/application-starter to setup local shipping/payment integrations I'll be happy to help you integrating.

@tiepdotme I answered two emails you sent me, both can't be delivered (your address seems to not be working), I think I've answered the same questions here, just about uploads you can give a new try now...

@leomp12 thanks you so much, you so great man. i can see it change now, as it working great, it is just i change the language to en_us, when checkout it must enter zip code and check first before it can show up. everything seems working fine, good job. i'm on thinking on translate the i18n, and working on some stuff that could process payment on vietnam, and the delivery app checking via vnpost, our main national delivery system.


dashboard/app: fix parsing bug and accept "gs://" prefixes

We mock the whole dashapi communication to test clients.
But the dashapi itself is not tested as far as I know.
The easiest way for this part is to deply&test.

I was wrong -> https://app.codecov.io/gh/google/syzkaller/blob/master/dashboard%2Fapp%2Fapi.go

#5634 to test the first, trivial one.
Second will be challenging because it may require gcs mocking....


replace arrow library with pendulum

Coverage decreased (-0.002%) to 98.575% when pulling 86737282f7630e22fdafc73439b5f73010d1c29d on use_pendulum into de98782ecb76080b73a2f9a5199ad4d3307bc110 on master.


Move OpticalChannelComponentFromPort util method to components.go

Pull Request Functional Test Report for #3005 / 6030b4edd20676a86fe39a53572cfc026f85eace
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
5ed7fc71
Log

Cisco 8000E

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
34227203
Log

Cisco XRd

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
e3117823
Log

Juniper ncPTX

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
d0dcc658
Log

Nokia SR Linux

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
d1a31193
Log

Openconfig Lemming

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming
03cbfb4b
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Cisco 8808

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Juniper PTX10008

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Nokia 7250 IXR-10e

TRANSCEIVER-9: Telemetry: 400ZR TX laser bias current telemetry values streaming.TRANSCEIVER-11: Telemetry: 400ZR Optics logical channels provisioning and related telemetry.TRANSCEIVER-8: Telemetry: 400ZR Optics module temperature streaming.TRANSCEIVER-1: Telemetry: 400ZR Chromatic Dispersion(CD) telemetry values streamingTRANSCEIVER-3: Telemetry: 400ZR Optics firmware version streamingTRANSCEIVER-7: Telemetry: 400ZR Optics inventory info streaming

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 23 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 55.5%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/components/components.go
0
23
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


How to import this into webpack or laravel-mix?

I tried doing require("is_js");
But I am seeing warning
Could not find a declaration file for module 'is_js'. '/node_modules/is_js/is.js' implicitly has an 'any' type.
  Try `npm install @types/is_js` if it exists or add a new declaration (.d.ts) file containing `declare module 'is_js';`

Use fork: https://github.com/evdama/is-it-check


Can't get path to work

0.9.2 with foundry 0.8.8, installed this for first time and have tried to follow the example but I can't get a path to work
Only this and the two support modules are active

created a scene
drop a default acolyte token on it
draw a two segment line drawing
name it Path1 in the text box
update position tab of the token to tick path patrol and put Path1 into the name field
pause/unpause the game to be sure
click the reset paths/nodes button
click the toggle patrol button
nothing happens..

should be fixed


FatalErrorException Declaration of ...\StringBladeCompiler::compile($viewData)

hi,
I tried to build a mail the way you described in #21, but I get the error:
Symfony\Component\Debug\Exception\FatalErrorException: Declaration of Wpb\String_Blade_Compiler\Compilers\StringBladeCompiler::compile($viewData) must be compatible with Illuminate\View\Compilers\BladeCompiler::compile($path = NULL) in /.../vendor/wpb/string-blade-compiler/src/Compilers/StringBladeCompiler.php:8
Stack trace:
#0 {main}

I couldn't figure out the problem as the stack trace wasn't helpful.

I have the same issue. It seems to be related to PHP 7.2 - works fine with 7.1.
I think it's more strict. Is that your case?

you're totally right, my version of php was the issue. everything was working fine until I switched to php 7.2 some days ago. I just switched back to 7.1 and everything's back to normal.
Any possible fix with php7.2?

Adding:
public function compile($viewData = null)

Should conform with the parent function, and then maybe throw an exception.
I could make a PR if you like, but what exception would you like to be thrown in case no viewData is thrown?

Any update here? Really need to get this fixed.

@petermein In which file do I need to add that code?

merged https://github.com/TerrePorter/StringBladeCompiler/pull/35


chore: fix gradle merge conflict

Fixes merge conflict in dependencies.gradle
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I don't think this is required any longer. Feel free to re-open.


Rancher container is restarting every 15 seconds on Ubuntu 22.04

Rancher Server Setup

Rancher version: v2.6.3
Installation option (Docker install/Helm Chart): Docker install

Describe the bug

After I restarted my ubuntu vm, my Rancher UI docker container is restarting every 15 seconds
Here is the log:
2022/01/22 11:40:19 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/22 11:40:19 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/01/22 11:40:19 [INFO] Listening on /tmp/log.sock
2022/01/22 11:40:19 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6443: connect: connection refused
2022/01/22 11:40:21 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6443: connect: connection refused
2022/01/22 11:40:23 [INFO] Waiting for server to become available: the server is currently unable to handle the request
2022/01/22 11:40:25 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/22 11:40:27 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/22 11:40:42 [INFO] Running in single server mode, will not peer connections
2022/01/22 11:40:43 [INFO] Applying CRD features.management.cattle.io
2022/01/22 11:41:29 [ERROR] unable to update feature harvester in initialize features: Put "https://<IP_ADDRESS>:6443/apis/management.cattle.io/v3/features/harvester": EOF
2022/01/22 11:41:29 [FATAL] k3s exited with: exit status 255

Any advice how to make it work again?

Having same issue running v2.6.3 in a single node docker container.

This has been happening to me for about a month and I cannot solve it. I can restore snapshots via Proxmox and it'll be good for about 3 days and randomly back to the reboot loop. Prior to the random event, everything on the node looks healthy.

This has been happening to me for about a month and I cannot solve it. I can restore snapshots via Proxmox and it'll be good for about 3 days and randomly back to the reboot loop. Prior to the random event, everything on the node looks healthy.

Sane thing,

This has also been happenig to me. I installed Version 2.5 and it worked but the latest stable release has the behavior described above.

This has also been happenig to me. I installed Version 2.4 and it worked but the latest stable release has the behavior described above.

I'm going to give this a shot.

Sorry I wasn't more specific, I installed using the docker container with the tag v2.4.9. It works!

Sorry I wasn't more specific, I installed using the docker container with the tag v2.4.9. It works!

Unfortunately using older versions does not help me, my downstream clusters are k8s 1. 22 so can't import them.

Our team is seeing this behavior as well with single-node Rancher v2.6.3-patch1 running on AlmaLinux 8.5 (one of the Enterprise Linux distros).
For the Rancher devs -- this is basically the same behavior reported in #35892 and #36047, which my team is also seeing -- the error messages we get alternate between the ones reported here and the ones in those tickets. The comments on #35892 seem to indicate that this is a problem with updates to various systemd packages in EL 8.5, and that the problems did not occur in EL 8.4.

We have the same problem :(

Same problem here on a fresh OpenSUSE server for v2.6. Downgrading to v2.4.9 worked.

^ Worked for me as well.
I've briefly tried Rancher so many times in the 1st quarter of this year, and never managed to get one to stay up long enough to USE it.
WHY is this STILL going on?

hello i have this same problem on ubuntu 22.04 LTS and rancher is not working.
2022/04/26 20:33:36 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6443: connect: connection refused

I'm having the same issue ... downgrading to version 2.5 works, however some of my clusters are running 1.22 and I cannot import them.
after SUSE bought rancher it has became the worst product ever ... version 2.6 is very buggy and unstable. I'm willing to rebuild my cluster on version 1.21 and not move to 2.6

Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding

hello i have this same problem on ubuntu 22.04 LTS and rancher is not working.
2022/04/26 20:33:36 [INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6443/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6443: connect: connection refused

Same here. Will try Ubuntu 20.04 LTS, as the last time that worked.

Fresh Debian 11 images. Same issue.

VMware - Ubuntu 20.10 to 22.10. same issues.
Even tried rancher v2.5.X. all same issues.

Ubuntu 20.04 - no issues with all latest releases of Rancher. This has proven to be the solution for all my issues so far.

Ubuntu 18.04
Docker 20.10.15
Tried rancher latest, tried 2.6.4, tried 2.5.2.
Same thing every time.  It runs long enough to get itself setup, then restarts every few minutes.
I can't understand how this has been happening for months with no engagement from the devs?

The solution for me was changing from Ubuntu to CentOS 7 (from AWS Marketplace).
I'm using AWS and I installed the Rancher as a single node (for the main/local cluster).
Here are the steps that I did.
1-) Install the docker on CentOS:
sudo yum install docker
2-) Install vim editor:
sudo yum install vim
3-) Create the file daemon.json:
sudo vi /etc/docker/daemon.json
3.1-) File content:
{    "group": "dockerroot" }
4-) Restart docker:
sudo systemctl restart docker
5-) Enable docker:
sudo systemctl enable docker
6-) Add centos user to group dockerroot:
sudo usermod -aG dockerroot centos
7-) Last but not least, install Rancher:
sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /rancher:/var/lib/rancher --privileged rancher/rancher

Downgraded from Debian11 to 10 works fine

Also tried with Debian 10 and it works. With debian 11 it doesn't work.

Rancher 2.6.5 on ubuntu 22.04 (Hetzner Cloud VM) - same problem.
Reinstalled VM with debian 10 - rancher works fine.

I had this issue on Ubuntu 22.04 i fixed it by editing /etc/default/grub file. Added these values into GRUB_CMDLINE_LINUX:
GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"
then did:
sudo update-grub
sudo reboot
This resolved my problem but i spent entire day on it. Maybe it helps someone else as well.  I think the same thing works for Debian 11.

@ognjen011 Thank you, this GRUB config worked for me on Ubuntu 21.10.

I had this issue on Ubuntu 22.04 i fixed it by editing /etc/default/grub file. Added these values into GRUB_CMDLINE_LINUX:
GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"
then did:
sudo update-grub sudo reboot
This resolved my problem but i spent entire day on it. Maybe it helps someone else as well. I think the same thing works for Debian 11.

It works for Debian 11(debian-11.3.0-amd64-DVD-1.iso) you save my day bro!

Still having this issue... cannot get rancher to run successfully on any Linux distributions (older versions Ubuntu, Centos and Debian)... I have updated the grub file as suggested above but this seems to disable SSH  for me on Ubuntu?
Really want to try Rancher out but no success... it just keeps restarting every 30 odd seconds

I had this issue on Ubuntu 22.04 i fixed it by editing /etc/default/grub file. Added these values into GRUB_CMDLINE_LINUX:
GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"
then did:
sudo update-grub sudo reboot
This resolved my problem but i spent entire day on it. Maybe it helps someone else as well. I think the same thing works for Debian 11.

Thank you!

Same issue on macOS Big Sure M1 with the latest image 2.6. Downgrading to 2.4 worked as well.

Trying to install Rancher 2.6.x with no luck either. The latest version that seems to have started successfully is the 2.5.15 version.
My servers use fully patched Oracle Linux Server 8.6 with docker-ce 20.10.17
With every 2.6.x version I get the same error: Waiting for server to become available: an error on the server (“apiserver not ready”) has prevented the request from succeeding
What can we do?

Rancher version v2.6.6  with ubuntu22.04 still has the problem,  how can we do? quick, quick!

I've personally settled on 2.5.15, now exploring the product and building my first downstream clusters. I recommend you to do the same.

I've personally settled on 2.5.15, now exploring the product and building my first downstream clusters. I recommend you to do the same.

Thanks @irenucio... I did get 2.4 running but it lacked the Linode drivers so will try 2.5.15

I had this issue on Ubuntu 22.04 i fixed it by editing /etc/default/grub file. Added these values into GRUB_CMDLINE_LINUX:
GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"
then did:
sudo update-grub sudo reboot
This resolved my problem but i spent entire day on it. Maybe it helps someone else as well. I think the same thing works for Debian 11.

I love you

I have installed Rancher 2.5.15 on Ubuntu 18.04 and can confirm that this issue is also occurring on 2.5.15 :

Out of ideas.... is no-one from Rancher bothered about this at all ?

How is it that Ubuntu 22.04 (A LONG TERM SUPPORTED RELEASE) is not actually tested against for Rancher? Testing against Alpha/Beta versions of Ubuntu 22.04 were available for MONTHS before its release. And naturally, there's good reasons to move from 20.04 to 22.04.
I have a feeling @ognjen011 's solution is going to fix it for me. But like... this is just straight up unacceptable.
Not only is this an undocumented fix, I don't see ANYONE from the dev team responding in this thread at all!
Literally building a new production environment here and this clearly off to a great start... FFS guys...

GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"

Thank you!
It works perfectly for
Ubuntu 22.04.1 LTS
5.15.0-43-generic
Docker 20.10.12
Rancher v2.6.6

Yeah the "GRUB_CMDLINE_LINUX" aspects did the trick for me too.

Not working on debian 11 (cloud image) with the above mentioned grub cmd line change either.

rancher/rancher:v2.4.9
Yeah, me too. My server is also debian 11 and I can only use tag 2.4.9

well I spoke too soon..
Doesn't work a fresh cloud image ubuntu 22.04 with only latest docker / compose installed..
Just keeps on trying to conect forever to k3s (which I can see seems to be running processes via htop)

weird, the rancher/rancher:v2.4.9 works fine in ubuntu-jammy-22.04-amd64-server. But latest or the newerst tag doesn't work. Doing docker logs -f 1f9dfc254c09 we can see the failing loop Waiting for server to become available. Which is sad.

@kinarashah on cursory investigation of this issue it looks like we're running into an issue with our embedded K3s running with unified cgroups hierarchy (v2) enabled
@galal-hussein @brandond any ideas on this here?

Does anyone have the K3s log file available from the failing startup?
Did Rancher ever pull in the cgroup v2 evacuation script from k3d? The cgroup evacuation needs to be done before the kubelet is started, by the container's init process (pid 1). If k3s is pid 1 it will do this for itself, but if it is being started by an entrypoint script, the entrypoint should do something like https://github.com/k3d-io/k3d/blob/main/pkg/types/fixes/assets/k3d-entrypoint-cgroupv2.sh before starting k3s.

The GRUB change worked for me on my Proxmox VE V7.1 with a Ubuntu 22.04 VM.
Thank you!
PS.  Be patient after rebooting.  It takes a minute for rancher to restart.

sudo nano /etc/default/grub
Rancher
GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"
sudo update-grub
sudo reboot

Instead of keeping cgroup V1 with the above fix to grub systemd.unified_cgroup_hierarchy=0 ,   which may not work for futures releases
Docker 20.10.17 is using the new cgroupv2 kernel  but still using the old iptables and not nftables for the containers
You can do the following  fix.
Ubuntu / Debian
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1"
sudo update-grub
sudo reboot

Fedora/Redhat
sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=1"
sudo reboot

And then if you try to connect to your rancher container, you will see these line at the end:
I0831 08:24:20.442967      66 network_policy_controller.go:151] Starting network policy controller
F0831 08:24:20.443474      66 network_policy_controller.go:368] failed to check for the existence of chain KUBE-ROUTER-INPUT, error: running [/usr/bin/iptables -t filter -S KUBE-ROUTER-INPUT 1 --wait]: exit status 3: iptables v1.8.6 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
panic: F0831 08:24:20.443474      66 network_policy_controller.go:368] failed to check for the existence of chain KUBE-ROUTER-INPUT, error: running [/usr/bin/iptables -t filter -S KUBE-ROUTER-INPUT 1 --wait]: exit status 3: iptables v1.8.6 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

New kernels for Ubuntu 22 or Redhat8 deactivate iptables and activate nftables
So you need to activate the iptables kernel module:
Ubuntu / Debian
modprobe ip_tables
echo ip_tables | sudo tee -a /etc/modules

Fedora/Redhat
modprobe ip_tables
echo ip_tables > /etc/modules-load.d/ip_tables.conf

after that, without reboot, my rancher container is able to start!!
INFO: Running k3s server --cluster-init --cluster-reset
Doing /etc/rancher/ssl
WARNING: key.pem does not contain a certificate or CRL: skipping
2022/08/31 09:07:20 [INFO] Rancher version v2.6.5 (c4d59fa88) is starting
2022/08/31 09:07:20 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/08/31 09:07:20 [INFO] Listening on /tmp/log.sock
2022/08/31 09:07:30 [INFO] Running in single server mode, will not peer connections
2022/08/31 09:07:30 [INFO] Applying CRD features.management.cattle.io
2022/08/31 09:08:16 [INFO] Applying CRD navlinks.ui.cattle.io
2022/08/31 09:08:16 [INFO] Applying CRD clusters.management.cattle.io
[...]
2022/08/31 09:08:31 [INFO] Starting rke.cattle.io/v1, Kind=ETCDSnapshot controller
2022/08/31 09:08:31 [INFO] Starting management.cattle.io/v3, Kind=ClusterAlert controller
2022/08/31 09:08:31 [INFO] Starting management.cattle.io/v3, Kind=ClusterLogging controller
2022/08/31 09:08:31 [INFO] Listening on :443
2022/08/31 09:08:31 [INFO] Listening on :80
2022/08/31 09:08:31 [INFO] Listening on :444

Same issue with Rancher 2.6.6, 2.6.7 and 2.6.8 on Ubuntu 22.04LTS with docker 20.10.17. Thanks @lerminou for the workaround!

 It's not sustainable to have a custom entrypoint.sh in the long term.

I can send a PR for the entrypoint but the cgroup prerequisites won't be inside and should be in your side, maybe another documentation PR?

https://github.com/k3s-io/k3s/pull/3237/files#diff-28ca1392bc87e90a7b14087d1451b94891f76e17def41647545c898fdf94bd20

/backport v2.6.9

There is already a documentation ticket, https://github.com/rancher/docs/pull/4251

I have also hit this issue on the latest v2.6-head. There does seem to be a workaround that was found here by another user. After the workaround, Rancher container stopped restarting and worked as expected, being able to provision downstream cluster as well.

@thaneunsoo what about mac workaround?

@Sahota1225  not only Ubuntu is impacted, Redhat too.

Available to test with v2.7-head once https://drone-publish.rancher.io/rancher/rancher/8317/1/1 is green

@kinarashah  for me works. Thanks

update-grub

What does this actually do? This solved the problem for me too!
VPS with ovh cloud

Test Environment:
Rancher version: v2.7-head
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: Custom

Testing:
Tested this issue with the following steps:

On Ubuntu 22.04 instance install Rancher using docker
Verify install is successful
Verify that rancher container does not restart every 15 seconds
Reboot the instance
Verify that rancher container does not restart every 15 seconds

Result
Rancher container is no longer restarting on Ubuntu 22.04
I am now seeing the following error in the docker logs and am unable to reach Rancher
[ERROR] available chart version (1.0.5+up0.2.6) for rancher-webhook is less than the min version (1.0.6+up0.2.7-rc4)
2022/09/21 21:33:09 [ERROR] Failed to find system chart rancher-webhook will try again in 5 seconds: no chart name found

Test Environment:
Rancher version: v2.7-head eab28dd
Rancher cluster type: single-node docker install
Docker version: 20.10

Testing:
Tested this issue with the following steps:

On Ubuntu 22.04 instance install Rancher using docker
Provision RKE1 cluster
Provision RKE2 cluster

Result - Pass
Rancher container is running successfully and RKE1 and RKE2 clusters also come up fine as well.

Still not working in el9, correct? I can't get stable nor v2.6.9 running on Rocky Linux 9

Still not working in el9, correct? I can't get stable nor v2.6.9 running on Rocky Linux 9

Same issue, EL9.1 any workarounds?

I managed to resolve this issue with the following procedure. It turned out that iptables where not installed and appropriate modules loaded into kernel.
Please note that I named rancher container "rancher" (--name=rancher docker run flag)
create directory on your host:
sudo mkdir /rancher
sudo chmod 777 /rancher

run rancher with the following command. It is essential to mount volumes for debugging purposes.
sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /rancher:/var/lib/rancher --privileged --net=host --name=rancher rancher/rancher`

execute
docker logs -f rancher`

if rancher fails to start because of https://<IP_ADDRESS>:6444/ cannot connect error "[INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused", then you need to investigate /rancher/k3s.log on your host
I found that iptables installtion was missing on the host
After installing iptables I had to manually load two modules - k3s was complaining about missing them in k3s.log:
sudo modprobe iptable_nat
sudo modprobe iptable_filter

add both modules to the file
sudo cat<<EOF >/etc/modules-load.d/modules.conf
iptable_nat
iptable_filter
EOF

then I got an issue with x509 certificate which got resolved by - please note that I named my container "rancher":
sudo docker exec -it rancher sh -c "rm /var/lib/rancher/k3s/server/tls/dynamic-cert.json"
sudo docker exec -it rancher k3s kubectl --insecure-skip-tls-verify=true delete secret -n kube-system k3s-serving
sudo docker restart <container id>

I managed to resolve this issue with the following procedure. It turned out that iptables where not installed and appropriate modules loaded into kernel. I tested it on Rocky 8.7 with rancher 2.7.3.
SOLUTION:

install iptables
make sure that missing iptables modules are loaded into kernel:

Add both modules to the file
sudo cat<<EOF >/etc/modules-load.d/modules.conf
iptable_nat
iptable_filter
EOF

and reboot your host"
sudo reboot

execute:

sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged --name=rancher rancher/rancher`

TROUBLESHOOTING:
Please note that I named rancher container "rancher" (--name=rancher docker run flag)
Create directory on your host:
sudo mkdir /rancher
sudo chmod 777 /rancher

Run rancher container with the following command. It is essential to mount volumes for debugging purposes.
sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /rancher:/var/lib/rancher --privileged --net=host --name=rancher rancher/rancher`

Execute
docker logs -f rancher`

If rancher fails to start because of https://<IP_ADDRESS>:6444/ cannot connect error "[INFO] Waiting for server to become available: Get "https://<IP_ADDRESS>:6444/version?timeout=15m0s": dial tcp <IP_ADDRESS>:6444: connect: connection refused", then you need to investigate /rancher/k3s.log on your host.
I found that iptables were missing on the host. After installing iptables I had to manually load two modules - k3s was complaining about missing them in k3s.log:
sudo modprobe iptable_nat
sudo modprobe iptable_filter

Add both modules to the file
sudo cat<<EOF >/etc/modules-load.d/modules.conf
iptable_nat
iptable_filter
EOF

and reboot your host"
sudo reboot

Then I got an issue with x509 certificate which got resolved by the following commands (please note that I named my container "rancher"):
sudo docker exec -it rancher sh -c "rm /var/lib/rancher/k3s/server/tls/dynamic-cert.json"
sudo docker exec -it rancher k3s kubectl --insecure-skip-tls-verify=true delete secret -n kube-system k3s-serving
sudo docker restart rancher

When you finish troubleshooting and get missing iptables modules loaded into kernel then you can run docker in the way provided in the solution section - without volumes attached and host network. The issue with the invalid x509 certificates could be a side effect of troubleshooting.

on rocky linux 9.3 works fine

@hhruszka  your solution works for my oracle linux 9.3


My first contribution

Added first and last name to contributor list.

I made my first pull Request. Thank you!


examples: update i3-cycle-focus.py for recent api changes

Hopefully, I didn't miss any changes :grinning:

:+1: :+1:


fix(tier4_perception_launch): fix error of tier4_perception_launch_param_path

Signed-off-by: Takagi, Isamu<EMAIL_ADDRESS>Description
Fix this error.
TypeError: add_launch_arg() takes from 1 to 2 positional arguments but 3 were given
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@isamu-takagi Thank you so much. :bow:


Makes drive letter capitalized

Making the drive letter, capital when using get_drive() function. Should reflect in all cases wherever the drive letters are being displayed

Bugsquad edit: potential fix for #26844

Probably safe.

@kartikey0303 You can check out the solution at #26847. The solution that you propose is probably safe and doesn't break compatibility. But the solution is a bit inefficient because the drive letters are originally hard-coded in as small caps letter. Changing these hard-coded values is probably the best way to provide a program-wide solution but could break compatibility.
Right now we are waiting for the core devs to make 3.1 stable. We can then inquire redu_z for the design decision behind keeping small drive letters

It will be a breakage in compatibility, but nothing common or severe.
Currently, I have path validations in some of my scripts (mainly tools), that check if a path is legit before attempting to create a directory using it.  In a few areas there is a comparison of the given drive letter.  If this is input by typing, I split the drive letter from the String, and use to_lower() to compare against the results given by get_drives().
When a change like this goes into affect, I'll have to remember to go and swap those with to_upper().  A minor fix, but I can't think of anything worse than that.

Closing because of #26847 being more spot on.


HCLOUD-2606_add-lastActive-field-to-the-user-modal-and-use-findOneAndUpdate-during-whoami-to-enable-a-lastActive-date_Jorge-Brown

Task linked: HCLOUD-2606 add lastActive field to the user modal and use findOneAndUpdate during 'whoami' to enable a lastActive date


LilyGo T-Relay(6) S3 - pin assigments in documentation doesnt match schematic/reallity

The pin assignments shown in LilyGo T Relay S3 documentation doesn't match the schematics.
I think that these are the right ones:
static const uint8_t TX = 43;
static const uint8_t RX = 44;
static const uint8_t SDA = 16;
static const uint8_t SCL = 17;
// Temperature Sensor
static const uint8_t DSDATA = 21; // Not Connected
// RTC
static const uint8_t RTC_CLK32 = 15; // Not Connected
static const uint8_t RTC_INT = 18;
// HT74HC595ARZ
static const uint8_t SHIFT_REG_CLK   = 5
static const uint8_t SHIFT_REG_LATCH = 6
static const uint8_t SHIFT_REG_DATA  = 7

Thank you. It seems that the document was not changed in time after changing the GPIO. It has been corrected now.


Standardization

Documentation standardizations, better "Standard JS" conformance, bumped package versions and implemented "Standard JS" tests.

These two commits should handle your concerns. Unless I got the indentation wrong...


Completions are returning 204 No Content for anything but "global" scope

I've just tried with a quite fresh (yesterday) install of YouCompleteMe + racer completion, and any time I trigger a completion with . or :: I get no results back (the stdout log of racerd shows 204 No Content).
If I however trigger a completion at a "global" scope (just hitting ctrl-space on an empty line), it returns 200 OK with actual completion suggestions

Can you provide concrete examples of what works and what doesn't?

Hi @jwilm
I've encountered into the same issue.
My steps to reproduce:

run racerd --logging
run example curl command from example
see "204" in racerd's console:

GET http://<IP_ADDRESS>:3048/ping -> 200 OK (0.018089 ms)
POST http://<IP_ADDRESS>:3048/list_completions -> 204 No Content (0.579337 ms)

no json returned to curl

/find_definition has the same issue.
I use racerd 0.3.3 compiled within YouCompleteMe plugin for Vim.

If it helps see debug log below:
DEBUG:hyper::server: threads = 48
racerd listening at <IP_ADDRESS>:3048
DEBUG:hyper::server: Incoming stream
DEBUG:hyper::server::request: Request Line: Post AbsolutePath("/list_completions") Http11
DEBUG:hyper::server::request: Headers { User-Agent: curl/7.47.0, Content-Length: 146, Content-Type: application/json, Host: <IP_ADDRESS>:3048, Accept: */*, }
DEBUG:racer::core: Path: contextstr is |path::Path|, searchstr is ||
DEBUG:racer::core: Complete path with line: "let p = path::Path::"
DEBUG:racer::nameres: resolve_path P[path::Path::] "src.rs" 47 StartsWith
DEBUG:racer::nameres: resolve_path P[path::Path] "src.rs" 47 ExactMatch
DEBUG:racer::nameres: resolve_path P[path] "src.rs" 47 ExactMatch
DEBUG:racer::nameres: resolve_name path "src.rs" 47 ExactMatch Type
DEBUG:racer::nameres: search_local_scopes PathSegment { name: "path", types: [] } "src.rs" 47 ExactMatch Type
DEBUG:racer::nameres: searching scope Type start: 26 point: 47 'path' "src.rs" ExactMatch local: true, session: Session { .. }
DEBUG:racer::nameres: search_scope found matches ExactMatch []
DEBUG:racer::nameres: search_scope_headers for |path| pt: 25
DEBUG:racer::nameres: search_scope_headers preblock is |fn main() |
DEBUG:racer::nameres: search_fn_args: found start of fn!! 15 |impl blah {fn main() {}}| path
DEBUG:racer::nameres: searching scope Type start: 0 point: 47 'path' "src.rs" ExactMatch local: true, session: Session { .. }
DEBUG:racer::matchers: found use: path in |use std::path;|
DEBUG:syntex_syntax::parse::lexer: scanning whitespace: Some(TokenAndSpan { tok: Whitespace, sp: Span { lo: BytePos(3), hi: BytePos(4), expn_id: ExpnId(4294967295) } })
DEBUG:syntex_syntax::codemap: byte pos BytePos(0) is on the line at byte pos BytePos(0)
DEBUG:syntex_syntax::codemap: char pos CharPos(0) is on the line at char pos CharPos(0)
DEBUG:syntex_syntax::codemap: byte is on line: 1
DEBUG:syntex_syntax::parse::attr: parse_outer_attributes: self.token=Ident(use#0)
DEBUG:syntex_syntax::parse::attr: parse_outer_attributes: self.token=Eof
DEBUG:racer::nameres: resolve_path P[std::path] "src.rs" 0 ExactMatch
DEBUG:racer::nameres: resolve_path P[std] "src.rs" 0 ExactMatch
DEBUG:racer::nameres: resolve_name std "src.rs" 0 ExactMatch Type
DEBUG:racer::nameres: get_crate_file std, "src.rs"
DEBUG:racer::cargo: get_crate_file: from_path="src.rs"
DEBUG:racer::nameres: search_local_scopes PathSegment { name: "std", types: [] } "src.rs" 0 ExactMatch Type
DEBUG:racer::nameres: searching scope Type start: 0 point: 0 'std' "src.rs" ExactMatch local: true, session: Session { .. }
DEBUG:racer::matchers: import use std::path; involved in a cycle; ignoring
DEBUG:racer::nameres: search_scope found matches ExactMatch []
DEBUG:racer::nameres: search_crate_root |PathSegment { name: "std", types: [] }| "src.rs"
DEBUG:racer::nameres: search_prelude file PathSegment { name: "std", types: [] } ExactMatch Type
DEBUG:racer::nameres: resolve_path returning []
DEBUG:racer::nameres: search_scope found matches ExactMatch []
DEBUG:racer::nameres: search_crate_root |PathSegment { name: "path", types: [] }| "src.rs"
DEBUG:racer::nameres: search_prelude file PathSegment { name: "path", types: [] } ExactMatch Type
DEBUG:racer::nameres: resolve_path returning []
DEBUG:racer::nameres: resolve_path returning []
POST http://<IP_ADDRESS>:3048/list_completions -> 204 No Content (0.557813 ms)
DEBUG:hyper::server::response: writing head: Http11 NoContent
DEBUG:hyper::server::response: headers [
Headers { Content-Length: 0, Date: Fri, 07 Apr 2017 13:45:28 GMT, }]
DEBUG:hyper::server: keep_alive = true for <IP_ADDRESS>:47426
DEBUG:hyper::server: keep_alive loop ending for <IP_ADDRESS>:47426

Sorry, I set rust source folder as ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust but it should be set as ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src (I missed last component).
Now it works fine.


Setting annotations in viewDidLoad adds superfluous annotations in Landscape

If you set up the annotations for your map view controller in viewDidLoad - as suggested in the README then you get a superfluous cluster annotation if presenting the map view controller in Landscape. Note the big "59" cluster on top of ÖSTERREICH.

If you move it to viewWillAppear or later, then this extra cluster does not appear:

I believe that the reason for the misbehavior comes from MKMapView having an incorrect position during viewDidLoad. I added logging for the visible map rect in the -init of CCHMapClusterOperation.
Portrait, viewDidLoad:
Visible map rect = {{141014758.6, 88274850.3}, {6111232.3, 10743653.0}}
Visible map rect = {{141014758.6, 88274850.3}, {6111232.3, 10743653.0}}

Portrait, viewWillAppear:
Visible map rect = {{141014758.6, 88274850.3}, {6111232.3, 10743653.0}}

Landscape, viewDidLoad:
Visible map rect = {{40502319.6, 79459175.3}, {127778493.3, 69020511.0}}
Visible map rect = {{141014758.7, 91996163.0}, {6111232.1, 3301027.8}}

Landscape, viewWillAppear:
Visible map rect = {{141014758.7, 91996163.0}, {6111232.1, 3301027.8}}

The second line in the Landscape-viewDidLoad log comes from this call stack:

As you can see there is a timer delay that fixes the visible map rect and calling the mapView:regionDidChange:animated: thus triggering a reclustering.
Putting the setup code into viewWillAppear resolves the issue, but the question for this bug report is, whether the initial clustering shouldn't be delayed until after the first setting of the visible region. The current recommendation and code leads to a superfluous clustering operation.
The second question is, why the second clustering operation does not correct the superfluous cluster annotations that the first one created.
This issue observed on an app with deployment target 8.1, running on 8.3, using a MKMapView from storyboard and size classes throughout.

I updated the sample code to read in 500 annotations synchronously in viewDidLoad. In this scenario, CCHMapClusterOperation gets called twice: once for a setRegion call and once for adding annotations. The clusterer has to re-cluster the annotations in both cases because either operation causes a change in the visible annotations /the first one will be basically for free because there are no annotations to cluster). Is this what you are seeing as well?
As for the second case: setting the region should definitely recluster all visible annotations. Could you provide sample code that demonstrates this issue? When I use the example project, the app starts in portrait and when I rotate manually to landscape, everything works fine. But your are starting this view controller in landscape?

Unfortunately I don't have time to provide more than these steps to reproduce:

map controller is inside a tab view controller as second VC
app supports landscape
log the visible map rect property of the app
run app
turn to landscape
tap on tab with map controller

This should show you the described behavior


Phylogenetic data prep training

New tutorial on data preparation for phylogenetic analysis (mask repeats, predict proteins, find orthologs and align)

@hexylena and @bebatut I was wondering what to status was of this pull request. Are there changes that we still have to make on our side? Thanks in advance!


splitview page width is wrong

Looks like when a new browser tab is initialized, its width is being set to the window width, even when they are in a split pane. I think it should initialize the web view with the split width, not the window width.
Image showing issue, notice scroll bar in bottom right:

I don't understand? That's how GitHub works in a normal browser as well.


Non blocking smtp check

I merged this into a test branch - but it is still failing tests. I will pass it back to you to get the tests passing. (I have just merged master into non_blocking_smtp_check branch to force it to retest with the latest changes but I am not hopeful)

I have dropped the test branch since the tests failed - happily accept a pull request with passing tests


Crash when setting AVAudioSessionRouteSharingPolicy for iOS

On an iOS 14.5 simulator setting the AVAudioSessionRouteSharingPolicy will cause an exception or crash.

AVAudioSessionRouteSharingPolicy.defaultPolicy works fine
AVAudioSessionRouteSharingPolicy.longFormAudio and AVAudioSessionRouteSharingPolicy.longFormVideo cause an OSStatus error -50 platform exception*
AVAudioSessionRouteSharingPolicy.independent causes a Lost connection to device. from the IDE without any Flutter or system logs.

*more info: https://stackoverflow.com/questions/26718103/what-does-osstatus-error-50-mean

Apple's documentation for independent says:

Apps shouldn’t try to set this value directly.

I wasn't able to get any exception on longFormAudio. Can you provide a minimal reproduction project?

Any update on this or is the issue resolved?


[Android] Add forceGetLocation filed to get AssetEntity

Use scenario: When retrieving List object, you want to return the location information of all Asset Entity objects directly, instead of iterating through the List to retrieve it individually through get Lat Lng Async method, which is time-consuming
使用场景：获取List对象时，想要直接返回所有AssetEntity对象的地理位置信息，而不是遍历list去单独的通过getLatLngAsync方法去获取，那样很耗时。

The PR itself seems ineffective. EXIF should depend on permissions on recent Android versions, and the request will make the loading complexity increase from O(n) to O(n^2).

The PR itself seems ineffective. EXIF should depend on permissions on recent Android versions, and the request will make the loading complexity increase from O(n) to O(n^2).

Suppose there are 100,000 pictures in the album, and the pictures with geographic location information need to be found out from them. According to the previous logic, 100,000 pictures need to be recycled first, and then 100,000 times to obtain the exIF of the picture. Now, the need Geo field is used to control the extraction of exIF information when the picture is taken out, which saves the cycle time
假设相册有10万张图片，需要从其中找出有地理位置信息的图片，按照之前的逻辑就需要先循环取出10万张图片，再循环10万次去获取图片的exif,而现在通过needGeo字段去控制在取出图片的同时取出exif信息，节省了循环的时间

Suppose there are 100,000 pictures in the album, and the pictures with geographic location information need to be found out from them. According to the previous logic, 100,000 pictures need to be recycled first, and then 100,000 times to obtain the exIF of the picture. Now, the need Geo field is used to control the extraction of exIF information when the picture is taken out, which saves the cycle time

This only saves callers, not the total time. Also, I don't see you're handling the permission here.

The solution is not in a good state IMO. Please file a new PR after the design is more solid and clear. Thanks.


8080 Syntax Highlighting is Missing JZ/JNZ Mnemonics

JZ/JNZ mnemonics for 8080 Syntax Highlighting are missing. They work properly if you switch to 8085 (Which is identical except includes SIM and RIM instructions)

Hi, thanks for pointing this out. The 8080 mnemonics used by TASM are a bit odd. For example, 'JP NZ' instead of JNZ and 'JP Z' instead of JZ. It also includes some undocumented opcodes. I suspect this mnemonic set was a holdover from some other popular assembler back in the day that folks were used to. The same sort of oddness was common if you used an assembler made for Motorola for one of their processor's vs a 3rd party.
I hesitate to change the original TASM table for the 8080 as that might break existing code. I can create another one though based on the 8085 without SIM and RIM.


About Firebase

Hello...
My Question is that i have create my firebase console project.
can you please explain me that how to use that firebase console specification and it's data structure into this(https://github.com/ionic-in-action/ionic-demo-resort-app) demo project.?

You can get the raw data by looking for all of the Firebase URLs and adding .json to the end and requesting that payload.
Example: https://ionic-in-action-demo.firebaseio.com/events -> https://ionic-in-action-demo.firebaseio.com/events.json


Entry for opensource project - CAP+FE demo project

 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.


Does not load all PR/Issue comments if there are too many

When looking at the comments of a PR/Issue, there is a limit on how many comments you can see on the app. To see an example, find PR #132.
There doesn't seem to be a way to load more comments from the app.

This should be easily done with GraphQL

Ah this a good catch :+1:
So like most of the endpoints, it defaults to 30 per page and although with GraphQL this would be easier, we can add a filter it to 100 in the meantime. https://api.github.com/repos/gitpoint/git-point/issues/132/comments. Will put up a PR for this soon.
Note: Pull request comments are still not visible #6 and definitely something we need to integrate in the near future (looks like half of the conversation is missing in the app :joy: :sob: )

Extended to 100 issue comments

Closing this since I've extended to 100 comments. However, that doesn't help if issues contain more than 100 comments so definitely open to discuss how we can solve that 🤔
Similar issue #217 open for managing how many issues/PRs show for repositories.


Hard coded link removed in top static-nav site

Previous URL was hard coded for the top-nav site.

Hey, thank you very much but I fixed it already.. ;-)

Oh.. and blame GitHub for delayed notifications.. Sorry about that.


Cannot have different values per host for global arguments

Describe the bug
Setting use_sudo_password differently for two different hosts fails, the same password is used for both.

Fixed via workaround in v1.6.2 (https://github.com/Fizzadar/pyinfra/commit/2cd2e1a5b3ad6389a9ae815b28f2326fe55a4f42), v2 will properly fix this.


Bug with disabling Optimizely

Ref #5798.

This code block is never being executed on staging, only on local
This code won't work, because it asks for for the confirmation interactively

Disabling Optimizely module on staging.
The following extensions will be disabled: optimizely
Do you really want to continue? (y/n): y

cc @angaither

https://github.com/DoSomething/phoenix/pull/5813

Duplicate of #5811.


Return an empty list when include is given but there's no data from included

There's an issue when a graphql query/mutation expects a field which is a jsonapi relationship(data in included) but no data is given from the response.
I think the expected behavior here would be returning an empty list.
Sample error message:
Error: Error writing result to store for query:
 {"kind":"Document","definitions":[{"kind":"OperationDefinition","operation":"mutation","name":{"kind":"Name","value":"UpdateReel"},"variableDefinitions":[{"kind":"VariableDefinition","variable":{"kind":"Variable","name":{"kind":"Name","value":"input"}},"type":{"kind":"NonNullType","type":{"kind":"NamedType","name":{"kind":"Name","value":"UpdateReelInput"}}}}],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"reel"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"input"},"value":{"kind":"Variable","name":{"kind":"Name","value":"input"}}}],"directives":[{"kind":"Directive","name":{"kind":"Name","value":"jsonapi"},"arguments":[{"kind":"Argument","name":{"kind":"Name","value":"path"},"value":{"kind":"StringValue","value":"/reels/{args.input.data.id}?include=reel_video_clips","block":false}},{"kind":"Argument","name":{"kind":"Name","value":"method"},"value":{"kind":"StringValue","value":"PATCH","block":false}}]}],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"name"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"publishStatus"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"reelVideoClips"},"arguments":[],"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"FragmentSpread","name":{"kind":"Name","value":"VideoClip_videoClip"},"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}}]}},{"kind":"FragmentDefinition","name":{"kind":"Name","value":"VideoClip_videoClip"},"typeCondition":{"kind":"NamedType","name":{"kind":"Name","value":"VIReelVideoClips"}},"directives":[],"selectionSet":{"kind":"SelectionSet","selections":[{"kind":"Field","name":{"kind":"Name","value":"id"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"name"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"startTime"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"endTime"},"arguments":[],"directives":[]},{"kind":"Field","name":{"kind":"Name","value":"__typename"}}]}}],"loc":{"start":0,"end":421}}
__typename is undefined bundle.esm.js:704

@ins429 I've noticed that inlining empty has_many relationships is failing:
  it('handles empty included relationships', async () => {
    expect.assertions(1);

    const link = new JsonApiLink({ uri: '/api' });
    const author = {
      id: '1',
      type: 'authors',
      attributes: { name: 'George R. R. Martin' },
      relationships: { books: [] },
    };

    fetchMock.get('/api/authors/1?include=books', {
      data: author,
      included: [],
    });

    const query = gql`
      query authorQuery {
        author @jsonapi(path: "/authors/1?include=books") {
          id
          books {
            id
            title
          }
        }
      }
    `;

    const { data } = await makePromise<Result>(
      execute(link, {
        operationName: 'authorQuery',
        query,
      }),
    );

    expect(data).toMatchObject({
      author: {
        __typename: 'authors',
        id: author.id,
        books: [], // This fails because `books` is `null`, not `[]`
      },
    });
  });

I'm not positive if that exactly translates to the store error you're seeing--do you think this is the cause?

Ah, whoops, that case is actually succeeding, I just miswrote the test above. It should be
  it('handles empty included relationships', async () => {
    expect.assertions(1);

    const link = new JsonApiLink({ uri: '/api' });
    const author = {
      id: '1',
      type: 'authors',
      attributes: { name: 'George R. R. Martin' },
      relationships: { books: { data: [] } }, // I forget to nest `[]` in `data` here
    };

    fetchMock.get('/api/authors/1?include=books', {
      data: author,
      included: [],
    });

    const query = gql`
      query authorQuery {
        author @jsonapi(path: "/authors/1?include=books") {
          id
          books {
            id
            title
          }
        }
      }
    `;

    const { data } = await makePromise<Result>(
      execute(link, {
        operationName: 'authorQuery',
        query,
      }),
    );

    expect(data).toMatchObject({
      author: {
        __typename: 'authors',
        id: author.id,
        books: [],
      },
    });
  });


Adjustments to E2E tests to decrease CI test run time

skip driver late-binding stress tests in direct mode - supposed to save ~40m
limit running package manager and imagefile unit tests part of E2E tests - supposed to save ~10m

Did (and how) we verify tests actually run in shorter time with these changes?
The job for this PR took 7h57min which is significantly longer than other PRs tested close in time (879, 880 about 5h30min)
https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/job/pmem-csi/view/change-requests/

I hope that Jenkins duration display is not affected by some side effect, like including wait-time for workers. Around running these jobs, worker capacity as maxed and some jobs had to wait for some time to get started.

Did (and how) we verify tests actually run in shorter time with these changes?

Not really, as the disabled/Skipped tests are "[Slow]" tests which do not run on PRs .

The job for this PR took 7h57min which is significantly longer than other PRs tested close in time (879, 880 about 5h30min)
https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/job/pmem-csi/view/change-requests/

This is bit strange, This PR should skip existing tests, but not introduce any delays or run new tests.

Not really, as the disabled/Skipped tests are "[Slow]" tests which do not run on PRs

ah, in that case, my checking for run times is not relevant, there has been some other reason, as I suspected.

This saved less time than expected. Latest "devel" testing on 1.19 before this change took 8h 33m 28s (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/devel/315/pipeline/86), with this change 8h 13m 28s (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/devel/316/pipeline/86).
It's still worthwhile, but we probably can do better.
I noticed that "late binding stress test [Slow] – fedora-1_18.operator-direct-production.driver" still ran. Should that have been skipped?

This saved less time than expected. Latest "devel" testing on 1.19 before this change took 8h 33m 28s (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/devel/315/pipeline/86), with this change 8h 13m 28s (https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/devel/316/pipeline/86).

Could have made ~10min difference if no test failures. Those failed tests took timeout.

Olev Kartau<EMAIL_ADDRESS>writes:

Did (and how) we verify tests actually run in shorter time with these
changes?

I've looked at recent "devel" builds and drilled down to the actual
execution of the E2E step for 1.19. That runs on the already started
worker and thus should not occur any additional wait time.


Homepage Spelling

Contributors is spelt Contribuitors in the Contributors section of the homepage.

Ready, I can fix thank you very much


Automate trigger of openjdk10-openj9 systemtest in x64x & ppc64le linux

Automate triggering of openjdk10-openj9 systemtest in x64x & ppc64le linux platforms once the sdk build job of these platforms succeeds.
Signed-off-by: Mesbah<EMAIL_ADDRESS>

@sophia-guo - could you please review?

Conflict removed.


backup snapshot contains unspecified content

backup：files-from-paraments
test-file like these:

cat filelist:
  /home/test1/dk1/*.java
  /home/test1/dk1/*.sh

the backup command:
restic -r ./repo -p ./pd ./dk --files-from=./filelist --tag java-and-sh

then the snapshot show these:

I don't know why the dk file in thesse snapshot，I only want to backup the files from filelist
backup：exclude-file-paraments
the exclud-file like these:

also doesn't work
](https://github.com/restic/restic/issues/4376)

sorry,write the error step  not have this issue


analyzer: Bump oasis-core version

SUMMARY

oasis-core 22.2 was released. We should probably bump.
ISSUE TYPE

Feature Idea

COMPONENT NAME

ADDITIONAL INFORMATION

https://app.clickup.com/t/3u9ypbu


Abstract method verbose in FluxCalibration

When running reduction_sequence_science.ipynb, the second to last cell is failing:
TypeError: Can't instantiate abstract class FluxCalibration with abstract method verbose
I tracked the error to the CorrectionsBase class, particularly in the verbose decorators:
    @property
    @abstractmethod
    def verbose(self):
        return self._verbose

    @verbose.setter
    def verbose(self, verbose):
        self._verbose = verbose

I tried to fix it by commenting the @asbractmethod but did not work. Also, that may break others instances. The other option that I'm trying is to redefine the function list_available_stars(verbose=True) or change the usage of attribute verbose for this class.

Issue has been fixed in PR #456, please review.

This issue has been fixed and tests were passed. I'm closing this issue now.


Rename @azure/keyvault-keys enumerations to be consistent

We need to rename the following enumerations to be consistent with the key vault libraries across other languages, as well as internally consistent with the naming of these enumerations.
JsonWebKeyCurveName -> KeyCurveName
JsonWebKeyOperation -> KeyOperation
JsonWebkeyType -> KeyType
JsonWebKeyEncryptionAlgorithm -> EncryptionAlgorithm
KeySignatureAlgorithm -> SignatureAlgorithm

This is pretty easy to do (thanks TypeScript!), and I do like shorter names.
Some questions though:

In the code it's JsonWebKeySignatureAlgorithm, which I assume should be SignatureAlgorithm
Should we rename the JsonWebKey interface to be simply Key? or is that not what other languages do?

Right now these all are exported type aliases, so they're not actually a runtime artifact that can be imported. You can see this in how VS Code doesn't even show the alias name:

I'm not sure this is release blocking, since users are expected to pass a string literal today instead of an enum value. Maybe that's unexpected / not as good for JS devs, but I think that's part of a broader question around if we want to provide runtime enums for string values or not.

@xirzec Specifically it's the types that need to be renamed as users could import these for instance from the API extractor output:
// @public
export type JsonWebKeyCurveName = "P-256" | "P-384" | "P-521" | "P-256K";

// @public
export type JsonWebKeyEncryptionAlgorithm = "RSA-OAEP" | "RSA-OAEP-256" | "RSA1_5";

// @public
export type JsonWebKeyOperation = "encrypt" | "decrypt" | "sign" | "verify" | "wrapKey" | "unwrapKey";

// @public
export type JsonWebKeyType = "EC" | "EC-HSM" | "RSA" | "RSA-HSM" | "oct";

Looks like it's still JsonWebKey in .NET: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/keyvault/Azure.Security.KeyVault.Keys/src/JsonWebKey.cs
So I'll leave that one alone.


https://code.visualstudio.com/sha/download?build=stable&os=linux-x64 returns 403 Forbidden when queried

~Does this issue occur when all extensions are disabled?: Yes/No~

VS Code Version: irrelevant
OS Version: GNU Wget 1.24.5 built on linux-gnu.

Steps to Reproduce:

wget 'https://code.visualstudio.com/sha/download?build=stable&os=linux-x64' -O "code-stable-$(date -Iminutes).tar.gz"

Works fine when accessed from browser.
This URL can be used in scripts to automate installing the latest code version. Previously it responded with redirect to the latest version. That makes it a regression.

Looks like this was just fixed...

Looks like the issue is gone now. Thanks to everyone involved.


chore: update templates to quote test_otp

What kind of change does this PR introduce?
Test otp phone number needs to be in quotes
Relevant issue: https://github.com/supabase/gotrue/issues/1293

on hold, let me confirm why it's not working with double quotes first..


float16 support for synaptic variables on the GPU (and CPU)

It would probably be useful to use float16 for the synaptic variables.  There is a nice existing Go package: https://github.com/x448/float16
vulkan 1.2 now includes it as a fully supported option: https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VK_KHR_shader_float16_int8.html and in HLSL it is float16_t fully supported with shader model 6.2 and moltenvk appears to support it as of 2018: https://github.com/KhronosGroup/MoltenVK/issues/368
some older GPU hardware does not have native 16 bit support, so it will run much slower there, but the advantages on current hardware likely outweighs that.

Actual Lvis model tests show that the A100 does not allow addressing of more than 31 bits of memory even if broken up using a SynMemBlock:
struct SynMemBlock {
	float vals[64];
};

float SynV(in Context ctx, uint syni, SynapseVars svar) {
	uint64 ix = ctx.SynapseVars.Idx(syni, svar);
	return Synapses[ uint(ix / 64)].vals[uint(ix % 64)];
}

For bench_lvis net, with ndata=2, we're under, but ndata=3 puts over to SynCa = 2.5 GB
  BenchLvisNet:	 Neurons: 47204	 NeurMem: 30.6 MB 	 Syns: 32448512 	 SynIdxs: 371.3 MB 	 SynWts: 618.9 MB 	 SynCa: 1.7 GB

So the next strategy is to use pages of memory instead of blocks, for SynCa which is the main point of failure.
And float16 will help relieve pressure considerably!

this looks like a great resource: https://therealmjp.github.io/posts/shader-fp16/


setting too many constraints

if I set left, right, and width constraints, upon resizing the art board nothing happen. since the object is over defined. (I think)
same story with setting top, bottom, and height.
is there a way to clarify this?
so if I have left and right constraints, enabling width, would disable one of the left or right ones.
or another way to make it clear that the current set of constraints are not working.

Size constraints are stronger than position constraints, I chose to let all position constraints in these cases because how can I choose which constraint is more important without a strength system? As you noticed, currently only left/top and size constraints are applied in these cases.

I learnt about constraint strength two days ago from my developer friend. is there a way to show this in the interface?
maybe if the user sets all 3, (in your example, left/right/width) then the right constraint gets dimmed to 50% or something?
that way the user would know right away that their current set of constraints don't work.


Issue with spot details display on Notebook header

Notebook header shows spot details on multiple lines and misses some data for imagebasemap spots.
A clear and concise description of what the bug is.
Are you able to reproduce the problem in a new project after restarting the app?
Yes
Steps to reproduce the behavior:

Set a spot on imagebasemap
Check the notebook header, misses some details

Screenshots..

@nicolasmroberts : Please suggest if you want us to increase the header size to fit in all the content or want to use abbrevations like N, E, W, S for North east west and south ? and X, Y for Xpx and Ypx.

@sdamaraju In this order, here are things you can do to reduce space as needed: 1) use cardinal direction abbreviations; 2) make font size slightly smaller; 3) round the displayed coordinates to one less decimal place than currently exists. NOTE: of course, store the full coordinate data (unrounded).

@nicolasmroberts Hello nick, just with the cardinal direction abbreviations the header looks like this and the space looks good.
It doesn't need any further resizing or one decimal cut.
Please let me know if this looks okay ?

Yes, that looks good!

closed with commit 81028c5af50277103715962ae8eb62fcadea8efb


Build fail when the files referenced in Dockerfile are not found

Issue
It is possible that the build fails because files used in Dockerfile are missing in the Docker build context.
Background

docker_vcstool offers a way to specify the path to Dockerfile (and some other specific files for now, not list of arbitrary files), by copying them into a temporary Dockerfile build context.
This process doesn't check what files are used in the given Dockerfile.

It is the user's responsibility to define Dockerfile to be passed to docker_vcs properly. That said it'd be great if the tool can check prior to the build whether certain files used in Dockerfile are missing or not.


SDFGI produces wildly inaccurate and extreme lighting intensities, and strange colors

Tested versions
Reproducible in Godot 4.2.1 (.NET). Anecdotally this has been an issue for me since SDFGI was released, and has been present for me in every version of Godot 4 I have tried, which were previously non-.NET versions.
System information
Godot v4.2.1.stable.mono - Windows 10.0.19044 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics 620 (Intel Corporation; <IP_ADDRESS>5) - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 Threads)
Issue description
When enabling SDFGI, it doesn't appear how I expect. I am demonstrating this bug in @WickedInsignia's Godot Garden global illumination test scene, as it is a widely available benchmark with many images of how it should look.
How it should look (from Godot Garden issue linked above)

How it looks for me

You may notice a lack of directional shadows in my images. I have the DirectionalLight3D visible, so I have no idea why this is but it's not relevant to this bug report.
This type of issue is present any time I have used SDFGI, in every version of Godot 4 I have tried, including v4.2.1.
I have made slight changes to the original Godot Garden project. I added a camera and saved the main scene to view the scene at runtime. This bug was present from the moment I opened the project. I also don't think this is a result of using a project from v4.0a12 in v4.2.1. I have replicated this bug in a fresh 4.2.1 project too, and in many previous versions of Godot 4.
I have a feeling this issue is a result of me using Intel integrated graphics. I haven't been able to find this same bug reported yet, but of course I could have missed it. I'm not doing anything weird — just using SDFGI out of the box from another well-known project, and yet I have such a catastrophic result. I think the only weird thing I'm doing is using an Intel laptop with a rare issue. That said, nothing would delight me more than someone else confirming these results.
Edit: I know SDFGI is going to be replaced in 4.3, so I don't expect major effort to be invested in fixing this likely niche bug.
Steps to reproduce

Download the Godot Garden project from Issue #63374 or the original Dropbox link or my personal project.
Open in Godot 4.2.1 (Note: the original project is intended for Godot v4.0a12, but I don't think this is relevant as this issue persists in my own projects made in Godot 4.2.1, or any version of Godot 4 I've tried)
Notice how bad it looks.

Minimal reproduction project (MRP)
Original Godot Garden project Dropbox link (for Godot v4.0a12)
My specific project (slight changes mentioned above)

I can't reproduce this on 4.3 13a0d6e9b (Linux, GeForce RTX 4090 with NVIDIA 545.29.06):

Can you try removing the .godot/ folder while the editor is closed, then reopen the project? This will force all resources to be reimported.

Thank you for the tip. This did not fix the SDFGI bug, but it did fix the DirectionalLight3D.

I thought this issue might be related to #84738 Reflection Probe Too Glossy wIth Panorama Sky, as this scene is also using a PanoramaSkyMaterial. However, when I change to a procedural sky, the issue doesn't go away.

Yeah so I honestly can't say I'm helping on this subject, I can only say that I also use an intel integrated PC and have been having the exact same issues with meshes and SDFGI interactions (Godot v 4.2.1), and my only theory is that Intel has some sort of weird problem with Vulkan (Godot's rendering engine for SDFGI), and that this could be potentially a hardware bug which I'll look into at a later time.
Also, here's a screenshot of my issues so that hopefully you're sure we're having the same issue. I'm SOOOOOOO glad someone else had this bug lol.
Scene with no SDFGI (Directional light on .1 intensity and sky influence at .5)

Scene with above settings but with SDFGI enabled

Yeah so I honestly can't say I'm helping on this subject, I can only say that I also use an intel integrated PC and have been having the exact same issues with meshes and SDFGI interactions (Godot v 4.2.1), and my only theory is that Intel has some sort of weird problem with Vulkan (Godot's rendering engine for SDFGI), and that this could be potentially a hardware bug which I'll look into at a later time.
Also, here's a screenshot of my issues so that hopefully you're sure we're having the same issue. I'm SOOOOOOO glad someone else had this bug lol.
Scene with no SDFGI (Directional light on .1 intensity and sky influence at .5)
Scene with above settings but with SDFGI enabled

Okay, so I'm currently installing new graphics drivers for intel integrated, will update you soon!

Okay so sadly the update didn't fix any troubles, so I believe that sadly it is just a problem with the integrated graphics hardware on intel chips, we might need to upgrade our potatoes Andrew

Hey guys, me again. After some research I found that Godot v 4.2.1 and most likely all older godot 4 versions are using Vulkan 1.3, which was released 2 years ago in Q1 2022. ALL Intel integrated only support up to Vulkan v1.2, with only the newest, highest end GPU's from Intel supporting Vulkan 1.3. This is not a Godot bug but merely an oversight by us and not doing our proper research on our PC's.
Supported graphics (Source : Intel website)

Sorry @aaandrewww but we might just need a computer upgrade. I'm requesting simply a feature which tells you if your PC specs are compatible with ALL of godot's 3d features (i.e. what Unreal does where it tells me that my PC doesn't support Nanite and has its features turned off). I don't know how engine programming works, and with Godot not requiring an install I don't know if it's possible, but for developer's sakes that is definitely a necessary feature.

some research I found that Godot v 4.2.1 and most likely all older godot 4 versions are using Vulkan 1.3, which was released 2 years ago in Q1 2022.

Godot only requires Vulkan 1.0 to run, and it aims to keep its Vulkan requirements as low as possible. We don't intend to introduce a Vulkan 1.3 requirement anytime soon for this reason, although 1.2 could end up being required in the long run on desktop (it's already ubiquitous in practice).

although this is an old thread, i'd like to add that

this is still an issue in the most recent stable release of 4.3
it's still an issue with Vulkan 1.3.261 on my Dell XPS 13 Plus from late 2022 (with Intel Iris Graphics)

on the Dell XPS:

(not identical, but same area and same configuration) on the desktop with a Nvidia 3060:

i wasn't aware SDFGI is being replaced, but hopefully this issue can be fixed. it would be a shame to lose such a powerful and lightweight GI on platforms without a dedicated GPU (especially since Godot is arguably THE engine for building low-requirements games).


TypeScript support

Describe the solution you'd like
It'd be really nice if you could support TS.
Describe alternatives you've considered
There are two ways you can go about it (afaik):

Simply create a declaration file (and since your module exports just one function, this should be fairly simple).
(Gradually) rewrite the library using TS -- this would improve type safety if this is something you care about.

Additionally
There are forks to your library that already have TS support. Perhaps, you could consider simply ingesting their code.

As a side note, your library works wonders! Thank you very much!

Sure no problem, I will add a declaration file, I just don't think that rewriting the whole library using typescript makes sense since it exports only one function


Can not redirect output of helm template to a file in bash

Output of helm version:
version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"}

I'm on Ubuntu 20.04.
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.13-gke.401", GitCommit:"eb94c181eea5290e9da1238db02cfef263542f5f", GitTreeState:"clean", BuildDate:"2020-09-09T00:57:35Z", GoVersion:"go1.13.9b4", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): none/localhost
I'm trying to render this helm template using helm template installer/manifests/keptn and store the output in a file, e.g.:
helm template installer/manifests/keptn > test.txt

Using helm 3.3.4 the file test.txt is empty, while using helm 3.2.4 the file contains the content that I was expecting.
However, if I don't redirect the output to a file everything works as expected, e.g.:
helm template installer/manifests/keptn | grep kind

kind: ServiceAccount
kind: ServiceAccount
kind: ServiceAccount
kind: ServiceAccount
kind: Secret
kind: Secret
kind: Secret
kind: ConfigMap
kind: ConfigMap
...

I believe there is some weird bug that prevents me from redirecting the output to a file.

I can imagine that's a frustrating problem.
I have tried to replicate this using the chart in question using both Helm v3.3.4 and the tip of master. I've done this on Ubuntu 20.04. I have not been able to reproduce the problem. When I send it to a file it works.
Note, in Helm v3 the template command can (and should) have two argument. It works with just one but it should have two. You can find the details with helm help template.
Is there some other detail about the situation? I've looked through the code path and I don't see anything that would cause this.

I swear to all gods that are known to the people on this planet, that I've tried the command 5 times, then tried it using helm 3.2.4, and then again using helm 3.3.4. The problem persisted with 3.3.4, and vanished with 3.2.4.
Anyway, the problem came up because I'm piping the output of helm template to pluto, using
helm template installer/manifests/keptn | pluto detect-files -

and this also did not work with helm 3.3.4, but with 3.2.4 it did.
It is working now, without any change to the code-base, nor a reboot or anything on my machine. I've never seen a behaviour like this, but I'm going to blame full moon.
The only other thing I can think about is that helm 3.2.4 has changed something in my local helm config, and with that change helm 3.3.4 works fine again.

I'm glad it's working now.
There shouldn't have been any changes between Helm 3.2.4 and 3.3.4 to the local config. None that I can think of.
My best guess is gremlins. Good luck with them.