Welcome message

fixed welcome message according to readme

Oh I didn't checkout to origin/master I'll create new request :)


improvements

Hi,
Could you please make the output like: pride seven deny frown twenty .....etc
not like

pride
seven
....etc
Also, is possible to mass generate a number of mnemonics on a text file. 12 words on each line?
Thanks!

Hey @su314ka thanks for the suggestions! I'll consider adding those improvements to the generator.
One caveat, the output would make it easier to copy/paste a seed into a desktop wallet but I wouldn't recommend that. You'd be saving very sensitive information in the clipboard history which could present a security risk.
One potential improvement I've been thinking about is the ability to save the seed to an encrypted file, and it would be possible to create multiple seeds with that same method as well pretty easily.
I'm not sure of an ETA on new features for mnemonicgen so I'm going to close the issue for now, but I wanted you to know I've taken those suggestions in to consideration.
-Josh


footerTemplate not working

This is regarding the ui-grid footerTemplate. I tried entering html content (a div with some text) in a string, I've also tried adding a .html file name in the string and even the ID of a rendered div, but none of them seem to work.
It also wasn't clear for me if I need to enable showGridFooter for this or not, so I tried both, but the footerTemplate is either not shown at all, or if I set showGridFooter to true, it  shows the default footer (total lines in the grid).
Am I doing something wrong?
Thanks :)

You can change template for footerTemplate. I have:
 $scope.gridOptions.footerTemplate = myGridOptions.footerCreate('profile.campaign.create', 'Create Campaign');

I have service that return footer collumn template:
        this.footerCreate = function (createLink, linkLabel) {
            return '
' +
                '' +
                '<button type="button" class="btn btn-success btn-tarzan">' + linkLabel + '</button>' +
                '' +
                '
';
        };

In grid options I have
showColumnFooter: true

@PaulL1 Hi Paul, It has stopped working for sure. I see many bugs created on footer cell template.
I have a custom template as:
var footerCellDescTempelate = '
Total
' +
        '
 Post Dated Total
' +
        '
 Eft Total
' +
        '
 Manual Total
' +
        '
 Void Total
' +
        '
 Outstanding Total
';

Above code was working earlier and now it doesn't. It shows only one cell and is not expanding.

Expected result:

I'm not sure that "I see many bugs created on footer cell template" means that it's stopped working.  Could you perhaps provide a plunker, and explain when it was that it worked, and what it was that changed that made it stop working?

Ok, so if I understand this right, the footerTemplate is actually a custom column footer, rather than a grid footer, right? If someone could confirm that, this could be closed.

yes it is custom column footer which gets hidden due to some css changes happened recently. Hight remains fixed and doesn't expand any-more. @PaulL1: Fix is very small in css if you can add it.
.ui-grid-footer-panel {
height: auto !important;
}

I'm not sure if we expected the footer to auto-size, and I'm not a big fan of using !important to force things.  But I see the use case, so I'll leave this open.

@PaulL1 : Yeaterday i was trying footerTemplate and is not working at all instead gridFooterTemplate works!

@PaulL1  gridFooterTemplate property  is completely misses out from documentation/GridOptions  API.


docs(examples): update examples and docs to use node 18

There are no code changes here, so it should be a pretty easy ✅

This was previously approved in https://github.com/vercel/turbo/pull/5030 (before I reduced that PR to just updating docs to actually build with node 18), so I'm going to merge this when CI passes!


[BUG] Segfault when extending CAGRA index with less than 128 nodes

Describe the bug
When trying to extend a CAGRA index that has less than 128 nodes, a segfault occurs.
Steps/Code to reproduce bug
Run the test BuildExtendSearch in cpp/test/neighbors/ann_cagra_c.cu and set main_data_size to 127
or (using CAGRA with C++ directly):
Change n_rows to 127 in one of the test inputs in ann_cagra.cuh
Expected behavior
The index gets extended successfully
Environment details (please complete the following information):
Bare-metal, compiled from source. I've seen this bug on CUDA toolkit 12.6, 12.5 and 12.4.

Thank you @ajit283 for reporting the bug. I could reproduce the problem (by using dim 127 at this line).
I believe that CAGRA-Q requires that dim is a multiple of pq_dim, therefore the modified input config is incorrect. This is still a bug, since the code should not crash, instead it should exit after printing an informative error message. We will fix this.
For reference, here is the test output:
[ RUN      ] AnnCagraTest/AnnCagraTestF_U32.AnnCagra/1
using ivf_pq::index_params nrows 10000, dim 127, n_lits 100, pq_dim 32
[I] [13:41:49.824636] optimizing graph
[I] [13:41:49.851619] Graph optimized, creating index
unknown file: Failure
C++ exception with description "std::bad_alloc: CUDA error at: /workspace1/cuvs/cpp/build_90/_deps/rmm-src/include/rmm/mr/device/cuda_memory_resource.hpp:62: cudaErrorIllegalAddress an illegal memory access was encountered" thrown in the test body.
unknown file: Failure
C++ exception with description "CUDA error encountered at: file=/workspace1/cuvs/cpp/build_90/_deps/raft-src/cpp/include/raft/core/interruptible.hpp line=303: call='query_result', Reason=cudaErrorIllegalAddress:an illegal memory access was encountered
Obtained 12 stack frames
#1 in gtests/NEIGHBORS_ANN_CAGRA_TEST: raft::cuda_error::cuda_error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) +0x6a [0x560a8bcd630a]
#2 in gtests/NEIGHBORS_ANN_CAGRA_TEST: void raft::interruptible::synchronize_impl<cudaError (*)(CUstream_st*), rmm::cuda_stream_view>(cudaError (*)(CUstream_st*), rmm::cuda_stream_view) +0x213 [0x560a8bcd7373]
#3 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0xb5401) [0x560a8bd26401]
#4 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x1d3551) [0x560a8be44551]
#5 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x1bfd95) [0x560a8be30d95]
#6 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x1c0375) [0x560a8be31375]
#7 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x1c7d0f) [0x560a8be38d0f]
#8 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x1bfe5a) [0x560a8be30e5a]
#9 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x5d594) [0x560a8bcce594]
#10 in /usr/lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x153a325d4d90]
#11 in /usr/lib/x86_64-linux-gnu/libc.so.6: __libc_start_main +0x80 [0x153a325d4e40]
#12 in gtests/NEIGHBORS_ANN_CAGRA_TEST(+0x5d5f5) [0x560a8bcce5f5]
" thrown in TearDown().
[  FAILED  ] AnnCagraTest/AnnCagraTestF_U32.AnnCagra/1, where GetParam() = {n_queries=100, dataset shape=10000x127, k=16, auto, max_queries=10, itopk_size=64, search_width=1, metric=L2, device, build_algo=IVF_PQ, pq_bits=8, pq_dim=63, vq_n_centers=100}

@tfeher interesting, I actually meant to change n_rows in ann_cagra.cuh. Maybe the behavior described by you is a separate bug?


Feature request : Support for Druid histograms

I'd like to see support for Druid histograms. I'm specifically interested in charts of a given percentile.
See: http://druid.io/docs/latest/development/approximate-histograms.html
Thanks for considering!

@xrmx any update for this feature? the approximate histogram feature is very important for us.

@yinzhiqiang If it's important for you feel free to work on this. As a general rule don't expect someone else is doing the work for you for free.

@mmcgowan can you provide more info of what you are after?
At time of ingestion you create an approxHistogramFold, you can then create metrics based on that histogram in superset.
in ingestion schema:
{ "type" : "approxHistogramFold", "name" : "hist_response_time", "fieldName" : "response_time", "resolution" : 50},
metric json spec:
{ "type" : "quantile", "name" : "hist_response_time", "fieldName" : "hist_response_time",
"probability" : 0.95 }


Formating number, numeric, currency columns values

How can I format my currency columns to currency format  ?
My original value is
163.563,08
In my exported the value is :
163,56308
here is how I'm exporting my data :
const ws: XLSX.WorkSheet = XLSX.utils.table_to_sheet(this.tabela.nativeElement);
const wb: XLSX.WorkBook = XLSX.utils.book_new();

XLSX.utils.book_append_sheet(wb, ws, this.titulo);
XLSX.writeFile(wb, `${this.titulo} - ${'GODAIME'} - ${format(new Date(), 'DD-MM-YYYY hh:mm:ss')}.xlsx`);

My table is this :

did you figure it out?

The issue is ultimately JS assuming en-US formatting:
parseFloat("163.563,08") // 163.563, a number between 100 and 1000

Until we implement locale-aware value parsing, there are a few workarounds:

in the table, use the data-v / data-t / data-z attributes to specify the raw numeric value and number format.  They bypass the attempts to parse the strings, but you have to specify the values in US style.

emit values in the en-US style ("." is the decimal point and "," is the thousands separator)


Combination with Human pose detection

@liruilong940607 Thank you for sharing such a great work.
But I wonder why didnt you combine this network with human pose detection in order to make an end-to-end instance segmentation network ?

in the ablation study i saw the gap between the result of using GT  kpts and predicted kpts

in the ablation study i saw the gap between the result of using GT  kpts and predicted kpts


Can't see clearly with the dark theme

Yes, this is indeed a problem should be solved. But I'm quite busy recently, I will try my best to find some time to dig into this issue. Thanks for your report : )


Fix Indices List Command

$ php artisan es:indices:list

  [ErrorException]
  trim() expects parameter 1 to be string, array given

This commit fix it

Hello @chocopowwwa,
Please tell me the version of elasticsearch/elasticsearch package As I am working with version v5.0.0 and cat()->indices() returns a string response not an array.

Hi, sorry i wasn't test well enough,
The problem occours when i'm using elasticsearch/elasticsearch:5.1.3
5.0.0 => Pass The Original Code
5.1.0 => Pass The Original Code
5.1.1 => The Problem Is Here

Thanks @chocopowwwa I will update my code to match the two cases.


Pods do not inherit k3OS' DNS server

Version (k3OS / kernel)

k3os version v0.20.4-k3s1r0

5.4.0-70-generic #78 SMP Fri Mar 26 17:09:23 UTC 2021
Architecture

x86_64
Describe the bug

On a fresh install of k3OS (cloud config only contains SSH public keys), pods seem to not be using the DNS server of k3OS.
To Reproduce

