feat(core): ability to compare two immutable structures

Hi Juan! First, thanks for this port :smile:
I thought it would be a good idea to implement the ability to compare two immutable structures, since using redux with immutable is a common pattern that tend to grow.
The only potential issue is that it require to add the immutable dependency, to both check if passed states are immutable iterables, and to compare them. But it shouldn't be too much of a problem, since redux-ava is supposed to be installed only in development anyway.
I've decided to deep-freeze only the action in case both states are immutables, since the previous state would be inevitably immutable.
Let me know your thoughts about this!

Any updates on merging this? Would love to see this feature in redux-ava, as Immutable.js is often the best choice in use with redux.

Hi! Sorry I've been super busy :-( I'll review this during my lunch and get back to you—adding a big dependency is always a hard choice but it looks like the benefits outweigh it. Thanks for your patience.

Hi @sotojuan, thanks for the merge!
Just to explain why I added the version field inside the package.json, was because I was installing the package using my specific url Apercu/redux-ava#immutable, and npm wasn't happy this field was missing, but could it be removed if you wish, since it's not a very common way to install.


fix: list only the sub directories if working directories are nested

The logic of list-targets will change.
A/
  tfaction.yaml
  B/
    tfaction.yaml
    modules/
      hello.tf

If A/B/modules/hello.tf is updated,

Before: CI is run in both A and B
After: CI is run in only B

https://github.com/suzuki-shunsuke/tfaction/releases/tag/v1.6.0-6


Port to Connexion 3 (WIP)

This is a work in progress to port Airflow to Connexion 3.
I believe I'm close to making the debugging app work. Then some more work will be needed to run it with an actual server.

Hi Robbe!
Thank you for magnificent work you have done here, now i have better understanding of what we are trying to archive here :D
As i understood you are close to finish the changes here. Please, tell me what i can do to help you in this one. Will be glad to help and support!

Also, i have checked that your changes are based on the old code from Apache Airflow. I think you need to rebase, because now there changes in master branch that affect your implementation: https://github.com/apache/airflow/pull/35488


Launching experiments in AzureML

Hi Chen-Hsuan,
Thanks for the great repo and a great piece of research! I think it would have even more impact if any user who wants to try it could launch training in the cloud, with automated hyperparameter sampling.
I have just made a PR which includes all the necessary infrastructure to be able to launch experiments in AzureML https://github.com/chenhsuanlin/bundle-adjusting-NeRF/pull/14. This should enable faster and easier experimentation with your code for anyone who might want to use it. Let me know if you have any suggestions of how to make the PR better.
Best wishes,
Stan

Hi @szymanowiczs, thanks for the PR!
Adding AzureML support sounds very nice. However, I'm not using AzureML at the moment and won't be able to verify the functionality of the PR. Also, I would prefer to keep the main branch as lightweight as possible with minimal overhead of using the code. I'm happy to mention AzureML support and link to your branch in the README, but I probably won't merge it into main at this time. Hope this makes sense to you!

All makes sense, thank you!


Drone0.7 can get repo list from gitlab.But always 401 with active repo.

I use drone:v0.7.Drone can login and get repo list success,but can not active repo,always 401.
Drone server log only one line 401 Unauthorize.
Environment:
mysql:5.5
kubernetes:1.7
gitlab:9.0

apiVersion: v1
kind: ConfigMap
metadata:
  creationTimestamp: 2016-03-30T21:14:38Z
  name: drone-config
  namespace: default
data:

  ################################
  # Drone Server (master) Config #
  ################################

  server.debug.is.enabled: "true"

  # You'll probably want to leave this alone, but you can point to external
  # DB instances if you'd like: http://readme.drone.io/0.7/manage/database/
  server.database.driver: mysql
  server.database.config: drone:drone@tcp(<IP_ADDRESS>:30008)/drone?parseTime=true

  server.is.open: "false"
  # CHANGEME: If you want to restrict access to a particular org, put the
  # name here.
  server.orgs.list: ""
  # CHANGEME: Add your GitHub/Bitbucket/Gogs/etc username here. This is a
  # comma-separated list of usernames who will have admin privs.
  server.admin.list: donghb,zhaozy,fuqq
  server.admin.everyone.is.admin: "false"

  # See http://readme.drone.io/0.5/manage/server/ for possible values here.
  # For now, our demo is GitHub-only. Drone supports other remotes, we just
  # haven't set the others up in here yet.
  # CHANGEME: Substitute your Github OAuth application client ID and secret.
  server.remote.gitlab.is.enabled: "true"
  server.remote.gitlab.client.id: cc4ce2db3715abadd9cff88cd8df34140d9078a8a060d8140684ab32fc5c1529
  server.remote.gitlab.secret: 0ec1f4d7f46c50d9b236fc475b1881dbab8c523ab49433850a4f443b1619fe77
  server.remote.gitlab.url: http://<IP_ADDRESS>

Please use https://discourse.drone.io for questions and support


Password Strength Checker.py

it lets you check whether your password is strong enough or not
Type of change

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

Changes proposed in this pull request

Project name :

Short description :

Checklist

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

Add in password projects folder


The Link "Prepare For the Github Foundation exam" gets disappeared when we switch to dark-mode

Issue
The Link "Prepare For the Github Foundation exam" gets disappeared when we switch to dark-mode
Other similar links also gets disappeared .
Bug
Image 1

Image 2

@sanjay-kv Please assign labels under gssoc'24 and hacktoberfest


utf8_string::get_num_codepoints returns number of bytes under certain circumstances with ::lut_active

Hi Jakob,
Looks like the part of get_num_codepoints that uses lut_active has issues under some circumstances. I only could fix it by disabling the entire part altogether.
Here is the example:
utf8_string bad_find = u8"S’pore Starbucks selling. gorgeous";
utf8_string substr = u8".";
std::cout << bad_find.find(substr, 0);
std::cout.flush();

The . character is at position 24. The return value is 26 due to ’ being a "compound" codepoint.
Best regards,
Vadim

Hi Vadim,
I currently have little time to have a look, but I will, as soon as I do.
Hopefully this will be in a week or so.Thank you for providing a minimal example, that helps a lot!
All the Best
Jakob

Thanks, Jakob!

