HBASE-24813 ReplicationSource should clear buffer usage on Replicatio…

This a backport for PR #2546 merged into master. The cherry-pick into branch-2 required some conflicts resolution.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 10s
branch-2 passed

+1 :green_heart:
checkstyle
1m 29s
branch-2 passed

+1 :green_heart:
spotbugs
2m 44s
branch-2 passed

_ Patch Compile Tests _

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

-0 :warning:
checkstyle
1m 27s
hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

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

+1 :green_heart:
hadoopcheck
15m 37s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 47s
the patch passed

_ Other Tests _

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

43m 30s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 3e177a1c62b0 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
95 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 10s
branch-2 passed

+1 :green_heart:
checkstyle
1m 29s
branch-2 passed

+1 :green_heart:
spotbugs
2m 44s
branch-2 passed

_ Patch Compile Tests _

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

-0 :warning:
checkstyle
1m 27s
hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

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

+1 :green_heart:
hadoopcheck
15m 37s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 47s
the patch passed

_ Other Tests _

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

43m 30s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 3e177a1c62b0 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
95 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 22s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
branch-2 passed

+1 :green_heart:
compile
1m 10s
branch-2 passed

+1 :green_heart:
shadedjars
7m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
1m 16s
the patch passed

+1 :green_heart:
javac
1m 16s
the patch passed

+1 :green_heart:
shadedjars
7m 24s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
138m 37s
hbase-server in the patch passed.

169m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/testReport/

Max. process+thread count
4373 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 22s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
branch-2 passed

+1 :green_heart:
compile
1m 10s
branch-2 passed

+1 :green_heart:
shadedjars
7m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
1m 16s
the patch passed

+1 :green_heart:
javac
1m 16s
the patch passed

+1 :green_heart:
shadedjars
7m 24s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
138m 37s
hbase-server in the patch passed.

169m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/testReport/

Max. process+thread count
4373 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 29s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 40s
branch-2 passed

+1 :green_heart:
compile
1m 18s
branch-2 passed

+1 :green_heart:
shadedjars
7m 13s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
1m 11s
the patch passed

+1 :green_heart:
javac
1m 11s
the patch passed

+1 :green_heart:
shadedjars
7m 59s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
209m 25s
hbase-server in the patch passed.

241m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1536ea91ae89 4.15.0-126-generic #129-Ubuntu SMP Mon Nov 23 18:53:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/testReport/

Max. process+thread count
2887 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 29s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 40s
branch-2 passed

+1 :green_heart:
compile
1m 18s
branch-2 passed

+1 :green_heart:
shadedjars
7m 13s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
1m 11s
the patch passed

+1 :green_heart:
javac
1m 11s
the patch passed

+1 :green_heart:
shadedjars
7m 59s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
209m 25s
hbase-server in the patch passed.

241m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1536ea91ae89 4.15.0-126-generic #129-Ubuntu SMP Mon Nov 23 18:53:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cec9f18737

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2849/1/testReport/

Max. process+thread count
2887 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Running tests locally to make sure we don't have a similar problem to last time :)

Not observing any run-away logging for replication tests in hbase-server. 👍🏼

Running tests locally to make sure we don't have a similar problem to last time :)

Not observing any run-away logging for replication tests in hbase-server. 👍🏼


apicalls.d doesn't follow all children, only fork‘ed ones

There's a bug in my implementation of apicalls.d that prevents it from following exec’ed children :-1:

On the other hand, if they were fork’ed it works like a charm)

I guess the reason is attaching dtrace way too early — when shared libraries are not loaded yet into the child address space, and thus probes from pid provider could not be installed on them.

OK, tried to fix that with https://github.com/rodionovd/cuckoo-osx-analyzer/commit/e590724af2b50f2e1a46f4e8efd7217f2cbd82dc. But it doesn't work all the time (maybe 1 of 20 tests fails on my machine). I believe the way dtrace firing exec-related probes maybe a reason why it fails from time to time. Need to investigate it more, though.

Another try: https://github.com/rodionovd/cuckoo-osx-analyzer/commit/d776c07355b417819d00842ed3ea39f06188d5d5. Here I've replaced the «master–child» script model to «many masters», so the single dtrace script now watches only it's own direct children (not grandchildren).


Cleanup of checks for old versions

Checks for old versions of firefox (3.x) removed

My first modest contribution on github. A fix for issue 3 Remove super ancient code that will never happen anymore


Add preprocessor directives

Mostly fixes #15
I stole the preprocessor rules from tree-sitter-c and modified them to fit the Fortran grammar.
"Simple" stuff is supported, including #include, #define, #if and #ifdef. One big limitation is that preprocessor directives in continuation lines are not supported, so something like:
use mod, only: a, b &
#ifdef HAVE_C
   , c
#endif

is not parsed correctly. This mostly corresponds to not supporting the preprocessor splitting up expressions -- which is generally not good practice anyway.
Use of preprocessor macros is also mostly not supported. In particular, it's not uncommon to do something like:
#define MyType type(_mytype)

MyType :: var

Allowing any identifier as a type name causes all sorts of clashes with other rules, so I've not made a serious attempt to support this.
There are still some other edge cases that won't work. The general trick to get #if working is via the function preprocIf(suffix, content) to define a recursive rule:
    ...preprocIf('_in_module', $ => seq(
      repeat($._specification_part),
      optional($.internal_procedures)
    )),

    module: $ => seq(
      $.module_statement,
      repeat(
        choice(
          $._specification_part,
          alias($.preproc_if_in_module, $.preproc_if),
          alias($.preproc_ifdef_in_module, $.preproc_ifdef)
        ),
      ),
      optional($.internal_procedures),
      $.end_module_statement
    ),

This gets complicated because Fortran is very structured, and the child nodes of preproc_if can basically have any children their parent node could have. This means we end up having to define a new rule for every "kind" of possible parent node -- and I've only done the most common ones.

Preprocs are a mess since it's a different language within a language and basically anything goes. Sounds like this is probably the best support we can offer within reason? I don't have any issue with hitting the high points and calling it.

Yep, I think this offers pretty decent support for the majority of projects. This successfully parses about 86% of the 500 or so .F90 files I have in my corpus -- and a good chunk of those failures are from other missing features.
Ok to merge?

Great work, thanks for that.


query filtration by measurement source.

[ ] - bloom filter to measurement source
[ ] - filtration in ReadInterval
[ ] - filtration in RadInTimePoint

in #19


related pairing_profile and pairing_key fails on terraform destroy

resource "illumio-core_pairing_profile" "terraform_pairing_profile_1" {
name = "terraform_pairing_profile_1"
enabled = true
labels{
  href = illumio-core_label.terraform_app_label.href
}

labels{
  href = illumio-core_label.terraform_loc_label.href
}

labels{
  href = illumio-core_label.terraform_env_label.href
}

allowed_uses_per_key = "unlimited"
key_lifespan = "50"
env_label_lock = true
loc_label_lock = true
role_label_lock = false
app_label_lock = true
log_traffic = false
log_traffic_lock = true
enforcement_mode = "full"
enforcement_mode_lock = true
visibility_level = "flow_summary"
visibility_level_lock = true

}
resource "illumio-core_pairing_keys" "terraform_pairing_key_1" {
pairing_profile_href = illumio-core_pairing_profile.terraform_pairing_profile_1.href
token_count = 3
}
running terraform destroy results in
Error: not-found: /orgs/1/pairing_profiles/33/pairing_keys
This is due to dependent deletion of pairing_keys pairing_profile. The provider needs to check to see if the key exists before delete.

Hello Kyong, we are assigning these issue to our team and have started working on them. We will update here for any progress in resolving these issue.

@kyongkim-illumio We were unable to reproduce this issue. We tried to destroy the resources multiple times but it gave consistent outputs of successful creation and destruction.
Creation:
illumio-core_pairing_profile.terraform_pairing_profile_1: Creating...
illumio-core_pairing_profile.terraform_pairing_profile_1: Creation complete after 2s [id=/orgs/1/pairing_profiles/198]
illumio-core_pairing_keys.terraform_pairing_key_1: Creating...
illumio-core_pairing_keys.terraform_pairing_key_1: Creation complete after 1s [id=/orgs/1/pairing_profiles/198/pairing_keys]

Deletion:
illumio-core_pairing_keys.terraform_pairing_key_1: Destroying... [id=/orgs/1/pairing_profiles/198/pairing_keys]
illumio-core_pairing_keys.terraform_pairing_key_1: Destruction complete after 1s
illumio-core_pairing_profile.terraform_pairing_profile_1: Destroying... [id=/orgs/1/pairing_profiles/198]
illumio-core_pairing_profile.terraform_pairing_profile_1: Destruction complete after 1s

Can you please provide us TF files and if possible a video reference showing this error.

Deep, that issue is triggered by the UAT I had sent earlier. I'm wondering if it's more likely to occur with many resources being created simultaneously. Also, try creating more than 1 key associated with that profile. I'll send over the TF files I'm using to trigger that in an email.

Turns out this is a compatibility issue. Only the pre-21.2 PCE versions have this issue and those versions are not supported.


HTTPS calls are not registered by mitmproxy on MacOS

Problem Description
I have mitmproxy set up on a MacOS. Everything works fine but calls from two tools do not appear in the mitmproxy logs. The two tools are notation and oras. I am trying to understand the call flows for those tools to Docker Hub registry. Docker CLI calls are logged. Istn's mitmproxy be supposed to be systemwide?
Steps to reproduce the behavior:

oras push command doesn't get logged

System Information
Paste the output of "mitmproxy --version" here.
Mitmproxy: 9.0.1
Python:    3.11.2
OpenSSL:   OpenSSL 1.1.1t  7 Feb 2023
Platform:  macOS-13.2.1-arm64-arm-64bit

