Feature: brew edit: autotap homebrew/core

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
I think brew edit should automatically tap homebrew/core (maybe only if the formula actually exists in https://formulae.brew.sh/). If my memory serves me well, that used to be the case. Now, the behavior is the following:
$ brew edit cbonsai
Usage: brew edit [options] [formula|cask ...]

Open a formula or cask in the editor set by EDITOR or HOMEBREW_EDITOR,
or open the Homebrew repository for editing if no formula is provided.

      --formula, --formulae        Treat all named arguments as formulae.
      --cask, --casks              Treat all named arguments as casks.
      --print-path                 Print the file path to be edited, without
                                   opening an editor.
  -d, --debug                      Display any debugging information.
  -q, --quiet                      Make some output more quiet.
  -v, --verbose                    Make some output more verbose.
  -h, --help                       Show this message.

Error: Invalid usage: cbonsai doesn't exist on disk.
Run brew create --set-name cbonsai $URL to create a new formula!

I found that tapping homebrew/core fixes it:
$ brew tap homebrew/core
Warning: Tapping homebrew/core is no longer typically necessary.
Add --force if you are sure you need one.
==> Tapping homebrew/core
Cloning into '/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core'...
remote: Enumerating objects: 1543905, done.
remote: Counting objects: 100% (1543903/1543903), done.
remote: Compressing objects: 100% (456934/456934), done.
remote: Total 1543905 (delta 1083859), reused 1543817 (delta 1083802), pack-reused 2
Receiving objects: 100% (1543905/1543905), 402.14 MiB | 6.29 MiB/s, done.
Resolving deltas: 100% (1083859/1083859), done.
Tapped 3 commands and 6752 formulae (7,121 files, 460.7MB).
$ brew edit cbonsai
Warning: Unless `HOMEBREW_NO_INSTALL_FROM_API` is set when running
`brew install`, it will ignore your locally edited formula.
Editing /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/cbonsai.rb

Let me know if not automatically tapping is intentional because of migrating from Git-cloned taps to JSON downloads. I don't think a contributor would mind a little extra storage overhead. And from the brew edit warning message, it shouldn't affect the default download method.
What is the motivation for the feature?
I ran brew edit and noticed that
How will the feature be relevant to at least 90% of Homebrew users?
It will not. This feature is for beginner contributors who may not have read the full documentation yet (especially the part instructing the contributor to tap).
What alternatives to the feature have been considered?

Manually tapping (what I did)
Adding to the error message (an alternative "feature")

System information
$ brew doctor
Your system is ready to brew.
$ brew config
HOMEBREW_VERSION: 4.0.28-35-g18b4fc4
ORIGIN: https://github.com/Homebrew/brew
HEAD: 18b4fc4ba5e9ac917479587e147a319adfddfe45
Last commit: 19 hours ago
Core tap origin: https://github.com/Homebrew/homebrew-core
Core tap HEAD: dc62629778adfb8ee0b6be6a0f77c3da00025ea7
Core tap last commit: 24 minutes ago
Core tap branch: master
Core tap JSON: 11 Jul 17:01 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.10 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.10_1/bin/ruby
CPU: octa-core 64-bit skylake
Clang: N/A
Git: 2.34.1 => /bin/git
Curl: 7.81.0 => /bin/curl
Kernel: Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64 GNU/Linux
OS: Ubuntu 22.04.2 LTS (jammy)
WSL: 2 (Microsoft Store)
Host glibc: 2.35
/usr/bin/gcc: 11.3.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@11: N/A
gcc: N/A
xorg: N/A

The same goes for brew audit (and perhaps other related developer commands):
$ brew doctor
Your system is ready to brew.
$ brew audit
Error: Calling brew audit is disabled! Use brew audit --eval-all or HOMEBREW_EVAL_ALL instead.
$ brew audit --eval-all
Error: No matching formulae or casks to audit!
$ HOMEBREW_EVAL_ALL=1 brew audit
Error: No matching formulae or casks to audit!
$ HOMEBREW_EVAL_ALL=1 brew audit --eval-all
Error: No matching formulae or casks to audit

We probably won't do this for eval all given it's not clear from that alone whether you are interested in Homebrew/core, Homebrew/cask, both, or neither (just third-party taps).
I agree that error messages should however be improved at least.

We probably won't do this for eval all given it's not clear from that alone whether you are interested in Homebrew/core, Homebrew/cask, both, or neither (just third-party taps).

Fair point. What about for one specific formula? i.e.
$ brew audit cbonsai
Error: No available formula with the name "cbonsai".

Not sure what the error message should be, considering edge cases like docker being both the name of a formula and the name of a cask.
I'd say either a generic error message, or a behavior that is consistent with pre-api (I don't remember what the behavior was).

The README might also need to be edited based on the https://github.com/Homebrew/brew#contributine, since brew audit --strict without args is a recommended way to contribute.

I just realized that the brew edit behavior is fine since https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request instructs to brew tap --force homebrew/core. The issue with argument-less brew audit might just require updating the README. Let me know if I should open a new issue.


Failed tests are not shown in Annotations

Hi,
I'm using such step in gh actions:
      - name: Publish Test Report
        uses<EMAIL_ADDRESS>        if: success() || failure() # always run even if the previous step fails
        with:
          report_paths: '**/build/test-results/test/TEST-*.xml'

In the end, I see such a report, but failed test(assertion) is not shown in the annotations.

Am I doing something wrong or is it a bug?

By default the action will create the annotations via the checks API of GitHub: https://github.com/mikepenz/action-junit-report/blob/main/src/annotator.ts#L85-L102
Would you like to see annotations within the test files? or your aim is to have the report of files which failed in the summary.
For the later you want to enable this by setting detailed_summary to true

Unfortunately, there are no annotations created in my Job Summary like in this example. https://github.com/mikepenz/action-junit-report/blob/main/.github/images/annotations.png
As you may see at my first screen I have only 1 annotation that build failed

I would need to see more logs for that, possibly with a sample to try to see why that may be the case.
An example build where such annotations are generated from this repos tests: https://github.com/mikepenz/action-junit-report/actions/runs/5304280643

same issue with run on schedule

Ok sorry for the late answer. Tested it now here: https://github.com/mikepenz/action-junit-report/actions/runs/5552550460
And it actually makes sense. Given there is no PR - so the action has no place where it can actually create the check for. Like how it would do here: https://github.com/mikepenz/action-junit-report/actions/runs/5552522553

So for this particular usecase I'd suggest to use annotate_only.
Which will result in an output like this: https://github.com/mikepenz/action-junit-report/actions/runs/5552618163

Thank you @mikepenz
annotate_only: ${{ github.event_name == 'workflow_dispatch' || github.event_name == 'schedule'}} - works in my case

That's great to hear!


fix bug: handle exception cases in vela comp status

Exception cases handled by vela comp status currently:

The component is unhealthy => show diagnosis
The component is not referenced by a HealthScope => show status as Not Diagnosed and workload status
The component is unknown to the HealthScope => show status as Not Diagnosed and workload status
The component's workload controller is not working => show status as Not Diagnosed and warning info

Signed-off-by: roy wang<EMAIL_ADDRESS>

Can you give the sample output for each case?

case 1

case 2 & 3

case 4

change the output of case 2&3 into yaml format


Enums are not extensible by default anymore

Next step into the migration from enum to union #269

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-autorest


Android audio classification example does not work on a Pixel with Android 10

URL(s) with the issue:
https://github.com/tensorflow/examples/tree/master/lite/examples/sound_classification/android
Description of issue (what needs changing):
Perhaps indicate that although hardware may support Android 6+, it may not be capable enough to run the example.
Clear description
The README.md file indicates that any device supporting Android 6+ with audio support is sufficient. While the example worked fine on my Pixel 4 XL (Android 11), it would not on my Pixel (Android 10). The screen controls are displayed, but it only displays "Silence" as the classification, and does not update the bar to the right as it does on my 4 XL. The slider control is also extremely slow to respond, somewhere on the order of 3/4 of a second to a second. I think the hardware just isn't capable enough to run TensorFlow even though it does support Android 10.

@wangtz could you take a look?

Hi @jcwren !
I am able to run Audio classification example with  Pixel 4 and 5 (Android 10) with Android Studio( Chipmunk). Could you let us know from your end.
Thank you!

My original post was from almost a year ago, and I no longer have the Pixel to test with. I don't believe it to be a problem with Android 10 so much as the original Pixel processor just doesn't have the "oomph" to run the application. I'm OK with closing this report since there's no further action I can take.  Thanks!

@jcwren !
Moving this issue to closed status as requested.
Thank you!


Generated Containers with only Extension Views do not restore focus on reload

Regressed this #89567
Search still works so it is not as major as the original issue. But, here's the summary:

On reload we try to restore a generated container.
That is successful, but the container has no views yet because extensions have not finished loading.
Since it has no views, we hide the view container and send focus to the default view (terminal for panel).

We now are able to construct a view pane container very rapidly but with incomplete information. If I hold the hide behavior mentioned in step 3 until after extension are loaded, this bug is fixed, but it exposes a separate issue. The generated container will show the default Custom Views title until the extension is loaded. Our cache is correct, but the cache is not used if the View Pane Container is present, even if it is incomplete.
Maybe we just add logic if the 'custom views' container title is returned from the model, we use the cache still?
/cc @eamodio

@sandy081 the fix here actually addresses 2 issues.

Use the cached panels that we added recently to prevent prematurely hiding the composite
A second issue arose where generated containers that were not focused during the reload were starting hidden and not showing until reload.

I am not a fan of the fix for the second issue, so we should revisit.

I reverted the previous change. Need to retackle.


Fix check for missing rv in factorized_joint_logprob

Currently, random variables that are not provided with their value variable equivalent can result in a KeyError in factorized_joint_logprob when given warn_missing_rvs=False. This error rose when working with a graph corresponding to a Gaussian random walk.
import aesara.tensor as at
from aeppl import factorized_joint_logprob

mu = at.random.normal(loc=2, scale=0.1)
sigma = at.random.gamma(shape=1, rate=1)
innovation_dist = at.random.normal(mu[..., None], sigma[..., None], size=(10,))
rv_out = at.cumsum(innovation_dist, axis=-1) # gaussian random walk

The following code chunk yields a KeyError:
factorized_joint_logprob(
    {
        rv_out: rv_out.copy(),
    },
    extra_rewrites=TransformValuesOpt({}),
    use_jacobian=True,
    warn_missing_rvs=False
)

