text:
Cluster node appears in member list, can't be removed

Hi. I started a three node cluster using the initial-cluster options and tried to add a fourth node, following the instructions at https://github.com/coreos/etcd/blob/master/Documentation/other_apis.md#add-a-member. I didn't cop that the example POST does not include a name variable. Should it? At any rate, I now can't remove that node from the node list. It shows up in etcdctl member list and through the API but I cannot remove it through either.
 curl -X GET <our-etcd-url>:4001/v2/members/
{"members": [
	{"id":"19fb066f0e9fbad9","name":"<host1>","peerURLs":["<ipaddress1>:7001"],"clientURLs":["<ipaddress1>:4001"]},

	{"id":"1eeb57f0c047c949","name":"<host2>","peerURLs":["<ipaddress2>:7001"],"clientURLs":["<ipaddress2>:4001"]},

	{"id":"4e731f0f2f175c29","name":"","peerURLs":["http://<ipaddress4>:7001"],"clientURLs":[]},

	{"id":"ed0be6765092ead1","name":"<host4>","peerURLs":["<ipaddress3>:7001"],"clientURLs":["<ipaddress3>:4001"]}
	]
}

curl -X GET <our-etcd-url>:4001/v2/members/4e731f0f2f175c29
{"message":"Not found"}

How can I remove the entry for this node, or update it such that it has a name and I can try start etcd on the machine in question? Also, should there be some validation on the member add API endpoint to prevent creating node entries without name?

@kieranmanning You can go ahead and start the member. It will publish the name and client url information itself.

Ah, cool. I had an error in my configuration as well so I didn't realize it picked up the name automatically.
Thanks for the help, closing


text:
mvcc: Add metric for count of db key revisions compacted.

When digging into etcd/boltdb "storage space exceeded" issues, this metric may help answer questions about if/when compactions occured and how much data was freed.

/assign @heyitsanthony Here's one of the metrics that might help us in the future.

would s/Revisions/Keys be better? There may be confusion between an etcd revision (mainrev) and a backend revision (mainrev + subrev).

Codecov Report

Merging #8280 into master will decrease coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8280      +/-   ##
==========================================
- Coverage   76.42%   76.23%   -0.19%
==========================================
  Files         346      346
  Lines       27055    27059       +4
==========================================
- Hits        20676    20628      -48
- Misses       4901     4940      +39
- Partials     1478     1491      +13

Impacted Files
Coverage Δ

mvcc/kvstore_compaction.go
79.41% <100%> (+1.99%)
:arrow_up:

mvcc/metrics.go
96% <100%> (+0.16%)
:arrow_up:

pkg/transport/timeout_conn.go
80% <0%> (-20%)
:arrow_down:

proxy/grpcproxy/register.go
69.44% <0%> (-13.89%)
:arrow_down:

auth/simple_token.go
86.79% <0%> (-6.61%)
:arrow_down:

pkg/adt/interval_tree.go
87.38% <0%> (-3.61%)
:arrow_down:

etcdserver/api/v3rpc/watch.go
90.14% <0%> (-3.29%)
:arrow_down:

integration/bridge.go
89% <0%> (-3%)
:arrow_down:

clientv3/concurrency/election.go
80% <0%> (-2.41%)
:arrow_down:

pkg/netutil/netutil.go
62.35% <0%> (-2.36%)
:arrow_down:

... and 9 more

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 608df0f...2d2c076. Read the comment docs.

@heyitsanthony s/Revisions/Keys sounds good. I'll update the PR.

lgtm

source: gharchive/pull-request

authors: codecov-io heyitsanthony jpbetz xiang90

repo: coreos/etcd

license_type: permissive

license_source: github-api


text:
Set "instance" as node hostname instead of IP

Add relabelings for set "instance" as node hostname instead of IP.

This goes against Prometheus best practices and also doesn't make sense, as the instance label is always supposed to reflect the identity of the target, and when it's the node name, this is not unique to the pods on the node anymore.

repo: coreos/prometheus-operator


text:
deploy: update example pre-reboot hook

This updates the hook with the results from testing.

Manually tested on a vanilla k8s running on alpha (1535.0.0), it works fine.

authors: lucab squeed

repo: coreos/tectonic-torcx


text:
Dark theme

Hi!
It would be great to have a dark\night version of this theme, ideally by just changing css file.

here it is: https://coreui.io/#live-preview

It looks great, but how do you enable it? the .c-dark-theme class appears to do nothing

@james-tcc
The dark theme works with coreui-pro.

source: gharchive/issue

authors: Nixellion james-tcc xidedix

license: MIT


text:
Add preprocessing and use own function to interpret time

Overview
This PR adds a preprocessing step to the opendap dataset. This adds overhead to the to_xarray function. Optimization is needed to make it faster, currently it takes about 2 min for 1 day of data from instruments in #48.
Demo
In [36]: %time ds_list = ooi.to_xarray()
    ...:
[########################################] | 100% Completed |  0.7sDIMS SWAPPED
COMPLETE
DIMS SWAPPED
COMPLETE
DIMS SWAPPED
COMPLETE
CPU times: user 1min 47s, sys: 1min 34s, total: 3min 21s
Wall time: 2min 2s

Notes

Not fully optimized, don't request big data yet.

Testing Instructions

Try with some cabled array instruments.
Use %time on to_xarray() function and try out different range of data request.

Pull Request Test Coverage Report for Build 137

0 of 0   changed or added relevant lines in 0 files are covered.
51 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 47.708%

Files with Coverage Reduction
New Missed Lines
%

/home/travis/miniconda/envs/TEST/lib/python3.6/site-packages/yodapy/datasources/ooi/helpers.py
10
38.1%

/home/travis/miniconda/envs/TEST/lib/python3.6/site-packages/yodapy/datasources/ooi/init.py
41
44.24%

Totals

Change from base Build 136:
-0.1%

Covered Lines:
333

Relevant Lines:
698

💛  - Coveralls

Confirmed success! Thanks @s-kganz!
Merging...

authors: coveralls lsetiawan

repo: cormorack/yodapy


text:
Remove sqlcipher  (DEV)

⬆

Didn't check yet, but in case there are no other zetetic dependencies, this (and many following lines) may also be taken out?
https://github.com/corona-warn-app/cwa-app-android/blob/6e281ebfadbb1d945bcff5dc545289b16335b36a/Corona-Warn-App/src/main/assets/technical.html#L114

Didn't check yet, but in case there are no other zetetic dependencies, this (and many following lines) may also be taken out?
https://github.com/corona-warn-app/cwa-app-android/blob/6e281ebfadbb1d945bcff5dc545289b16335b36a/Corona-Warn-App/src/main/assets/technical.html#L114
@vaubaehn Thanks for point this out, I updated the file

authors: mtwalli vaubaehn

repo: corona-warn-app/cwa-app-android


text:
Add Support for lower case characters in the teleTAN screen

Checklist

[x] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
[ ] If this PR comes from a fork, please Allow edits from maintainers
[x] Set a speaking title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes #41)
[ ] Link your Pull Request to an issue (if applicable)
[ ] Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
[x] Make sure that your PR is not introducing unncessary reformatting (e.g., introduced by on-save hooks in your IDE)
[x] Check our Contribution Guidelines

Description
The current teleTAN entry screen only supports upper case characters, this is wrong according to the official teleTAN entry spec. This PR fixes these issues.

I disagree. The text clearly states that the TAN is case insensitive. That change would be quite confusing for the end users.

@tweimer good catch! The text for all screens is currenlty still in a temporary state, but obvious mismatches between what is on screen and the functionality should still not happen.
Fixed now thanks for the heads up 👍

authors: kolyaopahle tweimer


text:
persistent notification if exposure logging is active

Current Implementation
The user has to open the app in order to see if the exposure logging is active.
Suggested Enhancement
Add a persistent notification wich tells the user if exposure logging is active. If the user wants this notification should be adjustable in the settings.
Expected Benefits
The user can easily see if the logging is active and doesn´t need to open the app.

Maybe a separate issue, but should be solved as well in this context: According to FAQ activating location is as bluetooth prerequisite for risk identification on android devices. When turning bluetooth off the cwa risk identification changes to off as well. But when setting loation to off the cwa risk identification stays on. Thus for the user location seems not be necessary.

@Spirit100 this is already a known issue but thanks for mentioning!

Dear @ChillerSargant ,
thank you very much for your proposal.
To give the community a space for discussing new feature ideas or enhancements that might not be taken up immediately by the development teams, we created the cwa-wishlist repository.
This idea is one of these feature ideas or enhancements. Consequently, we will move this issue to this repository and allow the community and you to further refine it, discuss pros and cons, and evaluate alternatives.
The issue will not be closed in this repository to ensure long-term visibility. All issues in the cwa-wishlist repository will be discussed with our contracting entities. They will decide whether they will be implemented or pursued further. As soon as we have any updates, we will let you know about the details.
Best regards,
TK
Corona-Warn-App Open Source Team

authors: ChillerSargant Spirit100 corneliusroemer tkowark

repo: corona-warn-app/cwa-documentation


text:
Fabo/change milkTIA base denom to IBC trace

Instead of using the base denom of the token on the native chain we need to provide the base denom of the token on Osmosis

Thinking it over. osmosis' TIA gets deposited, but in the backend it transferres back to celestia and stakes TIA, so maybe it should stay as is.

Closing for now. Thank you

repo: cosmos/chain-registry


text:
Code consistency nits in grpc handler

Summary

Use k instead of `q, see comment
Unwrap the sdk context first, see comment

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

I have changed the q's to k but I am not able to undertand on how to unwrap the sdk context first .

authors: colin-axner ruthishvitwit

repo: cosmos/ibc-go


text:
Make separate go.mod for 08-wasm

To reduce dependencies of ibc-go and decouple the release of 08-wasm from ibc-go, the module should have its own go.mod.

Closed by #4026


text:
tendermint proto imports are not consistent between cosmos-sdk and ibc-rs revisions

The upstream proto revisions as currently pulled to build ibc-proto-rs are not consistent as per the revisions of tendermint files they expect to import:

https://github.com/cosmos/cosmos-sdk/commit/2e9e5d6eea24d6c11eddc9c002c66e89ae036187 uses v0.37
https://github.com/cosmos/ibc-go/commit/57fcdb9a9a9db9b206f7df2f955866dc4e10fef4 uses v0.38
https://github.com/cosmos/interchain-security/commit/ea545b490b53b8e6f422492b4fb2820ab0bc140b uses v0.37

However, by the way the build process is set up in sync-protobuf.sh, all of these inputs to proto-compiler actually end up including the tendermint/* protobuf files found in the cosmos-sdk buf export (the proto-include directory).
Which means our ibc:: generated types for this set of upstream revisions do not necessarily interoperate with the Go types generated in ibc-go as per the targeted commit.
The proper way out of this mess is to convert the upstreams to produce buf modules and reuse buf.build/cometbft/cometbft as a common dependency. Then the build process in ibc-proto-rs could consume the buf modules to generate Rust bindings for them.
Meanwhile, it's possible to juggle the src/*_COMMIT files in ibc-proto-rs to arrive at a combination of proto upstreams that happens to use the same revision of the tendermint protos, and then do the extern_path trick on that. But it's a high-quality balancing act that needs developer's time and care. Which is precisely what buf is meant to get rid of.
Originally posted by @mzabaluev in https://github.com/cosmos/ibc-rs/issues/1073#issuecomment-1934724440

From a discussion on Slack, the best quick course of action is to bring all dependencies to Tendermint/CometBFT 0.38.
But in case of ICS, it is blocked on https://github.com/cosmos/interchain-security/issues/1246.

https://github.com/cosmos/ibc-proto-rs/pull/190/commits/5bb2b45a0bb94398acd0ac0ca2553a7b0aae60bf brings the cosmos-sdk checkout up to v0.50.4. In terms of the tendermint version, this gets the includes up to 0.38.
We're in luck with interchain-security: it uses tendermint.crypto.PublicKey, tendermint.abci.Validator, and tendermint.abci.ValidatorUpdate, the definitions of which has not changed since 0.34. So we are able to hold up this house of cards for now.

repo: cosmos/ibc-proto-rs


text:
Update tutorial to use go.mod instead of dep #51

close: #51

This should not be committing to master. Are these docs still invalid/outdated on develop? If not, they'll be updated once v0.34.0 is released.

This should not be committing to master

Branch develop did not exist in tutorial repository.

Are these docs still invalid/outdated on develop?

Which doc did you mean ?

All your changes in this PR should be targeted against develop. Only develop merges into master.

Ahhh ignore my comments @yangyanqing 👍

Thank you @yangyanqing! I think there are some more updates here, but I need to do a full sweep of this tuto and will take care of it then.

authors: alexanderbez jackzampolin yangyanqing

repo: cosmos/sdk-application-tutorial


text:
Probably found typo in docs

Visited https://docs.cossacklabs.com/themis/languages/wasm and saw this:

Should there be a word "platform" instead of "platorm"?

yes, you are right. thanks for noticing. we will fix it.
feel free to contribute into our docs, they are public and open for contribution

we have fixed it

thank you @DandyDrop!

authors: DandyDrop Lagovas vixentael

repo: cossacklabs/themis

license_source: bigquery


text:
Fix a warning about memory leak in Secure Message

clang-tidy is being cautious about allocations. Calm it down by freeing the allocated context if we're going to return NULL.
This actually cannot happen because we check the key type earlier and return before allocating a crypto context. However, clang-tidy is not that smart to see through five layers or preprocessor macros. I'd bet that developers aren't that smart either.

👍

authors: ilammy vixentael


text:
Merge CI fixes: release/0.13 => stable

Pull in some stuff that should make all jobs green again. Except for Bitrise. They might be working on it. Or maybe not.
Checklist

[X] Change is covered by automated tests
[X] The coding guidelines are followed
[X] Changelog is updated (no changes for users)

Also, let's see how this process works. I've included the merge commit into this PR directly, created by
git checkout stable
git merge -S release/0.13

The only allowed merge mode is “squash” right now. Let's see if GitHub allows me to merge that merge commit as is once this is approved and the builds are confirmed to be okay.

Now I'm on my local branch stable which is the same as bump-stable at 3148510, doing just
git push upstream

And this pushes the merge into stable as is, closing this PR as resolved.
⭐ 🤏

I'll leave future merge of master => stable as an exercise. (Or stable => master, if there will be yet another maintenance release of 0.13.x before 0.14.0 finally happens.) Now there's a conflict in .circleci/config.yml there that you'll have to resolve.


text:
Build failed in ubuntu 18.04

Hello! Thank you for this project. I have trouble building this gem.
Build with docker failing with the following scenario:
$ cat Dockerfile
FROM ubuntu:18.04

RUN apt-get update && apt-get install -y ruby-dev bundler

RUN gem install http -v4.2.0

$ docker build .
...

Successfully installed ffi-compiler-1.0.1
Building native extensions. This could take a while...
ERROR:  Error installing http:
        ERROR: Failed to build gem native extension.

    current directory: /var/lib/gems/2.5.0/gems/http-parser-1.2.1/ext
/usr/bin/ruby2.5 -rrubygems /usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake RU
BYARCHDIR=/var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1 RUBYLIBDIR=/va
r/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1
/usr/bin/ruby2.5: No such file or directory -- /usr/share/rubygems-integration/all/gems/rake
-12.3.1/exe/rake (LoadError)

rake failed, exit code 1

Gem files will remain installed in /var/lib/gems/2.5.0/gems/http-parser-1.2.1 for inspection
.
Results logged to /var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1/gem_ma
ke.out

$ docker run --rm -it ubuntu:18.04 bash
root@179ab131b3be:/# apt-get update && apt-get install -y ruby-dev bundler

...

root@179ab131b3be:/# gem install http-parser -v1.2.1
Fetching: ffi-1.11.1.gem (100%)
Building native extensions. This could take a while...
Successfully installed ffi-1.11.1
Fetching: ffi-compiler-1.0.1.gem (100%)
Successfully installed ffi-compiler-1.0.1
Fetching: http-parser-1.2.1.gem (100%)
Building native extensions. This could take a while...
ERROR:  Error installing http-parser:
        ERROR: Failed to build gem native extension.

    current directory: /var/lib/gems/2.5.0/gems/http-parser-1.2.1/ext
/usr/bin/ruby2.5 -rrubygems /usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake RUBYARCHDIR=/var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1 RUBYLIBDIR=/var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1
/usr/bin/ruby2.5: No such file or directory -- /usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake (LoadError)

rake failed, exit code 1

Gem files will remain installed in /var/lib/gems/2.5.0/gems/http-parser-1.2.1 for inspection.
Results logged to /var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1/gem_make.out

root@179ab131b3be:/# cat /var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1/gem_make.out
current directory: /var/lib/gems/2.5.0/gems/http-parser-1.2.1/ext
/usr/bin/ruby2.5 -rrubygems /usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake RUBYARCHDIR=/var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1 RUBYLIBDIR=/var/lib/gems/2.5.0/extensions/x86_64-linux/2.5.0/http-parser-1.2.1
/usr/bin/ruby2.5: No such file or directory -- /usr/share/rubygems-integration/all/gems/rake-12.3.1/exe/rake (LoadError)

rake failed, exit code 1

It's an Ubuntu gems packaging issue. See https://github.com/httprb/http/issues/572 for details.

authors: DmitryBochkarev ixti

repo: cotag/http-parser

license: mit


text:
having problem deploying pages

Checklist

[x] I have read the newlest tutorials and know the correct effect of the functional design.
[x] There is no similar question on existing issues (including closed ones).
[x] I have tried to find the answer on Jekyll Forum and StackOverflow.
[x] My question is based on the latest code of the master branch.

Description
i have just commanded get push and it showed this error! please help

i have tried it many time! but in past it showed
--- layout: home # Index page ---
and now this! ,,please help! I'm trying this for whole day !

Run bundle lock --add-platform x86_64-linux on your local copy of the repository.
Add the modified gemlock to your repo and commit.

I'd  been troubled similar error as follow.
It's solved  with same command (Run bundle lock --add-platform x86_64-linux) now.

I found  important comments ,that might related to these errors, are deleted at README.MD file during simolifying .

Wow, it's my first contribution to one of the open source projects by first
comments.
Thanks , Mr. Cotes.
2022년 11월 12일 (토) 오후 7:32, Cotes @.***>님이 작성:

Closed #721 https://github.com/cotes2020/jekyll-theme-chirpy/issues/721
as completed via c855f09
https://github.com/cotes2020/jekyll-theme-chirpy/commit/c855f091469cbceeda57fabe25f33b70061c13bd
.
—
Reply to this email directly, view it on GitHub
https://github.com/cotes2020/jekyll-theme-chirpy/issues/721#event-7796573972,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A36P66ZXRGWQ5BVPAV3KNSLWH5W4DANCNFSM6AAAAAARLHZ2SQ
.
You are receiving this because you commented.Message ID:
@.***
com>

I have the same issue, but bundle lock --add-platform x86_64-linux does not solve for me.

I have the same issue, but bundle lock --add-platform x86_64-linux does not solve for me.

authors: CoolJosh0221 Ntf-Sadnan myHobbyBest sharonwoo


text:
🛑 Mainnet [TezTools] (eu01-node.teztools.net) is down

In aa70baa, Mainnet [TezTools] (eu01-node.teztools.net) (https://eu01-node.teztools.net/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 372 ms

Resolved: Mainnet [TezTools] (eu01-node.teztools.net) is back up in f65fabf.

repo: cotezos/teznodes


text:
Document.addChangeListener(new Document.ChangeListener() {} not getting any changed callback after putProperties.

Folks,
Wont i get any callback after i do putProperties to document.Local DB callback is suppressed? Do i get a callback after synced to server?
I am puzzled.Is it linked to Database.addChangeListener or something.
In general can i listen to single doc update and avoid Database.addChangeListener for a instance.?
Thanks
Nithin

Hi @NitzDKoder ,
You can obtain Document Change Event through Database.ChangeListener. http://developer.couchbase.com/mobile/develop/references/couchbase-lite/couchbase-lite/database/database/index.html#void-addchangelistenerchangedelegate-delegate
Database.ChangeEvent contains list of updated Document's ChangeEvent.
Hope this helps you.

Hi @hideki ,
Well i am able to get Database.changeListener event.But question is why am i not able to get Document.changeListner ?
http://developer.couchbase.com/mobile/develop/references/couchbase-lite/couchbase-lite/document/document/index.html#void-addchangelistenerchangedelegate-delegate

Hi @NitzDKoder ,
I wrote simple unit test from http://developer.couchbase.com/mobile/develop/guides/couchbase-lite/native-api/document/index.html#notifications . Document.addChangeListener() works as expected. Please confirm. Following is the unit test code that tests Document.addChangeListener() method.
https://github.com/couchbase/couchbase-lite-android/commit/4169c7f5c69c503a362a4711474b49583fc03c20

authors: NitzDKoder hideki

repo: couchbase/couchbase-lite-android


text:
Rewrite doc comments to use a complete sentence for first line

As per Rust RFC 505, the first line of a doc comment should be a complete sentence—not a fragment.

Resolved as part of the v0.6.0 release.

repo: couchdb-rs/couchdb


text:
[Bug]: ML not affecting groupBy queries.

Which product are you using?
Headless
product version
2.8.10
bug description
Hello!
We've recently observed the following issue: we have a search results page with tabs - divided into some categories based on a template of a page - for example Products Jobs Events Stories this is implemented using Headless Tab. Now the tricky part is - that one of the requirements is to have the count of the results for each category in the tab title. This is easy with facets, but not so easy with tabs. We added a custom group by to the query, grouping results by the template - so same thing by which we split results.
All was working fine until I guess more and more searches were triggered by visitors. ML model was learning, and now we're observing differences between what we get from our groupBy and what are the real results when you select a tab.
For example - groupBy returns only 1 product, but clicking on the Product tab gives you 5 results - 4 from ML.
Now the question is - anything we could do here? like how to get the count of results per tab in this case, could we make a group by somehow also count ML results?
Or have Headless tabs return count similar to Facets?
Or ...?
Any help is appriciated🙂 Thanks!
Steps to reproduce
No steps - see description on what's the issue.
It could be that it's not an issue, rather Feature request
Relevant log output
No response

This is indeed a feature request, I advise you to reach out to your CSM or representative @coveo.

Ok, thanks @louis-bompart will do!

repo: coveo/ui-kit


text:
feat(atomic): disableSearch prop for search box

https://coveord.atlassian.net/browse/KIT-1765
We're not changing anything to the OOT behaviour. This is just to allow developers to externally prevent users from triggering searches for X condition

Hmm I could make this a prop on the interface & add it to the store so other component can use it.
But it would take a lot of work to adapt all components that trigger searches to be disabled...
Also, would there be an easy way to disable searches in headless at large?

https://coveord.atlassian.net/browse/KIT-1765

Which other components trigger searches other than the searchbox and facets? If we don't want a facet to trigger a search the user would just hide it, no?

Yes it's my original though too, mostly only the search box would need to be visible & interactive while preventing searches altogether
We can also keep this as a search box only prop from the time being, and if we make it general to the whole interface, we can deprecate the prop

Yes it's my original though too, mostly only the search box would need to be visible & interactive while preventing searches altogether
We can also keep this as a search box only prop from the time being, and if we make it general to the whole interface, we can deprecate the prop

Sounds like a plan

authors: ThibodeauJF mbenkirane-coveo


text:
Improve computation of maxTick

Addressing the y-axis issue: https://trello.com/c/82IW2Lvm/323-poor-y-axis-range-when-graph-barely-enters-critical-range
If the highest y coordinate of the dataset surpassed upper limit (in this case 20%) of the High level, the maxTick would be set to that Y, rather than 1.5 x the upper limit.  This is why maxTick went from 35% to 21% as soon as the data passed 20%.

@pnavarrc Can you verify this when you get back?  Thanks!

 Poor y-axis range when graph barely enters critical range.

authors: apeterson7 mikelehen pnavarrc

repo: covid-projections/covid-projections


text:
Adjust projection timeline to 3 months

This PR adjusts projection timeline from one year to three months. Some considerations:

Some variable names might be getting a little long? What's the best practice here for keeping variable names concise?
Need some confirmation on the new text to ensure the new content makes sense and is good to go.

 Update the incidence chart to be 3 months out

 Update the incidence chart to be 3 months out


text:
Scraper for [LOCATION_HERE]

The source
Please ensure the source meets our source guidelines.  Thank you!

**Full location name: ** [Name here, e.g., "County x,WuHan , CN")]
**Source URL: ** [URL]

Looks like you didn't use the issue template correctly.

repo: covidatlas/coronadatascraper


text:
USA Independent Cities (County -> City)

Original issue https://github.com/covidatlas/coronadatascraper/issues/635, transferred here on Friday Apr 03, 2020 at 21:23 GMT

We should look at migrating independent cities from being listed as counties to being listed as cities at some point. This includes but is not limited to: Baltimore City, St. Louis City, and some 38 cities in VA.

(Transferred comment)
See #599 / #627 as an example.

repo: covidatlas/li


text:
add footer links (Privacy Policy, TOS)

Closes #367 .  Still waiting on some clarification on the Terms of Service document so this will be a draft for now until that is finalized.  Then should be quick merge given minimal adjustments happening here

I removed the Terms of Use link because it seems that it will take some time to receive this from legal team and currently we have a dead link for it in production.  Obviously having dead links is bad so better to remove it for now to avoid confusing user and we can update when we have a Terms of Use document in hand.

repo: covidwatchorg/portal


text:
LKL BBR SSR Config can't compatibility GoFlyway

LD_PRELOAD=/root/lkl/liblkl-hijack.so LKL_HIJACK_NET_QDISC="root|fq1" LKL_HIJACK_SYSCTL="net.ipv4.tcp_congestion_control=bbr;net.ipv4.tcp_wmem=4096 16384 30000000" LKL_HIJACK_OFFLOAD="0x9983" LKL_HIJACK_NET_IFTYPE=tap LKL_HIJACK_NET_IFPARAMS=lkl-tap LKL_HIJACK_NET_IP=10.0.0.2 LKL_HIJACK_NET_NETMASK_LEN=24 LKL_HIJACK_NET_GATEWAY=10.0.0.1 ./goflyway -k=12345 -l=12345 > GoFlyWay.log &
Same config SSR has been working but above config could't.

I have never used BBR on openvz so hope someone else can help.
Try running shadowsocks-go on the server with this config, see whether it can work or not.
If works, it's an issue solely with goflyway, if not, it's an issue with all the programs written in golang.

authors: coyove fudingyu

repo: coyove/goflyway


text:
The image is flipped after detection

When a face has been detected and is displayed on an imageView, it is flipped.

@cp110

Can you give me a picture of the problem?


text:
cparse/builtin-features/operators.inc

The precedence of operators for C++ have changed with the addition of the <=> operator in C++20.
I have updated the "operators.inc" file on my own local clone of cparse from a few days ago and updated the operator precedences to their current values and then added additional C++ operators ^, & and | for my own use.
I have attached the modified file. I have made many other customizations to my GIT clone already, so I do not want to start a new branch at this point, so I am only sending this updated file for your usage.
By the way...the README says it supports the ^  operator which it doesn't and does not mention the ** operator which cparse does support [FYI]
operations.inc.zip

Dang, found a bug in my code. On line 184 in the file "operations.inc" that I uploaded, the & needs to be changed to a | ...

Here is the testing program I used that found the bug.  Please find it attached.
test-shunting-yard.cpp.zip

Hello, @bignmllc I was on vacation sorry for the delay.
That is cool @bignmllc I will read it, if you could send me this in the form of a PR it would be very useful, I will consider what to do about this and get back to you in this thread soon.

Hi @VinGarcia I am not really sure how to do the PR you asked for, I think you are referring to a new Pull Request?  Even though I use Git on a base level, I am certainly not a Git expert, so I would appreciate you telling me how to do the PR. In any case, the only changes are to the "cparse/builtin-features/operators.inc" file, so is it possible just to use the file already provided?

Yeah I can use it, I actually got 4 reports/suggestions on open-source projects during vacations so it might take some time before I stop to create it, so if you want to do it in the meantime the process is:

Fork the project by going up on this page and clicking on "Fork"
Clone your forked project, you can do this with: git clone https://github.com/bignmllc/cparse.git some_dir_name
Enter the project and the make the changes you want
Commit the changes and git push origin master
Enter https://github.com/bignmllc/cparse and use the interface to create a new Pull Request from bignmllc/master to cparse/master

Thanks for the instructions. I have created the PR for you as requested.

Great, I will review it when I have the time.
Thanks!

Oh I also just updated the README to include all the operators you mentioned, i.e. added &, | and **.

authors: VinGarcia bignmllc

repo: cparse/cparse


text:
No compiled files in v0.0.1~v0.5.4

Hey @cpettitt,
I'd like to host your library, dagre on cdnjs — It is one of the most famous free and public web front-end CDN services which is used by ~1,143,000 websites worldwide.
However, I noticed that for v0.0.1~v0.5.4, final ready-to-use compiled files haven't been included in the repository. What do you think should be done regarding those?

We don't host the old versions
The compiled files exist but I somehow overlooked them
Maybe you provide the compiled files for the above mentioned versions

cdnjs/cdnjs/11141

I would suggest ignoring those versions. They had a different API and the current release has been out for a couple of years now - crazy to realize it has been that long!
If you really want them you could recreate them from tags in the source.

Thanks for the response @cpettitt!

repo: cpettitt/dagre


text:
Front end currently not displaying

When the front end is launched, the screen opened is blank with the title 'Vue App'. It appears this bug was introduced in commit fefb780 when the manager files were updated.

This seems to be something else than issue #93. Still, can you try to clear your cache and launch again from the command prompt?

Still the same error after clearing the cache. This works fine on the current main branch by the way (I undid the changes). It's just the commit linked above where there is the issue. I believe @Femkemilene and @QuentinLETERRIER also had this bug.

authors: cormacmlynch pv-camecon


text:
automate update of CHANGELOG when bumping version

see here for some starters: https://github.com/bids-standard/bids-specification/blob/c27f613c779ba75e35397576998ccf388cfb8943/.circleci/config.yml#L65

if (git log -1 --pretty=%s | grep Merge*) && (! git log -1 --pretty=%b | grep REL:) ; then
github_changelog_generator --user bids-standard --project bids-specification --token ${CHANGE_TOKEN} --output ~/build/CHANGES.md --base ~/build/src/pregh-changes.md --header-label "# Changelog" --no-issues --no-issues-wo-labels --no-filter-by-milestone --no-compare-link --pr-label "" --release-branch master
cat ~/build/CHANGES.md
mv ~/build/CHANGES.md ~/build/src/CHANGES.md
else
echo "Commit or Release, do nothing"
fi

closing for now because we can rely on the github generated release notes


text:
[DOC] rewrite readme

I updated the README.
@CerenB let me know if this helps.

It would like this on github
https://github.com/Remi-Gau/CPP_BIDS/tree/remi-doc

Will merge this as this mostly documentation and unit test related


text:
Search box needs to be moved away from the top nav

We can't really put the search box in the top nav since that will interfere with the design. I would try putting it at the top of the left ToC area.

@novoio, when you create a PR that's fixing an issue, you can link a commit to an issue with the footer fix #<number>.
The PR associated with this has been merged already though.

authors: alandefreitas vinniefalco

repo: cppalliance/site-docs


text:
FAIL CppUTestTests (exit status: 2) Failure in TEST(OutOfMemoryTestsForOperatorNew ...

This was the output for make check:
============================================================================
Testsuite summary for CppUTest 3.8
============================================================================
# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to https://github.com/cpputest/cpputest
============================================================================
make[2]: *** [Makefile:2914: test-suite.log] Error 1
make[2]: Leaving directory '/home/timo/cpputest-3.8'
make[1]: *** [Makefile:3022: check-TESTS] Error 2
make[1]: Leaving directory '/home/timo/cpputest-3.8'
make: *** [Makefile:3236: check-am] Error 2

So doing as instructed.
VM through Oracle VM VirtualBox with 2,5 GB allocated RAM,
Running with Ryzen 5 3600. Just downloaded the latest version and tried to build it.
And test-suite.log output:

===================================
   CppUTest 3.8: ./test-suite.log
====================================

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: CppUTestTests
===================

............................!........!..!..!..!..!
..!..!..!..!..!.................!....!.!......!...
..!..!..!..!..!..!..!..!..!..!..!..!..!..!........
!..!..!..!..!..!..!..!..!..!..!..!..!.............
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
.......
tests/MemoryOperatorOverloadTest.cpp:349: error: Failure in TEST(OutOfMemoryTestsForOperatorNew, FailingNewArrayOperatorThrowsAnExceptionWhenUsingStdCppNewWithoutOverride)
	expected to throw std::bad_alloc
but threw nothing

.
tests/MemoryOperatorOverloadTest.cpp:344: error: Failure in TEST(OutOfMemoryTestsForOperatorNew, FailingNewOperatorThrowsAnExceptionWhenUsingStdCppNewWithoutOverride)
	expected to throw std::bad_alloc
but threw nothing

..........................................
..................................................
..................................................
..
Errors (2 failures, 652 tests, 610 ran, 1136 checks, 42 ignored, 0 filtered out, 153 ms)

FAIL CppUTestTests (exit status: 2)

v3.8 is pretty old.

Thanks a lot for the tip! I just grabbed latest referenced version from the webpage. Just cloned latest version from git and error disappeared!

authors: peltsippi thetic

repo: cpputest/cpputest


text:
updated actioncable to newest version 5.1.4

package.json, actioncable dependency update

The semver '^5.0.0' compatible with '^5.1.4'.

authors: astrocket cpunion

repo: cpunion/react-native-actioncable


text:
Remove Java code from Grammar

Per #390

Remove Java code from Grammar

In attempt to flatten the grammar, similar to this example (https://github.com/antlr/grammars-v4/blob/master/python/tiny-python/tiny-grammar-without-actions/Python3.g4).
At the end the grammar will not have only mentions of TAB or UNTAB, thus making htail and tail unnecessary.
Note: this change is also beneficial for https://github.com/cqfn/eo/issues/494 https://github.com/cqfn/eo/issues/485

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@andreoss @yegor256 Oops, I failed. You can see the full log here (spent 2min)
 * [new branch]      gh-pages   -> fork/gh-pages
 * [new branch]      issue-268  -> fork/issue-268
 * [new branch]      issue-268-2 -> fork/issue-268-2
 * [new branch]      issue-345  -> fork/issue-345
 * [new branch]      issue-390  -> fork/issue-390
 * [new branch]      issue-395  -> fork/issue-395
 * [new branch]      issue-396  -> fork/issue-396
 * [new branch]      issue-397  -> fork/issue-397
 * [new branch]      issue-404  -> fork/issue-404
 * [new branch]      issue-420  -> fork/issue-420
 * [new branch]      issue-421  -> fork/issue-421
 * [new branch]      issue-429  -> fork/issue-429
 * [new branch]      issue-431  -> fork/issue-431
 * [new branch]      issue-443  -> fork/issue-443
 * [new branch]      issue-455  -> fork/issue-455
 * [new branch]      issue-472  -> fork/issue-472
 * [new branch]      issue-480  -> fork/issue-480
 * [new branch]      issue-488  -> fork/issue-488
 * [new branch]      issue-490  -> fork/issue-490
 * [new branch]      issue-499  -> fork/issue-499
 * [new branch]      issue-504  -> fork/issue-504
 * [new branch]      issue-505  -> fork/issue-505
 * [new branch]      issue-519  -> fork/issue-519
 * [new branch]      issue-524  -> fork/issue-524
 * [new branch]      issue-533  -> fork/issue-533
 * [new branch]      issue-541  -> fork/issue-541
 * [new branch]      issue-551  -> fork/issue-551
 * [new branch]      issue-554  -> fork/issue-554
 * [new branch]      issue-564  -> fork/issue-564
 * [new branch]      master     -> fork/master
 * [new branch]      master-1   -> fork/master-1
 * [new branch]      master-2   -> fork/master-2
+ args=
+ '[' default == default ']'
+ args=' --ff'
+ '[' default == no ']'
+ '[' default == only ']'
+ export BRANCH=__rultor
+ BRANCH=__rultor
++ git show-branch __rultor
++ wc -l
+ '[' 0 -gt 0 ']'
+ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
+ git checkout -B __rultor fork/issue-390
Switched to a new branch '__rultor'
Branch __rultor set up to track remote branch issue-390 from fork.
+ git checkout -B master origin/master
Switched to and reset branch 'master'
Branch master set up to track remote branch master from origin.
Your branch is up-to-date with 'origin/master'.
+ '[' false == true ']'
+ '[' false == true ']'
+ git merge --ff __rultor
Auto-merging eo-parser/src/main/antlr4/org/eolang/parser/Program.g4
CONFLICT (content): Merge conflict in eo-parser/src/main/antlr4/org/eolang/parser/Program.g4
Automatic merge failed; fix conflicts and then commit the result.
'cid' file is absent, container wasn't started correctly

@andreoss seems to be a conflict with your own changes. Please, resync.

@yegor256 Done

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 9min)

@andreoss thanks!

authors: andreoss rultor yegor256

repo: cqfn/eo


text:
Fix annotations

This change removes the link spanning from the narrative output to address issues #86 and #61. For #86, the problem is that the span-painting algorithm does not account for the fact that the parse tree will move back through the source in the case of in-fix operators, and so duplicates text output in the narrative. For #61, the problem is that the way spanning is currently done involves mixed content, which outputs poorly in the JSON format. This fix addresses both of these in the simplest way possible, by just removing the link output. So all narratives are now output as a single span. I will log another issue to request that the link-spanning functionality be added back in, but delay implementation until we get feedback that it is an important enough feature to warrant effort.

I've tested this against CMS146v2_CQM.cql, and run into the binary infix operator issue from https://github.com/cqframework/clinical_quality_language/issues/86
Key point is r=14 and its children, which have the leading 'AgeInYearsAt(start of MeasurementPeriod) >=' followed by elements containing the same data.
     <annotation xsi:type="a:Annotation">
        <a:s r="21">define "InDemographic":
          <a:s r="20">
              <a:s r="14">
                AgeInYearsAt(start of MeasurementPeriod) >=
                <a:s r="12">
                  AgeInYearsAt(
                  <a:s r="11">
                    start of
                    <a:s r="10">MeasurementPeriod</a:s>
                  </a:s>
                  )
                </a:s>
                >=
                <a:s r="13">2</a:s>
              </a:s>
              and
              <a:s r="19">
                AgeInYearsAt(start of MeasurementPeriod) <
                <a:s r="17">
                  AgeInYearsAt(
                  <a:s r="16">
                    start of
                    <a:s r="15">MeasurementPeriod</a:s>
                    </a:s>
                    )
                  </a:s>
                  <
                  <a:s r="18">18</a:s>
              </a:s>
           </a:s>
        </a:s>
     </annotation>

Hmmm, so when I run this locally it works for me (I see a single span for all expressions). I did push additional changes to this branch today as part of this pull request, and the output you've posted looks like it would have prior to those changes. Can you verify you're running the latest on the fix-annotations branch?

I can confirm Bryn's comment.  I pulled down the fix-annotations branch and ran CQL-to-ELM against CMS146v2_CQM.cql.  For the InDemographic expression, I get the following annotation:
<annotation xsi:type="a:Annotation">
  <a:s>define "InDemographic":
    AgeInYearsAt(start of MeasurementPeriod) >= 2 and AgeInYearsAt(start of MeasurementPeriod) < 18</a:s>
</annotation>

Bryn, is this what you expect?  It seems to work for me.  That said, I question how useful this will be to Bonnie.  I expect Bonnie wants a higher level of fidelity than just annotations at the expression level.

Yes, that's what I expect to be output, it solves both the problems, although with admittedly less useful output. That's why I opened issue #95 to track whether or not we need to go to the extra effort of actually linking the source up to the nodes.

@alexanderelliott121: Assuming you can get the cql-to-elm working as described above, does this change improve things for you, keep things about the same, or make them worse?  If either of the first two, I'm inclined to accept the PR.  If, however, it makes things worse, we should probably discuss.

I'll let @alexanderelliott121 respond to if he sees the same output. Based on the output the @cmoesel noted, that won't be helpful for the Bonnie team. The most helpful thing would be to have all terminal nodes from the cql tree listed in the annotations with their associated elm logic components.

Thanks, @edeyoung.  Then I guess the relevant question really is whether or not this update sets you back, or leaves you in the same place.  If the previous functionality was unusable anyway, I'm inclined to accept this PR and move on with a plan to get the functionality Bonnie needs in place.  On the other hand, if the previous (broken) functionality was still better than this fix, then we should discuss w/ Bryn.

Okay, can we use the other issue to track adding the linked nodes functionality back in and let this one go through so we can at least get processable JSON output?

Would the output here dictate the specification for the JSON output?

Only to the extent that we would make sure that the annotations were JSON friendly (i.e. no mixed content spans).

I've had a chance to run the tests again.  I'm now seeing the output expected for the fix (the local identifiers are stripped out and the duplicate lines have been removed).

authors: alexanderelliott121 brynrhodes cmoesel edeyoung


text:
feat: support Q4_1

TODO:

add vec dot test
add SIMD

part: https://github.com/crabml/crabml/issues/48

@flaneur2020 Could you please take a look?

repo: crabml/crabml


text:
Is there anyway to customize the 'action' route(s) ?

I work on a sign-up process on a project that will need to create two entry (for 2 different sections) on the same "form" (I will handle this by ajax) and I want to avoid the use of guest-entries/save in my template to be more constant with my form process. Is there any way to use the builtin Craft routing to do that ?
Already try with something like this :
return [
    'app' => [
        'app/create/parent' => 'guest-entries/save',
        'app/create/child' => 'guest-entries/save',
    ],
];

...and that’s not working event if the official doc on the advanced routing let you believe that you can add a custom routing for a controller.

That should work in theory, yes, but you will need to reference the route in the request URI (e.g. POST https://example.com/app/create/parent, and also make sure you’re not passing an action param in the request body.

Where should I add the "route reference in the request URI" ?

I just mean that the URL you are making an Ajax request to should have a URI based on the route.

authors: brandonkelly jesuismaxime

repo: craftcms/guest-entries


text:
nitro apply exit status 2 on windows

Using develop, have a machine successfully running with:
php: "7.4"
mounts:
- source: D:\dev\nitro
  dest: /home/ubuntu/sites/site.test
sites:
- hostname: site.test
  webroot: /home/ubuntu/sites/site.test/www

Change to:
php: "7.4"
mounts:
- source: D:\dev\nitro
  dest: /home/ubuntu/sites/site2.test
sites:
- hostname: site2.test
  webroot: /home/ubuntu/sites/site.test/www

Run nitro apply and get Error: exit status 2

Resolved this in beta 7.

authors: angrybrad jasonmccallister

repo: craftcms/nitro


text:
Top margin on star-rating-text misaligns it for smaller size stars (and isn't even needed)

An example of what I mean is in the "Lots of Stars" example in the JSFiddle.
I'm assuming the top-margin of 7px was to align the number vertically, but since the parent div.vue-star-rating already has align-items: center, it isn't even needed.
PS. Nice little component. Thanks!

I can create a PR if you prefer.


text:
Epoch can not be set

It looks like the Epoch is hard-coded to 0 in Builder.java. It should be configurable.

+1

repo: craigwblake/redline


text:
Amazon Linux 2023 target

Hi @Enchufa2,
(Apologies in advance if this is out of scope.)
Back in March, Amazon Linux 2023 was launched. tl;dr this is the successor distro to AL2 and will become the default for much of AWS infrastructure (incl. a lot of internal tools).
AL2023 is closer to Fedora than its predecessor and I noticed that copr recently added build targets for it. https://github.com/fedora-copr/copr/issues/2666
Would it be possible to add AL2023 support to cran2copr?
Thanks for considering.

Thanks, I would be happy to support AL2023. There are two limitations though:

Disk space in Fedora Copr infrastructure.
Important dependencies that are unavailable in AL2023.

Disk space has been the main limitation in the past for activating new chroots in this project, so I should ask the Fedora Copr team first. If we have their ok, then we could look into the second limitation. For instance, I just tried:
$ podman run --rm -it amazonlinux:2023
$ dnf -q install gdal proj libarrow
Error: Unable to find a match: gdal proj libarrow

So my question is: how do you compile CRAN packages without these dependencies (probably others too)? Is there any EPEL-like repository for AL2023 providing them? If not, would you be willing to help maintain them in a separate repo (maybe another Fedora Copr project)? My guess is that most of them should work just by running the Fedora spec for the AL2023 target, but some adaptations may be needed.

Hi, @praiskup @FrostyX, we are talking about the possibility of enabling the AL2023 chroot in iucar/cran. Before assessing the feasibility in terms of dependencies, and knowing that disk space has been a problem in the past, I would like to ask for the feasibility from the point of view of the infrastructure.

So my question is: how do you compile CRAN packages without these dependencies (probably others too)? Is there any EPEL-like repository for AL2023 providing them? If not, would you be willing to help maintain them in a separate repo (maybe another Fedora Copr project)? My guess is that most of them should work just by running the Fedora spec for the AL2023 target, but some adaptations may be needed.

In truth, I am less familiar with both Fedora and AL2023 than I am other distros. But I believe the preferred approach is to first raise a FR on the main AL2023 GitHub repo. From a quick search, I can see that GDAL has already been requested. I didn't see PROJ or arrow, but I'm happy request those. (A list of currently all AL2023 packages is available here.)
As regards EPEL, that is not supported. I am certainly  happy to help maintain a separate Copr project for the libraries that we can't pass through the main FRs, but may need some handholding to set it up.

Ok, great, so first off, in the sysreqs.csv file in this repo, there's a comprehensive list of dependencies (also you can see there which package needs them):
df <- read.csv("sysreqs.csv")
x <- sort(unique(do.call(c, strsplit(c(df$build), " ")))); x
#>  [1] "/usr/bin/exiftool"                "autoconf"
#>  [3] "automake"                         "bison"
#>  [5] "boost-devel"                      "bwidget"
#>  [7] "cairo-devel"                      "cargo"
#>  [9] "cmake"                            "coin-or-Clp-devel"
#> [11] "coin-or-SYMPHONY-devel"           "cyrus-sasl-devel"
#> [13] "devscripts-checkbashisms"         "ffmpeg-free-devel"
#> [15] "fftw-devel"                       "fftw3-devel"
#> [17] "flex"                             "freetype-devel"
#> [19] "fribidi-devel"                    "gdal-devel"
#> [21] "geos-devel"                       "glib2-devel"
#> [23] "glibc-devel(x86-32)"              "glpk-devel"
#> [25] "gmp-devel"                        "gnupg2"
#> [27] "gpgme-devel"                      "gsl-devel"
#> [29] "harfbuzz-devel"                   "haveged-devel"
#> [31] "hdf5-devel"                       "hiredis-devel"
#> [33] "ImageMagick-c++-devel"            "jags-devel"
#> [35] "jq-devel"                         "leptonica-devel"
#> [37] "libarchive-devel"                 "libarrow-dataset-devel"
#> [39] "libcurl-devel"                    "libgit2-devel"
#> [41] "libicu-devel"                     "libjpeg-turbo-devel"
#> [43] "libpng-devel"                     "libpq-devel"
#> [45] "librsvg2-devel"                   "libsecret-devel"
#> [47] "libsodium-devel"                  "libssh-devel"
#> [49] "libssh2-devel"                    "libtiff-devel"
#> [51] "libtool"                          "libwebp-devel"
#> [53] "libxml2-devel"                    "libxslt-devel"
#> [55] "libXt-devel"                      "mariadb-devel"
#> [57] "mbedtls-devel"                    "mecab-devel"
#> [59] "mesa-libGL-devel"                 "mesa-libGLU-devel"
#> [61] "mpfr-devel"                       "ncurses-devel"
#> [63] "netcdf-devel"                     "nng-devel"
#> [65] "openbugs"                         "opencv-devel"
#> [67] "openmpi-devel"                    "openssl-devel"
#> [69] "pcre"                             "pocl-devel"
#> [71] "poppler-cpp-devel"                "poppler-data"
#> [73] "poppler-glib-devel"               "proj-devel"
#> [75] "protobuf-devel"                   "python3dist(jupyter-kernel-test)"
#> [77] "python3dist(ndjson-testrunner)"   "qpdf-devel"
#> [79] "QuantLib-devel"                   "R-CRAN-BH"
#> [81] "R-CRAN-RcppGSL"                   "R-java-devel"
#> [83] "redland-devel"                    "rrdtool-devel"
#> [85] "scala"                            "sqlite-devel"
#> [87] "tbb-devel"                        "tesseract-devel"
#> [89] "texlive-pgf"                      "tiledb-devel"
#> [91] "udunits2-devel"                   "unixODBC-devel"
#> [93] "v8-devel"                         "xorg-x11-server-Xvfb"
#> [95] "zeromq-devel"                     "zlib-devel"

Then we can check which packages provide these dependencies:
system2("dnf", c("rq -q --qf '%{source_name}'", paste("--whatprovides", shQuote(x))), stdout=TRUE)
#>  [1] "ImageMagick"                "QuantLib"
#>  [3] "R"                          "R-CRAN-BH"
#>  [5] "R-CRAN-RcppGSL"             "autoconf"
#>  [7] "automake"                   "bison"
#>  [9] "boost"                      "bwidget"
#> [11] "cairo"                      "cmake"
#> [13] "coin-or-Clp"                "coin-or-SYMPHONY"
#> [15] "curl"                       "cyrus-sasl"
#> [17] "devscripts"                 "ffmpeg"
#> [19] "fftw"                       "flex"
#> [21] "freetype"                   "fribidi"
#> [23] "gdal"                       "geos"
#> [25] "glib2"                      "glibc"
#> [27] "glpk"                       "gmp"
#> [29] "gnupg2"                     "gpgme"
#> [31] "gsl"                        "harfbuzz"
#> [33] "haveged"                    "hdf5"
#> [35] "hiredis"                    "icu"
#> [37] "jags"                       "jq"
#> [39] "leptonica"                  "libXt"
#> [41] "libarchive"                 "libarrow"
#> [43] "libgit2"                    "libgit2_1.5"
#> [45] "libjpeg-turbo"              "libpng"
#> [47] "libpq"                      "librsvg2"
#> [49] "libsecret"                  "libsodium"
#> [51] "libssh"                     "libssh2"
#> [53] "libtiff"                    "libtool"
#> [55] "libwebp"                    "libxml2"
#> [57] "libxslt"                    "mariadb"
#> [59] "mbedtls"                    "mecab"
#> [61] "mesa"                       "mesa-libGLU"
#> [63] "mpfr"                       "ncurses"
#> [65] "netcdf"                     "nng"
#> [67] "nodejs16"                   "nodejs18"
#> [69] "nodejs20"                   "openbugs"
#> [71] "opencv"                     "openmpi"
#> [73] "openssl"                    "pcre"
#> [75] "perl-Image-ExifTool"        "pocl"
#> [77] "poppler"                    "poppler-data"
#> [79] "proj"                       "protobuf"
#> [81] "python-jupyter-kernel-test" "python-ndjson-testrunner"
#> [83] "qpdf"                       "redland"
#> [85] "rrdtool"                    "rust"
#> [87] "scala"                      "sqlite"
#> [89] "tbb"                        "tesseract"
#> [91] "texlive"                    "tiledb"
#> [93] "udunits2"                   "unixODBC"
#> [95] "xorg-x11-server"            "zeromq"
#> [97] "zlib"

We need to go through this list, identify the missing pieces, and submit them to AL2023; then we'll see what we can do with the ones that are not accepted. Note that:

R-CRAN-* stuff can be ignored, because these are self-references.
jags, openbugs, and tiledb can be ignored too, because these are provided in this repo too.
There are several nodejs versions listed. It would be enough to provide one of them.
For reference, the corresponding Fedora spec can be found by prepending https://src.fedoraproject.org/rpms/, e.g. https://src.fedoraproject.org/rpms/curl. But the AL2023 managers of course already know this. :)

Update after moving the repo to the cran4linux org and cleaning up a bit the sysreqs:
setwd("/home/iucar/Documents/repos/cran2copr")
deps <- read.csv("sysreqs/sysreqs.csv", na.strings="") |>
  subset(build, fedora_rhel, drop=TRUE)

Let's ask AL2023 to install all of them and thus to report what's missing:
out <- suppressWarnings(system2("podman", c(
  "run --rm -it -v $PWD/sysreqs:/mnt:z -w /mnt",
  "public.ecr.aws/amazonlinux/amazonlinux:2023",
  "dnf install -q", paste(shQuote(deps), collapse=" ")
), stdout=TRUE, stderr=TRUE)) |> print()
#> [1] "Error: Unable to find a match: libarrow-dataset-devel bwidget coin-or-Clp-devel coin-or-SYMPHONY-devel devscripts-checkbashisms /usr/bin/exiftool ffmpeg-free-devel gdal-devel geos-devel glpk-devel hdf5-devel hiredis-devel jags-devel leptonica-devel libsodium-devel mecab-devel mariadb-devel netcdf-devel openbugs glibc-devel(x86-32) opencv-devel pocl-devel poppler-cpp-devel poppler-data poppler-glib-devel proj-devel QuantLib-devel redland-devel scala tesseract-devel tiledb-devel udunits2-devel zeromq-devel\r"
#> attr(,"status")
#> [1] 1
out <- sub("\\r", "", strsplit(out, ": ")[[1]][3])
unavailable <- strsplit(out, " ")[[1]] |> print()
#>  [1] "libarrow-dataset-devel"   "bwidget"
#>  [3] "coin-or-Clp-devel"        "coin-or-SYMPHONY-devel"
#>  [5] "devscripts-checkbashisms" "/usr/bin/exiftool"
#>  [7] "ffmpeg-free-devel"        "gdal-devel"
#>  [9] "geos-devel"               "glpk-devel"
#> [11] "hdf5-devel"               "hiredis-devel"
#> [13] "jags-devel"               "leptonica-devel"
#> [15] "libsodium-devel"          "mecab-devel"
#> [17] "mariadb-devel"            "netcdf-devel"
#> [19] "openbugs"                 "glibc-devel(x86-32)"
#> [21] "opencv-devel"             "pocl-devel"
#> [23] "poppler-cpp-devel"        "poppler-data"
#> [25] "poppler-glib-devel"       "proj-devel"
#> [27] "QuantLib-devel"           "redland-devel"
#> [29] "scala"                    "tesseract-devel"
#> [31] "tiledb-devel"             "udunits2-devel"
#> [33] "zeromq-devel"

And finally, let's ask Fedora the source package names for these:
pkgs <- system2("dnf", c(
  "rq -q --qf '%{source_name}'",
  paste("--whatprovides", shQuote(unavailable))
), stdout=TRUE) |> print()
#>  [1] "QuantLib"            "bwidget"             "coin-or-Clp"
#>  [4] "coin-or-SYMPHONY"    "devscripts"          "ffmpeg"
#>  [7] "gdal"                "geos"                "glibc"
#> [10] "glpk"                "hdf5"                "hiredis"
#> [13] "jags"                "leptonica"           "libarrow"
#> [16] "libsodium"           "mariadb"             "mecab"
#> [19] "netcdf"              "openbugs"            "opencv"
#> [22] "perl-Image-ExifTool" "pocl"                "poppler"
#> [25] "poppler-data"        "proj"                "redland"
#> [28] "scala"               "tesseract"           "tiledb"
#> [31] "udunits2"            "zeromq"

Therefore:

There are a few packages that are strongly required: gdal, geos, proj, udunits2. If these are not available, we cannot build the geospatial stack as well as its dependencies. These are a lot of packages.
Some nice to have, for obvious reasons: ffmpeg, hdf5, hiredis, libarrow, mariadb. We don't lose many packages without them, but some of those packages are pretty useful.
The others are far less important in principle, and only a handful of packages are lost. It depends of course on whether you rely on them.

In other words, if you manage to get the geospatial packages accepted, that would be enough to activate the AL2023 chroot. :)

Update after moving the repo to the cran4linux org and cleaning up a bit the sysreqs:
deps <- read.csv("sysreqs/sysreqs.csv", na.strings="") |>
  subset(build, fedora_rhel, drop=TRUE)

Let's ask AL2023 to install all of them and thus to report what's missing:
out <- suppressWarnings(system2("podman", c(
  "run --rm -it -v $PWD/sysreqs:/mnt:z -w /mnt",
  "public.ecr.aws/amazonlinux/amazonlinux:2023",
  "dnf install -q", paste(shQuote(deps), collapse=" ")
), stdout=TRUE, stderr=TRUE)) |> print()
#> [1] "Error: Unable to find a match: libarrow-dataset-devel bwidget coin-or-Clp-devel coin-or-SYMPHONY-devel devscripts-checkbashisms /usr/bin/exiftool ffmpeg-free-devel gdal-devel geos-devel glpk-devel hdf5-devel hiredis-devel jags-devel leptonica-devel libsodium-devel mecab-devel mariadb-devel netcdf-devel openbugs glibc-devel(x86-32) opencv-devel pocl-devel poppler-cpp-devel poppler-data poppler-glib-devel proj-devel QuantLib-devel redland-devel scala tesseract-devel tiledb-devel udunits2-devel zeromq-devel\r"
#> attr(,"status")
#> [1] 1
out <- sub("\\r", "", strsplit(out, ": ")[[1]][3])
unavailable <- strsplit(out, " ")[[1]] |> print()
#>  [1] "libarrow-dataset-devel"   "bwidget"
#>  [3] "coin-or-Clp-devel"        "coin-or-SYMPHONY-devel"
#>  [5] "devscripts-checkbashisms" "/usr/bin/exiftool"
#>  [7] "ffmpeg-free-devel"        "gdal-devel"
#>  [9] "geos-devel"               "glpk-devel"
#> [11] "hdf5-devel"               "hiredis-devel"
#> [13] "jags-devel"               "leptonica-devel"
#> [15] "libsodium-devel"          "mecab-devel"
#> [17] "mariadb-devel"            "netcdf-devel"
#> [19] "openbugs"                 "glibc-devel(x86-32)"
#> [21] "opencv-devel"             "pocl-devel"
#> [23] "poppler-cpp-devel"        "poppler-data"
#> [25] "poppler-glib-devel"       "proj-devel"
#> [27] "QuantLib-devel"           "redland-devel"
#> [29] "scala"                    "tesseract-devel"
#> [31] "tiledb-devel"             "udunits2-devel"
#> [33] "zeromq-devel"

And finally, let's ask Fedora the source package names for these:
pkgs <- system2("dnf", c(
  "rq -q --qf '%{source_name}'",
  paste("--whatprovides", shQuote(unavailable))
), stdout=TRUE) |> print()
#>  [1] "QuantLib"            "bwidget"             "coin-or-Clp"
#>  [4] "coin-or-SYMPHONY"    "devscripts"          "ffmpeg"
#>  [7] "gdal"                "geos"                "glibc"
#> [10] "glpk"                "hdf5"                "hiredis"
#> [13] "jags"                "leptonica"           "libarrow"
#> [16] "libsodium"           "mariadb"             "mecab"
#> [19] "netcdf"              "openbugs"            "opencv"
#> [22] "perl-Image-ExifTool" "pocl"                "poppler"
#> [25] "poppler-data"        "proj"                "redland"
#> [28] "scala"               "tesseract"           "tiledb"
#> [31] "udunits2"            "zeromq"

Therefore:

There are a few packages that are strongly required: gdal, geos, proj, udunits2. If these are not available, we cannot build the geospatial stack as well as its dependencies. These are a lot of packages.
Some nice to have, for obvious reasons: ffmpeg, hdf5, hiredis, libarrow, mariadb. We don't lose many packages without them, but some of those packages are pretty useful.
The others are far less important in principle, and only a handful of packages are lost. It depends of course on whether you rely on them.

In other words, if you manage to get the geospatial packages accepted, that would be enough to activate the AL2023 chroot. :)

Super, thanks @Enchufa2. I'm on vacation now but will ping the AL2023 repo with requests when I get a chance!

Just a minor update on this:
The arrow homepage includes install instructions for binary artifacts on AL2023 (scroll down towards the bottom).
Unfortunately, by default, this pulls in the latest release of libarrow & co. So, there's a good chance that there will be a version mismatch with the R release (which is normally a couple of months behind for some reason.) Nonetheless, I managed to adapt their instructions in a way that pulls in the appropriate arrow system library version(s) based on the available CRAN release:
# Note: No sudo because i assumE you are root

# preliminaries: install R and some system deps
dnf install -y R libcurl-devel openssl-devel

# Set env vars for matching up the R and system arrow versions

ARCH=$(uname -m)
R_ARROW_VER=`Rscript -e 'cat(available.packages(filters = list(function(db) db[db[, "Package"] == "arrow", ]), repos = "https://cran.r-project.org")[["Version"]])'`
R_ARROW_VER="${R_ARROW_VER%.*}-1"
ARROW_URL="https://apache.jfrog.io/artifactory/arrow/amazon-linux/2023/${ARCH}/Packages"

# Install

ARROW_ENDPOINT=${R_ARROW_VER}.amzn2023.noarch.rpm
dnf install -y ${ARROW_URL}/apache-arrow-release-${ARROW_ENDPOINT}

ARROW_ENDPOINT=${R_ARROW_VER}.amzn2023.${ARCH}.rpm
dnf install -y ${ARROW_URL}/arrow-devel-${ARROW_ENDPOINT} # For C++
dnf install -y ${ARROW_URL}/arrow-glib-devel-${ARROW_ENDPOINT} # For GLib (C)
dnf install -y ${ARROW_URL}/arrow-acero-devel-${ARROW_ENDPOINT} # For Apache Arrow Acero
dnf install -y ${ARROW_URL}/arrow-dataset-devel-${ARROW_ENDPOINT} # For Apache Arrow Dataset C++
dnf install -y ${ARROW_URL}/arrow-dataset-glib-devel-${ARROW_ENDPOINT} # For Apache Arrow Dataset GLib (C)

# Note: I couldn't get the flight libs to build (see comments below)
# dnf install -y ${ARROW_URL}/arrow-flight-devel-${ARROW_ENDPOINT} # For Apache Arrow Flight C++
# dnf install -y ${ARROW_URL}/arrow-flight-glib-devel-${ARROW_ENDPOINT} # For Apache Arrow Flight GLib (C)
# dnf install -y ${ARROW_URL}/arrow-flight-sql-devel-${ARROW_ENDPOINT} # For Apache Arrow Flight SQL C++
# dnf install -y ${ARROW_URL}/arrow-flight-sql-glib-devel-${ARROW_ENDPOINT} # For Apache Arrow Flight SQL GLib (C)

dnf install -y ${ARROW_URL}/gandiva-devel-${ARROW_ENDPOINT} # For Apache Gandiva C++
dnf install -y ${ARROW_URL}/gandiva-glib-devel-${ARROW_ENDPOINT} # For Apache Gandiva GLib (C)
dnf install -y ${ARROW_URL}/parquet-devel-${ARROW_ENDPOINT} # For Apache Parquet C++
dnf install -y ${ARROW_URL}/parquet-glib-devel-${ARROW_ENDPOINT} # For Apache Parquet GLib (C)

Once that's done, installing the R arrow package & compilation works:
install.packages("arrow")

Comments:

One bummer (given the fact that it's Amazon Linux) is that this configuration doesn't come with S3 support enabled. I'm probably missing some step, but hopefully there's a reasonable solution.
I couldn't get the arrow flight libs to install correctly due to an unresolved dependency version issue. (I believe realted to abseil-cpp.) On the release page there's a separate group of targets for, e.g., `arrow14-flight* libs that you probably need to work with. but I didn't pursue this much further.


text:
[improvement] Use Materialize's tags

In Materialize's docs under Forms->Chips, there are instructions for making tags (with click-removal and autocomplete). That would be cool to use.

In progress in branch "tags," but on hold until I can figure out some of the weird behavior.

repo: cranndarach/lifetracker


text:
Added external link for formatted geoshape results

@chaudum This links to http://geojson.io/ - but the geo_point data type links to a google maps link. Do you think this is fine, or do you think both should use geojson, or at least openmapbox?

Current coverage is 20.83% (diff: 100%)

Merging #364 into master will increase coverage by 0.09%

@@             master       #364   diff @@
==========================================
  Files            20         20
  Lines          1635       1637     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            339        341     +2
  Misses         1296       1296
  Partials          0          0

Powered by Codecov. Last update 0b481c5...68c1da2

@Autophagy I like geojson.io because you can also see the geojson input next to the map. I would point both types to geojson.io

@chaudum I can point a geopoints coordinates at geojson.io but it doesnt place a marker down at the point, like gmaps does - it just centers the map on that location. A solution could be to encode the lat & long of a geopoint into a geoarea point, like:
{
        "type": "Point",
        "coordinates": [
          15.380859374999998,
          47.81315451752768
        ]
}```

Which would place a marker, but I worry it would be confusing. OSM does support markers in the URL based on lat/long, like this http://www.openstreetmap.org/?mlat=51.510772705078125&mlon=0.054931640625#map=9/51.5108/0.0549

@Autophagy so your suggestion would be to use OSM for both geo_point and geo_shape?

@chaudum My suggestion would be to use geojson.io for geo_shape and OSM for geo_point. Geojson uses OSM, so both maps would be at least visually consistent

authors: Autophagy chaudum codecov-io

repo: crate/crate-admin


text:
DBeaver: NumberFormatException when importing data into table with boolean column

create table repro (flag BOOLEAN);

Then create a .csv file and try to import it from DBeaver with the default "Data load settings" with "Skip bind values during insert" not selected
flag
0

In CrateDB this will fail with
NumberFormatException in java.base/java.math.BigDecimal.<init>(BigDecimal.java:703).CXX000.FSQLExceptions.java.ResToCrateException.L152.Wio.crate.exceptions.SQLExceptions.esToCrateException(SQLExceptions.java:152)

in PostgreSQL it works
(DBeaver also succeeds if the column is INT instead of BOOLEAN or if we select the option to skip binding)
I can get the same stack trace in Java if I use a setBigDecimal against a PreparedStatement instead of a setBoolean , however this fails also against pgqsl while DBeaver works against pgsql.
So perhaps this something about pg_type not having composite type entries for the tables or about pg_description not having an entry for the boolean data type?

Hi @hlcianfagna and @surister. Can I humbly ask you to evaluate the problem closer, and maybe derive or move this issue into crate/crate, when applicable?
/cc @proddata, @seut

I did a quick test, this still occurs with the latest version of DBeaver and the latest nightly of CrateDB.

In the spirit of the above proposal, to focus on the CrateDB JDBC Driver again, which hopefully works in more occasions than the one for PostgreSQL, let me reference DBeaver plugin descriptions of CrateDB (Legacy) vs. CrateDB.
Because always being compatible with vanilla PostgreSQL is difficult, maybe we should remove the PostgreSQL-based item again, and also promote "CrateDB (Legacy)" to canonical "CrateDB" here, to reduce confusion and friction for all users of DBeaver and CrateDB.
This might partly revert the updates submitted by @proddata the other day,

Also this moves the generic CrateDB connector using the CrateDB specific JDBC Driver to legacy, as with recent CrateDB versions the default recommendations is to use the standard PostgreSQL JDBC Driver.

https://github.com/dbeaver/dbeaver/pull/20549

so I'd also like to involve him into this discussion, in order to possibly collectively agree to the conclusion that the CrateDB JDBC Driver should NOT be declared legacy, but should be promoted as the primary JDBC connector library to use with CrateDB.
/cc @kneth, @surister

agree to the conclusion that the CrateDB JDBC Driver should NOT be declared legacy, but should be promoted and avertised to be the primary JDBC connector library to use with CrateDB instead.

[!Caution]
The CrateDB JDBC driver is outdated and shall only be used with caution. Until there is a decision to bring this back to full maintenance, no tool or integration shall use this at all.

If there is something not working in DBeaver, this shall be fixed by customizing the CrateDB connection there (which is possible) or adding functionality to CrateDB.

This issue has been fixed with CrateDB 5.9.1 and later versions

Fixed an issue that would cause an error to be thrown when using PostgreSQL wire protocol and attempting to insert 0 value for a numeric NUMERIC, or trying to get 0 numeric value from a query, e.g.:

cr> create table repro (flag BOOLEAN);
CREATE OK, 1 row affected (0.164 sec)
cr> SELECT * FROM repro;
+------+
| flag |
+------+
+------+
SELECT 0 rows in set (0.064 sec)

cr> SELECT * FROM repro;
+-------+
| flag  |
+-------+
| FALSE |
+-------+
SELECT 1 row in set (0.013 sec)

This is great news, thank you very much. In this case, all what is left is to wrap up this patch, demonstrating DBeaver with CrateDB >= 5.9.1, and using the vanilla pgJDBC adapter? Excellent!

https://github.com/crate/cratedb-guide/pull/157

authors: amotl hlcianfagna proddata

repo: crate/crate-clients-tools


text:
Introduce maven profile to run server tests

Use mvn -PserverTest -am test to build the dependencies as needed,
but only run tests for server module.

retest this please

retest this please

repo: crate/crate


text:
remove unused PositionalRow/Bucket stuff

became unused with 07c87340f97cbdd759fe377e82fce84bc37d6fad

ack

authors: dobe mfussenegger


text:
Correction: copyright fix

Summary of the changes / Why this is an improvement

Copyright fix as part of copyright review

Checklist

[ ] CLA is signed

Hi Matthijs,
integrating #31 will most probably unlock merging your patch.
With kind regards,
Andreas.

Hi Matthijs,
integrating #31 will most probably unlock merging your patch.
With kind regards,
Andreas.

authors: amotl matthijskrul


text:
cincinnati/*: break out initial implementation

Splitting out the core Cincinnati functionality into a separate crate
will allow other crates to make use of this functionality. This initial
implementation only supports the very basics needed to create a graph.

Travis seems to be confused.

repo: crawford/cincinnati


text:
[CI] Update the CI to latest RHEL version

openshift-ci is currently provision machine which is outdated (8.6), it is need to be updated. We use https://github.com/ironcladlou/openshift4-libvirt-gcp/ to manage the CI nodes and same images are used for multi arch team and also for libvirt installer e2e tests.

I have updated the CI images, will keep an eye on different CI jobs to make sure it it is doesn't break before closing it.

It is already done and CI is running as expected. Closing it.

repo: crc-org/crc


text:
Issue with value 0 in $in operator

I have sample code over here on which I am trying "$in" operator to search value 0, but not getting expected result.
data = [{"a":{"b":[{"status":0}]}},{"a":{"b":[{"status":2}]}}]
Query :
objects = sift({"a.b.status":{"$in": [0, 2]}}, data);
//result = 1, expected result = 2
objects = sift({"a.b.status":{"$in": [0]}}, data);
//result = 0, expected result = 1
objects = sift({"a.b.status":{"$in": [2]}}, data);
//result = 1, expected result = 1
Could you please help?

Should be fixed with 2.x.

authors: crcn roshan-built-io


text:
Apple Event timed out..

I have tried 2-3 times this dmg I need to share with someone and all the time I bump on this:
hdiutil: resize: completed successfully Mounting disk image... Device name:     /dev/disk7 Searching for mounted interstitial disk image using /dev/disk7s... Mount dir:       /Volumes/dmg.ke2T6f Copying background file 'easyred2_1324780.jpg'... Running AppleScript to make Finder stuff pretty: /usr/bin/osascript "/var/folders/57/69z69th12597j72xkrz7cn0w0000gn/T/createdmg.tmp.XXXXXXXXXX.F0nuhm1U" "dmg.ke2T6f" /var/folders/57/69z69th12597j72xkrz7cn0w0000gn/T/createdmg.tmp.XXXXXXXXXX.F0nuhm1U:395:407: execution error: Finder got an error: AppleEvent timed out. (-1712) Failed running AppleScript Unmounting disk image... "disk7" ejected.
Could it be cause of the size of the app which is 12.5GB?
Thanks in advance for looking at this!

Okay, this time seems it was permissions.. Full Disk Access.
You might want to update the script someday to include this on first run or something checking this with if/error etc.
We need to get the bundle Identifier first, for an app it would be like:
mdls -name kMDItemCFBundleIdentifier -r /Applications/Safari.app[/code] It will give you something like: com.apple.Safari%`
Replace /Applications/Safari.app with the create-dmg path
like so mdls -name kMDItemCFBundleIdentifier -r /usr/local/Cellar/create-dmg/1.2.1./bin/create-dmg
This will suddenly give (null)%
But if you get it from the path and drag and drop it to the System Settings > Security & Privacy > Privacy > Full Disk Access panel it will be added
Doing the above, keeps the Apple Event from timeout.
Again thanks so much for making this tool. Hopefully that update will help others that using it on latest Apple systems. :)

