tcod-sys doesn't build on OSX

Hey, having some trouble building tcod on OSX.
anathema@Adorjan ~/C/r/ferl> cargo build
   Compiling tcod-sys v2.0.11
failed to run custom build command for `tcod-sys v2.0.11`
Process didn't exit successfully: `/Users/anathema/Code/rust/ferl/target/debug/build/tcod-sys-2a137dae9d1f93a4/build-script-build` (exit code: 101)
--- stdout
STDOUT: \rm -f /tmp/libtcod/release/bresenham_c.o /tmp/libtcod/release/bsp_c.o /tmp/libtcod/release/color_c.o /tmp/libtcod/release/console_c.o /tmp/libtcod/release/fov_c.o /tmp/libtcod/release/fov_circular_raycasting.o /tmp/libtcod/release/fov_diamond_raycasting.o /tmp/libtcod/release/fov_recursive_shadowcasting.o /tmp/libtcod/release/fov_permissive2.o /tmp/libtcod/release/fov_restrictive.o /tmp/libtcod/release/heightmap_c.o /tmp/libtcod/release/image_c.o /tmp/libtcod/release/lex_c.o /tmp/libtcod/release/list_c.o /tmp/libtcod/release/mersenne_c.o /tmp/libtcod/release/noise_c.o /tmp/libtcod/release/parser_c.o /tmp/libtcod/release/path_c.o /tmp/libtcod/release/sys_c.o /tmp/libtcod/release/sys_opengl_c.o /tmp/libtcod/release/sys_sdl_c.o /tmp/libtcod/release/sys_sdl_img_bmp.o /tmp/libtcod/release/sys_sdl_img_png.o /tmp/libtcod/release/tree_c.o /tmp/libtcod/release/txtfield_c.o /tmp/libtcod/release/wrappers.o /tmp/libtcod/release/zip_c.o /tmp/libtcod/release/namegen_c.o /tmp/libtcod/release/png/lodepng.o /tmp/libtcod/release/bresenham.o /tmp/libtcod/release/bsp.o /tmp/libtcod/release/color.o /tmp/libtcod/release/console.o /tmp/libtcod/release/fov.o /tmp/libtcod/release/heightmap.o /tmp/libtcod/release/image.o /tmp/libtcod/release/lex.o /tmp/libtcod/release/mersenne.o /tmp/libtcod/release/mouse.o /tmp/libtcod/release/noise.o /tmp/libtcod/release/parser.o /tmp/libtcod/release/path.o /tmp/libtcod/release/sys.o /tmp/libtcod/release/txtfield.o /tmp/libtcod/release/zip.o /tmp/libtcod/release/namegen.o /tmp/libtcod/release/gui/button.o /tmp/libtcod/release/gui/container.o /tmp/libtcod/release/gui/flatlist.o /tmp/libtcod/release/gui/hbox.o /tmp/libtcod/release/gui/image.o /tmp/libtcod/release/gui/label.o /tmp/libtcod/release/gui/radiobutton.o /tmp/libtcod/release/gui/slider.o /tmp/libtcod/release/gui/statusbar.o /tmp/libtcod/release/gui/textbox.o /tmp/libtcod/release/gui/togglebutton.o /tmp/libtcod/release/gui/toolbar.o /tmp/libtcod/release/gui/vbox.o /tmp/libtcod/release/gui/widget.o /tmp/libtcod/debug/bresenham_c.o /tmp/libtcod/debug/bsp_c.o /tmp/libtcod/debug/color_c.o /tmp/libtcod/debug/console_c.o /tmp/libtcod/debug/fov_c.o /tmp/libtcod/debug/fov_circular_raycasting.o /tmp/libtcod/debug/fov_diamond_raycasting.o /tmp/libtcod/debug/fov_recursive_shadowcasting.o /tmp/libtcod/debug/fov_permissive2.o /tmp/libtcod/debug/fov_restrictive.o /tmp/libtcod/debug/heightmap_c.o /tmp/libtcod/debug/image_c.o /tmp/libtcod/debug/lex_c.o /tmp/libtcod/debug/list_c.o /tmp/libtcod/debug/mersenne_c.o /tmp/libtcod/debug/noise_c.o /tmp/libtcod/debug/parser_c.o /tmp/libtcod/debug/path_c.o /tmp/libtcod/debug/sys_c.o /tmp/libtcod/debug/sys_opengl_c.o /tmp/libtcod/debug/sys_sdl_c.o /tmp/libtcod/debug/sys_sdl_img_bmp.o /tmp/libtcod/debug/sys_sdl_img_png.o /tmp/libtcod/debug/tree_c.o /tmp/libtcod/debug/txtfield_c.o /tmp/libtcod/debug/wrappers.o /tmp/libtcod/debug/zip_c.o /tmp/libtcod/debug/namegen_c.o /tmp/libtcod/debug/png/lodepng.o /tmp/libtcod/debug/bresenham.o /tmp/libtcod/debug/bsp.o /tmp/libtcod/debug/color.o /tmp/libtcod/debug/console.o /tmp/libtcod/debug/fov.o /tmp/libtcod/debug/heightmap.o /tmp/libtcod/debug/image.o /tmp/libtcod/debug/lex.o /tmp/libtcod/debug/mersenne.o /tmp/libtcod/debug/mouse.o /tmp/libtcod/debug/noise.o /tmp/libtcod/debug/parser.o /tmp/libtcod/debug/path.o /tmp/libtcod/debug/sys.o /tmp/libtcod/debug/txtfield.o /tmp/libtcod/debug/zip.o /tmp/libtcod/debug/namegen.o /tmp/libtcod/debug/gui/button.o /tmp/libtcod/debug/gui/container.o /tmp/libtcod/debug/gui/flatlist.o /tmp/libtcod/debug/gui/hbox.o /tmp/libtcod/debug/gui/image.o /tmp/libtcod/debug/gui/label.o /tmp/libtcod/debug/gui/radiobutton.o /tmp/libtcod/debug/gui/slider.o /tmp/libtcod/debug/gui/statusbar.o /tmp/libtcod/debug/gui/textbox.o /tmp/libtcod/debug/gui/togglebutton.o /tmp/libtcod/debug/gui/toolbar.o /tmp/libtcod/debug/gui/vbox.o /tmp/libtcod/debug/gui/widget.o libtcod.a libtcodxx.a libtcod.dylib libtcodxx.dylib libtcodgui.dylib libtcod_debug.dylib libtcodxx_debug.dylib libtcodgui_debug.dylib libtcodpy.pyc
Compiling debug src/bresenham_c.c
Compiling debug src/bsp_c.c
Compiling debug src/color_c.c
Compiling debug src/console_c.c
Compiling debug src/fov_c.c
Compiling debug src/fov_circular_raycasting.c
Compiling debug src/fov_diamond_raycasting.c
Compiling debug src/fov_recursive_shadowcasting.c
Compiling debug src/fov_permissive2.c
Compiling debug src/fov_restrictive.c
Compiling debug src/heightmap_c.c
Compiling debug src/image_c.c
Compiling debug src/lex_c.c
Compiling debug src/list_c.c
Compiling debug src/mersenne_c.c
Compiling debug src/noise_c.c
Compiling debug src/parser_c.c
Compiling debug src/path_c.c
Compiling debug src/sys_c.c
Compiling debug src/sys_opengl_c.c
Compiling debug src/sys_sdl_c.c
Compiling debug src/sys_sdl_img_bmp.c
Compiling debug src/sys_sdl_img_png.c
Compiling debug src/tree_c.c
Compiling debug src/txtfield_c.c
Compiling debug src/wrappers.c
Compiling debug src/zip_c.c
Compiling debug src/namegen_c.c
Compiling debug src/png/lodepng.c
Linking libtcod_debug.dylib

STDERR: In file included from src/sys_c.c:41:
include/libtcod.h:172:9: warning: 'MAX' macro redefined [-Wmacro-redefined]
#define MAX(a,b) ((a)<(b)?(b):(a))
        ^
/usr/include/sys/param.h:218:9: note: previous definition is here
#define MAX(a,b) (((a)>(b))?(a):(b))
        ^
In file included from src/sys_c.c:41:
include/libtcod.h:173:9: warning: 'MIN' macro redefined [-Wmacro-redefined]
#define MIN(a,b) ((a)>(b)?(b):(a))
        ^
/usr/include/sys/param.h:215:9: note: previous definition is here
#define MIN(a,b) (((a)<(b))?(a):(b))
        ^
src/sys_c.c:373:13: warning: 'sem_init' is deprecated [-Wdeprecated-declarations]
        if ( ret ) sem_init(ret,0,initVal);
                   ^
/usr/include/sys/semaphore.h:55:5: note: 'sem_init' has been explicitly marked deprecated here
int sem_init(sem_t *, int, unsigned int) __deprecated;
    ^
src/sys_c.c:403:3: warning: 'sem_destroy' is deprecated [-Wdeprecated-declarations]
                sem_destroy((sem_t *)sem);
                ^
/usr/include/sys/semaphore.h:53:5: note: 'sem_destroy' has been explicitly marked deprecated here
int sem_destroy(sem_t *) __deprecated;
    ^
4 warnings generated.
src/zip_c.c:87:30: warning: cast to 'void *' from smaller integer type 'int' [-Wint-to-void-pointer-cast]
                TCOD_list_push(zip->buffer,(void *)val);
                                           ^
1 warning generated.
osx/macsupport.m:17:22: warning: unused variable 'pool' [-Wunused-variable]
        NSAutoreleasePool  *pool = [[NSAutoreleasePool alloc] init];
                            ^
1 warning generated.
ld: warning: ignoring file lib/libz.a, file was built for archive which is not the architecture being linked (x86_64): lib/libz.a
Undefined symbols for architecture x86_64:
  "_gzclose", referenced from:
      _TCOD_zip_save_to_file in zip_c.o
      _TCOD_zip_load_from_file in zip_c.o
  "_gzopen", referenced from:
      _TCOD_zip_save_to_file in zip_c.o
      _TCOD_zip_load_from_file in zip_c.o
  "_gzread", referenced from:
      _TCOD_zip_load_from_file in zip_c.o
  "_gzwrite", referenced from:
      _TCOD_zip_save_to_file in zip_c.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [libtcod_debug.dylib] Error 1

--- stderr
thread '<main>' panicked at '`make` returned: exit code: 2', /Users/anathema/.cargo/registry/src/github.com-1ecc6299db9ec823/tcod-sys-2.0.11/build.rs:39