but setting warn_missing_rvs=True only issues warnings.
In this PR, so far, I fix the case where users decide to not issue warnings.

Can you add a test? Your example should be fine just assert that the warning raised in one case but not the other, but the output is the same.

Done! There was already a test for this, I just added a verification for warn_missing_rvs=False

Failing test as described in #148:
https://github.com/aesara-devs/aeppl/blob/cc78f30b5ed89e5b247b88d697467a76cc1e424e/tests/test_scan.py#L349

You can just cherry pick this commit: https://github.com/aesara-devs/aeppl/commit/e0f9623fa6734061e05850eb14c72e18ddd7027f

You should have the two commits separate.
One for the xfail and the other for the bugfix and new test condition.

You should have the two commits separate.
One for the xfail and the other for the bugfix and new test condition.

Done! Thanks for the clarification

Small nitpick the test and bugfix make sense to go in the same commit

After several attempts and many force pushes, I think that I got it right (?) 😅


Find By Sign Value

The findByEntityName method of MagmaCoreService is fine for 'well-known' objects, i.e. those types and instances that a system needs to find quickly, such as reference data items or objects that are needed to bootstrap a model.
Many objects will be referred to by signs, therefore please provide a findBySignValue() method that uses the sign pattern to find objects identified by the given sign value - this should be used in preference to findByEntityName in most cases.
The method signature should probably be something like this:
    /**
     * Find the Set of {@link Thing} represented by the given sign value.
     *
     * <p>
     * This could probably be replaced with a (rather complex) SPARQL query if {@link MagmaCoreDatabase}
     * allowed the execution of such queries.
     * </p>
     *
     * @param community   the {@link RecognizingLanguageCommunity} that recognises the sign value.
     * @param pattern     the {@link Pattern} the sign conforms to.
     * @param value       {@link String} the sign value to look for.
     * @param pointInTime {@link PointInTime} the point in time we are interested in.
     * @return {@link Set} of {@link Thing} represented by the value.
     * @throws MagmaCoreException if the number of {@link RepresentationByPattern} found is not 1
     */
    public Set<? extends Thing> findBySignValue(
            final RecognizingLanguageCommunity community,
            final Pattern pattern,
            final String value,
            final PointInTime pointInTime) throws MagmaCoreException {
        // TO-DO: implement this - see GH-25
        return Set.of();
    }

I have a solution implemented locally and will create a PR when the prerequisite PRs are merged.


run --transform in global context

This give me access to all node.js stuff, that needed for difficult transformation scripts

Seems pretty dangerous... can you share what context you want access to?

Seems pretty dangerous...

Sorry, but I don't understand what mean is dangerous. You mean, that I pass some "virus" code in transform and totally destroy all my infrastructure?))

can you share what context you want access to?

I want to use maximum power of node.js. In my case, need to generate special doc._id via some libs, that need to be required in transform. Sorry, but it incomplete now in this PR, as it turned out, runInThisContext not enough.

+1
This script is being run by an administrator on the CLI, where does untrusted code come into play?
Sure, if you ask the web app user to input the code used in the transform, it will be unsafe.
But that's not happening here. This is a server-side CLI. You are entering the code, in the same way as writing it in a source file would be.
It's as safe as the account writing the code and running the command.

I would (for example) like to anonymize data going through the pipe. Doing that in a string parameter without access to globals is very difficult, I would have to manually recreate all the resources I need (within the constraints of a command parameter string).

@darky I have a neat solution incoming as another PR.

@datashaman thanks to your other PR, this can't be merged now... can you please update?

Whoa... Github has a new online merge-conflict fixer!


How I can update Osris/offsets?

How I can update offsets of Osris Hack?

There are no offsets.

How I can update the cheat? (on my own) Or it is automatically updated?

You can come back every update and change what he changed or re-download it?

Just clone/pull and recompile.

Things that may require updating after game update are:

memory patterns
interfaces versions
game structs and classes


adding saveLayerFinished callback when layers are saved

@xavijam the change you did related to save layers in a sequencial way changed also the number of times done is called.
Before your change done was being called as many times as layers and now it's only called once.
Basemaps dialog needs saveLayersFinished in order to enable layers buttons so once you changed the basemaps you couldn't change it again
I'm merging this since this is a hotfix. This needs to be removed and change saveLayers to match the previous behavior.
cc @saleiva

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


Migrate Logging tests to Junit5

Splitting out of https://github.com/square/okhttp/pull/6340 so that PR only focuses on native launcher


Implement Format for the core::ops structs.

Is it on purpose that RangeTo is omitted?

Is it on purpose that RangeTo is omitted?

Oops! Added now :)

I will add snapshot tests in a separate PR


[release-v1.9] tmp trigger build :robot:

Please merge, if no error. last build was 2 month ago. But inbetween images got renamed, so we need to push...

before this, we get no image e.g. like:
docker pull registry.ci.openshift.org/openshift/knative-eventing-kafka-broker-source-image:knative-v1.9

INFO[2023-12-20T13:17:15Z] Building knative-eventing-kafka-broker-source-image
INFO[2023-12-20T13:17:15Z] Created build "knative-eventing-kafka-broker-source-image-amd64"

hence merging


rule - cloudtrail_put_object_acl_public

to: @airbnb/streamalert-maintainers
size: small
Background
Sync latest version of rule that looks for use of PutObjectAcl that creates public objects.
Changes

Works for logs generated via CLI or API

Testing
StreamAlertCLI [INFO]: (59/59) Successful Tests
StreamAlertCLI [INFO]: (93/93) Alert Tests Passed
StreamAlertCLI [INFO]: Completed

Coverage remained the same at 95.636% when pulling 6185eda94a9e2b248937c4af6d21c7b1940e087b on mimeframe-cloudtrail-put-object-new into b1966aa630455d0dfd7f511476347dc30bbf97d5 on master.

@jacknagz I cool feature we could ship in the future is to make a helper that abstracts CTW from CWE so that way you can just write one rule

Coverage remained the same at 95.687% when pulling 69cdb15d304209f386ad3d9d2ad458158b2d1fae on mimeframe-cloudtrail-put-object-new into 8ce127356dac1be4249de6d90e2fddbacdf304b1 on master.


pagination sets next query even though there are no more results

If the query contains a limit, backend keeps returning MORE_RESULTS_AFTER_LIMIT even though there are none.
var q = ds.query(['Kind']).limit(10);

We make an end cursor comparison to detect where to terminate pagination, but it costs us one extra query that returns an empty list of results.

Our default pagination behavior has changed dramatically since this issue (almost exactly 1 year ago!). By default, we now run query after query until no results are returned. This behavior can be switched off to revert to manual pagination. But, this specific issue no longer applies to our library, and whatever is going on in "b/10688926", that's where the misleading backend behavior issue can be tracked.


Difference between ResNet and VGG train.prototxt?

In VGG, ReLU follows BatchNorm Layer immediately but in ResNet, a Scale Layer is inserted between BatchNorm and ReLU layer. Why is the inconsistency? What is the difference between these two usage?

According to Caffe Documents:
http://caffe.berkeleyvision.org/doxygen/classcaffe_1_1BatchNormLayer.html#details

Normalizes the input to have 0-mean and/or unit (1) variance across the batch.
This layer computes Batch Normalization as described in [1]. For each channel in the data (i.e. axis 1), it subtracts the mean and divides by the variance, where both statistics are computed across both spatial dimensions and across the different examples in the batch.
By default, during training time, the network is computing global mean/variance statistics via a running average, which is then used at test time to allow deterministic outputs for each input. You can manually toggle whether the network is accumulating or using the statistics via the use_global_stats option. For reference, these statistics are kept in the layer's three blobs: (0) mean, (1) variance, and (2) moving average factor.
Note that the original paper also included a per-channel learned bias and scaling factor. To implement this in Caffe, define a ScaleLayer configured with bias_term: true after each BatchNormLayer to handle both the bias and scaling factor.

So I think a BatchNorm Layer is always used with a scale Layer.

Hi Tianlin Gao,
please see the similar issue https://github.com/cvjena/cnn-models/issues/11


Multi-Agent Setup and Decision Making Implementation

@sarrah-basta discussed this today in our meeting. To follow up next week.

Thanks a lot for creating the issue !

Completed in the week 6 of the GSoC project. The merged pull request can be found at https://github.com/OREL-group/GSoC/pull/52


Add reset and expand to MacroContext

Re-submit of #552.
This PR adds .reset which allows the context to be returned to its initial state. It also removes the enforestation logic from .next to .expand.

This is looking great! Unless you had anything else you wanted to do I'll go ahead and merge it.

Nothing I can think of. Merge away.


Enable extension diagonally.

Currently, extension can happen in one way, either vertically or horizontally. It would be great if we allow users to extend the size diagonally.

@Lee-Si-Yoon Last time, I remember that you have made the extension to happen diagonally. If you have time, could you think of taking care of this issue?


NS1ZONE-5: Security Analysis

name: NS1ZONE-5: Security Analysis
about: Enables Security Analysis across the repository
title: 'NS1ZONE-5: Security Analysis'
labels: 'enhancement'
assignees: 'nkpetko'

Is your pull request related to the project? Please describe.
This pull request enables CodeQL security analysis for Pull Requests and any pushes to the master branch.
Describe how it works
On push, or pull request to the following paths:
- "pkg/**"
- ".github/workflows/**"
- "go.mod"
- "main.go"

It will perform this action, unless the commit message contains the following text:
[SKIP ANALYSIS]
Describe alternatives you've considered
N/A
Additional context
With security analysis, we can catch very easy to spot security vulnerabilities
Checks and Reviews
If you have passed all the above, await the actions to complete, and then await reviews to submitted.

Message from 'Alex B. (bkordan@vmminfra.net)' in channel '#ghc-upstream-auditor
(C033PV1EH62)' at 'Sunday 20 February 2022 19:03:23':
These changes are broken, they will not run correctly for the windows runner.


Retrieve custom StateEvent

Hello,
I'm using the Android SDK to interact with a Matrix server and I need to retrieve a custom StateEvent with a type like com.corp.feature but I didn't find a way to call:
GET /_matrix/client/r0/rooms/{roomId}/state/{eventType}
Is it me having trouble understanding how the SDK works?
Is this call not supposed to be implemented in org.matrix.androidsdk.rest.api.RoomsApi?
Best regards,

merged on develop


feat: update backstage chart to 1.9.1

