Labels should allow excluding chart by default

This is probably a feature request.
Labels in current form allow a nice separation of charts, but they do not change the default helmfile sync behavior, when all charts are executed. For example, if we follow approach described in https://github.com/roboll/helmfile/tree/master/examples#managing-oneshot-jobs-with-helmfile, the usual helmfile sync would execute everything, while it might be natural only regular charts without that one time job.
Would it be possible to allow exclusion of some chart based on labels, or all pipelines should just included explicit --selectors?

@amnk Good point. Honestly I'm not very sure but would --selector job!=dbmigrator would exclude the oneshot job only? It isn't straightforward even if it worked, but I don't have a better alternative.
Also, it doesn't address your concern that helmfile sync should run only long-running services only. Would it make sense to add defaultSelector to helmfile.yaml, which is applied to helmfile sync when no --selector is specified?

@mumoshu defaultSelectors (plural) makes sense for me. For example, if someone has tier: backend, tier: frontend and tier: ci, he might want to use tier: backend and tier: frontend by default.

@amnk Thanks. Understood :) The last thing I'm considering now is that how we could harmonize the feature with the helmfile.d feature.
In nutshell, helmfile -f dir/ sync is almost equivalent to helmfile -f dir/00-foo.yaml sync PLUS helmfile -f dir/01-foo.yaml sync. In which yaml file would you like to define the defaultSelectors?
Possible options:

Introduce an another yaml file to define global options like defaultSelectors 🤔
Merge defaultSelectors from multiple yaml files 🤔

Any thoughts? @osterman @sstarcher

@mumoshu I vote for merge of defaultSelectors from multiple files.
To give it a little bit more details: usually all those conf.d folders, where you can have several configuration files, are treated in the same way:  configuration is read, then it is merged, then it is evaluated and checked for errors, then it is executed. If you have this flow in mind - automerge fits perfectly.
But if you want to evaluate them one by one - then the order of config files becomes very important, and it kinda removes some of the determinism.

@amnk Thanks! I'm trying to understand - what is your expected outcome for the below example?
helmfile.d/00-frontend.yaml:
defaultSelectors:
- tier: app

releases:
- name: frontend-app
  # ...
  labels:
    tier: app
- name: frontend-ci
  # ...

helmfile.d/01-backend.yaml:
releases:
- name: backend-app
  # ...
  labels:
    tier: app
- name: backend-ci
  # ...

@mumoshu both frontend-app and backend-app will be deployed.

I'm against merging helmfiles that are in the helmfile.d directory.  It adds significant complication and disallows us from having separate configurations for those files.  With the separation allowed by helmfile.d I can now specify a --timeout setting for one of the yaml files and it will not effect the other files.
If we were to implement a default selector you could put it into each of your helmfile.yaml files or they could each have different default selectors.  Although overall I find the idea of a default selector skeptical and wonder why you don't just put them into a entirely separate helmfile in a different location as it sounds like you have operational things you want to separate out.

@sstarcher agreed, I could have put in the different file. But on the side my usecase is simple: replace multiple Helm calls with one helmfile call. And then selectors updating things only when they changed in code. Having several helmfiles complicates things, and sounded quit logical to me.
At the same time I have a question is well: how is helmfile.d different from a simple bash script?
for helmfile in *
do
    helmfile --file $helmfile sync
done

this can be easily enhanced with conditionals as well to put timeout for some files. Sorry if the question sounds dumb, and I'm most likely missing something here.

That's essentially what helmfile is doing for helmfile.d.
I would think it would be logically easier to have 2 separate helm files in your case.

Update things helmfile sync
Run jobs helmfile -f jobs sync

If we implemented merging it would remove alot of useful capabilities that we currently have in helmfile.  I'm up for other solutions, but I can't think of one atm to make this easier.  Unless we added firstclass support for jobs.

@osterman FYI, you'd be interested in this issue about default selectors.

@amnk @sstarcher Hey! So how about just adding defaults.selectors to helmfile.yaml, that is overridable via --selectors` flag?
For the use-case of collocating releases for oneshot jobs and other long running apps in each helmfile.yaml, you may have the below snippet in all the yaml files:
defautls:
  selectors:
  - tier=frontend
  - tier=backend

And helmfile apply is literally translated to helmfile -l tier=frontend -l tier=backend, whereas helmfile --selectors tier=ci apply or helmfile --selectors tier=oneshot apply targets respective releases only.
In case "all" the helmfiles under helmfile.d/ has no releases matching the specified selector, helmfile fails. In other words it succeeds as long as at least one of helmfiles has matching releases.
Makes sense? Any comments are welcomed. Thanks.

So for implementing something like this I think it likely makes sense to support all helmfile specific command line variables and if they are set on the command line they would be overriden.
Maybe
options:
  selectors:
  - tier=frontend
  concurrency: 1
  auto-approve: true

@mumoshu I like that approach
@sstarcher I like your idea as well! :)

@sstarcher Sounds great. Would you like it if it is configurable per enviroment, too?
environments:
  prod:
    options:
    # override the top-level(default) options as you like
    # ...

options:
  selectors:
  - tier=frontend
  concurrency: 1
  auto-approve: true

@amnk Missed to mention you :) I appreciate your comment, too!

As it the selectors are overridable via the --selector flag, I'm now against naming it options:. I'd prefer defaults::
defaults:
  selectors:
  - tier=frontend
  concurrency: 1
  autoApprove: true

But then the problem is that how we differentiate between helmDefaults vs defaults. It is confusing, especially given that we can also override what are provided in helmDefaults.
helmDefaults:
  tillerNamespace: tiller-namespace  #dedicated default key for tiller-namespace
  kubeContext: kube-context          #dedicated default key for kube-context
  # additional and global args passed to helm
  args:
    - "--set k=v"
  # defaults for verify, wait, force, timeout and recreatePods under releases[]
  verify: true
  wait: true
  timeout: 600
  recreatePods: true
  force: true

defaults:
  selectors:
  - tier=frontend
  concurrency: 1
  autoApprove: true

My idea is to rename helmDefaults just an alias to defaults:, and gradually deprecate helmDefaults. On the other hand I would say that defaults is for anything global to helmfile run, which is customizable via command-line flags.

I would like to know if selector can be regex?

Nope.

Is there any current way to do this?  We are wanting to implement our long running DB migrations are HelmChart/jobs, but we also want to prevent someone from being able to run them by accident.
Moving the jobs into their own helmfile would be fine, but would still need a way to force passing something on the CLI before it runs.  Even being able to set them to condition: false, and overriding that on the command line would work.
helmfile -f jobs.yaml -e qa1 --selector name=app1-job  --set condition.enable true --set image.tag yadda yadda
even something like that would work, as long as helmfile -f jobs.yaml apply failed to run.


Fixed RPS load test

Prerequisites

[X] I am using the latest version of Locust
[X] I am suggesting a new feature, not asking a question

Description
I'm testing API endpoints in which the test case is that in total 10 minutes I have to ramp up users linearly until the rps is >= 70 if rps greater than 70 and the current time is < 10 minutes then maintain in steady state for remaining time. My question is, is there a way I can take the current RPS and user count in every iteration? My code is
from locust import TaskSet,HttpUser, LoadTestShape

class Scan(TaskSet):
    @task
    def perf_scan(self):
        self.client.get(“/api”)

class url(HttpUser):
    tasks = [Scan]

class CustomLoadShapeScenario2(LoadTestShape):
    def tick(self):
        total_time = 600
        run_time = self.get_run_time()
        if RPS < 70 and run_time<total_time: # here for RPS I need a solution to extract from locust
            users = run_time//10
            spawn_rate = 1
        elif run_time<total_time:
            users = user_count # here for RPS I need a solution to extract from locust. It is the user_count until the if condition was satisfied
            spawn_rate = 1
        return (users, spawn_rate)

Any code example or solution will be of great help.

A one possibility I can see would be to access the stats instance within environment and then lookup inside it's entry dictionary and then on entry's num_reqs_per_sec property.
see doc

A one possibility I can see would be to access the stats instance within environment and then lookup inside it's entry dictionary and then on entry's num_reqs_per_sec property.
see doc

Thank you @Sawiq. Does locust supports different endpoints with different custom load shape? For example if I have 10 endpoints and each endpoints have different custom load shape. I want all the endpoints to run simultaneously.

A one possibility I can see would be to access the stats instance within environment and then lookup inside it's entry dictionary and then on entry's num_reqs_per_sec property.
see doc

Thank you @Sawiq. Does locust supports different endpoints with different custom load shape? For example if I have 10 endpoints and each endpoints have different custom load shape. I want all the endpoints to run simultaneously.

No and yes. You cant have different load shapes for different endpoints. Load shapes only control how many User instances are started (and optionally the distribution between User types).
So you'll need to define 10 User classes and use the user_classes parameter for the shape to control when/how many users are started at each stage. https://docs.locust.io/en/stable/custom-load-shape.html#restricting-which-user-types-to-spawn-in-each-tick


samples: Add explicit zephyr_include_directories to get <board.h>

There are a small handful of samples that still utilize <board.h>
include, to minimize the use of <board.h> to these specific cases and
allow us to remove adding the board dir to the top level include search
path, we explicitly in each sample add the specific board dir it needs.
For the microbit cases these could be replaced by DTS support in the
future when the pwm_nrf5_sw supports DTS.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

FYI, this is in prep for being able to remove ${BOARD_DIR} from zephyr_include_directories in toplevel CMakeLists.txt

Codecov Report

Merging #11369 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11369   +/-   ##
=======================================
  Coverage   48.37%   48.37%
=======================================
  Files         265      265
  Lines       42188    42188
  Branches    10137    10137
=======================================
  Hits        20408    20408
  Misses      17703    17703
  Partials     4077     4077

Continue to review full report at Codecov.

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


Improve documentation

I think we can migrate so stuff from the readme to readthedocs and add some jupyter notebooks for illustrative examples. Also type annotations would help. Low prio though.

[ ] create readthedocs
[ ] add jupyter notebooks wirh some examples
[ ] add type annotations

An alternative to readthedocs would be an github io page, e.g.: https://basf.github.io/mopti/


Reference Leak in function args

How to reproduce error: 'tests/test_secrets.py'

you can use triple back-quote (```) to make text quote


net/http: problems or undocumented features dealing with handler timeout

What steps will reproduce the problem?

First problem: a http handler which delays longer than server.WriteTimeout just silently
sends nothing, not even a HTTP error header. This behaviour might be deliberate (on the
basis of "use a timeout handler instead"), but it needs documenting.

Second problem: responseWriter.Write() returns nil for err (a write success) if
WriteTimeout has been exceeded. (Contrast: using a http.TimeoutHandler, it returns
"http: Handler timeout" correctly.)

