Compatiblity djangae error 500

I'm currently trying to setting up django-nose in my project.
I also use Djangae (https://djangae.readthedocs.org/en/latest/) for my app engin compatibility.
I add 'django_nose' in my INSTALLED_APPS I set TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'
Launching "python manage.py test" is not raising any exception.
But when I want to launch the server with "python manage.py runserver", the server is running but when I try to call "localhost:8000" I get :
    ERROR    2016-03-23 15:59:49,299 wsgi.py:263]
Traceback (most recent call last):
  File "/Users/briva/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 240, in Handle
    handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
  File "/Users/briva/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 299, in _LoadHandler
    handler, path, err = LoadObject(self._handler)
  File "/Users/briva/google-cloud-sdk/platform/google_appengine/google/appengine/runtime/wsgi.py", line 96, in LoadObject
    __import__(cumulative_path)
  File "/Users/briva/Desktop/dangoptest/dangoptest/wsgi.py", line 18, in <module>
    application = DjangaeApplication(get_wsgi_application())
  File "/Users/briva/Desktop/dangoptest/lib/django/core/wsgi.py", line 13, in get_wsgi_application
    django.setup()
  File "/Users/briva/Desktop/dangoptest/lib/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/briva/Desktop/dangoptest/lib/django/apps/registry.py", line 85, in populate
    app_config = AppConfig.create(entry)
  File "/Users/briva/Desktop/dangoptest/lib/django/apps/config.py", line 90, in create
    module = import_module(entry)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "lib/django_nose/__init__.py", line 5, in <module>
    from django_nose.runner import BasicNoseRunner, NoseTestSuiteRunner
  File "lib/django_nose/runner.py", line 61, in <module>
    from django.test.simple import DjangoTestSuiteRunner as DiscoverRunner
ImportError: No module named simple

Thanks for answers.

Given that https://github.com/potatolondon/djangae/issues/633 has been closed, I think this issue can be closed too.


feat: Loading modal for actions

PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context
changed: buy, list, mint nft , mint colelction

[x] Closes #8061

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI;

long modal, with scroll

Copilot Summary

🤖[deprecated] Generated by Copilot at d3c236d
This pull request introduces a new BoxedModal component that standardizes the appearance and behavior of the modal components. It also refactors the ConfirmPurchaseModal.vue component to use the new BoxedModal and to show a loading state based on the user's balances. Additionally, it adds a new loading animation for the dots element and cleans up some code.

🤖[deprecated] Generated by Copilot at d3c236d

We're trapped in a modal of doom
Waiting for the balances to load
The dots are spinning in a loop
The BoxedModal is our only hope

i know its a draft but the close x-mark icon does not work on both modals (loading, loaded)

still not a fan of the name tbh
i think it should reflect the fact that it adds loading UI around the slot

well it does add a prop with loading but you don't have to use it , and can have the title box and the body
any suggestions

i would wait for #8136 to be merged before this one, wdyt?

Is there an estimation of the modal height that is after that?

I think in this case we can make the rescalling possible.
I did not like that it was before or after the auto teleport loaded. This will be okay (loading modal, once loaded it opens a modal that is slightly larger)

https://github.com/kodadot/nft-gallery/assets/90852205/69a25f87-f935-403b-8128-0d031a9276b5
Or make the loading modal higher?

because here we are restricting so much of the vertical space imo

Or make the loading modal higher?

yes, prev max modal height was 50vh now 70vh
https://github.com/kodadot/nft-gallery/assets/44554284/e0506504-88dc-492e-8004-9625f5d9aa86

oki oki. we can always make follow-up, tried it now and it's working nicely, thanks!
ready to be merged? So we can continue to #8163

blocked as suggested on https://github.com/kodadot/nft-gallery/pull/8124#issuecomment-1819584672

👀

I think there's been a lot of change for a modal, can we do it with less code change? maybe without NeoModalBody?

@roiLeo  I'm not sure what to say,
you mean this solution has more code than it should ?
could you please elaborate
thanks

I think there's been a lot of change for a modal, can we do it with less code change? maybe without NeoModalBody?

@roiLeo I'm not sure what to say,

maybe no need to add a skeleton to the whole component (title, body). Just add a skeleton to the fee/deposit section and below. Because loading depends on const loading = computed(() => !autoteleport.value?.hasBalances) in this PR. So, we don't need to create a new component for this
I don't think the title and some components on the body need to wait to load

I don't mind, makes sense just following the design  cc @exezbcz

Would you be ready for merge? cc @hassnian

on it

I don't mind, makes sense just following the design cc @exezbcz

I am not really fan of landing a modal that is not loaded. Having a loader and then getting to a modal that is 100% ready is IMO better UX.

Yeah, this was the reason
The thing why the whole modal: rest of the modal apart from the auto teleport does not need to be loaded, so you see that. After teleport loads, it resizes the modal. One step is better for me.
we can always iterate, but right now it makes sense to me to show this loading modal

I would move NeoModalBody component inside kodadot repo since you add logic & text inside

sure, it was prev there I'll move it back

fast tracking
pay 70 usd

😍 Perfect, I’ve sent the payout
💵 $70 @ 5.16 USD/DOT ~ 13.566 $DOT
🧗 13QUj3pZyFNfYj4AM336hRdyLQbevj5H3sR4PKmLEXLdwZhh
🔗 0x0000f0c756be0b6889c48e848fbd55e6f95f4b053c04c1d919559e98c5171121
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Add application platform support to SNS

SNS has a couple of endpoints so you can use it to send push notifications to mobile devices and this PR adds support for that. I had trouble running the full test suite but mix test test/lib/ex_aws/sns_test.exs runs fine with no errors.

Hey there sorry I'm just noticing this, our slack integrations got messed up and I missed out on some PRs. Thanks!


HTML <title>s

Right now, the <title>s of all the pages just say Lean community, which isn't brilliant when a user may have multiple pages open at the same time, or if they want to search for something, as they'll have to look at the URL to find what they want.
Also it might help when people are looking for things using a search engine? Although right now Google is the only search engine that even finds any of the install pages, and it's smart enough to pull in the <h1>.
It might make more sense to use the markdown titles for the HTML <title> tags.

Do you plan to work on this or are you only opening the issue to draw our attention to this suboptimal situation? Also I'm not sure what you call the "markdown title". Do you mean the filename of the first h1 contained in the file? Both are possible of course, falling back on the current unhelpful title if a markdown file doesn't contain a h1. The only advantage of the filename is that it's shorter.
If you are interested in working on this then I can explain stuff if needed. Otherwise I'll put it on my huge pile of stuff to do (unless Bryan or someone else does it first).

I'm happy to look into this (probably next week at earliest) if @shingtaklam1324 doesn't feel up to it.

More to draw attention to this. And yes, I do mean the first h1. Right now, Google already uses the h1 as part of the search result when looking for pages on leanprover-community.github.io.
I've taken a look at the repo to see how the page title could be set, but I'm not sure how any of this works, so if Bryan wants to do it it'd probably be better,

I don't think Bryan wants to do it. He is ready to do it. The actual question here was: would you like to learn stuff by doing this, and then be happy with what you'll done, or do you have enough nice projects, or maybe don't want to learn stuff in this direction?
I started to write a long explanation about our site building procedure, but then I noticed some details that makes the implementation harder than I thought yesterday. It requires a bit of refactoring, so I'll do it myself, especially since I already spent some time thinking about it.

Oh right I see, I misunderstood his message when skimming through the thread. Apologies if my comment seemed like I was suggesting that he should do it.
I don't think I know enough about Python/Jinja to be able to really make a start with this, hence I wasn't sure about it in the first place, and to be perfectly honest, I'm not that interested in learning about using Jinja.
Nonetheless, thank you very much for making the changes!


Add  bullet-item component story

This PR adds missing story for bullet-item component.

:tada: This PR is included in version 7.7.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


No googlesearch module

I've followed the instructions from the readme, run main.py and get the following error:
\Robo-GPT\robo-gpt\action_runner.py", line 9, in
from googlesearch import search
ModuleNotFoundError: No module named 'googlesearch'
What have I missed?

The most likely reason is that you either didn't create the pipenv shell (pipenv shell) or didn't install the pipenv dependencies (pipenv install) before trying to run the program (python robo-gpt/main.py).


nixos/rename: fix evaluation

Motivation for this change
cc @svanderburg

@GrahamcOfBorg eval

Oh, I just pushed https://github.com/NixOS/nixpkgs/commit/e2a32b747fd6a1291540064b82ab43a37efad635

fine for me, TBH I don't understand why it was renamed in first place…


Observable.zip: use Options

Some update where potentially missed.
(mayne not on Store as I think the immediate callback would have mitigated the issue, not sure).

This looks like a sensible change (thank you), was there a use case that failed previously?

I haven't found one. I just happened to look into Observable.zip as it was in the call stack of some issue I was troubleshooting - I think it was unrelated.

Thank you!


Update dependencies

