text:
Formatting Input to ONNX Sklearn converter

Hello :) I'm working on embedding a trained RandomForest model into a simulation so i can see how the results of the model influence behavior. I just found the ONNX Helper and so far so awesome. I was hoping for some help in figuring out how to prepare inputs in the simulation model for ONNX. I'm using the sk_learn converter and it expects output in a format that looks like this: initial_type = [('input', FloatTensorType([None, 4]))]. I have tried passing the input from the model as a simple array [4], HashMap (String, int[4]) and Pair (String, int[4]). The first one (simple array) fails and I get an error stating: Object at index 0 (shape 4) failed to match expected size (input 'X', shape *,4). The last two also fail and I get a NullPointerException. When I trace, it's failing at onnx_wrapper.OnnxHelper.findArrayDims. Any help is appreciated, thank you!
Below is my AnyLogic Attempt
int[] input0 = new int[]{1, 2, 4, 1}; //Map<String, int[]> inputs = new HashMap<>(); //inputs.put("X", input0); Pair<String, int[]> inputs = new Pair("X", input0); traceln(inputs); //output = onnxHelper.predict(inputs); int[] output = onnxHelper.predict(int[].class, input0); traceln(output);
Here's my ONNX model:
initial_type = [('float_input', FloatTensorType([None, 4]))] onx = convert_sklearn(clf, initial_types=initial_type) with open("rf_test.onnx", "wb") as f:     f.write(onx.SerializeToString())

Hi! Your [None,4] input shape (referred to as *,4 in the helper) indicates the first dimension is variable sized. If you're only passing one value, then just wrap it in another array (e.g., new int[][]{{1,2,4,1}}). If you're still running into issues, uploading it here would be helpful, if it's not anything confidential.
Also, if the tensor is a float type, you should use float instead of int (but you can double check what it expects by looking clicking the helper during runtime to see the inspection window).

Thank you so much for responding! I should have thought of wrapping the array! That resolved the shape problem but I'm having data type issues despite aligning all data types. ONNX doesn't support Int32 so i just changed everything to float but now I'm getting errors stating that there are mismatches with the input as double? I've attached my testing model (my actual model is different but the way it works is the same). Thanks again for helping :)
Sales Funnel_Test.zip

Glad to help! And thank you for attaching the test model, it was helpful to see the full context.

there are mismatches with the input as double

If you check the inspection window during runtime, you'll see the input needs to be a double.

I confirmed this information is the same as in Python (i.e., not a bug with the helper) by printing out onx.graph.input and onx.graph.output. So it seems it's an issue with how skl2onnx converts the classifier to an ONNX file.
Though, regarding parsing the output, there is an issue with the helper in that it assumes you requesting a single output means there's only one output in the model (which doesn't work in this case, as there's two outputs). I'll look into adding type detection to the helper 🙂
In short, with the current ONNX file, you need to make two changes to your AL code:

Change the input type to double
Use the single-argument form of predict (returns a map) and get the labels by querying the input name

i.e.,
double[][] input0 = new double[][]{{1,2,4,1}};

// To get labels and probabilities:
//Map<String,Object> outputs = onnxHelper.predict(input0);
//long[] labels = (long[]) outputs.get("output_label");
//List<Map<Long,Double>> probs = (List) output.get("output_probability");

// To just get labels:
long[] labels= (long[])onnxHelper.predict(input0).get("output_label");
traceln(labels[0]);

BTW, ONNX does seem to support int32, as per their spec doc.

Thank you so much Tyler!!! Worked like a charm after applying to my main model. I really appreciate the help and I appreciate ONNX Helper. I'm excited to run experiments now.

authors: idiasuley shirtandtieler

repo: t-wolfeadam/AnyLogic-ONNX-Helper


text:
mistyped paths in some demos

The following links are mistyped (missing 'http:')
<link rel="stylesheet" href="//code.jquery.com/ui/1.11.2/themes/cupertino/jquery-ui.css">
<script src="//code.jquery.com/jquery-1.10.2.js"></script>
<script src="//code.jquery.com/ui/1.11.2/jquery-ui.js"></script>

in the custom-grid-field, data-manipulation and rows-reordering demos

No, it's valid url http://stackoverflow.com/questions/8951423/html-links-without-http-protocol

OK.....I won't work when viewing it locally (which is what I was doing).
From that SO link:
If a web page is saved on a local disk and then opened from there, it has no protocol (just the file: pseudo-protocol), so URLs like //www.example.com won’t work; so here’s one reason for including the “http:” or “https:” part.

Agree, it makes sense.

source: gharchive/issue

authors: jmoreau-enquizit tabalinas

repo: tabalinas/jsgrid

license: mit

license_type: permissive

license_source: bigquery


text:
[FEATURE]: Permission for showing player distance/mode of travel

Scope
In-Game Menu
Feature Description
The ability to enable/disable seeing player distances/mode of travel within the player card via permissions on the in game txAdmin menu.
Use Case
In roleplay servers seeing the distance to players is a huge power advantage and being able to disable this "un-loggable" action for those that shouldn't have it would be great.
Proposed Solution
No response
Additional Info
No response

No way I'm implementing this.
People basically have asked for every single feature of txAdmin to be disabled due to server owners not trusting their own staff.
This doesn't make any sense for me.
If anything, what you guys want is a way to do /onduty and /offduty, and that MAYBE will come some day to txAdmin... but not today

authors: solareon tabarra

repo: tabarra/txAdmin

license: MIT

license_source: github-api


text:
Add support for skip-connection-check-flag in workbooks.publish()

There is a way to set the flag skip-connection-check-flag in the  "Publish Workbook" requests of workbooks.publish()?
https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref.htm#publish_workbook
Rationale:
I'm automating the deploy of the same reports in several environment where the original data source used for the Tableau developers it isn't available, and I can't figure out another way to change server_address in workbooks before publishing.

Thanks for reporting this - I'll mark as an enhancement so we can look into adding that flag.

Available in v0.15.0.

authors: bcantoni gmiretti shinchris

repo: tableau/server-client-python


text:
Add gray background theme option.

In lieu of a dark theme, add an option to show log view and value dialog
in gray background to reduce contrast.
For simplicity, the UI option is a single check box; but for future
flexibility, the option is saved as a color string instead of a Boolean
value in the settings file.
If desired, we can allow setting different color in the UI later. The
code also recognized if the color is “hacked” in the settings file and
avoid overwriting it.

I have support for theme (light and dark) in the "themes" branch, it is basically ready to go. These themes affect all of TLV (all controls, styles, color palette). Take a look, perhaps we can add an additional grey theme (?)
The commit for "Remember list of last monitored log folders." Should probably go in its own branch.

Cool. I'll leave this request open and wait for the final theme pull request. One thing I noticed - the dark theme does not work well with existing highlight colors, as they all expects black/dark font colors. That's one reason I went with gray theme first.
The "remember last log folders" feature is already in dev branch. I think it shows up here because I created the new branch before that feature got merged to dev.

I noticed the highlight filters thing before. The "themes" branch actually has some logic to be smart about font color. If the highlight color is dark, the font will be white, if the highlight color is light, the font should be black; trying to optimize contrast between font and highlight color.
However, I think that some highlight colors will just not work on the dark themes (just like some colors will just not work on light themes).

source: gharchive/pull-request

authors: luiseeo terencesoh

repo: tableau/tableau-log-viewer


text:
Breakpoint Generator (CLI support)

Hey,
To solve the problem of creating new breakpoints and update them along the project. I try to create the most unobtrusive breakpoint generator. I love the simplicity and the independence of each tachyons step. So I try to respect that:

The generator is outside of CSS files, is optionally available in the tachyons-cli
you can parse a single file or an entire directory (works for the modules or the entire build)
The CLI extract the @customMedias from the file. You can use with _variables.css, _media-queries or the module css file
Per default, the code don't overwrite media queries already on file, so if you modify _typography.css and forget some breakpoint, the code will maintain your code and add the new media query.
The build by tachyons-css remain. Everything happens pre-build.

How works
I wrote a generic postcss plugin called postcss-update-media-queries a specific wrap module tachyons-build-mediaquerie to help the tachyons-cli functions.
Usage
$ tachyons /src --customMedia --variables=src/_variables.css --overwrite=false

input
/*Variable.css*/
@custom-media --breakpoint-not-small screen and (min-width: 30em);

.underline { text-decoration: underline; }
.strike { text-decoration: line-through; }

output
.underline { text-decoration: underline; }
.strike { text-decoration: line-through; }
@media (--breakpoint-not-small) {
 .underline-ns { text-decoration: underline; }
 .strike-ns { text-decoration: line-through; }
}

Look at tachyons-bulild-mediaqueries to see more.
Future thoughts
Has a lot of things to improve like error messages, return promises (to have a better control), ES6 standard, decent tests, naming...
But taking a look and see if is useful for the major project.
P.S: @johnotander I read a lot of your code to have insights to do that. Thanks :)

@zehfernandes 100% absolutely love this. I've only just had a quick glance at the code and the concept, but this is exactly what we'd like to incorporate into the project (via options of course). We've come across use cases to not only change media queries, but to add them as well. If a project wants to have 4, 5, or even more breakpoints we would love to provide an official mechanism. Tachyons should be able to target watches and televisions, too 😎 .
This will especially fit in nicely for some future Tachyons projects we're working on:

https://github.com/johnotander/tachyons-generator
https://github.com/johnotander/tachyons-generator-app

It will be a day or two before I can give a thorough review and start the process of adding this to the next version of the cli. But, I wanted to let you know that I love where this is headed and that you can expect a more formal response with review in the next 24 to 72 hours.
Thanks! 🍻 💯

OHH! This JSON config file is amazing. 😍

Update:
The output code of tachyons --customMedia contains whitespace in variable name
.pa0 { padding: var( --spacing-none ); } /* quebra */

