text:
Implement OpenSearch

Enables quick searches like this:

Does this mean browsers will go to https://wikipendium.no/search/?q={searchTerms} to display search results?
I don't think that works, currently.

Ah, I forgot the 'www' part. Fixed that now.

Ah, I forgot the 'www' part. Fixed that now.

Interesting, that redirect should have worked, in my opinion. Will have to update the nginx config, then.

Does this mean browsers will go to https://wikipendium.no/search/?q={searchTerms} to display search results?
I don't think that works, currently.

It does work if it's https://www.wikipendium.no/search/?q={search_term}

Yup, if you rebase the branch @iver56 we can get this in I think :smile:

Rebased

Thanks!

authors: cristeahub iver56 sigvef stianjensen


text:
[Fix] Osc manager portgroup registration

New port group was not registered in the dictionary.
This was preventing multiple OSCInput instances to use the same port for different instances.
Fixes : #87

Seems it messed up with my fork again, gonna re fork and do it again

hi vux.
any progress with this? There was quite a lot of refactoring on the dev branch last week. I hope this doesn't cause too many merge issues... :(

That was fixed by other PR, that's why I closed this one

source: gharchive/pull-request

authors: mrvux pixtur

license: MIT

license_type: permissive

license_source: github-api


text:
feat: implement shellcheck lints in command blocks (#191)

This pull request adds a new rule to wdl-lint.

Rule Name: ShellCheckRule

Describe the rules you have implemented and link to any relevant issues.
I have implemented a lint rule that runs shellcheck against command sections and reports the comments as diagnostics. This is to address #191 .
Before submitting this PR, please make sure:

[x] You have added a few sentences describing the PR here.
[x] You have added yourself or the appropriate individual as the assignee.
[x] You have added at least one relevant code reviewer to the PR.
[x] Your code builds clean without any errors or warnings.
[x] You have added an entry to the relevant CHANGELOG.md (see
["keep a changelog"] for more information).
[x] Your commit messages follow the [conventional commit] style.

Rule specific checks:

[x] You have added the rule as an entry within RULES.md.
[x] You have added the rule to the rules() function in wdl-lint/src/lib.rs.
[x] You have added a test case in wdl-lint/tests/lints that covers every
possible diagnostic emitted for the rule within the file where the rule
is implemented.
[x] If you have implemented a new Visitor callback, you have also
overridden that callback method for the special Validator
(wdl-ast/src/validation.rs) and LintVisitor
(wdl-lint/src/visitor.rs) visitors. These are required to ensure the new
visitor callback will execute.
[ ] You have run wdl-gauntlet --refresh to ensure that there are no
unintended changes to the baseline configuration file (Gauntlet.toml).
[ ] You have run wdl-gauntlet --refresh --arena to ensure that all of the
rules added/removed are now reflected in the baseline configuration file
(Arena.toml).

There's still a lot of testing and polishing to do, which will undoubtedly reveal some issues, but I wanted to open for comments before I went any further in case I'm way off from what's desired.

Rebased. Gauntlet in arena mode is giving me the following:
thread 'main' panicked at /home/spencer/projects/wdl/gauntlet/src/lib.rs:258:25:
duplicate diagnostic: `ww-fastq-to-cram.wdl:101:20: note[ShellCheck]: `shellcheck` reported the following diagnostic` at /ww-fastq-to-cram.wdl:101

so I'll look into that tomorrow.

@a-frantz  Here's a link to an example of a new install-shellcheck action running on my fork.

@a-frantz Here's a link to an example of a new install-shellcheck action running on my fork. One thing to note is Ubuntu being Ubuntu only has 0.8.0 by default. macOS and Windows will always run latest. Maybe a good thing to be testing across versions. But if we want to forego the apt caching we could just pull from GH the same as Windows.
edit: it's also suspicious that Arena passed on Windows when the duplicate diagnostic bug was still present. Makes me think it probably isn't finding the executable.

My two cents: let's just always pull from latest on everything (including Mac). It makes it a bit more straightforward to maintain the Github action associated with that, and it also ensures that every platform always works with the bleeding edge Shellcheck.

I'm starting to see why the miniwdl folks went with literals instead of variables / expansions when substituting placeholders.
The common false positives I'm seeing from Arena are:
SC2076
❌ read_group.wdl:200:43: note[ShellCheck]: Remove quotes from right-hand side of =~ to match as a regex rather than literally.

caused by:
| [[ ~{read_group.ID} =~ ~{restrictive_pattern} ]]

because we're replacing both of these placeholders with double-quoted expansions.
and SC2001
❌ util.wdl:132:9: note[ShellCheck]: See if you can use ${variable//search/replace} instead.

caused by:
echo ~{string} | sed 's/~{delimiter}/\n/g' > split_strings.txt

because with a bash variable you can use the suggested syntax but that obviously doesn't apply to WDL placeholders.
as well as SC2066:
❌ samtools.wdl:577:21: note[ShellCheck]: Since you double quoted this, it will not word split, and the loop will only run once.

caused by:
 for file in ~{sep(" ", bams)}

Though, this one is also basically identical to one that miniwdl has to suppress.
I've found (what I think) is an elegant solution to determine whether to use a literal or expansion, which reduces but does not eliminate false positives.
That being said, I think miniwdl's approach of guessing the placeholder's type and using an appropriate literal would be overly complicated here. So I think it comes down to the severity and frequency of the lints we end up needing to suppress. I still think (with the commit I'm about to push) that we're better off than always using literals. We could probably spend weeks working to get the false positives to an absolute minimum without suppressing anything, but that feels a bit bikesheddy to me. Of course I will defer.

I'm starting to see why the miniwdl folks went with literals instead of variables / expansions when substituting placeholders.

So am I. However with wdl-lint currently being based off of wdl-ast, we don't have a good way of knowing the right type of literal to inject. We've discussed potentially refactoring wdl-lint to be based off of wdl-analysis so that we'd have access to resolved type information. That refactor would certainly be OOS for this PR, but would potentially simplify this problem by a great amount.
I'm thinking we shouldn't expend a large amount of effort eliminating these false positives with the current AST-based implementation.
@thatRichman can you remove this rule from the default set of rules (as Clay originally suggested) so that this is opt-in only?
We should re-architect wdl-lint so that it can have the results of a full static-analysis and revisit this rule at that time. In the meantime, this rule can be in a bit of a beta stage. It's certainly still useful and worth merging into main, but the false-positive lints are too big an issue to include this in the default rule set IMO.

Sounds good. I'll disable the shellcheck-install action (once I get it working on all OSes) so that it be re-enabled at a later date.
I know the intent is to support non-default rules in sprocket eventually, but should I put any work into supporting non-default rules in the dev CLI in this PR? Seems OOS, so happy to throw in an issue if there isn't one already.
Also, I think I will wait for the resolution of #268 before making any final changes to this PR, as it throws off diagnostic placements.

I know the intent is to support non-default rules in sprocket eventually, but should I put any work into supporting non-default rules in the dev CLI in this PR? Seems OOS, so happy to throw in an issue if there isn't one already.

I think it should be straightforward to handle this as a special case (by adding a --shellcheck flag to the wdl lint dev command), but I wouldn't call it necessary for merging. You could leave that change out and open an issue as well 🤷 your call.

@a-frantz  This should be ready for final review. One question I have is whether or not to run gauntlet with shellcheck enabled (I added this option), since this rule is in 'beta' and thus gauntlet will report missing lints if not run with --shellcheck (if it has previously been blessed while using --shellcheck).
Also, I fully intend to squash these 39 commits into 1. I can do that before or after final review, whatever you prefer.

Sweetness! Will give this a review in the morning. I also added the rest of the team as reviewers in case I miss something.

One question I have is whether or not to run gauntlet with shellcheck enabled (I added this option), since this rule is in 'beta' and thus gauntlet will report missing lints if not run with --shellcheck (if it has previously been blessed while using --shellcheck).

IMO we leave it out of gauntlet/arena for now. I imagine it is going to add a boatload of diagnostics, and we like to review each one. Considering we know upfront some portion will be false positives, I don't think it's worth the effort.

Also, I fully intend to squash these 39 commits into 1. I can do that before or after final review, whatever you prefer.

We squash as part of the merge, so you shouldn't need to do anything to deal with it.

@thatRichman can you add a test that #shellcheck disable= directives work as expected?

We're pretty dang close here @thatRichman . Please get the CI all green, then I think this will have my approval
https://github.com/stjude-rust-labs/wdl/blob/main/CONTRIBUTING.md#the-ci-has-turned-red-how-do-i-make-it-green-again
The general rule we follow is to require approval from two core team members for a merge.

@a-frantz  Sounds good. One thing to note is that I did end up needing to re-enable shellcheck install in the CI. This is because if shellcheck isn't present, the first lint test that is run will end up with the 'shellcheck not found' warning, and the source.errors for the shellcheck-* lints will be empty. I thought about modifying the lints test script to selectively skip the shellcheck lints, but this would not address the 'missing shellcheck' lint.
Here is an example of the modified CI going green on my repo but I don't think there's any way to reflect that here unless we merge the actions changes to main in a separate PR first.

authors: a-frantz claymcleod thatRichman

repo: stjude-rust-labs/wdl


text:
How to use svd file in VS Code or STM32 Cube IDE

Hi, I would like to use patched svd, but I can not because in VS-Code (Cortex Debug Extension) return error and in STM32 Cube IDE in debug mode I don't see pheripherials:

Is any manner to fix that?

I found some information about similar problem here:
https://github.com/Marus/cortex-debug/issues/513

I'd suggest you to use probe-rs-debugger
But I don't know how good it works out of Rust world.

Perhaps patched files are not compatible with CMSIS schema?

They are. We check them with xmllint against https://github.com/stm32-rs/stm32-rs/blob/master/svd/cmsis-svd.xsd
Although derivedFrom link resolution is not a trivial task, so ST avoid to use them.

As alternate solution you could try to expand derived registers with
svdtools convert --expand <IN_PATH> <OUT_PATH>

before pass SVD to cortex-debug

It's better, now It works but output file contains mistakes:

Enumerate fields do not contain numbers and description (not shown on figure) is set as "H0" for all fields.
It looks like bug in parser. Output file:
<register>
          <name>HR0</name>
          <displayName>HR0</displayName>
          <description>digest registers</description>
          <addressOffset>0xC</addressOffset>
          <size>0x20</size>
          <access>read-only</access>
          <resetValue>0x00000000</resetValue>
          <fields>
            <field>
              <name>H</name>
              <description>H0</description>
              <bitOffset>0</bitOffset>
              <bitWidth>32</bitWidth>
            </field>
          </fields>
        </register>
        <register>
          <name>HR1</name>
          <displayName>HR0</displayName>
          <description>digest registers</description>
          <addressOffset>0x10</addressOffset>
          <size>0x20</size>
          <access>read-only</access>
          <resetValue>0x00000000</resetValue>
          <fields>
            <field>
              <name>H</name>
              <description>H0</description>
              <bitOffset>0</bitOffset>
              <bitWidth>32</bitWidth>
            </field>
          </fields>
        </register>

I tried to modify input file but with no result.  In my opinion, displayName and field Name should have variable syntax to enumerate value
<register>
          <dim>5</dim>
          <dimIncrement>0x4</dimIncrement>
          <dimIndex>0-4</dimIndex>
          <name>HR%s</name>
          <displayName>HR0</displayName>
          <description>digest registers</description>
          <addressOffset>0xC</addressOffset>
          <size>0x20</size>
          <access>read-only</access>
          <resetValue>0x00000000</resetValue>
          <fields>
            <field>
              <name>H</name>
              <description>H0</description>
              <bitOffset>0</bitOffset>
              <bitWidth>32</bitWidth>
            </field>
          </fields>
        </register>

Perhaps is it bug in svdtools during the patch operation?

I don't understand what the issue and what you mean under variable syntax

It means that :
HR%s has "%s" to expand (0,1,2....) ,  but
HR0 and
H
H0
not.
It should looks like:
HR%s
...
HR%s
...
H%s
...
H%s

I see two issues.

SVD should contains more fields able to enumerate like above.
Valid handling this case through svdtools :)

Moreover, You said that files are compatible with CMSIS schema but CMSIS tools returned errors after scans. For example svdconv tool from https://github.com/ARM-software/devtools return over 1k+ errors for patched files and 0 errors for vendor files. I know that this repo is kind of fork but It should align with widthly community that using stm32, both Rust and the Others.

Saying about displayName I could agree. We just never worry about this tag as it is not part CMSIS specification and we've never used it for our goals.
Saying about H name of fields they were renamed consciously to collect HRx registers in array. See https://github.com/stm32-rs/stm32-rs/blob/master/devices/common_patches/hash/hash_v1.yaml

About enhancment:
The user in above linked issue said:
https://github.com/Marus/cortex-debug/issues/513#issue-1034561233

This SVD contains a enumeratedValues field that ST's SVD does not have.
thought that the cause of the error was probably that enumeratedValues deriveFrom was a forward >reference, so I changed the order of the SVD description so that the definition of enumeratedValues comes >first, and now it can be loaded.
.....
I couldn't find a spec on whether forward references are allowed, so I proposed this as an issue, but this may >not be allowed.

Perhaps the changing the order of the definition of enumeratedValues is good point to be align with CMSIS checking tools? It could using patched SVD with widthly group, various extensions related to Cortex debug and official stuff from ST :)

About enumeratedValues derivedFrom. I've remembered that historically we are supporting 1 unspecified case - link name (dis_en_enum) without field name (clk) if both derived and linked enums are in same register.
Accordingly to CMSIS there must be clk.dis_en_enum: https://www.keil.com/pack/doc/CMSIS/SVD/html/elem_registers.html#elem_enumeratedValues
Try to change derivedFrom="ENUM" with derivedFrom="FIELD.ENUM". Is this solves issue with Cortex-Debug.
Saying about svdconv checking open different issue for this, please.

I think that we could close the issue because other issue has been opened and is a real problem with svd file. When we will be met requirements about the svd file it will be possible to use in VSCode and others IDE.
https://github.com/stm32-rs/stm32-rs/issues/825

source: gharchive/issue

authors: KamilDuljas burrbull


text:
.defmt section found, but no version symbol

I get this when trying to run the examples
$ cargo run --example blinky --features stm32g474 -- --chip STM32G474RBTx
Compiling stm32g4xx-hal v0.0.1
    Finished dev [unoptimized + debuginfo] target(s) in 0.21s
     Running `probe-run --connect-under-reset target/thumbv7em-none-eabihf/debug/examples/blinky --chip STM32G474RBTx`
(HOST) INFO  flashing program (9 pages / 9.00 KiB)
(HOST) INFO  success!
Error: `.defmt` section found, but no version symbol - check your linker configuration

Adding the line use defmt_rtt as _; in the blinky example makes the error go away, however there is no sign of the logging output. There is no difference when replacing info!() with error!().

Adding use defmt_rtt as _; to the example/hello (which uses cortex_m_semihosting::hprintln to print) gives
Compiling stm32g4xx-hal v0.0.1 (stm32g4xx-hal)
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
     Running `probe-run --connect-under-reset target/thumbv7em-none-eabihf/debug/examples/hello --chip STM32G474RBTx`
(HOST) INFO  flashing program (13 pages / 13.00 KiB)
(HOST) INFO  success!
────────────────────────────────────────────────────────────────────────────────
────────────────────────────────────────────────────────────────────────────────
stack backtrace:
   0: __c_m_sh_syscall
(HOST) WARN  call stack was corrupted; unwinding could not be completed
(HOST) ERROR error occurred during backtrace creation: debug information for address 0x80017d4 is missing. Likely fixes:
        1. compile the Rust code with `debug = 1` or higher. This is configured in the `profile.{release,bench}` sections of Cargo.toml (`profile.{dev,test}` default to `debug = 2`)
        2. use a recent version of the `cortex-m` crates (e.g. cortex-m 0.6.3 or newer). Check versions in Cargo.lock
        3. if linking to C code, compile the C code with the `-g` flag

Caused by:
    Do not have unwind info for the given address.
               the backtrace may be incomplete.
(HOST) INFO  device halted without error

To verify, I have tested https://github.com/knurling-rs/app-template which works as expected.
Am I doing something wrong or is this a bug?
stm32g4xx-hal version: 0.0.1
device: Nucleo-G474RE (STM32G474RE)

Reading https://docs.rs/defmt-rtt/0.4.0/defmt_rtt/
NOTE when using this crate it’s not possible to use (link to) the rtt-target crate

could this be the problem?


text:
Add support for interrupts to DMA API

This pull request is based on #14. I recommend reviewing/merging that pull request first, before this one.
I have additional commits to test this against the Tlera Corp Gnat here:
https://github.com/braun-embedded/stm32l0xx-hal/compare/dma-interrupts...braun-embedded:dma-interrupts-gnat
cc @lthiery

Rebased, ready for review.


text:
Update lpc55-pac repository

Moved the repo into the lpc55 organization, keeping up :)
Do you think it would make sense to build the PAC as well? For stm32 it's probably too much, but for lpc55 (on my relatively beefy machine...) a simple cargo build takes ~30 seconds, which seems acceptable?