This PR upgrades Starlette (vulnerability) (already done by #821 for front/ - this PR also fixes services/admin and services/api)
It also upgrades all the dependencies to the next minor version. I checked the important ones: starlette, uvicorn.
And nearly all the changes come from the upgrade of mypy to v1 -> I fixed a lot of types, and it exposed some (not critical) bugs.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Codecov Report
Base: 90.66% // Head: 89.08% // Decreases project coverage by -1.58% :warning:

Coverage data is based on head (d898bf9) compared to base (f43a0d2).
Patch coverage: 93.58% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #823      +/-   ##
==========================================
- Coverage   90.66%   89.08%   -1.58%
==========================================
  Files         105       71      -34
  Lines        5292     3024    -2268
==========================================
- Hits         4798     2694    -2104
+ Misses        494      330     -164

Flag
Coverage Δ

jobs_mongodb_migration
80.09% <72.72%> (-0.20%)
:arrow_down:

libs_libcommon
92.90% <96.21%> (+0.07%)
:arrow_up:

services_admin
87.32% <91.02%> (+0.47%)
:arrow_up:

services_api
89.34% <100.00%> (+0.07%)
:arrow_up:

services_worker
?

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

Impacted Files
Coverage Δ

services/admin/src/admin/routes/cancel_jobs.py
55.00% <0.00%> (ø)

services/admin/src/admin/routes/jobs_duration.py
55.00% <0.00%> (-2.90%)
:arrow_down:

...s/mongodb_migration/src/mongodb_migration/check.py
34.48% <37.50%> (-4.23%)
:arrow_down:

jobs/mongodb_migration/tests/conftest.py
78.57% <75.00%> (-3.25%)
:arrow_down:

libs/libcommon/tests/conftest.py
73.91% <75.00%> (-2.56%)
:arrow_down:

services/admin/tests/fixtures/hub.py
86.20% <76.92%> (+0.32%)
:arrow_up:

libs/libcommon/src/libcommon/queue.py
95.20% <88.57%> (-0.87%)
:arrow_down:

services/admin/src/admin/routes/dataset_status.py
91.66% <91.66%> (ø)

libs/libcommon/tests/test_queue.py
99.00% <99.00%> (-0.37%)
:arrow_down:

...bs/mongodb_migration/src/mongodb_migration/plan.py
100.00% <100.00%> (ø)

... and 65 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

OK, once conflicts with main resolved...

Done.
@lhoestq I fixed some details from #809, see:

get mypy happy: https://github.com/huggingface/datasets-server/pull/823/commits/44531554ccc3b903acb32673dd8d68203c0db35a#diff-6636f2a4e026dc2652c3feed9369d0442a781b96a77cac10feab7e1f64d8d648R506
add from error to get the complete traceback: https://github.com/huggingface/datasets-server/pull/823/commits/44531554ccc3b903acb32673dd8d68203c0db35a#diff-6636f2a4e026dc2652c3feed9369d0442a781b96a77cac10feab7e1f64d8d648R506 (it's redundant with the argument, we might be able to fix that in CustomError)
I had to split your test function in two, because I don't know how to type it: https://github.com/huggingface/datasets-server/pull/823/commits/44531554ccc3b903acb32673dd8d68203c0db35a#diff-1690e9f8283cb9406a2585171e8f44dee147dbc7124d9bdff13520635cd83170R234. It's how I do it for the other tests everywhere, for that reason.

Once merged, all the current PR will need a rebase (or a merge, but... I still think it's cleaner to rebase)

Please don't hate me


Buzzer support

Nice work on this project! I am planning to modify your code to enable a buzzer which would warn of impending pushback, i.e. when battery-to-board current goes above a certain threshold. Are you thinking to add this type of feature at some point?

I just finished installing the chip, it is a tight fit! There was not enough room to mount the buzzer directly to the board so I ran it out towards the charger port (buzzer is in red shrink-wrap at the bottom of the picture). I opted to attach the buzzer to 3.3V and D7 (GPIO13). I put a startup beep sequence in the code and so far it seems to be working. The buzzer I had on hand is a bit too quiet unfortunately. I don't know if a louder buzzer would still be able to fit in the case. Regardless, I plan to do some testing next week. I am on the Pint so I set the code to beep when the current goes above 10A. We'll see how it goes.

Sorry I got no plans to support this, I am not convinced that Owie/BMS information is enough to provide what you're trying to achieve.
10 amps at full charge with backing of a powerful battery or a VnR setup is different from 10 amps at 45 volts. What you really need is duty cycle of the PWM powering the motor.
Another issue you've bumped into yourself is the power needed to support any sort of loud buzzer. The BMS power supply doesn't have much juice. This was the reason behind me using ESP8266 as opposed to smaller ESP32 boards - The BMS would die with the WiFI modem turning on because it didn't have enough juice

Yep, I am abandoning this as well. Would be more flexible to build this feature into an app if ever. Pushback is always there as a warning and I don't think the owie chip can prevent pushback.
To clarify regarding beeper volume, the beeper itself is plenty loud and only draws <25 mA according to the spec sheet. The issue is that the sound is muffled by the waterproof casing of the Onewheel battery compartment. If there was a good way to mount outside the case then this would be less of a problem.


Add post about Joel / Kozo talk

@kozo2, I've started two pseudo drafts (based on the README) -- maybe we can populate it with a little more detail based on what's now a rough memory! :)
Great idea to get it started, though!


[Question]: does SubQuestionQueryEngine support streaming?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Does SubQuestionQueryEngine support streaming?  For example, how to stream response from docs/examples/usecases/10k_sub_question.ipynb?  Tried to add streaming=True to llm, lyft_engine, and uber_engine, but still couldn't get s_engine to produce streaming response.

A follow-up question: how to make SubQuestionQueryEngine work with Chainlit, as in the LlamaIndex-Chainlit integration example: https://docs.chainlit.io/integrations/llama-index ?

The bot's answer works for RetrieverQueryEngine, but not for SubQuestionQueryEngine.  I tried to add response_synthesizer to SubQuestionQueryEngine and call the query method, but the returned response object doesn't have print_response_stream or response_gen.
Any human insights?

Thanks @logan-markewich for the clarification.  It turns out that in the 10k_sub_question.ipynb example lyft_engine and uber_engine cannot have streaming=True too; with this removed the bot's suggestion is working now.
Closing this issue - though it would be nice to be able to stream answers to sub-questions :smile:


Title of Doc pages do not match the title in the navigation bar

The following topics need to have the same titles in the navigation and on the page:
Getting started:

Welcome
Run in Dev Environment
Add Custom Code
Deploy your app

*Community:

Handling a new issue

Also, the following need to be synced:
Customize your application:

Add business logic
Add REST API Action
Add GraphQL Query


Win copy field

Another setting in the dosomething campaign hot module setting grouping to allow for generic template copy when a campaign is in the win phase

again would prefer this being in a Win Module group
Let's have this field name be "Win Module Copy"

@deadlybutter for this we'll need the following variables:

[node:title]
[campaign_progress] (not sure if this is exactly what this is called)
[node:field_reportback_noun]
[node:field_reportback_verb]

@deadlybutter default copy:
"[campaign_progress] [node:field_reportback_noun] [node:field_reportback_verb]! That's amazing - thanks to everyone for rocking [node:title]. Let's keep it up! Add your contribution in the prove it section below."


fix: Enable to run broken TextureConverter Tests

PR Details
This PR fixes TextureConverter tests that previously couldn't even be run. In addition, I fixed a bug related to loading dds on Linux I detected by running unit tests
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] 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)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed. (Both on Linux and Windows)
[ ] I have built and run the editor to try this change out.

Thanks !


Feature/4618

Contributing to the AWS Control Tower Account Factory for Terraform
Thank you for your interest in contributing to the AWS Control Tower Account Factory for Terraform.
At this time, we are not accepting contributions. If contributions are accepted in the future, the AWS Control Tower Account Factory for Terraform is released under the Apache license and any code submitted will be released under that license.
If you have a feature request, please create an issue using the Feature Request template, thanks!

wrong repo


improve installation script

Currently the installation script has the following limitations:

always download the latest version
cant be told to download a specific version

The proposal is to base the installer script either on the Helm installer or leverage godownloader

The Helm installer looks good


Enable CodeQL for scheduled CI jobs

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run python - storage-blob - tests

/azp run python - storage - tests

/azp run python - storage - tests

/azp run python - cosmos

/azp run python - cosmos

/azp run python - cosmos

/azp run python - cosmos


feat(core): Change Operator and Builder Pod user as non root 1000

Motivation
Since the new builder pod is configured to run with non root user and a persistent volume has been created there have been some permission/copy issues I fixed while working on #4297. The permissions issues can be fixed two different way on kubernetes security : extend root user or extend non-root user.
Since it make more sense to try to avoid root (as a general rule) and some Dockerfile already use user with ID 1000 (same for group ID), I made some first modifications to try to have more non-root user for operator and builder pods.
There are also some warnings on integration containers security validations, but they will be dealt with #4297.
Description

Dockerfile : sets the group for folders used for dependencies is 1000
Force 1000 as User ID/ Group ID/FS Group ID to be coherent with the one declared in Dockerfile
Use 1000 on volume to ensure dependencies from camel-k-runtime can be added

Release Note
Extend usage of non-root user (1000) on operator and builder pods

Check failure because #4408


Accounts needed

I have recently had a customer use this article to set up communication credits and after speaking to support have a suggestion to make.
After step 5 there is a blue box which talks about EA customers being able to bill communication credits to their EA. If the customer wants to go down this route they need to use a Global Admin account and not a Billing Admin account. If you use a billing admin account the option is not shown.
Maybe we could add a note to help other customers?
ta
Rich

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

ID: 277cf140-5c6c-82c7-cc56-490ef2188754
Version Independent ID: 72e7de29-fd71-23bf-15a7-172634c2a5fd
Content: Set up Communications Credits for your organization - Microsoft Teams
Content Source: Teams/set-up-communications-credits-for-your-organization.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Add ClientUriBuilder helper class implementation

Fixes: https://github.com/microsoft/typespec/issues/3680

API change check
API changes are not detected in this pull request.


Initial setup gets stuck when discovering android TV

Using the docker command to install it gets stuck at connected to TV, its running android TV 11. IsponsorBlock stopped working as well. Can provide details if you tell me how.

It looks like it successfully connected to all of your devices, so I don't think it's stuck. Does it never skip videos? Could you run again with --env=LOG_LEVEL=debug?

The problem is solved, the issue was the missing api key.


Reading files written by parquet-go fails in pandas using pyarrow

Error returned by pyarrow:
Not yet implemented: Unsupported encoding.

I am able to read and write the file in parquet-go, here is an example of how I am writing it out right now:
//The struct is used for csv & parquet
type Data struct {
	PropertyKeyID                       int64   `csv:"PropertyKey_ID" parquet:"PropertyKey_ID"`
	Dealid                              int64   `csv:"Deal_id" parquet:"Deal_id"`
	Propertyid                          int64   `csv:"Property_id" parquet:"Property_id"`
	Portfolio                           string  `csv:"Portfolio" parquet:"Portfolio"`
	Propertynb                          int64   `csv:"Property_nb" parquet:"Property_nb"`
	Statustx                            string  `csv:"Status_tx" parquet:"Status_tx"`
	Statusdt                            string  `csv:"Status_dt" parquet:"Status_dt"`
	IntConveyednb                       string  `csv:"IntConveyed_nb" parquet:"IntConveyed_nb"`
	IntConveytx                         string  `csv:"IntConvey_tx" parquet:"IntConvey_tx"`
	TransTypetx                         string  `csv:"TransType_tx" parquet:"TransType_tx"`
}