Istn's mitmproxy be supposed to be systemwide?

Depends on which mode you're running, see https://docs.mitmproxy.org/stable/concepts-modes/
Does oras even use HTTP? Did you configure it to use mitmproxy? I'm going to move this to discussions as this doesn't sound like a bug in mitmproxy.


With Reference to  issue #80

I went ahead with your solution as provided by you in issue #80 , I am still not able to install your package, version 3.0 requires, illuminate/contracts 5.2.* and lumen 5.5 has to have 5.5.*..  Please let me know if it can be used at all with lumen 5.5.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: remove illuminate/contracts v5.5.34
- Conclusion: remove laravel/lumen-framework v5.5.2
- Conclusion: don't install laravel/lumen-framework v5.5.2
- Conclusion: don't install laravel/lumen-framework v5.5.1
- Conclusion: don't install laravel/lumen-framework v5.5.0
- Installation request for laravel/lumen-framework 5.5.* -> satisfiable by laravel/lumen-framework[5.5.x-dev, v5.5.0, v5.5.1, v5.5.2].
- Conclusion: don't install illuminate/contracts v5.3.23
- Conclusion: don't install illuminate/contracts v5.5.0|install illuminate/contracts v5.3.23
- Conclusion: don't install illuminate/contracts v5.5.2|install illuminate/contracts v5.3.23
- Conclusion: don't install illuminate/contracts v5.5.16|install illuminate/contracts v5.3.23
- Conclusion: don't install illuminate/contracts v5.5.17|install illuminate/contracts v5.3.23
- Conclusion: don't install illuminate/contracts v5.5.28|install illuminate/contracts v5.3.23
- Installation request for vinkla/hashids 3.0 -> satisfiable by vinkla/hashids[3.0.0].
- Conclusion: don't install illuminate/contracts v5.5.33|install illuminate/contracts v5.3.23
- vinkla/hashids 3.0.0 requires illuminate/contracts 5.2.* || 5.3.* -> satisfiable by illuminate/contracts[5.2.x-dev, 5.3.x-dev, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4].
- Can only install one of: illuminate/contracts[5.5.x-dev, 5.3.x-dev].
- Can only install one of: illuminate/contracts[v5.3.0, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.3.16, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.3.4, 5.5.x-dev].
- Can only install one of: illuminate/contracts[5.5.x-dev, 5.2.x-dev].
- Can only install one of: illuminate/contracts[v5.2.0, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.19, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.21, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.24, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.25, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.26, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.27, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.28, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.31, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.32, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.37, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.43, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.45, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.6, 5.5.x-dev].
- Can only install one of: illuminate/contracts[v5.2.7, 5.5.x-dev].
- laravel/lumen-framework 5.5.x-dev requires illuminate/contracts 5.5.* -> satisfiable by illuminate/contracts[v5.5.34, 5.5.x-dev, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33].
- Conclusion: don't install illuminate/contracts v5.5.34|install illuminate/contracts v5.3.23

Try using the latest version of 3.0 which is 3.3.

Yes, it worked, when I tried with that version, should have first reported here. Thanks.


chore(release): cut v1.0.0-rc.4

[X] I have cherry-picked any changes labelled needs-cherry-pick-vX.Y.Z

[X] I have made all of the following version and patch updates:

Updated the container image tag in charts/osm/values.yaml
Updated the chart and app version in charts/osm/Chart.yaml
Updated the image tags used in the demo manifests
Regenerated the Helm chart README.md

[X] I have checked that the base branch for this PR is correct as defined by the release guide

Is this a release candidate? Yes

Codecov Report

Merging #4462 (6dcba54) into release-v1.0 (568e165) will increase coverage by 0.26%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release-v1.0    #4462      +/-   ##
================================================
+ Coverage         68.90%   69.17%   +0.26%
================================================
  Files               212      212
  Lines             14580    14580
================================================
+ Hits              10047    10085      +38
+ Misses             4481     4443      -38
  Partials             52       52

Flag
Coverage Δ

unittests
69.17% <ø> (+0.26%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/certificate/rotor/rotor.go
86.95% <0.00%> (+2.17%)
:arrow_up:

pkg/crdconversion/crdconversion.go
69.40% <0.00%> (+27.61%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 568e165...6dcba54. Read the comment docs.


Not working in IE

Hello,
It seems that the download-excel tag is not working in IE. It works fine in Chrome, but when I click on it in IE, nothing happens. Any advice on how to get this working would be appreciated!

@angiespencer Hi, sorry for the late response. Basically this component use a Blob object to create the download file and download.js library to trigger the download process. Download.js and Blob type aren't  support in IE9 or below.


Update doc comments for #gradient and #valueAndGradient.

The #gradient syntax was changed in https://github.com/apple/swift/pull/17470.
The of: label was removed and withRespectTo: was renamed to wrt:.
Add fixit to replace withRespectTo with wrt.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

Ok, if the fixit actually replaces wrt: with withRespectTo: instead of withRespectTo::, it's better to include the colon.

Do you want this behavior?
test.swift:1:16: error: use 'wrt:' to specify parameters to differentiate with respect to
#gradient(foo, withRespectTo: .0)
               ^~~~~~~~~~~~~
               wrt:
test.swift:2:16: error: use 'wrt:' to specify parameters to differentiate with respect to
#gradient(foo, withRespectTo:: .0)
               ^~~~~~~~~~~~~~
               wrt:

Currently, the behavior is:
test.swift:1:16: error: use 'wrt:' to specify parameters to differentiate with respect to
#gradient(foo, withRespectTo: .0)
               ^~~~~~~~~~~~
               wrt
test.swift:2:16: error: use 'wrt:' to specify parameters to differentiate with respect to
#gradient(foo, withRespectTo:: .0)
               ^~~~~~~~~~~~~
               wrt


[SPARK-43744][CONNECT][FOLLOW-UP]Throw error from the constructor

What changes were proposed in this pull request?
Made the stub constructor to throw ClassNotFoundException if called.
A tiny improvement to not recreate class loaders in executor if stubbing is not enabled.
Why are the changes needed?
Enhancement to https://github.com/apache/spark/pull/42069
Should be merged to 3.5.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests.

Merged to master and branch-3.5.


bad network link

"After multiple attempts to change the headers in the code, I am still encountering the 'bad network link' error. May I inquire if there are alternative solutions available? Your assistance would be greatly appreciated. Thank you for your time and consideration. Best wishes!"

Have you solved the 'bad network link'  problem?

Thank you for your concern. I have already resolved this issue.
Best regards!


"antigen theme" command in .zshrc not updating theme

I'm kinda new to ZSH customization, so I don't know if I'm doing something wrong. I'm so sorry if this is not the right place to ask this.
My .zshrc:
DEFAULT_USER="${USER}"
DISABLE_AUTO_UPDATE='true'

source /usr/share/zsh/share/antigen.zsh

antigen use oh-my-zsh

case ${TERM} in
    # Use Powerlevel9k if our terminal support 256 colors
    xterm*|rxvt*|Eterm|aterm|kterm|gnome*)
        POWERLEVEL9K_INSTALLATION_PATH="${HOME}/.antigen/bundles/bhilburn/powerlevel9k"
        POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD=0
        POWERLEVEL9K_COMMAND_EXECUTION_TIME_BACKGROUND='245'
        POWERLEVEL9K_COMMAND_EXECUTION_TIME_FOREGROUND='black'
        POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(status context dir rbenv vcs)
        POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(root_indicator background_jobs command_execution_time time)
        POWERLEVEL9K_STATUS_VERBOSE=false
        POWERLEVEL9K_MODE='nerdfont-fontconfig'

        # For testing purposes only
	echo 'using "powerlevel9k" theme'
        antigen theme bhilburn/powerlevel9k powerlevel9k
    ;;
    # Use a simpler theme if our terminal doesn't support 256 colors
    *)
        # For testing purposes only
	echo 'using "evan" theme'
        antigen theme robbyrussell/oh-my-zsh themes/evan
    ;;
esac

antigen bundle robbyrussell/oh-my-zsh plugins/catimg
antigen bundle robbyrussell/oh-my-zsh plugins/gitfast
antigen bundle robbyrussell/oh-my-zsh plugins/jsontools
antigen bundle robbyrussell/oh-my-zsh plugins/urltools
antigen bundle zsh-users/zsh-syntax-highlighting

antigen apply

Basically, I'm trying to use the evan theme when I login into a virtual console and Powerlevel9k on my graphical terminal (xfce4-terminal). Unfortunately, it's not working for me. I made a video showing the behavior:
https://www.youtube.com/watch?v=t5m3z8o2wok
Am I doing something wrong or is this an antigen issue? Any help is appreciated. Thank you!
Arch Linux x64
XFCE 4.12 (xfce4-terminal)
zsh 5.3.1
Antigen develop

This happens because Antigen compiles bundles to avoid loading them each time a terminal launches.

I see. So is there any workaround for this at the moment? Thanks for quickly answering me.

Yes, you could use ANTIGEN_CACHE to configure each branch with an alternative cache file:
case ${TERM} in
    xterm*|rxvt*|Eterm|aterm|kterm|gnome*)
        ANTIGEN_CACHE=$HOME/.antigen/init-xterm.zsh
    ;;
    *)
        ANTIGEN_CACHE=$HOME/.antigen/init-other.zsh
    ;;
esac

Please note this has to be done before sourcing Antigen.

We're gonna add an option to skip cache generation, probably for 2.0.1, as we are currently on a release :)

Thank you very much!

Closing for now. Thanks for reporting the issue. :+1:

