text:
Endless waiting for the consumer when trying to read all sent messages in the topic.

Hello! Thanks for your work.
I have a question.
I am using your example https://github.com/mostafa/xk6-kafka/blob/main/scripts/test_consumer_group.js
and ran into the problem that if you try to subtract all 300 messages, then the consumer waits indefinitely. And this happens somewhere in 3 out of 5 attempts.
Full code
/*
This is a k6 test script that imports the xk6-kafka and
tests Kafka with a 200 JSON messages per iteration.
*/

import { check } from "k6";
// import * as kafka from "k6/x/kafka";
import {
  Writer,
  Reader,
  Connection,
  SchemaRegistry,
  CODEC_SNAPPY,
  SCHEMA_TYPE_JSON,
} from "k6/x/kafka"; // import kafka extension

// Prints module-level constants
// console.log(kafka);

const brokers = ["localhost:9092"];
const topic = "test";
const groupID = "my-group";

const writer = new Writer({
  brokers: brokers,
  topic: topic,
  compression: CODEC_SNAPPY,
});
const reader = new Reader({
  brokers: brokers,
  groupID: groupID,
  groupTopics: [topic],
});
const connection = new Connection({
  address: brokers[0],
});
const schemaRegistry = new SchemaRegistry();

if (__VU == 0) {
  connection.createTopic({
    topic: topic,
    numPartitions: 3,
    replicationFactor: 1,
    configEntries: [
      {
        configName: "compression.type",
        configValue: CODEC_SNAPPY,
      },
    ],
  });
}

export const options = {
  thresholds: {
    // Base thresholds to see if the writer or reader is working
    kafka_writer_error_count: ["count == 0"],
    kafka_reader_error_count: ["count == 0"],
  },
};

export default function () {
  let messages = [];
  for (let i = 0; i < 100; i++) {
    for (let partition = 0; partition < 3; partition++) {
      messages.push({
        // The data type of the key is JSON
        key: schemaRegistry.serialize({
          data: {
            key: "value",
          },
          schemaType: SCHEMA_TYPE_JSON,
        }),
        // The data type of the value is JSON
        value: schemaRegistry.serialize({
          data: {
            key: "value",
          },
          schemaType: SCHEMA_TYPE_JSON,
        }),
        parition: partition,
      });
    }
  }

  writer.produce({ messages: messages });

  // Read one message only
  messages = reader.consume({ limit: 300 });

  check(messages, {
    "10 messages is received": (messages) => messages.length == 300,
  });

  check(messages[0], {
    "Topic equals to xk6_kafka_consumer_group_topic": (msg) =>
      msg["topic"] == topic,
    "Key contains key/value and is JSON": (msg) =>
      schemaRegistry.deserialize({
        data: msg.key,
        schemaType: SCHEMA_TYPE_JSON,
      }).key == "value",
    "Value contains key/value and is JSON": (msg) =>
      typeof schemaRegistry.deserialize({
        data: msg.value,
        schemaType: SCHEMA_TYPE_JSON,
      }) == "object" &&
      schemaRegistry.deserialize({
        data: msg.value,
        schemaType: SCHEMA_TYPE_JSON,
      }).key == "value",
  });
}

export function teardown(data) {
	  if (__VU == 0) {
    // Delete the topic
    connection.deleteTopic(topic);
  }
  writer.close();
  reader.close();
  connection.close();
}

logs
time="2023-03-13T09:02:59+03:00" level=info msg="entering loop for consumer group, my-group\n"
time="2023-03-13T09:02:59+03:00" level=info msg="entering loop for consumer group, my-group\n"
time="2023-03-13T09:03:04+03:00" level=info msg="joined group my-group as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41 in generation 10"tions
time="2023-03-13T09:03:04+03:00" level=info msg="selected as leader for group, my-group\n" VU
time="2023-03-13T09:03:04+03:00" level=info msg="joined group my-group as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-87f19579-d19e-4e5c-aed6-b3b2bc286b5f in generation 10"
time="2023-03-13T09:03:04+03:00" level=info msg="joinGroup succeeded for response, my-group.  generationID=10, memberID=k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-87f19579-d19e-4e5c-aed6-b3b2bc286b5f"
time="2023-03-13T09:03:04+03:00" level=info msg="Joined group my-group as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-87f19579-d19e-4e5c-aed6-b3b2bc286b5f in generation 10"
time="2023-03-13T09:03:04+03:00" level=info msg="using 'range' balancer to assign group, my-group"
time="2023-03-13T09:03:04+03:00" level=info msg="found member: k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41/[]byte(nil)"
time="2023-03-13T09:03:04+03:00" level=info msg="found member: k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-87f19579-d19e-4e5c-aed6-b3b2bc286b5f/[]byte(nil)"
time="2023-03-13T09:03:04+03:00" level=info msg="found topic/partition: test/0"
time="2023-03-13T09:03:04+03:00" level=info msg="assigned member/topic/partitions k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41/test/[0]"
time="2023-03-13T09:03:04+03:00" level=info msg="joinGroup succeeded for response, my-group.  generationID=10, memberID=k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41"
time="2023-03-13T09:03:04+03:00" level=info msg="Joined group my-group as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41 in generation 10"
time="2023-03-13T09:03:04+03:00" level=info msg="Syncing 2 assignments for generation 10 as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-de501498-6407-4c63-8e28-15f52cd51a41"
time="2023-03-13T09:03:04+03:00" level=info msg="received empty assignments for group, my-group as member k6@QPRM-FVSC1F3 (github.com/segmentio/kafka-go)-87f19579-d19e-4e5c-aed6-b3b2bc286b5f for generation 10"
time="2023-03-13T09:03:04+03:00" level=info msg="sync group finished for group, my-group"
time="2023-03-13T09:03:04+03:00" level=info msg="sync group finished for group, my-group"

running (00m05.0s), 1/1 VUs, 0 complete and 0 interrupted iterations
default   [--------------------------------------time="2023-03-13T09:03:04+03:00" level=info msg="started heartbeat for group, my-group [3s]"
time="2023-03-13T09:03:04+03:00" level=info msg="subscribed to topics and partitions: map[]"
] 1 VUs  00m05.0s/10m0s  0/1 iters, 1 per VUtime="2023-03-13T09:03:04+03:00" level=info msg="started heartbeat for group, my-group [3s]"

time="2023-03-13T09:03:04+03:00" level=info msg="initializing kafka reader for partition 0 of test starting at offset first offset"
time="2023-03-13T09:03:04+03:00" level=info msg="subscribed to topics and partitions: map[{topic:test partition:0}:-2]"

I have tried the rebalanceTimeout and sessionTimeout settings but without success.
Could you suggest what I am doing wrong?

@bloodgang94
I ran your exact script (with no modifications) for a minute with 50 VUs and this is the result:

View results
./k6 run --vus 50 --duration 60s /mnt/c/Users/Mostafa\ Moradian/Desktop/test-kafka.js

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

  execution: local
     script: /mnt/c/Users/Mostafa Moradian/Desktop/test-kafka.js
     output: engine

  scenarios: (100.00%) 1 scenario, 50 max VUs, 1m30s max duration (incl. graceful stop):
           * default: 50 looping VUs for 1m0s (gracefulStop: 30s)

ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."

     ✓ 10 messages is received
     ✓ Topic equals to xk6_kafka_consumer_group_topic
     ✓ Key contains key/value and is JSON
     ✓ Value contains key/value and is JSON

     █ teardown

     checks.........................: 100.00% ✓ 1764        ✗ 0
     data_received..................: 0 B     0 B/s
     data_sent......................: 0 B     0 B/s
     iteration_duration.............: avg=137.67ms min=122.3ms med=131.32ms max=941ms    p(90)=147.73ms p(95)=155.48ms
     iterations.....................: 441     4.857311/s
     kafka_reader_dial_count........: 1       0.011014/s
     kafka_reader_dial_seconds......: avg=4.13µs   min=0s      med=0s       max=1.82ms   p(90)=0s       p(95)=0s
   ✓ kafka_reader_error_count.......: 0       0/s
     kafka_reader_fetch_bytes.......: 7.5 MB  83 kB/s
     kafka_reader_fetch_bytes_max...: 1000000 min=1000000   max=1000000
     kafka_reader_fetch_bytes_min...: 1       min=1         max=1
     kafka_reader_fetch_size........: 124995  1376.733793/s
     kafka_reader_fetch_wait_max....: 10s     min=10s       max=10s
     kafka_reader_fetches_count.....: 16      0.176229/s
     kafka_reader_lag...............: 7400    min=6500      max=14600
     kafka_reader_message_bytes.....: 4.0 MB  44 kB/s
     kafka_reader_message_count.....: 132401  1458.30578/s
     kafka_reader_offset............: 132400  min=400       max=132400
     kafka_reader_queue_capacity....: 100     min=100       max=100
     kafka_reader_queue_length......: 100     min=99        max=100
     kafka_reader_read_seconds......: avg=127.24ms min=0s      med=0s       max=4.01s    p(90)=0s       p(95)=0s
     kafka_reader_rebalance_count...: 1       0.011014/s
     kafka_reader_timeouts_count....: 0       0/s
     kafka_reader_wait_seconds......: avg=32.96µs  min=0s      med=0s       max=1.54ms   p(90)=0s       p(95)=0s
     kafka_writer_acks_required.....: 0       min=0         max=0
     kafka_writer_async.............: 0.00%   ✓ 0           ✗ 490
     kafka_writer_attempts_max......: 0       min=0         max=0
     kafka_writer_batch_bytes.......: 26 kB   281 B/s
     kafka_writer_batch_max.........: 1       min=1         max=1
     kafka_writer_batch_size........: 490     5.397012/s
     kafka_writer_batch_timeout.....: 0s      min=0s        max=0s
   ✓ kafka_writer_error_count.......: 0       0/s
     kafka_writer_message_bytes.....: 7.6 MB  84 kB/s
     kafka_writer_message_count.....: 147000  1619.103705/s
     kafka_writer_read_timeout......: 0s      min=0s        max=0s
     kafka_writer_retries_count.....: 0       0/s
     kafka_writer_wait_seconds......: avg=0s       min=0s      med=0s       max=0s       p(90)=0s       p(95)=0s
     kafka_writer_write_count.......: 147000  1619.103705/s
     kafka_writer_write_seconds.....: avg=30.37µs  min=12.5µs  med=23.17µs  max=163.86µs p(90)=50.43µs  p(95)=78.4µs
     kafka_writer_write_timeout.....: 0s      min=0s        max=0s
     vus............................: 0       min=0         max=50
     vus_max........................: 50      min=50        max=50

