limits are in wrong position

when the page loaded limit numbers are in wrong position.

If when you change the value of the slider, they all get positioned correctly, then see #164. Otherwise, can you reproduce it in a JSFiddle example so I can have a look?

yes after change it fixed. and #164 fixed it. Thanks


v0.5.2 does not have the "open" tag anymore

Describe the bug
The open-tag introduced in #237 is no longer available as of 0.5.0. Can we re-introduce it? It's a killer feature in my opinion.
Reproduction
Open a test file. The "@vitest:open" tag is no longer there.
System Info
N/A

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Curious as to the p2-nice-to-have, as it is technically a regression right? It's an advertised feature that is being removed, I suppose?
And if that's the case, we should at least remove its reference from the README.md. But very sad to see this one go in that case 🙁

Just reimplement it, 0.5.0 is a pre-release, it doesn't have half the functionality we had before.


Guide for LinkedList

Dear @aaryahjolia  ,
I hope this message finds you well. I want to request the addition of my files about LinkedList to your repository. Please, assign this issue to me.

I want to contribute on this issue ,  i can include the most important concepts of linked- list along with good explanation . please assign this issue to me


When creating a new project, creating a new folder causes a crash

Godot version
v4.0.alpha.custom_build.7bb963efe
System information
Linux 5.13.0-52-generic; Lubuntu 21.10 (Impish); ASUS ImagineBook
Issue description
When creating a new project, Godot crashes immediately upon creating a new folder.
I have confirmed that I have free disk space, and that the specific renderer doesn't matter.
[BEGIN crash dump]
(base) gregk@imaginebook:~/Code/adas_adventure_build_environment$ ./do_edit_game_linux.sh
Godot Engine v4.0.alpha.custom_build.7bb963efe - https://godotengine.org
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

Vulkan API 1.2.162 - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics 615 (AML-KBL)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.alpha.custom_build (7bb963efe9083662baa356f56a2d5c368b96a9a0)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f42a0d63520] (??:0)
[2] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x1a7c655) [0x55ee442ef655] (??:0)
[3] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x1a6d6f5) [0x55ee442e06f5] (??:0)
[4] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x477bfe6) [0x55ee46feefe6] (??:0)
[5] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2afa83a) [0x55ee4536d83a] (??:0)
[6] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x477bfe6) [0x55ee46feefe6] (??:0)
[7] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2a4e632) [0x55ee452c1632] (??:0)
[8] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2a4f5c9) [0x55ee452c25c9] (??:0)
[9] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2a4fa4c) [0x55ee452c2a4c] (??:0)
[10] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x29c98de) [0x55ee4523c8de] (??:0)
[11] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x29de6b9) [0x55ee452516b9] (??:0)
[12] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x29e6eca) [0x55ee45259eca] (??:0)
[13] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2a0b036) [0x55ee4527e036] (??:0)
[14] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x2a19786) [0x55ee4528c786] (??:0)
[15] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x9dfdb5) [0x55ee43252db5] (??:0)
[16] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x44b54e7) [0x55ee46d284e7] (??:0)
[17] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x44b6c6d) [0x55ee46d29c6d] (??:0)
[18] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x9e6713) [0x55ee43259713] (??:0)
[19] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x9c8d80) [0x55ee4323bd80] (??:0)
[20] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x9bd456) [0x55ee43230456] (??:0)
[21] /lib/x86_64-linux-gnu/libc.so.6(+0x29fd0) [0x7f42a0d4afd0] (??:0)
[22] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x7d) [0x7f42a0d4b07d] (??:0)
[23] ./godot/bin/godot.linuxbsd.opt.tools.64(+0x9c7735) [0x55ee4323a735] (??:0)
-- END OF BACKTRACE --
================================================================
./do_edit_game_linux.sh: line 4:  2420 Aborted                 (core dumped) ./godot/bin/godot.linuxbsd.opt.tools.64

[END crash dump]
Steps to reproduce
USING LINUX/BSD...
1. BEGIN CREATING A NEW PROJECT

2. DURING PROJECT CREATION, CREATE A FOLDER

3. Observe the crash dump in 'Issue description'
Minimal reproduction project
N/A (This happens DURING project creation)

Observe the crash dump in 'Issue description'

Unfortunately, the backtrace is not useful as you ran a binary that didn't contain debugging symbols. To get a useful backtrace, you need to compile from source.

Sorry for the confusion. I'm building from source using the following script:
#!/usr/bin/env bash

# Builds the Godot game engine. The output executable is in the godot/bin directory.

cd godot
git checkout master
git pull
scons -j4 platform=linuxbsd target=release_debug

What can I change to be more helpful?

What can I change to be more helpful?

Don't strip debug symbols by running the strip command. Also try using target=debug (the default) instead of target=release_debug.

Thanks! I don't think I'm using strip, but I'll try target=debug and update you asap. Really appreciate the fast response!

It looks like this is a non-issue.
Apparently, months ago, the linuxbsd executable extension was changed from .64 to .x84_64, and I missed that while initially troubleshooting this issue--- I was repeatedly running an old build (".64"), instead of the one I had been compiling (".x86_64").
Sorry about that.


Improves/Fixes data-drag-delay to actually delay dragStart.

Fixes collisions with ng-click on ui-tree-node elements.
Builds on pull request #393, by adding the dragStart callback to the dragStart method.

Note: d8a6188 was based off PR #393 and had an issue with the callback referencing an undefined variable. I moved the dragStart callback firing to the dragStart() method, after dragInfo has been declared and fetched (as seen in 3b84268).

+1

+1

Reviewed and tested. Great fix! Please make your PR up-to-date with the master branch, so it can be merged.
Thanks again :cake:

Done!
Also fixed all the warnings/errors linter was throwing.

Merged, thanks!


Don't handle file open dialog window

Open file dialog window not handled by berry.
 $xprop
_NET_WM_USER_TIME(CARDINAL) = 3644362
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL
WM_HINTS(WM_HINTS):
		Client accepts input or input focus: True
		Initial state is Normal State.
		window id # of group leader: 0x1400001
_GTK_THEME_VARIANT(UTF8_STRING) =
WM_TRANSIENT_FOR(WINDOW): window id # 0x1600017
XdndAware(ATOM) = BITMAP
WM_WINDOW_ROLE(STRING) = "GtkFileChooserDialog"
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 20971533, 20971534
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x140000c
WM_CLIENT_LEADER(WINDOW): window id # 0x1400001
_NET_WM_PID(CARDINAL) = 21571
WM_LOCALE_NAME(STRING) = "C"
WM_CLIENT_MACHINE(STRING) = "aser"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified minimum size: 532 by 320
		program specified base size: 0 by 0
		window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "code-oss", "Code-oss"
WM_ICON_NAME(STRING) = "Open File"
_NET_WM_ICON_NAME(UTF8_STRING) = "Open File"
WM_NAME(STRING) = "Open File"
_NET_WM_NAME(UTF8_STRING) = "Open File"

This dialog I opened by vscode file->open menu command.

This window appears at top left corner and shown at all workspaces.

hm yes.
herbstluftwm implements a feature where users can decide which windows are handled by the window manager and which ones are not. berry currently has these fixed, which I suppose is not very flexible. I'll try working on a feature to make this behavior toggleable.

Can you make dialog and menu windows handled by berry for now? Just for quick fix?
There is also problem with virtualbox settings window.