schema := pq.SchemaOf(new(Data))
pw := pq.NewGenericWriter[Data](pqWriter, schema)
defer pw.Close()
_, err = pw.Write([]Data{data})
if err != nil {
	return errSummary, err
}

If I load up the file and just read it in in go I can read it back into the struct and get all the values. Is there a way to write it out in a compatible way for pyarrow or any library in python to read it into a dataframe?

I think I figured it out, if you change the encoding type for strings to dict everything seems to work. Example:
type Data struct {
	PropertyKeyID                       int64   `csv:"PropertyKey_ID" parquet:"PropertyKey_ID,snappy"`
	Dealid                              int64   `csv:"Deal_id" parquet:"Deal_id,snappy"`
	Propertyid                          int64   `csv:"Property_id" parquet:"Property_id,snappy"`
	Portfolio                           string  `csv:"Portfolio" parquet:"Portfolio,dict,snappy"`
	Propertynb                          int64   `csv:"Property_nb" parquet:"Property_nb,snappy"`
	Statustx                            string  `csv:"Status_tx" parquet:"Status_tx,dict,snappy"`
	Statusdt                            string  `csv:"Status_dt" parquet:"Status_dt,dict,snappy"`
	IntConveyednb                       string  `csv:"IntConveyed_nb" parquet:"IntConveyed_nb,dict,snappy"`
	IntConveytx                         string  `csv:"IntConvey_tx" parquet:"IntConvey_tx,dict,snappy"`
	TransTypetx                         string  `csv:"TransType_tx" parquet:"TransType_tx,dict,snappy"`
}

Hello, thanks for reporting the issue!
Parquet is a complex file format, it appears that pyarrow does not support the DELTA_LENGTH_BYTE_ARRAY encoding that parquet-go uses by default, and is documented as being the default in the parquet specification.
Adding the dict tag switches to dictionary encoding, you may also use plain to force plain encoding which all libraries should support.

I appreciate your help looking at this.


Improvements to helpers.almostWhole

This is the agreed upon parts of https://github.com/chartjs/Chart.js/pull/5992. I'm going to close that PR for the time being to keep the review queue clear until we have an agreed upon path forward

Makes epsilon inclusive and adds corresponding tests for almostWhole. Thanks @costerwi for the suggestion in https://github.com/chartjs/Chart.js/pull/5992
Add additional tests for decimalPlaces as suggested by @kurkle in https://github.com/chartjs/Chart.js/pull/5992/files#r249953203

@benmccann can you resolve conflicts then we can merge?

@simonbrunel I've rebased this PR. Thanks for the review


Pressing backspace in text field should delete entire emoji, even when its a compound emoji

Describe the bug
Certain characters, like flags or family emojis, are compound symbols made up of multiple unicode characters. For example:

These are expected to be deleted with a single "backspace" press. However, in Compose Multiplatform, they are handled as their individual joined pieces:
https://github.com/JetBrains/compose-multiplatform/assets/2178959/582c3510-b8d8-4fdd-b7c3-9512ebcd6c95
Affected platforms
Select one of the platforms below:

iOS (did not test on Desktop)

Versions
Compose 1.5.2
To Reproduce
Type 👩👩👧👧 into a text field and press backspace. Watch the individual family members disappear.
Expected behavior
The whole emoji should be deleted

Duplicate of #3104, should be fixed in the last beta

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


mrpt2: 2.4.0-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository mrpt2 to 2.4.0-1:

upstream repository: https://github.com/MRPT/mrpt.git
release repository: https://github.com/mrpt-ros-pkg-release/mrpt2-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: 2.1.3-1

Supersedes #31461

@jlblancoc a LICENSE file at the source repo root would be ideal (see contributing guidelines).

Thanks for the approval Michel! Mmm... We have such a file, named COPYING, as common in many other packages... It's recognized by the GitHub web interface for example, etc.

@jlblancoc indeed, I missed it the first time. Policy says there should be a LICENSE file, but I think that policy did not consider a COPYING file. @nuclearsandwich ?
At any rate I won't block a minor release.


VM Clone Validation - Fix Attached VM selector

Related issue https://github.com/harvester/tests/issues/1196

Tested on the staging run test pipeline.
Can PASS the VM clone Validation case

Related test job and test report

Test job:
http://<IP_ADDRESS>:8080/job/harvester-cypress-run-test/28/console

Test report:
https://minio.provo.rancherlabs.com:31524/cypress-test-report/cypress/results/20240624-145956-77e2a81/index.html


add new config sample and check scripts

This PR introduces new config system wiht bases.
Check script will be deleted before merge.
To test configs in this PR, please refer use mmcv from here https://github.com/open-mmlab/mmcv/pull/194
During refactor, the following principles are applied.

The base model (e.g. r50) of each method is composed of components.
The variations of base models are inherited from the closest base model.
For the inherited configs, only the updated key-value pairs are included.
_delete_ indicates the original dict will be deleted instead of updated, which is useful when two dicts have non-overlapped keys.

Notes:
faster_rcnn_r50_caffe_fpn_1x.py, guided_anchoring/ga_retinanet_r50_fpn_1x.py, guided_anchoring/ga_faster_r50_fpn_1x.py, retinanet_r50_caffe_fpn_1x.py, mask_rcnn_r50_caffe_fpn_1x.py, ms_rcnn/ms_rcnn_r50_fpn_1x.py, rpn_r50_caffe_fpn_1x.py, guided_anchoring/ga_rpn_r50_fpn_1x.py are not in the current configs. They are added for the convenience of inheritance.

Please refer to the updated PR first comment.


Make Appversion in operator.yaml templatable.

What this PR does / why we need it:
Make the version and appVersion variables in operator.yaml as a template to statefulset.yaml. This is still a WIP, and creating this PR as I need guidance in completing this.

Fixes #871

I modified the first-operator with {{ .AppVersion }} to test this, should I commit that too?? @alenkacz ^

@sivaramsk oh yeah, that would be lovely, thanks

Thanks @alenkacz. I will document the changes in that page.

Thanks @sivaramsk 🎉


Cannot unstake to TIME

I approved the unstaking on Meta Mask but no TIME shown in wallet, still MEMO. I retried unfortunately it says “Insufficient reserves” on Wonderland. I do still have enough AVAX for transactions. Anyone facing this issue before?

Me too. Are we being rug-pulled?

did you guys every figure this out?

Also getting this, would love to know solution! thanks

Same here

Guys, you can unstake your time right now, go for it!! I wouldn't use metaswap, it seems very sketchy with so few twitter followers.  Anyways, good luck!


Fix a potential compiler bug for CUDA-aware MPI call

This PR fixes a potential compiler bug while invoking the mpi_allreduce for communication.
Issue:

It turns out that the !$acc update host and !$acc update device directives around an MPI_ALLREDUCE call do not work properly and produce a wrong result in a GPU run unless the managed memory is used.

Solution:

use the "!$acc host_data use_device" directive
specify the array bounds explicitly in the "!$acc update host" and "!$acc update device" directives