Description of the change

Existing or Associated Issue(s)

Additional Information

Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Variables are documented in the values.yaml and added to the README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes.
[x] JSON Schema template updated and re-generated the raw schema via pre-commit hook.
[x] List tests pass for Chart using the Chart Testing tool and the ct lint command.

Depends on #5 being merged first? if so you'll have to rebase since that bumps the chart version too.


Update renovatebot/github-action action to v34.124.1

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v34.109.1 -> v34.124.1

Release Notes

renovatebot/github-action
v34.124.1
Compare Source
See the the changelog for changes in all releases.
34.124.1 (2023-02-04)
Bug Fixes

deps: update renovate/renovate docker tag to v34.124.1 (28cf1e9)

v34.122.0
Compare Source
See the the changelog for changes in all releases.
34.122.0 (2023-02-04)
Features

Allow using non-slim renovate image (#626) (e18dc08)

Bug Fixes

broken release (#687) (0a8bd9a)
deps: update renovate/renovate docker tag to v34.111.1 (6231276)
deps: update renovate/renovate docker tag to v34.113.0 (8949164)
deps: update renovate/renovate docker tag to v34.114.0 (673af1b)
deps: update renovate/renovate docker tag to v34.114.1 (#683) (76551df)
deps: update renovate/renovate docker tag to v34.115.1 (f879033)
deps: update renovate/renovate docker tag to v34.116.0 (493d6ca)
deps: update renovate/renovate docker tag to v34.116.1 (985cb3a)
deps: update renovate/renovate docker tag to v34.117.1 (d29dda5)
deps: update renovate/renovate docker tag to v34.118.2 (38ae6ca)
deps: update renovate/renovate docker tag to v34.119.5 (aeff215)
deps: update renovate/renovate docker tag to v34.120.0 (d005484)
deps: update renovate/renovate docker tag to v34.121.0 (bf8b93a)
deps: update renovate/renovate docker tag to v34.122.0 (4793a06)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


Pinctrl for applicable ARC boards

Some ARC development boards support pinmuxing. The HSDK board had a minimal pinmux driver which was removed when pinmux got deprecated. Since the default pinmux setting cover typical use of these boards, pinctrl support is not required but it would be good to support this in a future release.

See also #39740 for Zephyr roadmap for pinctrl.
To be investigated if this also applies to ARC development boards "pmodmux" feature (not pin-level, but connector level pin muxing).

Duplicate of https://github.com/zephyrproject-rtos/zephyr/issues/52436


Adding word limits to ASC response fields on the platform

The issue
As an admin, I have to manually check whether answers provided in relation to Additional Selection Criteria are within the 250-word limit that always applies to this question. This task takes members of my team a very long time to complete, especially when we have large exercises with over 400 candidates. User error can also occur when the text is copied out of the platform and pasted into Word to check, leading to a lack of accuracy.
Describe what solution you would like
I would like functionality that automatically applies a 250-word limit to the answer field for Additional Selection Criteria questions.
This will ensure that word limit requirements are applied fairly for all candidates while reducing drain on Selection Exercise Team resources.
If users are able to include bullet points or numbering that is not included in the word count, that is ideal.
Describe alternatives you have considered
Current state - manual checking of application form answers, which is too resource intensive.
The issue

ive just had a once over of the scenario word limit logic and what ive written for this solution works quite differently, but a notable differing requirement is removing hyphens so i think for now it may be best to leave them separate although same of the logic could eventually go to JAC-kit for sharing/future refactoring

Hey @KateMJAC and @tomlovesgithub there are other places in the code base that ask the 'Additional Selection Criteria' questions, as follows:

Self Assessment Competencies
Statement of Eligibility
Statement of Suitability

This change will need rolling out to all those places.
In addition there's a little too much duplication so, unless there are subtle differences I haven't spotted, I'd suggest we refactor slightly so we re-use one piece of code for ASC questions. @tomlovesgithub you know what to do :)

A test script for this feature has been circulated to the user testing group. Responses/feedback should be provided in the uer testing Slack channel by COB 1 April.
This feature needs to be pushed to production when there are no exercises open. It looks like we have 14 April as our next oportunity to push this to production.

Due to the pre QT code freeze, this ticket cannot be released until after 27 April. At that stage we will need to assess when an apprioriate window will be for release, taking into account what, if any exercises are open for applications.

As of today, we only have 00064 open on production.
Tom has been asked to confirm whether releasing this on production would negatively impact that open exercise.

If this ticket is released while 00064 or any exercise with ASC is open will not see the changes implemented for apps in draft. This ticket needs to be released when no exercises are open or when no open exercises have ASC.
We will continue to code review and send to the UTG so that we can push the button when ready.


Improve error message when user forgets "properties"?

Is it possible to improve the error message if someone places a YAML attribute that should be under properties? (This idea occurred to me because the error message for specifying an invalid property name is so helpful and the onboarding was so gentle for me and because I made this mistake several times while writing my first Pulumi YAML programs.)
e.g.:
myBucket:
  type: aws:s3:bucket
  bucket: 'my-bucket-name'

Could result in some error message like:
Resource 'myBucket' has invalid key 'bucket'. Did you mean to put this key for the resource under 'properties', e.g.:

myBucket:
  # ...
  properties:
    bucket: 'my-bucket-name'

Let's make sure we identify common resource options to make sure we suggest that key correctly (e.g.: parent, provider), or inspect the schema to determine if it's even a valid property.


Kong 1.0.3 vs 1.2.1 Load Test CPU Utilization Benchmark Diff

Summary
I just ran a 120 TPS load-test against a proxy(service/route pair) running just a plain request termination plugin on-top of the route throwing {"message": "Success"} HTTP 200 on two different Kong versions
On 1.0.3 with a few modifications to src outlined here:
https://github.com/Kong/kong/issues/4769#issuecomment-513873111
I am seeing utilization hit .41 CPU utilized at a stable rate
On 1.2.1 I am seeing CPU utilization hit .53 CPU utilized at a stable rate(note I do run 1 mod on 1.2.1, outlined here):
https://github.com/Kong/kong/issues/4194#issuecomment-498001854
This is our sandbox env and no other active traffic would be hitting these environments. Both times I also had global plugins enabled like rate-limit,statsd,http log, correlation id as well.
I figured the 29.27% increase would be of interest to yall. Maybe a quick internal load-test Kong side could check for similar findings?
Steps To Reproduce

Run load test as prescribed above on the various Kong versions.

Additional Details & Logs

Kong version 1.0.3(with slight mods) and 1.2.1(1 modification from standard)
Leveraging C* as DB
Kong Alpine Docker

Kong 1.2.1 ENV Var Config:
- name: KONG_HEADERS
  value: latency_tokens
- name: KONG_PLUGINS
  value: >-
    kong-plugin-oauth,zipkin,kong-error-log,kong-oidc-implicit-token,kong-response-size-limiting,request-transformer,kong-service-virtualization,kong-cluster-drain,kong-upstream-jwt,kong-splunk-log,kong-spec-expose,kong-path-based-routing,kong-oidc-multi-idp,correlation-id,oauth2,statsd,jwt,rate-limiting,acl,request-size-limiting,request-termination,cors
- name: KONG_DNS_ORDER
  value: 'LAST,SRV,A,CNAME'
- name: KONG_CASSANDRA_CONTACT_POINTS
  value: 'server8171,server8176,server8180,server8173,server8175,server8172'
- name: KONG_LOG_LEVEL
  value: notice
- name: KONG_PROXY_ACCESS_LOG
  value: 'off'
- name: KONG_ADMIN_ACCESS_LOG
  value: 'off'
- name: KONG_PROXY_ERROR_LOG
  value: /dev/stderr
- name: KONG_ADMIN_ERROR_LOG
  value: /dev/stderr
- name: KONG_ANONYMOUS_REPORTS
  value: 'off'
- name: KONG_PROXY_LISTEN
  value: '<IP_ADDRESS>:8000, <IP_ADDRESS>:8443 ssl http2'
- name: KONG_ADMIN_LISTEN
  value: '<IP_ADDRESS>:8001'
- name: KONG_MEM_CACHE_SIZE
  value: 1024m
- name: KONG_SSL_CERT
  value: /usr/local/kong/ssl/kongcert.crt
- name: KONG_SSL_CERT_KEY
  value: /usr/local/kong/ssl/kongprivatekey.key
- name: KONG_SSL_CERT_DER
  value: /usr/local/kong/ssl/kongcertder.der
- name: KONG_CLIENT_SSL
  value: 'off'
- name: KONG_UPSTREAM_KEEPALIVE
  value: '60'
- name: KONG_TRUSTED_IPS
  value: '<IP_ADDRESS>/0,::/0'
- name: KONG_REAL_IP_HEADER
  value: X-Forwarded-For
- name: KONG_REAL_IP_RECURSIVE
  value: 'on'
- name: KONG_CLIENT_MAX_BODY_SIZE
  value: 100m
- name: KONG_CLIENT_BODY_BUFFER_SIZE
  value: 50m
- name: KONG_ERROR_DEFAULT_TYPE
  value: text/plain
- name: KONG_DATABASE
  value: cassandra
- name: KONG_PG_SSL
  value: 'off'
- name: KONG_CASSANDRA_PORT
  value: '9042'
- name: KONG_CASSANDRA_KEYSPACE
  value: kong_dev
- name: KONG_CASSANDRA_TIMEOUT
  value: '5000'
- name: KONG_CASSANDRA_SSL
  value: 'on'
- name: KONG_CASSANDRA_SSL_VERIFY
  value: 'on'
- name: KONG_CASSANDRA_USERNAME
  value: *****
- name: KONG_CASSANDRA_PASSWORD
  value: *****
- name: KONG_CASSANDRA_CONSISTENCY
  value: LOCAL_QUORUM
- name: KONG_CASSANDRA_LB_POLICY
  value: RequestDCAwareRoundRobin
- name: KONG_CASSANDRA_LOCAL_DATACENTER
  value: DC1
- name: KONG_DB_UPDATE_FREQUENCY
  value: '5'
- name: KONG_DB_UPDATE_PROPAGATION
  value: '5'
- name: KONG_DB_CACHE_TTL
  value: '0'
- name: KONG_DNS_HOSTSFILE
  value: /etc/hosts
- name: KONG_DNS_STALE_TTL
  value: '4'
- name: KONG_DNS_NOT_FOUND_TTL
  value: '30'
- name: KONG_DNS_ERROR_TTL
  value: '1'
- name: KONG_DNS_NO_SYNC
  value: 'off'
- name: KONG_LUA_SSL_TRUSTED_CERTIFICATE
  value: /usr/local/kong/ssl/kongcert.pem
- name: KONG_LUA_SSL_VERIFY_DEPTH
  value: '3'
- name: KONG_LUA_SOCKET_POOL_SIZE
  value: '30'
- name: KONG_ROUTER_CONSISTENCY
  value: eventual
- name: KONG_DB_CACHE_WARMUP_ENTITIES
  value: 'services,plugins,consumers'

Kong 1.0.3 ENV Config:
        - name: KONG_PLUGINS
          value: >-
            kong-plugin-oauth,zipkin,kong-error-log,kong-oidc-implicit-token,kong-response-size-limiting,request-transformer,kong-service-virtualization,kong-cluster-drain,kong-upstream-jwt,kong-splunk-log,kong-spec-expose,kong-path-based-routing,kong-oidc-multi-idp,correlation-id,oauth2,statsd,jwt,rate-limiting,acl,request-size-limiting,request-termination,cors
        - name: KONG_HEADERS
          value: latency_tokens
        - name: KONG_DNS_ORDER
          value: 'LAST,SRV,A,CNAME'
        - name: KONG_CASSANDRA_CONTACT_POINTS
          value: 'server8342,server8344,server8346,server8348,server8419,server8350'
        - name: KONG_LOG_LEVEL
          value: notice
        - name: KONG_PROXY_ACCESS_LOG
          value: 'off'
        - name: KONG_ADMIN_ACCESS_LOG
          value: 'off'
        - name: KONG_PROXY_ERROR_LOG
          value: /dev/stderr
        - name: KONG_ADMIN_ERROR_LOG
          value: /dev/stderr
        - name: KONG_ANONYMOUS_REPORTS
          value: 'off'
        - name: KONG_PROXY_LISTEN
          value: '<IP_ADDRESS>:8000, <IP_ADDRESS>:8443 ssl http2'
        - name: KONG_ADMIN_LISTEN
          value: '<IP_ADDRESS>:8001'
        - name: KONG_MEM_CACHE_SIZE
          value: 1024m
        - name: KONG_SSL_CERT
          value: /usr/local/kong/ssl/kongcert.crt
        - name: KONG_SSL_CERT_KEY
          value: /usr/local/kong/ssl/kongprivatekey.key
        - name: KONG_SSL_CERT_DER
          value: /usr/local/kong/ssl/kongcertder.der
        - name: KONG_CLIENT_SSL
          value: 'off'
        - name: KONG_UPSTREAM_KEEPALIVE
          value: '60'
        - name: KONG_CLIENT_MAX_BODY_SIZE
          value: 100m
        - name: KONG_CLIENT_BODY_BUFFER_SIZE
          value: 50m
        - name: KONG_ERROR_DEFAULT_TYPE
          value: text/plain
        - name: KONG_DATABASE
          value: cassandra
        - name: KONG_PG_SSL
          value: 'off'
        - name: KONG_CASSANDRA_PORT
          value: '9042'
        - name: KONG_CASSANDRA_KEYSPACE
          value: kong_stage
        - name: KONG_CASSANDRA_TIMEOUT
          value: '5000'
        - name: KONG_CASSANDRA_SSL
          value: 'on'
        - name: KONG_CASSANDRA_SSL_VERIFY
          value: 'on'
        - name: KONG_CASSANDRA_USERNAME
          value: *****
        - name: KONG_CASSANDRA_PASSWORD
          value: *****
        - name: KONG_CASSANDRA_CONSISTENCY
          value: LOCAL_QUORUM
        - name: KONG_CASSANDRA_LB_POLICY
          value: RequestDCAwareRoundRobin
        - name: KONG_CASSANDRA_LOCAL_DATACENTER
          value: DC1
        - name: KONG_DB_UPDATE_FREQUENCY
          value: '5'
        - name: KONG_DB_UPDATE_PROPAGATION
          value: '5'
        - name: KONG_DB_CACHE_TTL
          value: '0'
        - name: KONG_DNS_HOSTSFILE
          value: /etc/hosts
        - name: KONG_DNS_STALE_TTL
          value: '4'
        - name: KONG_DNS_NOT_FOUND_TTL
          value: '30'
        - name: KONG_DNS_ERROR_TTL
          value: '1'
        - name: KONG_DNS_NO_SYNC
          value: 'off'
        - name: KONG_LUA_SSL_TRUSTED_CERTIFICATE
          value: /usr/local/kong/ssl/kongcert.pem
        - name: KONG_LUA_SSL_VERIFY_DEPTH
          value: '3'
        - name: KONG_LUA_SOCKET_POOL_SIZE
          value: '30'
        - name: KONG_TRUSTED_IPS
          value: '<IP_ADDRESS>/0,::/0'
        - name: KONG_REAL_IP_HEADER
          value: X-Forwarded-For
        - name: KONG_REAL_IP_RECURSIVE
          value: 'on'

@jeremyjpj0916 since youre keeping a stable rate of requests in this benchmark, are you noticing any different in p9x latencies?

@p0pr0ck5 Will get back to you on p99 latencies, so far just looking at http plugin logs in my splunk:
1.2.1:  Avg: 1.9534540444794333  Min: 1  Max: 11 (What Kong reports internally)
1.0.3  Avg: 2.4038063307366135  Min: 1  Max: 16 (What Kong reports internally)
Based on that 1.2.1 looks to be faster, but client calling via soapUI load test gives a different result:
1.2.1 Avg client side latency:  56.76ms
1.0.3 Avg client side latency:  37.82ms
Granted my env that is on 1.0.3 is our Stage which actually has a different LB in front of it than Dev, and our 1.2.1 test is Dev environment.
Also gave wrk tool a run locally on the network(Im finally on a mac :D ) as well against Dev(1.2.1) vs Stage(1.0.3):
  ~  wrk -t 1 -c 1 -d 30 https://kong-dev-core-dc1.company.com/F5/status
Running 30s test @ https://kong-dev-core-dc1.company.com/F5/status
  1 threads and 1 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    54.94ms   25.81ms 250.43ms   93.84%
    Req/Sec    19.31      4.50    30.00     83.10%
  571 requests in 30.01s, 130.48KB read
Requests/sec:     19.03
Transfer/sec:      4.35KB

☁  ~  wrk -t 1 -c 1 -d 30 https://kong-stage-core-dc1.company.com/F5/status
Running 30s test @ https://kong-stage-core-dc1.company.com/F5/status
  1 threads and 1 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    34.44ms    1.32ms  49.89ms   94.23%
    Req/Sec    28.80      3.14    39.00     90.51%
  867 requests in 30.00s, 198.12KB read
Requests/sec:     28.90
Transfer/sec:      6.60KB

Seems the wrk client is on par with what soapUI got too as far as latencies.
We are going to upgrade Stage to the 1.2.1 today so I will retest and confirm these client latencies again in Stage once moved to 1.2.1(Personally I think the LB is not playing the role in these latency differences).

Actually better test to pull my laptop out of equation is run from a server within the DC, results were not vastly different in the avg latency department:
root@server00380:/home/me
# wrk -t 1 -c 1 -d 30 https://kong-stage-core-dc1.optum.com/F5/status
Running 30s test @ https://kong-stage-core-dc1.optum.com/F5/status
  1 threads and 1 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    20.71ms  102.60ms   1.01s    97.17%
    Req/Sec   221.12     24.29   242.00     96.91%
  6431 requests in 30.03s, 1.44MB read
Requests/sec:    214.16
Transfer/sec:     48.94KB

root@server00380:/home/me
# wrk -t 1 -c 1 -d 30 https://kong-dev-core-dc1.optum.com/F5/status
Running 30s test @ https://kong-dev-core-dc1.optum.com/F5/status
  1 threads and 1 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    25.77ms  100.16ms   1.01s    96.07%
    Req/Sec   178.44     53.41   222.00     89.08%
  5066 requests in 30.03s, 1.13MB read
Requests/sec:    168.71
Transfer/sec:     38.55KB

With our Stage environment upgraded to 1.2.1 as well I can confirm there too we went from the .41 CPU utilization rate to .525-.53 rate as well @ 120 tps. I will also test 1.2.1 without ANY of my modifications in sandbox and see if not having concurrency.lua modified reduces cpu utilization(my guess is that it won't). Could just be the 1.0.3 I was running with the Bungle mods just has some efficiency advantages in my case the OG 1.0.3 didn't have and 1.2.1 subsequently lack.
Would be nice to get that CPU back to the levels we saw though on 1.0.3 with those tweaks we been running for 4-5 months that have served well 😆. I may try to test 1.0.3 without the Bungle mods and see what CPU utilization looks like there too to get a better picture. If it was the mods then all hail sir bungle and the crazy perf benefits we were seeing 🤴, rip bungle homebrew 1.0.3 .

out of curiosity @luo985 and @wurenhai , if you get a chance can you test your resources on 1.0.3 under tps load(say 120+ tps) compared to 1.2.1 and see if you see the CPU utilization differing similar to my findings in the other issue? And not necessarily while adjusting resources(adding/removing/updating routes or plugins). Might help us all correlate this with your issue too.

Actually I am changing my view here. Just ran a bunch of better/more extensive tests in an environment I am a bit more confident in the data on(leveraged an unused Stage environment 😆 )
By literally taking that environment and deploying bare 1.0.3 vs 1.2.1 with none of the patch work we run I notice these levels of CPU differences:
Kong 1.2.1: .37-.38 CPU used @ 112 TPS
Kong 1.0.3: .345-.35 CPU used @ 115 TPS
So while the difference is ever so slight in an environment I am more confident on than the data collected in my first trial run when I raised the issue, it is not enough to warrant investigation over that amount of difference.
Closing this so focus can be diverted elsewhere, there are better issues to dig into 👍 .

@jeremyjpj0916 thanks for getting back to this and giving us an update!


dispatch-ify ALL THE MACROS!

This is a:

[x] bug fix PR with no breaking changes — please ensure the base branch is master
[ ] new functionality — please ensure the base branch is the latest dev/ branch
[ ] a breaking change — please ensure the base branch is the latest dev/ branch

Description & motivation
see #311
cc: @alittlesliceoftom
Checklist

[ ] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[ ] Redshift
[ ] Snowflake

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have added an entry to CHANGELOG.md

@jtcohen6 not sure what I've done here...
Encountered an error:
Compilation Error in test dbt_utils_equality_test_generate_series_ref_data_generate_series_ (models/sql/schema.yml)
  macro 'dbt_macro__test_equality' takes no keyword argument 'arg'

  > in macro test_equality (macros/schema_tests/equality.sql)
  > called by test dbt_utils_equality_test_generate_series_ref_data_generate_series_ (models/sql/schema.yml)

Removing myself as reviewer, as Jeremy has it covered :)

Removing myself as reviewer, as Jeremy has it covered :)

onto the next thing... I don't have a postgres target handy (but can get one running without too much trouble probably). @jtcohen6 any shoves in the right direction here? I haven't the slightest how the dispatch addition would make a test fail...
Failure in test dbt_utils_expression_is_true_data_test_expression_is_true_col_b_0_5__col_a_0_5 (models/schema_tests/schema.yml)
  Got 2 results, expected 0.

  compiled SQL at target/compiled/dbt_utils_integration_tests/models/schema_tests/schema.yml/schema_test/dbt_utils_expression_is_true_data_test_expression_is_true_col_b_0_5__col_a_0_5.sql

onto the next thing... I don't have a postgres target handy (but can get one running without too much trouble probably). @jtcohen6 any shoves in the right direction here? I haven't the slightest how the dispatch addition would make a test fail...
Failure in test dbt_utils_expression_is_true_data_test_expression_is_true_col_b_0_5__col_a_0_5 (models/schema_tests/schema.yml)
  Got 2 results, expected 0.

  compiled SQL at target/compiled/dbt_utils_integration_tests/models/schema_tests/schema.yml/schema_test/dbt_utils_expression_is_true_data_test_expression_is_true_col_b_0_5__col_a_0_5.sql

If my memory serves me correctly, we don't want to pass through the defaults twice. e.g. instead of:
{% macro test_expression_is_true(model, condition='true') %}
This conversation was marked as resolved by swanderz
  {{ return(adapter.dispatch('test_expression_is_true', packages = dbt_utils._get_utils_namespaces())(model, condition, **kwargs)) }}
{% endmacro %}

{% macro default__test_expression_is_true(model, condition='true') %}
...

We only want:
...
{% macro default__test_expression_is_true(model, condition) %}
...

I think this caused us issues in a Snowplow macro somwhere 🤔

If my memory serves me correctly, we don't want to pass through the defaults twice. e.g. instead of:
{% macro test_expression_is_true(model, condition='true') %}
This conversation was marked as resolved by swanderz
  {{ return(adapter.dispatch('test_expression_is_true', packages = dbt_utils._get_utils_namespaces())(model, condition, **kwargs)) }}
{% endmacro %}

{% macro default__test_expression_is_true(model, condition='true') %}
...

We only want:
...
{% macro default__test_expression_is_true(model, condition) %}
...

I think this caused us issues in a Snowplow macro somwhere 🤔

@clrcrl It really could be an issue! I was trying to remember earlier today.
The problem in #279 is that we passed the default args into a macro call—not explicitly an issue with repeating them across two macro signatures.

@clrcrl It really could be an issue! I was trying to remember earlier today.
The problem in #279 is that we passed the default args into a macro call—not explicitly an issue with repeating them across two macro signatures.

oh right, yes I see the difference now!

oh right, yes I see the difference now!

let this comment stand in for what should have been marking my draft PR as ready for review!

let this comment stand in for what should have been marking my draft PR as ready for review!

@jtcohen6 — I'm going to let you do the honors here (unless you'd prefer me to!)
0.6.4 seems imminent!

@jtcohen6 — I'm going to let you do the honors here (unless you'd prefer me to!)
0.6.4 seems imminent!