$ git diff wm.c
diff --git a/wm.c b/wm.c
index 984e6a3..cff8b97 100644
--- a/wm.c
+++ b/wm.c
@@ -1193,10 +1193,10 @@ manage_new_window(Window w, XWindowAttributes *wa)
         if (prop_ret) {
             prop = ((Atom *)prop_ret)[0];
             if (prop == net_atom[NetWMWindowTypeDock] ||
-                prop == net_atom[NetWMWindowTypeToolbar] ||
+                // prop == net_atom[NetWMWindowTypeToolbar] ||
                 prop == net_atom[NetWMWindowTypeUtility] ||
-                prop == net_atom[NetWMWindowTypeDialog] ||
-                prop == net_atom[NetWMWindowTypeMenu]) {
+                // prop == net_atom[NetWMWindowTypeDialog] ||
+                // prop == net_atom[NetWMWindowTypeMenu]) {
                 D fprintf(stderr, WINDOW_MANAGER_NAME": Window is of type dock, toolbar, utility, menu, or splash: not managing\n");
                 D fprintf(stderr, WINDOW_MANAGER_NAME": Mapping new window, not managed\n");
                 XMapWindow(display, w);

This works for me as temporary solution

I added a manage/unmanage feature as of 4acf24760ea7fc9bbd05cb7c6fb0afcc7d28c868. Closing.


Outputs heat map

In Figure.7, it shows how the MM direct the model to focus on the effective area.I woder how you made it, is there any convience to share the code, thanks~

Thank you~ and is the feature a single channel? or the 28?

Average them

Thanks~


Less gargantuan debug libraries

fixes #1062
Problem is cppwinrt\winrt\Windows.UI.Xaml.Controls.h defines a lot of template that gets compiled inside .obj and concatenated in the .lib.
The more .cpp including <Babylon/Graphics/Platform.h> the bigger the library.
There is no define ([WIN32_LEAN_AND_MEAN like) that will help. It looks like some build parameters with implicit templates might help but it doesn't cover our use case here.
Only solution is to limit the number of .cpp including it. That's what I did in this PR with forward reference and an added method UpdateSize so WindowConfiguration is forward until last moment in a .cpp that already includes the winrt header.
This way, we get from 40+Mb to 18. It's possible to shave off another 7Mb by removing Plaform.h inclusion from DeviceImpl but this line will produce an error:
Resize(config.Width, config.Height);
I have some thoughts that I leave to your appreciation:

have a base struct WindowConfigurationBase that WindowConfiguration will inherit from. It will contain only Width and Height. So, it's possible to cast from a WindowConfiguration to a WindowConfigurationBase reference in DeviceImpl and only use Width/Height
Try to do an amalgamated build for this project using cmake. Basically, cmake build a new temporary file that include every .cpp. Only this file will be compiled. So, template will only be instanciated once. On a large scale, this can help reduce build time for other projects too (I experience around 40% less time in other projects)

Closing because unity build is more promising.


🌱 Test Registry

Test Registry
Adds a bare-bones test registry and a folder tree for our test images.
This PR aims to improve our test infrastructure by removing scripts and external images for registry operations in favor of bare-bones tools built in golang using well-known libraries (go-containerregistry in particular).
Structure
The PR adds two tools:registry and  push. It also aggregates all our image-related makefile targets into one: image-registry.
registry
Just about the simplest possible image registry that can be built using the go-containerregistry lib. See README here.
push
Utilizes crane within go-containerregistry to build and push our catalog and bundle images. It uses a directory walker which is intended to make adding future test bundles and catalogs easily. It also (IMO - totally subjective) makes our test image collection more WYSIWYG by clearly showing all the images and tags we use in the folder rather than hiding them in scripts or makefiles.
See README here for more info on the expected folder structure.
make image-registry
Builds the registry and push binaries, bundles them into one image, then deploys them both. registry is deployed essentially as before. push executes as a job, building all the images bundled inside of it then pushing them to the specified registry address.
TODOs / Follow-Ups
PR size is currently huge due to the amount of prometheus manifests being copied for each bundle tag... I'm open to suggestions on how we could address this. Maybe we could remove the prometheus-operator in favor of a test operator with fewer manifests?
Remaining items to address:

[ ] Either:
A: Find a better way to organize tags such that we need not have many copies of the same manifests.
B: Keep the current folder structure for tags but simplify the manifests we're using in test to reduce file count/complexity.
C: Modify the catalog yaml so that every version of prometheus-operator uses the same bundle image (v1.0.0). We were previously doing this anyway essentially because each tag we created for this bundle had the exact same content.
[ ] Metadata reading for bundle images is using one path instead of reading dynamically (which we can get away with right now because all the bundles are identical).
[ ] Configurable cert/key path for registry (not super critical right now).
[ ] Use mounted secrets for push instead of crane.Insecure (also not critical).

Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

verdiff is complaining about new go.mod files; we should be ok with that.

I have a wicked simple bundle that can be installed: https://github.com/tmshort/test-image
It consists of just a configmap

I have a wicked simple bundle that can be installed: https://github.com/tmshort/test-image It consists of just a configmap

If you're suggesting this to replace the prometheus-operator, I'm happy with that as long as we're OK with not having things like: crd, deployment with runtime, etc. in our test bundle. But I think that having at least a running pod as a result of the ClusterExtension is important for the e2e to check for installation success.
I did also just test that we can definitely get away with just having the test-catalog's bundles all point to the same prometheus-operator version.

It's a bundle, it can be installed... Not sure how critical it is to actually have something with a CRD or deployment. That being said, it's just an offer. Not making it a requirement.


Add Apache Spark version to --version text

Commit cherry picked from pull request #1360

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1815/
Test PASSed.


ci(node-test): split up build and running test stages

Description

Test Plan

#513  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hyf0 and the rest of your teammates on  Graphite

Merge activity

Mar 9, 3:47 PM EST: @hyf0 started a stack merge that includes this pull request via Graphite.


Upload to NFT storage

This aims to fix #68.
Checklist:

[ ] Documentation
[ ] Tests
[ ] Code complete
[ ] Changeset

There's a few things to clear up before this can be wrapped up. I'll try explain what this PR does.
Currently, you can pass your own url to deploy. This assumes you've uploaded your NFT with relevant metadata and got the URL back. This PR does not change this, it attempts to avoid a breaking change.
const sdk = new OpenFormatSDK({
  network: 'http://localhost:8545',
  signer,
});

const receipt = await sdk.deploy({
  name: 'Test',
  url: 'ipfs://',
  symbol: 'TEST',
  maxSupply: 100,
  mintingPrice: 0.01,
});

Here's where things start to change. If you omit a url, it will throw an error when trying to deploy.
const sdk = new OpenFormatSDK({
  network: 'http://localhost:8545',
  signer,
});

const receipt = await sdk.deploy({
  name: 'Test',
  symbol: 'TEST',
  maxSupply: 100,
  mintingPrice: 0.01,
});

However. If you specify a factory and omit a url, it will attempt to upload your NFT for you via nft.storage.
const sdk = new OpenFormatSDK({
  network: 'http://localhost:8545',
  signer,
  factory: "some-id",
});

const receipt = await sdk.deploy({
  name: 'Test',
  symbol: 'TEST',
  maxSupply: 100,
  mintingPrice: 0.01,
});

Now uploading the NFT is really nice on behalf of the users, though there's some things worth double checking in this PR.
If you specify a factory and omit the url (like above) it will now throw an error if you don't supply some assumed mandatory fields. You now need to additionally pass description, image and releaseType.
description and image are required fields of NFT storage and I've made releaseType required as it seems to make sense when the metadata is built with factory_id.
const sdk = new OpenFormatSDK({
  network: 'http://localhost:8545',
  signer,
  factory: "some-id",
});

const receipt = await sdk.deploy({
  name: 'Test',
  description: "some description",
  image: new Blob([""], {type : 'image/png'}),
  releaseType: "image",
  symbol: 'TEST',
  maxSupply: 100,
  mintingPrice: 0.01,
});

You can also optionally supply an object of metadata which can include other files.
const receipt = await sdk.deploy({
  name: 'Test',
  description: "some description",
  image: new Blob([""], {type : 'image/png'}),
  releaseType: "image",
  symbol: 'TEST',
  maxSupply: 100,
  mintingPrice: 0.01,
  metadata: {
    some: 'test',
    audio: new File(...),
  },
});

Is sounds a bit confusing given there a various optional things now but really this is the main change to the deploy function...
// an optional URL a user can supply when calling the deploy function
let url = nft.url;

// if the url is not provided, but they've set factory ID when intialising the SDK, we attempt to upload the NFT for them
if (typeof url === 'undefined' && factory) {
  // we check to see if a few required fields have been passed, these are optional in TypeScript due to being able to pass your own url
  invariant(nft.description, 'A description must be set');
  invariant(nft.image, 'An image must be set');
  invariant(nft.releaseType, 'A release type must be set');

  const customMetadata = nft.metadata ?? {};

  // we send the NFT to storage, spreading any other metadata
  const metadata = await nftStorage.store({
    name: nft.name,
    description: nft.description,
    image: nft.image,
    factory_id: factory,
    release_type: nft.releaseType,
    ...customMetadata,
  });

  url = metadata.url;
}

// is no url has been supplied and no factory id was set to perform an upload, an error is thrown
invariant(url, 'An IPFS URL must be set');

One thing worth checking with the nft.storage api is that in most of our examples that have been built so far, the metadata is spread across the root stored object.
await nftStorage.store({
  name: nft.name,
  description: nft.description,
  image: nft.image,
  // custom data
  factory_id: factory,
  release_type: nft.releaseType,
});

Whereas in their docs, they specify a properties field should be used. https://nftstorage.github.io/nft.storage/client/classes/lib.NFTStorage.html#store
So I'm not sure if we need to change things to... in our code.
const metadata = await nftStorage.store({
  name: nft.name,
  description: nft.description,
  image: nft.image,
  properties: {
    factory_id: factory,
    release_type: nft.releaseType,
    ...customMetadata,
  },
});

Ideas from @coatezy: Potential for the factory ID to be optional and potential for the factory ID to be passed through with the deploy function rather than when initialising the SDK.

The properties  field is a metadata storage standard that some NFT marketplaces use. For example Opensea will automatically detect metadata if it is stored in key value pairs inside the properties field.

The properties field is a metadata storage standard that some NFT marketplaces use. For example Opensea will automatically detect metadata if it is stored in key value pairs inside the properties field.

That makes sense, thanks. I guess we can ignore that for now then and keep the data how we currently have it.

cool, for reference they talk about it here - https://nft.storage/docs/how-to/mint-erc-1155/
'When adding custom properties, we recommend that you put them in the properties object, rather than at the top level. However, if you're minting for a specific marketplace, you should consult their documentation and follow their recommendations.'

Moving my changes into a separate PR.

Is it worth refactoring open-format-NFT to also use the properties standard?? I think that whatever route we go down are examples should be inline.

@benjaminreid Is it worth refactoring open-format-NFT to also use the properties standard?? I think that whatever route we go down are examples should be inline.

The properties weren't used for the subgraph stuff in the end, so should be okay to stay as is 👍

Great work on this. I think it's important to note in the documentation that the metadata can currently only be a key/value pair with the value being a string. Please see here for more. Nested metadata is on the roadmap for future releases.

@tinypell3ts Hopefully this note covers it https://open-format-docs-pahg5ufeh-simpleweb-ltd.vercel.app/guides/deploying


configuration problem

I find that I can not use the setup.py
there are some errors in config-pkg

that is all


MPI crashes on Ubuntu 14.04

Hi,
I was testing the simple mpi example included in emcee, and it was causing a crash with this message:
File "mpi_test.py", line 23, in
pool.wait()
File "/home/federico/anaconda/lib/python2.7/site-packages/emcee-2.1.0-py2.7.egg/emcee/mpi_pool.py", line 95, in wait
task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
File "Comm.pyx", line 1175, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:99438)
File "msgpickle.pxi", line 263, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:39179)
mpi4py.MPI.Exception: Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff1c5cd0b0) failed
MPIDI_CH3I_Progress(461)...........:
MPID_nem_handle_pkt(636)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
Fatal error in MPI_Finalize: Other MPI error, error stack:
MPI_Finalize(281)..................: MPI_Finalize failed
MPI_Finalize(209)..................:
MPID_Finalize(117).................:
MPIDI_CH3U_VC_WaitForClose(383)....: an error occurred while the device was waiting for all open connections to close
MPIDI_CH3I_Progress(461)...........:
MPID_nem_handle_pkt(636)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
This is on Ubuntu 14.04, using anaconda, and after a freshly built mpi4py where every single test passed without any failures.  Any clue what might be causing this?