What do you think maybe a good place for this information at the most top of the readme? It's completely unexpected behaviour.

Sounds good. In 2.1.0 it should not be a problem as Antigen will auto-detect it's configuration.
Nevertheless it should be clearly stated how Antigen loads its configs. I'm open to suggestions.

@desyncr please review #514


Feature Request: IdlBuffer Program

There has been some issue with supporting IDLs in the program binary via a new ELF header section, versus officially supporting IDLs in PDAs.
Given that Anza is prioritizing changes to make program binaries smaller & more efficient to load, it seems like officially supporting the IDL in PDAs is better for cluster performance.
Good place to start would probably be to copy the IdlInstructions from anchor's injected macros.
I think it would be awesome if uploading IDLs to this program was natively supported in solana program deploy as well

I think this is a great idea, especially if it was standard via the Solana/agave tooling. Having all programs upload their idl will boost comparability for programs

It might be interesting to consider some version pairing constraints. Imagine you store your program's version in the ELF header instead, and then when you register the IDL with IdlBuffer, the version has to match the deployed binary's program version (must be deployed, not a buffer, this way the ELF has been verified). This would unlock versioned IDLs and the ability to identify missing/outdated IDLs.
You could also - in the future - maybe outfit the IdlBuffer program to identify known interfaces in the IDL, to store PDAs that contain program IDs of registered SPL Token programs, for example.
In either case, the tricky part is for IdlBuffer to be able to verify the IDL is actually for the provided program. Otherwise, program authorities could register false IDLs for malicious programs. I suppose you can still do that with an Anchor program, though...

@buffalojoec updated the spec to incorporate the versioning feedback: https://solanafoundation.notion.site/Program-Metadata-128d36dad52d801e974fcc3a30736506

I think it's better to leave the IdlBuffer unopinionated for now (storing only authority & bytes) & allow developers to figure out versioning systems - like just getting metadata.version in Codama & Anchor would be a win.


Constructor shouldn't be asynchronous

new Embedly shouldn't need to get a callback as an argument.
If you need to send an http request to initialize the API just make a method for that.

Pardon my ignorance. Why?

It is simply bad practice.
Writing new Class() should return an instance. Not execute code, and even less being asynchronous.
I invite you to read the following answer for more details:
http://stackoverflow.com/a/24686979

Alright. I really don't want to add another step, things should be as simple as possible, so I'll probably do some lazy init on first call. It might take me a little, pretty busy, but I will accept a patch that doesn't add another step to using our API.


Strange project. Example not working

Simple example from Standalone page (https://yogalayout.com/getting-started/standalone/) not working.
It gives me thise results
Root:
bottom: 0, height: 300, left: 0, right: 0, top: 0, width: 500
Child1:
bottom: 0, height: 100, left: 0, right: 0, top: 50, width: 100
Child2:
bottom: 0, height: 100, left: 0, right: 0, top: 150, width: 100
Items are always stacked vertically.
Latest version from npm

Items are always stacked vertically

The website currently sets UseWebDefaults as part of YGConfig. This is confusingly not set by default as part of Yoga standalone, leading to a default flexDirection of column.


[Card] Enable definition tooltips as the title text (in place of info icon)

• Info icon prop still exists. This story does not replace that feature. This is an additional, mutually-exclusive property
• Ensure that the tooltip opens in an appropriate direction (not off the page to the left, when the card is on the left edge of the screen)
• Ensure that the tooltip opens at the proper z-index, and does not get covered up by other cards, card content, etc
• Allow a custom render inside of the tooltip (buttons, links, etc. Not just a label)
• Title text truncates into an ellipsis if it does not fit. There is no option for wrapping.

@JordanWSmith15 How does this feature operate with the overflow tooltip that is standard on the cards?

@davidicus Do you mean the info icon? My preference was to completely replace it, but @dianatran18 wants to continue to support them. First line in the description above:

• Info icon prop still exists. This story does not replace that feature. This is an additional, mutually-exclusive property

@JordanWSmith15 No if the card title is too long it gets ellipsis and a tooltip that shows the whole text.

@davidicus Got it. So in that case I guess we would want to pass that text into the tooltip, as the first paragraph of text.  Then, the help information would appear after, as a second paragraph. @dianatran18 can confirm.

OK. Any reason not to just use the info icon that is for that purpose? Just wondering why we are endorsing multiple ways to do things.

@davidicus I agree, but I think the definition tooltip is actually a much cleaner/condensed approach. The info icon takes up space and consumes space needed by the other icons that can appear on the right.  I will be setting it as the ONLY option in Graphite, and deprecating the info icon there. I am open to doing that in PAL as well, if you can convince @dianatran18 :)

This also conflicts with the multiline prop we have for title to be on multi-line. @bjornalm we will have to warn with both are added together.

Note: especially if there are actions in the tooltips like in the two cards in the example, the tooltip needs to be triggered on click for accessibility reasons.

Agree about click vs hover. I also prefer click due to touch screens/mobile.

But for the truncated text, do we generally style our own tooltip like that, or use the browser tooltip to show the full name? I don't know how it works in other components.

@dianatran18 We do both. I think the browser tooltip (I assume you are referring to the title attribute) is more commonly used for smaller elements like List and Dropdown items

If we keep the browser tooltip on hover for truncated text we can perhaps let the TooltipDefinition open on click and only show custom content there like Jordans initial suggestion?
I don't typically like to rely on hover effects, because I anticipate touch screens/mobile scenarios to come into play in the future for all of these applications.

@JordanWSmith15 Turns out I can't use the TooltipDefinition component for this since it doesn't support interactive content. Trying to click a button in the TooltipDefinition will close the tooltip and the click event from the button is never triggered.
So I will use the normal "Tooltip" function and make it look like the TooltipDefinition. The normal "Tooltip" also has the advantage that it can be triggered by click.


[Feature Request]: RAG emmbeddings & 挂外部文档

Problem Description
when writing some personal document I need my own doc, if there are RAG & Emmbedding function to let me upload my personal file it will be very helpful.
当写自己私有文档时需要自己的其他文档作为参考，如果可以提供挂载外部文档的功能将非常有用。
Solution Description
add vector db like chromadb to save local files.
增加向量数据库比如chromadb用来保存本地文件。
Alternatives Considered
No response
Additional Context
No response

Implementing this feature in desktop or mobile apps is a piece of cake. However, the web version presents a challenge, especially when it comes to storing files in local storage.

Does it mean, in order to ensure consistency across multiple platforms, this project will not consider features that are difficult to implement on some platforms, no matter how useful the feature may be?
I prefer to first integrate these key features on platforms where they are easy to implement.

Problem Description
when writing some personal document I need my own doc, if there are RAG & Emmbedding function to let me upload my personal file it will be very helpful. 当写自己私有文档时需要自己的其他文档作为参考，如果可以提供挂载外部文档的功能将非常有用。
Solution Description
add vector db like chromadb to save local files. 增加向量数据库比如chromadb用来保存本地文件。
Alternatives Considered
No response
Additional Context
No response

Implementing this feature in desktop or mobile apps is a piece of cake. However, the web version presents a challenge, especially when it comes to storing files in local storage.

It is feasible to store only the reference via localstorage. However, when the file changes, the historical references will become invalid.
The most reasonable way is to introduce back-end support and implement relevant object storage capabilities on the back-end

The workload to support embedding seems to be fine, but it needs to be tied to the user's openai account

v2.15.0支持插件功能（可以将外部的api以gpts action一样的方式包装成plugin使用）
这里有一个示例，将fastgpt的api包装成plugin在聊天中使用
https://github.com/ChatGPTNextWeb/NextChat-Awesome-Plugins/tree/main/plugins/fastgpt


can't compile - are all branches broken ???

Trying to compile on MAC, but it seems every branch is broken (unstable, master were tried):
just a few...
es-core/src/AudioManager.h:15:42: error: a space is required between consecutive right angle brackets (use '> >')
static std::vector<std::shared_ptr> sSoundVector;
^~
> >
EmulationStation-master/es-core/src/AudioManager.cpp:6:34: error: a space is required between consecutive right angle brackets (use '> >')
std::vector<std::shared_ptr> AudioManager::sSoundVector;
EmulationStation-master/es-core/src/AudioManager.cpp:19:35: error: a space is required between consecutive right angle brackets (use '> >')
std::vector<std::shared_ptr>::const_iterator soundIt = sSoundVector.cbegin();
EmulationStation-master/es-core/src/ThemeData.h:26:7: error: ISO C++ forbids forward references to 'enum' types
enum PropertyFlags : unsigned int
^
/EmulationStation-master/es-core/src/ThemeData.h:26:21: error: expected unqualified-id
enum PropertyFlags : unsigned int
^
EmulationStation-master/es-core/src/ThemeData.h:45:7: error: exception specification of overriding function is more lax than base version
class ThemeException : public std::exception
EmulationStation-master/es-core/src/GuiComponent.cpp:314:18: error: use of undeclared identifier 'POSITION'
if(properties & POSITION && elem->has("pos"))
^
/EmulationStation-master/es-core/src/GuiComponent.cpp:320:30: error: no member named 'SIZE' in namespace 'ThemeFlags'
if(properties & ThemeFlags::SIZE && elem->has("size"))

so thats a yes?


don't open falsy links

Just a note for the future - avoid ' in branch name, it makes it unweildy to deal with in the CLI and can break some git scripts.


Use smaller yolov5

Have been training with --img 416 but images are approx 285x180 pixels, meaning I have been oversized. This means the generated anchor boxes are probably also oversized

Noticed that roboflow actually stretches to 416x416 as a preprocessing step, so this might not be an issue


fix: parameter order for date-fns#differenceInMinutes

