Couldn't find a way to get a pubsub connection with a sentinel-based topology

Hi,
If I create a connection like in this example from the wiki:
RedisClient redisClient = RedisClient.create();

StatefulRedisMasterSlaveConnection<String, String> connection = MasterSlave.connect(redisClient, new Utf8StringCodec(),
        RedisURI.create("redis-sentinel://localhost:26379,localhost:26380/0#mymaster"));
connection.setReadFrom(ReadFrom.MASTER_PREFERRED);

How can I create a pubsub connection ? Doing it straight from the redisClient fails (no URI).

Master/Slave connections have a strong focus on slaves and read routing. Use regular Pub/Sub connections with a Sentinel URL:
RedisURI redisUri = RedisURI.create("redis-sentinel://localhost:26379,localhost:26380/0#mymaster");
RedisClient client = RedisClient.create(redisUri);

RedisPubSubConnection<String, String> connection = client.connectPubSub();

See also the wiki for further details.


Create a loading placeholder.

The page while communicating with database will display "Please wait"
placeholder with an animation.

This is what it looks like.


Feat/update utilization contract

Bumps platform-client-sdk-go from 116 to 119, I need the new version before I can put up new PRs with utilization labels.
This version bump causes resource_genesyscloud_routing_utilization and resource_genesyscloud_user to break, as there was a contract change. A class was renamed from Utilization to UtilizationResponse, and that change is being made here to keep those resources working. I ran a test in each resource and they passed.
However, this bump is causing an issue when running "go generate".
genesyscloud_recording_media_retention_policy_proxy.go is breaking, because getFormsEvaluationFn is supposed to return Evaluationform, but the api is returning Evaluationformresponse. I assume it's a similar change to my utilization one, but I don't know for sure, so I didn't change it, as I don't know the whole process.
If I should try to fix the above, please let me know. I just wanted to ask for guidance before changing things I'm unfamiliar with.
This is my first PR to this repo, so apologies in advance for mistakes or if I'm jumping the gun on this, and should wait for you guys to update the version. Please feel free to decline this PR.

Hello, @charliecon, I've updated the Evaluationform in the 3 places the compiler was complaining at.


On Intel Haswell IGPs on Windows 8, materials with normal maps appear overly dark (3D)

This is reproducible with this demo: https://github.com/Calinou/fps-test
This happens in both editor and game.
Note how the pillars are overly dark, but the grass isn't (it has no normal map in use).

I can confirm this is true for me with a Haswell, but with Linux Mint 17.1

I can confirm this is true for me with a Haswell, but with Linux Mint 17.1

I don't think the Platformer 3D demo uses any normal maps.

Oh okay. I couldn't figure out what was wrong with your demo because I had no frame of reference, but I'm guessing grass was supposed to be there and I saw none. More importantly it runs awfully slow. I could not get it to chug faster than 4 frames a second. Might be on my end as I am not using the best drivers, but the 3D demos that come with it work fine for me.

It seems to affect only TestCubes, not models imported with Better Collada.
I will close this until I get better confirmation of this bug.


Rename ratelimit and authTypeEnable configs

Purpose
This will rename the apiRatelimit, OperationRatelimit and authTypeEnabled configs in apk conf.
Fixes

https://github.com/wso2/apk/issues/1727

Codecov Report
Patch coverage has no change and project coverage change: +0.01% :tada:

Comparison is base (b465631) 25.46% compared to head (3f9562c) 25.47%.
Report is 34 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1728      +/-   ##
==========================================
+ Coverage   25.46%   25.47%   +0.01%
==========================================
  Files         262      131     -131
  Lines       30304    15162   -15142
  Branches     5116     2563    -2553
==========================================
- Hits         7716     3863    -3853
+ Misses      22326    11168   -11158
+ Partials      262      131     -131

Flag
Coverage Δ

adapter
25.55% <ø> (-0.02%)
:arrow_down:

common-controller
1.11% <ø> (ø)

config-deployer-service
26.41% <ø> (+0.08%)
:arrow_up:

idp-domain-service
80.10% <ø> (ø)

router
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


NoSql time series database ?

Hi
Nice job, thanks
Can we investigate to use time series NoSql database like elasticsearch or prometheus ?
these databases are designed to return a lot of logs
Regards

None of those are supported by Prisma, which is the primary database connector.


HOTT-962: Update rules data

Jira link
HOTT-962
What?
I have added/removed/altered:

[x] Updated the rules of origin data
[x] Added check for duplicate rules
[x] Expose the Alternate rule data in the API
[x] Allow blank rules in the validator

Why?
I am doing this because:

We require updated rules of origin data

Agreed, but we'd probably end up with the files in the repo anyway - they are big but not that big and shouldn't change that often and they gzip well because they're text. Pulling them in from external brings its own complications anyway.


Explicitly install OC as one of the build steps

Error: Error: Unable to locate executable file: oc. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

https://github.com/hibernate/hibernate-github-bot/actions/runs/12347663679/job/34466352632
oc should've been installed by default according to the https://github.com/redhat-actions/oc-login/blob/dfbd9912672664f9df2023c1c16e07bcf306043c/README.md#getting-started
but the build complains about it 😖
looking at the logs of this failing deploy-build:
Operating System
  Ubuntu
  24.04.1
  LTS

and in the others e.g. for search.quarkus.io:
Operating System
  Ubuntu
  22.04.5
  LTS

Both request a ubuntu-latest... according to https://github.com/actions/runner-images/blob/5c8a14c94ce4ce691feb225859daa030c5ff896f/README.md it should've been a 22...
Do we report this to the runner-images or .... (since oc should be available by default on these...)

Do we report this to the runner-images or .... (since oc should be available by default on these...)

The lack of oc in Ubuntu 24 appears to be on purpose; official documentation from GitHub lists oc on Ubuntu 22 but not on Ubuntu 24:

https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md
https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md

I suppose you can try to find the reason for this change, or look for already reported issues, but I doubt this will lead anywhere.
The fact 24 was used instead of 22 for ubuntu-latest might be due to a rollout in progress? Still, similarly if you can't find any announcement about that, it's worth reporting.
In any case, I think this change is worth merging: it'll shield us from this problem ever happening again, and will ensure we're using the latest version of oc.

OpenShift CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.

https://github.com/actions/runner-images/issues/10636
No need to open a ticket, I suppose 😄
I'll add this update to other repositories where we use oc login


osf.io/framework/auth/cas.py action valuable don't have any values.

When logging in osf through local accounts, line 264 action valuable in cas.py don't have any values.
But the code is implemented to use action valuable.
To prevent this, it might be fixed below.
line 263 in osf.io/framework/auth/cas.py
Before
    if cas_resp.authenticated:
        user, external_credential, action = get_user_from_cas_resp(cas_resp)
        # user found and authenticated
        if user and action == 'authenticate':
            # if we successfully authenticate and a verification key is present, invalidate it
            if user.verification_key:
                user.verification_key = None
                user.save()

After(fixed)
    if cas_resp.authenticated:
        user  = get_user_from_cas_resp(cas_resp)[0]
        external_credential = get_user_from_cas_resp(cas_resp)[1]
        action = get_user_from_cas_resp(cas_resp)[2]
        # user found and authenticated
        if user and action == 'authenticate':
            # if we successfully authenticate and a verification key is present, invalidate it
            if user.verification_key:
                user.verification_key = None
                user.save()

I'm very sorry, I misunderstood it.


link: :force doesn't link if already installed.

Hi
I just set up development for an application I'm working on that uses Brewfile, which has:
brew 'gettext', link: :force

I already had gettext installed, but not linked. After brew bundle running, it was still not linked.
I understand depending on linking isn't a great idea, but I'd still expect this to force link even though it is already installed, just so that it matches the Brewfile.
Thanks,
Adam

Yes, I agree. We'd accept a pull request to fix this.


[iOS/Android][Frictionless SDK consumption]

What platform is your feature request related to? (Delete other platforms).

Android
iOS

Is your feature request related to a problem? Please describe.
try find out issues developers may facing using our mobile SDKs, and understand the frictions devs are facing, and remove the frictions.

P.R out with change : https://github.com/microsoft/AdaptiveCards/pull/3633/
@Aditya0603 to check.


duplicate files docs/CONTRIBUTING.html and docs/contributing.html

When cloning the repo on MacOS I get a warning:
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

  'docs/CONTRIBUTING.html'
  'docs/contributing.html'

Thanks @pbodnar - much appreciated. Are you doing most of the maintenance these days?

Thanks @pbodnar - much appreciated. Are you doing most of the maintenance these days?

Yes, I do, I was given contributor rights by Mi Yu some time ago. I mostly do some minor updates or merge PRs when I have time and when in a good mood... :) So, contributions are welcome, but I cannot guarantee when I will get to them...

OK, so I have removed the extra "docs/CONTRIBUTING.html" file and added a README file with a deprecation note. I guess that this could suffice for now.


The proved implementation of the priority queue is slow

Currently, from some benchmarks, it seems that the huge bottleneck is Pqueue.extract_min_exn (which re-balances the priority queue). The Domain_elt.compare is also called a lot (probably due to cancelled tasks). We should take a deeper look on the implementation.

I've noticed quite a few allocations in the major heap with this implementation but with other observation tools, it seems that Miou_pqueue (the proved impl.) isn't Miou's biggest problem. There are still some interesting areas for optimisation (inlining of Vector.get, the functor doesn't allow you to inline the function compare elements, etc.). It's clearly a low priority.
I'll leave this issue open, however, if one day implementation becomes a real problem.


eks: Run cilium-cli inside a container

Update {eks,eks-tunnel}.yaml to run cilium-cli inside a container instead of using cilium-cli-test-job-chart.
Ref: #2623
Ref: #2627
Ref: cilium/design-cfps#9

✅ success

eks: https://github.com/cilium/cilium-cli/actions/runs/9672643155/job/26685298688?pr=2631
eks tunnel: https://github.com/cilium/cilium-cli/actions/runs/9672643150/job/26685413902?pr=2631

marking it ready for review


Exec tachikoma update<PHONE_NUMBER>3346

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

@sanemat are you aware of all these empty commit PR ?

