Gentoo live build is failing

Hyprland Version
 System/Version info
Hyprland, built from branch  at commit 185a3b48814cc4a1afbf32a69792a6161c4038cd  (swipe: nuke numbered).
Date: Thu Apr 11 18:46:19 2024
Tag: v0.38.0-92-g185a3b48, commits: 4425

flags: (if any)

System Information:
System name: Linux
Node name: ExilOS
Release: 6.6.21-gentoo-exilos
Version: #3 SMP PREEMPT_DYNAMIC Mon Mar 25 22:57:40 +07 2024

GPU information:
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c1) (prog-if 00 [VGA controller])

os-release: NAME=Gentoo
ID=gentoo
PRETTY_NAME="Gentoo Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.gentoo.org/"
SUPPORT_URL="https://www.gentoo.org/support/"
BUG_REPORT_URL="https://bugs.gentoo.org/"
VERSION_ID="2.15"

plugins:

Bug or Regression?
Bug
Description
I can't emerge hyprland-9999 on Gentoo. The build is failing, logs are below
How to reproduce
try to emerge hyrpland-9999
Crash reports, logs, images, videos
https://logpaste.com/CpDKduaM

~amd64 (v0.39.1-r1) is compiling fine

outdated hyprwayland-scanner. Next time use cmake and it will tell you what's wrong.


Updated hw-latest/caliptra-rtl to d792ce264da10b5303b2e5831768fce97a78b210

One issue: uart.rs uses raw address for generic output wires, which did change address

Right now seeing two issues:
Store access fault when setting a data vault entry. Specifically WarmResetEntry48::RtTci
FMC is not logging (emulator and FPGA). ROM and RT do log.


How to schedule a one-off job that is executed immediately?

I'm having some issues trying to setup a one-off job that executes immediately.
I want to run a job on server startup.
Following the documentation, this is how I setup my job, but it never runs:
SyncedCron.add({
  name: 'Crunch some important numbers for the marketing department',
  schedule(parser) {
    // parser is a later.parse object
    return parser.recur().on(new Date()).fullDate();
  },
  job() {
    ...
  }
});

How can I debug this? What is the proper way to schedule jobs to execute immediately?
db.cronHistory.find() returns nothing
Console output:

SyncedCron: Scheduled "Crunch some important numbers for the marketing department" next run @0

@vfonic use Meteor.defer to prevent blocking


Manage kubernetes clusters on openstack

User Story

As a giant swarm customer I want to create kubernetes clusters on openstack so that I can make use of my existing openstack infrastructure.

Details, Background
When talking to new customers especially in the telecommunication industry, but also in manufacturing and retail we see a demand to manage clusters on existing openstack infrastructure. With our move to Cluster API we will be able to provide this functionality using controllers provided by the upstream community.
Blocked by / depends on
Monitor CAPI workload Clustes https://github.com/giantswarm/roadmap/issues/313
Default apps for CAPI Clusters https://github.com/giantswarm/roadmap/issues/320

Closing this as this is in progress now and and tracked in a different issue #600


Create 2016 AGU poster & lightning talk

[ ] What poster format is preferred? @bekozi normally uses Inkscape.
[ ] What is the slide count and content for the lightning talk?
[ ] How to handle printing?
[ ] How to handle printing costs?
[ ] Draft deadlines.

Happy to use whatever software... I use omnigraffle, but it's pay to play.
I don't know that we are part of the lightning talk?
I can cover printing / costs.
I'll need to get things reviewed, so lets not get too last minute, but it shouldn't be a big deal. Shoot to have things done by the end of November?

I use PowerPoint for posters, so would enjoy learning a better alternative.
Rumor has it the netCDF poster block, of which we are a part, has been granted a lightning talk session. But beyond that details are sketchy. Supposedly the sessions are two hours long and talks are about five minutes long.  First pass at slide content:

CF handles grids and some simple geometries (points, and sorta kinda profiles, trajectories, which are just series of points).
What about polygons and lines. Show watersheds with evapotranspiration, rivers with streamflow.
At this GitHub repo, we're exploring enhancements to CF to handle this.
The basic notion is....high level overview of whatever our scheme for doing this is. (I haven't synthesized the latest feedback from Jonathan yet.)
Here's how we do lines (simple example for to teach the basic notion).
Here's how we do polygons (simple example for to teach the basic notion).  I don't think we go into the details of how we handle holes and multiparts. We can show pictures on the next slide and they can talk to us or see GitHub if they really care.
Here are pictures of the 6 geometry types we handle.
We have a Python reference implementation and sample data.
We've corresponded with CF metadata and are hoping to make and official proposed update to CF by some date.
Thanks, and help us out on GitHub or with CF, or buy Dave a pizza for presenting for us.

Want to create a PPTX in an online shared folder that we can edit for the lightning talk?  Here's a slide to demonstrate line geometries that would be cool to store in netCDF.
https://utexas.box.com/s/j09lp9gsok5d5eflmjsc83mzaab8bjgk

Nice graphic. I made a presentation we can hack on Monday: https://docs.google.com/presentation/d/18-BDfXirY9rSwYX6sccEWOKmvtR7ELHNcen2NTXM8eM/edit#slide=id.p. I probably don't have the correct drive emails, so let me know.

It's actually an animation. Play the presentation to see it.  Also, we should decide if we're using PPTX, Drive, etc. for format.

Ahhh. Power Point is confounding as a Linux user. :dizzy_face:
I think we should use drive to get the content and then export and refine in @dblodgett-usgs's preferred format. Drive works well for collaboration, but there may be newer solutions out there.

👍  to using Drive for the draft then migrate it to something to shine it up.

Sounds good. The video in that slide is an AVI which I can provide separately if you want to use it. It's also on YouTube. https://www.youtube.com/watch?v=jI_wtcw5Zuk

@twhiteaker that is a very nice animation. Why did you make it?

I model streamflow in a few Texas river basins for a project funded by the Texas Commission on Environmental Quality to help watermasters determine if there is enough water to support requested water diversions. I made that video to demonstrate what I'm doing in the Brazos River Basin for a meeting with the Brazos River Authority to introduce them to our work; however, the meeting never happened due to a flood event and we haven't rescheduled.

Very nice! Looking forward to meeting Monday. I should be freed up to work on this stuff in the next couple weeks.

Posted milestones for the poster and talk on the wiki: https://github.com/bekozi/netCDF-CF-simple-geometry/wiki/AGU-2016---Poster-&-Lightning-Talk. Please modify if you like. Thanks again for meeting today. I think we have a good plan in place.

Also, let's plan on holding another telecon near the end of November.

I updated the Bull Creek example to include upstream flowline endpoints (that's what the National Water Center provides for spatial representation of National Water Model results), flowlines, and catchments. These features are all indexed by COMID, and each feature is associated with the streamflow data.  The data include an entire short range simulation, which has 15 one-hour time steps.
The updated CDL includes COMID but no geometry, and there are GeoJSON files for the three geometry types. @bekozi said on our phone call today that he could turn that into CDL following our simple geometry pattern. Let me know if I need to help with that. Otherwise, my next focus is a slide showing the Bull Creek Watershed.

@bekozi said on our phone call today that he could turn that into CDL following our simple geometry pattern.

That's correct. The GeoJSON looks well-formed from what I can tell, so we should be good to go with these. Was @dblodgett-usgs planning to provide some hydrologic data associated with these features? I can't remember. It would be nice to have something like precipitation, etc. in addition to the identifiers.
We don't have an example of multi-geometries. I think I'll collapse all features into a single multi-geometry by feature type as an additional example.

Sorry for the github spam. This is kind of the master issue, which I think we should use for general conversation leading into AGU. I made an AGU milestone just to keep things straight in my head. https://github.com/bekozi/netCDF-CF-simple-geometry/issues?q=is%3Aopen+is%3Aissue+milestone%3AAGU
Turns out I'll not be traveling the week before AGU so will have more space to help finish this stuff up.

Closing this out. We are more or less done with these, just need to finalize and print.


feat: CHAPI didconnect view updates

showing list of credentials being sent along with invitation
closes #311

Signed-off-by: sudesh.shetty<EMAIL_ADDRESS>

Would be able to add the screenshot for UI change ?

Would be able to add the screenshot for UI change ?

it is not exaclty look and feel enhancement, getting user consent while storing credentials from didconnect


Support dmacvicar/libvirt when defining multiple providers

What does this PR change?
Allow us to define multiple providers (with their aliases) and use the libvirt provider that suppports latest terraform.
This is only a temporary solution that must not be merged.
@rjmateus will come with a proper solution.

closing in favor of: https://github.com/uyuni-project/sumaform/pull/1014


User can specify release command in Procfile.

Allows the user to run arbitrary release commands (such as running Django collectstatic and/or migrations). The 'release' command runs before workers are spawned.
Kind of works like this: https://devcenter.heroku.com/articles/release-phase

Thanks for these, they're all short and to the point :)


Best approach to save data locally

When developing with meteor for the client, it implicitly uses a minimongo db on the clientside, which also stores the data in the local storage. Also this enables users to run queries (sort, filter) on those data sets.
I've been saving the data coming in currently to local HashMaps but sorting and filtering data items is really resource intensive and leads to many UI  hangs. Is there any solution or suggestion on how to save this data locally and have decent performance for getting specific subsets?
(One could of course always just subscribe to the specific published feed in every activity but there is not persistence when switching)

Thanks for your question! This is definitely an interesting topic that needs attention.
There's already something in the works that will free you from having to parse the JSON yourself and save the results every time. This is not something that should mess up your domain logic, of course. It's really something that this library should take care of and thus there will be some enhancements.
In the beginning, an in-memory database that consists of Map instances in the application's memory -- just like what you did -- will be the only solution provided. Nevertheless, the library will allow you to provide your own database class that extends or replaces the existing behaviour. That way, you could provide a database adapter that saves to and reads from SQLite.
SQLite is also the alternative that should probably be recommended for your current problems. And if the UI hangs, you probably have to move the resource intensive operations to a separate thread.
Does that help?

In regards of parsing the JSON: I'm currently using the gson library with underlying models - but that does not take into account the changing object structure of mongodb objects. Any ideas on how to tackle this?
There two issues with Maps:
a.) They can't be searched or sorted
b.) Its not too easy to use theme in a Adapter for a ListView, thus the need to copy the whole thing into a arraylist and losing any update notifications. I've used an observer pattern to counter this but it is less than ideal as the search & sort has to be done everytime the dataset changes
SQLite is not an alternative in regards to losing the notification of any updates that happen. The whole idea of DDP & Meteor is of course to let the user know as soon as possible when a change occurs anywhere in the chain. Also you would need to drop the structure and data everytime you restart the app. Plus object structure changes are a pain to keep in sync this way.
I'm not sure if we can work together to find a solution similar  to minimongo for android. Do you have the map changes on a branch somewhere? Maybe I can contribute something?

