ASP.NET Core 2 IWebHostBuilder.BuildWebHost throws FileNotFound Exception Due to Dependency Version

In Main.cs, we have the the following method since this is generated from ASP.NET Core 2.0 codegen.
public static IWebHost BuildWebHost(string[] args) =>
        WebHost.CreateDefaultBuilder(args)
            .UseStartup<Startup>()
            .Build();

But it throws exception,
發生 System.IO.FileLoadException
  HResult=0x80131040
  Message=Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  Source=Microsoft.AspNetCore.Hosting
  StackTrace:
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at Project.Program.BuildWebHost(String[] args) in C:\path\Program.cs:line 27
   at Project.Program.Main(String[] args) in C:\path\Program.cs:line 23

This worst thing is that this WebHosting is calling System.Diagnostics.DiagnosticSource of version <IP_ADDRESS>, while in NuGet I saw the version should be 4.4.1, link https://preview.nuget.org/packages/Microsoft.AspNetCore.Hosting/.
The version this project is using is Microsoft.AspNetCore.All 2.0.0 (just released a few days ago!)
Also there is a unresolved SO question out there, [ref] link https://stackoverflow.com/questions/45464126/signalr-core-w-asp-net-core-2-0-in-vs-2017-15-3-could-not-load-file-or-assembly.

Also found some clues at SignalR repo, aspnet/SignalR#690, and it requires an preview version of ASP.NET Core 2.1, which I don't want to use preview for that. Any suggestions?

Wait a little bit.

Actually I don't use SignalR, but just the original Microsoft.AspNetCore.All.dll 2.0.0.

What exactly is conflicting then? What other things are you referencing? Are you targeting .NET Core 2.0?

System.Management.Automation 6.0.0-beta.5 (from myget)
Microsoft.AspNetCore.All 2.0.0 (from nuget)
What I want this project to do is targeting ASP.NET Core 2 with Windows Auth, and enable to use PowerShell inside.

Show your entire project file and all project files it references. Also, if you could grab obj/project.assets.json and put that in a gist, it would be good. That way we can see what you're actually referencing

project.assets.json: https://gist.github.com/WilliamWsyHK/2241c6e374cbe3d5234a5cc6bb5c7bb3

Looking at your assets file, it's likely a mismatch between the Microsoft.NETCore.App and ASP.NET Core 2.0.0.
"Microsoft.NETCore.App": {
            "target": "Package",
            "version": "2.0.0-preview2-25407-01",
            "autoReferenced": true
          },
          "Microsoft.AspNetCore.All": {
            "target": "Package",
            "version": "2.0.0"
          }

You need to wait until the 2.0.0 SDK is released, or go download a newer preview version from https://github.com/dotnet/core-setup#daily-builds.

Tried, thanks.
But that is weird that ASP.NET Core released earlier than .NET Core.


Updated Ages Cholera through Hib

Closing this for the time being. I see now how I should do this so I don't issue several pull requests.

Ok, I'm hoping this works, but you should now see a full set of changes Cholera through Hib and then HPV through Zoster.

Final version. Should be 3 commits. 2 noted above and one for updated concept-types


ClassNotFoundException: EsHadoopNoNodesLeftException

I've created a spark job that reads from elasticsearch and then writes back to it. Locally it runs fine, but when I submit it to a cluster I'm not able to get it working. I've tried different things, as described below.
Spark-cluster is running spark-1.5.1-bin-without-hadoop on 3 nodes as a test setup.
I included the following packages in my uberjar:

org.elasticsearch/elasticsearch-spark_2.10: 2.2.0-m1 (also tried with 2.1.1)
org.elasticsearch/elasticsearch-hadoop-mr: 2.2.0-m1

The job then fails with
java.lang.ClassNotFoundException: org.elasticsearch.hadoop.rest.EsHadoopNoNodesLeftException
The ClassNotFoundException surprised me, it also prevents me from seeing the
actual reason for the exception, so I tried to solve the ClassNotFoundException.
I downloaded the packages on all nodes, added them to the spark classpath, rebooted
spark and re-submitted the job.
It then tells me
15/10/30 10:57:42 WARN scheduler.TaskSetManager:
Lost task 0.0 in stage 5.0 (TID 11, <IP_ADDRESS>):
java.lang.Error: Multiple ES-Hadoop versions detected in the classpath; please use only one
....

Makes sense, there are multiple ES-Hadoop packages.. So I build an uberjar without
the packages described in step 1.
Exception in thread "main" java.lang.ExceptionInInitializerError
....
Caused by: java.lang.ClassNotFoundException: org.elasticsearch.spark.rdd.api.java.JavaEsSpark

This also happens when I don't put the packages on the spark-classpath but provide
them when submitting the job:

submitted with --packages org.elasticsearch:elasticsearch-hadoop-mr:2.2.0-m1,org.elasticsearch:elasticsearch-spark_2.10:2.2.0-m1
submitted with --jars /home/hadoop/extra/elasticsearch-spark_2.10-2.2.0-m1.jar,/home/hadoop/extra/elasticsearch-hadoop-mr-2.2.0-m1.jar

So now I'm a bit confused of what's the right way to go about this. Do you have
any tips on how to run the job?

Why do you submit both -hadoop-mr and elasticsearch-spark jars? You only need the spark jar - that's it; it contains both mr and the spark native API.
P.S. The ClassNotFoundException appears because Spark will shutdown its job classloader immediately in case of an exception so any other classes that need to be loaded, will fail causing the initial error to be hidden.

And by the way, 2.2.0-beta1 was released yesterday; try that instead.

Hey Costin,
Thanks for the answers, the ClassNotFoundException was the confusing part, at which I decided to add the hadoop-mr in the hope the class would become available.
I found the actual error in one of the workers and it works good now, also with 2.2.0-beta1. Thanks for your help!

freakinruben@ looks like im having the same issue, however, im still troubleshooting it. Can you share what was the actual error in the worker?

@fabiantan

java.lang.Error: Multiple ES-Hadoop versions detected in the classpath; please use only one

@fabiantan The original error (where all of this started) had to do with writing to ES with a RDD that didn't have the configuration of where to find ES


pod manifests should allow setting environment variables

https://github.com/appc/spec/blob/master/spec/pods.md doesn't mention setting environment variables for apps.  That said, rkt seems to support it.

Pod Manifests also provide the ability to override application execution parameters for their constituent ACIs (i.e. the app section of the respective Image Manifests).

and

app (object, optional) substitute for the app object of the referred image's ImageManifest. See Image Manifest Schema for what the app object contains.

How can we make this clearer?

It's already clear.  I was being lazy/tired.  I did find in my browser on pods.md and looked for environment and gave up.

to be clear, I'm not being passive-aggressive, this has been raised before as something nonobvious, so would love to know how to improve it..

You could copy and paste the entire app section from the image manifest under this section:

app (object, optional) substitute for the app object of the referred image's ImageManifest. See Image Manifest Schema for what the app object contains.

But then you have the problem of maintaining the two lists.


Implement SwidenLow and SwidenHigh for the interpreter

Implemented SwidenLow and SwidenHigh for the Cranelift interpreter,
doubling the width and halving the number of lanes preserving the low
and high halves respectively.
Conversions are performed using signed extension.
Copyright (c) 2021, Arm Limited

Happy to address the iterator chain comment.
Regarding the idea to factor out commonality between un/signed cases, I think that would work, but may be easier to do (given that the unsigned and signed variants are in separate branches / PRs at the moment) either as a follow-up patch after both of these are merged, or after one of them merge and then implemented in the remaining PR.

Yep, a followup that factors things appropriately (maybe across any other signed/unsigned pairs as appropriate too) would be perfectly fine, thanks!


updated react, react-dom, lodash, etc

Update packages to eliminate vulnerabilities
Tested on Chrome v75 with some warnings but no errors

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow #3 option )
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

ci add to white list

ci add to whitelist

@thaorell - Is there any issues with upgrading from React 16.4 to 16.8.6?  Any breaking changes or things in upgrade guides?

ci test please


Update README.md for inclusion of RCTCameraRoll in project

Can you provide more information ?
What commit did that change ?
How do you link RCTCameraRoll ?

@iamulya could u please improve and update this PR?

No respond from author for quite a while. Will close this.


Anki tags only appear if the tags exist in tiddlywiki

I have a bunch of classes, and I have my anki set up to stick its tags at the top of the flashcard so I know the context it's talking about. With full class names it was taking up a lot of room, so I changed my tag mapping to return a shorthand. The issue is, TiddlyRemember only allows me to put tags that exist in my TiddlyWiki on my anki cards (as far as I can tell). I really wish this was not a limitation, because a bunch of useless tags floating around just makes a mess.

I  don't think this is a limitation, unless I'm misunderstanding you; the filter language should let you add arbitrarily complex logic to determine what tags to include on your cards. Can you maybe explain / provide screenshots of your current tag mappings and where you're trying to pull the data from?

Heres my current tag mapping:

[tags[]] :intersection[[Class]tagging[]addsuffix[Notes]] +[removesuffix[Notes]get[short]]

if I remove the get[short] it works fine, but If it is there, it won't work unless I make chem also a tag instead of just chemistry.