I cloned the tcod-rs repository and ran cargo run --example keyboard though and it worked.
Cheers.

So this only happens when you download from crates.io? If so that's pretty interesting, since tcod_sys was last modified at 09 April 2015. Try deleting your target directory to force cargo to redownload and remake all dependencies?

Running cargo clean will also clean target. But yeah, if the clean checkout of tcod-rs works and your own app using it doesn't, something is probably wrong with the cashed dependencies there.

cargo clean -> cargo build gives the same error, as does creating a new project, adding tcod as a dependency and trying to build.

Could you do a make -f makefiles/makefile-osx clean followed by a make -f makefiles/makefile-osx build in the tcod_sys/libtcod directory and post the output for the second? Also a clang --version.

https://gist.github.com/ProfessionalNihilist/1189e3c8a714d4fdabf4

So wait, manually running the make actually succeeded?

Yeah, in the tcod-rs repository I cloned the build succeeds. But in my project where I add a dependency to tcod in my cargo.toml file I cannot build my project and instead get the error I opened the issue with.

Could you do the same makefile thing using this file: crates.io tcod-sys crate? This should literally be the same as the repo version, but I'm running out of ideas.

Welp, changing my depdnency from tocd="*",  to
[dependencies.tcod]
git = "https://github.com/tomassedovic/tcod-rs"

compiled successfully.

I've pushed a new version on crates.io. No idea how libz.a managed to sneak in. I made sure to clean everything this time and then checked the geterated tcod*.crate files before uploading. Hopefully it works. There is a rule to exclude *.a in .gitignore so I don't know what happened.

Closing this issue. Feel free to reopen (or create a new one) if you have any more problems. Thanks for reporting this, @ProfessionalNihilist!
Oh, also just in case you're not aware: if you don't use "*" as the version in Cargo.toml, once things compile, Cargo won't re-download the dependency or update to a new one. If you want to update to a newer version, you have to do it manually by cargo update -p tcod.
Not sure it'd fix the problem you were having here but if tcod="*" worked, then maybe it would.

I'm getting the same error as @ProfessionalNihilist using tcod="*" as well as the [dependencies.tcod] fix noted above.

I'm building on Mac OS X and having the exact same problem.
[dependencies]
tcod = "*"

That won't build but:
[dependencies.tcod]
 git = "https://github.com/tomassedovic/tcod-rs.git"

Works just fine.

And it's the exact same issue, libz.a made its way into the crates.io distribution. @tomassedovic do you have any idea what could be causing this?

I'll have another look.

So yeah, my Cargo seems to be ignoring .gitignore for whatever reason. And if libz.a is on my machine (because I ran cargo build in the past), cargo package will just include it (among with a bunch of other files that shouldn't be there I presume).
I've updated the release checklist to ensure git clean removes any files not in the repo and I've added the file into Cargo.toml's exclude section for good measure.
As soon as the tests for that commit pass, I'll make upload a new release on crates.io.

Okay, tcod_sys v. 3.0.1 is out. To use it with our existing project, run cargo update -p tcod_sys.

Hello, I believe I have the same issue with tcod 0.13, tcod-sys 5.0.0 on macOS 10.14.3. I've installed pkg-config and sdl. I get:
error: failed to run custom build command for tcod-sys v5.0.0
Unfortunately the workaround used above, replacing the dependency this:
[dependencies.tcod]
 git = "https://github.com/tomassedovic/tcod-rs.git"

doesn't seem to work either.


New parameter for Alzdefaults exclusions

Overview/Summary
This PR will add flexibility to exclude specific policies from ALZ Default Policy Assignments module via the new parameter parExcludedPolicyAssignments. This will help organizations that need to deviate from some of the ALZ reference implementation policies, but at the same time wants to keep the ALZ Default Policy Assignments module as is for easier upstream updates.
This PR fixes/adds/changes/removes

New parameter parExcludedPolicyAssignments in ALZ Default Policy Assignments module
New wiki section in AssigningPolicies.md to describe how to use the exclusion parameter.

Breaking Changes

The new parameter is optional only.

Testing Evidence

First test excluding all default policy assignments

Deployment success with no policy assignments

Second test excluding 6 specific policy assignments

Deployment success with all policy assignments excluding the 6 from parameter

As part of this Pull Request I have

[ x ] Read the Contribution Guide and ensured this PR is compliant with the guide
[ x ] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[ x ] Checked for duplicate Pull Requests
[  ] Associated it with relevant GitHub Issues
[ x ] (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
[ x ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ x ] Performed testing and provided evidence.
[ x ] Updated one or more of the following tests (if required)

Unit
Linting
E2E (End-To-End)
ValidateAzCloud (Base validation in Azure Cloud)
ValidateMcCloud (Base validation in Azure China Cloud)

[ x ] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
[ x ] If relevant, created or updated Code Tours here

/azp run validateazcloud

/azp run validateazcloud

/azp run e2e

/azp run validateazcloud

/azp run e2e


feat: migration to BlockId

Feature Request
The way we currently handle block id is not compliant with the ecosystem(example)
Beerus needs to handle a BlockId similar to other RPC Providers
Describe Preferred Solution

Use starknet-rs jsonrpc-models

Describe Alternatives

implement a Deserialize/Serialize implementation in beerus-core for BlockId that rpc, cli can import and use

ex part 1  ex part 2 ex part 3

If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)

[ ] Yes
[ ] No

@drspacemn I'll take this.

How is it going with the BlockId ?

How is it going with the BlockId ?

It's done, need https://github.com/keep-starknet-strange/beerus/pull/363 merged first. Depends on updated starknet-rs library.

Now that the starknet-rs upadte has been merged #364 you should be able to close this one too.


[serverless-1.31] Use s2i GA image

Use s2i GA image on func s2i tasks. It aligns with https://github.com/openshift-knative/serverless-operator/pull/2366

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (serverless-1.31@327ce23). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                 @@
##             serverless-1.31     #722   +/-   ##
==================================================
  Coverage                   ?   49.43%
==================================================
  Files                      ?       96
  Lines                      ?    13119
  Branches                   ?        0
==================================================
  Hits                       ?     6486
  Misses                     ?     5990
  Partials                   ?      643

Flag
Coverage Δ

unit-tests-ubuntu-latest
49.43% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

hello @matejvasek Could you PTAL?
Btw I had to change the s2i bin location.. the GA image has it under root.

/approve
/lgtm

/override "On Cluster Test (1.20.2, ubuntu-latest)"


some question with AndroidStreamingClient

when I want to try the example project,there are some errors in Eclipse,
like
E/AndroidRuntime(25286): java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.c77.androidstreamingclient.example/com.c77.androidstreamingclient.example.DecoderMainActivity}: java.lang.ClassNotFoundException: Didn't find class "com.c77.androidstreamingclient.example.DecoderMainActivity" on path: DexPathList[[zip file "/data/app/com.c77.androidstreamingclient.example-2.apk"],nativeLibraryDirectories=[/data/app-lib/com.c77.androidstreamingclient.example-2, /vendor/lib, /system/lib]],

@ZhuChaozheng this sounds like a problem with the project set-up in Eclipse, particularly the classpath.
Can you provide more detail on how you set-up the example project in Eclipse until you got to that error?
Also take into account that the example project is prapared for Android Studio, not for Eclipse, so you will have to do some kind of import process to make it work on Eclipse, we haven't tried that yet.

OK,I will hava a try with Android Studio.Thank you!

This issue seems to have been addressed.


Backrelation expansion does not work properly in with list getter methods

I am using the Javascript client to expand back relations.  I have noticed that if I use the get*List methods, the back relations do not expand however if I use the getOne and use the same expand it works. Only back relation to one of the collections works and I have made sure that all the API rules and index settings are the same between them.
This does not work:
const result = await pb.collection("user_profile").getList(1, 1, {
  filter: "user.username = 'apollo'",
  expand: "user_availability_via_user_profile",
});

This works:
  const result = await pb
    .collection("user_profile")
    .getOne("6425nwxsn66jmm8", {
      expand: "user_availability_via_user_profile",
    });

The user_availability has a relation to user_profile but not the other way around. I have other collections similar to user_availability.

I'm not able to reproduce it. I've just tested it locally and on the live demo and it works correctly for me.
Make sure that for both requests your client satisfies the View API rule of the expanded collection.
Another possible common reasons why this may not work:

error in custom hooks code
external cache (common if use Next.js because they have custom fetch implementation enabled by default)

For the latter, I recommend to test the requests directly against PocketBase to rule out 3rd party misconfiguration, either with curl or add a plain pb_public/index.html:
<!DOCTYPE html />
<html>
<head>
    <meta charset="utf-8" />
    <title>Test</title>
</head>
<body>
    <script type="module">
        import PocketBase from<EMAIL_ADDRESS>
        const pb = new PocketBase("http://<IP_ADDRESS>:8090");

        your requests...
    </script>
</body>
</html>

Open your browser and navigate to http://<IP_ADDRESS>:8090 and test it.
If you still think that there is a PocketBase issue, please provide a minimal reproducible example + export of your collections configuration as json (Admin UI > Settings > Export collections) and I'll try to have a look at it.

@ganigeorgiev Thanks for the prompt reply. It magically started working so I am assuming this was related to Next.js caching. I will let you know with more info if it happens again.

Please make sure to read https://github.com/pocketbase/pocketbase/discussions/5313.


Add option to hide tweets order navbar

Twitter has added the tweets ordering option as a navbar at the top of the main page.

(Sorry for the french screecap)
For minimalism purposes, it could be hidden.
The selector is div[data-testid="primaryColumn"] nav[role="navigation"]on Firefox. I don't know if Chrome's the same or not.

Not seeing this UI? Feel free to re-open if it's still an issue.


getconsumption gives void answer from api

Thanks a lot for this handy tool. I have been using the localsmappy part quite extensively.
I hope you can have a look at the code again, as accessing consumption data from the web smappee API does not work properly (anymore?).
I can authenticate successfully and use Epoch Timestamps as entries for the _getConsumption command.
e.g.:
start =<PHONE_NUMBER>
end =<PHONE_NUMBER>
s.get_consumption(service_location_id=service_location_id, start=start, end=end, aggregation=3)
This results in an asnwer from the Smappee API like this:
{u'consumptions': [], u'serviceLocationId': 19938}
I would expect an outcome similar to the one in your example on the wiki https://github.com/EnergieID/smappy/wiki .
It would be great, if you could have a look. thanks

