Unable to use bonsai elastic search heroku add-on on my wagtail site.

I am trying to use Bonsai for search with django 1.9.7 and Wagtail 1.5.2, but when I try to search or use python manage.py update_index I am getting following error.
`
Traceback:
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/connectionpool.py" in urlopen
578.                                                   chunked=chunked)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/connectionpool.py" in _make_request
351.             self._validate_conn(conn)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/connectionpool.py" in _validate_conn
814.             conn.connect()
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/connection.py" in connect
289.                                     ssl_version=resolved_ssl_version)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/util/ssl_.py" in ssl_wrap_socket
308.         return context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.4/ssl.py" in wrap_socket
365.                          _context=self)
File "/usr/lib/python3.4/ssl.py" in init
601.                     self.do_handshake()
File "/usr/lib/python3.4/ssl.py" in do_handshake
828.             self._sslobj.do_handshake()
During handling of the above exception ([SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)), another exception occurred:
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/elasticsearch/connection/http_urllib3.py" in perform_request
78.             response = self.pool.urlopen(method, url, body, retries=False, headers=self.headers, **kw)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/urllib3/connectionpool.py" in urlopen
604.             raise SSLError(e)
During handling of the above exception ([SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)), another exception occurred:
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/handlers/base.py" in get_response
149.                     response = self.process_exception_by_middleware(e, request)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/handlers/base.py" in get_response
147.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/ratan/mywebsite/search/views.py" in search
27.         search_results = paginator.page(page)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/paginator.py" in page
50.         number = self.validate_number(number)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/paginator.py" in validate_number
39.         if number > self.num_pages:
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/paginator.py" in _get_num_pages
86.             if self.count == 0 and not self.allow_empty_first_page:
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/django/core/paginator.py" in _get_count
72.                 self._count = self.object_list.count()
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/wagtail/wagtailsearch/backends/base.py" in count
144.                 self._count_cache = self._do_count()
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/wagtail/wagtailsearch/backends/elasticsearch.py" in _do_count
402.             body=self._get_es_body(for_count=True),
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/elasticsearch/client/utils.py" in _wrapped
69.             return func(*args, params=params, **kwargs)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/elasticsearch/client/init.py" in count
753.             doc_type, '_count'), params=params, body=body)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/elasticsearch/transport.py" in perform_request
307.                 status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)
File "/home/ratan/Desktop/venv/lib/python3.4/site-packages/elasticsearch/connection/http_urllib3.py" in perform_request
83.             raise SSLError('N/A', str(e), e)
Exception Type: SSLError at /search/
Exception Value: ConnectionError([SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)) caused by: SSLError([SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600))`
I have followed documentation exactly, here are my settings for search backend
`ES_URL = urlparse(os.environ.get('BONSAI_URL'))
WAGTAILSEARCH_BACKENDS = {
'default': {
'BACKEND': 'wagtail.wagtailsearch.backends.elasticsearch',
'URLS': [ES_URL.scheme + '://' + ES_URL.hostname + ':80'],
'INDEX': 'ratansblog',
'TIMEOUT': 5,
}
}
if ES_URL.username:
WAGTAILSEARCH_BACKENDS['default']['KWARGS'] = {"http_auth": ES_URL.username + ':' + ES_URL.password}
`
And I have checked that my cluster is running on elastic search 1.7.

Hi @RatanShreshtha - please use the Wagtail Google group for support queries.

Ok thanks for information
On 13-Jun-2016 2:57 PM, "Matt Westcott"<EMAIL_ADDRESS>wrote:

Hi @RatanShreshtha https://github.com/RatanShreshtha - please use the Wagtail
Google group https://groups.google.com/forum/#!forum/wagtail for
support queries.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/torchbox/wagtail/issues/2707#issuecomment-225531392,
or mute the thread
https://github.com/notifications/unsubscribe/AKTR0n9M_NUcK_EzlIuRMPr3V-Pa4JZLks5qLSKCgaJpZM4I0JDN
.


[Improvement]: Update Netty dependency version in Redis connector

Connector Name
module/redis (Redis)
Suggested improvement
It seems that we observe the following jar conflicts warnings when using redis and http connector together.
'netty-transport-4.1.71.Final.jar' dependency of 'ballerinax/redis' conflict with 'netty-transport-4.1.77.Final.jar' dependency of 'ballerina/http'
                'netty-codec-4.1.71.Final.jar' dependency of 'ballerinax/redis' conflict with 'netty-codec-4.1.77.Final.jar' dependency of 'ballerina/http'
                'netty-resolver-4.1.71.Final.jar' dependency of 'ballerinax/redis' conflict with 'netty-resolver-4.1.77.Final.jar' dependency of 'ballerina/http'
                'netty-buffer-4.1.71.Final.jar' dependency of 'ballerinax/redis' conflict with 'netty-buffer-4.1.77.Final.jar' dependency of 'ballerina/http'
                'netty-handler-4.1.71.Final.jar' dependency of 'ballerinax/redis' conflict with 'netty-handler-4.1.77.Final.jar' dependency of 'ballerina/http'
                'netty-common-4.1.77.Final.jar' dependency of 'ballerina/http' conflict with 'netty-common-4.1.71.Final.jar' dependency of 'ballerinax/redis'
        target/bin/negotiator.jar

The reason is because the http module recently updated its netty version for latest due to security vulnerabilities and the relevant dependencies have been found to be in the previous version in redis . As a current work around we can update the redis version with latest netty version and use in Ballerina version 2201.0.4  .
Related issues
I am trying to do [...] but [...]

Redis connector version 2.2.2 is released to the DEV with the netty version update to v4.1.77.Final

RCA and QA Checklist
RCA

Details

Update the Netty Maven dependency version of the connector from 4.1.71.Final to 4.1.77.Final
While using redis connector and http module together conflicts warnings arises. As ballerina http module recently updated its netty version for the latest due to security vulnerabilities. The relevant dependencies have been found to be in the previous version in Redis. As a current workaround netty version in Ballerina.toml is updated with the latest as in http module
Checklist

[x] StoryPoint/ label added:

[x] ValuePoint/ label added:

[x] Reason/ label added:

[x] Resolution/ label added:

Original PR that introduced the bug:

QA

Automation tests

N/A

E2E smoke tests

N/A

Closing this issue since the Redis connector is released to all environments and verified the above issue


🐞 [Bug]: Node set with additional fee can only be used as dedicated but deploy section shows they are sharable

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?

when a farmer set additional fees on a node

then it can only be rented as dedicated
but it still can be found on the dashboard deploy section and we can try to deploy on it but it never works

solution

make sure node set with additional fees is not shown in the dashboard section as being deployable as a shared node

Steps To Reproduce
No response
which network/s did you face the problem on?
Main
version
latest
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records
none
Relevant log output
none

Whilst this should be protected and enforced by the tfchain, we can filter it out from the client side

This issue will be fixed once https://github.com/threefoldtech/tfgrid-sdk-go/issues/1023 is deployed

I can't add any additional fee anymore to an offline or even online node.
screen-capture (15).webm
Note that the values are saved on the form, but if I refresh, it goes away; it doesn't save on the gridproxy or the tfchain.
dashboard (6).log