Has anyone else run into this? I get almost the exact same error message. I'm on Red Hat 6.6 with a newly installed anaconda. I am running rather large chains with ~100 dimensions, 500 walkers and 100,000 steps, and I run into this error once or twice per run. I save the chain to disk and reset it every 10,000 steps, so I'd be surprised if this was a memory issue. Any help would be appreciated!
File "/usr/lusers/rodluger/anaconda/lib/python2.7/site-packages/emcee/mpi_pool.py", line 95, in wait
  File "run.py", line 92, in Run
    pool.wait()
  File "/usr/lusers/rodluger/anaconda/lib/python2.7/site-packages/emcee/mpi_pool.py", line 95, in wait
        task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
    task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
  File "Comm.pyx", line 816, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:66815)
  File "Comm.pyx", line 816, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:66815)
task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
  File "Comm.pyx", line 816, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:66815)
    task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
  File "Comm.pyx", line 816, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:66815)
  File "pickled.pxi", line 236, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:27858)
  File "pickled.pxi", line 236, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:27858)
  File "pickled.pxi", line 236, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:27858)
  File "pickled.pxi", line 236, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:27858)
mpi4py.MPI.Exceptionmpi4py.MPI.Exceptionmpi4py.MPI.Exception: : Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff02e2cb50) failed
MPIDI_CH3I_Progress(432)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
: Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff2c96a520) failed
MPIDI_CH3I_Progress(432)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff45daf9d0) failed
MPIDI_CH3I_Progress(432)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
mpi4py.MPI.Exception: Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff292b4220) failed
MPIDI_CH3I_Progress(432)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.

I get the same message,
Traceback (most recent call last):
File "emcee_mpi_benchmark.py", line 28, in
pool.wait()
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/mpi_pool.py", line 95, in wait
task = self.comm.recv(source=0, tag=MPI.ANY_TAG, status=status)
File "MPI/Comm.pyx", line 1192, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:106889)
File "MPI/msgpickle.pxi", line 266, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:42711)
mpi4py.MPI.Exception: Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=0, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7fff794b88f0) failed
MPIDI_CH3I_Progress(461)...........:
MPID_nem_handle_pkt(636)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.
is getting annoying

In my case I found that is sensitive on the number of walkers.
If I use nwalkers = 250 and 2 processes I get the error.
If I set nwalkers=200 instead it run flawlessly (though is slower than in the scalar case)

Do you get the same crash if you add loadbalance=True while creating the MPIPool object?
(Replace MPIPool() with MPIPool(loadbalance=True))

yes

Will you please post a minimal set of code to reproduce the problem, including the command-line to run emcee.

`from future import print_function
import sys
import numpy as np
import emcee
from emcee.utils import MPIPool
import time
import mpi4py.MPI as MPI
def lnprob(x):
return -0.5 * np.sum(x ** 2)
#check if mpi is running
if_mpi = (MPI.COMM_WORLD.Get_size() > 1)
Initialize the MPI-based pool used for parallelization.
if (if_mpi) :
pool = MPIPool(loadbalance = True)
print('rank',pool.rank,'size',pool.size)
if not pool.is_master():
    # Wait for instructions from the master process.
    pool.wait()
    sys.exit(0)

ndim = 50
nwalkers = 250
burnin=100
step=1000
p0 = [np.random.rand(ndim) for i in xrange(nwalkers)]
print('after pool')
Initialize the sampler with the chosen specs.
tp=time.time()
if (if_mpi):
sampler = emcee.EnsembleSampler(nwalkers, ndim, lnprob, pool=pool)
else:
sampler = emcee.EnsembleSampler(nwalkers, ndim, lnprob)
pos, prob, state = sampler.run_mcmc(p0, burnin)
sampler.reset()
sampler.run_mcmc(pos, step, rstate0=state)
if (if_mpi):
pool.close()
print(u"Mean acceptance fraction: ", np.mean(sampler.acceptance_fraction))
`
I launch it with mpirun -np 2 python femcee_mpi_test.py
if i set nwalkers to 200 no problem
if i set nwalkers to 250 i get

Traceback (most recent call last):
File "emcee_mpi_test.py", line 57, in
sampler.run_mcmc(pos, step, rstate0=state)
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/sampler.py", line 157, in run_mcmc
**kwargs):
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/ensemble.py", line 259, in sample
lnprob[S0])
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/ensemble.py", line 332, in _propose_stretch
newlnprob, blob = self._get_lnprob(q)
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/ensemble.py", line 382, in _get_lnprob
results = list(M(self.lnprobfn, [p[i] for i in range(len(p))]))
File "/opt/local/anaconda/anaconda-2.2.0/lib/python2.7/site-packages/emcee/mpi_pool.py", line 207, in map
tag=MPI.ANY_TAG, status=status)
File "MPI/Comm.pyx", line 1192, in mpi4py.MPI.Comm.recv (src/mpi4py.MPI.c:106889)
File "MPI/msgpickle.pxi", line 266, in mpi4py.MPI.PyMPI_recv (src/mpi4py.MPI.c:42711)
mpi4py.MPI.Exception: Other MPI error, error stack:
MPI_Probe(113).....................: MPI_Probe(src=MPI_ANY_SOURCE, tag=MPI_ANY_TAG, MPI_COMM_WORLD, status=0x7ffef96696c0) failed
MPIDI_CH3I_Progress(432)...........:
MPIDI_CH3_PktHandler_EagerSend(606): Failed to allocate memory for an unexpected message. 0 unexpected messages queued.

