Replace postinstall script for npm packages with libc field in package.json

Prerequisites
We have a scripts inside ./npm that generates npm packages published on npm that allow for easier installation of tailcall cli on different systems.
Describe the bug

npm/post-install.js doesn't work as expected due to usage of the result of async call inside sync code. So, the final name of the package is wrong and no package is installed actually. The script came from https://github.com/tailcallhq/tailcall/pull/607
on linux despite system's libc both gnu and musl versions are installed (i.e. twice of required space is occupied)  and I can't run "tc" command probably due to the naming clash. The script from above in theory should fix the problem on linux but it's actually does nothing. At least on linux, on other os I expect optionalDependencies should work

Expected behavior
The easiest way to fix this would be using libc field as it is should be supported by npm and other package managers. At least swc uses this approach
After that the postinstall script could be removed.
The main concern would be only compatibility with legacy versions of npm and other package managers
Testing published packages
We want to make sure that everything will work as expected and we won't face new problems with that. To do that we may want to implement tests for published packages in ci.
The implementation could look like this:

for main target systems (windows, macos, unix-glibc, unix-musl) run test job
use local registry as verdaccio to run local registry in ci
publish npm packages in local registry (may require changing publish script to specify registry)
create temporary dir
install @tailcallhq/tailcall from running local registry
make sure that commands tc --version works
also show the output of npm ls -a to verify that only required packages are installed

@meskill can you review #633?

@meskill can you review #633?

Thank you, that looks good. I think now we need to verify that everything works on different platforms. I've updated the issue description with ci testing description. Would you mind giving a try to implement this as well?

Let me give this a try

https://github.com/tailcallhq/tailcall/blob/4566993e1c96932625311d443236f2c95e24d348/README.md?plain=1#L18-L20


Check availability of target as soon as a valid address is inserted.

Description
Currently, the getAvailability is only checked as soon as the user presses transfer.
Check getAvailability as soon as the address is input, and require/validate that the available is true.
Acceptance criteria

Check availability as soon as a valid address is inserted.
Show availability color-coded in the UI

Tasks

[ ]

Story Points

Is getAvailability checking the matrix presence?
If yes #150 could be closed?

Yes this will be checking the presence in matrix.
On Wed, Oct 9, 2019, 6:16 PM christianbrb<EMAIL_ADDRESS>wrote:

Is getAvailability checking the matrix presence?
If yes #150 https://github.com/raiden-network/light-client/issues/150
could be closed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/raiden-network/light-client/issues/218?email_source=notifications&email_token=AARKEJAB7KA5LXK7OCDWC33QNWONLA5CNFSM4IGQRHO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAXHDBQ#issuecomment-539914630,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARKEJDXRT3LDPGSJSZEVPDQNWONLANCNFSM4IGQRHOQ
.

Need to go through the user flow of the app and see at what steps the user inputs an address
Need to decide what system or color-coding to use for distinguishing available targets from non-available ones

Related to #600, #408: the same way I don't want to be bothered by paying PFS dialog & routes if there's just direct transfer, I don't want to be presented the PFS fees dialog if the target is offline, which can be done beforehand through this issue.

From @andrevmatos

How about 3-4s after last change in transfer in status, so if signatures keep being prompted (there’s activity) it’s delayed a little longer, and if it doesn’t change in 3-4s, may mean the transfer is getting stuck or slow, and then hide it


ublox_dgnss: 0.4.2-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository ublox_dgnss to 0.4.2-1:

upstream repository: https://github.com/aussierobots/ublox_dgnss
release repository: https://github.com/ros2-gbp/ublox_dgnss-release.git
distro file: rolling/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.3.5-4

ntrip_client_node

No changes

ublox_dgnss
* fixed dependc
* Contributors: Nick Hortovanyi

ublox_dgnss_node

No changes

ublox_nav_sat_fix_hp_node

No changes

ublox_ubx_interfaces

No changes

ublox_ubx_msgs

No changes

@hortovanyi presumably this PR is superceded by https://github.com/ros/rosdistro/pull/37361 and can be closed?

I am closing these PRs under the assumption that the latest release is the preferred one. Conflicts prevent these from being merged as-is anyway.


Verifying that new generated files are added to git.

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
We need to make sure all generated files are added to git.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Here is discussion about that.
Does this PR introduce a user-facing change?

NONE

/cc @alculquicondor


Allow lower-dimensional DistributedTree

Based on top of #905, and also for allowing using HyperGeometry classes in deal.II. With #905, we can already use BasicBoundingVolumeHierarchy but not DistributedTree.
This pull provides a means to make that possible but is mostly meant as a base for discussion and as a proof-of-concept.
The current implementation simply adds a second template parameter for the bounding volume type to use for the lower and upper BVH trees (since that seemed to be the quickest solution).
Of course, we could also template on the tree type directly and/or introduce new classes for a DistributedBoudingVolumeHierarchy or similar.

We'll need to talk about this one. Introducing BoundingVolume template argument right now would mean we'll need to carry it for a long time. I think APIv2 changes, like those in #900, would have to be merged first, and the interface to the DistributedTree will have to follow in some way. So I'd rather delay the decision to move on with this, and wait until we finalize the new API for a single tree.

We'll need to talk about this one. Introducing BoundingVolume template argument right now would mean we'll need to carry it for a long time. I think APIv2 changes, like those in #900, would have to be merged first, and the interface to the DistributedTree will have to follow in some way. So I'd rather delay the decision to move on with this, and wait until we finalize the new API for a single tree.

My preference would be to carry the functionality introduced in this pull request including the tests around without committing to backward-compatibility for the interface. For that matter, I'm happy to put it into an Experimental or Impl namespace.

Closing in favor of #1017.


Self signed certificate in chain

When attempting to use electron-packager, I receive an error:
Error: self signed certificate in chain

I receive this error because the network at work intercepts traffic for security reasons and seems to disallow downloading files through means such as node-gyp or whatever electron-packager is using.
I had this problem when first learning how to create node addons for Electron apps, which I worked around by being able to download Electron headers and pointing node-gyp to these headers.
As far as I can tell, there is no way to currently tell electron-packager where the Electron headers are located so that it can run without the self signed certificate error. Are there plans for such functionality?

I assume this happens when it tries to download the prebuilt electron binaries?

That's what it looks like. I have prebuilt binaries downloaded already, which I'd love to point to instead of it trying to download them anyway.

Did you try setting the --cache parameter?

I tried that and I get the same problem with the self-signed certificate in chain.
I am calling electron-packager as such:
electron-packager . RedBook --platform=win32 --arch=x64 --version=0.34.0 --cache="c:\users\greco\documents\electron0.34.0"

Just to be thorough, I assume the file electron-v0.34.0-win32-x64.zip exists in that cache directory?

It is unzipped there. It should be still in .zip form?

Pointed cache to the folder containing the .zip file. It now works without the self signed certificate errors.
Thank you for your help! That list of flags was a little confusing.


Discord Status