Both solutions work so far and we decide to go with the first option since it enables the CUDA-aware MPI communication. No managed memory is needed for the new GPU run.
Verification result:
GPU run with managed memory (from https://github.com/george-bryan/CM1/pull/88):

Identical variables: 44
variables with red_diff > 1.e-6: 29
variables with red_diff <= 1.e-6: 13
four variables with largest error: KSVMAX, KSHMAX, VOR2KM, VOR1KM

GPU run without managed memory:

Identical variables: 44
variables with red_diff > 1.e-6: 29
variables with red_diff <= 1.e-6: 13
four variables with largest error: KSVMAX, KSHMAX, VOR2KM, VOR1KM

@sjsprecious, I noticed that there are other '!$acc update host()' that are associated with MPI reduction calls.  For example in solve1.F and solve2.F. Is there a particular reason why these were not modified?

@sjsprecious, I noticed that there are other '!$acc update host()' that are associated with MPI reduction calls. For example in solve1.F and solve2.F. Is there a particular reason why these were not modified?

Thanks for catching them. I do not modify them because it is a mpi_iallreduce call and thus skips from my grep search. Let me go through the code again and eliminate the potentially buggy !$acc update host directive.

@johnmauff I have removed additional !$acc update host() directives in other source code. The verification results remain unchanged. Let me know if you have further questions.

@sjsprecious Thanks for the updates.  It now looks good.


Just want to ask a few simple questions?

I notice that this app can load a model less than 1s. I am quite curious how this is done.
I also built a glTF renderer rustracer but it take me seconds or even tens of seconds to load a model.
And where are the shaders? I cannot find it in the src folder.

The model viewer uses https://github.com/playcanvas/engine as the renderer. You will find the GLB loader/parsing code, shaders etc there :)


compose done

separate binary operations between Distributions / Kernels into separate files + separate tests.

Codecov Report
Base: 82.81% // Head: 82.93% // Increases project coverage by +0.11% :tada:

Coverage data is based on head (1ace829) compared to base (5727e61).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
+ Coverage   82.81%   82.93%   +0.11%
==========================================
  Files          10       12       +2
  Lines         291      293       +2
==========================================
+ Hits          241      243       +2
  Misses         50       50

Impacted Files
Coverage Δ

src/kernels/dirackernel.jl
83.33% <ø> (-5.13%)
:arrow_down:

src/kernels/normalkernel.jl
85.71% <ø> (-3.18%)
:arrow_down:

src/invert.jl
100.00% <100.00%> (ø)

src/kernels/compose.jl
100.00% <100.00%> (ø)

src/marginalise.jl
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


The AtomInteger trait is not needed for Atomic::fetch_update

The function Atomic::fetch_update is only available for types that implement AtomInteger. However, it doesn't actually do any implicit integer operations like, say, fn fetch_add does — it explicitly leaves the update to a Rust closure that is restricted to safe operations on the data types. As such, the restriction is not needed, allowing fetch_update to be used on enum types, for example.
Here's my example that does not work with atomig as it is now:
#[derive(Atom, Copy)]
#[repr(u8)]
enum Enum {
    Off,
    On,
}

fn foo() {
    let t: Atomic<Enum> = Atomic::new(Enum::Off);
    t.fetch_update(Ordering::Relaxed, Ordering::Relaxed, |t0| Some(match t0 {
        Enum::Off => Enum::On,
        Enum::On => Enum::Off,
    }));
}

Somehow I managed to unwatch my own repository :astonished: I just now stumbled upon your comment by pure chance. Sorry for the delay!
The problem here is that fetch_update was not implemented for non-integer atomics in std for some time: https://github.com/rust-lang/rust/issues/78639
This seems to be a simple oversight though. AtomicBool::fetch_update and AtomicPtr::fetch_update were already added and their stabilization hits stable with 1.53, in roughly three weeks. I will wait till then to properly fix this issue. I will let you know once I release the fix as 0.3.

I just released 0.3 which has fetch_update for all T: Atom available, not only for T: AtomInteger.

Thanks


Avoid using multiple KDE4 kdelibs versions at the same time.

See https://github.com/NixOS/nixpkgs/issues/6883 for a detailed explanation of the problem with kdelibs. This PR implements the second approach suggested there. I've confirmed that a bunch of KDE4 software that I use run fine (including KDevelop, Konversation, and Akregator from kdeApps.kdepim). In the latter, there is no more problem with widget styles.
I think that the next step would be to manually move some KDE4 software from kdeApps by updating it in the kde4 expressions. This makes sense to me since it's still the same software just released differently. I see that it's a pain to maintain, but hopefully we won't see much KDE4 updates anyway.

This is fixed in master as we discussed in #6883. kde4 uses the updated kdelibs in kdeApps_stable by default. kde4 is also parametrized so that kdeApps_latest is built with KDE 4 libraries using the correct version of kdelibs.


Introduce Turbo.config object

The initial implementation aims to replace the ad hoc configurations spread across window.Turbo and Turbo.session. Those objects shouldn't be considered part of the public interface, especially for extension.
This commit exports a single object from src/core/config to serve as a centralized, user-facing repository for configuration values.
The main src/core/config object is composed of two constituent parts:

src/core/config/drive
src/core/config/forms

In the future, the directory structure can be expanded upon to suit the needs of the project.
Any user-facing configuration outside of Turbo.config is deprecated.

@afcapel @jorgemanrubia Trix utilizes a similar style of Object that consists of multiple modules scoped to particular concerns.

@jorgemanrubia @brunoprietog are either of you able to review this proposal?

Hey @seanpdoyle.  I was kind of surprised to learn of a change to Turbo's public API in a patch release.  But seeing as that ship has sailed, I have another question for you.
We maintain a package that integrates with Turbo.setConfirmMethod and wondering if you have an opinion on the best way to handle this change?
I'd rather not introduce branching logic based on the existence of a Turbo.config object. e.g.
  if (window.Turbo.config) {
    window.Turbo.config.forms.confirm = confirmationHandler
  } else {
    window.Turbo.setConfirmMethod(confirmationHandler)
  }

However, I'd also prefer not to entirely drop support for previous versions of Turbo.  Especially considering that I'm not offering any other reasons for upgrading our package other than you can't, unless you also upgrade Turbo itself.
I'm concerned that adding a peerDependency requirement only emits a warning that is easily overlooked, but will actually crash our package if left unmet.
I would appreciate any feedback you have on the matter.
Thank you,

Andy

our internal discussion: https://github.com/RoleModel/turbo-confirm/pull/31

@OutlawAndy thank you for sharing those details here. Personally, I am not involved in Turbo's release schedule, so I cannot provide any insights into that process. I will say that the deprecations in this diff were intended to buy time and provide hints to consuming packages.
This diff proposed the Turbo.config object to serve as the interface for configuring Turbo. Until the setConfirmMethod is removed, you can continue to call it instead of interacting with Turbo.config, but it is will emit a deprecation warning.
As far as the impacts to your package are concerned, I understand your distaste for adding a conditional to cover this case. However, if you are committed to maintaining support for all historical Turbo version, that decision involves supporting Turbo's full range of interfaces as they evolve. Turbo does not programmatically expose version information to the JavaScript runtime, so packages are left with graceful degradation-style conditionals to serve as safety nets.
Again, while I cannot speak to Turbo's release schedule or maintenance policies, I do believe that as the package and its interfaces evolve, there will be an evolving minimal threshold version that will serve as a baseline of backwards compatibility. For now, the deprecations keep Turbo.setConfirmMethod on the supported side of that threshold, but eventually that won't be true anymore.

I'm concerned that adding a peerDependency requirement only emits a warning that is easily overlooked

I think this ultimately boils down to your package's compatibility goals, but a peerDependency requirement feels one of the few concrete ways to encode your support goals to the consumers.

@seanpdoyle Thank you for the insightful response!  That's quite helpful!


"tag_classes" will be treated as css classes

Syntax of Pug for classes was not treated as css classes but as attributes.
It is not good because difference occured between css meta languages.

Please file is PR against https://github.com/davidrios/jade-tmbundle. We use that grammar as is and don't want to create our own fork. Once accepted there, I'll resync our grammar.


suggestion for performance

just a tiny change to improve memory usage. A weakmap entry get automatically removed when key get garbage collected. which would in this case only happen when you remove a switch. and therefor also no longer need the meta data you store in the map.
I would also suggest to create a custom element that extends the input element, this way you do not have to manually init each switch, and all switches added in runtime are also automatically initialized for you. with the current code if I were to add a new switch to the DOM it would not work with the drag. I do realise this is out of the scope of this challenge. but I estimate it is about the same amount of code, and sets a good example for beginners imo (custom elements / webcomponents are the future imo)

Nice! A custom element was a stretch goal, but didn't get the time. I'm hoping someone contributes one :wink wink wink wink: 🙂

loved the video, nice and concise and to the point 👌

I'm hoping someone contributes one
😉😉😉


I think I have a problem that isn't listed. What should I do?

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

You could simply describe the problem you are facing here, in a comment. What were you trying to do? What problem did you meet?


"Cooked" component

Description

Something that would increase the nutrient value of any dish and change a sprite or color of a sprites layer.

can you elaborate on this a bit? like just a basic component that allows something to be cooked to increase its nutriment and sprite?

can you elaborate on this a bit? like just a basic component that allows something to be cooked to increase its nutriment and sprite?

Yes. When you're not making a specific dish in the microwave/cooking machine/fire, have the item become "cooked" by applying a brown layer to it. (This can be substituted for a unique sprite too).
This would also be useful for deep-frying and burned/overcooked things.
This component would also add something on to the name and description of the item such as "Cooked" or "Deep-fried".

Just to add some notes. I believe the component should have a options for prefix, suffix and appearance.
Prefix and suffix giving you a field to add "fried", "cooked", "steamed" etc and insert this relevant to the name but also add to the end of the description "this one is xxxx" xxxx being the adjective.
Appearance would add a layer also relevant as swept said such as making it fuzzy and brown for deep fried for example or golden brown in the case of pastry.
This could even just be condensed into one line I imagine where you'd give it type: cooked then have a field for fried etc which will affect all of the above without having to define eac one. This would leave space for other fields like nutrient amount.

this is more or less superseded by the other cooking issues and planned cooking refactor, needs more discussion on the specifics


Refresh Not Working at Specified Rate

Hi Eric, Found your code online and it is awesome! I've got a bunch of config files that seem to be working. The only thing I'm noticing is that it seems like there is a 90 second refresh between these checking to see if they are in stock? I'm attaching a screenshot of my docker logs. Not a big issue just curious if you know of a quick fix.
P.S. I do have the refresh interval set to 2 as you do in your examples.

Can you try updating your copy of the code and rebuilding the docker container? I fixed this last night.


Intra-Region network energy/data transfer coefficient is unclear in the documentation

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details
Hi.
In the documentation regarding energy/data transfer coefficient, I see here a coefficient of 0.001 kWh/Gb with a little b, as in "100 Gbps" mentioned in the same section, which I understand as 0.001 kWh/Gigabits (Gbps being Giga Bits Per Seconds). In the following sections like the memory one, the factor is explicitly in kWh/GB for GigaBytes so the little b in the network section was really confusing.
In the Appendix I it's said Networking Kilowatt Hours / Gigabyte: 0.001 which seems clear to be 0.001 kWh/GB(ytes).
Which one is the intended factor to be used ? It seems in the code this is 0.001 kWh/GB(ytes). However, looking at the litterature this would seem pretty low, the very lowest estimates I found for inside the core network of an operator's network being as a very minimum 0.002 kWh/GB (Fischer, Berthoud) and up to 0.02 kWh/GB (Coroama).
Expected Behavior

I think it would be good to change Gb to GB in the "choosen coefficient" section of the documentation to avoid any mistake, if the coefficient chosen is 0.001kWh/GB
In my opinion (but I could of course, be wrong), the intra-Region factor could be reconsidered regarding the current litterature. Looking at the different issues you have on those topics, for different traffic categories, it seems to be WIP so I'd be very interested discussing those topics with you and see how you feel about it.

Last but not leat
Thanks for bringing open-source software to the table to help with a better evaluation of ICT's environmental impacts.
At Boavizta, we are very thankful to you for this work and would love to collaborate even more with you.

Great research! I was just noticing that Gb/GB difference and wondering if there was an underlying source to reference.
Thank you for sharing those four articles, I'd love to hear a comparative reasoning between the coefficients you linked and the one currently in use.


[5.7] Cherry-pick parser changes to 5.7

Cherry-pick of:

https://github.com/apple/swift-experimental-string-processing/pull/253
https://github.com/apple/swift-experimental-string-processing/pull/245
https://github.com/apple/swift-experimental-string-processing/pull/269
https://github.com/apple/swift-experimental-string-processing/pull/272
https://github.com/apple/swift-experimental-string-processing/pull/278
https://github.com/apple/swift-experimental-string-processing/pull/237
https://github.com/apple/swift-experimental-string-processing/pull/280
https://github.com/apple/swift-experimental-string-processing/pull/301

Most notably, this allows scalar escape sequences such as \n to be matched against, fixes non-semantic whitespace in custom character classes, corrects matching option scoping behavior, and starts rejecting invalid character properties at compile time.
Based on top of https://github.com/apple/swift-experimental-string-processing/pull/246 to avoid a merge conflict (it's included in https://github.com/apple/swift-experimental-string-processing/pull/298).

@swift-ci please test

@swift-ci please test


Use "queryst" library to decode nested query strings

Just look at https://github.com/rustless/queryst, maybe you can use it to cover some complex cases.

Is this a standard thing? I'm generally going to avoid putting in features if they aren't a standard feature for a library like this one.

@reem it parses query string the same way Rails does. And it's the same format that jQuery uses in it's .param(). So I think it's quite standard. There is no RFC of course. But I don't insist, I've just wanted to show you the library.

I think this is the kind of thing I would be happy to have as an external library - there's no reason this has to support every use case.


Hidden elements are visible until DOMContentLoaded is executed

Description: Hidden elements are visible or "flash" until JavaScript after DOMContentLoaded is executed on /account/register: password and state field.
Environment: macOS Catalina, Safari 15.6.1
Steps to reproduce: Click on Next with empty fields
Expected result: Hidden field is always hidden.
Actual result: See enclosed gif (animated).

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-36171.
[created from NEXT-36171, comment 486595]


[Feature]-[4000]:Table Widget Skeleton should not disappear till the data is loaded

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
On the deployed app, there is no way to indicate that the queries/functions are loading as the user looks at the page with blank widgets. On the edit mode, we have a spinner at the top but this doesn't show in the deployed version.  Would be nice to have the spinner on the top bar or have the cursor change to a clock icon.
Why should this be worked on?
Suggestion by a discord user - https://discord.com/channels/725602949748752515/760761686549463060/957322085242384446

@danciaclara the skeleton loading state is what indicates this right?
Cursor is not a good experience because it means the entire application is unresponsive and loading which is never the case. The respective widgets going into loading state seems to be the right UX to me so I'm closing this but please do re-open with more information if you think I missed something

@Nikhil-Nandagopal Yeah that makes sense about the cursor. However, the skeleton screen disappears too quickly when the application is a bit heavy.  It takes a few seconds for the table to populate after the skeleton screen disappears. Probably that caused the user to ask for the loading state as the skeleton screen went unnoticed.  For eg: Here's a screenshot of the page showing the table without any data.
Be it the skeleton screen or a circular loading state for individual widgets (as different widgets load times may differ based on the query) the data should appear immediately after the loading state.

@danciaclara yeah that makes sense. This is a performance problem and the loading state should not change till the evaluation is complete

I think this is a problem only with table widget, but not with any other widgets. Does anyone have any evidence for other widgets on this?

Needs triaging:
We need to understand if this is happening because of any code in the table widget or because of the evaluations.
Please check our a-force app to understand the empty table issue.

Reach - 303
Impact - High

@dilippitchika This looks like due to evaluations. filteredTableData used by the table to render the body is a derived property and requires an evaluation cycle. but the header is generated from primary columns which is part of DSL and doesn't require an evaluation cycle.
CC: @Rishabh-Rathod

@sbalaji1192 then is it possible to delay the loading of the header as well till evaluations are complete?

@dilippitchika Table doesn't know whether the filteredTableData  is not computed or is empty (tableData is empty). so we cannot make that decision inside the table widget.

Stats

Stat
Values

Reach
1500

Effort (months)
0.75

@sbalaji1192.
We're showing loading state (not through isLoading prop) till evaluations are done for a widget.
editorSelectors.tsx -> getCanvasWidgetDsl
isLoading property is set, only whenever a query/api is triggered, which bound to the widget data.

The empty rows case happens when

The table data is empty (should be addressed by #12709)
The table is evaluated but the API is not triggered yet.

For the case where is API is not triggered.

It can be the case where the API.run() is bound to a button click or some other action, that the user has to perform.

In this case, we shouldn't be setting the loading state pre-emptively. But show the No data available

There's something we can do for on page load actions though (which seems to be the case with A-force)

Created a task #12809

@eco-monk Thanks for the detailed explanation!

Bumping to high for the following reasons

When the data is huge or the evaluations are slow, the app viewer is unable to understand why they are still seeing older data
There's no way for app developer to fix this by using something like a progress bar widget and update the user that evaluations are pending.

One suggestion Balaji had was to add an isEvaluating flag on our widgets. To begin with only Table widget can have this.

@dilippitchika @eco-monk Suggested isEvaluating flag will be true when the query has been completed but the derived properties are computed yet.

@sbalaji1192 i think something is evaluating should not be conveyed to a developer, for them all of it should be one property - query loading + table evaluating. What do you think? Can we improve the DX here?

@dilippitchika That should also work. There is no need to differentiate between query is loading vs table data is getting evaluated. To the end user, both should be conveyed in the same way. that data is not ready yet. So having one flag for both is  totally fine.

Understood, can we use something like Table.isLoading property to handle both of these?

I just noticed the same while triaging https://github.com/appsmithorg/appsmith/issues/18105 in List v2. The experience can be a bit jarring here as we see the old data for a flash and then see the new data. Although I am thinking of doing a monkey patch in the List widget but having a proper isLoading to handle both should be the right way.
@dilippitchika @somangshu This issue seems to be tagged for App Viewers and UI Builders, shouldn't this be assigned to FE-Coders?

I agree Ashit.
@satbir121 we need help here from you guys. The way isLoading behaves is the reason this experience exist. So you have suggestions? LMK what you think

@somangshu @ashit-rath
The current logic to determine the widget's loading state ( WidgetLoadingSaga/setWidgetsLoadingSaga ) works as follows

Get all the actions that are being fetched in isLoadingActions
Check the dependency of the widget's loadingProperties

For example, In the case of TableWidget tableData is a loadingProperty and we would check its dependency. If it depends on Api1 and Api1 being present in isLoadingActions then we would set that table in the loading state.
If we want to show the initial isLoading state for TableWidget until tableData is evaluated, we could show isLoading for all widgets until the 1st evaluation is not completed as after that tableData would be evaluated.
We could try adding an isInitialEvaluationInProgress redux state that could be consumed in the above setWidgetsLoadingSaga to set all widgets that has any dependency to isLoading.
cc: @sbalaji1192

@Rishabh-Rathod but its not just about first load, it's also if the API is running via a button, the table stops loading once the API is complete, but the table doesn't render because the evaluation is not yet complete.

@satbir121 assigning to you and team, i think this is a big impact on perceived performance as all our widgets have to wait until evals are also complete to show the data.
People using the isLoading binding find it hard to figure out what is going wrong with the table and how can we improve it. The same reason, animate loading property doesn't work as expected, because it doesn't take evals into consideration. @somangshu if you also agree that this is a perceived performance issue, can you please get this prioritised as a perf improvement?

@bharath31 created a new issue as a dependency for this issue - https://github.com/appsmithorg/appsmith/issues/20600

Reopening, as the PR#36857 provides an alternative solution to the original problem and not completely fixes it.


[TEVA-1757] Part 2 of many: refactor account feedback to use new Feedback model

Updates to other types of feedback to follow. This is a trial run to make sure Steven (performance analysis) is receiving the data.
Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-1757
Changes in this PR:

Rename 'back_link' to 'origin' to match terminology in trigger_subscription_event
Add and use form object instead of AccountFeedback object

Next steps:

[ ] Before removing account_feedback table, transfer data to DataForm/BigQuery.

Review app deployed to https://teaching-vacancies-review-pr-2754.london.cloudapps.digital


[BUG] [cli] rancher token does not recognize Generic OIDC auth provider

Rancher Setup

Rancher server version: 2.9.1
Rancher CLI version: 2.9.2

Describe the bug
Title.
To Reproduce

Setup Generic OIDC auth provider.
Try to authenticate.

Result
% rancher token --server=rancher.example.com --user=[redacted] --auth-provider=genericOIDCProvider
https://rancher.example.com/v3-public/authProviders
FATA[0001] provider genericOIDCProvider not found

Expected Result
Successful authentication.
Additional context
Output from /v3-public/authProviders:
{
  "type": "collection",
  "links": {
    "self": "https://rancher.example.com/v3-public/authProviders"
  },
  "actions": {},
  "pagination": {
    "limit": 1000,
    "total": 2
  },
  "sort": {
    "order": "asc",
    "reverse": "https://rancher.example.com/v3-public/authProviders?order=desc",
    "links": {
      "type": "https://rancher.example.com/v3-public/authProviders?sort=type",
      "uuid": "https://rancher.example.com/v3-public/authProviders?sort=uuid"
    }
  },
  "filters": {
    "created": null,
    "creatorId": null,
    "name": null,
    "removed": null,
    "type": null,
    "uuid": null
  },
  "resourceType": "authProvider",
  "data": [
    {
      "actions": {
        "login": "https://rancher.example.com/v3-public/genericOIDCProviders/genericoidc?action=login"
      },
      "baseType": "authProvider",
      "creatorId": null,
      "id": "genericoidc",
      "links": {
        "self": "https://rancher.example.com/v3-public/genericOIDCProviders/genericoidc"
      },
      "redirectUrl": "https://auth.example.com/realms/[redacted]/protocol/openid-connect/auth?client_id=rancher&response_type=code&redirect_uri=https://rancher.example.com/verify-auth",
      "scopes": "openid profile email",
      "type": "genericOIDCProvider"
    },
    {
      "actions": {
        "login": "https://rancher.example.com/v3-public/localProviders/local?action=login"
      },
      "baseType": "authProvider",
      "creatorId": null,
      "id": "local",
      "links": {
        "self": "https://rancher.example.com/v3-public/localProviders/local"
      },
      "type": "localProvider"
    }
  ]
}

Related: https://github.com/rancher/rancher/issues/35194

+1 For a nice developer experience, we would need this feature too. The UI login works perfectly with OIDC. So it would be very nice to have the same authentication workflow for the CLI.


Update run_chaos_experiment.md

update link address

Codecov Report

Merging #652 into master will decrease coverage by 0.06%.
The diff coverage is 38.23%.

@@            Coverage Diff             @@
##           master     #652      +/-   ##
==========================================
- Coverage   55.78%   55.71%   -0.07%
==========================================
  Files          68       68
  Lines        4383     4397      +14
==========================================
+ Hits         2445     2450       +5
- Misses       1768     1776       +8
- Partials      170      171       +1

Impacted Files
Coverage Δ

controllers/networkchaos/ipset/ipset.go
37.14% <0.00%> (ø)

pkg/store/experiment/experiment.go
32.20% <0.00%> (-6.58%)
:arrow_down:

pkg/utils/chaosdaemon.go
51.21% <0.00%> (ø)

pkg/utils/grpc.go
0.00% <0.00%> (ø)

controllers/twophase/types.go
54.20% <40.00%> (-1.68%)
:arrow_down:

controllers/networkchaos/netem/types.go
47.27% <50.00%> (ø)

controllers/podchaos/containerkill/types.go
64.38% <100.00%> (ø)

controllers/timechaos/types.go
61.44% <100.00%> (ø)

pkg/webhook/config/watcher/config.go
100.00% <100.00%> (+58.33%)
:arrow_up:

pkg/utils/selector.go
51.42% <0.00%> (-0.82%)
:arrow_down:

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 2a1d6b6...899b073. Read the comment docs.

Suggest replacing with these two links from our new EN website to save the trouble:

Get Started With TiDB Operator in Kubernetes | PingCAP Docs
https://docs.pingcap.com/tidb-in-kubernetes/v1.1/get-started#create-a-kubernetes-cluster-using-kind
Get Started With TiDB Operator in Kubernetes | PingCAP Docs
https://docs.pingcap.com/tidb-in-kubernetes/v1.1/get-started#create-a-kubernetes-cluster-using-minikube

@anotherrachel
I have modified it, please take a look.

/merge


'results' attribute deprecated

When accessing the site, there's an alert on the console:

'results' attribute is deprecated and will be removed in M53, around September 2016. See https://www.chromestatus.com/features/5738199536107520 for more details.

Will this break something? Any workaround?

Ok, just clicking on the link gave me an answer. It just needs to be removed


App is stuck at "Extract"

Once I click extract nothing ever happens? Any ideas? Reran with new version now it gets stuck at sign :/

test this release
it should work
https://github.com/iMokhles/TweakApp/releases/download/1.1-2/TweakApp.1.1-2.zip


Update npm install snippet with @condenast/

Description

Prior snippet gives
npm ERR! 404 Not found : xml-to-react
npm ERR! 404
npm ERR! 404  'xml-to-react' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

under npm v4.1.2
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] Chore, documentation, cleanup

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Checklist:

[ ] My code follows the code style of this project.
[ ] I have updated the documentation (if required).
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Pull Request Test Coverage Report for Build 190

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 173:
0.0%

Covered Lines:
60

Relevant Lines:
60

💛  - Coveralls

I should probably add more here. With this the imports should be
.... from '@condenast/xml-to-react'

Good point. Yeah, if you wouldn't mind updating the rest of the README, that would be excellent. Thanks for the PR!


[2.0] Backward compatibility with InfluxQL Query

Proposal:
Backward compatibility with InfluxQL Query
Current behavior:
According to 2.0 document, if I understanding correctly, the API could take InfluxQL query
https://v2.docs.influxdata.com/v2.0/api/#operation/PostQuery
However, I can't seem to come across any examples of how to use InfluxQL with this API with curl. And the error returned is not too helpful.
x-platform-error-code: internal error

{"code":"internal error","message":"An internal error has occurred"}

I was able to find an example and use the flux with this API with curl and it works, but it is different from the document :thinking:
Desired behavior:
A better explanation of the "internal error" to ease troubleshooting.
Perhaps some curl examples on how to use InfluxQL with 2.0. I understand InfluxDB wants to move away from InfluxQL to flux. However, I think most programmers are familiar with the SQL-like language. Some examples will ease the upgrade [1.x->2.0] process without too much resistance.
Alternatives considered:
Continue to support 1.x type API?
Use case:
As stated above, the change from InfluxQL to flux is a steep learning curve when most programmers are familiar with the SQL like query... This may be a slow down (or show stopper) for 1.x->2.0 upgrade.

@Derek-K Thanks for the issue. InfluxDB 2.0 does not support InfluxQL directly. In the future, InfluxDB will ship with an optional InfluxQL transpiler that will transpile an InfluxQL query into Flux before sending it to the query engine. The transpiler is not available yet, but the type=influxql option in the API is stubbed out for it when it does land.
The transpiler is still under development, but you can manually use it in its current state with the 2.0 influx transpile command. It takes an InfluxQL query and returns a Flux query.

I see... no wonder it doesn't work when I try to query influxdb cloud with influxql always fails with 500... thanks!

@Derek-K Quick follow-up – InfluxDB Cloud will support InfluxQL natively. I don't know exactly when it will land, but I know it's close.


⚠ Bofrost.lu has degraded performance

In 0ac33f7, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1258 ms

Resolved: Bofrost.lu performance has improved in eb7e29a after 17 minutes.


Question: How to find out whether MathJax.Hub.Queue(["Typeset", MathJax.Hub]); rendered anything?

Hi,
I am using MathJax on a page that dynamically loads content, so I am issuing  MathJax.Hub.Queue(["Typeset", MathJax.Hub]); several times with a certain delay until I am convinced that no new elements appear on the page.
To optimize that, I would like to find out whether the last call  MathJax.Hub.Queue(["Typeset", MathJax.Hub]); rendered any new element.
Is there any possibility to do this?
Cheers,
Kilian

Do you control the process that is loading the pages?  It would be better to link into that process to determine when the page is completely loaded and then run MathJax.
If not, then one possible approach would be to count the number of equations before typesetting, and then check the number afterward and see if they are different.  E.g.,
function () {
  var eqnCount;
  MathJax.Hub.Queue(
    function () {
      eqnCount = MathJax.Hub.getAllJax().length;
    },
    ["Typeset", MathJax.Hub],
    function () {
      if (eqnCount === MathJax.Hub.getAllJax().length) {
        // no new math was processed; do whatever you need here.
      }
    }
  );
})();

