Split wasmstation into separate crates for web support.

Wasmstation in WebAssembly isn't really very difficult to create at this point, if this PR is merged I think I can complete it this weekend. I tried to keep this PR small, but really there's not much I can do when it moves most source files in the repo around and renames packages. All tests pass and it is just as successful with wasm4-test-cart.
Here are my intentions for the crates created in this PR:

crate wasmstation-core - The core WASM-4 types, functions, and constants in all wasmstation programs. Extremely fast and robust: polished, no panics, no platform-specific code, minimal/no heap allocations.
crate wasmstation-desktop - Desktop-specific renderer (e.g. launch). In the future this can have simple flags like sdl2 and wgpu.
crate wasmstation-wasmer - The default Backend for wasmstation-desktop (maybe it should be re-exported by wasmstation-desktop?).

and soon:

crate wasmstation-web - Includes fn launch_on_canvas(backend: impl Backend, id: &str) and struct WebBackend.

Changes:

wasmstation::renderer has been moved to the wasmstation-desktop crate. SDL2 is the most platform-specific dependency and it is only used here, so I'd like to separate it from the other pieces of code.
wasmstation::backend::wasmer has been moved to the wasmstation-wasmer crate, mainly because it requires heavy usage of libstd.
wasmstation has been renamed to wasmstation_core.
wasmstation::console has been moved to the crate root of wasmstation_core.
Removed #![allow(unused_variables, dead_code)] - I understand why you might want to add this at the beginning of a project when you're adding incomplete features, but this allow rule kept in a lot of dead and unused code. Fixing these warnings made me do a few things:

Tests in individual wasmstation::console::framebuffer::foo::tests modules and related data types have been moved to wasmstation_core::framebuffer::tests.

This was done because about half the things in wasmstation::console::framebuffer were solely for tests (e.g. ArrayScreen, as_fb_vec variants).
This also improves general readability quite a bit 😄.

Some struct fields and variables were changed to _foo instead of foo because they weren't used anywhere in the crate (and they weren't related to any public interfaces). I want to remove these types of thing in a future PR but I've silenced the error here so I can get as much done in as little controversy.

Workspace default values. This enables us to only use a single bytemuck/log/anyhow version and edition/license/repository metadata across the workspace for compatibility.
Add MemoryViewSource in wasmstation_wasmer because Source is no longer implemented in the same crate as WasmerBackend. This is something that I probably should have done in preparation for this during #42.
Fix some basic "uncontroversial" clippy lints such as:

for loop => enumerated iter in Source::items_at
mem::swap instead of "variable musical chairs" in line.
Unnecessary &s and explicit returns.
impl Default => #[derive(Default)]
etc. etc. etc.

Standardize some documentation.

Sounds good, thanks for pointing out some dead code 👍🏽. I didn't want to remove some of those values in fear that they would inadvertently break something that I didn't write.


[Improvement][MLedger]Modernizer managed ledger

Master Issue: https://github.com/apache/pulsar/issues/12271
Motivation
Apply modernizer-maven-plugin maven plugin to encourage the use of modern & JDK builtin APIs.
Modifications
Add modernizer-maven-plugin plugin to managed-ledger module and fix violation by upgrading to suggested APIs.
Verifying this change

[x] Make sure that the change passes the CI checks.
No real change to functionality, covered by existing unit tests.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

[x] doc-not-needed
No public client related changes.

LGTM. Interesting patch and the movement :)
I like linters to help the codebase style consistent and this plugin additionally avoid continue using deprecated methods.


Added Wordpress version 6.15.0.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I need to do some serious bug fixing on my script. Thanks for catching this.


FFMPEG utilize GPU