So im having an issue with the "discord_status":"..." not showing up correctly and I have as my snippet:
				{#if userPresence.discord_status === 'offline'}

					Offline
				{:else}

						{#if userPresence.discord_status === 'idle'}
							🟡 Idle
						{:else if userPresence.discord_status === 'dnd'}
							🟠 Do Not Disturb
						{:else}
							🟢 Online
						{/if}

and my  is:
	// check if the user is currently in VSCode
	$: inVSCode =
		userPresence?.data?.discord_status == 'dnd' &&
		userPresence?.data?.activities?.find((activity) => activity?.name == 'Visual Studio Code');

	// get the icon to display based on whether the user is listening to Spotify or coding in VSCode
	$: statusIcon = inVSCode ? VSCODE_ICON : currentActivity ? SPOTIFY_ICON : null;

	// check if the user is online or idle
	$: isOnline =
		userPresence?.discord_status === 'online' || userPresence?.discord_status === 'idle';

	// get the details of the user's current VSCode session
	$: vsCodeSession = userPresence?.data?.activities?.find(
		(activity) => activity?.name === 'Visual Studio Code'
	);

	// get the name and ID of the current file being edited
	$: fileName = vsCodeSession?.details?.match(/(?<=📁\s).+(?=\s\|)/)?.[0];
	$: fileId = vsCodeSession?.id;

	// get the line number being edited
	$: lineNum = vsCodeSession?.details?.match(/(?<=📝 Editing line ).+(?=\/)/)?.[0] ?? '';

	// construct the status message to display
	$: statusMessage =
		isOnline && inVSCode && fileName && lineNum
			? `Editing ${fileName} on line ${lineNum} in VSCode`
			: isOnline && currentActivity
			? `Listening to ${currentSong}`
			: 'Offline';
			```
So when I manually change the status to test it, it works via lanyard api and shows the correct status but, it change on my webpage.

Is anyone else having this issue or is it just me?

Also not to mention it shows im Editing line 75/625 for like an hour and im using the LeonardSSH.vscord extension on vscode.

are you using svelte or sveltkit?

This works for me but replace it with your values
{#if $data && $data.discord_status === "online"}

Online

{:else if  $data && $data.discord_status === "offline"}

Offline

{:else}

Do not disturb

{/if}

Thanks, Ill give it a try here in a min or two, just in for work. Thanks for you comment! 👍🏾

Ive tried that and it still dont update the discord_status at all. I even change my status left and right on purpose to see each time and it dosnt work no matter what from https://api.lanyard.rest/v1/users/625796542456004639. But when I go to @eggsy's doc it works on the fly on https://lanyard.eggsy.xyz/. This crap is giving me gray hairs without tailwind too:

{#if userPresence.discord_status === 'online'}
	🟢 Online
{:else if userPresence.discord_status === 'idle'}
	🟡 Idle
{:else if userPresence.discord_status === 'dnd'}
	🟠 Do Not Disturb
{:else}
	⚫ Offline
{/if}

That is what I have and the only thing thats working is the spotify. But for some damn reason the discord_status is not working and theres not 1 person in the svelte community or here even to help.

What does the discord_status label under anyways?
Also here is the full code I was using https://sourceb.in/R1nGgMPZzG

Use this one instead https://github.com/iGalaxyYT/svelte-lanyard

Sorry I've been away guys and I do thank you for your cooperation and help. @Ogooooo , I used the code you gave me which didnt work but I reworked and and got something else that will work. You can see it here which is similar to what you and I both have: https://codesandbox.io/s/svelte-lanyard-demo-forked-qtflmc?file=/App.svelte

👍


Unbound not resolving some keystonecollects.com subdomains until restart

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[ x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
So far I've only noticed this issue with the following subdomains:

www.keystonecollects.com
newmy.keystonecollects.com

Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Run nslookup www.keystonecollects.com
See ** server can't find www.keystonecollects.com: NXDOMAIN
Run nslookup www.keystonecollects.com <IP_ADDRESS>
See resolution

Non-authoritative answer:
Name:	www.keystonecollects.com
Address: <IP_ADDRESS>
** server can't find www.keystonecollects.com: SERVFAIL

Sometimes restarting fixes the issue and sometimes it does not.
Adding query forwarding entries for these two domains to forward to <IP_ADDRESS> allows these domains to resolve correctly.
Expected behavior
No restart should be required
Describe alternatives you considered
A clear and concise description of any alternative solutions or workaround you considered.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.7.8 (amd64).
Intel® Xeon™ E3-1225V5 3.3Ghz Quad Core
Network Intel® I210-AT

I also found that efile.keystonecollects.com is having this issue, too.
@kulikov-a well I just turned off dnssec support and my query forwarding rules, restarted unbound, and two of the three resolved but www. did not.

but www. did not

just a negative cache maybe? is it working now?
it looks like another effect of aggressive nsec (https://forum.opnsense.org/index.php?topic=38888.msg191480#msg191480)

Haven't noticed any more issues so I guess we can close this.


cannot open shared object file

hi, i built the image today but running it get this:
--- tmate/tmate-docker » docker run --privileged -e HOST=joo.local -e PORT=2222 -p 2222:2222 -t tmate-docker:latest
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/message.sh...
Add this to your ~/.tmate.conf file
set -g tmate-server-host <server ip/hostname>
set -g tmate-server-port <server port>
set -g tmate-server-rsa-fingerprint "55:fd:66:f4:3c:59:a9:f1:f7:c1:62:5f:f3:1b:39:b1"
set -g tmate-server-dsa-fingerprint "No"
set -g tmate-server-ecdsa-fingerprint "22:7c:41:05:42:b8:00:08:73:07:e5:eb:9b:e3:89:fa"
set -g tmate-identity
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 21
./tmate-slave: error while loading shared libraries: libmsgpackc.so.2: cannot open shared object file: No such file or directory
syslog-ng: error while loading shared libraries: libsyslog-ng-3.5.3.so: cannot open shared object file: Permission denied

attaching a shell shows that the libmsgpackc.so.2 file is there:
root@e2a8a2dc3e07:/# ls /usr/local/lib/libmsgpackc.so.2* -la
lrwxrwxrwx 1 root root     20 Sep 19 10:16 /usr/local/lib/libmsgpackc.so.2 -> libmsgpackc.so.2.0.0
-rw-r--r-- 1 root root 183733 Sep 19 10:15 /usr/local/lib/libmsgpackc.so.2.0.0

but i cannot find any libsyslog-ng-3.5.3.so file.

Hi @varac, thanks for reporting this issue.
I have no good internet now to debug this issue.
If you don't have time to make a pull request, i would suggest you to use the prebuilt hub.docker.com image at https://hub.docker.com/nicopace/tmate-docker
Will get on this ASAP

Solved by https://github.com/nicopace/tmate-docker/pull/9


Map: two points at same location

Hi,
I've been playing around a bit with NeoDash, and most features are very easy to use :)
One minor bug I found is in the map, if I have two nodes at the same location. In that case, only one of them is displayed, and the other just vanishes.

hi @JoridK ,
Just tried this as well and it seems to the same for me. How'd you suggest fixing this?
I'm having trouble coming up with a nice solution so that both are visible at the same time, any ideas?

The best I can think of is to put one point in a slightly wrong place next to the other, if two points have the same location (if there are more than two points, the third point would need to be offset in a slightly different direction, etc) . I think on most maps it will not matter whether it is offset by a couple of centimeters in comparision to real life.
In case it is critical for some use case, maybe you could make this feature optional?

Hi @JoridK ,
I thought a bit about your comment and came up with another idea. What about having a small number below the marker that appears when there's >1 point at this location. The inspect view after clicking will then show details on both nodes. I think this is also how other map libraries do it. What do you think?

Closed in 2.3


ImportError: No module named 'wsgidav.server'

pip install git+https://github.com/mar10/wsgidav.git
Installing collected packages: jsmin, MarkupSafe, Jinja2, PyYAML, WsgiDAV
  Running setup.py install for jsmin ... done
  Running setup.py install for MarkupSafe ... done
  Running setup.py install for PyYAML ... done
  Running setup.py install for WsgiDAV ... done
Successfully installed Jinja2-2.10 MarkupSafe-1.0 PyYAML-3.12 WsgiDAV-3.0.0a2 jsmin-2.2.2

wsgidav --version gives:
Traceback (most recent call last):
  File "/usr/bin/wsgidav", line 9, in <module>
    load_entry_point('WsgiDAV==3.0.0a2', 'console_scripts', 'wsgidav')()
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 568, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2720, in load_entry_point
    return ep.load()
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2380, in load
    return self.resolve()
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 2386, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
ImportError: No module named 'wsgidav.server'

I did not install cheroot, cause I want to use nginx as my webserver.
Edit: Well after I installed cheroot it gives the same error, wsgidav version 3.0.0a2 seems pretty broken to me. Call me a whimp, but at least 2.2.4 seems to give me back the version number I ask for

Thanks for reporting, should work now.
wsgidav --version -v

You don't need to install cheroot, but a WSGI compliant server is required (see here)
WsgiDAV comes with a builtin wsgiref,
wsgidav --root . --server wsgiref

but being single threaded is not fit for production scenarios.
cheroot, gunicorn, etc. may be  better choices.

This is confirmed working now, thank you for taking care of it!


Use innerHTML for buttonText option.

I want use font awesome icon for button - then i change innerText to innerHTML.

Closing due to no answer.


Camera Roll not returning any photos on iOS

I reported this bug in the react-native repo here at facebook/react-native#24140 , but they said to post it here.
🐛 Bug Report
When fetching photos from the Camera Roll on iOS by calling CameraRoll.getPhotos(), it always return an empty array of edges in the data. This problem is not present when I run it on Android nor in a Snack. I tried implementing the community version and the built-in version of the Camera Roll, but the problem persisted. I also tried running it on the iOS simulator, on an iPhone, and an iPad with no success.
To Reproduce

Create a new react native project (with react-native init)
Link the Camera Roll library
a. With the RCTCameraRoll library as described here from facebook's website
b. Or with the RNCCameraRoll library as described in your README
Add the permission keys in the Info.plist as described here from facebook's website
Copy paste the sample code from facebook's website
Run react-native start --reset-cache (Solved the problems I was having with metro)
Run react-native run-ios

Expected Behavior
I would expect the Camera Roll getPhotos function to return a populated edges array in the edges with the information/URI of images in the phones camera roll.
Code Example
Cannot replicate bug in a Snack.
With the built-in Camera Roll
Here is a repo with the code example. I also uploaded the iOS release app file to appetize.io, which does have the problem.
With the community version
Here is a repo with the code example. I also uploaded the iOS release app file to appetize.io, which does have the same problem.
Environment
Output of the react-native info command
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
      Memory: 18.59 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.12.0 - /usr/local/bin/node
      Yarn: 1.15.2 - /usr/local/bin/yarn
      npm: 6.7.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        API Levels: 21, 23, 25, 26, 27, 28
        Build Tools: 21.1.2, 23.0.3, 25.0.2, 26.0.2, 27.0.3, 28.0.2, 28.0.3
        System Images: android-28 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5<IP_ADDRESS>64788
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.1 => 0.59.1
    npmGlobalPackages:
      react-native-cli: 2.0.1

Thanks for reporting! I confirmed that there is a different set coming back, between older version of CameraRoll and the latest from RN core and the latest from RNC. There are images coming back for my device though, but it is a different set so I'm looking into this at priority.
I suspect it has something to do with one of the last fixes synched over from react native core https://github.com/react-native-community/react-native-cameraroll/commit/bc557cf1693ed40b9924e19bd6206255f1dcffcf
@JoshuaGross could you help us out with the reasoning behind PHAssetCollectionSubtypeSmartAlbumUserLibrary VS the original PHAssetCollectionSubtypeAny ?

Hi @bartolkaruza - bc557cf mentions that if PHAssetCollectionSubtypeAny is used, CameraRoll.getPhotos never gets to the end of the list of photos: no matter how far you paginate, there are always more photos, and it starts looping (we see the same IDs repeatedly). I'm not entirely sure why there was an infinite loop, though. Switching to PHAssetCollectionSubtypeSmartAlbumUserLibrary solved that problem and the returned photos seemed more correct; they seem to match iPhoto's "all photos" view, whereas PHAssetCollectionSubtypeAny didn't.

In my testing it wasn't entirely obvious to me that it's possible for us to return the exact same set of photos as in the past (between PHAssetLibrary and ALAssetLibrary, a lot changed). But I don't understand what would cause no data to be returned and I've never seen that in our many uses within Facebook, so any more information to reproduce would be helpful.

What kind of information would be useful to reproduce the problem, apart from the info from the initial post? If you guys can't reproduce it, I suppose it's a problem on my end, would you have any suggestion if it comes to that? (I've already cleared the cache of npm and yarn)

@JoshuaGross After reverting that linked change I still get no photos at all. No errors, no warnings, no photos. Do we have any other clues as to where to look for a workaround? I have an app that I want to upgrade to v0.59 but I can't because of this issue.

Found solution:
After poking around in the native code - RN 0.59.0 contains a breaking change:
You are now required to supply the groupTypes: "All" option when calling getPhotos like so:
CameraRoll.getPhotos({
  groupTypes: 'All', // undocumented requirement or results will be empty
  ...
})

If you omit groupTypes, a predicate (filter) will be applied such that no photos will be returned in some cases. It's possible this filter will show some photos but not all. This issue applies to both community version and RN bundled version of CameraRoll.
@JoshuaGross Could we default groupTypes to 'All' by default?

@BenJeau Does @scarlac's suggestion solve the problem for you?
@scarlac I would prefer a documentation change if it's a documentation problem. I have a concern that changing the default to all will fix the case where you want all photos, and break cases where you might want to filter to specific photos.
For what it's worth, this is the code in iOS that uses the flag. It may be worth revisiting this, but nothing sticks out to me as being problematic:
https://github.com/react-native-community/react-native-cameraroll/blob/bc557cf1693ed40b9924e19bd6206255f1dcffcf/ios/RNCCameraRollManager.m#L197

@JoshuaGross I'd be fine with a docs fix.
Current code example in README.md do not include this options (see https://github.com/react-native-community/react-native-cameraroll#example). I also see Expo snacks around the web not using this property, so we're almost guaranteed to have people fumbling for answers. If it's truly breaking, I think it deserves a proper mention.

@JoshuaGross Yep, that fixes my problem! Thanks @scarlac

@scarlac I changed my mind, I think it's worthwhile changing the default in this case, I'll just need to test a lot of things on my end to ensure nothing breaks at FB. Would you mind submitting a PR? Might be worthwhile submitting followup documentation changes to indicate that "all" is the default for that param.

Sounds good! I'll have a look on Monday, @JoshuaGross

@JoshuaGross and now there are some duplicate (since it returns every album), but when I put the groupName param to filter out the photo to only be from the 'Camera Roll' or 'Recently Added', no images are returned even though when this param is not specified, the images have either the 'Camera Roll' or 'Recently Added' value for group_name

@BenJeau does SavedPhotos work any better for you?

@JoshuaGross when I put SavedPhotos, no images are returned, weird

That's unfortunate. We'll need to dig into it more then - I'll see if I can do that Monday as well.

@JoshuaGross Sounds good, thank you. For now, I'll just filter the data after CameraRoll.getPhotos() gets called

Actually nevermind, the duplication stopped happening after rebuilding the project a couple of times without the groupName param and withgroupTypes: 'All'

@JoshuaGross did you see this commit on the RNC repo (that's not on RN core) ? https://github.com/react-native-community/react-native-cameraroll/commit/0d1059ef75889103382c26e2cc18b32c393943e0
It basically sets all as default on JS side.

@JoshuaGross PR up. Let me know what tweaks you want, if any.

When I try to specify a value for groupTypes (for example All or SavedPhotos) I get this weird error
ExceptionsManager.js:82 Invalid PHAssetCollectionSubtype 'savedphotos'. should be one of: (
    albumCloudShared,
    albumMyPhotoStream,
    albumRegular,
    any,
    imported,
    smartAlbumAllHidden,
    smartAlbumBursts,
    smartAlbumDepthEffect,
    smartAlbumFavorites,
    smartAlbumGeneric,
    smartAlbumLivePhotos,
    smartAlbumPanoramas,
    smartAlbumRecentlyAdded,
    smartAlbumScreenshots,
    smartAlbumSelfPortraits,
    smartAlbumSlomoVideos,
    smartAlbumTimelapses,
    smartAlbumUserLibrary,
    smartAlbumVideos,
    syncedAlbum,
    syncedEvent,
    syncedFaces
)

But If I try instead to specify one of the enums from the error such as 'Any' I get
ExceptionsManager.js:82 Warning: Failed params type: Invalid params `groupTypes` of value `any` supplied to `CameraRoll.getPhotos`, expected one of ["Album","All","Event","Faces","Library","PhotoStream","SavedPhotos"].
Bad object: {
  "first": 1,
  "assetType": "Photos",
  "groupTypes": "any"
}

Since I am not able to set groupTypes, I am getting back an empty array :/
Here is my code
    loadLatestImage = () => {
        CameraRoll.getPhotos({
            first: 1,
            assetType: 'Photos',
            groupTypes: 'any'
        }).then(r => {
            if (r.length > 0) {
                console.log('loaded image');
                this.setState({latestImage: r.edges[0]});
            } else {
                console.log('User does not have photos');
            }
        }).catch((err) => {
            console.log('Error loading latest image ' + err);
        });
    }

And I am using "react-native": "0.59.8". Any ideas?

@JoshuaGross

I am facing a problem with videos specifically. In my scenario, I have to save a file on cameraRoll and pick the last saved file from the camera roll to share it further.
iOS cameraRoll retains the video's original metadata and thus save the file with createdate and not with today's Date.
So when I pick the last saved file, I get someother file instead of the video I just saved to cameraRoll
Any help in this regards will be highly appreciable. it is bit Urgent. Thanks in advance.


Add tooltip code details

Just idly playing with tooltips here. Let me know what you think?
Some nice examples:

Some more suspect examples:

I was hoping I could improve the formatting here with some divider lines, which would especially help when we have both parameters and an output value, but Godot's bbcode implementation doesn't seem to support [hr], so we'd have to do a whole other thing with the custom tooltip scene (and that whole thing should really involve adding syntax highlighting anyway).

Another interesting example:

Personally I think this is too much information. I would want to get e.g. Justin's opinion as an educator.

Maybe the tooltip could include the minimum information and an option in the context menu would have the full summary

Converting to Draft until we get feedback from Justin or any other educator.


Question: FunctionalJS w/o OO?

Not a knock on anyone or any code, because I'm a functional programming wannabe.
However, I've been wondering if anyone knows of a functional JS lib that does not use new and also does not use this in the implementation.
What I really want to know is that even possible.
My apologies for this being orthogonal to λamda.

Does ramda use new/this?

there's a couple of places we might call a function in the context of this, but i'm not aware of any new

All the Transducer implementation (_xall, _xany, etc.) use new.
And I believe for the most part, where we are in the business of specifically creating functions (and not merely currying them), we pass this through.  That's not essential for FP, of course, but allows users to use Ramda-created functions as object methods if they desire.

@wayneseymour Yes it's certainly possibly.  And Ramda could avoid doing so if we were motivated to.  But we make a major distinction between our public API and our internal implementation.  We are trying to create a functional API.  But for various exigent reasons, our internal implementation is mostly imperative, and our Tranducers code actually has an OO implementation.  The use of this is only to allow users to more easily combine Ramda functions in their OO projects; it's far from essential, but is perhaps nice to do.
Would there be a particular practical goal to avoiding new and this, or it mostly of academic interest?

What I really want to know is that even possible.

It certainly is. new is merely sugar for the invocation of a constructor function and setting up the prototype based on the constructor functions prototype property. If you don't use prototypal inheritance any use of new can easily be converted to a direct invocation of the constructor function. And any method invocation can easily be converted to a plain function that takes the object as a normal parameter.
It's not even just possible it's pretty practical as well.

All the Transducer implementation (_xall, _xany, etc.) use new.

And they would be pretty easy to get rid of.

Would there be a particular practical goal to avoiding new and this, or it mostly of academic interest?

I highly doubt that! But if one can get over it ugliness I think it is in some cases the easiest way to use prototypal inheritance.

Wow, thank you all for the responses.
@CrossEye I cannot attend to this being academic as I've humbly come FP from Java.
As of late, I'm a full time JS engineer.  My initial reaction to FP was the recognition of a breath of fresh air.  Better yet, a breath of freedom from creating enterprise boring applications.
The practical goal is to simplify mental state.  There have been times in the past where I really felt my brain would come undone due to having to juggle so much state in large OO applications.

So far, I've attempted to solve problems with Underscore, Lodash, and now Highland is in heavy use at the office.
I'm wondering if highland is abstracting too much from me.  But alas, that is probably a question for another blog/post/issue.
Thanks gentlemen.


Use unified APIs to initialize and shutdown app layer and platform la…

…yer together
Problem
What is being fixed?  Examples:

The problem is the Matter*PluginServerInitCallback functions are currently implemented as if they are called once per process lifetime, which register delegates to platform, but CHIP stack init(chip::DeviceLayer::PlatformMgr().InitChipStack()) is handled in the application logic. For all server examples, if the CHIP stack is shut down and restarted (e.g. via PlatformManager::Shutdown and then a new InitChipStack, etc), those registered delegates might not valid

Fixes #11568

Change overview
Use unified APIs to initialize and shutdown app layer and platform layer together
Testing
How was this tested? (at least one bullet point required)

Test pairing with lighting-app and all-clusters-app on Linux and ESP32 platforms and confirm no regression.

This change is based on the discussion with @bzbarsky-apple @mrjerryjohns, the goal is to introduce a unifired API to initilize chip stack so that app layer and platform layer have the same life-cycle, init both or shutdown both together for all server examples.
After this change, each examples server shall not initialize the memory, platform layer, cluster layer separately, which could potentially solve the race condition during CHIP stack initialization.
Please note, I only apply this change to lighting-app and all-clusters-app right now, I will apply this change to all other example apps after we decide to proceed with this route.

Need to switch to a new solution based on offline discussions. Close it for now.


Fixes buffer resizing for PnR tools

Fixes https://github.com/The-OpenROAD-Project/OpenROAD/issues/2339
Fixes The-OpenROAD-Project/OpenROAD#2339

It's a good idea to open an issue first for discussion.

[  x ] Tests pass
[ x  ] Appropriate changes to README are included in PR

@antonblanchard Is this the right fix for https://github.com/The-OpenROAD-Project/OpenROAD/issues/2339?

@proppy Heads up

Does it also fix https://github.com/google/gf180mcu-pdk/issues/81 ?

Do we need the equivalent change for https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_sc_mcu9t5v0 ?

@antonblanchard Is this the right fix for The-OpenROAD-Project/OpenROAD#2339?

Yes it looks right to me.

Do we need the equivalent change for https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_sc_mcu9t5v0 ?

Yes, it does need the same fix.


python310: 3.10.0a3 -> 3.10.0a4

Motivation for this change
hopefully it's able to build wheels now...
https://github.com/pypa/wheel/issues/354 was closed, but we may need to update packaging and wheel for it to work.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/110445

1 package built:
python310

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110445 run on x86_64-linux 1

1 package built:

python310

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110445 run on x86_64-linux 1

1 package built:

python310

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110445 run on x86_64-darwin 1

1 package failed to build and already failed to build on hydra master:

python310: log https://termbin.com/e6yy

:/

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110445 run on x86_64-darwin 1

1 package failed to build and already failed to build on hydra master:

python310: log https://termbin.com/e6yy

:/

hmm, I don't have a darwin machine to verify that it works, and this is still an "alpha" build.

hmm, I don't have a darwin machine to verify that it works, and this is still an "alpha" build.

python310 wont be a stable release for at least another few months. So we still have time for darwin to "brought up to quality" before exposing the package set

python310 wont be a stable release for at least another few months. So we still have time for darwin to "brought up to quality" before exposing the package set


Error appear during product edit and extra attribute add

Error appear during product edit. Please check the error
Exception in ProductController.php line 169: Error in Saving Product: Invalid argument supplied for foreach()
Same error appears when we add an extra attribute to product

currently working on it. thanks

@testpratap bug has been fixed. Thanks once again.

Thanks
On Fri, Jun 2, 2017 at 8:33 AM, Purvesh<EMAIL_ADDRESS>wrote:

@testpratap https://github.com/testpratap bug has been fixed. Thanks
once again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mage2/laravel-ecommerce/issues/35#issuecomment-305676697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbonzZELV6h6L3VPuQpMKGtEiVchF1vDks5r_3tqgaJpZM4Np_Rn
.


add ClipboardEvent to lib/dom

Just for completion, this feature is actually experimental: https://developer.mozilla.org/en-US/docs/Web/API/ClipboardEvent
Since the newest flow version 0.26 reintroduced some deprecated / experimental features (with opt-in), it would be interesting how new features should be supported... maybe via the flow-typed project?
\cc @marudor

I would add this here - it is experimental, but included in browser for quite some time.
So adding it to the main flow types seems reasonable.

Because we already have DataTransfer the declaration could be as simple as:
declare class ClipboardEvent extends Event {
  clipboardData: DataTransfer,
}

Shouldn't this be fixed in Flow 0.74?

@iddan you have a commit hash or something that addresses this?

Yeah I think it's fixed in current Flow.


Go client with cryptographic verifications

I have implemented a golang client with all cryptographic verifications. Currently, what you see is a simple CLI client. I'm going to reorganized the code into reusable libraries.
https://github.com/the729/go-libra

Please add your great libra library / client with pull request. Cheers. Prost.


Laravel 7 support

@bubba-h57, could you please take a look on this PR?

Yea man, thanks for this.


"Back to Main Page" text is covering content.

I noticed this today, when opening a PDF, not sure what happened...

Is this resolved?

Hey! Haven't had a chance to pull latest docker image. Get out of work at 5:30, I'll let you know then!

Is this resolved?

Hey! Haven't had a chance to pull latest docker image. Get out of work at 5:30, I'll let you know then!

Yes, the issue is resolved for me now.

Running the latest app version 0.17.2, I can still see this same issue:

Also, I was wondering about the logo next to the page numbers. It seems a bit misplaced and - like the house icon mentioned above - links to the main page:

@Frooodle Should I open another issue for this? This issue is still there for me in the latest app version 0.19.1.

Re opened

@Frooodle Should I open another issue for this? This issue is still there for me in the latest app version 0.19.1.

Just to confirm if on chrome can you press f12 right click refresh button and do hard refresh and clear cache
Just to confirm it's using latest files

Yes, I have just repeated those steps on LibreWolf and Brave and the result is the same.
I guess the text is shown because it is defined (twice) here:
Back to Main Page
Back to Main Page

Maybe something like this would make more sense?
<button id="backToHome" class="toolbarButton hiddenLargeView" title="Back to Main Page" tabindex="30" data-l10n-id="back_to_home" onclick="location.href='/'">
Back to Main Page
</button>

Btw, this can also be seen when accessing the page from a mobile device or decreasing window size, so secondaryBackToHome is also shown:

If I delete the words after the ::before tag, in the edge console, it goes away.

If I delete the words after the ::before tag, in the edge console, it goes away.

It appears that I am using a different version than the latest one. I was using a template from Portainer. I am going to comment on their repo. Just wanted you to know it looks to be fixed when looking at this repo. frooodle/s-pdf:0.18.1

Is that "Back to Main Page" button even needed?
A user can always click the Stirling Pdf logo to get back to the home page.
It looks like since this is a link instead of a button in the code, it is being styled differently.

Is that "Back to Main Page" button even needed?
A user can always click the Stirling Pdf logo to get back to the home page.
It looks like since this is a link instead of a button in the code, it is being styled differently.

No it can be removed if anyone wishes to raise pr


Add test for KubeClient

Related Issue:  open-cluster-management/backlog#17247
Description of changes
Add test for GetConfig method in config package.

/retest


Using Least Privileged role

The instructions state that we need to sign in using a Global Admin account, Can we use a Conditional Access Administrator account ? this appears to be a better way that implements the least-privileged role concept
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 80005683-d3e5-aab5-2642-677a2ef96203
Version Independent ID: 6abac9a6-5472-62c3-5eae-fa39ecccd12e
Content: Enable Azure AD Multi-Factor Authentication
Content Source: articles/active-directory/authentication/tutorial-enable-azure-mfa.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

Thanks for bringing this to our attention. Your question has been shared with the content owner for further review.

@DeanGross Great point. I added alternative roles. Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue. #please-close

Step 1 still states that we need to be global admin, is that accurate?


Update README.md to reflect 4.0 App Store release.

Sorry we didn't get to this in time. Let us know if you find any other mistakes in our current README.


Fix ordering by numeric values when there is no index

This PR fixes a tricky bug that happens when running queries with an ORDER BY clause in which the field is a numeric value and there is no index for that field.
The bug happens because in plan.go in the the wrong byte-encoded representation of the value was used, and that does not tell if a number is bigger or smaller than another one. For example:
0 is encoded as []byte{128}
100 is encoded as []byte{228}
200 is encoded as []byte{128, 200}
Doing a pure byte comparison yields that 100 is greater than 200, because []byte{228} is considered greater than []byte{128, 200} by bytes.Compare().
To fix the issue, I exported the index.EncodeFieldToIndexValue() so the same function is used for generating the index and for ordering when there is no index.
I also changed tests in select_test.go, but only to put numeric values that would trigger the bug and to actually test ordering by numeric fields, with and without index; a case that was missing. The old tests passed without touching.

Good catch!


Headers are not passed to self.client.post in TestClient.request

The headers parameter is not passed further in TestClient:
https://github.com/blb-ventures/strawberry-django-plus/blob/6d120d3eb445d16bd24663c05fdf7471d14e38e2/strawberry_django_plus/test/client.py#L20-L32
In AsyncTestClient it's fine though.

@bellini666 thank you!


How to get started with KEDA for durable functions?

I want to use KEDA for durable functions, but in the doc only a few triggers are supported yet in KEDA, and not Durable functions triggers like ActivityTrigger or OrchestratorTrigger etc. I came across this repo, and tried to follow Getting Started doc, but it shows "Please make sure you have the correct access rights and the repository exists" error while trying to clone KEDA and durable scaler repos. Is this project still under development, or is it supposed to be an internal/private project? If yes, is there any other way to use Durable Functions in Kubernetes?

Adding @TsuyoshiUshio

Never mind, I cloned the repo using https instead of ssh as mentioned in the doc (should have tried this earlier). Thanks for replying, excited to try this out. Closing this issue for now.


BIC-232 # Uncaught Type Error when accessing model.attributes.currentForm

Interaction view now listens for route:beforechange event to ensure
cleanup of view happens on the old view, not the new one
Interaction view no longer removes its element from the DOM as jqm
expects to have control over its removal

LGTM :+1:

does this need UX review considering that its a bug fix?

I'm really torn. Strictly speaking, I think pretty much every change can impact the UX in some way, so in that respect it's probably good to grab a customer advocate for a minute.
That said, I've personally skipped the UX review for chores like ESLint fixes. Ultimately it's a probably a judgement call until we come up with hard rules on this. We had agreed in one of our earlier retrospectives that it was a good idea to get separate code and UX reviews for our work. /shrug
I do think bug fixes, especially when the bug fixes improves the UX warrants such a review. If only so that edge cases we might not have been considered can be explored, and so customer advocates are aware of the fix's position in the release pipeline.

Maybe we should ask about this at the next retrospective?

UX from Ray and rachel


Fix service name missing in 403 empty state

Fixes undefined in the title of this error state.

Codecov Report
Base: 81.83% // Head: 81.83% // No change to project coverage :thumbsup:

Coverage data is based on head (7a95c4d) compared to base (5dfc6ee).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 7a95c4d differs from pull request most recent head 8220d15. Consider uploading reports for the commit 8220d15 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   81.83%   81.83%
=======================================
  Files          34       34
  Lines         622      622
  Branches      157      157
=======================================
  Hits          509      509
  Misses        113      113

Impacted Files
Coverage Δ

...omponents/PresentationalComponents/ErrorHandler.js
25.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add missing group_barriers at the end of host scans.

This is required as the scratch memory might be reused with a different access pattern.

@hipSYCL-ci-bot test please


add datadog metrics to meadow and playground

@michaelpj for the rest of today I will be refactoring the nixops and terraform code so I was planning on pulling out a lot of duplication. In addition I will refresh the documentation in the PR for that as I might end up changing something.

Sounds good to me!


Unable to delete XPaths filters in SOAP operation

Describe the bug
When I import a previously exported SOAP project and I try to delete any Xpath I can't
To Reproduce

Create a SOAP Project
Create one response that filters the requests using xpath
Export the project
4 Import the project (in another instance of castlemock)
5 Try to delete the previously created Xpath in the exported project

Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):

OS: Ubuntu
Browser : Chrome
Version: docker image castlemock/castlemock:1.34

There is this error in the console:
Uncaught SyntaxError: missing ) after argument list
It is because the '  are not escaped in a case like this:
removeXpath('//Em[@R='abcdefg']')

Why not just send a PR?

Hi @anaperaita.
Thank you for reporting this bug. I will take a look at it as soon as possible. Most likely sometime during this weekend :)
Best regards,
Karl Dahlgren

Hi @anaperaita.
Thank you once again for raising this issue. Unfortunately, I haven't been able to reproduce this issue. This was a bug that was resolved in 1.34. I'm wondering if your browser might have cached the old JS file. Would it be possible for you to try to do a hard refresh on the page and see if that helps?
Thank you.
Best regards,
Karl Dahlgren

Closing this since we were able to reproduce this on a later version. The issue should have been resolved.
Best regards,
Karl Dahlgren


GEODE-9920: Switch String intergration tests to use JedisCluster.

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Looks good! We should no longer need two instances of Jedis in any of the classes. I was also wondering why we randomly added hash tags in some tests?

When we have multiple keys in a command, JedisClusterClient makes sure both key need to be in the same slot (requirements of cluster client.) Otherwise an exception would be thrown.


Absorb Escape Implementation

Hi author,
Thanks for the amazing work. I have read the newer version of your work and noticed that Absorb Escape Implementation could greatly improve performance. Could you please clarify this part of the implementation in the repo? If you haven't done it yet, do you plan to release it in the future, thanks.

Absorb and Escape is not in this repo as the paper is currently going through the review process. We might release it upon the publication of the paper.

Thanks for your answer!


Fix NullReferenceException if the connection string is missing RedirectUri

Can be easily reproduced with the following code:
new ServiceClient("Url=https://lanxess.crm4.dynamics.com;AuthType=OAuth;AppId=51f81489-12ee-4a9e-aaae-a2591f45987d")

@0xced  Thanks we will accept this change to our main branch.
We cannot accept this here, but will include this in the next Push from our internal repro.  Will close this at the time we push this.


Print lexographically largest subsequence of a string

💥 Proposal
The program will print the largest possible subsequence of the string which is lexographically the largest among all the possible subsequences in C++ language.
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


[android] Delaying offer display (offers initialization perhaps) after Software Updater logic is done

Ads are getting in the way of updating the app, perhaps also on other scenarios.
I guess the simplest way to avoid this is to do the call for ad networks initialization past any SoftwareUpdater logic. If a software update dialog is shown, we don't initialize it at all if the user agrees to do the update.
This would not be the case in Basic.
Looking at this code might also provide some insight on why sometimes ads are still shown.
My guess is that perhaps there's an error thrown along the way of Google Play initialization.
I think if such error is thrown, we should try the google play initialization a minute later and have some sort of "pending" state to show ads or not.
We had a fix on which ads were not shown by default, but this fix ended up in no ads being shown at  all, the solution is perhaps similar, but I'm almost convinced we should have a new state, that serves us as a "wait-and-see" state during google play services initialization

Update on thinking.
It seems the error manifests right after an app update.
Let's disable all offers during the first session right after an update.


[Experimental] Powerfulseal-agent

This work is based on #136 and #120 discussions.
I decided to build a proof of concept around this feature, and Powerfulseal-agent is the result.
Long history short. Powerfulseal-agent is a container packed with deadly tools (stress, tc, sysrq access). These tools are used by Attacks. These Attacks can be Listed, Deleted or Created with API calls. When creating a new attack you can customize it with a set of args.
Examples of Attacks? Right now CPU, Memory, Shutdown, and Restart attacks work.
More docs available here.
Cool things:

One container. Deployed on-demand or as a daemonset.
Easy to add new attack types.
Easy to add new attack surfaces.
REST API. It can be deployed/used by other projects too.
Small codebase.
Minimal setup.
Integration with Powerfulseal should be easy.
Works :)

Ugly things:

Some parts of the code
No requirements.txt
No packaging.
No docs.
No tests.
No retry errors in the API.
Container size.
(A lot of things)

I would love to hear your thoughts on this. I'm happy to answer any questions :)

As a note. Right now this lives in its own repo, but if its the right direction... I'm happy to move the dev work to the main repo :)

I love the idea! Added to my todo list to give your repo a try!

Hey, sorry for being slow at getting to this. Crazy times we live in.

I'm still interested in working on a production-ready version of this (almost complete rewrite, this was a POC :P)- if needed I can create some spec/formal description.
Did you have some time to give it a look? I feel this addition pairs well with the sidecar-model proposed for Network disruptions/attacks - and would like to remove the attack abstractions to further rely on the base tools (stress-ng... etc).
Actually this model is similar to the one that Service-mesh implements:

(with one daemon and multiple sidecars)

Nice, happy to see that we go forward with this idea :)
I'll allocate some time this week to write a more formal/concise proposal that hopefully can address the points that you cited.
Then, we can start ironing/discussing the details :blush:
(btw, your book looks awesome :rocket: )

As per our discussion, @dgzlopes, I think it would make sense to also check out whether it would be sufficient to do this with ConfigMaps and jobs, allowing us to stick to k8s primitives rather than having to build a lot of custom tooling. As you mentioned,  this kind of depends on whether jobs allow usage of nodeSelectors or not.
Below are some examples I put together as part of a PoC I did for k6:
k6.job.yml
  template:
    metadata:
      creationTimestamp: null
      labels:
        job-name: k6-1
        jobgroup: k6-performance-test
    spec:
      containers:
      - command:
        - k6
        - run
        - /test/test.js
        env:
        - name: K6_NODES_TOTAL
          value: "5"
        - name: K6_NODES_INDEX
          value: "1" // Likely not needed for this, I used this to be able to split load between instances of the job
        - name: K6_TEST_ID
          value: aaaabbbb
        image: loadimpact/k6:new-executors
        imagePullPolicy: IfNotPresent
        name: k6
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /test
          name: test-volume
      dnsPolicy: ClusterFirst
      restartPolicy: Never
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
      volumes:
      - configMap:
          defaultMode: 420
          name: k6-test
        name: test-volume

k6.configmap.yml
apiVersion: v1
kind: ConfigMap
metadata:
  name: k6-test
  namespace: default
data:
  test.js: |
    import http from 'k6/http';

    import { Rate } from 'k6/metrics';
    import { check, sleep } from 'k6';

    const failRate = new Rate('failed_requests');

    function getExecutionSegment() {
      const n = __ENV.K6_NODES_INDEX;
      const s = __ENV.K6_NODES_TOTAL;

      let sequence = [];
      for (let i=0; i <= s; i++) {
        sequence.push(`${i}/${s}`);
      }

      let output = {
        executionSegment: `${n-1}/${s}:${n}/${s}`,
        executionSegmentSequence: sequence.join(','),
      }

      console.log(JSON.stringify(output, null, 2));
      return output;
    }

    const segment = getExecutionSegment();
    export const options = {
      executionSegment: segment.executionSegment,
      executionSegmentSequence: segment.executionSegmentSequence,
      stages: [
            { target: 200, duration: '30s' },
            { target: 0, duration: '30s' },
      ],
      threshold: {
        failed_requests: ['rate<=0'],
        http_req_duration: ['p(95)<500'],
      },
    };

    export default function () {
      console.log(__VU);
      const result = http.get('https://test-api.k6.io/public/crocodiles/');
      check(result, {
        'http response status code is 200': result.status === 200,
      });
      failRate.add(result.status !== 200);
      sleep(1);
    }

So yeah, had a small (but productive) talk with @simskij  about this feature and he helped me rethink some concepts/approaches used on the Powerfulseal-agent POC.
We thought that maybe it's a good idea to use Kubernetes primitives for building this feature instead of building API's and fiddling with security.
How? Using Kubernetes Jobs and NodeSelectors.
Some benefits:

Remove the need for an API.
Fewer security issues - see 1.
No pull and no push - we can use Kubernetes!
Works if Powerfulseal runs inside or outside the cluster.
People can use their Chaos tools inside K8s (if they want).
We can fully manage the lifecycle with Powerfulseal.
We can integrate this as an extra action.
Easier to develop and maintain.

The idea is that you have some kind of Node action:
- nodeAction:
  # pick all master VMs
  matches:
    - property:
        name: "name"
        value: ".*master.*"
  filters:
    # only pick the VMs which are in UP state
    - property:
        name: "state"
        value: "UP"
    # and only pick a single VM
    - randomSample:
        size: 1
  actions:
    - job:
        # maybe we can have a default image with some tools - (?)
        image: powerfulseal_job
        cmd: stress-ng --cpu 4
        duration: 60s

And well, schedule jobs with certain commands/actions/stuff, to create Chaos on your nodes. Also, this would help power users that want to run their tools or craft complex attacks with the existing tools.
This approach would work too if we want to abstract that complexity from the users! We could build a thin layer on top of this with predefined CPU, MEMORY, stuff - attacks :)
Lifecycle? Powerfulseal can deploy these jobs on-demand, and collect the hanging ones when it finishes, or something happens.
To be fair, I prefer this approach - It's more flexible, easier to maintain/develop, and as powerful (or more!!) as my initial POC.
But... It's just another POV - we can dig further on this approach or follow the initial one @seeker89, I suppose there is no silver bullet!
(btw, @simskij helped a lot on this proposal. Thanks a lot!)

I'm excited to see what you guys come up with!
You might still need to communicate somehow - for example to cancel the experiment before its term, but the jobs idea does make things easier. Looking forward to some more concrete proposals!

I'm excited to see what you guys come up with!
You might still need to communicate somehow - for example to cancel the experiment before its term, but the jobs idea does make things easier. Looking forward to some more concrete proposals!

You make a solid point, for sure! If, for instance, the hypothesis of the experiment is disproved, we need to be able to abort prematurely and cleanly, likely even with the additional option of doing some kind of rollback action (not exactly sure how that would look in this case yet).


conv_transpose3d precision issues causing flaky tests for vmapjvp tests

test_vmapjvpall_nn_functional_conv_transpose3d_cuda_float32
Traceback (most recent call last):
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_internal/common_utils.py", line 1745, in wrapper
    method(*args, **kwargs)
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_internal/common_utils.py", line 1745, in wrapper
    method(*args, **kwargs)
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_internal/common_device_type.py", line 376, in instantiated_test
    result = test(self, **param_kwargs)
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_internal/common_device_type.py", line 761, in test_wrapper
    return test(*args, **kwargs)
  File "test/test_ops.py", line 774, in test_vmapjvpall
    self.assertEqual(loop_out, batched_out, atol=1e-4, rtol=1e-4)
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_internal/common_utils.py", line 2112, in assertEqual
    assert_equal(
  File "/home/circleci/project/env/lib/python3.8/site-packages/torch/testing/_comparison.py", line 1064, in assert_equal
    raise error_metas[0].to_error()
AssertionError: Tensor-likes are not close!
AssertionError: Tensor-likes are not close!

Mismatched elements: 1 / 10976 (0.0%)
Greatest absolute difference: 0.000102996826171875 at index (3, 0, 1, 3, 4, 3) (up to 0.0001 allowed)
Greatest relative difference: 0.008538899430740038 at index (3, 0, 1, 3, 4, 3) (up to 0.0001 allowed)

The failure occurred for item [0]

This is expected: convolution is non-deterministic. We probably want to relax the tolerance

Specifically, that's why this commit failed: https://app.circleci.com/pipelines/github/pytorch/functorch/1721/workflows/80f5785b-173a-4c0a-8c79-dbdfaa8a2ea8/jobs/10280

affected me too https://app.circleci.com/pipelines/github/pytorch/functorch/1834/workflows/61225e3f-d78e-4cc3-9feb-65789325a706/jobs/10947

So there is not an easy way to modify the OpInfo from outside of PyTorch core! The mechanism for overriding the precision for OpInfos is:

someone has to add a precision override into the OpInfo
but the OpInfo lives inside PyTorch core
We can easily hack this to work (by grabbing the OpInfo, monkeypatching its contents, then sending it to our test) but that doesn't feel very good

We can easily hack this to work (by grabbing the OpInfo, monkeypatching its contents, then sending it to our test) but that doesn't feel very good

Definitely something to think about long term if we're bumping things out of core but want them to use OpInfos. For now though we are already patching the OpInfo decorators for skipOps right? So we could build something similar for toleranceOverrides

Should be fixed by #560


Share gradient card image with social media

Share gradient card image with social media without card footer icon and even should share app link with image.

anybody want to work on this issue...

anybody want to work on this issue...

can you explain more about this

Share gradient card image with social media without card footer icon and even should share app link with image.

what i have to do actually
if you please elaborate

Share gradient card image with social media without card footer icon and even should share app link with image.

what i have to do actually if you please elaborate

@Kunal-deve1oper when user click share btn then user can share this card on social media like whatsapp, fb, twitter etc

Share gradient card image with social media without card footer icon and even should share app link with image.

what i have to do actually if you please elaborate

@Kunal-deve1oper when user click share btn then user can share this card on social media like whatsapp, fb, twitter etc

I can do it

I have added a view button which will display only the card which the user want to see and each card has an unique url which can be shared. I think it is good enough. please see the screen shorts

can I raise a PR

can I raise a PR

Testing me after that you can raise pr

Ok you can create a pr


Added isDeficient() function

Node v10.12.0
Fixes issue #17
Also added a validation folder for various input validations to avoid repetition of code.

Closing this PR due to merge conflicts!


updates to AMSI script

Fixes #652 #653

Looks like there is an formatting issue.

.build\CodeFormatter.ps1 -Save will fix both issues.

One oddity to note is that the shell continues to ignore certificate errors for some time after that setting is used. We seem to be caching the Invoke-WebRequest session or something, and I haven't found a way to make the $null immediately take effect. It would be nice if we could eventually address this somehow.


Update Composer dependencies (2024-07-03-00-18)

Visual regression test passed!
View the visual regression test report


Multisite production with SSL

I'm currently looking into using laradock to run two applications on a Ubuntu 16.04 VPS. These are run on two different subdomains (app.example.com and sub.app.example.com) and I want to enable SSL for both of them. Got it working on Nginx, but I'm looking to switch to Caddy since it should be easier to get the certificates.
I've followed the documentation here, but it doesn't seem to work. This is the error that shows up when running the container.
[app.example.com] failed to get certificate: acme: Error 400 - urn:ietf:params:acme:error:connection - Fetching http://app.example.com/.well-known/acme-challenge/codeforletsencryptchallenge: Connection refused
So, the challenge can't be accessed from the outside. Entering the address in my browser confirms that. I looked around on my server, but couldn't find the .well-known folder either.
Any clue what's going on or where the .well-known folder should be?

@paulpoot  u need change [app.example.com] to your domain name like [google.com]


Implement traces to allow for more flexible connections

This pull request is still work in progress, but I wanted to share it so that I get an opinion that I'm heading in the right direction.
The PR is related to the discussion in #38 and implements traces, which allow us to place connecting arrows on the perimeter of a diagram. For example, we are now able to draw something like this:

Currently, I have implemented traces for diagrams made out of paths (rectangles, regular polygons) and circles; for the rest of the diagrams, the trace defaults to the corresponding bounding box.
A remaining challenge is to make the traces work on named subdiagrams: currently, we can only retrieve the bounding box of a subdiagram, but ideally we want to access the (sub)diagram, such that we get its trace. I can take a stab at this, but I would like an opinion prior to doing that, since I expect to involve some sizeable changes.
Finally, I am aware that the geometric functionally of the library is poorly organized and likely confusing (we now have lines, segments, paths, trails, points, vectors); any advice on how to clean this up is appreciated.

This is really nice implementation. It's pretty clean as written and seems to preserve all the existing functionality.
My rec would be to commit this functionality, and then we should consider next steps.
For example, it seems like we should remove bounding boxes entirely as a first class object visible to the user? Align is now really trivial right (trace with unit vectors), and besides / atop as well.
That being said, there are some non-trivial cases (pad?) Also I like viewing bounding boxes, but we can add a show_trace as well which samples the trace around a diagram. A couple of the examples also use box arithmetic (tree for example).

Oh I guess padding is not so bad, it seems like Diagrams does this by padded Envelopes https://hackage.haskell.org/package/diagrams-lib-<IP_ADDRESS>/docs/Diagrams-Envelope.html#t:Enveloped (traces from the origin.) And you can get pad_l by composing with a projection.
This seems like the part of the library where the functional parts really shine.

Hello! Sorry for the late reply!

For example, it seems like we should remove bounding boxes entirely as a first class object visible to the user?

I don't think that bounding boxes are really exposed to the user, are they?
The main issue that I see with bounding boxes is that they don't compose well: we end up with loose bounding boxes after certain transformation. Let's consider the following diagram:
square(1).rotate_by(1 / 8).show_bounding_box()

If we were to add a small circle and rotate back with end up with a looser bounding box:
(square(1).rotate_by(1 / 8) + circle(0.05)).rotate_by(1 / 8)

Note also this doesn't happen if the transformations are applied in sequence (because we first compose the transformations, prior to applying them to the bounding box):
square(1).rotate_by(1 / 8).rotate_by(1 / 8)

Align is now really trivial right (trace with unit vectors), and besides / atop as well.

Yes, if I understand correctly this is also how diagrams implements the juxtaposition of two diagrams.
But I wanted to draw attention regarding an aspect. They distinguish between two primitives: envelopes (which roughly correspond to convex hulls) and traces (which roughly correspond to the boundary of the shape). I would assume these two behave differently for non-convex shapes, but I'm not sure if there other implications as well.

Interesting, I'll have to read some more. The definition of envelope looked superficially to me like a trace from the origin. I wonder if the convexity is enforced by initializing it as the convex hull for paths, and then only applying affine transformations.
One issue I see is that we currently allow shapes that do not intersect the origin. Think this would be not allowed.
In terms of exposing bounding boxes, we currently has "show_bounding_box" and "get_subdiagram_bounding_box" in the API. But we should remove them for the sake of interestingness.
Finally it does seem like we will implement a lot of 2d geometry. Wonder if it is worth bringing in a dependency for this? Scikit-geom is one possibility, but maybe overkill.

Actually a bit worried that envelopes might make cat extremely slow in Python, as the number of function calls for boundaries would grow with number of elements. Might be unwieldy without tail calls.
If we implement them, might consider having it be optional, or consider just allowing polygon boxes.

(Edit: realize that the need for union makes these pretty hard.)

As far as I understand envelopes are implemented as functions from a direction vector to a distance. The union of two envelopes is just the maximum of the two envelopes:
class Envelope:
    ...
    def __add__(self: "Envelope", other: "Envelope") -> "Envelope":
        return Envelope(lambda d: max(self(d), other(d)))

This is also illustrated in Figure 5 from the Monoids paper:

I think you are correct that we define Envelopes of basic diagrams and then the transformations will preserve them, that is:
envelope(transform(diagram)) = transform(envelope(diagram))

One issue I see is that we currently allow shapes that do not intersect the origin. Think this would be not allowed.

I'll need to think about this. I guess you are making this observation in the context of Envelopes, but I'm not 100% sure that this is an issue.

In terms of exposing bounding boxes, we currently has "show_bounding_box" and "get_subdiagram_bounding_box" in the API. But we should remove them for the sake of interestingness.

I would be inclined

to keep show_bounding_box since it is a useful utility and it doesn't return a BoundingBox, but a Diagram;
prefix get_subdiagram_bounding_box with an underscore to denote that it is a private method.

Finally it does seem like we will implement a lot of 2d geometry. Wonder if it is worth bringing in a dependency for this? Scikit-geom is one possibility, but maybe overkill.

Thank you for the suggestion! I'll check it out. I don't mind using an existing library, as long as it replaces most of the functionality that we have coded by hand.

Actually a bit worried that envelopes might make cat extremely slow in Python, as the number of function calls for boundaries would grow with number of elements. Might be unwieldy without tail calls.

I think we can cache the envelopes similarly to what we do for bounding boxes and to what is presented in Variation III of the monoids paper. Would that be enough?

One quick clarification regarding what I've said previously:

I would assume these two behave differently for non-convex shapes, but I'm not sure if there other implications as well.

In fact, the following example shows that the trace and envelope don't agree even for convex shapes (the green lines go outside the boundary):

Ah, that's very helpful. So to summarize.

Traces are an independent question from envelopes. We should probably just merge this PR, roughly as is.

We should remove Boxes from the public API. Particularly subdiagrams. For now we can replace connect with this implementation.

Envelopes are interesting but separate than traces. They solve the problems you showed above (and would also solve the tensor.py example in an elegant way, I think, since the cube would be enveloped).

Consider a lightweight geometry implementation to reduce library size.

I will read the papers to catch up with you 🤣

Good summary! I guess we can merge then. One small question: I haven't had the chance to rename the cardinals from north, south, etc. to top, bottom, etc. as you suggested in the other issue (#38). Should I still do it, or maybe it isn't that critical now that we won't expose the BoundingBox to the user?

I think an elegant way to handle these is by exposing unit vectors for directions? So N is unit_y  / NE is unit_x + unit_y? I think that plays well with traces? The paper makes a convincing cases that bounding boxes / envelopes should not in the end be used for connections.


Get Started with Microsoft Advertising

"Get Started with Microsoft Advertising" https://help.ads.microsoft.com#apex/ads/en/56873/-1

@tmamb Closing, due to lack of information.


怎么配置连接jira

我想要用casdoor来验证jira的登录信息，应该怎么配置

@dingchenzy plz modify all texts into English

hi,you can use casdoor java jdk to do it or I do it.

@dingchenzy see docs: https://casdoor.org/docs/integration/java/jira

Thank you


Fix autofilled text visibility in dark mode

Fixes #22087

The issue seems to be caused by Formatic UI, not directly from Gitea

The issue seems to be caused by Formatic UI, not directly from Gitea

Yup, so maybe it could only be overwritten by Gitea's CSS files, and it needs comments IMO

Changing the background would arguably be better, but this is good enough for now. I would expect browsers to eventually choose a better background color depending on color-scheme, which we already set.

The background of the autofill is chosen by Formantic UI here:
https://github.com/fomantic/Fomantic-UI/blob/27384cb4cb827221c336e95974a2bfbfb7ed29ee/src/themes/default/globals/site.variables#L1486

The background of the autofill is chosen by Formantic UI here: https://github.com/fomantic/Fomantic-UI/blob/27384cb4cb827221c336e95974a2bfbfb7ed29ee/src/themes/default/globals/site.variables#L1486

I see, so this is part of Fomantic's form module, which isn't exactly easy to get rid of, but it should be an eventual goal to remove it.


Duplicate x-axis values in outcome maps (Part 2)

Originally posted by @Zapiano in https://github.com/open-AIMS/ADRIA.jl/issues/442#issuecomment-1709423005
Hi @Rosejoycrocker, I did some investigation on this (to try to review it) and that lead to a conversation with @ConnectedSystems in which we agreed that you PR fixes a bug but there is another one happening there (so you may still get duplicate values eventually). Just to summarize the second bug: look at the behavior of the function quantile when the vector has some duplicate values:
julia> quantile([1, 1, 1, 1, 2, 2, 2, 2, 3, 3, 3, 3], 0:0.1:1)
11-element Vector{Float64}:
 1.0
 1.0
 1.0
 ⋮
 3.0
 3.0
 3.0

This probably has to do with how the default algorithm used by quantile works. It might be the case that the line X_q .= quantile(X[:, fact_t], steps) inside outcome_map function, at analysis/sensitivity.jl may have duplicated values but, because the values used to compute mean, max and min are bootstrapped, the y value in these cases are most likely going to be different - leading to two points with the same x value but different y values.
As this is a different bug (that might lead to similar problems), it may be solved in a different PR.

Also related:

[ ] #459


Replace ZeroInit with bytemuck::Zeroable

r3_core::utils::ZeroInit should be replaced by bytemuck::Zeroable. The latter is derivable (which helps us remove some unsafe impls) and has a better Rust ecosystem compatibility.
Zeroable is missing the following implementations:

core::atomic::Atomic{Bool,{U,I}{8,16,32,64,size},Ptr<impl Sized>} (https://github.com/Lokathor/bytemuck/issues/74)
Option<fn(Args...) -> R>
Option<&[mut ]_>
UnsafeCell<impl Zeroable> (https://github.com/Lokathor/bytemuck/pull/148)
[impl Zeroable + Sized] Zeroable requires Sized

Merged in b6de1c0466b44b4f5e3b5287d3490ec3043318ab


Garbage collecting tasks

I have test tasks that users iterate on by backtesting them until they reach a desired configuration and threshold. Once that happens, the task is upgraded to a production task which can be managed manually.
Not all backtested tasks will graduate to production, and some may be abandoned for a while and be worked on again. These build up so we'd like to be able to periodically and automatically clean up any tasks that haven't been run in the last X weeks. Currently I don't see a way to get the last modified time or last active time of a task. Is this available somewhere? These tasks backtest tasks would only ever be used to record and replay past data.
I could potentially add a "created" timestamp to the name of the task, but this feels a bit kludgy and might cause problems for tasks that are being actively worked on.

Those stats are not available but can be added: Would adding a created and last enabled date be enough, to implement the clean up code on your end?

It would. Assuming we can get a last recorded/replayed date for backtest tasks and last enabled date for production tasks we probably don't actually need/care for a created date. A last modified date instead would be more useful (a creation would count as a modification in this case). The goal here is to clean up tasks that haven't been used or modified recently.
Thanks!

@lpalm I am starting work on this. Just to make sure what I have planned will work....
I plan to add to dates to all tasks.

Last enabled date
Last modified date

What this means is that to find unused tasks you would search for tasks that are:

Not enabled
Last enabled date is more the X old
Last modified date is more the Y old

Depending on your needs. Note the a task make have really old enabled and modified dates but still be active because it is currently enabled and simply hasn't needed to change in a while.

@nathanielc that sounds good. If the created date is easy to keep, it would be handy for auditing/stats collection down the road. That's not a blocker and not as important as the enabled/modified dates, though.

I think it will be a good addition to add LastCollectedTime and LastEmittedTime for nodes, so you can find tasks that aren't in use or don't trigger alerts.

@yosiat we currently log both the batched/aggregated datapoints used as inputs to the alerts and the alert firing instances themselves into InfluxDB. This has some overlap with your use case (tracking emissions) and I believe will be natively supported soon (#286. we currently do it with a simple HTTP/JSON translator).

@lpalm I am talking about a streaming mode where we ingest directly to Kapacitor and where we don't want to save historical statistics to influxdb.
A simple dates for last collected and last emitted can be very helpful, for example: querying "/tasks" and find tasks with stream1 that didn't emitted for the last X days.


dask.dataframe.groupby with tuple keys fails

To reproduce:
In [1]: import numpy as np; np.__version__
Out[1]: '1.13.3'

In [2]: import pandas as pd; pd.__version__
Out[2]: '0.21.1'

In [3]: import dask.dataframe; dask.__version__
Out[3]: '0.16.0'

In [4]: df = pd.DataFrame(np.random.choice((0,1), (10, 3)), columns=list('abc'))

In [5]: df.groupby('b').apply(len)
Out[5]:
b
0    3
1    7
dtype: int64

In [6]: df.groupby(('b', 'c')).apply(len)
Out[6]:
b  c
0  1    3
1  0    4
   1    3
dtype: int64

In [7]: ddf = dask.dataframe.from_pandas(df, npartitions=2)

In [8]: ddf.groupby('b').apply(len, meta=int).compute()
Out[8]:
b
1    7
0    3
dtype: int64

In [9]: ddf.groupby(('b', 'c')).apply(len, meta=int).compute()
...
ValueError: Wrong number of items passed 0, placement implies 5

We just hit this - just a heads up that figuring out that tuple vs list was the issue was not straightforward! The error messages we got were ValueError: Multiple levels only valid with MultiIndex and IndexError: Index ... is out of bounds for size x.

The issue in https://github.com/dask/dask/issues/3047#issuecomment-355595521 is still present (I actually get a SystemError now, fun). But I think given pandas' difficulties with handling keys as tuples I'm comfortable ignoring it now.
The original issue of specifying a list of keys as tuples currently (correctly) raises in both pandas and Dask.


Settings default leading class with TW Merge not working

Hi there,
first of all, this plugin is great! I do have a small issue tho...
It looks like tw merge is removing my leading class, while I don't have a leading applied with fluid. I also don't use the fontSize from fluid, as I don't want the default line-height to be set. I always wondered why tailwind adds this out of the box, since this is in most project far from ideal... But that is another topic :)
cva("font-bold leading-tight", {
    variants: {
      level: {
        1: "~text-[3.815rem]/[5.61rem]",
        2: "~text-[3.052rem]/[4.209rem]",
        3: "~text-[2.441rem]/[3.157rem]",
        4: "~text-[1.953rem]/[2.369rem]",
        5: "~text-[1.563rem]/[1.777rem]",
        6: "~text-[1.25rem]/[1.333rem]",
      },
    },
  }),

As you can see in the image above, there is no leading class in my element.

Update
Thanks to #18 I found a workaround by adding ! in front of my leading class. Of course not what I really want as adding !important is really bad IMO.
Still like to see this working out of the box :)

Nice catch! I'll look into supporting this.


[<IP_ADDRESS>] Create DTs, DSs & ORs.

Issue Details
Description
To Create Data Transfer Requirements (DTs), Data Storage Requirements (DSs) and Other Requirements (ORs). This is a subset of the Non-Functional Requirements to help specify additional important requirements based on the above mentioned topics.
Success or Completion Criteria
A list of Non-Functional Requirements (NFRs) based on these 3 types of NFRs.

[x] #73
[x] #77

Allocated Time
4 days
Start Date: 08/09/23, 0000
End Date: 13/09/23, 2359

Issue Comments
Description
Successfully completed list of Non-Functional Requirements
Changes to success or completion criteria? y/n (if y, describe)
n
Start Date: 08/08/23, 0000
End Date: 13/09/23, 2359


Regressions

I didn't inspect the implementation details since I don't know the mathematical details but it looks fine to me.


Mobile 1713 choice - Improve choice results in the app

Swapped the choice results in the app to using chart.js.
Unsure how to deal with the strings that are not being used anymore, some help on this would be appreciated.
Test:

Create a choice activity, allow the choices to be published.
Log in as students and vote on the choice activit.
Log in as person who can see the results.

Found some mistakes, with npm-resolver and users being displayed when choice is not published.


Regression in average_frame_rasterizer_time_millis  mac_android_imagefiltered_transform_animation_perf__timeline_summary

https://flutter-flutter-perf.skia.org/e/?begin=1616720329&end=1617270843&keys=X16d58f4952fb3a99f57c42ade1611418&requestType=0&xbaroffset=23345
Starts at https://github.com/flutter/flutter/pull/79167 and does not drop to baseline, although previous benchmark runs had hit this peak. Maybe a device issue in the lab? I don't think the commit here would cause this.
/cc @flar, this week's engine sheriff.
The commit in question is one from @jonahwilliams if he wants to comment on my hypothesis that it's not actually that commit. Feel free to remove the tool label if I'm correct.

Also seen on other benchmarks at https://flutter-flutter-perf.skia.org/e/?begin=1616715843&end=1617270843&keys=X1ac9e25bb824cb5d3f915c8434fa33ad&requestType=0&xbaroffset=23342, which is another benchmark formerly bimodal.

Do these benchmarks use the gallery? There was a gallery roll in the commit before #79167 at https://github.com/flutter/flutter/commit/4d54b8966a0f2244a2d4416c0d728f903fc82f40

No - this benchmark is built from https://github.com/flutter/flutter/tree/master/dev/benchmarks/macrobenchmarks

I don't see any reasonable way the tooling change could have triggered it (of course, there are always some unreasonable ways...)
Since this is an android test it would also be unrelated to the iOS version update

Bisected this to https://github.com/google/skia/commit/de3cb0b454e8ab79967bfd21d48443c2538d3c7d
@bsalomon

This is not entirely unexpected. The change is an expansion of a driver bug workaround. It will only affect Adreno 4xx devices and very old/rare Tegra2/3 devices. It's possible we could claw this performance back in the future, but it will take some significant refactoring in our texture allocation to make that possible.

@bsalomon Would it be possible to devise an issue in the Skia bug tracker that details the work needed to claw back this performance? The current regression makes the frame time get very close to the frame interval on this device. Earlier, this was well within budget.

Sure thing. filed skbug.com/11833 for the longer term fix and skbug,com/11834 to see if we can narrow the set of affected devices in the shorter term.

skbug.com/11834 is now fixed, which limits the workaround by driver version. If the test device has been upgraded from Marshmallow (shipped OS) to Nougat (latest available update) it should see the performance go back to the previous level.

The bot must be running Android N because the performance has recovered.

So it has


Multi stage build

Switch our Dockerfile to use a multi-stage build in an effort to reduce image size, maybe improve builds times, and hopefully reduce the potential number of CVEs.
Image size has shrunk from ~1.56GB 👉 700MB.

Does the deploy-preview step require us to include curl and jq in the final layer? Not really a bug deal if so

Does the deploy-preview step require us to include curl and jq in the final layer? Not really a bug deal if so

Yeah it does. I'm just now taking a look at adding a separate layer to target that step.

One possible improvement from a vulnerability scanning perspective would be to add apt purge --assume-yes linux-libc-dev in the final layer. It won't save space, but it will avoid a buncha useless CVE warnings.

Nice one. I'm definitely keen to wipe out CVE warnings so for sure I'll follow up with this.


Android Teams App can't resolve @mention token from Power Automate

Power Automate:

Desktop:

iOS:

Android:

@SergeyGrayman - Could you please share your flow zip package for reference. Its help us to repro the  issue.

@SergeyGrayman - We are able to repro the issue at our end and have raised the bug for it. Concerned team is looking into it and we will inform you once get any update.

Any news on this bug?

@SergeyGrayman - Engineering team is working on it. Right now we don't have any ETA to share. We will let you know once we get any update.

Any update ?

@Snoxfox - Engineering team is looking into this issue.
Currently we do not have any ETA to share but we will let you know once we get any update from them.

Any update ?

@SergeyGrayman, @Snoxfox - This bug has fixed now. Could you please update the Teams version and check again.


[Question] Loading 4D Ultrasounds

Describe the Bug
I’ve been attempting to load in a DICOM of a 4D ultrasound (multi-frame sequences across the axial, coronal, sagittal planes) into the OHIF viewer, but I get a black canvas/thumbnail with a “Unsupported displayset” message. This same DICOM can be viewed in 3D slicer, which is where I exported the file from.
Is the viewing of 4D ultrasounds even supported or am I misplacing my efforts? Also, if I am able to get this resolved, my goal was to be able to perform segmentation across each of the frames in each of the views. I understand segmentation is not supported for US at the moment, so I was wondering what issue is preventing that feature from having been rolled out already.
Thank you for your time in advance!
Steps to Reproduce

Load in 4D US DICOM
Open Basic Viewer

The current behavior
Empty thumbnail and canvas with a "1. Unsupported display set." message
The expected behavior
If viewing 4D US is indeed supported, I expect to see 3 different views loaded in (each being a sequence).
OS
macOS 14.3
Node version
18.13.0
Browser
Edge (122.0.2365.59)

We are adding some 4D support very soon, see here
Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?


Sound markers and related events

Add the ability to specify markers in sound assets that trigger events when they are reached during playback.  This would be particularly useful to restart a song at a particular point on the next ball after a ball drains.  Markers should be specified at the sound asset level at a particular number of samples or time.  Optionally, one or more events to be emitted should be listed under each marker.
Markers should also be able to be used as start points in a sound (optionally provide a marker in the play method).

Implemented in 0.31.


[Program]: Write a Kotlin program to find lcm of two numbers by recursion

Description
Write a Kotlin program to find lcm of two numbers by recursion
LCM (Least Common Multiple) of two numbers is the smallest number that can be divided by both numbers. For example, the LCM of 15 and 20 is 60 and LCM of 10 and 15 is 30.
Input  : 12 18
Output : 36

How to contribute

Save the solution in program/program/find-lcm-of-two-numbers-by-recursion/FindLcmOfTwoNumbersByRecursion.kt file

!assign


refactor: update desc when pass --diff option

show diffed files when pass --diff options, otherwise show staged files

Thanks for the PR! Can we use changed instead of diffed though?

Sure, I will update the PR

I don't know why these CI fails. Could you please review again? @iiroj

The MR test failure will be fixed in https://github.com/okonet/lint-staged/pull/1200