Changes to make it work on Python 3 with wxPython 4.

Tested only on Linux, using KiCad with Python 2/wxPython 3 and KiCad with Python 3/wxPython 4

This looks great, thanks. I was planning to do this at some point, didn't expect it to be so easy.
I'll test this on windows and osx in a bit and merge if there are no issues.

This breaks cli usage:
Traceback (most recent call last):
  File "D:/OSP/KicadBomPlugin/InteractiveHtmlBom/generate_interactive_bom.py", line 12, in <module>
    from . import dialog
ValueError: Attempted relative import in non-package

Isn't python great? :-/
I don't see a way of fixing this without moving entry point of cli script outside of the package, which I'm reluctant to do because people are already used to this.

mm, that's bad, I didn't test for CLI usage.
What about adapting the module to use as python -m InteractiveHtmlBom boardfile.kicad_pcb?

I found a way to work around the limitation of python import system without moving the script itself. It may be not pretty but oh well. Maybe later I will reorganize directory structure and get rid of the hack.


How can I store a vector of JS object references

Summary
Is there a way I can store JS references into a vector? I have tried to store a vector of JS object but I always got an error saying explicit lifetime required. But I don't know where can I add the lifetime decorator.
Additional Details
I have an JS object which has a property 'mass'. I defined the object in rust as:
#[wasm_bindgen(module = "/class_defined.js")]
extern "C" {
    pub type Shape;
    #[wasm_bindgen(method, getter, structural)]
    pub fn get_mass(this: &Shape) -> f64;
    #[wasm_bindgen(method, setter, structural)]
    pub fn set_mass(this: &Shape, value: f64);
}

To store the JS object in rust, I create a struct called container in Rust:
pub struct Container {
    shapes: Vec<&Shape>, // complains expected lifetime parameter
}

#[wasm_bindgen]
impl Container {
    pub fn new() -> Container {
        Container {
            shapes: Vec::<&Shape>::new(),
        }
    }

    pub fn add_one(&mut self, one: &Shape) {
        self.shapes.push(one); // complains explicit lifetime required in the type of `one`. lifetime `'static` required
    }
}

I tried to add 'static to the structure definition but I have no idea how to fix the complain in the push function.

Using Vec<Shape> should work fine: the types created by wasm-bindgen are already references (at least internally), so you don't need the &.
If you want to use a Shape in multiple places, you can explicitly call shape.clone() (this is very fast, since it doesn't actually copy the object, it just increments the reference).

Thanks @Pauan for the suggestion and explanation . That does solve the problem for me.


Error deleting Role Binding on destroy

Error when running "terraform destroy" of a standard cluster with RBAC.

Cluster Type: Standard
Availability: SINGLE_ZONE
Cloud: GCP
Region: europe-west3

Error: error deleting Role Binding "rb-2PgRL": 403 Forbidden: Unable to get role binding for id: rb-2PgRL

Every resource is created as expected with "terraform apply", but I got that error when executing "terraform destroy", after that, if I execute "terraform destroy" again, it works fine and every resource is removed.
The RB is with the issue seems to be the related with the group:  group=confluent_cli_consumer_*
The github repo: https://github.com/mcolomerc/ccloud-demo-tf

Thanks for filing the issue!
Could you confirm that rerun did help? I'm wondering whether it was a glitch of one our services or something. That said, 403 might signal your Cloud API Key didn't have a sufficient permission for that operation.
I just rerun https://github.com/confluentinc/terraform-provider-confluent/tree/master/examples/configurations/standard-kafka-rbac but didn't manage to reproduce it 🤔

Thanks @linouk23 for answering.
Yes, it always fails on the first destroy, then on the second destroy it deletes any remaining resources.
I tried the standard-kafka-rbac example, using the same CONFLUENT_CLOUD_API_KEY, and it works fine for me too. In the case of BASIC cluster I have not found problems either(with the example and with my code) . So it doesn't seem like a permissions issue.
My suspicions:
I wonder if the problem could be with the resource destruction order, because that is the main difference between the standard-kafka-rbac and my code.
It could be an issue if Terraform tries to destroy the RB related to the admin service account first, (role_name   = "CloudClusterAdmin"), since it is used to create the topic?
Could be possible that it tries to delete an already deleted resource?
I'll enable TF_LOG="DEBUG" and review my code and tfstate to try to get more info.


doc: west: add guide for west completion fish and zsh

This add the user guide for west completion in fish and zsh shells.

this seems like a duplicate of #62785?

this seems like a duplicate of #62785?

Thanks, I will close the PR :)

Thanks! Let's make sure the other one gets some love for 3.5 :-)


Concurrency in the tcp_echo_server example

use wstd::io;
use wstd::iter::AsyncIterator;
use wstd::net::TcpListener;

#[wstd::main]
async fn main() -> io::Result<()> {
    let listener = TcpListener::bind("<IP_ADDRESS>:8080").await?;
    println!("Listening on {}", listener.local_addr()?);
    println!("type `nc localhost 8080` to create a TCP client");

    let mut incoming = listener.incoming();
    while let Some(stream) = incoming.next().await {
        let stream = stream?;
        println!("Accepted from: {}", stream.peer_addr()?);
        io::copy(&stream, &stream).await?;
    }
    Ok(())
}

Currently, the main example in this project is non-concurrent.
io::copy(&stream, &stream).await blocks new incoming streams.
It doesn’t make much sense to use an async runtime if streams are processed sequentially.
It would be great to see this example become concurrent.
Related:
https://github.com/yoshuawuyts/wstd/issues/17
https://github.com/yoshuawuyts/wasm-http-tools/issues/7

By the way, it seems that each new piece of data from InputStream triggers Pollable(from socket.subscribe()) twice. The first call works as expected, but the second one reads 0 data, which breaks the loop in io::copy(&stream, &stream).
This also occurs in a standalone Wasmtime environment. Is this behavior expected?

In https://github.com/Heap-Hop/wstd/blob/2f7c736c0dee60216e89047c7bf2aca6acb18535/tests/test-programs.rs#L122-L140 you're trying to read_to_end on a connection that already ended, so thats expected to no longer provide more output.
I agree we can make the example better! This crate is rapidly evolving right now but I will try to revisit that soon. I also want to rewrite the host side of the test to just use tokio instead of being kinda contorted to just use std. If you want to send a PR to fix any of these things, feel free.

