Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

1.0.0-rc3 Missing function / classes for configuration #1420

Open
eyalcha opened this issue Nov 14, 2023 · 5 comments
Open

1.0.0-rc3 Missing function / classes for configuration #1420

eyalcha opened this issue Nov 14, 2023 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@eyalcha
Copy link

eyalcha commented Nov 14, 2023

The following doesn't exists

const { createConfiguration, ServerConfiguration } = require('../dist');
const { PromiseMiddlewareWrapper } = require('../dist/gen/middleware');

https://github.com/kubernetes-client/javascript/blob/release-1.x/examples/patch-example.js
@eyalcha eyalcha changed the title 1.0.0-rc3 Missing 1.0.0-rc3 Missing function / classes for configuration Nov 14, 2023
@SarthakNikhal
Copy link

Hey. Which functionality is broken because of this issue? Can I work on it?

@mstruebing
Copy link
Member

@eyalcha I believe this should be available if we release another RC.
Can you validate if the issue is still the same on the release-1.x branch?

mstruebing added a commit that referenced this issue Dec 15, 2023
@mstruebing
chore: move node options into npm script
a90d0f5 
I wanted to cut another RC to potentially close
* #1420
* #1398
* #1397

but the release is erroring at the test because of the memory limit
so I moved the increased memory limit node options into the npm script
rather than the Kubernetes Javascript Client - Validation workflow
@mstruebing mstruebing mentioned this issue Dec 15, 2023
Merged
mstruebing added a commit that referenced this issue Dec 15, 2023
@mstruebing
chore: switch to c8 instead of nyc
665608e 
I wanted to cut another RC to potentially close
* #1420
* #1398
* #1397

but the release is erroring at the test because of the memory limit
so I decided to use c8 instead of nyc because when trying to remove nyc
I concluded that the memory error comes from it and its last release was
4 years ago. It works as a drop-in replacement.

https://www.npmjs.com/package/c8
@mstruebing
Copy link
Member

@eyalcha I've published a new release 1.0.0-rc4: https://www.npmjs.com/package/@kubernetes/client-node/v/1.0.0-rc4
Could you confirm that this issue is solved in this release?

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 22, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mstruebing @k8s-ci-robot @k8s-triage-robot @SarthakNikhal @eyalcha