Install latest k3OS and try to resolve a local LAN hostname (most home routers provide this functionality out of the box).
Running kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup router.lan I expect nslookup to be able to resolve my custom hostname, since k3OS is using a DHCP-provided DNS server and is able to resolve it. This is what I'm getting instead:
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS> kube-dns.kube-system.svc.cluster.local

nslookup: can't resolve 'router.lan'

Note that k3OS is able to resolve the hostname:
k3os-24066 [~]$ nslookup router.lan
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>:53

Name:   router.lan
Address: <IP_ADDRESS>

Non-authoritative answer:

Expected behavior

DNS resolving from inside the pod should work and return the correct IP, just as k3OS does.
Actual behavior

Resolving fails.
Additional context

Not relevant but k3OS is running as a VM.
This might help too:
kubectl run -i --restart=Never --rm test-${RANDOM} --image=ubuntu -- sh -c 'cat /etc/resolv.conf'
search default.svc.cluster.local svc.cluster.local cluster.local
nameserver <IP_ADDRESS>
options ndots:5
pod "test-10461" deleted

kubectl run -i --restart=Never --rm test-${RANDOM} --image=ubuntu --overrides='{"kind":"Pod", "apiVersion":"v1", "spec": {"dnsPolicy":"Default"}}' -- sh -c 'cat /etc/resolv.conf'
nameserver <IP_ADDRESS>
pod "test-5910" deleted

I'm not involved with the k3os project but I did run into this issue when running on Oracle's Cloud.
On Oracle's Cloud, the IP address of the DNS server provided via DHCP is in the 169.254/16 range. This was causing k3s to presume it'd be better off using <IP_ADDRESS> instead. That's not an unreasonable assumption, but it did present an unexpected hurdle.
Ended up working around this by using the --resolv-conf arg to k3s and just passing in the default path (/etc/resolv.conf). That was enough for k3s to just use what's there instead of presuming it knows better.
I think I tracked the relevant line of code to the k3s project here:
https://github.com/k3s-io/k3s/blob/2705431d9645d128441c578309574cd262285ae6/pkg/agent/config/config.go#L277
And I'm not an expert in golang, but the documentation of that function seems to be here:
https://golang.org/pkg/net/#IP.IsGlobalUnicast
Hope it helps either you or someone who finds this later on.

Interestingly enough, I gave this a try again on v0.20.7-k3s1r0 and it seems to be working as expected. I can't say for sure that the newer version fixed the issue since I also changed hypervisors in the meantime.
The following works now:
kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 -- nslookup server.lan
Server:    <IP_ADDRESS>
Address 1: <IP_ADDRESS> kube-dns.kube-system.svc.cluster.local

Name:      server.lan
Address 1: <IP_ADDRESS> server.lan
pod "busybox" deleted


What about variables with same name across different variable groups and variables created using the web editor referenced in the same pipeline?

if i created a variable "foo" in the pipeline variables with value "bar",
created a variable group with variable "foo" value "bar2" and referenced the variable group in the pipeline,
which one would have a precedence?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
Content: Variables - Azure Pipelines
Content Source: docs/pipelines/process/variables.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

@swappy208 Thank you for the question.
The order of precedence for variables goes,

Variables used in the yaml file.
Variables declared in the pipeline's variables.
Variables declared in the shared variable groups.

So to answer your question, the pipeline variable foo would take precedence over the variable group foo.

What happens when two variable groups having same variable are imported in a stage.
For Eg: Group1 has variable "variable1" and Group2 also has "variable1" and I am referring both the groups in one stage. How to access Group1.Variable1 ?
Thanks

What happens when two variable groups having same variable are imported in a stage.
For Eg: Group1 has variable "variable1" and Group2 also has "variable1" and I am referring both the groups in one stage. How to access Group1.Variable1 ?
Thanks


[SPARK-47672][SQL] Avoid double eval from filter pushDown

What changes were proposed in this pull request?
Changes the filter pushDown optimizer to not push down past projections of the same element if we reasonable expect that computing that element is likely to be expensive.
This introduces an "expectedCost" mechanism which we may or may not want. Previous filter ordering work used filter pushdowns as an approximation of expression cost but here we need more granularity. As an alternative we could introduce a flag for expensive rather than numeric operations.
Future Work / What else remains to do?
Right now if a cond is expensive and it references something in the projection we don't push-down. We could probably do better and gate this on if the thing we are reference is expensive rather than the condition it's self. We could do this as a follow up item or as part of this PR.
Why are the changes needed?
Currently Spark may double compute expensive operations (like json parsing, UDF eval, etc.) as a result of filter pushdown past projections.
Does this PR introduce any user-facing change?
SQL optimizer change may impact some user queries, results should be the same and hopefully a little faster.
How was this patch tested?
New tests were added to the FilterPushDownSuite, and the initial problem of double evaluation was confirmed with a github gist
Was this patch authored or co-authored using generative AI tooling?
No

oh this is a hard one. The cost of predicates is hard to estimate, and also the benefit as we need to estimate the selectivity and the input data volume.
cc @kelvinjian-db @jchen5

It is. In general I think since we still apply the filter post projection if a user has created a projection with a named field and then filtered on that field the user is probably doing that intentionally since they don't want to double eval the filter. That plus some basic cost heuristics (simple math is cheap udfs can be expensive and so can regexes) should be a net win.

Another possible solution would be to also break up the projection and move the part of the projection which is used in the filter down with the filter unless the only thing the projection is adding is the filter field in which case we'd leave it as is.
This logic starts to get more complex, but I think in that case it's probably more of a "pure" win (e.g. no downsides). WDYT @cloud-fan ?

Do folks have a preference between this approach & the one in https://github.com/apache/spark/pull/46143 ?

CC @cloud-fan do you have thoughts / cycles?

I've been thinking hard about it. Filter pushdown should always be beneficial if we don't duplicate expressions, and the new With expression can avoid expression duplication.
So my proposal is: when we push down filter, and we are about to duplicate some expressions, let's use With to avoid it. At the end of the optimizer, we run the rule RewriteWithExpression to rewrite With and pull out common expressions into a Project below. Data source pushdown rule doesn't require the scan node to be the direct child of Filter, so everything should work as before.

Let me take a look at the with functionality but that sounds potentially reasonable.


Introduce Mask class, apply operators, and a threshold method on GrayscaleImage

This introduces the Mask class, the workhorse object for feature identification. Essentially just a bit mask over images, it provides a map of which pixels contain a particular feature. It's also useful for altering images using the apply method (i.e. black out pixels that don't match the mask, or altering pixels that do match). This PR also contains the threshold and mask_from methods on the GrayscaleImage for mask generation (see note on these methods for additional details).
Future changes I want to add to the Mask class (names are all working titles only):

bounding_box - return an x, y, width, and height where all true bits are contained. Useful for a potential crop or draw_box methods on images to identify where particular features are on an image.
expand and contract - fill in gaps in the true bits or remove them from the edges of true bit areas. Useful for cleaning up errant mask bits that are false that are surrounded by true bits (or vice versa).
regions - return an Array of regions (same response as bounding_box above) where all true bits that touch each other are considered a "region", and the array represents all distinct areas in the mask that don't connect.

Thoughts welcome! I like the implementation of Mask, but unsure about some of the interface method implementations. And of course, all of the above is contingent on @sanks64 accepting it :) Please let me know if I begin to overstep the purpose of this library and these methods and objects are better suited for its own.

