deb-get not working on debian bookworm

deb-get issue template
Reporting a bug 🐛
Please make sure the version of deb-get you are using is up to date:
Using deb-get v0.3.5 on debian bookworm
/etc/os-release:
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
/etc/debian_version:
bookworm/sid
deb-get is not working on my system (amd64), because UPSTREAM_CODENAME gets no value (Line 2595). This fixes it for me:

diff -u /usr/bin/deb-get.org /usr/bin/deb-get
--- /usr/bin/deb-get.org	2022-08-20 01:51:22.000000000 +0200
+++ /usr/bin/deb-get	2022-09-03 15:17:19.728406939 +0200
@@ -2592,13 +2592,15 @@
case "${UPSTREAM_ID}" in
ubuntu) UPSTREAM_CODENAME=$(grep UBUNTU_CODENAME /etc/os-release | cut -d'=' -f2);;

   debian) UPSTREAM_CODENAME=$(grep VERSION_CODENAME /etc/os-release | cut -d'=' -f2);;

   debian)

  #UPSTREAM_CODENAME=$(grep VERSION_CODENAME /etc/os-release | cut -d'=' -f2);;

  UPSTREAM_CODENAME=$(grep ^PRETTY /etc/os-release|cut -d\  -f3|cut -d/ -f1);;
   *) UPSTREAM_CODENAME="";;

esac
else
fancy_message fatal "/etc/os-release not found. Quitting"
fi

+#echo "${UPSTREAM_CODENAME}"
case "${UPSTREAM_CODENAME}" in
buster)   UPSTREAM_RELEASE="10";;
bullseye) UPSTREAM_RELEASE="11";;
HTH,
joan

Can you provide the output of cat /etc/lsb-release?

I'm afraid no, because there is no /etc/lsb-release. I might point out that I installed the system from a bookworm iso (IIRC directly from Debian), then changed the setting in /etc/apt/sources.list to "testing". Perhaps that's why. Ihave /etc/apparmor.d/lsb_release, but that does not look helpful (I'll append it (anyway).
HTH, Joan
/etc/apparmor.d/lsb_release
--8<--
Note: This profile does not specify an attachment path because it is
intended to be used only via "Px -> lsb_release" exec transitions from
other profiles. We want to confine the lsb_release(1) utility when it
is invoked from other confined applications, but not when it is used
in regular (unconfined) shell scripts or run directly by the user.
abi <abi/3.0>,
include <tunables/global>
Do not attach to /usr/bin/lsb_release by default
profile lsb_release {
include <abstractions/base>
include <abstractions/python>
owner @{PROC}/@{pid}/fd/ r,
/dev/tty rw,
/usr/bin/lsb_release r,
/usr/bin/python3.{1,}[0-9] mr,
/etc/debian_version r,
/etc/default/apport r,
/etc/dpkg/origins/** r,
/etc/lsb-release r,
/etc/lsb-release.d/ r,
/{usr/,}bin/bash ixr,
/{usr/,}bin/dash ixr,
/usr/bin/basename ixr,
/usr/bin/dpkg-query ixr,
/usr/bin/getopt ixr,
/usr/bin/sed ixr,
/usr/bin/tr ixr,
TODO - many more permissions needed for this to work
deny /usr/bin/apt-cache x,
/usr/bin/ r,
/usr/include/python*/pyconfig.h r,
/usr/share/distro-info/** r,
/usr/share/dpkg/** r,
/usr/share/terminfo/** r,
/var/lib/dpkg/** r,
file_inherit
deny /tmp/gtalkplugin.log w,
Site-specific additions and overrides. See local/README for details.
include if exists <local/lsb_release>
}
-->8--
--
The soul would have no rainbows, if the eyes had no tears.
----- Original message -----
From: Natan Junges @.>
To: wimpysworld/deb-get @.>
Cc: joanarling @.>, Author @.>
Subject: Re: [wimpysworld/deb-get] deb-get not working on debian bookworm (Issue #487)
Date: Sunday, 4 September 2022 6:39 PM
Can you provide the output of cat /etc/lsb-release?
—
Reply to this email directly, view it on GitHub https://github.com/wimpysworld/deb-get/issues/487#issuecomment-1236376384, or unsubscribe https://github.com/notifications/unsubscribe-auth/A24KPGPXSCLPY7KATPTFKA3V4TGCZANCNFSM6AAAAAAQD5GOVM.
You are receiving this because you authored the thread.Message ID: @.***>

Please paste the output from cat /etc/os-release

Same issue here my output from cat /etc/os-release:
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Oops... I just rebooted my raspi (which I rarely do, hence my late "insight")
Raspian version of /etc/os-release:
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Debian version:
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
That invalidates the diff I submitted in my OP. The "cut" would have to be modified according the ID variable (or the substring of PRETTY_NAME). Hardly an elegant solution. Better idea, anyone?
Oh yes, Raspian doesn't have /etc/lsb*, either.
Joan

Debian has dropped VERSION_ID, VERSION and *CODENAME variables from /etc/os-release in base-files 12, so grepping UPSTREAM_CODENAME returns empty value on both bookworm and sid.
https://tracker.debian.org/news/1249897/accepted-base-files-12-source-into-unstable/

----- Original message -----

From: chiak597 @.***>

Debian has dropped VERSION_ID, VERSION and *CODENAME variables from /etc/os-release in base-files 12, so
grepping UPSTREAM_CODENAME returns empty value on both bookworm and sid.

It might be a good idea, then, not to rely on lsb_release too much. Both Raspbian (Bullseye) and Debian (Bookworm)
complain about missing LSB Modules, and deb-get only escapes an error because it reads from STDIN and not STDERR.
I've reworked my patch (see OP) to work on both Raspian and Debian, but I have not tested for long-term issues (i.e. packages clashing). Admittedly, elegance looks different, but that's all I could come up with.
Here we go:
--- /usr/bin/deb-get.org	2022-08-20 01:51:22.000000000 +0200
+++ /usr/bin/deb-get	2022-09-07 23:25:49.324962152 +0200
@@ -2572,6 +2572,7 @@
OS_ID=$(lsb_release --id --short)
case "${OS_ID}" in
Debian) OS_ID_PRETTY="Debian";;

Raspbian) OS_ID_PRETTY="Debian";;
Linuxmint) OS_ID_PRETTY="Linux Mint";;
Neon) OS_ID_PRETTY="KDE Neon";;
Pop) OS_ID_PRETTY="Pop!_OS";;
@@ -2592,13 +2593,17 @@
case "${UPSTREAM_ID}" in
ubuntu) UPSTREAM_CODENAME=$(grep UBUNTU_CODENAME /etc/os-release | cut -d'=' -f2);;

   debian) UPSTREAM_CODENAME=$(grep VERSION_CODENAME /etc/os-release | cut -d'=' -f2);;

   debian)

  #UPSTREAM_CODENAME=$(grep VERSION_CODENAME /etc/os-release | cut -d'=' -f2);;

  UPSTREAM_CODENAME=$(grep ^PRETTY /etc/os-release|cut -d\  -f3-4|sed 's/\/.*//g'|tr -d " 0-9()\"")

;;
*) UPSTREAM_CODENAME="";;
esac
else
fancy_message fatal "/etc/os-release not found. Quitting"
fi

case "${UPSTREAM_CODENAME}" in
buster)   UPSTREAM_RELEASE="10";;
bullseye) UPSTREAM_RELEASE="11";;

same here, debian/sid

Similar issue here after installing:
Debian GNU/Linux testing Bookworm - Unofficial amd64 DVD Binary-1 with firmware 20220829-03:47
$ cat  /etc/os-release
PRETTY_NAME="Debian GNU/Linux bookworm/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ cat /etc/lsb-release
cat: /etc/lsb-release: No such file or directory
As a temporary workaround, I changed the line to 'warn' so it will work, as the standard error is 'fatal' and aborts:

[!] ERROR! Debian Bookworm is not supported because it is not derived from a supported Debian or Ubuntu release.

I'm working on a solution.


Use file name from downloadURL instead of elemental.iso

Current version of the UI plugin defaulted the file name for Elemental OS image to elemental.iso or elemental.img (for raw image). Latest versions of elemental-operator provide a more accurate file name in the downloadURL field, so it might be better to use this file name instead.

from which operator version can we get the name from the downloadURL?

@juadk @fgiudici @davidcassany  from which version can we get the name from the downloadURL?

@juadk @fgiudici @davidcassany from which version can we get the name from the downloadURL?

Hey Alex! The file name should be present from v1.6.5, which is the current stable (just for info, from this version there will also be the option to download a SHA256 checksum of the iso).


Vanilla Java Script

Would it be possible to have pure JS plugin?
Looks like now days this could be possible.

Yes, it's definitely possible, but unlikely to happen anytime soon. I've been brainstorming about a v2 rewrite of timeago. There would still always be a jquery wrapper, but I'll consider a vanilla JS core -- that is if I ever get around to the rewrite.


Forward if blue or green is the new version for correctly retrieving data

The GitHub service updates the configuration and defines which color a new version gets - either blue or green. We need to forward this information to the evaluation phase, so we can uniquely identify the entity we want to get metrics from.

The following questions need to be discussed in a design session:

Name of the new property
Is the property mandatory? Since there is no color in case of a direct deployment.
How to deal with canary deployments?

The github-service has a branch with changes in this regard: https://github.com/keptn/github-service/tree/feature/422/active-color

the changes made in #850 enable Pitometer to retrieve metrics from the correct DT service entity

Can we close this issue then, @bacherfl ?


Make configuration, especially of listeners, more flexible.

Allows loading config from a file during startup to be disabled, useful if you prefer to configure phobos with a hash in ruby instead of with a yaml file.
Allows a separate listeners file to be specified, making it easy to run multiple phobos processes with different sets of listeners.

Hi @undergroundwebdesigns, thanks for the PR and sorry for the delay, I was in a conference last week. I will take a look and get back to you!
Thanks again!

Can you add the changes @undergroundwebdesigns?

@tulios yep, will do within the next day or two, just haven't gotten around to it yet.

Nice, take your time. Thanks

Any update on this?

I'll try and get the requested changes done sometime this week, sorry for the delay.

@tulios updated the PR with specs and a description of the new option in the README.

@tulios Any update on this one?

Wow, sorry about the delay. I missed the updates completely. It looks good to me!


Error when accessing abstract property in constructor #9230