@j0k3r Yes. Interval pull request (with empty commit) kicks tests on travis-ci. Sometimes I see failing test. E.g. https://github.com/sanemat/tachikoma/pull/168 This is like a health check.
Can I help you?
tachikoma gem supports none, bundler, carton, david, composer and cocoapods.
But tachikoma.io web service supports none, bundler, carton and david.
http://tachikoma.io/configuration.html
Sorry for the inconvenience.
I recommend this article(in Japanese) for composer users and cocoapods users.
http://packsaddle.org/articles/interval-pull-request-update-overview/
TL;DR

Kick interval dependency update (e.g. from heroku)
Run composer update on your CI
Send pull request

:smile_cat: Thanks


Using heuristic evaluation to inform the user experience strategy of a product

Describe the blog post your would like to write
This blog will cover what a heuristic evaluation is. How it can benefit cloud tooling vs. a website and more, the way to conduct a heuristic evaluation and best practices offered to the community
What is the title of the blog post?
Using heuristic evaluation to inform the user experience strategy of a product
Who are the authors?
Ray and Aparna
What is the proposed posting date?
July 19th; write up is ready; see quip

Attached blog draft for review. @nateynateynate - Can you help move this into a PR for review?
UX Heuristics Blog Post - AS comments and ray additions.docx

I'll have to create a community member profile for Ray Salas. Will reach out for details privately.

Completed with #3091


Change number of custom vars and fix concurrent error

Supporting more than 5 Custom Variables #69
Concurrency issue when setting custom variables #89

What about wrapping an instance of HashMap instead of extending it? Would make it way easier to guard (just synchronization on 3 methods). Other calls like Map.clear() might still cause issues otherwise, I'm still on mobile, can't check the sources well.
We only need a few specific methods anyways and not all HashMap has to offer.
What do you think?

@d4rken I've got rid of extending HashMap, as always good idea :+1:

Sorry took me a bit longer.
Tests look good, but I may have found a sleaker solution.
Let me know what you think regarding my comments.
Should we do another release after this is merged into dev?
On a side note, shouldn't we submit PRs via forks ;)?

@d4rken all comments addressed/fixed.

Should we do another release after this is merged into dev?

Sure!

On a side note, shouldn't we submit PRs via forks ;)?

Honestly I Didn't think about it before You asked, for me it was easier to maintain only remote.

:+1: I think this can be merged into dev now.
Then we could either do a release with that state or see if we want to include something for #92


Compiling on fedora

Hi,
I'm trying to build this package on fedora, since I have trouble using it:
First I install
dnf install libevent-devel pcre-devel gc-devel libmongo-client-devel

While downloading the code via git, I can not build this library crystal build src/mongo.cr, running it lead me to a
/usr/lib/gcc/x86_64-redhat-linux/5.3.1/../../../../lib64/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'

cc compilation crashes

in fact the command
cc -o "mongo" "${@}"  -rdynamic  -lmongoc-1.0 /opt/crystal/src/ext/libcrystal.a -levent -lrt -lpcre -lgc -lpthread -ldl

lead to this.
added -shared options isolve the problem

with the latest version of crystal, I have
./.crystal/root/mongo.cr/src/mongo.cr/Fiber.o: In function `*Fiber#push_gc_roots<Fiber>:Void':
Fiber:(.text+0x17d): undefined reference to `GC_push_all_eager'
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: `cc -o "mongo" "${@}"  -rdynamic  -lmongoc-1.0 /opt/crystal/src/ext/libcrystal.a -levent -lrt -lpcre -lgc -lpthread -ldl`

without changing anything in the code
do somebody understand ?


Setup server for deployment

[ ] Run the application on a server
additional
[ ] CI / CD

[ ] install fop and generate the letters

deplozed at http://wgcard.zuercher.io (auto deployment added and reset daily 01:00)

well sorry to reopen this, but when i open it in firefox it blocks the loading of the xsl stylesheet because of the Content Security Policy

I also see you run the internal php development webserver which might be problematic and doesn't allow setting such headers for files as far as i know... :/


Lower node version minimum to 18 from 19 to support usage on Vercel.

Lower node version minimum to 18 from 19 to support usage on Vercel.
I haven't actually been able to get this to work, but it should... I can't imagine there's a specific node 19 feature that would make it incompatible?

Testing

Codecov Report

Merging #1 (86dc73a) into main (d2e2480) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage   33.33%   33.33%
=======================================
  Files           3        3
  Lines         117      117
  Branches       22       22
=======================================
  Hits           39       39
  Misses         78       78

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Investigate a loading bar when starting the app because the map can take several seconds to load on older devices

Not doing this, closing


Recommend replicating encryption key for API data encryption at rest

This is split out from PR https://github.com/kubernetes/website/pull/33285 in order to make a review more likely. See that PR and its previews to show the changes in a wider context.
When using API encryption at rest without KMS, document that the same encryption key must be securely replicated to all the hosts that run a kube-apiserver.
/sig security docs
/language en

/approve


Fixed ucwords to be functionally the same as in-built PHP version

As you can see, this breaks the tests with TurkishUtf8.
ucfirst and lcfirst need no patch at all, they both have the behavior you expected them to have.
For ucwords, "space" is not the only character that should trigger capitalization.
You need a regexp to catch all first chars of "words". I suggest /\b(.)/ and applying mb_convert_case on the match

My bad, I didn't run the TurkishUtf8Test locally. Good point on the word boundaries. I've updated ucwords to use the regex you provided. The unit tests all pass locally now.
The reason I changed ucfirst and lcfirst is that previously they used ucwords and I wanted to ucwords to use ucfirst. My latest commits doesn't require that anymore, so I've changed them back. However, ucfirst and lcfirst both used non multibyte functions (substr and strlen). Is that correct?
One other tangential thing, in the ucfirst and lcfirst functions, you use iconv_substr. This function is about 60% slower than mb_substr. Can they be changed over?

Yes, using strlen+substr is on purpose, because in this case, we don't need multi-byte handlig but for the first utf-8 char.
Are you sure about iconv_strlen being faster than mb_strlen? I bet this is ot true on every platform (Windows, Linux+libc, other). Do you have any facts?

Thanks you @martinkiva


feat: add secondary button in menu item

SUMMARY:
feat: add secondary button in menu item
GITHUB ISSUE (Open Source Contributors)
JIRA TASK (Eightfold Employees Only):
CHANGE TYPE:

[ ] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4242cc9). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #540   +/-   ##
=======================================
  Coverage        ?   84.69%
=======================================
  Files           ?      789
  Lines           ?    16584
  Branches        ?     5768
=======================================
  Hits            ?    14046
  Misses          ?     2472
  Partials        ?       66

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

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

@ypike-eightfold This change adds a feature not yet available in the DS Figma:

It adds an additional button within Menu for actions like delete.


Decode non-Ethereum precompiles when tracing

Right now we only decode the Ethereum precompiles when tracing, we should add some way to decode extra precompiles. What are some example precomppiles from other networks?
Originally posted by @mattsse in https://github.com/gakonst/foundry/pull/1067#discussion_r835886363

Avalanche subnets that use the evm have these precompiles

0x0200000000000000000000000000000000000000
0x0200000000000000000000000000000000000001
0x0200000000000000000000000000000000000002
0x0200000000000000000000000000000000000003

More details on the interfaces are here

we can integrate them,
what we'd need is a list of:

address
function signature: <name>(<inputs>)<outputs>

@avaxmoon do you mind also leaving a comment on https://github.com/foundry-rs/forge-std/issues/134 with the list of relevant avalanche precompiles + what chain IDs they apply to + links to docs? That way we remember to include them there when implementing that

@mattsse I believe you can find all this information here

Celo has a bunch of extra precompiles here: https://github.com/celo-org/celo-blockchain/blob/91993404cdf69ff4dad810bae8ac02763ae667d8/core/vm/contracts.go#L168-L199

thanks for linking this.
It would help if you could prepare them as address + signature pairs, this would make it easier to integrate them in the codebase.

Hi @mattsse 👋 @douglasqian kindly pointed me to this Github discussion.
We'd love Celo to be fully compatible with Foundry out of the box 🙌
Regarding to your comment above:

It would help if you could prepare them as address + signature pairs, this would make it easier to integrate them in the codebase.

I put together a gist (Adding Celo to Foundry) with key information (for future reference) and @palango (from the Celo blockchain team) kindly provided a small sample of address + signature pairs to verify the format suits you.
I copied the sample below for ease of reference
0x00000000000000000000000000000000000000fd transfer                 (bytes32 sender, bytes32 recipient, uint256 amount) bytes

0x00000000000000000000000000000000000000fc fractionMulExp           (uint256 aNumerator, uint256 aDenominator, uint256 bNumerator, uint256 bDenominator, uint256 exponent, uint256 decimals) (uint256, uint256)

0x00000000000000000000000000000000000000fb proofOfPossession        (address sender, bytes blsKey, bytes blsPop) bool

0x00000000000000000000000000000000000000fa getValidator             (uint256 index, uint256 blockNumber) address

0x00000000000000000000000000000000000000f9 numberValidators         (uint256 blockNumber) uint256

0x00000000000000000000000000000000000000f8 epochSize                () uint256

0x00000000000000000000000000000000000000f7 blockNumberFromHeader    (bytes header) uint256

0x00000000000000000000000000000000000000f6 hashHeader               (bytes header) bytes32

0x00000000000000000000000000000000000000F5 getParentSealBitmap      (uint256 blockNumber) bytes32

0x00000000000000000000000000000000000000F4 getVerifiedSealBitmap    (bytes header) bytes32

My question: How does the above look to you? (i.e. would this format make the integration easier for you?)

Let's move the conversation to https://github.com/bluealloy/revm/issues/280

Just noting that one other part of compatibility would be to update StdChains and assumeNoPrecompiles in forge-std with the required Celo information

Let's move the conversation to bluealloy/revm#280. Most of these precompiles are stateful, so would like to understand how you are thinking about introducing that state, e.g. https://github.com/bluealloy/revm/blob/main/crates/revm_precompiles/src/lib.rs#L58

Will there be anything else needed besides the changes in revm for decoding, like the ABIs? Or will this just work once the precompiles are in revm?


