Line breaking should use Unicode line breaking algorithm

The rules for breaking lines are more complicated than a naive test against white space (for instance, en-dashes and em-dashes are valid points to break text on, although they're not whitespace): this library should use the UAX #14 line-breaking logic provided by the NPM linebreak module (see the canwrap library for an example implementation).

Agreed – PRs welcome. 😉

The way I would refactor this for compatibility would entail changing the signature of the measure function to be just measure(string) to get the width of the given string in pixels - the way it works now involves the measurement function making comparisons and measurements for text that can't be rendered, and doesn't play nicely with ligatures that may change the width of a multi-character sequence.

It's a bit different — it introduces a lot of calls to text.substring and also a lot of extra text width calculations. But the extra features may make those issues moot.
I'll think about it. I haven't needed 100% accurate line-break yet but at some point it will be nice to have, even if it's in a new module.


transformer without domain of predictor

https://github.com/kubeflow/kfserving/blob/659b2c43841ea98bcfab5411b05964e49b34811c/pkg/constants/constants.go#L307:6

@jiaqianjing the predictor host is correct here as transformer to predictor is via local gateway which uses the in cluster service name.

@jiaqianjing the predictor host is correct here as transformer to predictor is via local gateway which uses the in cluster service name.


How to add json file?

Thank you so much for the good open source.
I was wondering how to compile a *.json file in the confings folder while developing utilizing that open source. The include option seems to exist, but I don't know exactly how to use it.
Note image.

It tries to compile the contents in the src folder.
This is the command used.
$ swc src --out-dir dist or swc src -d dist

However, like the image, the configs folder is excluded.
my .swcrc file
{
    "jsc": {
        "target": "es2017",
        "externalHelpers": false,
        "parser": {
            "syntax": "typescript",
            "tsx": false,
            "decorators": true,
            "dynamicImport": true
        },
        "transform": {
            "legacyDecorator": true,
            "decoratorMetadata": true
        }
    },
    "module": {
        "type": "commonjs",
        "strict": true,
        "noInterop": true
    }
}

Thank you.

Sry, I try swc src -d dist --copy-files


Adds web access icon to Access dropdown

https://www.pivotaltracker.com/story/show/146090327
Unsure if the below is the same icon... might be going mad, one of this pr looks a little bolder than one from Product Intergration page

@ManageIQ/core-ux for your review :)
/cc @Loicavenel

@AllenBW I've got to find the right icon, that's not it ;)

I stand corrected, looks like they updated the fa version of the icon, so we are good to go!


Allow to accept sync function for Nullable/mapOrAsync

We close this once by https://github.com/option-t/option-t/issues/1683#issuecomment-1456004819.
We'll reopen this when we conclude about #1683.
If you have some opinions, please comment to #1683


ktor 3

changelog in the 4.0 version is not yet available ? and is there additional config for this version ?

hi, i also updated the changelog in the wiki :+1:


feat: hp changes, revert tank KB passive, damage correction, and more

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


Support encoded dest-strings in /GoTo destination dictionaries (issue 14864)

Interestingly enough this appears to be the very first case of encoded dest-strings, in /GoTo destination dictionaries, that we've actually come across. What's really fascinating is that it's less than a week after issue #14847, given that these issues are somewhat similar.

/botio unittest

It reminds me this article: https://www.pdfa.org/understanding-utf-8-in-pdf-2-0/

Not sure these are encoded right, though (unless there’s another commit between 2.13.216 and master that does this; I just retrofitted this commit on top of the prebuilt release to test this):

I would expect “H%C3%A4ndel”, for example.
(This is unrelated to the other issue, I didn’t know about it, and I had to kick Tₑχ/LᴬTᴇΧ really hard to even generate this (read: I’m doing the UTF-16 encoding outside, in a script).)


[WIP] Share things from main.cpp and src.ino

Remake of https://github.com/datomusic/duo-imxrt/pull/100

Not relevant for now


Fix: Fail "helper.saveScreenshot is not a function" on stepByStepReport plugin.

Motivation/Description of the PR

Description of this PR, which problem it solves

Fix: Fail "helper.saveScreenshot is not a function" when using simultaneous:

helpers [REST, WebDriver]
plugins [autoDelay, stepByStepReport]

Original message fail: <Can't save step screenshot: TypeError: helper.saveScreenshot is not a function> undefined.
Related #2508,  #2513
Applicable helpers:

[x] WebDriver
[ ] Puppeteer
[ ] Nightmare
[x] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[ ] TestCafe
[ ] Playwright

Applicable plugins:

[ ] allure
[x] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] puppeteerCoverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[x] stepByStepReport
[ ] wdio

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

If a variable by reference is changed, all other plugins will have their values changed as well. Then, adding 'REST' in autoDelay.js, stepByStepReport.js will have 'REST' to.
I only changed the "supportedHelpers" to variable by value, allowing to change values only in autoDelay.js.

oh, interesting @andrerleao. I didn’t know this 😅 .

Probably we consider to add test for this.

We have removed REST helper from a list so this PR is not needed anymore

hey @DavertMik regarding this If a variable by reference is changed, all other plugins will have their values changed as well. Then, adding 'REST' in autoDelay.js, stepByStepReport.js will have 'REST' to. I thought this PR is still needed?

> We removed the REST helper from a list, so this PR is no longer needed
Hello @DavertMik, this is the problem!
In the changes to remove the REST helper, we added this bug :'(
In the autoDelay.js file, the supoortedHelpers variable is declared by reference.

If a variable by reference is changed, all other plug-ins will have their values changed as well, so by adding REST helper to the autoDelay.js file, the plugin, stepByStepReport.js will have 'REST' as well.

In this PR we changed the declaration of the variable to be by value, so we changed the list only in this plugin.
Please reconsider this PR.****


Help: how to make the region story for httpsCallables?

I think the region story of Firebase Cloud Functions callables is broken, and would like to get advice & practical use cases where people use httpsCallables with one or multiple regions.
firebase-tools 9.12.0 changed the behaviour of the emulators. Before, it ran everything in us-central1. Now it seems to use regions.
This is good. But how should the firebaseClientLike interfaces reflect this??? (tests broke on firebase-tools 9.12.0)

My understanding of the Firebase regions, with callables

Functions code must declare the region in its code:
const regionalFunctions = functions.region("mars-central2");

Client needs to know, in which region it wants to reach the function (this is fair).

Problem: These two settings are related, but separately defined.

I don't want to go with the "let's just test with default region" because that's too easy.
I want the Cloud Functions implementations be what one would have for production. No test awareness, there.
One doesn't need to test all the regions with the emulator (if functions were to be deployed to multiple). Also, let's presume all regions have the same set of functions?? (and testing any one of them in emulator is enough)

In production, one can use the functions:config:set regions.0 method for passing the functions region as a configuration instead of fixed in the code (the code still reads it).. We cannot rely on this for testing this repo (since we don't have an active Firebase project), but should be compatible with it.
Note that also in that method, setting the regions is done separately for the client and the functions.

IF Firebase were to declare the client-side Functions regions in firebase.json, it would make this easy for us. We'd just take the value from there. Currently (May 2021) they provide it in code.
Choices
A. Take the region from firebase.json as a custom field.
Pro:

cleaner
provides a neat transition if Firebase ever were to move in this direction
Con:
not how Firebase clients do it

B. Provide a way in the httpsClientLike API to provide the region.
Firebase JS SDK has region as the 2nd parameter of getFunctions(). We don't have getFunctions() concept.
Pro:

like Firebase does it
Con:

C. Something else - setRegion
Provide a setRegion function that Jest tests can call, to state which region the httpsCallable calls would go to. If the function is not called, it's default ("us-central1").
Pro:

simple, straightforward
Con:

Implemented setRegion in 554013066cf5fffe6cd9bfc6779353da352dd997


Fixed setMouseCursorGrabbed on Linux

Description: Fixed the issue https://github.com/SFML/SFML/issues/1671 by setting m_cursorGrabbed to false when you disable grabbing. Without this change, every time we receive a FocusIn event (When you unfocus and refocus the window) it reconfines the mouse to the window even if setMouseCursorGrabbed was set to false. I tested with the code sample used in the issue and the problem was resolved.

SFMLBuildMaster: Build this please.

SFMLBuildMaster: Build this please.

Thanks a lot of spotting the issue and providing a fix! 🙂

Thanks a lot of spotting the issue and providing a fix! 🙂


Include WMStats allWorkflows view in erlang

This PR addresses the issue #6837.
I translated the WMStats view allWorkflows to Erlang.
After a diff comparison, everything seems to be working just as it should. :)
@amaltaro and @ticoann, could you please double check?

Thanks Bruno

Test this please

Actually this view is used by agent which doesn't have Erlang version set for couch app.  So I will hold on to this until we change the agent to set up the couch app.

test this please


Fonts License

The fonts used on the PDFKit library are free for commercial use?
The thing is, the style guide specifications manual for the QR-bill says that the sans-serif fonts permitted are:

Arial
Frutiger
Helvetica
Liberation Sans

And by default the library uses Helvetica but also gives you the option to use Times and Courier.
Sorry if this is unrelated to an actual issue, just want it to make sure where are this fonts coming from and if we would need to replace them.