Third problem: using a TimeoutHandler, with the actual handler having the behaviour or
Write, long delay, Write, and a timeout set to fire during the delay, the first write
sends the headers and the written value, then the timeout fires and appends the timeout
text and fails to set headers (because they were already sent). The result is a jumble
of output. This is not exactly an error, but it's a thing that needs communicating in
the docs: that the TimeoutHandler uses the same ResponseWriter, and if you have written
anything it will be unable to rescind it.

Which compiler are you using (5g, 6g, 8g, gccgo)?

8g

Which operating system are you using?

Ubuntu Linux 12.04 32 bit.

Which version are you using?  (run 'go version')

go version go1.1 linux/386

I think most of this has since been fixed or documented, but assigning to myself to double-check.

In regards to:

We've got TestServerTimeouts https://github.com/golang/go/blob/07a22bbc11de6c8cdac599f59ef00f019d22ff67/src/net/http/serve_test.go#L505-L595
We've got TestOnlyWriteTimeout https://github.com/golang/go/blob/07a22bbc11de6c8cdac599f59ef00f019d22ff67/src/net/http/serve_test.go#L771-L824
am not sure fully yet, I'll defer to Mr. HTTP @bradfitz

Thanks @odeke-em for investigating and finding the tests.
And #3 has been documented much more in the four years since this bug was filed. It now says:
        // Changing the header map after a call to WriteHeader (or
        // Write) has no effect unless the modified headers are
        // trailers.

So I think we're good here. These many-bug-reports-in-one bugs tend to slip through the cracks since they can't be closed piecemeal. In the future, feel free to spam us with a dozen small bugs, cross-referenced as needed.


Scaffold 20150411

Coverage decreased (-4.8%) to 72.03% when pulling 803499e990d695930c98e1f57553b11992e84868 on scaffold-20150411 into a0e014010ad37e828b79f86d0003ba7621fd69d2 on master.

Coverage decreased (-4.8%) to 72.03% when pulling 803499e990d695930c98e1f57553b11992e84868 on scaffold-20150411 into a0e014010ad37e828b79f86d0003ba7621fd69d2 on master.

Coverage decreased (-4.8%) to 72.03% when pulling 7edcc178e6a364e56364390ac2415ad2e0d54308 on scaffold-20150411 into a0e014010ad37e828b79f86d0003ba7621fd69d2 on master.


proximity placement group support

VMSS Flex configuration blade shows "Proximity placement group configuration cannot be changed in virtual machine scale sets with flexible orchestration mode"

@fitzgeraldsteele
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

This is not correct. PPG is supported, just not changable after deployment

This merge should be denied

Thanks @fitzgeraldsteele I'll close the PR now.


Page "flashes" when first loading

If you load the page, you'll notice that a bunch of content "flashes" before going away.
I'm guessing this is because the content starts out displayed, and then the JS hides it when first executing. It would be better if it starts out hidden to prevent the flashing.

I think I fixed this, though I'm not sure the solution is the most elegant - the exercise text window (which has the intro text, and is the main source of flashing because the text is cleared if localstorage is nonempty ) is now set to a hidden CSS style initiallly, and the className is changed once the text is finalised.


[Feature][Test] Test

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
测试测试
测试 bot
Use case
No response
Related issues
测试
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

不懂欣赏


Can i use 'BitcoinKit' Framework Implement 'Send btc' function in testnet?

I saw no code in SendViewController.swift.
Thanks!

Hi, thanks for asking this question!
We implemented send feature in SendViewController.swift in our PR.
So after merging this PR, you can see codes there!

@usatie thanks a lot ,i debug your code, i saw it is a BCH wallet?is not BTC wallet?

@usatie i found the Class Network, i change value testnetBTC ...Thanks a lot again!

@victorylau It's my pleasure to be your help!
Thanks for giving us a comment.
If you have other questions or another request, feel free to create an issue again!


clarify selection in FMT_MOF for "configuration of extensions" and plugins

Does this really just mean whitelist?

Added a mgmt setting to address email notifications since FDP_NOT_EXT.1.1 was deleted.  Issue  needs further discussion.

Added MOF 13. Recommend close.


Updated the README with new Carthage instructions.

Can you update the reference section of the dev docs after this is published?
https://github.com/optimizely/developers.optimizely.com/commit/8ee73e9703b45ef5919d4ccecfeaa1b187f571c8


Snapshot Prometheus disk after tearing Prometheus down (1.15)

Gracefully tear down Prometheus retaining PD, then snapshot and delete PD.
Cherry-picks: #1178, #1199
Fix: #1020
/cc mm4tt mborsz

/lgtm
/approve


iOS build failed issue with AppAuth Pod

Not sure what is going on, using cordova<EMAIL_ADDRESS>and getting a compile error with AppAuth:
The following build commands failed:
CompileC /Users/user/Library/Developer/Xcode/DerivedData/Oil_Analysis-alepbbrfapgngxbrndlbvvkdcvqp/Build/Intermediates.noindex/ArchiveIntermediates/Oil\ Analysis/IntermediateBuildFilesPath/Pods.build/Debug-iphoneos/AppAuth.build/Objects-normal/arm64/OIDExternalUserAgentIOSCustomBrowser.o /Users/user/oa/platforms/ios/Pods/AppAuth/Source/iOS/OIDExternalUserAgentIOSCustomBrowser.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
Not sure if there is an actual problem with that POD or with all of them because that is the first one.
Tried removing platforms completely, reading the ios platform then adding the plugin
Have updated the pods, the pod depencency manager, installed all the gems, done everything.
Any idea?  Is it an issue with 5.1.1 and 5.1.0  ?  It was working fine for me earlier today witgh 5.0.1 but I need 5.1.0+ to use WKWebView instead of the old one.
My build does work without this plugin, but I need this for firebase notifications.
Any ideas?

Please make sure you have set up Cocoapods and updated your local pods repo using pod repo update. See the documentation for details. Try building the example project to validate your build environment against a known working codebase.
Closing as this issue seems specific to your build env - works fine my build envs using cordova-ios@5,1,1

Yep, I've done that numerous times.  I'm going to start fresh again and see if I can get it working.

Ah, well no the example project does not compile either, gets an error at the same spot.
** ARCHIVE FAILED **
The following build commands failed:
CompileC /Users/user/Library/Developer/Xcode/DerivedData/FirebaseTest-hkgzcyasfxzxizhgjdtaovnujyrt/Build/Intermediates.noindex/ArchiveIntermediates/FirebaseTest/IntermediateBuildFilesPath/Pods.build/Debug-iphoneos/AppAuth.build/Objects-normal/armv7/OIDExternalUserAgentIOSCustomBrowser.o /Users/user/fbx/cordova-plugin-firebasex-test/platforms/ios/Pods/AppAuth/Source/iOS/OIDExternalUserAgentIOSCustomBrowser.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
xcodebuild: Command failed with exit code 65
Users-iMac:cordova-plugin-firebasex-test user$

Here's my console.log for the build

Tried another fresh install using<EMAIL_ADDRESS>and same result.  What could be causing this!

I'm wondering if the latest cocoapods update no longer works with XCode 10.1 .. That's the only thing I can think of.   I will try again in my cloud environment using the latest XCode.  This Mac I have locally won't let me go to the latest version :(

I'm getting a parse error on the AppAuth file, expected "," ... see screenshot.  What would be causing this!!?

Seems like others have had this problem https://stackoverflow.com/questions/59023380/firebase-ios-swift-authentication-api-unavailablemaccatalyst-problem

After some trial and error I found a solution. Use pod 'GoogleSignIn', '~> 4.1.1' instead of version 5.0.1 -- for anyone using XCode 10.1  .. the new GoogleSignin only works with Xcode 11+

Is there any way to build it without the Google Signin?

Not without forking the plugin and removing it yourself

I've put in a request to my boss to buy me a new Mac.  This is just sillly trying to work in a Legacy environment.  Thanks for your help on this.

Yeah, Apple is always going to deprecate old hardware pretty fast so they can sell you new hardware!
Look out for their new Macs due later this year which use Apple ARM architecture instead of Intel x86.
I'm pretty sure they will deprecate the Intel-based Macs soon after their ARM Macs hit the market.
So lookout for the next major version of Xcode which runs on ARM-based Macs only 😠
Tell your boss I told him to buy you a new Mac 😁

Oh no lol. Well we got the 2018 model iMac 21 inch.  Come on they can't deprecate all the intel machines can they?  Not for a long time I think.

Hi, I have issue with AppAuth too.
If I downgrade AppAuth to 1.2.0 or try to use GoogleSignIn 4.1.1 then i catch a lot of errors (14) linked with this items. For example with ASAuthorizationControllerDelegate: Cannot find protocol declaration for 'ASAuthorizationControllerDelegate'; And also a lot of errors in AppDelegate(FirebasePlugin) in "Apple Sign In" section (l.504). The same with corodova-plugin-firebasex-test ENV.
May ot be Xcode version? My Xcode version 10.1

Hello,
I'm having this issue with Xcode 10.1, which I assume is incompatible with the plugin recent versions.
So I guess the last version compatible with Xcode 10 is 7.0.2, right? Thank you!

Hello,
Based on my test 7.0.2 was the latest version not requiring GoogleSignIn and downgrading to this version fixed it for me.


Initial commit with boilerplate files.

This commit adds our code of conduct, OWNERS, contribution guidelines and README.md

/lgtm

/approve


feat: add draft logic for eager evaluation feature in REPL

Progress: #2073.
Description

What is the purpose of this pull request?

This pull request:

add draft logic for eager evaluation feature in REPL

Related Issues

Does this pull request have any related issues?

This pull request:

Progress: #2073.

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@kgryte Please take a look at the logic when you have time. If everything looks good, I can proceed with:

Fixing conflicts with the Tab preview
Adding tests and additional files for eager evaluation"


Added Elasticserach data stream ilm policy support

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?
Added support for data_stream_ilm_policy and data_stream_ilm_policy_overwrite fields in Elasticsearch plugin
Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

@petergvizd please run the make generate command


gen2-gaze-estimation 'depthai.OpenVINO' has no attribute 'VERSION_2020_1'

Huge newbie here, so apologies if this is a simple problem and greatly appreciate any advice.
Trying to get gaze estimation running and coming across the problem in the title. I assume version 2020_1 is outdated and wasn't downloaded on my system when I set everything up today. I tried to change the version in the first below image:

unsurprisingly it didnt work, and gave me the below error:

My question is how do I update "Pipeline - 'NeuralNetwork' node with id: 2"?

