RangeError: Max payload size exceeded

ref to: https://github.com/websockets/ws/issues/1543
[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
RangeError: Max payload size exceeded
    at Receiver.haveLength (C:\Users\CXPLAY\AppData\Local\nostr_relay_tray\app-1.2.3\resources\app.asar\node_modules\ws\lib\receiver.js:423:28)
    at Receiver.getPayloadLength16 (C:\Users\CXPLAY\AppData\Local\nostr_relay_tray\app-1.2.3\resources\app.asar\node_modules\ws\lib\receiver.js:374:10)
    at Receiver.startLoop (C:\Users\CXPLAY\AppData\Local\nostr_relay_tray\app-1.2.3\resources\app.asar\node_modules\ws\lib\receiver.js:162:16)
    at Receiver._write (C:\Users\CXPLAY\AppData\Local\nostr_relay_tray\app-1.2.3\resources\app.asar\node_modules\ws\lib\receiver.js:98:10)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Socket.socketOnData (C:\Users\CXPLAY\AppData\Local\nostr_relay_tray\app-1.2.3\resources\app.asar\node_modules\ws\lib\websocket.js:1303:35)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:335:12)

This is because I have restricted the payload maximum to 128k. You might be trying to insert a huge event.

This is because I have restricted the payload maximum to 128k. You might be trying to insert a huge event.

You're right, but I have absolutely no idea which event is causing this. Is there any option to stop the warning window from popping up?

You're right, but I have absolutely no idea which event is causing this. Is there any option to stop the warning window from popping up?

You can clone the source code, delete line 143 in main.js, and then package and run it.

In the future, I will add a settings panel to allow for setting some restrictions.


List jquery as a dependency in package.json

The reason https://github.com/twitter/typeahead.js/issues/872 happens is because jquery is not a dependency in your package.json.  Adding it should make browserify/webpack work with no extra shimming necessary. Would you be open to this? If so I can send a PR.

+1


RSpec/EmtpyLineAfterSubject triggers on Rubocop comment

    # rubocop:disable Metrics/LineLength
    subject(:document_upload) do
      DocumentUpload.new(
        document,
        confirmation_url: "http://localhost:3000//document_upload_results?result=success",
        cancellation_url: "http://localhost:3000//document_upload_results?result=failure"
      )
    end
    # rubocop:enable Metrics/LineLength

I am disabling Metrics/LineLength because of https://github.com/rubocop-hq/rubocop/issues/5916
But then I get an alert on enabling a cop again.
Versions:

rubocop (0.59.2)
rubocop-rspec (1.25.1)

Technically,
    # rubocop:enable Metrics/LineLength

is not an empty line.
    # rubocop:disable Metrics/LineLength
    subject(:long) { "ergoqiawhgpajdkjslfjszldfjlasjdflkasjdflkjaslkdfjaslkdfjalksdjflkasjdflaskjdf" }
    # rubocop:enable Metrics/LineLength
    before { ... }

is still too dense.
I can still reproduce this issue by adding the following example to spec/rubocop/cop/rspec/empty_line_after_subject_spec.rb:
  it 'handles subject followed by a comment' do
    expect_no_offenses(<<-RUBY)
      RSpec.describe User do
        subject { described_user }
        # not an empty line
        let(:foo) {}
      end
    RUBY
  end

@pirj I don't actually think that was the original problem, but @rpbaptist can correct me if I'm wrong. I believe he was using a slightly out of date version of rubocop-rspec which wouldn't allow you to do  (adapting your example) this:
it 'handles subject followed by a comment' do
    expect_no_offenses(<<-RUBY)
      RSpec.describe User do
        subject { described_user }
        # not an empty line

        let(:foo) {}
      end
    RUBY
  end

and would require you to write:
it 'handles subject followed by a comment' do
    expect_no_offenses(<<-RUBY)
      RSpec.describe User do
        subject { described_user }

        # not an empty line

        let(:foo) {}
      end
    RUBY
  end

or
it 'handles subject followed by a comment' do
    expect_no_offenses(<<-RUBY)
      RSpec.describe User do
        subject { described_user }

        # not an empty line
        let(:foo) {}
      end
    RUBY
  end

Which was pretty awkward for rubocop:enable statements. I fixed and unified all the blank line logic so it accepted any blank line between the rspec constructs, with or without comments in between.
Flagging
  it 'handles subject followed by a comment' do
    expect_no_offenses(<<-RUBY)
      RSpec.describe User do
        subject { described_user }
        # not an empty line
        let(:foo) {}
      end
    RUBY
  end

has always been intended behavior.
I'm closing this since I think the issue was an out of date rubocop-rspec, but if I'm wrong, feel free to re-open, @rpbaptist.


Sign In, Sign Out, Profile Page

[x] Give users the ability to sign in with GitHub. The Sign In button should send users directly to the GitHub Sign In page.
[x] Include a Create Account (with GitHub) in the marketing page as well, this page will take you directly to the GitHub Create your account page. Once the user creates an account, we will redirect to thenewboston website signed in.
[x] When the user signs into thenewboston, redirect them to their profile page.
[x] Once you're signed into thenewboston website, we do not need to display the Sign In & Create Account button on the top nav, we only need to display your avatar on the right of the Download button.
[x] Selecting on the avatar will display a dropdown of 2 buttons, Your Profile & Sign Out.
[x] For mobile, if you are signed in, inside the top nav, we are going to include options for 'Your Profile' & 'Sign Out'
[x] The profile page will display the users avatar (pull in their GitHub profile image), the users Display Name (filled out by the user), the users role & team, Slack Name (filled out by the user), GitHub username (link to their GitHub), account number (with QR code), & all the tasks they completed.
[x] Display the Team Lead tag on the profile if they are one.
[x] When a user is viewing their own profile, there will be a 'Edit Profile' icon. Here they can edit their Display Name, Slack Name, & Account Number.
[x] Just to note, the avatar has a white stroke (2px) around it, so it doesn't blend in with the background color.
[x] On the 1366px screens, the user info block & the task completed block thats been designed is the max width of those containers, for smaller screens, the blocks will respond according to the tablet/mobile
[x] On the leaderboard, the users github names will now link to the users profile.
[x] On the tasks page, clicking on the users avatar will link to the users profile.
[x] For mobile specifically, on the Tasks Completed section, we can remove the Repository section & the Completed section. We will move Total Earnings up to the top and we will include Total Tasks on the left.
[x] For mobile, when the user edits their profile, the edit profile should take up the whole screen. The standard pattern is, Save button will be on the top right, close button will be on the top left.
[x] We are going to update the mobile top nav by putting the Get Started & Community options into the dropdown. (Currently all the options are displayed without selecting the dropdown) We are going to do this because now that there are more options on the top nav, we need to collapse the options so the newer options are more prominent.
[x] For mobile, it is a little difficult to click the nav items with your thumb since they are so close together, so we are updating them to have 24px padding in-between.

https://www.figma.com/file/ChyT88EmP2Rmzx35I9erCL/Marketing-Site?node-id=1353%3A1915

this one is not ready for engineering yet

prereq: https://github.com/thenewboston-developers/Website/issues/461

[ ]  On the leaderboard, the users github names will now link to the users profile.
[ ]  On the tasks page, clicking on the users avatar will link to the users profile.

It seems like these two points are not done, should I create a separate PR and take on this issue? @thesanjeevsharma @Hristijan95

Just to check, are all these tasks done?

Just to check, are all these tasks done?

@jamessspanggg #1123 is still opened so should I wait until it is closed before moving it to Paid?

@jamessspanggg #1123 is still opened so should I wait until it is closed before moving it to Paid?

Closing since this is out of date. Majority is done but waiting on some backend changes. Any further changes needed we can split up into a separate ticket.


Label based multi-grid manual sorting options

Issue: Some labels do not lend themselves to alphabetical sorting.
Ex: Prod, Pre-Prod, Dev, Test. Or PP, PR, DV, TS.
If there could be some way to either do a manual sort or a hybrid manuel + alphabetical for anything not matching the manual items.
This would permit pinning the 1 or two critical items first in the right order, and whatever else comes next would be using the current sorting mechanism.
ps. I Love the idea and implementation of the multi-grid.

You can override label values for sorting via grid:sorting: customValues:labels, example:
grid:
  sorting:
    customValues:
      labels:
        severity:
          critical: 1
          warning: 2
          info: 3

This will be used for all sorting operations, including multi-grid.

Ah.. I had not clearly understood the use of the customValues: labels.
Great stuff, as always. Thank you for the answer.
The linked documentation is very clear in the text. I probably skimmed it looking at the examples and missed it.


What about "Manim.js" in javascript !?

It will be great if there is a library in javascript that can make the exact same video that manim in python does.
I checked this but it not able to perform that transformation between SVG files and even not able to perform the same writing animations.
This javascript library will also use for manipulating SVG files in HTML page, that will be great.
I just started it here but I am very confused about how should I start it?
Any guidance/help will be very appreciable.

@eulertour

I'm currently working on a javascript frontend to manim in this repo. There's a compatible version of manim on this branch.
If you want any help setting it up get in touch with me on the discord.


Showing error some time on a first attempt of installing app or creating instance

This issue is a:
[ ] Bug Report
hlw, i am beta tester,
whenever i am creating an instance or installing apps, this will take me to the Error message look like "Sorry for trouble if persist contact on mail"
but this behaviour is only in the frontend but the instance is creating in the backgroung.
Bug Reports
If the issue is a Bug Report, please detail the following:

Expected behaviour
Try to create an instance or install apps, some times you will definitely get this error.

Escalated


fix(form): ignore properties in prototype chain in $error

Closes #10469

there were some refactors on input.js and inputSpec.js can you please rebase this?

there were some refactors on input.js and inputSpec.js can you please rebase this?


Confusing output of oscar_fork_app management command

Sample output of oscar_fork_app:
> ./manage.py oscar_fork_app order apps
Creating package apps/order

Creating admin.py

Creating app config

Creating models.py

Creating migrations folder

Replace the entry 'oscar.apps.order.apps.OrderConfig' with 'apps.order.apps.OrderConfig' in INSTALLED_APPS