I can't reproduce the behavior you're seeing, but maybe I don't understand how your notes are laid out. Here's a video showing how I'm interpreting how you're expecting this to work:
https://user-images.githubusercontent.com/2313414/156455208-eafac701-9b2a-41a3-9f18-eb1ee01eecd1.mp4

I'm going to close this now. Thanks for trying to help. I don't know what has changed, but I did the same steps I did earlier, and now it works....
( You did reproduce it exactly though :) )


"Becicherecu Mic" is listed in the drop-down menu

Description:
The commune is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions:
The website (https://peviitor-ro.github.io/ui.orase/) is up and running. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Becicherecu Mic".

Expected results
The location is listed in the drop-down menu as "Comuna Becicherecu Mic, TIMIȘ ".


CMake build tasks don't respect debug.onTaskErrors

Brief Issue Summary
When launching a program from Visual Studio Code, with a task of "type": "cmake" set as the preLaunchTask for that launch configuration, the program will launch after the preLaunchTask results in an error, despite the user having set the user setting debug.onTaskErrors to something like abort.
Steps to reproduce:

Create a task.json similar to what's shown below
Create a launch.json similar to what's shown below
Ensure that "My Build Task" results in an error when run
Set the user setting debug.onTaskErrors to abort
Launch the "My Launch Task" configuration
Note how it runs "My Build Task" first
Note how "My Build Task" results in an error
Note how it still launches the application set in "My Launch Configuration"
Note how the CMake/Build output log says [proc] The command: [redacted] exited with code: 1 and signal: null

.vscode/tasks.json:
{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "cmake",
      "label": "My Build Task",
      "command": "build",
      "preset": "${command:cmake.activeBuildPresetName}",
      "targets": ["${command:cmake.buildTargetName}"],
      "group": { "kind": "build", "isDefault": true }
    }
  ]
}

.vscode/launch.json:
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "cppvsdbg",
      "request": "launch",
      "name": "My Launch Configuration",
      "program": "C:/Path/To/Executable.exe",
      "preLaunchTask": "My Build Task"
    }
  ]
}

CMake Tools Diagnostics
N/A

Debug Log
N/A

Additional Information
No response

We have a fix for this here: https://github.com/microsoft/vscode-cmake-tools/pull/2803/files, we haven't released this fix yet, it is still in pre-release. If you install the pre-release version this should work for you. If it didn't work, let us know and we will investigate more.


GraphCaptureScopeGuard

Problem description
If one wants to catch exception during graph capture thrown by op, they need to end graph capture if it was still active. Requires manual tracking.
What's changed
Introduced GraphCaptureScopedGuard, a wrapper class that begins capture on the creation, can be manually ended, or ends when goes out of scope.
Utilized in the op_constraints
Checklist

[ ] Post commit CI passes

maybe it is a good idea to call all end_function for all funcrtions which we didn't close.

I've rebased and added a test. I didn't make a fake op, I've caused existing op (softmax) to fail by providing wrong arguments.

maybe it is a good idea to call all end_function for all funcrtions which we didn't close, it might happen in your case. But lest take a look at test.

as you said, capture that had exception thrown - it's functions would not be ended. it doesn't impact subsequent graph captures.
this is the graph with exception

while these are before/after

this is ok for compiler scenario, but I don't have all context on the graph capture usage; @dmakoviichuk-tt  please let me know what is your preference - to insert function ends or keep it like this.


[Bug]: some cloudtrail checks are failing

It seems like some of the cloudtrail checks are failing
The check cloudtrail_logs_s3_bucket_access_logging_enabled is marked as an error when the s3 bucket has the logs enabled.

The checks cloudtrail_s3_dataevents_read_enabled and cloudtrail_s3_dataevents_write_enabled are failing and the cloudtrail config is ok
CloudTrail data events config:
[
  {
    "name": "S3 Read Events",
    "fieldSelectors": [
      {
        "field": "eventCategory",
        "equals": [
          "Data"
        ]
      },
      {
        "field": "resources.type",
        "equals": [
          "AWS::S3::Object"
        ]
      },
      {
        "field": "readOnly",
        "equals": [
          "true"
        ]
      }
    ]
  },
  {
    "name": "S3 Write Events",
    "fieldSelectors": [
      {
        "field": "eventCategory",
        "equals": [
          "Data"
        ]
      },
      {
        "field": "resources.type",
        "equals": [
          "AWS::S3::Object"
        ]
      },
      {
        "field": "readOnly",
        "equals": [
          "false"
        ]
      }
    ]
  }
]

Prowler version: 3.1.2

I don't have that policy in cloudtrail bucket. It only has the Server access logging enabled (this is how is created by aws terraform module)

Hi @ichasco-heytrade can you check this again with the latest version code please?

Yes, this is working now @n4ch04 . Thanks!


time: add a Date type

We have a datatype to store time, under time.Time, however, there are plenty of places where we need to store only Date, without having to store Time information, For example: Date of Birth, College opening date, release date, etc.
Many databases provide fields to store Date alone. For example, Postgres has date type https://www.postgresql.org/docs/9.1/static/datatype-datetime.html; Mysql has DATE type https://dev.mysql.com/doc/refman/5.7/en/datetime.html
Javascript has input types for <input type="date"> which shows a datepicker which can be used for Date input. Demo: https://www.w3schools.com/html/tryit.asp?filename=tryhtml_input_date
If a web application has a date input field, the javascript front end can show dates, the database can save dates, but just for the sake of the Golang backend server, we are forced to write a custom Golang type that receives a string from the JS frontend, converts the string into a time.Time struct and then again, trim the time while storing into the database. A js frontend and a db backend can handle Date type natively, while a Golang backend could not.
I propose that we add native support for a date package or a time.Date struct. In case, we choose the latter approach, we need to break the API by removing the existing time.Date() function, which even though called as a "Date" function, accepts "hours, minutes, seconds, nanoseconds and Locations" as input parameters. I propose this for Go 2.

Can you elaborate on the challenges or problems with defining your own Date struct, one that fits the needs of your project?
For example, in https://godoc.org/github.com/shurcooL/resume/component#Date, I needed a very similar Date type as you described. It has only the precision of a year, and possibly a month.
I was able to implement it as a custom type:
// Date represents an imprecise date.
type Date struct {
	Year  int        // Year. E.g., 2009.
	Month time.Month // Month is 1 - 12. 0 means unspecified.
}

Which worked well for the needs of that project.
It also implements some methods that only my project needed. I doubt that a time.Date would've worked for my specific needs, despite being very close to the description you've provided in nature.

The only problem with defining my own Date struct is that, I need to define that.
It is a common feature that many will find useful, (like Context or Mux or CookieJar) I would even argue that native support for Date is more important and useful than native support for Complex numbers, which golang supports already natively.
Defining a Date type is also not very trivial. It is easy to miss things or make mistakes, that it would be reliable if it comes from the stdlib. For example, we need to implement support to verify if the date is actually valid (Say flagging errors for: Feb 29 on non-leap-year or January 45th, etc.) We also need to write MarshalJSON, UnmarshalJSON too. The database drivers (pq for postgres for example) could directly use the Date type instead of an approximate time.Time field to store and retrieve the Date data in the database.

Please explain how's the proposed time.Date type different from the existing time.Time type. AFAICS, they are the same thing, see https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Date.

could directly use the Date type instead of an approximate time.Time

What do you mean by approximate? time.Time's resolution is 1 nanosecond. Javascript's Date has a 1000 times worse resolution - 1 millisecond.
BTW: In a database, you can store the result of time.UTC().UnixNano().

I would even argue that native support for Date is more important and useful than native support for Complex numbers, which golang supports already natively.

Please note that you're mixing the standard library with the language itself. They're different things.
I also don't understand how this would be different or significantly better over the current time.Time.
Marking as Go2, since it would need to break the current time.Date func.

What do you mean by approximate? time.Time's resolution is 1 nanosecond. Javascript's Date has a 1000 times worse resolution - 1 millisecond.

I was wrongly using the word "approximate" (non-native speaker). What I meant is, the driver has to use time.Time for storing a Date sql column. For a TIMESTAMP column, using time.Time is straightforward, but since the standard library does not have a Date type, the sql driver needs to use the same time.Time for both Date and TIMESTAMP/TIME sql columns. By approximate, I meant, a sql type that does not directly map to a golang type.

If your pain lies in SQL, perhaps database/sql (or even a third-party SQL driver package) would be a better place for this?

If your pain lies in SQL, perhaps database/sql (or even a third-party SQL driver package) would be a better place for this?

It is not only SQL. For example, in Javascript, if I do <input type="date"> then it gives a YYYY-MM-DD as value which I cannot directly convert to a time.Date element (in a HTTP API handler in golang).
For example:
type Employee struct {
 Name string
 DoB time.Date
}

func handler(res http.ResponseWriter, req *http.Request) {
    x := Employee{}
    decoder := json.NewDecoder(req.Body)
    err := decoder.Decode(&x)
}

would be easier to write/read than: Declaring Employee:DoB as time.Time writing a MarshalJSON or UnMarshalJSON for Employee struct where I need to convert the incoming string to a time.Time.
If we declare DoB to be a custom struct, then it adds a new extra dependency, which could be avoided if there is a Date package as part of the standard library.
If a separate Date field will be too heavy for the standard library (because it is felt that it can be trivially implemented as a custom struct), I can close the bug report. I just wanted to make a proposal, in case it may be appealing to others too. Thanks.