Thank you!
These things are not on a public branch yet, but I can certainly do this.
First, let's agree on the problems that really exist and on the solutions that we need, though:

Are you parsing the JSON into custom objects, "beans" or POJOs? Do you need these for structural safety and to access their member methods? Or would having all data in maps (with keys and values) help you as well? The problem is, obviously, that this library could only provide a built-in database if you can go without your custom classes and have maps only (just as in minimongo).
For searching and sorting, the plan is to mirror most of the methods that minimongo provides and then implement the search on a map of maps in this library, i.e. clone minimongo's behaviour in the best way possible. For example, if you search for a single property that should have a specified value, the library iterates over all the entries in the map and compares the properties for you.
No matter if we use the in-memory database or SQLite, that data store is only backing your collections, you don't lose any real-time capabilities. So you are still informed that an update happened to collection myColl where the document myDoc was added. If you know this, you can just query the database to get myDoc from myColl and see the up-to-date values. Does that make sense?

The source code for minimongo is available here, by the way: https://github.com/meteor/meteor/tree/devel/packages/minimongo
As you can see in this new commit, you will be able to pass any instance of a class implementing the new DataStore interface to the constructor. Then either keep that reference in your Activity or fetch it again using mMeteor.getDataStore().
That data store will automatically receive all data updates. The "only" thing that you have to implement in your data store is saving that data (to whatever location you want) and providing read access with queries and lookups.
To make this much more easy, we will provide a built-in solution that keeps all data in memory and will try to emulate as much of minimongo's behaviour as possible.
That being said, I'm sure we can make this work together :)

I'm using GSON (Checkout "Consuming http://www.javacreed.com/simple-gson-example/)  to parse the JSON object into a normal java object (POJO). It makes accessing the members simpler and also gives you type safety instead of having to reparse <String, String> maps every time you need a specific value.
That is exactly the problem though: (hash)maps are not build for iteration, search or sorting. Also this gets impractical & slow when you work on larger data sets with a couple hundred items in the maps.
Well if we do the iterate through the map and return an arraylist approach then the arraylist does not get updated when the map changes. We would need something like a observer pattern for the maps so listview adapters can get notified when the underlying data set changes. With SQLite it gets even worse, as you would need to manage update notifications to adapters separately. Plus SQLite would do a lot of work on the flashdrive/disk.

DataStore looks good - that might help to keep all classes updated but its just a first step to really tackle this issue.
I'm not sure if replicating minimongo is the best approach as it might not really work for Java, but it would definitely be nice. I would suggest though to first tackle #48, #34 and #45 to get the project better organized.

Thank you!
Sure, DataStore is only the very first step, really the foundation. The other code just hasn't been committed yet because we still need to discuss how to do this best, it seems.
Well, you're using GSON, while this library uses Jackson. They should be pretty much compatible, though. Anyway, the purpose of DataStore and the upcoming database classes is that you, as a user of this library, don't have to parse the JSON anymore. You should just receive maps in your DataStore subclass.
The fact that you're using POJOs, which is great for type safety, of course, makes this problem more difficult. We probably won't be able to provide a common database interface that uses your custom POJOs. With maps, on the other hand, this will be possible.
The implementation issues (especially search, sorting) is why I've posted the link to the minimongo source code. This might be really helpful.
You said:

(hash)maps are not build for iteration, search or sorting. Also this gets impractical & slow when you work on larger data sets with a couple hundred items in the maps.

Sure, but this is what minimongo has to do as well. I think we might understate Java's performance when iterating merely hundreds of properties in a map and doing simple string comparisons. In JavaScript, your objects are not optimized for search and sorting, either. From minimongo's README:

Internally, all documents are mapped in a single JS object from _id to the document. Besides this mapping, Minimongo doesn't implement any types of secondary indexes.

Regarding your third point:

Well if we do the iterate through the map and return an arraylist approach then the arraylist does not get updated when the map changes.

Is this really a problem? You get the update notifications in the onDataXxx(...) callbacks. Say, a field named myProp has been added to document myDoc in collection myColl. Knowing that, you just query the database to get that document as an immutable Java object that you can use to update your UI. If you need to update your adapter, update it in that callback with the new value returned from the database.
That's the plan, at least. Doesn't this make sense to you? When you get the update notifications in the onDataXxx(...) callbacks, you don't really need reactive collections or observers on the lists, right?
So the plan was not to remove the onDataXxx(...) callbacks. What may be removed in the future, but will definitely be kept for compatibility reasons for now, is the parameters of those callbacks where data is received. You don't need that if you have a database. You only need to know the document that has changed, then.
Maybe @iahvector wants to discuss these ideas as well :) We have already talked about database access. Two ideas were:

Re-using raw MongoDB queries from the Meteor client (written in JavaScript) and parsing them in this library. But maybe we will not be happy with that much inlined JavaScript code inside our Java code, without any type safety, etc. It would look like this:
mMeteor.collection("inventory").find("{ type: 'food', price: { $lt: 9.95 } }")

Implementing a query builder. To me, this seems to be the best solution. Something like this:
mMeteor.collection("inventory").equals("type", "food").lowerThan("price", 9.95).find()

Sorry for not getting back to you sooner!
Using POJOs was just for me as I know how the objects look like. But yea we will need to use maps in order to be able to support changing data object structures.
I guess I'm having my performance issues with HashMap as I still use the autopublish package in development, but that might not be an too big issue. I didn't know that minimongo does not optimize for performance on the client side - really interesting!
I'm still unsure on the whole callback thing. I don't really know what the best approach would be, but I'm open for any suggestions. The initial problem is: how does the adapter that shows a subscription or subset of data get notified if any of the objects change. Yes, we can register a callback in every adapter, but I think thats no the best approach.
In terms of API: I would prefer the  query builder as JSON in strings does not come with any IDE support.

A first draft of the integrated database is available now:
Prerequisites
dependencies {
    compile 'com.github.delight-im:Android-DDP:e4c6f4ba0c'
}

Enabling the database
Pass an instance of Database to the constructor. Right now, the only subclass provided as a built-in database is InMemoryDatabase. So the code for the constructor becomes:
mMeteor = new Meteor(this, "ws://example.meteor.com/websocket", new InMemoryDatabase());

After that change, all database entries received from the server will automatically be parsed, updated in the built-in database and managed for you. That means no more manual JSON parsing!
So whenever you receive database notifications via DdpCallback#onDataAdded, DdpCallback#onDataChanged or DdpCallback#onDataRemoved, the data has already been updated in the database and can be retrieved from there.
Accessing the database
Database database = mMeteor.getDatabase();

Operations
On the database
// String collectionName = "myCollection";
Collection collection = mMeteor.getDatabase().getCollection(collectionName);

String[] collectionNames = mMeteor.getDatabase().getCollectionNames();

int numCollections = mMeteor.getDatabase().count();

On collections
// String documentId = "wjQvNQ6sGjzLMDyiJ";
Document document = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId);

String[] documentIds = mMeteor.getDatabase().getCollection(collectionName).getDocumentIds();

int numDocuments = mMeteor.getDatabase().getCollection(collectionName).count();

On collections (with the chainable query builder)
Any of the following method calls can be combined to select documents via complex queries:
// String fieldName = "age";
// int fieldValue = 62;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereEqual(fieldName, fieldValue);

// String fieldName = "active";
// int fieldValue = false;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNotEqual(fieldName, fieldValue);

// String fieldName = "accountBalance";
// float fieldValue = 100000.00f;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereLessThan(fieldName, fieldValue);

// String fieldName = "numChildren";
// long fieldValue = 3L;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereLessThanOrEqual(fieldName, fieldValue);

// String fieldName = "revenue";
// double fieldValue = 0.00;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereGreaterThan(fieldName, fieldValue);

// String fieldName = "age";
// int fieldValue = 21;
Query query = mMeteor.getDatabase().getCollection(collectionName).whereGreaterThanOrEqual(fieldName, fieldValue);

// String fieldName = "address";
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNull(fieldName);

// String fieldName = "modifiedAt";
Query query = mMeteor.getDatabase().getCollection(collectionName).whereNotNull(fieldName);

Query query = mMeteor.getDatabase().getCollection(collectionName).find();

// int limit = 30;
Query query = mMeteor.getDatabase().getCollection(collectionName).find(limit);

// int limit = 30;
// int offset = 5;
Query query = mMeteor.getDatabase().getCollection(collectionName).find(limit, offset);

Query query = mMeteor.getDatabase().getCollection(collectionName).findOne();

Chained together, these calls may look as follows, for example:
Document document = mMeteor.getDatabase().getCollection("users").whereNotNull("lastLoginAt").whereGreaterThan("level", 3).findOne();

On documents
// String fieldName = "age";
Object field = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).getField(fieldName);

String[] fieldNames = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).getFieldNames();

int numFields = mMeteor.getDatabase().getCollection(collectionName).getDocument(documentId).count();

