readme.md clarification

can you please clarify this statement?
"The MAC must match the programmed MAC, it seems there firmware checks this against the MAC burned in CCFG"
are you saying we must use the mac originally printed on the detachable base or it won't work?  my sensors with 00000000 mac are hopelessly mixed up together at this point.  trial & error could run into the 100s of flashes.

Yes, it must be the MAC printed on the case or what you can read from the CCFG data region. You should be able to find the MAC by reading the flash.

thanks!  given the number of sensors involved this likely is my only viable option.  i have 0 experience with jtag type flashing so please don't shy away from being too rudimentary in your instructions.
i'm finding it increasing difficult to understand the mechanism for how the mac is lost in the first place.  the lost mac can be superimposed over a doner firmware so somehow it's lost from the original firmware, but is that really the case?  the firmware resides in flash and so does the CCFG which it performs a check against.  even with the lost mac the sensor is still able to function except that it can't be distinguished from any other sensor with a null or 00000000 mac.  my initial understanding was that the flash was somehow lost in a low/dead battery condition, but this would mean the entire firmware and CCFG would be lost which can't be the case.  i haven't examined your script, but you stress that your solution is a hack so i have to think you're modifying something else to circumvent the condition of the lost mac and that once the mac is lost from whatever critical location it's stored in--it's lost forever?

I compared a working vs. lost MAC firmware image and the places where the MAC was became null. I don't know why, I just know a find and replace worked only for the MAC that is in the CCFG.

absolutely bizarre.  has me wondering how the battery is even involved

@dannutu The cheap one works. That's exactly what I used, the launchpad eval module. You remove the jumpers and just connect it to the sensor.

The python script didn't work for me on my mac (i tried using terminal) so instead, I manually changed the AABBCCDD mac address using find/replace in BBedit and it worked like a charm.  Just in case someone out there has that same issue

@dannutu The cheap one works. That's exactly what I used, the launchpad eval module. You remove the jumpers and just connect it to the sensor.

@sycophantic I had the CC1310 Launchpad since January and I finally took some time today to try to resurrect my dead Wyze contact sensors.
I installed Uniflash on a spare Windows machine and it detects the CC1310 Launchpad as CC1310F128. This is exactly what's printed on top of the small square chip in the middle of the Launchpad board so all is good so far. Once I select CC1310F128 Uniflash shows "Selected connection: Texas Instruments XDS110 Debug Bridge", which matches the ports under "Device Manager", which I think it's how it should be.
The first time I tried to "load" the patched firmware to the contact sensor Uniflash said it needed to update the firmware in the Launchpad itself. It failed the first time, I closed it and restarted it and then it worked and the board was successfully updated.
But I cannot get any further - no matter what I try in Uniflash (e.g. "more info", "erase flash" or "load") I get one of two errors:
"Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register" or "Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed"
I googled, I even watched some youtube videos (from TI themselves and a few others) but I can't figure what's wrong and how can I make progress. The TI youtube video ("SimpleLink™ Wi-Fi ® CC3220 Getting Started with Project 0") was for another Launchpad board and an older version of Uniflash, it talked about having to put the Launchpad board into "Development mode" but I can't see that option in the latest version of Uniflash from the TI web site. Not sure at all if it's still needed or it's just old info nowadays. The Uniflash "help" opens a web page from the TI site, there is no mention of any errors codes, descriptions nor ways to fix them.
I followed the steps described here: https://forums.wyzecam.com/t/unbricking-wyze-contact-sensor-pcb-reset-pin/146856/102
I configured the jumpers as in this picture https://aws1.discourse-cdn.com/wyze/optimized/3X/9/e/9eaf0b965af1fb96817e1ac708d59d8d36c936bd_2_440x499.jpeg
When the Wyze contact sensor gets 3.3V via the Launchpad board the red LED blinks twice.
The magnet makes the Wyze contact sensor blink as expected.
When trying to erase the flash or load the patched firmware the magnet is touching the sensor.
I even changed the USB cables between the Windows machine and the Launchpad board - nothing helped.
I've run out of ideas here, would you by any chance have a hint, please? Cheers!

The python script didn't work for me on my mac (i tried using terminal) so instead, I manually changed the AABBCCDD mac address using find/replace in BBedit and it worked like a charm. Just in case someone out there has that same issue

@exeljb I closely followed the steps you described on the wyzecam forum but I'm stuck getting "Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register" or "Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed", do you have any idea(s)? It's my very first contact with the Launchpad board and Uniflash and I have to say it's a bit daunting. Many thanks!

BTW, I can see cJTAG comms over TCK and TMS using a protocol analyser whenever I try to "erase flash", "load" or "more info", however the protocol decoder throws an error. I don't yet know if that's because the sampling rate of 12 MHz is not fast enough for cJTAG, the computer is running out of memory before capturing all the cJTAG data, or maybe something else.

Ha, I figured it out, it was the windows firewall, for whatever reason it needs inbound access. Once I allowed that I could reflash the 2 sensors and they are both working again now. Thanks for figuring out how to do this, is there a way I could buy you a virtual coffee or something like that?


It support Comet Lake？

My computer CPU is i7 10510U

Someone knows if is necessary a Comet Lake version for mapping USB ports?


add API to return the number of allocation slots

RGB assets are allocated to colorable UTXOs. One UTXO can support more than one allocation, depending on the value of max_allocations_per_utxo (in WalletData) provided at wallet instantiation time.
It would be useful to be able to query how many available allocations slots the wallet has. An example use case would be to know if new colorable UTXOs need to be created, in advance rather in response to an error when e.g. calling blind_receive.

name: allocations
parameters: none
response: a new Allocations struct containing

total_available: the number of total available allocations
map: a map of UTXOs and the respective allocations (given the current value of max_allocations_per_utxo)

key: utxo
value:

used: the number of currently used allocations
available:  the number of currently available allocations

With this data, the user can easily know:

if there is at least one available allocation
the total number of possible new allocations, before having to create more UTXOs
the number of UTXOs that can support a new allocation

Notes:

the number of used allocations can be obtained via get_rgb_allocations
the number of available allocations corresponds to the value of max_allocations_per_utxo minus the currently used allocations

"Hi everyone from Plan ₿ Tech School, I'm interested in working on this problem. I plan to implement the allocations structure described in the problem. Are there any preferences on how to structure the data or UTXO mapping?"
I'm planning a test that verifies that after calling create_utxos on a new wallet, the allocations API returns the number of UTXOs created multiplied by max_allocations_per_utxo.
Thanks in advance for any feedback!

"Hi everyone from Plan ₿ Tech School, I'm interested in working on this problem. I plan to implement the allocations structure described in the problem. Are there any preferences on how to structure the data or UTXO mapping?"

I'm not sure what you're asking, the issue already describes the structure the API response should have.

I'm planning a test that verifies that after calling create_utxos on a new wallet, the allocations API returns the number of UTXOs created multiplied by max_allocations_per_utxo.

This is a good idea!


ARM64 version on Windows - Extensions fail to install from store.

Steps to Reproduce:

Launch VS Code
Notice the Run Icon is missing

Try to install any extension (e.g. visualstudioexptteam.vscodeintellicode )
Notice that extension fails to install

Download vsix manually
Install vsix and notice that extension installs without problems.

VS Code version: Code - Insiders 1.46.0-insider (1d268b701376470bc638100fbe17d283404ac559, 2020-05-28T08:45:28.569Z)
OS version: Windows_NT arm64 10.0.19041

System Info

Item
Value