For example, in Javascript, if I do  then it gives a YYYY-MM-DD as value which I cannot directly convert to a time.Date element (in a HTTP API handler in golang).

But it does not "give you" a YYYY-MM-DD. That's a particular representation of that value, which is just an integer. time.Time is just an integer as well. The two integers in JS Date and time.Time differ by a constant factor of 1000 and it's trivial to go from one of the numbers to the other and vice versa. (Considering above just UTC for the first approximation).

But it does not "give you" a YYYY-MM-DD.

May be I am not clear by "give you". What I meant is, I can write JS code, where I can set/get the value of a date input field as a string
<input type="date" min="2014-02-09" max="2014-02-11" value="2014-02-10" />
$("#myinput").val("2014-02-10"); // with jquery

Here the value, min, max are all taking a string in YYYY-MM-DD format. I can map this string value to a golang time.Time too (or vice versa) but if there is a golang time.Date (or a custom Date struct), that is what I would prefer to map this YYYY-MM-DD value, instead of a time.Time struct.

I can write JS code, where I can set/get the value of a date input field as a string

And you can write Go code where you can get/set a value of time.Time as a string:

https://golang.org/pkg/time/#Time.Format
https://golang.org/pkg/time/#Parse

You may have missed the earlier question, but let me repeat

Please explain how's the proposed time.Date type different from the existing time.Time type. AFAICS, they are the same thing, see https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Date.

Yes, the names of methods differ, the layout string is special (and better) in Go and few other minor details. But the functionality and concepts are otherwise the same. Where do you see the difference and/or missing functionality that would warrant considering adding of time.Time? So far everything you wrote can be done with time.Time rather easily.

Here the value, min, max are all taking a string in YYYY-MM-DD format. I can map this string value to a golang time.Time too (or vice versa) but if there is a golang time.Date (or a custom Date struct), that is what I would prefer to map this YYYY-MM-DD value, instead of a time.Time struct.

Checking limits is a one if statement. That's not a good reason to add a new type to the time package. And you may extend time.Time and add this one limits-checking method. It will contain that if statement discussed above.
BTW, working with times/dates as strings is best left to the last mile when inputting/presenting them. Everywhere else the number (wrapped in time.Time) is more convenient and performant.

I agree with the other posters. If you use a canonical form of time.Time where the time zone is always UTC and the time is always midnight, time.Time seems to work fine as a way of storing and parsing dates to me.
You can write a trivial wrapper around it if you like, but that doesn't seem like it would pull its weight in the standard library. For example: https://play.golang.org/p/Szfza9ZAt0
(note that for convenience I used a type alias, available in go 1.9 only)

See civil.Date in the cloud.google.com/go/civil package for an example of a civil date type:
http://godoc.org/cloud.google.com/go/civil#Date
See also #19700 ("proposal: civil time package").
I recommend the "Fundamental Concepts" section of the cctz library (C++) as a good introduction to the difference between civil and absolute time:
https://github.com/google/cctz#fundamental-concepts
I would strongly recommend against using a time.Time in UTC at midnight as a representation of a civil date or time. A time.Time represents an absolute time and using it to represent civil time is both confusing and error-prone.

A civil date package makes sense, but I would rather see it outside of the standard library before trying to bring it in.

Since Ian basically asked for examples outside the stdlib. In my opinion the date type in the mentioned http://godoc.org/cloud.google.com/go/civil#Date is heavy and awkward.
See https://godoc.org/github.com/rickb777/date, https://godoc.org/github.com/RangelReale/epochdate or https://godoc.org/github.com/infobaleen/date for variations of a lighter approach. The second and the last one are good minimal examples, but rickb777's approach of wrapping it in a struct can protect against some accidents. I wrote the last one, so I may be biased.

I agree wholeheartedly with @neild that instants in time (time.Time) are very different concepts from a civil Date.  It it obvious that they need different types, the question is whether to include it in the stdlib.
I think for me, the problem comes down to documentation.  Any reasonably experienced programmer would look at a timezone-aware "instant in time" library and have serious doubts if it could correctly implement a civil Date.  Even if they were to dig into the code, nothing in there suggests that that is a feature. I think most gophers are going to not dig in any further and look for a library or write their own.
I think we can either document this feature of the time package in prose, or in code (as a time.Date type).  In my opinion both accomplish the task equally well since implementing civil.Date is trivial if you know time.Time supports it, if you do not it is fairly daunting.  This actually seems to be the dividing line between people in this proposal as well.

I think the ideas here are best covered by the ideas in #19700.  Closing in favor of that one.


Interface not working on Windows using WSL no errors

Hello, after following installation recommandations, it compile with no error but it result on the interface not working (no any buttons respond when being clicked) and i basically can't do anything. Maybe i did something wrong. Here are some screenshot of my terminal and web ui.  I am not used to WSL utilisation, i just installed it but i don't know if it require more manipulations in order to work as intended. Thank you by advance for your help to run this promising project on my computer ! :)

Same on me but I installed WIndows not WSL.

Same issue here, WSL anthony@MSI:~/devika$ ollama serve
git clone https://github.com/stitionai/devika.git
cd devika/
uv venv
uv pip install -r requirements.txt
cd ui/
bun install
bun run dev
python3 devika.py
Error: listen tcp <IP_ADDRESS>:11434: bind: address already in use
Cloning into 'devika'...
remote: Enumerating objects: 251, done.
remote: Counting objects: 100% (73/73), done.
remote: Compressing objects: 100% (55/55), done.
remote: Total 251 (delta 43), reused 24 (delta 18), pack-reused 178
Receiving objects: 100% (251/251), 5.23 MiB | 13.10 MiB/s, done.
Resolving deltas: 100% (72/72), done.
Using Python 3.10.12 interpreter at: /usr/bin/python3
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate
Resolved 117 packages in 519ms
Installed 117 packages in 370ms

annotated-types==0.6.0

anthropic==0.21.3

anyio==4.3.0

arabic-reshaper==3.0.0

asn1crypto==1.5.1

beautifulsoup4==4.12.3

blinker==1.7.0

certifi==2024.2.2

cffi==1.16.0

chardet==5.2.0

charset-normalizer==3.3.2

click==8.1.7

colorama==0.4.6

cryptography==42.0.5

cssselect2==0.7.0

distro==1.9.0

exceptiongroup==1.2.0

fastlogging==1.0.0

filelock==3.13.1

flask==3.0.2

flask-cors==4.0.0

fsspec==2024.3.1

gitdb==4.0.11

gitpython==3.1.42

greenlet==3.0.3

h11==0.14.0

html5lib==1.1

httpcore==1.0.4

httpx==0.25.2

huggingface-hub==0.21.4

idna==3.6

iniconfig==2.0.0

itsdangerous==2.1.2

jinja2==3.1.3

joblib==1.3.2

keybert==0.8.4

lxml==5.1.0

markdown==3.6

markdown-it-py==3.0.0

markdownify==0.11.6

markupsafe==2.1.5

mdurl==0.1.2

mistletoe==1.3.0

mpmath==1.3.0

netlify-py==0.1.0

networkx==3.2.1

numpy==1.26.4

nvidia-cublas-cu12==<IP_ADDRESS>

nvidia-cuda-cupti-cu12==12.1.105

nvidia-cuda-nvrtc-cu12==12.1.105

nvidia-cuda-runtime-cu12==12.1.105

nvidia-cudnn-cu12==<IP_ADDRESS>

nvidia-cufft-cu12==<IP_ADDRESS>

nvidia-curand-cu12==<IP_ADDRESS>

nvidia-cusolver-cu12==<IP_ADDRESS>

nvidia-cusparse-cu12==<IP_ADDRESS>

nvidia-nccl-cu12==2.19.3

nvidia-nvjitlink-cu12==12.4.99

nvidia-nvtx-cu12==12.1.105

ollama==0.1.7

openai==1.14.2

oscrypto==1.3.0

packaging==24.0

pdfminer-six==20231228

pillow==10.2.0

playwright==1.42.0

pluggy==1.4.0

pycparser==2.21

pydantic==2.6.4

pydantic-core==2.16.3

pyee==11.0.1

pygments==2.17.2

pyhanko==0.23.1

pyhanko-certvalidator==0.26.3

pypdf==4.1.0

pypng==0.20220715.0

pytest==8.1.1

pytest-base-url==2.1.0

pytest-playwright==0.4.4

python-bidi==0.4.2

python-slugify==8.0.4

pyyaml==6.0.1

qrcode==7.4.2

regex==2023.12.25

reportlab==4.0.9

requests==2.31.0

rich==13.7.1

safetensors==0.4.2

scikit-learn==1.4.1.post1

scipy==1.12.0

sentence-transformers==2.6.0

six==1.16.0

smmap==5.0.1

sniffio==1.3.1

soupsieve==2.5

sqlalchemy==2.0.29

sqlmodel==0.0.16

svglib==1.5.1

sympy==1.12

text-unidecode==1.3

threadpoolctl==3.4.0

tiktoken==0.6.0

tinycss2==1.2.1

tokenizers==0.15.2

toml==0.10.2

tomli==2.0.1

torch==2.2.1

tqdm==4.66.2

transformers==4.39.1

triton==2.2.0

typing-extensions==4.10.0