Alternative solution via Terminal (doesn't work on Big Sur, which I am testing it right now)
sudo sqlite3 "/Library/Application Support/com.apple.TCC/TCC.db"
INSERT INTO access (service, client, client_type, allowed, prompt_count) VALUES ('kTCCServiceSystemPolicyAllFiles', '/usr/local/bin/create-dmg', 0, 1, 1);

We experience the same issue our our self hosted arm64 github runner.

authors: infeo silicooon

repo: create-dmg/create-dmg


text:
Support service instances having environment variables and exposed ports

part of: https://github.com/creek-service/creek-system-test/issues/10
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage increased (+0.5%) to 98.934% when pulling ccf217020e39e02b62f1b0a236b700a41528a631 on expose_port into 8a28739350e64281548a12b3efa55bab3f358ec8 on main.

authors: big-andy-coates coveralls

repo: creek-service/creek-system-test


text:
🛑 Aqsalaan Logistics Website is down

In 35a2cdb, Aqsalaan Logistics Website (https://aqsalaanlogistics.co.tz/) was down:

HTTP code: 403
Response time: 119 ms

Resolved: Aqsalaan Logistics Website is back up in 88a2a7c.

repo: crefati/monitoring


text:
🛑 MyTrip Connector Tourism Website is down

In 8d3aaa4, MyTrip Connector Tourism Website (https://mytripconnector.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MyTrip Connector Tourism Website is back up in bddce7b after 9 minutes.


text:
Reorder reset and add to pool to avoid adding connections with remain…

…ing work.  Utilize atomic operations to avoid set(0) at wrong time concurrently.

In my testing I found that this change had a significant impact on performance when more concurrent operations where being attempted than connections in the pool.

Thanks! I don't use this library as much anymore so I don't know when I'll be able to look real close to check for leaks or concurrency issues (I'm sure there are none). I may request a change or two on formatting/spacing (e.g. around operators, after if keyword, around lambda parameters, but not before closing parens).

Thank you for the feedback.  Do you have a checkstyle that I can use to ensure I meet your formatting standards?  I've eyeballed the change and it appears similar to your style.
I'm curious if you use a different driver for your postgres work or if you've simply moved to another database.

I don't have a checkstyle I'm afraid. I have left the JVM ecosystem entirely for the most part.

authors: cgenrich cretz

repo: cretz/pgnio


text:
Update conmon-rs to v0.6.4

What type of PR is this?
/kind ci
What this PR does / why we need it:
Update conmon-rs to the latest release.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/approve
/lgtm

authors: kwilczynski saschagrunert

repo: cri-o/packaging


text:
URL Link to the PR is incomplete

Describe the bug
The Plugin is installed locally on an AzureDevOps Server 2019 (on premise).
All the PRs are listed correctly. But when I click on the PR, the link to the PR is incomplete.
The regular URL Scheme is http://[DevOpsServer]:8080/tfs/[collection]/[teamproject]/_git/[repository]/pullrequest/[pr]
The current URL of the PR manager is: http://[DevOpsServer]:8080/tfs/[collection]/[teamproject]/_apps/hub/caribeiro84.pull-request-manager-hub.view
But the Link points to  http://[DevOpsServer]:8080//[teamproject]/_git/[repository]/pullrequest/[pr]
The iis Application Path and the collection name are missing.
Do I have to configure something or is this a bug?

Same issue seen here with ADS 2020 on premise.

Thanks for both of you for raising this issue, I will try to find some buffer to work on this.

authors: cribeiro84 daniellessard smuddy


text:
SAFEARRAY_1D structure

Is the SAFEARRAY_1D structure correct?
A quick examination it  doesn't apear to match up in structure  size.
Shouldn't Win64 be pvData As LongPtr instead of LongLong  ?
From
Public Type SAFEARRAY_1D
    cDims As Integer
    fFeatures As Integer
    cbElements As Long
    cLocks As Long
    #If Win64 Then
        dummyPadding As Long
        pvData As LongLong
    #Else
        pvData As Long
    #End If
    rgsabound0 As SAFEARRAYBOUND
End Type

Shouldn't it be the X32 requires the padding not the  X64?
#If Win64 Then
pvData As LongLong
#Else
dummyPadding As Long
pvData As Long
#End If
Too early think if the padding is in the correct  order.  Makes me think if I need to fix my X32 SafeArray  structures.
I prefer using the LongPtr when referring to addresses.   Bit rusty on  SafeArrays was organising my old SafeArray and memory functions was checking out your memory library.  Not sure  you had a FillMemory function.
I did some safearray manipulation to  process dictionary keys.
https://github.com/MarkJohnstoneGitHub/VBA-IDictionary/blob/master/scr/ManagedCharSafeArray.cls
https://github.com/MarkJohnstoneGitHub/VBA-IDictionary/blob/master/archive/Archive V2.0/src/TextEncoderUnicode.cls

The x32 structure is 4-byte aligned so no padding needed. Definitely needed for x64.

Argh yes you're  correct the X64 requires the padding.
I checked out my old post on https://stackoverflow.com/questions/18784470/where-is-safearray-var-type-stored/57729377#57729377
The memory dump  I posted displays the four bytes of padding required.
I think saw some old code I had in the TextEncoderUnicode.cls with fill memory.  Found a some memory dump code I used for testing possible needs some cleaning up.

authors: MarkJohnstoneGitHub cristianbuse

repo: cristianbuse/VBA-MemoryTools


text:
Cleanup type expansion in crochet_infer

[x] merge key_of.rs into expand_type.rs
[ ] simplify expansion of mapped types
[ ] update value AST to support numeric keys in object literals

Codecov Report

Merging #371 (cbe67be) into main (7b3023b) will decrease coverage by 0.20%.
The diff coverage is 81.98%.

@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
- Coverage   88.98%   88.78%   -0.21%
==========================================
  Files          42       41       -1
  Lines        6155     6186      +31
==========================================
+ Hits         5477     5492      +15
- Misses        678      694      +16

Impacted Files
Coverage Δ

crates/crochet_infer/src/lib.rs
97.51% <ø> (ø)

crates/crochet_ast/src/types/obj.rs
53.84% <75.00%> (+2.41%)
:arrow_up:

crates/crochet_codegen/src/d_ts.rs
76.15% <75.00%> (-0.11%)
:arrow_down:

crates/crochet_infer/src/expand_type.rs
75.88% <79.68%> (+1.78%)
:arrow_up:

crates/crochet_infer/src/util.rs
87.93% <80.00%> (-0.19%)
:arrow_down:

crates/crochet_dts/src/parse_dts.rs
88.55% <100.00%> (-0.08%)
:arrow_down:

crates/crochet_infer/src/infer.rs
95.08% <100.00%> (ø)

crates/crochet_infer/src/infer_expr.rs
95.09% <100.00%> (ø)

crates/crochet_infer/src/infer_pattern.rs
91.08% <100.00%> (ø)

crates/crochet_infer/src/infer_type_ann.rs
82.91% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter kevinbarabash

repo: crochet-lang/crochet


text:
Oneclick deploy to Centaur

Deploy Oneclick to Centaur to ease post-processing (processed results will be kept in the archive with computation files).
Ideally update source code at /home/eacirc/src and create an out-of-tree CMake build at /home/eacirc/oneclick
Centaur may not have the required minimal versions of compilers and CMake (consult with Mirek). Build target to avoid building EACirc may be necessary (consult with @xtracko ).

Only executable could have been deployed. For details see https://github.com/crocs-muni/EACirc/wiki/Oneclick@Centaur

authors: LuboO mathius

repo: crocs-muni/EACirc


text:
Can I access .meta files from my script?

It would be perfect for my script. I making a tires spending/types/selling script and enhanced tuning like add one more gear & incrase speed if transmission lvl 3 installed. Anyway I sooo want to get access to handling.meta, wheelfx.dat and carcols.ymt

Not with SHVDN

authors: GARMSK crosire

repo: crosire/scripthookvdotnet

license: Zlib


text:
[Bug]: Role.iam silently removes [] from spec.forProvider fields

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)

iam.aws.upbound.io/v1beta1 - Role

Resource MRs required to reproduce the bug
apiVersion: iam.aws.upbound.io/v1beta1
kind: Role
metadata:
  name: role-with-inline-policy
spec:
  forProvider:
    assumeRolePolicy: |
      {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Effect": "Allow",
            "Principal": {
              "Service": "eks.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
          }
        ]
      }
    managedPolicyArns: []
    inlinePolicy:
      - name: "my_inline_policy"
        policy: |
          {
            "Version": "2012-10-17",
            "Statement": [
              {
                "Effect": "Allow",
                "Resource": "*",
                "Action": "ec2:Describe*"
              }
            ]
          }