Thanks for posting the code fragment - nothing in the code immediately jumps out to me.
Is it possible that there are multiple MPI installations and mpi4py was compiled with a different MPI implementation than what mpirun on the command-line directly refers to. Easiest way to check would be to replace python with the python-mpi within the mpi4py/bin directory. Next step might be to reinstall mpi4py via your package manager.

Has there been any developments in this issue? I too get the same error and it seems somewhat random in nature.
What I mean buy this is if I fit 5 objects with same parameters 2 would execute fine and 3 would fail with this error.
@manodeep mpi4py has been installed within a conda venv in g2. This fails as a queue job and even in the interactive node in g2.

Seemingly random failures sigh. I had dug around previously for this issue but did not find any promising avenues.
@themiyan do you want to come by my office and we can debug this issue? Hopefully we can get to the bottom of this. May be we can squash this issue once and for all.

I encountered the same problem and concluded that this is an mpi (or rather mpi4py) problem. This is also occurred on a conda installation of mpi4py. The solution in my case was
conda remove mpi4py
conda config --add channels conda-forge
conda install mpi4py
Fetching package metadata ...........
Solving package specifications: .

Package plan for installation in environment /home/moon/dietrich/applications/anaconda3/envs/py27:

The following NEW packages will be INSTALLED:

    mpi4py: 2.0.0-py27_2 conda-forge
    mpich:  3.2-4        conda-forge

Proceed ([y]/n)?

The new mpich seems to have solved this for me.

Thanks @joergdietrich - the problem does seem to be the mpich bit of mpi4py. We figured that a different mpi4py for the platform should do the trick. For @themiyan case, this will most likely require something like conda install -c mpi4py openmpi=2.0.2


Mark fitBounds events triggered by this library

This is very useful for onDragEnd, onZoomEnd and onBoxZoomEnd etc. event handlers to detect reason of drag/zoom (it can be either because user dragged map / clicked zoom button, or because fitBounds has been changed).
With this change each zoom/drag event triggered by this lib is marked with { auto: true } which can be used for example in followng way:
            onBoxZoomEnd={(_, event) => {
              if (event.auto !== true) {
                this.performSearch()
              }
            }}

Hey @sheerun could we add this to the doc? I would also rename the property from auto: boolean to something like fitboundUpdate: boolean

Done

Thank you for you work, I will release asap


Does Nylo has a default state manager ?

I wanted to know if you recommend a state manager with Nylo and how you advice us to use state manager such as Riverpod with your framework

Hi @NemesisX1, you can use whichever state manager you like. Nylo's been built to create a streamlined approach to scaffolding new projects. Hope that helps :)


SVG thumbnails for "Blog" category

🚀 Feature
A default thumbnail is being used currently for a code block.
For the "Blog" category, SVG thubmnails that represents the code block preview in an abstract manner (like a skeleton template) would help a user to get an intuition about the template in a glance in the sidebar itself
Have you spent some time to check if this issue has been raised before?
Yes
Have you read the Contributing Guidelines?
Yes
Pitch
This would enhance the user experience by providing a quick abstract preview of the code block in the sidebar that would reduce the time required to find the desired template. The thumbnail can be designed using any designing tool like Figma, Adobe XD etc.

Hey @VaibhavSaini19, I would like to work on this issue.
Please assign me this.

Sure. Happy hacking 😀


Fixes after IP BOM 7.0.0.CR4 upgrade

+1 Do it needs to be merged at the same time with others?

Yes, all PRs need to be merged together (will add a comment to each of them just to be sure).

ok, can you merge in such occasions?
this is not a one time thing, such a multi-repo merge. We might want to standarize a tag or phrase, for example "multi-repo merge". Which implies that you need a +1 of each repo gatekeeper, but you 'll do the merge yourself - and the gatekeepers shouldn't merge because otherwise they'll break their repo (unless they merge all others too). Wydt?

Yeah, me or @csadilek are usually merging these PRs. We should definitely be putting a clear comment in the PR so that gatekeepers know all the PRs need to be merged at the same time. We could standardize a phrase or something, but not not sure if it is worth it. These kinds of big upgrades are not that common.


Correct way to access SceneLineItemBlock "value"