tzlocal==5.2

uritools==4.0.2

urllib3==1.26.15

webencodings==0.5.1

werkzeug==3.0.1

xhtml2pdf==0.2.15
bun install v1.0.35 (940448d6)

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

163 packages installed [1.71s]
$ vite dev
Forced re-optimization of dependencies
VITE v5.2.2  ready in 443 ms
➜  Local:   http://localhost:3000/
➜  Network: use --host to expose
➜  press h + enter to show help
10:39:15 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:115:10 A11y: '#' is not a valid href attribute
10:39:15 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:124:14 A11y: '#' is not a valid href attribute
10:39:15 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:186:16 A11y: '#' is not a valid href attribute
10:39:16 AM [vite] ✨ new dependencies optimized: xterm
10:39:16 AM [vite] ✨ optimized dependencies changed. reloading
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:115:10 A11y: '#' is not a valid href attribute
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:124:14 A11y: '#' is not a valid href attribute
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:186:16 A11y: '#' is not a valid href attribute
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:115:10 A11y: '#' is not a valid href attribute
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:124:14 A11y: '#' is not a valid href attribute
10:39:16 AM [vite-plugin-svelte] /home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:186:16 A11y: '#' is not a valid href attribute

NOTE:I even tried fresh installing/changing config, but its this file:
/home/anthony/devika/devika/ui/src/lib/components/ControlPanel.svelte:186:16
Which
<a
href="#"
class="text-white block px-4 py-2 text-sm hover:bg-slate-700"
on:click|preventDefault={createNewProject}
>
    is the issue

Same on me but I installed WIndows not WSL.

Windows doesnt have BUN support yet sadly.

Fixed with separate terminals IE:
first is the BUN UI and all that, second terminal is simply running devika/devika.py
Fixed WSL issues.

Same on me but I installed WIndows not WSL.

Windows doesnt have BUN support yet sadly.

What about with WSL, especially WEL2? Is that OK?

Same on me but I installed WIndows not WSL.

Windows doesnt have BUN support yet sadly.

What about with WSL, especially WEL2? Is that OK?

Yes bun is easily installed using ubuntu/visual studio code WSL or just the WSL terminal. still need the 2 terminals though. :D

Fixed with separate terminals IE: first is the BUN UI and all that, second terminal is simply running devika/devika.py Fixed WSL issues.

How you fixed that issue in windows without using WSL?

Not possible to use bun yet on regular windows.

Same Issue with Windows. I used the experimental version of BUN, and everything was going well until I tried to run the code, I tried to start the UI first and then the server but still no response.

Fixed with separate terminals IE: first is the BUN UI and all that, second terminal is simply running devika/devika.py Fixed WSL issues.

Same issue with separated terminals

Fixed with separate terminals IE: first is the BUN UI and all that, second terminal is simply running devika/devika.py Fixed WSL issues.

Same issue with separated terminals

Can you possibly send more info like pip freeze? uv/bun both installed? Do you like pie or cake?

** CMD**

ollama
if its already run or getting freeze than kill their process using
taskkill /IM ollama.exe /F

start ollama

it will resolve the issue

having same issues on windows 10 tried powershell and gitbash even tried different ports not sure whats going off

Same issue here with experimental windows build

fetch the latest changes. I also use windows 11 and install bun(experimental) and works perfectly fine with node 20.9.0.
tell me if it's help or not

I updated to the latest one, now it's even worse :D Now http://localhost:3000/ is just a blank screen.

share the network log and console log from browser also which node version?

It's a bit weird. There are two options: it's either 'loading' instantly, looks like it finished loading, in this case I have a totally empty console log and a pretty populated network log.

If I try to reload it again, it just keeps working (the working icon is spinning indefinitely). The console log is still empty. Network log only has a localhost.

If I press stop, however, I get a cancelled localhost and an error in the console.

Where can I see the node version?

Fetch the latest changes and do a clean install.

When I do the bun run start, I get this:
$ vite build && vite preview
vite v5.2.8 building SSR bundle for production...
✓ 649 modules transformed.
error when starting preview server:
undefined
error: script "start" exited with code 1

do you have latest version of bun?

I updated that as well, now it goes a bit further:
$ vite build && vite preview
vite v5.2.8 building SSR bundle for production...
✓ 649 modules transformed.
vite v5.2.8 building for production...
✓ 688 modules transformed.
.svelte-kit/output/client/_app/version.json                                                            0.03 kB │ gzip:   0.05 kB
.svelte-kit/output/client/.vite/manifest.json                                                          5.68 kB │ gzip:   0.91 kB
.svelte-kit/output/client/_app/immutable/assets/tiktoken_bg.D1vgAo9Z.wasm                          1,100.09 kB
.svelte-kit/output/client/_app/immutable/assets/2.B4T8hs7e.css                                         6.19 kB │ gzip:   2.27 kB
.svelte-kit/output/client/_app/immutable/assets/Toaster.BkLvsHqN.css                                  12.78 kB │ gzip:   2.79 kB
.svelte-kit/output/client/_app/immutable/assets/0.ky7OTPEa.css                                        20.59 kB │ gzip:   4.69 kB
.svelte-kit/output/client/_app/immutable/entry/start.BjLKhbXo.js                                       0.07 kB │ gzip:   0.08 kB
.svelte-kit/output/client/_app/immutable/chunks/stores.Y4PAX1XE.js                                     0.23 kB │ gzip:   0.17 kB
.svelte-kit/output/client/_app/immutable/nodes/1.CcRYBzjx.js                                           0.79 kB │ gzip:   0.50 kB
.svelte-kit/output/client/_app/immutable/chunks/each.M-WWh_9i.js                                       0.86 kB │ gzip:   0.53 kB
.svelte-kit/output/client/_app/immutable/chunks/index.CtFfpz60.js                                      0.99 kB │ gzip:   0.60 kB
.svelte-kit/output/client/_app/immutable/chunks/Toaster.svelte_svelte_type_style_lang.CxETsj9g.js      2.57 kB │ gzip:   1.06 kB
.svelte-kit/output/client/_app/immutable/chunks/mode.D1BbPwL2.js                                       2.66 kB │ gzip:   1.06 kB
.svelte-kit/output/client/_app/immutable/nodes/3.cUIO3gCP.js                                           3.69 kB │ gzip:   1.52 kB
.svelte-kit/output/client/_app/immutable/chunks/index.CcqImCu-.js                                      5.52 kB │ gzip:   2.67 kB
.svelte-kit/output/client/_app/immutable/entry/app.XrUJMKMm.js                                         6.76 kB │ gzip:   2.72 kB
.svelte-kit/output/client/_app/immutable/chunks/icons.N1DyG8ix.js                                      6.98 kB │ gzip:   2.81 kB
.svelte-kit/output/client/_app/immutable/chunks/scheduler.B_jgbYNs.js                                  9.23 kB │ gzip:   3.58 kB
.svelte-kit/output/client/_app/immutable/chunks/utils.Ckxz92B5.js                                     22.06 kB │ gzip:   7.54 kB
.svelte-kit/output/client/_app/immutable/chunks/entry.CKS99Ke6.js                                     25.81 kB │ gzip:  10.32 kB
.svelte-kit/output/client/_app/immutable/nodes/0.C5uExL6Y.js                                          41.27 kB │ gzip:  13.25 kB
.svelte-kit/output/client/_app/immutable/chunks/api.Bs-WsMpV.js                                       42.46 kB │ gzip:  13.28 kB
.svelte-kit/output/client/_app/immutable/nodes/4.By3_eLQt.js                                         120.29 kB │ gzip:  34.82 kB
.svelte-kit/output/client/_app/immutable/nodes/2.CaR3aJ7y.js                                       1,449.05 kB │ gzip: 600.66 kB
(!) Some chunks are larger than 500 kB after minification. Consider:

Using dynamic import() to code-split the application
Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✓ built in 9.06s
error when starting preview server:
undefined
error: script "start" exited with code 1

follow this https://github.com/stitionai/devika?tab=readme-ov-file#installation


PT 159587547 Add contract create compute

PT-159587547
Add tx/contract/create/compute call.

I see it failed the static analysis test but I don't see why. I will try to find the reason and fix it.

I have tried to understand what the problem is but as far as I can see it is complaining that the apps/aehttp/priv/swagger.json file has changed, which is not surprising as I have added to swagger.yaml and rebuilt the .json file. If this is wrong then please let me know what is the problem and I will fix it.

I also see that I have an error in this branch as the first 2 commits shouldn't be there. Perhaps I should kill this PR and fix up the branch first.

I have tried to understand what the problem is but as far as I can see it is complaining that the apps/aehttp/priv/swagger.json file has changed, which is not surprising as I have added to swagger.yaml and rebuilt the .json file. If this is wrong then please let me know what is the problem and I will fix it.

Interesting. Does make swagger-check report same error locally? (I am thinking maybe you locally have a swaggercodegen version that is overloading the one the makefile downloads, or maybe you have a version of Java different from the CI).

I also see that I have an error in this branch as the first 2 commits shouldn't be there. Perhaps I should kill this PR and fix up the branch first. They are good commits but shouldn't be there, they were supposed to be in another branch.

I see this PR needs rebase anyway because of apps/aehttp/test/aehttp_contracts_SUITE.erl conflict. I suggest rebasing/selecting commits and force-pushing on this same branch PR (and opening separate PR(s) for commits you feel do not fit focus of this PR).

