feat(button): adding active prop to Button

Button( active prop )
This PR will introduce possibility to specify active buttons. Most of the code logic have been picked up from #14.
TODO

[ ] Conformance test
[x] Minimal doc site example
[ ] Stardust base theme
[x] Teams Light theme
[ ] Teams Dark theme
[ ] Teams Contrast theme
[ ] Confirm RTL usage
[ ] W3 accessibility check
[ ] Stardust accessibility check
[ ] Update glossary props table
[ ] Update the CHANGELOG.md

API Proposal
active

active property will make buttons in active state by manipulating backgroundColor
<Button active content="click" />

<button class="ui-button" active="">
  Click me
</button>

@jurokapsiar It was a typo. I meant to say active property.


Add stratagem endpoints to end point exception

Add stratagem endpoints to end point exception
Signed-off-by: Will Johnson<EMAIL_ADDRESS>

Codecov Report

Merging #1037 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1037   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 0087867...ba5f960. Read the comment docs.


Can not parse a valid csv file

Can't parse a valid csv file.
Failed to parse with "jquery.csv:250 Uncaught Error: CSVDataError: Illegal Quote [Row:5][Col:1]" message
Looks like its a valid file - tested with online CSV Lint(validator) and Google spreadsheet.
(Uploaded the tested data :
https://dl.dropboxusercontent.com/u/1791448/errorcsv.csv )

Looks like there were some errors while processing the input text.
Forget about it. :)

Haha. The GIGO struggle is real.
Thanks for taking the time to double-check the input. Saves me from having to chase phantom bugs.


deleting emails may change messageIDs stored in Email object

Currently a dynamic message id is stored in an email object. The message ids are enumerated beginning from 1 on the server. If a email is removed out of our system from the server, the stored message ids may not be up to date.
This could be fixed by a server wide global message id or by fetching the message ids every time before they are used.

Closed because we use UIDs at the moment


hotfix: avolid auth for yunionmeta dbinstance_skus

这个 PR 实现什么功能/修复什么问题:
meta 服务的rds套餐不需要认证
是否需要 backport 到之前的 release 分支:
None
/area region
/cc @swordqiu @yousong

Codecov Report

Merging #2790 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #2790      +/-   ##
=========================================
- Coverage    7.21%   7.21%   -0.01%
=========================================
  Files         472     472
  Lines       74601   74601
=========================================
- Hits         5384    5382       -2
- Misses      68765   68766       +1
- Partials      452     453       +1

Flag
Coverage Δ

#aFlag
7.21% <ø> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

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 d29b4fb...2dd60a7. Read the comment docs.

/approve
/lgtm


[question] Theoretical bound for the Connector env

Hey,
Is there a theoretical bound on the Connector env that the solution will always exist (even if suboptimal) for the agents such that there's no overlapping paths?

Hi @clement-bonnet,
Thank you for the quick reply. I found the generators here but wasn't able to find the ratio_connections metric, is it in a seperate place?
Also, I was wondering if it makes sense to penalise the agent for the episode if the solvability is not guaranteed?

ratio_connections is returned as an extras metric inside the timestep object which is the output of the reset or step function. The ratio is computed as part of the environment dynamics in here.
Regarding the reward, you may implement the reward you wish here. The dense reward formulation which is already implemented gives a small penalty per timestep, encouraging fast wiring. Indeed, when the instance is not solvable, the penalty will be given at each timestep until the horizon is reached. Although I don't think this is a problem, it does make more sense to combine this reward with a solvable generator. I would recommend using the solvable generator (RandomWalkGenerator). Hope this answers your question.

Thank you so much for the response Clement. Lastly, was the connector env introduced in the jumanji paper or is there any precursor to it?

Hey @ashok-arora I implemented this a while ago, but I'm not aware of any previous environment that this is based on. It was just meant to be a very simple PCB routing env

I'm closing this as it seems to be resolved.


Integrating firebase database in django

Article checklist
Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #3658.

hello @shosenwales
Consider reading the docs to get the process of opening a pull request.
ping me if you have any troubles doing the same.
Thanks

Hi @jerimkaura ,
I think i might need help

Fixes #3685

Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept.
Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content.
Be sure to see our resources page to see more info on plagiarism and what is considered as such.
Integrating firebase database in django

@shosenwales, please remember to follow the Topic suggestion this closes instructions in the PR template correctly to link your topic suggestion to your PR. This helps ensure a swift payout.
You should remove the backticks from the line below and add your issue number there. You added it in a new comment which doesn't work. It must be in the initial comment.

Hi @louisefindlay23
I don't really get you. Could you please re-explain

@shosenwales, I've made a screencast which should show what I mean. Let me know if you need any further clarification.
I've made the changes for you in this PR but in the future, make sure to link them correctly.

@louisefindlay23
Thanks.

Hi @ahmadmardeni1
Made some fixes, kindly go through.

@jerimkaura thanks i will

Plagiarism check done ✅


return node is not a swarm when unlock a normal node

Hi, All,
I found that in docker/master, cluster has been refactored.
And when I test new code, I found that unlock a normal node, daemon returns swarm is not locked. I think it is better to return an error "this node is not swarm manager...."
- What I did

make daemon return more accurate error
add a test case to verify this.

This did the same thing as https://github.com/docker/docker/pull/28533
/cc @aaronlehmann @tonistiigi
Signed-off-by: allencloud<EMAIL_ADDRESS>

/cc @aaronlehmann @tonistiigi

LGTM

I am afraid the windows CI fails unexpectedly.

ping @aaronlehmann PTAL

LGTM
Feel free to make the change I suggested if you want, but I think this is fine to merge as-is.


unsaved_SRAM and status dicts are  shared by all instances

The Device.unsaved_SRAM and Device.status dictionaries are class attributes shares by all instances. Since they're mutable, this means multiple instances are actually modifying and reading the same dictionaries, leading to incorrect behaviour when talking to two MCP2221s from the same Python process.
This can be fixed by simply by assigning these two dicts as instance attributes self.unsaved_SRAM and self.status in __init__ instead of at the class level.

Hello.
AFAIK class variables need to be addressed with the Class name, like this:
class c:
    foo = 1

    def __init__(self):
        self.bar = 1

    def __str__(self):
        return "foo: %d   bar: %d" % (c.foo, self.bar)

    def incr(self):
        self.bar = self.bar + 1
        c.foo = c.foo + 1

c1 = c()
c2 = c()

print(c1)
print(c2)
c1.incr()
print(c1)
print(c2)

After call c1.incr(), both "foo" values do increase:
foo: 1   bar: 1
foo: 1   bar: 1
foo: 2   bar: 2
foo: 2   bar: 1

But, as long as you address foo via self, it will be an instance variable:
class c:
    foo = 1

    def __init__(self):
        self.bar = 1

    def __str__(self):
        return "foo: %d   bar: %d" % (self.foo, self.bar)

    def incr(self):
        self.bar = self.bar + 1
        self.foo = self.foo + 1

c1 = c()
c2 = c()

print(c1)
print(c2)
c1.incr()
print(c1)
print(c2)

Result: only c1's foo have been inrceased:
foo: 1   bar: 1
foo: 1   bar: 1
foo: 2   bar: 2
foo: 1   bar: 1

I can manage multiple MCP2221 at the same time with no problem:

Please, could you elaborate your issue with a code example?
Thank you.

AFAIK class variables need to be addressed with the Class name, like this:

This is correct if you're talking about modifying immutable types as with your example with integers, since immutable types can't actually be modified, only be reassigned. So when you access and reassign the attribute via the instance, you're actually just creating a new instance attribute and not changing the class attribute. So there's no problem with all the immutable class attributes in the MCP2221.Device class.
However, for mutable datatypes such as dictionaries, the situation is different. They can be modified without being reassigned, whether they are accessed via the instance or the class:
class c:
    x = {'value': 0}
    def __init__(self):
       self.x['value'] += 1
       print(self.x['value'])

c()
c()
c()
c()

1
2
3
4

This problem is similar to use of mutable default function arguments in Python. Mutable class attributes should be avoided unless you actually do want them to be shared by all instances.
I don't have an example of incorrect behaviour since I don't really know what these dicts are used for, but if they're used for anything important then I'm sure there is incorrect behaviour somewhere, since there is only one of each of unsaved_SRAM and status dictionary shared by all instances. I don't have access to hardware at the moment to test, but if you instantiate two MCP2221s in the same Python process and print their "status" dictionaries, you will find that they are the same.

You are right. Thank you. I moved these variables to the init function. Happy to learn something new today.


Code128

Hi, this does not scan a code128 type. Tried with QR and it's working,

Can you provide more detail? On which platform does this not scan code128? Did you specify code128 as type?

Code 128 seems to work on Android, but not iOS

Hi, are there any updates regarding this issue? Also, all EAN formats are not being read on iOS, although they work fine on Android.

Thanks for the PR, fixed in 0.1.6 which should be available any minute.


[Backport 1.3] Bump reactor-netty-http to 1.0.24 in repository-azure