But there is no entry like 'oscar.apps.order.apps.OrderConfig' in INSTALLED_APPS.
Based on Oscar docs there is only 'oscar.apps.order'.
Probably instead of app_config_class_path here:
https://github.com/django-oscar/django-oscar/blob/e347ad9ed052e82eb275d3bb32500f3f5f225007/src/oscar/core/customisation.py#L122-L129
we should use app_config.name.
I can prepare a PR to change the current behavior. Please comment. Thanks.

I would prefer that we update the documentation on setting up a project to use the explicit app configs in the settings (i.e., the INSTALLED_APPS should contain oscar.apps.order.apps.OrderConfig), which is the recommended approach by Django. This will then make the output of the command correct.

@solarissmoke Thanks!
I will create a PR to update the documentation then.


Connected but I can't write in console?!

Checklist

[X] Checked the issue tracker for similar issues to ensure this is not a duplicate
[X] Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
[X] Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?
always
Expected behavior
I went to this page:
https://espressif.github.io/esptool-js/
I rebooted the ESP32 with both button pressed.
Then I flashed the latest micropython firmware.
Then I connected the "console"
If I hit the reset button I see this:
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4892
ho 0 tail 12 room 4
load:0x40078000,len:14896
load:0x40080400,len:4
load:0x40080404,len:3372
entry 0x400805b0
MicroPython v1.24.1 on 2024-11-29; Generic ESP32 module with ESP32
Type "help()" for more information.
>>>

Whetever I write at the >>> prompt is not echoed and even pressing return is not executed.
Actual behavior (suspected bug)
I would expect to interactively write to the console.
Error logs or terminal output
Non errors anywhere, not even in javascript console.

Steps to reproduce the behavior
As in the first description.
Project release version
latest
System architecture
Intel/AMD 64-bit (modern PC, older Mac)
Operating system
Windows
Operating system version
Windows 10
Shell
other (details in Additional context)
Additional context
No response

This is not a real terminal just a console output terminal.


Change origin for spark.hadoop.hive.llap.daemon.service.hosts

Minor change - step 4d under Hive Warehouse Connector setup should technically be pulled from hive.llap.daemon.service.hosts from the Hive cluster's Advanced hive-interactive-site config section.  This gives you '@llap0'.
LLAP App Name under the Advanced hive-interactive-env configs is just 'llap0'.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f4c331d3-c2cd-977d-b253-07dc0b3672a1
Version Independent ID: d38338d5-aad7-1e6d-4a4f-89c73623e1fc
Content: Integrate Apache Spark and Apache Hive with the Hive Warehouse Connector
Content Source: articles/hdinsight/interactive-query/apache-hive-warehouse-connector.md
Service: hdinsight
GitHub Login: @nakhanha
Microsoft Alias: nakhanha

@arerlend Thanks for your contribution, I've addressed this issue in PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/84419.
The changes should be live EOD or tomorrow. We will now close this issue. In future, if you see any minor bug fixes in the doc, feel free to click on the edit button and submit a PR to update. we love to take community contributions.


Pass in -m option to check-templates

Feel free to squash/modify these as you see fit, if there aren't any major issues to be discussed.

Automated message from Dropbox CLA bot
@showell, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@showell, thanks for signing the CLA!

Since lint-all currently is designed to not produce output in the event of no errors, I think you should move the print statements under a --verbose option.
While you're at it, you can fix the Python 3 compatibility :)
Otherwise looks great!

How do you feel about simply omitting the print statements?  (They were introduced in this pull request, so it wouldn't be a regression for anybody.)

That's reasonable.

27484ad was my modified commit from last time.  Not sure what the protocol is for rewriting history on pull requests.

Just do a force-push to the branch the pull request was based on with the new version (there are no concerns about rewriting PR history).  And we still merge individual commits, so keep the commits themselves clean :)

I think the commit I flagged as squashed should be squashed with the second, and the last commit also stands alone, but the middle commits are sort of personal preference.  They were individually tested.  Any thoughts?

Honestly I'm happy to keep the commits you have as-is, with just a real commit message for the first one.  It's a lot easier to read this way, and there's no real cost to extra commits in the history

On a somewhat related issue, check-templates skips over some Django files that have unusual HTML in them, which I punted on parsing when I wrote this tool initially.  Here is one snippet in base.html.
    <!-- HTML5 shim, for IE6-8 support of HTML5 elements -->
    <!--[if lt IE 9]>
      <script src="https://html5shim.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->

Before I hack check-templates to support the ![endif] syntax, I'm wondering if we still really support the IE shim.

I merged the -m stuff; thanks @showell!  Feel free to either keep using this PR or open a new one for the tag issue stuff.  One thing I forgot to mention is that you can include e.g. Fixes: #123 in the commit message of the commit fixing an issue, and then the GitHub issue will auto-close when the commit is merged.
I think Zulip does currently work with IE8, so we should keep that shim, but it's probably not something we'll need long-term.

Thanks for pushing the -m stuff, @timabbott. Can you please have somebody look over dab1869?  It's a small change; I just want a second pair of eyes that nothing broke the formatting for the API help page.
I'm just gonna leave base.html alone for now.

Sounds reasonable, merged!

Thanks!  You will find subsequent HTML cleanup commits on #1198


Add web streams

Add the ability to stream web requests.
Streaming Requests is not possible at the moment. Try integrating that as well.

https://medium.com/python-pandemonium/how-to-serve-http-2-using-python-5e5bbd1e7ff1
https://medium.com/python-pandemonium/how-to-serve-http-2-using-python-5e5bbd1e7ff1


Add Elixir textobjects

There may be some incompatible parts.  😅

function: with/without condition, do block/inline, anonymous_function
class: actually it is module
comment: heredoc docs only
block

Thanks!


[Test revamp][change][2211]

Please review.

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/messaging-extensions/doc-revamp-test.md
87
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 0b81245:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/doc-revamp-test.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add step to publishToMavenLocal in the build script

Description
Adds a step to publishToMavenLocal in the security plugin's build script. This will resolve an issue in the distribution build where flow framework is trying to get a "release" (non-snapshot) artifact of the security plugin at build time. See related issue here. The job-scheduler plugin runs this step in its build.sh script.

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance
Issues Resolved

https://github.com/opensearch-project/flow-framework/issues/410

Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Moved this to draft. ./gradlew publishToMavenLocal is failing locally for me with the following error:
➜  security git:(publish-to-maven-local) ✗ ./gradlew publishToMavenLocal
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.5
  OS Info               : Mac OS X 14.2.1 (aarch64)
  JDK Version           : 11 (Amazon Corretto JDK)
  JAVA_HOME             : /Users/cwperx/.sdkman/candidates/java/11.0.21-amzn
  Random Testing Seed   : 2C9F75A6312C4D23
  In FIPS 140 mode      : false
=======================================
> Task :generatePomFileForNebulaPublication FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':generatePomFileForNebulaPublication' (type 'GenerateMavenPom').
  - Gradle detected a problem with the following location: '/Users/cwperx/Projects/opensearch/security/build/distributions/opensearch-security-<IP_ADDRESS>-SNAPSHOT.pom'.

    Reason: Task ':publishMavenPublicationToMavenLocal' uses this output of task ':generatePomFileForNebulaPublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':generatePomFileForNebulaPublication' as an input of ':publishMavenPublicationToMavenLocal'.
      2. Declare an explicit dependency on ':generatePomFileForNebulaPublication' from ':publishMavenPublicationToMavenLocal' using Task#dependsOn.
      3. Declare an explicit dependency on ':generatePomFileForNebulaPublication' from ':publishMavenPublicationToMavenLocal' using Task#mustRunAfter.

    For more information, please refer to https://docs.gradle.org/8.5/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 2s
15 actionable tasks: 5 executed, 10 up-to-date

@cwperks you can refer https://github.com/opensearch-project/flow-framework/pull/226 to fix the above error?

@reta any idea why flow-framework cannot get the security zip? If this line is in security's build.sh:
./gradlew publishPluginZipPublicationToZipStagingRepository -Dopensearch.version=$VERSION -Dbuild.snapshot=$SNAPSHOT -Dbuild.version_qualifier=$QUALIFIER
Shouldn't the artifact be being published for other plugins to consume? This command works for me locally and publishes to <OPENSEARCH_SECURITY_ROOT>/build/local-staging-repo.

@cwperks @peternied we shouldn't publish JARs to Apache Maven, but the ZIP distribution only (which is done on the next line)

@reta Totally agreed; however, this change doesn't publish externally - I'm pretty sure you had the same reaction I did when I first saw this PR (I requested changes and then accepted).  The build script is used when the distribution build is created and the command is publishToMavenLocal where the same machine in jenkins is used to build all of the artifacts in one place.
OpenSearch publishes to maven local in its scripts/build.sh

The build script is used when the distribution build is created and the command is publishToMavenLocal where the same machine in jenkins is used to build all of the artifacts in one place.

Why should build script be published? It is owned by security plugin and only, but publishing it you would introduce a) build split brain (why only internal? what if someone accidentally publish it?) b) maintenance load for a team to maintain publishing artifacts that not needed

I switched this to using publishPluginZipPublicationToMavenLocal, same as k-NN.
I'm trying to figure out how job-scheduler publishes the zip during distribution build times for dependent plugins.

Why should build script be published?

@reta This script is used by the distribution build process docs which operates differently than gradle builds.  This problem was discovered when attempting to run the integration tests against a distribution build.  I'm not if there is another kind of approach that could address this, do you have other ideas?
@zelinh Would you mind reviewing this PR and is there more context you can provide for the questions that @.reta has called out?

@reta This script is used by the distribution build process docs which operates differently than gradle builds.

Hm ... I see it needs ZIP and with the ZIP publishing to Mavel Local, we should be all set:
 zipArchive group: 'org.opensearch.plugin', name:'opensearch-security', version: "${opensearch_build}"

@zelinh How does opensearch-build allow plugins to have a zipArchive dependency on job-scheduler? From what I am looking at in job-scheduler's build script it is not publishing the zip to maven local. There are lines in job-scheduler's build script to copy the zip to $OUTPUT/plugins.
I'm not sure if this is connected, but I see special handling for job-scheduler in opensearch-build. Is this how plugins are able to have a zipArchive dependency on job-scheduler (Example from AD)?