Thank you @themarpe  - this answers my question so I am closing the issue


Rollback breakage caused by Dagger CLI 0.3 release

Problem
We recently released a new Dagger CLI, version 0.3, which is a hard breaking change from 0.2. There is a migration path in preparation (using a new CLI called dagger-cue which is drop-in compatible with 0.2), that was meant to be rolled out soon.
But we accidentally broke users of the current github action now, without warning, by auto-updating this action to dagger 0.3. This should be immediately reversed regardless of future migration plans.
Solution
Change the latest version of this action @v3 to pin to dagger 0.2, instead of latest.
This should resolve the immediate issue for users of the Github Action, and allow us to finish planning a proper migration path.
Thank you @fredleger for alerting us and we apologize for the poor experience!

Hey @fredleger! Can you confirm that this fixes your issue?

Sure thing! Thanks for the quick reply 🏎


Fix tests

In the fork, the tests were not really compatible with the source in TS.

[ ] Return tests to functional state

Hello, i’m one of the old maintainer developer of this lib.
I’m glad you like it and want to keep it alive.
I’ll take this issue and try to fix the tests.

Great! It's awesome to have you here, thank you.
I have the time to put into helping maintain this library if people want to use it.

@christopher-caldwell we have the tests running again, but we must review each test file one by one.
What about creating an check list for each test that must be reviewed? maybe we can create a PT for each one.

Sure, yeah. We can create a milestone to get all of them done, and link as many issues as we need. Great idea!


Update prepare_data.sh and prepare_data_no_dicom.sh to make it compatible for BIDS

Also add documentation

Data preparation is now supported by this repository: https://github.com/neuropoly/bids_neuropoly


Handle stats not conforming to the triplet format

Addresses issue #92
In Ubuntu's (14.04) version of memecached packaged with the OS the
version STAT line contains a fourth value due to a space. This breaks
the expected triplet pattern and incorrectly caused an exception.

Looks good, I'll get this out to pypi over the weekend. Thanks!

:fireworks:  Thanks!


Storage checkstyle and spotbugs. Spotbugs is done. Organize the impor…

Issue #3021

Can one of the admins verify this patch?


Update target distributions

Both of distributions are already removed from GitHub Actions.

buster: EOL (2022-09-10), though LTS is still alive (2024-06-30)
bionic: End of Standard Support (June 2023), EOL April 2028

See
https://wiki.debian.org/DebianReleases
https://wiki.ubuntu.com/Releases

As #510 was merged, rebased it.

I've fixed it.


Change log level in device generator if /sys/block does not exist

Fixes #421. Some the directory is unavailable on some PaaS.

I think this p/r is not a good solution... better to change the log level to warning?

Thank you!


Replace docker-image-not-found in CircleCI publish workflow

What would you like?
The npm module docker-image-not-found, sourced from the repo cypress-io/docker-image-not-found, is out of date and should be replaced.
Why is this needed?
The npm module docker-image-not-found is on the critical path for releasing Cypress Docker images to the repositories Docker Hub and Amazon ECR (Elastic Container Registry) Public Gallery.
The module is used in the CircleCI workflow command halt-if-docker-image-exists.
docker-image-not-found (current latest), which was released in March 2020, is not compatible with default multi-architecture manifests using OCI formats. If an OCI type image exists, then docker-image-not-found reports the same 1 return code as for an existing docker manifest image. The error log however shows that there has been a problem evaluating the manifest, leading to loss of confidence in the module's reliability.
The following issues would need to be resolved in order to continue to use it in the medium term:

https://github.com/cypress-io/docker-image-not-found/issues/6
https://github.com/cypress-io/docker-image-not-found/issues/5
https://github.com/cypress-io/docker-image-not-found/issues/4
https://github.com/cypress-io/docker-image-not-found/issues/3
https://github.com/cypress-io/docker-image-not-found/issues/2

Considering that its only function is to check for the existence of an image, the effort to update it to current environments is out of proportion to its benefit. The original repo https://github.com/mishguruorg/docker-image-exists, from which it was forked, was last updated 7 years ago and would not be helpful for any update.
Other
Related

https://github.com/cypress-io/cypress-docker-images/issues/1141
https://github.com/cypress-io/cypress-docker-images/issues/1095

Recap

As experienced in issue #1093, docker-image-not-found was unable to evaluate a media_type in the form of  oci and it output an error message:

message: 'unsupported schema version 2 in cypress/factory:4.0.1 manifest',

The manifest causing an issue contained the following:
"schemaVersion": 2,
"mediaType": "application/vnd.oci.image.index.v1+json",

Due to uncertain root causes and effects, the change was reverted in PR #1094 changing the media_type back to docker:
"schemaVersion": 2,
"mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",