Signed-off-by: Ryan Bogan<EMAIL_ADDRESS>Description
Bumps reactor-netty-http to 1.0.24 in repository-azure
Issues Resolved
CVE-2022-31684
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[ X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #6022 (7546b49) into 1.3 (4350ea9) will increase coverage by 0.05%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##                1.3    #6022      +/-   ##
============================================
+ Coverage     77.82%   77.88%   +0.05%
- Complexity    63394    63465      +71
============================================
  Files          4454     4454
  Lines        274944   274944
  Branches      41166    41166
============================================
+ Hits         213988   214148     +160
+ Misses        44033    43920     -113
+ Partials      16923    16876      -47

Impacted Files
Coverage Δ

...g/opensearch/index/analysis/CharFilterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../action/ingest/SimulatePipelineRequestBuilder.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...org/opensearch/indices/IndexCreationException.java
60.00% <0.00%> (-40.00%)
:arrow_down:

...pensearch/transport/NodeDisconnectedException.java
60.00% <0.00%> (-40.00%)
:arrow_down:

...ion/admin/cluster/node/info/PluginsAndModules.java
53.12% <0.00%> (-34.38%)
:arrow_down:

...rch/client/transport/NoNodeAvailableException.java
71.42% <0.00%> (-28.58%)
:arrow_down:

...rc/main/java/org/opensearch/ingest/IngestInfo.java
51.72% <0.00%> (-27.59%)
:arrow_down:

...va/org/opensearch/client/sniff/SnifferBuilder.java
72.72% <0.00%> (-27.28%)
:arrow_down:

...nsearch/index/shard/IndexingOperationListener.java
63.93% <0.00%> (-22.96%)
:arrow_down:

...lucene/index/SequentialStoredFieldsLeafReader.java
77.77% <0.00%> (-22.23%)
:arrow_down:

... and 486 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add IN-12B Nixie Tubes

SUMMARY
Add IN-12B Nixie Tubes.

Note: Initially I was confused about the relation between Sovtek and Reflektor. According to ChatGPT (I plausibilized the statement), Sovtek is the brand and Reflektor is the production plant (owned by the USSR).

DATASHEETS / REFERENCES

https://www.tube-tester.com/sites/nixie/data/in-12b.htm
https://www.tube-tester.com/sites/nixie/dat_arch/IN-12A_IN-12B_01.pdf

OPEN QUESTIONS / UNRESOLVED ISSUES
n/a
CHECKLIST

[x] I have read and followed the library conventions¹.
[x] For packages, I followed IPC7351C (see details in library conventions).
[ ] For modified elements, I bumped their version number².
[x] I already used the new library elements in a design and verified their correctness (optional).
[x] I'm the copyright owner of the added content (i.e. the changes are made by myself, not copied/imported from somewhere else).
[x] I agree to publish all my changes under the CC0 Public Domain License³, allowing everyone to use and modify the content without any restrictions.

¹ Library Conventions: https://docs.librepcb.org/#libraryconventions
² Minor version bump if only metadata was modified (e.g. "0.1" -> "0.1.1"), major version bump if functional changes were made (e.g. "0.1" -> "0.2")
³ CC0 Public Domain License: https://en.wikipedia.org/wiki/CC0

Theoretically the documentation polygon is missing

Oops, you're right!

and the legend polygon should be outside the package outline (currently both polygons are identical):

I originally kept them like that because every tube has slightly different dimensions, so it won't be exact anyways. But since I edited the outlines to add the documentation layer, I also fixed that one.


[BUG] When providing -b arg, the folder is not completely rebuilt, but copied in to.

When providing a build path with -b, the path does not get cleared as it does when the argument is omitted.
The asset-manifest is deleted and re-created so there is no risk (read very little, there is always a risk 😉) of a build using the wrong files so expected current impact of the bug is minimal.

Examples;
Running with -b arg
cra-build-watch -b dist/ --chunk-filename './test_1/[name].[hash].js'
cra-build-watch -b dist/ --chunk-filename './test_2/[name].[hash].js'
+---dist
|   |   asset-manifest.json
|   |   favicon.ico
|   |   index.html
|   |   manifest.json
|   |
|   +---js
|   |       bundle.js
|   |       bundle.js.map
|   |
|   +---test_1
|   |       0.04b6ae9291b3834ef72a.js
|   |       0.04b6ae9291b3834ef72a.js.map
|   |       main.04b6ae9291b3834ef72a.js
|   |       main.04b6ae9291b3834ef72a.js.map
|   |
|   \---test_2
|           0.04b6ae9291b3834ef72a.js
|           0.04b6ae9291b3834ef72a.js.map
|           main.04b6ae9291b3834ef72a.js
|           main.04b6ae9291b3834ef72a.js.map

Running without -b arg
cra-build-watch --chunk-filename './test_1/[name].[hash].js'
cra-build-watch --chunk-filename './test_2/[name].[hash].js'
+---build
|   |   asset-manifest.json
|   |   favicon.ico
|   |   index.html
|   |   manifest.json
|   |
|   +---js
|   |       bundle.js
|   |       bundle.js.map
|   |
|   \---test_2
|           0.04b6ae9291b3834ef72a.js
|           0.04b6ae9291b3834ef72a.js.map
|           main.04b6ae9291b3834ef72a.js
|           main.04b6ae9291b3834ef72a.js.map

Hum interesting indeed. I haven't had the time to reproduce it yet on Linux but there definitely seems to be a bug on your environment at least.

Sorry I don't have time to maintain this project anymore so I'll archive it and add a note in the README. Feel free to fork it as you see fit.


fix: usage with tokio panics

fixes https://github.com/makarski/gauth-rs/issues/25

at this stage all the tests are disabled. as most of the functions are now async, we're required to have an async test library. tokio::test would probably do the trick, should I go ahead and implement tokio::test? @makarski

I've just converted the tests that require async from #[test] to #[tokio::test]

Thank you @adnanjpg! at the first glance this looks good 👍 I will have a more closer look in the afternoon so that we can go over feedback if any and get the change in.

Thank you for the PR, looks good to merge. It would be great also to update the README file code snippets.

sure, but should I just go ahead and make all the examples in the README use tokio?
like:
#[tokio::main]
async fn main() {
    gauth::serv_account::ServiceAccount::from_file(
        "service-account-key.json",
        vec!["https://www.googleapis.com/auth/firebase.messaging"],
    );
}

That'd be great

@makarski please check the updated README

@adnanjpg just publish v0.6 with your changes https://crates.io/crates/gauth/0.6.0 - many thanks! 🚀

@makarski thanks to you for maintaining this amazing package 🙏


[bug]The evaluation of live_parallel and rest may have some problem

BFCL_v2_live_parallel.json
The first eight samples in BFCL_v2_live_parallel.json are problems on using the get_current_weather function. However, the possible answer is that only Fahrenheit units are allowed, although both Celsius and Fahrenheit are okay. This affects the performance of some models.
BFCL_v2_rest.json
For some instances, an auth param is needed, a tuple-type object. However, the tuple type is not supported in the JSON schema, so the tuple type is converted to the list type. Many function-call APIs will return an auth param with list type. When executing requests.get, this will be an error.

Execution failed. 'list' object is not callable

Hey @Cppowboy,
Regarding your first question on live_parallel. It is indeed that only fahrenheit is allowed. This is because the unit is a  optional parameter, and the prompt didn't imply anything regarding fahrenheit or celsius. So its default value should be used.
{
    "id": "live_parallel_2-0-2",
    "question": [
        {
            "role": "user",
            "content": "<<question>> What\\'s the weather like in the two cities of Boston and San Francisco?"
        }
    ],
    "function": [
        {
            "name": "get_current_weather",
            "description": "Retrieves the current weather conditions for a specified city and state.",
            "parameters": {
                "type": "dict",
                "required": [
                    "location"
                ],
                "properties": {
                    "location": {
                        "type": "string",
                        "description": "The location for which to get the weather, in the format of 'City, State', such as 'San Francisco, CA' if State for the city exists. 'City, Country' if State for the city doesn't exist."
                    },
                    "unit": {
                        "type": "string",
                        "description": "The unit of temperature for the weather report.",
                        "enum": [
                            "celsius",
                            "fahrenheit"
                        ],
                        "default": "fahrenheit"
                    }
                }
            }
        }
    ]
}

BFCL_v2_rest.json
For some instances, an auth param is needed, a tuple-type object. However, the tuple type is not supported in the JSON schema, so the tuple type is converted to the list type. Many function-call APIs will return an auth param with list type. When executing requests.get, this will be an error.

Your observation of "Many function-call APIs will return an auth param with list type. " is a result of casting gorilla types to OAI types for many model styles here https://github.com/ShishirPatil/gorilla/blob/main/berkeley-function-call-leaderboard/model_handler/utils.py#L71-L73. So, tuples are all casted to lists in the function documents.
During evaluation, the right thing to do is to cast it back to tuple. In the current pipeline, we didn't implement this. This won't affect AST because we compare with list possible answers. It won't affect executable python functions (simple, multiple, parallel, parallel multiple) since all functions can function correctly on lists even though they are specified as tuple in the function document.
For REST category, all auth parameters are optional for the 70 data points ground truth https://github.com/ShishirPatil/gorilla/blob/main/berkeley-function-call-leaderboard/eval_checker/api_status_check_ground_truth_REST.json. So the correct model output is either don't specify auth in the function call, or specify auth=().
I just double checked requests.get won't error on either auth=[] or auth=() for an example REST API.
>>> requests.get(url='https://date.nager.at/api/v3/LongWeekend/2023/CA', auth=()).json()
[{'startDate': '2023-04-07', 'endDate': '2023-04-09', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-05-20', 'endDate': '2023-05-22', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-09-02', 'endDate': '2023-09-04', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-10-07', 'endDate': '2023-10-09', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-12-23', 'endDate': '2023-12-25', 'dayCount': 3, 'needBridgeDay': False}]
>>> requests.get(url='https://date.nager.at/api/v3/LongWeekend/2023/CA', auth=[]).json()
[{'startDate': '2023-04-07', 'endDate': '2023-04-09', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-05-20', 'endDate': '2023-05-22', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-09-02', 'endDate': '2023-09-04', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-10-07', 'endDate': '2023-10-09', 'dayCount': 3, 'needBridgeDay': False}, {'startDate': '2023-12-23', 'endDate': '2023-12-25', 'dayCount': 3, 'needBridgeDay': False}]

So it won't have effects on scores. I haven't encounter "Execution failed. 'list' object is not callable" you have pointed out, can you provide an example?
Thanks


[3.0] bug: logo doesn't show in header when viewport has 590+px width

but it shows on smaller widths, up to 580px:

works fine in beta1, thanks!


CITE-seq-Count for multimodal data

Hi,
Thanks for developing this great tool. I just have 2 questions regarding CITE-seq-Count.
Question1:
So, I have a multimodal scRNAseq dataset in which both CITEseq and Hashtag antibodies were pooled together in one R1/R2 pair. I was wondering if CITE-seq-Count can handle such multimodal data.
Specifically, should I run CITE-seq-Count twice to count CITEseq and Hashtag separately like following:
CITE-seq-Count -R1 R1  -R2 R2 -t Hashtag_antibodies -wl whitelist -cbf 1 -cbl 16 -umif 17 -umil 28 -cells cell_number --start-trim 10 -o output_folder
CITE-seq-Count -R1 R1  -R2 R2 -t CITEseq_antibodies -wl whitelist -cbf 1 -cbl 16 -umif 17 -umil 28 -cells cell_number --start-trim 10 -o output_folder
Or just put all antibodies in one csv and run it once like the following:
CITE-seq-Count -R1 R1  -R2 R2 -t Hashtag_plus_CITEseq_antibodies -wl whitelist -cbf 1 -cbl 16 -umif 17 -umil 28 -cells cell_number --start-trim 10 -o output_folder
Question 2:
This is a whole tissue sequencing, meaning that I will get a lot of unmapped reads in the CITEseq output because the CITEseq Abs are specific. Should I remove the unmapped row from the matrix before normalization?
Thanks for you time

@YingzhengXu : Where you able to answer your concern. If Yes. Can you please comment how you handled it. I am having the same question.
Thanks in advance

@YingzhengXu : Where you able to answer your concern. If Yes. Can you please comment how you handled it. I am having the same question.
Thanks in advance

Hi,
I was able to solve it. I ran CITE and Hashtag Abs separately.  Just give it a try to see which method is better for you. Let me know if you have any other questions I can help with.

@YingzhengXu : Thanks understood. Final question Did you ran the citeseq on the Raw run or on the 10x cellranger outs?

@YingzhengXu : Thanks understood. Final question Did you ran the citeseq on the Raw run or on the 10x cellranger outs?

I assume you meant by fastq files by “raw run”. Yes, you use fastq files as input. CITEseq count is basically an alignment/mapping tool, so you should run it on fastq files.

@YingzhengXu : I ma little confused now. Does that mean Once I used CITSeq count I don't use the 10x cellranger?

@YingzhengXu : I ma little confused now. Does that mean Once I used CITSeq count I don't use the 10x cellranger?

You use both pipelines for different purpose. cellranger provides fastq (output of mkfastq) and rna expression matrix(output of count); where CITE-seq-count is specifically for generating matrix for cite seq antibodies or hashtags. In a Seurat object, you save these matrices(RNA, citeseq, hashtag) in different assay slots.
If you have ran mkfastq, use the output fastq files as input for CITE-seq-count to generate additional matrix.
Additionally, use cellranger count output as the main RNA expression matrix for RNA assay slot in Seurat.

@YingzhengXu : I ma little confused now. Does that mean Once I used CITSeq count I don't use the 10x cellranger?

You use both pipelines for different purpose. cellranger provides fastq (output of mkfastq) and rna expression matrix(output of count); where CITE-seq-count is specifically for generating matrix for cite seq antibodies or hashtags. In a Seurat object, you save these matrices(RNA, citeseq, hashtag) in different assay slots.
If you have ran mkfastq, use the output fastq files as input for CITE-seq-count to generate additional matrix. Additionally, use cellranger count output as the main RNA expression matrix for RNA assay slot in Seurat.

Hi @YingzhengXu I am new to CITE-seq data analysis and am using Seurat as well. I was wondering how you were able to integrate the citeseq matrix with the main RNA expression matrix but get a "All cells in the object being added must match the cells in this object" error. Is it because the barcodes in the cellranger RNA matrix have "-1" at the end and the barcodes for CITE-seq-Count don't?

@YingzhengXu : I ma little confused now. Does that mean Once I used CITSeq count I don't use the 10x cellranger?

You use both pipelines for different purpose. cellranger provides fastq (output of mkfastq) and rna expression matrix(output of count); where CITE-seq-count is specifically for generating matrix for cite seq antibodies or hashtags. In a Seurat object, you save these matrices(RNA, citeseq, hashtag) in different assay slots.
If you have ran mkfastq, use the output fastq files as input for CITE-seq-count to generate additional matrix. Additionally, use cellranger count output as the main RNA expression matrix for RNA assay slot in Seurat.

Hi @YingzhengXu I am new to CITE-seq data analysis and am using Seurat as well. I was wondering how you were able to integrate the citeseq matrix with the main RNA expression matrix but get a "All cells in the object being added must match the cells in this object" error. Is it because the barcodes in the cellranger RNA matrix have "-1" at the end and the barcodes for CITE-seq-Count don't? Thanks for your help!

Hi,
You were right about the "-1" attachment. I assume you have removed "-1" but did not remove cells that don't match after that. A simple solution would be: find the overlapping barcodes between citeseq and RNA matrix, remove the barcodes that don't match, then integrate.
Here's a simple template for it:
intersect<-instersect(colnames(citeseq_matrix), colnames(RNA_expression_matrix))
citeseq_matrix<-citeseq_matrix[,intersect]
RNA_expression_matrix<-RNA_expression_matrix[,intersect]
seurat_obj<-CreateSeuratObject(counts=RNA_expression_matrix)
seurat_obj[['CITE']]<-CreateAssayObject(counts=citeseq_matrix)
If you get few cells that overlap, try to run CITEseqCount with a whitelist (generated from cellranger, barcodes.tsv) provided to the -wl argument. This will force citeseq to look for the barcodes that are already in the whitelist.
Let me know if I can further help


When running the checker, it "spams" the terminal and freezes the UI

What's broken?
When the analysis process  is running, the terminal continues beeps and asks for focus (Mac non-M1 here). This makes the terminal to beep and kinda freezes the UI.

Version used
latest on this date
Context
Simple or complex repos, same result

I saw this happening with iTerm, but not with the default terminal that comes with MacOS.
Probably this happens due to the progress bar cursor relocation. We need to investigate how to avoid this.


Update UG for FindCommand

Describe your changes

Update content of FindCommand to reflect latest changes
Update image for FindCommand example
Add tips
Add common mistakes

Issue ticket number and link
closes #155
Checklist before requesting a review

[X] I have performed a self-review of my code.
[X] If it is a core feature, I have added thorough tests.

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


why second request Throw out Error: write after end In watch-server

  Error: write after end
      at writeAfterEnd (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_writable.js:288:12)
      at PassThrough.Writable.write (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_writable.js:332:20)
      at File.log (D:\Code\Github\demo-ts\node_modules\winston\lib\winston\transports\file.js:158:34)
      at File._write (D:\Code\Github\demo-ts\node_modules\winston-transport\index.js:81:19)
      at doWrite (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_writable.js:428:64)
      at writeOrBuffer (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_writable.js:417:5)
      at File.Writable.write (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_writable.js:334:11)
      at DerivedLogger.ondata (D:\Code\Github\demo-ts\node_modules\readable-stream\lib\_stream_readable.js:619:20)
      at emitOne (events.js:121:20)
      at DerivedLogger.emit (events.js:211:7)

I only open the db logger
createConnection({
    type: 'postgres',
    host: connectionOptions.host,
    port: connectionOptions.port,
    username: connectionOptions.user,
    password: connectionOptions.password,
    database: connectionOptions.database,
    synchronize: true,
    logging: false,
    entities: [
       'dist/entity/**/*.js'
    ],
    extra: {
        ssl: config.dbsslconn, // if not development, will use SSL
    }
 })

I think error is here
//
// - Write all logs error (and below) to `error.log`.
// new winston.transports.File({ filename: 'error.log', level: 'info' })

You are so right, I have a private application in production using the boilerplate and yesterday I also realised of this...
The error was when rewriting in the error.log file, as it was already closed by the time it was trying to write into it the new log line. I think the error started happening a couple of weeks ago when I updated Winston to 3.0.0 and had to modified a bit the logging.ts file... I have fixed it together with a small fix in the new release 1.4.1.
In addition, the log level was 'info' when is should be 'error', also modified it.
Thanks for catching that :)


feat: one to one relationship

@Rithingithub  i have temporarily removed swagger from app since it is not working as expected


[feat] Do not use Docker or Sandbox text in UX - change wording to just Local Clusters

Docker is a trademarked commercial company. We should avoid using the name Docker in this product.

"Docker Projects (Sandbox)" -> "Local Sandboxes"

@mhmdkrmabd I think we need to just say "Local Clusters" and remove the "Sandbox" reference. Can you updat the UX to no longer use the text sandbox or docker. Make sure to update the translations.

@millerjp working on that

@millerjp @hshimizu
https://github.com/user-attachments/assets/37dbbb16-0639-467e-aaa1-586e52ece573

looks great @mhmdkrmabd


suggestion: provide an overview of the files in the template

Describe the bug
Its not a bug :-)
for someone new to electron like me, like me, it would be useful to have in the documenation a section on pointers on the layout of the files in the template and where to begin customising this template.
To Reproduce
n/a
Expected behavior
n/a
Screenshots
n/a
Desktop (please complete the following information):
n/a
Additional context
I love that this works immediately! ive come across a lot of templates that didnt work first time. excellent work!

Hello. Thanks for your feedback!
I added a project structure page with a project tree and description attached. Hope this helps:
https://vutron.jooy2.com/project-structure.html
For other information, please check the Getting Started page of the documentation page.
Guidelines for beginners will be improved in the future. If you want to correct errors or add content to the documentation, you can always send us a pull request.
Thank you.


Issue#1682/repository simulator fetch tracker

This commit implements a feature in Repository Simulator to
track the fetch calls to the metadata and targets. This feature was
mentioned in PR #1666 that generated issue #1682.
This commit adds RepositorySimulator.fetch_tracker. It also changes
the tests/test_updater_consistent_snapshot.py to use the
fetch_tracker instead of using mock.
It implements a dataclass that stores the calls to fetch metadata
(_fetch_metadata) in fetch_tracker.metadata and targets
(_fetch_targets) in fetch_tracker.targets.
The fetch calls for metadata, and targets are stored as lists.
Signed-off-by: Kairo de Araujo<EMAIL_ADDRESS>Please fill in the fields below to submit a pull request.  The more information
that is provided, the better.
Fixes  #1682
Description of the changes being introduced by the pull request:
Please verify and check that the pull request fulfills the following
requirements:

[X] The code follows the Code Style Guidelines
[X] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.58%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4030

Relevant Lines:
4114

💛  - Coveralls

I closed this PR to avoid too many unrelated commits to fix my mess in merging the develop on top of kairoaraujo:issue#1682/repository-simulator-fetch-tracker branch.
The above-linked PR will be taking over with all relevant information.


[Docs]: Migrate changes from old to new docs

Type
Maintenance task
What do you want to report?
Migrate changes from old to new docs
Code of Conduct

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

Progress:

[X] September
[ ] August
[ ] July
[ ] June
[ ] May


[SuperEditor] Typing ~~ removes the text

Package Version
Latest main
To Reproduce
Steps to reproduce the behavior:

Go to SuperEditor demo
Type ~~

Actual behavior
The text is removed
Expected behavior
The text is preserved
Platform
Any platform
Flutter version
Fluter 3.22 or master channel
Additional context
This happens because the markdown plugin is attempting to use ~~ as a strikethrough syntax, even though there is no text between the characters.

cc @matthew-carroll


Adding non-serialisable metadata to toState

This is a follow up of https://github.com/router5/router5/issues/60#issuecomment-233296870
@troch I'm hitting the issue that @iotch mentioned.. I would like to attach non-serializable stuff into toState:
// getComponentMiddleware.js
export default (routes) => (router) => (toState, fromState) => {
    const { toActivate } = transitionPath(toState, fromState);

    // Get the routes involved in the transition
    const routesToActivate = toActivate.map((segment) => routes.find((route) => route.name === segment));

    // Build a map in which keys are the route names and values that resolve to their components
    const promisesMap = fromPairs(routesToActivate.map((route) => [route.name, route.component || route.getComponent()]));

    return pProps(promisesMap)
    .then((components) => ({ ...toState, components }));
};

DOMException: Failed to execute 'pushState' on 'History': An object could not be cloned.
So here are a few questions:

Do we really have to persist the state to the history api? browser.getState is only used here. Isn't it more correct to compare the URLs instead of comparing states? In my opinion, the browser plugin is just a way to set and react to URL changes, it shouldn't be storing nor handling states. Also, this would remove the inconsistency that exists now between using history API or hashbangs.
If you would like to keep it like this, could we have field that would not be included in the history state? This would allow us to add big data structures (big structures generate QUOTA errors) or unserializable data to be added to toState.

Thanks in advance.

@troch I'm really trying to use router5 and it looks like a great router to me, both conceptually and in terms of execution.
This middleware is just one of the ideas that I have to improve react-router5. Perhaps could we discuss this in gitter or something similar?

Personally, I find really interesting to persist the state in the browser history, in order to retreive “hidden” parameters when the user navigates with back and forward buttons.
However — tell me if I’m wrong — I think you can actually do what you want if you inject a mocked browser in the plugin factory, at the second argument:
import defaultBrowser from 'router5/plugins/browser/browser'

let savedState

const myCustomBrowser = {
    ...defaultBrowser,
    pushState(state, title, path) {
        window.history.pushState({}, title, path)
        savedState = state
    },

    replaceState() {
        // Similar hack
    },

    getState() {
        return savedState
    },

    // Unfortunately, you’ll probably also need to hack
    // `addPopstateListener` and `removePopstateListener`.
}

router.usePlugin(browserPlugin({}, myCustomBrowser))

There is something similar here.
In anyway, it’s probably too cumbersome and hackish and I’d be glad to know better ways to achieve it.

@motet-a you are right, we are able to do that. But I would like to avoid that and only use it as last resort.
One of the strong reasons to not store the state is that, right now, the browser plugin behave differently when using hash or not. But I'm fine if you want to keep the current functionality but I think we should be able to attach metadata into something like state.locals, quite similar to res.locals from express.

Yes. I think the best is to allow the user to customize entirely the way the state is stored with simple options. I think something in the spirit of react-redux could be suitable:
let savedBigData

function mapRouterStateToBrowserState({ bigData, ...state }) {
    savedBigData = bigData
    return state // Will be saved in window.history.state (bigData has been extracted)
}

function mapBrowserStateToRouterState(browserState) {
    return {
        ...browserState,
        bigData: savedBigData,
    }
}

router.usePlugin(
    browserPlugin({
        mapRouterStateToBrowserState,
        mapBrowserStateToRouterState,
    })
)

mapRouterStateToBrowserState and mapBrowserStateToRouterState can both default to an identity function, s => s. This is not breaking changes.

@satazor the state is added to the history so when going back and forward, paths don't have to be matched and states are already built.
I don't believe using hash or not makes a difference: in both cases the history API is used. What difference do you see?

@satazor this has been fixed with v4.7.1: only base state properties (meta, name, path and params) are pushed to history.


CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead   from cryptography.utils import int_from_bytes

When I run 01_setup_dependencies, I get the following error:
CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead
from cryptography.utils import int_from_bytes
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [18 lines of output]
Traceback (most recent call last):
File "", line 36, in
File "", line 34, in
File "/tmp/pip-install-p556_z83/termcolor_6e020657f5c345abad744de44dec15b6/setup.py", line 53, in
'Topic :: Terminals'
File "/opt/conda/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 109, in setup
_setup_distribution = dist = klass(attrs)
File "/opt/conda/lib/python3.7/site-packages/setuptools/dist.py", line 466, in init
for k, v in attrs.items()
File "/opt/conda/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 293, in init
self.finalize_options()
File "/opt/conda/lib/python3.7/site-packages/setuptools/dist.py", line 885, in finalize_options
for ep in sorted(loaded, key=by_order):
File "/opt/conda/lib/python3.7/site-packages/setuptools/dist.py", line 884, in
loaded = map(lambda e: e.load(), filtered)
File "/opt/conda/lib/python3.7/site-packages/setuptools/_vendor/importlib_metadata/init.py", line 196, in load
return functools.reduce(getattr, attrs, module)
AttributeError: type object 'Distribution' has no attribute '_finalize_feature_opts'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
Any pointers on how I can resolve this issue is greatly appreciated.
Thanks.

interesting.  need to track this down.
@antje have you seen this before?

@sirishageeth do you have a screenshot?  where are you running this?
I'm trying to reproduce - and I see the warning, but i am able to proceed.
send some more data and we'll try to debug this.


Count of how many of a certain item you have in your inventory

Would be useful when using superglassmake and buying from Charter Crewmembers on an ironman.

What did you have in mind on how it would be displayed?

Maybe an overlay similar to the team overlay?

Could get very cluttered though. It's possible, of course, though, can get quite messy.

This would be a summarized inventory viewer, basically.

Maybe an option for Inventory Viewer that shows a summary of your inventory instead of the full thing?

So why not just use inventory viewer at that point?

Well a number is easier than eyeballing it

Exactly. With for example 9 soda ash and 11 buckets of sand, it's difficult to see what you need to buy more of.

I still think its sort of dumb, but I guess we could add grouping to inventory viewer as toggle, why not.

Fulfilled by runelite/plugin-hub#189


how to create udp retention policy

Hi
I write data into influxdb by using UDP protocol. And I want to create a half_year retention policy for data that be written by UDP. I want to set this configure into config file and don't know how to do, can you give me an example for how to set my own udp retention policy in the config file ? Here is the UDP configure in the config file, I don't know how to set.
enabled = true
bind-address = ":38086"
database = "mkt_data"
retention-policy = ""

Answered here: https://community.influxdata.com/t/how-to-create-udp-retention-policy/1074


yarn create grandstack-app hanging on "Creating scripts configuration"

 ✖ Creating scripts configuration...
      → EEXIST: file already exists, mkdir '***************/grandStarter/scripts/config'
      Removing unused templates:
       ✔ web-react-ts
       ✔ web-angular
       ✔ mobile_client_flutter
    Initialize git
    Installing Packages with yarn
(node:885) UnhandledPromiseRejectionWarning: Error: EEXIST: file already exists, mkdir '***************/grandStarter/scripts/config'

Is the error I get. I am using the Neo4j online sandbox but I think there may be an issue with the Creating scripts configuration step.
How to resolve this error? I'm using WSL
Thanks

Hi @spritefullake I've just pushed an update that should fix this. Could you please try again?

Guess that was an incorrect assumption, going to use this issue to document either manual addition of config or update CLI to check and flag creation of config.

That brings up a good question - how should the start script handle your non-choice of frontend if you've cloned the repo instead of using create-grandstack-app CLI. I guess the start script should just default to React in the case of missing config.

@johnymontana Thank you, I tried again and it installed everything (the dependencies did take a while).

That brings up a good question - how should the start script handle your non-choice of frontend if you've cloned the repo instead of using create-grandstack-app CLI. I guess the start script should just default to React in the case of missing config.

yeh, that's what having this file there manually was meant to address, thought it would be overwritten...

@spritefullake yeh the deps take a minute. wonder if there is a good way to optimize that... ?


add opensuse-tumbleweed for aarch64

Description
Hello,
After some digging and copy pasting stuff around, I was able to make tumbleweed working on aarch64 using the following yaml config file:
images:
- location: http://download.opensuse.org/ports/aarch64/tumbleweed/appliances/openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64.qcow2
  arch: "aarch64"
mounts:
- location: "~"
- location: "/tmp/lima"
  writable: true
provision:
- mode: system
  script: |
    #!/bin/bash
    set -eux -o pipefail
    zypper refresh
    zypper install -y sshfs
    for FILE in fuse fuse3; do echo 'user_allow_other' >> "/etc/${FILE}.conf"; done

is it something I can propose a merge request in /examples/experimental/opensuse-tumbleweed.yaml ?
I would:

add the new aarch64 location
setup the script to have the requirement for mount point in place
keep the comments in place from the original file

However as I don't own a x64 mac machine I wouldn't be able to make sure that the script properly runs on x86_64. Maybe someone could review it and test it ? :)