Does make swagger-check report same error locally?

BTW this is check that CI runs: https://github.com/aeternity/epoch/blob/2db7ecae9f34a91ff7291ea3de265cd2585a1688/.circleci/config.yml#L310

make python-env && make swagger-check

I confirm running locally that I get many errors too. I suggest rebasing on master, re-generating swagger.json and force-pushing.

So I rebased it onto the latest master (last night) and added the changes needed, really only changing the mining calls.
What do you mean by the release notes file?

What do you mean by the release notes file?

This file. (I should have been more explicit - apologies.)
Please refer to past examples. It is best development practice to update release notes file in same PR that does functional change (even if it sometimes introduces conflicts among concurrent PRs).

OK, added info in release notes file.

I took the liberty of marking as WIP - PR in protocol repo needed plus rebase of this PR needed for conflict on release notes.

OK, I will rebase and fix a PR for the protocol.


FIx non-openable links in Linux

This solve #108 by using Electrons shell.openExternal instead of the open package. Please verify that it still works on Windows.

Works in W10 (1709) and Elemenary Freya


Exception when resolving controller with ILogger as dependency

First, thanks for the awesome project! It is very useful, and I appreciate your keeping up with the .NET Core releases.
I've found an issue when a MVC Controller has a dependency on ILogger without a generic constraint. When the generic constraint is present, there is no exception. So
  [Route("api/[controller]")]
    public class ValuesController : Controller
    {
        public ValuesController(ILogger<ValuesController> logger)
        {
            _logger = logger;
        }
    }

Works correctly while
[Route("api/[controller]")]
  public class ValuesController : Controller
  {
      public ValuesController(ILogger logger)
      {
          _logger = logger;
      }
  }

