Is there a way to add a relation to one of navigations created?

Hi,
I was trying to find a way to add a relation to navigation plugin. I mean: imagine you have a single type used as site global configuration where I set many things, the page that is the homepage (using a relation to the page content type), a relation to cookie page and so on.
Using my custom menu content type I had a relation to a menu, so the user could create different menus and select the desired one using that relation.
So the question: is it possible to add a relation to navigations so the user can choose the one he wants?

I'd +1 this, for example we'd quite to make our link component be able to refer to the NavigationItem collection so a user could select from a page route that exists
But I see you dismissed https://github.com/VirtusLab-Open-Source/strapi-plugin-navigation/issues/340
We're generating all our routes from the navigation plugin, is there a workaround to make a link component that reads from existing routes?

To archive that you can try to extend the Content Types of our plugin using Strapi Extensions strategy and simply do the changes in this part:
  pluginOptions: {
    "content-manager": {
      visible: false
    },
    "content-type-builder": {
      visible: false
    },
    i18n: {
      localized: false
    }
  },

content-manager is responsible for availability of Content Type in the Editor
content-type-builder is responsible for availability of Content Type in the Builder

Hope it gives you some kind of direction :)

Closing as no response.


Image not uploaded to DockerHub

The releases of 24.5x.yz has not been uploaded to Docker Hub.
It looks like it should have been published when looking at the GitHub Action Log, but I'm not allowed to use it when specifying image: netdaemon/netdaemon4:24.52.0.
I get the following error:
Error response from daemon: manifest for netdaemon/netdaemon4:24.52.0 not found: manifest unknown: manifest unknown

I can see it has been moved to another repo on DockerHub.
Closing this


Is the current code at master working correctly?

Expected Behavior
Build an run the image using the Dockerfile on the root directory should start the Grafeas server correctly
Actual Behavior
I'm building a new image using the Dockerfile. Then based on that new image I'm building https://github.com/grafeas/grafeas-pgsql/blob/master/server/Dockerfile. The build is succesfull but when I try to run the server I'm getting:
{"error":"all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake","message":"all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake","code":14,"details":[]}

