feat: add python client quickstart

@Mini256 WE can also add a simple desciption in /README.md and /examples/README.md.


[Editor] A pasted FreeText editor was missing when printing/saving

When a FreeText editor is pasted then it hasn't an editorDiv yet when added
to the layer, hence it's empty.
So this patch just move the call to addToAnnotationStorage to ensure we've
what we need.

/botio integrationtest


Remove jest-check.

Summary
Nobody uses it and it is slow. I don't want to keep maintaining it.
Test plan
it's gone.

Current coverage is 87.93% (diff: 100%)

Merging #2086 into master will not change coverage

@@             master      #2086   diff @@
==========================================
  Files            38         38
  Lines          1343       1343
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1181       1181
  Misses          162        162
  Partials          0          0

Powered by Codecov. Last update cd8976e...bb90af9


How to generate only one file bundle.css instead of generating new unique file every time I save changes

Hello! I'm new in programming and now I am building my second project on JS. I am using this plugin to bundle my css files, but when I save changes, this plugin makes new folder called "assets" and put there file like "bundle-ea06de58.css". After next saving changes it makes new file like "bundle-aeb0df5f.css" in folder "assets". I want this plugin to generate only one file "bundle.css" in folder "dist" and  regenerate it after every saving without creating new unique files. I saw that this plugin has options, but I can not understand how to use them. How can I solve my problem?

Hi @markstopkidding, I hope your enjoying programming so far!
In order to change how the css bundle is created you can use the options provided by the plugin, the behavior and data types of the options are outlined in the readme. Since you would like your css bundle file to be called "bundle.css" and have it always generated inside the "dist" folder, here is an example config that does this:
import css from "rollup-plugin-import-css";

export default {
    input: "index.js",
    output: { file: "dist/index.js", format: "esm" },
    plugins: [ css({ output: "bundle.css" }) ]
};

the plugin determines the build folder using the rollup output.file option, in this case the folder is "dist", then in the css plugin options you can specify the output file name, this is where you can set the file name to "bundle.css".
this should create the outcome you are a looking for. I hope this helps. Let me know if you have any further questions.

Thank you very much! Your answer helped me a lot!


Support build output paths (other than the default one)

Hi,
as discussed after submitting a support ticket pgscan supports that the build output of Visual Studio (project.assets.json) is in the directory of the .csproj. For example .\MyProject\obj\project.assets.json.

We have configured other output paths for our Visual Studio projects for example:  .\Output\obj\MyProject\project.assets.json so pgscan doesn't find any packages
It would be awesome if pgscan would search recursively in the directory of the .sln for all project.assets.json and read the project name (here: MyProject) from the project.assets.json. Then it would find the files even if they are in a completely different output path.
If not possible it would help to at least specify a custom path / fallback path where it searches for the project.assets.json in case it wasn't found in the default path.

Hi @eschbachJR,
We've updated pgscan to search recursively from the solution directory for all project.assets.json files. It took a few more changes than expected so we bumped the minor version up to 1.4.0, and aren't ready to publish a stable version just yet.
Would you be willing to test a prerelease build with your configuration? If you're using this as a dotnet tool, you can install v1.4.0-ci.1 by first adding https://proget.inedo.com/nuget/NuGetLibraries/v3/index.json as a nuget package source.
Or, if you'd prefer to just download it as a zip file, you can get it from the Build Artifacts section of this page (use either zip file - one requires .net 4.6.2 and the other requires .net 6.0).
Thanks!
-Greg

Hi @gdivis,
I appreciate your super fast implementation. I tested it with our project and it worked perfectly fine! The SBOM was generated as expected. When can we expect a stable version? Just as a rough idea for our schedule.
Thank you so much.
Jana

Hi @eschbachJR,
We'll release it early next week. Probably Tuesday or Wednesday - now that you've tested it with your data and we've tested it for regressions it shouldn't be a problem.
-Greg


feat: add load older transactions on Nano Contract Details screen

Acceptance Criteria

Add 'Load More' in the footer of transactions list, which triggers the request for older transactions when pressed
Hides the 'Load More' button when the last transaction of the list is the 'initialize'

Loading older transactions
https://github.com/user-attachments/assets/68f99f4e-b8be-4cf2-a02f-63f1268bfa18
The video above shows a list of transactions initialized in the newest transaction only. When the button 'Load More' is pressed a list of older transactions is loaded. The button 'Load More' didn't show after load because the list has reached its end.
Security Checklist

[ ] Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

I'm closing this PR to concentrate only on https://github.com/HathorNetwork/hathor-wallet-mobile/pull/512. I've incorporated all commits of this PR there.


[Modal] 100% coverage for modalManager.js

@leMaik ;)

From time to time, this line isn't covered. I think that I have found the coverage flakiness we were suffering from:

We should only have green build on the v1-beta branch. It's not ok to have a red one from time to time.


how to set this via node init.js?

just tried to give input for init.js  as below but it throws some error
F:\2nd Version - Angular - Examples\Angular_DRY WALL__\angular-drywall-master>node init.js
=====Create admin user=====
username (root) jsuriya
email<EMAIL_ADDRESS>password
=====Setup Mongo DB=====
MongoDB host (localhost) drywall
MongoDB port (27017)
MongoDB database (angular-drywall) Suriya-drywall
MongoDB user Jsuriya
MongoDB password
=====(Optional) Set smtp server credential (to send notification email)=====
smtp username<EMAIL_ADDRESS>Jsuriya
smtp password
smtp server host (smtp.gmail.com) suriyaJaay
error connecting to db, please verify Mongodb setting then try again.
F:\2nd Version - Angular - Examples\Angular_DRY WALL__\angular-drywall-master>
before that did start mongo

You're probably using a different project (one forked from Drywall maybe). We never used Angular in Drywall.


The APPROVAL LETTER is not wrapped with the  component

Describe the bug
The APPROVAL LETTER is not wrapped with the <PrintPreview> component
To Reproduce
Steps to reproduce the behavior:

Go to 'Resource on sidebar'
Click on 'any "all details" button'
Click on 'APPROVAL LETTER button'

Expected behavior
Wrap the APPROVAL LETTER with the  component to provide a better preview experience
Screenshots

Desktop (please complete the following information):

OS: [windows]
Browser [chrome]
Version [131.0.6778.109]

@Jacobjeevan  i would like to work on this

@Jacobjeevan, I’d like to work on this issue.

@modamaan assigning to @Rajasimhareddybolla since he has already made a PR. @modamaan Guide him in making the PR right, since you've already worked with PrintPreview component in previous PRs.

Hi @rithviknishad, @modamaan
Thanks for your quick feedback!

Duplicate Print Button: I understand the issue of the duplicate print button due to the existing PrintPreview component. To resolve this, I've implemented conditional rendering to hide the redundant print button when the PrintPreview component is available.

Button Component: As requested, I’ve switched to using the primary variant of the Button component from the ui directory instead of ButtonV2.

Here’s the updated outcome:

Please let me know if any further changes are required before new PR.

@Rajasimhareddybolla feel free to create a pr for review purpose

@rithviknishad  If @Rajasimhareddybolla is not working on this issue, I would like to take it up


Contribution for Slack Bot

Did my contribution blog post! Let me know if there are any isssues.

LGTM!


Feedback and notes for the Tech Reports and Scheduling Studio Session

[x] 50 minutes might not quite be enough time for Asana tutorial. Maybe 70 minutes? But many students didn't seem to want to work on the chart development more than just an initial example of how it works.
[ ] The tech report thing was cramped. Had to rush the end (started at about 25 after and continued to about 7 after). Last bit was rushed. Not quite enough time for students to look through both reports.
[ ] Need to give structured questions when comparing the two memos.
[ ] Could mention that the challenger disaster also had major communication issues. People knew about o-rings but it didn't get to the management (need to verify).
[x] Many students said the reading quiz is a negative.
[x] We need to create a diagram that dipicts a milestone with tasks and sub-tasks in Asana. This should label each item to correspond with the words used in the book and lecture: tasks, milestones, etc. It isn't clear to all of the students the exact structure that we are trying to get them to setup:

Asana sections = groups of tasks tied to a milestone
Instagantt tasks = tasks that can be done by one person or a super task that is broken up into subtasks that each are associated with one person
Instagantt subtasks = single person level tasks that are group under main task
Last task in group = convert it to a milestone marker to signfiy that that group of tasks is done, e.g. "Report Due".

@nav-go @clayfanatic @swkresie Feel free to edit this list and add more.

I added a file titled 03-planning-scheduling-activity-ASANA-GUIDE.pdf to the EME 185>2019>lecture-studio-materials folder. This pdf contains the content, including screenshots, that is taught during the Asana/Instagantt tutorial including creating milestones in Asana, tasks, and subtasks in instagantt.


Binary Op should accept mixed precision inputs

Loosen the sanity check for binary op
Add support for bf16 when creating constant.

Backends currently assume that op inputs have the same type; this change is a major API change that would break every current backend if mixed types showed up. The current approach is that framewor bridges should add explicit conversions according to framework semantics when a conversion is required.

Understandable. It is kind of hacky, and the PR is more like a showcase of it.

@diyessi Since Node is the basis of everything in ngraph perhaps we should not put validation there. Node should not care what the types of the inputs are but particular ops should care. If we put constructor validation of inputs in Node then we can't ever create a node with dissimilar inputs.

It's a method that a class may call. If your op doesn't want to call it, don't call the methods. Most ops don't call it.

The test in question was already in elementwise_args so it is fine. These changes belong in nnptr. We already have the ability to override ngraph core validation, we just need to use it

Revert the removal of validation. Only fix for constant builder remains

already merged in #3741


⚠ Secret Website 3 has degraded performance

In 22651f4, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2582 ms

Resolved: Secret Website 3 performance has improved in 0d0e316.


Permissions issue for default OUTPUT_DIR

Description

If I remove OUTPUT_DIR=/tmp from my .env file, which results in the default /var/workflow_output being used, I get permissions errors in the DAGs to write to /var/workflow_output.
Reproduction

