Native filter tabs

Current filter system is used more like button to shift state causing posts feed to re-render posts list items. This causes a momentary lag in app performance.
Expected behavior
The transition from one tab to another should be instantaneous. just like bottom navigation tabs only in this case it should change posts filter.
Additional context
The idea is to replace button based filter tab with actual native tabs with built-in cache functionality.
Ideally the new system will use most of the same codebase as available postsContainer and sub components
Checklist

[x]  promoted posts
[x]  user switching hooks - (buggy when switching user while in non feed tab)
[ ]  double tap to scroll up
[x]  load posts from storage on startup
[x]  handling logout
[x]  Make hide Images button functional
[x]  scheduled new posts check
[x]  Fix memory leak on component unmount
[x]  fix missing keys issues
[ ]  post tabbedPosts to profile screen
[ ]  port tabbedPosts to community pages
[ ]  port tabbedPosts to tag results pages

A quick status update regarding native filters...
So far we have,

Implemented basic tabs with clean filter change implementation.
Ported load posts routine to it's separate sub-class under tabbedPosts
Ported our reducer as it is from postsContainer and organised it better along with some cleaning.

Only drawback we have in our current implementation is the fact when a list is updated, the chagne is not register thrown by reducer, to make it force throw a change callback, I am copying state Object.create(state) and returning it back, not the most efficient solution but is done only for experimentation for now.
Status Update Log
https://user-images.githubusercontent.com/6298342/113621976-cb3c5180-9675-11eb-9e2a-277a0a0a3b4a.mov
The recording is from an android phone running in debug mode, release mode performance will be even better for sure.

Status Update
The feed screen is now useable with most of primary functions like,

pagination
refresh
logged out view
empty list view for friends and communities tabs

Pending Items

promoted posts
user switching hooks
double tap to scroll up
new posts check

Video
https://youtu.be/ZDgcxsvxw-k

@feruzm please if you get a change feel free to update the ToDo/Pending items to list of feed screens functionalities... it's a big component, very easy to miss something from tests.

@feruzm checkout this issue related to promoted posts fetch on tab change...there is a glitch when new promoted posts is rendered in place of previous post because of image height calculation. this should affect our previous builds as well...
However if user move to other tab for the first time, the glitch do not affect anything as expected.
https://user-images.githubusercontent.com/6298342/114015269-efb94900-9882-11eb-8999-d1fb3ea0cd94.mov

Suggestion 1:
we keep the current structure but fix height of promoted post, it will remove the glitch in no time.
Suggestion 2:
we fetch updated promotions on list end callback and stack promoted posts just like regular posts.

@noumantahir

You mean have fixed size for height of promoted posts?
You mean on first list end callback we show all promoted posts? Promoted posts should be showing every 3 item on list, so right now limit 20 means we should have at least 6 promoted post until first list end callback.

@feruzm

yes
if we remove refresh ads on tab change, we will have same old list of ads, what I am suggesting is we add more ads to promotedPosts array when all ads are displayed so user see new ads as scrolling down instead of not showing at all

Status Update

[x]  1. promoted posts
[x]  2. user switching hooks - (buggy when switching user while in non feed tab)
[ ]  3. double tap to scroll up
[ ]  4. new posts check
[x]  5. load posts from storage on startup

Updates

[x]  promoted posts
[x]  user switching hooks - (buggy when switching user while in non feed tab)
[ ]  double tap to scroll up
[x]  load posts from storage on startup
[x]  handling logout
[x]  Make hide Images button functional
[x]  scheduled new posts check
[x]  Fix memory leak on component unmount
[x]  fix missing keys issues
[ ]  post tabbedPosts to profile screen
[ ]  port tabbedPosts to community pages
[ ]  port tabbedPosts to tag results pages

Updates

[x]  port tabbedPosts to community pages
[x]  port tabbedPosts to tag results pages

Pending

[ ]  post tabbedPosts to profile screen - scroll issues, tab change issues

attempting to make use of this package...
https://github.com/zyslife/react-native-head-tab-view

skipping head-tab-view for now, documentation is very confusing and is not well written package

[x]  port tabbedPosts to profile screen

Know issues

tab change issue while scrolling

Finally! fixed weird unresponsive tab change while scrolling issues by discarding nested scrollview in favour of stacked tab bars.
The final implementation is surprisingly more clean may even be more efficient as there are not nested tab bars.
Only thing I dislike the fact there are 2 tabs for each stack when viewing your own profile, that does not look as promising compared to 3 - 2 stacked tabs
https://user-images.githubusercontent.com/6298342/114520188-9b371480-9c5a-11eb-8925-d4dcadfae5f2.mov

@feruzm
My suggestion:
We can do non stacked 3 tabs [Posts, Blogs, Replies] for user's profile and keep other profile stacked..

@noumantahir lets move Blog to 1st line of tabs and remove sub tabs ? My only concert is that, can these tabs if 3-4 items fit nicely in smaller screen sizes. We can of course make Wallet tab as icon so it takes lesser space when viewing other people's account.

let me try.. we can also try removing image icon perhaps... we already have images toggle button in feed screen

good point, on profile page that's (view change toggle) probably not necessary

@feruzm single profile tab bar on small to large screens, codes pushed as well..

after update from previous version, I launched app and this is what I got... For example, Top filter at first loaded posts and then showing spinner, it did stop but on other tabs it is not stopping so there is likely some bug or cache update logic that's not working.
https://user-images.githubusercontent.com/3015990/114842475-8c2e9e80-9de1-11eb-9247-4c0867466fc4.MP4

could be something introduced because editable tag update as it did required tweak to tabbedPost... will debug


Entrypoint only supports CIC 6105

It always uses 0x80000318. Also see system.c which uses both addresses 0xA0000318 and 0xA00003F0.

This is not true anymore in the unstable branch, as libdragon only supported the new open source IPL3, whose API is not CIC-dependent.

IPL3 was merged to trunk too, so we now support all CIC types transparently (with the same IPL3).


Add logging handling

This will handle logging that can be showed to the user to help them understand what the program is doing

Done.


Should we remove Duplicate Exceptions on Qualification & State?

In gitlab by @A-Lawrence on Sep 2, 2016, 15:01
These have been in use on production.  Should these methods just be idempotent?

In gitlab by @A-Lawrence on Sep 2, 2016, 15:02
Changed title: {-R-}emove Duplicate Exceptions on Qualification & State → {+Should we r+}emove Duplicate Exceptions on Qualification & State

In gitlab by @A-Lawrence on Sep 2, 2016, 15:02
Removed ~98470 ~137454 ~152644 ~584592 labels

In gitlab by @A-Lawrence on Sep 2, 2016, 15:02
Changed title: Should we remove Duplicate Exceptions on Qualification & State → Should we remove Duplicate Exceptions on Qualification & State{+?+}

In gitlab by @A-Lawrence on Sep 2, 2016, 15:11
mentioned in commit 912d789d51326e112f3f15f9ca0dd58e16e5d323

In gitlab by @A-Lawrence on Sep 2, 2016, 15:11
mentioned in commit ddfda934680a3a5ed693c2591e68a72fbe9782c8

In gitlab by @A-Lawrence on Sep 2, 2016, 15:29
Removed ~98471 label

In gitlab by @A-Lawrence on Sep 2, 2016, 15:29
Milestone removed

In gitlab by @NFarrington on Sep 8, 2016, 03:36
Yes - we don't need to check if it's already assigned, since it doesn't matter (just as long as it is assigned). I've never liked the duplicate exceptions, and these have caused issues in the past where the developer hasn't accounted for this being thrown.

In gitlab by @A-Lawrence on Sep 9, 2016, 19:25
We need to discern where this matters, and where this doesn't.  My view is that properly catching these errors gives us far more flexibility.  Consider issue #558 - we need a way of notifying the user, but it's the same method that the cert feed uses.


grid.reload()

reload function is not work well. If cell already edited and then I call reload function this cell did not show. if I reload grid it must show all coloms and cells please help me

You can see example for CRUD operations with ASP.Net at https://github.com/atatanasov/gijgo-asp-net-examples
Please use it as an example


Permit arguments for barnyard always.

Definitely open to suggestions on this, just figured I'd try my hand at implementing arguments for barnyard_run_. I'm not sure what the regex to detect a module should look like, so for testing purposes it is currently looking for a file ending in .zsh.

And so, it would seem that we're going to assume that *.zsh is a program and we're going to stop interpreting arguments to barnyard always once we reach a none *.zsh or -- and that kind of makes sense. We could insist that the user run programs one at a time, though. It was kind of a nice to have to not have to checkout the work on each module, to have multiple modules run on a single invocation of always, but now that is making for some goofy command line parsing.
If we get rid of multiple modules, then command line interpretation is simple.
Within a Barnyard invocation, the barnyard_always function uses the current working extract on each call so it's only Zsh function call overhead, not git extract overhead.
Also, when using --barnyard=../my-barnyard we do not do an extract, we just use the given directory. We only do an extract when using the system barnyard.
And so...
Makes more sense to get rid of run a batch of modules and then have deathly simple argument parsing.
And then removed the ambiguity. We only have one barnyard module for which we want to pass arguments, but the moment we have two we couldn't call them multi-module. Who's argument are we going to use? Let's not conjure on the concept of consuming arguments and leaving remainders, or using multiple -- (which kind of wouldn't work, because then -- itself is can never be an argument.
Leaning toward one module at a time for always. The invocation on a production machine, yes I do it, but never multi-module style. When you're working on a production machine you should never be in a milliseconds hurry.