Thanks, yes, PR is appreciated but the script should be placed in https://github.com/lima-vm/lima/blob/9daf5851ae9f0fcd739c7e260f3367268b5dda96/pkg/cidata/cidata.TEMPLATE.d/boot/30-install-packages.sh#L148

I'm not yet certain why but the script should already pick up the needed dependencies (sshfs, setting user_allow_other).
If I look at the logs, it seems the script is triggered a little bit too early in the process because refreshing the repository metadata is failing (apt can't resolve download.opensuse.org). If I use apt-get myself later in the process, it works (I'm also noticing that the network is reporting as online, which add a little to my confusion):
[...]
[  OK  ] Started OpenSSH Daemon.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
[  OK  ] Finished Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting Apply the settings specified in cloud-config...
[    9.340622] cloud-init[1026]: Cloud-init v. 21.4-2.2 running 'modules:config' at Sun, 07 Aug 2022 18:24:42 +0000. Up 9.31 seconds.
[  OK  ] Finished Apply the settings specified in cloud-config.
         Starting Execute cloud user/final scripts...
[    9.606469] cloud-init[1030]: Cloud-init v. 21.4-2.2 running 'modules:final' at Sun, 07 Aug 2022 18:24:42 +0000. Up 9.57 seconds.
[    9.665476] cloud-init[1030]: + LIMA_CIDATA_MNT=/mnt/lima-cidata
[    9.666248] cloud-init[1030]: + LIMA_CIDATA_DEV=/dev/disk/by-label/cidata
[...]
[   10.805500] cloud-init[1030]: + command -v newuidmap
[   10.805850] cloud-init[1030]: + '[' -n ' sshfs iptables' ']'
[   10.806245] cloud-init[1030]: + DEBIAN_FRONTEND=noninteractive
[   10.806659] cloud-init[1030]: + export DEBIAN_FRONTEND
[   10.807139] cloud-init[1030]: + apt-get update
[   11.009632] cloud-init[1030]: Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata [.error]
[   11.012289] cloud-init[1030]: Repository 'openSUSE-Tumbleweed-Oss' is invalid.
[   11.013394] cloud-init[1030]: [repo-oss|http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/] Valid metadata not found at specified URL
[   11.015084] cloud-init[1030]: History:
[   11.015377] cloud-init[1030]:  - [|] Error trying to read from 'http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/'
[   11.016288] cloud-init[1030]:  - Download (curl) error for 'http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/content':
[   11.017101] cloud-init[1030]:    Error code: Connection failed
[   11.017629] cloud-init[1030]:    Error message: Could not resolve host: download.opensuse.org
[   11.018249] cloud-init[1030]: Please check if the URIs defined for this repository are pointing to a valid repository.
[   11.018964] cloud-init[1030]: Skipping repository 'openSUSE-Tumbleweed-Oss' because of the above error.
[   12.222609] cloud-init[1030]: Retrieving repository 'openSUSE-Tumbleweed-Update' metadata [..done]
[   12.231709] cloud-init[1030]: Building repository 'openSUSE-Tumbleweed-Update' cache [....done]
[   12.233464] cloud-init[1030]: Some of the repositories have not been refreshed because of an error.
[   12.235067] cloud-init[1030]: LIMA| WARNING: Failed to execute /mnt/lima-cidata/boot/30-install-packages.sh
[   12.236109] cloud-init[1030]: LIMA| Executing /mnt/lima-cidata/boot/40-install-containerd.sh
[   12.237412] cloud-init[1030]: + '[' '' '!=' 1 ']'
[...]
[   28.489731] cloud-init[1030]: ###  END  ###
[   28.491324] cloud-init[1030]: [INFO] Set `export CONTAINERD_SNAPSHOTTER="stargz"` to use the stargz snapshotter.
[   28.493044] cloud-init[1030]: + '[' -n '' ']'
[   28.493625] cloud-init[1030]: LIMA| Executing /mnt/lima-cidata/provision.system/00000000
[   28.494901] cloud-init[1030]: + apt-get update
[   44.173262] cloud-init[1030]: Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata [................done]
[   46.760536] cloud-init[1030]: Building repository 'openSUSE-Tumbleweed-Oss' cache [....done]
[   47.326412] cloud-init[1030]: Repository 'openSUSE-Tumbleweed-Update' is up to date.
[   47.329462] cloud-init[1030]: All repositories have been refreshed.
[   47.334325] cloud-init[1030]: + apt-get install -y sshfs
[   47.387235] cloud-init[1030]: Loading repository data...
[   47.471899] cloud-init[1030]: Reading installed packages...
[   47.659290] cloud-init[1030]: Resolving package dependencies...
[   47.704372] cloud-init[1030]: The following 3 NEW packages are going to be installed:
[   47.705049] cloud-init[1030]:   fuse3 libfuse3-3 sshfs
[   47.705500] cloud-init[1030]: 3 new packages to install.
[   47.705842] cloud-init[1030]: Overall download size: 191.9 KiB. Already cached: 0 B. After the operation, additional 625.4 KiB will be used.
[   47.706670] cloud-init[1030]: Continue? [y/n/v/...? shows all options] (y): y
[   47.753928] cloud-init[1030]: Retrieving package libfuse3-3-3.11.0-1.3.aarch64 (1/3),  80.8 KiB (258.2 KiB unpacked)
[   48.617389] cloud-init[1030]: Retrieving: libfuse3-3-3.11.0-1.3.aarch64.rpm [done]
[   48.619382] cloud-init[1030]: Retrieving package fuse3-3.11.0-1.3.aarch64 (2/3),  58.6 KiB (214.4 KiB unpacked)
[...]

