Flag routes with paginated responses that have a result namespace

Ref https://github.com/octokit/rest.js/issues/1161
Affected routes

[ ] https://developer.github.com/v3/search/#example (key items)
[ ] https://developer.github.com/v3/checks/runs/#list-check-runs-for-a-specific-ref (key: check_runs)
[ ] https://developer.github.com/v3/checks/runs/#list-check-runs-in-a-check-suite (key: check_runs)
[ ] https://developer.github.com/v3/checks/suites/#list-check-suites-for-a-specific-ref (key: check_suites)
[ ] https://developer.github.com/v3/apps/installations/#list-repositories (key: repositories)
[ ] https://developer.github.com/v3/apps/installations/#list-repositories-accessible-to-the-user-for-an-installation (key: repositories)
[ ] https://developer.github.com/v3/actions/artifacts/#list-workflow-run-artifacts (key: artifacts)
[ ] https://developer.github.com/v3/actions/secrets/#list-secrets-for-a-repository (key: secrets)
[ ] https://developer.github.com/v3/actions/workflows/#list-repository-workflows (key: workflows)
[ ] https://developer.github.com/v3/actions/workflow_jobs/#list-jobs-for-a-workflow-run (key: workflow_jobs)
[ ] https://developer.github.com/v3/actions/workflow_runs/#list-workflow-runs (key: workflow_runs)
[ ] https://developer.github.com/v3/actions/workflow_runs/#list-repository-workflow-runs (key: workflow_runs)

Make sure to not accidentally include, it’s not a response which paginates

[ ] https://developer.github.com/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref

Example
Search repositories.
Instead of just responding with "items" in the response body root, the response body has 3 keys: total_count, incomplete_result and items.
{
  "total_count": 40,
  "incomplete_results": false,
  "items": [
    {
      "id": 3081286,
      "node_id": "MDEwOlJlcG9zaXRvcnkzMDgxMjg2",
      "name": "Tetris",
      "full_name": "dtrupenn/Tetris",
      "owner": {
        "login": "dtrupenn",
        "id": 872147,
        "node_id": "MDQ6VXNlcjg3MjE0Nw==",
        "avatar_url": "https://secure.gravatar.com/avatar/e7956084e75f239de85d3a31bc172ace?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-user-420.png",
        "gravatar_id": "",
        "url": "https://api.github.com/users/dtrupenn",
        "received_events_url": "https://api.github.com/users/dtrupenn/received_events",
        "type": "User"
      },
      "private": false,
      "html_url": "https://github.com/dtrupenn/Tetris",
      "description": "A C implementation of Tetris using Pennsim through LC4",
      "fork": false,
      "url": "https://api.github.com/repos/dtrupenn/Tetris",
      "created_at": "2012-01-01T00:31:50Z",
      "updated_at": "2013-01-05T17:58:47Z",
      "pushed_at": "2012-01-01T00:37:02Z",
      "homepage": "",
      "size": 524,
      "stargazers_count": 1,
      "watchers_count": 1,
      "language": "Assembly",
      "forks_count": 0,
      "open_issues_count": 0,
      "master_branch": "master",
      "default_branch": "master",
      "score": 10.309712
    }
  ]
}

I think I would set x-github.paginates to either true or the name of the property that holds the array


createMachine fails to infer typestate for particular state

Description

given this code

type YesNoContext = { value?: number };

type YesNoEvent = { type: 'YES' };

type NoLiteralContext = { value: 'no'; context: { value: undefined } };
type YesLiteralContext = { value: 'yes'; context: { value: number } };

type YesNoTypestate =
  | NoLiteralContext
  | YesLiteralContext;

const expectYesLiteralContext = (ctx: YesLiteralContext) => ctx;
const expectNoLiteralContext = (ctx: NoLiteralContext) => ctx;

const yesNoMachine = createMachine<
  YesNoContext,
  YesNoEvent,
  YesNoTypestate
>({
  context: {
    value: undefined
  },
  initial: 'no',
  states: {
    no: {
      on: {
        YES: 'yes'
      },
      entry: expectNoLiteralContext,
    },
    yes: {
      type: 'final',
      entry: expectYesLiteralContext,
    }
  }
});

Expected Result

assertion is not satisfied since context within entry is inferred as YesNoContext

Actual Result

Within state, it should be inferred as one of literal contexts, see assertion functions
Reproduction

CodeSandbox template (JavaScript)
CodeSandbox template (TypeScript)
⚛ CodeSandbox template (React)
⚛ CodeSandbox template (React + TypeScript)
💚 CodeSandbox template (Vue + Composition API)
XState Visualizer

please take a look on this snippet in CodeSandbox: https://codesandbox.io/s/beautiful-cartwright-02oiw?file=/src/index.ts
Additional context

Latest XState version by the moment
XState version: 4.8.0
TypeScript version: 3.8.3

May be, there is some way to get this working?
I'd like to utilize TypeSchema as well
may be, there is some generic with 4 parameters? e.g. MachineDefinition<TContext, TSchema, TEvent, TTypestate>? That would be enough for me, to use it in somewhat like following snippet:
type YesNoContext = { value?: number };

type YesNoEvent = { type: 'YES' };

type NoLiteralContext = { value: 'no'; context: { value: undefined } };
type YesLiteralContext = { value: 'yes'; context: { value: number } };

type YesNoTypestate =
  | NoLiteralContext
  | YesLiteralContext;

const expectYesLiteralContext = (ctx: YesLiteralContext) => ctx;
const expectNoLiteralContext = (ctx: YesLiteralContext) => ctx;

type YesNoSchema = {
    states: {
        yes: {},
        no: {},
    },
};

const states: MachineDefinition<YesNoContext, YesNoSchema, YesNoEvent, YesNoTypestate> = {
    no: {
      on: {
        YES: 'yes'
      },
      entry: expectYesLiteralContext,
    },
    yes: {
      type: 'final',
      entry: expectNoLiteralContext,
    }
  };

const yesNoMachine = createMachine<
  YesNoContext,
  YesNoEvent,
  YesNoTypestate
>({
  context: {
    value: undefined
  },
  initial: 'no',
  states,
});

may be related but I'm not sure https://github.com/davidkpiano/xstate/issues/1120

The Typestate feature is for state.matches(...), and not yet for within the state machine. That's something we're going to work on for V5.

Thank you for your answer!
So, there is no temporary workaround for this?

Ah yes, it seems that main point is here:
export declare type StatesConfig<TContext, TStateSchema extends StateSchema, TEvent extends EventObject> = {
    [K in keyof TStateSchema['states']]: StateNodeConfig<TContext /* <--- here! */, TStateSchema['states'][K], TEvent>;
};

I would accept a PR if you really want this feature.

Sure but please advise me on some steps to get started, because I'm not familiar with codebase. It's StatesConfig right?

This use case should be supported by the Typestate because it is an intuition.
I feel very strange why the context is not following the Typestate under a specific state and trying to figure out why until I find this thread and read the answer from @davidkpiano.
Really looking forward to upgrading with the v5 alpha/RC/beta/next because there are lots of exciting improvements.

Typestates were removed in v5. We know that this is a highly requested feature but to introduce it back we need to do it in a type-safe way and that's very challenging


listStakePools - Include metadata in API responses

Relates to #1065.
Overview

Modified Api.Server.listPools and StakePoolLayer listStakePools to include metadata.
Made it possible to use an environment variable for the registry url.
Handles the case where different stake pool owners register different metadata by logging and then ignoring all inconsistent data.

Comments

This is a draft.

bors try

bors r+


Startup shell script fails with >1 line in AWS config

When using quickstart.sh or startup.sh using default AWS region, the scripts fail when more than one properly line is present in ~/.aws/config - for example, I set my output format to 'table', which added a new config like to 'config'. The sed command "eval $(grep -v '^[' ~/.aws/config | sed 's/^(region)\s?=\s?/export AWS_DEFAULT_REGION=/')" does not properly filter for only the line beginning with region, but rather returns all lines in the file. Script fails with the following error "./quickstart.sh: line 84: export: `=': not a valid identifier".
Unfortunately, simply hardcoding the region with '-r' does not prevent this error, as the config files appears to be parsed regardless of the input value.
Removing the format config line from the files resolves this issue.

./quickstart.sh line 84
./startup.sh line 118


Git secret server pass as url

Pass GIT_SECRET_SERVER as is so that the git credential store can be created with the correct scheme.
Depends on https://github.com/jenkins-x/jx-helpers/pull/132

Hi @cameronbraid. Thanks for your PR.
I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign garethjevans
You can assign the PR to them by writing /assign @garethjevans in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/ok-to-test
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jstrachan
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jstrachan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cameronbraid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
1b55635ad9497dadb042be9a8c59e956b8763b9f
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@cameronbraid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
1b55635ad9497dadb042be9a8c59e956b8763b9f
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest


cmake: enable more stm32 builds in ci

Summary
cmake: enable more stm32 builds in ci
Impact
Testing
ci

mac CI failure not related to this PR - stm32 configs passed

Yes, macOS ci isn't stable in last few days, let's ignore it.


Ensure that unicode characters are valid

Fixes #104

I've tested it locally using: stack test --test-arguments=--seed=1971057639 --resolver nightly-2018-10-04 --fast, but it passes.

LGTM.  Only problem is it might end up producing empty values, as evinced by the travis failure.
Is it feasible to use something like https://hackage.haskell.org/package/QuickCheck-<IP_ADDRESS>/docs/Test-QuickCheck-Modifiers.html#t:UnicodeString? Or otherwise make arbitrary construct valid strings rather than filter invalid elements?

I wonder if
UTF8.fromString <$> listOf1 arbitraryUnicodeChar -- or arbitraryPrintableChar

would work

arbitraryUnicode will fail, because it includes these invalid chars. The printable should work fine thought.

Vexingly, there are still edge cases: https://travis-ci.org/vimus/libmpd-haskell/jobs/453998056
My only other suggestion is
listOf1 (arbitrary `suchThat` isValid)

where isValid is the previous version you proposed.  Surely that must work, given that the predicate is suitably constraining?

Sorry, that should be not . isValid, of course.

The worst thing is that it works fine locally even with that seed. I'll add better logging

I agree that the set of stack resolvers can be constrained. Even limiting to default and nightly (the latter as permitted failure) might suffice. (I use nixpkgs for everything so I've really no idea what range of resolvers make sense, I'm happy to defer to your judgement).


