Update peer dependencies to allow React 17

Fixes #1616

[x] The existing test suites (npm test) all pass
[x] Format your code with prettier (yarn run prettier).
[x] Run the Flow typechecks (yarn run typecheck).

Tested manually of course. And we're using react-virtualized + react 17 in production for quite a while now

Tested manually of course. And we're using react-virtualized + react 17 in production for quite a while now

Bump to get this pushed through. Thanks!

Bump. This would help a lot, thanks.

any updates on this, would be super helpfull :)

Is this library still being updated? As judging from the PRs dating months and months back, nobody is doing anything. I want to submit a PR as well but seeing the progress seems like a time consuming task

@bvaughn is there any chance we can get this in?

hey! can we get an update?

hey @yamadapc. @bvaughn seem to not be actively doing stuff only more. Is there a chance you can merge this?

Bump. This would help a lot, thanks.

@wuweiweiwu  Thank you for merging it . Is there a timeline on when it would be released ?

@wuweiweiwu Could you release a new version with these changes, please? :-)

Still blocked without this. A release with this is greatly appreciated.

Would be awesome to get a release for this, now in 2022 with React 18 already released 🙏

Please release it <3

Bump for release


Task name not showing correct element in UI

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Sep 20, 2020, 07:27
One of our most frequently regressing problems has appeared once again.
Testing the latest port of freedesktop-sdk with master today I observed the following:
[--:--:--][f7ebac9b][   build:bootstrap/build/gcc-stage1.bst] START   freedesktop-sdk/bootstrap-build-gcc-stage1/f7ebac9b-build.4071769.log
[--:--:--][f7ebac9b][   build:bootstrap/gnu-config.bst      ] STATUS  Staging bootstrap/gnu-config.bst/41de65c5
[--:--:--][f7ebac9b][   build:bootstrap/build/base-sdk/filtered.bst] STATUS  Staging bootstrap/build/base-sdk/filtered.bst/5747e62f
[--:--:--][f7ebac9b][   build:bootstrap/build/base-sdk/symlinks.bst] STATUS  Staging bootstrap/build/base-sdk/symlinks.bst/b4e168e0
[--:--:--][f7ebac9b][   build:bootstrap/build/base-sdk.bst  ] STATUS  Staging bootstrap/build/base-sdk.bst/36b8498b
[--:--:--][f7ebac9b][   build:bootstrap/build/binutils-stage1.bst] STATUS  Staging bootstrap/build/binutils-stage1.bst/8f278972

Here we can see that we are staging a bunch of elements in order to build bootstrap/build/gcc-stage1.bst.
Note:

The cache key of gcc-stage1.bst is correctly printed for all lines
The message content shows the correct elements being staged
The element name shown in the UI is incorrect

Even though we issue log messages on dependency elements, we are supposed to be stamping those messages with the task_id
The frontend is supposed to favor the task_id to print the element name here if one is present, instead of the plugin_id

As a secondary note, I think that these messages are supposed to be silent_nested=True, I think this is a bit overly verbose.

In GitLab by [Gitlab user @tristanvb] on Sep 21, 2020, 09:10
This appears to be a regression from 0026e37918998addb61d7cefcbb9b5f7f6f7b4f4 in !1500

In GitLab by [Gitlab user @tristanvb] on Sep 21, 2020, 10:05
mentioned in commit 0ac455d173efbb08e5e9846d2221d070911b789b

In GitLab by [Gitlab user @tristanvb] on Sep 23, 2020, 07:43
mentioned in commit 4ee9df9a80ab0a0c4515e4e4274b3ba309e6b2ef

In GitLab by [Gitlab user @tristanvb] on Sep 23, 2020, 11:39
mentioned in commit 28762fe5dbc15440bbc64dcc69a2a111929d1b67

In GitLab by [Gitlab user @tristanvb] on Sep 24, 2020, 12:13
mentioned in commit e399c00dd981e214c81a32c676b9c373139307bc

In GitLab by [Gitlab user @tristanvb] on Sep 25, 2020, 08:02
mentioned in commit 136e8699d91ac2511816e3d451624555192ae720

In GitLab by [Gitlab user @tristanvb] on Oct 1, 2020, 09:02
mentioned in commit 4d6a9f7fa28d3e7c375fe3e9128fab230326ff2e

In GitLab by [Gitlab user @tristanvb] on Oct 25, 2020, 07:38
mentioned in commit 3729e39ec3c57aa0469227cd8d50d0e477bcaa7d

In GitLab by [Gitlab user @tristanvb] on Oct 26, 2020, 08:54
mentioned in commit 903365a82b414574b408d2834d8e10f9aa88f2d0

In GitLab by [Gitlab user @tristanvb] on Oct 27, 2020, 08:29
mentioned in commit 35865a4d7b1529cffc78caa3d26c261de8839c96

In GitLab by [Gitlab user @tristanvb] on Oct 27, 2020, 08:46
mentioned in commit 13feafdcf23a674c3eebee59aa5ce991dd6175fe

In GitLab by [Gitlab user @juergbi] on Oct 27, 2020, 09:01
mentioned in commit 655d6c60b982067daf09687e86fd055d11301a11

In GitLab by [Gitlab user @tristanvb] on Oct 27, 2020, 09:17
mentioned in commit f083c0e45996164a82978589192a395ad40d2b27

In GitLab by [Gitlab user @marge-bot123] on Oct 27, 2020, 11:26
mentioned in commit a39b57ada4302d2835ccc2bd8e23d191402da275


Figure out if it's possible to run chrooted or unpriviledged

Saw this over at reddit and thought it was worth nailing down.
https://www.reddit.com/r/codius/comments/8t2h17/simple_script_to_install_codius/

Thanks man , I havn't test it againts an non root user but I think at least users should have ability to run commands as root ( sudo) to the services and install required packages
also the current user should be replace with root in moneyd, codius services
https://github.com/xrp-community/codius-install/blob/master/codius-install.sh#L437
https://github.com/xrp-community/codius-install/blob/master/codius-install.sh#L481

I'm thinking it makes sense to create a user for the service.
Also, I'm not dictating here. I'm just throwing out what I think could be useful. Anyone is free to shoot this full of holes.
I believe the same way nginx often runs as nginx or apache runs as apache. The services could run like this.
This is a bit verbose but to be very specific I'll lay it out like this:
hyperd should run as hyperd with a group called codius.
nginx should run as nginx (or www) with a group called codius.
codiusd should runs as codiusd with a group called codius.
moneyd-xrp should run as moneyd with a group called codius.
All of these users should be unprivileged (no sudoer/root privs) anything that needs to interoperate between the services could use the group access (currently I think they only communicate through listening ports so I doubt this will be needed).

We should definitely use whatever requires the least privileges, but it's worth noting that codiusd needs access to add network devices and I believe hyperd also needs root access for certain tasks. The safest thing is to have a machine completely dedicated to codius so that if someone breaks into the machine they wouldn't disrupt anything except the codius host

@sharafian - I think the primary issue was related to the individual services all being run as root.
I am imagining it will just take some iterating and policy configurations to lock these down.
@N3TC4T - I'm willing to help out with this effort when I've gotten my own Codius project nailed down. (I think, in a few weeks I could contribute some time to this).


implemented the main use case of answering questions in a game by..

updating the game DAI, input/output boundary, controller, state, view model and adding new game and questionAnswer entities. The view files are just sample to help in coding, no need to merge it

great pr!!!!!!


[mbedtls] upgrade to 2.6.1

mbedTLS release notes:

2.4.2
2.5.1
2.6.0

@hubertmis, thanks for validating this PR!


No explaination

[Enter feedback here]
The doc is great for setting up the RD Gateway role but in what scenarios or why would we need to set up that role. There is no explanation on why would we need to do this.

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

ID: 8c48acc6-21e6-2569-7c4b-ec102783ad8d
Version Independent ID: db92ab59-ec03-5eb2-d2e7-8cfd24f5c713
Content: Deploy RD Gateway role Windows Virtual Desktop - Azure
Content Source: articles/virtual-desktop/rd-gateway-role.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@cshea15 - Thanks for brining this to our attention. We will investigate it further and update you shortly.

@cshea15 - Thanks for brining this to our attention. We will investigate it further and update you shortly.

@cshea15 - This product is in Public Preview and we have added this in our backlog to get the document updated.
Thanks again for bringing this to our attention. Once the doc is updated it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@Heidilohr

@cshea15 - This product is in Public Preview and we have added this in our backlog to get the document updated.
Thanks again for bringing this to our attention. Once the doc is updated it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@Heidilohr


not working

