Worse results by reproducing MoCo, InsDIS and CMC on ImageNet100

Hi @HobbitLong,
Thanks for your nice paper and publlic code!
I have reproduced results of MoCo and InsDIS on ImageNet100 following your steps.
I got 67.44 for MoCo and 66.02 for InsDIS, which are worse than the expected 73.4 and 69.1.
Could you please help me about this?
Best
Mengyuan

Hi, @nkliuyifang ,
Can you share more details? e.g., training command line, testing command line.
How is the result for CMC on your end? I want to see if this is a common issue for all of the three or only InsDis and MoCo.

Hi, @HobbitLong ,
The best result of CMC using "--view YCbCr" and "--nce_k 16384" is 70.54
The corresponding training command line is:

The corresponding testing command line is:

All related results of InsDIS, MoCo and CMC on ImageNet100 dataset is listed as follows, where the training set of ImageNet100 is used for both unsupervised learning and fine-tuning, and the testing set of ImageNet100 is used for testing classifiaction results.

Hi, @nkliuyifang,
I can see several gaps as below, which apply to all MoCo, InsDis, and CMC:
(1) For pre-training on ImageNet100, use batch_size 128 instead of 256. This is equivalent to increase the learning rate a bit.
(2) Switch from NCE loss to softmax-ce for pre-training
(3) Use a learning rate of 10 for linear probing stage, as can be found in README

Hi, @HobbitLong,
Thanks! I will modify these settings and try again.

I have reached the expected result. Thanks!


IOS : 1 scan -> 1 alert, 10 scans -> 10 alerts