Fix audience parameter issue

Resolves https://support-internal.wso2.com/jira/browse/APIMINTERNAL-1292

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Docker Files for Container Based Development & Testing

This will make it a lot simpler for developers to run the tests prior to
submitting their PR. This new make target, dshell, will put developers into a
bash shell, using the same container images that are used for CI.
From there deveopers can run make test integration.
I've written about this pattern on my blog:
https://rawkode.com/2018/01/27/docker-shell-pattern/

We are going to be adding TravisCI for OSX testing soon. Does that impact on this @rawkode.

That doesn't impact anything; these files don't affect anyone, or thing. They exist should anyone wish to use Docker for development and test. It's completely opt-in.

This seems like it deserve notice in the release notes, @rawkode do you feel up to writing up what would go into the release notes?
Question is "Adopt Docker Shell Pattern" the best title to have appear in the CHANGELOG. If not, what should it be? Assuming it should be different, can you update the PR title accordingly?

@rawkode Ping. Can you write up some release notes for this? Then we can get this released (probably as part of a renaming)


Publications Feature Tracker

About
Publication pages adds an easy way to create custom no-code page types, with support using a custom front matter schema and Blade templates. This feature is in development at the HydePHP develop monorepository, https://github.com/hydephp/develop/pull/685, and will be published as an official HydePHP extension tied to HydePHP v1.0.

Awesome!


inits the kubeadm upgrade docs

addresses kubernetes/kubernetes.github.io/issues/4689
note this is the first draft, just to get the ball rolling ;)
CC: @luxas

This change is

@mhausenblas please ping me when ready so I know

@luxas sure thing, scheduled for beginning of next week. Will ping you then …

SUGGESTED CHANGES TO THE TEXT
Opening paragraph
Remove comma between cluster and currently.
Before you Begin
Change "You need to have a Kubernetes cluster" to "You need to have a self-hosted Kubernetes cluster" or "You need to have a kubeadm Kubernetes cluster".
Put the note about one minor version somewhere outside of the Before you begin section.
Does upgrading etcd have to be done before you begin? If not, move the note out of the Before you begin section.
Make the steps more concise. For example:

You need to have a self-hosted Kubernetes cluster running version 1.7.x.
Read the release notes.
Back up any app-level state. For example ...

Move the note about being eventually idempotent outside of the Before you begin section.
On the master
Include a link to using curl to install the most recent version of kubeadm.
Spell out Software Defined Network.
Spell out Container Network Interface once.
No need to say, "After kubeadm upgrade you need to". Just say "Manually upgrade your Software Defined Network."
Recovering from a bad state
I don't understand what's being said here. Maybe rephrase and blend in the statement about kubeadm upgrade being eventually idempotent.

@mhausenblas any updates here?

@kargakis I'm on it

@luxas I've addressed you latest round of comments now

Merging this based on @chenopis docs review.
You can address the really small nits in a follow up if you want.


Refresh fast/README.md

Probably not 100% but way more than the current one! I can have a more thorough look in the coming days


Improve overall design of Account Information Page

-Explore ways to prompt family user to update their stage in process each time they access this area.  Consider separating My Information from My Stages or My Progress and/or having a progress bar on main page which visually depicts progress and prompts user to update.
Additionally, provide design consistency across all sub tabs

closing as duplicate


Issue757/dpl 065 cardinal pbmc isolation and cell count input files

Contributes towards #757
Changes proposed in this pull request:

Add CSV file config
Add optional params to export links
Rubocop appeasment
barcode printing requirements

Not here:

Configuration changes

Closing this as the code was merged into our Cardinal pipeline epic branch, in the following pull request - https://github.com/sanger/limber/pull/819


Controls data property is null on v0.1.54

Post v0.1.52  a controls data property now returns null.
 c2 = Container(
        data=20,
        ink=True,
        content=Text("KShs 20", size=20, color=colors.BLACK54, weight="w600"),
        margin=10,
        padding=padding.symmetric(vertical=30),
        alignment=alignment.center,
        bgcolor=colors.SURFACE_VARIANT,
        border=border.all(1, "#7284A8"),
        width=100,
        height=100,
        border_radius=0,
        on_click=compute,
        expand=1,
    )

On firing an event e.data is now null instead of 20 as in the example above. On v0.1.52 the correct value (20) was returned.

Ah, it's a good note, thanks for pointing that out!
So, before v0.1.54 Control.data is used to send its value to Flet server and thus Flutter UI with every page update. In some controls data property value was returned in event's data. It was a "legacy" solution that was migrated from Pglet where it wasn't easy way to know which control generated the event.
Now Control.data is not used in the event callback and always stays a client - Python program: https://github.com/flet-dev/flet/commit/67fe7136f8ff5616d6e91bf8821de88809a480e3#diff-bacf19c2b12a8f3ef9649e54432fb3beeffdd0b90fdbe380448d418f566d9eeb
Also, data value is not placed into control attributes anymore: https://github.com/flet-dev/flet/commit/67fe7136f8ff5616d6e91bf8821de88809a480e3#diff-153f8fef463d23c67097e593f496229e6bb89e81ee984c450812932d1db2af43R292-R298
In the event handler instead of checking e.data you should use e.control.data which is original, unmodified value:
import flet
from flet import ElevatedButton, Page

def main(page: Page):
    def button_click(e):
        print(e.control.data)

    page.add(
        ElevatedButton(text="Test button", data=20, on_click=button_click),
    )
    page.update()

flet.app(target=main)

Like now you can put not just literal into Control.data but any object.

Ah! Perfect!


nuxt generate only causes 404

@medfreeman I'm still getting 404 when I run nuxt generate (instead of nuxtent generate with previous binaries)
JSON files are generated but it seems like pages are not compiled appropriately. For example with multiple content type example I get:
==== Error report ====
Route: '/nuxtent' thrown an error:
{"statusCode":404,"message":"This page could not be found"}

Route: '/ency' thrown an error:
{"statusCode":404,"message":"This page could not be found"}

If I serve the site, the client navigation works fine but refreshing page displays not found error.
Also related to #88, if we stick to not having binaries we have to let users specify static=true some other way, e.g. via config, so that browser URL can be set appropriately and static files can be generated.

I feel like your solution (https://github.com/nuxt-community/nuxtent-module/blob/master/lib/module.js#L131) should be equivalent to using binaries, as the only special thing I was doing was starting the Nuxt server so that server middleware could be active when pages were being generated.

If it can help you I have a small different error when a set an apiBaseUrl

my

nuxtent.config.js

module.exports = {
  content: [
    [
      'posts',
      {
        page: '/_post',
        permalink: ':year/:slug',
        generate: ['get', 'getAll']
      }
    ],
    [
      'projects',
      {
        page: '/projects/slug',
        permalink: '/:slug',
        isPost: false,
        generate: ['get', 'getAll']
      }
    ]
  ],

api: {
  baseURL: process.env.NODE_ENV === 'production'
    ? 'http://stnetwork.surge.sh'
    : 'http://localhost:3000'
}
}

my

package.json

{
"name": "example",
"version": "1.0.0",
"description": "nuxtent multiple content types example",
"author": "Alid Castano<EMAIL_ADDRESS>"dependencies": {
"@nuxtjs/axios": "^4.3.0",
"nuxt": "latest",
"nuxtent": "latest"
},
"scripts": {
"dev": "HOST=<IP_ADDRESS> PORT=3000 nuxt",
"build": "nuxt build",
"start": "HOST=<IP_ADDRESS> PORT=3000 nuxt start",
"generate": "STATIC=true NODE_ENV='production' nuxt generate",
"lint": "eslint --ext .js,.vue --ignore-path .gitignore .",
"precommit": "npm run lint"
},
"devDependencies": {
"@nuxtjs/cssnano": "^1.0.1",
"@nuxtjs/optimize": "^1.1.1",
"@nuxtjs/pwa": "^0.2.1",
"babel-eslint": "^8.0.1",
"buefy": "^0.5.2",
"bulmaswatch": "^0.5.0",
"eslint": "^4.7.2",
"eslint-config-standard": "^10.2.1",
"eslint-loader": "^1.9.0",
"eslint-plugin-html": "^3.2.2",
"eslint-plugin-promise": "^3.5.0",
"eslint-plugin-standard": "^3.0.1",
"highlight.js": "^9.12.0",
"node-sass": "^4.5.3",
"sass-loader": "^6.0.6"
}
}

@alidcastano @medfreeman
Sorry but I updated nuxtent with the version 1.0.2 and I always have exactly the same error that I posted in my screen above.


Stacked bar

Is is possible to have a stacked bar? If so which sort of options+values would do it?

It's not possible. I guess the question of how it would progressively enhance some structured (and meaningful) text is at the core of the question of how to do it - as opposed to actually writing the code. You could probably have text something like 5,3,9|6,5,9|7,3,5 to give three stacked columns delimited by | with their values delimited by a comma.
Ultimately I'm not sure that the feature is in the scope of this little jQuery plugin - though I'm happy to be persuaded otherwise.


AMBARI-23503: Fix installation issues caused by execution_command library

What changes were proposed in this pull request?
Spot fixes for execution_command library changes
How was this patch tested?
Deployed ZK on cluster
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1697/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1698/
Test FAILed.
Test FAILured.


chore: allure test reporting

Problem
Test results were hard to follow in the console output.
Also we had no history to check flaky tests
Solution
Added allure test reports that are deployed with github pages: https://waku-org.github.io/allure-jswaku/5676/#
Notes

Moved mocha config from json to js so it supports conditional changes

why do we need to create a separate mocharc for all packages?

@danisharora099
Well I just replaced .mocharc.json to .mocharc.cjs, so all the packages that contained tests already had their own mocharc.json
I guess the reason for this is that each package can be considered as a standalone project with it's own config (tsconfig, eslint, typedoc etc) and scripts (package.json).
The advantage with this is that we can run all tests(from all packages) from the root of the project or cd to a specific package and run the tests in isolation.  We can also have different configs for each package.


[Help] Get Column ID and Name

Hello, guys!
How can I get the Column ID and Name using:
onSelected:
onRowDoubleTab:
nowSecondaryTap:

Thanks a lot !

Are you able to run the sample code ? I have many error with it so I would like to know if the latest version works

I give up on "pluto_grid".
Researching a little and using ChatGPT I am using "PaginatedDataTable" to create the Grid,
Filter and interaction with the Grid cell.


Add support for MOD

Closes #1
Implementation

Define MOD as a token and identify it in the lexical analyzer.
Compile MOD to relevant instruction as defined by Yamini VM.

Waiting for corresponding PR to be merged in Yamini VM.

PR in Yamini VM merged, merging this too.


refactor: Improve auth sessions using context

Improves the current auth / session code by using react context and a "useSession()" hook that can be used anwhere (client components) in the app.

@okunamayanad review?

Noice stuff man


CLOUD-60075 Update Blueprint Name field validation message

@biharitomi plz review

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2739/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/230/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2740/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/231/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2741/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/232/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2742/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/233/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2743/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/234/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2744/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/235/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2745/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/236/

LGTM


operator datadog-operator-certified (1.7.0)

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-release-pipeline

/pipeline restart operator-release-pipeline


Add known branch exceptions to version matching

Description
Maybe doing it this way is better, since we don't "break" existing consumption elements, while just adding to already existing exception -rc-.
Forcing version-type: strict, while explicit, would probably force some installations to use a too-specific Elixir version, so we "fix" what we had to prevent that.
Closes #241.

[x] I have performed a self-review of my changes
[x] I have read and understood the contributing guidelines

@josevalim, @grzuy, this adds an exception (to loose version matching) for "known" branches main, maint, and master. Would you be so kind as to check the tests and maybe run this branch where it's failing now, so we can move to merge it? Thanks.

Looks great, thank you!

Perfect stuff. Thanks @starbelly. I'll release a patch now.

v1, v1.17 and v1.17.1 released, pointing to the latest commit.


Update the README.md to follow the recommended Action flow

As mentioned in #13 GitHub Actions is deprecating set-env so workflows that set environment variables need to be updated to use the new environment files.
Resolves #13

Thanks for helping out and fixing this :+1:

Thanks for helping out and fixing this :+1:


[doc] Fixed typo in url

First of all, thank you for your contribution!
Please makes sure that these checkboxes are checked before submitting your PR, thank you!

CheckList:
if isBugFix :

[ ] Make sure that you add at least one unit test for the bug which you had fixed.

elif isNewFeature :

[ ] Update API docs for the component.
[ ] Update/Add demo to demonstrate new feature.
[ ] Update test scripts for the feature.
[ ] Add unit tests for the feature.

@stranger26 thanks for your pull request.
I have merge your pr at here,but the pr still open because of bot broken.
Can you close this pr,please? 3Q.


Change "Symfony2" references

Please don't hesitate to reject this if there is a good reason that it is still the way/version it was … but "hype train" :wink:

Well, I'm not sure about this change.
http://symfony-reloaded.org/ was the Symfony 2 website during early development (before the switch to https://symfony.com). Changing the menu item to say Symfony 4 > Coming soon while using the old link looks weird (and the example would then have to be updated in 2 weeks to say 4.1 as 4 would be there already...).
I see 2 options here:

keep the existing example, with the reference to the old domain, but I don't think most people would understand the reference (most people joined the community long after the symfony-reloaded.org domain stopped being used, except for a redirection which still exists)
change the example entirely, in favor of an example which does not become outdated after each Symfony release

We might go for the second option

Yeah, I did wonder about the link … it does have the big PR banner down the bottom, but still.
While agreeing with all points, what I would note though, is that we've found it wrong to assume how long people have been around for, or the depth of knowledge they might have about the project and its history  … e.g. plenty of people still get confused about Bolt's :koala: references, and what does issue 1555 mean something :wink:
Ancillary to your option 2, if you want to close this please don't think it would be taken confrontationally here … otherwise, I'll have a think over coming days and try to come up with a better option. But family celebrations in Paris have me missing release.

In any case, even if we were merging the new example as is, the PR is broken: it changes the menu definition, but does not update the output in the next code block.
The fact that many people don't know the history on the early Symfony 2 development is the reason why I tend to think that option 2 would be better: remove the joke related to Symfony 2 coming soon, and give a generic example instead.
I would be happy if you could change the example that way. And no pressure about the delay. We have no deadline to update the readme.

I had a bit of time before catching the train, so I thought I'd have another attempt. This time I've been a bit more thorough.
So I have opted for s/Symfony2/Symfony/, s/Coming soon/Happy Awesome Developers/ (a hat-tip to Knp) and s/symfony-reloaded.org/symfony.com/.
Easy to tweak, happy to do so if if you have better ideas or wishes.

thanks


component fields only accept concrete type (like seq[T]) 🐛

To Reproduce 👨🔬
  component ToDo:
    messages: seq[string]
    `template`:
      tDiv:
        for i in messages.items:
          "{i} "

Error: 'seq' is not a concrete type
Expected behavior 🤔
I'd normally expect to be able to do declare all types of things to be fields of the component. Preliminary investigation on my part suggests that this behavior might be due to runtime declaration of the component, but I'm not sure.
It's worth noting that for now, the issue seems to be easy to work around for those who already understand it, since declaring the component with a default seq  allows successful functionality. This works, for example:
  component ToDo:
    messages: seq[string] = @["yello","goodbye"]
    `template`:
      tDiv:
        for i in self.messages.items:
          "{i} "

  appRoutes("ROOT"):
    "/":
      component ToDo(messages = @["wavy", "shavy"])

I found reason

This will solved in the next commit


[BridgingHeader] Provide a deterministic unique pch file path

Teach swift driver to use a deterministic path for compiled PCH output. Also when dependency scanner is updated to return a module scanning or PCH hash from the scanning result, it will add that to the code path to have an unique PCH file path for the specific compilation.

@artemcm let me know what you think about this. The dependency scanner is not yet returning the context hash for main module but that can be easily added.

@swift-ci please test

@swift-ci please test windows platform

@swift-ci please test

@swift-ci please test windows


Bug/tailwindcss - Update devenv.nix to Use Tailwind Nix Package

The base devenv.nix configuration relied on NPX to execute Tailwind CSS commands. However, for users without Node.js installed locally, these commands would fail. This update replaces NPX with the Tailwind package from Nix, ensuring compatibility regardless of local Node.js installations.

@domenkozar Here is the bug I was talking about. It's hard to work on the dev package since the pre-commit hook uses NPX and my other branches fail to commit without this.
If this can get reviewed and integrated first, it would be great!


Android uri lifetime

Description of Change
These changes should fix some people's problems to use picked content:// URIs that are stored in the meantime and can't be used later. The changes use ACTION_OPEN_DOCUMENT on Android 4.4 (KitKat) or higher, and TakePersistableUriPermission() is called after picking to keep permissions to access the content:// URIs.
I debugged the code with the sample app and picking made no difference in UI, and it didn't crash. The patch should maybe go into a beta build so that people can try out the change before publishing a release NuGet package.
@championofblocks This PR is a variation of #173, where the ACTION_OPEN_DOCUMENT intent is made configurable. Since the PR modifies the public API of the public, the change may still go into a 2.2-beta release at some point in time.
Issues Resolved

fixes #172, #158

Platforms Affected

Android

OK CI really fixed this time!

CI looks good, thanks!


Feature: Funkwhale API Integration

[ ] Implement authentication (oauth or application token?)
[ ] Poll listenings endpoint for tracks

Looks like for single-user scenarios the maloja plugin for funkwhale will be easier than setting up anything for MS.
However the funkwhale api (not subsonic) supports a listening endpoint that allows retrieving history for all users who make it available on that instance (pod?)...I can't think of a scenario where it would be more useful to have one point of control (MS) to record all users that wouldn't be equivalent to just getting all users to use the maloja plugin but maybe someone in the future will come across this with an idea...


tweaks to #1027 - single more general protocol

This PR just tweaks the protocols in #1027 to make it a bit more general. Core idea is still @ershockley 's
Differences

Only difference is that now the protocol would return the keys as they are requested from the json'gain_ab' instead of 'ab' - depending on what the columns are in the file.
Call the time column 'time' instead of 'times' or 'timestamps'

Updates

I've also added a few words of documentation and also expanded the test to work on CSV files
testing code on the CorrectedAreas-plugin

Further generalization options

Not sure if the comma separation keys = strax.to_str_tuple(itp_dict_keys.split(',')) could be handled by the URLConfig

@JoranAngevaare I made a few changes to make the protocol more generalizable (allows for passing time key as a parameter) in order for it to be backwards compatible. I also had to add an additional protocol that reformats the dict to be what the plugin expects, again for backwards compatibility.
Personally I still feel like the other protocols are a bit more transparent, even if they aren't as general as these ones, as now the urls get crazy long. But if you prefer this way we can go with this. Let me know what you think.

I've changed my mind, let's go with the general protocols but with longer urls. Probably better for longterm.


Fix error handling for ModelExperimental

Model loading errors were not getting propagated correctly in ModelExperimental. I added two unit tests but this should have been unit tested when ModelExperimental was first added.
loadAndZoomToModelExperimental.js was also not handling rejected promises correctly. I modeled it after waitForLoaderProcess.js. It's a little verbose but it should work for catching any errors.

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Set min and max width logic for notebook

Things might get wonky if things get too wide or narrow. Set reasonable defaults for the minimum and maximum widths.

Use rich's measurement.clamp.


Adding molecule tests for edpm_neutrond_dhcp role in the zuul CI

It appears that the ansible_user variable, doesn't in fact have to be set at all, so it isn't a reasonable default for user name/id. I'll look into alternatives.
https://github.com/ansible/ansible/issues/23530


Parse Data in npidata.csv file

Get this csv file parsed out to be used for both back end and front end

Completed


Question about FID calculation