Closes https://github.com/Kong/insomnia/issues/5084
Previous PR https://github.com/Kong/insomnia/pull/5331/ fixed the time for tokens but broke the time in other places
This PR ensures it is correct in both places

Thank you @arunnalla, tested locally, LGTM 👍


fix nit in README

This PR fixes the instructions for running an individual test by removing the hardcoded TestSaveFiles class name... which initially confused the heck out me :)

Thanks for the pull request, @cgoldberg! I've created OSPR-1340 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.
If you like, you can add yourself to the AUTHORS      file for this repo, though that isn't required.     Please see the CONTRIBUTING     file for more information.


Bug or feaure request?

Not sure if it is a bug or something that is not yet been considered
mtcarsnew <- mtcars |>
  dplyr::mutate(cyl = as.factor(cyl))

fit <- lm(formula = mpg ~ wt:cyl,data = mtcarsnew)
equatiomatic::extract_eq(fit)

$$
mpg = \alpha + \beta_{1}() + \beta_{2}() + \beta_{3}() + \epsilon
$$
Created on 2024-07-17 with reprex v2.1.0
The output should be something like:
$$
mpg = \alpha + \beta_{j}(wt)  + \epsilon
$$

No, this is not a model with interactions. This equation is simply a model representing different slopes. Standard model. You would then test the H0: beta_j = beta.

With the default treatment contrast matrix, the first level is considered as reference and the other betas are change in the slope. Hence, if you want a model with a different slope for each level of cyl, you have to use mpg ~ wt + wt:cyl. Then, you got the following equation:
$$
mpg = \alpha + \beta_{1}(wt) + \beta_{2}(wt \times wt_{cyl6}) + \beta_{3}(wt \times wt_{cyl8}) + \epsilon
$$
beta_1 is the slope adjusted to cyl = 4, then beta_2 and beta_3 are changes from the beta_1 slope, respectively for cyl = 6 and cyl = 8. I think this is what you are looking for, although parameterized differently. mpg ~ wt:cyl does not match H0: beta_j = beta in R, at least with the default contrast treatments. It is not the way lm()was programmed.

Here, you have to check that beta_2 and beta_3 are not significantly different to zero to match your H0:beta_j = beta hypothesis.

Thanks @phgrosjean . I am just looking for a clean representation of a formula. I am not using lm. I just used lm to create an example model that i can translate through this package into a form that i want. And the specific example i gave is just that. I am not using mtcars for anything, just to give an example of a representation of a formula i was hoping your package might be able to translate. You have a nice package i'll use it for other things but probably not for this project


Fix loading document type attributes from DynamoDB when when saveUnknown=true

This PR fixes an issue when using saveUnknown + useDocumentTypes and trying to retrieve  a model that hasn't yet been "used" for example:
  var Cat = new Schema({
    id: Number,
  }, {
    useDocumentTypes: true,
    saveUnknown: true,
  });

  // Assume an item is in the Cat table:
  // {
  //   id: { N: '1' }
  //   petProperties: {
  //     M: {
  //       name: { S: 'Fluffy' },
  //       age: { N: 10 },
  //     }
  //   }
  // }

  Cat.get({ id: 1}};

  // throws SyntaxError: Unexpected token o in JSON at position 1

This is because since the Cat schema doesn't have getProperties attribute Schema.parseDynamo will create an new attribute with an Object type because Attribute.lookupType returns Object for Dynamo "'M" types.
This then causes the Attribute.parseDynamo to be parsed using JSON.parse instead of the correct mapify.
Interestingly this error doesn't happen if the model has been used to create (or put/save) before doing get/query/scan.
  var Cat = new Schema({
    id: Number,
  }, {
    useDocumentTypes: true,
    saveUnknown: true,
  });

  Cat.create({
    id : 1,
    petProperties: {
      name: 'Fluffy',
      age: 10,
    },
  );

  // Cat's schema now has a petProperties attribute

  Cat.get({ id: 1}};

  // No error

This is because when Cat.create runs, it creates the petProperties attribute in the model's schema, and when Cat.get runs, Schema.parseDynamo see that is has petProperties and doesn't try to create a new, incorrectly-typed Attribute.

Thanks so much for this @jonathonlui. I'm going to have @brandongoode review this at some point before we get it merged in. We will aim to get this in version 0.9. Thanks again!


[Data Quality] Column is displayed for unsupported columns

Affected module
UI
Describe the bug
When defining a column test, I expect only relevant tests to be offered given the column data type.
For example, the columnValuesToMatchRegex is only expected to run on STRING types yet I am offered to run it on a numeric type in this example:

Expected behavior
For a column test, display only the tests that apply to the column data type.
Version:

OpenMetadata version: 1.4.3

{
  "name": "columnValuesToMatchRegex",
  "fullyQualifiedName": "columnValuesToMatchRegex",
  "displayName": "Column Values To Match Regex Pattern",
  "description": "This schema defines the test ColumnValuesToMatchRegex. Test the values in a column to match a given regular expression. ",
  "entityType": "COLUMN",
  "testPlatforms": ["OpenMetadata"],
  "supportedDataTypes": ["BYTES", "STRING", "MEDIUMTEXT", "TEXT", "CHAR", "VARCHAR"],
  "parameterDefinition": [
    {
      "name": "regex",
      "displayName": "RegEx Pattern",
      "description": "The regular expression the column entries should match. For database without regex support (i.e. MSSQL, AzureSQL) this test will use `LIKE`.",
      "dataType": "STRING",
      "required": true
    }
  ],
  "supportsRowLevelPassedFailed": true,
  "provider": "system"
}

The test definition has the supported dtype, we should check if it is enforced correctly from the ui


Check return values of mmap calls

Against all intuition, mmap returns MAP_FAILED (-1) instead of NULL
in an error case. This commit fixes 3 occurrences of this bug.
One of the bugs was reported in
https://bugs.launchpad.net/qemu/+bug/1879998 and the other two where
found using the script from https://github.com/hannob/mmapfail/
Please do not submit a Pull Request via github.  Our project makes use of
mailing lists for patch submission and review.  For more details please
see https://open-power.github.io/skiboot/

Hi, thanks for the patch. Are you planning on sending this to the list or do you want me to pick it up?

I closed this PR because I missed https://github.com/open-power/skiboot/pull/252 and https://github.com/open-power/skiboot/pull/255, both of which address the same issue.


People List Scene

Depends on #95 #111

Hi, I made the person card for this but then realized it was blocked. I'll stop working on this now but whoever works on this issue when it become unblocked doesn't have to make the person card.

After discussing with @prutherford we are going to skip this for initial release. Patrick says the current list of "all people" is not used by field at all. He wants to do 1+ lists that are relevant to the user. Which can come later.


Bootstrap updated to 2.0

There are a few CSS issues since the new bootstrap.css use differnent class names. We fixed that on the base.html and topbar.html.
new boostra.js calls for jQuery>=v.1.7, we have upgraded jquery and it worked charms

sweet!
On Wed, Mar 7, 2012 at 4:34 PM, Myf Ma <
<EMAIL_ADDRESS>
wrote:

There are a few CSS issues since the new bootstrap.css use differnent
class names. We fixed that on the base.html and topbar.html.
new boostra.js calls for jQuery>=v.1.7, we have upgraded jquery and it
worked charms
You can merge this Pull Request by running:
git pull https://github.com/modilabs/formhub bootstrap
Or you can view, comment on it, or merge it online at:
https://github.com/modilabs/formhub/pull/218
-- Commit Summary --

update bootstrap, leaving few problems with the js
Merge branch 'master' of https://github.com/modilabs/formhub into
bootstrap
rename
modified html templates in order to fit boostrap2.0, also updated jQuery
to 1.7

-- File Changes --
M main/static/bootstrap/bootstrap.css (4167)
M main/static/bootstrap/bootstrap.min.css (914)
A main/static/bootstrap/bootstrap.min.css.old (330)
A main/static/bootstrap/bootstrap.old.css (2381)
M main/static/bootstrap/formhub-extras.css (5)
A main/static/bootstrap/js/bootstrap.js (1720)
A main/static/bootstrap/js/bootstrap.min.js (1)
M templates/base.html (13)
M templates/topbar.html (10)
-- Patch Links --
https://github.com/modilabs/formhub/pull/218.patch
https://github.com/modilabs/formhub/pull/218.diff

Reply to this email directly or view it on GitHub:
https://github.com/modilabs/formhub/pull/218

wait, dropdown menu is still broken, didn't see it before. back to the code

Cool, we can go through and delete some of the deprecated files before we merge

more css rendering problems in the body, will report soon

I removed a bunch of the deprecated files, if we need uminizied files for reference we can view them in the bootstrap github repo, if we really need them, add them back in.
I'm going to close this request for now, we can reopen it when it's ready.


Full Stack Traces for Unity Windows builds

Description
When building games for Windows in Unity, busnag only shows stacktraces without lines. Having lines would make it easier to debug errors.
Describe alternatives you've considered
According to this page: https://docs.bugsnag.com/platforms/unity/#showing-full-stacktraces
this is currently only possible on ios and android. Similar functionality for Windows/Linux/Macos would be amazing.

Hi @staneta 👋🏻, we do have an item in our backlog aimed to support Windows symbolication in Unity, however we don’t have a firm ETA for this functionality.
Once there will be any updates on this, we’ll make sure to update this thread.


tests: larger query leader timeout

10ms is too short, it may never get responses even if a leader is elected.
Close #3079
Close #3089

/run-unit-test

But it will retry after timeout, so is it OK to take 10ms * 500 finish a campaign when election timeout is 250ms? If you change it to 100ms, does it mean it will take at least 50s to report error when there is something wrong?

Besides campaigns, query requests are queued in raftstore channel, so if there are many time consuming requests or slow disk, 10ms * 500(5s) may not enough.

many time consuming requests or slow disk

Any logs or metrics?

#3079 and #3080 have backtraces, but test's log is gone, unfortunately. You can see #3073, jenkins-ci-tikv/unit-test failed frequently.

It fails doesn't mean 5s is too short. It can due to inappropriate configured isolation or anything possible. In 5s it can campaign 10 times. There is probably something wrong when it fails to campaign after trying so many times.

A friendly ping.


No module named 'config'

Thanks for your great work!    When I run src/run/predirct.py, it pointed out No module named 'config'. Should I set the working directory ?  My current working directory is already SADRN.

Hi, how did you solve this issue? I am running into the same problem and not sure what the solution is.

Just get the config module using pip install config

@haoxurt How did you solve the issue

export PYTHONPATH=/home/"username"/SADRNet:$PYTHONPATH


Respect the system mode

Is there any way to do so to respect the system theme? Instead of manually setting the schedule in plugin. I mean if I have automatic theme switching enabled in the system. The problem is that macOS automatically switches it from sunset to sunrise based on my location, but in the plugin schedule fixed and in this case I need to sync it every time.

I'm pretty sure that to follow system theme you can just use native Obsidian setting:
→ Settings
→ Appearance
→ Base color scheme
→ Adapt to system

@a13ph yeah, but I want to use different themes for light and dark mode, that's why I chose this plugin. Unfortunately obsidian doesn't provide settings for it. We can select only one theme.

I am not sure if there is a way to get the system theme schedule using the Obsidian API.
I'll spend some time researching and see if this is possible.

I suppose we could add the option to settings, and then use window.matchMedia to detect the colorscheme mode in the system. If it make sense :)