For sort the collection is there anything like?
Query query = mMeteor.getDatabase().getCollection(collectionName).sort(field).find(limit);
Thanks!

@romaluca Unfortunately, this is not available, yet. But exactly that syntax is planned for this feature.
We first wanted to know if the database access works in general. If it does, sorting will probably be the first new feature to be added.
In the meantime, you should be able to sort entries with the Arrays.sort(T[], java.util.Comparator) method. Can you try this?

Hi all,
Sorry for very late reply. I was very busy lately and didn't notice the notifications.
@kordianbruck My solution to this was creating a SQLite table for each of my collections and a content provider for the database. In each activity/fragment, I use a CursorLoader to subscribe to changes in the db and display the changes reactively. In the DDP callbacks, I parse the json and add/update records in the db accordingly and notify the content provider with change. The problem with this is that it's very tedious and you have to repeat it for every app.
@mwaclawek great work on the data store. I'll try to test it as soon as I have time. Isn't there any existing NoSQL db or key-value store for Android that can be used instead of the in memory store for more efficiency and maybe built in query builder?

@iahvector how do you handle schema/object structure changes with SQLite? I imagine it might be really complicated at some stages to hande this...

I don't. You'll have to update your schema in an application update, but I think you'll have to do this with any solution so I don't this should be considered a problem (except for the amount of work required for the change).

@iahvector not with the HashMaps that @mwaclawek implemented. Those are absolutely dynamic and don't care if a property is added or missing from a object...

You won't need to update the schema, as there isn't any, but you'll have to update your code and make an app update.

@mwaclawek it works!
The best would be have (sort and limit) but for now i used this:
Document[] docs = mApplication.meteor.getDatabase().getCollection("comments")
                    .whereEqual("photoId", photo.getId()).find();
            Arrays.sort(docs, new Comparator<Document>() {
                @Override
                public int compare(Document o1, Document o2) {
                    return Utility.getDateMap(o1.getField("createdAt"))
                            .compareTo(Utility.getDateMap(o2.getField("createdAt")));
                }
            });

            for (int i = 0; i < (docs.length > limit - 1 ? limit - 1 : docs.length); i++) {
                adapterComments.add(new Comment(docs[i]));
            }

Do you have any suggests for do something less weight?
For now i get the document's array and i put every element in a list of my objects (in this case i used  Comment). I use this list for adapter in recyclerview Thanks!

@iahvector and @kordianbruck I didn't find any good existing solution for the data store. Maybe I've missed some. But anyway, I hope the in-memory database is working for now, as a first step. Maybe you can try it when you find some time. Apart from that, I'm open to other solutions that could probably integrated into the new structure of interfaces as well. We could have both the new InMemoryDatabase and some potential SqliteDatabase extend the Database interface. But we can't use SQLite if that means each developer has to maintain their schema in a separate file. So schema-less is probably what we have to go with.
@romaluca That's great! Is that really working in that form? That would be perfect :) For now, isn't that a good first step? It should hopefully be less code than you would have needed without the built-in database. And if we can soon replace those 7 lines for sorting with a simple sort("createdAt") call, won't that be sufficient? The limit is already there, by the way: Just pass the desired maximum number of entries to the find method.

Thanks! it's a great step! i didn't see the limit :)

@romaluca Maybe we should remove the parameter(s) from the find method and instead add two methods limit and offset, as you suggested. I just thought it would make more sense to have these as parameters to the find method since there's also the findOne method. And findOne wouldn't make any sense if you had set a limit or offset before. But if the parameters are hard to discover, it's not a good solution, either.

the method with parameter is ok the only thing is rename the parameters of sign, because now is:
find(int i)
find(int i, int i1)

and i didn't understand that "i" was "limit" :)

@romaluca Oh, sorry for that! The parameter names were already limit and offset in the source code, of course. But apparently, reasonable parameter names and Javadoc were missing everywhere. The build process had to be fixed for that.
Could everybody please update their dependency to the following?
compile 'com.github.delight-im:Android-DDP:v3.1.0'
Please try and see if it's better then. Thanks for spotting this!

Thanks! tonight i'll try it!

Closing this issue since database access is now available in the latest releases.
The current implementation is not perfect (yet), of course, but I'm sure we can improve it over time so that it fits everyone's needs. And if it doesn't work for you due to performance issues, you can implement the various interfaces, mainly DataStore and Database, to store the data somewhere else, e.g. in a SQLite database, instead of in memory.
Another way to improve performance (and prevent a freezing UI) may be to parse, store and load data from memory in separate threads, not on the main thread.
Whenever you have any questions about the database access, bug reports or feature requests, please feel free to open a new issue :)
Thanks for all your help!


Baloo file indexer runs at 100% CPU

Describe the bug
The Baloo file indexer in KDE is using all my system resources. My CPU runs at 100%, and my fan is running at top speed. My laptop is never like this, unless it's compiling something. This doesn't seem like ordinary behavior, and it's been going on for quite some time.
To Reproduce
Steps to reproduce the behavior:

Have lots of files
Run KDE
Notice that your computer is about to die from overheating, since it's been running at 100% CPU for hours.

Expected behavior
A clear and concise description of what you expected to happen.
A file indexer wouldn't run this hot.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 5.4.21, NixOS, 20.09pre214537.39892985b00 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(jon): "home-manager, home-manager-sway, nixpkgs-20.09pre214168.686274ea62c"
channels(root): "nixos-20.09pre214537.39892985b00"
nixpkgs: /home/jon/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

It's possible it's trying to index the /nix or /tmp directories. I thought that was turned off by defadult though.

It's possible it's trying to index the /nix or /tmp directories.

Or maybe your /home is that big :3

Seems to still be an issue, at least in my case where I enabled syncthing to sync with someone that has lots of files.
Took a while to figure out what was locking up my system since my system kept locking up. :(


Update amazon.py

Exception Handling: The code currently catches broad requests. exceptions.RequestException. It's better to catch more specific exceptions like requests. exceptions.HTTPError for HTTP errors.

User-Agent String: You might want to replace the placeholder "Your User Agent Here" with a valid user-agent string. You can find user-agent strings online or use the one from your browser's network requests.

Function Parameters: Instead of hardcoding the product URL inside the script, you can modify the 'check_amazon_availability' function to accept the URL as a parameter. This makes the function more flexible.

Type of change

[ ] Added new project
[ ] Bug fix
[ ] New features
[ ] Enhanced documentation

Changes proposed in this pull request

Project name :

Short description :

Checklist

[ ] The code is Python 3 compatible
[ ] I have added relevant comments in my file to make code understandable
[ ] I have added my project in a folder which includes all the necessary files

Thanks for your changes ⭐


Item exporter duplication/voiding bug

Duplication:
https://user-images.githubusercontent.com/49848633/173829238-fc1f225a-9733-4909-840a-72e1eeb54dd8.mp4
Voiding:
https://user-images.githubusercontent.com/49848633/173829841-0912521a-6a69-4008-8625-f151784ca216.mp4
Reproduction steps:
Voiding:
-set up a system with a digital terminal and an exporter pointing to a chest
-put two stacks of 64 items into the system
-put in another, non-64 stack
-set the exporter to export the items you just put in
-the chest should only have one 64 stack and the non-64 stack, deleting the second 64 stack
Duplicating:
-put a 64 stack of an item into the system
-put multiple non-64 stacks into the system
-set the exporter to export the item you just put in
-every non-64 stack should have turned into a 64-stack in the chest, except the last one

Both fixed.


New skin and some new features

New skin, color schemes, timestamp and last message in conv list, presence status, material icons font, roboto font, new (temporary ?) icon, and some more fixes and improvements.
https://github.com/yakyak/yakyak/issues/147 https://github.com/yakyak/yakyak/issues/155 https://github.com/yakyak/yakyak/issues/103 https://github.com/yakyak/yakyak/issues/152 https://github.com/yakyak/yakyak/issues/137 https://github.com/yakyak/yakyak/issues/21 https://github.com/yakyak/yakyak/pull/156
see: https://github.com/ariu/yakyak/releases

wow. tons of stuff here :+1: can we perhaps just rebase off master?

hm. ok. perhaps you clash because of the theme switch i merged #146 . can your work be made to work in tandem with that?

I have implemented color themes too, but in a slightly different way. It would be complicated to get @mrohr system, because I changed some html for my skin, (removed elements, added new ones, ...) and I have a slightly different approach for color variables. I think mine is less complex and easier to use.
While @mrohr uses less variables and mixins, and generate css theme files, I use css variables instead ( https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_variables ) available in chrome 49, to define colors for the whole document on  root element. If I want te create a new color theme, I just add a new class to  element and override css variables I want to override. I can, with this class and css cascade system, override a specific element color too. And that's all, only some css magic. No less mixins, no new css file. See this less file.
In yakyak menu, I simply add / remove css classes when switching from a theme color to another. see here , here , and here.
I tried to create a dark theme using @mrohr colors from his theme, and added a new commit with it. We can still tweak it, maybe @mrohr will do it? :)
Since I changed a lot or stuff, I'm suggesting revert to https://github.com/yakyak/yakyak/commit/9c678ebfbd35dbe013772d41f9feda7c93123ace , merge this pull, then update icon, deps, and other stuff you did.
vanilla yakyak light theme:

vanilla yakyak dark theme from https://github.com/yakyak/yakyak/pull/146 :

new skin yakyak default theme:

new skin yakyak dark theme:

Okay. I have backed out @mrohr changes, so perhaps you can rebase off master now? A couple of things regarding your changes:

your css variable names should change so that they describe function instead of colour. i.e. instead of --gray it should be --panelbackground.
regarding your new default designs a couple of thoughts

we've deliberately distanced ourselves from google's styles, since we don't know whether a reversed engineered chat protocol would sit well. taking on their brand identity as default is not a great idea.
google's brand identity sucks :) ... the design philosophy of yakyak is more in line with apple's messages. particularly in your changes i would ask myself "what does the top bar do?" and my biggest bug bear "why does it need to say Conversations" always at the top?