Make sure local .env file doesn't contain an OUTPUT_DIR variable
just recreate
Attempt to run any DAG that writes to the OUTPUT_DIR.
See error.

I've just run the Stocksnap DAG locally on my machine with the OUTPUT_DIR defaulting to /var/workflow_output without errors. Do you mind trying to do a just build "--no-cache webserver" and trying once more?

 User error, thanks.


Password reset ticket invalidated before use

We've noticed an issue with the password reset flow. The link sent to the user is a one time ticket that enables them to login. It looks like this ticket is deleted as soon as there is a GET request to the verify endpoint. We've seen certain Mail Transport Agents perform checks on links embedded in emails, which will result in a GET request to the endpoint, making use of the one time ticket. By the time the user receives their email, the ticket has already expired.
It looks like this has been encountered in the past for other platforms, in other similar scenarios, such as email clients providing previews of links, so I don't believe the issue is limited to MTA link scanning. Here is an example of a very similar thing being raised for Drupal - https://www.drupal.org/node/2828034
The conclusion made there, which makes sense to me, is that a GET request shouldn't change a resource. So expiring something on a GET isn't respecting the HTTP protocol. Their solution appears to be landing the user on page when they follow the ticket, which has a form that they need to submit, triggering a POST that would then log the user in. Link scanning or previews won't submit the form (or make POST requests) and thus won't expire the ticket.
Is there a way to avoid this problem with Nhost?

Thinking about this issue you should be able to fix it yourself very quickly. You can basically change the email template to make sure the link points to your own application. You have the link and ticket variables available so you can implement this the best way for you. For instance, you could change the template to include the link https://myapp.com/reset-password?redirecTo={link} instead of the default one (which is just {link}. Then in that page you could present the user with a form or just perform the POST automatically with the help of a bit of javascript magic, whatever suits your application. The advantage of this solution is two-fold:

You have full control to do this in any way you want.
Everything remains on brand as opposed to some generic form coming from hasura-auth's domain, which might be off-putting for the user.

Let me know what you think.

Hi David, thanks for getting back to me.
I had the same idea, which I think will hopefully work for us, although it feels like an issue that should be addressed in Nhost for the benefit of other users.
One issue with your exact suggestion, does the template engine come with anything that enables the correct escaping when building URLs? https://myapp.com/reset-password?redirecTo={link} will end up with unescaped question marks etc in the URL.

I can see in the code it doesn't. If I want well formed URLs I can guess I can try and manually build the URL from the finer grained variables

for the benefit of other users

If there is any idea that doesn't introduce too much complexity or that requires changing the semantics of the link we are open to suggestions :)

does the template engine come with anything that enables the correct escaping

if there is anything that needs adding we can do so but I think it might be better to do something like https://myapp.com/reset-password?ticket={ticket} instead. Ticket is the only info you need that you don't already have in your application

Reading along here. I looked for the correct POST method to verify the ticket but wasn't able to find the correct one 😬  Could you please point me in the right direction?

There is no POST method, it's just a GET to BASE_URL/verify?ticket={ticket}

So how should one handle the redirect that is done in the verifyHandler here.
Because redirectTo is required we always redirect from the page where we are doing the GET to the /verify endpoint.
Now I am currently ignoring the redirect by setting redirect: 'manual' in the fetch options, but then I never get any feedback. Not if the verification was successful or when we have an expired tickets, since this info is in the query string of the page we redirect to.
Am I maybe implementing this wrong?

It feels like a verifyEmail method could solve the problem?

Maybe, if someone wants to implement a POST /verify that works similar to GET /verify but returns data instead of doing the redirect we'd be open to PRs.

I did some more research on this and the POST /verify solution doesn't work. To do a POST to the /verify endpoint you need to use a form but that doesn't open a link and, more importantly, doesn't follow any 302 coming as response. This means that you'd need a bit of javascript to emulate the behaviour (do a fetch using the method POST and try to open the link given in the 302), however, this has two issues:

If you are using a webmail solution this will fail due to CORS
If you are using a desktop mail client this will fail as javascript execution will certainly will blocked

So the only real solution is the following:

The email redirects to www.app.com/verify (instead of hasura-auth)
That website has a single button that:
Performs a POST to the subdomain.auth.region.nhost.run/v1/verify
If the POST fails show the error on screen
If the POST returns a 302 follow it

Thanks @ajluker for opening this issue! We were getting complaints from our customers regularly that they are getting the expired token error whenever they try verifying their mails but we could never reproduce this. In case anyone is interested, we implemented the proposed solution from @dbarrosop in nextjs. You can find the route handler here and an example email template here.

We were not able to reproduce this using outlook default settings. But we now have React and Vue examples for the workaround described above thanks to @dbarrosop and @chrtze. We encourage others to test the workaround in this PR and share their feedback on whether it resolves the issue.

For reference, here you can find a blog post about the solution:
https://nhost.io/blog/protect-your-magic-links-from-email-clients
and some example implementations:
https://github.com/nhost/nhost/pull/2590


Link the "arm_night" mode to a custom mode on Eufy security

The Alarm entity in HA has 4 modes by default, and 3 of them (home, away and disabled) are linked to native Eufy security modes.
The fourth on (night) is not accessible by the integration, and it would be great to link this mode (night) to a custom one on Eufy.
Is there a way to add the "night" mode on the entity and to link it to a custom mode on Eufy ?
Thanks

you should use respective services mentioned in README.
https://github.com/fuatakgun/eufy_security#12-station-services

Well, sorry, but I don't understand how that answer helps :)
Indeed, I can make use custom services to have a custom mode activated, but the "night" mode still does not appear in the homebase alarm panel  on HA. Or maybe I don't understand what you mean and how to use the custom services to enable the night mode on the homebase alarm panel on HA ?

home assistant front end card does only support 3 modes, disarm, home and away.
If you want to switch to night mode, which should be a custom mode in eufy app, just call alarm_arm_custom1 or alarm_arm_custom2 or alarm_arm_custom3 service. Find out the correct number :)

Indeed, the card does only support these 3 modes, but the underlying services (and hence the Homekit integration) does support other modes, as the night mode I was refering to ;)
For example, the "manual alarm" integration offers all 4 modes, which are then accessible to Homekit.
Right now, using the alarm_control_panel.alarm_arm_night service on the homebase alarm panel does nothing. I was suggesting that this service might enable a custom mode on Eufy, hence redering it usable on Homekit for example.

Hopefully my last explanation was more clear and helpful :D

There's even a fifth mode on the alarm control panel : arm_vacation. Maybe another custom mode could be liked to this mode too ?

I see but I do not have control on services exposed to HomeKit, we rather agreed this solution here: https://github.com/fuatakgun/eufy_security/issues/112
You can build a custom switch yourself until I finish developing this.

Don't you have control to what alarm_control_panel modes you are using on the Homebase alarm control panel ? Just like we can enable these modes on the "manual alarm" integration ? Am I wrong ?

Here the complete list of states accessible when creating an alarm panel :

armed_custom_bypass
armed_home
armed_away
armed_night
armed_vacation
disarmed
triggered

Right now, only armed_home, armed_away, disarmed and triggered are exposed by your integration.
There's still room to expose the 3 last states ;)

By default configuration, Eufy supports home, away and disarmed. Skipping geofencing and schedule because they are rule sto switch between other modes, rather than being an actual mode.
So, users can create 3 more custom modes and if I understand correctly, you want me to map Night mode to Custom1, right?

Using configuration, we could also have Vacation mapped to Geofencing for example.
Personnally, I'd be using only the night mode, but I guess there's a lot of people that would like to get Eufy modes linked to native states (and native services) instead of relying on dedicated services.

I understand it now, I would prefer to implement to do this by opt in method using configuration rather than enabling it for all by default. Makes sense for you?

I understand it now, I would prefer to implement to do this by opt in method using configuration rather than enabling it for all by default. Makes sense for you?

Totally ! That's even how I imagined this ;)

I might be jumping into conclusion too early because of historical questions and issues. I should break the bias.

I might be jumping into conclusion too early because of historical questions and issues. I should break the bias.

No problem 😉

Coming back here, are you fine to map night and vacation modes to custom1 and custom2 respectively?
Other way around will be too much time consuming for me?

Coming back here, are you fine to map night and vacation modes to custom1 and custom2 respectively?
Other way around will be too much time consuming for me?

That’s fine by me ! So, we forget the settings and opt-in ?

Yes, having settings should be implemented for each base and individual camera systems, which includes lots of changes

OK, no problem 😉

releasing a new version, please get it and update here with your results.

please comment back, resolving for now

Hello ! I just updated, and I may be missing something but the panel didn’t change and I still got only 3 modes available : disabled, home and away. Is there anything I can do to refresh maybe ?

note to myself: be a good housekeeper and inform users how to enable new functionality :) Please enable according to below screenshot.

Ok, that’s better, but it seems the « night » profile has been connected to the Custom2, and Vacation to Custom3, and Custom1 does seem connected to « arm with custom bypass » 😅
Is there any chance you connect the modes the way we talked earlier or is that a deliberated move ?

If it’s deliberated, that’s not an issue, I’ll just copy my « night » profile to custom2 😉

I had to follow a rule and followed alphabetical ordering :)
ByPass -> Custom1
Night -> Custom2
Vacation -> Custom3

Also, another « issue » : when selecting the custom modes, the change is not passed to HomeKit, but is passed using the default modes. When changing the mode from Homekit, the action is passed to HomeAssistant, but there seems to be an acknowledgment missing as it still displays « activating… » instead of the mode selected.

I had to follow a rule and followed alphabetical ordering :)
ByPass -> Custom1
Night -> Custom2
Vacation -> Custom3

Ok, ni problem 😉

Also, another « issue » : when selecting the custom modes, the change is not passed to HomeKit, but is passed using the default modes. When changing the mode from Homekit, the action is passed to HomeAssistant, but there seems to be an acknowledgment missing as it still displays « activating… » instead of the mode selected.

I am not sure how HomeKit integration is fetching custom modes, all I can do is to test locally and it seems to be working inside HA, right?