Bump the version number

Hello @dudeche, @mikesall,
Please review. Updating the version number.

lgtm


Issue with Item Sets Being Pulled

5.18 - Looks like item sets are being pulled down weird; everyone starts with a ward in their final build, then junglers have the first upgrade + full item listed separate. 6th item usually doesn't get past boots for any champion.

Looks like an issue on their end, seems they're having some odd aggregation issues. Joel is probably already on it!
http://champion.gg/champion/Nidalee
http://champion.gg/champion/Lux

Yeah looking into this at the moment - I think there have been some changes to riots api, as I haven't changed anything on my side, will be fixed up within the next day or two!


How to play next video on Button click?

I have an array of videos, called VIDEOS [ ] whose index I increment +1 when i click a button. The button fires a function nextVideo().
How do i get the player to play the next video?
So  <Video source={{uri: VIDEOS[videoCounter]}} /> needs to reload in my render() function in App.js with the updated counter called videoCounter.

You can set the uri from this.state.
Something like:
onPress = () => {
  this.setState({ videoCounter: this.state.videoCounter + 1 });
}

source={{ uri: VIDEOS[this.state.videoCounter] }}


Opera web browser is outdated

Hi,
Opera web browser is outdated. Thus it's vpn does not work. The vpn API has been changed on new years. I am reading from reddit: https://www.reddit.com/r/operabrowser/comments/bfk1ba/vpn_not_working_to_anyone_else/
I will be happy if someone will update it.
Thank you