so technically the script part in the yaml file is useless, as it would be to add a specific bit in 30-install-packages.sh since it technically should already be doing that but is currently failing to do so
I'll try to see if I can understand why this happens

so the available version of apt-get in opensuse is a wrapper around zypper written in perl. As is, it doesn't seem to work with some of the options usually set for it. Even if the script is able to refresh the repository metadata, actually installing the requirement are failing because this option cause the apt wrapper to fail:
lima-tw:/mnt/lima-cidata/boot # ./30-install-packages.sh
+ INSTALL_IPTABLES=0
+ '[' '' = 1 ']'
+ '[' 1 = 1 ']'
+ INSTALL_IPTABLES=1
+ '[' 56526 -ne 0 ']'
+ INSTALL_IPTABLES=1
+ command -v apt-get
+ pkgs=
+ '[' reverse-sshfs = reverse-sshfs ']'
+ '[' 2 -gt 0 ']'
+ command -v sshfs
+ pkgs=' sshfs'
+ '[' 1 = 1 ']'
+ '[' '!' -e /usr/sbin/iptables ']'
+ pkgs=' sshfs iptables'
+ '[' 1 = 1 ']'
+ command -v newuidmap
+ '[' -n ' sshfs iptables' ']'
+ DEBIAN_FRONTEND=noninteractive
+ export DEBIAN_FRONTEND
+ apt-get update
Repository 'openSUSE-Tumbleweed-Oss' is up to date.
Repository 'openSUSE-Tumbleweed-Update' is up to date.
All repositories have been refreshed.
+ apt-get install -y --no-upgrade --no-install-recommends -q sshfs iptables
The flag --no-upgrade is not known.
lima-tw:/mnt/lima-cidata/boot #