I am not sure whether I am the problem or I misunderstood something, but while trying to include rmscene into rmrl (see https://github.com/benneti/rmrl ), I stumbled upon the problem that it is not possible to access block.value but only block.item.value.
But looking at the code (as someone unfamiliar with @dataclass notation) it looks like there should be a value optional available directly.
Some more insight would be appreciated!

Hi,
I think this is a mistake by me, in ad592adc1524b941814f95e656f1b85b75f76a3f I changed to using block.item, but did not remove all the old value attributes. Using block.item.value is the right way.
I would anyway recommend using the “scene tree” interface, since it will handle the tree structure, nesting, layers etc. See for example the code in https://github.com/ricklupton/rmc/blob/scene-tree/src/rmc/exporters/svg.py

Ah, thanks for the reply, this makes sense. I think the rmscene part is already working but transforming I do not yet understand how to correctly transform to fit it ontop of a potential base pdf.

Fixed in 15c4964afdcf0b2dc85a005253e1954b42d3a609


Can we get a 2023.02.00-alpha02?

It seems there has been another wave of alpha library releases: https://androidx.tech/blog/2023/01/25/late-january-artifact-wave.html

Yep, I've been trying all day but Maven Central has been having a lot of issues.
I just pushed up a version bump commit, so hopefully it works this time (I've seen reports that things are better).

Still failing unfortunately https://github.com/chrisbanes/compose-bom/actions/runs/4019793013/jobs/6907035699

v2023.02.00-alpha02 has been released!


Tasks and communication

 Issue by larsbergstrom
Wednesday Jul 16, 2014 at 13:30 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/15713
This issue was labelled with: A-concurrency, A-libs, A-servo in the Rust repository

Currently, any large program using tasks and channels will have a mixture of deadlocks and unpredictable task failures due to the interaction of task failure, channel communications, and asynchronous communication protocols.
Ideas in this space:

Controlled tear-down behavior, ala either the old linked task failure or something else easier to implement for a group of tasks.

Static protocol checking to ensure progress / avoid deadlock or livelock. Note that, unlike much of the existing literature, this needs to be robust in the face of both async. comm. and async. + multiple failures.

CC: @pcwalton

Please close - we're planning to do this on our side instead.


how to get the value using jquery?

How to use the JQuery to get the color value?
In this jsfiddle, I am trying to use $("#colorvalue").text($("#test").val()) to get my color values, e.g. #000000. However, if you see the console log, the $("#test").length is surprisingly 0.  It seems that the new Pickr() somehow removed the #test and replaced it with something else. Anyway, is there a way to use JQuery to return the color value? Or how the color values should be returned?
Thank you for the great package! I love it.

You can use pickr.getColor().toHEXA() to get the current HEX color value as array (e.g. ['ff', 'fa', 'fb']), or pickr.getColor().toHEXA().toString() to get it as string value (e.g. #fffafb).
The element you pass to pickr gets replaced with pickr, so after initialization .color-picker wont exist anymore. I think I know what you want, checkout this updated fiddle: http://jsfiddle.net/z2qd3jkf/
You also used a really, really old version. Be sure to load the latest one :)

Thank you for the prompt reply. It works fine.
Yet, I think it could be more convenient if the replaced pickr can inherit the original id of the div so that it can be caught by id. I am asking this is because I will have dynamically multiple pickrs in the page and I would like to return the value of any of the pickr when it changes, instead of having a callback function for each of the pickrs.

I would like to reopen this question. Is there a way of getting the color by div ID or anything? Suppose I have two pickr on a page and I would like to get the color of each of them using jquery or pure javascript. Is it possible?

What are you trying to achieve? You need at least the instance of pickr to get a color.
Pickr is completely independent of any framework or library, if your are using JQuery as dom-selector or d3 makes no difference :) You can get the current color of each by just calling getColor() on a pickr instance. Take a look at the methods section in the docs.
Just create two pickr instances and you're done. Take a look at this fiddle

I just have multiple pickr on the page. Each pickr has its corresponding dynamically created id. I just would like to use jQuery to get any pickr color I want using the ids.

Why don't you have a centralized place where you store your instances / application state? You need to initialize pickr somewhere, therefore you got the instance stored in a variable on your page or bundle. Pickr isn't meant to polyfill or enhance a native HTML5 feature like input[type=color].
I can't imagine a situration where you don't have access to the pickr instance anymore... The only possible solution would be to wrap pickr into a web-component, then you could "access" it via document.getElement

I'll close this for now. Re-open if you have any questions.

calling initSimon wep picker two times at same page reset the value in edit scenario


Fix evolved operator ansatz

Summary
This resolves issue #11680, which pertains to a bug encountered when creating an EvolvedOperatorAnsatz with an empty list of operators.
Details and comments
The changes implemented ensure that EvolvedOperatorAnsatz.num_qubits returns a sensible result (specifically zero) when operators is an empty list, rather than throwing an error. This adjustment alone enables the following code to function correctly:
e = EvolvedOperatorAnsatz(operators=[])

By solely doing this, in the above code, e.qregs contains a QuantumRegister with zero qubits. While its base class, QuantumCircuit, handles the case with no qubits by setting qregs to an empty list.
https://github.com/Qiskit/qiskit/blob/d033e8a4185c0299b644f0bdf4e8ed1d17d2bb08/qiskit/circuit/quantumcircuit.py#L1454
We have mirrored this behavior in EvolvedOperatorAnsatz to ensure that EvolvedOperatorAnsatz(operators=[]) behaves the same as QuantumCircuit(). This equivalence is also asserted in a test.
Please note that a brief release note has been added to the branch.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 89.565%

Files with Coverage Reduction
New Missed Lines
%

qiskit/synthesis/two_qubit/two_qubit_decompose.py
2
96.64%

crates/qasm2/src/lex.rs
4
91.69%

crates/qasm2/src/parse.rs
12
97.15%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
59611

Relevant Lines:
66556

💛  - Coveralls

Hi @Cryoris , I know you must've been busy, I just wanted to make sure you didn't miss this.

@Mergifyio backport stable/0.46


Adding a  chatbot

Hello! I am a GSSOC'21 participant.
I observed that there is no chatbot in the website which needs to be there as there are lots of benefits of having chatbots like-
Customer engagement will be increased
Customer service will also be increased
Its trending
There could be some person who would be replying the messages or some bot for faqs.
@khannakshat7 @CodesbyUnnati  I would like to work on this

@Debashish-hub Hello I am a GSSOC participant.
Actually I have made a chatbot by using ML libraries for a hostel website so i know about chatbot . I would like to work on it .
Please assign it to me.

@khannakshat7 please assign me this issue

@arpit456jain we can work on it together . Can u tell me ur discord so that we can discuss on it.
@khannakshat7 Please add a label on this issue.
Thanks.

Sir I am a Django developer and currently working on integrating Django backend to React Frontend using DJANGO REST FRAMEWORK and trying to build REST APIs, I will feel pleasure if you assign me this issue
for any confirmation and references you may checkout my repos on django and flask
by the way I have a fully functional chatbot which i have made using flask, Repo:- https://github.com/vinayak3010/chatBot_flask.git
I may also make it on django

Sir/Ma'am may I get your discord I'd to talk about the project, if possible


Enhanced Load Balancing and Aggregation Strategy for Uneven Battery Charging Rates

Context:
We’ve observed a notable issue in scenarios where batteries connected to the same system charge at different rates. The attached image highlights a specific instance where one battery (Battery-2) reaches a charge rate (74.1A) that exceeds the predefined maximum charge current (43A), while the aggregate charge current remains below the combined potential maximum (92A). This discrepancy suggests that the other batteries in the system are under-utilized in terms of their charging capacity.

Problem:
The current aggregation algorithm seems to not dynamically adjust the distribution of charge currents based on the real-time charge acceptance of each battery. This leads to scenarios where one battery could potentially be overcharged or charged at a rate higher than its set maximum, while others might not utilize their full charging capability, resulting in inefficient overall system performance.
Suggested Enhancement:
1.	Dynamic Adjustment of Charge Rates: Implement an algorithm within the BatteryAggregator that continuously monitors the charge rates and capacities of individual batteries and adjusts the distribution of current to maximize the overall efficiency and safety. The algorithm should reduce the charge current of batteries nearing their maximum charge rate and redistribute the excess to other batteries which are charging below their maximum capacity.
2.	Utilization of Unused Margins: For batteries that rapidly reach their max charge current, the system should consider the ‘unused’ charge capacity (margins) of these batteries and dynamically reallocate it to other batteries in the system which are underperforming. This ensures a balanced charge state across all batteries and maximizes the usage of available current.
3.	Alternative Solutions: Exploration of other potential solutions or enhancements that could optimize charge balancing and efficiency, such as machine learning algorithms predicting battery behavior based on historical data to pre-adjust charge rates dynamically.

Impact:
Addressing this issue will not only enhance the operational efficiency of the battery system but also prolong the lifespan of the batteries by preventing scenarios of overcharging and under-utilization. This improvement is crucial for maintaining the health and efficacy of power storage systems, especially in complex setups where multiple batteries are involved.

one more example

thank you

ups, i had installed some old version, will check it again.


[BEAM-2256] Add the last previous range filter

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[X] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[X] Make sure tests pass via mvn clean verify.
[X] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[X] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @dhalperi

R: @lukecwik

@jbonofre I will address the comments I made and will get it merged.

This has been merged, please close PR.

Thanks @lukecwik !


Can you please include these apps

paint.net
https://www.getpaint.net/
https://chocolatey.org/packages/paint.net
line
https://line.me/th/download
guitar pro
https://www.guitar-pro.com/en/index.php?pg=download&software=
mirilis
https://mirillis.com/en/products/action.html
filebot
https://www.filebot.net/
https://chocolatey.org/packages/filebot
cheat engine
https://www.cheatengine.org/
https://chocolatey.org/packages/cheatengine
wunderlist
https://www.wunderlist.com/
https://chocolatey.org/packages/wunderlist
CORSAIR iCUE v3.14.104
https://www.corsair.com/ww/en/downloads#download_form_1
https://chocolatey.org/packages/cue
Some packages doesn't exist in chocolatey so I am not sure if it is possible to be included here!

wunderlist
https://www.wunderlist.com/

Moved to more more appropriate repo https://github.com/appget/appget.packages/issues/3203.


Testing?

There's no tests currently for any of the code, is this planned?

This is a problem right now. We're currently in the process of adding unit tests to the WebChat project. Emulator tests coming soon after.

We now have a testing framework for the emulator! Currently we're a little sparse on coverage, but we'll get more tests soon.


[1375] Add affiliation handling to LDAP lookup [v5.5]

Resolves #1375 for v5.5

accept new env variable with comma-separated parameters, and return concatenated results

ok


Create 0000-01-02-RICHIN.md

I feel so happy to complete the assigned task so far ,I have created branch, created a file and made a commit, and opened a pull request

git fetch origin
git checkout -b  origin/
git merge main


fails to build with current homebrew csfml package on OSX

After discussion of easy haskell sound libs on #haskell just now, I tried installing SFML on OSX 10.12.4. It seems slightly out of date with csfml 2.4:
$ brew install csfml
...
==> Installing dependencies for csfml: flac, sfml
==> Installing csfml dependency: flac
==> Downloading https://homebrew.bintray.com/bottles/flac-1.3.2.sierra.bottle.tar.gz
####################################################################################################################################################################################################### 100.0%
==> Pouring flac-1.3.2.sierra.bottle.tar.gz
🍺  /usr/local/Cellar/flac/1.3.2: 53 files, 1.8MB
==> Installing csfml dependency: sfml
==> Downloading https://homebrew.bintray.com/bottles/sfml-2.4.2.sierra.bottle.tar.gz
####################################################################################################################################################################################################### 100.0%
==> Pouring sfml-2.4.2.sierra.bottle.tar.gz
🍺  /usr/local/Cellar/sfml/2.4.2: 126 files, 1.7MB
==> Installing csfml
==> Downloading https://homebrew.bintray.com/bottles/csfml-2.4.sierra.bottle.tar.gz
####################################################################################################################################################################################################### 100.0%
==> Pouring csfml-2.4.sierra.bottle.tar.gz
🍺  /usr/local/Cellar/csfml/2.4: 99 files, 793.8KB
$ stack install SFML
stack install SFML
SFML-<IP_ADDRESS>: configure
SFML-<IP_ADDRESS>: build

--  While building package SFML-<IP_ADDRESS> using:
      /Users/simon/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_<IP_ADDRESS>_ghc-8.0.2 --builddir=.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS> build --ghc-options " -ddump-hi -ddump-to-file"
    Process exited with code: ExitFailure 1
    Logs have been written to: /Users/simon/.stack/global/.stack-work/logs/SFML-<IP_ADDRESS>.log

    Configuring SFML-<IP_ADDRESS>...
    Building SFML-<IP_ADDRESS>...
    Preprocessing library SFML-<IP_ADDRESS>...
    BlendMode.hsc:22:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    FontInfo.hsc:15:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    RenderStates.hsc:22:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    ContextSettings.hsc:19:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    Event.hsc:131:15: warning: '' is deprecated [-Wdeprecated-declarations]
        hsc_peek (sfMouseWheelEvent, delta);
                  ^
    /usr/local/Cellar/csfml/2.4/include/SFML/Window/Event.h:126:9: note: '' has been explicitly marked deprecated here
    typedef struct CSFML_DEPRECATED
            ^
    Event.hsc:132:15: warning: '' is deprecated [-Wdeprecated-declarations]
        hsc_peek (sfMouseWheelEvent, x);
                  ^
    /usr/local/Cellar/csfml/2.4/include/SFML/Window/Event.h:126:9: note: '' has been explicitly marked deprecated here
    typedef struct CSFML_DEPRECATED
            ^
    Event.hsc:133:15: warning: '' is deprecated [-Wdeprecated-declarations]
        hsc_peek (sfMouseWheelEvent, y);
                  ^
    /usr/local/Cellar/csfml/2.4/include/SFML/Window/Event.h:126:9: note: '' has been explicitly marked deprecated here
    typedef struct CSFML_DEPRECATED
            ^
    3 warnings generated.
    JoystickIdentification.hsc:18:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    Mouse.hsc:22:9: warning: 'hsc_alignment' macro redefined [-Wmacro-redefined]
    #define hsc_alignment(t ) hsc_printf ( "%lu", (unsigned long)offsetof(struct {char x__; t(y__); }, y__));
            ^
    /Users/simon/.stack/programs/x86_64-osx/ghc-8.0.2/lib/ghc-8.0.2/template-hsc.h:88:9: note: previous definition is here
    #define hsc_alignment(t...) \
            ^
    1 warning generated.
    [ 1 of 75] Compiling SFML.Window.WindowHandle ( src/SFML/Window/WindowHandle.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/WindowHandle.o )
    [ 2 of 75] Compiling SFML.Window.VideoMode ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/VideoMode.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/VideoMode.o )
    [ 3 of 75] Compiling SFML.Window.Types ( src/SFML/Window/Types.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Types.o )
    [ 4 of 75] Compiling SFML.Window.Keyboard ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Keyboard.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Keyboard.o )
    [ 5 of 75] Compiling SFML.Window.JoystickIdentification ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/JoystickIdentification.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/JoystickIdentification.o )
    [ 6 of 75] Compiling SFML.Window.Joystick ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Joystick.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Joystick.o )
    [ 7 of 75] Compiling SFML.Window.ContextSettings ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/ContextSettings.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/ContextSettings.o )
    [ 8 of 75] Compiling SFML.Utils       ( src/SFML/Utils.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Utils.o )
    [ 9 of 75] Compiling SFML.System.Vector3 ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Vector3.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Vector3.o )
    [10 of 75] Compiling SFML.System.Vector2 ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Vector2.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Vector2.o )
    [11 of 75] Compiling SFML.Window.Mouse ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Mouse.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Mouse.o )
    [12 of 75] Compiling SFML.Window.Event ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Event.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Event.o )
    [13 of 75] Compiling SFML.System.Time ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Time.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Time.o )
    [14 of 75] Compiling SFML.System.Sleep ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Sleep.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Sleep.o )
    [15 of 75] Compiling SFML.System.InputStream ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/InputStream.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/InputStream.o )
    [16 of 75] Compiling SFML.SFResource  ( src/SFML/SFResource.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/SFResource.o )
    [17 of 75] Compiling SFML.Window.Context ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Context.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Context.o )
    [18 of 75] Compiling SFML.SFException ( src/SFML/SFException.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/SFException.o )
    [19 of 75] Compiling SFML.SFDisplayable ( src/SFML/SFDisplayable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/SFDisplayable.o )
    [20 of 75] Compiling SFML.Window.SFWindow ( src/SFML/Window/SFWindow.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/SFWindow.o )
    [21 of 75] Compiling SFML.Window.Window ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Window.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window/Window.o )
    [22 of 75] Compiling SFML.SFCopyable  ( src/SFML/SFCopyable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/SFCopyable.o )
    [23 of 75] Compiling SFML.System.Clock ( src/SFML/System/Clock.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System/Clock.o )
    [24 of 75] Compiling SFML.System      ( src/SFML/System.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/System.o )
    [25 of 75] Compiling SFML.Window      ( src/SFML/Window.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Window.o )
    [26 of 75] Compiling SFML.Graphics.Types ( src/SFML/Graphics/Types.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Types.o )
    [27 of 75] Compiling SFML.Graphics.SFSmoothTexture ( src/SFML/Graphics/SFSmoothTexture.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFSmoothTexture.o )
    [28 of 75] Compiling SFML.Graphics.SFShapeResizable ( src/SFML/Graphics/SFShapeResizable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFShapeResizable.o )
    [29 of 75] Compiling SFML.Graphics.SFCoordSpace ( src/SFML/Graphics/SFCoordSpace.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFCoordSpace.o )
    [30 of 75] Compiling SFML.Graphics.SFBindable ( src/SFML/Graphics/SFBindable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFBindable.o )
    [31 of 75] Compiling SFML.Graphics.Rect ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Rect.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Rect.o )
    [32 of 75] Compiling SFML.Graphics.SFBounded ( src/SFML/Graphics/SFBounded.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFBounded.o )
    [33 of 75] Compiling SFML.Graphics.SFViewable ( src/SFML/Graphics/SFViewable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFViewable.o )
    [34 of 75] Compiling SFML.Graphics.Texture ( src/SFML/Graphics/Texture.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Texture.o )
    [35 of 75] Compiling SFML.Graphics.Transform ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Transform.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Transform.o )
    [36 of 75] Compiling SFML.Graphics.SFTransformable ( src/SFML/Graphics/SFTransformable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFTransformable.o )
    [37 of 75] Compiling SFML.Graphics.View ( src/SFML/Graphics/View.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/View.o )
    [38 of 75] Compiling SFML.Graphics.PrimitiveType ( src/SFML/Graphics/PrimitiveType.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/PrimitiveType.o )
    [39 of 75] Compiling SFML.Graphics.Glyph ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Glyph.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Glyph.o )
    [40 of 75] Compiling SFML.Graphics.FontInfo ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/FontInfo.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/FontInfo.o )
    [41 of 75] Compiling SFML.Graphics.Font ( src/SFML/Graphics/Font.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Font.o )
    [42 of 75] Compiling SFML.Graphics.Color ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Color.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Color.o )
    [43 of 75] Compiling SFML.Graphics.Image ( src/SFML/Graphics/Image.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Image.o )
    [44 of 75] Compiling SFML.Graphics.SFShape ( src/SFML/Graphics/SFShape.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFShape.o )
    [45 of 75] Compiling SFML.Graphics.SFTexturable ( src/SFML/Graphics/SFTexturable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFTexturable.o )
    [46 of 75] Compiling SFML.Graphics.ConvexShape ( src/SFML/Graphics/ConvexShape.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/ConvexShape.o )
    [47 of 75] Compiling SFML.Graphics.RectangleShape ( src/SFML/Graphics/RectangleShape.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/RectangleShape.o )
    [48 of 75] Compiling SFML.Graphics.Shader ( src/SFML/Graphics/Shader.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Shader.o )
    [49 of 75] Compiling SFML.Graphics.Shape ( src/SFML/Graphics/Shape.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Shape.o )
    [50 of 75] Compiling SFML.Graphics.Text ( src/SFML/Graphics/Text.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Text.o )
    [51 of 75] Compiling SFML.Graphics.Vertex ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Vertex.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Vertex.o )
    [52 of 75] Compiling SFML.Graphics.VertexArray ( src/SFML/Graphics/VertexArray.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/VertexArray.o )
    [53 of 75] Compiling SFML.Graphics.CircleShape ( src/SFML/Graphics/CircleShape.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/CircleShape.o )
    [54 of 75] Compiling SFML.Graphics.BlendMode ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/BlendMode.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/BlendMode.o )
    [55 of 75] Compiling SFML.Graphics.RenderStates ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/RenderStates.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/RenderStates.o )
    [56 of 75] Compiling SFML.Graphics.SFRenderTarget ( src/SFML/Graphics/SFRenderTarget.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFRenderTarget.o )
    [57 of 75] Compiling SFML.Graphics.RenderTexture ( src/SFML/Graphics/RenderTexture.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/RenderTexture.o )
    [58 of 75] Compiling SFML.Graphics.RenderWindow ( src/SFML/Graphics/RenderWindow.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/RenderWindow.o )
    [59 of 75] Compiling SFML.Graphics.SFDrawable ( src/SFML/Graphics/SFDrawable.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/SFDrawable.o )
    [60 of 75] Compiling SFML.Graphics.Sprite ( src/SFML/Graphics/Sprite.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics/Sprite.o )
    [61 of 75] Compiling SFML.Graphics    ( src/SFML/Graphics.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Graphics.o )

    /private/var/folders/r7/f9j9c2zd1k97v47cr84j_qvc0000gn/T/stack55950/SFML-<IP_ADDRESS>/src/SFML/Graphics.hs:19:2: warning: [-Wtabs]
        Tab character found here.
        Please use spaces instead.
    [62 of 75] Compiling SFML.Audio.Types ( src/SFML/Audio/Types.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/Types.o )
    [63 of 75] Compiling SFML.Audio.SoundStatus ( src/SFML/Audio/SoundStatus.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundStatus.o )
    [64 of 75] Compiling SFML.Audio.SFSoundRecorder ( src/SFML/Audio/SFSoundRecorder.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SFSoundRecorder.o )
    [65 of 75] Compiling SFML.Audio.SFSoundBuffer ( src/SFML/Audio/SFSoundBuffer.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SFSoundBuffer.o )
    [66 of 75] Compiling SFML.Audio.SFSound ( src/SFML/Audio/SFSound.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SFSound.o )
    [67 of 75] Compiling SFML.Audio.Sound ( src/SFML/Audio/Sound.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/Sound.o )
    [68 of 75] Compiling SFML.Audio.SoundStream ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundStream.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundStream.o )
    [69 of 75] Compiling SFML.Audio.SFSampled ( src/SFML/Audio/SFSampled.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SFSampled.o )
    [70 of 75] Compiling SFML.Audio.SoundBuffer ( src/SFML/Audio/SoundBuffer.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundBuffer.o )
    [71 of 75] Compiling SFML.Audio.SoundBufferRecorder ( src/SFML/Audio/SoundBufferRecorder.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundBufferRecorder.o )
    [72 of 75] Compiling SFML.Audio.SoundRecorder ( src/SFML/Audio/SoundRecorder.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/SoundRecorder.o )
    [73 of 75] Compiling SFML.Audio.Music ( src/SFML/Audio/Music.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/Music.o )
    [74 of 75] Compiling SFML.Audio.Listener ( src/SFML/Audio/Listener.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio/Listener.o )
    [75 of 75] Compiling SFML.Audio       ( src/SFML/Audio.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/SFML/Audio.o )

    /private/var/folders/r7/f9j9c2zd1k97v47cr84j_qvc0000gn/T/stack55950/SFML-<IP_ADDRESS>/cbits/SFML/Graphics/Font_helper.c:6:67: error:
         error: too few arguments to function call, expected 5, have 4
            *glyph = sfFont_getGlyph (font, codePoint, characterSize, bold);
                     ~~~~~~~~~~~~~~~                                      ^

    /usr/local/Cellar/csfml/2.4/include/SFML/Graphics/Font.h:100:1: error:
         note: 'sfFont_getGlyph' declared here
    CSFML_GRAPHICS_API sfGlyph sfFont_getGlyph(sfFont* font, sfUint32 codePoint, unsigned int characterSize, sfBool bold, float outlineThickness);
    ^

    /usr/local/Cellar/csfml/2.4/include/SFML/Graphics/Export.h:43:32: error:
         note: expanded from macro 'CSFML_GRAPHICS_API'
            #define CSFML_GRAPHICS_API CSFML_API_IMPORT
                                       ^

    /usr/local/Cellar/csfml/2.4/include/SFML/Config.h:101:34: error:
         note: expanded from macro 'CSFML_API_IMPORT'
                #define CSFML_API_IMPORT CSFML_EXTERN_C __attribute__ ((__visibility__ ("default")))
                                         ^

    /usr/local/Cellar/csfml/2.4/include/SFML/Config.h:43:28: error:
         note: expanded from macro 'CSFML_EXTERN_C'
            #define CSFML_EXTERN_C extern
                                   ^
    1 error generated.
    `gcc' failed in phase `C Compiler'. (Exit code: 1)

