need to update command on how to run coverage and fix directory path where riscof looks for elf

moving issue from https://github.com/riscv-software-src/riscv-config/issues/135
https://riscof.readthedocs.io/en/stable/coverage.html
The current directions say to run coverage:
riscof --verbose debug coverage --suite /path/to/suite --env /path/to/suite
this will generate an error. -c or --cgf_file is a required option.
However, even if -cgf_file is used, there is another error. riscof looks for the elf file in the wrong directory:
FileNotFoundError: [Errno 2] No such file or directory: '/riscof/riscof_work/rv32i_m/C/src/caddi-01.S/ref.elf'
but it looks like it should instead be looking in:
./rv32i_m/I/src/addi-01.S/ref/ref.elf
Thanks
I don't think the paths are wrong. Both would probably point to the same thing. All paths are resolved to be absolute paths before the actual execution of riscof starts. The former simply looks like the absolute path of the latter. I think the compilation was not successful. Can you share the entire log?
@dansmathers its better to move/track this issue in the riscof repo since it doesn't have anything to do with riscv-config.

riscof coverage  --config=config.ini --suite=riscv-arch-test/riscv-test-suite/ --env=riscv-arch-test/riscv-test-suite/env --cgf-file /riscof/riscv-arch-test/coverage/rvi_c.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_fencei.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_m.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_priv.cgf | tee cov.log
INFO | ****** RISCOF: RISC-V Architectural Test Framework 1.25.3 *******
INFO | using riscv_isac version : 0.17.0
INFO | using riscv_config version : 3.9.1
INFO | Reading configuration from: /riscof/config.ini
INFO | Preparing Models
INFO | Input-ISA file
INFO | Loading input file: /riscof/spike/spike_isa.yaml
INFO | Load Schema /.local/lib/python3.8/site-packages/riscv_config/schemas/schema_isa.yaml
INFO | Processing Hart: hart0
INFO | Initiating Validation
INFO | No errors for Hart: 0 :)
INFO |  Updating fields node for each CSR
INFO | Dumping out Normalized Checked YAML: /riscof/riscof_work/spike_isa_checked.yaml
INFO | Input-Platform file
INFO | Loading input file: /riscof/spike/spike_platform.yaml
INFO | Load Schema /.local/lib/python3.8/site-packages/riscv_config/schemas/schema_platform.yaml
INFO | Initiating Validation
INFO | No Syntax errors in Input Platform Yaml. :)
INFO | Dumping out Normalized Checked YAML: /riscof/riscof_work/spike_platform_checked.yaml
INFO | Generating database for suite: /riscof/riscv-arch-test-20230726/riscv-test-suite
INFO | Database File Generated: /riscof/riscof_work/database.yaml
INFO | Env path set to/riscof/riscv-arch-test-20230726/riscv-test-suite/env
INFO | Will collect Coverage using RISCV-ISAC
INFO | CGF file(s) being used : ('/riscof/riscv-arch-test-20230726/coverage/rvi_c.cgf', '/riscof/riscv-arch-test-20230726/coverage/rvi.cgf', '/riscof/riscv-arch-test-20230726/coverage/rvi_fencei.cgf', '/riscof/riscv-arch-test-20230726/coverage/rvi_m.cgf', '/riscof/riscv-arch-test-20230726/coverage/rvi_priv.cgf')
INFO | Selecting Tests.
INFO | Running Tests on Reference.
ERROR |     INFO | ****** RISC-V ISA Coverage 0.17.0 *******
INFO | Copyright (c) 2020, InCore Semiconductors Pvt. Ltd.
INFO | All Rights Reserved.
Traceback (most recent call last):
File "/.local/bin/riscv_isac", line 8, in
sys.exit(cli())
File "/.local/lib/python3.8/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/.local/lib/python3.8/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
File "/.local/lib/python3.8/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/.local/lib/python3.8/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/.local/lib/python3.8/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/.local/lib/python3.8/site-packages/riscv_isac/main.py", line 136, in coverage
isac(output_file,elf,trace_file, window_size, expand_cgf(cgf_file,int(xlen),int(flen),log_redundant), parser_name, decoder_name, parser_path, decoder_path, detailed, test_label,
File "/.local/lib/python3.8/site-packages/riscv_isac/cgf_normalize.py", line 565, in expand_cgf
cgf = utils.load_cgf(cgf_files)
File "/.local/lib/python3.8/site-packages/riscv_isac/utils.py", line 163, in load_cgf
safe_yaml.dump(dict(safe_yaml.load(fp)),string_stream)
File "/.local/lib/python3.8/site-packages/ruamel/yaml/main.py", line 426, in load
return constructor.get_single_data()
File "/.local/lib/python3.8/site-packages/ruamel/yaml/constructor.py", line 111, in get_single_data
node = self.composer.get_single_node()
File "_ruamel_yaml.pyx", line 706, in _ruamel_yaml.CParser.get_single_node
File "_ruamel_yaml.pyx", line 724, in _ruamel_yaml.CParser._compose_document
File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
File "_ruamel_yaml.pyx", line 775, in _ruamel_yaml.CParser._compose_node
File "_ruamel_yaml.pyx", line 889, in _ruamel_yaml.CParser._compose_mapping_node
File "_ruamel_yaml.pyx", line 743, in _ruamel_yaml.CParser._compose_node
ruamel.yaml.composer.ComposerError: found undefined alias
in "", line 15, column 11
make: *** [/riscof/riscof_work/Makefile.Reference-sail_c_simulator:5: TARGET0] Error 1
INFO | Merging Coverage reports
Traceback (most recent call last):
File "/.local/bin/riscof", line 8, in
sys.exit(cli())
File "/.local/lib/python3.8/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/.local/lib/python3.8/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
File "/.local/lib/python3.8/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/.local/lib/python3.8/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/.local/lib/python3.8/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/.local/lib/python3.8/site-packages/click/decorators.py", line 33, in new_func
return f(get_current_context(), *args, **kwargs)
File "/.local/lib/python3.8/site-packages/riscof/cli.py", line 399, in coverage
report, for_html, test_stats, coverpoints = framework.run_coverage(base, isa_file, platform_file,
File "/.local/lib/python3.8/site-packages/riscof/framework/main.py", line 126, in run_coverage
'test_size': [str(entry) for entry in find_elf_size(elf)],
File "/.local/lib/python3.8/site-packages/riscof/framework/main.py", line 59, in find_elf_size
with open(elf, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/riscof/riscof_work/rv32i_m/C/src/cadd-01.S/ref/ref.elf'

@pawks Can you share your command you use to run coverage and I will try that?  I was guessing at the correct command because I didn't see a quickstart command that I could just run correctly?
Thanks,
Dan

The error you are seeing is because you didnt include the dataset.cgf in the command line. It should be the first file in the list of cgf file arguments. The correct command should look something like the following:
riscof coverage --config=config.ini --suite=riscv-arch-test/riscv-test-suite/ --env=riscv-arch-test/riscv-test-suite/env --cgf-file /riscof/riscv-arch-test/dataset.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_c.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_fencei.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_m.cgf --cgf-file /riscof/riscv-arch-test/coverage/rvi_priv.cgf

@dansmathers as we noted in the last SIG call.. the docs for "test contributors" is missing and we will be fixing that asap in the coming weeks. It would be great if you could list out the missing docs you encountered in your struggle so we can accurately address those and others together.
Thanks for the inputs.

Thanks.  that command helped.   I still see errors going by for some tests but the script ran.   I was trying to build everything from scratch again to check but it looks like the current github sail build is currently broken.   It does seem like it might be hard to do large unified pulls because there are 4 or 5 githubs that need to be kept in sync?


Fix archival handled requests not match pumped requests

What changed?
Use json instead of gob when hashing archival requests

Why?
gob is non-deterministic when encoding map objects

How did you test it?
Unit test

Potential risks
No, this fixes a sanity check itself.

Coverage increased (+0.08%) to 67.086% when pulling<PHONE_NUMBER>0bad486585f5d16118005a147246a9 on yycptt:fix-pump-not-equal-handled into 3973b054c3fd92476343b957398e1bad7e43a560 on uber:master.

It looks like gob non-deterministic encoding issue was fixed at 2012 https://github.com/golang/go/issues/3026, If there is still such issue we probably can submit an issue to them

It looks like gob non-deterministic encoding issue was fixed at 2012 golang/go#3026, If there is still such issue we probably can submit an issue to them

I am aware of the issue you linked. However if I understand that issue correctly, it's talking about decoding not encoding. The encoding for map is still non-deterministic. https://stackoverflow.com/a/50733233


Switch claim reconcilers from HasDirectClassReferenceKind to IsManagedKind predicate

What happened?

HasDirectClassReferenceKind does not support static provisioning. crossplane-runtime has been updated with a fix, but this stack must be updated. See https://github.com/crossplaneio/crossplane-runtime/issues/28 for details.

https://github.com/crossplaneio/crossplane-runtime/issues/33


Exposure system notification logic

Issue
It opens now a test EN screen
Expected
Exposures screen?

closed in #73


Update requirements.txt to include all mandatory pre-requisites

Attempt to deploy streamlit and if requirements file needs updating it will flag up in there.

Note: Speak to Nick as Admin rights needed to deploy app to Streamlit.

Reviewed and merged


[Title] Bug Template

Found:
Repro Steps:

First
Second
etc...

Actual Result:
Expected Result:
Attach Image or Video with issues highlighted

(Location) Issues has been fixed on pull #8, in (scene name), at (where in the scene).
(State the new state or behavior to the fix) Whatever is currently behaving in this new way. Or, object was a square now is a circle.
[No need prof unless really necessary]


What does the +m option do?

Category

[x] fzf binary

What does the +m option to fzf do? Can't seem to find it in the man page, but it's used in many examples.

It's the opposite of -m (a.k.a. --multi), so it explicitly disables --multi. --multi is not enabled by default, but we do this because users may have it in their $FZF_DEFAULT_OPTS. Likewise, +i is the opposite of -i, +s is the opposite of -s. And you're right that +m is currently missing in the man page.
Another things that is not clearly stated is that most options have their --no-* counterpart. --no-multi, --no-sort, --no-reverse, --no-height, etc. I'll update the man page.


Cut 0.14.0.

:+1: besides nit

Perhaps we should release client_golang first, so that we can set the Godeps to a release tag.
I expect that helps Tincho et al. creating distribution packages.

@beorn7 Hmm, do we know how important that is really? We do want to get 0.14.0 out there, especially in light of the conference talk tomorrow.

It should be a matter of minutes...
Not sure how important it is, because Tincho might just work with commit
id's anyway.
On Mon, Jun 1, 2015 at 6:51 PM, Julius Volz<EMAIL_ADDRESS>wrote:

@beorn7 https://github.com/beorn7 Hmm, do we know how important that is
really? We do want to get 0.14.0 out there, especially in light of the
conference talk tomorrow.
—
Reply to this email directly or view it on GitHub
https://github.com/prometheus/prometheus/pull/759#issuecomment-107634619
.

--
Björn Rabenstein, Engineer
http://soundcloud.com/brabenstein
SoundCloud Ltd. | Rheinsberger Str. 76/77, 10115 Berlin, Germany
Managing Director: Alexander Ljung | Incorporated in England & Wales with
Company No. 6343600 | Local Branch Office | AG Charlottenburg  | HRB 110657B


Optimize regexp matcher with list of alternations ending with .*

While investigating some query performance issues in production, I noticed that the set of very slow queries all had non-optimized regexp matchers in the format (?i)(a.*|b.*|c.*) (with many more alternations following the same pattern). In this PR I propose to optimize for such case too.
The proposed change is intentionally pretty small, in order to make it easier to review and reduce risks.
Analyzing the customer queries, here the difference in the number of optimized customer queries (out of 72018 queries analyzed):

Before: 71.21%
After: 99.39%

What the benchmark says (the 2nd last entry is the customer regexp). I've omitted memory comparison because there's no difference:
goos: darwin
goarch: amd64
pkg: github.com/prometheus/prometheus/model/labels
cpu: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
                                                     │  before.txt   │              after.txt              │
                                                     │    sec/op     │   sec/op     vs base                │
FastRegexMatcher/#00-12                                  61.81n ± 4%   62.21n ± 2%        ~ (p=0.896 n=10)
FastRegexMatcher/foo-12                                  76.14n ± 4%   74.79n ± 7%        ~ (p=0.143 n=10)
FastRegexMatcher/^foo-12                                 61.77n ± 3%   61.07n ± 2%        ~ (p=0.436 n=10)
FastRegexMatcher/(foo|bar)-12                            66.71n ± 3%   64.46n ± 3%   -3.38% (p=0.011 n=10)
FastRegexMatcher/foo.*-12                                147.6n ± 2%   139.2n ± 3%   -5.63% (p=0.000 n=10)
FastRegexMatcher/.*foo-12                                169.2n ± 3%   173.7n ± 3%        ~ (p=0.085 n=10)
FastRegexMatcher/^.*foo$-12                              170.4n ± 3%   173.6n ± 3%        ~ (p=0.138 n=10)
FastRegexMatcher/^.+foo$-12                              168.0n ± 5%   171.2n ± 3%        ~ (p=0.184 n=10)
FastRegexMatcher/.*-12                                   131.3n ± 5%   127.0n ± 3%        ~ (p=0.089 n=10)
FastRegexMatcher/.+-12                                   127.3n ± 5%   127.0n ± 5%        ~ (p=0.224 n=10)
FastRegexMatcher/foo.+-12                                148.4n ± 3%   139.2n ± 5%   -6.23% (p=0.000 n=10)
FastRegexMatcher/.+foo-12                                166.6n ± 3%   168.4n ± 2%        ~ (p=0.493 n=10)
FastRegexMatcher/foo_.+-12                               134.9n ± 5%   133.1n ± 4%        ~ (p=0.383 n=10)
FastRegexMatcher/foo_.*-12                               134.8n ± 4%   137.8n ± 4%        ~ (p=0.393 n=10)
FastRegexMatcher/.*foo.*-12                              280.9n ± 4%   284.3n ± 4%        ~ (p=0.325 n=10)
FastRegexMatcher/.+foo.+-12                              293.9n ± 4%   295.2n ± 3%        ~ (p=0.871 n=10)
FastRegexMatcher/(?s:.*)-12                              58.61n ± 5%   58.98n ± 3%        ~ (p=0.565 n=10)
FastRegexMatcher/(?s:.+)-12                              73.86n ± 6%   71.20n ± 3%   -3.59% (p=0.000 n=10)
FastRegexMatcher/(?s:^.*foo$)-12                         168.6n ± 3%   162.2n ± 5%        ~ (p=0.101 n=10)
FastRegexMatcher/(?i:foo)-12                             112.7n ± 3%   113.4n ± 5%        ~ (p=0.725 n=10)
FastRegexMatcher/(?i:(foo|bar))-12                       240.4n ± 8%   243.8n ± 4%        ~ (p=0.739 n=10)
FastRegexMatcher/(?i:(foo1|foo2|bar))-12                 426.8n ± 6%   418.3n ± 6%   -1.99% (p=0.043 n=10)
FastRegexMatcher/^(?i:foo|oo)|(bar)$-12                  1.062µ ± 4%   1.054µ ± 5%        ~ (p=0.684 n=10)
FastRegexMatcher/(?i:(foo1|foo2|aaa|bbb|ccc|ddd|e-12     1.889µ ± 1%   1.910µ ± 1%   +1.11% (p=0.000 n=10)
FastRegexMatcher/((.*)(bar|b|buzz)(.+)|foo)$-12          688.4n ± 4%   667.9n ± 3%        ~ (p=0.075 n=10)
FastRegexMatcher/^$-12                                   63.50n ± 4%   64.28n ± 3%        ~ (p=0.565 n=10)
FastRegexMatcher/(prometheus|api_prom)_api_v1_.+-12      226.9n ± 3%   230.1n ± 6%        ~ (p=0.247 n=10)
FastRegexMatcher/10\.0\.(1|2)\.+-12                      134.8n ± 4%   136.1n ± 3%        ~ (p=0.698 n=10)
FastRegexMatcher/10\.0\.(1|2).+-12                       136.7n ± 3%   134.2n ± 2%        ~ (p=0.148 n=10)
FastRegexMatcher/((fo(bar))|.+foo)-12                    311.3n ± 7%   284.2n ± 4%   -8.69% (p=0.000 n=10)
FastRegexMatcher/zQPbMkNO|NNSPdvMi|iWuuSoAl|qbvKM-12     289.5n ± 5%   296.2n ± 4%        ~ (p=0.515 n=10)
FastRegexMatcher/jyyfj00j0061|jyyfj00j0062|jyyfj9-12     314.2n ± 6%   315.5n ± 3%        ~ (p=0.796 n=10)
FastRegexMatcher/(?i:(zQPbMkNO|NNSPdvMi|iWuuSoAl|-12     1.898µ ± 1%   1.909µ ± 1%   +0.55% (p=0.006 n=10)
FastRegexMatcher/(?i:(zQPbMkNO.*|NNSPdvMi.*|iWuuS-12    46.267µ ± 4%   9.513µ ± 4%  -79.44% (p=0.000 n=10)
FastRegexMatcher/(?i:(.*zQPbMkNO|.*NNSPdvMi|.*iWu-12   1549.88µ ± 5%   11.38µ ± 5%  -99.27% (p=0.000 n=10)
geomean                                                  286.7n        236.4n       -17.53%

I've also run the fuzzy tests for a while:
$ go test -run '^$' -fuzz 'FuzzFastRegexMatcher_WithStaticallyDefinedRegularExpressions' ./model/labels

fuzz: elapsed: 0s, gathering baseline coverage: 0/312 completedfuzz: elapsed: 1s, gathering baseline coverage: 312/312 completed, now fuzzing with 12 workers
fuzz: elapsed: 3s, execs: 23161 (7719/sec), new interesting: 9 (total: 321)
fuzz: elapsed: 6s, execs: 48026 (8288/sec), new interesting: 11 (total: 323)
fuzz: elapsed: 9s, execs: 71033 (7668/sec), new interesting: 15 (total: 327)
...
fuzz: elapsed: 5m39s, execs: 2648543 (13497/sec), new interesting: 85 (total: 397)

$ go test -run '^$' -fuzz 'FuzzFastRegexMatcher_WithFuzzyRegularExpressions' ./model/labels

fuzz: elapsed: 1s, gathering baseline coverage: 0/3156 completed
fuzz: elapsed: 4s, gathering baseline coverage: 1269/3156 completed
fuzz: elapsed: 7s, gathering baseline coverage: 2580/3156 completed
fuzz: elapsed: 8s, gathering baseline coverage: 3156/3156 completed, now fuzzing with 12 workers
fuzz: elapsed: 10s, execs: 20376 (5940/sec), new interesting: 3 (total: 3159)
fuzz: elapsed: 13s, execs: 49398 (9675/sec), new interesting: 10 (total: 3166)
fuzz: elapsed: 16s, execs: 50765 (456/sec), new interesting: 11 (total: 3167)
...
fuzz: elapsed: 2m52s, execs: 367428 (5230/sec), new interesting: 54 (total: 3210)

LGTM. This took me a while to get my head around this.

This stuff is very tricky 🤞


fix: cleanup ddev-webserver bashrc variables, fixes #5409

The Issue
As described in #5409, this PR fixes this issue
Manual Testing Instructions
See #5409 - steps to reproduce to verify this PR
Related Issue Link(s)
#5409

Updated the actual image and rebased.

@benwalch please use the artifacts in https://github.com/ddev/ddev/actions/runs/6469106799 to test that you got what you wanted out of this. Info on testing techniques at https://ddev.readthedocs.io/en/latest/developers/building-contributing/#testing-a-pr


Missing DialogStateOut.supplemental_display_text

I'm always get audio-out response, but supplemental_display_text I get sometimes.
Any idea?

It may depend on the query, as the display text may not be provided always, as it's supplemental.


Update Ruby names and discovery docs

Hmm... will this discovery doc update now break other languages?

Current coverage is 81.10% (diff: 100%)

Merging #611 into master will not change coverage

@@             master       #611   diff @@
==========================================
  Files           267        267
  Lines         10017      10017
  Methods           0          0
  Messages          0          0
  Branches       1308       1308
==========================================
  Hits           8124       8124
  Misses         1558       1558
  Partials        335        335

Powered by Codecov. Last update c2bd314...303046f

It might break the baseline tests, though it shouldn't of itself break compilecheck in production. It looks like @tcoffee-google ran the baseline tests and updated as needed, so IIUC, this should work.
LGTM

Yes, the baselines have been updated.

Note this will not resolve Ruby compile check issues until https://github.com/google/google-api-ruby-client/pull/482 is submitted, assuming no discovery docs have been updated in the meantime.


[flagd-provider] FlagdProvider constructor which takes only Uri will throw object null reference

FlagdProvider(Uri url) does not initialize _config object hence using this constructor will leave _config null and throw exception.

Yes, this definitely seems to be the case.
We should fix this, add a test, and also reduce the duplication across the constructors, if possible.

Fixed with release: https://github.com/open-feature/dotnet-sdk-contrib/pull/85


add armstrong outputs to gitignore

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

/azp run


[CI] disable microshift TEKTON check for now

by this PR disable microshift TEKTON check for now

merge as it is.


Errors don't dessapear after fix

Issue Type: Bug
In some moment ide show a lot of totaly random errors that don't want to dissapear at all (i have no resharper)
Extension version: 1.23.9
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.91GB (3.21GB free)

Process Argv
--crash-reporter-id 8423cd46-ba26-4088-9144-3a920a61ac63

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475

I think it's one of those weird behaviors (#4404) that happens a lot for almost everyone.

A lot has changed with O# code analysis since this issue was opened. If you are still having problems, please open a new issue at https://github.com/omnisharp/omnisharp-roslyn/issues


Source update for <IP_ADDRESS>2

would it be possible to sync this repo with the latest changes from version <IP_ADDRESS>2?

Yes, please?

Ping!

ping!

That'd be <IP_ADDRESS>8 by now 😄

Anyone?

@KrisBash
@microsoftopensource
@blakedrumm
@khusmeno-MS
@x-limitless-x
@mcoskuntr

Please, someone at @microsoft raise this project and its issues at the appropriate positions.


Sept 29- World Heart Day

Did you know that climate change is threatening public health — especially in Africa’s most vulnerable communities?
As temperatures rise and air pollution worsens, it’s not just the planet that suffers — it’s our people. In Africa, women, children, and the elderly are often hit hardest by these challenges. From heatwaves to droughts, from polluted air to food insecurity, climate change deepens poverty and makes it even harder for families to stay healthy.
On this World Heart Day, let’s remember that protecting the planet also means protecting our hearts and our communities. Poor families, already struggling to survive, face the double burden of health issues linked to a warming climate. Children suffer from asthma due to pollution. The elderly, who are already vulnerable, are at greater risk from heat-related illnesses. And women, who are often caregivers, bear the emotional and physical toll of supporting their families in a rapidly changing environment.
We cannot turn a blind eye. Together, we must act now to build a healthier, greener future where everyone can thrive — regardless of their circumstances.
💚 A healthy planet means healthier people. Let’s fight for both.
#WorldHeartDay #ClimateAndHealth #HealthyPlanetHealthyPeople #ClimateJustice #FightForOurFuture
Cc @clentafrica/wg-marketing-comms @clentafrica/wg-design

@clentafrica/wg-design please start working on this design. Thank you🙏🏾

Did you know that climate change is threatening public health — especially in Africa’s most vulnerable communities?
As temperatures rise and air pollution worsens, it’s not just the planet that suffers — it’s our people. In Africa, women, children, and the elderly are often hit hardest by these challenges. From heatwaves to droughts, from polluted air to food insecurity, climate change deepens poverty and makes it even harder for families to stay healthy.
On this World Heart Day, let’s remember that protecting the planet also means protecting our hearts and our communities. Poor families, already struggling to survive, face the double burden of health issues linked to a warming climate. Children suffer from asthma due to pollution. The elderly, who are already vulnerable, are at greater risk from heat-related illnesses. And women, who are often caregivers, bear the emotional and physical toll of supporting their families in a rapidly changing environment.
We cannot turn a blind eye. Together, we must act now to build a healthier, greener future where everyone can thrive — regardless of their circumstances.
💚 A healthy planet means healthier people. Let’s fight for both.
#WorldHeartDay #ClimateAndHealth #HealthyPlanetHealthyPeople #ClimateJustice #FightForOurFuture
Cc @clentafrica/wg-marketing-comms @clentafrica/wg-design

@yigakpoa nice one

Awaiting on the design. Thank you

Hello. I am a new member and do not know how to operate github. Can you
please brief me as to what I have to work on. Sorry, it is confusing.
Thanks!
On Fri, 27 Sep 2024 at 4:41 PM, SDauphin15 @.***> wrote:

Awaiting on the design. Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/clentafrica/marketing-and-comms/issues/51#issuecomment-2379032204,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLHC3W2JFS4QPNY54QOS243ZYU4PJAVCNFSM6AAAAABN2EFBUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZZGAZTEMRQGQ
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

@erioc @SDauphin15 @yigakpoa  , sending the design below:

Thank you @breno02lucas . Nice Design!
@Okpeelizabeth1989 or @yigakpoa  please post on IG&FB . @erioc please post on twitter. I scheduled the post on LinkedIn. It’s due tomorrow 09/29

Done for FB, IG & Twitter


Kea: Support DHCP Vendor Option codes

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X ] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
Kea is missing Vendor option codes which are used for various network devices such as Unifi devices to discover controllers or SIP phones to discover servers etc.
Describe the solution you like
Expose the Option codes in the GUI, Kea should already support them.
Describe alternatives you considered
Go back to the old DHCP server
Additional context
None

duplicate https://github.com/opnsense/core/issues/7550

Probably better to link to https://github.com/opnsense/core/pull/7361
I searched open issues but not PRs, issues should probably not be closed till the linked / related PR is merged .

The feature request was already a duplicate of the PR. It would be nice if people trusted us running the bug tracker here in an efficient and useful way for the project. 😉


Bumped py-synology to 0.3.0 and added support for turning on and off.

Description:
I noticed two services did not work with the synology components, physically turn a camera on and off - pushed the code to the py-synology and services. The py-synology needs to be 0.3.0 to use the new services.
Related issue (if applicable): fixes #
Fixes the component not supporting on/off camera
Checklist:

[x ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.

Hi @alekslyse,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

You'll also need to run script/gen_requirements_all.py to generate a new REQUIREMENTS_ALL.txt file and include that in the PR 👍

You'll also need to run script/gen_requirements_all.py to generate a new REQUIREMENTS_ALL.txt file and include that in the PR 👍

I think I did it correctly now. Sorry first time :)

Also added enable / disable home mode due to request


Update build configuration

The build configuration of this project is outdated and may no longer work.
This pull request will be merged automatically if there are no conflicts.

:tada: This PR is included in version 3.0.11 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


mec15xxevb_assy6853: tests/drivers/adc/adc_api asynchronous test failed

Describe the bug
mec15xxevb_assy6853 board daily test tests/drivers/adc/adc_api asynchronous test failed
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? mec15xxevb_assy6853
What have you tried to diagnose or workaround this issue? Found a WA.
Is this a regression? No, this problem is randomly happen.

To Reproduce
Steps to reproduce the behavior:

west build -p always -b mec15xxevb_assy6853 tests/drivers/adc/adc_api/

Expected behavior
The test can pass
Impact
1 test case fail in daily test.
Some times the ADC will lost a sample.
Logs and console output
Original log
*** Booting Zephyr OS build zephyr-v3.1.0-4237-g6c03cb9fb433  ***
Running TESTSUITE adc_basic
===================================================================
START - test_adc_asynchronous_call
Samples read: 0x0af3 0x0af4 0x0af3 0x0af4 0xffff8000
    Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/adc/adc_api/src/test_adc.c:447: check_samples: (INVALID_ADC_VALUE equal to sample_value)
[4] should be filled
 FAIL - test_adc_asynchronous_call in 0.021 seconds

Add some printk
            568:@@@ test_task_asynchronous_call
            570:adc_xec_read_async
            573:@@@ adc_read_async done
            575:xec_adc_get_sample:v channels = 16, bit = 5
            578:xec_adc_get_sample: *data->buffer = 2803
            582:adc_context_on_sampling_done
            584:@@@ ctx->sampling_index = 0
            587:@@@ adc_context_start_sampling
            589:z_impl_k_poll
            591:xec_adc_get_sample:v channels = 16, bit = 5
            595:xec_adc_get_sample: *data->buffer = 2803
            598:adc_context_on_sampling_done
            600:@@@ ctx->sampling_index = 1
            603:@@@ adc_context_start_sampling
            605:poll: z_pend_curr before
            608:xec_adc_get_sample:v channels = 16, bit = 5
            612:xec_adc_get_sample: *data->buffer = 2803
            615:adc_context_on_sampling_done
            617:@@@ ctx->sampling_index = 2
            620:@@@ adc_context_start_sampling
            624:xec_adc_get_sample:v channels = 16, bit = 5
            627:xec_adc_get_sample: *data->buffer = 2803
            631:adc_context_on_sampling_done
            633:@@@ ctx->sampling_index = 3
            636:@@@ adc_context_start_sampling
            646:xec_adc_get_sample:v channels = 0, bit = 0     //channels should be 16 here.
            650:adc_context_on_sampling_done
            652:@@@ ctx->sampling_index = 4
            655:@@@ finish = true
            656:@@@ k_poll_signal_raise
            659:z_impl_k_poll_signal_raise
            662:poll: z_pend_curr after
            664:@@@ k_poll done
            666:check_samples: 2803 2803 2803 2803 -32768
           6629:

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows): Ubuntu 20.04
Toolchain (e.g Zephyr SDK, ...) 0.15.0
Commit SHA or Version used: 6c03cb9fb4334e67735b9ae138fe2704a348e4ce

Additional context
The test will collect 5 samples of the ADC.
In the last sample, the interrupt is triggered, but the register shows there is no channel that have the ADC data.
If there is there is no ADC channel ready, there should not be an interrupt.
But in this case, I think the interrupt is correct, the problem is the adc_regs->status_reg not correct. If manually set the channel of last sample to 16, the case can pass correctly. So we need to analyze why this value is 0.
the WA

In the test test_task_asynchronous_call(), change k_poll(&async_evt, 1, K_MSEC(1000)) to k_poll(&async_evt, 1, K_MSEC(500)), this problem will not happen.
If change the timer to 2000ms, the problem will 100% happen.
if the adc_regs->status_reg is 0, set the the value of it to the value of the last sample.

Close as the bug is unable to reproduce for some days


Add download data for November 2020 to March 2021

The Circe organization had 4,679,855 downloads for March, which is an all-time high, up 9.2% from February, 19% from December, and 6% from the previous high last October. Unique IPs showed even more growth, with March at 166,165, up 31.8% from last October's 126,066.
The Typelevel organization's download count was similarly up 11% from February to March (to 11,346,769, also a record).
Most growth is from Scala 2.13, with circe-core_2.13 downloads up 30% from January to March. Scala 2.12 is still increasing in absolute numbers, but slowly (March up 12% from January). Scala 2.12 is still far ahead of 2.13 (64% more downloads in March), but 2.13 seems to be on track to pass 2.12 this year.
Scala 2.11 downloads finally started decreasing in absolute numbers in February, with March downloads for circe-core_2.11 down 44% from January. Scala 2.10 has been fairly stable with both circe-core_2.10 and cats-core_2.11 in the mid-1,000s since last summer and will probably never die.
(Reminder: these numbers are for Maven Central only and don't directly reflect adoption, since many organizations use internal mirrors. This data is useful mostly as a way of tracking changes in adoption over time, or in comparing adoption across Scala versions, although even in those cases comparisons shouldn't be considered precise in any way.)

Codecov Report

Merging #1721 (80b8a0f) into master (a776345) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1721      +/-   ##
==========================================
- Coverage   86.99%   86.98%   -0.02%
==========================================
  Files          59       58       -1
  Lines        2392     2382      -10
  Branches      142      142
==========================================
- Hits         2081     2072       -9
+ Misses        311      310       -1

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/MapDecoder.scala
88.00% <0.00%> (-8.00%)
:arrow_down:

...core/shared/src/main/scala/io/circe/CursorOp.scala
54.16% <0.00%> (-1.39%)
:arrow_down:

...es/core/shared/src/main/scala/io/circe/Error.scala
62.06% <0.00%> (-0.44%)
:arrow_down:

...nter/src/main/scala/io/circe/pointer/Pointer.scala
89.34% <0.00%> (-0.13%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.82% <0.00%> (-0.04%)
:arrow_down:

...in/scala/io/circe/pointer/PointerSyntaxError.scala

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
87.71% <0.00%> (+1.16%)
: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 a776345...80b8a0f. Read the comment docs.


ApiView feedback: custom code serialization abstraction

This does the standalone changes previous incorporated into #42 that address the ApiView feedback of extreme repetition in the needed custom serialization code.
It establishes a set of templated static helpers along with a common pattern of SerializeFoo/DeserializeFoo that are then passed as delegates into those helpers. This allows full flexibility with derived type partial (de)serialization relative to instance-only methods.
Together, this makes the common impl pattern fairly minimal:
public partial class Foo : IJsonModel<Foo>
{
    Foo IJsonModel<Foo>.Create(ref Utf8JsonReader reader, ModelReaderWriterOptions options)
        => ModelSerializationHelpers.DeserializeNewInstance(this, DeserializeFoo, ref reader, options);

    Foo IPersistableModel<Foo>.Create(BinaryData data, ModelReaderWriterOptions options)
        => ModelSerializationHelpers.DeserializeNewInstance(this, DeserializeFoo, data, options);

    void IJsonModel<Foo>.Write(Utf8JsonWriter writer, ModelReaderWriterOptions options)
        => ModelSerializationHelpers.SerializeInstance(this, SerializeFoo, writer, options);

    BinaryData IPersistableModel<Foo>.Write(ModelReaderWriterOptions options)
        => ModelSerializationHelpers.SerializeInstance(this, options);

    string IPersistableModel<Foo>.GetFormatFromOptions(ModelReaderWriterOptions options) => "J";

    internal static Foo DeserializeFoo(JsonElement element, ModelReaderWriterOptions options = default)
    {
        // Deserialize from element here, can easily call derived type methods as needed
    }

    internal static void SerializeFoo(Foo foo, Utf8JsonWriter writer, ModelReaderWriterOptions options)
    {
        // Serialize "foo" here, can invoke overriden derived type serializers like "WriteDerived" as needed
    }

    // As needed for type hierarchies
    internal abstract void WriteDerived(Utf8JsonWriter writer, ModelReaderWriterOptions options);
}

Closing in favor of
https://github.com/joseharriaga/openai-in-typespec/pull/113


Adding recommendation for network isolation

In a multi-tenant environment, certain use case might requires traffic to be allowed between tenant owned namespaces, be very mindful to avoid any use of empty label selector {} for namespaceSelector field in network policy definition and strictly stick with specific labels which is set to namespaces.
if you think about consequences of using empty selector mistakenly for namespaceSelector field..It indeed matches all the available namespaces leading to condition where it will open communication from all other available namespace which will violate network isolation. So i think it would be right choice to make user aware of this as a recommendation.

Note: this PR replaced #34624.

#34624

/sig security

Can we have it reviewed, please?

Ping @kubernetes/sig-security-pr-reviews


Add development guide

How to contribute to kCTF - like contributors.md

I think we can do this after the release (== -label out of beta)

I think we can do this after the release (== -label out of beta)

yep, agreed. I thought this was about user docs.

yep, agreed. I thought this was about user docs.


Charm upgrade doesn't update alert rules

I've upgraded the hardware-observer charm to rev 22 today. Alert rules didn't get updated. For example, this old alert rule is still there:
name: IPMISensorStateNotOk
expr: ipmi_generic_sensor_value{juju_application="nova-compute",juju_model="openstack",juju_model_uuid="redacted",state=~"Warning|Critical"}

Freshly deployed rev 22 in another juju model created this alert rule correctly:
name: IPMISensorStateNotOk
expr: ipmi_generic_sensor_value{juju_application="infra-node",juju_model="maas-infra",juju_model_uuid="redacted",state=~"Warning|Critical",type!~"Entity\\sPresence|Slot/Connector"}

Can you try removing relation and adding relation to see if it solve the problem? If it does solve the problem, then I think we can try to adding the upgrade event to COSAgentProvider

Removing and re-adding relations with nova-compute and grafana-agent resulted in all units in this env stuck in the blocked state reported in issue #128.
The same alert from the previous charm revisions is still visible in Prometheus, the new one still hasn't appeared but that might be because all units are now blocked.

hmm, I guess one of the relation data should be updated hardware-observer <--A--> grafana-agent <--B--> prometheus-k8s because the alert rules are passed via the relation data.
If removing and re-adding A isn't working, maybe B should be re-created. However, I would probably not do it in prod environment, since I am not sure what could break. juju show-unit may give you the hints

This is a production environment and the relation you described as B cannot be recreated just for troubleshooting purposes. Prometheus redeployment is even less acceptable in this env. Besides, all hardware-observer units are now blocked as mentioned earlier due to another issue.

I shared the output of juju show-unit for one of the grafana-agent units privately.

It should be an issue in cos-proxy after dig into the issue.

Need to register the refresh event during create COSAgentProvider
ex: https://github.com/canonical/postgresql-operator/blob/main/src/charm.py#L145


MQTT "retain" attribute not supported by AWS IOT

From http://docs.aws.amazon.com/iot/latest/developerguide/protocols.html

The MQTT specification provides a provision for the publisher to request that the broker retain the last message sent to a topic and send it to all future topic subscribers. AWS IoT does not support retained messages. If a request is made to retain messages, the connection is disconnected.

This code should not try to set the retain flag, and should clear the retain flag if an attempt is made to set it.

I updated following your suggestion. Thanks for your reference link.

Relating to issue#8, the options must be an empty {} to avoid adding chars of qos or retain that will cause the IoT rule is fallen when passing the payload to AWS ElasticSearch. But using with DynamoDB, the payload is parsed OK.

Interesting. Our downstream database is DynamoDB and so we didn't notice the problem.


Multiple responses to relationship questions

Firstly, thank you to all those involved in the developing CENode! It is a very cool library and a perfect fit for the project I am working on.
While following the Getting Started Guide, I noticed that when asking a relationship question like
"What orbits the sun?", only a single answer would be returned. Here is a screen shot from the demo.

After looking over the implementation of the QuestionParser class, it seemed that once a valid response is found in the whatRelationship function, it short circuits only returning the first match.
This PR introduces a small change to the logic that allows for multiple unique responses to be returned for "what relationship" questions. The new expected behavior would be as follows.
For a question like "What orbits the sun?" the response would be "Mercury orbits the star sun. Venus orbits the star sun. Earth orbits... etc"
If this proposed code change diverges from the CEStore specification, I can withdraw this PR. It just seemed that if multiple instances in the knowledge base matched a query, they should be included in the response.
I wasn't sure how to best test this behavior. My naive attempt consisted of replicating the broken behavior exhibited in the demo. In order to wait for the gist card to be present, I needed to use a setTimeout similarly to how it is used in the demo code. I found this lead to false positives if I wasn't being careful, so if there is a better way to unit test for this behavior, I can definitely rework the test.

This is great - thanks a lot for your contribution! This side was certainly lacking in functionality so it's good that we can extend this out a little. As long as the responses can be properly integrated into the rest of the card protocol (which they do), then additions like this are perfect.
The test case is fine - timeouts are often the only way to test due to the asynchronous nature of the CEAgent. However, I am sure that there may be better ways we can ivestigate further down the line.
Thanks again, and nice to see someone finding some use in this library outside of our research.


Add Toggle Button for Total Price Including GST on Listings Page (Fixes #241)

Fixes #241
Added a toggle button on the listing page, allowing users to view the total price with GST included. This feature aligns with platforms like Airbnb, enhancing pricing transparency and improving user trust
Changes

Added Toggle Button: A new toggle switch labeled "Display total with GST" is added next to the filter options on the listings page for easy visibility.
GST Calculation: Integrated functionality to dynamically include GST in the displayed price when the toggle is enabled, providing users with the full cost view.

Screenshots (if applicable)
https://github.com/user-attachments/assets/f8e13ccc-f3fc-48a6-a7d9-157f20540baa
Checklist

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I am working on this issue under GSSOC

Hello @Soujanya2004 ,
My last pull requests haven’t been reflected on the GSSoC leaderboard. Could you help me understand why they might not be counted?

@dipexplorer can you name the issue number


[feature request] StableCascade

After StableCascade has been introduced natively in comfyUI, a direct conversion from stage_b latent to SDXL or SD1.5 latent format would be very useful!
But I need to admit, I have no idea if it's even possible..

But I need to admit, I have no idea if it's even possible..

I mean, it should be, if you don't mind the quality being sub-par. I only did a quick test w/ stage C so far to see if I could ditch stage B completely, and that seemed to kinda-sorta work.

@city96 Sounds interesting! But I don't think it's a good idea to connect to stage_c latent, because - of what I understood - stage_c latent is compressed and stage_b takes over the decoding of the compressed latent. The latent output of stage_b would then be more in my focus.

@MoonMoon82 Hi, a bit late but I finished training some models for stage_b. Also redid the v1/xl stuff to be slightly better. Can you test it if you have the time? They're on the experimental branch for now but I'll merge them to main if everything looks fine.


Added support to provide device Id on runtime.

Added support to provide device Id on runtime. so that user can run test for different variants on different device in Parallel way.
Let me know, if you have any thoughts on this.

Device IDs can be specified using the spoon extension in an application build.gradle.
spoon {
  devices = ['333236E9AE5800EC']
}

And in your build.gradle file you can use a project property to provide values via the command line.
It should work for you too.

yup, you are right,
but in my case as i want to run test for different variants simultaneously, it won't work. It will pickup the device that you mentioned in build.gradle file for both variants, and hence will run them one after another.
Correct me if I'm wrong.
./gradlew spoonProjectADebugAndroidTest -PdeviceId=firstDeviceId
./gradlew spoonProjectBDebugAndroidTest -PdeviceId=secondDeviceId

In this way, these are two different process running test on two device simultaneously.

What I'm talking about is that you will achieve the same result with the following lines in your build.gradle, without the plugin modification:
spoon {
  if (project.hasProperty('deviceId')) {
    devices = [project.deviceId]
  }
}

yup, you are right.
Apologies,
i am new to groovy so didn't know this way to assign the variable devices.
I should've seen this example .
Thank you for your time.


Erratic freehand line ends that get bed with a graphic tablet

Hey there!
First of all, thanks for the awesome piece of software!
There is a bit of an issue with freehand drawing. Here is a random word handwritten on a wacom in the latest Safari:

And here are a few random scribbles to showcase the issue:

As you can see, stroke ends almost always have that disconnected dot at the end which looks quite messy.
It's a bit better in Chrome, surprisingly, but not perfect either:

I haven't looked at the code, but it looks like pressure sensitive part of stroke drawing is a bit misaligned with the end-of-stroke-circle logic, which leads to those inconsistencies.
I looked through the issues and haven't found anything similar yet, apologies if it's a duplicate.

can reproduce with my wacom intuos s on windows 11. Happens both in firefox and chrome, aswell as in the obsidian plugin.


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on 594119119 for fa5007feb87aa8a25bdcbcf14c7a29d9f07763cc
https://gitlab.com/MatrixAI/open-source/js-db/-/pipelines/594119119

Pipeline Succeeded on 594119119 for fa5007feb87aa8a25bdcbcf14c7a29d9f07763cc
https://gitlab.com/MatrixAI/open-source/js-db/-/pipelines/594119119


Support for Cloudflare.

Clear and concise description of the problem
Due to frequent blocking when deploying to Vercel, Cloudflare is also a good solution. I hope to have
Suggested solution
https://docs.astro.build/en/guides/integrations-guide/cloudflare/
https://docs.astro.build/zh-cn/guides/deploy/cloudflare/
Currently, I followed the above solution to migrate ddiu8081/chatgpt-demo from "@astrojs/vercel": "^3.1.3" to "@astrojs/cloudflare": "^6.1.3".
When deploying with Cloudflare, set NODE_VERSION to 19.7.0.
The deployment log is as follows:
11:50:41.062 |
-- | --
11:50:41.122 | HEAD is now at 0533b2d ci: cloudflare
11:50:41.123 |
11:50:41.267 |
11:50:41.294 | Success: Finished cloning repository files
11:50:42.101 | Installing dependencies
11:50:42.113 | Python version set to 2.7
11:50:45.794 | Downloading and installing node v19.7.0...
11:50:46.250 | Downloading https://nodejs.org/dist/v19.7.0/node-v19.7.0-linux-x64.tar.xz...
11:50:46.698 | Computing checksum with sha256sum
11:50:46.840 | Checksums matched!
11:50:51.271 | node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
11:50:51.272 | node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
11:50:51.272 | node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
11:50:51.327 | nvm is not compatible with the npm config "prefix" option: currently set to ""
11:50:51.329 | Run `npm config delete prefix` or `nvm use --delete-prefix v19.7.0` to unset it.
11:50:51.330 | Failed to install node version '19.7.0'
11:50:51.334 | Failed: build command exited with code: 1
11:50:52.391 | Failed: an internal error occurred

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Sounds good. PR welcome.

@h7ml cloudflare unsupport node 18+, how do you fix this?

16:34:41.770 | Cloning repository...
-- | --
16:34:42.611 | From https://github.com/clearcodecn/chatgpt-demo
16:34:42.612 | * branch            f70b3296d66a36b58a21856fc88bb3f1882f3e2f -> FETCH_HEAD
16:34:42.612 |
16:34:42.663 | HEAD is now at f70b329 feat: change logo
16:34:42.664 |
16:34:42.803 |
16:34:42.829 | Success: Finished cloning repository files
16:34:43.561 | Installing dependencies
16:34:43.572 | Python version set to 2.7
16:34:46.879 | Downloading and installing node v18.14.2...
16:34:47.301 | Downloading https://nodejs.org/dist/v18.14.2/node-v18.14.2-linux-x64.tar.xz...
16:34:47.753 | Computing checksum with sha256sum
16:34:47.889 | Checksums matched!
16:34:52.080 | node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
16:34:52.080 | node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
16:34:52.081 | node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
16:34:52.127 | nvm is not compatible with the npm config "prefix" option: currently set to ""
16:34:52.129 | Run `npm config delete prefix` or `nvm use --delete-prefix v18.14.2` to unset it.
16:34:52.130 | Failed to install node version '18.14.2'
16:34:52.134 | Failed: build command exited with code: 1
16:34:53.060 | Failed: an internal error occurred

cloudflare unsupport node 18+, how do you fix this?

I have reviewed the following documents:

https://github.com/cloudflare/pages-build-image/discussions/1#discussioncomment-4988959
https://community.cloudflare.com/t/github-pages-astro-framework-node-js-v12-18-0-is-not-supported-by-astro/430276
https://community.cloudflare.com/t/support-node-18-in-pages-or-allow-config/414797

However, it does support Node 17.

Cloudflare doesn't support Node 18,  you can take a look at the currently supported platforms.: https://docs.astro.build/en/guides/deploy

Now, Cloudflare support higher node version but it's in Beta
Settings -> Builds& Deployments -> Build system version ->  Configure Production build system

And I follow the https://docs.astro.build/en/guides/integrations-guide/cloudflare/ docs, I even cannot build successfully locally, So I temporally change to build a static file instead of an SSR file
Change to build Static File
export default defineConfig({
  integrations: [
    unocss(),
    solidJs(),
  ],
  output: 'server', // Delete this line
  adapter: envAdapter(), // Delete this line
  ....
})

When I use SSR mode runs locally
I have tried node v16.20.1,v18.16.1,v20.1.0 all got same error message,  if I change adapter to vercel() or netlify() it will build success
Simplified Configuration:
import cloudflare from '@astrojs/cloudflare';
export default defineConfig({
  integrations: [
    unocss(),
    solidJs(),
  ],
   output: 'server',
   adapter: cloudflare()
  ....
})

Execute Command
astro build

I got the error:
05:05:39 PM [build] Rearranging server assets...
✘ [ERROR] Could not resolve "util"

    node_modules/.pnpm/undici@5.20.0/node_modules/undici/lib/fetch/file.js:4:26:
      4 │ const { types } = require('util')
        │                           ~~~~~~
        ╵                           "./util"

  The package "util" wasn't found on the file system but is built into node. Are you trying to
  bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "assert"

    node_modules/.pnpm/undici@5.20.0/node_modules/undici/lib/fetch/dataURL.js:1:23:
      1 │ const assert = require('assert')
        ╵                        ~~~~~~~~

  The package "assert" wasn't found on the file system but is built into node. Are you trying to
  bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
......

Error: Build failed with 67 errors:
node_modules/.pnpm/busboy@1.6.0/node_modules/busboy/lib/types/multipart.js:3:39: ERROR: Could not resolve "stream"
node_modules/.pnpm/busboy@1.6.0/node_modules/busboy/lib/types/urlencoded.js:3:29: ERROR: Could not resolve "stream"
node_modules/.pnpm/undici@5.20.0/node_modules/undici/lib/api/api-connect.js:4:34: ERROR: Could not resolve "async_hooks"
node_modules/.pnpm/undici@5.20.0/node_modules/undici/lib/api/api-pipeline.js:7:12: ERROR: Could not resolve "stream"
node_modules/.pnpm/undici@5.20.0/node_modules/undici/lib/api/api-pipeline.js:14:34: ERROR: Could not resolve "async_hooks"

.....

If someone knows how to use SSR mode for build, I would be very grateful.

This project cannot run in static file mode, this will make API call doesn't work


Support custom openai base url in config_list_openai_aoai

Add support to custom openai base url

Why do we need this?

@thinkall ?

Why do we need this?

To support local models. Currently, if a local model is defined with environment variables, it won't work.

Why is that? Does openai's Client ignore the base_url?


Highlight landable planets with high gravity

We've all been there. "Hey look, a cool planet with volcanism! I'm just gonna land there and check it out" and then boom... you just crash on the planet and lose your exploration data because you forgot to check the gravity on the planet and turns out, it's a 1.5G.
From what I saw in the journal files, the gravity data is present in the SurfaceGravity field of Scan type events so you shouldn't need to change the core of the app, only the web rendering.
It would be great to have visual awareness of these bodies in the interface, without having to open the System Map. It could be another icon next to the landable sign, representing high G body; or even a small border around the body entry for instance.
Let me know what you think. I can open a PR with that change

I think that's an excellent idea. No need to open another one - the detail here is just fine for a request.
The question is, how much gravity is too much gravity i.e. where do we set the bar?

Just be gentle when you're hunting through the code. At web dev i am no master 😉

I think anything past 1g should have some warning. 2 isn't bad, but the point is to have a warning beforehand so you don't assume anything, and going in quick on a 2 could get touchy. What about a diamond warning sign with "g" inside, over 1 g is yellow, over 2 orange, over 3 red. Adjust the numbers if need be, maybe even have it so users can adjust them in the ini (for experienced pilots who know their limits).

Configurable limits in the config file for warning (amber) and high-alert (red) both with a black background sound like a neat idea. Could display it after the body name or as another icon. Displaying the number of G to 1.d.p if it's over the 1g limit could work well I think. Could overlay the landable icon with it as another possible.option.
Need to prototype a few.of these and fly with them for. A bit to see (that's how I normally try out new ideas)..

My initial idea was to keep it simple and just display another icon if the gravity is >= 1.0G.
I'm not the most experienced explorer but I don't think I've encountered many landable planets above 2.0G. In any case, @Rhaedas I really like your idea of color progression depending on the value. Sounds good to me as well!
@joncage let me know if you need help with the prototypes. Either of the variants we've been talking about sound like a simple feature to implement and I'm more than glad to contribute and put my hands on the code if needed

Happy to receive a pull request. I think I'm sold.on an extra signal that appears to the right of the landable icon. Just text that appears orange of 1.0-1.9G and red if 2.0+ by default.
Then add come config options to adjust those thresholds.
Keeping this info right next to the landable icon keeps the information together and makes it quicker to grok

Not a bad start:

Just need to:

Add some background clearing behind the numbes to the colour is always legible.
Adjust the styles when it's looking like a tricky landing (javascript is in there to add the tags, just need the CSS).

I'm wondering if the landable flag should be included in this black box so it's another clear indicator?

Tada!

Ahhh! You beat me to it, I was now cloning the repo. Heh.
That's it mate! Now is just a matter of styling it the way you feel appropriate for the app! Nice work!

Looks like the text in that span is shuffled down by two pixels annoyingly which means the black surround hits the bottom of the div that contains it. I'll push what I've got so far - see what you think in the 0117-AddHighGIndicator branch I've just pushed.

It's looking ok on my end:

Like what you all are putting together, I think the numbers approach works well, gives more info than my first idea of a range symbol. 9.8 - ow, my back.

One more touch I've been mulling over today to add. I'm going to make it so landable planets always get a number next to them but it'll be green for low G planets.
I'll also expand the black background around the landable icon to tie them together.
If that pans out, it should make a nice neat consistent solution I think.
After a bit of flying around last night with the first attempt at this I've suddenly realised there are a lot of 6+G planets out there. I say am 8.4 too.. ...although they were all boring ice planets so not something I would have attempted a landing on.

Awesome! I think this is going to help a lot of explorers out there! Thank you for the support!


docs: mention type import alias

Description
When using Typescript's bundler resolution, I'd like to import the BreadcrumbLink type. I think I'm not able to yet, but I'd like to be.
Additional context
No response

You can import this type from #ui/types:
import type { BreadcrumbLink } from '#ui/types'

Those types are for internal usage and I don't really see a use-case where you'd need to import them. That's why it is not in the documentation.

E.g. when defining wrapper components:
<template>
  <UBreadcrumb :links="items">
    <template #icon="{ link }">
      <IHeroiconsHome v-if="link.to === localePath('/')" />
    </template>
  </UBreadcrumb>
</template>

<script setup lang="ts">
import type { BreadcrumbLink } from '#ui/types'

export interface Props {
  links: BreadcrumbLink
}
withDefaults(defineProps<Props>(), {})

const localePath = useLocalePath()
</script>

@dargmuesli I've added a TypeScript section to the docs with your example: https://ui.nuxt.com/dev/getting-started/installation#typescript

❤ Thank you!

Unfortunatly importing from '#ui/types' is not resolved here, getting 'Cannot find module '#ui/types' or its corresponding type declarations.'

@ulysse-lacour Would you mind providing a reproduction? What version are your using?

@benjamincanac of course thank you!
As general infos I'm using "@nuxt/ui": "^2.12.0", I had to add "resolutions": {"vue": "3.3.13"} to package.json to avoid multiples hydratation mismatches and the nuxt app is dockerized, for now i'm testing the library with the Dropdown for locale selector. Beside this import error the NuxtUI components are rendering very nicely and everything's working, here is the component :
`typescript

`
Lemme know if I can provide any other meaningfull infos!

@ulysse-lacour Would you mind sharing a StackBlitz reproduction with the error?

Trying to do so but not succeeding for now, the whole repo is quite big (with a strapi backend), never really used Stackblitz to upload anything there and don't really know how to run docker containers up there...

Just made a simple reproduction where the type import works: https://stackblitz.com/edit/nuxt-ui-4lcnqa?file=app.vue.

Thank you very much for your help!
I just realized the import error is in fact just a vscode alert but still works, weirdly enough adding the aliases manually to root tsconfig.json makes the import "valid" for vscode
"#ui": [
        "./node_modules/@nuxt/ui/dist/runtime"
      ],
      "#ui/*": [
        "./node_modules/@nuxt/ui/dist/runtime/*"
      ],
      "#ui-colors": [
        "./ui.colors"
      ],

But my .nuxt tsconfig already has valid imports and root one is extending it, the issue is certainly not related to NuxtUI but on some incoherence on my project structure and vscode/typescript set up, will keep investigate on what is happening there!

After doing a few research I couldn't find a better way to fix this problem but to import and adapt path aliases in root tsconfig.json. A bit painfull but absolutly working!

Do you have nuxt prepare in your postinstall script?

I do, and types do get well generated in my .nuxt folder, but vscode seems to not read ts config of .nuxt and only root one

Again, without a reproduction I won't be able to help you better. If you get one, it could be nice to open a new issue about this 😊

You can import this type from #ui/types:
import type { BreadcrumbLink } from '#ui/types'

Should it be working for Nuxt UI 3 ?

@jimbatamang In Nuxt UI v3, you can import types from @nuxt/ui.


Prevent integer overflow crashes

The current implementation of integer mapping does not guard against integer overflow, and in addition, does not properly guard against trying to store 64-bit values in (U)Int on 32-bit devices. This is an attempt to mitigate against integer overflow crashes and unwrap values from JSON more appropriately into the specified (U)Int widths. This takes advantage of some new additions in Swift 3.1.

Thanks!


[platform automation] stage/configure/apply without product

This applies to pivotal platform automation; I don't want to go through Pivotal support because I hate not being able to reference conversations + comments in it, so I'm dumping these thoughts here & if they suck or you don't want them then here please close this out as soon as possible 😉
context
I looked through some of the Task References and wanted to share what I noticed.
Most tasks such stage, configure or selective-deploy all take in the product as an input. This makes sense, because then you can use om product-metadata to get the name/version.
problem
But passing around *.pivotal files just for the name/version is time-consuming and stressful on the Concourse environment. It means passing around a 10+gb cf.pivotal file just to stage and apply PAS, even though it was already uploaded. Even on good days, passing around big honkin' files to stage and triggering apply for PAS can take 20-40 minutes just to start the process for the ceremony surrounding extracting the name/version.
The same applies with replicated tiles-- if you're reliant on the product for the name/version, you have to download the isoseg tile, replicate it, and then pass it to stage/assign stemcell/configure/apply (or once you replicate it you store it in s3, but it's still a pain)
The only time you need the product is when uploading it, replicating it, generating configuration from it, or yanking metadata from it. After that, you don't need it-- you just need the name of it.
proposal... sort of
I'll have to actually implement & try it before suggesting anything that would be part of the platform-automation toolchain, but: currently we store the product-version and stemcell-version as flat files in a config repo. Our stage/configure/apply tasks read from these files and pass their content to om.
What if the product-name came from the product.yml, and the product-version came from a flat file that just had the semver of the product or stemcell in it? (e.g., 2.6.11-build.3 or 315.95.0, etc.).
If the product is passed in, it's used for the name/version. If the product-{name,version} files get passed in, they're used instead.
disclaimer / conclusion
We've fallen off the platform-automation mainline train for some of our tasks, so at some point we need to re-familiarize ourselves with the out-of-the-box configuration like stemcell handling, downloading products, etc. to see how these can fit together. We'll get around to uplifting all this eventually. I say this because even though I'm making this suggestion, I'm not going to have a ton of time to personally implement it in the next few days/weeks...
... What I'm saying is this proposal is untested and isn't an immediate priority, but I know it's a problem & I know it's something that can be solved, it's just a matter of finding the perfect pattern that fits within a logical framework of how platform CI/CD should/could be done
Thoughts and feedback welcome. And obviously feel free to close it whenever, I know it's off-top from om, so apologies about that. Thanks for your time 👍

Expanding on this issue to explore a possible use-case for this change:
Platform Automation tasks that stage a product all take a product file. This is useful for pipeline design/simplicity reasons, but Ops Manager 2.8 has a pre-uploaded-but-not-staged telemetry tile. Since there's no product file necessary for this tile, users have to write a custom task to stage it.

We made some changes to platform automation to support passing in either a separate file to stage-configure-apply with just the name and version, or the product.yml used by configure-product with the version added. Take a look at what we're thinking for the next release of platform automation. Going to close out this issue! Thanks for being so willing to chat with the team and work with us through this!
https://docs.pivotal.io/platform-automation/develop/release-notes.html#whats-new

Hey @kcboyle okay real quick, sorry to append this to the same github issue I can create another one, but quick idea:
on tasks such as apply-changes there are certain envvars which can be set like this:
  ALLOW_PENDING_CHANGES: false
  # - Optional
  # - If false, will fail if there are pending changes in OpsMan

  RECREATE: false
  # - Optional
  # - If true, will recreate the vms for the product
  # - If true, will also recreate the director vm if there are changes

  IGNORE_WARNINGS: false
  # - Optional
  # - If true, will not fail when verifiers have warnings,
  #   it will still fail for any errors.
  # - This is not recommended unless unless the warning failure(s)
  #   are well understood.

Those are valuable flags, though they're set as envvars "statically" and can only be changed/set using fly, rather than dynamically reading them from a file in git.
Any thoughts on making configuration switches like that available to be set in a file as well? E.g. imagine features.yml or options.yml or flags.yml or switches.yml or command-flags.yml, I have no idea what to actually call it, but it'd be a file that has those same kinds of flags set via task envvars except parameterized as code, example:
# flags.yml
recreate: true
allow-pending-changes: false
ignore-warnings: false

then have the flags.yml be able to be passed in for commands such as om apply-changes [...] --flags=/some/product/and/foundation/path/here/flags.yml?
To be honest this is something I was going to do regardless for how we pass --recreate now that we're on 2.9.x+, but just hadn't gotten to it or evaluated it yet 😬
Just a thought, I can absolutely create this as a separate issue.
regardless, thanks a ton to you all as well, thanks for your time!

Hmmmm I can definitely see the use case for the recreate and allow-pending-changes flags. (though in the case of SCA, ALLOW_PENDING_CHANGES: true seems like it would be undesired in the majority of cases)
I have concerns about ignore-warnings being a passable flag. We've been very defensive about how you can set that flag (and only recently added it because there are a few warnings in ops man that do not disappear even if you disable the verifier). if we could pass those in via a file, that would be an om change though, not just a change to platform automation.
I'm not sure how I feel about passing in the flags via a --flags flag though. for other commands, we got away with it by allowing a config file (or an --env file in the case of the global flags). It just feels...strange?..to have a flag for a command called flags that accepts a file.
Created a new issue to talk about this further: #494


Update Dockerfile

WIP: In this PR, I am not using script.sh file which was not being accessed by the Docker container even though path was correct.
Problem: ./a.out command does not get executed in Docker Container


Add missing closing bracket to mutation structure

I noticed this was missing a balanced bracket!

Why:

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

@Patrycz3k Thanks so much for opening a PR! I'll get this triaged for review ⚡

@Patrycz3k Thanks so much for opening a PR! I'll get this triaged for review ⚡


Capacitive examples

I've created a version of 2 of the samples that work with the capacitive version of the board. I've put them under a folder called capacitive-examples but feel free to suggest somewhere else of them to go.

Thank you for your contribution! Sorry for leaving this without any reaction for so long.
Currently this repo focuses on the CYD (+CYD2USB). Your PR would add parts of code for a different display which uses different pinouts/touch and probably other things.
Personally I would prefer this repo to keep focus on the current two variants to keep complexity managable.
Any other opinions?

There's a directory in this repo for variants, right?

True, but it only has a minimal set of information right now and no deeper folder structure.
We could move this to /variantes/[variant name]/examples 🤔


Redoc document never renders

I'm getting a "Loading ... " response, but it never returns.
Asp.Net 462 WebAPI with Owin.  Here is the relevant code for defining the endpoints:
app.UseSwagger(typeof(OwinStartup).Assembly, settings =>
                {
                    settings.GeneratorSettings.OperationProcessors.TryGet<ApiVersionProcessor>().IncludedVersions = new[] {"1.0"};
                    settings.GeneratorSettings.SchemaType = SchemaType.OpenApi3;
                    settings.GeneratorSettings.Title = "Magnus API";
                    settings.GeneratorSettings.Version = "v1.0";
                    settings.DocumentPath = "/swagger/v1.0.json";
                });

                app.UseSwagger(typeof(OwinStartup).Assembly, settings =>
                {
                    settings.GeneratorSettings.OperationProcessors.TryGet<ApiVersionProcessor>().IncludedVersions = new[] { "2.0" };
                    settings.GeneratorSettings.SchemaType = SchemaType.OpenApi3;
                    settings.GeneratorSettings.Title = "Magnus API";
                    settings.GeneratorSettings.Version = "v2.0";
                    settings.DocumentPath = "/swagger/v2.0.json";
                });

                app.UseSwaggerUi3(settings =>
                {
                    settings.Path = "/swagger";
                    settings.SwaggerRoutes.Add(new SwaggerUi3Route("v1.0", "/swagger/v1.0.json"));
                    settings.SwaggerRoutes.Add(new SwaggerUi3Route("v2.0", "/swagger/v2.0.json"));
                });

                app.UseSwaggerReDoc(settings =>
                {
                    settings.Path = "/redoc";
                    settings.DocumentPath = "/swagger/v1.0.json";
                });

Here is the snippet from Web.config:
      <remove name="NSwag_swagger" />
      <remove name="NSwag_redoc" />
      <add name="NSwag_swagger" path="swagger" verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="NSwag_redoc" path="redoc" verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />

Both of the swagger endpoints render properly.
Anything obviously incorrect with the above?
Thanks in advance,
Nick

any error in your browser's console?

None - just no response.

Wondering now if it's because our api document (json) is ~2MB?  Any recommendations on how to debug further?

No idea, probably an issue with redoc if the json file is loaded properly if there's nothing in the console, I really don't know what you could do except asking redoc what to do...

@jeremyVignelles  - thanks for the response.
I believe it's related to this issue: https://github.com/Redocly/redoc/issues/696
Digging now.


Add support for type 3 converter

Type 3 converter is a gas optimized version of the type 1 converter, specifically for standard pools (2 reserves and 50%/50% weights).
The interface is identical (except some legacy functions - see below) but since the type is different, some references might need to be adjusted.
Setting a fee queries the type today so that's one example the code needs to be updated, after pool creation.
There might be more references to the type as well so it requires checking those areas.
The only interface change (other than the actual type) is the fund/liquidate functions that were removed. addLiquidity/removeLiquidity should be used instead.
Note that the converter also supports dedicated simplified add/remove liquidity functions but no need to integrate that right away.
The converter registry is updated such as that when a caller requests to create a standard type 1 pool, type 3 is actually created, so no code change requires there. Same goes for the upgrader - standard type 1 pools will be upgraded to type 3 pools.
Ropsten is updated with the changes.

done https://github.com/bancorprotocol/webapp/commit/71be6e7dd8b0c39b63a42e1d319fb1da1d962fc0


wasm: add api for configuring environment variable in VmConfig

Commit Message: wasm: add api for configuring environment variables in VmConfig. This commit adds an API on VmConfig so that users can configure env vars to be injected to Wasm VMs. Resolves https://github.com/envoyproxy/envoy/issues/14958
Signed-off-by: Takeshi Yoneda<EMAIL_ADDRESS>

what happens if both host_env_keys and key_values define the same key. Should we reject such configurations?

Thanks, that's a good point. I think we should reject since that case may cause some unintended behavior in Wasm programs. WDYT?

Thanks, that's a good point. I think we should reject since that case may cause some unintended behavior in Wasm programs. WDYT?

SGTM.

/retest

do you want to add the implementation to this PR?

Will do.

/retest

macos failure is irrelevant to this RP according to the discussion in Envoy slack

/retest

@htuch could you take another look? Thank you!

@moderation as well for deps.

/lgtm deps

@htuch Thanks for the review!  PTAL :+1:

/retest

/lgtm deps


Update README.md

Added superseded notice

@vcolmenar Just flagging this for you. Hoping you can accept this change so that people know that your guide is out of date.


Custom array_ufunc does not get called in binary operation

Description
When subclassing ndarray, the custom subclasses with __array_ufunc__ sometimes show unexpected behavior when used in binary operation.
Cases:

Binary operation with both operands being ndarray or its subclass object, e.g., custom_obj + custom_obj or custom_obj + ndarray_obj, does not invoke __array_ufunc__ of the subclass.  Instead, it falls back into that of CuPy ndarray.
Binary operation with one operand being a scalar like int or float does invoke __array_ufunc__ of the subclass as expected.

Just as a note, we do not observe this with NumPy ndarray class and its subclasses.  With NumPy, custom __array_ufunc__ overrides ndarray __array_ufunc__.
To Reproduce
import numpy, cupy

for xp in [numpy, cupy]:
    class Foo(xp.ndarray):
        def __array_ufunc__(*args, **kwargs):
            print(args, kwargs)

    carr = xp.zeros(2).view(Foo)
    xarr = xp.zeros(2)

    print(xp.__name__)
    print("Expression 1")
    carr + carr
    print("Expression 2")
    carr + xarr
    print("Expression 3")
    xarr + carr
    print("Expression 4")
    carr == carr
    print("Expression 5")
    carr + 1.0
    print("Expression 6")
    carr == 0
    print()

Installation
Wheel (pip install cupy-***)
Environment
OS                           : Linux-3.10.0-957.el7.x86_64-x86_64-with-glibc2.17
Python Version               : 3.10.4
CuPy Version                 : 11.5.0
CuPy Platform                : NVIDIA CUDA
NumPy Version                : 1.23.0
SciPy Version                : None
Cython Build Version         : 0.29.32
Cython Runtime Version       : None
CUDA Root                    : /nvme/h/buildsets/eb_cyclamen/software/CUDAcore/11.1.1
nvcc PATH                    : /nvme/h/buildsets/eb_cyclamen/software/CUDAcore/11.1.1/bin/nvcc
CUDA Build Version           : 11010
CUDA Driver Version          : 11020
CUDA Runtime Version         : 11010
cuBLAS Version               : (available)
cuFFT Version                : 10300
cuRAND Version               : 10202
cuSOLVER Version             : (11, 0, 1)
cuSPARSE Version             : (available)
NVRTC Version                : (11, 1)
Thrust Version               : 100910
CUB Build Version            : 100910
Jitify Build Version         : 4a37de0
cuDNN Build Version          : (not loaded; try `import cupy.cuda.cudnn` first)
cuDNN Version                : (not loaded; try `import cupy.cuda.cudnn` first)
NCCL Build Version           : None
NCCL Runtime Version         : None
cuTENSOR Version             : None
cuSPARSELt Build Version     : None
Device 0 Name                : Tesla P100-PCIE-16GB
Device 0 Compute Capability  : 60
Device 0 PCI Bus ID          : 0000:86:00.0

Additional Information
No response

To increase performance and reduce CPU code overhead, we don't call __array_ufunc__ if both operands are CuPy arrays. This was done before array subclassing was implemented, so maybe it is worth enabling some exceptions to this rule.

Maybe we can replace if isinstance(y, ndarray): with if type(y) == ndarray:?
https://github.com/cupy/cupy/blob/36ce0bb12c214f1c9c46d42c3d6b9be3453b8543/cupy/_core/core.pyx#L1268-L1269


[Bug] Cursor placement with Quick Actions message seems wrong

Describe the bug
When on a new line, the message "Press / for quick actions" appears.
However, the cursor is at the end of that text which is quite disturbing. (For instance, this behavior is different from Notion behavior)
Indeed, when typing "/", the cursor then abruptly returns to its normal position.
Yet, I am not sure whether it's a bug or if it is intended.
To Reproduce
Steps to reproduce the behavior:

Open a note
Press "Enter" to go to a new line

Expected behavior
The cursor should stay on the left of the page and on the left of the "Press / for quick actions" text.
Screenshots

On this screenshot, one can see the cursor on the right of the text.
Desktop (please complete the following information):

OS: Windows 11
Version : 0.20.1

Seems like a Windows related issue, since it isn't the case on Mac. I'll investigate, thanks!

@AntoineQ1 This has been fixed. Please download the latest release from https://octarine.app/beta-releases to install it.


[SPARK-19220][UI] Make redirection to HTTPS apply to all URIs. (branch-2.1)

The redirect handler was installed only for the root of the server;
any other context ended up being served directly through the HTTP
port. Since every sub page (e.g. application UIs in the history
server) is a separate servlet context, this meant that everything
but the root was accessible via HTTP still.
The change adds separate names to each connector, and binds contexts
to specific connectors so that content is only served through the
HTTPS connector when it's enabled. In that case, the only thing that
binds to the HTTP connector is the redirect handler.
Tested with new unit tests and by checking a live history server.
(cherry picked from commit d3dcb63b9709a34337327be9b7d3705698716077)

Test build #72031 has started for PR 16711 at commit b3959ed.

Test build #72031 has finished for PR 16711 at commit b3959ed.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72031/
Test FAILed.

retest this please

Test build #72049 has started for PR 16711 at commit b3959ed.

Test build #72049 has finished for PR 16711 at commit b3959ed.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72049/
Test PASSed.

Merging to 2.1 (and 2.0 if no conflicts).

Didn't merge to 2.0.


Filenames split at whitespaces when using --cluster

Snakemake version

6.5.1
(did not yet track down the version where this first occurred, but somewhere after 6.1.0)
Describe the bug

Only when using snakemake --cluster ..., input filenames are split at whitespaces resulting in missing files.
Possibly related to https://github.com/snakemake/snakemake/issues/1007?
Logs

Waiting at most 60 seconds for missing files.
Missing files after 60 seconds:
data/biomass/JRC
Biomass
Potentials.xlsx

Minimal example

rule build_biomass_potentials:
    input:
        jrc_potentials="data/biomass/JRC Biomass Potentials.xlsx"
    output:
        biomass_potentials="resources/biomass_potentials.csv"
    script:
        "scripts/build_biomass_potentials.py"

Additional context

I can confirm this seems to be happening on my side as well when using an input function designed to return a path of the form: /storage/users/user/Reference Genomes/GRCh38.fa.gz, I end up getting a debug message stating :
Missing files after 5 seconds:
/storage/users/user/Reference
Genomes/GRCh38.fa.gz

I have tracked it back to this stack overflow submission, where it was pointed out by @Manavalan Gajapathy that you can use quotation marks in shell scripts to honour the whitespace in the command itself. With that in mind, this behaviour would indicate that the fault lies in some kind of check-up script that is run by snakemake to 'watch' for the output files?

Just a quick update. I changed my filename from Reference Genome to Reference_Genome and viola! Worked like a bomb. Definitely seems like something to do with how Snakemake handles file waiting.

As a side note, I did try to dig around the codebase myself, but despite getting pretty far along, I cant seem to find any functions relating to the wait_for_files group of functions called on inputs spesifically, much fewer inputs from function-based inputs as is my case (Though between @fneum and I's issue, it would indicate it's not an issue with function-based inputs specifically, just inputs in general?)


fix stack trace on blur cm #2332

block  scope.$apply(function ()....) has been deleted as unneeded

:+1:


[v1.14] images: bump cni plugins to v1.6.0

Backport of https://github.com/cilium/cilium/pull/36075

/test-backport-1.14

/test-backport-1.14


Can I use this library with selenium-webdriver as well? Instead of using Puppeteer.

Thanks for this library.
I'd like to know if I can use this library with selenium-webdriver.

I don't know because I'm not familiar with selenium-webdriver.
I'm assuming all it requires is the path to the headless Chromium binary, if so you can try this:
const pathToHeadlessChromium = await (require('chrome-aws-lambda').executablePath);

Should do the trick. You might need to use some of the default provided args as well.


[Compile perf] Make scale-test conditional on assertions, rdar://2909…

Finally reproduced the failure in rdar://29090287, it's just a "release-no-asserts" build which I hardly ever check; turns out that completely disables stats-gathering, so there's no output and the test fails.
Apologies for the delay.

@swift-ci please smoke test and merge


SauceLabs integration: report test status (success/fail) to the SauceLabs service

Are you requesting a feature or reporting a bug?
A feature
What is the current behavior?
After test job has been completed, SauceLabs task status is "unknown".
"This status is set if one or more jobs of the latest build haven't been reported as passed or failed. This state is equivalent to Finished."
What is the expected behavior?
Test results status is reported to the SauceLabs service.
Provide the test code and the tested page URL (if applicable)
https://github.com/surveyjs/surveyjs
Take a look to the sauce labs test status badge.

Please check the Annotating Tests with the Sauce Labs REST API article.
Also an option to make test results public could be helpful.

@AndreyBelym Can you take a look, please?

Ok, so we should perform a request to the SauceLabs REST API when tests are finished to set the status of the SauceLabs session to passed/failed. It requires some interaction between reporter and browser provider.


Changing process.env globally so no need for envvars anymore

What's in this PR?
Removing the need for envVars import, just use the node environment variable directly through process.env
Why
Because envVars was having a typing issue with e2e tests and needed a way to add more types to environment variables.  Plus, by doing this, we can make it so that each environment (test, dev, e2e, etc) can have a different typed set of environment variables and it also means that environment variables are dynamic now (not constant in const import)
Added feature flags
None
Affected issues
None
How has this been tested?
it compiles and all tests still work
Whats Next?
Continue working on e2e tests

Hi @mboudreau, I want to cautious here, so we are trading runtime strong type checking for testing time flexibility? The trade feels down grade from runtime perspective.
And envVar I assume checking the mandatory part during startup, while process.env does not, that's also another thing I am cautious.
Can you elaborate what exactly do you mean by Because envVars was having a typing issue with e2e tests?

Hi @mboudreau , can you please elaborate what exactly do you mean by Because envVars was having a typing issue with e2e tests  (like with a code sample?) so that we could understand more of the why?
Some thing could be a caveat is, like depends on when we call process.env, the env.ts (envVars) may or may not be included at that time, so the value of process.env.xxx may or may not be checked/initialized. This is a bit tricky to wrap head around.

Blocking till the concerns are addressed/eliminated :feelsbadman:

@gxueatlassian in the .env files, we can have different variables for tests, e2e, dev or any other environment.  Currently with envVars, there's no way of globally changing the current typing of EnvVars, you can only extend, which means that the code then has to read it from a different place to get the correct typings for that specific environment.  It becomes super confusing instead of just everything using process.env

Hi @mboudreau

there's no way of globally changing the current typing of EnvVars

Is it due to need a new field or need to change the value type of an existing field?
If former, can we do
export const envVars: EnvVars = {
	...process.env,
	...,
	getTestingVars: () => {
		return {
			VAR1: 'aaa',
			VAR2: 'bbb'
		}
	}
} as EnvVars;

export interface EnvVars {
	getTestingVars: ()=> {
			VAR1: 'aaa',
			VAR2: 'bbb'
	},
	NODE_ENV: EnvironmentEnum,
	MICROS_ENV: EnvironmentEnum;
	...
	// Cryptor
	CRYPTOR_URL: string;
	CRYPTOR_SIDECAR_CLIENT_IDENTIFICATION_CHALLENGE: string;
}

And so in the xxx.test.ts file, we can call envVars.getTestingVars().VAR1? With this, the production business code should never call envVars.getTestingVars(), still keep some sane in it.

If it is due to need for change value type of existing, can you please give some example? I don't understand it.

@bgvozdev I've updated the code, please review again

@bgvozdev I've updated the code, please review again

Awesome, @mboudreau , thanks a lot! And thanks for the patience 🙏 😄


Point release for Kotlin 1.9.10 support

Expected Behavior
Can build with Kotlin 1.9.10
Current Behavior
1.23.1 only supports Kotlin 1.9.0
Context
Hello, would it be possible to get a point release with Kotlin 1.9.10 support? This is currently blocking our projects from upgrading to Kotlin 1.9.10. Kotlin 1.9.10 has JDK 21 support and we plan on migrating our projects to JDK 21 once Gradle and detekt support it.
I along with the community would be very appreciative if we could get a point release with minimal changes quickly, that will allow us to run our Kotlin 1.9.10 builds with detekt.
Thank you for your support with the last issue https://github.com/detekt/detekt/issues/6278 to release a build to support Kotlin 1.9.0

The Current behavior section reads:

1.23.1 only supports Kotlin 1.9.10

Is that 1.9.10 correct?

The current detekt 1.23.1 only supports Kotlin 1.9.0. Sorry i have corrected the bug. I also found out Kotlin 1.9.10 only supports JDK 20. So the importance of this issue is lower for me at least. Kotlin 1.9.20 should support JDK 21 so once that is released it would be more important. I am more interested in a version of Kotlin that supports JDK 21.

Detekt supports any version of detekt. You can have problems with detekt if your configuration of gradle overwrites the dependencies of detekt. But there is not any good reason to do that. So, in general, you should check your gradle configuration.

Sorry maybe i didnt provide enough information in the original bug.
When i attempt to run Detekt 1.23.1 with kotlin 1.9.10 i receive the following error:
* What went wrong:
Execution failed for task ':gameserver:detekt'.
> detekt was compiled with Kotlin 1.9.0 but is currently running with 1.9.10.
  This is not supported. See https://detekt.dev/docs/gettingstarted/gradle#dependencies for more information.

This is how i am applying detekt as part of a gradle convention plugin in buildSrc
import io.gitlab.arturbosch.detekt.Detekt

/**
 * Kotlin static code analysis using detekt.
 */

plugins {
    id("io.gitlab.arturbosch.detekt")
}

dependencies {
    detektPlugins(libs.detekt)
}

detekt {
    toolVersion = "1.23.1"
    config.setFrom(files(project.rootDir.resolve("config/detekt/config.yml")))
    debug = false
    parallel = false
}

tasks.withType<Detekt> {
    exclude(".*/resources/.*")
    exclude(".*/tmp/.*")
    exclude(".*/build/.*")

    reports {
        xml.required.set(false)
        html.required.set(true)
    }
}

Please see https://github.com/detekt/detekt/issues/6198#issuecomment-1700332653 in the meantime.
Snapshots are also available and are updated to 1.9.10.

@credmond-git would you be able to provide a reproducer as @3flex suggested? We'll be doing a point release with 1.9.10 support in the immediate future anyway

Also have the same problem.

Any news on the issue?

I managed to reproduce, based on some real projects I work with at my job: https://github.com/gb-jairo/detekt6428
In this case, the problem is that:

we use kotlin BOM 1.9.10
the projects have custom detekt rules that depend on detekt-cli to run. detekt-cli has a strict dependency on compiler-embeddable 1.9.0

Running any gradle command gives the following error:
 > Could not resolve org.jetbrains.kotlin:kotlin-compiler-embeddable:{strictly 1.9.0}.
     Required by:
         project : > project :detekt-custom-rules > io.gitlab.arturbosch.detekt:detekt-cli:1.23.1
      > Cannot find a version of 'org.jetbrains.kotlin:kotlin-compiler-embeddable' that satisfies the version constraints:
           Dependency path 'org.example:detekt6428:1.0-SNAPSHOT' --> 'com.example:detekt-custom-rules:1.0' (runtimeElements) --> 'io.gitlab.arturbosch.detekt:detekt-api:1.23.1' (runtimeElements) --> 'org.jetbrains.kotlin:kotlin-compiler-embeddable:1.9.0'
           Constraint path 'org.example:detekt6428:1.0-SNAPSHOT' --> 'com.example:detekt-custom-rules:1.0' (runtimeElements) --> 'org.jetbrains.kotlin:kotlin-bom:1.9.10' (platform-runtime) --> 'org.jetbrains.kotlin:kotlin-compiler-embeddable:1.9.10'
           Dependency path 'org.example:detekt6428:1.0-SNAPSHOT' --> 'com.example:detekt-custom-rules:1.0' (runtimeElements) --> 'io.gitlab.arturbosch.detekt:detekt-cli:1.23.1' (runtimeElements) --> 'org.jetbrains.kotlin:kotlin-compiler-embeddable:{strictly 1.9.0}'

I'm having the same problem, would be awesome to have a new detekt version with Kotlin 1.9.10. Right now because of this problem, we are thinking about removing detekt from our dependencies since we want to upgrade to Kotlin 1.9.10

@gb-jairo your issue is unrelated to the original issue. But in your case, there's no need to depend on detekt-cli in a custom ruleset, so remove that dependency from detekt-custom-rules. You also need to change detekt(project(":detekt-custom-rules")) to detektPlugins(project(":detekt-custom-rules")) in your root build file - detekt custom rules must be added as a plugin, not to the detekt configuration. That allows the build and detekt tasks to work.
@CaiqueCoelho you have the same issue as the original issue, or as gb-jairo? You gave the comment above a thumbs up so I'll assume that my comments your use case too.

Hey @3flex thank you for your quick reply, my problem is related to the original problem.
I want to bump kotlin("plugin.spring") to version "1.9.10", but I'm getting the following error
Execution failed for task ':detekt'.
> detekt was compiled with Kotlin 1.9.0 but is currently running with 1.9.10.
  This is not supported. See https://detekt.dev/docs/gettingstarted/gradle#dependencies for more information.

The following workaround works, but we are afraid of the side effects this may have, the static analysis will run in one version and the code in another. Can you tell us if doing this would have any risks?
configurations.matching { it.name == "detekt" }.all {
    resolutionStrategy.eachDependency {
        if (requested.group == "org.jetbrains.kotlin") {
            useVersion("1.9.0")
        }
    }
}

@CaiqueCoelho please add any comments/questions on that to the original issue:  https://github.com/detekt/detekt/issues/6198

Done https://github.com/detekt/detekt/issues/6198#issuecomment-1781148233

it was indeed bad configuration on the company's projects :facepalm:
fixed with your instructions
thank you and sorry for the unrelated problem

Heads up that we published https://github.com/detekt/detekt/releases/tag/v1.23.2 with support for 1.9.10. Apologize for the delay.
If necessary we can make 1.23.3 with support for Kotlin 1.9.20 just after.

Heads up that we published https://github.com/detekt/detekt/releases/tag/v1.23.2 with support for 1.9.10. Apologize for the delay. If necessary we can make 1.23.3 with support for Kotlin 1.9.20 just after.

👋 hey any plans to support 1.9.20 now as well? :)

👋 hey any plans to support 1.9.20 now as well? :)

I'll prepare a point release with support for 1.9.21 in the near future