Reset should recreate collateral and protx for local node

Resetting a local node will need to recreate the collateral and protx before the system is usable again. We should recreate this when running reset on local, or alternatively automate something like mn reset && mn setup local.
Expected Behavior
Node should be immediately startable after reset
Current Behavior
Node needs to run through setup local again before becoming startable after reset, and config is different.
Possible Solution

Steps to Reproduce (for bugs)

Spin up local node
mn reset
mn start

Context

Your Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop, server, or mobile):
Link to your project:

@strophy is the temp reset script that ships with dashmate sufficient to cover the scope of this issue or shall we keep this issue open and create an incubator bounty for it?


Be more helpful when validating the input database

igdiscover init validates the input database and checks whether there are duplicate sequences.
The error we get complains only about the first duplicate sequence that it finds, so it is necessary to re-run init in order to fix and find all problems, which is annoying, especially if the GUI is used.

@NestorVB I am going to fix this such that the input database is automatically repaired.

It works as follows.

If a record is empty, it is skipped.
If a record name occurs more than once, the second record name gets a suffix (_1, _2 etc.).
If a sequence occurs more than once, occurrences after the first are skipped

This is how it looks when running igdiscover init:
$ igdiscover init --library-name=testing --db=db-with-problems --reads=reads.1.fastq.gz test
INFO: Records 'VH2b' and 'VH2c' contain the same sequence, skipping 'VH2c'
INFO: Record 'empty_sequence' is empty, skipping it.
INFO: Record name 'same_name' occurs more than once, replaced with 'same_name_1'
INFO: Directory test initialized.
INFO: Edit test/igdiscover.yaml, then run "cd test && igdiscover run" to start the analysis


🚀 Enhance Security and Development Experience: Add .env.example, Remove .env, and Provide Vercel Setup Instructions

Description
🎉 Summary:
This pull request aims to improve the security of the project and streamline the onboarding process by introducing changes related to environment variables. It includes the addition of a .env.example file, the removal of the .env file, and step-by-step instructions for setting up environment variables on Vercel
Fixes #738
Replace issue_no with the issue number which is fixed in this PR
Changes:

Added .env.example File:

Created the .env.example file containing placeholder environment variables and explanations to guide developers.
This file will serve as a template for local development environment setup.

Removed .env File:

The sensitive .env file has been removed to prevent accidental exposure of sensitive information in the repository.

Provided Vercel Setup Instructions:

Added detailed instructions for maintainers to set up environment variables on Vercel before merging this pull request.
These instructions ensure a smooth deployment process while maintaining security and privacy.

🔧 Instructions for Maintainer:
Before merging this pull request, please follow these steps on Vercel to set up the environment variables required for the project:

Open the Vercel dashboard for the project.

Go to the project's settings or environment variables section.

Add the necessary environment variables with their corresponding values:

MONGODB_URI: MongoDB connection string for database access.
OPENAI_API_KEY: OpenAI API key for integrating with the AI service.
JWT_ACCESS_SECRET: JWT access token secret for authentication.
JWT_REFRESH_TOKEN: JWT refresh token secret for authentication.
GOOGLE_CLIENT_ID: Google OAuth client ID for authentication.
GOOGLE_CLIENT_SECRET: Google OAuth client secret for authentication.
GOOGLE_AUTH_URI: Google OAuth authentication URI.

Ensure the environment variables are securely stored and not exposed publicly.

Once the environment variables are set up on Vercel, you can confidently merge this pull request to enhance project security and development efficiency.
🚀 Benefits:

Improved security by excluding sensitive .env file from version control.
Streamlined onboarding process with clear instructions for local environment setup.
Enhanced development experience with a standardized environment variable template.

Screenshots
Please see this video for vercel settings its imporant
https://github.com/SurajPratap10/Imagine_AI/assets/85815172/ee380e8e-294a-4a0c-b5bc-7e0d548aafbd
Checklist

[ ] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[ ] Code follows the established coding style guidelines
[ ] All tests are passing

@SurajPratap10 ,please see video and make changes on vercel if remainning ,before merging my pull request

@SurajPratap10 ,please see video and make changes on vercel if remainning ,before merging my pull request

@SurajPratap10 ,please review and merge my pull request

@SurajPratap10 ,you have given level2 in issue,but in pr you have given level1 ,please value my contribution and give me level2


Hang when the size of read-bytes is less than the size of write-bytes

Your environment.

Version: Release or SHA
Browser: include version
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

Version: c4c9c17a848896b2b1ffb7c60c904ca67fc18d31
What did you do?

Modify the example in data-channels-detach
(setting buffer size as messageSize-1)
and communicate with data-channels-detach-create
(setting up 2 nodes.
nodeA: data-channels-detach-create
nodeB: modified data-channels-detach)
The modified data-channels-detach is as follow:
https://gist.github.com/chhsiao1981/e054f6263b1c1b147bbc35076a7f93f2
What did you expect?
non-blocked with error, may or may not still read some bytes.
What happened?
looks like blocked.
It's possible that some bad guy may send large amount size of the msg to the receiver.
and results in blocked/deadlock in the receiver side.

After further testing～
The mechanism is that the receiver just skips the msg in which the size of read-bytes < the size of write-bytes.
the receiver still receives the msgs in which the size of read-bytes >= the size of write-bytes.
We can view this as a feature rather than a bug.


about part of dataset(json file) that can be used to train by the the version published in May , but loaded failed in this version(publishing in June)

Reminder

[X] I have read the README and searched the existing issues.

System Info

llamafactory version: 0.8.2.dev0
Platform: Linux-5.10.134-16.1.an8.x86_64-x86_64-with-glibc2.35
Python version: 3.10.12
PyTorch version: 2.3.0+cu121 (GPU)
Transformers version: 4.41.2
Datasets version: 2.20.0
Accelerate version: 0.31.0
PEFT version: 0.11.1
TRL version: 0.9.4
GPU type: NVIDIA H100 80GB HBM3
DeepSpeed version: 0.14.3
Bitsandbytes version: 0.43.1
vLLM version: 0.5.0.post1