I had to follow a rule and followed alphabetical ordering :)
ByPass -> Custom1
Night -> Custom2
Vacation -> Custom3

Ok, no problem 😉

Also, another « issue » : when selecting the custom modes, the change is not passed to HomeKit, but is passed using the default modes. When changing the mode from Homekit, the action is passed to HomeAssistant, but there seems to be an acknowledgment missing as it still displays « activating… » instead of the mode selected.

I am not sure how HomeKit integration is fetching custom modes, all I can do is to test locally and it seems to be working inside HA, right?

Also, another « issue » : when selecting the custom modes, the change is not passed to HomeKit, but is passed using the default modes. When changing the mode from Homekit, the action is passed to HomeAssistant, but there seems to be an acknowledgment missing as it still displays « activating… » instead of the mode selected.

I am not sure how HomeKit integration is fetching custom modes, all I can do is to test locally and it seems to be working inside HA, right?

Yup, Homekit apart, it seems OK

Let's revive this, i believe overriding bypass, night and vacation state names with custom ones causing this issue in homekit end.
Given that you have home kit locally, can you change visible custom names in integration options as Bypass, Night and Vacation, and refresh the integration, and let's see how it goes

I just did that and it’s the same, « activating… » instead of acknowledging the Night mode. Just like there was no return from the command when on night mode (as there’s no « bypass » or « vacation » in Homekit I can’t say if it’s the same for other modes 😉)

Got it, sorry not being able to help further. I would create couple of input booleans to control these states through homekit, if i were you.


Nunique dropping NaN values

[ ] Closes #10550
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.


Zig toolchain uses slow-path for string shuffling in a few places

The ABI of the libc++ std::string is complex and hasn't been implemented host-side, so the current guest ABI for std::string uses a simple fallback method. It's probably better to first get the size() and the use something like https://en.cppreference.com/w/cpp/string/basic_string/resize_and_overwrite to initialize it.

I have considered just always allocating the long string variation of libc++ std::string, even when they are smaller.
Implementation details: https://joellaity.com/2020/01/31/string.html
The raw struct:
struct __long {
    size_type __cap_;
    size_type __size_;
    pointer __data_;
};


[bug] reproducible crash

Steps to reproduce

open the app and click on the hamburger menu in the upper right corner
click on Android app
click on the GET IT ON Google Play Button

the google play site should load for ~2 seconds, but then the site (not yet the app) crashes
the screen should now contain the message Oops, failed to connect to DeepL server with a reload button below and a Toast message shows net::ERR_UNKNOWN_URL_SCHEME

Leave the app, e.g. by clicking your home or overview button

the app should now crash

stack trace
Scoop catches the following stack trace:
FATAL EXCEPTION: main
Process: com.example.deeplviewer, PID: 25527
java.lang.NullPointerException: findViewById(R.id.webview) must not be null
	at com.example.deeplviewer.MainActivity.onSaveInstanceState(Unknown Source:17)
	at android.app.Activity.performSaveInstanceState(Activity.java:1496)
	at android.app.Instrumentation.callActivityOnSaveInstanceState(Instrumentation.java:1386)
	at android.app.ActivityThread.callCallActivityOnSaveInstanceState(ActivityThread.java:4762)
	at android.app.ActivityThread.performStopActivityInner(ActivityThread.java:4066)
	at android.app.ActivityThread.handleStopActivity(ActivityThread.java:4125)
	at android.app.ActivityThread.-wrap25(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6548)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:857)

possible cause
the toast message suggests, that the google play site tries to open a URL with an unknown protocol, probably something that tries to open the play store app.
The webview doesn't know how to handle the URL and crashes, deepl crashes because the webview is now null.
Thus the crash may only occur on devices without the Google Play Store (like mine).
Device Info
Model: SHIFT6m
Android: 8.1 without any google services (ShiftOS-L)

Thank you for your detailed report! And sorry for the delay in replying.
The v8.5 update resolves the potential crash by disabling transitions to URLs other than /translator.
https://github.com/sakusaku3939/DeepLAndroid/releases/tag/v8.5
If you find any other bugs, please let me know. ☕


UT : Report not in standard Maven Failsafe

Dear,
With  mvn clean verify -Dskip.unit.tests -s /usr/share/maven/ref/settings-docker.xml
It generate target/failsafe-reports/failsafe-summary.xml.
It seem Maven Failsafe Plugin genetare by default, these files are generated in ${basedir}/target/failsafe-reports/TEST-*.xml.
How could we have test Junit report ?
Bests regards

Done with the rigth maven Pom setup


Support unregister device

connect #249

@ben181231, thanks for your PR! By analyzing the history of the files in this pull request, we identified @rickmak and @cheungpat to be potential reviewers.


Guild::getMembersAttribute() should be removed

The API behind this is being removed very soon. This API library is the only one calling it.

Thanks!


TypeError: LlamaModel.forward() got an unexpected keyword argument 'labels' when using LoRA on Llama 3.2

System Info
Python version: 3.12.3
Platform: Ubuntu 24.04 (WSL2)
peft==0.13.2, accelerate==1.0.1, transformers==4.46.3
Who can help?
No response
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[X] My own task or dataset (give details below)

Reproduction
Code:
import torch
from transformers import AutoModel, BitsAndBytesConfig as BnBConfig, AutoTokenizer, Trainer, TrainingArguments, DataCollatorForLanguageModeling
from peft import LoraConfig, LoraModel, prepare_model_for_kbit_training, get_peft_model
from peft.optimizers import create_loraplus_optimizer
from bitsandbytes.optim import PagedAdamW8bit

quantization_config = BnBConfig(
    load_in_4bit=True,
    bnb_4bit_compute_dtype=torch.bfloat16,
    bnb_4bit_quant_type="nf4",
    bnb_4bit_use_double_quant=True,
)

lora_config = LoraConfig(
    r=8,
    target_modules="all-linear",
    lora_alpha=32,
    task_type="CAUSAL_LM",
    init_lora_weights="loftq"
)

model = AutoModel.from_pretrained("meta-llama/Llama-3.2-1B-instruct", quantization_config=quantization_config,
                                             torch_dtype=torch.bfloat16)
tokenizer = AutoTokenizer.from_pretrained("meta-llama/Llama-3.2-1B-instruct")
tokenizer.pad_token = tokenizer.eos_token
tokenizer.pad_token_id = tokenizer.eos_token_id
model = get_peft_model(model, lora_config)
model = prepare_model_for_kbit_training(model)

tokens = tokenizer("Hello, my dog is cute", return_tensors="pt")
output = model(**tokens)

