trace in bit reverse order

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#857  👈
#845
#841
#830
#829
#825
#818
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shaharsamocha7 and the rest of your teammates on  Graphite

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

Please upload report for BASE (09-19-State_machine_prover@dea43a5). Learn more about missing BASE report.

Additional details and impacted files
@@                      Coverage Diff                      @@
##             09-19-State_machine_prover     #857   +/-   ##
=============================================================
  Coverage                              ?   91.99%
=============================================================
  Files                                 ?       90
  Lines                                 ?    12375
  Branches                              ?    12375
=============================================================
  Hits                                  ?    11384
  Misses                                ?      883
  Partials                              ?      108

Flag
Coverage Δ

91.99% <ø> (?)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cherry pick #698 [Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0]

What this PR does / why we need it:
Cherry pick #698 which updates protobuf version to resolve CVE-2024-24786.

Bump github.com/golang/protobuf to v1.5.4, google.golang.org/protobuf to v1.33.0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes # CVE-2024-24786

/ok-to-test

/ok-to-test

/retest

/approve

/lgtm


Make ^which be an embed

bye character count

This will let us have dismissible messages too! (it's required to have an ims to be dismissible so it actually has to be an embed)
See #967 for how to actually edit higher than character count

Also split on bold headings into individual sections

sections = embed fields


Directed graph not discovered

I would like to point out that some directed graphs are not being discovered by the algorithm. Input example:
t # 0
v 0 2
v 1 1
v 2 3
e 0 1 1
e 2 0 2
t # -1
With a support =1, the algorithm outputs as frequent the subgraphs with 2 vertices but the algorithm seems not to generate the candidate with 3 vertices. Is there something I am missing?  The following is the code's output:
t # 0
v 0 2
v 1 1
e 0 1 1
t # 1
v 0 3
v 1 2
e 0 1 2
Thanks in advance for your time.

I found the same problem. If the directed edge's frm.vlb > to.vlb, the subgraph mining does not consider it in get_forward_XXX_edges

did you find a solution?


Add timestamp to block header

Required by https://github.com/dapperlabs/flow-go/issues/3271 and https://github.com/dapperlabs/flow-go/issues/2255

Thanks! We are using google.protobuf.Timestamp already in the block protobuf, so that should be no issue @turbolent . Merging now.


[bug] Cannot find module ... or its corresponding type declarations

Link to minimal reproducible example
https://github.com/smelnikov/walletconnect-sample/tree/web3modal-tsc-errors
Summary
To Reproduce:
Checkout branch web3modal-tsc-errors of repo:
https://github.com/smelnikov/walletconnect-sample
yarn install
tsc

This produces many errors of same type:
node_modules/@web3modal/core/dist/_types/src/controllers/ClientCtrl.d.ts:5:22 - error TS2307: Cannot find module '@web3modal/ethereum' or its corresponding type declarations.

5     client(): import("@web3modal/ethereum").EthereumClient;
                       ~~~~~~~~~~~~~~~~~~~~~

node_modules/@web3modal/core/dist/_types/src/controllers/OptionsCtrl.d.ts:8:32 - error TS2307: Cannot find module '@wagmi/chains' or its corresponding type declarations.

8     getSelectedChain(): import("@wagmi/chains").Chain | undefined;
                                 ~~~~~~~~~~~~~~~

node_modules/@web3modal/core/dist/_types/src/types/controllerTypes.d.ts:1:44 - error TS2307: Cannot find module '@web3modal/ethereum' or its corresponding type declarations.

1 import type { Chain, EthereumClient } from '@web3modal/ethereum';
                                             ~~~~~~~~~~~~~~~~~~~~~

Found 3 errors in 3 files.

Adding yarn add -D @web3modal/ethereum to dependencies causes more type declaration errors.
Expected behavior
There are no errors.
List of related npm package versions
"@walletconnect/sign-client": "2.5.2",
"@web3modal/standalone": "^2.2.2",
"typescript": "^4.9.3"

You need to add "skipLibCheck": true to your tsconfig

You need to add "skipLibCheck": true to your tsconfig

But why? Aren't library types supposed to be correct?

Code that is being checked is for optional dependencies that are never used / built for what you have set up in your package json. Since you don't have these (nor need) optional deps typecheck fail. In your case it is sufficient to confirm your own app types are correct as well as it also checks all used functions


Fix minor syntax mistake in readme

On line 3 of the flat eslint config example for typescript, a colon is used instead of a semicolon. This PR fixes that.

Thank you very much!


Fix products page structure

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for linneaslustgard processing.

Name
Link

🔨 Latest commit
cf01a207d383fc7ede4d3c9a49bb2b5436215590

🔍 Latest deploy log
https://app.netlify.com/sites/linneaslustgard/deploys/627d3c76fb4502000848c13f


Add GitLab TE --> EE migration guide

We might want to also tell them to migrate the database or (if possible) point the EE instance at GitLab's Mattermost database. I'm not 100% sure how to do that and if the database is even ran after shutting off the internal Mattermost instance, so I'd have to look more into how to do that if we want it


Move main from index.js to BeaconEntryPoint

Description
Follow-up of #12 and needed for auto build in WP Rocket: we don't use index.js anymore as the entry point, but we use BeaconEntryPoint.js. So a few things must be adapted so that npm knows it and install the right files.
Documentation
User documentation
NA
Technical documentation
NA
Type of change
Delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality).
[x] Bug fix (non-breaking change which fixes an issue).
[ ] Enhancement (non-breaking change which improves an existing functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before).

New dependencies
NA
Risks
NA
Checklists
Feature validation

[x] I validated all the Acceptance Criteria. If possible, provide sreenshots or videos.
[x] I triggered all changed lines of code at least once without new errors/warnings/notices.
[ ] I implemented built-in tests to cover the new/changed code.

@mostafa-hisham will this work with inspector code without a problem?

Let's discuss this with @mostafa-hisham tomorrow. Maybe inspector will need an adaptation as well. ; but we need to either have the index.js, either the EntryPoint but we shouldn't keep both approaches I think.

_isGeneratedBefore is now _getGeneratedBefore should i make the new function return false?

Yes, I think so.

Another idea we can create an inspector mode in this repro BeaconManager that do what is needed to run it in wpr-inspector and use BeaconManager in the inspector mode by setting a config, instead of overwriting the class in wpr-inspector

I don't know if that would be better 🤔 Those hacks are quite specific to the inspector, so I am not sure it would make sense to make them in the shared codebase?

we have to export the class that will be used in wpr-inspector
I think the class with the logic now is BeaconManager so we have to export it then import the class in the inspector.

Does that mean adding export default BeaconManager; to BeaconEntryPoint.js, if this file is now used as main on rocket-scripts? I don't know how it would interact on both side (inspector and wp-rocket).
@mostafa-hisham, can you have a look into this? Feel free to commit on those PR to adjust. Thank you


Fix export error

It is fixed on the develop branch, which is where pull requests should be based off.  It's also fixed in a better way there.

Thanks @aure, any idea when it will be merged to master as recorder seems to need that fix to work.


CS-50: implement import for objects.

What needed to be changed to get import to work? I don't see any large changes / implementation -- is it inherently supported in a provider implementation, and the issue was just that there needed to be some bug fixes?

A bit of luck... based on the way read was implemented, import was fairly simple: pulling name from the Id() field, and using a read-passthrough for the Importer. Most of the work was in making the unit tests happy (especially the file object).

I see some unit tests -- have you tested this after creating some actions from an op pack on a cluster manually and then running a terraform import?

Still doing some manual testing.


Darwin: promote Cooking Appliances to Introduced

Continuing the theme of v1.3 promotions.  Added comments about WATTS and affected provisional bits.

@kiel-apple this PR seems quite old and has merge conflicts. Is it supposed to go in?