There is PR #58735 but it needs some more work


Wunderground produces bad JSON data

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.57.2
Python release (python3 --version):
Python 3.5.3
Component/platform:
Wunderground
Description of problem:
Front-end periodically stalls and displays "Loading Data".  Logs show JSON errors at the time.
Expected:
Front-end able to handle bad JSON
Problem-relevant configuration.yaml entries and steps to reproduce:
sensor:
  platform: wunderground
  monitored_conditions:
    - weather_1h

Traceback (if applicable):
2017-11-07 18:57:15 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/remote.py", line 132, in default
    return json.JSONEncoder.default(self, o)
  File "/usr/lib/python3.5/json/encoder.py", line 179, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <function WUHourlyForecastSensorConfig.__init__.<locals>.<lambda> at 0x69ef5270> is not JSON serializable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/remote.py", line 138, in default
    for child_obj in o]
TypeError: 'function' object is not iterable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/aiohttp/web_protocol.py", line 422, in start
    resp = yield from self._request_handler(request)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/aiohttp/web.py", line 306, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.5/asyncio/coroutines.py", line 213, in coro
    res = yield from res
  File "/usr/lib/python3.5/asyncio/coroutines.py", line 213, in coro
    res = yield from res
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/components/http/__init__.py", line 423, in handle
    result = yield from result
  File "/usr/lib/python3.5/asyncio/coroutines.py", line 213, in coro
    res = yield from res
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/components/websocket_api.py", line 388, in handle
    yield from self._writer_task
  File "/usr/lib/python3.5/asyncio/futures.py", line 382, in __iter__
    return self.result()  # May raise too.
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/components/websocket_api.py", line 238, in _writer
    yield from self.wsock.send_json(message, dumps=JSON_DUMP)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/aiohttp/web_ws.py", line 188, in send_json
    return self.send_str(dumps(data))
  File "/usr/lib/python3.5/json/__init__.py", line 237, in dumps
    **kw).encode(obj)
  File "/usr/lib/python3.5/json/encoder.py", line 198, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
    return _iterencode(o, 0)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/homeassistant/remote.py", line 141, in default
    return json.JSONEncoder.default(self, o)
  File "/usr/lib/python3.5/json/encoder.py", line 179, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <function WUHourlyForecastSensorConfig.__init__.<locals>.<lambda> at 0x69ef5270> is not JSON serializable

Additional info:

Hi,
Wunderground has sometimes unstable JSON responses. Similar issue: #10387
Trying to address error handling in PR https://github.com/home-assistant/home-assistant/pull/10295


Add an "another?" button

It's sad to only be congratulated once per day, I should be able to ask for more by clicking a button.

It's there now


implement chillidkg

Implements the ideas from the bip-frost spec. This is a WIP. I think I like the new spec way better so I want to make proper errors for the error cases as well do documentation and renaming. Then delete the old key generation.
This deviates from the spec in several ways that I won't bother to list but they are mostly superficial things that I'll either fix or make an issue about.

This is ready for review now.

implemented (my loose interpretation) of chilldkg
Remove all of our existing keygen stuff
Also fca38b59348be0c6085beeb715a7827e18f71374


Change Grunt Dependencies, r=borjasalguero

So that Grunt continues working with FxOS master

LGTM. Merging!


updated goal list (Includes spelling fixes free of charge)

We might revert to have rom again but yeah thanks


I would like to add icons inside tag

Description
When tags are used as a status indicator and the text do not say anything abour the status. It would need something more than color to indicate states. Icons would be a good way to enhance this in our tags.
Example:

Additional Information
Example from Aksel

This is already supported in code :)


testlink-0.4.3: bump bitnami/testlink image to version 1.9.15-r6

Thanks @dbarranco, closing in favour of #493.


Investigate CI jobs timing

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
With a slowing growing CI running times we might want to look into what's taking how long and whether there are any small wins that we could capture.
Would be good to understand better how long what part of job takes, what are the options to reduce duration (if any), if we could maybe skip CI jobs when they are obviously not required (i.e. change of readme file or something similar that would not benefit in any way from testing or building)
Examples 🌈
No response
Motivation 🔦
No response

With a slowing growing CI running times

Not that there could be no value in improving CI timings, but the data suggests differently. There has been a peak, but CI times are at a similar level to July. I'm not 100% sure what happened around beginning of september, I don't remember builds taking one hour. I do remember there to be a few circleci outages with delayed jobs, perhaps related?

IMO, once CI passes the two minute mark, you can't really use it in a synchronous way anymore. From that point on, if I want to increase efficiency, I'll have to find ways to asynchronously work around CI. e.g.

Pick up a new task, similar to how I'd deal with waiting for reviews, doing more work in parallel. Treat CI as just another team member that reviews your code.
If a piece of work has a part with high risk of breaking an integration test and a part with low risk, I do the high risk first, push it and work on the low risk part until CI has finished. Any red integration tests? Now I know what to single out locally and can continue working on the high risk part again.

That being said, it looks like the CI job taking most of the time is the docker one. And within that workflow, the docker build. I'm not sure there's any quick wins there, besides beefing up the machine. IMO, if we're going to start optimizing the docker build, I believe we should rather optimize for image size and not for build time as improving image size has direct user value.
Besides decreasing the monthly circleci bill. I personally don't feel like I would gain much from improving CI time with say 5 minutes (and neither would I lose much from it increasing 5 minutes).
As for render.com, after analyzing the build logs, I see it basically divided equally between dependency installation and next.js build (about 7, 8 minutes each). I find this rather on the long end for both of them and I wonder about caching. render.com does some build caching, but doesn't allow us the set custom cache folders (please upvote 🙂). The logs also suggest Next.js doesn't have its build cached. I don't see at the many opportunities for improvement.