Callback-based rerouting

This series of changes introduces the reroute method on Middleman::Sitemap::Store, which allows for registering callbacks that can mutate the destination path of a page. Given that, I rewrote how the builder and process_request work to take advantage of these new callbacks and some new properties on Middleman::Sitemap::Page (as well as trying to pass Pages around more instead of just paths). You can see how much this simplifies the directory_indexes extension, and I'm hoping this can be the basis for a clean implementation of issue #174 and middleman/middleman-blog#15.

Awesome.


Discussion: handling comparison of intervals

Is your feature request related to a problem or challenge?
Data of type DateTime::Interval  (spans of time measured in calendar units like days and months)  are tricky business because the absolute size (in number of seconds) is not a fixed quantity. For example the 1 month is 28 days for February but 1 month is 31 days in December.
This makes the seemingly simple operation of comparing two intervals quite complicated in practice. For example is 1 month more or less than 30 days? The answer depends on what month you are talking about.
Arrow also includes a type DateTime::Duration that is a fixed width of time and suffers from many fewer challenges, but may not be as intuitive for humans to use;
Currently DataFusion \ errors with "not supported" when trying to compare an interval. This is

good as it doesn't get inconsistent answers
bad as it might imply it is a feature gap to be filled rather than an intentional lack (which seems to have happened in https://github.com/apache/arrow-rs/pull/5180)

For example you can't compare an interval of 1 month and 100 days:
❯ select interval '1 month' = interval '100 days';
This feature is not implemented: Unsupported interval operator: Eq
❯ select interval '1 month' < interval '100 days';;
This feature is not implemented: Unsupported interval operator: Lt

Nor can you compute things like min/max on an interval
❯ create table foo(i interval) as values (interval '1 month'), (interval '100 days');
0 rows in set. Query took 0.008 seconds.

❯ select max(i) from foo;
Internal error: Min/Max accumulator not implemented for type Interval(MonthDayNano).
This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker
❯ select min(i) from foo;
Internal error: Min/Max accumulator not implemented for type Interval(MonthDayNano).

(those should probably be unsupported errors rather than internal errors 🤔 )
 select interval '100 days';
+---------------------------------------------------------+
| IntervalMonthDayNano("1844674407370955161600")          |
+---------------------------------------------------------+
| 0 years 0 mons 100 days 0 hours 0 mins 0.000000000 secs |
+---------------------------------------------------------+
1 row in set. Query took 0.000 seconds.

❯ select interval '1 month';
+-------------------------------------------------------+
| IntervalMonthDayNano("79228162514264337593543950336") |
+-------------------------------------------------------+
| 0 years 1 mons 0 days 0 hours 0 mins 0.000000000 secs |
+-------------------------------------------------------+
1 row in set. Query took 0.001 seconds.

Describe the solution you'd like
It would be nice to discuss and determine what behavior we would like. Saying "datafusion will not support this kind of comparison" would be fine as an outcome, for the reasons  explained above
Describe alternatives you've considered
We could also adopt what postgres does which is to simply convert months into 30 days and treat them as a fixed quantity
postgres=# select interval '1 month' < interval '100 days';
 ?column?
----------
 t
(1 row)

postgres=# select interval '1 month' < interval '31 days';
 ?column?
----------
 t
(1 row)

postgres=# select interval '1 month' < interval '30 days';
 ?column?
----------
 f
(1 row)

Additional context
I made https://github.com/apache/arrow-rs/pull/5192 to try and clarify the semantics in arrow

We could also adopt what postgres does which is to simply convert months into 30 days and treat them as a fixed quantity

Coercing to a duration is an interesting option, although this would inherently be lossy and so could also be confusing...
Perhaps we could have a middle-ground where we add syntactic sugar to make coercing to a duration easy, and then direct users to this? e.g. something like '1 month'::duration_nanos or something... :thinking:

We fixed this in our fork with the semantics discussed in the linked arrow-rs issue. Happy to contribute it upstream if there is interest in it, just let us know.


Discussions

Curious why the Discussions was removed.  Any chance of bring that back, there was some good stuff in there.

Hi @stahler. I was hoping to combine discussions with issues to have one place for all the info. I meant to move the discussions over, but didn't get a chance yet. Unfortunately, there is no read only option for discussions.  For now, I've reopened discussions.

Great!  Appreciate your module immensely!


Poppy Integration Testing - payments feed

Josh/Shelley with Suzette

Suzette tested on 2/23, no issues found. Done.


Gateway missing translations.json

Version:
js-ipfs version: 0.40.0-
Repo version: 7
System version: x64/linux
Node.js version: v11.15.0
Platform: Linux  4.15.0-72-generic #81-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
Subsystem: webui

Type: Bug
Severity: Very Low
Description:
Gateway dashboard UI cannot be translated to other than English. Translation snippets appear to be requested but missing.
Steps to reproduce the error:

Run ipfs daemon service
Open in the browser the Gateway->settings
http://<IP_ADDRESS>:9090/ipfs/Qmexhq2sBHnXQbvyP2GfUdbnY7HCagH2Mw5vUNSBn2nxip/#/settings
In Language section click on "Change" and select for example "Spanish"
Dashboard is partially translation (probably due to missing i18n snippets)
On browser network tab you can see a 500 http error fetching
http://<IP_ADDRESS>:9090/ipfs/Qmexhq2sBHnXQbvyP2GfUdbnY7HCagH2Mw5vUNSBn2nxip/locales/es/translation.json
The fact that translation.json is missing does not affect the actual partial internationalization of the UI

Screenshot

Note to self: we don't use that file, but:

i18next per default loads it translations from one file named translation.json
https://www.i18next.com/principles/fallback

Changing the default namespace to app (defaultNS: 'app' in init) might remove unnecessary request.


While building the model  it's showing sum error?

I'm using it in google colab..
Thanks in Advance.
CODE:
%cd src/lib/models/networks/DCNv2
!./make.sh
ERROR:
/content/PPDM/src/lib/models/networks/DCNv2
Traceback (most recent call last):
File "build.py", line 3, in
from torch.utils.ffi import create_extension
File "/usr/local/lib/python3.6/dist-packages/torch/utils/ffi/init.py", line 1, in
raise ImportError("torch.utils.ffi is deprecated. Please use cpp extensions instead.")
ImportError: torch.utils.ffi is deprecated. Please use cpp extensions instead.
Traceback (most recent call last):
File "build_double.py", line 3, in
from torch.utils.ffi import create_extension
File "/usr/local/lib/python3.6/dist-packages/torch/utils/ffi/init.py", line 1, in
raise ImportError("torch.utils.ffi is deprecated. Please use cpp extensions instead.")
ImportError: torch.utils.ffi is deprecated. Please use cpp extensions instead.

This error may be caused by using the high-version pytorch. https://github.com/xingyizhou/CenterNet/issues/559

which version of Pytorch i should use?

Pytorch 0.4.1

Thanks.. it's working..!


Add dockerfile, docker-compose and Docker section to readme

Let's not merge this one I have another one comming.


Fixed bug in reverse complement assembly detection

Tests pass. Looks pretty good. Again, not super familiar with this code :)


Server crashing on join

Hello,
I am using Pex 2.0 Bukkit.
Getting this crash report when joining:
https://paste.timocraft.at/avayugajim.css
Help please!!!

Thanks for doing something, @Stormbow . But it is really urgent. It worked before, but suddenly it works nowhere! I used a MySQL backup - nothing changed.

Update: Does not work in any way. Using a fresh installed spigot.jar, newest version from jenkins, also self-built version. Always crashing when interacting with backend.
#ShowStopper

Since PEX 2.x has not been officially released, the only person who can tell you anything about it is zml.

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.


[Monitor Query] Typing updates

Regenerated with latest autorest and updated some samples.

API change check
API changes are not detected in this pull request.


double nullifier tree height

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