I don't know for sure.
I think the fonts come from the Core 14 AFM Files, whose readme states that they can be used for any purpose.
There  also was an issue in PDFKit discussing something about font licensing, which also implies that the fonts are free for commercial use. But this is something the developers of PDFKit would have to answer.

Thanks for the quick answare, I'll take a closer look


MOTD Update?

It works fine in S3 but since it's not updated for S3 it auto disables every time the game is launched. Is there a way to keep it enabled or get it updated to the current version?

Nevermind I found how to stop it auto disabling, but having it up to date would be amazing since it's such a nice mod.

Can you tell me how to do it

@wdragondragon ESC > MODDING > Top left-hand corner "Auto Disable Outdated Mods"


Integrate character index with the backend

Closes #105
Description
The data originally displayed on the character page was provided in the form of mock data. This has been replaced and the data displayed on the character page is obtained through the props passed in the Inertia render request.
Changes made
-Removed character mock data
-Added new type 'CharacterRowData' to handle the data acquired from the database
-Adjust the Character and CharacterTable components to use the Inertia passed props instead of mock data
-Refactor few Character variable names to simply and/or better reveal purpose
How you can test it

run 'php artisan migrate:fresh && php artisan db:seed'
login with an existing user:
-- 1. run 'php artisan tinker'
-- 2. use command 'User::first()' to obtain the first user's email
-- 3. Log in using the user's email and password : password
navigate to localhost/character to display a table of characters assigned to the logged in user

also unit test failed


[top-level,test,cdc] Fix CDC failure for chip_sw_power_idle_load

Description
This test fails due to an unexpected fatal alert from rstmgr. However, this is not really an alert but a ping response, but apparently the alert_esc_agent looses track of the ping request. This only fails when CDC instrumentation is enabled.
To reproduce it, set cdc_instrumentation_enabled to 1 in chip_sim_cfg, and run
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_power_idle_load -s<PHONE_NUMBER>
It can also be reproduced for some of multiple seeds.
The error message is as follows:
UVM_ERROR @ 3061.930698 us: (cip_base_vseq.sv:519) [uvm_test_top.env.virtual_sequencer.chip_sw_power_idle_load_vseq] Check failed 0 == cfg.m_alert_agent_cfgs[alert_name].vif.get_alert() (0 [0x0] vs 1 [0x1]) Alert rstmgr_aon_fatal_cnsty_fault fired unexpectedly!
You will see there is an incoming ping request that is causing the assertion of the outgoing alert transition. For additional debug help you can compare the test behavior with and without cdc instrumentation enabled. This failure could be related to https://github.com/lowRISC/opentitan/issues/3275, which is pending.

I think this is fixed by #19235. When I run ./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_power_idle_load -s<PHONE_NUMBER> --reseed 8 on the tip of the branch in that PR, I get 8 passes. Does that show that this is fixed by that PR?

@rswarbrick You are probably right this is fixed, since I also cannot reproduce it with 12 reseeds. Closing it.


Add sticky-air subduction benchmark

Adds the subduction benchmark from Schemling et al. 2008 in 2D and pseudo-3D (8 cells in the y-dimension).


Informational Meeting - Tracking Azure Communication Services

This meeting was created by Jorge Garcia Hirota.

It will be used to Track the conversation in the informational Session for the Azure Communication Services Service.

Detailed meeting information and documents provided can be accessed here

https://github.com/Azure/azure-rest-api-specs/issues/20040

Duplicate #20040


Use renamed alias when restoring a snapshot with rename parameters

Use renamed alias when restoring a snapshot with rename parameters
AND alias existed (which is the case only for partitioned tables)
Otherwise restore happens into original table instead of the renamed one due to using wrong alias.
Tests missed this because we checked only that new partitions were created but didn't check the contents of the source/target tables
Closes https://github.com/crate/crate/issues/15980

Fix for partitioned tables broke regular tables, pushed a fixup to fix it.


The Result of WTQ on tapas_wtq_wikisql_sqa_masklm_large_reset model  is only 39.04%

Thanks for releasing the new pre-trained model yesterday. I test the WTQ on tapas_wtq_wikisql_sqa_masklm_large_reset model. But the result is only 39.04% on the WTQ test dataset. What is the reason about that? My commend line is as follows:
python3 run_task_main.py
--task=WTQ
--output_dir=/home/cjc/tapas-master/WTQ  --model_dir=/home/cjc/tapas-master/tapas_wtq_wikisql_sqa_masklm_large_reset
--init_checkpoint=/home/cjc/tapas-master/tapas_wtq_wikisql_sqa_masklm_large_reset/model.ckpt
--bert_config_file=/home/cjc/tapas-master/tapas_wtq_wikisql_sqa_masklm_large_reset/bert_config.json
--mode="predict_and_evaluate" --use_tpu=False --iterations_per_loop=5 --test_batch_size=4 --max_seq_length=512

You need to set the reset parameter and I am just realizing that that's not possible with the current run_task_main.
I'll push a fix for that.
In the meantime, can you test that the tapas_wtq_wikisql_sqa_masklm_large model produces the reported accuracy?

I pushed the fix you can now run run_task_main.py with --reset_position_index_per_cell for the reset models.

Thanks for your reply. I tested WTQ on the tapas_wtq_wikisql_sqa_masklm_large model just now and got the reported accuracy on readme

Nice! Thanks for verifying.


Table 'MySQL.user' doesn't exist

[20:28:41] [INFO] Connect target success
[20:28:41] [INFO] testing if the target envirment is suitable
[20:28:41] [INFO] target envirment is suitable
[20:28:41] [INFO] testing power baseline
[20:28:41] [ERROR] run mysql  system account can login
[20:28:41] [INFO] run mysql  account check finish
Traceback (most recent call last):
File "db_baseline.py", line 93, in
result = checkscript.runtest()
File "/usr/local/soft/DB_BaseLine-master/script/db_baseline_basic.py", line 85, in runtest
self.run_power_test()
File "/usr/local/soft/DB_BaseLine-master/script/mysql_baseline.py", line 80, in run_power_test
result = self.getOneLine(sql)
File "/usr/local/soft/DB_BaseLine-master/script/mysql_baseline.py", line 473, in getOneLine
self.cursor.execute(sql)
File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 165, in execute
result = self._query(query)
File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 321, in _query
conn.query(q)
File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 860, in query
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1061, in _read_query_result
result.read()
File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1349, in read
first_packet = self.connection._read_packet()
File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1018, in _read_packet
packet.check_error()
File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 384, in check_error
err.raise_mysql_exception(self._data)
File "/usr/lib/python2.7/site-packages/pymysql/err.py", line 107, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.ProgrammingError: (1146, u"Table 'MySQL.user' doesn't exist")

原因是 Linux默认是区分大小写
#检查默认管理员账号
sql = "SELECT * from MySQL.user where user='root';"
不知道作者你当时的环境是不是不区分大小写

对 不区分大小写

script/mysql_baseline.py文件的MYSQL全部替换成mysql


Two different versions of @optimizely/js-sdk-utils in final bundle

Hello!
I'm currently working improving load times of a web-app & noticed thanks to inspectpack that on the app final bundle there are two different versions of @optimizely/js-sdk-utils, 0.1.0 & 0.4.0
see the report here:

I could resolve it setting a resolution to always use 0.4.0, but not sure if safe? could lead to bad functioning of the library? Also would like for this library to not introduce duplicates (& increase bundlesize/loadtimes) since I like it & use it on various projects :)
What's a feasible solution? is there any reason in particular @optimizely/react-sdk is still using<EMAIL_ADDRESS>?

We just fixed this in @optimizely/react-sdk 2.8.0


Colab notbook run fails

Hi the owner of this github,
Your colab notebook (link) run fails with error (see screenshot below) : "ModuleNotFoundError: No module named 'utils'"

Seems that you can fix it as follows: replacing 'from utils.logging_helper import setup_logger' by 'from yolact_edge.utils.logging_helper import setup_logger' (i.e. add yolact_edge. before utils)

May be late reply, but still relevant.
What is happening is that: "utils" folder directory is "./yolact_edge/yolact_edge/", but cwd is "./yolact_edge/", that's why could not find the utils folder out of "./yolact_edge/".
I have solved the issue: and you can follow the link : https://colab.research.google.com/drive/1Jqb45oxsNbHk1btTwUlaT3u-HOgckKSP?usp=sharing.
Thanks Nikhil Rasal for pointing out the issue correctly.


Many selects on a page makes stop script

Hi, I am new and congratulations for this excelent plugin.
I am using it, but now I have hundreds of ajax selectpicker and when loading page, it lasts long time to load it.
I saw that the command:
$('.selectpicker').selectpicker().filter('.with-ajax').ajaxSelectPicker(options);
is the problem.
How can I optimize it? Any suggestions?
Tks,
Lee

any time you have that many selects its going to be select. That is actually coming from selectpicker because it needs to replace the original selects with its own.  That means it's injecting a lot of DOM elements and replacing the original selects.  All that is very expensive.  You have a couple options:
First is, do they all really need to be on one page?  If not break the process into multiple pages.  If they all REALLY need to be on one page then you can try only initializing them once they are in the viewport.  This is more difficult and you would need to figure out how to do it, but it should be doable.
Either way there's not much Ajax bootstrap select can do so marking this as won't fix, and closing.  Let me know if you have any other questions.