@flatheadmill updated to permit command line arguments for barnyard always calls. We now permit a single module per instance of barnyard always and the remainder of the command line arguments are forwarded to the executed program.

Does this work with the barnyard_always function?

I'll test it.

@flatheadmill yes it works with barnyard_apply.


Ecobee3 sensors are often duplicated after a restart.

Once in a while, ecobee3 sensors are duplicated.  They will then appear in HA as additional sensors at the top of the web interface.
In "Set State", the entities are duplicated.  For example:
sensor.ecobee3_humidity
sensor.ecobee3_humidity_2
Doesn't happen everytime, but does seem to happen often.

If you have, remove the following line from your config:
sensor:
  platform: ecobee

I don't have the lines as you've indicated.  The only thing I have that's related to ecobee is the ecobee section:
ecobee:
api_key: [redacted]
hold_temp: False

I made an attempt to fix this in 4840dd297a84369eed6a609193c3d781d86476b2
It will be part of the next release of Home Assistant.

Thanks Balloob!


Use ably-js as peer dependency

Using a library as a peerDependency offers several advantages, including: reduced bundle size, simpler updates, clear separation between ably react-hooks and ably-js

We decided to move react-hooks as ably-js submodule in future


Better js package

This is a shot at revamping the javascript packagin story to get it ready for a preview release which will replace the current automerge NPM package.
The primary change here is to package for wasm-bindgens bundler target rather than the web target when distributing code for browsers. This allows us to do away with the async init function which automerge-wasm exposed - that now being automatically handled by the bundler - which in turn allows us to directly depend on automerge-wasm package in the automerge package and consequntly not require any initialization steps on the part of users. This seems like such a huge benefit that it is worth requiring everyone to use a bundler.
This PR includes an example of bundling with Webpack 5 and Vite. Unfortunately create-react-app doesn't work because there's no way to tell CRA that we want to use Webpack's experimental webassembly support.
In order to effectively test all this I've added a tool in automerge-js/e2e which publishes the various packages to a local NPM repository and then builds against that. This is used in the scripts/ci/js_tests and scripts/ci/wasm_tests scripts to run the tests against the version of the code in the repository even if that hasn't been published to NPM yet. This script  also includes a way of running the local NPM server so that other projects on the same machine can point at it if for some reason you need to do that - such as debugging without having to edit three levels of transitive dependencies.

I'll pull & try it today but isn't CRA still a pretty important thing to support?

Right, this supports create-react-app via a bunch of awful hacks - explained in automerge-js/examples/create-react-app. I've also renamed the JS version to 2.0.0-alpha.1. I think we should merge this now and then push a JS alpha release. Please object in the next few hours or forever hold your peace.


replace "listhen" url

Not sure https://listhen.unjs.io/ is working.
🔗 Linked issue

❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks for PR. *.unjs.io redirect to github.com/unjs/*. This is mainly to allow auto migrating to docs (websites) when they are published.


gc_limbo is not thread-safe?

I've been reading over the source for libqsbr - it looks like a great library which I'd like to use in a few applications, however I'm confused about one aspect of the design.  Specifically, regarding the code that inserts removed elements into the limbo list - why is this code not thread-safe?  I mean, the code for gc_limbo, for example, does not use any memory barriers or atomic instructions when it adds the removed element into the limbo list.  And the limbo list is not thread-local.  Yet, the example in the README file indicates that we can call gc_limbo from any random worker thread.  So how is this possible?
It would seem that since gc_limbo does not use memory barriers or atomic instructions, it would only be safe to call it from one thread - perhaps a specially designated "reclamation thread" or something - except the README seems to imply we can call gc_limbo from any arbitrary worker thread.  I'm very confused about this issue, and would appreciate any insight into how gc_limbo is supposed to work.
Thanks

The limbo list is now managed atomically and is therefore MT-safe. Also, updated README to indicate that the reclamation function takes a list of entries rather than a single entry.
Implemented Epoch-based reclamation (EBR) algorithm. Might switch G/C mechanism to EBR at some point.


Failed to load resource: the server responded with a status of 404 (Not Found)

I've followed the quick walk through and when I run my project I have these errors :
Failed to load resource: the server responded with a status of 404 (Not Found)
localhost/:23 Error: Error: XHR error (404 Not Found) loading http://localhost:55976/angular2-modal(…)(anonymous function) @ localhost/:23
http://localhost:55976/angular2-modal/plugins/bootstrap Failed to load resource: the server responded with a status of 404 (Not Found)
http://localhost:55976/angular2-modal Failed to load resource: the server responded with a status of 404 (Not Found)
http://localhost:55976/angular2-modal/plugins/bootstrap Failed to load resource: the server responded with a status of 404 (Not Found)

Maybe the walk through is not up to date ? I'm using angular2 rc6.

RC7 here.
Are we missing something?

I solved this problem by adding the following  in systemjs.confg.js
map: {
  ...
  ...
  'angular2-modal' : 'npm:angular2-modal',
  'angular2-modal/plugins/bootstrap' : 'npm:angular2-modal/plugins/bootstrap'
},
packages: {
  ...
  ...
  'angular2-modal': {
    main: './index.js',
    defaultExtension: 'js'
  },
  'angular2-modal/plugins/bootstrap' : {
    main: './index.js',
    defaultExtension: 'js'
}


[WIP] IJRC - implementation

Auto-generate an installation script together with the launch file. Installing all the required ROS dependencies and guide the user in case ROS is not installed to automatically setup and install the preferred distro
Add java actions to:

simulate the connections that will be automatically created at runtime
remove all the the connections
connect all the open ports with the same msgs type

Docu still missed


[auth] Update Condition Attribute enum values

:nut_and_bolt: Description: What code changed, and why?
The allowed values for a rule's Condition Attribute were a mix of plural and singular and didn't match how they're meant to be shown in the UI. Now they've been updated to match this list provided by superteam:
*Node Attributes*
Chef Organization
Chef Server
Environment
Chef Role
Chef Tag
Chef Policy Name
Chef Policy Group

*Event Attributes*
Chef Organization
Chef Server

:athletic_shoe: How to Build and Test the Change
curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects -d "$(jq -n '{ id: "bar", name: "my bar project"}')" | jq .

# no longer works
curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects/bar/rules -d "$(jq -n '{ id: "rule2", name: "my foo rule", type: "NODE", conditions: [{ operator: "EQUALS", attribute: "CHEF_ORGS", values: ["The Misfits"]}]}')" | jq .

# works
curl -kH "api-token: $TOK" https://localhost/apis/iam/v2beta/projects/bar/rules -d "$(jq -n '{ id: "rule2", name: "my foo rule", type: "NODE", conditions: [{ operator: "EQUALS", attribute: "CHEF_ORGANIZATION", values: ["The Misfits"]}]}')" | jq .

:white_check_mark: Checklist

[x] Tests added/updated?
[x] Docs added/updated?

:camera: Screenshots, if applicable

:hrm: Are there any user-facing docs we'd need to update? Or concerns about backwards compatibility?

these maybe?
https://automate.chef.io/docs/client-runs/#node-filters
https://automate.chef.io/docs/reports/#search-bar-and-filters


Bump Apache Curator from 5.3.0 to 5.4.0

Description
Follow up to #12939. As noted in that PR there are a few fixes in 5.4.0 that should make running on Kubernetes more reliable. Notably:

https://issues.apache.org/jira/browse/CURATOR-538
https://issues.apache.org/jira/browse/CURATOR-649

Release note
Bump Apache Curator from 5.3.0 to 5.4.0

This PR has:

[x] been self-reviewed.
[x] a release note entry in the PR description.
[x] added or updated version, license, or notice information in licenses.yaml

This fixes #13167


How to go to first card

Hello,
Is there a way to go to the first card when card stack finished?

You can just set the loop props to true:
<CardStack loop={true}

@lhandel  please check with https://github.com/lhandel/react-native-card-stack-swiper/issues/40


gce: default network short_name to mantl

[x] Installs cleanly on a fresh build of most recent master branch
[x] Upgrades cleanly from the most recent release
[x] Updates documentation relevant to the changes

fixes #1502

LGTM


Better Documentation of all functions

Thanks for the software looks really nice :)
It is not really clear what this library can do. The examples are not enough.
Can this library send video streams or is it only for receiving and decoding?

Yes absolutely. The repository author needs more attention to the documentation. Otherwise, it will work like a junk program and not trustworthy to apply the production-ready project.
One more important thing, if you have your own repository, please look at the issues section on a daily basis and reply to the reported issues. If you are not willing to do otherwise this repository becomes a tourist trap.


[Bug] Paimon catalog can't read orc file from local filesystem

Search before asking

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

Version
2.1.4
What's Wrong?
When create paimon catalog used local file system via 'file:', can't get any data from select sql.
And be.WARNING log reported :
W20240619 10:40:28.923295 14875 file_system.cpp:35] [NOT_FOUND]failed to open file:/bigdata/paimon/test.db/
test1/bucket-0/data-f5fd76ac-0ef3-41dc-bfe9-9510c6b66a7c-0.orc

on the other hand, show databases and show create table work well
What You Expected?
please fix this, let doris can read paimon data from local file system.
How to Reproduce?
in flink sql client, create paimon catalog and insert some data.
CREATE CATALOG paimon WITH (
    'type' = 'paimon',
    'warehouse' = 'file:///bigdata/paimon'
);

USE CATALOG paimon;

create database test;
create table test.test1 (
id INT PRIMARY KEY NOT ENFORCED,
tchar CHAR(100),
tdecimal DECIMAL(12,3)
);

in doris, create paimon catalog and select ,would report a warning.
CREATE CATALOG `paimon_local` PROPERTIES (
"type" = "paimon",
"warehouse" = "file:///bigdata/paimon"
);

switch paimon_local;

SHOW CREATE TABLE test.test1;
SELECT * FROM test.test1;

Anything Else?
in Release 2.1.2 , doris works well
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

遇到过这个问题，paimon格式设置为avro没问题。parquet，orc会出报错


Docs: wrong anchor link used for CSS API

Basically, all the components have links to the CSS API for the component, where the anchor part is #css-api. This doesn't correlate with the actual anchor link, whose name is #css.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Steps to Reproduce 🕹

Go to https://material-ui.com/api/input/
Press the highlighted "CSS API" link in the classes prop
Observe that nothing happens, except the url changing to https://material-ui.com/api/input/#css-api
Verify that the actual anchor is #css by clicking the CSS title further down on the page.

@fatso83 This bug was fixed in https://next.material-ui.com by #14554.

A bit confusing that something was fixed 2 weeks ago, but still present, but then I realized it means doc fixes are not back-ported. Which is fine, I just didn't understand it at first.

@fatso83 v3.9.2 might be the last release of v3. We are full steam on v4 now.


Bug: Wins Should Not Be Higher Than Played

There are hundreds of players who report that their Wins is higher than their Played. This leads to a lot of problems when trying to calculate number of games lost, win rate and many other issues. The fact is Wins CANNOT be higher than Played
IGN: Cdw849 Region: EU
Relevent To Issue
{
played: 572,
wins: 642,
 }

Player Object
{ elo_earned_season_4: 0,
elo_earned_season_5:<PHONE_NUMBER>44039,
elo_earned_season_6: 1088.5247873184278,
elo_earned_season_7: 1349.403975530395,
karmaLevel: 1,
level: 29,
lifetimeGold: 15275.875,
lossStreak: 0,
played: 572,
played_ranked: 86,
skillTier: 13,
winStreak: 0,
wins: 642,
xp: 143933 }

#153

Got to the bottom of this with 2.8.  Here's the ticket that fixes it.
#290


ActiveSupport Object#blank?

https://github.com/rails/rails/blob/v<IP_ADDRESS>/activesupport/lib/active_support/core_ext/object/blank.rb


FancyZones steals input focus on display resolution change which breaks fullscreen games

Environment
Windows build number: 10.0.18362.295
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce
Ensure FancyZones is active. The option "Flash zones when the active FancyZones layout changes" may need to be enabled as well.
Run any fullscreen game which uses a resolution different from the desktop resolution.
I first noticed this on Spyro: Reignited Trilogy for PC but then made a simple Unity project to confirm it's nothing specific that game is doing. I have attached it below (source code and binary) to allow for easy reproduction.
Test.zip
The resolution selection dialog has been enabled for the included build. Disable "Windowed" and select a resolution different from the desktop resolution.
Expected behavior
The game runs as it normally would.
Actual behavior
FancyZones attempts to display the zones in the new resolution, stealing focus from the game. This causes Windows to minimize the game and revert to the previous desktop resolution. It is impossible to maintain focus on the game.
After closing out of PowerToys the game can be restored and runs normally.

Hi @The-MAZZTer
thank you for reporting the bug.

@The-MAZZTer
can you confirm that with "Flash zones when the active FancyZones layout changes" off the problem doesn't occur?
We are planning to turn it off by default so it will be less common for users to run into this issue.
Thank you.

Yup, seems to work fine.

@The-MAZZTer
can you confirm that with "Flash zones when the active FancyZones layout changes" off the problem doesn't occur?

I just ran into the same issue and disabling that option fixed the issue! :)

I have this issue too. It is intermittent so I don't know for sure if the "Flash zones..." option is to blame. But I want to add that it is not only full screen games that are affected: I started one app (PyCharm) whose window appear maximized - the window was minimized to tray a split second after it appeared.

Agreed with all the findings above. I would be able to open a full screen game and play without issue until I ever tabbed out of it, then nothing I could do would get me back in the game as the zones would always flash up and take me back to desktop.
I can also confirm that it does seem to be fixed with Flash Zones off.

Assigned to @vldmr11080

Fixed in https://github.com/microsoft/PowerToys/releases/tag/v0.14.1


IntelliCode keeps breaking for external libraries for Java Development (without any build tools)

VSCode Version:
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

Steps to Reproduce:

Clone my project from https://gitlab.com/shrinidhiinstasafe/iptables-wrapper
Switch to "new" branch,
Install all required Java and Spring Boot extensions,
Notice that the import of the jar files from the external folder keeps breaking in IntelliCode continously.

Details ::
I am currently doing all the development in a server and use Remote SSH. (It is such an excellent feature).
For this particular Java project, I am not using any build tools like gradle and maven. I created a basic Java project in VSCode and it gave me .project and .classpath files.
I needed to use two external libraries for my project, Json Simple and Hamcrest. I downloaded both the jar files, added them to the project and changed the .classpath to ::
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8"/>
	<classpathentry kind="src" path="src"/>
	<classpathentry kind="output" path="bin"/>
	<classpathentry kind="lib" path="external/json-simple-1.1.1.jar" />
	<classpathentry kind="lib" path="external/hamcrest-all-1.3.jar" />
</classpath>

Everything works perfectly for sometime. VSCode IntelliCode is able to recognize the libraries, import works, documentation tips while hovering works, even the build works.
But exactly some 5 mins later, for no reason at all, it stops recognizing the existence of the external libraries completely.
I tried reloading the window, restarting the server, uninstalling all Java related extensions and installing again but it the exact same behavior.
It simply cannot acknowledge external libraries for more than a few minutes and I have no idea what the cause maybe. After lots of efforts from past few days, I have come to you all for help.
See the below screenshot. This is how it becomes just a few minutes later.

Please file this issue on the intellicode repo https://github.com/MicrosoftDocs/intellicode. It's not clear to me whether you are actually using the intellicode extension but if not, I assume you are using the Java language extension and you can file this issue there: https://marketplace.visualstudio.com/items?itemName=redhat.java


⚠ Bofrost.de has degraded performance

In f8314d8, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 919 ms

Resolved: Bofrost.de performance has improved in d5ffd70 after 313 days, 10 hours, 36 minutes.


config: Update proxy config according to virtcontainers

Proxy config now relies only on a URL provided to the library so
that it can connect to the proxy.

lgtm

LGTM

Coverage increased (+0.7%) to 13.082% when pulling 090d43e5efd1478405fac610d4767605deb585ec on sboeuf/add_proxy_config into d02c072db744b2d20721938aa570a9f9bea5f421 on sboeuf/add_shim_config.


Added 'Sumin Jin' in Korean

Changes

Implementation details

How to read this PR

Screenshots

 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.


A few observations

Here are a few observations:

Application instance should clearly be a singleton instance. I couldn't find any reasons why a dev should be able to have multiple.
We should get rid of the injection factory and leave injections to the dic. The new one will handle deps quite wisely.
We should stop using the container as a service locator (looking at you, request stack). It should be injected into the application IMO.
In general the application object should hold everything which is needed by the framework and everything should be retrieved from it if possible.

The reason it isn't a singleton is that you should be able to define multiple applications within a single webserver instance. It is an additional level of abstraction, which can be used for multiple (separate) application components, like for example a frontend and a backend application. Note that the code to suppport using them isn't present yet, index.php just creates a single application instance now.
The problem where was that object instantiation needs to happen from within the class, but you don't want to create a dependency with either the DiC or the required class. So this is not about deps, it is about a class requesting an instance of "something" without defining what that "something" is.
I would like to see your suggestions for an alternative to create objects trees, so you can access a parent or child objects.
I agree, I think for most services that is already the case.

In this case the application itself is still a singleton. You should not be able to fetch whichever application in an environment, only a specific one.
In most cases the injection factory simply gets an instance from the DiC.  So I don't really get the point.
Have to think about that
Noop

No, there can and will be multiple application objects simultaneously. This has not been implemented yet, but is required functionality
Same as above. The code that is there is needed to make it work, it is not the final code. I'm not referring to the current codebase, but again, to the required functionallity.
Ok
Can you be more specific, maybe I misunderstood you.

Can you explain me this (with a possible use case)? It seems illogical to me (though it might make sense, I just don't get it)
IIRC we already talked about this InjectionFactory thing. At that time you said you didn't like it. Same as above: I don't see the benefit while it adds extra complexity (which might make sense again)
No more comments, just a joke (noop) ;)

I always have the feeling that the reason why fuel is not so popular is that there are some parts of it which are too complex. Then I always realise that there is a reason for that and makes fuel better than its competitors. That said, the complexity is still an issue for some people. If we could clarify things (even in the docs) than it would be awesome. You see, even me, a massive fueler (working with fuel EVERY SINGLE DAY) have some questions like these.

You can see it as an additional level of abstraction within the application. For example, all our applications consist of two parts: a frontend  (one or more) and a backend (one or more). The are defined as separate applications, and either run in the same virtualhost, or on a different one, even on a different machine. This allows for instant scaling without a single change to the application. They may not be aware of each other at the PHP level, and communicate through an API using HMVC alike calls. This is all transparent for those using only one application. The application class is already prepared for this, there is no HMVC mechanism for it yet.
I totally agree with you on the factory uglyness. What I'm saying is that the target class (the class now using the factory) may not be tightly coupled to the DiC, and may also not be tightly coupled to the target class (the class it wants a new instance of). And this is the problem the factory currently solves (for the moment thru hardcoding, but obviously it has to use the DiC to request instances).
Complexity is never good. On the other hand, every toolbox contains tools that are more useful that others for a particular person. The challenge is that tools you don't use should be in your way. Like for example Theme in v1. If you don't need it, don't use it, and you won't know is there.
This also applies to the entire application discussion: it your apps only need a single Application object, why worry about the fact there may be more?

Damn, firefox crashed and my little novel went away. I am not going to rewrite the whole, but only the most important parts.
 (Proof) It breaks the whole dependency injection thing. I still think it is a mistake to put bootstrapping logic into the application ctor. (The situation: the application uses the container to resolve resources which has dependencies which are not there because the Application injects them later. WTF?) This circular dependency thing makes me crazy.
Secondly: I made some code cleaning in the whole project, standardized dockblocks, removed some legacy code, fixed some issues, etc. It was a good experience because I got an overall view of the framework, but also showed me that we have much work left.
Last but not least: along with code cleaning I cleaned up a few repos as well (I mean project files, readme, etc). I am going to standardize these things a bit so we can be consistent about how repos look like. However you should take a look when you have some time. ;)

Agreed with the 'it sucks' part. :laughing:
The issue here was:

We don't want classes to have a dependendy to the DiC itself
We don't want classes to have any dependency to any other classes
We need a solution in which a class can create new class instances at runtime without dependency

This means you can not:

inject a DiC instance
use new ClassName to create a new instance

And you're stuck. This was the only solution Frank could come up with at the moment, to handle the requirements, and fix a blocking issue. It was never meant to be a permanent solution (the InjectionFactory class violates the same rules), so if you have a better solution, I'm all :ear's.

We don't want classes to have a dependendy to the DiC itself

Why is that? Also, currently classes ARE resolved from the DiC. InjectionFactory uses it internally.
In this particular case (view manager) I don't see why it can't be resolved from the dic. Everything would be a lot more easier. And it doesn't mean the application cannot alter the state.
So I think I either don't understand or disagree with the arguments which led to this injection factory thing as a solution.

Perhaps I wasn't clear enough.
The InejctionFactory is NOT a solution, it is a workaround for a problem we had no solution for at the moment it was written. And it blocked the rest of the foundation package. I know the factory uses the DiC, that was the part we didn't have a solution for, and at least it meant the classes themselfs don't have a dependency on the DiC.
What we didn't want at the time was:
class Someclass
{
    public function __construct($dic)
    {
        $instance = $dic->resolve('SomeOtherClass', array('params'));
    }

because that makes  Someclass dependent on the DiC. But you also can not inject an instance of SomeOtherClass, because at the time SomeClass is instantiated, you don't have the params you need to pass to the SomeOtherClass constructor yet. Frank wanted to option of be able to use a third-party DiC.
Now, if we say we don't have that requirement anymore, and define some interface any DiC most implement, we no longer need the factory but can have the class resolve itself. But then I still would like to decouple the class from the DiC, by using an abstraction layer.
namespace FuelPHP\Foundation;

class DiC
{
    public function  __construct($externalDiC)
    {
        $this->dic = $externalDiC;
    }

   public function resolve($class, $parms)
   {
        // use an external DiC method to get an instance of some sort
        return $this->dic->findAndInstantiate($class, $params);
}

Then we can inject an instance of this class in all FuelPHP classes requiring DiC access, and still have sufficient abstraction. If you want to use a different DiC, just write a new class that functionality does the same, but interfaces with the other DiC. No changes needed to FuelPHP classes then.

Well, I see some things now. (For the record: I strictly typehinted our implementation for now where a container is injected, we can change it back later if needed).
Actually I would like to see class instantiations moved out of the Application object. But I see now that the state is not always available, so we have to find the point in the application where we have the state (config, etc) available, but still outside of the Application constructor.

Ok, further thinking about it, my primary issue is (strongly tied to the code) that some of the initialization code is placed in the constructor, which means it won't be available in the dic until the constructor finishes, but in some cases we want to get it during the constructor is running.
So how about breaking things into two parts: create the application object, save it into the container and do initialization afterwards. I am not sure if it solves all of our problems, but does a few which causes me headache in the past few days.

@WanWizard what do you think about this? It would save us from a lot of DI bullshit.
$app = new Application;
$dic->add('application::'.$name);
$app->initialize();

Currently the initialization logic is full of circular dependencies: depending on application when it is not even in the dic, etc. This would make the app available in the container, however if someone tries to use a feature before it is initialized....that person deserves what he/she get. :stuck_out_tongue_winking_eye:

I am open for any improvement. :smile:
However, there is reason for the current madness, so you have to be careful when stripping existing functionality. Most objects are tied to an application object. Take for example the ViewManager, if you need that, you need to be able to get the Application instance from the DiC first. Which is impossible in your example unless you know the name (which you usually don't). This is the reason the first app object is also stored as "application::main".

Right. But how does it related to the solution above? The difference is that the application is available in the DIC before initialization logic. Actually, some application dependencies require the application in the dic. The only thing we have to care about is to don't rely on something which is no available in the application object at that time. For example parsers in display require a view manager instance which is resolved by the dic. When parsers are requested from the dic, the application is already available in the dic, so as the view manager. Problem solved.

Related to injection factory thing: I like the way how event emitter does this: it has a trait which exposes a getter and a setter for an event emitter. If no custom implementation is set, a default implementation is instantiated (and set) upon first usage.

No problem with the solution above, just highlighting a possible issue with having an un-initialized object in the DiC.

That problem currently exists as well. Actually this lowers the chance of a not found object.


Any way to get the current name of the folder related to a specific msg ?

Hi,
I am working with Gmail and I need to know the name of the folder related to a specific msg.
Any clue ?
Thanks.
Nelson.

@Wu4m4n I could not find in the IMAP library a way to grab the folder containing a message directly so I submitted PR #92 that recursively finds it
Usage:
$folder = $message->getContainingFolder();


Verify and support Node 4.*

https://nodejs.org/en/blog/release/v4.0.0/

We'll need to determine when Node 4 is solid enough to be a fully supported engine.
Switching to Node 4 as a required engine will mean dropping some current library dependencies in favour of Node.js 4 built-in support and some resulting refactoring as well as refactoring to take advantage of E6 and ES6-friendly refinements to the interface.
Flipping it back to an RFE because of the interface aspects of the adoption.

@ehennum - Many project choose to support Node 4 in a phased fashion.

Basic Compatibility: targeting a current stable branch, and only requiring a minor version bump.  This phase may include upgrading/enhancing dependencies to have basic Node 4 support.
Enhancement: taking advantage of a more robust API.

Is there opportunity to get to Basic Compatibility in the short-term?  Doing so could help applications that are otherwise prevented from upgrading to stable/supported Node.

@robcolburn - we want to support performant and reliable enterprise production deployments. I'm guessing Node 4 will be shaking out side effects of the IO / Node merge for a while (but I would be happy to be wrong).
I did run our basic tests on Node 4 a few weeks ago, and they all ran green. So, even if we're not ready to recommend Node 4 for production, experiments might work in the short term.

@ehennum,
Yes, I'm actually targeting an enterprise production deployment for my corp. ;)  We have a project that integrates ML in addition to other API's.  Personally, I don't work on the ML pieces of that project, but it seems our only issue upgrading is the engine warning during install.  If your tests are green, I'll ask my team-mates to run their tests as well. Thanks!
If we do run into minor/fixable compat issues, can I throw a PR your way? If so, should I target master branch?

@robcolburn - It sounds like you're not running into any significant issues with Node 4, which is an interesting data point. Yes, please feel free to submit a PR.  Here's what we request:
https://github.com/marklogic/node-client-api/blob/master/CONTRIBUTING.md
The develop branch is pretty stable at this point because 8.0-4 is expected out in the near term (with forward looking caveats).

Just want to put some details, ran qa tests with 4.0.0 and it's green too

adding another data point;  ran bugtrack node tests (total 294), all of them passed. Used v4.2.1.

Stating the obvious, the engine has to change:
https://github.com/marklogic/node-client-api/blob/develop/package.json#L38

The package.json file has been updated.

Please revert the change on master and make the change on develop, then we will push it to master


Hypergan produces only black samples

Hello,
when training Hypergan on my custom dataset, it saves exclusively black images to the samples folder. I suppose I must have done something wrong. Does anyone have an idea where my mistake you be?

Hi, please try again with hypergan 0.10 as it's more stable.


One liner for generation of image for Raspberry / Raspberry support

I wanna have something like -
eden config add raspberry_conf
eden config set raspberry_conf --key eve.devmodel--value raspberry
eden config set raspberry_conf --key eve.ssid--value NPC_network
eden config set raspberry_conf
eden setup

and get an image that I need to transfer to SDcard
Then I power raspberry on, it connects to wifi (is able to connect to WPA wifi) , I run eden start and use eden pod deploy commands to deploy something on raspberry

Now I have it


Use output statements to generate .dump.expected file

The access1 test is taken from the souffle tests. The plan is to remove it in the future and to automatically download all tests when running tests. But I have submitted it so we can test the new functionality before we have the download code.
Also TBD is the concatenation of all tests into a single big one.

I will close this PR, and I will submit a new one more complete.


Add Chronograf Chart

Signed CLA and fulfilled all the requirements. Any feedback is more than welcome!

@k8s-bot ok to test

Chart installs without issue, able to access UI. UX LGTM

Thanks @jackzampolin!


Generalize the Touch gesture

multiRub and multiBrush are currently initialized as fixed-sized array of [4], the logic can be updated to support dynamic arrays.

[ ] generalize gestures like rub and brush (1 DoF)
[ ] update Touch class to support dynamic arrays?

Isn't this a duplicate of #16 ?

Isn't this a duplicate of #16 ?

oops - just added to the other description and will delete this @edumeneses


Edit AboutUs-Yong Zhe

Closes #25

Closes #25

LGTM!

Have merge conflicts, please check AboutUs.md. Thanks!

LGTM!


Birthday Sample, does not populate birthday.

Sample (which sample are you having trouble with)
Birthday List Formatting Sample
https://github.com/pnp/List-Formatting/tree/master/view-samples/birthdays
What Should Happen
Birthday should be display as expected. Birthday value is not displaying as expected on the Birthday custom view. Birthday is a required field. Column type is date and time as suggested.

What Actually Happens

Birthday value does not display on the custom view.
Confirmed that all spelling is correct include case sensitivity.
Confirmed that column ordering or positioning is the same as explained on the Readme.md
Kind regards,

Hi @AkeelEdwardss !
I tried it in my environment and the BirthMonthDay value is displayed.

There are two possible reasons why BirthMonthDay values are not displayed.
Cause 1: The view does not contain a BirthMonthDay column
If the view does not contain a BirthMonthDay column, the values in the BirthMonthDay column will not be displayed. Please check to see if the view contains the BirthMonthDay column from the [Add or remove fields].

Cause 2: The internal name of the column is incorrect
If the internal name of the column is not BirthMonthDay, the value will not be displayed. The internal name of the column is the name used when the column was created, not its display name.
You can find the internal name of the column in the URL on the Edit Column screen; the value after Field= is the internal name of the column. Please check this.

If the internal name is incorrect, try re-creating the calculated column. (Unfortunately, the internal names of columns cannot be changed after creation.)

Hi  @tecchan1107,
I appreciate your insightful response.
Cause #2 was my issue particularly. The internal comment name was set to "BirthMonthDay1" as an accident. That leads me to discover another issue. The birthdaymonth column is a calculated column yet it appears the list webpart formats it incorrectly.
The date and time format is displayed:

Tabular view displays the birthday correctly:

While the column data format is set to date only:

That leads me to discover another issue. The birthdaymonth column is a calculated column yet it appears the list webpart formats it incorrectly.

It may be because the type of the aggregate value column is set to a date column. Please try changing the aggregate value column type to a single line of text column.

That fixed it. Thanks @tecchan1107!

Resolved


Use GPU when generating bitmaps

I am using SkiaSharp to generate bitmaps in a .NET Standard project. I would like to use hardware acceleration but it looks like all the hardware accelerated surfaces are in the platform dependent views. Do you have any advice how to do this? Is there perhaps a hardware accelerated surface in the core? Is this possible at all? Should I inject the platform dependent view? Or use bait and switch?

Using the GPU to construct images is slightly different: bitmaps are raster based, so this is a pure CPU/memory process.
To create a GPU-backed image, you need to first set up a GL context as you would if you were just using normal OpenGL. Then, you instantiate the GRContext to create a surface.
I do this automatically for views, but for headless/.NET Standard libraries, you can have a look at what I do for my GPU tests:
For a Mac test to set up the OpenGL (or rather CGL): https://github.com/mono/SkiaSharp/blob/v1.60.0/tests/Tests/GlContexts/Cgl/CglContext.cs
Once the context is created, you can just create the SKSurface:
// create the context
var grContext = GRContext.Create(GRBackend.OpenGL);

// create the surface
var surface = SKSurface.Create(grContext, true, new SKImageInfo(100, 100));

// get the canvas for drawing
var canvas = surface.Canvas;

I really want to create a .NET Core app that uses the GPU and OpenTK (for example), but I just haven't had the chance to get to it yet.

Thanks a lot. I will try to create a sample my self. Maybe you can use it.

That will be great!

Closing this as it appears to be "resolved" - if a question can be marked as such.

@pauldendulk have got an example you could post?
I`m in the same situation
https://stackoverflow.com/questions/53360854/skiasharp-drawing-image-with-gpu-acceleration

@aspecialkey I did never get around to implementing this. It looks like your solution is close to how it should work. Did you try disposing all objects you create?

@pauldendulk  disposing the object makes no difference


Add missing packages for test suite to run

There were a bunch of missing packages that are require to run jest which I've added in.
I've updated the npm test script to use a relative reference to jest so that we can fix the jest version and don't require global package installation.
I've also added an .editorconfig so that editors that support it will properly format the code.

@ryanlanciaux do you think this is mergable? I assume the packages were missing on accident

As far as I can tell, all the missing packages have been added and now grunt works on a fresh checkout. What are your thoughts @ryanlanciaux on also adding in an npm run watch task or something similar to fire up grunt? Let me know if you see things missing on the PR


ver 1.1.1

Pull Request Test Coverage Report for Build 81

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 90.505%

Totals

Change from base Build 79:
0.2%

Covered Lines:
842

Relevant Lines:
902

💛  - Coveralls

Codecov Report

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

@@           Coverage Diff           @@
##           master      #17   +/-   ##
=======================================
  Coverage   94.15%   94.15%
=======================================
  Files          13       13
  Lines         513      513
  Branches       93       93
=======================================
  Hits          483      483
  Misses         30       30

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 7cf571f...2f47a8f. Read the comment docs.


Start Two Spring Boot Project Error

ERROR: This scheduler instance (86825868-6f63-4589-ba41-291d3aff6fc8) is still active but was recovered by another instance in the cluster.  This may cause inconsistent behavior.
I google this,find nothing,hope you can help me

did both instance excute the job same time?


Fetching tags before reading last tag

Current dependencies on/for this PR:

main

PR #37   👈

This comment was auto-generated by Graphite.


Add 'api' endpint

Mimic an API endpoint using a static json file

Apps data is now available in this json file.


DarkComboBox Not Drawing Correctly

The DarkComboBox is not drawing correctly if it is in a TableLayoutPanel cell and "Dock" is set to "Fill" and the form is resized. It seems to only draw correctly for the region that represents the original size of the DarkComboBox.
As a work around, when the DarkComboBox is created I set the width to something larger than the form will ever be (such as int.MaxValue) this draws the DarkComboBox correctly even when the form is shrunk. Example workaround code (where "comboControl" is the DarkComboBox):
comboControl.Size = new Size(int.MaxValue, comboControl.Size.Height);
Here is a screenshot of the DarkComboBox before the form is resized:

And here it is after the form is resized:

Can you confirm which version you're using? This should have been fixed by https://github.com/RobinPerris/DarkUI/pull/26

According to the NuGet Package Manager I am using 2.0.1, but if I check the reference properties or file properties of the DLL then it is 2.0.0
Not sure what is going on. I installed it via the NuGet Package Manager.

Moments after I previously commented I saw you just released 2.02 on NuGet. After installing that version the issue is resolved.
Thanks a lot!

Yeah, I was able to replicate your issue by swapping to NuGet 2.0.1. Looks like I botched the release and included an outdated DLL.
Sorry about that. 2.0.2 also includes another fix for dropdown items not clearing as an added bonus. 👍


Cut new releases in PyPI

Hey @btubbs. I hope all is well. I just noticed you're the sole owner on this project in PyPI. Would you please add me as an owner on the project?

Yep. Done.


Set the correct system property for krb5 config flie.

Clean up ember build properly

Coverage remained the same at 0.0% when pulling 1c6d5a9a7a3bc1edbed6ae64417b7948f5886427 on mars-lan:krb into aa38df3a7dbda14b6d573423af807a15fc82f856 on linkedin:linkedin.


remove prune arg in Dockerfile

Codecov Report

Merging #648 (7e5921f) into main (18e7b89) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #648   +/-   ##
=======================================
  Coverage   10.35%   10.35%
=======================================
  Files          57       57
  Lines        8101     8101
=======================================
  Hits          839      839
  Misses       7200     7200
  Partials       62       62

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 18e7b89...7e5921f. Read the comment docs.


exposing selectYears and selectMonths

There's a broken test, is that something you could take a look at?

sure, let me check

@Dervisevic tests are passing. I had to upgrade PhantomJS.

I just noticed that it is already possible to pass the options also in the current version by the following form definition:
datePicker: {
  type: 'datepicker',
  pickadate: {
    selectYears: true,
    selectMonths: true
  }
}

This PR provides then just a shortcut.

@Dervisevic is there a change to get this merged?

@Dervisevic any news?

I'm currently not available, @kornosaurus, could you take a look?

This looks good, merging this without commit b9c4d07 as mentioned in #42


Deprecating this meant losing Coffee-React syntax highlighting

I am guessing that sublime-react now maps to babel in sublime's package control. As a result, I now have no coffee+react syntax highlighting. This is especially depressing since my packages seem to auto-update. The workaround would be to manually installing sublime-react without package control to get syntax highlighting. I noticed: https://github.com/aponxi/sublime-better-coffeescript/issues/148 and people discussing whether or no to add the syntax highlighting there. I suppose there could be another separate package for coffee+react. Thoughts?
Commentary: I am all for deprecation of packages and such; however, it would have been nice to find a new home for cjsx before killing this package.

My current workaround seems to be open up the command palette and run Package Control: Add Repository then paste https://github.com/reactjs/sublime-react/tree/ec17f5dfd00eaa326dc299a4febd46cac21e7904.

The CJSX is taking care of this https://github.com/babel/babel-sublime/issues/96#issuecomment-95252964


Update Documentation

Working to improve and update the documentation.
For some reason the configuration to execute the jupyter notebooks isn't working for me locally:
execute:
  execute_notebooks: force

Any suggestions @g4brielvs?
This will eventually close #16

For some reason the configuration to execute the jupyter notebooks isn't working for me locally:

@elbeejay Thanks! My guess is that the symlink was the issue. Could you please pull and retry?

For some reason the configuration to execute the jupyter notebooks isn't working for me locally:
execute:
 execute_notebooks: force

@elbeejay Thanks! My guess is that the symlink was the issue. Could you please pull and retry?

I'm still not having any luck; symlink looks correct locally but for some reason I still get warnings like the following:
/GOSTurban/docs/README.md:: WARNING: toctree contains reference to nonexisting document 'notebooks/Tutorials/UrbanAreas_tutorials' [etoc.ref]

Unfortunately still not having luck with the notebook execution. The symlink is working as expected and it seems slick @g4brielvs, just need to figure out why the documentation isn't running the notebooks as it should... they are showing up in the locally hosted documentation just without outputs which suggests they aren't being executed

Unfortunately still not having luck with the notebook execution.

@elbeejay Because sphinx-build is being used (instead of jupyter-boook build, the configuration is conf.py. This was generated from _config_yml, but it is inert. Maybe we should remove it.

Unfortunately still not having luck with the notebook execution.

@elbeejay Because sphinx-build is being used (to generate the docs from docstrings instead of jupyter-boook build), the configuration is docs/conf.py. This was generated from docs/_config_yml, which is inert. Maybe we should remove docs/_config_yml in these cases.
Here the config on docs/conf.py
nb_execution_mode = "force"

That sounds right. I am thinking we can continue to use _config.yml and use .gitignore to stop tracking the conf.py file. Instead we can use jupyter-book to generate the sphinx configuration file in the CI docs workflow. This aligns with the warning in the jupyter book documentation on the subject.
Unfortunately it looks like the sphinx conf.py file was messed with in isolation from the _config.yml file, so I'm going to work on updating the _config.yml file so that we get a working conf.py file and eventually a working docs build.

@elbeejay Thanks! I agree totally. I'll defer @bpstewar to merge the PR though.

@elbeejay I agree totally and thank you for the changes. I'll defer to @bpstewar to when to merge the PR.

@bpstewar - any thoughts on these changes?

Added the https://github.com/kynan/nbstripout tool as a pre-commit hook to remove notebook metadata/output automatically. This closes #24.

@g4brielvs conflicts are resolved, the pre-commit stuff gets taken care of in #26, which probably also has these new conflicts I need to go resolve...


feat: health check for scheduler (ENG-2154)

PR #42 added the check for expected periodic jobs to the worker health check, but that doesn't actually help because it restarts the worker process rather than the scheduler process. This creates a health check for the scheduler and moves the periodic jobs check to that. Switching the scheduler to use supervisord like the worker will likely also make it more resilient to things like Redis reboots / hiccups.
Fixes: ENG-2154

Tested in my sandbox to confirm that the health check is running and jobs get scheduled as expected. Not sure how to test the case where a specific job drops off, but it did recover gracefully from a Redis reboot, at least.


Add microserver environment variable for hostname

Right now micro-server use InetAddress.getLocalHost().getHostName() to get hostname for registering inside application registry , but inside docker containers it gets container own hostname, so all registration finished with wrong hostname. This pull requests use environment variable host.address, that can be set  trough "-D" option and allow use host machine hostname for registration.

This is useful, I was wondering what would happen inside containers.
We should also look at making this plugin depend on the IP Retriever plugin, then in the service-registry itself we can capture the IP address from incoming requests - and investigate whether those are useful or not.


Calculate current charging speed (watt or amps)

One thing I have been missing in the official skoda app is the ability to see the current effect/charging speed. We did have a timer for "time until fully charged", and I can see that we now also has this sensor in Home Assistant.
However, would it be possible to calculate a "current charging speed", if one is not provided by the car, based on "time left", "battery level" and "max capacity"?
For instance, currently my battery level is at 98% and it is estimated 15 minutes left, and max capacity for battery is a theoretical 36.8.kWh
Some back-of-the-envelope-calculation would therefore mean:

736Wh remaining to charge (2% of 36800Wh)
15/60 = 0.25 hour
736Wh/0.25 = 2944W (2.9 kW)

Having this in a sensor would not (for me) be beneficial in home automation, but having it in lovelace would make me able to see how much of the theoretical 50kW charging-speed I get.
sensor.$carname_charging_speed_estimate?

I assume you have a Citigo then?
IIRC this is available for Enyaq that use a newer API but not for older cars.
It could be done but there's one major difficulty and that is determining what's the capacity of the given vehicle.
For some, at least my Superb iV, the charging current gradually drops as the charge increase. So no matter how I implement this it will always be a guesstimate that you might as well create yourself with a template sensor.
I'll see if I can make an example at least on how to accomplish this.

Correct, 2020 Citigo IV.
Yes, I saw it was available for Enyaq and that made me think of the option of calculating it. I looked at the data available now and max capacity was not one of them (yet) so it would have to be an option in the integration to specify this.
And yes, the current drops towards the end, naturally. Would still be interesting to be able to have a "charging curve".  From home assistant it looks like the car is updating the battery charge every 30 minutes when the battery is at < 90%, and this increases to every 5 minute as the battery is at 90-100%.  So I also know that it wouldn't be instant. But it would still be interesting to see how close to the theoretical 7kW slow charging and 50kW rapid charging one can get.

Thank you for the tip about template sensor, this might be just what I need! I'll do some reading about it.

I think I'm on to something...
`template:

sensor:

name: "Charge speed guesstimate"
state: >
{% set maxcharge = 36800 %}
{% set percentleft = 100 - states('sensor.oda_battery_level') | float %}
{% set hoursleft = states('sensor.oda_charging_time_left').split(':')[0] | int %}
{% set minutesleft = states('sensor.oda_charging_time_left').split(':')[1] | int %}
{% set totalminutesleft = hoursleft*60 + minutesleft %}
{% set chargeleft = maxcharge * percentleft / 100 | float %}
{% set chargespeed = chargeleft / (totalminutesleft / 60) | float %}
{{ chargespeed / 1000 }}
`
I get a value that is supposedly charging speed in kW

Will need some sort of failsafe and checking so that it would check if it is charging and if not display something else ("not charging").
Looking forward to some input from the rest of the community

After some experimenting I've come up with some small changes.

If the car is not charging we should display 0 (if we don't, the sensor is just listed as unavailable, probably because division by 0 or something)
correct usage of round, to round to 1 decimal.
remove unneeded "float"

template:
  - sensor:
    - name: "Charge speed guesstimate"
      state: >
        {% if is_state('switch.oda_charging', 'on') %}
        {% set maxcharge = 36800 %}
        {% set percentleft = 100 - states('sensor.oda_battery_level') | int %}
        {% set hoursleft = states('sensor.oda_charging_time_left').split(':')[0] | int  %}
        {% set minutesleft = states('sensor.oda_charging_time_left').split(':')[1] | int %}
        {% set totalminutesleft = hoursleft*60 + minutesleft %}
        {% set chargeleft = maxcharge * percentleft / 100  %}
        {% set chargespeed = chargeleft / (totalminutesleft / 60)  %}
        {{ (chargespeed / 1000) | round(1) }}
        {% else %}
        0
        {% endif %}
      unit_of_measurement: "kW"
      state_class: measurement

The interim variables can of course be eliminated, but as a way to track how I thought my way to the answer it's a good point in having them there..

After some experimenting I've come up with some small changes.

If the car is not charging we should display 0 (if we don't, the sensor is just listed as unavailable, probably because division by 0 or something)
correct usage of round, to round to 1 decimal.
remove unneeded "float"

template:
  - sensor:
    - name: "Charge speed guesstimate"
      state: >
        {% if is_state('switch.oda_charging', 'on') %}
        {% set maxcharge = 36800 %}
        {% set percentleft = 100 - states('sensor.oda_battery_level') | int %}
        {% set hoursleft = states('sensor.oda_charging_time_left').split(':')[0] | int  %}
        {% set minutesleft = states('sensor.oda_charging_time_left').split(':')[1] | int %}
        {% set totalminutesleft = hoursleft*60 + minutesleft %}
        {% set chargeleft = maxcharge * percentleft / 100  %}
        {% set chargespeed = chargeleft / (totalminutesleft / 60)  %}
        {{ (chargespeed / 1000) | round(1) }}
        {% else %}
        0
        {% endif %}
      unit_of_measurement: "kW"
      state_class: measurement

The interim variables can of course be eliminated, but as a way to track how I thought my way to the answer it's a good point in having them there..

Looks good!
I will give it a try as well and if OK with you I'll add it to README?

Looks good!
I will give it a try as well and if OK with you I'll add it to README?

Sure thing! And thank you for the tip about the template sensor. I'm a new home assistant user (but have been running fibaro and doing programming for years), so I have much to learn.
Unfortunately python is not my forte, or I would be able to contribute more.


Wallet resets when you reinstall the app

If you reinstall the app, it deletes the old wallet

Yes, I encountered the same problem, do you think data could be saved somewhere securely (cloud/pc storage)?


Documentation on Installing RISE locally and in the container

RISE released a Jupyterlab extension version on 12/11/2022.
The repository is: https://github.com/jupyterlab-contrib/rise.
We can run pip install jupyterlab-rise to install it.


how to process download Voxceleb2 data

I have downloaded Voxceleb2 datasets from student email, including mp4 and txt file. what should i do next to train TPSMM. [video-preprocessing] scripts seems not match to deal with the download datasets.

Where did you get Voxceleb2 videos, could please provide me a download url?


used urllib2 instead of requests

requests is not working with other applications such as google appengine.
ref: http://stackoverflow.com/questions/9604799/can-python-requests-library-be-used-on-google-app-engine/28544823#28544823
Suggest any change in code required.
Note: Also fixed some pylints.

I'm pretty sure you can use requests on GAE. It was a conscious decision to use requests library. Requests is a widely use package and it simplifies lots of things. You can use the old pypi package of python-gcm if you want urllib2 support.


[Statistics] Add a frontend counter for Swift 6 errors diagnosed via warnUntilSwiftVersion(6).

This is useful for gathering how many Swift 6 errors a project has without scraping the diagnostics output for the text ; this is an error in Swift 6.
For example, to gather all concurrency diagnostics that a project will have when enabling Swift 6, you can build with -strict-concurrency=complete -stats-output-dir <path-to-dir> where <path-to-dir> is the path to output the JSON file. In the JSON file, the value for "Sema.NumSwift6Errors" is the number of errors Swift 6 errors diagnosed, which includes errors that are downgraded to warnings in Swift 5 mode.

@swift-ci please smoke test

@swift-ci please smoke test


NamedCommands::registerCommand will crash depending on static initialization order

Describe the bug
When calling NamedCommands::registerCommand(), the static vector namedCommands might not be initialized based on the order of compilation.
https://en.cppreference.com/w/cpp/language/siof
To Reproduce
Steps to reproduce the behavior:

Create a named command in C++ and call registerCommand on it.
Hope the compiler initializes it incorrectly :)

Expected behavior
The vector should be initialized properly on the first call
Relevant FRC discord messages:
https://discord.com/channels/176186766946992128/528555967827148801/1230553097307295805

Fixed in #685


DMON management system

During the third year we will create a distributed management system for DMON.
It will be able to:

Scale logstash and elasticsearch instances
change configuration options

Because of the need to potentially provision additional VMs could we use the Deployment service to
enact these changes?
We will provide the YAML and Chef recipes. Do you think it is feasible?

Cloudify has facility for scaling up/down, but we haven't used it in the DICE deployer yet. But we can certainly use Chef cookbooks we already have (some modificiations will likely be needed, but hopefully not too much) and employ Cloudify directly.
We will look into this.

Giuliano's comment in Bordeaux was that the dynamic scaling of the DICE services is not something he sees in the scope of the DICE project.
That said, I think that having a more distributed DMon+ELK would be beneficial already in the DICE project. So if you can provide Chef cookbooks updated to support that, we will extend the TOSCA blueprint for the DMon.


Breaking Change - error handling

ProviderEngine previously appended errors to the result object without including an error in the callback response. It will now provide an error and include the error in the result object.
so in summary:

json rpc has 1 ‘channel’, the json response blob
the callback has 2 ‘channels’, the error field and the json response blob

we had problems when we:

presented the json response channel incorrectly
presented the error field channel incorrectly

so we’ll redundantly present both channels correctly
Here is some musings on the topic.
appending the error to the result is really confusing when theres an error parameter in the callback

tim [11:45 AM]
Let me point you to the JSON RPC spec.

kumavis [11:46 AM]
im familiar with the json rpc spec

[11:46]
let me point you to the callback spec?

tim [11:46 AM]
See #5: http://www.jsonrpc.org/specification

kumavis [11:46 AM]
we’re kinda at an impasse there, theres no correct answer

tim [11:47 AM]
At that point in the code, the error object is sent back to web3. Web3 implements the spec, and expects an `result.error`. Not having `result.error` will cause other issues that hide the real problem, because your result won’t be formatted correctly.

kumavis [11:47 AM]
this is of course really a design failure of our favorite love-to-hate library

tim [11:47 AM]
kumavis: This isn’t a web3 issue, if that’s what you mean.

[11:47]
This is the broader JSON RPC spec.

kumavis [11:47 AM]
it is what i mean

[11:48]
theres more than the json rpc spec going on at this point in the stack

tim [11:48 AM]
Not the Ethereum JSON RPC. But the general JSON RPC

kumavis [11:48 AM]
theres an error first callback

tim [11:49 AM]
kumavis: At that point in the code, the provider engine has wiped its hands of anything that has happened.

[11:49]
kumavis: The provider engine implements the RPC spec, and should follow it.

[11:49]
You break dapps and web3 otherwise.

kumavis [11:50 AM]
yeah but it also implements error first callbacks

[11:50]
i dont really see how the rpc spec trumps the callback format

tim [11:50 AM]
kumavis: Where’s that error-first callback given to?

kumavis [11:51 AM]
its used in places like this https://github.com/ethereum/web3.js/blob/0ae82cf895b74b264d309d21feecbf3645713d0b/lib/web3/requestmanager.js#L80-L89

GitHub
ethereum/web3.js
web3.js - Ethereum Compatible JavaScript API

tim [11:51 AM]
(this question is meant to be rhetorical)

kumavis [11:51 AM]
and if you notice its handling the error-first case

tim [11:51 AM]
Hmm.

kumavis [11:52 AM]
though perhaps differently than if it was attached to the response obj

tim [11:52 AM]
I think `.error` is handled further up, but let me check. (edited)

kumavis [11:52 AM]
nah its that line 85-87 there

[11:52]
wells its other places as well

[11:53]
i realized this bc we actually have some failing tests

[11:53]
that we missed bc of the json error format / callback error format mixup

tim [11:54 AM]
Hmm. The only reason I’m arguing so strongly for the spec is that I’ve had the opposite problem: Missed errors because various responses didn’t comply with the spec.

kumavis [11:55 AM]
like web3 was dropping the err?

tim [11:56 AM]
If my memory serves, yes. But that `callback(null, result.result);` line doesn’t seem to back that up.

[11:57]
Let me study this code more.

tim [12:03 PM]
kumavis: Ah, I found where I ran into the issue. It’s when the provider engine is running server side.

[12:04]
Error-first callbacks are great when the provider engine and the web3 instance are running in the same context. But when running server side, you’re then requiring everything that implements the provider engine to format error responses correctly against the spec, which likely won’t happen.

[12:04]
When a badly formatted error response is sent over the wire, web3 drops it.

kumavis [12:04 PM]
why is it a platform problem?

tim [12:05 PM]
> When a badly formatted error response is sent over the wire, web3 drops it.`
(edited)

kumavis [12:05 PM]
web3 is ignorant of the wire

[12:05]
so what exactly do you mean?

tim [12:05 PM]
Ya, let me write it out more specifically.

[12:06]
1. Web3 sends a payload via an XMLHttpRequest. Properly formatted JSON blob.

[12:06]
2. When the server-side provider engine respond to it, currently (without your changes) if there’s an error, it will output a properly formatted json blob which you can send back over the wire. (edited)

kumavis [12:07 PM]
ah ok

tim [12:08 PM]
3. With your changes, whatever’s wrapping the provider engine will need to catch your errors first error, and then create a properly formatted json blob itself, which is prone to error or people just won’t do it out of ignorance to the issue.

[12:08]
4. Web3 either won’t get the error or it will get an Error serialized as a string, which will be squashed as an “invalid response” because it’s not properly formatted.

[12:08]
(done)

kumavis [12:09 PM]
done(null, result) :laughing:

[12:09]
ok so as you said, i suggest that it is the responsibility of the server thats responding to the error

[12:09]
your concern that people will not handle it correctly is correct

[12:10]
but we have that problem on the other side as well - that is, we werent even handling it correctly in our tests where we check the result (edited)

tim [12:11 PM]
kumavis: I don’t understand: The provider engine merges errors-first errors into JSON RPC errors. These errors are then handled by web3 correctly.

[12:11]
How were they missed?

kumavis [12:11 PM]
in the tests we’re looking at the error in the callback to make sure everything went smoothly (edited)

[12:12]
but things were actually broken and the error was on the result

tim [12:12 PM]
kumavis: How about a truce: Send both the error *and* the result properly formatted with an error? (edited)

[12:12]
i.e.,

kumavis [12:12 PM]
yeah, i’m considering that

[12:12]
i think it might be the best answer

tim [12:13 PM]
        resultObj.error = {
          message: error.stack || error.message || error,
          code: -32000
        }
        finished(error, resultObj)

[12:13]
Agreed.

kumavis [12:14 PM]
so in summary:
* json rpc has 1 ‘channel’, the json response blob
* the callback has 2 ‘channels’, the error field and the json response blob
we had problems when we:
* presented the json response channel incorrectly
* presented the error field channel incorrectly
so we’ll redundantly present both channels correctly (edited)

tim [12:15 PM]
Ugh. I still need to change testrpc’s error handling even if you do that.

kumavis [12:15 PM]
whysthat?

tim [12:15 PM]
            provider.sendAsync(payload, function(err, result) {
              if (err != null) {
                headers["Content-Type"] = "text/plain";
                response.writeHead(500, headers);
                response.end(err.stack);
              } else {
                headers["Content-Type"] = "application/json";
                response.writeHead(200, headers);
                response.end(JSON.stringify(result));
              }
            });

[12:15]
I don’t want to 500 on a handled error.

kumavis [12:16 PM]
yeah ill bump a major version

tim [12:16 PM]
Well, what I mean is, when I upgrade to your new version.

[12:16]
It actually makes things more complicated - because of the two channels.

[12:17]
This is the server-side perspective, of course.

kumavis [12:17 PM]
not just server side but reserializing the provider result — ill have this same issue in the dapp-extension bridge

[12:18]
server side sounds like its a node vs browser platform issue

tim [12:18 PM]
Well, JSON RPC was meant to be serialized - so there was only ever one channel to begin with. (in the strict sense; it was meant to go over the wire) (edited)

kumavis [12:18 PM]
caution: lanes merge ahead (edited)

[12:19]
the json rpc spec makes sense

[12:20]
just gets confusing when you wrap it with other standards

tim [12:20 PM]
Right.

[12:20]
I should probably try/catch my response anyway - that’s when it should 500. (edited)

[12:20]
Remove that if statement.

kumavis [12:20 PM]
try/catching async tho

[12:21]
slippery fish

tim [12:21 PM]
kumavis: Well right - that’s the only time an error won’t come through the channel I expect.

[12:21]
kumavis: Assuming we “merge channels” like you suggested, I can just rely on the result object to correctly handle the error, and I could forward that along.

[12:22]
kumavis: The testrpc should 200 when a successful request was made, even if there was an error. (because the rpc has its own error channel, and so it *was* a successful request) (edited)

[12:22]
500 only when something totally unexpected happens.

kumavis [12:22 PM]
yeah makes sense

[12:22]
want me to file an issue on testrpc

tim [12:23 PM]
Sure.

this breaking change is included in 7.0.0

If I understand this correctly, this is the proper for fix and this commit should be reversed: https://github.com/MetaMask/provider-engine/commit/159468c594a8955ff2371d1e788f2df12b4442ee

@axic good catch

reverted in 7.0.1


How would one go about utilizing this with a Edgerouter 4

Additionally, could you lend any insight into utilizing a block of static ips using eap_proxy?

I used a guide from devicelocksmith for setting things up on an ER4.  Does this help?  You may need to make some adjustments depending how you have things setup (I had to)

btw -- read through the comments on that thread as the link to downloading the wpa supplicant package as originally authored is a dead link.

@ktreese thanks!
Over the last 4 days of irregular work, I was able to have this work.
do you have any experience utilizing a block of static ip's provided by att and wpa_supplicant on the ER4?

@nikolaishields, I do not.

@Archerious I think this issue can be closed as resolved.

Glad you got it working, most of what I found from trial and error is posted on this thread: https://github.com/jaysoffian/eap_proxy/issues/18
Static IPv4 blocks are simple to setup on pfSense and Mikrotik but require more work on EdgeOS.


Removing dummy text

Fixes #125

Description:  Updated the community section with relevant text and removed all the console errors throughout the website.
Checklist

[x] I've followed the Contributing guidelines provided in the repository.
[x] I've made the changes which were demanded in the linked issue.
[x] I've tested my code on a Chromium based browser.
[x] I've tested my code on Mozilla Firefox.
[x] My code gave a clean console on debugging. (no warnings/errors)

Testimonial

https://deploy-preview-209--houseofgeeks.netlify.app

I think we should also update the respective logos of communities in this PR itself

Suggestion : For the communities whose logos are not designed yet , we can replace them with the House of Geeks logo for now.

Merging this..


Implement preferred_chunks for netcdf 4 backends

According to the open_dataset documentation, using chunks="auto" or chunks={} should yield datasets with variables chunked depending on the preferred chunks of the backend. However neither the netcdf4 nor the h5netcdf backend seem to implement the preferred_chunks encoding attribute needed for this to work.
This PR adds this attribute to the encoding upon data reading. This results in chunks="auto" in open_dataset returning variables with chunk sizes multiples of the chunks in the nc file, and for chunks={}, returning the variables with then exact nc chunk sizes.

[ ] Closes #xxxx
[x] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

Hope this is up to the standards! Please tell me if there is anything I can do to improve this PR.

@djhoese if chunks={}, the same chunks size as the on-disk file will be used. if chunks="auto", a multiple of the on-disk chunk size will be used to accommodate the dask chunk size preferences. This is in line with what is said in the open_dataset docstring as I understand it.
For our case, using chunks="auto" with this patch resulted in a significant performance boost in processing the data as compared to the main branch.

Found 5 errors in 1 file (checked 142 source files)
xarray/tests/test_backends.py:1568: error: Need type annotation for "tmp_file"  [var-annotated]
xarray/tests/test_backends.py:1577: error: Argument 1 to "contextmanager" has incompatible type "Callable[[NetCDF4Base, Any, Any], None]"; expected "Callable[[NetCDF4Base, Any, Any], Iterator[<nothing>]]"  [arg-type]
xarray/tests/test_backends.py:1578: error: The return type of a generator function should be "Generator" or one of its supertypes  [misc]
xarray/tests/test_backends.py:1599: error: Need type annotation for "tmp_file"  [var-annotated]

@Illviljan @headtr1ck  help!

I attempted to fix the type annotation problem, please tell me if there is more.

What's new now updated

The mypy failures are. related to these changes I think:
xarray/tests/test_backends.py:1559: error: "str" has no attribute "data"  [attr-defined]
xarray/tests/test_backends.py:1559: error: Invalid index type "str" for "str"; expected type "SupportsIndex | slice"  [index]
xarray/tests/test_backends.py:1576: error: "str" has no attribute "data"  [attr-defined]
xarray/tests/test_backends.py:1576: error: Invalid index type "str" for "str"; expected type "SupportsIndex | slice"  [index]
xarray/tests/test_backends.py:1610: error: "str" has no attribute "encoding"  [attr-defined]
xarray/tests/test_backends.py:1610: error: Invalid index type "str" for "str"; expected type "SupportsIndex | slice"  [index]

@Illviljan can you take a look please?

Thanks, @mraspaud !

My pleasure! thanks for merging!