about google's "brand identity":

I wouldn't call material design a brand identity. It's more like a ui framework, that they've made with the hopes that it will be used by others, so I don't see "taking" it as an issue
as far as the top bar, you're right, but this is mostly because google's and apple's designs kind of clash. If you want to keep the material themes as options, I'd recommend doing away with one of the bars. Either the material one, or the os x one. (maybe use something like https://github.com/kapetan/titlebar to add the window controls to the material bar)

@algesten
I did rebase / merge from current yakyak master: https://github.com/ariu/yakyak/commits/master

I see your point. Mine was instead: I want to replace all green in page, regardless of what element it is. For exemple, all default green as to go blue. So I change green variable to blue, and voila, every green element becomes blue. Perhaps, we could have general variables, and specific variables that make use of general variables like bootstrap does.
exemple:
// general
--blue: #0000FF;
// specific
--topbarbackground: var(--blue);
--panelbackground: var(--blue);
etc...

So we could change general colors, or tweak individual ones. What do you think?

I'm not an art guy, I'm having hard times choosing one color over another, or wether this or that should be square or rounded... :) . My work is based on @austin-guevara work. See his mockup here. It can (and must) be adjusted, improved, and we should discuss and share ! I will be happy to implement any great and popular idea. UI should be a forever work in progress, and everyone can bring exciting new ideas. I could make it look more apple messages like, we just need someone to draw it, improve it, and I could implement it. As I said, I'm not good at drawing things, I just took someone else design ideas !
As for the top Bar, well, for conv list, it's just a placeholder for now. We could have a search input here later (like in apple messages, or in @austin-guevara mockup), and / or access to general application settings, etc... On the main panel, it reminds current conversation name, and gives access to conversation details and settings. We can make it transparent with blur like apple messages, or add informations / actions, etc...

@matthewdias

I agree with you. material design are only guidelines that we are free to use, adapt, etc... https://www.google.com/design/spec/material-design/introduction.html#introduction-goals

I wanted to get rid of osx bar in the first place, and add close / minimize / fullscreen to the top bar. But yakyak is cross platform, and I do not have any windows or linux platform to test it, as we should still bring native platform feeling to those window controls I think. But its high on my list of things to try !

I tried your branch, but it seems to have some issues.

warnings for woff2. and then errors whenever i try to switch conversation

if you look at the pull request I had submitted (no hard feelings about reverting!), I ended up abstracting out what constituted a 'theme' into 10~ variables that were much more generic than topbarbackground or panelbackground.  Maybe a middle ground like my previous work had could be the answer?
P.S. css vars are pretty cool, hadn't seen them in use before.

@mrohr There is no topbarbackground or panel background for now, just very generic variables like you had (see here). But names are not that good, and we could do really more, and maybe a middle ground as you suggested. Please feel free add some change :)
@algesten Will look into it as soon as possible. I already saw the woff2 problem, looks like trifl library is causing this, dont know why yet.

@ariu It's really sad to see your amazing work hasn't been adapted to the main project.

@austin-guevara Yes I know, I've been very busy (new exciting job, family stuff...) and didn't find the time to solve the merge conflicts, and work on this. But i'm still around, and I hope I will fix this soon enough ;)

@arnriu users want this badly. Just saying.

I have checked out this branch and merged-in updates from master (rebasing would have been a nightmare due to mrohr branch being merged and reverted in master)

. I played around a bit.
Updating the branch with master was easy but the way i see it (if i did nothing too wrong) the work is not finished. While some UI things are more appealing some functionalities are missing. I don't see the "controls" bar at the bottom of the user list therefore there is no functionality for muting/closing/starring conversations. Some styles in the conversation are a bit wrong even it some other things are very cool. "Show conversation thumbnails" is broken too. I attach a screenshot here

Here are my thoughts

I think material design does not look too good on desktop because lots of space is wasted.
The previous theme bent really well with osx and did not look too-bad elsewhere. It's a bit sad for me to loose the osx "integration" feeling.
In the list of "contacts" i find "timestamp" and "last message" cool at first, but then useless and caotic. Conversation are already sorted by timestamp and i think it's enough
I love how the user icons bend into the message bubble, expecially when the bubble is more than one line long
I love that conversation actions have been moved inside the conversation
I hate the big header below the window titlebar.  I don't have a better solution but I could try to make it smaller at first
I am not sure how i feel about "contact list" group headers with gray background and centered text alignment
I like how the selected conversation looks in the "contact list" but not how the 'scrollbar' space cuts it out. It actually cuts the entyre contact list. Maybe it should float over it
Looks like noto font fixes problems we had with emoticons. It seems to me they look pretty neat

Of course these are just my first thought and i am open to other ideas.
I am not sure how to go forward from this PR. Maybe i should push a separate branch to work on then merge it to master once it's ready

So @davibe did you successfully merge ? It would be nice, cause I have no time to rebase, it is hard as you said, lot of things changed.
Original skin discussion is here: https://github.com/yakyak/yakyak/issues/147
I agree with most of your thoughts:

The previous theme bent really well with osx and did not look too-bad elsewhere. It's a bit sad for me to loose the osx "integration" feeling.

Yeah, but then, what about windows or linux users. Maybe we could have light custom styles for specific os?

In the list of "contacts" i find "timestamp" and "last message" cool at first, but then useless and caotic. Conversations are already sorted by timestamp and i think it's enough

Maybe we could add this as an option, and toggle it form menu? Like user icons in contact list.

 Maybe we could try metling them together, at least on osx, like this https://github.com/electron/electron/blob/master/docs/api/frameless-window.md

Yeah, I already tried it, and it looks pretty nice on mac os. And solves the "big header" feeling. But I had no linux / windows to test so I dropped it for now. But It sure is on my list when i'll have some time for yak yak :)

I like how the selected conversation looks in the "contact list" but not how the 'scrollbar' space cuts it out. It actually cuts the entyre contact list. Maybe it should float over it

It was like this at some point, but I changed it to what it is now. I can't remember why I did this...
Don't know either what we should do about the PR. For me, if your merge is successfull, its stable right now, and ready to use. I still plan to work on it later on though. There are many improvements to do. Well it's UI / UX, there is always something to improve :)
As for separate branch, I don't know, but we should definitely not wait so long before rebase next time ^^'

@ariu or @arnriu in your commit "svg logo" you have delete deploy.sh
Why ?

It seems to me we're also missing

glup scripts to copy fonts over to the installed app/
a way to autogenerate the icon.icns for the new icon.

Anyway. I have updated a few things on the 'ariu-master' branch of yakyak. @arnriu check them out if you have time :)

@ariu or? @arnriu : I would like to add you as a contributor on the readme when i release this. Do you agree ? Which account should I link ?

Hey @davibe , I'll check your updates later today when I have time. Your screenshot looks pretty good :)
If I deleted files, it was a mistake. I'm a front-end web developer, and this was my first steps with electron. I'm not sure what I did with deploy or icons. As for gulp, well, I do not remember why I changed this task.
You sure can add me as a contributor. You can use @arnriu , I will use this account now. Maybe you could ask @austin-guevara too ? He did the design that inspired this PR https://github.com/yakyak/yakyak/issues/147#issuecomment-195805583 , and took part in most discussions about this. Graphics and UI design is half the job in my opinion, and I don't want to take credits for his good contribution.

Well @austin-guevara I'll add you too, if you have something against it just tell me. I think i will do v1.3.0

Huge props to everyone involved. Thank you for you dedication to making this client better for everyone! I'd certainly like to step up my developer game soon, but I'm so happy I was able to contribute.

@davibe I've made some minor adjustments over yours, how should I upload them?

@arnriu i merged into master! I am about to release 1.3.0
Rebase on master and submit another pull request!

Done :)

I am not sure about the aaa you made darkgray. I need to try it out. When i put #aaa i was trying to give less importance to the timestamp because it's indeed less important than compared to the conversation name. I felt that gray-ing it out made things less caotic. Anyway i will merge this and think about it.
Thank you !