Reproduction
06/18/2024 06:11:50 - INFO - llamafactory.data.template - Replace eos token: <|im_end|>
06/18/2024 06:11:50 - INFO - llamafactory.data.loader - Loading dataset identity.json...
Generating train split: 0 examples [00:00, ? examples/s]
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/datasets/packaged_modules/json/json.py", line 130, in _generate_tables
pa_table = paj.read_json(
File "pyarrow/_json.pyx", line 308, in pyarrow._json.read_json
File "pyarrow/error.pxi", line 154, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 91, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: JSON parse error: Column() changed from object to array in row 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/datasets/builder.py", line 1997, in _prepare_split_single
for _, table in generator:
File "/usr/local/lib/python3.10/dist-packages/datasets/packaged_modules/json/json.py", line 153, in _generate_tables
df = pd.read_json(f, dtype_backend="pyarrow")
File "/usr/local/lib/python3.10/dist-packages/pandas/util/_decorators.py", line 211, in wrapper
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/pandas/util/_decorators.py", line 331, in wrapper
return func(*args, **kwargs)
TypeError: read_json() got an unexpected keyword argument 'dtype_backend'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/llamafactory-cli", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/llamafactory/cli.py", line 110, in main
run_exp()
File "/usr/local/lib/python3.10/dist-packages/llamafactory/train/tuner.py", line 47, in run_exp
run_sft(model_args, data_args, training_args, finetuning_args, generating_args, callbacks)
File "/usr/local/lib/python3.10/dist-packages/llamafactory/train/sft/workflow.py", line 48, in run_sft
dataset = get_dataset(model_args, data_args, training_args, stage="sft", **tokenizer_module)
File "/usr/local/lib/python3.10/dist-packages/llamafactory/data/loader.py", line 174, in get_dataset
all_datasets.append(load_single_dataset(dataset_attr, model_args, data_args, training_args))
File "/usr/local/lib/python3.10/dist-packages/llamafactory/data/loader.py", line 109, in load_single_dataset
dataset = load_dataset(
File "/usr/local/lib/python3.10/dist-packages/datasets/load.py", line 2616, in load_dataset
builder_instance.download_and_prepare(
File "/usr/local/lib/python3.10/dist-packages/datasets/builder.py", line 1029, in download_and_prepare
self._download_and_prepare(
File "/usr/local/lib/python3.10/dist-packages/datasets/builder.py", line 1124, in _download_and_prepare
self._prepare_split(split_generator, **prepare_split_kwargs)
File "/usr/local/lib/python3.10/dist-packages/datasets/builder.py", line 1884, in _prepare_split
for job_id, done, content in self._prepare_split_single(
File "/usr/local/lib/python3.10/dist-packages/datasets/builder.py", line 2040, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the dataset
Expected behavior
老的数据集如果加载不成功可以跑一边下面的代码：
import pandas as pd
import pyarrow as pa
import pyarrow.json as paj
import json
加载 JSON 文件
with open('your_file.json', 'r', encoding='utf-8') as f:
data = json.load(f)
确保所有列的数据类型一致
def ensure_consistent_types(record):
return {k: str(v) for k, v in record.items()}
data = [ensure_consistent_types(record) for record in data]
创建 DataFrame
df = pd.DataFrame(data)
将 DataFrame 保存为 JSON 文件
output_file = 'processed_file.json'
df.to_json(output_file, orient='records', lines=True, force_ascii=False)
读取并验证新的 JSON 文件
pa_table = paj.read_json(output_file)
print(pa_table)
Others
No response

@SleepyHollowforesthills datasets=2.20.0 requires pandas>=2.0.0，you can use the datasets=2.19.2. see #4356


azure-function-maven-plugin version 1.3.4 does not work anymore

Plugin name and version
azure-function-maven-plugin version 1.3.4
The 1.3.4 version of the plugin does not work anymore.
The underlying auth fails.
Upgrading to the 1.14.1 version solves the problem.

@mnriem Thanks a lot for your report! Azure cli has made a breaking change since 2.30.0, deprecated old authentication and migrate to MSAL, which was not supported by old maven plugins, you may get more info from here.
Azure maven tooling has migrated to azure identity library for authentication which support authentication with latest azure cli, please upgrade to the latest maven plugin when meet this issue.


Pause requests when chain is disabled

Alliance staking asset links should load gracefully and not crash when refreshed

an example localhost link


Bundle update

This was mostly routine, but there were two notable updates:

Amazon released version 3 of their Ruby SDK and have moved to a modular approach. When I first did my bundle update, there were TONS of gems in the diff. I remembered reading something about this, so I switched over to requiring just the S3 gem and all was well with the world.

The micromachine gem had a major version bump because they changed the arity of the callbacks to accept a payload. I got a bunch of failing tests on this, but there was an obvious release note about it on the repo, so I just updated the couple callbacks to throw away another argument and was on my way.

Other than that, I did update bundler too.

Doing a selfie-merge on this one...


add support for oh-my-fish

You need to:

rename your repo to theme-pure (omf convention)

then submit the package
omf submit theme/pure https://github.com/rafaelrinaldi/theme-pure.git

closes https://github.com/rafaelrinaldi/pure/issues/3

Bump.

@bpinto thanks for jumping in but this has been addressed already. Check #3.
@edouard-lopez FYI I'm closing the PR.


Support Multiple clientids for aws cognito

get_current_user = CognitoCurrentUser(     region=region, userPoolId=poolid, client_id=clientid )
Often, we would like to support multiple aws Cognito app clients for a single API.
Requesting a feature to support multiple app client ids for the aws Cognito objects.
Maybe something like
get_current_user = CognitoCurrentUser(     region=region, userPoolId=poolid, client_id=[clientid1, clientid2] )

I would be interested by this, a naive approach would probably be to keep the data in memory? Also it would be great to do that dynamically and not only at start

I would be interested by this, a naive approach would probably be to keep the data in memory? Also it would be great to do that dynamically and not only at start

what do you mean by "dynamically"?


Go Live [25 May]

Push to live

Docs Build status updates of commit 8ab6f18:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/webhooks-and-connectors/how-to/connectors-creating.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Account settings needs the UI cleaned up, possibly merged with the "Modify Organization" page

Page needs some esthetics help. Align text, etc.
Question: Why do we have this? Only one single email address is there? Can’t this just be combined on the Modify Organization Page? Why have this on a whole separate page? Doesn’t seem useful to user and makes things less “fluid.”

This was fixed with your PR and the css fixes I put in.
It is all lined up on the page now:


Version b31 failing to JB iPhone-6 on 11.4.1

The new version b31 isn't jailbreaking my iPhone-6 on 11.4.1, for some reason it shows running thru all 38 processes every time without issue, it even downloaded the Kernel Cache form Apple.  But each time it runs thru the 38 processes it just simply reboots my phone into stock mode.  I've had to re-sideload version b28 again to get my JB back working.  Not sure if there is any log files I can send you.  I am MetrolinaAlerts on twitter I helped you test on my iPhone-6 11.4.1 right before you released the JB for A8 support...  Thank you.  Not sure if anyone else is having this same issue...

I have the same issue on my iPad Pro with iOS 12.1.1

what is the success rate for iPhone 6 11.4.1 with b28 ?

No diagnostics given or logs, so closing.

With version b28 I was usually having to do it multiple times. Usually by #6 or #7 it would finally JB.  For some reason Unc0ver kept rebooting my phone randomly at night when my power cord was connected and a few days ago it sent me into a bootloop where my phone wouldn’t even restore.  I has to get an iPhone-6S and i downloaded the new version b38 & it has greatly improved success rate!


'X-Frame-Options' set to 'DENY' ?

Error while trying to migrate to SDK 3Refused to display.
'https://console.firebase.google.com/project/XXXXX/database/data .... ' in a frame because it set 'X-Frame-Options' to 'DENY'.
What does it mean ?

I started having this problem when trying to migrate to Firebase SDK 3. Before migrating everything was working just fine.
Hope for a solution soon.

I see the same problem..

@locomuco Have you found a solution yet ?

@myuseringithub no unfortunately not, but doesn't bother me enough to start searching for the root cause

Same issue here.
This is the reply I get from firebase:
{
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "keyExpired",
    "message": "Bad Request"
   }
  ],
  "code": 400,
  "message": "Bad Request"
 }
}

All the keys I know about are absolutely fine.

When does this error occur? On page load? I haven't seen this one myself...

Happens on page load, yes

Does anyone have a public URL that exhibits this behavior? I've not been able to reproduce this.

https://project-4156531278292366083.firebaseapp.com/#/blog

@locomuco your auth-domain is incorrect:
auth-domain="project-4156531278292366083.firebaseio.com"

should be firebaseapp.com instead.
Is that potentially the problem for everyone here?

solves my problem

Solved mine too.


feat: menu button as column type

Description
Add menu Button as a Column type
Fixes #5636  (issue)
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: feat/menu-button-as-column-type

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
54.79 (-0.02)
36.75 (-0.19)
33.82 (0.01)
55.4 (-0.03)

:red_circle:
app/client/src/components/propertyControls/ComputeTablePropertyControl.tsx
32.76 (-1.17)
16 (-3.05)
22.22 (0)
32.14 (-1.19)

:red_circle:
app/client/src/components/propertyControls/MenuItemsControl.tsx
22.83 (0)
26.32 (-3.09)
7.69 (0)
24.69 (0)

:red_circle:
app/client/src/entities/Widget/utils.ts
92.86 (-4.11)
89.13 (3.84)
100 (0)
92.71 (-4.17)

:green_circle:
app/client/src/widgets/WidgetUtils.ts
75 (8.33)
40.63 (22.45)
50 (33.33)
69.23 (11.34)

:red_circle:
app/client/src/widgets/ButtonWidget/component/index.tsx
48.91 (-6.35)
33.67 (-3.3)
42.86 (-9.14)
48.15 (-5.39)

:red_circle:
app/client/src/widgets/MenuButtonWidget/component/index.tsx
26.92 (-1.08)
15.15 (-0.48)
0 (0)
31.11 (-0.71)

:red_circle:
app/client/src/widgets/TableWidget/component/TableUtilities.tsx
36.53 (-4.03)
22.43 (-0.87)
14.63 (-1.59)
34.64 (-4.59)

:sparkles: :new:
app/client/src/widgets/TableWidget/component/components/menuButtonTableComponent.tsx
29.79
14.71
0
35

:sparkles: :new:
app/client/src/widgets/TableWidget/widget/getTableColumns.tsx
30.43
0
0
20

:green_circle:
app/client/src/widgets/TableWidget/widget/index.tsx
26.84 (0.24)
5.59 (-0.2)
28 (1.08)
26.52 (0.18)

:green_circle:
app/client/src/widgets/TableWidget/widget/propertyConfig.ts
95.56 (57.26)
100 (89.8)
93.1 (28.58)
95.56 (55.85)

:sparkles: :new:
app/client/src/widgets/TableWidget/widget/propertyUtils.ts
24.8
8
23.08
23.28

@Tooluloope Verified this PR and please find the issues below - Testing in-progress will update further
1.Disabled , Visible and Compact toggle should be displayed one by one

2.Sub menu's are overlapping with the table rows and columns

@YogeshJayaseelan No.2 requires you to set a background color for the Menu buttons. It's currently on transparent thats why it looks like they overlap

@Tooluloope Verified the fix for the issue 1 and it is working fine now.
Please find the additional issues below,

Re-open - By default the sub menu's are transparent - There needs to be default colour for the sub menu items

The order of items in property pane of Menu Button slightly differs with the Menu button column - The order of items in property pane should match

Menu Button:

Label
Menu Item
Menu 1
Menu 2
Menu 3
Visible Toggle
Disable Toggle
Compact Toggle
Styles
Menu Style
Menu Variant
Border Radius
Box Shadow
Shadow Colour
Icon
Icon Alignment

Menu Button Column

Visible Toggle
Disabled Toggle
Compact Toggle
Button Properties
Icon
Icon Alignment
*Label
*Menu Colour
*Menu Variant
*Border Radius
*Box Shadow
*Shadow Colour
Menu Items
Menu 1
Menu 2
Menu 3

4.By default the Menu Button column looks like disabled - This is due to Default menu colour is not set

5.By default the label field - Evaluated value is undefined

@Tooluloope Verified the fixes for issues 2,4,5 and they are working as expected
New issues:

By Default the Menu button column's colour is 'Not Selected' and it should be Green - #03B365

Can we rename the Menu Button Column Default label to 'Open Menu' instead of Action. Currently Both Button and Menu Button shows the Label name as 'Action'

@YogeshJayaseelan
Issue 3. This isn't an issue, We're making the table widget property pane consistent.
issue 6 and 7 have been fixed

@Tooluloope Verified all the issues and they are working as expected. we can proceed further


Add support for universal wheels

Since arrow is a pure python module which support python 2 and 3 with the same code, it can be put in a universal wheel.

Current coverage is 100% (diff: 100%)

Merging #371 into master will not change coverage

@@           master   #371   diff @@
====================================
  Files           8      8
  Lines        1244   1244
  Methods         0      0
  Messages        0      0
  Branches      193    193
====================================
  Hits         1244   1244
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 319f2d0...e0d408a

shipit 👍

Looks good to me.


Can I import AR.js to react  or webpack now ?

Do you want to request a feature or report a bug?
I want  import AR.js to react.

What is the current behavior?
I don't know how to do it with  import AR.js to react .
If the current behavior is a bug, please provide the steps to reproduce.

Please mention other relevant information such as the browser version, Operating System and Device Name
ios13.4.1
safari
What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?

We are working on this feature see PR https://github.com/AR-js-org/AR.js/pull/116, see also issue https://github.com/AR-js-org/AR.js/issues/99

Yes you can we have also published the first npm beta packages<EMAIL_ADDRESS>you can install with npm:
npm i @ar-js-org/ar.js

and for additional infos read this issue https://github.com/AR-js-org/AR.js/issues/234


Reselect with Immer not playing well together?

I'm using createSelector along with createReducer/createSlice function provided by Redux Toolkit.
This backed by Immer, and it allows me to directly mutate state in reducers. Very useful.
https://redux-toolkit.js.org/api/createReducer#direct-state-mutation
However I'm finding that because it ALWAYS returns a new state, it makes createSelector useless, because even a deeply nested toggle to a boolean, causes a whole new State object to be returned, and so it fails the === test that Reselect relies on.
Below is an example
export interface CounterState {
    value: number
    items: Items[]
}

export interface Items {
    enabled: boolean
}

const initialState: CounterState = {
    value: 0,
    items: []
}

export const counterSlice = createSlice({
    name: 'counter',
    initialState,
    reducers: {
        toggleLast: (state) => {
            state.items[state.items.length - 1].enabled = !state.items[state.items.length - 1].enabled
        },
        add: (state) => {
            state.items.push({ enabled: false })
        },
    },
})

and UI
import { RootState } from './store'
import { useSelector, useDispatch } from 'react-redux'
import { add, Items, toggleLast } from './counterSlice'
import { createSelector } from "@reduxjs/toolkit";

let items: Items[] = []
const selectedItems = createSelector(
    (state: RootState) => {
        if (items === state.counter.items) {
            console.log("Same")
        } else {
            console.log("Diff")
        }
        items = state.counter.items
        return state.counter.items
    },
    (items) => {
        return items.filter(x => x.enabled).length
    }
)

export function Counter() {
    const selectedItemCount = useSelector(selectedItems)
    const itemsCount = useSelector<RootState>((state) => state.counter.items.length)
    const dispatch = useDispatch()

    console.log("Render")
    return (

                <button
                    aria-label="Add"
                    onClick={() => dispatch(add())}
                >
                    Add
                </button>
                <button
                    aria-label="Toggle"
                    onClick={() => dispatch(toggleLast())}
                >
                    Toggle
                </button>
                Selected:{selectedItemCount}

                Total:{itemsCount}

    )
}

There's some test code that shows that, the item[] are always in a new array, even when just a toggle call is made (item[items.count-1].enabled  = !enabled)
Do Immer and Reselect not work well together? Anyone have any experience with the new?

To be clear, immutable updates always require returning new references for every level of nesting being updated:

https://redux.js.org/usage/structuring-reducers/immutable-update-patterns#updating-nested-objects

Immer just makes that process simpler to write.
It's worth noting that createSelector runs two different checks internally:

First, are all of the input arguments the same as last time?  If so, it can bail out right away
Second, if any of the arguments are different, it will call all of the "input selectors".  It then takes all of their return values, and checks to see if any of those have changed.

createSelector will only actually run the "output selector" if at least one of the extracted values have changed.
So, yes, I would fully expect that the rootState check would almost always show that it's a different value. That's how immutable updates work, and that's how Redux works.
What matters from there is how often the output selector gets run. If you move your logging down into that function, you should see that it does not re-run if other parts of the state change - only when state.counter.items is updated in some way.  But, per the earlier comment, updating one field in one of those items will cause the creation of a new item object, a new items array, a new counter object, and a new state object.  So, flipping counterState.items[3].enabled = false would generate a new counterSlice.items array, and thus cause the output selector to re-run.
So, yes, this is all expected behavior because of how immutable updates work, and not anything specific to Immer.
You might want to take a glance at these resources:

https://daveceddia.com/react-redux-immutability-guide/
https://redux.js.org/usage/structuring-reducers/immutable-update-patterns
https://redux.js.org/usage/deriving-data-selectors

The one other note here is that this can lead to situations where the output selector is forced to re-run, even though the output ends up being conceptually similar to before. As an example, picture an output selector of (todos) => todos.map(todo => todo.id), and then flip one todo.completed flag.  New todo object, new todos array, so the output selector reruns... but all of the todos still have the same ids.  So, the previous and new todoIds arrays are shallow equal to each other (all the same contents), but are different references. This can lead to some unnecessary re-rendering.
That's why Reselect 4.1 added the ability to customize output result comparisons. In this situation, we could use shallowEqual as a way to compare the old and new todoIds arrays, and if they're equivalent it will reuse the old array reference.
See https://github.com/reduxjs/reselect/releases/tag/v4.1.0 for some more details.


Make sparsity detection and coloring interfaces public

Closes #82.

Since the discussion in https://discourse.julialang.org/t/is-compat-jl-worth-it-for-the-public-keyword/119041/ has come to a close, I think I'd rather put all the public declarations for ADTypes in one file, which makes the following approach the most appealing:
if VERSION > ...
    include("public.jl")
end

Looking at the "likes" on Discourse, it looks to me like most people favor Mason's macro-based solution, which is what is implemented here as of 1cd4162. The disadvantages of a separate src/public.jl file have been discussed on Discourse as well.
Have you taken a look at the current diff? I think it's simple, succinct and readable.

I'm obviously biased towards my own code, but I like the clean overview it provides in the main file, separated by use-case:

# Automatic Differentiation
export AbstractADType
export AutoChainRules,
       AutoDiffractor,
       AutoEnzyme,
       AutoFastDifferentiation,
       AutoFiniteDiff,
       AutoFiniteDifferences,
       AutoForwardDiff,
       AutoModelingToolkit,
       AutoPolyesterForwardDiff,
       AutoReverseDiff,
       AutoSymbolics,
       AutoTapir,
       AutoTracker,
       AutoZygote
@public AbstractMode
@public ForwardMode, ReverseMode, ForwardOrReverseMode, SymbolicMode
@public mode
@public Auto

# Sparse Automatic Differentiation
export AutoSparse
@public dense_ad

# Sparsity detection
export AbstractSparsityDetector
export jacobian_sparsity, hessian_sparsity
@public sparsity_detector
@public NoSparsityDetector
@public KnownJacobianSparsityDetector
@public KnownHessianSparsityDetector

# Matrix coloring
export AbstractColoringAlgorithm
export column_coloring, row_coloring, symmetric_coloring
@public coloring_algorithm
@public NoColoringAlgorithm

In the spirit of maintainability, I would like to avoid macros whenever I can. But I don't feel very strongly about this so if others prefer this way I'll yield.

As you know, I generally agree with that sentiment, but in this case the macro simply returns Expr(:public, args...).

Also for some reason I didn't see code coverage?

Looks like it wasn't triggered on previous PRs either. The codecov PR page looks odd as well, with all PRs being untitled. Maybe just the usual codecov bugginess?

Fair enough. Are the symbols correctly marked on 1.11?

How do I check this? By looking at the docstrings in REPL help mode?

I think the easiest is to add a test that only runs on 1.11 and that verifies whether the unexported Symbols we marked public are part of names(ADTypes).
https://discourse.julialang.org/t/what-does-the-new-public-keyword-actually-do/108975/3?u=gdalle


background video of welcome page

I think the website will look more effective if we replace the background video of foreigner in home page by some Indian stuff, because the website is dedicated to INDIA only.

@Saumya-Patel this issue is already open https://github.com/QAZIMAAZARSHAD/Voters-Registration-Portal/issues/145.
You can work on that, ping me to assign you.

/assign


chore: prepare google-cloud-java for (23.0.0) upgrade

google-cloud-shared-dependencies is now part of this google-cloud-java repository.


[AIRFLOW-2748] dbexportcmd & dbimportcmd should support use_customer_cluster, use_customer_label in QuboleOperator

JIRA

[x] My PR addresses the following Airflow JIRA

Description

[x] Currently the QuboleOperator & qubole_hook in the Airflow codebase doesn't support use_customer_cluster, customer_cluster_label  and hive_serde command arguments in Airflow. This PR is for adding the above functionality.

Tests

[x] This is a very small change to add additional parameters to the API (Qubole SDK) call, hence doesn't require adding test cases.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3597   +/-   ##
=======================================
  Coverage   76.85%   76.85%
=======================================
  Files         204      204
  Lines       15522    15522
=======================================
  Hits        11930    11930
  Misses       3592     3592

Continue to review full report at Codecov.

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

Thanks @Joylal4896 for the PR.  Cheers

sure @Fokko, I have squashed all my commits into one with the Jira Ticket Id mentioned in the commit message.

@Fokko could you please review and merge this change, it's needed urgently.


Sign in and out refresh page fix. #123

For bug mentioned here https://github.com/StarcounterApps/Website/issues/123#issuecomment-320702788

It seems this PR doesn't fix the issue.
Steps:

Go to http://localhost:8080/websiteeditor
Log out
Refresh the page
Log in

Result: the page doesn't refreshed correctly


Code snippet preview now properly hides the preview tiggering classname

Original code wasn't accessing the top level "codeToCreateSnippetClass", since it was running inside the each loop and wasn't proxied, so "this" pointed to the jQuery element. Also, _this."codeToCreateSnippetClass" returns the classname with the period at the beginning, but we don't need that, since the outerHTML does not include that and the replace will fail. Thus why it is regexped out.

Perfect! Thank you so much!


owners: add Trail of Bits to PST for current contract.

Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

CC @envoyproxy/security-team


Feature request: Make keywords more visible in results pane

I tried this on default theme and it is slightly better, but if the linked word/phrase in the results pane could be given more contrast than present, either via darker bolding or a highlight, that could be helpful.
Not sure if possible, but just wanted to put it out there 🫠

Thank you for reaching out with this idea. SNW in the file preview is using default styling for the pane from search. What this means is its using the themes default as defined for search results. So you can tweek these settings with CSS.

Oh that's good to know! I'm not very technical so I'll have to ask around for some help with that :)

Thank you for reaching out with this idea. SNW in the file preview is using default styling for the pane from search. What this means is its using the themes default as defined for search results. So you can tweek these settings with CSS.

@TfTHacker Thanks for creating this plugin. I don't think the current version respects the default styling from search. Demo:

Built-in search: highlight
Built-in backlinks ("toggle backlinks in document"): highlight
SNW panel: normal

I have been able to tweak the behaviour somewhat using the following CSS snippet, but it would highlight all links in the search context, not just the relevant link.
.snw-ref-item-info a {
    text-decoration: underline;
    /* color: var(--link-color) !important; */
    background-color: var(--text-highlight-bg);
}

Is there a way to selectively restyle links to the node under inspection? Thank you.


Refactor watch and provider logic

I wanted to do some hacking so here goes. I'm fine if you don't want to have a PR, but have a discussion about the design first.
This is a refactoring of the watch logic and consequently also the provider logic. It simplifies the watch logic by offloading it to the client-go IndexInformer infrastructure which additionally fixes a bug currently in the controller where it could loose events.
The provider has been changed to a smaller interface:
type Provider interface {
	Ensure(configs map[Resource]map[string]struct{}) error
	String() string
}

Where the provider has to implement Ensure() which takes the full desired configuration observed by the controller and applies this. For AWS provider this means:

Check if a stack already exists
If not, create a new stack.
If it already existed, check if the configuration has changed from what is stored on the stack, and update the stack with the new configuration.

Small diagram showing the internal flow:
+------------------+
| ConfigMapWatcher |
+-------------+----+
              |
              v
          +---+-----+        +------------+      +----------+
          | eventCh +<-------+ controller +----->+ provider |
          +---------+        +------------+      +----------+

Apart from only acting on the eventCh the controller also has an internal resync interval default 5m where it will call the provider to ensure the config is applied.
Status

[x] Add/refactor tests
[x] Fix TODOs

I like the PR, the statemachine style channel I had done before was nice in the beginning, but turned out to be not well testable

@szuecs ready for final review. I added tests to the main part of AWS provider and to the controller loop.

:+1:

:+1:


dts: update memory map and remove ext-uicr

Extended UICR will not be used as its configurations will be merged
with the UICR registers in NVR.
Memory maps changes are needed to align with pre compiled
firmware.

Tested here: https://github.com/zephyrproject-rtos/zephyr-testing/pull/286


path to pr-reminder in incorrect

should be
The configuration for pr-reminder is located in the openshift/release repo under clusters/app.ci/pr-reminder.

/close


Cannot join chat group via sign in link

https://glipped.herokuapp.com/
There is a sign in button with link https://app.glip.com/r/chat/3901284358
Clicking this link doesn't take me to the correct glip group.

This should be updated to:
https://app.glip.com/chat/r?groupid=3901284358


Removal of flair

I was confused, as I was trying to use flair but realized that the code doesn't recognize that intent handler.
fa24588ea45e4f507c3f1258653a24634970d841 seems to be the moment where flair was... deprecated? But that commit kept the flair documentation, and I have been unable to find any reference on the status of flair, its deprecation or what happens with it.
Can I (Should I?) use flair in my GPU-ready headless (mic-less, speaker-less) device?

I hadn't found the rhasspy-voltron documentation, and reading its documentation I realized that it says explicitly that is not yet supported in 2.5. I'll keep an eye on that!


Fixes #11 - Add code to configure the expiration of the S3 signature #3

There is a merge conflict. Could you please fix it?


New method: webpage "as user would see" - like htmlunit page.asNormalizedText()

Hi,
I write app that needs to read webpage as would user see, then save it to file (without interaction).
Here's a webpage I need to process.
I've read the docs and tried to do it with bow.Body() but I get the html source so with tags like <pre> <p> so bufio reads it and it does mess, of course I can post-process removing all < started etc. but It's a lot of code to cover all scenarios.
I've done it in java once with htmlunits page.asNormalizedText() or python with selenium (I know there's selenium for go, but I'd rather omit additional webdriver config etc. that's why I also use your library :))
Do you think it'd be good to add such feature? Or if, you don't think it's a good idea, could you help me find other solution?
Thanks in advance