Wow, I have the exact same issue.

Here's a quick fix: https://github.com/biglambda/SFML/commit/0b57192a638d70690c1b6d1e455bcb9011f24583

That is right; last time I touched these bindings SFML was at version 2.3. Do you want to make a pull request with that fix or make changes directly to this repo?

I think thats a hack, I didn't actually pipe the parameter all the way up to the binding, I just put a default in. This gets it to compile basically.


Paging for mailing list members

For this API https://github.com/mailgun/mailgun-java#list-of-members, we can only limit the number of records. But in the response, there is an paging object and there is no function to get the next page data.

@arundaskd, thanks for raising this issue!
Sorry for the late reply.
The mentioned functionality was updated in the new release 1.1.0
Now you can get the first / last / next / previous page data by referencing this documentation: List of members
Please let us know If your issue is resolved and If we can close this ticket

the issue has been commented on, fixed and is closed due to the lack of an answer


Drop the use of load_only() where no longer needed

Since Release.description is now deferred by default, we no longer need to bend over backwards with load_only to attempt to minimize data. While the minimized queries are still technically more efficient since we're only pulling over exactly what we need, they are not meaningfully more efficient and are more likely to accidentally trigger N+1 query issues.

@ewdurbin Changes made!


bug: release process fails

When creating a new release using nx release, the ci job publish fails every time - https://github.com/s1seven/schema-tools/actions/runs/8157244270/job/22296463018
The issue is that the root package-lock.json file is not in sync after the updates, causing the ci to fail with the following error:
npm ERR! npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.
Investigate why the updated package-lock.json file is not being automatically committed.