@davibe Yeah, i saw your point, that's why i didn't revert to --lightblack (#455a64) but --darkgrey instead.  #777 is not #aaa I know, but it's still more grayer than before ! My whole points is to have any colors in variables so it's easy for anyone to create a color scheme, and I want to keep as less different colors as possible to make it easy and simple That's why I didn't add a new one for #aaa . If you feel #aaa is better, feel free to add it, but add a new variable for it. ;)

i saw it, indeed i removed my comment but you were too fast :P

I haven't experienced any problems but shouldn't woff2 files be added to the paths of fonts?
I find a constant error in the inspector about this. This seems to fix it though: averissimo/yakyak@da405f9

You're probably right


First run users should get a popup that explains what the program does

What the title says. Especially about downloading models.

Quick mock-up. Something like this?

Could be made a bit interactive, e.g. update the screenshot with arrows when you hover over each of the steps.
I'm a bit worried people will try to interact with the screenshot. Maybe it's technically possible to temporarily draw the main window inside that dialog while the dialog is open (and make it stand-alone as soon as you click "Close") but that also feels gimmicky. Maybe it works better without a screenshot.

Hmm... I have a couple of problems with the screenshot, but I am not sure I can propose a meaningful solution.

The screenshot may work very differently from your platform's appearance.
Inevitably as you said, someone will try to interact with it, and be disappointed.

I was just thinking of a simple Dialog option such with things such as. "Go to the drop down menu to select/download translation models, go to the settings to increase/decrease the font size and to configure advanced translator settings."
This is not a very good tutorial, but may do what is necessary. I find the interface self explanatory, but a few people asked for pointers ;/
The ideal solution would be a guided, interactive wizard that expected the user to click in a few places. eg "Click the download models drop down menu" and the drop down menu is highlighted at the same time.

The other option I had in mind was something like https://introjs.com. I personally hate these, but they do guide the user quite well. And since it uses the actual application, no issues with screenshots.
There might be a qt library made by someone to implement such a tour. I don't think it's too difficult to implement ourselves, but it will be a bit more involved than just popup dialog.

Yeah I like that bit, but unsure of how difficult it is, and what tools we have for implementing it.

@kpu do you mean we should ask the user on first time start up what the "Download models…" option should do? (I.e. show the list or open a website.) And second, should we after that choice immediately do that?
Very bad mock-up (problem is I wanted to make the preferred option the biggest one instead of just "yes")

As far as model distribution is concerned, we could (later on) make an installer for windows and mac that ships with compressed models and the user chooses which ones they want at that steps. I had a few win users complain to me that there is no installer.

We can probably shorten that text.
Paging @ChrisBurnsOneOne

Some thoughts :
-I don't think "models" is very meaningful for the average user who'll end up using this. I would refer to them as something else, even if it's simplistic like "dictionaries" or "libraries". It won't convey the complexity of what's going on, but users are unlikely to care about that so long as it does what it's supposed to do.
-"translateLocally needs to download a library for each language it translates. translateLocally can download these libraries automatically, or you can do this yourself. Do you want to :
                                                      <dialogue boxes>

There's an adjunct issue if the libraries are ever updated, as this will need to be explained to the user since the crux of the app is that it doesn't communicate externally to accomplish the translations.

Technically all three OS-s have mime type handling, it's not too difficult to implement that.

We should really make progress on this one in the release.  There are business decision makers trying it once or twice.

If we distributed a zip file containing the exe + a number of models in the same directory, the app will detect them and avoid the ugly message.

Shipping models would also put more emphasis on "no cloud necessary!" not even for getting started.
Model sizes: https://gist.github.com/jelmervdl/1a48816e4c3643ff5d9e1fd6821bc499
Shipping all tiny models would add another 150mb to the package, which might be a bit much, compared to the current release sizes:
10.27MB	https://translatelocally.com/release/translateLocally-v0.0.2+be52de5-Ubuntu-20.04.avx.deb
82.39MB	https://translatelocally.com/release/translateLocally.avx.exe
38.56MB	https://translatelocally.com/release/translateLocally.avx.dmg

Additionally, we'll need to figure out how to ship these additional files. I.e. on Windows, do we now need an installer? Or do we just distribute a zip and hope that people will figure it out? On Mac, do we ship the models inside the application bundle? And if so, would it pick them up correctly? Linux… where does the package write the models to and will the binary be able to detect them there.
I remember recalling we already had a plan to ship a batteries-included version, so figuring all of that out might need doing anyway to make that version. And while this issue of the intro popup isn't released yet, we could opt for only distributing that batteries-included edition.

Oh! I see what @XapaJIaMnu is getting at.
For demo purposes, being able to point to a Windows zip file with the de-en & en-de models included would make sense and would be an easy "fix" I suppose.

Yeah, the model searching code first checks all the current subdirectories for marian configuraiton files and then also checks the system configuration directory. No need to even manually import.

Unless this is for a completely managed demonstration, you need an installer. There are some related issues; a recognisable icon and even a loading screen for 3-5 seconds (which doesn't get in the way of actually doing translation) will help reinforce what it is and does.

Are we happy with the current popup for first run? I demo'ed to two users and they figured it out quite fast.

I'd need a compiled Windows version to take a look. Can be emailed at my Edinburgh address if that helps.

https://github.com/XapaJIaMnu/translateLocally/releases then click on "Assets"

I see the message now; it looks suitable.
Ran into an adjunct issue, however - on a Windows PC that's run earlier versions (installed doesn't seem to be the right word, as there's nothing to uninstall in the control panel), I don't actually get the message popup - TranslateLocally just opens. I had to switch to a different PC (Windows 11) which has never run TranslateLocally to see the popup.

@ChrisBurnsOneOne, translateLocally checks if the configuration directory is present, which gets built after first run for a given user. You are right though, we don't currently have an uninstaller.


Fixes windows build

Another attempt to fix the most recent bugs in the CI for Windows.

Changes in this PR:

Using windows-2019 instead of windows-2022 (windows-latest): In windows-2022, the GCC compiler gives an error 0xc0000139, which means "missing library". I couldn't figure out what is the exact problem there. I have also tried to use clang on windows-2022, but it gives me an incompatibility error with a non-standard header installed on windows.
Do not test libquadmath on Windows: the function quadmath_snprintf() seems to have a bug or it does not exist. I don't know for sure.


Please do not recommend installing nvm with homebrew

Per http://facebook.github.io/react-native/docs/getting-started.html#requirements - "Homebrew is the recommended way to install nvm" this is not the case. I'm the maintainer of nvm, and I do not in any way support or recommend installing nvm with homebrew. (See https://github.com/creationix/nvm/issues/850#issuecomment-143236495 for some background)
Please either:

use the curl command in the readme on http://nvm.sh to install nvm, which is currently the sole recommended way to install it.
or
change the documentation to indicate that Facebook recommends it but nvm does not, so that a support burden is not created for me by users who expect that brew install nvm should work properly.

Thanks!

I'll update this since I added the nvm mention in the first place (previously it suggested installing Node via brew but nvm is a winner in my eyes - so thanks for that).

Thanks, much obliged!


NewObservedGenFailure will pop up once upgrading the images of serving progressive rollout

Function-wise, it won't bring any blocker, but this status can show up in the CR status of RO.
 - lastTransitionTime: "2024-05-23T02:05:46Z"
    message: unsuccessfully observed a new generation
    reason: NewObservedGenFailure
    status: Unknown
    type: Ready

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: autoscale-go
  namespace: default
spec:
  template:
    metadata:
      annotations:
        # Knative concurrency-based autoscaling (default).
        autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
        autoscaling.knative.dev/metric: concurrency
        # Target 10 requests in-flight per pod.
        autoscaling.knative.dev/target: "10"
        # Disable scale to zero with a min scale of 1.
        autoscaling.knative.dev/min-scale: "1"
        #autoscaling.knative.dev/max-scale: "5"
        rollout.knative.dev/progressive-rollout-enabled: "true"
        #rollout.knative.dev/progressive-rollout-strategy: "availability"
        rollout.knative.dev/progressive-rollout-strategy: "resourceUtil"
    spec:
      containers:
        - image: ghcr.io/knative/autoscale-go:latest

then
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: autoscale-go
  namespace: default
spec:
  template:
    metadata:
      annotations:
        # Knative concurrency-based autoscaling (default).
        autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
        autoscaling.knative.dev/metric: concurrency
        # Target 10 requests in-flight per pod.
        autoscaling.knative.dev/target: "1"
        # Disable scale to zero with a min scale of 1.
        autoscaling.knative.dev/min-scale: "1"
        # Limit scaling to 100 pods.
        autoscaling.knative.dev/max-scale: "6"
        rollout.knative.dev/progressive-rollout-enabled: "true"
        #rollout.knative.dev/progressive-rollout-strategy: "availability"
        rollout.knative.dev/progressive-rollout-strategy: "resourceUtil"
    spec:
      containers:
        #- image: artprod.dev.bloomberg.com/ds/shou73/autoscale-go:latest
        - image: ghcr.io/knative/autoscale-go:latest1

then remove the ro and let it recreate the ro.
The status will be marked NewObservedGenFailure.
This is one way to recreate. There are other ways, but not convenient at all.

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: autoscale-go
  namespace: default
spec:
  template:
    metadata:
      annotations:
        # Knative concurrency-based autoscaling (default).
        autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
        autoscaling.knative.dev/metric: concurrency
        # Target 10 requests in-flight per pod.
        autoscaling.knative.dev/target: "10"
        # Disable scale to zero with a min scale of 1.
        autoscaling.knative.dev/min-scale: "1"
        #autoscaling.knative.dev/max-scale: "5"
        rollout.knative.dev/progressive-rollout-enabled: "true"
        #rollout.knative.dev/progressive-rollout-strategy: "availability"
        rollout.knative.dev/progressive-rollout-strategy: "resourceUtil"
    spec:
      containers:
        - image: ghcr.io/knative/autoscale-go:latest

then
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: autoscale-go
  namespace: default
spec:
  template:
    metadata:
      annotations:
        # Knative concurrency-based autoscaling (default).
        autoscaling.knative.dev/class: kpa.autoscaling.knative.dev
        autoscaling.knative.dev/metric: concurrency
        # Target 10 requests in-flight per pod.
        autoscaling.knative.dev/target: "1"
        # Disable scale to zero with a min scale of 1.
        autoscaling.knative.dev/min-scale: "1"
        # Limit scaling to 100 pods.
        autoscaling.knative.dev/max-scale: "6"
        rollout.knative.dev/progressive-rollout-enabled: "true"
        #rollout.knative.dev/progressive-rollout-strategy: "availability"
        rollout.knative.dev/progressive-rollout-strategy: "resourceUtil"
    spec:
      containers:
        #- image: artprod.dev.bloomberg.com/ds/shou73/autoscale-go:latest
        - image: ghcr.io/knative/autoscale-go:latest1

then remove the ro and let it recreate the ro.
The status will be marked NewObservedGenFailure.
This is one way to recreate. There are other ways, but not convenient at all.

The reconcile loop should update the status of the CR, no matter it really has any changes on the status.


Add more topic labels (was: [Nix-dev] Skillset labels)

Moved from the mailing list (http://lists.science.uu.nl/pipermail/nix-dev/2016-July/021181.html).
The original proposal was to add skill labels, however, I find they are mostly covered by 6.topic: labels. Currently, we have next labels:

closure-size
darwin
emacs
erlang
gnome3
golang
grsecurity
haskell
hygiene
kernel
nixos
non-nixos
policy discussion
printing
python
qt/kde
reproducible builds
ruby
rust
usability
user experience
vim

Out of those proposed on ML, next are not covered:

shell
javascript
erlang
c/c++
build toolchain
systemd
containers
virtualization
nixos tests
module system
java
tex
perl
cross-compilation

Questions I have are:

should we add a separate skill label?
any other labels to add?

/cc @wmertens @Profpatsch @danbst @matthiasbeyer

I wouldn't mind renaming all topic labels to skill, to make things more obvious.

/participate

Suggestions for new topic labels off the top of my head: ocaml, graphics (or some variation thereof), games (or some variation thereof), typesetting (potentially subsumed by tex), fonts.
Also, the Review, Done, Backlog, and Working labels seem to be virtually unused --- can they be pruned?

@joachifm 0 - Backlog is just an indicator for the label category.

We should clarify what "needs: feedback" means and maybe split it into two separate labels to distinguish whether feedback from maintainer or reporter is needed.

I think feedback from reporter was meant originally. That's a typical bug tag, called e.g. "moreinfo" or "needinfo". Creating some reference like https://www.debian.org/Bugs/Developer would help.

Since I've been applying labels like a madman, I've noticed a few things:

What is the difference between "Usability" and "User experience"?
We need "needs: Investigation" and "needs: Maintainer feedback"
I would keep "topic" instead of turning them into "skill"
Labeling "good first bug" more often may invite more contributions, we have been bad at using that label :)
Some labels are PR-specific, some are issue-specific; not sure how you could mark them as such

Can we rename "needs: feedback" to "needs: reporter-feedback" then?

Renamed and added "needs: community feedback". Some probably have the wrong of those two, so we at least can switch.

:D

"usability" had fewer tickets than "user experience", so I replaced the former by the latter (by hand).

I see no "needs: investigation".

Because we need that!

I see; maybe we do. We also have various tiny issues that would take disproportionately lots of work to fix and thus noone wants to do it, but I don't see how a label could help it.

Are there any updates on this issue, please

Is this still a good idea?
If yes, we should make an RFC - if no, we can close.
I'm OK to close, not sure any more if these extra skill labels will make any difference in participation and managing the labels takes extra time and knowledge


gitleaks: init at 7.2.0

Motivation for this change
Scan git repos (or files) for secrets.
https://github.com/zricethezav/gitleaks
Related to #81418
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110015 run on x86_64-linux 1

1 package built:

gitleaks

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110015 run on x86_64-linux 1

1 package built:

gitleaks


1.17.1 Proposal

Just a heads up that I'm planning a 1.17.1 release for tomorrow to fix a suspected Windows regression.
UPDATE: This will be 1.18.0.

You're the releaser so you get to make the call but I would have reverted the uv_os_getpid() commit, do a 1.17.1 release with the bug fix, unrevert and then roll out 1.18.0.

Yea, I landed the uv_os_getpid() just before cutting the release and the thought crossed my mind to wait until after the release to land it. Looking back, I probably should have done that, as the only commits that were staged were the revert, a doc change, and a compiler warning fix.


TypeError: context.getScope is not a function

I am already using the latest version of this plugin but it is not yet compatible with the latest version of eslint (9.6.0). So I have to use the workaround for the plugin to work.
Raising this here because it says to do so in the eslint docs: https://eslint.org/docs/latest/use/troubleshooting/v9-rule-api-changes

This plugin is not compatible yet with eslint v9, which means you can't upgrade yet, as the peer dep warnings should have told you when you tried to install them. Stick with v8 until this plugin supports v9.
Duplicate of #2948.


MINOR: Implement ApiError#equals and hashCode

ok to test

ok to test

retest this please

test failures are unrelated flakes


bad argument #2 to 'blend' (no value)

Error: EError running notification service: ...opt/nvim-notify/lua/notify/service/buffer/highlights.lua:59: bad argument #2 to 'blend' (no value)
the highlight used for notify because normal is none for me
cmd("autocmd ColorScheme * highlight NotifyBG guibg=#3d3d3d guifg=#3e4451")

code in context
function Make:Report(msg)
    vim.cmd [[packadd nvim-notify]]
    local opt = {
        title = "Neomake"
    }
    local info = vim.g.neomake_hook_context.jobinfo
    local notify = require("notify")
    notify.setup(
        {
            -- Animation style (see below for details)
            stages = "fade",
            -- Default timeout for notifications
            timeout = 3000,
            -- For stages that change opacity this is treated as the highlight behind the window
            background_colour = "NotifyBG",
            -- Icons for the different levels
            icons = {
                ERROR = "",
                WARN = "",
                INFO = "",
                DEBUG = "",
                TRACE = "✎"
            }
        }
    )
    if info.exit_code == 0 then
        notify("Job Finished Successfully", _, opt)
    elseif info.exit_code == 1 then
        notify("Job Failed", "error", opt)
    else
        notify("Job Started", "log", opt)
    end
end

This should be solved by #19, please try the latest commit

can confirm works now thanks


Extract grafana, loki and prometheus to a dedicated namespace\chart in k8s instance

Probably, neo4j can be also extract to a separate namespace

Automated version upgrades suggested by Renovate, such as #2143, may break compatibility.
For each single version increment, such as the Loki Helm chart, one should not only review what has changed in the Helm chart between versions 4.4.2 and 4.10.0, but also what changed in the underlying application (Loki) between versions.
To ease testing, we could introduce two namespaces (such as save-cloud-grafana and save-cloud-grafana-uat), and switch our save-cloud services/pods to target either of the above, before the upgraded Grafana/Loki/Prometheus versions get propagated into the save-cloud-grafana k8s namespace.


Test: SCM - History Item Reference picker

Refs: https://github.com/microsoft/vscode/issues/227213

[x] anyOS @bhavyaus
[x] anyOS @alexr00

Complexity: 5
Create Issue

This milestone we have added a new history item reference picker to the "Source Control Graph" view.
Prerequisites

Download and install the latest VS Code Insiders release
The scm.graph.badges setting is set to filter

Auto

Launch VS Code Insiders
Open a folder/workspace that contains a git repository
Open the "Source Control Graph" view

Confirm that the history item reference picker is set to "Auto"
Confirm that the graph shown a badge for the current/remote/base (optional) history item references

Use the Checkout command from the status bar to switch between branches

Confirm that the graph is being updated correctly

Use the Checkout command from the status bar to checkout a tag, and a detached commit

Confirm that the graph is being updated correctly

Use the Checkout command from the status bar to create a new branch

Confirm that the graph is being updated correctly

All

Launch VS Code Insiders
Open a folder/workspace that contains a git repository
Open the "Source Control Graph" view
Click on the History Item Reference picker and choose "All"

Confirm that the graph is updated accordingly
Confirm that all references (HEAD, branches, tags appear in the graph)
Confirm that each badge is colored and is matching the color of the "*" in the graph
Confirm that the first badge has a label which all others only display the icon

Scroll down to load more pages

Confirm that the graph is being rendered correctly (ex: no broken swim lanes, etc.)

Explicit History Item Refs

Launch VS Code Insiders
Open a folder/workspace that contains a git repository
Open the "Source Control Graph" view
Click on the History Item Reference picker and choose 2, 3 explicit history item references

Confirm that the graph is being updated correctly

Reload the window

Confirm that the filter state/graph is restored

Use the Checkout command from the status bar to switch between branches

Confirm that the graph is not updated and it maintains its state

History Item Ref Deletion

Launch VS Code Insiders
Open a folder/workspace that contains a git repository
Switch to the default branch of the repository
Use the Checkout command from the status bar to create a new topic branch (ex: topic-branch)
Switch back to the default branch of the repository
Open the "Source Control Graph" view
Click on the History Item Reference picker and choose only the history item reference of the newly created topic branch (ex: topic-branch)

Confirm that the graph is updated accordingly

Open the integrated terminal and run the following command git branch -D topic-branch to delete the topic branch

Confirm that the history item reference picker is reset to "Auto"
Confirm that the graph is updated accordingly

Explicit History Item Refs

Use the Checkout command from the status bar to switch between branches

Confirm that the graph is not updated and it maintains its state

The colors of the swim lanes change, but the graph otherwise stays the same.

Works great! Excited to be using this.


Add view-model alias for partial

fixes Starcounter/starcounter-include/issues/21

Have you tested it? Does it pass tests when you just replace partial= with view-model=?

Thanks. Sorry, I didn't tested setting it before createdCallback I think once we will agree on final naming replacement, we will just replace it everywhere in the code, so we will not have to maintain tests for aliasing

I have tried it with KitchenSink, but it seems to not work. View-model changes seem to be not propagated. Can you pls check?

I did and it works

@warpech Thanks!
released as 2.2.0

Thank you. Added to Starcounter 2.3


fix(chart): add JSON tags to chart object

Go capitalizes field names by default. Release metadata is JSON-encoded. This wasn't an issue in Helm 2 because everything was encoded in gRPC protocol buffers over the wire. In Helm 3, the client creates the release object directly from the Release struct.
To replicate:
helm create foo
helm install foo ./foo
kubectl get secret sh.helm.release.v1.foo.v1 -o jsonpath='{.data.release}' | base64 -d | base64 -d | gunzip

Marking as a last-minute 3.0 fix as changing this after 3.0 would break compatibility.
Signed-off-by: Matthew Fisher<EMAIL_ADDRESS>

@bacongobbler Maybe worth another maintainer also taking a look?

Just curious, why is this called a fix? Does capital case break anything?

And in any case, I would recommend adding tests for this, or things might be changed by mistake later

@karuppiah7890 Naming consistency for json object field names.

But a good point on what does it break?

serializing and de-serializing release object prior to this change. This is a backwards compatibility breaker.

Maybe worth another maintainer also taking a look?

Yeah, I can get @mattfarina or @thomastaylor312 to review this.


none is not an allowed value: sources -> source.default.xyz -> metadata -> type

I get the above error for dbt version 1.4.1 using snowflake.
The error is related to this line: https://github.com/yu-iskw/dbt-artifacts-parser/blob/main/dbt_artifacts_parser/parsers/catalog/catalog_v1.py#L33
The obvious fix here is to adapt the type to be Optional[str] - but if I understand this is auto-generated based on this line. And this is based on the dbt-core definition here.
What's the standard process in this case?

The underlying issue here is a bug in dbt-snowflake: https://github.com/dbt-labs/dbt-snowflake/pull/818


add xorg-libxrender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

If the problem in https://github.com/bgruening/docker-galaxy-stable/issues/420 is the same X11 issue that I am having in https://github.com/bioconda/bioconda-recipes/pull/7859, then after adding libXrender and libSM, the next required dependency will be libXext (xorg-libxext).

I would really appreciate a test, but was not able to pin one up until now.

I'll work on coming up with a suitable test.

OK. Here's a test that will confirm that the X11 dependencies (and also Pandoc) are installed and functional:
$R -e "x <- tempfile(fileext = '.Rmd'); file.create(x); rmarkdown::render(x)"  # [not win]
"\"%R%\" -e \"x <- tempfile(fileext = '.Rmd'); file.create(x); rmarkdown::render(x)\"" # [win]

It creates and empty file and then renders it. Both files are created in the R session's temporary directory, and are thus deleted the second the command ends. I confirmed in the galaxy-stable image that this fails when missing the X11 libraries and passes otherwise. I didn't actually check the Windows command, but presumably the CI should catch if there's a typo with all the quotation marks and backslashes.
Also, testing this in the galaxy-stable docker image was a pain because I had to manually install Miniconda first. Do you have a Docker image available that is galaxy-stable plus conda?

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [60]

@jdblischak added the test and hope it will crash now. Then I will fix it. Thanks a lot for your fixes.
The Galaxy Docker images containers since 2 years a conda installation. You can find it under /tool_deps/_conda/.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [61]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

You can find it under /tool_deps/_conda/.

@bgruening Thanks. Now I know for next time.
FYI Pandoc is now listed twice in the run-time dependencies, once at the beginning specifying a minimum version and then the one you added specifying a maximum. Support for Pandoc 2.* has been added in more recent versions of rmarkdown, so we can clean this up in the future.


Issue with using the SDK with the ERC4337 wallets, HSM, and WalletConnect

Description
The way the SDK is architectured, it always assumes that the wallet that will be used for PUSH Chat/GroupChat will be always be an EOA with application always having access to wallet keystore. The SDK is not compatible with 4337 wallets, HSM and WalletConnect since in any of the above case we might have access to keystore.

Closing, because we can customize signer by extending Signer our own signer for the use cases apart from ones where we have keystore available.


[bug] accidentally converts a multiline attribute into multiple attributes

Continued from https://github.com/ryansolid/dom-expressions/issues/143
input:

output:
     [
      {
        type: 'tag',
        name: 'div',
        voidElement: false,
        attrs: { foo: '', bar: '' },
        children: []
      }
    ]

What if we switch to this: https://npmjs.com/html-dom-parser
It falls back to the native DOM parser on the client, and it gets the parsing correct.
Was the regex faster than DOM APIs on the client?
I'm having a hard time getting the regex to work well for all the attribute cases (still trying...).

Here's the new test input I'm using (all are valid HTML attributes, but not all valid attributes possible are included yet):
`

`

For reference, here are the results of the current regex here in html-parse-string:
https://regexr.com/6p8dc
Here's one that catches more results, but still not there yet:
https://regexr.com/6p82g

Yeah.. hmm this is super old. We could swap it out. I used this library because I was familiar with it, and it was something I had done back in the knockout days. I had forked a different library and added some functionality (because the original didn't properly handle web components). I'm almost positive there are better solutions.

Hmm. I can't find a single regex that catches them all yet, but I did find a two-step approach using two regexes. First we extract all the attributes with values like so:
https://regexr.com/6p82j
Then we delete those matches from the string, and we can finally extract the remaining boolean attributes:
https://regexr.com/6p8on

I know this is a resolved issue, but I would like to know why this library is needed when there is the DomParser API in the Browser? Why not use DomParser API for dom-expression instead of this?


In file with comments, find all references tree loses focus

Open a PR using the GH PR extension
Open a file that has comments
Do "Find all references"
Use up/down arrow keys
The focus should be in the tree of the references peek view, but the focus is in the peek editor

I can see focus switch from the tree to the peek editor shortly after opening. I see this in a couple files that have comments and nowhere else so I assume it's related to the comments widget somehow.

Related: ctrl+tab to a file with comments and immediately press cmd+f. The editor will steal focus from the find widget after half a second.


globals.md / packages.md vs index.md

What package is your question related to?
typedoc-plugin-markdown
What would you like to ask?
I am using typedoc-plugin-markdown along with typedoc-vitepress-theme and I noticed that typedoc-plugin-markdown generate globals.md file for my modules and a packages.md
These looks like index file to me, but the plugin also generate index.md file and these is the one referenced in the generated typedoc-sidebar.json by typedoc-vitepress-theme
Is there an option to merge index.md and (globals.md/packages.md) ?

You can set mergeReadme: true to append the index page to the readme page to create a single entry point file, or readme:  'none' to ignore readme file completely.

Thanks @tgreyuk
mergeReadme: true will probably work for what I want. It seems it merge the top level README in if none if present at the package level, so I might just need to create empty README file there if I want to document the module via @module tag in index.ts.
I tried to set "readme": "none" in typedoc.json but it does not seem to do anything. I was hoping it would remove the need for me to create these empty README

To set readme:none for individual packages in addition to the top level you can try:
packageOptions: {
 readme: "none"
}


Pin the mdbook version for CI.

Fixes #779.

r? @fitzgen

@bors-servo r+
Thanks! :)

:pushpin: Commit 9b4bd6b has been approved by fitzgen

:hourglass: Testing commit 9b4bd6bff754e6b654f85fc676288ff660dbc6b3 with merge 607b5bd5cd0aac4bf2f7ba1d87875c8e9dd71a20...

:sunny: Test successful - status-travis
Approved by: fitzgen
Pushing 607b5bd5cd0aac4bf2f7ba1d87875c8e9dd71a20 to master...


Poap design

We should make a poap with the webaverse mark.
It can be a mario red coin style. The first thing we need is the 2d version, but it can also be modeled to be 3d.

lets use one of our logos / stamps we have ..
u can find it in drive as well as ask ahmed @GaladWarder


Make a specific icon for Kresus

All the previous icons for Kresus have been proposed by Cozy, as far as I can tell.  And if it's a nice logo, I would even print some stickers and send them to contributors and people when attending meetups, that'd be great!
I thought about using the K letter, as it's prominent in the application's name. Experiments included barring the K with a double bar (as for the Euro sign), or using the mathematical ensemble K letter, but I couldn't get to anything good looking.
Any proposals here would be appreciated :-)

The currency K with double bar idea looks fine (note that the single bar variant, ₭, is already assigned to a real currency, the laotian Kip).


wrong $RESOURCE_GROUP_NAME variable used in one of the example commands

Throughout the article, the resource group is pointed to in each az command with
--resource-group $resourceGroup
only in the second-to-last command it uses:
--resource-group $RESOURCE_GROUP_NAME
which should also use the same $resourceGroup instead
in other words:
sed 's/$RESOURCE_GROUP_NAME/$resourceGroup/g'

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

ID: 6a2b459d-cbbb-100d-a10c-6652c55885b7
Version Independent ID: d45dcb68-316d-d166-426a-88feb1fd05e3
Content: Configure static outbound IP - Azure Container Instances
Content Source: articles/container-instances/container-instances-egress-ip-address.md
Service: container-instances
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

@gitmpr
Thanks for your feedback! We will investigate and update as appropriate.

@gitmpr
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Feature Add attribute for auto focus within off canvas

Checks for the attribute [data-autofocus] within the toggled off canvas
and focuses on the first occurrence if available.  Otherwise reverts to
standard behaviour.

Seems reasonable to me - @brettsmason what do you think?

ping @brettsmason

@kball sorry missed this. This sounds like a really good idea. Had a quick look at the code and it looks fine to me. Maybe you could just double check from a JS point of view (not my strong point 😄 ) and merge if you are happy.

Thanks team,  how do I go about get this documented?

@gorriecoe => /docs/pages/offcanvas.md
Just In case you confused about how to run docs,
see => https://github.com/zurb/foundation-sites#documentation


Chapter Page: Invisible link

There is a invisible block which redirects to same page in chapter page. I have marked the spot below

In marked area you can see that background is disturbed. Also the line seperating different chapters is white, it could be either a little more pronounced or removed. Also each div containing chapter names extends upto the end not just the name, hence the area to click too

Actually it's not the invisible block @engorgedspirit , each college block itself is not upto it's size, try resolving this
And let the current clg when clicked , linked to that page itslef, as we will be linking separate pages soon

Description :
An invisible link will run when we click on any of the college from the given colleges list.This link redirects to its respective website on the same page, when back button in the browser is clicked it comes back to its chapters page. Could you assign this to me under gssoc'23.


domain and subdomain in nginx

How I can have domain and subdomain for examle my blog in a WordPress website and I wanna have blog.site.com
where I should config it?

Try to use google how to configure nginx. Issue is not related to this environment.


Remove frameworkAssembly reference to System.Net.Http

It should be sufficient to have a dependency on the System.Net.Http nupkg.
The frameworkAssembly reference breaks downstream packages that target net461 but have other dependencies that target netstandardx.x and depend on System.Net.Http via NuGet because the assembly versions in the GAC (for both 4.5.x and 4.6.x) differ from the latest published via NuGet.

PR?

I will try to submit one before the weekend.

My first PR on github, hope I did it right :-)