You could try using a specific css selector instead of bow.Body(). For instance.
bow.Dom().Find("body p pre").Each(func(_ int, s *goquery.Selection) {
    fmt.Println(s.Text())
})

That should give you the text inside of the inner  tag.

Thanks! :)


Implementation for adding external links in release notes

This pull request provides implementation for adding external links in release notes using property. Issue #46.

@mahendrabishnoi2 Thank you for your first contribution! This has now been merged into master.

Thank You @mbhave @philwebb for the opportunity.


Fix for clicking section header in API shows correct sub-sections

Currently if you visit http://expressjs.com/4x/api.html and click the "Request" menu item it expands the "Application" section since the last item in "Application" is closest() to the one you clicked. Same goes for other sections as well.
I unified all the IDs and included the .h2 anchors in the list of headings so it can find the correct closest one.

Thanks. This can be merged, if you can fix its affect on 3.x docs.
We are working on a new menu, by the way.

Actually 3.x docs never had this issue that those work just fine still.
Nice, I noticed that scrolling issue too once I got home and used my laptop. I could take a stab at fixing that as well. A quick fix would be to not have the menu as a fixed position so you can scroll down and click Response. I will comment over there to keep the discussions intact.

This should be a fix for the overflowing issue on smaller screens unless you had a better idea for a menu.