Going with the same iterative approach, I'm able to get apt working if I remove --no-upgrade, --no-install-recommends and -q options.
to complete my test I have to re-export LIMA_CIDATA_MNT manually and the script works then:
lima-tw:/mnt/lima-cidata/boot # export LIMA_CIDATA_MNT=/mnt/lima-cidata
lima-tw:/mnt/lima-cidata/boot # /tmp/30-install-packages.sh
+ INSTALL_IPTABLES=0
+ '[' '' = 1 ']'
+ '[' 1 = 1 ']'
+ INSTALL_IPTABLES=1
+ '[' 56526 -ne 0 ']'
+ INSTALL_IPTABLES=1
+ command -v apt-get
+ pkgs=
+ '[' reverse-sshfs = reverse-sshfs ']'
+ '[' 2 -gt 0 ']'
+ command -v sshfs
+ '[' 1 = 1 ']'
[...] [previous tests installed sshfs] [...]
+ /mnt/lima-cidata/boot/09-host-dns-setup.sh
[...] [doing a bunch of iptable things here] [...]
+ '[' reverse-sshfs = reverse-sshfs ']'
+ update_fuse_conf
+ '[' 2 -gt 0 ']'
+ fuse_conf=/etc/fuse.conf
+ '[' -e /etc/fuse3.conf ']'
+ fuse_conf=/etc/fuse3.conf
+ grep -q '^user_allow_other' /etc/fuse3.conf
+ echo user_allow_other
lima-tw:/mnt/lima-cidata/boot #