circuit_simulation_time_in_ms (private-kernel-init): 46.1 (-48%)
circuit_simulation_time_in_ms (private-kernel-ordering): 23.5 (-57%)
circuit_simulation_time_in_ms (base-rollup): 878 (-61%)
circuit_simulation_time_in_ms (root-rollup): 37.5 (-62%)
circuit_simulation_time_in_ms (private-kernel-inner): 41.5 (-35%)
node_history_sync_time_in_ms (5): 11,750 (-59%)
node_history_sync_time_in_ms (10): 22,528 (-60%)
note_history_successful_decrypting_time_in_ms (5): 2,338 (-69%)
note_history_successful_decrypting_time_in_ms (10): 4,783 (-68%)
l2_block_building_time_in_ms (8): 9,102 (-42%)
l2_block_building_time_in_ms (32): 36,442 (-41%)
l2_block_building_time_in_ms (128): 160,471 (-36%)
l2_block_rollup_simulation_time_in_ms (8): 6,773 (-48%)
l2_block_rollup_simulation_time_in_ms (32): 27,105 (-48%)
l2_block_rollup_simulation_time_in_ms (128): 108,379 (-48%)
l2_block_public_tx_process_time_in_ms (128): 51,433 (+27%)
l2_block_processing_time_in_ms (8): 1,053 (-54%)
l2_block_processing_time_in_ms (32): 3,920 (-55%)
l2_block_processing_time_in_ms (128): 15,331 (-55%)
note_successful_decrypting_time_in_ms (8): 331 (-53%)
note_successful_decrypting_time_in_ms (32): 1,018 (-59%)
note_successful_decrypting_time_in_ms (128): 3,934 (-59%)
note_trial_decrypting_time_in_ms (8): 34.0 (+580%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 6c4e26cf and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,876
868,184
3,449,408

l1_rollup_execution_gas
841,963
3,595,292
22,204,777

l2_block_processing_time_in_ms
:warning: 1,053 (-54%)
:warning: 3,920 (-55%)
:warning: 15,331 (-55%)

note_successful_decrypting_time_in_ms
:warning: 331 (-53%)
:warning: 1,018 (-59%)
:warning: 3,934 (-59%)

note_trial_decrypting_time_in_ms
:warning: 34.0 (+580%)
108
137 (+1%)

l2_block_building_time_in_ms
:warning: 9,102 (-42%)
:warning: 36,442 (-41%)
:warning: 160,471 (-36%)

l2_block_rollup_simulation_time_in_ms
:warning: 6,773 (-48%)
:warning: 27,105 (-48%)
:warning: 108,379 (-48%)

l2_block_public_tx_process_time_in_ms
2,286 (-9%)
9,216 (-8%)
:warning: 51,433 (+27%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
:warning: 11,750 (-59%)
:warning: 22,528 (-60%)

note_history_successful_decrypting_time_in_ms
:warning: 2,338 (-69%)
:warning: 4,783 (-68%)

note_history_trial_decrypting_time_in_ms
122 (-3%)
150 (-3%)

node_database_size_in_bytes
1,634,589
1,104,912 (+1%)

pxe_database_size_in_bytes
27,188
54,187

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
:warning: 46.1 (-48%)
61,697
18,841

private-kernel-ordering
:warning: 23.5 (-57%)
24,233
8,089

base-rollup
:warning: 878 (-61%)
705,845 (+10%)
811

root-rollup
:warning: 37.5 (-62%)
4,072
1,097

private-kernel-inner
:warning: 41.5 (-35%)
81,504
18,841

public-kernel-private-input
47.4 (-6%)
41,455
18,841

public-kernel-non-first-iteration
30.5 (-3%)
41,497
18,841

merge-rollup
0.833 (-14%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,723
27,510 (-6%)


🔧 toast style change

Text feels a bit small now
PR Type

[x] Bugfix

Context

[x] related with https://github.com/kodadot/nft-gallery/issues/4341#issuecomment-1322318855

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Screenshot 📸
light

dark

I was thinking if we would position it bit lower so it doesn't overlap with searchbar?

I was thinking if we would position it bit lower so it doesn't overlap with searchbar?

Where?

Updated!

yes probably works!
I guess we will redesign whole notification system anyway.
So probably we then keep all this at one place for simplicity of user interactions :)


test: Re-enable few test suites missed as part of recent migration

Please refer to individual commit for more details.
Thanks to @marseel and @giorio94 to highlight this.

/ci-integration

/test


Determine gate infrastructure

With the current implementation of gates, gates are simply functions which do not require any internal structure. However, it may be beneficial to change this to a class representation for a few reasons:

With classes, we could simulate the CMOS layout of each gate and simulate the actual ternary gate operations
With classes, we could probably add to a global counter with each instantiation to count the total number of gates used
We could also assign to each gate a number of tris or 3-muxes needed per gate so that we could count the total number of features used per chip

However, there are downsides. This would be a lot slower with a much large overhead, and we would need to greatly increase the amount of logic surrounding the wordMap functions. Clearly more thinking is required to decide on an infrastructure.

As a note, whatever we do with the gates should also be done for the muxes, since those are currently implemented as functions which simply select from and pass through one out of an array of input IOBus.data arrays. If the gates are kept as simple functions, then the muxes can be also to match them, but if the gates are converted to some kind of object with a more hardware specific implementation, so too should be the muxes.

As a note, whatever we do with the gates should also be done for the muxes, since those are currently implemented as functions which simply select from and pass through one out of an array of input IOBus.data arrays. If the gates are kept as simple functions, then the muxes can be also to match them, but if the gates are converted to some kind of object with a more hardware specific implementation, so too should be the muxes.

And to add onto this, a class based definition for the muxes would allow for some kind of type checking enforcement to ensure that every mux gets data arrays passed into them to choose between and not any other kind of object to standardize the mux usage and enforce the intended architecture of the system.

I've begun to think that we should use CNTFET over MOSFET given that it is a rising technology which would make ternary more feasible. With this in mind, let's brand away from CMOS as a building block, and resolve this issue by building a representation of our gates using CNTFET. The exact infrastructure in software is yet to be determined, but we can follow the actual gate circuits given here

I've begun to think that we should use CNTFET over MOSFET given that it is a rising technology which would make ternary more feasible. With this in mind, let's brand away from CMOS as a building block, and resolve this issue by building a representation of our gates using CNTFET. The exact infrastructure in software is yet to be determined, but we can follow the actual gate circuits given here

A first pass at providing infrastructure on this sort of approach is on the branch hardware

Moving the implementation of the CNTFET structure down the road. For right now, I want to focus on extending the functionality of the simulator so that I can study the algorithmic effectiveness and syntactic niceties of the ternary system first. CNTFET can be added on the backend at a later date. Want to get more functionality setup and rolling before I return to class in the Fall.

Closing due to scoping of the project; Would rather focus on the software pipes and development of a web app to showcase the functional ALU.


Bump to 5.9.1-SNAPSHOT

Summary of the changes / Why this improves CrateDB
Checklist

[x] Added an entry in the latest docs/appendices/release-notes/<x.y.0>.rst for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in the latest docs/appendices/release-notes/<x.y.0>.rst
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Shoudln't we update pom files like in https://github.com/crate/crate/pull/16335?

Thanks @BaurzhanSakhariev


Cannot do custom resolver string on macOS GUI

Hello all!
I have an apple M1 2020 macbook air. I have used Warp, and I have other VPNs installed but they were all disabled and completely shut down as I was installing controld. For some reason, when I use the custom resolver string no-ads-drugs-gambling-typo-malware-dating in the GUI mac installer, it does not allow me to submit this. I discovered that the reason it was erroring "Invalid Resolver ID" is that there was a character limit in the resolver ID field. I think that this isn't supposed to happen? PFA a video:
https://github.com/Control-D-Inc/ctrld/assets/68437385/e7fd98a5-d749-416a-bafe-90839a054544
The resolver id p3 works so I think it is just custom ones over a certain length. I tried using the terminal and I actually got it to work. Just a GUI fix :)

This is not a ctrld issue, as there is no problem if you do this in ctrld itself.
The GUI wrapper is at fault here, which is outside the scope of this issue tracker. This will be fixed.


How to Create a custom function in jQuery when click in buttons in Adaptive card  ?

i try to create a function when i click in buttons in adaptive card -----> hide the card but isn't working
when i do it in any different buttons outside the card is working
why can't create a function of buttons inside the adaptive cards?

hi @mohd3wamleh - can you please provide a code sample and additional information about the issue you're facing?

`    public static Attachment CreateAdaptiveCard()
{
AdaptiveCard card = new AdaptiveCard();
        string imgName = @"logo.png";
        string currentDirectory = System.IO.Directory.GetCurrentDirectory();
        string[] fullFilePath = System.IO.Directory.GetFiles(currentDirectory, imgName, SearchOption.AllDirectories);

        //https://ash-chatbot-5npgsta.azurewebsites.net/wwwroot/ChatBotAssets/img/logo.png

        var uri = new System.Uri(currentDirectory + "\\" + imgName);
        var converted = uri.AbsoluteUri;

        // Body content
        card.Body.Add(new AdaptiveImage()
        {
            //http://paisbot.eastasia.cloudapp.azure.com/UploadedImages/alsayer-logo.png
            //https://brandloungeme.com/wp-content/uploads/2017/07/logo-Al-Sayer.png
            //https://brandloungeme.com/wp-content/uploads/2017/07/logo-Al-Sayer.png
            Url = new System.Uri(/*fullFilePath.FirstOrDefault()*//*"https://www.jobawy.com/wp-content/uploads/2019/05/1880559_logo_1554268728_n.png"*/"https://chat.alsayergroup.com/alsayer-logo.png")
            ,
            Size = AdaptiveImageSize.Stretch,
        });

        card.Actions.AddRange(new List<AdaptiveSubmitAction>()
        {
            new AdaptiveSubmitAction()
             {
                 Title = TextResource.LocationAndTiming,
                 Data = TextResource.LocationAndTiming
             },
            new AdaptiveSubmitAction()
             {
                 Title = TextResource.SalesPromotion,
                 Data = TextResource.SalesPromotion
             },
            new AdaptiveSubmitAction()
            {
                 Title = TextResource.VehicleService,
                 Data = TextResource.VehicleService
             },
        });

        card.Actions.AddRange(new List<AdaptiveSubmitAction>()
        {
            new AdaptiveSubmitAction()
             {
                 Title = TextResource.VehicleDelivery,
                 Data = TextResource.VehicleDelivery
             },
            new AdaptiveSubmitAction()
             {
                 Title = TextResource.ContactUs,
                 Data = TextResource.ContactUs
             }
        });

        // Create the attachment with adapative card.
        Attachment attachment = new Attachment()
        {
            ContentType = AdaptiveCard.ContentType,
            Content = JsonConvert.DeserializeObject(JsonConvert.SerializeObject(card))
        };
        return attachment;
    }`

this code for the card from bot to frontend .
requirements : this card i want to hide when i click in any button in this card
issue: when i write a function in jQuery the code doesn't have any response
$(".ac-pushButton").bind("click",function(){
$( ".webchat__row.attachment" ).last().css( "display", "none" );
})
when i create this function in any other button is working fine but dose not work when i create in buttons inside the adaptive card
and thank you so much

@dclaux - does the nodejs renderer support jQuery handlers or should @mohd3wamleh use the built-in mechanism to handle the action clicks?

To handle an action button in an Adaptive Card, you need to implement an onExecuteAction handler. Please refer to the documentation: https://docs.microsoft.com/en-us/adaptive-cards/sdk/rendering-cards/javascript/actions

Thanks David! The solution is to use the built-in handlers; we do not support using jQuery handlers out-of-box.


Include changes from latest CR

Closes #233

The build is green, so all CR problems are now fixed.


testcase for DEL command

This PR aims to improve test coverage by adding test cases for DEL command
Issue: https://github.com/DiceDB/dice/issues/73

@JyotinderSingh @AshwinKul28 please review this PR. TIA!


nodejs-15_x: 15.0.1 -> 15.1.0

Motivation for this change
https://github.com/nodejs/node/releases/tag/v15.1.0
Things done

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

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

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

Result of nixpkgs-review pr 102852 run on x86_64-darwin 1

1 package failed to build:

lumo

2 packages built:

nodejs-15_x (nodejs_latest)
nodejs-slim-15_x (nodejs-slim_latest)


Add support for component interface dependencies to build system

Split interfaces into separate header files
Add a mechanism for including any interface in any component (similar to the way modules resolve their dependencies)

I know this is rather old, but I'm not sure how to review this. Maybe you could help me anwsering some questions below. (Not sure answering/solving this has priority now, but at least this documents current status)
-"Split interfaces into separate header files": does that mean that all individual interfaces should be defined in a separate file? (I think some granularity is good, to minimize additional dependencies). Currently there is an interface file per Module (group of components) that lists all interfaces used within that group, but this was already the case before this issue. Not sure what has been addressed here.
-"Add a mechanism for ...": How (and where) exactly is the case handled that some Components in a Module (group of components) wants to use one interface that is defined in another Module?
I found https://github.com/SuperElastix/SuperElastix/blob/develop/CMake/selxModules.cmake#L133-L135
Does this mean that all Components have access to all Interfaces found by the glob anyways? That means there is no actual depency check. What about header only Components (which are practically all of them)? Do we need a dependency check at all, since it will be one build unit anyways?


Update/Added talk after the split

Addition of my talk after the split of the videos/were in one file (Trent McConaghy - Blockchains for Artificial Intelligence & Radovan Kavicky - Data Science & Data Visualization in Python. How to harness power of Python for social good?)

Thanks for both contributions!
If you want to add more data (tags, related urls, ...) to the talk, feel free to add other PR or an issue.
Any contribution will be more than welcome (issues pointing new conference video lists, corrections, improvements, ...).

Thank you @Daniel-at-github ! (will add soon also all the videos from our PyData Bratislava meetups: https://www.youtube.com/watch?v=XYpKpmapqjI&list=PLISV6olKXnd9pE-KPtPgwwLe6qPXvb9K7)
As for conference (we will have our first PyData Bratislava in 2019/will add them too)


Remove duplicated restart definition

Duplicating the definition was causing errors:
docker compose up -d
parsing docker-labs/file-inclusion/college_website/docker-compose.yml: yaml: unmarshal errors:
  line 9: mapping key "restart" already defined at line 6

Good catch, thanks for this!


Component - Chocolate box (3 column)

This component  provides a visual grouping of related content e.g. examples of use-cases or benefits
Figma frame, see 'off chain' and 'on chain' Governance sections for the structure.
More details

@isaacpearl (I'm late with the notes on this I apoligize)
Chocolate boxes are simple components, especially since we don't have to be concerned with managing their individual heights.
This component is a case where we must go against the rules of it's design to ensure it can be scripted flexibly in MDX. What I mean is, while the designs provided Chocolate Box's in examples of 3x2 It should support an infinite amount of containers.
NOTE: I would recommend using Grid styles for this since they have specific sizes.
1 Container

Max Width 245px
Align Left

2 Containers

Max Width 245px each
Align Center / Space Around

3 Containers

Max Width 245px each
Align Center / Space Around (by this point it should fill up the width of it's parent container)

4 Containers

Max Width 245px each
Align Center

5 - Infinity
Rinse and Repeat 3 Container styles

Acceptance criteria will be (very similar to Column Comparise):

I should be able to script this component in MDX with as little friction to remember as possible. This means that each child that MDX sees should be the equivalent of 1 Chocolate Box. (See my List/Process components for examples of this)

NOTE: Mind the gaps. MDX is picky about line breaks (similarly to MD) on how it recognizes individual children. Notice the line break at the start and end of the component and in-between children.
<Chocolate>

   Choco Box 1

   - Choco Box 2

   - Choco Box 3

   1. Choco Box 4

    ### Choco Box 5

    <Box>
      Choco Box 6
    </Box>

</Chocolate>

A more realistic example would be:

<Chocolate>

<Box>

<Icon name="stocks" size={3}/>

Measuure community sentiment about issues affecting the MakerDAO ecosystem.

[See example ➡](https://example.com)

</Box>

<Box>

<Icon name="scale" size={3}/>

Determine the consensus that something needs to be done in response to a perceived issue.

[See example ➡](https://example.com)

</Box>

</Chocolate>

No margin top for this component when it comes to spacing around other components. But the individual components do have a margin bottom.

Height differences. From the spec, height differences can be ignored as the tallest will automatically push down the next row.

Closed by #65


Wallet: Improve Custom Onboarding Flow

After talking with Chris, we decided the following changes should be made:

Disable the continue buttons instead of hiding them on Installing Coda step.

Will close with https://github.com/CodaProtocol/coda/pull/4625


Docker Registry API v2: Deleting images and tags does not work

I am using the Docker Registry 2.2.0 (Docker Hub image) as part of a continuous integration/deployment setup. My Jenkins creates a new image on every successful build and pushes it to the private registry. That sums up to an average of say 20 builds/images a day. To keep the registry server nice and tidy I need to do some automatic cleanup of images that never make it to the acceptance environment. I did a lot of experiments this week and have come to the conclusion that the API v2 does not handle deletion of images nor does it handle deletion of tags. This makes the docker registry nearly unusable for me, but I need it badly. To clean up, I have to shutdown the registry and run a housekeeping script. Unfortunately, the tags are still there :-(. I see output like this:
curl --insecure -XDELETE https://localhost.localdomain:5000/v2/be/manifests/ad2dc50509b0855bb91cc898d40c05ceee57491fca08e59612168c4f6a1e8baf
{"errors":[{"code":"UNSUPPORTED","message":"The operation is unsupported."}]}
Anyone who can help me with this? Am I doing something wrong? Why is the "operation unsupported"?
Here are my coordinates:
docker version:
Version:      1.9.0
API version:  1.21
Go version:   go1.4.2
Git commit:   76d6bc9
Built:        Tue Nov  3 17:37:20 UTC 2015
OS/Arch:      linux/amd64
docker info:
Containers: 3
Images: 40
Server Version: 1.9.0
Storage Driver: devicemapper
Pool Name: docker-253:0-2354982-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 2.821 GB
Data Space Total: 107.4 GB
Data Space Available: 11.45 GB
Metadata Space Used: 4.346 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.143 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.74 (2012-03-06)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.2.69-xnt-nogr-1.5.3
Operating System: Debian GNU/Linux 7 (wheezy)
CPUs: 16
Total Memory: 7.875 GiB
Name: localhost.localdomain
ID: F4IG
WARNING: No memory limit support
WARNING: No swap limit support
uname -a:
Linux dev03.xxxxxx.xx 3.2.69-xnt-nogr-1.5.3 #1 SMP Thu May 14 21:03:15 CEST 2015 x86_64 GNU/Linux

we are running a similar setup using jenkins and an internal registry and fell foul of this issue, basically they have yet to include the ability to delete images from the registry for v2, even though its shown in the docker registry v2 api documentation, pretty nasty eh!. This caused us to have tp revert back to registry 0.9, as this does include the ability to delete images, awaiting hopeful inclusion of this in docker registry v2.3
see here https://github.com/docker/distribution/issues/422

@eembsen can you open this issue on the https://github.com/docker/distribution issue tracker (or look for existing issues)? This is an issue for the registry (distribution) project, and not something that can be solved in this repository.
I'm going to close this issue here for the reason given above, but thanks for reporting :+1:


Test flight bottom bar redesign

Pull Request Title
Bottom Bar redesign - Message Field container view https://github.com/stakwork/sphinx-mac/issues/389
Bottom Bar redesign - Record Audio and Send button https://github.com/stakwork/sphinx-mac/issues/390
Bottom Bar redesign - Price Button and Paid Message state https://github.com/stakwork/sphinx-mac/issues/391

Description
This pull request addresses the Bottom Bar redesign in Issues:

https://github.com/stakwork/sphinx-mac/issues/389
https://github.com/stakwork/sphinx-mac/issues/390
https://github.com/stakwork/sphinx-mac/issues/391

The following are the addressed issues:

Bottom bar default elements

Background color of the bottom bar changes matching the background color of the chat view
Plus button stays on left side with different color, size and asset
Gif and Emoji buttons are moved to right with different color, size and asset
Plus, Gif and Emoji buttons are now inside the box of the input field
Send button is hidden by default
Record Audio button changes color, size and asset (Recording view stays the same but needs to be adapted to existing position of the record audio button on the bottom bar)

Entered text state

When text is entered in the message field: Font and size changes
When text is entered in the message field: Record audio button is replaced by Send button (send button size, color and asset might change)

Entered large text state

When text entered in the message field becomes multiline:

Plus, Gif and Emoji buttons stay aligned to top inside the field box
Price and Send buttons stay aligned to bottom on the bottom bar
Send buttons stay aligned to bottom on the bottom bar

Paid message state

Tapping on Add Price button reveals price field and changes colors of all elements

Paid large message with large price state

As price string becomes bigger the price view will become wider and the message input field box will become narrower. Keep existing UI constraints and logic to accomplish this.

Open thread state

Add Price button will be collapsed and show just icon instead of icon and label (Add Price) since space is reduced
Add Price button should be removed on threads for now (as it is right now)

Changes Made

Added new set of icons
NSColor

Added new set of colours

ChatBottomView.xib

Update the designs from the xib

ChatMessageFieldView+FieldsExtension.swift

Added updateColor method
Added updateSendButtonColor method
Added updateBGColor method
Added updateMessageBGColor method
Updated textDidChange method

ChatMessageFieldView.swift

Added Outlets and Actions
Updated some methods

Recording Link:
Here is the link to the recording:

https://www.loom.com/share/1ca105cae6eb42c0a3b973ee99129702?sid=79c5e55f-c440-444d-a032-98326fc7c061

@Korede612 Nice work so far! I was watching the loom video you sent and I'm posting some corrections we will need based on what I saw. I might missed some issues that I will see when testing from Xcode and this is why when it's about UI design changes it's critical that you inspect every color, size, margin, font, etc from Figma. Otherwise it could be an endless back and forth with corrections. So please review everything regarding those aspects of the designs I detailed above. On any case I will detail those that I could notice while watching the video:

Plus icon circle background color is wrong and the + itself should be transparent showing the background color of the bottom bar (right now it's kind of white). Check size as well (can't see if it's ok from the video)
Gif and emoji icon colors are wrong as well (too light compared with the color on the designs). When you add an asset you need to set "render as Template Image" for the tint color to apply.

Mic button should be slightly bigger than Send button (and bigger in height than the field view) (they seem to be the same size on your video)
Send button seems to be aligned to the top of the field view but it should be vertically centered
Price button colors seem wrong (font size, weight and color)
Not sure if it's wrong but please check font size and color of the message field text
As it says in the last item of the Price Button and Paid Message state ticket "Add Price button should be removed on threads for now". That means paid messages should be disabled in the thread view for now!

Please once you are done with the corrections send me a new video showing both dark and light mode! Thanks in advance

Update on the Fixes Requested

Thanks for the feedback especially on the render as template. It was really helpful.
I am open to correction although I did my best crosschecking every details over again.

Links to the recording for both dark and light mode

https://www.loom.com/share/f4caee994a3449d3a9c8cd34c18c5d38?sid=9e09cbd6-56ec-4b5b-a24a-2d55c695bb58
https://www.loom.com/share/7edd133ab66e49249d0ebdde4f2559eb?sid=452102d3-ecea-4082-99d9-6b301f72f531


BUG: bounding_box property failing while bbox works

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
bounding_box property returns an error. See code below, bounding_box is also available and if bbox is replaced by this one it fails,
Steps To Reproduce
from pyedb.dotnet.edb import Edb
from pyedb.generic.general_methods import generate_unique_folder_name
import pyedb.misc.downloads as downloads
temp_folder = generate_unique_folder_name()
targetfile = downloads.download_file("edb/ANSYS-HSD_V1.aedb", destination=temp_folder)
edbapp = Edb(edbpath=targetfile, edbversion="2024.1", remove_existing_aedt=True)
poly_with_voids = [pp for pp in edbapp.modeler.polygons if pp.has_voids]
for poly in poly_with_voids:
for void in poly.voids:
test = list(idx.intersection(void.bbox))
if test:
void.expand(1e-3)
Which Operating System are you using?
Windows
Which Python version are you using?
3.10
Installed packages
NA

Hey @svandenb-dev idx is not defined. What does it stand for?

@gkorompi I assume you took the code from unit test ? idx is the Rtree index (Spactial indexed class) to speed up the via search.
https://en.wikipedia.org/wiki/R-tree fyi

@gkorompi this bug is now fixed.
void.bbox works and now regarding the refactoring it is :
void.polygon_data.bounding_box


Build a Playground for the P4 Language

Scala and the Rust Foundation have a Playground where you can try out the language using an interpreter. It would be nice if we had something similar for the P4 language. The switch model can be simple.

We have this!
https://p4.org/sandbox-page/
On Fri, Oct 4, 2024 at 11:08 PM Fabian Ruffy @.***>
wrote:

Scala https://www.scala-lang.org/ and the Rust Foundation
https://www.rust-lang.org/ have a Playground where you can try out the
language using an interpreter. It would be nice if we had something similar
for the P4 language. The switch model can be simple.
—
Reply to this email directly, view it on GitHub
https://github.com/p4lang/project-ideas/issues/21, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOCFUSXPUCSRMD7W4AU5KTZZ5JZ7AVCNFSM6AAAAABPM5U266VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DONRRG43DCMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Oh I see, it is actually on the front-page but I didn't register that.

We should still get this going with an open-source and up-to-date version. Perhaps using Jaehyun's more actively-maintained reference interpreter.


[5.5] Fix make:model factory option behavior

As pointed out in #20793 by @paulredmond, when we run the command:
php artisan make:model -fa Category

it performs all tasks that are done by all option for make:model command, but it should simply create a model & a factory.
This PR achieves the desired behavior by renaming the factory option to s (could be better short code. But i used s because it is indirectly a seeder to a table).

I feel like I'd be creating factories more than I would use --force. Does everything need a short version as a convention? That way -f could be used for the factory.

@paulredmond Yes every command option needs a short code as a convention. This is needed because not everyone likes to type the full option name when running a command. Why i think in this case having the f short code for force is needed.

yah, @paulredmond, that seems like a good suggestion, since force will not be a common action.
every command does not need a short code. it looks like the underlying symfony command allows you to pass in null for the shortcode.  you may want the shortcode but it is not required.
in fact, if you run artisan help route:list, you'll see that there are plenty of options that don't have a 1 letter short code.

there is also precedence for this with the migrate command.
php artisan help migrate
you'll see the force option does not have a short code

As a user, I would probably use --force anyway, because it's less overhead.

Paul, I'd go with this for the PR.  remove the short code for force, and switch factory to an f.

Fixed in another PR.


Type 'undefined' is not assignable to type 'Property'.

Created by: @bradtumy Oct 31 2021 at 18:04 CET
Last updated: Oct 31 2021 at 20:10 CET
ClickUp ID: IK-1709
Description:
I am testing the updatePropertyValue() method in the backend Node SDK.  In my sample code I am fetching the email property from a digital twin and then trying to update the value for that property.
Environment:
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Steps to Reproduce:
Retrieve the email property from a DT
// get the primary email for this DT
const primaryEmail = dt.getProperty('email');
console.log("Primary Email: ", primaryEmail);
2. Create a new string that contains the new value

// the new value for the email property
const email =<EMAIL_ADDRESS>// I like to see what change is about to be made ;-)
console.log("Update the DT with this email: ", email);
3. using updatePropertyValue, provide the primaryvalue object and the new email value

// update the property with the new value
dt.updatePropertyValue(primaryEmail, "brad.tumy@indykite.com");
Expected Behavior:
I am expecting this to update the value of the email property w/o producing errors.
Actual Behavior:
I am getting the following error when the above code runs:
/usr/local/lib/node_modules/ts-node/src/index.ts:587
return new TSError(diagnosticText, diagnosticCodes);
^
TSError: ⨯ Unable to compile TypeScript:
src/authn.ts:190:26 - error TS2345: Argument of type 'Property | undefined' is not assignable to parameter of type 'Property'.
Type 'undefined' is not assignable to type 'Property'.
190   dt.updatePropertyValue(primaryEmail, "brad.tumy@indykite.com");
~~~~~~~~~~~~
at createTSError (/usr/local/lib/node_modules/ts-node/src/index.ts:587:12)
at reportTSError (/usr/local/lib/node_modules/ts-node/src/index.ts:591:19)
at getOutput (/usr/local/lib/node_modules/ts-node/src/index.ts:921:36)
at Object.compile (/usr/local/lib/node_modules/ts-node/src/index.ts:1189:32)
at Module.m._compile (/usr/local/lib/node_modules/ts-node/src/index.ts:1295:42)
at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Object.require.extensions.<computed> [as .ts] (/usr/local/lib/node_modules/ts-node/src/index.ts:1298:12)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12)

Commented by: @bradtumy Oct 31 2021 at 20:10 CET
I was able to clear the error by modifying how I am setting the value for primaryEmail … const primaryEmail = new Property("email").withValue(dt.getProperty("email"));
the issue was that when I was just setting the value by reading the property value nodejs saw that this could possibly return an empty string and would cause the type to be either a property or undefined.  I had to force it to be of type property. Because the method updatePropertyValue was only expecting a property … not a property or undefined.

Closed: Oct 31 2021 at 20:10 CET


Test reattach via playground

Description
Allow developers to test the reattach functionality in both Video and Call Fabric SDKs.
Type of change

[x] Internal refactoring
[ ] Bug fix (bugfix - non-breaking)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Code snippets
In case of new feature or breaking changes, please include code snippets.

I used this piece of code to reproduce issues with the reattach. This allows the SDK to reattach in case the page is reloaded with an active call.
If it is helpful for you as well, we may consider merging it. @jpsantosbh


Contributors

This issue will remain open as a way to add contributors using the @allcontributors bot.
To add yourself as a contributor for this project is really easy. Simply type the following text as a new comment, replacing the text yourusername with your GitHub username:
@all-contributors please add @yourusername for tutorial

@all-contributors please add @Ismael-KG for review

@all-contributors please add @mikekatell for content


Feature Request: Single HTML File

It would be awesome to have a tool that reads in a markdown file and then exports out a single HTML Ficdown file.
Currently, because the HTML file reads in an external MD file, it requires you to host the game on a server in order to play. If all the dependencies of Ficdown were baked into a single HTML file, including the MD text - authors can distribute their games without having players needing to know how to host/serve the game. Essentially, It would allow players to play games offline, kind of like Twine a game.

This can be achieved by throwing the markdown content into an element on the page, then retrieving that into a variable and passing it to the player.
See the test.html example, which works just fine offline.


No response after clicking the build server button

https://*/org//servers/new
{"status":500,"error":"Internal Server Error"}
application-0dd293ea0a8f7f37880ae5bea4a4f1627195bd86b17430b7fb0313790f195df8.js
Loading config from /config/postal.yml
3.3.4

please don't duplicate discussions into issues


DatePicker is setting time to default after selecting time for the first time

🐛 Bug Report
DatePicker is setting time to default after selecting time for the first time
🤔 Expected Behavior
Should set it to the time we selected using the DatePicker
😯 Current Behavior
After inserting the time and leaving the DatePicker, the time is set to the default one.
💁 Possible Solution

🔦 Context

💻 Code Sample

🌍 Your Environment

Software
Version(s)

react-spectrum
"^3.19.0"

Browser
Chrome

Operating System
Mac

🧢 Your Company/Team
 Adobe/Campaign
🕷 Tracking Issue (optional)

To be clear this is specifically because you did not enter the AM/PM segment and left it as the placeholder.

But it is little confusing right?

Looks like it is already supposed to be the case that if the am/pm field is the only one not filled in, that we accept the placeholder. Maybe there is a bug causing that not to happen.
https://github.com/adobe/react-spectrum/blob/1f3dbd56b87c9f5adcdab63e81a6ee64b33314e6/packages/%40react-stately/datepicker/src/useDateFieldState.ts#L336-L343


Ubuntu package for v1.6.2 is released in rpm instead of deb

In assets of v1.6.2 release, ubuntu package is named by eosio.cdt-1.6.2-ubuntu-18.04_amd64.rpm . In local build, packaging script works correctly.

Fixed.
https://github.com/EOSIO/eosio.cdt/releases/tag/v1.6.2


portfolio blows up, when processing user positions

caused this issue when optimizing market selector.

approved

works on dev...still not working on the other

pete is looking into the issue where try.augur.net doesn't behave the same as dev.augur.net


[Bug] MacOS Application hangs when fonts.google.com domain is blocked

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

block domain fonts.google.com
Open the APP
it will take about a minute before the application proceeds to load (I suppose the retries to load the remote fonts)
See error

Expected behavior
A clear and concise description of what you expected to happen.
There should be NO DEPENDENCY on google fonts or any 3rd party services while running a desktop application. also fonts loading should not block the loading of the app.

all google domains/ services are blocked on the network due to the security policy in place.

are you using client from this https://github.com/Yidadaa/ChatGPT-Next-Web/releases/tag/v2.9.9 ?

The latest version of the desktop application, loading Google Fonts does not block the app startup, please upgrade.


Add closed task in the Cumulative flow diagram

It could be great to add closed tasks in the "Cumulative flow diagram". Let me explain why.
In several use cases, the last column is called "Done" or "Finished". Once a task is put in this column, it is (automatically or not) closed. Therefore, in the "Cumulative flow diagram", it seems that not much tasks have been done, but a lot of them are still to be done. In reality, a lot of tasks are already closed and finished, but doesn't appear in the diagram.

The CFD include all tasks now (in master).


How to convert images to C array ?

I've been trying everything and I can't get proper colors.  The color is always shifted one way or the other. see photo.
Is there a walkthrough somehwhere on how to do this ?  The tool in the TFT_eSPI doesn't work.  I can get recognisable images by exporting from GIMP as PNG and using img2cpp utility to create the C-array, but the colors are never correct.

I have tried the instruction in this repo but no matter what Blue and Red are swapped.

It looks exactly like a
tft.setSwapBytes(true);
issue, where the two colour bytes are swapped, Big Endian-Little Endian issue, where Ox00FF is transposed to 0xFF00

Method 1: tft.setSwapBytes(true);
Method 2: Use the mouse to drag the blue and red to exchange

Wow, thank you for the solution.  Dragging the Red block over to the blue fixed the issue.  But It never worked when I tried modifying swapBytes(true);  Why would setting swapBytes(false) not work, but dragging the little color swatch would ?

The other solution that works is changing the following options in the user setup for tft_espi
// #define TFT_RGB_ORDER TFT_RGB  // Colour order Red-Green-Blue
#define TFT_RGB_ORDER TFT_BGR // Colour order Blue-Green-Red

swapBytes() is to modify the order of sending.
For example, the normal transmission is from bit7->bit6->....->bit0.
After enabling, the order is reversed even if bit0->bit1->..bit7


main.node is not a win32 application

I'm able to package and run my Electron app on macOS, however not on Windows. I get:

I've done a rebuild with npm rebuild which appeared to run successfully and recreated main.node and renderer.node.  Didn't fix it.
Please help.

Actually I'm wondering - was it originally built as a 64-bit module?
I'm packaging using a 32-bit Electron, so maybe that's the issue?

@chrisgordon so what was your solution? Other people may experience the same issue in the future so share your findings please!


js-widget: users can perform a blank additional question after the first question

@wd0517 Isn't there a backend verfication logic ?

https://github.com/pingcap/tidb.ai/commit/4503d0f714139b15bdd27fdcc56873f01d111523


Allow user to use "Social login" AND "default login" to access one account

My account was created using "default login" (normal form). Today i tried to login using "social login" and "speakerfight" says:
"Você já tem uma conta, mas escolheu o provedor errado para acessar desta vez. Clique aqui para ser redirecionado para a página correta."
As user, is not good to know that i'm wrong when i'm trying to do something that i think to be right.
In my opinion, if Speakerfight know that i have one account and i'm the owner, the behavior must be: just login and associate all "social login" to "default login" and i'll have "N" ways (Form, Facebook, Google, Twitter, etc) to login using the same account.
Thank's.
(sorry about my poor english)

In the Django allauth package, there are a sort of configuration for doing this.
We can do this by syncing social accounts or when the user tries to log in we look for his alternative account with that same email.


life cycle manager as bean

Extract starting and stopping life cycles into it's own bean.
Additionally, providing the possibility to configure that life cycle beans should not be started at all. This may be relevant in scenarios where the entire service should not be started (db-migration only, etc).

Build fails during security check commons-compress-1.25.0.jar: CVE-2024-26308(5.5), CVE-2024-25710(5.5). The main branch has just been updated to update all dependencies to the latest version.


[EngSys] Validate Changelog before merge instead of during release

After validating a release I was met with this error:
##[error]The changelog entry has the following sections with no content (Bugs Fixed, Breaking Changes, Other Changes). Please ensure to either remove the empty sections or add content to the section.
We should either move this check as-is into the PR CI gates or if we want to be really fancy, make it happen when we go from Unreleased - > a real date.

@xirzec did you run the Prepare-Release script? It would have caught this issue and other potential things like unapproved apis.
That said @praveenkuttappan and I chatted and we are also going to look to start enforcing more of these in the build process when we see the date stamped into the changelog.

@xirzec and I chatted now and found that prepare release script was not run in this case.

Just to clarify @heaths  Prepare-Release did error on the empty sections correct? If not that is a bug that should be fixed. As for the request to have it strip empty sections that is reasonable and we can probably add that, issue filed https://github.com/Azure/azure-sdk-tools/issues/1895.

It did not. That said, I ran it mid-last week. Not sure if there were changes since then. My PR (it's resulting output) was just sitting, waiting for release day.

That change should have already been in place for a while, I'll have @chidozieononiwu double check when he works on issue I opened.

@chidozieononiwu use this issue to check whether or not we are actually running the correct changelog validation steps during prepare-prerelease.

Ran into this exact issue as well for @azure/ai-form-recognizer. I had an empty "Breaking Changes" section in the log. I did run the Prepare-Release script and it did not produce an error, but the pipeline validation failed after approving the release.
For what it's worth, I think all validation steps that might result in a new commit to the repo to resolve them have to be run before approval, since I can't approve the pipelines until I've already gone through the painstaking process of validating the artifact and I have to assume that it will publish successfully once I approve it. If it fails, I have to fix the package and generate and test a new candidate artifact.

It would be helpful if,

The script just removed empty sections. It's already making changes to the file e.g., add the release date.
The release pipeline validate empty sections during the build jobs so we don't waste time validating the signed bits only to find out there was a doc error.

Yes the goal is to have Prepare-Release do all the work and validation that would happen during release and also makes sense for it to do any last edits that are needed before a release.
As for validation during the build that is a little more tricky because we don't always know that we are going to release or not but we are thinking about adding more build step validation when we see that you have a release date stamped into your changelog which tells us you plan to release soon.

How is manually running, say, "net - keyvault" different from it running nightly? There's a condition there (don't feel like looking now, so the aforementioned question wasn't pointed 🙂) you could probably use to determine when you're running the pipeline for a release vs. scheduled (and maybe that is literally it - IIRC, there's an AzPipelines variable that gives you a reason).

From docs:
Build.Reason
There's probably more to the condition to be reliable than that, but one idea to validate earlier but conditionally.

When Build.Reason is manual it might mean you want to do a release but it might not people do manual builds without the intent of releasing. So it isn't the best variable to use. We could introduce another variable but I think the best way we have currently is by checking the release date stamped in the changelog. If you have that then any build we do should start failing if you aren't meeting all the release criteria (i.e. changelog verification, api approval etc)?

Releasing on the actual release date won't always work: many start it early or, like in this case because of the issues this caused, I started late. For various reasons, that's also not unheard of and I've not seen anyone go back and fix their changelog dates.
The archtype-sdk-client.yml currently just uses:
  - ${{if and(ne(variables['Build.Reason'], 'PullRequest'), eq(variables['System.TeamProject'], 'internal'))}}:

If the release stage would run even in that case, why not check the changelog as well?

The trouble is that if we run it in that case and there are multiple sdk's in a given pipeline and you only plan to release a subset of them then the other ones that aren't planning to release and aren't in a valid state will block you from releasing the ones that are in a valid state.
As for the date it doesn't matter what the date is it only matters there is a date as opposed to unreleased and if there is a date then we can assume that you plan to release soon and add the extra validation for that library.

How about not adding them in the first place and just check that all header names are standard (what's documented)? Start from clean.

We definitely will be adding those checks in Prepare-Release and we will also start cleaning out empty sections. I thought it was already enabled there but based on the feedback there must be a bug there.


a hightlight layer occur when switch layer

help help help
Describe the bug
This highlight arises when I use the API "updateParams" to switch different layer
To Reproduce
Steps to reproduce the behavior:

Please visit the Web Site "http://<IP_ADDRESS>:38080/views/openlayer_jingjinji.html"
Click on the seconds tab "污染物类型地图"
select an category in left mune, click "确定"
Play the timeline in bottom
See hightlight （layer of dark color） when switch layer for an instant.

Expected behavior
I don't know why it appeared for an instant and don't hope it appeared
(Please ignore my poor english)

It looks like a tile transition effect as individual tiles will load at different speeds.  Setting transition: 0 in the ol.source.TileWMS options may help to reduce the effect, or you could consider using ImageWMS for your overlay layers.

It looks like a tile transition effect as individual tiles will load at different speeds. Setting transition: 0 in the ol.source.TileWMS options may help to reduce the effect, or you could consider using ImageWMS for your overlay layers.

It’s useful to setting transition:0,although it still exists,I am all gratitude


Rule Validator needs recursively convert attributes to an array.

As reported here:
https://github.com/cloudcreativity/json-api/issues/18
This line:
https://github.com/cloudcreativity/laravel-json-api/blob/master/src/Validator/Attributes/RulesValidator.php#L149
Needs to recursively change the object to an array before passing into the Laravel validator.

@lindyhopchris hello
I'm using cloudcreativity/laravel-json-api v0.2.1 and I believe I found another bug with the object to array conversion.
For structures that contain an array of objects, these won't get converted into arrays:
// request attributes

"multiple": [
  {
    "val1": "one",
    "val2": "two"
  },
  {
    "val3": "three",
    "val4": "four"
  }
],
"nestedObj": {
  "obj1": {
    "val1": "one",
    "val2": "two"
  },
  "obj2": {
    "val3": "three",
    "val4": "four"
  }
}

// toArray conversion of attributes

"multiple" => [
  {
    "val1": "one",
    "val2": "two"
  },
  {
    "val3": "three",
    "val4": "four"
  }
],
"nestedObj" => [
  "obj1" => [
    "val1" => "one",
    "val2" => "two"
  ],
  "obj2" => [
    "val3" => "three",
    "val4" => "four"
  ]
}

This same behavour happens regardless of the nesting level. Please let me know if I can help any further.

Hi @nickelozz
Sorry for slow reply - been on holiday. Yes, this is definitely a bug. I'll be able to look at it on Monday when I'm back from holiday.
Cheers,
Chris

@nickelozz
Believe I've now fixed this if you update your cloudcreativity/json-api dependency to v0.3.3

@lindyhopchris I've tested and it works now...thanks so much.
Apparently in the upcoming version (5.2) of Laravel a lot of what I've been doing manually will be "laravelized" thanks to the new "Form Array Validation"... oh well it was a learning experience :smiley:
In case anyone wants to read about it check here: https://laravel-news.com/2015/11/laravel-5-2-a-look-at-whats-coming/


[Consensus] Couple of omissions

in PowMining when block is found, there is a sequence AcceptBlock, Puller.SetLocation, consensusLoop.FlushAsync, blockRepository.PutAsync and signals.SignalBlock
while in PosMining, i can only see AcceptBlock, Puller.SetLocation, blockRepository.PutAsync and signals.SignalBlock, i am missing consensusLoop.FlushAsync there, i guess these two sequences should be similar

this.UTXOSet.SaveChangesAsync(context.Set.GetCoins(this.UTXOSet), null, this.Tip.HashBlock, context.BlockResult.ChainedBlock.HashBlock); in AcceptBlock in ConsensusLoop should use await or GetResult to wait for it, because otherwise we rely on the fact that the cached coin view that is used here is synchronous

yes we need to add that as well.
You are right in general, but in this case it is sequential so we dodged this one (good spot).

Both should be trivial to fix, can do that soon.


[Snipe Bug] Bot continues to search for pokemon also after capture

Expected Behavior
Bot should walk to the Pokemon, capture it and then go to an other pokemon
Actual Behavior
Bot walks to the pokemon, captures it and then walks to the same pokemon until it reaches the exact position!
Output when issue occurred

2016-08-17 09:40:01,997 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Golduck, 0.06km, left (10 minutes, 11 seconds)
2016-08-17 09:40:07,858 [PokemonCatchWorker] [INFO] [pokemon_appeared] A wild Golduck appeared! [CP 430] [Potential 0.56] [A/D/S 4/9/12]
2016-08-17 09:40:11,274 [PokemonCatchWorker] [INFO] [threw_berry] Threw a Razz Berry! Catch rate with Greatball is now: 48.47
2016-08-17 09:40:11,276 [PokemonCatchWorker] [INFO] [threw_pokeball] Used Greatball, with chance 48.47 (57 left)
2016-08-17 09:40:12,151 [PokemonCatchWorker] [INFO] [pokemon_vanished] Golduck vanished!
2016-08-17 09:40:50,992 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Golduck, 0.04km, left (9 minutes, 22 seconds)
........
 2016-08-17 09:41:00,153 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_encounter] Encountered Pokemon: Golduck

My config
{
    "auth_service": "",
    "username": "",
    "password": "",
    "location": "",
    "gmapkey": "",
    "encrypt_location": "",
    "websocket_server": false,
    "tasks": [
      {
        "type": "HandleSoftBan"
      },
      {
        "type": "SleepSchedule",
        "config": {
          "enabled": true,
          "time": "22:00",
          "duration":"10:00",
          "time_random_offset": "00:24",
          "duration_random_offset": "00:43"
        }
      },
      {
        "type": "CollectLevelUpReward"
      },
      {
        "type": "IncubateEggs",
        "config": {
          "longer_eggs_first": true
        }
      },
      {
        "type": "UpdateLiveStats",
        "config": {
          "enabled": true,
          "min_interval": 15,
          "stats": ["username", "uptime", "stardust_earned", "xp_earned", "xp_per_hour", "stops_visited"],
          "terminal_log": true,
          "terminal_title": true
        }
      },
      {
        "type": "TransferPokemon"
      },
      {
        "type": "NicknamePokemon",
        "config": {
          "enabled": false,
          "nickname_template": "{iv_pct}_{iv_ads}"
        }
      },
      {
        "type": "EvolvePokemon",
        "config": {
            "evolve_all": "Rattata,Weedle,Zubat,Caterpie,Kakuna,Metapod,Diglett,Meowth",
            "first_evolve_by": "cp",
            "evolve_above_cp": 0,
            "evolve_above_iv": 0.1,
            "logic": "or",
            "evolve_speed": 20,
            "use_lucky_egg": false
        }
      },
      {
        "type": "RecycleItems",
        "config": {
          "min_empty_space": 15,
          "max_balls_keep": 100,
          "max_potions_keep": 50,
          "max_berries_keep": 70,
          "max_revives_keep": 70,
          "item_filter": {
            "Pokeball":       { "keep" : 100 },
            "Potion":         { "keep" : 0  },
            "Super Potion":   { "keep" : 5  },
            "Hyper Potion":   { "keep" : 60 },
            "Revive":         { "keep" : 60 },
            "Razz Berry":     { "keep" : 60 }
          }
        }
      },
      {
        "type": "CatchVisiblePokemon"
      },
      {
        "type": "CatchLuredPokemon"
      },
      {
        "type": "SpinFort"
      },
      {
        "type": "MoveToMapPokemon",
        "config": {
          "address": "http://localhost:5000",
          "max_distance": 1000,
          "min_time": 60,
          "min_ball": 10,
          "prioritize_vips": true,
          "snipe": false,
          "snipe_high_prio_only": true,
          "snipe_high_prio_threshold": 400,
          "update_map": true,
          "mode": "priority",
          "map_path": "raw_data",
          "catch": {
            "==========Legendaries==========": 0,
            "Aerodactyl": 1000,
            "Snorlax": 1000,
            "Articuno": 1000,
            "Zapdos": 1000,
            "Moltres": 1000,
            "Dratini": 1000,
            "Dragonair": 1000,
            "Dragonite": 1000,
            "Mewtwo": 1000,
            "Mew": 1000,

            "==========Region Locked==========": 0,
            "Farfetch'd": 1000,
            "Kangaskhan": 1000,
            "Mr. Mime": 1000,
            "Tauros": 1000,

            "==========Very Rare==========": 0,
            "Lapras": 900,
            "Electabuzz": 900,
            "Magmar": 900,
            "Ditto": 900,

            "==========Starters==========": 0,
            "Bulbasaur": 400,
            "Ivysaur": 600,
            "Venusaur": 1000,

            "Charmander": 400,
            "Charmeleon": 600,
            "Charizard": 1000,

            "Squirtle": 400,
            "Wartortle": 600,
            "Blastoise": 1000,

            "Pikachu": 600,
            "Raichu": 1000,

            "==========Semi Rare==========": 0,
            "Porygon": 200,
            "Scyther": 200,
            "Jynx": 200,

            "==========Uncommon==========": 0,

            "Omanyte": 150,
            "Omastar": 500,

            "Seel": 300,
            "Dewgong": 500,

            "Grimer": 200,
            "Muk": 500,

            "Shellder": 200,
            "Cloyster": 500,

            "Gastly": 200,
            "Haunter": 500,
            "Gengar": 1000,

            "Onix": 600,

            "Drowzee": 600,

            "Hypno": 600,

            "Vulpix": 200,
            "Ninetales": 600,

            "Paras": 100,
            "Parasect": 500,

            "Growlithe": 200,
            "Arcanine": 700,

            "Tentacool": 200,
            "Tentacruel": 500,

            "Mankey": 150,
            "Primeape": 500,

            "Clefairy": 150,
            "Clefable": 500,

            "Jigglypuff": 150,
            "Wigglytuff": 500,

            "Venonat": 100,
            "Venomoth": 500,

            "Diglett": 200,
            "Dugtrio": 500,

            "Meowth": 250,
            "Persian": 500,

            "Psyduck": 150,
            "Golduck": 500,

            "Geodude": 100,
            "Graveler": 500,
            "Golem": 800,

            "Eevee": 200,
            "Vaporeon": 800,
            "Jolteon": 800,
            "Flareon": 800,

            "Kabuto": 150,
            "Kabutops": 500,

            "Magikarp": 150,
            "Gyarados": 800,

            "Pinsir": 150,

            "Ponyta": 200,
            "Rapidash": 500,

            "Slowpoke": 200,
            "Slowbro": 500,

            "Magnemite": 250,
            "Magneton": 500,

            "Krabby": 100,
            "Kingler": 500,

            "Voltorb": 200,
            "Electrode": 500,

            "Exeggcute": 300,
            "Exeggcutor": 500,

            "Cubone": 300,
            "Marowak": 800,

            "Hitmonlee": 400,

            "Hitmonchan": 400,

            "Lickitung": 500,

            "Koffing": 200,
            "Weezing": 500,

            "Rhyhorn": 200,
            "Rhydon": 500,

            "Chansey": 800,

            "Tangela": 300,

            "Horsea": 200,
            "Seadra": 600,

            "Goldeen": 150,
            "Seaking": 500,

            "Staryu": 200,
            "Starmie": 800,

            "==========T1 Evolvers==========": 0,
            "Caterpie": 10,
            "Metapod": 10,
            "Butterfree": 500,

            "Kakuna": 10,
            "Beedrill": 500,

            "Pidgeotto": 10,
            "Pidgeot": 300,

            "==========T2 Evolvers==========": 0,
            "Nidoran F": 10,
            "Nidorina": 10,
            "Nidoqueen": 10,

            "Nidoran M": 10,
            "Nidorino": 10,
            "Nidoking": 10,

            "Oddish": 100,
            "Gloom": 200,
            "Vileplume": 600,

            "Poliwag": 200,
            "Poliwhirl": 400,
            "Poliwrath": 800,

            "Abra": 300,
            "Kadabra": 600,
            "Alakazam": 800,

            "Machop": 150,
            "Machoke": 400,
            "Machamp": 800,

            "Bellsprout": 100,
            "Weepinbell": 400,
            "Victreebel": 800

          }
        }
      },
      {
        "type": "MoveToFort"
      },
      {
        "type": "FollowSpiral"
      }
    ],
    "map_object_cache_time": 5,
    "forts": {
      "avoid_circles": true,
      "max_circle_size": 50,
      "cache_recent_forts": true
    },
    "walk_max": 4.16,
    "walk_min": 2.16,
    "action_wait_min": 2,
    "action_wait_max": 4,
    "debug": false,
    "test": false,
    "health_record": true,
    "location_cache": true,
    "distance_unit": "km",
    "reconnecting_timeout": 15,
    "catch_randomize_reticle_factor": 1.0,
    "catch_randomize_spin_factor": 1.0,
    "min_ultraball_to_keep": 10,
    "logging_color": true,
    "catch": {
      "any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
      "// Example of always catching Rattata:": {},
      "// Rattata": { "always_catch" : true }
    },
    "catch_throw_parameters": {
      "excellent_rate": 0.1,
      "great_rate": 0.5,
      "nice_rate": 0.3,
      "normal_rate": 0.1,
      "spin_success_rate" : 0.6
    },
    "release": {
      "any": {"keep_best_cp": 2},
      "// Example of always releasing Rattata:": {},
      "// Rattata": {"always_release": true},
      "// Example of keeping 3 stronger (based on CP) Pidgey:": {},
      "// Pidgey": {"keep_best_cp": 3},
      "// Example of keeping 2 stronger (based on IV) Zubat:": {},
      "// Zubat": {"keep_best_iv": 2},
      "// Also, it is working with any": {},
      "// any": {"keep_best_iv": 3},
      "// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
      "// Zubat": {"keep_best_cp": 2, "keep_best_iv": 3}
    },
    "vips" : {
         "Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
        "any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
        "Lapras": {},
        "Moltres": {},
        "Zapdos": {},
        "Articuno": {},

        "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
        "Mewtwo": {},
        "Dragonite": {},
        "Snorlax": {},
        "// Mew evolves to Mewtwo": {},
        "Mew": {},
        "Arcanine": {},
        "Vaporeon": {},
        "Gyarados": {},
        "Exeggutor": {},
        "Muk": {},
        "Weezing": {},
        "Flareon": {}
    }
}

Other Information
OS: LUbuntu
Branch: master
Git Commit: 423e4dea72c0b04d8882ef90f03949fe3bf35ac2
Python Version: Python 2.7.9

this is not connected to sniping but walking

this is also somewhat not trivial to solve as MoveToMapPokemon, as the name says, takes care only of moving, not catching the pokemon. That is done by a different task. For now the pokemon is considered caught after it's location has been reached
As this is not a bug, but probably a feature request, i would propose adding it to http://feathub.com/PokemonGoF/PokemonGo-Bot
as a feature request

exactly, so I would ignore this issue :P

I'm confused as to what the feature request is @Raiven66 ?
Also we're using github for feature requests, not feathub - https://github.com/PokemonGoF/PokemonGo-Bot/tree/dev#feature-requests

well currently the bot walks with MoveToMap to the location of the pokemon. It is encountered(and caught) when in range though and not upon reaching the destination. As from what I looked at the code, it would not be trivial to stop pursuing the destination of the pokemon after it being caught and since the bot is working fine (just walks extra 50meters) as-is, I think this would be a nice to have thing rather than a bug/issue.
I would close this and file a feature request like

[MoveToMapPokemon] stop going "the last mile" to a pokemon's location after it has been caught and switch to another

@Raiven66 I'll meet you half way, if you make the FR, I'll close this issue. Deal?

As I am not overly in need of this, @MatteCarra would be the person for that :)


Android Studio 4.0 Upgrade

Getting Failed to resolve: br.com.zbra:android-linq:1.1.0
With the latest version of Android Studio with latest version of gradle.
Android Gradle Plugin Version: 4.0.0
Gradle Version: 6.4.1
I know it's an old lib, that's not needed by the masses any more due to java.streams, but unfortunately for me, I am developing an app that needs to work on Android 6!

Hello!
Did you add JCenter to your buildscript repositories section?
buildscript {
    repositories {
        jcenter()
    }
    ...
}

At any rate, I would recommend maybe trying an alternative like RxJava which will provide better support and its more powerful and modern by today's standards.

Yes added it, the lib works perfect for what I want, up until the android studio 4.0 release this weekend. Already have quite a big list of apps for this business made using this lib within them, so would like to keep it working.

Great! Nice to know. Have a good one! Closing.

Sorry, I think my message may have been unclear. It's not resolved, I have had that in the app all the time, it is still failing with it in.

Oh, ok. Will give it a look, but the Android Studio version should not interfere. Will let you know if I find anything.

I found this on StackOverflow https://stackoverflow.com/questions/47760395/android-studio-does-not-import-dependency-from-jcenter-or-maven-central
Had new comments a few days ago (may 28) recommending the removal of mavencentral() from repositories. Maybe its linked. Not sure if this may be your issue, but its worth a try.

I don't have mavencentral, build.gradle here... my phone is removing line spacing from the code, apologies about that 😕
buildscript {
repositories {
google()
jcenter() }

dependencies {
classpath 'com.android.tools.build:gradle:3.6.3'
classpath 'com.google.gms:google-services:4.3.3'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.1.0'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files } }
allprojects {
repositories {
google()
jcenter() } }
task clean(type: Delete) {
delete rootProject.buildDir }```

I have removed my project dependency on this lib, thanks for suggesting RxJava for it alternatively, looked into it, and the method for using it is nice.
Only thing is, the syntax for this lib was very nice and readable, and very little code for it, but can't win everything!

Hey,tks for the kind words. I put some time into finding out what was missing but I could not put my finger on it. Seems like its not actually published to JCenter, but to Spring and for some reason, that doesnt cut it anymore. I will update this issue if I can find the solution.

@gfaiers You can still add jar file from https://repo.spring.io/plugins-release/br/com/zbra/android-linq/1.1.0/

@begali how does that translate to the gradle file? Please post a sample so I can update the README with that info.

@brunovinicius  Problem is with gradle version 6.1.1 not Android studio. New gradle version refusing to download the library. Gradle version 5.6.4 and gradle plugin version 3.6.2 works perfectly. But in order to work with new gradle version I downloaded jar file of library from maven repository and added it locally. You should be wondering why maven not jcenter. First I downloaded from jcenter, but all classes and interfaces didn't have public access modifiers, then downloaded from maven. I don't know why new gradle refusing to download.

1.1.0 release tag is missing from repo. I was using this library in my project "compile 'br.com.zbra:android-linq:1.1.0'". What is the alternative?

Hey everyone! With the help of @hamzaahmedkhan we managed to pull of an viable alternative to use the lib.
Refer to https://jitpack.io/#zbra-solutions/android-linq/1.1.0 for instructions. I will update the ReadME accordingly


🐛 BUG: Incorrect "too many crons" error

What version of Wrangler are you using?
2.0.24
What operating system are you using?
Linux
Describe the Bug
I'm wrongly getting workers.api.error.too_many_crons [code: 10072].
I'm on the Workers free plan, which has a maximum of 5 Cron Triggers per account. I have 4 already active Cron Triggers divided over 2 Workers, one script has 3 Cron Triggers and the other one has 1 Cron Trigger. I'm trying to publish the Worker that has 3 Cron Trigger again (just a normal code update) and I get that " too many crons" error.
My theory is that it sees that my account currently has 4 total Cron Triggers. Then when I want to upload the Worker it thinks 3 more Cron Triggers are getting added, thus 4 + 3 > 5. In fact, the 3 Cron Triggers in the script I'm trying to upload are already on my account, there are no new Cron Triggers.

We will investigate, we may have more questions once we have started looking into it. Thank you! 😄

Quick win to reproduce it reliably.

I've encountered the same issue with wrangler publish with wrangler 2.0.24.
My wrangler file has the line crons = ["0 * * * *", "0 0 * * 1", "0 0 1 * *"].
It works fine the first time I publish but I get the error "workers.api.error.too_many_crons" on every subsequent publish.
The workaround it to delete the crons via the dashboard before publishing.
Also weird, trying to delete a cron trigger via the dashboard also says "You've reached your cron limit" when there a 4 cron triggers on the account (3 in service A and 1 in service B). Deleting service B allowed to delete a trigger on service A).
All the triggers were created via wrangler.toml

Just to update here—we've confirmed this is a issue and are working on fixing it (as you suspected, the issue is with the addition of old triggers and replaced triggers)

This should be fixed going forward as of the next release


Write articles for communicating elements release

To help coordinate the Carbon elements release with other IDL refresh-related work, we're most likely going to need to craft a couple of articles stating what we're going to be building, and then when they are built. This issue is to help coordinate drafts/outlines/etc for these articles 👍

First draft: https://gist.github.ibm.com/joshblack/356820a911fc76a1a708259a7ca15707
Ready for any/all comments/feedback!


Fixed few issues with Storage concepts section.

Removed plural api object names such as PersistentVolumes.

Explicitly mentioned alpha status of snapshot APIs.

Fixed #16321.

Other minor changes.

This PR is created based on feedback in this thread:
https://groups.google.com/forum/#!msg/kubernetes-sig-storage/EBGjZJ-0gGs/0wWhZMgXAgAJ

I signed CNCF's CLA so that check should pass now.

/lgtm

/assign @xing-yang

I have pushed a commit to handle few of the review comments. For now, this is a separate commit. Please let me know if I need to squash it with the previous one (I don't know the recommended procedure as this is my first PR here). Thanks.

I fixed one merge conflict and pushed a single commit containing all the changes.

/lgtm

@mistyhacks Thanks for extensive review. I just wanted to point out that many comments are regarding text that I haven't changed in this PR. I am not opposed to making the suggested changes but just wanted to mention it. BTW, I am still not clear about the best practice regarding plural object names. Should we use object name in plural but without backquotes? For example, "VolumeSnapshots" as opposed to "VolumeSnapshots".
In case of persistent volumes, their abbreviation seems to be prevalent so one alternative there would be to use "PVs" and "PVCs".
Lastly, there is one part of this PR which fixes a bug in the document (#16321). I am thinking of moving it into its own PR so that the error can be fixed while we continue to discuss other changes.

/sig storage

@draghuram if you're talking about a Kubernetes object like Namespace, Pod, DaemonSet, etc, then the style guide pretty much never puts those names in quotes.
Sometimes in English localization it's appropriate to write “namespace”, “namespaces”, “services” etc because those are also the English words for the relevant concept. That's fine so long as it's very clear to readers which meaning you intend.

I made some changes based on review comments. More over, couple of changes originally present in this PR have been merged with master using separate PRs. So I removed those changes from here.

@draghuram Please feel free to /reopen this PR when you're ready to continue with feedback.
/close