Steps to Reproduce
Start running kubectl get -o yaml role.iam.aws.upbound.io --watch
Apply the manifest to the cluster. I observe the same behavior regardless of whether it is server-side or client-side applied.
Observe that while the very first version of the resource contains managedPolicyArns: [] as specified, every subsequent version has the key removed.
Here are the first few observed versions of the resource:
---
apiVersion: iam.aws.upbound.io/v1beta1
kind: Role
metadata:
  annotations:
    meta.upbound.io/example-id: iam/v1beta1/role
  creationTimestamp: "2024-06-12T23:37:16Z"
  generation: 1
  labels:
    testing.upbound.io/example-name: role
  name: role-with-inline-policy
  resourceVersion: "5128"
  uid: f6ff7514-ffd1-44be-ab15-e4b3790f2ca8
spec:
  deletionPolicy: Delete
  forProvider:
    assumeRolePolicy: |
      {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Effect": "Allow",
            "Principal": {
              "Service": "eks.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
          }
        ]
      }
    inlinePolicy:
    - name: my_inline_policy
      policy: |
        {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Resource": "*",
              "Action": "ec2:Describe*"
            }
          ]
        }
    managedPolicyArns: []
  managementPolicies:
  - '*'
  providerConfigRef:
    name: default
---
apiVersion: iam.aws.upbound.io/v1beta1
kind: Role
metadata:
  annotations:
    meta.upbound.io/example-id: iam/v1beta1/role
  creationTimestamp: "2024-06-12T23:37:16Z"
  generation: 2
  labels:
    testing.upbound.io/example-name: role
  name: role-with-inline-policy
  resourceVersion: "5129"
  uid: f6ff7514-ffd1-44be-ab15-e4b3790f2ca8