Hopefully if svd2rust generates the crate without error it should always build, but it's a good idea to check. Maybe just cargo check will be a bit quicker than build? Would you like to try that in this PR or make it a separate one?

Yeah, added. Check is only slightly faster (~28s vs ~32s to build on my machine), but it's sufficent.

bors merge

Looks like this has started failing (https://github.com/stm32-rs/svdtools/runs/1998491029), any ideas?

authors: adamgreig nickray


text:
Connected SPI bus to on-board Flash and SPI peripheral

Added Connection to on-board FLASH and SPI bus.
Resolved ERR_FLSH error
Storing to Flash and booting from Flash working

Oh, seems like the SPI signals got lost during some earlier update of this wrapper... 🙈 Thanks for fixing this!

authors: lovelesh-mis stnolting


text:
Memory Leak

It seems to me that this module is leaking both memory and file descriptors in nginx versions 1.10 and 1.9.14. Concretely it leaks file descriptors (and memory) when built as a dynamic module in 1.10. When built 'statically' it only leaks memory.
The leaked file descriptor points to /dev/urandom
I've tried Ubuntu PPA's and Nginx official packages. The first one has this module built statically, whereas I compiled myself dynamically for Nginx's official package.

Give concrete examples and configurations, I can't guess what is happening in your system with your description.
In any case keep in mind that the memory and file description problems can come from this module, but the problem is usually caused by the PAM modules configured, not the module (i.e. the libpam-ldap module has memory problems when loaded dynamically)

I've tried compiling the module with nginx versions 1.8.1, 1.10.0 and 1.9.14 on Ubuntu Trusty 14.04 + libpam-ldap 1848.5.ubuntu
I've tried both ngx_http_auth_pam_module 1.5.1 and 1.4. Version 1.5.1 leaks both memory and filedescriptors and 1.4 just memory.
I'm doing static compilation now. I'm basically trying the example from the README + an ab run to throw 20-30k logins. The memory usage by nginx increases and it is never fully freed.
The ab I run is something like: ab -n 25000 -c 10 -A user:password https://foo.bar.com

I will try libpam-ldapd to see whether this problem reproduces there or not

As I've already said, that is known bug from libpam-ldap, see:
https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/1418265

👍 , thank you!

authors: stogh zonzamas

license_source: bigquery


text:
Extend to include other files

web.config  look for "password="

/.git/HEAD look for ref:


text:
adding conditional addition of global pull secret to EDIT environment variable

Signed-off-by: Nathan Weatherly nweather@redhat.com
This is in response to the following bug: https://github.com/stolostron/backlog/issues/22164
The change is only to the chart regeneration script. After this change is merged, the chart regeneration action needs to run.
This should not merge before the corresponding upstream change made to accept the new argument.
PR for the upstream change here: https://github.com/open-cluster-management-io/managed-serviceaccount/pull/40/files
The resulting argument yaml looks like this:
      containers:
      - args:
{{- if .Values.global.pullSecret }}
        - --agent-image-pull-secret={{ .Values.global.pullSecret }}
{{- end }}
        - --leader-elect=true
        - --agent-image-name={{ .Values.global.imageOverrides.managed_serviceaccount }}
        - --agent-install-all=false
        - --feature-gates=EphemeralIdentity=true

This is a draft and requires further testing.

If this is going to update the chart I'd like those changes to be included in the PR so it is atomic

Can do-- I only ask that we run the git action after we merge <whatever we're going to merge> to make sure the action that I ran locally lines up with what github expects.

Related slack conversation: https://coreos.slack.com/archives/C02K4843LMQ/p1651758804837399
Goal: Add global pull secret to deployment's env variable (but only for managed serviceaccount chart)

/assign @TheRealHaoLiu

@TheRealHaoLiu although we hit that bug around secret mis-typing, the environment i spun up w/ this code proved that the image pull secret is at least passed to the managed service account as an environment variable. Reckon we can merge this now, then continue testing?

green path tested
when global pull secret is set the env var is correctly injected into the deployment
managed-serviceaccount-e2e passed on non-OCP cluster (kind)

negative test-case passed
when image pull secret is not set (and proxyConfigs not set) the container deploy successfully without env var

authors: JakobGray TheRealHaoLiu nathanweatherly

repo: stolostron/backplane-operator


text:
Using recreate strategy in cluster-proxy-addon-manager.

Description
This PR change rollout strategy of cluster-proxy-addon-manager to be "Recreate".
Related Issue
https://issues.redhat.com/browse/ACM-11947
Changes Made
cluster-proxy-addon-manager doesn't using leader election to start controller, so in upgrade case from 2.10 to 2.11, the old pod and new pod will override the managedclusteraddon with different value. Which will create many CSRs and cause cluster-proxy-addon pending.
In 2.11, we have to turn the rollout strategy to "Recreate" to avoid new pods and old pods run together, we also working on adding leaderelection on cluster-proxy-addon-manager.
Screenshots (if applicable)
Add screenshots or GIFs that demonstrate the changes visually, if relevant.
Checklist

[x] I have tested the changes locally and they are functioning as expected.
[x] I have updated the documentation (if necessary) to reflect the changes.
[x] I have added/updated relevant unit tests (if applicable).
[x] I have ensured that my code follows the project's coding standards.
[x] I have checked for any potential security issues and addressed them.
[x] I have added necessary comments to the code, especially in complex or unclear sections.
[x] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
Definition of Done

[x] Code is reviewed.
[x] Code is tested.
[ ] Documentation is updated.
[ ] All checks and tests pass.
[ ] Approved by at least one reviewer.
[ ] Merged into the main/master branch.

/assign @dislbenn

/lgtm

authors: dislbenn xuezhaojun


text:
remove unused dependencies

Refer to the go 1.22 release notes

go get is no longer supported outside of a module in the legacy GOPATH mode (that is, with GO111MODULE=off). Other build commands, such as go build and go test, will continue to work indefinitely for legacy GOPATH programs.

Before upgrading to 1.22, this PR is to remove GO111MODULE=off and replace go get with go install for dependencies, since the release repo reports the below error when just upgrading the golang version to 1.22.
INFO[2024-09-19T02:18:00Z] which: no kustomize in (/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/opt/sonar/bin:/usr/local/kubebuilder/bin)
which: no patter in (/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/opt/sonar/bin:/usr/local/kubebuilder/bin:/usr/local/kubebuilder/bin)
Installing patter ...
go: modules disabled by GO111MODULE=off; see 'go help modules'
make: *** [Makefile:42: dependencies] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-09-19T02:17:59Z"}
INFO[2024-09-19T02:[18](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/56897/rehearse-56897-pull-ci-stolostron-clusterlifecycle-state-metrics-backplane-2.7-check/1836587508071141376#1:build-log.txt%3A18):00Z] Ran for 11m55s
ERRO[2024-09-19T02:18:00Z] Some steps failed:
ERRO[2024-09-19T02:18:00Z]
  * could not run steps: step check failed: test "check" failed: could not watch pod: the pod ci-op-psb715dd/check failed after 27s (failed containers: test): ContainerFailed one or more containers exited
  *

Good catch!
/lgtm
/hold
Unhold if you feel good to go @haoqing0110

/unhold


text:
Use patternfly log viewer component in search logs

Signed-off-by: Zack Layne zlayne@redhat.com
This replaces the current custom logs view with the new patternly reusable logs viewer.

/hold

/unhold

repo: stolostron/console


text:
ACM-2647: Problems with time window links (#2446)

ACM-2647: Problems with time window links

Signed-off-by: Maggie Chen magchen@redhat.com

use link with generate path

Signed-off-by: Maggie Chen magchen@redhat.com

fix edit issue

Signed-off-by: Maggie Chen magchen@redhat.com

Add test cases

Signed-off-by: Maggie Chen magchen@redhat.com

Add more test coverage

Signed-off-by: Maggie Chen magchen@redhat.com
Signed-off-by: Maggie Chen magchen@redhat.com
https://issues.redhat.com/browse/ACM-2647

/retest

/lgtm


text:
lower MaxConcurrentReconciles to 1 for helmRelease controller for les…

…s memory consumption

[X] I have taken backward compatibility into consideration.

Two issues are fixed:

lower MaxConcurrentReconciles to 1 for helmRelease controller.
With the previous 10 concurrent setting, we identified there is OOM killed issue in the footprint assessment test env where the managed cluster is SNO cluster with limited memory. Setting it to 1 stabilized the running of the application-manager pod

https://issues.redhat.com/browse/ACM-8936

take the chance to upgrade the missing pkg github.com/docker/docker, which is reported by the git repo Dependabot

/test test-unit

/approve
/lgtm

authors: mikeshng xiangjingli


text:
[release-2.10] Delete cluster-specific broker resources on add-on removal

Manual backport of https://github.com/stolostron/submariner-addon/pull/1456

/override "Red Hat Konflux / submariner-addon-acm-210-on-pull-request"

/cc @vthapar

/override "Red Hat Konflux / submariner-addon-acm-210-on-pull-request"

/override "Red Hat Konflux / submariner-addon-acm-210-on-pull-request"

/retest

/lgtm

/approve

authors: dfarrell07 skitt tpantelis

repo: stolostron/submariner-addon


text:
Swap: ton not received

Hello,
I am facing an issue with swapping Amber tokens for TON using the DEX SDK. Amber tokens are deducted from my wallet, but I do not receive TON as expected. I would like to understand what might be going wrong and how to fix it.
Here is the hash of the transaction:
https://tonviewer.com/transaction/bcfac1b0c02a6c3a1a452d778a37c1486a34c96891283ad926f51229c40c1f70
try {
    const client = new TonClient({
        endpoint: 'https://toncenter.com/api/v2/jsonRPC',
        apiKey: '***'
    });

    const router = client.open(new DEX.v1.Router());

    const swapParams = await router.getSwapJettonToTonTxParams({
        userWalletAddress: user.address,
        offerJettonAddress: 'EQBv2cEJ-T-1GNRdzaY_JYoJvpAISuFHOKmJZPQnoUqEHTlU',
        offerAmount: toNano(10000),
        proxyTon: new pTON.v1(),
        minAskAmount: '1',
        queryId: +Date.now(),
    });

    console.log("Swap Parameters: ", swapParams);

    await user.walletInstance.send(user.secretKey, swapParams);

    console.log("Transaction sent successfully!");

} catch (e) {
    console.log(e);
}

// Supporting function
async send(secretKey, txParams) {
    const seqno = await this.contract.getSeqno();

    return await this.contract.sendTransfer({
        seqno,
        secretKey: secretKey,
        sendMode: SendMode.PAY_GAS_SEPARATELY,
        messages: [
            internal({
                ...txParams,
                bounce: true,
            })
        ]
    });
}

@kkrenev
You’re experiencing an infinite swap issue which might be caused be the following reasons…
Network Issues: Sometimes, network congestion can cause transactions to get stuck. Check if the TON network is experiencing high traffic.
Gas Fees: Ensure that you're setting an appropriate gas fee. If the gas price is too low, your transaction might not get processed, causing it to retry endlessly.
Contract Issues: If the swap involves a specific token or contract, there might be issues with that contract. Make sure the token is supported and the contract address is correct.
Browser Issues: Try clearing your browser cache or using a different browser to see if that resolves the issue.

@kkrenev
If none of the above is related to why you’re having this issue
This will then be review by the support team. Visit the live support page to initiate a chat with an agent for further assistance via live agent.

Access the Live Chat:
•	Navigate to our website’s home page.
•	Look for the chat icon located at the bottom right corner of the screen and start a 💬.
Regards

with same code usdt to ton its ok

The transaction that I made with my hands on the site https://tonviewer.com/transaction/eb994351155178d445634d35ab4d91eef1e66fa0ccc662e7c321f79d77bb5ea0
can you tell me what the difference is and how to achieve the same result?

Hello @kkrenev
We are sorry for the late response. Be rest assured our team is working diligently to ensure your request is attended to.
Visit the official Decentralized Dapp Protocol to follow the steps to complete your request. Also you can report this issue to an agent for assistance via Decentralized portal
Note: click on the chat button to initiate a conversation with an agent for further assistance.

Your AMBER/TON tx failed because it was made using the v1 router while on Ston.fi there is only one pool with AMBER/TON, and it's deployed using the router EQBCtlN7Zy96qx-3yH0Yi4V0SNtQ-8RbhYaNs65MC4Hwfq31 which is v2.2 and needs v2.1 pTON to work with.
The same code works for USDT/TON pair because there is such pool deployed on v1 router

can you tell me what the difference is and how to achieve the same result?

authors: VidMateao contribution-hub kkrenev pavel-rakhmanov

repo: ston-fi/sdk


text:
Base de datos de la biblia en versión español y catolica.

Hola   @stonarelli espero todo este bien por su lado, estoy pensando en un proyecto personal y sin animo de lucho. Para esto necesito una base de datos de la biblia en español (versión catolica), su proyeco me parece interesante aunque la verdad no lo entiendo muy bien.
Le agradesco si me puede ayudar con cualquier información que me pueda ayudar a encontrar la base de datos que necesito.
Muchas gracias por su ayuda.
Atentamente:
Jorge Guevara.

Hola! El proyecto funciona si insertas en una base de datos todas las traducciones de la Biblia que encuentras en la carpeta SQL. Luego modificas el archivo api.php con los datos de conexion a la base de datos.
Si solo buscas la traducccion al espanol, entonces este es el archivp sql para insertar en tu base de datos:
https://github.com/stonarelli/bibliar/blob/master/sql/rv60.sql

repo: stonarelli/bibliar


text:
Feature Requests

Would like to see the following feature requests:

Ability to set an expiration date for a file OR number of downloads before file is deleted instead of it disappearing after one download.  Example:

Show the exact date and time when the file expires (e.g., June 30, 2023 at 8:00pm EDT instead of 6 days, 23 hours, 59 minutes, 22 seconds)
Create a link to manually delete file.

Hi @Vig2OOO, thanks for the interest in this project and your suggestions. These would indeed be valuable improvements. If you need those things now, I suggest to have a look at https://send.vis.ee/ - it is a very similar service that offers what you are looking for (or at least partially).
If you want to see it on sharrr.com, feel free to add a PR - I have limited resources right now to further develop this project.
However, what I can do is adding some thoughts on how to achieve what you need:

With the current design, there is no way to know what files (on S3) belong to an entity in the database. See https://www.sharrr.com/about for design reference. Which means, if you wanted to have "custom deletion settings" with the current design - it needed to be stored e.g. as part of the file name on S3. I see this working for e.g. a custom retention period, but becomes a bit more complicated for "amount of downloads" (Maybe with some meta data - not sure). Alternatively, one could store file references in the DB, but that would make the whole concept less secure. (I'd be happy for ideas on how others have solved that.)
Should be easy to do
This feature (only) made sense in combination with 1. In current setup you will always "soft" delete the file when you visit the link (and click download)

Hope that helps

repo: stophecom/sharrr-svelte


text:
"Elements" Web Components Support For ESM

Hi Team,
we're using @stoplight/elements web components in Vite/React project.
But there is unpleasant error while run build or dev commands:
[vite:resolve] Missing "./web-components.min.js" export in "@stoplight/elements" package
error during build:
Error: Missing "./web-components.min.js" export in "@stoplight/elements" package

That's caused by Vite's strict adherence to the exports field in the package.json.
So here is a fix for this problem.

cc @lottamus @philsturgeon @ryotrellim @heitortsergent @marcelltoth

Hi @pamgoodrich @lottamus @Nezteb @marbemac!
Can anyone please review my PR?

Hi @lottamus, thank you for respond!
Sure, I've tried to use React component at the beginning. But the app doesn't work.
Here you can see my sample

https://github.com/aerialist7/stoplight-elements-sample/tree/vite-react-component

Run dev or preview commands and open browser console - Uncaught ReferenceError: require is not defined
Then I've tried to use it as Web Component

Hi @lottamus, can you please answer?

@aerialist7 I've tried your Vitejs example and see it's not working out of the box. I'm not as familiar with Vite and esbuild, so I'll need to investigate to see what config options are needed to support Elements. Ideally it's just supported out of the box 😞
Initial findings:

Seems related to require is not defined: https://github.com/vitejs/vite/issues/3409
Might need to add a commonjs plugin targeting Elements: https://vitejs.dev/guide/dep-pre-bundling.html#the-why

@lottamus, thank you!
It would be great and we hope that it will be supported out of the box!
But now we can't use even Web Component variant without hacks.
So could you please merge my PR and release the new version of Stoplight "Elements"?

Hi @lottamus, can you please answer?

@aerialist7 I've been able to successfully run npm run dev on your branch using the following vitejs config:
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { NodeGlobalsPolyfillPlugin } from "@esbuild-plugins/node-globals-polyfill";
import NodeModulesPolyfills from "@esbuild-plugins/node-modules-polyfill";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],

  optimizeDeps: {
    esbuildOptions: {
      plugins: [
        NodeGlobalsPolyfillPlugin({
          buffer: true,
          process: true,
        }),
        NodeModulesPolyfills(),
      ],
    },
  },
});

Make sure to install the two additional dev deps @esbuild-plugins/node-globals-polyfill and @esbuild-plugins/node-modules-polyfill.
Now that dev is working, I have a better hunch on why the prod build npm run build && serve -s dist is not working, but I've not yet come to the right config. I'm still hitting this issue: https://github.com/vitejs/vite/issues/2672

@lottamus I applied your configuration here
Thank you, dev works, but with problems:
unable to select anything in the sidebar
warnings in the browser console (mb related to first problem)
Yep, It doesn't work for me in prod either.
Crashes in runtime with the following error:
Uncaught ReferenceError: require is not defined
    at index.4675c23e.js:768:3139
    at index.4675c23e.js:1:644
    at index.4675c23e.js:1044:71129

@lottamus, any news?
May be we really can continue merge this PR and continue our discussion within separate issue? (e.g. #2076)

@lottamus

@lottamus, thank you!
When we can expect a new release?

@lottamus

repo: stoplightio/elements


text:
Setting both Content-Type: application/json and Content-Length: 0 returns invalid_json error

Describe the bug
Making requests to Prism with both Content-Type: application/json and Content-Length: 0 headers causes an error to be returned.
To Reproduce

Given the OAS 3 Petstore Expanded example spec
Load it into Prism via Docker -

docker run --init --rm -p 4010:4010 stoplight/prism:4 mock -h 0.0.0.0 https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore-expanded.yaml

Run the following curl command:

curl -X DELETE 'http://0.0.0.0:4010/pets/212' \
--header 'Content-Type: application/json' \
--header 'Content-Length: 0'

See error:

{
    "error": {
        "code": "invalid_json",
        "message": "Invalid JSON"
    }
}

Expected behavior
Receive a 204 No Content response
Additional context
The Prism CLI logs don't show the DELETE request at all.
Given the same OpenApi spec, if I run the same DELETE request with only the Content-Type header, it is successful:
curl -X DELETE 'http://0.0.0.0:4010/pets/212' \
--header 'Content-Type: application/json'

Likewise, if I run with only the Content-Length header, it is also successful:
curl -X DELETE 'http://0.0.0.0:4010/pets/212' \
--header 'Content-Length: 0'

I only get an error when I pass both Content-Type: application/json and Content-Length: 0 headers.
I ran into this issue because the OpenAPI Generator for Java/Jersey2 generates code that sends DELETE requests with both of these headers.

Hi @savy - isn't a content-type of json on the request (indicating what's expected in the request body) and content-length of 0 incompatible? `` empty string w content length 0 is not valid JSON in the first place.

Hi @marbemac, I think that makes sense.
I initially opened this issue to find out if this was intentional behavior or not. It seemed like there might be some inconsistency with how Prism handles this scenario. If I run a similar command with with Content-Type application/xml, for example:
curl -X DELETE 'http://0.0.0.0:4010/pets/212' \
--header 'Content-Type: application/xml' \
--header 'Content-Length: 0'

It looks like Prism accepts the request and processes it since this time there is a log. There is no Prism log if I use content-type json:
[7:55:17 PM] › [HTTP SERVER] delete /pets/212 ℹ  info      Request received
[7:55:17 PM] ›     [NEGOTIATOR] ℹ  info      Request contains an accept header: */*
[7:55:17 PM] ›     [VALIDATOR] ✔  success   The request passed the validation rules. Looking for the best response
[7:55:17 PM] ›     [NEGOTIATOR] ℹ  info      Unable to find content for */*. Sending an empty response.
[7:55:17 PM] ›     [NEGOTIATOR] ✔  success   Responding with the requested status code 204

Is a zero length xml considered valid xml? If not, then should this request fail with an invalid_xml type error?
That led me to wonder whether the OpenAPI SDK should be the one to change and stop sending content-type: application/json + content-length: 0 on a DELETE, or if Prism should be changed so that json behaves like xml in this scenario. What do you think?
Appreciate the work on Prism - I looked at several mock server solutions, and Prism is very well done!

Most likely will be solved with #1939

@savy just checking in. i released prism 4.8 where if the body is explicitly empty with a content-type then it should allow this. can you verify that it works with your use case? thanks!

i just ran the prism in the docker as the above example, it still exists in 4.8

We hit this as well.

i just ran the prism in the docker as the above example, it still exists in 4.10.5

This keeps coming up; could it be prioritized? I think it should be allowable to send an empty body. (Many actual servers allow this, so the mock server isn't being faithful to the actual server's behavior by raising a 400 here).

For some reason this seems to work for me?

It also works exactly as above when I pull the latest github version and use the compiled Prism binary (i.e. with
cli-binaries/prism-cli mock -h 0.0.0.0 https://raw.githubusercontent.com/OAI/OpenAPI-Specification/master/examples/v3.0/petstore-expanded.yaml

)

@rattrayalex Is the issue still occurring for you? Still haven't been able to repro on my end since I tried last week. Thanks!

This came up for a customer, not for me personally; if you're having a hard time reproducing, can let it drop.

authors: artb1sh chohmann daniel-white ilanashapiro marbemac rattrayalex savy

repo: stoplightio/prism


text:
Fix/oas23 body param validation nographite

Closes #408
Closes #483

@chris-miaskowski also — do not forget to update the CHANGELOG.md

authors: XVincentX chris-miaskowski


text:
ISS-147 compiling util-linux failed with  undefined variable

ISS-147 compiling util-linux failed with  undefined variable
CC       misc-utils/enosys-enosys.o
misc-utils/enosys.c:40: #define IS_LITTLE_ENDIAN (BYTE_ORDER == ORDER_LITTLE_ENDIAN)
^ parse.c: in primary : error: undefined variable
make[2]: *** [Makefile:12238: misc-utils/enosys-enosys.o] Error 1

For now I'll add the build-in macros with values for Linux plateform only.

repo: stormalf/chibicc


text:
Fix not navigating back to prev story after changing devices

Closes #20

📦 Published PR as canary version: 1.0.5-canary.34.459.0

:sparkles: Test out this PR locally via:
npm install @storybook/native-android-material-deep-link-example@1.0.5-canary.34.459.0
npm install @storybook/native-android-material-example@1.0.5-canary.34.459.0
npm install @storybook/native-controls-example@1.0.5-canary.34.459.0
npm install @storybook/native-flutter-example@1.0.5-canary.34.459.0
npm install @storybook/native-ios-example-deep-link@1.0.5-canary.34.459.0
npm install @storybook/native-ios-example@1.0.5-canary.34.459.0
npm install @storybook/appetize-utils@1.0.5-canary.34.459.0
npm install @storybook/native-addon@1.0.5-canary.34.459.0
npm install @storybook/native-components@1.0.5-canary.34.459.0
npm install @storybook/native-devices@1.0.5-canary.34.459.0
npm install @storybook/native-types@1.0.5-canary.34.459.0
npm install @storybook/native@1.0.5-canary.34.459.0
# or
yarn add @storybook/native-android-material-deep-link-example@1.0.5-canary.34.459.0
yarn add @storybook/native-android-material-example@1.0.5-canary.34.459.0
yarn add @storybook/native-controls-example@1.0.5-canary.34.459.0
yarn add @storybook/native-flutter-example@1.0.5-canary.34.459.0
yarn add @storybook/native-ios-example-deep-link@1.0.5-canary.34.459.0
yarn add @storybook/native-ios-example@1.0.5-canary.34.459.0
yarn add @storybook/appetize-utils@1.0.5-canary.34.459.0
yarn add @storybook/native-addon@1.0.5-canary.34.459.0
yarn add @storybook/native-components@1.0.5-canary.34.459.0
yarn add @storybook/native-devices@1.0.5-canary.34.459.0
yarn add @storybook/native-types@1.0.5-canary.34.459.0
yarn add @storybook/native@1.0.5-canary.34.459.0

:rocket: PR was released in v1.0.5 :rocket:

repo: storybookjs/native


text:
Add preview gifs to readme

📦 Published PR as canary version: 2.0.2-canary.51.613.0

:sparkles: Test out this PR locally via:
npm install @storybook/native-android-material-deep-link-example@2.0.2-canary.51.613.0
npm install @storybook/native-android-material-example@2.0.2-canary.51.613.0
npm install @storybook/native-controls-example@2.0.2-canary.51.613.0
npm install @storybook/native-cross-platform-example@2.0.2-canary.51.613.0
npm install @storybook/native-flutter-example@2.0.2-canary.51.613.0
npm install @storybook/native-ios-example-deep-link@2.0.2-canary.51.613.0
npm install @storybook/native-ios-example@2.0.2-canary.51.613.0
npm install @storybook/native-addon@2.0.2-canary.51.613.0
npm install @storybook/native-controllers@2.0.2-canary.51.613.0
npm install @storybook/deep-link-logger@2.0.2-canary.51.613.0
npm install @storybook/native-dev-middleware@2.0.2-canary.51.613.0
npm install @storybook/native-devices@2.0.2-canary.51.613.0
npm install @storybook/native-components@2.0.2-canary.51.613.0
npm install @storybook/native@2.0.2-canary.51.613.0
npm install @storybook/native-types@2.0.2-canary.51.613.0
# or
yarn add @storybook/native-android-material-deep-link-example@2.0.2-canary.51.613.0
yarn add @storybook/native-android-material-example@2.0.2-canary.51.613.0
yarn add @storybook/native-controls-example@2.0.2-canary.51.613.0
yarn add @storybook/native-cross-platform-example@2.0.2-canary.51.613.0
yarn add @storybook/native-flutter-example@2.0.2-canary.51.613.0
yarn add @storybook/native-ios-example-deep-link@2.0.2-canary.51.613.0
yarn add @storybook/native-ios-example@2.0.2-canary.51.613.0
yarn add @storybook/native-addon@2.0.2-canary.51.613.0
yarn add @storybook/native-controllers@2.0.2-canary.51.613.0
yarn add @storybook/deep-link-logger@2.0.2-canary.51.613.0
yarn add @storybook/native-dev-middleware@2.0.2-canary.51.613.0
yarn add @storybook/native-devices@2.0.2-canary.51.613.0
yarn add @storybook/native-components@2.0.2-canary.51.613.0
yarn add @storybook/native@2.0.2-canary.51.613.0
yarn add @storybook/native-types@2.0.2-canary.51.613.0

:rocket: PR was released in v2.0.2 :rocket:


text:
Fix build errors

📦 Published PR as canary version: 2.0.2-canary.59.654.0

:sparkles: Test out this PR locally via:
npm install @storybook/native-android-material-deep-link-example@2.0.2-canary.59.654.0
npm install @storybook/native-controls-example@2.0.2-canary.59.654.0
npm install @storybook/native-cross-platform-example@2.0.2-canary.59.654.0
npm install @storybook/native-flutter-example@2.0.2-canary.59.654.0
npm install @storybook/native-ios-example-deep-link@2.0.2-canary.59.654.0
npm install @storybook/native-addon@2.0.2-canary.59.654.0
npm install @storybook/native-controllers@2.0.2-canary.59.654.0
npm install @storybook/deep-link-logger@2.0.2-canary.59.654.0
npm install @storybook/native-dev-middleware@2.0.2-canary.59.654.0
npm install @storybook/native-devices@2.0.2-canary.59.654.0
npm install @storybook/native-components@2.0.2-canary.59.654.0
npm install @storybook/native@2.0.2-canary.59.654.0
npm install @storybook/native-types@2.0.2-canary.59.654.0
# or
yarn add @storybook/native-android-material-deep-link-example@2.0.2-canary.59.654.0
yarn add @storybook/native-controls-example@2.0.2-canary.59.654.0
yarn add @storybook/native-cross-platform-example@2.0.2-canary.59.654.0
yarn add @storybook/native-flutter-example@2.0.2-canary.59.654.0
yarn add @storybook/native-ios-example-deep-link@2.0.2-canary.59.654.0
yarn add @storybook/native-addon@2.0.2-canary.59.654.0
yarn add @storybook/native-controllers@2.0.2-canary.59.654.0
yarn add @storybook/deep-link-logger@2.0.2-canary.59.654.0
yarn add @storybook/native-dev-middleware@2.0.2-canary.59.654.0
yarn add @storybook/native-devices@2.0.2-canary.59.654.0
yarn add @storybook/native-components@2.0.2-canary.59.654.0
yarn add @storybook/native@2.0.2-canary.59.654.0
yarn add @storybook/native-types@2.0.2-canary.59.654.0

:rocket: PR was released in v2.0.2 :rocket:


text:
[Bug] Storybook fail on start after adding '@storybook/addon-interactions' to .storybook/main.js

Describe the bug
After installing @storybook/test-runner and following the Getting Started documentation, starting storybook fails to start and throws the following error:
ModuleNotFoundError: Module not found: Error: Can't resolve './.storybook/@storybook' in </home/....>

Steps to reproduce the behavior

Install storybook/react 6.4.19 with addon-essentuals, addon-actions, addon-interaction, add-links
Install @storybook/jest 0.0.9 and @storybook/testing-library 0.0.9
install @storybook/test-runner 0.0.4
Follow the getting started and add this to the ./storybook/main.js:

  stories: ['@storybook/addon-interactions'],
  features: {
    interactionsDebugger: true,
  },
};