The plugin postcss-css-variable(https://github.com/MadLittleMods/postcss-css-variables) has an issue https://github.com/MadLittleMods/postcss-css-variables/issues/27 about the CSS4 spec considering --spacing : different from --spacing:
Fixed using Perfectionist compressed option to remove whitespaces.

authors: johnotander zehfernandes

repo: tachyons-css/tachyons-cli

license: isc


text:
Empty comment lines result in the whole file not being parsed

Config::INI return Nil for this:
;
foo=bar

However, if there is a space character after ;, then everything is alright.

PR merged, so it's fixed now. Thanks!

authors: AlexDaniel tadzik


text:
FreeBSD build failed with libc 0.2.138

The last successful build used libc 0.2.137 and all failed build used libc 0.2.138, so probably related to the 0.2.137 -> 0.2.138 update.
https://github.com/taiki-e/cargo-hack/actions/runs/3608985912/jobs/6081906097
error: linking with `x86_64-unknown-freebsd12-gcc` failed: exit status: 1
  |
  = note: "x86_64-unknown-freebsd12-gcc" "-m64" "/tmp/rustcVB3IQA/symbols.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.0.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.1.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.10.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.11.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.12.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.13.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.14.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.15.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.2.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.3.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.4.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.5.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.6.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.7.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.8.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.cargo_hack.2318d226-cgu.9.rcgu.o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547.591caykrjgsvxhd7.rcgu.o" "-Wl,--as-needed" "-L" "/target/x86_64-unknown-freebsd/debug/deps" "-L" "/target/debug/deps" "-L" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib" "-Wl,-Bstatic" "/target/x86_64-unknown-freebsd/debug/deps/libctrlc-51998d80f6a72864.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libnix-18ba575260dfad93.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libcfg_if-e38878cf087dac5d.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libtoml_edit-28f6cb71c0f6d966.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libitertools-320cf178378eeeaa.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libeither-e7df64a0ed6ac327.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libcombine-23c1f11c3a9ef338.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libmemchr-641fb448d4e1589d.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libbytes-796123aa541d7ea8.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libtoml_datetime-6007df2bfa888181.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libserde_json-25fa7d12aeda0b06.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libryu-c251820d1f9b81c8.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libitoa-88f22cbe8ae56cdb.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libserde-a8313a979998b903.rlib" "/target/x86_64-unknown-freebsd/debug/deps/liblexopt-63123080e1641219.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libindexmap-121d5ed938e48639.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libhashbrown-69ed5b1ddb63db22.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libis_terminal-9dff342a08150e31.rlib" "/target/x86_64-unknown-freebsd/debug/deps/librustix-64848a51b177c873.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libbitflags-2c68063a742fe5a4.rlib" "/target/x86_64-unknown-freebsd/debug/deps/liberrno-3eefe7e4872ad9b4.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libio_lifetimes-f695832c596a10ea.rlib" "/target/x86_64-unknown-freebsd/debug/deps/liblibc-c37ea1fde818e47a.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libtermcolor-b92f43711680adb6.rlib" "/target/x86_64-unknown-freebsd/debug/deps/libanyhow-e4d331e2c107587b.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libstd-2e2ed02d69a9f376.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libpanic_unwind-9833c7b1a3ab3ba0.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libobject-a4819315bc8bd434.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libmemchr-3b3c29eb743e21fd.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libaddr2line-6855750abe51f6eb.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libgimli-3f49948781a939b7.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/librustc_demangle-da6d4cb1cee27a7c.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libstd_detect-858666892f335d6e.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libhashbrown-1ad997d3d3a267f6.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libminiz_oxide-2ccf2aa4712c236f.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libadler-418d538a05b92d78.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/librustc_std_workspace_alloc-cf5c5dee4dc6005a.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libunwind-71480e653c0efa74.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libcfg_if-bef4f98576d91896.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/liblibc-daed9adcdb4f1c5c.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/liballoc-c461ba80f2ae5f7b.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/librustc_std_workspace_core-0f3d942f27fcf4a5.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libcore-b6632458290bd1a1.rlib" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib/libcompiler_builtins-b37c418607db7120.rlib" "-Wl,-Bdynamic" "-lrt" "-lutil" "-lexecinfo" "-lkvm" "-lmemstat" "-lkvm" "-lutil" "-lprocstat" "-lrt" "-ldevstat" "-lexecinfo" "-lpthread" "-lgcc_s" "-lc" "-lm" "-lrt" "-lpthread" "-lrt" "-lutil" "-lexecinfo" "-lkvm" "-lutil" "-lprocstat" "-lrt" "-ldevstat" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/rust/lib/rustlib/x86_64-unknown-freebsd/lib" "-o" "/target/x86_64-unknown-freebsd/debug/deps/cargo_hack-fc9c6c512f63e547" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro,-znow" "-nodefaultlibs"
  = note: /usr/local/lib/gcc/x86_64-unknown-freebsd12/6.4.0/../../../../x86_64-unknown-freebsd12/bin/ld: cannot find -lmemstat
          collect2: error: ld returned 1 exit status

x86_64-unknown-freebsd12/bin/ld: cannot find -lmemstat

Probably related: https://github.com/rust-lang/libc/pull/2998

Filed https://github.com/rust-lang/libc/issues/3025 and pinned libc to 0.2.137 for now (a0482fa232897c079c0e345e327ea03bc46a1f6d).

repo: taiki-e/cargo-hack


text:
sqlite: call initTx from BeginTx for write transactions

This makes BeginTx call BEGIN IMMEDIATE immediately for write
transactions, and prevents stale txs.
Signed-off-by: Maisem Ali maisem@tailscale.com

FWIW I think we can rip out this optimization.

Done, PTAL.

repo: tailscale/sqlite


text:
Export meta

added named exports as an array to meta. Exported existing functions getMetaJson and getMetaJsonString

Once done, we should also add a test for this new public function

authors: LeelandClenista tajo

repo: tajo/ladle


text:
SkyLightProbe produces NaN texels under certain conditions

Related to https://github.com/takram-design-engineering/three-geospatial/issues/7

Confirmed that some vertices of Google Photographic 3D Tiles have normals as zero vectors. I'd rather say this is a bug in TileCreasedNormalsPlugin, or normals aren’t natively supported by Google Photographic 3D Tiles. Keeping this issue open for the record.

This is odd... I wrote the toCreasedNormals function so I'll take a look later. The only reason I can imagine this happening is if we have a degenerate triangle with all vertices at a single point - but in that case we shouldn't see the triangle rasterized to the screen.
From https://github.com/takram-design-engineering/three-geospatial/commit/2b93b01be25cd8ad9f4079a0d48f7e019ed56f8b - do you know how are NaNs making it into that shader? Is it downsampling normals? Or are NaN values making it into the color buffer due to a 0,0,0 normals?

That shader takes the color buffer from the render pass, and NaN values are in the color buffer. I suspect the source is here, which invokes this.

but in that case we shouldn't see the triangle rasterized to the screen

That’s true, now that you mention it…

"Fixing up" these degenerate normals seems to fix the issue:
for ( let i = 0, l = normal.count; i < l; i += 3 ) {

  v0.fromBufferAttribute( normal, i + 0 );
  v1.fromBufferAttribute( normal, i + 1 );
  v2.fromBufferAttribute( normal, i + 2 );
  if ( v0.length() < 0.5 || v1.length() < 0.5 || v2.length() < 0.5 ) {

    normal.setXYZ( i + 0, 0, 0, 1 );
    normal.setXYZ( i + 1, 0, 0, 1 );
    normal.setXYZ( i + 2, 0, 0, 1 );

  }

}

I took a look and it looks like 0, 0, 0 normals are only generated on triangles with an area of 0. Though the triangles are degenerate lines - ie two vertices are in an identical location and the third is offset. I'd think this would result in no pixels being rasterized but this doesn't seem to be the case - though there may be something else going on? computeVertexNormals results in the same issue while setting material.flatShading does not.

An image of 0, 0, 0 normals being rasterized, highlighted in red by modifying a normal material 🤷 :

Fixed in https://github.com/takram-design-engineering/three-geospatial/commit/7fd13501de0df68c4591e6a8aa0f5282852b1cbf

authors: gkjohnson shotamatsuda


text:
Python encountered SyntaxError('invalid syntax', ('/opt/Autodesk/shared/python/FlamePy/sg_batchgroup_from_plates.py', 19, 8, 'print ""\n')) in unknown code

Hi there !
Getting some errors after 472 frames calculated :
flame202231_flame6_app.log
flame202231_flame6_shell.log
Can you point us in the right direction ?
Many thanks for your help :)

the error seems related to the hook mentioned (/opt/Autodesk/shared/python/FlamePy/sg_batchgroup_from_plates.py)
the print statement is for python2, you probably need to add () ===>  print(""\n)

authors: avassor xenjee

repo: talosh/flameTimewarpML


text:
iOS Weekly Report with 3.7 million devices

Describe the bug
We got the weekly report with over 3.7 million devices. This can't be our app. Maybe an other app or even all devices you have.
To Reproduce
regenerate the report for iOS.
Expected behavior
Only get the weekly report data for our app.
Screenshots
Can give you the report on request. Won't put the data here publicly.
Please complete the following information:

Device: PDF weekly report
OS version: PDF weekly report
Version of freeRASP: PDF weekly report

Additional context
None.

Hello @ikosta ,
that's quite strange. Could you please send us the reports at support@talsec.app along with your watcherMail and packageName/bundleId? Thank you!
Kind regards,
Talsec team

Hello,
the issue has been fixed. Thank you for reporting it!
Kind regards,
Talsec team

authors: ikosta msikyna

repo: talsec/Free-RASP-Community


text:
Sheet crashes when default position set to one of snap points in percentage mode.

Current Behavior
When I set default state of position to 15. App crashes and gives this trace:
ERROR  Your app just crashed. See the error below.
com.facebook.react.bridge.NoSuchKeyException: toValue
  com.facebook.react.bridge.ReadableNativeMap.getValue(ReadableNativeMap.java:113)
  com.facebook.react.bridge.ReadableNativeMap.getValue(ReadableNativeMap.java:117)
  com.facebook.react.bridge.ReadableNativeMap.getDouble(ReadableNativeMap.java:154)
  com.facebook.react.animated.SpringAnimation.resetConfig(SpringAnimation.java:64)
  com.facebook.react.animated.SpringAnimation.<init>(SpringAnimation.java:55)
  com.facebook.react.animated.NativeAnimatedNodesManager.startAnimatingNode(NativeAnimatedNodesManager.java:279)
  com.facebook.react.animated.NativeAnimatedModule$14.execute(NativeAnimatedModule.java:730)
  com.facebook.react.animated.NativeAnimatedModule$ConcurrentOperationQueue.executeBatch(NativeAnimatedModule.java:171)
  com.facebook.react.animated.NativeAnimatedModule$3.execute(NativeAnimatedModule.java:365)
  com.facebook.react.uimanager.UIViewOperationQueue$UIBlockOperation.execute(UIViewOperationQueue.java:579)
  com.facebook.react.uimanager.UIViewOperationQueue$1.run(UIViewOperationQueue.java:926)
  com.facebook.react.uimanager.UIViewOperationQueue.flushPendingBatches(UIViewOperationQueue.java:1037)
  com.facebook.react.uimanager.UIViewOperationQueue.-$$Nest$mflushPendingBatches(Unknown Source:0)
  com.facebook.react.uimanager.UIViewOperationQueue$2.runGuarded(UIViewOperationQueue.java:995)
  com.facebook.react.bridge.GuardedRunnable.run(GuardedRunnable.java:29)
  android.os.Handler.handleCallback(Handler.java:958)
  android.os.Handler.dispatchMessage(Handler.java:99)
  android.os.Looper.loopOnce(Looper.java:205)
  android.os.Looper.loop(Looper.java:294)
  android.app.ActivityThread.main(ActivityThread.java:8177)
  java.lang.reflect.Method.invoke(Native Method)
  com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
  com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)

