ref失效问题

Vue version
3.2.37
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-dls8zb?file=src%2FApp.vue,package.json&terminal=dev
Steps to reproduce
打开https://stackblitz.com/edit/vitejs-vite-dls8zb?file=src%2FApp.vue,package.json&terminal=dev就可以看到问题，目前显示为空白，正常应该显示字符串"xxx"
What is expected?
正常显示docid字符串xxx
What is actually happening?
目前显示为空白
System Info
No response
Any additional comments?
No response

Top lvwl await can only be used in children of a Suspense component.

https://vuejs.org/api/sfc-script-setup.html#top-level-await

The problem has not been solved！

Solution: Don't use top-level-await.

it's ok.
`
`


Document embeding Document embeding document with GridFS inside.

Um, hello :)
I've got a bit of a problem...  it's a  bit nippy...
Some background:
Three are a three documents. Four actually - Lets call them BaseDocument, Game, Map and Media.

BaseDocument is MappedSupperClass, with fields like Id, CreatedAt, UpdatedAt, and some callbacks for them. (dont know is this a good practice...)
Game extend BaseDocument and has Name field and Maps field, which embedMany Maps.
Map has Name field and Media field, which embedOne Media.
Media has one field (File) and many callbacks.

Above schema was working in my head, but after project start it fail. I wasn't able to embed Games. When I've figure it out I was still taking "zero-length keys are not allowed, did you use $ with double quotes?" error.
I've find out in this topic (only one I've found: http://stackoverflow.com/questions/11857975/gridfs-using-mongo-odm-not-working dated at Feb 6) that embedding anything, which use GridFS Isn't (wasn't?) possible.
So in general my questions are:

Is this possible (at current mongodb-odm project state) to build document tree like above?
Is it possible to embed Media/Class with GridFS at all (even on first level)?

I'm asking, because I'm just curious - my project is barely started and I know perfectly how to solve this issue with references, but I've figure it out, that using my Media class an embed document will be best solution for this project.

This is something we want to change with the new GridFS implementation in 2.0: a file will likely no longer just be a property in a document but will be treated as the root-level object it actually is in MongoDB, with all other fields being metadata for that file.


Updated error message where variable is integer or string

Updated error message where variable is integer or string. As integer and string are not differentiable and there will be no gradients. Fixes #20058

The error message is correct -- no gradients provided for any variable. The proposed change would be incorrect, since no assumptions can be made about the variable types.


max_accel_to_decel has been removed in newest klipper versions

since 20240313 klipper has removed the max_accel_to_decel parameter from its config. klipper_estimator currently fails at parsing the printer configuration without this config option present.

Came here to report this exact issue, thanks!

me too

it was easy just do like this /Users/mrx/Documents/skrivare2024/klipper_estimator_osx --config_file ~/Documents/skrivare2024/config.json post-process; and make own configfile

no i have wrong :/

Hi,
This has been fixed in 8d50d71 and released as version 3.7.0.
Best regards,
Lasse


Apply --use-class-uris option from linkml v1.6.5 to MIxS schema

Some of the tasks/objectives that are being completed/realized in this PR are:

[x] Add black code formatter and format all custom scripts in src/scripts
[x] Update pyproject.toml file to use syntax compatible with poetry > v1.2
[x] Apply --use-class-uris to documentation pages globally

Got feedback on this work, and approval to merge this PR in at GSC CIG call on 12/12.


Push-Icon sizes shown in README correct?

Are you sure the push-icon sizes shown in the README are correct?
I have 36px has hdpi here and 96px as xxxhdpi. But not sure where I got the sizes from.

https://developer.android.com/guide/practices/ui_guidelines/icon_design_launcher.html

The link refers to launcher icons not push notification icons.

I think they are the same. Using those sizes for 3 years now and at least 17 apps on Play Store. Doens't saw any issue related to this.

@eberlitz Could you add the model for push notification icons like you mention it in README.md?


Update package.json

add license (necessary to display a screenshot on the new module list)
fix name (only lower case is possible)
elaborate description

Nice. Your module is now displayed with a screenshot in the new module list :slightly_smiling_face:

Very much appreciated!!


[5.6] Added chunkById support in relations.

Pivot data doesn't attached to model If you use Builder::chunkById.
This PR is fixing this and using actual of relation keys for chunking.
Related to https://github.com/laravel/nova/issues/152
Backport for https://github.com/laravel/framework/pull/26919

@taylorotwell It need for Nova, but I don't know, it's normally to change requirements in Nova like ^5.6.N|^5.7.N where N - versions with this PRs. Maybe polyfill(through macro) for 5.6 | <5.7.N will be better?

5.6 isn't receiving bug fixes or improvements anymore.


Fix remove tmp directory on Windows startup script

Purpose
Fixes https://github.com/wso2/product-is/issues/13017
Check whether the <IS_HOME>/tmp directory is there and run the removing command only if the directory exists as in wso2server.sh script

@rajithacharith Merge the PR once the PR builds is successful


Rio doesn't support clusters with oidc authentication

After running rio install several times and just getting a simple - FATA[0000] can't contact Kubernetes cluster. Please make sure your cluster is accessable , I started running other commands like rio console and saw this: No Auth Provider found for name "oidc".
So two things:

The error coming off the rio install command could do a better job of telling me why it didn't work (--debug didn't help produce any more hints what was wrong either)

The real problem: no support for OIDC auth.. 😢

@jpapejr yes, we already had a pr for this issue https://github.com/rancher/rio/pull/264...

This should be fixed by the PR mentioned in previous comment. @jpapejr


Mergify/bp/branch 3.0/pr 19468

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.25 out of 26 committers have signed the CLA.:white_check_mark: amber-create:white_check_mark: Astralidea:white_check_mark: leoyy0316:white_check_mark: Smith-Cruise:white_check_mark: wyb:white_check_mark: Seaven:white_check_mark: letian-jiang:white_check_mark: stdpain:white_check_mark: satanson:white_check_mark: zombee0:white_check_mark: Youngwb:white_check_mark: nshangyiming:white_check_mark: meegoo:white_check_mark: kevincai:white_check_mark: zaorangyang:white_check_mark: gengjun-git:white_check_mark: evelynzhaojie:white_check_mark: sduzh:white_check_mark: ABingHuang:white_check_mark: EsoragotoSpirit:white_check_mark: wangsimo0:white_check_mark: dirtysalt:white_check_mark: HangyuanLiu:white_check_mark: srlch:white_check_mark: hellolilyliuyi:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


ref(builder): push deis/slugrunner in the background

This was attempted in https://github.com/deis/deis/pull/3453 but was blocked due to concurrency issues with the v1 registry. Instead of attempting to shoehorn something hacky in (why break what ain't broken?), we should just wait until we migrate over to the new registry.

This is not something we'll be able to get to for the LTS release (#4776) and the architecture in deis v2 has dramatically changed such that this is no longer relevant so I'm closing this.


Android - Chat - Text field is hidden by keyboard once it is called

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Message field is always above keyboard and user can see what they're typing
Actual Result:
Message field gets overlapped by keyboard, user can't see what they're typing
Action Performed:

Open app and login
Open any conversation
Tap on message field in order to type a message

Workaround:
Unknown
Platform:
Where is this issue confirmed?
Web
iOS
Android ✔
Desktop App
Mobile Web
Version Number: 1.0.31-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/116148787-5924be80-a6af-11eb-8604-09ab06020a95.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @JmillsExpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Doing my best to track the source of this regression

Okay, confirmed that this PR was the source of this regression.

Reverting the problem PR here

@isagoico Can you please retest this during tomorrow's QA cycle? Should be fixed 🙂


Default export main class

Changes the export of the main class TLNetwork to default.

Ah ok good points... My intention was originally to solve an other issue using default export but was going in the wrong direction. I will close this PR then and open a new one for the webpack update later.


Edit UG, DG, About me, README

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (84ecaea) compared to base (77a32bf).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #126   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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.


SoundStream class for playing streaming wave banks

DirectXTK for Audio has a WaveBank class which allows in-memory XACT-style wave banks to be used to play one-shots and to create SoundEffectInstances.
The package also includes a command-line utility, XWBTool, to build XACT-style wave banks. In addition to building in-memory wave banks, it can build streaming wave banks which are suitable for use with async IO as demonstrated in  XAudio2AsyncStream.
Therefore, this work item is to create a WaveBank::CreateSoundStream() function which creates a SoundStream class to perform this kind of streaming as part of the DirectXTK for Audio library.

Code for doing async streaming from PCM format wavebanks can be found here

See this PR


Guide Test Fixtures - broken link

Go to http://www.yiiframework.com/doc-2.0/guide-test-fixtures.html#fixtures-format
the "documentation" hyperlink is broken.

That document refers to itself. It was 2 separate documents before. These are to be merged.

Samdark believe he's speaking What OS 2 links are broken , lead paragraph 404 um , like myself checked .
WHY NOT exists This file EVEN IF HE AND linked ?

Look, in the current master version this file exists: https://github.com/yiisoft/yii2/blob/master/docs/guide/test-fixtures.md
Who problem? Named erro!
test-fixtures.md e test-fixture.md

See #10890 PU

PR is merged https://github.com/yiisoft/yii2/commit/9b9d198f2482b0b47115762837e19d33fb994402
Thank you!

@duynguyen0511 done! @SilverFire  lets rock!


Add individual crud functionality

What is the Purpose?
this is an initial workflow for the crud functionality for Individual
What was the approach?
i reused some of the old code while also removing unnecessary code
Mentions?
Mention persons you'd like to review this PR
Issue(s) affected?
List of issues addressed by this PR.

hey @myugetsu and @TAnas0 quick question on the forms and modal windows: they are using crispy_forms and JQuery right now. I thought we were going to use Vue directly or were we planning to move to Vue later. What were your thoughts?
The program modal uses Vue if you need reference 🙂 templates/workflow/level1_list.html