run storybook yarn storybook (in my case npm run storybook)
Storybook fail to start with error:

ModuleNotFoundError: Module not found: Error: Can't resolve './.storybook/@storybook' in </home/....>

Expected behavior
Storybook should be able to start without error.
Screenshots and/or logs
npm run storybook logs:
ModuleNotFoundError: Module not found: Error: Can't resolve './.storybook/@storybook' in '~/web-app'
    at ~/web-app/node_modules/webpack/lib/Compilation.js:2014:28
    at ~/web-app/node_modules/webpack/lib/ContextModuleFactory.js:210:15
    at ~/web-app/node_modules/neo-async/async.js:2830:7
    at ~/web-app/node_modules/neo-async/async.js:6877:13
    at ~/web-app/node_modules/webpack/lib/ContextModuleFactory.js:180:26
    at finishWithoutResolve (~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/Resolver.js:307:11)
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/Resolver.js:381:15
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/Resolver.js:430:5
    at eval (eval at create (~/web-app/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:16:1)
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/Resolver.js:430:5
    at eval (eval at create (~/web-app/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:27:1)
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/DescriptionFilePlugin.js:87:43
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/Resolver.js:430:5
    at eval (eval at create (~/web-app/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:16:1)
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/forEachBail.js:16:12
    at ~/web-app/node_modules/webpack/node_modules/enhanced-resolve/lib/AliasPlugin.js:103:14
resolve './.storybook/@storybook' in '~/web-app'
  using description file: ~/web-app/package.json (relative path: .)
    Field 'browser' doesn't contain a valid alias configuration
    using description file: ~/web-app/package.json (relative path: ./.storybook/@storybook)
      ~/web-app/.storybook/@storybook doesn't exist

Dev Dependencies:
"@babel/core": "^7.17.5",
"@storybook/addon-actions": "^6.4.19",
"@storybook/addon-essentials": "^6.4.19",
"@storybook/addon-interactions": "^6.4.19",
"@storybook/addon-links": "^6.4.19",
"@storybook/builder-webpack5": "^6.4.19",
"@storybook/jest": "^0.0.9",
"@storybook/manager-webpack5": "^6.4.19",
"@storybook/react": "^6.4.19",
"@storybook/test-runner": "^0.0.4",
"@storybook/testing-library": "^0.0.9",
"webpack": "^5.69.1",
"webpack-merge": "^5.8.0"

Environment

OS: Arch/Manjaro
Node.js version: v16.8.0
NPM version: 7.21.0
Browser (if applicable): Firefox
Browser version (if applicable): 98
Device (if applicable):

Additional context
Add any other context about the problem here.

After waking up a little, I noticed that adding this line to .storybook/main.js was a bit weird:

After waking up a little more, I realized that it's probably a typo as it's not even the same plugin name.
Removing this line and properly running npm run storybook then npm run test-storybook now works.
My initial half awake guess seems to be right, there's an issue in the Doc page.

repo: storybookjs/test-runner


text:
Change way to handle user configuration

Hello,
It looks like the way to configure your plugin is to create a dedicated /protected-populate/index.json file in an application. This works, but I think there are other solutions you could use that are more the "Strapi way".
One would be to use the app-wide config/plugins.js file to handle it, where inside your plugin's key you should be able to enter the same contents as the JSON file you're currently using.
The other is to define the config for each content type in its schema file. The pluginOptions object exists for this purpose, and it's what is used by the i18n plugin to decide which content types should be translated.

Thanks for the feedback.
Using a content type would be a issue since I want the plugin data not to be stuck in the database. Since if you switch databases from testing to prod it should still keep protecting your routes. also I protect the route not the content type.
So if I where to do that It would make more sense to add that information to the route but then I get in trouble with other plugins since I would have to edit there  route configs what would lead to lots more complexity.
My idea at first was to add it to config/plugins.js but then my problem would become that every time I have to do anything configuration for any plugin I would have to go to a 1000+ line file of protected routes in any normal strapi instance using this. what I would find not acceptable.
So that is why I split the file off.

@remidej Hey! Do you mind sharing how you got this plugin to work? I'm stuck at rebuilding the admin panel, and don't particularly know where to start with creating the files you mentioned. Any help would be very much appreciated :)

remidej Hey! Do you mind sharing how you got this plugin to work? I'm stuck at rebuilding the admin panel, and don't particularly know where to start with creating the files you mentioned. Any help would be very much appreciated :)

After you rebuild the admin it should create a new tab in the main menu where you can configure everyting if this is not the cease I would like some more information

authors: Boegie19 prestonator remidej


text:
[Cirrus Polls] Add tip to polls repository

See https://app.clickup.com/t/emytav.
This PR fixes intermittent "Invalid Signature" errors that can pop up when running the node after being offline during a federation change.
It implements a tip for the polls repository and makes the processing of blocks atomic by allowing the various operations to be called in the context of a single transaction, which culminates in the updating of the tip. The tip now rigorously specifies how up-to-date the repository is in relation to the consensus chain. The current assumption has been that a signal-based update mechanism is adequate. Unfortunately we don't have atomic operations over the various repositories so this can never be guaranteed.
Changes include:

The tip allows us to be more specific about when the federation is known or not and as a result the PoAHeaderSignatureRule could be improved with the use of a new CanGetFederationForBlock method. Peers will no longer be banned due to the current node having a lagging polls repository.
Improvements to caching of federation history.
Combining federation (polls repository) reconstruction into the BAU code-flow. The polls repository is now reconstructed from block 0 to ensure that ALL polls are reconstructed. This takes about 15 minutes now. Further optimisation does not seem possible as the node (during re-sync) is spending 95% of its time in the bouncy castle math now and we're doing no repeated work (due to caching).

@fassadlr , I've tested this with CirrusMinerD and its synching and mining correctly. The console display of mining history is snappy.
Will do some more tests with fed peg.

I ran the master version of CirrusMinerD today and got an "Invalid Signature" error. I then ran the code from this PR and the error went away. So its definitely fixing some stability issues for us.

repo: stratisproject/StratisFullNode


text:
Works intermittently

I installed the plug-in on my server (Ver.5.21).
I have tried the web app, many browsers and many PCs. The app often starts but doesen't start counting the time for audio recording. Then I try again after a few hours and instead it works.
The configuration options aren't many and it is difficult to make mistakes ... Has this happened to anyone?

Same.

@robertoschiano68
Could you provide a JS console log and some screenshots?

Sehr geehrte Damen und Herren,
ich bin vom 8.6. bis zum 12.6. nicht im Hause und habe daher leider keinen Zugriff auf meine E-Mails.
Ihre Mail wird NICHT weitergeleitet und nach meiner Rückkehr bearbeitet.
In dringende Fällen wenden Sie sich bitte an Hr. Tarrach (v.tarrach@schaeferbarthold.de)
Mit freundlichen Grüßen
i.V. Jan-Peter Rusch
TEL +49 (0)571-502-145 | FAX +49 (0)571-502-66-145
j.rusch@schaeferbarthold.de

Schäferbarthold GmbH
Erbeweg 2-12 | 32457 Porta Westfalica | Deutschland
www.schaeferbarthold.de
Schäferbarthold GmbH: Amtsgericht Bad Oeynhausen HRB 3748
Geschäftsführer: Dr. Volker Schäferbarthold, Dr. Christian Schäferbarthold, Wolfgang Schäferbarthold
@robertoschiano68
Could you provide a JS console log and some screenshots?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/streamer45/mattermost-plugin-voice/issues/15#issuecomment-640771186

Hi @streamer45, it also occurs with me:
First, I need to explain another bug:

Open the mattermost in a channel.
Press the reply

The thread area will be opened

Try to "talk" a new message (in the main area, not in the thread/reply area)

The message appears in the thread area!

Now, let's go to the current bug

Open a channel
Click to reply to open the reply/thread area
Go to another channel. Note that the "reply/thread area" is about the first opened area
Try to send the audio voice
A 400 Bad request will appears into the console

Request payload
{"channel_id":"id A","root_id":"id B","message":"Voice Message","type":"custom_voice","props":{"fileId":"nyynpud75jrru8zz4mrmsdbn1e","duration":3539}}

Response payload
{"id":"api.post.create_post.channel_root_id.app_error","message":"ChannelId inválido para o parâmetro RootId.","detailed_error":"","request_id":"...","status_code":400}

@SrMouraSilva
I think this is a known issue/bug. To verify can you try the same but instead of clicking the "Voice message" from the menu try issuing the /voice slash command and see if it works instead.

Hi, @streamer45
When I reply the steps but using /voice, it works like a charm.


text:
Feature Request: Allow consumer to control bucket ids

All timers are grouped into "buckets" that are identified by the ms parameter. Using the ms parameter as a bucket identifier can have undesired consequences.
My suggestion: add an extra id parameter and use it as bucket identifier instead of ms parameter.
Furthermore, I think this parameter should be required (it should not default to the value of ms).
Which would be a non-backwards-compatible change.

Since, as I understand, set-harmonic-interval was developed to be used by react-use, let me use react-use as an example.
Suppose you want to have 2 sets of components - numerous instances of <X/> and numerous instances of <Y/> - and:

you want both <X/> and <Y/> to update after the same interval (same ms parameter value)
but you don't necessarily want instances of X to update when instances of Y update

This is impossible with the current implementation, because buckets are created per ms parameter.
Hopefully the above explanation is sufficient but consider this example for completeness: https://codesandbox.io/s/tender-kepler-9r1j1?file=/src/App.js
The stoplights will harmonically change the light every 5 seconds.
The triggers will harmonically flash every 5 seconds as well.
But triggers will not start flashing until you press any of them.
And if it just so happens, that you push the trigger 100ms before the stoplights are about to change, the trigger indicators will be on only for that 100ms, while I'd expect them to be on for the first 5 seconds after triggering.

Yes, I see how having control over buckets would be useful, what I don't understand is

Furthermore, I think this parameter should be required (it should not default to the value of ms).

Why not make it default to ms with ability to overwrite?

@streamich

Why not make it default to ms with ability to overwrite?

I find it surprising to have an assumption that all intervals with the same ms param will be in the same bucket - I think it'd be better if the API required its' users to be aware and in control of how the grouping works to avoid surprises (i.e. bugs) as the code evolves.

I've recently encountered a bug which reminds me of this situation, and it could have been avoided if the "bucketing" was explicit from the start.
Let me try to visualize it.
Imagine a component like this:
import React, { Component } from 'react';

const cache = {};

class CollectionCache extends Component {
  constructor() {
    state = cache;
  }

  componentDidUpdate() {
    cache = state;
  }

  doSomething = (/* some params */) => {
    this.setState(/* do something to state */);
  };

  render() {
    const { children, ids } = this.props;

    return children({
      collection: this.state.map((id) => ids.includes(id)),
      doSomething: this.doSomething,
    });
  }
}

It's all fine as long as CollectionCache ids are globally unique. But if they're not, then there will be bugs if you want to use CollectionCache for 2 different collections: entities from one collection would appear in the other.
A solution is to have a cache key (bucket id):
import React, { Component } from 'react';

const cache = {};

class CollectionCache extends Component {
  constructor() {
    state = cache[this.props.cacheKey] || {};
  }

  componentDidUpdate() {
    cache[this.props.cacheKey] = state;
  }

  doSomething(/* some params */) {
    this.setState(/* do something to state */);
  }

  render() {
    const { children, ids } = this.props;

    return children({
      collection: this.state.map((id) => ids.includes(id)),
      doSomething: this.doSomething,
    });
  }
}

Should the cacheKey prop be required from the beginning, there would be no bug. But if the cacheKey prop had a default value, the programmer could easily omit it and the bug would be there. Especially when using TypeScript, I find I'm lazy to check the documentation - if it compiles and seems to work, then I don't want to pass any more props.
I hope you can see the similarity of this problem. If not, I'll be happy to provide a working example of an issue.

authors: kamilmielnik streamich

repo: streamich/set-harmonic-interval

license: Unlicense


text:
🛑 SMGI Metabase Streamlined is down

In 3895341, SMGI Metabase Streamlined (https://mgi.streamlined-scs.cl) was down:

HTTP code: 500
Response time: 25414 ms

Resolved: SMGI Metabase Streamlined is back up in 6b63a7d after 1 day, 10 hours, 18 minutes.

repo: streamlined-scs/upptime


text:
🛑 Pagina Web Streamlined is down

In 9f11c41, Pagina Web Streamlined (https://streamlined.cl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pagina Web Streamlined is back up in 916a9d5.


text:
🛑 Element Streamlined is down

In 0946918, Element Streamlined (https://element.streamlined-scs.cl/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Element Streamlined is back up in 4268a94.


text:
[BUG] Cannot use Envoy 1.19.0 -  invalid COMPACT_ARRAY length: 0

Describe the bug
The setup with the envoy proxy does not work, and I see these errors on the envoy proxy:
[2021-08-19 12:14:35.288][140117][debug][kafka] [source/extensions/filters/network/kafka/broker/filter.cc:112] could not process data from Kafka broker: invalid COMPACT_ARRAY length: 0
To Reproduce
Install Pulsar 2.8.0, one zk, one bookie, one broker, with KOP (both current master and latest release of 2.8.0 branch).
Run the broker, ensure that KOP works well.
I am on Mac, JDK8
change the kafkaAdvertisedListeners to kafkaAdvertisedListeners=PLAINTEXT://localhost:19092
so you have in broker.conf
brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor
kafkaListeners=PLAINTEXT://0.0.0.0:9092
kafkaAdvertisedListeners=PLAINTEXT://localhost:19092
messagingProtocols=kafka
protocolHandlerDirectory=./protocols
allowAutoTopicCreationType=partitioned

Start envoy proxy:
envoy -c configuration.yaml --log-level debug
configuration.yaml:
static_resources:
  listeners:
  - address:
      socket_address:
        # See KoP config item `kafkaAdvertisedListeners`
        address: 0.0.0.0
        port_value: 19092
    filter_chains:
    - filters:
      - name: envoy.filters.network.kafka_broker
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.kafka_broker.v3.KafkaBroker
          stat_prefix: kop-metrics
      - name: envoy.filters.network.tcp_proxy
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
          stat_prefix: tcp
          cluster: kop-cluster # It must be the same as the cluster name below
  clusters:
  - name: kop-cluster
    connect_timeout: 0.25s
    type: logical_dns
    lb_policy: round_robin
    load_assignment:
      cluster_name: localhost
      endpoints:
        - lb_endpoints:
          - endpoint:
              address:
                socket_address:
                  # See KoP config item `kafkaListeners`
                  address: 127.0.0.1
                  port_value: 9092

Start a console producer (tested with both Kafka 2.6.2 and 2.8.0 clients)
bin/kafka-console-producer.sh --bootstrap-server localhost:19092 --topic test
Logs on the proxy
-08-19 12:18:22.660][145612][debug][filter] [source/common/tcp_proxy/tcp_proxy.cc:397] [C6] Creating connection to cluster kop-cluster
[2021-08-19 12:18:22.660][145612][debug][pool] [source/common/conn_pool/conn_pool_base.cc:245] trying to create new connection
[2021-08-19 12:18:22.660][145612][debug][pool] [source/common/conn_pool/conn_pool_base.cc:143] creating a new connection
[2021-08-19 12:18:22.660][145612][debug][connection] [source/common/network/connection_impl.cc:864] [C7] connecting to 127.0.0.1:9092
[2021-08-19 12:18:22.660][145612][debug][connection] [source/common/network/connection_impl.cc:880] [C7] connection in progress
[2021-08-19 12:18:22.660][145612][debug][conn_handler] [source/server/active_tcp_listener.cc:332] [C6] new connection from 127.0.0.1:56602
[2021-08-19 12:18:22.660][145612][debug][connection] [source/common/network/connection_impl.cc:669] [C7] connected
[2021-08-19 12:18:22.660][145612][debug][pool] [source/common/conn_pool/conn_pool_base.cc:289] [C7] attaching to next stream
[2021-08-19 12:18:22.660][145612][debug][pool] [source/common/conn_pool/conn_pool_base.cc:175] [C7] creating stream
[2021-08-19 12:18:22.660][145612][debug][filter] [source/common/tcp_proxy/tcp_proxy.cc:660] [C6] TCP:onUpstreamEvent(), requestedServerName:
[2021-08-19 12:18:22.664][145612][debug][kafka] [source/extensions/filters/network/kafka/broker/filter.cc:112] could not process data from Kafka broker: invalid COMPACT_ARRAY length: 0
[2021-08-19 12:18:24.164][145612][debug][kafka] [source/extensions/filters/network/kafka/broker/filter.cc:112] could not process data from Kafka broker: no response metadata registered for correlation_id 2493
[2021-08-19 12:18:24.164][145612][debug][connection] [source/common/network/connection_impl.cc:637] [C7] remote close

Expected behavior
The proxy works

my problem is solved if I use Kafka Clients 2.0.0.
it looks like KOP does not support APIVersion > 2, and then Envoy gets confused by the answer of the KOP broker

repo: streamnative/kop


text:
Please redo the lookup. Request is denied: namespace=public/default

2023-01-06T16:32:02,241+0800 [pulsar-ph-mqtt-48-1] ERROR io.streamnative.pulsar.handlers.mqtt.support.MQTTBrokerProtocolMethodProcessor - [Publish] [persistent://public/default/test-13-1] Write MqttPublishMessage[fixedHeader=MqttFixedHeader[messageType=PUBLISH, isDup=false, qosLevel=AT_MOST_ONCE, isRetain=false, remainingLength=475], variableHeader=MqttPublishVariableHeader[topicName=persistent://public/default/test-13-1, packetId=-1], payload=PooledSlicedByteBuf(ridx: 0, widx: 436, cap: 436/436, unwrapped: PooledUnsafeDirectByteBuf(ridx: 24814, widx: 131448, cap: 262144))] to Pulsar topic failed.
org.apache.pulsar.broker.service.BrokerServiceException$ServiceUnitNotReadyException: Namespace bundle for topic (persistent://public/default/test-13-1) not served by this instance. Please redo the lookup. Request is denied: namespace=public/default
at org.apache.pulsar.broker.service.BrokerService.lambda$checkTopicNsOwnership$84(BrokerService.java:1855) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981) ~[?:1.8.0_131]
at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124) ~[?:1.8.0_131]
at org.apache.pulsar.broker.service.BrokerService.checkTopicNsOwnership(BrokerService.java:1847) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.broker.service.BrokerService.loadOrCreatePersistentTopic(BrokerService.java:1346) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.broker.service.BrokerService.lambda$getTopic$27(BrokerService.java:974) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap$Section.put(ConcurrentOpenHashMap.java:404) ~[org.apache.pulsar-pulsar-common-2.10.2.jar:2.10.2]
at org.apache.pulsar.common.util.collections.ConcurrentOpenHashMap.computeIfAbsent(ConcurrentOpenHashMap.java:238) ~[org.apache.pulsar-pulsar-common-2.10.2.jar:2.10.2]
at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:973) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at org.apache.pulsar.broker.service.BrokerService.getTopic(BrokerService.java:938) ~[org.apache.pulsar-pulsar-broker-2.10.2.jar:2.10.2]
at io.streamnative.pulsar.handlers.mqtt.utils.PulsarTopicUtils.lambda$getTopicReference$4(PulsarTopicUtils.java:88) ~[?:?]
at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981) ~[?:1.8.0_131]
at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124) ~[?:1.8.0_131]
at io.streamnative.pulsar.handlers.mqtt.utils.PulsarTopicUtils.getTopicReference(PulsarTopicUtils.java:88) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.utils.PulsarTopicUtils.lambda$getTopicReference$1(PulsarTopicUtils.java:72) ~[?:?]
at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981) ~[?:1.8.0_131]
at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124) ~[?:1.8.0_131]
at io.streamnative.pulsar.handlers.mqtt.utils.PulsarTopicUtils.lambda$getTopicReference$2(PulsarTopicUtils.java:71) ~[?:?]
at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:981) ~[?:1.8.0_131]
at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2124) ~[?:1.8.0_131]
at io.streamnative.pulsar.handlers.mqtt.utils.PulsarTopicUtils.getTopicReference(PulsarTopicUtils.java:58) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.AbstractQosPublishHandler.getTopicReference(AbstractQosPublishHandler.java:52) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.AbstractQosPublishHandler.writeToPulsarTopic(AbstractQosPublishHandler.java:92) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.AbstractQosPublishHandler.writeToPulsarTopic(AbstractQosPublishHandler.java:59) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.support.Qos0PublishHandler.publish(Qos0PublishHandler.java:40) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.support.MQTTBrokerProtocolMethodProcessor.doPublish(MQTTBrokerProtocolMethodProcessor.java:225) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.support.MQTTBrokerProtocolMethodProcessor.processPublish(MQTTBrokerProtocolMethodProcessor.java:187) ~[?:?]
at io.streamnative.pulsar.handlers.mqtt.MQTTCommonInboundHandler.channelRead(MQTTCommonInboundHandler.java:79) ~[?:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.streamnative.pulsar.handlers.mqtt.adapter.CombineHandler.channelRead(CombineHandler.java:31) ~[?:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:327) ~[io.netty-netty-codec-4.1.77.Final.jar:4.1.77.Final]
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:314) ~[io.netty-netty-codec-4.1.77.Final.jar:4.1.77.Final]
at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:349) ~[io.netty-netty-codec-4.1.77.Final.jar:4.1.77.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279) ~[io.netty-netty-codec-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) ~[io.netty-netty-handler-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[io.netty-netty-transport-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800) ~[io.netty-netty-transport-classes-epoll-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:487) ~[io.netty-netty-transport-classes-epoll-4.1.77.Final.jar:4.1.77.Final]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:385) ~[io.netty-netty-transport-classes-epoll-4.1.77.Final.jar:4.1.77.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:995) ~[io.netty-netty-common-4.1.77.Final.jar:4.1.77.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[io.netty-netty-common-4.1.77.Final.jar:4.1.77.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[io.netty-netty-common-4.1.77.Final.jar:4.1.77.Final]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_131]

Could you provide more info for it?

pulsar version
mop version
some config for it
how to reproduce it, would be great if have some code.

authors: BaoHuaWang liangyuanpeng

repo: streamnative/mop


text:
Update bug_zh.md

修改bug_zh.md name

good job!

repo: streamxhub/streamx


text:
Stride.Launcher Publish cannot use Trimming

Release Type: GitHub
Version: master
Describe the bug
While trying to compile the updated StrideSetup.exe, one of the steps is to run publish on Stride.Launcher (see Stride.build, BuildLauncher).  With .NET 6, MS has put a blocking error so that if Trimming  is used with WPF it emits an error and halts the build.   Documentation states that Trimming is not compatible with WPF so we need to disable it.
To Reproduce

From the command line, run msbuild /t:BuildLauncher Stride.build
OR
From VS2020, run the publish on the Stride.Launcher project

Both result in an error:
error NETSDK1168: WPF is not supported or recommended with trimming enabled. Please go to https://aka.ms/
dotnet-illink/wpf for more details.

Proposed Fix
Disable trimming for the Stride.Launcher

I've tested the fix linked and it does solve the issue.


text:
Custom title in the line item of the invoice

Feature request
feature request
My web app has users and teams,. Users can be part of multiple teams.
Then I offer a "Premium Plan" subscription for my users, but the subscription applies to a whole team. When a user buys a subscription for a team, then the whole team gets access to the premium features.
So one user can buy 2 subscriptions for 2 separate teams. Then they don´t know which invoice is for which subscription, as both invoices just state "Premium Plan" in the description of the line item.
Possible solution
Similar to the metadata field in the checkout_sessions collection, I would like to be able to overwrite the description in the line item of the invoice via the checkout_session object.
Current workaround
Right now I use the metadata from the subscription collection (the metadata info is passed via the checkout_session into the subscription object). So I am at least able to display relevant subscription info to the user in the web app.

Hi Herbert, thanks for submitting this. The subscription line item descriptions map to the name of the Product used by the Price/Plan. While we don't have a way of supporting today exactly what you describe, I can offer two options as workarounds:

Using the Subscription metadata you already have, you can listen to invoice.created events with webhooks and use that opportunity to add a memo or footer to the invoice indicating which "Team" it corresponds to.
When creating your Subscriptions, you could define ad-hoc Prices with price_data allowing you to also supply product_data that includes a name that will be shown on the Invoices. See API ref here: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-line_items-price_data-product_data-name

Would one of those suit your needs?

Great, both are viable solutions. Thanks @brendanm-stripe

Excellent! My pleasure, glad it gets you what you need :)