Issue is not about spring. Gives similar error on direct animation too.
Expected Behavior
Gives no error and open sheet from position 15 as default.
Tamagui Version
1.90.15

Platform (Web, iOS, Android)
Only tested on Android

Didn't tested on IOS, could be.

Reproduction
import { useState } from "react";
import { Input, Sheet } from "tamagui";

export default function MapSheet() {
  const [position, setPosition] = useState(15);

  const snapPoints = [85, 50, 15];

  return (
    <>
      <Sheet
        forceRemoveScrollEnabled={false}
        modal={false}
        open={true}
        snapPoints={snapPoints}
        // defaultPosition={15}
        snapPointsMode={"percent"}
        dismissOnSnapToBottom={false}
        position={position}
        onPositionChange={setPosition}
        zIndex={100_000}
        animation={"quick"}
        animationConfig={{
          type: "spring",
        }}
      >
        <Sheet.Handle />
        <Sheet.Frame padding="$4">
          <Input width={200} />
        </Sheet.Frame>
      </Sheet>
    </>
  );
}

### System Info

```markdown
System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700HX
    Memory: 9.58 GB / 31.70 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.4.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (122.0.2365.59)
    Internet Explorer: 11.0.22621.1

I suspect that I'm seeing a similar issue, but on Web
In particular, when snapPoints here seems to be undefined, causing the crash on Web https://github.com/tamagui/tamagui/blob/master/packages/sheet/src/useSheetOffscreenSize.tsx#L30
Tracing it back, it appears that context here is {} https://github.com/tamagui/tamagui/blob/master/packages/sheet/src/createSheet.tsx#L147
That leads me to believe that SheetProvider isn't set anywhere, as it is related to useSheetContext: https://github.com/tamagui/tamagui/blob/master/packages/sheet/src/SheetContext.tsx#L8
I couldn't find any references to SheetProvider within createSheet, only within SheetImplementationCustom
My code is essentially the same as the Dialog docs, except I don't Adapt only for touch. Thus, when I open a Dialog, my app crashes when it goes into the small media query. I believe you can replicate it with the following taken from the Dialog docs and removing the touch adapt:
import { X } from '@tamagui/lucide-icons'
import {
  Adapt,
  Button,
  Dialog,
  Fieldset,
  Input,
  Label,
  Paragraph,
  Sheet,
  TooltipSimple,
  Unspaced,
  XStack,
} from 'tamagui'

import { SelectDemoItem } from './SelectDemo'

export function DialogDemo() {
  return <DialogInstance />
}

function DialogInstance() {
  return (
    <Dialog modal>
      <Dialog.Trigger asChild>
        <Button>Show Dialog</Button>
      </Dialog.Trigger>

      <Adapt when="sm">
        <Sheet animation="medium" zIndex={200000} modal dismissOnSnapToBottom>
          <Sheet.Frame padding="$4" gap="$4">
            <Adapt.Contents />
          </Sheet.Frame>
          <Sheet.Overlay
            animation="lazy"
            enterStyle={{ opacity: 0 }}
            exitStyle={{ opacity: 0 }}
          />
        </Sheet>
      </Adapt>

      <Dialog.Portal>
        <Dialog.Overlay
          key="overlay"
          animation="slow"
          opacity={0.5}
          enterStyle={{ opacity: 0 }}
          exitStyle={{ opacity: 0 }}
        />

        <Dialog.Content
          bordered
          elevate
          key="content"
          animateOnly={['transform', 'opacity']}
          animation={[
            'quicker',
            {
              opacity: {
                overshootClamping: true,
              },
            },
          ]}
          enterStyle={{ x: 0, y: -20, opacity: 0, scale: 0.9 }}
          exitStyle={{ x: 0, y: 10, opacity: 0, scale: 0.95 }}
          gap="$4"
        >
          <Dialog.Title>Edit profile</Dialog.Title>
          <Dialog.Description>
            Make changes to your profile here. Click save when you're done.
          </Dialog.Description>
          <Fieldset gap="$4" horizontal>
            <Label width={160} justifyContent="flex-end" htmlFor="name">
              Name
            </Label>
            <Input flex={1} id="name" defaultValue="Nate Wienert" />
          </Fieldset>
          <Fieldset gap="$4" horizontal>
            <Label width={160} justifyContent="flex-end" htmlFor="username">
              <TooltipSimple label="Pick your favorite" placement="bottom-start">
                <Paragraph>Food</Paragraph>
              </TooltipSimple>
            </Label>
            <SelectDemoItem />
          </Fieldset>

          <XStack alignSelf="flex-end" gap="$4">
            <DialogInstance />

            <Dialog.Close displayWhenAdapted asChild>
              <Button theme="active" aria-label="Close">
                Save changes
              </Button>
            </Dialog.Close>
          </XStack>

          <Unspaced>
            <Dialog.Close asChild>
              <Button
                position="absolute"
                top="$3"
                right="$3"
                size="$2"
                circular
                icon={X}
              />
            </Dialog.Close>
          </Unspaced>
        </Dialog.Content>
      </Dialog.Portal>
    </Dialog>
  )
}

Hope that's helpful! Let me know if I can assist further. Thanks!

@emirefek position is the index of snapPoint, so you should set it to 2 instead of 15

@tazsingh I guess it's fixed in the latest version of Tamagui, I wasn't able to re-produce it
basically removed the touch field form the Adapt and it seems ok.

I'll close this issue for now, @tazsingh if that issue still happens it's better to open a new issue for that, thanks :)

authors: TheEhsanSarshar emirefek tazsingh

repo: tamagui/tamagui


text:
Adding try/catch around date converters which can fail

I have seen examples of Roam files with date-like titles that cause the converter to fail. Two examples:
July19th,2020 (no spaces)
Another example where it looked fine, but somehow the spaces were not a space character but some other whitespace character (when I replaced split(' ') with split(/\s/) it worked). Since there is no telling what we will encounter, I propose just putting a try...catch around these two functions, and if it doesn't work, we just leave them as normal nodes.

somehow the spaces were not a space character but some other whitespace character

If written correctly, dates such as “1 June” or “June 1st” should use a non-breaking space – not a regular space. If you use a regular space you risk getting a line break in the wrong place. 🤓

@ehamberg These were titles generated automatically by Roam for its daily pages, not dates written by users :) But yes, good point :)

authors: ehamberg houshuang

repo: tanainc/tana-import-tools


text:
Tracker LK106 protocol H02 SOS option

Hello traccar team
I have 2 LK106 trackers that are working perfectly fine with traccar however this trackers have a SOS button that when is pressed for 3 seconds it sends a SMS to the admin phone number and it also sends a signal to the server. When testing this option I receive the following data string . Note: this log file is not from traccar is just the raw data received from the computer.
This is when its in normal reporting mode
13.01.2015 03:43:41.637 |-> Length: 101
13.01.2015 03:43:41.637 |-> ASCII:  *HQ,4106012030,V1,034334,A,1828.3057,N,06704.8021,W,016.20,344,130115,FFFFFBFD,310,410,51217,61252,6#
13.01.2015 03:43:41.637 |-> Hex:    2a48512c343130363031323033302c56312c3033343333342c412c313832382e333035372c4e2c30363730342e383032312c572c3031362e32302c3334342c3133303131352c46464646464246442c3331302c3431302c35313231372c36313235322c3623
13.01.2015 03:43:41.713 |-> Dez:    [42,72,81,44,52,49,48,54,48,49,50,48,51,48,44,86,49,44,48,51,52,51,51,52,44,65,44,49,56,50,56,46,51,48,53,55,44,78,44,48,54,55,48,52,46,56,48,50,49,44,87,44,48,49,54,46,50,48,44,51,52,52,44,49,51,48,49,49,53,44,70,70,70,70,70,66,70,68,44,51,49,48,44,52,49,48,44,53,49,50,49,55,44,54,49,50,53,50,44,54,35]
This is when the SOS button is  pressed
13.01.2015 03:43:42.245 |-> Length: 90
13.01.2015 03:43:42.245 |-> ASCII:  $A 0@()�pG������6)��D
$A 0@()�pG������6)��D
13.01.2015 03:43:42.245 |-> Hex:    24410601203003401213011518282990060670479706000000fbfffbffff000e0400000000013629c811ef440d24410601203003401713011518282990060670479706000000fbfffbffff000e0500000000013629c811ef440e
13.01.2015 03:43:42.320 |-> Dez:    [36,65,6,1,32,48,3,64,18,19,1,21,24,40,41,144,6,6,112,71,151,6,0,0,0,251,255,251,255,255,0,14,4,0,0,0,0,1,54,41,200,17,239,68,13,36,65,6,1,32,48,3,64,23,19,1,21,24,40,41,144,6,6,112,71,151,6,0,0,0,251,255,251,255,255,0,14,5,0,0,0,0,1,54,41,200,17,239,68,14]
Ok so I will like to  know if anyone here can point me to the right direction. How do I decode this SOS message or if any expert here could decode and tell me what info its shown when that SOS button is pressed. I hope it says info about the IMEI, date and time.
Best Regards
Joe

You can find description here:
https://dl.dropboxusercontent.com/s/6e6yrsjdc4q62nj/GPS杞﹁浇璁惧鍗忚(澶╃惔鍏ㄦ枃)瑙勭▼.doc
Unfortunately the document is in Chinese, but you can use Google Translate to get some info from it.

authors: joepr tananaev

repo: tananaev/traccar


text:
[NEW ICON] Maya , MEL

Skill Name
Maya
Why?
Maya is a widely used 3D software, used for modeling, texturing, animation, etc. It uses Python and MEL for scripting.
Reference Image

bump? It's been nearly 2 years.

authors: ltsLumina neurogamedev

repo: tandpfun/skill-icons


text:
[NEW ICON] Firebase

Skill Name
Firebase
Why?
Popular platform developed by Google for creating web and mobile apps (has things like NoSQL dbs, authentication, etc)
Reference Image
Ref

Added in 690c3f2

authors: callumisdumb tandpfun


text:
Example error

Hello:
I was trying to run the example file 'plot_go_term.py' in pycharm.  but I got an AttributeError :
Traceback (most recent call last):
File "plot_go_term.py", line 59, in
draw_children=opts.draw_children)
File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\obo_parser.py", line 594, in draw_lineage
obj = nx.from_agraph(grph) if engine == "pygraphviz" else nx.from_pydot(grph)
AttributeError: module 'networkx' has no attribute 'from_agraph'
Can anyone tell me how to fix this?
thanks

Thank you for your interest in GOATOOLS and thank you for taking your time to write to us.
Please try scripts/go_plot.py, rather than scripts/plot_go_term.py.
The script, go_plot, uses our newer code has more features, like being able to color your GO terms.
Graphviz's dot program is used in go_plot. You can check to be sure that you have Graphviz's dot program installed on your machine by doing:
$ dot -?
Usage: dot [-Vv?] [-(GNE)name=val] [-(KTlso)<val>] <dot files>
(additional options for neato)    [-x] [-n<v>]
(additional options for fdp)      [-L(gO)] [-L(nUCT)<val>]
(additional options for memtest)  [-m<v>]
(additional options for config)  [-cv]

 -V          - Print version and exit
 -v          - Enable verbose mode
 -Gname=val  - Set graph attribute 'name' to 'val'
 -Nname=val  - Set node attribute 'name' to 'val'
 -Ename=val  - Set edge attribute 'name' to 'val'
 -Tv         - Set output format to 'v'
 -Kv         - Set layout engine to 'v' (overrides default based on command name)
 -lv         - Use external library 'v'
 -ofile      - Write output to 'file'
 -O          - Automatically generate an output filename based on the input filename with a .'format' appended. (Causes all -ofile options to be ignored.)
 -P          - Internally generate a graph of the current plugins.
 -q[l]       - Set level of message suppression (=1)
 -s[v]       - Scale input by 'v' (=72)
 -y          - Invert y coordinate in output

 -n[v]       - No layout mode 'v' (=1)
 -x          - Reduce graph

 -Lg         - Don't use grid
 -LO         - Use old attractive force
 -Ln<i>      - Set number of iterations to i
 -LU<i>      - Set unscaled factor to i
 -LC<v>      - Set overlap expansion factor to v
 -LT[*]<v>   - Set temperature (temperature factor) to v

 -m          - Memory test (Observe no growth with top. Kill when done.)
 -m[v]       - Memory test - v iterations.

 -c          - Configure plugins (Writes $prefix/lib/graphviz/config
               with available plugin information.  Needs write privilege.)
 -?          - Print usage and exit

Thanks for your reply, I tried to use scripts/go_plot.py as you said, but I still can not generate the graph.
My first trial is python scripts\go_plot.py GO:0003304 -o file.png, then I get
go-basic.obo: fmt(1.2) rel(2020-06-01) 47,233 GO Terms
 GoSubDag:   2 sources in  12 GOs rcnt(True). 0 alt GO IDs
 GoSubDag: namedtuple fields: NS level depth GO alt GO_name dcnt D1 id
 GoSubDag: relationships: set()
        GO:0008150  # BP 29111 L00 D00       biological_process
#f1fbfd GO:0032502  # BP  3225 L01 D01 A     developmental process
        GO:0009653  # BP   703 L02 D02 A     anatomical structure morphogenesis
        GO:0048598  # BP   109 L03 D03 A     embryonic morphogenesis
        GO:0035239  # BP    89 L03 D03 A     tube morphogenesis
(env) E:\PHD\goatools-master>python scripts\go_plot.py GO:0003304 --outfile=<file.png>
The syntax of the command is incorrect.

(env) E:\PHD\goatools-master>python scripts\go_plot.py GO:0003304 -o file.png
go-basic.obo: fmt(1.2) rel(2020-06-01) 47,233 GO Terms
 GoSubDag:   1 sources in   7 GOs rcnt(True). 0 alt GO IDs
 GoSubDag: namedtuple fields: NS level depth GO alt GO_name dcnt D1 id
 GoSubDag: relationships: set()
        GO:0008150  # BP 29111 L00 D00       biological_process
#f1fbfd GO:0032502  # BP  3225 L01 D01 A     developmental process
        GO:0009653  # BP   703 L02 D02 A     anatomical structure morphogenesis
        GO:0048729  # BP   197 L03 D03 A     tissue morphogenesis
        GO:0002009  # BP   148 L04 D04 A     morphogenesis of an epithelium
        GO:0060571  # BP    15 L05 D05 A     morphogenesis of an epithelial fold
#ffffe4 GO:0003304  # BP     0 L06 D06 A     myocardial epithelial involution involved in heart jogging
"dot" with args ['-Tpng', 'C:\\Users\\chest\\AppData\\Local\\Temp\\tmp0h8h_cv6'] returned code: 1

stdout, stderr:
 b''
b'Format: "png" not recognized. Use one of:\r\n'

Traceback (most recent call last):
  File "scripts\go_plot.py", line 16, in <module>
    run()
  File "scripts\go_plot.py", line 12, in run
    PlotCli().cli()
  File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\cli\gosubdag_plot.py", line 172, in cli
    self.plot(godag, kws_all)
  File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\cli\gosubdag_plot.py", line 179, in plot
    objplt.plt_dag(fout_img)
  File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\gosubdag\plot\gosubdag_plot.py", line 160, in plt_dag
    self._plt_pydot(fout_img)
  File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\gosubdag\plot\gosubdag_plot.py", line 169, in _plt_pydot
    self.wr_pydot_dag(fout_img, dag)
  File "C:\ProgramData\Miniconda3\lib\site-packages\goatools\gosubdag\plot\gosubdag_plot.py", line 174, in wr_pydot_dag
    dag.write(fout_img, format=img_fmt)
  File "C:\ProgramData\Miniconda3\lib\site-packages\pydot.py", line 1817, in write
    s = self.create(prog, format, encoding=encoding)
  File "C:\ProgramData\Miniconda3\lib\site-packages\pydot.py", line 1945, in create
    assert process.returncode == 0, process.returncode
AssertionError: 1

Then I tried python scripts/go_plot.py GO:0003304 GO:0003146 -o heart_jogging_r1.png
and I get the same output.
I also tried some code in but I didn't get the same result as the graph shows.
Thanks in advance...

It looks like you are using the Windows operating system.
Try running the command from a command shell from Cygwin, which can be downloaded from: https://www.cygwin.com/,.
Cygwin gives you that Linux-like feel while running native Windows programs.
Download go-basic.obo with:
$ wget http://geneontology.org/ontology/go-basic.obo
Here is what you should see when creating the plot:
$ scripts/go_plot.py GO:0003304 -o file.png
go-basic.obo: fmt(1.2) rel(2020-06-01) 47,233 GO Terms
 GoSubDag:   1 sources in   7 GOs rcnt(True). 0 alt GO IDs
 GoSubDag: namedtuple fields: NS level depth GO alt GO_name dcnt D1 id
 GoSubDag: relationships: set([])
        GO:0008150  # BP 29111 L00 D00       biological_process
#f1fbfd GO:0032502  # BP  3225 L01 D01 A     developmental process
        GO:0009653  # BP   703 L02 D02 A     anatomical structure morphogenesis
        GO:0048729  # BP   197 L03 D03 A     tissue morphogenesis
        GO:0002009  # BP   148 L04 D04 A     morphogenesis of an epithelium
        GO:0060571  # BP    15 L05 D05 A     morphogenesis of an epithelial fold
#ffffe4 GO:0003304  # BP     0 L06 D06 A     myocardial epithelial involution involved in heart jogging
    1 usr   7 GOs  WROTE: file.png

Thanks, I made it.

repo: tanghaibao/goatools


text:
vercel部署出现Error: Command "npm run build" exited with 1

描述遇到的问题
严格按照网站上部署的打野50秒左右报错
截图

似乎是上午更新的代码有问题，稍等我检查一下

已修复 更新代码版本即可

已修复 更新代码版本即可

正常了 谢谢大佬


text:
Mbtiles rendering performance

I have a question about rendering performance from mbtiles file. I am generating mbtiles for all countries in Europe with zooms 0 - 14. I cannot create mbtiles with 0 - 15 zooms as that mbtiles will be very huge I think that approximately 4 times larger and they are already prettly large. I have also modified a tileserver code to add features from zoom level 16 to tiles with zoom level 14.
As I am testing it, tile rendering is really slow. In dense areas in cities it will take approximately 5 - 10 seconds to render a tile on Nexus 5X. I understand that there is certainly tradeoff between memory and speed. But could this rendering speed be somehow improved?
I have noticed that rendering speed does not correlate to used style - I tested it for very simple style and with Walkabout and Bubble Wrap. So I assume that it is due to quering features in tile and as that tiles are big it is taking so long to render.

First, to clarify: When you say "the time to render a tile", it sounds like you mean the time to build the tile data into a drawable object. We call this "tile build time", as opposed to "render time" which is the time it takes to draw the tile during each frame. Correct me if I've misunderstood.
A lot of factors could make tile building slower in your scenario.

Data format: MVT tile data is the fastest for Tangram ES to read, TopoJSON and GeoJSON can be substantially slower.
Data size: Tile data should optimally contain only the geometry and tags that are useful at a given zoom level. Tangram ES has to evaluate all of the data in a tile to figure out what to draw, so the less data you put in the faster it will be.
Overzooming: When zoomed beyond the max_zoom value for a data source, tiles are built covering exponentially larger screen areas, which can lead to a slower build time per tile.

From your description, I would speculate that data size is the biggest factor here. Your zoom 14 tiles probably contain a lot of data and you should find a way to trim it down, or not support detail levels beyond zoom 14.

/cc @bcamper as this overlaps with your work on on Tangram JS with the 512px tile overzooming.

@matteblair Thank you a lot for your answer. Yes, mean "tile build time" I just didn't know how you are calling this. Yes, I understand these factors I was wondering whether it is possible to modify code so that it will build tiles faster as it is now Tangram ES is hasn't reached 1.0 release yet.

Many things are possible 🙃
The first step to improving performance is measurement, so we would need to reproduce and measure the slowness that you have reported. If you can share a sample of your data we could measure the tile building and get a better idea of how we can improve performance. If you would rather not post your data somewhere public, you can send me a small sample or a link at matt@mapzen.com

@matteblair That sounds great! For benchmarking I was using Brussel mbtiles which I created using tilepacks. It contains 0 - 14 zooms with 512px MVT tiles (to my knowing it basically means that every zoom contains features for zoom + 1). But I have also modified a little bit tileserver for zoom 14 to return features for 16 zoom instead of 15. So on 14 zoom there is a lot of data and in center of Brussel which has very high data density is takes on my Nexus 5X around 5 seconds to build tile. Here is that mbtiles: https://www.dropbox.com/s/ak3a01zc9o41pbc/brussel_z14.mbtiles?dl=0 .

authors: matteblair nvkelso rwrx

repo: tangrams/tangram-es


text:
Geo-referenced images AKA Ground Overlay

This is more a feature request than a bug.
I would like to be able to draw what Google at least call Ground Overlays  onto the map.
I thought I found a way to do it by putting a raster layer with just the image in the right place in the tiles over the vector data. However outside of the few tiles I need the raster layer draw black pixels over the rest of the map.
Thanks

Hi @ac87, thanks for your feedback.
Supporting Google-style image overlays is an interesting suggestion which we will consider, though probably won't be able to add in the near term. @blair1618: if we added this, we could consider slicing the image into raster tiles on the fly, similar to what geoson-vt does, but for Raster sources (I spoke with someone at State of the Map doing this).
In the meantime, your suggestion of a bounded raster tile source makes sense. We are currently  considering the ability to apply a bounding box to any data source (vector or raster), outside which no tiles will be requested. See https://github.com/tangrams/tangram/issues/366.

Thanks for the feedback, just to be clear this is not for using huge GeoTiffs as a raster overlay (which you have to pre-slice to be able to render) but more small images such as a building floorplan.
I see it being more a mapdata object, perhaps a polygon with image source where the image stretches between the top left and bottom right points in the polygon. Having looked through the issues now, I think this is related to custom markers #763 #653, only the marker is a polygon

For any other newbie trying to do this, Tangram is more than capable already.
I am still just playing with Tangram and there is a lot to absorb in the docs. Hadn't spotted Geometry Masking
I created tiles for the zooms where I want the image to appear and used a GeoJson file to define the location to render the tiles at.
The other thing I had missed was why transparent pixels in the tile were rendering as black, the raster draw style needed to have blend added, and blend must be a parameter of a style not added to a draw block.
styles:
    raster-blended:
        base: raster
        blend: overlay

sources:
    image-overlay-rasters: { type: Raster, url: 'http://localhost:8888/{x}/{y}/{z}.overlay.png' }
    image-overlay-source:
        type: GeoJSON
        url: image_overlay.json
        rasters: [image-overlay-rasters] # attach image layer

layers:
    overlay-image:
        data: { source:  image-overlay-source }
        draw:
            raster-blended:
                order: 220

Can now see why you had mentioned bounded tile source. That would make this a perfect solution.

There is indeed a lot to absorb :)  We need to improve the learning curve for sure.
Tile bounding box is coming soon (in Tangram JS, then easy to add to ES as well)! https://github.com/tangrams/tangram/issues/366

Tangram JS has recently added a much easier way of achieving this effect: https://github.com/tangrams/tangram/pull/688
I expect that the best resolution to the need expressed in this issue is to implement this feature, as captured now in https://github.com/tangrams/tangram-es/issues/2032. To consolidate the issues, I'll close this one.

authors: ac87 bcamper matteblair


text:
Label/Sprite offsets

Give the ability to offset sprite icons and labels,

add a vertex attribute to the point style (offset in pixel applied directly in screen space)
the following options are now availble from the stylesheet:

draw:
    icons:
        # applies an offset of 13 pixels up along y-axis
        offset: [0px, 13px]
[...]
draw:
    text:
        # applies an offset of 13 pixels down along y-axis
        offset: [0px, -13px]

quick refactor on how features are stored in the text style

Can we flip the Y axis so positive offset is down? :) Since it's the default coordinate system for the browser/CSS, etc.
https://twitter.com/ID_AA_Carmack/status/633426212304646144

Oh yes, and it would also match with the native version! Let's get closer 1.0

Seems like it's still behaving as y pointing up... maybe it got double-flipped?

I just checked and it's working for me. Can you double check?

authors: bcamper karimnaaji

repo: tangrams/tangram


text:
[Snyk] Upgrade @prisma/client from 5.1.1 to 5.4.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @prisma/client from 5.1.1 to 5.4.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 370 versions ahead of your current version.
The recommended version was released a month ago, on 2023-10-09.

Release notes

Package name: @prisma/client

5.4.2 - 2023-10-09Today, we are issuing the 5.4.2 patch release.
Fix in Prisma Client

5.4.0 subquery has too many columns
One-to-Many relationship does not join on the specified field

5.4.2-dev.1 - 2023-10-09

5.4.1 - 2023-10-04Today, we are issuing the 5.4.1 patch release.
Fix in Prisma Client

Invalid ….findMany() invocation: The column j1.id does not exist in the current database.

Fix in @ prisma/adapter-planetscale

Planetscale driver: unsupported column type NULL

5.4.1-dev.2 - 2023-10-04

5.4.1-dev.1 - 2023-10-04

5.4.0 - 2023-10-04 Read more

5.4.0-integration-libsql-adapter.7 - 2023-09-25

5.4.0-integration-libsql-adapter.6 - 2023-09-25

5.4.0-integration-libsql-adapter.5 - 2023-09-21

5.4.0-integration-libsql-adapter.4 - 2023-09-20

5.4.0-integration-libsql-adapter.3 - 2023-09-20

5.4.0-integration-libsql-adapter.1 - 2023-09-19

5.4.0-integration-fix-type-leaks.9 - 2023-10-03

5.4.0-integration-fix-type-leaks.8 - 2023-10-03

5.4.0-integration-fix-type-leaks.7 - 2023-09-29

5.4.0-integration-fix-type-leaks.6 - 2023-09-29

5.4.0-integration-fix-type-leaks.5 - 2023-09-29

5.4.0-integration-fix-type-leaks.4 - 2023-09-22

5.4.0-integration-fix-type-leaks.2 - 2023-09-22

5.4.0-integration-fix-type-leaks.1 - 2023-09-21

5.4.0-integration-fix-controlled-exports.1 - 2023-09-18

5.4.0-integration-fix-client-extension-mock.16 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.15 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.14 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.13 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.12 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.11 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.10 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.9 - 2023-10-03

5.4.0-integration-fix-client-extension-mock.8 - 2023-09-29

5.4.0-integration-fix-client-extension-mock.7 - 2023-09-28

5.4.0-integration-fix-client-extension-mock.6 - 2023-09-20

5.4.0-integration-fix-client-extension-mock.5 - 2023-09-20

5.4.0-integration-fix-client-extension-mock.4 - 2023-09-20

5.4.0-integration-fix-client-extension-mock.3 - 2023-09-19

5.4.0-integration-fix-client-extension-mock.2 - 2023-09-19

5.4.0-integration-fix-client-extension-mock.1 - 2023-09-19

5.4.0-integration-fix-client-disable-env-adapter.2 - 2023-10-04

5.4.0-integration-fix-client-disable-env-adapter.1 - 2023-10-04

5.4.0-integration-feat-driver-adapters-in-client.9 - 2023-09-19

5.4.0-integration-feat-driver-adapters-in-client.8 - 2023-09-19

5.4.0-integration-feat-driver-adapters-in-client.7 - 2023-09-15

5.4.0-integration-feat-driver-adapters-in-client.6 - 2023-09-15

5.4.0-integration-feat-driver-adapters-in-client.5 - 2023-09-15

5.4.0-integration-feat-driver-adapters-in-client.4 - 2023-09-14

5.4.0-integration-feat-driver-adapters-in-client.3 - 2023-09-14

5.4.0-integration-feat-driver-adapters-in-client.2 - 2023-09-13

5.4.0-integration-feat-driver-adapters-in-client.1 - 2023-09-13

5.4.0-integration-engines-5-4-0-7-libsql-adapter-80b70c2ed99e6febf0f4a3832eaa12c73c53d083.1 - 2023-09-19

5.4.0-integration-engines-5-4-0-40-janpio-shadow-drop-with-force-134b510303ababf88da061a7d13b598a4b8f9c95.1 - 2023-09-29

5.4.0-integration-engines-5-4-0-24-libsql-adapter-8337c6b372b0f4eb2500403a7cf450885aee4cdc.1 - 2023-09-25

5.4.0-integration-engines-5-4-0-17-libsql-adapter-4bdd9f5982a2a7e03a9d18b798a260989a71bb16.1 - 2023-09-21

5.4.0-integration-engines-5-4-0-15-libsql-adapter-037ce403b001dacf99a1532070d6a18a3879bc65.1 - 2023-09-20

5.4.0-integration-dispose-tx.3 - 2023-09-27

5.4.0-integration-dispose-tx.2 - 2023-09-27

5.4.0-integration-dispose-tx.1 - 2023-09-26

5.4.0-dev.86 - 2023-10-04

5.4.0-dev.85 - 2023-10-04

5.4.0-dev.84 - 2023-10-03

5.4.0-dev.83 - 2023-10-03

5.4.0-dev.82 - 2023-10-03

5.4.0-dev.81 - 2023-10-03

5.4.0-dev.80 - 2023-10-03

5.4.0-dev.79 - 2023-10-03

5.4.0-dev.78 - 2023-10-03

5.4.0-dev.77 - 2023-10-03

5.4.0-dev.76 - 2023-10-02

5.4.0-dev.75 - 2023-10-02

5.4.0-dev.74 - 2023-10-02

5.4.0-dev.73 - 2023-09-29

5.4.0-dev.72 - 2023-09-29

5.4.0-dev.71 - 2023-09-29

5.4.0-dev.70 - 2023-09-29

5.4.0-dev.69 - 2023-09-29

5.4.0-dev.68 - 2023-09-29

5.4.0-dev.67 - 2023-09-29

5.4.0-dev.66 - 2023-09-29

5.4.0-dev.65 - 2023-09-29

5.4.0-dev.64 - 2023-09-29

5.4.0-dev.63 - 2023-09-29

5.4.0-dev.62 - 2023-09-28

5.4.0-dev.61 - 2023-09-28

5.4.0-dev.60 - 2023-09-28

5.4.0-dev.59 - 2023-09-28

5.4.0-dev.58 - 2023-09-28

5.4.0-dev.56 - 2023-09-28

5.4.0-dev.55 - 2023-09-28

5.4.0-dev.54 - 2023-09-28

5.4.0-dev.53 - 2023-09-28

5.4.0-dev.52 - 2023-09-27

5.4.0-dev.50 - 2023-09-27

5.4.0-dev.49 - 2023-09-27

5.4.0-dev.48 - 2023-09-27

5.4.0-dev.47 - 2023-09-27

5.4.0-dev.46 - 2023-09-27

5.4.0-dev.45 - 2023-09-27

5.4.0-dev.44 - 2023-09-27

5.4.0-dev.43 - 2023-09-26

5.4.0-dev.41 - 2023-09-26

5.4.0-dev.40 - 2023-09-26

5.4.0-dev.39 - 2023-09-26

5.4.0-dev.38 - 2023-09-25

5.4.0-dev.37 - 2023-09-25

5.4.0-dev.35 - 2023-09-25

5.4.0-dev.34 - 2023-09-25

5.4.0-dev.33 - 2023-09-25

5.4.0-dev.32 - 2023-09-25

5.4.0-dev.31 - 2023-09-22

5.4.0-dev.30 - 2023-09-22

5.4.0-dev.29 - 2023-09-21

5.4.0-dev.28 - 2023-09-21

5.4.0-dev.27 - 2023-09-20

5.4.0-dev.26 - 2023-09-20

5.4.0-dev.25 - 2023-09-20

5.4.0-dev.24 - 2023-09-20

5.4.0-dev.23 - 2023-09-20

5.4.0-dev.22 - 2023-09-19

5.4.0-dev.21 - 2023-09-19

5.4.0-dev.20 - 2023-09-15

5.4.0-dev.19 - 2023-09-15

5.4.0-dev.18 - 2023-09-15

5.4.0-dev.17 - 2023-09-15

5.4.0-dev.16 - 2023-09-15

5.4.0-dev.15 - 2023-09-14

5.4.0-dev.14 - 2023-09-14

5.4.0-dev.13 - 2023-09-14

5.4.0-dev.12 - 2023-09-13

5.4.0-dev.11 - 2023-09-13

5.4.0-dev.10 - 2023-09-13

5.4.0-dev.9 - 2023-09-13

5.4.0-dev.8 - 2023-09-13

5.4.0-dev.7 - 2023-09-13

5.4.0-dev.6 - 2023-09-13

5.4.0-dev.4 - 2023-09-13

5.4.0-dev.3 - 2023-09-13

5.4.0-dev.2 - 2023-09-13

5.4.0-dev.1 - 2023-09-13

5.3.1 - 2023-09-15Today, we are issuing the 5.3.1 patch release.
Fix in Prisma Client

Duplicated keys in metrics properties

5.3.1-dev.1 - 2023-09-14

5.3.0 - 2023-09-13🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!
Improvements and bug fixes
We made the following changes:
Prisma Client improvements

Validation for undefined values in arrays in Json fields
We added runtime validation for undefined values in arrays in Json fields. Prisma Client will now return an error when an array contains an undefined value. Therefore, we encourage you to add validation that either removes the value or transforms it to null if you stumble on the runtime validation:

// Query
await prisma.user.findMany({
where: {
// JSON field
preferences: [undefined, '"theme": "dark"', null, ]
}
})
// Example error message on running the query
Can not use undefined value within array. Use null or filter out undefined values

Performance improvements for models with many unique fields

This release improves Prisma Client’s memory consumption for models with many @ unique constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory.

Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
Metrics Preview feature improvements:

We updated the counters and gauge properties
We fixed the bug that caused the prisma_pool_connections_open metric to have a negative value in some cases.

Prisma Migrate improvements

Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, prisma db pull would throw an error. We resolved this, and views are now ignored.
Added the PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK environment variable that enables you to disable advisory locking.

VS Code extension improvements

Added support for rendering multi-line comments in tooltips when hovering on a block.
Improved the auto-completion for composite types in other blocks.
Added a Code Action that allows you to replace SetDefault with NoAction when using MySQL and the default/foreignKeys relation mode.

Fixes and improvements
Prisma Migrate

Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING
MongoDB views should be ignored introspecting the database
Error in Connector on MongoDB executing listIndex: "system.views"
prisma migrate deploy: MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'

Prisma Client

Remove all special cases for Data Proxy in our tests
Segmentation fault on ARM64 Linux
In the metrics feature a gauge & counter are swapped
The prisma metrics prisma_pool_connections_open has a bug where it goes negative
Prisma crashes with GraphQL queries of nested one-to-many relationship
P1017 Server has closed the connection on linux_arm64
Error: socket hang up on Linux/arm64
Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)
Prisma 5 drops undefined from Arrays when using Json fields with Postgres
Suspected memory leak in Lambda function after upgrading from 4.10.1
Error when generating - No unsupported field should reach that path

Language tools (e.g. VS Code)

Models with multi line comments only show last line in tooltip
Add VS Code quick fix / code action to replace SetDefault with NoAction when provider = "mysql" and relationMode = "foreignKeys" | default
Composite Types aren't offered as being auto-completable in other blocks

Credits
Huge thanks to @ alencardc, @ Oreilles, @ christianledgard, @ skyzh, @ alula, @ michaelpoellath, @ RobertCraigie, @ stephenwade for helping!

5.3.0-integration-fix-client-20243.1 - 2023-08-28

5.3.0-integration-feat-js-connectors-in-client.17 - 2023-09-06

5.3.0-integration-feat-js-connectors-in-client.16 - 2023-09-05

5.3.0-integration-feat-js-connectors-in-client.15 - 2023-09-05

5.3.0-integration-feat-js-connectors-in-client.14 - 2023-09-05

5.3.0-integration-feat-js-connectors-in-client.13 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.12 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.11 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.10 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.9 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.8 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.7 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.6 - 2023-09-01

5.3.0-integration-feat-js-connectors-in-client.5 - 2023-08-30

5.3.0-integration-feat-js-connectors-in-client.4 - 2023-08-30

5.3.0-integration-feat-js-connectors-in-client.3 - 2023-08-28

5.3.0-integration-feat-js-connectors-in-client.2 - 2023-08-23

5.3.0-integration-feat-js-connectors-in-client.1 - 2023-08-22

5.3.0-integration-feat-driver-adapters-in-client.4 - 2023-09-11

5.3.0-integration-feat-driver-adapters-in-client.3 - 2023-09-06

5.3.0-integration-feat-driver-adapters-in-client.2 - 2023-09-05

5.3.0-integration-feat-driver-adapters-in-client.1 - 2023-09-05

5.3.0-integration-feat-auto-edge-import.4 - 2023-09-07

5.3.0-integration-feat-auto-edge-import.3 - 2023-09-07

5.3.0-integration-feat-auto-edge-import.2 - 2023-09-07

5.3.0-integration-feat-auto-edge-import.1 - 2023-09-07

5.3.0-integration-engines-5-3-0-7-qe-remove-unsafe-log-callback-1eb2a814ca332858858b479ede3d45f80c68d293.1 - 2023-08-25

5.3.0-integration-engines-5-3-0-32-integration-json-span-4dbffec2916e7d85fd3f98b0aebe4f56916d8f25.2 - 2023-09-08

5.3.0-integration-engines-5-3-0-32-integration-json-span-4dbffec2916e7d85fd3f98b0aebe4f56916d8f25.1 - 2023-09-08

5.3.0-integration-engines-5-3-0-24-integration-arm-openssl-main-92c9273a161ecfa87c1e2b27abd570c922b184a6.2 - 2023-09-01

5.3.0-integration-engines-5-3-0-24-integration-arm-openssl-main-92c9273a161ecfa87c1e2b27abd570c922b184a6.1 - 2023-09-01

5.3.0-integration-engines-5-3-0-23-arm-openssl-86636092afd42d73241c93c2aafe60f131001f52.1 - 2023-09-01

5.3.0-integration-chore-upgrade-esm-deps.1 - 2023-08-26

5.3.0-integration-arm-openssl-5-2-0.1 - 2023-09-01

5.3.0-dev.55 - 2023-09-11

5.3.0-dev.54 - 2023-09-11

5.3.0-dev.53 - 2023-09-08

5.3.0-dev.52 - 2023-09-07

5.3.0-dev.51 - 2023-09-07

5.3.0-dev.50 - 2023-09-07

5.3.0-dev.49 - 2023-09-06

5.3.0-dev.48 - 2023-09-06

5.3.0-dev.47 - 2023-09-06

5.3.0-dev.46 - 2023-09-06

5.3.0-dev.45 - 2023-09-06

5.3.0-dev.44 - 2023-09-05

5.3.0-dev.43 - 2023-09-05

5.3.0-dev.42 - 2023-09-05

5.3.0-dev.41 - 2023-09-05

5.3.0-dev.40 - 2023-09-05

5.3.0-dev.39 - 2023-09-04

5.3.0-dev.38 - 2023-09-04

5.3.0-dev.37 - 2023-09-04

5.3.0-dev.36 - 2023-09-01

5.3.0-dev.35 - 2023-09-01

5.3.0-dev.34 - 2023-09-01

5.3.0-dev.33 - 2023-09-01

5.3.0-dev.32 - 2023-08-31

5.3.0-dev.31 - 2023-08-31

5.3.0-dev.30 - 2023-08-31

5.3.0-dev.29 - 2023-08-31

5.3.0-dev.28 - 2023-08-30

5.3.0-dev.27 - 2023-08-30

5.3.0-dev.26 - 2023-08-30

5.3.0-dev.25 - 2023-08-30

5.3.0-dev.24 - 2023-08-30

5.3.0-dev.23 - 2023-08-30

5.3.0-dev.22 - 2023-08-30

5.3.0-dev.21 - 2023-08-30

5.3.0-dev.20 - 2023-08-30

5.3.0-dev.19 - 2023-08-29

5.3.0-dev.18 - 2023-08-29

5.3.0-dev.17 - 2023-08-29

5.3.0-dev.16 - 2023-08-28

5.3.0-dev.15 - 2023-08-28

5.3.0-dev.14 - 2023-08-28

5.3.0-dev.13 - 2023-08-28

5.3.0-dev.12 - 2023-08-28

5.3.0-dev.11 - 2023-08-28

5.3.0-dev.10 - 2023-08-28

5.3.0-dev.9 - 2023-08-26

5.3.0-dev.8 - 2023-08-25

5.3.0-dev.7 - 2023-08-25

5.3.0-dev.6 - 2023-08-24

5.3.0-dev.5 - 2023-08-23

5.3.0-dev.4 - 2023-08-23

5.3.0-dev.3 - 2023-08-23

5.3.0-dev.2 - 2023-08-23

5.3.0-dev.1 - 2023-08-22

5.2.0 - 2023-08-22 Read more

5.2.0-integration-remove-binary-sql.1 - 2023-08-10

5.2.0-integration-refactor-remove-dataproxy.8 - 2023-08-16

5.2.0-integration-refactor-remove-dataproxy.7 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.6 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.5 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.4 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.3 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.2 - 2023-08-15

5.2.0-integration-refactor-remove-dataproxy.1 - 2023-08-14

5.2.0-integration-refactor-cli-remove-dataproxy-envvar.1 - 2023-08-07

5.2.0-integration-refactor-cli-remove-dataproxy-checks.1 - 2023-08-07

5.2.0-integration-ld-library-path.2 - 2023-08-02

5.2.0-integration-js-connectors-in-client.2 - 2023-08-07

5.2.0-integration-js-connectors-in-client.1 - 2023-08-07

5.2.0-integration-joel-proxy-runtime.9 - 2023-08-22

5.2.0-integration-joel-proxy-runtime.8 - 2023-08-21

5.2.0-integration-joel-proxy-runtime.7 - 2023-08-19

5.2.0-integration-joel-proxy-runtime.6 - 2023-08-19

5.2.0-integration-joel-proxy-runtime.5 - 2023-08-19

5.2.0-integration-joel-proxy-runtime.4 - 2023-08-19

5.2.0-integration-joel-proxy-runtime.3 - 2023-08-18

5.2.0-integration-joel-proxy-runtime.2 - 2023-08-16

5.2.0-integration-joel-proxy-runtime.1 - 2023-08-16

5.2.0-integration-fix-enums-browser.1 - 2023-08-01

5.2.0-integration-fix-client-class-type-assignability.1 - 2023-08-02

5.2.0-integration-feat-no-engine.5 - 2023-08-17

5.2.0-integration-feat-no-engine.4 - 2023-08-17

5.2.0-integration-feat-no-engine.3 - 2023-08-17

5.2.0-integration-feat-no-engine.2 - 2023-08-17

5.2.0-integration-feat-no-engine.1 - 2023-08-17

5.2.0-integration-feat-js-connectors-in-client.28 - 2023-08-21

5.2.0-integration-feat-js-connectors-in-client.27 - 2023-08-19

5.2.0-integration-feat-js-connectors-in-client.26 - 2023-08-19

5.2.0-integration-feat-js-connectors-in-client.25 - 2023-08-19

5.2.0-integration-feat-js-connectors-in-client.24 - 2023-08-19

5.2.0-integration-feat-js-connectors-in-client.23 - 2023-08-19

5.2.0-integration-feat-js-connectors-in-client.22 - 2023-08-18

5.2.0-integration-feat-js-connectors-in-client.21 - 2023-08-18

5.2.0-integration-feat-js-connectors-in-client.20 - 2023-08-17

5.2.0-integration-feat-js-connectors-in-client.19 - 2023-08-17

5.2.0-integration-feat-js-connectors-in-client.18 - 2023-08-17

5.2.0-integration-feat-js-connectors-in-client.17 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.16 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.15 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.14 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.13 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.12 - 2023-08-14

5.2.0-integration-feat-js-connectors-in-client.11 - 2023-08-11

5.2.0-integration-feat-js-connectors-in-client.10 - 2023-08-11

5.2.0-integration-feat-js-connectors-in-client.9 - 2023-08-10

5.2.0-integration-feat-js-connectors-in-client.8 - 2023-08-10

5.2.0-integration-feat-js-connectors-in-client.7 - 2023-08-10

5.2.0-integration-feat-js-connectors-in-client.6 - 2023-08-10

5.2.0-integration-feat-js-connectors-in-client.5 - 2023-08-07

5.2.0-integration-feat-js-connectors-in-client.3 - 2023-08-07

5.2.0-integration-feat-js-connectors-in-client.2 - 2023-08-07

5.2.0-integration-feat-js-connectors-in-client.1 - 2023-08-07

5.2.0-integration-engines-5-2-0-23-integration-js-tx-race-7068ca12a54e5f87c02bcf5881874e8a783de34b.2 - 2023-08-17

5.2.0-integration-engines-5-2-0-23-integration-js-tx-race-7068ca12a54e5f87c02bcf5881874e8a783de34b.1 - 2023-08-17

5.2.0-integration-engines-5-2-0-16-integration-obj-description-facb547327f758310fad219991fe97276679d392.2 - 2023-08-11

5.2.0-integration-engines-5-2-0-16-integration-obj-description-facb547327f758310fad219991fe97276679d392.1 - 2023-08-11

5.2.0-integration-engines-5-2-0-14-joel-basedon-vitess-docker-image-version-update-5a2d26a26c5f7f7ca0deb9908246abfafd259a65.1 - 2023-08-10

5.2.0-integration-engines-5-2-0-10-integration-mongo-relation-mode-prisma-skip-integrity-ed91a7b2497b937965f670a81b14ad3b5b2318cc.2 - 2023-08-09

5.2.0-integration-engines-5-2-0-10-integration-mongo-relation-mode-prisma-skip-integrity-ed91a7b2497b937965f670a81b14ad3b5b2318cc.1 - 2023-08-09

5.2.0-integration-deno-auto-install-client.2 - 2023-08-17

5.2.0-integration-deno-auto-install-client.1 - 2023-08-11

5.2.0-dev.75 - 2023-08-22

5.2.0-dev.74 - 2023-08-22

5.2.0-dev.73 - 2023-08-22

5.2.0-dev.72 - 2023-08-21

5.2.0-dev.71 - 2023-08-18

5.2.0-dev.70 - 2023-08-18

5.2.0-dev.69 - 2023-08-18

5.2.0-dev.68 - 2023-08-18

5.2.0-dev.67 - 2023-08-18

5.2.0-dev.66 - 2023-08-18

5.2.0-dev.65 - 2023-08-18

5.2.0-dev.64 - 2023-08-17

5.2.0-dev.63 - 2023-08-17

5.2.0-dev.62 - 2023-08-17

5.2.0-dev.61 - 2023-08-17

5.2.0-dev.60 - 2023-08-17

5.2.0-dev.59 - 2023-08-17

5.2.0-dev.58 - 2023-08-17

5.2.0-dev.57 - 2023-08-16

5.2.0-dev.56 - 2023-08-16

5.2.0-dev.55 - 2023-08-16

5.2.0-dev.54 - 2023-08-16

5.2.0-dev.53 - 2023-08-16

5.2.0-dev.52 - 2023-08-16

5.2.0-dev.51 - 2023-08-15

5.2.0-dev.50 - 2023-08-15

5.2.0-dev.49 - 2023-08-15

5.2.0-dev.48 - 2023-08-15

5.2.0-dev.47 - 2023-08-14

5.2.0-dev.46 - 2023-08-14

5.2.0-dev.44 - 2023-08-14

5.2.0-dev.43 - 2023-08-14

5.2.0-dev.42 - 2023-08-14

5.2.0-dev.41 - 2023-08-14

5.2.0-dev.40 - 2023-08-14

5.2.0-dev.39 - 2023-08-14

5.2.0-dev.38 - 2023-08-11

5.2.0-dev.37 - 2023-08-11

5.2.0-dev.36 - 2023-08-11

5.2.0-dev.35 - 2023-08-11

5.2.0-dev.34 - 2023-08-10

5.2.0-dev.33 - 2023-08-10

5.2.0-dev.32 - 2023-08-09

5.2.0-dev.31 - 2023-08-09

5.2.0-dev.30 - 2023-08-09

5.2.0-dev.29 - 2023-08-09

5.2.0-dev.28 - 2023-08-09

5.2.0-dev.27 - 2023-08-09

5.2.0-dev.26 - 2023-08-08

5.2.0-dev.25 - 2023-08-08

5.2.0-dev.24 - 2023-08-08

5.2.0-dev.23 - 2023-08-07

5.2.0-dev.22 - 2023-08-07

5.2.0-dev.21 - 2023-08-07

5.2.0-dev.20 - 2023-08-07

5.2.0-dev.19 - 2023-08-07

5.2.0-dev.18 - 2023-08-07

5.2.0-dev.17 - 2023-08-07

5.2.0-dev.16 - 2023-08-07

5.2.0-dev.15 - 2023-08-07

5.2.0-dev.14 - 2023-08-07

5.2.0-dev.13 - 2023-08-07

5.2.0-dev.12 - 2023-08-03

5.2.0-dev.11 - 2023-08-03

5.2.0-dev.10 - 2023-08-02

5.2.0-dev.9 - 2023-08-02

5.2.0-dev.8 - 2023-08-02

5.2.0-dev.7 - 2023-08-02

5.2.0-dev.6 - 2023-08-02

5.2.0-dev.5 - 2023-08-02

5.2.0-dev.4 - 2023-08-02

5.2.0-dev.3 - 2023-08-02

5.2.0-dev.2 - 2023-08-01

5.2.0-dev.1 - 2023-08-01

5.1.1 - 2023-08-03Today, we are issuing the 5.1.1 patch release.
Fixes in Prisma Client

Browser bundle: Unhandled Runtime Error when upgrading to 5.1.0 from 5.0.0
Prisma Client: disconnect: true does not appear to delete the foreign key in the returned data
Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no needs and count method

    from @prisma/client GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.MarvinShawn, @shangwfa, @dikar, @Tony2000-cmd, @br0kej, @sebastiangeiger01, @ShukurullohNabijonov7, @cellstratindra, @jtsang4, @daylenjeez, @atveit, @Degfy, @normarad, @davidghatley, @chenlulouis, @suhdev, @9imagi, @SilmarMacedo, @mega1365, @petemeng

authors: Cuzzie tanner-chiang

repo: tanner-chiang/AutoGPT


text:
refetchOnWindowFocus necessary for inactive queries?

Hi, I have a page with some data and a faceted search, a new search request is executed every time I add a filter (as expected), but if I change to another window and then return, the refetchOnWindowFocus executes not only for the current query but all inactive search queries.
Is there a usefulness to this behavior that I'm not seeing?
Can we maybe add some way to avoid this? I can do the PR.
(react-query version 1.0.17)

It shouldn't be refetching inactive queries, only stale queries. Are you sure they are inactive and not stale?

@tannerlinsley  please check the video, to the best of my understanding the queries are inactive.
http://somup.com/cYeloOhkkL

Interesting. I’ll take a deeper look at this
On Mar 12, 2020, 9:28 AM -0600, Ivo Anastácio notifications@github.com, wrote:

@tannerlinsley please check the video, to the best of my understanding the queries are inactive.
http://somup.com/cYeloOhkkL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I confirm, here's a codesanbox: https://codesandbox.io/s/goofy-thunder-kzfgw
I'll submit a PR later

Wow, that was fast :D

authors: cherniavskii ivowork tannerlinsley

repo: tannerlinsley/react-query


text:
Documentation Site: CodeSandbox examples are not loading

Describe the bug
When viewing the documentation, i am unable to get the examples to load from codesandbox.
To Reproduce
On the inline section on the documentation i get

if i go to the codesandbox example directly i get

This appears to be with all examples (didn't click on every one but did try about 5 different ones)
Expected behavior
See example on codesandbox

looks like it is back, maybe an issue with CodeSandbox...


text:
Bug: tanstack link is broken in react query official documentation

I opened react query official documentation, when i navigate to tanstack tab, it responded with This site can’t be reached
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop

OS: Windows
Browser Chrome
Version: 83.0.4103.116 (64-bit)

This was due to a cloudflare outage.

authors: abdelrahmanahmed tannerlinsley


text:
Issue 90

Issue 90
GIVEN: I’m logged into the application
WHEN: I need to add a league into the database.
THEN: I want to be able to store all the information for that league
Added CreateLeagues function in db/league.go
AddedPostLeagues Handles in apis/leagues
Added documentation in the leagues.yaml file

A couple nitpicky things, but looks great!

repo: tannerwheeler/powerplay-backend-stats


text:
Segment fault issue

Hi Tao,
I am having some issues with peak calling. From the terminal output, I can see that "building peak model" is being skipped and I guess that is why the peaks are not called. How do I fix this problem?
The terminal output is pasted below.
Thanks in advance
Swadha
Command line: callpeak -t /home/roylab/swadha/histone/HTZ_1/HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001.sam -n /HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001 -g ce --bdg --keep-dup=auto --broad --broad-cutoff=0.01 --nomodel -f SAM --extsize=250 --outdir /home/roylab/swadha/histone/HTZ_1/macs_output
ARGUMENTS LIST:
name = /HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001
format = SAM
ChIP-seq file = ['/home/roylab/swadha/histone/HTZ_1/HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001.sam']
control file = None
effective genome size = 9.00e+07
band width = 300
model fold = [5, 50]
qvalue cutoff for narrow/strong regions = 5.00e-02
qvalue cutoff for broad/weak regions = 1.00e-02
Larger dataset will be scaled towards smaller dataset.
Range for calculating regional lambda is: 10000 bps
Broad region calling is on
Paired-End mode is off
INFO  @ Wed, 03 Oct 2018 14:00:28: #1 read tag files...
INFO  @ Wed, 03 Oct 2018 14:00:28: #1 read treatment tags...
INFO  @ Wed, 03 Oct 2018 14:00:35:  1000000
INFO  @ Wed, 03 Oct 2018 14:00:41:  2000000
INFO  @ Wed, 03 Oct 2018 14:00:55: #1 tag size is determined as 50 bps
INFO  @ Wed, 03 Oct 2018 14:00:55: #1 tag size = 50
INFO  @ Wed, 03 Oct 2018 14:00:55: #1  total tags in treatment: 3353652
INFO  @ Wed, 03 Oct 2018 14:00:55: #1 calculate max duplicate tags in single position based on binomial distribution...
INFO  @ Wed, 03 Oct 2018 14:00:55: #1  max_dup_tags based on binomial = 2
INFO  @ Wed, 03 Oct 2018 14:00:55: #1 filter out redundant tags at the same location and the same strand by allowing at most 2 tag(s)
INFO  @ Wed, 03 Oct 2018 14:00:55: #1  tags after filtering in treatment: 2967172
INFO  @ Wed, 03 Oct 2018 14:00:55: #1  Redundant rate of treatment: 0.12
INFO  @ Wed, 03 Oct 2018 14:00:55: #1 finished!
INFO  @ Wed, 03 Oct 2018 14:00:55: #2 Build Peak Model...
INFO  @ Wed, 03 Oct 2018 14:00:55: #2 Skipped...
INFO  @ Wed, 03 Oct 2018 14:00:55: #2 Use 250 as fragment length
INFO  @ Wed, 03 Oct 2018 14:00:55: #3 Call peaks...
INFO  @ Wed, 03 Oct 2018 14:00:55: #3 Call broad peaks with given level1 -log10qvalue cutoff and level2: 1.301030, 2.000000...
INFO  @ Wed, 03 Oct 2018 14:00:55: #3 Pre-compute pvalue-qvalue table...
INFO  @ Wed, 03 Oct 2018 14:01:05: #3 In the peak calling step, the following will be performed simultaneously:
INFO  @ Wed, 03 Oct 2018 14:01:05: #3   Write bedGraph files for treatment pileup (after scaling if necessary)... /HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001_treat_pileup.bdg
INFO  @ Wed, 03 Oct 2018 14:01:05: #3   Write bedGraph files for control lambda (after scaling if necessary)... /HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001_control_lambda.bdg
INFO  @ Wed, 03 Oct 2018 14:01:05: #3 Call peaks for each chromosome...
Segmentation fault

Could you remove the first '/' from the name "-n /HTZ1.SSTT004_S36HTZ1EX39_TTAGGC_L005_R1_001" and try again? Also, could you let me know the version of MACS2 you installed?

Hi Tao,
Thank you so much for your response. It works now. I have one more doubt which I wanted to clarify:
In my analysis, I didn't give any control/input SAM file then why am I getting "control_lambda.bdg" as one of the outputs which is: bedGraph format for input sample. How is this output generated?
Thanks in advance,
Swadha

@Swadha22 When control data is not available, the control_lambda.bdg would be calculated from treatment/ChIP file instead of control/input in your case.

repo: taoliu/MACS


text:
Apps: Protect against control characters

During create/update check various attributes for signs of command injection.
Also check for characters that are most likely garbage, such as control characters.
Reject request.
See also issues:
https://github.com/tapis-project/tapis-systems/issues/55
https://github.com/tapis-project/tapis-jobs/issues/26

No need to check for command injection. Jobs will do it and conditionally quote strings on command line as needed.
Apps never sends anything directly to command line.

repo: tapis-project/tapis-apps


text:
Wont animate

I can't get the spinner to stay in the middle of the frame

Sorry, can you add more details describing your problem. Thanks!

authors: EfraimB ElectrumDevelopment

repo: tapptitude/TTFortuneWheel-iOS


text:
Basic HTTP Proxy Implementation [Reopens #8]

Http#via and Http#through are the primary methods. They basically transform an array into a dictionary of pieces of proxy software `{proxy_address: addr, proxy_port: port, etc}. Specs need work, but oughta stop us from breaking the functionality.
Usage:
Http.via("127.0.0.1", 8080, "username", "password").get("http://git.io/")