Does it work, if you replace line 736 in tinyutf8.cpp
// Iterate over relevant multibyte indices
while( lut_iter > lut_begin ){

with
while( lut_iter >= lut_begin ){

?
I'm pretty sure, that's the bug, but don't have time to try it out right now.
I look forward to hearing from you!
Jakob

Hi Jakob,
Now I'm unavailable (relocating) :)  - sorry, will take me a day or two to get to that. I will let you know though.
Best regards, Vadim

Yes, it works with my example! Thanks a lot for fixing it.
Best regards, Vadim

Hi Jakob,
Long time no talk :) !
Sadly, the same thing strikes again, this time, with a longer string but again the multibytes are the culprits. Here is an example:
    utf8_string anotherFindBug = "who were engaged in “recent narcotics trafficking activity.” Those two individuals were of Newport Beach.";
    utf8_string dot = ".";
    std::cout << anotherFindBug.find(dot, 60);

It is supposed to return 104. It returns 102. If you replace “ by ", then it's all correct.
The workaround for me is to comment out the block starting at the line 2701:
if( utf8_string::is_lut_active( lut_iter ) )
...

Hi Vadim!
Indeed, I hope your doing well!
As I am currently not at home, I haven’t tried out the issue yet. Just to make sure, are you aware, that find returns the number of the Codepoint, not the Byte index? I ask, because In case of question, the lower is more likely to be correct (as the number of codepoints is <= the number of bytes).
Cheers,
Jakob

Hi Jakob,
I'm good, thanks, hope you're also doing well.
Yes indeed, the issue is now different, and it's definitely not the number of bytes, but the number of codepoints is absolutely incorrect. I naturally assumed the issue was in my code before zeroing in on the issue. I don't know where the number comes from, but there's definitely an issue in this part. Run the example, and you'll see.
Best regards, Vadim

I had a look to the code and it was a small ">" to ">=" issue 😃
Thanks a lot for pointing me to it, I hope the issue was not blocking you. I'll commit in a second...

Does it work for you now as well?

Sorry about  the belated reply, Jakob! (Crazy weeks, then I forgot about it.)
I checked and indeed it works now. Thank you very much for the quick resolution.

No probs!


Missing pluralize helper

Am I missing something or is the pluralize method missing?
If I were to help you add it, should it be added in a similar fashion as this? I'm not familiar with the codebase but happy to help.

Looks like I missed one! Yes, I believe it would be a value helper which means it would return something rather than output something.


Allow Timeout Extension In Pipeline Generation

Follow up issue filed here.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


Add support for reordering location services

Now it is available to select which services are enabled, but ordering is pre-selected and cannot be changed anywhere. Just BetterLocation link (not button) is always first.
Add option to re-order these items what user wants. BetterLocation link should be still always first.

Previously

New

Changing order of service (drag&drop is not supported)
https://github.com/user-attachments/assets/71a4a7af-9b30-4ad1-9e46-fda2e4e8d38c


cursorColor doesn't seem to be working

I am unable to change the cursor color. I have tried to change this using the newly added cursorColor attribute. Please advise.

Same here

I has been resolved with the latest update


subsample_paired_power draws subsamples in the wrong place

After simulation, and some consideration, it looks like the current implementation of subsample_paired_power needs to draw subsamples before each test to fully explore the space and collapse the number of permutations needed.
This addresses some of the issues in #880.

@JWDebelius, do you have an ETA for a fix on this? We're hoping to release 0.3.0 next Thursday, before the sprint, but we don't want to do that release with a known bug.

I think I have a fix. It worked for test data, and I'm running on the American Gut now to confirm. I should have a  new PR in by tomorrow.

Fantastic, thank you!

Fixed in #911.


Disable http2 for indexServer

Please specify the area for this PR
/server
What does does this PR do / why we need it:
This PR disables the HTTP2 protocol from the index server, following the instructions from here: https://pkg.go.dev/net/http#hdr-HTTP_2
This task is related to the mitigation of the Rapid Reset CVE. More info can be found in the related issue: https://github.com/devfile/api/issues/1342
Which issue(s) this PR fixes:
Fixes https://github.com/devfile/api/issues/1342
PR acceptance criteria:

[x] Test Coverage

Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

Documentation (WIP)

[x] Does the REST API doc need to be updated with your changes?
[x] Does the registry library doc need to be updated with your changes?

How to test changes / Special notes to the reviewer:

As the current issue is related to security, I'd suggest to create a separate issue in order to improve the coverage on index.go

As the current issue is related to security, I'd suggest to create a separate issue in order to improve the coverage on index.go (having in mind that the coverage diff is ~0,3%)

I've created issue https://github.com/devfile/api/issues/1361 in order to keep track of the new test cases implementation


output_issue

Hello, I am runing the pretrained model with UNet but there is an issue in output ,Can you guide me on how fix it ,I will attach the output here.

Are you using the test.py for lane marking prediction?

yes,I used test.py &changing the model from here cli_helper_test.py
ENet give good result but UNet No .

How long did you train the UNet model?

I didnot train the UNet mode ,i used your pretrained model in file log

I don't provide pretrained UNet weight. Maybe you load the wrong ENet weight into the UNet model.


[Feature Request] Make storage path configurable

I stumbled upon this repo and realized this is exactly what I've been looking for as a lot of my data is very large 20k+ records. One issue I noticed is there is no way to configure the storage location as it's hard coded. If you could make that configurable that would make this plugin work perfectly!

Thank you very much!!!


Adding a back to top button feature

Brief description
Due to length of index.html a back-to-top button was long needed. This feature is fully implemented using CSS only. It uses hover to control visibility of the button.
Developer Certificate of Origin

[x] I certify that these changes according to the Developer Certificate of Origin 1.1 as described at https://developercertificate.org/.

Sample pictures

Further details
Had to add a back2top.less file and a class .to-top to control the behavior of button

mixins?

Very nice and very needed while this is still a monster index.html file. Since this is unique to the documentation page, would it be best to move this into the demo.css? Or could this be a feature that can be used by others in their sites?

I'm confused too about whether this could be a feature or not.
BTW what does demo.css do?

@afzalsayed96 demo.css is an independant file from the framework, which is only used in the docs/demo app for demonstration purposes.

@tomtominc thanks for clarification :)

Awesome, thank you!


Make the code more portable

The portable builds fail on my machine (Fedora) with Program received signal SIGSEGV: Segmentation fault - invalid memory reference. It appears that the code is not statically compiled
Currently the code is compiled with -march=native, if we want portable builds we should change this to -march=x86-64.

[ ] Compile with -march=x86-64
[ ] Static compilation (-static)
[ ] Dump backtraces to find exact reason for segfaults (-fbacktrace)

So will we need to generate 3 different builds?
Linux x86, MacOS x86, and MacOS ARM.

Yeah, if you want to have builds for Mac we should set up separate workflow steps.
Do you have installation instructions for macos?
I don't have access to macos, so I cannot test it.

The installation steps for MacOS are mostly the same as Linux, as long as gfortran is being used. I have gfortran and the NetCDF libraries installed via brew.
brew install netcdf netcdf-fortran gfortran
The only other difference versus Linux is the location of the NetCDF library, which is located automatically with the nf-config command used by the configure script. This tool is downloaded by brew alongside the NetCDF libraries themselves.

I changed the compiler flags to -march=x86-64 -fbacktrace -g -static.
I had to install these libraries:
sudo dnf install netcdf-fortran-static netcdf-static glibc-static libgfortran-static.
But the compilation is giving some errors of this kind:
...
(.text+0x257): undefined reference to `nc_insert_array_compound'
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/14/../../../../lib64/libnetcdff.a(nf_lib.o): in function `nc_inq_compound_field_ndims':
(.text+0x2a4): undefined reference to `nc_inq_compound_field'
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/14/../../../../lib64/libnetcdff.a(nf_lib.o): in function `nc_inq_compound_field_f':
(.text+0x2ff): undefined reference to `nc_inq_compound_field'
/usr/bin/ld: (.text+0x349): undefined reference to `nc_inq_compound_field'
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/14/../../../../lib64/libnetcdff.a(nf_lib.o): in function `nc_inq_varnparams':
(.text+0x3d9): undefined reference to `nc_inq_var_filter'
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/14/../../../../lib64/libnetcdff.a(nf_lib.o): in function `nc_inq_numgrps':
(.text+0x397): undefined reference to `nc_inq_grps'
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/14/../../../../lib64/libnetcdff.a(nf_lib.o): in function `nc_inq_numtypes':
(.text+0x3a7): undefined reference to `nc_inq_typeids'

I'm not entirely sure how these can be solved.

Seems like it can no longer find the netcdf library.


Update collapsibleState value on expand/collapse

For the unified design in resource groups we check the value of collapsibleState to determine if tree items are visible. This value was never actually being updated, and was only representing the initial collapsibleState of the tree item.
I set it up to listen to the onDidCollapseElement and onDidExpandElement events provided by TreeView.

Closing in favor of #1150


Bind handleEvent to squire instance

handleEvent can be called with the wrong context, force it to be bound to the
squire instance.

handleEvent can be called with the wrong context, force it to be bound to the
squire instance.

How? There should be absolutely no need for this. It's not very well known, but you can add an object as an event handler rather than a function using the standard addEventListener, and it will call the handleEvent method on the object when the event fires. This is what Squire makes use of. It sounds like you're either configuring something wrong, or you have some other code in the page interfering with the standard addEventListener DOM methods?

I made this change over a month ago and don't remember how I triggered it, going to try disabling it to see if I can reproduce.

Haven't had a problem removing this, so closing this PR. if I see it pop up again and have a clear code path I'll let you know.


[Bug] sendSplitRequest condition optimization

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
1.18
Flink CDC version
3.0
Database and its version
mysql
Minimal reproduce step

com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader#start
这个地方判断条件是否应该是 <=0 而不是 <=1
What did you expect to see?
判断条件是否应该是 <=0,checkpoint恢复后。没有分片，需要申请新的分片，如果有的话不应该申请分片，而是在splitfinished时申请分片
如果cdc这边必须是<=1，能给出原因吗
What did you see instead?

Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

This condition using <=1 is for the scan.newly-added-table.enabled.
When restoring from a savepoint, a job may be sent the BinlogSplit. If the parallelism = 1, the source reader will not request new splits and the newly added tables will not be read.


Group 6 assignment

We're done.

Hi Team 6,
To get the ball rolling on the code review, I think the main issue I notice with the code is that the individual language names are hard coded throughout your program. This means that whenever your client/users wanted to add a new language to be detected, say French, you would need to change your code in a number of places. If we were to consider the languages.py to be our database, we would want to be able to update the database any number of times without having to change code, the code should be separated from the data. Another approach would be to loop through the the value being passed into the languages parameter and store the result in a variable.


Document How to Add pointer-events: none To Shape/Timeline

Okay, I've got some nice Shapes in my app now! But, after they execute, they leave a 'dead-zone' on the interactive elements behind them. I'd like to be able to just set pointer-events:none on them, but MoJS elements don't have classes or ids, and setting pointerEvents: 'none' to the Shape creation doesn't seem to work as I expected it to. I can't see anything about pointer-events in the documentation.
Is there a preferred way to set pointerEvents: 'none' on an individual shape, or a whole Timeline?

This can be solved by applying setting className: 'pointer-events-none' to all of the bursts/shapes created (where pointer-events-none is defined by Tailwind CSS, but can be any class where pointer-events: none). Cheers!


Fix for GCC warning "control reaches end of non-void function".

Curious! What version of gcc are you using and on which OS?
The Travis builds have never shown that warning - maybe I need to update the compiler versions.
The switch statement covers all enum values, so gcc should be smarter :-)

The warning appears when compiling with GCC 8.3.0.
I've tested both in elementary OS 5.1 (based on Ubuntu 18.04) and in Debian 10.

Thanks José!


Getting the country name in Simple Letters

Is there a way to get the country name in Simple letters rather than all in Capital

Sorry for the late response.
Can you elaborate more your requirement? Currently country name is capitalized only on the first letter.

Feel free to reopen this issue..


fix(linter): false positive for filename_case where filename doesn't have a proper casing

Current dependencies on/for this PR:

main

PR #2032   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 15, 1:36 AM: @Boshen merged this pull request with Graphite.