The Smappee API takes milliseconds sinds epoch as input, not seconds. If you input a datetime object to Smappy, the conversion is done for you, but if you input an int it just passes it along without checking. So you should've used start =<PHONE_NUMBER>000 and end =<PHONE_NUMBER>000.
This info is missing from the docstrings, so I'll add it there.

Thanks @JrtPec  for the swift answer - yes, that is, what I tried at first. However I get an error message, which points at the part of the smappy code, where milliseconds are automatically added:
>>> s.get_consumption(service_location_id=service_location_id, start=<PHONE_NUMBER>000, end=1503731649000, aggregation=3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 28, in wrapper
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 197, in get_consumption
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 245, in _get_consumption
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 446, in _to_milliseconds
NotImplementedError: Time format not supported. Use epochs,                                        Datetime or Pandas Datetime

the same error comes up, when I use the datetime format and led the code convert:
>>> s.get_consumption(service_location_id=service_location_id, start='2017-08-20 16:55:25.063857', end='2017-08-27 16:56:28.457132', aggregation=3)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 28, in wrapper
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 197, in get_consumption
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 245, in _get_consumption
  File "build/bdist.linux-armv7l/egg/smappy/smappy.py", line 446, in _to_milliseconds
NotImplementedError: Time format not supported. Use epochs,                                        Datetime or Pandas Datetime

only when I use epoch timestamp without the miliseconds I receive an answer from the smappee API (even if it is a void one :-) )
>>> s.get_consumption(service_location_id=service_location_id, start=1503213249, end=150373164, aggregation=3)
{u'consumptions': [], u'serviceLocationId': 19938}

I assume I do some very stupid mistake.....

Wow, this is something I haven't seen before.
First let's get this out of the way: there is no bug in your second approach, because '2017-08-20 16:55:25.063857' is a string, not a datetime object.
So about the first try:
The method _to_milliseconds should return after the line isinstance(time, int). So it seems like your Python installation is evaluating<PHONE_NUMBER>000 as something else than an int.
Could you try isinstance(1503213249000, int) in a console? Does it evaluate to False?
I found this reference:

In Python 2, the expression isinstance(x, int) will return False if x is an integer that has been promoted to a long.

I tried it on my Python 2 installation and isinstance(1503213249000000000, int) was still True, but isinstance(15032132490000000000, int) was suddenly False.
So you could get rid of the problem by using Python 3 (hint hint).
Replacing that line with isinstance(time, (int, float, long)), should fix it though.
Can you try isinstance(1503213249000,(int, float, long))?

Since the long type no longer exists in Python 3, I have fixed it like this:
import numbers
isinstance(x, numbers.Number)

That should cover all bases.
I pushed it in https://github.com/EnergieID/smappy/commit/053e9b3bee082085b16c7f357e0f119d5b9e6a13 and it is on PyPi in Smappy version 0.2.12

hi @JrtPec
thx - I had in deed Python 2.7 running here updating now ... will report how it works in Python3....
;-)

Hi @JrtPec
after installation of python3, panda etc: I can confirm that the problem was with me using python2.7. It shows indeed ´isinstance(15032132490000000000, int)´ as ´False´.
I checked: and all is fine, when run in python3:
 >>> isinstance(1503213249000000000, int)
True
>>> isinstance(15032132490000000000, int)
True

using epoch values without miliseconds produces as expected an void answer
>>> s.get_consumption(service_location_id=service_location_id, start=1503213249, end=150373164, aggregation=3)
{'consumptions': [], 'serviceLocationId': 19938}