spec:
  deletionPolicy: Delete
  forProvider:
    assumeRolePolicy: |
      {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Effect": "Allow",
            "Principal": {
              "Service": "eks.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
          }
        ]
      }
    inlinePolicy:
    - name: my_inline_policy
      policy: |
        {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Resource": "*",
              "Action": "ec2:Describe*"
            }
          ]
        }
    tags:
      crossplane-kind: role.iam.aws.upbound.io
      crossplane-name: role-with-inline-policy
      crossplane-providerconfig: default
  initProvider: {}
  managementPolicies:
  - '*'
  providerConfigRef:
    name: default
---
apiVersion: iam.aws.upbound.io/v1beta1
kind: Role
metadata:
  annotations:
    crossplane.io/external-name: role-with-inline-policy
    meta.upbound.io/example-id: iam/v1beta1/role
  creationTimestamp: "2024-06-12T23:37:16Z"
  generation: 2
  labels:
    testing.upbound.io/example-name: role
  name: role-with-inline-policy
  resourceVersion: "5130"
  uid: f6ff7514-ffd1-44be-ab15-e4b3790f2ca8
spec:
  deletionPolicy: Delete
  forProvider:
    assumeRolePolicy: |
      {
        "Version": "2012-10-17",
        "Statement": [
          {
            "Effect": "Allow",
            "Principal": {
              "Service": "eks.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
          }
        ]
      }
    inlinePolicy:
    - name: my_inline_policy
      policy: |
        {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Resource": "*",
              "Action": "ec2:Describe*"
            }
          ]
        }
    tags:
      crossplane-kind: role.iam.aws.upbound.io
      crossplane-name: role-with-inline-policy
      crossplane-providerconfig: default
  initProvider: {}
  managementPolicies:
  - '*'
  providerConfigRef:
    name: default
---

What happened?
The managedPolicyArns field in the iam Role resource is a bit unusual. Its description says that setting an empty array will result in disassociating any policies attached out-of-band, while setting it to null will simply ignore attached policies.
I would like to use crossplane to enforce that additional policies are not attached to a certain IAM role, but it seems that the provider (or some other part of the reconciliation machinery) is removing the explicitly set [] value, so I can't actually get the managed resource to have the state it would need to enforce no additional policies.
Relevant Error Output Snippet
No response
Crossplane Version
1.14
Provider Version
1.6.0
Kubernetes Version
v1.30.0
Kubernetes Distribution
kind
Additional Info
No response

We're seeing the exact same behavior... thanks for opening this bug.

The issue is caused by the omitempty tag in the type definition. This is generated code, and as far as I can tell upjet does not expose the ability to configure it, instead just always adding omitempty to every Field it creates.
I removed omitempty from the generated code and ran the provider locally, and this resolved the bug. The provider no longer removed the field from spec.forProvider, and it correctly enforced that externally-attached policies should be detached during the reconciliation loop. I did a little bit of testing of the more common use case of not specifying spec.forProvider.managedPolicyArns, and I didn't see any issues, although I wouldn't consider my tests exhaustive.
@ulucinar Do you remember why we're always setting omitempty? Conceptually, it seems unnecessary, and while it's harmless in most cases, it's causing a problem here where the empty state is meaningful.

We discussed this at the SIG-Upjet meeting today. I think the video gets automatically uploaded to youtube, but I don't know the exact link.

We need omitempty because the ManagedPolicyArns field has type []*string, which is a slice of pointers to strings, not a pointer to a slice of strings (or a pointer to a slice of pointers to strings), so there's no way to store a null value in a way that's distinct from an empty list. Similarly, InlinePolicy has type []InlinePolicyParameters, which has the same issue.
Because of that golang type, at the golang level we cannot distinguish between a missing/unspecified/null value and one that is set to an empty array. Since being able to tell when a user has specified a field or not is so important to crossplane providers, we chose to interpret "either null or empty" as "null" rather than "empty", which is what the omitempty annotation does. The unfortunate consequence is that declaring the user's intent that a field be defined and set to an empty collection becomes impossible.
There were several questions around XRM fidelity, and a desire to give @mergenci and @turkenf some more time to re-familiarize themselves with the history. We plan to discuss it again at the next meeting in 2 weeks.

Background and terminology:
In AWS IAM, a role supports two different types of policies: managed and inline. The main difference is that an inline policy can only ever be attached to a single role, while a managed policy can be attached to zero or more roles, groups, or users. They are also counted differently against various AWS quotas.
A managed policy can either be AWS-managed and simply referenced by the AWS-documented ARN, or customer-managed, and created by a Policy managed resource. The RolePolicyAttachment managed resource declares that a particular managed policy should be attached to a role, and detaches it when the managed resource is deleted. It uses the role name, together with a timestamp, as its external name and terraform id.
The RolePolicy managed resource declares that a particular role should have a particular inline policy, and deletes that policy when the managed resource is deleted. It uses the name of the inline policy as its external name (and the combination of policy name and role name as its terraform id).
When the Role resource was first added to the v1beta1 apiVersion, both inlinePolicy and managedPolicyArns were only present in the status.atProvider fields of the Role managed resource, and the RolePolicy resource was skipped, possibly due to some misunderstanding around the slight, nuanced difference between inline and managed policies.
This left no way to manage inline role policies using this provider until version 0.40.0, which moved inlinePolicy and managedPolicyArns to also be in spec.forProvider of the Role, and added support for the RolePolicy resource.
It's also worth noting that at the time of provider release v0.40.0 we were still forking a terraform cli process for every reconciliation of every managed resource, which was extremely resource-intensive. There were some short-term pressures for ways to reduce the number of managed resources, that became moot once we switched to the no-fork architecture with dramatically improved performance.
References:
I mentioned at the meeting finding some reference that well-behaved kubernates operators should treat absent keys and empty values identically. I looked for and wasn't able to find the reference I remember. Here are two semi-related ones I could find.
https://github.com/kubernetes/kubernetes/pull/125317/files
This is a (recent) discussion related to distinguishing nil vs empty in Server Side Apply. It seems only peripherally related, but shows the kubernetes maintainers distinguishing between nil and empty arrays/objects.
https://github.com/kubernetes/kubernetes/issues/124050 Includes the quote