Thanks a lot for helping me out on this one!
Yes, for the most part I have hooks that trigger a MathJax-rerendering, however so far there were still cases where some unrendered formulas were left over, so I want to implement a workaround for this (until a proper solution is found). But I totally agree that this is only a workaround.
Thanks a lot for your solution! This is just what I was looking for!


Progress circle

// Feature request
Something like this library would be awesome for the center button, just be sure to increase the side margin on the center button by the new extra few dp.
Edit:
Or alternatively something like the center button being able to display an animated drawable or something. A lot of potentially cool use cases

Thanks for the suggestion @BinaryWaves, this change would require a lot of effort, I can see this could be interesting for some applications, I'll take it into consideration.

I'm closing this since it would be almost impossible for me to have the time to code with API14.


Provide README description for each demo application

We need to have a short description of each application

what it is
what it does
what is the expected input/output
how/who developed it.
status?

@shaniaki : could you please provide a short description for the mp3-decoder and the vad examples? Something along the lines of the jpeg-encoder description.


Jellyscrub for Truecharts

I installed Jellyfin through the Truecharts Catalog on Truenas Scale. While I can create BIF files, I don't get a preview in any way, not in the web app (even with modified index.html) nor in any app.
Does anyone have Jellyscrub working within Truenas?

I am having the same issue