Thanks!


Optimize WGL context creation performance on some systems

Cache the results of WglContext::selectBestPixelFormat to speed up context creation on systems where pixel format selection is an expensive operation.
This is a simpler version of the change proposed in #2508.
While I can't test this change myself (doesn't make much of a difference when using an AMD GPU it seems), it is possible that it might make a more noticeable difference on systems with an Nvidia/Intel GPU.
To test this change just create a lot of contexts and see which variant finishes faster.

Updated.

@lucasz93 does this fix your slow start up?


Update deprecated theme api's (after v3.19)

I also believe that it is no longer maintained, let's wait for the owner a few weeks, then we can consider creating a parallel package.

Is there a way to have Flutter checkout your PR #8 version specifically?
Or did someone migrate this to a parallel project in the end?

Is there a way to have Flutter checkout your PR #8 version specifically? Or did someone migrate this to a parallel project in the end?

@mobikats
We at the moment have locally embedded the library in our project waiting for this PR, it is few files and we decided to integrate it.
I hope @JackJonson can merge it.

Thanks @rickypid, good idea and probably simpler to support in future.


ImageTool.load() fails in war

Hi,
Thanks for the ImageTools plugin!
I have been trying to use the image-tools plugin in my grails application. It works as expected when running in InteliJ or under 'grails run-app' but is failing when I deploy it as a war in Tomcat.
I have been persisting the image files to the database (it fails for both hSQLdb and PostgreSQ data sources)/  The problems occurs when I create and image from the stored byte [] object in production.
I have made s small test app that demonstrates the problem.
domain class:
class Image {
byte [] img
static constraints = {
}
}
controller:
class ImageController {
...
...
...
def getImageThumbnail = {
    def imageInstance = Image.get(params.id)

    def imageTool = new ImageTool()

    println "starting load"
    imageTool.load(imageInstance.img)
    println "done!"

    imageTool.thumbnail(55)
    def thumbImage = imageTool.getBytes("JPEG")

    response.contentType = "image/jpeg"
    response.contentLength = thumbImage.length
    response.outputStream << thumbImage
}

(I have trimmed things down to the bare essentials here)
the point is the getImageThumbnail action works fine in development, but fails when I build a war and deploy it in Tomcat.
I don't think it is the Tomcat config - my other web apps and other aspects of the app work fine, but the getImageThumbnail action fails at the ImageTool.load call. In other words the output to the log file is the single line
'starting load' and the app hangs
What am I doing wrong?
Mike

Resolved this problem, at least for now.
This turned out to be a problem with the commons daemon jsvc on Mac OS/X Lion
Now I am running Tomcat using the startup.sh/ shutdown.sh scripts and everything is fine.  This is strange, because everything else was working fine in the webapp besides the imagetools plugin.
Don't have any more time to spend on this now.
Other details:
Mac OS/X Lion / grails 1.3.7
Tomcat V. 7.0.21
Postgresql 9.0.4
jsvc and jni binaries built without issue in x86_64.
I also tried using the jai calls from the plugin source and, as before, everything
worked fiun except when running in a tomcat instance started by jsvc.

closed this issue as it was not due to a problem with the image-tools plugin


Bugfix: Suspend event out of order

For more details, see https://trello.com/c/vKfxm83B

 [uploader] Error: Suspend/resume events out of order


Regex filtering through environment variables for responses?

I have extremely severe Tourette's Syndrome, and almost all of my triggers are extremely common, and cause me great physical pain through motor tics (taking the form of painful twitching). Unfortunately, some of my triggers are in the current database of responses for certain moods, so I can't exactly use the full extent of cargo-mommy's features, without editing responses.json. Thankfully, if cargo-mommy supported regexes (with hex escapes so that I don't have to type my triggers, since that would also trigger me) for filtering out certain responses via an environment variable, all I'd have to do is set an environment variable in my .bashrc or whatever, and cargo-mommy would be safe for me to use. Sadly, I don't have much experience with the Rust ecosystem, so I have no idea what crates would be best for this, or how to implement this effectively.

I will also note that I have something similar set up for my IRC client, HexChat, using a Python script. It's kinda finicky and doesn't always work, but when it does it's pretty great.

Not to toot my own horn (well, maybe just a little bit), but my own mommy implementation allows you to filter out phrases that include specific words or phrases using the MOMMY_FORBIDDEN_WORDS setting. If you have any issues or suggestions for the feature, feel free to open an issue over there.


flyekit requires importlib-metadata>=4.0

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
Upstream package does not specify importlib-metadata as a pinned requirements, however features in the 4.0 release series are required for the standard entrypoints:
Repro trace with importlib-metadata < 4.
This is a little confused, because it looks like importlib-metadata and importlib_metadata are both present in conda-forge.
% python mvp.py
Traceback (most recent call last):
  File "mvp.py", line 1, in <module>
    from flytekit import task, workflow
  File "/Users/brianmcconeghy/abcd/.conda/lib/python3.8/site-packages/flytekit/__init__.py", line 245, in <module>
    load_implicit_plugins()
  File "/Users/brianmcconeghy/abcd/.conda/lib/python3.8/site-packages/flytekit/__init__.py", line 239, in load_implicit_plugins
    discovered_plugins = entry_points(group="flytekit.plugins")
TypeError: entry_points() got an unexpected keyword argument 'group'

Looked into this confusion: The importlib-metadata repo looks like it's archived and read-only, so I'll open a PR to pin importlib_metadata>=4 as a req.


helmfile sync --timeout <timeout_value> returns "unknown flag: --timeout" despite being documented as supported

Operating system
macOS Ventura 13.6.7 (22G720)
Helmfile Version
v0.165.0
Helm Version
version.BuildInfo{Version:"v3.11.3", GitCommit:"323249351482b3bbfc9f5004f65d400aa70f9ae7", GitTreeState:"clean", GoVersion:"go1.20.3"}
Bug description
The helmfile sync --timeout option does not appear to be supported despite being documented.

# wait for k8s resources via --wait. (default false)
wait: true
# if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout (default false, Implemented in Helm3.5)
waitForJobs: true
# time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks, and waits on pod/pvc/svc/deployment readiness) (default 300)
timeout: 600

$ helmfile sync --timeout 900
unknown flag: --timeout

$ echo $?
3

The --wait and --wait-for-jobs options do appear to be accepted as documented:
$ helmfile sync --wait false --wait-for-jobs false --help
...<SNIP HELP OUTPUT>...

$ echo $?
0

Looking at the code, it appears that timeout may not have been implemented:

https://github.com/helmfile/helmfile/blob/3f6c03999afd06cb06236189becb5a13c4e46ac4/cmd/sync.go#L44-L45
https://github.com/helmfile/helmfile/blob/3f6c03999afd06cb06236189becb5a13c4e46ac4/pkg/config/sync.go#L21-L24

Example helmfile.yaml
N/A
Error message you've seen (if any)
unknown flag: --timeout
Steps to reproduce
helmfile sync --timeout 900
Working Helmfile Version
N/A
Relevant discussion
No response

@yxxhero Any update on this? Does your pinning of the issue signal an acknowledgement that it's a bug? If so, any plans to address it?
Thanks!


Documentation calls deno add an alias for deno install, and deno remove alias for deno uninstall