that happens as your node has node contracts, @A-Harby please open an issue to make the error message more clear.

Verified, Devnet 9d671ca.
I opened a separate issue for the error message: https://github.com/threefoldtech/tfgrid-sdk-ts/issues/2937.
For the node I had a fake node 72, which was shared and after adding the addition fee the status of the node changed to dedicated.

screen-capture (16).webm
TC2443 - Set Fee


Properly implement HTTP 503 error

Problem:
Response Status Code 503 does not indicate a faulty request but that the api server is currently not available. From documentation: 503 | The server is not available (maintenance work)
Approach 1: The user needs to get a result that indicates that the server is (currently) not available. (can be done right now, when throw-style is used via constructor)
Approach 2: The failed request should be reexecuted some time later. If that fails again, then the user gets to see the error.

Basically I believe we should forward the error directly (meaning approach 1) and not take care of error handling / resume-on-error behaviour in the wrapper. IMO this should be handled by the application using bexio.net.
So I would vote for Approach 1


Updated validations.py Python script

Fixes #1

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

I have fixed everything


DepthAnything example for the web and without any servers...

Hi!
I just wanted to take a moment to thank you for the fantastic repository and model. I’ve been experimenting with DepthAnything and have developed a browser-based implementation of it, powered by ONNX.
You can check it out here:
Github Repo: https://github.com/akbartus/DepthAnything-on-Browser
Interactive Demo: https://depthanything.glitch.me/
Feel free to share it on your page if you think it might be of interest!

Hi @akbartus, thank you very much for your contribution! I will add this to our README in the next update.

Thank you. Feel free to close the issue.

That's a nice tool! Which metric model are you running? It would also be nice to be able to pass the focal length as a parameter instead of using a fixed fov of 45.

That's a nice tool! Which metric model are you running? It would also be nice to be able to pass the focal length as a parameter instead of using a fixed fov of 45.

@NikolasE thanks for the feedback. In the example it is small quantized model. Will update example to include interactive sliders for FOV and others.

@NikolasE created example with sliders, you can check it here: https://depthanything.glitch.me/webgpu-sliders.html but for DepthAnything v2 already. Updated repo accordingly.


contact diary: use already existing code on github

It seems to me that this subject is worth its own issue. I just learnt that the app kontakt-tagebuch was removed from the App story. I really don't want to comment on this (unwise) decision by apple to remove a free app that helps to fight the pandemic, I merely want to point out that the apps' developer, Stefan Traut, generously has made his code public under the MIT license on github download link could that code (save its access to the contact list) included in the Corona Warn app. I, unfortunately, don't know enough swift to judge.
regards
Uwe Brauer

Internal Tracking ID: EXPOSUREAPP-3034