A solution for checking if an image has already been published to Docker Hub is needed which covers both the older docker type and the newer oci type. This issue is preventing further version updates taking place (see #1095 & #1145).
Solution suggestion
Using the Docker HUB API (beta)'s Check repository tag with the following format it is possible to replace the outdated npm module docker-image-not-found. The API does not require a Docker client and is therefore independent of any Docker engine version installed:
https://hub.docker.com/v2/namespaces/{namespace}/repositories/{repository}/tags/{tag}

For instance
curl -s https://hub.docker.com/v2/namespaces/cypress/repositories/factory/tags/4.0.2 | grep -iq 'httperror 404'
echo $?
curl -s https://hub.docker.com/v2/namespaces/cypress/repositories/factory/tags/missing | grep -iq 'httperror 404'
echo $?

returns 1 (failure) = image exists (not 'not found')
returns 0 (success) = image check returned HTTP 404 'not found'

respectively, exactly as docker-image-not-found does.
Additionally the API is able to cope with images that have an imageType oci. For example, we can check the method using ubuntu/jammy which has converted to vnd.oci.image:
$ curl -s https://hub.docker.com/v2/namespaces/library/repositories/ubuntu/tags/jammy | python -mjson.tool | grep media_
type
    "media_type": "application/vnd.oci.image.index.v1+json",

and executing this command against the oci image correctly returns the expected result:
curl -s https://hub.docker.com/v2/namespaces/library/repositories/ubuntu/tags/jammy | grep -iq 'httperror 404'
echo $?

returns 1 (failure) = image exists. This is despite it having an oci manifest.

Note that the experimental Docker command docker manifest inspect in the currently used Docker engine 20.10 fails to recognize images with an oci manifest, and so it is not yet a candidate to replace docker-image-not-found. It does however work in later versions such as Docker engine 24.0 and its status can be monitored to see if docker manifest inspect should be used at a later time.


Fix undead containers

Fixes #12825
When a container has errors on removal, it gets flagged as dead.
If you docker rm -f a dead container the container is dereffed from
the daemon and doesn't show up on docker ps anymore... except that the
container JSON file may still be lingering around and becomes undead
when you restart the daemon.

Hmm..I think a good portion of the reason the original PR was written was because the err that gets you into that defer block is a lack of ability to os.RemoveAll the container rootfs (e.g. devicemapper busy errors, etc.).  That doesn't mean it isn't reasonable to try to remove it, but I think there will be situations where this doesn't actually change the behavior if there is still a "device busy" problem on the rootfs.

@estesp This shouldn't be the container rootfs, it should be the config root /var/lib/docker/containers

@cpuguy83 yup, you're right.. was sidetracked by the incorrect comment in the string of remove steps below the defer block :)

LGTM

LGTM


Rename identifiers which shadows a builtin attribute

Rename identifiers flagged with # noqa: A003 for built-in attribute shadowing.
Known potential problem: if the identifier collides with the data type name (e.g. list), it even breaks mypy.

was resolved as part of https://github.com/apify/apify-sdk-python/pull/172


Cross-platform “Open debug logfile”

The option to open the debug logfile from the debug window was implemented only for
windows. By using QDesktopServices::openUrl it now works on any platform.
This includes (requires) #418 and #419.

#409 got me thinking about getting 'Open debug logfile' to work cross platform so I thought I would do the Windows testing on #409 if @jwrb wants to do the Mac OS X testing on this :)

Sounds good! Will do!

@scroogemcdev before merging but after testing I will rebase this to remove the commits from #418 and #419 from this pull.

Tested on my arch box, works properly (25 minutes)

This is good on Mac!

This needs to be rebased over master.

Rebased still includes the unmerged #419 until it's merged.

Requires rebase

Rebased


Provide size hint information about the contents of Queries

Probably as a method on the Fetch trait. Sum the lower and upper bounds of the constituent types to create a new bound.
Would be useful to properly pre-allocate data storage  for get_multiple_mut, introduced in #3333.

This doesn't seem to be needed; #3333 found a workaround so I expect other cases will be able to as well.


refactor: Extract AppEngine Cron source check into middleware

This de-duplicates the code we have to check the AppEngine Cron request header and pushes it into the HTTP router and out of the app logic.
As a convenient side effect, this also ensures that any cron job failure produces and HTTP 500 response (indicating failure to AppEngine) and an ERROR-severity log line (which we're starting to use for alerts).

Ref: #61


EFAX-84 implement OutputService proxy

Description
This PR includes the following proposed change(s):
EFAX-84
Implement OutputService proxy (an old PDF flattening service).

Refactored existing PdfService to be an interface
Kept original LiveCycleGateway implemenation, but disabled via properties config
implemented new OutputService impl using javax.xml.ws.Service

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Does the change impact or break the Docker build?

[x] Yes
[ ] No

If Yes: Has Docker been updated accordingly?

[x] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

I added a new PdfService implementation (PdfOutputService) with junit tests, yet the total-coverage went down.  Hmm. I'm unable to override this.

I added a new PdfService implementation (PdfOutputService) with junit tests, yet the total-coverage went down. Hmm. I'm unable to override this.

In a pinch we can adjust the threshold temporarily.


failoverNodes should be separated by whitespace

From martin.grotzke on October 18, 2009 00:44:35
failoverNodes right now are separated by colon (":"). To be consistent with
the memcachedNodes attribute, they should be separated by whitespace.
Documentation also needs to reflect this.
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=16

From martin.grotzke on October 17, 2009 15:47:34
Done.
Status: Fixed


Add between and surroundedBy combinators

Codecov Report

Merging #79 (73c4790) into main (493581c) will decrease coverage by 0.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   96.63%   96.48%   -0.15%
==========================================
  Files           4        4
  Lines         624      626       +2
  Branches       53       61       +8
==========================================
+ Hits          603      604       +1
- Misses         21       22       +1

Impacted Files
Coverage Δ

core/shared/src/main/scala/cats/parse/Parser.scala
97.15% <100.00%> (-0.17%)
:arrow_down:

Continue to review full report at Codecov.

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

You might also want to try using this in the JSON benchmark.

@johnynek good call on trying to add this to the json example. I realised we needed a few more things.


[HOLD for payment 2024-07-26] [$250] Android - Task - Deleted task is shown briefly and then disappears from conversation page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.5
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4704499
Issue reported by: Applause - Internal Team
Action Performed:

Launch app
Open a report
Tap plus icon -- assign task
Enter a title and tap next
Tap confirm task
Open the task created
Tap header - delete option

Expected Result:
Deleted task must not be shown briefly in conversation page
Actual Result:
Deleted task is shown briefly and then disappears from conversation page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/b283acce-2621-4d33-a894-82d212c686b4
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d0d653c8ad7776ae
Upwork Job ID:<PHONE_NUMBER>806319286
Last Price Increase: 2024-07-09
Automatic offers:

alitoshmatov | Reviewer | 103061198
dominictb | Contributor | 103061200

Issue OwnerCurrent Issue Owner: @alitoshmatov

@VictoriaExpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Issue recreated. Agree this is a bug that belongs in VSP.

Please re-state the problem that we are trying to solve in this issue.
Deleted task is shown briefly and then disappears from conversation page
What is the root cause of that problem?
The root cause of this issue is that the pendingAction for a deleted task is always set to CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE, regardless of whether the task should be deleted. This results in the task being displayed until the backend confirms the deletion. Specifically, in App/src/libs/actions/Task.ts, the pendingAction is set to UPDATE, which leads to the following filtering conditions in App/src/pages/home/report/ReportActionsList.tsx not excluding the deleted task immediately:
https://github.com/Expensify/App/blob/4a3ecb348a49f490ad3c3f466bed716dbc4803ef/src/pages/home/report/ReportActionsList.tsx#L200-L208
What changes do you think we should make in order to solve the problem?
const sortedVisibleReportActions = useMemo(
    () =>
        sortedReportActions.filter(
            (reportAction) =>
                (isOffline ||
                    ReportActionsUtils.isDeletedParentAction(reportAction) ||
                    (reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE &&
                     reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE) ||
                    reportAction.errors) &&
                ReportActionsUtils.shouldReportActionBeVisible(reportAction, reportAction.reportActionID),
        ),
    [sortedReportActions, isOffline],
);

reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE && reportAction.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.UPDATE: Ensures that tasks with pending DELETE or UPDATE actions are excluded from the visible actions.
video:-
https://github.com/Expensify/App/assets/43398804/8aa16603-7a88-4220-8441-896868cacd81

@cretadn22 Thank you for your proposal, your RCA is correct. However you missed a case where task report is still shown where it has some report actions in it. Your solution makes it disappear in optimistic data and appear again when backend data is received.

@dominictb Thank you for your proposal, your RCA is correct and your are providing a correct solution

@kaushiktd Thank you for your proposal, your RCA seems to focus on wrong area and provided a wrong solution

@alitoshmatov  can you please explain where it go wrong

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/24137
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/24137/files#r1692881438
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No need
Determine if we should create a regression test for this bug. I think there is no need for test

Link the GH issue for creating/updating the regression test once above steps have been agreed upon: - N/A

Contributor: @dominictb paid $250 via Upwork
Contributor+: @alitoshmatov paid $250 via Upwork
Upwork job here!


Donate animals page can be more beutify with some background images and colors

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
i want to make more beautiful donate animal pages by using images etc
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

assign me this so that i can contribute to gssoc 2023

I am interested to work on this issue under GSSoC 2023 as a contributor


Ticketmaster webpage third-party content causing NSURLErrorDomain -1002

Bug description:
Some sites have content that does not follow proper web standards and are causing our component to fail hard. There needs to be a way to let these errors fail silently so the entire page doesn't crash.
I have Allow Arbitrary Loads & NSAllowsArbitraryLoadsInWebContent enabled in our Info.plist file
<key>NSAppTransportSecurity</key>
	<dict>
		<key>NSAllowsArbitraryLoads</key>
		<true/>
		<key>NSAllowsArbitraryLoadsInWebContent</key>
		<true/>
	</dict>

I also have set mixedContentMode="always"
To Reproduce:
Loading any Ticketmaster.com ticketing page will initially load and as secondary content (JS, images, etc...) loads an error will be thrown.
For ex: https://www1.ticketmaster.com/billy-joel-billys-70th-birthday-new-york-new-york-05-09-2019/event/3B00554F06438807
The URL will throw a NSURLErrorDomain with error code: -1002 (unsupported URL)
Expected behavior:
Webview does not throw error on webpage content or secondary url requests, should be able to fail gracefully on nested content instead of a hard failure.

This also happens with any Medium.com article. Did you ever find a solution?

No need to patch the native code. Here's how to solve it:
<WebView originWhitelist={['http://*', 'https://*']} ... />

@asrytis I have not found a solution to this but I will certainly try this. I would rather not have to enter a huge list of URL schemes and might just add a return, not sure what that will do since I am not an iOS developer either.

@asrytis are you sure that will work? I have the following set in our code and still get the error:
<WebView originWhitelist={['*']} />

This is the reason you get the error because you allow WebView to load any scheme. It’s probably attempting to load some weird resource like the ‘medium://‘ link in my example above.

@asrytis Interesting ... I thought it was because http content was being loaded in a https url

Can I close this ?

@Titozzz For now yes, we've tested on several ticketmaster URLs (and around 50 others) and the issue seems to be curbed. We may need to reopen since it wasn't really clear what was causing the error and it could return. Thanks @asrytis for the fix!

if anyone is strugling with this on iOS, what solved it for me was:
<dict>
    <key>LSApplicationQueriesSchemes</key>
    <array>
        <string>YOUR SCHEME</string>
    </array>
</dict>

in Info.plist

@Overtorment does the scheme need to be all caps, or how does the letter case affect it?

@whitefang57 no difference i think, but i have it lower case

I have tried all of the suggestions above and still no luck - I am getting the same error.
Further I tried to encode the URL which is being rendered in the webview (in case of special characters, though I don't have any query params) and to control the rendering of the url through onShouldStartLoadWithRequest, but it does not get detected before the error is triggered.
Should I raise another issue to discuss this further?


DirectShape.ByGeometry creates DS, but outputs an error

As the title says, the object is created, but does not appear in the node output, instead:
File "<string>", line 88, in NewDS SystemError: Der Typeninitialisierer für "Revit.Elements.DirectShape" hat eine Ausnahme verursacht.
This is likely caused by the ToDSType() call, since this function only supports a very small portion of all Revit categories/types. (See https://github.com/DynamoDS/Dynamo/issues/2460 for more info...)

Removing the ToDSType() call will result in there not being an error message. Instead, the node returns null. It would be really nice if it could return the newly created element for downstream use...

I've never had this problem before. Do you mind sharing an example where this happens?

This happened when converting a geometrically complex shared family nested into another. I'll see if I can create a minimal reproducible test case next week.

The node has gone through a few revisions since. Give it another go and post here if you see this happening again. Closing for now.


All language utilities imported by 'revscoring.languages' (with proposal)

This causes a lot of trouble.

A lot of stuff is loaded even if only one LanguageUtility is needed.
All aspell and myspell packages must be installed for the system to work at all.

So, these language utilities should be imported on demand.  This is difficult to accomplish due to the structure of the 'languages' module.
Right now, languages/init.py imports all of the languages.  For example:
from .english import english
from .french import french
# etc.

I propose that we replace this pattern with a dynamic import module.  I haven't been able to get that one to work in my python 3.4 environment yet though -- so I expect we'll need to do a bit of research.

Fixed by https://github.com/wiki-ai/revscoring/pull/141

Let's merge this awesome work (per IRC)!
Do you think it would be a benefit if we could also load languages like, english = Language.get('en')?  This looks like a really good application for mostly declarative configuration.  revscoring/languages/spanish.py, for example, is isomorphic with a simple and much more readable YAML file, like:
spanish:
  bad_regexes:
    - ano
    - ...
  dictionaries: enchant
  informal_regexes: ....
  utilities:
    - stem_word
    - is_badword
    - ...

@adamwight, I don't think the yaml approach would work for anything but regexes as the functions may need custom definition.  We could have a mixture of simple yaml definitions and complex python definitions, but I'm not sure that would be any more easy it understand/maintain.  However, I do agree that there should be simple subclass of Language that does the non-declarative bits for the common cases.  E.g. RegexEnchantLanguage
One thing I am troubled with re. Language.get() pattern is the ability to write your own language in your own module and use that as a drop-in replacement.  If you are going to use Language.get() in that circumstance, you'll need to make sure your module gets loaded first so that the language can be registered.  With the current structure of revscoring extract_features and revscoring train_test utilities, that wouldn't work (uses classpath of language utilities).  It would also break https://github.com/wiki-ai/ores' configuration strategy.  In the end, we'd be implementing dynamic loading ourselves within a python function and mimicking python's import system.  The problems I'm concerned about above are due to this incomplete mimicry.

Great points!  Let's move in the direction you suggest, of pushing more common functionality into generic classes.  I would recommend against an inheritance hierarchy, rather a component-based approach, but that's a small detail.  Once we have the shared code in reusable units, that will help with the main problem, of maintaining a lot of repeated code.  We can always reevaluate the potential for further abstraction after the cruft is cleaned up.


Make sure we get the new form_fields for the transition

fixes #628
The status of the application has not been updated when the transition method is called. So we need to find out where we are transitioning to and the use that to get the new form_fields.

When I invite a concept to proposal and then proposal is about to load I get this:
Request Method: | GET
-- | --
http://apply.otf.test/apply/submissions/322/
2.0.8
TypeError
'NoneType' object is not iterable
/Users/frjo/.virtualenvs/otf/lib/python3.6/site-packages/django/db/models/lookups.py in get_prep_lookup, line 204
/Users/frjo/.virtualenvs/otf/bin/python3.6
3.6.5
['/Users/frjo/Sites/otf',  '/Users/frjo/.virtualenvs/otf/bin',  '/Users/frjo/.virtualenvs/otf/lib/python36.zip',  '/Users/frjo/.virtualenvs/otf/lib/python3.6',  '/Users/frjo/.virtualenvs/otf/lib/python3.6/lib-dynload',  '/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6',  '/Users/frjo/.virtualenvs/otf/lib/python3.6/site-packages',  '/Users/frjo/Sites/otf']
Fri, 28 Sep 2018 12:13:46 +0100

That is linked to the failing tests, fix incoming.

ab17391 is unrelated to this PR, could you move into a new PR?


Rpmsg syslog: update rpmsg syslog

Summary

syslog/syslog_rpmsg.c: the last log may be lost when it crashes

At line 236, we may set the null terminate to the priv->buffer,
when flushing the priv->buffer, we should use up_putc() instead up_nputs()
to ensure all the data has been output, because up_nputs() will check
the null terminate but up_putc() not.

syslog/syslog_rpmsg.c: out of memory

syslog_rpmsg: fix coding style

Follow the nxstyle

4,    syslog/syslog_rpmsg.c: improve syslog_rpmsg performance
use copy buffer instead of single assignment

Impact
Rpmsg syslog
Testing
sim rpserver and rpproxy

[Experimental Bot, please feedback here]
This PR appears to partially meet the NuttX requirements.  Here's a breakdown:
Strengths:

Summary:  Provides a decent overview of the changes made. Each numbered point clearly identifies a problem addressed.
Impact: Correctly identifies the impacted component ("Rpmsg syslog").
Testing: Mentions the testing environments ("sim rpserver and rpproxy").

Areas for Improvement:

Summary:

Lacks a clear statement on the "why" for some points. For example, point 2 mentions "out of memory" but doesn't explain the cause or how the PR fixes it.
Could benefit from more technical detail in places. For example, in point 1, specifying the size of priv->buffer would be helpful.

Impact:  Needs to address all the listed impact points (user impact, build impact, etc.). Even if the answer is "NO," it should be explicitly stated.
Testing:

Lacks specific details about the build host and target used.
The testing logs sections are empty – these should contain actual logs demonstrating the issue before the change and the successful outcome after the change.

Recommendations:

Elaborate on the "why" for each change in the Summary. Provide concise explanations of the problems and how your code addresses them.
Complete the Impact section. Explicitly address all listed impact points, even if the answer is "NO."
Provide detailed testing information. Include:

Build host details (OS, CPU, compiler).
Target details (arch, board, config).
Actual testing logs demonstrating the issue before the change and the fix after the change.

By addressing these points, you'll make your PR more comprehensive and easier for reviewers to evaluate, increasing its chances of being merged.


Can't open a workspace

code-server version: 1.621
OS Version: ubuntu 18

Description
When I use latest docker image, I can't open a workspace or add folder to workspace. Nothing happend. No refresh, no error, no new added folder in exploler. Mounted folder works.
docker run -it -p 3400:8443 --name test -v "/var/www:/home/coder/project" codercom/code-server --allow-http --no-auth

But when I try older docker image, it works.
docker run -it -p 3400:8443 --name test -v "/var/www:/home/coder/project" codercom/code-server:1.604-vsc1.32.0 --allow-http --no-auth

This is a duplicate of https://github.com/codercom/code-server/issues/490, we'll track the issue there. Thank you!


[Suggestion] README Rake section about YardocTask

I think the README should be updated to clarify the below issues for the Rake section about YardocTask (Usage...2. Rake Task).
Options
Just like Issue #1043, I stupidly tried this:
task.options = ['--protected','--template-path my_templates']
And then figured out that you have to specify "my_templates" separately:
task.options = ['--protected','--template-path','my_templates']
Require
Just like Issue #499, I first tried doing this:
require 'yard/rake/yardoc_task' # NameError: uninitialized constant YARD::CLI
And then realized you have to do this:
require 'yard'
To prevent further Issues being created from new users, I think it'd be a good idea to update the README if possible.
Thank you.

Require
Just like Issue #499, I first tried doing this:
require 'yard/rake/yardoc_task' # NameError: uninitialized constant YARD::CLI
And then realized you have to do this:
require 'yard'
To prevent further Issues being created from new users, I think it'd be a good idea to update the README if possible.

This particular issue has been fixed in #1244 (not merged to master yet).

This has been merged and should be resolved in the next release.


Intermittent shouldSlowDownToSlowPreferredWithPreferredMulticastFlowControlStrategy

I seen the following fail on Windows but it does not repeat.
io.aeron.FlowControlStrategiesTest > shouldSlowDownToSlowPreferredWithPreferredMulticastFlowControlStrategy FAILED
    org.mockito.exceptions.verification.TooLittleActualInvocations:
    fragmentHandler.onFragment(
        <any org.agrona.DirectBuffer>,
        <any integer>,
        992,
        <any io.aeron.logbuffer.Header>
    );
    Wanted 192 times:
    -> at io.aeron.FlowControlStrategiesTest.shouldSlowDownToSlowPreferredWithPreferredMulticastFlowControlStrategy(FlowControlStrategiesTest.java:361)
    But was 190 times:
    -> at io.aeron.logbuffer.TermReader.read(TermReader.java:74)
        at io.aeron.FlowControlStrategiesTest.shouldSlowDownToSlowPreferredWithPreferredMulticastFlowControlStrategy(FlowControlStrategiesTest.java:361)

Just seen this fail again.
io.aeron.FlowControlStrategiesTest > shouldSlowDownToSlowPreferredWithPreferredM
ulticastFlowControlStrategy FAILED
    org.mockito.exceptions.verification.TooLittleActualInvocations:
    fragmentHandler.onFragment(
        <any org.agrona.DirectBuffer>,
        <any integer>,
        992,
        <any io.aeron.logbuffer.Header>
    );
    Wanted 192 times:
    -> at io.aeron.FlowControlStrategiesTest.shouldSlowDownToSlowPreferredWithPr
eferredMulticastFlowControlStrategy(FlowControlStrategiesTest.java:361)
    But was 189 times:
    -> at io.aeron.logbuffer.TermReader.read(TermReader.java:74)
        at io.aeron.FlowControlStrategiesTest.shouldSlowDownToSlowPreferredWithP
referredMulticastFlowControlStrategy(FlowControlStrategiesTest.java:361)
Results: FAILURE (39 tests, 38 successes, 1 failures, 0 skipped)

I've not seen this exception in many builds since this https://github.com/real-logic/Aeron/commit/c9eb6126a3f21062368d58a54da7efe222baab2a commit.

It started to occur much more often again.

Some of the tests did not account for driver A getting behind.


add backward support for python38

Enables installation on Python 3.8 and 3.9.
Tested on Windows and GNU/Linux with Python 3.8 and 3.10

Yeah, luckily seems like no dependency version issues (yet) - probably at some point though the Pandas API changes


multiple selectorts

Used jquery multiple selectors to spare us a couple of lines...

@boguz thanks but a click on a client logo doesn't work now

Sorry, i don't have jekyll so i couldn't test it, but i thought this should work.
=/

Okay. If you want to dive into that again feel free to reopen PR.


k_timer_remaining_get returns incorrect value on long timers

Describe the bug
k_timer_remaining_get returns incorrect value when reading time remaining on long timers. I am not sure on the exact timer length but setting a timer for 48 hours will cause this issue
To Reproduce
Steps to reproduce the behavior:

Start a timer over 48 hours. (Could be shorter. 24 hours seems to work but 48 does not)
Read the timer with k_timer_remaining_get.
Timer value will return incorrect value for time remaining.

Expected behavior
Timer is expected to return the correct time remaining in milliseconds.
Environment:

OS: Windows
Toolchain nRF Connect Toolchain manager version 1.4.0

Additional context
Changing k_timer_remaining_get to use k_ticks_to_ms_floor64 instead of k_ticks_to_ms_floor32 seems to remedy this issue. It looks like k_ticks_to_ms_floor32 does not allow the tick count to be large enough.

k_timer_remaining_get() is a legacy function that returns a value in milliseconds as a 32 bit quantity.  It does its internal math to 32 bit precision simply because it always has, and is thus subject to overflow bugs.  It's true that we could do better than we do by computing a 64 bit intermediate result, but it's always going to be skewed relative to what you can achieve with the underlying timeout representation (which is 64 bit by default now, but can be configured to 32 bits).
Use k_timer_remaining_ticks() to return a k_ticks_t value in the full internal precision that you can convert however you like.  I'm not opposed to trying to augment the internal precision of the legacy function, I'm just not sure that it's very useful (given that this bug has been present forever AFAICT).

k_timer_remaining_get() is a legacy function that returns a value in milliseconds as a 32 bit quantity.  It does its internal math to 32 bit precision simply because it always has, and is thus subject to overflow bugs.  It's true that we could do better than we do by computing a 64 bit intermediate result, but it's always going to be skewed relative to what you can achieve with the underlying timeout representation (which is 64 bit by default now, but can be configured to 32 bits).
Use k_timer_remaining_ticks() to return a k_ticks_t value in the full internal precision that you can convert however you like.  I'm not opposed to trying to augment the internal precision of the legacy function, I'm just not sure that it's very useful (given that this bug has been present forever AFAICT).

  This particular function is really a legacy holdover from the era when we had millisecond timeouts everywhere.  At that point, we only had 32 bit timeout precision internally and so a 64 bit intermediate results wasn't even feasible.  Code written to that API clearly won't be expecting the full precision of the output space, and new code should be written to the ticks variant of the call which gives full internal precision by design.

Thinking harder on this, I think I'm just going to close this.  This particular function is really a legacy holdover from the era when we had millisecond timeouts everywhere.  At that point, we only had 32 bit timeout precision internally and so a 64 bit intermediate results wasn't even feasible.  Code written to that API clearly won't be expecting the full precision of the output space, and new code should be written to the ticks variant of the call which gives full internal precision by design.


Integrate type hints with typeshed

To make the package typed, let's reuse types defined for the tarfile library in typeshed: https://github.com/python/typeshed/blob/eee28ad90f467c6b6328bab44a6eed5c2694f68a/stdlib/tarfile.pyi

That sounds great. What's the best way to do that? Given that typeshed already has that file, perhaps it makes sense for it to also expose stubs/backports/tarfile.pyi and just symlink it to ../../stdlib/tarfile.pyi. What are the tradeoffs between that and simply copying the stubs here?
Oh, this project can't simply adopt the typeshed hints because they vary by Python version, whereas this backport uses the latest interfaces across all Python versions (where latest may become stale). Porting those type hints and keeping them aligned with the implementation is probably going to be more work than the entirety of creating this backport (without type hints).
I think the proper way to address this concern would be for someone to add the type hints to the stdlib version source. Then this backport would inherit those hints (and could apply any compatibility wrappers if needed).
What approach would you recommend?


PromptValidatorContext.AttemptCount will throw an exception when used in a validator for an OAuthPrompt or an ActivityPrompt

Version
4.4.3
Describe the bug
The introduction of PromptValidatorContext.AttemptCount was presumably intended only for use with prompts that derive from Prompt<T>, because Prompt<T> automatically initializes State[AttemptCountKey] to zero. No such initialization occurs in OAuthPrompt or ActivityPrompt, yet these classes still use validators. If you provide a validator for one of those prompts and try to access the public method PromptValidatorContext.AttemptCount an unfriendly exception will be thrown.
To Reproduce
Steps to reproduce the behavior:

Create an OAuthPrompt or an ActivityPrompt
Give the prompt a validator
Try to access PromptValidatorContext.AttemptCount in the validator
See error

Alternatively you can insert the following code into ActivityPromptTests.Validator and run the tests in that class:
Assert.IsTrue(promptContext.AttemptCount > 0);

Expected behavior
There are a few options here:

Throw a friendlier exception that explains that AttemptCount is only meant to be used with prompts that derive from Prompt<T>
Handle the case when State[AttemptCountKey] hasn't been initialized by
a. initializing it, or
a. returning a default value

If we don't want to throw an exception, we can also decide whether or not we want to add the attempt count feature to OAuthPrompt and ActivityPrompt.
Screenshots

[bug]

I believe I saw something similar on the JS side, too, where it was either missing or wouldn't ++ some of the attempts in some of the prompts. Haven't investigated or tested yet, though.


Add stub interfaces

so we can stop depending on @types/node

By adding stubs with a combination of d.ts files and interfaces.ts. I no longer see "node" reference in our generated d.ts files, nor our api.md review file.


(build) Update packages and add package-lock

Add package lock file to fix the usual shenanigans with npm packages.

Fixed by Refactor/use typescript #25


Fails to detect certain load failure messages

When I delete the file being monitored, or if it didn't exist to begin with, ghcid always reports "All good". This is confusing, because it hides the fact something is probably wrong.
I'm using version 0.3.2 and the command ghcid --command='ghci GHCidTest.hs'  on Ubuntu Linux.

I think robustly detecting all the variants is too hard, so I changed it to detect no files loaded at the start and then quickly exit, without hiding the error messages that ghci almost certainly already gave you. That makes the experience in these cases almost as good as if I'd actually caught the error.


would you like to provide the 'MIT_BIH_data_5class.p'?

firstly, thanks for the excellent work,
secondly, can you provide the data of 'MIT_BIH_data_5class.p'

firstly, thanks for the excellent work, secondly, can you provide the data of 'MIT_BIH_data_5class.p'

well, I am also in the same type of hurdle.

Hi, did you get the "MIT_BIH_data_5class.p"  file?


’swin‘ train without pth

I want to use swinb to train the model and report the error 'Checkpoint swin_base_patch4_window7_224_22k_d2.pth not found!', where can I get the weight file?

We use the same initial file as Mask Transfiner, so you can download the pretrained checkpoint in this page


Enhance logging of cancelled effects by including function name and arguments

This pull request enhances the logging of cancelled effects by including the name of the saga function and its arguments. When an effect is cancelled, we want to be able to identify which saga function was cancelled and with what arguments. This additional information will be useful in debugging and troubleshooting issues related to cancelled effects.

@clarketm Would be nice to see this merged

@clarketm You think you may merge this one? :)


Update Composer dependencies (2023-08-31-00-13)

Visual regression test passed!
View the visual regression test report


Error ngt_remove_index() only with normalized distance types

Summary
I've come across a problem when calling index.remove(id: VecId), but it only happens with certain distance types:

NormalizedAngle
NormalizedCosine
NormalizedL2

The common theme seems to be that these are normalized?
This is the error that is produced:
Error: Capi : ngt_remove_index() : Error: /.../ngt-sys-2.1.3/NGT/lib/NGT/Index.h:remove:1544: Not found the specified id

Reproducer
I've made a basic project with test cases:
ngtbug.zip
These are the versions in use:
[dependencies]
anyhow = "1.0.75"
ngt = "0.6.1"
uuid = { version = "1.5.0", features = ["v4"] }

and in the lock file, ngt-sys is at 2.1.3.
This is test case, to explain what is happening:
#[cfg(test)]
mod tests {
    use anyhow::Result;
    use ngt::{NgtIndex, NgtDistance, NgtProperties, EPSILON};

    fn run_test(dist: NgtDistance) -> Result<()> {
        // Create a new index
        let prop = NgtProperties::<f32>::dimension(3)?
            .distance_type(dist)?;

        // Temp dir for tests
        let temp_dir_p = std::env::temp_dir();
        let temp_dir = temp_dir_p.to_string_lossy();
        let u = uuid::Uuid::new_v4();
        let u = u.as_simple();
        let index_path = format!("{temp_dir}/{u}");
        std::fs::remove_dir_all(&index_path).ok();

        let mut index = NgtIndex::create(&index_path, prop)?;

        // Insert two vectors and get their id
        let vec1 = vec![1.0, 2.0, 3.0];
        let vec2 = vec![4.0, 5.0, 6.0];
        let id1 = index.insert(vec1)?;
        let id2 = index.insert(vec2)?;
        println!("id1: {}", id1);
        println!("id2: {}", id2);

        // Actually build the index (not yet persisted on disk)
        // This is required in order to be able to search vectors
        index.build(2)?;
        index.persist()?;

        // Perform a vector search (with 1 result)
        let res = index.search(&[1.1, 2.1, 3.1], 1, EPSILON)?;
        assert_eq!(res[0].id, id1);

        // PROBLEM HERE
        index.remove(id1)?;

        // Cleanup - remove the index path
        std::fs::remove_dir_all(&index_path)?;

        Ok(())
    }

    #[test]
    fn test01_L1() -> Result<()> {
        run_test(NgtDistance::L1)
    }

    #[test]
    fn test02_L2() -> Result<()> {
        run_test(NgtDistance::L2)
    }

    #[test]
    fn test03_Angle() -> Result<()> {
        run_test(NgtDistance::Angle)
    }

    #[test]
    fn test04_Hamming() -> Result<()> {
        run_test(NgtDistance::Hamming)
    }

    #[test]
    fn test05_Cosine() -> Result<()> {
        run_test(NgtDistance::Cosine)
    }

    #[test]
    fn test06_NormalizedAngle() -> Result<()> {
        run_test(NgtDistance::NormalizedAngle)
    }

    #[test]
    fn test07_NormalizedCosine() -> Result<()> {
        run_test(NgtDistance::NormalizedCosine)
    }

    #[test]
    fn test08_Jaccard() -> Result<()> {
        run_test(NgtDistance::Jaccard)
    }

    #[test]
    fn test09_SparseJaccard() -> Result<()> {
        run_test(NgtDistance::SparseJaccard)
    }

    #[test]
    fn test10_NormalizedL2() -> Result<()> {
        run_test(NgtDistance::NormalizedL2)
    }

    #[test]
    fn test11_Poincare() -> Result<()> {
        run_test(NgtDistance::Poincare)
    }

    #[test]
    fn test12_Lorentz() -> Result<()> {
        run_test(NgtDistance::Lorentz)
    }
}

This is the output from the test run:
$ cargo test -- --test-threads=1
   Compiling ngtbug v0.1.0 (/home/caleb/tmp/ngtbug)

running 12 tests
test tests::test01_L1 ... ok
test tests::test02_L2 ... ok
test tests::test03_Angle ... ok
test tests::test04_Hamming ... ok
test tests::test05_Cosine ... ok
test tests::test06_NormalizedAngle ... FAILED
test tests::test07_NormalizedCosine ... FAILED
test tests::test08_Jaccard ... ok
test tests::test09_SparseJaccard ... FAILED
test tests::test10_NormalizedL2 ... FAILED
test tests::test11_Poincare ... ok
test tests::test12_Lorentz ... FAILED

failures:

---- tests::test06_NormalizedAngle stdout ----
id1: 1
id2: 2
Error: Capi : ngt_remove_index() : Error: /home/caleb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ngt-sys-2.1.3/NGT/lib/NGT/Index.h:remove:1544: Not found the specified id

---- tests::test07_NormalizedCosine stdout ----
id1: 1
id2: 2
Error: Capi : ngt_remove_index() : Error: /home/caleb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ngt-sys-2.1.3/NGT/lib/NGT/Index.h:remove:1544: Not found the specified id

---- tests::test09_SparseJaccard stdout ----
Error: Capi : ngt_insert_index_as_float() : Error: /home/caleb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ngt-sys-2.1.3/NGT/lib/NGT/ObjectRepository.h:allocatePersistentObject:345: ObjectSpace::allocatePersistentObject: Fatal error! The dimensionality is invalid. The specified dimensionality=3. The specified object=2.

---- tests::test10_NormalizedL2 stdout ----
id1: 1
id2: 2
Error: Capi : ngt_remove_index() : Error: /home/caleb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ngt-sys-2.1.3/NGT/lib/NGT/Index.h:remove:1544: Not found the specified id

---- tests::test12_Lorentz stdout ----
id1: 1
id2: 2
thread 'tests::test12_Lorentz' panicked at src/main.rs:40:23:
index out of bounds: the len is 0 but the index is 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    tests::test06_NormalizedAngle
    tests::test07_NormalizedCosine
    tests::test09_SparseJaccard
    tests::test10_NormalizedL2
    tests::test12_Lorentz

test result: FAILED. 7 passed; 5 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

The failures in SparseJaccard and Lorentz are interesting but unrelated to my issue. I need to use NormalizedCosine for my application.
Comments
It is possible this is an issue with the upstream NGT library. I am not sure but I decided to ask here first.  It is also possible that I have missed some detail about these distance types are supposed to be used.

Thanks for the detailed report, I am indeed able to reproduce the errors you see.
I also think it might be due to some bugs in the underlying NGT code and it would be worth reporting it there too.
I will try to investigate NGT code.

Ok I made a reproducer using ngt-py and made a corresponding issue there ☝🏼

@cjrh @lerouxrgd this looks to be fixed in the latest release https://github.com/yahoojapan/NGT/releases/tag/v2.1.5

GitHub automatically closed this issue when I merged the PR, however there seems to be an issue remaining for Lorenz and SparseJacccard distances. I have mentioned it in the related NGT issue.

As Lorentz and SparseJaccard seem a bit special, I have released 0.7.0 that fixes the issue for the other distances.


Keeps disconnecting from Google

Draw.io keeps disconnecting from Google after a short time. Is there a way to adjust this?

Is this still happening?

No!

How handy...


New Activity When text fill full

How can i go to next activity when i put full fill text

You can use TextWatcher to listening the text changes.


Apply PHP 7.1 typing

Coverage decreased (-0.9%) to 91.936% when pulling 6f23c062fe88e2b624b05fcc7317de7ab1f3fc31 on keradus:3.0_71_typing into a01d9a5d2f62b983bacbc565c05d3d2f086c90f3 on FriendsOfPHP:3.0.


Data Grid: Add sortable header cell to Figma component

https://www.figma.com/file/7KgRuAqrlNM8pYSMRthbjt/branch/S3KmWEEmAwHvYq1jS6KolU/Salt-Light-Components?node-id=16%3A3068&t=zyvRpo1HQY5Q7vD7-1

March 28 - will need to add to figma component for release -

March 31 - Figma components and QA playground have been completed; reviewed with Ben; and merged into the main branch


.htpasswd authentication not working when using allow_unauthenticated_reads: true

We're running the docker image on version 2.1.2 in our environment and detected a problem with the allow_unauthenticated_reads: true feature.
Used version of the image:
$ docker images
buchgr/bazel-remote-cache   latest    c2afbbddcd67

Docker run command to start the image:
docker run -p 8080:8080 -v ~/.config/bazel-remote/:/config buchgr/bazel-remote-cache --config_file /config/cache.yaml

When we now use basic auth (with a .htpasswd file provided in the config) to connect to the cache from bazel, we get 401 errors for "PUT" requests.
This does not happen when allow_unauthenticated_reads is disabled and everything else is the same.

Hi, could you share your config file and bazel-remote's startup log?

Here are the logs and the config
Startup log:
[ec2-user@ip-<redacted> ~]$ docker run -p 8080:8080 -v ~/.config/bazel-remote/:/config buchgr/bazel-remote-cache --config_file /config/cache.yaml
2021/09/09 10:09:43 bazel-remote built with go1.16.2 from git commit ee83b71253a191f8fbf5a95f06758c0986dc4bfe.
Using S3 backend.
2021/09/09 10:09:43 Initial RLIMIT_NOFILE cur: 32768 max: 65536
2021/09/09 10:09:43 Setting RLIMIT_NOFILE cur: 65536 max: 65536
2021/09/09 10:09:43 Loading existing files in /home/ec2-user/cache.
2021/09/09 10:09:43 Sorting cache files by atime.
2021/09/09 10:09:43 Building LRU index.
2021/09/09 10:09:43 Finished loading disk cache files.
2021/09/09 10:09:43 Loaded 0 existing disk cache items.
2021/09/09 10:09:43 Authentication: basic
2021/09/09 10:09:43 Access mode: authentication required for writes, unauthenticated reads allowed
2021/09/09 10:09:43 Mangling non-empty instance names with AC keys: disabled
2021/09/09 10:09:43 Starting HTTP server on address <IP_ADDRESS>:8080
2021/09/09 10:09:43 HTTP AC validation: enabled
[...]
2021/09/09 10:10:14 S3 DOWNLOAD <redacted> <redacted>/ac/31/311ee57031836b5717331ceaebd7990254f32496cb1b92f9865c764bc1ec4fa5 NOT FOUND
2021/09/09 10:10:14  GET 404     <redacted> /ac/311ee57031836b5717331ceaebd7990254f32496cb1b92f9865c764bc1ec4fa5
2021/09/09 10:10:18  PUT 401     <redacted> /cas/4042d72b9e413c66e6ae9976e9db6ca12692bb4d2c0e744e611e1a394d32d102
2021/09/09 10:10:18  PUT 401     <redacted> /cas/2d08f6b55a8067a82b4b9710c031aefe3aea93407a4973cc975368f009d2edbd
2021/09/09 10:10:18  PUT 401     <redacted> /cas/b021bd2130ba7d9f33ba1db2108b3112f6156f1a84956764349427974f220914
2021/09/09 10:10:18  PUT 401     <redacted> /cas/3cccb4056a13a6d813171efc4088a8a729e4cb0735889d81a2f48ae1a87eaae9
2021/09/09 10:10:18  PUT 401     <redacted> /cas/76886956a9113a5112ebf1cf1054935516c0b411fc6f1102deb58c88842f6112
[...]

Short Version of config (all "#" lines removed):
dir: /home/ec2-user/cache
max_size: 25
host: <IP_ADDRESS>
port: 8080
http_read_timeout: 15s
http_write_timeout: 20s
htpasswd_file: /config/.htpasswd
allow_unauthenticated_reads: true
key_format: 2
s3_proxy:
  endpoint: s3.eu-central-1.amazonaws.com
  bucket: <redacted>
  prefix: <redacted>
  access_key_id: <redacted>
  secret_access_key: <redacted>

Long Version of config
# These two are the only required options:
dir: /home/ec2-user/cache
max_size: 25

# The form to store CAS blobs in ("zstd" or "uncompressed"):
#storage_mode: zstd

host: <IP_ADDRESS>
# The port to use for HTTP/HTTPS:
port: 8080
# The port to use for gRPC:
#grpc_port: 9092

# If profile_port is specified, then serve /debug/pprof/* URLs here:
#profile_host: <IP_ADDRESS>
#profile_port: 7070

# HTTP read/write timeouts. Note that these do not apply to the proxy
# backends or the profiling endpoint. Reasonable values might be twice
# the length of time that you expect a client to read/write the largest
# likely blob. Units can be one of: "s", "m", "h".
http_read_timeout: 15s
http_write_timeout: 20s

# Specify a certificate if you want to use HTTPS:
#tls_cert_file: path/to/tls.cert
#tls_key_file:  path/to/tls.key
# If you want to use mutual TLS with client certificates:
#tls_ca_file: path/to/ca/cert.pem

# Alternatively, you can use simple authentication:
htpasswd_file: /config/.htpasswd

# If tls_ca_file or htpasswd_file are specified, you can choose
# whether or not to allow unauthenticated read access:
allow_unauthenticated_reads: true

#To avoid per-prefix rate limiting with Amazon S3 enable:
key_format: 2
# If specified, bazel-remote should exit after being idle
# for this long. Time units can be one of: "s", "m", "h".
#idle_timeout: 45s

# If set to true, do not validate that ActionCache
# items are valid ActionResult protobuf messages.
#disable_http_ac_validation: false

# If set to true, do not check that CAS items referred
# to by ActionResult messages are in the cache.
#disable_grpc_ac_deps_check: false

# If set to true, enable metrics for each HTTP/gRPC endpoint.
#enable_endpoint_metrics: false

# Specify a custom list of histogram buckets for endpoint request duration metrics
#endpoint_metrics_duration_buckets: [.5, 1, 2.5, 5, 10, 20, 40, 80, 160, 320]

# At most one of the proxy backends can be selected:
#
# If this is 0, proxy backends won't upload blobs.
#num_uploaders: 100
# The maximum number of proxy uploads to queue, before dropping uploads.
#max_queued_uploads: 1000000
# The largest blob size that will be accepted, for example 10MB:
#max_blob_size: 10485760
#
#gcs_proxy:
#  bucket: gcs-bucket
#  use_default_credentials: false
#  json_credentials_file: path/to/creds.json
#
s3_proxy:
  endpoint: s3.eu-central-1.amazonaws.com
  bucket: <redacted>
  prefix: <redacted>
  access_key_id: <redacted>
  secret_access_key: <redacted>
#
# Provide either access_key_id/secret_access_key, or iam_role_endpoint/region.
# iam_role_endpoint can also be left empty, and figured out automatically.
#  iam_role_endpoint: http://<IP_ADDRESS>
#  region: us-east-1
#
#http_proxy:
#  url: https://remote-cache.com:8080/cache

# If set to a valid port number, then serve /debug/pprof/* URLs here:
#profile_port: 7070
# IP address to use, if profiling is enabled:
#profile_host: <IP_ADDRESS>

# If true, enable experimental remote asset API support:
#experimental_remote_asset_api: true

# If supplied, controls the verbosity of the access logger ("none" or "all"):
#access_log_level: none

I have a potential fix in #469 - but I still need to add some regression tests before landing.
Could you try this in the meantime, and report if it works for you?
https://hub.docker.com/layers/mostynb/bazel-remote-cache/fix_basic_http_auth_writes/images/sha256-3d6aea11b1adadbbd0f6cca7083541d8e4654dc8079355d047dbe79b24d2a389?context=repo

I have a potential fix in #469 - but I still need to add some regression tests before landing.
Could you try this in the meantime, and report if it works for you?
https://hub.docker.com/layers/mostynb/bazel-remote-cache/fix_basic_http_auth_writes/images/sha256-3d6aea11b1adadbbd0f6cca7083541d8e4654dc8079355d047dbe79b24d2a389?context=repo

hi,
I tested it right now:
"allow_unauthenticated_reads = true" => PUT requests are not anymore shown in logs, also nothing is available on machine/s3
"allow_unauthenticated_reads=false" => PUT requests are shown in the logs and everything is working properly

@mostynb if I read @minmichail 's comment correctly, the cache isn't working at all, since the request seems to get lost. I don't think this resolves the issue - at least if I read @minmichail 's comment correctly.

Sorry- I created some tests, then reworked the PR with the tests passing now. There's a new image with these updates that you can try here (I was waiting for that to finish before leaving an update here):
https://hub.docker.com/layers/buchgr/bazel-remote-cache/latest/images/sha256-b5d8a7d5ae0f647444d6ea41017c57b7b41b5fbdebc342aef365924ae57b96a8?context=repo
(Reopening the issue until the fix has been confirmed...)

issue seems to be fixed.
Thanks for your quick support  @mostynb

Thanks for checking- released v2.1.3 (and pushed it to docker hub).


Convert Base64 encoded IDs to hex encoded IDs

The '/' character is causing trouble when querying from elasticsearch. A hex encoding will fix this. Afterwards, the indices will need to we wiped and reloaded.

Changed encoding in ParseResumes and ExtractPictures and renamed the data folder pictures to the new encoding as well.


Fix helm chart ingress

Fix for values.schema.json in helm chart.
With type "string" it cannot validate paths.path array in values.yaml

Thanks @BlindB0 . I have requested @knrt10 to take a look.
Can you sign your commits so the DCO checks validate it? (git commit --amend -s will do the job)


chore: use eslint-config-ipfs import sorting

This PR shows an example of what changes https://github.com/ipfs/eslint-config-ipfs/pull/126
would enforce. All of this these changes (except package.json) were done
by running npm run lint -- --fix.
CALLOUTS:

eslint was failing with locally linked package on missing plugins.
lint fix was called twice, with the first run failing due to an empty
line the first fix runthrough didn't fix.
tsc seems to be failing for aegir

tsc seems to be failing for aegir

It's failing because the automated reordering of imports didn't also move the associated // @ts-expect-error comments from above imports of modules that don't export types.
E.g. this used to work:
// @ts-expect-error foo-no-types has no types
import foo from 'foo-no-types'
import bar from 'bar-has-types'

then with the changes in https://github.com/ipfs/eslint-config-ipfs/pull/126 aegir lint --fix turns it into this:
// @ts-expect-error foo-no-types has no types
import bar from 'bar-has-types'
import foo from 'foo-no-types'

so it explodes because the @ts-expect-error is no longer on the line above the import of the module that has no types.

Superseded by #1229


Is there a small model trainer, such as llama2.c?

Is there a small model trainer, such as llama2.c?

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

@win10ogod what do you mean,? A trainer to train this model? You should try making a script to train it we need help there

llama2.c

I believe it would be beneficial to introduce a training program akin to llama2.c to enhance understanding of this project among a wider audience. Not everyone involved may have an engineering background or be an expert in this field.

We can use simple training projects to train models that can use voice dialogue, which will help the project become more widely known.

@win10ogod Yeah good idea, can you help make this happen I'm still smoothening out some rough spots?

@kyegomez
Hello, please refer to the code in llama2.c. As long as you can truly implement the project.

@win10ogod submit a pull request for the training code, the implementation is complete

@win10ogod submit a pull request for the training code, the implementation is complete

Which pull request is it? Can you provide a link?

@kyegomez


Variables Passed to renderGraphiQL Are Occluded by Default Assignment

Using graphiqlExpress specifically here, but Hapi and Koa all have the same issue as well:

https://github.com/apollostack/graphql-server/blob/master/packages/graphql-server-express/src/expressApollo.ts#L161
https://github.com/apollostack/graphql-server/blob/master/packages/graphql-server-hapi/src/hapiApollo.ts#L227
https://github.com/apollostack/graphql-server/blob/master/packages/graphql-server-koa/src/koaApollo.ts#L127

Given an invocation like this:
const initialQuery = `query exampleQuery ($name: String!) {
  person(name: $name) {
    id
    name
  }
}`;

const initialVariables = { name: 'Joe Bob' };

app.use('/graphiql', graphiqlExpress({
  endpointURL: '/graphql',
  query: initialQuery,
  variables: initialVariables,
}));

... your variables will never be used.
This is because an initial assignment is made inside of graphiqlExpress, etc, of:
const variables = q.variables || '{}';

And then renderGraphiQL is invoked with:
variables: JSON.parse(variables) || options.variables,

Because variables will always be an empty object if you didn't pass variables in the query string, options.variables will never be provided.

@hansef Good catch! Could you make a PR to fix it!? 🙂

Yep, will hit it shortly. 😉

@hansef how shortly is "shortly"? :wink:

Hi guys, coworker of @hansef here.
I forked graphql-server and followed the instructions of npm link'ing it into another app. I picked https://github.com/apollostack/frontpage-server, figuring it should be easily amenable. I made some modifications to support this bug scenario (https://github.com/cdidyk/frontpage-server/tree/query-posts-with-variables), but another coworker using frontpage-server master got the same problem I'm about to describe.
graphiql for frontpage-server works fine if I npm install and thus use the version of graphql-server-express from npm. However, if I npm link in my local version of graphql-server-express, graphiql gives me the dreaded "Schema must be an instance of GraphQLSchema. Also ensure that there are not multiple versions of GraphQL installed in your node_modules directory." error message. I can view /schema and it looks ok. I can console.log it and it looks ok and of the correct type. I also don't see any extra versions of graphql in node_modules.
Any idea what might be going on? Or is there a more preferable sample app setup? I'm grateful for any help/insight you can provide.


'docker build -t tuya:latest .' won't work until:

It will fail with sth like this:
[+] Building 0.5s (2/2) FINISHED                                                                                docker:default
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 426B                                                                                0.0s
 => ERROR [internal] load metadata for docker.io/phusion/baseimage:master                                                                                0.4s
------
 > [internal] load metadata for docker.io/phusion/baseimage:master:
------
Dockerfile:1
--------------------
   1 | >>> FROM phusion/baseimage:master
   2 |
   3 |     RUN apt-get update && apt-get install -y sudo iproute2 iputils-ping
--------------------
ERROR: failed to solve: phusion/baseimage:master: failed to resolve source metadata for docker.io/phusion/baseimage:master: docker.io/phusion/baseimage:master: not found

It will work if you change the first line in the Dockerfile to this:
FROM phusion/baseimage:jammy-1.0.4

Just wanted it to be available for anybody walking  that road behind me ;-)


Not working with aframe 1.1.0

It doesnt work on aframe 1.1.0. It crushes as soon as the component is added to a entity that in the scene.
Uncaught TypeError: Cannot read property 'array' of undefined
    at TextGeometry.computeBoundingSphere (index.js:96)
    at P.raycast (three.js:8649)
    at ki (three.js:34685)
    at Ui.intersectObjects (three.js:34733)
    at i.checkIntersections (raycaster.js:227)
    at i.tock (raycaster.js:199)
    at HTMLElement.tock (a-scene.js:764)
    at e.object3D.onAfterRender (a-scene.js:53)
    at We.render (three.js:18659)
    at HTMLElement.render (a-scene.js:798)

Ah thank you for the issue report! I'll take a look at this issue and try to solve it

Ah thank you for the issue report! I'll take a look at this issue and try to solve it

As it turns out this was an issue with Aframe v1.1.0 itself, as further explained in this comment
Using the latest master build (using the URL below) instead of v1.1.0 seems to resolve the issue (and should be fixed by the next aframe release)

<EMAIL_ADDRESS>

As it turns out this was an issue with Aframe v1.1.0 itself, as further explained in this comment
Using the latest master build (using the URL below) instead of v1.1.0 seems to resolve the issue (and should be fixed by the next aframe release)

<EMAIL_ADDRESS>


rspec exits with 0, but fails to display tail message

Versions:
ruby "2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin17]"
gem 'rails', '~> 4.2'
gem 'rspec-rails', '~> 3.6'
gem 'spring-commands-rspec', '~> 1.0'
gem 'rubocop-rspec', '~> 1.10.0', require: false # upgrades need to be tested with rubocop version
gem 'rspec_junit_formatter', '~> 0.3'
gem 'rspec-retry', '~> 0.5'
gem 'rspec-collection_matchers', '~> 1.1'

Output:
bin/rspec spec/requests/api/v1/users_request_spec.rb
Running via Spring preloader in process 47193
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

/v1/users
  /two_factor_auth
    with a user that has no phone
      supplying an email

====> React On Rails: Checking app/assets/webpack for outdated/missing bundles

        returns success
        returns the id of the account
        fires an email with the otp
      supplying a good code and good phone number
        returns success
        returns the id of the account
        uses the user's unverified phone number
      supplying a good phone number with attached code with ISO human style
        returns success
        returns the id of the account
        uses the user's unverified phone number
      supplying a good phone number with attached code with ISO machine style
        returns success
        returns the id of the account
        uses the user's unverified phone number
      supplying a good phone number with attached code with ISO machine style no plus
        returns success
        returns the id of the account
        uses the user's unverified phone number
      supplying a good phone number human without attached code
        returns success
        returns the id of the account
        uses the user's unverified phone number
      supplying a bad code and good phone number
        returns 422
        returns a success of false
        contains the bad number error message
      supplying a bad code and bad phone number
        returns 422
        returns a success of false
        contains the bad number error message
      supplying a really bad phone number
        returns 422
        returns a success of false
        contains the bad number error message
      supplying a bad phone number
        returns 422
        returns a success of false
        contains the bad number error message
      without a phone number
        returns unprocessable_entity
        returns a success of false
        contains the no phone number error message
    when the user already has a (unverified) number
      supplying an email
        returns success
        returns the id of the account
        returns the obfuscated phone of the account
        fires an email with the otp
      supplying a good code and good phone number
<EMAIL_ADDRESS>at . on ± i2fa 𝑓 echo $?
0

I can definitely supply more information if needed.

If I specify certain contexts, via line specification, I don't get this issue. Currently I'm "bisect"ing my way though this, apparently there's a specific test that's doing this.

I've further narrowed it down to only spec contexts that contain a include_examples of a specific shared example:
    shared_examples "the user response has the phone number obfuscated" do
      it "returns the obfuscated phone of the account" do
        expect(response).to have_json_attributes("phone" => "********#{phone.last(2)}")
      end
    end

If I put a binding.pry in that example, in a test context that would normally "strange good exit", it now exits good, but with the correct tail:
𝑓 bin/rspec spec/requests/api/v1/users_request_spec.rb:283
Running via Spring preloader in process 47850
Run options: include {:focus=>true, :locations=>{"./spec/requests/api/v1/users_request_spec.rb"=>[283]}}

/v1/users
  /two_factor_auth
    when the user already has a (unverified) number
      supplying an email

====> React On Rails: Checking app/assets/webpack for outdated/missing bundles

        fires an email with the otp

Finished in 1.9 seconds (files took 0.34878 seconds to load)
1 example, 0 failures

I've removed two comments because they were false alarms.

Okay, I've tracked it down to this:
At the top level of this test I have this:
    before do
      post "/api/v1/users/two_factor_auth", JSON.dump(body), default_headers.merge(headers)
    end

If I binding.pry inside that, before the post, and I manually call it:
    29:       end
    30:     end
    31:
    32:     before do
    33:       binding.pry
 => 34:       post "/api/v1/users/two_factor_auth", JSON.dump(body), default_headers.merge(headers)
    35:     end
    36:
    37:     context "with a user that has no phone" do
    38:       let(:user) { create(:user, phone: nil) }
    39:

(test) #<RSpec::ExampleGroups::V1Users::TwoFactorAuth::WhenTheUserAlreadyHasAUnverifiedNumber::SupplyingABadPhoneNumber:0x00007fe893b9b378>:0> post "/api/v1/users/two_factor_auth", JSON.dump(body), default_headers.merge(headers)
``

There's zero loglines generated from that expression in my rails test.log, so that leaves me to believe the problem lies inside rpsec's scope of things.

I noticed you're running rspec via spring.  Can you try without spring?  Historically, spring has been the source of many, many odd behaviors folks see when using it to run RSpec.
Also, can you grep your codebase (and your gems, if possible) to see if any of them might be calling exit anywhere?

Historically, spring has been the source of many, many odd behaviors folks see when using it to run RSpec.

I should have known. I'm no fan, anyways this is what spring was hiding:
     SystemStackError:
       stack level too deep
     # ./spec/requests/api/v1/users_request_spec.rb:385:in `block (5 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:264:in `block (4 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:385:in `block (5 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:264:in `block (4 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:385:in `block (5 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:264:in `block (4 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:385:in `block (5 levels) in <top (required)>'
     # ./spec/requests/api/v1/users_request_spec.rb:264:in `block (4 levels) in <top (required)>'

I can handl it from here.

9 times out of 10 this kind of error is because I have a recursive application code level problem, not necessarily in the spec suite. Just a heads up for future lookers.