@andy31415 let me take a stab at bringing it back up to date today, I think it won't be awful.

@bzbarsky-apple thanks for checking the spec, I could have done better there given how long it has been since I opened this

I would recommend removing the provisional annotations for things being added; that would also make it clearer what's still marked as provisional.

I still need to go back and do this.  Coming soon!

need to move all these entries forward to new Future since Future from back when this started has been released

incorporated into #36793


Support for multisession data with multiple T1s

In case the dataset includes multiple sessions and each session includes at least one T1w image the pipeline should default to coregistering EPI to the T1w image from the corresponding session.
Alternatively an unbiased subject specific template (combination of all T1w images from a given subject) should be created and set as the coregistration target.
Currently the pipeline defaults to combining all T1w images (even across sessions) by coregistering all of them to the first T1 found. This is acceptable for combining multiple T1w images from a single session, but results in a bias towards the first T1w and thus is suboptimal in context of longitudinal studies.

I am planning to implement an unbiased template approach.
Roughly this means:

creating an unbiased template from the T1w images
registering from template-T1w to MNI space
within each session: registering from session-EPI to session-T1w, from session-T1w to template-T1, and combining with base-T1w-to-MNI-T1w-transformation

The template could be create with

the longitudinal freesurfer stream (e.g., Tracula uses that for longitudinal registration of DWI data)
and/or
ANTs

@chrisfilo and others: do you have experience with either of those approaches?

This sounds good to me. I only have small amount of experience with
freesurfer longitudinal processing. Since there are more users in volume
based processing I would prefer at least starting with ants. Thanks!
On Jan 11, 2017 5:54 AM, "fliem"<EMAIL_ADDRESS>wrote:

I am planning to implement an unbiased template approach
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3389460/.
Roughly this means:

creating an unbiased template from the T1w images
registering from template-T1w to MNI space
within each session: registering from session-EPI to session-T1w,
from session-T1w to template-T1, and combining with base-T1w-to-MNI-T1w-
transformation

The template could be create with

the longitudinal freesurfer stream (e.g., Tracula
https://surfer.nmr.mgh.harvard.edu/fswiki/Tracula uses that for
longitudinal registration of DWI data)
and/or
ANTs

@chrisfilo https://github.com/chrisfilo and others: do you have
experience with either of those approaches?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/310#issuecomment-271873924,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp98PrGhie-EYqY31VbZJ-EfAUI5Iks5rRN8SgaJpZM4Lf8Ex
.

I’m not 100 percent sure, but I think Tracula only uses volumes as templates and basing the fmri workflow on the dmri workflow probably would be straightforward.
As far as ATNs goes, it seems there is

buildtemplateparallel.sh which has a (legacy) nipype interface and
more recently: antsMultivariateTemplateConstruction2.sh which has no nipype interface

Also there are two nipype workflows

antsRegistrationBuildTemplate and
ANTSBuildTemplate

@chrisfilo: do you now an ANTs expert from the nipype community who could give recommendations regarding the different options? Thanks

Yup - @hjmjohnson is the man!
On Jan 11, 2017 8:03 AM, "fliem"<EMAIL_ADDRESS>wrote:

I’m not 100 percent sure, but I think Tracula only uses volumes as
templates and basing the fmri workflow on the dmri workflow probably would
be straightforward.
As far as ATNs goes, it seems there is

buildtemplateparallel.sh
https://github.com/stnava/ANTs/blob/master/Scripts/buildtemplateparallel.sh
which has a (legacy) nipype interface
http://nipy.org/nipype/interfaces/generated/nipype.interfaces.ants.legacy.html#buildtemplateparallel
and
more recently: antsMultivariateTemplateConstruction2.sh
https://github.com/stnava/ANTs/blob/master/Scripts/antsMultivariateTemplateConstruction2.sh
which has no nipype interface

Also there are two nipype workflows

antsRegistrationBuildTemplate
http://nipype.readthedocs.io/en/latest/interfaces/generated/nipype.workflows.smri.ants.antsRegistrationBuildTemplate.html
and
ANTSBuildTemplate
http://nipype.readthedocs.io/en/latest/interfaces/generated/nipype.workflows.smri.ants.ANTSBuildTemplate.html

@chrisfilo https://github.com/chrisfilo: do you now an ANTs expert from
the nipype community who could give recommendations regarding the different
options? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/310#issuecomment-271908897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp_aVFbodjYlaIEHClhLRn31x4bHZks5rRP02gaJpZM4Lf8Ex
.

Great.
Hi @hjmjohnson. Do you have any recommendations regarding which ANTs tool to use for unbiased template creation?
Thanks