Switched back to draft to prevent this from being merged. I'd like to understand how zipArchive dependency works for the integ tests in greater detail. Other plugins do not publish the zip to maven local even when other plugins have a zipArchive dependency on them (example from security-analytics which has a zipArchive dependency on alerting), so this may not be necessary for the security plugin

Let me explain this based on what I understood:
The zipArchive is a custom configuration that has been added in the configurations block. This configuration is used to group and declare dependencies related to OpenSearch plugins. It doesn't have a predefined meaning in Gradle rather, it's a configuration name chosen by the build script author.
configurations {
    zipArchive
}

By creating a custom configuration like zipArchive, the build script author can organize dependencies based on their purpose or use case. It's a way to group dependencies that share a common characteristic or belong to a specific category.
Now In the dependencies block, the OpenSearch plugin dependencies are associated with the zipArchive configuration:
Example as
dependencies {
    zipArchive group: 'org.opensearch.plugin', name:'alerting', version: "${opensearch_build}"
    zipArchive group: 'org.opensearch.plugin', name:'opensearch-notifications-core', version: "${opensearch_build}"
    zipArchive group: 'org.opensearch.plugin', name:'notifications', version: "${opensearch_build}"
    zipArchive group: 'org.opensearch.plugin', name:'opensearch-job-scheduler', version: "${opensearch_build}"
}