thanks - done!

Thanks, @suddenelfilio.  Life intervened for me, unfortunately, so I'm grateful that you picked up the slack.

I moved to the new csproj
Could you try the dev branch - and if this fixes your scenarios?
Just call the build.ps1 in the root - it will produce a nuget

I think this 'fix' is causing problems when using it in the full .NET Framework since "System.Net.Http" is a part of the .NET Framework already.
When I install IdentityModel2 in my full .NET framework (net461) project and target this package in 2.5.0 or above (the version from which this dependency was introduced), I am getting a lot of errors regarding missing references if I try to use the the classes defined in System.Net.Http.
Aren't you supposed to ONLY put the dependency on System.Net.Http for the netstandard version and keep it as a framework reference for .NET framework?

I don't know - open a new issue please.

Been investigating this a bit more by trying to:

Create new project.
Ensure the project targets net461.
Add nuget dependency to System.Net.Http.
Create class that inherits from HttpClientHandler.
Build and watch it fail or succeed.

I tried this for project types: [project.json/xproj], [new csproj], [old csproj]. It was ONLY a problem for the [project.json/xproj] build system. All other attempts succeeded just fine.
Basically, when targeting the OOB nuget packages (System.Net.Http) that are also a part of the .NET framework in a project which targets net46 or greater while using project.json the problem may occur. If you target net45 it also works, even for [project.json/xproj].
I think the same issue is described here https://github.com/dotnet/corefx/issues/14445
I'm not going to open a new issue, unless you feel it is important. But not having a dependency on OOB nuget packages for the net46+ version of this library would fix the problem.