I don't see how this actually uses a proxy, but it does at least appear to be forward progress so I'm merging it

authors: ezkl tarcieri

repo: tarcieri/http


text:
Different behaviour on first load (vs static init script), so custom prezto prompt not loaded

Hi, first of all thanks for zgen, moving from antigen and then from oh-my-zsh to prezto was super easy and now everything is faster.
My custom prezto prompt is not loading when the static init script is not generated. I think it is because, when generating the script, prezto and the modules are loaded in place, while the fpath is not modified until the end after generating the script. I can workaround this by modifying fpath myself, but I'd love to keep it clean and just use zgen load.
I guess there are 2 possible solutions:

Modifying fpath in place in -zgen-add-to-fpath and then it's not necessary to do it in zgen-apply
Not loading stuff in place and once the script is generated source it

Let me know what you think.

Yes this problem still persists but I'm not completely sure what causes it.
I'm leaning towards the option 2 since it makes things simpler. This also means that zgen-apply is no longer needed because you can source the init script at the end of zgen-save.
Does this make debugging faulty configurations a bit harder though? You've basically already generated the static init script and trying to source it as a whole. Is there any benefit for sourcing plugins one by one during the initial setup?

I am having an issue with this as well.  The problem is I am running into is that I cannot override aliases or functions defined in prezto modules with my own aliases defined in custom plugins.  My own custom aliases will be loaded when the init.zsh is initially build, because Zgen sources them in a different order than when sourcing the generated file.
I believe this is caused by putting the calls to pmodload after the General modules section in the init.zsh script.
The fix would be to order the output in init file like this:
# ### General modules
source "/Users/username/.zgen/sorin-ionescu/prezto-master/init.zsh"

