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.

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

Apply this change related to masesgroup/JNet#334 #390

Merged
merged 2 commits into from
Jan 27, 2024
Merged

Apply this change related to masesgroup/JNet#334 #390

merged 2 commits into from
Jan 27, 2024

Conversation

masesdevelopers
Copy link
Contributor

Description

Applied changes related to masesgroup/JNet#334, PR shall be closed when available a new JNet version

Related Issue

closed #389

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@masesdevelopers masesdevelopers added enhancement New feature or request Docker KNet related issue labels Jan 27, 2024
@masesdevelopers masesdevelopers self-assigned this Jan 27, 2024
…t-dockerfiles-since-384-shall-wait-jnet-long-time
@masesdevelopers masesdevelopers merged commit 2c73f27 into masesgroup:master Jan 27, 2024
7 checks passed
@masesdevelopers masesdevelopers deleted the 389-apply-this-change-in-current-dockerfiles-since-384-shall-wait-jnet-long-time branch January 27, 2024 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docker KNet related issue enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Apply this change in current Dockerfiles since #384 shall wait JNet long time
1 participant