Separate examples by sub-pages. Update all examples. Add back Poise. Minor fixes.

Draft for #86 and other fixes.
I put each example on a sub-page, updated the examples, and added the Cargo.toml file aswell.
The examples are from https://github.com/shuttle-hq/shuttle-examples/pull/60.

If this looks good, I can continue doing this for Actix and Serenity.
Closes #86

Hey @jonaro00, thanks for this, looks very clean!
I have a couple of questions:

I might be out of the loop but why are we moving the contributing part of it over to GH? For easing maintenance?
I saw you've added some icons on various spots but when trying to run your changes locally, nothing pops up.
Some links in the sidebar are now "empty" -- eg. if I click on "Contributing", I get an empty docs page
What is supposed to go under 'All Examples'?

Other than that, thanks for also sorting out some of the minor things such as changing 'API Docs' to 'Crate Docs' and others!

Mainly that but also that the graph fails to render on the webpage.
2-4. Oh, it seems like I was using a bunch of Mintlify 3 features without knowing. I used v3 locally when introducing these. I guess #130 is needed before this, but you can try it locally if you upgrade. The icons will then show up, it's just plain font-awesome. Let me know if they are fitting or not, or if all pages should have icons etc. The "empty" links you got will correctly link to the external page in v3. All Examples link to the examples repo.

The Crate Docs name is tricky. It links to runtime docs, but we have so many crates... But that one can be considered a homepage. maybe add links to the other's docs in there.

That's fine. We can check with Mintlify whether they can add mermaid support if that was the deal breaker :)
2 - 4. I'll comment that over there.

re: Crates docs - let's keep it this way for now (linking to the runtime docs)

@jonaro00 lmk when this is ready for final review! :)

I think it is. There should not be any major v3 additions in here now. (If there are, they will work in production anyways :P)


updatehub-callbacks: drop usage of run-parts

Drop usage of run-parts in favour of custom implementation.
We need to run a code between programs execution, which evaluates
the stdout to determine the state flow.

@gustavosbarreto the commit is good but we need the Signed-off-by ;-)


No variable "fullName" in ListView class

Hi there i was following your guide to create a list view. Unfortunately on line 669
(listView.fullName = 'Test__c.MyListView';) it produces an ERROR that says there is no variable fullname in listview. Actually i inspected the class and found out that there is actually no variable "fullname" in the ListView Class.
Can you please help in this issue

If you use the MetadataService.cls from this repository there is.


examples not working on Android

Simple example not working on android but works on iOS.
And it gives a red border to the Interactable.View
<ScrollView style={{flex:1}}>
<Interactable.View
  horizontalOnly={true}
  style={{width: '100%', borderWidth: 0}}
  snapPoints={[{x: 0}, {x: -200}]}>

  <Text style={{
    fontSize: 16, fontWeight: 'bold', backgroundColor: colors.background,
    paddingLeft: 15, paddingBottom: 8
  }}>Text</Text>

</Interactable.View>
</ScrollView>

Any  idea what's going on?

@aminroosta  No idea . I made it worked a month ago but when using it again in a different project , it do gives the red border and doesn't work.

@yash2code Can you please check in which version was it working? Maybe it's broken recently.

@aminroosta  I was using RN 0.46.4 and interactable version 0.0.9

@aminroosta Do tell if it worked! :dancer:

@yash2code
I can confirm that v0.1.3 (and probably earlier versions) work.
// in MainApplication.java
    @Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
          new MainReactPackage(),
          new Interactable() // Add this line
      );
    }

Somehow react-native link react-native-interactable failed to add that line.
I'd suggest to close this issue :-)


cloud: cannot determine metric endpoint name

The shepherd is currently spamming
etrics.go:74] Unknown Equinix API GET /projects/7d6e77dd-dba3-4158-bdca-becef01bcc7d/hardware-reservations - cannot determine metric endpoint name

This was a typo inside the metrics matcher https://review.monogon.dev/c/monogon/+/1823


Are the two model acgan.py and sgan.py the same?

acgan.py    --- sgan.py

They are quite similar, but if you look at how the generators are defined you see that the ACGAN generator takes both noise and labels as input, while the SGAN generator only takes noise as input.

oh, I see, thanks!


Update cppslippi to <IP_ADDRESS>

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[N/A] The "supports" clause reflects platforms that may be fixed by this new version
[N/A] Any fixed CI baseline entries are removed from that file.
[N/A] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

I'm immediately closing this because I forgot some changes that I would like to roll into this release.


Enumerable

Created a class MyList that has an instance variable @list.
In MyList implement a method #each that yields successive members of @list and uses the MyEnumerable module.

Created a module MyEnumerable that implements the following methods (they should have the same functionality as methods in Enumerable):

#all?
#any?
#filter

Create our list
irb> list = MyList.new(1, 2, 3, 4)
=> #<MyList: @list=[1, 2, 3, 4]>
Test #all?
irb> list.all? {|e| e < 5}
=> true
irb> list.all? {|e| e > 5}
=> false
Test #any?
irb> list.any? {|e| e == 2}
=> true
irb> list.any? {|e| e == 5}
=> false
Test #filter
irb> list.filter {|e| e.even?}
=> [2, 4]

@DammyShittu Thank you for reviewing my project


fix: broken link and image property

Description

fix: broken Next.js link and image property
add: more steps to README > Getting Started

Oh, I didn't realise I closed it. I can make a new PR in a bit

Done: https://github.com/ndom91/next-auth-example-sign-in-page/pull/4#issuecomment-1525927820


Uploads Service implementation post-Azure

The service definitions assumed we would come up with a way to implement the Uploads service that doesn't involve using Azure (like the previous C# implementation did). Now that everything is "de-Azure-fied" lets figure out what to do about the Uploads Service.

@LukeTillman @SonicDMG Is it still relevant? I'd suggest to solve/close the issue.

Closed as inactive


hubble: Add --hubble-monitor-events flag

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

Related https://github.com/cilium/cilium/issues/19929
Adds a --hubble-monitor-events flag that let's a user control the event types that get to the hubble subsystem.
Add `--hubble-monitor-events` flag, to control the event types that get to the hubble subsystem.

Why
Nodes with traffic heavy workloads are doing 30k+ flows per second. This causes very high CPU utilization for the cilium-agent container. We'd like to be able to only monitor drop and other events and ignore the normal flows.
Flame graph showing that most of the CPU time is spent in the hubble subsystem decoding the events:

cc @michi-covalent

Oh and worth noting that I think we can take this further in order to disable these in the datapath, but we can always do that in a subsequent PR. It looks to me like this approach already will provide benefit to users even if we can take the approach further and make it even faster. :rocket:

Just thinking this through a bit further: should this be an allow list, or a block list? Since the default is already to emit everything, perhaps this should be a block list? Or should we have a 2 flags, one for allow, one for block.

either allow or deny list works for me. i don't need both.
i don't feel strongly enough about deny list to suggest re-implementing this as a deny list. let's see if @gandro or @kaworu has preference.

@epk btw let's squash these 2 commits into 1 with sign-off from both you and me.

i don't feel strongly enough about deny list to suggest re-implementing this as a deny list. let's see if @gandro or @kaworu has preference.

I have a slight preference for an allow-list. We introduce new events every other minor release, and I think it's better for users who have filters on the event types to opt-in to them, rather than opting out.

Thanks a lot for this folks!

Sorry for the delay on this folks, I have addressed the feedback.
Let me know if there's anything else.

/test

/test

test-1.27-net-next failure looks like https://github.com/cilium/cilium/issues/24966. it might have gotten fixed by https://github.com/cilium/cilium/pull/24785. i'll rebase and re-run the test

/test

test-runtime: hit https://github.com/cilium/cilium/issues/22373

/test-runtime

ci-multicluster: filed https://github.com/cilium/cilium/issues/25064

/ci-multicluster

Can we back-port this to 1.12 / 1.13? that would really help with managing Hubble CPU usage.
Cheers.

Opened https://github.com/cilium/cilium/pull/25167 addressing @marqc's comments.