CPUs
Microsoft SQ1 @ 3.0 GHz (8 x 1670)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.54GB (1.80GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.51.0

remote-wsl
ms-
0.44.2

powershell
ms-
2020.4.0

 paste.

I don't think it's ARM specific, most likely same problem in all insiders builds: #98726

It seems you're right! Did a search for issues related to the new ARM release but didn't think to include all versions, my bad. Closing the issue.

Fixed it and triggered new insiders release.

From https://github.com/microsoft/vscode/issues/98726#issuecomment-635486050

Off-topic: How do you find VS Code on SP X ? Is in possible to work on Windows side (for Node.js and other JS related stuff if you use it) or better to use WSL/SSH from the beginning?

Off-topic: How do you find VS Code on SP X ? Is in possible to work on Windows side (for Node.js and other JS related stuff if you use it) or better to use WSL/SSH from the beginning?

It is sure possible to install nodejs, git and all other dependencies on Windows but I prefer WSL2 since all (nodejs, git, etc..) is ARM native under linux while most of the stuff runs emulated in windows (also, vscode WSL extension works great).
 Also battery charges in 1 hour.

Thanks for feedback!


remaining pages button in pagination

When I click on remaining-pages-button in your simple table example pagination, it shows me only last page 6 and I am remaining-pages-button button is disabled. But there are 7 pages.
Do you have some explanation for this, or is it a bug?

@berc this will be fixed once #138 is released

Thanks @seminull, sorry for the delay for the new feature. Make sure to have this release on the weekend. I'm changing team on Twitter and I didn't have so much time to work on open source stuff :(
See you soon! Grazie


Google Sheets support is broken

A few users have reported that Google Sheets support is broken, since Google have changed their API. This should be fixed.

Closing as duplicate of #461


Can I create kiwi_generator record for a string?

Something like
@Register.singleton('localhost', name: 'websiteUrl' )

So that I can easily change it for dev/staging/prod. Often it is useful for other classes created via DIC to have these string parameters. And I cannot come up with any other way than to create a class for each environment and register the class instead.

That is not possible with the genrator. You should register that manually.
KiwiContainer().registerSingleton((container) => 'This is an awesome string', name: 'string_named');

The generator will generate a dependency three. But because your string does not have a constructor or a factory method. it should be added manually.
We register this in our main.dart file. Or call a function that registers this string.

@vanlooverenkoen OK, good to know. How do I then resolve the issue where I want the string to be a dependency for something I create via the generator? A assume it is not possible? And I have to also do it the same way in the main.dart file when I register the string?

That would look like this:
import 'package:kiwi/kiwi.dart';

part 'kiwi_generator_example.g.dart';

abstract class Injector {
  @Register.singleton(Service, resolvers: {String: 'my_awesome_string'})
  void configure();
}

class Service {
  Service(String serviceA);
}

void setup(String value) {
  var injector = _$Injector();
  KiwiContainer().registerSingleton((container) => value, name: 'my_awesome_string');
  injector.configure();
}

@vanlooverenkoen thank you for the example. One more question - sorry if too obvious I am new to dart - how do I pass the string value to setup?

your main.dart file
import 'packages:my_app:your_path_to_injector.dart'

void main() {
 setup('your awesome string');

 runApp(MyApp());
}

your injector.dart file
import 'package:kiwi/kiwi.dart';

part 'kiwi_generator_example.g.dart';

abstract class Injector {
  @Register.singleton(Service, resolvers: {String: 'my_awesome_string'})
  void configure();
}

class Service {
  Service(String serviceA);
}

void setup(String value) {
  var injector = _$Injector();
  KiwiContainer().registerSingleton((container) => value, name: 'my_awesome_string');
  injector.configure();
}

One important part to note. is that this will only use the same string. It is best to have multiple main.dart files so threeshaking can be done on your code correctly. If you only include another dart file in main_alpha.dart it will not be shiped with the main_beta.dart app. Take a look at flavors for flutter. Or just use different main.dart files for eacht env/flavor

@vanlooverenkoen Thank you, you have been a big help. Is there a way I can https://www.buymeacoffee.com/ or something? :smile:

Haha https://www.buymeacoffee.com/vanlooverenkoen is my link


Return null instead of exception when job output prop does not exist …

…and show READY jobs in UI.
In Azkaban partial execution, some jobs can start even if some job output prop is missing.

Pull Request Test Coverage Report for Build 7106

3 of 5 (60.0%)  changed or added relevant lines in 1 file are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 45.464%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunner.java
3
5
60.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunner.java
6
78.09%

Totals

Change from base Build 7104:
-0.01%

Covered Lines:
18382

Relevant Lines:
40432

💛  - Coveralls


isPlainObject check fails in serverless env

When trying to use some of these hashing functions in the context of a serverless environment, such as vercel or cloudfare, this function
https://github.com/paulmillr/noble-hashes/blob/54c3197fc53bbfa4521b6883eed0e7bd1430beab/src/utils.ts#L163
fails to accept this object {c:2048,dkLen:64} as a plain object.
I have followed it down to this line:
obj.constructor === Object never being true. I'd suggest something like this instead:
obj.constructor.name === 'Object'

ah, applies to btc-signer, too:
Wrong object type for transaction options: [object Object]

We have other checks, like: a instanceof Uint8Array, which, I assume, would also fail in the scenario.

I have tested it: https://github.com/aulneau/noble-edge-bug/blob/main/src/pages/api/index.ts
Here is a reproduction. I'm not familiar with the reliability of constructor.name or not unfortunately.

I think we can remove obj.constructor === Object check. Object.prototype.toString.call is already done. That would make it return different result for ({__proto__: []}), but if tests pass, I think it could work.
The function is used in only a few places.

@aulneau fixed!


Support leak checking

What problem does this PR solve?
What is changed and how does it work?
What's more, I extract the panic check and leak check and create an interface named plugin.
To enable leak checking, set the -plugin.leak.eat=/resources/leak/eat.txt.
Check List
Tests

Unit test
E2E test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has Go code change
Has CI related scripts change
Has Terraform scripts change

Side effects

Breaking backward compatibility

Related changes

Need to update the documentation

Does this PR introduce a user-facing change?:

NONE

goroutine 538 [select, 20 minutes]:
github.com/pingcap/tidb/ddl.(*ddl).limitDDLJobs(0xc000b39e00)
        /home/jenkins/agent/workspace/tidb_release-4.0/go/src/github.com/pingcap/tidb/ddl/ddl_worker.go:209 +0x2e8
created by github.com/pingcap/tidb/ddl.(*ddl).Start
        /home/jenkins/agent/workspace/tidb_release-4.0/go/src/github.com/pingcap/tidb/ddl/ddl.go:320 +0x2ba

I caught a goroutine leak stack, and this stack trace isn't the same with one in eat.txt @jebter
goroutine 716 [select, 20 minutes]:
github.com/pingcap/tidb/ddl.(*ddl).limitDDLJobs(0xc007db6240)
	/home/jenkins/agent/workspace/tidb_release-3.0/go/src/github.com/pingcap/tidb/ddl/ddl_worker.go:191 +0x219
github.com/pingcap/tidb/ddl.(*ddl).start.func1.1()
	/home/jenkins/agent/workspace/tidb_release-3.0/go/src/github.com/pingcap/tidb/ddl/ddl.go:441 +0x2a
github.com/pingcap/tidb/util.WithRecovery(0xc006e127b8, 0xc006e127a8)
	/home/jenkins/agent/workspace/tidb_release-3.0/go/src/github.com/pingcap/tidb/util/misc.go:89 +0x57
github.com/pingcap/tidb/ddl.(*ddl).start.func1(0xc007db6240)
	/home/jenkins/agent/workspace/tidb_release-3.0/go/src/github.com/pingcap/tidb/ddl/ddl.go:440 +0xa3
created by github.com/pingcap/tidb/ddl.(*ddl).start
	/home/jenkins/agent/workspace/tidb_release-3.0/go/src/github.com/pingcap/tidb/ddl/ddl.go:438 +0x301


Suggestion: Add a couple bonus areas/easter eggs

Unless I did not discover such areas, it seems that the transformation mechanism is only used to progress through the story so far.
It would be nice to add a couple optional areas (doesn't have to be big, just an island with some coins for example) that can be accessed via transformation (e.g. one via flying and one via minimizing) to get some bonus coins, and/or an easter egg (could be a skeleton or a ghost urging you not to battle Satan, or a Godot avatar :P).

Thanks for the suggestion. It's a great idea and I particularly like the Godot avatar...
There's a lot of cleaning up to do on a post-jam version. We will probably start sometime in January, naively following the Jam rules.

The forest and the tombs would be a nice place to put Easter eggs.
Also, make one tormentor an Octocat with cool ability. They shared similar appearance.

I really like the idea of secret areas. But what's a tormentor with an Octocat?

The tormentor actually look like the Octocat. So, It would be nice if
there's a allied Octocat tormentor, for example
On Dec 25, 2017 11:13, "securas"<EMAIL_ADDRESS>wrote:
I really like the idea of secret areas. But what's a tormentor with an
Octocat?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/securas/Daemon-vs-Demon/issues/10#issuecomment-353822977,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aalf3pIcPsbuPrCHa3frIiF9QoblT7dJks5tDxLKgaJpZM4Q8qas
.


Disable automatic timer flush in logdev and simplify sync flushes

2 parts on this request

As we stand with current design for replication, we need to disable automatic timer flush in logdev. This would mean we split the logdev into 3 flush modes, (inline, timer, explicit). A logdev could be flushed in any combinations or all of them. For HomeObject use case, as it stands now, it will enable only explicit flush.

We have written logdev flush when there was no coroutines and everything is done async. As a result, there are lots of deadlock possibility when we tried to integrate with raft log store as they need sync code. It is time to use coroutines and significantly simplify and completely get rid of async flush.

We need to also take care of situation where raft can call compact/truncate on lsns which were not written yet.

we can not close it for now. 1 and 2 are implemented. but 3 seems not.
need @raakella1 to confirm it.

we do sync flush for log store now


disable specific dates using an array of dates.

Hi,
I want disable specific dates using an array of dates.

Same here.

Please make sure you search the closed issues for your question before opening your issue.
You can check #189 for how to disable specific dates

My apologies, I see that the helpful part of the issue I linked was added after you had opened this issue.


fix(label): text overflow for slotted headings

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] ~Docs have been reviewed and added / updated if needed (for bug fixes / features)~
[x] Build (npm run build) was run locally and any changes were pushed
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
Headings that are put in the slot of an ion-label don't inherit the text-overflow: ellipsis style.
Issue Number: #17087.
What is the new behavior?

Adds styling for slotted headings to inherit overflow and text-overflow.

Does this introduce a breaking change?

[ ] Yes
[x] No

If anyone really wanted headings inside labels to just have hidden overflow (very unlikely), they'd need to explicitly set the overflow.
Other information
Closes #17087.

master
branch

This looks good! Thank you! I made a small change to the test just to reduce the amount of words so that it would all fit in the screenshot. 🙂


Support persisting serialized Grants search criteria in the Postgres DB

Subtask of: #674
DOD: Saved searches can be created, retrieved, and deleted
Implementation details:

Write a Knex migration that creates a new table, grants_saved_searches with the following schema:

id: int, auto-increment, pk
name: text, not null
agency_id: int, fk to agencies.id, not null
created_by: int, fk to users.id, not null
created_at: timestamp with timezone, default CURRENT_TIMESTAMP, not null
criteria: text, not null

Write a src/db/ typescript module that provides an interface for the following activites:

Creates and saves a new saved search, given a name, agency ID, user ID, and criteria
Retrieves saved searches, given an agency ID, result limit, and result offset
Retrieves a count of results, given an agency ID, result limit, and result offset
Deletes saved searches, given an ID and agency ID (not just ID)

Write unit tests for the interface

Regarding the change, I'd like to hear from @cajinajr from the UX perspective, although I'd tend to agree with the premise that users seeing duplicate names could be confusing without any other compensating design factors.

That, however, may be taking security a bit far.

I think it's generally good practice to avoid leaking user strings beyond their intended scope. However, in this case, I see an argument for including agency_id in any unique index/constraint as one of usability- if I have a saved search called "My Awesome Filters", it should prevent anyone else from having their own "My Awesome Filters" saved search.
If @cajinajr agrees that the spec should be updated to enforce uniqueness, I'm on board, but I do think that the constraint needs to include the agency_id column.

Pulling this back since functionality is still being figured out.


error: "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"

When building the mlx project I'm getting an error in regards to : NEON intrinsics not available with the soft-float ABI
Please use -mfloat-abi=softfp or -mfloat-abi=hard
ChatGPT suggests updating MakeFile with, but this doesn't work
CFLAGS += -mfloat-abi=softfp

or updating CMakeLists.txt (in project root) didn't help either.
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mfloat-abi=softfp")

Steps to reproduce
git clone git@github.com:ml-explore/mlx.git mlx && cd mlx

mkdir -p build && cd build
cmake .. && make -j

throws
/Library/Developer/CommandLineTools/usr/lib/clang/15.0.0/include/arm_neon.h:28:2: error: "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
#error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
 ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:59:8: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
       ^~~~~~~~~~~
       float16_t
/Users/stephan/projects/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:59:34: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
                                 ^~~~~~~~~~~
                                 float16_t
...

Apple M1 Max
I'm on Sonoma 14.1.1 (23B81)
cmake version 3.27.9
Python 3.10.5

Full error list:
/Library/Developer/CommandLineTools/usr/lib/clang/15.0.0/include/arm_neon.h:28:2: error: "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
#error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
 ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:59:8: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
       ^~~~~~~~~~~
       float16_t
/Users/stephan/projects/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:59:34: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
                                 ^~~~~~~~~~~
                                 float16_t
/Users/stephan/projects/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:60:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vmulq_f16(x, vdupq_n_f16(1.442695)); // multiply with log_2(e)
                   ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:61:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vmaxq_f16(x, vdupq_n_f16(-14)); // clamp under with -14
                   ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:62:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vminq_f16(x, vdupq_n_f16(14)); // clamp over with 14
                   ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:64:3: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
  float16x8_t ipart = vrndmq_f16(vaddq_f16(x, vdupq_n_f16(0.5)));
  ^~~~~~~~~~~
  float16_t
/Users/stephan/projects/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:64:47: error: use of undeclared identifier 'vdupq_n_f16'
  float16x8_t ipart = vrndmq_f16(vaddq_f16(x, vdupq_n_f16(0.5)));
                                              ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:65:3: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
  float16x8_t fpart = vsubq_f16(x, ipart);
  ^~~~~~~~~~~
  float16_t
/Users/stephan/projects/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:65:23: error: use of undeclared identifier 'vsubq_f16'
  float16x8_t fpart = vsubq_f16(x, ipart);
                      ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:67:7: error: use of undeclared identifier 'vdupq_n_f16'
  x = vdupq_n_f16(1.535336188319500e-4f);
      ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:68:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.339887440266574e-3f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:69:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.339887440266574e-3f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:70:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(9.618437357674640e-3f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:71:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(5.550332471162809e-2f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:72:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(2.402264791363012e-1f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:73:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(6.931472028550421e-1f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:74:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.000000000000000f), x, fpart);
                ^
/Users/stephan/projects/mlx/mlx/backend/accelerate/softmax.cpp:78:3: error: unknown type name 'int16x8_t'; did you mean 'int16_t'?
  int16x8_t epart = vcvtq_s16_f16(ipart);
  ^~~~~~~~~
  int16_t
/Library/Developer/CommandLineTools/SDKs/MacOSX14.0.sdk/usr/include/sys/_types/_int16_t.h:30:33: note: 'int16_t' declared here
typedef short                   int16_t;
                                ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[2]: *** [CMakeFiles/mlx.dir/mlx/backend/accelerate/softmax.cpp.o] Error 1
make[1]: *** [CMakeFiles/mlx.dir/all] Error 2
make: *** [all] Error 2

Please reopen if this is still unresolved.

I have xcode installed (Version 15.0.1 (15A507))
$ xcode-select -p
/Applications/Xcode.app/Contents/Developer

FYI - The complete install worked on a Mac Studio (Apple M1 Ultra) but not on a MacBook Pro.

I also have this problem.  The key issue is the same:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/include/arm_neon.h:28:2: error: "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"

I'm running Sonoma 14.1.2 with a Macbookpro M2.
Cmake is version 3.27.1
xcode-select-p reports
/Applications/Xcode.app/Contents/Developer

Also with version 15.0.1

Sorry closed this prematurely, reopened.

I tried this with my M2 chip and it still doesn't compile for me.

Duplicate https://github.com/ml-explore/mlx/issues/51

I tried this with my M2 chip and it still doesn't compile for me.

Just to be sure, did the CMake build messages say “Building for arm” ?
it would be great if you could paste in all the results from the build command (add a -v option if doing a pip install from source)

That's probably the problem.  It's building for x86_64
-- Building METAL sources
-- Building with SDK for MacOS version 14.0

-- Building for processor x86_64
-- Accelerate found /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/System/Library/Frameworks/Accelerate.framework
CMake Deprecation Warning at build/_deps/doctest-src/CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

 Please use -mfloat-abi=softfp or -mfloat-abi=hard"
#error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard"
 ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:59:8: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
       ^~~~~~~~~~~
       float16_t
/Users/fozziethebeat/devel/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:59:34: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
inline float16x8_t neon_fast_exp(float16x8_t x) {
                                 ^~~~~~~~~~~
                                 float16_t
/Users/fozziethebeat/devel/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:60:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vmulq_f16(x, vdupq_n_f16(1.442695)); // multiply with log_2(e)
                   ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:61:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vmaxq_f16(x, vdupq_n_f16(-14)); // clamp under with -14
                   ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:62:20: error: use of undeclared identifier 'vdupq_n_f16'
  x = vminq_f16(x, vdupq_n_f16(14)); // clamp over with 14
                   ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:64:3: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
  float16x8_t ipart = vrndmq_f16(vaddq_f16(x, vdupq_n_f16(0.5)));
  ^~~~~~~~~~~
  float16_t
/Users/fozziethebeat/devel/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:64:47: error: use of undeclared identifier 'vdupq_n_f16'
  float16x8_t ipart = vrndmq_f16(vaddq_f16(x, vdupq_n_f16(0.5)));
                                              ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:65:3: error: unknown type name 'float16x8_t'; did you mean 'float16_t'?
  float16x8_t fpart = vsubq_f16(x, ipart);
  ^~~~~~~~~~~
  float16_t
/Users/fozziethebeat/devel/mlx/mlx/types/half_types.h:16:29: note: 'float16_t' declared here
typedef struct _MLX_Float16 float16_t;
                            ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:65:23: error: use of undeclared identifier 'vsubq_f16'
  float16x8_t fpart = vsubq_f16(x, ipart);
                      ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:67:7: error: use of undeclared identifier 'vdupq_n_f16'
  x = vdupq_n_f16(1.535336188319500e-4f);
      ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:68:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.339887440266574e-3f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:69:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.339887440266574e-3f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:70:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(9.618437357674640e-3f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:71:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(5.550332471162809e-2f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:72:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(2.402264791363012e-1f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:73:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(6.931472028550421e-1f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:74:17: error: use of undeclared identifier 'vdupq_n_f16'
  x = vfmaq_f16(vdupq_n_f16(1.000000000000000f), x, fpart);
                ^
/Users/fozziethebeat/devel/mlx/mlx/backend/accelerate/softmax.cpp:78:3: error: unknown type name 'int16x8_t'; did you mean 'int16_t'?
  int16x8_t epart = vcvtq_s16_f16(ipart);
  ^~~~~~~~~
  int16_t
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.0.sdk/usr/include/sys/_types/_int16_t.h:30:33: note: 'int16_t' declared here
typedef short                   int16_t;
                                ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[2]: *** [CMakeFiles/mlx.dir/mlx/backend/accelerate/softmax.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/mlx.dir/all] Error 2

I run into this issue, just trying it out on an M3 Pro device. By prepending the processor setting, I get the build to succeed on my machine. The build does issue a bunch of warnings, but may be worth trying:
CMAKE_SYSTEM_PROCESSOR=arm6 cmake .. && make -j 10

I run into this issue, just trying it out on an M3 Pro device. By prepending the processor setting, I get the build to succeed on my machine. The build does issue a bunch of warnings, but may be worth trying:
CMAKE_SYSTEM_PROCESSOR=arm6 cmake .. && make -j 10

Hi! Quick question, could you maybe share what warnings you get ?

I run into this issue, just trying it out on an M3 Pro device. By prepending the processor setting, I get the build to succeed on my machine. The build does issue a bunch of warnings, but may be worth trying:
CMAKE_SYSTEM_PROCESSOR=arm6 cmake .. && make -j 10

Hi! Quick question, could you maybe share what warnings you get ?

Certainly. I run a clean then rerun the build, here is the output:
√ isakatraore@Affinis in ~/code/applePlatforms/mlx/build
=> CMAKE_SYSTEM_PROCESSOR=arm6 cmake .. && make -j 10                                                                                12:56:14
-- Building METAL sources
-- Building with SDK for MacOS version 14.2
-- Building for processor arm64
-- Accelerate found /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Accelerate.framework
CMake Deprecation Warning at build/_deps/doctest-src/CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
-- Configuring done (0.8s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/isakatraore/code/applePlatforms/mlx/build
[ 17%] Built target mlx-metallib
[ 70%] Built target mlx
[ 77%] Built target linear_regression
[ 77%] Built target logistic_regression
[ 77%] Built target tutorial
[100%] Built target tests
√ isakatraore@Affinis in ~/code/applePlatforms/mlx/build
=> make .. clean                                                                                12:56:25
√ isakatraore@Affinis in ~/code/applePlatforms/mlx/build
=> CMAKE_SYSTEM_PROCESSOR=arm6 cmake .. && make -j 10                                                                                12:56:44
-- Building METAL sources
-- Building with SDK for MacOS version 14.2
-- Building for processor arm64
-- Accelerate found /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Accelerate.framework
CMake Deprecation Warning at build/_deps/doctest-src/CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
-- Configuring done (0.8s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/isakatraore/code/applePlatforms/mlx/build
[  1%] Building random.air
[  2%] Building softmax.air
[  3%] Building arange.air
[  4%] Building unary.air
[  6%] Building scan.air
[  6%] Building indexing.air
[ 11%] Building gemm.air
[ 11%] Building reduce.air
[ 11%] Building gemv.air
[ 11%] Building sort.air
[ 12%] Building copy.air
[ 13%] Building conv.air
[ 15%] Building binary.air
[ 16%] Building arg_reduce.air
[ 17%] Building mlx.metallib
[ 17%] Built target mlx-metallib
[ 18%] Building CXX object CMakeFiles/mlx.dir/mlx/dtype.cpp.o
[ 20%] Building CXX object CMakeFiles/mlx.dir/mlx/fft.cpp.o
[ 20%] Building CXX object CMakeFiles/mlx.dir/mlx/array.cpp.o
[ 23%] Building CXX object CMakeFiles/mlx.dir/mlx/ops.cpp.o
[ 23%] Building CXX object CMakeFiles/mlx.dir/mlx/graph_utils.cpp.o
[ 24%] Building CXX object CMakeFiles/mlx.dir/mlx/device.cpp.o
[ 25%] Building CXX object CMakeFiles/mlx.dir/mlx/random.cpp.o
[ 27%] Building CXX object CMakeFiles/mlx.dir/mlx/load.cpp.o
[ 27%] Building CXX object CMakeFiles/mlx.dir/mlx/allocator.cpp.o
[ 29%] Building CXX object CMakeFiles/mlx.dir/mlx/primitives.cpp.o
[ 30%] Building CXX object CMakeFiles/mlx.dir/mlx/transforms.cpp.o
[ 31%] Building CXX object CMakeFiles/mlx.dir/mlx/scheduler.cpp.o
[ 32%] Building CXX object CMakeFiles/mlx.dir/mlx/utils.cpp.o
[ 33%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/arg_reduce.cpp.o
[ 34%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/binary.cpp.o
[ 36%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/conv.cpp.o
[ 37%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/copy.cpp.o
[ 38%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/erf.cpp.o
[ 39%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/fft.cpp.o
[ 40%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/primitives.cpp.o
[ 41%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/reduce.cpp.o
[ 43%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/scan.cpp.o
[ 44%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/softmax.cpp.o
[ 45%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/sort.cpp.o
[ 46%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/threefry.cpp.o
[ 47%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/indexing.cpp.o
[ 48%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/common/load.cpp.o
[ 50%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/accelerate/conv.cpp.o
[ 51%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/accelerate/matmul.cpp.o
[ 52%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/accelerate/primitives.cpp.o
[ 53%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/accelerate/reduce.cpp.o
[ 54%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/accelerate/softmax.cpp.o
[ 55%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/allocator.cpp.o
[ 56%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/conv.cpp.o
[ 58%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/copy.cpp.o
[ 59%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/device.cpp.o
[ 60%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/fft.cpp.o
[ 61%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/indexing.cpp.o
[ 62%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/matmul.cpp.o
[ 63%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/metal.cpp.o
[ 65%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/primitives.cpp.o
[ 66%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/scan.cpp.o
[ 67%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/softmax.cpp.o
[ 68%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/sort.cpp.o
[ 69%] Building CXX object CMakeFiles/mlx.dir/mlx/backend/metal/reduce.cpp.o
[ 70%] Linking CXX static library libmlx.a
[ 70%] Built target mlx
[ 73%] Building CXX object examples/cpp/CMakeFiles/tutorial.dir/tutorial.cpp.o
[ 73%] Building CXX object tests/CMakeFiles/tests.dir/allocator_tests.cpp.o
[ 74%] Building CXX object tests/CMakeFiles/tests.dir/tests.cpp.o
[ 75%] Building CXX object examples/cpp/CMakeFiles/linear_regression.dir/linear_regression.cpp.o
[ 76%] Building CXX object tests/CMakeFiles/tests.dir/blas_tests.cpp.o
[ 77%] Building CXX object tests/CMakeFiles/tests.dir/autograd_tests.cpp.o
[ 79%] Building CXX object examples/cpp/CMakeFiles/logistic_regression.dir/logistic_regression.cpp.o
[ 80%] Building CXX object tests/CMakeFiles/tests.dir/array_tests.cpp.o
[ 81%] Building CXX object tests/CMakeFiles/tests.dir/arg_reduce_tests.cpp.o
[ 82%] Building CXX object tests/CMakeFiles/tests.dir/creations_tests.cpp.o
clangclang: : clangwarning: : argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]warning:
argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]clang
: clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]nd-line-argument]warning:
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 83%] Building CXX object tests/CMakeFiles/tests.dir/device_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 84%] Linking CXX executable linear_regression
[ 86%] Building CXX object tests/CMakeFiles/tests.dir/eval_tests.cpp.o
[ 87%] Building CXX object tests/CMakeFiles/tests.dir/fft_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 88%] Linking CXX executable tutorial
[ 89%] Linking CXX executable logistic_regression
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 90%] Building CXX object tests/CMakeFiles/tests.dir/graph_optimize_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 91%] Building CXX object tests/CMakeFiles/tests.dir/load_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 93%] Building CXX object tests/CMakeFiles/tests.dir/ops_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 94%] Building CXX object tests/CMakeFiles/tests.dir/random_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 95%] Building CXX object tests/CMakeFiles/tests.dir/utils_tests.cpp.o
[ 96%] Building CXX object tests/CMakeFiles/tests.dir/scheduler_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 97%] Building CXX object tests/CMakeFiles/tests.dir/vmap_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 98%] Building CXX object tests/CMakeFiles/tests.dir/metal_tests.cpp.o
clang: warning: argument unused during compilation: '-mfloat-abi=softfp' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[ 98%] Built target tutorial
[ 98%] Built target linear_regression
[ 98%] Built target logistic_regression
[100%] Linking CXX executable tests
[100%] Built target tests
√ isakatraore@Affinis in ~/code/applePlatforms/mlx/build

I just updated to HEAD and building the C++ library from source worked without problem.
This is fixed for me.


where can i get the typical performance benchmark data of MSDK?

I want to have one whole picture about the MediaSDK, where can i get the performance data?

Reference numbers may be found on Media Delivery solutions https://github.com/intel-innersource/containers.docker.gpu.media.intel-media-delivery/blob/master/doc/performance.rst


Indicator bar on second tier nav is confusing

This was brought up during an internal review of our redesigned Living Atlas website- Active page and hover have the same blue bar so can be confusing (in this example, I’m on the Home page and hovering over Benefits. Looks like both pages are active).

Yes, the active indicator is the same as hover. But I should point out that :hover is supposed to also use the blue for it's text color. I'm guessing some of the overrides you've added to the top nav removed this behavior? There should also be a gap between the nav items?
Open to suggestions as to the styling of the hover/focus state, though.

Adding @sanjibpanda and @ChrisMahlke to this conversation, as they are the developers for the site.
Can you please answer @paulcpederson 's question above?

Yes, There should be a gap between the nav items. We can make it happen with a minor fix. I think intentionally we have replaced (replaced with white) default :hover blue color text as it was not looking good on black background.

@TamaraYoder You could change the border color for hover, or add a slight translucent background on hover maybe. I think since this is pretty custom to Living Atlas I'm going to close this issue. Feel free to reopen, though if there is a change in Calcite Web I can make to help with this.


Save best model durning trainning only consider part valset

When save best model during training, it seems only check prec1 acc on part valset, Is this way accurate？

Thanks! We recommend that you run test.py after the training phase. We do validation during the training phase just for checking the experiment. Besides, you can also modify our code for your convenience.


is it possible to train multiple concepts simultaneously now?

I have always processed the dataset and tagged the pictures locally.
Following this guide, I created several concept subfolders with different repetitions under the 'train_data_dir'.

This method worked well in the previous version but not in the latest version.

Hi, it's still possible for train multiple concepts but just need more work, because colab aren't compatible with the latest changes, but not using --dataset_config means we will facing folder naming scheme again.
Instead of editing markdown, you can edit dataset_config.toml created in 5.3. Dataset Config cell and add nesting for dataset and dataset.subset
for example this is my dataset_config.toml : https://huggingface.co/Linaqruf/namazu/blob/main/namazu_locon_db_config/dataset_config.toml
[[datasets]]
resolution = 512
min_bucket_reso = 256
max_bucket_reso = 1024
caption_dropout_rate = 0
caption_tag_dropout_rate = 0
caption_dropout_every_n_epochs = 0
flip_aug = false
color_aug = false

  [[datasets.subsets]]
  image_dir = "/content/LoRA/train_data/concept_1"
  class_tokens = "mksks  style"
  num_repeats = 10

  [[datasets.subsets]]
  is_reg = true
  image_dir = "/content/LoRA/reg_data"
  class_tokens = " style"
  num_repeats = 1

[general]
enable_bucket = true
caption_extension = ".txt"
shuffle_caption = true
keep_tokens = 0
bucket_reso_steps = 64
bucket_no_upscale = false

now i want to add new dataset folder, you can create new subset by copying above config, and it will gonna be like this
  [[datasets.subsets]]
  image_dir = "/content/LoRA/train_data/concept_1"
  class_tokens = "mksks  style"
  num_repeats = 10

# this is new dataset subset folder
  [[datasets.subsets]]
  image_dir = "/content/LoRA/train_data/concept_12"
  class_tokens = "sls frog"
  num_repeats = 10

  [[datasets.subsets]]
  is_reg = true
  image_dir = "/content/LoRA/reg_data"
  class_tokens = " style"
  num_repeats = 1

For further information, you can read this guide.
With this new update you can also train on different resolution on each dataset subset, or whether you want to use --random_crop, not --enable_bucket for certain dataset, or anything. More flexible. But just not familiar for colab.
I hope you understand

It worked! Thanks for your reply.


fix: In FluentEditForm FluentTextField With And Without Lable re not aligned and are not in the same line

🐛 Bug Report
Problem with Fluent Text Field convention with Attribute Label and without Attribute Label next to each other in FluentEditForm
In this case, the labels are not aligned and are not in the same line
💻 Repro or Code Sample

🤔 Expected Behavior
place FluentTextField with Attribute Label next to each other in one line in FluentEditForm
😯 Current Behavior
They do not line up next to each other in FluentEditForm

💁 Possible Solution
🔦 Context
Create Form With FluentEditForm
🌍 Your Environment
FluentUi : 4.10.2
OS Name: Windows
OS Version: 10.0.19045
OS Platform: Windows
RID: win-x64
DotNet 8.0.10 X64
Browser : Chrome Version 130.0.6723.59 (Official Build) (64-bit)
Editor : Visual Studio 2022 v17.10.5 X64

In line with the Fluent Design specs, a label should be placed above a control (https://fluent2.microsoft.design/components/web/react/label/usage#layout)
As you have not posted code, I can't see if you are using the FluentInputs's Label parameter or a separate label. If you want them the line up horizontally, separate them and put them in a div with a flex layout.


"L" and "Y" case sensitivity

Not sure if this will come up or not, but with user input I expect that it might. Do we also want to allow "l" and "y"?

This can certainly be done, but my own bias is to keep it upper case partially because 'l' and '1' are just too similar, but whatever.... "be liberal in what you accept'

That's what I was thinking too. I'm good to leave it as is for now...can deal with it if it comes up.


Adding additional functionalities to profiling tool

This PR ports remaining functionalities required for profiling. In this we are reading job, stage and task level metrics and storing them as dataframes for analysis and qualification.
This doesn't address the memory issue if we are parsing more event logs(~100+).
Signed-off-by: Niranjan Artal<EMAIL_ADDRESS>

build


Admin navbar mobile UI Fixed

Screenshot for reference: https://prnt.sc/jkmNs2QuH0-L

@prateek-webkul
Thanks, this is working fine. Please find the screenshot Here


Updated doc for prometheus/prometheus#649 docker image refactoring PR

Everything is said in the title ;)
Signed-off-by: Steve Durrheimer<EMAIL_ADDRESS>

LGTM but can't merge. @juliusv?


Is there a preference for memory order (C or F) in tabmat?

Followup to https://github.com/Quantco/glum/issues/838. In particular, I'd like to avoid any unnecessary copies when creating a
data_continuous = tabmat.DenseMatrix(data[:, continuous_mask], column_names=column_names)

Tabmat has supports both, so no copies will be made when creating the matrices or doing sandwich and matvec operations. I don't know the performance implications, though. C layout feels more natural for columnar data and matvec, but that's just a hunch.


Should meta be a frozen object

This probably doesn't matter, but if the meta object is an ordinary object, user code could add or remove properties from it. Since it is contextual to the module I don't think this would have any adverse effects.. Perhaps this is something that will be decided by the host in HostFinalizeImportMeta?

Yeah, it's a fair point. We discussed this in committee and tentatively decided against it. I should update the readme with the reasoning. Briefly:

There's no real problem with allowing it to be mutated because it's local to the module; it's not shared by anyone, unless you explicitly pass it around.
Freezing would preclude module -> module transpilers from inserting a few lines at the top of each module adding additional import.meta properties. E.g. if in a year HTML adds a few extra properties, you could write a transpiler that adds them for you when targeting older browsers.

I hadn't thought about the transpiler use-case, that's pretty compelling. Those are two good reasons to keep it unfrozen, I think. Thanks for the explanation!


Downgrade ubuntu to 22.04

refer to https://github.com/actions/runner-images/issues/10636

Breaking changes
Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.

Target date
This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.

OpenShift CLI 	latest available 	- 	Removed from the Ubuntu 24.04 image due to maintenance reasons.

In our tests, we are using oc command which is provided by Ubuntu image. The oc command is not available on Ubuntu 24.04. Currently, there is no problem in this repository because the change has not been rolled out in this area yet. However, it could be impacted eventually after January 17th. I noticed that this issue has already affected https://github.com/stolostron/maestro/pull/20

/assign @qiujian16


Ensure appropriate granularity of tests

Discussion with @travs:
In some cases, we have a single test that verifies an entire class of behavior.  For example, in the evidence quality tests that we just added, we verify wholesale that every fact has a doi or url.  This means that in the event that there is a failure, the user will have to interactively determine where exactly the failure is- the test won't reveal that information.
We should review all of the tests at some point and make sure they are appropriately granular for the sake of making debugging easier.  One way to do this would be to use generating tests:
http://nose.readthedocs.org/en/latest/writing_tests.html#test-generators

This task needs to be broken down into a list of which tests need to be decomposed and how.

It's hard to do this as one self-contained task. Developers should keep in mind how to write good tests that explain themselves, but that's ongoing.


Identity requests Approval for every transaction after cookie expires

I originally posted this in /frontend, but it was the wrong place. We're having an issue on Safari desktop with approvalRequired on the React web app we're building. I understand that Identity needs to request access again 1 week after login, but we are finding that even after approval is given, and the cookie is updated, Identity continues to request access for every transaction thereafter. i.e.:
Given that I'm using Safari
And I logged in 1 week ago with access level 4
When I attempt to buy a coin
Identity requires me to Approve transaction
And when I Approve transaction, then it is successful
But when I attempt another transaction
Then Identity asks for approval again
Despite the fact that the seed-hex-key in Cookies was correctly updated to last another week (i.e. now to expire 2 weeks from when I originally logged in)
We'd appreciate if you could look into this or provide some insight.

I'd love to help figure this out. First, I'm wondering about what your local setup looks like. Are you running a local copy of Identity? If not, are you using localhost to develop your app? Is this reproducible on a real domain like myapp.com and identity.bitclout.com? I've seen lots of weird behavior when developing Identity locally.

Thanks maebeam. I'm using identity.bitclout.com and a firebase hosted web-app, and that's where we noticed the issue. I also ran a local copy of Identity and I get the same behaviour.

Would you be willing to share the URL of the firebase app so I can play with it?

Of course, will send it to you privately :)


Moved runjob helper functions from __init__.py to utils.py

Looks reasonable - have you been able to test it?

Sorry for my ignorance but how do you test this? I thought we can only merge this and redeploy the sandbox and see if anything blows up.

Looks reasonable - have you been able to test it?

Sorry for my ignorance but how do you test this? I thought we can only merge this and redeploy the sandbox and see if anything blows up.

Should be sufficient to set up a new (no existing DB) instance of Nautobot with nautobot-app-firewall-models installed/enabled and confirm that it starts up, migrates, and runs successfully.

Looks reasonable - have you been able to test it?

Sorry for my ignorance but how do you test this? I thought we can only merge this and redeploy the sandbox and see if anything blows up.

Should be sufficient to set up a new (no existing DB) instance of Nautobot with nautobot-app-firewall-models installed/enabled and confirm that it starts up, migrates, and runs successfully.

Tested and started up successfully👍


refactor: make sequence bounded with max value

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
as title
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@fengjiachun PTAL


Empty Messages

There's no validation on the message input, therefore you can send an empty message.
This also seems to lock up the client so the user can no longer send a message until they refresh the page.

Insufficient testing, will revert commit and re-assess.


Suggestion for stitching library

Opencv looks promising and this tutorial seems close to the actual goals (as far as I understand them). The library has python bindings. I might try out the tutorial later this weekend, but let me know if you have other plans for the project, so I won't attempt an already solved problem.

That OpenCV Stitcher-class lookgs good. I might start writing Stitcher-class before the weekend, but I don't expect to finish it this week. My idea for the first version was to be able to produce a watchable panorama video out of two 10s clips from both cameras. Let me know if you need video material. My broad idea was to stitch frames together one by one and produce a new video out of a bunch of panorama images. I could not find many examples of video-stitching, but it might be doable also.
I saved these resources during research related to the video stitching:
https://www.pyimagesearch.com/2016/01/25/real-time-panorama-and-image-stitching-with-opencv/
https://towardsdatascience.com/image-panorama-stitching-with-opencv-2402bde6b46c
https://github.com/krutikabapat/Video-Panorama
https://kushalvyas.github.io/stitching.html
https://www.pyimagesearch.com/2018/12/17/image-stitching-with-opencv-and-python/
http://datahacker.rs/005-how-to-create-a-panorama-image-using-opencv-with-python/


Support localization

We need an option to localize the graph.
The only place where this can be done is in the D3-lib. This has to be done through Plottable.js (if that is possible).
https://github.com/mbostock/d3/wiki/Localization

@tleguijt Looks like Plottable has localization support since 1.14.0
Are you able to do what you need if you switch to this version of Plottable or later?
https://github.com/palantir/plottable/releases/tag/v1.14.0


Requirements Error

https://pypi.org:443 "GET /simple/perfkitbenchmarker-requires-python-311/ HTTP/1.1" 404 13
Status code 404 not in (200, 203, 300, 301, 308)
Could not fetch URL https://pypi.org/simple/perfkitbenchmarker-requires-python-311/: 404 Client Error: Not Found for url: https://pypi.org/simple/perfkitbenchmarker-requires-python-311/ - skipping
Skipping link: not a file: https://pypi.org/simple/perfkitbenchmarker-requires-python-311/
Given no hashes to check 0 links for project 'perfkitbenchmarker-requires-python-311': discarding no candidates
ERROR: Ignored the following versions that require a different python version: 0.24 Requires-Python >=3.10; 0.24rc2 Requires-Python >=3.10
ERROR: Could not find a version that satisfies the requirement PerfkitBenchmarker_requires_Python_311 (from versions: none)
ERROR: No matching distribution found for PerfkitBenchmarker_requires_Python_311
I have the Python
Python 3.9.6 and pip 24.1.2
Is there any incompatibility?

PerfKitBenchmarker requires 3.11+ and is tested on Python 3.11. You can try updating python.


Medbay has no way to tell what chemicals are in a patient

Description
Chemicals have small overdose thresholds, and when medbay cannot tell what chemicals are in someone, overdoses can happen, especially if two different medics are trying to treat one person.
Having to remember what chemicals are in someone, and guess how many have been metabolised adds unnecessary complexity.

true

Just draw blood with a syringe, put the blood into a beaker and then put the beaker into a ChemMaster to check what's in the blood stream:

me when doctors communicate and not just all inject bicar at the same time

Just draw blood with a syringe, put the blood into a beaker and then put the beaker into a ChemMaster to check what's in the blood stream:  (This is after injecting myself with a space medipen and doing what I described above)

Imagine being a doctor, taking a blood sample of a patient, then passing it to chemistry for them to pour it into a beaker, put in the chemmaster or chemdispenser and relay it back to you, to not even know the numbers of chemicals in the patient - you have to extrapolate by looking at the total volume of blood in the patient, and then the size of the sample.

What I'm hearing is the ChemMaster should have Print
Also maybe medkits should come with pre-written sticker notes you can slap on the patient about the chem you gave them

bloodstream analyser.

Just don't put bicaridine in one patient's mouth with the whole medical department?

Putting ability to scan chems on health analyzer is not balanced.

I suppose when they make the sleepers this issue will be resolved.

Putting ability to scan chems on health analyzer is not balanced.

a lot of ss13 builds have it
a lot of have that ability roundstart
what if we make health analyzer upgrades in some of technologies

Every day we get closer and closer to just putting sleepers back in lol.

scanning chems is either suggested in a way that makes it so out of the way that no one will bother to do it, or likely too late in the round to be relevant to gameplay. Someone needs to make a design choice here...

This is the case for a lot of techs tbh.
Science just unlocks things too slowly. But again, this is an issue with ALL researches, not this feature in particular.
And overall this is fine atm. Scanning chems is not critical and this follows design choices with other departments.

Sec has advanced lasers, but you rarely if ever see the tech come into play due to being out of the way and the sec-lathe being in the armory most of the time.
Robotics depends on salvage, but nothing suffers if they can't make any borgs.
In the same way, getting borgs for a specific department requires a lot of effort and is rarely seen, but those departments don't NEED borgs to work.
Cloning...

Either way lank mentioned making this a seperate item from health analyzer was okay, it really isnt powerful enough to matter where the heck you get it from but at least it would be in the game

How about just adding charts to the beds? Or something similar which could be updated with what was injected? Also makes sense RP-wise I guess

How about just adding charts to the beds? Or something similar which could be updated with what was injected? Also makes sense RP-wise I guess

Patient charts would be amazing!


Build fail after merging new page

After merging #4, which had new images, the build is failing to push the new content:

[vite]: Rollup failed to resolve import "/sydfjords/whales/whale-480w.webp" from "/home/runner/work/sydfjords/sydfjords/src/components/WhaleWatching.vue".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
✓ 30 modules transformed.
✓ built in 650ms
error during build:
Error: [vite]: Rollup failed to resolve import "/sydfjords/whales/whale-480w.webp" from "/home/runner/work/sydfjords/sydfjords/src/components/WhaleWatching.vue".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
at viteWarn (file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/vite@4.4.5/node_modules/vite/dist/node/chunks/dep-46921e22.js:48069:27)
at onRollupWarning (file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/vite@4.4.5/node_modules/vite/dist/node/chunks/dep-46921e22.js:48101:9)
at onwarn (file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/vite@4.4.5/node_modules/vite/dist/node/chunks/dep-46921e22.js:47829:13)
at file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/rollup@3.28.0/node_modules/rollup/dist/es/shared/node-entry.js:24152:13
at Object.logger [as onLog] (file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/rollup@3.28.0/node_modules/rollup/dist/es/shared/node-entry.js:25825:9)
at ModuleLoader.handleInvalidResolvedId (file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/rollup@3.28.0/node_modules/rollup/dist/es/shared/node-entry.js:24738:26)
at file:///home/runner/work/sydfjords/sydfjords/node_modules/.pnpm/rollup@3.28.0/node_modules/rollup/dist/es/shared/node-entry.js:24698:26

Digging through the docs suggest I need to include the assetsInclude option.

Transforming asset URLs so they don't include an absolute path fixes part of it, but now icons and the "hero" images from the home page and Colwdvatn don't work.


Search for keybinding by description

Please describe the problem you're trying to solve
You need to find the keybinding of a specific action.
E.g., you want to go to the downloads dir, but you can't remember / don't know it's "gd".
Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
In the "help (~)" screen, press "f" to filter the list of keybindings.
Additional context

This will help beginners like me to familiarize themselves with yazi.
It is a time-tested workflow to use natural language to describe your need.

In VS Code, you can "F1" or "Ctrl+Shift+P" to open the command palette.
In Google Doc/Sheet/Slides, "Alt+/" searches commands.
In MS Office, "Alt Q" searches commands.

Related: #1153

When you press "~" to get the helpscreen, you only get keybindings, the keybindings at the left, command in middle and description at right. Even your plugins keybindings show up. You can always search for "downloads" using "/" there, to get to "gd".

When you press "~" to get the helpscreen, you only get keybindings, the keybindings at the left, command in middle and description at right. Even your plugins keybindings show up. You can always search for "downloads" using "/" there, to get to "gd".

Thank you for mentioning "/"! In conclusion, the feature I ask for already exists. Closing the issue now. ;-)


Diff/ratio of geds params with AUX params

This PR will enable the possibility to express a parameter for geds (and spms - not tested atm) as a difference or ratio with respect to the same parameter recorded in one of any of the AUX channels (eg. PULS01ANA).
The activation can be done through the input configuration file:
"geds": {
    "Uncalibrated energy": {
      "parameters": "cuspEmax",
      "event_type": "pulser",
      "plot_structure": "per string",
      "resampled": "no",
      "plot_style": "vs time",
      "AUX_diff": "pulser_aux", // or "AUX_ratio": "pulser_aux" if you want to take the ratio
      "variation": false,
      "time_window": "20S",
      "range": [null, null]
    }
  }

In "AUX_diff" or "AUX_ratio" you have to specify the name of the AUX channel of reference you want to take into account, ie either pulser, pulser_aux, muon or FC_bsln.

Still need to fix:

calculation of diff/ratio wrt AUX channel data in case of more than one parameter
check saving
check append feature

New changes
We save hdf files in output for speeding up the reading of saved data. These files have different keys, each one containing a dataframe of the following type (there is one datetime column; channel IDs are columns' name; values of interest are reported in cells):

The example shows two dataframes: one for the key IsPulser_Baseline, and one for the key IsPulser_Baseline_var.
Config file
Now, the removal of the AUX channel is always done wrt PULS01ANA by default (at least in L200, still need to fix the L60 case).
This means that if you want baseline(geds) / baseline(PULS01ANA) you need to type
    "Baselines in pulser events": {
      "parameters": "baseline",
      "event_type": "pulser",
      "plot_structure": "per string",
      "resampled": "only",
      "plot_style": "vs time",
      "AUX_ratio": true, // !!!
      "time_window": "10T"
    },

If you want baseline(geds) - baseline(PULS01ANA), then type
    "Baselines in pulser events": {
      "parameters": "baseline",
      "event_type": "pulser",
      "plot_structure": "per string",
      "resampled": "only",
      "plot_style": "vs time",
      "AUX_diff": true, // !!!
      "time_window": "10T"
    },

Plotting VS Saving
You're always ended up plotting the parameter with the options specified in the config file. However, you are going to save everything you load/evaluate for generating the plots, even if you don't specify any "AUX_ratio": true or "AUX_diff": true in the config file. That is: if you want to plot the baselines for geds, you are going to load/save PULS01ANA baselines and perform the ratio and difference with geds values and store them in the final hdf file. Why? To have everything we need in one hit, there is no need to re-load everything again. This is particularly useful for when we want to produce output files to be used for the dashboard.
HDF file content
If the AUX channel info were included, you'll save the following keys for a fixed parameter (<param>) and event type (<flag>, eg pulser, FCbsln, muon) in the file l200-p04-phy-geds.hdf (supposing you're inspecting the subsystem of geds):

<flag>_<param>_info = un po' di info che possono tornare utili on the fly

                   Value
subsystem           geds
unit                 ADC
label           cuspEmax
event_type        pulser
lower_lim_var     -0.025
upper_lim_var      0.025
lower_lim_abs       None
upper_lim_abs       None

<flag>_<param> = absolute values
<flag>_<param>_mean = average over the first 10% of data (within the selected time window) of <flag>_<param>
<flag>_<param>_var = % variations of <param> wrt <flag>_<param>_mean
<flag>_<param>_pulser01anaRatio = ratio of absolute values <flag>_<param> with PULS01ANA absolute values
<flag>_<param>_pulser01anaRatio_mean = average over the first 10% of data (within the selected time window) of  <flag>_<param>_pulser01anaRatio
<flag>_<param>_pulser01anaRatio_var =% variations of <flag>_<param>_pulser01anaRatio wrt ``<flag>_<param>_pulser01anaRatio_mean
<flag>_<param>_pulser01anaDiff = difference  of absolute values <flag>_<param> with PULS01ANA absolute values
<flag>_<param>_pulser01anaDiff_mean = average over the first 10% of data (within the selected time window) of <flag>_<param>_pulser01anaDiff
<flag>_<param>_pulser01anaDiff_var = % variations of <flag>_<param>_pulser01anaDiff  wrt <flag>_<param>_pulser01anaDiff_mean

Saving AUX info
Suppose you are inspecting geds data, for which you end up loading some parameters from the aux channel too. Data of the AUX channel are stored in a second HDF file (name: l200-p04-phy-<aux_name>.hdf), with a similar structure of the previous one. Of course now you'll find just keys of the type

<flag>_<param>_info
<flag>_<param>
<flag>_<param>_mean
<flag>_<param>_var


React step 1

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Closing again, need to resolve @babel/helper-builder-react-jsx-experimental dependency.


Help building for Windows with node-gyp

Does anyone have a Solution file which works with the build.gyp file in the Windows branch of node-sqlite3?  Thanks!
Some background:
A month ago, I managed to get node-sqlite3 to build for Windows using the VS Express GUI.  Now I would like to learn how to build with gyp.  So I am starting with a clean copy of the Windows branch of node-sqlite3.
I see that the build.gyp file seems to not quite match up with the node-sqlite3.sln file.  But just for fun, I made a copy of node-sqlite3.sln called build.sln and then tried to "node-gyp build" just for fun.  Actually, quite a bit got built.  But then I got the fatal error on looking for precompiled headers.  (This will be familiar to anyone who has tried to use the node-sqlite3.sln file as-provided; it won't work; see one of my closed issues here.)

See #61.