Thanks for your reply!
I’m trying out futures_concurrency::future::FutureGroup, and would love to contribute as soon as I better understand your design philosophy (#17).
Regarding TcpStream, I'm sorry I didn't realize it was using read_to_end. I had only modified the original code.
One more question: who is responsible for closing the connection? Is read_to_end expected to wait indefinitely?
I’ve updated my testing to use a read, and you can observe the broken connection.
https://github.com/Heap-Hop/wstd/blob/cc3b34795842d8545d30be4a1e92bd1221a05fe0/tests/test-programs.rs#L134
https://github.com/Heap-Hop/wstd/actions/runs/11982701484/job/33411136111#step:5:272

Or you can run the tcp_echo_server example and connect to it using nc localhost 8080. Once you send any data, the connection will break immediately.

I'll have to dive into this further, I already know of at least the buffering bug in TCP streams https://github.com/yoshuawuyts/wstd/issues/23 and its likely more will shake out when we change the example to serve many connections concurrently.

#32
Here's my version of a non-blocking tcp echo server example.


style(submit-channel): improve submit channel design

A few simple CSS tweaks to design our submit channel form per it's design mocks

@Empact updated based on comments

@Empact updated

utACK 7e426eb


Support Orion RC

It would be great if you would add support for the release candidate version of Orion. It's simply an identical workflow to the Orion one, but with ./list-tabs-webkit.js "Orion RC" in the script filter.
Or perhaps there could even be a workflow variable for entering a webkit-based browser of choice...

@paulrudy you should be able to add support for this in the workflow by either copying or updating the following

Then updating the script filter and browser value

Script Filter

Variables

Yes, thank you. I discovered that was possible, but I'd also like to retain the ability to seamlessly update the workflow through Alfred gallery. I realize though that you might not want to add options for every minor version of every possible browser.
That's why I also suggested the idea of perhaps adding a variable in the workflow for whatever webkit-based browser one might be using, and perhaps the same could go for chromium browsers, Gecko, etc.

Seems like a reasonable ask. I'm open to it if you or someone wants to submit a PR


arranged mentor page

Related Issue

Closes: #514
Description of Changes
Changes:

wrote fresh code keeping previous format
utilized tailwind css to its fullest for better code readability.
added: better styles and icons
made the page fully responsive.

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Just quick UI overview:

Instead blue Icon can we have our purple color/theme color
FAQ are very big in size should be reduced..
Mobile optimization needed...
Please replace the vector(copyright issue), or change color to ours

have a look:https://mentro.tech/mentor/

Hey @anmode, I have done the needed changes according to the above feedback,

Forr the image/svg part, please have a look and tell me if this is what you were referring to. I have added a background of color purple to it.

If the image is to be changed, can you please provide me with the image/vector to replace if you have already one.

I have reduced the font sizes for the FAQ section with added responsiveness.

Made the page responsive for mobile devices.

dimensions: 410 x 722

Thank You !

Some fixes:

Color code is wrong... this is our color: #845ec2
Theme image or main vector image is not good please replace or you can create awesome animation in other PR. It will of level 3 too. ( I'll provide vector then if you are not up for animation ) no worries :)
actully i was also talking about color of icon as cohort courses from to our color.

btw it is looking nice just needs some optimization.. let me know I'll set gmeet too if need

Alright @anmode , I get it now, will make necessary changes. Can you please provide me the new image. I couldn't find one. Thanks

Sorry @rishuraj1 i took time due to grab2.0 launch..
so here : https://www.freepik.com/free-vector/pensioners-financial-literacy-finance-education-savings-management-investment-awareness-consultant-explaining-finance-system-basics-elderly-people-vector-isolated-concept-metaphor-illustration_12083567.htm#query=mentorship&position=15&from_view=search&track=sph

@rishuraj1 Need UX improvents too.. based on the page theme ( a mentor page to show what they will get from us you take refer from https://mentro.tech/mentor/, actually we have just copied same UX toh may be issue hoskta h.
2nd When I hover those services...cyan is coming.. change it to other color from this our theme pallet:

Hey @anmode made some additional changes according to above theme pallete, I have changed the bg from cyan to #FBEAFF and used #845EC2 wherever needed. also I added another section "Become a Mentor" and some text under it so the page looks filled. I plan to add another section "testimonial" inspired from the reffered website above but, will open seperate issue for that. For now, Do let me know if any additional changes are required. Thank You !

Wow looks cool, Hopefully this will be last fixes.. I'll explain in detail too... thanks for coperating

Remove the background of vector please

In this section:

icon color before hover should be white

background color of rectangular box which is light pink should be replace by darker grey then background color.

On hover remove the cyan from icon instead you can have green from our pallet.

In this section:

some fixes as box should also close on clicking anywhere on screen too.

On open you see pink background color... same here replace by darker grey then background

@anmode  , done with the changes. plz check

ok let's break this issue...
please next PR need the mobile optimization and some UX fixes as faq and testimonials....
thanks for making it!


WIP Fix 533

Work item links now include:

work items (source and target)
work item link types
work item link categories

The designs for work item links, link types, and link categories now use the JSONSingle and JSONList functions which cause updates in many places.

Just like the design/workitems.go I've outsource user types, media types, and resources to their own files:

design/work-item-link.go
design/work-item-link-category.go
design/work-item-link.go

Approve changes beyond the test failure :)

Current coverage is 69.58% (diff: 85.57%)

Merging #583 into master will increase coverage by 0.71%

@@             master       #583   diff @@
==========================================
  Files            71         71
  Lines          3967       4011    +44
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2732       2791    +59
+ Misses          974        955    -19
- Partials        261        265     +4

Powered by Codecov. Last update 1f2923e...0514ff7


standard Error traits?

Any chance of implementing the standard error traits for ipfs_api?
    pub async fn heartbeat(&mut self) -> Result<(), Box<dyn Error>> {
        let client = IpfsClient::default();
        let nodeid = client.id(None).await?;
        println!("Connected to {}", nodeid.id);
        Ok(())
    }

error[E0277]: the trait bound `ipfs_api::response::Error: std::error::Error` is not satisfied
  --> src/ipfsbackend/mod.rs:33:43
   |
33 |         let nodeid = client.id(None).await?;
   |                                           ^ the trait `std::error::Error` is not implemented for `ipfs_api::response::Error`
   |

I think it should be already. Which version and backend (hyper or actix) are you using?

default (hyper I think?)  ipfs-api version is 0.11.

Ahh okay, this should be added in the next release already. You can try pulling down the code in master and seeing if that resolves, but there might be breaking changes.


latest changes

added synced "checked" flag (strike-through)
added support for qr-code scanning and ean->product resolution
etc.
please test it out thoroughly.

We must update the APP in the fdroid store.
Am 21. August 2018 16:55:54 MESZ schrieb "Thomas E. Horner"<EMAIL_ADDRESS>
added web ui at /index.php (note: android app endpoint needs to end
with .../api.php)
added synced "checked" flag (strike-through)
added local config file support to avoid overwriting local settings on
update
added support for qr-code scanning and ean->product resolution
etc.
please test it out thoroughly.
You can view, comment on, or merge this pull request online at:
https://github.com/GroundApps/ShoppingList/pull/65
-- Commit Summary --

Fixed dependency download by upgrading gradle
Fixed dependeny
Fixed missing context in logger
Added save and update of checked attribute
Added option to scan QR code using the front camera (for a wall
mounted tablet)
Workaround for repeating items when scrolling list
Fixed parsing the backend response when deleting items
Menu access to cached list, save checkmarks in cached list
Option to hide checked items
Change front camera selection and use a checkbox
Raised compile SDK and build tools version
Added option to add item by scanning a qr code (needs backend
support)
Added option to rename and delete a selected item
Fix missing icon for add item by qr code
Fix missing close of main menu when starting qr code scan
Fix using the front camera when set in preferences
Fix keeping list position after update
Fix crash when api is already busy: Skip updating list
updated to latest gradle
updated by android studio

-- File Changes --
D .idea/.name (1)
A .idea/caches/build_file_checksums.ser (0)
A .idea/codeStyles/Project.xml (29)
D .idea/compiler.xml (22)
D .idea/copyright/profiles_settings.xml (3)
D .idea/encodings.xml (6)
M .idea/gradle.xml (2)
M .idea/misc.xml (22)
M .idea/vcs.xml (2)
M ShoppingList.iml (2)
M app/app.iml (108)
M app/build.gradle (18)
M app/src/main/java/org/janb/shoppinglist/CONSTS.java (1)
M app/src/main/java/org/janb/shoppinglist/LOGGER.java (3)
M app/src/main/java/org/janb/shoppinglist/activity/MainActivity.java
(17)
M app/src/main/java/org/janb/shoppinglist/api/ListAPI.java (15)
M
app/src/main/java/org/janb/shoppinglist/fragments/CacheListFragment.java
(18)
M
app/src/main/java/org/janb/shoppinglist/fragments/SettingsFragment.java
(2)
M
app/src/main/java/org/janb/shoppinglist/fragments/ShoppingListFragment.java
(110)
M
app/src/main/java/org/janb/shoppinglist/model/ShoppingListAdapter.java
(27)
M app/src/main/java/org/janb/shoppinglist/model/ShoppingListItem.java
(10)
A app/src/main/res/drawable/ic_delete_white_24dp.png (0)
A app/src/main/res/drawable/ic_photo_camera_black_48dp.png (0)
M app/src/main/res/layout/dialog_add_custom.xml (1)
M app/src/main/res/layout/dialog_update_item.xml (27)
M app/src/main/res/layout/fragment_list.xml (9)
A app/src/main/res/layout/list_row_hidden.xml (5)
M app/src/main/res/menu/menu_main.xml (4)
M app/src/main/res/values-de/strings.xml (6)
M app/src/main/res/values/strings.xml (6)
M app/src/main/res/xml/preferences.xml (4)
M build.gradle (5)
M gradle/wrapper/gradle-wrapper.properties (4)
-- Patch Links --
https://github.com/GroundApps/ShoppingList/pull/65.patch
https://github.com/GroundApps/ShoppingList/pull/65.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/GroundApps/ShoppingList/pull/65

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

yes we should. definitely.

Could you Marke a apk so i could test it.
Am 21. August 2018 17:00:24 MESZ schrieb "Thomas E. Horner"<EMAIL_ADDRESS>
yes we should. definitely.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/GroundApps/ShoppingList/pull/65#issuecomment-414705698

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

The last update in the store is two years old and has a security issue.
Am 21. August 2018 17:00:24 MESZ schrieb "Thomas E. Horner"<EMAIL_ADDRESS>
yes we should. definitely.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/GroundApps/ShoppingList/pull/65#issuecomment-414705698

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

@beli3ver here's the program version I use since August, sorry for missing to provide it earlier: shoppinglist-debug.zip


Add a new sensor after the default ones isn't working

Hello,
After installing the default sensors, it is not possible to add a new one (ex day+2)
Using UI, it seems fine but the sensor is not created.

Indeed, at the moment you need to remove and then re-add the integration. I'll try to add this next weekend.

Version 0.3.0 (pre-release for now) has a way to add more sensors. I could not find a way to delete existing sensors using this mechanism. Let me know if there are still issues and I'll reopen this issue.

Adding a new sensor is ok, maybe just missing a reload/refresh to update the sensor count
Thanks

It's working on my demo instance. Could you set custom_components.rte_ecowatt: debug logger config and send me the output? (take care of removing your credentials if they appear).

Either I messed up my setting or debugging doesn't provide output.


gitlab-workhorse: migrate to using buildGoPackage

Motivation for this change
Part of #52469, make the gitlab-workhorst derivation using buildGoPackage :angel:
Things done

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

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

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

This breaks pkgs/applications/version-management/gitlab/update.py, for gitlab-workhorse (like it's already broken for gitlab-shell, see description of https://github.com/NixOS/nixpkgs/pull/50962):

For some weird reason in how go packages are being built, meta.position for gitlab-shell points to pkgs/development/go-modules/generic/default.nix, so update-source-version isn't able to bump this automatically (but we show the version and hash to bump to on the console).

Since then, the discovered location meta.position seems to have moved again: `
/nix/store/5chw603011946kg8w42961zsp4p4shr9-common-updater-scripts/bin/.update-source-version-wrapped: error: Couldn't locate old source hash '1r75jj0xb4jv5fq2ihxk0vlv43gsk523zx86076mwph1g75gi1nz' (or it appeared more than once) in '/home/flokli/dev/nixos/nixpkgs-2/lib/attrsets.nix'!

I agree it makes a lot of sense to switch to buildGoPackage, but updating gitlab and all dependencies is a bit complicated to do manually - so having tooling for it is nice.
Any idea how to fix update-source-version for buildGoPackage derivations?

ohh damn :sweat: :thinking:
I'll try to look at it (after the holidays though :angel:)
Let me close this one for now then :wink:


Enhanced Block Entities: java.lang.IllegalStateException: Render layers can only be set during client loading! This might ideally be done from FMLClientSetupEvent.

Mod Name
Enhanced Block Entities
Mod Homepage
https://modrinth.com/mod/ebe/versions
Describe the bug
Game crashes when changing EBE settings
Steps to reproduce
No response
Logs
https://mclo.gs/R0u6aNO
Additional context
No response

So apparently mods do register render layers past client setup, too. I'm afraid the best way to prevent this error is to remove the check put in place by Forge. Mods can register render layers for any blocks and not just their own, so there is no way to figure out which mod called the method and let only fabric mods pass.


scene_manager.stats_manager.save_to_csv wrong key word in init file

In the init file kw argument for the csv file is path but it is an unknown argument in the function:
scene_manager.stats_manager.save_to_csv(path=stats_file_path, base_timecode=video.base_timecode)
it should be -
scene_manager.stats_manager.save_to_csv(csv_file=stats_file_path, base_timecode=video.base_timecode)

the error is not resolved:
from running -
scene_list = detect(video_path=video_path,
                   detector=AdaptiveDetector(luma_only=True,min_scene_len=300,window_width=2),
                   show_progress=True)

I get the error
  File "/home/user/miniconda/lib/python3.8/site-packages/scenedetect/__init__.py", line 193, in detect
    scene_manager.stats_manager.save_to_csv(
TypeError: save_to_csv() got an unexpected keyword argument 'path'

that references the function call -
scene_manager.stats_manager.save_to_csv(path=stats_file_path, base_timecode=video.base_timecode)

I believe the argument "path" should be changed to "csv_file" and it will fix it.
when I change it manually in your code it seems to work fine.
Thanks!!

This is fixed in the v0.6.1 branch and will be included in the next release of PySceneDetect.  You can download a development version from one of the recent builds in the meantime. Thanks!


Pandas-backed Dataset types

Pandas is the go-to library to do lots of things with data, and GluonTS should probably provide easy ways to use its data structures directly in models.
One way to do this is to provide an appropriate Dataset type that feeds from Pandas structures, and produces DataEntry objects (the dictionaries that GluonTS models use) when iterated over.
A single DataFrame as a Dataset
The simplest use case would be to be able to use a single DataFrame as Dataset, i.e. to consider each column in it as time series to train, test, or make predictions on. One could even specify a subset of the series to be used, using indices or column names for example.
This has some apparent restrictions:

All time series share the same index
It's probably hard to specify per-series features

On the other hand, this would allow doing stuff like
df = pd.read_csv("data.csv")
training_dataset = PandasDataset(df)
estimator.train(training_dataset)

which I think would be quite nice.
One DataFrame per DataEntry
This would allow to overcome some limitations of the previous approach: each DataFrame has its own index, so each DataEntry spans its own time range, and one could indicate which column(s) should be used as target, which as dynamic features.
Some limitations here would remain:

How to provide static features?

Other observations
Given that we assume uniformly spaced data, accepted DataFrames would probably need to have a DatetimeIndex type of index, such as the ones returned by pd.date_range (see here).

A long format dataframe could include any type of information in a single dataframe.
For parsing it the user would have to specify which columns are feat_static_cat etc.

date
item_id
target
product_type (feat_static_cat)
product_price (feat_dynamic_real)

2019-01-31
0
15
a
9

2019-02-28
0
25
a
7

2019-03-31
0
27
a
7

2019-01-31
1
195
b
1

2019-02-28
1
80
b
3

2019-03-31
1
114
b
2

Some recent discussion is in #1930, also contemplating the long format proposed here.


Wrong output points and parameters in gte::DCPQuery<double, gte::Segment2, gte::Segment2>

Running this code:
  auto s0 = gte::Segment2<double>({2.2352092822407803, -1.7068004885705972}, {1.4357507764403734, -4.4188128129047435});
  auto s1 = gte::Segment2<double>({1.8515323877379666, -1.5936985848524166}, {1.2171034035398707, -3.7458793566829809});

  gte::DCPQuery<double, gte::Segment2<double>, gte::Segment2<double>> query;
  auto res = query.ComputeRobust(s0, s1);

  std::cout << res.parameter[0] << " " << res.parameter[1] << std::endl;

  std::cout << res.closest[0][0] << " ";
  std::cout << res.closest[0][1] << std::endl;
  std::cout << std::endl;
  std::cout << res.closest[1][0] << " ";
  std::cout << res.closest[1][1] << std::endl;
  std::cout << std::endl;

Gives the following output:
0 5.5132038956111662e-18
2.2352092822407803 -1.7068004885705972
1.8515323877379666 -1.5936985848524166

Returned values are not one of the closest pairs.

The segments are nearly parallel. If you compute DotPerp(s0.p[1] - s0.p[0], s1.p[1] - s1.p[0]) using 'double', you get 0.0. I ran the experiments using rational arithmetic (BSRational) and the dot-perp is exactly 1.6B5E83EC2A19 * 2^{-55} which when converted to 'double' is -3.9396567657242201e-17. The distance returned from the 'double' query is 0.39999999999999980. The distance returned from the rational query and then cast to 'double' is 0.39999999999999986. Whether  the query uses 'double' or rational, the closest points are the endpoint s0.p[0] and (within a tiny rounding error) s1.p[0]. So I believe the query is working as it should.
I do not understand your comment "Returned values are not one of the closest pairs." By saying "closest pairs" (plural), you lead me to believe that there are multiple pairs. This can happen when the segments are parallel (using real-valued arithmetic) but it can happen when the segments are nearly parallel and computing with floating-point arithmetic. Concluding that you believe there are multiple pairs, it appears you have posted your image to show visually that the closest pair of the query is not a true closest pair. That is not the case.
I ran the experiment in Mathematica and it agrees the distance is nearly 0.4. The image I have posted is a plot of the 2 segments. The closest pair the query returns are the beginning points of the arrows in the image. These are certainly a closest pair.

I tried to be smart and visualize the issue, but I haven't noticed that the scales on x and y were different, so it looked like the closest points were actually at the bottom of the graph  🤦 (I'm referring to the image I posted as a comment)
And then I had a bug in another place in my code, which together lead me to believe that the bug was in the library code.
And yes, by saying that there are many pairs, I meant that the segments were parallel in float arithmetic.
I'm sorry for wasting your time on this. Next time I'll triple-check my data (and visualizations!) first.
Thank you for your explanations. And thank you for a great library.


Fix syntax in .travis.yml

travis.yml currently contains incorrect YAML syntax, which is causing the build errors (issue #26). I've reformatted and restructured it to use the latest stable Node build, then run your Gulpfile.

Fixed #45


Test SPA in Brave

This is mostly related to the JWT authentication functionality.

I have been testing this development mostly in Brave. This seems to be working just fine.


offsets is not consistent

Hi,
I'm using deepspeech.pytorch but experiencing offset inconsistency problem.
I seems returned offsets form CTCDecoder is not consistent.
Is there anyway to prevent this problem?
https://github.com/SeanNaren/deepspeech.pytorch/issues/483
Thanks in advance.

I ran into the same issue.
tl;dr - the following line is a possible cause of the issue (but it might not be the ultimate root-cause):
https://github.com/parlance/ctcdecode/blob/9a20e00f34d8f605f4a8501cc42b1a53231f1597/ctcdecode/src/path_trie.cpp#L44
this line allows overwriting the timestep of an existing trie-node at some place in the trie-tree-data-structure, with a lower value causing the timestep to suddenly drop.
I replaced this with the following guard logic (which seems to me as a cosmetic workaround, but at least it seems to work):
if ( child->second->timestep > new_timestep ) {           child->second->timestep = new_timestep; }
I tried to understand the logic behind the code, but I was able to only partially understand what is going on there. it seems that all suffixes are retained at every timestep (up to beam-width, using sort by score). during an attempt to add a new character to an existing beam (which is one of the trie-prefixes), sometimes this beam has children of it's own. if one of the children of this beam equals to the new character, then the existing child-node is overwritten with a new probability score, and a new timestep. however, this may cause a wrong timestep at the wrong place in the sequence.
i'm not sure why all suffixes are retained though... couldn't fully grasp that. perhaps there is a more fundamental bug there...
@SeanNaren , do you think it's worthwhile to ask the original authors?
fyi - @spakhomov

@levhaikin @kouohhashi Useful observations! I'm using the probability distribution over characters in the language for each timestep in order to extract the timestamps of space characters. I'm doing this to extract word alignments from the probability distribution. Unfortunately it looks like, given a long sequence (say a half hour audio file), I am getting timestamps that are skewed more and more starting from the beginning of the file.
At the beginning the time stamps seem reasonable, but after even a minute or so, the timestamps are offset significantly and quickly build up over time. I don't think an offset would fix as it isn't a consistent skew. This would also impact beam searching for me as that would require the time stamps.
Am I correct in thinking that the issue you guys are facing is related?

@ShantanuNair
not sure it's related directly..
I have never tried feeding the network and beam-decoder with such long sequences.. a common practice is to break the long audio into distinct, shorter utterances first, and then feed the isolated utterances into the network and decoder. this can be done using speech-detection/silence-detection for example. there are a lot of open-source tools that use simple energy based techniques to detect silences. if i'm not mistaken, the nvidia nemo kit has a neural based speech-detection mechanism.

Hi,
What update like this:
auto children_of_child = child->second->children_;
auto comp = [](const std::pair<int, PathTrie*> &x, const std::pair<int, PathTrie*> &y){
  return x.second->timestep < y.second->timestep;
};
auto first_child = std::min_element(children_of_child.begin(), children_of_child.end(), comp);
if (first_child == children_of_child.end() || first_child->second->timestep > new_timestep){
  child->second->timestep = new_timestep;
}

Above code should update timestep only in case if it is not make inconsitency in final timesteps. Of course it can require in some cases to additional iterate over all children of some node.
One think that I can not understood is that it seems that we always call method get_path_trie with nondescending values of new_timestep. So first child in vector children_ should have always the lowest timestep and more generally children should be kept in order of their timesteps, but I checked it out and it is not true. Removing nodes also should not change order and not break anything. Any idea why children may not be kept in order of timesteps?

hi,
I ended up reimplementing the whole algorithm from scratch in c++..
came to the conclusion that merging paths that have same "squeezed" form loses information that can't be recovered afterwards.
key idea was to create code that holds a list of beams in their "unsqueezed" form at all times. unsqueezed beams contain repetitions and blanks. there could be two different beams that have the same squeezed form (i.e. when blanks and repetitions are removed they are the same). for that I implemented a different custom trie class.
these beams are merged if possible at every timestep, and the one with higher probability is kept.
when unfolding through time is finished, we can back-traverse the beams in order to get the correct time-step and count for each character. it's possible because blanks and repetitions are saved in the beam. we can also compute confidence for each character because we know where it was.
there are some subtleties, but overall this works quite well.
unfortunately can't share the code because it's proprietary at this moment.. need to go through many legal hoops in order to make it public..

@levhaikin
I understand the propiertary issues in sharing code. Anyway when it is possible I would like to see your code.
How about the efficiency(computation time and memory usage), because keeping all hypothesis in "squeezed" form seems to be motivated mainly to decrease memory usage and computation time. Is it your solution comparable to original ctcdecode?
I updated my above comment about updates in the existing code.


Handling different configuration in crawls (ACHE and Nutch)

Short-term:

[x] Use default configuration for crawlers and remove all configuration fields from forms #137

Long-term:

[ ] UI/UX around different configuration mechanisms

This has to be done in order for Ache crawls to be run alongside eachother. Not sure if the UI/UX stuff is still relevant.

Right now ache is set up to allow different configs for each crawl, but I'm not sure whether it's still important to be able for a user to change these configs.

No longer necessary.


Feat/rgba

Working on the first two points made in #79, making RGB maps to RGBA and converting between RGB and RGBA for 3D/2D, respectively

The code seems to work fine, we just have to decide what we want here!
I would invert main & background traces to have them ordered as [background, main, selected] instead of the current [main, background, selected] to ensure the points in main appear on top of the ones in background.
I would also introduce named constants for traces, i.e. const MAIN_TRACE = 1; const BACKGROUND_TRACE = 0; const ALL_TRACES = [0, 1, 2] and so on.

Regarding styling, I don't think we want for the user to be able to set min/max opacity, instead I would go with fixed values of 0.3 for min and 1 for max.
On the top of this, we might want to try setting the background points color to grey instead of the main color, it might help to make selected points pop a bit more (potentially as an option? like this is done in the viewer's environment options).

The code seems to work fine, we just have to decide what we want here!
I would invert main & background traces to have them ordered as [background, main, selected] instead of the current [main, background, selected] to ensure the points in main appear on top of the ones in background.
I would also introduce named constants for traces, i.e. const MAIN_TRACE = 1; const BACKGROUND_TRACE = 0; const ALL_TRACES = [0, 1, 2] and so on.
Regarding styling, I don't think we want for the user to be able to set min/max opacity, instead I would go with fixed values of 0.3 for min and 1 for max.
On the top of this, we might want to try setting the background points color to grey instead of the main color, it might help to make selected points pop a bit more (potentially as an option? like this is done in the viewer's environment options).

I handled the first part of this in the most recent commit.
I disagree on the second part, I think users should be able to decide on opacity, especially considering it is so easy to do so.

I saw there's lots of setting coordinates to NaN around. TBH couldn't carefully inspect the whole thing but I feel very strongly that we need to steer away from this NaN trick, not add more of it.

I saw there's lots of setting coordinates to NaN around. TBH couldn't carefully inspect the whole thing but I feel very strongly that we need to steer away from this NaN trick, not add more of it.

Can you explain? The only new introductions of NaN's come in initializing the background trace, where it is empty upon initialization. I modeled it after the other empty traces added for symbols and such. No other NaN's listed in the code are introduced by this PR.

We ought to be able to initialise both additional traces with empty traces (x: [] instead of x: [NaN]), especially now that the map supports having 0 selected/highlighted points. I remember having an issue with empty trace at some point, but we might be able to workaround it.

@Luthaf Should I resurrect this?

At some point, yes! If you rebase it on top of the current master, I'll can have a new look to it


Allow repatead players classes in the same game

Codecov Report

Merging #56 (2fe3c3f) into dev (27620c3) will decrease coverage by 0.05%.
The diff coverage is 12.50%.

@@            Coverage Diff             @@
##              dev      #56      +/-   ##
==========================================
- Coverage   51.90%   51.84%   -0.06%
==========================================
  Files          28       28
  Lines        1000     1001       +1
  Branches      174      173       -1
==========================================
  Hits          519      519
- Misses        471      472       +1
  Partials       10       10

Impacted Files
Coverage Δ

pythonium/bots/pacific_player.py
0.00% <0.00%> (ø)

pythonium/bots/random_walk.py
0.00% <0.00%> (ø)

pythonium/bots/standard_player.py
0.00% <0.00%> (ø)

pythonium/game.py
23.33% <ø> (+1.45%)
:arrow_up:

pythonium/main.py
0.00% <0.00%> (ø)

pythonium/player.py
100.00% <100.00%> (ø)

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 27620c3...2fe3c3f. Read the comment docs.


Open-Source Release Status

Hi!
Welcome to QA-Board! As you likely noticed, the project is not on GitHub yet. We are working on it and are targeting Q1 2020.
What needs to be done before the release

When items marked 🌱 are done, we can pre-release the code to get early feedback.

Open-source process

[x] Authorization to release as OSS 🌱
[x] Licence (Apache 2) 🌱

Docs

[x] get started 🌱
[ ] README
[x] website
[ ] release blog post
[x] cookbook
[ ] server bringup and admin guide

Technical changes

[x] qa init creates a functional project
[x] merge the qatools and qaboard internal repositories 🌱
[ ] change some naming conventions
[x] make sure nothing is hardcoded for our infra : pass secrets at least as ENV 🌱variables or config files, and handle mount naming convention with a centralized config.... 🌱
[ ] ensure 1min server bringup with e.g. docker-compose
[ ] make a few cosmetic API changes... (output folder naming conventions with hashes, qatools.yaml->qaboard.yaml, maybe all the from qatools import * and ctx.obj->ctx)
[ ] add more tests

Features needed for the release

[ ] support for at least one common task runners beyond our infra, and explain how to implement support for  others 🌱
[ ] make it easier to debug visualizations and metrics with per-batch settings
[ ] make the info from git hosts' hooks optional, and support more providers
[ ] better docker support
[ ] support for different storage backends e.g. S3 vs NFS
[ ] remove sklearn dependency?

Hi, some updates:

Merged the two repos that composed qaboard
Added basic support for "secrets" to pass e.g. gitlab credentials.

We're getting closer to a pre-release. What's missing is creating a "master-open-source" branch with a clean history, replacing a few default / docs, and pushing it..!

Update:

there is now a fully sanitized version of the code. I'll publish it ASAP now 😌
I uploaded the website/docs to the gh-pages branch, but GitHub Pages isn't setup correctly so we'll have to wait for it to be live...

The code is online 🎉🎉🎉 !
There is still work to do, but things feel more concrete now. 🎆

The website is live https://samsung.github.io/qaboard !

Hi!
I've been making progress refactoring batches to allow more types of runners. For now the API I picked is
class MyRunner():
  type: str  # local, celery, ray, kubernetes...
  start(blocking=True)
  stop()

  @static
  start_jobs(jobs, job_options)
  @static
  stop_jobs(jobs, job_options)

  # those function would use
  self.RunContext.job_options
  # to know the selected concurrency, settings to connect to the task queue...

@amirfru hi! Any update about what you'd need?
I expect to push the branch in the next few days, possibly directly merge on master.

✨ There is now support for Celery ! https://samsung.github.io/qaboard/docs/celery-integration/
Tuning from the web application is still hardcoded to use our infra... But that will be fixed soon.

Hi! I quick update to say that we're still working on the open-source release, although we've focused more on quality of life features and small fixes this past month. Stay tuned!

Hello!
Last month we've been busy with other priorities, still some notable improvements landed:

support for "matrix" batches
filtering is now much more performant
lossless image viewer support

Hi!
I am finishing adding support for docker-compose:

the whole application stack can already be started in 1 command, and there is a structured way to specify custom ENV variables.
makes it easier to implement a public CI, host a demo server, or just have users try QA-Board.
will help us provide pre-built container images.
will provide an easy migration path to more complex orchestration tools (e.g. k8s..).
Other benefits: the app now has only seconds of downtime during upgrades, is served from a unique port, no need for cron jobs managed separately, and our internal tweaks are much more isolated.

I expect to push the changes and new docs in the coming days. Bye!

We now use docker-compose!

New guide to start a QA-Board server
Faster startup/update time, as all services are split
Everything is served from a single port, we reviewed the whole mess of reverse proxies.
The docs are available from the application at /docs
Almost all the code is the same in the OSS and our internal version.
We will shortly add in docker-compose.yml  a sample cron job doing backups

We also started using github actions to create a public CI:

the website is already updated automatically from the docs
we're building the docker images. We need to add some code to check and push them to github's docker registry. We might also upload the CLI package to pypy.

The next task is not requiring read-access to the git repositories of the users' projects - or at least support github in addition to gitlab (currently required...)

Hi!
Here are some updates:

QA-Board now doesn't require Gitlab anymore, nor read-right to projects' repositories. Using Gitlab enables nice-to-have features like showing user avatars, but we'll work on doing it with Github too.
Each batch can now have its own config and metrics, making using with qa --share much more pleasant.
If you've missed it, we now support a new visualization, flame graphs.

We're now in new territory: anyone can start using QA-board! We'll check it's as smooth as promised by the docs, and give updates.

There is now a demo server at demo.qamarks.com!

It was straightforward to setup just following the guide, so we can now feel at ease looking for users.
For now there is a single demo project comparing 2 versions of a map-based algorithm. We'll add more demos and polish it...

Some major updates:

The API was simplified:

Instead of the ugly context.obj["configurations"], there is context.configs. And so on.
Tuning comes for free, no need to worry anymore about context.obj["extra_parameters"]
For convenience there is now context.params
The docs were updated and changes are backward compatible.

Users can now save artifacts and outputs at different locations, and it's all a bit simpler to specify. Go to the docs to read more.

Those changes close the TODOs to make QA-Board "public-ready" 🚀 !
I'm closing the issue!


Figure out how to bypass Remix to execute smart contract.

We can bypass Remix to execute the smart contract using Python and a compiled smart contract.   I documented this here:   https://github.com/quinnwong31/FintechProject3/wiki/Deploying-a-Smart-Contract-with-Python

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @giodemedrano, @Arthas-sketch, @HXN2, @tiananfeng12, @murilo, @ImaniAN, @Warshoow, @herotopic, @Pravda-dev, @OuIChien, @RickyLeeie, @felipecbueno, @cicciboy, @simms21, @kushsharma2910, @okeangel, @boykac, @gutohertzog, @jamneck, @BBiering, @imtaherul, @jackliu8722, @aichizhajiang, @LeoThern, @liampgrichardson, @floydspace, @Si110n, @chiely, @kent-pawar, @fabrizioff, @fromddy, @MatteoRaffaeleDeSilvestri, @jw-y, @stevenguo001, @WorldHellooo, @quinnv8, @Banging12, @and-kul, @SoulPiercer, @Ractive89, @hongjingli, @brudnyon, @lmmsoft, @MJazz225, @kingyueyang, @CodeGueas, @dengjiang123, @SW36, @tizhproger, @0xshandy

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @


Add Cytoscape layout for the Service Graph page

Preliminary Service Graph with Cytoscape

https://issues.jboss.org/browse/SWS-73
Next steps to hook up to Jay's live data (we have already agreed on a cytoscape data format to send).
Still need to tweak look-n-feel more, add namespace selection and linking to other screens.

Hopefully, we can merge this quickly so everyone can start playing (since we don't have much time). And then address all concerns.

Should a click on node take you to the detail page or render information about that node (say in a popup info block)?

Also, in general, I guess we are going with a white background in our main page section when the patternfly sections are dark?
Seems like we should be lite or dark profile?

Because we have no real wireframe mockups everyone is just making stuff up at this point. Every developer with their own style.

White background is what we (mostly) see in OpenShift console, so +1 on white background only.
And yes, let's merge this one when reviewed that it works and improve the LnF in other iterations

Checked out the current status locally and this shows nicely. So also +1 on merging now and refining afterwards.


AKS + ISTIO 1.9 + CNI + AZURE polixy erro to create sidecar

(** NOTE **: This is used to report product bugs:
To report a security vulnerability, visit https://istio.io/about/security-vulnerabilities
To ask questions on how to use Istio, visit https://discuss.istio.io)
** Description of the bug **
Error creating the sidecar and the error message appears on the deployment:
  Error creating: Internal error occurred: failed calling webhook
  "sidecar-injector.istio.io": Post
  "https: //istiod.istio-system.svc: 443 / inject? timeout = 30s": dial tcp
  <IP_ADDRESS>:443: i / o timeout

** Affected product area (put an X in all applicable options) **
[] Docs
[] Installation
[] Networking
[] Performance and scalability
[] Extensions and telemetry
[ ] Safety
[X] Test and Release
[X] User experience
[] Developer infrastructure
[] Improvement
** Affected features (put an X in all that apply) **
[] Multi Cluster
[ ] Virtual machine
[] Multiple control plan
Expected behavior
** Steps to reproduce the bug **
Install AKS cluster with kubernetes version 1.19.9, enable CNI and use policy Azure.
Install istio using the manifest:
istioctl install -f install-istio.yaml
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: istio-control-plane
spec:
  components:
    cni:
      enabled: true
    base:
      enabled: true
    pilot:
      enabled: true
  # Use the default profile as the base
  # More details at: https://istio.io/docs/setup/additional-setup/config-profiles/
  profile: default
  values:
    global:
      # Ensure that the Istio pods are only scheduled to run on Linux nodes
      defaultNodeSelector:
        beta.kubernetes.io/os: linux
    cni:
      excludeNamespaces:
       - istio-system
       - kube-system
       - kube-node-lease
       - kube-public
      logLevel: info

Install bookinfo:
https://istio.io/latest/docs/examples/bookinfo/
https://docs.microsoft.com/pt-br/azure/aks/servicemesh-istio-install?pivots=client-operating-system-linux
** Version ** (includes the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
$ istioctl version --remote
2 errors occurred:
        * error port-forwarding into istiod-9445656d7-zggd5.istio-system: an error on the server ("unknown") has prevented the request from succeeding (get pods istiod-9445656d7-zggd5: 15014)
        * error exec'ing into istiod-9445656d7-zggd5 discovery container: error exec'ing into istiod-9445656d7-zggd5 / istio-system discovery container: error dialing backend: dial tcp <IP_ADDRESS>:10250: i / o timeout
1.9.5

$ kubectl version --short
Client Version: v1.21.0
Server Version: v1.19.9

** How was Istio installed? **
It was installed using the guidelines that are in the links:
https://istio.io/latest/docs/setup/additional-setup/cni/
https://docs.microsoft.com/en-us/azure/aks/servicemesh-istio-install?pivots=client-operating-system-linux
** Environment where the bug was observed (cloud vendor, operating system, etc.) **
Azure AKS.
Also, consider running istioctl bug-report and attach the cluster state tarball generated for this problem.
See [cluster status file] (http://istio.io/help/bugs/#generating-a-cluster-state-archive) for more details.
[istio-1.9.5 / samples / bookinfo $ istioctl bug-report

Target cluster context: aks

Running with the following config:

istio-namespace: istio-system
full-secrets: false
timeout (mins): 30
include: {}
exclude: {Namespaces: kube-system, kube-public, kube-node-lease, local-path-storage} AND {Namespaces: kube-system, kube-public, kube-node-lease, local-path-storage}
end-time: 2021-05-14 12: 51: 01.9497592 -0300 -03

The following Istio control plane revisions / versions were found in the cluster:
Revision default:
2 errors occurred:
        * error port-forwarding into istiod-9445656d7-zggd5.istio-system: an error on the server ("unknown") has prevented the request from succeeding (get pods istiod-9445656d7-zggd5: 15014)
        * error exec'ing into istiod-9445656d7-zggd5 discovery container: error exec'ing into istiod-9445656d7-zggd5 / istio-system discovery container: error dialing backend: dial tcp <IP_ADDRESS>:10250: i / o timeout

The following proxy revisions / versions were found in the cluster:

Fetching proxy logs for the following containers:

httpd / httpd-deployment / httpd-deployment-765d4d7947-n6n7x / httpd
istio-operator / istio-operator / istio-operator-c6cb49d99-dmln5 / istio-operator
istio-system // istio-cni-node-8pwn6 / install-cni
istio-system // istio-cni-node-8pwn6 / repair-cni
istio-system // istio-cni-node-8tr42 / install-cni
istio-system // istio-cni-node-8tr42 / repair-cni
istio-system // istio-cni-node-p7dxm / install-cni
istio-system // istio-cni-node-p7dxm / repair-cni
istio-system / istio-ingressgateway / istio-ingressgateway-5dc85cccdb-r76nv / istio-proxy
istio-system / istiod / istiod-9445656d7-zggd5 / discovery
nginx / nginx-deployment / nginx-deployment-7559c7bfff-ph28l / nginx

Fetching Istio control plane information from cluster.

The following fetches are still running:
  ProxyGet istio-system / istio-ingressgateway-5dc85cccdb-r76nv: certs
  PodExec istio-system / istiod-9445656d7-zggd5 / discovery: pilot-discovery request GET debug / adsz
  PodLogs istio-operator / istio-operator-c6cb4

9d99-dmln5 / istio-operator
  PodLogs istio-system / istiod-9445656d7-zggd5 / discovery
  PodExec istio-system / istio-ingressgateway-5dc85cccdb-r76nv / istio-proxy: find / var / lib / istio -name core. *
  PodExec istio-system / istio-ingressgateway-5dc85cccdb-r76nv / istio-proxy: netstat -natpw
  PodLogs istio-system / istio-ingressgateway-5dc85cccdb-r76nv / istio-proxy

Running istio analyze on namespace nginx.
Running istio analyze on namespace httpd.
Running istio analyze on namespace istio-operator]([url](url))

bug-report.zip

Same issue.

Sounds like your cluster networking has some issues. if you cannot exec into pods, api-server cannot connect to istiod, etc you may have some excessive firewall rules or something preventing things from working

@howardjohn
yea! It was the network error, but it was in the subnet configuration. I had created the subnet with enforce_private_link_endpoint_network_policies = true
When I disabled it, it worked correctly.
thanks for the contribution


help에 버전 표기하기.

https://blog.kowalczyk.info/article/vEja/embedding-build-number-in-go-executable.html


Fix authentication for calls to PACER API

PACER sent and email requesting to update all authentication requests to their API by 11/21/2021, when their new API es expected to be released:

Update Automated Authentication Requests by 11/21/21
Automated script users who have written authentication requests to automatically log in to PACER and/or CM/ECF must update these requests to meet the new technical specifications and security requirements outlined in the PACER Authentication API User Guide by November 21, 2021. These requests will fail after that date.
On September 19, the PACER authentication application programming interface (API) was released. The API simplifies the use of automated scripts to access PACER and implement new security measures.

Fixing current libraries to call the PACER API, will also imply to make changes to the calls from CourtListener.

The main change with current code is that PACER has an API to get an authentication token using user's PACER username and password.
To get the authentication token, its necesary to send a POST request with the username/password values in a REST request:
curl --location --request POST 'https://pacer.login.uscourts.gov/services/cso-auth' \
    --header 'Accept: application/json' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "loginId": "USERNAME",
        "password": "PASSWORD"
    }'

Changes to the code were made based on the documentation for PACER Authentication API User Guide:
https://pacer.uscourts.gov/help/pacer/pacer-authentication-api-user-guide


组织查看empty

组织查看empty

@hellotyty can you give an example of where this occurs? You've to change the visibility of being part of the organization to "public" for it to appear in the organisation tab

Thanks~This problem was solved when i changed the visibility "public".
                            tyty2017

<EMAIL_ADDRESS>

    在2021年06月12日 15:12，Shreyas Thirumalai 写道：

@hellotyty can you give an example of where this occurs? You've to change the visibility of being part of the organization to "public" for it to appear in the organisation tab
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/git-touch/git-touch/issues/245#issuecomment-860012802",
"url": "https://github.com/git-touch/git-touch/issues/245#issuecomment-860012802",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


Add product guide section before "Building" about prerequisites

This would include discussion of installing docker-ce in alignment with ANMS #53 and installing and using puppet to apply the anms::hostenv to the local host.

It was also found that some OSs with compatible docker have an incompatible bash earlier than v4 and cannot run the build script.


Need viewWillDisappear method in HUBComponentViewObserver protocol

Need to be able to perform tasks such as adding animations just before a component is removed from the view. Haven't found a suitable solution for this use case. Need a convent way to do this without a lot of overhead.

The Hub Framework is being phased out at Spotify, and therefore we will not be maintaining it further.


Unifi Device Tracker Issues missing from network go unknown on restart

Home Assistant release with the issue:
0.97.1
Last working Home Assistant release (if known):
0.96.5
Operating environment (Hass.io/Docker/Windows/etc.):
Docker Container from Home Assistant Repo
Component/platform:

https://www.home-assistant.io/components/unifi/
Unfi presence detection and device tracker
Description of problem:
If a device that was previously registered as a device_tracker is off the network for a period of time, and Home Assistant is restarted, they will not show as Away upon restart but instead show as missing entities in Lovelace.  Entity database still shows the tracker but it does not appear in the integration.  In States, it is missing.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# Unifi Presence Detection
unifi:
  controllers:
    - host: <IP_ADDRESS>
      site: Home
      ssid_filter:
        - 'Private Home 2'

Traceback (if applicable):

Additional information:
Ipad test - Powered on and showing at Home on Unifi

Ipad powered off, eventually marked away as it should.

Home Assistant restart shows how entity is not being re-registered as Away when starting up.

As a note, it does not seem to do this for all devices, but definitely does for quite a few of the trackers I have in place for automation of friends and family.

Here is an example of the Integration view of the device.

Can you enable and share logs? Specifically when those clients are detected and when they're not

Yes, do you want me to turn on debug level for all HA or just the unifi component?

Take those entries listed in unifi component documentation

Recreated issue with debug logging settings as noted.
Two devices used for testing and actually had different results so either device can be used to check logs.
Two log files in the zip.  One is before restart with Home and Away, the other is after restart when in Away mode.
https://www.dropbox.com/s/v858avjzfki0ug7/HA-unifi-debug-logs.zip?dl=0
Devices Used for Testing
device_tracker.emma_ipad (8c:fe:57:a7:c3:fb)
device_tracker.matt_ipad (34:ab:37:0d:07:18)
Timings
HA Started 8:24

Both devices on wifi and marked Home
Powered off devices at 8:25
Both marked away ~8:30

Restarted HA both in Away form before restart, One of two devices missing on restart.  Matt_ipad incorrect saying Home, emma_ipad saying Missing

8:33

Powered on devices

8:36
8:38 - Both marked Home

Updated to 0.97.2 and recreated test.  Results are same as expected but more consistent.  Both devices went missing again on restart.
Two log files in the zip. One is before restart with Home and Away, the other is after restart when in Away mode.
https://www.dropbox.com/s/7vxmufpg767qt7u/HA-unifi-debug-logs-0.97.2.zip?dl=0
Devices Used for Testing
device_tracker.emma_ipad (8c:fe:57:a7:c3:fb)
device_tracker.matt_ipad (34:ab:37:0d:07:18)

Timings
HA Started 9:47

Both devices on wifi

Emma iPad
Matt iPad

Powered off at 9:50

Marked Away ~9:55

Restarted HA both in Away form before restart, Both Devices Entity Not Available

9:57

Powered on devices

9:58
10:02- Both marked Home

So I believe I was able to fix this issue.  I know I tried this before but as of now, I am no longer seeing the issue.
Steps to correct:

Deleted Integration of Unifi
Removed Unifi configuration in configuration.yaml
Restart HA.
Confirmed no entities left in entity database, no unifi setup.
Setup Unifi integration inside HA
Restarted HA
Repeated test.

Only item different now is I did not add my configuration back in.  I also have deleted known_hosts file to assure it did not try and import any of the old devices.  I performed a few restarts while devices were away and they show back up as away.

Great! Lets hope that's all to it!


RAML for container based routes

RAML for container based routes

Projects
Collections
Sessions
Acquisitions

Does NOT include RAML for sub-lists implemented with ListHandler, only ContainerHandler based routes
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

closing and re-opening to trigger travis build for PR


Description of F1 score is incorrect

Says, "For example, the F1 score is a weighted average of precision and recall. ", should say "For example, the F1 score is the harmonic mean of precision and recall. "
Change needed:
- For example, the F1 score is a weighted average of precision and recall.
+ For example, the F1 score is the harmonic mean of precision and recall.

Also notable is F1 score is not a primary metric for optimization in AutoML. We may want to recommend a different metric for imbalanced data as the user can not directly optimize towards F1 score. List of available primary metrics: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-configure-auto-train#primary-metric.
Thanks to @inchiosa for noticing the doc issue.

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

ID: 441d4999-ab6f-b371-bfbc-7441f6a866c8
Version Independent ID: 3aabaf41-b1cf-5689-f358-54de7f42cbba
Content: Avoid overfitting & imbalanced data with AutoML - Azure Machine Learning
Content Source: articles/machine-learning/concept-manage-ml-pitfalls.md
Service: machine-learning
Sub-service: core
GitHub Login: @nibaccam
Microsoft Alias: nibaccam

@justinormont thank you for reporting this. I'm happy to update the document as suggested. Please provide your recommendation as to which primary metric would be best for helping users with managing imbalanced data.

This fix is being addressed internally offline. We will now proceed to close this thread.
#please-close


Add package org-autolist

Thanks for the PR, but I cannot accept it. This workflow already exists with:

C-RET (appends a new plain list item)
C-S-RET (prepends a new plain list item),
TAB promotes the current list item
S-TAB demotes the current list item

Awesome, sorry didn't realize there is an existing workflow before opening this.


Java meta-annotation not supported

[@sgalles] I'd like to be able to declare a CDI qualifier in Ceylon
[Migrated from ceylon/ceylon-compiler#2427]

I believe that this issue was already fixed in 1.2.0. Please reopen if I'm wrong.


Tests reports generated by gradle

Hello,
When i launch gradle task "connected{FLAVOR}AndroidTest" I got a tests report in html generated in build/reports directory.
I know bitrise has its own tests reports section, but is there a way we can export tests reports generated by gradle to upload it somewhere else ?
Thank you

Hi @muskacirca!
Yes, there is a way. In fact all test related steps should export their test results to the $BITRISE_DEPLOY_DIR by default.
All the more, you can also use custom solutions and export those to the Bitrise Test Report add-on. https://devcenter.bitrise.io/testing/exporting-to-test-reports-from-custom-script-steps/


Add useful information about invisibility of an element in an error message

Currently we have only a short message The element that matches the specified selector is not visible. for any cases we have.
But we can add some detected reasons why this element is invisible: display === 'none', visibility = 'hidden', we wasn't able to scroll to this element. We can even include a particular point that is invisible (the center of the element, offsetX/offsetY).

[optional] During waiting for an element we can even show a corresponding message in the Status Panel: not just Waiting for element to appear... bt something more specific.


Space needed in text around hyperlinks on OAR pages

https://openapparel.org/contribute

There should be a space before and after "your list processing" at the bottom of the page.

https://openapparel.org/settings

Noting that I went back and refreshed and this seems to have righted itself, but leaving here to check back later today, just in case.