Can we back-port this to 1.12 / 1.13? that would really help with managing Hubble CPU usage.

In general, only bugfixes are backported, see the backporting policy here. This is considered a new feature. This feature will be made available in an upcoming v1.14 snapshot release which you're welcome to try out and provide feedback. Furthermore, as we can see from recent posts on this PR, there's still active development on it, so it would be premature to release at this stage without further testing and feedback.

@joestringer that make sense, thank you for the details.


Update local installation instructions for 0.19

Projects identified as Elm 0.19 will use the elm.compiler option instead of the elm.makeCommand option.

For reference, the differentiation happens here:
https://github.com/Krzysztof-Cieslak/vscode-elm/blob/735723afacdfb92d1ac7c045d4665a8df52b3c13/src/elmLinter.ts#L117-L127

Thanks a lot!


feature: multiple axes in charts

Tracking more than one value axis is necessary for e.g. scatter plots and manipulating charts with a secondary axis.
In the oxml/chart/chart.py file, the catAx and valAx should be ZeroOrMore arrays of axes instead of ZeroOrOne values that store only the first axis in a chart.  I think it would be nice to preserve the behavior today where you get the first axis with e.g. chart.value_axis and only expose the multiple axes via some new API like chart.value_axes_list.
There will need to be provisions for working with axis IDs and assigning the axis IDs for each plot within a chart.  The pptx.chart.axis._BaseAxis will need to be able to set c:crossAx, c:crosses, and c:axPos values.

@huandzh, those are some great changes but as far as I can tell, there's no implementation of secondary axes.  Can you create charts like the one I pasted below?
@scanny, this scatter plot has 4 <c:valAx>s (with 2 <c:scatterChart>s) and no category axes:

This surface plot has a <c:catAx>, a <c:valAx>, and a <c:serAx> (which are not yet supported).

I'll start writing a feature analysis...

I've uploaded a draft of an analysis page.  It's here.

Hi Alex, this looks great :)
I'm traveling this week, but will take a closer look over the weekend and provide some comments.

Hi @AlexMooney, I read through your draft feature analysis. My main first reaction is that I'm rethinking my idea of the axis access API being Chart.value_axis, .secondary_value_axis, .category_axis, .secondary_category_axis. That would be fine if that were the most there could be, but your example showing four value axes demonstrates that design is not going to be general enough.
Taking a closer look at the Microsoft API it looks like the possible axis configurations for a chart are a partial cover of a three-dimensional space where axis-type(value, category, series), axis-group(primary, secondary), and orientation(horizontal, vertical) are the three dimensions.
I'm thinking the best next step is a reasonably thorough case analysis about what configurations are possible. Those would inform the API design and then go on to be test cases.
 Then having .type, .axis_group, and .orientation properties on each axis so they could each be well characterized. The .value_axis and .category_axis properties on Chart could stay since they're so handy for the most common cases.
I suppose the next step after that would be to have a way to add an axis. The MS API uses the Chart.HasAxis(type, group) method/property for this, but I think we'd want something a bit more Pythonic in this case; it would be odd to see something like this in Python code although it could be made to work with descriptors or something:
chart.has_axis(XL_AXIS_TYPE.VALUE, XL_AXIS_GROUP.SECONDARY) = True

Off the top of my head I'd be thinking something more like:
chart.add_axis(XL_AXIS_TYPE.VALUE, XL_AXIS_GROUP.SECONDARY)

I don't see how they manage to cover all the possibilities with just the two parameters though. I suspect they overload XlValue and XlCategory to mean VALUE+VERTICAL and VALUE+HORIZONTAL respectively in the case of an XY Scatter plot. It would take some experimentation with the MS API to discover that I expect.
Anyway, it looks like it's shaping up to be a fairly big job to handle the general case. I think the following list of features would be a good place to start because 1) they don't break anything, 2) they would be required infrastructure for the rest of it, and 3) they would provide an opportunity to uncover more of the details required for the other bits like adding a new axis:

Chart.Axes -- collection of all axes in chart, having list semantics I think for a start, but possibly using dictionary-style lookup on a 3-tuple (type, orientation, group).
_BaseAxis.type, .orientation, and .group

On the issue of validation, I think we'd need to have the case analysis worked out pretty firmly so we could keep the user from doing something that PowerPoint would barf on. It creates a support problem when newbie users can generate a presentation that won't load. Much better to just raise an exception when they try something we know won't work. Of course that means we'd need to do the analysis to know what will work and what won't.

In the XML, orientation and group are not directly represented.  Instead of orientation there is position (top, bottom, right, left; presumably others for 3d charts), although we could make a lookup to do something like 'v' if position in ['l', 'r'] else 'h'.  To determine the group, we'll need to look at which axis Ids are associated with the plots in a given chart.  I think the first occurance of an orientation in the chart becomes the primary axis.  If that's true, we would need to iterate over the plots and the first vertical axis referenced in the c:axId tags becomes the primary vertical axis.  The next step is to test changing primary and secondary axes by reordering them in plots.  If it works, .group should be relatively simple.
_BaseAxis.type and _BaseAxis.position have been added in my multiple_axes branch.

I added the _BaseAxis.orientation and Chart.axes which supports the same indexing stuff that Chart.plots does.
Not sure how to implement _BaseAxis.group without butchering things.  Each axis would have to know where it fell in the list of all axes to figure out if it was the first or second instance of a particular orientation.  Since an instance of _BaseAxis isn't aware of all axes involved in a chart, it seems like it has to involve a nasty hack.  Do you have any advice?

I don't have my head freshly wrapped around this, so take that into account, but off-hand I'd say that .group would be a collection responsibility, most naturally belonging to _Axes. Usually I've accomplished this sort of thing by an axis, in this case, keeping a reference to the collection it belongs to, generally named ._parent
This would require that all axes be constructed by an _Axes object. That might not be a bad idea anyway.
So the operation might look vaguely like this:
class _BaseAxis(...):
    @property
    def group(self):
        return self._parent.axis_group(self)

class _Axes(...):
    def axis_group(axis):
        # work out which group this axis belongs to here
        return _AxisGroup(...)

The protocol would be reminiscent of how list.index(item) works in Python.
What do you think?

Worked like a charm, thanks!  That's committed but breaks most of the axis tests since making an axis has a different signature now.  Should the tests be rewritten or should there be a default ._parent of None and error handling code around that?
To summarize, we now have Chart.axes, along with _BaseAxis.type, .orientation, and .group as well as _BaseAxis.orientation, since that's what's in the raw xml.

Hi Alex, sorry for the delay in responding, been a crazy week or so :)
In general, I'd say just update the tests using None for the parent parameter of the _BaseAxis() call or whatever, wherever that will work. I expect that will be most of them if not all.
If there are any that actually require the ._parent field, they'll need a suitable mock or perhaps a stub like a string or int, depending.
I haven't taken a look at them, but if you fix the ones where a None will get it done and still have any you need me to look at I'll be happy to. If you can send me a link to the right line(s) in the repo that will make it quick for me to review.
I've encountered this situation before as an object gets to the point where it needs to delegate something "upward" and it seems like almost of the tests just need a working constructor call and not an actual parent. Makes sense of course since none of the prior tests could have used a parent that wasn't there and usually that field is only used by the new method you're adding :)
Interestingly, the practice of using None wherever possible is actually good testing practice as it provides some measure of assurance the code is not depending on a value you're not expecting it to :)

Hi Steve, no worries!
None fixed all of the tests in the test_axis.py but there are a couple of failing tests in test_chart.py that I'm not sure how to deal with.
tests/chart/test_chart.py lines 34 and 45 are running CategoryAxis_.assert_called_once_with(catAx) and ValueAxis_.assert_called_once_with(valAx), respectively.  Here's the error that the Category Axis test fails:
E           AssertionError: Expected call: CategoryAxis(<Element {http://schemas.openxmlformats.org/drawingml/2006/chart}catAx at 0x7f88e5a2f8e8>)
E           Actual call: CategoryAxis(<Element {http://schemas.openxmlformats.org/drawingml/2006/chart}catAx at 0x7f88e5a2f8e8>, <pptx.chart.chart._Axes object at 0x7f88e5a46d50>)

The cat_ax_fixture starts on line 110 , but I'm not sure how to modify it to work properly.  I think like 112 is the problem.
The corresponding val_ax_fixture starts on line 205.

Ah, right, that makes sense.
So the first one you can fix by adding ', chart.axes' to line 34:
def it_provides_access_to_the_category_axis(self, cat_ax_fixture):
    chart, category_axis_, CategoryAxis_, catAx = cat_ax_fixture
    category_axis = chart.category_axis
    CategoryAxis_.assert_called_once_with(catAx, chart.axes)  ## <<< here
    assert category_axis is category_axis_

The same approach should fix the second test as well.
It points up an interesting question though, and that is whether the implementation of .category_axis and .value_axis are still appropriate when there is an _Axes object available.
I think before long we'll want an implementation more like this:
@property
def category_axis(self):
    """
    The first category axis of this chart. Raises |ValueError| if no
    category axes are defined.
    """
    try:
        return self.axes.list_by_type(MSO_AXIS_TYPE.CATEGORY)[0]
    except IndexError:
        raise ValueError('chart has no category axis')

but that can wait until after you get it working :)
Basically the idea being there shouldn't be more than one way to get the first category axis because it would represent duplication in the code. We would want the Axes object to be in charge of all axis getting and the .category_axis property of chart would delegate that job to its Axes object instead of handling it directly as it does today.
So we'll need to noodle a bit on what the broader API of Axes will be. The .list_by_type() method is just off the top of my head.
Anyway, we can get to all that in due time, step by step :)

Thanks to that snippet, the tests are all passing again.
Instead of .list_by_type(), we could simply change the code to something like this:
@property
def category_axis(self):
    """
    The first category axis of this chart. Raises |ValueError| if no
    category axes are defined.
    """
    try:
        return next((ax for ax in chart.axes if ax.type == 'category'))
    except IndexError:
        raise ValueError('chart has no category axis')

It's really a matter of how useful the .list_by_type would be, since that's just as easily implemented in Chart.axes.
What do you think should be next?

Oooh, that's an idea. I think the except IndexError would have to become except StopIteration, but I really like the idea. We could just change it to that and then worry about any .list_by_type() method later when and if we needed it for something else. :)

Changing the category and value axis methods (with except StopIteration, of course) causes failures in the same two tests.
tests/chart/test_chart.py:34:
[...]
E           AssertionError: Expected to be called once. Called 0 times.

I don't suppose you know how to rewrite those tests off the top of your head..?  :confused:

Well, they would need to be rewritten. They use mocks so changing the interaction used to get the result will need a different test. A mocked test tests the interaction rather than the final result.
First, it would take two tests, one for the success case and one for the error case.
For the success case you need to mock the Chart.axes property to return an Axes mock, then have the Axes mock return a type of CATEGORY and have its iter() method return the right axis object.
I know that's a little bit tricky probably if you're not used to working with the Python mock library :)
Also I think there will need to be some sort of AXIS_TYPE enumeration, we wouldn't want to use a raw XML attribute string value in there.
It would be perfectly fine to leave it the way it was (calling CategoryAxis() directly) for now and we can get it upgraded when we actually close in on a set of commits. I'll leave that up to you. I think if we can get it working that's probably the first priority for most folks. We can attend to the careful craftsmanship of it as a second step. We might need more of my attention for that, but the actual incorporation of these into the main branch always seems to take a lot of that one way or the other :)