telly release with the issue:
telly, version <IP_ADDRESS> (branch: dev, revision: 96424a4719f33de9c1b66d8d2186e0452e45a234)
build user:       root@7abd9a6a6502
build date:       20200704-05:23:36
go version:       go1.12.17
Last working telly release (if known):
Operating environment (Docker/Windows/Linux/QNAP, etc.):
Ubuntu 20.04 (LXC)
Description of problem:
When use FFMpeg = true in the config file it properly uses FFMPEG but it does not utilize any available GPU.  The FFMPEG that I have from build does have proper utilization of NVIDIA GPU.
Contents of telly.config.toml [if you're using a version above 1.1]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

FFMpeg = true

Command line used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

Docker run command used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

telly or docker log:

Additional information:

telly just invokes ffmpeg with some flags; can the GPU be enabled with some flags?


Overscrolling when an element is hidden in the app

Working on an app with ember-cloaking – while the defaultHeight is set to 55px, we're seeing some weird behavior when we really aggressively scroll (like 2/3 down the page). We have a table list of items (just divs, basically), and some of them are hidden until they're enabled via a button in the UI. When we scroll really far down the page, the items load, but then the page starts to scroll up on its own a variable amount.
My guess here is that having rows that are "hidden" (a height of 0px) but still in the DOM is messing with the height calculations in some way. Any ideas?

I did a bit more research on here and I'm still not really sure what the right solution is. I think part of the problem is that ember-cloaking wraps the actual itemView used for the cloaked elements in its own view; if that view exists at all, we have problems. Is there a point where I can plug in from inside the app to stop the wrapper views from rendering at all?
I should've mentioned in the original comment that when all the rows are shown (no zero-height elements), the scrolling works flawlessly. So this is definitely related to having zero-height elements.

The wrappers are necessary for the way it works, as elements are replaced with the height of the content they cloaked. Why are rows hidden at 0px and not their original height?

So the template would look like:
{{#if canDisplay}}
  {{ (dom stuff here) }}
{{/if}}

This is what causes the 0px row. What would you suggest as a better way of implementing this? I have a custom view that handles each row – should I be setting isVisible on there instead?

Hmm that's an interesting use case. I am not sure what the correct answer would be. If elements can be swapped in/out that will definitely affect scrolling.

We resolved this by moving all the logic out of the template!


[BUG] Many Grok failures do not tag events

Describe the bug
There are several exceptions which the grok processor catches that do not tag the event.
To Reproduce
Run a pipeline with a grok pattern than times out. The event is not tagged.
Expected behavior
I expect that any failure to match will result in a tag.

We will support this by a new tags_on_timeout configuration in the grok processor.


added: ImHashMap (C#) from https://www.nuget.org/packages/ImTools/1.0.0-preview-01

Outperforms by 2x for <= 1000 items

Hi. Thanks for your submission. I have updated the charts with the new data now as well.


remove unused argument in trigger

This is a small optimization trick, using an unused argument to avoid writting the word "var". But more clarity in the code trump a couple of bytes for sure


Add syntax highlighting to posts

Is your feature request related to a problem? Please describe.
No, just a lacking feature. Would love to have code blocks highlights on posts 😁

Describe the solution you'd like
I would like to have formatted markdown on posts

Describe alternatives you've considered
Code blocks, bold and italic would be a great start.

Additional context

I would like to see it too! Looks like there's a similar issue, #4750.
I am not very experienced with rendering markdown in React but react-remark seems to accomplish this task well.
Also, I want to point that adding markdown support in a social media would require a WYSIWYG editor to be used by all users.

If I remember well, rendering shiki in such a level can bring performance issues but it still can be done 😁

+1 this would be amazing

Paul Frazee wrote about this text formatting issue, "Why RichText facets in Bluesky", so I guess we won't get the markdown support. However, it would be really nice to have bold, italic and syntax highlight at least!

I can even code it using react-remark if needed 💖

Paul Frazee wrote about this text formatting issue, "Why RichText facets in Bluesky", so I guess we won't get the markdown support. However, it would be really nice to have bold, italic and syntax highlight at least!

This changes everything. There are valid reasons to not use it then. I agree with the linked post's arguments.

+1 this would be amazing

+1 This feature will be awesome

+1 This so cool!!

Paul Frazee wrote about this text formatting issue, "Why RichText facets in Bluesky", so I guess we won't get the markdown support. However, it would be really nice to have bold, italic and code blocks at least!

Code blocks seem nice, but very limiting in 300 characteres.
Maybe it would be nice to have a way of "attaching" code, the same way we attach pictures. It would not be limited by the 300 characters, and it would be more accessible than a screenshot.

+1 this is awesome!

I think that it should be a code snippet, the same way that slack does.
In a sense, it's just attaching a file to a post (on a different format from a video or a photo). I don't know how files work inside of Bluesky, but i think it would be the easiest implementation.
And the character limit wouldn't be an issue

Paul Frazee wrote about this text formatting issue, "Why RichText facets in Bluesky", so I guess we won't get the markdown support. However, it would be really nice to have bold, italic and code blocks at least!

Point from the article, though: You can do Markdown in the post field, you just parse it into facets before transmitting it.


Improve typography styles system

Put all typography styling in a single stylesheet
Move google fonts loading from HTML to sass @import

Won't do. The current system is better.


Enhance AAD privileged access including PIM for Groups and Least privilege policy check

Description
This epic is about enhancing the ScubaGear AAD policies pertaining to highly privileged access (section 7).
AAD Policy enhancement issues:

#755
#376
#756
#757
#548

Goal
The goal is to improve the AAD secure configuration baseline by including Microsoft functionality PIM for Groups into the baseline.
Hypothesis
By improving the set of AAD highly privileged access policies, ScubaGear can be made more usable and relevant to real-world tenants.  This hypothesis can be tested by collecting feedback from agencies and running the tool internally against tenants in which these roles are implemented to support a range of users and missions.
Acceptance criteria
Criteria that are considered must have for feature launch and in-scope for this epic include:

[ ] All linked issues have been completed

Closes #697 as completed.


Verify api reference generation

Verify documentation generation with doxygen. Try https://github.com/UglyToad/PdfPig as an example.

Duplicate of #411


[server][chore]: drop dead code

Notes for Reviewers
There are some unused functions lurking around in the code base.
Their references were removed somewhere between v0.6.90 and v0.6.91 release https://github.com/meshery/meshery/compare/v0.6.90...v0.6.91
This PR fixes #
Signed commits

[x] Yes, I signed my commits.

Thanks for cleaning up, @VihasMakwana.
I wonder if we are removing an API that we intend to support. Is this graphql api for resetting the database not exposed or not connected to a resolver?
is it only the REST API for resetting the database that is functional?

Hard reset is done via graphql. The API I removed was to persist the data received by meshsync. And it is not connected to any resolver.
The persisting is done via https://github.com/meshery/meshery/blob/master/server/models/meshsync_events.go#L54-L77.

If they both have the same behavior, even though the Meshery UI as a client may not be using this graph API, we may want to leave it available for other client’s use.
I believe that mesheryctl is only using the REST API, so I don’t think it’s of concern.
As an extensible platform, we tout the fact that we support both choice of REST and GraphQL for system to integrate with Meshery.

I see. Makes sense.

Hey @VihasMakwana  Let's discuss this on Meshery Development Meeting today at 8:30 PM IST / 9 AM Central time. Please add this as an agenda item in the meeting minutes.

Excellent 🙂


Using VictoriaMetrics leads Connection reset by peer after 2 minutes

Describe the bug
Using VictoriaMetrics leads Connection reset by peer after 2 minutes.
To Reproduce
Steps to reproduce the behavior:

krr simple --verbose --prometheus-url https://vmselect.test.com/select/0/prometheus
See error:

During handling of the above exception, another exception occurred:

╭─────────────────────────────── Traceback (most recent call last) ────────────────────────────────╮
│ /Users/furkan.turkal/robusta_krr/core/runner.py:202 in run                                       │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/robusta_krr/core/runner.py'           │
│                                                                                │
│ /Users/furkan.turkal/robusta_krr/core/runner.py:177 in _collect_result                           │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/robusta_krr/core/runner.py'           │
│                                                                                │
│ /Users/furkan.turkal/robusta_krr/core/runner.py:138 in _gather_objects_recommendations           │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/robusta_krr/core/runner.py'           │
│                                                                                │
│ /Users/furkan.turkal/robusta_krr/core/runner.py:113 in _calculate_object_recommendations         │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/robusta_krr/core/runner.py'           │
│                                                                                │
│ /Users/furkan.turkal/robusta_krr/core/integrations/prometheus/loader.py:97 in gather_data        │
│                                                                                │
│ [Errno 2] No such file or directory:                                                             │
│ '/Users/furkan.turkal/robusta_krr/core/integrations/prometheus/loader.py'                        │
│                                                                                │
│                                     ... 6 frames hidden ...                                      │
│                                                                                │
│ /Users/furkan.turkal/requests/sessions.py:635 in post                                            │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/requests/sessions.py'                 │
│                                                                                │
│ /Users/furkan.turkal/requests/sessions.py:587 in request                                         │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/requests/sessions.py'                 │
│                                                                                │
│ /Users/furkan.turkal/requests/sessions.py:745 in send                                            │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/requests/sessions.py'                 │
│                                                                                │
│ /Users/furkan.turkal/requests/models.py:899 in content                                           │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/requests/models.py'                   │
│                                                                                │
│ /Users/furkan.turkal/requests/models.py:818 in generate                                          │
│                                                                                │
│ [Errno 2] No such file or directory: '/Users/furkan.turkal/requests/models.py'                   │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
ChunkedEncodingError: ("Connection broken: ConnectionResetError(54, 'Connection reset by peer')", ConnectionResetError(54, 'Connection reset by peer'))

Expected behavior
Maybe worth adding some resiliency with retries and timeouts.
Screenshots
-
Desktop (please complete the following information):

OS: macOS
Browser -
Version v1.4.0

on 0: [INFO] Prometheus connected successfully for kubernetes-admin@foo cluster
Calculating Recommendation |                                        | █▆▄ 0/111 [0%] in 1:38 (~0s, 0.0/s)

2mins passed but it seems progress bar get stuck. 🤔

Could you please send me the full log with verbose mode?


Upgrading Mysql single server v8 to a newer version

Is there an ability to perform some sort of out of band upgrade for a mysql single server instance from 8.0.15 version to 8.0.16 or later?
We are aware of the need to move to flexible server service, issue is we are in need of support to Azure AD in order to proceed with that path

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a5a1f81c-0ec7-c0f0-b920-de84a9d0d60e
Version Independent ID: 379fc07b-105d-e159-548a-76ebf85a5f2f
Content: Version support policy - Azure Database for MySQL - Single Server and Flexible Server
Content Source: articles/mysql/concepts-version-policy.md
Service: mysql
Sub-service: single-server
GitHub Login: @sr-msft
Microsoft Alias: srranga

Hi @assaf-grth,
Thanks for your feedback. We are looking into this and will update as appropriate.

Hi @@sr-msft,
Could you please look into this request. Thanks

Hi @shaktisingh-msft @sr-msft any updates on this?

Hi Parikshit Savjani,
Could you please look into this issue as it is related to MySql server. Thanks

it's now GA - https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-azure-ad


[fix bug 746795] Add multiple curators per group.

@glogiotatidis @johngian r? pretty please?

I did a very quick pass that should not be considered a full code review due to limited time. If time allows and this is still open I'll re-review later this week.

This PR might need rebase and change in migrations after #1268

Tests are failing.

Creating a new group doesn't automatically add me as a curator nor as a group member.

@johngian pr updated

Tests are failing.

GroupFactory needs some compatibility work. In the past groups created using factory had a curator assigned, now this is None.

I am getting local variable 'created' referenced before assignment when removing the last curator.

Probably you just need to update your branch

Groups can end up with no curator.

Tested it locally:

Creating a new group with multiple curators
Removing curators

and works OK.

r+wc


Imports in Webpack

Using https://github.com/johnpapa/event-view as a guide, I've tried implementing this in my project which uses webpack. However the import statement doesn't work
import {
  InMemoryBackendConfig,
  InMemoryBackendService,
  SEED_DATA
} from 'angular2-in-memory-web-api/core';

Console Output
bootstrap d05bac4…:50 Uncaught ReferenceError: System is not defined
The offending line is https://github.com/angular/in-memory-web-api/blob/master/core.js#L1
The workaround for webpack is just to use the import from 'angular2-in-memory-web-api/src/core'.
It might be worth changing this to be consistent with most other ng2/typescript libraries.

@foxandxss?

So the problem in here is that Webpack 1 doesn't talk "System.js" (Webpack 2 will).
The transpiled source won't work with Webpack so as @jhuntoo said, the workaround is to directly load from the source (which is not really a bad idea).
What the other libraries are doing is just using commonjs and that will work with any solution.

Fixed by PR #5


broken links from CD docs to PL docs

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

fixing broken links

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


harden against empty arrays in DL responses

I've been told that if an array field exists we don't need to check if it's an array, but we should check that it has elements. In other words:
if (message.attachments)                 HandleAttachment(message.attachments[0])
should become:
if (message.attachments && message.attachments.length > 0)                 HandleAttachment(message.attachments[0])
but we don't need to do:
if (message.attachments && message.attachments.isArray() && message.attachments.length > 0)                 HandleAttachment(message.attachments[0])
One possible approach is to clean this up on intake inside DirectLine().

I fixed as many of these as I could find. We could use more test cases.


fix bug in the reading from oracle clob

OCILobGetLength and OCILobRead for character LOBs (CLOBs, NCLOBs) uses the number of characters, not bytes. So, there is a bug with buffer array sizing

Is the switch to using a callback really needed? If the problem is really just a wrong byte count, couldn't we multiply (divide?) the length by whatever to fix it?

If we should avoid the callback we can try  OCILobRead2
How to know the multiplier ?

Also, it would be tremendously helpful if you could please add a unit test checking for this problem, i.e. failing now and passing with this fix. Could you please do this? TIA!

Ok

In fact, the same problem happens with a plain VARCHAR2() too, not just CLOB, so even if there is a problem with count mismatch for CLOBs, it's clearly not the only problem here.
I don't know anything about charsets in Oracle, but it looks like we need to specify that we're using UTF-8 somehow. It's pretty weird that this doesn't work out of the box, even though NLS_CHARACTERSET database parameter is set to AL32UTF8 and it would be nice to understand what's going on here, but I'm pretty sure that this PR is not the right solution for the problem, whatever it is.

In fact, the same problem happens with a plain VARCHAR2() too, not just CLOB, so even if there is a problem with count mismatch for CLOBs, it's clearly not the only problem here.

There are no problems with varchar2, export NLS_LANG is required on client session

I don't know anything about charsets in Oracle, but it looks like we need to specify that we're using UTF-8 somehow. It's pretty weird that this doesn't work out of the box, even though NLS_CHARACTERSET database parameter is set to AL32UTF8 and it would be nice to understand what's going on here, but I'm pretty sure that this PR is not the right solution for the problem, whatever it is.

I have changed oracle.sh to use utf-8 encoding

Thanks, I forgot about NLS_LANG weirdness. However I still don't think this has anything to do with using callback — does the (simpler) solution in #1184 work for you or do you still see any problems with it and, if so, how can they be reproduced?

Thanks, I forgot about NLS_LANG weirdness. However I still don't think this has anything to do with using callback — does the (simpler) solution in #1184 work for you or do you still see any problems with it and, if so, how can they be reproduced?

What is the advantage of using a self-made loop over an oci internal loop with the callback?
However, I won't insist on my solution. What matters to me is resolving the bug

What is the advantage of using a self-made loop over an oci internal loop with the callback?

I think using both the buffer and the callback is confusing, if the OCI really doesn't allow to do without the buffer in this case, I'd rather avoid defining the callback.
I don't know if the behaviour is the same with OCILobRead2(), maybe we could make things simpler using it, but I didn't have time to try it.


Fix source dist testing

When testing the source distribution install, only install noisepy from source. Installing all from source it's unnecessary and more unstable. E.g. recently hatchling==1.18.0 was failing to install from source.
The change to gen_req.py is opportunistic since it was missed in the last AWS PR and is only used in dev testing.

Codecov Report
Patch and project coverage have no change.

Comparison is base (2c22fef) 58.70% compared to head (451ae53) 58.70%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #219   +/-   ##
=======================================
  Coverage   58.70%   58.70%
=======================================
  Files          32       32
  Lines        3819     3819
  Branches      528      528
=======================================
  Hits         2242     2242
  Misses       1465     1465
  Partials      112      112

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


add new extensions configuration

Should we go ahead and add an url attribute?

Let's wait until we think more about how we are going to support external URLs

I created an issue for this effort: https://github.com/kiali/kiali/issues/7485


Cleanup alarm state - stalled chain

After the chain has been stalled (not producing blocks for more than 10 minutes), and the chain has been restored, the notification is still marked active.
Observed with Terra2 testnet upgrade today. Chain was waiting for 2/3 quorum for a couple of hours, alarm was raised as expected after 10 min. But does not invalidate the state, even after restart of Tenderduty.
10:50:29 PM - 📂 restored %s alarm state - dashboard stalled: have not seen a new block on pisco-1 in 10 minutes
Expected: Automatic alarm state cleanup, IF the chain is producing again AND the validator participates in voting/proposals as expected.

Still seeing this issue on v2.2.0


How are the test scores in cv_results_ and best_score_ calculated?

I'm using BayesSearchCV to optimise an XGBoost model to fit some data I have. While the model fits fine, I am puzzled by the scores provided in the diagnostic information and am unable to replicate them.
Here's an example script using the Boston house prices dataset to illustrate my point:
from sklearn.datasets import load_boston

import numpy as np
import pandas as pd

from xgboost.sklearn import XGBRegressor

from skopt import BayesSearchCV
from skopt.space import Real, Categorical, Integer
from sklearn.model_selection import KFold, train_test_split

boston = load_boston()

# Dataset info:
print(boston.keys())
print(boston.data.shape)
print(boston.feature_names)
print(boston.DESCR)

# Put data into dataframe and label column headers:

data = pd.DataFrame(boston.data)
data.columns = boston.feature_names

# Add target variable to dataframe

data['PRICE'] = boston.target

# Split into X and y

X, y = data.iloc[:, :-1],data.iloc[:,-1]

# Split into training and validation datasets

X_train, X_val, y_train, y_val = train_test_split(X, y, test_size=0.2, random_state=42, shuffle = True)

# For cross-validation, split training data into 5 folds

xgb_kfold = KFold(n_splits = 5,random_state = 42)

# Run fit

xgb_params = {'n_estimators': Integer(10, 3000, 'uniform'),
			   'max_depth': Integer(2, 100, 'uniform'),
			   'subsample': Real(0.25, 1.0, 'uniform'),
			   'learning_rate': Real(0.0001, 0.5, 'uniform'),
			   'gamma': Real(0.0001, 1.0, 'uniform'),
			   'colsample_bytree': Real(0.0001, 1.0, 'uniform'),
			   'colsample_bylevel': Real(0.0001, 1.0, 'uniform'),
			   'colsample_bynode': Real(0.0001, 1.0, 'uniform'),
			   'min_child_weight': Real(1, 6, 'uniform')}

xgb_fit_params = {'early_stopping_rounds': 15, 'eval_metric': 'mae', 'eval_set': [[X_val, y_val]]}

xgb_pipe = XGBRegressor(random_state = 42,  objective='reg:squarederror', n_jobs = 10)

xgb_cv = BayesSearchCV(xgb_pipe, xgb_params, cv = xgb_kfold, n_iter = 5, n_jobs = 1, random_state = 42, verbose = 4, scoring = None, fit_params = xgb_fit_params)

xgb_cv.fit(X_train, y_train)

After running this,  xgb_cv.best_score_ is 0.816, and xgb_cv.best_index_ is 3. Looking at xgb_cv.cv_results_, I want to find the best scores for each fold:
print(xgb_cv.cv_results_['split0_test_score'][xgb_cv.best_index_], xgb_cv.cv_results_['split1_test_score'][xgb_cv.best_index_], xgb_cv.cv_results_['split2_test_score'][xgb_cv.best_index_], xgb_cv.cv_results_['split3_test_score'][xgb_cv.best_index_], xgb_cv.cv_results_['split4_test_score'][xgb_cv.best_index_])

Which gives:
0.8023562337946979,
 0.8337404778903412,
 0.861370681263761,
 0.8749312273014963,
 0.7058815015739375

I'm not sure what's being calculated here, because scoring is set to None in my code. XGBoost's documentation isn't much help, but according to xgb_cv.best_estimator_.score? it's supposed to be the R2 of the predicted values. Anyway, I'm unable to obtain these values when I manually try calculating the score for each fold of the data used in the fit:
# First, need to get the actual indices of the data from each fold:

kfold_indexes = {}
kfold_cnt = 0

for train_index, test_index in xgb_kfold.split(X_train):
    kfold_indexes[kfold_cnt] = {'train': train_index, 'test': test_index}
    kfold_cnt = kfold_cnt+1

# Next, calculate the score for each fold
for p in range(5): print(xgb_cv.best_estimator_.score(X_train.iloc[kfold_indexes[p]['train']], y_train.iloc[kfold_indexes[p]['train']]))

Which gives me the following:
0.9953058342929344
0.9954795401877629
0.995066439221176
0.9950907019868662
0.995765389875457

How is BayesSearchCV calculating the scores for each fold, and why can't I replicate them using the score function? I would be most grateful for any assistance with this issue.
(Also, manually calculating the mean of these scores gives: 0.8156560..., while xgb_cv.best_score_ gives: 0.8159277... Not sure why there's a precision difference here.)

I tried fitting a new XGBoost model for each fold of data using the same parameters as xgb_cv.best_estimator_:
xgb_best_params = xgb_cv.best_estimator_.get_xgb_params()

for p in range(5):

	xgb_temp = XGBRegressor(**xgb_best_params)

	xgb_temp.fit(X_train.iloc[kfold_indexes[p]['train']].values, y_train.iloc[kfold_indexes[p]['train']].values)

	xgb_cv_scores_emu[p] = xgb_temp.score(X_train.iloc[kfold_indexes[p]['test']].values, y_train.iloc[kfold_indexes[p]['test']].values)

This gives me values that are much closer to the original CV scores, but they are still not exactly the same:
0.81142551,
0.82771065,
0.87877982,
0.88612015,
0.70819454

Why would there still be a discrepancy if the exact same folds and parameters are used? Is BayesSearchCV doing something else with XGBoost inside the fitting process that I'm not aware of, or is this an issue with precision?

I tried replacing BayesSearchCV with sklearn's RandomizedSearchCV, and I my problem disappears when fitting for 5 CV folds. So it would seem that BayesSearchCV is the issue here.
However, when I tried using 2 CV folds, I found that the 2nd fold's score was different as before, so does that mean that there is something wrong with XGBoost instead? Why would this produce two different scores when provided the exact same parameters, data, and random seeds each time?

Hello @JSAnandEOS! I am having a similar issue myself. I too believe there is some kind of issue with the results of best_score_. In my use case, I aim at scores on the order of e-12 but best_score_ is in the order of e-6 which suggests it should be doing awfully but test score and train score are on e-12. In my case, I pass a scorer function. The only alternative I can think of is that there is a modification of the scoring values being performed somewhere internally, something close to a sqrt() maybe?

BayesSearchCV had been recently revamped. Make sure you're testing with the git master rather than the currently released version.

@kernc I am using the git master version.


Exception chaining/cause not mirrored into Python

Both Python and Java have exception chaining (Throwable.getCause() in Java, exception.__cause__ in Python).
This information doesn't make it across from Java to Python though. Take the following snippet:
import jpype as jp
jp.startJVM()

java = jp.JPackage('java')
e1 = java.lang.RuntimeException("Some parent exception")
e2 = java.lang.RuntimeException("Some message", e1)

When we inspect the object:
>>> print(e2.__cause__, e2.__context__)
None None

>>> raise e2
Traceback (most recent call last):
  File "/home/pelson/github/jpype/jpype/support/exception_cause.py", line 19, in <module>
    raise e2
java.lang.RuntimeException: java.lang.RuntimeException: Some message

By adding the exception to __cause__ (via e2.__cause__ = e1) we get an improved exception:
java.lang.RuntimeException: java.lang.RuntimeException: Some parent exception

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

Traceback (most recent call last):
  File "/home/pelson/github/jpype/jpype/support/exception_cause.py", line 19, in <module>
    raise e2
java.lang.RuntimeException: java.lang.RuntimeException: Some message

In investigating this, I also wondered if I could pass a Python exception as a cause for a Throwable, but unfortunately that wasn't possible:
>>> e1 = ValueError('foo')
>>> e2 = java.lang.RuntimeException("Some message", e1)

TypeError: No matching overloads found for constructor java.lang.RuntimeException(str,ValueError), options are:
	public java.lang.RuntimeException()
	public java.lang.RuntimeException(java.lang.String)
	public java.lang.RuntimeException(java.lang.String,java.lang.Throwable)
	public java.lang.RuntimeException(java.lang.Throwable)

I'm not sure on the practicalities, but it would be also interesting if we could make BaseException be understood as a Throwable.

The Python exception system is mostly hardcoded which makes extensions of it very complicated.   You can see the level of hacking that was required to get the stack frames to connect to each other.   I have some outstanding tickets with the Python developers regarding providing methods to connect the two together but as I can't contribute to Python (seeing as my employer refuses to sign the contributor agreement) I remain stuck.
As for __cause__ that may be possible, if that field is not part of the hard coding.   My main concern is that I use the __cause__ field when chaining on from Python to Java.   But I would need to look more closely to see if the Java wrapper can override that field.   The unfortunate side effect of the way that Python has implemented this, is that even if I were to make __cause__ to be the correct value when probed, the Python exception printer ignores user side code and simply goes to the hard coded slot.   Thus to make it actually work properly with the printers I would have to convert the __cause__ object to Python (and its __cause__ etc, proactively whenever an Exception wrapper was created.   This means a speed hit for a bunch of information which may get thrown away without ever being looked at.   Of course if you are Java oriented and "Exceptions should be exceptional" rather than Pythonic "Exceptions are just another return path", then the speed hit should be rare.
As for making a ValueError appear as a BaseException.  This is possible with the reverse bridge.   The only issue it that we still having not recruited enough people to serve as beta testers/developers to complete the epypj code.  I know that writing 1000 test routines and solving the pile of edge cases are not fun tasks, but it would be required to release that code.

I looked into this some further.  It is possible for me to wire up the __cause__, however this creates a conflict in the stack traces produced by Java and the ones produced within Python.   The issue is that CPython does not currently let use add the Java stackframes into the exception stack, so we are currently creating a fake exception with the Java stackframes and placing it as the cause.   For this to be a meaningful PR, we would need to find someway to insert a marker into the Python traceback system such that when an exception is thrown, we would know where in the Python stack trace listing the Java call occurred, and then replace the marker with the Java stackframes that we are getting from the Java exception.
I see that that whole system CFrame system is being reworked from 3.11 so it is very unclear if there is any way this can be accomplished in a cross version fashion.   At least as far as I can tell, there is no public API for creating tracebacks (so we are hacking that in place), and there is no way in the public API to push a marker into the Python traceback and pop it after the Java call returns such that if an exception took place in Java that we can splice out exception information in.  However,  perhaps   @markshannon be so kind as pointing me towards the API if it exists.


Does anyone want to use ytdl-core in a browser?

Describe the feature
As of v5.1.7, you can use your own proxy. Please see the proxy support in the README for details.
So, there is now a possibility to use ytdl-core in the browser if you disable CORS with your own proxy.
Until now, the YouTube API was not available due to CORS (it was not designed for browsers in the first place), but now it may be time to implement it.
So I would like to hear how many of you would like to use ytdl-core in your browsers. Please comment on anything or respond with an emoji!

I keep getting this error tho:
TypeError: Cannot read properties of undefined (reading 'decipher')


Central_heating sensor activated by automatically heating domestic hot water

Hello,
i have a strange situation with the software, when my boiler (itho base cube) is automatically heating dhw water the sensor central_heating gets activated. Buth the central heating is not running. When i turn on the hot water the sensor domestic_hot_water get active.
my boiler has multiple states for heating, heating hot water and heating cv.
im using version 0.10.2
Is this an bug in the software of the esp or is this normal behavior?
thanks in advance

Hi @bjornmorsman
It is not a bug, it is normal l that when you turn on hot water your hot water indicator is ON. The boiler is then heating.
Hope that explains,
Robert

Hi robert,
thats not what i ment, my central_heating indicator goes on when my dhw water is heating
thank you

Hi @bjornmorsman
Can you share some logging. So I can see the messages that are being sent?
Thanks
Robert

Hi @rvdbreemen
i added the log below.


[AutoDiff] Diagnose unsupported coroutine differentiation.

Coroutines are functions that can yield values and suspend/resume execution.
SIL has dedicated coroutine types. Coroutines are applied via begin_apply.
The read and modify accessors are coroutines.
Coroutine differentiation requires extra support, so it should be diagnosed
for now.

Differentiation transform:

Generalize differentiation utilities from ApplyInst to FullApplySite.

bool isArrayLiteralIntrinsic(FullApplySite)
void forEachApplyDirectResult(FullApplySite, llvm::function_ref<...>)

apply: direct result is the apply result, unless the apply result
has tuple-type and a single destructure_tuple user. Then, direct results
are the destructure_tuple results.
begin_apply: direct results are the begin_apply results.
try_apply: direct results are successor blocks' arguments.

bool LinearMapInfo::shouldDifferentiateApplySite(FullApplySite)

Generalize activity analysis from ApplyInst to FullApplySite.

Propagate variedness for FullApplySite through direct/indirect results and
inout arguments.
Propagate usefulness for FullApplySite through arguments.

Diagnose begin_apply instructions with active arguments and results in
PullbackEmitter::visitBeginApplyInst.

Sema:

Diagnose @differentiable attribute on read and modify coroutines.

Resolves TF-1081.
TF-1080 tracks coroutine differentiation support.
TF-1083 tracks throwing function differentiation support.

Example:
@differentiable
func foo(array: [Float], x: Float) -> Float {
  var array = array
  // `read` and `modify` accessors are coroutines.
  // Array subscript assignment below calls `Array.subscript.modify`.
  array[0] = x * x
  return array[0]
}
print(valueWithGradient(at: [3, 4], 5, in: foo))

// Before: silently incorrect results.
// (value: 25.0, gradient: ([1.0, 0.0], 0.0)).

// After: diagnosed.
// coroutine.swift:1:2: error: function is not differentiable
// @differentiable
// ~^~~~~~~~~~~~~~
// coroutine.swift:2:6: note: when differentiating this function definition
// func foo(array: [Float], x: Float) -> Float {
//   ^
// coroutine.swift:5:12: note: differentiation of coroutine calls is not yet supported
//   array[0] = x * x
//     ^

@swift-ci Please test tensorflow

Merging now. Happy to address review feedback later!


Add CopyObjectPart support for Core client

This is towards resolving https://github.com/minio/minio/issues/4885

Can we add CopyObjectOptions? Than we can extend the API. For users it should feel even more convenient:
GetObjectOptions
PutObjectOptions
StatObjectOptions
CopyObjectOptions?
EDIT: Especially because CopyObjectPart is the only way S3 provides to change object metadata for objects > 5GB...

CopyObject already has ComposeObject - SourceInfo, DestinationInfo - CopyObjectOptions doesn't cater for both source and destination though.

CopyObject already has ComposeObject - SourceInfo, DestinationInfo - CopyObjectOptions doesn't cater for both source and destination though.

Okay, than why do we need CopyObjectPart at all? For completeness?
As far as I can see ComposeObject works like multipart copy...

Okay, than why do we need CopyObjectPart at all? For completeness?
As far as I can see ComposeObject works like multipart copy...

This is for Core API for S3 gateway, this is not documented API.

@harshavardhana @aead Added extra metadata parameter to copy-object-part API. I think this facilitates adding encryption for copying APIs too.


Move CI tests to GIFT-Little

As discussed with @tvercaut and @wyli we are going to move the current CI tests from Adelie to the new CI server GIFT-Little. This issue is for testing that transition.

[ ] persistently set GPU for quick and slow tests, to ensure they run on separate GPUs?

Hi Dzhosh,
This looks strange, may I have ssh access to Little? I can have a look tomorrow.
(I've seen some different error messages for the same line of command
net_autoencoder.
Couldn't locate the issue precisely, but retrying the CI tests often
runs without an error.)
Thanks,
Wenqi
On Tue, 31 Jul 2018 at 10:17, Dzhoshkun Ismail Shakir
<EMAIL_ADDRESS>wrote:

@wyli Is this segfault expected? Does it ever happen on Adelie? (This particular segfault occurred on Little)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Research Associate
Dept of Biomedical Engineering
King's College London

I've retried the failing build. This time net_segment segfaults. Will retry again.

[ ] revert irrelevant changes to CI script

@wyli This time the pip-installer script seems to fail... It's either a segfault or an unknown node. It'd be great if you could have a look. I'll continue retrying in the meantime.

Everything seems to run well up to the pip-camera-ready script, which should (and does) fail for all commits not tagged with a v prefix.
The release-notes script (which follows the pip-camera-ready script) is minimal, and also does a chandler push for the release notes. So no testing action item for it at this stage. Worst case we can re-run it. However maybe:

[ ] set up chandler on Little

[ ] cross-check NVIDIA driver (against the Adelie) for the segfault issues

I've found this discussion, which talks about uncorrectable ECC leading to segfaults.
I've tried to reproduce the segfault by running:
for i in `seq 1 10`; do python net_gan.py inference -c $niftynet_dir/config/GAN_demo_train_config.ini; done

inspired by this failed build, keeping an eye on the output of the nvidia-smi output. However I couldn't reproduce the segfault.

The NVIDIA driver 384.130 (Little) seems to have similar Google hits as 384.111.

@wyli Nope. I haven't set any memory limits on Little yet.

It's interesting that in the last segfaulting CI task we get:
/home/gitlab-runner/builds/bf2aef4f/0/NifTK/NiftyNet/niftynet-dev-test-py3/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
  return f(*args, **kwds)
/home/gitlab-runner/builds/bf2aef4f/0/NifTK/NiftyNet/niftynet-dev-test-py3/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
  return f(*args, **kwds)

Which I fixed yesterday by downgrading NumPy to 1.14. But apparently some settings are different on the gitlab-runner account. Will take a look.

First pass succeeded, but second pass segfaulted.

It's been reported that import order might be the cause of segfaults.

[a conflict installing scikit-learn after tensorflow?]](https://stackoverflow.com/questions/45134309/sporadic-core-dumps-segmentation-faults-illegal-instruction-using-tensorflow)
I couldn't replicate the issue by running the ci script manually with or without virtualenv.

I think the segfault has gone after upgrading to TF1.9 and resetting the session/graph https://github.com/NifTK/NiftyNet/blob/403589122ca5c233348100a6d2f1f51737b4c6b0/niftynet/init.py#L143-L149

Great! I've now upgraded the global TF installation on Little to 1.9 as well.


AwesomeWM: awesome API

Most of these methods are either calling compositor/wm primitives (e.g shutdown the compositor, restart it, etc. These should be pretty easy to do) or xkb functions.
Since this is Wayland, I fully expect those xkb functions to not survive. The main issue is if they are returning or taking in any xkb-specific data structures. Even if so, they can be faked because we can usually get similar information from wayland. We shouldn't try to rely on xwayland though, so if something only works with xwayland clients it's ok to ignore it. We'll have to revisit this once we have more of the API done.
Functions

[ ] __index
[ ] __newindex
[x] quit
[x] exec
[x] kill
[x] sync
[ ] spawn
[x] restart
[x] connect_signal
[x] disconnect_signal
[x] emit_signal
[ ] systray
[x] load_image
[x] set_preferred_icon_size
[x] register_xproperty
[x] set_xproperty
[x] get_xproperty
[ ] xkb_set_layout_group
[ ] xkb_get_layout_group
[ ] xkb_get_group_names
[ ] xrdb_get_value

Working on this API now. Going to mock out the xkb functions

Actually we need the xkb functions to function properly...lets see if we can get them to work before the move to wlroots


Familiarize with the GitHub Project Management Tools

We need to be able to use all the tools at our disposal to do things in a proper manner and learn project management from it

A good link for GitHub workflow : Github itself
https://docs.github.com/en/free-pro-team@latest/actions/quickstart

Static code analysis tutorial : why, by cplusplus.com
http://www.cplusplus.com/articles/9E18T05o/
example of tool : http://cppcheck.sourceforge.net/
Informations to learn : gettings started & beyond  for the tool :https://sourceforge.net/p/cppcheck/wiki/Home/


Upload photo using Google Assistant

Summary:
Was just wondering if it would be cool to launch the upload flow in the Commons app directly from Google assistant. I can't think much about what all actions could be performed using the assistant launcher but it would surely be a novelty feature to have.
The basic action that I can think of is:
"Hey, Google! Upload photo on Commons"
Would you like to work on the issue?
Yes. Have worked on a couple of assistant apps in the past and it would be a cool thing to work on. :D

Sounds interesting to me! Would be nice if it would show the nearest location needing pictures, too. :)

Yes, great idea. Asking google about nearest location needing pictures would be a much better action.
Something like:

find nearest place that needs a picture on Commons
navigate me to the nearest place that needs a picture on Commons

Also, it would be great to use google Assistant for browsing.
Something like

Google, search some butterflies from commons.

@maskaravivek can you share a link using which we can integrate Google Assistant?

Nice suggestion @ujjwalagrawal17.
Here's the link for Google Assistant's console.
https://console.dialogflow.com/api-client/

This looks really good - I might have a look into it if I get the time
https://codelabs.developers.google.com/codelabs/voice-interaction/index.html


Created new directory SearchBar and new files RenderSearchBarContaine…

…r.js, SearchBarContainer.js, index.js
Description
DESCRIBE YOUR PULL REQUEST'S CHANGES AND REFERENCE THE FEATURE/USERSTORY/BUG IT'S REALATED TO.  REPLACE THIS TEXT.
Type

[ ] This is a bugfix.
[x ] This is a new feature.
[ ] This is part of a feature.

Organization

[ ] Have you linked this pull request to a Trello card?
[ ] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[ ] Is this a work in progress?
[ ] Is this ready to be reviewed?
[ ] Have you added two reviewers to this pull request?

 create a search bar


Migrate Fix from MRTK

Last week MRTK builds encountered an issue with their generated projects after a software update was pushed to the build machines. For some reason, the specific setup of the machine was causing the issue.
The issue was that MSBuild would ignore precedence of AssemblySearchPaths, which places HintPath before {TargetFrameworkPath} when resolving the assemblies, and this resulted in the .NET 4.6 (the target framework of the generated project) assembly to be chosen over the explicitly referenced one of .NET 4.7.2 (what unity uses to compile).
The fix here is to remvoe {TargetFrameworkDirectory} from the search paths, and prevent the explicit addition of targetFramework dlls.

Will you add some comments explaining these new entries in the proj?

Added the comments.


Add more strict  process around breaking changes

Feature request
This is more of a process request
During my work with many colleges who use view_component the largest frustration that many developers I work with have is the constant breaking changes, many may decide to not use view_component on new projects, so I feel this is large enough issue
So my suggestion is allowing view_component to be backwards compatible to the last major version and use deprecation notices for a full major version to allow the ability to migrate over a longer period of time
Also all breaking changes should be documented more explicitly and possibly for breaking changes to be introduced a migration guide must be in place as a criteria
I would like to close this off as saying this is all a suggestion and not an ultimatum, I just wanted to give a few suggestions and bestow how dire this situation can get from my interactions with real users of this library

@Spone  @BlakeWilliams  @boardfish(apologies to anyone I left out) can you please take a look at this and leave your thoughts

So my suggestion is allowing view_component to be backwards compatible to the last major version and use deprecation notices for a full major version to allow the ability to migrate over a longer period of time

If I'm understanding you correctly here, is this to say that if we wanted the next version to introduce breaking functionality, we should wait two major versions to remove the old functionality entirely:
graph LR
    A[V1] -- Functionality introduced with backwards compatibility and deprecation warnings --> B
    B[V2] -- Backwards compatibility removed --> C[V3]

...as opposed to the current process, which is:
graph LR
    A[V1] -- Functionality introduced with backwards compatibility and deprecation warnings. Backwards compatibility removed --> B
    B[V2]

@boardfish I feel that may be a good idea, I myself only started using view_component in 3.0 and I love it but manny users that have been using view_component 2.0 have not had the best time moving to version 3 and have been actively soured on it, I worry about this as it seems to be a large opinion in the circles I work in and this could ultimately make less people want to use view_component in all its awesomeness

I do also want to shout out deprecation_toolkit – we found this really useful in our V3 migration.

Hey @reeganviljoen, thanks for bringing this up!

the largest frustration that many developers I work with have is the constant breaking changes

I'm curious specifically about your use of the word "constant" here, since we try pretty hard to follow semantic versioning and only introduce breaking changes in major versions. I'd love to hear more about which changes in particular people are finding difficult, because my intuition is there are unique reasons why each individual change is challenging. For example, @boardfish mentioned renaming slot methods. That migration was challenging for us at GitHub too, mostly because Ruby doesn't have a great way to identify methods called on component instances (aside from grep). In the slot renaming case, we printed deprecation warnings and provided a clear upgrade path, waiting until v3 to switch over to the new naming strategy. What other upgrade issues are people running into?

my suggestion is allowing view_component to be backwards compatible to the last major version and use deprecation notices for a full major version to allow the ability to migrate over a longer period of time

I think this describes our existing process. Minor/patch releases of ViewComponent are backwards-compatible with the last major version... or at least, they should be. Again, I would be genuinely curious to hear about specific upgrade issues. We should not be making backwards-incompatible changes in major/patch releases, and if we are, we should stop.

Also all breaking changes should be documented more explicitly

Ok that makes sense to me. We probably shouldn't rely exclusively on deprecation warnings. I have a few ideas here:

Format the CHANGELOG to indicate which changes are breaking vs non-breaking. Here's an example from the Zeitwerk gem.
In the same vein, use changesets to indicate which changes resulted in a major/minor/patch version bump. See this example from primer/view_components.
Maybe mention them on the front page of viewcomponent.org?
Other stragegies?

...a migration guide must be in place as a criteria

Yes, this I agree with 100%. We should have had a migration guide for the jump from v2 to v3. However, I do question how useful a migration guide would have been for migrating to the new slot names API, since there's nothing anyone could have written that would have made it less painful 😅

I'm curious specifically about your use of the word "constant" here, since we try pretty hard to follow semantic versioning and only introduce breaking changes in major versions. I'd love to hear more about which changes in particular people are finding difficult, because my intuition is there are unique reasons why each individual change is challenging. For example, @boardfish mentioned renaming slot methods. That migration was challenging for us at GitHub too, mostly because Ruby doesn't have a great way to identify methods called on component instances (aside from grep). In the slot renaming case, we printed deprecation warnings and provided a clear upgrade path, waiting until v3 to switch over to the new naming strategy. What other upgrade issues are people running into?

@camertron the largest frustration I have seen is indeed slots, and an example that was given to me is if you look at rails active record, it really hasn't  had many breaking changes between major versions, even action_view itself has  soft deprecated form_for for many versions now but it is still available.So what I suggest is we try to soft deprecate things where possible(I understand slots was a painful jump, and is the exception) and only remove things where absolutely necessary

I think this describes our existing process. Minor/patch releases of ViewComponent are backwards-compatible with the last major version... or at least, they should be. Again, I would be genuinely curious to hear about specific upgrade issues. We should not be making backwards-incompatible changes in major/patch releases, and if we are, we should stop.

The largest breaking change between major versions that causes frustration is slots between v2 and v3, and again I understand it was necessary, It just may be wise to approach it more carefully next time with a migration guide and so forth

Ok that makes sense to me. We probably shouldn't rely exclusively on deprecation warnings. I have a few ideas here:

Format the CHANGELOG to indicate which changes are breaking vs non-breaking. Here's an example from the Zeitwerk gem.
In the same vein, use changesets to indicate which changes resulted in a major/minor/patch version bump. See this example from primer/view_components.
Maybe mention breaking changes on the front page of viewcomponent.org?
Other stragegies?

...a migration guide must be in place as a criteria

Yes, this I agree with 100%. We should have had a migration guide for the jump from v2 to v3. However, I do question how useful a migration guide would have been for migrating to the new slot names API, since there's nothing anyone could have written that would have made it less painful 😅

I agree with all the suggestions, a migration guide would have still been helpful as deprecation warnings are easier to get muddled up between other deprecation warnings of other gems

Alright thanks for your feedback @reeganviljoen, we'll take it into consideration for the next major release 😄


Added Project that finds people who don't follow you on instagram

This automation python script uses selenium module on python to run a script. It retrieves a list of the people you follow, the people who follow you and then returns a list consisting of all those accounts you follow, who don't follow you back.
More details on the exact usage, instructions and details can be found in the README.md file in the project folder.
Thanks and Regards
Sarthak Saxena

@sarthak1905 just add your details in Contributors Wall

@DeepNinja07x Hey there! In the Contributing.md file it says that I must edit the Contributors.md file, however, I am unable to locate the file. Shall I just update the README.md? Or am I missing something?
Thanks and Regards
Sarthak Saxena


Enhancement - Telegram Push Notifications

Enhancement
Integrate Push Notifications into Telegram so users can be notified of their brigade's calls.
This will basically work the same as Pushover Notifications..
Set in each Alias which Telegram Channel/Group you wish to send notification too.
Set API/Bot Key in Settings.
ADDITION
Would be cool also to have a Telegram of all pager messages as well.
Telegram Documentation: https://core.telegram.org/

I've seen a fork with this implemented already, may just need to be cleaned up and implemented cleanly with the existing notification stuff.
I might take a looksie at this one when i get some time.

That's a good idea, I likey. I've done some telegram integration work before, but only with userbots. I'll also have a look at some point if I get the time :)

Test this one out ... Not 100% it is bug free yet and not really happy with the message format but i couldn't come up with anything better with a 2yo climbing all over my lap 😛
https://github.com/davidmckenzie/pagermon/pull/113
I reused some of the code from this fork https://github.com/e-bits/pagermon/tree/feat/telegram where he added telegram support, but set it up the same way as pushover.
If you want to write some documentation on how to get a API Key and Chat ID @s3m1s0n1c  feel free, that was a damn pain! :wink:

Wow.. That was quick... Thanks Dan
Will give it a whirl and see how it goes..  Yeah i can imagine having a 2yr old climbing around would make it more difficult.. Don't have that issue YET.
Yeah getting the API Key and Chat ID is a pain in the butt..  I will write some instructions on how to get get the info..
Thanks..

Solved in #113 thanks guys!


Fix Typos in 7 Unexpected Ways Verifiable Credentials Are Used Today Blog Post

Fix Typos in 7 Unexpected Ways Verifiable Credentials Are Used Today Blog Post
🚀 Goal
We want to ensure our website's blog posts don't have any mistakes.
🤔 Background
This issue focuses specifically on fixing typos across on one of our blogs. Your contributions here make a difference!
🤝 How You Can Contribute
We've broken it down into specific typos for you to address. Every contribution counts!
🔑 Tasks and Acceptance Criteria

Fix typos in 7 Unexpected Ways Verifiable Credentials Are Used Today Blog Post:

[ ] Change "Verifiable Credentials seem niche." to "Verifiable Credentials seems niche." to represent the singular concept

Make sure all tests are passing.

🌟 Resources

7 Unexpected Ways Verifiable Credentials Are Used Today Blog Post
Blog, Developer Website

Getting Started

Comment ".take" on this issue to get assigned
Fork the repository and create a new branch for this task
Follow the tasks outlined above
Submit a pull request with your changes
Respond to any feedback during the review process

Questions?
If you have any questions or need clarification, please comment on this issue or join our Discord community.
Happy coding! 🎉

.take

Hey @aniketh-varma I noticed you're assigned to 8 issues and they're all typo issues. While we appreciate the enthusiasm, we kindly ask that you finish an issue before assigning yourself a new one. We want to give everyone a chance to be able to make their first contributions to open source. So, I'll leave you assigned to ticket #1578 , but I will unassign you from the rest.
If you finish that ticket, then you can assign yourself to a new one! Thank you

.take


Update docs for 0.3.0

0.3.0 deprecated annotate, remove and describe. We should account for that.

Question: are they really deprecated? or they work on dvc.yaml instead of artifacts.yaml? Which command will replace them then? Will you move these commands to dvc?

In 0.3.0, I removed them @francesco086.

What do you mean by removed? I can still see them...
❯ gto --version
🪴  GTO Version: 0.3.1
❯ gto -h
Usage: gto [OPTIONS] COMMAND [ARGS]...

  Git Tag Ops. Turn your Git repository into an Artifact Registry:
  * Registry: Track new artifacts and their versions for releases and significant
  changes.
  * Lifecycle Management: Create actionable stages for versions marking status of
  artifact or it's readiness to be consumed by a specific environment.
  * GitOps: Signal CI/CD automation or other downstream systems to act upon these
  new versions and lifecycle updates.

Options:
  --version      Show version and exit
  -v, --verbose  Print debug messages
  -h, --help     Show this message and exit.

Read the registry:
  check-ref  Find out the artifact version registered/assigned with ref.
  doctor     Display GTO version and check the registry for problems.
  history    Show a journal of registry operations.
  show       Show the registry state, highest version, or what's assigned...
  stages     Print list of stages used in the registry.

Modify artifacts:
  assign (promote)  Assign stage to specific artifact version.
  deprecate         Deprecate artifact, deregister a version, or unassign a
                    stage.
  register          Create an artifact version to signify an important,...

@francesco086, sorry, I think I'm misunderstanding you. The output you posted doesn't have annotate, remove and describe because they were deprecated in 0.3.x. Did you mean something else?


dynamic rule updates via API

Would an additional interface for Rules (to allow dynamic pulls/updates) be possible? I'm thinking "what if k8s deployments defined bpfd Rules". Like an amped-up Twistlock network policy enforcement.

yes yes I was thinking a grpc api :) please feel free to discuss design
here and send a PR :) that was how i wanted the client to communicate with
the daemon as well
On Mon, Sep 10, 2018 at 10:23 AM Jeff Bachtel<EMAIL_ADDRESS>wrote:

Would an additional interface for Rules (to allow dynamic pulls/updates)
be possible? I'm thinking "what if k8s deployments defined bpfd Rules".
Like an amped-up Twistlock network policy enforcement.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/bpfd/issues/1, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbHjzEHLrs5YkVh1r2uKl315Ud4-gks5uZnXggaJpZM4Whgdf
.

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

added the api and dynaic rule adding :)

(thank god Jess is fast and I didn't have to embarrass myself trying to learn to code grpc)


Error if trying to use library before body is found

Hi,
I just noticed that this library doesn't work if it's used in a script included in the head section of the page (before the body is in place). It also requires script tag to not have defer attribute.
It boils down to this line
https://github.com/caroso1222/notyf/blob/27cd61ad8726f21fcab2add9b58799d92aac9d2f/src/notyf.view.ts#L34
It will give the following error: Cannot read property 'appendChild' of null which basically means that the body is not there yet and can't append to it. It works if I move script tag to bottom or use defer attribute, but in my case I can't use neither.
Is there a way to fix this?

Hey! Hmm good catch. Just wondering, why do you need it to work on the head? scripts like this library are generally meant to be placed on the body bottom so that it doesn't block initial rendering and can also make use of the body.
Can you please give a bit more context on why you need it on the head? Maybe there's another way around.

It's just in my local development setup (CMS site). I have it in the head because otherwise there's a flash of unstyled content. I have a webpack dev server in use and the styles are injected when the script is executed. It's a minor issue but still a bit annoying 😄. It's kind of my issue maybe now when I think. I just wanted to let you know.


TimeoutException after 0:00:10.000000: Future not completed

When I use the aqueduct (conduct) back-end framework and dart to write the back-end, I simulate the twitter API request to create a tweet. I have successfully created it in the flutter project on the Android side. However, if I test with this framework, there is only one Mian function in the main program entry and directly call the test method. In this way, an error message appears after running. It is useless to modify the timeout for a long time, This code is the same as that in fluent
TimeoutException after 0:00:10.000000: Future not completed

final twitterApi = TwitterApi(
client: TwitterClient(
consumerKey: '',   //There are no errors in the parameters
consumerSecret: '',
token: '',
secret: '',
defaultTimeout: const Duration(minutes: 2)),
);
Future test() async {
try {
// Update your status (tweet)
await twitterApi.tweetService
.update(
status: 'Hello world!',     //The modified text information cannot be repeated in a short time
)
.whenComplete(() => print("success"));
} catch (error) {
print('error while requesting home timeline: $error');
}
}
//Only these packages and versions
dependencies:
aqueduct: 3.3.0+1
random_string:
crypto: ^3.0.2
dart_twitter_api: ^0.5.6+1
http: 0.13.4
conduit: ^3.1.2

How is this related to the geolocator plugin? Did you post this issue in the wrong package repository?

No description provided.


ImportError: /usr/local/lib/python3.10/dist-packages/causal_conv1d_cuda.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN3c104cuda9SetDeviceEi

ImportError                               Traceback (most recent call last)
 in <cell line: 4>()
2 import argparse
3
----> 4 from mamba_ssm.models.mixer_seq_simple import MambaLMHeadModel
5 from transformers import AutoTokenizer, TrainingArguments
6 from trainer.data import ChatDataModule
3 frames
/usr/local/lib/python3.10/dist-packages/causal_conv1d/causal_conv1d_interface.py in
5
6
----> 7 import causal_conv1d_cuda
8
9
ImportError: /usr/local/lib/python3.10/dist-packages/causal_conv1d_cuda.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN3c104cuda9SetDeviceEi

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.
I am facing above error when starting the fine-tuning in Google Colab.

Could you try installing causal-conv1d manually and not from the requirements using pip install causal-conv1d ?


A terrible issue about "Emoji Plug"

Informations
Just have a look at the image:
http://www.bluestep.cc/demos/20180317160335.png
Browser version:
All browsers
Screen resolution:
How to reproduce the bug?

Please do me a favor, thx a lot.

https://alex-d.github.io/Trumbowyg/demos/#plugins-emoji
Did it works here?
Don't forget the CSS file :)

Now I can add emoji now, the issue caused by I used the "textarea" HTML TAG,  I changed it with "DIV" TAG, but a new issue occured:
when we add some words in the middle of the content, the cursor always focus the start of the content.

Should work now :)


feat: Use ordinal measures with maps

Closes #734.
Fixes #781.
This PR introduces the usage of ordinal measures in maps (both in area and symbol layers). Additionally, we now fetch optional colors assigned to dimension values and use them as default, initial color values in color mappings. It also adds title for non-hierarchical map legend.
How to test

Go to /en/browse/dataset/https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Ftest_ordinal_507%2F7?dataSource=Int
Select map chart type.
Select area layer.
See that ord1 (ordinal measure) is selected and it's possible to select other ordinal measures.
See that the colors are custom-defined (green-red).
Select symbol layer.
Enable the layer.
See that in this extreme example we don't have any numerical measure so the radius of the symbols is fixed and shared across all symbols.
Change color mapping and see that it's possible to choose ordinal measure to color the symbols.

I think it'd be good to have an E2E test for this feature :)