Hi, thanks for your amazing project!
Anyway I was looking through your code and found that while calculating covariance matrix in fid_score.py you set ddof to 0 .
https://github.com/tqch/ddpm-torch/blob/5a2566e1583aa442ed0d5ea414da7c1d6d38261f/ddpm_torch/metrics/fid_score.py#L124
But when I look at pytorch-fid library, it seems like they didn't set ddof to 0, which mean they set ddof to None.
https://github.com/mseitzer/pytorch-fid/blob/0a754fb8e66021700478fd365b79c2eaa316e31b/src/pytorch_fid/fid_score.py#L230
Is there any reason you set ddof parameter to 0? It seems like setting ddof to 0 or not makes significant change in FID score. For example, I trained DDPM for cifar10 dataset and tried to calculate FID score. If I set ddof to 0 then resulting FID score was about 8 but when I just use default value for ddof just like pytorch-fid library did it, then resulting FID score was about 11.
Furthermore DDPM library by lucidrains (https://github.com/lucidrains/denoising-diffusion-pytorch), which is one of the most known library implementing DDPM in pytorch, also calculates FID score with ``ddof``` to default value(None)
So I was qurious about the reason you set ddof=0.
Thanks in advance!

Thanks for your kind explanation:) It helped me a lot.
May good luck always be with you!


feat: Improve unwrapping result data

Description
As a Clarity developer, I would like to be able to unwrap native data types (uint, int, string, bool) returned by read only functions and not wrapped with (ok value).
This PR:

fix incorrect regexp pattern used to unwrap utf8 string
adds unwrapBool function for unwrapping boolean values
modifies all regexp patterns to enable parsing data not wrapped with (ok value) function
adds missing unit tests

Type of Change

[x] New feature
[x] Bug fix
[ ] API reference/documentation update
[ ] Other

Does this introduce a breaking change?
no
Are documentation updates required?
no
Testing information
All modifications are covered with unit tests that can be found in unwrappingDataTypes.ts file.
Checklist

[ ] Code is commented where needed
[x] Unit test coverage for new or modified code paths
[x] npm run test passes
[ ] Changelog is updated

@zone117x, @lgalabru

unwrap should be kept for, well, unwrapping, if the function returns just u12345, then unwrap should fail instead.

unwrap should be kept for, well, unwrapping, if the function returns just u12345, then unwrap should fail instead.

Haven't though about it this way but it seems to be reasonable approach. In that case we are still missing a possibility to extract values not wrapped with (ok value) function.
Maybe we should introduce separate classes for each datatype used in Clarity (principal, uint, int, tuple, list etc.) and return instances of those classes when we call unwrapXXX ?
For example:
export class UInt {
  public value: BigInt;

  constructor(value: number | BigInt | string) {
    switch (typeof value) {
      case "number":
        this.value = BigInt(value);

      case "string":
        const pattern: RegExp = /^u?(\d+)$/
        const match = pattern.exec(value as string);
        if (!match) {
          throw new Error(`Unable to convert "${value}" to UInt`);
        }
        this.value = BigInt(match[1]);

      default:
        this.value = value as BigInt;
    }
  }

  toString(): string {
    return `u${this.value.toString()}`;
  }
}

export function unwrapUInt(input: ResultInterface<string, unknown>): UInt {
  const match = getWrappedResult(input, /^\(ok\su(\d+)\)$/);
  return new UInt(match);
}

unwrapUInt would still be used to unwrap values returned with (ok value) and if function returns just u123 we'll use new UInt(value) instead.
Those new objects could be also useful while constructing new transactions or calling read only functions.

yes, that would be a better approach, as this is something you end up implementing yourself otherwise


Color spaces JS API

Description
Exposes a JS API for the Color Spaces proposal
Rendered Proposal

https://trello.com/c/2R7Mnj6s/1-i-want-js-users-to-have-access-to-new-color-spaces

 I want JS users to have access to new color spaces.

Moved to https://github.com/sass/sass/pull/3665

 I want JS users to have access to new color spaces.


Polars: simplify code by reducing ownership

closes #1731

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1732  👈
#1703 : 2 other dependent PRs (#1715 , #1716 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite

Didn't have as much of an effect as I thought it would.


ES6 Classes

Is there a way to use the mixins in an ES6 class if not is there an update coming that works with ES6 classes.

I'm not sure, that depends on if React lets you use mixins with ES6 classes or not. If it doesn't, then no, I'm  afraid not. And I have no plans to add support at the moment.

Starting with React 16, React.createClass() will no longer be part of the core React package. Mixins are also considered harmful by the core React team. An option could be to reimplement the mixins as Higher Order Components (HoC)

Oh, that's annoying. I can't promise I'll get around to keeping up with any of that in a timely manner at the moment I'm afraid.

@caleb272 @palnes version 4.0.0 has just been published and supports ES6 classes with an HOC :)


hie-bios can't load tests and executables in subdirs

Hi,
I've noticed this strange behavior on projects with top-level cabal.project and *.cabal files in subdirs, like https://github.com/haskell-servant/servant.
First of all, versions. I use hie and hie-bios used by it is:
hie-bios version 0.5.0 compiled by GHC 8.8.3

Relevant parts of hie.yaml (generated with implicit-hie, but that should not matter):
cradle:
  cabal:
    - path: "servant-server/src"
      component: "lib:servant-server"

    - path: "servant-server/example/greet.hs"
      component: "servant-server:exe:greet"

    - path: "servant-server/test"
      component: "servant-server:test:spec"

Now, what happens if I try to load some file from the test suite:
$ hie-bios check servant-server/test/Servant/ServerSpec.hs
hie-bios: can't find file: test/Spec.hs