Is the API for the second y axis avaiable now? I checked the chart and series source withtout clue.
Thanks.

Is this feature something that I can use? If so, is there anyway you could post an example of how to plot on the secondary axis or direct me to some documentation. Thank you!

No. This is a feature request. No one's working on it as far as I know. Looks like Alex made some progress on it a couple years ago. You can check out his fork, although it's 400-odd commits behind this master, so a lot of the latest features would be missing.

@scanny is there any work around to get two axis charts ? large part of our application depends upon python-pptx.i will be able to look into more detail of a permanent fix once i have some time off from work. Thanks

@anekix I don't know of any. There was some work done on this as you can see from the prior posts, so you might be able to pull from there. If your team has budget to devote to it you might consider sponsoring this feature.

Hi @scanny
I have a simple problem , i am trying to add a reference line on the head of a bar keeping my value axis line same. For example

I want to add that blue line on the top of my reference bar.

@aishwarya91 Please post support questions on StackOverflow, using the 'python-pptx' tag.

Hi
Have posted On StackOverflow.
Thanks

So, do you plan to implement it in the future ？


Allow authors to specify an HTML template

Not everyone will want the default template, with its JS-based navigation and
fancy header. Allow authors to customize this HTML template. To accomplish
this, move HTML template from server to config and generate it into the book.

Thanks for the suggestion and for the contribution. Unfortunately, I get an internal server error when trying to run a fresh book with the new template. Also, the test suite is red, at least on my system. Finally, you can already get a plain view of HTML output by opening any of the files in the html/ directory. You have to give up the auto-refresh, but is it really so terrible to have to live with the top menu? I'll consider implementing this if it comes with tests, a passing test suite, and a corresponding update to the manual, but otherwise I think it's too narrow a use-case given the effort required to integrate it with the main codebase.


Failing test

The following program sample.go triggers an unexpected result
Just clone the repo and run `go test ./...`.

Expected result
Running `go test ./...` passed.

Got
?   	github.com/traefik/yaegi	[no test files]
ok  	github.com/traefik/yaegi/cmd/yaegi	(cached)
ok  	github.com/traefik/yaegi/example/closure	0.009s
ok  	github.com/traefik/yaegi/example/fs	(cached)
ok  	github.com/traefik/yaegi/example/getfunc	0.010s
?   	github.com/traefik/yaegi/internal/cmd/extract	[no test files]
?   	github.com/traefik/yaegi/internal/cmd/genop	[no test files]
?   	github.com/traefik/yaegi/stdlib	[no test files]
?   	github.com/traefik/yaegi/stdlib/syscall	[no test files]
?   	github.com/traefik/yaegi/stdlib/unrestricted	[no test files]
?   	github.com/traefik/yaegi/stdlib/unsafe	[no test files]
ok  	github.com/traefik/yaegi/example/pkg	0.053s
ok  	github.com/traefik/yaegi/extract	0.031s
ok  	github.com/traefik/yaegi/internal/unsafe2	(cached)
--- FAIL: TestInterpConsistencyBuild (155.45s)
    --- FAIL: TestInterpConsistencyBuild/composite6.go (0.00s)
        interp_consistent_test.go:148: ../_test/composite6.go:6:2: import "github.com/traefik/yaegi/_test/ct1" error: unable to find source related to: "github.com/traefik/yaegi/_test/ct1"
    --- FAIL: TestInterpConsistencyBuild/d3.go (0.00s)
        interp_consistent_test.go:148: ../_test/d3.go:3:8: import "github.com/traefik/yaegi/_test/d2" error: unable to find source related to: "github.com/traefik/yaegi/_test/d2"
    --- FAIL: TestInterpConsistencyBuild/import3.go (0.00s)
        interp_consistent_test.go:148: ../_test/import3.go:3:8: import "github.com/traefik/yaegi/_test/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo"
    --- FAIL: TestInterpConsistencyBuild/import4.go (0.00s)
        interp_consistent_test.go:148: ../_test/import4.go:3:8: import "github.com/traefik/yaegi/_test/p1" error: unable to find source related to: "github.com/traefik/yaegi/_test/p1"
    --- FAIL: TestInterpConsistencyBuild/import5.go (0.00s)
        interp_consistent_test.go:148: ../_test/import5.go:3:8: import "github.com/traefik/yaegi/_test/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo"
    --- FAIL: TestInterpConsistencyBuild/import7.go (0.00s)
        interp_consistent_test.go:148: ../_test/import7.go:3:8: import "github.com/traefik/yaegi/_test/foo-bar" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo-bar"
    --- FAIL: TestInterpConsistencyBuild/import8.go (0.00s)
        interp_consistent_test.go:148: ../_test/import8.go:3:8: import "github.com/traefik/yaegi/_test/b1/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/b1/foo"
    --- FAIL: TestInterpConsistencyBuild/import9.go (0.00s)
        interp_consistent_test.go:148: ../_test/import9.go:3:8: import "github.com/traefik/yaegi/_test/baz-bat" error: unable to find source related to: "github.com/traefik/yaegi/_test/baz-bat"
    --- FAIL: TestInterpConsistencyBuild/issue-1355.go (0.00s)
        interp_consistent_test.go:148: ../_test/issue-1355.go:3:8: import "github.com/traefik/yaegi/_test/p2" error: unable to find source related to: "github.com/traefik/yaegi/_test/p2"
    --- FAIL: TestInterpConsistencyBuild/method38.go (0.00s)
        interp_consistent_test.go:148: ../_test/method38.go:6:2: import "github.com/traefik/yaegi/_test/method38" error: unable to find source related to: "github.com/traefik/yaegi/_test/method38"
    --- FAIL: TestInterpConsistencyBuild/named3.go (0.00s)
        interp_consistent_test.go:148: ../_test/named3.go:3:8: import "github.com/traefik/yaegi/_test/named3" error: unable to find source related to: "github.com/traefik/yaegi/_test/named3"
    --- FAIL: TestInterpConsistencyBuild/p5.go (0.00s)
        interp_consistent_test.go:148: ../_test/p5.go:3:8: import "github.com/traefik/yaegi/_test/p5" error: unable to find source related to: "github.com/traefik/yaegi/_test/p5"
    --- FAIL: TestInterpConsistencyBuild/p6.go (0.00s)
        interp_consistent_test.go:148: ../_test/p6.go:6:2: import "github.com/traefik/yaegi/_test/p6" error: unable to find source related to: "github.com/traefik/yaegi/_test/p6"
    --- FAIL: TestInterpConsistencyBuild/tag0.go (0.00s)
        interp_consistent_test.go:148: ../_test/tag0.go:6:8: import "github.com/traefik/yaegi/_test/ct" error: unable to find source related to: "github.com/traefik/yaegi/_test/ct"
    --- FAIL: TestInterpConsistencyBuild/var14.go (0.00s)
        interp_consistent_test.go:148: ../_test/var14.go:3:8: import "github.com/traefik/yaegi/_test/vars" error: unable to find source related to: "github.com/traefik/yaegi/_test/vars"
--- FAIL: TestInterpErrorConsistency (0.88s)
    --- FAIL: TestInterpErrorConsistency/import6.go (0.01s)
        interp_consistent_test.go:308: got "../_test/import6.go:3:8: import \"github.com/traefik/yaegi/_test/c1\" error: unable to find source related to: \"github.com/traefik/yaegi/_test/c1\"", want: "import cycle not allowed"
Hello
Hello bar
Hello baz
io: read/write on closed pipe
io: read/write on closed pipe
io: read/write on closed pipe
1:28: undefined: reflect
--- FAIL: TestNoGoFiles (0.00s)
    interp_eval_test.go:1723: failed to detect no Go files: 1:21: import "github.com/traefik/yaegi/_test/p3" error: unable to find source related to: "github.com/traefik/yaegi/_test/p3"