Fixes #9230
Add an error when accessing an abstract property within the constructor of the abstract class.
This is the first Effort: Moderate issue that I have tackled and the first time I have dealt with adding a new diagnostic message, so please let me know if there is something that I overlooked.

Updated the test cases to include a callback, an inner function in the constructor, and a conditional block (Which I believe would have failed my previous approach since it was only looking for top-level access to an abstract property).

Thanks! This is a very nice addition for complex OO programs.


Created PR and Issue templates

@ArunTeltia done. I have added general PR and ISSUE (bug and feature) templates. Please review.

Looks Really GOOD, Thank you merging


Posture-Score saving in CSV with Time

A Function that saves the posture score in a csv file with the timestamp.
It will be used as report and be displayed in a dashboard for the user to see

line-diagramm;
x-axis = Time
y-axis = true or false, good posture, bad posture


Instrument Weights & Biases

Adds an optional callback that logs episode data to W&B rather than the terminal.

Note: Sorry about the changes my auto-formatters made! Let me know if they're problematic.

@Xyzrr @matthiasplappert
it seems that feature was not tagged (lst tag 0.4.2). How can i use it?
Current error:
from rl.callbacks import WandbLogger

ImportError: cannot import name 'WandbLogger'


cmd/compile: bounds and overflow checks erroneously applied to non-constant expressions

This source file is valid Go code according to my reading of the spec and go/types accepts it:
package p

import "unsafe"

var _ = string([]byte(nil))[0]
var _ = uintptr(unsafe.Pointer(uintptr(1))) << 100

But cmd/compile rejects it with:
r.go:5:28: invalid string index 0 (out of bounds for 0-byte string)
r.go:6:45: constant<PHONE_NUMBER>228229401496703205376 overflows uintptr

This is because cmd/compile tracks constant values for a larger set of expressions than the Go spec defines as constant expressions.
Theoretically, this is best fixed by just not folding expressions that aren't Go constants is the frontend. This should simplify const.go, and the SSA backend has a more thorough constant folding pass anyway.

The front-end folding does play an important role, e.g. in doing early deadcode elimination, which impacts escape analysis and inlining. So simply punting constant folding to SSA might still have performance downsides. We’d have to evaluate case by case.

Yeah, we'd still have to fold Go constants, because the language requires that.
I'm only suggesting we could stop folding expressions that involve conversion through non-Go-constant types (e.g., pointers and other nullable types). Off hand, I can't imagine real-world scenarios where dead code analysis might depend on doing that.
As far as I can tell, users would have to write comparisons like:
if []byte(nil) == nil { ... }
if string([]byte(nil)) == "" { ... }
if uintptr(unsafe.Pointer(nil)) == 0 { ... }

to be affected by this.

It seems to me it's assumed that the compiler must accept all valid code, but I'm not sure about that. Consider:
func main() {
        a := 0
        println(5 / a)
}