# ### Prezto modules
pmodload 'environment' 'terminal' 'editor' 'history' 'directory' 'spectrum' 'utility' 'completion' 'prompt' 'history-substring-search'

source "/Users/username/.zgen/other-module/other-module/init.zsh"
...

Unfortunately, that solution requires special handling of the Prezto plugin and it's not immediately apparent how I could do that in a non-terrible way.  I do think it would be preferable if Zgen would respect the order in which I define my plugins to help with debugging and keeping with a principle-of-least-surprise.
I don't have time at the moment to try to fix this, but I can investigate how to do this in a sane way and whip up a PR if there is interest in pursuing this path.

I was able to work around the issue by setting export ZGEN_PREZTO_LOAD_DEFAULT=0, and loading any Prezto modules with the zgen load sorin-ionescu/prezto modules/[MODULE] syntax.   This prevents Zgen from generating the calls to pmodload.  Generating my init.zsh file is now deliciously deterministic.

My above solution has some problems of its own, namely that without pmodload, functions from prezto modules (in 'functions' dir) aren't loaded properly.  This became a big enough issue for me that I fixed it:  https://github.com/tarjoilija/zgen/pull/87
The change is here on my fork: https://github.com/brandon-fryslie/zgen
@tarjoilija, thanks for your great work.  Your project is fantastic.  I hope we can find a way to merge my PR so I don't have to maintain a fork.