Thanks for the PR.
Honestly, this looks pretty specific (i.e., I'm not sure if a large number of users need it). It's also hard for me to reason about performance.
If you think some parts could be useful independently, we might consider keeping them. Otherwise, I would suggest creating a third-party library (which, by the way, can be mentioned in README.md). At some point we will also have 1.0, so this is going to guarantee stability of that library.

Btw, I think you should be able to create branches in this repository? Feel free to do so if it's more convenient.

Sounds good, I'll close this PR and migrate it to its own repo. The set of changes I outlined above were intended for information extraction from images, whereas this library seems to be (currently) for the modification of images instead. Sorry for misinterpreting the long term goals of this project :) Anything I find along the way that I think would be beneficial to this library I'll be sure to port over :+1:
Regarding branches - I've been using forks for so long that it's neither here nor there on where the branches are, both are equally convenient :sweat_smile:


Windows Hello, SCRIL and Pin Reset

Hi
We are trialing Windows Hello for Business with goal to disable password completely with users restricting to login via Windows Hellow(by enabling   Smart card is required for interactive login) and remove password credential provider.
One thing we are struggling with is, how admins can reset the PIN if users forget their PIN. Right now if we enable PIN reset option for users and user try to reset the PIN, the reset screen asks for user password to verify the identity, but we have disabled the password credentials and by enabling the smart card is required options in user profiles, , Active Directory changes the affected user's password to a random 128 bits of data.. so there is no password anymore.
In short by enabling SCRIL and enforcing user to login via smart card/Windows Hello only, how admin/users can reset their PIN if forgotten.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d9dae9da-eaf0-c209-7c65-be8d2c1ada12
Version Independent ID: 28b6788d-7982-23c2-5f19-f80690ebc0ce
Content: Pin Reset
Content Source: windows/security/identity-protection/hello-for-business/hello-feature-pin-reset.md
Product: w10
Technology: windows
GitHub Login: @mapalko
Microsoft Alias: mapalko

@officedocsbot assign @jvsam

Hello @iffarrukh, have you tried the recommendation on the doc to generate a new random 128 bit password?

Although a SCRIL user's password never expires in early domains, you can toggle the SCRIL configuration on a user account (clear the check box, save the settings, select the check box and save the settings) to generate a new random 128 bit password....

As for the Pin Reset Service, there are some requirements that you need to meet for it to work correctly. Have you looked at the Windows Hello for Business deployment guide to re-check your implementation? If you are using Azure AD, please look at the Passwordless scenarios here specifically the one where "User manages their Windows Hello for Business credentials."
For further troubleshooting, it will be best to open a service/support ticket. There are also other support resources that you can explore like the Microsoft Tech Community or the Technet forums where you can post your question and get help from the community.
Kindly keep us informed if you find any relevant information that can be incorporated into this documentation and we will submit it for review. We always strive to give users the best Windows 10 experience by ensuring that contents of the Microsoft Docs are useful, accurate and up-to-date.
Thank you.

Duplicate of #5213. Closing this issue.
@officedocsbot close


v0.3.305 ChatId error if using group id

Hello.
I found a bug in v0.3.305, ChatId error if using group id, which begin with minus "-" sign.
If you using group id, bot didn't start & the following error appears.
If you use direct ChatId no problems occur.

2018-03-06 19:04 +03:00: [19:04:21 ERR] ChatId is invalid or missing in Telegram config
2018-03-06 19:04 +03:00: [19:04:21 ERR] Error in reading Telegram config
2018-03-06 19:04 +03:00: Application startup exception: System.ApplicationException: Telegram config is invalid - please check contents!
at CryptoGramBot.Startup.ConfigureConfig(IContainer container, IConfiguration configuration, ILogger1 log) in C:\projects\telecoinigy\CryptoGramBot\Startup.cs:line 192    at CryptoGramBot.Startup.ConfigureServices(IServiceCollection services) in C:\projects\telecoinigy\CryptoGramBot\Startup.cs:line 155 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.ConfigureServices(IServiceCollection services)    at Microsoft.AspNetCore.Hosting.Internal.WebHost.EnsureApplicationServices()    at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication() 2018-03-06 19:04 +03:00: [19:04:21 FTL] Application startup exception System.ApplicationException: Telegram config is invalid - please check contents!    at CryptoGramBot.Startup.ConfigureConfig(IContainer container, IConfiguration configuration, ILogger1 log) in C:\projects\telecoinigy\CryptoGramBot\Startup.cs:line 192
at CryptoGramBot.Startup.ConfigureServices(IServiceCollection services) in C:\projects\telecoinigy\CryptoGramBot\Startup.cs:line 155
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.ConfigureServices(IServiceCollection services)
at Microsoft.AspNetCore.Hosting.Internal.WebHost.EnsureApplicationServices()
at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()

That’s my fault, I didn’t realize there could be negative numbers for the ChatId. Easy fix, I should be able to do it tonight.

Np, i will wait for a new release.
Thank you.


6.1.2 not in maven central

The packages / bundles for the 6.1.2 release seem to be missing in mvn/sonarytype repo.

Thanks much, we have added automated processes to do this, but this last step was gated, and somebody fell asleep at the wheel (it was me). In progress now.

Can you check now?


Create backtracking

Pull Request Description
Please provide a brief description of your changes here.
Changes Made

List the main changes or features added or modified in this pull request.

Checklist

[ ] I have tested these changes locally.
[ ] I have updated the documentation if necessary.
[ ] I have followed the coding style guidelines.

Merging @lazyMonk1010


parsedown-extra dev version - broken image class handling

Hi,
it seems that the latest dev of erusev/parsedown broke erusev/parsedown-extra.
CSS classes in curly braces for images don't work anymore.
Grav's composer.json requires "dev-master as 1.6.0".
I was able to solve the problem for me by changing the requirement to:
"erusev/parsedown": "~1.6.1"
in my composer.json
This might need some more research though.
The parsedown commit, that possibly broke class handling:
https://github.com/erusev/parsedown/commit/48351504deb0336e265a9453cf9acab04fadae6d

Did some more research... The very latest dev of "erusev/parsedown" (dev-master cc5b38c) works fine.
Whatever the problem was - it seems to be gone.
So I'd say everything works as designed.


now-cli should use @now/routing-utils to verify routes config

Similar to how production uses this module for validation, so should now dev to produce matching error messages.

Closed by https://github.com/zeit/now/pull/2871.


ERD: Display relationships on the columns

I think the ERD view would benefit from a different relationship notation (as an option) which is called “connect to columns” in MySQL workbench. It also seems to be the default (or only) option in Microsoft Access and pgModeler.

With this notation it is clearly visible which columns the foreign keys use without clicking on the relationship (which is not possible on printouts).

Hello @serge-rider @tati-kru
Do you know if different types of relationship will be implemented soon or is there work in progress on such an item?
And do you have any ETA about that?
Thank you!

duplicates #1319


question about joint orders and directions

Hi friend, good work.
Could I ask for quad sdk joint orders ?
testing on my robot, not a unitree one.
all my controllers are clockwise. I seems that it's not thecase on unitree..
Could you share your sent joint order and their direction ?
mine are : Fr_haa, Fr_hfe, Fr_kfe, Fl...., Hr..., HL...  ? (from 0 to 11)
mine direction are : (-++ --- +++ +--)
Really hope any help .
Thanks friend
Vincent

Hi! Files with the directions of rotation of the joints can be found in this file

hello, sent you mail. would you take time to check and answer ? Thanks Dmitriy

Ok

Perhaps in this file you will be able to find the changes you need
unitree_go1_ros_driver-vlad_sarm_driver.zip
https://drive.google.com/file/d/1kOIdRwx_eybRgFv5LyhcbvoXw3_LC2JI/view?usp=drive_web
вт, 12 сент. 2023 г. в 19:31, FOUCAULT Vincent @.***>:

hello, sent you mail. would you take time to check and answer ? Thanks
Dmitriy
—
Reply to this email directly, view it on GitHub
https://github.com/mfclabber/quad-sdk_go1/issues/3#issuecomment-1716055306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4FHQMM2WTRFKRF5RJKH4TTX2CE4RANCNFSM6AAAAAA4ITSFBU
.
You are receiving this because you commented.Message ID:
@.***>

thanks Dmitriy


Trying to install OpenRazer

Hey, recently I bought a Razer mouse and found out that its software for Linux is a program or driver called OpenRazer and I have tried to install it but it always ends up with some kernel issues so I was hoping you could fix it or help me fix it.
Screenshots:

I have tried their troublshooting but I have no kernel headers so i dont how to install for the breath kernel so please can u help me. Thank you

We're going to provide a release for UEFI that includes kernel headers.


[solid-start-static]: assets are linked from / instead of using config.base

Reproduction:
Use the default solid-start starter with the static adapter and in vite.config.ts, you set base: "" or base: "./". Run npm run build (or pnpm or yarn).
Expected outcome:
In index.html, assets are linked from a relative path, according to the given base.
Actual outcome:
in both cases, the base path is ignored and the assets are still linked from /assets/....
Workaround:
Use sed to fix the path, e.g. sed -i 's/\\/assets/assets/g' dist/index.html, but that's not an ideal workflow.

Fixed in PR#311


Benchmarking: ensemble memory

For manuscript revisions, we'd like to include benchmarking of memory usage in Medusa for an ensemble compared to the equivalent individual cobrapy models. The benchmarking should include a range of ensemble sizes (e.g., 10-1000 members). Repeating for ensembles with more/less diversity (e.g., greater number of features) could be interesting but not necessary at the moment.
The benchmarking should be done in a jupyter notebook that will be included in the documentation.

Closed by @Tjmoutinho in #51


Rename repo to xenon-examples

Most other repos in https://github.com/xenon-middleware are named xenon-*. The examples  repo should follow this naming scheme.
The repo is linked to in several places, these also need to be updated.

Agree

did the simple thing. now let's see what breaks (although github redirects so breakage may not be such a big problem)

renamed to xenon-tutorial actually


Failing when switching toolchains

Attempting to run cargo +nightly test then cargo +stable test fails due to the generated skeptic-tests.rs file not being properly handled.

Hmmm, actually now I'm seeing the following error too:
clang: CommandLine Error: Option 'h' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options

Maybe something's wrong with my system?


Update tests

Seems mostly ok but I'd like to suggest the following additions be made before merging:

Use tabs everywhere, you've committed files with mixed space/tab indentations. I'm religiously into tabs so please be mindful of that :)
This only adds test-all.sh, would be nice to have an equivalent bat file for Windows too.

OK, it will be done


Update fetch functions and guzzle client instanceissue

Purpose
This pull request introduces v1.1.0 of FetchPHP, addressing key improvements in performance, flexibility, and error handling, while introducing custom middleware support. The most significant change is the deprecation of the fetchAsync function in favor of the more consistent fetch_async.
Linked Issues:

Improves client efficiency by reusing a singleton Guzzle client.
Addresses edge cases related to empty or malformed JSON handling.
Allows developers to add custom middleware for advanced request management (e.g., retries, logging).

Approach
How does this change address the problem?

Singleton Guzzle Client: By using a static variable, the Guzzle client is instantiated once and reused for multiple requests, reducing overhead. This improves performance, especially in applications making frequent HTTP requests.
Custom Middleware Support: Developers can pass a custom Guzzle client with middleware via the options['client'] parameter, adding flexibility for logging, retries, and request manipulation.
Deprecation of fetchAsync: To improve consistency, fetchAsync has been deprecated, and fetch_async is introduced. The new naming scheme aligns with best practices and future-proofs the library.
Enhanced JSON and Error Handling: The Response::json() method now handles empty or malformed responses more gracefully, throwing exceptions for decoding errors while returning null for empty bodies.

Open Questions and Pre-Merge TODOs

[ ] Deprecation Handling: Have we sufficiently warned users about the deprecation of fetchAsync in all documentation?
[ ] Documentation Updates: Is the newly added example for custom middleware comprehensive enough?
[ ] Thread Safety Considerations: Should we provide more guidance for using FetchPHP in multi-threaded environments where the static client might introduce concurrency issues?

Learning
During the research for this release, we investigated:

Singleton Design Pattern: Studied the impact of reusing a single Guzzle client to minimize memory usage and reduce the overhead of repeated instantiation.
Custom Middleware Implementation: Reviewed Guzzle's middleware stack to ensure that FetchPHP could support logging, caching, and retry mechanisms.
Error Handling Best Practices: Investigated proper handling of JSON decoding errors, ensuring that developers receive clear feedback for empty or malformed responses.

This pull request aims to make FetchPHP more robust and versatile while maintaining a smooth migration path for existing users while also pereparing for release of version 1.1.0. Let us know if any changes or additional feedback are needed before the merge!

Closing this in favor of a better refactored PR.


Color functionality

Since today the Amazon Echo supports color changing of Hue bulbs. Would it be possible to implement this so I can change the color of my MiLight bulbs through Domotocz using Ha-bridge?

Duplicate of #327

Closing as issue us already tagged


Kasan error when exiting task.

I just got a KASan error, when a task is exited.
I am using the simulator for this test.
It seems related to the semaphores.
I may not be able to further troubleshoot this today, but here is a stack trace in case anyone has any ideas:

Can you try CONFIG_SIM_ASAN which could report more detailed info

The issue is within nxsem_freeholder() were there is a NULL-pointer dereference.
I see that pholder->htcb is NULL, but the code tries to use pholder->htcb->holdsem directly, without a check.
I am not sure if a check is missing here, or indeed this field shouldn't be NULL (and thus the root cause is elsewhere).
@pkarashchenko This issue may be of interest to you.

Yes. I will try to take a look into it as soon as I can. Most probably this weekend

I did a brief look and see the 3 calls of nxsem_freeholder are done from nxsem_foreachholder loop that has DEBUGASSERT(pholder->htcb != NULL); and the only other call of nxsem_freeholder is from nxsem_release_all that is called from nxsem_recover. Based on your log it is a case of nxsem_recover that is called from nxtask_recover. We need to debug how it happens that htcb->holdsem->htcb != htcb and is actually NULL.
I'm filling like nxsem_recover has a bug. Do you have any sample code that can help me to reproduce an issue?

@pkarashchenko Unfortunately I haven't been able to create a minimum working example.
My code runs Lua in a pthread, and executes the Lua tests suite (which is quite complex, and exercises lots of APIs).
After exiting this pthread, the error is triggered.
I am trying to narrow it down more...

I finally got it!
The semaphore is freed before its holder is released!
Later on when the holder is to be released, as it still has a reference to the (now deallocated) semaphore, KASAN throws an error.
I am currently testing on 59416af3e697ab89a85f8598751654422f63d46c, as it is one of the revisions that reproduce the issue easily.
So, what I did is to add the following to mm_free():
  extern dq_queue_t g_readytorun;
  struct tcb_s *rtcb = g_readytorun.head;
  if (rtcb->holdsem && rtcb->holdsem->sem == mem)
  {
	  DEBUGASSERT(0);
  }

This is to indicate me that a semaphore is to be freed, while it is still being referenced by this task's holder.
The assertion indeed fires, and KASAN is right to complain later on.
The stack trace at the time of the failure is this:

To my understanding the issue is that the file is locked at fs_tmpfs.c line 1418, and then deallocated at line 1446 without it being unlocked first.
And thus, the lock causes a holder to be allocated for this task which ends up pointing to a destroyed object.