Hi @jfrenchjr. Do you have any recommendations regarding using AFNI for building intra-subject templates (similarly to study-specific templates in #330)? Thanks.

Hello @fliem. Depending on your needs, the tools mentioned in #330 could work. 3dWarpDrive may also be of use.

Closed here https://github.com/poldracklab/fmriprep/pull/481#issuecomment-297136612

#481 did not close this. We don't use an unbiased template (see https://github.com/poldracklab/fmriprep/pull/481#issuecomment-297141567), yet.

Oh, sorry!


Can I stop when failed

I have a task running every 5 minutes to send scheduled emails.
I found that it will fork a list of process when I deployed via Capistrano as the app is overloading the server.
Can I either stop the whenever task when it failed or pause it during capistrano deploy?
Thanks,

You could run whenever:clear_crontab early in your deploy to prevent any new jobs from running during your deploy, but beyond that it would be a matter of finding running processes and terminating them using some kind of unix script.
Using nice might help you keep your cron jobs from consuming too many resources.


ab => apr_socket_recv: Connection reset by peer (104)

Hi
I have just finished a webserver + API REST drogon program where I set:
drogon::app().setThreadNum(0);
Then I decided to test its HTTP response time using ab tool but first I evaluated the answer time of the drogon sample called benchmark issuinng 100 request where 10 may be in paralel: $ab -n 100  -c 10 http://...
ab tool worked well with benchmark.
Then I used ab to send just one request to my drogon program and worked well. When I use ab tool for 2 or more requests I always see this error from ab tool:
apr_socket_recv: Connection reset by peer (104)
Any ideas about what could be firering this error?
Thank you
Av

This happen when sending data on connections closed by peer, usually not real error (so it's a DEBUG level log).

Right, but ab tool can not execute until the end and does not show statistic data. Could this mean that in the future when multiples clients will be  connecting to the program the same will happen and no answer will be returned ?


Lumber resource trading doesn't work in some circumstance

https://user-images.githubusercontent.com/8995690/215001853-c3633461-6ddc-4844-8fa1-4be7f34e4025.mp4

I cannot see the video

Looks like the upload failed. I'll just link the Discord post when I'm at my computer.

https://discord.com/channels/553888327103807491/1067842620358938654

Tried this locally and it seems to work. Presumably related to your recent forces fix @SebastianTanoni - not sure what it was.

As per https://discord.com/channels/553888327103807491/1073737277563469825 this seems to still be an issue.
I think we should consider just disable resource trading again. Not sure if the feature is really worth this level of effort.

I'll solve this with #2095


Ledger type

Fixes #231
The "New Ledger Wallet" view now looks like this so it's easier to identify:

Looks better

Looks better


Include header in Send Transactional email (templates)

By now, is it possible to add a mail header when we send a Transactional email (without templates)  so it's really useful to add tags and other custom fields.
$mailin->send_email($to,$subject,$from,$html,$text,$cc,$bcc,$replyto,$attachment,$headers)
I think it would be nice to add this option when we send Transactional email (templates)

Hello,
Thank you for contacting us.
The option to send custom headers  is available now in Transactional email (templates).
Please refer our Apidoc here https://apidocs.sendinblue.com/template/#1
Regards,
SendinBlue Team


[question] mocha and path mappings

I'm trying to migrate our mono-repo from rules_nodejs to rules_js/rules_ts and have made good progress. However, running tests with mocha doesn't work and I believe they are executed in a different manner than how it is done in rules_nodejs.
We're using paths in tsconfig to do cross-module imports which works when building. But when running the tests they fail and claim the files aren't found. Looking at the output-directory I can see that all needed files are transpiled and part of the runfiles-set. So I'm thinking it must be something with how the tests are executed.
In our WORKSPACE file I've added the following for the bins option in npm_translate_lock:
        # derived from "bin" attribute in node_modules/mocha/package.json
        "mocha": {
            "mocha": "./bin/mocha.js",
        },

And looking at your macro example in rules_js I've created a mocha_test macro looking like this:
# Inspired by https://github.com/aspect-build/rules_js/blob/main/examples/macro/mocha.bzl
load("@npm//:mocha/package_json.bzl", "bin")

def mocha_test(name, srcs, args = [], env = {}, **kwargs):
    bin.mocha_test(
        name = name,
        args = args,
        data = srcs,
        env = env,
        **kwargs
    )

Since the tests are also written in typescript we create a ts_project where srcs contain the test files and then depend on the needed modules in deps. This works perfectly fine with rules_nodejs 5.7.0 so I'm wondering if I'm missing something while migrating. I see that the output looks different compared to rules_nodejs so I'm guessing I might need some kind of adaption to how rules_js expects things.
In rules_nodejs I'm using js_library to create virtual packages that map against the paths configured in tsconfig.json where I set package_name to match the expected import. I don't see a similar option for js_library in rules_js so I guess I might need npm_link_package or similar but I've yet figured out how to make it work.
Running with rules_js 1.6.5, rules_ts 1.0.0-rc5, typescript 4.8.4, mocha 10.1.0.

https://github.com/aspect-build/rules_js/blob/main/examples/npm_package/packages/pkg_a/BUILD.bazel this might help you.
rules_nodejs and rules_js has different ways of linking 1p packages.
https://github.com/aspect-build/bazel-examples/tree/main/pnpm-workspaces is an example demonstrating this.

@fredrik-w does this help you?

 And I think I finally cracked it.
I was trying to the define the npm_link_package in the BUILD-file of the package itself, rather in the root of the project.
Thanks to your links and the comments in those BUILD-files I realized I was doing it wrong.
Linking it from the root of the package and then explicitly set visibility to //:__subpackages__  suddenly made things start moving. However, it appears I need to depend on the name of the link rather than the module, which I can buy as it has the package_name from npm_package and thus matches the path-alias from tsconfig.json.

However, it appears I need to depend on the name of the link rather than the module

1p packages work differently than the rules_nodejs. I see why you didn't expect that.
I take this as the solution and close the issue.

@thesayyn Yes, it was solved for me, thanks for the links :slightly_smiling_face:


cannot move out of captured outer variable...

This is not working for me:
#![feature(plugin)]
#![plugin(maud_macros)]

extern crate maud;

use std::io;

fn main() {
    let template1 = html! {
        span {
            "This is the inner content"
        }
    };
    let html1 = template1.to_string();

    let template2 = html! {
        html {
            div {
                $$html1
            }
        }
    };

    template2.render(&mut io::stdout()).unwrap();
}

I get
<quote expansion>:2:64: 2:80 error: cannot move out of captured outer variable in an `Fn` closure
<quote expansion>:2                                                                name_71,ctxt_9)
                                                                                ^~~~~~~~~~~~~~~~
src/main.rs:1:1: 25:1 note: in expansion of html!
src/main.rs:16:21: 22:6 note: expansion site
error: aborting due to previous error

Is there some other way to have templates include other templates?

Good catch! It appears that splicing ($) moves the value, when it should borrow it instead.
That's on oversight on my part; I've fixed it in version 0.4.2.


feat(bpdm-cert): initial commit for updated folder structure as per TRG

Description
Add folder structure and simple api for certificate on following eclipse TRG.
Fixes #1
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

Created an IP-Check issue at EF: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11654

Thank you, I can see created IP-Check issue: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11654 is approved and closed.


Detect_json for selected fields

I am selecting two database columns from my mssql database. Both contain valid JSON, but i need one JSON to stay as a string in ElasticSearch.
Is there any possibility to do just that? Or would that be an ElasticSearch issue?

Currently, there is only a switch that can turn JSON detection on or off, but not per field.


The redis cache plug-in cannot access the redis server with password authentication

system introduction
Answer version: 2.2.5
Answer plug-in: the latest version of the plug-in repository
Running method: Build Docker image by yourself, with plug-in
Redis plug-in display version: 0.0.1
Problem Description
Using the latest Redis plug-in, when the Redis address is filled in with password authentication, redis cannot be connected correctly. The Redis address is: redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379,
Test 1
Enable the Redis plug-in, fill in the address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379, log:
2024-02-19T02:40:34.677 app[9185d61a426038] nrt [info] 2024-02-19 10:40:34.675 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:34.831 app[9185d61a426038] nrt [info] 2024-02-19 10:40:34.830 ERROR question/question_repo.go:341 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:34.831 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3

2024-02-19T02:40:49.513 app[9185d61a426038] nrt [info] 2024-02-19 10:40:49.512 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:50.288 app[9185d61a426038] nrt [info] 2024-02-19 10:40:50.288 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.084 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.084 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.130 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.129 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.290 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.289 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.492 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.492 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.656 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.656 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.816 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.816 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:51.998 app[9185d61a426038] nrt [info] 2024-02-19 10:40:51.997 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:52.180 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.179 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:52.305 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.305 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:52.506 app[9185d61a426038] nrt [info] 2024-02-19 10:40:52.506 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:53.277 app[9185d61a426038] nrt [info] 2024-02-19 10:40:53.277 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:54.025 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.024 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:54.051 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.050 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:54.090 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.089 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:54.235 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.235 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:54.967 app[9185d61a426038] nrt [info] 2024-02-19 10:40:54.967 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:58.436 app[9185d61a426038] nrt [info] 2024-02-19 10:40:58.435 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:58.565 app[9185d61a426038] nrt [info] 2024-02-19 10:40:58.564 ERROR action/captcha_strategy.go:36 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:59.318 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.317 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:59.391 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.390 ERROR action/captcha_strategy.go:36 dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] 2024-02-19 10:40:59.472 ERROR handler/handler.go:53 code: 500, reason: base.database_error, message: , error: dial tcp: address redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/repo/captcha/captcha.go:94 github.com/apache/incubator-answer/internal/repo/captcha.(*captchaRepo).SetCaptcha

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:175 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).GenerateCaptcha

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:87 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).ActionRecord

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/controller/user_controller.go:502 github.com/apache/incubator-answer/internal/controller.(*UserController).ActionRecord

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/base/middleware/auth.go:64 github.com/apache/incubator-answer/internal/router.(*AnswerAPIRouter).RegisterMustUnAuthAnswerAPIRouter.(*AuthUserMiddleware).Auth.func1

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:620 github.com/gin-gonic/gin.(*Engine).handleHTTPRequest

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:576 github.com/gin-gonic/gin.(*Engine).ServeHTTP

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2938 net/http.serverHandler.ServeHTTP

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2009 net/http.(*conn).serve

2024-02-19T02:40:59.473 app[9185d61a426038] nrt [info] /usr/lib/go/src/runtime/asm_amd64.s:1650 runtime.goexit

At the same time, when you visit the project again and log in, you will be prompted to enter a verification code, but the verification code has not been set yet.
Test 2
Test the connection default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379, reset the Answer, and fill in the Redis connection default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379 again. The log is as follows:
2024-02-19T02:49:48.570 app[9185d61a426038] nrt [info] start cron