Just to ensure that I understand you correctly:
You want to add the whole "Kontakt-Tagebuch"-app go get added to CWA?
This is not that simple as it sounds, the integration maybe would not be the big part, but the UI would have to be adapted to the CWA UI.
Leave this Issue open since this is the wishlist, but this seems very unrealistic to me.
I think it would be better if you open new Issues which requests features from this App. (Take a look at #310) 👍

Just to ensure that I understand you correctly:
You want to add the whole "Kontakt-Tagebuch"-app go get added to CWA?
This is not that simple as it sounds, the integration maybe would not be the big part, but the UI would have to be adapted to the CWA UI.
Leave this Issue open since this is the wishlist, but this seems very unrealistic to me.
I think it would be better if you open new Issues which requests features from this App. (Take a look at #310) 👍

"ET" == Ein Tim<EMAIL_ADDRESS>writes:

Just to ensure that I understand you correctly:

You want to add the whole "Kontakt-Tagebuch"-app go get added to CWA?

yes, save the contact list feature which is controversial as I understand.

This is not that simple as it sounds, the integration maybe would not
be the big part, but the UI would have to be adapted to the CWA UI.

Maybe one could link both  apps?
For example if you export information of a specific app, the share
functionality allows you either to use Apple's own apps like mail, but
although 3rd party apps. So,  maybe for this specific purpose, that would be
possible to, so the button, add contacts would open that app?

Leave this Issue open since this is the wishlist, but this seems very
unrealistic to me.

I think it would be better if you open new Issues which requests
features from this App. (Take a look at #310) 👍

I did, it looks a bit like reinvent the wheel again.

"ET" == Ein Tim<EMAIL_ADDRESS>writes:

Just to ensure that I understand you correctly:

You want to add the whole "Kontakt-Tagebuch"-app go get added to CWA?

yes, save the contact list feature which is controversial as I understand.

This is not that simple as it sounds, the integration maybe would not
be the big part, but the UI would have to be adapted to the CWA UI.

Maybe one could link both  apps?
For example if you export information of a specific app, the share
functionality allows you either to use Apple's own apps like mail, but
although 3rd party apps. So,  maybe for this specific purpose, that would be
possible to, so the button, add contacts would open that app?

Leave this Issue open since this is the wishlist, but this seems very
unrealistic to me.

I think it would be better if you open new Issues which requests
features from this App. (Take a look at #310) 👍

I did, it looks a bit like reinvent the wheel again.


[feat] Load Apibara script values from the environment

Using Deno.env.get, load hostname, indexer and backend ports from environment variables in the Apibara scripts.
Then combine docker-script.js and script.js indexer scripts.
References

Apibara scripts
Apibara docs

@b-j-roberts  may i be assigned to this issue? I have never worked on anything related to Apibara it could be a good start!

For sure, @TAdev0 could be a good issue to get an idea of what it's doing. Let me know if you have questions.


[Question] Is it in a working state yet?

Am planning on writing a Scala wrapper around this and using that to make an IntelliJ plugin for Rich Presence, is this lib working fully yet?

I am still working on fine tuning and documentation, but it already works for Win64, Win32 and Unix64


Test Issue created at Tue, 16 Mar 2021 09:01:05 GMT

Test issue body  Tue, 16 Mar 2021 09:01:05 GMT

Comment on issue at Tue, 16 Mar 2021 09:01:09 GMT


Add a function to get the current cursor shape.

Godot version:
3.1+
OS/device including version:
All systems
Issue description:
There should be a function to get the current mouse cursor shape. I assume it should be on the OS singleton, but Input also deals with setting the cursor, so it might make more sense there.
The reason I want this is because I want to create a custom cursor for my game, but I want it to have animation, resizing, and other effects. So I can't just set a custom cursor image, I need to hide the cursor and use a Sprite as a cursor substitute. I still want to use the cursor shapes from GUI nodes to change my custom cursor though, but there's no function that gets the current shape of the cursor.

CC @guilhermefelipecgs


Implement additional similarity measures

[x] n-grams
[x] regular expressions
[x] glob patterns
[x] taxonomies
[x] timelines swa
[x] timelines dtw

All of the above are implemented now, if similarity measures are missing feel free to open a new issue or start a discussion.


Feature slim 882 generate and replace keys

SLIM-882

This pull request makes the build fail.

All is well.

retest this please

This pull request makes the build fail.


setup.sh: Support XDG_DATA_DIRS (bash completion in nix-shell)

Motivation for this change
Add bash completion support for packages in nix-shells.
Closes #26031
XDG_DATA_DIRS is to /share as PATH is to /bin.
It was defined as part of the XDG basedir specification.
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
While it originated from the X Desktop Group, it is not limited to
the X11 ecosystem, as evidenced by its use in bash-completion.
TODO

[x] one more test locally
[x] check buildInputs vs nativeBuildInputs behavior (not expecting any surprises though)

~either of which works with bash completion because strictDeps is disabled~
[x] buildInputs should not be loaded because those will be for the wrong system

[ ] test a significant portion of Nixpkgs builds

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

While I think this is a good idea, I just wanted to note something similar was previously discussed in https://github.com/NixOS/nix/pull/2443 and @edolstra had some objections. It may be less controversial in Nixpkgs though since we rely on XDG_DATA_DIRS in a lot of places already.

Ok, XDG_DATA_DIRS now follows strictDeps-like behavior. No mixing with cross-compilation outputs will occur.
(If some hypothetical build saves XDG_DATA_DIRS, that's equivalent to saving the builder's PATH; just one out of a thousand potential bad build ideas)
Also XDG_DATA_DIRS is now always exported as one will expect it to. Previous behavior was potentially confusing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/setup-bash-completion-when-running-under-nix-shell-on-macosx/5216/6

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/shell-nix-load-completions/8803/15

My understanding is that only nativeBuildInputs have shell completion from this, however, most examples use buildInputs.
nix manual: https://nixos.org/manual/nix/unstable/command-ref/nix-shell.html
wiki: https://nixos.wiki/wiki/Development_environment_with_nix-shell
wiki / cachix: https://nixos.wiki/wiki/Caching_nix_shell_build_inputs
I don't think this is a blocker, but we should probably update the documentation examples so that people get expected behavior

My understanding is that only nativeBuildInputs have shell completion from this, however, most examples use buildInputs.

That is correct. buildInputs shouldn't be loaded on PATH either. That is a legacy behavior.
The idea is that XDG_DATA_DIRS supports apps that run in the "current" context, build in our cross compilation terminology. buildInputs can, in general, only run in the host context. Loading these by default will cause issues with cross compilation.
This change does affect all derivations after all, for better or for worse. I'm hopeful but this needs testing.
Speaking of testing, on non-cross we should probably change or unset XDG_DATA_DIRS during checkPhase and installCheckPhase.

I don't think this is a blocker, but we should probably update the documentation examples so that people get expected behavior

:100:. Should have been done with the introduction of cross compilation.

@jonringer Yeah, we've never found a sane way to flip the strictDeps switch without breaking the world. This PR to me says "fine, but new functionality can be effectively be strictDeps-style". I think this is a rather clever way to "nudge not shove" the ecosystem in the right direction --- nothing will be broken, per se, but the incentive to switch will compound over time.
I like it a lot!

One thing I didn't understand is; what kind of black magic auto-loads the completion? Is it part of bash itself to look for those files?
Incidentally, I recently worked on unifying the bash completions outputs: https://github.com/NixOS/nixpkgs/pull/103421

@zimbatm

One thing I didn't understand is; what kind of black magic auto-loads the completion? Is it part of bash itself to look for those files?

No black magic, just a shell script in the bash-completion package.
https://github.com/scop/bash-completion/blob/f7475cf2c0d60f690a0bd758e3fa84976017b99a/bash_completion#L2185-L2187

Incidentally, I recently worked on unifying the bash completions outputs: #103421

That's great!

Fixed up the first commit to unset the "private" _XDG_DATA_DIRS (note the underscore)
Tested build and execution of

gnome3.eog
konsole (KDE)

Speaking of testing, on non-cross we should probably change or unset XDG_DATA_DIRS during checkPhase and installCheckPhase.

We don't do this for PATH either, so let's keep it simple.
Another reason not to automagically change it for the check phases is that we want the package author to figure out that the data dependency exists, so that they are aware that XDG_DATA_DIRS must be set when the package is used.

@GrahamcOfBorg eval

wiki: https://nixos.wiki/wiki/Development_environment_with_nix-shell
wiki / cachix: https://nixos.wiki/wiki/Caching_nix_shell_build_inputs

BTW I just updated those to use nativeBuildInputs where appropriate. Perhaps is a hoop users won't choose to jump through, and that's fine, but at least those docs won't be misleading them.

Any objections to testing this on staging?


[r] Seurat <> SOMA Integration Improvements

Improved messaging for to_seurat()

Silence unnecessary warnings for default arguments
Silence duplicate warnings emitted by to_seurat() and downstream methods

Improve messaging about ingesting extended assays

write_soma.Seurat() now returns the URI instead of the experiment to be more inline with Python

Quick thought:  Can you show 'before' vs 'after' examples?

Codecov Report
Patch coverage has no change and project coverage change: -37.09 :warning:

Comparison is base (f9d6d56) 91.01% compared to head (03932a2) 53.93%.

:exclamation: Current head 03932a2 differs from pull request most recent head b2e3ad8. Consider uploading reports for the commit b2e3ad8 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1305       +/-   ##
===========================================
- Coverage   91.01%   53.93%   -37.09%
===========================================
  Files          30       67       +37
  Lines        2416     5364     +2948
===========================================
+ Hits         2199     2893      +694
- Misses        217     2471     +2254

Flag
Coverage Δ

python
?

r
53.93% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 97 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Right, sorry. Currently outgestion with query$to_seurat() emits warnings using default values:
> exp <- SOMAExperimentOpen(
+   "s3://tiledb-paulhoffman/pbmc3k-raw",
+   tiledbsoma_ctx = SOMATileDBContext$new(c(soma.init_buffer_bytes = "45000000"))
+ )
> query <- SOMAExperimentAxisQuery$new(exp, "RNA")
> obj <- query$to_seurat(c(data = "data"))
Warning: No reductions found
Warning: No graphs found in 'obsp'

After this patch, outgestion with query$to_seurat() no longer emits these warnings when using the default values
Messaging about extended assays during ingestion from Seurat currently is as follows
> library(Seurat)
> library(SeuratData)
> pbmc3k <- UpdateSeuratObject(LoadData("pbmc3k"))
> pbmc3k <- SCTransform(pbmc3k)
> class(pbmc3k[["RNA"]])
[1] "Assay"
attr(,"package")
[1] "SeuratObject"
> class(pbmc3k[["SCT"]])
[1] "SCTAssay"
attr(,"package")
[1] "Seurat"
> write_soma(pbmc3k, file.path(tempdir(), "pbmc3k-sct"))
Warning: Extended assays (eg. SCTAssay) cannot be written
to SOMAs at this time

Which isn't entirely correct. We can write out the standard parts of a Seurat Assay, just not the extended bits. After this patch, the warning is now:
Warning: Extended assays (eg. SCTAssay) are not fully
supported; core Assay data has been written but
additional slots have been skipped


ppc64le: kata-env fails due to missing vendor field

There is no vendor field in /proc/cpuinfo contents
on ppc64le. Make sure the check is only for
arm and amd64.
Fixes: #864
Signed-off-by: Nitesh Konkar<EMAIL_ADDRESS>

@jodh-intel @marcov: Fixed Travis ppc job.

Can someone please start the Jenkins CI job.

/test

/retest

Is the failure in CI due to the warnings of func genericTestGetCPUDetails and func genericGetExpectedHostDetails being unused? I see arm64 defining its own
TestGetCPUDetails as well.

@grahamwhaley : Okay. Also is it okay to put arch specific checks in genericTestGetCPUDetails (I guess no) ?
So the only option is to have a ppc64le specific TestGetCPUDetails and not call genericTestGetCPUDetails and not get a warning as well.

/me pulls in @jodh-intel @sboeuf - afaik we tend to put arch code into arch postfixed source files (which go understands), like https://github.com/kata-containers/runtime/blob/master/cli/kata-check_amd64.go
We don't normally use golang build constraints afaik.

Yup, that's why I put the code in cli/kata-check_ppc64le_test.go in this PR.

Yup, that's why I put the code in cli/kata-check_ppc64le_test.go in this PR.

@nitkon, I see the code for the ppc and generic functions is exactly the same, apart from few variables values, so it's worth doing some refactoring and keep calling the generic functions from the ppc specific code.
You just need to do adapt the generic functions to accept some extra arguments:
the func genericTestGetCPUDetails(t *testing.T, vendorname string, data testdata)
func genericGetExpectedHostDetails(tmpdir string, cpuVendor string) (HostInfo, error)

The Travis-CI build is now passing. Can someone run the jenkins-ci-ubuntu for me? Thanks.

/test

CI failing because of
latest: Pulling from library/fedora
d0483bd5a554: Pulling fs layer

Stderr: error pulling image configuration: unknown blob

--- FAIL: TestIntegration (12.75s)
    main_test.go:60: failed to pull docker image: fedora
FAIL

network issue? /retest ?

/retest

Some of the test failures I am seeing are due to the following:
Stderr:
Running command '/usr/bin/docker [docker pull fedora]'
command failed error 'exit status 1'
[docker pull fedora]
Timeout: 600 seconds
Exit Code: 1
Stdout: Using default tag: latest

Stderr: Error response from daemon: unauthorized: authentication required

--- FAIL: TestIntegration (12.34s)
    main_test.go:60: failed to pull docker image: fedora
FAIL

Not sure if the CI is broken or its a network issue.

The jenkins are failing due to the following:
14:15:11 ERROR: Found unexpected /usr/libexec/kata-containers/kata-proxy present
14:15:12
14:15:12 ===== starting test [memory footprint inside container] =====
14:15:12 command: docker: yes
14:15:12 11189
14:15:12 ERROR: Found unexpected /usr/libexec/kata-containers/kata-proxy present
14:15:12 Executing test: boot times image=ubuntu runtime=kata-runtime units=seconds
14:15:12 command: bc: yes
14:15:12 command: awk: yes
14:15:12
14:15:12 ===== starting test [boot times] =====
14:15:12 command: docker: yes
14:15:13 11189
14:15:13 ERROR: Found unexpected /usr/libexec/kata-containers/kata-proxy present
14:15:13
14:15:13 ===== starting test [blogbench] =====
14:15:13 command: docker: yes
14:15:13 11189
14:15:13 ERROR: Found unexpected /usr/libexec/kata-containers/kata-proxy present
14:15:13 11189
14:15:14 ERROR: Found unexpected /usr/libexec/kata-containers/kata-proxy present
14:15:14 ~/workspace/workspace/kata-metrics-runtime-ubuntu-16-04-PR/go/src/github.com/kata-containers/tests
14:15:14 ~/workspace/workspace/kata-metrics-runtime-ubuntu-16-04-PR/go/src/github.com/kata-containers/tests/cmd/checkmetrics ~/workspace/workspace/kata-metrics-runtime-ubuntu-16-04-PR/go/src/github.com/kata-containers/tests

@marcov : Can you restart the jobs, probably. Also these don't have a "Required" tag. Does it signify that it not required for a PR to be reviewed/merged .

Restarting one more time. About the Required tag, I am not sure what's the usual way to interpret it in this repo.

Thank you! Looks all green now. @marcov @grahamwhaley @jodh-intel

Added dnm to avoid inadvertent merging - see my comments.

Jenkins needs to be started?

/test

jenkins-ci-fedora-27 is failing because of
" name=kata-proxy pid=32201 sandbox=38c5dbd446d132839f003a7ae401460fb3da53e218567b391c3ad09532f6c549 source=agent
time="2018-11-27T16:00:16.387115726Z" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/b14c1466ee90361ee323721049456add4219a45c70dca95fae184fb239f2d803/kata.sock: use of closed network connection"

Manually restarting just that test would probably help.

lgtm


drivers: add support of pwm capture driver

Summary

add lower half support of capture for stm32_capture, because there's no external interface for device driver in stm32_capture.c;
add support of pwm input capture driver in drivers/timers;
add setup of pwm capture device on stm32f4discovery board, for pwm input capture test;

Impact
stm32 timers and capture
Testing
Tested on custom board based on stm32f405 and stm32f4discovery board, the duty and frequence measurement result is correct.

Very nice @zouboan !!! Are you planing to add an app/ example to use /dev/capture0 ? Is it able to read PWM pulse used to control servo motors? I'm thinking about connecting a PWM signal from a RC receiver (i.e. I have a FrSky TFR6) and show the joystick position on NuttX

Ok，i will add a capture example in apps
---Original---
From: "Alan Carvalho de @.>
Date: Tue, Jun 28, 2022 07:10 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [apache/incubator-nuttx] drivers: add support of pwm capture driver (PR #6525)
Very nice @zouboan !!! Are you planing to add an app/ example to use /dev/capture0 ? Is it able to read PWM pulse used to control servo motors? I'm thinking about connecting a PWM signal from a RC receiver (i.e. I have a FrSky TFR6) and show the joystick position on NuttX
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Clicking "upload all" on an empty "offline edit" list proposes to send the list

Clicking "upload all" on an empty "offline edit" list proposes to send the list.
In that case, it should be turned into a Scan product button.

It seems that @naofum fixed it. Closing.


sphinxcontrib-devhelp: init at 1.0.1

Motivation for this change
build dependency of sphinx 2.2.0
Things done

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

[X] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @

since this is a part of #71601 , do you mind if i close all these smaller namespace pacakges and just track the issues in #71601

since this is a part of #71601 , do you mind if i close all these smaller namespace packages and just track the issues in #71601

whatever looks cleaner on git log - i reworked the commit messages for the individual PRs to fit the required format, so merging the individual PRs would be a bit more beautiful than doing it all in #71601

right, but not of them really have tests, but that's okay if sphinx exercises those code paths, its just that a series of fragmented PRs are a little harder to track, not to mention that they are all highly aligned to bumping sphinx

I deactivated the tests as they depend on sphinx. I'm pretty new to Nix, but in BitBake i would have made dependencies on the build stages on the packages (so sphinx would be built in between build of the sphinxcontrib-packages and test of the sphinxcontrib-packages). Any way to express this in Nix?

nix resolves the dependency graph into a direct-acyclic graph, so there's no way to have cycles. It's a known issue: https://github.com/NixOS/nixpkgs/issues/63168

you could technically do an override and pass whether or not you want to the dependencies to test themselves, but AFAIK this is discouraged as you get a lot of one-off derivations

nix resolves the dependency graph into a direct-acyclic graph, so there's no way to have cycles. It's a known issue: #63168

Yes. That would need some way of snapshotting the derivations before running the tests, building sphinx and then running the tests from the snapshots. The derivations should not be influences by the test results. The important thing is that postponing the tests needs to be triggered by a nix expression so that the derivation does not change.

superseded by https://github.com/NixOS/nixpkgs/pull/71601


Setting PDO Fetch mode to FETCH_CLASS

Library would not work with connections with non-default fetch modes (e.g. FETCH_ASSOC), so we set it explicitly.

@guntars, thank you for the PR. I will add the setFetchMode() code to Manager.php since it is the source for the connection in Controller.php code. That way all uses of connection will be fixed.

@guntars, on my system setFetchMode() causes a run-time error of method not found.
I am adding a config setting:
    /**
     * Enable manually setting PDO fetch mode when it is not the default
     *
     * Only applies to connections that support setFetchMode() method
     *
     * If not defined then connection's default fetch mode will be used
     *
     * @type boolean
     */
    'pdo_fetch_mode_enabled' => false,

if this is set to true then your solution of setting fetch mode code will be run. That way it only applies to those that need it. A bit hacky but it solves the problem.
I am going to make a release with this change. I cannot test it so please let me know if it solves the problem on your setup.

@guntars, solution released. Please add the above setting to your LTM config file.

@vsch, thank you for a prompt fix and the great tool in general! My fault that I forgot to mention that I'm still on Laravel 5.3 and the issue is related to this version and below. I checked 5.4 and there "setFetchMode" indeeed has been removed, and there is a comment on that in Upgrade Guide, section "Fetch Mode" (https://laravel.com/docs/5.4/upgrade). Long story short, from 5.4 it is always FETCH_OBJ unless you override it in an event listener. I have no idea how to configure it for a case when two fetch modes are used for different libs.
Btw, the solution can be shortened a bit, by checking method_exists($connection, 'setFetchMode') at runtime, no need for a config var.

@guntars, I'll roll back the changes on 5.4 branch and make patch release for 5.3 version with your shortened solution.

@guntars, created a branch Laravel-5.3 and made the changes.
Use "vsch/laravel-translation-manager": "~2.3" for Laravel 5.3 compatibility.

@vsch, great, thank you very much!


[breaking change]: Deprecation and discontinuation of standalone Dart tools

Background
Historically the Dart team has offered a number of smaller developer tools for things like formatting code (dartfmt), analyzing code (dartanalyzer), etc. In Dart 2.10 (October 2020) we introduced a new unified Dart developer tool, the dart tool.
Intended change
As we discussed at launch in the blog post, we plan to first deprecate and then discontinue the smaller tools in favor of the new combined tool. The this meta-bug presents an overview of the status of this migration. As this is considered breaking, it will happen in a staged fashion over time, when each individual tool first becoming deprecated in one stable release (here it will still exist but print a warning), and then fully discontinued (here it will no longer be in the SDK).

Historical tool
dart replacement
Deprecation
Discontinuation

stagehand
dart create
2.14
✅ 2.14*

dartfmt
dart format
2.14
✅ 2.15

dart2native
dart compile exe
2.14
✅ 2.15

dart2js
dart compile js
2.17
2.18

dartdevc
none
2.17
2.18

dartanalyzer & package:analyzer_cli
dart analyze
2.16
2.18

dartdoc
dart doc
2.16
✅ 2.17

pub
dart pub
2.15
✅ 2.17

Notes:

We currently have no plans to deprecate dartaotruntime.
stagehand will go directly to discontinuation as it's a pub global tool on pub.dev, and not a SDK distributed tool like the rest. This means it can still be invoked (with dart pub global run stagehand) even after it's been discontinued.
dartdevc will be discontinued as a publicly visible tool. The tool was never intended or supported as a stable command line tool for end users. The underlying binary for this compiler will still be shipped with the SDK to be used by build systems tools (such as bazel, webdev, and flutter_tools). However, it will no longer be exposed to be used by developers directly on the command line.

Rationale
With the new unified tool the existing tools are no longer needed. To reduce maintenance, remove confusion for new users, and to ensure we offer a single high-quality toolset the old commands are being removed.
Should you have any issues with missing functionality in the new dart-based tools, please file an issue.
Migration
To migrate, switch to using the dart tool, and the subcommands listed in the above table.

I can begin switching the flutter usages of the packages with specified deprecation dates. For some of these, it seems like there is still a significant gap in functionality (analysis server usage with dart analyze, or the various compile options for dart2js). Is there a plan to resolve this before announcing deprecation dates?

... significant gap in functionality (... various compile options for dart2js)

I can at least speak for the dart2js side, yes. We will ensure there isn't any gap in our case. It's very likely that we'll even preserve all existing flags, but we'll confirm once the plan is finalized.

The items marked as deprecated in 2.14 in the table are considered "feature complete" and we're not aware of any things missing from them.
For dart analyze it's fairly complete, and we'd like to hear more input on what might be missing. We've migrated a bunch of uses of dartanalyzer in various Dart repos already.

what is the replacement for the web-angular which is in now in stagehand?

As angular-dart is also being discontinued, most probably dart create will not include web-angular template. But Is the google team planning to release a separate CLI tool for angular-dart or there are other existing alternatives?

stagehand will continue to work as today; it just won't see any future work -- so that can still be used to create web-angular projects.

@mit-mit I'm thinking of functionality like the lsp mode that the analysis server supports, unless that snapshot won't be removed.

The analysis server snapshot won't be going anywhere any time soon since we don't have a replacement for it in the CLI.

ack, I actually forgot about dartanalyzer, but that one makes more sense 😅

As of this CL, dartfmt is now printing a deprecation notice.

In the 2.16 release notice, it was mentioned that the standalone dartdoc command is going away in 2.17.
I'm currently using the options --rel-canonical-prefix and --link-to-source-revision when invoking dartdoc. dart doc doesn't appear to accept those options, what's the replacement for them?

As discussed in various meetings, support for analyzing the Dart SDK core libraries doesn't seem to be available with the new command form.  From the command line, currently:
xcodebuild/ReleaseX64/dart-sdk/bin/dartanalyzer  --dart-sdk=/Users/leafp/src/dart-repo/sdk/sdk --sdk-warnings  /Users/leafp/src/dart-repo/sdk/sdk/lib/

works but the corresponding dart analyze command does not.

I'm currently using the options --rel-canonical-prefix and --link-to-source-revision when invoking dartdoc. dart doc doesn't appear to accept those options, what's the replacement for them?

To anyone else also stumbling across this, my solution was to add a dev_dependency on dartdoc and then use dart run dartdoc instead of the more limited dart doc command.

@simolus3 - can you open an issue against https://github.com/dart-lang/dartdoc for the dartdoc CLI flags you're missing? And, have you tried configuring dartdoc via the dartdoc_options.yaml file (https://github.com/dart-lang/dartdoc#dartdoc_optionsyaml)? That allows you to tweak more parameters than are available through dart doc.

@jakemac53 - yes, the goal is still to support their use from build_web_compilers. For now we intend to keep the snapshots, but there have been discussions about combining the snapshots into the CLI snapshot sometime in the future (but that's not a short term goal).
To avoid the warning, using dart compile js will work (that will also be safe in the future if dart2js gets merged into the Dart CLI). Alternatively, we can also pass a special flag to the dart2js snapshot to indicate that you are one of the use cases we support (that was our intended design at first).
As for DDC, the snapshot will remain available for foreseeable future. Note that DDC should not give you a warning if you are using the snapshot (only the shell script does today).

Thanks, I will go ahead and land the change to  use dart compile js and leave the rest as is for now. So you should be unblocked soon to merge the snapshot with the CLI snapshot when you are able, that should probably help sdk size a fair bit :).


Make sure HostCollectiveId is set for Organizations

Resolve https://github.com/opencollective/opencollective/issues/6616
add-funds.webm

Assumptions needs to be rechecked.

Yes, my mistake. I was under the impression that after making a host one should be able to add funds. But it seems that only after activating the budget the host is able to add funds and receive financial contributions etc.


Getting "Scan failed because feature unsupported (code 8)" when calling startDeviceScan() for Android devices

Expected Behavior
Scan BLE peripherals with startDeviceScan()
Current Behavior
Runs for IOS, but returns "Scan failed because feature unsupported (code 8)" for Android.
Error message:
{"message":"Cannot start scanning operation","errorCode":600,"attErrorCode":null,"iosErrorCode":null,"androidErrorCode":null,"reason":"Scan failed because feature unsupported (code 8)","name":"BleError"}

Steps to Reproduce
Please provide detailed steps for reproducing the issue.

step 1
step 2
...

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions. Both JS and platform logs can be enabled via setLogLevel function call.

react: 17.0.2
react-native: 0.67.3
react-native-ble-plx: 2.0.3
Platform: Android/iOS.
Android Device: Pixel 2, Android 12 (API 31)

bleManager.startDeviceScan(null,
      {
        scanMode: ScanMode.LowLatency,
        callbackType: ScanCallbackType.FirstMatch,
      },
      async (error, device) => {
        if (error) {
          this.bleManager.stopDeviceScan();
          console.error('error scanning');
          console.log(JSON.stringify(error));
          rejectDevicePromise(error);
          return;
        }
        if (device?.localName === this.peripLocalName) { ... }

same issue, what's any solution? please

This is the error on the android side: https://developer.android.com/reference/android/bluetooth/le/ScanCallback#SCAN_FAILED_FEATURE_UNSUPPORTED
Most likely, the device has a problem with ScanMode.LowLatency. I tried to reproduce this problem on a phone with the same SoC but I didn’t find any problems. Could you confirm the issue after updating the package?


Bundling sometimes fails on JRuby

If I bundle Gemstash from MRI, creating a Gemfile.lock and then switch to JRuby, bundling with missing gems fails with the following error:
Could not find gem 'gemstash (>= 0) ruby' in source at ..
Source contains 'gemstash' at: 0.1.0

Doing the reverse works fine. (see the shell session at the bottom to see a full example of the problem)
The Gemfile simply points to the gemspec:
source "https://rubygems.org"

# Specify your gem's dependencies in gemstash.gemspec
gemspec

I suspect the key to the problem may be how I specified the platform:
  spec.platform      = "java" if RUBY_PLATFORM == "java"

Which produces this in my lock on MRI:
PATH
  remote: .
  specs:
    gemstash (0.1.0)
...

And this in JRuby:
PATH
  remote: .
  specs:
    gemstash (0.1.0-java)
...

I am using MRI 2.2.2 and JRuby <IP_ADDRESS>.
Example shell session illustrating the problem:
$ rvm use 2.2.2
Using ~/.rvm/gems/ruby-2.2.2
$ rm Gemfile.lock
$ bundle
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using rake 10.4.2
Using ast 2.1.0
Using parser <IP_ADDRESS>
Using astrolabe 1.3.1
Using bundler 1.10.6
Using dalli 2.7.4
Using diff-lcs 1.2.5
Using multipart-post 2.0.0
Using faraday 0.9.2
Using faraday_middleware 0.10.0
Using lru_redux 1.1.0
Using puma 2.15.3
Using sequel 4.28.0
Using rack 1.6.4
Using rack-protection 1.5.3
Using tilt 2.0.1
Using sinatra 1.4.6
Using sqlite3 1.3.11
Using thor 0.19.1
Using gemstash 0.1.0 from source at .
Using powerpack 0.1.1
Using rack-test 0.6.3
Using rainbow 2.0.0
Using rspec-support 3.3.0
Using rspec-core 3.3.2
Using rspec-expectations 3.3.1
Using rspec-mocks 3.3.2
Using rspec 3.3.0
Using ruby-progressbar 1.7.5
Using tins 1.6.0
Using rubocop 0.35.1
Bundle complete! 6 Gemfile dependencies, 31 gems now installed.

Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Could not find gem 'gemstash (>= 0) ruby' in source at ..
Source contains 'gemstash' at: 0.1.0
$ rm Gemfile.lock
$ bundle
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies....................
Using rake 10.4.2
Using ast 2.1.0
Using parser <IP_ADDRESS>
Using astrolabe 1.3.1
Using bundler 1.10.6
Installing dalli 2.7.4
Using diff-lcs 1.2.5
Using multipart-post 2.0.0
Using faraday 0.9.2
Using faraday_middleware 0.10.0
Using jdbc-sqlite3 <IP_ADDRESS>
Using lru_redux 1.1.0
Using puma 2.15.3
Using sequel 4.28.0
Using rack 1.6.4
Using rack-protection 1.5.3
Using tilt 2.0.1
Using sinatra 1.4.6
Using thor 0.19.1
Using gemstash 0.1.0 from source at .
Using powerpack 0.1.1
Using rack-test 0.6.3
Using rainbow 2.0.0
Using rspec-support 3.3.0
Using rspec-core 3.3.2
Using rspec-expectations 3.3.1
Using rspec-mocks 3.3.2
Using rspec 3.3.0
Using ruby-progressbar 1.7.5
Using tins 1.6.0
Using rubocop 0.35.1
Bundle complete! 6 Gemfile dependencies, 31 gems now installed.

Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using rake 10.4.2
Using ast 2.1.0
Using parser <IP_ADDRESS>
Using astrolabe 1.3.1
Using bundler 1.10.6
Installing dalli 2.7.4
Using diff-lcs 1.2.5
Using multipart-post 2.0.0
Using faraday 0.9.2
Using faraday_middleware 0.10.0
Using jdbc-sqlite3 <IP_ADDRESS>
Using lru_redux 1.1.0
Using puma 2.15.3
Using sequel 4.28.0
Using rack 1.6.4
Using rack-protection 1.5.3
Using tilt 2.0.1
Using sinatra 1.4.6
Using thor 0.19.1
Using gemstash 0.1.0 from source at .
Using powerpack 0.1.1
Using rack-test 0.6.3
Using rainbow 2.0.0
Using rspec-support 3.3.0
Using rspec-core 3.3.2
Using rspec-expectations 3.3.1
Using rspec-mocks 3.3.2
Using rspec 3.3.0
Using ruby-progressbar 1.7.5
Using tins 1.6.0
Using rubocop 0.35.1
Bundle complete! 6 Gemfile dependencies, 31 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
$ rvm use 2.2.2
Using ~/.rvm/gems/ruby-2.2.2
$ gem uninstall dalli
Successfully uninstalled dalli-2.7.4
$ bundle
Fetching gem metadata from https://rubygems.org/.........
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies...
Using rake 10.4.2
Using ast 2.1.0
Using parser <IP_ADDRESS>
Using astrolabe 1.3.1
Using bundler 1.10.6
Installing dalli 2.7.4
Using diff-lcs 1.2.5
Using multipart-post 2.0.0
Using faraday 0.9.2
Using faraday_middleware 0.10.0
Using lru_redux 1.1.0
Using puma 2.15.3
Using sequel 4.28.0
Using rack 1.6.4
Using rack-protection 1.5.3
Using tilt 2.0.1
Using sinatra 1.4.6
Using sqlite3 1.3.11
Using thor 0.19.1
Using gemstash 0.1.0 from source at .
Using powerpack 0.1.1
Using rack-test 0.6.3
Using rainbow 2.0.0
Using rspec-support 3.3.0
Using rspec-core 3.3.2
Using rspec-expectations 3.3.1
Using rspec-mocks 3.3.2
Using rspec 3.3.0
Using ruby-progressbar 1.7.5
Using tins 1.6.0
Using rubocop 0.35.1
Bundle complete! 6 Gemfile dependencies, 31 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

The same failure happens for JRuby 1.7.22 as well

I created a simple gem called example to replicate this issue with just a single dependency. Then I started digging into the issue, and I found some insights into the problem, but I don't really know Bundler code, so I'm not sure what direction to take the fix.
lib/bundler/definition.rb seems to be where the Gemfile.lock and Gemfile are loaded and checked for updates and whatnot.
This code then goes on to construct the Bundler::Resolver which ultimately checks the dependencies and attempts to resolve them:
    def resolve
      @resolve ||= begin
        last_resolve = converge_locked_specs
        if Bundler.settings[:frozen] || (!@unlocking && nothing_changed?)
          last_resolve
        else
          # Run a resolve against the locally available gems
          requested_ruby_version = ruby_version.version if ruby_version
          last_resolve.merge Resolver.resolve(expanded_dependencies, index, source_requirements, last_resolve, requested_ruby_version)
        end
      end
    end

Now, I was able to dig in and hack a fix, but I don't really understand what all the pieces are supposed to do yet. So, I don't really understand what the purpose of expanded_dependencies is, but in my example gem it starts with the following:
[#<Bundler::DepProxy:0x4612b856 @__platform="ruby", @dep=Gem::Dependency.new("example", Gem::Requirement.new([">= 0"]), :runtime)>,
 #<Bundler::DepProxy:0x22875539 @__platform=#<Gem::Platform:0x97a @cpu=nil, @os="java", @version=nil>, @dep=Gem::Dependency.new("example", Gem::Requirement.new([">= 0"]), :runtime)>,
...

The key thing to notice is that it starts with the ruby platform. I patched `expanded_dependencies with the following which caused my bundle to start succeeding:
    def expanded_dependencies
      @expanded_dependencies ||= expand_dependencies(dependencies, @remote)
    end

    def expand_dependencies(dependencies, remote = false)
      deps = []
      dependencies.each do |dep|
        dep = Dependency.new(dep, ">= 0") unless dep.respond_to?(:name)
        next unless remote || dep.current_platform?
        dep.gem_platforms(@platforms).each do |p|
          # ========> NOTE: The following line is my patch <========
          next if p == "ruby" && dep.name == "example"
          deps << DepProxy.new(dep, p) if remote || p == generic(Gem::Platform.local)
        end
      end
      deps
    end

So this drops the ruby platform that ultimately causes the failure, but clearly isn't a real fix.
Let's dig deeper into what's going on by looking at lib/bundler/resolver.rb.
verify_gemfile_dependencies_are_found!(requirements) is the method where the error is coming from, and it is because search_for(requirement).empty? returns true for that very first requirement that I patched out previously (the example for ruby platform one).
The last line of search_for(dependency) is significant here:
search.select {|sg| sg.for?(platform, @ruby_version) }.each {|sg| sg.activate_platform(platform) }

The search only has 1 result: [#<Gem::Specification:0x3520 example-0.1.0-java>] (which is a SpecGroup from the same file, which extends Array, hence the surrounding brackets). The select block is then passing platform which is ruby (because it is coming from that first dependency from before, again). I'm not really sure what @ruby_version is, but it's not relevant here. The for? method on the SpecGroup then looks at @specs which explicitly has nil in the hash, causing the select to reduce to nothing, which ultimately comes back to verify_gemfile_dependencies_are_found!(requirements) and results in an exception.
Let's look at where @specs comes from. It is in the initializer for SpecGroup, which is looking at the values in reverse order, and matching against all the platforms. Thus, that spec in the SpecGroup remember is #<Gem::Specification:0x3520 example-0.1.0-java>, which clearly has the java platform. If we look at the match_platform implementation in lib/bundler/match_platform.rb, we will see that our platform (java) ends up being false for match_platform for ruby, causing @specs to get nil for ruby.
In the reverse case (going from jruby to ruby), things end up being reversed. However, the SpecGroup has example-0.1.0, which is for the ruby platform, which ends up matching every platform, and so it makes sense then that this same problem doesn't happen in reverse.
Now.... what needs to change...? Bundler::Resolver#search_for? Bundler::Definition#expand_dependencies? Something else entirely? Throw in the towel and just let the answer to this bug be: separate gemspec files? This is the part where I'm stumped.

Wow, great job investigating! I think the platform in the dependency is the problem here, but I can't be sure.

@segiddins thanks! After more investigating, I think I figured out a solution that works, and yeah, the dependency platforms was the problem. My solution restricts the platforms to what the gemspec indicates the platforms are, which causes the expanded_dependencies method to only include those platforms, and then everything seems to work ok.


config file always overwritten when launching spf

Describe the bug
I update my config file, save, launch superfile and my config file gets overwritten.

Expected behavior
should not overwrite my config
System information (please complete the following information):

OS: macOS
Version 15.0.1
Superfile Version v1.1.5

Thanks for your report! this been solve in [71edf64].(https://github.com/yorukot/superfile/commit/71edf6454575ada283da91016cc06ba666477b36)


SW-2475 Remaining link style updates

seeds pages
updated font weight to 500 as per hannah's suggestion
updated font size on people, seedbanks, nurseries

in the first two screenshots, the links are using Arial instead of Inter. all other styling is accurate though!

Thanks for pointing that out @hannah-cai fixed it


Remake the UI

The UI looks bad and has been shown to cause errors in at least one case before. Switching to another framework like Qt is probably the better choice

Turns out QT looks about as bad as egui and is like 60 times more complicated. I might just have to learn how to make egui look less bad I guess

You could take a look at https://iced.rs

Thanks for the suggestion! Looks pretty good from what I can see so far, I will give that a try

You could take a look at https://iced.rs

That was an amazing suggestion! Thanks again, I really liked working with that. It is much simpler, better looking and has better async support than egui. Really improved this project by a lot


[BUG] smatthings tagv4

my smart things tags are not working any more since moving to 2021:12 release they now show a binary input that never used to be there and they are almost always at away status very occasionally they will show as home for a min or so then show away again.
they used to work quite reliably for detecting the state at home or away but now they don't.

Happy New Year to the awesome dev team here.  Tossing in my two cents, I am seeing the same behavior, with one exception.  After about 2 days one of mine went unavailable.  I cannot get it to check in again.  I dug out my old SmartThings hub and it paired right up.  It will not even pair as a new device now in ZHA.

Happy New Year to the awesome dev team here.  Tossing in my two cents, I am seeing the same behavior, with one exception.  After about 2 days one of mine went unavailable.  I cannot get it to check in again.  I dug out my old SmartThings hub and it paired right up.  It will not even pair as a new device now in ZHA.

These devices are completely useless now they are either away when home and occasionally check in. Or go to unavailable if away for long enough

Right after I made my post, I dug into the cluster settings and was able to get two mine to work and report correctly.  checkin_interval in the Poll Control cluster does not appear to be properly set.  When paired to SmartThings it is being set to 60.  I assume the value is seconds, but couldn’t find a credible source to confirm.

Go to Manage Clusters
Select Poll Control
Select checkin_interval under Attributes
Enter 60 for Value (I went with 240 in an attempt to save battery life)
Click Set Zigbee Attribute

Its been almost a month and both fobs are correctly reporting arrivals and departures and they’re not falsely going offline when we are home.  So far so good..

If i remember right is the value 1/4 seconds so standard is 60 seconds and you custom is 15 seconds.

so far so good. with setting to 60. on a side note using set zigbee attribute I was able to make the tag beep quite useful so I can make an automation to make the keys beep in an aid to finding them when thy are misplaced at home


Support of configuration overrides

Background
To install kyma you need to apply the installer CR as well as a set of predefined configMaps which you can customize. At the moment you can specify a custom yaml file containing the configMaps and the installer CR all in one file using the --config flag at install
Motivation
Sometimes it is handy to replace just the installer CR or just one dedicated configMap. The rest of the configuration should be still based on the base yaml file provided by the release. To easily manage your changes it will be helpful to configure the different customizations individually, not all in one file.
Goal
Instead of replacing the full yaml config using the --config flag, support a override of the configmaps and the installer cr defined in the base yaml file
Before: kyma install --config customConfig.yaml
After: kyma install --config monitoringConfig.yaml --config installerCR.yaml --config eventBusConfig.yaml

https://github.com/kyma-incubator/kyma-cli/pull/52 - solves this. -o option allows providing multiple configuration files, each file may contain more than one config map, secret, etc.


schulmberger readCTD bug

uses old skip_footer keyword arg for read_csv. Should be updated to skipfooter I think.

Fixed https://github.com/CovingtonResearchGroup/olm/commit/88621d100986e0adbfa3e758c5e693f0ef8839ea


refactor: add get_base_grid() to states

Pull Request doc
Purpose
What is the larger goal of this change?
To pay down some tech debt and hopefully make PowerSimData codebase more maintainable
What the code is doing
How is the purpose executed?
Removing many similar/copy and pasted calls to initialize the original Grid that a scenario was derived from via information from the scenario object
Testing
How did you test this change (unit/functional testing, manual testing, etc.)?
Existing unit tests
Time estimate
How long will it take for reviewers and observers to understand this code change?
20 minutes

Nice, the implementation looks good to me. One other thing I would consider is updating the usages of scenario.state.get_base_grid() to be simply scenario.get_base_grid().

Nice, the implementation looks good to me. One other thing I would consider is updating the usages of scenario.state.get_base_grid() to be simply scenario.get_base_grid().

@jon-hagg I used scenario.state.get_base_grid() because in the code there was already scenario.state.get_grid() throughout. I'm happy with switching over to scenario.get_base_grid() but if so I would ask if I could also do scenario.get_grid() to be consistent. Let me know!

The code is clear, and it simplifies the logic within the powersimdata.design module. I support a general change from scenario.state.foo to scenario.foo, which is available since #503. Previously we simplified the user-facing example code but kept the more verbose calls within the internal code so that the tests would still pass with the mock objects, but now we should be able to simplify everywhere.
One comment is that with the variable renaming from grid_new to grid within the investment cost functions, we should be sure to remember that what's in this object named grid is not really a grid in the usual sense of the word, but a grid difference for one table within the grid (e.g. the branch table or the plant table or the dcline table), which we use a Grid object for because it's convenient to have those other Grid attributes around (i.e. the bus table, sub table, other non-table attributes, etc.) within the investment cost calculation functions. One day we might decide that we want a cleaner implementation, e.g. maybe with a new GridDelta class that could have one or more tables that are really tables of element differences, not of elements themselves, but I think that's outside of the scope of this PR.

@goccert25 good call - I would also support switching to scenario.get_grid().

@jon-hagg done
@danielolsen renamed the grid variable to grid_differences to be more appropriate
Feel free to approve and merge whenever, I rebased on develop as of the time of this comment


customizable prompt

probably call a lua function to create the prompt, but using state flows on the kotlin side is tempting to make the prompt update in realtime. potential flickering issue, but it is worth a test.

this probably needs another sub system. like autocmd


chore: bump k8s deps to 1.24 and Go to 1.17

bump k8s dependencies to 1.24

@ryantking @zach-source would either of you be able to merge this commit? If not do you mind if I do?

@jmrodri Got it! Sorry for missing this.
/lgtm


Dynamic hostgroup filter

A dynamic hostgroup filter is not implemented, yet - only a prepared setting..

Fixed in commit 9f626ddf4cd1b8934d0f744152bc3e4dc5a7fa17


'nodeSelector' for rstudio-connect helm

In our current RStudio Connect K8s environment, we have two nodes - one 'main' node intended for rstudio-connect deployment (nfs, ingress, database and main app), and one 'content' node for the content pods.
We can successfully target the content pods to go into the content node, so no worries there. However, we just ran into a situation where we did a helm upgrade  and the main rstudio-connect deployment got re-deployed into the content node, versus the main node that we expected.
We would like to avoid this in the future. Would we need to update the rstudio-connect helm chart to allow the 'main app' deployment to target a node via nodeSelector, or is it possible with the current helm chart version?

I think we managed to solve the problem by using affinities instead, which exist in the current helm chart.
pod:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
            - key: rsc
              operator: In
              values:
              - main

Apologies for the noise.