Could you please paste the parts of your jellyfin logs relating to jellyscrub and script injection status?

I fixed the issue today, I had to clear the cache of my web browser

I fixed mine too, set the values of "runasUser" and "runasgroup" to 0 (run as root). Did the same for the Share Jellyfin accessed (set group and user 0 to have full access)


fix: start migration to eso

Removing backwards compatability, as we'll promote this change with the ESO migration

/cc @msvticket

I'll have a first look now and will continue next week.
I'll begin with firing a question: How have you tested this so far?

To get the schema right it might be easiest to import github.com/external-secrets/external-secrets/apis/externalsecrets/v1beta1 and use the structures defined in https://github.com/external-secrets/external-secrets/blob/main/apis/externalsecrets/v1beta1/externalsecret_types.go


feat: Expose the Curve25519SecretKey type

n.b. for the reader: this is for PkEncryption/PkDecryption support in the Rust SDK.


Investigate using bigints for all uint64 types

Currently, we represent Slot and Epoch as a number, even though it is defined as a Uint64. In practice this has been ok,because we start from 0 and increment these values slowly.
One wrinkle to that assumption, FAR_FUTURE_EPOCH.We get around that by representing it as infinity.
We've also had pain running ssz spec tests and fuzz tests that exercise the higher bits of epoch and slot.
We'd like to explore changing these types from number to bigint.

Should internal types in the beacon-state-transition function that represent Unix timestamps be also converted to BigInt? For example in this function when should the BigInt -> Number casting happen if any?
export function computeTimeAtSlot(config: IBeaconConfig, slot: Slot, genesisTime: Number64): Number64 {
  return genesisTime + Number(slot) * config.params.SECONDS_PER_SLOT;
}

I think any internal types that don't touch ssz-defined datastructures can remain numbers, if they are naturally so.
I think the spirit of this issue is to have a more literal conformance to https://github.com/ethereum/eth2.0-specs/blob/dev/specs/phase0/beacon-chain.md#custom-types which defines all numbers in eth2 datastructures as uint64.

Last attempt on https://github.com/ChainSafe/lodestar/pull/1011 required massive changes everywhere on the code. Maybe it would be best to discuss the strategy on how to deal with key issues such as how to use bigint for array indexing


Global override for jwt issuer

This patch makes it possible to override all the jwt issuers globally.

@kfox1111 Please peek into the CI failures.  I feel that if we can get this passing in CI, reviews will then follow.

I stopped clicking the merge button because it wasnt getting reviews in so long. It takes effort and no effort was being put in. If it will get reviews then, I'll fix it, again.

I understand, but it is a bit ironic that such a statement is in direct reply to a review attempt. :)
We have a lot of stuff in the backlog, but we are burning it down.  It was up to about 30 open issues not too long ago, now it's really close to 15.  This means that some of these older items are finally getting the attention they deserve.
In any case, we need to apply work to the old PRs to get them out of the system, or they'll just stay in limbo forever.


