text:
Enabled not working with plotOptions using Highcharts

Bug or Feature Request?
It seem like a error.
Description
There's already ''enabled'' used in the code but for some reason its not working. I am using a line chart with Highcharts and want the lines to be highlighted while fading  out the others. Here is the code, do let me know what possibly can be the error.
const plotOptions = {
series: {
stickyTracking: false,
states: {
inactive: {
enabled: true,
}
}
}
};
Also there's a link below to the example which I am trying to achieve in my code.
How to reproduce
https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/plotoptions/series-states-inactive-disabled
Some other similar examples :
https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/plotoptions/series-selected/
https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/members/series-select/
Live demo demonstrating bug
Versions

React JSX Highcharts version:
Highcharts version:
React version:

I don't quite understand what the problem is.
Can you please make an example with https://stackblitz.com/edit/base-chart-example

Thanks for the reply.
The example you have mentioned is something I am trying to recreate using Highcharts but for some reason its not working.
And here ( https://stackblitz.com/edit/base-chart-example ) I can't see any function or module used to highlight the line.
So I am bit confused why there's an error while I tried doing it.

authors: Chitralekha-Hassan anajavi

repo: whawker/react-jsx-highcharts


text:
New 2.1.5 does not sync

I've just upgraded to the new 2.1.5 and it does not sync the blockchain. There are errors in the log file like:
...
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

2024-02-19T14:23:33.727 full_node wheat.full_node.full_node: ERROR    Error: Err.INVALID_BLOCK_COST, Invalid block from peer: PeerInfo(_ip=IPv4Address('188.163.24.151'), _port=21333)
2024-02-19T14:23:33.730 full_node full_node_server        : ERROR    Exception: Error short batch syncing, failed to validate blocks 4499897-4499929, PeerInfo(_ip=IPv4Address('188.163.24.151'), _port=21333). Traceback (most recent call l
ast):
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 404, in wrapped_coroutine
    result: Message = await coroutine
                      ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/limited_semaphore.py", line 37, in acquire
    yield self._available_count
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node_api.py", line 134, in new_peak
    await self.full_node.new_peak(request, peer)
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 764, in new_peak
    if await self.short_sync_batch(peer, uint32(max(curr_peak_height - 6, 0)), request.height):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/priority_mutex.py", line 77, in acquire
    yield
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 606, in short_sync_batch
    raise ValueError(f"Error short batch syncing, failed to validate blocks {height}-{end_height}")
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

2024-02-19T14:23:33.732 full_node full_node_server        : ERROR    Exception: Error short batch syncing, failed to validate blocks 4499897-4499929 <class 'ValueError'>, closing connection PeerInfo(_ip=IPv4Address('188.163.24.151'), _po
rt=21333). Traceback (most recent call last):
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 425, in _api_call
    response: Optional[Message] = await asyncio.wait_for(wrapped_coroutine(), timeout=timeout)
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/tasks.py", line 447, in wait_for
    return await fut
           ^^^^^^^^^
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 404, in wrapped_coroutine
    result: Message = await coroutine
                      ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/limited_semaphore.py", line 37, in acquire
    yield self._available_count
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node_api.py", line 134, in new_peak
    await self.full_node.new_peak(request, peer)
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 764, in new_peak
    if await self.short_sync_batch(peer, uint32(max(curr_peak_height - 6, 0)), request.height):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/priority_mutex.py", line 77, in acquire
    yield
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 606, in short_sync_batch
    raise ValueError(f"Error short batch syncing, failed to validate blocks {height}-{end_height}")
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

我刚刚升级到新的 2.1.5，它不同步区块链。日志文件中有如下错误：
...
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

2024-02-19T14:23:33.727 full_node wheat.full_node.full_node: ERROR    Error: Err.INVALID_BLOCK_COST, Invalid block from peer: PeerInfo(_ip=IPv4Address('188.163.24.151'), _port=21333)
2024-02-19T14:23:33.730 full_node full_node_server        : ERROR    Exception: Error short batch syncing, failed to validate blocks 4499897-4499929, PeerInfo(_ip=IPv4Address('188.163.24.151'), _port=21333). Traceback (most recent call l
ast):
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 404, in wrapped_coroutine
    result: Message = await coroutine
                      ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/limited_semaphore.py", line 37, in acquire
    yield self._available_count
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node_api.py", line 134, in new_peak
    await self.full_node.new_peak(request, peer)
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 764, in new_peak
    if await self.short_sync_batch(peer, uint32(max(curr_peak_height - 6, 0)), request.height):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/priority_mutex.py", line 77, in acquire
    yield
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 606, in short_sync_batch
    raise ValueError(f"Error short batch syncing, failed to validate blocks {height}-{end_height}")
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

2024-02-19T14:23:33.732 full_node full_node_server        : ERROR    Exception: Error short batch syncing, failed to validate blocks 4499897-4499929 <class 'ValueError'>, closing connection PeerInfo(_ip=IPv4Address('188.163.24.151'), _po
rt=21333). Traceback (most recent call last):
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 425, in _api_call
    response: Optional[Message] = await asyncio.wait_for(wrapped_coroutine(), timeout=timeout)
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/tasks.py", line 447, in wait_for
    return await fut
           ^^^^^^^^^
  File "/home/fik/wheat-blockchain/wheat/server/ws_connection.py", line 404, in wrapped_coroutine
    result: Message = await coroutine
                      ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/limited_semaphore.py", line 37, in acquire
    yield self._available_count
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node_api.py", line 134, in new_peak
    await self.full_node.new_peak(request, peer)
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 764, in new_peak
    if await self.short_sync_batch(peer, uint32(max(curr_peak_height - 6, 0)), request.height):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/contextlib.py", line 222, in __aexit__
    await self.gen.athrow(typ, value, traceback)
  File "/home/fik/wheat-blockchain/wheat/util/priority_mutex.py", line 77, in acquire
    yield
  File "/home/fik/wheat-blockchain/wheat/full_node/full_node.py", line 606, in short_sync_batch
    raise ValueError(f"Error short batch syncing, failed to validate blocks {height}-{end_height}")
ValueError: Error short batch syncing, failed to validate blocks 4499897-4499929

source: gharchive/issue

authors: jfikar wheatnetwork

repo: wheatnetwork/wheat-blockchain

license_type: permissive

license_source: github-api


text:
Device doesn't show up when loaded/imported if no device was previously loaded (Trac #138)

Fixed in 6b814143e2e19239e2692fec3fe6625ce73799da
Migrated from http://microfluidics.utoronto.ca/microdrop/ticket/138
{
    "status": "closed",
    "changetime": "2014-04-17T19:39:01",
    "description": "Fixed in 6b814143e2e19239e2692fec3fe6625ce73799da",
    "reporter": "ryan",
    "cc": "",
    "resolution": "fixed",
    "_ts": "1397763541728826",
    "component": "microdrop",
    "summary": "Device doesn't show up when loaded/imported if no device was previously loaded",
    "priority": "major",
    "keywords": "",
    "version": "0.1",
    "time": "2013-04-09T17:08:46",
    "milestone": "Microdrop 1.0",
    "owner": "",
    "type": "defect"
}

Trac update at 20130409T17:15:48:

ryan changed description from "" to "Fixed in 6b814143e2e19239e2692fec3fe6625ce73799da"
ryan changed resolution from "" to "fixed"
ryan changed status from "new" to "closed"

Trac update at 20140417T19:39:01: ryan changed component from "" to "microdrop"

repo: wheeler-microfluidics/microdrop

license_source: bigquery


text:
[windows] Добавить в плеер управление скоростью

его почему-то нет)

забыл :trollface:

топ 😊

вернул

authors: neverlane wheremyfiji

repo: wheremyfiji/ShikiWatch

license: MIT


text:
allow filtering done() by method

Fix for https://github.com/wheresrhys/fetch-mock/issues/262

Coverage increased (+0.03%) to 97.765% when pulling ec1f0cc370d09de1001a9449a3ca10df12a59979 on filter-done-by-method into 25fdad98f2ab818eb92bf9600356e206f9eeef54 on master.

source: gharchive/pull-request

authors: coveralls wheresrhys

repo: wheresrhys/fetch-mock

license: mit


text:
Missing .podspec file

While doing Install with cocopods part of setup and running pod install I got following message:

No podspec found for 'react-native-nfc-manager' in '../node_modules/react-native-nfc-manager'

While there is react-native-nfc-manager.podspec file in your repository, there is no such file in node_modules/react-native-nfc-manager directory. Additionally it isn't included in files in package.json
  "files": [
    "NfcManager.js",
    "NdefParser.js",
    "index.d.ts",
    "android",
    "ios",
    "example"
  ],

Is running pod install not necessary?

Sorry for the late response, it's indeed missing and I will add it back. Thanks for spotting this issue!

Any update on this or a workaround?

Hi, sorry for the delay. I have just added the podspec back to released npm module in latest v0.5.5 release. Thanks!

authors: jlkalberer maciejimielowski whitedogg13


text:
TI DAC081C081CIMK TSOT-6

Nothing closely related. Package seems unusual, needs close attention.

This is just a SOT-23-6, except it's THIN.

https://github.com/KiCad/kicad-symbols/pull/463 Kicad PR

Merged upstream

authors: awygle whitequark

repo: whitequark/Glasgow-JTAG


text:
chore(release): v1.0.1 🎉

:robot: I have created a release beep boop
1.0.1 (2023-09-16)
Bug Fixes