Reading some other issues seem to indicate that detecting package managers by querying their existence is done purposefully. I feel like the easiest way for a fix would be to remove the above mentioned problematic options but I also guess they're here rightfully for debian-like systems to avoid un-necessary dependencies and to get a clean output.
I think I can keep the same spirit but I'd need to change the detection for apt-get to this: hexdump -C -n 4 "$(command -v apt-get)" | grep -qF 'ELF'
it would fail on opensuse:
julien@lima-tw:/Users/julien> hexdump -C -n 4 "$(command -v apt-get)" | grep -qF 'ELF'
julien@lima-tw:/Users/julien> echo $?
1

and it would success on ubuntu:
julien@lima-default:/Users/julien$ hexdump -C -n 4 "$(command -v apt-get)" | grep -qF 'ELF'
julien@lima-default:/Users/julien$ echo $?
0

debian would also be ok :
julien@lima-debian:/Users/julien$ hexdump -C -n 4 "$(command -v apt-get)" | grep -qF 'ELF'
julien@lima-debian:/Users/julien$ echo $?
0

what do you think ?

The suggestion was to just look for "and not zypper", but then it was complicated by distribution

damn I should have read your issue more throughfully since we basically got into the same issues and steps to identify the root cause :)
I would agree to switch to system detection and infer package management from that. it's usually how it's done. but in thecurrent situation I took for granted that the solution had to be done with package manager detection, hence why I'm trying to dig a little deeper and see if the version of apt or apt-get is indeed legit or not. I think it would practically solve our issues while keeping the current approach as is, and it would leave the room open for discution on switching to a different detection method later

Seems weird of opensuse to provide "apt", but maybe it's a feature (muscle memory, and all that)


Support mango queries

CouchDB 2 has a new way to query the database without using views:

https://blog.couchdb.org/2016/08/03/feature-mango-query/
https://github.com/cloudant/mango

Perhaps this could be implemented as two new database functions:

mango_query
mango_index

Hey, thanks for the notice. I haven't installed CouchDB 2 yet, but will likely do so soon after release. Still, I'm not sure adding APIs for Mango will be a high priority for me, personally, so it would be great if you're able to contribute some code towards this goal.

Just thought I'd chime in that without some mango support, there will be no way to perform a query without creating a view, as they've removed temporary views in favor of this new json-based query system.

I'm new to CouchDB and this project but I'm looking at trying to add these new functions mango_query and mango_index. If I have any success I'll submit a pull request.

A Mango query is just a POST request to /:db/_find containing some JSON in the body, so this shouldn't be hard to make, right?

Honestly, this was really dead simple to monkeypatch:
        _, _, data = db.resource.post_json('_find', body={"selector" : query}, headers = {'Content-Type': 'application/json'})                                                return data["docs"]
Almost nearly a one-liner. Anybody wanna make a PR?

Maybe like in django:
For example:
data1 = db.find(field__eq='A', limit=50)
data2 = db.find(Q(field__eq='A')
                & (Q(field1__subfield1__in=['lama', 'amal'])
                    | Q(field2__subfield2__regex ="foo")), limit=40, fields=['field1', 'field2'])

I have implementation of this. If it is acceptable, I can provide my implementation.
Q obj - https://github.com/pirr/alt_couch/blob/c690771f729c38ac39041d4fea981b44623a0748/_libs/vb/couch.py#L14
find method - https://github.com/pirr/alt_couch/blob/c690771f729c38ac39041d4fea981b44623a0748/_libs/vb/couch.py#L222
Sorry for my terrible english.

I would like to add an implementation to CouchDB-Python. If you can provide one that fits into the library and has comments in English, I could probably review it.

I added filter method (mango query) with comments:
https://github.com/pirr/couchdb-python/commit/6f051bcd4879955610d6d2c182b53f09266022e7

Looks pretty good, do you want to do a pull request for this?

Ok. I will do.


Make it known that SEEKRET_RULES_PATH can be used

Unless you know the code base of the seekret library, you would never know in this repository that the library can use SEEKRET_RULES_PATH

Addressed by #16


Support init SQL for each session

Why are the changes needed?

How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #857 (acfa89a) into master (bf0042c) will increase coverage by 0.04%.
The diff coverage is 100.00%.

:exclamation: Current head acfa89a differs from pull request most recent head bc39268. Consider uploading reports for the commit bc39268 to get more accurate results

@@             Coverage Diff              @@
##             master     #857      +/-   ##
============================================
+ Coverage     78.60%   78.65%   +0.04%
  Complexity       10       10
============================================
  Files           135      135
  Lines          5123     5135      +12
  Branches        642      643       +1
============================================
+ Hits           4027     4039      +12
  Misses          745      745
  Partials        351      351

Impacted Files
Coverage Δ

...rg/apache/kyuubi/engine/spark/SparkSQLEngine.scala
69.64% <100.00%> (+1.12%)
:arrow_up:

.../engine/spark/session/SparkSQLSessionManager.scala
94.44% <100.00%> (+0.89%)
:arrow_up:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
94.15% <100.00%> (+0.08%)
: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 bf0042c...bc39268. Read the comment docs.

@turboFei @yaooqinn would you please take a look? thx

use .show seems not gentle, how about .count ?

use .show seems not gentle, how about .count ?

make sense

use .show seems not gentle, how about .count ?

make sense

count introduced new job, which broken UTs depends on JobId, reverted.

thanks, merged to master


feat(tagging): added tagging for removed tracers - revert

Reverts epsagon/epsagon-node-frameworks#117

:tada: This PR is included in version 1.27.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: Add ProviderName type

Description

Type ProviderName created to help identify structures instead of using map[string] it changed to map[ProviderName]

helps to close: #1167

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

[ ]  Let's move it back to config or we can create a new package, provider to store both the type and list of providers.

Putting the structure ProviderName inside the config package would generate an import cycle we could create a new package provider in price-feeder/provider, but this way we would have 2 provider packages at 2 different locations, which doesn't sound good to me

[ ]  Provider type should be stored next to the list of providers, not in the types package. In the future we will refactor the types package.

The Provider types is already inside price-feeder/oracle/provider

Any suggestions @robert-zaremba ?

The Provider types is already inside price-feeder/oracle/provider

@RafilxTenfen then let's keep both the Provider type and the list in the existing provider package.

@RafilxTenfen then let's keep both the Provider type and the list in the existing provider package.