using correct epoch format is successful
>>> s.get_consumption(service_location_id=service_location_id, start=<PHONE_NUMBER>000, end=1503731649000, aggregation=3)
{'consumptions': [{'timestamp':<PHONE_NUMBER>000, 'solar': 0.0, .......

thanks for swift reply -- now I can start my project :smile:


node upgrade by snyk openssl fix

Relevant information
A Snyk vulnerability was found, this PR fix it.
https://hub.docker.com/_/node/tags?page=1&name=20.3-bullseye-slim
Checklist

[ ] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

Closing since I've moved those to node:latest


[Feature request] Add ORPO finetuning

Hi @armbues, thank you for this great project.
Please add ORPO finetuning to do SFT and DPO in one step https://arxiv.org/abs/2403.07691

Great idea! I will add this to the roadmap.

The official implementation of the "ORPO Trainer" can be found here.


Add locate command

LocateCommand followed by INDEX, to show the location on Google Map

@melvintzw, @Der-Erlkonig, comments?


PHP 7.3

Add support for PHP 7.3
Don't think theres any code changes here, just adding it to the test matrix

Fixed in 4.0.0


I can't get you component to work

He I'm interrested in trying out this component you've build but i'm having trouble getting it to work. I'm setting it up like you're saying in the README file. My editor tells me this statement "import Canvas from 'react-canvas-polygons';" has a problem:
module "d:/14.ReactDev/draw-testing/draw-test1/node_modules/react-canvas-polygons/build/index"
Could not find a declaration file for module 'react-canvas-polygons'. 'd:/14.ReactDev/draw-testing/draw-test1/node_modules/react-canvas-polygons/build/index.js' implicitly has an 'any' type.
Try npm install @types/react-canvas-polygons if it exists or add a new declaration (.d.ts) file containing declare module 'react-canvas-polygons';ts(7016)
No quick fixes available
I'm unable to fix this.

So just an update and clarification. It does show me a canvas with the background image but I can't draw on it. Accourding to your readme I should be able to draw lines on the canvas with the following code:
import React, { Suspense } from 'react';
import ReactDOM from 'react-dom';
import type from 'prop-types';
import { CircularProgress } from '@material-ui/core';
import Canvas from 'react-canvas-polygons';
class DrawCanvas extends React.PureComponent {
handleCleanCanva = () => this.canva.cleanCanvas();

render() {
    const { imageInfo } = this.props;
    const imageInfoLength = Object.keys(imageInfo).length === 0;

    return(
        <Suspense fallback={<CircularProgress color="secondary" />}>
            <button variant="outlined" style={{ marginBottom: '20px' }}
                onClick={this.handleCleanCanva}
            >
                Clean Canvas
            </button>
            {imageInfoLength &&
                <CircularProgress color="secondary" />
            }
            <Canvas
                ref={canva => this.canva = canva}
                imgSrc={imageInfo.url}
                height={imageInfo.height}
                width={imageInfo.width}
            />
        </Suspense>
    );
}

}
export default DrawCanvas;
DrawCanvas.propTypes = {
tool: type.string,
imageInfo: type.object,
};
var test_image = {url:'https://wikitravel.org/upload/shared/thumb/c/cd/Map_of_East_Asia.png/500px-Map_of_East_Asia.png', width:500, height:300};
ReactDOM.render(, document.getElementById('root'));

Oke so I did get te storybook version of your component to run. I forked your project and am planning to start developing what I need from there. I needed a component that could draw polygons over an image. I will cut the code down to that specific requirement and build other functionality from there.

@FlyingApe I am using the same code as your snippet above. How were you able to draw lines on the canvas? For me, the code compiles properly but it does not allow me to draw any lines or polygons on the canvas.

Hi @edisonmoy, I'm not sure if you still need help on this, but I was able to draw the polygons by wrapping the example in the README into the Input component that you can find in dev/src/stories/input.js as @FlyingApe previously wrote.
Changing the example like this should do the trick:
//components/DrawCanvas.js
import React, { Suspense } from 'react';
import type from 'prop-types';
import { CircularProgress } from '@material-ui/core';
import Canvas from 'react-canvas-polygons';

import Input from './input';

class DrawCanvas extends React.PureComponent {

    handleCleanCanva = () => this.canva.cleanCanvas();

    render() {
        const { imageInfo, initialData } = this.props;
        const imageInfoLength = Object.keys(imageInfo).length === 0;

        return(
            <Suspense fallback={<CircularProgress color="secondary" />}>
                <button variant="outlined" style={{ marginBottom: '20px' }}
                    onClick={this.handleCleanCanva}
                >
                    Clean Canvas
                </button>
                {imageInfoLength &&
                    <CircularProgress color="secondary" />
                }
                <Input render={ state => (
                    <Canvas
                        ref={canva => this.canva = canva}
                        height={240}
                        width={300}
                        imgSrc="https://ric-bucket.s3.amazonaws.com/device_5c05ee0cb669e165879e622a/sensorview.jpg"
                        brushSize={Number(state.brush)}
                        color={state.color}
                        tool={state.tool}
                        onDataUpdate={(data) => console.log('data updates: ', data)}
                        onFinishDraw={() => console.log('finish draw')}
                        initialData={initialData}
                    />
                )} />
            </Suspense>
        );
    }
}
export default DrawCanvas;
DrawCanvas.propTypes = {
    tool: type.string,
    imageInfo: type.object,
};

I've noticed that component starts to work when tool is changed. Like so:
import React, { useEffect, useState } from "react";
import Canvas from "react-canvas-polygons";

export const DrawCanvas = React.forwardRef(({ imageInfo }: any, ref) => {
  const [tool, setTool] = useState("Line");
  useEffect(() => {
    const timeout = setTimeout(() => setTool("Polygon"), 1000);
    return () => clearTimeout(timeout);
  }, []);
  return (
    <Canvas
      ref={ref}
      imgSrc="https://images.globalindustrial.com/images/enlarge/695511.jpg?t=1628284125430"
      height={800}
      width={800}
      tool={tool}
      onCompleteDraw={console.log.bind(console)}
    />
  );
});

As suggested by @kirill-konshin tool is empty on mount. We have to update the tool after the intial rendering, then only we can start drawing. And also after drawing an Object, tool is set to null

Hi @kirill-konshin @love4bugs,
I am trying to place the clean button but when I clean it I am getting the following error. Could you please help me wher I am doing mistakes.

My current code:
`import React, { useEffect, useState } from "react";
import Canvas from "react-canvas-polygons";
export const Draw2 = React.forwardRef(({ imageInfo  }, ref) => {
const [tool, setTool] = useState("Line");
useEffect(() => {
    const timeout = setTimeout(() => setTool("Polygon"), 1000);
    return () => clearTimeout(timeout);
}, []);

const handleCleanCanva = () => {
    this.ref.cleanCanvas();
}
return (
    <div>
        <Canvas
            ref={ref}
            imgSrc="https://images.globalindustrial.com/images/enlarge/695511.jpg?t=1628284125430"
            height={800}
            width={800}
            tool={tool}
            onCompleteDraw={console.log.bind(console)}
            canUndo={true}
        />
        <button variant="outlined" style={{ marginBottom: '20px' }}
                onClick={handleCleanCanva}>
            Clean Canvas
        </button>
    </div>
);

});
`
Thank you

@atikaakmal It's too late for you. I wrote an example code for everyone who doesn't understand how this library work.
Code sandbox

I am so sorry guys, I have sent add a filter to GitHub e-mails in Gmail and I have never seen those issues.
@FlyingApe I am so sorry. I will definitely update the docs and probably reference @RTae (thanks a lot) code sandbox or enhance that.
This weekend I will revisit this project and catch up.


As a Professor, I want to grant hardware access to students in my classroom, so that they can experiment with real systems.

Background
Professors care deeply about students experimenting with hardware. Although these students can get access via the open provider, this usually results long queue times. Currently, we have the Educators Program but there's a disconnected experience between syllabus creation and hardware access
Goal
Professors should be able to add enrolled students into a classroom provider
Acceptance Criteria

[ ] Professors should be able to click a button to the Educator's Program access on a syllabus page

This repository is no longer maintained. It has been superseded by IBM Quantum Learning.


Wrong C++ version check for span_HAVE_NORETURN?

Compiling as C++11, I see:
/home/smarchi/src/babeltrace/src/cpp-common/vendor/span-lite/span.hpp:831:1: error: function 'throw_out_of_range' could be declared with attribute 'noreturn' [-Werror,-Wmissing-noreturn]
  831 | {
      | ^
/home/smarchi/src/babeltrace/src/cpp-common/vendor/span-lite/span.hpp:854:1: error: function 'report_contract_violation' could be declared with attribute 'noreturn' [-Werror,-Wmissing-noreturn]
  854 | {
      | ^

The definition of span_HAVE_NORETURN is:
 #define span_HAVE_NORETURN                  span_CPP17_000

cppreference says it's available in C++11:
https://en.cppreference.com/w/cpp/language/attributes/noreturn
So I guess the definition of span_HAVE_RETURN should be span_CPP11_OR_GREATER or one of the span_CPP11_* ones. I have no idea about the support of MSVC for this, unfortunately.

@martinmoene Would you mind making a new release including this fix?
We include your projects directly into ours and I prefer referring to a specific version/tag.

@eepp Yeah, I'll do that, thanks for the heads-up.

@eepp Created release 0.11.0; notes yet to be edited.


Update Cascadia Code to 2008.25

https://github.com/microsoft/cascadia-code/releases ???

Might this fix the #7260 issue?

Nah, that font isn't even cascadia -- it reproduces anywhere with NF glyphs :(
CCode release going up in a bit.


Fix: The alloc crate uses the Rust 2021 edition now

The alloc library was switched to the 2021 edition in https://github.com/rust-lang/rust/pull/92068. However, it did not use any features of the new edition until PR https://github.com/rust-lang/rust/pull/98103, which relies on the newer closure capture mechanism. This commit fixes the build on the latest nightlies, which include that PR.
Fixes #104

Published as v0.6.6


fix participant list autoupdate

resolves #1571 introduced by  #1364.
The functionality of  #1364 for the participant list should be checked too when reviewing this PR.

@bastianjoel prettify check failed


Make dev env LAN access easier

Summary
As in title.
Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

Fixes #

This looks good. I had to do the same when testing in windows VM when debugging paste upload.
However, when testing this, it didn't work. When access the site locally, it just redirects to localhost. See
curl -I http://<IP_ADDRESS>:8899/
HTTP/1.1 302 Found
Date: Thu, 02 Jul 2020 09:47:38 GMT
Server: Apache/2.4.38 (Debian)
X-Powered-By: PHP/7.4.7
Location: http://localhost:8899/
Content-Type: text/html; charset=UTF-8

Did this work locally for you @merapi ?
I think there is a simple workaround, that I have used before.
Add something like this in the wp-config.php file.
What this does it dynamically set the home/ site urls to what host headers are passes. This means that site will not redirect to whatever the localhost.

@spacedmonkey This works for me, browser/os cache can be involved in this, but on a clean slate - never had a problem (just had to go to localhost and change the URLs to my IP, and then access the new site). I was only redirected to localhost if I didn't change WP General Settings URL - did you?

@spacedmonkey This works for me, browser/os cache can be involved in this, but on a clean slate - never had a problem (just had to go to localhost and change the URLs to my IP, and then access the new site). I was only redirected to localhost if I didn't change WP General Settings URL - did you?

I think it would be better, if we can the home / site url dynamic so you don't have to do this.

@spacedmonkey This works for me, browser/os cache can be involved in this, but on a clean slate - never had a problem (just had to go to localhost and change the URLs to my IP, and then access the new site). I was only redirected to localhost if I didn't change WP General Settings URL - did you?

I think it would be better, if we can the home / site url dynamic so you don't have to do this.

Without a doubt. If there is an easy and reliable way to do this - 🙏 .
My concern was about getting the right local IP (which interface?) on all OSs - in that solution we don't need to care about it?

My concern was about getting the right local IP (which interface?) on all OSs - in that solution we don't need to care about it?

It is not an OS issue. The host header is handled via apache in the docker. So apache is the only place that it needs to detect host header correctly is there.

From my testing, it doesn't work as expected.
Started the env and accessed it from my phone via http://<IP_ADDRESS>:8899/ (this works because of my docker-compose.yml change) now Log in link redirects to localhost:8899 (we have hardcoded WP_HOST=${WP_HOST-"localhost"}) and because there is no localhost on my phone - it doesn't work.
So are we back to

My concern was about getting the right local IP (which interface?) on all OSs

?
We need to get that IP and feed it into WP_HOST=${WP_HOST-"<IP_ADDRESS>"}, right? @spacedmonkey


Strange behaviour while processing a huge amount of request

Hi guys,
I use typhoeus in one of my projects and recently I saw a weird thing. I queue a lot of request, sometimes even about 70 000 and when several are completed, there are queued next ones within the "on_complete" block.
request.on_complete do |response|
  if response_has_widget?(response)
    @result = true
  elsif has_more_urls_to_check?
    queue_next_url
  else
   @result = false
  end
end

The weird thing I saw is a wrong result returned by my response_has_widget, despite the fact that should be correct (checked manually). This method base on a response body, so I write it out during processing. I expected a full website html, but in this body was a html cut down usually around first body tag. There were also many empty outputs when they shouldn't be.
This behaviour shows up around a 2000th processed request and stay to the last one.
My hydra max concurrency is 100, timeouts are also high.
Is anyone know what is going on?
Thanks for help.

@sayradley ... out of curiosity, can you take a look at your TCP connections and see if any are stuck in a CLOSE_WAIT state with pending bytes in the receive queue?  (we're trying to track down a problem that appears to be related to sidekiq, celluloid, or typhoeus, and seem to have intermittent problems with connections closed prematurely).
$ netstat -an | grep CLOSE_WAIT
tcp       32      0 x.x.x:y     z.z.z.z:443       CLOSE_WAIT
tcp       32      0 x.x.x:y     z.z.z.z:443       CLOSE_WAIT
tcp       32      0 x.x.x:y     z.z.z.z:443       CLOSE_WAIT
...


Filter hotkeys for specific windows

Is it possible to only register hotkeys for specific windows? The parameter HWND Window's API Function RegisterHotKeys (https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-registerhotkey) seems to implement this functionality.
How would someone use winapi-easy best to get a HWND to the processes main window and pass it to RegisterHotKeys?
Thanks for your help!

It surely should be possible, but not with RegisterHotkey. According to the docs, passing a window handle would only mean that the associated window would receive the messages, nothing more. The hotkeys would still be global.
So, implementing this would require other functions from the Windows API, something which I haven't looked into yet.
Constructing / getting a window can already be done with winapi-easy, though I consider the API for this highly experimental still. But you can take a look at the new_window and get_window_infos examples.


TST: Fix DrizzlePac align_multiple_visits

Currently, CI is failing because align_multiple_visits notebook uses glob to provide inputs for TweakReg. Unfortunately, glob order can be arbitrary and not well suited for the purpose of running it in a CI. The solution is to provide a deterministic list of input files via .lis file.
Related issues: #77, #78

You would also need to un-exclude the notebook so CI would pick it up again. I excluded it in 18ba024 .

align_mosaic might have the same problem, as it failed in an unrelated PR in #88.
https://spacetelescope.github.io/notebooks/notebooks/DrizzlePac/align_mosaics/align_mosaics.html

See #89 for the fix - currently WIP but hopefully this test will solve the issue we were running into.


Error on Windows

Hi!
Great software! Unfortunately, I'm getting an error on windows when SDR++ loads with the DLL in the folder.
Can you please help?
73!
Sasha VE3SVF

Yes, I'm getting the exact same error

@aero924 I was able to solve it by upgrading to the latest nightly SDR++ build


dev: return value of Starknet Messaging should be returned

In L1KakarotMessaging.sol, starknetMessaging.sendMessageToL2 and starknetMessaging.consumeMessageFromL2 are not returned.
They should be

Can I work on this @obatirou

hi @obatirou, can you please elaborate the issue further?

Message is removed with https://github.com/kkrt-labs/kakarot/pull/1623
Closing


feat: add file save listener for auto formatting TypeScript and JavaScript files using Biome

This update addresses a critical issue where the Biome extension was completely non-functional. Prior to this fix, the extension failed to perform any automatic or manual actions.

Hey @pageton,
Thanks for creating this PR
This is however already handled by VS Code using Format on Save (editor.formatOnSave), so I'm going to close it.
If you feel there's another bug here, please open an issue with a reproduction so we can discuss it.


IRGen: rework linking against CxxStdlib

Rewrite the handling for the CxxStdlib implicit linking to use a slightly more functional style for filtering.  Additionally, add Windows to the list providing the overlay.  The Windows linking scenario is a slightly more complicated as the library names differ between static and dynamic variants to disambiguate between import libraries and static libraries.  Take this into account when embedding the library name so that the linker can find the appropriate content.

CC: @egorzhdan @hyp

@swift-ci please test

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please smoke test macOS platform

@swift-ci please smoke test Linux platform


Update profiling tools

Small update where the major parts are:

a common cmake target called do-all-memory-profiling (added into bloaty, stackusage and heaptrack)
move profiling results from valgrind into common folder build/profiling/
added debug flag -g when running valgrind memcheck, so it's not dependent on cmake build type.
formatting

@RReichert, I've updated all profiling tools to support the variables working_directory and report_directory.
Also renamed code_profiling -> gprof, but I've kept the cmake variable CODE_PROFILING because of the -pg flags that get added to all libraries in the function target_code_profiling, so that those libraries don't get "polluted" when running the other profiling tools
Last, it was quite tricky to get the post_command to work in gprof, when generating a report, and it could probably be updated again but I need some input there.
Please comment a lot :)


Some youtube video can load but not be able to play

Hi @CookPete, first thanks a lot for the repo!! A totally random question (and it's also highly likely it's not related to the react-player component): it seems sometimes I cannot play some of the youtube videos using react-player, for instance: https://www.youtube.com/watch?v=n4wgXOoQ2mA
A couple of things worth noticing:

I can play it if I hit localhost but not from another computer. I'm able to load it but when I try to play I got error "Video unavailable". This can sort of be reproduced by hitting https://www.youtube.com/embed/n4wgXOoQ2mA directly. (However even with this url from youtube I can sometimes play it and sometimes not so it's really weird). The best chance to reproduce it is copy-paste the URL directly into the address bar. Clicking from here seems works.
When I use your demo app it can always play so that's why I'd like to see if you have any input on what might be going on. If you could share any hints/thoughts I'd really appreciate.

also if I use the sample video you have in the demo
"https://www.youtube.com/embed/oUFJJNQGwhk"
"https://www.youtube.com/embed/jNgP6d9HraI"
they have no issue to play even with copy-pasted url into address bar directly.

It seems when I deployed the app to Heroku then this issue is gone. I can now play the above the video. Thanks! Closing.


InlineQueryResult with more than one result in array.

I'm having difficulty getting the InlineQueryResult to send back more than one result.  I can return one result, and if using loop below it is always the second result of course.  I am not sure how to create InlineQueryResultArticle array of multiple objects within InlineQueryResult.  Do you have an example of one?
       List<string> tempString = new List<string>();
        tempString.Add("1");
        tempString.Add("2");

        InlineQueryResultArticle[] article = new InlineQueryResultArticle[tempString.Count];

        for (int index = 0; index < tempString.Count; index++)
        {
            article[index] = new InlineQueryResultArticle

            {
                MessageText = "Test Text",
                Id = inlineQueryId,
                DisableWebPagePreview = false,
                ParseMode = ParseMode.Html,
                ThumbUrl = "",
                Title = "Test Title " + tempString.Count

            };

        }

        InlineQueryResult[] queryResults = new InlineQueryResult[article.Length];

        for (int index = 0; index < article.Length; index++)
        {
            queryResults[index] = article[index];
        }

        var response = Bot.AnswerInlineQuery(inlineQueryId, queryResults, null, false, null);

Issue was that Id needed to be unique for each response, whereas I thought it had to match the incoming message ID.


fix: MYNW-114 Temporary hide bridge section from topup-page

MYNW team decided to hide bridge section from Topup page because the only one option here is Rainbow Bridge. Right now MYNW users can't use Rainbow Bridge because of lack of integration. Work in progress on this issue, but for now best option is not to confuse users and hide section.

@Patrick1904 Sorry, I'm refactored a little bit. Hope you don't mind

@Patrick1904 Sorry, I'm refactored a little bit. Hope you don't mind

Thanks @followdarko. Can you please just rebase this PR and make sure all usage of isWhiteLabel is correct after this change (some usage in latest release), and we'll this merged ASAP.

Outdated since Rainbow Bridge integrate support for MyNearWallet.


scrape users' information automatically

I planned to use the Instaloader to collect profiles' followees for my project, and I need thousands of profiles' information, therefore I hope I can get that information automatically. I have written some code to loop the function "profile.get_followees()", and it works. However, this only problem is I always met the '429 - Too Many Requests', so I would like to know except for use 'time.sleep(t)" to slow down the scraping, it there any better way to meet my requirement ( like change IP or proxy)?

When obeying the note at https://instaloader.github.io/troubleshooting.html#too-many-requests, 429 should not occur.
If you're logged in, the rate limit seems to be per-user, otherwise it's per-IP.

Yes, I found that the rate limit is about both per-user and per-IP, actually, I built a proxy pool and cookie pool to solve the 'request problem', and it really helps. Anyway, thank you for your reply and this great project!

Hey blrg87
can you share the code to loop between different proxy IP addresses.
i am trying to do it but unsuccessful.
this will be of great help
thank you


List item alignment issue

Category

[ ] Question
[x] Bug
[ ] Enhancement

Expected or Desired Behavior
The list items should be aligned in straight lines like shown in the content type sample.
Observed Behavior
The list items are aligned stacked. The issue only appears on some PC, but independent from browser (Tested with IE and Chrome)
Steps to Reproduce
Apply the pnp template provided in the content type sample on a SharePoint Online site. (FruitTemplate.xml) Result in screenshot.

Sounds like you may be floating your elements? Unfortunately floating items is not supported in List Formatting inside of the web parts due to some of the out of the box UI Fabric styles. Unfortunately, we cannot fix this.

Not sure, I used the template provided here:
https://github.com/pnp/sp-dev-list-formatting/tree/master/view-samples/contenttype-format
On Fri, Jul 24, 2020 at 3:29 AM Beau Cameron<EMAIL_ADDRESS>wrote:

Closed #151 https://github.com/pnp/sp-dev-list-formatting/issues/151.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pnp/sp-dev-list-formatting/issues/151#event-3582266053,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJF7Z5W7HOLMRR7O4IYJUDLR5DPWNANCNFSM4HLHW65Q
.


LASB-2974 Add GA4 Tag Ids for MLRA development, test and preproduction environments

Add GA4 Tag Ids for the MLRA application for development , test and preproduction environments.
Leaving production empty, to be included once all testing has been completed.
Terraform variable is: google_analytics_4_tag_id
Google Parameter Store variable name is: MLRA_GOOGLE_ANALYTICS_4_TAG_ID
Application environment/property is: APP_GOOGLE_ANALYTICS_4_TAG_ID
Jira: https://dsdmoj.atlassian.net/browse/LASB-2974

@nittagr @venkat980 @Ross-Nation
I have resolved the pipeline issues and moved the Google Tag Ids to the AWS Parameters Store, can you check once more and approve or otherwise let me know any additional feedback?


Flow on Windows: server keeps respawning

While we now have an IDE integration with WebStorm, it really is quite bad.
There is one point that I assume is in Flow's court and not the IDEs fault, so (in addition to countless - and usually ignored - tickets I created in Jetbrains ticket system for WebStorm and Flow) I post it here.
Because looking at Flow results in WebStorm is a) unreliable (sometimes they show up, often they don't), b) information is missing (only the first half of the error message, for example, only line #1 but not what it says about line #2), I often run Flow on the command line.
Now, a simple "flow status" should be enough, right? After all, WebStorm already has a Flow server process running. I assume though that that process suffers from the same problem.
The problem: Endless restarts!! Very rarely do I just get the current flow-status. In most cases I get "timeout, retry, restart, recheck", which takes forever. Sometimes I have to wait for "out of retries - error" to run it again to get a result.
Example:
$ flow
Launching Flow server for C:\Users\ME\Project
Spawned flow server (pid=6016)
Logs will go to C:\Users\ME\AppData\Local\Temp\flow\CzCzBUserszBMEzBProject.log
Launching Flow server for C:\Users\ME\Projects
Spawned flow server (pid=8992)
Logs will go to C:\Users\ME\AppData\Local\Temp\flow\CzCzBUserszBMEzBProject.log
The flow server is not responding (0 retries remaining): [processing] -
Out of retries, exiting!

Another example (it cycles between 4 or 5 different kinds of errors that all end in a new server being spawned - which doesn't last long before it too is replaced by the next one):
$ flow
Launching Flow server for C:\Users\ME\Project
Error: There is already a server running for C:\Users\ME\Project

Archive: flow.tar.gz

I run Flow from the command line and have the same issue

I run flow from the command line as well and am having the same issue, except mine just goes forever, never saying its out of retries.
OS: MacOS Sierra 10.12.3
Flow version: 0.39.0
Sometimes re-cloning the repo fixes it temporarily, but then it reappears. Makes it basically impossible to develop!

Same.
Launching Flow server for E:\Users\MegaMozg\code\github-issue-viewer-21-02-17
Spawned flow server (pid=9244)
Logs will go to E:\Users\MegaMozg\AppData\Local\Temp\flow\EzCzBUserszBMegaMozZgzBcodezBgithub-issue-viewer-21-02-17.log The flow server is not responding (0 retries remaining): [processing] /
Out of retries, exiting!

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run-script" "flow"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>flow: `flow`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>flow script 'flow'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the github-issue-viewer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     flow
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs github-issue-viewer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls github-issue-viewer
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\Users\MegaMozg\code\github-issue-viewer-21-02-17\npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run-script',
1 verbose cli   'flow' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'preflow', 'flow', 'postflow' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for preflow, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;E:\Users\MegaMozg\code\github-issue-viewer-21-02-17\node_modules\.bin;C:\Program Files\cmder\bin;C:\Program Files\cmder\vendor\git-for-windows\cmd;C:\Program Files\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Program Files\cmder\vendor\conemu-maximus5;C:\Program Files\cmder\vendor\conemu-maximus5\ConEmu;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\nodejs\;C:\Program Files (x86)\scala\bin;C:\Program Files (x86)\sbt\bin;E:\Users\MegaMozg\AppData\Roaming\OCamlPro\OCPWin\wrappers;E:\Users\MegaMozg\AppData\Roaming\OCamlPro\OCPWin\4.01.0+ocp1-full-mingw64-20160113\bin;C:\Program Files (x86)\activator-dist-1.3.12\bin;E:\Users\MegaMozg\AppData\Local\atom;E:\Users\MegaMozg\AppData\Roaming\npm;C:\Program Files\cmder\vendor\git-for-windows\usr\bin;C:\Program Files\cmder\vendor\git-for-windows\usr\share\vim\vim74;C:\Program Files\cmder\
10 verbose lifecycle<EMAIL_ADDRESS>CWD: E:\Users\MegaMozg\code\github-issue-viewer-21-02-17
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'flow' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 7  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec flow script
14 verbose stack Error<EMAIL_ADDRESS>flow: `flow`
14 verbose stack Exit status 7
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd E:\Users\MegaMozg\code\github-issue-viewer-21-02-17
17 error Windows_NT 10.0.14393
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run-script" "flow"
19 error node v6.9.5
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>flow: `flow`
22 error Exit status 7
23 error Failed at the<EMAIL_ADDRESS>flow script 'flow'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the github-issue-viewer package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     flow
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs github-issue-viewer
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls github-issue-viewer
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Using (latest versions) Flow 0.51.0 and Webstorm 2017.2 on Windows 10: The ever-crashing and Flow service (and respawning by Webstorm takes time and doesn't even always work) takes all joy out of using that combination. I have to go to a console and run Flow to see what's up.

Using Flow 0.53.1 and WebStorm 2017.2.2 (latest), very often (80%?) when there is an error reported by Flow (in the code) Flow crashes and has to be respawned. Which WebStorm doesn't always do automatically and there is no indication that Flow is dead, but that is something Jetbrains has to solve. These near CONSTANT CRASHES make it near impossible to rely on with the IDE, I have to run it on the command line all the time to get any use from it.

Yeah, I've heard from several other people that the WebStorm integration is problematic. Unfortunately, I think it's maintained by them, and they have said on twitter they have various custom behavior in the flow integration. I'm not sure if there's much we can do from here. They have said they are watching progress on the flow language server and hope to adopt new stuff as it's available.
(PS not true! There are actually fewer open issues than three days ago. I've spent a lot of the last three days combing through old issues to retry them on newer versions, mark them as fixed, or cross-link multiple reports of the same thing. As of now, only FB employees have the power to label/close issues, so it's a little slow for me to mark things and hope the original requestor closes them, but we're actually making progress.)

OT
@asolove As long as nobody gets paid for Flow related work nothing is going to change. Only the issues that Facebook projects benefit from have a "budget". That's such a general problem that I don't understand why companies like Github don't even seem to try to address it. Hoping for individual contributions for individual projects won't work (neither will hoping for volunteer work for any sizable project, such as Flow). Very discouraging, actually.
I would not mind a discriminatory policy such as "you don't pay into the subscription pool for the 100,000 open source projects from which we get paid, your so your ticket is low priority". Basing it all on volunteerism and hoping for the best has limits.  A lot of people needs this tools for "real" (commercial) projects, but we can't go and pay on an individual basis because the projects just are too numerous and too small.

Possible workaround?
I'm trying out this package: https://github.com/amilajack/eslint-plugin-flowtype-errors
It runs Flow as part of eslint checks, so if Flow crashes I hope to get Flow errors reported through eslint now.

I've tried Flow on a number of Windows 10 machines, all exhibiting the same issue over the past year. I agree with @sagar12861. This is a pretty major issue and while it exists, any mention of Windows support should link to this issue to prevent people from wasting their time.
Are there any Windows users that have not encountered this issue?

For what its worth, I was experiencing the same flow server infinite restart issue on OSX (same as @corinnaerin above).  Updating to latest version (v0.76) resolved this for me.
One thing to double-check, make sure you only have flow-bin specified in the root of your project and not in any other sub-directory package.json files.

Try to disable "safe write" in WebStorm. This works for me. All flow crashes are gone after this. (And if I enabled it again there is a tone of crashes, for example, if the code is syntactically wrong for a moment) I think this problem raises from WebStorm too fast delete temporary files that's it created for "safe write" purpose and something in flow itself. But it's only my assumption. I hope it helps you too.
Checked for flow 0.61 and 0.77

@lll000111 is there any solution for Windows+Webstorm?

@Aziaev Yes: I switched to working in a Linux VM — and now I switched to TypeScript. Experience: There is no (other) technical reason to make that switch, I wanted to be "mainstream" and its easier to get the rest of the team to adopt types now. Apart from these crashes Flow is at least as good and a bit more strict, and TS is not any faster or "better" (external lib defs excluded, they are much easier to get).

With Pycharm I am still getting this problem, even if I turn off "safe write"


Non semantic HTML id tag

The div wrapper for the slider has a slider id. An HTML document cannot have more than one element with the same id, so this become unsemantic when including multiple sliders to a page.

There is an id prop (which defaults to slider), maybe that's what you want to change ?

I absolutelly missed this prop, my bad.
However, I would default id to undefined (not have an id).

Change the id to undefined by default in 2.0.0 up.


Question about NewComponent and multiple invocations of the model constructor vmCreator per component instance

In component.go, NewComponent has a closure called vmfn, which calls the vmCreator function every third time it (vmfn) is invoked.  The intent seems to be call vmCreator once for each instance of the given component.
As near as I can tell, vmfn is called four times per component.
Is there a mismatch going on somewhere, or have I missed something, or what?
Thanks for this package!

vmCreator is called twice in the "init" lifecycle event, and then twice in Vue.prototype._initData, once as dataFn() and once as this._runtimeData().

yes, the multiple invocation of vmfn is on purpose for  vue.GetVM to work in components


Add LearningRateDecay to Adam

Is it possible to add a learning rate decay to Adam ?
I use it everytime.

Thanks!


[Suggestion] Add a "Glider Speed (2x)" cheat code variant for TotK

Good day.
I've been enjoying the cheats in this repo for Tears of the Kingdom, and I'd only like to suggest one.
Currently the only available one to modify the speed of the glider is the "Glider Speed (3x)" one.
While it works just fine, the only problem I have with it is that it makes Link go so fast in the overworld that it forces the game to load areas quite frequently, essentially freezing the game in place for a few seconds until it's done loading the assets.
I'd like to suggest the addition of a 2x speed modifier for the Glider, to more or less mitigate this problem by reducing the traveling speed to give more room to the game to load assets without triggering the loading freeze.
Thanks in advance!

Tried the 1.5x speed code in-game, and it works SO much better than the 3x one. The speed feels good without feeling too fast, and the loading freezes when the game loads new assets have been reduced a lot, I think I have only gotten time like twice or thrice since I tried them.
If possible, I'd like to suggest adding that Glider Speed code to the list of main codes for TotK, so users have more options when it comes to speeds like the other movement options do at the moment.

plz (For 1.1.1)   1.5x

Tried the 1.5x speed code in-game, and it works SO much better than the 3x one. The speed feels good without feeling too fast, and the loading freezes when the game loads new assets have been reduced a lot, I think I have only gotten time like twice or thrice since I tried them. If possible, I'd like to suggest adding that Glider Speed code to the list of main codes for TotK, so users have more options when it comes to speeds like the other movement options do at the moment.

plz (For 1.1.1) 1.5x

v1.1.1    super speed [ZR]   1.5x  plz ...

any chance you can make this for 1.1.0 and 1.20? please


language tag 'xml' is not applied consistently

for example, https://review.docs.microsoft.com/nuget/create-packages/creating-a-package has a .nuspec file that has no syntax coloring

Code blocks should all be marked now.


Fix bug in issue #79

Not working because
https://github.com/nbuilding/N-lang/blob/76a62fd7b9dde35cfdce1ba2b667f0993f8389f3/python/run.n#L1-L18
is invalid under the current code


future of library & maintenance

Hi there. I think dnd-kit is one of the best architected, most composable react dnd open source libraries around. However there are, as with all libraries, a good chunk of issues to contend with. I'm wondering if there are plans for the future of the library and its maintenance. It seems that after an initial burst of activity, releases have died down and pull requests and bug reports have gone unaddressed. Any insight into future plans/ maintenance/ roadmap etc would be very welcome

@clauderic Any input on this? Perhaps you could make a comment asking if anyone wants to join as a maintainer of the library, while you're busy on other projects.

Hey folks, thanks for inquiring about the state of the project. I want to reassure everyone that I'm still actively working on this library. The reason why a lot of issues have gone unaddressed for a while is that I have been working on a significant refactor of @dnd-kit since earlier this year.
Some of the key things I want to achieve with this refactor are:

Framework agnostic (adapt @dnd-kit to work with vanilla js, react, solidjs, vue, etc.) by building an agnostic layer that can be extended by concrete implementations, such as a DOM layer.
Keep most of the same core concepts, such as sensors, collision detection algorithms, and modifiers, but make the library easier to learn and adopt.
Making the core library extensible via a plugin system.
More granularity: Each draggable can have its own sensors and modifiers, and each droppable can have its own collision detection algorithm.
Reliability with unpredictable layouts
Performance improvements (reducing unnecessary re-renders being very high on the list, https://github.com/clauderic/dnd-kit/issues/1071, https://github.com/clauderic/dnd-kit/issues/994, https://github.com/clauderic/dnd-kit/issues/898 https://github.com/clauderic/dnd-kit/issues/943)
Better type safety
Leverage newer APIs like the top layer and View Transitions for browsers that support them.

Following progress
I am actively working on this refactor, and hope to have it released in the next couple of months, but there is still much work to be done and I'm not in a position to commit to a specific launch date at the moment.
If you are curious and want to follow progress, I am working on the experimental branch in this repository.
You can also take a look at the storybook which provides an overview of the use cases currently supported by the refactor, as well as some initial documentation for the APIs introduced in this refactor:

https://experimental--5fc05e08a4a65d0021ae0bf2.chromatic.com/
Keep in mind this is still in an experimental stage, so bugs are to be expected.
How can you help?
I am hoping to launch the refactor with React and Vanilla as the main two targets, and lots of APIs are still in flux, so it's a bit early to involve others in this refactor.
Having said that, if you would like to get involved, I will be looking for developers who have experience working in other frameworks such as Vue, SolidJS, Svelte, etc. to adapt @dnd-kit to work with those frameworks and maintain those compatibility layers. Since the library now exposes a @dnd-kit/dom package, adding support for other frameworks is mostly a matter of connecting the DOM layer to the framework, so the amount of effort should be relatively low.

Looks and sounds promising! 🎉
Once you are comfortable with outside contributions let us know in this ticket, I'd imagine there are more people willing to contribute. :)

Looking forward to the new refactored dnd-kit. This is an awesome library

@clauderic Excited to see this update! I'd be interested in contributing and being an early adopter, though we are mainly focused on a React solution if we can help in that area, with maybe a few vanilla use cases.
In the interim, if there are issues that we may need to resolve that need a change to the source code while the refactor is happening, would you recommend forking and opening PRs to backport when the time is right?

Hey @hussam-i-am, I will definitely be looking for contributors to help maintain the vanilla and React layers as well.
If there are any PRs that you think would be beneficial in the interim feel free to open them and ping me for review on them. I can't promise they will be ported over to the re-write but I am trying my best to keep feature parity (though not API parity).

Great, thanks @clauderic! As for the upcoming refactor, do you see it is an upgrade with breaking changes, or more like a new library requiring a rework of any existing usage?

Good question! I would say it depends on how much custom functionality consumers have built.
The current core library is coupled with the React implementation. With the new approach, there will be new packages you have to install depending on the target environment, so if you were previously using @dnd-kit/core or @dnd-kit/sortable, you would have to now use @dnd-kit/react and @dnd-kit/react/sortable.
For most consumers, if you have not deviated too far from what is provided out of the box (for example, using built in sensors and collision detection algorithms), while there will be breaking changes, the migration steps should be relatively straightforward to follow, and the APIs should feel very familiar (useDraggable, useSortable, <DndContext>, etc.)
For consumers that have built custom collision detection algorithms or custom sensors, there will be more work required to adapt them to the new APIs.
If you are using any experimental or undocumented APIs, it's more likely that these will change or no longer be supported.

Really a awesome library we are using it in live since a year. awaiting for more granular control on draggable n dropable feature to replace the react dnd with dndkit in our codebase.

We are also looking to further improve the accessibility experience for drag and drop, I know @dnd-kit/accessibility is already its own module, but curious if the plan is to pull it out of core or also make it more configurable, as it also has some undocumented API that we are using, for example, to pull the aria-live element out of the list elements.

I have been on the lookout for a good DnD lib with little luck in the Vue.js ecosystem. I would love to see this adopted for Vue.js with the new refactor. I will be happy to contribute to a @dnd-kit/vue version in the upcoming weeks or provide help in any way I can.

Waiting for the refactored version to come out. Might be a prerelease or beta release.

@clauderic I'm a maintainer of the popular react-beautiful-dnd fork @hello-pangea/dnd and I've been investigating your library recently. I love the concept of custom sensors, collision strategies, etc and support for grids is awesome. The only drawback I've run into has been performance which has me really excited about this update.
If you'd like any help with the new version you're working on I'd be happy to lend a hand 😁

Hi @clauderic - we're deciding which dnd to use and this looks to be on the top of the list but with a little uncertainty of the refactor. Is there any target date on this?

Hi @clauderic - is there any target date on the refactor?

The docs in the experimental version is a great improvement over the past. Thank you for your hard work! Can we start using the experimental branch?

Hi @clauderic, thank you for writing this library. It's very impressive! Sadly, I am also on the boat of the performance issue once reaching a certain amount of items. No matter how much I memoize, I am still left with significant lag, which is a major blocker.
I am particularly interested in the performance enhancement that AlissaVrk wrote: https://github.com/clauderic/dnd-kit/pull/1096
Any idea when the performance and multiselect will be merged? That would really help us plan for our release. Thank you.

I'm still unable to get the experimental branch examples working on any local test project. While the API appears to have been significantly improved, it seems that the performance considerations have yet to be addressed, based solely on the storybook examples - eagerly waiting for an update on this! @clauderic

@eephrati @tomasmenezes I've tested the new branch, the state management was rewritten, and the particular issue my branch addressed does not reproduce there.
good luck :)

@alissaVrk turns out my storybook-based performance concerns were caused by an external mac mouse extension. The performance seems to have improved significantly!

@clauderic any update ?

@clauderic Thank you so very much for the great library, looking forward for the updates.

@clauderic  Thanks a ton for the awesome library, we are really looking forward for the updates as we heavily rely on this library for our use case

If maintenance of dnd-kit will be stopped (I really don't hope so as I really like it, too), there is also a new kid in town ... Pragmatic Drag & Drop, which is the spiritual successor of react-beautiful-dnd (same company behind it). Just to provide a possible alternative for those with performance problems.

Pragmatic DnD is very much focused on using the platform, and the user-experience is tied to that (mobile is finicky). dnd-kit is an abstraction that doesn't use the platform for better experience, but less interoperability with things outside the browser window (other windows or the OS).
Just some notes on the difference between the two libraries. They are both good but have pretty different goals.

@clauderic I have been using this library for the past year and a half, and it has been incredibly useful, offering many features out of the box. However, I am experiencing significant performance issues related to unnecessary re-renders (#1071). As we are about to release our product, these issues have become critical.
During load testing, the drag and drop functionality becomes very slow with more than 200 elements due to the re-rendering of all items. Our flows contain over 500 draggable items. I have tried memoization techniques and other workarounds, but there has been no significant improvement in performance.
Please prioritize resolving this issue as soon as possible, as we urgently need a solution to proceed with our release.

@alissaVrk Can you please confirm if we can use the experimental branch until it is merged into the main branch? Our release date is approaching, and we need to implement some workarounds to avoid delays. Are there any potential issues we might face by using the experimental branch?

@TimFL I tried it with React 19 but couldn't even get it to work. Uncertain if that is due to our setup or the package itself.

@TimFL I tried it with React 19 but couldn't even get it to work. Uncertain if that is due to our setup or the package itself.

I tried with React 19 and mine works fine with no error. So maybe something wrong with your setup. Haven't tried the compiler yet.

@shridharrai sorry it took me time, not sure what you're asking. which experimental branch?

@alissaVrk I am referring to the experimental branch of the dnd-kit repo, which @clauderic  mentioned is being worked on to improve performance. Can you please confirm if we can use this experimental branch until the improvements are merged into the main branch? Our release date is approaching, and we need to implement some workarounds to avoid delays. Are there any potential issues we might face by using the experimental branch?
https://github.com/clauderic/dnd-kit/tree/experimental

@shridharrai I'm sorry, but I really don't know. I haven't written the code in the branch or used it for more than to verify that the performance issues don't reproduce there.
I assume that there are more changes in the experimental branch than just performance improvements though
I have created a PR a while ago from master that fixes most of the re-render issues, as far as I know it should be ok, so you can update this PR from master, test it and try to use it.
good luck :)

Hey folks, sorry for not posting an update here sooner, it's been a busy year. I've got lots of exciting progress updates to share:
Alpha releases
There's now frequent releases of the experimental branch. Here are the main three entry points:

@dnd-kit/abstract: This layer handles all of the abstract drag and drop logic that is decoupled from any concrete implementation, such as state management, lifecycle, collision detection, event handlers, and more. Most consumers will not interact directly with this layer. In the future, other implementations could be built on top of this layer, such as a @dnd-kit/react-native package.
@dnd-kit/dom: This package consumes the abstract layer and implements all of the DOM specific logic (event handlers, resize observers, mutation observers, intersection observers, scroll listeners, etc.). It exposes some classes that can be used in vanilla JavaScript, DragDropManager, Draggable, Droppable, and Sortable.
@dnd-kit/react: This package consumes the @dnd-kit/dom package and exposes hooks to make it easier to consume in React applications, such as useDraggable, useDroppable, and useSortable.

All of these new packages should be considered early alpha releases, so I would not recommend using them in production environments yet, unless you're comfortable with the risk of there being breaking changes in the near future, as the APIs are still somewhat unstable.
I'll be releasing frequent updates to the alpha releases (0.0.x) and working towards beta releases in the near future (0.x.x).
Documentation
There's a brand new documentation website, it's still a work in progress but should give you a good overview of how @dnd-kit will work in the future.

There's now interactive documentation for all of the different concepts:

I'm also working on writing several guides to help users get started and learn how to build common use-cases. One of the most frequent feedback I get with the current version of @dnd-kit is that it's too complicated to adopt, so I've been working hard to make sure that is no longer the case.
For example, I just finished writing an interactive guide on how to build multiple sortable lists (kanban boards). It now takes a fraction of the amount of logic to set up and should be much more straightforward to understand.

Roadmap
There's still much to do before this can be considered production-ready. Some of the things I still have on my roadmap include:

The new documentation is a good starting point, but still needs a lot of work:

The API reference is still incomplete, and there are many undocumented features.
Write more guides for common use-cases.

Streamline the migration for current users of @dnd-kit:

Writing a migration guide.
Introducing a <DragOverlay> component in the @dnd-kit/react package.

Add automated tests using Playwright to prevent regressions.
Finish migrating all of the current stories to make sure all of the current use-cases are well supported.
Better auto-scroller implementation.
Introduce more feedback strategies for draggable elements.
Work on the HTML 5 drag and drop sensor implementation for cross-window events.
And so much more!

How can you help
Testing out the new packages and reporting issues
While the current version of @dnd-kit has been battle-tested for years in production, these new packages still require thorough testing to identify and resolve any bugs or imperfections that may have been overlooked. If you run into issues with the new experimental packages, please let me know and tag the issue with the experimental label.
Contributing
I'm now accepting pull requests to the experimental branch. If you encounter any issues and wish to contribute fixes, don't hesitate to open a pull request.
I'm also still looking for contributors to help me build out support for other frameworks, such as introducing a @dnd-kit/vue package so that we can make sure the @dnd-kit/abstract library has all of the right APIs exposed, now that the APIs are a bit more stable.
Sponsoring
If you want to show your support for this refactor, consider sponsoring the development of @dnd-kit 🙏

@clauderic What an amazing update, thank you so much for all the hard work put into this!
I would love to join the Slack workspace, but it doesn't allow me. Are you able to provide access?
<email> doesn’t have an account on this workspace.

Try this link

Just wondering if we're all good to go with React 19 and @dnd-kit 6.1.0? Not the experimental. Had a bit of an issue. Cheers

Hello @clauderic, I am a big fan and appreciate your work over the years! I've been following your journey from react-sortable-hoc lol.
I was wondering if you had any idea of like rough ballpark timelines/estimates for any of this stuff. Are we looking at a production ready release in 2024, 2025, 2026?
we're currently migrating away from react-beautiful-dnd temporarily to @hello-pangea/dnd and are considering a full migration to one of of either pragmatic-drag-and-drop or dnd-kit.
you may or may not have also seen @Xhale1 's comment about collaboration since he's one of the co-maintainers of react-beautiful-dnd's successor @hello-pangea/dnd. as an outside observer and user of these libraries, it would be nice to see some unification under the two main paradigms that seem to be out there, libraries that leverage the "browsers built in drag and drop functionality" like pragmatic-drag-and-drop and libraries that are "not built on top of the HTML5 Drag and drop API" like dnd-kit.

A timeline will be much appreciated. Can we use the experimental branch in our development project?

The experimental branch had it's MIT license deleted 😭 . Hopefully it comes back, but def wouldn't want to ship something or devote resources (sponsorships, contributions) without it.

The experimental branch had it's MIT license deleted 😭 . Hopefully it comes back, but def wouldn't want to ship something or devote resources (sponsorships, contributions) without it.

Just an oversight, fear not. It's back.

A timeline will be much appreciated. Can we use the experimental branch in our development project?

You can already use the experimental branch yes, there are periodic releases to it but these are considered to be alpha releases. (0.0.x). As for a timeline, I'm currently aiming for January for stable releases.

@clauderic is it possible to add an extra layer of nesting to the kanban board (multiple containers)? For example, sorting items at the same level as containers? I have had a very hard time getting this working with the core library and I still can't get it to work properly, but the new library looks promising.

Hi @clauderic,  any suggestion for implement multi select on a sortable list with the new version?
Refer to this MR https://github.com/clauderic/dnd-kit/pull/588 . I was able to achieve it with the old version, but it didn’t work when I tried upgrading to the new version.
The storybook
https://5fc05e08a4a65d0021ae0bf2-yivpqsvbcy.chromatic.com/?path=/story/presets-sortable-multiple-containers--multi-select
thanks you

Any updates on being able to use this lib in react native ?


Can I use a new photo which is modified by PS to test this model?

Thanks to your interest in our work. I think you can have a try, but it would be a bit difficult for our proposed method to deliver a precise manipulation localization. However, i think the detection performance (e.g., binary classification) can remain effective.


Development preset Connection type can show wrong color

The Connection Types pane in Preferences sometimes shows the wrong color. DBeaver comes with a preset "Development" connection type which seems to have no color assigned. However, when Development is selected, there is sometimes a color displayed. It seems that if one selects a connection type with color x, then selects connection type Development, the color displayed (for Development) will remain x. For example, if I click on Test, then on Development, the color displayed for Development is green.
This affects DBeaver 6.3.0.

I can't reproduce this. Could you post some explaining screenshot/video?

I've created a screencast of DBeaver 6.2.5: https://drive.google.com/file/d/1T3CKL02uc8U-QVmczk4HUxOjRpTMTSeE/view?usp=sharing

Unfortunately I can't reproduce either. What is your OS and database?

@Chealer Could you please reopen the ticket if the bug appears in newer versions again?

Unfortunately not currently @kseniiaguzeeva

I believe that won't be needed. I upgraded my stand-alone DBeaver to 6.3.2 and cannot reproduce. I am therefore crossing fingers that this is solved.
I note a strange behavior in the Connection types dialog. In the table at the top, when a row is selected, the background color of its right column (Description) becomes white, no matter what color is assigned to that connection type.


CassandraAST::new needs to return Result Instead of CassandraAST

Currently it panics internally when it fails to parse but we need to be able to handle this failure in shotover instead of panicking.

Do you ahve a test case for this.

A test case is not possible as currently the API does not allow for error handling.
This needs to return a Result
https://github.com/Claude-at-Instaclustr/rust_cql3_parser/blob/93d12d0e488608de802bc3701bbc57414593d4dd/src/cassandra_ast.rs#L1967
This needs to bubble up the Err case instead of unwrap.
https://github.com/Claude-at-Instaclustr/rust_cql3_parser/blob/93d12d0e488608de802bc3701bbc57414593d4dd/src/cassandra_ast.rs#L1981

The parser makes a  best effort parse.  So even in the case of an error it
should return a result and a flag indicating there is an error in the
parse.  Cna you give me an example of a statement that panics?
On Mon, 28 Mar 2022 at 05:48, Lucas Kent @.***> wrote:

A test case is not possible as currently the API does not allow for error
handling.
This needs to return a Result
https://github.com/Claude-at-Instaclustr/rust_cql3_parser/blob/93d12d0e488608de802bc3701bbc57414593d4dd/src/cassandra_ast.rs#L1967
This needs to bubble up the Err case instead of unwrap.
https://github.com/Claude-at-Instaclustr/rust_cql3_parser/blob/93d12d0e488608de802bc3701bbc57414593d4dd/src/cassandra_ast.rs#L1981
—
Reply to this email directly, view it on GitHub
https://github.com/Claude-at-Instaclustr/rust_cql3_parser/issues/5#issuecomment-1080181485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVM5ARKL4EB5SZOWQD6IVEDVCE2ZZANCNFSM5RJXE6SA
.
You are receiving this because you commented.Message ID:
@.***>

I have added a test case in cassandra_statements.rs
fn test_invalid_statement() {
        let stmt = "This is an invalid statement";
        let ast = CassandraAST::new(stmt.to_string());
        assert!(ast.has_error() );
        let stmt = &ast.statement;
        assert!( match ast.statement {
            CassandraStatement::Unknown(_) => true,
            _ => false,
        });
        let stmt_str = stmt.to_string();
        assert_eq!(stmt.to_string(), stmt_str);
        assert_eq!( stmt.to_string(), match ast.statement {
            CassandraStatement::Unknown(text) => text,
            _ => "".to_string(),
        });
    }

This shows that an invalid statement does not panic and that a result returned as the statement and as the text in the CassandraStatement::Unknown is the input string.

Oh I see!
I missed that the error case was being handled as a CassandraStatement::Unknown.
In shotover we could just directly replace the CQL struct with CassandraStatement.
https://github.com/shotover/shotover-proxy/blob/d5f90a7d6ef6c414eec6bf931b505ce8bf18ec11/shotover-proxy/src/frame/cassandra.rs#L466


Investigate converting to stateless function for performance boost

See https://facebook.github.io/react/docs/reusable-components.html

Stateless Functions
You may also define your React classes as a plain JavaScript function. For example using the stateless function syntax:
function HelloMessage(props) {
return Hello {props.name};
}
ReactDOM.render(, mountNode);
Or using the new ES6 arrow syntax:
const HelloMessage = (props) => Hello {props.name};
ReactDOM.render(, mountNode);
This simplified component API is intended for components that are pure functions of their props. These components must not retain internal state, do not have backing instances, and do not have the component lifecycle methods. They are pure functional transforms of their input, with zero boilerplate. However, you may still specify .propTypes and .defaultProps by setting them as properties on the function, just as you would set them on an ES6 class.
NOTE:
Because stateless functions don't have a backing instance, you can't attach a ref to a stateless function component. Normally this isn't an issue, since stateless functions do not provide an imperative API. Without an imperative API, there isn't much you could do with an instance anyway. However, if a user wants to find the DOM node of a stateless function component, they must wrap the component in a stateful component (eg. ES6 class component) and attach the ref to the stateful wrapper component.
NOTE:
In React v0.14, stateless functional components were not permitted to return null or false (a workaround is to return a  instead). This was fixed in React v15, and stateless functional components are now permitted to return null.
In an ideal world, most of your components would be stateless functions because in the future we’ll also be able to make performance optimizations specific to these components by avoiding unnecessary checks and memory allocations. This is the recommended pattern, when possible.

401b81beda closes this.

Close 401b81beda. Conversion to stateless complete.


Fixed an issue of missing Backend key in configuration when application has no tasks

Fixed an issue of missing Backend key in configuration when no tasks are available for an application
If Marathon application has no valid tasks in existence (either because the tasks are in bad state or they are in the process of being started or shut down), the generated configuration is completely missing the Backend key entry for the bound Frontend, resulting in a 404 response from Traefik instead of the expected 503.

Refs #1689.

@dtomcej you probably want to have a look at this too.

This directly addresses the cause of the issue. I am totally on board with this. 👍  This is not a band-aid approach :D

@aantono Could you change the base branch to 1.4 and rebase? Thanks.

I'll give this one a quick whirl just to be sure some time tonight.

Should I rebase against v1.4 branch?

@aantono shouldn't be necessary: Traefiker (our bot) can handle this by now. If not, it'll complain. :)


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

@huypub : Thanks for your contribution! The author, @asgang, has been notified to review your proposed change.

@huypub : Thanks for your contribution! The author, @jeevansd, has been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author, @jeevansd, has been notified to review your proposed change.


Logger is not an interface

Describe the bug

The logger is defined as a class, but should be defined as an interface.
Reference:
Interface: https://github.com/ChainSafe/lodestar/blob/master/src/logger/interface.ts
Class: https://github.com/ChainSafe/lodestar/blob/master/src/logger/winston.ts

I think I mean't to implement info, warning and other methods to invoke single abstract method (exmpl. log) to make it easier to implement some log processing

hmmm, ok that makes sense

#241


Add offline message to IOU and Split bill and allow currency selection while offline

cc @chiragsalian
cc @tgolen and @marcaaron because of changes to processNetworkRequestQueue
Currently, requests that are sent offline and should not be retried are hanging since the promises never resolve. This PR should solve that and allow users to go through the currency selection, as well as see an offline error message on the confirmation page.
Fixed Issues
$ https://github.com/Expensify/Expensify.cash/issues/3792
Tests

Login to app
Kill internet connection
Click '+' and select Request Money
Verify that you can go through the flow and see Looks like you're offline. Please check your connection and try again. error message on the request confirmation page.
Dismiss the modal
Click '+' and select Split Bill
Verify that you can go through the flow and see Looks like you're offline. Please check your connection and try again. error message on the request confirmation page.

QA Steps
Steps above.
 Thank you so much for the awesome feedback - I really appreciate it!

Just to clarify, it seems like this PR is solving two separate issues?
Correct! The goal for 2 is to allow users to go through the IOU flow and get to the confirmation page while offline.

Updated! Changes to Network were reverted and the solution now implements a second selectedCurrency key.

Updated with requested changes! I will create a PR in Web-E renaming preferredCurrency to localCurrency in the API.

Updated!

Unassigning @MariaHCD as she's ooo for the next 2 weeks.

Hold removed here

Updated!

Nice catch @Julesssss and I'm also really impressed with your speed! Updated to prevent this edge case.

Leaving this to @marcaaron, as he also requested changes

Updated!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

I requested a CP for this PR as deploying it will fix this issue sooner.

🚀 Deployed to staging         in version: 1.0.79-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production         in version: 1.0.79-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging         in version: 1.0.79-5🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production         in version: 1.0.80-2🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


ModuleOptions are not inferred correctly

Environment

Operating System: Darwin
Node Version:     v20.8.1
Nuxt Version:     3.10.1
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/~/github.com/rinux55/nuxt-module-types
You can see that nuxt.options.publicRuntimeConfig does not contain the myModule with myComplexType: false | {a : string}, in module.ts:23
Describe the bug
When creating a Nuxt Module, according to the docs (https://nuxt.com/docs/guide/going-further/runtime-config#typing-runtime-config) the module options are generated with untyped. It seems to generate the types from the defaults object.
If you have more complex types, which cannot be inferred from the defaults object, it should be possible to declare an index.d.ts, according to the docs.
I am not able to get this to work. I've created a minimal reproduction. In the reproduction, I've added the index.ts to /src, but I've also tried adding it to /playground or /.
Additional context
No response
Logs
No response

Just creating an index.d.ts isn't enough.
I've updated your reproduction to show how to make it work:

https://github.com/rinux55/nuxt-module-types/pull/1

Thanks for your suggestion Daniel, this seems to work!