That sounds fair enough 👍
I'm just wondering if it would be worth to use GH action which could conditionally run certain jobs, i.e. if we change something that does not require build - skip build job, etc...?

Dug a bit further and it looks like we can build caching ourselves in render.com. Trying that out in https://github.com/mui/mui-toolpad/pull/1166

I'm just wondering if it would be worth to use GH action which could conditionally run certain jobs, i.e. if we change something that does not require build - skip build job, etc...?

Maybe, only thing I could think of could perhaps be not building the docker image on PRs that only contain changes in the ./docs folder. (We don't need GH actions for this, circleci should be able to do this as well)

Maybe, only thing I could think of could perhaps be not building the docker image on PRs that only contain changes in the ./docs folder. (We don't need GH actions for this, circleci should be able to do this as well)

That could be a start 🤔 we could also try to see if we are able to identify some other PR "types" that would not require CI run, I mean just a general observation over few weeks and then discuss with team whether it useful to run jobs for picked PRs or not 🤔

I believe we should look into turborepo to help us with that.

+1 for turborepo, if there are no changes in certain packages it would just use its cache so building would be instant.
It may even help with build times when we make changes while developing - not sure if we're caching those right now.


Logistic Regression

Bayesian logistic regression is a useful model used in many applications. We might want to consider adding the example from
https://github.com/TuringLang/Turing.jl/issues/546
to tutorials.

I agree, this was already proposed in issue #3 and I think @cpfiffer is working on it.

That's correct, I'm still doing the write-up for this one. It should hopefully be along shortly.

Merged over with #17. Does anyone have any comments on it before I close this issue?

I'm happy, the tutorial in #17 is really nice.


File name too long. Ubuntu

I'm writing longish research prompts in order to guide the model to get what I want. At what I believe is the end of the job, when it's trying to save the output to a markdown file, i get an error that the filename is too long. Filesystem is ext4. Here is the error output. Don't mind my silly question :)
Error in converting Markdown to DOCX: [Errno 36] File name too long: "outputs/task_1715125933_Figure out what parts I need to build the following: a computer with an intel i9 with at least 12 cores, a case that supports 20 3.5 hard drives, a motherboard that has at lease 2 nvme ssd slots and 2.5gbe, enough room for an nvidia 1080 video card in both the case and the motherboard. at least 2 8x pcie slots in addition to the slots used by the video card. preferably ipmi but thats not a requirment. server grade hardware is ok, but i don't have a rack so it would sit on a desk...docx"
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 240, in run_asgi
    result = await self.app(self.scope, self.asgi_receive, self.asgi_send)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 69, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/middleware/errors.py", line 151, in __call__
    await self.app(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/routing.py", line 756, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/routing.py", line 776, in app
    await route.handle(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/routing.py", line 373, in handle
    await self.app(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/routing.py", line 96, in app
    await wrap_app_handling_exceptions(app, session)(scope, receive, send)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/starlette/routing.py", line 94, in app
    await func(session)
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/fastapi/routing.py", line 348, in app
    await dependant.call(**values)
  File "/home/joey/Downloads/gpt-researcher/backend/server.py", line 58, in websocket_endpoint
    md_path = await write_text_to_md(report, filename)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/joey/Downloads/gpt-researcher/backend/utils.py", line 32, in write_text_to_md
    await write_to_file(file_path, text)
  File "/home/joey/Downloads/gpt-researcher/backend/utils.py", line 19, in write_to_file
    async with aiofiles.open(filename, "w", encoding='utf-8') as file:
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/aiofiles/base.py", line 98, in __aenter__
    self._obj = await self._coro
                ^^^^^^^^^^^^^^^^
  File "/home/joey/Downloads/gpt-researcher/venv/lib/python3.11/site-packages/aiofiles/threadpool/__init__.py", line 94, in _open
    f = yield from loop.run_in_executor(executor, cb)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/joey/.pyenv/versions/3.11.9/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 36] File name too long: "outputs/task_1715125933_Figure out what parts I need to build the following: a computer with an intel i9 with at least 12 cores, a case that supports 20 3.5 hard drives, a motherboard that has at lease 2 nvme ssd slots and 2.5gbe, enough room for an nvidia 1080 video card in both the case and the motherboard. at least 2 8x pcie slots in addition to the slots used by the video card. preferably ipmi but thats not a requirment. server grade hardware is ok, but i don't have a rack so it would sit on a desk...md"
INFO:     connection closed

as a work around, i changed this:
https://github.com/assafelovic/gpt-researcher/blob/66c37425af17aa7f519470642e67e18570b206c1/backend/server.py#L50
to this:
filename = f"task_{int(time.time())}_{task[:50]}"

Thanks @joeysantana3 . Just fixed in latest commit: https://github.com/assafelovic/gpt-researcher/commit/836fea9b763814b36c075b11fa21f0d7f2d0a1b8
Pull the latest and should work


integrate sign in / session flow with nano ledger

waiting for firmware developement.

check it out ya'll!
https://github.com/cosmos/ledger-cosmos

Blocked on missing cross compilation ability of the ledger code in the SDK.
Closing in favor of #1338


should clean_call have internal error checking and file existence checks and execution?

@1054 right now these are external, but I could see that we would prefer the internal logic to be ... internal? to clean_call.

Closing.


[SE-2725] Updating deprecated GitHub commands for build-push-image

SE-2725
Description
Updating deprecated GitHub commands for build-push-image

set-output
actions/checkout version

How to test

Tested using this commit as reference on this PR, fixed all warnings on our workflow.

Development checks

[ ] Add changeset according to guidelines (if needed)

PR commands

List of available commands:

@toptal-anvil ping reviewers - Ping FX team for review

@toptal-anvil ping reviewers

@toptal/fx-codeowners could tell me if some information is missing to get this merged? I'd appreciate 😄

Hello, @lorainegarutti ! Thanks for contributing to davinci products!
You should generate a changeset, to properly conduct a release.
You can run yarn changeset locally to define a type of change: major, minor or patch.
For me, it seems to be patch change.

Hello, @lorainegarutti ! Thanks for contributing to davinci products! You should generate a changeset, to properly conduct a release. You can run yarn changeset locally to define a type of change: major, minor or patch. For me, it seems to be patch change.

@dmaklygin Thank you for the fast response! I already added as you suggested


processing block invalid character

Received this error when trying to scrape the blocks:
time="2021-04-13T20:30:00Z" level=error msg="[scraper] Error decoding invalid host specified\n: invalid character 'i' looking for beginning of value" block=1

additional logs:

time="2021-04-14T02:42:23Z" level=error msg="[scraper] Error decoding invalid host specified\n: invalid character 'i' looking for beginning of value" block=5
time="2021-04-14T02:42:25Z" level=info msg="[core] processing block" block=6
time="2021-04-14T02:42:25Z" level=debug msg="[scraper] getting block" block=6
time="2021-04-14T02:42:25Z" level=debug msg="Making http request with 1 RPCs\n"
time="2021-04-14T02:42:25Z" level=error msg="[scraper] Error decoding invalid host specified\n: invalid character 'i' looking for beginning of value" block=6
time="2021-04-14T02:42:27Z" level=info msg="[core] processing block" block=5
time="2021-04-14T02:42:27Z" level=debug msg="[scraper] getting block" block=5
time="2021-04-14T02:42:27Z" level=debug msg="Making http request with 1 RPCs\n"
time="2021-04-14T02:42:27Z" level=error msg="[scraper] Error decoding invalid host specified\n: invalid character 'i' looking for beginning of value" block=5
time="2021-04-14T02:42:29Z" level=info msg="[core] processing block" block=6
time="2021-04-14T02:42:29Z" level=debug msg="[scraper] getting block" block=6
time="2021-04-14T02:42:29Z" level=debug msg="Making http request with 1 RPCs\n"
time="2021-04-14T02:42:29Z" level=error msg="[scraper] Error decoding invalid host specified\n: invalid character 'i' looking for beginning of value" block=6
time="2021-04-14T02:42:31Z" level=info msg="[core] processing block" block=5
time="2021-04-14T02:42:31Z" level=debug msg="[scraper] getting block" block=5
time="2021-04-14T02:42:31Z" level=debug msg="Making http request with 1 RPCs\n"

Add --http.vhosts "*" --http.corsdomain "*" to the geth command. 🥇


[BUG] - Potential non-deterministic failures in fastjson1-compatible module

问题描述
I am a masters student from University of Illinois-Urbana Champaign and as part of my research project, I test open-source repositories to detect and address flaky tests. For carrying out this process, I use a tool called NonDex.
I have been assigned the fastjson2 repository for my research project. Earlier, students from the same university have addressed some flaky tests in fastjson1.
I have begun testing the various modules under fastjson2 for detecting potential flaky tests. I am sharing the initial round of results based on the fastjson1-compatible.
Please let me know if I can proceed with developing fixes for the detected flaky tests.
环境信息
请填写以下信息：

OS信息：  [MacOS Sonoma 8GB]
JDK信息： [JAVA 11.0.21-amzn]
版本信息：[2.0.42]

重现步骤
如何操作可以重现该问题：

Run mvn -pl fastjson1-compatible edu.illinois:nondex-maven-plugin:2.1.1:nondex -DnondexMode=ONE to identify potential flaky tests in the fastjson1-compatible module.
This execution will run all tests in fastjson1-compatible module by shuflling the order of non-deterministic elements.
The section Across all seeds  in the logs displays the list of flaky tests detected in the execution.

期待的正确结果
Most of the flaky tests detected in the fastjson1-compatible module seem to be arising from the non-deterministic nature in which certain JAVA data storage types tend to store data. If we can change the data storage types to ones which keep the order definite and don't shuffle elements when its accessed, we can make those tests more resilient to non-deterministic failures.
相关日志输出
The list of tests identified by NonDex as potential flaky tests are as follows:
[INFO] All tests pass without NonDex shuffling
[INFO] ####################
[INFO] Across all seeds:
[INFO] com.alibaba.fastjson.issue_2400.Issue2447#test_for_issue2
[INFO] com.alibaba.fastjson.issue_2400.Issue2447#test_for_issue
[INFO] com.alibaba.fastjson.issue_2100.Issue2182#test_for_issue
[INFO] com.alibaba.fastjson.issue_2400.Issue2428#test_for_issue
[INFO] com.alibaba.fastjson.issue_1900.Issue1972#test_for_issue
[INFO] com.alibaba.fastjson.issue_1300.Issue1363#test_for_issue
[INFO] com.alibaba.fastjson.issue_1300.Issue1363#test_for_issue_1
[INFO] com.alibaba.fastjson.issue_1100.Issue1177_1#test_for_issue
[INFO] com.alibaba.fastjson.issue_1100.Issue1177_2#test_for_issue
[INFO] com.alibaba.fastjson.geo.FeatureCollectionTest#test_geo
[INFO] com.alibaba.fastjson.jsonp.JSONPParseTest1#test_f
[INFO] com.alibaba.fastjson.jsonp.JSONPParseTest#test_f

附加信息
Based on how the developers want to take this forward, I can run nondex for other fastjson2 modules and create separate issues to track flaky tests reported in different modules individually.
Your inputs on whether I can proceed with creating PRs for the identified issues will be of great help towards strengthening my research project.

Welcome to participate in the test of fastjson2. I will try my best to respond to your PR in a timely manner. Generally, it will be processed within 2 to 3 days, not more than 1 week.


module 'elastic' has no attribute 'Elastic'

HI, I tried to run the tutorial, but it sounds that the module 'elastic' has no attribute 'Elastic'.
Any idea?
Thanks

Same here.
After facing this particular issue i tried to search for  Elastic in the elastic directory and did not found the attribute


update vllm patch to v0.2.6

currently, outlines.serve only works with vllm-v0.2.5, this PR updates it to vllm-v0.2.6. I'm testing this currently, will update if I run into problems

not great so far:
/usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py:474: NumbaPendingDeprecationWarning:
Encountered the use of a type that is scheduled for deprecation: type 'reflected set' found for argument 'fsm_finals' of function '_walk_fsm'.

For more information visit https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-reflection-for-list-and-set-types

File "../usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py", line 226:
@numba.njit(nogil=True, cache=True)
def _walk_fsm(
^

  state_seq = _walk_fsm(
/usr/local/lib/python3.10/dist-packages/numba/core/ir_utils.py:2172: NumbaPendingDeprecationWarning:
Encountered the use of a type that is scheduled for deprecation: type 'reflected set' found for argument 'fsm_finals' of function 'state_scan_tokens'.

For more information visit https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-reflection-for-list-and-set-types

File "../usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py", line 462:
@numba.njit(cache=True, nogil=True)
def state_scan_tokens(
^

  warnings.warn(NumbaPendingDeprecationWarning(msg, loc=loc))
INFO 12-24 15:45:08 async_llm_engine.py:379] Received request 891d2ad827604ec28c56f22d882ae045: prompt: 'What is the capital of France?', sampling params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=1.0, top_p=1.0, top_k=-1, min_p=0.0, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=[], stop_token_ids=[], include_stop_str_in_output=False, ignore_eos=False, max_tokens=16, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True), prompt token ids: None.
Exception in callback functools.partial(<function _raise_exception_on_finish at 0x7fe7969551b0>, request_tracker=<vllm.engine.async_llm_engine.RequestTracker object at 0x7fe786667520>)
handle: <Handle functools.partial(<function _raise_exception_on_finish at 0x7fe7969551b0>, request_tracker=<vllm.engine.async_llm_engine.RequestTracker object at 0x7fe786667520>)>
Traceback (most recent call last):
  File "/workspace/vllm/engine/async_llm_engine.py", line 28, in _raise_exception_on_finish
    task.result()
  File "/usr/lib/python3.10/asyncio/futures.py", line 201, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 234, in __step
    result = coro.throw(exc)
  File "/workspace/vllm/engine/async_llm_engine.py", line 359, in run_engine_loop
    has_requests_in_progress = await self.engine_step()
  File "/workspace/vllm/engine/async_llm_engine.py", line 338, in engine_step
    request_outputs = await self.engine.step_async()
  File "/workspace/vllm/engine/async_llm_engine.py", line 191, in step_async
    output = await self._run_workers_async(
  File "/workspace/vllm/engine/async_llm_engine.py", line 219, in _run_workers_async
    all_outputs = await asyncio.gather(*coros)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 304, in __wakeup
    future.result()
  File "/usr/lib/python3.10/asyncio/tasks.py", line 234, in __step
    result = coro.throw(exc)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 650, in _wrap_awaitable
    return (yield from awaitable.__await__())
INFO 12-24 15:45:08 async_llm_engine.py:134] Aborted request 891d2ad827604ec28c56f22d882ae045.
  File "/usr/lib/python3.10/asyncio/futures.py", line 285, in __await__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.10/asyncio/tasks.py", line 304, in __wakeup
    future.result()
  File "/usr/lib/python3.10/asyncio/futures.py", line 201, in result
    raise self._exception.with_traceback(self._exception_tb)
ray.exceptions.RayTaskError(RaySystemError): ray::RayWorkerVllm.execute_method() (pid=762, ip=<IP_ADDRESS>, actor_id=81008059c117df77dfd1d76001000000, repr=<vllm.engine.ray_utils.RayWorkerVllm object at 0x7fb61c7604f0>)
  At least one of the input arguments for this task could not be computed:
ray.exceptions.RaySystemError: System error: Can't patch loop of type <class 'uvloop.Loop'>
traceback: Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/outlines/__init__.py", line 3, in <module>
INFO:     <IP_ADDRESS>:40022 - "POST /generate HTTP/1.1" 500 Internal Server Error
    import outlines.models
  File "/usr/local/lib/python3.10/dist-packages/outlines/models/__init__.py", line 12, in <module>
    from .openai import OpenAI, openai
  File "/usr/local/lib/python3.10/dist-packages/outlines/models/openai.py", line 11, in <module>
    from outlines.base import vectorize
  File "/usr/local/lib/python3.10/dist-packages/outlines/base.py", line 16, in <module>
    nest_asyncio.apply()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 19, in apply
    loop = loop or asyncio.get_event_loop()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 41, in _get_event_loop
    loop = events.get_event_loop_policy().get_event_loop()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 68, in get_event_loop
    _patch_loop(loop)
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 184, in _patch_loop
    raise ValueError('Can\'t patch loop of type %s' % type(loop))
ValueError: Can't patch loop of type <class 'uvloop.Loop'>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 63, in uvloop.loop.Handle._run
  File "/workspace/vllm/engine/async_llm_engine.py", line 37, in _raise_exception_on_finish
    raise exc
  File "/workspace/vllm/engine/async_llm_engine.py", line 32, in _raise_exception_on_finish
    raise AsyncEngineDeadError(
vllm.engine.async_llm_engine.AsyncEngineDeadError: Task finished unexpectedly. This should never happen! Please open an issue on Github. See stack trace above for the actual cause.
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/workspace/vllm/engine/async_llm_engine.py", line 28, in _raise_exception_on_finish
    task.result()
  File "/usr/lib/python3.10/asyncio/futures.py", line 201, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 234, in __step
    result = coro.throw(exc)
  File "/workspace/vllm/engine/async_llm_engine.py", line 359, in run_engine_loop
    has_requests_in_progress = await self.engine_step()
  File "/workspace/vllm/engine/async_llm_engine.py", line 338, in engine_step
    request_outputs = await self.engine.step_async()
  File "/workspace/vllm/engine/async_llm_engine.py", line 191, in step_async
    output = await self._run_workers_async(
  File "/workspace/vllm/engine/async_llm_engine.py", line 219, in _run_workers_async
    all_outputs = await asyncio.gather(*coros)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 304, in __wakeup
    future.result()
  File "/usr/lib/python3.10/asyncio/tasks.py", line 234, in __step
    result = coro.throw(exc)
  File "/usr/lib/python3.10/asyncio/tasks.py", line 650, in _wrap_awaitable
    return (yield from awaitable.__await__())
  File "/usr/lib/python3.10/asyncio/futures.py", line 285, in __await__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.10/asyncio/tasks.py", line 304, in __wakeup
    future.result()
  File "/usr/lib/python3.10/asyncio/futures.py", line 201, in result
    raise self._exception.with_traceback(self._exception_tb)
ray.exceptions.RayTaskError(RaySystemError): ray::RayWorkerVllm.execute_method() (pid=762, ip=<IP_ADDRESS>, actor_id=81008059c117df77dfd1d76001000000, repr=<vllm.engine.ray_utils.RayWorkerVllm object at 0x7fb61c7604f0>)
  At least one of the input arguments for this task could not be computed:
ray.exceptions.RaySystemError: System error: Can't patch loop of type <class 'uvloop.Loop'>
traceback: Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/outlines/__init__.py", line 3, in <module>
    import outlines.models
  File "/usr/local/lib/python3.10/dist-packages/outlines/models/__init__.py", line 12, in <module>
    from .openai import OpenAI, openai
  File "/usr/local/lib/python3.10/dist-packages/outlines/models/openai.py", line 11, in <module>
    from outlines.base import vectorize
  File "/usr/local/lib/python3.10/dist-packages/outlines/base.py", line 16, in <module>
    nest_asyncio.apply()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 19, in apply
    loop = loop or asyncio.get_event_loop()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 41, in _get_event_loop
    loop = events.get_event_loop_policy().get_event_loop()
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 68, in get_event_loop
    _patch_loop(loop)
  File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 184, in _patch_loop
    raise ValueError('Can\'t patch loop of type %s' % type(loop))
ValueError: Can't patch loop of type <class 'uvloop.Loop'>

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 426, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/usr/local/lib/python3.10/dist-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 1106, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/usr/local/lib/python3.10/dist-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/lib/python3.10/dist-packages/fastapi/middleware/asyncexitstack.py", line 20, in __call__
    raise e
  File "/usr/local/lib/python3.10/dist-packages/fastapi/middleware/asyncexitstack.py", line 17, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.10/dist-packages/starlette/routing.py", line 66, in app
    response = await func(request)
  File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 274, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 191, in run_endpoint_function
    return await dependant.call(**values)
  File "/usr/local/lib/python3.10/dist-packages/outlines/serve/serve.py", line 84, in generate
    async for request_output in results_generator:
  File "/workspace/vllm/engine/async_llm_engine.py", line 445, in generate
    raise e
  File "/workspace/vllm/engine/async_llm_engine.py", line 439, in generate
    async for request_output in stream:
  File "/workspace/vllm/engine/async_llm_engine.py", line 70, in __anext__
    raise result
  File "uvloop/cbhandles.pyx", line 63, in uvloop.loop.Handle._run
  File "/workspace/vllm/engine/async_llm_engine.py", line 37, in _raise_exception_on_finish
    raise exc
  File "/workspace/vllm/engine/async_llm_engine.py", line 32, in _raise_exception_on_finish
    raise AsyncEngineDeadError(
vllm.engine.async_llm_engine.AsyncEngineDeadError: Task finished unexpectedly. This should never happen! Please open an issue on Github. See stack trace above for the actual cause.
(RayWorkerVllm pid=762) Can't patch loop of type <class 'uvloop.Loop'>
(RayWorkerVllm pid=762) Traceback (most recent call last):
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/ray/_private/serialization.py", line 404, in deserialize_objects
(RayWorkerVllm pid=762)     obj = self._deserialize_object(data, metadata, object_ref)
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/ray/_private/serialization.py", line 270, in _deserialize_object
(RayWorkerVllm pid=762)     return self._deserialize_msgpack_data(data, metadata_fields)
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/ray/_private/serialization.py", line 225, in _deserialize_msgpack_data
(RayWorkerVllm pid=762)     python_objects = self._deserialize_pickle5_data(pickle5_data)
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/ray/_private/serialization.py", line 215, in _deserialize_pickle5_data
(RayWorkerVllm pid=762)     obj = pickle.loads(in_band)
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/outlines/__init__.py", line 3, in <module>
(RayWorkerVllm pid=762)     import outlines.models
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/outlines/models/__init__.py", line 12, in <module>
(RayWorkerVllm pid=762)     from .openai import OpenAI, openai
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/outlines/models/openai.py", line 11, in <module>
(RayWorkerVllm pid=762)     from outlines.base import vectorize
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/outlines/base.py", line 16, in <module>
(RayWorkerVllm pid=762)     nest_asyncio.apply()
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 19, in apply
(RayWorkerVllm pid=762)     loop = loop or asyncio.get_event_loop()
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 41, in _get_event_loop
(RayWorkerVllm pid=762)     loop = events.get_event_loop_policy().get_event_loop()
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 68, in get_event_loop
(RayWorkerVllm pid=762)     _patch_loop(loop)
(RayWorkerVllm pid=762)   File "/usr/local/lib/python3.10/dist-packages/nest_asyncio.py", line 184, in _patch_loop
(RayWorkerVllm pid=762)     raise ValueError('Can\'t patch loop of type %s' % type(loop))
(RayWorkerVllm pid=762) ValueError: Can't patch loop of type <class 'uvloop.Loop'>
(RayWorkerVllm pid=762) [W CUDAGraph.cpp:145] Warning: Waiting for pending NCCL work to finish before starting graph capture. (function operator())

some success:
INFO 12-24 21:56:26 llm_engine.py:73] Initializing an LLM engine with config: model='/mnt/llmd/base_models/Mistral-7B-Instruct-v0.2', tokenizer='/mnt/llmd/base_models/Mistral-7B-Instruct-v0.2', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=32768, download_dir=None, load_format=auto, tensor_parallel_size=1, quantization=None, enforce_eager=False, seed=0)
INFO 12-24 21:57:40 llm_engine.py:223] # GPU blocks: 25213, # CPU blocks: 2048
INFO 12-24 21:57:42 model_runner.py:394] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
INFO 12-24 21:57:48 model_runner.py:437] Graph capturing finished in 6 secs.
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8000 (Press CTRL+C to quit)
/usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py:474: NumbaPendingDeprecationWarning:
Encountered the use of a type that is scheduled for deprecation: type 'reflected set' found for argument 'fsm_finals' of function '_walk_fsm'.

For more information visit https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-reflection-for-list-and-set-types

File "../usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py", line 226:
@numba.njit(nogil=True, cache=True)
def _walk_fsm(
^

  state_seq = _walk_fsm(
/usr/local/lib/python3.10/dist-packages/numba/core/ir_utils.py:2172: NumbaPendingDeprecationWarning:
Encountered the use of a type that is scheduled for deprecation: type 'reflected set' found for argument 'fsm_finals' of function 'state_scan_tokens'.

For more information visit https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-reflection-for-list-and-set-types

File "../usr/local/lib/python3.10/dist-packages/outlines/fsm/regex.py", line 462:
@numba.njit(cache=True, nogil=True)
def state_scan_tokens(
^

  warnings.warn(NumbaPendingDeprecationWarning(msg, loc=loc))
INFO 12-24 21:58:38 async_llm_engine.py:379] Received request c96271e42d38463b91549220e3c26e81: prompt: 'What is the capital of France?', sampling params: SamplingParams(n=1, best_of=1, presence_penalty=0.0, frequency_penalty=0.0, repetition_penalty=1.0, temperature=1.0, top_p=1.0, top_k=-1, min_p=0.0, use_beam_search=False, length_penalty=1.0, early_stopping=False, stop=[], stop_token_ids=[], include_stop_str_in_output=False, ignore_eos=False, max_tokens=16, logprobs=None, prompt_logprobs=None, skip_special_tokens=True, spaces_between_special_tokens=True), prompt token ids: None.
INFO 12-24 21:58:38 llm_engine.py:653] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 1 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%
INFO 12-24 21:58:38 async_llm_engine.py:111] Finished request c96271e42d38463b91549220e3c26e81.
INFO:     <IP_ADDRESS>:40684 - "POST /generate HTTP/1.1" 200 OK

At least it doesn't crash anymore.

everything works

@rlouf thanks for the review! I made some changes based on your feedback

Great contribution, thank you!


Copy constructor from clientOptions is inclompleted

The copy constructor only take care of cloning the per retry and per call policies but it is not initializing the other options based on the copied reference

fixed by https://github.com/Azure/azure-sdk-for-cpp/pull/1788


doc: The magnetometer values are in nT not mG

commit be8451e723c0021e53d7eb7160ed534bd1abe1a1 introduced the scaling
factor of 150 from the microbit codal by lancaster university. This
factor is however explicitly mentioned to be a conversion factor to SI
units here:
https://github.com/lancaster-university/microbit-dal/blob/master/inc/drivers/LSM303Magnetometer.h#L36
With Tesla being the SI unit for magnetic field strength and the
documentatoin of the dal also declaring the output values as being
nanoteslas it is likely that this means this converts the magnetometer
raw data to nanoteslas (This is also the only way the values im
measuring with my lsm303agr are explainable).

😬 sorry if I wasted a lot of your time @hargoniX. I really struggled with figuring out what the 150 was all about when I looked.


What would you say about mobile web apps using websites?

If you were forcing all users to convert to responsive layouts, whats happening for people who use mobile web apps like 'Duda mobile sites' for their mobile users? Why can't you put some notes/google fundamentals for people to follow guidance for mobile app using websites/etc..????

I don't really want people using transpilers for this, I would rather teach people the fundamentals about how to build great mobile and desktop sites.


In testing，I downloaded the eval data，but can't find the test dataset I need about DTU.

Hi @liubowen1233 , thank you for pointing out. It seems that I packed the test data into training data link.  I just update README and include a new link for the test data only. Hope this helps.


test: --- FAIL: TestCtlV2RoleList

--- FAIL: TestCtlV2RoleList (1.03s)
	etcdctl_test.go:219: failed to add role (read /dev/ptmx: input/output error)

Ack. Will take a look.

Similar error from  https://semaphoreci.com/coreos/etcd/branches/pull-request-4992/builds/5
--- FAIL: TestCtlV2UserList (1.03s)
	ctl_v2_test.go:201: failed to add user (read /dev/ptmx: input/output error (expected User username created, got ["client: etcd cluster is unavailable or misconfigured\r\n"]))

Just got reproduced with more log:
--- FAIL: TestCtlV2RoleList (1.03s)
	ctl_v2_test.go:219: failed to add role (read /dev/ptmx: input/output error (expected "foo", got ["client: etcd cluster is unavailable or misconfigured\r\n"]))

https://semaphoreci.com/coreos/etcd/branches/pull-request-4976/builds/8

Fixed via https://github.com/coreos/etcd/pull/4999.


Allow CiviForm admins to see a published program / question's configuration

Presently, we only show this information for draft programs / questions. Surfacing a read-only view will allow admins to more easily see what has changed between the published content and the draft content.

This issue refers to Phase 2 of this Mini prd
I discussed some open questions with Cassandra and will pick this up next.
Some personal notes are here


Android Gatt AutoConnect is always set to true

The PlatformInit for Android, force the connection to autoconnect = true, this parameter is not always correct,
in my case I will control the disconnection and reconnection.
private void PlatformInit()
{
_gattCallback = new GattCallback(this);
_gatt = ((ABluetooth.BluetoothDevice)Device).ConnectGatt(Android.App.Application.Context, true, _gattCallback, ABluetooth.BluetoothTransports.Le);
}

Thanks, good catch. Going forward I think the required behaviour is to set this false and allow the consumer of the library to manage reconnection, using events to detect a disconnection.

I have pulled a request for a change.
Thanks

Pull request #160 merged.


fix: Panicked when OceanBase table client is initialing

Which issue does this PR close?
Closes #
Rationale for this change
related with https://github.com/oceanbase/obkv-table-client-rs/pull/21
Table client will init timeout when one OB server is invalid, eg, OUT_OF_MEM, SERVER_IS_INIT.
What changes are included in this PR?
Update OceanBase rust client
Are there any user-facing changes?

How does this change test
Integration test

Codecov Report

Merging #728 (ac3a1e7) into main (8837aa6) will decrease coverage by 0.01%.
The diff coverage is n/a.

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

@@            Coverage Diff             @@
##             main     #728      +/-   ##
==========================================
- Coverage   68.26%   68.25%   -0.01%
==========================================
  Files         288      288
  Lines       45335    45335
==========================================
- Hits        30946    30944       -2
- Misses      14389    14391       +2

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


update min sdk version

@morganchen12 Is this a new requirement from the firestore sdk?
I still see 19 as the minSdk on the source code:
https://github.com/firebase/firebase-android-sdk/blob/ad22aebec96b744643a6f6011c6cb2657517bea6/firebase-firestore/firebase-firestore.gradle#L61

Ah, I guess not. I'll close this PR.