Error:
Traceback (most recent call last):
  File "/mnt/d/stuff/other/test/main.py", line 46, in <module>
    output = model(**tokens)
             ^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
    return forward_call(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/peft/peft_model.py", line 1644, in forward
    return self.base_model(
           ^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
    return forward_call(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/peft/tuners/tuners_utils.py", line 197, in forward
    return self.model.forward(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hoang/.local/lib/python3.12/site-packages/accelerate/hooks.py", line 170, in new_forward
    output = module._old_forward(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: LlamaModel.forward() got an unexpected keyword argument 'labels'

Expected behavior
The script runs normally without errors.

The error should disappear if you load the model using AutoModelForCausalLM:
model = AutoModelForCausalLM.from_pretrained(...)

@BenjaminBossan Yes, I agree. I believe the error occurs because AutoModel does not include the lm_head layer, which is responsible for converting the model's outputs into logits. This is crucial when labels are provided, as it directly computes the loss during training.

Great, so it sounds like your problem has been resolved. I'll close this issue then, feel free to re-open in case the error did not go away.

It was not my error, but you can close it anyway,  xD

Closing just means that the issue is completed and no further work is needed ;)

Actually, I came across your GitHub profile and just wanted to say how inspiring it is to see someone with such incredible work. It’s rare to stumble upon people who are so deeply involved in AI and making a real difference. It’s truly motivating!
Keep up the amazing work!


LA_Team Submission

Submission from Lukas Mosser and Alfredo de la Fuente for the 2016-ml-contest using XGBoost algorithm to fit the data and predict the facies for test data.

Thank you team! Awesome to see a new submission.


[1.8.9] Server Crash/Lockup upon Login Event & Full Server

Had about 40-50+ Crashes/lock ups from this so far. I had posted this is SpongeForge previously, but that was before looking into it and realizing it came from SpongeCommon.
http://pastebin.com/m0puTEw7
You cannot reproduce this without Sponge. Looks like its triggered off of a ClientConnectionEvent.Login event being cancelled (i.e. this line). Which in turn calls this. Which then goes to close the channel then you end up at awaitUninterruptibly.
If you want to reproduce it, create a ClientConnectionEvent.Login event and have people trying to connect over and over while the server is full.

For those that are also having issues with this, my current "fix" is to always setCancelled(false) to the Login even then kick the user 1 tick later if the server is full.

My gut feeling is that there's a disconnect occurring when it shouldn't be occurring. Currently, vanilla will disconnect players during the player joining the server (through NetHandlerPlayServer::update() when the login state is: NetHandlerLoginServer.LoginState.READY_TO_ACCEPT). It seems like Sponge is trying to disconnect clients far too early, basically during the authentication process, before authentication has completed and before the net handler play server has been ticked.
@Rhonim would it be possible to test for similar setups in 1.10? As currently the code seems to have been ported very well to replicate the issue, but I lack enough players to fill a server to the full server status :).

@gabizou couldn't you just set the player max to zero and try connecting?

@Deamon5550 I still believe that it has to do with the order of events taking place. It's actually really easy to move the login into the tryAccept of NetHandlerLoginServer where the ban lists and server capacity are checked.

@gabizou Currently don't have a 1.10 setup that would be easy to test on unfortunately. I'll see if I can get something set up in the next few days.

Is this still an issue in the latest builds?

1.8.9 is no longer supported.
Re-test with stable-5 and report back if it still occurs. We'll re-open in the event that it does.


module 'tensorflow.python.compiler.tensorrt.utils' has no attribute 'versionTupleToString'

Tensorrt conversion fails on Ubuntu
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): 2.7 binary (via pip)
TensorFlow version (use command below): 2.7
Python version: v2.7.0-rc1-69-gc256c071bb2 2.7.0
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 11.5
GPU model and memory:  Geforce RTX 2060 Super

Describe the current behavior
The tensorrt conversion fails when the installed version 7.2.3 is higher than the linked version 7.2.2, because the python code in the logger statements is wrong.
Describe the expected behavior
Tensorrt conversion is expected to succeed.
Contributing

Do you want to contribute a PR? (yes/no): no
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
Not needed here, just look at trt_convert.py:229ff - the function trt_utils.versionTupleToString is called multiple times but is not defined, there is only trt_utils._version_tuple_to_string. The logger only gets called when there is a version mismatch.  A simple
versionTupleToString = _version_tuple_to_string

in utils.py will solve it.
File trt_convert.py:229ff:
  def raise_trt_version_deprecated(version_type, trt_version):
    assert version_type in [
        "linked", "loaded"
    ], ("Incorrect value received for version_type: %s. Accepted: ['linked', "
        "'loaded']") % version_type

    logging.error(
        "The {version_type} version of TensorRT: `{trt_version}` has now "
        "been removed. Please upgrade to TensorRT 7 or more recent.".format(
            version_type=version_type,
            trt_version=trt_utils.versionTupleToString(trt_version)))

    raise RuntimeError("Incompatible %s TensorRT versions" % version_type)

  if not trt_utils.is_linked_tensorrt_version_greater_equal(7, 0, 0):
    raise_trt_version_deprecated("linked", linked_version)

  if not trt_utils.is_loaded_tensorrt_version_greater_equal(7, 0, 0):
    raise_trt_version_deprecated("loaded", loaded_version)

  if (loaded_version[0] != linked_version[0] or
      not trt_utils.is_loaded_tensorrt_version_greater_equal(*linked_version)):
    logging.error(
        "Loaded TensorRT %s but linked TensorFlow against TensorRT %s. A few "
        "requirements must be met:\n"
        "\t-It is required to use the same major version of TensorRT during "
        "compilation and runtime.\n"
        "\t-TensorRT does not support forward compatibility. The loaded "
        "version has to be equal or more recent than the linked version.",
        trt_utils.versionTupleToString(loaded_version),
        trt_utils.versionTupleToString(linked_version))
    raise RuntimeError("Incompatible TensorRT major version")

  elif loaded_version != linked_version:
    logging.info(
        "Loaded TensorRT %s and linked TensorFlow against TensorRT %s. This is "
        "supported because TensorRT minor/patch upgrades are backward "
        "compatible.", trt_utils.versionTupleToString(loaded_version),
        trt_utils.versionTupleToString(linked_version))

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

Did you try with Tensorrt version 7.2.2, also check the compatibility and limitations of Tensorrt 7.2.2 here.

@sachinprasadhs - I didn't check w/t 7.2.2, but if you look at the code above, you see that the function trt_utils.versionTupleToString is only being called if the runtime version is different than the linked version. The problem is, that this function doesn't exist, adding it to utils.py will solve the issue. The code says, it should be working with the same major version and any equal or larger minor version in the runtime. Which it did for me when I made the quick fix described above.

@sachinprasadhs, @sanjoy  - do you have any update on this? Could you please acknowledge that this is a bug and will get fixed. It's basically a blocker when you want to upgrade to tf 2.7 and you support tensorrt.

is this fixed in tf2.8?

@sachinprasadhs, @sanjoy  - do you have any update on this?

it was fixed in r2.8 and 2.8.0

utils._version_tuple_to_string was renamed to utils.version_tuple_to_string
trt_convert.py uses trt_utils.version_tuple_to_string instead of trt_utils.versionTupleToString.

As mentioned by @apivovarov , It was. fixed in TF 2.8, you can find the source code below.
https://github.com/tensorflow/tensorflow/blob/v2.8.0/tensorflow/python/compiler/tensorrt/trt_convert.py#L261-L262
Here is the fix which resolved the issue. https://github.com/tensorflow/tensorflow/commit/b523f96d480fd6783aa16c1ce55419a6e4cd9cc6

Cherrypicks will be usually done when there is any security vulnerability, in this case you can use Tensorflow 2.8, since the fix is already available and Tensorflow 2.9 release is around the corner as well.

Thanks @sachinprasadhs!


[Bug] [connector-cdc-mysql] mysql connections and memory of jvm increased abnormally

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
During my use of the mysql-cdc, I discovered a phenomenon. Firstly, I need to explain my environment. My source and target are both MySQL, and I have a batch of inventory data. In the process of fully synchronizing inventory data, there will be no problem if no new data is added to the source database. But if during this period, I have a batch of new data that needs to be inserted into the source library, during which time the JVM memory and MySQL connections will continue to grow. When this process is long enough, it can cause JVM memory to approach the threshold, triggering GC, but GC cannot effectively release memory. At the same time, it will cause excessive consumption of MySql Connection pool.
SeaTunnel Version
seatunnel-2.3.2
SeaTunnel Config
env {
  # You can set SeaTunnel environment configuration here
  job.name = "mysql_test"
  job.mode = "STREAMING"
  checkpoint.interval = 10000
  execution.checkpoint.interval = 10000
  execution.checkpoint.data-uri = "hdfs://localhost:9000/checkpoint"
}

source {
     MySQL-CDC {
        result_table_name = "mysql_cdc_test"
        snapshot.split.size = 3000
        incremental.parallelism = 1
        server-id = "5400"
        username = "xxxx"
        password = "xxxxxxxx"
        database-names = ["xxxxx"]
        table-names = ["xxxxx.test_data"]
        base-url = "jdbc:mysql://192.168.xxx.xxx:xxxx/xxxxx"
    }
}
sink{
    jdbc {
        url = "jdbc:mysql://192.168.xxx.xxx:xxxx/xxxxx"
        driver = "com.mysql.cj.jdbc.Driver"
        user = "xxxx"
        password = "xxxxxx"
        table = "xxxxx"
        primary_keys = ["id"]
	database = "xxxxxxxx"
	batch_size = 3000
	batch_interval_ms = 20
    }
}

Running Command
./bin/seatunnel.sh -c config/v2.mysql_cdc.config

Error Exception
No obvious abnormality

Flink or Spark Version
No response
Java or Scala Version
Jdk11
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@happyboy1024  Is there a solution? I see this problem, too

@happyboy1024 Is there a solution? I see this problem, too
I analyzed the problem and found that it was in the phase of full synchronization history data. Since it is read in fragments, it is necessary to compensate after reading. During fragment compensating, an event listener is registered with BinaryClient, and then the End event is sent based on the offset of binlog. Each listener is associated with a queue to receive data change events, but I found that the current listener was not released after the compensation was completed, resulting in the queue data being unable to be GC. In the subsequent stages of the complete synchronization history, the binlog event will continue to trigger the send End event condition, placing the event in the queue. As for the number of MySQL connections, I found that during sharding reads, each shard enabled will obtain a connection to check the gtid status of MySQL. However, after sharding ends, this connection is not released, resulting in continuous connection growth. I have tried to solve this problem, and I am currently testing to solve it. If possible, I will try to submit a pr

perfect

@happyboy1024  Hi, have you found metaspace outof memory while using the zeta engine? Although I have found this problem, I have not found a good solution

@happyboy1024 Hi, have you found metaspace outof memory while using the zeta engine? Although I have found this problem, I have not found a good solution

Sorry, I haven't found this problem at the moment. However, you can try to analyze this problem from the generation of dynamic classes and the loading of plugin jars. Of course, this is just my personal opinion, a better solution is to submit an issue, describing the problem in detail.


Understanding increase in 1980 recruitment from last year's assessment

Not really an issue, but doing here rather than clogging up Slack.
So here's two figures for recruitment scaled by 2010 recruitment:
2023 assessment:

2024 assessment:

Look at 1980. Much higher (relatively) now than for last year.
Here are the numbers:
Billions of fish, median and 95% intervals:
                    1980 recruitment     2010 recruitment:
2023 assessment:    17.1 (10-34          16.9 (11-30)
2024 assessment:    19.7 (12-37)         15.8 (11-27)

So 1980 has gone up and 2010 has gone down a bit, hence the change in relative values (looking at medians, credible intervals in that table still mostly overlap).
I think this is caused by the penultimate bridging step, adding in the modelled temporal weight-at-age, see the red to blue step here (green then mostly covers blue), from Fig 15. Slight increase (but on log scale) for 1980, slight decrease for 2010.

So these slight changes in rec deviations seem to translate to changes in billions of fish (haven't done the math). Just trying to tease out the changes.

Yep, agree with your assessment.

Great. And such changes aren't "bad", because as Kelli has pointed out, we're moving to better assumptions for weight-at-age.

Closing. Have included the numbers in Section 3.4.2. Presumably the extra 2 billion 1980 recruits will be further explained by the new time-varying weight-at-age and maturity values.

Just updating these numbers for the record, as am editing the related text:
Billions of fish, median and 95% intervals:
                    1980 recruitment     2010 recruitment:
2023 assessment:    17.1 (10-34)          16.9 (11-30)
2024 pre-SRG:         19.7 (12-37)         15.8 (11-27)
2024 post-SRG:       17.7 (10-35)          16.0 (11-29)

So no longer have a change of 2 billion fish born in 1980.


setup GitHub Action

In this PR, I set up basic CI for this project.

fix several compile error
update protobuf generated files with latest version of protoc and rust-protobuf
add GitHub Action for test and benchmark
add cargo fmt check, and format all codes
add Cargo.lock into repo
comment out table as it cannot compile for now

For some tests and benchmarks not passing on GitHub Action:

test_one_key will timeout on CI, so I increased timeout for this test.
skiplist_write will overflow thread 'thread '<unnamed>' panicked at 'assertion failed: offset as usize + size <= self.core.cap', skiplist/src/arena.rs:50:9 still investigating

Running result of the workflows can be found at https://github.com/skyzh/agatedb/pull/1 . Workflow files will take effect in this repo after being merged.

Seems clippy is not run.

Seems clippy is not run.

Yes, as it will produce a lot of errors, I'll open a separate PR to fix clippy warnings and enable clippy.


MintomicTests failing 64-bit atomic tests on Cortex-A15

[1/64] Test "test_load_store_32 x 2"... pass, 122.847 ms
[2/64] Test "test_load_store_32_fail x 2"... pass, 122.611 ms
[3/64] Test "test_load_store_64 x 2"... *** FAIL ***, 910.220 ms
[4/64] Test "test_load_store_64_fail x 2"... pass, 148.853 ms
[5/64] Test "test_return_values_32 x 1"... pass, 11.536 ms
[6/64] Test "test_return_values_64 x 1"... *** FAIL ***, 0.052 ms
[7/64] Test "test_increment_32 x 1"... pass, 787.949 ms
[8/64] Test "test_increment_32 x 2"... pass, 1318.826 ms
[9/64] Test "test_increment_32 x 3"... pass, 1990.425 ms
[10/64] Test "test_increment_32 x 4"... pass, 2663.286 ms
[11/64] Test "test_increment_64 x 1"... *** FAIL ***, 843.509 ms
[12/64] Test "test_increment_64 x 2"... *** FAIL ***, 1356.733 ms
[13/64] Test "test_increment_64 x 3"... *** FAIL ***, 2070.575 ms
[14/64] Test "test_increment_64 x 4"... *** FAIL ***, 2742.229 ms
[15/64] Test "test_add_triangle_32 x 1"... pass, 788.530 ms
[16/64] Test "test_add_triangle_32 x 2"... pass, 1297.612 ms
[17/64] Test "test_add_triangle_32 x 3"... pass, 1967.130 ms
[18/64] Test "test_add_triangle_32 x 4"... pass, 2635.434 ms
[19/64] Test "test_add_triangle_64 x 1"... *** FAIL ***, 849.492 ms
[20/64] Test "test_add_triangle_64 x 2"... *** FAIL ***, 1369.319 ms
[21/64] Test "test_add_triangle_64 x 3"... *** FAIL ***, 2111.927 ms
[22/64] Test "test_add_triangle_64 x 4"... *** FAIL ***, 2768.629 ms
[23/64] Test "test_bitarray_32_128 x 1"... pass, 1710.495 ms
[24/64] Test "test_bitarray_32_128 x 2"... pass, 1386.480 ms
[25/64] Test "test_bitarray_32_128 x 3"... pass, 1426.303 ms
[26/64] Test "test_bitarray_32_128 x 4"... pass, 1409.053 ms
[27/64] Test "test_bitarray_64_128 x 1"... pass, 1841.618 ms
[28/64] Test "test_bitarray_64_128 x 2"... *** FAIL ***, 1449.511 ms
[29/64] Test "test_bitarray_64_128 x 3"... *** FAIL ***, 1467.553 ms
[30/64] Test "test_bitarray_64_128 x 4"... *** FAIL ***, 1471.809 ms
[31/64] Test "test_bitarray_32_32768 x 1"... pass, 1784.692 ms
[32/64] Test "test_bitarray_32_32768 x 2"... pass, 1119.866 ms
[33/64] Test "test_bitarray_32_32768 x 3"... pass, 1122.928 ms
[34/64] Test "test_bitarray_32_32768 x 4"... pass, 1110.437 ms
[35/64] Test "test_bitarray_64_32768 x 1"... pass, 1943.600 ms
[36/64] Test "test_bitarray_64_32768 x 2"... *** FAIL ***, 1200.292 ms
[37/64] Test "test_bitarray_64_32768 x 3"... *** FAIL ***, 1196.412 ms
[38/64] Test "test_bitarray_64_32768 x 4"... *** FAIL ***, 1190.239 ms
[39/64] Test "test_mutex_acq_rel_32 x 1"... pass, 613.998 ms
[40/64] Test "test_mutex_acq_rel_32 x 2"... pass, 1802.519 ms
[41/64] Test "test_mutex_acq_rel_32 x 3"... pass, 3151.955 ms
[42/64] Test "test_mutex_acq_rel_32 x 4"... pass, 5188.046 ms
[43/64] Test "test_mutex_acq_rel_32_fail x 1"... pass, 435.748 ms
[44/64] Test "test_mutex_acq_rel_32_fail x 2"... pass, 1110.851 ms
[45/64] Test "test_mutex_acq_rel_32_fail x 3"... g_sharedValue=14999957 fail (allowed), 1847.388 ms
[46/64] Test "test_mutex_acq_rel_32_fail x 4"... g_sharedValue=19912873 fail (allowed), 3095.298 ms
[47/64] Test "test_mutex_acq_rel_64 x 1"... pass, 699.551 ms
[48/64] Test "test_mutex_acq_rel_64 x 2"... g_sharedValue=8631120 *** FAIL ***, 1397.798 ms
[49/64] Test "test_mutex_acq_rel_64 x 3"... g_sharedValue=12975386 *** FAIL ***, 2101.325 ms
[50/64] Test "test_mutex_acq_rel_64 x 4"... g_sharedValue=17307777 *** FAIL ***, 2814.244 ms
[51/64] Test "test_mutex_acq_rel_64_fail x 1"... pass, 489.877 ms
[52/64] Test "test_mutex_acq_rel_64_fail x 2"... g_sharedValue=7793500 fail (allowed), 790.630 ms
[53/64] Test "test_mutex_acq_rel_64_fail x 3"... g_sharedValue=11673743 fail (allowed), 1188.455 ms
[54/64] Test "test_mutex_acq_rel_64_fail x 4"... g_sharedValue=15624294 fail (allowed), 1607.486 ms
[55/64] Test "test_storeload_32 x 2"... pass, 20418.911 ms
[56/64] Test "test_storeload_32_fail x 2"... fail (allowed), 2516.005 ms
[57/64] Test "test_linkedlist_32 x 1"... pass, 822.158 ms
[58/64] Test "test_linkedlist_32 x 2"... pass, 1290.646 ms
[59/64] Test "test_linkedlist_32 x 3"... pass, 1960.287 ms
[60/64] Test "test_linkedlist_32 x 4"... pass, 2552.706 ms
[61/64] Test "test_linkedlist_64 x 1"... pass, 776.735 ms
[62/64] Test "test_linkedlist_64 x 2"... pass, 1289.945 ms
[63/64] Test "test_linkedlist_64 x 3"... pass, 1940.593 ms
[64/64] Test "test_linkedlist_64 x 4"... pass, 2577.832 ms

----- Summary: -----
Out of the tests required to pass, 34/53 passed.
Out of the tests allowed to fail, 5/11 passed.

These same test failures repro on the NVIDIA Jetson TK1 board.
[1/64] Test "test_load_store_32 x 2"... pass, 78.709 ms
[2/64] Test "test_load_store_32_fail x 2"... pass, 79.337 ms
[3/64] Test "test_load_store_64 x 2"... *** FAIL ***, 769.256 ms
[4/64] Test "test_load_store_64_fail x 2"... pass, 103.981 ms
[5/64] Test "test_return_values_32 x 1"... pass, 9.311 ms
[6/64] Test "test_return_values_64 x 1"... *** FAIL ***, 0.033 ms
[7/64] Test "test_increment_32 x 1"... pass, 443.182 ms
[8/64] Test "test_increment_32 x 2"... pass, 865.064 ms
[9/64] Test "test_increment_32 x 3"... pass, 1267.602 ms
[10/64] Test "test_increment_32 x 4"... pass, 1685.060 ms
[11/64] Test "test_increment_64 x 1"... *** FAIL ***, 479.475 ms
[12/64] Test "test_increment_64 x 2"... *** FAIL ***, 881.312 ms
[13/64] Test "test_increment_64 x 3"... *** FAIL ***, 1282.887 ms
[14/64] Test "test_increment_64 x 4"... *** FAIL ***, 1725.400 ms
[15/64] Test "test_add_triangle_32 x 1"... pass, 440.697 ms
[16/64] Test "test_add_triangle_32 x 2"... pass, 873.684 ms
[17/64] Test "test_add_triangle_32 x 3"... pass, 1280.632 ms
[18/64] Test "test_add_triangle_32 x 4"... pass, 1698.038 ms
[19/64] Test "test_add_triangle_64 x 1"... *** FAIL ***, 493.184 ms
[20/64] Test "test_add_triangle_64 x 2"... *** FAIL ***, 885.253 ms
[21/64] Test "test_add_triangle_64 x 3"... *** FAIL ***, 1285.721 ms
[22/64] Test "test_add_triangle_64 x 4"... *** FAIL ***, 1726.648 ms
[23/64] Test "test_bitarray_32_128 x 1"... pass, 1002.267 ms
[24/64] Test "test_bitarray_32_128 x 2"... pass, 912.122 ms
[25/64] Test "test_bitarray_32_128 x 3"... pass, 882.339 ms
[26/64] Test "test_bitarray_32_128 x 4"... pass, 867.814 ms
[27/64] Test "test_bitarray_64_128 x 1"... pass, 1033.750 ms
[28/64] Test "test_bitarray_64_128 x 2"... *** FAIL ***, 945.004 ms
[29/64] Test "test_bitarray_64_128 x 3"... *** FAIL ***, 905.626 ms
[30/64] Test "test_bitarray_64_128 x 4"... *** FAIL ***, 900.279 ms
[31/64] Test "test_bitarray_32_32768 x 1"... pass, 1074.185 ms
[32/64] Test "test_bitarray_32_32768 x 2"... pass, 703.625 ms
[33/64] Test "test_bitarray_32_32768 x 3"... pass, 530.730 ms
[34/64] Test "test_bitarray_32_32768 x 4"... pass, 443.871 ms
[35/64] Test "test_bitarray_64_32768 x 1"... pass, 1115.395 ms
[36/64] Test "test_bitarray_64_32768 x 2"... *** FAIL ***, 735.406 ms
[37/64] Test "test_bitarray_64_32768 x 3"... *** FAIL ***, 555.333 ms
[38/64] Test "test_bitarray_64_32768 x 4"... *** FAIL ***, 463.146 ms
[39/64] Test "test_mutex_acq_rel_32 x 1"... pass, 372.909 ms
[40/64] Test "test_mutex_acq_rel_32 x 2"... pass, 1307.785 ms
[41/64] Test "test_mutex_acq_rel_32 x 3"... pass, 2562.287 ms
[42/64] Test "test_mutex_acq_rel_32 x 4"... pass, 4362.388 ms
[43/64] Test "test_mutex_acq_rel_32_fail x 1"... pass, 259.713 ms
[44/64] Test "test_mutex_acq_rel_32_fail x 2"... g_sharedValue=9999950 fail (allowed), 585.239 ms
[45/64] Test "test_mutex_acq_rel_32_fail x 3"... g_sharedValue=14999951 fail (allowed), 1289.089 ms
[46/64] Test "test_mutex_acq_rel_32_fail x 4"... g_sharedValue=19999934 fail (allowed), 2285.626 ms
[47/64] Test "test_mutex_acq_rel_64 x 1"... pass, 449.332 ms
[48/64] Test "test_mutex_acq_rel_64 x 2"... g_sharedValue=8763870 *** FAIL ***, 963.968 ms
[49/64] Test "test_mutex_acq_rel_64 x 3"... g_sharedValue=11026744 *** FAIL ***, 1476.256 ms
[50/64] Test "test_mutex_acq_rel_64 x 4"... g_sharedValue=13051720 *** FAIL ***, 2052.289 ms
[51/64] Test "test_mutex_acq_rel_64_fail x 1"... pass, 325.009 ms
[52/64] Test "test_mutex_acq_rel_64_fail x 2"... g_sharedValue=9092264 fail (allowed), 621.822 ms
[53/64] Test "test_mutex_acq_rel_64_fail x 3"... g_sharedValue=12097105 fail (allowed), 985.445 ms
[54/64] Test "test_mutex_acq_rel_64_fail x 4"... g_sharedValue=14615560 fail (allowed), 1357.424 ms
[55/64] Test "test_storeload_32 x 2"... pass, 9487.237 ms
[56/64] Test "test_storeload_32_fail x 2"... fail (allowed), 19.459 ms
[57/64] Test "test_linkedlist_32 x 1"... pass, 486.512 ms
[58/64] Test "test_linkedlist_32 x 2"... pass, 840.659 ms
[59/64] Test "test_linkedlist_32 x 3"... pass, 1215.655 ms
[60/64] Test "test_linkedlist_32 x 4"... pass, 1573.729 ms
[61/64] Test "test_linkedlist_64 x 1"... pass, 504.794 ms
[62/64] Test "test_linkedlist_64 x 2"... pass, 858.529 ms
[63/64] Test "test_linkedlist_64 x 3"... pass, 1241.857 ms
[64/64] Test "test_linkedlist_64 x 4"... pass, 1585.131 ms

----- Summary: -----
Out of the tests required to pass, 34/53 passed.
Out of the tests allowed to fail, 4/11 passed.

Can you post the disassembly for mintomic_gcc.o which resulted in 34/53 tests passed?
$ objdump -d mintomic_gcc.o

And info about the compiler and assembler that generated that .o file.
$ gcc -v
$ as --version

Also, did you modify the project before running it here? Additional compiler or CMake options passed in? How did you make it build if you also had compile issue #2?

Yes, I had to modify it in order to make it build. I used the original "fix" I mentioned in #2. But I'm fairly certain that doing what I did originally will screw up the calling conventions, so it would never work that way anyway.
If I build your master branch with -mthumb, it breaks with:
[  3%] Building C object mintomic/CMakeFiles/Mintomic.dir/mintomic_gcc.c.o
/tmp/ccvG9pbA.s: Assembler messages:
/tmp/ccvG9pbA.s:24: Error: junk at end of line, first unrecognised character is `_'
/tmp/ccvG9pbA.s:37: Error: junk at end of line, first unrecognised character is `_'
/tmp/ccvG9pbA.s:54: Error: junk at end of line, first unrecognised character is `_'
/tmp/ccvG9pbA.s:77: Error: junk at end of line, first unrecognised character is `_'
/tmp/ccvG9pbA.s:95: Error: junk at end of line, first unrecognised character is `_'
/tmp/ccvG9pbA.s:113: Error: junk at end of line, first unrecognised character is `_'
make[2]: *** [mintomic/CMakeFiles/Mintomic.dir/mintomic_gcc.c.o] Error 1
make[1]: *** [mintomic/CMakeFiles/Mintomic.dir/all] Error 2
make: *** [all] Error 2

If I build with -marm, it breaks with:
Linking CXX executable MintomicTests
CMakeFiles/MintomicTests.dir/generated.test_mutex_acq_rel_64.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_mutex_acq_rel_64.cpp:24: undefined reference to `mint_compare_exchange_strong_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_mutex_acq_rel_64.cpp:34: undefined reference to `mint_store_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_mutex_acq_rel_64_fail.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_mutex_acq_rel_64_fail.cpp:24: undefined reference to `mint_compare_exchange_strong_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_mutex_acq_rel_64_fail.cpp:34: undefined reference to `mint_store_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_bitarray_64_128.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_bitarray_64_128.cpp:31: undefined reference to `mint_fetch_or_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_bitarray_64_128.cpp:43: undefined reference to `mint_fetch_and_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_increment_64.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_increment_64.cpp:14: undefined reference to `mint_fetch_add_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_bitarray_64_32768.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_bitarray_64_32768.cpp:31: undefined reference to `mint_fetch_or_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_bitarray_64_32768.cpp:43: undefined reference to `mint_fetch_and_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_add_triangle_64.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_add_triangle_64.cpp:14: undefined reference to `mint_fetch_add_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_load_store_64.cpp.o: In function `threadFunc':
/home/snoonan/Development/mintomic/tests/generated.test_load_store_64.cpp:62: undefined reference to `mint_store_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_load_store_64.cpp:77: undefined reference to `mint_load_64_relaxed'
CMakeFiles/MintomicTests.dir/generated.test_return_values_64.cpp.o: In function `test_return_values_64(int)':
/home/snoonan/Development/mintomic/tests/generated.test_return_values_64.cpp:17: undefined reference to `mint_compare_exchange_strong_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_return_values_64.cpp:24: undefined reference to `mint_fetch_add_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_return_values_64.cpp:30: undefined reference to `mint_fetch_and_64_relaxed'
/home/snoonan/Development/mintomic/tests/generated.test_return_values_64.cpp:36: undefined reference to `mint_fetch_or_64_relaxed'
collect2: error: ld returned 1 exit status
make[2]: *** [MintomicTests] Error 1
make[1]: *** [CMakeFiles/MintomicTests.dir/all] Error 2
make: *** [all] Error 2

So before the tests can even be run with any confidence, the build failure needs to be correctly addressed. My original fix in #2 (killing the underscores) makes the linker happy with -marm, but leaves -mthumb broken, and the tests fail to execute correctly on the -marm build anyway.

OK, so with your original fix in #2, and building with -marm, you get the 34/53 result shown here. Can you post the disassembly of mintomic_gcc.o in that case? You should be able to find it somewhere in your build folder.
$ objdump -d mintomic_gcc.o

Also, how exactly do you pass -marm and -mthumb to the build? Do you pass them on the cmake command line somehow? Pass them to make? Or modify BuildSettings.cmake beforehand?

I added it to the release build flags in BuildSettings.cmake, and ran cmake with -DCMAKE_BUILD_TYPE=Release.
 GCC 4.9.2 uses the EABI, while "Apple LLVM 6.0" in Xcode 6.1 still uses the old ABI. I verified it by inspecting the assembly. The assembly I wrote in mintomic_gcc.c only works with the old ABI. That's the root cause of this issue.
One safe fix would be to check for ARM_EABI in mintomic_gcc.c, and provide alternative implementations for those functions that adhere to the newer EABI. For example, mint_store_64_relaxed would expect its second argument in r2 and r3 instead of r1 and r2.
(However, that still leaves the question of why you had to remove the underscores in issue #2. I'm not sure about that. Yesterday, I tried building Mintomic on Debian x64 using a GCC 4.9.2 cross-compiler for armv7-a, and IIRC it accepted it OK. I'll have to make sure I did that right.)
I like your idea of putting the assembly in the header using inline functions, but you've used the "%H0" operand which not all compilers support. "Apple LLVM 4.1" definitely did not support it. I haven't tried 6.0 yet. Will give it a try later.

Hi tycho, Mintomic is nearing the end of its life. I've basically moved all the atomic C code to Turf: https://github.com/preshing/turf/tree/master/turf/c
Note, though, that native ARM support is currently disabled in Turf (it falls back to C++11 atomics). I'll re-enable it after a couple of issues get sorted out. (Contributions welcome :))


Add integration tests

Operations with data
Description
Added tests for find_element, search_sorted_lower and usort
Checklist

[x] Integration tests added.

These test will be used to benchmark hints and compare the rust hints implementation vs the python interpreted ones, so it would be nice to have a way to iterate over the tests, just like we are doing with the other integration tests. For this you can check math_integration_tests.cairo, memory_integration_tests.cairo and math_cmp_and_pow_integration_tests.cairo

Codecov Report

Merging #362 (732a899) into main (0883829) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #362   +/-   ##
=======================================
  Coverage   97.83%   97.84%
=======================================
  Files          44       44
  Lines       11697    11701    +4
=======================================
+ Hits        11444    11449    +5
+ Misses        253      252    -1

Impacted Files
Coverage Δ

tests/cairo_run_test.rs
98.29% <100.00%> (+0.06%)
:arrow_up:

src/vm/hints/math_utils.rs
99.51% <0.00%> (+0.08%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Contribute Glowroot 0.14-compliant Helm Chart to the Glowroot project

After #16 #18 #19 please consider perhaps contributing the Glowroot helm chart to the Glowroot project for ongoing maintenance.

Yeah, i will talk to trask, maybe he is interested in hosting the helm chart :)


MPRIS position/duration data not being exported properly(?)

Describe the bug
the MPRIS data for the duration of the song, and the position and the remaining is unknown.
To Reproduce
~ teapot$ playerctl metadata --format "{{ position }}"
62
~ teapot$ playerctl metadata --format "{{ position }}"
15
~ teapot$ playerctl metadata --format "{{ position }}"
110
~ teapot$ playerctl metadata --format "{{ position }}"
33
~ teapot$ playerctl metadata --format "{{ position }}"
85
~ teapot$ playerctl metadata --format "{{ position }}"
14
~ teapot$ playerctl metadata --format "{{ position }}"
80
~ teapot$ playerctl metadata --format "{{ duration(position) }}"
0:00

Expected behavior
Metadata about the duration and position is properly shown.
Screenshots
The most useless video ever:
https://user-images.githubusercontent.com/47404953/212978732-523d588a-e246-433d-8e91-2f440c4253d5.mp4
now, it may look like the wmusic dockapp is getting the 'information', but in reality it is guessing it.
Environment

Application version: cc0fde5e9d7f5dd7dace9abe8cd9ea6fe563e7a5
Application features: alsa-backend,media-control

Related: #99
The incorrect "progress" metadata on Linux seems to be the result of these lines of codes:
https://github.com/aome510/spotify-player/blob/cc0fde5e9d7f5dd7dace9abe8cd9ea6fe563e7a5/spotify_player/src/media_control.rs#L26-L39
Not sure if this can be really fixed. I'll need to do some experiments with my old ubuntu laptop, so it may take a while

yeah probably..

UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU, what a great song.


Add compile flag to allow register() for Vulkan

I don't think this compiler option exists, I wasn't able to find anything in the help for it. If it does exist please let me know what the option is.
Currently, when compiling for to SPIR-V for Vulkan, Slang does not support resource declaration using register(X, [Y]) where X is the binding number and Y is the set number. Slang requires the usage of [[vk::binding(X, [Y])]] to specify the binding and set numbers. If [[vk::binding()]] is absent and register() is present, the behavior I've observed is that register() is ignored (with a warning) and resource binding numbers are auto assigned based on declaration order.
The current behavior might unexpected for some users. It's understandable that Slang wants users to be deliberate with the usage of [[vk::binding()]] but it's really inconvenient having to add that decoration to every shader resource in shader source that' shared between Vulkan and other graphics APIs. In cases where the same values are used for register() and [[vk::binding()]]` it's just the same information that's duplicated...and if incorrectly duplicated could lead to some really annoying bugs to track down.
Additionally, for some users it may be non-obvious that having only register() won't do the thing they're expecting and instead binding numbers will be auto assigned. This can easily produce a mismatch between the shader and the graphics API that results in a device lost. For example the snippet below where the register binding numbers are all over the place and auto assignment would just assigns based on declaration order, see spirv-reflect output below.
I think having something like -fvk-allow-register-bindings that allows register(X, [Y]) for binding and set if [[vk::binding(X, [Y])]] isn't present would make shader source sharing much easier and reduce the barrier to entry for on-ramping.
Shader snippet:
ConstantBuffer<SceneParameters> SceneParams : register(b5); // Scene params

// -----------------------------------------------------------------------------
// Ray Tracing Resources
// -----------------------------------------------------------------------------

RaytracingAccelerationStructure  Scene         : register(t0); // Acceleration structure
RWTexture2D<float4>              RenderTarget  : register(u1); // Output texture
RWTexture2D<float4>              AccumTarget   : register(u2); // Accumulation texture
RWStructuredBuffer<uint>         RayGenSamples : register(u3); // Ray generation samples

struct Triangle {
    uint vIdx0;
    uint vIdx1;
    uint vIdx2;
};

StructuredBuffer<Triangle> Triangles[25] : register(t20); // Index buffers
StructuredBuffer<float3>   Positions[25] : register(t45); // Position buffers
StructuredBuffer<float3>   Normals[25]   : register(t70); // Normal buffers

// -----------------------------------------------------------------------------
// PBR Resources
// -----------------------------------------------------------------------------
struct MaterialParameters
{
    float3 baseColor;
    float  roughness;
    float  metallic;
    float  specularReflectance;
    float  ior;
    float3 emissionColor;
};

StructuredBuffer<MaterialParameters> MaterialParams : register(t9); // Material params

Texture2D    IBLEnvironmentMap[100] : register(t100);
SamplerState IBLMapSampler          : register(s10);

SPIRV-Reflect of resources of above shader snippet - binding numbers are auto assigned.
  Descriptor bindings: 10

    Binding 0.0
      set      : 0
      binding  : 0
      type     : VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER (CBV)
      count    : 1
      accessed : true
      name     : SceneParams (SceneParameters_natural)

    Binding 0.1
      set      : 0
      binding  : 1
      type     : VK_DESCRIPTOR_TYPE_ACCELERATION_STRUCTURE_KHR (SRV)
      count    : 1
      accessed : true
      name     : Scene

    Binding 0.2
      set      : 0
      binding  : 2
      type     : VK_DESCRIPTOR_TYPE_STORAGE_IMAGE (UAV)
      count    : 1
      accessed : true
      name     : RenderTarget

    Binding 0.3
      set      : 0
      binding  : 3
      type     : VK_DESCRIPTOR_TYPE_STORAGE_IMAGE (UAV)
      count    : 1
      accessed : true
      name     : AccumTarget

    Binding 0.4
      set      : 0
      binding  : 4
      type     : VK_DESCRIPTOR_TYPE_STORAGE_BUFFER (UAV)
      count    : 1
      accessed : true
      name     : RayGenSamples (RWStructuredBuffer)

    Binding 0.5
      set      : 0
      binding  : 5
      type     : VK_DESCRIPTOR_TYPE_STORAGE_BUFFER (UAV)
      count    : 25
      array    : [25]
      accessed : true
      name     : Triangles (StructuredBuffer)

    Binding 0.7
      set      : 0
      binding  : 7
      type     : VK_DESCRIPTOR_TYPE_STORAGE_BUFFER (UAV)
      count    : 25
      array    : [25]
      accessed : true
      name     : Normals (StructuredBuffer)

    Binding 0.8
      set      : 0
      binding  : 8
      type     : VK_DESCRIPTOR_TYPE_STORAGE_BUFFER (UAV)
      count    : 1
      accessed : true
      name     : MaterialParams (StructuredBuffer)

    Binding 0.9
      set      : 0
      binding  : 9
      type     : VK_DESCRIPTOR_TYPE_SAMPLED_IMAGE (SRV)
      count    : 100
      array    : [100]
      accessed : true
      name     : IBLEnvironmentMap

    Binding 0.10
      set      : 0
      binding  : 10
      type     : VK_DESCRIPTOR_TYPE_SAMPLER (SAMPLER)
      count    : 1
      accessed : true
      name     : IBLMapSampler

I am assuming register syntax means Texture2D<float4> v : register(slot, space); and not Texture2D<float4> v : register(cs_6_0, t0) : register( ps_6_0, t0) : register(gs_5_0, t99); syntax?
(Texture2D<float4> v : register(cs_6_0, t0) : register(ps_6_0, t0) : register(gs_5_0, t99); is 'supported'  but is non functional in DXC)

Yes, that's right: register(slot, space) where slot is come combination of the resource type and register index and space is just spaceN where is is the space index.
I've never used the register(profile, slot) variation. I think I've only seen it in older shader code.


Can't access enum which is nested in a class

I have a class which contains a nested enum but I can't access it..
Class looks like following:
class A {
   public enum Status {
      Active,
      Disabled
   }
}

How to handle that problem? Thanks!

See https://github.com/vfsfitvnm/frida-il2cpp-bridge/issues/219#issuecomment-1237993445 :cheese:


Change the API of grid lines, update the API of axes

Updated the API of grid lines: support the same one, that is used in the new Axis (tickValues and tickTotal);
Eliminate the use of d3-axis: all grids are now rendered using React.
Renamed the orientation property of the axes to position (makes more sense, doesn't overlap with the grid's orientation anymore).
Performed minor updates.

Looked through. Only concerns here are on the API props naming. orientation and position seem quite confusing especially since we're adding a new meaning to orientation and changing all references of orientation to position.

@chrisirhc , done, thanks!


No resources.limits.cpu defined on k6-curl container (starter pod)

Hello,
Version: 0.0.7
In production, when I started a CRD k6, I had an error due to gatekeeper:
Error creating: admission webhook "validation.gatekeeper.sh" denied the request: [container-must-have-limits] container  has no cpu limit.
So the pod *--starter that synchronize injector's pods with curl never started.
I see in associated job that resources was defined like this:
    image: docker-ghcr-proxy.repository.pole-emploi.intra/grafana/operator:latest-starter
    imagePullPolicy: IfNotPresent
    name: k6-curl
    resources:
      limits:
        memory: 200Mi
      requests:
        cpu: 50m
        memory: 2Mi

So no cpu limits defined (sic!)
find in:
pkg/resources/containers/curl.go
        return corev1.Container{
                Name:  "k6-curl",
                Image: image,
                Env:   env,
                Resources: corev1.ResourceRequirements{
                        Requests: corev1.ResourceList{
                                corev1.ResourceCPU:    *resource.NewMilliQuantity(50, resource.DecimalSI),
                                corev1.ResourceMemory: *resource.NewQuantity(2097152, resource.BinarySI),
                        },
                        Limits: corev1.ResourceList{
                                corev1.ResourceMemory: *resource.NewQuantity(209715200, resource.BinarySI),
                        },

I tried to patch myself by adding the new line  (same as request ;-))
make delete
make deploy

but no better...
Can you give me a workaround (I'm not GO developer)?
Best regards
Claude

Hello,
Ok, finally I made a  new local docker image of controller with corrected manager binary (on our local repo) and it's worked fine.
But if you can include this CPU limits line in next release, it's would be fine.
Regards,
Claude

Fixed in https://github.com/grafana/k6-operator/commit/cb4fb354ee87e0dc94658bf87c8598246cb16358
@mikeja67 thanks for spotting this!


metadata missing?

is metadata.rb supposed to be missing?

Yes, I just merged over the kickstarter branches which means these are no longer normal cookbooks. My new cookbooks all use Halite so they are standard Ruby gems and are converted to cookbooks as needed.


Support CAS updates via Thrift

Hello,
Cassandra 2 will soon add new features, i.e. CAS updates. Do you have some time plan to add support in astyanax? Thanx.

+1


icon request (plasma-icons): delete icon

That would be a good idea to add an delete icon to plasma-icons. I thought about using cancel icon as a delete but it might sometimes cause misconception. In addition, almost every inconset has a delete icon :)

available under
import { IconTrash } from "@salutejs/plasma-icons";


How to set divider between each cell？

horizontal and vertical

There is no direct API but you can use fixed size rows and columns with span sizes equal to row and column size to achieve your goal.


Get rid of code related to question sets.

Also did some cleanup to unbreak the menu page and remove some try/catch logic that was hiding errors.


Ionic2: ion-input Issue with label not floating up when type is a number and value is 0

If you have an ion-input element with type="number".  When the model changes to zero, the label does not float up.
I expect the label to float up.
Steps to reproduce:

Click on Calculate button
A zero is populated in the input
The label and the input are on top of each other.

    <form [ngFormModel]="weightForm" novalidate>
      <ion-item>
        <ion-label floating>Weight</ion-label>
        <ion-input type="number" ngControl="weight" [(ngModel)]="weightModel"></ion-input>
      </ion-item>
      <button secondary (click)="calculateWeight()">Calculate</button>
    </form>

Here is the plunker that demonstrates the issue:
http://plnkr.co/edit/TEWz3FtRTH1lWgXbWHNU?p=preview
Cordova CLI: 6.3.1
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.11
Ionic CLI Version: 2.0.0-beta.37
Ionic App Lib Version: 2.0.0-beta.20
ios-deploy version: 1.8.5
ios-sim version: 3.1.1
OS: Mac OS X El Capitan
Node Version: v5.8.0
Xcode version: Xcode 7.3.1 Build version 7D1014

Thanks for the plunker! Note to self/team: the input-has-focus class is not applied when the input is initialized with 0.

Not initialized to zero but set to zero dynamically

Just merge the PR

Hello @keithdmoore thanks for posting a PR 😄 . There is currently a code freeze on master because of all the internal changes going on with the completely new AOT compile, tree shaking, and minifying build process we are working on. Because of this it may be a little while before your PR is merged, but be assured that we will be looking at it.

Ok.  Thanks for letting me know. Cheers!

@keithdmoore thanks a lot for the PR. But it could not longer be merged without conflict so I used your fix.

@manucorporat No problem. Thanks for working this one.  Glad to see it is fixed.  I will be able to remove my hack soon.


COMP-3 field is being read with a value 3 less than expected value

Trying to read a file which has the following
07  IM-LKUP-LM-HH-MM-SS     PIC S9(7)   COMP-3.
The resulting value for each record is coming up with a value thats 3 more than expected.
For instance instead of seeing 131444 - its resulting in 131441
Happens for every single record - all other fields are being parsed correctly - this is the only COMP field.
Added the following option
.option("debug", "hex")
and I see
{131441, 0131441F}
Here is what I see in the file using a hex editor: (ignore double quotes)
"à"
Any idea why this is happening and how to fix it.
Is this because of an unsigned COMP field and the sign value should be ignored but the code is somehow including it in the value?

0131441F is COMP-3 encoded 131441. Looks correct . Why do you expect 131444?

I think we figured out the issue. The file record format is U (undefined)
Does Cobrix support this.
The first field(s9999 Comp-3) defines how many bytes the record is….

Yes, you can use record length expressions, like:
.option("record_format", "F")
.option("record_length_field", "RECORD_LENGTH_FIELD + 10")

more details are in README


NIFI-11231 Stateless NiFi sensitive parameter context support

Summary
NIFI-11231
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 11
[X] JDK 17

Licensing

[X] New dependencies are compatible with the Apache License 2.0 according to the License Policy - N/A
[X] New dependencies are documented in applicable LICENSE and NOTICE files - N/A

Documentation

[X] Documentation formatting appears as expected in rendered files

Hmm.. I'm not sure Parameter Value Provider would work for us since these have to be passed in on runtime and known beforehand. We're going to be supporting a variety of flows stored in Registry. The goal is to run stateless NiFi with any given Registry url, bucket id, flow id, and flow version without any knowledge of what properties/params users have configured in their flows. So those flows that utilize sensitive parameter contexts need to be able to work under any running statless nifi pod/container. We wouldn't be changing the run command or properties files for each flow that's processed with stateless NiFi. Let me chat some more with @Dye357 to see if there's anything I'm missing.

Hi @slambrose, what you describe should be possible with the existing EnvironmentVariableParameterValueProvider.  Let me know if you have any other questions about the setup.


Support vending products that are backed by binaryTargets

This adds support for vending an executable product that consists solely of a binary target that is backed by an artifact bundle. This allows vending binary executables as their own separate package, independently of the plugins that are using them.
rdar://101096803

@swift-ci please smoke test

Some tests need updating due to new diagnostic, but this one surprises me a bit:
<EXPR>:0: error: PluginTests.testLocalAndRemoteToolDependencies : threw error "signalled(4): /home/build-user/swiftpm/.build/x86_64-unknown-linux-gnu/debug/swift-package --package-path /tmp/Miscellaneous_Plugins_PluginUsingLocalAndRemoteTool.QzzITS/MyLibrary --configuration debug plugin my-plugin output:
    Commands/SwiftPackageTool.swift:1083: Fatal error: no product named RemoteTool

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


docs(gcp): Kubeflow cluster upgrade instructions and revamp of env vars

Part of https://github.com/kubeflow/gcp-blueprints/issues/139
Fixes https://github.com/kubeflow/gcp-blueprints/issues/142
Major changes:

add kubeflow cluster upgrade instructions
revamp env var ${KF_DIR} and ${MGMT_DIR} to a unified format

Please review related pages on https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/

/assign @joeliedtke @chensun @8bitmp3

/hold
allow some time for a thorough review

@8bitmp3 @chensun thank you for so much valuable feedback!
I've addressed most of them, PTAL
I'll leave formatting out of scope, because there's too much, I hope we can fix it programmatically.

If we move forward on this, I would recommend that we approach this like building a linter for Markdown docs. It would also be great to also include a check for terms that should not be used in docs (such as "please"). I have started to look into building a linter in the past, but I haven't had much time to devote to it.
Regarding evaluating Markdown format, it may be interesting to see if we can use the parser in the Goldmark library to detect potential issues. This would require some thought and testing though.

Preview:
https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/delete-cli/
https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/deploy-cli/
https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/deploy-ui/
https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/management-setup/
https://deploy-preview-2372--competent-brattain-de2d6d.netlify.app/docs/gke/deploy/upgrade/

WIP: I haven't finished updating management setup and upgrade docs.

@joeliedtke @8bitmp3 I've cleaned up format using the markdown lint tool and updated all env var usages.
PTAL again, thank you so much!

/lgtm
I'll follow up with a PR to define the environment variables in each doc.

Thanks
/unhold


Update sbt-izumi to 0.0.91

Updates io.7mind.izumi.sbt:sbt-izumi from 0.0.89 to 0.0.91.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.0.89).
You might want to review and update them manually.
build.sbt
project/Deps.sc

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.7mind.izumi.sbt", artifactId = "sbt-izumi" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #327.


colorize not working when tty is not present

This is the case when you run capistrano using jenkins. Still I would like to see colors on the outputs. This is broken on sshkit and downgrading to 1.3.0 fixed it.
Is this the expected behaviour? If so is there a way to enable color output with stdout.tty? = false ?
Thanks!

To any future readers who, like me, stumbled here via a google search:
You can now enable coloured Jenkins output for Capistrano tasks, by setting:
ENV['SSHKIT_COLOR'] = "true"

(As can be seen in the SSHkit code here.) This could either be configured globally, or on a per-job basis.

@tom-lord - comments like yours bolster my faith in humanity. I've been needing a fix for this for months.

@tom-lord @ryderstorm If we could do a better job at documenting this, please feel free contribute a PR and I'll merge it. Thanks!

Locking the issue because we ought all to know how the relationship between a tty and terminal control colorization codes works... Colorization is not magic, it's a feature of a terminal. No terminal, no colours, without forcing the issue.


Re: "Limit the number of Ajax calls that can be reported in every page view, or switch off Ajax reporting."

I haven't seen a way to "disable AJAX reporting". It would be nice if there was a link to instructions.  I assume it refers to dependency tracking, but I haven't seen a way to turn that off either.

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

ID: 93d51fcb-63a2-c622-7df3-27703a171b3a
Version Independent ID: 0e2ed122-08c3-fae2-3b7f-6fde780a9933
Content: Manage pricing and data volume for Azure Application Insights
Content Source: articles/application-insights/app-insights-pricing.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@rothschild86 Under Reduce your data rate there is a link to Limit the number of Ajax calls that can be reported which has instructions for using the following parameter:
// Don't log ajax calls. disableAjaxTracking: boolean,

A nice addition :) Thank you.


SnapshotEnvironmentBinding webhook should not reject updates to existing object

The most recent update to the SnapshotEnvironmentBinding (SEB) webhook causes update of SnapshotEnvironmentBindings to fail, due to SEB update algorithm matching on itself when looking for duplicates.

LGTM @jgwest Thank you

Thanks @Rizwana777!


Ensure test-retry-plugin usages are visible in gradle

The internal gradle api usages of the test-retry-plugin should be visible to gradle, so that api changes are considered carefully.

@marcphilipp I think I forgot to merge that one - Is it still ok to merge to release?

Someone from the build tool team should approve and decide if master or release should be used as base branch.

@wolfs can you decide if this change should go into release or master.

@jonnybbb I'd say the change should go into master, since I don't see any urgency to put it on release and the first RC has already been published from release.


dedup k8s/openshift install manifests

install manifests for k8s and OpenShift are present in both the product docs and in the solution docs.
Solution docs should reference an authoritative version in the product docs.

Will be addressed by the move from this repo into individual product repos.