The documentation page for the CLI runtime subcommand deno install (https://docs.deno.com/runtime/reference/cli/install/) says that the subcommand deno add is an alias for deno install.
I think that calling this an alias is misleading since the two commands do not do the same thing. deno add only updates the configuration file to add the specified dependency to the "imports" field. deno install actually downloads and installs dependencies on the user's computer.

Similarly, the documentation page for the CLI runtime subcommand deno uninstall (https://docs.deno.com/runtime/reference/cli/uninstall/) says that the subcommand deno remove is an alias for deno uninstall.
I think that calling this an alias is misleading since the two commands do not do the same thing. deno remove only updates the configuration file to remove the specified dependency from the "imports" field. deno install actually removes/uninstalls dependencies form the user's computer.

The tip is now deleted

@thisisjofrank Thank you for looking at this issue. The tips appear to still be in the files for both pages (screenshots and line numbers shown below). If you agree with the suggestion to remove or modify these to be less misleading about what the subcommands do, I will gladly open a pull request with suggested changes.
runtime/reference/cli/install.md, lines 31 to 35

runtime/reference/cli/uninstall.md, lines 33 to 37


[Documentation] Custom Association Field

It may be useful to add in the documentation how to add a relation as a custom field.
You only need to add the reference column to the table and the following lines in initializers/public_activity.rb
PublicActivity::Activity.class_eval do
  belongs_to :parent, :polymorphic => true
end

Works like a Charm, even for polymorphic associations (maybe it could work for has_many_and_belongs_to relations... didn't test it).
Thanks for this awesome gem.

We moved it to the README, thanks!


Calibration Features

[x] Expected Calibration Error metric
Implemented calibration versions of all major multiple-choice benchmarks:
[x] LogiQA
[ ]

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

@herbiebradley I see that your checklist is marked fully complete. Is this ready for review, or is more work needed?

@herbiebradley I see that your checklist is marked fully complete. Is this ready for review, or is more work needed?

More work needed, will update tomorrow


first-cut model, interface updates, sample data

@jread-usgs check it out when you can, please

Coverage increased (+16.23%) to 77.86% when pulling 757d96d752c858fbbc7fc743dc521e4084fa073e on aappling-usgs:master into 46bc0e5655eafdb04b27f4112e77b27896cc93f6 on USGS-R:master.


Update 01-setup-ldap-password

BUGFIX: Dont exit before creating new secrets.tdb

@guillaumedsde can you fix/merge this? I am also running into issues, because the container program exits instead of creating the secrets.tdb file.

hi @Oliver-Hanikel I have commited a fix for this


Possible problems with Python 3.4

I've made a new setup of the project on a virtualenv with Python 3.4 (I've been using Python 3.5 until now), and on this setup (Py3.4) the test suite has presented some erros, specially related to TCP connections and some kind of "timing" error.
Should we try to fix the errors on Py3.4 or should we go with Python 3.5 (that is working fine)?
Below is the log of python setup.py test when using python 3.4.
python-openflow is also the current develop branch version (commit bcaa729 )
kyco is on the develop branch version (commit 73b78e0 ).
This issue may be related to issue #58 . Maybe, fixing #58 this will be also fixed.

make: Entering directory '/home/diraol/devel/kyco/docs'
sphinx-build -b doctest -d _build/doctrees   . _build/doctest
Running Sphinx v1.4.5
loading pickled environment... done
loading intersphinx inventory from python.inv...
WARNING: intersphinx inventory 'python.inv' not fetchable due to <class 'FileNotFoundError'>: [Errno 2] No such file or directory: '/home/diraol/devel/kyco/docs/python.inv'
building [mo]: targets for 0 po files that are out of date
building [doctest]: targets for 9 source files that are out of date
updating environment: 0 added, 1 changed, 0 removed
reading sources... [100%] modules
/home/diraol/devel/kyco/docs/modules.rst:1: WARNING: toctree contains reference to nonexisting document 'kyco'
looking for now-outdated files... none found
pickling environment... done
checking consistency... /home/diraol/devel/kyco/docs/kyco.core.rst:: WARNING: document isn't included in any toctree
done
running tests...
Doctest summary
0 tests
0 failures in tests
0 failures in setup code
0 failures in cleanup code

build succeeded, 3 warnings.
Testing of doctests in the sources finished, look at the  results in _build/doctest/output.txt.
make: Leaving directory '/home/diraol/devel/kyco/docs'
Running examples in documentation
running test
running egg_info
writing top-level names to Kyco_Kytos_Controller.egg-info/top_level.txt
writing Kyco_Kytos_Controller.egg-info/PKG-INFO
writing dependency_links to Kyco_Kytos_Controller.egg-info/dependency_links.txt
writing requirements to Kyco_Kytos_Controller.egg-info/requires.txt
reading manifest file 'Kyco_Kytos_Controller.egg-info/SOURCES.txt'
writing manifest file 'Kyco_Kytos_Controller.egg-info/SOURCES.txt'
running build_ext
test_client (tests.test_core_apps.test_ofcore.TestOFCoreApp)
Testing basic client operations. ... 2016-08-04 14:40:17,509 - INFO [Kyco] Starting Kyco - Kytos Controller
2016-08-04 14:40:17,509 - INFO [Kyco] Message In Event Handler started
2016-08-04 14:40:17,510 - INFO [Kyco] App Event Handler started
2016-08-04 14:40:17,510 - INFO [Kyco] Raw Event Handler started
2016-08-04 14:40:17,511 - INFO [Kyco] Message Out Event Handler started
2016-08-04 14:40:17,511 - INFO [Kyco] Loading kyco apps...
2016-08-04 14:40:17,514 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:17,514 - INFO [Kyco] Loading app ofcore
2016-08-04 14:40:17,611 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:17,611 - DEBUG [Kyco] [buffer: raw_event] Added: KycoNewConnection
2016-08-04 14:40:17,611 - DEBUG [Kyco] New connection from <IP_ADDRESS>:43063
2016-08-04 14:40:17,612 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoNewConnection
2016-08-04 14:40:17,612 - DEBUG [Kyco] New message from <IP_ADDRESS>:43063 at thread Thread-2
2016-08-04 14:40:17,614 - INFO [Kyco] Handling KycoNewConnection event
2016-08-04 14:40:17,615 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:17,616 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:17,617 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:17,618 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:17,619 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInHello
2016-08-04 14:40:17,619 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInHello
2016-08-04 14:40:17,619 - DEBUG [Kyco] MsgInEvent handler called
2016-08-04 14:40:17,619 - DEBUG [Kyco] Handling KycoMessageInHello
2016-08-04 14:40:17,620 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:17,620 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutHello
2016-08-04 14:40:17,620 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutHello
2016-08-04 14:40:17,620 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:17,621 - DEBUG [Kyco] Sending a FeaturesRequest after responding to a Hello
2016-08-04 14:40:17,623 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:17,623 - DEBUG [Kyco] Client <IP_ADDRESS>:43063 disconnected
2016-08-04 14:40:17,624 - INFO [Kyco] Stopping Kyco
2016-08-04 14:40:17,624 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutFeaturesRequest
2016-08-04 14:40:17,624 - DEBUG [Kyco] Connection lost from <IP_ADDRESS>:43063
2016-08-04 14:40:17,625 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutFeaturesRequest
2016-08-04 14:40:17,625 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:17,625 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:17,625 - DEBUG [Kyco] [buffer: raw_event] Added: KycoConnectionLost
2016-08-04 14:40:17,626 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoConnectionLost
2016-08-04 14:40:17,627 - INFO [Kyco] Handling KycoConnectionLost event
2016-08-04 14:40:18,112 - INFO [Kyco] Stop signal received by Kyco buffers.
2016-08-04 14:40:18,112 - INFO [Kyco] Sending KycoShutdownEvent to all apps.
2016-08-04 14:40:18,112 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,113 - DEBUG [Kyco] [buffer: raw_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,113 - INFO [Kyco] raw_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,113 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,113 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:18,114 - DEBUG [Kyco] RawEvent handler stopped
2016-08-04 14:40:18,114 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,115 - INFO [Kyco] msg_in_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,115 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,115 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:18,116 - DEBUG [Kyco] MsgInEvent handler stopped
2016-08-04 14:40:18,116 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,116 - INFO [Kyco] msg_out_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,117 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,117 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:18,117 - DEBUG [Kyco] MsgOutEvent handler stopped
2016-08-04 14:40:18,117 - DEBUG [Kyco] [buffer: app_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,118 - INFO [Kyco] app_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,118 - DEBUG [Kyco] [buffer: app_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,118 - INFO [Kyco] Stopping thread: MsgInEvent Handler
2016-08-04 14:40:18,119 - DEBUG [Kyco] AppEvent handler stopped
2016-08-04 14:40:18,119 - INFO [Kyco] Stopping thread: AppEvent Handler
2016-08-04 14:40:18,119 - INFO [Kyco] Stopping thread: RawEvent Handler
2016-08-04 14:40:18,120 - INFO [Kyco] Stopping thread: MsgOutEvent Handler
2016-08-04 14:40:18,120 - INFO [Kyco] Stopping thread: TCP server
ok
test_echo_reply (tests.test_core_apps.test_ofcore.TestOFCoreApp)
Testing a echo request/reply interaction ... 2016-08-04 14:40:18,125 - INFO [Kyco] Starting Kyco - Kytos Controller
2016-08-04 14:40:18,126 - INFO [Kyco] Message In Event Handler started
2016-08-04 14:40:18,126 - INFO [Kyco] App Event Handler started
2016-08-04 14:40:18,127 - INFO [Kyco] Raw Event Handler started
2016-08-04 14:40:18,127 - INFO [Kyco] Message Out Event Handler started
2016-08-04 14:40:18,128 - INFO [Kyco] Loading kyco apps...
2016-08-04 14:40:18,128 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:18,129 - INFO [Kyco] Loading app ofcore
2016-08-04 14:40:18,227 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,227 - DEBUG [Kyco] [buffer: raw_event] Added: KycoNewConnection
2016-08-04 14:40:18,228 - DEBUG [Kyco] New connection from <IP_ADDRESS>:43064
2016-08-04 14:40:18,228 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoNewConnection
2016-08-04 14:40:18,229 - DEBUG [Kyco] New message from <IP_ADDRESS>:43064 at thread Thread-5
2016-08-04 14:40:18,229 - INFO [Kyco] Handling KycoNewConnection event
2016-08-04 14:40:18,230 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,230 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:18,231 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:18,233 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:18,233 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInHello
2016-08-04 14:40:18,234 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInHello
2016-08-04 14:40:18,234 - DEBUG [Kyco] MsgInEvent handler called
2016-08-04 14:40:18,234 - DEBUG [Kyco] Handling KycoMessageInHello
2016-08-04 14:40:18,235 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:18,235 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutHello
2016-08-04 14:40:18,235 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutHello
2016-08-04 14:40:18,236 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:18,236 - DEBUG [Kyco] Sending a FeaturesRequest after responding to a Hello
2016-08-04 14:40:18,238 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:18,238 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutFeaturesRequest
2016-08-04 14:40:18,238 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutFeaturesRequest
2016-08-04 14:40:18,239 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:18,241 - DEBUG [Kyco] New message from <IP_ADDRESS>:43064 at thread Thread-5
2016-08-04 14:40:18,241 - DEBUG [Kyco] Reading the binary_data
2016-08-04 14:40:18,241 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,241 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:18,242 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:18,252 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:18,252 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInFeaturesReply
2016-08-04 14:40:18,252 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInFeaturesReply
2016-08-04 14:40:18,252 - DEBUG [Kyco] MsgInEvent handler called
2016-08-04 14:40:18,252 - DEBUG [Kyco] Handling KycoMessageInFeaturesReply Event
2016-08-04 14:40:18,253 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:18,253 - DEBUG [Kyco] [buffer: app_event] Added: KycoSwitchUp
2016-08-04 14:40:18,253 - DEBUG [Kyco] [buffer: app_event] Removed: KycoSwitchUp
2016-08-04 14:40:18,253 - DEBUG [Kyco] AppEvent handler called
2016-08-04 14:40:18,279 - DEBUG [Kyco] New message from <IP_ADDRESS>:43064 at thread Thread-5
2016-08-04 14:40:18,280 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,280 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:18,281 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:18,282 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:18,283 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInEchoRequest
2016-08-04 14:40:18,283 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInEchoRequest
2016-08-04 14:40:18,284 - DEBUG [Kyco] MsgInEvent handler called
1
None
2016-08-04 14:40:18,285 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:18,285 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutEchoReply
2016-08-04 14:40:18,286 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutEchoReply
2016-08-04 14:40:18,286 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:18,288 - INFO [Kyco] Stopping Kyco
2016-08-04 14:40:18,288 - DEBUG [Kyco] Client <IP_ADDRESS>:43064 disconnected
2016-08-04 14:40:18,288 - DEBUG [Kyco] Connection lost from <IP_ADDRESS>:43064
2016-08-04 14:40:18,289 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,289 - DEBUG [Kyco] [buffer: raw_event] Added: KycoConnectionLost
2016-08-04 14:40:18,289 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoConnectionLost
2016-08-04 14:40:18,290 - INFO [Kyco] Handling KycoConnectionLost event
2016-08-04 14:40:18,290 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:18,290 - DEBUG [Kyco] [buffer: app_event] Added: KycoSwitchDown
2016-08-04 14:40:18,291 - DEBUG [Kyco] [buffer: app_event] Removed: KycoSwitchDown
2016-08-04 14:40:18,291 - DEBUG [Kyco] AppEvent handler called
2016-08-04 14:40:18,728 - INFO [Kyco] Stop signal received by Kyco buffers.
2016-08-04 14:40:18,729 - INFO [Kyco] Sending KycoShutdownEvent to all apps.
2016-08-04 14:40:18,729 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:18,729 - DEBUG [Kyco] [buffer: raw_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,729 - INFO [Kyco] raw_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,730 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,730 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:18,730 - DEBUG [Kyco] RawEvent handler stopped
2016-08-04 14:40:18,730 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,731 - INFO [Kyco] msg_in_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,731 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,731 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:18,732 - DEBUG [Kyco] MsgInEvent handler stopped
2016-08-04 14:40:18,732 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,733 - INFO [Kyco] msg_out_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,733 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,733 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:18,733 - DEBUG [Kyco] MsgOutEvent handler stopped
2016-08-04 14:40:18,734 - DEBUG [Kyco] [buffer: app_event] Added: KycoShutdownEvent
2016-08-04 14:40:18,734 - INFO [Kyco] app_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:18,735 - DEBUG [Kyco] [buffer: app_event] Removed: KycoShutdownEvent
2016-08-04 14:40:18,735 - INFO [Kyco] Stopping thread: MsgInEvent Handler
2016-08-04 14:40:18,735 - DEBUG [Kyco] AppEvent handler stopped
2016-08-04 14:40:18,736 - INFO [Kyco] Stopping thread: AppEvent Handler
2016-08-04 14:40:18,736 - INFO [Kyco] Stopping thread: RawEvent Handler
2016-08-04 14:40:18,736 - INFO [Kyco] Stopping thread: MsgOutEvent Handler
2016-08-04 14:40:18,736 - INFO [Kyco] Stopping thread: TCP server
ok
test_full_handshake_process (tests.test_core_apps.test_ofcore.TestOFCoreApp) ... 2016-08-04 14:40:18,741 - INFO [Kyco] Starting Kyco - Kytos Controller
2016-08-04 14:40:18,742 - INFO [Kyco] Message In Event Handler started
2016-08-04 14:40:18,743 - INFO [Kyco] App Event Handler started
2016-08-04 14:40:18,743 - INFO [Kyco] Raw Event Handler started
2016-08-04 14:40:18,744 - INFO [Kyco] Message Out Event Handler started
2016-08-04 14:40:18,744 - INFO [Kyco] Loading kyco apps...
2016-08-04 14:40:18,745 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:18,745 - INFO [Kyco] Loading app ofcore
2016-08-04 14:40:18,842 - INFO [Kyco] Stopping Kyco
2016-08-04 14:40:19,246 - INFO [Kyco] Stop signal received by Kyco buffers.
2016-08-04 14:40:19,246 - INFO [Kyco] Sending KycoShutdownEvent to all apps.
2016-08-04 14:40:19,246 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,246 - DEBUG [Kyco] [buffer: raw_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,247 - INFO [Kyco] raw_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,247 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,247 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:19,247 - DEBUG [Kyco] RawEvent handler stopped
2016-08-04 14:40:19,248 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,248 - INFO [Kyco] msg_in_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,248 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,249 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:19,249 - DEBUG [Kyco] MsgInEvent handler stopped
2016-08-04 14:40:19,249 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,250 - INFO [Kyco] msg_out_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,250 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,250 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:19,250 - DEBUG [Kyco] MsgOutEvent handler stopped
2016-08-04 14:40:19,251 - DEBUG [Kyco] [buffer: app_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,251 - INFO [Kyco] app_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,252 - DEBUG [Kyco] [buffer: app_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,252 - INFO [Kyco] Stopping thread: MsgInEvent Handler
2016-08-04 14:40:19,252 - DEBUG [Kyco] AppEvent handler stopped
2016-08-04 14:40:19,252 - INFO [Kyco] Stopping thread: AppEvent Handler
2016-08-04 14:40:19,253 - INFO [Kyco] Stopping thread: RawEvent Handler
2016-08-04 14:40:19,253 - INFO [Kyco] Stopping thread: MsgOutEvent Handler
2016-08-04 14:40:19,253 - INFO [Kyco] Stopping thread: TCP server
ok
test_handshake (tests.test_core_apps.test_ofcore.TestOFCoreApp)
Testing OF switch handshake process ... 2016-08-04 14:40:19,258 - INFO [Kyco] Starting Kyco - Kytos Controller
2016-08-04 14:40:19,259 - INFO [Kyco] Message In Event Handler started
2016-08-04 14:40:19,260 - INFO [Kyco] App Event Handler started
2016-08-04 14:40:19,260 - INFO [Kyco] Raw Event Handler started
2016-08-04 14:40:19,261 - INFO [Kyco] Message Out Event Handler started
2016-08-04 14:40:19,261 - INFO [Kyco] Loading kyco apps...
2016-08-04 14:40:19,262 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:19,262 - INFO [Kyco] Loading app ofcore
2016-08-04 14:40:19,361 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,362 - DEBUG [Kyco] [buffer: raw_event] Added: KycoNewConnection
2016-08-04 14:40:19,362 - DEBUG [Kyco] New connection from <IP_ADDRESS>:43065
2016-08-04 14:40:19,362 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoNewConnection
2016-08-04 14:40:19,363 - DEBUG [Kyco] New message from <IP_ADDRESS>:43065 at thread Thread-12
2016-08-04 14:40:19,363 - INFO [Kyco] Handling KycoNewConnection event
2016-08-04 14:40:19,364 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,365 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:19,366 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:19,367 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:19,367 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInHello
2016-08-04 14:40:19,368 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInHello
2016-08-04 14:40:19,368 - DEBUG [Kyco] MsgInEvent handler called
2016-08-04 14:40:19,368 - DEBUG [Kyco] Handling KycoMessageInHello
2016-08-04 14:40:19,368 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:19,368 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutHello
2016-08-04 14:40:19,369 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutHello
2016-08-04 14:40:19,369 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:19,369 - DEBUG [Kyco] Sending a FeaturesRequest after responding to a Hello
2016-08-04 14:40:19,371 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:19,371 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoMessageOutFeaturesRequest
2016-08-04 14:40:19,372 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoMessageOutFeaturesRequest
2016-08-04 14:40:19,372 - DEBUG [Kyco] MsgOutEvent handler called
2016-08-04 14:40:19,374 - DEBUG [Kyco] New message from <IP_ADDRESS>:43065 at thread Thread-12
2016-08-04 14:40:19,374 - INFO [Kyco] Stopping Kyco
2016-08-04 14:40:19,374 - DEBUG [Kyco] Reading the binary_data
2016-08-04 14:40:19,375 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,375 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:19,375 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoRawOpenFlowMessage
2016-08-04 14:40:19,376 - DEBUG [Kyco] Client <IP_ADDRESS>:43065 disconnected
2016-08-04 14:40:19,380 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:19,380 - DEBUG [Kyco] Connection lost from <IP_ADDRESS>:43065
2016-08-04 14:40:19,380 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoMessageInFeaturesReply
2016-08-04 14:40:19,380 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,381 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoMessageInFeaturesReply
2016-08-04 14:40:19,381 - DEBUG [Kyco] [buffer: raw_event] Added: KycoConnectionLost
2016-08-04 14:40:19,381 - DEBUG [Kyco] MsgInEvent handler called
2016-08-04 14:40:19,382 - DEBUG [Kyco] Handling KycoMessageInFeaturesReply Event
2016-08-04 14:40:19,382 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoConnectionLost
2016-08-04 14:40:19,382 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:19,382 - INFO [Kyco] Handling KycoConnectionLost event
2016-08-04 14:40:19,383 - DEBUG [Kyco] [buffer: app_event] Added: KycoSwitchUp
2016-08-04 14:40:19,383 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:19,383 - DEBUG [Kyco] [buffer: app_event] Added: KycoSwitchDown
2016-08-04 14:40:19,383 - DEBUG [Kyco] [buffer: app_event] Removed: KycoSwitchUp
2016-08-04 14:40:19,384 - DEBUG [Kyco] AppEvent handler called
2016-08-04 14:40:19,384 - DEBUG [Kyco] [buffer: app_event] Removed: KycoSwitchDown
2016-08-04 14:40:19,384 - DEBUG [Kyco] AppEvent handler called
2016-08-04 14:40:19,862 - INFO [Kyco] Stop signal received by Kyco buffers.
2016-08-04 14:40:19,863 - INFO [Kyco] Sending KycoShutdownEvent to all apps.
2016-08-04 14:40:19,863 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,863 - DEBUG [Kyco] [buffer: raw_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,863 - INFO [Kyco] raw_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,864 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,864 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:19,864 - DEBUG [Kyco] RawEvent handler stopped
2016-08-04 14:40:19,865 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,865 - INFO [Kyco] msg_in_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,865 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,866 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:19,866 - DEBUG [Kyco] MsgInEvent handler stopped
2016-08-04 14:40:19,866 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,867 - INFO [Kyco] msg_out_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,867 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:19,867 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,868 - DEBUG [Kyco] [buffer: app_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,868 - DEBUG [Kyco] MsgOutEvent handler stopped
2016-08-04 14:40:19,868 - INFO [Kyco] app_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,869 - DEBUG [Kyco] [buffer: app_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,869 - INFO [Kyco] Stopping thread: MsgInEvent Handler
2016-08-04 14:40:19,869 - DEBUG [Kyco] AppEvent handler stopped
2016-08-04 14:40:19,870 - INFO [Kyco] Stopping thread: AppEvent Handler
2016-08-04 14:40:19,870 - INFO [Kyco] Stopping thread: RawEvent Handler
2016-08-04 14:40:19,870 - INFO [Kyco] Stopping thread: MsgOutEvent Handler
2016-08-04 14:40:19,871 - INFO [Kyco] Stopping thread: TCP server
ok
test_client_sending_a_message (tests.test_controller.TestKycoController) ... 2016-08-04 14:40:19,873 - INFO [Kyco] Starting Kyco - Kytos Controller
2016-08-04 14:40:19,874 - INFO [Kyco] Message In Event Handler started
2016-08-04 14:40:19,875 - INFO [Kyco] App Event Handler started
2016-08-04 14:40:19,875 - INFO [Kyco] Raw Event Handler started
2016-08-04 14:40:19,876 - INFO [Kyco] Message Out Event Handler started
2016-08-04 14:40:19,876 - INFO [Kyco] Loading kyco apps...
2016-08-04 14:40:19,876 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:19,876 - INFO [Kyco] Loading app ofcore
2016-08-04 14:40:19,976 - INFO [Kyco] Stopping Kyco
2016-08-04 14:40:19,976 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,977 - INFO [Kyco] Stop signal received by Kyco buffers.
2016-08-04 14:40:19,977 - DEBUG [Kyco] [buffer: raw_event] Added: KycoNewConnection
2016-08-04 14:40:19,978 - INFO [Kyco] Sending KycoShutdownEvent to all apps.
2016-08-04 14:40:19,978 - DEBUG [Kyco] New connection from <IP_ADDRESS>:43066
2016-08-04 14:40:19,979 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoNewConnection
2016-08-04 14:40:19,979 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,980 - DEBUG [Kyco] New message from <IP_ADDRESS>:43066 at thread Thread-16
2016-08-04 14:40:19,981 - INFO [Kyco] Handling KycoNewConnection event
2016-08-04 14:40:19,981 - DEBUG [Kyco] [buffer: raw_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,982 - DEBUG [Kyco] Reading the binary_data
2016-08-04 14:40:19,982 - INFO [Kyco] raw_event buffer in stop mode. Rejecting new events.
Exception in thread TCP server:
Traceback (most recent call last):
File "/usr/lib/python3.4/threading.py", line 920, in _bootstrap_inner
self.run()
File "/usr/lib/python3.4/threading.py", line 868, in run
self._target(*self._args, **self._kwargs)
File "/home/diraol/devel/kyco/kyco/core/tcp_server.py", line 46, in serve_forever
super().serve_forever(poll_interval)
File "/usr/lib/python3.4/socketserver.py", line 236, in serve_forever
poll_interval)
File "/usr/lib/python3.4/socketserver.py", line 154, in _eintr_retry
return func(*args)
ValueError: file descriptor cannot be a negative integer (-1)
2016-08-04 14:40:19,983 - DEBUG [Kyco] [buffer: raw_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,983 - DEBUG [Kyco] Added new event to raw_event event buffer
2016-08-04 14:40:19,984 - DEBUG [Kyco] Added new event to msg_in_event event buffer
2016-08-04 14:40:19,984 - DEBUG [Kyco] RawEvent handler stopped
2016-08-04 14:40:19,984 - DEBUG [Kyco] [buffer: raw_event] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:19,984 - DEBUG [Kyco] [buffer: msg_in_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,985 - DEBUG [Kyco] Client <IP_ADDRESS>:43066 disconnected
2016-08-04 14:40:19,985 - INFO [Kyco] msg_in_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,985 - DEBUG [Kyco] [buffer: msg_in_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,986 - DEBUG [Kyco] Connection lost from <IP_ADDRESS>:43066
2016-08-04 14:40:19,986 - DEBUG [Kyco] Added new event to msg_out_event event buffer
2016-08-04 14:40:19,986 - DEBUG [Kyco] MsgInEvent handler stopped
2016-08-04 14:40:19,986 - DEBUG [Kyco] [buffer: msg_out_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,987 - INFO [Kyco] msg_out_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,987 - DEBUG [Kyco] [buffer: msg_out_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,987 - DEBUG [Kyco] Added new event to app_event event buffer
2016-08-04 14:40:19,987 - DEBUG [Kyco] MsgOutEvent handler stopped
2016-08-04 14:40:19,988 - DEBUG [Kyco] [buffer: app_event] Added: KycoShutdownEvent
2016-08-04 14:40:19,988 - INFO [Kyco] app_event buffer in stop mode. Rejecting new events.
2016-08-04 14:40:19,988 - DEBUG [Kyco] [buffer: app_event] Removed: KycoShutdownEvent
2016-08-04 14:40:19,988 - INFO [Kyco] Stopping thread: MsgInEvent Handler
2016-08-04 14:40:19,989 - DEBUG [Kyco] AppEvent handler stopped
2016-08-04 14:40:19,989 - INFO [Kyco] Stopping thread: AppEvent Handler
2016-08-04 14:40:19,989 - INFO [Kyco] Stopping thread: RawEvent Handler
2016-08-04 14:40:19,989 - INFO [Kyco] Stopping thread: MsgOutEvent Handler
2016-08-04 14:40:19,989 - INFO [Kyco] Stopping thread: TCP server
ok
test_one_connection (tests.test_core.test_tcp_server.TestKycoOpenFlowHandler) ... 2016-08-04 14:40:19,992 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
2016-08-04 14:40:20,093 - DEBUG [Kyco] Added new event to test event buffer
2016-08-04 14:40:20,094 - DEBUG [Kyco] [buffer: test] Added: KycoNewConnection
2016-08-04 14:40:20,094 - DEBUG [Kyco] New connection from <IP_ADDRESS>:43067
2016-08-04 14:40:20,095 - DEBUG [Kyco] New message from <IP_ADDRESS>:43067 at thread Thread-17
2016-08-04 14:40:20,096 - DEBUG [Kyco] Reading the binary_data
2016-08-04 14:40:20,096 - DEBUG [Kyco] Added new event to test event buffer
2016-08-04 14:40:20,097 - DEBUG [Kyco] [buffer: test] Added: KycoRawOpenFlowMessage
2016-08-04 14:40:20,097 - DEBUG [Kyco] Client <IP_ADDRESS>:43067 disconnected
2016-08-04 14:40:20,098 - DEBUG [Kyco] Connection lost from <IP_ADDRESS>:43067
2016-08-04 14:40:20,098 - DEBUG [Kyco] Added new event to test event buffer
2016-08-04 14:40:20,098 - DEBUG [Kyco] [buffer: test] Added: KycoConnectionLost
ok
test_one_connection (tests.test_core.test_tcp_server.TestKycoServer) ... 2016-08-04 14:40:20,600 - INFO [Kyco] Kyco listening at <IP_ADDRESS>:6633
ok

Ran 7 tests in 3.696s
OK

Updating....
These exceptions were raised by the Controller, not by the "client". As it was raised by the controller, and they are not being evaluated on the tests, on the end all tests are passing.
See tests on:
tests/test_core_apps/test_ofcore.py


AutoPaste ez

what the thing im saying actually is
uhh, so when someone sends a log file or a big code thingy automatically converts the message to a pastebin thing and deletes the message. for lazy people basically or people who are on mobile or something.
its done in this C# bot, dunno if this helps or not
https://github.com/tModLoader/tModLoader-Discord-Bot/blob/rework/Services/HastebinService.cs
I've contributed to it :sunglasses:
ok thanks
also lol

What if the log is over 3000 characters

cat latest.log | tail -n 2000 | nc termbin.com 9999


Release 2022.11.15

This release adds the following PRs:

#33
#34
#35
#36

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


x/mobile: gomobile init not work

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.11.1 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build759758858=/tmp/go-build -gno-record-gcc-switches"
What did you do?
https://github.com/golang/go/wiki/Mobile
go get golang.org/x/mobile/cmd/gomobile
gomobile init   # 1 second stop
go get -d golang.org/x/mobile/example/basic
gomobile build -target=android golang.org/x/mobile/example/basic

What did you expect to see?
Compiled successfully
What did you see instead?
init Done, build took 0s.
output gomobile: no Android NDK path is set. Please run gomobile init with the ndk-bundle installed through the Android SDK manager or with the -ndk flag set.

sorry,i error think this is auto tool

My travis ci fails now and was passing before. My ndk path is set correctly but it's asking for openal. Any ideas?


Typo correction: this.config.search -> this.config.searchEnabled

The dropdown just closes when clicking on the search field which has a value filled in.
Error in action: https://www.screencast.com/t/e23Ti7eT7J.

Perfect thanks 👍


CLI Commands: honor default namespace from project

Apparently, this is a thing in project.json.
{
  "tooling": {
    "defaultNamespace": "Not.Project.Name"
  }
}

We should honor that in our commands instead of just using the project name.

Not sure where this "tooling" node came from, but it is not in the project model for CLI projects.

cc @rowanmiller since I know we had resolved a few bugs as dupes of this one. We may want to have something (maybe repurpose this issue?) to make sure we handle the equivalent scenario for tooling RTM.

Agreed, reopening and removing milestone so that we can discuss in triage

Edited title to make it non project.json specific.

This will go away as we consolidate with MSBuild

Where is the "tooling" element supposed to go in project.json? I can't seem to find any documentation on this.
Also, what version of the CLI was it first supported in?

@NightOwl888  The  .NET Core SDK 1.0.0 no longer supports project.json or Visual Studio 2015. Everyone doing .NET Core development is encouraged to migrate from project.json to csproj and Visual Studio 2017.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

I've been told (but have not confirmed) that VS 2017 and the unified .csproj file for .NET Framework/.NET Core is not fully functional yet. And I really don't have the time to migrate my 35 projects (105 different build configurations) to .csproj just to jump over a lot of other hurdles trying to develop again. So for the time being, we are sticking with the project.json file (since that is the way your Microsoft contributor set it up a few months ago).
That said, my question still applies and is not yet answered.


Ignore dynamic objects from the sharedSchema

Closes #1783.
\c @jpsim  @tgoyne

Since we don't specify Realm for any other schema-related methods (ignoredProperties/primaryKey/defaultPropertyValues), I'd prefer if this one was just called shouldPersist. Otherwise :+1:

:+1:

@jpsim the reason I made this method more verbose is that it's not exposed publicly and I wanted to limit the chances of a name collision.

:+1:


Add a Menu

Summary
Replace the button that cycles the Swadge mode with a top level menu.
Technical Spec
The OLED display is the only peripheral requirement.
This will exist as the 0th Swadge mode
UI

The menu will be a list of names with a single ">" as the cursor
The left button will cycle through the list of modes
The right button will start the selected mode
The mode change button will close the current mode and open the menu (perhaps after a delay)

How to Test
Go to the menu, enter a mode, go back to the menu, go to a different mode

Left and right buttons ended up scrolling up and down. The menu button selects the mode when in the menu and returns to the menu when held during any other mode.


SWARM-528 second part of fix - case when port properties are defined …

…in arquillian.xml

Why was this closed? By mistake?:)

It was apparently auto-closed due to a completely unrelated merge.  This is weird.
Re-opening.

@bobmcwhirter what's the status of this? can it be merged?


v1.1.3 - Google reCAPTCHA Support and Custom Redirects

Integrate Google reCAPTCHA 3.0; add shortcode attributes for custom redirection after successful form submission;

Today's update to the Develop branch included the Geolocation endpoint update in this PR.


[pref] Fix CSS textarea issue whereby the signature box was too small…

… when editing raw HTML.
Before:

After:

Is there something wrong with my commit?


10.0.17134.1 need help

require windows 10 10.0.1734.1 rdpwrap.ini,please help me,thank you

termsrv.zip

Please, rename your issue to 10.0.17134.1 and fix RDPConf screenshot.

Offsets here: https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini

Thanks a lot !!!

PLEASE help me , Remote access to my computer from another computer, display other accounts, log in with account password and report password error .   that account belongs to administrator

termsrv.zip

PLEASE help me , Remote access to my computer from another computer, display other accounts, log in with account password and report password error . that account belongs to administrator

@sebaxakerhtc Is this offsets correct?

Duplicate of https://github.com/stascorp/rdpwrap/issues/690

Is this offsets correct?

Yes, i think so.
It's an old build. If the offsets are wrong - we should have an information


Comments counter testing using jest

Introduced Changes

Created a comments-counter.test.js file for adding unit test cases to check the countComments method.

Added three test cases,

Case 1: 5 comments present
Case 2: 1 comment present
Case 3: No comments present

All test cases passed with 100% coverage.

Excluded the coverage folder from the stylelint linters.

Task Implemented:

[x] #5

Great job on this side of the project Tanmayi.
Just one little suggestion:

It would look better if you reduce the size of the image in the popup for the comment section.


Add basic documentation

At the very least, I should have some description of the package in the README. However, it'd be worth spending some time playing around with Sphinx and readthedocs to see if I can build out something more extensive in a relatively quick/semi-automated manner.

Started working on this with #71; filled in docs and tweaked config leading up to v0.3.0


fix(language-core): correct type inference of defineModel & defineEmits in generic

fix #4822

Hello,
Can you please consider accepting this PR ?
I can't upgrade to Vue 3.5 otherwise (see https://github.com/vuejs/core/issues/11866).
Thank a lot !

LGTM, thanks for the hard work!


Remove dependency on [Target] and instead operate on [Architecture]

The dart-lang/native repository contains a Target class that is almost not needed anymore. The remaining uses are mainly due to kernel asset mapping (which we may be able to remove in the future).
This PR removes usages of that Target (in favor of Architecture) class in most places in flutter tools.
This makes the code also cleaner because we no longer have an implicit assumption that
a List<Target> all belong to the same operating system.

Thanks, @dcharkes !


Add support for multiple disks resources

Disk source should also be checked. Otherwise it will cause a mistaken resource comparison when using multiple disks.

Coverage decreased (-0.2%) to 52.448% when pulling 8dc5789764c557ed1898b98ce94f586b01e396b9 on everpcpc:disk into 464c8d6a7d891b5f7695e6a6e78c6e3974223db4 on mesos:master.

Thanks for the PR! Would you mind fleshing out TestResources_PersistentVolumes or else writing a new unit test to exercise this new code?

Coverage decreased (-0.1%) to 52.49% when pulling 7cdc264f7b5250b5394526b11856c3cee46dd539 on everpcpc:disk into 464c8d6a7d891b5f7695e6a6e78c6e3974223db4 on mesos:master.

Hi, I've put the tests in TestResources_Equivalent.

Coverage decreased (-0.1%) to 52.51% when pulling 46ddaa4b1bf2c75dbc26ac7998d6e03a8980ed22 on everpcpc:disk into 464c8d6a7d891b5f7695e6a6e78c6e3974223db4 on mesos:master.

thanks, lgtm


Interstistial ad always load on mounted even loadOnMounted = false ??

I try to load interstitial ad on onPress evets but ads are always loaded on mounted. Check my code below
import { useInterstitialAd, TestIds } from '@react-native-admob/admob';

const App = () => {
    const { adLoaded, load} = useInterstitialAd(TestIds.INTERSTITIAL, {
      requestOptions: {
          loadOnMounted: false, // i am not loading ad on mounting
          loadOnDismissed: false
      },
    });

    useEffect(() => {
        if (adLoaded) {
          console.log("Loaded")   /// i never call the load function but still the add is loaded why?????
        }
    },[adLoaded])

   /* rest of the code*/
}

How to resolve this now????
Thanks.

I checked in example app but did not found the case. Can you show the part how you load the ad?

Your option object is wrong. It should be:
{
  loadOnMounted: false,
  loadOnDismissed: false
}

Your option object is wrong. It should be:
{
  loadOnMounted: false,
  loadOnDismissed: false,
  requestOptions:{
    //...
  },
}

They should be declared outside of the requestOptions object.

My bad, thank you its working now.


Move save css button to right

Confirm buttons in spotify are generally on the right I think

Fixed in 8978785


Add support for "Datasource Permissions" API

Description
Add support for "Datasource Permissions" API
Checklist

[x] The patch has appropriate test coverage
[x] The patch follows the style guidelines of this project
[x] The patch has appropriate comments, particularly in hard-to-understand areas
[x] The documentation was updated corresponding to the patch
[x] I have performed a self-review of this patch

Excellent. Thank you very much.


Add Bitcoin Transcripts section

I have put placeholders where I think the section should refer back to previous newsletters but I haven't actually set up those links. Still figuring out how you do those. If you could let me know I'll make sure the links actually work in future months :)

To create links to specific parts of previous newsletters, we usually just click the hyperlink-blue bullet next to the specific item.  E.g.:

That will give you the anchor link.  Just turn it from an absolute URL (https://bitcoinops.org/foo/bar) into a relative URL (/foo/bar) so that it works correctly in localhost previews and gets checked by our internal link checker.
You don't need to worry about that for this month, I'll turn your placeholders into links for this PR.
I gave the content a quick skim and it LGTM, thanks!  I'll edit it shortly and merge it into the main PR.

Merged into the main PR with minimal content edits (just formatting).  Great section this month, thanks Michael!


SymfonyLockAdapter throws Exception with wrong information

Please see
https://github.com/GoogleCloudPlatform/google-cloud-php/blob/master/Core/src/Lock/SymfonyLockAdapter.php#L63
The code block for catching and throwing the error looks like below
throw new \RuntimeException($ex->getMessage());

This tells me almost nothing about the actual exception that was thrown.
Is there a reason why it's handled this way?

There's no good reason we can't add more detail to the exception here, we'll get that fixed soon.


WECHATY_PUPPET_HOSTIE_TOKEN

WECHATY_PUPPET_HOSTIE_TOKEN这个在哪获取？启动总是报错：cannot get ip by token, check token

Please refer to https://github.com/wechaty/wechaty/issues/1986

Please refer to wechaty/wechaty#1986
Here's the FAQ for Wechaty Puppet Service Providers: wechaty/puppet-service-providers#1

好的 谢谢

You are welcome!

已解决


Silence JavaScript preprocessor deprecation warning on Ember 2.12

As of Ember 2.12 the addon started triggering the following deprecation warning:
DEPRECATION: Addon files were detected in `.../node_modules/ember-data-factory-guy/addon`, but no JavaScript preprocessors were found for `ember-data-factory-guy`.
Please make sure to add a preprocessor (most likely `ember-cli-babel`) to in `dependencies` (NOT `devDependencies`) in `ember-data-factory-guy`'s `package.json`.

Thanks for this one .. slipped by me. Good catch. :)

https://github.com/danielspaniel/ember-data-factory-guy/releases/tag/v2.12.1  has fix


Added search_as_you_type value in ELASTICSEARCH_TYPES

Please merge this as search_as_you_type is supported in elasticsearch field types. https://www.elastic.co/guide/en/elasticsearch/reference/current/search-as-you-type.html

Hi, Should we add additional types here? I do have the same case for range types.
I need to be able to add an integer_range type

Hi, Should we add additional types here? I do have the same case for range types. I need to be able to add an integer_range type

Feel free to add as needed