Hello
In Hi:
hello from Myint 4
--- FAIL: TestFile (3.75s)
    --- FAIL: TestFile/composite6.go (0.00s)
        interp_file_test.go:36: ../_test/composite6.go:6:2: import "github.com/traefik/yaegi/_test/ct1" error: unable to find source related to: "github.com/traefik/yaegi/_test/ct1"
    --- FAIL: TestFile/d3.go (0.00s)
        interp_file_test.go:36: ../_test/d3.go:3:8: import "github.com/traefik/yaegi/_test/d2" error: unable to find source related to: "github.com/traefik/yaegi/_test/d2"
    --- FAIL: TestFile/import3.go (0.00s)
        interp_file_test.go:36: ../_test/import3.go:3:8: import "github.com/traefik/yaegi/_test/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo"
    --- FAIL: TestFile/import4.go (0.00s)
        interp_file_test.go:36: ../_test/import4.go:3:8: import "github.com/traefik/yaegi/_test/p1" error: unable to find source related to: "github.com/traefik/yaegi/_test/p1"
    --- FAIL: TestFile/import5.go (0.00s)
        interp_file_test.go:36: ../_test/import5.go:3:8: import "github.com/traefik/yaegi/_test/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo"
    --- FAIL: TestFile/import6.go (0.00s)
        interp_file_test.go:36: got "../_test/import6.go:3:8: import \"github.com/traefik/yaegi/_test/c1\" error: unable to find source related to: \"github.com/traefik/yaegi/_test/c1\"", want: "import cycle not allowed\n\timports github.com/traefik/yaegi/_test/c1"
    --- FAIL: TestFile/import7.go (0.00s)
        interp_file_test.go:36: ../_test/import7.go:3:8: import "github.com/traefik/yaegi/_test/foo-bar" error: unable to find source related to: "github.com/traefik/yaegi/_test/foo-bar"
    --- FAIL: TestFile/import8.go (0.00s)
        interp_file_test.go:36: ../_test/import8.go:3:8: import "github.com/traefik/yaegi/_test/b1/foo" error: unable to find source related to: "github.com/traefik/yaegi/_test/b1/foo"
    --- FAIL: TestFile/import9.go (0.00s)
        interp_file_test.go:36: ../_test/import9.go:3:8: import "github.com/traefik/yaegi/_test/baz-bat" error: unable to find source related to: "github.com/traefik/yaegi/_test/baz-bat"
    --- FAIL: TestFile/issue-1355.go (0.00s)
        interp_file_test.go:36: ../_test/issue-1355.go:3:8: import "github.com/traefik/yaegi/_test/p2" error: unable to find source related to: "github.com/traefik/yaegi/_test/p2"
    --- FAIL: TestFile/method38.go (0.00s)
        interp_file_test.go:36: ../_test/method38.go:6:2: import "github.com/traefik/yaegi/_test/method38" error: unable to find source related to: "github.com/traefik/yaegi/_test/method38"
    --- FAIL: TestFile/method39.go (0.00s)
        interp_file_test.go:36: got "../_test/method39.go:7:2: import \"github.com/traefik/yaegi/_test/method38\" error: unable to find source related to: \"github.com/traefik/yaegi/_test/method38\"", want: "17:11: undefined selector Get"
    --- FAIL: TestFile/named3.go (0.00s)
        interp_file_test.go:36: ../_test/named3.go:3:8: import "github.com/traefik/yaegi/_test/named3" error: unable to find source related to: "github.com/traefik/yaegi/_test/named3"
    --- FAIL: TestFile/p5.go (0.00s)
        interp_file_test.go:36: ../_test/p5.go:3:8: import "github.com/traefik/yaegi/_test/p5" error: unable to find source related to: "github.com/traefik/yaegi/_test/p5"
    --- FAIL: TestFile/tag0.go (0.00s)
        interp_file_test.go:36: ../_test/tag0.go:6:8: import "github.com/traefik/yaegi/_test/ct" error: unable to find source related to: "github.com/traefik/yaegi/_test/ct"
    --- FAIL: TestFile/var14.go (0.00s)
        interp_file_test.go:36: ../_test/var14.go:3:8: import "github.com/traefik/yaegi/_test/vars" error: unable to find source related to: "github.com/traefik/yaegi/_test/vars"
FAIL
FAIL	github.com/traefik/yaegi/interp	176.933s
FAIL

Yaegi Version
0.15.0
Additional Notes
I'm trying to package yaegi for AlpineLinux, but my local build are failing (see the log above).
Also, it would be nice to have race optional when running test. AlpineLinux (and a few other distros) set -buildmode=pie that forbid -race flag.
https://github.com/traefik/yaegi/blob/da03c922cad7cfa07ece6fed917d01994e006be9/cmd/yaegi/yaegi_test.go#L54

I have tested under alpine-3.17.2 (aarch64) and go1.19.6 (alpinelinux package) and I have no errors.
I think the errors are not related to alpinelinux, but due to yaegi repo probably not installed at $GOPATH/src/github.com/traefik/yaegi, the old Go way which is still expected to pass all the tests, waiting for support of Go modules in yaegi.

I think the errors are not related to alpinelinux, but due to yaegi repo probably not installed at $GOPATH/src/github.com/traefik/yaegi, the old Go way which is still expected to pass all the tests, waiting for support of Go modules in yaegi.

Thanks for the explanation. I moved the cloned repo to the suggested path and the tests ran successfully. Would you consider adding this note into contributing / building from source guideline? That would be helpful. Then, this issue can be closed.
Also can you look into the -race flag in test as I mentioned. I don't want to keep a patch downstream forever with just 2 LOCs removed. A variable to disable race while running test would be nice.

I will update the readme to document the constraint on repo path.
I'm running on alpinelinux and can totally run go test -race ./...
You mention -buildmode=pie, but I do not see that in my setup. Where is it coming from ? What is the output of go env on your alpinelinux setup ?

I'm running on alpinelinux and can totally run go test -race ./...

Yes, nothing goes wrong when we run the command manually with default Go package in AlpineLinux.

You mention -buildmode=pie, but I do not see that in my setup

https://git.alpinelinux.org/abuild/tree/abuild.conf#n5
It is set in abuild configuration file (the program used to package AlpineLinux packages).
-race is enforced when running test based on the environment architecture. You can see the patch here: https://git.alpinelinux.org/aports/tree/testing/yaegi/remove-race-in-test.patch


Run request body is not editable when continuous deployment is configured

The "request body" field should be editable in the function app dashboard even when continuous deployment is configured. Currently everything in the UI becomes read-only when continuous deployment is enabled. The run request body field should remain editable so you can still edit the configuration for manually running the app using the UI

This bug is fixed in the dev branch, but has not been pushed to the portal. See https://github.com/projectkudu/AzureFunctionsPortal/issues/606.


publish<EMAIL_ADDRESS>

Requested by: @BYK
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] github
[ ] registry
[ ] gcs
[ ] docker[release]
[ ] docker[latest]

Gonna retry with https://github.com/getsentry/relay/pull/1033


Defensive check on sendRawTransaction response

TronWeb sometimes throws the below exception when triggering contracts.
Error: The passed value is not a valid hex string
It is raised because the sendRawTransaction response did not contain the message field.
E.g. { code: 'SERVER_BUSY' }
This block should contain a defensive check on the response broadcast
https://github.com/TRON-US/tronweb/blob/dcb8efa36a5ebb65c4dab3626e90256a453f3b0d/src/lib/contract/method.js#L211-L215

Thanks.
I am fixing this in https://github.com/TRON-US/tronweb/pull/21


Kingdom Builder board game

Hello,
I have implemented the Kingdom Builder board game from Queen Games (there a maybe reserved rights) in python3.
The repo is here: https://github.com/Counterfeiter/KingdomBuilder
I have written this game with the goal to train an alpha zero agent to create a really powerful player, but I failed. =(
I would like to ask smarter guys then me, to build a advanced player. So I could learn why I failed that bad...
The game:

non deterministic (random terrain cards)
some hidden information (terrain cards of opponents)
multiplayer (2 - 5 players)
hexagon grid board (20x20) (complex CNN)
board could be build with 2 * 8 * 4 = 48 different combinations
random rule cards for each new game - changes strategy drastically
there is a immediately "gold" reward per move, but following this reward will miss the long term strategy and in fact this "nice feature" is useless

History of my tries:
I have forked a multiplayer alpha zero implementation for the agent and made a complete code mess with my tries (sorry for that): https://github.com/Counterfeiter/multiplayer-alphazero/tree/AddKB
I have changed the implementation a lot to fit my needs:

allow hidden information (states) to be saved and transferred to the stateless game class
add a modified version of rays rllib MCTS with recursive traversing because the original MCTS implementation made a memory and cpu mess, because of my new game interface
rework the multiplayer value loss function: The loss is only calculated over players current in the game. My hope was that one agent could play strong with different numbers of opponents. I think mathematically there should be no problem and this would be a nice "investigation"
rework the overall loss function to weight the value head more then the policy head - because the 4802 logits large policy head has never learned anything
add chance nodes for the terrain cards
rework observation variable to bypass the CNN and add some extra information to the CNN following FF directly (save some CNN layers) - add some models for this tests
rework the CNN hexgon interpretation so that each node in each row has the same neighbors
add tensorboard support for some training data parameters

I have trained only on my nvidia laptop GPU (GTX 1660 TI). Could be the missing processing power the bottleneck?
Would be great to get some assessments for more advance people.
I know this topic is not a real issue, but if there is no copy right issue this game would be a really good learning environment. Also this games makes a lot of fun to play :)
Thanks
Sebastian

@Counterfeiter: apologies that we were not able to addressed this, but I was happy to see more interest in Eurogames!