import cycle again...
the good thing about being in the types package is that the types itself doesn't import any other package
@robert-zaremba

Something must be wrong. Why  moveing the list to the provider package creates the import cycle? Can you write down the cycle here?

Something must be wrong. Why moveing the list to the provider package creates the import cycle? Can you write down the cycle here?

The list of providers and the new type are inside price-feeder/oracle/provider

--> Installing...
CGO_ENABLED=0 go install -mod=readonly -ldflags '-X github.com/umee-network/umee/price-feeder/cmd.Version=-3cc05765e399057b3b6ff8b27a9f2d8fdeff468f -X github.com/umee-network/umee/price-feeder/cmd.Commit=3cc05765e399057b3b6ff8b27a9f2d8fdeff468f' ./...
package github.com/umee-network/umee/price-feeder
imports github.com/umee-network/umee/price-feeder/cmd
imports github.com/umee-network/umee/price-feeder/config
imports github.com/umee-network/umee/price-feeder/oracle/provider
imports github.com/umee-network/umee/price-feeder/config: import cycle not allowed
package github.com/umee-network/umee/price-feeder
imports github.com/umee-network/umee/price-feeder/cmd
imports github.com/umee-network/umee/price-feeder/config
imports github.com/umee-network/umee/price-feeder/oracle/provider
imports github.com/umee-network/umee/price-feeder/config: import cycle not allowed

@robert-zaremba can you check this again?

@RafilxTenfen it seems that the import cycle was caused by the importing the config.ProviderEndpoint in provider package. If we move that type to the provider package then we solve the import cycle, and we will store all provider types in the provider package. Note: when moving ProviderEndpoint to provider package, we should remove Provider prefix (to avoid name clash: provider.ProviderEndpoint).

The struct CurrencyPair is also imported, do you think that should be sent to the price-feeder/oracle package as well?

This reorganization of price-feeder structs could be done in another PR after we discuss and plan an issue specific to that
Since @adamewozniak already approve this and if you agree @robert-zaremba  I will merge it

The struct CurrencyPair is also imported, do you think that should be sent to the price-feeder/oracle package as well?

Yes. CurrencyPair is in the domain of a provider. So let's put it there.


Feature proposal: add a hook that allows a component to support both controlled and uncontrolled modes

This hooks is implemented in many React UI component libraries, and I find this logic very useful
(usually it is named useMergeValue or useControlValue)
https://github.com/mui/material-ui/blob/master/packages/mui-utils/src/useControlled.js
https://github.com/chakra-ui/chakra-ui/blob/main/packages/hooks/use-controllable-state/src/index.ts
https://github.com/react-component/util/blob/master/src/hooks/useMergedState.ts
https://github.com/ant-design/ant-design-mobile/blob/master/src/utils/use-props-value.ts
This hooks allows the state of the component to be both self-managed and externally controlled

hi, here useControlled

hi, here useControlled

Thanks!


The deadline for ICDE 2024 is wrong?

The official site says the deadline is Friday for anywhere on earth. So it should be November 24th CST instead of November 25th CST?

We set the deadline of ICDE to 2023-11-24 23:59:59 (Anywhere on Earth), which is aligned with one presented on the official site. This timeline will be automatically transformed based on local time zone.

Please refer to an AoE->CST Converter for resolving your confusion.

Thanks a lot!


Make read-only properties read-only

A read-only property shouldn't be allowed to be edited ;-)
Fixed by not creating an editor in that case.
Related #654 which attempted to solve that issue by disabling the property,
which in turn was reverted in #679 due to its side effects.

Any idea how this relates to https://github.com/ros-visualization/rviz/pull/687?

lgtm
I was able to reproduce by using the move_base_amcl_10cm.launch example in the navigation_stage package. Before the patch I could edit the position fields for the costmaps which are of display type "map". After the patch I could not.


Add parallel option for executing tasks

Fixes #18

Fixed and rebased

changed and rebased

Super nice! Thanks a lot @southpolesteve for this PR :).


Add function to plot empirical cdf

This PR adds a function, plot_ecdf, to plot empirical CDFs of model performance given a data frame of model results. The plot includes 1 CDF curve for each model represented in the model results. I opted to format the model results as a data frame instead of a list, which we discussed in #189.  I think it makes the function more generalizable to move data formatting code outside of the plotting function. The model results list is formatted as a data frame in p3_model_results.
Much of the plot formatting is already parameterized, but we could other formatting options like color more flexible. Here's what p3_ecdf_all_reaches_png looks like for me:

Looks good! Is the code ready for review? / Do you think it needs a review?

Looks good! Is the code ready for review? / Do you think it needs a review?

Thanks, this is ready for review! I don't think this needs an extensive review so long as it meets the proposed use cases. I'd appreciate it if you could check that the RMSE values I'm using to plot the ecdf match what you were expecting (e.g. summarization steps in lines 45-50; 67-72; and 90-98 of the plot_ecdf.R script).


Acario/lsp ui sideline

Commit on top of #364
Add lsp-ui related faces :

sidelines as "more bg" comments
lsp-ui-peek "trigger" (the searched symbol) as yellow in the menu

Thanks again!


CDN fix for Content-Security-Policy

Description
Add a slash / to CDN_HOST when handling Content-Security-Policy.
This is required when CDN_HOST rather than just the host
ex:
d29ujl8n7pu7k5.cloudfront.net

contains a longer prefix
d29ujl8n7pu7k5.cloudfront.net/cidev
                             ^^^^^^

Jira Ticket
Please add link to Jira ticket
Coding Standards
Code Style Guide: https://github.com/companieshouse/dissolution-web/wiki/Code-Style-Guide
Checklist

[ ] 3 Amigos
[ ] Acceptance Criteria met
[ ] Branch named {feature|hotfix|task}/{S4-*}
[ ] Commit messages are meaningful
[X] Manually tested
[X] All unit tests passing
[ ] WAVE accessibility testing tool ran on new or updated pages
[ ] All UI Tests Passing
[ ] Pulled latest master into feature branch
[ ] Sonar Analysis
[ ] Master branch on Rebel1 and CIDev CI/CD pipeline is green
[ ] Any Docker environment variables added are consistent with those on our upstream environments (Rebel1, CIDev etc)
[ ] If your pull request depends on any other, please link them in the description

Screenshots of new or updated views

As discussed with Stefano, please hold off on merging this until after fees release as we don't want to add complexity or risk to that deployment.

This PR is currently parked until ongoing decisions are settled down:
"[...] long term we'll probably want to have every service institute its own CSP, and so we'll need a global config variable they can all use, so maybe the name should be more contextual at that point. Something like CSP_CDN_HOST or some variation of that

This is not going to go in as the specs have changed:

There are a few issues with paths in CSS files in cdn.ch.gov.uk and so we’re going to change the way the reworked CDN works (one CloudFront distribution per environment), so at some point we’ll be updating configs again and the CDN_HOST value will be a naked domain (without any / suffix) Which should resolve both the path issue and the issue we saw the the content security policy


Pre-connect to the selected kernel before running the first command

According to my experience, after selecting a kernel, Jupyter is not connected to the kernel until the first execution is perform. And in this case, we have to wait a plenty of time to get connected. We would like Jupyter to connect in advance to the a kernel after the kernel is selected.

It seems to auto-start for me, can you check if you have "jupyter.disableJupyterAutoStart": false (default)

We would like Jupyter to connect in advance to the a kernel after the kernel is selected.

We alrteady do this today for local kernels, please can you confirm you do not have this setting "jupyter.disableJupyterAutoStart": false
Or are you connecting to a remote Kernel, with remote Jupyter kernels, we do not auto start (pre-warm) the kernels, as its possible users might not want to run some code.

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.


URI encode path params

Update test snapshot to reflect uri encoded path params
Update method template to uri encode path params supplied by consumers
Run npm audit fix to fix some security vulnerabilities

This commit fixes issue: https://github.com/mtennoe/swagger-typescript-codegen/issues/92

I'm unsure as to whether this should be a patch or a minor version bump, as now that path parameters will be uri encoded, any consumers who are manually encoding their path parameters will be broken by this change.

I made a mistake with the commit when bumping the version. Will make a new PR to keep it clean


Trouble with MPEG-DASH live stream rewind

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.0.3
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
macOS 10.15.6, Version 84.0.4147.105 (Official Build) (64-bit)
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?

https://edge1.1internet.tv/dash-live13/streams/1tv/1tvdash-test.mpd - this live stream with DVR -12 hours.
What did you do?

Open the demo player app - https://shaka-player-demo.appspot.com/demo
Insert the MPEG-DASH live stream link and press Play -> live stream playing
Rewind the stream to one hour later -> stream playing from hour later
Rewind the stream to two and more hours later -> stream not playing

What did you expect to happen?
Rewind works correctly up to -12 hours.
What actually happened?

Stream not playing if rewind more than 1h 20min.
In console:
Ignoring large gap at 66901.115971 size 13378.926694999987
14:25:06.795 dash_parser.js:1032 Updating manifest...
14:25:17.809 dash_parser.js:1032 Updating manifest...
14:25:28.723 dash_parser.js:1032 Updating manifest...
14:25:38.753 dash_parser.js:1032 Updating manifest...
14:25:48.760 dash_parser.js:1032 Updating manifest...
14:25:58.771 dash_parser.js:1032 Updating manifest...
...
This issue appears only in Shaka 3.x branch. For example, on 2.15.4 rewind works correctly.

