fix: add the search input cancel button in Chrome/Safari again

Currently all modern browsers support the search input cancel button.
So removing it in normalize-scss makes no more sense.
In fact normalize 8.0.0 added it back, see https://github.com/necolas/normalize.css/commit/f7c98c4c859c15363763f10a439b63d85b9afba0
But the used normalize-scss still relies on an old version of normalize.
References:
https://github.com/JohnAlbin/normalize-scss/issues/131
https://github.com/necolas/normalize.css/issues/685
Closes https://github.com/zurb/foundation-sites/issues/11015

Sorry, I had in mind a cleaner version of #11015 (comment) to resolve this issue, so this overwrite would not be required. I'll take care of it.

Not yet sure what a cleaner approach would be. Let me know how it should be then =)


OOM on Light and Bridge nodes

I found my mainnet LN getting OOMed a day ago on 8GB DO instance. @renaynay, found here BN ooming on BN with 16GB instance. There is definitely a leak somewhere, and it's likely to exist in the  FN as well.
At this point, there is not much info on why it happens, as well as why we haven't seen this on other networks like Arabica, Mocha, and Robusta

Right now, I am collecting profiles for further investigation

Running it with pprof for a day. No suspicious memory grow noticed, as well nothing leaky in profiles

Running for another 24 hours with continuous profiling. RAM usage is stable at 1.22 GB with a single spike to 1.91 GB.
Clearly, the leak does not happen under normal conditions, and some edge case has to be triggered in order to see it. It's unclear what exactly one has to do to trigger it, and I don't see any better ideas than continue profiling and observing.

New update. My node oomed again during badger compaction, which bursts ram usage. The node uses around 3GB of RAM right before the compaction, and most of the profiles lead to badger allocations. We have yet to investigate if this is a badgerv4  bug or if we incorrectly use it.
Talking to @Jorropo, he said they observe similar behavior with badger.

Just wanted to add that I am experiencing this issue on Arabica and have begun collecting pprof info. My server has 16GB of memory and the celestia light process will slowly consume until it's OOM

I am running the binary again with gomemlimit=2mib and gogc=25 to make runtime more conservative about ram usage

Such a low GOMEMLIMIT is equal to:
for {
 runtime.Gc()
 time.Sleep(time.Second)
}

This so far seems to be the leakiest of them all. It looks like badger txs are not cleaned up after Commit. Particularly, the trace comes from peerstoreds's flush.
So seems like there might be a bug in the DS-backed store, or it's the bug in Badger that was fixed in main, but nit in the release we use.

I tried with the latest master of Badger to test if the bug has anything to do with this, but it kept leaking
Out of curiosity, I tried to switch to Pebble, yielding results worth exploring.

LN kept syncing with no more than 500mib in use
It's not clear if, CPU-wise, the Pebble is more efficient than the Badger
Pebble looks like a much better maintained and more approachable code. It's easier to read, and it's very well documented.
Pebble provides more knobs to tune up things going further.