Fix linting errors and code standarization

Created PR:
https://github.com/appmazing/express-starter/pull/8


Cache of AnalyzeJarTask is not relocatable

Build scan link

--
Plugin version

0.78.0
Gradle version

7.2
(Optional) Android Gradle Plugin (AGP) version

7.0.2
Describe the bug

Cache miss of AnalyzeJarTask between different machines.
To Reproduce
I've checked it on the same commit on different machines similar to this doc

./gradlew :module:projectHealth on the first machine. It pushes to a remote build cache
./gradlew :module:projectHealth on the second machine. It reads from the remote build cache

Expected result: AnalyzeJarTask is FROM_CACHE
Actual result: executed.
Expected behavior

The task is relocatable.
Additional context

I narrowed it down to the root cause.
./gradlew :module:projectHealth shows the difference in inputs:
// machine 1

> Task :module:analyzeJarRelease
Appending implementation to build cache key: com.autonomousapps.tasks.AnalyzeJarTask_Decorated@e78b8455a7d7eca5bf491b961b530fff
Appending additional implementation to build cache key: com.autonomousapps.tasks.AnalyzeJarTask_Decorated@e78b8455a7d7eca5bf491b961b530fff
Appending input file fingerprints for 'allArtifacts' to build cache key: 0382434ae95159f487e2ac43802e8459 - RELATIVE_PATH{/home/ekrivobokov/project/module/build/reports/dependency-analysis/release/intermediates/artifacts.json='artifacts.json' / 89d3d3d2e98941190304333c7f3e7c71}
Appending input file fingerprints for 'androidLinters' to build cache key:<PHONE_NUMBER>7c59a29efbd867d34c3548 - IGNORED_PATH{...}
Appending input file fingerprints for 'artifactFiles' to build cache key: ddb32eb9d84a5e01fd21fe7c8cb2ebd1 - CLASSPATH{...}
Appending input file fingerprints for 'testArtifactFiles' to build cache key: e393e963da94c4bf226972a08bb294cc - CLASSPATH{...}
Appending output property name to build cache key: allComponentsReport
Appending output property name to build cache key: allComponentsReportPretty
Build cache key for task ':module:analyzeJarRelease' is 112841c19cdf27ab0811a0df3e3b26c7

// machine 2

> Task :module:analyzeJarRelease
Appending implementation to build cache key: com.autonomousapps.tasks.AnalyzeJarTask_Decorated@e78b8455a7d7eca5bf491b961b530fff
Appending additional implementation to build cache key: com.autonomousapps.tasks.AnalyzeJarTask_Decorated@e78b8455a7d7eca5bf491b961b530fff
Appending input file fingerprints for 'allArtifacts' to build cache key: 11e308b0a9f5e188e40e2f61f4eaa537 - RELATIVE_PATH{/Users/ekrivobokov/project/module/build/reports/dependency-analysis/release/intermediates/artifacts.json='artifacts.json' / 6ed5f24c323f102f048a652af4a6ff3e}
Appending input file fingerprints for 'androidLinters' to build cache key:<PHONE_NUMBER>7c59a29efbd867d34c3548 - IGNORED_PATH{...}
Appending input file fingerprints for 'artifactFiles' to build cache key: ddb32eb9d84a5e01fd21fe7c8cb2ebd1 - CLASSPATH{...}
Appending input file fingerprints for 'testArtifactFiles' to build cache key: e393e963da94c4bf226972a08bb294cc - CLASSPATH{...}
Appending output property name to build cache key: allComponentsReport
Appending output property name to build cache key: allComponentsReportPretty
Build cache key for task ':module:analyzeJarRelease' is 6e52e33c96407cd2b19abfea2735f7d3

The difference is only in the allArtifacts input.
/**
   * A [`Set<Artifact>`][Artifact].
   */
  @get:PathSensitive(PathSensitivity.RELATIVE)
  @get:InputFile
  abstract val allArtifacts: RegularFileProperty

I've compared the content and found these differences:

They contain the same dependencies, but the records are sorted randomly. The same dependency is on different positions in Json arrays.
The probable workaround is to sort records before serializing them to file.

Absolute paths to project files:

{
        "dependency": {
            "identifier": ":utils:lang"
        },
        "file": "/home/ekrivobokov/project/another-module/build/libs/module.jar"
}

VS

{
        "dependency": {
            "identifier": ":utils:lang"
        },
        "file": "/Users/ekrivobokov/project/another-module/build/libs/module.jar"
}

The probable workaround is to store paths relative to the root project dir: another-module/build/libs/module.jar

Absolute paths to external dependencies:

{
        "dependency": {
            "identifier": "com.squareup.retrofit2:retrofit",
            "resolvedVersion": "2.9.0"
        },
        "file": "/home/ekrivobokov/.gradle/caches/modules-2/files-2.1/com.squareup.retrofit2/retrofit/2.9.0/d8fdfbd5da952141a665a403348b74538efc05ff/retrofit-2.9.0.jar"
}

VS

{
        "dependency": {
            "identifier": "com.squareup.retrofit2:retrofit",
            "resolvedVersion": "2.9.0"
        },
        "file": "/Users/ekrivobokov/.gradle/caches/modules-2/files-2.1/com.squareup.retrofit2/retrofit/2.9.0/d8fdfbd5da952141a665a403348b74538efc05ff/retrofit-2.9.0.jar"
}

The probable workaround is to store paths relative to the Gradle cache dir: com.squareup.retrofit2/retrofit/2.9.0/d8fdfbd5da952141a665a403348b74538efc05ff/retrofit-2.9.0.jar

This is the ultimate cause: https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/blob/main/src/main/kotlin/com/autonomousapps/tasks/ArtifactsReportTask.kt#L40-L49
I.e., the output of ArtifactsReportTask is based on an input (to that task) that has absolute path sensitivity.
It's possible there's a solution, but I don't know offhand what it would look like and can't prioritize it right now.

AnalyzeJarTask no longer exists in v1.0.0rcX. There are still tasks that use absolute-path sensitivity, however.
Since you already did significant analysis of the problem, would this be something you'd be willing to work on? That is:

Find tasks with non-relocatable outputs.
Ensure outputs are sorted before being serialized.
Take note of the tasks using absolute-path normalization and see if they can be relativized.

I would propose doing those three steps in that order. That is, the first step is getting a list of tasks that need to be optimized. The second step is relatively simple (and may already be done -- in my work on the new model, I made an effort to ensure all outputs are sorted, but I may have missed a few cases). The third step is the most complex.

Thanks for the proposal.
Unfortunately, most probably I'll have no time in the near future.

Closing this for now.


ios运行后出错

undefined is not an object (evaluating 'ViewPropTypes.style')

<unknown>
    DefaultTabBar.js:20
loadModuleImplementation
    require.js:171
<unknown>
    index.js:20
loadModuleImplementation
    require.js:171
<unknown>
    day3.js:11
loadModuleImplementation
    require.js:171
<unknown>
    index.ios.js:15
loadModuleImplementation
    require.js:171
guardedLoadModule
    require.js:116
global code
    require-0.js:1

that may caused by different version of node ,so you need to update the code by yourself changing ViewPropTypes into View.propTypes

What is the specific operation? Please explain? I am a beginner

I have the same problem，help

I have the same problem

same problem , help

I have the same problem，help

find node_modules/react-native-scrollable-tab-view，all xxx.js
change ViewPropTypes.style to View.propTypes.style，it works for me.


feat(http): remove

Removes choo/http. In previous IRC conversations we kind of came to the conclusion that this doesn't make a lot of sense to bundle in anymore given that a lot of choo's narrative is now about how to glue views, logic and state. We weren't mentioning it anywhere in the README anymore anyway, so it might make sense to deprecate in its entirety.
Having thoughts on this would be highly welcome! - Thanks!

Yea. I thought for this too. Because I was playing with choo these days and its size browserify bundled isn't 7kb, nor 4kb. It was 30kb+.
% ❯ ls -al dist                                                                                 October 08, 03:03:49
total 384K
drwxr-xr-x 2 charlike users 4.0K Oct  5 05:12 ./
drwxr-xr-x 4 charlike users 4.0K Oct  5 05:17 ../
-rw-r--r-- 1 charlike users  152 Oct  5 05:17 200.html
-rw-r--r-- 1 charlike users 273K Oct  5 05:17 bundle.js
-rw-r--r-- 1 charlike users  38K Oct  5 05:17 bundle.min.js
-rw-r--r-- 1 charlike users  56K Oct  5 05:17 bundle.min.js.map

with client.js example from the README.

@tunnckoCore you might want to consider running gzip and other optimizations: npm run instrument:gzip will create an optimized bundle

everyone seems to be ok with this, merging!


Allow Local Caching of URLs

Look for /srv/releases/<name>-<verison>.tgz and /srv/stemcells/<name>-<version>.tgz for locally cached copies of stemcells and releases, and use those (as file:/// URLs) instead of the upstream URLs, if present.  SHA1 checksums should also be calculated using these files, if they exist.
A new environment variable, GENESIS_LOCAL should force Genesis to rely exclusively on these locally cached assets.

To clarify:
Local files take precedent over remote urls and GENESIS_LOCAL drops remote urls entirely?

Closing - obviated by genesis-v2


[Camera plugin] Image capture not respecting device orientation on iOS

When taking a picture with the camera plugin, it does not seem to ever be able to take a landscape picture when the device is rotated. Not sure if there is some setting that needs to be enabled or configuration issue
Device is iPhone 8 (MQ6K2LL/A)
iOS 12.0.1
This looks like the same issue, on android: #21545
Might also be a duplicate of: #16587
See screenshot of camera plugin example below:

Flutter doctor output:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.0.1-pre.72, on Mac OS X 10.14.1 18B75, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.2)
[✓] Connected device (3 available)

• No issues found!

Duplicate of #17606

There is a PR waiting to be approved.
Please add a comment to have this issue reopened if you don't think this is a duplicate.


Feature/type annotations and mypy

Pull Request Test Coverage Report for Build 2637

230 of 234 (98.29%)  changed or added relevant lines in 26 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 96.588%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

eventsourcing/domain/model/entity.py
68
69
98.55%