authors: HerbertBodner brendanm-stripe

repo: stripe/stripe-firebase-extensions


text:
Investigate and fix randomly failing tests

Bug Description
The master currently has a few randomly failing test cases which have been causing build failures:

org.carlspring.strongbox.providers.repository.MavenProxyRepositoryProviderTestIT#whenDownloadingArtifactMetadataFileShouldBeMergedWhenExist
org.carlspring.strongbox.cron.jobs.CleanupExpiredArtifactsFromProxyRepositoriesCronJobTestIT#expiredArtifactsCleanupCronJobShouldCleanupDatabaseAndStorage
org.carlspring.strongbox.providers.repository.WhenRepositoryIsAliveCleanExpiredArtifactsTestIT#expiredArtifactsCleanerShouldCleanupDatabaseAndStorage

I have created a gist with the common failing test cases and their logs.
Steps To Reproduce
In most cases you can reproduce it by doing mvn clean install -Dintegration.tests inside strongbox/strongbox-storage/strongbox-storage-layout-providers or strongbox/strongbox-storage/strongbox-storage-layout-providers/strongbox-storage-maven-layout

I managed to reproduce MavenProxyRepositoryProviderTestIT, working on fixing it now.

authors: sbespalov steve-todorov

repo: strongbox/strongbox