It was ONLY a problem for the [project.json/xproj] build system.

IOW - this is not an issue anymore since project.json is deprecated. right?

That would be correct.

OK - thanks for researching that. Since project.json and the other combinations seem to work - we can leave it as it is.


add twitter new logo

What kind of changes does this PR include?

Add an icon

Description

Add the new twitter svg logo next to the older one.

Thanks for your contribution. :raised_hands:
This changes makes me wonder a few things:

Should this be added as a new logo or should it replace the current twitter one?
Should this have an impact on the social media icons displayed in the site header?
If yes, should twitter be renamed to x or both be kept?

Not sure what to think as x.com links redirects to twitter.com but twitter.com uses the new x logo on the official Twitter website, this is a bit confusing ^^ :thinking:

If we replace twitter for x, we risk to break references to the old icon if some dev buddies used it directly. Maybe we could keep both for a few months and remove twitter icon after that?
Regarding social media icons I will create a new pull request for supporting X as social media.

One thing: I wonder if we should use x.com as the key here? We’ve discussed expanding our built-in icon support to include the full set of Unicons (the icon set Starlight uses currently) and it already includes a generic x icon that could clash. What do you think?

Sounds fine by me.
I guess the remaining missing changes after updating the key would be updating docs/src/content/docs/guides/customization.mdx & docs/src/content/docs/reference/configuration.md to document it and adding a changeset.