yeah it should be in vue currently i was just looking to get the backend functionality before i proceed as i was cleaning excess code and reusing code that was already there. if the current workflow is ok i can convert it to vue fully

yeah it should be in vue currently i was just looking to get the backend functionality before i proceed as i was cleaning excess code and reusing code that was already there. if the current workflow is ok i can convert it to vue fully

got it! sounds like a good plan 🙂

nice! @myugetsu shall i create a separate ticket to move the CRUD to Vue? so we can wrap up this PR?
Let me know what's best

looks really good to me as well! nice one 🧁


Create Docker image.

Docker is an increasingly important way to deploy Linux apps. Having a docker image allows users and orgs to quickly deploy and try out DevAudit in a stable runtime environment without needing to install any dependencies. A DevAudit Docker image based on the latest stable Mono image from Xamarin should be created.

Is this expected to be available for 2.0, or is it best I postpone it to the next release? Bear in mind we are trying to reduce the remaining effort for release, so unless it is ready for prime time I would rather delay till 2.1.0

Definitely will be available for 2.0. The Docker image works now with the only issue being I haven't updated the build with the latest code. I'll make sure to update it this weekend.

The latest build is pushed to the Docker image at https://hub.docker.com/r/ossindex/devaudit/.


error on POST request

This carbonara-42.herokuapp.com page can’t be found

No webpage was found for the web address: https://carbonara-42.herokuapp.com/
HTTP ERROR 404

Application Error


pcli does not work offline following refactoring

Describe the bug
The refactoring @hawkw did in #1003 made the code much cleaner, splitting the role of the Opt struct (now just representing the arguments themselves) and the App struct (now representing the configured and constructed application data.
However, as a side effect, it also made pcli stop working offline, for subtle reasons.  Previously, the needs_sync method on the command controlled both (1) whether pcli would try to synchronize before doing the command and (2) whether pcli would connect to the network at all.  Now, needs_sync controls whether we wait to sync before running the command, but we unconditionally connect to the remote node in Opt::view_client.  This means that if the node is offline, we won't run the command at all.
I'm not sure what the best way to fix this is, because we can't easily get rid of the requirement to construct a view service in the App.  It's not essential to have pcli work solely offline, at least for now, so this isn't urgent, but it would be ideal to be able to run it offline.

Agh, whoops! I can try to fix this.


Indicate if a file could not be read ("[Permission denied]")

When opening a file where you do not have permissions to read it, Vim displays:

"noperm.txt" [Permission Denied]

It would be nice if there was an indicator displayed by vim-airline, besides the read-only lock in this case.
TEST CASE:

sudo touch noperm.txt
sudo chmod 600 noperm.txt
vim noperm.txt

that is an interesting request. Can you check, if this works for you?
diff --git a/autoload/airline/parts.vim b/autoload/airline/parts.vim
index 498eaed..26fdf24 100644
--- a/autoload/airline/parts.vim
+++ b/autoload/airline/parts.vim
@@ -70,7 +70,12 @@ function! airline#parts#iminsert()
 endfunction

 function! airline#parts#readonly()
-  return &readonly ? g:airline_symbols.readonly : ''
+  let buffer=winbufnr('')
+  if &readonly && !filereadable(buffer)
+    return '[Perm denied]'
+  else
+    return &readonly ? g:airline_symbols.readonly : ''
+  endif
 endfunction

 function! airline#parts#filetype()

ping