running (1m30.8s), 00/50 VUs, 441 complete and 49 interrupted iterations
default ✓ [======================================] 50 VUs  1m0s

I am aware of the reader errors, as you see in the logs. The writer generated 147k messages and the reader consumed 132k. The number of errors and your limit of 300 correlates to the difference between the messages produced vs. consumed. I tweaked the reader config and this is the best result I can get:
import {
  Writer,
  Reader,
  Connection,
  SchemaRegistry,
  CODEC_SNAPPY,
  SCHEMA_TYPE_JSON,
  SECOND,
} from "k6/x/kafka"

const reader = new Reader({
  brokers: brokers,
  groupID: groupID,
  groupTopics: [topic],
  queueCapacity: 300,
  readBatchTimeout: 20 * SECOND,
  maxBytes: 10000000, // 10 MB
  readLagInterval: 10 * SECOND,
})

View results
 ./k6 run --vus 50 --duration 60s /mnt/c/Users/Mostafa\ Moradian/Desktop/test-kafka.js

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

  execution: local
     script: /mnt/c/Users/Mostafa Moradian/Desktop/test-kafka.js
     output: engine

  scenarios: (100.00%) 1 scenario, 50 max VUs, 1m30s max duration (incl. graceful stop):
           * default: 50 looping VUs for 1m0s (gracefulStop: 30s)

ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."
ERRO[0090] Unable to read messages.                      error="Unable to read messages."

     ✓ 10 messages is received
     ✓ Topic equals to xk6_kafka_consumer_group_topic
     ✓ Key contains key/value and is JSON
     ✓ Value contains key/value and is JSON

     █ teardown

     checks.........................: 100.00%  ✓ 1808        ✗ 0
     data_received..................: 0 B      0 B/s
     data_sent......................: 0 B      0 B/s
     iteration_duration.............: avg=134.43ms min=122.3ms med=128.82ms max=998.19ms p(90)=138.76ms p(95)=145.67ms
     iterations.....................: 452      4.971897/s
     kafka_reader_dial_count........: 1        0.011/s
     kafka_reader_dial_seconds......: avg=2.98µs   min=0s      med=0s       max=1.35ms   p(90)=0s       p(95)=0s
   ✓ kafka_reader_error_count.......: 0        0/s
     kafka_reader_fetch_bytes.......: 7.8 MB   86 kB/s
     kafka_reader_fetch_bytes_max...: 10000000 min=10000000  max=10000000
     kafka_reader_fetch_bytes_min...: 1        min=1         max=1
     kafka_reader_fetch_size........: 130200   1432.170354/s
     kafka_reader_fetch_wait_max....: 10s      min=10s       max=10s
     kafka_reader_fetches_count.....: 10       0.109998/s
     kafka_reader_lag...............: 8700     min=0         max=14400
     kafka_reader_message_bytes.....: 4.1 MB   45 kB/s
     kafka_reader_message_count.....: 135901   1494.880056/s
     kafka_reader_offset............: 135900   min=600       max=135900
     kafka_reader_queue_capacity....: 300      min=300       max=300
     kafka_reader_queue_length......: 300      min=300       max=300
     kafka_reader_read_seconds......: avg=125.21ms min=0s      med=0s       max=6.52s    p(90)=0s       p(95)=0s
     kafka_reader_rebalance_count...: 1        0.011/s
     kafka_reader_timeouts_count....: 0        0/s
     kafka_reader_wait_seconds......: avg=17.22µs  min=0s      med=0s       max=1.14ms   p(90)=0s       p(95)=0s
     kafka_writer_acks_required.....: 0        min=0         max=0
     kafka_writer_async.............: 0.00%    ✓ 0           ✗ 501
     kafka_writer_attempts_max......: 0        min=0         max=0
     kafka_writer_batch_bytes.......: 26 kB    287 B/s
     kafka_writer_batch_max.........: 1        min=1         max=1
     kafka_writer_batch_size........: 501      5.510886/s
     kafka_writer_batch_timeout.....: 0s       min=0s        max=0s
   ✓ kafka_writer_error_count.......: 0        0/s
     kafka_writer_message_bytes.....: 7.8 MB   86 kB/s
     kafka_writer_message_count.....: 150300   1653.265778/s
     kafka_writer_read_timeout......: 0s       min=0s        max=0s
     kafka_writer_retries_count.....: 0        0/s
     kafka_writer_wait_seconds......: avg=0s       min=0s      med=0s       max=0s       p(90)=0s       p(95)=0s
     kafka_writer_write_count.......: 150300   1653.265778/s
     kafka_writer_write_seconds.....: avg=34.71µs  min=11.38µs med=21.61µs  max=406.52µs p(90)=45.03µs  p(95)=130.23µs
     kafka_writer_write_timeout.....: 0s       min=0s        max=0s
     vus............................: 0        min=0         max=50
     vus_max........................: 50       min=50        max=50

running (1m30.9s), 00/50 VUs, 452 complete and 49 interrupted iterations
default ✓ [======================================] 50 VUs  1m0s

I'll close this due to inactivity. Feel free to re-open it if you still have the issue.

@mostafa
After making changes also getting Unable to read messages error right
Then what does it mean?
How to avoid this error?

Even in your result also writer message count and reader message count are different

authors: SanthoS-web bloodgang94 mostafa


text:
Please add docs search

Is your feature request related to a problem? Please describe.
I am checking someone else's code and trying to understand what this function does:
import { wrap } from "@motionone/utils";
const x = useTransform(baseX, (v) => `${wrap(-20, -45, v)}%`);

It seems that utils are not documented, yet I still have to click through the docs to ensure I missed something.
Describe the solution you'd like
A search function like Agnolia would same a lot of time.

I'm currently porting the docs to Framer, once complete this will have search functionality.

https://www.framer.com/motion/scroll-animations/
https://codesandbox.io/p/sandbox/framer-motion-scroll-velocity-r1dy4u?file=%2Fsrc%2FApp.tsx%3A6%2C13
the docs are probably outdated, I'm trying to follow the docs but in the framer-motion version: "^11.0.3", and I have the same problem saying it doesn't exist: import { wrap } from '@motionone/utils'; Do we need to install the part? Or has this function been discontinued?

source: gharchive/issue

authors: MiguelSilvaViana kouliavtsev mattgperry

repo: motiondivision/motionone

license: MIT

license_type: permissive

license_source: github-api


text:
README: add Mikros Image

And thank you for your amazing tool :+1:

Thanks to you @cchampet!

Very cool! 🎉

source: gharchive/pull-request

authors: cchampet fredrikaverpil mottosso

license: mit

license_source: bigquery


text:
scoop shows the wrong version: 1.7 while shipping 1.8.1 which caused an hash error

See https://github.com/ScoopInstaller/Extras/issues/10663
And https://github.com/ScoopInstaller/Extras/commit/63b9f4702f7207c03f68511f07175977813c84bb

Someone has added it to Scoop. But it needs updating

authors: martin-rueegg moudey

repo: moudey/Shell


text:
Win+X menu?

Is there any way to add/modify items in the Win+X menu? I feel like there should be, since it is affected by the theme.
I tried this:
item(title='This should appear everywhere')
And it appeared everywhere but the Win+X menu.

I try not to make a mess of all menus. Therefore, other options will be added to adjust the display of dynamic items

Refer to #78


text:
🛑 pmgconsulting.org is down