As an alternative, I also tried running the main.go from v1beta1 and I added some debug flags:
GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info GRPC_VERBOSITY=DEBUG go run main.go --config config.yaml
2019/09/16 20:00:16 pagination key is empty, generating...
2019/09/16 20:00:16 starting grpc server on <IP_ADDRESS>:8080
INFO: 2019/09/16 20:00:16 parsed scheme: ""
INFO: 2019/09/16 20:00:16 scheme "" not registered, fallback to default scheme
INFO: 2019/09/16 20:00:16 ccResolverWrapper: sending update to cc: {[{[::]:8080 0  <nil>}] <nil>}
INFO: 2019/09/16 20:00:16 ClientConn switching balancer to "pick_first"
2019/09/16 20:00:16 grpc server is configured without client certificate authentication
INFO: 2019/09/16 20:00:16 pickfirstBalancer: HandleSubConnStateChange: 0xc00006c070, CONNECTING
INFO: 2019/09/16 20:00:36 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
WARNING: 2019/09/16 20:00:36 grpc: addrConn.createTransport failed to connect to {[::]:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/09/16 20:00:36 pickfirstBalancer: HandleSubConnStateChange: 0xc00006c070, TRANSIENT_FAILURE
INFO: 2019/09/16 20:00:37 pickfirstBalancer: HandleSubConnStateChange: 0xc00006c070, CONNECTING
INFO: 2019/09/16 20:00:57 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
WARNING: 2019/09/16 20:00:57 grpc: addrConn.createTransport failed to connect to {[::]:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/09/16 20:00:57 pickfirstBalancer: HandleSubConnStateChange: 0xc00006c070, TRANSIENT_FAILURE
INFO: 2019/09/16 20:00:58 pickfirstBalancer: HandleSubConnStateChange: 0xc00006c070, CONNECTING
^Csignal: interrupt

Steps to Reproduce the Problem
Environment, commands

Download the latest version of the code
make
GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info GRPC_VERBOSITY=DEBUG go run main.go --config config.yaml
Go to http://localhost:8080/v1beta1/projects/user

Additional info
config.yaml
grafeas:
  # Grafeas api server config
  api:
    # Endpoint address
    address: "<IP_ADDRESS>:8080"
    # PKI configuration (optional)
    cafile:
    keyfile:
    certfile:
    # CORS configuration (optional)
    cors_allowed_origins:
      # - "http://example.net"
  storage_type: "postgres"
  # Postgres options
  postgres:
    # Database host
    host: "<IP_ADDRESS>:5432"
    # Database name
    dbname: "postgres"
    # Database username
    user: "postgres"
    # Database password
    password: "password"
    # Valid sslmodes disable, allow, prefer, require, verify-ca, verify-full.
    # See https://www.postgresql.org/docs/current/static/libpq-connect.html for details
    sslmode: "disable"
    # 32-bit URL-safe base64 key used to encrypt pagination tokens
    # If one is not provided, it will be generated.
    # Multiple grafeas instances in the same cluster need the same value.
    paginationkey:

Hi @judavi, did you follow the steps described in Starting Grafeas? It sounds like you're trying to start the server from grafeas-pgsql Dockerfile, but also perhaps using the Dockerfile in grafeas GH project -- could you please clarify?
I was able to start the server in go/v1beta1 per instructions. From the description of the issue, it sounds like you're trying to bring up the Grafeas server with PostgreSQL backend. I recommend using https://github.com/grafeas/grafeas-pgsql to get started with that.

Hi @aysylu
Yes, in the past I was able to start the project successfully. I have been working to complete the PR from here https://github.com/grafeas/grafeas-pgsql/pull/6
I also tried the following :
cd ~/go/src/github.com/grafeas/grafeas
cd go/v1beta1
go run main/main.go

Output
➜  main git:(master) ✗ go run main.go
2019/09/16 20:43:56 starting grpc server on <IP_ADDRESS>:8080
INFO: 2019/09/16 20:43:56 parsed scheme: ""
INFO: 2019/09/16 20:43:56 scheme "" not registered, fallback to default scheme
INFO: 2019/09/16 20:43:56 ccResolverWrapper: sending update to cc: {[{[::]:8080 0  <nil>}] <nil>}
INFO: 2019/09/16 20:43:56 ClientConn switching balancer to "pick_first"
2019/09/16 20:43:56 grpc server is configured without client certificate authentication
INFO: 2019/09/16 20:43:56 pickfirstBalancer: HandleSubConnStateChange: 0xc000032030, CONNECTING
WARNING: 2019/09/16 20:44:16 grpc: addrConn.createTransport failed to connect to {[::]:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/09/16 20:44:16 pickfirstBalancer: HandleSubConnStateChange: 0xc000032030, TRANSIENT_FAILURE
INFO: 2019/09/16 20:44:16 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/09/16 20:44:17 pickfirstBalancer: HandleSubConnStateChange: 0xc000032030, CONNECTING
```

Basically what happened is I was testing my changes to remove the pgsql storage files from the main project. So I pulled the latest changes from the main repo (grafeas) and I faced the error. Then thinking it was something with my code I came back to the master branch and I tried to build the app without any of my changes but similar situation.

Hm, interesting. I just synced to the latest and ran go run main/main.go in the same directory as you and got:
2019/09/16 15:53:36 starting grpc server on <IP_ADDRESS>:8080
2019/09/16 15:53:36 grpc server is configured without client certificate authentication

Could you please confirm your grafeas GH repo is synced to the latest commit?
Also, I just merged https://github.com/grafeas/grafeas-pgsql/pull/7 which should fix one of the issues.

@aysylu yes the server is starting correctly. The extra information is because I'm using
GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info GRPC_VERBOSITY=DEBUG

Then the error is happening when you try to use one of the methods of the API.  Like
http://localhost:8080/v1beta1/projects/user --> this normally should reply with a Json

Just to be sure it wasn't something with my local repo I started a new container and I pulled the code there and manually build and started the API: https://asciinema.org/a/nP4XRtzynBvONDT60Rx0oNXz7

Great! So is this resolved now?

@judavi please re-open if this is still an issue. Closing for now.

@aysylu I'm afraid this is still happening. Is not only about starting the server, because the server is "starting" correctly. The issue appears as soon as you try to use any of the services of the API. Something like http://localhost:8080/v1beta1/projects

cc @vtsao

Hi @aysylu  curl or the browser, same result:
~ curl http://localhost:8080/v1beta1/projects
{"error":"all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake","message":"all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake","code":14,"details":[]}%

On the server side, if you enable GRPC debug information this is the output:
$ export GRPC_GO_LOG_VERBOSITY_LEVEL=99
$ export GRPC_GO_LOG_SEVERITY_LEVEL=info
$ export GRPC_VERBOSITY=DEBUG
$ go run main.go --config config.yaml
2019/10/08 17:26:18 starting grpc server on localhost:8080
INFO: 2019/10/08 17:26:18 parsed scheme: ""
INFO: 2019/10/08 17:26:18 scheme "" not registered, fallback to default scheme
INFO: 2019/10/08 17:26:18 ccResolverWrapper: sending update to cc: {[{<IP_ADDRESS>:8080 0  <nil>}] <nil>}
INFO: 2019/10/08 17:26:18 ClientConn switching balancer to "pick_first"
2019/10/08 17:26:18 grpc server is configured without client certificate authentication
INFO: 2019/10/08 17:26:18 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, CONNECTING
WARNING: 2019/10/08 17:26:38 grpc: addrConn.createTransport failed to connect to {<IP_ADDRESS>:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/10/08 17:26:38 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
INFO: 2019/10/08 17:26:38 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, TRANSIENT_FAILURE
INFO: 2019/10/08 17:26:39 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, CONNECTING
INFO: 2019/10/08 17:26:59 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
WARNING: 2019/10/08 17:26:59 grpc: addrConn.createTransport failed to connect to {<IP_ADDRESS>:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/10/08 17:26:59 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, TRANSIENT_FAILURE
INFO: 2019/10/08 17:27:00 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, CONNECTING
INFO: 2019/10/08 17:27:20 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
WARNING: 2019/10/08 17:27:20 grpc: addrConn.createTransport failed to connect to {<IP_ADDRESS>:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/10/08 17:27:20 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, TRANSIENT_FAILURE
INFO: 2019/10/08 17:27:23 pickfirstBalancer: HandleSubConnStateChange: 0xc0001e0940, CONNECTING
WARNING: 2019/10/08 17:27:43 grpc: addrConn.createTransport failed to connect to {<IP_ADDRESS>:8080 0  <nil>}: didn't receive server preface in time. Reconnecting...

Hi @aysylu @vtsao I built again on a clean machine (Centos 7.5). Similar situation. This time I'm running the DB on the host to discard issues with Postgres running on a container. Same result. I'm not able to use any of the endpoints using CURL or the browser.
A complete log of the build and run command is available here: https://gist.github.com/judavi/bb8d6eb20fcce037dbbf4d02545daad6
Please, could you give me some advice, for building I'm not using anything different to "make" and then go run main.go --config config.yaml

@aysylu @vtsao
Ok, I have some extra information. If I go back to an old version the REST API starts working again.  For example:
main git:(master) ✗ git checkout 9e63ccc6d9ce929f7674fe7ad693b10832760af7
Note: checking out '9e63ccc6d9ce929f7674fe7ad693b10832760af7'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 9e63ccc... Merge pull request #361 from aysylu/0.1.0

Then
make
...removed make output...

go run main.go --config config.yaml
2019/10/10 15:00:07 pagination key is empty, generating...
2019/10/10 15:00:07 starting grpc server on localhost:8080
2019/10/10 15:00:07 grpc server is configured without client certificate authentication

and finally
curl http://localhost:8080/v1beta1/projects
{"projects":[],"nextPageToken":""}%


Removing duplicate crown copyright link from footer

Application of new design, now renders the previous crown copyright link redundant.

Good read! +1


called reset() in personalize()

Added a bool in parameter: true does a reset, false doesn't.#6

@johanstokking can't we just call reset() unless personalize() was called with no arguments? Or am I not understanding the reason for reset()?

Yep. I think if you want to personalize with custom keys, that it's good to reset first. Otherwise, when you want to personalize with whatever is in the RN module, you don't reset first.

@Nicolasdejean no it's OK like this
Code is approved
@FokkeZB can you test?

I've successfully tested with this in setup()
  ttn.init(loraSerial, debugSerial);

  debugPrintLn("Personalize with keys");
  ttn.personalize(devAddr, nwkSKey, appSKey);

  debugPrintLn("Send 0x11");
  byte payload[] = { 0x11 };
  ttn.sendBytes(payload, sizeof(payload));

  debugPrintLn("Personalize without keys");
  ttn.personalize();

  debugPrintLn("Send 0x22");
  byte payload2[] = { 0x22 };
  ttn.sendBytes(payload2, sizeof(payload2));

Both messages came through fine.


Missing Technical.md from the README's Contribution section's link

Description
Just noticed that the documentation for contributing is pointing at a non existent document called technical.md.
Where's this live now? And can we update the docs to point to it if it's still relevant? Otherwise, I think it should be removed to avoid confusion.

Oh, thanks a lot for pointing it out! I'll add it for the upcoming release 🚀

Done in the latest version! 🚀


GeoJSON with lines is very slow

I'm using L.GeoJSON to draw 32,623 lines on a Leaflet map.
The lines have between 2 and 709 coordinates with an average of 14 coordinates. But having these loaded in makes the app unusable or at least very slow.
Expected Behavior
More fluent dragging and zooming on the map.
Current Behavior
When I drag or change zoom the application freezes for a bit and then after a second it continues but stutters a lot. When I release the drag it also freezes for a second. This makes quick short drags impossible to do.
Screenshot:
https://imgur.com/a/ZqgIGpA
Biggest part of the lines on the map and a zoomed in part to see the layout of the lines
Animated GIF:
https://gyazo.com/42dc8f76e1e33db055a4558455250ed4
In the GIF you see when I start dragging I move my mouse and only after a second or so the map goes with.
I'm currently working from home on a pc with an AMD Ryzen 9 CPU and 32GB of DDR4 RAM so on my work pc or any of my customers work pcs it would result in ever a slower reaction.
Possible Solution
Removing listeners/interactivity at certain zoom levels maybe or optimizing code that runs when I start dragging.
Steps to Reproduce
I use a Leaflet map with a TileLayer (Carto) and I load a GeoJSON with 32,623 features. The features have one property and that's the uuid of their linked object. When it's loaded it's incredibly slow when I START and STOP dragging. After the freeze it seems to work decently as long as I hold the mouse. When I'm all the way zoomed out though even dragging stutters a lot. But I could live with that.
Environment

Leaflet version:  1.7.1
Browser & Version: Chrome 84.0.4147.135
OS & Version:  Windows Microsoft 10 Pro v1909
Running Example: n/a

I'm using L.GeoJSON to draw 32,623 lines on a Leaflet map.

This is basically too much.
But you can try that with https://leafletjs.com/reference-1.7.1.html#map-prefercanvas option.

I'm using L.GeoJSON to draw 32,623 lines on a Leaflet map.

Try adding 32 623 SVG elements on a webpage and measuring how long that takes to display.

I'm using L.GeoJSON to draw 32,623 lines on a Leaflet map.

Try adding 32 623 SVG elements on a webpage and measuring how long that takes to display.

I'm sorry but is this irony? Using L.GeoJSON is an alternative for using a plugin called Leaflet.PixiOverlay which uses Pixi's WebGL engine and that kind of works fine performance-wise but I'm having interactivity and graphical issues there.

I'm sorry but is this irony?

No, it's not.

A different solution could be to disable interactivity on lower zoom levels [...]

No, since 32 623 non-interactive SVG elements will take the same time to be drawn than 32 623 interactive SVG elements (hey, prove me wrong!).
Use VectorGrid or something if you want, but the "I'm adding 40000 elements to my map and it's slow" use case is not a Leaflet bug.

It seems to me you're stating the obvious to prove a point that it's not possible. I was hoping to find a work-around because I know it's asking a lot of the client to render everything at once and I'm not asking that you change some code so that it magically works. I was hoping someone could point me towards a solution I haven't thought of yet.

The workaround is VectorGrid.

The workaround is VectorGrid.

I'll look into it. Thanks.


As a user, I want to be able to view all points plotted on a map without them being group into clusters at a high zoom level.

Expected behavior
I like how when the map first displays it zooms automatically into the area of interest, I would like an option to prevent PixieDust from clustering points together
Actual behavior
PixieDust groups points in close proximity into clusters, and to view the individual points one has to zoom into the cluster.
Steps to reproduce the behavior
I prepared a notebook where I show the plot that I generated in Folium and would like to replicate in PixieDust. You can download it via this link.

addressed in #327 by adding non-clustered map options


Remove derives

Summary
Removed what I could, a couple of the Decentralized ones don't compile if I remove them for some reason
Test plan
cargo test
Dependencies
This is stacked on top of #861
Issues
#768

Seems like I can't set the base commit of this to be the other PR's branch, so I can either create this PR differently, or you guys can just review the last commit in the stack :)
Let me know what you prefer


the play/resume button is a white circle [BUG]

As described in the title, the the play/resume button is a white circle. I'm on the latest version of Spotify and Spicetify, and I installed the theme through the Marketplace.

can you give details of your spotify version try updating spicetify and spotify
screenshot or copy paste the info

i cant reproduce the issue if the version, extensions used is not specified

can you give details of your spotify version try updating spicetify and spotify
Spotify for Windows (64 bit): <IP_ADDRESS>1.ge66eb7bc (latest from Spotify's website)
Spicetify: v2.36.11
Extensions: adblockify, Better Spotify Genres (the problem happens even with a fresh installation without any extensions)

sorry for the inconvinence.
i cant reproduce the problem. it might be a issue with spicetify or spotify installation
Try installing via using scripts after a fresh install of spotify and spicetify.
# uninstall spicetify
spicetify restore
rmdir -r -fo $env:APPDATA\spicetify
rmdir -r -fo $env:LOCALAPPDATA\spicetify

Windows (Powershell)
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
iex "& { $(iwr -useb 'https://sanoojes.github.io/better-bloom/install/Better-Bloom.ps1') }"

Tried reinstalling spicetify , spotify , marketplace , theme on windows 10, 11.

There's no point in reinstalling because I've already done it. It's not a big deal, I can live with it

Happening to me too, already tried reinstalling
Spotify for Windows (64 bit): <IP_ADDRESS>1.ge66eb7bc
Spicetify: v2.36.11
Extensions: Cat-Jam Synced, Beautiful Lyrics, No Tracking Links, Playlist Icons

Happening to me too, already tried reinstalling
Spotify for Windows (64 bit): <IP_ADDRESS>1.ge66eb7bc Spicetify: v2.36.11 Extensions: Cat-Jam Synced, Beautiful Lyrics, No Tracking Links, Playlist Icons

sorry i dont know whats the issue i will try fixs for that

i will try to add -webkit-mask for mask-image compatibility sometimes it should fix the issue

i will try to add -webkit-mask for mask-image compatibility sometimes it should fix the issue

nope ;_;

i will try to add -webkit-mask for mask-image compatibility sometimes it should fix the issue

nope ;_;

soory my bad i will try other fixes now

@tajito @kamez104
hey can you check out the new update i removed the inline svg and add the play button image with scripts

@tajito @kamez104 hey can you check out the new update i removed the inline svg and add the play button image with scripts

fixed! tysm :D

ok !

fixed, tysm :D


[1.16] Redstone Integrator Set* does nothing.

Using modpack Enigmatica 6, MC 1.16
Redstone integrator setAnalogOutput/setOutput does nothing.
get* works with external redstone input calls.
Edit:
Seems the set* commands read the state from computer not from the integrator. IE setOutput("top",true) sets the computers top rs high not the integrators top. Is this intended.

Wrong repository
Please report bugs to https://github.com/Seniorendi/AdvancedPeripherals


constructFrom langlib method doesn't handle closed array properly.

Description:
Tuple/open array to closed array conversion doesn't look at the array size
public function main() {
    (int, int) intTuple = (1, 2);
    int[3]|error valueArray = int[3].convert(intTuple);
}

public function main() {
    int[] intArr = [1, 2];
    int[3]|error valueArray = int[3].convert(intArr);
}

Currently the above conversions do not fail. These should fail, since the minimum number of elements required is not present in the source type.

Tested with the following program (on 1.2.2)
public function main() {
    [int, string] intTuple = [1, "2"];
    int[3] valueArray = checkpanic int[3].constructFrom(intTuple);
}

Still the same behavior.

Need to verify if something like creating a T[3] array from a T[2] array should be allowed in cases where T has a filler value.
But the following should fail anway.
import ballerina/io;

type TypeWithNoFillerValue 1|"foo";

type Array TypeWithNoFillerValue[3];

public function main() {
    [TypeWithNoFillerValue, TypeWithNoFillerValue] tuple = [1, "foo"];
    TypeWithNoFillerValue[3] arr = checkpanic tuple.cloneWithType(Array);
    io:println(<any> arr[2] is ()); // Prints true!
}

Need to verify if something like creating a T[3] array from a T[2] array should be allowed in cases where T has a filler value.
But the following should fail anway.
import ballerina/io;

type TypeWithNoFillerValue 1|"foo";

type Array TypeWithNoFillerValue[3];

public function main() {
    [TypeWithNoFillerValue, TypeWithNoFillerValue] tuple = [1, "foo"];
    TypeWithNoFillerValue[3] arr = checkpanic tuple.cloneWithType(Array);
    io:println(<any> arr[2] is ()); // Prints true!
}


v2: Global search does not zoom on selected location

To reproduce:

Open https://mapwith.ai/rapid-sotm-2022#background=Maxar-Premium&datasets=fbRoads,msBuildings&disable_features=boundaries&map=2.00/54.2/10.4 which shows the world
Search for "Rixdorf, Germany",
Click first entry "village"
==> Should zoom to the location; does nothing

Don't see anything on the console; Some locations do move the map a tiny bit, but don't zoom; Network tab shows successful request on click.

Let's get this retested before our upcoming sotm / foss4g release alpha.

It looks like if the shape of the searched entity is too large (i.e. a very large relation, admin boundary for a county etc) then it doesn't get displayed until the user zooms in.
That said, the map will zoom to the feature in question now- tested on oslo, tokyo, rapid city SD.


[FEAT] Revamping whole About Us Page to help Grab Attention to it.

Issue: Revamp About Us Page for Improved Engagement and Readability
Description:
The current About Us page needs a complete overhaul to enhance user engagement and improve readability. The revamped design will make it visually appealing and easy to navigate, ensuring visitors can quickly grasp the key messages.
Sections to Revamp:

Our Mission

Refine the wording to clearly articulate our mission.
Use engaging visuals or icons to emphasize key points.

Our Vision

Rewrite the vision statement to resonate more with our audience.
Consider adding a visual representation of our future goals.

What We Offer

Highlight our services or products more effectively.
Use bullet points or infographics for better clarity and impact.

Why Choose Us

Create a compelling case for why users should select our services.
Incorporate testimonials or statistics to reinforce our value proposition.

Our Team

Provide engaging profiles for key team members, including photos and brief bios.
Make it more personal by adding fun facts or quotes.

Goals:

Increase user engagement on the About Us page.
Enhance readability and comprehension of our core messages.
Ensure consistent styling that aligns with our brand identity.
Improve accessibility for all users.

Current Page

References:

this is just a demo, I will implement these features according to the UI design and context of the StationGuide

https://github.com/user-attachments/assets/2cd2a1ed-c8a2-480f-b893-6e6a877ce646
Are you participating in GSSoC?

[x] Yes
[ ] No

I can deliver it in around 1 day.


500 Internal Server Error

We are using NuGet.Server v<IP_ADDRESS>. During startup the server returns "500 Internal Server Error" to every client which wants to access the nuget server. The Server needs about a minute to start up.
I did disable FileSystemMonitoring in Webconfig and set initialCacheRebuildAfterSeconds =1. Now the "500 Internal Server Error" is returned for only about 10 Secondes.
Is this by design or a bug? Everyone thinks the server is broken but it is only waking up.

Iam getting following Stracktrace while debugging or making an request from localhost
<m:message>Exception has been thrown by the target of an invocation.</m:message>
<m:type>System.Reflection.TargetInvocationException</m:type>
<m:stacktrace> at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Web.Http.OData.Query.ODataQueryOptions.LimitResults(IQueryable queryable, Int32 limit, Boolean& resultsLimited) at System.Web.Http.OData.Query.ODataQueryOptions.ApplyTo(IQueryable query, ODataQuerySettings querySettings) at NuGet.Server.V2.Model.QueryResult1.ExecuteQuery(IQueryable1 queryable, ODataQueryOptions1 queryOptions) at NuGet.Server.V2.Model.QueryResult1.GetInnerResult() at NuGet.Server.V2.Model.QueryResult`1.d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()</m:stacktrace>
-<m:internalexception>
<m:message>This operation is not supported for a relative URI.</m:message>
<m:type>System.InvalidOperationException</m:type>
<m:stacktrace> at System.Uri.GetComponents(UriComponents components, UriFormat format) at NuGet.Server.Core.DataServices.PackageExtensions.AsODataPackage(IServerPackage package, ClientCompatibility compatibility) at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator1.MoveNext() at System.Linq.Buffer1..ctor(IEnumerable1 source) at System.Linq.OrderedEnumerable1.<GetEnumerator>d__1.MoveNext() at System.Linq.Enumerable.<SkipIterator>d__311.MoveNext() at System.Linq.Enumerable.d__251.MoveNext() at System.Linq.Enumerable.<TakeIterator>d__251.MoveNext() at System.Collections.Generic.List1..ctor(IEnumerable1 collection) at System.Web.Http.OData.Query.TruncatedCollection1..ctor(IQueryable1 source, Int32 pageSize) at System.Web.Http.OData.Query.ODataQueryOptions.LimitResults[T](IQueryable`1 queryable, Int32 limit, Boolean& resultsLimited)</m:stacktrace>
</m:internalexception>

This behavior exists since v.<IP_ADDRESS>. V 2.14.2 was working fine

Could you check the icon URL, license URL, or project URLs of the packages in your feed? A minimal repro with the broken package(s) would help. Feel free to prune the .nupkg of any private information like .DLLs. I think the only part of the package that could cause this problem is one of the URLs in the .nuspec.
This code looks to be throwing the exception. My best guess is that a relative URI is somehow making it into the server and then failing to be displayed like this:
https://github.com/NuGet/NuGet.Server/blob/97e3d99ca143dc1f48da54f7a1646de6e4b7cd01/src/NuGet.Server.Core/DataServices/PackageExtensions.cs#L27-L29

hello Joel,
Thanks for the quick reply. I did some tests.
We just use . We use Icons on unc fileshare and they are displayed in nuget client.
//fileserver/Framework/NuGet/server.png
I did change the URL to http://code.google.com/p/autofac/logo and the server is starting up fine.
Can this please be fixed in the nuget server or should we change all existing packages?

I need to investigate more about the root cause and play with UNC URLs in NuGet.Server. I'll respond back to this issue when I know more.

Thanks a lot. I did also notice that some pictures have been deleted on unc share. In my tests there was no difference between deleted or available pictures on the fileshare.

I tried both of these formats locally:
//fileserver/Framework/NuGet/server.png
\\fileserver\Framework\NuGet\server.png

Both worked for me and were mapped to the form:
file://fileserver/Framework/NuGet/server.png

Could you determine the version of .NET Framework that you are using on the server hosting NuGet.Server?
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed
Also, how are you pushing your packages to NuGet.Server? Are you dropping them in the package directory or are you pushing them from command line, e.g. nuget.exe push?
Could you check the *.cache.bin file (it's JSON) and see what the "IconUrl" property says for the affected package(s)?
Also, could you try making a simple console app like this and run in on the machine hosting the NuGet.Server?
using System;

namespace ConsoleApp1
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine(new Uri("//fileserver/Framework/NuGet/server.png")
                .GetComponents(UriComponents.HttpRequestUrl, UriFormat.Unescaped));

            Console.WriteLine(new<EMAIL_ADDRESS>                .GetComponents(UriComponents.HttpRequestUrl, UriFormat.Unescaped));

            Console.WriteLine(new Uri("file://fileserver/Framework/NuGet/server.png")
                .GetComponents(UriComponents.HttpRequestUrl, UriFormat.Unescaped));
        }
    }
}

Hello
We are testing  to migrate the Nugetserver from  2.8 to Version 3.3.3. For Migration  all Packages are file copied into the new local. After that the build uses the push command. The error occurs only while the server is starting up. After a couple of seconds it is working fine. Anyway the clients who first access the server will get the error
I can reproduce the error on our server and my devmachine they both use .NET Framework 4.7.2
I did further tests and the error occurs only with / and not with . I did also check with fileshares on different machines.
Working
\probackup2012\TFS_VS_Customizing\NuGet\PROFX_server.png
Cachefile:
"IconUrl":"\\probackup2012\TFS_VS_Customizing\NuGet\PROFX_server.png",
not workuing
//probackup2012/TFS_VS_Customizing/NuGet/PROFX_server.png
Cachefile:
"IconUrl":"//probackup2012/TFS_VS_Customizing/NuGet/PROFX_server.png"
The result of your code is
file://fileserver/Framework/NuGet/server.png
file://fileserver/Framework/NuGet/server.png
file://fileserver/Framework/NuGet/server.png

Sorry for the late reply. The Uri is relative during server startup. I can reproduce it with following code:
           Console.WriteLine(new Uri("//fileserver/Framework/NuGet/server.png",UriKind.Relative)
                .GetComponents(UriComponents.HttpRequestUrl, UriFormat.Unescaped));

I did following fix on dev machine and will push it to dev Environment
public ServerPackage(IPackage package,PackageDerivedData packageDerivedData)
        {
 Id = package.Id;
            Version = package.Version;
            Title = package.Title;
            Authors = package.Authors;
            Owners = package.Owners;
           // old IconUrl = new Uri(package.IconUrl
            IconUrl = new Uri(package.IconUrl.ToString(), UriKind.Absolute);

The rootcause should be the Package in Nuget.core. Iam not sure if my fix is a good fix

The rootcause should be the Package in Nuget.core. Iam not sure if my fix is a good fix

I like your fix a lot actually. NuGet.Core is very old repository for us so we do minimal changes in that area. We have done other workarounds in NuGet.Server to make up for NuGet.Core limitations so this seems very reasonable.
I'll take a look a little deeper because I did a superficial investigation into NuGet.Core last week and got the impression that we should be parsing such URLs as absolute all the time. I must have been mistaken.

Thanks for the explanation my knowledge about the nugetprojects is very limited.
I guess the fix has to be applied also to licenseurl and projecturl as well.

Did publish the fix to the developer nugetserver. Seems running fine . Will observe it for a couple of days.
Would be great if will be fixed in the product.

I was able to reproduce the issue. Turns out I was misunderstanding your original steps and was only testing the case where a new package is pushed to the server after startup, not the case when the package is already pushed and the server is reading the information from the cache.
It looks like things behave inconsistently for URLs of the following shape:
//fileserver/Framework/NuGet/server.png

The problems seems to lie in how we deserialize the JSON cache file. We use Newtonsoft.Json to deserialize the URL properties into type Uri. I dug into the Newtonsoft.Json source and found this line:
https://github.com/JamesNK/Newtonsoft.Json/blob/cdf10151d507d497a3f9a71d36d544b199f73435/Src/Newtonsoft.Json/Utilities/ConvertUtils.cs#L478
Newtonsoft.Json is using new Uri(input, UriKind.RelativeOrAbsolute). In a simple console app, I was able to confirm that this yields a relative URI for UNC paths. The strange part is that new Uri(input, UriKind.Absolute) yields an absolute URI for the same input string.
We assumed we could safely round trip a Uri through Newtonsoft.Json using the default serialization settings. I filed a bug about this on Newtonsoft.Json's repo but we should workaround the issue on our own:
https://github.com/JamesNK/Newtonsoft.Json/issues/2128
Here is a PR with the workaround:
https://github.com/NuGet/NuGet.Server/pull/87
Could you connect to this feed and try a prerelease build with this change?
Feed URL: https://dotnet.myget.org/F/nuget-build/api/v3/index.json
Package ID: NuGet.Server
Package Version: 3.4.0-jver-abs-2935664

Thank you. I did download the nuget and its working fine.

NuGet.Server 3.4.1 is released with this fixed.
https://www.nuget.org/packages/NuGet.Server/3.4.1


Tern server opened in wrong project folder

I had two project directories open in tree view. The second project has the .tern-project file and the js file I was working on. I was getting the no autocompletions from the plugins. I tried restarting the tern server but it had no effect.
So, I closed the first project directory and restarted the tern-server. Now I was able to see autocompletions from the plugins.
I think the fix should be consider the path of file open in activeEditor if there is one while restarting the tern server.
Sorry, for my bad english (non-native english speaker).

Hey,
Yes. Supporting multiply projects is on the todo list :)
Thx for reporting.
tststs

Thanks for the quick reply. On a side note, after I press writing tab to write another function parameter, the cursor doesn't leave a space after the comma. It is kind of annoying to insert it manually.
And thanks for the plugin I waited this for so long. I just discovered this recently.


Prepare for 2.0 release

Resolves #72
Still to do:

[x] Implement MonadAsk / MonadTell - #63
[x] Figure out what needs to happen with #60

I'll finish up tomorrow, unless anyone beats me to it.

As far as I can tell, ExceptT needs to have Apply implemented as ap so that the behaviour is consistent with bind, but this does mean that we have a Monad m constraint from Apply downwards now... but, I've just realised that the change I made to MaybeT to loosen the constraints suffers from the very problem I just fixed for ExceptT.
I'm not sure what to suggest, since it seems like this the right thing, since the difference is this: the m is run regardless of whether the value is Nothing / Left in the apply case, but not in the Monad case. Maybe there's some way to make bind behave the same as apply instead, but I'm not really sure what that means, and it might have negative consequences.
Without the looser constraints we can't have MonadPar instances for MaybeT and now ExceptT it would seem, but then maybe that is correct, since they "don't work properly" in parallel?

Maybe the answer is to use the Monad constrained versions and provide custom applicative newtyped versions for MonadPar?

Does it make sense to break up ComonadEnv and ComonadTraced too? What are examples of monads which have ask but not local etc.?

Why not
apply (ExceptT f) (ExceptT x) = ExceptT (lift2 ($) <$> f <*> x)

?
Do you mean they're not equal in terms of what gets evaluated? True, but they're observationally equivalent, right?

That is how I changed apply for MaybeT, and how it was for EitherT - that exact implementation is what #60 complains about.
Honestly I have no idea, I stared at it for quite a long time trying to figure out whether the extra m running mattered or not.

What do you mean when you say the m is run?

I mean, with the apply version the effects occur for both sides regardless of whether the left fails or succeeds... right?
I was going to put something together to try and prove whether it matters or not, but haven't gotten around to it yet.

(Trying now)

A good test would be something like forever in the MaybeT (Eff _) monad, I think.

It sounds like there is an issue, but we can probably fix it with a newtype, either here (preferable) or in parallel, but I would really like to be able to implement MonadPar for something related to ExceptT and MaybeT.

main :: Eff (console :: CONSOLE) Unit
main = do
  void $ runMaybeT $ f <*> a
  log "---"
  void $ runMaybeT $ ap f a

f :: forall a. MaybeT (Eff (console :: CONSOLE)) (a -> a)
f = do
  lift $ log "Hello"
  MaybeT $ pure Nothing

a :: MaybeT (Eff (console :: CONSOLE)) String
a = do
  lift $ log "LAUNCH THE MISSILES!"
  pure "foo"

Hello
LAUNCH THE MISSILES!
---
Hello

We can definitely define newtype(s) with the desired applicative behaviour, with the caveat that they'll behave in the above way. I think the example above settles the discussion over whether the ap approach is right or not here though, unfortunately.

Sounds good

I'd vote for putting those newtypes in Parallel, as they're probably not going to be that useful on the whole outside of that situation. Given that, I think this PR is done sans any further comments.

I'm fine with putting them in parallel. Can we add ComonadTell though? It will be necessary to break things up in my pairings and day libraries when I implement a MonadTell instance for Co w.

That's supposed to come out of ComonadTraced right? It might need some refactoring if so, as it's already only made up of one function: track :: forall a. t -> w a -> a.

Ah ok, interesting. Sounds good then.


doc: update Recommended usage conventions for karmadactl, and fix a t…

…ypo in configure-controllers document
What type of PR is this?
/kind documentation

What this PR does / why we need it:
If the documents are updated, users can more easily find the karmadactl interpret --operation ReviseReplica section.
Which issue(s) this PR fixes:
Fixes #347
Fixes #3401
Special notes for your reviewer:
@Poor12

Note that karmadactl needs to be based on the latest kube library.

/lgtm


Never show non-taxon things as taxon

It seems like we have been showing the step by step pages with the taxon layout recently. I think this is caused by the DocumentTypeRoutingConstraint not finding the content item temporarily, and thinking it's a taxon (the fallback in the routes).

By crashing we 1) get insight into the error, 2) Fastly will serve the previous (correct) page from the mirror, instead of a wrong page.

@tijmenb Heads up - this can cause time sensitivity issues with unpublishing (which is revealed through end-to-end tests).
If we have the situation where we have an unpublished a taxon and the router and content store aren't in sync this will return a 500. Will probably need to embrace ability to return gone and redirect here to make this resilient like we have in government frontend: https://github.com/alphagov/government-frontend/blob/master/app/controllers/content_items_controller.rb


Compare mode crashes after 1st scan

Compare mode crashes after 1st scan, bringing me back to the empty compare mode screen
https://user-images.githubusercontent.com/1689815/128891462-18d2e5e6-d97d-4cd0-bf8e-ea2fe2957ee1.mp4

Any stacktrace? @teolemon

Had the same behavior, no any crash in logcat
https://openfoodfacts.slack.com/archives/C02L15QLA/p1628512324026900

will try to investigate


Update USAGE for setting language and API in batch command

Current coverage is 78.29% (diff: 100%)

Merging #107 into master will not change coverage

@@             master       #107   diff @@
==========================================
  Files            35         35
  Lines          1184       1184
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            927        927
  Misses          257        257
  Partials          0          0

Powered by Codecov. Last update b59fa7e...00c9c10

LGTM


STYLE: Use ITK_UNEQUAL_OPERATOR_MEMBER_FUNCTION in Modules/Core

Replaced hand-written definitions of operator!= member functions by
ITK_UNEQUAL_OPERATOR_MEMBER_FUNCTION macro calls, in Modules/Core.
Did some minor adjustments to corresponding operator== member
functions, where necessary, and removed non-const operator overloads.


Configure Git link broken in setting started manual

I was going through the ARFC website, and in the getting started guide the 'configure git' link sent me to a page not found error.
I'm submitting a ...

[x] bug report
[ ] feature request
[ ] question

Expected Behavior
when clicking on the link you go to a setting up page.
Actual Behavior
when clicking on https://swcarpentry.github.io/git-novice/02-setup/ you go to a page not found.
How can this issue be closed?
The link gets fixed

Thanks for the bug report @nglaser3 !! I think the link to fix this issue is https://swcarpentry.github.io/git-novice/02-setup.html . The carpentries recently redid their lesson design so now the URL has changed slightly.

Addressed in #296


Unbreak haskellPackages.rapid

Rapid version 0.1.5 has it's base dependency bumped to <4.18.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

Cherry-picked as https://github.com/NixOS/nixpkgs/pull/272097/commits/66ea46be076e4ea891d2c647b53701c12dae46ea.

We don't have 0.1.5 in haskell-updates yet. This should probably have waited for the next Hackage bump?

@ncfavier I guess! Is there another branch where all these types of changes are collected?


DCOS-40673: prevent header bar from overlapping popup-like ui

A recent change to the header bar's z-index caused it to overlap UI such as modals and tooltips
Closes: DCOS-40673
Testing
Go to the "Services" view
Hover the "+" button for adding a service
Click the "+" button to open the modal flow for adding a service
Ensure the header does not overlap the tooltip that appears on hover or the modal that appears on click
Trade-offs
If you click too low on either of the dropdowns in the header, your cursor will be over the dropdown menu while it's animating in, causing the dropdown trigger to very briefly lose it's :hover style. If this is a blocker, I can continue to investigate a solution
Dependencies
None
Screenshots
Before:

After:

Tagging @leemunroe since he filed the ticket

:tada: This PR is included in version 2.14.0 :tada:
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.13.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tutorial thumbnail popovers should be removed

The popover texts seem to be based on the raw ("un-processed") input, so for the devel docs I get e.g.:

And for the stable docs the CSS seems to be broken:

Besides, for those tutorials where I don't see such layouting issues, the provided information is not helpful to me at all as it's just too little text. If we want more info, we should amend the captions of the thumbnails.
Besides, I don't like stuff jumping all around on my screen as I move the mouse cursor over it anyway, it's irritating; and it hides content.
So my vote is clear – let's get rid of those popovers entirely, and potentially amend the captions.
@drammock WDYT?

The content for those is drawn from the first sentence of the tutorial text. I agree it is of limited use. At some point @larsoner had done some magic in sphinx-gallery to make it "sanitize" those preview snippets so that backticks and tildes would not render, but it looks like it's not working in all cases anymore.  I have no objection to suppressing them. Can you see if there's a config option for sphinx-gallery that will just turn them off?

We can just set display none in the CSS for the class. It's easier than adding yet another option to SG

Sounds good to me!!


Enable SimpleRedirectAction to redirect to whitelisted external hosts

Not sure if this should go in as hotfix?

This behavior hasn't changed recently, correct? If not, I'd say the fix can probably wait for 20.3 unless we've received strong feedback that it's a high priority.


⚠ Secret Website 3 has degraded performance

In 104609f, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 28795 ms

Resolved: Secret Website 3 performance has improved in 88b3384.


Request Entity Too Large in v0.5.1

In version v0.5.1 starts a problem with Request Entity Too Large on save snapshot.

File "/home/airflow/.local/lib/python3.11/site-packages/evidently/ui/managers/projects.py", line 159, in add_snapshot
    await self.project_metadata.add_snapshot(project_id, snapshot, blob)
  File "/home/airflow/.local/lib/python3.11/site-packages/evidently/ui/workspace/remote.py", line 206, in add_snapshot
    return self._request(f"/api/projects/{project_id}/snapshots", "POST", body=snapshot.dict())
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/evidently/ui/workspace/remote.py", line 137, in _request
    raise EvidentlyServiceError(details)
evidently.ui.errors.EvidentlyServiceError: Request Entity Too Large

Seems it correspond to new version of litestar whitch has this new features and restrict it by default to 10Mb:

Workaround: need add a way to specify increase max request size (snapshots can be much more then 10mb).

Hi @oleg-savko
Nice catch! Thanks for it!
Would you like to contribute 😊?
Just add  request_max_body_size = None, to this file before **self.kwargs
I guess this is nice to have no limits by default in application layer (and good to have limits in other layers like proxy (nginx etc.))


[Translatable] TranslationFormBundle has problems with translation fallback

hi i am using a2lix/TranslationFormBundle,
but it does not support the translation fallback that was added later in this bundle.
might there be a way to make it working?
my first test was a new class that does implements ArrayAccess which does work as a wrapper returned from getTranslations, but it didn't work as i wanted yet.
it might not be fixed in TranslationFormBundle because it does use a PropertyAccess String and my Symfony version doesnt support Callable at that place yet.

I'm going through the old issues/PRs and closing most of them so we can focus on now.
This one is missing any feedback or reasoning so I cannot deduce anything from it.
Thanks for you though, but closing for reasons above.
If the bug still remains, please send failing test case to verify it. Only with test we'll be albe to help.


Allow barback to suppress secondary assets when the output subsumes them

 Issue by alan-knight
Originally opened as dart-lang/sdk#17843

For example, consider a transformer that sprites multiple images together to produce a single combined image. I may not want the original images to appear in the output.

 Comment by nex3

Added Duplicate label.
Marked as being merged into dart-lang/barback#17.

 Comment by alan-knight

Removed Type-Defect label.
Added Type-Enhancement label.

 Comment by lrhn

Added Area-Pkg label.


Begin error propogation

This PR is very focused on solving #93, but would also lay the groundwork for error propagation in support of #91 and #5.
I wish to "fail fast" if this method of error propagation is undesired, although I don't note anything controversial (avoiding another "second thoughts" re: #88). If this is approved I'll begin work on further error propagation.
In summary:

Matchbox gets a root level Error type.
The error library chosen is thiserror, to keep parity with the matchbox_server's error library.
WASM/Native Errors are configured in webrtc_socket/error.rs and enabled through cfg-directives (cfg-if would help here).

The error library chosen is thiserror, to keep parity with the matchbox_server's error library.

I'm open to suggestions here if you think there are better alternatives, though I do like thiserror.

WASM/Native Errors are configured in webrtc_socket/error.rs and enabled through cfg-directives (cfg-if would help here).

Feel free to add cfg_if if you want, it's something I've been considering anyway.
Definitely a big step in the right direction, though it doesn't completely fix #93, for me it still panics:
thread 'webrtc_socket::test::unreachable_server' panicked at 'send failed: TrySendError { kind: Disconnected }', matchbox_socket\src\webrtc_socket\native\message_loop.rs:66:72

Added a test for this in #99

Note: I'm ok with merging this even it doesn't completely solve #93

All potential signalling errors should be caught now


[Chat] The "Load more" button is present if  more than 50 messages.

Reproducible: always
Build found: 1.0.99
Preconditions
The "Car" app is opened
The user is a participant of the Journey
The chat is created
Steps to reproduce

Go to the "Chat" page
Go to journey chat
Scroll up the journey chat
Observe the result

Actual result
The "Load more" button is present if more than 50 messages.
Expected result
The oldest message must be shown when the user scrolls up without a button.
E.g.: "User story #45
Test case"
Labels to be added
"Bug" ("bug"), Priority ("pri: ")

Is also reproducible for following Environment: Redmi Note 9 Pro, Android 12.0.3, app version 1.0.140
User Story: https://github.com/ita-social-projects/Car-Back-End/issues/45


Transfer fees not shown in Mobile Wallet

On the mobile wallet the transfer fee doesn't show, which should be shown. Here is also an example how staking is shown, also no transfer fees shown.
Staking is shown as follows:

And when looking at the details, the fee is missing:

How the the staking and fee details are shown on Desktop Wallet:

This was fixed in the 1.0.9 release.


make relational grammar parser more consistent with protocol

For PropertyPointer instead of outputting null for class when the property is of embedded property mapping, we will output empty string. This behaviour will make this:

comply with the protocol
in sync with Studio
compiler more resilient

Closing this as after discussing with @pierredebelen, we might eventually decide to change the Pure protocol instead. Also setting the unset field to empty string seems like a code-smell.


Filters notification

The more I use it the more I fill filtering needs some improvements to the UX, to let the user clearly see what is currently viewed.In particular I fill the UI is not informative enough when filters are applied from menus of links, because the only clue for the user is the Filter button turning blue.
I would like to find a way to report active filters values, in a compact way. I think it would be more effective, but we need to think about a smart way to implement it.
Meanwhile an option could be report the number of active filters also inside the "# of resources" label, and make the "# filters" text open the filters panel.

@giohappy
The use of Resource found for needs to be localized and combined with 1 filter while adding an internal action to open the panel. This could cause complexity in the composition of translation.
My proposal is to separate the two translation Resource found for and for # filters using this formula:

resource found text
filter applied text (open filter panel)
clear filter as thrash icon with tooltip
change the style of badge

We could also try to remove the current buttons and add only a single button with the filter icon to open the panel when there are no filter applied

no filter applied


Improve exception handling in python bindings

Currently error codes are simply converted to python RuntimeErrors, whereas it might be more appropriate to throw some of them as ValueErrors based on the type of error status

Also consider adding more custom exception types for each binding to deal with their specific errors. Then update the documentation, tests and samples accordingly to highlight the proper usage of these APIs and exceptions.


Repositioning all the elements at once

Kind of like a select all type feature, where in conjunction with #116, we can scale and move all the elements on the canvas to fit exactly onto the background image layer to allow for easier note correction.

Started this in 443c0841f8639c82871047982c7ef306c5f9de3c.
Two issues:

Extremely slow, especially when there are a lot lot lot of elements, it takes a long time to move all of them. Potentially related to all the errors in the console.

The snapping causes the notes to be super messed up and not move uniformly.

No longer updating fabric.js


Add warning for navigate in cDM of app components

See #91

I was about to come and ask a question about something I think is related. Here's an example app: https://codesandbox.io/s/l728k05onm
If I go to / without logging in I expect to be navigated to /login and see the form, but instead the URL updates but nothing is rendered. Is this the same issue?

@chooban I had the same problem and i think that yes, using <Redirect> instead of navigate() worked properly

As Ryan mentioned in #91, changing your code to:
const Authorizer = ({ Component, ...props }) => {
  if (!loggedIn) {

     return <Redirect to='/login'/>;
  }
  return <Component {...props} />;
};

would do the trick 🎩 🐰


Added list of breaking changes

Docs Build status updates of commit 3e11802:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-8.1.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.1.0)

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

Docs Build status updates of commit ef1e45e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-8.1.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.1.0)

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


Refactored some functions and created tests

check what i have included in my code

hey @bevennyamande , I wouldn't call this refactoring as this will break the API, but if you're interested in trying some experiments with the Paynow SDK you can check out my clone of Paynow that supports both 2 and 3

why would you want to develop an SDK for python2 when soon it will not be supported, i didnt have a merchant key to test with but i made a pretty straight forward fork https://github.com/bevennyamande/paynowzw

why would you want to develop an SDK for python2 when soon it will not be supported, i didnt have a merchant key to test with but i made a pretty straight forward fork https://github.com/bevennyamande/paynowzw

It supports both 2 and 3 ;)


Prettier 3 and this plugin do not work as intended with Yarn 2 PNP

What version of prettier-plugin-tailwindcss are you using?
For example: v0.5.9
What version of Tailwind CSS are you using?
For example: v3.3.0
What version of Node.js are you using?
For example: v18.18
What package manager are you using?
For example: Yarn 2 with PNP
What operating system are you using?
For example: macOS arm
Reproduction URL
https://github.com/liamlows/Prettier-Issues
NOTE: uses yarn 2 with PNP and zero installs, all you should need to do is ensure corepack enable is run and run yarn to install unplugged dependencies.
Describe your issue
I've been battling this issue for a few weeks now and just got around to finally making a reproduction repo for it.
When attempting to load plugins via prettier version 3, they dont seem to work as intended. I use two plugins one being a import sorting plugin and the other being this plugin. If i try and provide the plugin as stated in the installation instructions for prettier v3, eslint/prettier will fail to load the plugin saying it cannot be found. This is the error ESLint spits out (and prettier when you run a force format):
[Info  - 12:42:11 PM] ESLint server is starting.
[Info  - 12:42:12 PM] ESLint server running in node v18.15.0
[Info  - 12:42:12 PM] ESLint server is running.
[Info  - 12:42:13 PM] ESLint library loaded from: [REPO_PATH]/.yarn/sdks/eslint/lib/api.js
[Error - 12:42:14 PM] An unexpected error occurred:
[Error - 12:42:14 PM] Error: Cannot find package 'prettier-plugin-tailwindcss' imported from [REPO_PATH]/noop.js
    at new NodeError (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:21374:5)
    at packageResolve (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:22354:9)
    at moduleResolve (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:22386:20)
    at defaultResolve (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:22473:16)
    at resolve (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:22490:12)
    at importFromFile (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:22505:16)
    at importFromDirectory (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:23186:10)
    at file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:23203:12
    at async loadPlugin (file://[REPO_PATH]/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/index.mjs:23208:28)
    at async Promise.all (index 1)

I first had this issue with the import sorting plugin but when i created an issue on their repo (https://github.com/IanVS/prettier-plugin-sort-imports/issues/140), I was provided with a easy fix. Simply unplugging the plugin and adding it to the plugins array in the prettier config with require.resolve(). That worked fine in isolation and format on save and linting worked fine, but the second I tried adding in the tailwind plugin it broke prettier's format on save. I also tried using the require.resolve() trick on the prettier plugin and it did make the cannot find error go away
Currently the repo linked above has it setup with require.resolve() and the linting works but formatting on save does not. If you remove the prettier-plugin-tailwindcss from the plugins array, it will work again and format on save.
I assume this is the correct place for this issue, however let me know if this also needs to be cross-posted to prettier or yarnpkg.
Thanks for any insight as to what the problem is!

So, I'm not able to reproduce this with the eslint extension in VSCode. However, when I installed the project it used Yarn 4 rather than Yarn 2 like the title suggests (it's set to 4 in the package.json file). So might be worth checking out if you're somehow using Yarn 2.
I can however reproduce a similar error with the Prettier extension in VSCode but I suspect this is actually an issue with either the Prettier extension or Yarn and not our plugin because it works from the command line without issue. I'm purely speculating here but I think it has to do with the fact that our plugin is ESM and that may not work well with Yarn PnP. I tried another plugin like Astro which is also ESM only and get a similar error when using just it.
On a holiday break right now but I'll take a closer look when back.

@thecrypticace sorry that was my bad! I meant to say yarn 4 and was saying yarn 2 in the sense that it was the type of yarn version/executable that lives in the project rather than globally on the system.
In regards to the plugin, I think you are correct. ESLint picks up and shows that the classnames are ordered wrong. It also shows this with other formatting issues. Take the following screenshot as an example:

As you can see there is a indent that is incorrect and two locations where classnames are out of order. If I hover over the yellow squiggly lines the quick fix hover window appears and I can manually fix the issue that way and it works.
The issue I am seeing is that when I enable this plugin, format on save and running format from the command palette (cmd+shift+p) no longer formats the file. The error I get when i run the format with prettier command from vscode is as follows:
["ERROR" - 8:47:32 PM] Cannot find package 'prettier' imported from [ABSOLUTE_PATH_TO_PROJECT]/prettier-issue/.yarn/unplugged/prettier-plugin-tailwindcss-virtual-9c74c069bc/node_modules/prettier-plugin-tailwindcss/dist/index.mjs
Did you mean to import prettier-issue/.yarn/unplugged/prettier-npm-3.1.1-072c31ec21/node_modules/prettier/plugins/angular.js?

So you may be right that the issue could reside with the vscode prettier extension, but it only occurs when this plugin is enabled. When I remove this plugin from the prettier config the formatting works automatically on save or when running from the command palette as expected.
I am also on holiday break for the next few weeks but I will try to monitor this thread and reply if anything is needed!

@liamlows I am running into the same issue on one of my projects. I'm using yarn 4 with pnp enabled, and I'm using the prettier vscode extension. As you noted, it's only an issue with the vs code extension enabled (have it set as my default formatter). However, if I remove the prettier tailwind css plugin, the prettier vscode extensions seems to works fine.. I have to unplug prettier, along with any other plugin I am using for it to work as well.
I thought maybe there needed to be a dependency or peer dependency specified in the yarn rc file? I have yet to figure it out so I've resulted in just using the cli temporarily.
I run format on save, and the output window for prettier will show me the exact error as you pointed above.
["ERROR" - 8:12:16 PM] Cannot find package 'prettier' imported from [ABSOLUTE_PATH_TO_PROJECT]/.yarn/unplugged/prettier-plugin-tailwindcss-virtual-27c5ce4149/node_modules/prettier-plugin-tailwindcss/dist/index.mjs Did you mean to import prettier-npm-3.1.1-072c31ec21/node_modules/prettier/plugins/angular.js?
Using the prettier cli in the command line works fine with the prettier tailwind plugin enabled.

I have this issue with yarn 4. This plugin breaks prettier "Format on save" and "Format document with..." command, although it works when prettier is ran from the terminal.

I encountered the same above mentioned issues with the VS code extension. When I add the plugin definition to my prettier config file Prettier stops working. I am also using Yarn 4 with PnP.

After nothing else worked, as a workaround I managed to get this working on yarn 4 by switching from PnP to the node_modules folder as described here: https://yarnpkg.com/configuration/yarnrc#nodeLinker

After nothing else worked, as a workaround I managed to get this working on yarn 4 by switching from PnP to the node_modules folder as described here: https://yarnpkg.com/configuration/yarnrc#nodeLinker

I have found this also works for me as well although due to our use of the novel "zero-installs" feature I cannot use it as a workaround for now since it requires PNP.
This makes me think that it could be a peer dependency issue or something along the lines of that. If it works fine when not in PNP, but breaks in PNP and prettier and plugins are installed unplugged then maybe a peer dep is not being install that also needs to be unplugged? I'll take a look at this later and see what I can find although im on vacation right now so a little tough.

If u using prettier v3 and prettier-plugin-tailwindcss v0.5:
cd ./node_modules/prettier-plugin-tailwindcss/ yarn install prettier

I ended up creating a "node_modules" at the parent directory and placed "prettier" and "prettier-plugin-tailwindcss" inside it. If I had put them directly into the project's node_modules folder, they would have been removed every time I ran "yarn install."

hmmm...
try using this version (working for me)
"prettier": "^3.2.5"
"prettier-plugin-tailwindcss": "^0.5.11"
and install this:
"prettier-plugin-svelte": "^3.1.2"

i'm still have this issue, writing tailwind classes without sort in so bad

Just an update from my end. We ultimately switched to PNPM and a monorepo for our projects and no longer have this issue. Now that we are using node_modules folders the issue has completely resolved itself. However, this is still an issue on my personal projects that use Yarn PNP.

the issue persists

Any progress? Creating node_modules in the Yarn PNP project isn't a good solution, I guess.

My temporary solution is to use a config file like this.
// .prettierc.js
module.exports = {
  singleQuote: true,
  trailingComma: 'all',
  tabWidth: 2,
  printWidth: 80,
  // Using import()
  plugins: [import('prettier-plugin-tailwindcss')],
};

With this config yarn prettier . command works fine.
But the problem is prettier extension in VSCode gets infinitely loaded.
(For more information on this, see prettier-vscode issue)
So I decided to temporarily replace "Format on save" with "format on pre-commit" by using husky.

I found a way to use this plugin with Yarn 2
First you type this command yarn unplug prettier-plugin-tailwindcss
Then you can find the directory start with prettier-plugin-tailwindcss-virtual- in .yarn/unplugged
Edit your .prettierrc like below lines
{
  "semi": false,
  "singleQuote": true,
  "plugins": [
    ".yarn/unplugged/prettier-plugin-tailwindcss-virtual-6a7c69ed2e/node_modules/prettier-plugin-tailwindcss/dist/index.mjs"
  ]
}

But I don't want to use this with specific path. Are there any good solution?

After an afternoon of searching, I finally found the perfect solution.
unplug the prettier-plugin-tailwindcss
yarn unplug prettier-plugin-tailwindcss

for the .prettierrc.cjs
module.exports = {
    plugins: [

        require.resolve('prettier-plugin-tailwindcss'),
    ],
}

details are here
https://dev.to/javien/how-to-use-prettier-plugin-with-yarn-pnp-in-vscode-4pf8


Abilities to use lr-mobile-config.js and lr-desktop-config.js

Hello,
First I would like to say this extension is really great, it is very convenient for us to be able to run lighthouse tests together with sitespeed.io test, and having the possibility to consult them in just one panel (html reports or grafana).
Actually only two profiles can be extended: default-config.js and full-config.js.
This issue is to sugger to add two more: lr-mobile-config.js and lr-desktop-config.js
So we can set like:
--lighthouse.extends lr-mobile
--lighthouse.extends lr-desktop
This way in combination with the --lighthouse.settings.emulatedFormFactor difference between desktop/mobile are best reflected.
I hope it makes sense.
Thanks!
Best regards

After some further test (please see: https://github.com/sitespeedio/plugin-lighthouse/issues/48), adding the possibility to use those 2 new profiles will be a really great things to achieve better result in same line of the results of Google Page Speed Insight.
In the meantime, is there a way to use custom profile or add those two file prrofile manually ? (as they are here: https://github.com/GoogleChrome/lighthouse/tree/master/lighthouse-core/config)
Thanks.

I can review and test a PR for that, it needs to be implemented on our side if I understand correctly see
https://github.com/GoogleChrome/lighthouse/blob/master/docs/configuration.md#config-extension


Prettier show for Colon

Currently:
julia> @varname(x[:,1])
x[Colon(),1]

On this branch:
julia> @varname(x[:,1])
x[:,1]

Seems like the latter is preferable, and will make a lot of downstream printing much nicer, e.g. chains obtained in Turing.
Only potential issue is that people might have code that access elements in a chain, etc. using Colon() in the string-rep, so maybe this should be a breaking release?

I'll make it a breaking release.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 83.051%

Totals

Change from base Build 854623890:
0.6%

Covered Lines:
49

Relevant Lines:
59

💛  - Coveralls

Eehh maybe we should require tests to pass before merging here too? The tests are now failing (I forgot to rename some stuff in the tests).

@torfjelde sounds like a good idea. Where can I activate that?


ATB-233: Added permission to QueueKmsKey resource so that SNS can access key and send undeliverable SNS messages to the UserAccountDeletionTopicDeadLetterQueue

Proposed changes
Give SNS permission to access the QueueKmsKey so that it can send undeliverable messages to the UserAccountDeletionTopicDeadLetterQueue.
What changed
Permission was added to the QueueKmsKey resource to allow SNS to access this key.
Why did it change
The UserAccountDeletionTopic is not sending to the UserAccountDeletionTopicDeadLetterQueue messages which it cannot deliver to the DeleteUserServicesFunction because it does not have permission to access the QueueKmsKey.
Issue tracking

ATB-233

Checklists
Testing
https://user-images.githubusercontent.com/110468919/216605712-2d9fe9c5-7573-4916-90dc-d7771b9d11e1.mp4

I couldn't see a PR template so I copied the template from the di-authentication-account-management repo and simplified it. I hope that's ok.


Use an existing table?

This is more of a question than an issue...
Is there a way to use an existing table?
I wanted to keep the basic DynamoDB table managed directly by cloudformation (using CDK) and use OneTable for all the interactions with the table, handling GSIs, etc.
Is there a way to use createTable(), but pass in an existing minimal table?
The other way I can go about it is to use a custom resource and execute OneTable for the table creation and removal, then import the table for other resources to reference it. Would that be a better way of doing it?
Thanks!

Sure, all you need is a schema and call the Table constructor. In fact, this is the normal mode of operation.
You don't (and shouldn't) call createTable for an existing table. createTable is really for dev and test time testing.


Autolimits for plots

Find out why the automatic limits cut of parts of the wavefunction.

Forgot to transpose the wavefunctions array


Add aggregate job for a forthcoming nixpkgs-darwin-unstable channel

@TikhonJelvis FYI

This looks great. I'd be happy to help with the nixpkgs-darwin-unstable channel.

Why do we need a separate channel for Darwin?

nixpkgs-unstable doesn't really test things that matter to Darwin users and this paves the way towards more formal darwin-nixpkgs releases (like we have on NixOS). Is there a better way to do that? Ideally we'd have some sort of cross-platform task force for nixpkgs releases, but I think most Linux nixpkgs users are already on NixOS...

It would be better to add this to the nixpkgs-unstable channel, unless we expect this job to be broken for extended periods of time. That way, people who need both Linux and OS X builds (e.g. in Hydra jobsets) can depend on a single Nixpkgs tree.
The OS X builds should not be included in the NixOS jobsets, however.

Are you assuming that Linux is generally going to be less broken than Darwin, so it's unlikely for Linux stuff to hold up Darwin channel releases?

I'm curious though: if we decided we wanted to have a release of nixpkgs that we assert works well for Darwin users (and are willing to maintain), what would that look like?

I agree with @edolstra, let's make these part of nixpkgs-unstable and have us macOS users watchdog those packages.

My experience with using the current nixpkgs-unstable on OS X is that it breaks more often than the Linux/NixOS packages and that OS X issues are fixed on a different time scale than Linux/NixOS issues. (This includes both OS X-specific patches on our end and upstream issues.)
I think there are enough platform-specific issues that separating the two channels will let each one fix platform-specific issues quickly, without being blocked on the problems specific to the other platform.

In particular, packages I depended on were broken for extended periods of time after being included in nixpkgs-unstable. I would be happy if nixpkgs-unstable only included packages that at least built correctly on OS X, but that might slow the channel down as a whole.

@domenkozar @edolstra I think it's more about disentangling the two concerns, as @TikhonJelvis suggests:

We could add several more jobs to nixpkgs-unstable, but then if something on the Darwin side breaks, it holds up Linux channel release
We fundamentally (and for the foreseeable future) have a much smaller work force on Darwin than we do on Linux, so fixing those things is almost guaranteed to be slower
So if we stick more jobs into nixpkgs-unstable, we'll likely have more Linux users breathing down our necks about broken builds, which is good for awareness but if we have a fundamental limit on person-hours to contribute, the channel will still be slowed down by macOS's jobs
macOS users still want a reasonably well tested channel where they can expect stuff to work. I doubt they care about it being super recently up to date (so e.g., if the last time all jobs passed was a month ago, that isn't the end of the world), but stuff should work.

To put it another way, Linux users always have NixOS releases they can pin to if they want stuff that works. macOS users have no such thing, so either we start making periodic nixpkgs releases for macOS, or we have a rolling release with lots of jobs, specifically geared at macOS. Does that make sense? I don't know how else to give Mac users a good experience here, but I'd love suggestions.

@copumpkin @edolstra I think we have to be very careful fragmenting our community. I am obviously biased here, someone who uses macOS and Linux for many different environments nowadays.
I'm very much for having nixpkgs (macOS/Linux) channel with lots of tests that stop the update on failures.
Since we already have NixOS stable channels that get security fixes, I would add macOS support for them. I think we have enough infrastructure to get that going, including enough macOS users.
TL;DR I'm for 1.

It's not about fragmenting the community though, right? The two "fragments" would be working on the same code in the same branch, but optimizing for different concerns. You personally might be in favor of blocking nixpkgs-unstable for two months due to macOS failures, but I can guarantee that a fair number of Linux users here who track that channel will be annoyed at macOS holding them up, and understandably so, because there's no fundamental reason that a Linux user shouldn't get a newer version of a package just because that new version introduced a slight incompatibility with Darwin that we haven't had time to patch yet.
All having two separate channels means is that the notion of "in a good state" is different across different subcommunities within the project, all working on the same codebase. It's the same reason we have nixos-unstable vs. nixpkgs-unstable: nixos-unstable adds additional VM tests and such that don't really mean much to non-NixOS users but that the NixOS community cares about. Contributors to both still work on the same codebase with a shared goal of improving nixpkgs.
All this Darwin channel would do is add another independent pointer into the branch history of our master branch. All code/fixes for both channels would still go into the usual staging/master branches, so there's no meaningful fracturing of code effort, just a meaningful separation of user experience. All a separate channel does is allow different sets of users different "views" of the same history.

@copumpkin that's very helpful.
I see where the motivation comes from now, but I wonder if separating channels is still the right cure.
If a commit breaks Linux OR macOS channel update, it should just be reverted.
Having two channels will encourage breaking other platform, since it won't be blocking your platform.
I wonder if following is not good enough:
a) add more tests/packages required for channel to pass
b) using CI, revert commits that break them

Yeah, in principle I think that makes sense, and I'm definitely not sure that a channel is the best solution.
My fear is just the practice of it, given the way we work on the project. Often someone just wants to quickly bump a version of some tool/library, tests it locally on their own platform, and pushes it up. If I had a reasonable proposal to let a Linux user test on Darwin, I'd feel better about being "strict" about this sort of thing, but here's the scenario I fear:

Linux user A pushes random update to package P
Mac user B uses P on a daily basis and points out that the new version of P is now broken on Darwin
A tries some speculative fixes, trying to coax Hydra to build a new version properly on Darwin, but with feedback loops of several hours, it's pretty frustrating and doesn't get very far.
B does not have the skill to fix P (on average this is true; we have comparatively few actual maintainers of nixpkgs on Darwin), but is now sad that the package no longer works.

Now have two options:

We revert the update A made, which is sad for the community as a whole (and A will probably be frustrated after wasting time on it), but fixes B for now. Perhaps the revert could include a comment warning the next person to come along against updating without testing on Darwin. But even then, it's fairly rare for a Linux user to have access to a Darwin box to test on, so the comment might ask you to test on both systems but it's hard to.
We leave the update A made in place but tell B to pin nixpkgs against an older version that still works. A and B will now be on different versions but will both have working software.

TBC, I don't really like either solution, but #2 feels less disruptive to users, and gives them an out. There's nothing stopping people who want or need to ensure that they have consistent versions on both Linux and Darwin from using the same channel on both, but now there's a "I'm just a semi-casual nixpkgs user on Darwin and really just want my packages to work reliably" option for Darwin folks as well. It's not quite a nixpkgs-YEAR.MONTH, but it's a step in that direction, I think.

being "less disruptive to users" is very subjective given that:

a) it encourages for user A not to care about user B, resulting into the culture of "it works for me on Linux"
b) moreover, it pushes macOS users into full-on catch-up game. Given that we have lots of Linux users, it's a lot of work
c) you can pin nixpkgs to a specific commit now already and I encourage anyone to do it
d) you would essentially adding more and more packages to block the darwin channel, but you will never be able to please everyone except for requiring all darwin packages to pass (which in turn would really need a better CI for pull request testing and extremely good team of playing the catch-up game)
I think your arguments are good @copumpkin, I'm just trying to see what issues will come up going this path. Sometimes a solution to a problem brings up more problems on the long run.
I guess the question we should ask ourselves is:

can we define a minimal set of packages that are required to work
can we make sure if a change breaks, we track who/what broke it can act in timely matter

Except it's questionable whether user A should care about user B, or even if it's possible to. "it works for me on Linux" is inevitable given our current technologies, and I don't even think it would be right for us to encourage our developers in general to think otherwise right now

Right now they can really just merge code to master and wait for Hydra to report successful or unsuccessful Darwin build.
In future we will hopefully have a CI that can test PRs for all platforms. Then comes the decision if something breaks macOS if it should be merged.

I don't think this is true. After all, we don't have all linux packages blocking the unstable channel. And darwin users are by and large very reasonable and understanding that darwin support is by necessity a second-class citizen.

Exactly, but a separate channel would only depend on jobs passing or not. Otherwise it's the same as nixpkgs-unstable.
Ideally we would have a better way to communicate when channel is blocked, given the amount of macOS users these days, I don't think it should be an issue.
Even better would be if we could parse Hydra tested job, to see how many times darwin was the blocker and for how long.

Right now they can really just merge code to master and wait for Hydra to report successful or unsuccessful Darwin build.
In future we will hopefully have a CI that can test PRs for all platforms. Then comes the decision if something breaks macOS if it should be merged.

This is definitely not enough. It's way too long of a feedback loop and too hard to test changes (you can't e.g. just run a single command and see what it does)

Exactly, but a separate channel would only depend on jobs passing or not. Otherwise it's the same as nixpkgs-unstable.

Right, but my point is that the darwin users will be reasonable about what they put in there.

Anyway, if we're actually OK with putting these jobs into nixpkgs unstable and maintaining that promise to darwin users then the immediate need is solved, but I suspect it will just cause frustration and delays for linux users at little benefit above a separtae darwin channel.

Some questions

Should Nix default to the nixpkgs-darwin-unstable channel on OS X?
Should nixpkgs-unstable include Darwin builds?
Should nixpkgs-darwin-unstable include Linux builds?
If I have a Hydra jobset that I want to test on both Linux and OS X (like Nix or patchelf), should I now include both nixpkgs and nixpkgs-darwin as jobset inputs?

Should Nix default to the nixpkgs-darwin-unstable channel on OS X?

I think so, yeah.

Should nixpkgs-unstable include Darwin builds?
Should nixpkgs-darwin-unstable include Linux builds?

I can see these going either way. Probably a good start would be to say no to both (except the tarball in nixpkgs-darwin-unstable but if nixpkgs-darwin-unstable (which will almost certainly lag behind nixpkgs-unstable) turns out to regularly be super broken on linux we may want to change this (so e.g. groups can peg the same nixpkgs rev on darwin and linux based on the channel)

If I have a Hydra jobset that I want to test on both Linux and OS X (like Nix or patchelf), should I now include both nixpkgs and nixpkgs-darwin as jobset inputs?

I think the answer to this is the same as whether you test against both unstable and 17.03. But I'm not completely sure.
@copumpkin thoughts?


Update label component to include sizes

Update label/legend component to include different sizes, or have label component options that use Heading stylings (for cases where the label will be the H2 of the page - as seen in the second image below)

Needs discussion with devs regarding accessibility concerns before implementing.

Resolved as part of recent changes.


chore: bumps sdk version to 2.2.1

:tada: This PR is included in version 9.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 9.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Updated homebrew-php

josegonzalez/php was transferred as homebrew/php a long time ago.

Thanks :+1:


Some jobs cannot be cloned

Some legacy jobs cannot be cloned

Due to some jobs don't have namespace, so can't get the config. PR #1561 fix it.


Typo in readme.md, develop branch

https://github.com/microsoft/ApplicationInsights-node.js/blob/develop/README.md
There is a small typo in a method name in a code snippet within the configuration section. Method setDistributedTracingMode is written incorrectly as setDistributedTracingTracingMode.

Fixed, thanks.

Fixed by #567


anulus versus annulus - use of alternative forms in MP terms

The following MP terms use the "anulus" variant in their primary term label:
abnormal aortic valve anulus morphology
abnormal pulmonary valve anulus morphology
abnormal mitral valve anulus morphology
abnormal tricuspid valve anulus morphology
In contrast, the following terms use the "annulus" variant:
abnormal sperm annulus morphology
absent sperm annulus
abnormal annulus fibrosus morphology
I suggest that we use "annulus" (more prevalent form) in all above terms and add "anulus" as a synonym for consistency with the HPO.

All relevant MP terms now use "annulus" in their primary label, with "anulus" added as an exact synonym.


Setup core transitive dependency

This PR does two things:

When developing the local core module is used to developer against the latest changes of core.
When publishing konfetti-xml and konfetti-compose the core module is pulled from the remote Maven repository. This way the pom refers to a remote copy of konfetti-core so that it works as a transitive dependency.

This is a follow-up on https://github.com/DanielMartinus/Konfetti/pull/290.
When building a release the core module needs to be pulled from the remote maven repository so that it can be included in the pom file. Other option was using fat aar to include core's files. Though what I read is that maintaining fat aar can be lots of work. One downside of this solution is that core always needs to be published first before publishing konfetti-xml and konfetti-compose.

@DanielMartinus I'm curious if you saw my comment here: https://github.com/DanielMartinus/Konfetti/pull/290#issuecomment-1040869971
The solution you have in this PR gets the job done, but it is adding complexity for something the maven-publish plugin is built to handle


Add the link for "How to see data retention policy"

Issue in ./help/technotes/data-retention.md
It would be nice if FAQ on this page https://experienceleague.adobe.com/docs/analytics/technotes/data-retention.html?lang=en contains a link to https://experienceleague.adobe.com/docs/analytics/admin/data-governance/gdpr-view-settings.html?lang=en with a topic "How to see/validate current data retention policy".

Hey @himanshu-pathak Can I do this?

@himanshu-pathak - here you go:
https://experienceleague.adobe.com/docs/analytics/technotes/data-retention.html?lang=en


[orc] update to 1.9.0

Library name
orc
New version number
1.9.0
Other information that may be useful (release notes, etc...)
The current usage file of the port also includes find_package calls to orc's dependencies. These should be replaced by find_dependeny()-calls in orc's cmake config file.

@Thomas1664
Please try #33077 to see if it works or not.

You can use following commands to get and apply patches and then install it.
curl -Ls https://github.com/microsoft/vcpkg/pull/33077.patch | git apply
vcpkg install orc

After this pr got merged, you may want to drop your local changes via
git checkout .
git clean -fd


Handle no data with graphType=pie

Display 'No Data' graphs for graphType=pie when there's no data.
Also, perform the same defensive tests before attempting to draw a legend with no elements that happens in LineGraph's drawGraph.
Added a few tests to cover this.

Codecov Report

Merging #2071 into master will increase coverage by 1.37%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master    #2071      +/-   ##
==========================================
+ Coverage   73.52%   74.89%   +1.37%
==========================================
  Files          79       79
  Lines        7652     7660       +8
  Branches     1496     1498       +2
==========================================
+ Hits         5626     5737     +111
+ Misses       1775     1663     -112
- Partials      251      260       +9

Impacted Files
Coverage Δ

webapp/graphite/render/glyph.py
39.69% <88.88%> (+7.6%)
:arrow_up:

webapp/graphite/render/views.py
68.86% <0%> (+1.88%)
:arrow_up:

webapp/graphite/tags/localdatabase.py
92.68% <0%> (+2.92%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ca156b...efdfff9. Read the comment docs.


Local CSS Imports

Hey there, I'm dealing with a legacy system so I've opted to use the IIFE version. However, It's now throwing the following error on my stylesheets containing local imports.
Uncaught (in promise) Error: (styles.css): Advanced beyond the end
Removing the imports resolved the issue and allowed the script to do its job once more. I can look into alternative methods to my CSS imports, but hopefully I can find a way to resolve this without restructuring everything.

Are you talking about @import? Because yes, I totally did not add support for that. Can you give me a small code sample that breaks?

I think I have a hint. Blocks when adding a ccs file with @import OR with :root {--whatever}. Then I have another problem: doesn't work with CSP, beacaus of blob:URL

So I tried to recreate this outside of my other environment and all seems fine with the import. I need to look more into this come Monday.
https://codepen.io/ThomasDaugherty/project/editor/AMQRLd

I managed to find a moment. So I've updated that pen above to include a quick toggle to help showcase the issue.
Success: good.css, Includes styling for the card module, Includes :root, Zero imports.
Failure: bad.css, Only imports good.css

I'm seeing the same problem with this when trying to include the IIFE. The only container query I've got on the page is included just before this script. You can see the error here: https://tim.ac-leo.com

This issue should be resolved by the latest version of the polyfill (currently in alpha). Please give that a try and feel free to open a new issue if you run into further troubles.
Thank you!


Disable SSL if hostname is set to localhost or host.docker.internal or <IP_ADDRESS>

(For self-hosted=true environments)

https://github.com/sequinstream/sequin/commit/be193b8a92acc31c20728fe34727f02e41eef50d


Visualization of CityGML 3.0 using 3D Web Client

Is there a way to export CityGML3.0 data in KML/COLLADA/glTF format using 3DCityDB?
If I get it right, according to the 3dcitydb-docs of latest version, 3D Web Client visualizes KML/COLLADA/gITF data exported from 3DCityDB by using importer-exporter tool. The tool supports CityGML 1.0 and 2.0, but not 3.0.
Now I see citydb-tool supports the import and export of CityGML 3.0. However, the 'citydb export help' command doesn't show the possibility of exporting data in KML/COLLADA/glTF format. How to make use of 3D Web Client in this situation?

Hi there, unfortunately there is no visualisation export in the Open Source code yet. We do not have a funding for implementing this so far. So, any contributions would be welcome here. An option might be the mapping of the new database schema onto database views following the old schema. Then, the current KML/COLLADA/glTF exporter would become usable. We already did some extensive experiments about this, but have not updated that code recently to work with the most recent beta version of the new DB schema.

It should not be too difficult to get the Open Source software "pg2b3dm" to run on the new DB Schema, but we did not try this yet. Check it here: https://github.com/Geodan/pg2b3dm. It does not support textured models, though.
A second alternative would be modify the Open source software "py3dtilers" to work with our new DB schema. But since this software has not been created by us, I cannot say how difficult this would be to achieve. Check it here: https://github.com/VCityTeam/py3dtilers. This software also support textures.
A third Open Source alternative could be to use the "plateau-gis-converter", a recently published powerful software that can convert the CityGML models of Japan into many other representations including 3DTiles (and textures). Currently it only supports CityGML V2, but since in Japan they are also moving towards using CityGML 3.0 I would expect that CityGML 3.0 might be supported in the not too far future.

Just in case commercial solutions are also welcome, my company Virtual City Systems offers tools for converting CityGML 3.0/2.0/1.0 into multiple output formats including 3DTiles (with textures, LoDs, implicit geometries, ...). And our tools already connect to new 3DCityDB v5 schema.
Also note that citydb-tool is not just a CLI tool but also offers a simple but strong Java API. This API lets you easily connect to the 3DCityDB v5 and load and export feature data. So, this API would be a good starting point for implementing a 3DCityDB to KML/COLLADA/glTF/3DTiles/whatever converter. Any contribution is welcome :-)

Thanks for the advice! I'll check the alternatives.


runtime folder missing

you forgot the runtime folder in the download.

I am amazed that I forgot to check that what was uploaded works - Sorry! I've replaced the download with a new one that does contain the runtime as well as the extract script.


Custom color for chat text

I was wondering if it would be possible to add a feature that allows users to change the color of the chat text. Currently, the chat text is green, but it would be great if users could choose between blue or white as well.
Thank you for your time and consideration.

Great suggestion. I'll get the feature release later today. Code block will be hard to customize. But chat messages should be easy.

The feature has been added to the latest package (v1.5.1). I'd appreciate a review of the extension marketplace. Many thanks
to use the feature:
Access settings in the conversation menu

The select the color scheme you wish to use:

Works Great, Thank you!
I have another suggestion. Could you please add an option to select a name for each Conversation.

It'd be very useful for those people who wants to keep history of chats.