2024-02-19T02:49:48.731 app[9185d61a426038] nrt [info] 2024-02-19 10:49:48.730 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:49:48.887 app[9185d61a426038] nrt [info] 2024-02-19 10:49:48.886 ERROR question/question_repo.go:341 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:49:48.888 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3

2024-02-19T02:50:11.946 app[9185d61a426038] nrt [info] 2024-02-19 10:50:11.944 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.670 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.669 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.678 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.677 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.700 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.699 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.912 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.912 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.928 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.928 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:12.943 app[9185d61a426038] nrt [info] 2024-02-19 10:50:12.942 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:13.134 app[9185d61a426038] nrt [info] 2024-02-19 10:50:13.133 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:13.251 app[9185d61a426038] nrt [info] 2024-02-19 10:50:13.250 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.047 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.046 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.113 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.112 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.138 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.137 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.296 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.295 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.428 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.428 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.718 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.717 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:14.863 app[9185d61a426038] nrt [info] 2024-02-19 10:50:14.863 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:15.169 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.168 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:15.410 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.409 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:15.603 app[9185d61a426038] nrt [info] 2024-02-19 10:50:15.602 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:16.375 app[9185d61a426038] nrt [info] 2024-02-19 10:50:16.374 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:17.158 app[9185d61a426038] nrt [info] 2024-02-19 10:50:17.158 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:17.330 app[9185d61a426038] nrt [info] 2024-02-19 10:50:17.330 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:23.782 app[9185d61a426038] nrt [info] 2024-02-19 10:50:23.781 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:23.897 app[9185d61a426038] nrt [info] 2024-02-19 10:50:23.895 ERROR action/captcha_strategy.go:36 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:24.598 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.597 ERROR site_info/siteinfo_repo.go:101 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:24.674 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.673 ERROR action/captcha_strategy.go:36 dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] 2024-02-19 10:50:24.819 ERROR handler/handler.go:53 code: 500, reason: base.database_error, message: , error: dial tcp: address default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/repo/captcha/captcha.go:94 github.com/apache/incubator-answer/internal/repo/captcha.(*captchaRepo).SetCaptcha

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:175 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).GenerateCaptcha

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/service/action/captcha_service.go:87 github.com/apache/incubator-answer/internal/service/action.(*CaptchaService).ActionRecord

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/controller/user_controller.go:502 github.com/apache/incubator-answer/internal/controller.(*UserController).ActionRecord

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/apache/incubator-answer/internal/base/middleware/auth.go:64 github.com/apache/incubator-answer/internal/router.(*AnswerAPIRouter).RegisterMustUnAuthAnswerAPIRouter.(*AuthUserMiddleware).Auth.func1

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/context.go:174 github.com/gin-gonic/gin.(*Context).Next

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:620 github.com/gin-gonic/gin.(*Engine).handleHTTPRequest

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /answer_build1258453270/vendor/github.com/gin-gonic/gin/gin.go:576 github.com/gin-gonic/gin.(*Engine).ServeHTTP

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2938 net/http.serverHandler.ServeHTTP

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/net/http/server.go:2009 net/http.(*conn).serve

2024-02-19T02:50:24.822 app[9185d61a426038] nrt [info] /usr/lib/go/src/runtime/asm_amd64.s:1650 runtime.goexit

When logging in, the same problem occurs as in test 1.
Test 3
Test the Redis connection ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379, the log is as follows:
 nrt [info] 2024-02-19 10:56:52.641 ERROR site_info/siteinfo_repo.go:101 dial tcp: lookup<EMAIL_ADDRESS>no such host

2024-02-19T02:56:52.956 app[9185d61a426038] nrt [info] 2024-02-19 10:56:52.950 ERROR question/question_repo.go:341 dial tcp: lookup<EMAIL_ADDRESS>no such host

2024-02-19T02:56:52.963 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3

Test connection redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379, log:
[info] 2024-02-19 11:25:33.298 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:33.456 app[9185d61a426038] nrt [info] 2024-02-19 11:25:33.455 ERROR question/question_repo.go:341 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:33.458 app[9185d61a426038] nrt [info] answer Version: 1.2.5 Revision: 5132cb3

2024-02-19T03:25:34.563 app[9185d61a426038] nrt [info] 2024-02-19 11:25:34.562 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:36.709 app[9185d61a426038] nrt [info] 2024-02-19 11:25:36.708 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:36.751 app[9185d61a426038] nrt [info] 2024-02-19 11:25:36.751 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:39.425 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.424 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:39.562 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.561 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:39.764 app[9185d61a426038] nrt [info] 2024-02-19 11:25:39.764 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

2024-02-19T03:25:40.011 app[9185d61a426038] nrt [info] 2024-02-19 11:25:40.010 ERROR site_info/siteinfo_repo.go:101 dial tcp: address redis://ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379: too many colons in address

Build Dockerfile
FROM apache/answer as answer-builder

RUN apk --no-cache add \
    build-base git bash nodejs npm go && \
    npm install -g pnpm

RUN answer build \
    --with github.com/apache/incubator-answer-plugins/search-meilisearch \
    --with github.com/apache/incubator-answer-plugins/cache-redis \
    --with github.com/apache/incubator-answer-plugins/storage-s3 \
    --output /usr/bin/new_answer

FROM apache/answer

COPY --from=answer-builder /usr/bin/new_answer /usr/bin/answer
RUN chmod 755 /entrypoint.sh

VOLUME /data
EXPOSE 80
ENTRYPOINT ["/entrypoint.sh"]

@LinkinStars My Redis is provided by upstash.com. The link provided is in the form of redis://default:ce5a7b1d80e44320a7877ac2aafae5cd@123.upstash.io:6379. The specific explanation is: Protocol name://username:user password@ Host domain name or IP:port, only use 123.upstash.io:6379, unable to provide access password to upstash.com.

@lincolnzhou Just a small follow-up, do you want to continue contributing features about configuring redis usernames? Because you did the feature of the password before. Of course, if there is no time, I can assign it to someone else. Just asking out of courtesy.

Okay, I'll try to fix it

#71 Please review this pr

@lincolnzhou @LinkinStars I have tested the redis plug-in version 1.2.6. After entering the address, username, and password, redis is enabled normally and this problem is closed.


BiggerLobby not initializing? NullReferenceException

LogOutput.log

Friend had the same issue with the same error, unknown if such is caused by the Log Object from LC_API being used is loaded at that time.

We can't use biggerlobby, it's not working, we can't use escape to back to the menu, and we can't launch the ship...

Please help us, we want to play with our friends :)

If you're installing it manually (I don't recommend it, you should use a modmanager), make sure you install every file, not just the dll. There's a required AssetBundle
I should probably add null checks/a more specific warning though


Page Layout Tab Structure

Summary
Adds page layouts tab structure hidden behind a feature flag that are based on templates.

Adds template loading function to useAPI
This includes pills, but not the search field
Page layouts (template pages) are rendered as empty boxes, but are hooked up with react-virtual
Selecting a pill filters the page set

ticket
Relevant Technical Choices

To-do

User-facing changes
Hidden behind a feature flag for "Page layouts tab"

Testing Instructions

To view tab, enable "Page layouts tab" in Experiments

Fixes #5079

@BrittanyIRL The small browser issue is going to show itself on the other tabs too with manually defined widths for items in the tabs. I think we should punt on solving the small browser issue because of that.


[Feature Request]: Dark Mode/Light Mode not working in Contact Us Page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

Make these changes in #182


make it run on root filesystem

The whole logic about not running on NVMe is buggy. It appears to assume the script is in /volume*/ which isn't always true.
We need to be able to run this script in /root or another non-NVMe volume without errors.

I'm surprised nobody else has mentioned this issue as it's existed since January, in v3.4.77


Stage 2: Search and filter

In the call today we discussed the registry-level searching, such as:
GET /v2/_oci/references?q_manifests__mediatype__contains=chocolate