In a01b10f, pmgconsulting.org (https://pmgconsulting.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: pmgconsulting.org is back up in 695c4c9 after 9 minutes.

repo: moul/uptime


text:
Perlmutter setup

This PR adds the salloc commands for cori and perlmutter in the Reproducibility section.
Additional question from the Known Issues section:
* For secondary targets in SV1, the targeting catalog filenames recorded in the
  fiberassign header are inconsistent with the contents of the corresponding
  fibermap catalog for a given TILEID.

Isn't that fixed now, by the most recent major patch of the fiberassign files?

Thank you for this contribution, @weaverba137.

Additional question from the Known Issues section:

For secondary targets in SV1, the targeting catalog filenames recorded in the
fiberassign header are inconsistent with the contents of the corresponding
fibermap catalog for a given TILEID.

Isn't that fixed now, by the most recent major patch of the fiberassign files?

Yes, but for the v1.0 version of these VACs, this Known Issue is still relevant.

Follow-up on the known issue: after the major fiberassign patch, would the target photometry be more consistent if it were obtained directly from the fiberassign files, rather than stepping back to the targeting files? That only applies to assigned fibers, of course, not to potential targets.

The targeting files have always been correct. The re-patched fiberassign files just fixed issues that arose by not populating (some) data from the targeting files correctly (as well as some mixed-rows issues from the first round of patching).

repo: moustakas/desi-photometry


text:
Rename --only-deps to --fetch-deps-only, make it only populate MOVE_HOME

Motivation
Fixes https://github.com/move-language/move/issues/236
Overwrites https://github.com/move-language/move/pull/104
AFAIK, the only IDE that uses dependencies source code is the Intellij-move plugin. Move-analyzer yet to support that, I assume no breakages there.
@vladimirovmm @awelc @tnowacki
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Testing would require mocking MOVE_HOME, calling the command with the flag, and checking that correct git repos are cloned. I want to hear the feedback first, then I'll try to write one.

On the test side of things, it's a network-heavy feature that requires mocking many things. Considering its niche use case, I'd leave it untested.

repo: move-language/move


text:
5.3.0 is not compatible with Expo FileSystem

This example used to work
import * as FileSystem from 'expo-file-system';
import { InteractionManager } from 'react-native';
import { fileAsyncTransport, logger } from 'react-native-logs';

const consoleLog = logger.createLogger({
  transport: fileAsyncTransport,
  transportOptions: {
    FS: FileSystem,
    fileName: `logs_${new Date().toLocaleDateString()}.txt`,
  },
  asyncFunc: InteractionManager.runAfterInteractions,
});

But now it's complaining that

error TS2322: Type 'typeof import("C:/p/expo-experiments/node_modules/expo-file-system/build/index")' is not assignable to type 'RNFS | EXPOFS'.
Type 'typeof import("C:/p/expo-experiments/node_modules/expo-file-system/build/index")' is missing the following properties from type 'EXPOFS': DocumentDirectoryPath, appendFile

What you likely need to do is remove the never lines in the type at least to get it to pass the typing.
  DocumentDirectoryPath: never;

Same issue with RNFS, the type definitions in fileAsyncTransport.ts don't appear to be correct.
TS2322: Type
typeof import("/Users/{name}/IdeaProjects/pop/node_modules/react-native-fs/index")
is not assignable to type RNFS | EXPOFS
Type
typeof import("/Users/{name}/IdeaProjects/pop/node_modules/react-native-fs/index")
is missing the following properties from type RNFS: documentDirectory, writeAsStringAsync

I think having custom type definitions to enforce using a particular package won't really work as you'll constantly need to update it as the packages update. In my opinion you'd either have to import both of those packages and do typeof (if possible) or revert to any?

repo: mowispace/react-native-logs


text:
Add type="button" to ArrayFieldTemplate example

Reasons for making this change
Without the type="button" Enter keypresses in any of the input fields cause the button's onAddClick to trigger. Just a quick edit to make copy-paste experimentation with this example smoother.
If this is related to existing tickets, include links to them as well. (N/A)
Checklist

[x] I'm updating documentation

[x] I've checked the rendering of the Markdown text I've added
[ ] If I'm adding a new section, I've updated the Table of Content

[ ] I'm adding or updating code

[ ] I've added and/or updated tests
[ ] I've updated docs if needed
[ ] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

Thanks! (And sorry for the delay in review!)

authors: glasserc theengineear

repo: mozilla-services/react-jsonschema-form


text:
Close more intermittent bugs more frequently

Otherwise we will catch up too slowly.
Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[x] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

"The Hitchhiker's Guide to the Galaxy"

repo: mozilla/bugbot


text:
Install cargo-dist to generate releases

This PR was generated by running cargo dist init and selecting all the default options. It seems to have pretty sane behaviour out of the box.
This requires the repository URL fix in https://github.com/mozilla/cargo-vet/pull/599 to work correctly.
Fixes https://github.com/mozilla/cargo-vet/issues/484

For anybody following along on this, https://matrix.to/#/!dRHkXGXAEhtBOpnLTY:mozilla.org/$4_H4pbu-FftonOnqfHJLXWZzd1ZNHSDdtptBk1IW_r4?via=mozilla.org

repo: mozilla/cargo-vet


text:
Remove 'Full nomination will be available in...' (bug 1200790)

@magopian r?

Updated to drop the feature entirely.

Excellent work, thanks! r+wc

Done, thank you!

authors: magopian wagnerand

repo: mozilla/olympia


text:
Certain links (e.g. textedit://...) missing from renders

Attach (recommended) or Link to PDF file here
test (1).pdf
Configuration:

Online example

Steps to reproduce the problem:

Upload and view the attached PDF
Links on the note heads are missing, but the link in the footer

What is the expected behavior? (add screenshot)
Links on the note heads are shown (From Adobe Acrobat)

What went wrong? (add screenshot)
Links on noteheads are missing.

The textedit protocol is not allowed by https://github.com/mozilla/pdf.js/blob/d9d626a5e16cb3662c188bd2f12cb8584360c86a/src/shared/util.js#L397-L412, which most likely explains this problem. Only whitelisted protocols are allowed for links for security reasons (and the textedit protocol also seems specific to one particular piece of software), especially since this tries to open local files.

Please note that we only "standard" protocols when creating/validating URLs, please refer to https://github.com/mozilla/pdf.js/blob/ba99e54c66c33562a7d88f1d230d7bc4d02bbadb/src/shared/util.js#L397-L434
This looks, for all intents and purposes, like a duplicate of e.g. issue #10057

authors: Snuffleupagus lhl2617 timvandermeij


text:
Draw tool should warn users that it shouldn't be used for redaction

Some users may use the draw tool incorrectly assuming the content obscured by any drawing has been entirely removed from the document. This may pose a security/privacy risk to those using it as there is no indication to suggest otherwise. I think a notice should be included to ensure users are aware that the markings created using the draw tool can be removed.

For reference, using the Markup tool in the macOS Preview application generates a similar warning

@timvandermeij To address this, I propose adding a notice to inform users that markings created with the draw tool can be removed and that the underlying content is still accessible.
I would like to take on this task and work on implementing the necessary changes to mitigate this risk. Could you please assign this issue to me?

Unfortunately I believe that UX needs to be involved first, before this issue becomes actionable, to help decide if something like this should be done and if so provide a specification for the implementation.

Hii @timvandermeij @Snuffleupagus
I've created a design for the new Note section and would like to share a screenshot of it for your review and feedback.
Looking forward to your thoughts!

Hii @timvandermeij i have added a notice to the draw tool UI and opened a PR .

authors: Snuffleupagus foxt siddharthisrani


text:
[Bug]: Cannot read properties of undefined (reading 'createElement')

Attach (recommended) or Link to PDF file
I can't add a example of the PDFs I'm using because they are proprietary.
Web browser and its version
Chrome 126
Operating system and its version
OSX Ventura
PDF.js version
4.0.379
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem
Make a call to the pdf.getPage.render method:
export const processUploadedPDF = async (file: File): Promise<string[]> => {
  try {
    const pagePreviews: string[] = [];
    const loadingTask = pdfjs.getDocument({ data: new Uint8Array(await file.arrayBuffer()) });
    const pdf = await loadingTask.promise;

    for (let i = 1; i <= pdf.numPages; i++) {
      const page = await pdf.getPage(i);
      const viewport = page.getViewport({ scale: 1.0 });
      const canvas = document.createElement('canvas');
      const context = canvas.getContext('2d');
      canvas.width = viewport.width;
      canvas.height = viewport.height;

      await page.render({
        canvasContext: context!,
        viewport: viewport,
        background: '#fff',
      }).promise;

      const base64Image = canvas.toDataURL('image/png');
      pagePreviews.push(base64Image);
    }

    return pagePreviews;
  } catch (error) {
    return [];
  }
};

What is the expected behavior?
pdf.getPage.render should not error and paint the pdf to the passed canvas context.
What went wrong?
An error is thrown:
TypeError: Cannot read properties of undefined (reading 'createElement')
    at DOMCanvasFactory._createCanvas (display_utils.js:383:35)
    at DOMCanvasFactory.create (base_factory.js:51:25)
    at CachedCanvases.getCanvas (canvas.js:203:40)
    at CanvasGraphics._scaleImage (canvas.js:1221:39)
    at CanvasGraphics.paintInlineImageXObject (canvas.js:2993:25)
    at CanvasGraphics.paintImageXObject (canvas.js:2891:10)
    at CanvasGraphics.executeOperatorList (canvas.js:1088:20)
    at InternalRenderTask._next (api.js:3389:37)
    at api.js:3378:14

The this in the line this._document.createElement("canvas"); is undefined.
Link to a viewer
No response
Additional context
We recently moved from Create React App to Vite and this issue was only noticed after that so it must have something to do with that.
This doesn't happen with all the PDFs we use but it happens on about 90% of them.
We use pdfjs installed from NPM and have the worker file in the public folder using:
pdfjs.GlobalWorkerOptions.workerSrc = new URL('/pdf-viewer/pdf.worker.js', import.meta.url).href;

to set up the GlobalWorkerOptions.workerSrc.
I tried updating to the latest version of PDFJS but got the same error.

With no reproduction is really difficult to understand what's going on.
I suggest placing a breakpoint at https://github.com/mozilla/pdf.js/blob/ccad2f889ae8e721b1a1119190f03f99c68ae763/src/display/display_utils.js#L482 in your app, and figuring out why _document is set to undefined.

Attach (recommended) or Link to PDF file
I can't add a example of the PDFs I'm using because they are proprietary.

Unfortunately this makes this issue, or any issue really, non-actionable.

Steps to reproduce the problem
Make a call to the pdf.getPage.render method:

Please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

Additional context
We recently moved from Create React App to Vite and this issue was only noticed after that so it must have something to do with that.

In that case, this unfortunately seems unrelated to the PDF.js library.

authors: Snuffleupagus adamdaly nicolo-ribaudo


text:
Add new fonts

i have a PDF file that has custom font , when run it in pdf.js the font not rendered ,
how can i add this font or other fonts to pdf.js ?
http://d1.islamhouse.com/data/pdf-viewer/web/viewer.html?file=http://d1.islamhouse.com/data/kn/ih_fatawa/single/kn_merits_of_arafat.pdf

You should embed the necessary fonts in the PDF files, but otherwise you can use CSS's @font-face. Closing as answered.

thanks for you @timvandermeij :)

How to incorporate a font in the rendered page using CSS's @font-face T_T ? I am rendering a canvas with pdfjs, i have done some tests and it does not work.

authors: arelaxend maherelgamil timvandermeij


text:
Visualisation problems

Link to PDF file (or attach file here): http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/111/95/491-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/112/96/493-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/113/97/494-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/115/98/495-1
Configuration:

Web browser and its version: All, it happens more in google chrome and in opera,  happens less frequently in internet explorer and firefox.
Operating system and its version: Windows and Linux
PDF.js version:   1.0.907
Is an extension: Yes

Steps to reproduce the problem:

Click the link in different Browsers and OS.
If visualization is weird:
Click fullscreen button
Press Esc

What is the expected behavior?
PDF should be showed well formated.

What went wrong?
Some fonts problems.

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/111/95/491-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/112/96/493-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/113/97/494-1
http://www.livrosabertos.sibi.usp.br/portaldelivrosUSP/catalog/view/115/98/495-1

WFM on Mac OSX. Please provide exact versions of the Linux (and Windows) as well as browsers.
Can you reproduce this with the viewer at http://mozilla.github.io/pdf.js (files can be opened via the open file button)?

Hi,
With viewer at http://mozilla.github.io/pdf.js I can't reproduce the error.
Let's starting getting just one OS and Browser.
OS: Windows 10 x64
Browser chrome: Versão 55.0.2883.87 m
Please open all the four links.
It does not happen every time.
I think it's cache-related.
After displaying the PDF correctly it does not show weird for a while.
After half an hour, weird reappears.
Regards.

Tarcisio Pereira

De: Yury Delendik notifications@github.com
Enviado: quarta-feira, 21 de dezembro de 2016 11:46
Para: mozilla/pdf.js
Cc: Tarcisio; Author
Assunto: Re: [mozilla/pdf.js] Visualisation problems (#7908)
WFM on Mac OSX. Please provide exact versions of the Linux (and Windows) as well as browsers.
Can you reproduce this with the viewer at http://mozilla.github.io/pdf.js (files can be opened via the open file button)?
Pdf.js: PDF Reader in JavaScript - mozilla.github.iohttp://mozilla.github.io/pdf.js
mozilla.github.io
©Mozilla and individual contributors. PDF.js is licensed under Apache, documentation is licensed under CC BY-SA 2.5

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mozilla/pdf.js/issues/7908#issuecomment-268526419, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGZMcyrGz5wseJipwcrD-1Q6wLsu_NDuks5rKS3MgaJpZM4LS67-.

PDF.js version: 1.0.907

With viewer at http://mozilla.github.io/pdf.js I can't reproduce the error.

The viewer deployed at www.livrosabertos.sibi.usp.br is old version. We cannon upgrade third-party deployment. Please notify the admins of this site about the issue. Closing as fixed.

Hi @yurydelendik
Viewer deployed at www.livrosabertos.sibi.usp.br is now updated.
Now, this problem is less frequent.
From what I've noticed is only happening in chrome and never when I use the open button.
It's very strange.
Regards,
Tarcisio Pereira

Sounds like #7136, but it's hard to guess or suggest anything without being able to reproduce the issue on different computer.

authors: amatsumiro yurydelendik


text:
Correctly order added annotations when saving or printing

the annotations must be rendered in the same order as the chronological one.
fix a bug in document.js which avoids to read a saved pdf correctly in Acrobat:
there is no need to reset the xref state: it's done in worker.js once everything
has been saved.

/botio test


text:
Fix more regressions from PR 15812

Don't dispatch "pagerendered"-events on the temporary CSS-only zooming done when drawingDelay is used (PR #15812 follow-up)
We shouldn't dispatch a "pagerendered"-event when doing temporary CSS-only zooming, but simply wait until the actual rendering is done.
While I don't believe that this regression has caused any actual bugs, dispatching duplicate events is nonetheless inconsistent and should be fixed.

Don't use partially rendered pages to generate thumbnails when drawingDelay is used (PR #15812 follow-up)
While it's slightly difficult to trigger in practice, unless the defaultZoomDelay-value is increased, it's currently possible to generate thumbnails from partially rendered pages when doing temporary CSS-only zooming.

/botio-linux preview


text:
Add normalizedTextContents function

Move the code to concatenate and normalize the contents of a page into its own function in pdf_find_controller so that it could be reused elsewhere.
This is a small part of the ongoing work to address #3172, which I decided to break off and post already as a PR so that we could start iterating on it in parts and be more agile.
There's two open questions with this patch, beyond the common "what can we name this function":

Where should this new refactored function live? It's currently still in pdf_find_controller but that might not be ideal and we might want to move stuff to a more central location (this would incur a bigger diff unfortunately).
Do we need to normalize the text for our upcoming use case as well? While the concat logic is definitely required the normalization might not be entirely necessary especially with the v flag.

This is a small part of the ongoing work to address #3172, which I decided to break off and post already as a PR so that we could start iterating on it in parts and be more agile.

Given that we don't really know what the final solution will look like yet, it's not entirely clear (at least to me) that a bunch of separate PRs is a good idea since it might lead to a lot of code churn (and changed git blame) that may or may not ultimately be necessary for the final patch(es)?

@Snuffleupagus me and @calixteman suggested @ryzokuken to break this down into multiple PRs to make reviewing easier. Another option could be to create the larger PR first (maybe as a draft, it doesn't have to be perfect) to show the full thing, then break it down into multiple PRs.

Another option could be to create the larger PR first (maybe as a draft, it doesn't have to be perfect) to show the full thing, then break it down into multiple PRs.

That sounds better, at least to me, since that could help us avoid making "unnecessary" changes along the way.

Closing this as it's subsumed by another PR.

authors: Snuffleupagus marco-c ryzokuken


text:
tabzilla broken, shows as unformatted text

When I visit platform-status.mozilla.org, I see the tabzilla as an unformatted piece of text.

On first look, the tabzilla CSS doesn't seem to be included in the build output.

Maybe caused by postcss update #294

could be related to fe4930189f7f05044c0b170bb21111174614597c ?

On first look, the tabzilla CSS doesn't seem to be included in the build output.

If that's the case, this would have been caught by the test we removed in 84d9b9deb9d1916b7c1f0996ff6f36309788b96d
I'm morphing #291 to track us re-adding a less burdensome version of that test

authors: TimAbraldes digitarald wfwalker

repo: mozilla/platatus


text:
Check root favicon.ico on host to use for favicon if not found elsewh…

…ere. r=vporof

Coverage decreased (-0.09%) to 43.804% when pulling abb1aea45cf36088daf003c6de94a507dfba1a7c on jsantell:favicon-fallback into a081c65d96705e6b06528c8707bc71f7d93c8ce5 on mozilla:master.

Coverage decreased (-0.1%) to 43.752% when pulling abb1aea45cf36088daf003c6de94a507dfba1a7c on jsantell:favicon-fallback into a081c65d96705e6b06528c8707bc71f7d93c8ce5 on mozilla:master.

Coverage decreased (-0.1%) to 43.752% when pulling 2d13aea6f43ca4097dc6d191f43bd17563b794b2 on jsantell:favicon-fallback into 96cdc2d0869de23bfc49932f6852bbf44d52860e on mozilla:master.

authors: coveralls jsantell

repo: mozilla/tofino


text:
add arctic-themed scene (fixes issue #268)

:warning: do not merge
I'm moving this work to a separate repository so it's forkable and maintainable outside of this core project, which ought to be used for only the Unity Assets Store package.

I'm moving this work to a separate repository so it's forkable and maintainable outside of this core project, which ought to be used for only the Unity Assets Store package.

repo: mozilla/unity-webvr-export


text:
Mod items not showing

Hello! I have the mod installed along with some other mods and for some reason it doesn't show me the items in the mod, but it is on my mods folder. Is there any dependency for the mod?

This has been updated, you can now see items in JEI and the creative inventory.

repo: mpbb/ironbows


text:
🛑 DBPERU is down

In af37fa8, DBPERU (https://www.dbperu.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DBPERU is back up in b87562b after 10 minutes.

repo: mperezdbperu/dbperu


text:
Added SIMD

I am opening this PR which introduces:

SIMD version of compute single-gain
use of query_change to track which terms are in the partition

Compression is slightly improved for the reason that now compute single-gain does not accumulate all the before-gains and after-gains and finally subtract, but it does a subtraction for every term.
before_move += before[q];
after_move += after[q];
...
float gain = before_move - after_move;

Instead:
float gain = 0;
...
gain += before[q] - after[q];

Confirmed that this patch is working as expected.

authors: JMMackenzie amallia


text:
underscore folder problem with github pages

The stylemark folder starting with an underscore cause problem with github pages.
Files in that folder aren't loaded when you use github pages for you documentation.

Simply add a .nojekyll file in the styleguide directory. This will solve your issue.
github blogpost

Fixed with .nojekyll file, thank you !

I had the same issue and tried adding a .nojekyll file both to the root of my Github pages repo and also within the "docs" folder where I output stylemark files for my project. Neither has worked and I get 404s on my github page for all the files in the "_stylemark" directory.
Would it be possible just to rename the directory to "stylemark" without the underscore so that all this isn't necessary to begin with?
(I experimented with manually renaming the directory and references to it which worked but isn't a good long term solution...)

I wrote the above too soon. GIthub finally recognized the file and my Stylemark github page is finally working. This was a big headache to discover the cause and how to fix though so respectfully I'd still like to request the directory be renamed if possible to help others avoid this issue in the future. Thanks.

authors: ghost kbradley spazola stefankunze

repo: mpetrovich/stylemark


text:
Banner image: crash

If an image is uploaded in the "Banner Media Type" of an Episode in the CMS, the section (Channel) breaks.
To recreate:

Upload a new image to the Banner Media Type and save it.
Go to the Channels landing page an observe results.

CMS view

Console

Front end

Thanks, fixed.

authors: chrismplus rdunk

repo: mplusmuseum/mplusmuseum-stories


text:
CSS ClassName

Iggy $el

Die CSS Classen werden ohne Leerschlag hinzugefügt.
Resultat -->
D.h. man muss immer  <--- mit Leerschlag

fixed with version 0.0.17.
83e8984d9dc6f90942f2ba55a424b70ed36da579

FYI: Tests with the new Backbone version 1.2.x are failing

authors: CitySim mpneuried tcs-apeters

repo: mpneuried/iggy


text:
Foreach in conversation results in infinite loop

When I use foreach inside a conversation I end with infinite loop of the method in which I use foreach. Code example:
`
public function askFirstname() {
$this->ask('Podaj adres strony www', function(Answer $answer) {
// Save result
$this->url = $answer->getText();
        $this->audyt = new WebsiteAudit('http://' . $this->url);
        $this->auditData = $this->audyt->auditResults;

        $this->say('No to zaczynamy.. ');
        if ($this->audyt->error) {
            $this->say($this->audyt->error);
        } else {
            $this->say('1. Zaczniemy od analizy znaczników META');
            $this->say('Tytuł strony www <title> (' . $this->auditData['metaData']['titleLen'] . ' znaków): ');// . $this->auditData['metaData']['title']);
            $this->say('Opis strony <meta ..> (' . $this->auditData['metaData']['descriptionLen'] . ' znaków): ');// . $this->auditData['metaData']['name-description']);

                $this->say('--');
                $this->say('Do poprawy:');
                foreach ($this->auditData['metaData']['errorsMeta'] as $error1) {
                    $this->say($error1);
                }

            $this->askMore1();
        }
    });
}

`

I tried with implode function and it also gives me the loop. I think that implode also use foreach.
So no way to foreach on array.

What do you mean by infinite loop?
I don't really see how this is related to BotMan.

Thank you for reply.
I mean that my bot is sending over and over the same messages.
 $this->say('No to zaczynamy.. ');
$this->say('1. Zaczniemy od analizy znaczników META');
$this->say('Tytuł strony www <title> (' . $this->auditData['metaData']['titleLen'] . ' znaków): ');
$this->say('Opis strony <meta ..> (' . $this->auditData['metaData']['descriptionLen'] . ' znaków): ');
$this->say('--');
$this->say('Do poprawy:');

and never send anything from foreach.
To stop it I have to clear the cache of laravel.
I spend few ours on that and don't know what to do next.

The same effect you can see when try to do:
for($i=0;$i<=10;$i++)
                    {
                        $this->say('test'.$i);
                    }

Which driver do you use?

If you ask about cache driver I use database with mysql configured.

Normally a loop with repeating messages sent indicates an error inside your code. Have you checked your logs?

Sorry but I don't know how to debug code inside conversation. I know that there is something wrong but can't see error message. I use laravel.
The same code run outside conversation class works fine.

Are you using ngrok or valet for your local tunnel? With ngrok there is a web interface where you see all requests. there you could check if there are 500 responses. But the errors should be in your Laravel logs too. If there is an error inside your conversation and your bot starts sending the same reply again and again, then you can clear the cache php artisan cache:clear and the responses should stop. If it doesn't it must be something else though.

ok. I found my mistake. Sorry for this.

authors: christophrumpel jozwikp mpociot

repo: mpociot/botman


text:
add record widget to recording tab

This is a milestone branch in my mind. Having this functionality in place will be a substantial step forward for ease of use. It is conceivable that this becomes resolved within the day, which is exciting. But if it doesn't, then that's ok, too.

Currently trying to track down why it is that the window crashes when "Stop Recording" is pressed on the RecordingWidget within the MainWindow....
This appears to only happen when recording at faster frame rates....
Not sure if this is related to that issue, but it is another issue that must be sorted out:
The Recording Widget had been defaulting to turning off tracking via the synchronizer:
    calibration_index = self.tab_widget.indexOf(self.calibration_widget)

this needs to be something that is managed interactively when moving between tabs.
Similarly, I want to make sure that the synchronizer unsubscribes as appropriate when moving back to the calibration tab
If the stereocalibration widget is up, then it should keep synchronizer subscribed and track frames

[ ] need to turn off all monocalibrators (unsubscribe them) when moving from Calibration tab

Need to add functionality for stereoframe to reset fps and tracking as needed...


text:
Package proposal: bytecodeviewer.vm

Package Name
bytecodeviewer
Tool Name
Bytecode Viewer
Tool's version number
2.11.2
Category
Java
Tool's authors
Konloch
Tool's description
A lightweight user-friendly Java/Android Bytecode Viewer, Decompiler and more.
Package type
SINGLE_EXE
Download URL
https://github.com/Konloch/bytecode-viewer/releases/download/v2.11.2/Bytecode-Viewer-2.11.2.jar
Download SHA256 Hash
536ad387424106083f76cd0cb7c051a22aff21f08663ba2539c11f1ddef9147f
Why is this tool a good addition?
It's great!

Testing comments

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM was just released it and to will make the project more open and maintainable.
Please check out our blog post at  and give the new installation a try.
If your issue still persists with the new installation, please reopen this.
Note: this is a default message to remove outdated issues and start with a clean slate for the next generation of FLARE VM.

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM was just released it and to will make the project more open and maintainable.
Please check out our blog post at LINK and give the new installation a try.
If your problem still persists with the new installation, please reopen this issue.
Note: this is a default message to remove outdated issues and start with a clean slate for the next generation of FLARE VM.

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM was just released it and to will make the project more open and maintainable.
Please check out our blog post at LINK and give the new installation a try.
If your problem still persists with the new installation, please report:

new tools or package installation related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Note: this is a default message to remove outdated issues and start with a clean slate for the next generation of FLARE VM.

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM was just released it and to will make the project more open and maintainable.
Please check out our blog post at LINK and give the new installation a try.
If your problem still persists with the new installation, please report:

new tools or package installation related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Note: this is a default message to remove outdated issues and start with a clean slate for the next generation of FLARE VM.

repo: mr-tz/VM-Packages


text:
Kotlin: anagram detection

@mre note that my approach is very different from yours.

Very cool solution. I dig the functional style.

authors: Fleshgrinder mre

repo: mre/the-coding-interview


text:
HMR Failures

The response from a call such as http://localhost:5000/64ef3ad1b9684d6b00d8.hot-update.json
Is being intercepted/handled by custom middleware, and returning html instead of a hmr payload.
Uncaught (in promise) SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse ()
at XMLHttpRequest.request.onreadystatechange (common.js:77)

resolved in v2.0.4

repo: mrellipse/toucan


text:
setPanelBrightness() corrupts top line when using colour depth of less than 4 bits

Hi,
I recently started experimenting with this library to see if  it would suit my application. I started with your demo test sketch, and configured it for 4 panels of 64x32. At this point I only have 1 of the 4 panels connected, so can only see x of 192-255.
I don't need much colour depth, so I configured it for only 2 bits using setPixelColorDepthBits(2), then started experimenting with how intensity is handled, by displaying a gradient and dimming the display with setPanelBrightness().
The lowest visible intensity with 2bit depth is corrupted in the top row if I use either 2 or 3 bits of colour depth (see picture).

I produced the attached image by putting the following into loop() on your test sketch (and speeding up the cycles to 200mS).
static   uint8_t b = 255;
Serial.printf("panel brightness: %u\n", b);
x = 192;
while(x != 256)
{
c = (x-192)*4;
matrix->drawFastVLine(x,0,25, c, c, c);
x++;
};
matrix->setPanelBrightness(b);
b--;
It's not a show stopper for me, as there is enough ram with this configuration to run 4 bits of colour depth, but It's a shame to waste the ram if the colour depth isn't needed.

mxconfig.clkphase = false;   fixed it... (sorry).
Thanks for a great library, looks like it will do everything I need :-)

mxconfig.clkphase = false; fixed it... (sorry).
Thanks for a great library, looks like it will do everything I need :-)


text:
Specify accept in file inputs

RapiDoc should check if a contentType is available for any given binary field in a multipart request body and use it to set the accept attribute of the input element so that the selection dialog can properly filter the files.

RapiDoc do not put any constraints on the UI, even when it is specified in the spec.
The reason for doing so is, coz, many of our users/developers use it for testing their APIs. Therefore it allows user to provide incorrect values and test out how the API responses are received.
It is not the goal of RapiDoc to become a perfect client for the APIs. Instead it helps in quick and dirty testing of APIs

The accept attribute doesn't validate the types of the selected files; it provides hints for browsers to guide users towards selecting the correct file types. It is still possible (in most cases) for users to toggle an option in the file chooser that makes it possible to override this and select any file they wish, and then choose incorrect file types.


text:
Newer GPUs needs additional nvcc arguments

Just for your information, some newer GPUs needs the following code in order to work.
NVCCFLAGS += -gencode arch=compute_80,code=sm_80
I am not familiar enough with Makefiles to implement a more flexible solution, so I leave that to you guys.

Hey, can you tell us more about the issues you had on your newer GPU? And with which GPU you encountered issues?
We are using the current NVCCFLAGS on GPUs from the end of 2022, and see no issues there.

Hi, so we have 2 machines with the same generation of Nvidia GPUs, one of them is running CentOS 7, and the other one is running Ubuntu 22.04.3 LTS.
The CentOS 7 one is the one with the problem. I also have to modify the Makefile to include lapacke. I understand that CentOS is an outdated OS at this point, but I though I should let you guys know anyway.
On the CentOS machine, the gcc is 11.4.0, GPU driver is 515.65.01, CUDA is 11.7.
Thanks!

Hmm, do you mind posting the ouput of nvidia-smi and nvidia-smi -q on a system where you had to change the NVCCFLAGS? That might help us understand the underlying issue

Fri Mar 22 14:19:16 2024
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A6000    On   | 00000000:17:00.0 Off |                  Off |
| 30%   44C    P2    98W / 300W |  25100MiB / 49140MiB |     22%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA RTX A6000    On   | 00000000:31:00.0 Off |                  Off |
| 30%   58C    P2   164W / 300W |  31131MiB / 49140MiB |     73%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA RTX A6000    On   | 00000000:B1:00.0 Off |                  Off |> Fri Mar 22 14:19:16 2024
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A6000    On   | 00000000:17:00.0 Off |                  Off |
| 30%   44C    P2    98W / 300W |  25100MiB / 49140MiB |     22%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA RTX A6000    On   | 00000000:31:00.0 Off |                  Off |
| 30%   58C    P2   164W / 300W |  31131MiB / 49140MiB |     73%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA RTX A6000    On   | 00000000:B1:00.0 Off |                  Off |
| 30%   28C    P8    31W / 300W |  12952MiB / 49140MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  NVIDIA RTX A6000    On   | 00000000:CA:00.0 Off |                  Off |
| 30%   41C    P2    97W / 300W |  19541MiB / 49140MiB |     40%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
| 30%   28C    P8    31W / 300W |  12952MiB / 49140MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  NVIDIA RTX A6000    On   | 00000000:CA:00.0 Off |                  Off |
| 30%   41C    P2    97W / 300W |  19541MiB / 49140MiB |     40%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Timestamp                                 : Tue Apr  2 16:47:53 2024
Driver Version                            : 515.65.01
CUDA Version                              : 11.7

Attached GPUs                             : 4
GPU 00000000:17:00.0
    Product Name                          : NVIDIA RTX A6000
    Product Brand                         : NVIDIA RTX
    Product Architecture                  : Ampere
    Display Mode                          : Disabled
    Display Active                        : Disabled
    Persistence Mode                      : Enabled
    MIG Mode
        Current                           : N/A
        Pending                           : N/A
    Accounting Mode                       : Disabled
    Accounting Mode Buffer Size           : 4000
    Driver Model
        Current                           : N/A
        Pending                           : N/A
    Serial Number                         : 1324521059351
    GPU UUID                              : GPU-ca78cd83-364f-e645-8bd2-33390e5a7aef
    Minor Number                          : 0
    VBIOS Version                         : 94.02.5C.00.02
    MultiGPU Board                        : No
    Board ID                              : 0x1700
    GPU Part Number                       : 900-5G133-1700-000
    Module ID                             : 0
    Inforom Version
        Image Version                     : G133.0500.00.05
        OEM Object                        : 2.0
        ECC Object                        : 6.16
        Power Management Object           : N/A
    GPU Operation Mode
        Current                           : N/A
        Pending                           : N/A
    GSP Firmware Version                  : N/A
    GPU Virtualization Mode
        Virtualization Mode               : None
        Host VGPU Mode                    : N/A
    IBMNPU
        Relaxed Ordering Mode             : N/A
    PCI
        Bus                               : 0x17
        Device                            : 0x00
        Domain                            : 0x0000
        Device Id                         : 0x223010DE
        Bus Id                            : 00000000:17:00.0
        Sub System Id                     : 0x145910DE
        GPU Link Info
            PCIe Generation
                Max                       : 4
                Current                   : 1
            Link Width
                Max                       : 16x
                Current                   : 16x
        Bridge Chip
            Type                          : N/A
            Firmware                      : N/A
        Replays Since Reset               : 0
        Replay Number Rollovers           : 0
        Tx Throughput                     : 0 KB/s
        Rx Throughput                     : 0 KB/s
    Fan Speed                             : 30 %
    Performance State                     : P8
    Clocks Throttle Reasons
        Idle                              : Active
        Applications Clocks Setting       : Not Active
        SW Power Cap                      : Not Active
        HW Slowdown                       : Not Active
            HW Thermal Slowdown           : Not Active
            HW Power Brake Slowdown       : Not Active
        Sync Boost                        : Not Active
        SW Thermal Slowdown               : Not Active
        Display Clock Setting             : Not Active
    FB Memory Usage
        Total                             : 49140 MiB
        Reserved                          : 454 MiB
        Used                              : 26786 MiB
        Free                              : 21899 MiB
    BAR1 Memory Usage
        Total                             : 256 MiB
        Used                              : 8 MiB
        Free                              : 248 MiB
    Compute Mode                          : Default
    Utilization
        Gpu                               : 0 %
        Memory                            : 0 %
        Encoder                           : 0 %
        Decoder                           : 0 %
    Encoder Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    FBC Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    Ecc Mode
        Current                           : Disabled
        Pending                           : Disabled
    ECC Errors
        Volatile
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
        Aggregate
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
    Retired Pages
        Single Bit ECC                    : N/A
        Double Bit ECC                    : N/A
        Pending Page Blacklist            : N/A
    Remapped Rows
        Correctable Error                 : 0
        Uncorrectable Error               : 0
        Pending                           : No
        Remapping Failure Occurred        : No
        Bank Remap Availability Histogram
            Max                           : 192 bank(s)
            High                          : 0 bank(s)
            Partial                       : 0 bank(s)
            Low                           : 0 bank(s)
            None                          : 0 bank(s)
    Temperature
        GPU Current Temp                  : 30 C
        GPU Shutdown Temp                 : 98 C
        GPU Slowdown Temp                 : 95 C
        GPU Max Operating Temp            : 93 C
        GPU Target Temperature            : 84 C
        Memory Current Temp               : N/A
        Memory Max Operating Temp         : N/A
    Power Readings
        Power Management                  : Supported
        Power Draw                        : 29.92 W
        Power Limit                       : 300.00 W
        Default Power Limit               : 300.00 W
        Enforced Power Limit              : 300.00 W
        Min Power Limit                   : 100.00 W
        Max Power Limit                   : 300.00 W
    Clocks
        Graphics                          : 210 MHz
        SM                                : 210 MHz
        Memory                            : 405 MHz
        Video                             : 555 MHz
    Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Default Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Max Clocks
        Graphics                          : 2100 MHz
        SM                                : 2100 MHz
        Memory                            : 8001 MHz
        Video                             : 1950 MHz
    Max Customer Boost Clocks
        Graphics                          : N/A
    Clock Policy
        Auto Boost                        : N/A
        Auto Boost Default                : N/A
    Voltage
        Graphics                          : 750.000 mV
    Processes
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 57888
            Type                          : C
            Name                          : python
            Used GPU Memory               : 3151 MiB
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 67599
            Type                          : C
            Name                          : /usr/local/MATLAB/R2022b/bin/glnxa64/MATLAB
            Used GPU Memory               : 4997 MiB
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 126377
            Type                          : C
            Name                          : /usr/local/MATLAB/R2022b/bin/glnxa64/MATLAB
            Used GPU Memory               : 18633 MiB

GPU 00000000:31:00.0
    Product Name                          : NVIDIA RTX A6000
    Product Brand                         : NVIDIA RTX
    Product Architecture                  : Ampere
    Display Mode                          : Disabled
    Display Active                        : Disabled
    Persistence Mode                      : Enabled
    MIG Mode
        Current                           : N/A
        Pending                           : N/A
    Accounting Mode                       : Disabled
    Accounting Mode Buffer Size           : 4000
    Driver Model
        Current                           : N/A
        Pending                           : N/A
    Serial Number                         : 1324521012524
    GPU UUID                              : GPU-676b4b2c-cd66-9d9f-f771-5494e6192f41
    Minor Number                          : 1
    VBIOS Version                         : 94.02.5C.00.02
    MultiGPU Board                        : No
    Board ID                              : 0x3100
    GPU Part Number                       : 900-5G133-1700-000
    Module ID                             : 0
    Inforom Version
        Image Version                     : G133.0500.00.05
        OEM Object                        : 2.0
        ECC Object                        : 6.16
        Power Management Object           : N/A
    GPU Operation Mode
        Current                           : N/A
        Pending                           : N/A
    GSP Firmware Version                  : N/A
    GPU Virtualization Mode
        Virtualization Mode               : None
        Host VGPU Mode                    : N/A
    IBMNPU
        Relaxed Ordering Mode             : N/A
    PCI
        Bus                               : 0x31
        Device                            : 0x00
        Domain                            : 0x0000
        Device Id                         : 0x223010DE
        Bus Id                            : 00000000:31:00.0
        Sub System Id                     : 0x145910DE
        GPU Link Info
            PCIe Generation
                Max                       : 4
                Current                   : 4
            Link Width
                Max                       : 16x
                Current                   : 16x
        Bridge Chip
            Type                          : N/A
            Firmware                      : N/A
        Replays Since Reset               : 0
        Replay Number Rollovers           : 0
        Tx Throughput                     : 5000 KB/s
        Rx Throughput                     : 27000 KB/s
    Fan Speed                             : 30 %
    Performance State                     : P2
    Clocks Throttle Reasons
        Idle                              : Not Active
        Applications Clocks Setting       : Not Active
        SW Power Cap                      : Not Active
        HW Slowdown                       : Not Active
            HW Thermal Slowdown           : Not Active
            HW Power Brake Slowdown       : Not Active
        Sync Boost                        : Not Active
        SW Thermal Slowdown               : Not Active
        Display Clock Setting             : Not Active
    FB Memory Usage
        Total                             : 49140 MiB
        Reserved                          : 454 MiB
        Used                              : 31087 MiB
        Free                              : 17598 MiB
    BAR1 Memory Usage
        Total                             : 256 MiB
        Used                              : 6 MiB
        Free                              : 250 MiB
    Compute Mode                          : Default
    Utilization
        Gpu                               : 25 %
        Memory                            : 13 %
        Encoder                           : 0 %
        Decoder                           : 0 %
    Encoder Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    FBC Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    Ecc Mode
        Current                           : Disabled
        Pending                           : Disabled
    ECC Errors
        Volatile
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
        Aggregate
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
    Retired Pages
        Single Bit ECC                    : N/A
        Double Bit ECC                    : N/A
        Pending Page Blacklist            : N/A
    Remapped Rows
        Correctable Error                 : 0
        Uncorrectable Error               : 0
        Pending                           : No
        Remapping Failure Occurred        : No
        Bank Remap Availability Histogram
            Max                           : 192 bank(s)
            High                          : 0 bank(s)
            Partial                       : 0 bank(s)
            Low                           : 0 bank(s)
            None                          : 0 bank(s)
    Temperature
        GPU Current Temp                  : 50 C
        GPU Shutdown Temp                 : 98 C
        GPU Slowdown Temp                 : 95 C
        GPU Max Operating Temp            : 93 C
        GPU Target Temperature            : 84 C
        Memory Current Temp               : N/A
        Memory Max Operating Temp         : N/A
    Power Readings
        Power Management                  : Supported
        Power Draw                        : 103.47 W
        Power Limit                       : 300.00 W
        Default Power Limit               : 300.00 W
        Enforced Power Limit              : 300.00 W
        Min Power Limit                   : 100.00 W
        Max Power Limit                   : 300.00 W
    Clocks
        Graphics                          : 1800 MHz
        SM                                : 1800 MHz
        Memory                            : 7600 MHz
        Video                             : 1590 MHz
    Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Default Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Max Clocks
        Graphics                          : 2100 MHz
        SM                                : 2100 MHz
        Memory                            : 8001 MHz
        Video                             : 1950 MHz
    Max Customer Boost Clocks
        Graphics                          : N/A
    Clock Policy
        Auto Boost                        : N/A
        Auto Boost Default                : N/A
    Voltage
        Graphics                          : 931.250 mV
    Processes
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 57888
            Type                          : C
            Name                          : python
            Used GPU Memory               : 8595 MiB
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 107143
            Type                          : C
            Name                          : /usr/local/MATLAB/R2022b/bin/glnxa64/MATLAB
            Used GPU Memory               : 22489 MiB

GPU 00000000:B1:00.0
    Product Name                          : NVIDIA RTX A6000
    Product Brand                         : NVIDIA RTX
    Product Architecture                  : Ampere
    Display Mode                          : Disabled
    Display Active                        : Disabled
    Persistence Mode                      : Enabled
    MIG Mode
        Current                           : N/A
        Pending                           : N/A
    Accounting Mode                       : Disabled
    Accounting Mode Buffer Size           : 4000
    Driver Model
        Current                           : N/A
        Pending                           : N/A
    Serial Number                         : 1324521060624
    GPU UUID                              : GPU-40ce844c-3875-5de5-f4e3-dbbbe31092d7
    Minor Number                          : 2
    VBIOS Version                         : 94.02.5C.00.02
    MultiGPU Board                        : No
    Board ID                              : 0xb100
    GPU Part Number                       : 900-5G133-1700-000
    Module ID                             : 0
    Inforom Version
        Image Version                     : G133.0500.00.05
        OEM Object                        : 2.0
        ECC Object                        : 6.16
        Power Management Object           : N/A
    GPU Operation Mode
        Current                           : N/A
        Pending                           : N/A
    GSP Firmware Version                  : N/A
    GPU Virtualization Mode
        Virtualization Mode               : None
        Host VGPU Mode                    : N/A
    IBMNPU
        Relaxed Ordering Mode             : N/A
    PCI
        Bus                               : 0xB1
        Device                            : 0x00
        Domain                            : 0x0000
        Device Id                         : 0x223010DE
        Bus Id                            : 00000000:B1:00.0
        Sub System Id                     : 0x145910DE
        GPU Link Info
            PCIe Generation
                Max                       : 4
                Current                   : 1
            Link Width
                Max                       : 16x
                Current                   : 16x
        Bridge Chip
            Type                          : N/A
            Firmware                      : N/A
        Replays Since Reset               : 0
        Replay Number Rollovers           : 0
        Tx Throughput                     : 0 KB/s
        Rx Throughput                     : 0 KB/s
    Fan Speed                             : 30 %
    Performance State                     : P8
    Clocks Throttle Reasons
        Idle                              : Active
        Applications Clocks Setting       : Not Active
        SW Power Cap                      : Not Active
        HW Slowdown                       : Not Active
            HW Thermal Slowdown           : Not Active
            HW Power Brake Slowdown       : Not Active
        Sync Boost                        : Not Active
        SW Thermal Slowdown               : Not Active
        Display Clock Setting             : Not Active
    FB Memory Usage
        Total                             : 49140 MiB
        Reserved                          : 454 MiB
        Used                              : 12952 MiB
        Free                              : 35733 MiB
    BAR1 Memory Usage
        Total                             : 256 MiB
        Used                              : 4 MiB
        Free                              : 252 MiB
    Compute Mode                          : Default
    Utilization
        Gpu                               : 0 %
        Memory                            : 0 %
        Encoder                           : 0 %
        Decoder                           : 0 %
    Encoder Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    FBC Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    Ecc Mode
        Current                           : Disabled
        Pending                           : Disabled
    ECC Errors
        Volatile
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
        Aggregate
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
    Retired Pages
        Single Bit ECC                    : N/A
        Double Bit ECC                    : N/A
        Pending Page Blacklist            : N/A
    Remapped Rows
        Correctable Error                 : 0
        Uncorrectable Error               : 0
        Pending                           : No
        Remapping Failure Occurred        : No
        Bank Remap Availability Histogram
            Max                           : 192 bank(s)
            High                          : 0 bank(s)
            Partial                       : 0 bank(s)
            Low                           : 0 bank(s)
            None                          : 0 bank(s)
    Temperature
        GPU Current Temp                  : 29 C
        GPU Shutdown Temp                 : 98 C
        GPU Slowdown Temp                 : 95 C
        GPU Max Operating Temp            : 93 C
        GPU Target Temperature            : 84 C
        Memory Current Temp               : N/A
        Memory Max Operating Temp         : N/A
    Power Readings
        Power Management                  : Supported
        Power Draw                        : 31.81 W
        Power Limit                       : 300.00 W
        Default Power Limit               : 300.00 W
        Enforced Power Limit              : 300.00 W
        Min Power Limit                   : 100.00 W
        Max Power Limit                   : 300.00 W
    Clocks
        Graphics                          : 0 MHz
        SM                                : 0 MHz
        Memory                            : 405 MHz
        Video                             : 555 MHz
    Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Default Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Max Clocks
        Graphics                          : 2100 MHz
        SM                                : 2100 MHz
        Memory                            : 8001 MHz
        Video                             : 1950 MHz
    Max Customer Boost Clocks
        Graphics                          : N/A
    Clock Policy
        Auto Boost                        : N/A
        Auto Boost Default                : N/A
    Voltage
        Graphics                          : 0.000 mV
    Processes
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 126233
            Type                          : C
            Name                          : /opt/anaconda3/envs/torch-env2/bin/python
            Used GPU Memory               : 12949 MiB

GPU 00000000:CA:00.0
    Product Name                          : NVIDIA RTX A6000
    Product Brand                         : NVIDIA RTX
    Product Architecture                  : Ampere
    Display Mode                          : Disabled
    Display Active                        : Disabled
    Persistence Mode                      : Enabled
    MIG Mode
        Current                           : N/A
        Pending                           : N/A
    Accounting Mode                       : Disabled
    Accounting Mode Buffer Size           : 4000
    Driver Model
        Current                           : N/A
        Pending                           : N/A
    Serial Number                         : 1324521060341
    GPU UUID                              : GPU-83f78936-a6e1-3cb8-b6ab-41dd1af7bbd9
    Minor Number                          : 3
    VBIOS Version                         : 94.02.5C.00.02
    MultiGPU Board                        : No
    Board ID                              : 0xca00
    GPU Part Number                       : 900-5G133-1700-000
    Module ID                             : 0
    Inforom Version
        Image Version                     : G133.0500.00.05
        OEM Object                        : 2.0
        ECC Object                        : 6.16
        Power Management Object           : N/A
    GPU Operation Mode
        Current                           : N/A
        Pending                           : N/A
    GSP Firmware Version                  : N/A
    GPU Virtualization Mode
        Virtualization Mode               : None
        Host VGPU Mode                    : N/A
    IBMNPU
        Relaxed Ordering Mode             : N/A
    PCI
        Bus                               : 0xCA
        Device                            : 0x00
        Domain                            : 0x0000
        Device Id                         : 0x223010DE
        Bus Id                            : 00000000:CA:00.0
        Sub System Id                     : 0x145910DE
        GPU Link Info
            PCIe Generation
                Max                       : 4
                Current                   : 1
            Link Width
                Max                       : 16x
                Current                   : 16x
        Bridge Chip
            Type                          : N/A
            Firmware                      : N/A
        Replays Since Reset               : 0
        Replay Number Rollovers           : 0
        Tx Throughput                     : 0 KB/s
        Rx Throughput                     : 0 KB/s
    Fan Speed                             : 30 %
    Performance State                     : P8
    Clocks Throttle Reasons
        Idle                              : Active
        Applications Clocks Setting       : Not Active
        SW Power Cap                      : Not Active
        HW Slowdown                       : Not Active
            HW Thermal Slowdown           : Not Active
            HW Power Brake Slowdown       : Not Active
        Sync Boost                        : Not Active
        SW Thermal Slowdown               : Not Active
        Display Clock Setting             : Not Active
    FB Memory Usage
        Total                             : 49140 MiB
        Reserved                          : 454 MiB
        Used                              : 19389 MiB
        Free                              : 29296 MiB
    BAR1 Memory Usage
        Total                             : 256 MiB
        Used                              : 6 MiB
        Free                              : 250 MiB
    Compute Mode                          : Default
    Utilization
        Gpu                               : 0 %
        Memory                            : 0 %
        Encoder                           : 0 %
        Decoder                           : 0 %
    Encoder Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    FBC Stats
        Active Sessions                   : 0
        Average FPS                       : 0
        Average Latency                   : 0
    Ecc Mode
        Current                           : Disabled
        Pending                           : Disabled
    ECC Errors
        Volatile
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
        Aggregate
            SRAM Correctable              : N/A
            SRAM Uncorrectable            : N/A
            DRAM Correctable              : N/A
            DRAM Uncorrectable            : N/A
    Retired Pages
        Single Bit ECC                    : N/A
        Double Bit ECC                    : N/A
        Pending Page Blacklist            : N/A
    Remapped Rows
        Correctable Error                 : 0
        Uncorrectable Error               : 0
        Pending                           : No
        Remapping Failure Occurred        : No
        Bank Remap Availability Histogram
            Max                           : 192 bank(s)
            High                          : 0 bank(s)
            Partial                       : 0 bank(s)
            Low                           : 0 bank(s)
            None                          : 0 bank(s)
    Temperature
        GPU Current Temp                  : 28 C
        GPU Shutdown Temp                 : 98 C
        GPU Slowdown Temp                 : 95 C
        GPU Max Operating Temp            : 93 C
        GPU Target Temperature            : 84 C
        Memory Current Temp               : N/A
        Memory Max Operating Temp         : N/A
    Power Readings
        Power Management                  : Supported
        Power Draw                        : 20.79 W
        Power Limit                       : 300.00 W
        Default Power Limit               : 300.00 W
        Enforced Power Limit              : 300.00 W
        Min Power Limit                   : 100.00 W
        Max Power Limit                   : 300.00 W
    Clocks
        Graphics                          : 0 MHz
        SM                                : 0 MHz
        Memory                            : 405 MHz
        Video                             : 555 MHz
    Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Default Applications Clocks
        Graphics                          : 1800 MHz
        Memory                            : 8001 MHz
    Max Clocks
        Graphics                          : 2100 MHz
        SM                                : 2100 MHz
        Memory                            : 8001 MHz
        Video                             : 1950 MHz
    Max Customer Boost Clocks
        Graphics                          : N/A
    Clock Policy
        Auto Boost                        : N/A
        Auto Boost Default                : N/A
    Voltage
        Graphics                          : 0.000 mV
    Processes
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 8753
            Type                          : C
            Name                          : /opt/anaconda3/envs/torch-env2/bin/python
            Used GPU Memory               : 981 MiB
        GPU instance ID                   : N/A
        Compute instance ID               : N/A
        Process ID                        : 75196
            Type                          : C
            Name                          : /usr/local/MATLAB/R2022b/bin/glnxa64/MATLAB
            Used GPU Memory               : 18405 MiB```

I forgot to include the above nvidia-smi -q output.

Very strange, we have GPUs that are also from that time frame and do not need to change the NVCCFLAGS. Normally, CUDA should handle that by default and generate appropriate code, and your CUDA version definitely supports the A6000.
Still, I think we should leave this to CUDA by default.
By the way, you do not need to edit the Makefile for this: If you create a file called Makefile.local with contents
NVCCFLAGS += -gencode arch=compute_80,code=sm_80

it should work as well.

Thanks for the tip.
I think it might has to do with the CentOS as well. It's just old and weird at this point.

authors: Zhitao-Li hcmh

repo: mrirecon/bart