@chrisbra
Sorry for not responding earlier.
The patch works!
(using the test case I've provided)

Great. You might want to add this here

Couldn't/shouldn't this be added by default?

I thought about this for a while. But first of all, I personally find the 'RO' flag enough, since this always triggers also for Permission denied messages, and second, I think this also triggered for new files, which I kind of did not like and then, one probably also wants to catch the message 'NEW FILE'.
So in short, I wasn't sure, whether it should be caught by default in vim-airline. So the second best thing would be to write it down in the wiki.

Cherry-picked into my fork for now, with an additional check for &modifiable (which skips fugitive buffers): https://github.com/blueyed/vim-airline/commit/55efc9901cea5921b67b9dc62285b93359eeafcf.

does this not also trigger for new files?

No, they are displayed as [New file] only (from vim newfile.txt).

Okay, go ahead and create a PR please. Thanks!

Done.


Investigate AzDO simple test failure

Fixes #152 which was failing the AzDO build. A previous PR changed the code so that the push option was supposed to depend on whether imageName was set or not, but the definition still had the default push value specified so the code didn't function correctly.
Pin the CLI to 0.7.1 due to an issue with 0.0.8 (see https://github.com/devcontainers/cli/issues/91)

/test

/test

/test

/test

/test

/test

/test
previous run failed on image pull


ludwig test sometimes does not produce correct confusion matrix values

This has happened to me multiple times, and I am now trying to get to the root cause of this.
Basically, really often, this is the confusion matrix that I generate from the model+dataset I am working on:

As you can see there are some actual values that are never predicted, but they should at least be predicted as unknown (note that I have set the --normalize flag, so total sum per-row should always be 1)
I checked in the test_statistics.json (attached)
test_statistics.zip
and the values reported for the confusion matrix always show a 0 in the corresponding column.
In the other result files, all source items have a corresponding prediction (right or wrong, that's not the point)
results.zip
This is the commandline I use to generate the results:
ludwig test --data_csv dataset.csv --split validation --model_path path\to\model --batch_size 12
This is the commandline I use to generate the confusion matrix:
ludwig visualize --visualization confusion_matrix --normalize --test_statistics results\test_statistics.json --ground_truth_metadata dataset.json
I also tried using hdf5 in place of the .csv, but with no avail. Actual predictions return a result (of course). Given the performance values of this example it might be the wrong result, but it's none the less a result that should be mapped in the confusion matrix.
For this specific one I cannot share the dataset (personal IDs) but anything else I can do, please advise.

Not sure what is the problem here. As some labels are never predicted, the sum of the row is 0. In theory each value of the row should be 0/0 but i avoid doing division by zero so the resulting value is 0. It sounds all correct to me, what behavior would have you expected?
The relevant code is here anyway: https://github.com/uber/ludwig/blob/master/ludwig/visualize.py#L2738-L2743

Since PP_FRONTE, PG_RETRO and CF_FRONTE (for example, bunching up the last ones) are present in the validation dataset, I expected to see a value greater than 0, in whichever predicted label have they been predicted.
I just double-checked again and purged .hdf5 and .json, they are present in the validation dataset, but they are not in output, according to the confusion matrix (and more importantly according to the confusion matrix data within test_statistics.json).
For example, the last 3 values in my validation dataset are PG_FRONTE, PG_RETRO and PP_FRONTE. Looking at the results prediction.csv they have all been erroneously predicted to be CE_FRONTE. Although this is not correct for the purpose I'm training for, I expected to see a high value in the corresponding "CE_FRONTE" column, for all the bottom three rows, but they're empty.
It's not the visualizer that is doing wrong... it's the test that is not correctly enumerating the occurrences of the predictions. Within test_statistics.json I expected not to get a 0 for those values. The visualize you are referring to is just plotting what it is seeing in the test_statistics.json

Might that be that, since those categories are never predicted in the output, the array gets cut to the wrong size as per this: https://github.com/uber/ludwig/blob/master/ludwig/utils/metrics_utils.py#L36
?
The only peculiar thing about this dataset is that I never got a prediction for those labels (I know, right now I have a tiny validation dataset, with just one item per label, and that might be the edge-situation that is generating this issue).

In that piece of code predictions and conditions should be of the same size, the min is mostly a precaution, but if you run the test script you an put a break point / print there to see what they are and how long they are, if they are not the same size it's probably worth investigating.
I could help you out, but i need a reproducible setting ;)

That's not the case, as they are the same size. I however noticed these warnings in the ludwig test CLI output:
sklearn\metrics\classification.py:1437: UndefinedMetricWarning: Precision is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
sklearn\metrics\classification.py:1437: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 in labels with no predicted samples.
'precision', 'predicted', average, warn_for)
This seems to be the exact symptom, as per https://github.com/scikit-learn/scikit-learn/blob/0.21.X/sklearn/metrics/classification.py#L1407-L1410
In this case we have true_positive, false_positive and false_negative = 0 (label is not present in the predictions at all), so if I'm understanding correctly the behavior, sklearn will return 0 no matter what.
If you could just confirm me that I'm understanding this correctly, we could even think of closing this issue as a won't fix, since it's due to how sklearn treats these issues and it should only happen with such a small dataset used during test that some labels are not ever in the prediction results.

Just to have a proof of concept, I forcibly stopped early a training, and got it to a point where all ground truth classes are categorized in the same result class (TS_RETRO). As in previous examples I expected to see a vertical solid yellow colored line spanning all classes on the TS_RETRO column, since any input document has been classified as TS_RETRO only (no other result has been produced other than that class)

Now I get your point. So the solution should be to set the range of the color map to [0, 1] in case of normalization.
Moreover, it looks to me like the 2 axes of the plot are inverted: if all classes are predicted to be TS_RETRO there should be a column of colors different than purple, not a row, right?
Will investigate.

I don't think you should need to mess with the scale. This is the result of not having all the correct values in the matrix. If all other rows had a solid 1.0 in the TS_RETRO or whatever it is, the maximum value for the scale will be automatically set to 1.0
The issue is that, row by row, the sum of all the prediction distribution should always be 1.0, but for all the rows other than the populated one, the sum is 0.0
Thanks!

What about the columns and rows? again they look flipped to me, aren't they?

They are reversed indeed... I trained a classification model on the same dataset, tweaked a little bit,
images.zip
giving him only dogs as validation (forcing the model to come to the solution that everything's a dog), then I ran the confusion matrix, and this is the output:

It should definitely be reversed, you are right.
Type_predictions.csv only contain dog as a prediction (one validation sample per every one of the 4 classes), and I just don't know how to interpret the confusion_matrix key in the test_statistics.zip. If the arrays are column-by-column they are right (ie: the second member shows 0 for UNK and 1 for anything else), and the graphic output is wrong. If the arrays are row-by-row they are wrong (the second row shows exactly what we see in the output), but at least the graphic visualization part is right.
If i flip the array values axis, from "confusion_matrix": [[0,0,0,0,0],[0,1,1,1,1],[0,0,0,0,0],[0,0,0,0,0],[0,0,0,0,0]] to "confusion_matrix": [[0,0,0,0,0],[0,1,0,0,0],[0,1,0,0,0],[0,1,0,0,0],[0,1,0,0,0]] I get this visualization, which also has the correct scale being calculated:

Found it and fixed. It was an order mismatch between two parameters in the confusion_matrix results build.
I made a PR... it seems to be working (giving the correct results in CMs) but as usual you should double check that.

Merged, thanks!


[new-arch] How to specify explicit skip messages due to unmet conditions ?

See: https://github.com/googlefonts/fontbakery/pull/1419/files/f706952d2c7c5cd74d5d2249e17757927a5dc3e7#r126024754
There I said:

Is a condition understood as "falsy" if its value is an empty list ?
In some places we need to explicitely skip because we want to provide a feedback message to the user explaining why it was skipped. Alternatively we could perhaps declare in the condition code what message to be displayed whenever the condition is false.

Let's continue this discussion here.

yes, everything that is falsy in python is also falsy as a condition.
e.g.:
>>> bool([])
False
>>> not []
True
>>> not not []
False
>>>

In some places we need to explicitely skip

I don't understand, how do we implicitly skip? We have output like this for a test skipped because of unmet conditions:
>> com.google.fonts/test/064 with ((u'font[0]', '../barcodelibre/fonts/LibreBarcode39Text-Regular.ttf'),)
   Is there a caret position declared for every ligature?
 * SKIP: Unfulfilled Conditions: ligatures

   Result: SKIP

Alternatively we could perhaps declare in the condition code what message to be displayed whenever the condition is false.

We could easily print the description of the condition if available, the decorator is able to take one:
@register_condition
@condition(description="A dict containing all ligatures of the font.)
def ligatures(ttFont):
  all_ligatures = {}
  if "GSUB" in ttFont:
    for lookup in ttFont["GSUB"].table.LookupList.Lookup:
      ...
  return all_ligatures

(BTW, that one would be nice to have a doc-string as well, I didn't understand the structure of the returned all_ligatures just now, but it looks bogus to me.)
but in this case, an even more verbose solution would be to add:
@register_condition
@condition(description="True if the font has ligatures, otherwise false.")
def has_ligatures(ligatures):
  return bool(ligatures)

Because we want to provide a feedback message to the user explaining why it was skipped, could be formatted like:
>> com.google.fonts/test/064 with ((u'font[0]', '../barcodelibre/fonts/LibreBarcode39Text-Regular.ttf'),)
   Is there a caret position declared for every ligature?
 * SKIP: Unfulfilled Conditions:
             has_ligatures: True if the font has ligatures, otherwise false.

   Result: SKIP

I also think you can yield a SKIP within a test already. From the original example just remove the conditions=[] part. Instead of (old):
@register_test
@test(
    id='com.google.fonts/test/048'
  , conditions=['missing_whitespace_chars']
)
def check_font_has_proper_whitespace_glyph_names(ttFont,
                                                 missing_whitespace_chars):
  """Font has **proper** whitespace glyph names?"""
  if missing_whitespace_chars != []:
    yield SKIP, "Because some whitespace glyphs are missing. Fix that before!"
  elif ttFont['post'].formatType == 3.0:
    yield SKIP, "Font has version 3 post table."

If you want to make this, even though missing_whitespace_chars is empty do:
@register_test
@test(
    id='com.google.fonts/test/048'
)
def check_font_has_proper_whitespace_glyph_names(ttFont,
                                                 missing_whitespace_chars):

There's absolutely no reason to have a conditions declaration if you want to read the value in any case.
The rest of the body could start like this, if you are serious with the SKIP status
  """Font has **proper** whitespace glyph names?"""
  if not missing_whitespace_chars:
    yield SKIP, "Because some whitespace glyphs are missing. Fix that before!"
    return
  if ttFont['post'].formatType == 3.0:
    yield SKIP, "Font has version 3 post table."
    return

after that you don't need the extra else block and its indentation (I prefer that style, early exit let's me focus on what's left to do)

@felipesanches can this be closed?

yes!


⚠ Bofrost.at has degraded performance

In 02bb46f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1237 ms

Resolved: Bofrost.at performance has improved in 3b8773a after 6 minutes.


CS language - correction

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
"description": "Karta Home Assistant pro emulaci toku energie, který je zobrazen na obrazovce měniče Sunsynk",
"exporting": "Prodej",
"importing": "Nákup",

Steps To Reproduce
No response
Expected behaviour
"description": "Karta Home Assistant pro emulaci toku energie, který je zobrazen na displeji měniče Sunsynk",
"exporting": "Export",
"importing": "Import",

Card Version
3.5.1
Home Assistant Version
2023.10.3
Configuration
No response
Relevant log output
No response

Hi. Are these terms generally not translated for CS?
Interested to hear some other views before updating. @Legnava89 ?

Hi,
This terms are generraly translated to czech language as
exporting - vývoz
importing - dovoz.
But export/import are domesticated words in czech as other languages.
Legnava89 translated this as
Prodej / Nákup, it means in czech llanguage
Sell/Buy.
This attribute expresses power flow direction, not bussines relationship with energy company, so correct translation is export/import.
For example  if I use virtual battery, I transfer energy to/from virtual battery. No sell or buy (Prodej/Nákup).
Thanks

Hi @mamo-nick
TLDR: I also think it should be renamed to Export/Import
The long version:
You are technically right and wrong at the same time.
It might seem counterintuitive to translate export/import to sell/buy but for most people this is pretty much right and how they use their PV.
The term export/import is here to generalise the idea of this flow of electricity to and from grid
As you said, some people might have virtual battery and this suits them better.
In my view as long as you are connected to the grid you are technically selling the electricity even though your energy provider "saves" your Wh to virtual battery. (It is way more complicated than that but this should be sufficient explanation)
That being said.
I agree with you that it should be generalised.
In Czech language we do have quite heavily used Anglicism of export/import. In fact the exact same words.
So in sake of everything already being referred to as export/import (in the apps and other PV SW) I'd call it the Export/Import in Czech as well.

these expressions are translated correctly. this one person wants them in the english language

Export and Import have multiple meanings in the English language as well, but it terms of energy flow through the Inverter commonly used . What if we used sending and receiving to represent energy flow instead of Sell/Buy:
exporting: "Odesílání"
importing: "Příjem"

Ok i agree.
exporting: "Odesílání"
importing: "Příjem"

Hi @slipx06
Export and Import also have multiple meanings in all the languages you've translated.
Why did you translate export/import as export/import (in local form) in all languages, but only in CS this way?
I don't agree, but it's your decision as the author of the integration and I respect it.
And why is the term Standby not translated?
The imperfect translation is the very reason why I would like to be able to have this card in English even though I have a dashboard in Czech.
See https://github.com/slipx06/sunsync-power-flow-card/issues/113
Anyway, thanks for your work.

@Legnava89

These expressions are translated correctly. This one person wants them in the english language I buy or sell electricity from the distribution network.
    "exporting": "Prodej",
    "importing": "Nákup",

Export / import in the Czech Republic is used as a trade in goods from the Czech Republic to the whole world. In the domestic market, there is only buying and selling. Most people use buying and selling at spot prices in the market. So, I wouldn't change anything about the translation.

The longer I am looking at your response the more I realise that I probably got carried away by professional deformation.
Don't get me wrong, I still think it is for best to generalise it, but using anglicism wasn't probably the best idea from me.
I even wrote why I feel this way above.
@mamo-nick

And why is the term Standby not translated?

Sorry, but with this I know for a fact, that this is non issue in Czech.
Yes there are two possibilities (Standby [or] Pohotovostní režim / V pohotovosti) but these hold the same weight in terms of usage.
Yes, some people 45+ are more likely to use (pohotovostní režim), but most of the people I know from my family and friend either do not even call this state anything like that (Off or sleeping) or do use the two mentioned above interchangeably.
And even some manuals, written in Czech, these days state a "stand-by" mode.
So I think this is irrelevant and not worth changing.
@slipx06

Export and Import have multiple meanings in the English language as well, but it terms of energy flow through the Inverter commonly used . What if we used sending and receiving to represent energy flow instead of Sell/Buy:
exporting: "Odesílání"
importing: "Příjem"

About your suggestion.  I mostly agree with it.
But there is something about exporting as "Odesílání" that quite doesn't hit the spot.
Maybe my colleagues have something to add. Like I don't know, something like "Dodávání" but this isn't right either, because this is dependent on a context as it can be used for both import and export.
I don't know. Maybe I am just lost and nitpicking about small things. :D
Anyways, as @mamo-nick said. It is your project and I believe that now you have enough information to decide for what is the best.
Thank you for this project. It is a life saver.

@FajnB
thank you for your opinion.
I was based on the entities daily_grid_buy and daily_grid_sell from the grid, where the daily purchase and sale are already clearly written.
Everyone understands it without problems. Jens, do you mind exporting/importing translated purchases/sales?
In the Facebook group, everyone is happy to have such a wonderful card in the Czech language, but only one person still has a problem.

Who would have thought translating into Czech could be so contentious :smiley: Anyway thank you for all the input and discussion. The opinions are divided but I'd like to find a middle ground that would suite the majority of users. Is the general consensus that we settle on the below? If I get thumbs up I'll make the change
exporting: "Odesílání"
importing: "Příjem"

@mamo-nick as a workaround to keep those two items as Export and Import a quick fix/hack is to edit the js file that can be found in www>community>sunsynk-power-flow-card and just do a find and replace and reload the card.  You would just need to remember to do this with each update but it literally a few minutes effort. @Legnava89 you can do the same if you prefer to use selling/buying etc.

Hi All. Just a heads up that this is going to change based on the info provided in #119
It will more accurately reflect the work mode provided by register 179. Please make sure your sensor.work_mode_code returns the following:
    goodwe: {
        standby: { states: ['0', 'Wait Mode'], color: 'blue', message: localize('common.standby') },
        normal: { states: ['1', '2', 'Normal (On-Grid)', 'Normal (Off-Grid)'], color: 'green', message: localize('common.normal') },
        fault: { states: ['3', 'Fault Mode'], color: 'red', message: localize('common.fault') },
        flash: { states: ['4', 'Flash Mode'], color: 'yellow', message: localize('common.flash') },
        check: { states: ['5', 'Check Mode'], color: 'orange', message: localize('common.check') },
    }


Some questions about code

why need to  rescale offset range during testing, thanks
if 'test' in kwargs:
outputs_offsets[...,0] /= (img_h / 256)
outputs_offsets[...,1] /= (img_w / 256)

The model is trained using 256x256 image patches. The rescaling operation ensures a consistent offset range during training and inference.


Hey @Durgesh4993  ! Thank you for raising an issue 💗 You have been assigned this issue you can start working on the issue 🎮

Thank You @kunjgit

Sir issue #122 is also my please check it out also

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

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


Sieve of Eratosthenes

@smriti-v16
Can you please add the description for this?
Please add the compile and run details as well.
I'll review the code.
Please resolve the issues and update the PR.
Thanks!


[CAPI] Add check if model is null to ml_train_model_get_summary()

Check if model is null or not before checking in ml_train_model_get_summary_util()

Self evaluation:
Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped
Signed-off-by: Hyunil<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1890. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


m.Text: How to put ellipsis at the beginning of my Text?

OpenUI5 version:
Browser/version (+device/version):
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
1.
2.
3.
What is the expected result?
What happens instead?
Any other information? (attach screenshot if possible)

Hi @Jerry4013 ,
I can think of two approaches.

With JS calculation and string operations in the controller.
With custom CSS: you should hide the overflow with ellipsis (check the css property text-overflow) and custom class that reverts the direction of this text only.

Unfortunately there is no such feature implemented in the sap.m.Text.
Best Regards,
Hristo

Hi @hristop ,
Thank you very much for your reply! I tried to use a similar logic of the method sap.m.Text.clampText to find out the position of my ellipsis. My manager's requirement is allowing two lines of text for our folder path. If it is more than two lines, then put an ellipsis at the beginning of the text (first line).
I tried to find out a right position for my ellipsis. I use some same code as the source code. Then I found a bug in the clampText method. It determines the overflow by comparing oDomRef.scrollHeight and iMaxHeight, line 425. But this way is not correct, because in my case, window.getComputedStyle(oDomRef).lineHeight get a value of "normal". Then in the source code line 336, we calculate the line height with a formular "fLineHeight = parseFloat(oStyle.fontSize) * this.normalLineHeight;". In my case, fontSize is 14 and normalLineHeight is hard coded as 1.2 in our code. Therefore, the multiplication result is 14 * 1.2 = 16.8 . Then we get the Math.floor of 16.8, which is 16. Then we multiply 16 by 2 lines, which is 32. However, my oDomRef.scrollHeight for a two-line span is 34. The logic should be, if the actual height is larger than the max height allowed, then we should put ellipsis. In my case, I have a two-line text, my maxLines is 2, so the actual height should not larger than allowed height. But according to our source code, 34 > 32. This is incorrect.
I think maybe we should use some other approach instead of comparing the heights.
Thanks,
Jerry

Hi @Jerry4013 ,
Can you provide a snippet in which we can see what you are trying to do (JSBin works)?
What browser are you using to test this?
Best Regards,
Hristo

Hi @Jerry4013 ,
Since there is no response from the author for more than 4 weeks I'm closing the ticket.
Best Regards,
Hristo


Rustc Driver Chapter

I've started working on a rustc-driver chapter.
It's still very early days and I've written it as someone with experience instrumenting rustc from the outside so I don't know if it'll flow with the other chapters, so feedback, comments, and criticism are most welcome! :grin:
The basic points covered are:

What is it? glue code/the compiler's main() function
What phases does it go through?
At which points in the compilation process can I inspect the compiler's state, and what can I see

I also want to add something like @nrc's https://github.com/nrc/stupid-stats (which is awesome btw, thanks @nrc!) as an appendix for future explorers. If it's fine with him, I might end up copying most of it across and update it to take into account any changes to the compiler since the tutorial was written.
(fixes #74)

Also, it looks like a rebase is needed?

If it's fine with him

It is fine with me :-) You should check it still compiles and work - the driver is unstable, so it may have changed since I last checked stupid-stats.

@nrc

It is fine with me :-) You should check it still compiles and work - the driver is unstable, so it may have changed since I last checked stupid-stats.

Thanks!  Would you be able to have another look?
If you know anyone who's hacked on the driver recently it may be useful to CC them in. There's probably a lot of stuff I've missed.

@Michael-F-Bryan Thanks!
I personally don't know of anyone else to CC... The git blame of librustc_driver/lib.rs seems to show quite a lot of people :)
I think we can probably merge this and let others raise issues later for additions.


Feature: Payments API can be checked for validity

https://developer.mozilla.org/_kuma_status.json is used to verify real-time configuration of secrets. There should be a "payments" entry under "services":
{
  "services": {
    "payments": {
      "available": true (enabled and valid)
      "public_key": the public key or empty string
      "one_time": true if one-time payments are working (valid keys)
      "recurring": true if recurring payments are working (valid keys, product)
    }
  }
}

This can be used as a debug aid, or to run / skip acceptance tests

No longer relevant


Dont allow user typing in date?

Is there a way to make it only possible to select day? otherwise there is a need for a date validation and same date not always have the same format

You can make input field as readonly, so that user cannot modify the value.


PP-495 Analytics as a container service

Description
Using the dependency_injector framework, the Analytics class has been moved into a Container as a Singleton.
The Analytics no longer supports per library configurations, any configuration is for the entire CM.
Configurations have been moved to environment variables.
The API objects also make use of the dependency injection pattern for analytics.
The Admin UI for the Analytics service will display a "This service is no longer configurable" message.
Database entries for Analytics have not been removed in case a rollback is required.

Motivation and Context
The CM no longer needed per-library Analytics, it required only CM-wide configurations, not via the Admin Panel.
JIRA

How Has This Been Tested?
Manually tested some feeds and Admin pages.
Updated all unit tests to reflect the new patterns.

Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

I haven't started a code review here, but it looks there will be some deployment changes associated with this PR (I've added a label for that). Specifically, it looks like we add at least the following environment variables:

PALACE_LOCAL_ANALYTICS_ENABLED (default: False)
PALACE_S3_ANALYTICS_ENABLED (default: False)
PALACE_LOCATION_SOURCE (default: None, other values: ["neighborhood"])

It would be helpful to document these in the README.

I added the UI update label as well, since this will require an admin UI update.

Just a few more comments on this one. Its looking good otherwise!
We also need two additional PRs before this can get merged:

Add the new env var to the hosting-playbook
Remove the analytics configuration from the admin interface

Can you work on those as well?

Sure, I'll make tickets for them and get started.


OCR0041: Font creation from Derge glyphs

Description:

We have 477 tibetan glyphs and ligature from the first batch of annotation work, from the second batch we got around 40 glyphs, from the parsing the OPF we got 485 glyphs, in total we have around 1000 Tibetan glyphs and ligature.
We need to create font from these glyphs.

Implementation:
We already have the pipeline to create the font, there is a need for some small modification to the script.
Subtask:

Need to improve the implementation of spacing between characters

[x] modify the script to create a mapping of all the baselines, right-side-bearing and left-side-bearing of each glyphs
[x] modify the script to convert the pixel unit of baseline, rsb and lsb into font units

[x] Modification to the font creation pipeline

Completion Criteria:
To obtain a font in .ttf with these glyphs

first i kept all the baseline as contant value for each glyphs, and I applied the obtained width, lsb and rsb for each glyphs in the font, the result is the one above.
this method, was having issue with   ི  ོ    ེ, to tackle this, i created mapping of baseline,lsb and rsb and i am going to convert it into font unit and apply it to the the glyph.

great output! Sharing just an idea I have:
When making sentences from cropped out glyphs font, we may get clunky images that may not look natural sometimes.

Even though we manually try our best to reduce this by writing scripts, bounding box, left-right padding, etc, it may take lot of time and may not work as we visioned.
Maybe we can train a model to modify the image generated by font by just a little, in order to make it feel more natural, overlapping glyphs, better aligned baselines, etc.

@Norbu-Jamling this is good idea, we'll meet to discuss this

derge glyphs were use to generate font, this is a test script using the derge font

Img.1: Pecha Image of first page of Derge Kangyur

Img.2: Text created from E-text using generated Derge Font


'io_uring_enable_rings' not exposed

As 'io_uring_enable_rings' is not in 'liburing.map' it is not marked as an external symbol in 'liburing.so'. This results in package managers (arch and debian at least) build systems stripping the symbol from the shared object when striping symbols. The upshot is that the function can be referenced by user code at compile time as it's in the header, but linking to the shared object fails due to an undefined reference to the function.
https://github.com/axboe/liburing/blob/master/src/liburing.map
(liburing.map is a 'version-script' parameter to the linker when linking liburing.so.)
Is this a bug, or is the intent to not publicly expose this function?
(The initial issue is here, fwiw: https://github.com/facebook/proxygen/issues/434)

That's just an oversight... Want to send in a patch?

Sure, but before I do, here's a list of symbols that are in a non-stripped library that are also not external.
$ nm pkg/liburing/usr/lib/liburing.so | grep " t "<PHONE_NUMBER>002720 t deregister_tm_clones<PHONE_NUMBER>002790 t __do_global_dtors_aux<PHONE_NUMBER>003980 t _fini<PHONE_NUMBER>0027e0 t frame_dummy<PHONE_NUMBER>002000 t _init<PHONE_NUMBER>003680 t io_uring_enable_rings<PHONE_NUMBER>002c70 t __io_uring_flush_sq<PHONE_NUMBER>0027f0 t _io_uring_get_cqe<PHONE_NUMBER>003650 t io_uring_register_restrictions<PHONE_NUMBER>002a40 t __io_uring_submit<PHONE_NUMBER>002d50 t __io_uring_submit_timeout<PHONE_NUMBER>002750 t register_tm_clones
Should any of those also be in the patch?

io_uring_enable_rings should be exported.

__io_uring_flush_sq is marked as static since commit 7fc973fc6626
("queue: Mark __io_uring_flush_sq() as static"). This function was
never exported despite it was not marked as static in <= 2.3. This
function should NOT be exported.

_io_uring_get_cqe is a static function.

io_uring_register_restrictions should be exported.

__io_uring_submit is a static function.

__io_uring_submit_timeout is a static function.

Static functions should NOT be exported.


Added newaxis indexing to the cube.

Ah, I needed to fix biggus too...

I've added a commit which addressed the failing test, and improves the what's new entry.

There's a still a failing test: iris.tests.test_cell.TestCells - test_cell_from_multidim_coord

There's a still a failing test: iris.tests.test_cell.TestCells - test_cell_from_multidim_coord

Thanks @rhattersley. Let's see how that does.

@pelson What's the deal with this PR?  Is it still relevant and/or useful?  I don't mean to be blunt about it, I just noticed that this is ageing a bit.

Closing as we've stalled.


[Addon] Add ChartMuseum addon

Description of your changes
Add ChartMuseum addon, with some sane default values for new users.

Parameters

How has this code been tested?
This addon has been installed and used as vela addon registries.

Checklist

I have:

[x] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
It is now a experimental addon. Will update once matured. Relevant doc and examples will be here:
https://github.com/kubevela/kubevela.io/pull/792 at the official doc site.
[x] New addon should be put in experimental.
[ ] Update addon should modify the version in metadata.yaml to generate a new version.
[x] Any changes about verified addons should be tested with CI script.

Good job! Since this addon is a critical component building private addon registry，can we put this to verified addon directly.

Sure, if that's better. I will move this out of experimental addons.

https://github.com/kubevela/kubevela/issues/4138


Update vllm to 0.6.5

What this PR does / why we need it:
bump to vllm 0.6.5
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

Oh interesting. I wasn't expecting that patch release would introduce breaking changes.

@yuzisun @terrytangyuan Considering https://github.com/kserve/kserve/pull/4147 merged, would this be good to go?


Overlay airplane & camera info on JPEGs

Learn to add the following information as an overlay to JPEGs:

Aircraft lat/lon/alt, heading and groundspeed
Latlon age and alt age
Camera pitch and tilt angles.

This will help with debugging

Bonus points
Do the same with the RTSP stream.


Extend info cmd with status of cgroup controllers

This adds which controllers are attached to the cgroup v2 hierarchy. For devices I just check if it is possible to attach epbf programs to a cgroup. I also moved the freezer controller to pseudo controllers. While contrary to devices and unified, this is a real subsystem it is also quite different from the other controllers. More importantly you cannot read it from cgroup.controllers, nor write it to subtree_control which was one of the original motivations for introducing this distinction.

We should hold this off until the upgrade to the new oci-spec release is completed.

Codecov Report

Merging #286 (0b124b0) into main (dc7b04a) will increase coverage by 0.05%.
The diff coverage is 28.94%.

@@            Coverage Diff             @@
##             main     #286      +/-   ##
==========================================
+ Coverage   69.73%   69.79%   +0.05%
==========================================
  Files          46       46
  Lines        5687     5688       +1
==========================================
+ Hits         3966     3970       +4
+ Misses       1721     1718       -3

We should hold this off until the upgrade to the new oci-spec release is completed.

I agree with you.

@utam0k PTAL


Automator: update istio/client-go@master dependency in istio/istio@master

Generated by Automator - 2022-08-11T07:39:30+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
01fbd0e68ec56f9192402e2820218ea7021a787b
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

client-go changes will not merge into istio/istio until there is a change for the upstream api change. Look for a PR (https://github.com/istio/istio/pull/40142?) with these changes. @ramaraochavali

Doing some work in https://github.com/istio/istio/pull/40479 to get api/client-go changes to start merging.


add info icon and info overlay

Text: https://docs.google.com/document/d/1fWP7-taSDII9Mnxbc7eILS4Kwg9IIdKa796TBZQ8aHo/edit
info background is white, corners are rounded at 4px
scroll bar: #C49D4F
text: #282623
Text is Gentium Book Basic regular, not bold. Line-height is ~1.3. Text can be a little larger than appears in the screen shots - realized this is too small on a phone.
compass illustration is src/img/mini_compass.svg
info icon is 29x29 pixels (please also constrain the close icon and share icon to match). Arcs will need to be bumped down to make room for the info icon. See invision for final layout guidance https://projects.invisionapp.com/d/main#/projects/prototypes/15159709

I think everything here is done, with remaining tasks in follow up issues #66 and #68.


Renamed Contributors to activeMembers

Description:

Changed the navbar button for contributors to active members
Changed all the labels in code

Issue- #208
Screenshot:
Navbar-

Active member page-

Appreciate that!

the build fails, please check this locally

Closing this due file corruptions,raising new PR @FrancescoXX


improve ScalarQuantizer performance, ESPECIALLY on old GCC

Introduces FAISS_ALWAYS_INLINE pragma directive and improves ScalarQuantizer performance with it.
Most of performance-critical methods for ScalarQuantizer are marked with this new directive, because a compiler (especially, an old one) may be unable to inline it properly. In some of my GCC experiments, such an inlining yields +50% queries per second in a search.
The corresponding Faiss PR is https://github.com/facebookresearch/faiss/pull/3141.
/kind improvement

/lgtm

/approve

/run-e2e

/kind improvement


Slow performance using markers's children

Bug report
Summary
I am working in a project that I need to use markers with SVG, for that I am using the SVG as a marker child, but that has implied on a slow perfomance when many markers are displayed on the map. Is there a better way to solve this? I got an example from the docs and the problem is not only with SVG, even a simple View can reproduce it.
Environment info
react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz
react: 16.13.1
react-native-maps: ^0.28.0
expo: ~42.0.1

# device
Samsung Galaxy A71 (SM-A715F)

Steps to reproduce

Clone the repository from https://github.com/gustrigoni/react-native-maps-report
Choose how many markers do you want to add in the map

Press GO to add the markers on the map
Press in the marker icon to change the marker component
)
)

Conclusion
After 5000 makers with children in the map the app crashes.
Important: I'm using React Memo in the components

You might want to use react native map clustering if you have to display a lot of markers : https://github.com/venits/react-native-map-clustering#props

You might want to use react native map clustering if you have to display a lot of markers : https://github.com/venits/react-native-map-clustering#props

I've made my use case on the example, on our application, we need a svg on the marker, you can see that with 20 markers the performance is already affected, so there is not really much that clustered markers could do. It looks like a rendering issue on the map.

We are facing exactly the same issue. It used to work fine in version 0.27.1.

Try making tracksViewChanges={false} prop for Marker component.
It helps in my case - also have custom View as children.

Tip: use https://github.com/venits/react-native-map-clustering for clustering your markers. It has improved my app significantly, I'm handling thousands of markers.

I set this to false after that some UI Markers doesn't fully render


[BUG] Heap Corruption encountered when loading DWrite.dll from latest v124-r2 (Win XP)

Describe the bug
Process Heap corruption happens inside DWrite.dll calls on the browser start,
It happens every time when I allow to load it while debugging even with original progwrp 5018.
When I remove DWrite.dll, Heap corruption warning is not encountered.
To Reproduce
Start the browser under the debugger
Screenshots

Desktop:

OS: XP x86 SP3
Browser: release "v124-r2"
DWrite.dll from "v124-r2"
progwrp.dll from "v124-r2"

I have updated pwp_shl.dll in Supermium 126 to implement SHGetKnownFolderPath. I found that this issue occurred after the function was called as a stub.

Yes, it fixed now.

As it turns out, it's too early to rejoice. Another error now, caused by this libs. Now AccessViolation after using of it:
#855


fix: Minor fix in EventAdapter

Fixes #80
Changes: Removed keyword "final".
used getAdapterposition().

@somenath1435 is the app working correctly?

@amdal07 absolutely working fine


ChartJS Component much slower on Mendix 7.8.0 vs 7.7.1

Hi,
I have just upgraded my Mendix application from 7.7.1 to 7.8.0, and the (unchanged) ChartJS charts run much slower now, specifically rendering in ~10s on 7.8.0 vs ~2s on 7.7.1.
I updated Widgets; I even downloaded the ChartJS 7.8 and overrode it, to no avail.
There is a stark difference in performance. Is it a known issue? Is there a pending 7.8.x patch?
Thanks,
Guislain

As far as I know there shouldn't be any difference between the two Mendix versions, so this might be an R&D thing. I'll see if I can find the problem. As this widget is Platform supported, I also suggest creating a ticket with Support. Please reference this Github issue as well


Deriving IntoValue

Description
There's the Cast proc macro, which in particular derives IntoValue for an enum. I'd very much would like to derive IntoValue for my structs. As such, I'd wish for a derive macro for this to exist.
Would you be open to that addition? I've not yet written a proc macro, but I can probably learn it and make a PR.
Use Case
Passing arguments into the render engine via sys.inputs is really good, but needs a Dict, which in particular contains Values, so there's need to transform data structures into Value.

In principle, cast! should work for any types, not just enums. Are you having any specific problem with it?

As far as I understand it, I have to type out the individual fields anyways, which kind of defeats the purpose. Mainly, you can simply forget a field and the whole thing compiles anyways. A derive macro would take care of that.

Ah, I assume you want to specifically cast your type to/from a dictionary (not any value), as if you were using serde?
We currently don't have a macro for that because cast! is very general; there are types which cast to/from integers, floats, arrays, and so on. Additionally, even for types which use dictionaries, it isn't always possible to cleanly translate the expected dictionary to a Rust struct, as it might have varying structures or fields.
With that said, Dict implements serde::Serialize and serde::Deserialize, so you should be able to use serde to (de)serialize your struct as a Dict, and then wrap the resulting Dict in Value::Dict.

Yes, I was mainly concerned with turning a struct into a (Dict) Value, neither the other way around nor anything else. But I might have missed that going through serde is a possibility here, I'll have a look at that, thanks!

I think serde should indeed work. I'll close this for now, but feel free to reopen if serde doesn't turn out to be a good option!

First a little disclaimer: My immediate needs have been taken care of, so there's no need for action on my behalf ;)
That said, I looked into serde, and it can actually be done quite easily when using an intermediate format, like so:
let d: Daten = ... // elided;
let s = serde_json::to_string(&d).unwrap();
let dic: Dict = serde_json::from_str(&s).unwrap();

where of course one would need to #[derive(Serialize)] struct Daten {...}.
That's pretty bad from a performance point of view though, since we need to create the intermediate JSON string without using it really. It is be possible to avoid the intermediate format (see https://stackoverflow.com/questions/57477967/how-can-i-use-serde-to-serialize-a-struct-to-another-rust-data-structure/57488708#57488708), but that leaves the downside of having to copy out struct fields, where IntoValue is made to take ownership. As the link mentions, one could maybe do that with some custom work.
That somewhat brings us back to square 1 (or maybe worse, since a custom (De)Serializer is probably harder to do than a custom IntoValue implementation).
Tell you what, though. If I can make some time, I'll just make a crate providing such a proc macro, and if it is deemed useful by more people, you might subsume this into typst. Or not, once it's working, it won't be going anywhere of course :)

I've just pushed https://github.com/KillTheMule/derive_typst_intoval to github. If anyone would try it and/or comment on it, I'd be grateful :)

Published: https://programming.dev/post/13926215, https://crates.io/crates/derive_typst_intoval

This has saved me so much trouble!

This has saved me so much trouble!


bumped to netcoreapp2.1, and upgraded to latest versions.

demands some reference to newer version of BotMessageRouting. see other project...

Thank you, @helgeu ! I will try to verify your  PRs soon. Many, many thanks for contributing.


Svelte not working (not sveltekit)

Describe the bug
Install seems to work fine, npm run dev works, but both vscode and the browser complains that:

Property 'init' does not exist on type 'HoudiniClient'.ts(2339)

Severity
blocking all usage of Houdini
Steps to Reproduce the Bug

Reproduction
https://stackblitz.com/edit/vitejs-vite-rcvfuc?file=index.html

Oh I think this is a bug in the files that init creates. You should be able to just delete that line. I've opened up #1032 to clean up the starter project 👍

It works, thank you! 🙏🌷

Well, maybe "works" is a bit strong. I don't get THAT error anymore.
Don't know if it's Is it a Svelte/Sveltekit issue, but now, when I copy the code from https://houdinigraphql.com/

{#each $allItems.data.items as item}

{item.text}

{/each}

I get:

😢

Do you have the vite dev server running? that error means your queries haven't been processed by houdini yet

Thank you for your speedy replies! 😊

Are there any other error messages printed above that error? For some reason your runtime's not being generated

Aha,
It had to be a "real" query. I figured I'd just copy the example and see what happened. Makes sense. This works:

{#if $allItems.data}
  {#each $allItems.data.currencies as item}

{item.name}

  {/each}
{/if}

Thank you again!

Do I have to type the result manually?
allItems is typed as const allItems: getCurrenciesStore, which made me think that it would be typed automagically, but $allItems is typed as let $allItems: QueryResult<_Data, _Input>, so $allItems.data becomes any


Is there a way to customize the patterns that the scaffold generates?

for example, for foreign key relationships, it generates something like UserId_OwnerNavigation,
and I'd like to just be Owner which I could do by replacing everything before and including the _ and delete Navigation.
Is that possible? or something so that I can make the relationships a little less awkward?

This looks similar to https://github.com/aspnet/EntityFramework/issues/4038.

Yes, this is exactly what #4038 is about (this is one of the key scenarios for manipulating the model before it is sent to templating). There isn't really any way to do it at the moment - unless you want to start mucking around in the low-level provider components and even then I don't know that you can do it without effectively writing a wrapping provider.


[FLINK-29052][TABLE]Support TO_TIMESTAMP built-in function in Table API

What is the purpose of the change
Support TO_TIMESTAMP  built-in function in Table API.
Brief change log
Support TO_TIMESTAMP built-in functions in Table API.
Support TO_TIMESTAMP  built-in functions in Python Table API.
Verifying this change
This change added tests and can be verified as follows:
Added test that validates that TO_TIMESTAMP in Table API work
Added test that validates that TO_TIMESTAMP in Python Table API work
Does this pull request potentially affect one of the following parts:
Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)
Documentation
Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

@flinkbot  run azure


Added direct source code upload option to !editcc.

It works.

Cherry-picked and merged off-site.


Copy Context Menu's SubMenu pointless?

Why do we need a sub-menu on the Copy Command context menu to copy a DCS-BIOS configuration in order to paste it into another slot? Why isn't just 'Copy' enough of a command?

Perhaps only display the sub menu in that specific use case. Where I have a single dcs-bios setting per control, the sub menu is an inconvenience.

Check 4.6.8186.

Close this if not relevant anymore.

Brilliant. Much quicker now. Thanks!


User's can not verify their email on desktop

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Users should be able to verify their email on desktop app.
Actual Result:
Link doesn't redirect to desktop app to verify users.
Action Performed:

Register with email on desktop
Click verify link received on email

Workaround:
To login:

Click not {email} button below Resend Link button.

Login

(Relaunching the app doesn't reset the screen and user still has to click not {email} button)
Platform:
Web
iOS
Android
√ Desktop App
Mobile Web
Version Number: 1.0.51-4
Notes/Photos/Videos: Video below
https://user-images.githubusercontent.com/2808949/119371094-7d37e780-bccf-11eb-95a1-fa07f3268ef2.mov
View all open jobs on Upwork

Triggered auto assignment to @bfitzexpensify (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

OK, I can replicate this.
It would, I think, be better if the set password flow could be completed through the desktop app (so rather than being taken to web when clicking the magic sign-in link, the app is triggered instead), if that's possible.
An alternative would be to add another button that says "I verified!" or something similar on the desktop app which would take the user back to the regular login screen, because thatr workaround isn't super intuitive.

Triggered auto assignment to @Luke9389 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Hey @BayCo, thanks for making this issue.
I wanted to give you a quick heads up that if you'd like to fix this issue yourself, you'll need to submit a proposal for doing so (as per step 6 here). If not, and you're just posting this issue with no intention of fixing it, then you have our thanks!

It would, I think, be better if the set password flow could be completed through the desktop app

There is a way to do this with deep linking, but it's not yet set up for our Electron app.
This looks like a decent guide though I haven't looked into it much...
https://shipshape.io/blog/launch-electron-app-from-browser-custom-protocol/
The only other problem is that our validation links are "universal" and don't have a custom protocol (which electron requires e.g. a validation link might end up looking like expensify-cash-desktop://v/123/QWERTY). So we'd need to:

Have the web app first try to open a url to the desktop scheme to see if it's possible (and not ruin the validation link in the process).
Ask to open in the desktop app instead of continuing.

I'm not sure if there is any scenario where a user doesn't have to first hit a web browser before moving on to the desktop app or if it's easy to tell that the desktop app is installed from the website.
TL;DR not sure if this is really a priority for us right now, but we can keep discussing.

(Relaunching the app doesn't reset the screen and user still has to click not {email} button)

But if all we want is for the user to be able to go back to the password entry we can try this:
When on desktop clear the user email after 5 seconds so they do not have to manually click on "not {email}"

@marcaaron @Luke9389 the simplest solution could be putting Login link under the not {email} link and make the UX more friendly

We've let this issue atrophy long enough, and I think there are other priorities for us right now.


Update zotero.rb

to <IP_ADDRESS>

Thank you for the contribution. It was merged directly as a5e0a095dbb0842dfcbf3f6285a3fb53d1714490 to keep commit history cleaner. Your contribution is still credited to you.


chore: switch to a non deprecated ngram filter name

Today I ran gravity specs and noticed a warning that was quite loud. To get rid of the warning this PR does what warning message says and updates the filter name to edge_ngram.
warning: 299 Elasticsearch-7.17.18-8682172c2130b9a411b1bd5ff37c9792367de6b0 "The [edgeNGram] token filter name is deprecated and will be removed in a future version. Please change the filter name to [edge_ngram] instead.

Example in CI

Seeing as just today I pushed a new release 7.0.1, may as well fix the warning and release 7.0.2 and then update gravity.

I imagine this breaks compatibility with ES 1.5 and 2.0. I don't mind us dropping that compatibility, but we should update the readme if so.

I imagine this breaks compatibility with ES 1.5 and 2.0. I don't mind us dropping that compatibility, but we should update the readme if so.

@cavvia Thanks for chiming in and pointing this out. I was about to update the readme but in re-reading the relevant section about versions, my understanding is that ES 1.5 and 2.0 compatibility is limited to 'versions 2.0.0 and earlier' of this lib. Is that not correct?

Oh I see sounds good in that case @ovasdi!

OK, thats good enough for me then. Thanks for the 👁 @cavvia. Merging.


[Enhancement] Add checkbox for toggling SELECTED label color mode

🚀 Feature
Add a checkbox to toggle between SELECTED color mode and previous color mode for labels layers.

Motivation
During user feedback session, users were expecting the label selection spinbox to cycle through the displayed labels, and were confused by having to change color mode to SELECTED to achieve that functionality. A checkbox next to the spinbox would maybe be more intuitive, and also faster when needing to toggle frequently.
I don't necessarily think we should remove the option of selecting it from the drop down, but this may provide the best of both worlds. Happy to hear other suggestions of making the SELECTED color mode more discoverable.

I love this! I think actually that we should remove "selected" from the menu, I think that's part of the confusion. I think @Czaki already mentioned that it was suboptimal that the "selected" mode got the colormap from the last selection of "auto" or "direct". Now it doesn't have to be history dependent: the colormap is either auto or direct, and "selected" is a tick box on how the colormap is displayed.

I love this! I think actually that we should remove "selected" from the menu, I think that's part of the confusion. I think @Czaki already mentioned that it was suboptimal that the "selected" mode got the colormap from the last selection of "auto" or "direct". Now it doesn't have to be history dependent: the colormap is either auto or direct, and "selected" is a tick box on how the colormap is displayed.

Yes, I think we should drop this from the drop-down and not have two places where you can change the same functionality

@sofroniewn @DragaDoncila I would like to show how I solve this in my tool in the case where I need a selection of components:

This what is symilar to the selected mode in napari is hilight when mouse is over checklbox which representing component (implemented using adding small layer).
And showing selection allows user to see whole group of selected components. So it is possible to hilight one object, but also fast chcek if all objects from one group is marked. Currently, this is implemented by manipulating colormap.
For me selected means that I could select more than one component. Currently, it looks rather like hilight. For me napari should support selecting multiple components as part of core functionality.

This has been closed by #1762. We might want to allow selection of multiple labels at some point in time, but we can open a new issue to discuss that when ready.


Execution failed for task ':camera_android_camerax:compileDebugJavaWithJavac'.

Steps to reproduce
I did an upgrade today on Gradle 8 from 7 after latest Android Studio fails to compile my project on Gradle 7.
I do have Java
openjdk 17.0.12 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)

I am using the versions
  camera: 0.11.0+2
  camera_android_camerax: 0.6.9+2

build.gradle
allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

tasks.register("clean", Delete) {
    delete rootProject.buildDir
}

settings.gradle

pluginManagement {
    def flutterSdkPath = {
        def properties = new Properties()
        file("local.properties").withInputStream { properties.load(it) }
        def flutterSdkPath = properties.getProperty("flutter.sdk")
        assert flutterSdkPath != null, "flutter.sdk not set in local.properties"
        return flutterSdkPath
    }()

    includeBuild("$flutterSdkPath/packages/flutter_tools/gradle")

    repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
    }
}

plugins {
    id "dev.flutter.flutter-plugin-loader" version "1.0.0"
    id "com.android.application" version "8.1.0" apply false
    id "org.jetbrains.kotlin.android" version "1.8.22" apply false
}

include ":app"

gradle-wrapper.properties

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.3-all.zip

app build.gradle

plugins {
    id "com.android.application"
    id "kotlin-android"
    // The Flutter Gradle Plugin must be applied after the Android and Kotlin Gradle plugins.
    id "dev.flutter.flutter-gradle-plugin"
}

android {
    namespace = "com.example.camera_issue"
    compileSdk = flutter.compileSdkVersion
    ndkVersion = flutter.ndkVersion

    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = JavaVersion.VERSION_1_8
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId = "com.example.camera_issue"
        // You can update the following values to match your application needs.
        // For more information, see: https://flutter.dev/to/review-gradle-config.
        minSdk = flutter.minSdkVersion
        targetSdk = flutter.targetSdkVersion
        versionCode = flutter.versionCode
        versionName = flutter.versionName
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig = signingConfigs.debug
        }
    }
}

flutter {
    source = "../.."
}

Expected results
Build should work on Gradle 8
Actual results
Build fails
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
Running Gradle task 'assembleDevDebug'...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':camera_android_camerax:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':camera_android_camerax:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for JdkImageTransform: /Users/arzannebiu/Library/Android/sdk/platforms/android-34/core-for-system-modules.jar.
         > Error while executing process /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/jlink with arguments {--module-path /Users/arzannebiu/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/temp/jmod --add-modules java.base --output /Users/arzannebiu/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/jdkImage --disable-plugin system-modules}

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 5s
Error: Gradle task assembleDevDebug failed with exit code 1

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-arm64, locale en-US)
    • Flutter version 3.24.3 on channel stable at /opt/homebrew/Caskroom/flutter/3.24.3/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (4 weeks ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/arzannebiu/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode-15.4.0.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)

[✓] IntelliJ IDEA Ultimate Edition (version 2024.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 242.20629

[✓] VS Code (version 1.94.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554         • android-arm64  • Android 15 (API 35) (emulator)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 15.0.1 24A348 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 15.0.1 24A348 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 129.0.6668.90

[✓] Network resources
    • All expected network resources are available.

• No issues found!```

</details>

Hi @xeinebiu, kindly try https://github.com/flutter/flutter/issues/156304#issuecomment-2397707812 or https://github.com/fluttercommunity/plus_plugins/issues/3303 to see if it resolves your issue

it woked for me: #156304 (comment)  @danagbemava-nc Thank you!

Closing as a duplicate of https://github.com/flutter/flutter/issues/156304, where we are tracking this general issue.


SAK-32401 Added portal connection manager

SAK-32401 Included existing connections in search results.
SAK-32401 Updated to return search hits on current connections
Fixed some layout issues and updated labels
SAK-32401 Added callback to i18n loader
SAK-32401 Fixed problem with accept from popup
Pending count wasn't being updated.
SAK-32401 Added clearsearch to dropdown search box.
CONNECTIONMANAGER ui changes
Fixed cross colour.
Fixed tab backgrounds and colours.
Fixed modal backdrop colour and opacity.
CONNECTIONMANAGER Enter key on search launches more results view.
CONNECTIONMANAGER Click outside search closes results
SAK-32401 Turned off pointer events for the active tab

Very nice Adrian, looks pretty solid.

@ern Is that an LGTM, then? :)

Clearly it is only an LPS.
Nice one.
sent from my mobile
On 1 Jul. 2017 01:05, "Adrian Fish"<EMAIL_ADDRESS>wrote:

@ern https://github.com/ern Is that an LGTM, then? :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sakaiproject/sakai/pull/4530#issuecomment-312292558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH4aY5Ys7iGM_JNZiI4_vNlfG1B1pgOks5sJQ7MgaJpZM4OFSJ2
.

I've had a LPS (Looks Pretty Solid) from @ern and a NO (Nice One) from @steveswinsburg. I'm going to add those together to make a PR (Positive Review).

Very clever.


[Debian] Update to newer versions

From what I understand, you have to take extra steps to switch from a Debian release to its LTS "edition". As such, it is quite possible to be running 9(Stretch) and not get the LTS fixes.
Hence, the duplicate entries to make that obvious.


Incompatibility with 4.08 syntax

I had a bug in my program that I could reproduce with a minimal example. I installed a fresh 4.08.1 opam switch, and installed only ppx_import, then tried to compile the following code:
module Foo(M: sig type t end) = struct
  type t = [%import: M.t]
end

open Foo(Int)

Dune file being:
(executable
 (name foo)
 (preprocess (staged_pps ppx_import))
)

The error I get when I try to compile is:
    ocamldep .foo.eobjs/foo.ml.d (exit 2)
(cd _build/default && /tmp/_opam/bin/ocamldep.opt -modules -ppx '.ppx/730a1ffc71e71794f0005821abd2de02/ppx.exe --as-ppx' -impl foo.ml) > _build/default/.foo.eobjs/foo.ml.d
Fatal error: exception File "foo.ml", line 5, characters 0-13: complex open are not supported before OCaml 4.08
File "foo.ml", line 1:
Error: Error while running external preprocessor
Command line: .ppx/730a1ffc71e71794f0005821abd2de02/ppx.exe --as-ppx '/tmp/camlppxc8c780' '/tmp/camlppxef952c'

In my project I had the same error when trying to use let* also. Removing the preprocessing stanza and the %import removes the error.

I'm having a similar issue but with local module substitutions under 4.11.1, which makes no sense. Apparently ppx_import is still using Ast_407.


1.8.1 got error ,upgrade from 1.8.0

warn  2019-07-10T08:10:45.119 nodeos    controller.cpp:539            init                 ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database.
warn  2019-07-10T08:10:45.119 nodeos    controller.cpp:429            initialize_blockchai ] Initializing new blockchain with genesis state
error 2019-07-10T08:10:45.152 nodeos    main.cpp:114                  main                 ] 3180000 reversible_blocks_exception: Reversible Blocks exception
gap exists between last irreversible block and first reversible block
{"lib":408847,"first_reversible_block_num":408867}
nodeos  controller.cpp:618 init
{}
nodeos  chain_plugin.cpp:989 plugin_startup

what happend about this?

i upgraded from 1.8.0 ,when i first started the nodeos, it runs normally, but when i stopped and started it again,it happend this error,therefore how can i recovered this from this error?

I am getting this issue too.
My blockchain was running normally, but after I stopped it and started it up again, it told me cannot start due to database dirty flag set
So I did what was recommended, i.e I started the blockchain with --hard-replay-blockchain, and it ended with
info  2019-09-09T08:14:01.608 nodeos    http_plugin.cpp:465           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
warn  2019-09-09T08:14:01.609 nodeos    history_plugin.cpp:317        plugin_initialize    ] --filter-on * enabled. This can fill shared_mem, causing nodeos to stop.
info  2019-09-09T08:14:01.609 nodeos    mongo_db_plugin.cpp:1587      plugin_initialize    ] initializing mongo_db_plugin
warn  2019-09-09T08:14:01.609 nodeos    mongo_db_plugin.cpp:1664      plugin_initialize    ] mongodb plugin not recommended on producer node
info  2019-09-09T08:14:01.609 nodeos    mongo_db_plugin.cpp:1673      plugin_initialize    ] connecting to mongodb://eos:Eef9shoujee@<IP_ADDRESS>:27017/EOS
info  2019-09-09T08:14:01.611 nodeos    mongo_db_plugin.cpp:1436      init                 ] init mongo
info  2019-09-09T08:14:01.642 nodeos    mongo_db_plugin.cpp:1523      init                 ] starting db plugin thread
info  2019-09-09T08:14:01.642 nodeos    http_plugin.cpp:412           operator()           ] configured http with Access-Control-Allow-Origin: *
info  2019-09-09T08:14:01.643 nodeos    main.cpp:93                   main                 ] nodeos version v1.8.1
info  2019-09-09T08:14:01.643 nodeos    main.cpp:94                   main                 ] nodeos using configuration file /home/nodeos/.local/share/eosio/nodeos/config/config.ini
info  2019-09-09T08:14:01.643 nodeos    main.cpp:95                   main                 ] nodeos data directory is /home/nodeos/.local/share/eosio/nodeos/data
warn  2019-09-09T08:14:01.643 nodeos    controller.cpp:539            init                 ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database.
warn  2019-09-09T08:14:01.643 nodeos    controller.cpp:429            initialize_blockchai ] Initializing new blockchain with genesis state
info  2019-09-09T08:14:01.712 nodeos    mongo_db_plugin.cpp:1357      ~mongo_db_plugin_imp ] mongo_db_plugin shutdown in process please be patient this can take a few minutes
info  2019-09-09T08:14:01.712 mongodb   mongo_db_plugin.cpp:445       consume_blocks       ] draining queue, size: 0
info  2019-09-09T08:14:01.712 mongodb   mongo_db_plugin.cpp:507       consume_blocks       ] mongo_db_plugin consume thread shutdown gracefully
error 2019-09-09T08:14:01.715 nodeos    main.cpp:114                  main                 ] 3180000 reversible_blocks_exception: Reversible Blocks exception
gap exists between last irreversible block and first reversible block
    {"lib":1215582,"first_reversible_block_num":1215604}
    nodeos  controller.cpp:618 init

    {}
    nodeos  chain_plugin.cpp:989 plugin_startup

same issue:
gap exists between last irreversible block and first reversible block

Hi,
Any one happing this issue and resolved it?

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!

warn 2019-07-10T08:10:45.119 nodeos controller.cpp:539 init ] No existing chain state or fork database. Initializing fresh blockchain state and resetting fork database.
warn 2019-07-10T08:10:45.119 nodeos controller.cpp:429 initialize_blockchai ] Initializing new blockchain with genesis state
error 2019-07-10T08:10:45.152 nodeos main.cpp:114 main ] 3180000 reversible_blocks_exception: Reversible Blocks exception
gap exists between last irreversible block and first reversible block
{"lib":408847,"first_reversible_block_num":408867}
nodeos controller.cpp:618 init
{}
nodeos  chain_plugin.cpp:989 plugin_startup

what happend about this?


Handle Aiohttp Exceptions as valid responses

This PR fixes a bug that till now handled all exceptions as just 500,
while valid Aiohttp Exceptions have to be handled as valid responses.
They are used to notify none 2XX responses, perhaps a 401 is notified
with an HTTPUnauthorized exception.

Please, considere it in WIP I will add some changes. With the current code the Aiohttp exception is never reraised to the upper middlewares.

Please, considere it in WIP I will add some changes. With the current code the Aiohttp exception is never reraised to the upper middlewares.  Better close it, I will reopen it in  while

Without this PR all none 2XX response code are considered 500, so it needs to be fixed. The PR is ready to be reviewed.
Sorry to be late, I've seen that you have already released the 1.1.  but most likely this PR will deserve also a new release.
/cc @haotianw465

Sorry to bother you @haotianw465 , do you have any ETA for the next release?


[change] Implemented DjangoModelPermissions class #111

Closes #111

Coverage decreased (-0.02%) to 99.037% when pulling 8df5c7ee792feef128ccb022fe200b6e27405701 on issues/111-Add-DjangoModelPermission-class into 3c3404748a9ecab65f3f4a389f94d2c75fbde732 on master.


global: removal of access permissions

closes #137

I think you should before make a PR to clean

invenio-records-rest
invenio-records-ui example and tests.

Is tests/access_records.py used anywhere?
because I can't find any import at least in invenio-records-rest.

IMHO we can remove it (cc @nharraud).

Looks good :shipit:
Thanks @hachreak

@jirikuncar should I create there a default permission factory? see https://github.com/inveniosoftware/invenio-records-ui/blob/master/invenio_records_ui/config.py#L33


"color_temp_mired" attribute disappeared from switch.adaptive_lighting_ after updating to 1.4.1

Version information:
1.4.1
Description:
After updating to version 1.4.1 this morning my lights would not turn on anymore. After investigating i found out that the attribute "color_temp_mired" (which i used to turn on my lights for color_temp) did not exist anymore in the adaptive light switch entities, so the light.turn_on would throw an error.
Workaround: use color_temp_kelvin instead
For me it was an easy fix as I'm using a Node-Red subflow to turn on my lights, and I had to implement the change only in one place, but others might not be as lucky.

I am definitely not that lucky.
I used mireds to update the state of my hue scenes so that when I used dimmer switch to turn on the lights, they turned on to the correct color temperature.  Unfortunately, hue still needs mireds to update the scene.

@gderber the conversion is pretty simple - see https://github.com/home-assistant/core/blob/3312a041fd0adbc0b6f3e857106f575e75deaa81/homeassistant/util/color.py#L626
I am using your Hue scene sync method and adapted it accordingly.  Our scripts are different, but I did a conversion like this:
{% set kelvin = state_attr(adaptive_switch_id, "color_temp_kelvin") if state_attr(adaptive_switch_id, "color_temp_kelvin") is number else int(3670) %}
{% set mired = (1000000 / kelvin)|round(0,'floor') %}

@MizterB Thank you!  I had no idea how to do the conversion.
Also, thank you for letting me know you are using my scripts I am glad to know they have helped someone.
I am still tweaking them myself. Latest tweak, I now have one rest_command per number of lightbulbs in a scene, then added an input_text for each bulb's id, and an input_text for each scene id.  Then added as a variable in the script something like 'bulb01 = {{ input_text.bulb_name }}'
Makes it a little easier to move a bulb or make other changes without having to hunt down everywhere I used that bulb id.

Anyone who's had this issue, which version were you updating from?
I'd love to add this back in for cross-compatibility.

I had to revert back to 1.3.0 to get it working.
I am in the process of implementing a work around. I'd still prefer a built in solution.

I'm still a bit confused where your issue lies. I'm looking at the code from 1.3.0 and comparing to current to see what changed.
Just to confirm: adaptive-lighting is unable to adapt your light because the light uses Mirens over Kelvin?
If that's what I'm understanding, I'm confused why the other posts are suggesting using conversion methods, as there's no way to convert what's in the integration via an automation?
If you could post some more information I'd be happy to integrate backward-compatibility for you in the next upcoming version, as it should be a simple change with pre-existing code.

@gderber also can you confirm your adaptive-lighting 1.3.0 version works on the latest hass core version? If not could you at least tell me which hass core version you're running?

I believe I've identified the problem. From HASS core source:
ATTR_COLOR_TEMP = "color_temp"  # Deprecated in HA Core 2022.11
ATTR_KELVIN = "kelvin"  # Deprecated in HA Core 2022.11
ATTR_MIN_MIREDS = "min_mireds"  # Deprecated in HA Core 2022.11
ATTR_MAX_MIREDS = "max_mireds"  # Deprecated in HA Core 2022.11

From my understanding, updating HASS core should fix your problem. Regardless I know how much of a pain updating home assistant is and dealing with all the breaking changes, so I'd still like to introduce backwards compatibility here.

Alright I think I understand the problem well enough now, did you just want the color_temp_mired attribute back or do your lights simply do not respond to service data containing color_temp_kelvin?

The problem is, I use hue switches to turn on my lights.
To get the lights to turn on to the correct color temperature I have to update a hue scene periodically using a script with rest_commands and set it to use the current color temp in adaptive lighting.  Hue scenes require the color temp to be defined in mireds.
This attribute was removed with PR #375.
With Home Assistant changing the default color temp to Kelvin, making Kelvin the default for adaptive lighting makes sense.  However, rather than simply making Kelvin the default, the mired attribute was completely removed.
This attribute was specifically part of adaptive lighting, not related to any Home Assistant source code.

I've added the color_temp_mired back in a future pull request. That part was easy (1 line of code). It'll be exactly the same as it was for backwards compatibility.
Are you also, additionally, saying that your lights won't accept light.turn_on calls with color_temp_kelvin? Because that is a separate larger problem I'd like to escalate (if it's happening).

I'm sure the lights would work using lights.turn_on with the right kelvin setting.
I normally use hue switches to turn on my lights for a variety of reasons.

great! I'll move this issue further up the queue.

@gderber I have added your feature request to PR #460, feel free to try it out yourself!

@th3w1zard1 Thank you!


[Feature] - Add proper highlighting for react templates (jsx and tsx)

Description
Add proper highlighting for react templates (jsx and tsx). Related to PR https://github.com/dinbtechit/vscode-theme/pull/13
Feature for Platform & Language

Platform: IntelliJ, PyCharm, PhpStorm, Rider, Webstorm, GoLand
Platform Version: 2022.1.1
Language: Javascript/Typescript - React

Fixed in PR #25