Type: Bug
not working vs code means it repeatedly says that lauch.sjon
VS Code version: Code 1.80.0 (660393deaaa6d1996740ff4880f1bad43768c814, 2023-07-04T15:06:02.407Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 5700U with Radeon Graphics          (16 x 1797)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.37GB (8.42GB free)

Process Argv
--crash-reporter-id 990c8c90-3778-4b82-8029-9d8e294388a7

Screen Reader
no

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

include-autocomplete
ajs
0.0.4

htmlplay
bia
0.0.10

vscode-eslint
dba
2.4.2

prettier-vscode
esb
9.19.0

vscode-debug-launcher
fab
2.1.0

auto-close-tag
for
0.5.14

code-runner
for
0.12.0

codespaces
Git
1.14.9

cpptask
kay
0.0.1

data-workspace-vscode
ms-
0.5.0

mssql
ms-
1.19.1

sql-bindings-vscode
ms-
0.4.0

sql-database-projects-vscode
ms-
1.1.1

cmake-tools
ms-
1.14.34

cpptools-extension-pack
ms-
1.3.0

LiveServer
rit
5.7.9

cmake
twx
0.0.17

c-cpp-flag-debugging
uts
0.0.1

vscode-lldb
vad
1.9.2

vscode-java-debug
vsc
0.52.0

php-debug
xde
1.32.1

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30776702
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
hideindicator:30766889
pythongtdpath:30769146
i26e3531:30780429
pythonnosm12tcf:30779713
pythonidxpt:30784022
pythonnocebcf:30776496

Please be more specific. What does it repeatedly say about (presumably) launch.json? How does it "not work"? Does it close, are you blocked?

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Request for Symfony 5.4 Compatibility and Release of a Stable Version

Hello,

Compatibility with Symfony 5.4: Currently, I am working on a project that uses Symfony 5.4. I've found your package to be quite useful and would love to integrate it into my project. However, I noticed that it does not explicitly state compatibility with Symfony 5.4. Could you please confirm if it's compatible with Symfony 5.4 or update it accordingly?

Release of a Stable Version: When trying to install your package via Composer, I encountered an issue where Composer indicates that the package cannot be installed due to it not matching the minimum-stability requirement (stable). It would be immensely helpful if a stable version of the package could be released.

Hello, thank you for your interest in this package!
I've created a 1.0.0 release based on the current commit.
About Symfony 5.4 I haven't tested it, I'll try to test and make necessary changes in the coming weeks. In the meantime if you want to open a PR to address this issue please do so, any help is welcome!


[DBAAS-58] Updated the operator per the API doc

Description
Updated the apis and controllers per the updated API doc.
And updated the operator to use operator-sdk 1.8.0.
Verification Steps

N/A
Type of change

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

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[x] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

This PR includes the changes from https://github.com/RHEcosystemAppEng/dbaas-operator/pull/11


Update threader3000.py

line 91:  nmap = "nmap -p{ports} -sV -sC -T4 -Pn -oA {ip} {ip}".format(ports=",".join(discovered_ports), ip=target)
in this line {ip} has been coded two times
line :112    os.system(nmap)
here nmap will scan same ip two times
I think this is the right one.
nmap = "nmap -p{ports} -sV -sC -T4 -Pn -oA {ip} ".format(ports=",".join(discovered_ports), ip=target)

Your assumption is incorrect. The first {ip} is used for output files named after the target IP, marked by the -oA flag.
The second is what tells nmap the target to scan.

Ok , sorry for the inconvenience, thanks for the guide
On Thu, 14 Apr, 2022, 6:12 pm Joe Helle, @.***> wrote:

Closed #13 https://github.com/dievus/threader3000/pull/13.
—
Reply to this email directly, view it on GitHub
https://github.com/dievus/threader3000/pull/13#event-6434288523, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGG7FE2VXGH64PU5XGJIWTVFAHCJANCNFSM5TNRQEYA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Angular debugging experience is not good, Any help ?

I am not able to debug the angular code like I can do from local install. Am I missing something here.
I first tried on windows and it's showing me too many symbolic links so I test it on ubuntu. On Ubuntu I create a new project and put npm install -g @angular/cli in postcreatedcommand and I am ready to use angular in container.
I am able to do use it properly for coding. Now today I debug it by putting debugger in code and see code in firefox dev tool (I do use chrome and debuggin component to debug code).
I am not able to see anything. the tab is stuck on debugging but nothing came on tool like we does in chrome for a angular project.
Do we need to open some other port, if it's required for proper angular debugging or something else is required. The coding part is going good. I just feel missing debugging here.
Thanks for this repos. This help me to move development to container.

I am not sure how, but sometime thing started working just after raising a issue on GH. I was having this from morning and now when I did try debug again it's start showing the code. Thanks
I still didn't find what is causing the issue earlier.

I am not sure how, but sometime thing started working just after raising a issue on GH. I was having this from morning and now when I did try debug again it's start showing the code. Thanks
I still didn't find what is causing the issue earlier.


docs: how to contribute

https://hpinc.kanbanize.com/ctrl_board/79/cards/11554/details/

Congrats! The repository doesn't have any security vulnerability issues.


feat: change env's invalid hocon value from string to binary

keep ENV's invalid hocon value as binary when we store raw config.
before:
# before
EMQX_STATSD__SERVER='<IP_ADDRESS>:8124' ./bin/emqx console
> emqx:get_raw_config([statsd,server]).
"<IP_ADDRESS>:8124"
# after
> emqx:get_raw_config([statsd,server]).
<<"<IP_ADDRESS>:8124">>

Report from : StatsD server address changed to array format

LGTM, I think it matched what we decided 2 weeks ago.


Add support for FETCH syntax

Relates to https://github.com/prestosql/presto/issues/1

This is a good start. Let's add the corresponding AST node and a semantic check that fails with "unsupported" error. Otherwise, it will parse queries successfully and ignore the clause, which amounts to producing incorrect results.

There are no incorrect results, as I'm using the existing support for LIMIT so that it takes care of FETCH too.
This is why I use the same limit token in grammar to capture the row count.

There are no incorrect results, as I'm using the existing support for LIMIT so that it takes care of FETCH too.

Ah, that's right. I overlooked the assigment to the limit variable

Applied distinct FETCH handling up to LogicalPlanner (Implementation for LIMIT is used from there on)
plus tests
plus SqlFormatter change

Applied comments.
Works % some formatting issue.

No more formatting issues.

Applied comments.

Merged, thanks!


New Saxon version 10.2 is out

We can update to the new Saxon version <IP_ADDRESS> which is out since some days:
https://sourceforge.net/projects/saxon/files/Saxon-HE/9.9/
https://sourceforge.net/projects/saxon/files/Saxon-HE/9.9/SaxonHE9-9-1-7J.zip/download
In principle this only means a similar commit like in https://github.com/UB-Mannheim/ocr-fileformat/commit/4faff379843f4923960cbba6cbbd0a741fb4ffe6 but this should be tested then also.

And the next version on the maior release 10:
https://sourceforge.net/projects/saxon/files/Saxon-HE/10/Java/
https://sourceforge.net/projects/saxon/files/Saxon-HE/10/Java/SaxonHE10-0J.zip/download

Next is 10.1:
https://sourceforge.net/projects/saxon/files/Saxon-HE/10/Java/SaxonHE10-1J.zip/download

Next is 10.2:
https://sourceforge.net/projects/saxon/files/Saxon-HE/10/Java/SaxonHE10-2J.zip/download

Citation from http://www.saxonica.com/download/java.xml:

The latest maintenance release of 9.9 is Saxon <IP_ADDRESS>, released on 4 March 2020. Saxon 9.9 is currently considered the most stable and reliable release.

Pull request #127 updates to that version.

Meanwhile Saxon 10.6 is the current stable version, so we should update to that version.

Pull request #144 updates Saxon to version 10.6, so this issue can be closed as soon as these changes were merged.

Now there exists a bug fix release 10.8, and 11.3 is the latest release.

10.8 is now used in git master (and 11.x will follow soon), so I close this issue.


Fixed secstorage.proxy is not setting proxy configuration on SSVM in some cases

LGTM

LGTM

merging..

@anshul1886 next time, please specify the bug id in the commit message


Add option to lock gaze cursor [Issue #6350]

Overview
Added a togglable option (Lock Cursor When Focus Locked) to the GazeCursor to allow it to not stick to objects when selecting them.


Gestpay error handling

Currently, the Notification for Gestpay will raise a GestpayEncryptionResponseError if the server tells us there was an error.
This is handled in the helper, but not in the notification, so we end up throwing exceptions instead of marking the transaction as failed. I just set the status as anything other than successful, which is then detected as a failure, instead of blowing up.
@aprofeit @wvanbergen

Just one question, but otherwise SHIP ALL THE THINGS.

:+1:

Merging this for now, will deal with ALL THE ERRORS


feat: add transparency effect to the navbar

Fixes #269

I will review it as soon as possible. currently only on my phone.


Unable to connect to the machines by Mac

Describe the bug
I can see the document mentions that the bridge networking is working.
But I tried and saw that the network is not working at all.
To Reproduce

check the linux machine is working and capture the ip address:

@ubuntu:/Users/mafen$ uname
Linux

@ubuntu:/Users/mafen$ ip addr
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 <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip <IP_ADDRESS> brd <IP_ADDRESS>
3: eth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 86:83:93:be:e4:27 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet <IP_ADDRESS>/24 metric 100 brd <IP_ADDRESS> scope global dynamic eth0
       valid_lft 166893sec preferred_lft 166893sec
    inet6 fd07:b51a:cc66:0:8483:93ff:febe:e427/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft<PHONE_NUMBER>sec preferred_lft<PHONE_NUMBER>sec
    inet6 fe80::8483:93ff:febe:e427/64 scope link
       valid_lft forever preferred_lft forever

ping the ip address from mac

$ uname
Darwin
$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

Expected behavior
No response
Diagnostic report (required)
No response
Screenshots and additional context (optional)
No response

Please share a diagnostic report as required by the issue template: Help > Upload Diagnostics
If you're using Surge, you probably have a subnet conflict and/or #529. You'll have to fix the conflict on your side.

+1. I got this too in macOS Sonoma.
OrbStack info:
  Version: 1.0.1
  Commit: 0d4cdcf185489f992cf8e3187884f11f4feab1aa (v1.0.1)

System info:
  macOS: 14.0 (23A344)
  CPU: arm64, 8 cores
  CPU model: Apple M1 Pro
  Model: MacBookPro18,3
  Memory: 16 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-10-27T09-28-27.347254Z.zip
<!-- (To review the report, check ~/.orbstack/diag) -->

Can you try to figure out what in your network setup is causing this? VPN, proxy, Wi-Fi/Ethernet, DNS settings, content filter, enterprise app proxy, DHCP vs. static (manual) IP, anything?
I've only ever seen this specific error once after all this time, and have never been able to reproduce it again, but it'd be interesting if it happens consistently for you.

Not that I know though, when I try to connect through the terminal I disconnected WARP by Cloudflare, disconnected Private Relay. Should I restart OrbStack when I disconnected something like WARP or Private Relay?
Also, might be worth noting: I enabled the WARP DNS but that’s in Chrome. I think it might be related? But it should only work in Chrome though. Consider give it a try

After system restart, I managed to ping the instance using IP but not the orb.local domain. All is well, but I'm afraid I couldn't say the same to @afterhill

Please share a diagnostic report as required by the issue template: Help > Upload Diagnostics
If you're using Surge, you probably have a subnet conflict and/or #529. You'll have to fix the conflict on your side.

@afterhill

Closing due to lack of response, as it's almost always caused by the conflict I mentioned above. Please comment if the issue persists and I'll reopen this.


GPU memory model

Closes https://github.com/RadeonOpenCompute/ROCm/issues/2265

Also, please take a look at https://docs.olcf.ornl.gov/systems/crusher_quick_start_guide.html#enabling-gpu-page-migration

Brought in latest changes and resolved linting issues


Revert "first commit for utester-dao"

Reverts kinglcc/utester-dao#1

test a comment

test two comments

测试一下再来一条评论

Reverts #1

简单测试一下


Issue when the system scrolls the table view automatically

If the table view is scrolled without user interaction, the pong view will not know the current offset of the table, so it may show up on screen unintentionally.
The case that I ran into: I have cells that expand/collapse when they are tapped. If you tap a cell in the middle of the table, the device will automatically move the cells below, thus having no effect on the position of the Pong view up above. However if you tap the last item in the list, it will move everything above. When collapsing, it will scroll the cells down, which also brings down the pong view.
As soon as I scroll the table manually, it sees the correct offset and removes the pong view.
My fix for this was to include a call to "[self.pongRefreshControl scrollViewDidScroll];" after the cell is collapsed, which allows the pong view to update to the correct offset with the new table position.
Maybe this isn't a full-on bug, because I can't find a solution without a major refactor in the Pong library, but it should probably be included in the ReadMe as a footnote to call scrollViewDidScroll in cases where the table might be scrolled outside of "scrollViewDidScroll"

Thanks for finding this! I hadn't tested it with collapsing and expanding cells. I'll need to take a look at it, but I'll make a note for now.


[feat] add inheritance support

currently the decorated fields in the parent classes are not picked up due to the way meta data is stored.
Need to create a global storage for metadata and check instanceof for the constructor's prototype to find the matching fields

implemented in #7


Remove: Unity.Unity.6000.MacServer version 6000.0.2f1

Microsoft Reviewers: Open in CodeFlow

URL: https://download.unity3d.com/download_unity/c36be92430b9/TargetSupportInstaller/UnitySetup-Mac-Server-Support-for-Editor-6000.0.2f1.exe
OK
(Automated message - build 923)

https://github.com/microsoft/winget-pkgs/pull/186121#issuecomment-2445759087

[Policy] Needs-Manual-Merge


Create Shipment mockups

Split shipment form into four steps, to make more friendly for users. I grouped the steps by tematicaly and there are less items on the screen at any time, let me now what you thing :) It's best if you test this solution with someone who will use this form.

I like this phased approach as some of the fields are optional and likely not known at the time of creating the shipment details. This would simplify the user interaction. Do you think it would be a good idea to also give the user an option to finish creating the shipment early without having to go through all screens?

I like this phased approach as some of the fields are optional and likely not known at the time of creating the shipment details. This would simplify the user interaction. Do you think it would be a good idea to also give the user an option to finish creating the shipment early without having to go through all screens?

Yes, the possibility of ending the form early is a good idea if you do not need to fill out all the fields. Optional fields can also be placed in the last step. You can also put a star icon next to the mandatory fields, so that the user has the clarity on what is required.

Yes, the possibility of ending the form early is a good idea if you do not need to fill out all the fields. Optional fields can also be placed in the last step. You can also put a star icon next to the mandatory fields, so that the user has the clarity on what is required.

Perfect. Thanks.

Perfect. Thanks.

I  love the concept,  it'll make the app look professional. @harsimranmaan  do you think it's possible to get this done over the weekend? @martareg can you attach the icon for the shipment truck from the first image or export the design as flutter code in XD?

I  love the concept,  it'll make the app look professional. @harsimranmaan  do you think it's possible to get this done over the weekend? @martareg can you attach the icon for the shipment truck from the first image or export the design as flutter code in XD?

@schima do you have any feedback about this design. I think it'll simplify the user interaction for complex screens. As you have pointed out the current page is too cluttered, I think this would help. I am sorting the final bits of the address picker currently and plan to incorporate this in the next release of the app.

@schima do you have any feedback about this design. I think it'll simplify the user interaction for complex screens. As you have pointed out the current page is too cluttered, I think this would help. I am sorting the final bits of the address picker currently and plan to incorporate this in the next release of the app.

Great screenshots.

I think if all mandatory fields are on the very first page, that way, user can skip other pages and click FINISH.
In my opinion,  FINISH should be to the right of Continue.
screen2- I wonder if we need both 'label' & "Serial number"? Few more screens have double as well.  @harsimranmaan
-I think "Finish" & "Continue" buttons should be on the very bottom of each screen rather then fluctuating its location depending on width of fields.

But this workflow looks great.

Great screenshots.

I think if all mandatory fields are on the very first page, that way, user can skip other pages and click FINISH.
In my opinion,  FINISH should be to the right of Continue.
screen2- I wonder if we need both 'label' & "Serial number"? Few more screens have double as well.  @harsimranmaan
-I think "Finish" & "Continue" buttons should be on the very bottom of each screen rather then fluctuating its location depending on width of fields.

But this workflow looks great.

Thanks for your feedback. That's why I placed the 'Finish' button on the left side because it is the secondary button, and 'Conitue' is the primary button, and in mobile applications we mainly use the thumb and therefore the main actions should be within its reach. It is more difficult with the right thumb to reach the left side of the screen, so I put the secondary button there. When the primary action is on the left, it works against reading gravity. The user’s eyes want to move toward the bottom right, but the visual weight of the button keeps them fixated on the bottom left. After the fixation, they move to the bottom right only to revert to the left to tap the main button. As a result, the user’s eyes sweep back and forth sweep, increasing the user’s task time. When the primary action is on the right, the result is faster task completion because the button is where the reading gravity ends. Users don’t have to reverse their scanning flow or fixate on the primary action more than once. From my ux experience this way is better :)

Thanks for your feedback. That's why I placed the 'Finish' button on the left side because it is the secondary button, and 'Conitue' is the primary button, and in mobile applications we mainly use the thumb and therefore the main actions should be within its reach. It is more difficult with the right thumb to reach the left side of the screen, so I put the secondary button there. When the primary action is on the left, it works against reading gravity. The user’s eyes want to move toward the bottom right, but the visual weight of the button keeps them fixated on the bottom left. After the fixation, they move to the bottom right only to revert to the left to tap the main button. As a result, the user’s eyes sweep back and forth sweep, increasing the user’s task time. When the primary action is on the right, the result is faster task completion because the button is where the reading gravity ends. Users don’t have to reverse their scanning flow or fixate on the primary action more than once. From my ux experience this way is better :)

This is a link to this graphic from the Flaticon website. https://www.flaticon.com/free-icon/shipped_411763?term=delivery&page=1&position=10&related_id=411763&origin=search
The icon is free for use but you must include a link attribute the author. If that doesn't suit you, I draw a similar truck icon in  GIMP.

This is a link to this graphic from the Flaticon website. https://www.flaticon.com/free-icon/shipped_411763?term=delivery&page=1&position=10&related_id=411763&origin=search
The icon is free for use but you must include a link attribute the author. If that doesn't suit you, I draw a similar truck icon in  GIMP.


cannot import name '_LazyBatchNorm' from 'torch.nn.modules.batchnorm'

code is broken on latest torch 1.10.0
>>> import torch
>>> torch.__version__
'1.10.0+cu102'
>>> import onnx2pytorch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/__init__.py", line 1, in <module>
    from .convert import ConvertModel
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/convert/__init__.py", line 1, in <module>
    from .model import ConvertModel
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/convert/model.py", line 14, in <module>
    from onnx2pytorch.constants import (
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/constants.py", line 4, in <module>
    from onnx2pytorch.operations import (
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/operations/__init__.py", line 2, in <module>
    from .batchnorm import BatchNormWrapper
  File "<...>/lib/python3.9/site-packages/onnx2pytorch/operations/batchnorm.py", line 4, in <module>
    from torch.nn.modules.batchnorm import _BatchNorm, _LazyBatchNorm
ImportError: cannot import name '_LazyBatchNorm' from 'torch.nn.modules.batchnorm' (<...>/lib/python3.9/site-packages/torch/nn/modules/batchnorm.py)

Use the code from this PR: https://github.com/ToriML/onnx2pytorch/pull/23

Fixed in new version 0.4.1

I installed the tool off pip a few minutes ago and observed this issue

@j29scott - can you double check your torch and onnx2pytorch versions? what are they?


add the unlock fonction with the point system for the progression, ad…

…d sprint on the lisez moi

conflicts to resolve


webcord: 4.4.1 -> 4.4.2

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

2 packages built:

webcord
webcord-vencord

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

2 packages built:

webcord
webcord-vencord

Please update the description.

Please update the description.

In meta or for the PR


License

Hi,
Thanks for releasing Reverb!
I noticed that the README file describes this repo as an open source framework for inference/evaluation. It looks like the license is not an OSI-approved OSD license.
Are there any plans to switch the license to an open source license?
Thanks!

Hi there,
Thanks for checking out Reverb and for pointing out our license issue --- we just updated our code's license to Apache2 to facilitate it's use for inference/evaluation! We did however keep the original license for the models themselves which can be seen when downloading them from HuggingFace.
Thanks again!


Us81439 refactor image selector

remove image selector and its various friends.
currently released as v0.0.1 here: https://github.com/Brightspace/image-selector

It would be also nice if we could beak out all the simple overlay portions into a "image-selector-container" so that it'll be easier to just drop the image selector in somewhere
https://github.com/Brightspace/d2l-my-courses-ui/blob/138b1ec49f460a59b09ac740234719f328a82e83/d2l-my-courses.html#L123
Otherwise LGTM

I'mma be, I'mma be, I'mma I'mma I'mma be
I'mma be, I'mma be, I'mma I'mma I'mma be
I'mma be, I'mma be, I'mma I'mma I'mma be
I'mma be be be be I'mma I'mma be
I'mma be be be be I'mma I'mma be
I'mma be be be be I'mma I'mma be
testing this.

So when we launch the change image overlay we get an incorrect POST:
POST http://vv81-dharris:44444/d2l/home 500 (Internal Server Error)
Seems like we aren't correctly flowing the telemetry url down anymore because the Request Payload is {"name":"LaunchChangeImage","ts":1487346664}.

Thanks Dave, will investigate.

@CodeBaboon I'm seeing this problem on master as well, I do not think it is related to this particular PR. I will continue to investigate, but it shouldn't be a blocker here.


Delete aniket test branch

CHANGES TO BE DONE

Delete unnecessary branch from the repo.

why so?

Ok


Support for Deployment Visualizing External Messages

Right now, the deployment commsviz only shows the message connections between self defined messages. It would be good if it could also show connections between external messages and external nodes.

Unfortunately we have no model for what topics external nodes pub/sub/provide/require and on what names - we've talked about adding this but there is no real standard way of discovering them - so we'd have to have the user manually make them within the model (which isn't great because it is error prone and increases the development burden for something that's purely viz).  That being said, we're still considering it.

@jeholliday we're definitely open to suggestions for how you might want to represent / model such topics / advertisements


Add cross compiling functionality

This pull request adds cross compiling functionality to ponyc. It does not address cross linking and the usual gcc cross compile chain is required for linking.
See: https://github.com/dipinhora/rpxp for an example of use of the cross compiling features in a Linux X86_64 environment targeting a Linux Arm 32 bit environment.

Update all code generation related bits (codegen, expr, ast, pass,
pkg) in libponyc to dynamically check for target machine features
(OS, architecture, etc) based on LLVM Triple.
Adjust Makefile for building to 32 bit targets on 64 bit platforms.
Update test/libponyc/util to call package_init in order to
properly intialize compiler for dynamic targets to fix some failing
tests.
Disable some tests in test/libponyc/program.cc because they fail
when run as part of the full test suite but pass when run without
other tests in the test suite
(./build/debug/libponyc.tests --gtest_also_run_disabled_tests --gtest_filter=ProgramTest.*).
These tests can be fixed by adding a package_done to test/libponyc/util.cc via the following diff:

diff --git a/test/libponyc/util.cc b/test/libponyc/util.cc
index 2fa46a2..5e7aa4b 100644
--- a/test/libponyc/util.cc
+++ b/test/libponyc/util.cc
@@ -345,6 +345,8 @@ void PassTest::build_package(const char* pass, const char* src,

     ASSERT_NE((void*)NULL, *out_package);
   }
+^M
+  package_done(&opt);^M
 }

but this causes other tests to fail. I've confirmed that these same tests fail if the package_init/package_done are added to Pony master also so the failures are not related to the cross compiling changes.
The changes to src/libponyc/codegen/genprim.c are a bit of a hack in relation to the num_conv_t conv[] declaration/assignment due to the duplication.

Thanks for the huge effort!
When you say this doesn't address linking, do you mean that we're still just running the link command appropriate to the host machine? Presumably if the host linker can cope with the target platform then it will just work and otherwise it will produce some interesting error messages. I note that your specific case of interest is Intel 64 bit to ARM 32 bit both with Linux, so I assume this is easy enough to get working.
Unfortunately the tests have thrown up some issues with this PR.

On Linux, release builds are segfaulting when trying to build packages/stdlib.
On OS X, the unit test BadPonyTest.ClassInOtherClassProvidesList is now hitting an assert in the LLVM code:
"Assertion failed: (!ErrorHandler && "Error handler already registered!\n"), function install_fatal_error_handler, file /tmp/llvm20151214-56015-1irriwq/llvm-3.6.2.src/lib/Support/ErrorHandling.cpp, line 50."

Hi Andy,
Thanks for the quick response.
When I say this doesn't address cross-linking, I mean that this patch doesn't change anything about how ponyc does linking and that if someone wanted to do a full cross compiling and cross linking setup they should be using ponyc to generate the object file and then manually do the linking with the appropriate cross linker. This is not to say that the default linker couldn't handle things properly or that ponyc (with additional logic) couldn't invoke the appropriate linker, just that at the moment, I didn't address it because I couldn't address it in the same general manner as cross compiling.
Yes, my specific scenario was to cross compile from Intel 64 bit to Arm 32 bit but I initially started out with Intel 32 bit to Arm 32 bit (since initially it was easier to ignore how to make a 64 bit ponyc generate 32 bit code). Realistically, the way things are set up in this pull request, ponyc can create the appropriate object file for any target that llvm supports (assuming you tell it where to find the libponyrt.a for the target platform) and the final cross linking (including installation of the appropriate cross linker and the libs for the target platform and the cross compile of libponyrt.a) are left to the person setting up the cross compile environment. https://github.com/dipinhora/rpxp/blob/master/Dockerfile#L6 has the details of everything (possibly more things than strictly required) needed for a cross compile environment to target armhf. https://github.com/dipinhora/rpxp/blob/master/Dockerfile#L41-L51 takes care of cross compiling libponyrt for armhf. https://github.com/dipinhora/rpxp/blob/master/Dockerfile#L41-L51 takes care of compiling ponyc for x86_64 (which can target any platform llvm supports). https://github.com/dipinhora/rpxp/blob/master/build.sh#L5 uses ponyc to create the object file targeting armhf for a pony program. https://github.com/dipinhora/rpxp/blob/master/build.sh#L7-L18 takes care of the final cross linking of the object file with libponyrt.a for armhf and the standard libs for armhf. It should be relatively straight forward to set up a similar cross compile environment for any other target with the appropriate cross compiler and cross linkers.
In regards to the failing builds in Travis CI:

I looked into the release builds segfaulting on Linux x86_64 (I had done all my work on the debug builds so didn't even realize this was an issue until the Travis build failed) and I am encountering something peculiar. The normal release build does a -O3 and it segfaults but if I replace it with -O0 -<individual optimization flags> it works. <individual optimization flags> is the output of gcc -Q --help=optimizers -O3 > /tmp/O3 && gcc -Q --help=optimizers -O0 > /tmp/O0 && diff /tmp/O0 /tmp/O3| grep '^>'| awk '{print $2 " \\"}'. This is highly confusing to me since my understanding is that both of those should be equivalent. I had hoped instead to be able to disable optimizations in order to narrow down which specific (or combination of) optimization(s) is causing the segfault. Any ideas?
I haven't looked into the OS X build issues yet but will try to in the next few days.
Regarding the clang failures, I'm able to reproduce the issue on Linux x86_64 but unlike gcc I'm not able to debug further as I don't know how to manually reproduce the additional optimizations that -O3 applies that aren't applied normally so I can try to narrow down which specific optimization is causing the segfault.
As an aside regarding the ponyc tests, the current code in master (and this pull request) for PassTest::build_package in util.cc doesn't do a package_init and package_done (not in current pull request) but once these are added, some tests start failing and others start behaving oddly (test passes but output indicates error). This is an issue because for the cross compiling support both package_init and package_done are required in order to properly initialize/tear down the llvm compilation environment. This is true even when doing a native build because all code generation is now based on the llvm target triple which has to be determined at runtime. Unfortunately, as of right now, I do not know enough C/C++ (I haven't done anything "real" in over 15 years until this) nor enough about Pony to understand/fix these but hopefully you can.

Let me know if you have any additional questions. I'll post a followup comment once I have looked more into the OS X build issue.

Don't worry about not thinking to check the release build, we used to do that a lot. There are many commits in this repo with the comment "Fix release build" or similar.
I'd actually approach debugging the release build segfault completely differently. Rather than trying to work out which option causes the problem I'd find out where in the code the problem occurs.
You should be able to reproduce the crash just by running (with a release build of ponyc):
ponyc packages/stdlib

Run this inside gdb (or lldb if you prefer) and you'll get an instant back trace that will hopefully show you exactly where things are dying and what the relevant arguments, local variables, etc are.
Since the clang and gcc tests are both failing with segfaults in the code generation pass I'd guess they're the same problem.
Typically when things work fine in debug but segfault in release it's due to memory not being 0'ed in release and hence a random piece of data being treated as a pointer and dereferenced.
For the unit test package_init issues, sorry that's almost certainly my fault. Just disable (but not delete) the unit tests you need to due to this and I'll fix things once you're merged.

Thanks for the pointers. I had initially started with gdb but didn't get very far and had given up to look for other approaches (my lack of experience with C/C++ definitely didn't help). After your last comment, I went back to gdb/lldb and print statements and identified something weird but couldn't find the root cause after many hours of debugging/tracing.
Luckily, I was able to get @sylvanc to take a quick look in person and 15 minutes later he had identified my error. See the commit with message Fix lexical scoping issue to resolve release build issues. for the details.
I also re-enabled all tests and fixed the issues so now all tests pass with these changes.
Let me know if you have any questions or concerns or comments regarding how I implemented things.


Typesense does not support cross-field ORs at the moment. The adapter could not OR values between these field

Description

Typesense does not support cross-field ORs at the moment. The adapter could not OR values between these field
This error is from SearchRequestAdapter.js. The error itself is self-descriptive, I just want to know why in this example, https://showcase-nextjs-typesense-ecommerce-store.vercel.app/ ,it is completely to use cross-field ORs.

Steps to reproduce

{
  "name": "sections",
  "fields": [
    {
      "name": "organization",
      "type": "string",
      "facet": true,
      "optional": false,
      "index": true
    },
    {
      "name": "course_code",
      "type": "string",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "course_title",
      "type": "string",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "students",
      "type": "string[]",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "instructors",
      "type": "string[]",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "num_students",
      "type": "int32",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "num_instructors",
      "type": "int32",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "created_at",
      "type": "string",
      "facet": false,
      "optional": false,
      "index": true
    },
    {
      "name": "updated_at",
      "type": "string",
      "facet": false,
      "optional": false,
      "index": true
    }
  ],
  "default_sorting_field": ""
}

This is the schema.
The error should not happen, just as https://showcase-nextjs-typesense-ecommerce-store.vercel.app/
Metadata
Typsense Version: 2.2.0
OS: ubuntu

solved. The adapter use a regex to match facet filter internally. And the separator is :. Therefore I cannot : as my separator.

Hi there!
Is it possible to reopen this issue? We are running into this error with customer provided strings which contain colons. We would like to avoid asking our customer to change them. In our case, the colons are not a separator, but a way of categorizing a name of an item in the collection in a human-readable way. Take for example the name of locations, where a colon is used following a neighborhood to categorize several grocery stores with the same name:
“Capitol Hill: Whole Food’s Market”
“Belltown: Whole Food’s Market”
“Roosevelt: Whole Food’s Market”
Similar to gif in the original comment, the RefinementList component is somewhat functioning with the colons when only one item with a colon is selected. When there is more than one item, and one of the items contains a colon the error appears.
With one item containing the colon, the adapter is sending the following filter string: location_name:Capitol Hill:=[' Whole Food's Market'].
It does not resolve two colons unless they are both the same prefix leading up the first colon. For example, where both items have the prefix of “Capitol Hill”: location_name:Capitol Hill:=[' Whole Food's Market', ' QFC']
In both cases the adapter does not send the filters in quite the right syntax. We should be able to send a filter like location_name:=['Capitol Hill: Whole Food's Market', 'Capitol Hill: QFC', 'Belltown: Whole Food Market']  when using instantsearch components like RefinementList.
Seeing that colons are now supported in typesense filters as of v0.17.0, it is really cumbersome to not have the same support on this adapter. Can we please update the regex or logic that uses the regex to properly support colons in the filter values?

Instantsearch internally generates filter strings in this format: facetName:facetValue when a refinementList widget is used. The adapter then parses that into facetName and facetValue components using a Regex and converts it into a Typesense filter_by string format with those parsed components.
The problem is that given a hypothetical string like facetName:with:colons:facetValue:with:colons, it's hard to know which part of this is the facetName and which is the facetValue. Currently the regex used in the adapter assumes that all characters before the last colon are part of the facetName, and characters after that are part of the facetValue.
In your case, it sounds like the facetValue component has colons, but not the facetName.
I just pushed out v2.7.0-2 of the adapter, where I've added a new parameter called facetableFieldsWithSpecialCharacters to help with your use-case. Could you update to this version, and then follow these instructions: https://github.com/typesense/typesense-instantsearch-adapter/blob/e7d4c34e1b58192d1797b8d1f560fc9706216e46/README.md#special-characters-in-field-names--values

Thanks so much for the quick turnaround on this, Jason. I can confirm that this version of the adapter is working as expected with the new parameter. (Just for the colons in field values as we don’t currently have a use case for special characters in field names to test against at this time.)
While it appears to be behaving well with our current typesense server version of 0.24.0, we will likely hold off on upgrading the adapter to this version until there is an release of typesense 0.25.0 on the cloud to ensure everything plays nicely in a production environment.

Awesome, thank you for confirming!

we will likely hold off on upgrading the adapter to this version until there is an release of typesense 0.25.0

I'm guessing this is based on the compatibility matrix in the README file of this repo, yeah? If so, it's a bit confusing... I meant to convey that if you're using Typesense 0.25.0.rc then you want to use 2.7.0-x of the adapter to take advantage of some of the latest features. But otherwise, 2.7.0-x of the adapter is fully compatible with 0.24.0 of Typesense (it has graceful fallbacks built-in). So it's safe to use this in production, especially since 0.25.0 of Typesense Server is still ways out.


How do I wait for internet connection before

Hi @jasonacox Hope you are keeping well?
I have a new problem and thought you may be able to help.
I am trying to send signals to smart plug depending if pc is on or in standby
the problem is that when the system wakes up it takes about 10s for network to become alive again and in that time my code fails.
So question how do wait for internet connection before proceeding with control attempts.
#!/usr/bin/env python3
from datetime import datetime
import socket
import time
import tinytuya

#time.sleep(80)

def is_connected():
    try:
        #global sleep_time
        #time.sleep(sleep_time)
        # connect to the host -- tells us if the host is actually
        # reachable
        socket.create_connection(("<IP_ADDRESS>", 53))
        #print("yes")
        #sleep_time +=1
        return True
    except OSError:
        pass
    return False

c = tinytuya.Cloud()
id = "<maybe secret>" #Amplifier

turn_off = {
	'commands': [{
		'code': 'switch_1',
		'value': False
	}, {
		'code': 'countdown_1',
		'value': 0
	}]
}

turn_on = {
	'commands': [{
		'code': 'switch_1',
		'value': True
	}, {
		'code': 'countdown_1',
		'value': 0
	}]
}

sleep_time  = 1
time.sleep(sleep_time)
while True:
    time.sleep(sleep_time)
    now = datetime.now()
    print( "connected" ,now if is_connected() else "no internet!" ,now )
    print(sleep_time)
    sleep_time +=1
    if is_connected():
        c.sendcommand(id,turn_on)
        break
    else:
        sleep_time +=1

and the error is
socket.gaierror: [Errno -3] Temporary failure in name resolution
So am i missing something?
I thought id ask just in case there is a method iI not considered

Your concept is sound.  You run an infinite loop waiting for the network to come up then run your commands.  I may simplify it a bit:
import socket
import time

def is_connected():
    try:
        socket.setdefaulttimeout(3)
        s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
        host = "<IP_ADDRESS>"
        port = 53
        server_address = (host, port)
        s.connect(server_address)
    except OSError as error:
        return False
    else:
        s.close()
        return True

while True:
    if(is_connected()):
        print("connected!")
        # do your magic
    else:
        print("not connected!")
        # take a nap
    time.sleep(1)

The tinytuya.Cloud() call connects to the Cloud API to get an auth token, so you can't call it before you have internet.
Personally I wouldn't bother trying to connect to some random server such as <IP_ADDRESS> and instead just try/except the cloud calls:
#!/usr/bin/env python3
from datetime import datetime
import socket
import time
import tinytuya

id = "<maybe secret>" #Amplifier

turn_off = {
	'commands': [{
		'code': 'switch_1',
		'value': False
	}, {
		'code': 'countdown_1',
		'value': 0
	}]
}

turn_on = {
	'commands': [{
		'code': 'switch_1',
		'value': True
	}, {
		'code': 'countdown_1',
		'value': 0
	}]
}

sleep_time  = 2
retry = 30
while retry > 0:
    time.sleep(sleep_time)
    try:
        c = tinytuya.Cloud(**apiconfig)
        c.sendcommand(id,turn_on)
        break
    except socket.gaierror:
        retry -= 1

print( "connected" if retry > 0 else "no internet!", datetime.now() )


Update read-the-docs high level organization. More changes to follow

Re-organize the sections at the high level. This PR just includes skeletal changes, so rest of us can then work in parallel.
The new page looks as shown in the attached screenshot.

Codecov Report

Merging #3906 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3906      +/-   ##
============================================
+ Coverage     67.23%   67.32%   +0.08%
  Complexity        4        4
============================================
  Files          1032     1032
  Lines         50897    50897
  Branches       7109     7109
============================================
+ Hits          34220    34264      +44
+ Misses        14339    14295      -44
  Partials       2338     2338

Impacted Files
Coverage Δ
Complexity Δ

...he/pinot/core/query/pruner/ValidSegmentPruner.java
57.14% <0%> (-28.58%)
0% <0%> (ø)

...r/validation/RealtimeSegmentValidationManager.java
58.33% <0%> (-23.34%)
0% <0%> (ø)

...ore/query/scheduler/resources/ResourceManager.java
85.71% <0%> (-10.72%)
0% <0%> (ø)

.../BrokerResourceOnlineOfflineStateModelFactory.java
49.15% <0%> (-10.17%)
0% <0%> (ø)

...a/org/apache/pinot/common/config/TagNameUtils.java
64.1% <0%> (-5.13%)
0% <0%> (ø)

...e/operator/dociditerators/BitmapDocIdIterator.java
60.71% <0%> (-3.58%)
0% <0%> (ø)

.../impl/dictionary/BaseOffHeapMutableDictionary.java
81.03% <0%> (-2.88%)
0% <0%> (ø)

...e/operator/dociditerators/SortedDocIdIterator.java
55.55% <0%> (-2.78%)
0% <0%> (ø)

.../pinot/core/query/scheduler/PriorityScheduler.java
78.08% <0%> (-2.74%)
0% <0%> (ø)

...inot/core/operator/docidsets/AndBlockDocIdSet.java
55.55% <0%> (-2.09%)
0% <0%> (ø)

... and 21 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b95a64...b11dd74. Read the comment docs.


Is Snow useless without CSP?

I'm lately coming to the realization that Snow cannot protect same origin realms completely and will need some help from CSP.
I'd like to start an initiative around encouraging users to remember to use Snow while implementing some baseline of CSP. This creates a few tasks:

Research and understand what are the things and what is the spectrum Snow won't be able to defend against
Come up with a CSP that is as permissive as possible while as helping to Snow with protection as possible
Make it clear in documentation that this level of CSP is needed, explain it and break down the different directives
Create a hardened version of the demo that applies the CSP, so that we'll be able to differentiate Snow vulns that bypass both Snow and CSP or just Snow

This is important for the future of Snow because it's probably close to useless without CSP since there are some techniques Snow cannot defend against (unfortunately).

Some thoughts

Started #118 which attempts to introduce a base line of CSP to fight off the issues we no longer sure we can solve without it
In order for this project to work, we need a good infra for that
We need to create an easy way to tell websites if their current CSP allows bypass of Snow
To do that, would be neat to have a website that fetches the CSP of a web app, applies it to itself and then runs all of Snow tests
Or, maybe instead we should support running snow's current tests against any given website by demand?
Also, we need to communicate somehow what's the needed CSP to help Snow stay bulletproof.
I don't yet know if the current CSP implemented in #118 is enough to hold off all snow vulns, including open ones, need to verify
And from the other end, need to make sure current #118 CSP isn't too harsh, would be great to see if it works on MM

Closing for now after merging #118


base64 images in outlook

hi
do i have something special to get outllook display base 64 images i can see them in all mail clients i tried BUT outllook ... (damn windows..)
tried outlook 2010 and 2016, same problem
thanks !

By base64 images do you mean images in data URIs? This is not related to Nodemailer, as HTML content is not processed by Nodemailer, whatever you pass to it is delivered to destination as is. If data URIs do not work, use attachments as embedded images described here

Try this package: https://github.com/crocodilejs/nodemailer-base64-to-s3


Pass context as well as props

I need access to context as well as props in my compose functions.
I propose we add a third argument to the onPropsChange function, so it would be fn(props, onData, context). This way we aren't making a breaking change to the API.

Can you please take a look at my PR? I think it's reasonable. It won't affect anyone who isn't using context.

Isn't context() already a attribute of props? If you do a console.log of the props argument then you should get something like this:
actions: function actions()
cdnUrl: "localhost:4000/tm.js"
context: function context()
mode: "development"

Where mode and cdnUrl are props passed to the component in my example.

I'm talking about the React context not the Mantra context and no it's not.

Gotcha. I didn't realise you mean the React context.

Any update? I'm trying to use react material-ui which passes stuff down through context and it's not working.


Seeder differ between Eloquent and HTTP Request on Feature testing

Laravel Version
10.15
PHP Version
8.2.8
Database Driver & Version
SQLite in memory
Description
Hello, I have a problem regarding the feature test. I'm using .env.testing with the following details:
DB_CONNECTION=sqlite
DB_HOST=<IP_ADDRESS>
DB_PORT=3306
DB_DATABASE=:memory:
DB_USERNAME=root
DB_PASSWORD=

I'm using seeders for the populate database and doing API tests using HTTP Requests.
abstract class TestCase extends BaseTestCase
{
    use CreatesApplication, LazilyRefreshDatabase;

    public $seed = TRUE;
}

class IndicatorsTest extends TestCase
{
    use DatabaseTransactions;

    public function test_api_get_all_indicators(): void
    {
        $indicator = Indicator::count();
        dd($indicator); -----> seed works (return 11 indicator)

        $response = $this->get(route('api.v1.indicators.index'));

        $response->assertJsonCount(11, 'data.*'); -----> seed not works (return 0 indicator)
    }
}

Steps To Reproduce
sail test

After trying several ways, I use Factory for populate database.
public function test_api_get_all_indicators(): void
    {
        Indicator::factory(10)->create();

        $response = $this->get('api/v1/indicators');

        $response->assertJsonCount(4, 'data.*')->assertJsonStructure([
            'data' => [
                '*' => [
                    'id',
                    'name',
                    'description',
                    'unit',
                    'indicator_type_id',
                    'is_visible',
                    'created_at',
                    'updated_at',
                ]
            ]
        ]);
    }

It turned out that seeding was carried out in parallel with testing. Based on observations after 3 tests on a feature, the seeder is successful.
Then how to run the running feature when the seeder is successfully done?

Hi @newarifrh. Can you use the option presented here? https://laravel.com/docs/10.x/testing#parallel-testing-hooks
ParallelTesting::setUpTestDatabase(function (string $database, int $token) {
            Artisan::call('db:seed');
        });

Hi @newarifrh. Can you use the option presented here? https://laravel.com/docs/10.x/testing#parallel-testing-hooks
ParallelTesting::setUpTestDatabase(function (string $database, int $token) {
            Artisan::call('db:seed');
        });

Hi @driesvints, I've tried and the seed command on the AppServiceProvider doesn't seem to get called.
Currently I'm doing seeders only for dependent data, as a result the seeder process doesn't take much time. As for the data I want to test, I use a factory in each test.
<?php

namespace Tests;

use Database\Seeders\TypeSeeder;
use Illuminate\Foundation\Testing\LazilyRefreshDatabase;
use Illuminate\Foundation\Testing\TestCase as BaseTestCase;

abstract class TestCase extends BaseTestCase
{
    use CreatesApplication, LazilyRefreshDatabase;

    protected $seed = true;
    protected $seeder = TypeSeeder::class;
}

<?php

namespace Database\Seeders;

use Illuminate\Database\Console\Seeds\WithoutModelEvents;
use Illuminate\Database\Seeder;

class TypeSeeder extends Seeder
{
    /**
     * Run the database seeds.
     */
    public function run(): void
    {
        $this->call([
            PeriodTypeSeeder::class,
            IndicatorTypeSeeder::class,
            CategorySeeder::class
        ]);
    }
}

<?php

namespace Tests\Feature\Api;

use App\Enums\PeriodType;
use App\Models\Data;
use App\Models\Indicator;
use Illuminate\Database\Eloquent\Factories\Sequence;
use Tests\TestCase;

class IndicatorsTest extends TestCase
{
    /**
     * Testing API to get list of indicators
     *
     * Tests are carried out to get several indicators through pagination.
     * The expected results are in the form of 4 types of indicators (according to the amount specified at the endpoint)
     * with a predetermined structure.
     *
     * @return void
     */
    public function test_api_get_all_indicators()
    {
        Indicator::factory(10)->has(Data::factory()->count(3))->create();

        $response = $this->get('api/v1/indicators');

        $response->assertJsonCount(4, 'data.*')->assertJsonStructure([
            'data' => [
                '*' => [
                    'id',
                    'name',
                    'description',
                    'unit',
                    'indicator_type_id',
                    'is_visible',
                    'created_at',
                    'updated_at',
                ]
            ]
        ]);
    }
}

I now see the LazilyRefreshDatabase in yours tests. I don't think this works in combination with seeding. Can you try to change it to RefreshDatabase instead?

should i put on BaseTest or each Test?

Anywhere you used LazilyRefreshDatabase

@newarifrh since we only got one issue for this so far I'm going to close this, sorry. If you need more help please try a support channel:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC


How to prevent chromium from breaking?

I was running @sparticuz/chromium at 129.0.0 and playwright-core at 1.48.0 in a Nextjs app, deployed to Vercel with this code:
import chromium from "@sparticuz/chromium";
import playwright from "playwright-core";
const executablePath = await chromium.executablePath();
const browser = await playwright.chromium.launch({
  executablePath,
  headless: true,
  args: [...chromium.args,   "--no-sandbox", "--disable-setuid-sandbox", "--disable-gl-drawing-for-tests",],
});
....

Suddenly, it broke in production with the following error. It possibly broke with a deployment, but the lock file was never changed.
[pid=25][err] /tmp/chromium: error while loading shared libraries: libnspr4.so: cannot open shared object file: No such file or directory
I upgraded @sparticuz/chromium to 131.0.1 and playwright-core to 1.49.0, which fixed the issue.
I have 2 questions:

What was the cause of this problem? I can provide more info if needed
How can I prevent this happening in production in the future?

That error means the environment changed, most likely on deploy. There are dependencies that need to be extracted on each run, and they are different depending on if the serverless function is Amazon Linux 2 (<= node 18), or Amazon Linux 2023 (>= node 20)
If the environment is unable to be detected, no dependencies are extracted, which means they must be installed in the container the function is run in. If they are not, you will get that type of error.
I'm guessing maybe Vercel upgraded your functions to node 22, which support was added in 131.0.1
I would say, to avoid these types of errors, to have a completely separate function dedicated to running chromium. I would decouple it from any type of user input, being run on a SQS payload. That way payloads could be retried on failure and also your users are not blocked for the very slow process of running chromium. I would also deploy it straight to Lambda, not through Vercel.

Thanks for the response. I will consider these tips to improve reliability and performance.
I checked the logs and you are right about the cause. Node was upgraded to v22, even though I have v20 in Vercel settings. It was overridden by "engines" setting in package.json.
This was in the logs:
Warning: Due to "engines": { "node": ">=20" } in your `package.json` file, the Node.js Version defined in your Project Settings ("20.x") will not apply, Node.js Version "22.x" will be used instead. Learn More: http://vercel.link/node-version
Warning: Detected "engines": { "node": ">=20" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version


[New version] players not automatically turned to bots

Using the new version of Ebots, there are no checks if the user is AFK. The plugin should check if the user has been afk for 60 seconds and turn them into an Ebot if so. Thank you.

Issue resolved in latest release.


Dev

The extra capabilities are essential for the yosys_lso branch to be able to function correctly as it clones the master branch of LSOracle in its Makefile.

Resolve merge conflicts, otherwise looks good.


Big Middleware Size on Build

Description
Hi, I was trying to deploy my Next.js site on Vercel, and its failing due to the middleware.ts file being too big:
Error: The Edge Function "src/middleware" size is 2.47 MB and your plan size limit is 1 MB. Learn More: https://vercel.link/edge-function-size
I tried looking around a bit and couldn't seem to grasp why the middleware would need to be that large.
My middleware is purely just the next-intl middleware, nothing else:
import createMiddleware from 'next-intl/middleware';
import { languages } from '@/types';
export default createMiddleware({
locales: languages,
defaultLocale: 'en',
});
export const config = {
matcher: ['/((?!api|_next|_vercel|.\..).*)'],
};
I'm using:
"next": "13.5.4",
"next-intl": "^3.0.0-rc.7",
"react": "^18.2.0",
"react-dom": "^18",

Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://github.com/t2pellet/tenzin.live
Reproduction description
Steps to reproduce:
Use next-intl middleware in middleware.ts
Try to deploy to Vercel
Expected behaviour
The middleware.ts file should be a smaller/more reasonable size
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://github.com/t2pellet/tenzin.live
Reproduction description
Reproduction description
Steps to reproduce:
Use next-intl middleware in middleware.ts
Try to deploy to Vercel
Expected behaviour
The middleware.ts file should be a smaller/more reasonable size

Sorry, I am trying to reopen https://github.com/amannn/next-intl/issues/599 as I don't think this is a NextJS issue, but a problem with next intl's requirement to import translation files in the i18n-config file. Please read this:
@amannn I think this needs to be reopened. It is not nextjs, it is the fact that we are including messages on every request in the i18n configuration of Next Intl. Basically, when you write
export default getRequestConfig(async ({ locale }) => {
   return {
     .... you ask to import JSON files here in the docs
   }
}

Where you import JSON files, those JSON files are bundled by webpack, since you explicitly ask us to import them. This is causing the bloat in middleware size – this is not a NextJS problem, it's a next-intl problem!

@apavlinovic Can you upgrade next and next-intl to the latest version in your app to see if it makes a difference?
The middleware doesn't import anything from i18n.ts, so this shouldn't make a difference.

Hey @amannn I am not sure that's true...
So my middleware looks like this:
export function middleware() {}
and it's size is:
ƒ Middleware                                        290 kB
I've went through the code in middlewareImpl, and you are reading the messages from an in-memory dictionary, which is defined in i18n.ts. Every JSON file you imported ends up there, and since you are reading it on every request, it looks like it is getting bundled with middleware.ts, making next-intl unusable for real world usage?
I am on next-intl "3.5.2", next "14.1.0", and this behaviour is consistent for older Next JS versions like 13.5.4. It is not a Next JS problem, Next JS is doing the correct thing here, it is bundling imported strings with the middleware. You mentioned in
FYI, this is my i18n-config file:
export default getRequestConfig(async ({ locale = "xxx" }) => {     return {         namespaces: [             "bestAttackersPerType",             "bestGymDefenders",             "bestPerTypeList",             "bestRaidAttackers",             "buddyDistancesList",             "chargeMovesList",             "chargeMovesListPvP",             "common",             "comparer",             "disclaimer",             "fastMovesList",             "fastMovesListPvP",             "home",             "move",             "pokedex",             "pokemonPage",             "regionAndTypeList",             "shinyChecklist",             "typeChart",             "whosThatPokemon",             "pokemonTyping",             "navigationLinks",             "countersPage",             "pokemonIvChartPage",             "pokemonMovesPage",             "evolutionChartComponent",             "ivChartSpecialEncounters",             "moveCard",             "typeDescriptions",             "countersComponent",             "pokemonPvpPage",         ],         messages: {             bestAttackersPerType: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */                         ../messages/${locale}/bestAttackersPerType.json                    )                 ).default,             },             bestGymDefenders: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/bestGymDefenders.json                    )                 ).default,             },             bestPerTypeList: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/bestPerTypeList.json                    )                 ).default,             },             bestRaidAttackers: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/bestRaidAttackers.json                    )                 ).default,             },             buddyDistancesList: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */                        ../messages/${locale}/buddyDistancesList.json                    )                 ).default,             },             chargeMovesList: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/chargeMovesList.json                    )                 ).default,             },             chargeMovesListPvP: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */                        ../messages/${locale}/chargeMovesListPvP.json                    )                 ).default,             },             common: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/common.json                    )                 ).default,             },             comparer: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/comparer.json                    )                 ).default,             },             disclaimer: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/disclaimer.json                    )                 ).default,             },             fastMovesList: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/fastMovesList.json                    )                 ).default,             },             fastMovesListPvP: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/fastMovesListPvP.json                    )                 ).default,             },             home: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/home.json                    )                 ).default,             },             move: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/move.json                    )                 ).default,             },             pokedex: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/pokedex.json                    )                 ).default,             },             pokemonPage: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */                        ../messages/${locale}/pokemonPage.json                    )                 ).default,             },             regionAndTypeList: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/regionAndTypeList.json                    )                 ).default,             },             shinyChecklist: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/shinyChecklist.json                    )                 ).default,             },             typeChart: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/typeChart.json                    )                 ).default,             },             whosThatPokemon: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/whosThatPokemon.json                    )                 ).default,             },             pokemonTyping: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/pokemonTyping.json                    )                 ).default,             },             navigationLinks: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/navigationLinks.json                    )                 ).default,             },             countersPage: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */../messages/${locale}/countersPage.json                    )                 ).default,             },             pokemonIvChartPage: {                 ...(                     await import(                         /* webpackMode: "lazy-once" */                        ../messages/${locale}/pokemonIvChartPage.json`
)
).default,
},
pokemonMovesPage: {
...(
await import(
/* webpackMode: "lazy-once" */
                    `../messages/${locale}/pokemonMovesPage.json`
                )
            ).default,
        },
        evolutionChartComponent: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */
                    `../messages/${locale}/evolutionChartComponent.json`
                )
            ).default,
        },
        ivChartSpecialEncounters: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */
                    `../messages/${locale}/ivChartSpecialEncounters.json`
                )
            ).default,
        },
        moveCard: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */ `../messages/${locale}/moveCard.json`
                )
            ).default,
        },
        typeDescriptions: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */ `../messages/${locale}/typeDescriptions.json`
                )
            ).default,
        },
        countersComponent: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */ `../messages/${locale}/countersComponent.json`
                )
            ).default,
        },
        pokemonPvpPage: {
            ...(
                await import(
                    /* webpackMode: "lazy-once" */ `../messages/${locale}/pokemonPvpPage.json`
                )
            ).default,
        },
    },
};

});
`
webpackMode doesn't make any difference, but removing messages from this configuration makes a difference. There is nothing in my project saying that messages should be included in this file, but Next.JS is still including it! If you don't believe me, check this out.
Verification that this is being loaded:

I've used webpack's magic comments to force webpack to bundle the i18n configuration file under the name webpackChunkName: "all-i18n-data"

I've searched for that chunk name in my .next folder, and found it fetched in webpack-5626e5b0ee7d32f5.js bundle

The webpack-5626e5b0ee7d32f5.js bundle is used in the middleware-build-manifest.json

This is directly impacting the size of middleware.js, and introducing a massive performance penalty to anyone using next-intl and Next.JS middleware.ts. I don't think you can include the messages in this way, you need to remove them from request config when a middleware is calling your getRequestConfig method.
Or at least provide a way to know who is calling it, so that we as users of your library can load the messages based on the caller.

To add to this issue, we’ve noticed that the getRequestConfig is hit even when API routes are called, which is quite insane. We’ve noticed errors in our log due to a missing check if the locale exists in the list of locales, and we think it backtracks to api route calls!

I unfortunately don't see the content from i18n.ts you've posted above in the reproduction you've mentioned at https://github.com/t2pellet/tenzin.live/blob/next/src/i18n.ts. Is this the app where you're see the issue?
Here's btw. an example build output from example-app-router from this repo, where the middleware has a reasonable size:

You might want to compare your implementation with that one.
To continue here, we'd need a reliable reproduction where the issue is visible.


teensy 3.2 with littlevgl (Arduino IDE), setup problem?

Hello, I'm trying to compile the lvgl_test.ino from littlevgl arduino library and program it to my teensy 3.2.
Unfortunately I have follow first errors:

after change  #include <lvgl.h> to #include "lvgl.h" I have follow errors:

BTW:
Is it correct that in the "my_disp_flush" function, I have to write the x/y and color data directly to the Interface of my Display (via SPI) ? So for example follow code:
	writecommand(0x2A); //x pixel-position
	writedata(x); //start-position
	writedata(x); //start-position

	writecommand(0x2B); //y pixel-positon
	writedata(y); //start-position
	writedata(y); //start-position

	writedata(color-data); //
	writedata(color-data);  //

I think the "my_disp_flush" is not a function which is called for every pixel?
How is the structure of the "color_p" function/variable?
Where do I place the whole initialization of the Display? (in my case "init_ST7789V()"?

Hi,
Have you copied the littlevgl folder from here to your library folder?
disp_flush
Here you can see how should a disp_flush look like: https://github.com/littlevgl/lv_examples/blob/master/lv_tutorial/0_porting/lv_tutorial_porting.c.
Basically it should copy the color_p array to the specified area.

Have you copied the littlevgl folder from here to your library folder?
that's how my folder looks at the moment:

disp_flush
Here you can see how should a disp_flush look like: https://github.com/littlevgl/lv_examples/blob/master/lv_tutorial/0_porting/lv_tutorial_porting.c.
Basically it should copy the color_p array to the specified area.

I need only 16bit Color values per Pixel...
so what is the data typo of "color_p", is it already a 16bit, or 24bit Value?
thank you

lv_conf.h should be NEXT TO the src folder (as the example shows in the lv_boards repo)

I already check that, also your tutorial... it's difficult for me to understand.
I have no clue why I always get the error that "lvgl.h" is not found?!!

At first time, your error was "No such file or director: ../../lv_conf.h". It was because of the misplaced lv_conf.h.
What is your error message now?

What is your error message now?

thank you

lvgl.h error only disappears if I change to "lvgl.h" instead of <lvgl.h>.
but than or now I still have follow error:

so now I solved the problem of lv_conf.h and lvgl.h..., the problem is because I didn't read the "README.md" sorry to these circumstances :-/
Now I have follow errors see below, but I think is because I should configure something in the conf-file...

Hello, at the moment I didn't find a solution for the errors above? (undefined reference to 'lv_flush_ready' etc...

I put together a working Ardunio project for Teensy 3.2
Here you can see the directory structure.
Teensy_LittlevGL.zip

ok. thank you, now it works :-D
Follow Item in a "README" confused me:

In your main.c: #include "lvgl/lvgl.h"

now I finished the code, but it looks that function "my_disp_flush" is not called:
void my_disp_flush(int32_t x1, int32_t y1, int32_t x2, int32_t y2, const lv_color_t *color_array)
{
  /*TODO copy 'color_array' to the specifed coordinats of your disaply.*/
  writecommand(0x2A); //x pixel-position anfahren
  writedata(x1>>8); //start-position
  writedata(x1); //start-position
  writedata(x2>>8); //end-position
  writedata(x2); //end-position

  writecommand(0x2B); //y pixel-positon anfahren
  writedata(y1>>8); //start-position
  writedata(y1); //start-position
  writedata(y2>>8); //end-position
  writedata(y2); //end-position

  writecommand(0x2C); //RAM Daten senden
  digitalWrite(CS0, 0);
  digitalWrite(DC, 1); //Command = 0, Data = 1

  //SPI.transfer(color_array, 0, sizeof(color_array));
  SPI.transfer(0xA0);

  digitalWrite(CS0, 1);
  /*Tell the flushing is ready*/
  lv_flush_ready();
}

now it looks that function "my_disp_flush" is not called:
void my_disp_flush(int32_t x1, int32_t y1, int32_t x2, int32_t y2, const lv_color_t *color_array)
{

  /*TODO copy 'color_array' to the specifed coordinats of your disaply.*/
  writecommand(0x2A); //x pixel-position anfahren
  writedata(x1>>8); //start-position
  writedata(x1); //start-position
  writedata(x2>>8); //end-position
  writedata(x2); //end-position

  writecommand(0x2B); //y pixel-positon anfahren
  writedata(y1>>8); //start-position
  writedata(y1); //start-position
  writedata(y2>>8); //end-position
  writedata(y2); //end-position

  writecommand(0x2C); //RAM Daten senden
  digitalWrite(CS0, 0);
  digitalWrite(DC, 1); //Command = 0, Data = 1

  //SPI.transfer(color_array, 0, sizeof(color_array));
  SPI.transfer(0xA0);

  digitalWrite(CS0, 1);
  /*Tell the flushing is ready*/
  lv_flush_ready();
}

void loop() {
  // put your main code here, to run repeatedly:

  lv_task_handler();
  /*If 'lv_tick_inc(5)' is not called in a Timer then call it here*/
  lv_tick_inc(5);
  delay(5);             /*Wait a little*/
}

Glad to hear it compiles!
Are you sure it's not called? Can you verify it by printing to the console something in my_disp_flush?

just verified, the problem is that the program crashs :-(
If I do the "lv_tick_inc(5)" without timer means in the loop and add a delay of about 1000ms the program calls the loop aprox 10 times and than it crashes.
If I remove the 1000ms in the program nothing more works.
The same if I do the "lv_tick_inc(5)" with Timer...
If I remove the "lv_tick_inc(5)" handling the program does not crash anymore. What's wrong??
According your porting Infos "lv handler, and tick" should called every 1...5ms, but is that not very stressful for the CPU??
thank you.

It's not so stressful because it calls tasks only if their period time is over.
Please attach you ino file to check what might be wrong.

lvgl_test - Kopie.txt
see line 126, if I activate it, serial monitor(debug) shows follow:
setup
loop
.. nothing more
if line 126 deactivated:
setup
loop
loop
loop
loop etc.

At first look, it seems correct.
Please, post the summary of the crash issue to this thread: https://github.com/littlevgl/lvgl/issues/189
Here @rbultman also had a crash issue using Arduino. Join our forces to figure out what's going on :)
As the original question (set up)  is solved I close this issue. Let's continue in the other topic.


Cannot use IAM auth after migrating to v2

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.11
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
auth, api
Amplify Commands
Not applicable
Describe the bug
Hello
I've migrated my graphql api to GraphQL transformer v2.
I had specified { allow: public, provider: iam } as an auth rule in v1 and thus I was able to do all operations when logged in as an IAM user when having necessary permissions.
But after migrating to v2 and using the same auth directive, being { allow: public, provider: iam }, I am getting Unauthorized access.
what could be the cause for this ?
type Customer
  @model
  @auth(
    rules: [
      { allow: owner }
      { allow: groups, groups: ["Admin"] }
      { allow: public, provider: iam }
    ]
  ) {
  id: ID! @primaryKey
  owner: ID!
  customer_last_name: String!
  customer_mailing_address: String

This is the access control matrix for above type
iam:public
┌──────────────────────────┬────────┬──────┬────────┬────────┐
│         (index)          │ create │ read │ update │ delete │
├──────────────────────────┼────────┼──────┼────────┼────────┤
│            id            │  true  │ true │  true  │  true  │
│          owner           │  true  │ true │  true  │  true  │
│    customer_last_name    │  true  │ true │  true  │  true  │
│ customer_mailing_address │  true  │ true │  true  │  true  │
└──────────────────────────┴────────┴──────┴────────┴────────┘
Expected behavior
The { allow: public, provider: iam } needs to allow all operations for an IAM user with access to the API.
Reproduction steps

Create Customer table using v1.
Specify public IAM auth
Create Customer table using v2
Specify a similar public IAM auth
Test accessing data in both.

GraphQL schema(s)

# Put schemas below this line
type Customer
  @model
  @auth(
    rules: [
      { allow: owner }
      { allow: groups, groups: ["Admin"] }
      { allow: public, provider: iam }
    ]
  ) {
  id: ID! @primaryKey
  owner: ID!
  customer_last_name: String!
  customer_mailing_address: String

Log output

# Put your logs below this line

Additional information
No response

@rezab777 could you clarify what you mean by "Test accessing data in both." Are you using the AppSync console or something else? If you're using the AppSync console, please check out these instructions: https://docs.amplify.aws/cli/graphql/authorization-rules/#use-iam-authorization-within-the-appsync-console


Correct an amazing typo error

The title is somehow misleading, please do not create a pull request like that @dudubao2007 . However, it seems that there does exist an typo. There are no word "mandbelbrot" but "mandelbrot" to describe "曼德勃罗". Also, @dudubao2007 left his name and an inappropriate comment on the code, which I don't think is good way to fix this typo. I think this pull request needs more opinions from @Tony031218 and @cigar666 .

I'm thankful to your reply.
I'll help find and fix manim_sandbox's bugs in a more proper way from now on.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年12月18日(星期五) 下午5:12
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [manim-kindergarten/manim_sandbox] Correct an amazing typo error (#5)
The title is somehow misleading, please do not create a pull request like that @dudubao2007 . However, it seems that there does exist an typo. There are no word "mandbelbrot" but "mandelbrot" to describe "曼德勃罗". Also, @dudubao2007 left his name and an inappropriate comment on the code, which I don't think is good way to fix this typo. I think this pull request needs more opinions from @Tony031218 and @cigar666 .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Fixed "There are pending workloads due to capacity maxed by the admitted job" e2e test.

What type of PR is this?
/kind bug

What this PR does / why we need it:
Fix "There are pending workloads due to capacity maxed by the admitted job" e2e test.
Which issue(s) this PR fixes:

Fixes #2581
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/test all

/test pull-kueue-test-e2e-main-1-27
/test pull-kueue-test-e2e-main-1-28
/test pull-kueue-test-e2e-main-1-29
/test pull-kueue-test-e2e-main-1-30

/test pull-kueue-test-e2e-main-1-27
/test pull-kueue-test-e2e-main-1-28
/test pull-kueue-test-e2e-main-1-29
/test pull-kueue-test-e2e-main-1-30

/test pull-kueue-test-e2e-main-1-27
/test pull-kueue-test-e2e-main-1-28
/test pull-kueue-test-e2e-main-1-29
/test pull-kueue-test-e2e-main-1-30

How does this change help to fix the issue? I am curious :)

Looks like missed removing jobs from nsB.

But I think you right. We're creating jobs in nsB in the next cases but not in the failed.

/lgtm
but it would be nice to understand what is going on here as per https://github.com/kubernetes-sigs/kueue/pull/2608#discussion_r1677700448.

/approve

/cherry-pick release-0.7


ValueError when running collectstatic with ManifestStaticFilesStorage as static storage

When ManifestStaticFilesStorage is used as a storage class for static files, running collectstatic command with DEBUG = False causes ValueError exception because staticfiles_storage.url() tries to get hash-versioned filename from manifest.json that is not there yet. Current workaround is to temporarily switch to DEBUG = True and run collectstatic but it is not a good idea to manipulate with DEBUG in production. A solution is needed that both allows to run collectstatic with DEBUG = False and retains serving hash-versioned static assets from tinymce4-lite.

@romanvm This fix unfortunately isn't completely working for me.
if JS_URL is None:
    # Ugly hack that allows to run collectstatic command with ManifestStaticFilesStorage
    _orig_debug = settings.DEBUG
    if 'collectstatic' in sys.argv:
        settings.DEBUG = True
    JS_URL = staticfiles_storage.url('tinymce/js/tinymce/tinymce.min.js')
    settings.DEBUG = _orig_debug

I have a bunch of other commands using production environment variables, but locally. For example, my script to refresh the database now fails:
#!/bin/sh

set -e

envdir envs/prod pipenv run django-admin pg_dump && \
envdir envs/local pipenv run django-admin dropdb --noinput # allow dropdb to fail locally

envdir envs/local pipenv run django-admin createdb --noinput && \
envdir envs/local pipenv run django-admin pg_restore && \
envdir envs/local pipenv run django-admin migrate # runs local migrations on top of last version of prod db

The envdir envs/prod pipenv run django-admin pg_dump command fails.

Is this the same issue with ValueError and ManifestStaticFilesStorage?

@romanvm yeah, I get the ValueError since 'collectstatic' in sys.argv doesn't apply. I'm running a different command so collectstatic isn't in the sys.argv. Seems like the code gets run on import.

I suspected that it may not work with other management commands that import the whole Django project. Currently I don't have an acceptable solution so any help is appreciated.
Is there any specific reason why you are using ManifestStaticFilesStorage. Maybe the default file storage class will be enough?