This means that these dependencies are associated with the zipArchive configuration when you later run a task that requires the zipArchive configuration (e.g compiling code that depends on these plugins), Gradle will only then download and include these dependencies in the classpath for that task. Just declaring under dependencies and not using zipArchive will not download those dependencies.
So @cwperks the Example from AD even though it has  zipArchive group: 'org.opensearch.plugin', name:'opensearch-job-scheduler', version: "${opensearch_build}" It later never used the opensearch-job-scheduler.
Same with K-NN even though it has zipArchive group: 'org.opensearch.plugin', name:'opensearch-security', version: "${opensearch_build}" since it never uses zipArchive the 2.12.0 build passed for k-NN.
Now coming back to flow-framework and neural-search plugin it explicitly uses the zipArchive,
https://github.com/opensearch-project/neural-search/blob/2.x/build.gradle#L64-L83
configurations.zipArchive.asFileTree.each {
            if(it.name.contains("opensearch-security")){

Since security is not publishing to maven local gradle finds and fails the build as dependency not found with configuration zipArchive
A problem occurred evaluating root project 'opensearch-flow-framework'.
> Could not resolve all files for configuration ':zipArchive'.
   > Could not find org.opensearch.plugin:opensearch-security:<IP_ADDRESS>.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/opensearch/plugin/opensearch-security/<IP_ADDRESS>/opensearch-security-<IP_ADDRESS>.pom
       - file:/usr/share/opensearch/.m2/repository/org/opensearch/plugin/opensearch-security/<IP_ADDRESS>/opensearch-security-<IP_ADDRESS>.pom
       - https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/opensearch-security/<IP_ADDRESS>/opensearch-security-<IP_ADDRESS>.pom
       - https://plugins.gradle.org/m2/org/opensearch/plugin/opensearch-security/<IP_ADDRESS>/opensearch-security-<IP_ADDRESS>.pom
     Required by:
         project

This used to work for neural-search 2.11.0 release  where then it does not have explicit zipArchive opensearch-security. This was added for 2.12.0 and the story should be the same for flow-framework.
Adding @gaiksaya @vibrantvarun @bbarani @jmazanec15 @owaiskazi19

@prudhvigodithi Do you think it makes sense to add a step to publish to maven local for the security zip as part of security's build script? This PR should resolve Flow Framework's issue, but I'd like guidance from EE if this is the best way to fix their issue.


Add TypeScript Support

I would like to use TypeScript to program games in TIC-80

Native support is overkill, just use TypeScript compiler.

I think it's too heavy to embed whole Typescript Compiler to so tiny app
pls use smth like https://github.com/scambier/tic80-typescript in this case
thanks


Support adding GPG signing sub-key

Type : Feature request
Description
As @a1012112796 has mentioned in https://github.com/go-gitea/gitea/issues/14009#issuecomment-746558233 "Now gitea only allow add public gpg keys bounded with the user's email", it would be nice if Gitea also support adding GPG sub-key, just like mention in issue https://github.com/go-gitea/gitea/issues/14009.

Currently, the email address cannot be kept private when using the PGP key feature. So this issue is more a bugfix than a feature.

Currently, the email address cannot be kept private when using the PGP key feature. So this issue is more a bugfix than a feature.

#14054 was an attempt at fixing this issue - however, due to the lack of real life testing of this feature I've had to move it to the 1.15 milestone. Hopefully we'll merge after the merge window for 1.14 is closed.
If you really want this feature in 1.14 you will need to download and test this PR to ensure that it does what you want.


Ubuntu gcc12

Base: 62.13% // Head: 32.95% // Decreases project coverage by -29.17% warning

Fake news.

Base: 62.13% // Head: 32.95% // Decreases project coverage by -29.17% warning

Fake news.


fix error handling in packager

Currently on error I have following output:
 ERROR  Packager can't listen on port 8081
Most likely another process is already using this port
Run the following command to find out which process:

   lsof -n -i4TCP:8081

You can either shut down the other process:

   kill -9 <PID>

or run packager on different port.

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.
/Users/nucleartux/Work/projects/react-native/local-cli/server/server.js:90
    if (error.code === 'EADDRINUSE') {
             ^

TypeError: Cannot read property 'code' of undefined
    at process.<anonymous> (/Users/nucleartux/Work/projects/react-native/local-cli/server/server.js:104:14)
    at emitOne (events.js:77:13)
    at process.emit (events.js:169:7)
    at process._fatalException (node.js:211:26)

This makes sense because the server command doesn't really use promises so this makes total sense. Thanks for fixing it! :)

@facebook-github-bot shipit


Proper Logging

Probably a good idea to stop using print statements as still-alive indicators.
By default, set log message severity to Warning?
https://docs.python.org/3/library/logging.html#levels
It should be possible for the user to temporarily change loglevels from the default with something like
# Get the currently-active logger and set it to display DEBUG + higher-severity messages
logging.getLogger().setLevel(logging.DEBUG)

Not really necessary and may just add bloat.


Installing .NET 6 on Ubuntu 22.04 (Jammy)

Installing .NET 6 on Ubuntu 22.04 (Jammy)
We announced support for .NET 6 on Ubuntu 22.04 with our May 2022 Updates. At that time, the supported installation methods were manual installation via a tarball or a .deb package via packages.microsoft.com (PMC). .NET 6 is now available natively via Jammy feeds, which can cause conflicts with PMC feeds. You need to apply the following guidance to install .NET 6 reliably and correctly on Ubuntu 22.04+.
More information will be shared shortly on .NET 6 being available natively in the jammy-updates feed. In general, we recommend that you use the native packages from this feed since it is much easier and simpler.
You can use one of the following scenarios:

The first two scenarios assume a clean machine. You want .NET 6 packages and haven't installed them before.
The second two scenarios assume you're machine is in a mixed-state, that you've installed .NET 6 packages before and don't have the ones you want or are in a bad state.

Related:

https://github.com/dotnet/core/issues/7713

Clean machine scenario 1: Use .NET 6 Package via Jammy feed
The easiest approach is to use the .NET 6 package available in Jammy feeds. In this scenario, just install dotnet6 and don't register the PMC feed.
You can do that via the following commands:
sudo apt update && sudo apt -y install dotnet6

You can see this demonstrated with Docker:
$ docker run --rm -it ubuntu:jammy
root@4c9d58f507a3:/# apt update && apt install -y dotnet6
root@444999ffd672:/# dotnet --version
6.0.108

Note: This build of .NET 6 is for the 6.0.1xx band.  6.0.4xx builds are available via PMC. That difference matters most to Windows users. Both builds are supported.
Clean machine scenario 2: Use .NET 6 Package via PMC
You can install .NET 6 on Ubuntu 22.04 from packages.microsoft.com  using the following steps:
wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

Configure apt preferences, to prioritize PMC repository, by creating the following file: /etc/apt/preferences
To create the file:
sudo touch /etc/apt/preferences

with contents:
Package: *
Pin: origin "packages.microsoft.com"
Pin-Priority: 1001

Update your APT information:
sudo apt update
Install .NET SDK 6.0:
sudo apt install dotnet-sdk-6.0
Mixed state scenario 1: Use native Jammy packages after installing a previous .NET release from PMC
You may want to switch to using the .NET 6 package available in Jammy after installing .NET 6 from PMC.
Do the following:

Remove all .NET packages

sudo apt remove --purge dotnet*
sudo apt remove --purge aspnetcore*

Delete PMC repository from APT, using any of the typical methods, for instance by deleting the repo .list file

sudo rm /etc/apt/sources.list.d/microsoft-prod.list

Update APT

sudo apt update

Install .NET SDK 6.0

sudo apt install dotnet-sdk-6.0
Mixed state scenario 2: Use PMC packages after installing native Jammy packages
You may want to switch to using packages.microsoft.com packages after installing native packages, potentially because you want to use 6.0.4xx builds.
Do the following:

Remove all .NET packages

sudo apt remove --purge dotnet*
sudo apt remove --purge aspnetcore*

Create apt preferences file as specified in the section above
Install .NET SDK 6.0

sudo apt install dotnet-sdk-6.0
How to identify which packages you'd installed
We'll install .NET 6 with both feeds, from a clean state, and then point the various ways you can identify which feed you installed the package from.
First, let's install the native Jammy packages using the "Clean machine scenario 1" guidance.
rich@kamloops:~$ docker run --rm -it ubuntu:jammy
root@db7fd8ec177e:/# apt update && apt install -y dotnet6
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet6 amd64 6.0.108-0ubuntu1~22.04.1 [20.5 kB]
root@db7fd8ec177e:/# dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.108
 Commit:    4e3a463d2b

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  22.04
 OS Platform: Linux
 RID:         ubuntu.22.04-x64
 Base Path:   /usr/lib/dotnet/dotnet6-6.0.108/sdk/6.0.108/

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  6.0.108 [/usr/lib/dotnet/dotnet6-6.0.108/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

Notice that we've installed .NET SDK 6.0.108, installed to /usr/lib/dotnet/, and that the dotnet6 package is being installed from http://archive.ubuntu.com/ubuntu jammy-updates/universe. That's expected for the native packages.
Let's try the same thing with PMC, but with the "Clean machine scenario 2" guidance.
rich@kamloops:~$ docker run --rm -it ubuntu:jammy
root@626dcadc888b:/# apt update && apt install -y wget
root@626dcadc888b:/# wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
root@626dcadc888b:/# dpkg -i packages-microsoft-prod.deb
root@626dcadc888b:/# rm packages-microsoft-prod.deb
root@626dcadc888b:/# touch /etc/apt/preferences
root@626dcadc888b:/# echo "Package: *" >> /etc/apt/preferences
root@626dcadc888b:/# echo "Pin: origin \"packages.microsoft.com\"" >> /etc/apt/preferences
root@626dcadc888b:/# echo Pin-Priority: 1001 >> /etc/apt/preferences
root@626dcadc888b:/# cat /etc/apt/preferences
Package: *
Pin: origin "packages.microsoft.com"
Pin-Priority: 1001
root@626dcadc888b:/# apt update && apt -y install dotnet-sdk-6.0
Get:11 https://packages.microsoft.com/ubuntu/22.04/prod jammy/main amd64 dotnet-sdk-6.0 amd64 6.0.400-1 [86.4 MB]
root@626dcadc888b:/# dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.400
 Commit:    7771abd614

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  22.04
 OS Platform: Linux
 RID:         ubuntu.22.04-x64
 Base Path:   /usr/share/dotnet/sdk/6.0.400/

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  6.0.400 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

Notice that we've installed .NET SDK 6.0.400, installed to /usr/share/dotnet/, and that the dotnet6 package is being installed from https://packages.microsoft.com/ubuntu/22.04/prod jammy/main. That's expected for PMC packages.
We can also tell if the Microsoft PMC feed is registered:
root@626dcadc888b:/# ls /etc/apt/sources.list.d/
microsoft-prod.list
root@626dcadc888b:/# cat /etc/apt/sources.list.d/microsoft-prod.list
deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/ubuntu/22.04/prod jammy main

If you are using native packages, that file won't and shouldn't be present.

Should we add these to https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-mixup ?

Should we add these to https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-mixup ?

A set of modifications for the page was here too: https://github.com/dotnet/docs/issues/30457#issuecomment-1209280875

https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#2204 should be updated too.

There is one issue, for PMC, dotnet stop recognizing any SDK versions (on the 6.0.400 SDK update)
Host:
Version:      6.0.8
Architecture: x64
Commit:       55fb7ef977
.NET SDKs installed:
No SDKs were found.
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info

I'm having the exact same problem

Can you elaborate @bastare?

Tried the steps but to no avail.
Ubuntu 22.04
$ dn --info

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

This is specific to package version 6.0.8+. Downgrading to 6.0.7 resulted in the SDK showing.

Did folks who are having this problem follow the instructions? If so, did you go with scenario 1 or 2?

Thanks so much, I've been trying to fix the error for hours, Scenario 1 did it for me.

I updated the scenarios to make it clearer. We now have two "Clean machine" scenarios and two "Mixed-state" scenarios.
BTW: We are very sorry that this situation occurred. We should have predicted that it would but sadly did not. That's on us. We've learned that mix-and-matching package feeds with the same package names that install to different locations is a recipe for what we're seeing here. Again, we're sorry about that and won't repeat it.

Why is there this sudden change of installation steps?
Is this going to be the one used moving forward?

What do we do if we want powershell installed from PMC but to install SDK from jammy repo?
Also removing and re-installing dotnet* and aspnetcore* did not fix the issue for me either.

Did folks who are having this problem follow the instructions? If so, did you go with scenario 1 or 2?

After some trial and error, found this github issue and went with "Clean machine scenario 2: Use .NET 6 Package via PMC" as this allows using the latest dotnet 6 sdk version.  These instructions worked well.

How can I get dotnet 5 SDK installed on 22.04 ?
Its not supported using packages.
does this mean i cant use the native packages if i want to use SDK 5 & 6 ?

In our company we're using a mirror with the same starting url for both feeds - PMC and Ubuntu sources.
Hence pinning won't work by setting
Pin: release mirror.company.com

Instead the following configuration works for me:
Package: *
Pin: release o=microsoft-ubuntu-jammy-prod jammy, n=jammy, a=jammy, c=main
Pin-Priority: 1001

Just in case anybody has a similar issue...

@mickdelaney Only .NET 6+ is supported on Ubuntu 22.04. That's unrelated to this discussion. See: https://github.com/dotnet/core/issues/7038#issuecomment-1110377345
.NET 6 is our first release to support OpenSSL v3. Ubuntu 22.04 only includes OpenSSL v3. As a result .NET 5 cannot function. You can install OpenSSL v1.x yourself if needed. We don't support that. Same thing with .NET Core 3.1. Also, .NET 5 is EOL.

Why is there this sudden change of installation steps? Is this going to be the one used moving forward?

We've been working with Canonical to make .NET available in the official feeds. That landed last week. We're making an official announcement tomorrow to better describe the change. This is a case where technical and marketing dates didn't match, sadly. We tried our best to resolve this situation by posting this issue with these instructions within a couple hours of realizing what had happened. We've updated the instructions a few times based on feedback and better understanding the mechanics to help users adapt to the new packages.

Tried the steps but to no avail. Ubuntu 22.04
$ dn --info

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

@khteh which exact scenario steps were attempted? We have steps for 2 clean and 2 mixed scenarios.

What do we do if we want powershell installed from PMC but to install SDK from jammy repo?
Also removing and re-installing dotnet* and aspnetcore* did not fix the issue for me either.

@ar0311 which exact scenario steps were attempted? We have steps for 2 clean and 2 mixed scenarios.

Tried the steps but to no avail. Ubuntu 22.04
$ dn --info

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

I had the same issue and I tried the Mixed state scenario 2 and it works

The official Jammy .NET package is not fit for purpose and conflicts with software like Discord.
This used to work absolutely fine with the the PMC packages. Whilst I'm supportive of making .NET more widely available like this, and easier to install, this seems like a step backwards.
I'm now having to work-around this by messing with /etc/apt/preferences - not a great developer experience.

There is a Canonical bug tracking this: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/1984450

In case this helps anyone, I had to add a step to mixed-state scenario 2. I was not able to install the PMC packages until I purged and reinstalled the PMC repository like this:
sudo dpkg --purge packages-microsoft-prod
sudo dpkg -i packages-microsoft-prod.deb
sudo apt update

You can verify that the repository is working by running apt-cache policy dotnet-sdk-6.0. You should see a whole bunch of entries from packages.microsoft.com. If you only see entries from archive.ubuntu.com, then the repository is broken and dotnet will be installed from canonical repositories even if you pinned the packages in apt preferences file.

.NET SDK version from Jammy package repo is outdated. The current version is 6.0.108 instead of 6.0.400

Hi @sakno,
unfortunately, 6.0.4xx cannot be built from source for Ubuntu (nor for Linux distros in general)  because it's not supported:

https://github.com/dotnet/source-build#support
https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/1984451/comments/4

Hi @sakno,
unfortunately, 6.0.4xx cannot be built from source for Ubuntu (nor for Linux distros in general) because it's not supported:
* https://github.com/dotnet/source-build#support

* https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/1984451/comments/4

OMG, switching back to packages.microsoft.com

OMG, switching back to packages.microsoft.com

Could you share more information about what missing features in 6.0.1xx motivate the switch?

@omajid , sure. The latest version of SDK has some updates on Roslyn compiler. I found that my code can be compiled on the earlier versions but not on the latest. For instance,
using System;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;

public struct C {
    private int value;

    private Span<byte> Span => MemoryMarshal.AsBytes(MemoryMarshal.CreateSpan(ref value, 1));
}

Thus, the latest Roslyn update introduces incompatible changes at the source level.

Oh. I thought you meant the opposite...
Ubuntu has the older 6.0.1xx SDK (with older Roslyn), compared to packages.microsoft.com. If I am reading your concerns correctly, you want to avoid packages.microsoft.com?

@omajid , no, I can't use it because as a maintainer of OSS project I need to be sure that everyone who cloned the repo is able to build the project locally (and remotely on Azure DevOps). So, everything that can be compiled on 6.0.4x can be compiled on 6.0.1x but not vice versa.

When will support for Arm64 .NET 6 come to the Ubuntu package? It's not available when I try to install it. This website says it's only for amd64 (aka x86_64), but Microsoft's download page also provides binaries for Arm32 and Arm64 Linux. Please add the Arm64 architecture version to the Ubuntu package.

Is Microsoft released package for .net 7 sdk on 22.04?

When will support for Arm64 .NET 6 come to the Ubuntu package? It's not available when I try to install it. This website says it's only for amd64 (aka x86_64), but Microsoft's download page also provides binaries for Arm32 and Arm64 Linux. Please add the Arm64 architecture version to the Ubuntu package.

We're working on it.

Upgraded to ubuntu 22 and hit this problem. I want the latest version, from the MS repo, not an older version from canonical. I've tried every approach but none worked (for me).
Does someone have a working script that installs from the MS repo?

@lonix1
I have used dotnet-install.sh and installed dotnet sdk 6.0.400 and runtime in home/.dotnet folder, it worked alongside existing version (6.0.108) installed in the system with package manager. I'm not sure, if it is possible to remove the version from package manager, and use dotnet-install.sh to install latest version into systems' folders for all users.

Upgraded to ubuntu 22 and hit this problem. I want the latest version, from the MS repo, not an older version from canonical. I've tried every approach but none worked (for me).
Does someone have a complete working script that installs from the MS repo?

I removed all the packages and went for manual install using the dotnet-install.she also, works for me

Thanks guys. What eventually worked for me was this approach. It uses apt pinning.

Hello, I'm confused over whether to install the dotnet-sdk-6.0 or dotnet6 package. I followed "Mixed state scenario 1: Use native Jammy packages after installing a previous .NET release from PMC" and installed dotnet-sdk-6.0 and all is well (I have an sdk and runtime listed in dotnet --info), but throughout this thread it often states to install package dotnet6, which do I want?

I just installed (on Ubuntu 22.04):
sudo apt install dotnet6

then when I
dotnet --list-sdks

Nothing shows up.
Then when I attempt to build a package, I get
> dotnet build
The command could not be loaded, possibly because:
  * You intended to execute a .NET application
        The application build does not exist.
  *  You intended to execute a .NET SDK command
        No .NET SDKs were found.

However, the install log says other wise...
Ubuntu apt install log
➜  ~
 sudo apt remove dotnet\*
[sudo] password for filbot:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'dotnet-hostfxr-3.1' for glob 'dotnet*'
Note, selecting 'dotnet-hostfxr-6.0' for glob 'dotnet*'
Note, selecting 'dotnet-sdk-6.0' for glob 'dotnet*'
Note, selecting 'dotnet6' for glob 'dotnet*'
Note, selecting 'dotnet-targeting-pack-6.0' for glob 'dotnet*'
Note, selecting 'dotnet-nightly' for glob 'dotnet*'
Note, selecting 'dotnet-templates-6.0' for glob 'dotnet*'
Note, selecting 'dotnet-host' for glob 'dotnet*'
Note, selecting 'dotnet-runtime-deps-3.1' for glob 'dotnet*'
Note, selecting 'dotnet-runtime-deps-6.0' for glob 'dotnet*'
Note, selecting 'dotnet' for glob 'dotnet*'
Note, selecting 'dotnet-sdk-6.0-source-built-artifacts' for glob 'dotnet*'
Note, selecting 'dotnet-apphost-pack-3.1' for glob 'dotnet*'
Note, selecting 'dotnet-apphost-pack-6.0' for glob 'dotnet*'
Note, selecting 'dotnet-runtime-6.0' for glob 'dotnet*'
Package 'dotnet' is not installed, so not removed
Package 'dotnet-nightly' is not installed, so not removed
Package 'dotnet-sdk-6.0-source-built-artifacts' is not installed, so not removed
Package 'dotnet-templates-6.0' is not installed, so not removed
Package 'dotnet-apphost-pack-3.1' is not installed, so not removed
Package 'dotnet-hostfxr-3.1' is not installed, so not removed
Package 'dotnet-runtime-deps-3.1' is not installed, so not removed
Package 'dotnet-runtime-deps-6.0' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  aspnetcore-targeting-pack-6.0 liblttng-ust-common1 liblttng-ust-ctl5 liblttng-ust1 libunwind-13 netstandard-targeting-pack-2.1
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  aspnetcore-runtime-6.0 dotnet-apphost-pack-6.0 dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0 dotnet-targeting-pack-6.0 dotnet6
0 upgraded, 0 newly installed, 8 to remove and 11 not upgraded.
After this operation, 474 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 72398 files and directories currently installed.)
Removing dotnet6 (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-sdk-6.0 (6.0.400-1) ...
Removing aspnetcore-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-apphost-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-hostfxr-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-host (6.0.108-0ubuntu1~22.04.1) ...
Removing dotnet-targeting-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
➜  ~
 sudo apt install dotnet6
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  aspnetcore-runtime-6.0 dotnet-apphost-pack-6.0 dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0 dotnet-targeting-pack-6.0
The following NEW packages will be installed:
  aspnetcore-runtime-6.0 dotnet-apphost-pack-6.0 dotnet-host dotnet-hostfxr-6.0 dotnet-runtime-6.0 dotnet-sdk-6.0 dotnet-targeting-pack-6.0 dotnet6
0 upgraded, 8 newly installed, 0 to remove and 11 not upgraded.
Need to get 124 MB of archives.
After this operation, 474 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet-targeting-pack-6.0 amd64 6.0.108-0ubuntu1~22.04.1 [2238 kB]
Get:2 https://packages.microsoft.com/ubuntu/22.04/prod jammy/main amd64 dotnet-sdk-6.0 amd64 6.0.400-1 [86.4 MB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet-host amd64 6.0.108-0ubuntu1~22.04.1 [156 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet-hostfxr-6.0 amd64 6.0.108-0ubuntu1~22.04.1 [154 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet-runtime-6.0 amd64 6.0.108-0ubuntu1~22.04.1 [23.7 MB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 aspnetcore-runtime-6.0 amd64 6.0.108-0ubuntu1~22.04.1 [8090 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet-apphost-pack-6.0 amd64 6.0.108-0ubuntu1~22.04.1 [3735 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 dotnet6 amd64 6.0.108-0ubuntu1~22.04.1 [20.5 kB]
Fetched 124 MB in 7s (17.2 MB/s)
Selecting previously unselected package dotnet-targeting-pack-6.0.
(Reading database ... 68662 files and directories currently installed.)
Preparing to unpack .../0-dotnet-targeting-pack-6.0_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-targeting-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package dotnet-host.
Preparing to unpack .../1-dotnet-host_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-host (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package dotnet-hostfxr-6.0.
Preparing to unpack .../2-dotnet-hostfxr-6.0_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-hostfxr-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package dotnet-runtime-6.0.
Preparing to unpack .../3-dotnet-runtime-6.0_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package aspnetcore-runtime-6.0.
Preparing to unpack .../4-aspnetcore-runtime-6.0_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking aspnetcore-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package dotnet-apphost-pack-6.0.
Preparing to unpack .../5-dotnet-apphost-pack-6.0_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-apphost-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Selecting previously unselected package dotnet-sdk-6.0.
Preparing to unpack .../6-dotnet-sdk-6.0_6.0.400-1_amd64.deb ...
Unpacking dotnet-sdk-6.0 (6.0.400-1) ...
Selecting previously unselected package dotnet6.
Preparing to unpack .../7-dotnet6_6.0.108-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet6 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-host (6.0.108-0ubuntu1~22.04.1) ...
update-alternatives: using /usr/lib/dotnet/dotnet6-6.0.108/dotnet to provide /usr/bin/dotnet (dotnet) in auto mode
update-alternatives: warning: skip creation of /usr/share/bash-completion/completions/dotnet because associated file /usr/lib/dotnet/dotnet6-6.0.108/bash-completion/completions/dotnet (of link group dotnet) doesn't exist
Setting up dotnet-apphost-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-targeting-pack-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-hostfxr-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up aspnetcore-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-sdk-6.0 (6.0.400-1) ...
This software may collect information about you and your use of the software, and send that to Microsoft.
Please visit http://aka.ms/dotnet-cli-eula for more information.
Welcome to .NET!
---------------------
Learn more about .NET: https://aka.ms/dotnet-docs
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli-docs

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

Configuring...
--------------
A command is running to populate your local package cache to improve restore speed and enable offline access. This command takes up to one minute to complete and only runs once.
Setting up dotnet6 (6.0.108-0ubuntu1~22.04.1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Failed to retrieve available kernel versions.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
➜  ~
 dotnet --list-sdks
➜  ~
 dotnet build
The command could not be loaded, possibly because:
  * You intended to execute a .NET application:
      The application 'build' does not exist.
  * You intended to execute a .NET SDK command:
      No .NET SDKs were found.

Download a .NET SDK:
https://aka.ms/dotnet-download

Learn about SDK resolution:
https://aka.ms/dotnet/sdk-not-found

Am I missing something?

@FilBot3 Thanks for the install log. It shows this bit:
Setting up aspnetcore-runtime-6.0 (6.0.108-0ubuntu1~22.04.1) ...
Setting up dotnet-sdk-6.0 (6.0.400-1) ...

The first package here is from the Ubuntu repositories. The second is from packages.microsoft.com. You are in a mixed state and that's why things don't work. See "Mixed state scenario 1" or "Mixed state scenario 2" from the top post in this issue and follow that advice.

Ah,yeah. Removing the microsoft-prod deb source and updating helped.
sudo apt remove dotnet\*
sudo rm /etc/apt/sources.iist.d/microsoft-prod.list
sudo apt update
sudo apt install -y dotnet6

However, I may have a similar issue on Fedora next...

For Fedora, see https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-mixup#solutions

Yup, same thing on Fedora.
sudo rm /etc/yum.repos.d/microsoft-prod.repo
sudo dnf remove dotnet\*
sudo dnf install dotnet-sdk-6.0

I am fixed now.

Tried the steps but to no avail. Ubuntu 22.04
$ dn --info

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

I resolve the same problem by installing runtimes first then SDK. I run "sudo apt install aspnetcore-runtime-6.0" first, then run "sudo apt install dotnet6".

Yes,I uninstall all the things you mention before I did this. But if I install dotnet6 first I would confront the same problem no matter I do the clean up or not. So just install runtime first work for me for this particular issue.

Ah,yeah. Removing the microsoft-prod deb source and updating helped.
sudo apt remove dotnet\*
sudo rm /etc/apt/sources.iist.d/microsoft-prod.list
sudo apt update
sudo apt install -y dotnet6

However, I may have a similar issue on Fedora next...

How to install libmsquic if packages.microsoft.com/keys/microsoft.asc is removed? https://learn.microsoft.com/en-us/windows-server/administration/linux-package-repository-for-microsoft-software

@khteh  -- These related instructions (linked from the top) for PowerShell might help: https://github.com/dotnet/core/issues/7713.

I have dotnet in an older previous Ubuntu, and then I updated to Ubuntu Jammy 22.04. After this, dotnet --list-sdks no longer return anything. So I have to fix it by:
sudo apt remove dotnet*
sudo apt remove aspnetcore*
sudo rm /etc/apt/sources.list.d/microsoft-prod.list*
sudo apt update
sudo apt install dotnet6

And it is fixed now.

Ah,yeah. Removing the microsoft-prod deb source and updating helped.
sudo apt remove dotnet\*
sudo rm /etc/apt/sources.iist.d/microsoft-prod.list
sudo apt update
sudo apt install -y dotnet6

However, I may have a similar issue on Fedora next...

Tried the steps but to no avail. Ubuntu 22.04
$ dn --info

global.json file:
  Not found

Host:
  Version:      6.0.8
  Architecture: x64
  Commit:       55fb7ef977

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.8 [/usr/lib/dotnet/dotnet6-6.0.108/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

I resolve the same problem by installing runtimes first then SDK. I run "sudo apt install aspnetcore-runtime-6.0" first, then run "sudo apt install dotnet6".

hey that does not worked for me on the first try because i copied the commands and "sources.iist.d" were typical wrong word .try "source.list.d" . it should wotk .

I tried it on ubunutu 22.04 and that worked
sudo apt remove 'dotnet*'
sudo apt remove 'aspnetcore*'
sudo rm /etc/apt/sources.list.d/microsoft-prod.list
sudo rm /etc/apt/sources.list.d/microsoft-prod.list.save
sudo apt update
sudo apt install dotnet6

dev and staging are now using the packages from PMC
tpak@stg-net6-nginx:~$ dotnet --list-sdks && dotnet --list-runtimes
6.0.402 [/usr/share/dotnet/sdk]
Microsoft.AspNetCore.App 6.0.10 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.10 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Quite painful, thanks for the guidance on getting up and running.
One extra step I had to do in order to run dotnet as a normal user (I'm not sure whether this is good practice from a security perspective):
cd /usr/lib
sudo chmod +x dotnet

When will support for Arm64 .NET 6 come to the Ubuntu package? It's not available when I try to install it. This website says it's only for amd64 (aka x86_64), but Microsoft's download page also provides binaries for Arm32 and Arm64 Linux. Please add the Arm64 architecture version to the Ubuntu package.

dotnet6 for arm64 has been released \o/

Which feed is more up-to-date: PMC or Ubuntu?

@richlander
The instructions should be updated to use single quotes when using the * in shell commands. For example:
sudo apt remove 'dotnet*'

Otherwise, if the current directory has any files or folders match the glob, the shell will expand them. For example, if the user had a file named dotnet_wish_list.txt in their current directory, the command sudo apt remove dotnet* would expand to sudo apt remove dotnet_wish_list.txt, which will not have the intended effect.

My dotnet application runs when started as user but fails as root with sudo command claiming that .NET is not installed.
Tried removing/reinstalling but nothing works
`fish@host:~/SimpleApp$ sudo ./SimpleApp
You must install .NET to run this application.
App: /home/fish/SimpleApp/SimpleApp
Architecture: x64
App host version: 6.0.10
.NET location: Not found
If I run the same without **sudo** everything works.fish@host:~$ dotnet --info
.NET SDK (reflecting any global.json):
Version:   6.0.111
Commit:    b3bb659a9d
Runtime Environment:
OS Name:     ubuntu
OS Version:  22.04
OS Platform: Linux
RID:         ubuntu.22.04-x64
Base Path:   /usr/lib/dotnet/sdk/6.0.111/
global.json file:
Not found
Host:
Version:      6.0.11
Architecture: x64
Commit:       943474ca16
.NET SDKs installed:
6.0.111 [/usr/lib/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.11 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.11 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info
`

Hi @d-kar!
Do you mean that if you do fish@host:~/SimpleApp$  ./SimpleApp it is OK?
For the .111 in Ubuntu we're facing some issues with the DOTNET_ROOT variable and the install_location files, affecting AppHost (https://github.com/dotnet/runtime/issues/79237 ... you can find here some workarounds in the meantime). We already have a fix that will be released next week on .112.
Sorry for the inconvenience.

Do you mean that if you do fish@host:~/SimpleApp$ ./SimpleApp it is OK?

Yes, running without sudo is OK.
When I check environment var DOTNET_ROOT it is set, but when I change to root user it dissapears. After that when I change back to my user account environment variable is dissapeared all together.
I'm not too familiar with Linux so not sure what's going on here.
fish@host:~/SimpleApp$ echo $DOTNET_ROOT
/usr/lib/dotnet
fish@host:~/SimpleApp$ sudo echo $DOTNET_ROOT
/usr/lib/dotnet
fish@host:~/SimpleApp$ sudo su
root@host/home/fish/SimpleApp# echo $DOTNET_ROOT

root@host/home/fish/SimpleApp# su fish
fish@host:~/SimpleApp$ echo $DOTNET_ROOT

I use my app as a systemd service, so setting environment variable in .service file manually as a workaround works for me.

fish@host:~/SimpleApp$ echo $DOTNET_ROOT
/usr/lib/dotnet
fish@host:~/SimpleApp$ sudo echo $DOTNET_ROOT
/usr/lib/dotnet
fish@host:~/SimpleApp$ sudo su
root@host/home/fish/SimpleApp# echo $DOTNET_ROOT

root@host/home/fish/SimpleApp# su fish
fish@host:~/SimpleApp$ echo $DOTNET_ROOT

I use my app as a systemd service, so setting environment variable in .service file manually as a workaround works for me.

It's weird that your $DOTNET_ROOT points to /usr/lib/donet
It looks empty for
(⎈|kubeapp:calico-system)   osanhaji@5CD2068Y53:~ $ ls /usr/lib/dotnet/
packs
(⎈|kubeapp:calico-system)   osanhaji@5CD2068Y53:~ $ ls /usr/lib/dotnet/packs/
NETStandard.Library.Ref

I have set it to:
(⎈|kubeapp:calico-system)   osanhaji@5CD2068Y53:~ $ echo $DOTNET_ROOT
/usr/share/dotnet/
(⎈|kubeapp:calico-system)   osanhaji@5CD2068Y53:~ $ ls $DOTNET_ROOT
dotnet  host  LICENSE.txt  packs  sdk  sdk-manifests  shared  templates  ThirdPartyNotices.txt

It looks like it works also when $DOTNET_ROOT is unset

Although I managed to install with PMC packages I am having trouble running tools.
dotnet ef returns
You must install .NET to run this application.
App: /home/xxxx/.dotnet/tools/dotnet-ef
Architecture: x64
App host version: 6.0.13
.NET location: Not found
Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.13
dotnet info
`.NET SDK (reflecting any global.json):
Version:   6.0.405
Commit:    27ab36058b
Runtime Environment:
OS Name:     ubuntu
OS Version:  22.04
OS Platform: Linux
RID:         ubuntu.22.04-x64
Base Path:   /usr/share/dotnet/sdk/6.0.405/
Host:
Version:      7.0.2
Architecture: x64
Commit:       d037e070eb
.NET SDKs installed:
6.0.405 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.13 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.13 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.2 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
DOTNET_ROOT       [/usr/lib/dotnet]
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
`

I hit a bug in the Jammy versions of the SDKs that were fixed in newer version, so switched over to PMC following the above guide, updated and all was fine (also nice to get .net 7 option).
I'm wondering if it's the case that as a developer, all roads lead to needing the PMC versions of SDKs? In which case does it make more sense to only publish the runtimes on Ubuntu feeds? So end-users can get the runtime OOTB without much fuss, and developers can read the manual on how to install the SDK if they want it?

Although I managed to install with PMC packages I am having trouble running tools.
dotnet ef returns You must install .NET to run this application.
App: /home/xxxx/.dotnet/tools/dotnet-ef Architecture: x64 App host version: 6.0.13 .NET location: Not found
Learn about runtime installation: https://aka.ms/dotnet/app-launch-failed
Download the .NET runtime: https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=ubuntu.22.04-x64&apphost_version=6.0.13
dotnet info `.NET SDK (reflecting any global.json): Version: 6.0.405 Commit: 27ab36058b
Runtime Environment: OS Name: ubuntu OS Version: 22.04 OS Platform: Linux RID: ubuntu.22.04-x64 Base Path: /usr/share/dotnet/sdk/6.0.405/
Host: Version: 7.0.2 Architecture: x64 Commit: d037e070eb
.NET SDKs installed: 6.0.405 [/usr/share/dotnet/sdk]
.NET runtimes installed: Microsoft.AspNetCore.App 6.0.13 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.13 [/usr/share/dotnet/shared/Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.2 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found: None
Environment variables: DOTNET_ROOT [/usr/lib/dotnet]
global.json file: Not found
Learn more: https://aka.ms/dotnet/info
Download .NET: https://aka.ms/dotnet/download `

I had the same issue, I think maybe there's different behaviours and file locations between the Ubuntu debs and the PMC debs (i.e. PWC isn't correctly setting the path, or the location is wrong - one or the other)
Your runtime location (like mine) is "/usr/share/dotnet"
But when I checked on my machine DOTNET_ROOT (environment variable) was set as "/usr/lib/dotnet" and so it was in the content of "/etc/profile.d/dotnet.sh" and "/etc/dotnet/install_location"
I updated it to "/usr/share/dotnet" in all 3 locations and it's fixed - you might need to log out and back in again to see the change.

Thank, add env DOTNET_ROOT work for me

.NET SDK 7.0 on Ubuntu 22.10, setting DOTNET_ROOT to /usr/share/dotnet did not solve the issue for me, ended up copying everything from /usr/share/dotnet to /usr/lib/dotnet and now it's working fine.

I tried it on ubunutu 22.04 and that worked sudo apt remove 'dotnet*' sudo apt remove 'aspnetcore*' sudo apt remove 'netstandard*' sudo rm /etc/apt/sources.list.d/microsoft-prod.list sudo rm /etc/apt/sources.list.d/microsoft-prod.list.save sudo apt update sudo apt install dotnet6

that did it for me. Thanks!!

@richlander better use /etc/apt/preferences.d/dotnet instead of /etc/apt/preferences ;-)

@richlander better use /etc/apt/preferences.d/dotnet instead of /etc/apt/preferences ;)
sudo sh -c "cat > /etc/apt/preferences.d/dotnet <<'EOF'
Package: dotnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"
sudo sh -c "cat > /etc/apt/preferences.d/aspnet <<'EOF'
Package: aspnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"

I'm trying to install dotnet 6 and 7 (sudo apt install dotnet-sdk-6.0 dotnet-sdk-7.0). That works for me.

Been struggling for hours with this. Soooo frustrating - Should be simple.
Latest error : A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist

I'm trying to install dotnet 6 and 7 (sudo apt install dotnet-sdk-6.0 dotnet-sdk-7.0). That works for me.

Sure but then apt will prefer installing from the ubuntu repositories and not from microsoft.

Been struggling for hours with this. Soooo frustrating - Should be simple. I am new to Linux.
Latest error : A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist ( dotnet --info)
When I run dotnet --list-runtimes, I only see 7.0.3. It seems the 6 & 7 sdks are there but only the 7 runtime. I have tried to install the ver 6 runtime many many times.
So, more errors when I try and run a .net 6 project:
Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64) .NET location: /usr/share/dotnet/ The following frameworks were found: 7.0.3 at [/usr/share/dotnet/shared/Microsoft.NETCore.App] Learn about framework resolution: https://aka.ms/dotnet/app-launch-failed To install missing framework, download: https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=ubuntu.22.04-x64 . Please check the diagnostic logs for more information.
I have tried to install .net 6 using all scenarios - nothing works. So... back to a full uninstall of everything .net.
What a mess

There seems to be an issue in the ubuntu repos.
This command will create a setting that let apt prefer the microsoft packages over the ones from ubuntu.
sudo sh -c "cat > /etc/apt/preferences.d/dotnet <<'EOF'
Package: dotnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"
sudo sh -c "cat > /etc/apt/preferences.d/aspnet <<'EOF'
Package: aspnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"

OK - so what happens next? I have run the command - I am guessing a full uninstall and re-install again?

sudo apt-get remove --purge dotnet-*
And then reinstall.
Not a dotnet dev myself but supporting collegues that do.
With Rider or vscode as IDE.

Thanks for the help = do you know if .Net 7.0 is usable on Linux or should I stick to .net 6.0 ?

Didn't heard something not working but we are yet starting to migrate applications to .net 7.0

OK - thanks, your fix worked for me - test suite is running correctly now,

sudo sh -c "cat > /etc/apt/preferences.d/dotnet <<'EOF'
Package: dotnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"
sudo sh -c "cat > /etc/apt/preferences.d/aspnet <<'EOF'
Package: aspnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"

I needed to add another clause for netstandard* because netstandard-targeting-pack-2.1 was being installed as a dependency of dotnet-sdk-6.0 and was otherwise coming from the Ubuntu repos.

I have the same problem:
matt@MattPc:~/Matt/linux$ apt list -a dotnet-sdk-6.0
Listing... Done
dotnet-sdk-6.0/jammy,now 6.0.408-1 amd64 [installed]
dotnet-sdk-6.0/jammy 6.0.407-1 amd64
...

But:
matt@MattPc:~/Matt/linux$ dotnet --info

global.json file:
  /mnt/c/Programming/Git/Matt/linux/global.json

Host:
  Version:      6.0.16
  Architecture: x64
  Commit:       1e620a42e7

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.NETCore.App 6.0.16 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]

I was able to make it work with SDK 6.0.16 but I need the SDK 6.0.408 for a project.
I also try the script provide by Microsolf to install dotnet:
matt@MattPc:~/Matt/linux$ ./dotnet-install.sh
dotnet-install: .NET Core SDK with version '6.0.408' is already installed.

But still desn't detect when I run  dotnet --info.

What I did to Installing .NET 7 on Ubuntu 22.04 (Jammy)
Purge old packages
sudo apt-get remove 'dotnet.'
sudo apt-get remove 'aspnet.'
Get Ubuntu version
declare repo_version=$(if command -v lsb_release &> /dev/null; then lsb_release -r -s; else grep -oP '(?<=^VERSION_ID=).+' /etc/os-release | tr -d '"'; fi)
Download Microsoft signing key and repository
wget https://packages.microsoft.com/config/ubuntu/$repo_version/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
Install Microsoft signing key and repository
sudo dpkg -i packages-microsoft-prod.deb
Clean up
rm packages-microsoft-prod.deb
Update packages
sudo apt update
see https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#register-the-microsoft-package-repository
Then followed @kitingChris suggestion

sudo sh -c "cat > /etc/apt/preferences.d/dotnet <<'EOF'
Package: dotnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"
sudo sh -c "cat > /etc/apt/preferences.d/aspnet <<'EOF'
Package: aspnet*
Pin: origin packages.microsoft.com
Pin-Priority: 1001
EOF"

That worked for me - everything else did not.

Now on Ubuntu 23.04 - Of course, everything is still broken. .Net 7 and .Net 8 RC 1 SDKS dont work. Same issues.

I updated the scenarios to make them clearer. We now have two "Clean machine" scenarios and two "Mixed-state" scenarios. I've kept the numbering the same.
BTW: We are very sorry that this situation occurred. We should have predicted that it would but sadly did not. That's on us. We've learned that mix-and-matching package feeds with the same package names that install to different locations is a recipe for what we're seeing here. Again, we're sorry about that and won't repeat it.

This is still broken on 23.04

I followed all the steps, still couldn't get anything back from dotnet --list-sdks. Then I read somewhere that I also had to uninstall dotnet-host and I reran the steps from here an now I'm getting this error:
A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist

Googling this leads me to many other suggested solutions yet, of which none has worked yet.
Man, I've been trying to upgrade from .NET 6 to .NET 7 on Ubuntu 22.04 for the last 3 hours now and not only does it not work, .NET is now completely broken and I'm unable to get it back into a working state again. What an abysmal experience.

Ok if someone else comes here and thinks that .NET just doesn't seem to install on Ubuntu 22.04 then there's hope. This is the only solution that worked for me:
First run this:
curl -sSL https://dot.net/v1/dotnet-install.sh | bash /dev/stdin -c 7.0.2xx

Then add this to your .bashrc:
export DOTNET_ROOT=$HOME/.dotnet
export PATH=$PATH:$HOME/.dotnet:$HOME/.dotnet/tools

@dustinmoris are you registering Microsoft package feed or rely on native Ubuntu package feeds? It seems that you do want to install 7.0.2xx feature band - solution for this scenario is provided in Mixed-state scenario 2 section of the first comment in this GitHub issue.
.NET 6 and 7 are provided in native Ubuntu feeds. The following page describes steps to install either .NET version on Ubuntu 22.04: https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-2204 On that page, it is called out that only one package feed should be registered at the time to avoid issues you have hit.

Ubuntu 22.04, .NET 6.0 - was originally set up using PMC, with the APT preferences file as described in this issue:
# cat /etc/apt/preferences.d/microsoft
Package: *
Pin: origin "packages.microsoft.com"
Pin-Priority: 1001

All seemed to work, but after last  last night's unattended upgrade of the .NET packages we get the dreaded
A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist
So it seems that it somehow ended in the "mixed scenario", even though we had the APT preferences file - and it seems to have been effective on other machines during previous upgrades!
/var/log/apt/term.log contains:
Log started: 2023-10-26  06:25:59
...
(Reading database ... 120909 files and directories currently installed.)
Preparing to unpack .../dotnet-hostfxr-6.0_6.0.124-0ubuntu1~22.04.1_amd64.deb ...
Unpacking dotnet-hostfxr-6.0 (6.0.124-0ubuntu1~22.04.1) over (6.0.23-1) ...
Setting up dotnet-hostfxr-6.0 (6.0.124-0ubuntu1~22.04.1) ...
Log ended: 2023-10-26  06:26:00

@loop-evgeny My latest expression is that .net 7.0 on 23.04 is broken. The microsoft documentation is inaccurate and incomplete. Are you aware of any documents that explain the solution clearly and accurately? Its almost certain that this issue will not be fixed by .net 8.0 launch and most teams resources will be used in fixing the bugs that come with that launch.

All seemed to work, but after last last night's unattended upgrade of the .NET packages we get the dreaded
...
So it seems that it somehow ended in the "mixed scenario", even though we had the APT preferences file - and it seems to have been effective on other machines during previous upgrades!

For those that wish to have unattended upgrades of dotnet, how about following https://askubuntu.com/a/1435868 and adding
Unattended-Upgrade::Allowed-Origins {
  ...
  "microsoft-ubuntu-${distro_codename}-prod ${distro_codename}:${distro_codename}";
};

Ok if someone else comes here and thinks that .NET just doesn't seem to install on Ubuntu 22.04 then there's hope. This is the only solution that worked for me:

@dustinmoris I hope no one tries to follow/read your comment, because it is very misplaced. This github issue is about Ubuntu packages of .NET x.y.z (which means, packages provided by the Ubuntu distribution, so that you can install directly with the native package manager tool apt without external scripts or external sources).

This issue still hasn't been fixed. And .net 9 is in preview and Ubuntu 23.10 has been out for a while.

I have opened tickets for 6, 7 and 8. The issue is being ignored.

What issue? what tickets? sigh

FYI on our plan for Ubuntu 24.04 packages
https://github.com/dotnet/core/discussions/9258

After a recent machine rebuild, upgrading to Linux Mint 22.0 (equivalent to Ubuntu 24.04) I have the dotnet sdk 8.0 running happily.  I now need to service an older  application running on DotNet 6.  I've been through your instructions and am left with:-
sudo apt install dotnet-sdk-6.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
dotnet-runtime-deps-6.0 : Depends: libicu but it is not installable or
libicu72 but it is not installable or
libicu71 but it is not installable or
libicu70 but it is not installable or
libicu69 but it is not installable or
libicu68 but it is not installable or
libicu67 but it is not installable or
libicu66 but it is not installable or
libicu65 but it is not installable or
libicu63 but it is not installable or
libicu60 but it is not installable or
libicu57 but it is not installable or
libicu55 but it is not installable or
libicu52 but it is not installable
E: Unable to correct problems, you have held broken packages.
What do you suggest?

Looks like we Linux users are being done over by Microsoft again.  Failing to provide consistent updates. Now the dotnet 9 sdk is only going to be available in Ubuntu format on Ubuntu distros. And that's after MS having insisted we not mix versions from different repos!  I'm incandescent at their duplicity.  After choosing MS's repos to get the latest and greatest I now have to remove dotnet completely and "make do" with what Ubuntu choose to provide. Which isn't the full set that had been available in the MS repos.  Also I don't know what the differences may be between the official MS releases and the distro's release.  I develop web sites professionally and need a mix of SDK's to support legacy and new projects. If anyone could help calm me down I'd appreciate it.

Looks like we Linux users are being done over by Microsoft again. Failing to provide consistent updates. Now the dotnet 9 sdk is only going to be available in Ubuntu format on Ubuntu distros. And that's after MS having insisted we not mix versions from different repos! I'm incandescent at their duplicity. After choosing MS's repos to get the latest and greatest I now have to remove dotnet completely and "make do" with what Ubuntu choose to provide. Which isn't the full set that had been available in the MS repos. Also I don't know what the differences may be between the official MS releases and the distro's release. I develop web sites professionally and need a mix of SDK's to support legacy and new projects. If anyone could help calm me down I'd appreciate it.

I'm using .net 8 and .net 9 on Ubuntu 24.10

I'm using .net 8 and .net 9 on Ubuntu 24.10

Thanks. I presume you're using them from the Ubuntu repos?  How about .net 6 which I understand isn't available there?  Are you noticing any issues with them?

I'm using .net 8 and .net 9 on Ubuntu 24.10

Thanks. I presume you're using them from the Ubuntu repos? How about .net 6 which I understand isn't available there? Are you noticing any issues with them?

I had endless trouble with .net 6 and .net 7 because I tried the ms repo and the unbuntu repo.
Now I only use ubuntu repo.

Quite, I read the instructions and opted for the MS repo! Now I'll have to swap over. MS have little idea about customer service. Never have, which I why I've used Linux for the last 15 years. Canonical are as bad as MS which is why I switched from Ubunuto to Mint 12 years ago. Keeping with the MS repos was my idea of just having to deal with one incompetent company rather than two.
Thanks for your insight.

See the instructions in this post. They work with Ubuntu 22.04 and 24.04. You can install several .NET versions that way.
https://devblogs.microsoft.com/dotnet/whats-new-for-dotnet-in-ubuntu-2404/


Move SDFGI update logic into clustered renderer

Part of the SDFGI logic was still in our RenderSceneRenderRD base class, this resulted in error spam if SDFGI is turned off but we're falling back on the mobile renderer.
Moved the related code into the clustered renderer and added stubs into the mobile renderer.

Thanks!


[Wiki]: Typo in FAQ page

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a theme

Describe the Bug
Original text:

No, Millennium by itself does not alter Steam® in a manor that grants persons an unfair advantage, as well as it does not alter the intended operations of the service.

Expected Behavior
manor should be manner
Steps To Reproduce
https://github.com/SteamClientHomebrew/Millennium/wiki/Frequently-Asked-Questions#is-millennium-against-the-steam-terms-of-service-tos
Operating System
Windows
Anything else?
Perhaps this entire sentence could be rephrased in the following way:

No, Millennium by itself neither alters Steam® in a manner that grants persons an unfair advantage, nor alters the intended operations of the service.

Thanks, updated it!


KB Editorial Clean Up - Bucket 1

typos, punctuation, formatting, in-house images, etc.

mahara-stack-logo.pngg is misspelled


Publish 0.3.0

Thank you for merging #18.
I have placed this issue as a friendly reminder to have the changes published to npm.
CC: @sonimadhuri  @gauravgupta123 @vinayak25

Hello @gimyboya, we have a sprint ending this week. We will be releasing new version with your PR this weekend.

@vinayak25 Grate! would love to see the new version out today!
PS: i have also added a new PR #20 it would be nice to see it merged as well
CC: @sonimadhuri @gauravgupta123

Hello @vinayak25 , currently facing issue solved in PR #18 . Do you have a timeline for v0.3.0?


Having trouble with nREPL

I'm trying to get a browser connected REPL setup with nREPL, Piggieback and Weasel.  I start up a lein repl and evaluate the following:
(require 'weasel.repl.websocket)
(cemerick.piggieback/cljs-repl
        :repl-env (weasel.repl.websocket/repl-env
                   :ip "<IP_ADDRESS>" :port 9001))

I then load my ClojureScript application in the browser and it successfully opens the websocket connection by calling:
(ws-repl/connect "ws://localhost:9001")

This all works great.  I can evaluate code directly in the REPL and have it run in the browser.  For example, entering the following in the REPL successfully displays an alert dialog in the browser:
(js/alert)

The problem I'm encountering is when I try to evaluate the same thing over an nREPL connection (i.e. from an editor).  In that case I get the error:
CompilerException java.lang.RuntimeException: No such namespace: js
To demonstrate the issue I can open a separate lein repl and create an nREPL connection:
(use '[clojure.tools.nrepl.repl])
(def conn (repl/connect :port 58569))
(def client (repl/client conn 10000))
(repl/message client {:op "eval" :code "(js/alert)"})

I get the following response:
({:ex "class clojure.lang.Compiler$CompilerException", :id "83ce9217-016a-4cd2-b652-9dfce01a3dcf", :root-ex "class clojure.lang.Compiler$CompilerException", :session "07f7d6cf-7ee6-4a59-b99e-4e1fcd134e33", :status ["eval-error"]} {:err "CompilerException java.lang.RuntimeException: No such namespace: js, compiling:(/private/var/folders/z3/x8fdxj9x1rv8zt4ylnkjcgyh0000gn/T/form-init2789710204217740010.clj:1:1) \n", :id "83ce9217-016a-4cd2-b652-9dfce01a3dcf", :session "07f7d6cf-7ee6-4a59-b99e-4e1fcd134e33"} {:id "83ce9217-016a-4cd2-b652-9dfce01a3dcf", :session "07f7d6cf-7ee6-4a59-b99e-4e1fcd134e33", :status ["done"]})

Is this related to Weasel?  Is there any additional configuration I need to do?  I'm not very familiar with CIDER/Emacs but, strangely, this error does not occur with that setup.  It does happen when I use the nREPL integration in Sublime Text 2 or Atom or when making nREPL calls directly as illustrated above.
Any help you can provide with this would be greatly appreciated.  Let me know if there's any additional information I can provide to make this more clear.

The Clojure nREPL client error looks like it's still running a Clojure REPL, probably because you did not appear to piggieback that session.
I don't think there's anything actionable here; if you disagree feel free to comment here and I'll reconsider. Thanks for the report!


bug with minmaxslider: on last update when i input min it resets to 0, only can slide min value,

shareX -> mp4 broke so i can't share video but here are the steps:

Can you provide:

Your unity version
a simple code that may re-produce it

As my testing:

Unity 2022.3.0f1 with UI Toolkit disabled.
SaintsField 3.4.9
Code as

[MinMaxSlider(5, 10, free: true), BelowRichLabel("$" + nameof(rangeInt))] public Vector2Int rangeInt;
[MinMaxSlider(0, 10), BelowRichLabel("$" + nameof(rangeInt2))] public Vector2Int rangeInt2;

gives
https://github.com/user-attachments/assets/4d69632e-aba1-4abc-8896-2bf68417d813

in unity 2020.3.48

Hi,
please check if it's been fixed in 3.4.10

yay victory!


mod_proxy metrics report stale / old data for backend status

Thanks @rainerjung for implementing mod_proxy metrics (https://github.com/Lusitaniae/apache_exporter/pull/102) - greatly appreciated.

I just updated to the new apache_exporter release (https://github.com/Lusitaniae/apache_exporter/releases/tag/v0.10.0). It works great, but unfortunately I ran into a bug with stale data on the reported state of balancer members ....
Initially the status for all backends is reported correctly, i.e.
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-01.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-02.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-03.example.com:7481"} 1

When the status changes though, the old status continues to be exported as well:
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Dis",worker="http://host-01.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Dis",worker="http://host-02.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Dis",worker="http://host-03.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-01.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-02.example.com:7481"} 1
apache_proxy_balancer_status{balancer="balancer://obst-balancer",status="Init Ok",worker="http://host-03.example.com:7481"} 1

I believe this is due to the currently reported status from the scoreboard is simply being added to exported data, but none of the old, non-current status data is ever removed in https://github.com/Lusitaniae/apache_exporter/pull/102/files#diff-fb1d52e526ddf3b580f7d8c5378ed5b4154d782c9de8da9e517b43ddf3d970fcR512

If I may raise another idea in this regard. Currently only the actual status string reported in the scoreboard is reported with value "1", but none of the others with value "0". The various status values are documented (https://httpd.apache.org/docs/trunk/howto/reverse_proxy.html#status) and looking at i.e. the node_exporter (https://www.robustperception.io/linux-software-raid-metrics-from-the-node-exporter) which reports state in this manner for i.e. node_systemd_unit_state or node_md_stat
node_md_state{device="md0",state="active"} 1
node_md_state{device="md0",state="inactive"} 0
node_md_state{device="md0",state="recovering"} 0
node_md_state{device="md0",state="resync"} 0

I know this creates more time series, but it does not waste storage with values rarely changing and it would simply aligns things style-wise.

Thank you for giving the details. I will look into it, but a friendly ping will help me not forgetting about it.

@rainerjung  ... may I kindly remind you again ;-)

@rainerjung  @Lusitaniae  ... I pushed a small PR just adding a reset to the ProxyBalancer metrics on each scrape.
Do you guys mind having a look if this works and fixes the issue of stale metrics?


Plain Vanilla JS files are excluded from SWC processing/transforms

I originally opened the issue here: https://github.com/lingui/swc-plugin/issues/77#issuecomment-1840504440
However it was brought to my attention it's actually this plugin that specifically only runs SWC macros on certain file extensions and excludes plain JS files with extensions .js, .mjs, .cjs, etc.
My argument for including it for plain JS files is that SWC macros cannot be used with plain JS files, when they should be allowed. The normal vite-plugin-react with Babel will transform babel macros for vanilla JS files, but switching to this vite plugin they will not be transformed. The reason I'm using vanilla (.mjs) JS files is because I am using Rescript, and the compiler outputs plain JS files with no types.
Here is the relevant line: https://github.com/vitejs/vite-plugin-react-swc/blob/main/src/index.ts#L206-L217
Here is a sample repo showing the Lingui SWC macro not working: chrischen/js-lingui@88e8e19. The Lingui JS SWC macro specifically has a "js" macro for usage outside of React and in Vanilla JS/TS files. The default behavior of this plugin makes that usage impossible unless it's used in a .ts file.
I believe the solution should be to run even plain JS files through SWC.

@yyx990803 what do you think?
@chrischen this is done to avoid running SWC on non user code and keep performance good for already compiled code. In the app land, JS is more a compiler target language than something you should write your source code in.

I am indeed using plain JS as a compiler target language (of Rescript). I am using an escape hatch to use the JS macro, so the macro code is left as-is in the compiled JS.
Maybe an option to override the parser config or perhaps to include JS files?
My understanding is non-user code is either in memory (in dev mode) or in a separate build output folder for production anyways?

@chrischen Thanks for your answer, I've implemented something that should be a good trade off in term of flexibility/maintainability, but given some other team member are off in the coming weeks this will probably not be added before January