eventsourcing/types.py
56
59
94.92%

Totals

Change from base Build 2632:
-0.04%

Covered Lines:
4444

Relevant Lines:
4601

💛  - Coveralls

Pull Request Test Coverage Report for Build 2637

230 of 234 (98.29%)  changed or added relevant lines in 26 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 96.588%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

eventsourcing/domain/model/entity.py
68
69
98.55%

eventsourcing/types.py
56
59
94.92%

Totals

Change from base Build 2632:
-0.04%

Covered Lines:
4444

Relevant Lines:
4601

💛  - Coveralls


Room for improvement on cloneWithRowsAndSections?

I find this to be extremely confusing the way one has to set up the section ID array and row ID array to pass into this function. It feels like a real brain-buster, and I don't think it should be. I was wondering if the team is open to ideas on refining this and making it much more straightforward.

Like for instance, why can't we pass just a single data blob like this?
[
  {
    section: 'Fruits',
    rows: [
      {
        name: 'Apple',
        color: 'red'
      },
      {
        name: 'Orange',
        color: 'orange'
      }
    ]
  },
  {
    section: 'Vegetables',
    rows: [
      {
        name: 'Celery',
        color: 'green'
      },
      {
        name: 'Carrot',
        color: 'orange'
      }
    ]
  }
]

That could work - write a helper function that takes in that data structure and returns a data source and publish your code to npm.

Hang on.. if I'm understanding the code, it seems like the section ids and row ids arguments for cloneWithRowsAndSections are optional. If you pass a data blob, probably structured similarly to the above, it'll handle all that for you. I'm testing now.

I tried following the format specified here:
https://github.com/facebook/react-native/blob/0e8b207cc34f230eb2cced3981734b522b601817/Libraries/CustomComponents/ListView/ListViewDataSource.js#L100-L110
And just passed a data blob into cloneWithRowsAndSection (no section IDs or row IDs), and all formats failed. Something's not right. In fact, this should work:
{ sectionID_1: [ <rowData1>, <rowData2>, ... ], ... }

And so I tried doing the following:
  dataBlob = {
    'Fruits': [{name: 'apple'}, {name: 'orange'}],
    'Veggies': [{name: 'broccoli'}]
  };

  this.setState({
    dataSource: this.state.dataSource.cloneWithRowsAndSections(
      dataBlob
      //sectionIds,
      //rowIds
    ),
    loading: false
  });

And I get literally thousands of these errors about sticky header out of range.

@ffxsam https://github.com/facebook/react-native/issues/1706

Thanks for that. Still though, it doesn't function as it's supposed to. The source code comments say you can just pass a certain structure in, and that fails. I'll attempt to do a PR once I have some free time.

Any update on this? Im having the same problem. I've tried so many ways and I cant get around thousands of sticky warnings.

I'm having the same issues too.

fwiw, I've had success using a blob with sectionId and rowId keys, so a map of maps, not a map of arrays. For example:
{
  "s1": {
      "row1": {...},
      "row2": {...},
  },
  "s2": {
      "row3": {...},
      "row4": {...}
  }
}

I think Ben's workaround here looks pretty good. We want to improve the ListView in general since it's one of the most feedbacked-about components, see a few more details in the roadmap at https://github.com/facebook/react-native/wiki/Roadmap . I am going to close this issue but I think if someone was interested in sending a PR to improve the documentation that would be great.

My personal preference is by using an array of array.
const sections = [{ title: 'Married' }, { title: 'Single' }]
const rows = [
  [
    { col1: 'Guilherme', col2: '26'},
    { col1: 'Luiza', col2: '22'}
  ],
  [
    { col1: 'Valentina', col2: '2'},
    { col1: 'Julian', col2: '1'}
  ]
]
const ds = new ListView.DataSource({
  rowHasChanged: (r1, r2) => r1 !== r2,
  sectionHeaderHasChanged : (s1, s2) => s1 !== s2,
  getRowData: (dataBlob, sectionID, rowID) => rows[sectionID][rowID],
  getSectionHeaderData: (dataBlob, sectionID) => sections[sectionID]
})
const dataSource = ds.cloneWithRowsAndSections(rows)


Better format for cage source ls

I've found that the display format of the old cage source ls was difficult to grok at a glance.
Here's a new, one-row-per-service format:
caladan:rails_hello dkastner$ cargo run source ls
  SERVICE        IMAGE                 STATUS      LOCAL   REMOTE
  coffee-rails                         unmounted           https://github.com/rails/coffee-rails.git
  rails_hello    faraday/rails_hello   unmounted           https://github.com/faradayio/rails_hello.git
caladan:rails_hello dkastner$ cargo run source clone coffee-rails
Cloning into '/Users/dkastner/cage/examples/rails_hello/src/coffee-rails'...
caladan:rails_hello dkastner$ cargo run source ls
  SERVICE        IMAGE                 STATUS      LOCAL              REMOTE
  coffee-rails                         mounted     src/coffee-rails   https://github.com/rails/coffee-rails.git
  rails_hello    faraday/rails_hello   unmounted                      https://github.com/faradayio/rails_hello.git

...aaaand looks like I need to fix the mount check :(

OK, fixed mounted check

@dkastner what did the old format look like for comparison?

@seamusabshere
dkastner@arrakis:~/cage/examples/rails_hello$ cage source ls
coffee-rails              https://github.com/rails/coffee-rails.git
  Available at src/coffee-rails (mounted)
rails_hello               https://github.com/faradayio/rails_hello.git

The "mounted" note is hard to see at a glance. Also, the multiline format makes it hard to grep

this looks great to me!

I'm not a huge fan of massive, multi-column tables that wrap on 80-character terminals. Can we think of any alternate ways to present this information? I'd be OK with two formats, one for writing to TTYs and one for writing to pipes, or a JSON format that could be passed to jq.

This is the same kind of format docker ps uses

@dkastner The fact that Docker displays tables that don't respect terminal width limits the way regular ps does is my single least favorite thing about Docker. 🙁 I would love to find something better.

I spoke with @dkastner about this again today, and I'm still leaning against supporting >80 char table output.
Instead, it might be possible to do something like the following:
sudo npm install -g json2csv
cargo install xsv

...and adding a --json flag to cage, allowing:
cage source ls --json | json2csv -f name,mounted | xsv table

(Optionally, jq could be used for more complicated filtering and transforms.)
However, this raises a related workflow issue, which is that we need some super-easy way to list just the mounted sources. I'd also be happy to support:
# One of the following?
cage source ls --mounted
cage source mounted

...or any reasonable variation on that theme.


Add tvOS support

Fixes https://github.com/spotify/HubFramework/issues/164.
There are several things going on here:

Made HubFramework compile for tvOS (lots of compile flags).
Added support for the focus engine (a little trickier than expected, especially with nested collection views).
Added a HubComponentWithFocusState protocol so that a component can update its view when in focus.
Added a tvOS test target.
Updated the podspec.

Missing:

I did not update the CI setup. I'm not super familiar with using fastlane for this (often use a simple shell script) and wanted to avoid breaking something.
A tvOS demo app (to come in a separate PR later on).

Current coverage is 93.17% (diff: 41.37%)

Merging #263 into master will decrease coverage by 0.22%

@@             master       #263   diff @@
==========================================
  Files            72         72
  Lines          5019       5042    +23
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           4688       4698    +10
- Misses          331        344    +13
  Partials          0          0

Powered by Codecov. Last update 185da1f...167a5c1

Thanks for the feedback.
A universal framework is much easier to maintain and that's a huge plus. The main technical argument against a universal framework was that Carthage couldn't build it but that's no longer the case.
See these for context:
https://github.com/Alamofire/Alamofire/pull/326
https://github.com/Alamofire/Alamofire/pull/1064
Any other argument we should consider in favour of a platform-specific framework?
An additional difference with @JohnSundell's implementation is that I added an explicit HubComponentWithFocusState protocol whereas John merged focus state with highlighted state.
I will update the PR with the changes requested by @rastersize and @cerihughes and will steal a couple of ideas from @JohnSundell's branch 😄

@marmelroy Thank you for the links and update, much appreciated! From reading the Alamofire discussions I think we should probably go with multiple targets. Like you’ve done in this PR.

Sorry for the delay in fixing this - moving countries is quite time exhaustive. This PR should be ready for another review.
Summary of changes:

Syntax was improved as per @cerihughes request.
Change requested re unsigned enums was applied framework-wide.
Change requested re configuration overrides was due to duplication of the dynamic target on production. Overrides were removed from both iOS and tvOS targets.
The test target was improved a little.

I would prefer we wait with this until we have the API more stable, we also need to refactor HUBViewController to do less and be easier to reason about which will become more difficult by having to care for tvOS as well.


Missing options on TalkAction ?

Hello,
In the doc, we can see several options that should be available for Talk.
For  TalkAction inside the sdk, i cannot see the options language and style but instead voicename.
Should the voicename be determined according the language ? Is there a helper function ?
Thanks.
Vonage SDK Version

Version:6.0.0

I just see in the api reference that the voicename is deprecated.
Is it planned to update the sdk options according the new api reference ?


python312Packages.python-telegram-bot: 21.4 -> 21.5

Diff: https://github.com/python-telegram-bot/python-telegram-bot/compare/refs/tags/v21.4...v21.5
Changelog: https://github.com/python-telegram-bot/python-telegram-bot/blob/v21.5/CHANGES.rst
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.11 Release Notes (or backporting 23.11 and 24.05 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.

Result of nixpkgs-review pr 338947 run on x86_64-linux 1

duplicate of https://github.com/NixOS/nixpkgs/pull/338848


[UI] Improve vote option messages

Actually, a lot of people came to me asking how they should vote because some of the options suggest they're not enjoying the proposal at all. For example, the laughing face. Sometimes when we don't really like a proposal it's not weird to laugh at it.

Label suggestions:

don't want to see it
not my thing
bored
liked it
very interested

You're welcome to suggest other labels. It's just an initial statement.

Yes, I also find it confusing.
I think there are many voting options, that's confusing.


update ci to go 1.18

Describe the solution you'd like
update to go 1.18

The trivy lib requires 1.18, so we should also bump up the go images we use for building the images.