pkg: expose extract oidc request uuid from origination cookie (d0bf7fb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/whodisio/simple-oidc-auth/releases/tag/v1.0.1 :sunflower:

repo: whodisio/simple-oidc-auth


text:
Updating Ubuntu versions in README.md

cf https://github.com/whoenig/thinkpad-p14s-gen2-ubuntu/issues/6

Thanks!

authors: faustusdotbe whoenig


text:
脚本目录中多了一个100多MB的文件core

Qinglong version
正式版 v2.17.1
Steps to reproduce
似乎安装依赖后生成的？我删除后，面板页面会闪烁，看到依赖那里正在重新安装依赖
What is expected?
不建议在用户拉取的脚本所在的目录创建，不便备份数据
What is actually happening?
不建议在用户拉取的脚本所在的目录创建，不便备份数据
System Info
No response
Any additional comments?
No response

脚本执行异常出现的，没用

脚本执行异常出现的，没用

没用也能不能写入在别的地方，尽量不要在/ql/data目录下。。。

authors: donething whyour

repo: whyour/qinglong


text:
Add processing of the field postfix_status_data

postfix_status_data is also a KeyValue field that contains interesting information in case of NOQUEUE.
Processing it give us the same informations as postfix_keyvalue_data field.

All examples in the test suite have in their status data only single-worded strings: either an ip or an email address. I also have an example of a verp-syntax email address (smtpd_0026). Running this string through the kv filter will break things.
Can you give an actual example of a complete log line (see the test files for examples) that contains the payload you're looking for?

Okay ... doing code 30 min before the end of the day is not the best idea in the world.
I mixed everything, I apologize for this mistake. postfix_status_data doesn't contains any keyValued data.
Please discard this pull request.

authors: Belphemur whyscream

repo: whyscream/postfix-grok-patterns


text:
No Let's Encrypt Certificate for base domain

Firstly, thank you for publishing this amazing project.
Currently, I am trying to deploy the project to a digital ocean droplet. I can access services like pgadmin, traefik and flower; however, on the base domain, I am missing a let's encrypt certificate (instead I am issued a traefik default cert).
Am I missing a configuration step besides the ones listed in the excellent deployment documentation? Or should the frontend and backend containers be part of the traefik netwok as well?
Thank you.

Hey @an-mu
Everything needs to be part of the traefik network since the front- and back- are going to be communicating via the API. I'm assuming you followed the guide step-by-step? https://github.com/whythawk/full-stack-fastapi-postgresql/blob/master/docs/deployment-guide.md#traefik-proxy-with-https

If it does break for something I haven't documented, please let me know. Always good to add gotchas to the documentation for future reference. It means we keep improving things. Thanks.

authors: an-mu turukawa

repo: whythawk/full-stack-fastapi-postgresql


text:
🛑 REST API is down

In b4634c9, REST API (https://de.wickepedia.org/rest.php/v1/page/Main_Page) was down:

HTTP code: 403
Response time: 9 ms

Resolved: REST API is back up in 6fdc951.

repo: wickepedia/status


text:
Me again.  How to install.

OK.  Now I have an EeePC running Debian.  And I have downloaded the wifi-tally-v0.4.2.zip  and wifi-tally-v0.4.2.tar.gz.   But I have no idea how to/whether to install them.
----Paul-----

Both of the archives contain the exact same files – so it does not matter which one you use. tar.gz is the format I would go with for linux, because any distribution can handle it without the need for additional packages. You just need to extract the archive using your file manager and should end up with a directory structure like that
wifi-tally-v0.4.2
  - documentation
  - firmware
  - hub
  - tally

You can ignore firmware and tally for now. You only need them when building your own hardware. Open a terminal and enter the hub directory.
cd ~/Downloads/wifi-tally-v0.4.2/hub

(Your path might vary, depending where your stored it)
You might need to install nodejs, if you have not already:
sudo apt-get install nodejs

Then start the hub
npm run start

... and you can open a browser and should see the hub on http://127.0.0.1:3000

Woo-hoo, it's  running.  Your instructions were great but I'm going to add a couple of things here because I expect some other noobs will find this thread useful.
Main guidance is:  when you get an error message, Google is your friend.
When I tried the sudo apt-get, I was informed I was not on the sudoers list.  Apparently a common fresh-install Debian issue.
Once I had nodejs installed and tried to run the hub, I was told npm was not a known command.  node -v worked but npm -v did not.  Again, apparently not all that uncommon.  A stackoverflow page gave me a curl command to run to fix it but then I had to install curl.
Finally , all seems to work.
Thank you.
-----Paul-----

Aaand, I'm back.  Two pics attached from my present setup.  Which almost but not quite runs.

Asbestos I can tell, the wifi-tally and the hub are fully working.  They are all static IPs and connected by ethernet.  I have created one web tally on the hub and when I click 'Connect' I get a screen that turns colors depending on how Camera One is set.
My problem comes when trying to access from outside via wifi.  At first I attached a simple AP and tried to set up dhcp on the same machine as the hub.  Never could get configuration right.  All the config guides assume there will be an internet connection and trying to leave that out upsets them.
Finally I realized I had an AP that had its own dhcp server.  I now have that attached to the system.  It seems to work.  Some of my phone network utilities can see 10.55 and 10.240 within the network.  But I cannot find a way to log in to get the phone to acts as a wifi tallly.  I am sure I am missing something basic but hope that you can point it out to me.
I have to admit the 0.0.0.0:7411 notation has me stonkered.
-----Paul-----

Hey.
Great you made it this far.

Asbestos I can tell, the wifi-tally and the hub are fully working.

Yes. Connection from Hub to ATEM looks perfect. :+1:

I have to admit the 0.0.0.0:7411 notation has me stonkered.

This address will not help you much. 0.0.0.0 is a special IP address that basically means that connections on all your network devices are accepted. So if your EeePC was connected via wire and wifi you could connect to the hub with either IP address. 7411 is the port.
To get the IP address of your EeePC, type ip addr. It returns something like this:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
...
    inet 192.168.178.42/24 brd 192.168.178.255 scope global dynamic noprefixroute enp4s0
       valid_lft 861173sec preferred_lft 861173sec
    inet6 fe80::6fb5:452e:c846:5c10/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:28:27:7d brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
...

Look for the address starting with 192.168.10 – that is the address you want your smartphones to connect to. In my example this address is 192.168.178.42. So I type http://192.68.178.42:3000 in my browser.

My problem comes when trying to access from outside via wifi.

Configuring networks can be quite confusing when doing it for the first time. It's a good decision to not run your own DHCP server. Speaking from experience. :smile:
I understand your network layout looks similar to this!?

The point where you seem to have trouble is the connection between your AP and the (old) router, correct? Did you manage to connect any devices that are on the different networks?
The AP seems to give out IP Addresses like 10.55.*.* or 10.240.*.*, but your ATEM has the address 192.168.10.240. Did you configure the routing tables to connect those two networks?
How you do this is highly depended on the devices you use. What you basically need to achieve is to tell your AP "if you get packages for an IP address that matches the pattern 192.168.178.*, send it to the router instead". And your Router needs to know "if you get packages for an IP address that matches 10.55.*.* or 10.240.*.*, send it to the access point".
I hope this helps you further and the information was not too basic or high-level. Routing table and the name of your AP or router is what you might want to search for.
If it does not help, feel free to check back.

Routing Tables, oh dear.  I have never ventured that deep into the jungle before.  But if that is what I need, I shall venture forth.  I do appreciate your guidance.  Yes, you visualize the network layout properly.   The router is a Netgear unmanaged switch, so as far as I can tell it doesn't change anything passing thru it.   I appreciate your confirming that the address I am trying to reach is  http://192.168.10.55:3000.  I believe I have the access point configured to give out 192.168.10.x addresses but I will do what I can to double check that.
-----Paul-----

OK, I thrashed around a good bit today.  Made enough changes to the router setup that I feared I would never get it going again.  Network configuration is truly a blend of witchcraft and black magic.  Anyhow, in the end it seems that my technology has been fooling me and it has been working all the time.  At any rate I can log in via wifi to 198.164.10.55:3000 using a laptop browser and the remote Tally function works just fine.   But, for the life of me I cannot get a phone based browser to successfully log in.  I have tried an android and an iPhone (old).  They both attach to the network and accept the URL and appear to begin to load the page but then stop, with nothing rendered.  No error codes, just stop.
Anyhow, I am ready to proceed to the next step - making the actual Tallys.  There will probably be more messages.
-----Paul-----

As I mentioned before, the hub and web tally's work fine.  My worship leader was able to log in with his iPhone, so I don't know why my phones won't hook up.  But I have been working of the wifi tallys.
I bought these (https://smile.amazon.com/gp/product/B07L8W9SP3/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1) and this (https://smile.amazon.com/gp/product/B07BKPS3G1/ref=ppx_yo_dt_b_asin_title_o02_s01?ie=UTF8&psc=1)
I had played with programming an Arduino years ago, so the programming process was not COMPLETELY foreign, though I struggled with it.  I think I succeeded.  The LED strip is a 3 wire as illustrated in the Reference rather than a  4 wire like in the Starting instructions.
I have yet to see anything from the LED strip.  On the 8266 board itself there is some reaction which is undescribed in the instructions.  So I thought I would ask if this is meaningful, either in a good or bad way.
There are two blue LEDs on the board.  One is on the upper right corner.  The other is just to the left of the USB port.  Without the LED strip attached, the blue light in the corner is on solid and the blue light next to the USB is blinking about once a second.
Attaching the LED strip by the diagram in tally.html generally causes both blue LEDs to go out.  Though not always.  I haven't discerned a pattern.  Attaching a simple single color LED between 3V3 and D4 causes the LED to light, the flashing blue LED to go out and the steady LED remains on.
I'm hoping some of this means something.  I don't have a way to test the LED strip since it apparently needs a modulated signal to produce any light at all.  I suppose I should have ordered a controller with it.
-----Paul-----

And so now I have ordered a controller.  At least I will be able to determine whether the LED strip is defective.

Great to hear you made it one step further.

I have yet to see anything from the LED strip. On the 8266 board itself there is some reaction which is undescribed in the instructions. So I thought I would ask if this is meaningful, either in a good or bad way.

It is not described in detail, because not all boards have this LEDs. But it seems you got the same build that I have.
Flashing is usually a good sign - it means the microcontroller is doing something. It seems your flashing process has worked.
Consider the LED in the top red corner as an indicator that the board is powered. The other LEDs flash pattern is described in the Troubleshooting Guide. You should find the pattern you are seeing and some possible causes there.

I'm hoping some of this means something. I don't have a way to test the LED strip since it apparently needs a modulated signal to produce any light at all. I suppose I should have ordered a controller with it.

Nah. You are good to go. What you are having is a WS2812 compatible LED strip – the microcontroller can drive that too. See the detailed tally documentation on how to set it up. It's just a configuration and a little different wiring.

Attaching the LED strip by the diagram in tally.html generally causes both blue LEDs to go out.

This sounds a bit concerning. This usually means that the controller stopped working, because of a short circuit or too high power drain. This does not do permanent damage in most cases, but it is one of the things that you should not do too often. And please take extra notice of this warning in the documentation: "Do not connect more than 5 LEDs to the board!" This might definitely drain too much current if you connected all 144 LEDs.

Thank you.  I have been doing my testing at home where there is not the wifi signal the Tally is looking for.  I will take it to church tomorrow and see if I get something new.  I have actually dropped back from 5 to 3 LEDs on the strip, just in case of excessive power draw.  The blue LED flash pattern - I was thinking the Troubleshooting Guide was talking about the WS2812 LEDs.  This is actually encouraging.
-----Paul-----

If I need to correct the tally-settings.ini that I uploaded, can I just re-upload the corrected file or do I need to erase the entire chip and start over?
Hope you are having a pleasant Memorial Day.

Was able to answer my own question.  While examining the tally-settings.ini examples in the instructions I noticed that I had messed up the hub.ip in my upload.  I had 12.168 instead of 192.168.  With that corrected, the tally connected to the hub near instantly, was recognized, and could be assigned to a camera.  Only thing it couldn't do was light up the LED strip.   Nothing shows there.  I tried moving around the connections.  No change.
On Thursday, Amazon is to deliver a controller for the strip.  Then I should be able to prove whether I destroyed the LEDs while trying to solder to those tiny pads or what.
I kind of wish there was a simpler version that would simply light up discrete LEDs.  Would seem simpler to diagnose.  But I look forward to exploring the mysteries of this one as they present themselves.
-----Paul-----

IT WORKS!!  First I decided to guess that the reference to Common Cathode might mean some discrete LEDs with the cathodes tied together.  Then I had to look up how to determine which was the cathode.  Then I spent an hour fruitlessly testing.  Then I reread the instructions and finally noticed that it said to connect to GND rather than 3v3.  And then I tested some different connection points and finally got an LED to turn on ... and off.  And then another LED at a different connection point turned on and off.  And now it tells me whether the camera is on preview or live.
Whahoo!  Thank you.  This is great.  Now if I can just package it in a moderately attractive package ....
*****Not your problem. *****
But maybe you could add a few more explanatory words to the section about Common Cathode.   1.  That it refers (or can refer) to discrete LEDs, and 2.  That they will use the same pins (D1, D2, D3) as the Build and Setup a Wifi Tally page EXCEPT using GND instead of 3v3.
-----Paul-----

Awesome!
It's always tricky to get documentation right to cater different audiences, but you are right there could be more details or an example schematic on your setup. Feel free to create a pull request on the documentation with the information that might have helped you. In the future I hope to have guides for different setups – with one recommended setup.
Just one thing to add: Did you add any resistors to the LEDs? When using discrete LEDs you should always add a resistor between the pin D1, D2, D3 and the respective pins on the LED. Otherwise you might risk burning the LED. It usually does not happen quickly, but reliability is key for a tally light. :wink: 150Ohm for red and 100Ohm for blue and green are common values to use.

Does the value for operator.ws2812 need any adjustment?

No. If you don't use it, it does not matter what you set. You could set it to 0, but you would not see any performance difference anyways.

Your comment on 'create a pull request' reminded me how little I know about the github environment. And then I got a note about renaming to vtally.  So I looked around in history.
.... My god you have poured a lot of work into this.  And I am so grateful for your support.
So far I have built a Mk 1 [(cardboard box size of an old cigarette case), ugly as home made sin but works], Mk 1 Mod 1 (smaller plastic case), and  a MK 2 model where the lights are on a cord independent of the case.  Trying to build a second Mk 2 but my clumsy fingers are in the way.
So far have not succeeded in incorporating WS2812, only individual LEDs, but they work fine and serve our purpose.
I don't want to violate githubs standards but would be interested in trying the 'pull request' and adding some commentary.  Is there a style guide or whatever I should peruse?
----Paul------

I don't want to violate githubs standards but would be interested in trying the 'pull request' and adding some commentary.

There is not much to worry about. 😄 Everyone of started with their first pull request at some point. The good thing is: You can't really break anything. So don't panic. I can have a look before your changes are integrated.

Is there a style guide or whatever I should peruse?

There is not really a styleguide. The documentation is generated by some files in the documentation directory. The file format is markdown (the same markup language you can use in the github comments) plus a few plugins for variable substitution and info boxes. You can edit it with any text editor or even with the browser editor on Github. The syntax should be pretty obvious, if you compare the markdown files with the rendered documentation.
If you want to see your result before submitting to github this should be really easy on a linux machine (you are working on the Eee Pc, right?). Brief documentation is here, but this should work for you on Debian:
# this should be installed by default, but to be sure
sudo apt-get install python3

cd documentation/
python3 -m pip install -r requirements.txt --user

mkdocs serve

and open your browser on http://127.0.0.1:8000 It should update the documentation shown everytime you save your changes.

Discussion went stale. Closing.

repo: wifi-tally/wifi-tally


text:
Deployment don't work.

hardhat-deploy version: 0.8.11
I am trying to deploy a simple contract with one dependency called ProtectionResolver.sol

I get stuck, no error and no deployment.

Let me know if you need more information.
Thanks!

This is most likely due to gas change while the deploy tx was sent, you can safely restart the process.
new version of hardhat-deploy will ask you if you want to increase gas
older will keep waiting for the tx unless you delete the .pendingTransactions file in the deployment folder

authors: Gauddel wighawag

repo: wighawag/hardhat-deploy


text:
Page images: Rerender mobile-sections for added properties as well

Follow-up on #123

Coverage remained the same at 93.196% when pulling 4aa0b6432496a04fa3de39d2988c42649b824713 on d00rman:page-images/added-props into 756d47a7ef3c95875e8f294d853f2a331a485b67 on wikimedia:master.

repo: wikimedia/change-propagation


text:
update of interaction types

Can you please have a look at this code and tell me if we can/should update this:
	private static Resource getLineTypeResource(LineType lt) {
		if(lt.equals(LineType.ARROW)) {
			return null;
		} else if (lt.equals(LineType.TBAR)) {
			return Wp.Inhibition;
		} else if (lt.equals(MIMShapes.MIM_CATALYSIS)) {
			return Wp.Catalysis;
		} else if (lt.equals(MIMShapes.MIM_CONVERSION)) {
			return Wp.Conversion;
		} else if (lt.equals(MIMShapes.MIM_INHIBITION)) {
			return Wp.Inhibition;
		} else if (lt.equals(MIMShapes.MIM_STIMULATION)) {
			return Wp.Stimulation;
		} else if (lt.equals(MIMShapes.MIM_TRANSLATION)) {
			return Wp.TranscriptionTranslation;
		} else if (lt.equals(MIMShapes.MIM_NECESSARY_STIMULATION)) {
			System.out.println("TODO: necessary stimulation");
		} else if (lt.equals(MIMShapes.MIM_MODIFICATION)) {
			System.out.println("TODO: modification");
		} else {
			System.out.println("Unknown and unsupported interaction type: " + lt);
		}
		return null;
	}

I think we might have to. This is what I find in the output of the RDF generation
778x "Unknown and unsupported interaction type: mim-binding"
30x "Unknown and unsupported interaction type: mim-cleavage"
9x "Unknown and unsupported interaction type: ReceptorSquare"
6x "Unknown and unsupported interaction type: Receptor"

@DeniseSl22, @mkutmon, what does your outline of interactions have for these three mim types?

mim-cleavage
MIM_NECESSARY_STIMULATION
MIM_MODIFICATION

Was there a reason why that one was missing in the current WikiPathways Ontology/Vocabulary?

Hi @egonw , @mkutmon and @RyAMiller ,
I think we should leave the current GPML2RDF conversion for the existing MIM-types in PWs.
We will not have a new interaction panel in the next PV release, because then we would need to do (major) updates to the WPs website as well (and it's better to do this for the new dev site, than for the old one)....
For the unsupported ones: the ReceptorSquare and Receptor should not be used; could you make a unit test for these in Jenkins, so we can find them and change them to whatever it should mean?
For the MIM-binding and cleavage, these do exist and people are allowed to use them.
In the new panel, I'm proposing the following:
Mim-cleavage: becomes "Conversion"
Mim-necessary-stimulation: becomes "Stimulation"
mim-modification: become "Modification" .
And may I draw your attention to the latest addition of the MIM panel, translocation? This was originally mentioned in the paper describing the MIMs in PV, but never implemented. It is part of the code now (and will be part of PV in the next release @mkutmon and me are working on).
Hope this gives @egonw enough info to go in, if not let me know!

See this document for details: https://docs.google.com/document/d/1YhaqPVznPyn270skwmEcDBWzezsu1lOClEG4eIKyTQM/edit?usp=sharing


text:
[WFLY-16627]: Remove some of the mixed-domain transformer from the messaging-activemq module.

Removing the test classes checking the mixed-domain for management API  versions prior to what was in WF 23.
Removing the chained transformation forr versions prior to what was in WF 23.

Jira: https://issues.redhat.com/browse/WFLY-16627
Signed-off-by: Emmanuel Hugonnet ehugonne@redhat.com

Thanks @ehsavoie

authors: bstansberry ehsavoie

repo: wildfly/wildfly


text:
First Open Dialog

Since the data for websites is now an optional permission that breaks image loading. Have a disablable popup that shows when it this permission is turned off letting the user know that this is the case and a button for quickly opening and turning on the permission.

https://extensionworkshop.com/documentation/develop/best-practices-for-collecting-user-data-consents/
Followed example from above and made a one time modal

repo: wilgaboury/super-speedy-dial


text:
Sourcing the image sensor?

Hello! I am not seeing any source online for the sensor. Maybe I am just missing it. Do you have any suggestions?

I haven't tried to find it on Aliexpress, but I think you might find one or two reseller there.

I found some on Alibaba but didn't try
https://www.alibaba.com/product-detail/-100-Brand-New-Original-IMX283EQJ_1600673386520.html?spm=a2700.galleryofferlist.normal_offer.d_title.6f9c6931VhjPxr

Thank you! I sent an inquiry.

Okay those are $65 each, with $30 DHL shipping. I will look more at getting these base boards made, and consider building some.

Oh that’s not the real price. The listing I found also said $1 but when you contact the vendor they are $65.

@will127534 how did you managed to solder Sony IMX283 on your PCB ? how difficult it was ?

Im also having issues find the sensor (ie sony IMX 585), without buying an entire camera that is.
where do you all buy it from? (im in usa)  thanks

@bob454522:
Try here: https://www.aliexpress.com/item/1005006320816093.html

@will127534 @tlalexander @matescb @DomML @bob454522 Do anybody know if the imx283EQJ sensor work for the oneincheye pcb? And as I understand it doesn't shoot color, is that correct? Kind regards aspiring engineer(:


text:
chore(main): release 1.26.0

:robot: I have created a release beep boop
1.26.0 (2023-12-21)
Features

add hdl_checker (#336) (9453e3d)
add snyk-ls server mapping (#342) (ef713a5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/williamboman/mason-lspconfig.nvim/releases/tag/v1.26.0 :sunflower:


text:
Listing Page Featured Images

Sometimes, Featured Images do not visually appear, or appear anywhere in the html of a post page, and it just lives on the listing page.
Sometimes, this image will be represented in the og:image tag, which is easy to grab, but I am not sure how to handle featured images which only live on the listing page.

I wanted to record a hack for something similar I did to grab tags from listing pages as they were not on posts.
Selectors:
    static final String TAGS_LINKS_FINDER = "https://www.koesterlawllp.com/blog";
    static final String TAGS_LINKS = ".blog-category-list a";
    static final String TAGS_LISTING_URIS_TO_SAVE = "a.blog-title-link.blog-link";

Builders:
    static void buildTagMultiMap() {
        try {

            org.jsoup.nodes.Document tagsdoc = Jsoup.connect(hubXmlSelectors.TAGS_LINKS_FINDER).get();
            if (hubXmlSelectors.TAGS_LINKS.length() != 0) {
                Elements tags = tagsdoc.select(hubXmlSelectors.TAGS_LINKS);
                if (!tags.isEmpty()) {
                    for (org.jsoup.nodes.Element tag : tags) {
                        try {
                            org.jsoup.nodes.Document tagListingPage = Jsoup.connect("https://www.koesterlawllp.com" + tag.attr("href")).get();
                            if (hubXmlSelectors.TAGS_LISTING_URIS_TO_SAVE.length() != 0) {
                                Elements taglistingUris = tagListingPage.select(hubXmlSelectors.TAGS_LISTING_URIS_TO_SAVE);
                                for (org.jsoup.nodes.Element taglistingUri : taglistingUris) {
                                    tagMultimap.put(taglistingUri.text(), tag.text());
                                }
                            }

                        } catch (Exception e) {

                            System.out.println("Had trouble finding the tag listing start page");
                        }
                    }
                }
            }

        } catch (Exception e) {

            System.out.println("Had trouble finding the tag listing start page");

        }

    }

and then just call hubXmlBuilders.buildTagMultiMap(); before calling builders

Okay I did do this with something like this in postFinder.java:
static ListMultimap<String, String> featuredImgeMultimap = ArrayListMultimap.create();
...
featuredImgeMultimap.put(listingLink.attr("href"), listingFeaturedImage.attr("src"));
(as your add links to postsToScrub)
...

and adding two new selector:
static final String BLOG_LISTING_FI = "img";
static final String BLOG_LISTING_ITEM = ".masonry-grid-item";

and then in builders:
List<String> featuredImageUri = hubXmlPostFinder.featuredImgeMultimap.get(post);
System.out.println(featuredImageUri.get(0));
Element postMeta = new Element ("post_meta", WP);
item.addContent(postMeta);
postMeta.addContent(new Element ("meta_key", WP).setText("_thumbnail_id"));
Element metaValue = new Element ("meta_value", WP);
CDATA metaValueCdata = new CDATA(String.valueOf(id + 4000));
metaValue.addContent(metaValueCdata);
postMeta.addContent(metaValue);
// Build <item> for featured image
buildFeaturedImage(post, featuredImageUri.get(0), id);```

I did not live how this worked for the record, but it did work

repo: williamspiro/hubXml


text:
ConfigCommands is not compatible with more than one Minecraft version

Due to the addition of OpSenders, ConfigCommands now accesses classes from the org.bukkit.craftbukkit package. These classes often change over different Minecraft versions, causing plugins from one version to throw ClassNotFound exceptions in other versions.
It would be good if ConfigCommands supported more than one Minecraft version, ideally all those supported by CommandAPI, 1.13 - 1.19.

Ready for release in version 3.0.0

repo: willkroboth/ConfigCommands


text:
Parsing html with an invalid url will crash Parse

The microformats parser will crash when url.Parse returns an error. The "parsed" will be nil and this will crash inside ResolveReference.
I found it while parsing: https://chat.indieweb.org/dev/2018-04-17. This will also crash when run with gomf https://chat.indieweb.org/dev/2018-04-17
https://github.com/willnorris/microformats/blob/bc552049783fddac99a36ffb65bf3c99f12b64d7/microformats.go#L226
(Originally published at: https://publog.stuifzandapp.com/posts/567)

For a test case, the URL that is failing is "http://vrij-inter.net profile bijnasimon"

authors: pstuifzand willnorris

repo: willnorris/microformats


text:
Random hangs (unresponsive) on latest x64 Supermium (122.0.6261.85 64 bit)

Describe the bug
The latest Supermium 122.0.6261.85 64 bit randomly hangs, it doesnt matter which webpage I am on, even with 1 or 2 tabs open.
When this occurs, a relaunch is required every time. Very annoying bug, and ruins the experience for me.
I had to go back to version 119.0.6045.192 (64-bit) because it seems like this is the last properly stable Supermium version which works without any issues. I dont know what you guys did, but whatever you did seems to have sort of broken both 121 and 122 versions of Supermium.
To Reproduce
I have not been able to reproduce the behavior. This truly seems random, although it might not be the case (perhaps it can be reproduced).
Expected behavior
Obviously I expect any browser or app to work without hanging/crashing/freezing etc.
Screenshots

Desktop (please complete the following information):

OS: Windows 7 SP1 x64
Supermium 122.0.6261.85 64 bit
All drivers and windows updates at latest version
User profile (User Data folder) is not "fresh", it comes from previous installations of Supermium

You can vote for this: https://github.com/win32ss/supermium/discussions/346
As fact, now it is just the "alpha preview". And not for everyday use.

Please try the latest release.

Any word on if the latest version fixes the hangs?  I am hesitate about setting it all up and getting it configured how I like just to have it still having the hanging issue.

Any word on if the latest version fixes the hangs? I am hesitate about setting it all up and getting it configured how I like just to have it still having the hanging issue.

Not sure why you need to "getting it configured" since it technically works without changing a single thing in your settings/profile.
All you do is update the actual browser files, the dir that has 122.0.6261.85 and chrome.exe in it.
Anyway,  I will update this, but it is too soon. I just tried the latest version today, and no hangs/crashes yet. But it is too soon to tell, havent been using it enough to be sure.
It looks promising so far though.

@DankiestCitra When I copied the dir that has 122.0.6261.85 and chrome.exe in it to the install of 119 some settings got reset and I needed to reinstall all the extensions I use again, the extension settings came back when they were reinstalled but it was a pain in the ass cause some of the addons I use aren't on the chrome store anymore


text:
[Feature] Reduce gas cost

https://github.com/windranger-io/windranger-mass-delegation-contracts/blob/main/contracts/MerkleDelegation.sol#L13
considering that DelegateeRecord.percentage is limited to 100_000, it can be changed to uint24. And as DelegateeRecord.delegate is address ( == uint160), then DelegateeRecord will take only 1 slot (24 + 160 < 256) instead of 2 slots, hence write and read gas will be 2 times less

Thanks, I think we can use uint64 and leave the whole number as a fraction of 2**64 in case we are delegating to more than 100,000 addresses. Also, there is a thing with precision, because we are using BigNumber off-chain and fractions on-chain we have to double check there are no discrepancies due to the hashing. If we do both on-chain and off-chain (currently on-chain only fraction is checked, not net balance, but can be added).
On-chain calculation vs Off-chain calculation
floor(delegator_balance * total_weight * 2^64 / weight_fraction_uint64) == floor(delegator_balance * weight_BigNumber / delegator_total_weight
For example, the total_weight is 100, if the delegator is splitting into 60,28,12 between 3 delegatees.

Another solution is to store the total weight also on-chain and then we have the exact BigNumber data to compare with off-chain data.

Also, the percentage or weight is only used in the verification that is a view function, so not sure it will impact gas costs.
https://github.com/windranger-io/windranger-mass-delegation-contracts/blob/jo-delegate2/contracts/MerkleDelegation.sol

authors: cyraxred joigno


text:
Vanilla libssh2 1.11.0

Untested build: https://github.com/winlibs/winlib-builder/actions/runs/10809454164
May be useful for next cURL update.
PS: just noticed that there is now libs/libssh2_static.lib which should probably be removed from the build.

Superseded by #6.


text:
Virus scanning doesn't work

Brief description of your issue
I have virus scanning on, but virus scanning doesn't work.
Steps to reproduce (optional)

Enable virus scanning with VirusTotal:

Virus scanning doesn't work

Try to do it manually:

This also doesn't work

Expected behavior (optional)
I expect the feature to work, i.e., that it scans for virii
Actual behavior (optional)
It doesn't work, no scans are performed
Environment (optional)
Windows 10 Pro x64
System Informer 3.1.24298.0 Release
OBJECT INFORMATION
PhObjectTypeObject: 22 objects
PhStringType: 5583 objects
PhBytesType: 0 objects
PhListType: 303 objects
PhPointerListType: 128 objects
PhHashtableType: 24 objects
PhFileStreamType: 0 objects
PhSymbolProviderType: 0 objects
PhProcessItemType: 239 objects
PhServiceItemType: 776 objects
PhNetworkItemType: 0 objects
PhModuleProviderType: 0 objects
PhModuleItemType: 0 objects
PhThreadProviderType: 0 objects
PhThreadItemType: 0 objects
PhHandleProviderType: 0 objects
PhHandleItemType: 0 objects
PhMemoryItemType: 0 objects
PhImageListItemType: 423 objects

Duplicate of #1783

authors: SanderBouwhuis dmex

repo: winsiderss/systeminformer


text:
custom level not work in typescript

Please tell us about your environment:

winston version?

[ ] winston@2
[x] winston@3

_node -v outputs:_v8.12.0
Operating System? macOS
Language? | TypeScript 3.1.3

What is the problem?
custom level not work in typescript 3.1.3
code

import winston from 'winston';

const myCustomLevels: winston.config.AbstractConfigSetLevels = {
  foo: 0,
  bar: 1,
  baz: 2,
  foobar: 3
};

const customLevelLogger = winston.createLogger({
  levels: myCustomLevels,
  transports: [
    new winston.transports.Console({
      level: 'foobar'
    })
  ]
});
//  [ts] Property 'foobar' does not exist on type 'Logger'.
customLevelLogger.foobar('some foobar level-ed message');

Facing the same issue. Do we need to define a custom type here or is there some other way how this can be achieved?

@sachinh19 it's work! Thanks for your reply

Another alternative is to just extend the winston.Logger interface and then cast the result of createLogger to your interface.
import winston from 'winston';

const myCustomLevels: winston.config.AbstractConfigSetLevels = {
  foo: 0,
  bar: 1,
  baz: 2,
  foobar: 3
};

interface CustomLevels extends winston.Logger {
  foo: winston.LeveledLogMethod;
  bar: winston.LeveledLogMethod;
  baz: winston.LeveledLogMethod;
  foobar: winston.LeveledLogMethod;
}

const customLevelLogger: CustomLevels = <CustomLevels>winston.createLogger({
  levels: myCustomLevels,
  transports: [
    new winston.transports.Console({
      level: 'foobar'
    })
  ]
});

customLevelLogger.foobar('some foobar level-ed message');

Both of these are nice solutions.  Not closing this yet because I think it would be a good idea to get some of these "FAQ"-type issues into some examples somewhere.  We don't have any TS-specific examples yet but maybe we can add a typescript folder under examples in the repo.  Don't want to lose this knowledge in case anyone asks about this in the future :) . @indexzero any thoughts?

If only they'd change from declare namespace to declare module...then the module could just be augmented externally. 😢

It would be even better if each logger could infer levels from the createLogger call. That means if we exclude certain common levels from the levels config, we will get the proper compile-time error if we try calling that.
For example, we could make it infer the levels in this example:
const logger = winston.createLogger({
  levels: { custom: 0 },
});

// works:
logger.custom('stuff');
logger.log('custom', 'stuff');

// compile error:
logger.info('stuff');
logger.log('info', 'stuff');

I'm happy to work on a PR when I get some free.

you could check out this answer on StackOverflow. works pretty well for my use case

authors: DABH cheerfyt dev-opus evankennedy fennecbutt jensbodal sachinh19

repo: winstonjs/winston


text:
Duplicator doesn't save materials

When duplicating props that are materialized, the materials aren't saved/pasted with the props. I don't see any errors in console when pasting.
Props that are colored using the color tool seem to be saved, though.

It only saves materials that were applied using a tool or script that calls the correct "save material" function. iirc E2 doesn't do this

Right, I'm talking about props that are materialized using the material tool.

and you're talking about Garry's Duplicator, Advanced Duplicator or Advanced Duplicator 2?

Advanced Duplicator. It's happening on my DarkRP server: 192.95.60.28:27015.

Are all of your mods up-to-date?
Does using the GitHub version change anything?
Did you try turning it off and on? :)

Doing an issue cleanup. If they come back and answer your question, they can reopen this.

authors: Anticept Divran TomyLobo timthefunnyman

repo: wiremod/advduplicator


text:
Change ReactDom.render to createRoot (React 18 render)

Fixes React 18 console warning
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead.
Until you switch to the new API, your app will behave as if it's running React 17.
Learn more: https://reactjs.org/link/switch-to-createroot

Let's wait until Slinky supports this.

authors: AlexITC KapStorm

repo: wiringbits/scala-webapp-template


text:
Can't join server when using Numismatic overhaul

I tried a modpack with this mod in it and it does not let me join servers. I confirmed this was the right mod as when I removed it from my mods folder I could join. this is the error message I get when trying to join a server "Internal Exception: io.netty.handler.codec.DecoderException: io.netty.handler.codec.EncoderException: java.io.IOException: Root tag must be a named compound tag"
latest.log

This isn't my server but it was a server people were playing on at the time so it's not the server

Also I know it is the mod as when I take just the mod off I can join servers just fine

To me this seems like an owo-networking error, as you are immediately being kicked due to some packet issue.
Numismatic Overhaul is not a serverside or clientside-only mod, and needs to be present on both the client and server you are connecting to.

OMG im so stupid I thought it was clientside and so tried to conntect to a modded minehut server but you need to go through a lobby without the mod to do that. the only problem was it was both serverside and client side

repo: wisp-forest/numismatic-overhaul


text:
i18n(zh-cn): update typescript.mdx

What kind of changes does this PR include?

updated content

Description

typescript.mdx missing part of the content.

Thanks for the PR! @szqingt
There seems to be a lot of outdated content on this page, can you update them too?

I found some, is there anything else

In technical documentation, you can use "你" instead of "您".

In technical documentation, you can use "你" instead of "您".

Is there anything else?

LGTM

authors: liruifengv szqingt

repo: withastro/docs


text:
i18n(pt-br): Translate deno.mdx

What kind of changes does this PR include?

New or updated content
Translated content

Description

Translates the Deno Integration Guide to Brazilian Portuguese

Ótimo trabalho @IgStefano, obrigado pelo PR! Adicionei algumas sugestões para você considerar purple_heart

Oi, @Yan-Thomas, obrigado pelos comentários! São pontos bem relevantes. Lamento que a minha tradução tenha dado tanto trabalho pra revisar. Vou tentar melhorar na próxima.

Oi, @Yan-Thomas, obrigado pelos comentários! São pontos bem relevantes. Lamento que a minha tradução tenha dado tanto trabalho pra revisar. Vou tentar melhorar na próxima.

Fica tranquilo! Revisões serem criteriosas faz parte e eu sou especialmente chato 😅, o trabalho foi ótimo, agradeço demais pela contribuição 🙌

authors: IgStefano Yan-Thomas


text:
ci: update error reference docs

This PR is auto-generated by a nightly GitHub action to update the error reference docs from source code in withastro/astro.

Fixing at source, to correct URLs changed by #6620 !


text:
🐛 BUG: Can't stop typescript errors

Describe the Bug
Can't stop typescript errors appearing.
Steps to Reproduce
Front matter
const array = [
  { required: '' },
  { required: '', optional: '' }
]
array[1].optional

optional is underlined in red and hovering explains error Property 'optional' does not exist on type '{ required: string; optional?: undefined; }'.ts(2339)
I tried to disable validation with "checkJs": false in jsconfig.json and "typescript.validate.enable": false in settings but it doesn't stop errors.
No error putting that code in .js file but error still in .astro file.
Using typescript is not requirement for astro so should not be required to write any typescript to stop these errors. They shouldn't appear if typescript checks are disabled.

Astro is TypeScript only at this time, TypeScript cannot be disabled.

Instead of "typescript.validate.enable": false can an extension specific setting be added to settings file disabling typescript errors in astro files? Can be people who don't want disable all typescript validation if they're writing typescript in non astro files but are writing astro as javascript (without type annotations which is valid typescript).

We'd rather make that option work if that's a possibility. Q

Is there any workaround until fixed? Disruptive for developing and causes to miss important errors because so many things are underlined in red. Even every access under Astro.locals complains with error that property doesn't exist.

@Princesseuh Can it be P1 bug? There are so many error everywhere. I can give more example. Cannot trust errors in IDE anymore because most of them are because of this extension instead of real problems with code. Trusting errors is more than nice to have I believe, it's very frustrating developer experience.

@Princesseuh Can it be P1 bug? There are so many error everywhere. I can give more example. Cannot trust errors in IDE anymore because most of them are because of this extension instead of real problems with code. Trusting errors is more than nice to have I believe, it's very frustrating developer experience.

TypeScript errors are real errors.. I'm sorry this is affecting your experience so much, but it's a niche issue, people typically use TypeScript just fine.

TypeScript errors are real errors..

This is opinion and objectively wrong. There are many example that run and build fine but this extension still complain with error. Rule of thumb is if it runs without error in astro and browser it's not an error.

it's a niche issue, people typically use TypeScript just fine

People typically use javascript just fine. It is allowed to write vanilla javascript in astro and everyone should respect right to choose for own code.

Fixed by https://github.com/volarjs/services/commit/6f13b47fc01e9999f6fa46023f80225957f421f8, we'll release an update with it soon-ish

Is it in 2.6.2?

Nope, not yet sorry. There was an unexpected delay, unfortunately. The holidays period also delayed things a fair amount. Still definitely planned, though!

Is it in 2.7.1?

Yes, it should work now!

I still have typescript errors like Property 'item' does not exist on type 'Element'. ts(2339). Is enough to set "typescript.validate.enable": false`?

@Princesseuh working for you?

Ah, it only seems to be working for certain kinds of errors, I'll take a look. Sorry for the inconvenience.

@Princesseuh can you open this issue?

I'll open an issue on the upstream project instead, since the code for this isn't in this repo

@Princesseuh where to find that issue number?

The option works for me at the moment:

authors: Princesseuh cdtut

repo: withastro/language-tools


text:
Add support for reloading the language server on config changes and manually

Changes
This add support for reloading the language server whenever tsconfig.json (and other similar files) is modified. I also added a command to manually reload the language server. This is helpful for whenever users encounter an issue where just reloading fix it (this help avoid needing to reload the entire VS Code window, which is not always pleasant to do)
The commit is a bit bigger than it should be because of formatting changes and also a small refactor removing unnecessary wrappers and abstractions. See GitHub comments on code for more info on why some changes were made
Testing
Tested manually as our tests don't cover this (not sure if it's even possible to test a VS Code extension)
Docs
No docs needed, the added command is self explanatory

Does this change (check for language server config) allow the Astro extension to work in a web environment?

Does this change (check for language server config) allow the Astro extension to work in a web environment?

I'm not sure I understand what you mean? Are you asking if this change is compatible with Astro running in web environnements?

Does this change (check for language server config) allow the Astro extension to work in a web environment?

I'm not sure I understand what you mean? Are you asking if this change is compatible with Astro running in web environnements?

Yes

When we say config are we talking about astro.config.js or the .vscode/settings.json>

When we say config are we talking about astro.config.js or the .vscode/settings.json>

The former and tsconfig.json (and jsconfig.json). The latter does not need reload since we can access the configuration directly (I believe at least, haven't checked yet)

Then I'm not sure the extension will work in something like vscode.dev, since, vscode.dev doesn't have access to a filesystem.

Then I'm not sure the extension will work in something like vscode.dev, since, vscode.dev doesn't have access to a filesystem.

It does through VSCode's API:

The opened workspace or folder is on a virtual file system. Access to workspace files needs to go through the VS Code file system API accessible at vscode.workspace.fs.

The watcher here is used through a VS Code API

Oh, cool, nvm then

authors: Princesseuh okikio


text:
Download Block (Component)

What version of starlight are you using?
0.11.0
What is your idea?
If you want to provide your users with files which are maybe not intended to be viewed but just used locally, a beautiful download button would be nice to have. I'm thinking of somethink like this:

To be more precise, it has the same dimensions as a code block, but as a content it has just the file name and a download button. Therefore, it doesn't have to look as ugly as this:

I am willing to submit a PR for this issue if someone explains to me (or provides links for me) how I can build a component. However, first we should discuss how the markdown behind this beautiful piece of art should look like or if we can combine this feature with other useful features...
Why is this feature necessary?
Make the UI more attractive...
Do you have examples of this feature in other projects?
If the code blocks look beautiful, why not make everything beautiful?
Participation

[X] I am willing to submit a pull request for this issue.

Thanks for your suggestion.
Just to clarify and make sure I understand correctly, is there any specific reason why this would need to be built-in in Starlight vs being a community package that users could install and use in their Markdown or MDX files, e.g.:
<DownloadLink href="link_to_something_to_download" />

Or not specifically but you think this is a common enough use case that it would be worth having it built-in?

Thank you for your quick response!
There is no specific reason why this needs to be built-in. I personally didn't know that there are community packages until now (although it makes a lot of sense), so maybe it's a better solution to ask the community.
I mean, it would be more convenient for me because I would use this feature commonly, but I guess that's not enough to get a built-in component... xD
Is there any specific website for community packages like crates.io for Rust crates? And where can I suggest this feature for the community? Just on discord or somewhere else?

I see, thanks for the details. I'm only speaking for myself of course, but I think this could be a great use-case for a third-party/community package.

Is there any specific website for community packages like crates.io for Rust crates?

Technically, this would be the npm registry just like Starlight itself. This means that any component can be installed using npm or your favorite package manager (e.g. npm i my-super-cool-component), imported in an MDX file (e.g. import SuperCoolComponent from 'my-super-cool-component') and used like the example I shared above.

And where can I suggest this feature for the community? Just on discord or somewhere else?

Anyone can publish a package to npm, so you can publish your own components and share them with the community if you want or just build and use them in your own projects.
If you are interested, for an example of a Starlight specific component shared as a package through npm, you can check out this one (repo) I made.

Thanks for the issue @trueberryless!
I think I agree with @HiDeoo that this is a good candidate for a community package — maybe even one you build yourself! We could then link to it in the Starlight Showcase.
One good way to start is probably to create a component you’re happy with in your own project. Then, once you’ve used it for a bit and feel it works well, you could extract it to a separate package and publish it to npm as explained by @HiDeoo.
Hope it’s OK if I close this issue as something we probably won’t add ourselves, but still happy to help explain more of these concepts or answer any questions you might have here.

authors: HiDeoo delucis trueberryless

repo: withastro/starlight


text:
i18n(ko-KR): udpate showcase.mdx

What kind of changes does this PR include?

Changes or translations of Starlight docs site content

Description
update showcase.mdx
#563

Thanks for the good point!
I tried to review hard, but this kind of mistake happens 😂


text:
Button text matching fails on Android due to default all-caps styling

Description
Starting SDK v21 (Material Design), by default, text set in native Button views appear all-caps. This is according to the guidelines, so RN doesn't provide an API to override that, and - as a matter of fact, it isn't easy to override that in native Android as well.
Therefore, looking up a button element by text using Detox API typically fails on Android while it works on iOS, since the provided text typically isn't all-caps.
Steps to Reproduce
Create a single-screen app with a single button with the text 'tap me'.
The following test code will fail:
await expect(element(by.text('tap me')).toBeVisible();

Device and verbose Detox logs
Typically error saying the element doesn't exist in the hierarchy.

After putting in some effort into solving this, here are the conclusions:

Creating and applying a custom matcher as discussed is easy.
In react native, Button components do not map to native buttons. They are just touchables with a background. See impl. here.

All in all, this makes it really hard for the custom matcher to distinguish plaintext views from "button" views. The only lead here is the accessibility roles/traits that are inherently set to "button" on the JS side. It is likely that this info is somehow propagated to the native side, but its not trivial to find out how and thus it is not a <1hr task.
(tl;dr Won't fix)

Jesus, so they hardcode the uppercase string in Android. This is why RN is terrible. 🤦♂

Yes. It's VERY unfortunate.

repo: wix/Detox


text:
App crashed and then displayed Signal 6 was raised

What happened?
Hi,
hope you are well. I'm new to detox testing and need some assistance. Since we upgrade to RN0.68.2, we been getting this signal 6 error when running IOS.
Detox can launch simulator but when it tries to log in, it hang for about 5 secs and then crashed.
I have shared the following configs/code.
config.json
{
"setupFilesAfterEnv": ["/init.js"],
"testEnvironment": "node"
}
init.js
// eslint-disable-next-line import/no-duplicates
import detox from 'detox';
import packageFile from '../package.json';
// eslint-disable-next-line import/no-duplicates
import { device } from 'detox';
const detoxConfig = packageFile.detox;
jest.setTimeout(120000);
beforeAll(async () => {
await detox.init(detoxConfig, { launchApp: false });
await device.launchApp();
});
afterAll(async () => {
await detox.cleanup();
});
jest test
import { expect, by, element } from 'detox';
describe('Testing login', () => {
it('user can successfully login', async () => {
await element(by.id('usernameInput')).typeText('username');
await element(by.id('passwordInput')).typeText('password');
await element(by.id('logInButton')).tap();
});
});
package.json
"detox": {
"testRunner": "jest",
"runnerConfig": "e2e/config.json",
"skipLegacyWorkersInjection": true,
"apps": {
"ios": {
"type": "ios.app",
"binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/something.app",
"build": "xcodebuild -workspace ios/something.xcworkspace -configuration Debug -scheme something -sdk iphonesimulator -derivedDataPath ios/build -arch x86_64 DETOX=1"
}
},
"devices": {
"simulator": {
"type": "ios.simulator",
"device": {
"type": "iPhone 11"
}
}
},
"configurations": {
"ios": {
"device": "simulator",
"app": "ios"
}
}
}
"jest": "^26.6.3",
"detox": "^19.5.7",
System:    OS: macOS 12.0
CPU: (10) x64 Apple M1 Max
Memory: 53.95 MB / 32.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.14.0/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.14.0/bin/npm
Watchman: 2022.03.21.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 27, 28, 29, 30
Build Tools: 29.0.2, 29.0.3, 30.0.3
System Images: android-29 | Intel x86 Atom_64, android-30 | Intel x86 Atom_64, android-30 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7935034
Xcode: 13.4/13F17a - /usr/bin/xcodebuild
Languages:
Java: 11.0.11 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.2 => 0.68.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
What was the expected behaviour?
Error
DetoxRuntimeError: The pending request #2 ("invoke") has been rejected due to the following error:
The app has crashed, see the details below:

Signal 6 was raised
(
	0   Detox                               0x0000000110453915 +[NSThread(DetoxUtils) dtx_demangledCallStackSymbols] + 37
	1   Detox                               0x0000000110456370 __DTXHandleCrash + 464
	2   Detox                               0x0000000110456ab1 __DTXHandleSignal + 59
	3   libsystem_platform.dylib            0x000000011338d06d _sigtramp + 29
	4   libsystem_malloc.dylib              0x0000000113014dee nanov2_allocate + 142
	5   libsystem_c.dylib                   0x00000001132436b7 abort + 130
	6   Foundation                          0x000000011252a78e +[_NSPredicateUtilities _predicateSecurityAction] + 42
	7   Foundation                          0x0000000112420dba -[NSFunctionExpression expressionValueWithObject:context:] + 958
	8   Foundation                          0x00000001123dc16f -[NSComparisonPredicate evaluateWithObject:substitutionVariables:] + 326
	9   Detox                               0x0000000110457a46 __87+[UIView(DetoxMatchers) _dtx_appendViewsRecursivelyFromArray:passingPredicate:storage:]_block_invoke + 65
	10  CoreFoundation                      0x000000011403a4a0 __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7
	11  CoreFoundation                      0x0000000113fc4732 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 224
	12  Detox                               0x0000000110457980 +[UIView(DetoxMatchers) _dtx_appendViewsRecursivelyFromArray:passingPredicate:storage:] + 185
	13  Detox                               0x0000000110457b61 +[UIView(DetoxMatchers) dtx_findViewsInWindows:passingPredicate:] + 89
	14  Detox                               0x0000000110457d6d +[UIView(DetoxMatchers) dtx_findViewsInKeySceneWindowsPassingPredicate:] + 144
	15  Detox                               0x00000001104733c6 Detox.Element.(views in _14E24C92C1353FEA1FC68E698CB917EF).getter : Swift.Array<__C.NSObject> + 214
	16  Detox                               0x00000001104736f2 Detox.Element.(view in _14E24C92C1353FEA1FC68E698CB917EF).getter : __C.NSObject + 50
	17  Detox                               0x0000000110465e0a merged Detox.TypeTextAction.perform(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> + 138
	18  Detox                               0x0000000110465d59 vtable thunk for Detox.Action.(perform in _04ABBB5C7C570871DB67625EF38728EC)(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> dispatching to Detox.TypeTextAction.perform(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> + 9
	19  Detox                               0x0000000110464990 Detox.Action.(perform in _04ABBB5C7C570871DB67625EF38728EC)(on: Detox.Element, completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 32
	20  Detox                               0x000000011046a08b partial apply forwarder for closure #1 () -> () in Detox.Action.perform(completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 43
	21  Detox                               0x000000011046a0d1 partial apply forwarder for reabstraction thunk helper from @callee_guaranteed () -> () to @escaping @callee_guaranteed () -> () + 17
	22  Detox                               0x0000000110466dfe reabstraction thunk helper from @escaping @callee_guaranteed () -> () to @escaping @callee_unowned @convention(block) () -> () + 14
	23  Detox                               0x0000000110460140 +[DTXAssertionHandler try:error:] + 47
	24  Detox                               0x0000000110464aa1 Detox.Action.perform(completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 241
	25  Detox                               0x00000001104716ba function signature specialization <Arg[1] = Dead, Arg[2] = Owned To Guaranteed, Arg[3] = Owned To Guaranteed> of function signature specialization <Arg[1] = [Closure Propagated : closure #1 (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> () in closure #2 () -> () in Detox.DetoxManager.webSocket(_: Detox.WebSocket, didReceiveAction: Swift.String, params: Swift.Dictionary<Swift.String, Any>, messageId: __C.NSNumber) -> (), Argument Types : [Detox.DetoxManager__C.NSNumber]> of static Detox.InvocationManager.invoke(dictionaryRepresentation: Swift.Dictionary<Swift.String, Any>, completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 954
	26  Detox                               0x000000011048b621 partial apply forwarder for closure #2 () -> () in Detox.DetoxManager.webSocket(_: Detox.WebSocket, didReceiveAction: Swift.String, params: Swift.Dictionary<Swift.String, Any>, messageId: __C.NSNumber) -> () + 65
	27  Detox                               0x0000000110466dfe reabstraction thunk helper from @escaping @callee_guaranteed () -> () to @escaping @callee_unowned @convention(block) () -> () + 14

Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 19.5.7
React Native version: 0.68.2
Node version: 16.14.0
Device model:
iOS version:
macOS version: macOS 12.0
Xcode version: 13.4
Test-runner (select one): jest
Detox logs
Detox logs
paste logs here!

DetoxRuntimeError: The pending request #2 ("invoke") has been rejected due to the following error:
The app has crashed, see the details below:

Signal 6 was raised
(
	0   Detox                               0x0000000110453915 +[NSThread(DetoxUtils) dtx_demangledCallStackSymbols] + 37
	1   Detox                               0x0000000110456370 __DTXHandleCrash + 464
	2   Detox                               0x0000000110456ab1 __DTXHandleSignal + 59
	3   libsystem_platform.dylib            0x000000011338d06d _sigtramp + 29
	4   libsystem_malloc.dylib              0x0000000113014dee nanov2_allocate + 142
	5   libsystem_c.dylib                   0x00000001132436b7 abort + 130
	6   Foundation                          0x000000011252a78e +[_NSPredicateUtilities _predicateSecurityAction] + 42
	7   Foundation                          0x0000000112420dba -[NSFunctionExpression expressionValueWithObject:context:] + 958
	8   Foundation                          0x00000001123dc16f -[NSComparisonPredicate evaluateWithObject:substitutionVariables:] + 326
	9   Detox                               0x0000000110457a46 __87+[UIView(DetoxMatchers) _dtx_appendViewsRecursivelyFromArray:passingPredicate:storage:]_block_invoke + 65
	10  CoreFoundation                      0x000000011403a4a0 __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7
	11  CoreFoundation                      0x0000000113fc4732 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 224
	12  Detox                               0x0000000110457980 +[UIView(DetoxMatchers) _dtx_appendViewsRecursivelyFromArray:passingPredicate:storage:] + 185
	13  Detox                               0x0000000110457b61 +[UIView(DetoxMatchers) dtx_findViewsInWindows:passingPredicate:] + 89
	14  Detox                               0x0000000110457d6d +[UIView(DetoxMatchers) dtx_findViewsInKeySceneWindowsPassingPredicate:] + 144
	15  Detox                               0x00000001104733c6 Detox.Element.(views in _14E24C92C1353FEA1FC68E698CB917EF).getter : Swift.Array<__C.NSObject> + 214
	16  Detox                               0x00000001104736f2 Detox.Element.(view in _14E24C92C1353FEA1FC68E698CB917EF).getter : __C.NSObject + 50
	17  Detox                               0x0000000110465e0a merged Detox.TypeTextAction.perform(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> + 138
	18  Detox                               0x0000000110465d59 vtable thunk for Detox.Action.(perform in _04ABBB5C7C570871DB67625EF38728EC)(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> dispatching to Detox.TypeTextAction.perform(on: Detox.Element) -> Swift.Optional<Swift.Dictionary<Swift.String, Any>> + 9
	19  Detox                               0x0000000110464990 Detox.Action.(perform in _04ABBB5C7C570871DB67625EF38728EC)(on: Detox.Element, completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 32
	20  Detox                               0x000000011046a08b partial apply forwarder for closure #1 () -> () in Detox.Action.perform(completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 43
	21  Detox                               0x000000011046a0d1 partial apply forwarder for reabstraction thunk helper from @callee_guaranteed () -> () to @escaping @callee_guaranteed () -> () + 17
	22  Detox                               0x0000000110466dfe reabstraction thunk helper from @escaping @callee_guaranteed () -> () to @escaping @callee_unowned @convention(block) () -> () + 14
	23  Detox                               0x0000000110460140 +[DTXAssertionHandler try:error:] + 47
	24  Detox                               0x0000000110464aa1 Detox.Action.perform(completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 241
	25  Detox                               0x00000001104716ba function signature specialization <Arg[1] = Dead, Arg[2] = Owned To Guaranteed, Arg[3] = Owned To Guaranteed> of function signature specialization <Arg[1] = [Closure Propagated : closure #1 (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> () in closure #2 () -> () in Detox.DetoxManager.webSocket(_: Detox.WebSocket, didReceiveAction: Swift.String, params: Swift.Dictionary<Swift.String, Any>, messageId: __C.NSNumber) -> (), Argument Types : [Detox.DetoxManager__C.NSNumber]> of static Detox.InvocationManager.invoke(dictionaryRepresentation: Swift.Dictionary<Swift.String, Any>, completionHandler: (Swift.Optional<Swift.Dictionary<Swift.String, Any>>, Swift.Optional<Swift.Error>) -> ()) -> () + 954
	26  Detox                               0x000000011048b621 partial apply forwarder for closure #2 () -> () in Detox.DetoxManager.webSocket(_: Detox.WebSocket, didReceiveAction: Swift.String, params: Swift.Dictionary<Swift.String, Any>, messageId: __C.NSNumber) -> () + 65
	27  Detox                               0x0000000110466dfe reabstraction thunk helper from @escaping @callee_guaranteed () -> () to @escaping @callee_unowned @convention(block) () -> () + 14
	28  DetoxSync                           0x0000000133f6d0c4 __36+[DTXSyncManager _tryIdleBlocksNow:]_block_invoke.128 + 184
	29  libdispatch.dylib                   0x00000001131368e4 _dispatch_call_block_and_release + 12
	30  libdispatch.dylib                   0x0000000113137b25 _dispatch_client_callout + 8
	31  libdispatch.dylib                   0x0000000113145043 _dispatch_main_queue_drain + 1050
	32  libdispatch.dylib                   0x0000000113144c1b _dispatch_main_queue_callback_4CF + 31
	33  CoreFoundation                      0x0000000114036ed5 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
	34  CoreFoundation                      0x00000001140316ca __CFRunLoopRun + 2761
	35  CoreFoundation                      0x0000000114030704 CFRunLoopRunSpecific + 562
	36  GraphicsServices                    0x000000011816cc8e GSEventRunModal + 139
	37  UIKitCore                           0x00000001281e365a -[UIApplication _run] + 928
	38  DetoxSync                           0x0000000133f68a52 __detox_sync_UIApplication_run + 362
	39  UIKitCore                           0x00000001281e82b5 UIApplicationMain + 101
	40  BetfairMobile                       0x000000010490b388 main + 104
	41  dyld                                0x000000010ff8af21 start_sim + 10
	42  ???                                 0x0000000207a4d4d5 0x0 + 8718177493
	43  ???                                 0x0000000000000003 0x0 + 3
)

Device logs
Device logs
paste logs here!

More data, please!
No response

@sivvoy please upgrade Detox to the latest version (19.7), this issue has been fixed there. See release notes.

I'm closing this issue because this bug has already been fixed.
Please let me know if you experience any additional issues with the latest version of Detox.

Thank you, I've upgrade and its all working. Thank you

authors: asafkorem sivvoy


text:
Simulator not lauching on CI workflow with Expo

Description
Hello there,
I am working on a mobile application with expo SDK 50, react-native@0.73.3 and I am using Detox for my e2e tests. It used to work well on Github Actions, but it seems that my action these days has trouble to find a simulator to run the tests.
NB: tests run perfectly locally, the issue occurs on CI only.
  DetoxRuntimeError: Failed to find a device by type = "iPhone 15 Pro Max"

    HINT: Run 'applesimutils --list' to list your supported devices. It is advised only to specify a device type, e.g., "iPhone Xʀ" and avoid explicit search by OS version.

I took a look to the react-native example on wix/detox repo to have an idea of the right configuration for my .detoxrc.js and ended to this chunk for iOS sim :
devices: {
  simulator: {
    type: 'ios.simulator',
    device: {
      type: 'iPhone 15 Pro Max',
      os: '17.2'
    },
  },
},

My yml file is as code below. I am not giving any configuration for the simulator, but I don't know if it's needed as long as I never saw something like that on Detox documentation or examples.
name: e2e-ios
on:
  push:
    branches:
      - main
      - 'SPA-**'
      - 'FEATURE-**'

jobs:
  e2e-ios:
    runs-on: macos-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v3

      - name: Setup Node.js
        uses: actions/setup-node@v3

      - name: Install Yarn dependencies
        run: yarn --frozen-lockfile --prefer-offline

      - name: Install macOS dependencies
        run: |
          brew tap wix/brew
          brew install applesimutils
        env:
          HOMEBREW_NO_AUTO_UPDATE: 1
          HOMEBREW_NO_INSTALL_CLEANUP: 1

      - name: Setup Ruby
        uses: ruby/setup-ruby@v1
        with:
          ruby-version: 3.2
          bundler-cache: true

      - name: Expo pre-build
        run: npx expo prebuild -p ios

      - name: Install Detox
        run: |
          yarn global add detox-cli
          yarn add detox

      - name: Detox rebuild framework cache
        run: yarn detox rebuild-framework-cache

      # - name: Cache Detox build # needed ?
      #   id: cache-detox-build
      #   uses: actions/cache@v3
      #   with:
      #     path: ios/build # WARNING : right here ??
      #     key: ${{ runner.os }}-detox-build
      #     restore-keys: |
      #       ${{ runner.os }}-detox-build

      - name: Detox build
        run: MY_APP_MODE=mocked detox build -c ios.sim.release

      - name: Detox test
        run: MY_APP_MODE=mocked detox test -c ios.sim.release --cleanup

      - name: Upload artifacts # what are those ?
        if: failure()
        uses: actions/upload-artifact@v3
        with:
          name: detox-artifacts
          path: artifacts

Maybe I am missing something obvious here, but please tell me if you need more information or details about my code.
Thank your for your help, I'll be pleased to discuss further with you on this subject.
Your environment
Detox version: 20.13.5
React Native version: 0.73.3
Node version: 20.7.0
Device model: Macbook Air M1, 2020
OS: Sonoma 14.0
Test-runner (select one): jest

Hi @brpinto,
We were facing the same issue. Sees there is an issue with the new default image which is macos-ventura-13.6-xcode-15.2 probably related to xcode 15.2 and detox incompatibility? To get round th e iss wr specifiedmacos-ventura-13.4-xcode-14.3.1  in eas.json
i.e.
"ios": {
        "simulator": true,
        "image": "macos-ventura-13.4-xcode-14.3.1",
        "cocoapods": "1.14.3"
},

Note in our particular situaltion we had specify cocoapods": "1.14.3" has the new version of one of the pods was incompatible with the 14.3.1 image

We're also experiencing something similar on GitHub Actions, with the macos-13 runner:
Fails on iOS Detox tests with:
pnpm detox test --configuration ios
11:25:07.073 detox[23852] B jest --config ./e2e/jest.config.cjs e2e
FAIL e2e/appStarts.e2e.ts
  ● Test suite failed to run

    DetoxRuntimeError: Failed to find a device by type = "iPhone 13 Pro"

    HINT: Run 'applesimutils --list' to list your supported devices. It is advised only to specify a device type, e.g., "iPhone Xʀ" and avoid explicit search by OS version.

      at SimulatorAllocDriver._queryDevices (node_modules/detox/src/devices/allocation/drivers/ios/SimulatorAllocDriver.js:177:13)
      at async SimulatorAllocDriver._groupDevicesByStatus (node_modules/detox/src/devices/allocation/drivers/ios/SimulatorAllocDriver.js:150:27)
      at async SimulatorAllocDriver._findOrCreateDevice (node_modules/detox/src/devices/allocation/drivers/ios/SimulatorAllocDriver.js:119:29)
      at async /Users/runner/work/hotline-bling-codealong/hotline-bling-codealong/node_modules/detox/src/devices/allocation/drivers/ios/SimulatorAllocDriver.js:43:14
      at async safeAsync (node_modules/detox/src/utils/safeAsync.js:4:13)
      at async /Users/runner/work/hotline-bling-codealong/hotline-bling-codealong/node_modules/detox/src/devices/allocation/DeviceRegistry.js:[6](https://github.com/upleveled/hotline-bling-codealong/actions/runs/7948582784/job/21698753711?pr=193#step:11:7)2:24
      at async ExclusiveLockfile.exclusively (node_modules/detox/src/utils/ExclusiveLockfile.js:41:15)
      at async SimulatorAllocDriver.allocate (node_modules/detox/src/devices/allocation/drivers/ios/SimulatorAllocDriver.js:42:18)
      at async /Users/runner/work/hotline-bling-codealong/hotline-bling-codealong/node_modules/detox/src/devices/allocation/DeviceAllocator.js:3[7](https://github.com/upleveled/hotline-bling-codealong/actions/runs/7948582784/job/21698753711?pr=193#step:11:8):[22](https://github.com/upleveled/hotline-bling-codealong/actions/runs/7948582784/job/21698753711?pr=193#step:11:23)

Ohh thanks for the link, didn't know this information was documented, thank! I'll try iPhone 14 Pro.

Hey @karlhorky, I noticed that your job is now passing with an iPhone 14 Pro simulator.
What is currently struggling me is the time that takes detox to assign a test after it starts, It takes almost 8min in your case (10min for the project I working on), It was way shorter on macos-12, is this a regression? Does anyone know what can cause this?
14:16:17.451 detox[13467] B jest --config ./e2e/jest.config.cjs e2e
14:24:06.68 detox[13468] i appStarts.e2e.ts is assigned to 5B1B6B4F-C3E2-4D8B-A768-777D9C04EF15 (iPhone 14 Pro)

I'm not sure what the cause of that would be (maybe indeed a regression in Detox?) but here are my numbers:

detox test on macos-12: 2m 46s
detox test on macos-13: 8m 24s

authors: ashermja brpinto eliottparis karlhorky


text:
feat(types): add function toHaveToggleValue

[x] This is a small change
[ ] This change has been discussed in issue #<?> and the solution has been agreed upon with maintainers.

Description:

Added missing function toHaveToggleValue to Expect interface.
Fix some typos in index.d.ts file.

@arendruni, thanks a lot for noticing this and taking the time to jot a PR.
Meanwhile, the master is broken due to a transitive dependency change — I'll merge when it is back to green.

@arendruni, merged. Probably we'll release the next version tomorrow or on Monday — thanks in advance for the patience.

authors: arendruni noomorph


text:
npm run build takes ages making development very difficult

add a flag in the developer scripts that will remove clean to make it faster, or avoid compiling the native

Improved with #03b0988
@rotemmiz Is making changes so that run build will not have to be called for each JS change.

authors: LeoNatan talkol

repo: wix/detox


text:
Add check for ungenerated code

We had at times updates of the source for code generation not being reflected in the adapters as the code was not generated again. Let's add a check for this here 👍

@rotemmiz added error message, could you review it again?

@rotemmiz I understood that we wanted to use prettier in our project, so I thought adding it to the generated code too makes sense. I think we are doing a suboptimal job enforcing it, I would offer to help with that. The mockserver I am currently writing enforces it with the help of jest, which I like very much, you can see the config here.
I found this quote on a podcast I listen to (freely quoted as I don't remember when they said it):

Prettier reformats your code to look worse, but at the same time it makes your co-workers code much more readable.

This resonated a lot with me, I think everyone has an opinion on how code should be looking like for whatever (totally) reasons. prettier frees us from having to have conversations about how it should look like, it just always looks the same, freeing up brain cycles for more important tasks 😇

You're right but I still really don't like these formatting choices. It makes the code longer (in lines), and very weirdly formatted.
I would want to explore it there are different "flavors" tho this formatting before running it on the whole project. I do like ESLint's defaults much better.
Sorry for delaying this for too long, but these formatting chocices made by prettier really hurt my eyes.

Prettier has a nice playground and at the bottom left corner there is a "Show Options" button where you can play with the options until you like the output ;)

@rotemmiz I think we are there now, please take another look 🙏
Might make sense to go over it commit by commit as the changeset is quite big due to prettier being unleashed on the generated code

I hate this argument as well, but please use spaces. Tabs make it much harder to read on GitHub, and we spend a lot of time reviewing here

Unfortunately, I can't do much about it. I add a leadingComments entry for the comment in babel, which means "insert the comment before this node", leading to the output you see. So my options are either

Go into babel and "fix" the leadingComments behaviour
Go into prettier and enable it to prettify this situation
Go with a hack solution (String replacement of the final output)
Let it be like this

4

Okay :)

@rotemmiz Could you give a final review here? 😇

@rotemmiz I removed prettier from the generated code (only applied the new style to the code generation). I opened an issue at prettier/prettier#4465 let's see if we can get any help there. I might investigate if there is a quick fix within prettier that doesn't take too long.

@DanielMSchmidt can you please take a look, seems like the build is broken due to this change.
https://travis-ci.org/wix/detox/jobs/378118106#L657

Yay, the check works. But damn, need to fix them 😂 will do that asap and ping you :)

authors: DanielMSchmidt rotemmiz


text:
ios instructions should have NotificationsIOS.consumeBackgroundQueue()

couldn't get any notifications (like onNotificationReceivedBackground() for example)
until I added this in my constructor
NotificationsIOS.requestPermissions();
NotificationsIOS.consumeBackgroundQueue();  // added

This is PRETTY CRITICAL, I've spent 2 days scratching my head trying to figure out why the library wasn't working on iOs, until I added the two lines from @roocell .
This should be in the documentation.
Thanks.

@roocell @ChakirMrabet either one of you can modify the doc and put in a pull request!

authors: ChakirMrabet allthetime roocell

repo: wix/react-native-notifications


text:
resolveExtends complodes when resolving a class that doesn't extend

Should return an array of only the class symbol itself.
Instead returns:
TypeError: Cannot read property '_kind' of undefined
Which isn't nice.

To recreate, use this css:
.baga
And try to resolve baga

Fixed by @qballer

repo: wixplosives/stylable-intelligence


text:
UI: Add optional setting for number of blocks vs time remaining for recovery path

I was kicking the tires on Liana via regtest and the "16 hours left before first recovery path becomes available" message isn't really all that useful if the chain isn't moving.
Obviously regtest doesn't move unless you tell it to, so my request is: Can you folks to add back in the "in X blocks" version of recovery path estimation as an optional display format?  Not a huge deal (it can be worked out with the info available, such as by clicking on specific items in Coins), but having it in the main page would be really convenient for testing.

related (duplicate) to #1161

My mistake. Sorry!

authors: pythcoiner schmitmd

repo: wizardsardine/liana


text:
Is it possible to declare NSURLIsExcludedFromBackupKey when using fs.mkdir()

I don't see this documented or in the source. Is there any way to do this after the fact?
If not, would you accept a PR for this? I'm thinking an optional options that could be passed to fs.mkdir(path: String, options: Object?). I'm not familiar with Android, so I'm not sure if there is something equivalent to this flag but if not the object could just be ignored there.
fs.mkdir('/some/path', { NSURLIsExcludedFromBackupKey: true })
Thoughts?

@aforty , there's no way to do this so far, it'd be great if you can make a PR 😄

@aforty , I've added an IOS only API RNFetchBlob.ios.excludeFromBackupKey, please upgrade to 0.10.2-beta.8 to verify it.


text:
Error calling RCTDeviceEventEmitter.emit failed to create value from json

Here is my file downloading code as below -
async downloadFile(fileURL) {
    const timeout = new Promise((resolve, reject) => {
      setTimeout(reject, 5000, "Request timed out");
    });

    **_const request = fetch(fileURL);_**

    return Promise.race([timeout, request])
      .then(response => {
        // alert(JSON.stringify(response, null, 4));
        if (response.status !== 404) {
          var filename = fileURL.substring(fileURL.lastIndexOf("/") + 1);

          const { config, fs } = RNFetchBlob;
          let DownloadDir = fs.dirs.DownloadDir;
          let options = {
            fileCache: true,
            addAndroidDownloads: {
              useDownloadManager: true, // setting it to true will use the device's native download manager and will be shown in the notification bar.
              notification: false,
              path: DownloadDir + "/MyApp/" + filename, // this is the path where your downloaded file will live in
              description: "Downloading Payslip."
            }
          };
          RNFetchBlob.config(options)
            .fetch("GET", fileURL, {})
            .then(res => {
              // the path should be dirs.DocumentDir + 'path-to-file.anything'
              alert("The file saved to " + res.path());
            })
            .catch((errorMessage, statusCode) => {
              // This is never hit for a server 404 error
              console.log(errorMessage, statusCode);
              Alert.alert(
                "MyApp",
                "Payslip not available.",
                [{ text: "OK" }],
                { cancelable: true }
              );
            });
        } else {
          Alert.alert(
            "MyApp",
            "Payslip not available.",
            [{ text: "OK" }],
            { cancelable: true }
          );
        }
      })
      .catch(error => {
        Alert.alert(
          "MyApp",
          "Payslip not available.",
          [{ text: "OK" }],
          {
            cancelable: true
          }
        );
      });

    return;
  }

I am getting the above error on the highlighted line , i.e, as below

const request = fetch(fileURL);

The error, I am getting in log is as follow -

07-25 10:44:15.128 9695-9732/com.MyApp E/unknown:ReactNative: Exception in native call
    java.lang.RuntimeException: Error calling RCTDeviceEventEmitter.emit
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:789)
        at android.os.Handler.dispatchMessage(Handler.java:98)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
        at android.os.Looper.loop(Looper.java:164)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:192)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: com.facebook.jni.CppException: Failed to create Value from JSON:
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:789)
        at android.os.Handler.dispatchMessage(Handler.java:98)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
        at android.os.Looper.loop(Looper.java:164)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:192)
        at java.lang.Thread.run(Thread.java:764)

I double-checked the url and it seems fine, and file is getting downloaded as well.

Hello,
What is your problem? and how can you fix it?
Can you share information @NarendraSingh88 :)