[Web] Canvaskit raise errors on latest Chrome stable version

Steps to reproduce

Install google Chrome in version 126.0.6478.57
Access ANY flutter web app using canvaskit, like https://flutter.github.io/samples/web/material_3_demo/
Observe that the initial page load is OK, but after a few page refreshes, the app starts displaying a blank page and logging a LOT of errors related to canvaskit.js.

Expected results
No errors on latest chrome
Actual results
unusable flutter web apps
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Unexpected errors compiling sksl_shared:
Y @ canvaskit.js:170
canvaskit.js:170
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .0001
Y @ canvaskit.js:170
canvaskit.js:170 ...pe);$es3 $pure $genHType fwidth($genHType);$pure half4 unpremul(half4 a){return half4(a.xyz/max(a.w,.0001),a.w);}$pure float4 unpremul(float4 a){return float4(a.xyz/max(a.w,.0001),a.w);}$pure half4 $unprem...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .0001
Y @ canvaskit.js:170
canvaskit.js:170 ...return half4(a.xyz/max(a.w,.0001),a.w);}$pure float4 unpremul(float4 a){return float4(a.xyz/max(a.w,.0001),a.w);}$pure half4 $unpremul_polar(half4 a){return half4(a.x,a.yz/max(a.w,.0001),a.w);}$pure half4 ...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .0001
Y @ canvaskit.js:170
canvaskit.js:170 ...loat4(a.xyz/max(a.w,.0001),a.w);}$pure half4 $unpremul_polar(half4 a){return half4(a.x,a.yz/max(a.w,.0001),a.w);}$pure half4 $rgb_to_hsl(half3 b,half d){half4 e=b.y<b.z?half4(b.zy,-1.,.6666667):half4(b.yz,...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .333333343
Y @ canvaskit.js:170
canvaskit.js:170 ...w);}$pure half4 $rgb_to_hsl(half3 b,half d){half4 e=b.y<b.z?half4(b.zy,-1.,.6666667):half4(b.yz,0.,-.333333343);half4 f=b.x<e.x?half4(e.x,b.x,e.yw):half4(b.x,e.x,e.yz);half h=f.x;half i=h-min(f.y,f.z);half j=h-...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .0001
Y @ canvaskit.js:170
canvaskit.js:170 ...):half4(b.x,e.x,e.yz);half h=f.x;half i=h-min(f.y,f.z);half j=h-i*.5;half k=abs(f.w+(f.y-f.z)/(i*6.+.0001));half l=i/((d+.0001)-abs(j*2.-d));half m=j/(d+.0001);return half4(k,l,m,d);}$pure half3 $hsl_to_rg...

Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .333333343
Y @ canvaskit.js:170
canvaskit.js:170 ...d);}$pure half3 $hsl_to_rgb(half3 a){half b=(1.-abs(2.*a.z-1.))*a.y;half3 c=a.xxx+half3(0.,.6666667,.333333343);half3 d=saturate(abs(fract(c)*6.-3.)-1.);return(d-.5)*b+a.z;}$pure half4 $hsl_to_rgb(half3 b,half ...

Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .002
Y @ canvaskit.js:170
canvaskit.js:170 ...($hsl_to_rgb(b)*c,c));}$pure half3 $css_lab_to_xyz(half3 a){half3 d;d.y=(a.x+16.)*.00862069;d.x=a.y*.002+d.y;d.z=d.y-a.z*.005;half3 g=pow(d,half3(3.));half3 h=half3(g.x>.008856452?g.x:(116.*d.x-16.)*.0011...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .005
Y @ canvaskit.js:170
canvaskit.js:170 ...;}$pure half3 $css_lab_to_xyz(half3 a){half3 d;d.y=(a.x+16.)*.00862069;d.x=a.y*.002+d.y;d.z=d.y-a.z*.005;half3 g=pow(d,half3(3.));half3 h=half3(g.x>.008856452?g.x:(116.*d.x-16.)*.00110705639,a.x>8.000001?...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .008856452
Y @ canvaskit.js:170
canvaskit.js:170 ....y=(a.x+16.)*.00862069;d.x=a.y*.002+d.y;d.z=d.y-a.z*.005;half3 g=pow(d,half3(3.));half3 h=half3(g.x>.008856452?g.x:(116.*d.x-16.)*.00110705639,a.x>8.000001?g.y:a.x*.00110705639,g.z>.008856452?g.z:(116.*d.z-16.)...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .00110705639
Y @ canvaskit.js:170
canvaskit.js:170 ...*.002+d.y;d.z=d.y-a.z*.005;half3 g=pow(d,half3(3.));half3 h=half3(g.x>.008856452?g.x:(116.*d.x-16.)*.00110705639,a.x>8.000001?g.y:a.x*.00110705639,g.z>.008856452?g.z:(116.*d.z-16.)*.00110705639);return h*half3(.9...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .00110705639
Y @ canvaskit.js:170
canvaskit.js:170 ...=pow(d,half3(3.));half3 h=half3(g.x>.008856452?g.x:(116.*d.x-16.)*.00110705639,a.x>8.000001?g.y:a.x*.00110705639,g.z>.008856452?g.z:(116.*d.z-16.)*.00110705639);return h*half3(.9642956,1.,.825104535);}$pure half3...

Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .00110705639
Y @ canvaskit.js:170
canvaskit.js:170 ...g.x:(116.*d.x-16.)*.00110705639,a.x>8.000001?g.y:a.x*.00110705639,g.z>.008856452?g.z:(116.*d.z-16.)*.00110705639);return h*half3(.9642956,1.,.825104535);}$pure half3 $a(half3 a){return half3(a.z,a.y*cos(radians(a...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .396337777
Y @ canvaskit.js:170
canvaskit.js:170 ...(half3 a){return $css_lab_to_xyz($a(a));}$pure half3 $css_oklab_to_linear_srgb(half3 a){half b=(a.x+.396337777*a.y)+.215803757*a.z;half c=(a.x-.105561346*a.y)-.06385417*a.z;half d=(a.x-.08948418*a.y)-1.29148555...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .215803757
Y @ canvaskit.js:170
canvaskit.js:170 ... $css_lab_to_xyz($a(a));}$pure half3 $css_oklab_to_linear_srgb(half3 a){half b=(a.x+.396337777*a.y)+.215803757*a.z;half c=(a.x-.105561346*a.y)-.06385417*a.z;half d=(a.x-.08948418*a.y)-1.29148555*a.z;half e=(b*b...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .105561346
Y @ canvaskit.js:170
canvaskit.js:170 ...ure half3 $css_oklab_to_linear_srgb(half3 a){half b=(a.x+.396337777*a.y)+.215803757*a.z;half c=(a.x-.105561346*a.y)-.06385417*a.z;half d=(a.x-.08948418*a.y)-1.29148555*a.z;half e=(b*b)*b;half f=(c*c)*c;half g=(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .06385417
Y @ canvaskit.js:170
canvaskit.js:170 ...klab_to_linear_srgb(half3 a){half b=(a.x+.396337777*a.y)+.215803757*a.z;half c=(a.x-.105561346*a.y)-.06385417*a.z;half d=(a.x-.08948418*a.y)-1.29148555*a.z;half e=(b*b)*b;half f=(c*c)*c;half g=(d*d)*d;return h...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .08948418
Y @ canvaskit.js:170
canvaskit.js:170 ...a){half b=(a.x+.396337777*a.y)+.215803757*a.z;half c=(a.x-.105561346*a.y)-.06385417*a.z;half d=(a.x-.08948418*a.y)-1.29148555*a.z;half e=(b*b)*b;half f=(c*c)*c;half g=(d*d)*d;return half3((4.0767417*e-3.307711...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .230969936
Y @ canvaskit.js:170
canvaskit.js:170 ...-1.29148555*a.z;half e=(b*b)*b;half f=(c*c)*c;half g=(d*d)*d;return half3((4.0767417*e-3.3077116*f)+.230969936*g,(-1.268438*e+2.60975742*f)-.341319382*g,(-.00419608643*e-.7034186*f)+1.70761466*g);}$pure half3 $...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .341319382
Y @ canvaskit.js:170
canvaskit.js:170 ...*c)*c;half g=(d*d)*d;return half3((4.0767417*e-3.3077116*f)+.230969936*g,(-1.268438*e+2.60975742*f)-.341319382*g,(-.00419608643*e-.7034186*f)+1.70761466*g);}$pure half3 $css_okhcl_to_linear_srgb(half3 a){return...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .00419608643
Y @ canvaskit.js:170
canvaskit.js:170 ...*d)*d;return half3((4.0767417*e-3.3077116*f)+.230969936*g,(-1.268438*e+2.60975742*f)-.341319382*g,(-.00419608643*e-.7034186*f)+1.70761466*g);}$pure half3 $css_okhcl_to_linear_srgb(half3 a){return $css_oklab_to_li...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .014804
Y @ canvaskit.js:170
canvaskit.js:170 ...o_linear_srgb($a(a));}$pure half3 $css_oklab_gamut_map_to_linear_srgb(half3 a){const half2 r=half2(-.014804,-.162608);const half2 s=half2(-.276786,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .162608
Y @ canvaskit.js:170
canvaskit.js:170 ...srgb($a(a));}$pure half3 $css_oklab_gamut_map_to_linear_srgb(half3 a){const half2 r=half2(-.014804,-.162608);const half2 s=half2(-.276786,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(.409702,-...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .276786
Y @ canvaskit.js:170
canvaskit.js:170 ...oklab_gamut_map_to_linear_srgb(half3 a){const half2 r=half2(-.014804,-.162608);const half2 s=half2(-.276786,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(.409702,-.912219))<0.){if(dot(z,half2(....
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .004193
Y @ canvaskit.js:170
canvaskit.js:170 ...mut_map_to_linear_srgb(half3 a){const half2 r=half2(-.014804,-.162608);const half2 s=half2(-.276786,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(.409702,-.912219))<0.){if(dot(z,half2(.460276,....
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .409702
Y @ canvaskit.js:170
canvaskit.js:170 ...,-.162608);const half2 s=half2(-.276786,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(.409702,-.912219))<0.){if(dot(z,half2(.460276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .460276
Y @ canvaskit.js:170
canvaskit.js:170 ...6,.004193);half2 z=a.yz;half A;half2 B;half2 C;if(dot(z,half2(.409702,-.912219))<0.){if(dot(z,half2(.460276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.0385...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .171122
Y @ canvaskit.js:170
canvaskit.js:170 ...;half2 C;if(dot(z,half2(.409702,-.912219))<0.){if(dot(z,half2(.460276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331)...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .102047
Y @ canvaskit.js:170
canvaskit.js:170 ...(.409702,-.912219))<0.){if(dot(z,half2(.460276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .092029
Y @ canvaskit.js:170
canvaskit.js:170 ...if(dot(z,half2(.460276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .038533
Y @ canvaskit.js:170
canvaskit.js:170 ...60276,.887776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .00165
Y @ canvaskit.js:170
canvaskit.js:170 ...7776))<0.){if(dot(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .232572
Y @ canvaskit.js:170
canvaskit.js:170 ...(z,half2(-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .094331
Y @ canvaskit.js:170
canvaskit.js:170 ...-.171122,.98525))<0.){A=.102047;B=r;C=s;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,....
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .318495
Y @ canvaskit.js:170
canvaskit.js:170 ...;}else{A=.092029;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .081709
Y @ canvaskit.js:170
canvaskit.js:170 ...;B=half2(-.038533,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .034601
Y @ canvaskit.js:170
canvaskit.js:170 ...,-.00165);C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .002215
Y @ canvaskit.js:170
canvaskit.js:170 ...;C=half2(-.232572,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .012185
Y @ canvaskit.js:170
canvaskit.js:170 ...,-.094331);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.90...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .338031
Y @ canvaskit.js:170
canvaskit.js:170 ...1);}}else{if(dot(z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.4215...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .091132
Y @ canvaskit.js:170
canvaskit.js:170 ...z,half2(.947925,.318495))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z...

Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .034139
Y @ canvaskit.js:170
canvaskit.js:170 ...))<0.){A=.081709;B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.91742...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .01817
Y @ canvaskit.js:170
canvaskit.js:170 ...B=half2(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.11390...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .37855
Y @ canvaskit.js:170
canvaskit.js:170 ...(-.034601,-.002215);C=half2(.012185,.338031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=hal...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .421562
Y @ canvaskit.js:170
canvaskit.js:170 ...38031);}else{A=.091132;B=half2(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.01...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .397919
Y @ canvaskit.js:170
canvaskit.js:170 ...(.07037,.034139);C=half2(.01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .113902
Y @ canvaskit.js:170
canvaskit.js:170 ....01817,.37855);}}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .090836
Y @ canvaskit.js:170
canvaskit.js:170 ...}}else{if(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.2843...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .036251
Y @ canvaskit.js:170
canvaskit.js:170 ...f(dot(z,half2(-.9068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.284304);}}el...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .226781
Y @ canvaskit.js:170
canvaskit.js:170 ...068,.421562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.284304);}}else{A=.102047;B=r;...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .018764
Y @ canvaskit.js:170
canvaskit.js:170 ...562))<0.){if(dot(z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.284304);}}else{A=.102047;B=r;C=s;}}ha...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .161739
Y @ canvaskit.js:170
canvaskit.js:170 ...z,half2(-.397919,-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.284304);}}else{A=.102047;B=r;C=s;}}half D=1.;half E=do...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .008202
Y @ canvaskit.js:170
canvaskit.js:170 ...-.917421))<0.){A=.113902;B=half2(.090836,.036251);C=half2(.226781,.018764);}else{A=.161739;B=half2(-.008202,-.264819);C=half2(.187156,-.284304);}}else{A=.102047;B=r;C=s;}}half D=1.;half E=dot(B,z);if(E>0.){h...

Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .01
Y @ canvaskit.js:170
canvaskit.js:170 ...ar_srgb($a(a));}$pure half3 $css_hsl_to_srgb(half3 b){b.x=mod(b.x,360.);if(b.x<0.){b.x+=360.;}b.yz*=.01;half3 c=mod(half3(0.,8.,4.)+b.x*.0333333351,12.);half d=b.y*min(b.z,1.-b.z);return b.z-d*clamp(min(...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .0333333351
Y @ canvaskit.js:170
canvaskit.js:170 ..._to_srgb(half3 b){b.x=mod(b.x,360.);if(b.x<0.){b.x+=360.;}b.yz*=.01;half3 c=mod(half3(0.,8.,4.)+b.x*.0333333351,12.);half d=b.y*min(b.z,1.-b.z);return b.z-d*clamp(min(c-3.,9.-c),-1.,1.);}$pure half3 $css_hwb_to_...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^^^^^^^^^
Y @ canvaskit.js:170
canvaskit.js:170 error: 1: floating-point value is too large: .01
Y @ canvaskit.js:170
canvaskit.js:170 ...(b.z,1.-b.z);return b.z-d*clamp(min(c-3.,9.-c),-1.,1.);}$pure half3 $css_hwb_to_srgb(half3 a){a.yz*=.01;if(a.y+a.z>=1.){half b=a.y/(a.y+a.z);return half3(b);}half3 b=$css_hsl_to_srgb(half3(a.x,100.,50.))...
Y @ canvaskit.js:170
canvaskit.js:170                                                                                ^^^
Y @ canvaskit.js:170
canvaskit.js:170 64 errors
Y @ canvaskit.js:170
canvaskit.js:170
Y @ canvaskit.js:170
canvaskit.js:170 ../../flutter/third_party/skia/src/sksl/SkSLModuleLoader.cpp:216: fatal error: "Unable to load module sksl_shared"
Y @ canvaskit.js:170
main.dart.js:7307 Uncaught RuntimeError: unreachable
    at canvaskit.wasm:0x72be9
    at canvaskit.wasm:0x2679b0
    at canvaskit.wasm:0x14bea6
    at canvaskit.wasm:0x267ee2
    at canvaskit.wasm:0xb325e
    at canvaskit.wasm:0x6f03b
    at canvaskit.wasm:0x2dfb10
    at canvaskit.wasm:0x2e5163
    at canvaskit.wasm:0x483c22
    at canvaskit.wasm:0x1c555

Flutter Doctor output
Doctor output
[Paste your output here]

For some reason not everybody seems affected by this. I could confirm the bug on another macbook pro's chrome in our office, but two other people tried the same operation and got a working web application

Hi @Miiite, are you seeing this issue only on macs?
Are the macs intel macs or apple silicon macs? I just checked on my m1 Mac and the website opens just fine.
What do you see when you enter chrome://gpu/ in chrome? Can you share the results?

Unfortunately I only have a mac available right now so I would not be able to tell you if I can reproduce it on Windows.
But here are my logs of chrome://gpu
about-gpu-2024-06-13T14-17-36-199Z.txt
Regarding the mac itself it's an Apple sillicon (M1 Pro)

Hi @Miiite, what versions of macOS are the devices that don't reproduce the issue running? It appears that you might be using an older version of Sonoma. Can you check if upgrading to the latest version of macOS resolves this issue?
I also checked on my dell xps 13 running windows 11 and the website loads properly without any issues

I'm on macOS 14.0, and I'll try to update to see if it changes anything, but a co-worker si on macOS 12.5 and has no issues whatsoever.
I'm starting to wonder if it's not a Google Chrome related issue, because I can see that as soon as I open the Chrome Dev Tools, the bug ... disappears ?
You can see in this video, that I initially open and refresh the website multiple times. At some point the website crashes with the logs I pasted in my initial post.
Then I open the Chrome Dev Tools, and refresh the page, and everything starts working again.
Then closed the dev tools, refreshed the page, and after one or two refreshes the website crashes again.
https://github.com/flutter/flutter/assets/475526/7427c39c-8cb4-415a-97d7-b929b8ac98c3

@danagbemava-nc I updated to MacOS 14.5 and am still facing the issue :(

Adding another datapoint here - I've been trying to track down what I assume is also this issue.
We have only two users that are having issues since updating to chrome 126.0.6478.62, where after a handful of app reloads they will get stuck on a blank screen.
This behavior exists running either flutter 3.19, or 3.22. These users are also both using apple silicon (a M2 and a M3 pro machine).

I am also seeing these errors today in Chrome 126.0.6478.62 on MacOS 14.5 running on M1. Using the latest flutter 3.22.2.
I have been testing a flutter app regularly for that last week or so and I have not seen this issue before today. I don't see these errors on Safari or Firefox on the same machine.

Hi @npabuwal, @ehedrick, thanks for the reports.  Are either of you able to reproduce the issue with https://flutter.github.io/samples/web/material_3_demo/ if not, could you provide a minimal sample that we could use?
Thank you

I also have the same issue.
Chrome version: 126.0.6478.62 (Official Build) (arm64)
But the Flutter web app works fine on Safari.

Hi @danagbemava-nc, the issue occurs randomly so a bit hard to reproduce. I am yet to see it with the material demo app ( https://flutter.github.io/samples/web/material_3_demo/ ), but it looks like any flutter app could run into this issue. ~5 people have already commented on this thread and I believe all of us have encountered it with different apps. I think a lot of users/apps might be getting impacted out there.
I am unable to post a code sample of my private repo but will post a sample if I can. Hopefully someone else will post one before me.
Thanks.

Ah, posted too soon. I just saw the video posted by the author of this issue ( https://github.com/flutter/flutter/issues/150193#issuecomment-2167399253 ) and did what was shown in the video i.e. kept refreshing the page. Within just a few refreshes, I encountered the issue with https://flutter.github.io/samples/web/material_3_demo/

I was then able to do the same thing with https://flutter.github.io/samples/web/simplistic_editor/

So, it can happen with almost any flutter web app. I think this issue needs to be investigated at a high priority.
@danagbemava-nc

Thank you all for the updates.
Labeling this for further investigation. While I can't seem to reproduce the issue on my device after several refreshes with both samples, there's enough evidence of an issue for an investigation.
cc @yjbanov

I'm NOT seeing this on my mac. But we'll dig in!

Let me take that back. Easy to reproduce with devtools CLOSED. With Chrome 126 on an M1 Mac.

Anyone seeing this: please go to Chrome's about:gpu page, click "Download Report to File", copy/paste it into pastebin, and post the link here. Also the full contents of about:version into a separate pastebin. Thanks.

https://gist.github.com/kevmoo/13c390edf221e9ade5602c04051b8b31

Chromium-side issue: https://g-issues.chromium.org/issues/347961785

I have two Flutter apps one with Flutter 3.19.3 and another one with 3.22.0. Only the latest Flutter version is affected by this bug. Mac M1 Chrome Version 126.0.6478.62

Per https://crbug.com/347961785 , the root cause has been identified and fixed. In theory all that should be necessary to pick it up is to quit and restart Chrome.

Great job with the investigation and the quick fix, thanks! I am not seeing the issue anymore.

Yup after restarting chrome, the issue seems to be gone.

Closing this out! Thank you Chrome, friends! 🙏 👍


python311Packages.botocore-stubs: 1.31.34 -> 1.31.36

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.botocore-stubs
python310Packages.botocore-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist


Zoning Appeals, vuejs and carto update.

Hi Tim,
This is the new version of Zoning Appeals, we have the green light from Andrew N. to deploy this update.
The Vuejs application for production is in the "dist" folder.
The same folder is already running on https://cityofphiladelphia.github.io/zoning-appeals-stage/ if you want to take a look before the merge and deploy on this official repository.
Any questions let me know,
Thank you very much.

Logo and breadcrumbs issue fixed.

Now fixed the scroll behavior when you are on the bottom of the first page and do click on any of the items of the table, now, instead of going to the bottom on the next page, it stays on top like a standard page redirect.

I did a last update to setup dist/ to work correctly on http://cityofphiladelphia.github.io/zoning-appeals/

Once you merge to master, it won't deploy automatically. Technically you could do what the current README.md says and create an orphan branch inside the dist directory and deploy it manually, but probably the easiest thing to do would be to wire it up with Travis-CI, similar to how we've done it for carto-api-explorer.
First, remove the dist folder from source control by adding it to .gitignore and using git rm -rf dist. This directory isn't "source code," it's compiled/built code that gets deployed, so we'll have our CI tool actually do the building and deploy the result to gh-pages instead.
Second, add .travis.yml to the root directory with these contents:
language: node_js
node_js:
  - "6"
script:
  - npm run build
deploy:
  provider: pages
  local_dir: dist
  skip_cleanup: true
  github_token: $GITHUB_TOKEN
  on:
    branch: master

Third, in the travis ci dashboard, enable travis for this repository.
Fourth, in order for it to deploy to this repo, you'll need to give it a github token as an environment variable in the settings panel of travis-ci. To get a github token, go to your personal access tokens and create a new one. Make sure when you add it to travis, "display value in build log" is off.
Once that's done, you should be able to merge this pull request to master and watch it deploy! Make sure you have enough time to troubleshoot. I'm around to help on slack.


feat: effects called multiple time when adding new element for first ime

When a new node is added to the canvas, the useEffect hook for the previous node is triggered twice—once for the previous node and once for the new node. This causes the previous node to be removed and then re-added to the canvas, creating a flickering effect.
Previously, this issue didn’t occur because the canvas only supported a single child node at any given time. However, with the recent requirement to support multiple overlays within the same container, this behavior has surfaced as a problem.
From a technical perspective, I believe adding refs to the dependency array of the useEffect is unnecessary since refs are generally stable across React render cycles.
https://xsolla.atlassian.net/browse/LSTREAM-811

Unsure if you still wanted to merge this but happy to approve in the meantime before I look into the flickering

I’ll wait.


simplified css-importing syntax.

simplified @import summernote syntax and refactored the view template with unobtrusive javascript pattern.
So. You can import the summernote css in application.scss as follows:
...
@import "summernote";
...

Do you mean the usage of both should be described in README.md file ?

yes :)

I've just committed the updated README.md file. ^^
You can find it in the "Commits" tab on the top of this page.

Maybe, you should bump up to v<IP_ADDRESS> because the  file structure of stylesheets/ directory was changed. Please keep in mind that you should rake release the updated version to rubygems.org.


Overlap views

can i create overlap views like lazygit

Any updates on this...

Hello ! Try this : https://github.com/mrusme/neonmodem/commit/cd7b173cc7b9db8224d4cf944c6da5391516767d
It's a little bit tricky but it works fine.

@StephGD thx i will try it.
#102 discuss this feature closed this issue


DOMElement of type  cause issues : Popper consider it an array (because of length present)

Well I think everything is in the title :p
When using {parent: document.querySelector('form')}, Popper.js display a warning about having an array of Nodes instead of just one (which is truly just one) because a form element has a length key in it's object, making Popper believe it's an array.
It may be better to check for an existing element from a dom (like parentElement) to know if it's an array or not ?

Moreover, it fails with a "console.warning is not a function".
Here's the appropriate codepen : http://codepen.io/anon/pen/mPLXPX

Awesome ! :)

You're welcome :)


Changing text to force test restart

What is this PR doing?
opentok-meet is a public repo so there is no way to restart the test.  Only commits can force a retest.  This PR changes text and then reverts it.  After the tests pass, then https://github.com/opentok/opentok-meet/pull/81 will be out-of-date.  We can then pull in these changes and force a retest.
How should this be manually tested?
Make sure CI tests pass.
What are the relevant tickets?
N/A

@michaelwhittemore, please test.


Remove URL field from database connector templates

I thought we'd ticketed and done this already but maybe I'm misremembering. For Database connections, the URL field still shows up. We're moving to the Host/Port/Username/Password form so we need to hide this field. I know it's used for demos and, to make this easier for sales, I will save the credentials into a 1P form.

Dupe of #3763


Add tharunc

Have you read the Contributing Guidelines on Pull Requests?
Yes
(Write your answer here.)
Description
Added icons and badges in the readme.md.
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#1768
(Write your answer here.)

I don't see the point of how the README has been enhanced. Please take a look at some existing Projects and come up with a new design.

I don't see the point of how the README has been enhanced. Please take a look at some existing Projects and come up with a new design.

There is no file in the repo named templates. If you wish me to add the file. Please tell me what to add.

There is no file in the repo named templates. If you wish me to add the file. Please tell me what to add.


feat: add workload identity azurerm resources and helm template

Description of the changes
terraform azure resources and kube service accounts

@fsismondi I converted to draft while waiting for a rebase on main.


Add return types and PHP generics

Thanks for the PR, but I don't want to add types to the package quite yet. I'm not personally a big fan of them.

I'm not personally a big fan of them.

All right.
Maybe later you develop a love-relation with typehints ❤

Maybe later you develop a love-relation with typehints ❤

Maybe so! Don't give up on me yet 😉


Rook block device not working for ReadWriteMany

Whe trying to create a PersistentVolumeClaim with ReadWriteMany, I get the following error when running kubectl describe pvc <name>:
rook multi node access modes are only supported on rbd `block` type volumes

My cluster:yml:
apiVersion: ceph.rook.io/v1
kind: CephCluster
metadata:
  name: rook
  namespace: rook
spec:
  backend: ceph
  hostNetwork: false
  dataDirHostPath: /storage
  placement:
    all:
      tolerations:
      - key: node-role.kubernetes.io/master
        operator: Equal
        effect: NoSchedule
  cephVersion:
    image: ceph/ceph:v14.2.4-20190917
  mon:
    count: 3
    allowMultiplePerNode: false
  storage:
    useAllNodes: true
    useAllDevices: false
    storeConfig:
      databaseSizeMB: 1024
      journalSizeMB: 1024
    # Uncomment the following line and replace it with the name of block device used for storage:
    deviceFilter: sdb
    # Uncomment the following lines when using a directory for storage:
    #directories:
    #- path: /storage/data

/dev/sdb it works for ReadWriteOnce claims though, any ideas?
(Also, can create a separate issue if needed, but might be worth updating the image used for the ingress controller as the nginx version in the default is fairly old, I used k8s.gcr.io/ingress-nginx/controller:v0.45.0 as a drop-in replacement)

It is not the problem of Rook. The is because  PVC is Project/Namespace specific.  And PV is available cluster wide accessible.
One has to create respective PVC for namespace where it is needed and not in another Namespace. PVC cannot be cross referenced in another Namespace.

It is not the problem of Rook. You see that issue because PVC is Project/Namespace specific. And PV is available cluster wide accessible. One has to create respective PVC for namespace where it is needed and not in another Namespace. PVC cannot be cross referenced in another Namespace.

That answer is just wrong and doesn't even make any sense at all. It has nothing todo with any namespaces and the OP already gave a hint on what's the issue.
As @ericgraf pointed out in his comment, ceph-csi doesn't support ReadWriteMany for rbd volumes (most likely because rbd doesn't support it, which would make absolute sense given that it's block storage). This is not a rook issue and it won't be fixed by ceph either so this issue can be closed.


Enable log streaming for Python/Linux functions

Closing as duplicate of https://github.com/Microsoft/vscode-azurefunctions/issues/589
We currently have that in 'tracking' milestone since we use kudu to stream logs and I don't know how we'd do it without kudu.


Update akka-actor, akka-actor-typed, ... to 2.6.20

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-actor-typed
com.typesafe.akka:akka-cluster
com.typesafe.akka:akka-cluster-metrics
com.typesafe.akka:akka-cluster-sharding
com.typesafe.akka:akka-cluster-tools
com.typesafe.akka:akka-cluster-typed
com.typesafe.akka:akka-discovery
com.typesafe.akka:akka-multi-node-testkit
com.typesafe.akka:akka-persistence
com.typesafe.akka:akka-persistence-query
com.typesafe.akka:akka-persistence-typed
com.typesafe.akka:akka-pki
com.typesafe.akka:akka-slf4j
com.typesafe.akka:akka-stream
com.typesafe.akka:akka-stream-testkit
com.typesafe.akka:akka-stream-typed
com.typesafe.akka:akka-testkit

from 2.6.19 to 2.6.20.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.typesafe.akka" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.45%. Comparing base (c04d33c) to head (6a401c7).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1330      +/-   ##
==========================================
+ Coverage   79.35%   79.45%   +0.09%
==========================================
  Files         144      144
  Lines        5008     5008
  Branches      670      670
==========================================
+ Hits         3974     3979       +5
+ Misses       1034     1029       -5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


internal_url: Replace all replaceAll with replace.

Replaces all occurrences of string.replaceAll with string.replace as
replaceAll is a relatively new addition to the language and some JS
engines (notably the one that currently ships with the iOS version
of Zulip Mobile) do not yet support it. No functional changes.
See https://caniuse.com/mdn-javascript_builtins_string_replaceall

@andersk thoughts?  I wonder if there's a polyfill solution we could use instead.

We’re already polyfilling this.
https://github.com/zulip/zulip/blob/74989d8171da7be96df82295c1757b7c9e1c3f2d/babel.config.js#L14-L22
I’m not opposed to using .replace here, but the commit message is a bit misleading about the current state.

@gnprice Can we configure Zulip mobile to use a polyfill?

Using a polyfill in mobile should be quite possible in principle. But we don't currently, and introducing a general polyfill suite like "corejs" would be an infra project that would require some careful validation.
I expect that in the next few months we'll (a) upgrade to RN v0.65 and then (b) try using Hermes, and hopefully be able to switch to it: https://github.com/zulip/zulip-mobile/issues/4131#issuecomment-820859341 In that case, we'll have a single JS implementation in the app across all platforms. That will probably mean we get new-ish JS features like this one; if not, it'll certainly greatly simplify validating any solution like a polyfill. So given that that's coming soon, I'd prefer to not try introducing polyfills now, and instead go ahead and use .replace here.
On the current state, see here:
https://github.com/zulip/zulip-mobile/pull/5271#issuecomment-1058746975
https://github.com/zulip/zulip-mobile/pull/5271#issuecomment-1058672938
So .replaceAll isn't present in the JS engine we ship in the Android app, or in the JS engine we get from the system when running on iOS <13.4.

OK; I generally don't think of polyfills as expensive, but it's literally a one line change here.  I pushed back here a version with an added comment that I think addresses the concerns about commit message / documentation and I'm fine with merging.


Errors with URP & VR

I am getting the following errors when I try to run this in URP for VR (Oculus).
Is it possible to fix it or not at all?
SplatUtilities.compute: Kernel at index (0) requires features which are unavailable on the current platform - 'wavebasic'. Make sure '#pragma require' is used correctly as unnecessary arguments can restrict platform reach. UnityEngine.StackTraceUtility:ExtractStackTrace () GaussianSplatting.Runtime.GaussianSplatRenderer:InitSortBuffers (int) (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:423) GaussianSplatting.Runtime.GaussianSplatRenderer:CreateResourcesForAsset () (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:408) GaussianSplatting.Runtime.GaussianSplatRenderer:Update () (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:614)
SplatUtilities.compute: Kernel at index (0) is invalid UnityEngine.StackTraceUtility:ExtractStackTrace () GaussianSplatting.Runtime.GaussianSplatRenderer:InitSortBuffers (int) (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:424) GaussianSplatting.Runtime.GaussianSplatRenderer:CreateResourcesForAsset () (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:408) GaussianSplatting.Runtime.GaussianSplatRenderer:Update () (at ./Packages/Splatting/Runtime/GaussianSplatRenderer.cs:614)

This is probably kinda same as #26 -- right now this project "most likely" does not work on a mobile GPU (which Quest is) at all, and also likely does not work in VR. Maybe it does, maybe it does not.
The error you get might go away if you make the project use Vulkan instead of OpenGL graphics API. Or it might not. Or the device might not support Vulkan. I don't know, and I have tested on exactly zero mobile or VR setups.

Hello, please ask, have you solved this problem?

@Songxinlei if the question is about running it on Quest or some other VR device, then no, that is not solved, and I don't plan on solving it (I have no VR devices to test/develop on). If someone else would contribute a fix that works, I'd gladly accept it, but so far no one did.


[Doc] Most connectors lack documentation

Search before asking

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

Documentation Related
List of connectors without documentation

[ ] eventmesh-connector-dingtalk (author: @yanrongzhen )
[ ] #4608 (author: @xwm1992 )
[ ] #4606 (author: @mxsm )
[ ] #4604 (author: @epiao55 )
[ ] eventmesh-connector-knative (author: @fabian4 )
[ ] #4609 (author: @fabian4 )
[ ] eventmesh-connector-openfunction (author: @xwm1992 )
[ ] eventmesh-connector-pravega (author: @fabian4 )
[ ] eventmesh-connector-prometheus (author: @willimpo )
[ ] eventmesh-connector-pulsar (author: @g0715158 )
[ ] #4607 (author: @fabian4 )
[ ] eventmesh-connector-rabbitmq (author: @fabian4 )
[ ] eventmesh-connector-rocketmq (author: @xwm1992 )
[ ] #4605 (author: @TheR1sing3un )
[ ] eventmesh-connector-slack (author: @yanrongzhen )
[ ] eventmesh-connector-spring (author: @yanrongzhen )
[ ] eventmesh-connector-wechat (author: @wizardzhang )
[ ] eventmesh-connector-wecom (author: @yanrongzhen )

Currently, most connectors lack documentation, such as the functions of the current connector, descriptions of configuration items, precautions (if any), relevant official reference links (if any), and other content that needs to be explained in the documentation. This can cause difficulties for users, even directly hindering their use, and also increase the difficulty for other developers to understand or optimize the code.
The author information in the list does not mean that the corresponding document must be written by the author. Anyone, including the author, can write a document for the module you are interested in. If non authors encounter problems while writing documents, they can try contacting the corresponding author or community.
Welcome to select the module or modules that interest you and create the corresponding issue and PR to complete documents.
目前大部分的Connector缺少文档，比如当前Connector的功能、配置项的说明、需要注意的情况（如果有）、相关官方依据链接（如果有），等等其他需要在文档中说明的内容。这会给用户的使用造成困难，甚至直接阻碍了用户的使用，也提高了其他开发者对代码的理解或者优化难度。
列表中的作者信息不表示必须由作者来写相应的文档，包括作者在内的任何人都可以写您感兴趣的模块的文档。如果非作者写文档时遇到问题，可以尝试联系相应的作者或者社区。
欢迎选择您感兴趣的模块并创建相应的的issue和PR完成文档。
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[ ] I agree to follow this project's Code of Conduct *

@pandaapo Where should we put the doc? In the relevant project path or somewhere else like our offical website doc for better reference.

Hi, I would like to give it a try. I will create all the issues and will take up one of them.

@pandaapo I see that we have many connectors related to many technologies. Are there any new connectors that are on your roadmap?

@pandaapo Okay. that is fine. I just wanted to know if there was something in the development roadmap.

Anyone can take them up. I will work on them one by one based upon the difficulty level. If someone is interested they can assign themself.

@pandaapo I see that all the connectors have a dependency on the events-open connect-java module. Don't you think there should be documentation for that too for the developers?

@pandaapo I think it would be better if an author of the module publishes documentation for the module. Based on that then I can write for the other connectors. Meanwhile, I am trying to run EventMesh using Kafka as storage. Is it okay?

Okay. I will look into it. Thanks for the constant guidance @pandaapo :)

@fabian4 Do you have anything to say? Have you planned to write one or some of these documents?

@pandaapo I'll write it later. Sorry for late response.

@pandaapo   Jdbc connector doc will wirte it after the mysql sink finished


Review @primer/octicons-react usage, update/replace dependency

Our @primer/octicons-react package cannot be updated:

v17.11 breaks dom-chef
v19 uses forwardRef

There were a couple of attempts at fixing this:

https://github.com/refined-github/refined-github/pull/4044
https://github.com/refined-github/refined-github/issues/6493
https://github.com/refined-github/refined-github/issues/4058

Probably jsx-dom is the best transition we can do right now, but also it's probably not working with v19.
So I think the easiest way forward would be to:

import the raw SVG
have webpack turn it into JSX-compatible imports ("svgr")

This should be reasonably easy to implement and likely the most stable and lightweight solution (octicons-react has more code than we need, at this point)

Extracted from https://github.com/refined-github/refined-github/issues/6000#issuecomment-1426645966

Yeah let's restore SVGR soon so we'll skip all the React drama


Update evalPostfix.py

The code which was written before was developing some sort of wrong answers for the question. Hence I got some idea and making changes for the code.

Hi there @Devangshu1 thanks for raising the issue, but can you tell me what problem you faced / wrong answer you got with the original code, because I rechecked it just now and it's working perfectly fine.
Ps. You can share some screenshot of the problem.

Okay I'll update you with the screenshots shortly
On Thu, Oct 20, 2022, 16:32 Narayan soni @.***> wrote:

Hi there @Devangshu1 https://github.com/Devangshu1 thanks for raising
the issue, but can you tell me what problem you faced / wrong answer you
got with the original code, because I rechecked it just now and it's
working perfectly fine.
Ps. You can share some screenshot of the problem.
—
Reply to this email directly, view it on GitHub
https://github.com/narayan954/niet-codetantra/pull/1#issuecomment-1285334687,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2Y36IRGMMPXT7SLZLAJ7M3WEERDNANCNFSM6AAAAAARJX52NY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Acer Iconia Tab A500 Reports as Non-Mobile

This tablet shows the following output from getBrowser():
stdClass Object (
[browser_name] => Mozilla/5.0 (Linux; U; Android 3.2; en-us; A500 Build/HTJ85B) AppleWebKit/534.13 (KHTML, like Gecko) Version/4.0 Safari/534.13
[browser_name_regex] => ^mozilla/5.0 (.linux.) applewebkit/.* (khtml, like gecko) .version/4.. safari/.$
[browser_name_pattern] => Mozilla/5.0 (Linux) AppleWebKit/ (KHTML, like Gecko) Version/4. Safari/*
[Parent] => Safari 4.0
[Platform] => Linux
[Browser] => Safari
[Version] => 4.0
[MajorVer] => 4
[Win32] => 1
[Frames] => 1
[IFrames] => 1
[Tables] => 1
[Cookies] => 1
[JavaScript] => 1
[JavaApplets] => 1
[CssVersion] => 3
[MinorVer] => 0
[Alpha] =>
[Beta] =>
[Win16] =>
[Win64] =>
[BackgroundSounds] =>
[VBScript] =>
[ActiveXControls] =>
[isBanned] =>
[isMobileDevice] =>
[isSyndicationReader] =>
[Crawler] =>
[AolVersion] => 0 )

Phpbrowscap is only a class which READS the browscap.ini file provided by Gary Keith. Please refer to him for issues regarding wrong data.


fix Stackview UI when reloading

After accept, please do pod update Pai on kaodim-ios. Currently Pai is updated manually on kaodim-ios project

Codecov Report

Merging #4 into develop will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff          @@
##           develop    #4   +/-   ##
=====================================
  Coverage        0%    0%
=====================================
  Files           14    14
  Lines          559   572   +13
=====================================
- Misses         559   572   +13


docker compose up failing docker context list gets "unexpected end of JSON input

Version
Microsoft Windows [Version 10.0.22621.1194]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
Docker Desktop 4.16.3
Repro Steps
Run
docker compose build
docker endpoint for "default" not found

before docker restart
.
├── buildx
│   ├── current
│   ├── defaults
│   └── instances
├── config.json
├── contexts
│   └── meta
├── desktop
│   └── log
│       └── host
│           └── docker-desktop-user-distro.log
├── features.json -> /mnt/c/Users/bap/.docker/features.json
├── run
│   └── docker-cli-api.sock
└── scan
    └── config.json

after the docker desktop restart
.
├── buildx
│   ├── current
│   ├── defaults
│   └── instances
├── config.json
├── contexts -> /mnt/c/Users/bap/.docker/contexts
├── desktop
│   └── log
│       └── host
│           └── docker-desktop-user-distro.log
├── features.json -> /mnt/c/Users/bap/.docker/features.json
├── run
│   └── docker-cli-api.sock
└── scan
    └── config.json

with symlink to local drive; both windows and wsl2
docker context ls
unexpected end of JSON input

remove contexts folder
both windows and wsl2 show
docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT               KUBERNETES ENDPOINT                                                                ORCHESTRATOR
default *           moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock   https://bogus

meta file created by docker desktop restart
ls
~/.docker/contexts/meta/fe9c6bd7a66301f49ca9b6a70b217107cd1284598bfc254700c989b916da791e
cat meta.json
EMPTY

cc: wsl2 PM @craigloewen-msft
Expected Behavior
docker compose build
[+] Building 0.5s (6/6) FINISHED
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 31B
Actual Behavior
docker compose build
docker endpoint for "default" not found

🕹Removing the contexts folder does result in a working docker compose.
Diagnostic Logs
No response

Have you tried with simply running dockerd and without using Docker Desktop?

This is not a WSL issue. unexpected end of JSON input has been reported many times at https://github.com/docker with a very good answer by https://github.com/docker/compose/issues/9956#issuecomment-1408407992

/close at https://docs.docker.com/desktop/release-notes/

https://github.com/docker/for-win/issues/13180#issuecomment-1446797194


Only count contributors with active public items for type count

Overview
We recently updated the contributors filter dropdown to only contain
contributors that have active, public list items. In this commit we fix the
contributor type counts by applying the same filter criteria before counting.
Connects #1001
Testing Instructions

Run ./scripts/resetdb
Browse http://localhost:6543/, open the contributor types dropdown and verify that "Auditor" has a count of "[1]"
Register a new account with type "Auditor," confirm it, and log in.
Browse http://localhost:6543/, open the contributor types dropdown and verify that "Auditor" still has a count of "[1]"
Browse http://localhost:6543/contribute and upload one-bad-one-good.csv.zip
Process the list through the first 2 steps

./scripts/manage batch_process --list-id 16 --action parse
./scripts/manage batch_process --list-id 16 --action geocode

Browse http://localhost:6543/, open the contributor types dropdown and verify that "Auditor" still has a count of "[1]"
Process the list through the final step

./scripts/manage batch_process --list-id 16 --action match

Browse http://localhost:6543/, open the contributor types dropdown and verify that "Auditor" now has a count of "[2]"

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Looks good, and worked as expected

Thanks for the review.


MathLinks in list don't render in live preview

A link to a note with a MathLink placed in an ordered or unordered list will not display that note's MathLink in live preview, and instead display the original link.

Will fix!
Btw, thanks a lot for pointing out all the issues. I would've never caught them myself.


chore(storybook): adds a11y tab to stories

Related Ticket(s)
#5405
Description
This adds the Accessibility tab to all Storybook environments.

Changelog
New

Accessibility tab added to react, web components (and react wrapper), and styles package Storybooks

It looks like we have to go through and fix some of these violations that the tabs are picking up, a lot seem to be the way we created the stories and not in the components themselves.

@jeffchew For sure, a few things we need to fix.


ksonnet.io release link

i want to send a pr for ksonnet.io (the site), but couldn't immediately find the appropriate repository. so i'm filing this here - forgive me.
https://ksonnet.io/get-started/ contains "Download a prebuilt binary" that points to "https://github.com/ksonnet/releases" instead of "https://github.com/ksonnet/ksonnet/releases"

Thanks for the catch! This should be updated now


use set display name for naming the export file

fixes #3810
Ensure we set the subject set display name as part of the file export name via the the content-disposition header for per subject set classification exports.
This PR adds the SubjectSet resource to the lookup types for setting the content disposition and in turn ensures the value is set on the uploaded object store resource to be used when downloading.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

One Q: I’m assuming that display names are sanitized (like project names are?) so that they will produce valid export file names. Is that a safe assumption?

It should be as it uses paramterize method https://apidock.com/rails/ActiveSupport/Inflector/parameterize
Also it's the same as we do for the workflow exports and we've had no complaints on those.

Are there any limits on subject set names? Here's one I've set up from a British Library catalogue file, with the name: Glass Plate Negative Collection: documentary photographs of Siberian indigenous peoples and cultures [Late 19th to Early 20th Century]

Are there any limits on subject set names?

there is a hard limit and it is very large.... that name should be fine, this is what the filename would look like as an export
glass-plate-negative-collection-documentary-photographs-of-siberian-indigenous-peoples-and-cultures-late-19th-to-early-20th-century-classifications.csv
> t
 => "Glass Plate Negative Collection: documentary photographs of Siberian indigenous peoples and cultures [Late 19th to Early 20th Century]"

> t.parameterize
 => "glass-plate-negative-collection-documentary-photographs-of-siberian-indigenous-peoples-and-cultures-late-19th-to-early-20th-century"


Migrate the home page from Google Docs to Netlify CMS

Overview

Based on the Website Improvements #23 discussion, we are planning to migrate our Google Docs-based CMS into a proper Headless CMS. This would provide more granular controls over the HTML structure that we're rendering on the page that allows us to style the website flexibly.
Implementation Model

Use Tina Cloud as the WYSIWYG headless CMS and store the content into Markdown files within this repository.

Current Tasks

[x] ~#37~
[x] #45
[ ] #109
[ ] #38
[ ] #62
[ ] #39

I think we need to expedite these. Unfortunately the HTML content that we pull from gdocs doesn't follow proper HTML hierarchy, as mentioned here:

https://twitter.com/ginseladipura/status/1416343727790985221

Some people also complained about too many texts in the homepage.

https://twitter.com/deus_xmchn/status/1416291634216673280

Agreed. Once we finished with #87, this should be our top priority. 💪

A quick fix for the time being is to utilise @tailwindcss/typography:
https://tailwindcss-typography.netlify.app/

Got it, thanks! Issue created at #109.

So the page under Netlify CMS is on:

https://www.wargabantuwarga.com/home-page

And the current version is on:

https://www.wargabantuwarga.com/

@mazipan Yes, agree. I think before we fully swap the home page to the Netlify CMS version, we should split the homepage contents first, so we could easily break up each section of the homepage like the planned design on the Figma.
cc: @zainfathoni

From the potential changes based on Figma design, do you have any suggestions on how we should split the sections into @resir014?

@zainfathoni I already have some mapping in my head right now:

Welcome Message (single page, rendered on dialog)
Cara Berkontribusi (single page)
Informasi Terbaru (multiple posts)

Stuff that's on a separate page

Kontak darurat (multiple items)
Tentang Kami (single page? multiple items?)
Edukasi (multiple items + sub-items)
Telemedicine (single page w/ metadata)

Stuff that I'm not certain how to split up yet, or if we should make the content for it:

Donasi Warga (are we pulling from another API? if not, we can create a section on Netlify CMS which aggregates those links)
Isolasi Mandiri (not sure where to put this?)

For now, we can flip the switch so that the Netlify CMS page becomes the actual homepage. Then we can slowly break away things and create some kind of a "Home Page 2.0" page with all the stuff that's already broken down into sections.

Yes, that's my initial idea.
Wanna have a call tonight @resir014? We can flip the switch together while discussing about the migration to v2.0

@zainfathoni I'm available but only before 20:30. Maybe let's try earlier?

Sure! I just announced it over here:
https://twitter.com/zainfathoni/status/1418138662223552517?s=20


Help.. Failed to process package 'matlab_ros_bridge':

Hi Giovanni and Ricardo,
I have tried setting the matlab_ros_bridge, with the corresponding indications. When compiling an error. Attach Images and compilation instruction.
catkin_make_isolated --cmake-args -DBOOST_ROOT=/home/john/boost_1_49_0_gcc_4_7 -DBoost_NO_SYSTEM_PATHS=ON -DCMAKE_C_COMPILER=/usr/bin/gcc-4.7 -DCMAKE_CXX_COMPILER=/usr/bin/g++-4.7 -DCMAKE_CXX_FLAGS=-U_GNU_SOURCE -DMATLAB_DIR=/home/john/matlab2014a/R2014a

Att,
John J.

Hello John,
I am kind of having the same error as yours. Did you manage to solve the issue?
Thanks,
Firas

Hi John, could you be a bit more precise about your platform?
I need to know :

OS Version

ROS Version. You need to give me the output of the command:
rosversion -d

Matlab Version you are using

gcc version installed on your computer. To do that you could open a new terminal and tell me the output of the command:
cd /usr/bin && ls | grep -i "g++-"
and of the command:
cd /usr/bin && ls | grep -i "gcc-"

After you should check which version of boost you are using (I think the 1_49 from your commands)

I wait for your reply to try to help you.
Fabrizio.

Hi,
I think I have the same problem. Could you please help me what to do?
After I ran the following command:
catkin_make_isolated --cmake-args -DBOOST_ROOT=/home/mahsa/ROSMATLAB/boost_1_49_0_gcc_4_7 -DBoost_NO_SYSTEM_PATHS=ON -DCMAKE_C_COMPILER=/usr/bin/gcc-4.8 -DCMAKE_CXX_COMPILER=/usr/bin/g++-4.8 -DMATLAB_DIR=/usr/local/MATLAB/R2014a
I got the following error:

I am running on:
Ubuntu 14.04 - 64bit
ROS version: indigo
MATLAB version: 2014a
gcc version: 4.8
g++ version: 4.8

Hello Masha,
In my case, the problem was that I didn't configure MATLAB (didn't do the "mex -setup" command).
I believe your error is different. The bridge is working fine for me and I didn't face this error. It looks weird. Have you used the pre-compiled boost or have you compiled it yourself?

Hello FirasAbiFarraj ,
Thanks for answering.
I used compiled boost download (https://github.com/lagadic/matlab_ros_bridge/releases/download/v0.1/boost_1_49_0_gcc_4_7.tar.bz2)
and used it in catkin_make_isolated.
Do I need to compile it on my own?

I used the compiled boost. But it is compiled with gcc/g++ 4.7 while yours is 4.8. Could be an issue..
Try to either change your gcc/g++ compiler or compile boost yourself.
The procedure is very tricky. You have to literally stick to every command.

Hello,
I have installed matlab_ros_bridge on  system with Ubuntu 16.04, ROS kinetic and Matlab 2016b, but I do not find the file 'setup.m' in matlab_ros_bridge. Can you please tell me what am I doing wrong or if I miss something... I can open the test.slx but when I run it I have the following errors and I do not find the ROS file that I should launch to create the topic '/Vector3_', can you help me with this (I am new in ROS)
Error in S-function 'test/Publish Vector3Stamped': S-Function 'rmsg_pub_Vector3Stamped' does not exist
Component:Simulink | Category:Modelerror
Error in S-function 'test/Real time synchronisation': S-Function 'rtblock' does not exist
Component:Simulink | Category:Modelerror
Error in S-function 'test/Subscribe Vector3Stamped': S-Function 'rmsg_sub_Vector3Stamped' does not exist
Many thanks,
Cosmin

@ccopot I have the same problem as you. Did you get a solution?
It took much time to follow, but nowadays no one maintains this project!

Yesterday I accepted a PR with some updates in README.md. Not sure it this new version can help.
Anyway this project was designed before Matworks made available a stable ROS bridge. It is now deprecated and no more maintained. You should rather use the official ROS bridge.

@robopassio In the end I didn't use this PR. I used the official ROS bridge from Matworks as @fspindle mention.


No progress with model.predict_all_image() when running demo on single video

When running the demo on a single video with the command (from README):
python -m demo_video --vid_path demo_data/penn_action-2278.mp4 --load_path models/hmmr_model.ckpt-1119816
the process seems to halt and the progress remains at 0%.
Any ideas on what is going wrong?

If you have anything else running on the same GPU, you may be running out of memory. Difficult to debug without seeing which operations are taking up most of the time

That sounds like what is most likely happening.
How could I go about solving this?
Is there somewhere in the code I can edit to lower memory consumption?

You can lower batch size (--batch_size 1) or reduce sequence length (--sequence_length 15). You can use nvidia-smi to check how much gpu memory you're using

Increasing the memory in my system solved this.
Thanks for the suggestions!


Update docs in preparation for Matrix Public Archive being generally available

Update docs in preparation for Matrix Public Archive being generally available
Dev notes
App screenshot: .../!OvgDmYaPOFRRWnIdQe:half-shot.uk/date/2021/08/06 at 90% zoom with even dimensions for better scaling
Previous PR where we added the screenshot: https://github.com/matrix-org/matrix-public-archive/pull/42

Thanks for the review @pdurbin 🐮