Did you notice any instability after switching to pebble? I'd be interested in building rc6.1 with pebble swapped in if that's possible by an end user (like with a go.mod dependency swap)|
(I need to keep my LN running 24/7 for Dymension and it keeps going down, so I'm excited for a solution)

Did you notice any instability after switching to pebble

I think it's too early to make any conclusions on stability. I need to run it for at least a week to be sure we don't have any side-effects after switching.

Update on the badger:
The code leaks in places where we write a single value to the Badger datastore directly, with Put. In places where we use Batch with multiple written it works well.
As an experiment, I tried using Batch inside of Put in go-ds-badger4 adapter, but it didn't yield any result. Profiles show that badger still leaks transactions inside of used batches.

At this point, the only clue we have is a single entry written vs multiple at the same time and this is likely to be a bug inside of the Badger.

On pebble:
Simply migrating to pebble made our node consume constantly around 300mibs for LN even during compactions. This is a good result, but we should not rush with migrating as its very disruptive. Also, considering that LNs won't have a high write-load we may also consider a different KV store engine that is not LSM-tree based and much simpler, likely B+ tree.
For now, I think we should focus on figuring out a simple patch for Badger and considering KV store migration in a separate issue.

New update on badger:
We were able to break the following by writing an additional entry every time we did a single Put. Even when we write two entries it still leaks.

At this point, the only clue we have is a single entry written vs multiple at the same time and this is likely to be a bug inside of the Badger.

However, there is good news. We were able to accelerate the memory growth by rewriting value for the same key over and over again. This also aligns with leaking code paths, where we update the state of something with a constant key. So there is enough proof at this point that the bug is in Badger.
The next step is to write a unit test for Badger that shows that and opens an issue on their side.

The bug is in DetectConflicts feature of Badger. By disabling it, I was able to get a stable RAM usage over an hour already

New final update:
The bug is not in DetectConflicts as I thought. Disabling DetectsConflicts just removes one of the leaks caused by the bug and it still had to be accompanied by some other case because everything was fine when I worked with Badger directly. A pure Badger test for overwriting the same key didn't show any leaks.
But right after DetectConflicts finding, I kept playing with the Badger to the point where I reduced RAM usage during sync up to 10 times(more on that later). This allowed me to detect another more minor leak in Badger that I hadn't realized but had seen before.
After a day of pure debugging, I found the true culprit of all the problems: an edge case in Badger. Check the patch for it here. Basically, when we flush an empty Batch, the transaction inside of the leak is not marked as read. Flushing of an empty Batch happens in DHT's provider manager. When the manager loads the provider set via ds.Query
, internally the autobatch wrapper does the Flush. As this query happens on startup, the batch is empty and thus the issue.(cc @Jorropo, this should explain why IPFS observes the leak with Badger as well)

Badger internals of the bug:
When we flush a datastore Batch with no data, it would not notify the internal synchronization primitive(Watermark) that the read side of the transaction has ended. The bug surprisingly does not leak the transaction or batch directly, but does not free up resources inside of the Watermark and does not progress the Watermark internal monotonic counter. The leak inside of the Watermark is the minor leak I mentioned in the previous paragraph, and the stalled counter causes the DetectConflicts feature to leak, which is the original leak.

The mystery is solved, and now we need to land the patch and apply all the optimizations I've collected along the way.
P.S. Debug branches:

https://github.com/celestiaorg/celestia-node/tree/badger-reproducible-bug
https://github.com/celestiaorg/celestia-node/tree/badger-bump - fixed with optimization and history of all the debug attempts
https://github.com/celestiaorg/go-ds-badger4/tree/debug - debug branch on datastore adapter
https://github.com/Wondertan/badger/tree/debug - debug branch on the Badger itself

Yes the watermark has to do w GC and we explored seeing watermark in pyroscope before. We fixed the leak but then we changed the badger parameters again recently so it's no longer fixed I assume

We fixed the leak but then we changed the badger parameters again recently so it's no longer fixed I assume

The leak has always been there(see above) various badger params only make it less or more severe.


Fastest way to convert videos

Actually my conversion script for videos is using your package this way :
    $ffmpeg   = FFMpeg::create(
                    [
                        'ffmpeg.binaries'  => getenv('FFMPEG_PATH').'/ffmpeg',
                        'ffprobe.binaries' => getenv('FFMPEG_PATH').'/ffprobe',
                        'timeout'          => 3600,
                        'ffmpeg.threads'   => 12,
                    ]
                );
                $video = $ffmpeg->open($original_path_here);
                $format = new X264();
                $format->setAudioCodec('libmp3lame');
                $video->save($format, $converted_path_here);

But the conversion is quite long for each (less than 1 minute) video. Is there any options to improve the conversion time ?

Hi @adepolas,
Your code seems good.
I don't think that you can optimize your code.
If you want to improve performances, you will have to increase the resources of your machine.
It also depends on the way your file is encoded.
I hope this helps.

closed due to inactivity.


enable more flexible options for compiler selection

In order to use different versions in non-default locations.
For example, replace:
cstring == 'clang'
with
cstring.endswith('clang'):
in driver/utils.py:614

paths are already allowable, rtfm.
I think what you want would better be described as  "some leeway in the name of the compiler" right?
clang-3.4   clang-2.7
right?  The cc hack was just a quick fix, yes?

right.

actually, I'd like to use it as described above too, and im not sure rtfm applies.
dejan@raven:~/workspace/souper/yices2$ export LLVM_COMPILER_PATH=/home/dejan/workspace/souper/third_party/llvm/Release/bin
dejan@raven:~/workspace/souper/yices2$ export LLVM_COMPILER=/home/dejan/workspace/souper/third_party/llvm/Release/bin/clang
dejan@raven:~/workspace/souper/yices2$ /home/dejan/workspace/whole-program-llvm/wllvm
CRITICAL:LLVM_COMPILER=/home/dejan/workspace/souper/third_party/llvm/Release/bin/clang : Invalid compiler type
Traceback (most recent call last):
  File "/home/dejan/workspace/whole-program-llvm/wllvm", line 18, in <module>
    builder = getBuilder(cmd, False)
  File "/home/dejan/workspace/whole-program-llvm/driver/utils.py", line 625, in getBuilder
    raise Exception(errorMsg)
Exception: LLVM_COMPILER=/home/dejan/workspace/souper/third_party/llvm/Release/bin/clang : Invalid compiler type

I'm currently hacking in LLVM_CC_NAME and LLVM_CXX_NAME support.
So the use case would be:
export LLVM_COMPILER=clang                                   #this is the type of compiler
export LLVM_COMPILER_PATH=/usr/local/llvm/bin
export LLVM_CC_NAME=clang-3.6
export LLVM_CXX_NAME=clang++-3.6

Make sense?

Try that. Let me know if it works for you.

Great another happy user ...

im quite happy

excellent  glad to increase euphoria rather than entropy.


[HW]

Name:
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/kamalakannan-nainar/
Attach the homework screenshots below for both step II and step III:

![homework1](https://user-images.githubusercontent.com/85203309/120405349-fb4a5d00-c365-11eb-810d-68f27dd8f597.jpg)
![CSQL-training](https://user-images.githubusercontent.com/85203309/120405370-09987900-c366-11eb-8e48-383ded98332a.jpg)
![datamodeling-training](https://user-images.githubusercontent.com/85203309/120405377-0bfad300-c366-11eb-8d2a-65ff272571bb.jpg)

Looks great Kamalakannan, thank you. Here's your badge -> https://api.badgr.io/public/assertions/og8W-CYpReStD-l5IHruaA?identity__email=nkk777c%40gmail.com


[warn]: in YARD::Handlers::Ruby::AttributeHandler: Undocumentable FIELDS

I've a class like this:
class A
  FIELDS = [:field1, :field2, :field3]
  attr_reader *FIELDS
end

when I generate the doc with yard doc --no-private -mmarkdown i get:
[warn]: in YARD::Handlers::Ruby::AttributeHandler: Undocumentable FIELDS
	in file 'lib/a.rb':3:

	3: attr_reader *FIELDS

What is the best way to handle this warning?
Is there a way to suppress this warning?
Environment details:

OS: OSX 10.12.6
Ruby version (ruby -v): ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
YARD version (yard -v): yard 0.9.9

The recommended way is to document your attrs, which you can't do in a single liner. You should do:
class A
  # docs for field 1
  attr_reader :field1

  # docs for field 2
  attr_reader :field2

  # docs for field 3
  attr_reader :field3
end

If you really don't care about the docs but want them to at least show up, you would use literals instead of constants. YARD cannot evaluate runtime code, even if that code may be a constant. This could work too:
class A
  attr_reader :field1, :field2, :field3
end


Don't mark done PipelineRuns as timed out

Changes
This PR fixes a bug that causes all completed PipelineRuns to eventually go into PipelineRunTimeout status. This was imo introduced by Fix for PipelineRuns getting stuck in the running state in the cluster #6095 in v0.47.0 @RafaeLeal @lbernick @jerop
To reproduce the issue, perform these three steps:
(1) Create a simple Pipeline
apiVersion: tekton.dev/v1
kind: Pipeline
metadata:
  name: noop
spec:
  tasks:
    - name: noop
      taskSpec:
        steps:
          - name: noop
            image: busybox
            command:
              - sleep
            args:
              - "1"
      timeout: 1m

(2) Create a simple PipelineRun
apiVersion: tekton.dev/v1
kind: PipelineRun
metadata:
  generateName: noop-
spec:
  pipelineRef:
    name: noop
  timeouts:
    pipeline: 1m

(3) The PipelineRun will complete successfully within a few seconds. Now wait three minutes.
(4) Restart the tekton-pipelines-controller. This will cause all PipelineRuns in the system to get reconciled.
And now the PipelineRun is moved into PipelineRunTimeout status.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

/kind bug
Release Notes
Completed PipelineRuns are not anymore changed to PipelineRunTimeout status

/uncc @wlynch
/cc  @lbernick @jerop

/need-cherry-pick

/retest

/test pull-tekton-pipeline-go-coverage

/cherry-pick release-v0.47.x


Adds repository field to package.json.

Also, fixes name of grunt-jscs. grunt-jscs-checker has been renamed grunt-jscs, and npm was warning about that. Unfortunately, there are no versions of grunt-jscs below 0.6.0, so I upgraded to a current version.
This change does not seem to affect installation or the results of grunt.
Also, I removed duplicate keys from package.json.

Thanks!


It might work... if it would download something...

^

I don't understand what the problem is. Can you please elaborate?

It opens the browser's download thing, and then it doesn't. Maybe you don't keep the file on the server enough time... or at all.

WebDGap uses the HTML5 FileReader and FileSaver API's. Which means you need to use a browser that supports those API's. What browser are you using?

Maxthon v<IP_ADDRESS>0, which is based off a chromium version from I think about a year ago... supports most of HTML5, and I didn't knew such thing existed... but why not try to maybe upload it on a free hosting somewhere?

Does your console say?
Github Pages is free hosting and the desktop apps of WebDGap are hosted via SourceForge.

I suggest using a support browser like Chrome/Firefox/Safari/ or Opera.


Add global debug option and more verbose options to sql-cli

Description
What is the current behavior?
Currently, we don't have an option for the user to show verbose output to debug.
closes: #1040
What is the new behavior?
We add a global --debug option and more local --verbose flags.

show airflow and other deps debug logs when debug is set
show raw exceptions when verbose is set
add verbose log to validate_connections
use sql-cli logger instead of new logger in run_dag
add RichHandler instead of StreamHandler to ti logger
add test for log level
set log level for ti.log
show airflow db init stdout/stderr when debug is set
catch exception in validate connections to continue validating

Does this introduce a breaking change?
No.
Checklist

[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Since we created the ticket, the scope has changed significantly. What do you think of updating the ticket description to explain why we have both debug and verbose, with examples of when we want to use each of them?

Done - updated the linked ticket.

to use set_verbose_mode in the commands that we want to have this option (can you think of any scenarios we don't want it to?)

As soon as we have something verbose to output, we can add that flag. Unfortunately this has to be added per command as global args such as debug have to come before the flow command i.e. flow --debug init.

What do you think we adding a minor beginning of SQL CLI developer documentation so any new team members could benefit from this information?

Makes sense. Would it a follow-up ticket work for you?


CQL Tracing

Description
This PR adds support for CQL tracing.
Tracing can be used like this:
// Create a simple query and enable tracing for it
let mut query: Query = Query::new("SELECT peer from system.peers".to_string());
query.set_tracing(true);

// QueryResult will contain a tracing_id which can be used to query tracing information
let query_result: QueryResult = session.query(query.clone(), &[]).await?;
let query_tracing_id: Uuid = query_result
    .tracing_id
    .ok_or_else(|| anyhow!("Tracing id is None!"))?;

// Get tracing information for this query and print it
let tracing_info: TracingInfo = session.get_tracing_info(&query_tracing_id).await?;
println!("Query tracing info: {:#?}\n", tracing_info);

Queries that support tracing are:

Session::query()
Session::prepare()
Session::execute()
Session::batch()
Session::query_iter()
Session::execute_iter()

In the specification it's written that only QUERY, PREPARE and EXECUTE queries support tracing so Session::batch() doesn't support it.
Notes
This PR depends on #180 and #187, I will rebase once they get merged - for now it's based on retry_policy2.
Only commits starting at 604599e - Return more information in Session::query() belong to this PR.
For now it's a Draft to disable merging.
TracingInfo contains columns from system_traces that are the same in Cassandra and Scylla. Scylla has some scylla specific entries that the user can query themselves if they really need to.
Retrying tracing info queries and its configuration is based on DataStax Java Driver
Fixed issues
Fixes: #189
Pre-review checklist

[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[x] I added relevant tests for new features and bug fixes.
[x] All commits compile, pass static checks and pass test.
[x] PR description sums up the changes and reasons why they should be introduced.
[x] I added appropriate Fixes: annotations to PR description.

The tests pass on my machine but fail in CI for some reason 0_o. Gonna investigate.

Probably related to timing - tracing data ends up in the tracing tables asynchronously, so you might need to try fetching the appropriate tracing id in a loop.
By the way, contrary to the protocol spec Scylla does support tracing batches, it's an important debugging mechanism, so we'd want to eventually support it in the driver too.

Probably related to timing - tracing data ends up in the tracing tables asynchronously, so you might need to try fetching the appropriate tracing id in a loop.

:+1: Added retrying in tests, also Cassandra sometimes had a null in the table which the code handled incorrectly, all fixed now.

By the way, contrary to the protocol spec Scylla does support tracing batches, it's an important debugging mechanism, so we'd want to eventually support it in the driver too.

Added

@piodul @psarna Rebased and ready for review

@cvybhu Looks good, but please also rebase on top of /main - after merging TLS, a small manual translation of this layer to QueryResult is in order.

@psarna rebased and ready


migrate old jira issues to simplebuild/simplebuild-dgcode repos

We should obviously migrate dgcode issues to simplebuild/simplebuild-dgcode repos so we don't miss anything important.

Done. We still need to have a look at https://jira.esss.lu.se/projects/DGSW

Done as well.


Differing behaviour between dev and release compilations when updating/rendering RwSignal<Vec<(Fragment, i32)>>

Describe the bug
Hello,
I am currently working on a demonstrative chatting client using leptos.
I have an RwSignal<Vec<(Fragment, i32)>> (Don't judge me), being updated via the following
                                                    val.push((
                                                    view!{cx,
                                                        <>

                                                                {link.inner_text()}
                                                                <Icon icon=IoIcon::IoClose class="h-3 w-3" on:click=move |_| {
                                                                    input_signal.update(|val| {
                                                                        let index = val.iter().position(|(_, id)| *id == link.value()).unwrap();
                                                                        val.remove(index);
                                                                    });
                                                                    (!input_signal.get().iter().any(|(_, id)| *id == link.value())).then(|| {
                                                                        input.set_value(&(input.value().replace(&(link.value().to_string() + ","), "")));
                                                                        input.set_value(&(input.value().replace(&(link.value().to_string()), "")));
                                                                    });
                                                                }/>

                                                        </>
                                                    },item.id)

And rendered here:
              <input type="text" class=move || format!("w-full py-2 px-4 border border-gray-300 rounded-md
                focus:outline-none focus:ring-2 focus:ring-indigo-500 focus:border-indigo-500
                text-transparent select-none selection:bg-none {}", if disabled.get() {"opacity-50"} else {""})
                placeholder="Select an option"
                name="other_users"
                _ref=_ref
                on:click=move |_| hidden_state.update(|val| *val = !*val )/>
                             {move || input_signal.get().iter().map(|val| {
                                  val.0.clone() // <--- Here
                              }).collect_view(cx)}

Leptos Dependencies
As requested:
actix-files = { version = "0.6", optional = true }
actix-web = { version = "4", optional = true, features = ["macros", "secure-cookies"] }
actix-identity = { version = "0.5.2", optional = true }
actix-session = { version = "0.7.2", features = ["redis", "redis-rs-session"], optional = true }
console_error_panic_hook = "0.1"
cfg-if = "1"
leptos = { version = "0.3", default-features = false, features = [
  "serde",
] }
leptos_meta = { version = "0.3", default-features = false }
leptos_actix = { version = "0.3", optional = true }
leptos_router = { version = "0.3", default-features = false }
wasm-bindgen = "0.2.87"
serde = { version = "1.0.163", features = ["derive"] }
serde_json = "1.0.96"
getrandom = { version = "0.2.9", features = ["js"] }
serde_urlencoded = "0.7.1"
fancy-regex = { version = "0.11.0" }
validator = { version = "0.16.0", features = ["derive", "phone"] }
lazy_static = "1.4.0"
env_logger = "0.10.0"
web-sys = { version = "0.3.63", features = ["HtmlFormElement", "SubmitEvent", "KeyboardEvent", "Window", "Location", "History", "File", "FileList", "HtmlInputElement", "HtmlLiElement"] }
gloo-net = "0.2.6"
gloo-file = { version = "0.2.3", features = ["futures"] }
tokio = { version = "1.28.1", features = ["rt", "process"], optional = true }
wasm-bindgen-futures = "0.4.36"
sea-orm-migration = { version = "0.11.3"}
async-trait = "0.1.68"
sea-orm = { version = "0.11.3", features = ["sqlx-mysql", "runtime-tokio-native-tls", "with-chrono"], optional = true }
lettre = { version = "0.10.4", optional = true }
askama = "0.12.0"
base64 = "0.21.2"
chrono = "0.4.24"
rand = "0.8.5"
redis = "0.23.0"
argon2 = "0.5.0"
leptos_icons = { version = "0.0.12", default_features = false ,features = ["AiCloseCircleFilled", "HiChatBubbleOvalLeftEllipsisSolidMd", "HiUserCircleSolidMd", "HiArrowLeftCircleOutlineLg", "AiUserOutlined", "AiUserAddOutlined", "HiChevronLeftSolidLg", "BiUserCircleSolid", "HiEllipsisHorizontalSolidMd", "TbPhotoFilled", "HiPaperAirplaneOutlineLg", "LuImageOff", "IoClose", "IoTrash", "FiAlertTriangle"] }
futures-util = "0.3.28"
iter_tools = "0.1.4"
infer = "0.13.0"

To Reproduce
Steps to reproduce the behavior:

Clone the following link
Run docker build -t zing .. This may take 10-15 minutes to build depending on your system.
Run docker run -p 8000:8000 zing
Create 3 accounts with valid email addresses as you will need to validate your email.
Visit this link and click the group chat icon adjacent to the "messages" header.
Select the other two users you have created and click on create. You will need to reload after this as I have not yet created an appropriate update signal.

Expected behavior
The expected behavior is that within the first image (Dev build).
The unexpected behavior is that within the second image (release build).
Screenshots

Additional context
The component is the GroupChatModal on line 1295 of the following link.
If I fix this issue, I will post the fix.

Thanks for this very detailed report!
The issue almost certainly has to do with the way you are cloning and reusing the fragment, I agree.
I'd recommend trying two things:

Is it possible for this to be an RwSignal<Vec<(HtmlElement
, i32)>> instead? i.e., to simply drop the wrapping <></> fragment around the
 you are using? If so, this would likely work correctly.
It's worth checking whether this is an issue that's been fixed between 0.3 and the current main release by updating from 0.3 to a dependency on git main.

Otherwise, a minimal reproduction that doesn't require a 10-15 minute build process, creating user accounts, etc. to set up will make it more likely I'll get to this sooner.

Ah, I see.
Is there a difference between the implementation of Fragment and other view elements at compile?

Yes. Fragments are backed by a regular web DocumentFragment, which are somewhat tricky to work with. (Although honestly, all DOM elements are hard to deal with). Appending a DocumentFragment to the DOM somewhere moves its children out, so we have to gather them back in if you unmount it and move them somewhere else. It's possible there's an edge case that's missed here somewhere, and the discrepancy between debug and release mode suggests that's the case, but it's also just true that fragments are trickier than regular elements.

Ok,
I have found a solution, but it points to an issue within the intricacies within the implementations of collect_view(cx).
A slight modification to the initial implementation has been introduced from:
{ move ||
    input_signal.get().iter().map(|val| {
        val.0
    })
.collect_view(cx)}

to:
                     <For
                       each=move || input_signal.get()
                       key=|input| input.1
                       view=move |cx, item: (HtmlElement
, i32)| {
                         view! {
                           cx,
                             {item.0}
                          }}/>

seems to have fixed the issue.

Here's a simpler reproduction, for my own purposes in addressing this one:
#[component]
fn App(cx: Scope) -> impl IntoView {
    let count = create_rw_signal(cx, 0);
    let frags = create_rw_signal(cx, vec![]);

    view! { cx,
        <button on:click=move |_| {
            count.update(|n| *n += 1);
            frags.update(|f| f.push((
                view! { cx, <>{count.get()}</> },
                count.get()
            )));
        }>"+1"</button>

            {move || frags.get().iter().map(|val| {
                val.0.clone() // <--- Here
            }).collect_view(cx)}

    }
}

No longer relevant in 0.7


Figure out some kind of sound board solution

How do we want to do a soundboard or collection of oneshots/favorites?
please suggest ideas in the comments.

Turns out, you can just make a note with whatever sounds you want and drag the note to the upper right corner to keep it with quick access.


X-Scale Problem

I have written my request here to add some screenshots:
http://stackoverflow.com/questions/35797229/android-mpandroidchart-scale-x-axis

Sorry for the late reply, but I'm not sure I understand how this relates to CompactCalendarView. Could you provide a bit more details?

Closing this issue since there been no activity.


Setting project metadata doesn't fail when project_metadata.cfg doesn't exist

Implemented specific errors for file not found in windows/unix, used for loading project metadata file when setting a value. If the file doesn't exist it will create one instead of failing.
Fixes #31444

Changes look good. Check the PR referenced in #31444, there are a few other places where this code was changed and should be changed back / improved as you did it.

I've made additional changes from PR #31077 but I didn't find any other case where it shouldn't fail on a missing file.
Here are all the uses of ConfigFile::Load I've found:
EditorSettings::set_project_metadata: creates project_metadata.cfg if it doesn't exist
EditorSettings::create: still fails (it checks if the file exists right before)
PluginConfigDialog::config: still fails (there's a proper error message earlier for missing plugin.cfg)
EditorPlugin::get_config: removed (not used)

Thanks!


Few enchancements for shader editor

Changes:

Draw space properly updates for shader editor (no longer require editor restart)
Same for Line guideline
Disables possibility to set breakpoints - cuz it's not possible for shaders

Cherry-picked for 3.2.1.


Fix remaining test cases

with the exception of the emoji and IDN domain names.

Would like to resolve these conflicts then I'll accept the PR? Thanks @KonajuGames 🙂

Would like to resolve these conflicts then I'll accept the PR? Thanks @KonajuGames 🙂

I'll try to get to that this afternoon. I'm going away tonight for the long weekend.


Remove from All Instances / Set to Default Instance

Is there a way to remove a player out of any instances they're in / return them back to the default instance (0)?
For example, on player respawn I want to set them back to 0. I could do this by removing them from the instance they're in, but this may require a loop to check all instances to see if they're in x instance and if so, remove them.

You can use the native GetPlayerRoutingBucket before setting it to 0 so you don't need to loop through all the instances.

Oh okay, thanks. I'll give that a check!


Support for storing challenge to a file

Challenges for each alternate name is fetched and then challenges are deployed. Due to some network error, the script exits and the challenge tokens are lost. This leads to exceeding the rate limit.

This shouldn't happen anymore since dehydrated now checks if a domain is already verified.


Problems using non-'soma' values for record_isec argument in simulate_dipole()

Hi all, I'm encountering a series of issues when trying to use the record_isec optional argument in simulate_dipole() to return i values from non-soma segments.

Running SS_dpls = simulate_dipole(SS_net, tstop=500, n_trials=5, record_isec='soma') works, but setting record_isec equal to 'all' crashes the kernel of the jupyter notebook I'm running it in. I undersand isec has more values than vsec (i.e., vectors for ALL synaptic currents rather than just voltage) and this doesn't happen with just 1 trial, so I assume this is a matter of memory overload.
However, I don't seem to be able to save outputs from a different segment by name to prevent this (e.g., 'basal_1') - this raises "Invalid value for the 'record_isec' parameter. Allowed values are 'all', 'soma', and False, but got 'basal_1' instead.".
Also, when simulating one trial with record_isec = 'all', the segment keys in SS_net.cell_response.isec[gid] only include 'soma', and none of the other segment names.

I'm particularly interested in saving the GABAb current from apical1, so let me know if there's another way I should be going about saving and accessing current values in other segments for one or multiple trials.

what you are requesting is probably going to require some combination of bugfix + enhancement.
Here is the diff of the original pull request: https://github.com/jonescompneurolab/hnn-core/pull/502/files by @ntolley . Can you see from there what could be the issue?

Sure. I understand if I need to find a better way to extract and save that variable per trial to avoid the memory issue as long as we fix the bug that's preventing it from getting returned on single trials.
Given that SS_dpls = simulate_dipole(SS_net, tstop=500, n_trials=1, record_vsec='all') is also returning a SS_net.cell_response.vsec dictionary with only 'soma' and no other segments, could there be a problem arising from line 551, section_names = list(self.sections.keys()), in referencing sections instead of _nrn_sections defined in line 313? In general, it looks like the only key getting iterated and saved for both isec and vsec when record is
'all' is still 'soma'.

@darcywaller glad you could figure it out. The code is written in a pretty general way ... so if you want to implement the feature to record from specific segments (instead of all), it might not be that difficult, specially with some local help from @ntolley !

We chatted about some strategies to deal with the memory issues!
Now I'm remembering why I decided not to implement passing something like record_isec='apical_tuft_ampa' as an option. Since this only applies to certain cells, the logic would have to be a little more complex under the hood.
But given the potential memory issues if you want something else it might be worth revisiting (I'm sure there's an elegant way to write up that enhacement :wink: )

Which ParallelBackend are you using @darcywaller? I'm just trying to diagnose whether its a memory issue or process timeout issue.

@rythorpe good point. MPIBackend with 4 cores was what I was using originally, but got the error "MPI simulation failed. Return code: 137". Then, simulating 5 trials while record_isec = 'all' without a ParallelBackend was what crashed my jupyter kernel.

Does JoblibBackend throw the same error? It might be slower but worth checking ...
also can you share the full traceback?

JoblibBackend also gets killed, traceback below:
Running simulation with loaded Successful stop parameters
Joblib will run 5 trial(s) in parallel by distributing trials over 4 jobs.

TerminatedWorkerError                     Traceback (most recent call last)
/tmp/ipykernel_42875/3558491913.py in
4 with JoblibBackend(n_jobs=4): # takes a little while to initialize!
5     print("Running simulation with loaded Successful stop parameters")
----> 6     SS_dpls = simulate_dipole(SS_net, tstop=500, n_trials=5, record_isec='all')
7
8 for dpl in SS_dpls:
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/dipole.py in simulate_dipole(net, tstop, dt, n_trials, record_vsec, record_isec, postproc)
98                       'smoothing and scaling explicitly using Dipole methods.',
99                       DeprecationWarning)
--> 100     dpls = _BACKEND.simulate(net, tstop, dt, n_trials, postproc)
101
102     return dpls
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/parallel_backends.py in simulate(self, net, tstop, dt, n_trials, postproc)
557         parallel, myfunc = self._parallel_func(_simulate_single_trial)
558         sim_data = parallel(myfunc(net, tstop, dt, trial_idx) for
--> 559                             trial_idx in range(n_trials))
560
561         dpls = _gather_trial_data(sim_data, net=net, n_trials=n_trials,
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/joblib/parallel.py in call(self, iterable)
1096
1097             with self._backend.retrieval_context():
-> 1098                 self.retrieve()
1099             # Make sure that we get a last message telling us we are done
1100             elapsed_time = time.time() - self._start_time
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/joblib/parallel.py in retrieve(self)
973             try:
974                 if getattr(self._backend, 'supports_timeout', False):
--> 975                     self._output.extend(job.get(timeout=self.timeout))
976                 else:
977                     self._output.extend(job.get())
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/joblib/_parallel_backends.py in wrap_future_result(future, timeout)
565         AsyncResults.get from multiprocessing."""
566         try:
--> 567             return future.result(timeout=timeout)
568         except CfTimeoutError as e:
569             raise TimeoutError from e
/gpfs/runtime/opt/python/3.7.4/lib/python3.7/concurrent/futures/_base.py in result(self, timeout)
433                 raise CancelledError()
434             elif self._state == FINISHED:
--> 435                 return self.__get_result()
436             else:
437                 raise TimeoutError()
/gpfs/runtime/opt/python/3.7.4/lib/python3.7/concurrent/futures/_base.py in __get_result(self)
382     def __get_result(self):
383         if self._exception:
--> 384             raise self._exception
385         else:
386             return self._result
TerminatedWorkerError: A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker.
The exit codes of the workers are {SIGKILL(-9)}
Here's the traceback with MPIBackend():
Running simulation with loaded Successful stop parameters
MPI will run 5 trial(s) sequentially by distributing network neurons over 4 processes.
numprocs=4
A process has executed an operation involving a call to the
"fork()" system call to create a child process.  Open MPI is currently
operating in a condition that could result in memory corruption or
other system errors; your job may hang, crash, or produce silent
data corruption.  The use of fork() (or system() or other calls that
create child processes) is strongly discouraged.
The process that invoked fork was:
Local host:          [[22323,1],0] (PID 43009)
If you are absolutely sure that your application will successfully
and correctly survive a call to fork(), you may disable this warning
by setting the mpi_warn_on_fork MCA parameter to 0.
Loading custom mechanism files from /oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/mod/x86_64/libnrnmech.so
Building the NEURON model
Loading custom mechanism files from /oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/mod/x86_64/libnrnmech.so
Loading custom mechanism files from /oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/mod/x86_64/libnrnmech.so
Loading custom mechanism files from /oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/mod/x86_64/libnrnmech.so
[Done]
[node1821.oscar.ccv.brown.edu:43003] 3 more processes have sent help message help-opal-runtime.txt / opal_init:warn-fork
[node1821.oscar.ccv.brown.edu:43003] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
Trial 1: 0.03 ms...
Trial 1: 10.0 ms...
Trial 1: 20.0 ms...
Trial 1: 30.0 ms...
Trial 1: 40.0 ms...
Trial 1: 50.0 ms...
Trial 1: 60.0 ms...
Trial 1: 70.0 ms...
Trial 1: 80.0 ms...
Trial 1: 90.0 ms...
Trial 1: 100.0 ms...
Trial 1: 110.0 ms...
Trial 1: 120.0 ms...
Trial 1: 130.0 ms...
Trial 1: 140.0 ms...
Trial 1: 150.0 ms...
Trial 1: 160.0 ms...
Trial 1: 170.0 ms...
Trial 1: 180.0 ms...
Trial 1: 190.0 ms...
Trial 1: 200.0 ms...
Trial 1: 210.0 ms...
Trial 1: 220.0 ms...
Trial 1: 230.0 ms...
Trial 1: 240.0 ms...
Trial 1: 250.0 ms...
Trial 1: 260.0 ms...
Trial 1: 270.0 ms...
Trial 1: 280.0 ms...
Trial 1: 290.0 ms...
Trial 1: 300.0 ms...
Trial 1: 310.0 ms...
Trial 1: 320.0 ms...
Trial 1: 330.0 ms...
Trial 1: 340.0 ms...
Trial 1: 350.0 ms...
Trial 1: 360.0 ms...
Trial 1: 370.0 ms...
Trial 1: 380.0 ms...
Trial 1: 390.0 ms...
Trial 1: 400.0 ms...
Trial 1: 410.0 ms...
Trial 1: 420.0 ms...
Trial 1: 430.0 ms...
Trial 1: 440.0 ms...
Trial 1: 450.0 ms...
Trial 1: 460.0 ms...
Trial 1: 470.0 ms...
Trial 1: 480.0 ms...
Trial 1: 490.0 ms...
Building the NEURON model
[Done]
Trial 2: 0.03 ms...
Trial 2: 10.0 ms...
Trial 2: 20.0 ms...
Trial 2: 30.0 ms...
Trial 2: 40.0 ms...
Trial 2: 50.0 ms...
Trial 2: 60.0 ms...
Trial 2: 70.0 ms...
Trial 2: 80.0 ms...
Trial 2: 90.0 ms...
Trial 2: 100.0 ms...
Trial 2: 110.0 ms...
Trial 2: 120.0 ms...
Trial 2: 130.0 ms...
Trial 2: 140.0 ms...
Trial 2: 150.0 ms...
Trial 2: 160.0 ms...
Trial 2: 170.0 ms...
Trial 2: 180.0 ms...
Trial 2: 190.0 ms...
Trial 2: 200.0 ms...
Trial 2: 210.0 ms...
Trial 2: 220.0 ms...
Trial 2: 230.0 ms...
Trial 2: 240.0 ms...
Trial 2: 250.0 ms...
Trial 2: 260.0 ms...
Trial 2: 270.0 ms...
Trial 2: 280.0 ms...
Trial 2: 290.0 ms...
Trial 2: 300.0 ms...
Trial 2: 310.0 ms...
Trial 2: 320.0 ms...
Trial 2: 330.0 ms...
Trial 2: 340.0 ms...
Trial 2: 350.0 ms...
Trial 2: 360.0 ms...
Trial 2: 370.0 ms...
Trial 2: 380.0 ms...
Trial 2: 390.0 ms...
Trial 2: 400.0 ms...
Trial 2: 410.0 ms...
Trial 2: 420.0 ms...
Trial 2: 430.0 ms...
Trial 2: 440.0 ms...
Trial 2: 450.0 ms...
Trial 2: 460.0 ms...
Trial 2: 470.0 ms...
Trial 2: 480.0 ms...
Trial 2: 490.0 ms...
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.

mpiexec noticed that process rank 0 with PID 43009 on node node1821 exited on signal 9 (Killed).
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/parallel_backends.py:167: UserWarning: Child process failed unexpectedly
warn("Child process failed unexpectedly")

RuntimeError                              Traceback (most recent call last)
/tmp/ipykernel_42875/3071245237.py in
4 with MPIBackend(n_procs=4): # takes a little while to initialize!
5     print("Running simulation with loaded Successful stop parameters")
----> 6     SS_dpls = simulate_dipole(SS_net, tstop=500, n_trials=5, record_isec='all')
7
8 for dpl in SS_dpls:
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/dipole.py in simulate_dipole(net, tstop, dt, n_trials, record_vsec, record_isec, postproc)
98                       'smoothing and scaling explicitly using Dipole methods.',
99                       DeprecationWarning)
--> 100     dpls = _BACKEND.simulate(net, tstop, dt, n_trials, postproc)
101
102     return dpls
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/parallel_backends.py in simulate(self, net, tstop, dt, n_trials, postproc)
718             command=self.mpi_cmd, obj=[net, tstop, dt, n_trials], timeout=30,
719             proc_queue=self.proc_queue, env=env, cwd=os.getcwd(),
--> 720             universal_newlines=True)
721
722         dpls = _gather_trial_data(sim_data, net, n_trials, postproc)
/oscar/home/ddiesbur/hnn-core/lib/python3.7/site-packages/hnn_core/parallel_backends.py in run_subprocess(command, obj, timeout, proc_queue, *args, **kwargs)
232         # simulation failed with a numeric return code
233         raise RuntimeError("MPI simulation failed. Return code: %d" %
--> 234                            proc.returncode)
235
236     child_data = _process_child_data(proc_data_bytes, data_len)
RuntimeError: MPI simulation failed. Return code: 137

That definitely looks like a memory issue. I'm assuming the same thing happens when running a single trial with 1 job using JoblibBackend?

Actually, no, apparently
with JoblibBackend(n_jobs=1):     SS_dpls = simulate_dipole(SS_net, tstop=500, n_trials=1, record_isec='all')
completes without an error.

how much RAM are you working with ? joblib definitely clones the data, so the more cores you use, the more memory you are going to consume ... it might just scale linearly


Allow commands to be restarted when in error/stalled state

As a user, I will want to be able to restart a command that goes into an error state. Depending on how we define error state, we may also want the user to be able to restart stalled commands (which may not be in error). For our purposes here, this should just be a test button below the account display.
Acceptance Criteria

User can click a button to restart a failed command.


Shipping methods title should be required.

Is your feature request related to a problem? Please describe.
Able to save shipping methods with blank titles. and showing shipping methods with blank names.
Also required the rate field.
Describe the solution you'd like
The Title fields should be required. Here Rate
Describe alternatives you've considered
No response
Additional context
No response

Now, this issue is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


rich presence not being set in macOs 12.3

script seems to run just fine (including good outputs in console) but i can't get the rich presence to be set on discord after upgrading to monterey from big sur
let me know if i can help with any debug information!!!

log

Client {
  options: { id: "773825528921849856" },
  ipc: DiscordIPC {},
  user: {
    id: "385196786438111233",
    username: "merilynn",
    discriminator: "1234",
    avatar: "0dbce623a026a372c3647d0d4d8df485",
    bot: false,
    flags: 528,
    premium_type: 2
  },
  config: {
    cdn_host: "cdn.discordapp.com",
    api_endpoint: "//discord.com/api",
    environment: "production"
  },
  token: undefined,
  tokenExpires: undefined,
  application: undefined
}
isOpen: true
state: playing
props: {
  class: "fileTrack",
  id: 9459,
  index: 1378,
  name: "Black Cat",
  persistentID: "BA16756898C727D0",
  databaseID: 6380,
  dateAdded: "2022-04-02T21:38:21.000Z",
  time: "3:58",
  duration:<PHONE_NUMBER>185547,
  artist: "Broadcast",
  albumArtist: "Broadcast",
  composer: "",
  album: "Tender Buttons",
  genre: "Leftfield/Synth-pop/Experimental",
  bitRate: 320,
  sampleRate: 44100,
  trackCount: 14,
  trackNumber: 2,
  discCount: 1,
  discNumber: 1,
  size: 9615553,
  volumeAdjustment: 0,
  year: 2005,
  comment: "Tumen Collection",
  eq: "",
  kind: "MPEG audio file",
  mediaKind: "song",
  modificationDate: "2022-03-31T05:56:44.000Z",
  enabled: true,
  start: 0,
  finish:<PHONE_NUMBER>185547,
  playedCount: 0,
  skippedCount: 0,
  compilation: false,
  rating: 0,
  bpm: 0,
  grouping: "",
  bookmarkable: false,
  bookmark: 0,
  shufflable: true,
  lyrics: "",
  category: "",
  description: "",
  episodeNumber: 0,
  unplayed: false,
  sortName: "",
  sortAlbum: "",
  sortArtist: "Broadcast",
  sortComposer: "",
  sortAlbumArtist: "Broadcast",
  loved: false,
  disliked: false,
  albumLoved: false,
  albumDisliked: false,
  cloudStatus: "unknown",
  work: "",
  movement: "",
  movementNumber: 0,
  movementCount: 0,
  location: {},
  playerPosition: 41.65399932861328
}
infos: {
  artwork: "https://is2-ssl.mzstatic.com/image/thumb/Music/v4/9b/5d/13/9b5d1300-f307-b0ed-b616-20bd3af30d45/sour...",
  url: "https://music.apple.com/us/album/tender-buttons/291071689?uo=4"
}

Hello! These logs looks fine, are you still running into this issue?

it seemed to start working again randomly after confirming a prompt to allow the script to access the music app

All right, feel free to reopen the issue if you encounter the same problem again.

same issue for me - rich presence wasn't being set.
it started working once I got the prompt and I allowed it to access the music app


[Bug] Readme errors

Hi,
Some errors in README like:
var sollet = new Wallet("mnemonic words ...", Wordlist.English);

Now its WordList, and in general some mistakes in the readme
Thanks

Thanks for reporting this, will patch it in an upcoming PR

Closed by #280


Issue with GUI using long regex

Hi,
Having long regex-matches seems to "break" the GUI; the width of the "dropdown" window is smaller than the width of the content, causing things to get out of scope, and without any scrollbars.
Going to the full-page option page, things are still out of scope, but it's possible to at least scroll sideways.

Thanks for the screenshot, I was going to ask one :)
The fix should be pretty straightforward, I plan to limit the width of the column and display an ellipsis to indicate that the regex is actually longer and display it on hover. Would that suits you ?

For showing them; sure. How about editing when you are in the "Popin" window?

Hey, had a pretty eventful week, so the fix is coming rather later than sooner.
I put the ellipsis in place, and when you hover the cell, the full content should be displayed as it is also now put as the title of the cell.
Concerning the edition, I don't have a "good" solution. It is possible to edit it as the input box allows to have longer text, but I agree it is not ideal. Do you have any idea ?

The fix is available in the latest release : https://github.com/krtek4/MultiPass/releases/tag/v0.7.3
I'll publish it after some more test

Hi,
Thanks. Seems to be working so far on my end. I don't think it's necessary to do anything more regarding editing long regexes. Sure, it's a bit cumbersome with a "horisontal scrolling" text input field, but you can just copy/paste stuff, and edit it somewhere else.

Just released on the three addon stores, update should be automatically applied shortly. I am closing this on the meantime :)


Update Shapes to 4.4.2

Thank you for the contribution. It was merged directly as e3f22a766c8afbc218515185c19c9b588e49c03f to keep commit history cleaner. Your contribution is still credited to you.


765 original language entry

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/7XX.csv

Is it correct to record free translation in 765 (and freely translated in 767)? The Toolkit mapping thinks so but I doubt it. If not, do we need to account for them?
These are the only instances I find in OCLC that don't record 'free translation' or 'freely translated' in 700-730.
765$i
(OCoLC)1114264456
775$i
(OCoLC)24009193, (OCoLC)872105317, (OCoLC)872104662, (OCoLC)227898861
787$i (I assume this is correct.)
(OCoLC)847985170, (OCoLC)953418747, (OCoLC)953418567

Translation is a relationship between expressions but 76x-78x link to manifestation records.
I can derive access points for expressions by combining values of $a and $s, or $a and $t, or using $t alone depending on the original main entry, but I wonder if we want to map the manifestation information as well. It may be like this:
[Expression1] translation of [Expression2]
[Expression2] access point for expression [values of ($a, $s) | ($a, $t) | $t]
[Expression2] manifestation of expression [Manifestation]
[Manifestation] access point for manifestation [values of ($a, $t, $b, $m, $d, $h, $k, $n, $g)]
[Manifestation] identifier for manifestation [value of $r | $u | $y | $z | $w]
[Expression2] work expressed [Work]
[Work] ISSN [value of $x]
$a, $t, $b, $m, $d, $h, $k, $n, $g follows the ISBD order, but where does $c fit in? I didn't find any information from either the LC or the OCLC MARC manual.

These are all really good questions that might benefit from in-person discussion, especially at a meeting where @AdamSchiff is around to answer MARC questions. I can't remember ever cataloging a freely translated work/expression. @junghaelee catalogs more literature so may have more experience than I do. If nobody answers this asynchronously before Tuesday, I'll put it on the agenda for Wednesday morning. Thanks for asking fabulous questions, @pan-zhuo !

@GordonDunsire Hi Gordon, the 765 is related to expression. Can we use the element translation of in some concise way to retain the relationship?
In the first pass, subfields a, s, t, c, b, m, d, h, k, n, g are mapped together to related manifestation of manifestation by structured description to avoid expression IRI duplication problems, but lose the relationship translation of.
And subfields r, u, y, z are mapped separately to has related manifestation of manifestation with the recording method being identifier. I am not sure how identifier works here. It is just recorded like a string.
And subfield i is mapped to note on manifestation, which is to use note to clarify the relationship.

@pennylenger: This is related to the (https://github.com/uwlib-cams/MARC2RDA/issues/74)[041 discussion]. We cannot process this field for aggregate manifestations.
For a manifestation that embodies a single expression, we can mint an IRI for the original language expression if the language is recorded in 041. I note in the discussion that this expression can be related to a minted work and both have an appellation that is an access point, but there is no primary related manifestation for the minted expression. Field 765 provides that primary related manifestation. If this is linked to the output of 041, then the translation relationship is already retained.
The transform cannot make a direction distinction between the unstructured, structured, and identifier recording methods; all use the RDA datatype property. The distinction appears elsewhere in the RDA description set: structured descriptions and identifiers have an XML datatype and/or use an object property with an IRI; unstructured descriptions are untyped literals. Structured descriptions and identifiers are distinguished by data provenance: structured descriptions have a value vocabulary term, an access point, or an associated string encoding scheme; identifiers have an identifier scheme.


Allow "no value" on lineChart

Hi!
Would be nice to allow no values on the linechart, at this moment the linechart only supports float64 values (that defaults to 0 if no value) but sometimes you don't have values to render on the graph. A  0 and a nil are two different things and could make the graph break by the Y axis getting very big (from 0 to N) in very high value graphs without very differences.
An example to show the graph when we don't have values:
We have this graph on Prometheus that shows us that from 5:27 to 5:29 doesn't have values (not rendered and the Y axis doesn't show 0):

Same as above but rendered using termdash:

The problem with the termdash rendering is that the "no values" are rendered with the default float64 as 0 and the Y axis shows 0 making the scale of the graph bigger and by this harder to get insights from it.
The first approach to solve this that comes to my mind is by having *float64 as value unit or similar (custom type with pointers on no values) in another method like SeriesWithNils, SeriesWithNoValues so it doesn't break the current API.

Thank you @slok, this certainly is an interesting use case that I didn't think about.
Luckily when it comes to the API, we might have another option that results in a compatible change. The float type can also have a special value NaN, which literally means "not-a-number". So we can adjust the LineChart to skip values that are NaN.
To be able to prioritize this work, can you help me understand if this is a "nice-to-have" enhancement or something that you would require right away?

Hi @mum4k!
As always thank you for responding so fast, first of all, I didn't know about the NaN! thanks!
At this moment I'm developing a new application in my spare time (is private for now, I'll make it public when I have the basic functionality, but I'm near), this application is a simplified grafana for terminal, so you can load dashboards based on config files and retrieve the metrics from different datasource, configure metric colors, thresholds, timerange...
Example:

I've selected termdash as the rendering engine for the widgets, although it lacks some functionality compared to libraries like termui, the API is cleaner and I think it has better looking, so once again, congrats :)
In the case of priority, I would say that this is very important if you render high values that don't vary a lot, so in my opinion is a requirement, but doesn't need to be right away, although if it's not too complicated for a person that lacks the knowledge of the internals of the library, I could contribute with a PR.

Thank you for sharing the screenshot @slok, that looks really good!
Understood about the priority. I would say the change itself will have medium complexity. It doesn't require knowledge of the infrastructure of termdash, and should be completely contained within the implementation of the linechart. However it will need to be propagated throughout all the layers of the linechart's implementation. I would roughly outline the required changes as follows:

Code that determines the min,max values needs to do the right thing for NaNs (ignore them):
https://github.com/mum4k/termdash/blob/a9515f27215c8c7f3c0df731c4e86103cb9cdb9d/widgets/linechart/linechart.go#L54-L65
The internal axes package might need some changes to support the NaN values:
The logic that draws the values will need to know that it is supposed to skip over NaNs without attempting to draw the braille lines:
https://github.com/mum4k/termdash/blob/a9515f27215c8c7f3c0df731c4e86103cb9cdb9d/widgets/linechart/linechart.go#L408

I might be missing something, but that should be it in a nutshell. It is great to hear you might be willing to contribute a PR. I would suggest you look at the code in the linechart package and its surrounding libraries and see if you feel like sending the PR. Please let me know what you decide. If you prefer me doing this, considering this is important for you I can slot it in a week or two.
Also please don't hesitate to open issues for any of the missing features you mentioned. Happy to discuss further improvements we need to make. Or you could help by prioritizing any issues that already exist so we develop the right things.

Thanks for the tips!
Checking your steps, hacking around a little bit  the code and making few changes I had good results, I need to check if I have corner cases, check the tests... but I'll do it with more calm in the following days and if everythings seems ok make the PR!
Before the changes:

After the changes:

Great news! Please feel free to ask me if you will have any questions.

Fixed in the devel branch.


Expose PFS load testing

This PR refactors and exposes the PFS load testing. The load testing has been simplified a bit by removing the required nesting of the components (operations, files, sizes) in a fuzz* component. The PFS load testing has been exposed through gRPC (RunLoadTest) and has a corresponding wrapper in the Go client (RunPFSLoadTest) / pachctl (pachctl run pfs-load-test). RunLoadTest takes a load test spec file (the specification and an example are viewable through pachctl run pfs-load-test -h) and a seed. RunLoadTest returns the branch that was generated for running the load test (the state is still viewable after the test completes, so additional validation can be run), the seed that was used, and any errors that occurred while running the load test.
Miscellaneous:

Fixed a goroutine leak in fileset iterator (not respecting context in goroutine).
Fixed an issue with fileset sharding (path ranges should be inclusive).
Updated and reenabled LargeDeleteRepo test. (removed the test for now, will get the same coverage through a load test)
Reenabled standby tests (may be addressed by bug fix). (still flaky)

I think I mentioned this in an earlier P.R, but it's worth mentioning again.  Representing probabilities as floats and parsing them is going to surprise the user at some point.

If they don't sum to 1, then the user will get something unexpected. Unless you check they sum to 1, but...
There is a good chance they won't actually sum to 1 because of how floating point arithmetic works.  I don't see where that validation happens in here, but I'll just mention that: floatA == floatB is rarely what you want.  You need to check that they are withing some epsilon of each other.

Weights/ratios on the other hand are the same math, but the configuration is done with integers, and the only validation you need to do is check they aren't unset (zero).

We discussed how we are representing the probabilities offline. We are moving to integer based probabilities in the range of [0, 100]. In the case where we are selecting from a set of components based on a probability per component, the probabilities must add up to 100.


[BUG] Ollama not using GPU and not using NPU

Describe the bug
When installing ollama from ollama.org it detects arm64, but all models including llama3.2 don't utilize the GPU/NPU. As result the laptop battery is drained within 1 hour by 45%. And performance is low.
To Reproduce
Just install ollama and run llama3.2 or phi3 or gemma2 or mistral on your command line.
Als see if the npu or GPU is used.
Expected behavior
Models running on NPU.
That was the main reason for buying this laptop.
Host configuration:

OS and version: Windows 11
Chip: x1e-78-100, 32GB

Info
I couldn't find another way to reach the Qualcomm team to report this. My colleagues have the same disappointment. We where under the impression - based on the news Qualcomm published - that ollama World Run on the npu. Running it on the CPU is not what we're interested in.

@kory thank you.
https://www.qualcomm.com/developer/blog/2024/10/qualcomm-partners-with-meta-ollama-on-new-quantized-llama-3-2-models
Calling it an AI PC, CoPilot+ PC because it contains an NPU that is designed to run LLM tasks.
Then telling the model runs on the Snapdragon explicitly mentioning it AI capability, while not utilizing that capability is not what we as consumers read and understand from the marketing communication.
It can be there in the small notes, but it's far from inline with the created perception and demo's. And not in line with what therefor people expect.
Having only 2 hours of battery life when using LLM, on a machine designed to work more than a working day and is designed to with with LLM. Is far below promis. And far below what a consumer fairly can expect from the machine based on it's promotions and the shared information.
What is the expected time to get it running smoothly for all customers?


Keyboard Shortcuts

[ ] ctrl+a https://dev.to/chromiumdev/detecting-select-all-on-the-web-2alo
[x] ctrl+x ctrl+v ctrl+c https://developer.mozilla.org/en-US/docs/Web/API/Element/copy_event and input-node needs to be serializable
[ ] clipboard

Thesis implementation note: Detecting keyboard shortcuts on the web is a PITA. Ctrl+Z isn't detected properly on the German keyboard, Ctrl+A isn't the only way of triggering "select all", ...


[go] update to 1.21 version

Summary
woo! new version is now in our index.
How was it tested?
testscripts should pass :fingers-crossed:

Current dependencies on/for this PR:

main

PR #1436   👈

This comment was auto-generated by Graphite.


Azure Iot Models Repository Readme and Sample Issue

Section link:

Suggestion:
Add const { ModelsRepositoryClient } = require("@azure/iot-modelsrepository");

Section link:

Reason:models doesn't have keys()
Suggestion:
Update to Object.keys(models).length.
@lilyjma , @ramya-rao-a , @ericmitt , @drwill-ms, @xirzec and @jongio for notification.

@YoDaMa Do you agree with the recommendation here? If so, @v-jiaodi can send a PR to fix this

These look like good changes. PR is welcome.

@YoDaMa - Can this be closed now that the associated PR is merged?


Overriding engine functions with GDScript do not works in some situations

Godot version
v4.0.alpha.custom_build [a32f84dda]
System information
Linux PopOS Intel HD Graphics 4600 on Mesa 22.0.1
Issue description
Hi, in the game i'm developing i often override the add_child function to make sure only the nodes i want are added and throw errors otherwise, but i have noticed there are some situations where the override is ignored and the original engine function is called.
I have isolated the problem in a test project that i add just below, but in short, when invoking the add_child method from a variable declared as member of a class, the original engine method is invoked. Meanwhile if the same is done on a variable declared locally within a function, it works perfectly fine.
This problem seems to only affect engine overrided functions, it works fine when overriding functions of other classes.
Thanks for listening and for your hard work, have a good day.
Steps to reproduce

Create a main scene with an associated script (that i will just call main from now on)
Create a new class MyClass that overrides add_child by printing something on the terminal.
Add to main the following var myclass: MyClass
Add to main a _ready function with the following content:

self.myclass = MyClass.new()
self.myclass.add_child(Node.new())

When the last row is executed, the overrided add_child of the class MyClass is not invoked.
On the other hands, when doing the same, but declaring var myclass: MyClass within the _ready instead will make it works correctly.
Minimal reproduction project
OverridingTest.zip

Duplicate of #55024
This is not supposed to work at all 🤔


introduce actions-commit-and-create-pr

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
338

Relevant Lines:
405

💛  - Coveralls


CP-SAT Java: take advantage of cached constants in CpModel.indexFromConstant()

CpModel.indexFromConstant() unnecessarily creates new constants in the model proto instead of using potentially cached ones, that are then immediately pruned during presolve. This patch makes indexFromConstant use newConstant() under the covers which might use cached constants instead.
From an example model I had (note the 9011 constants in before vs 1003 in after). The overall latency cuts down in roughly half (~31ms to 16ms).
Before:
Parameters: max_time_in_seconds: 1 log_search_progress: true num_search_workers: 1 cp_model_probing_level: 0
Optimization model '':
#Variables: 9017 (3 in objective)
 - 1 in [-2147483648,2147483647]
 - 1 in [0,1]
 - 1 in [0,100]
 - 1 in [0,109]
 - 1 in [0,7900]
 - 1 in [2,1001]
 - 9011 constants in {0,1,2,3,4,5,6,7,8,9,10,11,12 ... ,992,993,994,995,996,997,998,999,1000,1001,7900}
#kCumulative: 6
#kInterval: 1001
#kLinear1: 7 (#enforced: 2)
*** starting model presolve at 0.00s
Merged 0 into 0 cliques.
Unsupported constraint type kInterval
- 8008 affine relations were detected.
- 8008 variable equivalence relations were detected.
- rule 'cumulative: removed intervals with no demands' was applied 6 times.
- rule 'false enforcement literal' was applied 1 time.
- rule 'linear: empty' was applied 4 times.
- rule 'linear: fixed or dup variables' was applied 4 times.
- rule 'linear: size one' was applied 2 times.
- rule 'presolve: iteration' was applied 1 time.
- rule 'true enforcement literal' was applied 1 time.
Optimization model '':
#Variables: 1007 (3 in objective)
 - 1 in [0,100]
 - 1 in [0,109]
 - 1 in [0,7900]
 - 1 in [1,1000]
 - 1 in [2,1001]
 - 1002 constants in {1,2,3,4,5,6,7,8,9,10,11,12,1 ... ,992,993,994,995,996,997,998,999,1000,1001,7900}
#kCumulative: 6
#kInterval: 1001
Unsupported constraint type kInterval
#Bound   0.02s best:inf   next:[0,8109]   initial domain
*** starting to load the model at 0.02s
#Bound   0.03s best:inf   next:[119,8109] init
*** starting sequential search at 0.03s
Initial num_bool: 1
#1       0.03s best:120   next:[119,119]   fixed_bools:1/5
#2       0.03s best:119   next:[119,118]   fixed_bools:5/6
#Done    0.03s
CpSolverResponse:
status: OPTIMAL
objective: 119
best_bound: 119
booleans: 6
conflicts: 0
branches: 5
propagations: 5
integer_propagations: 135
restarts: 2
lp_iterations: 0
walltime: 0.0310139
usertime: 0.0310139
deterministic_time: 8.11e-07
primal_integral: 3.66638e-06

After
Parameters: max_time_in_seconds: 1 log_search_progress: true num_search_workers: 1 cp_model_probing_level: 0
Optimization model '':
#Variables: 1009 (3 in objective)
 - 1 in [-2147483648,2147483647]
 - 1 in [0,1]
 - 1 in [0,100]
 - 1 in [0,109]
 - 1 in [0,7900]
 - 1 in [2,1001]
 - 1003 constants in {0,1,2,3,4,5,6,7,8,9,10,11,12 ... ,992,993,994,995,996,997,998,999,1000,1001,7900}
#kCumulative: 6
#kInterval: 1001
#kLinear1: 7 (#enforced: 2)
*** starting model presolve at 0.00s
Merged 0 into 0 cliques.
Unsupported constraint type kInterval
- 0 affine relations were detected.
- 0 variable equivalence relations were detected.
- rule 'cumulative: removed intervals with no demands' was applied 6 times.
- rule 'false enforcement literal' was applied 1 time.
- rule 'linear: empty' was applied 4 times.
- rule 'linear: fixed or dup variables' was applied 4 times.
- rule 'linear: size one' was applied 2 times.
- rule 'presolve: iteration' was applied 1 time.
- rule 'true enforcement literal' was applied 1 time.
Optimization model '':
#Variables: 1007 (3 in objective)
 - 1 in [0,100]
 - 1 in [0,109]
 - 1 in [0,7900]
 - 1 in [1,1000]
 - 1 in [2,1001]
 - 1002 constants in {1,2,3,4,5,6,7,8,9,10,11,12,1 ... ,992,993,994,995,996,997,998,999,1000,1001,7900}
#kCumulative: 6
#kInterval: 1001
Unsupported constraint type kInterval
#Bound   0.01s best:inf   next:[0,8109]   initial domain
*** starting to load the model at 0.01s
#Bound   0.02s best:inf   next:[119,8109] init
*** starting sequential search at 0.02s
Initial num_bool: 1
#1       0.02s best:120   next:[119,119]   fixed_bools:1/5
#2       0.02s best:119   next:[119,118]   fixed_bools:5/6
#Done    0.02s
CpSolverResponse:
status: OPTIMAL
objective: 119
best_bound: 119
booleans: 6
conflicts: 0
branches: 5
propagations: 5
integer_propagations: 135
restarts: 2
lp_iterations: 0
walltime: 0.0163174
usertime: 0.0163174
deterministic_time: 8.11e-07
primal_integral: 3.66638e-06

Thanks


Update azure-stack-pki-certs.md

Update Microsoft Trusted Root Authority Program, List of Participants URL

@nzRegularIT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @nzRegularIT,
I realized I got the relative link wrong in my last response. I fixed the link in another PR. Thanks for letting us know. I'm going to request this PR be closed.
Thanks again,
Pat
#please-close


Class 1 Participation

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added file for class 1 participation
What did you learn from the changes you have made?
How to use hex codes in visualization in Python
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
different combinations of axes placement, font size, visual colours, etc.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
n/a
How were these changes tested?
ran the code
A reference to a related issue in your repository (if applicable)
n/a
Checklist

[x] I can confirm that my changes are working as intended

Pushed Class 2 participation (added comments to code)

Classes 3 and 4 participation added.

Added class participation 5 file


Update student_view_data argument to new format

Missed this on my first pass.

@mikekatz please review

:+1:


password validation policy is breaking existing additional users

TL;DR
When trying to use password validation policy, additional existing users password is getting changed as random_password resource arguments (min_special , special  and length)  causing force replacement. If  min_special , special  and length arguments are added to below lifecycle then it will not break existing additional users.
lifecycle {
ignore_changes = [
min_lower, min_upper, min_numeric
]
}
Expected behavior
password validation policy will be applied on new additional users without any issue and existing users will not impact.
Observed behavior
module.pgsql-db.module.gcp-pgsql.random_password.additional_passwords["adduser2"] must be replaced
-/+ resource "random_password" "additional_passwords" {
~ bcrypt_hash = (sensitive value)
~ id          = "none" -> (known after apply)
~ min_lower   = 0 -> 1
~ min_numeric = 0 -> 1
~ min_special = 0 -> 1 # forces replacement
~ min_upper   = 0 -> 1
~ result      = (sensitive value)
~ special     = false -> true # forces replacement
# (6 unchanged attributes hidden)
}
module.pgsql-db.module.gcp-pgsql.random_password.additional_passwords["adduser3"] must be replaced
-/+ resource "random_password" "additional_passwords" {
~ bcrypt_hash = (sensitive value)
~ id          = "none" -> (known after apply)
~ min_lower   = 0 -> 1
~ min_numeric = 0 -> 1
~ min_special = 0 -> 1 # forces replacement
~ min_upper   = 0 -> 1
~ result      = (sensitive value)
~ special     = false -> true # forces replacement
# (6 unchanged attributes hidden)
}
module.pgsql-db.module.gcp-pgsql.random_password.additional_passwords["adduser6"] must be replaced
-/+ resource "random_password" "additional_passwords" {
~ bcrypt_hash = (sensitive value)
~ id          = "none" -> (known after apply)
~ min_lower   = 0 -> 1
~ min_numeric = 0 -> 1
~ min_special = 0 -> 1 # forces replacement
~ min_upper   = 0 -> 1
~ result      = (sensitive value)
~ special     = false -> true # forces replacement
# (6 unchanged attributes hidden)
}
module.pgsql-db.module.gcp-pgsql.random_password.additional_passwords["adduser7"] will be created

resource "random_password" "additional_passwords" {

bcrypt_hash = (sensitive value)
id          = (known after apply)
keepers     = {

"name" = "pgsql-cftv15-test-06ff322e"
}

length      = 32
lower       = true
min_lower   = 1
min_numeric = 1
min_special = 1
min_upper   = 1
number      = true
numeric     = true
result      = (sensitive value)
special     = true
upper       = true
}

module.pgsql-db.module.gcp-pgsql.random_password.user-password must be replaced
-/+ resource "random_password" "user-password" {
~ bcrypt_hash = (sensitive value)
~ id          = "none" -> (known after apply)
~ min_lower   = 0 -> 1
~ min_numeric = 0 -> 1
~ min_special = 0 -> 1 # forces replacement
~ min_upper   = 0 -> 1
~ result      = (sensitive value)
~ special     = false -> true # forces replacement
# (6 unchanged attributes hidden)
Terraform Configuration
additional_users = [{
    name            = "adduser3"
    password        = null
    random_password = true
    },
    {
      name            = "adduser2"
      password        = null
      random_password = true
    },
    {
      name            = "adduser6"
      password        = null
      random_password = true
    },
    {
      name            = "adduser7"
      password        = null
      random_password = true
    }
  ]

Terraform Version
Terraform v1.3.3
on windows_amd64
+ provider registry.terraform.io/cyrilgdn/postgresql v1.16.0
+ provider registry.terraform.io/hashicorp/google v4.63.1
+ provider registry.terraform.io/hashicorp/google-beta v4.63.1
+ provider registry.terraform.io/hashicorp/null v3.2.1
+ provider registry.terraform.io/hashicorp/random v3.5.1

Your version of Terraform is out of date! The latest version
is 1.4.6. You can update by downloading from https://www.terraform.io/downloads.html

Additional information
No response

@Anand-chenepalli I believe this is related to https://github.com/terraform-google-modules/terraform-google-sql-db/pull/461?

@bharathkkb Yes you are right

Fixed in #461


[TASK] Look into using Twilio library to integrate with Auth building block

Description
Look at Twilio library to communicate with verify service.
Terry:

Twilio provides a "helper" library for Python at https://verify.twilio.com/v2/Service . Is there a reason the code isn't leveraging it?

Acceptance Criteria
Look into Twilio library for integrating with authentication building block.

Closing. Authentication BB is now replaced by Core BB.


Start documenting public API

[ ] Look into docstring formats and tools for generating documentation
[ ] Set up infrastructure for generating documentation from docstrings
[ ] Set up infrastructure for deploying generated documentation
[ ] Start adding docstrings for newly added / touched public modules, functions and classes

Related: https://github.com/runtimeverification/erc20-verification/issues/313

Look into docstring formats and tools for generating documentation

We'll use Sphinx with its own docstring format. This is probably the most common setup by far.


Avoid lens CATSIM galaxies when adding SNe

This pull request adds a data file with the galtileid info of lens galaxies used in the Twinkles field. This way we can tell CATSIM which galaxies to avoid when adding supernovae to the Twinkles Instance Catalogs.

Bravo! Glad to see the back of this little bugbear :-) Thanks both.


feature(apps/dev/prow/prow/release): bump hook's image tag to v20230627-6c92121

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Update dotnet-install.sh sha256sum

Why
Checksum is failing due to changes in the script.
What
Updated the sha256 for the script.
Tests
N/A

It seems that we exceed some size limits for CI.

Fixed via #742


Fix on save

Fix for #11
settings  onSaveUpdateFrontMatter=false and onSaveRenameFile=false where ignored

Thanks for your contribution ❤


Unify functional API function signatures

Many methods have similar behavior, like data augmentation methods and surgery-based methods, but their function signatures do not necessarily match. We should make all of their function signatures as similar as possible without changing the logic.

Resolved (enough) by #715. I apparently didn't type the write string in #715 to make it auto-close this, so closing it manually.


Table does not refresh automatically when I search for data

Hello,
When I search for data, the table does not refresh automatically to display the results found and I have to change pagination or number of rows displayed to see the result.
I did not have this issue, but when I started using Tabs containing multiple Tab generated with a loop, it appeared.
There is any custom options to fix it?
Thanks in advance for your reply.

I thinks it's a critical bug, whats version you used? v3.1.8? if yes, please go back to 3.1.7 for a workaround, I'll fix it quickly.

Please upgrade to v3.2.1 and let me know if the problem still remain. thank

I have upgraded to v3.2.1 and it is working good.
Thank you. :+1:


I ran mkerrors.sh in the unix directory in order to regenerate zerrors_aix_ppc64.go according to the README.
What did you see happen?
The process crashed with a segfault:
bash-5.2$ pwd
/home/jtroy/src/sys/unix
bash-5.2$ CC=gcc-12 GOOS=aix GOARCH=ppc64 ./mkerrors.sh
[lots of generated Go output omitted]

// Signal table
var signalList = [...]struct {
        num  syscall.Signal
        name string
        desc string
} {
        { 1, "SIGHUP", "hangup" },
        { 2, "SIGINT", "interrupt" },
        { 3, "SIGQUIT", "quit" },
        { 4, "SIGILL", "illegal instruction" },
        { 5, "SIGTRAP", "trace/BPT trap" },
        { 6, "SIGLOST", "IOT/Abort trap" },
        { 7, "SIGEMT", "EMT trap" },
        { 8, "SIGFPE", "floating point exception" },
        { 9, "SIGKILL", "killed" },
        { 10, "SIGBUS", "bus error" },
        { 11, "SIGSEGV", "segmentation fault" },
        { 12, "SIGSYS", "bad system call" },
        { 13, "SIGPIPE", "broken pipe" },
        { 14, "SIGALRM", "alarm clock" },
        { 15, "SIGTERM", "terminated" },
        { 16, "SIGURG", "urgent I/O condition" },
        { 17, "SIGSTOP", "stopped (signal)" },
        { 18, "SIGTSTP", "stopped" },
        { 19, "SIGCONT", "continued" },
        { 20, "SIGCLD", "child exited" },
        { 21, "SIGTTIN", "stopped (tty input)" },
        { 22, "SIGTTOU", "stopped (tty output)" },
        { 23, "SIGPTY", "I/O possible/complete" },
        { 24, "SIGXCPU", "cputime limit exceeded" },
        { 25, "SIGXFSZ", "filesize limit exceeded" },
        { 27, "SIGMSG", "input device data" },
        { 28, "SIGWINCH", "window size changes" },
        { 29, "SIGPWR", "power-failure" },
        { 30, "SIGUSR1", "user defined signal 1" },
        { 31, "SIGUSR2", "user defined signal 2" },
        { 32, "SIGPROF", "profiling timer expired" },
        { 33, "SIGDANGER", "paging space low" },
        { 34, "SIGVTALRM", "virtual timer expired" },
        { 35, "SIGMIGRATE", "signal 35" },
        { 36, "SIGPRE", "signal 36" },
        { 37, "SIGVIRT", "signal 37" },
        { 38, "SIGALRM1", "signal 38" },
        { 39, "SIGWAITING", "signal 39" },
        { 48, "SIGSYSERROR", "signal 48" },
        { 49, "SIGCAPI", "signal 49" },
        { 50, "SIGRTMIN", "signal 50" },
        { 57, "SIGRTMAX", "signal 57" },
        { 58, "SIGRECONFIG", "signal 58" },
        { 59, "SIGCPUFAIL", "CPU Failure Predicted" },
        { 60, "SIGGRANT", "monitor mode granted" },
        { 61, "SIGRETRACT", "monitor mode retracted" },
        { 62, "SIGSOUND", "sound completed" },
        { 63, "SIGMAX", "secure attention" },
./mkerrors.sh: line 793: 24052120 Segmentation fault      (core dumped) $GORUN ./_errors

What did you expect to see?
I expected mkerrors.sh to produce complete output on aix/ppc64 without crashing.
Debugging further:
bash-5.2$ CC=gcc-12 GOOS=aix GOARCH=ppc64 ./mkerrors.sh -g
[stdout omitted]
./mkerrors.sh: line 793: 20316654 Segmentation fault      (core dumped) $GORUN ./_errors
bash-5.2$ gdb _errors core
GNU gdb (GDB) 14.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc64-ibm-aix<IP_ADDRESS>".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from _errors...
Core was generated by `_errors'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x10000b54 in strncpy ()
(gdb) up
#1  0x100008e4 in main () at _errors.c:245
245                     strncpy(buf, strsignal(e), sizeof(buf) - 1);
(gdb) p e
$1 = 255
(gdb) p signals[i]
$2 = {num = 255, name = 0x10001878 <_GLOBAL__FD__errors+1564> "SIGMAX64"}

The program attempts to call strsignal() against SIGMAX64, which is not a real signal and is not a valid thing to do. Digging further, it seems the intent is to filter SIGMAX64 out with grep, but using a GNU syntax which doesn't behave the same way with AIX's grep. It looks like it may have broken in x/sys #137. The OS is AIX 7.3.
I've submitted a proposed fix in https://github.com/golang/sys/pull/217

Related Issues and Documentation

runtime: SIGSEGV: segmentation violation #69247
fatal error: unexpected signal during runtime execution [signal SIGSEGV: segmentation violation code=0x2 addr=0xc002000000 pc=0x46e698]  Linux version 5.10.135-yocto-standard  #58377 (closed)
src/runtime/signal_unix.go:202    Normal gameplay and subsequent code execution #67874 (closed)
runtime: spurious SIGSEGV in systemstack() #68632
cmd/go: get in docker buildx gets SIGSEGV error #40969 (closed)
runtime: cgo stuck because of go signal handler went into dead loop #56649 (closed)
cmd/compile: SIGBUS unaligned access on mips64 via qemu-mips64 #67160 (closed)
runtime: segmentation fault on linux/arm when GODEBUG=sbrk=1 #33159 (closed)
SIGSEGV: segmentation violation code=0x1 - help #49992 (closed)
runtime: getArgInfo nil dereference #17471 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

CC @golang/runtime, @ianlancetaylor,  @bradfitz, @tklauser per owners for x/sys/unix.


Keyset connections

Context
Allow to sort items inside of connection by two fields, where the first field can be not unique (e.g., created_at + id)
What's inside

[x] Keyset ASC
[x] Keyset DESC

Checklist:

[x] I have added tests
[x] I have made corresponding changes to the documentation

@bibendi I've cherry-picked API changes from another branch (the last commit): they include API changes (no breaking ones!) as well as specs for them. I tried it out in the real project, looks like it works (connections.add seems to work as well).

Could you please release a new version when you have a second?


Integration tests for theme method

Test Scenario 1: Valid Input

Provide a valid Context object to the theme method.
Call the theme method with the specified Context object.
Verify that the returned Theme object is not null and has the expected values.

Expected Result: The method should return the expected Theme object based on the specified color scheme.
Test Scenario 2: Invalid Input

Provide a null Context object to the theme method.
Call the theme method with the specified Context object.
Verify that the method throws a NullPointerException.

Expected Result: The method should throw a NullPointerException when provided with a null Context object.
Test Scenario 3: Unknown Color Scheme

Create a custom Configuration object with an undefined color scheme.
Set the Context object's resources to the custom Configuration object.
Provide the custom Context object to the theme method.
Call the theme method with the specified Context object.
Verify that the returned Theme object is not null and has the expected values.

Expected Result: The method should return the default Theme object when provided with an unknown color scheme.

outdated


Feat/guidelines ds

some icones size fixed
add guidelines UX
add documentation

Wow, that's a huge PR and a lot of work! Thanks very much!
Just noticed that the following lines are still in the package.json, but I think they are useless (l. 18 & 19):
    "css": "npm -C ./storybook/styles run css",
    "css:build": "npm -C ./storybook/styles run css:build",

Maybe you can remove them as well?

Sure, you're right @gcruchon , I propose to do this in another PR because this subject of this PR, ok ?

No problem. Let's add an issue, then? I can contribute :)

Hello,
Looks like there are some broken dependencies in non committed pug files.
E.g. : /storybook/design-system/src/components/form/mixins/mixin-form-field-card.pug, line 7:
          include ../../../pages/style/icons/templates/ok.pug

This template has moved to ../../../pages/guidelines/icones/templates/ok.pug
WIth a search in files on /style/icons/templates/ you should find all of them (100+ occurences in 48 files)
BTW, the french icones lacks a bit of consistancy here :)


Add FOOBAR to pull_request_template.md

Description

I am proposing we add the H1 heading "foobar" to the PR template  as requested in the ticket linked below. To see the change, you can preview the PR template in this PR.
https://issues.redhat.com/browse/RHCLOUD-XXXXX
Screenshots

Before

After

Checklist ☑

[x] PR only fixes one issue or story (open new ticket & PR for others)
[x] Diff reviewed for extraneous console statements, comments, files, incorrect file renaming (not using git mv), whitespace, etc.
[x] All PR checks pass locally

[x] Build
[x] Lint
[x] Test
[x] E2E

[x] UI best practices adhered to
[x] Commits squashed (2-3 commits per PR maximum, 1 is ideal)
[x] Commit(s) have meaningful message

[ ] (Optional) Release: Hold merge - not ready to be deployed to stage
[ ] (Optional) QE: Needs QE attention (OUIA changed, percieved impact to tests, no test coverage)
[ ] (Optional) QE: Has been mentioned
[ ] (Optional) UX: Needs UX attention (end user UX modified, missing designs)?
[ ] (Optional) UX: Has been mentioned

@fhlavac how does this look to you?

@florkbr looks good! Tried to shorten it a bit ^^
I am also thinking about the optional checklist section.. maybe it's not needed.
Maybe hold merge could be replaced by a label/converting back to draft.
And then QE and UX attention - not sure if checking a checkbox saying that it needs attention has any effect. UX and QE wouldn't have probably time to browse our PRs. So maybe reword the check items to CONFIRM that QE and UXers are aware and ok with the changes so there should be no hidden surprises for them? (changed OUIAs, design changes compared to mockups...)

@fhlavac @karelhala the simplified version looks good - however I personally feel we should have explicit checkboxes for each check or at minimum the general process we expect developers to run locally - even if they're enforced in the pipeline. I think this serves several purposes:

Reminds developers to run these locally - especially in repos that may have different commands for each of these "steps" or repos that do not have these steps (makes tech debt more obvious)
Drives consistency in the engineers process and mental model when developing code locally
Makes clear the MVP of opening a PR in our repos (while our engineers may already do this, new engineers or engineers from outside the team may not know the process)
Allows us to more easily identify if we have a process issue or a disconnect with our engineers/pipeline if the checkboxes are all checked and the PR is failing

We could also use something like https://typicode.github.io/husky/ to enforce these checks are run before commits if we don't want the checklist, but that would require updating every repo to use it.

Let's meet in the middle and add checkbox for All PR checks pass locally. No need to list all of them, because some of them will be different in some repositories. But this checkbox will at least stop the dev and let them think about PR checks and what it does.
Please let's not use husky. Whenever I've seen husky I had to remove it, because commit ammends run these as well and often times they break and I am unable to push even a draft PR.

Sounds good to me!

@karelhala @fhlavac sounds good to me too (single checkbox for PR checks pass locally). I also agree we should avoid Husky unless completely necessary - I'm just pointing out it is another tool in our toolbox :)