authors: brandon-fryslie tarjoilija xavistp

repo: tarjoilija/zgen


text:
Release 0.2.0

Berhubung telah dirilisnya versi 0.1.0, dan masih banyak beberapa fitur yang saya tunda ke rilis berikutnya, saya ingin mencatat beberapa yang akan saya tambahkan ke rilis 0.2.0.
Fitur tambahan untuk rilis 0.2.0
Software Development

[ ] testing!!!

Fitur hidrokit
prepkit

[ ] fungsi membaca satu file
[ ] fungsi membaca file lebih dari satu
[ ] fungsi membaca data bmkg online

calckit
Module calckit akan digunakan untuk pengolahan data setelah melalui proses prepkit.

[ ] fungsi statistik deskriptif

viewkit

[ ] fungsi mencetak hidrograf

Notebook (Tutorial)

[ ] Penggunaan hidrokit.bmkgkit
[ ] Penggunaan fungsi baru

Dokumentasi

[ ] Panduan instalasi untuk pengembangan / development
[ ] Panduan instalasi untuk penggunaan
[ ] (Jupyter) Membuat symbolic link untuk memudahkan akses dokumen di luar working directory
[ ] Penjelasan fungsi-fungsi di prepkit
[ ] Penjelasan fungs-fungsi di viewkit
[ ] Memperbarui roadmap

Punya ide lain? Jangan sungkan untuk menambahkannya. Dimungkinkan to-do list diatas dibuat terpisah dalam bentuk isu ataupun pull request.

 Diskusi Release 0.2.0

repo: taruma/hidrokit


text:
🛑 Immich is down

In 4f513b2, Immich (https://immich.goka.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Immich is back up in db1f0c7 after 14 minutes.

repo: tastelessjolt/upptime


text:
🛑 Immich is down

In c9ae149, Immich (https://immich.goka.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Immich is back up in b94766a after 12 minutes.