I read in https://github.com/kubernetes/kubernetes/issues/70281 that Kubernetes should treat absent keys, empty values (in this case, an empty map), and null values the same.

although I could not find that message in the linked issue.
#745 contains significant discussion around the decision to add inlinePolicy and managedPolicyArns to the Role MR.
Some possible approaches for a solution:

Change the golang type used for terraform List/Set fields to use pointers to slices instead of slices, and remove omitempty. This seems like the most "correct" approach, and would provide broader benefits to all upjet-based providers by allowing them to differentiate between null and [], but is probably also the most work, especially as far as regression testing.
Add separate detachAllManagedPolicies and detachAllInlinePolicies boolean fields to the Role's spec.forProvider, and remove spec.forProvider.managedPolicyArns and spec.forProvider.inlinePolicy. This would (mostly) remove the possibility of double-specifying attachments, leading to races like the one in #929, and support declaring "There should be zero [managed|inline] policies", but not declaring "There should be this list of [managed|inline] policies and no others". If we do this approach, we'd need to make a plan for how to handle existing resources/manifests that contain the removed fields in their spec, possibly by bumping the api version.
Change the decision to support the use case of wanting to delete all inline/managed policies for a resource (which @jeanduplessis cited as the main reason for adding the otherwise-duplicative inlinePolicy and managedPolicyArns fields to spec.forProvider, and update the documentation accordingly.

authors: diranged mbbush

repo: crossplane-contrib/provider-upjet-aws