No problem wrt the specification, but a hypothetical compiler can prove that the code will panic on division by zero and no other side effects exists. Some compilers may give a warning, but gc does not (https://play.golang.org/p/PG7Tgkm_TCX). In this particular case, I'd see no problem if the compiler rejected the code with an error not due to specs violation.
Is there a reason to limit the compiler reported errors only to invalid-by-specs? Especially when the compiler already does some such useful checks?

@cznic That code is valid Go code. It raises a divide-by-zero panic.

That code is valid Go code. It raises a divide-by-zero panic.

Well, AFAICT, that's what I said. I'd rather like to know your thoughts about

In this particular case, I'd see no problem if the compiler rejected the code with an error not due to specs violation.
Is there a reason to limit the compiler reported errors only to invalid-by-specs? Especially when the compiler already does some such useful checks?

By "error not due to specs violation." I mean "valid Go code", which was perhaps not written clearly enough.

Is there a reason to limit the compiler reported errors only to invalid-by-specs?

I think in its default configuration, a Go compiler should accept all valid Go programs and reject all invalid ones.

Especially when the compiler already does some such useful checks?

I'm not sure what checks you have in mind. The ones I can think of are allowed by the spec.

I think in its default configuration, a Go compiler should accept all valid Go programs and reject all invalid ones.

That's an opinion I have no problem to respect. However, the question was if there's a reason to limit the compiler reported errors only to the invalid-by-specs ones. (A superset, invalid code is of course always rejected).

I'm not sure what checks you have in mind. The ones I can think of are allowed by the spec.

In the OP you wrote:

This source file is valid Go code according to my reading of the spec and go/types accepts it:
package p
import "unsafe"
var _ = string([]byte(nil))[0]
var _ = uintptr(unsafe.Pointer(uintptr(1))) << 100
But cmd/compile rejects it with:
r.go:5:28: invalid string index 0 (out of bounds for 0-byte string)
r.go:6:45: constant<PHONE_NUMBER>228229401496703205376 overflows uintptr
This is because cmd/compile tracks constant values for a larger set of expressions than the Go spec defines as constant expressions.

(Emphasizes mine)
Have I understood it correctly that it sums up as "The compiler does more checks than required by the specs and thus it rejects a valid Go program"? Because that's what I'm talking about, but maybe it's just me...?

For what it's worth, gccgo compiles the initial function with no errors.

I'm afraid I don't understand your position here, and I worry we're talking past each other.

It's safe to assume it's my fault. I'm not a native English speaker and for the better part of my life the English I'm exposed to comes from mostly texts about programming only.

 Also, programs that panic at runtime are still valid Go programs.

Agreed, but I don't think anyone here claimed otherwise.

In default configuration, Go compilers should accept all valid Go programs without emitting errors, and should reject all invalid Go programs with at least one error.

That was stated before. My response was that I respect that opinion and I asked if there's a reason to do so. Or for that matter, if there's a reason to not reject a valid program that's proven both to not have any side effects and to produce a run-time panic and which proof the gc compiler obviously is partially already capable of to a certain extent in some cases (hence this issue exists). I'm not aware of any answer to this question.

As a matter of long-term convention, the cmd/compile Go compiler (again by default) does not emit warnings either. (go/types does this too; I'm not sure about gccgo.)

Agreed, but I don't think anyone here asked for any change about this.

I can appreciate the interest in detecting a set of "valid but probably undesirable" Go code, but that task is outside of cmd/compile's intended scope, and is what tools like cmd/vet are meant to fill.

I respect the opinion that it's outside of the compiler's scope. I am trying to get the rationale for what's discussed above.
Once again, I apologize for most probably not understanding properly your writings. Thanks for your patience.
tl;dr: No problem with the current compiler's policy. Just asking about the technical reasons for limiting the compiler errors to only those caused by violation of the specs. Even in cases where any useful effect of a program provably cannot exist and the compiler can already/could easily detect that.

My response was that I respect that opinion and I asked if there's a reason to do so.

 It would only be a most-of-Go compiler.
There's nothing inherently wrong with instead building a most-of-Go compiler, but that's not our goal with cmd/compile. By accepting exactly the set of programs specified by the Go language spec, we don't need to separately document all the cases cmd/compile allows/rejects. It also means users only need to read one document to understand how programs will (or at least should) behave when compiled with cmd/compile.

And one reason to accept all valid Go programs is to simplify life for program generators.  They can generate any random valid Go code that won't be executed, without having to worry about stepping around compiler restrictions.  It's best when everybody has a clear agreement as to what is valid and what is not.

@mdempsky Thanks for the answer.

 It would only be a most-of-Go compiler.

That refers to some definition not seen here. To accept seems here to mean "produce an executable binary", right? Not nitpicking, just verifying if that's what you mean by "to accept all valid Go programs".
That's of course a possible definition, even though a different one, like "able to correctly analyze all valid Go programs etc." would work for me as well. IOW, I would not classify a compiler not producing an otherwise unusuable binary not to be by definition a compiler-for-language-x. But that's just a different opinion.
@ianlancetaylor Your example usage is actually a pretty good reason to not reject any valid program. It reminded me of my own experience with a C to Go translator and CSmith produced test inputs. I'm now convinced that @mdempsky's position is the correct one.
Thanks to both of you.

To accept seems here to mean "produce an executable binary", right?

Correct, with the further restriction that the produced binary must implement the semantics specified for the language.


fix(cli): dev command stderr text overflow on Windows, closes #3995

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[x] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
Can you check this one @FabianLars ? I'm not sure because the issue isn't happening to me anymore, even without the change :|

@FabianLars it should work now, though I fear it only hides the issue (probably in Cargo?) by limiting the progress bar to width 60.

Yeah it works. It's looks kinda weird, because it doesn't have enough space to write the currently compiling crates, but i'd rather see this than this overflow mess 👍


Display of an error that is not an error

Issue Type: Bug
Hello,
ADS shows an error here, although this view has been around for a while (more than an hour).
I have changed again from create to alter. But there is no refresh or check whether this view exists. Therefore, the error is still displayed.
Azure Data Studio version: azuredatastudio 1.40.1 (3a32679ab590c1023ab4de6f191769e7e127d25b, 2022-11-22T18:30:25.850Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Preview Features: Enabled

If you run the command Refresh Intellisense Cache does it still show as invalid?

After executing the command - even if I have just created the view - this error is no longer displayed.
Therefore, this cache should be updated automatically as soon as an object is created or changed.

Yeah, sure, no problem.


[FEAT] Filter predicates in SQL join

Adds support for things like:
SELECT * FROM a JOIN b ON a.x = b.x AND a.y > 0

Enables TPC-H q13

@kevinzwang wouldn't this be better handled in the logical plan? That'd allow us to support non equi joins in the dataframe api as well.

@kevinzwang wouldn't this be better to handle directly in the logical plan? That would allow us to support non equi joins in the dataframe api as well.
ex
df1.join(df2, on=(df1["a"] > df2["a"] & df2["b"] > 0))

@kevinzwang wouldn't this be better to handle directly in the logical plan? That would allow us to support non equi joins in the dataframe api as well.
ex
df1.join(df2, on=(df1["a"] == df2["a"] & df2["b"] > 0))

I think I agree. However,  we would potentially need to have a concept of table-associated columns in our logical plan as well as make changes to our join op struct.
I think we should definitely do it in the future, but I didn't want to broaden the scope of this PR. Additionally, I think we would still need to have SQL-specific logic to identify the join keys for each side in a query, so a lot of the work in this PR is still relevant.
Let me know what you think!

@kevinzwang wouldn't this be better to handle directly in the logical plan? That would allow us to support non equi joins in the dataframe api as well.
ex
df1.join(df2, on=(df1["a"] == df2["a"] & df2["b"] > 0))

I agree. However, we would potentially need to have a concept of table-associated columns in our logical plan as well as make changes to our join op struct.
I think we should definitely do it in the future, but I didn't want to broaden the scope of this PR. Additionally, I think we would still need to have SQL-specific logic to identify the join keys for each side in a query, so a lot of the work in this PR is still relevant.
Let me know what you think!

I think we would still need to have SQL-specific logic to identify the join keys for each side in a query, so a lot of the work in this PR is still relevant.

that sounds good for now. I think an interesting dataframe case is df1.join(df2, on=(df1["a"] == df2["a"] & df2["b"] > 0)). How would the dataframe side identify df1.a vs df2.a? Wouldn't we need similar logic to handle this case?
Additionally, how would you express this using the dsl col syntax instead of bracket notation. col("df1.a")?  or df1.col("a")

I think we should definitely do it in the future, but I didn't want to broaden the scope of this PR.

I'll open up an issue for dataframe non-equi joins just so we don't lose this!

that sounds good for now. I think an interesting dataframe case is df1.join(df2, on=(df1["a"] == df2["a"] & df2["b"] > 0)). How would the dataframe side identify df1.a vs df2.a? Wouldn't we need similar logic to handle this case?

DataFusion has a concept of a table reference in a column expression and I think we could something similar if you use df["a"] notation


fix: update parameter name for rich.syntax.Syntax

Ref: https://github.com/Textualize/rich/releases/tag/v11.0.0

breaking Syntax.__init__ parameter lexer_name renamed to lexer

Hi, I mostly just use it when I'm in the iPython repl and want to quickly know what the function is doing. Previously, I would have to either open up GitHub or go through the filesystem, but this library is quite a relief when I found it. Thanks for making it!


Import wallet with incorrect passphrase fix

In response to issue #20
When an incorrect passphrase is typed, instead of creating a new wallet it now pops up an error dialog box and lets them try again.

@Hiram-Silvey would you like me to keep this PR open or will you open a new one for the changes?

@Hiram-Silvey I'll close this. Feel free to re-open or open a new PR if you start to take another look. Thanks!


Roadmap

I think that this is great project, but it seems to be in stalled state. I don't dived deep in code so I think it would be hard to understand some things.
If anyone wants to help me PRs are welcome!
Goals

[ ] Remove requirish (implicit)
[ ] TypeScript definition
[ ] Drop 0.10 support
[x] Update TL Schema and API Layer
[ ] Review pull requests (add labels etc)

[ ] Merge all pull requests from original project

[ ] Monorepo (?)

Repos

[ ] goodmind/telegram-tl-node
[ ] goodmind/telegram-mt-node
[ ] goodmind/telegram.link

So I stuck with updating to new TL schema (implementing flags)

Got INPUT_FETCH_ERROR so i don't know how to fix it sorry

Maybe I should port Telethon?

I'm only interested in telegram-mt-node. How much work do you think is needed to get it up to speed?

I don't know really I stuck with updating to recent tl schema

I think that this project will have some break, because I can't figure out what's wrong with flag serializing and recent schema

if someone wants to help  i will really appreciate it

Checkout working version! (at least I can login!)
/cc @jploh

@jploh And what's wrong with telegram-mt-node? I am just updated layer version to 57


Enhance editing notifications to notify edits on the API directly

From @steveswinsburg on May 4, 2015 13:0
Polling notifications should respect the Sakai event system as well so we know about edits in the original gradebook. This assumes that an edit fires an event (check this). If so, we can listen for it and add it to the cache.
Copied from original issue: steveswinsburg/gradebookNG#65

The gradebook API is inconsistent in its posting of events. Some actions send the gradebook.updateItemScore event, others don't do anything.
For the event that is posted, the data is:
/gradebook/bd659b9b-4daa-403a-9b82-b5ddd38e33db/item 3bb/276aca5b-0820-4861-9046-b05e4527d952/99.0/instructor
Which translates to: /gradebook/siteid/assignmentname/studentuuid/grade/rolethatdidit

The event sending needs to be made consistent in the GradebookService
There needs to be an event listener in the GBNG business service to pick up the event. However as above the data isn't great so it would need a DB hit to pickup the rest of the details.
The event listener would then pop the editing notification into the map

not a good solution for this one. closing.


How to use flan-t5?

Is it possible to use the flan models like https://huggingface.co/google/flan-t5-base ?

Okay thanks, I had a typo and missed the "google" in the model path "google/flan-t5-base". It would be lovely to add it to the usage support like:
# load (supports t5, google/mt5, google/byt5 and google/flan-t5 models)

That sounds like a good idea.


MUI compatibility

It is not possible to use MUI.
There is an example of how to use React component. However, no one from MUI components doesn't work.
Error is thrown.
VM52664:6265 Uncaught TypeError: Cannot read properties of undefined (reading 'current')
    at jsxDEV (<anonymous>:6265:84)
    at jsxWithValidation (<anonymous>:6449:29)
    at jsxWithValidationDynamic (<anonymous>:6487:22)
    at Slider2 (<anonymous>:17033:61)
    at d.t3 [as constructor] (<anonymous>:1544:29)
    at d.O [as render] (<anonymous>:474:17)
    at j (<anonymous>:397:53)
    at w (<anonymous>:290:9)
    at L (<anonymous>:443:40)
    at j (<anonymous>:401:91)

@yuanqing - Is there any solution or this is just totally impossible?


Midstream CI changes for release 0.13

Same as https://github.com/openshift-knative/eventing-operator/pull/2
Procedure:

Push upstream 0.13 branch to this repo as is
Delete OWNERS, create Dockerfile
Push to own repo, create a PR against the release-0.13 branch

That image failed here:
https://github.com/openshift/release/pull/7812
docke...hel8/go-toolset not found: does not exist or no pull access

Gonna revert to old image

Created https://github.com/openshift-knative/eventing-operator/pull/4


Fix mouse hover over message bar

visible_to_buffer can't be used on a point from message bar, such use
of function will result in crash.
This commit fixes the regression introduced in 9dddf64.
Fixes: #2699

visible_to_buffer can't be used on a point from message bar, such use
of function will result in crash.

It seems like we've got an assert! in place which will cause the crash, is that correct? Are there other instances where there's potential for this to crash Alacritty? I'm wondering if returning a Result might be better here, though performance should be considered. But it seems like a pretty simple mistake to make.

It seems like we've got an assert! in place which will cause the crash, is that correct?

Yes, you're correct here.

I'm wondering if returning a Result might be better here, though performance should be considered. But it seems like a pretty simple mistake to make.

I don't think that returning result matters here, since we have an assert, which absolutely make sense. The only problem I see, that we don't have UI tests to catch such problems during reviews.


Social Impact Data Hack 2017 10-12 November, Tartu

Page for the event: http://sidh2017.ut.ee/
Open Knowledge Estonia will help to get the data out!
https://github.com/okestonia/opendata-issue-tracker

Inforegister will propose a topic to SIDK 2017 for construction of a model for automatically detecting corruption cases from temporal networks of organizations, persons and assets (tenders, real estate, ...).
We can provide the following data:

Board members and owners of businesses
Some features of businesses
Real estate ownership data

In addition we will benefit from the following:

Public tender data (sums, descriptions and winners of tenders)
Public sector officials/employees
Corruption cases (specific organizations and persons) for learning

Some time ago in the context of opener.ee project public tender receords were collected for years 2013-2015. Is there any update on this data?
Are there any options for getting the lists of public sector officials and corruption cases?
Also, anyone interested in participation? Contact me (peep.kungas@ir.ee).

Results here: http://sidh2017.ut.ee/blog/


Consider moving to microfab for integration tests

Microfab can currently be found at https://github.com/IBM-blockchain/microfab
It provides a very fast standing up of a fabric network, but currently doesn't provide any easy capability to deploy chaincode. We could use the approach taken by the full stack guide here https://github.com/hyperledgendary/full-stack-asset-transfer-guide/blob/main/justfile to get setup (ideally use the peer binary that's inside to microfab container rather than having to download the binary package of fabric)
However this should only be considered if microfab is released to hyperledger-labs as then it stands the same chance of being maintained as the other fabric launcher tools (and hopefully will be kept in line with test-network)

Microfab has been archived


Address feedback on Playback functionality (confusing button, starting screen, user focus management)

General feedback is that user wants playback to look as close to normal chat UX as possible.

Starting screen is very different to normal chat, it's screaming "I'm Playback". Show model selection window with only one model available might be a good solution. Note: it's very common to playback model/application that your environment does not have
We need to manage audience focus and not showing next chat message prematurely. Right now user sees next message before it's even needed that drags his attention. We either need to not show it in edit box at all (may make playback chat to look different which is not good) or make it appear after user press next.
Exit button is extremely hard to find and it's tooltip is very confusing. We need to somehow either make it noticable (without screwing the overall look-and-feel of a normal chat) or find another place for it.

Start screen

Show playback icon and prefix [Playback] for the selected model
We do not allow any interactions with the chat settings panel. We should use a prohibiting cursor and show hint "Editing conversation settings is not available in playback mode" on click
Show placeholder "Type a message..." in the main chat input. We should use a prohibiting cursor and show hint "Editing conversation messages is not available in playback mode" on click

Let's show placeholder "Type a message..." right after sending previous message and only after clicking "next message" button we will show next message preview in input.

Let's use "Stop playback" button

Figma https://www.figma.com/file/lwL5jneveZczAj5RLcLFH2/DIAL-Chat?type=design&node-id=2889%3A8558&mode=design&t=OCuYxSjnViZVHk0c-1

Verified on staging successfully.


Support setting OS (runs-on) for publish job

What
Could you/we add support for changing the runs-on setting for the publish job too?
Why
For self-hosted runners, you need to set a custom githubWorkflowOSes. It then gets set on the build job, but not on the publish job (as you've documented in the Readme).
However, since we have a private Maven repo (Nexus), we'd like to be able to publish into that using our self-hosted runners.

What if we make this behave similarly to githubWorkflowJavaVersions, where the very first one in the list is used for the publication job?

Yes, that's fine. 👍
Longer-term maybe we could revisit the "OSes" concept/abstraction, since it doesn't align entirely with how labels work for GHA runners (especially self-hosted).
See "custom labels" here to see what I mean:
https://help.github.com/en/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow

Longer-term maybe we could revisit the "OSes" concept/abstraction, since it doesn't align entirely with how labels work for GHA runners (especially self-hosted).

Oh this is interesting! I wasn't aware of the deeper details of runners. I agree the "OSes" abstraction needs revisiting. If you have some ideas on what this should look like, please open a new issue and hold forth! I can't promise I'll get to it right away, but getting it into issue form ensures that I'll eventually loop back to it.

Yes, that's fine. +1
Longer-term maybe we could revisit the "OSes" concept/abstraction, since it doesn't align entirely with how labels work for GHA runners (especially self-hosted).
See "custom labels" here to see what I mean:
https://help.github.com/en/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow

Yes, this is also what motivated the patch I recently sent.
we have selection labels like:
'self-hosted', 'teamA', 'teamB'  that we use basically for accounting on which team gets billed for the runner hours; and that has nothing to do with the 'OS' or even the matrix generation for test running...
with the patch I am able to have 'run-on' combinations that both participate in the matrix, and do not participate in the matrix but allow me to specify the additional filter.. see #16

with the patch I am able to have 'run-on' combinations that both participate in the matrix, and do not participate in the matrix but allow me to specify the additional filter.. see #16

Ah, so #16 does what I want (not filtering runners on operating system but runner labels, solving filtering on the self-hosted label in my case), but only for the Build step and not the Publish step.

@MPV yeah, it is a different enough concern in any case. I guess eventually people decide to turn off the validation and maintain the github action by hand :/
there is a line after which its dimishing returns to remap all of gh actions in sbt ...

but only for the Build step and not the Publish step.

The publish step should be doable as well. Sorry this has been a bit far down my queue to look at, but I definitely do consider it in scope.


Epic: Observability Improvements to aid reliability efforts

Reincarnation of #7999 for the next few months
Error Instrumentation

[ ] #7816
[x] #8069
[x] #8504
[ ] #8743

API updates

[ ] #7138
[ ] #8502
[ ] #8623

Clearing milestone for now.  It's not obvious any of these should be prioritized right now.


impl, refactor and test fractions and currencies

do you have a twitter profile

do you have a twitter profile

Added.


Compatible with latest storybook?

Is this plugin compatible with the latest version of storybook?

Yes it is. Let me know if you have any issues.


Vertical cursor movement stops working when terminal runs out of vertical space

Environment
Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.3.2651.0

Steps to reproduce

Open a new PowerShell terminal tab
Make sure that there are plenty of vertical space available
Run Write-Output "$([char]27)[5BHELLO WORLD"
Notice the 5 empty lines before HELLO WORLD. All is fine.
Continue running Write-Output "$([char]27)[5BHELLO WORLD" until you run out of vertical space

Expected behavior
I expect the 5 empty lines to continue showing (since we moved the cursor 5 lines down)
Actual behavior
The 5 empty lines are not shown, the cursor is not moved.

(per https://vt100.net/docs/vt510-rm/CUD.html)

I'm pretty sure that's exactly how the cursor up/down/left/right sequences work - they're constrained by the size of the Terminal viewport. @j4james sanity check me?

Ok, my bad. I misunderstood how it was supposed to work. Thank you for the explanation.


Update Gradle build to download integration tests

Issue #, if available:
Description of changes:
This pull request updates the Gradle configuration to download the main branch of the Cedar repository, incorporating integration testing in the standard build. The gradle-download-task handles the HTTP request to the GitHub URL, downloading the Zip archive of the Cedar repository main branch.
Instead of setting the integration tests path from an environment variable, the Gradle tasks extract the Cedar repository archive to the build test resources directory. This approach makes the integration test corpus available as a class path resource. Updates to the SharedIntegrationTests class resolve the directory from the class path location.
Additional changes include updating the continuous integration workflow to run on both Ubuntu Linux and macOS 14. The macOS 14 runner uses AArch64 architecture. The updated workflow installs Zig using the platform-specific package manager, and also includes the setup-java action to provide a consistent vendor and version of the JDK.

Thanks for the review @khieta! I removed the Integration Testing section and also updated the main project README.md with simplified instructions for getting started.


Edit-DDMonitor - Anomaly Monitor

Good morning, I would like to report a problem about sending a request when editing the monitor.
File New-DDQuery in C:\Users\Documents\WindowsPowerShell\Modules\poshdog\0.0.6\Private
It was necessary to insert this parameter when using the anomaly monitor.
charset=utf-8
$result = Invoke-RestMethod -Method $Method -Uri $dd_url -ContentType "application/json; charset=utf-8" -Body $Body

Hi, thank you for reporting this. Can you share the command you ran and the error message?
Thanks


Add support for T::Enumerable

This PR adds support for T::Enumerable types which behave like T::Array types when it comes to the underlying typing.

👍


BACKPORT: Do not remove containers from memory on error

Changes from upstream patch:

daemon/delete.go:cleanupContainer: Adjust to the contents of 1.13.1 version of deferred nested function.

daemon/delete.go:cleanupContainer: Don't alter return strings. Upstream uses "github.com/pkg/errors" which is not even imported in 1.13.1. Sounds like an out-of-scope change. I've just updated the PR making sure error strings remain exactly the same.

@rhvgoyal can you ack on this?

bot, add author to whitelist

@slp, I see that docker-1.13.1, daemon/delete.go is importing "errors" package. If that's the, case, there is no need to drop the change upstream made. That makes backporting future changes easier?

@rhvgoyal "That's not the errors package you're looking for"
Sorry for the bad joke. Upstream imports are these:
"github.com/Sirupsen/logrus"
apierrors "github.com/docker/docker/api/errors"
"github.com/docker/docker/api/types"
"github.com/docker/docker/container"
"github.com/docker/docker/layer"
"github.com/docker/docker/pkg/system"
volumestore "github.com/docker/docker/volume/store"
"github.com/pkg/errors"

While 1.13.1 imports look like this:
"github.com/Sirupsen/logrus"
"github.com/docker/docker/api/errors"
"github.com/docker/docker/api/types"
"github.com/docker/docker/container"
"github.com/docker/docker/layer"
"github.com/docker/docker/pkg/system"
volumestore
"github.com/docker/docker/volume/store"
Wrapf is in "github.com/pkg/errors", so we don't have it in 1.13.1.

Ok, thanks for the clarification.
LGTM


Subsample reads

We can subsample the decontaminated reads (#1) with rasusa to 150x to ensure we know the upper limit on memory usage. We could concieveably go lower, but this just copies what I did in the head to head paper.

Closed via https://github.com/mbhall88/tbpore/pull/8


fix: fixes the direction of product tour button for RTL #1634

Description
This propose a fix for #1634 issue 1.
It just simply add a new CSS/SCSS for RTL, to use flex-start
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @ghassanmas!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@ghassanmas The buttons' alignment is just fine the way it is.
flex-end does the right job aligning the buttons to the right in LTR, and to the left in RTL.
With that style, you are actually breaking the mirroring and forcing alignment to the right.
besides, the issue #1634 has nothing to do with this suggestion.

@abdullahwaheed rewritting what I wrote in slack therad in #translation-working-group.
I see what you mean, I think I though about the buttons because I barely could see the arrow, its has really low contrast and the color look simliar to it’s background…
I am debugging the issue, the thing is frontend-app-learning is using paragon v 19 but the latest is 20… so the issue might be already resovled, I tried to force frontend-app-laerning to use paragon 20 but as expcted it failed, bceause there are breaking changes. hence: https://github.com/openedx/paragon/releases/tag/v20.0.0
It’s worth bringing up the question to #frontend-working-group, about having default MFEs to support new version of paragon.

@ghassanmas Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


[NG] textarea component

This introduces the new clrTextarea component, which handles the form validations for the textarea. It also extracts the control class logic into a service since it was being duplicated.
#1878

@youdz I decided to consolidate the tests for input and textarea because they are practically identical. So the changeset is larger but reduces overall code (and will be better for future components).


BUG: Overflows/NaNs cause segfault in integrate.quad on certain domains

Describe your issue.
I was working on something similar to this issue https://github.com/scipy/scipy/issues/12662 and am encountering similar segfaults, even without using weighted integration. Below is the simplest example that I can reproduce this on where I've essentially removed all mathematical calculations entirely.
Surprisingly, this is very sensitive to the domain of integration. It segfaults on [-1.5, 1.5], but does not on [-1.49, 1.5] or [-1.5, 1.49]. It does not appear particularly sensitive to the locations of the NaNs either.
No error message or warnings are printed before the segfault. The segfault is triggered by a general protection fault in scipy/integrate/_quadpack.cpython-39-x86_64-linux-gnu.so.
This consistently occurs after the 4557th query to f(theta) after this sequence of Gauss-Kronrod samples:

The final query (which segfaults) has theta=1.7144581914055983e-17, but I imagine the issue is in the scipy/QUADPACK bookkeeping of earlier samples.
Reproducing Code Example
import numpy as np
from scipy.integrate import quad

def f(theta):
    if theta < -1:
        return np.nan
    return 0.0

quad(f, -1.5, 1.5, limit=1000)

Error message
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

SciPy/NumPy/Python version information
1.7.1 1.21.2 sys.version_info(major=3, minor=9, micro=7, releaselevel='final', serial=0)

The segfault occurs on my machine with limit=109 and higher, so this may be faulty memory (re)allocation / blowing out the stack / etc.

This also appears to be fixed by https://github.com/scipy/scipy/pull/21201.

Just out of curiosity, here's the new sequence of samples inside quad.


chore: adjust NonHierarchicalViewBasedAlgorithm demo and doc

Clarify that width and height should be passed as dp to NonHierarchicalViewBasedAlgorithm
The calculations used to determine the visible bounds rely on the width and height being passed in as dp. The demo of the algorithm uses pixels which results in markers being rendered outside of the visible screen.
Thank you for opening a Pull Request!

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)
[x] Will this cause breaking changes to existing Java or Kotlin integrations? If so, ensure the commit has a BREAKING CHANGE footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/

Fixes #<issue_number_goes_here> 🦕

@googlebot I signed it!

@AndreasBoehm Good catch! Thanks for fixing this.
Two requests:

Could you also fix the variables passed to updateViewSize() in ClusteringViewModelDemoActivity to be dp instead of pixels?
Could you run the Gradle task generateV3 to fix this issue in the v3 demo app product flavor as well? This task will autogenerate the relevant v3 code from the changes you already made to the gms variant here. Note that currently the main branch v3 variant is already behind the gms variant with some whitespace and formatting changes - I've opened #896 to fix this.

Thanks for your review @barbeau.
Sorry it totally missed the usages of updateViewSize(). I pushed a new commit that fixes the variables and with updated v3 code (excluded whitespace only changes)


[Feature][Data Proxy]Golang SDK documents

Description
Add documents for Data Proxy Golang SDK, both in English and Chinese.
Use case
Add documents for Data Proxy Golang SDK, both in English and Chinese, to guide the users how to use this SDK to produce message to InLong.
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

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

Should to create issue

This issue should be create at inlong-website


Options Menu Doesn’t Work in iOS Safari

Describe the bug:
When attempting to use the Options menu on iOS Safari, none of the options are tappable.  The menu displays but you can’t select an option.  This happens regardless of whether it’s a clock menu or a regular Options menu. Has been happening on iOS 12 and 13 (Beta) and has been happening at least since HA 0.93.2 but possibly throughout 0.93.  Currently on 0.94.2.
Config YAML:
<!-- Paste your lovelace code for the card after this line -->
- type: custom:compact-custom-header
        main_config: true
        menu: overflow
        background: true
        options: clock
        voice: hide
        clock_format: 12
        clock_am_pm: true
        clock_date: true

HA and/or Browser Error:

None in HA.
HA, Card, and Browser Versions:

Card Version: 1.0.4b9
HA Version: 0.94.2
Browser: iOS Safari (iOS 12 and 13)
YAML Mode

This has happened in the past but was working for a while until recently (last couple of weeks).  Actually, this may not be a CCH problem as disabling with ?disable_cch doesn’t fix the Options menu.  Perhaps there’s a conflict with another card.  I’ll try hooking up to my Mac and pulling logs.  Works fine on a desktop.

As you have discovered, this is not related to CCH. I can confirm this happens on Android as well and items in options menu are very difficult to select. This happens with or without CCH installed.

Just to be sure that I didn't prematurely close this one:
To rule out CCH completely, comment out CCH's resource in your yaml and refresh the page. If this is still an issue we can be sure it's not CCH.

I know this issue is 'closed', but I'll add my comment for other folks that may be searching for this issue. I did test as you suggested, and you're correct that it is not caused by CCH (persists even after removing the CCH reference). I've found that a polymer issue has been opened:
https://github.com/home-assistant/home-assistant-polymer/issues/3453


Whitespace Removal via > and < possible?

Hey there,
first of all: Thank you for your effort in bringing HAML to the Python world. I’m coming from a Ruby background and your implementation makes me feel at home. :)
I’ve a quick question – in the original HAML there is the possibility to control whitespace output.
See the HAML-Documentation about Whitespace
I’m wondering if something similar exists in your implementation … the feature is especially important when it comes to inline-blocks because they are whitespace-aware and I need an output without any whitespace between them.
Any help on the matter would be greatly appreciated. :)
Best regards,
Harry

There's no feature in HamlPy to do this that I'm aware of. It's the first time I've come across it (and seems like a where-have-you-been-all-my-life feature!)
I'm quite busy myself over the next few weeks but if I find time I'll have a go at implementing it. You're welcome to do so yourself of course, just let me know so that we don't end up working on the same thing.

Hey again and thanks for the quick reply. As much as I want to help you, the coming weeks are pretty busy for me as well and I won’t have the time to look into it. I found a solution for the meantime though:
Just in case anyone else is struggling with this in Django … I found out you can achieve similar output by using a spaceless block: https://docs.djangoproject.com/en/1.3/ref/templates/builtins/#spaceless
Still, the < and > operators in HAML allow more fine-grained control – but the spaceless block will do just fine until you can find the time to implement it. No rush. Thanks again for your effort!


Add functionality to scrape url with Jina AI

What this Pull Request (PR) does

added --scrape_url or -su CLI command to curl the content of a webpage in markdown form
uses Jina AI
no API key is needed

How to use it
The easiest way to use it is with this format: fabric -su {URL} | fabric -sp extract_wisdown. This scrapes the {URL}, transforms it into markdown, and then pipes it into fabric. An example is provided in the screenshot below.
Screenshots

Great addition!

Since Fabric is transitioning to Go, will all PRs to the original repo be held in limbo?

I really want this added, this would be great tooling to have

Looks like there is a ton of noise in this PR, possibly due to some formatter that changed it. While I approve of the formatting changes, it would be better to separate that into another PR so that this Jina addition is easier to approve.

Looks like there is a ton of noise in this PR, possibly due to some formatter that changed it. While I approve of the formatting changes, it would be better to separate that into another PR so that this Jina addition is easier to approve.

I just removed all the formatting. I'm sorry about that. Let me know what else should be changed for this to be added!

This is great! We're working on some more robust scraping options though so I think we wait and address this after it moves to Go.


Real-Time segmentation

Hi!
First of all thank you for your work!
I would be interested in real-time skin segmentation!

Daniel

Hey Daniel!
Its great to see some interest in the project, I've added BiSeNetV2 for real-time segmentation and added a pre-trained skin segmentation model.
It'd be interesting to see what you use it for!
#2

Thank you! I would like to use it for pulse detection from video.
May I ask that on how many samples was the model trained? I will check it now, thanks a lot again!

Ah nice! Its around 150 images but with heavy augmentation. If you find any failure cases then feel free to mark them up and send them over, then I can train a new model that fixes those.

Hmmm; I'd suggest double checking the performance of the accurate one first. Then play around with the --threshold parameter to see if the arms are picked up at a lower threshold.
If those don't work then feel free to send over the annotated images and I'll add them to the training set.

with a threshold of 0.3 and resizing the image to 40% of the size you'll get a decent segmentation mask with the accurate one. The real-time one performs poorly and needs more data.


Cu 86b0zgy4j playback speed

Task linked: CU-86b0zgy4j Playback Speed

@changoug can you verify if this is working with command

will do


Victor VosMottor: Watch libomaxmaleperformancebuy(?#sites.google.com)

Victor VosMottor requests the watch of the watch_keyword libomaxmaleperformancebuy(?#sites.google.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

libomaxmaleperformancebuy(?#sites.google.com) has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


additional changes for PR 199

Fixed the id argument

Codecov Report

Merging #204 into master will increase coverage by 0.35%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
+ Coverage   69.74%   70.10%   +0.35%
==========================================
  Files          18       18
  Lines        5338     5338
==========================================
+ Hits         3723     3742      +19
+ Misses       1615     1596      -19

Impacted Files
Coverage Δ

stix2elevator/confidence.py
64.00% <100.00%> (ø)

stix2elevator/convert_stix.py
76.01% <100.00%> (+1.38%)
:arrow_up:

stix2elevator/missing_policy.py
57.93% <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 286693c...df77d2b. Read the comment docs.


Incorrect location for arm-template-parameters-definition.json

The article incorrectly states to "create a file named arm-template-parameters-definition.json in the root folder of the repository". It should read "... in the folder specified as the root folder for the data factory git integration".
If, when you setup git integration for data factory, you specify a non-empty rootfolder, then that's were the customer parameters definition file should go (and NOT in the repository root)

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

ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
Content: Continuous integration and delivery in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/continuous-integration-deployment.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@JayReally Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will provide an update as appropriate.


Support multiple compression formats

For the NYC Subway, the xz format is over 15 times more space efficient that gz. Hoard should make the compression format configurable so that different users can optimize it for their data type. The level should also be configurable.
Involves:

Identify all places where gz is assumed and generalize it. This will mostly involve adding a compression attribute to the AStore type, and then changing the string serialization and de-serialization accordingly.
Add a new audit action that ensures the archive files are in the right format. This action should probably not fix by default, unless the number of incorrect files is low.

Done


The rgb_frames of the wear dataset

Hello!Could you please provide the frame rate and any specific parameters or tools you used for extracting frames (e.g., resolution, frame sampling rate, etc.) about the wear dataset? This information would be extremely helpful in ensuring consistency with your original implementation.Thank you very much!

We convert the RGB video into frames with the same FPS as the video capture and then use the sampling rate indicated in the config file for each dataset.
As for the resolution, we save the frames so that their height is 256 while keeping the aspect ratio.

Thank you very much!

It depends on the dataset (I think it is 60 FPS for the WEAR dataset, but I am not sure so please check the original paper if you are curious).
Anyway, you need to extract all frames contained in videos, as you cannot extract them with a higher FPS than the original video capture setting.
The following is the function for extracting image frames just in case.
def extract_image_frame(video_path, output_dir="/path/to/output_dir"):
    print(f"processing {str(video_path)}...")
    video_name = Path(video_path).name.replace(".mp4", "")
    output_frame_dir = Path(output_dir) / video_name
    os.makedirs(output_frame_dir, exist_ok=True)
    video = cv2.VideoCapture(str(video_path))

    frame_rate = video.get(cv2.CAP_PROP_FPS)
    frame_width = video.get(cv2.CAP_PROP_FRAME_WIDTH)
    frame_height = video.get(cv2.CAP_PROP_FRAME_HEIGHT)

    target_height = 256
    target_width = int(frame_width*(target_height/frame_height))

    frame_num = 0

    while video.isOpened():
        ret, frame = video.read()

        frame_num += 1
        if ret:
            # rgb_center_frame = cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)
            frame = cv2.resize(frame, (target_width, target_height))
            cv2.imwrite(
                f"{output_frame_dir}/{str(frame_num).zfill(6)}.jpg", frame
            )
        else:
            break

Thank you very much for your reply!Thank you very much for your work and help ! I would greatly appreciate it!


Failed precondition: Attempting to use uninitialized value spectral_net_learning_rate

Hello, I want to reproduce the results in this paper but I failed. When I ran this code on Ubuntu 16.04 + Tensorflow 1.15 + keras 2.3.1,  the following error happened:

(0) Failed precondition: Attempting to use uninitialized value spectral_net_learning_rate
[[{{node spectral_net_learning_rate/read}}]]
[[Reshape_20/_1781]]
(1) Failed precondition: Attempting to use uninitialized value spectral_net_learning_rate
[[{{node spectral_net_learning_rate/read}}]]
0 successful operations.
0 derived errors ignored.

Then, I change the code in the class MvSCN (network.py):
K.get_session().run(tf.initialize_all_variables())
The code ran successfully, but I only get the poor results on Caltech101-20:
ACC:0.2994, NMI:0.4467
So how do I get the correct results? Thank you.

Solved by changing the environment to:
Ubuntu 16.04 + cuda 9.0
tensorflow1.9.0
keras 2.1.6

Solved by changing the environment to:
Ubuntu 16.04 + cuda 9.0
tensorflow1.9.0
keras 2.1.6


do linkml-lint as past of the build process

How to run in a mode that ignores Permissible value  standard_naming?
linkml-lint src/schema/nmdc.yaml  | grep -v 'Permissible value of Enum.*(standard_naming)'

I think we can ignore most of the canonical_prefixes, but we should review that
I think there are still some enums with lower snake case names, but this didn't catch any
@mslarae13 I think there's already an issue for many of these Slot description recommended warning

warning  Class 'FailureCategorization' does not have recommended slot 'description'  (recommended)
warning  Class 'FunctionalAnnotationAggMember' does not have recommended slot 'description'  (recommended)
warning  Class 'Protocol' does not have recommended slot 'description'  (recommended)
warning  Class 'LibraryPreparation' does not have recommended slot 'description'  (recommended)
warning  Class 'CollectingBiosamplesFromSite' does not have recommended slot 'description'  (recommended)
warning  Slot 'has_failure_categorization' does not have recommended slot 'description'  (recommended)
warning  Slot 'model' does not have recommended slot 'description'  (recommended)
warning  Slot 'vendor' does not have recommended slot 'description'  (recommended)
warning  Slot 'count' does not have recommended slot 'description'  (recommended)
warning  Slot 'functional_annotation_agg' does not have recommended slot 'description'  (recommended)
warning  Slot 'habitat' does not have recommended slot 'description'  (recommended)
warning  Slot 'location' does not have recommended slot 'description'  (recommended)
warning  Slot 'community' does not have recommended slot 'description'  (recommended)
warning  Slot 'ncbi_taxonomy_name' does not have recommended slot 'description'  (recommended)
warning  Slot 'ncbi_project_name' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_site' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_year' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_month' does not have recommended slot 'description'  (recommended)
warning  Slot 'library_preparation_kit' does not have recommended slot 'description'  (recommended)
warning  Slot 'extraction_method' does not have recommended slot 'description'  (recommended)
warning  Slot 'pcr_cycles' does not have recommended slot 'description'  (recommended)
warning  Slot 'library_type' does not have recommended slot 'description'  (recommended)
warning  Slot 'biosample_categories' does not have recommended slot 'description'  (recommended)
warning  Slot 'relevant_protocols' does not have recommended slot 'description'  (recommended)
warning  Slot 'applied_roles' does not have recommended slot 'description'  (recommended)
warning  Slot 'applies_to_person' does not have recommended slot 'description'  (recommended)
warning  Slot 'field_research_site_set' does not have recommended slot 'description'  (recommended)
warning  Slot 'collecting_biosamples_from_site_set' does not have recommended slot 'description'  (recommended)
warning  Slot 'pooling_set' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_day' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_hour' does not have recommended slot 'description'  (recommended)
warning  Slot 'sample_collection_minute' does not have recommended slot 'description'  (recommended)
warning  Slot 'soluble_iron_micromol' does not have recommended slot 'description'  (recommended)
warning  Slot 'host_name' does not have recommended slot 'description'  (recommended)
warning  Slot 'subsurface_depth' does not have recommended slot 'description'  (recommended)
warning  Slot 'proport_woa_temperature' does not have recommended slot 'description'  (recommended)
warning  Slot 'biogas_temperature' does not have recommended slot 'description'  (recommended)
warning  Slot 'soil_annual_season_temp' does not have recommended slot 'description'  (recommended)
warning  Slot 'biogas_retention_time' does not have recommended slot 'description'  (recommended)
warning  Slot 'completion_date' does not have recommended slot 'description'  (recommended)
warning  Slot 'value' does not have recommended slot 'description'  (recommended)
warning  Enum 'InstrumentModelEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'InstrumentVendorEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'StatusEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'ExtractionTargetEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'LibraryTypeEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'JgiContTypeEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'FileTypeEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'CreditEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'StudyCategoryEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'DoiProviderEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'DoiCategoryEnum' does not have recommended slot 'description'  (recommended)
warning  Enum 'CompoundEnum' does not have recommended slot 'description'  (recommended)
warning  Schema maps prefix 'CATH' to namespace 'https://bioregistry.io/cath:' instead of namespace 'http://identifiers.org/cath/'  (canonical_prefixes)
warning  Schema maps prefix 'CHEMBL.COMPOUND' to namespace 'https://bioregistry.io/chembl.compound:' instead of namespace 'http://identifiers.org/chembl.compound/'  (canonical_prefixes)
warning  Schema maps prefix 'DRUGBANK' to namespace 'https://bioregistry.io/drugbank:' instead of namespace 'http://identifiers.org/drugbank/'  (canonical_prefixes)
warning  Schema maps prefix 'EFO' to namespace 'http://www.ebi.ac.uk/efo/' instead of namespace 'http://identifiers.org/efo/'  (canonical_prefixes)
warning  Schema maps prefix 'EGGNOG' to namespace 'https://bioregistry.io/eggnog:' instead of namespace 'http://identifiers.org/eggnog/'  (canonical_prefixes)
warning  Schema maps prefix 'HMDB' to namespace 'https://bioregistry.io/hmdb:' instead of namespace 'http://identifiers.org/hmdb/'  (canonical_prefixes)
warning  Schema maps prefix 'MASSIVE' to namespace 'https://bioregistry.io/reference/massive:' instead of namespace 'http://identifiers.org/massive/'  (canonical_prefixes)
warning  Schema maps prefix 'MESH' to namespace 'https://bioregistry.io/mesh:' instead of namespace 'http://identifiers.org/mesh/'  (canonical_prefixes)
warning  Schema maps prefix 'ORCID' to namespace 'https://orcid.org/' instead of namespace 'http://identifiers.org/orcid/'  (canonical_prefixes)
warning  Schema maps prefix 'PANTHER.FAMILY' to namespace 'https://bioregistry.io/panther.family:' instead of namespace 'http://identifiers.org/panther.family/'  (canonical_prefixes)
warning  Schema maps prefix 'PFAM' to namespace 'https://bioregistry.io/pfam:' instead of namespace 'http://identifiers.org/pfam/'  (canonical_prefixes)
warning  Schema maps prefix 'PUBCHEM.COMPOUND' to namespace 'https://bioregistry.io/pubchem.compound:' instead of namespace 'http://identifiers.org/pubchem.compound/'  (canonical_prefixes)
warning  Schema maps prefix 'SUPFAM' to namespace 'https://bioregistry.io/supfam:' instead of namespace 'http://identifiers.org/supfam/'  (canonical_prefixes)
warning  Schema maps prefix 'TIGRFAM' to namespace 'https://bioregistry.io/tigrfam:' instead of namespace 'http://identifiers.org/tigrfam/'  (canonical_prefixes)
warning  Schema maps prefix 'edam.data' to namespace 'http://edamontology.org/data_' instead of using prefix 'EDAM.DATA'  (canonical_prefixes)
warning  Schema maps prefix 'rdf' to namespace 'http://www.w3.org/1999/02/22-rdf-syntax-ns#' instead of using prefix 'RDF'  (canonical_prefixes)
warning  Schema maps prefix 'rdfs' to namespace 'http://www.w3.org/2000/01/rdf-schema#' instead of using prefix 'RDFS'  (canonical_prefixes)
warning  Schema maps prefix 'wikidata' to namespace 'http://www.wikidata.org/entity/' instead of using prefix 'wd'  (canonical_prefixes)

Step away from the grep command.
Define your own configuration that leaves the standard_naming rule off if you don't want it.

Thanks. I want to check standard naming for everything except PV names. And I think I want even stricter checking of enum names. I will experiment some more and update today or Monday.


Updates the travis ci encryption and adds documentation for PyPi deployement

This is a small PR that does the  following:

updates the version number in setup.py to v0.3.1
updates the encrypted pypi deploy key in travis.ci script (the problem was that special characters need to be escaped when encrypting the password)
adds a section in the CONTRIBUTING.md file to explain the procedure to follow when cutting a new version and deploying to PyPi

Pull Request Test Coverage Report for Build 1498

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.495%

Totals

Change from base Build 1490:
0.0%

Covered Lines:
515

Relevant Lines:
545

💛  - Coveralls


Fix cache removal on network errors

At the moment, when a network error occurs, fetch will give an rejected promise, instead of of a Promise holding a Response object.
This creates an issue with the current implementation of the cache, which doesn't handle rejections, and in turn never removes it from cache. In practice, this causes a problem that once there is a network error, that cache entry is effectively "poisoned", and will always give the network error.
This addresses this issue by making sure it always gets removed from the cache, even in the event of an error.
Note that this can also be solved by a one-lines like return promise.finally(() => promiseCache.delete(key));, I have decided for this way as it is easier to read, and software is read more times than it is written (and it also mirrors the style of the rest of the code)
(I originally found a link to project from reddit, and decided to use it in some of my private projects, instead of a self written solution)

Greetings @ferrybig, thank you for your contribution. You are right about this issue, I will check your code and merge your pull request as soon as possible 😁

By the way, can you add a test case for this patch? I can also do it afterwards if you don't know how, but it would be nice if it is in the same pull request 😊

@ferrybig thank you very much for your contribution!  👍🏼


1.0 Release?

After a few days and maybe dropping in docopt-ng for some popular projects that use docopt, I'm hoping to do a 1.0 release - slightly breaking semver, but with 100% coverage I think the project deserves to be pulled out of "beta".

I'm gonna test it out on my projects this weekend. I use docopt heavily, and even modify it's behavior a little in my Colr library (optionally, to colorize docopt usage strings). I do this by importing docopt from Colr, where a couple functions/error-classes have been overridden. I'll have to modify Colr a little, to use docopt-ng when available. Not that any of this is your problem, just letting you know that I plan on putting docopt-ng  to the test. I doubt there will be any bugs on your end, but if there are then I'll file an issue.

@cjwelborn that sounds wonderful, thanks for taking the initiative! Looking forward to hearing how the tests go.
Looking at Colr: assuming you don't intend to support the more_magic functionality of docopt-ng, no changes should be required. If you want more magic, ie

long-argument spellcheck (--hel -> --help, --verBOse -> --verbose)
the arguments variable to be populated in the globals namespace if docopt() isn't assigned
__doc__ from the calling namespace to be used if docstring isn't passed to docopt(), and
more_magic to be set to True if docopt() is aliased to a function name containing magic (from docopt import magic_docopt)

then a few changes will be required, but not many.
Cheers!

@itdaniher, cool. Thanks for the extra info. I'll get back to you.

I ended up having to upgrade my OS this weekend and ran into trouble. I haven't been able to do any real testing so far. Only thing I've noticed is that the variable type annotations kill support for anything less than Python 3.6. A 1.0 release may be mandatory since breaking changes were introduced. The only other option I can think of involves losing all of the type-checked goodness. I'm still going to test this out on my projects ASAP.

Okay, so I've been testing this out with my stuff and it looks like it introduces major breaking changes. It's not a "drop-in" replacement for the old docopt. Parameter names have changed, so any program calling docopt like: docopt(usagestr, help=False) is going to fail. I would think a major version change is needed at the very least. Also, since both projects install as docopt (import docopt), you can't have both installed at the same time. I don't know how you would feel about renaming the module to docopt_ng or something simlar, but I'd at least do a 1.0 to mark these breaking changes.

Renaming to docopt_ng is probably reasonable. I'll also go through and make sure the parameter names for the keyword arguments match docopt, feel free to open a bug. Anything else blocking drop-in use?

Any updates on this? I'm using docopt a lot, but it has tons of issues, and has been seemingly abandoned, so this fork seems like the solution moving forwards. Except that a seemingly ready release hasn't gone through which makes me doubt about the future of docopt-ng :/

I'd still like to see a docopt_ng package also. I have so many scripts/tools using docopt right now and a package of my own that hooks into docopt, that if I installed this package as-is I would spend hours fixing everything. With a new name, I could install it side-by-side with docopt and slowly start adapting to the new way of doing things. Eventually I could drop the old docopt altogether.
I don't like asking people to rename their projects, but it would help me out a lot if this was imported as anything except docopt.

I'd love to see it as {docopt_ng, docoptng, docopt2, etc} as well, exactly for the reasons above. I have a ton of existing docopt code I'd love to port over if they were API compatible but if not, having side-by-side installs would be almost as good.
Any thoughts on what it would take to get to a new package name?


Upgrade to dbt 0.20.0

Tests pass on Darwin with Python 3.9.6 on ARM. Created a further docker container and ran against a real-world dataset in AWS with tables, views and incremental materialisation. Data tests passed, no errors, all seems to work fine.

@Prokopp Thanks a lot for this! I will be running some upgrades tests in a day or two on my side then will aim to get it all merged in 👍


Escape periods in Kafka version regex

This change makes error logging more informative for invalid version strings.

Nice catch, thanks.


[fix][metedata-postgres]parsing type error when use bigint types

Purpose of the pull request

parsing type error when use bigint types
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

你需要签出0.7分支。并在0.7分支上修改后pr到主仓库的0.7分支，dev在重构，bugfix主要在0.7分支

你需要签出0.7分支。并在0.7分支上修改后pr到主仓库的0.7分支，dev在重构，bugfix主要在0.7分支

好的


Feature - Add "Private" & "Public" Listings Functionality

Organization need to have the option to list an app as private. Only users within that apps organization shall be able to search and view a private app.
AppsMall Admin need to be able to see all private apps.

Dependent on new backend

@tonyalletag looks like the original requirement/mockups was for both the Org Steward and Center Steward to individually approve/deny a private request. Is this still accurate, or should the public/private status be chosen by the App Creator, much like the "enabled" status?
Keeping @blaino in the loop.
(https://github.com/ozone-development/ozp-documentation/wiki/Private-Listings)

And, the original plan includes a "short justification" for why the listing should be private. Are we still doing that?

The App Create should have the option to select a "private" status for the application when it is submitted

@blaino is this ticket replaced by #447?

@bhalt, I think so, provided everyone agrees #447 captures our discussion earlier.

please refer to #447


Weibayes issue with failures

Line 728:
I believe the code is correct when no failures exist:
etaseries[0, :] = ((self.data ** self.beta) / self.r)
but when failures exist, it should be:
etaseries[0, :] = ((self.data ** self.beta) / NumberOfFailures)
also, if 63% confidence is acceptable, and no failures exist, self.r = 1 would be functionally correct.
ref:
http://www.dtic.mil/dtic/tr/fulltext/u2/a143100.pdf
https://www.aesseal.com/sites/aesseal.com/files/whitepaper/WP-LABTECTALIFE-01.pdf

I appreciate the feedback.  When I get to this project again, I will definitely make the change.  Thank you!

hi!
this is Dj,
in weibull_text_Example.py(The example in the book Weibull Analysis by Bryan Dodson)
every thing is ok, for small data points, but in case of large Data, for example 1000 etc..
for all the suspended points, did we have to type  that many time type 0 or False, is their any other way
_fail_times = [
42.1, 105.9, 151.3, 195.6,
77.8, 117.0, 157.3, 207.0,
83.3, 126.9, 163.8, 215.3,
88.7, 138.7, 177.2, 217.4,
101.8, 148.9, 194.3, 258.8
]
suspensions = [1, 0, 1, 1,
0, 0, 0, 0,
1, 0, 0, 1,
1, 0, 1, 0,
0, 0, 1, 1]_

I don't know that particular example, but if you create a list of indexes
for the true values, then you could use a for loop to create a list with
1/0 in the necessary places (if I understand your intent)
On Fri, Jun 14, 2019, 11:57 PM djhak9<EMAIL_ADDRESS>wrote:

hi!
this is Dj,
in weibull_text_Example.py(The example in the book Weibull Analysis by
Bryan Dodson)
every thing is ok, for small data points, but in case of large Data, for
example 1000 etc..
for all the suspended points, did we have to type that many time type 0 or
False, is their any other way
_fail_times = [
42.1, 105.9, 151.3, 195.6,
77.8, 117.0, 157.3, 207.0,
83.3, 126.9, 163.8, 215.3,
88.7, 138.7, 177.2, 217.4,
101.8, 148.9, 194.3, 258.8
]
suspensions = [1, 0, 1, 1,
0, 0, 0, 0,
1, 0, 0, 1,
1, 0, 1, 0,
0, 0, 1, 1]_
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slightlynybbled/weibull/issues/13?email_source=notifications&email_token=ABVURKPH77X2GBW4SDSWR6LP2RZCHA5CNFSM4FPYVYXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXYQLJA#issuecomment-502334884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVURKIJZP2MVLLN43XF5R3P2RZCHANCNFSM4FPYVYXA
.

Please see the reliability package for a more feature-rich experience.  I am shifting my work over to that package and will consider the weibull package obsolete.


Left side pane does not collapse after selection of a page

Description:
Left side pane does not collapse after selection of a page
Suggested Labels:
EI Analytics dashboard

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This issue has been solved in this PR.


Ömer: Debugging, 4

🥚 Stepping Through: You can:
[x] Pause a script in a step debugger (breakpoints and debugger statement)
[x] Arrange the debugger, collapse extra panels
[x] Step through a script written with Just Enough JS.
[x] At each point in execution you can make a prediction of the next line before executing
[ ] Check your prediction using the scopes panel.
🥚 Assertion Testing:
[x] You are familiar with assertions
[x] Can use console.assert to guide your study of a program.
[x] 🥚 Linting: You can find and fix linting errors in JavaScript programs.
🥚 Naming Variables: You can:
[x] Analyze a program's variables using a structured comment
Rename the variables and give each variable two different names:
[x]  Generic: A name that describes the variable's role in a general way. This includes deciding whether to use let or const.
[x]  Specific: A name that fits the variable's role and contextualizes it in the program's domain.
[ ] 🥚 Program Life Cycle: You can explain the two phases of a program's life cycle.
[x] 🥚 Fixing Errors: You can use the structured comment to describe an error in your program, and can make several educated guesses at how to fix the error.
🥚 Documenting Functions: You can:
[x] Demonstrate your understanding of arguments, parameters
[ ] Return values by writing a JSDoc comment.
🐣 Explicit Coercion:
[x] You are aware of the rules for casting explicitly between types
[x] Can complete assertions to describe what value will result, they can have access to the internet and a console.
[x] 🐣 Implicit Coercion: You are aware that operators will implicitly cast operands to the same type before operating. They can look or experimentally discover the rules for an operator.
🐣 Statements vs. Expressions: You can:
[x] Explain the difference between a statement and an expression
[x] Identify them in a program. This will be very helpful for understanding how the debugger steps, and for ...
[x] 🐣 Operator Precedence: You can refactor an expression with several operators into several statements assigning each step of the expression to a new variable according to the languages rules of operator precedence.111
[x] 🐣 Fixing Bugs: You can use the structured comment to describe and fix a bug in small programs.
🐣 Reference vs. Value: You can:
[x] Explain how to swap references or values between variables
[x] Explain deep vs. strict equality
[ ] Compare two objects or arrays.
🐣 Procedural Programming: You can:
[ ] Tell whether or not a JS program is Procedural
[ ] Explain how you made your decision.
[ ] 🐣 Side-Effects: Given a function that takes an array as an argument you can determine if the function has any side-effects, and can suggest a way to avoid the side-effect.
🐣 Debugging Functions: You can:
[x] Read input/output assertion tests to understand a function's actual vs. expected behaviour
[x] Correct the function's behaviour.
[ ] 🐥 Sub-Goal Authoring: Given most of a small program with missing goal, you can write code to implement the missing behaviour.
[ ] 🐥 Hoisting: You can find hoisted functions and variables in the browser's debugger and explain how hoisting is related to program life-cycle.
[ ] 🐔 Refactoring Functions: You can refactor a designated chunk of a program into an empty function body and pass the given assertion tests.
[ ] 🐔 Reverse-Engineering: You can write a small program from scratch that matches the behavior of an example program.

Week 9
Check-In
I Need Help With:
 _

What went well?

I learned 2 good websites last week in the class for code exercises thanks to @denrique-alvarez : Projecteuler and  Codewars

What went less well?
 _

Lessons Learned

I learned the use of 'debugger;' code in JS
I learned console.assert() method in JS
I learned some tips about how to decide using while or for loop

Sunday Prep Work

Reading the suggested study materials
Doing exercises in JS tutor

@omerjava , if you're already going into code challenges you might want to check out solution-write-ups, it's an exercise from the Behavior Strategy Implementation module

@omerjava , if you're already going into code challenges you might want to check out solution-write-ups, it's an exercise from the Behavior Strategy Implementation module

Ok. I will look at. Thank you!

 Trying to learn some more so we can discuss some problems together soon :)

Week 10-11
Check-In
I Need Help With:
 _

What went well?

I am solving code problems in code challenge websites, it contributes a lot to my theoretical knowledge. I feel I improved a lot myself in for, while loops and in use of arrays. I also practiced well some built-in array/string/number methods and some array iterators. I am very familiar now with methods such as split(), push(), String(), Number(), reverse(), includes(), join().

What went less well?
 _

Lessons Learned

I learned the use of String(), Number() and Boolean() methods
I learned Objest.is() method
I learned template literals
I learned ternary operator

Sunday Prep Work

Reading the suggested study materials
Trying to solve code problems

Great to hear that you are learning and exploring. 💯

Week 12
Check-In
I Need Help With:
 _

What went well?

I am now familiar with for..of loop and their difference from "for" loop
I got used to creating an empty object variable and assigning "properties/keys : values" to them by using "for" loop. Very handy to find how many times numbers or letters repeat in a string. I can apply it in problems now.

What went less well?

I can't work as much as I want now due to time constraint. But my fulltime job will end soon and I will able to focus on totally coding.

Lessons Learned

Now, I am comfortable with using for..of loop.
Better understand splice() and slice() methods, they are also very useful
Learned to make an infinite loop with for..of loop. It is fun :)

Sunday Prep Work

Reading the suggested study materials
Trying to solve code problems

I can't work as much as I want now due to time constraint. But my fulltime job will end soon and I will able to focus on totally coding.

@omerjava let us know if you need any extra one-to-one time with the coaches (from what we can see, you are doing very well even with the time constraint)


Add hyperlink sid information to help topic

I keep forgetting to update this. Need to update the screenshot to show the SID hyperlink and the text to explain it.

Also add notes about the new airport and SID-specific notes, and about airport-wide initial altitudes.


run uncommitted balance checks only when there is not already an outbound channel open

Description
When a user opens channels, and the outbound succeeds but the inbound fails, we made it so they can commit again and we will just bypass creating the outbound channel. However, we still have checks in place that if they have an uncommitted balance lower than the channel they are trying to create, we do not allow them to commit funds. We need to run this check only if there is not already an outbound channel open.
Related PRs
List related PRs if applicable
Todos

[x] Tests
[x] Documentation
[x] Link to Trello

 CLI errors when re-committing the same amount


i586 error in generated xkb.py: AttributeError: /usr/lib/libX11.so.6: undefined symbol: _XData32

On openSUSE Tumbleweed i586 libX11.so.6 doesnt have symbol _XData32, which results in:
Traceback (most recent call last):
  File "setup.py", line 6, in <module>
    from xkbgroup.version import VERSION
  File "/home/abuild/rpmbuild/BUILD/xkbgroup-0.2.0/xkbgroup/__init__.py", line 14, in <module>
    from .core import XKeyboard, X11Error
  File "/home/abuild/rpmbuild/BUILD/xkbgroup-0.2.0/xkbgroup/core.py", line 31, in <module>
    from xkbgroup.xkb import *
  File "/home/abuild/rpmbuild/BUILD/xkbgroup-0.2.0/xkbgroup/xkb.py", line 4636, in <module>
    _XData32 = _libraries['libX11.so.6']._XData32
  File "/usr/lib/python2.7/ctypes/__init__.py", line 379, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 384, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/lib/libX11.so.6: undefined symbol: _XData32

Same occurs for _XRead32


Create GeoExploreAI.md

📝 Description
GeoExplore-AI is an advanced artificial intelligence agent dedicated to the comprehensive study and analysis of Earth's geology, weather patterns, and natural phenomena. With access to vast datasets and powerful analytical capabilities, GeoExploreAI offers insights into the intricate workings of our planet.
pr for this issue:  #2443
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

i will create a new one


Klayout tech

More refactoring of the KLayout technology module. Aside from the layer numbers appended to the layer names and the layers without names, the module can read our current layer properties (layers.lyp) into a KLayoutLayerProperties object and write to a new .lyp file.
Still need to fix the test and figure out what to do with the layer names that have layer numbers on them. Also might be worth naming the unnamed layers.
@joamatab how can I regenerate the yaml file that's used in the test?

More refactoring of the KLayout technology module. Aside from the layer numbers appended to the layer names and the layers without names, the module can read our current layer properties (layers.lyp) into a KLayoutLayerProperties object and write to a new .lyp file.
Still need to fix the test and figure out what to do with the layer names that have layer numbers on them. Also might be worth naming the unnamed layers.

@joamatab how can I regenerate the yaml file associated with the test?

Thank you Thomas!
just did pytest gdsfactory/tests/test_klayout_tech.py --force-regen and pushed a fix for the test


Can't build to parent outDir folder with 1.5.4

Versions
Angular CLI: 1.5.4
Node: 6.11.2
OS: win32 x64 (Win10)
Angular: 4.4.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-webworker
... platform-webworker-dynamic, router, tsc-wrapped

@angular/cdk: 2.0.0-beta.12
@angular/cli: 1.5.4
@angular/material: 2.0.0-beta.12
@angular-devkit/build-optimizer: 0.0.33
@angular-devkit/core: 0.0.21
@angular-devkit/schematics: 0.0.37
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.4
@schematics/angular: 0.1.7
typescript: 2.3.4
webpack: 3.8.1

Repro steps

Set apps[0].outDir as "../dist" on .angular-cli.json
run ng b

Observed behavior
Only a error message: An asset cannot be written to a location outside the project.
Desired behavior
Build the project without problem.
Mention any other details that might be useful (optional)
We have tried to add allowOutsideDir to ours assets configuration on cli config, but doesn't work. Is this the expected behaviour? I don't found related information about it in de64b86 or #8122 :(

Same problem here.
I can't believe a major functionality of the CLI, "ng b", doesn't work after an update...
Downgrade to 1.5.3...

@hansl can you have a look please?

@hansl @filipesilva @rbluethl: This issue is occuring when the outdir in .angular-cli.json is outside the angular folder. (eg. "outDir": "../../bin/Debug/www")

@hansl @filipesilva : Same issue here. Please fix the issue.
".angular-cli.json" Config
... "apps": [     {       "root": "src",       "outDir": "../web/src/main/resources/static",       "assets": [ ...
On Build
>ng build An asset cannot be written to a location outside the project.

Same problem, I 'm using the outDir param to build outside my angular root folder.

Same here

Same here

      // Prevent asset configurations from writing outside of the output path, except if the user       // specify a configuration flag.       // Also prevent writing outside the project path. That is not overridable.       const fullOutputPath = path.resolve(buildOptions.outputPath, asset.output);       if (!fullOutputPath.startsWith(projectRoot)) {         const message = 'An asset cannot be written to a location outside the project.';         throw new SilentError(message);       }
What flag is told about?

@gvart I think that the flag is allowOutsideOutDir in the last section.

Same problem

I think allowOutsideOutDir applies to asset copying - is this not different to build destination?

ya, something wrong when build.
{
      "root": "src",
      "outDir": "../../../target/frontend",
      "assets": [
        {
          "glob": "**/*",
          "input": "./assets/",
          "output": "../../../target/frontend",
          "allowOutsideOutDir": true
        }
      ],
...}
ya, i can't get it working.

{
      "root": "src",
      "outDir": "../../../target/frontend",
      "assets": [
        {
          "glob": "**/*",
          "input": "./assets/",
          "output": "../../../target/frontend",
          "allowOutsideOutDir": true
        }
      ],
...}

I'm not sure this covers every possible scenario, but the obvious thing to do is use an npm script to copy thing post-build
package,json
  "scripts": {
    ...
    "build-prod": "ng build --prod --stats-json",
    "postbuild-prod": "copyfiles ./dist/**/* c:/dist",
  },

This is quoted from issue 8122, and seems fair enough as a precaution.

This is done so that people don't overwrite their app by mistake (or a malicious app overwrites system files).

So, requiring the developer to specifically copy via script achieves both objectives.

And what about the --watch option ?

Patching the 1.5.4 with fix in #8630 solve the problem, so just wait for the next release.

oh man...

Does the merge also make ng serve work? The flag makes ng build work, but not the serve command yet. This was a rather bad error on Angular's part, it's very often neccesary for testing purposes to access dirs outside the ng cli project home dir, i.e. images, etc.

...same problem here, what about ng serve guys? ... 🙁

#8630 solves the problem. Until the fix is released, it's better to lock the cli version at 1.5.3.

Damn, no wonder, I was like, it was working at work before the weekend, why is it not working at home?
I was scratching my head so much I am almost bald now.

I'm glad  this is being fixed. I prevent my destination folder from being deleted by the CLI with the new "no-delete-output-path" option.  Not a problem.
"start": "ng serve --proxy-config proxy.conf.json --no-delete-output-path",
"build": "ng build --watch --no-delete-output-path",

when will this be fixed ...

@Sanafan You could look into it. It's marked as an easy to fix regression

This error is still occurring in 1.7.4. It's highly problematic for a project I'm working on since I have around 5GB worth of images to serve and placing them in the assets folder causes the ng serve to crash.
For anyone looking to fix it locally, edit<EMAIL_ADDRESS>The code starts at line 99. I'm not going to make a pull request to fix it because I don't know if there is a legit reason for this functionality (although it seems odd to me and as others have mentioned, it's not really a security thing).


Update command to electron-windows-store

Not 100% sure on this one, but it looks like this should reference electron-windows-store instead of https://www.npmjs.com/package/electron-windows-installer

Yes, you're totally right. I'm not smart.


add more cases for diff and patch tests

This refers to issue 13 https://github.com/Skinney/differ/issues/13 and
12 https://github.com/Skinney/differ/issues/12
The test should pass after those issues are solved

Thank you for this! I will review and push out a new build tonight :)

Thanks for accepting and merging!

Thanks for improving differ!


Replace redundant paragraph text in library.properties

The Arduino IDE's Library Manager displays the text defined in the library.properties paragraph field immediately after the sentence text so it's not desirable to duplicate the sentence text in paragraph.

Thank you!!


proxy configuration for npm test

I am using webpack-starter-angular2 project.
To make proxy for api i have used code as below
devServer: {
....
proxy: {
'/api/*': {     target: 'http://localhost:9090/',  secure: false   } }
},
Now I need to run npm test command so there urls are not redirecting to the proxy.
urls are like /api/v1/authenticate,
but i want urls should be like
'localhost:9090/api/v1/authenticate'
In which file do i need to set the proxy and what would be the code for that?
webpack.test.js or karma.config.js
Thank you.

You should be able to set up the configuration in your protractor config file See Selenium docs
It should look something like:
capabilities: {
  browserName: 'firefox',
  proxy: {
     proxyType: 'manual',
     httpProxy: 'localhost:8443',
     sslProxy: 'localhost:8888'
  }
}