So, for some reason something drops servant-test/ prefix from the path, although it's present in hie.yaml.
From hie logs:
2020-06-13 00:00:47.056703 [ThreadId 15] - New cradle: /Users/maksbotan/temp/servant/servant-server/test/Servant/ServerSpec.hs
2020-06-13 00:00:47.056912 [ThreadId 15] - Found "/Users/maksbotan/temp/servant/hie.yaml" for "/Users/maksbotan/temp/servant/servant-server/test/Servant/ServerSpec.hs"
2020-06-13 00:00:47.057219 [ThreadId 15] - Module "/Users/maksbotan/temp/servant/servant-server/test/Servant/ServerSpec.hs" is loaded by Cradle: Cradle {cradleRootDir = "/Users/mak
sbotan/temp/servant", cradleOptsProg = CradleAction: Cabal}
2020-06-13 00:00:47.057403 [ThreadId 15] - Found cradle: Cradle {cradleRootDir = "/Users/maksbotan/temp/servant", cradleOptsProg = CradleAction: Cabal}
2020-06-13 00:00:47.057557 [ThreadId 5] - <--2--{"jsonrpc":"2.0","params":{"value":{"kind":"end"},"token":464},"method":"$/progress"}
2020-06-13 00:00:47.05763 [ThreadId 5] - <--2--{"jsonrpc":"2.0","params":{"token":465},"method":"window/workDoneProgress/create","id":465}
2020-06-13 00:00:47.057698 [ThreadId 5] - <--2--{"jsonrpc":"2.0","params":{"value":{"kind":"begin","cancellable":false,"title":"Initializing Cabal project","percentage":0},"token":
465},"method":"$/progress"}
2020-06-13 00:00:47.058043 [ThreadId 4] - ---> {"jsonrpc":"2.0","id":465,"result":null}
2020-06-13 00:00:47.058105 [ThreadId 4] - haskell-lsp:Got reply message:"{\"jsonrpc\":\"2.0\",\"id\":465,\"result\":null}"
2020-06-13 00:00:47.058202 [ThreadId 10] - ****** reactor: got message number:1920
2020-06-13 00:00:47.058247 [ThreadId 10] - reactor:got RspFromClient:ResponseMessage {_jsonrpc = "2.0", _id = IdRspInt 465, _result = Just Null, _error = Nothing}
2020-06-13 00:00:47.058282 [ThreadId 10] - ****** reactor: top of loop
2020-06-13 00:00:48.826147 [ThreadId 13886] - Resolving dependencies...
2020-06-13 00:00:49.502951 [ThreadId 13886] - Build profile: -w ghc-8.8.3 -O0
2020-06-13 00:00:49.503037 [ThreadId 13886] - In order, the following will be built (use -v for more details):
2020-06-13 00:00:49.503088 [ThreadId 13886] -  - servant-0.17 (lib) (configuration changed)
2020-06-13 00:00:49.503132 [ThreadId 13886] -  - servant-server-0.17 (lib) (configuration changed)
2020-06-13 00:00:49.503171 [ThreadId 13886] -  - servant-server-0.17 (test:spec) (configuration changed)
2020-06-13 00:00:49.519729 [ThreadId 13886] - Configuring library for servant-0.17..
2020-06-13 00:00:51.352339 [ThreadId 13886] - Preprocessing library for servant-0.17..
2020-06-13 00:00:51.365653 [ThreadId 13886] - Building library for servant-0.17..
2020-06-13 00:00:52.562677 [ThreadId 13886] - Configuring library for servant-server-0.17..
2020-06-13 00:00:54.507245 [ThreadId 13886] - Preprocessing library for servant-server-0.17..
2020-06-13 00:00:54.517199 [ThreadId 13886] - Building library for servant-server-0.17..
2020-06-13 00:00:55.965902 [ThreadId 13886] - Configuring test suite 'spec' for servant-server-0.17..
2020-06-13 00:00:57.200188 [ThreadId 13884] - Warning: The package has an extraneous version range for a dependency on an
2020-06-13 00:00:57.200304 [ThreadId 13884] - internal library: servant-server -any && ==0.17, servant-server -any &&
2020-06-13 00:00:57.200355 [ThreadId 13884] - ==0.17. This version range includes the current package but isn't needed as
2020-06-13 00:00:57.200393 [ThreadId 13884] - the current package's library will always be used.
2020-06-13 00:00:58.096714 [ThreadId 13886] - Preprocessing test suite 'spec' for servant-server-0.17..
2020-06-13 00:00:58.23108 [ThreadId 13881] - Source error on cradle initialisation: can't find file: test/Spec.hs

hie-bios debug:
$ hie-bios debug servant-server/test/Servant/ServerSpec.hs
Root directory:      /Users/maksbotan/temp/servant
Component directory: /Users/maksbotan/temp/servant/servant-server
GHC options:         -fbuilding-cabal-package -O0 -outputdir /Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -odir /Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -hidir /Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -stubdir /Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -i -i/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -itest -i/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/autogen -i/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/global-autogen -I/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/autogen -I/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/global-autogen -I/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/spec-tmp -optP-include -optP/Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/build/spec/autogen/cabal_macros.h -hide-all-packages -Wmissing-home-modules -no-user-package-db -package-db /Users/maksbotan/.cabal/store/ghc-8.8.3/package.db -package-db /Users/maksbotan/temp/servant/dist-newstyle/packagedb/ghc-8.8.3 -package-db /Users/maksbotan/temp/servant/dist-newstyle/build/x86_64-osx/ghc-8.8.3/servant-server-0.17/t/spec/noopt/package.conf.inplace -package-id QuickCheck-2.13.2-IFlQsVhepoXHrDkLASCySh -package-id aeson-<IP_ADDRESS>-CYBfyzHWco0JrS94obsAvi -package-id base-<IP_ADDRESS> -package-id base-compat-0.11.1-4oueEGUxmwHC6tuHqQ6hE2 -package-id base64-bytestring-<IP_ADDRESS>-G2dYBQRtOn8Kxdm0ndZRY -package-id bytestring-<IP_ADDRESS> -package-id directory-<IP_ADDRESS> -package-id hspec-2.7.1-aWprQ9Cwpe3oyEKitw2xL -package-id hspec-wai-0.10.1-LnpMCbFbKnxFyLrTCjtYOD -package-id http-types-0.12.3-B9EkuT6UGia2QJglhdFRHH -package-id mtl-2.2.2 -package-id resourcet-1.2.4-6K2EEC3PWvYL6IkanWK5wW -package-id safe-0.3.19-LxDJURZu1921pHCEJqjvRE -package-id servant-0.17-inplace -package-id servant-server-0.17-inplace -package-id should-not-typecheck-2.1.0-Aj1oA7w1Cu9GKPJbdEbgtJ -package-id string-conversions-<IP_ADDRESS>-KKjGH1i6WmbIm0l1zjJpaj -package-id temporary-1.3-6rtkIO88VZm9X1XintkbH8 -package-id text-<IP_ADDRESS> -package-id transformers-<IP_ADDRESS> -package-id transformers-compat-0.6.5-4FrvPCFBsgnJ9PLf29P7hZ -package-id wai-<IP_ADDRESS>-FkX8kCk55MR1uSuQhWVyx2 -package-id wai-extra-<IP_ADDRESS>-F5qpFPbsyBgB3suZR2dFQg -XHaskell2010 test/Spec.hs Servant.ArbitraryMonadServerSpec Servant.Server.ErrorSpec Servant.Server.Internal.ContextSpec Servant.Server.Internal.RoutingApplicationSpec Servant.Server.RouterSpec Servant.Server.StaticFilesSpec Servant.Server.StreamingSpec Servant.Server.UsingContextSpec Servant.Server.UsingContextSpec.TestCombinators Servant.HoistSpec Servant.ServerSpec -Wall -hide-all-packages
System libraries:    /nix/store/qdxkswf4vg9b2ylmg819ff0n8gl8yqip-ghc-shell-for-packages-ghc-8.8.3-env/lib/ghc-8.8.3
Config Location:     /Users/maksbotan/temp/servant/hie.yaml
Cradle:              Cradle {cradleRootDir = "/Users/maksbotan/temp/servant", cradleOptsProg = CradleAction: Cabal}
Dependencies:        cabal.project cabal.project.local

This is annoying, since once I open some of test's files in my editor, hie just starts to consume CPU by restarting in a loop and failing with the same error.

This option: -itest is wrong. It should be an absolute path.

I did some more investigation.
Firstly, my first hunch that the option -itest is wrong was incorrect. It is correct, the path is made absolute later in the pipeline which cant be seen here (namely in initSession).
Secondly, $ hie-bios check servant-server/test/Servant/ServerSpec.hs fails due to the same reason  cabal repl servant-server/test/Spec.hs  fails (a bug in cabal <IP_ADDRESS> https://github.com/haskell/cabal/issues/6622 that has been fixed in upcoming versions).
Neither of these issues caused the compilation error you observed afaict. Also, I could only reproduce half of the problem. An error was shown when you opened  test/Spec.hs but the rest of the test-suite was working fine. The problem of test/Spec.hs seems to be related to hspec-discover (related issue https://github.com/mpickering/hie-bios/issues/187).
I was able to load the project when globally installing hspec-discover with no errors.

You can clearly see this in the command line:
... -XHaskell2010 test/Spec.hs Servant.ArbitraryMonadServerSpec Servant.Server.ErrorSpec ...

I.e., cabal for some reason adds test/Spec.hs as a file, not module name.
BTW, hspec-discover is in $PATH for me (due to nix), so that issue is unrelated.
Have you seen my PR #202? I can confirm that with this patch (rebased on top of 0.5.0) hie works fine with servant.

And my hie-bios and hie are built with Cabal-<IP_ADDRESS>, as far as I can tell. And that version is in $PATH as well.

Ah, https://github.com/haskell/cabal/issues/6622 has not yet made it to any release, maybe it's the reason I'm getting this error.
So, in other words, we have to wait for Cabal release?

You can clearly see this in the command line:

Yes, but the flags are post-processed later on. Unfortunately, they do represent the exact flags that are used by the ghc session anymore.

are built with Cabal-<IP_ADDRESS>

I think the fix is going to be shipped with the next minor version cabal-<IP_ADDRESS> release.

So, in other words, we have to wait for Cabal release?

No, it should work. Actually I think I got it wrong again. It should be unrelated to the cabal bug.

I.e., cabal for some reason adds test/Spec.hs as a file, not module name.

That is normal for the main module.

By the way, this succeeds:
$ cabal new-repl servant-server/test/Servant/ServerSpec.hs

That is normal for the main module.

Indeed, but it's broken for packages in subdirs :) That's why I added preprocessing for this specific case in #202.

By the way, this succeeds:

Yeah, the error is thrown by the GHC API.
The fix looks good in general, I am playing around with different ways.

Okay!
I'm not saying I think my fix is great, I just want to attract your attention to the root of the problem :)

I'm not saying I think my fix is great, I just want to attract your attention to the root of the problem :)

I think I have understood it now :) Adding a test and pushing my version of the fix for a review soon.

Nice to hear!

This should be fixed now! However, someone has to patch it in HIE as well


create docker environment for vim-bootstrap.com

[ ] dockerfile (run bottle)
[ ] docker-compose

:+1:

I might take a look into this.

@sfrique update issue, new version migrate to Go + Glide (package manage)

so i should use this branch instead of master correct?
I had the docker kind of working, but I also had installed youcomplete me, is there any reason why this plugin is not been used?
I am not sure if I should commit the Dockerfile using youcomplete me as it isn't a part of vim-bootstrap.


My linkvertise bypass is not working on fastward

please fix it

We are aware of problems with the linkvertise bypass. improvements were made earlier today and will be rolled out over the next week. (thanks rebane2001!!)


About upload and webhook

I am trying to set a vpn on a dedicated server to piracies issues and I'm unsure of the ports of upload and webhook.
(sorry to bother you again...)

And I got this while uploading through a vpn
Failed to upload vultr.com.1000MB.bin to Drive.


The workqueue of service should be service other than ingress

Signed-off-by<EMAIL_ADDRESS>

lgtm :+1: thanks!

@brancz the ci/circleci:build is still pending, but it seems not related with my code change :)

will merge when it goes green :)

Did the build fail or why did you force push? (it does take a while as it builds prometheus for all architectures, it just needs time if you thought it was stuck)

@brancz I thought it was stuck and force push to re-trigger it which I don't have the permission 😂

It does finish, just give it some time, if it truly takes too long then the timeout will kick in :)

@brancz It actually passed, but took so long time 😂

Thanks for the patience :)


Resolved CORS issues

CORS is nice to verify that public endpoints are being hit by the targets we want them to be hit by, at least when it comes to web browsing.
Added in a regex-based whitelist of origins to approve,  and stored actual whitelists in the .env file.

delete these commits!!! (AHHH)


Add support for the minimum heat setting where supported

This adds the minimum heat setting as a preset and resolves #27.
Given it alters the operation of the unit and the target temperature, it seemed to make more conceptual sense as a preset than a switch. It's odd that there's not an HVACMode for frost protect, but cést la vie.
Thanks very much!

:tada: This issue has been resolved in version 1.1.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Unfortunately, this has removed the "Swing" control for me.  I now get "Preset" of "None" and "Minimum Heat", whereas before I could control the swing position.

😅 Glad to see the update, I thought I'd broken something!
From memory, there's no way to filter the capabilities at present, it'd have to be new feature work.


Remove duplicate fields in BSON that break MongoDb 4.0

The col:count() and the authenticate functions use the function attachpairs_start  to construct the message to the MongoDb server.   This works in our old instance of MongoDb 2.4 but fails in MongoDb 3.x and MongoDb 4.0.   Analysis showed that the modified pairs function was duplicating entries e.g.
{  "count": "collectionname",  "count": "collectionname", "query":"something" }
This apparently now is prohibited in MongoDb.  The col:count() method (for example) silently fails due to MongoDb error message about duplicate BSON field names.   (Authenticate also fails with a similar message).
The corrections attached still perform the original intent (as best as I can figure out) of moving the named field to the start of the list, but skip it when encountered again.  We were able to successfully call col:count() once this patch was applied.

looks good! Sorry it took so long to merge, just had a baby and have been away.


Marriage abroad - Spain

https://trello.com/c/Idn8qff4/1196-getting-married-abroad-spain
Updated 4 outcomes because amount of time for CNI changed from 3 to 6 months.

Merged in https://github.com/alphagov/smart-answers/pull/3474.


[5.4] Plurals in __() JSON translation

Is there any chance to use plurals in JSON translations with __() helper?
https://github.com/laravel/framework/pull/16424 https://github.com/laravel/framework/pull/16470 https://github.com/laravel/framework/commit/94372447b9de48f5c174db2cf7c81dffb3c0c692

I don't think it's planned, anyways you can post on the https://github.com/laravel/internals repo. That's where we keep track of feature requests.