Hi @HiDeoo. I have updated customization & configuration files in all available languages. Let me know if I miss something but I think w're good :)


Set correct scope separator for Instagram

Instagram's scope separator is +, as documented here. This patch fixes that on master.

Did you also make an issue on oauth2-instagram?

Didn't realise they were separate packages now. Not sure how I missed that.

@shadowhand Created an issue here

No need to close this, the split provider is only for 1.0+. Would be good to fix this one master too. :)

I'm clearly having a good day it seems.


[question]ShenYu Agent  tracing support skywalking

Description
does ShenYu Agent  tracing support skywalking?
Task List
No response

Thank you for your attention. At present, I am developing this plug-in and will support it soon. Please pay attention.
issue:https://github.com/apache/incubator-shenyu/issues/3076

skywalking pr: https://github.com/apache/skywalking-java/pull/147
we should support http and other rpc.

good job，you can go on

skywalking pr: https://github.com/apache/skywalking-java/pull/147
we should support http and other rpc.

These have all been supported: HTTP,Spring Cloud,gRPC,Dubbo,SOFARPC,Motan,Tars .
I will write a post about integrating skywalking to achieve observability

The blog has been written. welcome to use.
chinese blog
english blog


Release always crash

Debugging works well, but when releasing it the build crash. I tried building your example and the same error happened!
It seems like there is a problem with the gradle version...
Do you have any ?
FAILURE: Build failed with an exception.
                     * Where:
                     Build file
                     '/home/travis/.pub-cache/hosted/pub.dartlang.org/flutter_ma
                     pbox_navigation-0.0.9/android/build.gradle' line: 26
                     * What went wrong:
                     A problem occurred evaluating root project
                     'flutter_mapbox_navigation'.
                     > Failed to apply plugin [id 'com.android.library']
                        > Minimum supported Gradle version is 5.4.1. Current
                        version is 4.10.2. If using the gradle wrapper, try
                        editing the distributionUrl in
                        /home/travis/.pub-cache/hosted/pub.dartlang.org/flutter_
                        mapbox_navigation-0.0.9/android/gradle/wrapper/gradle-wr
                        apper.properties to gradle-5.4.1-all.zip
                     * 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
                     BUILD FAILED in 21s
[        ] Running Gradle task 'assembleAarRelease'... (completed in 22.0s)
[        ]
           FAILURE: Build failed with an exception.

           * Where:
           Build file
'/home/travis/.pub-cache/hosted/pub.dartlang.org/flutter_mapbox_navigation-0.0.9
/android/build.gradle' line: 26

           * What went wrong:
           A problem occurred evaluating root project
'flutter_mapbox_navigation'.
           > Failed to apply plugin [id 'com.android.library']
              > Minimum supported Gradle version is 5.4.1. Current version is
4.10.2. If using the gradle wrapper, try editing the distributionUrl in
/home/travis/.pub-cache/hosted/pub.dartlang.org/flutter_mapbox_navigation-0.0.9/
android/gradle/wrapper/gradle-wrapper.properties to gradle-5.4.1-all.zip

           * 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

           BUILD FAILED in 21s

PS: Your package lost his track of versions, it seems like you're not using tags to mark the versions, and that caused us some problems with the code since there are some breaking changes between 0.0.4 and 0.0.9.... So the version 0.0.4 will always download the latest version of your package... can you also check that out?
Thanks :)

Can you upgrade your Gradle?
For the version, you will need to follow version specification guidelines for pubspec.yaml. ^0.1.2 means, version 0.1.2 and above. If you only want a specific version remove the ^


Create a .gitmessage template and a Composer script for configuration

When using the -g or --git option it would be useful to create a .gitmessage template, which follows the rules described by Chris Beams, and a Composer script for configuring it. This might raise the quaility of commit messages.

As .gitattributes and .gitignore are generated per default, maybe this addition should also be generated per default.


Update outdated label to use Fomantic UI style

This is an update to #13148. As I mentioned the CSS could be improved, and I didn't realize styling could have been done by just using native elements from Fomantic UI.

Is the UI same as before?

Got a screenshot?

Again, referencing my previous PR (and https://github.com/go-gitea/gitea/pull/13148#issuecomment-709416432). I noticed some unnecessary css/styling for labels that could be native Fomantic UI elements. I initially just change the one I recently added (the outdated label), but went ahead and updated the rest of them. I'm attaching screenshots from Firefox and Chrome for each of the affected elements, and both using the defualt theme and arc-green.
Emphasis in the labels:

Pending
Review
Collaborator
Owner
Outdated

Chrome default theme:

Chrome arc-green theme:

Firefox default theme:

Firefox arc-green theme:

@silverwind, @lunny: updated the PR with screenshots :)

Crap, broke the frontend linter, will fix it...

@ivanvc pleace resolve conflicts :)

@6543 done!

:rocket:

🚀


Login method is deprecated and no longer supported in versions above 6.45.1.

Please change login method for supporting routeros 6.45.1 and newer:
https://wiki.mikrotik.com/wiki/Manual:API#Initial_login

+1

Seems to be already fixed in https://github.com/go-routeros/routeros/pull/4

Implemented by @archaron in #4.

Implemented by @archaron in #4.


Update for ripplex.io/ripplex.money infra

Closing in-favor of https://github.com/hyperledger/quilt/pull/476


CNV-44956: Adjusting storage checkups new fields

📝 Description
Adjusting to new changes in BE for storage checkups according to https://github.com/kiagnose/kubevirt-storage-checkup?tab=readme-ov-file#checkup-results-retrieval
🎥 Demo

/retest


Issue in siteimprove: Scrollable element is not keyboard accessible

Please see this report in Siteimprove, where we can gain 1,5 points for fixing the issue:
https://my2.siteimprove.com/Accessibility/550893/NextGen/Issue/1?conformance=&pageSegments=&ruleName=sia-r84&ruleId=84&issueKind=1&exceptTags=1,2&siteTarget.conformanceLevels=0,1,3

Search for elements with overflow and set tabindex 0 on them

@BorghildSelle - anything to test for this?

@meols No, more techincal and have verified in staging :)


Can it be used for commercial purposes

Can I include this technology as part of my business project?

Hi, you can use the code to train your own model on your own data.
But the pretrained weights can only be used for non-commercial purposes.


outline: 0.78.0 -> 0.79.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for outline is: Fastest wiki and knowledge base for growing teams. Beautiful, feature rich, and markdown compatible
meta.homepage for outline is: https://www.getoutline.com/
meta.changelog for outline is: https://github.com/outline/outline/releases
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.79.0 with grep in /nix/store/q1477vi9y9k0k66lw5b1xhbxyq7p7xm4-outline-0.79.0
found 0.79.0 in filename of file in /nix/store/q1477vi9y9k0k66lw5b1xhbxyq7p7xm4-outline-0.79.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

outline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q1477vi9y9k0k66lw5b1xhbxyq7p7xm4-outline-0.79.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A outline https://github.com/r-ryantm/nixpkgs/archive/fec686e486eca5b6687f4c2d2ef97b68b55b7d42.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fec686e486eca5b6687f4c2d2ef97b68b55b7d42#outline

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q1477vi9y9k0k66lw5b1xhbxyq7p7xm4-outline-0.79.0
ls -la /nix/store/q1477vi9y9k0k66lw5b1xhbxyq7p7xm4-outline-0.79.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

outline

Maintainer pings
cc @cab404 @yrd @xanderio for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge