Unable to activate alerts + must manually restart monitor to register new alerts

My main problem is no matter how restrictive I set my mem limit I cannot get the alert to indicate active on the /alerts page in Prometheus. In the example below you will see I have set my service's mem_limit to 10% where at rest, the service in question uses at least 60% of it's available memory limit, and to be triggered with no timespan. Yet no long how I wait for the alert says (0 active)

      resources:
        limits:
          memory: 1000M
      labels:
        - com.df.notify=true
        - com.df.alertName=memlimit
        - com.df.alertIf=@service_mem_limit:0.1

This is how the alert translates into Prometheus
alert: monitoring_elasticsearch_memlimit
expr:
container_memory_usage_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"}   /
container_spec_memory_limit_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"}   > 0.1
labels:   receiver: system   service: monitoring_elasticsearch annotations:
summary: Memory of the service monitoring_elasticsearch is over 0.1

When I plug the expr into the Prometheus Expression receiver I get no-data. Not even container_memory_usage_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"} seems to produce a result.
Here are the relevant docker-compose instructions
  swarm-listener:
    image: vfarcic/docker-flow-swarm-listener
    networks:
      - proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure
      - DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove
    deploy:
      placement:
        constraints: [node.role == manager]
  monitor:
    image: vfarcic/docker-flow-monitor:${TAG:-latest}
    environment:
      - LISTENER_ADDRESS=swarm-listener
      - GLOBAL_SCRAPE_INTERVAL=10s
    networks:
      - proxy
    deploy:
      placement:
        constraints:
          - node.role == manager
    ports:
      - 9090:9090

It may be worth noting that I have not incorporated the alert-manager as I didn't want to set it up and figured I could test my alert settings before moving on to that step. Am I wrong in assuming I can continue with docker-flow-monitor without alert-manager.
It's also worth noting that I am using proxy as the shared network between docker-flow-monitor, docker-flow-swarm-listener because I am also using docker-flow-proxy in this stack.
It may also be worth noting that I must manually restart the docker-flow-monitor service for new alerts to register in the prometheus web console after spinning up other services that are not docker-flow-monitor I am not sure if that is intended behavior and perhaps this is a sign of something else wrong.
Nothing in the monitor logs seem to indicate anything is amiss either
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Requesting services from Docker Flow Swarm Listener
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Processing: [{"alertFor":"30s","alertIf":"@service_mem_limit:0.8","alertName":"memlimit","distribute":"true","replicas":"1","serviceName":"monitoring_kibana"},{"alertIf":"@service_mem_limit:0.1","alertName":"memlimit","distribute":"true","replicas":"1","serviceName":"monitoring_elasticsearch"},{"distribute":"true","port":"80","replicas":"1","serviceName":"proxy_letsencrypt-companion","servicePath":"/.well-known/acme-challenge"}]
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Writing to alert.rules
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Writing to prometheus.yml
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Starting Docker Flow Monitor
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 Starting Prometheus
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | 2018/03/02 02:50:46 /bin/sh -c prometheus --config.file="/etc/prometheus/prometheus.yml" --storage.tsdb.path="/prometheus" --web.console.libraries="/usr/share/prometheus/console_libraries" --web.console.templates="/usr/share/prometheus/consoles"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.425281311Z caller=main.go:225 msg="Starting Prometheus" version="(version=2.1.0, branch=HEAD, revision=85f23d82a045d103ea7f3c89a91fba4a93e6367a)"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.425401927Z caller=main.go:226 build_context="(go=go1.9.2, user=root@6e784304d3ff, date=20180119-12:01:23)"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.42546681Z caller=main.go:227 host_details="(Linux 4.4.0-1047-aws #56-Ubuntu SMP Sat Jan 6 19:39:06 UTC 2018 x86_64 ba5f63bfc96a (none))"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.425555206Z caller=main.go:228 fd_limits="(soft=1048576, hard=1048576)"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.428645759Z caller=main.go:499 msg="Starting TSDB ..."
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.438652055Z caller=web.go:383 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.443432951Z caller=main.go:509 msg="TSDB started"
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.443526522Z caller=main.go:585 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.444105035Z caller=main.go:486 msg="Server is ready to receive web requests."
proxy_monitor.1.b0gt7nw8bbt2@fences-dev-master1    | level=info ts=2018-03-02T02:50:46.444482222Z caller=manager.go:59 component="scrape manager" msg="Starting scrape manager..."

I am fully at a loss on how to debug this further. Perhaps I have made some mistake along the way or misunderstand what I should be expecting.

Can you execute container_memory_usage_bytes expression and send the output?

When I execute
container_memory_usage_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"} / container_spec_memory_limit_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"} > 0.1

or
container_memory_usage_bytes{container_label_com_docker_swarm_service_name="monitoring_elasticsearch"}

or
container_memory_usage_bytes

I get no data . Something about my deployment must be off.

Here are some additional specs I can find
prometheus --version
prometheus, version 2.1.0 (branch: HEAD, revision: 85f23d82a045d103ea7f3c89a91fba4a93e6367a)
  build user:       root@6e784304d3ff
  build date:       20180119-12:01:23
  go version:       go1.9.2

cat /etc/prometheus/prometheus.yml
global:
  scrape_interval: 10s
rule_files:
- alert.rules

The content of alert.rules looks all in order also.

The problem is in DFSL. It has only the proxy as the address in DF_NOTIFY_CREATE_SERVICE_URL and DF_NOTIFY_REMOVE_SERVICE_URL. You need to add (comma separated) the address of Prometheus as well (DFM). Otherwise, it will never receive a notification about exporters.

OH! I do see what you are saying and have modified my environment variables accordingly.
  swarm-listener:
    ...
    environment:
      - 'DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure,http://monitor:8080/v1/docker-flow-proxy/reconfigure'
      - 'DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove,http://monitor:8080/v1/docker-flow-proxy/remove'

What I had to failed to see was proxy was a reference to the service and not to the overlay network. Because of that confusion, I thought to place DFP, DFSL and DFM on the proxy network was sufficient and that proxy in the URL would talk to them all. I do know that's not how overlay networks work, but clearly, I needed a second set of eyeballs to help.
That being said, it has been several minutes now and my aforementioned issues don't seem to have changed.

I even went so far as to remove DFP from the equation but none of the queries e.g. container_memory_usage_bytes seem to produce any result in the Prometheus dashboard. Even an error would be more insightful to me.

The problem is that you changed the name of the service to monitor but you left the rest of the address intact (http://monitor:8080/v1/docker-flow-proxy/reconfigure). The reconfigure address should be http://monitor:8080/v1/docker-flow-monitor/reconfigure. You can find an example in http://monitor.dockerflow.com/tutorial/ .

 Well, I appreciate your patience with assisting me as this certainly resolves my issue. Much thanks again!

I found some time to revisit this part of my project again hopeful resolving my URL mistake would be the key, but I still find myself with unresponsive alerts and queries that execute to no data
In the example below I keep swarm-listener on a proxy network and a monitor network with DFM sharing the monitor network. But I also tried putting them both on exclusively proxy. In both cases nothing changes.
  swarm-listener:
    image: vfarcic/docker-flow-swarm-listener
    networks:
      - proxy
      - monitor
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - 'DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure,http://monitor:8080/v1/docker-flow-monitor/reconfigure'
      - 'DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove,http://monitor:8080/v1/docker-flow-monitor/remove'
    deploy:
      placement:
        constraints: [node.role == manager]

  monitor:
    image: vfarcic/docker-flow-monitor
    environment:
      - LISTENER_ADDRESS=swarm-listener
      - GLOBAL_SCRAPE_INTERVAL=10s
    networks:
      - monitor
    ports:
      - 9090:9090

I really wish I could provide more substantial info but I have exhausted all possible logs.
Is there an example that uses both DFM and DFP that you know to work that I can experiment with locally?

Please send me the current config of your stacks and I'll try to replicate the problem inside one of my clusters.
P.S. Sorry for not responding earlier. I had too much work on my plate.

Closing due to inactivity.


chore(deps): 1.4 fix CVE-2024-21534

Description
Please explain the changes you made here.
fix version of jsonpath-plus  is now in v10.2.0
Which issue(s) does this PR fix

Fixes #?
https://issues.redhat.com/browse/RHIDP-4440

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/lgtm


Download hex file by default when WebUSB not available.

This was in the spec for changing the flash button, but we accidentally changed the behaviour before merge. In the beta, clicking connect when WebUSB is not available will already download the hex.

Thanks. @microbit-robert please can you drop Lucy a note to explain the change as she'll be revisiting the dialog?


modes/asm/ghashv8-armx.pl: implement 4x aggregate factor.

This improves performance on 64-bit processors by 20-70% depending on processor.

BTW, I'd like to hear an opinion on whether or not commits should be squashed. They represent optimization steps and are nice to have as memory refresher in case code is revisited. And the trouble is that we are talking about only one person's memory.

For the stuff I do, and for what most people do, I prefer to squash.  But I appreciate the memory refresh aspect.  Do whatever seems best at the time.  In hindsight it will be shown to be wrong anyway :)

Ping


Bug: unique flag not implemented

sql.define({
    name: 'foo',
    columns: {
        fooId: { dataType: 'VARCHAR', primaryKey: true },
        bar: { dataType: 'VARCHAR', notNull: true, unique: true }
        }
}).create();

Using pg this generates
CREATE TABLE "foo" ("fooId" VARCHAR PRIMARY KEY, "bar" VARCHAR NOT NULL)
without including the UNIQUE constraint.

I'm also having this issue, I'm just commenting to hope that this issue is bumped.

@pwellner and @KieronWiltshire, version 0.65.0 of node-sql should contain a fix for this issue. Could you post back verifying if 0.65.0 fixes the issue?
thanks

Confirmed, thank you.


Changes nrc/rustfmt to rust-lang-nursery/rustfmt.

