Bars are not filled in according to value

Describe the bug
Bars are not filled in according to value:

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
The bars are filled in according to value:

Informations (please complete the following information):

Bubble Card version 2.0.1
Home Assistant version 2024.6

Additional context
number domain does not work, input_number domain does work normal
Thank you! 🍻

I have this myself, fans are very inconsistent and don't set state either.

Hi, this is because the sliders are currently supporting only lights, covers, media players and input numbers so this is expected.
But I will add more supported entities soon!

Closed as this is expected behaviour.
note: Looking forward to the update where this will be supported! :)

Hi! I've added an experimental support for number entities in v2.0.2, can you tell me if it's working correctly?
https://github.com/Clooos/Bubble-Card/releases/tag/v2.0.2

Fans are working great. I dunno if I like the slider been filled whilst it's off, maybe that could be a toggle? No dire need was just to mention.
I tested numbers for you as well and they work fine. Correctly sets the correct number. Toggle doesn't work with it but that was to be expected. Maybe the toggle service call could reset to min/max of the number entity.
Smashing work!


Table.load_sql hangs

When columns in the source sql table have changed, then atoti load_sql hangs indefinitely.
Expected result: finish execution and create a record in the loading report saying there were issues loading the data.
--
Steps to reproduce

Create a table with a predefined list of columns
Attempt to load data from an sql db using table.load_sql(sql statement)

Actual Result
The cell with table.load_sql never finishes
In the log there is a message saying that number of columns in the source is x versus y in the table.
Expected result
finish execution and say “127654 records failed loading, check loading report”

Hello,
Thanks for the issue. I did not managed to reproduce this.

Which version of atoti are you using ? I'm not able to reproduce this in 0.6.2.
Are all the names in sql and atoti table different ? Can you share the schema of the atoti and sql table ?
Can your share the logs ?

Closing because we couldn't reproduce. Feel free to reopen if the issue is still there.


Dynamically produce a chronologically-sorted index page for guides

What is the issue?
Currently, the index page for guides is manually generated and has minimal information eg. https://docs.dagger.io/sdk/go/275922/guides
We intend to centralize all the guides under a new "Tutorials" primary node in the navigation tree.
Ideally this Tutorials page should hold a dynamically generated index with the following characteristics:

Chronologically sorted
For each guide, display title, author, date of publication, abstract (maybe?) and tags
Allow filtering of listed items by tag eg. view only guides with tag go

Closing as duplicate of #4581

@crjm does the new guides index already implement the requirement in https://github.com/dagger/dagger/issues/4628? It seems to be Docusaurus metadata.

Yep, the index is sorted based on the date in the docs metadata.


Added necessary changes to use ZFP in Kripke and RAJA

Changes to cmake for integration with Kripke/RAJA
Made zfp::array1::pointer constructor public to use it in Kripke
Made ctor for zfp::arrayN::pointer public and set reference_t to zfp::arrayN::reference.
Added zfp::array::pointer::dims, zfp::array::pointer::size(), zfp::array::pointer::pointer(std::nullptr_t)

Codecov Report

Merging #72 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #72   +/-   ##
========================================
  Coverage    90.34%   90.34%
========================================
  Files           64       64
  Lines         3448     3448
========================================
  Hits          3115     3115
  Misses         333      333

Impacted Files
Coverage Δ

array/zfp/pointer2.h
100% <ø> (ø)
:arrow_up:

array/zfp/pointer3.h
100% <ø> (ø)
:arrow_up:

array/zfp/pointer1.h
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 047da67...f02535e. Read the comment docs.

Given the extra method on pointer which should not make it to master and the fact that I started working on the ARC branch, I will close this pull request until further notice.

I'd be happy to discuss this further and make sure that we both agree on what changes are needed, if any.  I'm hoping to consolidate some redundant zfp/ARC code.  For instance, make pointer templated on the surrounding container type (e.g., fixed- or variable-rate array).  You'll notice that pointer and vpointer are identical except for the reference to the underlying array.  The same applies to references and iterators.  I would hold off on pull requests until this has been ironed out.  Let's talk offline about any changes needed for Kripke/RAJA.


ReDoS in jspdf

Hi,
I would like to report a Regular Expression Denial of Service (REDoS) vulnerability in jspdf.
It allows cause a denial of service when adding images.
You can execute the code below to reproduce the vulnerability.
const fs = require("fs");
const { jsPDF } = require("jspdf")

function build_blank(n) {
var ret = "data:/"
for (var i = 0; i < n; i++) {
ret += "charset="
}
return ret + "!";
}

const doc = new jsPDF();
doc.text("Hello world1111!", 10, 10);

var imageData = "data:image/png;base64,"

var Octocat = fs.readFileSync("psb.png", { encoding: "latin1" });
doc.addImage(build_blank(30) + imageData, "test", 10, 40, 180, 180, undefined, "SLOW");

doc.save("a4ffff.pdf"); // will save the file in the current working directory
console.log("type:" + typeof(doc.addImage))

Best,
Yeting Li

Thanks for the issue report. I think we need to fix this regexp. Could you prepare a PR?

Thanks for the issue report. I think we need to fix this regexp. Could you prepare a PR?

Thank you for your reply, I'd be happy to oblige.

Fixed in #3091.


[Bug] can't resize window when close dialog appears.

Describe the bug
Sometimes I move the window to see the content behind it. but if I click close the window and did not save changes the dialog will appear, and I can't move the window to click on the dialog buttons.
Screenshots

Desktop (please complete the following information):

OS Name: Microsoft Windows 10 Pro Version 10.0.19044 Build 19044
Notepads Version: v<IP_ADDRESS>

same with setting dialog menu.

In case you don't know, there is a portion of the title bar which is reserved by the system that you can drag anytime you want:


Use a sentence as input

Hi, thank you for your great work. As mentioned in the paper, the input is the whole document, what about a sentence is given as the input? Is it OK? Thanks.

Hello. The input is a title and abstract. You can try a sentence but no guarantees. I recommend you use the follow-up model instead. SPECTER: https://github.com/allenai/specter
It's higher quality and easier to use. It even has an API.


Auto insert custom title on weekly, monthly, and yearly calendars?

I just saw "Daily weekly monthly yearly journal implementation" #143
Is there anyway to have something like "#+title: MONTH YEAR" or "#+title: Week No. YEAR" automatically inserted upon new file creation?
Many thanks in advance!

Not at the moment. I will add something.
anthrolisp<EMAIL_ADDRESS>writes:

I just saw "Daily weekly monthly yearly journal implementation #143": #143.
Is there anyway to have something like "#+title: MONTH YEAR" or "#+title: Week No. YEAR" automatically inserted upon new file creation?
Many thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you!
Somewhat related question: with  setq org-journal-file-type set to weekly, is it possible to have org-journal create all 7 days of the week when creating the file? I like to plan my week in advance, and being able to see the whole week and move items around in the file would be greatly appreciated. Thanks again!

You should be able to create future entries through the calendar, or org-journal-new-entry.

is it possible to have org-journal create all 7 days of the week when creating the file?

Currently, it is only possible to insert one future journal entry at a time. But somehow I like that idea.

@bastibe Should we add a new defcustom holding a function (user needs to write it) returning a string to be inserted at the top of new journal file. This would also solve #94

We already have an org-journal-after-entry-create-hook, and org-journal-date-format can already be a function. I suppose we could add an org-journal-new-file-hook or something like that. However, this function would most likely contain some pretty complicated code, as it would probably need to extract the file's date, and behave differently for daily, weekly, or monthly files. And if it needs to be complex already, one might as well add that one conditional, and use org-journal-after-entry-create-hook instead, but trigger only on recently-created files.
In summary, I would tentatively reject adding a new hook for this, on the grounds that there is no easy way of using that hook that wouldn't be similarly easy with the existing hook. Maybe a section in the README that explains how to do this with org-journal-after-entry-create-hook would be a more appropriate solution.

@cslux   I have used a bit of Howard Abrams code  https://github.com/howardabrams/dot-files  to use the emacs template system to add the headers to each new journal file.
(defun org-rename-header (label)   "Rename the current section's header to LABEL, and moves the point to the end of the line."   (interactive (list                 (read-string "Header: "                              (substring-no-properties (org-get-heading t t t t)))))   (org-back-to-heading)   (replace-string (org-get-heading t t t t) label))

It's also minimal work to manually enter a title for 1 (yearly), 12 (monthly), or even 52 (weekly) files a year.

Using org-journal-date-format is a good idea.
I will add this to the readme. Here is a working example.
(defun org-journal-date-format-func (time)
  "Custom function to insert journal date header,
and some custom text on a newly created journal file."
  (when (= (buffer-size) 0)
    (insert
     (pcase org-journal-file-type
       (`daily "#+TITLE: Daily Journal")
       (`weekly "#+TITLE: Weekly Journal")
       (`monthly "#+TITLE: Monthly Journal")
       (`yearly "#+TITLE: Yearly Journal"))))
  (concat org-journal-date-prefix (format-time-string "%A, %x" time)))