Enable ssl connection with ecto 2.0

Hi! How i can connect to my mongodb instanse with ssl parameter in true?
I have dsn string like mongodb://user:pass@host:port/?ssl=true and i can not disable ssl.
How i can connect with this parameters?

You can either break that apart into its different pieces. Something like
config :my_app, MyApp.Repo,
  adapter: Mongo.Ecto,
  username: "user",
  pass: "pass",
  hostname: "host",
  port: 27017,
  ssl: true

Or, you can take advantage of using the url option.
config :my_app, MyApp.Repo
  adapter: Mongo.Ecto,
  url: "mongodb://user:pass@host:port/?ssl=true"

The unfortunate thing about this is that the current release of the actual mongodb package does not have SSL support. So you will need to grab that from github

Tnx! With "url" parametr not work.
With config like:
config :crawler, Crawler.MongoRepo,
  adapter: Mongo.Ecto,
  database: "cache",
  username: "cache",
  password: "***",
  hostname: "***",
  port: ***,
  ssl: true

15:58:21.258 [error] Mongo.Protocol (#PID<0.340.0>) failed to connect: ** (Mongo.Error) ssl connect: TLS connection is closed - :closed

instance mongodb created in ms azure

You are going to want to file an issue with the mongodb package. That is where the SSL functionality is implemented.


Add attribution notices

For 3rd-party frameworks, packages and tools in use.
Add THIRD-PARTY-NOTICES.TXT to the root of the repo.
Add About section with GitHub names and links to all contributors - and also links to all awesome 3rd party libraries and tools that we rely on.

We're using an Apache-2.0 compliant NOTICE test file instead.
Also, we're including this NOTICE file in the published app (/wwwroot/).
We're going to parse that Markdown file (probably via Markdig), collapse all "code fences" (which include the license texts) and render that to HTML.


chore: Remove unused daemon::noise module

It was used to encrypt the legacy network connection.

bors r+


fix(lint): @turbo/test-utils

Description
Lint for test utils package

I'm assuming test/formatting will pass with the updated name.

🤦🏼 good catch, thanks!


Fix link in Natss readme pointing to a Knative Setup link which no longer worked

…
Fixes broken link to Knative Eventing Setup in Natss config readme file.
Proposed Changes

Update Natss config readme link to Knative Eventing Setup

Release Note

/assign @abd4lla

Need to fix the CLA.

The cla has hopefully been fixed now as I've added by GitHub username to the signed cla/google. I suppose we'll just give the system some time to find out if it's sufficient/I've done this correctly.

It doesn't look like the automation is able to detect that I've signed the CLA and that I've also made sure that my GitHub username is now associated with the signed Google Individual CLA agreement.
I'll probably just cancel this PR instead of trying to find out why as this PR is so small that it's probably not worth the hassle (I might try to create another PR later).
Anyway.. I'll wait a couple of more days just in case the automation is able to pick up that I have singed the Google Individual CLA and associated it with my GitHub username (which I assume ought to be sufficient???).

I'll might fight the CLA thing at a later time --- and/or come back with a new PR if the link hasn't been fixed the next time I have a need to read the documentation.

@HansK-p I hope link will be fixed https://github.com/knative/eventing-contrib/pull/988 and I look forward to work with you on Knative


Update renderer Path in Readme File

In my installation ia had top copy the twig file to a complete different folder

In my installation it works like it is documented under
https://www.kimai.org/documentation/export.html#adding-export-templates


Screen Recorder

Is your feature request related to a problem? Please describe.
It will Record the screen.
Describe the solution you'd like.
will upload soon
Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.
No response

I am working on it


javascript XSS when using MD links

Describe the bug
There is potential XSS issue when using MD links.
To Reproduce
Steps to reproduce the behavior:

Open editor
Add the following: To read more [click here](javascript:alert(localStorage["key"]))
When displaying the result MD created by the component - there is clickable link which alert a key from localStorage

Expected behavior
javascript should be sanitized, or at least should have a way to disable the support of it.

@ET-CS
What is your editor version?
I cannot reproduce it in the latest version.


[Container app] az containerapp create/update: Fix scale rule for TCP type

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Container app


Add example usage section generation

Codecov Report

Merging #42 (1d4d475) into main (dd48887) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   98.90%   99.03%   +0.13%
==========================================
  Files           5        5
  Lines         274      312      +38
==========================================
+ Hits          271      309      +38
  Misses          2        2
  Partials        1        1

Flag
Coverage Δ

unittests
99.03% <100.00%> (+0.13%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/document/markdown.go
100.00% <100.00%> (ø)

pkg/generator/markdown.go
100.00% <100.00%> (ø)

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 dd48887...1d4d475. Read the comment docs.


How will Octopress/Jekyll handle the "captions"?

Hi, I have only little to zero knowledge of the implementation details of Octopress/Jekyll. Therefore maybe my ideas/questions are already solved. In that case please just close the issue.
The idea of multilangual sites sounds great.
What I was looking for (and perhaps it is solved in the new Jekyll/Octopress release) is a method for the "captions".
I would suggest to define "captions" for all the text, menu entries, links (e.g. for "Recent posts", "Older", "Blog Archives" in case of Octopress). Somewhere the English texts are defined for these captions. If I want to switch to a new (not yet existing) language, I add an entry lang=de and somewhere have to define all the captions (e.g. in YAML) and perhaps a time/date format:
lang: de
captions:
  - blog_archives: "Archiv"
  - older: "Ältere Einträge"
...

That perhaps would it make easier for people to have a Non-English blog because there would be a central place for defining those captions.
I hope I made clear what I was thinking about. And perhaps it is already solved in the 3.0 release.

I think, configuring this in the front matter or even the config file is a terrible idea. Just remember that there are potentially hundreds of strings that need to be translated.
However, there is already a solution out there that solves this using liquid tags and a (language-specific) translation file: https://github.com/drallgood/jekyll-multilingual/blob/master/translation_plugin.rb
It's basically a copy of this (with a few important omissions):
https://github.com/screeninteraction/jekyll-multiple-languages-plugin

Thanks. Great to hear that something for these translations already exists. Would be great to have that "out of the box".

Using a language dictionary is an interesting feature. Implementing it seems to be fairly complicated and I wonder how often it would just be easier to write out the site for each language manually. @drallgood Do you think that feature makes a big difference to people? Is it worth the effort to build, maintain, and support?

I think so, yes. Otherwise you'd essentially need to duplicate your entire template (or at least the parts that contain text) which makes changes really difficult. Especially when we're talking about a bigger set of languages (>2).
The dictionary approach keeps your templates clean and the translations somewhat maintainable.

I would support that as well. Several German friends of me iasked "How to I get a 'German' blog?" Therefore it may be a good idea to have an easy way to switch language for the "user".

Switching the language is actually pretty easy.
Here's how I do it:

  {% if page.lang == "de" %}
    {% assign switch_to_language =  "en" %}
    {% capture language_switch_text %}{% t global.switch %} {% t global.german %}{% endcapture %}
  {% else if page.lang == "en" %}
    {% assign switch_to_language =  "de" %}
    % capture language_switch_text %}{% t global.switch %} {% t global.english %}{% endcapture %}
  {% endif %}

This includes a few things not yet supported by this plugin (e.g. removing the language from an URL or translating static text)
@imathis: Have you decided whether or not not add the language dictionary thing, yet?

On switching language, the approach you've listed above assumes there is a translated post and that it has the same title. I know that may be the most pragmatic approach for a single site, but it would be error prone to expect this to work for all sites. It also doesn't seem to take into account that there may not be a translated post in that language.
I'm trying to decide if I want to spend time developing a system for linking posts that are translations. This way you could have an English title and a German title but you could do something like:
Also read in: {% translated_posts post %}  # in the post loop

This could generate a list of urls to other posts with all the HTML necessary (including classes so you could style them with flag images).
The thing is, I'd need a way to link posts (or pages even) together. The first thing that occurred to me was to do it based on urls. So you keep some YAML file with arrays of linked posts or something, but the problem is that permalinks can be configured, so with a simple change in the _config.yml, all this becomes useless.
So, without a database, how can I link posts together in a way that won't ever break? I think my best idea is still to create a language fingerprint that translated posts can share. Perhaps I would add a command to Octopress so you can type octopress translate _posts/[filename], _posts/[filename], _posts/[filename]. Then it would generate a key something like translation_id: a31asdb12t1ba which would be uniquely based on the posts and automatically added to the YAML front-matter for each post.
Then the liquid tag would generate post lists like this:
def translated_posts (site)
  @translated_posts ||= site.posts.group_by { |post| post.data['translation_id'] }
end

def translate_post (post)
  links = ''
  translated_posts(post.site)[post.translation_id].reject{|p| p == post }.each do |translated_post|
    links << "#{translated_post.lang}"
  end
  links
end

I'm just roughing it out in this comment, but I think this approach would work quite well.

On switching language, the approach you've listed above assumes there is a translated post and that it has the same title.

Yeah. You're right, this approach assumes a lot (and I think I broke it when migrating to this plugin).
Especially for cross-posts this doesn't work at all, because people will get the site in the post's language, no matter what.
It worked previously because I just duplicated cross_posts internally and used the same slug for all translations of a post.
And I think we're throwing several issues in the same pot:

Cross-posts and how they show up for other languages
Linking translated posts
Translation of static text in templates

I like the way you think in regards to linking posts together.

Oh, I should also say… While that would work, I'm not sure if people will use it. It's kind of a pain to have to add translation ids to every post (if you already have a blog), but I guess it's also a pain to not just use tumblr, so… maybe this is a good idea.
As far as a language dictionary goes… I'm not entirely sure how I'd approach this. Even more than linking posts, this seems like a hard feature to standardize. When I and others start shipping Octopress Ink themes and plugins, they will each have their own places where translatable words may appear. Sometimes they may be words that are written by the plugin developer, and sometimes they'll be places where the user will have to figure out how to provide configurations in two languages.
For example, in the Genesis theme (still a work in progress) you can set your site's navigation like this:
nav:
  - { url: '/', title: 'Posts' }
  - { url: '/archive/', title: 'Archive' }
  - { url: '/feed/', title: 'Subscribe' }

The plugin spins through this list and adds them to the main navigation on each page. I could support a method where users can add language keys like this:
nav:
  en:
    - { url: '/', title: 'Posts' }
    - { url: '/archive/', title: 'Archive' }
    - { url: '/feed/', title: 'Subscribe' }
  de:
    - { url: '/', title: 'Beiträge' }
    - { url: '/archive/', title: 'Archivieren' }
    - { url: '/feed/', title: 'Zeichnen' }

Note: Apologies for German, (it's Google Translate).
Now the navigation link code could use the page.lang to decide which array of links to spin through, but the code would have to be rewritten to accept keys or an array if the user isn't translating titles. But this isn't a standard dictionary way of handling things, this is a one-off method for each configurable thing.
I may be able to write a layer than runs between a configuration and the implementation that takes the page.lang into account so everything can work as without needing to care about language. I'm still thinking about it though.

There is already a standardized way to do this (well, kind of). Most languages/frameworks (Java EE, PHP, Python, ... ) do this using dictionaries and mapping it at render time.
I don't think you necessarily need to change the configuration.
What you'd need instead is a standardized way to define translation keys for plugins, so they don't overlap. And a way for plugins to define them, of course.
Maybe plugins can provide their own translation files, which you can overwrite if necessary (just like you can overwrite the templates of the feeds plugin)?
Maybe like this: /plugins/<plugin name>/i18n/<lang>.yml
This would also mean there isn't one single YAML file that contains all the translations for your site but multiple ones...

Well, this is something specifically for Jekyll and Liquid, so Ruby support isn't going to be that helpful. The i18n directory/language system makes sense for compiling software, but it's a pretty unfriendly user experience. I don't want single-language users to have to manage an english translation file to configure text labels, but if I don't I have an inconsistency with how German users edit English labels. I don't think many plugin developers are going to buy into supporting i18n features unless there's a way to make it hassle free for them. This approach doesn't do that for developers or for end-users.

Well.. Users wouldn't have to deal with it unless they want/need to. As I said, each plugin can/should come with a set of default translations (maybe even just English. The community can always take care of the rest...).
I'm a developer, with a lot of experience in creating web services that serve markets in multiple countries. So, of course, my ideas should always be taken with a grain of salt. I'm used to doing this kind of stuff... :wink:

I'm still noodling on this. I'm thinking about trying this (example of configuring the octopress-feeds plugin):
_plugins/feeds/
  config.yml
  languages/
    de.yml
    it.yml

Octopress ink would read in the config.yml as the plugin's default language's configuration, then settings from other languages would be read in as overrides for the default language. Any references to those configs, i.e. {{ plugins.feeds.some_config }} would be automatically read using the current languages config file, if one exists.
For this to work seamlessly, I may end up changing how this plugin works. Currently it expects you to use a {% set_lang [lang] %} block, during which it processes everything as under the new other language. The change I'm thinking about is adding the ability to automatically convert the language scope for any page with a lang setting which is not the main language. People could still use the set_lang Liquid tag to change language context temporarily, but it probably won't be needed very much.

That sounds good to me.

I just released a large change in how this plugin works. Now there's no need to use {% set_lang %} anymore. Post loops are automatically filtered based on each page's lang setting in the YAML front-matter. It works beautifully. I'm currently updating Octopress Feeds to work with this new approach, and then I'll get to work on dictionary stuff.

Wow. Awesome!
I'll give it a try later and report back :smile:

Alright, octopress-feeds is updated, it now supports the new page.lang feature. I'm really excited for how this is coming together!

Yeah. I really like it, too!
Aside from the crossposts which aren't showing up, it seems to be working :smile:

@drallgood, did you see that the configuration changed so that crossposts are lang: all?

I did not.
Is that a good solution, though? You loose the ability to identify the primary language of a post.

An "all" language crosspost is set to the default language, configured in site.lang.

Yeah I got that... But what if it's written in anything but the default language?
I've got plenty of posts in either German or English, English being the default ;)

So you think it's a common enough scenario that people will want to crosspost from multiple source languages?

That's the big question even I can't answer.
Crossposting is probably not all that common anyway, so I guess it's even less common that someone is doing it in multiple languages.
I just feel that you're loosing information if you have to set the language of a post to 'all' to crosspost it.

Yeah I'm not entirely sure I buy it, but I don't like having an additional config (especially one with the cumbersome name crosspost_languages) to add a language to all feeds. To me, lang: all is the simplest way to configure the likely 99% uses of an edge-case feature.
Another option would be to accept an array ['en', 'de'] and basically treat it the same way as all except default the language to the first item in the array instead of site.lang.
Or yet another option would be to leave it this way and if enough people complain. I can add a way for them to set the language and the crosspost feature at the same time.

Yeah, you're absolutely right.
For me, that will mean that 99% of all posts will have to be configured with lang: all. Not sure whether that's helpful at all, but I guess I will have to live with it :wink:

Hmm. That's an interesting statistic. So in your usage, you're not as much running a multilingual blog as you are occasionally wanting to hide specific posts from one language group or another.

Well.. I've got multiple sites, each one being unique in its own way:
On my personal blog, I usually post in English (and those are all crossposts), with the occasional multilingual entry. And a few legacy posts which were written in German (which aren't that important anyway). Static pages are fully translated.
Another site primarily consists of German posts, with the occasional English post every now and then. Almost none of them are crossposts.
And to be clear: I don't care whether my particular needs are met or not. I'm very aware, that I'm an edge case and will find a way to make it work either way...
My guess would be, that there are three major use-cases for this type of plugin:

truly multilingual sites (everything is translated)
sites with very little overlap between the languages (i.e. there's rarely a post in one language that coincides with another in a different language).
sites that post only in one primary language (crossposts) but have translated the rest of the site (pages, navigation, ...)

Thanks for assembling these use-cases. As a monolinguist I'm not a good judge of this kind of stuff. I know over the years Octopress has been pretty popular with polylinguals and requests for a feature like this have come up often. I've avoided it until now because I hadn't figured out a simple way to get it to work. I'm still trying to figure this one out. I may change it. I'm sorry for all the runaround.
But, I just released some updates to this, Octopress Ink, and Octopress Feeds. Now all language feeds are generated automatically. So yay!

Alright, I've done just about everything except dictionaries. That's next. For now, if you update to 0.2.0 you'll have these new features.

Link between posts or pages with a matching translation_id.
Add translation IDs to posts or pages with octopress translate <path>.
Check if a post or page has been translated with [post or page].tranlsated.
Access translated posts or pages with [post or page].tranlsations.
New tags {% translations [post or page] %} and {% translation_list [post or page] %} for generating links to translated posts.
Convert language codes to language names with filter {{ de | language_name }}.

And in 0.1.4, I moved away from lang: all for crossposts and added it as lang_crosspost: true.
@drallgood I've update the readme and I'd love to get your feedback on these changes.

Wow. That looks amazing.
I'm in the middle of implementing this on my site. octopress translate doesn't work yet. Neither is it showing up in octopress -h
Thanks for your time @imathis !!

@drallgood, I forgot that the CLI extension depended on a release in Octopress. I just pushed that up, and bundle update should let you start translating posts.

Yep. That did it.
Works perfectly. Good job! :smile:

Alright, I've added translation dictionaries and released 0.3.0. I'd be curious to hear what you think of this. Here is how they work:
In your site's _data directory you can add language dictionaries with the file
naming pattern lang_[langauge_code].yml. For example:
_data
  lang_en.yml
  lang_de.yml

Your files might look like this:
# lang_en.yml
title: English title

# lang_de.yml
title: Deutsch titel

Now in your layouts or includes you can reference these dictionaries under the global variable lang. The configured page or post language will determine which language dictionary is used. For example:
# On a page or post where lang: en
{{ lang.title }} => English title

# On a page or post where lang: de
{{ lang.title }} => Deutsch titel

If no language is configured for a page or post, it will default to the site's default language.
# No page lang, site is configured lang: en
{{ lang.title }} =>  English title

Since these are Jekyll data sources, these dictionaries can also be accessed at site.data.lang_en and site.data.lang_de. This plugin merely adds the global lang variable and swaps out context based on configured language.

Sorry it took me a while to give this a try.
Works flawlessly. Really great job!

Cool, so it seems like I've covered all the basic use cases of a multilingual plugin. If there's anything you run into or if I've missed something, create an issue and I'll have a look. I think I'll probably go ahead and mark this a 1.0. Thanks for all your help!


feat(lang): init py env by generating the bulid.envd

Signed-off-by: Keming<EMAIL_ADDRESS>includes:

requirements.txt
env.yaml

maybe later:

pyproject.toml
setup.cfg
setup.py

Could we test it under root users?

Could we test it under root users?

What do you mean by "under root users"? Run the envd init with sudo?

Could we test it under root users?

What do you mean by "under root users"? Run the envd init with sudo?

such as
# envd init

Could we test it under root users?

What do you mean by "under root users"? Run the envd init with sudo?

such as
# envd init

sometimes ,root users executions will cause some unexpected error for file permission.

Is it related to https://github.com/tensorchord/envd/issues/666?
Do we need to add the root test to all the e2e tests?

Could we test it under root users?

What do you mean by "under root users"? Run the envd init with sudo?

such as
# envd init

sometimes ,root users executions will cause some unexpected error for file permission.

Is it related to #666?
Do we need to add the root test to all the e2e tests?

I think we could do all e2e tests in root users. WDYT @gaocegege

I'm going to merge this one. We can discuss the root user test in #666.


Render full plain readme

closes #17077
The old code just rendered the first 1024 bytes.

Codecov Report

Merging #17083 (5e20a94) into main (e2f0ab3) will increase coverage by 0.03%.
The diff coverage is 41.53%.

@@            Coverage Diff             @@
##             main   #17083      +/-   ##
==========================================
+ Coverage   45.23%   45.26%   +0.03%
==========================================
  Files         766      771       +5
  Lines       86706    86767      +61
==========================================
+ Hits        39220    39277      +57
- Misses      41139    41140       +1
- Partials     6347     6350       +3

Impacted Files
Coverage Δ

cmd/admin_auth_ldap.go
76.47% <0.00%> (-1.15%)
:arrow_down:

modules/context/api.go
74.17% <0.00%> (-0.71%)
:arrow_down:

modules/context/auth.go
19.81% <0.00%> (-0.37%)
:arrow_down:

modules/migrations/github.go
68.29% <0.00%> (-0.39%)
:arrow_down:

routers/api/v1/notify/user.go
14.00% <0.00%> (-0.59%)
:arrow_down:

routers/api/v1/repo/file.go
62.21% <0.00%> (-0.29%)
:arrow_down:

routers/api/v1/repo/issue.go
47.65% <ø> (ø)

routers/private/hook_verification.go
0.00% <0.00%> (ø)

routers/web/repo/view.go
41.28% <0.00%> (-0.24%)
:arrow_down:

routers/web/user/auth_openid.go
0.00% <0.00%> (ø)

... and 38 more

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 0b368aa...5e20a94. Read the comment docs.


Start the progress bar from $startRow

Description of the Change
When using WithChunkReading and WithProgressBar together, progress bars are wrong:
0 to 100 / 100 (0% to 100%)
0 to 100 jump to 200 / 200 (0% to 50% jump to 100%)
0 to 100 jump to 300 / 300 (0% to 33% jump to 100%)

We now advance the progress bar to $startRow - 1 right at the beginning to have:
0 to 100 / 100 (0% to 100%)
100 to 200 / 200 (50% to 100%)
200 to 300 / 300 (66% to 100%)

We start from $startRow - 1 to avoid going to 201 / 201.
Possible Drawbacks
Percentages are correct but the timing is still wrong (during the third progress bar, 66% to 100% is as long as the first progress bar from 0% to 100%). Maybe a future PR could fix the progress bar a bit more. Or I could make the change if someone tell me what behavior is wanted.
Easy to do:
0 to 100 / 100 (0% to 100%)
0 to 100 / 100 (0% to 100%)
0 to 100 / 100 (0% to 100%)

Or, second possibility, but not sure if it's possible to end the progress bar without jumping to 100%:
0 to 100 / 300 (0% to 33%)
100 to 200 / 300 (33% to 66%)
200 to 300 / 300 (66% to 100%)

Hey @ThibaudDauce, thanks for the PR and the possible fix. I decided to fix it in a different way. Now progress bar is supported in combination with WithChunkReading. Progress and timing are good now.

Nice! Thanks for the fix :-)

@ThibaudDauce Can I look your code ?

@zishiguo what code?


Simple getting started as a contributor docs

Having not looked at halotools for a year or so, it took a bit of work to remember the code/test workflow that worked with .pyx files. The first time around, this also took me a while. In both cases I worked out that this did what I wanted:
python3 setup.py build_ext --inplace # if I changed a .pyx file
cd halotools
pytest [-s -k my_test_seach_string]

I'm sure this is very standard and people who work on large, compiled, python projects are probably very used to it. But having this (or a simpler workflow that you use) in a findable place might help new contributors.

New page added to the docs in #962.


Sign up form

Issue: https://github.com/datopian/portaljs/issues/771
Changes:

Implemented the SendingBlue form on the hero section

@demenech looks good. I would suggest it is just email rather than name and email - it is simpler for users and the name is not that important. KISS rule.


Figure out Postgres Query Logic Step

Excited to start the project!

please assign

Assign to me as well!


core: add initial code

This commit adds inital code with
ceph command supported.
Closes: #2
Signed-off-by: subhamkrai<EMAIL_ADDRESS>

@travisn @leseb @BlaineEXE @sp98 ^^

@travisn or @leseb or @BlaineEXE  is GitHub action enabled for this repo or if not, can you please enable it? Thanks.

@travisn or @leseb or @BlaineEXE is GitHub action enabled for this repo or if not, can you please enable it? Thanks.

It's enabled but I think we need to merge first to kick in the initial workflow.

@travisn or @leseb or @BlaineEXE is GitHub action enabled for this repo or if not, can you please enable it? Thanks.

It's enabled but I think we need to merge first to kick in the initial workflow.

okay :+1:

I'm always skeptical when it comes to building CLI tool with bash. I just want to make sure we agree on the approach. @BlaineEXE thoughts?

The most clean way I have seen this work is to use case statements for the args. Lots of implementations use shift, which I don't love, but it works well for some. I would avoid if statements on the number of args other than to warn when not enough args were given and show usage. For ceph, commands, if the user passes no args, the ceph CLI will have its own default response we can rely on. I don't see a need to do our own warning for this.

I'm always skeptical when it comes to building CLI tool with bash. I just want to make sure we agree on the approach. @BlaineEXE thoughts?

The most clean way I have seen this work is to use case statements for the args. Lots of implementations use shift, which I don't love, but it works well for some. I would avoid if statements on the number of args other than to warn when not enough args were given and show usage. For ceph, commands, if the user passes no args, the ceph CLI will have its own default response we can rely on. I don't see a need to do our own warning for this.

which warnings the one I have put in usages method?

Please add a CI :)

added CI let me know if the approach is right.

Can we add a README to explain how to use/configure kubectl to have this plugin?

added

FYI,  Suggestion:
Anything we think should be done in follows up PR, it will be better to open a new issue so that we can follow up after this also.


image cropped or corrupted

1x and 2x images exported good, but 3x and 4x are corrupted.
2x preview screenshot

3x preview screenshot

4x preview screenshot

archive with images as it was downloaded
LandingCardsMobile (4).zip

Probably issue just with my computer. Solver by making export in another browser.


NullReferenceException: Object reference not set to an instance of an object

Hi, I'm getting this in a multi-project solution on solution root:
$ dotnet nuget-tree -d 2 .
Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
   at dotnet.nuget.tree.Command.OptionsCommand.<>c.<GetPackages>b__41_0(XElement e) in /home/runner/work/dotnet-nuget-tree/dotnet-nuget-tree/src/Command/OptionsCommand.cs:line 139
   at System.Linq.Enumerable.SelectEnumerableIterator`2.ToList()
   at dotnet.nuget.tree.Command.OptionsCommand.GetPackages(String fullProjectPath) in /home/runner/work/dotnet-nuget-tree/dotnet-nuget-tree/src/Command/OptionsCommand.cs:line 135
   at dotnet.nuget.tree.Command.OptionsCommand.Parse(String[] args) in /home/runner/work/dotnet-nuget-tree/dotnet-nuget-tree/src/Command/OptionsCommand.cs:line 34
   at dotnet.nuget.tree.Program.Main(String[] args) in /home/runner/work/dotnet-nuget-tree/dotnet-nuget-tree/src/Program.cs:line 43
   at dotnet.nuget.tree.Program.<Main>(String[] args)

It works inside one project sub-dir, but nowhere else. It always fails with this exception.

Tool fails for CentralPackageVersionManagement, there is already open issue about this.

Duplicate of #2


feat: metric-based scheduling (1/): AKS metric provider trackers

Description of your changes
This PR adds some trackers in use by the AKS metric provider to track certain stats regarding nodes/pods in a cluster.
I have:

[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

[x] Unit tests
[x] Integration tests

Special notes for your reviewer
Certain tests have been removed from the PR to control its size; they will be submitted in a separate PR.

Closing as it's no longer applicable (newer PR exists)


fix the bug of using optical_flow_to_color in train.py

Closes #
Changes

Change the import of optical_flow_to_color function from import _optical_flow_to_color to from neuralcompression.functional import optical_flow_to_color.
Change the function call _optical_flow_to_color.optical_flow_to_color to optical_flow_to_color

Hello @N1ghtstalker2022 could you run black on this PR so that it passes the tests?

OK. I'll do that.

Hello @N1ghtstalker2022 could you run black on this PR so that it passes the tests?

The black test can be passed on my machine. It should works now.

I don't know why it did not pass the test. The code can pass the test on my linux machine.

Hello @N1ghtstalker2022, it's just a different test, this one for isort. You can see all the tests we run here so we don't get hit with this again.

Hello @N1ghtstalker2022, it's just a different test, this one for isort. You can see all the tests we run here so we don't get hit with this again.

I've tested it again. Now it should be fine.

@N1ghtstalker2022 yes thanks so much! Sorry, was busy with some other things.


Handle existing installed flatpaks

Is your feature request related to a problem? Please describe.
Unsnap does not consider installed flatpaks.  It would be nice if it would detect (or provide candidate matches) where the system already has both the snap and the flatpak installed. (I have a couple, but this also might arise for a sane user from attempts to migrate with or without using this utility)
Describe the solution you'd like
I would like the script to match installed flatpaks (and/or make them candidate suggestions) rather than report them as missing, and maybe to comment out their entry in the generated installation script, and if they do not exist in the mapping also provide a possible mapping and a note to maybe submit an issue ...
For example:
$snap list obsidian fractal
Name      Version                Rev  Tracking       Publisher    Notes
fractal   4.4.0-244-g8781378a79  106  latest/stable  ken-vandine  -
obsidian  0.14.2                 x2   -              -            -
$sort missingflatpak.txt|grep -v snap-store >missing
$flatpak list|sort -u |join -i - missing
Fractal org.gnome.Fractal 4.4 stable system
Obsidian md.obsidian.Obsidian 0.14.2 stable system

Note the case of the flatpaks. joining the other way round can generate some suggested matches.
flatpak list|sort -u |join -i  missing - |awk '{print $1 "," $2}' |tee -a extra-applist.csv
fractal,org.gnome.Fractal
obsidian,md.obsidian.Obsidian

I don't have any flatpaks and snaps installed that are already in the applist.csv but I guess handling that then handling the "unknown"/"candidate" scenario would be OK - for such an edge-case I'd expect to end up with a candidate match list to submit as well as a a missing list, and to be able to chose to merge the "candidates" and re-generate new scripts to review/use.
Desktop (please complete the following information):
OS: Ubuntu MATE 21.10 x86_64
Kernel: 5.13.0-39-lowlatency
Shell: bash 5.1.8
Describe alternatives you've considered
Just ignoring the daft edge-case users who might be in this situation would be fine too .

Thanks for the issue @philclifford .
Yes, I agree, there's no point running flatpak install foo if foo is already installed. So we should at least omit those from the install script.


Update README.md

Corrected some typos.

Description

PR Type

[ ] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
[ ] Scripts & Website & Meta (anything related to files in the scripts folder, how the repository's automated procedures work and the website)
[ ] Glossary & Secondary Features (anything related to the glossary, such as new or updated terms or other secondary features)
[ ] General, Typos, Misc. & Meta (everything else, typos, general stuff and meta files in the repository - e.g. the issue template)

Guidelines

[ ] I have read the guidelines in the CONTRIBUTING document.
[ ] My PR doesn't include any testlog changes.

Do not update readme, please update the files that get made int the readme.


Add status endpoints to APIs

I think it would be helpful to add an endpoint to each API that returns trivial status information about each one (i.e., up/down). If something isn't working, users would be able to check if the service is down.

That is the intention of status.biosimulations.org. The issue with an API endpoint is that the API alone does not know about the various components but is just one of the components needed to get have everything working. Also it would not be able to report status if it was itself down. We should definitely make the existence of status.biosimulations.org more well known by including it in the docs/readme/front end apps however


Feature/#1908

Related issues
https://github.com/DivanteLtd/vue-storefront/issues/1908
Short description and why it's useful
I've created and registered GA module instead of extension that was implemented already
Screenshots of visual changes before/after (if there are any)
No UI changes has been introduced.
Screenshot of passed e2e tests (if you are using our standard setup as a backend)
(run yarn test:e2e and paste the results. If you are not using our standard backend setup or demo.vuestorefront.io you can ommit this step)
Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

[ ] I read and followed contribution rules
[ ] I read the TypeScript Action Plan and adjusted my PR according to it
[ ] I read about Vue Storefront Modules and I am aware that every new feature should be a module

Thanks! can you solve build errors?

@filrak Filip sorry for the delay with this, I didn't have time to tackle it once again. I will have another try during oncoming weekend and then close it no matter if I succeed or fail.

Take your time, it can wait ;) You'll just need to pull the recent changes and adjust every time you go back to this PR

OK, so let me keep this still open for a while :)


set_volume_size_limit

Set max volume size limit for the tenant
There is a need to limit maximum size of a volume to levels
that the storage infrastructure can handle.
Setting a maximum limit on size of a volume also prevents
a tenant from creating large volumes that have not been tested
and certified to satisfy SLA objectives.

Add the bug id info, as below (for ex):
Closes-Bug: #2


Unable to build the docker image

Logs
Staging lndmanage source code...
Building lndmanage docker container...
Sending build context to Docker daemon  1.554MB
Step 1/20 : FROM python:3 as builder
 ---> e2e732b7951f
Step 2/20 : RUN python -m venv /root/.venv
 ---> Using cache
 ---> 47777819d9d0
Step 3/20 : ENV PATH="/root/.venv/bin:$PATH"
 ---> Using cache
 ---> 3afe8642195e
Step 4/20 : ARG LNDMANAGE_HOST_SRC_PATH
 ---> Using cache
 ---> a65ed58bb47e
Step 5/20 : COPY "$LNDMANAGE_HOST_SRC_PATH/requirements.txt" .
 ---> Using cache
 ---> accbd970675a
Step 6/20 : RUN pip install wheel && pip install -r requirements.txt
 ---> Running in 8acf63bff7a4
Collecting wheel
  Downloading wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Installing collected packages: wheel
Successfully installed wheel-0.37.1
WARNING: You are using pip version 21.2.4; however, version 22.0.2 is available.
You should consider upgrading via the '/root/.venv/bin/python -m pip install --upgrade pip' command.
ERROR: Directory '.' is not installable. Neither 'setup.py' nor 'pyproject.toml' found.
WARNING: You are using pip version 21.2.4; however, version 22.0.2 is available.
You should consider upgrading via the '/root/.venv/bin/python -m pip install --upgrade pip' command.
The command '/bin/sh -c pip install wheel && pip install -r requirements.txt' returned a non-zero code: 1

Steps to reproduce

cd docker
bash build.sh

Environment

lndmanage version: v0.14.0
OS: Ubuntu 20.04.3 LTS
Docker version: 20.10.7

Thanks for reporting, will have a look into it, although docker functionality was contributed by @darwin.

This seems to have fixed the issue on my end. Don't have setup on this machine to test this properly.
diff --git a/docker/build.sh b/docker/build.sh
index f528192..b6ae9d0 100755
--- a/docker/build.sh
+++ b/docker/build.sh
@@ -14,7 +14,6 @@ rsync -a \
   --exclude='.idea/' \
   --exclude='docker/' \
   --exclude='cache/' \
-  --exclude='README.md' \
   "$LNDMANAGE_SRC_DIR" \
   lndmanage/_src

diff --git a/docker/lndmanage/Dockerfile b/docker/lndmanage/Dockerfile
index 26f45b6..6a3c6ae 100644
--- a/docker/lndmanage/Dockerfile
+++ b/docker/lndmanage/Dockerfile
@@ -10,8 +10,10 @@ ENV PATH="/root/.venv/bin:$PATH"
 ARG LNDMANAGE_HOST_SRC_PATH

 COPY "$LNDMANAGE_HOST_SRC_PATH/requirements.txt" .
+COPY "$LNDMANAGE_HOST_SRC_PATH/pyproject.toml" .

-RUN pip install wheel && pip install -r requirements.txt
+RUN pip install --upgrade pip setuptools wheel
+RUN pip install .

 # ---------------------------------------------------------------------------------------------------------------------------

@@ -39,7 +41,8 @@ ARG LNDMANAGE_HOST_SRC_PATH
 COPY "$LNDMANAGE_HOST_SRC_PATH" .

 # this should be fast because it is cached from builder image
-RUN pip install -r requirements.txt
+RUN pip install --upgrade pip setuptools wheel
+RUN pip install .

 WORKDIR /root
 COPY "home" .

@darwin build worked here with these changes. ty
Is it a good idea to create a PR for it?


[New game]: Pokemon Ball Finder

🎮 Game Request
Title: Pokemon Ball Finder
Description:
A Pokemon game using HTML, CSS, and JavaScript, where players control a character using arrow keys to search and collect Pokeballs, earning points to win the game. The game offers an immersive and enjoyable experience to the user.
Point down the features
Player Control: Player control using arrow keys to move the character across the game world. Allows smooth movement and responsive controls to provide an engaging gameplay experience.
Pokeball Collection: Pokeballs throughout the game world that players must collect to earn points. Logic to track the number of collected Pokeballs and update the player's score accordingly.
Obstacles and Challenges: Obstacles and challenges, such as obstacles that block the player's path or enemies that must be avoided. Colliding with obstacles or enemies results in appropriate consequences, such as losing points or health.
Power-ups and Bonuses: Power-ups and bonuses that players can collect to enhance their gameplay experience. Power-ups could include temporary invincibility, increased speed, or bonus points, adding excitement and strategic choices to the game.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @AK4266 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hello @AK4266, Time's Uppp!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @AK4266 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


[Media Library] Option to disable

Is your feature request related to a problem? Please describe.
I use the CMS to manage text only, and I want to prevent users from uploading media/images.
Describe the solution you'd like
I'd like to see an option to disable the Media Library uploading of images altogether.
media_folder is now a required configuration, I'd like to see this optional. This could also hide the Media toolbar button and the menu option in the editor UI under the "+" button.

This should be possible by registering an external media library class and returning false in the enableStandalone method.
See the uploadcare library as an example: https://github.com/netlify/netlify-cms/blob/60013a06f9dcffb27d2ae48984f93e2b5063985f/packages/netlify-cms-media-library-uploadcare/src/index.js#L168

Adding a full example:
cms.js:
CMS.registerMediaLibrary({
  name: 'disabled',
  init: () => ({ show: () => undefined, enableStandalone: () => false }),
});

config.yml:
media_library:
  name: 'disabled'


nuxt/kit addImports not working

Environment

Operating System: Windows_NT
Node Version:     v16.18.1
Nuxt Version:     3.2.0
Nitro Version:    2.2.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
I created new nuxt module with nuxi init
npx nuxi init -t module my-module
Describe the bug
I'm creating a nuxt module and I've run into an issue where I can't auto import composables in the playground , this a fresh install.
{
  "name": "nuxt3-auth-module",
  "version": "1.0.0",
  "description": "My new Nuxt module",
  "license": "MIT",
  "type": "module",
  "exports": {
    ".": {
      "types": "./dist/types.d.ts",
      "import": "./dist/module.mjs",
      "require": "./dist/module.cjs"
    }
  },
  "main": "./dist/module.cjs",
  "types": "./dist/types.d.ts",
  "files": [
    "dist"
  ],
  "scripts": {
    "prepack": "nuxt-module-build",
    "dev": "nuxi dev playground",
    "dev:build": "nuxi build playground",
    "dev:prepare": "nuxt-module-build --stub && nuxi prepare playground",
    "release": "npm run lint && npm run test && npm run prepack && changelogen --release && npm publish && git push --follow-tags",
    "lint": "eslint .",
    "test": "vitest run",
    "test:watch": "vitest watch"
  },
  "dependencies": {
    "@nuxt/kit": "^3.2.2"
  },
  "devDependencies": {
    "@nuxt/eslint-config": "^0.1.1",
    "@nuxt/module-builder": "^0.2.1",
    "@nuxt/schema": "^3.2.0",
    "@nuxt/test-utils": "^3.2.0",
    "@nuxtjs/eslint-config-typescript": "^12.0.0",
    "changelogen": "^0.4.1",
    "eslint": "^8.34.0",
    "eslint-config-prettier": "^8.6.0",
    "eslint-plugin-prettier": "^4.2.1",
    "nuxt": "^3.2.0",
    "prettier": "^2.8.4",
    "typescript": "^4.9.5",
    "vitest": "^0.28.4",
    "vue-tsc": "^1.0.24"
  }
}

 // src/modules.ts

  setup(_moduleOptions, nuxt) {
    const resolver = createResolver(import.meta.url);

    // add the plugin
    const runtimeDir = resolver.resolve('./runtime');   // var to path of runtime
    nuxt.options.build.transpile.push(runtimeDir);

    addPlugin(resolver.resolve(runtimeDir, 'plugin')); // add plugin to nuxt

    addImports({
      name: 'useAuth',
      as: 'useAuth',
      from: resolver.resolve('runtime/composables/useAuth'),
    });
  },

// src/runtme/composables/useAuth.ts

export const useAuth = () => {
  return {
    login: 'testing composable',
  };
};

I've also tried addImprtsDir and no luck either
and I also tried the nuxt.hook

nuxt.hook('imports:dirs', (dirs) => {
      dirs.push(resolver.resolve(runtimeDir + '/composables'));
    });

I get an error that useAuth is undefined and I have to import it from  import { useAuth } from '#imports';
app.vue inside playground folder
<template>

Nuxt module playground!

  <Auth />
</template>

How can I get this to work?
Additional context
No response
Logs
No response

You are experiencing this in the module starter because we deliberately disable auto-imports while developing a module:
https://github.com/nuxt/starter/blob/module/.nuxtrc#L1
The issue was that auto-imports won't work in node_modules so it was very easy for module authors to rely on auto-imports in their runtime code when developing their module.
Ideas for better ways of handling this are very welcome, and we should probably add a note to the module author documentation (or a comment in the module starter codebase).


Aurelia Webpack EsNext - package.json build resources "path" not being scanned when longer than one segment

I'm submitting a bug report

Aurelia Skeleton Version
skeleton-esnext-webpack
Operating System:
OSX 10.10.5
Browser:
all
Language:
ESNext

Current behavior:
I'm using
"aurelia": {
    "build": {
      "resources": [
       {
        "bundle": "homepage",
        "path": "application/homepage/homepage",
        "lazy": true
       }
      ]
    }
  },

and have these paths available in my project:
src/application/homepage/homepage.html
src/application/homepage/homepage.js
src/application/homepage/homepage.less
when running npm run build:prod
I get aurelia.da132ba….bundle.js:9 ERROR [app-router] Error: Template markup must be wrapped in a
I have pulled a fresh version of the webpack skeleton and moved the users.html and users.js into a the same structure.
src/application/users/users.html
src/application/users/users.js
and I also fixed the route to point to this path via...
{ route: 'users',         name: 'users',        moduleId: './application/users/users',        nav: true, title: 'Github Users' },
And I have changed the package.json to include:
"aurelia": {
    "build": {
      "resources": [{
        "bundle": "users",
        "path": "application/users/users",
        "lazy": true
      }]
    }
  },

However I am still getting the same error.  How can I get this fixed?
Expected/desired behavior:
I should not get this error when doing a prod build.

Would you please post a repository with the changes made?

@niieani This seems to happen when visiting http://aurelia.trekeffect.com/#/users and doing a hard reload.
Clone my repo here https://github.com/jasonbiondo/AureliaWebPackIssue
Run "npm run build:prod" and hit the above url.  Let me know if you know of a solution.

I'll add it to my long-standing list of issues of the current Aurelia+Webpack implementation. I'm working on a rewrite that solves all the issues present in the loader-webpack and webpack-plugin repos. Probably won't be solved until around November though.

@niieani thanks for the response.  I understand you probably have a lot on your plate, but I'm looking to put out a production build of http://trekeffect.com converted to Aurelia before November.  We were using Aurelia CLI but it couldn't handle the code chunking.  Now I just spent the last two days migrating it to Webpack but it seems this doesn't fully work either when you have dynamic routes (an extremely common issue for pretty much every application).
Anyway you can coach me on how to get a successful build out before November?  We are trying to get this project out and pushed to QA for testing.

I don't completely understand why this error appears: "Template markup must be wrapped in a element" yet. It might be something trivial.
If you'd like to expedite this we could do an hour or two of paid consulting next week to try and debug this.

I have the same issue. It seems that the JS files are not recognized when the html + js file sit in a subfolder and when referencing that folder in the router like subfolder/view.
When i put an alert or console.log in the constructor or attached method i never see that output.

Thanks for the confirmation @arnonuem. I'll be analyzing this as soon as possible.

https://cdn.meme.am/instances/500x/66328607.jpg

Hey guys,
Any update on this issue?  I'd like to be able to start testing a production version of my app asap.
Thanks,
Jason

@jasonbiondo sorry, not yet. November timeline still valid though.

Fixed by https://github.com/aurelia/skeleton-navigation/pull/714. No more build.resources though, use PLATFORM.moduleName instead.


Translations update from Hosted Weblate

Translations update from Hosted Weblate for Metadata Remover/Metadata.
It also includes following components:

Metadata Remover/Metadata Remover

Current translation status:

Thank you so much for your support, @Osama-Muzaffar! 😘


Correctly add detail to validation exceptions.

DRF exceptions apparently don't handle messages in the same way as Python's do by default.

r+

Thanks! Waiting on tests to pass, missed one thing.


Registry Gargage Collection job uses hardcoded docker image bitnami/kubectl

While evaluating kube-image-keeper 1.6.0, I noticed the following issue with the helm chart:

the pod spawned from the kube-image-keeper-registry-garbage-collection cronjob fails with ImageInspectError

$ kubectl create job mykuik -n kube-image-keeper --from cronjob/kube-image-keeper-registry-garbage-collection
job.batch/mykuik created

$ kubectl get pod -n kube-image-keeper | grep mykuik
mykuik-jfmfz                                     0/1     ImageInspectError   0          5m18s

$ kubectl describe pod -n kube-image-keeper mykuik-jfmfz | tail -n 5
  Type     Reason         Age                     From               Message
  ----     ------         ----                    ----               -------
  Normal   Scheduled      5m49s                   default-scheduler  Successfully assigned kube-image-keeper/mykuik-jfmfz to vm1.migration-brain
  Warning  Failed         3m50s (x12 over 5m49s)  kubelet            Error: ImageInspectError
  Warning  InspectFailed  45s (x27 over 5m49s)    kubelet            Failed to inspect image "bitnami/kubectl": rpc error: code = Unknown desc = short-name "bitnami/kubectl:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf.d/01-unqualified.conf"`

The reason is that the podspec in the cronjob job template references the bitnami/kubectl image which is unqualified and I have configured my system to refuse running unqualified docker images (the cronjob would have run if the docker image name was docker.io/bitnami/kubectl for example).
Since the docker image name is hardcoded in the helm chart I recommend to move it to values.yaml so that integrators can use a different kubectl docker image to run the cronjob.

I can volunteer for a PR to the helm chart, this should be quite easy.

:tada: This issue has been resolved in version 1.7.0-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ServiceAccount interface definition errors

the ServiceAccount interface specifies the member variables using camel case but they come in from Google Cloud JSON download as snake case and if changed in the JSON file to match the interface, when exporting the JSON file path in GOOGLE_APPLICATION_CREDENTIALS to work with other Google Cloud services locally in the emulator https://firebase.google.com/docs/functions/local-emulator#set_up_admin_credentials_optional it gives error {"result":"The incoming JSON object does not contain a client_email field"}
https://github.com/firebase/firebase-admin-node/blob/2e48327390dd25971944a066b4246c5eef8302cd/src/index.d.ts#L35
  interface ServiceAccount {
    projectId?: string;
    clientEmail?: string;
    privateKey?: string;
  }

ServiceAccount interface is used by the admin.credentials.cert() function. And that function is programmed to accept both camel case and snake case attributes. Therefore you don't have to modify downloaded service account JSON files to satisfy the interface. If you do it will most certainly break the OAuth flow.
One of the following should work for pretty much any use case:
// loading from file system
admin.credentials.cert('path/to/file.json');

// loading from the env (json contents in variable)
admin.credential.cert(process.env['GOOGLE_APPLICATION_CREDENTIALS']);

// loading from the env (file path in variable)
const obj = require(process.env['GOOGLE_APPLICATION_CREDENTIALS']);
admin.credential.cert(obj);

@hiranya911 - I am facing this issue when trying something similar to the last code snipped you posted.
import * as serviceAccount from "./serviceAccountKey.json";
admin.credential.cert(serviceAccount)

Here is the linter message:
Argument of type '{ "type": string; "project_id": string; "private_key_id": string; "private_key": string; "client_email": string; "client_id": string; "auth_uri": string; "token_uri": string; "auth_provider_x509_cert_url": string; "client_x509_cert_url": string; }' is not assignable to parameter of type 'string | ServiceAccount'.
  Type '{ "type": string; "project_id": string; "private_key_id": string; "private_key": string; "client_email": string; "client_id": string; "auth_uri": string; "token_uri": string; "auth_provider_x509_cert_url": string; "client_x509_cert_url": string; }' has no properties in common with type 'ServiceAccount'.

Basically it expects camel case keys, while the json file come with snake case, as described by @dgobaud .

Just require() the file instead of importing it (see my example above). If you insist on importing, then you should do something like the following:
import serviceAccount from "./serviceAccountKey.json";
admin.credential.cert({
  privateKey: serviceAccount.private_key,
  clientEmail: serviceAccount.client_email,
  projectId: serviceAccount.project_id,
});

But this must be a bug right? We want the type checking shouldn't the type match the data?

It seems a conscious effort has been made to keep snake-cased attributes out of the typings. I'm not sure why, but I guess it's a style-related choice made by the original developers of this library. This interface is quite old (last modified over 2 years ago), and it hasn't changed since I joined the project.
We can add the snake-cased properties to the interface as a solution. But given that there are simple workarounds, and this is the first time this issue has come up in over 2 years, I'm not sure if it's even necessary.
Does the problem occur only when the service account json is imported as a module? Any other ways to reproduce the issue?

I think think this is it and thinking about it more I think you have a good enough point it isn't necessary the JSON format match the interface so probably can leave it. Below I think makes sense as the way to do it.
import serviceAccount from "./serviceAccountKey.json";
admin.credential.cert({
  privateKey: serviceAccount.private_key,
  clientEmail: serviceAccount.client_email,
  projectId: serviceAccount.project_id,
});

This seems to work:
import admin from 'firebase-admin';
import serviceAccount from './serviceAccountKey.json';

admin.initializeApp({
  credential: admin.credential.cert(serviceAccount as admin.ServiceAccount),
  databaseURL: 'https://twisteringo-310c3.firebaseio.com',
});

TL;DR: The types are wrong in the SDK, but instead of just fixing them, you're advising every single (TypeScript) client of your SDK to hack their code.
Given you say that the function actually does support snake_case, why don't you just fix the type?
export interface ServiceAccountSnake {
  project_id?: string
  client_email?: string
  private_key?: string
}

...

function cert(
    serviceAccountPathOrObject: string | _admin.ServiceAccount | _admin.ServiceAccountSnake,
    httpAgent?: Agent): admin.credential.Credential;

This seems to work:
  credential: admin.credential.cert(serviceAccount as admin.ServiceAccount),

This is the cleanest hack today, but don't forget that it is a straight-up lie! You're asserting to TypeScript that your snake_case config is camelCase. You get away with it because the real JS implementation doesn't care what TS thinks & happily accepts snake_case. If the SDK were to drop snake_case support in the future, your code would runtime error (TypeScript would continue to trust your assertion).


[TCD-1741] Clarify Get Specific User API Call

Description
Updated the Get Teams and Get Users API definitions to more clearly reflect them as "query" calls, and clarified that the "Get Specific Team/User" API calls require the ID parameter, which must be looked up with the aforementioned query call.
Motivation and Context
The team-management API introduced a change in its calls that requires the ID of a team or user to make any API requests related to that entity. The previous API allowed username to be the identifier. The change is problematic because the only way to obtain the user or team ID is to retrieve it using another API (username is available in the SL UI on the profile page). The shift is causing some frustration , so this is an attempt at clarifying the behavior.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[X] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hey @spider-sauce -- Hoping this change helps us document our way out of the design flaw. ;) Let me know what you think.


Azure web app Windows : Stack is empty

Bicep version
Bicep CLI version 0.13.1 (e3ac80d678)
Describe the bug
Azure web app Windows : Stack is empty
To Reproduce
siteConfig: {
      numberOfWorkers: 1
      acrUseManagedIdentityCreds: false
      alwaysOn: true
      http20Enabled: false
      functionAppScaleLimit: 0
      minimumElasticInstanceCount: 0
      ftpsState: 'Disabled'
      healthCheckPath: '/api/health'
      netFrameworkVersion: netFrameworkVersion
    }

go to portal, stack is empty
Additional context
if I Add
siteConfig: {
   **metadata: [{
                name : 'CURRENT_STACK'
                value : 'dotnetcore'
            }]**

il looks like working

Based on this thread, I think this metadata property with that object is required:
https://github.com/Azure/bicep/issues/3314#issuecomment-876136647
Is the issue that you expected this to be handled by netFrameworkVersion?
cc @seligj95

For Linux web app  , setting LinuxFxVersion is enough to set both stack and net version.
One would expect netFrameworkVersion does the same
Using the metadata section generates a warning when bicep is run.
And , btw, why we need two different ways to pickup the desired net version depending on the os ?


elementary-xfce-icon-theme: 0.15.1 -> 0.15.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/shimmerproject/elementary-xfce/releases.
meta.description for elementary-xfce-icon-theme is: "Elementary icons for Xfce and other GTK desktops like GNOME"
meta.homepage for elementary-xfce-icon-theme is: "https://github.com/shimmerproject/elementary-xfce"
meta.changelog for elementary-xfce-icon-theme is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.15.2 with grep in /nix/store/dsqmr8i74fx3844bp0xwazg2k63w0q6a-elementary-xfce-icon-theme-0.15.2

directory tree listing: https://gist.github.com/8bc15c3b661a71db19a85b18493e9d76

du listing: https://gist.github.com/4e48a0fffdea706d538b0975b7d2d901

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
elementary-xfce-icon-theme

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dsqmr8i74fx3844bp0xwazg2k63w0q6a-elementary-xfce-icon-theme-0.15.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dsqmr8i74fx3844bp0xwazg2k63w0q6a-elementary-xfce-icon-theme-0.15.2
ls -la /nix/store/dsqmr8i74fx3844bp0xwazg2k63w0q6a-elementary-xfce-icon-theme-0.15.2/bin

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

1 package built:

elementary-xfce-icon-theme

Maintainer pings
cc @davidak for testing.

Minor release for Xfce 4.16 icons.

Add 32px versions of drive-removable-media, xfce4-panel, and xfwm4
Add symbolic links for all of the new Xfce 4.16 icons (#220)

Minor release for Xfce 4.16 icons.

Add 32px versions of drive-removable-media, xfce4-panel, and xfwm4
Add symbolic links for all of the new Xfce 4.16 icons (#220)