Hello,
On IOS 11 iphone8, on my app when i click a button it start NFC dialog (beginSession). I asked to display alert message with '123'. Everything worked. But if i press again the button, it start NFC dialog, i scan, and it display 2 alerts. (twice same alert with '123'). Same if i scan 10 times, 10 alerts.
How can i clear or reset the NFC CORE memory?
this is part of the code
nfc.beginSession(
function () {
nfc.addNdefListener(function (nfcEvent) {
alert('123');
Someone got the same issue?

Can't explain why but dont have this issue anymore. Sorry


Proposal: introduce "throws" keyword for error handling

First of all, I prefer leaving if err != nil alone, it's quite good. But if we must add something for error handling, here's a new approach to replace try().
The proposal suggests to add a new keyword throws for error handling.
The signature is simple:
// return the original error
func testFuncA() error {
    result, err := fooFunc() throws err
}

or
// return a new wrapped error with contexts
func testFuncB() error {
    message: = "error message"
    detail := "error detail"
    code := 500
    result, err := fooFunc() throws NewBarError(message, detail, code, err)
}

where NewBarError returns a new error of type BarError which implements the standard error interface.
In both cases, the last return value of enclosing function must be error interface type. if err != nil, the expression following throws will take place and the enclosing function returns with the expression evaluation result as the value of its last return parameter(error type) and its other return values are the type default values or the value of current corresponding variable(for named return parameters) .
If err == nil,  the expression after throws will not execute and the program goes on.
Examples:

The CopyFile example from the overview becomes:

func CopyFile(src, dst string) (err error) {
        defer func() {
                if err != nil {
                        err = fmt.Errorf("copy %s %s: %v", src, dst, err)
                }
        }()

        r, err := os.Open(src) throws err
        defer r.Close()

        w, err := os.Create(dst) throws err
        defer func() {
                w.Close()
                if err != nil {
                        os.Remove(dst)
                }
        }()

        err := io.Copy(w, r) throws err
        err := w.Close() throws err
        return nil
}

An example of returning custom error(an echo middleware example):

package main

import (
	"fmt"
	"net/http"

	"github.com/labstack/echo/v4"
)

const (
	successCode                   = 200
	serverErrorCode               = 500
)

// IngressError is the return error of manipulating ingresses.
type IngressError struct {
	httpCode int
	Code     int    `json:"code"`
	Message  string `json:"message"`
	Detail   string `json:"detail"`
}

// Error returns the formatted string of an IngressError.
func (e *IngressError) Error() string {
	return fmt.Sprintf("httpCode=%d Message=%s Detail=%s", e.httpCode, e.Message, e.Detail)
}

// NewIngressError returns a new IngressError.
func NewIngressError(httpCode, code int, message, detail string) *IngressError {
	return &IngressError{
		httpCode: httpCode,
		Code:     code,
		Message:  message,
		Detail:   detail,
	}
}

// CreateIngress creates an ingress
// POST /ingress
func CreateIngress(next echo.HandlerFunc) echo.HandlerFunc {
	return func(c echo.Context) error {
		spec := c.Get("spec").(*types.Spec)
		namespace := spec.Namespace
		name := spec.Name
		client := ingress.NewClient(namespace)
		message := fmt.Sprintf("create ingress error: %s/%s", namespace, name)
		result, err := client.CreateIngress(name, spec) throws NewIngressError(http.StatusInternalServerError, serverErrorCode, message, err.Error())

		c.Set("data", result)
		return next(c)
	}
}

I believe this approach may handle more scenarios than the try built-in proposal, especially when you need to wrap a new error for different function calls.
Drawbacks:

introduce a new keyword.
the code following throws may make the line longer(it depends).

Ah, another one...

This seems to be very similar to #32848.

@sirkon Please stay polite in discussions on this issue tracker.  Please see Gopher Code of Conduct at https://golang.org/conduct.  Thanks.

@sirkon Please stay polite in discussions on this issue tracker. Please see Gopher Code of Conduct at https://golang.org/conduct. Thanks.

@ianlancetaylor
I try to be rational, not polite. This recent “try” proposal allows
info := try(try(os.Open(fileName)).Stat())

I can easily imagine me, senior, making such a mistake when I’m tired, not to mention middles and juniors. Remember Murphy’s law?
  I hope you understand the message.

Just throwing it out there ...
and if we replace throws with ? ?
info := os.Open(fileName)?.Stat()?

(? equivalent to "if res is not nil and err from return is not nil")

Just throwing it out there ...
and if we replace throws with ? ?
info := os.Open(fileName)?.Stat()?

(? equivalent to "if res is not nil and err from return is not nil")

And we will have file descriptor leak

@sirkon -- so  the original "try" does Close too, or it leaks too?
info := try(try(os.Open(fileName)).Stat())

@sirkon -- so the original "try" does Close(), or it leaks too?
info := try(try(os.Open(fileName)).Stat())

No, it doesn’t. We don’t have a RAII in Go, so this essentially means a leak.

Thank you. Means ? is no worse than try, but unfortunately no better either...
(to expand a bit, I am thinking out loud here)
info := os.Open(filename)?.Stat()?

to be equivalent to
func stat(filename string) os.FileInfo {
	var info os.FileInfo
	{
		var a1 *os.FIle
		if a1, err := os.Open(filename); err != nil || a1 == nil {
			return _, err
		}
		var a2 os.FileInfo
		if a2, err := a1.Stat(); err != nil || a2 == nil {
			return _, err
		}
		info = a2
	}
return info
}

Thank you. Means ? is no worse than try, but unfortunately no better either...
(to expand a bit, I am thinking out loud here)
func stat(filename string) os.FileInfo {
     info := os.Open(filename)?.Stat()?
     return info
}

to be equivalent to
func stat(filename string) (os.FileInfo, error) {
	var info os.FileInfo
	{
		var a1 *os.FIle
		if a1, err := os.Open(filename); err != nil || a1 == nil {
			return _, err
		}
		var a2 os.FileInfo
		if a2, err := a1.Stat(); err != nil || a2 == nil {
			return _, err
		}
		info = a2
	}
	return info, nil
}

Yes, exactly

(continue TOLH)
func stat(filename string) (os.FileInfo) {
     file := os.Open(filename)?
     defer file?.Close()
     return file?.Stat()?
}

func stat2(filename string) (_ os.FileInfo, err error) {
     f, err := os.Open(filename)
     defer f?.Close()
     return f?.Stat()
}

(continue TOLH)
func stat(filename string) (os.FileInfo) {
     file := os.Open(filename)?
     defer file?.Close()
     return file?.Stat()?
}

func stat2(filename string) (_ os.FileInfo, err error) {
     f, err := os.Open(filename)
     defer f?.Close()
     return f?.Stat()
}

This is complicated. Better to invent RAII

defer is Go's RAII.  I am not smart enough to see something descriptive and working at that level short of destructors from c++.

@tandr Go type system cannot even warn you about lack of resource release. It is already an issue even though  we actually have sane syntax and semantics what softly directs  us to care about it.

@sirkon

I hope to be rational, not polite.

At least in this community, please be both rational and polite.  Thanks.

Guys, so far , is anyone realize that the try-catch is the best ?

As was mentioned, this is a lot like #32848, except that this variant only permits returning from the function.
It's not clear to me that we need a new keyword here; can we just use return?
This has the same odd assign-on-the-left then execute-on-the-right as in #32848.

As was mentioned, this is a lot like #32848, except that this variant only permits returning from the function.

That's the sell point, just return an error when applicable, and do no more to keep things simple.
This is like what try() tries to achieve and seems to be clearer. It also can handle more scenarios than try(), since we can return a new wrapped error with contexts -- that's the usual.

This has the same odd assign-on-the-left then execute-on-the-right as in #32848.

That's true, but is to reduce the if err != nil typing. And here's another advantage to try(), it keeps same number of variables on the left side of an assignment statement as the called function returns on the right side.

It's not clear to me that we need a new keyword here; can we just use return?

As of its 'assign-on-the-left then execute-on-the-right' nature, we should not confuse the return keyword use, and the keyword throws can better indicate the purpose and when to use it.

This has the same scoping problem as #32848: variables being defined in an assignment statement must come into scope at the point of the throws keyword.
In any case closing as dup of #32848.  The differences here seem like minor details.


Fix usage with --inspect flag

Mocha has poor error reporting for crashes that happen before tests start running. For those situations, the recommended debugging method is to use the --inspect flag, which is a Node feature.
Currently, when using --inspect along with test-environment, the following happens:

the debugging server is started and correctly reports errors
the ganache server fails to load (all calls to it timeout)
the following message is logged: Starting inspector on <IP_ADDRESS>:9229 failed: address already in use

What is going on here is a bit tricky. --inspect creates a server in port 9229, so no two processes may run with that flag at the same time. However, as has been noted on the Node repo, this is precisely what happens with .fork is used. This is because fork forwards execArgv by default, passing the child process the same options the parent one received (process.execArgv).
From the Node docs:

process.execArgv
This is the set of node-specific command line options from the executable that started the process. These options do not show up in process.argv, and do not include the node executable, the name of the script, or any options following the script name. These options are useful in order to spawn child processes with the same execution environment as the parent.

To preserve this intended behaviour, this PR simply prevents the --inspect flag from being forwarded.

Perfect fix, thank you. Do you have a link to the way Mocha is used with —inspect? I would like to understand the expectations of someone using the flag, and if disabling the flag for the forked process would result in anything unexpected. In any case there doesn’t seem to be any alternative.

From my understanding, --inspect is quite powerful and is a generally useful debugging tool. In Mocha's case, the use I've found for it is simply to debug issues in the setup of the suite, where Mocha will simply print the error message and not show a stack trace, or even the file or line number that emitted the error.


get-in-here.yml =>[updated]

PR Type: ___

Affiliation: N/A

Ticket: N/A

Checklist:

[x] I've read Contributing Guidelines
[x] I agree to follow the Code of Conduct

🤞hopefully i have done it right as this is my first pull request . So, a bit nervious

You've done it perfectly :)
Thanks @TechoChat


Default priorityClassName to blank string

Issue #, if available:
Relates https://github.com/aws-controllers-k8s/code-generator/pull/249
Relates https://github.com/aws-controllers-k8s/code-generator/pull/252
Description of changes:
This fixes a bug I introduced in a previous PR (sorry!)
This must default to an empty string rather than null or you get:
Error: values don't meet the specifications of the schema(s) in the following chart(s):
s3-chart:
- deployment.priorityClassName: Invalid type. Expected: string, given: null

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

All good. Thanks
/lgtm


Set max width on images within TinyMCE

The grumpycat picture in https://github.com/jacobobryant/platypub/issues/14 reminded me that images in the editor are displayed at full width. Better if we make them shrink so they don't overflow on the x axis.

I've been manually re-sizing images to 800 or 1024 pixel-width prior to upload.  I'd be nice to skip that step if upload-image could handle that step.

Hm, that should be doable... I've made a second issue for this: https://github.com/jacobobryant/platypub/issues/23

(for this issue I'm basically just thinking about setting style="max-width:..." on image elements inside TinyMCE; I'm hoping TinyMCE has an option for that we can flip on)


Added documentation for the "native" DF-MP2 implementation.

This is documentation for the new DF-MP2 code from pull request https://github.com/pyscf/pyscf/pull/963.
Please do not merge this without the pull request to the main pyscf code, otherwise this documentation will describe a non-existing feature.

Thanks for the docs!


General/threadingPolicy Preference Usefulness

Describe the Bug
The General/threadingPolicy preference is not documented anywhere and it is not possible to change it from the user interface.
Does someone know what it is/was used for? Is it still used (in this case it should be documented, at least on the wiki if used for debugging) or can we remove it?
https://github.com/omichel/webots/blob/0aee13196d44be0aea6232113224f4b8255efb9e/src/webots/core/WbPreferences.cpp#L67
https://github.com/omichel/webots/blob/0aee13196d44be0aea6232113224f4b8255efb9e/src/webots/engine/WbSimulationWorld.cpp#L323

Unless someone raises a good reason for keeping it, I would remove it.

I think it can be removed.
I retrieved a log description from an old commit of Mustafa:

Log:
ODE_MT 2.0 ---> 1. refactored code in util_MT.cpp to the folder ode_MT. definitions in util_MT.h are now in ode_MT.h 2. Made interfaces for threading and clustering. A Cluster Manager now handles the creation, update and deletion of clusters. 3. A ThreadManager now handles the creation, update and deletion of threads. 4. ThreadManager has a version for both Pthread and OpenMP. 5. Switched threading implementation to OpenMP. 6. If you notice your computer in hyperdrive (all cpus loaded 100% all the time when running webots), please add the OMP_WAIT_POLICY=PASSIVE as an environment variable before you run webots.

Fixed in #336


Build against latest version of prometheus golang-client

This pull request works again with the latest version of prometheus golang-client where in this commit the counter.Set method was removed.

Thanks @jlemaes for this change. Matching the new prometheus_client is the inevitable way forward.
I'll run this through some testing and if that is successful, this can be approved.

We have started using the exporter with this pull request applied on a new MongoDB cluster. It worked fine until ~5 minutes after we started inserting data, when all mongos metrics collection stopped.
The collectors pointing to the mongos daemons now return a 500 error with the following message:
An error has occurred during metrics collection:

6 error(s) occurred:
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"moveChunk.from_failed" > counter:<value:4 >  was collected before with the same name and label values
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"moveChunk.from" > counter:<value:3 >  was collected before with the same name and label values
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"multi-split" > counter:<value:18 >  was collected before with the same name and label values
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"moveChunk.start" > counter:<value:7 >  was collected before with the same name and label values
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"moveChunk.to" > counter:<value:3 >  was collected before with the same name and label values
* collected metric mongodb_mongos_sharding_changelog_10min_total label:<name:"event" value:"moveChunk.commit" > counter:<value:3 >  was collected before with the same name and label values

There are no errors or warnings on the collector log files. Restarting the collector results in the same error.
Metrics for mongod processes work fine, it's just mongos that fail.

There was a bug in the code that should be fixed now thanks to @mathieuhinderyckx. I don't have time to test this against a mongos cluster. Can you please try again?

This will need to wait a week or two as we are currently code locked for a new PMM release (currently in beta)

I have applied the latest commits and the exporter is working fine now, even during chunk migrations.

I've seen no issues in the testing of this PR. We will merge this soon

Hello  @jlemaes  ,  please sing Percona CLA so we can merge your PR
Thanks for Contributing!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: timvaillancourt:white_check_mark: jlemaes:x: Mathieu HinderyckxMathieu Hinderyckx seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Any update on when this might get merged? I was putting off using this exporter until this and #52 are merged.

Can you please resolve merge conflicts?

Original reported issues is solved by #67.


1908

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #1908
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@MundaneImmortal Thanks for posting pull request. you need to fix the golangci-lint errors. you can execute make lint command locally to check golangci-lint errors.

@rambohe-ch Thanks for your feedback, I have fixed that and committed again.

/lgtm

@MundaneImmortal I am very appreciate for your first pull request, and i will merge it because all github actions(except codecov/patch) are passed.


Usage of ofxLeapMotion2 in Linux

hi!
first of all, thanks for providing this update for LM2. I-ve been trying to use this library through its example in a Qt project, and seems like there's some problems. What I did was to create an oF project in the project creator for qt, and then import this project into qt. That's it! haven't modified the code or manipulated or such... first I wanted to see it working as natural as possible..
and when I try to compile it, I get these errors:
/OF/libs/openFrameworks/utils/ofConstants.h:400: error: expected unqualified-id before numeric constant
#define PI       3.14159265358979323846
^
and
/OF/libs/openFrameworks/utils/ofConstants.h:400: error: expected ‘)’ before numeric constant
#define PI       3.14159265358979323846
^
and some similar others...
would you have an idea if they have a collision or conflict with the LeapMotionMath library or something? because I think this is where the problem is, but not sure yet... or what would you think the problem is?
Thank you, any help will be appreciated!

Ok, that problem is solved, although now I have a more concerning issue... Have you experienced a segmentation fault issue? I integrated the ofx in a project and when I move really fast my hands and fingers, it throws a Segmentation fault saying> RTTI symbol not found for class 'Leap::Interface'
Have you experienced something like this? does that ring a bell?
Thanks for the attention!

@AdriannaGmz  Did you ever figure this out? I am having the same segfault issue with fast hand movement.
It is really concerning as I have a few performances lined up where I use the leap between 3 performers and some of them arent as cautious with the fast movement


When Try To Modify CROWDSALE End date Show Error Massage?

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Mainnet
If you were able to create it, what is the URL of your crowdsale?
https://wizard.oracles.org/manage/0x9E96c74a4e074cb95F4299A661317E8a30244e55
Do you have screenshots showing the problem?
*
*
Do you see errors in the dev console? If yes, please include a screenshot
To open the dev console in Google Chrome, press F12, or go to View -> Developer -> Developer Tools, and open the Console tab
If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.
Your answer

Look like it is duplicate of https://github.com/poanetwork/token-wizard/issues/728

Fixed in https://github.com/poanetwork/token-wizard/pull/766


Url confirmation

Hi,
I am porting this lib into JAVA. However, I need to confirm the final url because it is failing with 403 err.
Please confirm following url format for q="hello":
https://translate.google.com/translate_a/single?client=t&dt=at&dt=bd&dt=ex&dt=ld&dt=md&dt=qca&dt=rw&dt=rm&dt=ss&dt=t&ie=UTF-8&oe=UTF-8&otf=1&ssel=0&tsel=0&kc=7&sl=en&tl=bn&hl=bn&q=hello&tk=29979.29979

This library is using an invalid token. Try porting from https://github.com/vitalets/google-translate-api (which has fixed this issue and others) instead, or at least fix your port using ported fixes from that repo.


Remove mongo from Project

Pymongo was being used in the Sum Mongo Count files. These were no longer used so I removed them.
There are dependencies in the existing work-server package. This should be removed when that task is completed.
The other major dependencies seems to be in the job_validator. This should also be removed in the work-server removal.

The other major dependency seems to be the validator. Can the people who worked on the validator assist?

This is not ready for merge yet!

This PR is ready for review.


support layout variants

This PR makes it possible to switch between layouts with different layout variants.
Example usage:
path/to/i3-keyboard-layout cycle "bg bds" "bg phonetic"
or
path/to/i3-keyboard-layout cycle us "bg phonetic"

Great stuff, it works perfect! Thak you :smile_cat:


README.md: fix typo in git_stash description

from "stashes you local modifications"
to   "stashes your local modifications"

Coverage remained the same at 93.43% when pulling ace6e882696110c88d97f6693010de471debd9e2 on josephfrazier:readme-git_stash-typo into a015c0f5e271e9e3c668a9c6a75d13f337baafd0 on nvbn:master.

Coverage remained the same at 93.43% when pulling ace6e882696110c88d97f6693010de471debd9e2 on josephfrazier:readme-git_stash-typo into a015c0f5e271e9e3c668a9c6a75d13f337baafd0 on nvbn:master.

Coverage remained the same at 93.43% when pulling ace6e882696110c88d97f6693010de471debd9e2 on josephfrazier:readme-git_stash-typo into a015c0f5e271e9e3c668a9c6a75d13f337baafd0 on nvbn:master.

Coverage remained the same at 93.43% when pulling ace6e882696110c88d97f6693010de471debd9e2 on josephfrazier:readme-git_stash-typo into a015c0f5e271e9e3c668a9c6a75d13f337baafd0 on nvbn:master.

Coverage remained the same at 93.43% when pulling ace6e882696110c88d97f6693010de471debd9e2 on josephfrazier:readme-git_stash-typo into a015c0f5e271e9e3c668a9c6a75d13f337baafd0 on nvbn:master.

Thanks!


About gpu cost

Hi, may I ask what is the gpu memory cost during inference? Is a 2080ti enough to run inference code?

they have a collab and hf so will assume 16gb vram is enough


Releases being created with the same date

Every time I push a new release to github, it uses the exact same date as all my other releases. They all say "10 days ago". Running on OSX.

Solved. The latest release takes on the date of the latest commit, regardless of when the release is uploaded.


Update trace4cats-core, trace4cats-meta, ... to 0.13.1+106-d0c19130

Updates

io.janstenpickle:trace4cats-core
io.janstenpickle:trace4cats-meta
io.janstenpickle:trace4cats-tail-sampling

from 0.13.1+67-a7d9b849 to 0.13.1+106-d0c19130.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.janstenpickle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.janstenpickle" }
}]

labels: library-update, early-semver-build-metadata, semver-spec-build-metadata, commit-count:1

Superseded by #173.


[WIP] Add get Posts endpoint

Coverage decreased (-5.05%) to 78.75% when pulling 818e1510d99662c0781e0fbe198013911dfc9ae8 on add-get-tils-endpoint into 90bea5f35fc9d0360bf1ede86edff65ea3cd5225 on master.


Improved iCloud 2FA support

Description:
I couldn't for the life of me get the iCloud component to work.  After a lot of experimentation, I realized the issue were the fields= arguments being passed to the callbacks used.
Along the way, I added better rendering for SMS-based trusted devices, added some improved logging, and moved the configuration logic mostly out of the event loop to allow it to work "real-time" without waiting for a 10-59 second delay between every step of the process.
No configuration changes need to be made for this to work, and no new documentation changes should be required.
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hello @reedriley,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

16c298caa5658ce435140a828842062beb3b5839 - This commit has something that looks like an email address (reedriley@nox.local). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

Hi @reedriley,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @reedriley,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Any updates on this PR?

Hi @reedriley,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

(I believe this may fix issue #4259 as well.)


Update deploy.sh in gh-pages.md

Clarify documentation for deploy.sh in gh-pages.md](https://github.com/MoOx/statinamic/blob/next/docs/content/docs/usage/gh-pages.md#create-a-script)
I create an issue for this #388
I hope this is helpful

Nice, thanks!

Will be online for the next release (before the end of the week).

Thanks !


Add support for ESPOE32 board

Somehow missed off the platformio.ini file from my last request.

This should close #381

Squash 0a719cb and 1dbbb6e into a single commit.

@bgcngm that took some effort, but I think I did it

This might be helpful,

Thanks @swalsh11 it is a shame that there's not any extra pins for the relay.

It comes in a nice case, and it is easy to just add a new 5 pin header onto the grove port cable supplied. I use JST connectors, modified with a scalpel,  overall not a bad option if you do not have a 3d printer.
I think it might be possible to break out an I/O from the ESP32, But I do not have a use for that

I will test in POE mode, and also powered from the X10 mode, I will see  is there any difference in performance,

It comes in a nice case, and it is easy to just add a new 5 pin header onto the grove port cable supplied. I use JST connectors, modified with a scalpel, overall not a bad option if you do not have a 3d printer. I think it might be possible to break out an I/O from the ESP32, But I do not have a use for that

Yes I have few reasons to get a 3d printer and I can live without the relay for now.

Looking at the Schematic, IO2 on the Bottom Right, Looks like it could be used for an additional relay.

Thanks @Alibloke, I just approved another PR for the m5stickc2. Yours conflicts now on the platform.ini.
Could you please update it so I can approve it?

Will do, should have time to look at it in a few days.

@raomin all sorted now

Not exactly, proper way would be to rebase all commits.

Hello, Did POEESP32 support get added? Did doesnt appear when I change the environment

Hi,
I'm also interested in this ESPOE32 support.
Is it already foreseeable when this PR will be merged to main?
Thanks


Add 'prompt=consent&access_type=offline' to request to get refresh token

If a user logs in using Google more than once, the second and subsequent times they are not provided with a refresh token, which causes the following exception:
'package:googleapis_auth/src/auth_http_utils.dart': Failed assertion: line 98 pos 16: 'credentials.refreshToken != null': is not true.
auth_http_utils.dart:98

The issue is explained here:
https://stackoverflow.com/a/10857806/3950982
The fix is to add prompt=consent&access_type=offline to the request, to require the user to consent to Google login each time.

Actually this change seems to have no effect...


Oxen test fixes and improvements

This PR supercedes #16 and adds other some other small changes and capabilities to go with the high-level Oxen wallet ledger test suite (https://github.com/oxen-io/oxen-core/pull/1640).

Hello @jagerman ,
Thanks for the contribution, this PR looks good to me, you'll need to bump the version however
Also you might be interested in the test framework we developed, it's a pytest based framework that handles the Speculos, automatic screen navigation, screenshot comparison, etc
https://github.com/LedgerHQ/ragger
Seen in use here for example
https://github.com/LedgerHQ/app-boilerplate/tree/master/tests
Let me know if you find it useful or have remarks

Hi @jagerman can you please add the guidelines_enforcer as done here :
https://github.com/LedgerHQ/app-boilerplate/blob/master/.github/workflows/guidelines_enforcer.yml
In a follow-up PR ?

Hello @jagerman , I've taken the liberty of bumping the version number, otherwise we can't deploy on our provider

cc @darcys22


⚠ Young Discoverers has degraded performance

In 6588db2, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 7547 ms

Resolved: Young Discoverers performance has improved in ca7b165.


Add OpenOneLine, CloseOneline and update_ui functions

Add OpenOneLine, CloseOneline and update_ui functions, with their corresponding tests

@mzy2240 - if you could please review my commit I'd appreciate it. In short, I think that if we're implementing a ScriptCommand function we should include all optional parameters in our wrapper. Also, some type hinting was missing.


dynamic addRoutes in plugin beforeEach hook

I have problem with “dynamic addRoutes in plugin afterEach hook”
This is very interesting, since it allows you to implement almost any url, for example, from the root "/" can be
/category_slug
/post_slug
/other_slug
My part of config
module.exports = {
ssr: true,
mode: 'universal',
...(!isDev && {
modern: 'client'
}),
..
plugins: [
'~/plugins/route'],
}
plugins/route.js
function interopDefault(promise) {
return promise.then(m => m.default || m);
}
export default ({ app, router, routeres}) => {
app.router.beforeEach((to, from, next) => {
app.$axios.get('/seo/find_by_slug', {
params: {
slug: to.path,
locale: app.i18n.locale
}
})
.then(function (response) {
// response.data.view  maybe category, post
let dynamicView =  () => interopDefault(import('@/pages/'+response.data.view+'.vue'));
app.router.addRoutes([
{
path: to.path,
component: dynamicView
}
]);
app.context.next(to.path);
})
.catch(function (error) {
console.log(error);
});
})
}
When I disable ssr (ssr: false), it is work fine, but when I set “ssr: true” return 404 error "This page could not be found"
Versions

nuxt:  2.14.7
nuxt-i18n: "6.15.4"

Reproduction

Sorry but I don't have time to investigate your issue that doesn't seem to be directly related to nuxt-i18n.

Sorry but I don't have time to investigate your issue that doesn't seem to be directly related to nuxt-i18n.


Modified Makefile to work on ukwiki

Codecov Report

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

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   39.87%   39.87%
=======================================
  Files          16       16
  Lines         474      474
=======================================
  Hits          189      189
  Misses        285      285

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 f812dee...6c8e000. Read the comment docs.

@HAKSOAT This looks like it is in a good place.  Is it ready for review?

@halfak Yes. However, it is tied to this task. So I think when that task is done, then I can be sure of this PR. I was basically only experimenting with cutoff though to see if I'd get better results with the model metrics.

OK I'll hang tight then.  Please feel free to ping when you think this is ready to merge :)


Progress event not fired unless added before end is called.

You should still be able to register events after end is called to the request object after the end method is called. Here you can see that it only registers the progress event if it has been preregistered. This should be fixed.

No, end is the end.

Ripadipdip :skull:


Disable 'Python: Create Terminal' when python interpreter is not an environment that can be activated

Assume python environment selected in VS Code is not an environment that can be activated (not Conda environment and not a virtual env or the like)
In such instances using the command Python: Create Terminal will not activate the python environment in the terminal

Problem: Using python in the above terminal will not necessarily point to the same python interpreter selected in VS Code.

I'm having second thoughts about this change, @brettcannon and I agreed on this change.
@qubitron Please could you provide your feedback as well. Thanks.

@DonJayamanne users will still see the create integrated terminal command in the completion list, and the command has only been around since the Jan release, so I'm not concerned about taking the command away. The bigger issue for me would be that it is not clear to the same user why the same command is sometimes present and sometimes not.
We could rename the command to something like "Create Environment Terminal" so that it's clearer this command is meant to be used with conda/venv/etc. environments, and there is an expectation that it is only available if an environment is created. Moving forward, users who do not use environments would not see it.
It would be nice if we could somehow make the existing command prepend/append the path in a way that mostly works, but I know there are some challenges with that.

It would be nice if we could somehow make the existing command prepend/append the path in a way that mostly works, but I know there are some challenges with that.

Yes this could be done, however @brettcannon wasn't sold on this approach.

but I know there are some challenges with that.

To my knowledge we just need to append the VirtualEnv/Scripts (for Windows) or VirtualEnv/bin path (for Unix)

You would have to prepend it to override the defaults on PATH and hope you don't break the user's environment because it assumes a certain PATH resolution for e.g. python3.

Sorry yes, prepend

@qubitron
Bad news, setting path isn't sufficient as the name of the executable too needs to be defined.
I'm closing this issue as Brett and I both agree this is just getting too messy & not clean enough.


If DITA topic is not wellformed and prolog updating is disabled I still get a warning message

Oxygen should not report the topic is not wellformed because the prolog updater is disabled.

Is this issue still valid?

We fixed this issue in the new version: 1.1.0.


how do I specify multiple api hosts for the same API?

here is the scenario:
I have multiple nodejs instances serving the same API. Its a traditional Express JS app/website with cookie based sessions and routes/endpoints defined. The instances are behind HAproxy.
Now, I want to be able to introduce Kong in the mix, so third party consumers could access the backend API (exposed by nodejs instances) thru OAuth 2.0.
Where in the stack should Kong be introduced? How do I add multiple nodejs instances( host+port) to the same API instance included in Kong?

I think you are talking about #1735, which allows load balancing between multiple instances of the same service.

i think, you're right.
But, what  are people doing right now? API instances behind HAproxy etc or multiple Kong instances (1 per API instance) behind HAProxy or something else?
That'd add another layer to the stack though.

I think you will need to split your application into a frontend and a backend component in order to do this "right". The "classical" approach to this would be to have a pure API service which is always secured behind Kong using OAuth 2.0; the API is stateless, and takes the user information from the X-Authenticated-Userid and X-Authenticated-Scope coming from Kong.
Another thing which is in this case needed is an Authorization Server which talks to Kong via the backend (Admin API), of which the main purpose is: Establish User Identity and Authorize the User. This will give you an Access Token back, using one of the standard flows, i.e. Authorization Code or Implicit Grant (for SPAs or such).
After that, you will need to refactor your frontend application to also work on top of your backend API, using OAuth2. This will be a special sort of client for your backend API, it will be a "trusted" client, which in effect means that your Authorization Server must know this and e.g. assign all OAuth 2.0 scopes to the Access Token if requested by your own application.
In contrast to this trusted application, other clients of the API are not trusted, and will need to ask permission of the end user (this is also something the Authorization Server has to take care of in case a Client Application comes around which is not trusted) to access the API on his behalf, using some kind of OAuth Scope.
As you see, it's not quite just "adding Kong to the mix", your application needs quite some refactoring in order to make it "standard". I bet there are ways of doing this directly in your application, but really taking the components apart makes it a lot clearer what each component has to do.
Recap, you need:

Backend API component
Kong securing the backend via OAuth 2
Frontend implementation as "trusted client" using the Backend API via OAuth2 (like everybody else, using Authorization Code Grant or Implicit Grant)
Authorization Server taking care of the Authentication and Authorization

Oh: And if you have multiple backend API instances, you'd need to load balance those externally, as Kong doesn't support multiple backends yet (as Thibault points out). Running everything in Docker, e.g. using Kubernetes or Docker Swarm and its service abstraction would solve this as well (both provide internal load balancing of containers).

In addition to @DonMartin76 s answer;

But, what are people doing right now? API instances behind HAproxy etc or multiple Kong instances (1 per API instance) behind HAProxy or something else?

I think the most common approach is to use a dns based loadbalancer behind Kong. Eg. Consul. The API instances register with Consul, and Consul provides a DNS record to Kong with the registered instances.

That'd add another layer to the stack though.

yes, until #1735 is released.

Closing this as I believe the question has been answered.

JFYI: Consul provides support for load balancing multiple instances (on the same host) through SRV records and Kong does not support SRV records yet. However, a single instance per host can be supported through A records (that are supported).


Close btn on alerts has bad :active appearance

It should look a lil better. If I could ensure the height of the btn I could use the native one. Otherwise I'll need a custom one

Gonna close as revisit...this is a pretty minor thing


Bump jax and jaxlib versions

Currently, we have pinned jaxlib==0.4.8 and jax=0.4.7 in the extras dependencies, but we could look into bumping the versions for a multitude of reasons:

CPU-only native support for amd64 Windows is available now which will enable the use of the Jax solver on Windows (CPU-only) with Python 3.9–3.12. We can mark the dependency with a conditional in setup.py as is standard practice so that there are no conflicts based on platforms and Python versions, and continue to support a lower version for Python 3.8 until we drop support for it (#3390). More details below
Availability of arm64/aarch64 wheels for Linux has been there since some minor versions already, this will be helpful for the current proposed solution for multi-platform Docker images in #3430 and will make Jax importable in Docker on M-series macOS machines, the current versions fail due to the use of emulation which does not support AVX instructions.
GPU support with Jax: this is available by compiling CUDA and CuDNN on WSL2 and installing the GPU-specific wheels from the Google indices or otherwise directly installing CUDA from the wheels. However, WSL2 requires administrator permissions to install on Windows machines. On Windows, there are some community-enabled wheels for jax with CUDA 11.8 and 12.1 with CuDNN 8.6 and 8.9 on https://whls.blob.core.windows.net/unstable/index.html and the instructions for their usage are at https://github.com/cloudhan/jax-windows-builder. On M-series macOS, GPU support is available through the Metal plugin https://developer.apple.com/metal/jax/ which was also noted in https://github.com/pybamm-team/PyBaMM/issues/3274#issuecomment-1737005840. Note: both of these are experimental at this time and potentially unstable, but can be documented as such in the installation instructions. The good things are that both of them are in sync and require the same version of jaxlib, i.e., 0.4.11, and that both of them have now been tested and all GPU-related functionalities in the unit tests seem to be working as intended.

(For more details, please see the extended discussion in the #infrastructure channel on Slack)
Therefore, the minimum version to update to could be jaxlib=0.4.11 and jax==0.4.11 with the internal version requirement being relaxed a bit in #3121. However, it is also easy to target multiple versions with conditional dependencies so as to accommodate most if not all of these requirements. Jax itself does this and this is a reference setup.py file, for example. Considering that GPU support should be kept standalone, it can be given its own extra dependency set, something like [jax-gpu], or just [gpu], considering that only the Jax solver has it.
A configuration in the setup.py file could look like this:
extras_require={
        # provides arm macOS wheels for Docker and native CPU-only support on Windows
        "jax": [
            "jax==0.4.18", python_version>'3.9','<3.12'
            "jaxlib==0.4.18",  python_version>'3.9','<3.12'
            "jax==0.4.1X" # some other minor version that includes support for
            #  Python 3.8 so that our installation does not break
        ],
      # provides GPU support for macOS
        "jax-gpu": [
            "jax==0.4.10",
            "jaxlib==0.4.11",
            "jax-metal==0.0.3"
        ],

Otherwise, given the tricky requirements for pre-compiling CUDA and CuDNN, a nox session or a helper script can be provided that can be used to fetch the correct versions with pip based on the platform.

Some more resources, collected from the Jax CHANGELOG (https://jax.readthedocs.io/en/latest/changelog.html) and related places on the internet:

Windows CPU-only wheels were first added in 0.4.13, unofficial ones existed for versions 0.4.9—0.4.11, Python 3.8–3.11
Windows unofficial GPU wheels are still at 0.4.11, with Python 3.9–3.11 for CUDA 11.8 and Python 3.10–3.11  for CUDA 12.1
Linux aarch64/arm64 wheels were added in 0.4.18, useful for our Docker images which have Python 3.9 by default (will soon be bumped to 3.11)
0.4.14 was the last version to support Python 3.8
M-series macOS GPU support (Metal plugin) requires Python 3.9 and above with 0.4.11. This requires jax-metal which in-turn requires building jaxlib from source.

Therefore it would be suitable to handle just CPU support in setup.py and add instructions in the documentation about how to enable GPU support on platforms (with helper scripts and a pybamm_install_with_gpu entry point to go with them possibly in our next release?)
The final dependency resolution, with all of the above information, should look like this:
extras_require={
        "jax": [
            # Linux aarch64 wheels for images on Docker Hub, Windows CPU wheels for 3.9–3.11
            "jax==0.4.18", python_version>'3.9','<3.12'
            "jaxlib==0.4.18",  python_version>'3.9','<3.12'
            # Last version to support Python 3.8, supports Windows too
            "jax==0.4.14", python_version=='3.8'
        ],
        ...

which should cover Windows (3.8–3.11), Linux (amd64 on 3.8–3.11, aarch64 on 3.9–3.11: there should be a way to check for the system platform for the latter), and macOS (3.8–3.11).

I shall work on this issue over the next week; I assigned myself this. It looks like there is a lot of repetition in the installation instructions so I'll do a rewrite of them—which I will hopefully keep to be minor—in the same PR. I am considering moving the section on "Optional solvers" to a separate page. Then, there can be just two pages (excluding the Docker instructions): one page for the user installation and another for the source installation (instead of having separate pages for GNU/Linux + macOS and for Windows).
I will also improve the content and structure in the pages where things do not seem to be clear for new users and add some more entries to the FAQ based on common issues we have noted recently, would love suggestions! (cc: @arjxn-py @Saransh-cpp). The goal should be to not let users get overwhelmed with all these different pages in such a sprawling installation guide – which is something that I admit to being when I was new to the repository last year.


Pagination Controls are not showing

Hi,  I have installed your module working with Asynchronous Data and everything seems to be working except for the pagination controls. Am using a custom dirPagination template but I have not changed anything from your template except for the angularJS tags, so instead of '{{, }}'  I use '<@ , @>' maybe that could be the reason? Below is screenshot of what is produced by dir-pagination-controls.

Maybe pages.length is empty that's why its hidden? but I did console.log(pages);  in generatePagesArray() and it  returns 1.
Thanks.

Never mind I got it fixed by using the built in template and a few minor fixes.
Thanks for the great module.


Improvements

Hi @laurapareja  !!!
Here you have some tips to improve the exercise:
JavaScript

[x] Remember to convert input value string to a number
[x] Remember that every time we use .innerHTML or .value to get DOM content we receive a string. Sometimes we will need to use something like parseInt() to convert it to a number

Advanced

[x] Move the feedback logic to a function an execute it on each click
[x] Move you counter logic into a function and execute it on each click
[x] You are writing many times "trackEl.innerHTML = 'something';", what about making a function that accepts a string as param and paints it into 'trackEl'?

JavaScript - Good practices

[x] Use === instead of == for comparisons

HTML

[x] Add form
[x] Connect the label to the input using the for attribute of the label and the id of the input
[x] Use placeholder attribute instead of value one to show a field's hint

Steps to finish the game (for those far from the solution)
You are close to the exercise solution, but here you have a steps guide to complete it anyway ;)

Save a reference to DOM elements in variables
Generate the random number and save it to a variable
Init counter of trials to 0
Define a function that executes when the user clicks on the button, that

increments the counter and paints its value in the HTML
collect the value of the HTML input and compare it with the random number

if they are equal, draw a 'You Win' message
if it's lower, draw a 'Too short' message
if it's higher, draw a 'Too long' message

Assign a listener to the button click to execute the previous function

Further challenges
Then you can improve the game as you please, here you have some ideas:

Add new feedback when the number is bigger than 100 or smaller than 0.
Manage when the user hits the button and the input is empty.
Make the input work when hitting enter key.
Add a reset button that cleans the input, the counter, writes the initial feedback and generates a new random number to play again!
Whatever you want!

Call to action
Let me know if you have any doubts ;)
Go for it!!


Shellcheck Fixup: SC2316

We were exporting 'readonly' not setting a variable 'readonly' then exporting it
https://www.shellcheck.net/wiki/SC2316

Well, that's a weird CI failure.
Seems to be a result of dropping the export; let's keep both lines!

Well, that's a weird CI failure.
Seems to be a result of dropping the export; let's keep both lines!

Oh, that's right. I forgot that Litestream needs it exported to populate the config file:
https://github.com/mtlynch/logpaste/blob/c1a96859b55d2fe6536f703ad19695601f071083/litestream.yml#L5


Fix issue #1734 consumer not reset offset

Fix issue #1734 consumer not reset offset when CURRENT-OFFSET greater than LOG-END-OFFSET

Could you review this PR and give me some comments @bai?


KYC : if a card is not obtained from the server (data not available), the card is removed from the discover

concerned credentials, especially with driving license:

nationality card
place of birth
gender


PeoplePicker - retrived items should contains loginName

Category
[x] Enhancement
Version
1.10.0
Expected / Desired Behavior / Question
It will be good if items that PeoplePicker retrieves could contains loginName info. Because not all users/groups has emails, sip, etc.
Suppose also IPrincipal should be expanded to contains loginName.
Thanks!

Also defaultSelectedUsers property in PeoplePicker now should contains only array of Emails but not all users and also Groups (Security, SharePoint) has it.
At the end it leads to wrong behavior of PeoplePicker control when you try to add (delete) or save value.
Suppose this property also should support loginName.
Thanks!

Hi @vlad-nvs,
Latest version (3.15.0) checks all the enhancements you've requested.
Can you confirm those?


New Debian package URL

There is a Debian specific package to be used instead of the ubuntu version.  The ubuntu version gave me problems with libc-version.

This should now be fixed by #14 .


Make make-user-data useful

Change make_user_data so it does NOT put the part-handler
Python script in the userdata output (since nobody is using this functionality).
Omit Yeti endpoints in brkt-config output by make-user-data.
Added a hidden --brkt-files arg to make-user-data, to facilitate adding files to /var/brkt/ami_config/ via userdata.
Added unit tests for the above.
Fixed test_parse_timestamps to use timestamps 10s in the future.

Testing:

Ran unit tests.
Ran MV instance with userdata containing a brkt-config blob of '{"brkt": {}}', to make sure the identity server didn't barf.

PTAL

I like it.  Thanks!  👍


Generate Swagger calls for all dataset/class combinations

This will also show nicely how the api grows as new data is being added to the knowledge-graph.

Won't fix. It's easy enough to add custom webservices.


it only works right after "Deploy"

Hello. (sorry for mi english).
I am using your node to communicate with a xiaomi temperature and humidity sensor.
I have node-red over a raspberry pi 3 and I'm using the internal bluetooth of the raspberry.
The node only works when I do a "deploy", then the node stops "timeout". And it does not work until the next "deploy".
It works only when connecting for the first time after the "deploy".
Any ideas?
Thank you very much for your work.

Can you please evaluate the latest version (3.0.0)?
Reopen the issue when you have still the problem.


Allow certificates errors only for the Electron-created back end

What it solves
This commit ensures that the Electron app allows only the Electron-created backend at https://localhost:5000 to have an invalid (self-signed) certificate.
How this PR fixes it
Instead of appending 'ignore-certificate-errors' to the command line, catch certificate errors and check the associated origin.
Reference: https://www.electronjs.org/docs/latest/api/app#event-certificate-error

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 32.278%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3083

Relevant Lines:
8488

💛  - Coveralls

Thank you for all the PRs @Vasco-jofra!


Update no longer worked with 3.0.12 and beyond

Hi, I have created a fix for a recent change on the teamspeak download site.

Changed tar.gz to tar.bz2
Added -j to tar extract command for bzip2
File prefix changed to teamspeak3-server_linux_amd64 instead of teamspeak3-server_linux-amd64.

Also added change of the executable file, apparently thats now ts3server instead of ts3server_linux_amd64.

bzip2 is missing in the dockerfile as dependency

Really? Works fine for me.

I am not a docker expert but in my generated image the bzip2 binary was missing.

I am not running a bzip2 binary, tar can also extract bzip2. Please read over the commands more carefully.

Yeah man, so do I. But the tar binary seems to have a dependency on bzip2. Without it I get the following error:
tar (child): bzip2: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

Weird, my image is based on Ubuntu and it does not require it. Must be
different then.
On Feb 14, 2016 02:31, "pFriesch"<EMAIL_ADDRESS>wrote:

Yeah man, so do I. But the tar binary seems to have a dependency on bzip2.
Without it I get the following error:
tar (child): bzip2: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
—
Reply to this email directly or view it on GitHub
https://github.com/andreasheil/docker-teamspeak3/pull/2#issuecomment-183790094
.

bzip2 added.


Adopt new context tracking sysyem

Hi! I'm using this extension is a couple of Flask projects and a Quart one. When trying to migrate the Quart app to it's latest version, the extension stopped working with the flask_patch:
ImportError: cannot import name '_app_ctx_stack' from 'quart.flask_patch'
According to what I understand from this answer, _app_ctx_stack will soon no longer be available in Flask either.
According to Quart's changelog:

Remove usage of LocalStacks, using ContextVars more directly. This
should improve performance, but introduces backwards
incompatibility. _*_ctx_stack globals are removed, use *_context
instead. Extensions should store on g as appropriate.

Are there any plans on making the appropiate changes on this extension to support this newer Quart release and Flask's future releases that drop _app_ctx_stack?
Thanks

Accessing the context will now also lead to a deprecation warning
venv/lib/python3.7/site-packages/flask_sqlalchemy/__init__.py:14: in <module>
    from flask import _app_ctx_stack, abort, current_app, request
venv/lib/python3.7/site-packages/flask/__init__.py:56: in __getattr__
    stacklevel=2,
E   DeprecationWarning: '_app_ctx_stack' is deprecated and will be removed in Flask 2.3

Fixed in #1087. Using db.session or db.engine now always requires an active Flask application context. The session is scoped to the current context, which ensures it is always cleaned up.

Still doesn't seem to be working with Quart using the latest 3.0.0a2 version.
Traceback (most recent call last):
  File "c:\Code\proj\run.py", line 14, in <module>
    from flask_sqlalchemy import SQLAlchemy
  File "c:\Code\proj\env\lib\site-packages\flask_sqlalchemy\__init__.py", line 5, in <module>
    from .extension import SQLAlchemy
  File "c:\Code\proj\env\lib\site-packages\flask_sqlalchemy\extension.py", line 23, in <module>
    from .session import _app_ctx_id
  File "c:\Code\proj\env\lib\site-packages\flask_sqlalchemy\session.py", line 8, in <module>
    from flask.globals import app_ctx
ImportError: cannot import name 'app_ctx' from 'quart.flask_patch.globals' (c:\Code\proj\env\lib\site-packages\quart\flask_patch\globals.py)

Chech the traceback, that's an issue with Quart (which I think is also fixed).

This is also the latest version of Quart so its not fixed quite yet, and looks like it might not get fixed at all based on this comment https://github.com/pallets/quart/issues/156#issuecomment-1179691917 about flask-patching possibly being removed from Quart in the future.
Regardless, I understand this is a Quart issue and not a Flask-SQLAlchemy issue. I just wanted to share that this isn't working with Quart currently. Thanks.

Chech the traceback, that's an issue with Quart (which I think is also fixed). Regardless, this is Flask-SQLAlchemy, we don't provide direct compatibility with Quart.

Although I understand direct compatibility with Quart isn't provided, wouldn't importing app_ctx be incompatible when Flask 2.3 is out?

Quart 0.18.3 should fix the app_ctx issue.


Add documentation

Purpose
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the changelog
[ ] Added tests
[x] Updated the spec
[ ] Checked native-image compatibility

@NipunaRanasinghe  need review.


Production stacktraces don't reference the app bundle

Environment
Environment:

OS:  macOS High Sierra 10.13.6
Node:  10.9.0
Yarn:  1.9.4
npm:  6.4.1
Watchman:  4.9.0
Xcode:  Xcode 9.4.1 Build version 9F2000
Android Studio:  Not Found

Packages: (wanted => installed)

react: ^16.4.2 => 16.4.2
react-dom: ^16.4.2 => 16.4.2
react-scripts: 2.0.0-next.a671462c => 2.0.0-next.a671462c

The problem
I was debugging a problem in my React app that only occurred in production. When I clicked a button, instead of a popover appearing, the entire app crashed. Oh no!
The stack trace that got dumped to the console didn't give any helpful information as to where the problem occurred, other than obfuscated React function names:
vendors.dc5479cc.chunk.js:1 Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at e.exports (vendors.dc5479cc.chunk.js:1)
    at p (vendors.dc5479cc.chunk.js:1)
    at Lc (vendors.dc5479cc.chunk.js:1)
    at f (vendors.dc5479cc.chunk.js:1)
    at m (vendors.dc5479cc.chunk.js:1)
    at vendors.dc5479cc.chunk.js:1
    at To (vendors.dc5479cc.chunk.js:1)
    at Oo (vendors.dc5479cc.chunk.js:1)
    at Po (vendors.dc5479cc.chunk.js:1)
    at mi (vendors.dc5479cc.chunk.js:1)

These are very cryptic, and didn't help me in my bug hunting endeavors.
I eventually figured out that a certain component that I was using was turning into undefined due to the minifier. Why? Well, the component tree looked like this:
<Menu>
  <Menu.Item icon="trash">
    Delete
  </Menu.Item>
</Menu>

This worked fine in development, as no names were changed. However, I can only assume that the minifier mangled the Item property on the Menu component, causing it to become inaccessible in production.
This fixed the problem, as expected:
import { Menu, MenuItem } from "@stuff/ui-framework"

<Menu>
  <MenuItem>
  ...
...

I was relieved, but shouldn't stacktraces emitted in production environments point to the actual application bundle itself? 🤔 Or am I missing something here?

No, the stack trace in the console is not automatically mapped back to the application bundle. You need to use a tool to perform this mapping for you.
However, this situation smells of a bug because the minifier shouldn't of minified Item. Can you please provide a small project that reproduces this bug?

I tried creating a small project to reproduce the problem, but I couldn't. The problem is probably from the UI framework that I am using.


Thread support tickets feature

Describe the feature you'd like
Add command to make embed with button in some channel, then when users click on the button, a thread will be created for them. It could be good for support tickets and threads can see also other users, so for public support channels, it will be great to have it more organized.
Allow one user to have just one thread open at the time, threads should be named in username-usertag or userid format.
When a thread is opened by the bot, add there the user and send embed with a button to close it as first message. Then when staff clicks on this button, thread should be archived. Also owner of the thread (user) should be able to close it. when it's resolved.
Maybe there should be also option to add some pre-made questions that users can pick a question from menu or open a ticket.
Example:

Its from suggester support server - https://suggester.js.org/support

Hello and thanks for the feedback! The idea is really cool and I'm sure it would be helpful for a lot of servers. However, a core principle of thread-watcher is that it is basic and easy to use. Thread watcher really only exists to keep threads unarchived not to do anything else
I really do appreciate the idea but for the time being I'll have to pass on it

Can you make a different bot for this instead?

I think that server owners will appreciate it, it should have commands for adding pre-defined questions to menu, then command for removing pre-defined questions, for adding more buttons to message (like Resources button) that will reply with custom message and command to send the panel.
Maybe it could be made to support just for one server (selfhostable) so it will be easier for you to make it, that the pre defined questions, embed and others settings could be edited in config.js file.


Extracted form has blank fields

When using the extract function the fields are empty. Here is what is seen when using import from options:
var rules = [{
  "url": "https://www.albiononline2d.com/en/tools/refining-profit-calculator/ore",
  "name": "A rule for https://www.albiononline2d.com/en/tools/refining-profit-calculator/ore",
  "fields": []
}];

This is the actual form as seen through Chrome Element Inspect:
<form class="form-inline ng-pristine ng-valid" _lpchecked="1">

Tax <input class="form-control form-control-sm" placeholder="Fee, %" value="25" id="fee">

Return rate <input class="form-control form-control-sm" placeholder="Return rate, %" value="15" id="return-rate">

</form>

There are multiple forms on this site and I am trying to fill in all of the text values for these fields:
Craft amount, Tax, Return rate, Master T4, Mastery T5, Mastery T6, Mastery T7, Mastery T8

Hi,
i learned something today. I previously assumed that the typeattribute is mandatory on input elements.
Well, it isn't and defaults to type="text" if not specified.
The extension currently only looks for input with a type attribute.
Nice catch!

Tested my changes and this looks much better:
 {
  "url": "https://www.albiononline2d.com/en/tools/refining-profit-calculator/ore",
  "name": "A rule for https://www.albiononline2d.com/en/tools/refining-profit-calculator/ore",
  "fields": [{
    "selector": "#spec-t4",
    "value": "0"
  }, {
    "selector": "#spec-t5",
    "value": "0"
  }, {
    "selector": "#spec-t6",
    "value": "0"
  }, {
    "selector": "#spec-t7",
    "value": "0"
  }, {
    "selector": "#spec-t8",
    "value": "0"
  }]
}

Will push the code soon.

Version 3.9.1 should be updateable in 60 minutes or so.

This is great, thank you so much @thenoseman - it works perfectly.


ssl connection error rate increases after #24923

Title: ssl connection error rate increases after #24923
Description:
Denote connection sr = ssl.connection_error/ssl.handshake
Our ingress hosts' sr are usually > 99%
During our recent deployment based on https://github.com/envoyproxy/envoy/commit/3f198ba35873bba736374ea568fcfa6c4d903215,  the sr dropped to < 95% for those ingress hosts without cdn in front.
sr recovers after we manually revert #24923
we did not flip enforce_rsa_key_usage

cc author @tyxia

Hi @JuniorHsu , as you can see, enforce_rsa_key_usage is not enabled in that PR, though adding stats counter was_key_usage_invalid to track the misuse key usage.
However, that PR also reports the error in failure reason for general SSL_ERROR_SYSCALL.
I am wondering what is the failure/error reason for the increased error rate you saw?

Hello @tyxia,
It's non immediately to tell the reason of increased error since the debug log is flooding.
I sample one host, connection error increased from 3 to 30 but there's 3.8k line said
TLS error:SSL_ERROR_SYSCALL error has occured, which indicates the operation failed externally to the library. This is typically |errno| but may be something custom if using a custom |BIO|. It may also be signaled if the transport returned EOF, in which case the operation's return value will be zero. Also 35k line like TLS error: 33554536:system library:OPENSSL_internal:Connection reset by peer but should be normal i guess.
(a) does it mean we have this issue before #24293? However your PR reports the issue?
(b) any suggestion to dig more?

I tweet some code to show log only in
https://github.com/tyxia/envoy/blob/1fc1f036e3b725d0b9a6f3c6ac3fe41314608e17/source/extensions/transport_sockets/tls/ssl_socket.cc#L250
most of the failure reason is
TLS error:SSL_ERROR_SYSCALL error has occured, which indicates the operation failed externally to the library. This is typically |errno| but may be something custom if using a custom |BIO|. It may also be signaled if the transport returned EOF, in which case the operation's return value will be zero.

< 10% is
TLS error: 268435613:SSL routines:OPENSSL_internal:INAPPROPRIATE_FALLBACK
and
TLS error: 268436502:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN

Yes. SSL_ERROR_SYSCALL is exact error that is added in https://github.com/envoyproxy/envoy/pull/24923.
Based on its comment and envoy behavior that it will result in PostIoAction::Close. I think it is real error/failure.
I would also add ssl expert @ggreenway and @davidben  here to shed more lights on this error.

I think the only change in that PR related to these errors is in reporting: https://github.com/envoyproxy/envoy/pull/24923/files#diff-1b6d3bf54cf9bad48dd67ac9d0f87897b0669000cd0076573c4d5396733ee4d2R101
The SSL_ERROR_SYSCALL case previously went to default, but that has the same set of actions, just slightly different error reporting. But in either case it should be reported as an error.

Thanks @tyxia and @ggreenway!
Looks like handshake error due to SSL_ERROR_SYSCALL is hidden until @tyxia's work.
Next step could be more informative log given errno doesn't give us anything here and we're using non-special amazon host.
Does envoy have utility to get BIO message as the comment suggests?

one more observation,
(ssl.handshakes + ssl.session_reuse)/ downstream_cx_total is very similar with or without the patch, which is good.
However, downstream_cx_destroy_local goes up with the pr, which surprises me.

one more observation,
(ssl.handshakes + ssl.session_reuse)/ downstream_cx_total is very similar with or without the patch, which is good.
However, downstream_cx_destroy_local goes up with the pr, which surprises me.

That surprises me too. How much does downstream_cx_destroy_local increase by, as a percentage of total connections?
@tyxia I wonder if we should revert that change until we can figure out why it's causing this?

That PR doesn't have functional change except error reporting for SSL_ERROR_SYSCALL.  For SSL_ERROR_SYSCALL case, the behavior has always been return PostIoAction::Close.
So technically it should not cause downstream_cx_destroy_local . I think it will be great that we can confirm it is caused by that PR first before reverting.  Also if we want to revert, I think we can just revert SSL_ERROR_SYSCALL part as enable_ras_key (which is not enabled) has been asked by ssl team for a quite while. I can take care of this revert but I would like to confirm the cause here first.

I agree that it doesn't look like the PR should cause this behavior change; I looked it over again. But I'm worried we're missing something.
@JuniorHsu can you provide more details about the setup in which you're seeing this behavior change? And any other details you can provide that might help prove or disprove that this change is causing it?

Let's talk about stats first.
while ssl.connection_error consistently get 700 more than other hosts, downstream_cx_destroy_local get +900 then other hosts.
As for the rate, while 1- ssl.connection_error/ssl.handshakes goes from 99%+ to 95%, 1-downstream_cx_destory_local/downstream_cx_total remains the same, although the rate is around 80% and fluctuate so hard to tell.
Therefore it's hard to judge for me
About the setup, that is the ingress cluster without CDN in front.
We revert to https://github.com/envoyproxy/envoy/commit/a0620080acf46534675bc6484c8127ff1c2d0898 + nghttp2 patch while we find stats regression on https://github.com/envoyproxy/envoy/commit/3f198ba35873bba736374ea568fcfa6c4d903215
Let me know if anything could help from our side

It's hard to make judgement since downstream_cx_destroy_local is fluctuated because of the traffic volume, probably idle timeout? The amplitude is 30% so hard to tell if the patch have impact if only revert one pr in single host since SSL_ERROR_SYSCALL only have 5% impact here.
The first time we deployed 1az of ingress hosts so the trend is easier to tell. There might be other factor like outlier detection or zone awareness yeah.
We could check tomorrow to see if we have more finding or way to tackle.

I think that 1-downstream_cx_destory_local/downstream_cx_total remains the same is a good signal. Let's focus on downstream_cx related stats and try to control the variables in the experiments if possible

@ggreenway  Sure I will reverted the part related to syscall errors logging.
syscall error hanlding is not core part of tjat PR. It was added to surface the error information for testing in that PR

For future reference, here are debug logs for this happening. This is a remote-close case: I was testing with curl, and I killed the curl mid-request.
[2023-08-28 15:25:07.823][734886][debug][conn_handler] [external/envoy/source/extensions/listener_managers/listener_manager/active_tcp_listener.cc:157] [Tags: "ConnectionId":"87"] new connection from <IP_ADDRESS>:41336
[2023-08-28 15:25:07.830][734886][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:247] [Tags: "ConnectionId":"87"] remote address:<IP_ADDRESS>:41336,TLS error:SSL_ERROR_SYSCALL error has occured, which indicates the operation failed externally to the library. This is typically |errno| but may be something custom if using a custom |BIO|. It may also be signaled if the transport returned EOF, in which case the operation's return value will be zero.
[2023-08-28 15:25:07.830][734886][debug][connection] [external/envoy/source/common/network/connection_impl.cc:250] [Tags: "ConnectionId":"87"] closing socket: 0
[2023-08-28 15:25:07.830][734886][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:247] [Tags: "ConnectionId":"87"] remote address:<IP_ADDRESS>:41336,TLS error:SSL_ERROR_SYSCALL error has occured, which indicates the operation failed externally to the library. This is typically |errno| but may be something custom if using a custom |BIO|. It may also be signaled if the transport returned EOF, in which case the operation's return value will be zero.
[2023-08-28 15:25:07.830][734886][debug][conn_handler] [external/envoy/source/extensions/listener_managers/listener_manager/active_stream_listener_base.cc:121] [Tags: "ConnectionId":"87"] adding to cleanup list

This condition is counted in remote_close stats.


[DISCUSS] Black and iSort as pre-commit steps

We haven't talked about doing anything around approved steps.
I would like to standardize on using black with the isort profile for imports.

Always in favor of autoformatting, etc. Created a first pass at #52.


Add bonus question to step 5

Coverage remained the same at 32.911% when pulling a2c84e33fb41267e92b0488ccd0e66deb91f46dc on step-5-bonus-question into 23ad008132cd6320125453087d4157bc6f96a31a on master.

Coverage remained the same at 32.911% when pulling c9c4d32e1b79883cb9d2fb3d9e612f592757a5d6 on step-5-bonus-question into 23ad008132cd6320125453087d4157bc6f96a31a on master.


config: fix unnecessary log lines on remote close

Signed-off-by: Rama<EMAIL_ADDRESS>Description:
only call setRetryTimer instead of handleFailure on remote close
Risk Level: Low
Testing: Automated tests
Docs Changes: NA
Release Notes: NA
Fixes https://github.com/envoyproxy/envoy/issues/3024

@mattklein123 The case I am concerned about is any disconnection from management server (graceful/network disconnects), along with the log line
source/common/config/grpc_mux_impl.cc:205] gRPC config stream closed: 1,
there are bunch of config update failure log lines are coming and they keep repeating till the connection succeeds again. I  think the config update log lines are misleading because there is actually "no" update management server has send and envoy failed to update. It just that there is a disconnect between envoy and management server. So the "gRPC config stream closed" log line is sufficient.
And from stats perspective, the update_failure stat is incremented here which I think is misleading again. This change handles both.

@htuch  I think we are not silently ignoring the fact that we are unable to speak to the management server.
From logging perspective, we are still logging the following log line which would indicate the connection failure
[2018-04-21 17:29:40.765][7315769][warning][upstream] source/common/config/grpc_mux_impl.cc:217] gRPC config stream closed: 1,
And from stats perspective, the following stats (specially the first one) similar to what you are thinking about update_unreachable will indicate the connection failures.
cluster.xds_cluster.upstream_cx_connect_fail: 88
cluster.xds_cluster.internal.upstream_rq_503: 88
cluster.xds_cluster.internal.upstream_rq_5xx: 88

I do think that the update_xxx stats should really be used when there is a "real" issue with update then we can create alerts on them. This fix will enable that.

@ramaraochavali For a lot of Envoy users (including us at Google), having stale configuration due to an unreachable management server is pretty serious; it's definitely a "real" issue, i.e. it's not a benign event. I agree that the existing stats/logging are a bit misleading and can be improved. I also agree that there is some existing signal as you point out in your last comment. I think this might be enough, but can you also update operations and stats docs to clearly spell out to users what happens when a management server becomes unreachable and how this can be detected?

@htuch sure. Will update that. I agree working with stale  config is a "real" issue - even for us, the point I am trying to make there is, the update failure stats should be used only to indicate that a management server has sent an update to envoy, envoy received it and it failed to update because the update content is invalid. Only trying to say connection related issues should not be seen as data update failures. That is little confusing to me. But any way, I will see how can I can put that information in operations doc and update the PR.

@htuch  I tried to see where I can update this information. But could find any appropriate doc where such information is documented. Can you suggest me to the best place to document?

Clarify update_failure semantics at https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#config-cluster-manager-cluster-stats.
Discuss management server unreachability at https://www.envoyproxy.io/docs/envoy/latest/configuration/overview/v2_overview.html (e.g. latch last configuration, what happens with logs/stats, what the retry behavior is).

@htuch Added the docs, PTAL .

@htuch changed. PTAL.


Character glitch

Screencast from 2024-03-25 14-42-46.webm
This happens sometimes after Cody has finished outputting its answer. It doesn't seem to impede use, it's just weird. I tried and failed to find a log output I could share. Any ideas there?
I'm using the latest commit as of writing: https://github.com/sourcegraph/sg.nvim/commit/8d7735bfb810d919806da1e1c4f839fbc6ecccfe

I think it's by design, probably coz it's cool.

Could be, but it breaks text selection.

I think I've fixed this (at least on nvim 0.10 and latest plugin). I'm going to close, but if you see it again, please make an issue and I'll try to reproduce again (was able to reproduce locally but think latest fixes this).
Thanks for reporting!


Specifying default value for Kedge variable

Allow specifying a default value for a variable if it is not set.
example kedge file:
name: foo
image: foo/bar:[[ TAG:latest ]]

If TAG variable is not set, it latest will be used.
The rule for detecting default value should be: use everything between : and ]] and trim whitespaces from both ends.

I will pick this up


Adding Windows Service release folder into artifacts folder

I am trying to add windows service release folder into artifacts folder but I want to add under a certain folder like service name folder inside artifacts. Currently, I tried to copy files task but it adds just a bin folder inside artifacts for a service

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

ID: 81f02378-b85b-d3a4-d3c8-f07d935367da
Version Independent ID: fab57f76-35d2-4024-6f7f-1740d7b24743
Content: Copy Files
Content Source: docs/pipelines/tasks/utility/copy-files.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

You need to use the Publish Artifacts task, not Copy Files:
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/publish-build-artifacts?view=azure-devops


I am Using Nox emuletor your project not detect it

I am Using Nox emuletor your project not detect it

Run the following command: adb connect <IP_ADDRESS>:62001
Then run the tool

Closing


Team 04 - VnV Plan Review - NFRT Security Requirements

Great work on the entire document!
I believe it is also important to add a test for the security requirements that will ensure that a user is not able to hack the application. This was also mentioned as a potential hazard I believe in your HA.
I think testing to ensure that a user gets locked out of the system after X number of incorrect password attempts can be added as a test. This might even pertain to your User Authentication functional tests.
@samm82

Hack is too vague, there currently exists tests for unauthorized accessed.
Unsure about what the purpose of a lockout system would achieve, not a documented requirement.


mode as 'mix' not working

{
mode: 'mix',
pattern: /@|#|~|%|&|-/
}
tags.find is not a function
https://github.com/Brakebein/ngx-tagify/blob/b8e60313ae045eaa6e0c6e22e90f32008a991ede/projects/ngx-tagify/src/lib/tagify.component.ts#L96

Sorry, I have to admit that haven't really tested the mixed mode. I will fix it within the next days.

@rynangeles Can you please provide some more information and/or code snippets how you use it exactly? I can't reproduce your error.
I'm just adding support to load some initial mixed text & tags string.

I'm using the reactive form and my value is a string. so for example the value is 'the quick brown fox. {{{this_is_a_tag}}}' {{{}}} as my interpolator and the  tags which I guess is the value from a reactive form field. If value/tags is a string, then definitely  String.find() method will throw an error.

You may checkout the newest version. An initial string is now accepted with ngModel or reactive forms. But keep in mind that it gets parsed and transformed to tags. So, the initial string will be replaced by an array of tags.
Alternatively, you can pass a predefined value between the element tags: <tagify>tag 1, tag 2</tagify>. See readme and demo for details.

I think it would be better if the mode : mix preserve that string as its value.

You mean if the initial string value is {{{this_is_a_tag}}} some text {{{tag}}}, then you add more text and an additional tag, the string returned should be  {{{this_is_a_tag}}} some text {{{tag}}} more text {{{additional tag}}} ?
I thought of it as well, but I maybe overlooked some of docs:
https://github.com/yairEO/tagify#output-value
I also just looked deeper in the code and found this:
https://github.com/yairEO/tagify/blob/master/src/tagify.js#L1480-L1539
So, it should be possible. I will go for it within the next days.

In the newest version, the output type now corresponds with the input type, i.e. either string or TagData[].
However, for mode: 'mix', if the input value is, e.g., [[cartman]] and [[kyle]], the output string will be [[{"value":"cartman"}]] and [[{"value:"kyle"}]]. If you only want the pure value within the tag interpolators without the JSON syntax, you may need to address this issue to the core library. There should be some user-defined method similar to originalInputValueFormat to define the output format for tags and called within the getMixedTagsAsString() method.
https://github.com/yairEO/tagify/blob/master/src/tagify.js#L1480-L1539


temp: Perf test buildah with emptyDir medium: Memory

Do not merge, just for perf test

ok @jhutar @psturc let's see if this hits the unshare issue

Unfortunately we have the unshare problem here as well @jhutar @psturc
      COMMIT quay.io/redhat-user-workloads/build-templates-e2e/test-app-514/pip-e2e-test-mpqd:build-a8a2f-1693916765
      unshare: sigprocmask unblock failed: Invalid argument

switching to emptydir is causing an hiccup with this cachito / pip build

fyi bumping the build steps memory limit to 5Gi allowed the e2e's to pass over in https://github.com/redhat-appstudio/build-definitions/pull/551
hopefully we can get that merged after sufficient verification in staging and we can just close this out as superseded by https://github.com/redhat-appstudio/build-definitions/pull/551

https://github.com/redhat-appstudio/build-definitions/pull/551 is more complete now I think.


pr2_navigation_apps: 1.0.2-1 in 'hydro/distribution.yaml' [bloom]

Increasing version of package(s) in repository pr2_navigation_apps to 1.0.2-1:

upstream repository: https://github.com/PR2/pr2_navigation_apps.git
release repository: https://github.com/TheDash/pr2_navigation_apps-release.git
distro file: hydro/distribution.yaml
bloom version: 0.5.20
previous version for package: 1.0.2-0

pr2_2dnav
* Updated pr2_2dnav to install launch files and remove unecessary rosbuild files
* Contributors: TheDash

pr2_2dnav_local
* Removed rosbuild files, added install for launch files
* Contributors: TheDash

pr2_2dnav_slam
* Removed rosbuild files, added install for launch files
* Contributors: TheDash

pr2_navigation_apps

No changes

Hey Tully, about this package:
V1.0.1 is on the packages.ros.org repo, but V1.0.2 is building successfully on the buildfarm. Was something missed in a sync?
http://www.ros.org/debbuild/hydro.html
http://packages.ros.org/ros/ubuntu/pool/main/r/ros-hydro-pr2-navigation-apps/

We haven't synced hydro in a while. It's still in the testing repository. We currently have a regression on the rosjava builds: http://lists.ros.org/pipermail/ros-release/2015-May/004632.html

Thanks for the details. Is there a planned Hydro sync soon or are we done for Hydro?

Yes we'll get at least one more out.


pretraining hyper-parameters for tiered imagenet

I went through all the issue posts but didn't find the pretraining hyper-parameters for tiered imagenet. I can only find mini-imagenet's. Could you also release them for tiered imagenet?
Thanks!

Hi,
I use the following command to pretrain on the tieredimagenet:
../../anaconda3/bin/python3.7 pretrain.py --lr 0.1 --batch_size 128 --max_epoch 600 --backbone_class Res12 --schedule 400 500 550 580 --ngpu 1 --gamma 0.1 --dataset TieredImagenet --query 10


Fail to auto create through model for ForwardRef reference in ManyToMany relation

Thanks, the "CityRef" was working fine as a type hint, it seemed to just be the M2M relationship for borders. I still went ahead with removing my type hints for the ForwardRefs ( I'm using Python 3.9.5) and i'm still getting the same error message.
Any ideas?
Thanks again
Model changes I made:
class Country(ormar.Model):
... excluded for brevity
    capital = ormar.ForeignKey(CityRef, related_name="capital_city", nullable=True)
    borders = ormar.ManyToMany(CountryRef)

Stack trace on app boot:
File "./app/db/models.py", line 21, in <module>
    class Country(ormar.Model):
  File "/home/josushiman/.local/share/virtualenvs/travl-info-api-cb_AeNoS/lib/python3.9/site-packages/ormar/models/metaclass.py", line 579, in __new__
    new_model = populate_meta_tablename_columns_and_pk(name, new_model)
  File "/home/josushiman/.local/share/virtualenvs/travl-info-api-cb_AeNoS/lib/python3.9/site-packages/ormar/models/helpers/sqlalchemy.py", line 251, in populate_meta_tablename_columns_and_pk
    pkname, columns = sqlalchemy_columns_from_model_fields(
  File "/home/josushiman/.local/share/virtualenvs/travl-info-api-cb_AeNoS/lib/python3.9/site-packages/ormar/models/helpers/sqlalchemy.py", line 158, in sqlalchemy_columns_from_model_fields
    return _process_fields(model_fields=model_fields, new_model=new_model)
  File "/home/josushiman/.local/share/virtualenvs/travl-info-api-cb_AeNoS/lib/python3.9/site-packages/ormar/models/helpers/sqlalchemy.py", line 190, in _process_fields
    field.create_default_through_model()
  File "/home/josushiman/.local/share/virtualenvs/travl-info-api-cb_AeNoS/lib/python3.9/site-packages/ormar/fields/many_to_many.py", line 265, in create_default_through_model
    to_name = self.to.get_name(lower=False)
AttributeError: 'ForwardRef' object has no attribute 'get_name'

Originally posted by @josushiman in https://github.com/collerek/ormar/discussions/220#discussioncomment-823434

Fixed in 0.10.11 (#228)


Update MainActivity.java

magic!

You have moved the following from MainActivity to Application class. This is not good for a library to be dependent on the App, because the library is a module and you generally have no control over the app.
Your implementation is not incorrect and perhaps preferred in some circumstances, but handling the initialization to the Application layer is not a good practice in writing libraries.


accept Client Certificate for New-SSHSession

Allow a client certificate to be used to logon .

Library only allows for SSH keys.
Sent from my iPhone

On Aug 21, 2016, at 8:06 AM, theking2<EMAIL_ADDRESS>wrote:
Allow a client certificate to be used to logon .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

thanks.
What is SSH keys?

https://help.ubuntu.com/community/SSH/OpenSSH/Keys
Sent from my iPhone

On Aug 21, 2016, at 2:21 PM, theking2<EMAIL_ADDRESS>wrote:
thanks.
What is SSH keys?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

got it


Flutter Called setState and rebuilt, but the UI has not changed?

This is probably my own problem, but I don't know what caused it , how to solve it.
example: Clicking on the blue circle button, clicking on it will add a tabitem, but now clicking it will not respond.
online code:
https://dartpad.dev/52167cf8e29e20552cbb20385afc5f83

Hi @Aaron009
This platform is not meant for assistance on personal code.
I may suggest to avoid use business logic inside your widget's build function
and you may consider using some form of state management
like InheritedWidget or some of the excellent
3rd party solutions available like provider or bloc.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


improve alignment of Blog search clear button

Describe the bug
improve alignment of Blog search clear button

Screenshort

Hey @shivam-sharma7 you can work in this.

I would like to work on this issue, looking forward for your response.

I would like to work on this issue pls assign this to me


Description is not required for work

We need to review the required metadata fields with the libraries.  Description used to be required for a File.  I'm guessing it should still be required for a work.

We will also need Resource Type to be move up since we are keying off of that for sending information to Share Notify.

Should be as easy as just overriding the form and adding the fields to the required array.

Any item required for Google Scholar should be a required item.

PSUSprint03


Feature: WRITE_KZG_COMMITMENT hint

This implementation uses a default (panicking) implementation of the KZG
commitment computation as we do not know how these must be computed.
Issue Number: N/A
Type

[x] feature
[ ] bugfix
[ ] dev (no functional changes, no API changes)
[ ] fmt (formatting, renaming)
[ ] build
[ ] docs
[ ] testing

Description
Breaking changes?

[ ] yes
[x] no

Superseded by #304.


:construction: Collapse all days into one when guessing

Eugene, please, add description or link to something in the PR.
How about, instead of completely discarding the day of the week, we give different weights for those two things?. Example: If the hour matches it weights whatever for the smart guess match, but if the day of the week also matches then it weights more.

@Odrakir what do you think about this simple approach where i give importance if they are from the same group (weekdays, weekends)? if none is available from the same group the slot from the other group will still matter as they do now.

Is there an issue for this? Is it a bug fix or a change of behaviour? If the latter, what is the reasoning?


added support for query string fields on issues

With Jira v7.2.0 (this issue), you now have the ability to decide whether or not to notify users when you edit an issue through the api. To use this feature, a request needs to be made similar to the following:
http://jrl2014s:8080/rest/api/2/issue/TEST-9?notifyUsers=false
To resolve this, we need to pass in a value to the qs parameter of the buildRequestOptions function. This allows us to make api calls like so:
jira.issue.editIssue({issue: {update: {labels: [{add: 'blocked'}]}}, qs: { notifyUsers: false }, issueKey: 'TEST-9'})

Looks good; will try to publish a new version sometime this week.


three.js: ERROR: too many uniforms

Describe the bug
ERROR: too many uniforms.
Amethyst Details (required):

https://github.com/Geoxor/Amethyst/commit/3848fc78a26ad1fd029822fe8694b10de0c68f41 (v1.8.38)
MacOS dev build

No idea how I triggered that.
Will look into it.

#575 should fix this issue


Add login link on signup page

Update the sign up page by adding link to render again on login if already account was created.

@ankitgupta143 Please the mention the issue number on which this PR has been raised

@VanshKing30 Issue number of PR is 72

Great Work !!

Good Work Mate !!

@VanshKing30 Thanku for your support


REQUEST_URI instead of PATH_INFO

              environ.get('PATH_INFO', ''),
should use REQUEST_URI.

path_info does not include the query string, which is normally included in NCSA logs like apache
applications like werkzeug.wsgi.DispatcherMiddleware modify PATH_INFO and will lead to wrong logged values

Bump! Would love to see this fixed for: https://github.com/Miserlou/Zappa/issues/1048


Show status information in stages when stage is empty (no service deployed)

In case a user has created a project (+ onboarded a service), but not yet deployed an artifact, the stages are empty and might cause doubt.

To inform the user about the current status and to provide help, two info messages are required as shown in the definition of done.
Definition of Done:
If no deployment.finished event has been received for a stage,

[ ] show an info message on the stage.
[ ] provide a help message with a link to the keptn send new-artifact command (see details page on the right)

If there is no services onboarded yet, I show a different message with a link to instructions "how to onboard a service". This message is displayed in the "services" and in the "environment" tab. See images below.

When there is a service onboarded, but no deployment available yet on that stage, then I show the instructions how to deploy a service using "keptn send new-artifact".


Use Enums for subcommands

See https://dev.to/64bit/ideas-for-crafting-cli-in-rust-5b0d

Didn't like going in this direction