It seems that nx release calls a function called updateLockFile which runs npm install --package-lock-only which removes some entries from the package-lock.json file which is causing it to be out of sync with the package.json file, see the root package-lock.json file on this commit
There are several issues open on the nx repo that may be related:
https://github.com/nrwl/nx/issues/22066
https://github.com/nrwl/nx/issues?q=is%3Aissue+package-lock.json


fix: attempt to fix ci script

:tada: This PR is included in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Auto add language tag when posting kata issue

Right now when user posts an issue to a multilanguage kata it is not shown what language is that issue related to.
I suggest to add a language tag to such posts automatically, for example pre-insert it into the text field in square brackets, based on the language currently used.

+100: apparently most users don't get that an author or contributor just can't divinely guess what's going on and that would help. A LOT.

This might lead to wrong results if a user switches or completely disables the current language. However, a simple check whether the user has mentioned any programming language at all when he submits a message would be helpful, something along
var re = /(^|\s+)((java|coffee)script|java|haskell|c#|clojure|python|ruby)(\s+|[\.,\-!?])/ig
if(post_message.match(re) === null){
  if(window.confirm("You didn't specify a language for your issue. Do you really want to post it?")){
    /* post it */
  }
}

As a follow up - it is sometimes useful to see not only submitted solutions, but also attempted solutions of newbies when they post "issues". I'm not sure how hard to implement is that, but that really would be awesome if there was a way to see the current solution status (even if unfinished) of a poster, of course as a spoiler.

it is [..] useful to see [...] attempted solutions

I would refrain from this, as long as one cannot delete attempted solutions. For example, I have ~170 unfinished katas, most of them unfinished due to time, technical problems, or simply by giving up.

I meant such solutions to be shown ONLY when one posts into kata discourse, so that others can help him find out if this is his/her issue or kata issue. Perhaps it could be conditional, e. g. when someone posts, ask him if he wants to include current solution attempt into his post.
It was not my intention to make all attempted solutions available for review, that would be rather uncomfortable.

+1 to the check bkaes-senpai has proposed.
[And I didn't expect him to have those many unfinished katas, but I guess
that in a given amount of time one accumulates a lot]
On Wed, Jul 15, 2015 at 1:12 AM, MMMAAANNN<EMAIL_ADDRESS>wrote:

I meant such solutions to be shown ONLY when one posts into kata
discourse, so that others can help him find out if this is his/her issue or
kata issue. Perhaps it could be conditional, e. g. when someone posts, ask
him if he wants to include current solution attempt into his post.
It was not my intention to make all attempted solutions available for
review, that would be rather uncomfortable.
—
Reply to this email directly or view it on GitHub
https://github.com/Codewars/codewars.com/issues/124#issuecomment-121421450
.


Timer specification

So far PNA assumes the data plane supports a timer, but a timer is not defined as an extern. If not defined, how do implementations know which control blocks are allowed to use the timer extern? Or the timer can be used anywhere in the P4 program?

The only way in which PNA assumes that the data plane supports a timer is for the idle timeout behavior of tables.
A P4 target device can support idle timeout behavior WITHOUT exposing the timer functionality to the P4 developer, and making it available from a P4 control.
If a P4 target device has limits on HOW MANY P4 tables are allowed to use the idle timeout behavior, that is device-specific, and the device's P4 compiler should reject any P4 programs that try to use more such tables than the device supports.
A device's documentation should ideally document any limits it has in such an area, and many others.

Good clarifications, thanks. What about TCP timers to maintain state? Doesn't cpu offload TCP termination to nic in many products?

Whether a NIC implements TCP termination or not is target-specific, and currently not even mentioned in the PNA spec as a required feature.  Whether and how that feature is exposed to P4 developers is thus target-specific.

Ok, got it, thanks.


[AMBARI-24312] [LogSearch UI] Audit screen sub tab changes clear the Summary charts.

What changes were proposed in this pull request?
The graph creation process now is triggered from afterViewInit too, since we have to be sure that the chart has been created event if the afterViewInit runs later then ngOnChanges (so that the host property will be available later.
How was this patch tested?
It was tested manually and by running unit tests (Executed 268 of 268 SUCCESS (8.955 secs / 8.837 secs))
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3197/
Test PASSed.


Help

can i speak with you on discord?

Yes sure, my discord is notzastix send me a friend request or you can join my server


Fix footer and padding on hovering over links

Issues to be fixed: (first pic)

Footer can be made bold to make it readable
On hovering, need to add padding to make links look better on website

We shouldn't be adding/chaning padding on hover, that'll cause other elements to shift from their natural position, which doesn't look really nice
We could either make the text being hovered either bold or change its color or add shadow or underline or something
Hope that makes sense, let me know if you've any doubts!

We shouldn't be adding/chaning padding on hover, that'll cause other elements to shift from their natural position, which doesn't look really nice We could either make the text being hovered either bold or change its color or add shadow or underline or something Hope that makes sense, let me know if you've any doubts!

We shouldn't be adding/chaning padding on hover, that'll cause other elements to shift from their natural position, which doesn't look really nice We could either make the text being hovered either bold or change its color or add shadow or underline or something Hope that makes sense, let me know if you've any doubts!

Yes, I agree. But I have added padding to the links text and not while on hovering over the links. That won't affect the natural position of any element. I have already taken your point in consideration while making the changes.

2. On hovering, need to add padding to make links look better on website

Isn't that a bit confusing then?

On hovering, need to add padding to make links look better on website

Isn't that a bit confusing then?

My bad, I don't how to explain. I'll probably add a video demo or direct PR for that (whichever option you suggest).

Issues to be fixed: (first pic)

Footer can be made bold to make it readable
On hovering, need to add padding to make links look better on website

2nd point can be Add some padding to event links, therefore on hover when background changes, it should have some padding.


Implements tuple<->product conversions

Resolves #62
TupleConversion is just copied from zio-config - maybe we should consider adding it to zio itself, as it is general purpose enough, similarly to Zippable/Unzippable.

Nice!

They could be interesting as you as well. Due to the domain, I think it’s less commonly needed, but may be useful in certain cases. Any thoughts @adamgfraser?
Although. If this infers nicely, it might work for ZLayer.fromConstructor

It is certainly generally useful. I am a little Leary of adding things to ZIO Core that are generally useful but not necessary for what we are doing there. Maybe this belongs in zio-deriving?


Question: when to use StyleSpans?

I have a CodeArea. For piece of a text I can set style using StyleSpansor without them:
textArea.setStyleSpans(int from,  StyleSpans<? extends S> styleSpans)//with
textArea.setStyleClass(int from, int to, String styleClass)//without

Could anyone explain when I should use StyleSpans?

There are two cases for when to use StyleSpans:

setStyleClass will erase & replace the current styling of the specified range, while setStyleSpans will add the provided styling to any existing styling.
Every setStyleClass and setStyleSpans invocation is a single change event to the text which triggers a redraw for each change. If however you want to bundle multiple style changes into one undo event or optimize the amount of redrawing then you can bundle a group of StyleSpans together using StyleSpansBuilder and submit them in one go with setStyleSpans. Note that a series of StyleSpans are consecutive, that is the next StyleSpan position starts where the last one ended. So if you need to change separate sections of text in one go, you can insert an empty StyleSpan with the appropriate length to "move the change cursor" to the next change position.

So you would have to get the style spans for the section of text that you are interested in, make changes to the style spans as appropriate, and then apply the changed style spans back. Something like:
    private void changeStyle( IndexRange range )
    {
        if ( range.getLength() > 0 )
        {
            var newStyles = new StyleSpansBuilder<String>();

            for ( var span : area.getStyleSpans( range ) )
            {
                var style = span.getStyle();

                // Add or Remove styles as appropriate

                newStyles.add( style, span.getLength() );
            }

            area.setStyleSpans( range.getStart(), newStyles.create() );
        }
    }

You can also try going from style span to style, something like:
private void changeParagraphStyle( int p )
{
    var para = area.getParagraphs.get(p);
    var spanStart = 0;

    for ( var span : para.getStyleSpans() )
    {
        var style = span.getStyle();

	// Add or Remove styles as appropriate

        area.setStyle( p, spanStart, spanStart+span.getLength(), style  );

        spanStart += span.getLength();
    }
}

Could something in StyleSpans (ApiDoc) (Code) maybe help you ?

Maybe you should use a custom style class instead, where you can put the extra information etc. Try the the following framework to get started:
    public class CustomStyleArea extends StyledTextArea<String,MyStyle>
    {
        public CustomStyleArea()
        {
            super( "", CustomStyleArea::styleParagraph, MyStyle.NONE, CustomStyleArea::styleText );
            // Style codecs are used for (de)serialization during copy, paste, save, and load
            setStyleCodecs( Codec.STRING_CODEC, Codec.styledTextCodec(new MyStyleCodec()) );
        }

        private static void styleParagraph( TextFlow paragraph, String style )
        {
            // paragraph.getStyleClass().addAll( styles );
            paragraph.setStyle( style );
        }

        private static void styleText( TextExt text, MyStyle style )
        {
            // text.getStyleClass().addAll( style.getCssClasses() );
            // or
            // text.setStyle( style.getCss() );
        }
    }

    class MyStyle
    {
        public static final MyStyle NONE = new MyStyle();

        // TODO Styling info plus any extra data, flags, and methods eg:
        // public List<String> getCssClasses()
        // public String getCss()
    }

    /**
     * Codec methods are used for (de)serialization during copy, paste, saving, and load.
     * Note: you can leave this till last, once you've finished MyStyle.
     */
    class MyStyleCodec implements Codec<MyStyle>
    {
        @Override public String getName()
        {
            return "richtextfx/mystyle";
        }

        @Override public void encode( DataOutputStream os, MyStyle t ) throws IOException
        {
            // TODO
        }

        @Override public MyStyle decode( DataInputStream is ) throws IOException
        {
            // TODO
            return null;
        }
    }