@themsaid, I'm a bit confused with this and feel like you're best at making it clear.
We use your __() helper with single .json file everywhere.
// In views:
__('Product :product was saved successfully.', [
  'product' => 'My product'
])

// And in `resources/lang/de.json`, obviously:
{ "Product :product was saved successfully.": "German translation" }

It just works. However, if we wish plural translation there's no way to avoid translation string in trans_choise()? We can't do something like this, right?
trans_choice('[1,4] See all photos|[5,*] See all :photos photos', $photos, [
  'photos' => $photos
])

Does this mean for plural translations we have to use resources/lang/de/messages.php with trans_choice() and for others resources/lang/de.json with __() helper?

I'm a bit confused too for this point. It'd be easy to make transChoice method use json, something like this (I didn't dig deeper):
public function transChoice($key, $number, array $replace = [], $locale = null) {     return $this->choice($this->getFromJson ($key), $number, $replace, $locale); }
So we can use choice in JSON files:
"comment|comments": "commentaire|commentaires",
Because what I have to do now is not very clean:
trans_choice(__('comment|comments'), $number)

@bestmomo, trans_choice(__('comment|comments'), $number) works for me as well. And this way actually eliminates a need of storing plural (and any other) translations inside resources/lang/en/*.php file. All in JSON now.
I think, would be just awesome to introduce something like _n() helper for plural translations stored in JSON:
function _n($id, $number, $replace = [], $locale = null) {}

Added a very simple wrapper in our project based on @bestmomo's findings (thanks btw!):
if (! function_exists('__choice')) {
    /**
     * @param string $key
     * @param int $count
     *
     * @return string
     */
    function __choice(string $key, int $count) : string
    {
        return trans_choice(__($key), $count);
    }
}

so you can do
{{ __choice('results for', $total) }}

In your JSON translations, you can still use all default parameters and constructions:
{
    "results for": "{0} Geen resultaten voor|{1} Eén resultaat voor|[2,*] :count resultaten voor"
}

Sometimes you might need variables in these $key strings so it's okay to pass an array as well.
if (! function_exists('__choice')) {
    /**
     * @param string|array $key
     * @param int $count
     *
     * @return string
     */
    function __choice($key, int $count) : string
    {
        if (is_array($key)) {
            return trans_choice(__($key[0], $key[1]), $count);
        }

        return trans_choice(__($key), $count);
    }
}

I think it needs to be the following syntax:
trans_choice(__($key, $replace, $locale), $number);
Otherwise $locale wont work. Tested with Laravel 5.4.

I think it needs to be the following syntax:
trans_choice(__($key, $replace, $locale), $number);
Otherwise $locale wont work. Tested with Laravel 5.4.


Make pyarrow optional

I'm trying to install pfio in an environment where I can't install arrow.
I have no plan to use HDFS either.
I think it's very helpful if pfio can be installed without HDFS support.

Could you tell me any actual use case behind your request where you can't install? PFIO is originally a file system wrapper that does not support POSIX. And it supports HDFS as a primary file system to wrap. We assumed that PFIO users always needed pyarrow. I also want which feature of PFIO you're using, without need for HDFS. Also, pyarrow itself has an x86 wheel release - it can be installed without Hadoop or even Java installation. So does boto3. In case when you don't need them, they don't do any harm unless you use them.
Also, #187 would be a huge change that changes the usage of PFIO. I don't have good idea to implement pyarrow and boto3 as extras_require .

Thank you for a comment. This is the result of pip install pfio in my environment (on arm64).

Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
Collecting pfio
  Downloading pfio-1.4.3-py3-none-any.whl (46 kB)
Collecting boto3
  Downloading boto3-1.17.89-py2.py3-none-any.whl (131 kB)
Collecting pyarrow==3.0.0
  Downloading pyarrow-3.0.0.tar.gz (682 kB)
  Installing build dependencies: started
  Installing build dependencies: still running...
  Installing build dependencies: still running...
  Installing build dependencies: still running...
  Installing build dependencies: still running...
  Installing build dependencies: still running...
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
    Preparing wheel metadata: started
    Preparing wheel metadata: finished with status 'done'
Requirement already satisfied: numpy>=1.16.6 in ./.pyenv/versions/3.6.13/lib/python3.6/site-packages (from pyarrow==3.0.0->pfio) (1.19.5)
Collecting botocore<1.21.0,>=1.20.89
  Downloading botocore-1.20.89-py2.py3-none-any.whl (7.6 MB)
Collecting s3transfer<0.5.0,>=0.4.0
  Downloading s3transfer-0.4.2-py2.py3-none-any.whl (79 kB)
Collecting jmespath<1.0.0,>=0.7.1
  Downloading jmespath-0.10.0-py2.py3-none-any.whl (24 kB)
Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in ./.pyenv/versions/3.6.13/lib/python3.6/site-packages (from botocore<1.21.0,>=1.20.89->boto3->pfio) (2.8.1)
Collecting urllib3<1.27,>=1.25.4
  Downloading urllib3-1.26.5-py2.py3-none-any.whl (138 kB)
Requirement already satisfied: six>=1.5 in ./.pyenv/versions/3.6.13/lib/python3.6/site-packages (from python-dateutil<3.0.0,>=2.1->botocore<1.21.0,>=1.20.89->boto3->pfio) (1.16.0)
Building wheels for collected packages: pyarrow
  Building wheel for pyarrow (PEP 517): started
  Building wheel for pyarrow (PEP 517): finished with status 'error'
  ERROR: Command errored out with exit status 1:
   command: /home/niboshi/.pyenv/versions/3.6.13/bin/python3.6 /home/niboshi/.pyenv/versions/3.6.13/lib/python3.6/site-packages/pip/_vendor/pep517/in_process/_in_process.py build_wheel /tmp/tmpn6mv248f
       cwd: /tmp/pip-install-t4ofepcn/pyarrow_983f6fc761534b2db63cafc8296003f5
  Complete output (233 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-aarch64-3.6
  creating build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/orc.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/compat.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/filesystem.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/fs.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/jvm.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/__init__.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/compute.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/types.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/feather.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/flight.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/hdfs.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/pandas_compat.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/util.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/benchmark.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/cffi.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/dataset.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/ipc.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/_generated_version.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/cuda.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/json.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/plasma.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/serialization.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/csv.py -> build/lib.linux-aarch64-3.6/pyarrow
  copying pyarrow/parquet.py -> build/lib.linux-aarch64-3.6/pyarrow
  creating build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_cuda.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_hdfs.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/strategies.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_builder.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_plasma_tf_op.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/conftest.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_orc.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_sparse_tensor.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_serialization_deprecated.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_serialization.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_types.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_dataset.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/__init__.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_cffi.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_cython.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_strategies.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/pandas_examples.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_adhoc_memory_leak.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_deprecations.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_tensor.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_feather.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_jvm.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/util.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_flight.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_plasma.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_compute.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_io.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_scalars.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_cuda_numba_interop.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_table.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_misc.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_pandas.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_fs.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_gandiva.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_schema.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_convert_builtin.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_array.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_extension_type.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_filesystem.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_ipc.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_json.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/arrow_7980.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/pandas_threaded_import.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_memory.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/deserialize_buffer.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  copying pyarrow/tests/test_csv.py -> build/lib.linux-aarch64-3.6/pyarrow/tests
  running egg_info
  writing pyarrow.egg-info/PKG-INFO
  writing dependency_links to pyarrow.egg-info/dependency_links.txt
  writing entry points to pyarrow.egg-info/entry_points.txt

The error is because pyarrow 3.0.0 does not provide a wheel for aarch64 (pyarrow 4.0.0 does, though, but not any).
pfio's README says it's a file system abstraction. We use it in our library for that purpose. The library intends to support both HDFS and POSIX file system. Users (like me in this case) should be able to run it both with and without HDFS.

Got it. Thank you for detail. How about updating pyarrow to 4.0? (Now it has 4.0.1). That should work for you if you're using Linux, because pyarrow itself does no harm (once it's installed :P ), even without HDFS. That fix would also be easy for me, too.
For macos, maybe we can implement a special workaround like skipping pyarrow with warning.
I understand your concern that a dependency that's not needed is installed by opt-out, but the complexity introduced by naive resolution, like install options such as pip install pfio[hdfs,s3] would break a lot of applications' dependency. We should design and discuss more carefully.

I've released 1.5, which depends on pyarrow 4.0.1. I hope it works for you, but otherwise would welcome further discussion.

Thank you for the suggestion, but closing. Feel free to reopen, to resume the discussion.


update bazel scala rules (for java 18)