In faq.md and community.md, the link points to rust-lang-nursery.
In contribute-bugs.md and contribute-libs.md, the link pointed to nrc.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @aturon (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks!


VAC DETECTED

Hello, this cheat is likely detected from vac for a few reason. It's using many instances of things like WriteProcessMemory, or ReadProcessMemory. Which is obviously going to be detected by vac. I would recommend for anyone using this use Vac bypass. Now i haven't looked much into code specifically but glow can be easily detected by checking directx renderers, and i saw that you had glow.

I wouldn't say it uses that many memory reads or writes as it might be.
But yes, playing with cheats as always a risk, which you are automatically accept when running it.
Also the cheat hs not been VAC detected yet.
Many people tested it and there wasn't a single report of VAC ban.
The problem is that the more popular cheat gets, the higher risk of VAC detection is.
That is the main factor of VAC detection (that's why private cheats are not get detected, no matter how crappy they are).
So if you want to minimise the risk of VAC ban - you should manipulate the code as much as possible to make it more unique.

I wouldn't say it uses that many memory reads or writes as it might be.
But yes, playing with cheats as always a risk, which you are automatically accept when running it.
Also the cheat hs not been VAC detected yet.
Many people tested it and there wasn't a single report of VAC ban.
The problem is that the more popular cheat gets, the higher risk of VAC detection is.
That is the main factor of VAC detection (that's why private cheats are not get detected, no matter how crappy they are).
So if you want to minimise the risk of VAC ban - you should manipulate the code as much as possible to make it more unique.

Hey Blaumaus,
how exactly should I try getting it more unique? Any specific tipps what works / what not?
Does Junk Code do anything ?

Hey Blaumaus,
how exactly should I try getting it more unique? Any specific tipps what works / what not?
Does Junk Code do anything ?

@daniel11609, yes, adding some junk code might help in some cases, but the best you could do is to reimplement all the hacks you are using in some other way, rewrite the menu.
Anyway, you should always at least rename the cheat file and change it's hash sum.

@daniel11609, yes, adding some junk code might help in some cases, but the best you could do is to reimplement all the hacks you are using in some other way, rewrite the menu.
Anyway, you should always at least rename the cheat file and change it's hash sum.


Started working on new plugin remake

Well, time to revive this project!
Fresh has finally implemented the ability for plugins to create routes, so this makes
implementing fresh-seo look less like it's built with duct tape.
In my opinion we should keep the old functionality for backwards compatibility.
Other things to do:

[x] Remove the import from the deno.json and put it in deps.ts (I put it there temporarily)
[x] Implement glob matching in removing routes (see #22 )
[x] Add route options to include option
[x] Remove functionality to create setup in the old style

Oh yeah, I should've created the pull request as a draft but it is what it is.
include and exclude should also be an array of routes and options of those routes.
And yeah, the init process should be removed, but it shouldn't interfere with old setups.

Alright I think it's pretty much done. Anything to add?

lfg! thx for the update, excited to finally have the plugin api implemented


[DMP 2024]:  Extend ZK Medical Billing Platform Web3 components and enable a Decentralized NFT-based voting system frame on ERC-20 blockchain, Farcaster

Ticket Contents
Description
ZK Medical Billing enables:
■Secure medical billing data storage, transparent data movement, authenticity;
■Improving Data Transparency
■Enabling healthcare community by empowering medicare providers in universities to do medical counseling securely, transparently.
A greater and more seamless flow of information within a digital health care infrastructure, created by ZK Medical Billing Platform, encompasses and leverages digital progress and can transform the way medicine and healthcare is delivered and compensated.
We also wish to share the key motivation behind our attempt to learn and use Avail light clients:
Improve Throughput and performance in ZK Medical Billing: Avail light clients required significantly fewer resources (storage and processing power) to operate, making them more accessible to operate in a Mohalla clinic setting.
Strengthen Decentralization in ZK Medical Billing: Avail light clients contribute to a more decentralized and trust-minimized blockchain ecosystem, which is very significant in developing countries.
Improve Security in ZK Medical Billing: Avail light clients enabled us to provide security comparable to full nodes through random data sampling and verification, reducing reliance on other solutions.
Goals & Mid-Point Milestone
Goals

[ ] [Integrate Avail’s Light Client features with zk Medical wallet that seamlessly works across key Ethereum L2 Blockchains including Optimism, Scroll, Polygon ZkEVM and leverages Zero Knowledge Proofs for Crypto-transactions and Identity proofs.]
[ ] [Develop a blockchain token on Optimism, StarkNet Network, Avalanche Network and Cardano for ZK Medical Billing portal. Guide: https://github.com/starknet-edu/starknet-erc20 , https://iohk.io/en/blog/posts/2020/12/08/native-tokens-on-cardano/ , https://docs.optimism.io/builders/app-developers/tutorials/standard-bridge-custom-token]
[ ] [Enable tracing, monitoring and recording of medical invoices in a scalable manner on Optimism and Scroll, and use  Avail for data accessibility layer and Sindri for verification using circom, devops and user security.]
[ ] [Migrate from Python2.7 version to Python 3.12 version for ZK Medical Billing backend. Use nginx as a webserver and Amazon S3, MySQL as a database server. AWS Credits will be provided for this milestone. ]
[ ] [Develop a decentralized twitter application for ZK Medical Billing platform on Optimism blockchain.]
[ ] [ Develop an NFT marketplace for ZK Medical Billing platform on Optimism blockchain.]

Setup/Installation
Android version at https://github.com/seetadev/ZKMedical-Billing/tree/main/zk-medical-billing-tracker (please download tablet.apk).
Run Locally
Clone the project
Go to the project directory: https://github.com/seetadev/ZKMedical-Billing/tree/main/zk-medical-billing-tracker
cd zk-medical-billing-tracker
Install dependencies
npm i -g @ionic/cli
npm i
Start the server
For Browser
ionic serve
Build App
For Android
ionic capacitor add android
ionic capacitor sync android
ionic capacitor open android
For IOS
ionic capacitor add ios
ionic capacitor sync ios
ionic capacitor open ios
Expected Outcome

Complete all the 6 goals listed above to enable pilot of ZK Medical Invoicing solution in 11 Delhi universities supported by D.T.T.E. starting with NSUT.

Make key enhancements on the Python backend for ZK Medical Billing platform to enable DIY approach for billing in government setups.

Launch the blockchain token on Uniswap, Sushiswap and PankCakeSwap for ZK Medical Billing platform portal offerings. Complete the integration of ZK Medical Invoice Manager and Government Invoice dapp with integrations to Optimism, Polygon, zksync, Near, Arbitrum, Filecoin, Solana, Cardano, Tron's BTTC blockchain, Algorand, XDC and StarkNet.

Acceptance Criteria

Launch the ZK Medical Billing blockchain token on CEX-1 and CEX-2 along with Uniswap, Sushiswap and PankCakeSwap for the ZK Medical Billing platform offerings. Complete the integration of Invoice Manager and Government Invoice dapp with integrations to  Optimism, Near, Arbitrum, Filecoin, Polygon, zksync, Solana, Cardano, Tron's BTTC blockchain, Algorand, XDC and StarkNet.

Complete all the 6 goals listed above to enable pilot of invoicing solution in 11 Delhi universities supported by D.T.T.E. starting with NSUT.

Make key enhancements on the Python backend for ZK Medical Billing platform to enable DIY approach for billing in government setups.

Save to multi-cloud feature: We would consider a pilot execution with a database of 100+ invoices provided. Please find the screenshots attached for a workflow which is documented for dropbox on ionic angular. You could use supabase, firebase or AWS S3 and Google Database with ionic react if you wish. Please visit https://drive.google.com/drive/u/2/folders/1ORr1D9dQifuX-fkRux49ZDnu1_u7oAJE .

Implementation Details
We are developing the ZK Medical Billing Tracker app using ionic react. Wish to share the learning resources for bootstrapping the learning effort:
Getting Started: https://ionicframework.com/react
https://www.youtube.com/watch?v=xn-qpnT2n3Q
https://www.youtube.com/watch?v=WugT638KS3Q&list=PLYxzS__5yYQlhvyLXSKhv4oAvl06MInSE
https://www.youtube.com/watch?v=K7ghUiXLef8
https://www.youtube.com/watch?v=-aHBhvkrFlY
https://github.com/ionic-team/ionic-react-conference-app
https://stackblitz.com/edit/ionic-react-demo?file=index.js
We are using SocialCalc under the hood for developing the zk medical billing app developed by Dan Bricklin, inventor of the first spreadsheet, VisiCalc.
We have extended and adapted the web based spreadsheet to be mobile, tablet, desktop and iot devices using the ionic framework.
To learn more about SocialCalc: please refer to the following documentation
https://aosabook.org/en/v1/socialcalc.html
https://aosabook.org/en/posa/from-socialcalc-to-ethercalc.html
https://aosabook.org/en/500L/web-spreadsheet.html
Platform Tools needed:
Computer with Linux, Windows or Mac OS. In case windows, please install git-bash.
Testing Device: Smartphone with Android or ios
Backend: Conda, tornado app server, nginx web server (https://aosabook.org/en/v2/nginx.html), passlib and torando.auth
References on SocialCalc:
SocialCalc for Public Health and Education: Please visit
Guide for using Charting tools by Harvard University's Digital Literacy Project - http://vimeo.com/11886029
Guide for using Charting Tools - http://wiki.laptop.org/go/User:Ndoiron/SocialCalc
SocialCalc for improving social access to data and calculation at Federal Communication Commission (FCC): https://www.purplemotes.net/2009/09/13/universal-social-access-to-data-and-calculation/
Community Publications on SocialCalc
"Collaborating Towards Learning, Using Social Spreadsheets for Health Education and Community Awareness", Aastha Chhabra, Manu Sheel Gupta, Sixth International Conference of MIT’s Learning International Networks Consortium (LINC), MIT, Cambridge, Massachusetts, USA · Jun 16, 2013
"Spreadsheet on Cloud - Framework for Learning and Health Management System", K.S. Preeti, Vijit Singh, Sushant Bhatia, Ekansh Preet Singh, Manu Sheel Gupta, Proceedings of the EuSpRIG Conference 2011 "Spreadsheet Governance - Policy and Practice" ISBN : 978-0-9566256-9-4
"Constructionist Learning using Spreadsheet Based Models on Tablets", Mithil Gupta, Manu Sheel Gupta, Sixth International Conference of MIT’s Learning International Networks Consortium (LINC), MIT, Cambridge, Massachusetts, USA · Jun 16, 2013
"A Synchronized Spreadsheet Framework as an IT solution and its Data Management Issues" Rohit Jain, KS Preeti, Vijit Singh, Shubham Shukla, Sushant Bhatia, Yatharth Bansal, Manu Sheel Gupta, International Conference on Information Technology, Systems and Management, Indian Institute of Management, Kozhikode, India · Dec 17, 2011
"SocialCalc: A Spreadsheet Activity for Computer Supported Collaborative Learning", Manu Sheel Gupta, K.S. Preeti, Vijit Singh, Proceedings of the 2010 Conference on Frontiers in Education: Computer Science and Computer Engineering, FECS 2010, Las Vegas, Nevada, U.S.A., CSREA Press 2010, ISBN 1-60132-143-0, pp. 304-309 URL - http://www.informatik.uni-trier.de/~ley/db/conf/fecs/fecs2010.html
"Implementation of Private Cloud Computing using Integration of JavaScript and Python", K.S. Preeti, Vijit Singh, Manu Sheel Gupta, The Python Papers Monograph, The PyCon Asia Pacific 2010, Singapore Management University Download URL - http://ojs.pythonpapers.org/index.php/tppm/article/view/149/161
SocialCalc project has also been covered in important sections of the following conference papers -
"A March Towards Constructionism based on Storytelling, Gaming and Collaboration", Manu Sheel Gupta, Vijit Singh, Manjot Pahwa, The Fifth International Conference of Learning International Networks Consortium (LINC) 2010, Massachusetts Institute of Technology, Cambridge, Massachusetts, U.S.A.
"Collaborating Towards Learning: Using Web 2.0 for Educational Idea Development", Krittika Adhikary, Manu Sheel Gupta, Ekansh Preet Singh, Swarandeep Singh, The Fifth International Conference of Learning International Networks Consortium (LINC) 2010, Massachusetts Institute of Technology, Cambridge, Massachusetts, U.S.A.
Recent research contribution in SocialCalc: Co-author of the article, "Opinion of students on online education during the Covid 19 pandemic", please visit the paper at https://onlinelibrary.wiley.com/doi/epdf/10.1002/hbe2.240
Mockups/Wireframes
Please visit the 4.5 minute demo to understand the ZK Medical Billing Platform at https://drive.google.com/drive/u/1/folders/1zadM3Ac_KCEi5_x29seu-b6bBK6BkAus
Screenshots for each of the Web3 components bootstrapped in ZK Medical Billing Platform: https://drive.google.com/drive/u/1/folders/1MS_uLsmDUNcdgugJZqOCQFUC7GMqFdOt
ZK Medical Invoice Tracker (MVP): https://invoice-suite.vercel.app/
Demo Video for anonymization and encryption of medical data and dapp on decentralized medical counseling (dapp, security): https://www.youtube.com/watch?v=rJRRlaVQSMY
Demo Video for bulk query, retrieve of medical data & dapp using OP, Eth, Embark, IPFS (dapp, portal): https://www.youtube.com/watch?v=BUiVvhuUdrE
Product Name
ZK Medical Billing Platform for Government Universities
Organisation Name
NSUT in collaboration with C4GT, SEETA, AIC
Domain
Healthcare
Tech Skills Needed
AWS, Chart.js, CI/CD, DevOps, Express.js, Flask, HTML, Ionic, JavaScript, Node.js, Python, React, RESTful APIs, Selenium, Solidity, SQL, TypeScript
Mentor(s)
@seetadev @aspiringsecurity @aspiringdevapps
Manu Sheel Gupta;
Dr. MPS Bhatia;
Deepti Gupta (SAP Appgyer guidance and SAP BTP integrations) for utility government organizations in India.
Category
Beginner Friendly, CI/CD, Database, Delpoyment, Localization, Mobile, Security

Hey @seetadev, I would like to work on this project as part of dmp 2024

Hey @Mentors, I would love to work on this project as part of Code4GovTech 2024. As I am first time contributing in Code4GovTech, please support me, as I am having plenty of questions. Firstly I will need to submit the proposal for this project on unstop, right?

@seetadev @aspiringsecurity @aspiringdevapps I am familiar with the web3 frameworks that is required for the project,whom do i contact for further discussions ?

Weekly Learnings and Updates
Week 1
ERC20 MediToken Contract:

Created an ERC20 MediToken contract.
Deployed the contract on multiple test networks:

OP Sepolia
Arbitrum Sepolia
Polygon Amoy
Sepolia Testnet

Deployment Script:

Developed a deployment script to automate the process of deploying the MediToken contract on the specified test networks.

Test Suite:

Written a comprehensive test suite to ensure the functionality and reliability of the MediToken contract.

Makefile Configuration:

Configured a Makefile to include all necessary commands for building, testing, and deploying the contract, making the development process more streamlined and efficient.

README Documentation:

Created a detailed README file that provides:

Instructions for setting up the development environment.
Steps for deploying the contract on various test networks.
Guidance on running the test suite.
Deployed contract addresses with links to the respective block explorers.

Static Audit Review:

Reviewed the static audit logs of the MediToken contract to ensure it meets security standards and best practices.

Tokenomics Study:

Studied different tokens and their tokenomics to gain insights into industry standards and practices.

Links to Issues and PRs:

Issue: #2
PR: #3

Weekly Goals
Week 1

[ ] Create an ERC20 MediToken contract and deploy on L1 and L2 blockchain test networks.
[ ] Develop a deployment script to automate the process of deploying the MediToken contract on the L1 and L2 test networks.
[ ]  Write  a test suite to ensure the functionality and reliability of the MediToken contract.
[ ] Configure a Makefile for building, testing, and deploying the contract.
[ ] Static Audit Review and Tokenomics Study.

Weekly Goals
Week 2

[ ] Demonstrate the utility of ERC20 MediToken on a key use-case "Decentralize Healthcare systems" as a dapp.
[ ]  Complete the design, implementation of the use-case demonstrating ERC20 MediToken utility.
[ ]  Test and deploy the token gated mechanism in the Decentralize Healthcare system dapp.
[ ] Brainstorm on the set of applications and blockchains where ERC20 MediToken will be utilized effectively and cost efficiently.

Weekly Learnings and Updates
Week 2
Implemented and deployed a decentralized healthcare system DApp utilizing MediToken for token-gated access control.
Token-Gated Access Control:

Implemented different access levels based on the number of MediTokens held by the user:

Users with at least 1 MediToken can register and access the platform.
Users with at least 5 MediTokens can book an appointment with listed verified doctors.
Users with at least 10 MediTokens can book an emergency appointment with listed doctors.

Deployment Script:

Developed deployment scripts using Foundry to automate the deployment of the smart contracts.

ConnectKit Integration:

Integrated ConnectKit for seamless wallet connection.

Lighthouse Storage Integration:

Utilized Lighthouse storage as an IPFS gateway for decentralized storage.

Frontend Deployment:

Deployed the frontend for easy usability testing and interaction with the DApp.
Here's the link to the deployed version: MedETH.

Documentation:

Detailed documentation of the Foundry setup, contract deployment process, and frontend setup.

Deployed Contract Addresses

Sepolia Testnet

UserSide: 0x97e82f8a22793Cc270eE2a25D47006194053504f
DoctorSide: 0xd777F1661e6895B25D70Ff6375A114373ee6590c

OP Sepolia Testnet

UserSide: 0x1E2DBa267514C319E45C5E867f44f42e0f1Cd4F0
DoctorSide: 0x77C5f60D10625Bb80DecA89f5713d01964450aa8

Polygon Amoy Testnet

UserSide: 0x66E1e28A6E6BD3a4c30a53C964e65ADa11Cf9EB8
DoctorSide: 0xB551eE1236593Fe6cB5a679c0962E89d30740FF8

Arbitrum Sepolia Testnet

UserSide: 0x8D2fe41E336EF8a49AaE0FE26c3D346d7618541e
DoctorSide: 0xB6c60435840346C5Ef447bf4A2ECFbB075F45b48

Checklist:

[x] Built a decentralized healthcare system DApp utilizing MediToken for token-gated access control.
[x] Created Solidity deployment scripts for the smart contracts in the Foundry setup.
[x] Developed a comprehensive Makefile for command execution.
[x] Integrated ConnectKit for wallet connection.
[x] Utilized Lighthouse storage as an IPFS gateway.
[x] Deployed the frontend for usability testing.
[x] Documented the Foundry setup, contract deployment process, and frontend setup.


Implementing on Async function to EndPoint(Ajax)

Hi!. Im trying to implement a later.setInterval function, and the function is an async call to API (Ajax). Is there any reestriccion? The thing is that the function is executed just once. I change the api function using a 'console.log' function, and worked properly...any comments?
Regards!!

@evicent It seems like later can work with an async function just fine. The following is a simple example grabbing a random Star Wars character every 5 seconds using later.setInterval
const later = require('later')
const axios = require('axios')

const s = later.parse.text('every 5 seconds')

later.setInterval(async () => {
  const randomIndex = Math.ceil(Math.random() * 20)
  const { data } = await axios.get(`https://swapi.co/api/people/${randomIndex}/`)

  console.log(data)
}, s)

Maybe you can provide a simple example on what isn't working properly for you?


PackageConfiguration: Support matching any revision

Please have a look at the individual commit messages for the details.

@fviernau, after another discussion with @mnonnenmacher we decided to propose this change without hiding it behind a feature toggle. The reason mostly is that any such conventions like requiring a fixed revision could (and probably should) be implemented via CI checks on package configuration changes. That way, we avoid an increasing number of feature toggles being introduced, esp. before have a proper mechanism to share global configuration throughout all of ORT without passing config options everywhere.
So, what do you think @fviernau?


Bug: Rate Limit count should not apply on non-200 requests

Current Behavior
Attempts by users upon failing to make an account (invalid password format, the account already exists) count towards the rate limit, this means that after several tries, they won't be able to make an account for 5 minutes.
Expected Behavior
Only 200 OK Requests should count into the user's rate limit.

actually nvm cannot lol


[Clinical] System is not displaying prescription details as expected

Actual Results
System is not displaying the following details: ARV Change Reason, Interrupting Reason
Expected results
In case of a change of regimen and ARV Type selected is INTERRUPT the format should be: [Drug] [Dose] [Units], [Frequency], [Route]- [Duration] [Duration Units] ([Instructions]), ARV Plan: [ARV Plan], ARV Change Reason: [ARV Change Reason], Interrupting Reason: [Interrupting Reason]
Steps to reproduce
Login to eSaude POC->Clinical->type Dois -> select Paciente Dois -> refer to Prescrições/Regimes tab
Screenshot/Attachment (Optional)

 Display Prescriptions/ Regimens Test Report 2.1.1


[BUG]: Browser tab is not opening

Describe the bug
We are using Browser aptitude, we have installed the olive plugin. In our application, we are creating a local html file, and giving this html file path and trying to open it in browser. For us it is working fine. But on some users machine browser tab is not opening.
Please help us investigate this issue.
Steps to Reproduce
Catherine_ui.main.log
I have the log file. Please have a look.
Olive Helps Version
0.47.4
LDK Version
Latest
Operating System
windows
Code Sample
const FILE_NAME = 'index.html';
const filePath = await filesystem.join([this.filespath, FILE_NAME]);
// The permissions we want to give the file, in octal format
// https://www.linode.com/docs/guides/modify-file-permissions-with-chmod/
const FILE_PERMISSIONS = 0o777;
// The write operations to choose from while writing the file
const { overwrite, append } = filesystem.WriteOperation;
const writeFileParams = {
  data: FILE_CONTENT,
  path: filePath,
  writeMode: FILE_PERMISSIONS,
  writeOperation: overwrite,
};
await filesystem.writeFile(writeFileParams);
console.log('filePath==========', filePath);
//const newTabId = await browser.openWindow('file:///' + this.filespath + '/index.html');
try {
  //const newTabId = await browser.openWindow('file:///' + this.filespath + '/index.html');
  const newTabId = await browser.openTab('file:///' + this.filespath + '/index.html');
  console.log('newTabId============', newTabId);
} catch (error) {
  const newTabId = await browser.openWindow('file:///' + this.filespath + '/index.html');
  console.log('error newTabId=======', error);
}

Additional Context
No response
Code of Conduct

[X] I agree to these terms

It looks like there are no registered browser connections. This could either be that the browser extension is not installed or is turned off. I have attached screen shots from the logs.


[Feature Request] - boot2docker shared host volume for development

@SvenDowideit
As this has been an issue long around for many, I think there is an opportunity to get this solved...
As stated on the corresponding docker-machine issue here, there is a cifs/nfs volume share plugin available. However I have difficulties to get it working on boot2docker and it is not persisted. So this consists in an request to include https://github.com/gondor/docker-volume-netshare into boot2docker natively and make this the standard way (via docs) of sharing volumes on hypervisors (not just virtualbox).
A docker-compose.yaml then just looks something like this:
volumes:
    src:
        driver: nfs
        driver_opts:
            name: <IP_ADDRESS>/flct

What do you think?

xref: https://github.com/docker/docker/pull/20262

:heart: and :watch:  for baking cifs/nfs into boot2docker

cc/ @tianon

we are in different times (roadmap of mobylinux)

Was this issue closed as "Won't fix"?
I'm trying to get this to work per https://github.com/docker/docker/pull/20262 on Mac with boot2docker.
$ docker volume create --name=test --driver=local --opt type=nfs --opt device=<host-ip>:<nfs-share> --opt o="vers=3"
test
$ docker run -it --rm -v test:/test alpine ls -la /test
docker: Error response from daemon: invalid argument.

Mounting the share directly works fine:
mkdir /test
mount -t nfs <host-ip>:<nfs-share> -o vers=3 /test

Since the mount command works fine, but docker complains about invalid argument, the issue does not seem to be with boot2docker, but with docker volume local drive implementation.

Just tested with tmpfs and it works fine. Don't have a Windows share to test with right now.
$ docker volume create --name=tmpfs --driver local --opt type=tmpfs --opt device=tmpfs --opt o=size=100m,uid=1000
tmpfs
$ docker run -it --rm -v tmpfs:/test alpine ls -la /test
total 4
drwxrwxrwt    2 1000     root            40 Jul  6 22:49 .
drwxr-xr-x   25 root     root          4096 Jul  6 22:49 ..

Found an answer to my issue. See https://github.com/docker/docker/pull/20262#issuecomment-230941746


Redis Error - max number of clients reached

This error is popping up in sentry.
I'm not that familiar with redis, will do some research and  investigate :)

Hey @chriswedgwood — that's a good one. Can you link the issue here in Sentry? (Let me know if not, and I'll poke around in the Sentry UI to see if we can get that going.)

Here you go...
https://sentry.io/share/issue/07d9acfe9e0e4cc7bf71051b88d2c894/

@carltongibson  Looking in the redis config:

We have max connections of 50. Our plan doesn't enable us to see connection history graphs so hard to know whats happening. The only thing I can think to do is restart redis. I can query redis sporadically and see if connections are kept over time.
Or maybe we can upgrade redis?

The only thing I can think to do is restart redis.

Route 1. 😄 👍

I can query redis sporadically and see if connections are kept over time.

I can't see why a little app like this need 50 connections. So this might be worth a play. (Just casually)

Restarted redis. CLIENT LIST is currently showing 5 connections
Closing issue.

Thanks @chriswedgwood — it may be there's some slow connection leak somewhere... but... 😀

I'll keep an eye out for it 👍
On Thu, 4 Mar 2021 at 14:44, Carlton Gibson<EMAIL_ADDRESS>wrote:

Thanks @chriswedgwood https://github.com/chriswedgwood — it may be
there's some slow connection leak somewhere... but... 😀
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/django/djangosnippets.org/issues/224#issuecomment-790668052,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJW5M5B6CX3NGHMUNKGGUTTB6MDFANCNFSM4YSC22ZA
.


Maintainer tags on packages

This PR adds tags on all packages (on both all package views and single package pages) to indicate whether a package is authored/maintained by the community or by Pulumi.
This PR is currently using a PR branch from theme for styling - before merge I will merge that PR, and update this PR to use the release branch of theme as usual (https://github.com/pulumi/theme/pull/73).

fixes https://github.com/pulumi/registry/issues/577

Looking good! Just a few styling changes:

Christian brings up the point that the bg colors the tags use on the package page could be mistaken for buttons. For now, let's try reducing the opacity of those bg colors from 10% down to 5% and see if that helps break association.
Can we use Gilroy for the font on the tag itself?
I'm betting there's not a great way to do this, so it's not a huge deal if this is a no-go. But on the package page, can the tags be right-aligned with the right edge of the main container instead of the edge of that rightmost column?


Add Privacy Policy for Google Analytics

Just wanted to bump this from a quick scan I just stumbled upon. I saw you guys are using Google Analytics but don't have a privacy policy for user content. I recommend adding one to comply with recent legislation such as GDPR and CCPA in addition to Google's Terms of Service. I have attached a resource below containing some details on going about this.


The editor has crashed

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode - doesn't crash in safe mode, but it still crashes in normal mode and I do not wish to switch to safe mode for all usage
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom - unreasonable, I cannot read 4600 issues to find this exact crash, but I don't see it on the first page
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages - irrelevant, not looking for a package

Description
Since updating to Atom 1.19.0 (my tenth update), it crashes every time I run it.
Steps to Reproduce

Launch Atom
Press ctrl-comma to open settings
Click Packages

OR simply:

Launch Atom (after doing the above steps once)

Expected behavior: Atom runs and I'm able to browse the packages list
Actual behavior: The deprecated packages never finish loading, and the core app seg faults:

stdout and ~/.atom/nohup.out both say:
/usr/bin/atom: line 130: 19908 Segmentation fault      (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
(node:19908) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 focus listeners added. Use emitter.setMaxListeners() to increase limit
(node:19908) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 blur listeners added. Use emitter.setMaxListeners() to increase limit
Failed to generate minidump.

("Failed to generate minidump." is repeated 1210 times on that line, omitted for brevity.)
Browsing installed packages is kind of important after an update because some old packages might need to be updated, disabled, configured, or removed.
Reproduces how often: 100%
Versions
Atom    : 1.19.0
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0
apm  1.18.2
npm  3.10.10
node 6.9.5 x64
python 2.7.13
git 2.11.0

Ubuntu 17.04
Additional Information
I don't know what else would be useful, but I'll be happy to provide more info upon request.

Since you're not experiencing this in safe mode, some package that you have installed must be contributing to the crash. Could you share your list of installed packages? You might also want to manually try disabling different packages to pinpoint which particular package is causing the issue.

Here's the contents of ~/.atom/packages. I can't disable packages other than by deleting these directories, because that option is on the screen that crashes. Similarly, some of these are already disabled, but I can't check which ones because the screen that would give me that information crashes.
advanced-open-file
ambiance
ambiance-dark-syntax
ambiance-dark-ui
ambiance-pro-ui
api-docs
atom-beautify
atom-html-preview
atom-jq
atom-make
atom-material-numix-syntax
atom-material-syntax
atom-material-ui
atom-runner
atom-sharp
atom-ternjs
atom-ubuntu-dark-ui
atom-yeoman
audio
autocomplete-en-en
autocomplete-haskell
autoupdate-packages
browser-plus
build
build-make
build-tools
build-tools-make
busy
busy-signal
coffee-compile
custom-folds
dark-flat-ui
elastic-tabstops
file-icons
file-types
focus-follows-mouse
git-clone
git-control
git-diff-details
git-gui
git-log
git-plus
git-status
git-time-machine
haskell-ghc-mod
highlight-selected
ide-haskell
ide-haskell-cabal
ide-haskell-repl
imagemin
indent-guide-improved
intentions
irc
json-schema
language-awk
language-diff
language-haskell
language-patch
language-pug
language-sln
language-vala
line-diff-details
linter
linter-coffeelint
linter-jsonlint
linter-pug
linter-python
linter-stylint
linter-ui-default
MagicPython
man
markdown-preview-enhanced
markdown-preview-plus
merge-conflicts
minimap
minimap-codeglance
minimap-git-diff
minimap-split-diff
mixup-dark-syntax
monokai-ubuntu
npm-debug.log
npm-plus
numix-dark-ui
numix-ui
pdf-view
preview
remember-folds
run-command2
script
solarized-dark-bold-syntax
solarized-dark-ui
solarized-light-ui
solarized-one-dark-syntax
solarized-one-light-ui
sourcerer
split-diff
Stylus
term
transpile
tree-view-autoresize
tree-view-git-branch
tree-view-git-status
xmldoc-snippets

You can enable or disable packages by editing ~/.atom/config.cson, which you can access using the command Application: Open your Config. There should be a section called disabledPackages under core, like this:
'*':
  core:
    # ...
    disabledPackages: [
      # ...
    ]

You can disable or enable packages by adding or removing their names from this section.

Thanks, I checked my config.cson and split the disabled packages into a separate list in my previous comment.

@maxbrunsfeld , a binary search of the list revealed that git-gui triggers the crash. I can turn the rest of my packages back on and there's no crash, but whenever git-gui is enabled, the packages tab freezes.
(I removed the full list from the earlier comment to reduce clutter. I'll look for a place to add this to the main issue report as well.)

Thanks so much for that report @HebaruSan. That's really helpful.

I was not able to reproduce this with Atom 1.20.0-beta1 on Windows 7. Also I could not get the git-gui package to activate without throwing this exception https://github.com/andrewrynhard/atom-git-gui/issues/10.

Can confirm this on Windows 8.1 x64 only with Atom 1.19.1 and 1.19.2.
With 1.18 all was OK.
Disabling git-gui helps, thanks @HebaruSan
Crash reports attached
Atom Crashes.zip

I don't have git-gui installed, and am getting:
/usr/bin/atom: line 141: 12388 Segmentation fault      (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
<memory>:1: Invalid color constant '##d3d3d3'
Gtk-Message: 09:01:51.687: (for origin information, set GTK_DEBUG): failed to retrieve property `ChromeGtkFrame::frame-color' of type `GdkColor' from rc file value ""##d3d3d3"" of type `gchararray'


如何进行分区，请大神指点下

如何进行分区，请大神指点下

1、之前无论采取哪种分区模式都无法进行
生产者的分区的分割器
分区选择在多个分区存在的情况下,决定将消息发送到哪个分区.
sarama有多个分割器:
sarama.NewManualPartitioner() //返回一个手动选择分区的分割器,也就是获取msg中指定的partition
sarama.NewRandomPartitioner() //通过随机函数随机获取一个分区号
sarama.NewRoundRobinPartitioner() //环形选择,也就是在所有分区中循环选择一个(徐工)
sarama.NewHashPartitioner() //通过msg中的key生成hash值,选择分区,
徐工 我建议是第3种，刚好均匀分区，目前我已经修改为5个默认分区，到时候可以均匀分配，
参考文献
https://blog.csdn.net/qq_32292967/article/details/78675116
2、servser.properties中需要将默认分区配置修改为你想设置的那个数。
3、测试代码
测试代码
/*

@Author: Rui XuLe
@Date:   2019-07-12 22:40:03
@Last Modified by:   Rui XuLe
@Last Modified time: 2019-07-13 22:05:08
*/
package main

import (
"encoding/json"
"fmt"
"log"
// "math/rand"
"os"
"time"
"github.com/Shopify/sarama"

)
var Address = []string{"IP:9092"}
func main() {
p := syncProducerInit(Address)
sendMeg(p)
}
type MegInfo struct {
Name    string    json:"name"
Meg     string    json:"meg"
TimeMeg time.Time json:"timeTime"
}
//同步消息模式
func syncProducerInit(address []string) (p sarama.SyncProducer) {
config := sarama.NewConfig()
config.Producer.Return.Successes = true
config.Producer.Timeout = 5 * time.Second
config.Producer.Partitioner = sarama.NewRoundRobinPartitioner
//sarama.NewHashPartitioner()
p, err := sarama.NewSyncProducer(address, config)
if err != nil {
log.Printf("sarama.NewSyncProducer err, message=%s \n", err)
return nil
}
return
}
//主要是 消息的发送
func sendMeg(p sarama.SyncProducer) {
defer p.Close()
topic := "test_go_kafka_producer"
m := MegInfo{
Name:    "RUIXULE",
Meg:     "今天是20190720，我在测试gokafka",
TimeMeg: time.Now(),
}
data, _ := json.Marshal(m)
// srcValue := string(data) //"sync: this is ; message. index=%d"
for i := 0; i < 100; i++ {
	value := string(data) // fmt.Sprintf(srcValue)
	msg := &sarama.ProducerMessage{
		//Partition: int32(i),
		//Key:       sarama.StringEncoder(fmt.Sprintf("%d", rand.Intn(10))),
		Timestamp: time.Now(),
		Topic:     topic,
		Value:     sarama.ByteEncoder(value),
	}
	part, offset, err := p.SendMessage(msg)
	if err != nil {
		log.Printf("send message(%s) err=%s \n", value, err)
	} else {
		fmt.Fprintf(os.Stdout, value+"发送成功，partition=%d, offset=%d \n", part, offset)
	}
}

}

By default, the hashPartitionner is used. It use the key of the message to define on which partition the message goes.
If you use roundRobin or random you lose one nice feature of kafka: guarantee of order.
When you use hashPartitionner, you have the guarantee that messages are produced and consumed in the correct order for any given key.
This key is whatever you want.
Example: if the key is the userID, for a given user, every event are ordered.
It might not matter, this totally depend on what you do.
To be honest hashPartionner is fast enough, I don't really see the point of using anything else.
Also a caveate: if you use hashPartitionner but set the key to nil (or just do not define it), the roundRobin partitioner will be used.
As for the partition count, 12 is a good number. It is sufficiently high for most use case and divide evenly in multiples ways ( 2 consumers, 6 partitions each; 3 consumers, 4 partitions each ...).

I formatted the issue to help the reviewers

@2017RXL even that nowadays is easy for use to use an online translator, could you please provide an English description to the problem, so reviewers won't need to use an online translator? this will also help you getting more 👀 as no many people will try to translate the message or don't speak Chinese as apparently @FrancoisPoinsot does 😄


Update transition support

This completely updates the transition_support.bzl file. It now essentially is a 100% copy of the one in here: https://github.com/bazelbuild/rules_apple/blob/master/apple/internal/transition_support.bzl
This is important as Bazel 7 has changed this a lot.
Changes:

Delete old transition_support.bzl
Add rules_apple transition_support.bzl
Add rules_ios specific patches to transition_support.bzl (see the PATCH: comments)
Update existing rules to support this new transition_support
Remove unused transitions from transition_support.bzl that are used in rules_apple but not in rules_ios

With this change + some toolchain updates i have in a follow up i got a target in our project to pass the build


Acceleration is not consistent between iOS and Android

I found iOS and Android acceleration value has different sign, and it seems gravityNormalized option only correct accelerationWithGravity(gm.gx/gm.gy/gm.gz) but not acceleration(gm.x/gm.y/gm.z).
I made a plot for this situation to clarify my idea:

Those two green box shows that the gm.y and gm.z in iOS and Android are negative to each other.
Change line 350 - 355 to following could give consistent value, but I'm not sure I understand this library completely. I would like to make this a PR if you this's a correct fix.
// Normalize gravity
if (_gravityNormalized) {
  snapShot.dm.gx *= _gravityCoefficient;
  snapShot.dm.gy *= _gravityCoefficient;
  snapShot.dm.gz *= _gravityCoefficient;
}
// Change above to:
if (_gravityNormalized) {
  snapShot.dm.gx *= _gravityCoefficient;
  snapShot.dm.gy *= _gravityCoefficient;
  snapShot.dm.gz *= _gravityCoefficient;
  snapShot.dm.x *= _gravityCoefficient;
  snapShot.dm.y *= _gravityCoefficient;
  snapShot.dm.z *= _gravityCoefficient;
}

Yep! you are correct please make the PR and I will merge.
Thanks!
D.

@dorukeker Actually I found that gravityNormalized option can't be set by user at all, it's always true. Will make a PR later 😂

Thanks! I merged the PRs


Add net8.0 as TargetFramework

In my app I have net8.0 as a target frameworks besides the platforms I support. This helps with unit testing, as I can build the app as a dll-file and reference that from my unit test project. I want to unit test viewmodels and other logic and I have everything in the same Maui-project.
My csproj-file
   <TargetFrameworks>net8.0;net8.0-android;net8.0-ios</TargetFrameworks>
   <OutputType Condition="'$(TargetFramework)' != 'net8.0'">Exe</OutputType>

This change adds net8.0 as a TargetFramework, enabling unit testing without having to add #if ANDROID || IOS whenever the IInsights interface is referenced.

Do we need to have all the code in the .NET 8 constructor or will it work with an empty constructor? Do we need the constructor at all? It is not enough to mock the IInsightsProvider interface or even the IInsights interface?

To add .net 8 is a good idea. I asking question about the constructor just to understand your use case.

For me it is important that the IInsights interface exists on all platforms, so I don't have to do  #if ANDROID || IOS everywhere. The implementation of that interface could very well be empty or just a mock, doesn't really matter.
I have a view model with a constructor like:
MyViewModel(IInsights insights, ISomeOtherThing someotherThing) ...

When I unit test this view model, the IInsights interface must exist. I will provide a mock for it in the test anyway so it don't have to have an implementation.
Changing the 'InsightsExtension.UseTinyInsights' to do nothing would work as well, I think.


brew update generates a file for brew cleanup every time

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

$ brew doctor
Your system is ready to brew.
$ brew config
HOMEBREW_VERSION: 1.7.1-250-g2c68176
ORIGIN: https://github.com/Homebrew/brew
HEAD: 2c68176ac21b7c5fd53a2e02617376fac9fc6f4c
Last commit: 6 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 7ece5465d21b3544d5e0ea9b1b90c9e3788b125b
Core tap last commit: 17 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_NO_ANALYTICS_THIS_RUN: 1
CPU: quad-core 64-bit skylake
Homebrew Ruby: 2.3.7 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/bin/ruby
Clang: 9.1 build 902
Git: 2.18.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 10.0.2
macOS: 10.13.6-x86_64
CLT: N/A
Xcode: 9.4.1
XQuartz: N/A

$ brew cleanup
$ brew update
$ brew cleanup
Removing: /usr/local/var/homebrew/locks/update... (0B)

Should brew update be creating that file every time and showing its removal every time brew cleanup is run?
Likely introduced in #4639 @reitermarkus

Should brew update be creating that file every time

Yes.

and showing its removal every time brew cleanup is run?

Debatable, but I don't think it's worth special-casing this just to hide the output.

@reitermarkus The lock file should be either removed by brew update when it's no longer needed or not removed and recreated by brew update.


Hombrew install via basics.sh fails

Currently, there is an issue with the basics.sh script that causes Homebrew (the package manager) to install incorrectly on certain machines. This could be an issue with an out of date install script.
This issue can be bypassed by running basics.sh until the installation of Homebrew fails (which is signified by the error brew is not in path, installing brew via https://brew.sh/ and following the on-screen instructions (making sure to add the script to path) and then finally re-running basics.sh.

updated according to suggestion in the following link: https://brew.sh


Python3 port

Together with the python3 port of nototools
https://github.com/googlefonts/nototools/pull/488
This pull request makes it possible to build the font using Python3.
Using Python2 still works as well, the code works with both.

Can confirm this builds NotoColorEmoji.ttf fine!
As mentioned, currently this depends on this specific nototools branch. Lets push for that to be merged before merging this?

@mike-fabian hey! thanks again for patch. I'll merge and apply the fix-ups myself

Cosimo Lupo<EMAIL_ADDRESS>さんは書きました:

@mike-fabian hey! thanks again for patch. I'll merge and apply the fix-ups myself

Thank you!
--
📧 Mike FABIAN<EMAIL_ADDRESS>睡眠不足はいい仕事の敵だ。

Code looks good, font is being built without a hitch. 👍

Hi! It would help Debian switch their nototools from python2 to python3 if someone would also port https://github.com/googlefonts/robotoslab

@jbicha I wasn't aware that project relies on python2-only code. Can you please open an issue over there pointing to the files that need update? Thanks

@anthrotype Never mind. You're right. It was just a copy-and-paste mistake in the Debian packaging for robotoslab.


Add option to save album to a folder

For example I have set files in channel "test" to be downloaded to X:\test, when an album is found, it will be saved in X:\test\album.

Using the interactive mode you can specify the target folder. I have no plans to add sub folders to the automatic mode, sorry.


Feature Request: Ability to pick commits out to merge directly to main

In my development workflow, I often create commits encompassing refactoring, fixes, and other changes unrelated to new features. It's crucial that these changes are not hindered. While one workaround involves organizing commits so that feature-related ones come last, this still results in non-dependent commits relying on the initial commit.
To address this, I manually create a new branch, cherry-pick the independent commit, and initiate a new pull request. However, I believe this process could be streamlined using our tools.
Currently, our tool employs a conventional atomic commit and pull request strategy, creating a stack where subsequent commits depend on the approval of the initial one. This is effective for related dependent commits, like a new feature.
However, a common practice, including in my workflow, involves having commits unrelated to the current feature within the same stack. This, I believe, needlessly obstructs these commits, preventing them from being merged directly into the trunk branch without their original parent.
I propose the implementation of a CLI interface, allowing users to selectively include commits in the stack. For the remaining unselected commits, separate branches could be created, facilitating direct merging into the trunk. This process might involve creating new branches off the main branch and cherry-picking the desired commit.
One challenge with this approach is the potential lack of synchronization between the origin and local branches. Addressing this issue would be crucial for seamless integration.
What do you all think?

Hi!
So far handling this is delegated to the user.
The main reasoning of doing so is that there is high risk of rebase conflict and for the simplicity of the command line and workflow.
This said, I would be interested in reading your thoughts about how the command line could look like and evaluate having it as a feature


defining hashtag, links and adding hyperlinks

Good afternoon
Please tell me, does the library have a function for determining hashtags and links, as well as adding hyperlinks?
I tried to find information in the documentation but couldn't find anything.

Hi @RomanKozlovskiy
@DominikBucher12 started implementing link support, but it's not yet merged.

I am exploring an adjacent feature - where text is some sort of clickable token, like a hashtag. I expect it to be difficult. For starters, I would want to intercept a mouseclick.

@S1D1T1  I have mebtions and hashtag locally running as well thats next feature that will be implemented

I'd be interested to see that. My use isn't for hashtags or mentions, but for a scripting environment, where a variable name is a token. Similar to how variables are displayed in the Mac Shortcuts app- see attached graphic. the tokens should be "atomic" to the text editor - treated like a single character for purposes of cursor movement. I want to execute code when the token is clicked, to present a dialog with the token's properties.

That looks amazing! I'd love to use this library for snippet variables, but have no clue how to get started haha.

another UI model for handling a text token: address entry in Mail.app. You start out typing text, but when you complete a known address, it becomes an address object. it has a dropdown menu for managing its properties.

With TextKit2 this is very possible and actually more easy, I need to merge that PR with textKit2 in order to add those more "complex" features. I will try to sít down and take a look at that this week so I can merge those 2 PRs that are there for months.

@DominikBucher12 Can you tell me more about this change, and textkit 2? I would like to assess whether this will fit my needs. I'm not familiar with textkit2 - I see it's a new text editing library from Apple, but not in SwiftUI? At this point, just being able to intercept a mouse click or a .contextMenu would give me a starting point.
I've also considered implementing my "tokens" as embedded Images, making use of RTK's RTF capabilities. That would handle all the cursor movement perfectly, since they're already treated like a single character, and flow with text. But it sounds like your potential change might be better.

I'm a bit overwhelmed by the activity in this project, and would love be able to give it more time and attention. As of now, I however have to focus on some other project and freelance gigs, but can take a look at whatever you come up with.

With TextKit2 this is very possible and actually more easy, I need to merge that PR with textKit2 in order to add those more "complex" features. I will try to sít down and take a look at that this week so I can merge those 2 PRs that are there for months.

Did mentions ever get merged? I'm very much looking forward to that feature!

Hi @danielsaidi , thanks for the great tool! is there any update on the feature?

Hi @ammarasmro
Not at the moment, sorry.


Can provision the users using scim2/Me with invalid email formats

Suggested Labels
Affected : 5.8.0- alpha3
Severity: Major
Priority: Normal
Component: SCIM2
Type-Improvement
Environment
Linux, EmbeddedLDAP UserStore
Steps to Reproduce the Issue

Enable SCIM in user-mgt.xml
Set the scim2/Me Create Resource secured as false in identity.xml as in [1]
Provision a user using the sample request

curl -v -k --data '{"schemas":[],"name":{"familyName":"Johnson","givenName":"Alex"},"userName":"alex","password":"alexwso2","emails":[{"primary":true,"value":"alex.j","type":"home"},{"value":"alex_j@","type":"work"}],"EnterpriseUser":{"employeeNumber":"123A","manager":{"value":"Taylor"}}}' --header "Content-Type:application/json" https://localhost:9443/scim2/Me
Will allow to provision the users with email addresses that are invalid. Better to have a validation to validate the email addresses.
[1]. https://docs.wso2.com/display/IS570/apidocs/SCIM2-endpoints/#!/operations#MeEndpoint#createUserMe

Related - User Update using the below sample command also allows to update the users with invalid email formats.
curl -v -k --user alex:alexwso2 -X PUT -d '{"schemas":[],"name":{"familyName":"JacksonJohnoo","givenName":"Kimoo"},"userName":"alex","emails":[{"primary":true,"value":"jacksonkkkmmmgmail.com","type":"home"},{"value":"jackson_kkkwso2.com","type":"work"}]}' --header "Content-Type:application/json" https://is580.qa.com:443/scim2/Me

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


feat: add qs codemod

Adds a codemod for migrating from qs to picoquery.
Some options qs offers are not available. Currently, this mod will not warn on those but should in future.
Draft until we decide these things:

should it throw when unknown/unsupported options are used?
when encode: false is set, should we replace with decodeURIComponent(stringify(obj))? (encode is a pretty bad option to have so ideally we should just move consumers off it)
there are some rarely used options like object sort functions etc that we shouldn't really try codemod. do we just throw when they're used?

I think throwing with a clear error message is fine 👍

This is awkward 😅 https://github.com/es-tooling/module-replacements-codemods/pull/83

James and I had a long discussion about this on the e18e discord, and we concluded that migrating qs to pq might be the better long term solution for projects. While neoqs is a great drop-in replacement, pq also aligns closer to the URL spec, a lot of work went into the perfomance of it (that's not to say that's not the case for neoqs), and pq also fixes some of the "correctness" or weirdness/quirks of qs. We can discuss more about this on the discord in the #cleanup channel if you like, but let's keep the comments of this PR related to the actual PR 🙂

No worries, if that's the direction we're going with!

should it throw when unknown/unsupported options are used?

I think it's fine if we bail on these cases/if we can't codemod it

when encode: false is set, should we replace with decodeURIComponent(stringify(obj))? (encode is a pretty bad option to have so ideally we should just move consumers off it)

Hm that would be a breaking change in behavior, I'm ok with moving consumers off of it, but maybe we should add some logging to let them know about it?

there are some rarely used options like object sort functions etc that we shouldn't really try codemod. do we just throw when they're used?

I think thats fine yeah

Hm that would be a breaking change in behavior, I'm ok with moving consumers off of it, but maybe we should add some logging to let them know about it?

i think that would be sensible
the option leads to all sorts of bugs and weird behaviours so we should 100% be moving people off it. ill see if i can get it to wrap with decodeURIComponent then log a warning

@thepassle i've done the following:

reworked the options to be a map of option to Replacer to make things easier
added warnings for options we're unaware of (which will be dropped)
added a warning for encode: false and wrapped the result in decodeURIComponent automatically


Add newspaper icon from Feather requests #21

https://github.com/feathericons/feather/issues/21
Large:

100%:

@djsime1 Welcome to the Lucide community!
Please checkout our Icon Design Guide, we have some rules to make sure icons are consistent and match with the other icons.
If you can't figure it out, just say it we can help you.

I close this one due to inactivity

3 different Versions, any comment on them?
Not 2px spacing between the "header" and newspaper line:

Not 2px spacing between the lines representing the content of the newspaper:

Fulfilling all rules, but my least favorite:

What about that last one with the header not filled?

The header was not filled, it just was two pixels high, so it wouldn't show a white space in between.
Here two other versions.


"Hey Siri" stops working when using keyword recognition

Describe the bug

Set up Siri and make sure she responds to "Hey, Siri".
Launch VS Code with VS Code Speech installed.
Set accessibility.voice.keywordActivation to "chatInContext". (Probably anything other than "off" will do the trick.)
Say "Hey, Siri". Siri will not respond.

To Reproduce
Steps to reproduce the behavior:

open VS Code
install GitHub Copilot Chat and VS Code Speech extension
accessibility.voice.keywordActivation to "chatInContext"

Expected behavior
"Hey Siri" should still work.
Version of the Cognitive Services Speech SDK
1.33.x
Platform, Operating System, and Programming Language
Darwin arm64 23.3.0
Additional context
Originally reported as https://github.com/microsoft/vscode/issues/204811
VS Code extension is using the Azure Speech SDK in C++ and the keyword recognition code is here: https://github.com/microsoft/node-speech/blob/22064207050a16d0b30b1305857bafbba07402c9/src/main.cc#L424

hi @bpasero, the reason for this is that the SDK starts recording audio when keyword spotter is active, so this is expected to interfere with Siri in the same way that, for example, recording a voice memo would interfere with it. To mitigate this, the app can stop recognizing when it goes into the background.

Closed as answered, with a workaround.


Explicit flags to control HTTP probe request timeouts for slim and profile commands: --http-probe-req-wait, --http-probe-crawl-req-wait

Provides an ability to adjust the currently hardcoded http request timeouts. Also need to have corresponding fields in the custom HTTP profile JSON file definitions, request_wait and crawl_request_wait.
The --http-probe-req-wait flag would adjust the timeout value globally for all custom HTTP probe requests including crawler requests.
The --http-probe-crawl-req-wait flag would adjust only the crawler request timeout value (also globally).
Adjust per-request timeouts would require the use of the JSON command file.
Note that per-request timeout adjustments are possible to implement with the --http-probe-cmd flags too, but it would require adjusting the parsing logic for the value, so there's a place for the custom request timeouts. The probe command flag value is already busy as-is though and adding custom request timeouts will make it even messier and harder to use.

https://github.com/mintoolkit/mint/releases/tag/1.41.6


Soft Delete

Hi there,
I'm currently using this library and looking to implement a soft delete functionality instead of hard delete tenants/users/etc..., and I'm unsure about the best approach to achieve this within the library.
Could you provide guidance or best practices on how to implement soft delete functionality? Any code snippets, recommended practices, or pointers to relevant resources would be immensely helpful.
Thank you in advance for your assistance :)

Hi @bahaAbualkibash,
I actually built a library called EfCore.SoftDeleteServices which handles soft-delete and a multi-tenant key. The wiki holds documentation, plus links on the right to two articles and a EF Core standup where talked about soft delete with tenants (about 35 mins in).
Enjoy.


more video links

These still say coming soon on the website:

June 2019 https://www.youtube.com/playlist?list=PLclEcT4yxER75WBIf3-1qxO1Kuc0OAi-1
August 2019 https://www.youtube.com/playlist?list=PLclEcT4yxER6MT3tioOrWfNfJvDrjP0ts
January 2020 https://www.youtube.com/playlist?list=PLclEcT4yxER7Y1F5OAJ_NYb_cPFqYXAMq

Closed via https://github.com/donutjs/donutjs.club/commit/9ada854cf35aec5afc1c874bf2078f8a9319f3bc. Thank you @aaronpk! I think the only missing videos at this point are November 2019, and I can't remember what happened with those… is that a month where I messed up the A/V? 😅


Raise exception on all LibC.getaddrinfo errors

Opening a socket to a non existing host doesn't currently raise an error:
$ crystal eval 'require "socket"; p TCPSocket.new("localhosttttt", 4568)'
#<TCPSocket:fd 0>

Compared to Ruby (same code):
$ ruby -e 'require "socket"; p TCPSocket.new("localhosttttt", 4568)'
-e:1:in `initialize': getaddrinfo: nodename nor servname provided, or not known (SocketError)
	from -e:1:in `new'
	from -e:1:in `<main>'

Now, I have zero experience with C network programming, but according to getaddrinfo(3), not only -1 is an error, but everything nonzero. This PR does that, hopefully not breaking anything else :innocent:
It also adds a spec for the error raised when the connection is refused.
Thanks for the great work and keep up with it, I love Crystal!

:+1:

Build fails in Linux because the error message is different than in darwin (I'm using a mac) :cry:
I'll update the spec so that it works both platforms :sweat_smile:

It failed now on mac because of something unrelated and I have the suspicion that it would work if run again (but I have no permissions to restart it). I think it is ok now.

Well, you do, the trick is to rebase, amend nothing or similar and force push. Or in this case you could combine your commits into one: git rebase -i master, choose squash for the second, git push -f ;)

I will, thanks!

Thanks!


Massive memory leak, follow up on #2353

urql version & exchanges: urql/core 2.4.3 + cross-fetch 3.1.5 in NodeJS.
Steps to reproduce

Create a simple query with toPromise()
Place it in an infinite loop
Watch memory growth

Expected behavior
garbage collector cleans up old objects
Actual behavior
Closures, Request, Wonka objects remain in memory

After realizing issue #2353 was not related to Caching, I started removing code from my data processing application, until, literally just having a simple query in a loop. The Memory leak would still take place.
Here I attach memory charts as seen production, followed by memory after migrating the code to an alternative Graphql client with almost compatible interface:

Hey as referenced in that previous issue have you tried with v2.0.0 and 1.16.2, maybe we can track down whether this has always been there or is caused by an addition in urql.

I think I did, not entirely sure about 1.16.2, but definitely tried all the 2.x latest minors and the behavior seemed identical.

I mean, we might need a bit more to work with, like a way to reproduce this or notice this 😅 there might be a lot going on in your code that makes this irreproduceable for us on a clean core

sorry @JoviDeCroock I have already migrated to another toolkit.
In my last tests there was nothing but a simple query with .toPromise() in a loop, getting 10 rows on each execution. And not doing anything with the returned result.
Normally I put more effort on contributing but closing the previous issue despite letting know that I would come later with the result of the cache refactoring prompted me to look for an alternative lib, also... comments are disabled on closed issues too, I found out after writing a follow up.

Normally I put more effort on contributing but closing the previous issue despite letting know that I would come later with the result of the cache refactoring prompted me to look for an alternative lib, also... comments are disabled on closed issues too, I found out after writing a follow up.

I tend to stick to this idea. There is no point in closing an issue IMMEDIATELY if the person who found a problem is working hard to understand the cause.
@rvalle, may I ask which alternative did you find?

@rvalle You were still able to comment afaik, I mean just knowing how your client looked could go a long way for us but yes wishing you the best of luck anyway

@frederikhors for my application graphql-request is enough. I don't use UI features, mutations, or other things. I could have used fetch/post also....
@JoviDeCroock I do appreciate your project and contribution to opensource. I was not even upset, it is just that I also have a delivery calendar and I am in a rush.
don't know what happened with the other issue but after writing a long follow up is said "you cannot comment at this time".... I made a quick test now, and I its actually allowing comments. So, might have being some kind of glitch.
But honestly, I think the issue should be very easy to reproduce. Let me know if you cannot.

@rvalle We've got limited time and hence it's commonplace for reproductions to be necessary for non-obvious issues or questions to be resolved, meaning, if it's not simply in an existing example we provide then it takes work for us to make it. So, it's unfortunately not a question of whether it's easy or not to reproduce, but if you've got a code sample that reproduces the issue you achieve a couple of things that move all of us forward:

You're convincing yourself of the minimum (or close to minimum) requirements that are needed to reproduce the issue
You're providing a realistic scenario in case we need to make API changes or to test against (which makes it also easier to close an issue, even if you ran out of time to come back to us here)
We can see whether there's a potential misunderstanding between us before we go out and try to reproduce the exact sample of code you may have written (which eliminates assumptions)

So a code reproduction saves exponentially more time with each of these points.
That said, if you can also just post code here that you ran, I can see first whether there's something obvious we've missed or that causes this.
On the issue of commenting: closed issues are still open for commenting unless they're locked. GitHub did have API issues on the day you tried to potentially reply on though. So, that's likely what's caused this.
On the note that we closed the last issue on: The cacheExchange is not an LRU cache and if you're using @urql/core for one off requests you'll have to override the exchanges options and not pass a cache exchange, i.e. exchanges: [dedupExchange, fetchExchange]
Now, I assume you've done this, but hence what is actually retaining references to the responses becomes hard to tell for me. I had a scan through our Client a couple of days ago to rule out obvious mistakes from our end that'd maybe cause our "shared response sources" from being GC'd, but couldn't see anything obvious there

We think this may have been caused by a specific usage pattern with toPromise where multiple identical queries could leave behind copies of their result: https://github.com/FormidableLabs/urql/pull/2386
I'll close this for now, since I think this was the only condition that couldve caused this ✌

We think this may have been caused by a specific usage pattern with toPromise where multiple identical queries could leave behind copies of their result: #2386
I'll close this for now, since I think this was the only condition that could've caused this ✌

Hi
Unfortunately, I'm experiencing the exact situation that you are describing here,
I'm using @urql/core 3.0.3 to perform a lot of one-off requests (using toPromise), at a node express server, when some of the requests could be heavy (around 10MB).
Examining memory dump diffs shows undisposed Wonka objects:

Have you encountered any more reports like those? is it possible this bug wasn't fixed successfully

Anecdotally I am also seeing memory creep up as requests are sent with toPromise in a React Native app using @urql/core 3.0.3. I will try to examine more thoroughly, but as a simple binary test removing the requests does seem to "fix" the leak.

Hey folks, I can't confirm that the problem has been solved, I don't understand why the issue was closed. The same issue is still represented for me with the latest version of @urql/core. In meantime, I use the correct settings for exchanges which include only fetchExchange to prevent some caching there, and requestPolicy:  'network-only'.

Can anyone reproduce this? Like just a sandbox and some steps 😅

@JoviDeCroock
I couldn't share our production codebase or metrics but I've reproduced it as a part of a simple express application and I found the problem reproduced in the situation when I use the @urql/core client as a singleton. In case when I create a client for each request everything looks more stable and without memory leaking.
As @rvalle proposed, we can reproduce it with a simple loop or local DDOS (30+ RPS is fine) of the express app:
import 'isomorphic-unfetch';
import * as express from 'express';
import { createClient, fetchExchange, gql } from '@urql/core';

const fs = require('fs');
const v8 = require('v8');

function createHeapSnapshot() {
    const snapshotStream = v8.getHeapSnapshot();
    const fileName = `${Date.now()}.heapsnapshot`;
    const fileStream = fs.createWriteStream(fileName);
    snapshotStream.pipe(fileStream);
}

const app = express();
const port = 3000;

const query = gql`
    query {
        countries {
            name
        }
    }
`
const urqlClient = createClient({
     url: 'https://countries.trevorblades.com/',
     exchanges: [fetchExchange],
     requestPolicy: 'network-only',
});

app.use(require('express-status-monitor')());

app.get('/', async(req, res) => {
    await urqlClient.query(query, { test: new Date() }).toPromise().then()
    res.send('Hello World!')
});

const makeHeapSnapshot = () => {
    setInterval(() => {
        createHeapSnapshot()
    }, 20000)
}

makeHeapSnapshot()

app.listen(port, () => console.log(`Server started listening to port ${port}`));

You can see that memory is continiously growing:

If you move the initialization of the client to request, it will work fine (client isn't a singleton)
app.get('/', async(req, res) => {
    const urqlClient = createClient({
         url: 'https://countries.trevorblades.com/',
         exchanges: [fetchExchange],
         requestPolicy: 'network-only',
    });
    await urqlClient.query(query, { test: new Date() }).toPromise().then()
    res.send('Hello World!')
});

You can see that memory is fine:

Also I have the similar heap snapshot as @ShakedHad attached.
I din't go deeper to codebase for finding the reason yet but I hope this quick research will be helpful for you.

Just stepping in here really quick to say that we'll need details beyond these. We're very clear on what people are doing, however, in this case a heap snapshot (e.g. Chrome's devtools should be able to export memory profiles as per the snapshots shown) would be very helpful here.
In short, we'd need some details on the traced, retained objects to actually be able to see why this is happening, because we haven't quite been able to reproduce this cleanly, i.e. we haven't seen consistently retained objects and instead what I've seen is that usually retained "replay objects" (which is a secondary mini-cache in the Client) disappear cleanly 🤔

Hi @kitten
Thanks for your response, regarding your note on when to init the client:
I have to say it is really unclear from the documentation that these are your intentions (at least for me), specifically this part (https://formidable.com/open-source/urql/docs/basics/core/#one-off-queries-and-mutations)

@ShakedHad: To be fair, there's a difference here between SSR and non-SSR. What I mean is, if we were to make thousands of requests on one Client, we of course don't expect to create any memory leak. However, I don't want anyone to walk away with the wrong expectations here in case it's an unrelated issue 😅
Currently, I mostly expect that there's something wrong with the promise creation, but I don't have enough of an idea to go on here yet, since we previously already fixed a leak associated with that.
However, we don't have any relevant version info (@urql/core mainly), memory profiles that point at some objects in the stack, and such, which makes it hard to trace this down.
In other words, while this issue has collected a few new replies, every single case may in fact be different and only have Node.js in common. That's of course fine, but it's not the Node.js environment itself that's causing the leak, I mean, so our "original" issue creation requirements apply and we'll need new info to look into this :v:

So I have reproduced the problem and have created an example for you.
You need to start 2 servers and start the script for calling those.

You can see on the screenshot that after 1000 requests it starts consume more than 160mb and it will not be clean after finishing the script.

And also I created an example where I created urql for every incoming request.
so I suggest you to start first test:

Open terminal and run this: npm run gql-server
Open second terminal and run this: npm run request-server
Open third terminal and tun: npm run start
Open http://localhost:3000/status and check memory

Next time I suggest you to change second step and run npm run request-uniq-server.
You will see on http://localhost:3000/status that memory doesn't go up.

Just giving an update here; This will be resolved with the next release ✌
It's been really hard to chase this issue down, since it was in a very unrelated branch of the fetchExchange hidden in a stream operator. We believe the regression snuck in when we migrated that codebase over to TypeScript, since it came down to basically a single missing line of code / a single call.
While we spent a lot of time hunting this down, and it did take longer since the leak was small and steady, we did also take the opportunity to take a look into an alternative implementation of the fetch logic we had, which I worked on a while ago.
It's a more maintainable version of our current code and is based on async generators. Those should actually help the newer versions of Node.js/V8 a little along when it's under more load. At least, I've observed some small improvements while I was hunting down this issue.
However, that change will be delayed, so we have enough time to first get the memory leak patch shipped, without having to worry about introducing new regressions accidentally ✌


check for empty strings from arduino.

Your PR has too many conflicts.
Please link to your code so I can review it.


How to train a model with different dataset?

Thanks for the best work!
When I was learning this project, I was thinking how to use different dataset for training at the same time? Different dataset means different number of cameras, different bev size. I'm out of ideas, do you have any good ideas?
Looking forward to your reply!

I also encountered the same problem. May I ask how to train BEVFormer on the Kitti dataset？

have you trained bevformer on different datasets?

I also encountered the same problem. May I ask how to train BEVFormer on the Kitti dataset？

I haven't used the Kitti dataset before. This is how I solved the two problems:

Different number of cameras: padding zero image make all dataset have same input size.
Different bev size: take the largest bev size in the dataset.

have you trained bevformer on different datasets?

This is how I solved the two problems:
Different number of cameras: padding zero image make all dataset have same input size.
Different bev size: take the largest bev size in the dataset.

t

Can you tell me how you use the Kitti dataset

I also encountered the same problem. May I ask how to train BEVFormer on the Kitti dataset？

Can you tell me how you use the Kitti dataset

you can modify the data from kitti to nuscenes type(such as sample.json,sample_data.json, and so on.) or modify dataloader.whatever,if you can create right train.pkl,val.pkl,test.pkl.you can use kitti.
---- Replied Message ----
From @.> Date 05/09/2024 16:26 To @.> Cc<EMAIL_ADDRESS>Subject Re: [fundamentalvision/BEVFormer] How to train a model with different dataset? (Issue #141)
I also encountered the same problem. May I ask how to train BEVFormer on the Kitti dataset？
Can you tell me how you use the Kitti dataset
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Issue while compiling => script/setup_indexr-segment.sh: source: not found

I'm facing issues while compiling on ubuntu 16.04.
/home/anmol.singh/git/indexr/script/setup_indexr-segment.sh: 5: /home/anmol.singh/git/indexr/script/setup_indexr-segment.sh: **source: not found**

/home/anmol.singh/git/indexr/script/setup_lib.sh: 5: /home/anmol.singh/git/indexr/script/setup_lib.sh: **source: not found**

/home/anmol.singh/git/indexr/script/release_indexr-drill.sh: 15: /home/anmol.singh/git/indexr/script/release_indexr-drill.sh: **function: not found** cp: missing destination file operand after '/home/anmol.singh/git/indexr/distribution/indexr-/indexr-drill/jars/3rdparty/' Try 'cp --help' for more information.
/home/anmol.singh/git/indexr/script/release_indexr-drill.sh: 21: /home/anmol.singh/git/indexr/script/release_indexr-drill.sh: Syntax error: "}" unexpected
/home/anmol.singh/git/indexr/script/release_indexr-hive.sh: 5: /home/anmol.singh/git/indexr/script/release_indexr-hive.sh: source: not found
/home/anmol.singh/git/indexr/script/compile_indexr-hive.sh: 5: /home/anmol.singh/git/indexr/script/compile_indexr-hive.sh: source: not found

@radbrawler
Looks like source command not found in your shell. Try point sh to bash in your terminal.

replacing sh with bash works as the shebang(#!/usr/bin/env bash) asks for bash.


google-compute-engine: remove broken boto dependency

Description of changes
boto was marked as broken, causing any recent use of google-cloud-sdk with
with-gce set to true to fail to evaluate.
While the google-compute-engine package is quite old, its use of boto is
restricted to Pythons older than 3.0, so we can simply remove the boto
dependency entirely.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 342991 run on x86_64-linux 1

5 packages built:

google-cloud-sdk-gce
google-compute-engine (python312Packages.google-compute-engine)
google-compute-engine.dist (python312Packages.google-compute-engine.dist)
python311Packages.google-compute-engine
python311Packages.google-compute-engine.dist


chore: fix stats() return type

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

merging as this has no impact on code


[Go Live][May 24]

Push to live

Docs Build status updates of commit d2fe931:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/add-bot-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/deploy-azure/azure-deployed-app.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

msteams-platform/includes/get-started/azure-provisioning-instructions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-bot.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Crash: TestSuite error

Hi all,
After installing torch and cutorch/ cunn /cudnn I try to load the library with
require('cutorch')
but I get this error message
" _install/share/lua/5.1/torch/TestSuite.lua:15: Test atan2 is already defined.  "
Has anyone encountered something similar before?
This was after a clean installation, never had the problem before. I've noticed after installing
cudnn.
Thanks,

this is probably because of a change that I made yesterday. i'll fix it in a sec.

fixed via https://github.com/torch/cutorch/commit/1c8012af3bae22c377101600fc00153076484403


Issue when using a 4k Monitor

When using a 4k monitor, severall elements are displayed very small.
Would there be a way to specify a file to overwrite the original css?

If you wanted to make raidboss bigger, for example, you can create a user css file.  If you create the file cactbot/user/raidboss.css, then anything in that file will be included automatically into raidboss.  You can do the same for other modules by substituting a different name there.
In this case, you probably want css that is something like this:
body {
  transform: scale 2;
  transform-origin: 0 0;
}

ahh ok, thank you for this information and it worked like a charm

This didn't seem to work for me, but editing the html file in the UI folder and changing the body tag to
<body style="zoom: 130%;"> seemed to work for me in either jobs or raidboss.


DV Resolve - loading/updating - OTIO file

[cuID:PYPE-1141]

This is missing a description of the issue.


Handle coupons from database instead of config file?

Is there currently a way to change the coupon handling to read from database instead of the config file?

See #69, but instead of PlanRepository you'd create and rebind your own CouponRepository. I'll create a PR soon to update the docs for a better explanation