This is fixed in 8c52633 (so that's why it is not reproducible on the latest master).
Closing...


Wiki RLiveObjectService documentation isn't up to date.

The documentation shows still the old way of using the RLiveObjectService.
But it's deprecated (issue #639) and not usable anymore.

Done.

@jackygurui Thanks!


Simplify writing custom interceptors for upgraded properties

For custom interception we should simplify the whole process. Right now developer needs to know in details how interception annotation tool works. We should try to simplify that.
Developer should be able to define interceptor just as:
class AbstractDependencyReportTask {
    @ReplacesEagerProperty(adaptor = ConfigurationInterceptors.class)
    public abstract SetProperty<String> getConfigurations();
}

@Deprecated
@BytecodeUpgradeAdaptor
public static class ConfigurationInterceptors {
    @BytecodeUpgrade
    static Set<Configuration> getConfigurations(
        AbstractDependencyReportTask thiz
    ) {
        // Code...
    }

    @BytecodeUpgrade
    static void setConfigurations(
        AbstractDependencyReportTask thiz,
        Set<Configuration> configurations
    ) {
        // Code...
    }
}

We should recognize setters and getters and also take care of binary changes.
We should also make sure a class is marked as @Deprecated so users won't use it directly.

I've been thinking about this a bit, and I'd like to make a few changes:

Let's call the class ${UpgradedPropertyName}PropertyAdaptor; we'll need one for each custom-upgraded property.
Make the adaptor a static inner-class of the upgraded task or extension type. This adds a bit of noise, but we can put it at the end of the class.
Make the adaptor class package-private. We don't need the adaptor to be part of the public API, and if we put the generated code in the same package, it can access the adaptor class just fine -- we already agreed to make the methods package-private anyway.
If we make the adaptor class package-private, there's no need to mark it as @Deprecated either.
I'd lose the @BytecodeUpgradeAdaptor annotation. It's main function was to mark the class as an entry-point for IntelliJ's / ErrorProne's unused detection, but we'll be referring to it from the @ReplacesEagerProperty annotation, so it's not needed.

Here's how I think the resulting code should look like:
public class AbstractDependencyReportTask extends ... {

    // ...

    static class ConfigurationsPropertyAdaptor {
        @BytecodeUpgrade
        static Set<Configuration> getConfigurations(AbstractDependencyReportTask thiz) {
            return thiz.getConfigurations()
                .map(configurations -> configurations.stream()
                    .map(configurationName -> ConfigurationFinder.find(thiz.getProject().getConfigurations(), configurationName))
                    .collect(ImmutableSet.toImmutableSet()))
                .get();
        }

        @BytecodeUpgrade
        static void setConfigurations(AbstractDependencyReportTask thiz, Set<Configuration> configurations) {
            thiz.getConfigurations().set(configurations.stream()
                    .map(Configuration::getName)
                .collect(ImmutableSet.toImmutableSet()));
        }
    }
}

How about this terminology?

the "call-site" is the class that has the call with the old semantics that we want to upgrade
the "source class" had the old API we want to upgrade (we can call it the "source API"); in the typical case the source and target classes are the same
the "target class" has the new we API want to upgrade to (we can call it the "target API")
the "adaptor" is the class that describes how the intercepted source behavior is to be adapted to the target behavior
there is also a generated "bridge" class that delegates to the "adaptor"

In the above example AbstractDependencyReportTask is both the "source" and the "target" class, with the new SetProperty<String> getConfigurations() method being the "target API," while "void setConfigurations(Set)is the "source API." The "adaptor" isConfigurationsPropertyAdaptor. The "call-site" is the user code that calls setConfigurations()` that we are upgrading.
Because the "call-site" can be in any package, we can only inject replacement code that calls public APIs. However, we don't want the "adaptor" class or its methods to be part of the public API, because then it would add noise to auto-completion etc. Instead we keep them package-private, and add a generated public "bridge" type in the target package whose only job is to bridge the public-private barrier.
The decorator for ConfigurationsPropertyAdaptor looks like this:
package org.gradle.api.tasks.diagnostics; // Same as the "target" class

@Generated
public class $$BridgeFor$$ConfigurationsPropertyAdaptor {
    public static Set<Configuration> getConfigurations(AbstractDependencyReportTask thiz) {
        return AbstractDependencyReportTask.ConfigurationsPropertyAdaptor.getConfigurations(thiz);
    }

    public static void setConfigurations(AbstractDependencyReportTask thiz, Set<Configuration> configurations) {
        AbstractDependencyReportTask.ConfigurationsPropertyAdaptor.setConfigurations(thiz, configurations);
    }
}

By using the $$BridgeFor$$ prefix we make sure that even though the class is public, it will not pop up in auto-completion in the IDE unless the user explicitly looks for it.
Later, when we start to compile build logic against a published API JAR, we can omit these generated classes from the API JAR, and hence make them completely invisible to the compiler and IDEs.


Implement block signature aggregator

Addressed all comments, except the refactor suggestion, which I am going to start soon


fixing the "No input file specified" error

This should fix #485

Would this mess up repositories that are named cache themes etc due to the directory check?

Sorry can't access this PR for that reason, not sure it will even fix the "No input file specified" error.


Delta Lake data components has incorrect type mapping for delta_kernel::schema::DataType::Map type

Describe the bug
Configure a databricks table with map type data, when querying through spice under delta lake mode, it panic and fail with the following error:
Unexpected bitwidth and signed
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: arrow_ipc::convert::get_data_type
   3: arrow_ipc::convert::<impl core::convert::From<arrow_ipc::gen::Schema::Field> for arrow_schema::field::Field>::from
   4: arrow_ipc::convert::fb_to_schema
   5: arrow_ipc::convert::try_schema_from_flatbuffer_bytes
   6: arrow_flight::<impl core::convert::TryFrom<&arrow_flight::gen::FlightData> for arrow_schema::schema::Schema>::try_from
   7: <arrow_flight::decode::FlightDataDecoder as futures_core::stream::Stream>::poll_next
   8: <arrow_flight::decode::FlightRecordBatchStream as futures_core::stream::Stream>::poll_next
   9: flightrepl::run::{{closure}}
  10: tokio::runtime::park::CachedParkThread::block_on
  11: tokio::runtime::context::runtime::enter_runtime
  12: spiced::main

This is because the delta_kernel::schema::DataType::Map type is wrongly mapped to arrow type DataType::Dictionary, the equivalent arrow type should be DataType::Map instead
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Runtime Details
Spicepod
Add the relevant spicepod.yml section.
Output of describe table
Add any relevant describe table output here.
Output of explain query
Add any relevant explain query output here.
E.g. explain select 1
+---------------+--------------------------------------+
| plan_type     | plan                                 |
+---------------+--------------------------------------+
| logical_plan  | Projection: Int64(1)                 |
|               |   EmptyRelation                      |
| physical_plan | ProjectionExec: expr=[1 as Int64(1)] |
|               |   PlaceholderRowExec                 |
|               |                                      |
+---------------+--------------------------------------+

spice, spiced, OS info

spice version: spice version
spiced version: spiced --version
OS info: uname -a

Have you tried this on the latest trunk branch?

[ ] Yes
[ ] No

If possible, run spiced with DEBUG log level
By setting the environment variable SPICED_LOG="task_history=DEBUG,spiced=DEBUG,runtime=DEBUG,secrets=DEBUG,data_components=DEBUG,cache=DEBUG,extensions=DEBUG,spice_cloud=DEBUG"
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Closed by: https://github.com/spiceai/spiceai/pull/3776


docs: add useHover demo link

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Lambda Expression is wrong. Correct it.

Origin: next=> async context =>
Current: async (context. next) =>

Hi @chao-zhou, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Thanks a836f78ebe00fbdba6554e128f6173963ea9d917


Trivial solution set for Adjoint functor theorem

Hello, i am interested in the proof in the Adjoint functor theorem in the library. The usual proof of AFT requires that the solution sets are indexed by a small sets. In the proof given in the library, no such requirement seems to exists.
Doesn't this make the entire solution set requirement moot? For example, the following compiles when appended to SolutionSet.agda.
trivial : SolutionSet′
trivial = record {
  S₀ = λ {A X} f → A ;
  S₁ = λ {A X} f → C.id {A} ;
  ϕ = λ f → f ;
  commute = λ f → D.Equiv.trans (∘-resp-≈ˡ F.identity ) D.identityˡ
  }

Am I missing something?

I believe the above trivial solution set works for any functor F.
 I don't entirely understand them either Set-theoretically or in Agda. I do know that the smallness condition usually prevents the use of the above trivial solution in Set-theory.
This doesn't make the AFT proof wrong of course. It's just odd to have non-small solution sets. Feel free to close.

I am a bit suspicious of the size of completeness required; it seems like this would run afoul of https://ncatlab.org/nlab/show/complete+small+category

I now realize that I haven't seen a MLTT analogue of Freyd's argument that if a locally small category is largely complete it is a poset. Can it be done, and if not constructively with the classical proof, can a different proof be found?

See https://mathoverflow.net/questions/438333/small-complete-categories-in-hottlem/438568#438568

So, does this mean that the proof has a problem? Should Agda accept it? Pinging @HuStmpHrrr who did the original.

The proof is fine, it’s just that the hypothesis are too strong to make it something you can actually use.

Is there a PR which simplifies the proof. I would like to take a look.


BUG: segfault on Windows with latest nightly wheels

As seen in many MNE-Python CIs starting yesterday (things were okay using nightly wheels on Friday Dec 15 ), locally on Windows I can replicate with:
Python 3.11.5 | packaged by conda-forge | (main, Aug 27 2023, 03:23:48) [MSC v.1936 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import faulthandler
>>> faulthandler.enable()
>>> import scipy
>>> import scipy.sparse
Windows fatal exception: access violation

Current thread 0x00000a7c (most recent call first):
  File "<frozen importlib._bootstrap>", line 241 in _call_with_frames_removed

Not sure how to debug further. Nothing obviously jumps out to me based on commits in the last few days :(

Okay fortunately we print out versions, last one that worked according to MNE-Python CIs was:
├☑ numpy                2.0.0.dev0+git20231212.9726755 (OpenBLAS 0.3.23.dev with 2 threads)
├☑ scipy                1.12.0.dev0+1884.1fd74eb

and locally where it fails I can see:
>>> import scipy
>>> scipy.__version__
'1.12.0.dev0+1884.1fd74eb'
>>> import numpy
>>> numpy.__version__
'2.0.0.dev0+git20231215.08e6252'

So I actually wonder if it's a problem with some change in the NumPy version that got installed. Maybe the pip-pre wheel just needs to be recompiled against this newer version or something?

I'm assuming that you're getting the nightly wheels from https://anaconda.org/scientific-python-nightly-wheels/scipy / https://pypi.anaconda.org/scientific-python-nightly-wheels/simple/scipy/.
The last windows nightly wheels uploaded to there was 1 month 25 days ago.

Yeah, the commit matches 1fd74ebc2fe61d432c6fa347d8d8c4a2d0d1619f

That's correct. Is the advice then not to test the nightly wheels, or are they expected to be updated at some point? This would be a bit of a shame since the nightly wheels for other packages do seem available (or at least were a couple of months ago I think), and seems best to test on Windows if possible.
If people shouldn't test them, I wonder if it's possible to yank the wheels from there? Seems like the wheels going away might be better than them staying there unusable with the other nightly wheels.

cc @rgommers who was looking into the failures causing gh-19605.

I think we'll get that stuff patched up pretty soon, a lot of the cases you can just cheat and use np.dtype("long") to restore the old NumPy behavior for now. It is super annoying to do NumPy main + SciPy main on Windows though, and Ralf and I got pulled to other stuff I think.
As for deleting the nightly wheels, you can do that with the push of a button if you have the right permissions. I actually can't do that because there was a decision to scope privileges so that no one person had "too much power" if compromised or whatever. I think the folks with permissions may be documented somewhere though.

Yeah ... that doesn't make too much sense. There's 10 people with access, with only 3 from SciPy, with me the only one actually likely to actively deal with wheels right now. We should add you to that list @tylerjereddy (If you'd be compromised, we'd have much bigger problems than a few nightlies:)). And we should add @andyfaff as well. Should I put in a request for both of you?

Is the advice then not to test the nightly wheels EDIT: on Windows, or are they expected to be updated at some point?

They should update if we fix the issues, but I'd normally only test nightlies on a single platform (x86-64 Linux).
Maybe this situation is exceptional though, because at least for debugging towards the end of the numpy 2.0 release cycle, you may need other wheels - building everything you need from source on Windows is quite challenging, SciPy in particular. I'd suggest that the wheels for all other platforms should stay, but preferably not be used in regular CI.

Should I delete the Windows ones right now? There's something to say for that either way, since they still work with numpy 1.2x. But if they don't work with 2.0.0.dev0 then yes, probably not helpful right this minute.

@rgommers, yes that would be useful. Happy to use 2FA.

Should I delete the Windows ones right now?

I would. The usefulness of the nightly wheels is directly related to their freshness.

Okay, deleted everything that was 2 months old. The wheels for all platforms except Windows are present and <=4 days old right now.

Since the wheels are no longer available should be okay to close this as a duplicate of gh-19605 now

@andyfaff and @tylerjereddy can you share your username for anaconda.org, to request permissions for?

username: treddy

username: andyfaff


build image in podman?

Hi,
from my understanding osbuild-composer can only build image based on the same running OS (Fedora images from Fedora OS, ...).
Is it possible to build images inside a podman container to avoid this limitation?
I have tried to install osbuild-composer in a fedora:34 container but I cannot start the osbuild-composer.socket as systemd is not started.
Thanks

See PR#1427, that might be what you are looking for.
Check out the docker compose file in the repo for how to run things in containers, but that's not really supported, so the above PR might be what you are looking for.

Hello!
Thanks for your interest in this project. As Tom said, this is something that's currently being worked on, stay tuned for future releases.
If you have any more questions about this project, feel free to open a thread in our discussions: https://github.com/osbuild/osbuild-composer/discussions/categories/q-a I believe that discussions are a better place for questions. :)
I'm closing this as I believe that this question is answered. Feel free to reopen or start a new thread in discussions.

Thanks for the reply.
PR#1427 looks very interesting.
Can you point me in the direction of the docker compose file. I only manage to find a reference to it in NEWS.md.
Thanks

Sure, https://github.com/osbuild/osbuild-composer/blob/main/distribution/docker-compose.yml :)


Plugin Creator's Guide: fix links display

Page: https://www.spinnaker.io/guides/developer/plugin-creators/#create-stage-class
Fix:

fix links in Create Stage Class section; links are not displayed as links but rather as code snippets

@aimeeu will work on this


PagingHandler.Tracer is missing for pageable operations

Recall that this is off by default. Did you set inject-spans to true?


Mibao D700

Hi,
I have a Mibao D700 and i have the dump file using the backup.tar.gz.
Is it possible to add compatibility with this amazing firmware?
Thank you

It depends on the platform.
Share your backup with me and I will take a look.

I also have a Mibao D700 (which seems to be the same found in the issue #124, model q321br). Is there anything I could do to help adding support to this camera? Do you already have a backup? If not, I could send you mine.

I forked the project and added preliminary support for this model. It seems to be working nicely, I just tried PTZ controls, RTSP and snapshots, and they all seem to be working. I'll test it more thoroughly over the following days.

I also have a Mibao D700 (which seems to be the same found in the issue #124, suffix q321br). Is there anything I could do to help adding support to this camera? Do you already have a backup? If not, I could send you mine.

I already have the backup file if the model is q321br_lsx
If your model is q321br without _lsx then is different.
In this case, please share your backup with me.

Sure thing, there you go: https://we.tl/t-bpyL3BW3id

Thank you.
File downloaded.

The exact model is q321br_lsx
Check backup/init.sh

You're right, my bad; I saw the "q321br" string (without "_lsx") somewhere inside the backup files and assumed that was it.

i've try to dismount my camera to check the chip but not luck and i've tried to install qg311r hack but any port was opened and the cam was soft-bricked, i've extract the sd and after 2 restart i've recovered it.
Did you need my backup? i've shared with you and screenshot of my research.

If you share with me your backup, I can try to add the support for this cam.
But I need a backup before you apply the hack.

could you send me an email (my email in my profile) to send you the link to download the firmware please?
Thank you

Check the email address in the paypal link.

i can't find it. i've uploaded to mega. https://mega.nz/file/75tlwAiR#h3tJuPyeliHh1SThgGX7KpmmkoRYz6IAA7ODwcSFjig

Please, try this beta:
q321br_lsx_0.1.9.tar.gz
Could you please confirm that it's a ptz cam and the resolution is 3k?

The cam is this https://www.amazon.es/gp/product/B08FCDJDZ9/ref=ppx_yo_dt_b_asin_image_o00_s00?ie=UTF8&psc=1
And yes it's a ptz cam and the resolution in the specs is 1296x 2304 (1296P).
Today asap i will test the beta and i will write my feedback. thank you!

bricked, i've extracted the sd and the cam doesn't started to the default firmware.

Are you able to get a log with a serial connection?

no, it's complicated to dismount the case to me and i haven't got a serial cable to do it.

Please try this binary.
Clear your SD and unzip the archive.
backup_q321br_lsx.gz

i've tried it but it's bricked :( no motion or sound when i've started. thank you to try it with me

Weird. This solution should work.
Is the led on?
Is the power adapter/cable ok?

If led and power are ok, please another try:
backup_q321br_lsx.gz

Yes, it's connected and the cable and charger is OK. I've supposed that not run because after the brick i've extracted the micro sd and format in the pc in fat32 to install in a rpi. last time when i've installed the firmware, i've needed to format the microsd in the cam with the yi iot app.

Hi 👋 i need firmware caméra mibao d600 please 🥺

Hi 👋 i need firmware caméra mibao d600 please


Bug fix related to USB chunked data.

This PR resolves issue: #204 . Details in issue description.
CC: @r4gus

This bug fix is already included in #211 so this PR can be discarded if #211 will be merged.

Fix was merged with PR #211


Add support for Frame

Goals
I would like to use Frame (https://frame.sh) with Gnosis Safe. Currently when I load the Gnosis Safe app while using Frame I get this error message:

Requirements
When the user clicks "Connect Wallet" they should have an option for connecting to a generic Web3 interface. Or alternatively, a button for connecting using Frame, specifically, the same way that MetaMask has its own button, although I would prefer that all Web3 interfaces be connected using a generic "Web3" button rather than each getting its own button; this will reinforce that Web3 is an open standard and that these aren't siloed proprietary interfaces.
Links
https://frame.sh
https://github.com/floating/frame
https://github.com/floating/eth-provider

Please create an issue in https://github.com/blocknative/onboard, this is the library we use for wallet integrations. As soon as frame integration is available there we can evaluate adding it

The issue is available there and support will be released in the next onboard version: https://github.com/blocknative/onboard/issues/600

In addition to blocknative/onboard#600, which adds support for injected providers, Onboard also includes Frame as a wallet option. Adding { walletName: "frame" } allows users to natively connect to Frame.

Closing because it can be used as an "injected" wallet.


Publish snapshots to OSSRH Maven repo

Successfully published to https://oss.sonatype.org/content/repositories/snapshots/org/disq-bio/disq/.

Thank you, @tomwhite!

Thanks for merging @heuermh


move SCC initialization to kas-o

We now have a CRD for SCC, which means we can initialize this early.

/test all

/retest

/retest

/lgtm


User Permissions Blueprint

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

This PR adds a blueprint for enforcing user "Permissions" (currently known as "Capabilities", to be renamed to avoid confusion with "Server Capabilities") as an alternative to Role Privilege Level in the Traffic Ops API's authorization.
Which Traffic Control components are affected by this PR?
None
What is the best way to verify this PR?
Read the blueprint.
The following criteria are ALL met by this PR

[x] Tests are unnecessary
[x] Documentation is unnecessary
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Check if the user is trying to delete their own lock. If so, check the user’s role(and perms). If they have the cdn-locks-delete-cap permission, then let them proceed with the request.
However, if the user is trying to delete somebody else’s lock, check to see if they have the cdn-locks-admin-delete-cap . If they have it, then proceed with the request. If not, then return a 403.

i would just suggest that the "cap" aka permission is named intuitively. cdn-locks-admin-delete-cap doesn't mean anything to me and it has a "role" embedded in the name which seems like a no-no. this would make more sense to me: cdn-locks-delete permission (to delete your own locks) and cdn-locks-delete-all permission (to delete any/all locks).

Check if the user is trying to delete their own lock. If so, check the user’s role(and perms). If they have the cdn-locks-delete-cap permission, then let them proceed with the request.
However, if the user is trying to delete somebody else’s lock, check to see if they have the cdn-locks-admin-delete-cap . If they have it, then proceed with the request. If not, then return a 403.

i would just suggest that the "cap" aka permission is named intuitively. cdn-locks-admin-delete-cap doesn't mean anything to me and it has a "role" embedded in the name which seems like a no-no. this would make more sense to me: cdn-locks-delete permission (to delete your own locks) and cdn-locks-delete-all permission (to delete any/all locks).

Yeah makes sense. I just wanted to jot things down so that I dont forget later.

If Roles are taken out of the API, then would we not still need to make API changes, so that the configuration file contents can be returned through the API? It's less work than manipulable objects from the database, to be sure, but it's not nothing. How would we migrate existing Roles to the on-disk configuration? What happens to users with the "Foo" Role if that Role is removed from the configuration file? Testing this would also be difficult to do in the current framework, since creating or deleting Roles would require restarting Traffic Ops, which for the moment makes it a manual process during testing. I also think that being able to manipulate user permissions through Traffic Portal, and in particular the ability to create a new service account with permissions for only a few endpoints it needs quickly through Traffic Portal, would be a shame to trade away for the very manual process of ensuring everyone's okay with restarting TO, ssh in and edit a configuration file, then perform the restart and signal the all-clear (or, using Ansible as you said, which would probably be a longer process but safer than ssh-ing manually)

That would also preclude the tenancy of Roles, that you brought up earlier.

If Roles are taken out of the API, then would we not still need to make API changes, so that the configuration file contents can be returned through the API?

Not necessarily, we don't need the API to return which permissions belong to which roles.

How would we migrate existing Roles to the on-disk configuration? How could that migration be undone for downgrades?

Since User Permissions are optional, it seems like we'll still have to define privilege levels for every route we add. So, I'd think our existing roles wouldn't even belong in the on-disk config. Their permissions would continue to be defined by the privilege levels we assign to routes. If people created custom roles with different privilege levels, they will have to translate those custom roles into the new User Permissions model.

Testing this would also be difficult to do in the current framework, since creating or deleting Roles would require restarting Traffic Ops, which for the moment makes it a manual process during testing.

Testing permissions would be pretty easy via unit tests in this manner. You just simply update TO's internal memory representation (e.g. map[string]map[string]struct{}), then make an HTTP request. For the most part, you wouldn't have to mock the DB very much, since the request would be 403'd before even needing most DB queries. You'd probably just have to mock the DB for the user data (i.e. which role the user has). Long-term, testing via this method would probably be easier than writing API tests just to verify permissions functionality. In fact, the API tests we currently have to test privileges are pretty convoluted and confusing to begin with, since they require creating a new session, logging into the new session, and using the new session to attempt the requests.

I also think that being able to manipulate user permissions through Traffic Portal, and in particular the ability to create a new service account with permissions for only a few endpoints it needs quickly through Traffic Portal, would be a shame to trade away for the very manual process

It wouldn't be a shame if the trade-offs were well-understood and taken into consideration. I think creating roles and assigning permissions will be one of the most rare operations that ever occurs in an ATC environment. The default roles have covered 99% of all cases up to this point, we just want something better now (for security). Since better security is the main goal here, it might make sense to make the implementation of this security feature as secure as possible.

of ensuring everyone's okay with restarting TO, ssh in and edit a configuration file, then perform the restart and signal the all-clear (or, using Ansible as you said, which would probably be a longer process but safer than ssh-ing manually)

It wouldn't necessarily require a restart; we could make it reloadable if restarting TO was a problem. IMO, the way TO is designed, restarting is not really an issue in terms of availability. We can rolling-restart TO and still maintain 100% availability. Also, I would argue that most permissions requests wouldn't be so time-sensitive that we'd need to be able to quickly use TP to add permissions. If something was really time-sensitive, then any admin should be able to perform the time-sensitive task or get the user the time-sensitive data.

Not necessarily, we don't need the API to return which permissions belong to which roles.

You would at the very least need to return which Roles exist, so that new users can be created. I also would be against only allowing users to be created with unknown Permissions, though that would be technically possible.
Also, the new Traffic Portal is banking on visibility into what a user is allowed to do, in order to hide or disable UI elements to deliver different experiences to different users according to their needs. That's pretty heavily requested, and - although I'm not sure if it's totally true - has actually been called "required" for the self-service aspect on which it currently focuses to be production-ready.

Since User Permissions are optional...

Well, at first, yes, but only for a deprecation period. Manual translation of Roles does seem to be the only upgrade path, unless we're going to write a custom tool a la Traffic Vault and MySQL -> Postgresql.

Testing permissions would be pretty easy via unit tests in this manner. You just simply update TO's internal memory representation (e.g. map[string]map[string]struct{}), then make an HTTP request.

The existing API tests do not have access to the internal memory of TO, though. We could very easily make unit tests like you describe, but end-to-end testing would be much harder without testing framework changes.

... this method would probably be easier than writing API tests... In fact, the API tests we currently have to test privileges are pretty convoluted and confusing...

That's not wrong, it would be much easier and they are convoluted. But we could actually test very nearly every single API (calls to external servers and system commands aside, all of them) with unit tests that use mock databases and mock HTTP requests and response recorders - but we don't because firstly that leaves the client untested, and secondly because there's value in an end-to-end test period. Our current tests just happen to fill both of those needs at once (arguably; there are things the client tests can't test for e.g. erroneous extra response fields). As far as being convoluted, the reality is that to use a new Role, one must first log in as the new Role. We can make it easier to access a session structure for a generic Role by writing some testing code to support that, but we can't change that flow because that simply is how the API works.

Since better security is the main goal here, it might make sense to make the implementation of this security feature as secure as possible.

If Permissions aren't good enough  security to manage Roles and Permissions, why are they secure enough for everything else? It's sort of like planning for defeat, seems to me.

Also, I would argue that most permissions requests wouldn't be so time-sensitive that we'd need to be able to quickly use TP to add permissions.

Adding Permissions is unlikely to be time-sensitive, I agree, though I could probably imagine some contrived scenario for a poorly behaved script or something. But removing Permissions can be a security issue that needs to be addressed very quickly, which isn't addressed by just having "any admin... perform... the... task or get the user the time-sensitive data".

Not necessarily, we don't need the API to return which permissions belong to which roles.

You would at the very least need to return which Roles exist, so that new users can be created. I also would be against only allowing users to be created with unknown Permissions, though that would be technically possible.

This is what I meant by keeping Roles in the API but not Permissions. You'd only be able to create Users with Roles that exist in the DB, but the permissions would be defined via config.

Also, the new Traffic Portal is banking on visibility into what a user is allowed to do, in order to hide or disable UI elements to deliver different experiences to different users according to their needs.

One way to solve that would be to simply use the same config file for both TO and TP. The TO one would be authoritative, of course, while the TP one would be simply for hiding everything that their role doesn't allow. Or, we could have an API to return which permissions are currently assigned in TO's config file but still not allow assigning permissions via the API.

Since User Permissions are optional...

Well, at first, yes, but only for a deprecation period. Manual translation of Roles does seem to be the only upgrade path

The new permissions config file could define the current permissions of the legacy Roles, but if we will eventually make User Permissions required, won't that mean that we'd always have to update the legacy Roles to add new permissions as we add new routes/functionality? I.e. every upgrade, we'd have to get all the new permissions and manually add them to the legacy Roles? Why can't we continue to assign privilege levels to routes instead of having to add permissions to legacy Roles with every upgrade? It seems like at least for admin, we shouldn't have to manually assign new permissions to it with every upgrade. Or do you think every new route that's added needs to have a DB migration to add the permission to the legacy Roles?

The existing API tests do not have access to the internal memory of TO, though. We could very easily make unit tests like you describe, but end-to-end testing would be much harder without testing framework changes.

Permissions don't necessarily need tested in an end-to-end manner. We would still obviously have end-to-end tests for every route, but those end-to-end tests could focus on other things besides permissions. In fact, it would probably be overkill to test permissions in an end-to-end test for every route. The unit tests could cover permissions functionality as a whole, and we wouldn't necessarily require the specific permission to be tested on every route (although we could).

Since better security is the main goal here, it might make sense to make the implementation of this security feature as secure as possible.

If Permissions aren't good enough  security to manage Roles and Permissions, why are they secure enough for everything else? It's sort of like planning for defeat, seems to me.

I'm not really sure what you mean here, but storing permissions in a config file simply means there are fewer attack vectors in which an attacker could gain access to more permissions. DBs are usually available over the network, whereas on-disk config files typically aren't. Permissions stored in the DB data means they can be vulnerable to SQL injection. You also have to make sure your DB settings are secure. With a filesystem, you just have to set the proper file permissions so that even if an attacker was able to login to the system, they wouldn't be able to edit the permissions unless they had root (at which point they could do lots of nastier things anyways). I'm not saying Permissions aren't "good enough security"; I'm just saying that on-disk permissions could be considered "better security".

Adding Permissions is unlikely to be time-sensitive, I agree, though I could probably imagine some contrived scenario for a poorly behaved script or something. But removing Permissions can be a security issue that needs to be addressed very quickly, which isn't addressed by just having "any admin... perform... the... task or get the user the time-sensitive data".

Even with on-disk permissions, we could still use the API to quickly change a user's role to one without permissions.

-1 on trying to use a config file over the database.  It is an interesting idea for sure, but I don't think it really makes sense for something like that.
For whatever perceived development savings we think there will be, there will be more operational expense and, to me, I would rather have less operational expense.  I don't want to try to manage permissions across n servers, no matter how good ansible/puppet/etc is at it.
It seems pretty straightforward to just put this in the database so that it can be managed via API and via the UI, I don't really see why we wouldn't just go with that plan.

For the record, I'm not -1 on having permissions in the DB; I just think config-based permissions have some benefits worth considering as an alternative. That is why we have the ## Alternatives section in the blueprint template -- to explain how we weighed the pros/cons and why we chose one alternative over the other. Config-file based API permissions are not even my idea; I just recalled them from my OpenStack days: https://docs.openstack.org/oslo.policy/latest/admin/policy-yaml-file.html.
The config file idea is more about security and performance than it is about dev/maintenance savings. However, I've raised some OpEx concerns as well, in that if we remove the legacy priv-level based permissions, we'll need to manually add any new permissions from new APIs after we upgrade, in order to be able to use them. For example, admin users should generally just have all permissions; we shouldn't have to explicitly assign every single permission to the admin role. The same probably applies to the operations role which might as well be admin anyways. However, for roles like readonly and portal, we probably wouldn't need to add more permissions as we add more routes. For the disallowed role, which by definition has no permissions, should we even allow assigning permissions to it?
I guess as long as at least the admin role is special in that it implicitly has all possible permissions, we wouldn't have to jump through permissions hoops with every upgrade. That would alleviate some of my concerns with this proposal.

...we'll need to manually add any new permissions from new APIs after we upgrade, in order to be able to use them.

Sometimes. For new objects, that is true. But if, for example, we wanted to restrict the modification of DS DSCP properties to people with the ds-dscp-modify Permission, we can preserve existing behavior by granting that Permission to all Roles that already have the ds-write Permission which had been allowing them to do that, in the same migration that adds the new Permission. Or if we split servers into cache servers and "other", then people with the servers-read and servers-write Permissions would have, respectively, the read and write Permissions for both of the two new server categories.

... we shouldn't have to explicitly assign every single permission to the admin role... I guess as long as at least the admin role is special in that it implicitly has all possible permissions, we wouldn't have to jump through permissions hoops with every upgrade.

That's actually already true. The admin, read-only, and operations Roles are handled somewhat specially in that they are modified by seeds.sql, which is to say they're expected to exist in any new ATC installation. In particular, the admin Role has two special Permissions that no other Role is given (by default): all-read and all-write which are intended to convey exactly what it sounds like: admin can view and change anything. I didn't bring that up in the blueprint just because the concept already exists, if not implemented - but I can absolutely mention it if you like.

I don't hate the idea of admin being special in that way, it's just hard to know how to handle people redefining admin between install and upgrade.
It's also confusing to me why we have all-read and all-write instead of just all - all-read isn't used by anything else, not even read-only afaik, and all-write on its own just makes no sense at all.

I don't hate the idea of admin being special in that way, it's just hard to know how to handle people redefining admin between install and upgrade.

That's the thing -- it shouldn't be possible to redefine admin. It would be defined via the code in that it specifically bypasses all permissions checks. I agree just having all would be better than having both all-write and all-read, but having an assignable permission that grants all permissions seems a bit risky. If the admin somehow removed its own all permission, and it was the only one that had it, that role would be locked out of everything and would require manually running some SQL in order to get the permission back. If admin is special in that it bypasses permissions checks, that scenario isn't possible.

I'm good with all that, I just don't know what the upgrade path looks like. If there's multiple Roles with privLevel >= 30, do we delete all but one and rename it to admin (unless there's already one named admin)? If admin already exists but has privLevel < 30, do we escalate its privileges? Either way you're destroying data which makes downgrade difficult, though the first case is a bigger deal for downgrading than the second.

You still have to keep the priv-level around since the feature is optional (initially), right? So there shouldn't be any data loss, and I wouldn't really worry about escalating admin privileges if for some reason its priv-level was lowered, because in reality I'm having a hard time believing that anyone would've actually done that (although it is certainly possible, as are many things that shouldn't be done in TO).

Yeah you're right, it should be possible to roll back for at least one major release because of that. I'm sold; I'll update the blueprint to mention that the admin Role will need some extra protections and special handling.


About LEO and other experiment implement details (like ablation study, conflicts study)

Hi David! I really appreciate what you did in this work, I believe this should be considered as a great progress in meta-learning.  I check your repository and find that the leo experiment and conflicts study mentioned in paper didn't show up here, would you mind adding them to this repository? That would be really helpful, thanks a lot.
p.s. salute to your hard work with only one 1080ti in all these experiments:)

Hi,
Sorry for the late response. I've been occupied with other works.
And thank you for the interests in our work.
We are not planning to release other additional code any time soon as I just don't have enough time.
Just a few pointers to guide you though:

As for LEO experiments, We just added the attenuation part to LEO official code without changing hyperparameters or settings. If you are having trouble with porting to Tensorflow, let me know. I'm willing to help. Also, I'm planning to release a new code for TPAMI extended version of this paper, which includes MetaDataset results (in Tensorflow). So, please refer to that once we release them.

As for conflict study, I think we will release a separate code for this soon (within 1~2 months time frame) after code refactor. If you need to produce results earlier, please refer to the explanations in our paper and [26]. Again if you are having trouble, I'm willing to help.

[26] Santurkar et al. How Does Batch Normalization Help Optimization?
P.S. Just to clarify: Each experiment was performed on a single 1080Ti. But, they were performed in parallel using a multiple of them. Using only a single GPU for the whole paper would be a nightmare. Regardless, thank you for your words.
Best,
Sungyong


Publish 8.0-rc-1

Publish 8.0-rc-1

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.

Your PR is queued. See the queue page for details.

I've triggered a build for you.


Fix: Properly de-init KernelManager singleton and ProfileReport observer across tests

@CoreRasurae let me know when this is ready

@freemo It is ready for testing


Merge Environment files

Rather than using conda update to merge the environments we now merge the environment.yml files directly on the file system and then build the container with all constraints.

@niklassiemer This should fix the issue with the conda update.


Fix handling of ramalama login huggingface

Fixes: https://github.com/containers/ramalama/issues/465
Summary by Sourcery
Fix the handling of HuggingFace login by refining command execution and model path logic, enhance code clarity with refactored methods, and update garbage collection to include more repository paths.
Bug Fixes:

Fix the handling of login for HuggingFace models by adjusting the command execution and model path logic.

Enhancements:

Refactor the model path and existence check methods to improve code clarity and maintainability.
Update the garbage collection logic to include additional repository paths such as 'file', 'http', and 'https'.
Standardize the model type naming to lowercase for consistency across the codebase.

@bentito  PTAL

@bmahabirbu @cooktheryan PTAL

@bentito  PTAL

do you @rhatdan happen to know the pipx command to checkout the pr branch? I can't quite seem to get it right...

No idea, how to do this.
I would do a git clone of the repo and then run
./bin/ramalama

@bmahabirbu @cooktheryan PTAL

Did a quick test and worked for me!
./bin/ramalama login --token=XXX huggingface
The token has not been saved to the git credentials helper. Pass `add_to_git_credential=True` in this function directly or `--add-to-git-credential` if using via `huggingface-cli` if you want to set the git credential as well.
Token is valid (permission: fineGrained).
The token `PC` has been saved to /home/bmahabir/.cache/huggingface/stored_tokens
Your token has been saved to /home/bmahabir/.cache/huggingface/token
Login successful.
The current active token is: `PC`

I was able to login huggingface thanks!

Tried:
$ ramalama pull --authfile /Users/btofel/.cache/huggingface/token huggingface://ibm-granite/granite-3.0-8b-instruct
Error: failed to pull https://huggingface.co/ibm-granite/raw/main/granite-3.0-8b-instruct: HTTP Error 401: Unauthorized

$ ramalama pull --authfile /Users/btofel/.cache/huggingface/foo huggingface://ibm-granite/granite-3.0-8b-instruct
Error: failed to pull https://huggingface.co/ibm-granite/raw/main/granite-3.0-8b-instruct: HTTP Error 401: Unauthorized

if the token is supposed to be referenced as the authfile, I'm not sure it's checking that b/c it doesn't seem to care if it doesn't exist.

@bentito I have never worked with the hugginface login to pull images, so I don't know if this works, but I would love to work with you to make it work.  Could you ping me on the matrix channel.


[10.0-pos_product_available] Not show product stock

I have Odoo 10.0-20170508 installed and your module pos_product_available <IP_ADDRESS>.3 with only one warehouse, only one company and in the pos windows, not show te product stock. Can you help me?

And which user is running Odoo?

Python is running by odoo user, but all the other modules files has the same permission

That's wrong actually


no template folder, unable to create template on joplin v2.6.10 windows, Templates v2.2.0

Joplin 2.6.10, windows, first time installation of plugin-templates
After Joplin restart there is NO template folder.
In tools menu there is NO command to show templates folder.
While trying to create note form template or showing templates,

Create some notes an add the tag template to them.
https://github.com/joplin/plugin-templates#adding-a-new-template

Create some notes an add the tag template to them. https://github.com/joplin/plugin-templates#adding-a-new-template

it worked!
When I read again the WIKI at https://github.com/joplin/plugin-templates/wiki I noticed it was already described.
I have read this three times BEFORE posting issue ticked but didn't get it. Sorry!


⚠ Bofrost.be has degraded performance

In 9eece46, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2327 ms

Resolved: Bofrost.be performance has improved in af86bc5.


Update aws_ec2_contact_point options to include :ipv_6_address

Hi, I am using this great gem.
I added the functionality to be able to deploy on ipv6 as well.
The fixes are small, but I would appreciate it if you could merge them when you have time.
Thank you,

@jksy FYI it is published.

@fernandocarletti
Thank you for the quick response!
I'll use it new version for my software.


Catch HTTP Errors in case pod metrics resources not exist / access forbidden

If pod metrics cannot be loaded (not found or access forbidden) this results in a JS error. Its valid in this cases that API returns that error as metrics could just be not there or user does not have access.
Looks like its even causing display errors in the icon bar of the deployment. (Not tested with compiled binary)

Signed-off-by: Mario Sarcher<EMAIL_ADDRESS>

@Nokel81 thanks, added your changed and squashed the commits


Image-Renderer struggles to render the same image on more than one Graph

I've created some sort of dashboard where I render two Sigma-Graphs at once. Both should be able to use the Image-Renderer. However, when I try to dynamically add another instance, it breaks all the images. Its kinda hard to explain, and as there is no working Codesandbox Example I could quickly modify, I can only provide screenshots for now.
Does anyone have an idea why this could happen and how it could be fixed?
Normally, it looks like this:

But as soon as I dynamically create another, second graph, the image gets somehow removed and also the node's background color changes in a strange way:

Edit:
Weirdly enough, it actually has the image but it's repeated millions of times (that also explains the color difference). However I've no clue on why this happens :D

That seems like a desync between the texture (the image with all the images) and its atlas (the positions and sizes of each image in the texture) - and I've been trying to reproduce something similar recently.
One question though: To allow devs working with two sigma instances with two sets of images that are very different, node.image.ts does not export a renderer, but a factory getNodeImageProgram instead. Do you use the same instance returned by the factory for both your sigma instanced, or do you use two different cases?


pythonPackages.spacy: 2.1.7 -> 2.1.8

Motivation for this change
Changelog:
https://github.com/explosion/spaCy/releases/tag/v2.1.8
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@GrahamcOfBorg build pythonPackages.spacy python3Packages.spacy

Thanks!


CBL-5720 : Enable vector search tests on macOS, linux, and windows

Enabled vector search tests on macOS, linux, and Windows.
Use Vector Search Build 29.
Fixed Android PR Validation on Github Action.
Used a newer windows agent that supports AVX2 required by Vector Search Extension.
Disabled PQ 12-bits test as the tranining size error was fixed after beta-2.

The submodule check will be fixed once C has release/3.2 branch.


lib: avoid duplicate inclusion

Description
For lib/log and lib/utilities, add double-inclusion protection as we're so early in startup that these are loaded explicitly rather than through reloader.sh or even the early lib load loop.
Motivation and Context
This slightly improves performance, but alsö improves debugging by reducing surface area. Both lib/log and lib/utilities are explicitly loaded and then re-loaded again by the library loading loop.
How Has This Been Tested?
This branch is live on my system now.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the code style of this project.
[ ] If my change requires a change to the documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
[ ] I have added tests to cover my changes, and all the new and existing tests pass.

I copied it straight from bash-preexec...but I actually want to use "loaded". It makes it read better if I'm looking at environment variables and makes sense generally.

@davidpfarrell, I think you mistakenly check for "loaded" but set to "defined".
Also- we should probably unset those kind of variables on bash-it-reload invocation

Yes, I haven't yet touched any of the Bash It internal functions. I'll circle back on this one

I've just realize this addresses similar issue to #1826

Yes, I haven't yet touched any of the Bash It internal functions. I'll circle back on this one

let me know if you need any help with that. see _bash-it-reload in helpers.bash

I just haven't had an opportunity to noodle on reload vs restart. It seems like settings should be reset on reload so they can be loaded again, but libraries wouldn't need to be "reset" as there aren't settings in there. An update to Bash It already requires a restart.
That said, I don't feel like I have my thoughts any more spelled out than that one sentence so I haven't done anything with this yet.
(It's easy to lint files, but making behavior changes needs brain focus!)

I just haven't had an opportunity to noodle on reload vs restart. It seems like settings should be reset on reload so they can be loaded again, but libraries wouldn't need to be "reset" as there aren't settings in there. An update to Bash It already requires a restart.
That said, I don't feel like I have my thoughts any more spelled out than that one sentence so I haven't done anything with this yet.
(It's easy to lint files, but making behavior changes needs brain focus!)

so the difference on reload vs restart is that reload only sources the users .bashrc (and his Bash-it setup) while restart actually execs into a new bash instance. This means that you do not need to do anything on restart (as its like opening a new shell) but you should take care of the reload case. Only sourceing the libs again won't work as the variable is already defined. You can however unset the variable at the start of bash_it.sh which is the "main" file that is loaded back when sourceing

I got that part, but I have inadequately articulated concerns about function scope, exported variables, &c. Give me a little to get my thoughts together! 😃

We have two options that I see for the reload unset:

Unset those two variables explicitly, just like we load them explicitly.
Unset variables in a pattern of `_bi*_imported.

I think option 2 is a more generic approach. The function that unsets the variable can be a lib one as well so other places could use it

We have two options that I see for the reload unset:

Unset those two variables explicitly, just like we load them explicitly.
Unset variables in a pattern of `_bi*_imported.

I think option 2 is a more generic approach. The function that unsets the variable can be a lib one as well so other places could use it

I think rename them __bi_imported_log and __bi_imported_utilities and then unset "${!__bi_imported_*}" will catch them all and future additions if any.

I had a brainwave and did a whole different thing. Each lib adds itself to an array of libs loaded, then checks if it's in it. Whatcha think?

I had a brainwave and did a whole different thing. Each lib adds itself to an array of libs loaded, then checks if it's in it. Whatcha think?

Sounds like a good solution!
You can even reset the library when starting to not prevent bash-it-reload


add init function

We don't have tests here but this seems to work in japaric/f3#70. So I'm going to go ahead and merge.


Macos

Hi, the dmg wallet don't run in MacOS Sierra V.10.13.6
Dyld Error Message:
Library not loaded: @loader_path/libboost_system-mt.dylib
Referenced from: /private/var/folders/_s/lwswz6s56m71jdqzr_0s9zp40000gn/T/AppTranslocation/87E00C35-75C1-4DE1-82C2-7F29B29AD9C0/d/Actinium-Qt.app/Contents/Frameworks/libboost_thread-mt.dylib
Reason: image not found
You must copy libboost_system.dylib to libboost_system-mt.dylib to make it work.
Hope you can solve ASAP for others ;)

Install boost with brew:
brew install boost
If you don't know what brew is, visit this page: https://brew.sh

@Webmasterdevil ,
btw. you are simply renaming a non-threaded version into a multi-threaded version.
This is not a solution. And is highly problematic.
The problem with libbost_system-mt.dylib is present in many other coin projects, like Litecoin and even Bitcoin.
There is no general solution that can be applied everywhere.
The most safe way is to install boost libs locally. This has only to be done, independently from future versions of the wallet.

Fixed: https://github.com/Actinium-project/Actinium/commit/a4ef58a2d9a8fac7dd519600506724743f01e54b


session-store clear() not called on invalidate?

I see in the ember-simple-auth code that the session-store implementation provides a clear() hook.  I've created a new application-scoped session store that extends from the Base session store implementation and overrides the clear() function.  However, I don't see that function ever being called when the session is invalidated.  Looking at the source code, I see the clear logic in internal-session.js, but I don't see anything in the code that would suggest to me that the session-store clear() function is going to be called from anywhere.  Am I missing something or is that functionality not currently working?

I should add that overriding sessionInvalidated on my application route (with the ApplicationRouteMixin) does fire as expected

For the moment, this seems to work, but doesn't seem like it should be necessary.  (Application route):
  sessionInvalidated: function() {
  	this.get('session').get('session').get('store').clear();
  }

The session store's clear method is only really being used in tests as the session isn't cleared completely when it is invalidated (only the authenticated section is deleted, all other session data stays intact).


Unstabble CPU Usage

when aplying this themes, after that when write something on chat bar, sudenly my cpu usage raising into 30-50% sometimes into 80-90% make my discord lagging so hard, while i am take off the themes, the problem is gone. (look at bottom right, at electric emote, thats cpu usage)

i was afraid this would happen. there's 3 sections of code that use :has(something). can you delete those parts and see if the performance is still bad?

i was afraid this would happen. there's 3 sections of code that use :has(something). can you delete those parts and see if the performance is still bad?

i cant, because thats part on the core of your themes right ? at midnight.css

i was afraid this would happen. there's 3 sections of code that use :has(something). can you delete those parts and see if the performance is still bad?

oh yeah bruh, the problem at there, after i remvoe it, the problem is gone

ah yes, another one ig, when do slash command, the list of command section still vanilla, is this intentional ?

ah yes, another one ig, when do slash command, the list of command section still vanilla, is this intentional ?

I am still working on fixing stuff like this.

oh yeah bruh, the problem at there, after i remvoe it, the problem is gone but the icon placement at upper right look funny now

Ok, I will try to find a way to replace those lines. It might not be possible without using aria-labels, which I want to avoid because they are language specific.

@AnviIndo I have pushed a fix that slightly modifies the problematic :has() selectors. Could you update your theme and test the performance again?

@AnviIndo I have pushed a fix that slightly modifies the problematic :has() selectors. Could you update your theme and test the performance again?

@refact0r ah alr, the problem has been fixed, ty for your hardwork 👍