The general consensus was that this is out of scope for the current iteration.
Once we have figured out the basics of how to store and relate things, this group (or a new WG) should address the concept of cross-repo searching and filtering.

closing as out of scope for now


kicad: pin to python 3.11

Description of changes
Similar to #325682 , this PR pins the Python version used by kicad to Python 3.11.
KiCAD depends on wxWidgets, which still uses distutils (removed in Python 3.12), see also https://github.com/wxWidgets/Phoenix/issues/2104 .
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@jfly  Thank you for your suggestions, I have implemented them.

I also prefer this commit. I'll go ahead and close mine. Great work!

Is there any fix for the time being before this gets merged?

You can use kicad from nixos-24.05. For example this way. Or just run nix run nixpkgs/nixos-24.05#kicad-small (if you have flakes enabled).

@wentasah sadly I dont have flakes setup, thank your for your help though!

@wentasah sadly I dont have flakes setup, thank your for your help though!

Non-Flakes equivalent would be nix-build -A kicad-small channel:nixos-24.05 && ./result/bin/kicad. (Or nix-env -iA kicad-small -f channel:nixos-24.05 for installing to user profile.)

I would have merged this immediately after a friend made me aware of the kicad build issue but since it doesn't eval, I first pushed a fix for that.

@ofborg eval


Upload low res models

Low-resolution models for cardiac, abdominal organs and vertebrae segmentation

Superb! Please also test these: https://github.com/lassoan/SlicerMONAIAuto3DSeg/pull/19


Refund when memo is incorrect

closing in favor of https://github.com/threefoldfoundation/tft/pull/106


Suggestion: auto suggest label keys

Hi
When creating labels or placeholders it would be super cool if the Builder could suggest a label key
e.g when create a label for a field in a form something like this:
myplugin.mymodel.form.label.
and for the placeholser
myplugin.mymodel.form.placeholder.
and for lists
myplugin.mymodel.list.label.

Added this to the internal tracker for the next iteration of builder.
Thanks!


Assertion Failure in line.dart When Editing Text with Block-Level Attributes in Debug Mode

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
10.4.5
Steps to reproduce

Create a text using the Flutter Quill editor.
Apply a block-level attribute (e.g., list, alignment).
Delete a character in the text.
Continue typing.
Observe that the new text does not appear until the editor loses focus.

Expected results
Text should appear immediately when typed, without requiring the editor to lose focus. No assertion failures should occur.
Actual results
In debug mode, the text does not appear until the editor loses focus. An assertion failure occurs in line.dart on line 147.
Code sample
No response
Additional Context
I've encountered an assertion failure when using the Flutter Quill editor in debug mode. This issue occurs specifically when I apply block-level attributes (such as lists or alignment) to text, delete a character, and then attempt to type again. The issue manifests as follows:
Behavior in Debug Mode:
After deleting a character, any further typing does not immediately appear in the editor.
The typed text only becomes visible after the editor loses focus.
The following assertion is thrown:
Behavior in Release Mode:
The issue does not occur in release mode. The editor behaves as expected, with no assertion failure or delayed text rendering.
The issue might be related to https://github.com/singerdmx/flutter-quill/issues/1622
Logs
Exception caught by services library
The following assertion was thrown during method call TextInputClient.updateEditingState:
'package:flutter_quill/src/document/nodes/line.dart': Failed assertion: line 147 pos 14: 'style.values.every((attr) =>
attr.scope == AttributeScope.inline || attr.scope == AttributeScope.ignore)': is not true.

The assertion is bringing our attention to a fault in the logic.
Simply removing the assert, or using release mode, is not the correct solution as it corrupts the quill deltas and is likely to cause other problems at a later time.
The fault is in the caller, but I have not found the root cause yet.


Missing AOERadius from ability base properties

AOERadius is missing from ability base properties

I spoke too soon, looks like my previous testing was faulty and AOERadius doesn't have an effect in current dota. Commenting the AOERadius in KV and implementing GetAOERadius in Lua does correctly show the AOE radius.


iOS 9/10 Compatibility

Hey Wisor,
Awesome start on OBD2Connect. Are you able to get this working on iOS9/10 devices? My own OBD project no longer works. Trying your demo project, it request times out as well. It connects fine, but requests time out.
I previous had an iPhone 5 running iOS 8 that had ELM transmissions working properly, but I no longer have said device.

Hi Kalvin126,
I tried it on iPhone 7 iOS 10 and it works. I have two Wi-Fi adapters (ELM327 v1.5 and STN1170) and it is compatible with both of them. You should try to increase timeout interval, because by default it sets to 0.1 sec:
let connection = OBDConnection(requestTimeout: 2) // Timeout in seconds

I tried 1 second, but it timed out as well. I'll increasing it further. Would you be open to contributions?