Throws
2016-06-03 15:03:40.534 -07:00 [Error] Connection id ""0HKSBVBLPGB18"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Unable to resolve service for type 'Microsoft.Extensions.Logging.ILogger' while attempting to activate 'TestWebApp.Controllers.ValuesController'.
   at Microsoft.Extensions.Internal.ActivatorUtilities.GetService(IServiceProvider sp, Type type, Type requiredBy, Boolean isDefaultParameterRequired)
   at lambda_method(Closure , IServiceProvider , Object[] )
   at Microsoft.AspNetCore.Mvc.Internal.TypeActivatorCache.CreateInstance[TInstance](IServiceProvider serviceProvider, Type implementationType)
   at Microsoft.AspNetCore.Mvc.Controllers.DefaultControllerFactory.CreateController(ControllerContext context)
   at Microsoft.AspNetCore.Mvc.Internal.FilterActionInvoker.<InvokeAllActionFiltersAsync>d__40.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.FilterActionInvoker.<InvokeExceptionFilterAsync>d__39.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Internal.FilterActionInvoker.<InvokeAsync>d__32.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.MvcRouteHandler.<InvokeActionAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Swashbuckle.SwaggerUi.Application.SwaggerUiMiddleware.<Invoke>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Swashbuckle.SwaggerUi.Application.RedirectMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Swashbuckle.SwaggerGen.Application.SwaggerGenMiddleware.<Invoke>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.IISIntegration.IISMiddleware.<Invoke>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.Kestrel.Http.Frame`1.<RequestProcessingAsync>d__2.MoveNext()
2016-06-03 15:03:40.543 -07:00 [Information] Request finished in 463.8336ms 200

I am using Serilog, but the default ILogger interfaces.
Let me know if you need additional information.
Thanks,
Erick

This is not a swashbuckle issue

System.InvalidOperationException: Unable to resolve service for type 'Microsoft.Extensions.Logging.ILogger'

The error you're seeing is correct, ILogger is not registered as a server. You have two options:

Resolve ILoggerFactory and call CreateLogger(string name)
Resolve ILogger<T> - this does what 1) does, and provides a name based on T


[BUG] Roblox download

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?
Whenever I try and download roblox on my windows ten pc it doesn't work no more and i'm trying to fix that.

Can you describe the problem more specifically please?

Issue has stale for over a month, and will be reopened if further information is given.


k3s fails after upgrade

I have a fairly clean installation, not really anything deployed yet other that a small test app but it came to me (on a RPI computer) set up with an older version of k3s. So after using it for a while I decided to upgrade k3s. That did not go well as now it won't start up.
Environmental Info:
K3s Version:
v1.26.4+k3s1 (8d0255af)
Node(s) CPU architecture, OS, and Version:
Linux pibox 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
Cluster Configuration:
1 node that does it all
Describe the bug:
after upgrading from v1.24.4+k3s1 to v1.26.4+k3s1, k3s server now fails with this:
level=fatal msg="flannel exited: failed to acquire lease: subnet \"<IP_ADDRESS>/16\" specified in the flannel net config doesn't contain \"<IP_ADDRESS>/24\" PodCIDR of the \"pibox\" node"
k3s.service: Main process exited, code=exited, status=1/FAILURE
k3s.service: Failed with result 'exit-code'.

Steps To Reproduce:
just upgrade from v1.24.4+k3s1 using:
curl -sfL https://get.k3s.io | sh -

Expected behavior:
a clean upgrade
Actual behavior:
broken installation
Additional context / logs:
content of /var/lib/rancher/k3s/agent/etc/flannel/net-conf.json
{
        "Network": "<IP_ADDRESS>/16",
        "EnableIPv6": false,
        "EnableIPv4": true,
        "IPv6Network": "::/0",
        "Backend": {
        "Type": "vxlan"
}
}

I also see this in the logs - not sure if relevant:
Updating runtime config through cri with podcidr" CIDR="<IP_ADDRESS>/24
Initialized iptables rules." protocol=IPv4
Updating Pod CIDR" originalPodCIDR="" newPodCIDR="<IP_ADDRESS>/24

If you run k3s with the following config?
curl -sfL https://get.k3s.io | sh -s - --cluster-cidr: "<IP_ADDRESS>/16"
I think you configured a cluster-cidr on your previous setup.

So I'm not sure what options where used originally (the pibox came to me pre-configured with k3s) but from what I can tell, kube-system namespace several services were running in both the 10.43.10.x and 10.43.0.x address spaces. Pods in yet another 10.43.x.x. Furthermore, the rancher flannel conf file had one of those as well. I eventually got it working by finding a version of the k3s provisioning script used and through trial and error found that what was likely used (the authors switched it up a few times). Luckily I found just running the https://get.k3s.io upgrade again until I found the magic combination seems to do the right thing (mostly).
This is what finally stopped making things crash but not quite work. I'm not sure it is entirely correct but it works.
--cluster-cidr=<IP_ADDRESS>/24 --service-cidr=<IP_ADDRESS>/24
And I had to delete all the services and recreate them to get it fully back up and running as they hung onto the old 10.43.x.x addresses and continued to fail.
Oddly there's was never version of the k3s provisioning script for this device that ever used a cidr like 10.43.x.x (but there were versions that never specified a cidr at all during install). I have no idea which version of that script was used for my device unfortunately.
Which makes me wonder: Is this expected during an upgrade that those options have to be repeated exactly as first used? That you have to remember and use the same options or it all falls apart? Is there not a way/place for k3s to remember that so that upgrading is easier (i.e. keep the same config)?
Is there anything I should have done differently (other than somehow knowing how it was originally set up)?

Do you need the previous setup configuration? You can also run k3s-uninstall.sh script and deploy a new installation.

Well I had a functioning installation that I was trying to upgrade. The upgrade process broke because it didn't keep the configuration, leaving everything in a broken network State.
So in that sense, yes I think I needed the k3s upgrade process to keep the existing configuration.
I expected an upgrade to not break things. Or at least warn me that it was going to break things.

all args are valid config file entries. Just convert them to yaml:
cluster-cidr: <IP_ADDRESS>/24
service-cidr: <IP_ADDRESS>/24
disable:
  - traefik

and so on

I will note that I think you still have issues with your CIDRs, the cluster and service cidrs cannot overlap, and /24 is far too small. these are usually /16s.

I thought that too but this is what they (who set this up initially) used. Later on, they switched to this, which I tried, but it was giving me even more server & flannel errors on start up.
--cluster-cidr=<IP_ADDRESS>/16 --service-cidr=<IP_ADDRESS>/16

I agree that makes more sense but the server also didn't seem to like using 172.30.x.x and 172.31.xxx so unless they matched, it would not start. But maybe now that I've gotten things working and resolve the broken svcs, I can migrate back to the separate /24 addresses.

I thought that too but this is what they (who set this up initially) used.

It sounds like the pibox hosts shipped you a pretty broken configuration, and now you get to try to unwind it. You might be better off just starting over from scratch and redeploying your manifests.

I eventually sorted this out. It required using killall and me to delete and recreate the node so that I could edit the PodCIDR so that I could have separate 172.3x networks for the cluster and services. So I think this can be closed now.
BUT, I would sure like to see the upgrade documentation have something about how you have to use the same arguments when upgrading manually via the script. That would have saved me a lot of heartache and I just don't see that info anywhere in the docs.

https://docs.k3s.io/upgrades/manual#upgrade-k3s-using-the-installation-script

To upgrade K3s from an older version you can re-run the installation script using the same flags, for example:

I guess we could call out what happens if you ignore that, and don't use the same flags when re-running the installer?

ok, yeah I totally missed the implications of that.

closing, will improve docs.


Add lifecycle tests and fix resultant bug

Test the cache using gateway events rather than updating the cache
directly through private methods.
These tests found one bug in Role management, which will be fixed in
the next commit.

Closing this PR in favor of a wider overhaul of the cache's tests. The fix will be PRd separately.


Bug: timescale_service resource not propagating its attributes

Hi Timescale team,
We're currently deploying TS services thanks to your Terraform provider (v1.9.0) and are eager to integrate your provider with our multi tenant client deployments.
We have managed to programmatically create a Timescale VPC and accept automatically the Timescale peering connection within our AWS cloud, while launching a service and associating it with an internal DNS record (Route53).
While this works admirably, we reset the instance password through the Timescale web UI and ran into a situation where the password provided by the timescale_service resource didn't refresh, despite resync'ing / refreshing our Terraform plan.
To allow our application to connect, we had to destroy such a Timescale service and recreate a new one from scratch (and we ran into https://github.com/timescale/terraform-provider-timescale/issues/177 as well, where Terraform couldn't recognise that it was removed).
Please let us know if you need more information to investigate the issue. Many thanks in advance!

Thank you for your feedback.
I'm investigate as I know we labeled password a sensitive field and terraform internals might have a specific dynamic for it that we did not implement yet.

@Khyme I'm storing the timescale password in a secrets manager when terraform is run. It becomes null in the secrets manager everytime I run terraform, most likely because of this issue. Also, weirdly, only seeing this in one deployment. Is there a workaround/fix in progress?


Added support for Gradle

WARNING, ACHTUNG, AVISO, BEEP BEEP MORP!!!! Not really meant for merging, I'd just like some feedback.
So I've been working on adding support for Gradle to Ament, but I don't know if this is the correct approach. I wondered if there's a way to add Gradle in a modular way without actually changing Ament itself, but I couldn't figure out how.
An example which uses this and Gradle to build an .apk for Android can be found at https://github.com/esteve/ros2_talker/ (see https://github.com/esteve/ros2_talker/blob/master/build.gradle for the Gradle file)
Thanks!
:hamburger:

The build types are registered through entry points (https://github.com/ament/ament_tools/blob/51add3f0c449db97d63dc32a99c09fab495af728/setup.py#L51-L55). This can happen within this package as well as in a separate package. Once ament_tools and ament_build_type_gradle (or whatever name) has been built the command line tool ament will pick up all entry points and support all available build types.

@dirk-thomas cool, thank you so much for the explanation! So, I just need to create an new package (that uses ament_python as a build type) and add the following to the setup.py, and ament will add it as a supported build type, that's fantastic!
entry_points={
        'ament.build_types': [
            'ament_gradle = ament_build_type_gradle:AmentGradleBuildType',
        ],

Do I then have to add ament_build_type_gradle as a buildtool dependency too to any package that I want to build with ament_gradle, is that correct?

Do I then have to add ament_build_type_gradle as a buildtool dependency too to any package that I want to build with ament_gradle, is that correct?

Yes, that would be the cleanest. If you have built ament_build_type_gradle in another workspace it will work anyway.

It worked, thanks! I moved this to a separate package and did as you said. I have to build ament first and then use the ament tool from the install space, instead of doing it all in one pass, but it's no big deal. Thanks!

Can you please add a link to the new package so that when people find this ticket can find it.

It's not public yet, but I already planned to link to it when I release it.


Calling dotnet test from a shell script fails on Ubuntu server with net core 3

From @stuartd on Thursday, October 10, 2019 4:08:16 PM
We have a shell script that runs our .net core 3 integration tests on a Ubuntu server: it was running just fine, but since upgrading to .net core 3 it has stopped working.
It still works on OSX and in WSL using net core 3 (and the equivalent .bat file works on Windows).
I have reinstalled .net core 3 on the server but to no effect.
There are two problems, which are detailed below:

Calling dotnet test from a shell script fails with a permissions error in net core 3, but when calling it from the command line it will run - however..
Parameters to dotnet test are somehow mangled when running from the command line.

Permissions error
The shell script is just this:
# this works just fine
git pull

# run the project which gets the repo path, CDs to the test project folder,
# and runs the tests, passing along any parameters as a test filter
dotnet run --project TestRunner/TestRunner.csproj $@

# run the project which analyzes the test results and generates a results page
dotnet run --project TestResultAnalyzer/TestResultAnalyzer/TestResultAnalyzer.csproj

The first issue is a permissions error calling dotnet test from the script: this is the diagnostic output of the TestRunner project:
Current directory: /home/username/code/codename/src/API/App/App.Tests
Test command:
dotnet test --filter skeleton -l:trx;LogFileName=App_Test_Run_2019-10-10-11-40.trx -r /home/username/code/codename/src/API/TestRuns/App
Starting process

And this is the error which occurs when starting the process:

Unhandled exception. System.ComponentModel.Win32Exception (13): Permission denied
at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at TestRunner.Program.Main(String[] args) in /home/username/code/codename/src/Misc/TestRunner/Program.cs:line 77

And this is the code:
process = new Process {
	StartInfo = {
		Arguments = $"test {arguments} -l:trx;LogFileName={testRunName}.trx -r {testResultFolder}",
		FileName = "dotnet",
		UseShellExecute = false
	}
};

var commandDebug = $"{process.StartInfo.FileName} {process.StartInfo.Arguments}";

Console.WriteLine("Test command");
Console.WriteLine(commandDebug);
Console.WriteLine("Starting process");
process.Start(); // boom

So, my first issue is:
Why is calling dotnet test from a shell script resulting in a permissions error, when calling it from the command line does not?
Test parameter mangling
And that leads to my second issue.
If I run the above from the command line (note we are using NUnit as the test runner)
dotnet test --filter skeleton -l:trx;LogFileName=App_Test_Run_2019-10-10-11-40.trx -r /home/username/code/codename/src/API/TestRuns/App
Then the tests run, but I get this error message:

-r: command not found

As per the documentation, -r specifies the location of the test output file:

Directory in which to find the binaries to run.
-r|--results-directory

And indeed the file is not put in the right place, it ends out here, instead of in the TestRuns/App folder as specified:

/home/username/code/codename/src/API/App/App.Tests/TestResults/_servername_2019-10-10_11_46_36.trx

And thus the analyzer can't find it, as it's not in the right place.
Now as I said above, this exact same code works in Windows, OSX and WSL and worked on Ubuntu with net core 2.2 - but on the Ubuntu server it Just. Will. Not. Work. with net core 3.
So the second issue is:
Why is this test syntax not working on Ubuntu under net core 3?
Supplementary info:
Output of dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /snap/dotnet-sdk/49/sdk/3.0.100/

Host (useful for support):
  Version: 3.0.0
  Commit:  7d57652f33

.NET Core SDKs installed:
  3.0.100 [/snap/dotnet-sdk/49/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0 [/snap/dotnet-sdk/49/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0 [/snap/dotnet-sdk/49/shared/Microsoft.NETCore.App]

Package references in the test project
<ItemGroup>
  <PackageReference Include="FluentAssertions" Version="5.9.0" />
  <PackageReference Include="JetBrains.DotMemoryUnit" Version="3.0.20171219.105559" />
  <PackageReference Include="nunit" Version="3.12.0" />
  <PackageReference Include="NUnit.ConsoleRunner" Version="3.10.0" />
  <PackageReference Include="NUnit3TestAdapter" Version="3.15.1" />
  <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.3.0" />
</ItemGroup>

Server culture
The server culture is en-US-POSIX (which hates humans and their puny case-sensitivity, but I digress..)
Copied from original issue: dotnet/cli#12860

@stuartd I am trying to reproduce this issue, are you still facing it? I see some inconsistencies in behavior between 2.1 3.0 and 3.1 dotnet sdk in connection to LC_ALL=POSIX, but can't reproduce the exact problem you have. On the other hand I am getting some weird escape sequence printed into my terminal.
If you are still facing this issue, could you share a simple project that shows the error? I am for example not sure how you are getting the testRunName and testResultFolder, and that is potetnially important if you are running it from a script because this looks like a double parsing issue.
Thanks!

I did try it under 3.1 last week and still got the error.
I'll have a go at setting up a repro, when I can carve out some time.

I am for example not sure how you are getting the testRunName and testResultFolder

We get them like this:
// get local repo path
var process = new Process {
	StartInfo = {
		Arguments = "rev-parse --show-toplevel",
		FileName = "git",
		RedirectStandardOutput = true
	}
};

Console.WriteLine($"Starting git with command line: {process.StartInfo.FileName} {process.StartInfo.Arguments}");

process.Start();

string rootPath = null;
while (!process.StandardOutput.EndOfStream) {
	rootPath = process.StandardOutput.ReadLine();
}

process.WaitForExit();

Console.WriteLine($"Completed git request, using repo path '{rootPath}'");

rootPath = rootPath.Replace("/", @"\");

// This is the folder containing the project we run the tests in
var testDir = Path.Combine(rootPath, @"src\API\Project\Project.Tests");

// This is the folder where we want the test output file to be stored
var testResultFolder = Path.Combine(rootPath, @"src\Misc\TestRuns\Project");

if (!RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) {
	testResultFolder = testResultFolder.Replace(@"\", "/");
	testDir = testDir.Replace(@"\", "/");
}

Console.WriteLine($"Test result folder: {testResultFolder}");

Directory.CreateDirectory(testResultFolder);

Console.WriteLine($"Test folder: {testDir}");

Directory.SetCurrentDirectory(testDir);

Console.WriteLine("Current directory: " + Directory.GetCurrentDirectory());

var testRunName = "Project_Test_Run_" + DateTime.Now.ToString("yyyy-MM-dd-HH-mm");

string arguments = args.Any()
	? "--filter " + string.Join(" ", args)
	: null;

process = new Process {
	StartInfo = {
		Arguments = $"test {arguments} -l:trx;LogFileName={testRunName}.trx -r {testResultFolder}",
		FileName = "dotnet",
		UseShellExecute = false
	}
};

// and here we get the permissions error.
var command = $"{process.StartInfo.FileName} {process.StartInfo.Arguments}";

that is potetnially important if you are running it from a script because this looks like a double parsing issue

However, the second issue above - the error message when running the command generated by the above code directly in the terminal - still happens.
When I run this command:
dotnet test --filter skeleton -l:trx;LogFileName=Project_Test_Run_2020-02-11-17-05.trx -r /home/sme-graph/code/vendorgraph/src/Misc/TestRuns/Project

This is the final output:
-r: command not found

.. and the output file is not where it should be.

@stuartd thanks!

I am not seeing the access denied issue, nor the parameter mangling. I only see the -r command not found when I run it directly in terminal (see below).
I tried reproducing this like this, and it works:

n@nuuuub:~/folder$ ./runner.sh
Microsoft (R) Build Engine version 16.3.2+e481bbf88 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 31.71 ms for /home/n/folder/console1/console1.csproj.
  console1 -> /home/n/folder/console1/bin/Debug/netcoreapp3.0/console1.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:00.79
Microsoft (R) Build Engine version 16.3.2+e481bbf88 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 19.35 ms for /home/n/folder/src/API/Project/Project.Tests/Project.Tests.csproj.
  Project.Tests -> /home/n/folder/src/API/Project/Project.Tests/bin/Debug/netcoreapp3.0/Project.Tests.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:00.86
Starting git with command line: git rev-parse --show-toplevel
Completed git request, using repo path '/home/n/folder'
Test result folder: /home/n/folder/src/Misc/TestRuns/Project
Test folder: /home/n/folder/src/API/Project/Project.Tests
Current directory: /home/n/folder/src/API/Project/Project.Tests
Test command
dotnet test  -l:trx;LogFileName=Project_Test_Run_2020-02-24-16-31-19.trx -r /home/n/folder/src/Misc/TestRuns/Project
Starting process
n@nuuuub:~/folder$ Test run for /home/n/folder/src/API/Project/Project.Tests/bin/Debug/netcoreapp3.0/Project.Tests.dll(.NETCoreApp,Version=v3.0)
Microsoft (R) Test Execution Command Line Tool Version 16.3.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.
;1RResults File: /home/n/folder/src/Misc/TestRuns/Project/Project_Test_Run_2020-02-24-16-31-19.trx

n@nuuuub:~/folder$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.103
 Commit:    b7ef045669

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /snap/dotnet-sdk/65/sdk/3.0.103/

Host (useful for support):
  Version: 3.0.3
  Commit:  c03f2fe626

.NET Core SDKs installed:
  3.0.103 [/snap/dotnet-sdk/65/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.3 [/snap/dotnet-sdk/65/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.3 [/snap/dotnet-sdk/65/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

I can see the -r command not found error when I paste the code directly to command line, and it is caused by missing quotes:
-l:trx;LogFileName=Project_Test_Run_2020-02-11-17-05.trx -r <- incorrect
-l:"trx;LogFileName=Project_Test_Run_2020-02-11-17-05.trx" -r <- correct
You are basically terminating the first command on the ;, then defining an environment variable for the next command -r which does not exist, and so bash reports the error.
folder.zip

I faced  such a problem in .Net Core 3.1 when copying script from windows to Ubuntu.
The script contain commands with parameters.
dotnet myapp.dll --param1 --param2

If I run the commands from the terminal it is working fine, but fail from the script file.
The root problem was that every line was ended with CRLF characters.
I used dos2unix to convert the file to unix format and now  it is working fine.
sudo apt-get install dos2unix
dos2unix run.sh
./run.sh    # now it's ok

@nohwnd thank you very much and @moh-hassan that's very interesting. I had a niggling thought at the back of my mind about line terminators, but never looked at it properly.
I've been very busy (as are we all, of course) but I will look into these as soon as I can.

@stuartd gentle ping, if you'd find a moment to try this out 🙂

@stuartd Closing this due to no activity, the issue with ; should be a syntax issue. Let us know if you need more assistance.


Radio Group: Handle orientation

As per Compose guidelines, we let the consumersa implement the radio group however an example is provided in our demo app as well as in the component's readme file.


Check Each Module for Spotbugs and Checkstyle Validations

Seems like some of the modules are missing the spotbugs and checkstyle validation.
These two checks should be added to the every module build
Additionally, we should also fix the module builds which aren't configured to skip tests when ./gradlew build -x test is not skipping tests. Please tick the box if both the tasks are completed.
Let's verify each module here:

[ ] http
[ ] io
[x] encoding
[ ] java.arrays
[ ] jsonutils
[ ] random
[ ] runtime
[ ] regex
[ ] task
[x] time
[ ] xmlutils
[x] crypto
[ ] os
[ ] xslt
[ ] config
[ ] reflect
[ ] uuid
[ ] log
[ ] cache
[x] file
[ ] ftp
[ ] mime
[x] nats
[x] stan
[ ] tcp
[ ] udp
[x] auth
[ ] email
[x] jwt
[x] oauth2
[x] graphql
[ ] grpc
[ ] websocket
[ ] websub
[ ] websub
[ ] websubhub
[x] kafka
[x] rabbitmq
[ ] sql
[ ] java.jdbc
[ ] mysql

Messaging modules:
https://github.com/ballerina-platform/module-ballerinax-kafka/pull/56
https://github.com/ballerina-platform/module-ballerinax-nats/pull/43
https://github.com/ballerina-platform/module-ballerinax-rabbitmq/pull/46

Messaging modules:
https://github.com/ballerina-platform/module-ballerinax-kafka/pull/56
https://github.com/ballerina-platform/module-ballerinax-nats/pull/43
https://github.com/ballerina-platform/module-ballerinax-rabbitmq/pull/46

Checkstyle & Spotbugs validations are invalid for regex module since it doesn't have any native code.

Checkstyle & Spotbugs validations are invalid for regex module since it doesn't have any native code.

Completed


How to remove packages?

I followed the instructions in the wiki, but then decided that I didn't want to stick with this solution. I've tried to remove the packages that I installed in the process, but it seems that some of them can't be removed (pipewire-bin for example) - gnome itself is dependent on them. Was this dependency added in the process of following the instructions? Or is it possible these packages were already installed?
Either way, documentation on how to revert the installation described in the wiki would be very helpful.

see https://pastebin.com/FJGEjqPQ there is no gnome dependencies. Uninstall is quite straightforward like installation. Reverse of installation process.

Either way, documentation on how to revert the installation described in the wiki would be very helpful.

What to write man? Everything is simple.
The main goal of this PPA

Make Everything simple as much as possible.
To provide the latest release of PipeWire to debian/ubuntu users without modifying anything as the version is very old on their official repository.
To help its developers to make the PipeWire a bugfree product. As the Majority of Linux users targets ubuntu/debian based distros, If they can test PipeWire and report bugs or feature request to upstream you are unknowingly contribute to the project.

Meanwhile PipeWire 0.3.29 is released you can try.

Attempting to even remove just "pipewire" causes the following on my machine:
sudo apt remove pipewire
[sudo] password for trappar:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gir1.2-accountsservice-1.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdm-1.0
  gir1.2-gnomebluetooth-1.0 gir1.2-graphene-1.0 gir1.2-mutter-7 gir1.2-nm-1.0
  gir1.2-nma-1.0 gir1.2-rsvg-2.0 gir1.2-upowerglib-1.0 gnome-session-bin
  gnome-session-common gnome-shell-common gnome-shell-extension-system76-power
  gnome-startup-applications gtk2-engines-murrine libfreerdp2-2 libmutter-7-0
  libvncserver1 libwinpr2-2 libxcb-res0 libxkbcommon-x11-0 mutter-common
  pop-gnome-shell-theme pop-gtk-theme pop-icon-theme pop-shell
  pop-shell-plugin-system76-power pop-shell-shortcuts pop-sound-theme
  pop-theme switcheroo-control xwayland
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  policykit-1-gnome
The following packages will be REMOVED:
  chrome-gnome-shell gdm3 gnome-remote-desktop gnome-shell
  gnome-shell-extension-alt-tab-raise-first-window
  gnome-shell-extension-always-show-workspaces
  gnome-shell-extension-appindicator gnome-shell-extension-desktop-icons-ng
  gnome-shell-extension-pop-shop-details gnome-shell-extension-prefs
  gstreamer1.0-pipewire pipewire pop-default-settings pop-desktop pop-session
The following NEW packages will be installed:
  policykit-1-gnome
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  pop-desktop pop-session (due to pop-desktop)
  chrome-gnome-shell (due to pop-desktop) gdm3 (due to pop-desktop)
  gnome-shell (due to pop-desktop) pop-default-settings (due to pop-desktop)
0 upgraded, 1 newly installed, 15 to remove and 0 not upgraded.
Need to get 25.0 kB of archives.
After this operation, 10.1 MB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'

This appears to be because...
sudo dpkg --remove pipewire
dpkg: dependency problems prevent removal of pipewire:amd64:
 gstreamer1.0-pipewire:amd64 depends on pipewire (= 0.3.28-1~ubuntu20.10).
 gnome-remote-desktop depends on pipewire (>= 0.3.0).

dpkg: error processing package pipewire:amd64 (--remove):
 dependency problems - not removing
Errors were encountered while processing:
 pipewire:amd64

gnome-remote-desktop depends on pipewire (>= 0.3.0).

Read above carefully. what can i do for then? And all dependencies of https://packages.ubuntu.com/hirsute/gnome-remote-desktop will be removed as well. This is general problem, you have to search on net. PipeWire doesn't have any dependencies on above you mentioned. Please always use issue template for reporting, it saves my time

Hii @trappar  everything is fine with pipewire on my machine look below :
pop-os@pop-os:~$ pactl info
Server String: /run/user/999/pulse/native
Library Protocol Version: 34
Server Protocol Version: 35
Is Local: yes
Client Index: 57
Tile Size: 65472
User Name: pop-os
Host Name: pop-os
Server Name: PulseAudio (on PipeWire 0.3.29)
Server Version: 14.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_05.0.analog-stereo
Default Source: alsa_card.pci-0000:00:05.0.capture.0.0
Cookie: 51cc:9393
pop-os@pop-os:~$

The problem is because of PipeWire is already install as gnome-remote-desktop depends on pipewire (>= 0.3.0) and there is no way to completely remove PipeWire. To insall latest version follow wiki, If installation terminates with error run sudo apt-get install --fix-broken. This would make PipeWire install successfully. After that on every 15 days PipeWire should be upgraded as it is its release cycle.
How ever If you still want to remove there are tons of tutorial available on the internet like this one : ppa-purge program.
These are edge case, I can't write every edge case in installation wiki. There are thousands of debian derivated os. So for which one I should write.

How to remove Packages?

Tons of this types of questions and answer are available on internet, Search it.
:warning:  Can you confirm, Does it solves your problem? May I close it?

Yes, you can close this.

Thank you, Closing it now., As you told me, I have included uninstallation instructions and included ppa-purge program naively in this PPA, see this https://pipewire-debian.github.io/pipewire-debian/#uninstalling. If you wish you can further install and test it.


RenderObjectElement insertRenderObjectChild seems to throw an error when it shouldn't

Here's the implementation for insertRenderObjectChild in RenderObjectElement
@protected
  void insertRenderObjectChild(covariant RenderObject child, covariant Object? slot) {
    assert(() {
      throw FlutterError.fromParts(<DiagnosticsNode>[
        ErrorSummary('RenderObjectElement.insertChildRenderObject() is deprecated.'),
        toDiagnosticsNode(
          name: 'insertChildRenderObject() was called on this Element',
          style: DiagnosticsTreeStyle.shallow,
        ),
        ErrorDescription(
          'insertChildRenderObject() has been deprecated in favor of '
          'insertRenderObjectChild(). See https://github.com/flutter/flutter/issues/63269 '
          'for details.',
        ),
        ErrorHint(
          'Rather than overriding insertChildRenderObject() in your '
          'RenderObjectElement subclass, override insertRenderObjectChild() instead, '
          "and DON'T call super.insertRenderObjectChild(). If you're implementing a "
          'new RenderObjectElement, you should override/implement '
          'insertRenderObjectChild(), moveRenderObjectChild(), and '
          'removeRenderObjectChild().',
        ),
      ]);
    }());
  }

This method throws an error that says "insertChildRenderObject() has been deprecated in favor of insertRenderObjectChild()". Except, this method isn't called insertChildRenderObject(), it's called insertRenderObjectChild, which means this is the method that the error message is telling us to use.
This method is called from:
@override
  void attachRenderObject(Object? newSlot) {
    assert(_ancestorRenderObjectElement == null);
    _slot = newSlot;
    _ancestorRenderObjectElement = _findAncestorRenderObjectElement();
    _ancestorRenderObjectElement?.insertRenderObjectChild(renderObject, newSlot);
    final ParentDataElement<ParentData>? parentDataElement = _findAncestorParentDataElement();
    if (parentDataElement != null) {
      _updateParentData(parentDataElement.widget as ParentDataWidget<ParentData>);
    }
  }

I can see this in the following file:
https://github.com/flutter/flutter/blob/5804c1232302e978b1835fe769cbfd55fa04b8b4/packages/flutter/lib/src/widgets/framework.dart#L6160-L6169

Looks like when we removed the deprecated method RenderObjectElement.insertChildRenderObject we forgot to update this here.
cc @Piinks do you remember when this was removed?


Idea: Package Chromium and call it form a real App

Anyone know how how to get rid of the Chrome icon in the dock when it opens ?

Could you please provide a bit more information: which OS (macOS?), how do you run the app (as a bundle?) etc.

Sounds interesting - any progress? :+1:

I would really like this as an option.


Use image height to calculate watermark top offset

Shouldn't we use image height to properly calculate watermark top offset?

Oops! Thanks for the fix!


Destroying stack containing Lambda@Edge fails

Deleting Lambda@Edge functions manually is not possible as of now in AWS. The Lambda@Edge function gets deleted automatically 1 hour after the associated Cloudfront distribution gets removed. As such, Pulumi destroy keeps on failing during that time. Ideally, Pulumi should skip the deletion of Lambda@Edge functions.

As a workaround, you can pulumi state delete the function in question (which will leave it behind) if this is preventing you from destroying the rest of your stack. Then, delete the function after the replicas no longer exist.

@leezen AWS will delete the function automatically (replicas included). So really if the SDK tracked these functions differently (and didn't attempt to delete at all) it wouldn't be a problem.
@allroundexperts did you find a workaround?

https://forums.aws.amazon.com/thread.jspa?threadID=331402

So the only workaround that I found was using pulumi state delete the function in question. I think it would be more easier for Pulumi to treat replicas differently instead of Amazon directly.

@leezen AWS will delete the function automatically (replicas included). So really if the SDK tracked these functions differently (and didn't attempt to delete at all) it wouldn't be a problem.
@allroundexperts did you find a workaround?
I think a simple solution Amazon could provide is to not return a 400 in this case, but just treat the call as a success (the fucntion will get deleted eventually by CloudFront anyways). If you want to show support, check out my thread on their forums https://forums.aws.amazon.com/thread.jspa?threadID=331402

So the only workaround that I found was using pulumi state delete the function in question. I think it would be more easier for Pulumi to treat replicas differently instead of Amazon directly.

This is being tracked upstream in https://github.com/hashicorp/terraform-provider-aws/issues/1721.

It looks like this has been fixed upstream two weeks ago with https://github.com/hashicorp/terraform-provider-aws/pull/29646. 🎉
Any ETA when this might be integrated in Pulumi? We're blocked by this issue in an e2e test-setup that creates a new stack for each build (destroying the resources manually is not a feasible option in this case).

Just tested it with the latest @pulumi/aws (v5.31.0), which seems to integrate the relevant terraform-provider-aws version (https://github.com/pulumi/pulumi-aws/releases/tag/v5.31.0). This time it tried for 10 minutes to delete two Lambda@Edge functions. Unfortunately, this might still not be enough:
aws:lambda:Function (lambda-edge-redirect-404-to-resizer):
    error: deleting urn:pulumi:test-add-e2e-tests::file-processing-service::aws:lambda/function:Function::lambda-edge-redirect-404-to-resizer: 1 error occurred:
    	* deleting Lambda Function (lambda-edge-redirect-404-to-resizer-4ac83c9): operation error Lambda: DeleteFunction, https response error StatusCode: 400, RequestID: ea99fb70-6272-4b53-bad6-ba50f035cbf2, InvalidParameterValueException: Lambda was unable to delete arn:aws:lambda:us-east-1:xxx:function:lambda-edge-redirect-404-to-resizer-4ac83c9:1 because it is a replicated function. Please see our documentation for Deleting Lambda@Edge Functions and Replicas.

I'm having similar issues with a single lambda@edge function. On first try to delete it times out. If I wait a while and try again, it deletes nearly instantaneously.

I am having the same issue and we are using @pulumi/aws (v5.40.0).
As it is fixed upstream, can we expect to get it fixed too?

This is a limitation of the way Lambda@Edge works in AWS. When a Lambda@Edge function is deployed it is replicated to all of the edge locations. When it is then deleted, it has to be deleted from all of the edge locations which can take an indeterminate amount of time.
The upstream fix is as good as can be done for this issue. You can try setting a very long deletion timeout, but even then it is not guaranteed.
  new aws.lambda.Function('handler', {
    role: role.arn,
    code,
    handler: 'index.handler',
    runtime: 'nodejs20.x',
  }, {
    customTimeouts: {
      delete: '30m',
    }
  });