We limit the number of SegmentTemplate references we have to avoid having thousands of references.  Having of large number of segments can make lag more when doing updates.  But you can change this with the manifest.dash.initialSegmentLimit configuration.

@TheModMaker thanks.
'initialSegmentLimit' option helped me with the problem.


[Don't Merge] Less 3.7

@seanCodes, this PR is 99% of the conversion to Less 3.7.
It's marked "Don't Merge" because there's a discrepancy in how certain each() loops execute vs SCSS's @each, at the moment (see changes to bootstrap.css in b2837dfab23621bf09193d95c89fb55958711fde).  I'll investigate that when I get a chance to put together a reduced test case and file a bug w/ Less.
I'm opening this PR to claim #7 and because the 3.5+ syntax is exciting!   Looks like I did this for no reason today: https://github.com/seanCodes/bootstrap-less-port/pull/12

@matthew-dean no worries.  I've updated this one with your README and package.json updates, and the unquoting of the ~"calc(...)" variable values, so now the only difference is the maps, I think.  (And Autoprefixer worked for me.)  :p  I also reviewed #12 so @seanCodes can see what's going on and choose how far from Sass/how into Less he wants this project to go.

Replaced by #13

👍 Should I close the other PR?

@matthew-dean Unless you're opposed to #13 for some reason, I think we can simplify by closing #12.  Sorry for the confusion!


Pipelines working with granite

New templates
Updated images
Updated langchain
Added missing image bucket env var

Closes #113 #114


Hangfire 1.7.0

With the release of Hangfire 1.7.0 I am wondering if there is any impact (as there is also some breaking changes and data changes) for Hangfire.Mongo.
And if there is what the expected timetable is for a new version (note I just ask so I know if I should plan the upgrade on my end already or postpone until a later date).
Cheer,
Hans

@EngelenH,
Im planning to release 0.6.0 late next week.
That will be targeting Hangfire 1.7.0. There are some breaking changes in the hangfire api, but it shouldnt be necessary to do a migration to support that.
0.6.0 will also introduce a tailable collection for signaling jobs enqueued and locks released.
Br

Referencing Hangfire.Core 1.7.1 and latest mongo driver in 0.6.0, please let me know if you have any issues.


Some tools send DocumentMessage::Undo instead of DocumentMessage::AbortTransaction when Aborting

Example of a tool with this behavior is "SelectTool".
DocumentMessage::Undo stores the history step, which can lead to the deletion of a previously stored redo step see #1659 and related Pull request for more information.

Was this resolved by #1664? If so, we can close this, but I'm not sure if that PR did indeed resolve it or if this issue's part was left unfinished.

Presuming closed by #1664.


Docs.MS CI Updates for Azure.Communication.Sms

CI Update for release of Azure.Communication.Sms

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

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

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


error

$ python node.py
2024-09-25 22:48:48.242 | ERROR    | main:call_api:79 - Error during API call: HTTPSConnectionPool(host='api.nodepay.ai', port=443): Max retries exceeded with url: /api/auth/session (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7028c44f10>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=10)'))
2024-09-25 22:48:48.243 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy <IP_ADDRESS>:8080: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:48.244 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:49.075 | ERROR    | main:call_api:79 - Error during API call: HTTPSConnectionPool(host='api.nodepay.ai', port=443): Max retries exceeded with url: /api/auth/session (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))
2024-09-25 22:48:49.076 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy <IP_ADDRESS>:8080: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:49.077 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:53.088 | ERROR    | main:call_api:79 - Error during API call: HTTPSConnectionPool(host='api.nodepay.ai', port=443): Max retries exceeded with url: /api/auth/session (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))
2024-09-25 22:48:53.092 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy <IP_ADDRESS>:8080: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:53.093 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-25 22:48:56.213 | ERROR    | main:call_api:79 - Error during API call: HTTPSConnectionPool(host='api.nodepay.ai', port=443): Max retries exceeded with url: /api/auth/session (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))
2024-09-25 22:48:56.214 | ERROR    | main:render_p

i have some issue
2024-09-30 00:12:45.835 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://GVN3GG4632:n4J4QVix@<IP_ADDRESS>:4222
2024-09-30 00:12:45.835 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://GVN3GG4632:n4J4QVix@<IP_ADDRESS>:4222    : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.835 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.836 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://root:pDSS3j6r@<IP_ADDRESS>:39450
2024-09-30 00:12:45.837 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://root:pDSS3j6r@<IP_ADDRESS>:39450                                : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.837 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.838 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://kick4m7y:kIcK4m7y@<IP_ADDRESS>:12345
2024-09-30 00:12:45.838 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://kick4m7y:kIcK4m7y@<IP_ADDRESS>:12345                              : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.839 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.840 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://PVN24408:fCAK2u8y@<IP_ADDRESS>:20211
2024-09-30 00:12:45.840 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://PVN24408:fCAK2u8y@<IP_ADDRESS>:20211                             : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.840 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.841 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://GVN3GG4632:n4J4QVix@<IP_ADDRESS>:4222
2024-09-30 00:12:45.841 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://GVN3GG4632:n4J4QVix@<IP_ADDRESS>:4222                            : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.842 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.843 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://uqzy1t9g:uQzY1t9G@<IP_ADDRESS>:6789
2024-09-30 00:12:45.843 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://uqzy1t9g:uQzY1t9G@<IP_ADDRESS>:6789                             : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.844 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.845 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://mjys0qwp:cmjgPbhIGxzs@<IP_ADDRESS>:3175
2024-09-30 00:12:45.846 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://mjys0qwp:cmjgPbhIGxzs@<IP_ADDRESS>:3175                           : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.846 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.847 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://root:kYiK2b4L@<IP_ADDRESS>:32196
2024-09-30 00:12:45.848 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://root:kYiK2b4L@<IP_ADDRESS>:32196                         : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.848 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.849 | ERROR    | main:call_api:79 - Error during API call: Failed to parse: http://VNM00031:mVSM7p9X@<IP_ADDRESS>:20211
2024-09-30 00:12:45.850 | ERROR    | main:render_profile_info:56 - Error in render_profile_info for proxy http://VNM00031:mVSM7p9X@<IP_ADDRESS>:20211                             : Failed API call to https://api.nodepay.ai/api/auth/session
2024-09-30 00:12:45.850 | ERROR    | main:render_profile_info:66 - Connection error: Failed API call to https://api.nodepay.ai/api/auth/session

is this error fixed?

Nodepay change their endpoint and payloads..

ohhh

Nodepay change their endpoint and payloads..

you know any wokring dawn or nodepay or gradient network bot?

I have dawn code and working on gradient network(bit harder)

Share maybe @viki-ramesh
So we can also farm haha

yeah bro, share if you can 🔢

@viki-ramesh can you share me the code for Dawn and Gradient as well, much appreciate.

2024-10-14 21:45:54.970 | ERROR    | main:ping:113 - Ping failed via proxy http://admin:admin@<IP_ADDRESS>:56856: Failed API call to https://nw2.nodepay.ai/api/network/ping
2024-10-14 21:45:56.204 | ERROR    | main:call_api:79 - Error during API call: HTTPSConnectionPool(host='nw2.nodepay.ai', port=443): Max retries exceeded with url: /api/network/ping (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)')))

admin:admin@<IP_ADDRESS>:56856

bro delete this
you are exposing your proxy to everyone
other people can steal your bandwidth

I have dawn code and working on gradient network(bit harder)

can you share me code about gradient network pls

Has the error been fixed yet?

no

Hey, I want to learn making bot like you. I am interested those things. Can you suggest me where can i learn those thing. Or you will guide me. Please....


tc.visualization.scatter(x,y) hangs when x and y are SArrays of 3 million integers each

Repro on Debug build on macOS High Sierra:
x = tc.SArray(range(1,3000000))
y = tc.SArray(range(5,3000004))
scplt = tc.visualization.scatter(x,y)
scplt.show()

This hangs.
FYI, for a heatmap the plot appears in less than a second.

@shantanuchhabra Please provide:

Repro steps?
Expected vs. actual behavior?
How long does it take? How long should it take?
Debug or release build?
What platform/hardware?

I'm experiencing the same hang in scatter plot on a jupyter notebook.
I'm trying to scatter plot a roc_curve of a classifier with 13K data points on x and y
it took several minutes for the plot to display. Any suggestions?

@VlamV For now this is a known issue but not a high priority for us. If you need scatter plots in particular with this much data, you could try using another visualization library with scatter plot capability and see if it can handle this much data. Or, you could try a different plot: tc.visualization.heatmap should handle much more data comfortably, and will show density over ranges instead of individual points.

@shantanuchhabra , were you able to find a workaround of same ?. I have same issue with 20K data  points

This is still an issue in 6.4


Doc updates for AR getting started experience

I've received some feedback that its too hard to get the toolkit set up when building AR apps. I'm hopeful that the changes in this PR will help users successfully build AR apps.

I re-requested review since I was approved to migrate the wiki content here as well.