Yeap, you are welcome to contribute.
Try to check your adapter with any free OBD app from AppStore (for example  https://itunes.apple.com/app/obd-car-doctor/id652142348). Is it work?
Also, It would be great to check is there any data received from adapter in one of the methods of OBDConnection class:
private func handleReceived(data: Data)

Alright awesome. I actually just confirmed my obd wifi adapter is dead. Time to get another one :p

Might I ask what specific ELM327 adapter you are using? I have a Veepeak mini ELM327 v1.5 adapter. I tried it with obd car doctor and it work just fine actually. I guess I need to further debug.

I have the cheapest Noname adapter you can buy on aliexpress, but it actually works fine for me. I should notice, that my framework has responsibility to transfer data between adapter and a phone.
So, inside demo project I sent only ATZ command to reset the adapter to default settings. Usually, ATSP0 command follows next.
And as I mentioned earlier func handleReceived(data: Data) would be the best place to start to debug the adapter response. Good luck!

Ok so, I put a breakpoint in handleReceived(data:. Ocaissionally I would get a response of ?\r\r> when sending ATZ command. The response seems like garbage though...

Sorry for a late response. All commands must follow with a close line character \r and the response with ? character means that your adapter doesn't understand provided command.

No problems. I am just trying to get to the bottom of this. Apps like OBD Car Doctor from the app store work. Its able to send AT Z then the AT SP 0 commands.

It's incorrect to compare this framework to app from app store. OBD2Connect just a "data-tube". It connects your API above it and OBD2 adapter only, all commands syntax and response handling are up to you.

Right, I understand that. I am just saying that they are able to send the same ATZ command and get a valid response back. Will be closing this issue indefinately.


Update PostgresTypeTransformer.php

I was confused by these empty methods, so I cleaned it up for you.

@walkerranger sorry, my coworker is sometimes mean and closes things without saying anything. You don't need to remove anything, @aejnsn is working on it I think


Debug New Window not themed

Problem/Motivation
When clicking the "Open in new window" for the debug tab (http://[ip]:1880/debug/view/view.html) it shows as the default off-white colour

Theme version: latest (just installed it)
Node-RED version: 1.3.3
Platform/OS: Ubuntu 20.10 Server (Headless) running in Docker
Browser: Chrome

Steps to reproduce
Install theme, switch to debug tab in right hand panel, click new window button (very bottom-right)
Proposed changes
It should be themed to match main window
Thank you.

@My-Random-Thoughts thanks for the heads up. The issue is now fixed and should be available in the next Node-RED version.


Add a 'gui' parameter to the ROS2 version

For consistency with ROS1 and for RoboMaker integration (see https://github.com/aws-robotics/aws-robomaker-sample-application-helloworld/blob/ros2/simulation_ws/src/hello_world_simulation/launch/empty_world.launch)

https://github.com/aws-robotics/aws-robomaker-sample-application-helloworld/pull/33


Remove unused SUPER_L/R constants.

Missed them in https://github.com/godotengine/godot/pull/70052, everything use META instead.

Thanks!


Investigate cross-database support in views and functions

Cross-DB queries are currently supported in stored procedures, but not in views or functions, see details in this comment. This needs to be investigated and eventually brought to upstream Babelfish.

@staticlibs , any update on this? we are using many Views with cross DB join's, solving this issue will help us.

@psrinivasa2 , going to look at this after SSPI. I don't expect to fix this easily, only to re-raise it in upstream Babelfish. I assume there are some technical reasons why this logic was implemented quite a while ago for procedures, but not for views or functions.

@staticlibs  as a workaround we have executed below query, post that it enables cross DB join in Views.
GRANT SELECT ON ALL TABLES IN SCHEMA department_dbo TO PUBLIC;
ALTER DEFAULT PRIVILEGES IN SCHEMA department_dbo GRANT SELECT ON TABLES TO PUBLIC;
what your view on this workaround?

@psrinivasa2 , m, I did not expect this to work. It disables all the permissions checks for that schema for all users. Besides that I cannot immediately see other downsides. I copied this to issue #5 in towel repo, that seems to be better suited for discussion about it.

this can be closed @staticlibs , since our workaround works fine


[Twig] attributes.add function doesn't exist

This function present on documentation is not implemented

Hi,
Version 2.7 has not been released yet, see https://github.com/symfony/ux/releases

Thanks for your answer.
Do you have an ETA for this version?

Friendly ping @weaverryan

@alexgaill Can this issue be closed?


inconsistent representation of network interfaces

The representation of network interfaces is not consistent.
Specifically, while its name is indeed the name of the network interface, the id refereed to as ResourceUID  is taken from the network interface's primary_ip.
This is visible in the json format.
E.g.:
npGurard output include:
                "dst": {
                    "ResourceName": "yarn-canary-guileless-deftly",
                    "ResourceUID": "id:21",
                    "ResourceType": "NetworkInterface",
                    "Zone": "us-south-1"
                },

but the source is the following:
                    "href": "href:18",
                    "id": "id:19",
                    "name": "yarn-canary-guileless-deftly",
                    "port_speed": 3000,
                    "primary_ip": {
                        "address": "<IP_ADDRESS>",
                        "href": "href:20",
                        "id": "id:21",
                        "name": "precision-grudge-daylight-married",
                        "resource_type": "subnet_reserved_ip"
                    },

not sure why this is opened twice #237


Ubuntu 14.04 w/ NVIDIA CUDA 8.0.61 unable to build

Followed the following instructions:

sudo dpkg -i cuda-repo-ubuntu1404_7.5-18_amd64.deb

sudo apt-get -y install software-properties-common
sudo add-apt-repository -y ppa:ethereum/ethereum
sudo apt-get update
sudo apt-get install git cmake libcryptopp-dev libleveldb-dev libjsoncpp-dev libjson-rpc-cpp-dev libboost-all-dev libgmp-dev libreadline-dev libcurl4-gnutls-dev ocl-icd-libopencl1 opencl-headers mesa-common-dev libmicrohttpd-dev build-essential cuda -y
git clone https://github.com/Genoil/cpp-ethereum/
cd cpp-ethereum/
mkdir build
cd build
cmake -DBUNDLE=cudaminer ..
make -j8

Result:
Error limit reached.
100 errors detected in the compilation of "/tmp/tmpxft_000009ff_00000000-17_ethash_cuda_miner_kernel.compute_61.cpp1.ii".
Compilation terminated.
CMake Error at ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o.cmake:264 (message):
  Error generating file
  /home/ubuntu/cpp-ethereum/build/libethash-cuda/CMakeFiles/ethash-cuda.dir//./ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o

make[2]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o] Error 1
make[1]: *** [libethash-cuda/CMakeFiles/ethash-cuda.dir/all] Error 2
make: *** [all] Error 2

Output of NVIDIA Version:
ubuntu@TestRig:~/cpp-ethereum/build$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Tue_Jan_10_13:22:03_CST_2017
Cuda compilation tools, release 8.0, V8.0.61

Installed by run command and NVIDIA driver. I'm able to run CUDA samples without issue.

Building the OpenCL version cmake -DBUNDLE=miner .. works without issue

So just curious, you were able to compile by changing cudaminer to miner? Am I reading your notes correctly?

Yes, that is correct. However, I was not able to use the CUDA miner, which would be much more performant.

On Jun 13, 2017, at 5:52 PM, s1eight<EMAIL_ADDRESS>wrote:
So just curious, you were able to compile by changing cudaminer to miner? Am I reading your notes correctly?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Genoil/cpp-ethereum/issues/202#issuecomment-308271264, or mute the thread https://github.com/notifications/unsubscribe-auth/AAM07Pt7B7D_icd0S6Ip9VMiOG-djNtBks5sDxKUgaJpZM4N3mXY.

Dumb question, but are you sure you downloaded the correct CUDA software? The notes on the front page of this github, are outdated they still reference CUDA7.

Yes, I’m at the latest version of the CUDA software. The driver and kernel match, and I’m able to run sample code without issue.

On Jun 13, 2017, at 5:56 PM, s1eight<EMAIL_ADDRESS>wrote:
Dumb question, but are you sure you downloaded the correct CUDA software? The notes on the front page of this github, are outdated they still reference CUDA7.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Genoil/cpp-ethereum/issues/202#issuecomment-308271917, or mute the thread https://github.com/notifications/unsubscribe-auth/AAM07MHc2AokBmes4rvpLOOvBhjZS3pUks5sDxOIgaJpZM4N3mXY.

arggg
~/cpp-ethereum/build$ cmake -DBUNDLE=miner ..
CMake Error: The source "/home/matthew/cpp-ethereum/CMakeLists.txt" does not match the source "/home/matthew/cpp-ethereum/build/CMakeLists.txt" used to generate cache.  Re-run cmake with a different source directory.

Had same problem. Seems to be that problem is in libethash-cuda/CMakeLists.txt. More detailed - here https://github.com/Genoil/cpp-ethereum/commit/0b1da6b545198078d1bbe9278c3099add785237d
You need to change
set(CUDA_NVCC_FLAGS ${CUDA_NVCC_FLAGS};--disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo)

for
set(CUDA_NVCC_FLAGS ${CUDA_NVCC_FLAGS};--std=c++11;--disable-warnings;--ptxas-options=-v;-use_fast_math;-lineinfo)


Update extension dependencies

Overview

Update dependencies from @polkadot
Update jest (with resolution method)
Update ledger lib

Re-test:

[x] All features
[ ] Ledger support
[ ] @saltict re-check security issue

Version test: http://<IP_ADDRESS>:8900/s/TMQ4sQorsTkrmsr
All feature are normal


Sliding window across spatial neighbourhood

Description
Implementation of sliding window (inspired by Kasumi) over a spatial neighbourhood or view.
Input:

window size
overlap

Output:

assignment of cells to sliding window

Hi Francesca,
If all you need is a labeling function and not anything fancier I think I can help. I'm a bioinformatics analyst at the KF Cancer Center in Boston - I've done this before in R for a lung cancer analysis. Wrote up new code that does what you ask and takes in an AnnData object. I haven't tested it that thoroughly so keep that in mind. Two pictures below after running apply_grid_to_cells(adata, window_size=2500, overlap =500) on example data from a NanoString CosMx dataset. Since each cell can be in multiple windows when overlap>0, we need multiple columns to keep track of these assignments (up to 25 per cell for these parameters). The output is 25 new columns in adata with unique labels for the windows. You can use pd.melt to convert adata.obs to a long-form dataframe and treat each window's cells as unique, so that later collapsing into window-per-row data is easy. Here's the function:
import math
import anndata as ad

''' Label cells into "windows" for a coarser spatial analysis
    If overlap ==0, the windows for a grid and each cell is assigned to one unique window.
    Otherwise, each cell will be assigned to multiple windows. Multiple columns are needed as a result.
    Change  coord_columns to match columns names for XY coordinates in adata.obs '''
def apply_grid_to_cells(adata, window_size = 2500, overlap = 0, coord_columns = ('globalX', 'globalY')):
    x,y = coord_columns
    # No overlap
    if overlap ==0:
        xgrid, ygrid = xgrid, ygrid = (adata.obs[x] - min(adata.obs[x]))// window_size, (adata.obs[y]- min(adata.obs[y])) // window_size
        xrows = xgrid.max()
        adata.obs['Window grid'] = ((ygrid*xrows)+xgrid).astype(int).astype('category')
    else:
        grid_len = math.ceil(window_size / overlap)
        num_grid_systems = grid_len**2
        for i in range(num_grid_systems):
            grid_col_name = f'Sliding window grid {i+1}'
            row, col = (i // grid_len) , (i % grid_len)
            x_grid_start = min(adata.obs[x]) + (overlap * col)
            y_grid_start = min(adata.obs[y]) + (overlap * row)
            xgrid, ygrid = (adata.obs[x] - x_grid_start)// window_size, (adata.obs[y]- y_grid_start) // window_size
            xrows = xgrid.max()
            adata.obs[grid_col_name] = (f'{1+i}_' + ((ygrid*xrows)+xgrid).astype(int).astype(str)).astype('category')
    # adata modified in place

@richierip thanks for starting this, I will check it out!
To continue the brain storm, some additional implementation features that need to be considered:

z-coordinate
storing the sliding windows in .obs will explode the storage space. Alternatively storing in .obsm
Move implementation to SpatialData instead

Getter functions:

statistics about min, max, avg number of nodes per window


Research Mode Update for HL2

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

File
Status
Preview URL
Details

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 825588d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/research-mode.md
:warning:Warning
View
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md

Line 57, Column 22: [Warning-file-not-found] Invalid file link: 'hololens2-hardware.md'.
Line 122, Column 9: [Warning-bookmark-not-found] Cannot find bookmark '#Main-Sensor-Loop' in 'research-mode.md', did you mean '#main-sensor-loop'?
Line 131, Column 5: [Warning-bookmark-not-found] Cannot find bookmark '#Sensors' in 'research-mode.md', did you mean '#sensors'?
Line 131, Column 29: [Warning-bookmark-not-found] Cannot find bookmark '#Sensor-coordinate-frames' in 'research-mode.md', did you mean '#sensor-coordinate-frames'?
Line 138, Column 5: [Warning-bookmark-not-found] Cannot find bookmark '#Sensor-frames' in 'research-mode.md', did you mean '#sensor-frames'?
Line 300, Column 18: [Warning-bookmark-not-found] Cannot find bookmark '#Imu-sensors' in 'research-mode.md', did you mean '#imu-sensors'?
Line 854, Column 75: [Warning-file-not-found] Invalid file link: 'TBD'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 68f4461:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/research-mode.md
:warning:Warning
View
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md

Line 57, Column 22: [Warning-file-not-found] Invalid file link: 'hololens2-hardware.md'.
Line 130, Column 9: [Warning-bookmark-not-found] Cannot find bookmark '#Main-Sensor-Loop' in 'research-mode.md', did you mean '#main-sensor-loop'?
Line 139, Column 5: [Warning-bookmark-not-found] Cannot find bookmark '#Sensors' in 'research-mode.md', did you mean '#sensors'?
Line 139, Column 29: [Warning-bookmark-not-found] Cannot find bookmark '#Sensor-coordinate-frames' in 'research-mode.md', did you mean '#sensor-coordinate-frames'?
Line 146, Column 5: [Warning-bookmark-not-found] Cannot find bookmark '#Sensor-frames' in 'research-mode.md', did you mean '#sensor-frames'?
Line 308, Column 18: [Warning-bookmark-not-found] Cannot find bookmark '#Imu-sensors' in 'research-mode.md', did you mean '#imu-sensors'?
Line 1569, Column 75: [Warning-file-not-found] Invalid file link: 'TBD'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 806ffc6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 49055c9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 3400fb3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 4c0764a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 8cbe274:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/research-mode-img-01.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/research-mode-img-02.png
:white_check_mark:Succeeded
View

mixed-reality-docs/research-mode.md
:white_check_mark:Succeeded
View

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


how to insert the filter above into the header of the table in "status" column

This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Feature Request
please first make sure your request falls under the official Material Design spec guidelines https://material.google.com/
Bug Report
please provide steps to reproduce and if possible screenhots, animated Gifs and/or a Plunker (or similar).
you can easily create animated Gif with this free PC/OSX App: http://www.cockos.com/licecap/ and a Plunker to help us reproduce it
Plunker template: http://plnkr.co/edit/7uZQn4mLNJkL6XN9WSNd
Screenshots or link to CodePen/Plunker/JSfiddle
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Which version of Angular and Material, and which browser and OS does this issue affect?
Did this work in previous versions of Angular / Material?
Please also test with the latest stable and snapshot versions.
Other information
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)

Closing this since i guess its a duplicate of https://github.com/Teradata/covalent/issues/817


Add sections and sub-section to live document nav bar

Again following the webassembly example, the side bar should list all the sub-section heading in the current section, e.g. https://webassembly.github.io/spec/core/valid/types.html

This is done now, yes, @delapuente ?

I just checked and this is live so closing.

I just checked and this is live so closing.


ngx-monaco-editor not working with angular 6

ngx-monaco-editor not working with angular 6 and angular cli-6 getting below error
Refused to execute script from 'http://localhost:8425/dashboard/assets/monaco/vs/loader.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
I am using "ngx-monaco-editor": "^6.0.0". With angular 5 and mgx-monaco-editor 4 I am not facing any issues.

This is the sample code with angular 6 and ngx-monaco-editor 6.0.0. Please try if it works download

@atul-wizni thanks for the quick reply. It was my mistake with base href configuration to app. It's working. You can close the ticket.
Thanks again!!

for those of who have some trouble because of it, try this down below.
{ "glob": "/*", "input": "../node_modules/ngx-monaco-editor/assets/monaco", "output": "./assets/monaco/" }
->
{ "glob": "/*", "input": "./node_modules/ngx-monaco-editor/assets/monaco", "output": "./assets/monaco/" }
i don't know why but it works for me.

How can this be so convoluted? nothing of this works for me in angular 12 anymore.


Tasks to release 0.1.0

[x] Resolves #7 ref: #85, #93, #96
[x] Drop deprecated old major method ULID.monotonic_generate ref: #94
[x] ~Hide or drop MonotonicGenerator attr_accessor~ => This is needed for testability, I'll keep for now.
[x] At least, drop deprecated methods for part of #84 ref: 0f256006b93199e99a6a6afee8a25f8d208afb00
[x] Not crucial, but I'd like to get answer around #8, ~at least, entropy attr_reader should be removed~ => This is needed for testability, I'll keep for now.
[x] Make official or remove some undocumented methods. e.g ULID#timestamp, ULID#randomness =>  https://github.com/kachick/ruby-ulid/commit/fe2cb12a33bdff553f7fe9780511242e5e12ebe5
[x] Resolves #13 if it is possible ref: #113
[x] Make some constants be private constants if they have not clear name #121
[x] Make ULID.new as a private method for optimizations in feature. ULID#initialize interface might be changed and be complex ref: #107, #108

https://guides.rubygems.org/patterns/#semantic-versioning 👀


Strange Problem of solver

quadratic equation with one unknown
for Ag=2400 it works, but for Ag=2401 it failed

Hi!
Thank you for your question. This is a very important topic. It is a question of selecting a good target precision.
By default Calcpad uses Precision = 10^-15 which is very low. If you set Precision = 10^-12 before the $Root function, it will work. Why is that?
Since your equation actually involves a constant term R_g*A_g*e, it would be more properly to express it in the form:
$Root{f(x) = y @ x = 0 : h},
where y = R_g*A_g*e and f(x) contains the rest. This now can be solved for Precision = 10^-15.
If you solve for f(x) - y = 0 and y is of about 10^3 magintute, so will be 'f(x)' when approaching y. Subtarcting both will lead to cancelation of 3 significant digits due to the way floating point numbers are stored into the memory. They can hold not more than 17 significant digits (average 16). So you cannot achieve precision better than 10^-13.
So, if you need to solve an equation in the form f(x) - y = 0 you have to set the precision to be Precision = 10^-15*y.
In your case, just write Precision = 10^-15*R_g*A_g*e before calling the $Root function and it is always work.

"Thank you very much for your detailed explanation."
---Original---
From: "Ned @.>
Date: Tue, Nov 26, 2024 17:10 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [Proektsoftbg/Calcpad] Strange Problem of solver (Issue #395)
Hi!
Thank you for your question. This is a very important topic. It is a question of selecting a good target precision.
By default Calcpad uses Precision = 10^-15 which is very low. If you set Precision = 10^-12 before the $Root function, it will work. Why is that?
Since your equation actually involves a constant term R_gA_ge, it would be more properly to express it in the form:
$Root{f(x) = y @ x = 0 : h},
where y = R_gA_ge and f(x) contains the rest. This now can be solved for Precision = 10^-15.
If you solve for f(x) - y = 0 and y is of about 10^3 magintute, so will be 'f(x)' when approaching y. Subtarcting both will lead to cancelation of 3 significant digits due to the way floating point numbers are stored into the memory. They can hold not more than 17 significant digits (average 16). So you cannot achieve precision better than 10^-13.
So, if you need to solve an equation in the form f(x) - y = 0 you have to set the precision to be Precision = 10^-15y.
In your case, just write Precision = 10^-15R_gA_ge before calling the $Root function and it is always work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

No, problem. Thank you for asking.
If you want to solve the quadratic equation analytically, please use the recommended equation in "What every scientist..." [1] and "Numerical  recipes in C", page 227 [2]:

Unlike the "classical" one it is not sensitive for floating point rounding errors.
References:
[1] https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html
[2] https://nr304ob.s3.amazonaws.com/4G8102XTQPCMJ2XE.pdf


Redirect applet logging

Currently the applet may crash on loading under some circumstances (I see this when running in Firefox on one PC) with logging running in the Java Console - which goes poof immediately when the applet crashes. There might be a clue in the logging and this could be a simple issue, but the logging goes poof too fast!
Independent of this issue it would be nice to have a better handle on managing logging for applets. You're supposed to be able to enable extra logging with the Java Console up and I did see a log get created at C:\Users\Cervator\AppData\LocalLow\Sun\Java\Deployment\log - but it had nothing but a header in it, as the logging wasn't redirected!
Any (tested!) research into how to make this work better (with any sample applet, doesn't have to be ours) would be appreciated
Helpful link on the console: http://www.java.com/en/download/help/javaconsole.xml
Note: This may be redundant if we can get #65 to work instead

Turns out there are more related settings in the Java config (under control panel for Windows) that impact this. With added debug/logging enabled there some logging finally does show up in the deployment log. However, that logs to really ugly HTML - still wonder if there isn't a more simple approach to just redirect logging (maybe to the shiny new temp dir the applet saves stuff to)


Prepare to create a Java app with an MTA template

Tutorial URL: https://developers.sap.com/tutorials/cp-cf-java-create.html
Please specify the step you are referring to template MTA. I dont see the MTA template in my trail version. Could you please help me on this. I have also attached the screenshot for reference. Looking forwoard for your reply.
Thank you,
Venkhatesh.

Hey @DI9-dev ,
thanks for your issue. You are right, the screenshots in the tutorial are confusing. I'll fix this.
In the meantime: If you choose "Cloud Foundry" instead of "Neo" in the selectbox for the "Environment" you should be able to continue with the tutorial.
Cheers,
Max

Fixed.


Add parameter to dynamically map ID spaces

In the golr schema we always choose a clique leader from the equivalence set for setting fields like subject, object. In Monarch this is done by @jnguyenx's clique leader code. In GO this is hardwired along partly political grounds as to whose ID to show.
Clients often want associations mapped to their ID space of choice. While it is always possible to do this as a post-processing step using an ID map service, better to give the option to do this on the fly.
In Monarch we can do this because we have closures on subjects as well as objects. (this also gives us superclass closures which is unwanted, but in general these are ids in a different id space; longer term we should have one closure for equivalence, and one for reflexive closure over subclass).
@kltm - as part of general alignment can we have subject_closures in amigo-golr too? No action required on your part now I can make experimental PR, this is just for context.

Any kind of closure can be had, they just need to be added to the metadata and made sure that they come out in the right spot in the UI, etc.
Practically, the loader will need a lot of kicking on the GO side. Or a rewrite.

rewrite!


Add support for cluster sharding persistence

Are there any plans to update this plugin to support cluster sharding persistence?
Currently if you use Akka.Persistence.MongoDB as a persistence plugin for cluster sharding, it fails to serialize messages. Even if you register the types using RegisterClassMap. You end up with an empty payload like this:
"Payload" : {
    "_t" : "ShardRegionRegistered"
},

In sql plugin, it uses binary serialisation to generate byte[], so hyperion serializer works fine with all those payloads. But in mongo, when BsonSerializer comes accross those messages:
ex: ShardRegionRegistered, ShardHomeAllocated, ShardHomeDeallocated, etc. It always generates an empty payload.

closed via #42


nixos/podman: allow changing the default network

Description of changes
You might want a different network if you happen to be using the 10.88.x.x network for something else.
Been running with this for a very long time.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

TBH I'd really prefer not to add more networking options until after we've switched to netavark .

The formatting is just nixpkgs-fmt doing its thing on save, but I absolutely understand where you're coming from.
I've carried this PR locally for over a year I think, so if you want to hold off on changes, that's not a problem. Your call.

Thanks, give me a few weeks and I should get around to the netavark changes. I'll switch this to a draft for now.

Thanks, give me a few weeks and I should get around to the netavark changes. I'll switch this to a draft for now.

@zowoq I'm also interested in switching to netavark, let me know if you have something to test

now that nixpkgs-fmt changes have been merged, the changes are significant smaller. If you would still prefer to wait, that is of course your call @zowoq

Yes, I'd rather wait.

netavark PR: https://github.com/NixOS/nixpkgs/pull/199965
Closing this as it's not needed with defaultNetwork changing to settings style config.


Adding docs for Integer#downto

I've a small pull request to put in that adds some docs to downto as missing docs bother me, even for "obvious" stuff. It also renames the variable to to limit a là Ruby, because downto(limit) reads better than downto(to), especially for writing documentation. I've matched that up in the DowntoIterator for consistency.
As an aside, none of the issue templates really seemed appropriate for this, any chance of one for documentation? (or something like "other")
Regards,
iain
PS Yes, I meant Int not Integer

Sounds good.
Adding documentation is always welcome and doesn't necessarily require writing an issue about it first. If there's something that's up for discussion, I think the language improvement discussion choice is good.
Same for changing the API, it's a language improvement discussion.

I'll keep it in mind, thanks. I'll draft a template for documentation issues when I can, hopefully remove a little bit of friction, docs are always a good one for newcomers to have a go at :)
Regards,
iain

I'm not sure about changing to to limit. It's not a huge improvement, so the question stands whether it's worth it. We'd have to support to as a named argument as well for backwards compatibility.
This should also be discussed together with Int#upto which has the same parameter name. In Ruby, both parameters are called limit, in Crystal, both are called to. They should definitely match up.