On M1 Macs, only java 18 can successfully complete compilation and testing of unit tests.  However, the current bazel scala rules do not work in java 18.
This updates scala rules to work in java 18.
Also tested in java 8 (compiles scala and runs the tool, but won't compile unit tests on M1 macs).

It does not work Otherwise. Took me a while to figure out using a new file
solves the dependency issue.
On Tue, 16 Aug 2022, 6:03 am Brad Kotsopoulos, @.***>
wrote:

@.**** commented on this pull request.
In bzl/scala_config.bzl
https://github.com/Snapchat/djinni/pull/99#discussion_r946082198:

@@ -0,0 +1,4 @@
@.***_bazel_rules_scala//:scala_config.bzl", "scala_config")

+def djinni_scala_config():

scala_config(scala_version = "2.11.12")

Why do we have a new bazel file instead of putting this in setup_deps?
—
Reply to this email directly, view it on GitHub
https://github.com/Snapchat/djinni/pull/99#pullrequestreview-1073141356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHWY2RC5Z4SHMKEXMO2IDLVZKPCNANCNFSM56KVPIRA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Library generates uncompiled code if @NeedsPermission method has a parameter with keywords in canonical classname

Overview
In our project, we have is.effective as packageName. There are a model class Image located in is.effective.models package and some fragment with method foo, where Image is a parameter:
class ChatFragment: Fragment() {
...
   @NeedsPermission(WRITE_EXTERNAL_STORAGE)
   fun longClicked(image: Image) {
      // method code is omitted
   }
...
}

Expected

Library generates longClickedWithPermissionCheck extension method in ChatFragmentDispatcher.kt and generated code is compilable.

Actual

Library generates longClickedWithPermissionCheck extension method in ChatFragmentDispatcher.kt, but generated code is not compilable, due to inproperly generated import statement (non-escaped is keyword):

Environment

Which library version are you using?
3.1.0

On which devices do you observe the issue?
that's a compilation error

Note any other information that might be useful
As I understand, PermissionDispatcher relies on https://github.com/square/kotlinpoet, so we need to address the issue their. I went ahead, forked kotlinpoet, made a local fix and will submit PR to kotlinpoet shortly.

Huh, I'm certain that I did that before (edit: yes I did. @shiraji, @hotchemi, let's review the version of kotlinpoet we're pulling in with the latest version of PermissionsDispatcher. @AlexKorovyansky, can you try adding an explicit dependency on the latest kotlinpoet to the annotationProcessor configuration?

We need to wait https://github.com/square/kotlinpoet/pull/327 release. Right? @AlexKorovyansky

I see, this actually is somehow different to our previous work - weird. Admittedly, I only skimmed over the related kotlinpoet issue briefly. Okay, let's wait on a new release then!

Original PR (https://github.com/square/kotlinpoet/pull/248) fixes only issue in package declaration, while this issue relates to imports. The fix for kotlinpoet has been already merged to master and should be available in 0.8.0-SNAPSHOT. Is there any option to use kotlinpoet 0.8.0-SNAPSHOT with the latest version of PermissionDispatcher?

See https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/389#issuecomment-333682572

Thx guys! I'd say we need https://github.com/permissions-dispatcher/PermissionsDispatcher/pull/438 ? 👀

Oh I found with 0.8.0-SNAPSHOT generated kt class causes a compile error as below 🤔
(PermissionUtils.hasSelfPermissions(`this`, *PERMISSION_SHOWCAMERA))

Updated KotlinPoet to 1.0.0-RC.


Add liveness/readiness probes to kafka streams applications and integrate with K8s

Why are we not adding readinessprobe?


Can't send bitcoin from Ord wallet   code: -8, message: "Invalid parameter, output already locked", data: None

Hi I am trying to move bitcoin from my wallet to sparrow wallet,  (not ordinals) and I am getting the following error:
code: -8, message: "Invalid parameter, output already locked", data: None

I am getting the same issue. I did a test transaction with few sats and it worked. All further transactions fail with the same error

running into this as well

same problem

Tried to send funds to a fresh wallet with 0 balance and it works. Hope this helps someone

It was later discovered that this is a software issue.
Solution: When encountering an error while using the "ord wallet send" command, close Bitcoin Core and restart it.


Direct avatar rendering

This adds new template helpers for avatar rendering which output image elements with direct links to avatars which makes them cacheable by the browsers.
This should be a major performance improvment for pages with many avatars.

Besides removal of dead code which I still plan to do, this should now be fully functional.

Gravatar avatars are not yet tested. Not sure yet if the changes from https://github.com/go-gitea/gitea/pull/10540 need further adjustments, the avatar code is highly convoluted unfortunately.

Gravatar is working as well. Initially the images were a bit blurry on my high-dpi screen and I fixed that by increasing the requested size by two times.

Org avatars are not working yet, they still emit those redirect URLs, not sure yet where to fix them.

make fmt missing?

This is ready for review now. Turns out org avatars were already working and caching, I was just confused by their different URL scheme (they use /avatars/num instead of storage paths).
I don't think there is anything left to clean up from the old avatar code, bits and pieces are still in use in some places.

@silverwind the avatar on a users provile page is now too smal

@6543 hmm I thought I fixed that earlier, will recheck.

@6543 fixed that. turns out I only fixed the own avatar, not the other ones.

Also fixed a extra border on top of profile username. The remaining fixes to those cards are in https://github.com/go-gitea/gitea/pull/13751.

circles!!! why do we circle now!??!!

Oh, it seems Fomantic is doing that if an avatar appears in a card, let me fix that...

Should be better now with only our regular border-radius applied on avatars:

before:
now:

Intended?

Intended?

No. Seems like it's not properly falling back to generated avatars for unregistered users, checking.

@6543 should be fixed, including name tooltip for which I added another helper. Not happy having three helpers for avatars but functions overloading in go is quite hard.

Doh, it seems models.AvatarLink is the thing that emits those 302s again, need to fix.

Ready again. I've removed the now-obsolete avatar email hashing mechanism. The /avatars/user/size route needs to stay as that one is actively used by third parties like Drone.

Federated avatars are still WIP as per discussion in Discord, regular and Gravatar ones are testable.

wip again, there's a import cycle which I'm not yet sure how to resolve.

@silverwind this will need a refactor ...
models]$ rg 'code.gitea.io/gitea/modules/base'
token.go
12:     "code.gitea.io/gitea/modules/base"
action.go
15:     "code.gitea.io/gitea/modules/base"
branches.go
13:     "code.gitea.io/gitea/modules/base"
issue.go
15:     "code.gitea.io/gitea/modules/base"
review.go
11:     "code.gitea.io/gitea/modules/base"
pull_list.go
10:     "code.gitea.io/gitea/modules/base"
user.go
24:     "code.gitea.io/gitea/modules/base"
unit_tests.go
16:     "code.gitea.io/gitea/modules/base"
user_avatar.go
16:     "code.gitea.io/gitea/modules/base"

I think you have to remove models dependency on base

Actually I got around by moving everything into models, thankfully
This is ready again, federated avatars are uncached and working just like before. Gravatar and self-hosted avatars are of course caching.

Planning to do one more small refactor because there is some duplication still left between base and models.

@silverwind should we wait or start a follow up pull?

i'll do it in the next few hours, it should be rather trivial, please wait.

Dedupe done, ready now.


stdenv: don't clobber useArray and type in {prepend,append}ToVar

Some other packages, for example ruby gems via buildRubyGem, use a variable called "type" internally, which is overwritten here and causes failures like:
failure: $gempkg path unspecified

Fix for changes in 11c3127e38dafdf95ca71a85b1591a29b67e0c09.
Description of changes
Added local to some variables that should be local to a bash function.
Tested by building with nix-build -A tests.stdenv -A hello -A bundix -A vagrant, which all succeed.
Intended to fix ruby gem builds, like bundix and vagrant (https://github.com/NixOS/nixpkgs/issues/211153).
cc @Artturin
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Tested by building with nix-build -A tests.stdenv -A hello -A bundix -A vagrant, which all built ok.

Thanks

For those that want to track PR progress post build nixpk.gs is a handy tool.


Generalize npm dependency support for generated js code

Sister issue of https://github.com/grpc/grpc-web/issues/584  (copying content)
All generated code currently generates js import paths with similar structure with that of the imported .proto files.
The one exception for protobuf well-known types - google-protobuf based ont he import prefix:
https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/compiler/js/js_generator.cc#L128
string GetRootPath(const std::string& from_filename,
                   const std::string& to_filename) {
  if (to_filename.find("google/protobuf") == 0) {
    // Well-known types (.proto files in the google/protobuf directory) are
    // assumed to come from the 'google-protobuf' npm package.  We may want to
    // generalize this exception later by letting others put generated code in
    // their own npm packages.
    return "google-protobuf/";
  }

Equivalent code in grpc-web:
https://github.com/grpc/grpc-web/blob/master/javascript/net/grpc/web/grpc_generator.cc#L461
This will generate something like
import * as google_api_annotations_pb from './google/api/annotations_pb';
import * as google_protobuf_timestamp_pb from 'google-protobuf/google/protobuf/timestamp_pb';

An import option would allow users to explicitly override the relative path and specify a npm package at .proto import could be the right approach to generalize this.

This is something we should think about supporting.


add utf8 encoding when opening files for windows

The metadata_save() method in repocard.py does not work on Windows when creating Spaces. The reason is that UTF-8 encoding is not assumed on Windows and the presence of emojis in Spaces README leads to a UnicodeEncodeError. The simple fix is to set the encoding="utf8" when reading and writing the file, as is done in this PR.
More info about this issue: https://discuss.python.org/t/pep-597-use-utf-8-for-default-text-file-encoding/1819

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


fatal error: 'eosiolib/eosio.hpp' file not found

I've been trying to get the development environment working for the past three days but keep getting this error when generating wast and abi for my code using eosiocpp
fatal error: 'eosiolib/eosio.hpp' file not found #include <eosiolib/eosio.hpp>
I've tried all the solutions I could find, including modifying eosiocpp, sudo make install, etc.
I have also tried using master branch, v1.0.5, v1.0.9 and v1.1.0
I'm completely stuck, what to do now?

Try v1.1.0, build it and install it (./eosio_build.sh && cd build && sudo make install). You will see that your eosiocpp will be installed inside /usr/local/eosio/bin and your eosiolib will be installed inside /usr/local/eosio/include. This way, if you are compiling using /usr/local/eosio/bin/eosiocpp, your eosiocpp should be able to detect files inside /usr/local/eosio/include as it is already added to your include path by eosiocpp. Make sure you revert all the change you have made to eosiocpp previously to prevent unintended side effect. Let me know if you still encounter the problem.

Same thing happens, don't just frantically close the issue.
I can get it kind of working by modifying eosiocpp but then I get errors about missing boost library files.
EOS 1.1.0 is scuffed.

Hmm, that's strange I don't think eosiocpp boost include directory got changed recently. Normally, the above solution works fine for v1.1.0. What modification did you do?

must build and make install  the eos

I don't understand why the file path before the modification is placed separately. Is the directory clear? For newcomers who are not familiar with ubuntu, this will be annoying.
Can you give a solution? ?
`Revision: f4ffc26a1e393f33a1542f45f1b1ea388f416ad5
Author: Bucky Kittinger<EMAIL_ADDRESS>Date: 7/11/2018 1:28:13 AM
Message:
change default to /usr/local/eosio

Modified: eosio_build.sh`

https://www.bcskill.com/index.php/archives/304.html

I managed to get it working by making a fresh install of ubuntu.
After close inspection, it seems that build script dependency installation didn't take into account which version of boost I had, and skipped it, leading into missing files.
eosiocpp still doesn't work as expected, but with minor path tinkering I got it working.