(setq org-journal-date-format 'org-journal-date-format-func)

I used the org-journal-date-format-func suggested above; that is,
(defun org-journal-date-format-func (time)
  "Custom function to insert journal date header,
and some custom text on a newly created journal file."
  (when (= (buffer-size) 0)
    (insert
     (pcase org-journal-file-type
       (`daily "#+TITLE: Daily Journal")
       (`weekly "#+TITLE: Weekly Journal")
       (`monthly "#+TITLE: Monthly Journal")
       (`yearly "#+TITLE: Yearly Journal"))))
  (concat org-journal-date-prefix (format-time-string "%A, %x" time)))

(setq org-journal-date-format 'org-journal-date-format-func)

When I set (org-journal-file-type 'weekly), I get correct entries in the journal file, which is:
#+TITLE: Weekly Journal

* Tuesday, 2019-06-25
:PROPERTIES:
:CREATED:  20190625
:END:
** 19:33

I also get correct entries in the journal file when I set org-journal-file-type to 'monthly, or 'yearly.
However, when I set   (org-journal-file-type 'daily), I get the following incorrect entry in the journal file:
* Tuesday, 2019-06-25#+TITLE: Daily Journal

** 19:40

To get around this error, in org-journal.el, at line 472, I added 4 lines of code to the function org-journal-new-entry, as shown below:
      ;; Create new journal entry if there isn't one.
      (let ((entry-header
             (if (functionp org-journal-date-format)
                 (funcall org-journal-date-format time)
               (concat org-journal-date-prefix
                       (format-time-string org-journal-date-format time)))))
        (goto-char (point-min))
        (unless (search-forward entry-header nil t)
          ;; Insure we insert the new journal header at the correct location
          ;; ======= I ADDED THE FOLLOWING 4 LINES ==========
          (if (org-journal-daily-p)
              (goto-char (point-max))
              (forward-line)
            )
          ;; ========================================
          (unless (org-journal-daily-p)
            (let ((date (decode-time time))
                  (dates (sort (org-journal-file->calendar-dates (buffer-file-name))
                               (lambda (a b)
                                 (calendar-date-compare (list b) (list a)))))
                  found)

With this addition, I get the correct entry in the journal file, which is:
#+TITLE: Daily Journal

* Tuesday, 2019-06-25
** 19:51 (07:51 PM)

@sharad-shrestha Thank you! Should be fixed with 2135c5f.

Thank you @cslux .
Now, when my journal directory does not contain any files, insertion of daily custom header works fine, with the output file 20190626 containing:
#+TITLE: Daily Journal

* Wednesday, 2019-06-26
** 10:48 (10:48 AM)

If my journal directory already contains file 20190625 with the following contents:
#+TITLE: Daily Journal

* Tuesday, 2019-06-25
** 10:48 (10:48 AM)

and I run C-c C-j, it creates a new daily journal file 20190626 with correct contents:
#+TITLE: Daily Journal

* Wednesday, 2019-06-26
** 10:48 (10:48 AM)

However, then the program proceeds to search for TODO headers on the previous daily journal file, at which point it generates error with the following error messages:
Debugger entered--Lisp error: (error "Before first headline at position 1 in buffer 20190625")
  signal(error ("Before first headline at position 1 in buffer 20190625"))
  error("Before first headline at position %d in buffer %s" 1 #<buffer 20190625>)
  (condition-case nil (outline-back-to-heading invisible-ok) (error (error "Before first headline at position %d in buffer %s" (point) (current-buffer))))
  org-back-to-heading()
...
...

If I remove the title header from the previous day's journal file 20100625, which now looks like the following:
* Tuesday, 2019-06-25
** 10:48 (10:48 AM)

and I run C-c C-j, it creates new daily journal file 20190626 with correct contents:
#+TITLE: Daily Journal

* Wednesday, 2019-06-26
** 10:48 (10:48 AM)

So, it looks like the program is expecting the first line in the previous day's journal file to contain the header line of the form * Tuesday, 2019-06-26.

@sharad-shrestha Should be fixed with the commit c522039.
Sorry :-)
Thanks, Chris!

Thank you, @cslux .
The custom title for daily, weekly, monthly, and yearly org-journal-file-type all work correctly now when I execute C-c C-j command.
When I execute C-u C-c C-j, I observed the following behavior for daily, weekly, monthly, and yearly org-journal-file-type.  If the journal file for the day (or week, month, or year) does not exist, it creates a new file with the following entry (shown below for daily case):
#+TITLE: Daily Journal

* Wednesday, 2019-06-26

It behaves similarly for weekly, monthly, and yearly org-journal-file-type.
I think, may be a better response is for the program to simply generate a message (in the echo area) informing that the file does not exist (and not create a new file).
If the journal file for the day (for org-journal-file-type='daily) already exists and contains the following entries:
#+TITLE: Daily Journal

* Wednesday, 2019-06-26
** 23:17 (11:17 PM) Some text

and if I execute the command C-u C-c C-j, it opens up the file without adding any new entry, which is as expected.
If the journal file for the week (for org-journal-file-type = 'weekly) already exists and contains the following entries:
#+TITLE: Weekly Journal

* Tessday, 2019-06-25
:PROPERTIES:
:CREATED:  20190625
:END:
** 23:28 (11:28 PM) Some text

and if I execute the command C-u C-c C-j, it opens up the file and adds today's date as shown below:
#+TITLE: Weekly Journal

* Tessday, 2019-06-25
:PROPERTIES:
:CREATED:  20190625
:END:
** 23:28 (11:28 PM) Some text
* Wednesday, 2019-06-26
:PROPERTIES:
:CREATED:  20190626
:END:

I believe it should not have added the entry  * Wednesday, 2019-06-26.  It should have simply opened the file without adding any new entry.
I observed similar program response when the org-journal-file-type is monthly and yearly.
Regards,
Sharad

@sharad-shrestha Hey Sharad! Hmm, right! After rereading the function docstring, it shouldn't add a new heading indeed. My fault :-) Good catch!
Thanks,
Chris

@sharad-shrestha I updated the docstring. This behaviour is by design.


104 hero wave

Fix #104
Original: https://www.moleculardevices.com/en/assets/tutorials-videos/br/critical-considerations-for-choosing-right-microplate-reader
Test URLs:

Before: https://main--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/critical-considerations-for-choosing-right-microplate-reader
After: https://104-hero-wave--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/critical-considerations-for-choosing-right-microplate-reader

In the PR branch the hero as a thin bottom border which should be removed.

@paolomoz Here is the reference to the footer wave css, see https://github.com/hlxsites/moleculardevices/blob/main/styles/styles.css#L1067

@lydiapuric thank you!
Done


Error when running make build-contracts

🐛 Bug Report for zkSync Era In-Memory Node
📝 Description
There's an error when running make build-contracts (it is not working on main).
🔄 Reproduction Steps

Clone the repo.
Run make build-contracts.

🤔 Expected Behavior
This should compile the contracts with no errors.
😯 Current Behavior
An error is thrown and the contracts are not built.
🖥 Environment

Rust version: [e.g., rustc 1.74.0]
Operating System & Version: [e.g., macOS 14.0]

📋 Additional Context

📎 Log Output
➜  era-test-node git:(main) make build-contracts
cd etc/system-contracts && yarn; yarn install; yarn build; yarn preprocess; yarn build-bootloader
yarn install v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 🔨  Building fresh packages...
✨  Done in 5.98s.
yarn install v1.22.19
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.10s.
yarn run v1.22.19
$ hardhat compile
An unexpected error occurred:

/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/hardhat.config.ts:1
import '@nomiclabs/hardhat-solpp';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1124:15)
    at Module._compile (node:internal/modules/cjs/loader:1160:27)
    at Module.m._compile (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
    at Object.require.extensions.<computed> [as .ts] (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:1074:32)
    at Function.Module._load (node:internal/modules/cjs/loader:909:12)
    at Module.require (node:internal/modules/cjs/loader:1098:19)
    at require (node:internal/modules/cjs/helpers:108:18)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ rm -rf ./bootloader/build && yarn ts-node scripts/process.ts
$ /Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/.bin/ts-node scripts/process.ts
(node:73595) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/scripts/process.ts:2
import { existsSync, mkdirSync, writeFileSync } from 'fs';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1124:15)
    at Module._compile (node:internal/modules/cjs/loader:1160:27)
    at Module.m._compile (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
    at Object.require.extensions.<computed> [as .ts] (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:1074:32)
    at Function.Module._load (node:internal/modules/cjs/loader:909:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at phase4 (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/bin.ts:649:14)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.19
$ yarn hardhat run ./scripts/compile-yul.ts
$ /Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/.bin/hardhat run ./scripts/compile-yul.ts
An unexpected error occurred:

/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/hardhat.config.ts:1
import '@nomiclabs/hardhat-solpp';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1124:15)
    at Module._compile (node:internal/modules/cjs/loader:1160:27)
    at Module.m._compile (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1618:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
    at Object.require.extensions.<computed> [as .ts] (/Users/ivanlitteri/Lambda/zksync_learning_path/era-test-node/etc/system-contracts/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:1074:32)
    at Function.Module._load (node:internal/modules/cjs/loader:909:12)
    at Module.require (node:internal/modules/cjs/loader:1098:19)
    at require (node:internal/modules/cjs/helpers:108:18)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [build-contracts] Error 1

This doesnt seem to be an issue since: https://github.com/matter-labs/era-test-node/releases/tag/v0.1.0-alpha.17. Closing for now please re-open if issue persists.


improve debuggability of json ser/de errors

Description
JSON serde errors are very hard to debug because they are usually displayed with the following vague error messages:
Error: Invalid JSON in log record: EOF while parsing a value at line 1 column 1

Caused by:
    EOF while parsing a value at line 1 column 1

This PR separates JSON ser/de errors by different scenarios as well as adding more context to each error whenever applicable.

Looks like the python azure test has flaky timeout errors.


Markdown Support

Hi Good morning! Porsager, thanks for this great piece of software! I'm delighted by using it. I'm currently wondering how to implement or if anyone has already implemented markdown support on flems. Otherwise I'll work on it and as soon as it is ready, I'll open a PR. Thanks!

Hi Alan.. Sorry for the late reply. What kind of integration are you thinking? Where does flems need markdown?


[hi] Add  content/hi/docs/tutorials/kubernetes-basics/explore/explore-intro.html

This PR is part of ongoing hi localization effort here #29353
/language hi

/assign anubha-v-ardhan

/lgtm

/label tide/merge-mthod-squash

/label tide/merge-method-squash

Self approving this wit ref. to https://github.com/kubernetes/website/pull/29412#issuecomment-1010753132
/approve


Initial v3 API docs for Isolation Segments

Starting to populate the IS API docs.  More to come, obviously.
-IS object
-Creating an IS
Signed-off-by: Dan Lavine<EMAIL_ADDRESS>

Reviewed this with @DanLavine, looks good to us.    Merged.


Improve readme.md

It's pretty sparse here.  We should at least have install instructions, and probably some more badges.

Also we should update CONTRIBUTING.md ; it still says to use nosetests for testing.


what's the purpose of "raft-entry-max-size=8MB", in our environment "RaftEntryTooLarge" error occurs?

Question

For now rocksdb performs badly when there are large KVs. Hence we set a limit to the size of a raft entry.

Closing this. Feel free to reopen it or create a new issue if you have further questions.


Face a different direction without walking.

Tsunagari had this and it was useful and necessary. Have a key we can hold, probably shift, that lets your character change directions in place instead of walking.

Haha, I just use this today but found it we didn't have it yet.


feat(rating): a new component rating indicator

Checklist

[x] Fix linting errors
[x] Tests have been added / updated (or snapshots)
[x] Rating component tests 100% coverage
[x] Rating component docs
[x] Style guidelines for rating are checked
[ ]  Native drag on mobile not working but rating selection on mobile works properly

A new rating component
So i had some spare time to implement a rating component with a few possible options listed below:

customize amount of rating indicators and initial number of indicators
provide state callbacks for the current selection and lock state
styling events for mouseenter
icon customization support
native onClick/MouseEnter event callbacks

Please check and provide some feedback 😄
Preview

Thanks for your contribution ❤ , I think this component can be merged without any doubt, but there are still some details to be adjusted, can you follow up here?

Hey @unix , i will take a look and resolve your recommendations in the next days :). Thanks already for the guidance.

Expected to be released in version 2.2.0-canary.8, within 1 week.


patch for nmos-cpp patch file to call gRPC client

patch for nmos-cpp patch file to call gRPC client
within make_node_implementation_auto_resolver function to enable nmos client to communicate with processing server i.e ffmpeg over gRPC communication.

Please don't merge this PR before other commit that forming NMOS patch file, merging in wrong order can cause a complex git conflict issue.


OSError 30

Hello I am running the example code and got this error
Traceback (most recent call last):
  File "/data/user/0/ru.iiec.pydroid3/files/accomp_files/iiec_run/iiec_run.py", line 31, in <module>
    start(fakepyfile,mainpyfile)
  File "/data/user/0/ru.iiec.pydroid3/files/accomp_files/iiec_run/iiec_run.py", line 30, in start
    exec(open(mainpyfile).read(),  __main__.__dict__)
  File "<string>", line 2, in <module>
  File "/data/user/0/ru.iiec.pydroid3/files/aarch64-linux-android/lib/python3.8/site-packages/html2image/html2image.py", line 154, in __init__
    self.temp_path = temp_path
  File "/data/user/0/ru.iiec.pydroid3/files/aarch64-linux-android/lib/python3.8/site-packages/html2image/html2image.py", line 191, in temp_path
    os.makedirs(temp_dir, exist_ok=True)
  File "/data/user/0/ru.iiec.pydroid3/files/aarch64-linux-android/lib/python3.8/os.py", line 213, in makedirs
    makedirs(head, exist_ok=exist_ok)
  File "/data/user/0/ru.iiec.pydroid3/files/aarch64-linux-android/lib/python3.8/os.py", line 223, in makedirs
    mkdir(name, mode)
OSError: [Errno 30] Read-only file system: '/tmp'

[Program finished]

HTML2Image needs a directory where it can store html/css files so that they can then be fed to a headless browser.
The default directory on Linux based-systems is /tmp/html2image, but it seems from the error message that you lack the permission to do so.
To fix the issue, you can either:

allow your user to write to /tmp
or change the directory used by HTML2Image, like so:

hti = Html2Image(temp_path='/my/path')
hti.screenshot(...)

OR
hti = Html2Image()
hti.temp_path='/my/path'
hti.screenshot(...)

Hope this will help.

I'm now closing the issue. Feel free to reopen it if the problem persists, or to open a new discussion if you need more guidance about this.


daemon/cupslocald-systemd.service.in: add system-cups.slice

See https://github.com/OpenPrinting/cups/pull/1035 for rationale and an explanation.
The system-cups.slice file included in the aforementioned PR is not required; the system-cups slice will be automatically created if the file is missing.

Holding for now; will decide whether to do this at some later time.


exception from netlib - reason not well formated get request

Steps to reproduce the problem:
I had a problem with a client that sent a "wrong" GET request: GET  HTTP/1.1 with 2 spaces between  and HTTP/1.1
What went wrong?
exception from netlib/http/http1/read.py on line 247 because split in line 232
method, path, http_version = line.split(b" ")
seems to be wrong. I have fixed it for me be changing the split to
method, path, http_version = line.split()
Then it worked.
Best regards,
Thomas

Thanks for the report - I think it is a good idea to be more liberal in what we accept (slight non-conformity to RFC should be ok). This issue will be fixed in #1367 - are these the changes you applied?


[BUG] Backend start with an error

To Reproduce
python3 Backend/main.py

It throws:
ERROR:utils:Error occurred while checking environment variables: can only concatenate str (not "NoneType") to str

I entered the Backend directory, however it's the same result.
I'm sure python3 is from the virtualenv local path.

Send me a screenshot of your project structure and .env file, blur out sensitive information.

Not ls, but tree command

I removed it to show the tree to you, otherwise there're too many results.

oh, you mean the instance of ".env.example"?
I thought .env was the common name of virtualenv generated.

Works like charming now! Thanks!


Fix problem in local amplitude

Seems that the local amplitude still uses old version of resampler. Update that to new version.

By the way, I am using the local amplitude as the third channel now. It is the way you intended, Dan? Now the input of the network will change from [bs, 2, num_freq_bands, seq_len] to [bs, 3, num_freq_bands, seq_len]. I didn't change the original signal and just add the local amplitude as the third channel.
Should I divide the original signal by the local amplitude or just let the network learn how to make use of the local amplitude? Thanks!

My idea was that you'd divide by the local amplitude (or maybe some power of it that's less than 1), and you'd predict the normalized-amplitude version of the signal but possibly include the divided-by factor as a weighting factor in the objective function so it stays equivalent to what you had before.


Undocumented behavior for dir entries from lister with metakey

Docs of Operator::lister_with didn't mention that directory entries are special and their metadata may not be fetched even if required by metakey and storage service is able to supply this information.

Metakey has been removed.


Add pio pwm example

This adds a more advance pio example which uses side set and instruction injection

Moved pio code to seperate file so we can also close  #154


Fix for the IzPack exception: ResourceNotFoundException: Cannot find named resource: 'info'

Caused by: com.izforge.izpack.api.exception.ContainerException:
com.izforge.izpack.api.exception.ResourceNotFoundException: Cannot find
named resource: 'info'
Signed-off-by: Francis ANDRE<EMAIL_ADDRESS>

Thanks for this work. Please be patient with the release.


Dev mini perspective view

is this a hotfix?

is this a hotfix?

No sorry. I'll merge it to dev_mini_persp_merged_2.7.4


Sample Explorer tab - work in progress

Add sample explorer functionality using useq.
It needs info about the pixel size, so the micromanager "demo_config.cfg" has to be loaded.
I had to temporary do an addition to useq MDASequence:
class MDASequence(UseqModel):
   axis_order: str = "".join(INDICES)
   stage_positions: Tuple[Position, ...] = Field(default_factory=tuple)
   channels: Tuple[Channel, ...] = Field(default_factory=tuple)
   time_plan: AnyTimePlan = Field(default_factory=NoT)
   z_plan: AnyZPlan = Field(default_factory=NoZ)
   uid: UUID = Field(default_factory=uuid4)
   extras: str = ''         <-

@tlambert03 ready for review

Hi @fdrgsp, I merged in the master branch that has a bunch of tests, and it exposed one bug in this code here that needs to be fixed before merge.  whenever a zstack is acquired, I get the following stack trace, which indicates a bug in _save_mda_acq at ~ main_window.py:329:
Traceback (most recent call last):
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari-micromanager/micromanager_gui/main_window.py", line 283, in _on_mda_finished
    self._save_mda_acq(sequence, meta)
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari-micromanager/micromanager_gui/main_window.py", line 329, in _save_mda_acq
    tifffile.imsave(
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 891, in imwrite
    result = tif.write(data, shape, dtype, **kwargs)
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 1694, in write
    ijshape = imagej_shape(
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 14446, in imagej_shape
    raise ValueError('ImageJ hyperstack is not a grayscale image')
ValueError: ImageJ hyperstack is not a grayscale image

you should pull these changes to your local branch, and then you can run pytest to see whether you've fixed them

Hi @fdrgsp, I merged in the master branch that has a bunch of tests, and it exposed one bug in this code here that needs to be fixed before merge. whenever a zstack is acquired, I get the following stack trace, which indicates a bug in _save_mda_acq at ~ main_window.py:329:
Traceback (most recent call last):
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari-micromanager/micromanager_gui/main_window.py", line 283, in _on_mda_finished
    self._save_mda_acq(sequence, meta)
  File "/Users/talley/Dropbox (HMS)/Python/forks/napari-micromanager/micromanager_gui/main_window.py", line 329, in _save_mda_acq
    tifffile.imsave(
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 891, in imwrite
    result = tif.write(data, shape, dtype, **kwargs)
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 1694, in write
    ijshape = imagej_shape(
  File "/Users/talley/miniconda3/envs/napdev/lib/python3.9/site-packages/tifffile/tifffile.py", line 14446, in imagej_shape
    raise ValueError('ImageJ hyperstack is not a grayscale image')
ValueError: ImageJ hyperstack is not a grayscale image

you should pull these changes to your local branch, and then you can run pytest to see whether you've fixed them

Hey @tlambert03, I think I found the issue...basically the tifffile kwarg imagej=True is supporting stacks up 5 dimensions. So I guess we have 2 options:

not caring about the imagej compatibility of the stacks saved
or save each position in separate files all the time to reduce the stack size to max 5 dimensions.

side note:  even when there is only 1 position, the stack we generate is like: tpzcxy ->(2,1,3,2,512,512)
What do you suggest?

hmmm.  well, the ImageJ compatibility is nice, but I don't think we necessarily want to limit ourselves based on it.  Perhaps you could do
data = data.squeeze()  # remove singleton dimensions
imsave(..., imagej=data.ndim <=5)

?

thanks for all the work @fdrgsp!  I'm going to merge this, we can work on test coverage next


Web context management when running behind a reverse proxy

Proposed changes
Hello,
I propose to add an entry in values.yaml to handle the WEBLATE_URL_PREFIX value (when running behind a reverse proxy)
I've fixed the liveness and readyness probe url (/healthz) following issue:
When running behind a reverse proxy (ex: /weblate), the liveness and readyness probes checks /healthz (and not /weblate/healthz) , so always gets a 404, and the pod never gets ready to run.
Checklist

[x] Lint and unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added documentation to describe my feature.
[ ] I have squashed my commits into logic units.
[x] I have described the changes in the commit messages.

Other information
N/A

Merged, thanks for your contribution!


Incremental Rollup Mode Settings

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

@kofijohnson  This PR as a grandchild branch of rollups__IncrementalBatch can work, but only if it's the only grandchild branch and as long as there are no merges into feature/rollups before this branch is merged. This is because MetaCI does not support more than a single level down. So in this case, any other merge into feature/rollups will be sync'd directly into feature/rollups__IncrementalBatch__UI rather than first sync'ing into feature/rollups__IncrementalBatch and then up into feature/rollups__IncrementalBatch__UI.

We are closing this PR because we have created a new one https://github.com/SalesforceFoundation/Cumulus/pull/3606


YouTube "clip" embed

We embed youtube videos but not clips which are becoming more common. example: https://stacker.news/items/438611

This is harder than it seems.
The path /clip/ is not compatible with embed. To make it work as an embed, you must have 2 parameters that are not shared in this path, videoId (which is the default embed parameter) and clipt (some video time parameter, a hash that does not exist as a standard )
But there is a "solution", you can make a request directly to the link and get the embed link that is shown by the metadata tags og:video:url, og:video:secure_url or twitter:player.
The problem is that Youtube has a CORS policy that does not accept requests from other servers, so it is not possible to make a request directly through the code, the request would have to go through a reverse proxy server that bypasses cors
https://stackoverflow.com/questions/74697206/what-format-is-the-data-in-the-clipt-parameter
https://github.com/honestbleeps/Reddit-Enhancement-Suite/issues/5344


Adding some additional text

This probably doesn't need to be an issue, but I wanted to list these proposed additions to this repo so they are not forgotten or lost along the way.
I believe we need an introduction that provides the rationale behind adopting the test procedure.
I think a listing of the MUSTs and SHALLs from the Standard would clarify the exact elements the tests are designed to measure.
I think some background on how the initial tests were conducted would be helpful in framing the choice of tests. Note that on the 9/17 phone call Cameron Mott agreed to do a first cut of this text.

That's exactly what an issue is for. 👍

We now have the "Musts and Shalls" from the Standard posted on the repo as requirements." Thanks, Priyanka.
Some edits are needed:
``

you don't need an apostrophe in "Musts." Instead, make MUST and SHALL all uppercase, and make the plural 's' lowercase (MUSTs)

"Reference" in the left-hand column is missing the second "e."

The word "Control" should be centered, not flush right. The text in that box should be flush left, not flush right. Text in "Reference Number" column should be centered.

I'm not sure what "Domain" means. If it is referring to the section or subsection of the Standard, the title should be "Section." And why do you call the third column "Control"? "Context" might be a better word.

The first two points here are "requirements" in terms of broad goals. They are not technical "MUSTs  and SHALLs" which refer to specific design elements or steps that must be taken. I think, instead of including this in the table, they should be included in a brief section intro. I will do a separate pull request with suggested text.

If you are running partial sentences in the "Control" column, please indicate they are incomplete with an ellipsis (...)

In 5.2.1, moving from bulleted text in the document to one sentence here makes this potentially confusing. For the public key identifier (the 15th item I believe) please present it as follows: "A public key identifier is EITHER all of the following—(a) The value of the public key itself (b) the public key cryptographic algorithm, and (c) the particular scheme used to verify the signature—OR a secure hash over at least the above components."

Use the same set-up as above for all the items in this section that are lists of elements. Otherwise the syntax gets very confusing.

In <IP_ADDRESS>., there is some messy spacing. This might be corrected when this is set up as flush left, but words can't be on top of each other. Also, here and elsewhere, if you move a bulleted list into a paragraph, you generally don't capitalize the first word.

In <IP_ADDRESS>.1 Watch out for weird capitalizations. i.e. "A Payload Containing" should be "A payload containing..."

<IP_ADDRESS> Targets role...the name of roles, repositories, metadata is capitalized.


Add HTTPS functionality to client and util package

Closes #163

api/log/messagecodes.go: Created a new error category to reference the new util package.
api/server.go: Changed how the API starts to support HTTPS connections.
client/analysis/analysis.go: Changed how the requests are being made to support HTTPS functionality.
deployments/scripts/create-certs.sh: Added a new function to generate the certificates needed to a TLS connection.
deployments/scripts/generate-env-pass.sh: Fixed typo in environment variables.
deployments/scripts/run-create-certs.sh: Added a a new line to create the certificates needed for HTTPS.

Closes #150

api/analysis/dockerrun.go: Added the handlePrivateSSHKey() function to the util package.
api/dockers/api.go: Added NewClientTLS() function to the util package.
util/util.go: New file designed to handle useful functions across huskyCI.

Sounds awesome, @Krlier ! Thanks for this contribution! You rock!! 🔥


[joy-ui][Switch] Fix missing class name

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #39320

i want to work on this. could you please assign me this issue ?

👏 Thanks for the fix!


Updated validations.py python script

Update validations.py python script.
Fixed the behavior of validate_user function in validations.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Update validations.py python script


enforce_eager flag

2024-02-02 21:44:03.976
[b2k2ml81pl56tl]
[info]
engine.py :190 2024-02-03 03:44:03,976 Error initializing vLLM engine: CUDA out of memory. Tried to allocate 112.00 MiB. GPU 0 has a total capacty of 44.35 GiB of which 53.38 MiB is free. Process 3663367 has 44.28 GiB memory in use. Of the allocated memory 37.38 GiB is allocated by PyTorch, and 275.68 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation. See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
2024-02-02 21:43:49.554
[b2k2ml81pl56tl]
[info]
INFO 02-03 03:43:49 model_runner.py:629] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
2024-02-02 21:43:49.554
[b2k2ml81pl56tl]
[info]
INFO 02-03 03:43:49 model_runner.py:625] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
2024-02-02 21:43:48.339
[b2k2ml81pl56tl]
[info]
INFO 02-03 03:43:48 llm_engine.py:316] # GPU blocks: 7754, # CPU blocks: 2048
2024-02-02 21:43:24.749
[b2k2ml81pl56tl]
[info]
INFO 02-03 03:43:17 weight_utils.py:164] Using model weights format ['*.safetensors']

I get this error when trying to run gptq models. I've built the worker myself with enforce_eager set to True and it works. Maybe an environment variable? Or could there be something else preventing this model from utilizing the proper amount of vram?

Try lowering GPU_MEMORY_UTILIZATION first

Try lowering GPU_MEMORY_UTILIZATION first

I set it to 0.8 and it worked. Does this reduce the model's performance?

It should lower the total number of requests you can handle concurrently. Try setting a higher number (but lower than the default 0.95), and work your way down until it doesn't crash.

Disabling CUDA Graphs by setting enforce eager to true would lower performance though, so lowering memory utilization is better.

Thank you. I'll figure out a number that works.


make using miniver trivial

At the moment people need to manually copy a bunch of files and snippets, but most of this can be automated.
The contents of the setup.py cannot be automated, as it would be excessively complicated to parse that file and insert that snippet at the correct location. OTOH everything else can be automated.
We should:
+ add an entrypoint script that grabs the version.py in the installed version of miniver and inserts the necessary lines into __init__.py and .gitattributes. It should then print the necessary lines that need to be copied manually by the user to the terminal and exit
+ add a script that can be curld and piped into bash/python that will do the same thing as the entrypoint script, but it will get its version.py from GitHub instead.

Done, as of v0.1


Alignment problem of "#" in tags in Live Preview

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.0.11
Describe the bug
Hi Kepano!
Thank you for the work! As you can see, the # in tags is misaligned (I have the issue on both mac OS and Android):

Debug info
SYSTEM INFO:
Obsidian version: v1.0.0
Installer version: v1.0.0
Operating system: Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101 21.6.0
Login status: logged in
Catalyst license: none
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal
Snippets enabled: 1
Restricted mode: on
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

Closed in 6.0.13
https://github.com/kepano/obsidian-minimal/releases/tag/6.0.13


Add links to hook names to make navigation easier

Simple quality of life improvement (at least for me ;) )

Codecov Report

Merging #189 (e9f862e) into main (1405436) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #189   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           34        34
  Lines         4772      4772
  Branches      1077      1077
=========================================
  Hits          4772      4772

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1405436...e9f862e. Read the comment docs.


JB Table of Contents

closes #118
Establishes book structure and menu organization for the built jupyterbook.
Work-In-Progress

Created a branch and PR so that anybody can pull the TOC.yml to add, update, etc.
Push changes directly to this branch with edits to TOC.

An interesting idea that we could perhaps leverage here.... the TOC document is a list of references to source files.  We can include the same source file in multiple locations (i.e. chapters).  This may be useful for the case of pre-processing notebooks as discussed today.  The source notebook lives in one location in the repo, but its content can appear in two places in the table of contents -- once under "model evaluation" and once under "pre-processing".

@amsnyder
If I understand you correctly, you want the table of contents to match the folder structure exactly. You may want to consider the ordering of the chapters and make a decision there -- the alphabetical listing of the directory is not a good fit, in my opinion.  The appendix information, for example, should definitely come last.
In terms of a folder overview information, your impulse is correct -- much like this:
  - caption: Evaluation Workflows
    chapters:
    - file: model_evaluation/tutorials/nwm_streamflow/00_Overview
      sections:
      - file: model_evaluation/tutorials/nwm_streamflow/01_Data_Prep
      - file: model_evaluation/tutorials/nwm_streamflow/02_Analysis_NWM
      - file: model_evaluation/tutorials/nwm_streamflow/02_Analysis_DScore
      - file: model_evaluation/tutorials/nwm_streamflow/03_Visualization

The 'chapter' overview is in a document that describes what's in this folder. That can be a README.md or any markdown or notebook file. Those will need to be created in folders where you want them as part of this book-building process.
This book-building and documentation thread will address a few already-open issues... #8, for example.
We should also close the loop on #62 (naming of notebook files) before we get too far on this. I named my notebooks with leading numbers to ensure that they sorted into the order I wanted... but it doesn't have to be that way. If we are going to have a consistent standard for naming notebooks, we should sort that out as part of this process also.
Also, how does this PR/Issue relate to #50 ?

Yes, I am suggesting that the book structure mimic the folder structure. We put thought into the organization and naming of our directories, so I don't see why we shouldn't use this organization. I am open to organizing differently if anyone has thoughts on why a different organization might be better!

A few context notes as folks review the TOC and make changes:
As you move items around, maintain the indent level.
This is how YAML files know what is inside of what.
The general organizational scheme is outline-like.... the result will be akin to:
I. PART
  A. Chapter
     1. Section
     2. Section
  B. Chapter
     1. Section
II. PART
  A. Chapter
  B. Chapter

This TOC config file defines what is in the Table of contents pane in the book pages.
Not all files need to appear in that list -- only if you want folks to find it in the TOC and jump right to it.
We can add sub-sections if that would be useful, but we begin to overrun the width of the TOC panel if we do that.  Can be done, but with caution.
Not all documents need to be in the book (whether in the TOC or not).  An example of that would be the ./doc/JupyterBook_Admin.md file.  That file describes how to write jupyterbook-friendly documents, and is meant for contributors. It certainly can go in the book, but probably doesn't need to.

In terms of order, I think we probably want the order that folders are listed in this issue comment: #1 (comment)

I have ordered to match the suggested sequence in #1 as above...   Some folders not included in that issue comment are added at the end of the TOC ("docs", "essential_reading").
Continuing with https://github.com/hytest-org/hytest/pull/119#issuecomment-1337668643, we need to fill in the following documents at a minimum. These are all of the type 'what is in this folder':

[ ] /dataset_preprocessing/tutorials/README.md
[ ] /dataset_preprocessing/demos/README.md
[ ] /dataset_access/README.md
[ ] /model_evaluation/tutorials/README.md
[ ] /essential_reading/DataSources/README.md
[ ] /essential_reading/ParallelProcessing/README.md

In addition -- thinking as a potential reader, I'd find documents such as these useful:

[ ] /README.md (see #8)
[ ] /docs/About.md (HyTEST: what is it, who is it, what's the mission? etc)
[ ] /docs/How_To_Use_This_Book.md (what are the aims of this material?)
[ ] /docs/Code_of_Conduct.md (related to "contributing")
[ ] /docs/changelog.md
[ ] /docs/roadmap.md (what is planned for future?)

In terms of a naming convention for documents (#62) we can proceed with current naming with the understanding that if the standard changes, we'll have to re-plumb the TOC to reflect filename changes later.
I can take ownership on a few of those docs (in essential_reading for example), but I am not sure I'm the right person to describe many of the others. We should talk about whether those other docs are priorities for inclusion, and who will be writing them.  During 12/12 checkin meeting?
I propose that additions such as the above be committed to the gt-118-JupyterBook-TOC branch.  In this way, they'll all get swept up in the TOC update when it gets merged.
--gt

So... this PR and branch is a little stale -- so I re-based it off the current state of main so we can move forward.
Once files in the list in https://github.com/hytest-org/hytest/pull/119#issuecomment-1342788663 are created, we need to put them in the _toc.yml in the right spot.  I have stubs in there now, which will need to be edited.

@gzt5142 - I see this PR has 62 files changed. Can we close this and open a new PR with only the content for the JupyterBook so I can review that and we get it merged in?

This is an unfortunate side effect of the rebase I did to catch this branch up to the current state of main and resolve merge conflicts with those main changes.  This branch was made several weeks back, so had drifted quite a bit from main...  In retrospect, I think a merge rather than a rebase would have been better for me to do to address this drift.
Solutions -- Unfortunately, we can't un-rebase... the only solution (that I can think of) is to stash changes, abandon this branch and PR, then create a new branch where changes can be applied.

I'm ok with that if it's not too much of a lift for you


update owners of minikube doc

@balopat is the new owner of minikube, and the associated technical reviewer for docs
https://github.com/kubernetes/minikube/pull/3033

/assign @aaron-prindle

/cc @kubernetes/sig-cluster-lifecycle-pr-reviews

/lgtm
/approve
/hold
The hold is because I think we prefer to use Github groups rather than individuals, for single files. The OWNERS mechanism is the right place to use individuals. As this PR just sticks with how it was done for this file previously, I'm OK with this going in, so remove the hold if you feel like you don't want to deal with that here, by doing /hold cancel. Thanks!

Thanks @mistyhacks!  cc @kubernetes/sig-cluster-lifecycle-misc if anyone wants to own this from the SIG side.
/hold cancel


TG longname bug for service export/imports

If a service is imported and target group is created out of it, the longname for resource becomes invalid.
This may be due to our TG longname format:
k8s-{resourcename}-{routename}-{vpcid}

For an exported service, HTTP route name is missing.
The root cause is unclear at this point, but we need to figure out why make e2etest is failing on TARGET_GROUP_NAME_LEN_MODE=long

Hmmm, this is done by design.    The owner of  serviceexport  only intend to export its k8s service to VPC lattice federation which trigger a controller to create a target group.    The consumer in other VPC needs to use explicit name as service import.
Controller should never trigger creating a target group for serviceimport.

I might have root caused this incorrectly but make e2etest has been continuously failing if we have longname mode on. Needs further investigation it seems.

Use case was created to pass conformance testing, but breaks E2E tests. Need to determine how we will handle target group names as part of our work for managedBy Tags and ownership model.

https://github.com/aws/aws-application-networking-k8s/issues/392

should be fixed with #457


Can we display the metrics on the teammate review response map page?

View submissions > Assign Grade (Takes us to the heatgrid page)
Could the data be added to to the teammate review heatgrid page?

Done.


Support for tolerance in DistanceConstraint

Hi there!
Thank you for all your great work with this amazing library!
We needed to support horizontal drag-n-drop from a vertically scrollable container using touch. We added support for optionally specifying tolerance in DistanceConstraint so that the drag operation will not be started if the user drags more than tolerance. For our use case we specify
{
  distance: { x: 8 },
  tolerance: { y: 16 },
}

as activationConstraint so that the drag operation isn't started if you drag more than 16px vertically, because we want to continue the scrolling in that case.
Please consider merging our PR https://github.com/clauderic/dnd-kit/pull/399. :)

Fixed by https://github.com/clauderic/dnd-kit/pull/399


allow downloading models from public gdrive urls using gdown lib

Oh, nice. I didn't know there was a convenient package for this. Let me test it then I'll do the merge.

Looks good. We'll keep the UserWarning gdown prints.


bug: Data is added to Redis even if there are no titles

Describe the bug
Title data can still be added to Redis even without title data. This can be misleading on the UI end (#3) when routes for a particular date are being generated, especially on demand (ex. /dates/2023-07-14 when the current date is 2023-07-13.
To Reproduce
We'll base this off #3, but this applies outside the website and PR scope. This is in the context of the date being 2023-07-13.
Steps to reproduce the behavior:

Go to /titles/2023-07-14
The page will still be rendered, generating the relevant static path. However, no data is displayed on the page. This is because data for that date does not exist yet

Expected behavior
Two things should happen.

a) Data should not be committed to Redis if there are no titles for the requested date
b) The page should 404 since there is no data for that particular page

Screenshots

Additional context
https://github.com/acollierr17/netflix-refresh/blob/84bb5f2727e7bb708750c001d260ba988174e1b1/src/lib/netflix.ts#L117
This shows that the only condition to be met is if there isn't existing data in the dates set. We can add to this by adding data.size > 0.

I'm linking #3 to this because this is relevant to the UI and how titles should be stored in Redis.


Update analyze_results.py

correct spelling mistake(sucess->success)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


minimap does not behave correctly when canvas is dragged and nodes are out of view

Using the default example: https://g6.antv.vision/en/examples/tool/minimap
If you drag the canvas so that the nodes are not in the viewport anymore, the minimap does not reflect correctly the current view.

graph.fitView();

Minimap plugin on X6 behaves as expected. Maybe the code should be merged in G6?
https://observablehq.com/@jiazhewang/introduction-to-antv#X6Demo

For performance reasons, the minimap in G6 is updated only when the viewport is changed by dragging or zooming the canvas, but not dragging a node. In this case, drag the canvas after dragging the node will trigger the minimap update.
Do you think it is necessary to update minimap after 'dragend' event happens on a node? Users' suggestions are always the best input for us.

I don't think it is a problem with dragging nodes. The problem occurs when dragging the canvas so that the nodes becomes out of view. The minimap should then be updated as if the viewport has been zoomed out, or viewport has been expanded.
Please have a look at the X6 minimap plugin as it has the good behavior:
https://observablehq.com/@jiazhewang/introduction-to-antv#X6Demo
Even though this demo does not support canvas dragging, you can see that when a node is out of the viewport, the minimap is updated as if the viewport has been expanded.

Fixed by 3.4.5.

This works perfectly now in 3.4.5, thanks for the update.


MSTest2 support

First of all, many thanks for this great library.
I am in the process of transitioning to MSTest2 and I needed a support of a declarative Autofac integration. I created the following project that you can integrate in Autofixture if you want: https://github.com/frblondin/AutoFixture.MSTest2
As you can see I used the AutoFixture.xUnit.net2 project as a starting point.
Note that this project has a dependency with another project that I created to improve the data injection management (MSTest.TestFramework.AdvancedDataRow).

:+1:
Since we don't support MSTest and there are no plans to support MSTest2, and this isn't about some Pull Request, I'm going to close this.
Feel free to reopen this, or open a new issue, if something actionable or related arises in the future.  The URL provided in this issue is still searchable though, in case other people want to look at it, or use it.

You are right, there was no question :-)
My question is the following: if I submit a pull request, is there any chance it will be merged or you are not interested in providing a support of MSTest2?

I have a feeling that MSTest's extensibility model isn't a lot better than what we've got with NUnit2. Happy to be proven wrong though.

My 2 cents opinion is that even if MSTest2 is not better than other testing frameworks from your standpoint, it will likely be used by many projects as it will be pushed & supported by Microsoft.
My current problem is that XUnit2 is really too slow in my context (big solution for which test discovery takes 2 minutes with XUnit2 and 6 seconds with MSTest2, see this link) so I'll probably switch to MSTest2 and I'd like to continue using Autofixture.
Again, I can do a pull request but I want to know if you are interested.

IME, if we decide to take on a new unit-testing Glue Library, it's going to be easier (and faster) with a series of Pull Requests, like we did with NUnit2 and NUnit3.
Even that though won't probably be so easy due to the fact that currently there's a lot of duplicate code in AutoFixture.NUnit2, AutoFixture.NUnit3, AutoFixture.xUnit.net, and AutoFixture.xUnit.net2 projects.
I can see, for example, the FavorArraysAttribute, FavorEnumerablesAttribute, and FavorListsAttribute on each of the projects, and there are other similar (not to say nearly identical?) files like this.
Moving forward with a series of Pull Requests for MSTest V2 may first invoke the rule of three, to get rid of some duplicate code from the existing unit-testing Glue Libraries—a decision that has to wait until #703 is closed, IMHO.

so I'll probably switch to MSTest2 and I'd like to continue using Autofixture.

That should be possible already using the fork you've created, AFAICT. :smiley:


Add {{#alias}} block that works like {{#with}} but doesn't change context.

Using the new {{#with foo as bar}} aliasing is awesome.
Sometimes you don't want to create a new context, you just want to introduce the aliases:
{{#each items as item}}
    <-- a helpful alias -->
    {{#with item.foo + 12 as addFoo}}

    {{/with}}
{{/each}}

So I'm proposing {{#alias foo as bar}} that introduces the alias, but doesn't change the context:
{{#each items as item}}
    <-- a helpful alias -->
    {{#alias item.foo + 12 as addFoo}}

    {{/with}}
{{/each}}

Unless I'm misunderstanding, {{#with foo as bar}} doesn't introduce new context. It kinda just overloads with and if there are aliases no additional context is introduced. It just adds a block in the template to find aliases whilst walking up during resolution.
new Ractive({
  el: 'main',
  template: '{{#with foo.bar as bat}}{{.foo.bar}} {{bat}}{{/with}}',
  data: { foo: { bar: 'yep' } }
});

That results in yep yep. I decided not to try to add context because that gets really weird with multiple aliases in a list e.g. {{#with foo.bar as bat, bip.bop * 12 + 2 as wat, some[great].fun() as ynot}}.

Unless I'm misunderstanding, {{#with foo as bar}} doesn't introduce new context

Okay, my bad then. Still is this desirable?

outside: {{JSON.stringify(this)}}

    {{#with foo as bar}}

inside as: {{JSON.stringify(this)}}

    {{/with}}

    {{#with foo}}

inside: {{JSON.stringify(this)}}

    {{/with}}

outside: {"foo":{"name":"fooage"}}
inside as: {"foo":{"name":"fooage"}}
inside: {"name":"fooage"}

decided not to try to add context because that gets really weird with multiple aliases in a list e.g. {{#with foo.bar as bat, bip.bop * 12 + 2 as wat, some[great].fun() as ynot}}.

Yea, I see where your headed. Unless that context was a pseudo object with the rollup of those aliases.
Meh, okay - closing for now.


Source maps are not syncing with code on latest Chrome and Firefox on macOS

The last couple days, my source maps suddenly stopped working correctly in Fusebox. Namely, the debugger was off by several lines from where my breakpoint was. This happened in Chrome and Firefox. In short, I had to turn off source maps in order to debug. I'm still wondering what the cause is. Probably a bug with Babel? Anyway, I tried splitting out my bundles into smaller sizes but that didn't change anything. Now, I ended up using the Typescript compiler useTypescriptCompiler: true. Starting things up is a lot faster and it fixed my source map issue. I wanted to give Typescript a shot anyway so this was the catalyst. Just posting my struggle here in case anyone had ideas. Below is my fuse.js config. To fix it, I just flipped the compiler flag and removed the BabelPlugin().
Below is a link to a repo with the issue distilled to its essense:
https://github.com/aboyer1013/fuse-box-sourcemap-issue

It has been fixed in fuse-box@next


std::shared_ptr InferImpl::tensor  ERROR

hello， thanks for your share. i encounted one problem in function std::shared_ptr<Tensor> InferImpl::tensor(const std::string& name), the details of this error is below,
[2022-06-02 11:20:01][fatal][trt_infer.cpp:402]:Assert failed, this->blobsNameMapper_.find(name) != this->blobsNameMapper_.end()
[2022-06-02 11:20:02][error][trt_builder.cpp:30]:NVInfer: 1: [runner.cpp::execute::416] Error Code 1: Cuda Runtime (invalid argument)
[2022-06-02 11:20:02][fatal][trt_infer.cpp:340]:execute fail, code 0[cudaSuccess], message no error
 [2022-06-02 11:20:02][error][cuda_tools.cpp:25]:CUDA Runtime error cudaStreamSynchronize(stream_) # an illegal memory access was encountered, code = cudaErrorIllegalAddress [ 700 ] in file ..../src/tensorRT/common/trt_tensor.cpp:389
 [2022-06-02 11:20:02][error][cuda_tools.cpp:25]:CUDA Runtime error cudaFree(gpu_) # an illegal memory access was encountered, code = cudaErrorIllegalAddress [ 700 ] in file .../src/tensorRT/common/trt_tensor.cpp:101

looking forward to your reply!!!


ROT.Map.Cellular.prototype._getNeighbors

I've been debugging my code and traced that the dijkstra.compute never go into my callback functions, then I found this._computed never include the key fromX+","+fromY, then I found the _getNeighbors function didn't return the fromX+","+fromY key. I go into the _getNeighbors function, and found the following code ,
if (x < 0 || x >= this._width || x < 0 || y >= this._width) { continue; },
did you mean y < 0 after the second ||?
I've not finished my debugging, I don't think this is the problem. Because in the interactive manual the fromX+","+fromY does show in the path finding computation. I'm still working with the problem, and hope further helps from you. Thank you for your excellent work!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36111900-rot-map-cellular-prototype-_getneighbors?utm_campaign=plugin&utm_content=tracker%2F297828&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F297828&utm_medium=issues&utm_source=github).

I've found the problem: the passableCallback(fromX, fromY) should return true.

I've found the problem: the passableCallback(fromX, fromY) should return true.

did you mean y < 0 after the second ||?

Yeah, this is definitely a bug! Thanks for spotting it.

I've found the problem: the passableCallback(fromX, fromY) should return true.

Can you please be more specific? Where and what should I fix? :)

No. It is my fault. I'm using rot.js the first time. Because I didn't know the passableCallback(fromX, fromY) should return true, so dijkstra.compute did not work correctly. Thanks for the excellet rot.js.

I see. I will fix the duplicate x<0 issue soon. Stay tuned :)

Fixed, thanks :)


TraceLog: Missing Event - SchedulingLogContextChange

Hello - My ETL parser utility requires parsing of specific DxgKrnl Event Name - "SchedulingLogContextStateChange". I can spot them in Dxgkrnl Provider GUID's Event List in GPUView, but somehow I don't get them while parsing ETL with Trace Event Parser. Is this a known issue? Appreciate your help!
Originally posted by @smsunder in https://github.com/microsoft/perfview/discussions/1358

I'm not aware of an issue here.  Can you share a simple repro and a trace that exhibits this issue?

Hello - Following is a simple straightforward event parser that dumps the Event Data to console
I do get the "SchedulingLog" Event on the console, but I don't see "SchedulingLogContextStateChange" event all
Attached is the corresponding ETL file - SchedulingLog.etl
Nevertheless if I open the ETL file with GPU View I can see both events - SchedulingLog and SchedulingLogContextStateChange
Not sure what I'm missing here
`
using System;
using System.Collections;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.IO;
using System.Threading.Tasks;
using System.Text.RegularExpressions;
using Microsoft.Diagnostics.Tracing;
using Microsoft.Diagnostics.Tracing.Parsers;
using Microsoft.Diagnostics.Tracing.Session;
namespace Dummy
{
class Program
{
static void Main(string[] args)
{
using (var source = new ETWTraceEventSource("SchedulingLog.etl"))
{
// Set up the callback
source.Dynamic.AddCallbackForProviderEvent("Microsoft-Windows-DxgKrnl", "SchedulingLog", delegate (TraceEvent data)
{
Console.WriteLine("GOT SCHEDULING EVENT {0}", data);
});
            // Set up the callback
            source.Dynamic.AddCallbackForProviderEvent("Microsoft-Windows-DxgKrnl", "SchedulingLogContextStateChange", delegate (TraceEvent data)
            {
                Console.WriteLine("GOT SCHEDULING CONTEXT STATE CHANGE LOG EVENT {0}", data);
            });
            source.Process(); // Invoke callbacks for events in the source
        }
    }
}

}`
SchedulingLog.zip


Chore check duplicate column name when create table with rollup

Proposed changes
check duplicate column name when create table with rollup
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall


slow exporting mesh speed

After the training, start to ns-export mesh, it was found that the point cloud computing speed was particularly slow:

It took nearly 80 minutes to implement 4% of the progress
my ns-export mesh command as follows:

ns-export poisson --load-config outputs/dome/nerfacto/2023-11-04_151351/config.yml --output-dir exports/mesh/ --target-num-faces 50000 --num-pixels-per-side 2048 --normal-method open3d --num-points 1000000 --remove-outliers True --use-bounding-box True --bounding-box-min -1 -1 -1 --bounding-box-max 1 1 1

By the way, When I tested another object (the image resolution is the same, but the number of images is three less), the export speed is much faster and the export mesh command is the same. I wonder why the export speed is so different.
Thank you!!!

If it gets stuck like this, it is not going to proceed. It is related to the logic for how points are calculated. Likely the region you are extracting does not have much density / is not viewed enough in the source images.

@tancik Thanks a lot, the final result does show that there is no data.


Feat/add custom domain

Description
This MR does the following:

Support for custom domain names per stage
Support for custom domain name mapping
Updated README.md to generate documentation with terraform-docs
Added versions.tf to add providers and requirements

Motivation and Context
This is a common feature that should be supported, in this case it is using API Gateway v2 resources to be able to support the mapping, domain resources are the same for v1 and v2.
Breaking Changes
No breaking changes, the creation of the domain resources and mapping can be enable disable without impact other resources in the module.
How Has This Been Tested?

Provisioned a real API with this changes without issues.

See question on domain name resource & domain name mapping

I have fixed endpoint type issue and moved to v1 resources. Please review and let me know if there is anything else that can be improved!


fix up the description in the run_tests.sh

run_tests had the wrong invocation of the script in the comments. fix
that.

this also belongs in trunk-tracking once this is in here.

PAGESPEED_TEST_HOST can be passed in as the argument after the nginx binary though. Should we still doc that?
oschaaf@ubuntu:~/code/google/nps-issue-1175/test$ grep -ir PAGESPEED_TEST_HOST
...
run_tests.sh:PAGESPEED_TEST_HOST="$5"
...

fixed and squashed.

lgtm!


Add Capacitor

List URL: awesome-capacitor
This list provides resources on Capacitor to help anyone start building web native apps. It focuses on the plugins part for now but will be enhanced with the community.
Reviewed the following 4 PRs:

https://github.com/sindresorhus/awesome/pull/2160
https://github.com/sindresorhus/awesome/pull/2155
https://github.com/sindresorhus/awesome/pull/2169
https://github.com/sindresorhus/awesome/pull/2170

By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

unicorn

It is a good source, practical and rich in content

Thanks @ehsanghaffarii <3
hope that can be include soon @sindresorhus

Includes a succinct description of the project/theme at the top of the readme. (Example)

Not done

I would like to see more than just libraries. Include some blog posts, tutorials, links to community resources (Stack Overflow tag, IRC, chat, forums, communities, Reddit, etc. Example: https://github.com/sindresorhus/awesome-electron#community), videos of talks, book, learning material, etc.

@sindresorhus thanks for the review!
It made me push to make the list even more awesome!
i added some new sections :

Learning

Crash Courses
Tutorials
Case study

Community

With of course the resources i know are awesome!
i also made updated the header with a new image!
And linted again :)

I understood this is from capacitor-print, but I think the correct casing for webview is WebView. Or does it refer to something else that I may have missed?

Print - Print the webview.

@eozer good one, i fixed it !

:star2:

Capacitor Platform. => Capacitor platform.


Uri gets cut after buildUri method in Client class.

GuzzleHttp version: 6.5
The $uri gets transformed when passing it thru buildUri() method in GuzzleHttp\Client class.
public function test_get_all_users()
    {
        $response = $this->getJson('api/gcs-apps/gcs-helpdesk/users');
        $response->assertSuccessful();
        $response->assertHeader("content-type", 'application/json');
    }

From GuzzleHttp\Client@buildUri:
private function buildUri($uri, array $config)
    {
        // for BC we accept null which would otherwise fail in uri_for
        $uri = Psr7\uri_for($uri === null ? '' : $uri);

        if (isset($config['base_uri'])) {
            $uri = Psr7\UriResolver::resolve(Psr7\uri_for($config['base_uri']), $uri);
            dd($uri); // die and dump here
        }
...

Output (Not Intended URI):
GuzzleHttp\Psr7\Uri {#1218
  -scheme: "http"
  -userInfo: ""
  -host: "localhost"
  -port: 8000
  -path: "/api/gcs-apps/users"
  -query: ""
  -fragment: ""
}

If die and dump without passing the $uri thru the Psr7\UriResolver::resolve() method:
private function buildUri($uri, array $config)
    {
        // for BC we accept null which would otherwise fail in uri_for
        $uri = Psr7\uri_for($uri === null ? '' : $uri);

        if (isset($config['base_uri'])) {
            $uri = Psr7\UriResolver::resolve(Psr7\uri_for($config['base_uri']), $uri);
            dd(Psr7\uri_for($config['base_uri']));
        }
...

Output (Intended URI):
GuzzleHttp\Psr7\Uri {#1216
  -scheme: "http"
  -userInfo: ""
  -host: "localhost"
  -port: 8000
  -path: "/api/gcs-apps/gcs-holocron"
  -query: ""
  -fragment: ""
}

Seems it only can resolve endpoints no longer than 3 segments causing 404 errors due to unexistent endpoint.

I'm not sure if this applies to your case or not, but if you are using a base_uri, it should have a trailing slash.  See docs at: http://docs.guzzlephp.org/en/stable/quickstart.html#creating-a-client.  This was the cause of my issue at least.

@bpalme  I'll give it a try next time and come back to post my results, I appreciate your time.

Did the doc link helped you out?


this is cool.. but newest build not working

I have tried FantasticFox's build - which looks more like the original and working a bit.. although it's getting stuck on loading the tracks.. The one here is blue? new theme? and not working much at all :( very cool idea! want to play 👍

Thanks yungcloud. Sorry about the errors.  We are working on a new theme as well as a few cool new features, but my work has kept me away from the project this past week.  Hopefully we will have our first packaged build for available for download soon.
I had another user report problems with the current branch but I've been unable to replicate them on my machine.  If you open the developer tools, find the error and post a screenshot. I can try and debug it for you sometime this weekend.
Thanks again for checking out our project!

cool.. yea.. let me know if you update, once a more stable build is ready we could contribute!


[backend-dart] Create a client library for Dart

To start the mobile initiatives, having a client library written in Dart would help get things started.
This would need to replicate the Go and Node libraries.

I am interested in this, could you assign this to me?

Hey @sarkarshuvojit thanks - I've created the repo feel free to create a PR whenever you want.
Let me know if I can help with anything.

Thanks, will start it on and keep you updated.

Hi @dstpierre, I was a bit unwell the past few months and have started working on the library now. Creating the structure for this project based on the go/nodejs library as you mentioned.
Can I create incremental PRs per module, otherwise it might take quite a while for me to complete integrating all?
For example, I can create one PR after I complete writing the client code & tests for account-related apis.

Hey @sarkarshuvojit no worries and sorry for the delayed reply.
You may proceed as you prefer in the backend-dart project, either have a continuous PR where you add commits over time or have one when you feel it's time to create it. Up to you.


host no longer crashes on quit, when plugin was not instantiated (e.g…

prevents host from crashing on quit in case plugin could not be loaded,  e.g. wrong CLAP version. In that case the _plugin is a nullptr in unload.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Frank Hoffmann seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Spinner in initial loading screen should be white

As of now only black spinning progress is showing up in the beta.

Thanks for the report! Could you please be more specific? Where are you looking for the white spinner to appear; is it possible to post a screenshot? Also, are you on iOS or Android?

Since I have  downloaded the beta version of zulip.I have always felt the spinning progress bar at the start a little bit annoying. When I was going through the zulip Mobile codebase I found a file which corresponds to the progress bar white so I thought it might not be working.

Hi, I think didn't get what you are trying to tell.
Can you be more specific what is current behaviour and what should be expected, maybe with image/gif of both.

@harshbisle said:

I have always felt the spinning progress bar at the start a little bit annoying

This sounds like the main idea, to me, is that right? From that screenshot, I don't see anything going wrong related to spinning-progress-white.png. Currently, the white version is only used when "white" is passed as the color prop to the LoadingIndicator component, which currently is the cases only on some instances of the LoadingBanner, which looks like this:

I wonder if your concerns would be addressed with https://github.com/zulip/zulip-mobile/issues/2756.

@chrisbobbe Sorry to that I misinterpreted Since the color of 'Z' in the logo is white, I think that the color of spinning progress wheel should be white.

@chrisbobbe Sorry that I misinterpreted Since the color of 'Z' in the logo is white, I think that the color of spinning progress wheel should be white.

OK! I've just updated the title to match this.
Here's a screenshot of it with the white version. It's a very easy code change in src/start/LoadingScreen.js:
- <LoadingIndicator color="black" size={80} showLogo />
+ <LoadingIndicator color="white" size={80} showLogo />

so the main thing will be to decide whether we like this design better. Here it is with white instead of black:

tagging @gnprice @ray-kraesig just for quick visual design feedback (this new version, in white, vs. the current, black, posted above). I don't have a strong preference for one or the other.

I slightly prefer the black version – though, to be honest, I don't think I'd even have noticed if it had just been quietly changed.
(I think my real preference would be to make it the same dark grey as the logo background, but unfortunately that's rather more work.)


added template delete/list/paste command. renamed settemplate -> temp…

…lateset to be uniform with rest of naming scheme. will update messages in message file accordingly tomorrow.

Make sure to run the linter on all the calsses


improvement Add Connection Keepalive and Detailed Error Messaging for Druid Pool in FE

Proposed changes
Issue Number: close #xxx
In this PR, we've made improvements to the JDBC Catalog in the Frontend (FE) of Doris, specifically when connecting to the JDBC Catalog via the Druid connection pool.
Changes include:

Connection Keepalive Mechanism: We've added a connection keepalive mechanism to the Druid connection pool to prevent connections from becoming inactive during long periods of inactivity. This is achieved by setting a validation query that is executed periodically on idle connections. The queries are database-specific (Oracle, SAP HANA, etc.) to ensure compatibility.

Detailed Error Messaging: We've improved error messaging by throwing more specific exceptions when a connection error occurs in the Druid connection pool. This change will provide more detailed error messages, aiding in understanding and debugging connection-related issues.

These improvements will make the JDBC Catalog more robust and easier to maintain, particularly in scenarios where connections in the Druid connection pool are expected to be idle for extended periods of time.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


LibratoWriter includes descriptive User-Agent

I'm from the Librato team. It would help us to include a descriptive User-Agent header in the LibratoWriter that includes "jmxtrans" and the version number of jmxtrans, eg. "jmxtrans/1.2.3". This would assist in our debugging when working with users that are sending data with jmxtrans to Librato.
We have a full write-up here: http://support.metrics.librato.com/knowledgebase/articles/175825-how-to-set-a-custom-user-agent-when-integrating-wi

That would definitely be a welcomed contribution ! I'll promise to port it fast to JmxTrans 2 ... (but let me keep "fast" loosely defined).


Ctor parameter is not filled, when it was mapped with custom name (like "_id")

Hi!
It seems like CreateInstance factory is initialized after Entity<>() was called, but before any field mapping was set - BsonMapper.cs#L316. That's why CreateInstance doesn't respect 'Key' field from repro, since in BsonDocument it was stored as "_id".
Note: [BsonId] on Key field works fine. Can be used as workaround.
Minimal repro:
public class CustomMapping_Tests
{
    public class UserWithCustomId
    {
        public int Key { get; }
        public string Name { get; }

        public UserWithCustomId(int key, string name)
        {
            this.Key = key;
            this.Name = name;
        }
    }

    public CustomMapping_Tests()
    {
        _mapper.Entity<UserWithCustomId>()
            .Id(u => u.Key, false);
    }

    private BsonMapper _mapper = new BsonMapper();

    [Fact]
    public void Custom_Ctor_With_Custom_Id()
    {
        var doc = new BsonDocument { ["_id"] = 10, ["name"] = "John" };

        var user = _mapper.ToObject<UserWithCustomId>(doc);

        user.Key.Should().Be(10); //     Expected user.Key to be 10, but found 0.
        user.Name.Should().Be("John");
    }
}

Version: v5-alpha

Hi @Tirraon, thanks for this! I fixed in current master branch and will be available in beta version (next week).

@mbdavid
Thanks! I will merge it to my fork and check on this weekend.
I will close issue after.


gopass generate --clip not copying to clipboard

Summary

The --clip option of the gopass generate command no longer works. Using git bisect I found that this regression was introduced by #1806.
Steps To Reproduce

Using a clean build from source (from 877c3d8f or later):
$ ./gopass generate -c -f temp/temp 24
✅ Password for entry "temp/temp" generated
Not printing secrets by default. Use 'gopass show temp/temp' to display the password

No password is copied to the clipboard.
Expected behavior

Using a clean build from source (from v1.12.1):
$ ./gopass generate -c -f temp/temp 24
✅ Password for entry "temp/temp" generated
✔ Copied temp/temp to clipboard. Will clear in 45 seconds.
Copied to clipboard

Environment

OS: Solus
OS version: Linux enterprise 5.11.6-174.current #1 SMP PREEMPT Thu Mar 11 17:53:06 UTC 2021 x86_64 GNU/Linux
gopass Version: 1.12.2, 877c3d8, master
Installation method: from source

This looks suspicious.

Thanks for using bisect to find the culprit commit. That helped a lot!