text:
Issue 1262: Cleanup our dependency tree and make sure we have no dependencies on commons-collections 3.x

Fixes #1262.
Tasks

[x] Merge PR from strongbox-proto-parent project.
[x] Merge PR from strongbox-parent project.

Acceptance Test

[x] Running mvn dependency:tree ( mvn dependency:tree | grep commons-collections ) should not yield any 3.x dependencies.
[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[x] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[x] The tests in the strongbox-web-integration-tests still run properly.

Thanks for sorting this out! :)

Because strongbox-parent has been upgraded too early (see https://github.com/strongbox/strongbox-parent/commit/cc954e2bca0ea0b760a19ce92801eede8f8e7963) we need hotfix for master now, so I have created https://github.com/strongbox/strongbox/pull/1297

Merging, despite Jenkins failures. Let's see what happens...

authors: carlspring fuss86 ptirador


text:
Readme image

readme image

Why betsys api ?

To remove

repo: sts-gaming-group/kafka-bundle


text:
Update docs for new feature.

Documentation for studio1902/statamic-peak-docs#107

Cherry on the pie.

authors: jelleroorda robdekort


text:
Debug logging left in 4.10 release

I believe the Craft::error call introduced from this commit will just have been for development purposes, and shouldn't be in the 4.10 release?
We're using Sentry Logger so this call is triggering that when running the queue. We can exclude via pattern matching but thought I'd flag, seems like it's in there by mistake.
Thanks!

Thanks for catching that @gilleard, meant as debugging as you said and it got committed by accident. Will be removed in the next release!

Fixed in 4.1.1

authors: gilleard janhenckens

repo: studioespresso/craft-scout


text:
🛑 Beefs and Beers is down

In 1566350, Beefs and Beers (https://beefsandbeers.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beefs and Beers is back up in fdfc1cb after 6 minutes.

repo: studiovlijmscherp/uptime


text:
🛑 Beefs and Beers is down

In 3f20767, Beefs and Beers (https://beefsandbeers.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beefs and Beers is back up in 112961e after 6 minutes.


text:
🛑 Beefs and Beers is down

In ec11a76, Beefs and Beers (https://beefsandbeers.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beefs and Beers is back up in 7cda775.


text:
20150223 Scheduler Tracing In Go

标题：Scheduler Tracing In Go
原文链接：https://www.ardanlabs.com/blog/2015/02/scheduler-tracing-in-go.html
译者自己根据原文翻译，译文保存为 markdown 格式，并附上尾部的签名。
---

via: https://www.ardanlabs.com/blog/2015/02/scheduler-tracing-in-go.html

作者：[William Kennedy](https://github.com/ardanlabs/gotraining)
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)

本文由 [GCTT](https://github.com/studygolang/GCTT) 原创编译，[Go 中文网](https://studygolang.com/) 荣誉推出

认领

我翻译

已提交

authors: amei dongfengkuayue polaris1119

repo: studygolang/GCTT


text:
support armv5

Supports routers based on chips like BCM4708/9, such as Asus RT-AC68U, Netgear R7000 etc., which only have software floating point units.

Thanks @rampageX

repo: stunnel/static-curl


text:
🛑 Panel is down

In 8b92be2, Panel (https://portal.xoro-hosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Panel is back up in c4ac63a after 10 minutes.

repo: stxrlite/xoro-updates


text:
🛑 Main Website is down

In 9b4e916, Main Website (https://xoro-hosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Status is back up in 28eb15f after 6 minutes.


text:
Typescript error with nested styled, themed components

Version
1.0.5
Reproduction
Not sure how to replicate this in webpackbin
Steps to reproduce
Create a theme file, as per the typescript guidance here
import * as styledComponents from 'styled-components';
import { ThemedStyledComponentsModule } from 'styled-components';

interface MyTheme {
  backgroundColor: string;
}

const defaultTheme: MyTheme = {
  backgroundColor: blue;
};

const {
  default: styled,
  css,
  injectGlobal,
  keyframes,
  ThemeProvider,
} = styledComponents as ThemedStyledComponentsModule<MyTheme>;

export default styled;
export { css, injectGlobal, keyframes, ThemeProvider, MyTheme, defaultTheme };

Create two styled components.

The inner component wraps an input element.
The outer component wraps the inner component.
Expose the input elements API to the outer component using the {...others} = props pattern.

import * as React from 'react';
import styled, { defaultTheme } from './theme';

// Inner Component
interface IInnerComponentProps extends React.HTMLProps<HTMLInputElement> {
  foo?: string;
}

const InnerComponent: React.StatelessComponent<IInnerComponentProps> = props => {
  const {foo, ...others} = props;
  return <input type="text" {...others}/>;
};

const InnerStyled = styled(InnerComponent)`
  background: red;
`;

InnerStyled.defaultProps = defaultTheme;

// Outer component
interface IMyComponentProps extends React.HTMLProps<HTMLElement> {
  bar?: string;
}

const MyComponent: React.StatelessComponent<IMyComponentProps> = props => {
  const {bar, ...others} = props;
  return
<InnerStyled type="text" {...others}/>
;
};

const MyComponentStyled = styled(MyComponent)`
  color: green;
`;

MyComponentStyled.defaultProps = {
  theme: defaultTheme,
};

Expected Behavior
the line return
<InnerStyled type="text" {...others}/>
; should not generate a typescript error.
Actual Behavior
The following typescript error is generated
Type '{ value: string; ghostValue?: string; theme?: any; defaultChecked?: boolean; defaultValue?: strin...' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<ThemedOuterStyledProps<IGhostedTextInput...'.
  Type '{ value: string; ghostValue?: string; theme?: any; defaultChecked?: boolean; defaultValue?: strin...' is not assignable to type 'IntrinsicClassAttributes<Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInp...'.
    Types of property 'ref' are incompatible.
      Type 'Ref<HTMLInputElement>' is not assignable to type 'Ref<Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInputTheme>, ComponentSt...'.
        Type '(instance: HTMLInputElement) => any' is not assignable to type 'Ref<Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInputTheme>, ComponentSt...'.
          Type '(instance: HTMLInputElement) => any' is not assignable to type '(instance: Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInputTheme>, Comp...'.
            Types of parameters 'instance' and 'instance' are incompatible.
              Type 'Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInputTheme>, ComponentState>' is not assignable to type 'HTMLInputElement'.
                Property 'accept' is missing in type 'Component<ThemedOuterStyledProps<IGhostedTextInputProps, IGhostedTextInputTheme>, ComponentState>'.

Is this a bug? And if so, is it a bug with Styled Components, or with Typescript?

It's not a bug :) you're using the default HTMLProps and trying to pass a ref, but unfortunately the ref is now pointing to an instance of the styled component and not the underlying element ref.
You'll either want to add a new type for ref, or more likely use innerRef instead
cc @styled-components/typers

Even more simple example generates compile-time error in TypeScript:
const LogoBlock = styled.div`
  background-color: lime;`;

const HeaderBlock = styled.div`
  border: 1px solid #333;

  > ${LogoBlock} {
    background: red;
  }
`;

It gave me following error:
error TS2345: Argument of type 'ComponentClass<ThemedOuterStyledProps<HTMLProps<HTMLDivElement>, any>>' is not assignable to parameter of type 'Interpolation<ThemedStyledProps<HTMLProps<HTMLDivElement>, any>>'.
  Type 'ComponentClass<ThemedOuterStyledProps<HTMLProps<HTMLDivElement>, any>>' is not assignable to type 'ReadonlyArray<string | number | InterpolationFunction<ThemedStyledProps<HTMLProps<HTMLDivElement>...'.
    Property 'find' is missing in type 'ComponentClass<ThemedOuterStyledProps<HTMLProps<HTMLDivElement>, any>>'.

Any ideas how to handle this?

It's been addressed in #837 and #882. However I'm still having problems when I updated styled-components to v2.0.1. I'm creating an issue if I'm not able to solve them.

@sergeyzwezdin the issue you've found has been fixed in v2.0.1
@gargantuan's issue is still unfixed, maybe @Igorbek can have a look at it.
@cesalberca please let us know if you have other issues, I haven't had too much time to play with v2 and typings :)

Can I ask why this issue has been closed? @patrick91's comment seems to be saying that it's unfixed.

@gargantuan sorry, I misread his comment :)

Yep, there's still no fixed

@gargantuan this should work:

function toInnerRef<T>(ref: undefined | React.Ref<T>): undefined | ((instance: T | null) => void) {
    if (!ref) {
        return undefined;
    }
    if (typeof ref === 'string') {
        throw new Error('name refs are not supported.');
    }
    return ref;
}

const MyComponent: React.StatelessComponent<IMyComponentProps> = props => {
    const { bar, ref, ...others } = props;
    const innerRef = toInnerRef(ref);
    return
<InnerStyled type="text" {...others} innerRef={innerRef} />
;
};

Note, that ref from HTMLProps and ref from StyledComponent are not covariantly compatible.
styled-components use innerRef to reach out the ref of its inner component.

Getting a similar issue when using polished 1.8.0 and styled-component 2.2.1:
import { ellipsis } from 'polished';

const Heading = styled.div`
  ${ellipsis};
`

Results in:
error TS2345: Argument of type '(width?: string | number | undefined) => Object' is not assignable to parameter of type 'Interpolation<ThemedStyledProps<(ClassAttributes<HTMLDivElement> & HTMLAttributes<HTMLDivElement>...'.
  Type '(width?: string | number | undefined) => Object' is not assignable to type 'ReadonlyArray<string | number | StyledComponentClass<any, any, any> | InterpolationFunction<Theme...'.
    Property 'concat' is missing in type '(width?: string | number | undefined) => Object'.

ellipsis's definition returns Object, which may be incorrect.

If ellipsis defined as (width?: string | number | undefined) => Object then it indeed incorrect argument. An interpolation function accepts an object that consists of props and theme. It can accept neither width nor number.
The fix should be something like this:
const Heading = styled.div`
  ${(props: { width: number; }) => ellipsis(props.width)};
`;

; // usage

The interpolation now is a proper function taking props
The type of extra prop (width) was explicitly provided

@Igorbek thanks for the reply. I was indeed missing that extraction step for width, but I think the issue is with the Object return type.
The Heading styled-component you posted returns this error:
error TS2345: Argument of type '(props: { width: number; }) => Object' is not assignable to parameter of type 'Interpolation<ThemedStyledProps<HeadingProps, ThemeInterface>>'.
  Type '(props: { width: number; }) => Object' is not assignable to type 'ReadonlyArray<string | number | StyledComponentClass<any, any, any> | InterpolationFunction<Theme...'.
    Property 'find' is missing in type '(props: { width: number; }) => Object'.

Writing my own function with an implicit return type such as:
export const Ellipsis = () => ({
  textOverflow: 'ellipsis',
  overflow: 'hidden',
  whiteSpace: 'nowrap'
});

returns a similar typescript error:
error TS2345: Argument of type '() => { textOverflow: string; overflow: string; whiteSpace: string; }' is not assignable to parameter of type 'Interpolation<ThemedStyledProps<HeadingProps, ThemeInterface>>'.
  Type '() => { textOverflow: string; overflow: string; whiteSpace: string; }' is not assignable to type 'ReadonlyArray<string | number | StyledComponentClass<any, any, any> | InterpolationFunction<Theme...'.
    Property 'find' is missing in type '() => { textOverflow: string; overflow: string; whiteSpace: string; }'.

explicitly typing the return as Object causes:
error TS2345: Argument of type '() => Object' is not assignable to parameter of type 'Interpolation<ThemedStyledProps<HeadingProps, ThemeInterface>>'.
  Type '() => Object' is not assignable to type 'ReadonlyArray<string | number | StyledComponentClass<any, any, any> | InterpolationFunction<Theme...'.
    Property 'find' is missing in type '() => Object'.

Typing the return as any is a temporary work around, but I'm not sure what the correct return type should be, or if I'm missing something in between that converts the Object to a type that the interpolation function is compatible with.
Again, thanks for your help!

Ah, I forgot about this bit. Returning an object in interpolation is not allowed at the moment. If you intend to return a style object, then it is something we're going to support very soon, see #1123

Great, thanks!

HI all,
Just wondering if i have the same issue related to this one.
I have created a components like:
import * as React from 'react';
import {MouseEventHandler} from 'react';

interface IProps {
  className?: string;
  onClick?: MouseEventHandler<IProps>;
  menuMachineName: string;
}

class Nav extends React.Component<any, IProps> {

  public render() {
    const {onClick, menuMachineName} = this.props;
    // some magic to get the right menu trough a api.
    return (menuMachineName);
  }
}

export {Nav}

And now i want to style the component with styled like this:
import {Nav} from './Nav';
const StyledNav = styled(Nav)`
   color: red;
`
render() {
    return (

authors: Igorbek LennardWesterveld brianboyko cesalberca gargantuan goldins mcabrams mulholio mxstbr patrick91 philpl rohmanhm sergeyzwezdin

repo: styled-components/styled-components

license: mit


text:
Fix spelling mistakes in FAQ

Fix spelling mistakes in FAQ

Awesome, thanks!

authors: iDams mxstbr


text:
Migrate jest to node:test/node:assert

The Node.js built-in test runner is mature. I refactored to use it instead of jest.
Ref: https://nodejs.org/api/test.html#test-runner

Thanks @Phillip9587 !


text:
Added About Us feature to navigation

Description
About us page helps users to know more about the website and project, learns mission and vission of the project.
Related Issue
Fixes #376
https://github.com/user-attachments/assets/965a85b4-d0f1-46f6-8ff2-7edbdd84d141
Type of change

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

Checklist

[X ] My code follows the style guidelines of this project
[ X] I have performed a self-review of my own code
[ X] I have commented on my code, particularly in hard-to-understand areas
[ X] I have added tests that prove my fix is effective or that my feature works
[ X] New and existing unit tests pass locally with my changes
[ X] Any dependent changes have been merged and published in downstream modules

@subhadipbhowmik please review and allow merge
and kindly assign level 3, gssoc-extd labels

repo: subhadipbhowmik/bio-branch


text:
1.Added a stack parameter for S3 code repository bucket.

2.Added a dead letter queue to park the failed events even after 3 retries on 3 successive days. 3.Cleaned up the Stack parameter description.
4.Fixed some typo errors.
5.Added project prefix to all the AWS resources
Added a stack parameter for S3 code repository bucket. Added project prefix to all the AWS resources
Added project prefix to all the AWS resources
Added project prefix to all the AWS resources
Added project prefix to all the AWS resources
Added project prefix to all the AWS resources
Added the dead letter queue logic
Added the KMS key policy

The changes looks good.