refactor ZktrieState [dup #903]

This PR duplicated the target of #903 with another approach:
We consider:

A CircuitInputBuilder object should not be reused for building more witness block after it is used inside block_traces_to_witness_block_with_updated_state. as the result, we can updated the ZktrieState memeber in it into the zktrie state after the witness block is applied, just like the state/code_db members.
We also notice that Witnessgenerator do not need a snapshot about account /storage states since all the information can be read from the underlying database (ZkMemoryDb here) with trivial cost. So ZktrieState also do not need to keep such a snapshot inside it (they have been kept in state db).
With refactoring above, and thanks to the lambda nature of trie's storage. ZktrieState now can esaily switch to any state it have been once updated to, and create new ZkTrie object with almost no cost, which is ready for being updated by another witness block.

Have run mock proving on 40 batches (>200 chunks) from replayed alpha testnet, so far so good


Claim amount is in odd place and needs context

This comes on screen 14 for me. I don't really know how to interpret "claim amount" as a question. Maybe move this up front with more information and context to help someone figure out what amount they are asking for?
The auto-updating fee is a nice touch, but filing fee might also need to be explained.

Probably, this should be on the same screen or come after the "describe your claim" question, and we should separate out the part of the "describe your claim" question that asks the person to calculate it.


v12.0.0 lags behind by 5 days.

I have 2 identical physical machines with 24 GB RAM, each running Debian v5.10 and cardano-node v1.34.1, both fully synced at 100%.
One machine is running db-sync v11.0.4, and on average lags behind by 3 - 15 minutes.
The other machine is running db-sync v12.0.0 and is lagging behind by almost 6 days.

How long has it been running 6 days behind? Are you running if solid state or electo-magnetic disks? How old is the hardware?

it's at 7 days 21 hours now.
I'm running on 240GB ssds.
Processor specs:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          8
On-line CPU(s) list:             0-7
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           142
Model name:                      Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Stepping:                        11
CPU MHz:                         962.559
CPU max MHz:                     4600.0000
CPU min MHz:                     400.0000
BogoMIPS:                        3999.93
Virtualization:                  VT-x
L1d cache:                       128 KiB
L1i cache:                       128 KiB
L2 cache:                        1 MiB
L3 cache:                        8 MiB
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     KVM: Mitigation: VMX disabled
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB
filling
Vulnerability Srbds:             Mitigation; Microcode
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts a
cpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch
_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq
dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2
apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefe
tch cpuid_fault invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept
vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_no
tify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities

it's at 7 days 21 hours now.
I'm running on 240GB ssds.

There is no reason I can see for that machine to be running so slow.  I run an instance on 3 year old hardware and sync from genesis to chain tip in about 6 days.
Is your node syncing correctly and at chain tip? Anything in the logs? Either node or db-sync ?

Turns out that the service didn't restart after a power out. I'm sorry for wasting your time.

There is no reason I can see for that machine to be running so slow. I run an instance on 4 year old hardware and db-sync syncs from genesis to chain tip in a bit less than 6 days.

@erikd Can you share your specific hardware and setup? I'm running on a 8 core + 32G Ram + 40GB Swap + 800GB SSD with mainnet node and db-sync and I cannot sync beyond epoch 326. I am within the specified requirements on the Readme for the 12.0 release and even what is shown now in master.
It took me 13 days to get there. Since then there is always a failure, there connection to the node socket seems to shortly drop, thus subscription is lost then restarted, thus rollback triggered and a full day goes away just deleting blocks, before it restarts and hits the same problem.
Cardano node 1.34.0
DB-Sync 12.0.2

@Titan-C The machine is more than adequate for running db-sync.

I cannot sync beyond epoch 326.

What happens?

It took me 13 days to get there.

That machine should sync the whole chain in under 10 days. You are not running this on an AWS instance by any chance?

What happens?

The error log, from going fine, to error to restart :
[db-sync-node:Info:58] [2022-04-30 22:29:25.56 UTC] insertEpochInterleaved: Epoch 326, 1102152 rewards
[db-sync-node:Info:58] [2022-04-30 22:37:17.53 UTC] Offline pool metadata fetch: 74 results, 25 fetch errors
[db-sync-node.Mux:Info:50] [2022-04-30 23:30:51.11 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node-mainnet/socket"} event: State: Dead
[db-sync-node:Error:58] [2022-04-30 23:30:55.58 UTC] runDBThread: AsyncCancelled
[db-sync-node:Error:53] [2022-04-30 23:30:55.58 UTC] ChainSyncWithBlocksPtcl: AsyncCancelled
[db-sync-node.Subscription:Error:49] [2022-04-30 23:30:55.59 UTC] Identity Application Exception: LocalAddress "/run/cardano-node-mainnet/socket" MuxError MuxBearerClosed "<socket: 22> closed when reading data, waiting on next header True"
[db-sync-node.ErrorPolicy:Warning:6] [2022-04-30 23:30:55.59 UTC] IP LocalAddress "/run/cardano-node-mainnet/socket" ErrorPolicySuspendPeer (Just (ApplicationExceptionTrace (MuxError MuxBearerClosed "<socket: 22> closed when reading data, waiting on next header Tru>
[db-sync-node.Subscription:Notice:48] [2022-04-30 23:30:57.56 UTC] Identity Restarting Subscription after<PHONE_NUMBER>60766s desired valency 1 current valency 0
[db-sync-node.Subscription:Notice:48] [2022-04-30 23:30:57.56 UTC] Identity Starting Subscription Worker, valency 1
[db-sync-node.Subscription:Notice:3835] [2022-04-30 23:30:57.56 UTC] Identity Connection Attempt Start, destination LocalAddress "/run/cardano-node-mainnet/socket"
[db-sync-node.Subscription:Notice:3835] [2022-04-30 23:30:57.56 UTC] Identity Connection Attempt End, destination LocalAddress "/run/cardano-node-mainnet/socket" outcome: ConnectSuccessLast
[db-sync-node.Handshake:Info:3835] [2022-04-30 23:30:57.56 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node-mainnet/socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV>
[db-sync-node.Subscription:Notice:48] [2022-04-30 23:30:57.59 UTC] Identity Required subscriptions started
[db-sync-node.Handshake:Info:3835] [2022-04-30 23:30:57.78 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node-mainnet/socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_10 (TInt 7648>
[db-sync-node.Mux:Info:3835] [2022-04-30 23:30:57.78 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node-mainnet/socket"} event: Handshake Client end, duration 0.217621065s
[db-sync-node.Mux:Info:3836] [2022-04-30 23:30:57.78 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node-mainnet/socket"} event: State: Mature
[db-sync-node:Info:3839] [2022-04-30 23:30:57.78 UTC] Starting chainSyncClient
[db-sync-node:Info:3839] [2022-04-30 23:30:57.91 UTC] Cardano.Db tip is at slot 56177748, block 7018468
[db-sync-node:Info:3844] [2022-04-30 23:30:57.91 UTC] Running DB thread
[db-sync-node:Info:3844] [2022-04-30 23:30:58.16 UTC] Rolling back to slot 55999628, hash 0a122e44ecd20e2f78c8afcfc720d6afce4c79954fb059e22ff5c723ccf85782
[db-sync-node:Info:3844] [2022-04-30 23:30:58.36 UTC] Deleting 8469 blocks up to slot 56177748

That machine should sync the whole chain in under 10 days. You are not running this on an AWS instance by any chance?

That is way better than any of my experiences. I'm not on AWS, yet it is
a VPS from Contabo, the VPS-L. Are VPSs an issue?
I first had the NVMe offer but I ran out
of space 200GB where not enough for node & db-sync. It never
synchronized. From Feb-26 till April-2nd it was syncing, 36 days, it
didn't reach chain-tip and but I ran out of space. After some slow
customer service I changed my plan to the VPS-L on SSD and 800GB. In
between I also learned to tune Postgresql out of the default config. I
started the new VPS on April 15th, node and db-sync launched
simultaneously. The node reached the chain tip in a little more than a
day, db-sync was a lot slower. By April 27th db-sync started showing
these errors. There is no progress from there on. Stuck at epoch 326,
insert->Error->delete blocks->loop.
Last attempt was on PostgreSQL 13.6
shared_buffers = 1GB
work_mem = 128MB
maintenance_work_mem = 1GB
wal_level = minimal
max_wal_senders = 0

Everything seems to point to you VPS not being up to scratch. Check out the IOPS of that machine. As suggested in the system requirements, you will need 60k IOPS a second or better.


Relative static assets in CSS folder

Just opening a new issue confirming that bug #208 still exists and @githoniel's solution is still necessary today.
This has all to do with using relative paths in CSS files.
<style>
  .element {
    background-image: url('~./assets/img/bg.png');
    // works in dev
    // in production, browser will try to retrieve /static/css/assets/img/bg.png
  }
</style>

Just commenting to let you know that I intend to look into this, but it wil require to make thorough tests of various scenarios, especially nested routes in vue-router, so see if that fix actually works across all of them.
So please be patient, It's not forgotten.

So I tried to reproduce it, but still can't,

How should i use that same in vue with Typescript?
`image: require('../../assets/logo.png')
I have this error:

I'm trying to deploy into a sub folder on the production server, and using
module.exports = {
  publicPath: '/webapp/'
}

in vue.config.js
works fine for the javascript files, however the background image urls in the styles don't work
e.g.
    background: url(/assets/images/unit_tab_indicator_ss.png);
does not become
    background: url(/webapp/assets/images/unit_tab_indicator_ss.png);
I've tried removing the absolute path / from the front of the url and also tried using ./  but nether of these will compile into a valid Vue.js application,
I've also tried setting the assets path in the config e.g.
https://cli.vuejs.org/config/#assetsdir
setting it to './' or '/assets'  but this doesn't work either, as normally the build fails
Is there a workaround for this problem ?

I'm trying to deploy into a sub folder on the production server, and using
module.exports = {
  publicPath: '/webapp/'
}

in vue.config.js
works fine for the javascript files, however the background image urls in the styles don't work
e.g.
 background: url(/assets/images/unit_tab_indicator_ss.png);
does not become
 background: url(/webapp/assets/images/unit_tab_indicator_ss.png);
I've tried removing the absolute path / from the front of the url and also tried using ./ but nether of these will compile into a valid Vue.js application,
I've also tried setting the assets path in the config e.g.
https://cli.vuejs.org/config/#assetsdir
setting it to './' or '/assets' but this doesn't work either, as normally the build fails
Is there a workaround for this problem ?

Try this https://github.com/vuejs/vue-loader/issues/646#issuecomment-454959580


Category selector should use category selector module

:eyes:

Where is this category selector?

The core module for selecting a category in composer, for example .

Oh sorry, wrong repo. This should go in rss

https://github.com/barisusakli/nodebb-plugin-rss/issues/67


Enable slimScroll for control-sidebar in fixed layout

SlimScroll is not set for .control-sidebar. Moving the functionality from main sidebar is not possible because of different structure of control-sidebar.

The control sidebar is implemented for different purposes than that of the main sidebar. Thus, the structure of anything in the main sidebar is invalid in the control sidebar.
If you want to enable slimscroll for the control sidebar, then you can do so by activating it manually using:
$('.control-sidebar').slimscroll({
  //Add your options here
});

We may misunderstand each other, I will try to explain it better.
There is issue with control-sidebar for small screens and window resize. Because slimscroll is not applied  for .control-sidebar, common browser-based sidebar is shown for Fixed layout (and that is not so 'awesome'):

But it is not possible with current html/css for .control-sidebar to simply apply slimsroll in the same way like for sidebar menu (in app.js, fixSidebar() method). When applied, .control-sidebar is stretch to full width of screen:

I think slimscroll should by applied for .control-sidebar by default.

It is possible when you define a specific width since SlimScroll requires one. The default width is 230px.
SlimScroll has brought so much grief to the template and is not being maintained by its creator anymore. In a future release, I will replace this plugin with a more reasonable option.
Let me know if you need more help in adding slimscroll to your control-sidebar.

Thank you, I can set it. Actually, I meant it as a feature request rather then a question.


[Bug] 在npu上训练时，告警 Grad strides do not match bucket view strides

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (master) or latest version (3.x).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
master branch https://github.com/open-mmlab/mmdetection
Environment
ascend cann 6.3
pytorch 1.8.1.rc3
torch_npu 1.8.1.rc3
Reproduces the problem - code sample
bash tools/dist_train.sh configs/yolox/yolox_s_8x8_300e_coco.py 8
Reproduces the problem - command or script
bash tools/dist_train.sh configs/yolox/yolox_s_8x8_300e_coco.py 8
Reproduces the problem - error message
[W reducer.cpp:401] Warning: Grad strides do not match bucket view strides. This may indicate grad was not created according to the gradient layout contract, or that the param's strides changed since DDP was constructed.  This is not an error, but may impair performance.
grad.sizes() = [1, 128, 1, 1], strides() = [128, 1, 1, 1]
显示警告以后，不往下执行
Additional information
No response

Prerequisite

[x]  I have searched Issues and Discussions but cannot get the expected help.
[x]  I have read the FAQ documentation but cannot get the expected help.
[x]  The bug has not been fixed in the latest version (master) or latest version (3.x).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
master branch https://github.com/open-mmlab/mmdetection
Environment
ascend cann 6.3 pytorch 1.8.1.rc3 torch_npu 1.8.1.rc3
Reproduces the problem - code sample
bash tools/dist_train.sh configs/yolox/yolox_s_8x8_300e_coco.py 8
Reproduces the problem - command or script
bash tools/dist_train.sh configs/yolox/yolox_s_8x8_300e_coco.py 8
Reproduces the problem - error message
[W reducer.cpp:401] Warning: Grad strides do not match bucket view strides. This may indicate grad was not created according to the gradient layout contract, or that the param's strides changed since DDP was constructed. This is not an error, but may impair performance. grad.sizes() = [1, 128, 1, 1], strides() = [128, 1, 1, 1]
显示警告以后，不往下执行
Additional information
No response

训练集： coco2017

I have met the same problem


Use underscores to match Rome

Why:
Because all of the other entries use this notation

What's being changed (if available, include any code snippets, screenshots, or gifs):
before
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#supported-file-types

after
https://docs-32049-0a8f1b.preview.ghdocs.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#supported-file-types

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

@jsoref Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Squelch deprecation warning

Most recent CMake started complaining about the pending end of 3.8 support.

CMake Deprecation Warning at CMakeLists.txt:4 (cmake_minimum_required):
  Compatibility with CMake < 3.10 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.

We can retain support by adding a max version. This will not prevent use with newer versions, but indicates forward compatibility.^1

Why not use CMake > 3.8? 3.8 was released 2018 and there's barely a reason to stay on such an old version.

Why not use CMake > 3.8? 3.8 was released 2018 and there's barely a reason to stay on such an old version.

I considered that, but we're not using anything that requires anything newer, and this is easy enough to fix without breaking compatibility. I agree, however, that we should not hesitate to bump the minimum version if we ever want a newer CMake behavior.


[android] Ignoring AVD used during last build

Reasons for making this change:
deploymentTargetDropDown.xml stores the AVD used in last build and is not portable
Links to documentation supporting these rule changes:
https://betterprogramming.pub/exploring-the-idea-folder-790931c19191
If this is a new template:

Link to application or project’s homepage: TODO

Your link does not provide any context for this change. Can you expand on your explanation and fix the merge conflicts?

It seems that this change was already introduced in main branch by ignoring the whole .idea directory. I'll close this PR.


reorder-imports panics if first line is use-statement

use foo;

If reorder-imports is true, rustfmt panics with
thread 'main' panicked at 'index 0 and/or<PHONE_NUMBER> in `use foo;
` do not lie on character boundary', ../src/libcore/str/mod.rs:1707

Most likely caused by #1104 .

cc @studoot

This and #1116 reference the same issue - it's just that @crumblingstatue built with —release, while @pepyakin built in debug, as far as I can tell through my testing. This means that PR #1117 will fix this issue.
I've had a look at the relevant system tests and they seem unable to detect this defect, because of the comments that indicate the formatting options used - any suggestion for what might be added to cover this boundary condition, @nrc?

@studoot so, you can repro this locally? And what exactly is the problem? You need a single import on the first line of the file with no comments?

@nrc about the last one: issue is not reproducing if I add comment before import. Because of this #1117 has no tests.
All of the following tests are failing with the same issue:
use foo;

use quix::baz;
use foo;

use foo2;

fn main() { }

It seems it is enough to have an import on the very first line. It helps even after adding newline before import. So following code (where ⎵ — denotes newline)
⎵
use foo;

doesn't panics.

Yes, I can repro - with the files attached to #1116 extracted into a rustfmt build directory, using  cargo run --bin rustfmt --release -- main.rs --write-mode plain. In release mode, the arithmetic under flow detection isn't enabled, so the panic occurs when trying to resolve the character span that results.
The problem occurs because of how I'm persuading the FmtWriter to output an appropriate span before the use decl span - if a use declaration is first thing in a file, it has no preceding span, and its own span starts at zero. I subtract one from the start of the use decl span to get a preceding span, which is probably the wrong thing to do. @pepyakin's PR fixes the panic, but I think I need to think about a better fix for the underlying issue.
The crux of the problem re: testing is that the use decl span needs to start at zero, which precludes leading comments in the source file, so there needs to be some other way of indicating the desired configuration.

Hmm, it does seem there is no good way to test this. You could just use a unit test, rather than a regression test to catch it, I'd have thought.

I've added a PR (#1122) which adds a test case for this issue (which I've verified would catch this issue). As the PR states, it adds another route by which a test case can specify its config, which may or may not be something that you actually want, @nrc...

Closing, since this does not reproduce anymore.


error code when i press F5

i type in a command as simple as print('hello') then press F5 to run and my computer says it cant find Python

I too am experiencing this issue.
example code:
name = John print(name)
I get the following error: "Windows cannot find 'python'. Make sure you typed the name correctly, and try again."
error occurs upon running the code.
running version 1.35.1 of Atom (latest) on Windows 10 version 1803

I am having the same issue, and I even added Python to both my user path and my system path environment variables and it's still not working

I seem to have fixed, I started by uninstalling everything (python and Atom)and then re-installing python to "C:\Python3.7".
Not choosing quick install but manually selecting all the options and path.

Make sure you select the option to add "PATH"

I tested by running 'python' in my command prompt to make sure it was found on my system and then installed Atom.
If I now press F5 it opens up the Python IDE and runs the script.
I feel so dumb for not trying this sooner.


Update the Authorize.net Gateway docs to use $1

The documentation on:
http://readthedocs.org/docs/django-merchant/en/latest/gateways/authorize_net.html
Shows a transaction using credit card<PHONE_NUMBER>222 for $100, which is supposed to succeed.
This is actually a special card # on Authorize.net such that the return code from the API call will be the same value as the card amount.  In this case, it's error code 100, which means "The eCheck.Net type is invalid."
I spent about 4 hours debugging the error, wondering if there was in fact some malicious code that would attempt a check transfer.  I finally found it was normal behavior for Authorize.net
It seems like a small thing but I highly recommend adjusting the docs.  It really throws off someone who's just trying out your project, which actually seems pretty good.
Also, your demo site http://merchant.agiliq.com/authorize/ works, but only if all parameters on the form are filled correctly, otherwise it returns with a 500 error.  For people just checking it out, it would be helpful to actually show what working form data would be.

@dragonx Thanks for the bug report. The documentation has been fixed and I agree that the demo site needs some work.


Back button goes to main page in ''neaby''

Summary:
When pressing 'back' button in ''neaby'' after pressing the button on right top, it goes straight to the main page. I should expect that it would just close that tab , and continue searching on map.
Steps to reproduce:
At main page , go to ''neaby''
Press the button on right top , to show a list with places
Press back button
Commons app version:
2.9
Screen-shots:

Is this not a duplicate of #2245?

in fact is the same issue but this is version 2.9 , and that was 2.8.5

Okay in that case I'm going to close this issue in favour of #2245, given it's the same issue reported for different versions - there simply has not been a fix released yet.
If you think this should stay open please do reopen/comment for me to reopen.


Is this plug-in compatible with Django 2.0

Last commit at May 30, 2017
Django release date is Dec, 2017.
Readme is saying, requires 1.7 or newer. But, according to difference of dates, I'm wondering is "Admin Tools" plug-in is compatible with Django 2?

We are use 0.8.1 on new project with Django 2 - working fine

Thank you for the fast response.


[e2e]: gcb tag main annotated-build slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6375223609
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Mon Oct  2 02:26:33 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6387892019
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Oct  3 02:26:31 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6400809349
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Oct  4 02:27:05 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6413890219
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Oct  5 02:28:35 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6426753119
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Oct  6 02:27:10 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6438446904
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Oct  7 02:24:49 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6444982376
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Oct  8 02:29:11 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6451655560
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Mon Oct  9 02:26:14 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6463964372
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Oct 10 02:25:40 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6477206951
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Oct 11 02:26:13 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6490479036
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Oct 12 02:24:36 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6503287601
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Oct 13 02:30:03 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6515012760
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Oct 14 02:23:29 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6521454255
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Oct 15 02:29:08 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6528247034
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Mon Oct 16 02:29:30 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6541744637
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.gcb.tag.main.annotated-build.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Oct 17 02:27:32 UTC 2023
Tests are passing now. Closing this issue.


Provide IECC Climate Zone for each IECC Year

This could be very useful if it could look up both the 2006 and 2009 IECC climate zones for a location. I am about 80% sure those are the only years where the zones changed and that 2012 and 2015 have not changed them.

Thanks for the suggestion. What is your use case? That seems like something that could be added in the future if there was enough demand for it. If you could point to reference material showing the differences in the boundaries that would be helpful.

I'm working with @shorowit as he develops the ERI use-case for the HPXML standard for the purpose of improving the consistency of ERI and related home energy ratings, e.g. HERS, across different software. A recent discussion brought to light that the various software that would make use of the calculation engine may not be consistent in terms of what climate zone they consider a given location to have, and that there was no readily available machine consumable source-of-truth for the IECC climate zone for any particular IECC year. In looking for a solution I came across your work.
The canonical, to the best of my knowledge, IECC climate zone documents are available through the ICC's site.

2006 IECC (direct link to climate zones listing (embedded as pdf))
2009 IECC (direct link to climate zones listing (embedded as pdf))
2012 IECC (direct link to climate zones listing)
2015 IECC (direct link to climate zones listing)

Thank you! Very very helpful. I'll leave this issue open since I probably won't get started on it right away. I don't love PDFs as a source of truth and previously had made this CSV (below) by manually copying out the list. We had previously found errors (human mistakes) in it but aren't aware of any now.  This CSV is what eeweather bases its IECC climate zone handling on. At the time when I was working on developing this, I didn't realize there were multiple versions of the standard (obvious in hindsight - especially as even county names upon which this is based change from time to time), or I might have been more specific in indicating which version(s) the eeweather package uses.
If or when we do get started on this process, the first step will be to get those county/climate zone lists into this CSV. If this is an urgent matter for you, you could hasten the process by forking and adding new columns to this CSV containing the appropriate data and we can go from there.
https://gist.github.com/philngo/d3e251040569dba67942

This doesn't seem to be a high priority so I am closing this issue. If anyone interested in this makes progress on this issue, please feel free to reopen this issue to continue the discussion or (preferred) open a pull request with a proposed implementation.


Hidden folder (dot-directory) is not supported

If a folder containing JS files is a hidden dot folder (.customjs, for example) then plugin can't detect files to load.
Repro vault https://github.com/knopki/obsidian-custom-js-dot-dir-repro
I think it's because of using the app.vault.getFiles() to get list of files.
For example,
// working
app.vault.getFiles().filter(f => f.path.startsWith("customjs"))
  // => [{"path": "customjs/startup.js", ... }]

// not working
app.vault.getFiles().filter(f => f.path.startsWith(".customjs"))
  // => []

// but
await app.vault.adapter.list(".customjs")
  // => { "folders": [], "files": [".customjs/startup.js"]
}

Seconded. Is there any way around this? Besides showing a "scripts" folder in the vault, that is

It's been a while so I can't remember for sure, but I think app.vault.adapter was the only one that works on mobile. Have you tested mobile with your fix?

@saml-dev Working on android!
Tested snippet:
    // Get paths in folder
    if (this.settings.jsFolder != '') {
      const { files } = await this.app.vault.adapter.list(this.settings.jsFolder);
      const scripts = files.filter((f) => f.endsWith('.js'));
      filesToLoad.push(...scripts);
    }

I use this workaround:

My scripts-folder is named "_scripts"
I use the plugin "Hide Folders" (→ https://github.com/JonasDoesThings/obsidian-hide-folders) to hide all folders that start with _, with this setting:

Folders to hide: Startswith::_

The Hide Folders plugin removes the _scripts folder from the folder sidebar and search results, and most other places.


Homepage

We've considered ideas around:

A search box

Summary metrics

What is GBIF?

The GBIF Network map (see #70)

Featured datasets

News

[ ] Guidance for content in comments below

[ ] Implementation of page v1

@timrobertson100 revised text for home, per Skype discussion earlier this week.
Under development
We are now actively engaged in redesigning GBIF.org. This is still an early-access release with limited functionality. The content exposed here is the same as that presented on the current site.
Our first release aims to address issues reported and observed since we launched the current GBIF.org site in October 2013. Most common among these are a subpar search experience and confusing navigation within a large site.
Significant improvements in our data processing and handling infrastructure now make it possible to introduce site-wide cross-content search, and revisions to the navigation reflect a much leaner site featuring a menu that encapsulates a simpler overall structure.
Thanks for your interest, and your patience: we'll turn on feedback mechanisms to get your comments soon.


DMG is damaged

Operating system
MacOS Sonoma 14.5
YouTube Music Desktop App Version
0.12.11
Bug description
DMG is damaged and cannot open the Updater
Steps to reproduce

Download DMG
Open
Disappointment

Relevant log output
“YouTube Music for Desktop” is damaged and can’t be opened. You should eject the disk image.
This item is on the disk image “YouTube-Music-for-Desktop-0.12.11-arm64.dmg”. Chrome downloaded this disk image today at 7:03 PM.

Apple Silicon Builds need to run this command after installing:
xattr -dr com.apple.quarantine /Applications/YouTube\ Music\ for\ Desktop.app
until i pay ($99+) for a apple license

I decided to download the non arm64 version and it works perfectly. Great work you're doing.


Fix broken custom runtimes link

Leaving for you to merge just for the sake of process :nerd_face:


Lineup screen

[ ] Add more unit options to pick. Here are some free Unity assets:

https://www.notion.so/lambdaclass/Assets-for-enemies-bosses-e96a65420efe46619286e09feed45c08

[ ] Add enemy units

[ ] Add more unit options to pick. Here are some free Unity assets:

https://www.notion.so/lambdaclass/Assets-for-enemies-bosses-e96a65420efe46619286e09feed45c08

[ ] Add enemy units

I'm not a fan of the zombie, see if there is something else in the future


Resetting each epoch?

Using Adam optimizer, not L2L for the CIFAR problem: If I print the cost after each epoch, it doesn't decrease over time running with learning rate .001, num_steps 100 num_epochs 100. However, printing the cost for each num_step, it decreases within the epoch. Why does it seem like the weights are being reset each epoch?
I've also added code to check the training and validation accuracy after each epoch. These are also not decreasing with each epoch.

If I comment out line 4 from the original code, sess.run(reset), I get the expected results of decreasing error every epoch. Is it incorrect not to reset the problem_reset and optimizer_reset each epoch?
def run_epoch(sess, cost_op, ops, reset, num_unrolls):
"""Runs one optimization epoch."""
start = timer()
##sess.run(reset)  ## from evaluate.py: reset = [problem_reset, optimizer_reset]
for _ in xrange(num_unrolls):
cost = sess.run([cost_op] + ops)[0]
print(cost)
return timer() - start, cost

Ok so in their paper they only made the lstm learn to optimize for a fixed number of time steps i.e 100 iterations. So for them one epoch is training the lstm to learn to optimize for 100 steps. After the 100 steps or one epoch they reset and start over. In their paper they claim that for the number of steps the lstm is trained to optimize for, it gets better performance than Adam.
Now to your query, yes they reset Adam but always after 100 time steps. i.e number of optimization per epoch. After 100 epochs (each with 100 iterations) they average the loss which is then used to compare against the lstm. I hope this makes things clear.

@muneebshahid In the above code, the sess.run(reset) is inside the run_epoch function, so that reset would happen every 1 epoch, not every 100. Do you agree?

yes, after every epoch they reset. But in each epoch there are multiple optimization steps. i.e num_rolls


Anki: Darwin support

Motivation for this change
These are all changes needed to get Anki working on macOS. No changes to the Anki derivation are necessary. However, to run Anki correctly you must set DYLD_FRAMEWORK_PATH correctly until #20484 is fixed:
DYLD_FRAMEWORK_PATH=/System/Library/Frameworks `nix-build '<nixpkgs>' -A anki --no-out-link`/bin/anki

Things done

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

[ ] NixOS
[x] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This builds fine, but running it seems to require xcode. Is that expected?

@LnL7 It shouldn't require Xcode. Do you have any clues as to where it uses Xcode?

https://gist.github.com/9a33c428ab2748fcba50dd5727600bb4

@LnL7 see 7165b389084966b7a5c96e9b512b7312ae9c676d

Oh, I'll take a closer look at the error then.

gst-plugins-base does not build: ld complains about a missing framework (this is probably unrelated to this PR). After fixing it (patch below), I could build anki, but running it results in SIGSEGV.
OS version: Mac OS X 10.11.6 (15G1212)
--- a/pkgs/development/libraries/gstreamer/legacy/gst-plugins-base/default.nix
+++ b/pkgs/development/libraries/gstreamer/legacy/gst-plugins-base/default.nix
@@ -1,6 +1,7 @@
 { fetchurl, stdenv, pkgconfig, python, gstreamer, xorg, alsaLib, cdparanoia
 , libogg, libtheora, libvorbis, freetype, pango, liboil, glib, cairo, orc
 , libintlOrEmpty
+, darwin
 , # Whether to build no plugins that have external dependencies
   # (except the ALSA plugin).
   minimalDeps ? false
@@ -36,6 +37,8 @@ stdenv.mkDerivation rec {
         liboil ]
     # can't build cdparanoia on darwin
     ++ stdenv.lib.optional (!minimalDeps && !stdenv.isDarwin) cdparanoia
+    ++ stdenv.lib.optional stdenv.isDarwin
+       (with darwin.apple_sdk.frameworks; ApplicationServices)
     ++ libintlOrEmpty;

   NIX_CFLAGS_COMPILE = stdenv.lib.optionalString stdenv.isDarwin "-lintl";

@vbgl Are you on the latest master? http://hydra.nixos.org/build/46408265

After updating to master, gst-plugins-base indeed builds correctly. But anki still crashes before it starts.

@LnL7 Do you know which derivation requires Xcode to be installed? Most likely it is some bogus version check.

Oh right, for get about that. It's either fixed or I just did something strange when testing.


Fix E2E vagrant-libvirt image support

Is your feature request related to a problem? Please describe.

Libvirt images since 10.7 have consistently failed with our E2E pipeline. The images contain default dependencies that conflict with our k3s plugin.
conflicting dependencies excon (= 0.92.4) and excon (= 0.99.0)

As such I have been forced to manually close dependabot PRs like https://github.com/k3s-io/k3s/pull/7589
Describe the solution you'd like

Fix the E2E pipeline to support newer versions of the vagrant-libvirt base image.
Describe alternatives you've considered

Additional context

There is nothing to QA, this was a CI change only


[Blackhole bringup] Hang in transpose tests

This test:
TT_METAL_WATCHER=5 TT_METAL_DPRINT_CORES=all TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_metal/test_transpose_wh

passes after these commits: 9d208cc81f & 5212c7d862
but this test:
TT_METAL_WATCHER=5 TT_METAL_DPRINT_CORES=all TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_metal/test_transpose_hc

actually hits a runtime error:
                 Always | FATAL    | Watcher detected NOC error and stopped device: bad alignment in NOC transaction.
libc++abi: terminating due to uncaught exception of type std::runtime_error: TT_THROW @ ../tt_metal/impl/debug/watcher_server.cpp:367: tt::exception
info:
Watcher detected NOC error and stopped device: bad alignment in NOC transaction.

@abhullar-tt @aliuTT let me know if you can take a look at the second one

These other 2 transpose tests:
TT_METAL_WATCHER=5 TT_METAL_DPRINT_CORES=all TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_eager/ops/test_transpose_wh_single_core
TT_METAL_WATCHER=5 TT_METAL_DPRINT_CORES=all TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_eager/ops/test_transpose_wh_multi_core

are related from the hang here: #9941

TT_METAL_WATCHER=5 TT_METAL_DPRINT_CORES=all TT_METAL_SLOW_DISPATCH_MODE=1 ./build/test/tt_eager/ops/test_transpose_wh_multi_core

these tests are passing after applying the fix on abhullar/noc-header


Add Action.ToggleVisiblity to Input.Choice

Platform
What platform is your issue or question related to? (Delete other platforms).

.NET HTML
.NET WPF
Android
iOS
JavaScript
UWP

Author or host
Are you an author (like sending something to Outlook), or a host that is rendering your own cards? If host, please specify the corresponding host (app) name.
If you're an author, who are you sending cards to?
Version of SDK
What version are you using? Ex: NuGet 1.0.2, or latest main, etc...
Issue
Explain your issue. If you just have a question, please post on StackOverflow instead.

Adding toggle visibility to input. choice would allow for implementing skip patterns by toggling the visibility of questions that are only required based on the choice made.


Can't reset button group state

Current Behavior
With dashboard v.1.13 I was able to reset selected state from button group:
Example flow: https://discourse.nodered.org/t/button-group-selection-reset/91106/1
With v.1.17 I'm unable to do it so.
Expected Behavior
By sending empty msg.payload reset to unselected state
Steps To Reproduce
No response
Environment

Dashboard version: 1.17
Node-RED version: 4.0.2
Node.js version: 20
npm version:
Platform/OS:
Browser:

Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

@liulysk Your flow is sending {} while it should be sending [].
Try this:
[{"id":"2059f95a381c4ee9","type":"ui-button-group","z":"52793695ea0d6a4b","name":"SDSR/SODR/SODC","group":"82978573a448c0a7","order":5,"width":"3","height":1,"label":"","className":"","rounded":true,"useThemeColors":true,"passthru":false,"options":[{"label":"SDSR","icon":"","value":"{\"message\":\"SDSR\"}","valueType":"json","color":"#ff6666"},{"label":"SODR","icon":"","value":"{\"message\":\"SODR\"}","valueType":"json","color":"#009999"},{"label":"SODC|ASAP","icon":"","value":"{\"message\":\"SODC\",\"type\":\"ASAP\"}","valueType":"json","color":"#009933"},{"label":"|CLAY","icon":"","value":"{\"message\":\"SODC\",\"type\":\"CLAY\"}","valueType":"json","color":"#999999"}],"topic":"topic","topicType":"msg","x":240,"y":160,"wires":[["1a9fdb1f451fa462"]]},{"id":"1a9fdb1f451fa462","type":"trigger","z":"52793695ea0d6a4b","name":"","op1":"","op2":"[]","op1type":"pay","op2type":"json","duration":"500","extend":false,"overrideDelay":false,"units":"ms","reset":"","bytopic":"all","topic":"topic","outputs":1,"x":380,"y":110,"wires":[["2059f95a381c4ee9"]]},{"id":"82978573a448c0a7","type":"ui-group","name":"SODE Definition","page":"bad61fde43591b8a","width":"3","height":"1","order":1,"showTitle":true,"className":"","visible":true,"disabled":"false"},{"id":"bad61fde43591b8a","type":"ui-page","name":"Splitex","ui":"5c721863a3b3e0e8","path":"/splitex","icon":"home","layout":"grid","theme":"66ef48d50fdc6f7f","order":5,"className":"","visible":true,"disabled":"false"},{"id":"5c721863a3b3e0e8","type":"ui-base","name":"My Dashboard","path":"/dashboard","appIcon":"","includeClientData":true,"acceptsClientConfig":["ui-notification","ui-control"],"showPathInSidebar":false,"showPageTitle":true,"navigationStyle":"default","titleBarStyle":"default"},{"id":"66ef48d50fdc6f7f","type":"ui-theme","name":"Default With Blue","colors":{"surface":"#ffffff","primary":"#0094ce","bgPage":"#eeeeee","groupBg":"#ffffff","groupOutline":"#cccccc"},"sizes":{"pagePadding":"12px","groupGap":"12px","groupBorderRadius":"4px","widgetGap":"12px"}}]


142-additional-tests-to-increase-code-coverage

more tests added

Tests looks good and the tests cases are well-structured and cover different cases! Good job


Support importing typedefs

I get this error. The import syntax is valid in jsdoc.
Error: ERROR: Unable to parse a tag's type expression for source file ~/core/bus.js in line 6 with tag title "param" and text "{import('nanobus')} NanoBus": Invalid type expression "import('nanobus')": Expected "!", "=", "?", "[]", "|", or end of input but "(" found.

/**
 * Main event bus.
 *
 * @name Bus
 * @param {import('nanobus')} NanoBus
 * @returns {import('nanobus')}
 */
module.exports = function(NanoBus) {
	return NanoBus;
};

Ref: https://github.com/onury/jsdoc-x/issues/12

You've already opened an issue @ jsdoc-x for this. Closing this one.


ReferenceError: Stats is not defined

Hi there!. I am trying to use this module in my javascript. However I try to add this module using the followings in my html file.
<script src="https://mrdoob.github.io/stats.js/build/stats.module.js"></script>
or
<script src="/js/stats.min.js"></script>
or
<script src="/js/stats.module.js"></script>

However, they all gave me error says ReferenceError: Stats is not defined and there is an error also occured saying that Uncaught SyntaxError: Unexpected token 'export when I try to use the stats.module.js file.
Anybody knows what the problem is?

Try this, it works for me:
First
npm install stats-js
Then
import Stats from 'stats-js';
And then proceed as usual...
const stats = new Stats();


Don't overwrite params, and use params in Layer.ArcGISCache

See http://lists.osgeo.org/pipermail/openlayers-users/2012-February/024263.html

Excellent. Please merge.


If the data records were accidentally deleted, what should I do?

D:\conda_env\chucansvn\lib\site-packages\wagtail\query.py:565: RuntimeWarning: Specific versions of the following items could not be found. This is most likely because a da
tabase migration has removed the relevant table or record since the item was created:
[{'id': 9, 'title': 'blog_index_page', 'type': <ContentType: blog | blog index page>}, {'id': 7, 'title': 'Our Blog', 'type': <ContentType: blog | blog index page>}, {'id':
8, 'title': 'blogtitle', 'type': <ContentType: blog | blog index page>}]
If the data records were accidentally deleted, what should I do?

Hi @maya413 - please use Stack Overflow or the #support channel in the Wagtail Slack for support queries.


convert repo to cargo workspace

This should make it easier to add new crates to the repo (e.g. no need to add CI jobs for each one), and just generally makes more sense than stuffing everything that is not quiche itself under tools/.
Pretty much all the changes are related to build scripts and related things. All the actual code is just moved around.

hard to review, if CI passes I hope that covers all bases :D

So, I noticed that the doc tests were not being run, however this appears to have been a problem for a while (unrelated to this PR), but I fixed it by adding an additional cargo test --doc step because apparently this is a known cargo problem (https://github.com/rust-lang/cargo/issues/6669), that is you can't run examples and doc tests in the same command.


(SERVER-252) Add acceptance tests for irb and ruby subcommands

Without this patch there are no acceptance level tests for the ruby and irb
subcommands as they relate to the gem subcommand.  This is a problem because
we need to ensure these commands behave as expected, particularly when the
gem subcommand is used to install third party libraries.
This patch addresses the problem by installing the hiera-eyaml gem and then
checking that the ruby and irb subcommand can require 'eyaml'.
This patch also adds basic testing of the behavior of GEM_HOME and FOO_DEBUG
with regard to the irb and ruby subcommands in addition to ensuring require 'puppet' works in both subcommands.

Addressed @camlow325's comment about pe-puppetserver not being a thing.

:+1:

:+1: other than gem_utils

gem_utils has been fixed

:+1:

Looks like the related PR has been merged into stable, but not merged up to master yet.  I took a quick swing at the merge-up and there are conflicts, so I'm punting it for now.  Happy to try again if I get back around to this before anyone else does.

@cprice404 This PR was "special" in that we weren't sure what the merge up process was so we decided to cherry-pick the commits for SERVER-262, which affected the subcommand behavior from stable to master.  This is likely the cause of your merge conflicts, at which point I'm happy to help.  It should just be a matter of making sure JARS_NO_REQUIRE is handled as expected in stable (not present) and master (set to "false") and the acceptance tests in each branch reflect that expected behavior.


Add do_not_reactivate option to persist triages from triage-less scanners

Explained in https://github.com/DefectDojo/django-DefectDojo/issues/6892

@Gby56 this makes sense to me. I think it needs a little extra documentation to make it clear though. Copying the text from the attached issues and putting that somewhere in the docs would mostly likely be enough. Might be a good idea to add a hotlink within the help text to the location in the docs. What are your thoughts on that?

Completely agree, I'll get some more documentation around it and link to it in the helper message, it's not an easy concept to grasp

I'm not quite sure how to get a link with mark_safe into the help_text... I'd like to point to the docs website to have the full context

I just realized that I cannot easily implement do_not_reactivate in the importer, I need the reimporter's deduplication to be able to instantly mark the existing findings as untouched. The normal importer does deduplication out-of-band I think, and it should be taken care of in there, which is more complex

Adding some notes to explain maybe why a finding was not reactivated.

Okay, the get_import_meta_data_from_dict() function calls were broken because of my new variable do_not_reactivate, I'm not a fan of python unpacking and usually I work with dicts a lot, I think this should have fixed the unit tests :)

Hi @Gby56 there are a handful of tests failing here. Likely an issue of there being a new element on the page that throughs off the xpath of other elements

@Maffooch I think the integration tests failing are not from my changes, all of them are 404s on random stuff, no clue how to debug that...
{'level': 'SEVERE', 'message': 'http://nginx:8080/static/dojo/img/zoom-in.cur - Failed to load resource: the server responded with a status of 404 (Not Found)', 'source': 'network', 'timestamp':<PHONE_NUMBER>057}
{'level': 'SEVERE', 'message': 'http://nginx:8080/static/%20jquery.hotkeys/jquery.hotkeys.js - Failed to load resource: the server responded with a status of 404 (Not Found)', 'source': 'network', 'timestamp':<PHONE_NUMBER>671}

On my local dev machine btw

God... it was the black linter, it's formatting my html file when saving, and it added a bunch of spaces

@Maffooch all green !


Error while adding WSDL service Asp.net Core 3.1 web api

I am trying to add a service in a .net core 3.1 application .I share my steps with screen shots.
The following is from .csproj
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <WCFMetadata Include="Connected Services" />
  </ItemGroup>

</Project>

Step 1

Step 2

Step 3

Step 4

Step 5

[Edited by gewarren to add document details]

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

ID: 0e89651a-5ad9-c3f9-146f-8d87b87d9e11
Version Independent ID: 85c0e55f-abc0-3b2d-409a-06042b1f3ebb
Content: Add WCF Web Service Reference - .NET Core
Content Source: docs/core/additional-tools/wcf-web-service-reference-guide.md
Product: dotnet-core
GitHub Login: @dasetser
Microsoft Alias: dotnetcontent

@kuntalbose Have you tried using the dotnet-svcutil command instead? Just a thought.
https://docs.microsoft.com/en-us/dotnet/core/additional-tools/dotnet-svcutil-guide?tabs=dotnetsvcutil2x

@gewarren Don't forget to remove the not triaged label when categorizing 😄

@kuntalbose This looks like a bug in the tool where it doesn't work if you only have the .NET Core 3.x SDK installed. We'll work on fixing it, but for now I would suggest installing the .NET Core 2.1 SDK on your machine, which should allow this to run.

@dasetser Thanks for your suggestion .I already report here .If I install 2.1 SDK on my local machine to do this ,is it need to install in server?If so then its not help full for me .Because application hosted in a shared hosting and I have no access.

@kuntalbose No, you don't need to install it on the server too. You can continue to use .NET Core 3.1 on your client app as well. The only reason to install the 2.1 SDK is because that's what the tool needs to run. It won't impact the proxy that the tool generates.

Hi @gewarren I tried with bellow code
svcutil.exe /t:code /d:C:\Users\XXXX\Desktop\SOAP\WebApplication1\WebApplication1  http://ws.jobdiva.com/axis2/services/BIData?wsdl
And its generate the code file (BIData.zip) and required methods when when I call a method bellow error occurred

Can you please help me?whats going wrong

@kuntalbose I see you asked the question in the WCF repo, which is a better place to ask the question.  I will go ahead and close this documentation issue.


local install and local upgrade

This PR moves unstable install and unstable upgrade to the local namespace and adds an optional env var REBAR3_ERL_ARGS to allow setting custom VM args when running rebar3.

Doc updates will (possibly) be needed for this on the website.


Percent symbol '%' can be inserted as a property name

Describe the bug
When using the Refitter Source Generator, if a percent symbol is used as a property name in the OpenAPI spec, that same percent symbol will be inserted into the name of the property in the generated C#, violating C# property naming rules.

Screenshots

OpenAPI Specifications
https://api.percipio.com/reporting/swagger.json

@XeClutch Thanks for taking the time to report this. I'm surprised but the OpenAPI spec example provided is valid. I'm not sure how to handle such a property name but I'll see what I can do

@all-contributors please add @XeClutch for bugs

This is a tough one as I rely completely on NSwag for generating the contracts/models and this needs to be addressed in NSwag instead of Refitter.

This is a tough one as I rely completely on NSwag for generating the contracts/models and this needs to be addressed in NSwag instead of Refitter.

Scratch that... we can fix this from Refitter as we use a custom property name generator that addresses this kind of problem.
@XeClutch I have a fix on the way where the property % ofVideoOrBook will be generated as public string Percent_ofVideoOrBook {get; set; }. We already handle spaces by replacing them with an underscore, and changing that breaks it for other users


the "Profile Import" area should already have the correct width before selecting an address

When creating a new wallet, the width for "Profile import" and "Address to interact with" should not move when selecting the first address.

Select the address, the width of the "Profile import" area will be increased.
Deselect address again, area will be reduced in width

Even if no address has been selected yet, an appropriate width should already be specified.
There is already an empty area reserved for "Profile Import" and the widening is annoying, although the difference is not that big.

Video: https://share.getcloudapp.com/WnuBBqL4

Fixed.


Add Seldon Bot

This is an AI bot that can generate questions and invest in markets.

LGTM, thanks!


Add MATH1342 textbook.

Source: https://www.scribd.com/document/295270778

Thanks for finding this.


Update DatbaseUserProvider.php to add missing method

The getModel method was missing and caused issues with some additional packages.

What packages in particular is this an issue with?

wildside/userstamps was the one that threw it up initially but I would have
to go back and check on the other ones.
On 27 March 2017 at 12:14, Steve Bauman<EMAIL_ADDRESS>wrote:

What packages in particular is this an issue with?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Adldap2/Adldap2-Laravel/pull/287#issuecomment-289423719,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmgpPpIEcGav7vN-EuXVdsYOim2eUyuks5rp5n5gaJpZM4Mp_6R
.

Has this code been removed from master?

@designvoid Yes it was. I implemented a __call method that will call upon the underlying EloquentUserProvider for missing methods.
This is actually an issue with that package, not Adldap2.
They're assuming the method is there, when it adheres to no contract:
https://github.com/laravel/framework/blob/5.5/src/Illuminate/Contracts/Auth/UserProvider.php
https://github.com/WildSideUK/Laravel-Userstamps/blob/master/src/Userstamps.php#L110-L122


Generate Template link and blob container dropdown fix

As part of this PR 3 bugs have been fixed.

generate template link bugs.
In the 3 page as well now latest sku recommendation are fetched(earlier the recommended sku was displayed based on older sku recommendation) and a loading... text is displayed until the latest sku recommendation are fetched . Doing this change fixed both of the bugs related to generate template link.

blob container dropdown bug.
There was another bug , the ARM template was getting uploaded to the first blob container in the dropdown. Added an ondropdownchange event to fix the same.

ADO bug links-
https://msdata.visualstudio.com/Database Systems/_workitems/edit/3044065
https://msdata.visualstudio.com/Database Systems/_workitems/edit/3044076

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.006%) to 41.755%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

src/sql/workbench/services/connection/browser/connectionDialogWidget.ts
1
73.44%

extensions/notebook/src/book/bookTreeView.ts
1
36.91%

extensions/notebook/src/dialog/configurePython/configurePythonWizard.ts
1
46.46%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
30825

Relevant Lines:
69082

💛  - Coveralls

Looks good overall, I have added a comment, please take the change.

done


Error while installing wrapper in Rstudio

Hi, noticed an error while installing the wrapper, I believe it is because the authenticate_v1_0 was renamed to authenticate_v1_x?
Error: package or namespace load failed for ‘mysportsfeedsR’ in namespaceExport(ns, exports):
undefined exports: authenticate_v1_0
Error: loading failed
Execution halted
ERROR: loading failed

removing ‘/Library/Frameworks/R.framework/Versions/3.4/Resources/library/mysportsfeedsR’
Installation failed: Command failed (1)

Thanks for that @BobOscarHappyApple!  Just corrected for the name change.


[5.10] Create SwiftSyntax510 module for version indication

Cherry-pick of #2283
Resolved #2279

@swift-ci Please test


empty-line-between-blocks sass issue

Running into the same error as #447 (included below), except this is on version 1.7.0, which was after the original fix.
/Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:67
    if (previous.is('space') || previous.is('declarationDelimiter')) {
                 ^

TypeError: previous.is is not a function
    at findNearestReturnSass (/Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:67:18)
    at findNearestReturnSass (/Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:82:14)
    at /Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:175:27
    at Node.forEach (/Users/danpurdy/workspace/sass-lint/node_modules/gonzales-pe/lib/node/basic-node.js:1:2053)
    at /Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:155:16
    at RootNode.traverseByType (/Users/danpurdy/workspace/sass-lint/node_modules/gonzales-pe/lib/node/root-node.js:1:1739)
    at Object.module.exports.detect (/Users/danpurdy/workspace/sass-lint/lib/rules/empty-line-between-blocks.js:118:9)
    at /Users/danpurdy/workspace/sass-lint/index.js:44:27
    at Array.forEach (native)
    at Function.sassLint.lintText (/Users/danpurdy/workspace/sass-lint/index.js:43:11)

It seems to fail following the @include line here:
.foo
  @include clearfix
  .bar
    width: 32%

The clearfix mixin looks like:
@mixin clearfix
  zoom: 1

  &:before, &:after
    content: ""
    display: table

  &:after
    clear: both

Changing to this (empty line after @include) fixed the error:
.foo
  @include clearfix

  .bar
    width: 32%

Thanks for the report, I've managed to replicated.
@bgriffith wanna handle this one as you went through this recently?
The issue is in this case parent.content[i - 1] is a string ('x' from 'clearfix') and so it does pass the checks but doesn't have methods attached as it's not a node obviously.
There are also some other failing cases as far as i can see.
if you include a new block directly after an empty block
.foo
  .bar
    color: red

no warning will be raised about the lack of space between foo and bar.


add: ipa tree types

Adds the Stateless Tree types. May get refactored while implementing. Tried to make the most meaningful function names to avoid confusion.

@agnxsh
I think this should be better if shifted from inside the eth-verkle/tree/ipa to eth-verkle/ipa
Since the part we are going to add, helps in statelessness and not exactly core tree operation.
What's your suggestion ?

@agnxsh I think this should be better if shifted from inside the eth-verkle/tree/ipa to eth-verkle/ipa Since the part we are going to add, helps in statelessness and not exactly core tree operation.
What's your suggestion ?

okay makes sense

looks ok to merge

Plan to finish this pass by pass in future, will rebase and merge once #22 gets merged.

Ready for review, 1 verkle error file consisting of verkle error types, maybe needed in future for integration. Tests pending, will do in next passes, and subsequent fixes whenever needed.


Module '"next-intl/server"' has no exported member 'getRequestConfig'

Description
I use Next 13.5.3
I follow this guide - https://next-intl-docs.vercel.app/docs/getting-started/app-router-server-components
When I paste this to my i18n.ts (in root directory)
import {getRequestConfig} from 'next-intl/server';

export default getRequestConfig(async ({locale}) => ({
  messages: (await import(`./messages/${locale}.json`)).default
}));

I got this error
Module '"next-intl/server"' has no exported member 'getRequestConfig'
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://codesandbox.io/p/sandbox/i18n-thzc9v
Reproduction description
Steps to reproduce:

Open codesandbox
Click on VS conde in top right corner
See error in i18n.ts

Expected behaviour
I wait no error
But got an error

Any chance next-intl got installed incorrectly?
When I run your example I also get this error:

Seems like your middleware.ts example is empty.
I'll move this to a discussion since it seems to be a usage question.


Arg macro to fn

Simple port from macro to fn, and addition of first example scenario.
You can run examples like this:
cargo test --example scenarios

Codecov Report

Merging #88 (2fe253a) into dev (04e6226) will decrease coverage by 0.18%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev      #88      +/-   ##
==========================================
- Coverage   54.98%   54.79%   -0.19%
==========================================
  Files          34       34
  Lines        6718     6741      +23
==========================================
  Hits         3694     3694
- Misses       3024     3047      +23

Impacted Files
Coverage Δ

cli/src/lib.rs
0.00% <0.00%> (ø)

cli/src/main.rs
0.00% <0.00%> (ø)

cli/src/regtest.rs
0.00% <0.00%> (ø)

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


Add XNLI train set

I added the train set that was built using the translated MNLI.
Now you can load the dataset specifying one language:
from datasets import load_dataset

xnli_en = load_dataset("xnli", "en")
print(xnli_en["train"][0])
# {'hypothesis': 'Product and geography are what make cream skimming work .', 'label': 1, 'premise': 'Conceptually cream skimming has two basic dimensions - product and geography .'}
print(xnli_en["test"][0])
# {'hypothesis': 'I havent spoken to him again.', 'label': 2, 'premise': "Well, I wasn't even thinking about that, but I was so frustrated, and, I ended up talking to him again."}

Cc @sgugger

Hi! Thanks for adding the translated MNLI! Do you know what translations system / model you used when you created the datasets in the other languages?

The training data is not from translators.

What makes you think that ? The paper litteraly says

we hire translators to translate the resulting sentences into 15 languages using the One Hour Translation platform.

However the annotators only did test and validation sets, as this was what
in the paper: “we construct an evaluation set for XLU by extending the
development and test sets of the Multi-Genre Natural Language Inference
Corpus (MultiNLI) to 15 languages".
On Thu, Jun 9, 2022 at 10:35 AM Quentin Lhoest @.***>
wrote:

The training data is not from translators.
What makes you think that ? The paper litteraly says
we hire translators to translate the resulting sentences into 15 languages
using the One Hour Translation platform.
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/datasets/pull/781#issuecomment-1151202195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKLKWFZOQPLK4WSKFRLW6DVOH6LLANCNFSM4TE67NMQ
.
You are receiving this because you commented.Message ID:
@.***>


Due to some ugly inheritance you must use values with great care. In …

…equals it must use entrySet() due to some very ugly inheritance.
@bratseth PR
This is a mess... With this interface it can not be both convenient and fast.
Is there something that we can do to this mess....

or @bjorncs

or @lesters


Create mockup for landing page

Mockup includes the landing page, NavBar and Footer.

Moving issue to source code repo.


CLOUD-825 - Use community helm chart repo for installing MinIO

CHANGE DESCRIPTION
Problem:
https://helm.min.io/ is removed so we need to fix our tests to use something else.
Solution:
Since official docs use operator+tenants mode we decided to use community helm chart in standalone mode for tests (which is the same what we had before).
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?
[ ] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are the manifests (crd/bundle) regenerated if needed?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1527/commits/a6144e6228ca5b5dfe8e1c1ece073098f3a2db60
image: perconalab/percona-xtradb-cluster-operator:PR-1527-a6144e62


Bundle not starting after Server Restart | AEM 6.1 | Sightly

23.03.2016 08:07:05.683 ERROR [qtp805710203-5004] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle code-bundle [499]: Unable to resolve 499.0: missing requirement [499.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.sightly)(version>=2.2.0)(!(version>=3.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle code-bundle [499]: Unable to resolve 499.0: missing requirement [499.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.cq.sightly)(version>=2.2.0)(!(version>=3.0.0)))

This looks like an issue w your projects sightly dependency. What makes you believe this has something to do a acs commons?

As it is not happening in all the environments. We believe that it may be relates to acs commons.

Why do you believe that?

May be i m wrong :)
Could you please guide me, where should i Put this issue ?

Hi Nikhil,
We also have this issue occasionally.
To resolve it, we stop the server, navigate to following path:
\crx-quickstart\launchpad\felix\bundle21\data
and delete the digraph file.
We learned from Adobe that this file somehow retains some dependencies between bundles, so by removing the file, the issue should be solved.

I would suggest working with daycare before deleting any internal files.

@justinedelson This is a solution that was communicated to us by Adobe Managed services

@justinedelson: The solution is not working for us,
Raised the concern with the daycare. :)
Thanks guys. Will post here once daycare provide the solution.

Hi nikhil-gupta89,
We are facing same issue in my current AEM 6.1 project. Can you tell me if you got an update from Daycare on the solution?
Thanks,
Krass

Hi @krassib,
Daycare team provided the solution by deleting the ''org.eclipse.equinox.region" bundle from the felix and then restart the server and then redeploy your code bundle.
We learned from Adobe that this bundle has some dependency with eclipse and should not be in AEM6.1, it was meant for AEM 6.2. But somehow it got introduced in this version.
Hope this will work for you too.
Thanks,
Nikhil

Hi @nikhil-gupta89,
Thanks for the quick reply. I really appreciate it!
Do you remember during your research if the Geometrixx content was involved? I.e. did you have to have Geometrixx app and content in order to make it work? I am asking because we are facing some dependency on it. If the Geometrixx is present  and then uninstalled we don't see the bundle issue.
Thanks again,
Krass

@krassib this issue (aside from having nothing to do with ACS AEM Commons and so probably shouldn't be discussed further here) is non-deterministic. It has nothing to do with Geometrixx. It is a bug in the Equinox Region bundle and could appear with really any combination of installed packages.

This worked (removing the eclipse bundle).
However, it is a bit strange that the issue did present itself on environments where we had: 1dispatcher, 1publisher, 1author
The issue only showed up where we had: 4dispatchers, 4publishers, 1 author.
I'm still going to remove the eclipse patch from the environments with 1disptcher/1publisher to be consistent.
But I'm curious to know if there is something about the eclipse bundle that would cause it to work on a single instance setup and fail on a multiple instance setup?
Should this not be addressed in a SP?
Thanks


Feature: Implement Cookie Privacy Policy Page

This pull request introduces a new Cookie Privacy Policy page to the CryptoTracker application. The following changes have been made:
New Page: Created a dedicated Cookie Policy page with comprehensive information about how cookies are used on the platform, including details on user consent and cookie management.
Routing: Updated the App component to include routing for the Cookie Policy page, making it accessible from the main application.
Footer Update: Modified the Footer component to include a link to the new Cookie Policy page for easy access.
Styling: Added styling for the Cookie Policy page to ensure consistency with the existing design of the application.
'fixed:#202'  @vanshchauhan21
https://github.com/user-attachments/assets/7beceed1-1dbe-4161-846b-309c7ca36e88

This pull request introduces a new Cookie Privacy Policy page to the CryptoTracker application. The following changes have been made:
New Page: Created a dedicated Cookie Policy page with comprehensive information about how cookies are used on the platform, including details on user consent and cookie management. Routing: Updated the App component to include routing for the Cookie Policy page, making it accessible from the main application. Footer Update: Modified the Footer component to include a link to the new Cookie Policy page for easy access. Styling: Added styling for the Cookie Policy page to ensure consistency with the existing design of the application.
'fixed:#202' @vanshchauhan21
coooo.mp4

Bro I already said to you don't use (:) instead of this you can use 'fixed #202'
Don't do it again please


Added a preview function for screenshot purposes

I was taking an online class over the summer using Zulip and many of us found ourselves using this service to quickly draw a commutative diagram to share with others. Having a mode without borders would allow for nicer screenshots. One work item remaining before merging: this feature needs an icon. It seems like your icons were made in illustrator, which I don't have, so would you be willing to create one for me?

This is building on my system, no idea why prettier is giving different results on mine vs the CI server.

Sorry, but I'm unwilling to add this "feature". I've explained many times that this is not a tool for taking screenshots of diagrams, because the rendering of this tool is meant to be a rough approximation only. This is to help people write LaTeX code, so that LaTeX may render the diagram.


Request to delete repo

Hi,
Could I please request deletion of an old deprecated repo - https://github.com/ministryofjustice/yjaf-csppi
Regards,
Javaid.

Hi @javaidarshadnec I'll remove the collaborators before we archive the repo.

@javaidarshadnec the repo has now been archived. Any issues please let us know.


[API] Building a CRUD API with the Dapper ORM in ASP.NET Core

Formatting and structure checks

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

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

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

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

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

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

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

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

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

Grammar & plagiarism checks

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

Technical checks

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

This closes #4576

@section-engineering-education/peer-reviewers
is anyone available to jump on this PR ASAP.
Thank you

Hi, @paulodhiambo . Thanks for the review. I have made the requested changes and pushed.

Hello @Amoh-writer.
Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept.
Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content.
Be sure to see our resources page to see more info on plagiarism and what is considered as such.
[API] Building a CRUD API with the Dapper ORM in ASP.NET Core #5201 Copyleaks Report.pdf

Hi @Kayere . Thanks for the review. If the attached report is anything to go by, it shows that a considerable amount of the similarities(about 3%) point to the issue that should be closed by this PR. This is rightly so as I was required to provide an ntroduction to the article in the issue and this was the same intro used in the article itself.
The other similarities came from the code snippets. More specifically, the similarities came from the imports in the code snippets. It is very common for this to occur if i happen to use the same packages that someone else used in their project. The actual code itself, i.e. everything asides imports, had little to no similarities to other references. I sincerely hope the plagiarism check could be reveis

reviewer pinged via slack as well @paulodhiambo

Hello @olumidayy please remove the file  .vscode/settings.json

Done @Kayere .

@paulohiamdo we usually do not need to run TWO plagiarism checks unless the 1st ones was over 30% (typically).
|
Especially if some were boilerplate code.

@paulodhiambo can we get a status on this PR - if any more edits are needed.
WE WILL be closing the PR 👍


gsw not supported

We tried to localize swiss german (gsw-CH) unfortuately this language is not supported by l10ns as it is not part of cldr-data package. Switching to cldr-data-full package might solve that issue. Or maybe it could be installed if needed to prevent long installation.
fyi: Even with cldr-data-full, we will still have issues because there are some lacking data for gsw on cldr site. We opened a ticket at http://unicode.org/cldr/trac/ticket/9864 to add those data, which was accepted last week. It is scheduled to be fixed at March 15 2017. Until then, as a workaround we might go with a script copying the missing data from cldr-data-full and/or enhancing them with data on our own until the cldr ticket is solved.

Closed as opened with company account. Opened new issue as replacement: #140


refactor: improve psbt ui

Try out this version of the Hiro Wallet - download extension builds.

This PR got a bit large in refactoring the inscription types and collectibles code along with improving the PSBT UI. It was needed as I confronted trying to reuse code for the inscription query on the PSBT. However, the focus of this PR is to improve the PSBT UI. For v2, I am rendering a simple and advanced view. Simple shows the inputs/outputs separately, and does show if an input contains an inscription. The advanced view renders the object as is scene currently in the UI.
Setup tx:

Inputs:

Outputs:

View toggle:

Hoping to get feedback on this version. We can either move forward with this if there are other priorities, or I can start to match the inputs and outputs to achieve more of what the designs show.

@mica000 for tom, for the record, I think I can achieve the designs you already did but I just need to rework how I built this. If you want to make changes, you can, but I do think I can pair the inputs/outputs together the way you are showing them currently.

@markmhx any thoughts on if this is ok to merge into dev or should I hide the new UI work until I match the inputs/outputs? It would be easy just to show the 'advanced view' like it is currently until we are ready.

@kyranjamie I will add tests for getting the out script address in my next PR. That was one comment I didn't get to include here. I moved the functions, bit didn't get a chance to add the tests yet.

@fbwoolf merging into dev works for me 💪


 U: .

 U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2666/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
13m 49s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
master passed

+0 :ok:
refguide
3m 57s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  2s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+0 :ok:
refguide
4m  2s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 17s
The patch does not generate ASF License warnings.

32m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2666/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2666

Optional Tests
dupname asflicense refguide

uname
Linux 73416a5dd1e2 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 300b0a650f

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2666/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2666/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2666/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


[Feat]: Add a main page

Description
Add a main page similar to the daily.dev docs

Solution
similar to this:
https://docs.daily.dev/
Anything else?
No response
Code of Conduct

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

done by #432


⚠ Secret Website 3 has degraded performance

In 7e078c3, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 24877 ms

Resolved: Secret Website 3 performance has improved in a99fccc.


Remove some loops over vertical column

This PR removes some real_center_indices loops. A step towards #887.

bors r+


use nullable OpenAPI property to determine nullability

Basic attempt at using nullable instead of required to determine nullability. Fixes #359
My use case only deals with querying data so I removed required, however it may be still relevant when creating input/mutation types.

Thanks for filing the issue and the pull request! This looks good to me! Can you also sign off your commits?
git rebase HEAD~5 --signoff

In addition to this, we will also need to add some test cases and fix all the old ones. I can take a crack at this if you do not have the time. Just let me know!

Oh sure I'll sign off on them from my work machine tomorrow. I probably won't have the time to update the test cases in the next few days, this patch has unblocked some pressing work I'm perusing. I'd appreciate the help with the test suite.

There I believe those are now signed off. Apologies for the delay.

Thanks for getting back to me! I think there are still a few commits that need to be signed off, name e600a79, 7c84104, and 1d84f1e.
And I'll get started looking into the test cases!

After doing some more research, I wonder if the proposed change is too simple.
I'm still new to the conversation but it seems that historically, there seems to be a lot of debate over how nullability should be conveyed, either using nullable or specifying that the type can be null. This debate is quite intricate and can be confusing. From the surveys we've performed, it's clear that not all OAS are created the same (i.e. are of the same quality), so I doubt that everyone is using these properties consistently and properly. With the current changes, we are not taking these alternatives into consideration.
Another one of my concerns stems from the fact that the OAS by default assumes that nullable is set to false. This PR follows that precedent but with the current changes, this will break a lot of schemas due to cyclical relationships. It would require a lot of work to check for cyclical relationships and modify the schema to reflect that.
Arguably, it will be much easier and more functional if we just assume all fields to be nullable.
I was thinking we can check if nullable is explicitly set to false to create non-null fields, but I wonder if this is idiosyncratic, given that OAS assumes it to be set to false.
In any case, I am proposing that we remove the required as originally intended but we do not replace it with a nullable check. Perhaps we can check for nullable is explicitly set to false to create non-null fields but that could be a future enhancement. Thoughts?

nullable: true is the OpenAPI 3.0 and prior way of expressing nullability.
type: [string, whatever, null] is the OpenAPI 3.1 and forward way.
This is a result of the replacing the prior "it's pretty much JSONSchema" schema language with full-fat JSONSchema.
I'm adverse to the idea of not handling this according to the spec. IMO nullability is important to model as accurately as possible.
In my use case for example the generated schema is used to provide documentation to users via GraphQL Playground & GraphQL Voyager. I wouldn't want consumers of my API handling nulls everywhere thinking that every field is actually nullable.
Granted, my use case is pretty different than the typical user of this package, I'm not using the openapi-to-graphql server just the schema generator.
Aside from that, making every field nullable allows users to hit APIs with invalid null fields rather than catching them during the GQL mutation validation. Not the end of the world, but notable.
I wouldn't want to make this opt-in by explicitly setting nullable: false since it wouldn't be something the average OpenAPI would typically do. Making this change across all the teams my OpenAPI is composed from would be a colossal task.
Can you link to a public example of an organization who's not using nullable as they should, leading to the unintentionally infinitely recursively schemas you mention?
Perhaps the specs afflicted with this issue are older or out of date specifications and putting this behavior behind an OpenAPI version check is all that would be needed.
If there's no other reasonable way, than I'd support making this behavior opt-in via a flag.

@nlundquist You make a lot of convincing points.

Can you link to a public example of an organization who's not using nullable as they should, leading to the unintentionally infinitely recursively schemas you mention? Perhaps the specs afflicted with this issue are older or out of date specifications and putting this behavior behind an OpenAPI version check is all that would be needed.

I was originally concerned because a lot of the tests are now currently broken but after some careful inspection, I believe that these are errors with the example OASs that I created, which I blame on my own inexperience.
To verify that OtG can still successfully wrap the vast majority of OASs in GraphQL, I reran the APIs.guru evaluation. Here are my findings...
Current behavior:
----------------------
Overall results:
Assessed APIs: 1885
Successes: 1626
  with no warnings: 115
Errors: 259
----------------------
Warnings breakdown:
{
  "MISSING_RESPONSE_SCHEMA": 6352,
  "OBJECT_MISSING_PROPERTIES": 1166,
  "OAUTH_SECURITY_SCHEME": 1299,
  "UNKNOWN_TARGET_TYPE": 372,
  "MULTIPLE_RESPONSES": 9181,
  "UNRESOLVABLE_SCHEMA": 126,
  "DUPLICATE_FIELD_NAME": 11,
  "DUPLICATE_OPERATIONID": 1
}

Proposed non-nullable behavior:
----------------------
Overall results:
Assessed APIs: 1885
Successes: 1626
  with no warnings: 108
Errors: 259
----------------------
Warnings breakdown:
{
  "MISSING_RESPONSE_SCHEMA": 6352,
  "OBJECT_MISSING_PROPERTIES": 1162,
  "OAUTH_SECURITY_SCHEME": 1299,
  "UNRESOLVABLE_SCHEMA": 1484,
  "UNKNOWN_TARGET_TYPE": 359,
  "MULTIPLE_RESPONSES": 9181,
  "DUPLICATE_FIELD_NAME": 11,
  "DUPLICATE_OPERATIONID": 1
}

So it seems that we are still able to successfully wrap the same number of OASs from the wild. There are differences in the warnings but I wouldn't read into them too much because this PR needs to be rebased (for example, you fixed the .properties bug which is related to the UNRESOLVABLE_SCHEMA warning).
This makes me more confident that this is a change that we can accept but I am still wary about some its implications, for example with input object types. I've asked my colleague @ErikWittern to give his opinion on it. I'd like to hear his opinions before moving further with this PR.
If we feel that my concerns do hold some water, then I think we should add this as an opt-in option as your suggested or wrap it along with the strict option.

Okay, I've heard back from @ErikWittern and we're going to go through with this change. I still need to make a lot of changes to the tests so this will take some time.

Why am I being harassed to keep a branch current that a maintainer has said he would be need revisit?

@nlundquist Sorry for the spam. I do not know why this is happening either. I have reached out to a number of people to ask them to stop the ibm-ci-bot spam and I am currently waiting for them to get back to me. If it is easier, I can make a copy of your branch and perhaps you will stop getting spammed.


Add an option to preserve merge commits

I have a repo where we rebase feature branches on master and then merge them into it without fast-forwarding once they are finished. This makes the commit log look like this.
When trying to remove all the traces of a specific directory from the repo via GitRocketFilter, I've discovered that it unconditionally removes merge commits if it considers them empty. Here's the culprit: https://github.com/xoofx/GitRocketFilter/blob/ad205815153ed0538e3afe04f2c5e6473f4f3812/src/RocketFilterApp.cs#L354-L360
I see the logic behind this, but in this particular case it produces a lot of false positives and removes the commits I'd like to preserve. So I'd like to suggest adding a new --preserve-merge-commits option that, if enabled, would add an additional check for the parent count and only allow dropping an empty commit if it has less than two parents. I hacked together a hardcoded version of it in https://github.com/HellBrick/GitRocketFilter/commit/74356a2082fb8d4c10f97ded1569ac5661cfdf5c and it seems to be doing what it's supposed to without screwing up anything unrelated, so I could add a proper option for it and send a PR if you agree this is a useful feature to have.

sure that option can help, PR welcome.