Can't destroy dinghy VM

Just tried destroying my dinghy VM and it failed in a couple ways:

If the VM is stopped, running dinghy destroy fails with:

$ dinghy destroy
Stopping the FsEvents daemon
Stopping the dinghy VM...
Machine "dinghy" is already stopped.
/usr/local/Cellar/dinghy/HEAD-b584148/cli/dinghy/system.rb:11:in `system': Failure calling `docker-machine stop dinghy` (System::Failure)
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/dinghy/machine.rb:126:in `system'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/dinghy/machine.rb:106:in `halt'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/cli.rb:124:in `halt'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/cli.rb:143:in `destroy'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/thor/lib/thor/command.rb:27:in `run'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/thor/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/thor/lib/thor.rb:359:in `dispatch'
	from /usr/local/Cellar/dinghy/HEAD-b584148/cli/thor/lib/thor/base.rb:440:in `start'
	from /usr/local/bin/_dinghy_command:12:in `<main>'

If dinghy is running, dinghy destroy successfully stops the VM, but then quietly exits without deleting the image.

$ dinghy destroy
Stopping the FsEvents daemon
Stopping the dinghy VM...
Stopping NFS daemon, this will require sudo
$ docker-machine ls
NAME     ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER    ERRORS
dinghy   -        virtualbox   Stopped                 Unknown

In order to work around the problem, we used docker-machine rm dinghy.

Note that I'm up to date with the latest home-brew packages. e.g. Dinghy 4.4.2

I'm unable to reproduce either scenario in Dinghy 4.4.2, but I can reproduce on the latest master -- did you brew install --HEAD dinghy at some point by chance? I should set that up to report a different version number.
I'll look into why this is happening on master, there's only been a couple commits so I'm sure it's related to my error reporting modifications.

OK this is fixed on master, and I've modified the homebrew tap to give dinghy version a better version identifier when installing from HEAD rather than using the last release version.


Missing space in query

When using aliases in some cases the generated sql query is not valid because of a missing space.
Example:
data.select(Person.LAST_NAME).from(data.select(Person.LAST_NAME).as("l_name")) .groupBy(Person.LAST_NAME)
Well, this is a somewhat hypothetical example but it will result in this sql query:
select lastname from (select lastname from Person) l_namegroup by lastname
You can avoid that by adding a trailing white space to the alias but it's still a bug I think. ;-)

Thanks for reporting! yup definitely a bug


TextEdit: Change margin property to egui::Margin type

Despite their being an actual egui::Margin struct, Textedit has a margin() builder function that supports only Vec2 types and thereby only symmetric margins. This PR changes the function to accept egui::Margin type instead making it more congruent with overall egui logic as well as supporting asymmetric margins.
P.S: I tried to run all checks but I had to modify ./rust-toolchain to 1.67.0 to get the checks to run on macOS.

The code doesn't compile yet :)


the results is not reproducible

the results is not reproducible due to some random factors, is there a way to reproduce the exactly same result in NN training

Please re-ask this question on stackoverflow. Issues are primarily for bugs.

For people who come here:
import numpy as np
np.random.seed(0)  # make sure results are reproducible
import tensorflow as tf
tf.set_random_seed(0)  # make sure results are reproducible

The numpy part might not be necessary in your case.


status_server: add glibc, pthread, libgcc to the blocklist (#11205)

close #11108
Signed-off-by: YangKeao<EMAIL_ADDRESS>What problem does this PR solve?
close #11108
Problem Summary:
If the pprof-rs sample arrives and the current program is fetching a backtrace, the program will panic. The reason is that there is a lock inside the dl_iterate_phdr, which is called while unwinding the backtrace.
A more detailed description about this problem can be found in https://github.com/tikv/pprof-rs/pull/85#issuecomment-954446008 . In tikv, when an Error is generated, it's likely to get a backtrace and cause this problem.
After adding these libraries to the blocklist, it will also be able to turn on the heap profiling and pprof-rs cpu profiling at the same time, but I haven't modified (and tested) it yet.
What is changed and how it works?
What's Changed:
Skip all samples inside the glibc, pthread and libgcc.
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Side effects
The sample in the libc, libgcc and pthread will not be collected in the profiling result.
Release note
status_server: skip profiling sample in glibc, pthread, libgcc to avoid possible deadlock
status_server: upgrade pprof-rs to fix memory leak

/cc @sticnarf
/cc @BusyJay

/merge

/merge


changing tabstop has no effect

in my .vimrc.local
set shiftwidth=3
set tabstop=3
set softtabstop=3
But when I hit tab, it still uses 4 spaces.  The values are set, and set tabstop reports 3 but something else must be overriding it.

+1 This has been bugging me for like, a year! I am so happy now!

And 2 years later, hit this again, and found myself in the list of people who hit this. Amazing.

+1 again, I guess? Two years later this bit me again... ToT;


Scoped style does not work with multi-root child components

Version
3.2.31
Reproduction link
sfc.vuejs.org/
Steps to reproduce
See preview here: sfc.vuejs.org/

What is expected?
First 3 divs should have blue border
What is actually happening?
Only first div has blue border

It's by design, in my view.
The scoped data property is only inherited onto single root nodes because the intended use case is to add layout styles for that root node.
That doesn't make too much sense for a multi-root component.l, and could in fact have unintended side effects when the number of root nodes changes during the lifecycle of the child component.
So for multi-root components, the right approach would be to add a wrapper element in the parent for layouting purposes.
Provided that @yyx990803 confirms this I'd say we should make the docs more explicit about this.

That doesn't make too much sense for a multi-root component

The sense is that multiple root elements may use classes:

And I may need to apply styles to these classes.
But I can't achieve this neither with :deep pseudo class nor without it:

Adding or not adding v-bind="$attrs" also does not help:

Here is an updated example:
sfc.vuejs.org
I have very simple need.
I need to add blue border to each section in a component that needs to be multi-root.
How can I do this?
I think this is very simple task that I should be able to acomplish with flexible framework.

The sense is that multiple root elements may use classes:

Our perspective is that it's not a good idea to break separation of concerns/responsibilities in this way, so we don't go out of our way to support it.

But I can't achieve this neither with :deep pseudo class nor without it:

Yes, :deep doesn't work either in your specific example because it would need one element at least in the parent wrapping the children:
working with a root element in App.vue

How can I do this?

in this specific scenario where the parent has no elements of its own around Child, and Child has multiple roots:
a) Use a non-scoped style
b) use css modules instead of scoped:

<template>
  <Comp class="$styles.section" style="background: yellow;" />

  <Comp2 class="$styles.section" style="background: yellow;"  />
</template>

@LinusBorg from the comments is a bit unclear if you answered or understood this issue with multi-root components so I am going to give it a try to ask again because in my view this is a bug.
Component with multi-root nodes cannot be styled from parent with :deep() selector
See the demo on Stackblitz
If we have a HelloWorld.vue component with this code:
<template>

Hi

Hey

</template>

Then from the parent component, we can't style it within scoped style with :deep() selector nor with by accessing a class we add in the parent:

<template>

  <HelloWorld class="hello" />
</template>

So as you can see above, none of the 3 ways works to style the elements of the child component.
This fails only when mutli-root nodes are used in the child component.
Trying to understand your answers
Maybe there is something that I am missing here but how can this behavior be by design? Since multi-root components are supported, why do we have to wrap child components in order to enable :deep() styling?

There's a difference between a bug and a limitation of a design/solution/feature, wether that limitation is technical or intentional.
:deep()
:deep(.some-class-name) was explicitly designed to produce a selector like: [data-v-3478937439] .some-class-name.
That means, this design requires that the child component that you want to have the deep styles bleed into needs to be wrapped in one element in the parent which can carry the data-v-3478937439 attribute. That's how this feature works. Thats the design.
The fact that you can't use it in the specific way you want it to does not make it a bug. It makes it a feature that has a limitation falling short of your desired behavior. If you can come up with a feature proposal of how we can make scoped deep styles work without the requirement of such a wrapper component - feel free to open an RFC.
Also, I gave you a working solution which uses module instead of scoped. CSS modules work differently and thus can make it happen, but have different trade-offs.
multiple root nodes.
Back in Vue 2, root nodes were required, and the fact that scoped styles could bleed onto the root node was a double-edged sword:

It allowed for an escape hedge when one needs to layout a component without a wrapper element.
But it also meant that style encapsulation of scoped styles was leaky, and not 100% reliable. You can have class name collisions with this on root elements. People were and are bitten by this quite regularly.

During development and RFC phases of Vue 3, we considered removing this behavior completely because of 2., but left it in for single-root-components for two reasons:

Allow for easier migration: We don't force people migrating to re-organize for wrapper-elements in multiple places.
Point 1. above does have it's merits, especially when it's about layouting a child in relation to the parent - which also doesn't really affect multi-root components as layouting usually is done on wrapper elements.

Now, was this decision perfect? Certainly not, it has trade-offs. Does this mean it's a bug? Absolutely not. But does this mean that there are edge cases where this design is giving users a hard time? absolutely.
Can we change it without a major release? No.

@LinusBorg thank you for the detailed explanation. Make sense to me now why this is a limitation. Have a nice weekend

I believe a parent component (P) should be able to consume a child component (C) without knowing if C is a single or multi-root component.
If, in component P, we set some CSS class for C, the styles tied to that class should fall through C no matter the root configuration. In my opinion, That API is consolidated in the VUE design and should not be broken for multi-root components.
That fallthrough behavior is a decision for C to control. If it is a simple single root element already settled and working, in the other case of C being a multi-root component, the v-bind="$attrs" would guide the entire fallthrough behavior, including classes and styles coming from the parent.
That makes de API predictable. Someone read this doc and goes one applying v-bind=$attrs as a way to signal which of the root nodes is the nominal parent.
It is not my intention to trash the framework design. I love VUE and use it daily.  I also acknowledge that it is common for technical challenges to limit capabilities. That said, if this behavior is permanent, I think it should be declared as a limitation in the fallthrough docs and/or here


Change FitAction behavior in silx view and Plot1D

This PR proposes to change the behavior of the FitAction in Plot1D and silx view to use the behaviour of live update introduced in PR #2960.
It also proposes to keep the FitWidget always on top (only when started from the FitAction), related to #2935.

I think it is better. But Dialog should be used instead of WindowStaysOnTopHint.

You're right, it changed it.

I think this behavior is better


buildkite-agent annotate takes an arguments argument that is never explained

Hey @nickatsegment that arguments argument is actually a shorthand for all of the optional arguments, but I can see how that might not be clear.
I've seen [option], [OPTION...] and even [OPTION]... used elsewhere. Could you raise an issue over in https://github.com/buildkite/agent/ if you think it warrants it.

Yeah, looks a little inconsistent over there. I'll open an issue.


livescript ast doesn't store full information about code

Hi. I found that AST doesn't store the information about PIPING so it is not possible to convert back from ast to livescript code without loosing of quality of the code
"" |> convert 2

will be
convert 2,""

but it is not possible to understand is convert function carried or not.

Right, that's why it's an abstract syntax tree, instead of a concrete one :).

(In general, this is not feasible for us to expose, due to how much rewrites the lexer does)


[Snyk] Upgrade commander from 11.0.0 to 12.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade commander from 11.0.0 to 12.0.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 4 versions ahead of your current version.
The recommended version was released a month ago, on 2024-02-03.

Release notes

Package name: commander

12.0.0 - 2024-02-03Added

.addHelpOption() as another way of configuring built-in help option (#2006)
.helpCommand() for configuring built-in help command (#2087)

Fixed

Breaking: use non-zero exit code when spawned executable subcommand terminates due to a signal (#2023)
Breaking: check passThroughOptions constraints when using .addCommand and throw if parent command does not have .enablePositionalOptions() enabled (#1937)

Changed

Breaking: Commander 12 requires Node.js v18 or higher (#2027)
Breaking: throw an error if add an option with a flag which is already in use (#2055)
Breaking: throw an error if add a command with name or alias which is already in use (#2059)
Breaking: throw error when calling .storeOptionsAsProperties() after setting an option value (#1928)
replace non-standard JSDoc of @ api private with documented @ private (#1949)
.addHelpCommand() now takes a Command (passing string or boolean still works as before but deprecated) (#2087)
refactor internal implementation of built-in help option (#2006)
refactor internal implementation of built-in help command (#2087)

Deprecated

.addHelpCommand() passing string or boolean (use .helpCommand() or pass a Command) (#2087)

Removed

Breaking: removed default export of a global Command instance from CommonJS (use the named program export instead) (#2017)

Migration Tips
global program
If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new Command).
// const program = require('commander');
const { program } = require('commander');
option and command clashes
A couple of configuration problems now throw an error, which will pick up issues in existing programs:

adding an option which uses the same flag as a previous option
adding a command which uses the same name or alias as a previous command

12.0.0-1 - 2024-01-19Added

.addHelpOption() as another way of configuring built-in help option (#2006)
.helpCommand() for configuring built-in help command (#2087)

Changed

.addHelpCommand() now takes a Command (passing string or boolean still works as before but deprecated) (#2087)
refactor internal implementation of built-in help option (#2006)
refactor internal implementation of built-in help command (#2087)

Deprecated

.addHelpCommand() passing string or boolean (use .helpCommand() or pass a Command) (#2087)

12.0.0-0 - 2023-11-11Fixed

Breaking: use non-zero exit code when spawned executable subcommand terminates due to a signal (#2023)
Breaking: check passThroughOptions constraints when using .addCommand and throw if parent command does not have .enablePositionalOptions() enabled (#1937)

Changed

Breaking: Commander 12 requires Node.js v18 or higher (#2027)
Breaking: throw an error if add an option with a flag which is already in use (#2055)
Breaking: throw an error if add a command with name or alias which is already in use (#2059)
Breaking: throw error when calling .storeOptionsAsProperties() after setting an option value (#1928)
replace non-standard JSDoc of @ api private with documented @ private (#1949)

Removed

Breaking: removed default export of a global Command instance from CommonJS (use the named program export instead) (#2017)

Migration Tips
global program
If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new Command).
// const program = require('commander');
const { program } = require('commander');
option and command clashes
A couple of configuration problems now throw an error, which will pick up issues in existing programs:

adding an option which uses the same flag as a previous option
adding a command which uses the same name or alias as a previous command

11.1.0 - 2023-10-13Fixed

TypeScript: update OptionValueSource to allow any string, to match supported use of custom sources (#1983)
TypeScript: add that Command.version() can also be used as getter (#1982)
TypeScript: add null return type to Commands.executableDir(), for when not configured (#1965)
subcommands with an executable handler and only a short help flag are now handled correctly by the parent's help command (#1930)

Added

registeredArguments property on Command with the array of defined Argument (like Command.options for Option) (#2010)
TypeScript declarations for Option properties: envVar, presetArg (#2019)
TypeScript declarations for Argument properties: argChoices, defaultValue, defaultValueDescription (#2019)
example file which shows how to configure help to display any custom usage in the list of subcommands (#1896)

Changed

(developer) refactor TypeScript configs for multiple use-cases, and enable checks in JavaScript files in supporting editors (#1969)

Deprecated

Command._args was private anyway, but now available as registeredArguments (#2010)

11.0.0 - 2023-06-16Fixed

help command works when help option is disabled (#1864)

Changed

leading and trailing spaces are now ignored by the .arguments() method (#1874)
refine "types" exports for ESM to follow TypeScript guidelines (#1886)
Breaking: Commander 11 requires Node.js v16 or higher

    from commander GitHub release notes

Commit messages

Package name: commander

83c3f4e Bump version to 12.0.0
e3192a1 Merge pull request #2140 from tj/release/12.x
608eaf0 Update CHANGELOG for v12 (#2133)
3f44d29 Update dependencies preparing for release (#2132)
4d832b2 Merge remote-tracking branch 'origin/develop' into release/12.x
b53109b Add links in CHANGELOG
90f3c8a 12.0.0-1
eed665d Add 12.0.0-1 changes to CHANGELOG
09244af Refactor help option implementation to hold actual Option (#2006)
ff08a02 Refactor help command implementation to hold actual Command (#2087)
b0f789f Bump eslint from 8.54.0 to 8.56.0 (#2107)
8cc042d Bump @ types/jest from 29.5.8 to 29.5.11 (#2102)
1a41d3c Bump typescript from 5.2.2 to 5.3.3 (#2100)
f686b2e Bump @ typescript-eslint/eslint-plugin from 6.10.0 to 6.18.0 (#2117)
47f740c Bump github/codeql-action from 2 to 3 (#2108)
32c05a8 Improve JSDoc (#2103)
12a8b47 Rework exitOverride description (#2098)
d8a0938 Bump @ typescript-eslint/parser from 6.10.0 to 6.13.1 (#2091)
158c3c7 Bump eslint-config-standard-with-typescript from 39.1.1 to 40.0.0 (#2083)
02ba904 Bump eslint from 8.53.0 to 8.54.0 (#2082)
066e381 Add Removed section to Deprecated (#2078)
9821f3a Update url per npm advice (#2077)
8eed8c2 Bump eslint-plugin-n from 16.2.0 to 16.3.1 (#2075)
47a48c9 Bump @ typescript-eslint/parser from 6.9.1 to 6.10.0 (#2073)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.54%. Comparing base (882fba2) to head (9328d96).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #343   +/-   ##
=======================================
  Coverage   89.54%   89.54%
=======================================
  Files          10       10
  Lines         306      306
=======================================
  Hits          274      274
  Misses         32       32

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


How to clear cache after rebuild webpack

How to clear cache after rebuild webpack

Do you mean this cache: https://github.com/owais/django-webpack-loader/#cache
At the moment, it can not be invalidated. You'll have to restart the python process to clear it and reload the file or you can turn it off if that doesn't work for you.

but, we can add a command to Django to remove the cache key, right?
@owais

There is no cache key. There is no actual "caching" going on. We just read the file once and keep it in memory forever.


add more books from Ei Maung

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

TIP :rocket:: Thanks for taking your time on fill Pull Request fields in your first contribution :heart:
It's always a good practice which it use to increase the mantainers productivity.

Thanks, and welcome to free-programming-books!


Local module federation implementation

Describe the bug
Hi devs,
I was doing a POC on the repack Module Federation implementation with local MFE and could see in the superapp showcase regarding the poc-local-module-federation and could see there are some modifications needed for the mfe to work locally without any server, so i was able to see what changes needs to be done so that it will work on ios, but there were no references on how to implement it android, it would be helpful if anyone can comment on this.
Thank you
System Info
React native 0.74.4
Re.Pack Version
4.4.0
Reproduction
.
Steps to reproduce
.

Hi, @zmzlois,
I have created 3 MFE’s and one of them i want to load from local not from server, i saw one example in the super-app-showcase where it was briefly explained how we can load a mfe using local module federation, but in that example it was mentioned how to load in ios only , there were no info regarding how to load it in android, it would be helpful if you can provide any reference for loading the local mfe in android also

Hi @jbroma / @thymikee / @zmzlois
It would be helpful if you can provide some assistance in the above mentioned issue, was running the local-module-federation-poc from super-app-showcase and was stuck when running it for android. Please provide a response as i am unable to move forward with the implementation.
Thanks in advance


First pull request connecting OLCA schema to Refactor

Run the code by running the main file elci_database_generator. Other files are connected to it.
Remember to comment out the EIA923 file for the first time to allow downloading.
Final database is in a dictionary called final_electric_lci database,

The pycache folder should not be committed
Will change that
The init.py is a copy of the stewi file..this should not be committed as is.
I put an empty file by that name otherwise import was not working. Is it required or not required? Need to look a bit more into it.
I’m not sure why you created egrid_databasefile_setup.py? This code should be within generation_processes_from_egrid.py
Will change that.
There are too many EIA923 files committed. If its the same year, there should just be one file.
Regarding this, my script is downloading EIA 923 and then reading from that. EIA 923 gives you a zip file.  When I unzip that through the code, it produces many excel files from which only one is read.
Should I remove this part??


Indent (optionnally) all the paragraphs

Description
Currently, "Only the first line of a consecutive paragraph will be indented (not the first one in a block or on the page)."
Actually, this is a choice that is not universal. For instance, in French, it's quite common to have indentations on all the paragraphs.
Could this made configurable, to better support French typography ?
Use Case
Compose texts in French using the French conventions.

Duplicate of https://github.com/typst/typst/issues/311
TLDR: There are technical difficulties with offering such an option at the moment, but it will be implemented in the future.

Thanks.


x/tools/go/analysis, syscall: ptrace redeclared in this block

What version of Go are you using (go version)?

$ go version
go version go1.16 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

Currently, I'm only able to reproduce inside my IDE (goland).
I'm still trying to reproduce outside of goland.
I'm thinking that the build tag is missing in syscall/ptrace_ios.go
I created a minimal reproducible (inside goland) project:

ptrace-bug.zip

.
├── foo_test.go
├── go.mod
├── go.sum
└── testdata
    └── src
        └── a
            └── a.go

foo_test.go:
package sandbox

import (
	"testing"

	"golang.org/x/tools/go/analysis"
	"golang.org/x/tools/go/analysis/analysistest"
)

func TestBug(t *testing.T) {
	ana := &analysis.Analyzer{
		Name:     "ptrace-bug",
		Doc:      "example",
		Run: func(pass *analysis.Pass) (interface{}, error) {
			return nil, nil
		},
		Requires: nil,
	}

	testdata := analysistest.TestData()
	analysistest.Run(t, testdata, ana, "a")
}

a.go:
package a

import (
	"time"
)

func validCases() {
	_ = time.Second * 30
}

What did you expect to see?
GOROOT=/home/ldez/.gvm/gos/go1.16 #gosetup
GOPATH=/home/ldez/sources/go #gosetup
/home/ldez/.gvm/gos/go1.16/bin/go test -json ./...
=== RUN   TestBug
--- PASS: TestBug (0.52s)
PASS
ok  	github.com/golangci/sandbox	0.524s

Process finished with exit code 0

What did you see instead?
GOROOT=/home/ldez/.gvm/gos/go1.16 #gosetup
GOPATH=/home/ldez/sources/go #gosetup
/home/ldez/.gvm/gos/go1.16/bin/go test -json ./...
=== RUN   TestBug
/home/ldez/.gvm/gos/go1.16/src/syscall/zsyscall_linux_amd64.go:178:6: ptrace redeclared in this block
/home/ldez/.gvm/gos/go1.16/src/syscall/ptrace_ios.go:10:6: 	other declaration of ptrace
    analysistest.go:294: error analyzing ptrace-bug@a: analysis skipped due to errors in package
--- FAIL: TestBug (0.69s)

FAIL
FAIL	github.com/golangci/sandbox	0.694s

Process finished with exit code 1

I'm able to create a reproducible example without the IDE.
with go1.16:
$ go run .
-----------------
exit status 1
-----------------
/home/ldez/.gvm/gos/go1.16/src/syscall/zsyscall_linux_amd64.go:178:6: ptrace redeclared in this block
/home/ldez/.gvm/gos/go1.16/src/syscall/ptrace_ios.go:10:6:      other declaration of ptrace
--- FAIL: TestBug (0.78s)
    analysistest.go:294: error analyzing ptrace-bug@a: analysis skipped due to errors in package
FAIL
FAIL    github.com/golangci/sandbox     0.784s
FAIL

with go1.15:
 go run .
-----------------
<nil>
-----------------
ok      github.com/golangci/sandbox     0.436s

ptrace-bug-repo.zip

@gopherbot Please open backport to 1.16.
The 1.16 release can't be analyzed by tools built with earlier versions of Go, because those earlier releases don't recognize that "ios" is now a valid GOOS value.  The fix is to use an explicit build tag.  We should backport that fix to the 1.16 release branch.


Duplicate CA combinations on 28874 file decoded

Hi,
I've been trying to modify my 28874 file in order to add some CA combos to a Samsung S10e but something weird happen.
When I decode my original 28874 file I can see duplicated combos. And when I try to add some new lines and re encode the file cause the phone not getting any signal like a dead modem but once I return to the original file it works again. As you can see below there are lines duplicated like:
2A2A-2A4-14A2-66A4 12
2A2A-2A4-14A2-66A4 12
or
2A4-7A2A-7A4 10
2A4-7A2A-7A4 10
I'm adding the original file decode if someone want to take a look.
00028874original.txt
Your help will be highly appreciated.

Can you send the original 28874 ?


User Management - password criteria should be stated upfront

When you create a new user in the admin console, it requires a password of a certain number of letters + capitalized letter + special char etc. This criteria should be stated upfront so that you don't land up iterating over user creation to read the error messages one at a time to find out what the criteria are to set the password!
http://localhost:8081/user-management/new

For reference when making the update these are the requirements:
        if len(decoded_password) < 8:
            raise ValueError("Password must have at least eight characters.")
        if re.search("[0-9]", decoded_password) is None:
            raise ValueError("Password must have at least one number.")
        if re.search("[A-Z]", decoded_password) is None:
            raise ValueError("Password must have at least one capital letter.")
        if re.search("[a-z]", decoded_password) is None:
            raise ValueError("Password must have at least one lowercase letter.")
        if re.search(r"[\W]", decoded_password) is None:
            raise ValueError("Password must have at least one symbol.")


Use of relative paths to enable usage with different reverse proxy locations

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
It would be nice to use relative paths in the html files (for the assets, etc.)
It would make it possible, to use uptime kuma with reverse proxy locations other than "/"
E.g. proxy via nginx from https://someserver/uptime to http://uptimekumaip:3001
With the absolute paths used, uptime kuma will try to load the assets from https://someserver/assets/ instead of https://someserver/uptime/assets
✔ Solution
Change html (and other required files) to use relative instead of absolute paths for assets and links.
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate of https://github.com/louislam/uptime-kuma/issues/147

See #1092 for the challenges in verifying that this works


Requests missing an :authority pseudo-header return PROTOCOL_ERROR

We are using nghttpx to upgrade requests from HTTP to H2. nghttpx omits the :authority pseudo-header when creating the request to forward on via H2, this appears to be consistent with the spec:

The :authority pseudo-header field includes the authority portion of the target URI ([RFC3986], Section 3.2). The authority MUST NOT include the deprecated userinfo subcomponent for http or https schemed URIs.

To ensure that the HTTP/1.1 request line can be reproduced accurately, this pseudo-header field MUST be omitted when translating from an HTTP/1.1 request that has a request target in origin or asterisk form (see [RFC7230], Section 5.3). Clients that generate HTTP/2 requests directly SHOULD use the :authority pseudo-header field instead of the Host header field. An intermediary that converts an HTTP/2 request to HTTP/1.1 MUST create a Host header field if one is not present in a request by copying the value of the :authority pseudo-header field.

However, it appears that h2 incorrectly rejects the request with PROTOCOL_ERROR when this happens. It also seems like there should also be some logging around this code path, but I couldn't get it to trigger.

Nice write-up, I agree with your assessment! (Both that it shouldn't error, and some logs would be nice).

I hit similar problem related to authority header. Even more controversial. I'm using tower-grpc and k8s api client written in golang. Unix domain socket is used as the transport. golang client library inserts the name of the unix domain socket to authority header (i.e. /var/tmp/some.sock) and h2 fails the request (because slash is not allowed in authority header). I opened a ticket for the client side (https://github.com/grpc/grpc-go/issues/2628) so that they don't set authority header unless they are sure that it is a valid value.
If they fix their part and we fix this ticket, then it should be good. Another option would be to fix h2 to be more tolerant and ignore the authority if invalid (or make such behaviour optional based on some configuration flag). Opinions?

Well, I think we need to figure out who is in the wrong, it might be h2.
I think I misinterpreted:

The server MUST include a value in the :authority pseudo-header field for which the server is authoritative (see Section 10.1). A client MUST treat a PUSH_PROMISE for which the server is not authoritative as a stream error (Section 5.4.2) of type PROTOCOL_ERROR.

in this section.
That probably means that :authority is only required for push promises... So odds are it is a bug in h2.

@jkryl is this something that you can look into. It probably is just a question of finding the code that checks if :authority is present and updating the check to only run if it is a push promise frame. Does that seem correct @seanmonstar?

Though, I do think that h2 is correct to throw errors if :authority contains invalid characters like slashes... correct?

@olix0r hmm, yeah that is a good point (i missed that part).
Welp... I guess the question is if we want h2 to be tolerant of spec violations.

@carllerche http is supposed to be spec-compliant, right? If so, and if h2 uses http, then h2 probably needs to be as well.

The HTTP2 spec urged implementors to be strict, to try to battle what happened with HTTP1 becoming a weak mess. I'm in favor of that.

@seanmonstar I agree.

Thanks for your opinions 👍 The ticket for go-grpc mentioned above has been flagged as a bug, so there is a good chance that it will be fixed in future. If we just tolerate unspecified authority header, which has been the original intent of this ticket, then we will be fine.

I tried looking into fixing this, and came out unsure what the exact problem is. Here's what I found:

In the server case, it appears that a request without an :authority is permitted just fine: https://github.com/carllerche/h2/blob/a3e59eb7e24a3bd4ff59806ead7842377eb34b78/src/server.rs#L1248.
In the client case, if a request is sent with no :authority, then Request::version() cannot be Version::HTTP2, as per https://github.com/carllerche/h2/blob/a3e59eb7e24a3bd4ff59806ead7842377eb34b78/src/client.rs#L1515.

Thanks for looking into this! 👍 It is possible that the issue does not exist. My problem was a bit different and I'm using a temporary fix to work around invalid authority header problem.
based on the following comment in client code:

// It is not possible to have a scheme but not an authority set (the
// `http` crate does not allow it).

I'm wondering what h2 client will do when support for UDS (unix domain socket) is added in the future. As it seems that authority is always required for http2 but there is no reasonable value to put into the header. Basically the same problem that golang http2 client suffers from. But that is off topic.
It might be worth writing a test case that covers missing authority header if there is none. Just my 2 cents.

We finally found what was happening here. Even though the code in h2 allowed an optional :authority, the http::uri::Builder was unhappy about trying to build a Uri with a scheme and path, and so the error was still being triggered. Fix is in #372.


Fix Regular Expression injection

The fact of not sanitizing user input appended to a regular expression may lead to a Regular Expression Denegation of Service by an attacker crafting a regular expression taking too much to load, or simply change the behaviour of the program.
Vulnerable code:
https://github.com/tubone24/ebook_homebrew/blob/7df72331e9636ad2821543144c8aef02d40b7e23/ebook_homebrew/core.py#L90
References:
OWASP ReDoS

:x: Build ebook_homebrew 1.0.647 failed (commit https://github.com/tubone24/ebook_homebrew/commit/99e710f90d by @jorgectf)

🎉


userdb got lost, I found it.

Got deleted somewhere.. :man_shrugging:

Sorry, now all the tests have to be run again...


add action to get values from config.xml file on cordova projects

We've being using fastlane with our cordova projects and it works very good.
We are missing some actions that could make our Fastlane files cleaner.
This is one of those actions.
With cordova you usually not edit the xcode project directly, instead use the config.xml
file.

I could use some help here, @KrauseFx
Where should I add this gem dependency??
over here?? https://github.com/fastlane/fastlane/blob/master/fastlane.gemspec#L34

That's a great pull request, thanks @blackjid!

Where should I add this gem dependency??
over here?? https://github.com/fastlane/fastlane/blob/master/fastlane.gemspec#L34

no, you already added the verify_gem! call so no additional dependency is needed. Instead the user adds the dependency to their Gemfile

Ok, I like that, but for the test?? is failing because the gem is not installed.

Don't worry about the Travis tess

What do you think??
This is the scenario, the most useful values to get from the config.xml file are probably name and identifier.
Maybe version, but for that it makes more sense an action to update the version.
Does it make any sense to you to have specific actions for that values??
cordova_get_app_id # tools.fastlane.cordova
cordova_get_name # Cordova App
cordova_update_version(value: '1.2.1')

Maybe they can alse set some lane_context that other actions can use, specially the app_id
Or with this generic action would be enough??

Hey, thanks for updating the pull request. I added some final comments before it's ready to be merged. Could you also squash your commits so that we only add one commit to the history?
Thanks again for your great contribution :+1:

hey @blackjid, just wanted to check in here. would love to get this merged! would you mind just addressing @KrauseFx final comments and squash the commits and we will be good to go! :rocket:

hey @ohwutup sorry about that... I'm not really sure if I like this approach for getting that from the config file... I find it complicated to generalize because you need to understand how the xml parser works and how it return its values...
for example
name = cordova_get_config_value(path: 'cordova/config.xml', key: 'name').first

Here I have to call first, because it returns an array of n tags with the name "name"....
I'm thinking on other approach, on having actions for specific keys. I'm doing this in https://github.com/platanus/fastlane-cordova/tree/initial-release/fastlane/actions
Instead of having a generic action cordova_get_config_value to have specific actions cordova_get_app_name, cordova_get_app_ip, cordova_get_app_version
I would love to know what do you think....

i don't have too much context because I'm not really familiar with cordova config files, but that seems like a much safer idea! would you want to get those merged in?

cordova config files are just xml files...
what do you think on having both?? I could rebase this generic one, and then make a PR with the specific/safer ones??
cc: @KrauseFx ?

IMO, we should just go with the specific ones to avoid too many actions doing similar things.

IMO, we should just go with the specific ones to avoid too many actions doing similar things.

Hey @blackjid! Just wanted to bump this PR to see if we should close this in lieu of your upcoming PR with safer XML reading? :octopus:

yes, you can close it...;)

Cool, thanks @blackjid! Looking forward to the other implementation! This is a great feature!

+1 would love to see better cordova support.  thanks!

I created a PR with some basic actions for cordova. #3754


Add note about PyObjectProtocol

I've been porting some Python code to Rust module-by-module using PyO3. I'm not really a Rust person, so I've been using ChatGPT to write the new code. I give it the Python, it gives me back Rust. This has been unnervingly successful. It has even been giving back working PyO3!
One problem though is that it keeps suggesting a trait called PyObjectProtocol. And I cannot find a trace of this in the docs. Is it a so-called "hallucination"? No, it turns out that the "knowledge cutoff" was September 2021, and the trait was eliminated since then.
Given this strange situation, it might be helpful to add a comment somewhere about PyObjectProtocol and whatever replaced it.

We do have a migration guide which details that quite a few Py*Protocol traits have been first deprecated, then disabled by default and then removed, c.f. https://pyo3.rs/v0.18.2/migration#pyproto-has-been-deprecated


MSID: 92678 Version: 1 DOI: 2<IP_ADDRESS>6574

"msas": "Cancer Biology"
"msid": "92678"
"preprintDoi": "10.1101/2<IP_ADDRESS>6574"
"Reviewed Preprint posted": "2023-11-17"
"Sent for peer review": "2023-09-15"
"Posted to bioRxiv": "2023-09-26" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>6574v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92678)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/92678/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6574)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/92678/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/92678)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/92678

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/92678

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/92678/v1/92678-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/92678)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Thanks @fred-atherden. In the data availability section I noticed the link to the accession number is not hyperlinked (is in the PDF) although its not public anyway so I've marked this as QC OK.


add INGRESS_MODE suppport

tested with all three cloud "provider" values, both with tfstate and directly. Verified that the correct annotations got set on the ingress controller service.
Using branch "infra_mode". The existing branch "private_cluster" is stale and should be deleted. Leaving it around for now in case reviewers want to reference it.

not seeing anything in the code that would make this backward-incompatible. Still, I did a successful deployment on a gke cluster successfully with this branch, so I'm quite confident we are not breaking aws or gcp.

Looks good waiting on viya4-iac-azure PR Number 120.


Repo sync for protected CLA branch

The pull request is created from master637722722658458893 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change. @evanwindom


make the route404 customizable in the router component

Fixed with my PR.

I push a PR that fix it: https://github.com/tsoding/grecha.js/pull/17


ENYO-1447: [W2_Accessibility] It doesn't support speech rate when readin...

...g title
Issue
: In specific case garnet accessibility calls TTS api directly
regardless speech rate.
Fix
: Add the code getting speech rate form system setting and appying it
before calling TTS api.
Enyo-DCO-1.1-Signed-off-by: Jaewon Jang<EMAIL_ADDRESS>

getSpeechRate reads alertMessage. This is very ambiguous since function name and action is quite different.
Call getSpeechRate and readAlertMessage separately or call getSpeechRate inside of the readAlertMessage will be more straightforward. What do you think?

I've changed code using callback.

It looks good for me


Example 4-5. ValueError: Cannot evaluate w/o an evaluation worker set in the Trainer or w/o an env on the local worker!

ValueError: Cannot evaluate w/o an evaluation worker set in the Trainer or w/o an env on the local worker!
Try one of the following:
1) Set `evaluation_interval` >= 0 to force creating a separate evaluation worker set.
2) Set `create_env_on_driver=True` to force the local (non-eval) worker to have an environment to evaluate on.

In [252]: checkpoint = trainer.save()
     ...: print(checkpoint)
     ...:
     ...: evaluation = trainer.evaluate(checkpoint)
     ...: print(pretty_print(evaluation))
     ...:
     ...: restored_trainer = DQNTrainer(env=GymEnvironment)
     ...: restored_trainer.restore(checkpoint)
/root/ray_results/DQN_GymEnvironment_2022-10-25_10-50-33_uvb3xkn/checkpoint_000010
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [252], in <cell line: 4>()
      1 checkpoint = trainer.save()
      2 print(checkpoint)
----> 4 evaluation = trainer.evaluate(checkpoint)
      5 print(pretty_print(evaluation))
      7 restored_trainer = DQNTrainer(env=GymEnvironment)

File ~/.cache/pypoetry/virtualenvs/ray-KeD1w6JO-py3.9/lib/python3.9/site-packages/ray/rllib/algorithms/algorithm.py:775, in Algorithm.evaluate(self, duration_fn)
    770 else:
    771     if (
    772         self.evaluation_workers is None
    773         and self.workers.local_worker().input_reader is None
    774     ):
--> 775         raise ValueError(
    776             "Cannot evaluate w/o an evaluation worker set in "
    777             "the Trainer or w/o an env on the local worker!\n"
    778             "Try one of the following:\n1) Set "
    779             "`evaluation_interval` >= 0 to force creating a "
    780             "separate evaluation worker set.\n2) Set "
    781             "`create_env_on_driver=True` to force the local "
    782             "(non-eval) worker to have an environment to "
    783             "evaluate on."
    784         )
    786     # How many episodes/timesteps do we need to run?
    787     # In "auto" mode (only for parallel eval + training): Run as long
    788     # as training lasts.
    789     unit = self.config["evaluation_duration_unit"]

Input In [252], in <cell line: 4>()
      1 checkpoint = trainer.save()
      2 print(checkpoint)
----> 4 evaluation = trainer.evaluate(checkpoint)
      5 print(pretty_print(evaluation))
      7 restored_trainer = DQNTrainer(env=GymEnvironment)

File ~/.cache/pypoetry/virtualenvs/ray-KeD1w6JO-py3.9/lib/python3.9/site-packages/ray/rllib/algorithms/algorithm.py:775, in Algorithm.evaluate(self, duration_fn)
    770 else:
    771     if (
    772         self.evaluation_workers is None
    773         and self.workers.local_worker().input_reader is None
    774     ):
--> 775         raise ValueError(
    776             "Cannot evaluate w/o an evaluation worker set in "
    777             "the Trainer or w/o an env on the local worker!\n"
    778             "Try one of the following:\n1) Set "
    779             "`evaluation_interval` >= 0 to force creating a "
    780             "separate evaluation worker set.\n2) Set "
    781             "`create_env_on_driver=True` to force the local "
    782             "(non-eval) worker to have an environment to "
    783             "evaluate on."
    784         )
    786     # How many episodes/timesteps do we need to run?
    787     # In "auto" mode (only for parallel eval + training): Run as long
    788     # as training lasts.
    789     unit = self.config["evaluation_duration_unit"]

ValueError: Cannot evaluate w/o an evaluation worker set in the Trainer or w/o an env on the local worker!
Try one of the following:
1) Set `evaluation_interval` >= 0 to force creating a separate evaluation worker set.
2) Set `create_env_on_driver=True` to force the local (non-eval) worker to have an environment to evaluate on.

I think we've fixed this now, thanks for the issue!

(the API call in this example was wrong in any case... you just evaluate, no need to specify a checkpoint)


README.MD | Added missing requirement for buildozer

Added missing requirement to the "how to use with buildozer" example line
sdl2_ttf is required to show icons on android devices.
Description of Changes

added missing requirement on how to use with buildozer example line in README.md
fix for #257
fix #918

I have the same issue of no icons with the development version of KivyMD with sdl2_ttf == 2.0.15 included in the spec file. With the current stable version of KivyMD the icons show but not with the dev version which I need. I have repeatedly run,
buildozer android clean
and then
buildozer android debug
I have done a complete reinstall on a different computer with the same results. The icons show on WIn10 but not in the compiled apk.
Here are my requirements,
requirements = python3, pillow, kivy==2.0.0, https://github.com/kivymd/KivyMD/archive/master.zip, sdl2_ttf == 2.0.15
Is there another issue or am I missing something?


When tagging a release, don't have daily release build in helm

Describe the bug
{{ Succinctly describe the bug }}
When uninstalling and reinstalling the chart, my grafana pod stopped being able to start because the new image was throwing a db migration error.
Expected behavior
{{ What did you expect to happen? }}
When reinstalling the chart, it would still work.
Steps to reproduce the bug
{{ Minimal steps to reproduce the behavior }}
Install the istio chart using branch release-1.0
Version
{{ What version of Istio and Kubernetes are you using? Use istioctl version and kubectl version }}
Not using istioctl, used helm install on branch release-1.0.
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-08T16:31:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.6", GitCommit:"a21fdbd78dde8f5447f5f6c331f7eb6f80bd684e", GitTreeState:"clean", BuildDate:"2018-07-26T10:04:08Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Is Istio Auth enabled or not?
{{ Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input }}
no
Environment
{{ Which environment, cloud vendor, OS, etc are you using? }}
aws
I believe that when making a release, the helm chart should be tagged with the appropriate image instead of the daily release build:
https://github.com/istio/istio/blob/1.0.0/install/kubernetes/helm/istio/values.yaml#L9
should instead be 1.0.0
Thoughts?

Agreed. The 1.0.0 tagged version of this file should point to 1.0.0.
The release-1.0-latest-daily value picks up the latest 1.0.x build which isn't desired when working with the 1.0.0 tagged branch or the downloaded released source code.
cc @hklai

All daily releases should have the correct tag in values.yaml.
I verified the tar balls in https://gcsweb.istio.io/gcs/istio-prerelease/daily-build/release-1.0-20180823-09-15/gcr.io/ and found the right tag in install/kubernetes/helm/istio/values.yaml.
tag: release-1.0-20180823-09-15
Similarly, LTS releases should have the LTS version tag. The values.yaml in the tar balls on https://github.com/istio/istio/releases/tag/1.0.0 have the following correctly.
tag: 1.0.0
On the other hand, tag: release-1.0-latest-daily in https://github.com/istio/istio/blob/1.0.0/install/kubernetes/helm/istio/values.yaml#L9 is expected, as it is a floating tag which points to the latest daily build. It is meant for developers who tries to install from the source directly, instead of using any release artifacts. In that case, the latest daily release will be used instead.

@hklai Sounds reasonable but I downloaded https://github.com/istio/istio/archive/1.0.0.zip and it has tag: release-1.0-latest-daily.

https://github.com/istio/istio/archive/1.0.0.zip is a source code archive, so its values.yaml has the original tag value.
On the other hand, the release artifacts (i.e. istio-1.0.0-linux.tar.gz, istio-1.0.0-osx.tar.gz, and istio-1.0.0-win.zip) should have the right tag 1.0.0.

Okay thanks for the info @hklai, so it sounds like if I want the source for a specific tag or date I should download the release artifiacts from the releases tab or find it in that gcsweb online directory

@k Correct.
I am closing this as I think this has been resolved. Feel free to reopen if you see more issue.


The ordering of the arguments to pass to jl_method_def seems wrong

The ordering of the arguments to pass to jl_method_def seems wrong here:
https://github.com/perrutquist/CodeTransformation.jl/blob/c915df42db1c8913f227b03437070ce216a06713/src/CodeTransformation.jl#L21
also wrong here
https://github.com/NHDaly/DeepcopyModules.jl/blob/55093e747e0d7bca3fd2a7d880533788d4eba3d2/src/deepcopy_functions.jl#L58
According to
https://github.com/JuliaLang/julia/blob/19f44b661254cccca94ba11b7b6d0482470ed2bb/src/julia.h#L1487
they should be
jl_method_def(argdata::SimpleVector, ci::CodeInfo, mod::Module) =
    ccall(:jl_method_def, Cvoid, argdata, (SimpleVector, Any, Ptr{Module}), ci, pointer_from_objref(mod))

instead ?

argdata is the first argument not the second

argdata is the first argument not the second

argdata is the first argument not the second


React 0.14 support

Can you make a 2.0 and 0.0.13 release for react 0.14 support? I'm getting warnings mostly.

Hi @Nic128, could you help me to try these branches works or not?
https://github.com/patw0929/react-intl-tel-input/tree/upgrade-react-0.14
https://github.com/patw0929/react-intl-tel-input/tree/0.0.x-with-react-0.14
Thanks!

For this branch, https://github.com/patw0929/react-intl-tel-input/tree/0.0.x-with-react-0.14, you also need to put react-dom in your components that use findDOMNode (IntlTelInput.js and CountryList.js). Plus, in the package.json, if we put the peerDependencies up to date, can we delete the react 0.13.3 in the devDependencies?
Will test the other one.

Same comments for this branch. https://github.com/patw0929/react-intl-tel-input/tree/upgrade-react-0.14

Fixed. Please take a look again, thanks!

Warnings for react have gone away for both branches, it's good. Now that react 0.14.1 is out, let's put the peerDependencies to:
"peerDependencies": {
    "react": "^0.14.0",
    "react-dom": "^0.14.0"
  },

This way npm won't give warnings if we don't use 0.14.1.

Hey there, I was trying to wrap the Intl-tel-input into a react component and I found this project. I'm currently using react 0.14.0 and I think that usage of ^0.14.0 is a proper solution. I thinks I'll use this component in my project. Thanks.

Hey guys, I have revised it. Please check it.
Thanks again!

upgrade-react-0.14 is fine. can you update 0.0.x-with-react-0.14 with the same peerDependencies?

Sure. I have updated it.

Everything is good.

Merged. Is everything ok still?

Good for me.

Issue closed.
If you still find issues, please open a new issue. Thank you guys.


Split KSCrash cocoapod into several subspecs

Hi. We are working on an iOS lib which should handle crashes among other useful activities and want to use KSCrash for this part. As full KSCrash is quite large it would be great if it was possible to include only limited subset of functionality. Based on your answer to this issue https://github.com/kstenerud/KSCrash/issues/43 I suggest the following cocoapods subspecs could be created:

KSCrash/Core
KSCrash/Reporting
KSCrash/Sending

The latter two subspecs could optionally be split even further, e.g. KSCrash/Reporting/AppleFmt for only Aplle style crash report formatting and KSCrash/Sending/eMail for sending only via e-mail.
I actually tried creating cocoapod subspec which includes only core crash recording system and apple formatter(that's the parts used by our lib). It could be seen here https://github.com/fkazak/Specs/blob/master/KSCrash/0.0.1/KSCrash.podspec
However currently all the source files are stored in the same folder what leads to the following problems:

for subspec creation it's necessary to list all the files required (you can see my subspec is around 3 times larger then original podspec). If they were stored in separate folders subsspecs would take only a few lines.
if files are added or removed subspecs should be updated manually.

I believe in case you are interested in such a feature added to your library I can do most of files moving and sample projects adjustments myself and send a pull request then.
Thanks!

Fixed by #50 ?


Build the docker image from scratch, for a lighter docker image?

It just a proposal for now, but it being working perfectly, and i run it everyday with my own docker image.
Currently the docker image is build like this:
FROM golang:alpine AS build-env

RUN apk add --no-cache git make

WORKDIR /src
ADD . /src
RUN make doh-server/doh-server

FROM alpine:latest

COPY --from=build-env /src/doh-server/doh-server /doh-server

ADD doh-server/doh-server.conf /doh-server.conf

RUN sed -i '$!N;s/"<IP_ADDRESS>:8053",\s*"\[::1\]:8053",/":8053",/;P;D' /doh-server.conf

EXPOSE 8053

ENTRYPOINT ["/doh-server"]
CMD ["-conf", "/doh-server.conf"]

My proposition. To build the final image from 'scratch':
FROM golang:alpine AS build-env

RUN apk add --no-cache git make

WORKDIR /src
ADD . /src
RUN make doh-server/doh-server

FROM scratch

COPY --from=build-env /src/doh-server/doh-server /doh-server

ADD doh-server/doh-server.conf /doh-server.conf //Comment. this can also be changed to a COPY instead of a ADD

RUN sed -i '$!N;s/"<IP_ADDRESS>:8053",\s*"\[::1\]:8053",/":8053",/;P;D' /doh-server.conf

COPY --from=build-env /etc/passwd /etc/passwd
COPY --from=build-env /etc/group /etc/group
# run as non-privileged user
USER nobody:nobody

EXPOSE 8053

ENTRYPOINT ["/doh-server"]
CMD ["-conf", "/doh-server.conf"]

Advantage:

Since it a go image it can be shipped like this
the resulting image will be smaller
less attack surface since there will only be the go application.

Disadvantage:

currently no logs output (can be figured out i think)

The image could be also made smaller by adding '-s -w' to the 'ldflags' like this:

CGO_ENABLED=0 GOOS=linux go build -ldflags "-s -w"

I can make a pull request if your okay with those changes, but i just wanted to discuss it with you first ^^
I've been running my image for 9month straight with no issues on my side
You can check my current docker image and GitHub for it.

Adfditional comment on what the ldflags do:
-s    disable symbol table
-w    disable DWARF generation

-ldflags "-s -w"

I'm perfectly fine with this. Just make a PR and I'll be happy to merge it.

Disabling CGO

Disabling CGO is usually fine for most web applications in the wild, but this is a DNS server, and disabling CGO slightly changes how the DNS client in netgo behaves (from directly calling into the libc to mimicking the behavior in pure Go). This change has been causing unexpected problems all the time and I really don't recommend doing this.
And there will not be any libc version incompatibilities because we invented Docker to solve exactly this problem.

Starting from scratch

This is another popular thing that I don't recommend. 3 reasons:

There is a high chance you forget to add something that silently changes the behavior of the program in unexpected ways. For example, you forget to copy the trusted CA certificates which might cause problems when the program is connecting to a HTTPS server.
You lose the capability to live debug in the container.
Others cannot easily extend the image by FROM image; RUN .... For example, it is now 10x harder to add dig command to the container for health checks (this is a real use case: I deploy it in a cluster and have rolling updates).

Starting from scratch will save you at most a few megabytes, plus base image layers will be shared between images, so I personally feel it has more cons than pros.

Running as nobody

While running as non-root comes with some security defaults that makes the system slightly more secure, there are multiple problems:

Running as non-root with a host volume causes unexpected permission mappings. A lot people run this software not on dedicated application servers but their own computers or shared workstations, and we cannot reasonably assume any UID/GID will be mapped to a certain permission set on the host.
Not every Linux distro use the same UID/GID for nobody, which makes the first problem even worse.
If Docker rootless mode is configured, we cannot assume how many subUIDs/subGIDs has been allocated to a certain user namespace. Using a large UID/GID in the container might cause troubles.

There are modern ways to achieve the same security enhancements. Recommended:

Use docker run --cap-drop ... to remove non-essential capabilities (our documentation does not have an example; if you have time, do help add an example here!)
Set up Docker/Podman rootless mode.

I'll make a pr now for the ldflags 👍🏻
Also other question since we at it, is the latest tag based on commit or latest version ?

Alright so when a new version will be up the will be a tag for it then? ^^

I guess this can be safely closed for now.


Cannot find module '~/src/types' or its corresponding type declarations.

What happens?
We're experiencing issues when running nuxi typecheck:
node_modules/@scalar/nuxt/dist/runtime/components/ScalarApiReference.vue:9:36 - error TS2307: Cannot find module '~/src/types' or its corresponding type declarations.

9 import type { Configuration } from '~/src/types'
                                     ~~~~~~~~~~~~~

Found 1 error in node_modules/@scalar/nuxt/dist/runtime/components/ScalarApiReference.vue:9

Looking at node_modules, it seems like the src folder doesn't exist?

This is with Scalar 0.2.141. Tried to clean the build/cache folders and delete node_modules and build it again, but no luck so far.
What did you expect to happen?
This is the same issue as #2944 which was closed a few months ago. I'm running Nuxt 3.13.1.
OpenAPI Document
No response

hello !
same with
@scalar/nuxt 0.2.160
nuxt 3.14.1592
node v23.4.0 or bun / pnpm
also happening in CI
thanks !


Same machine in two different back-end pools

Hello,
We have been using Application Gateway with a simple backend pool configuration with Virtual machines. We have two different pools with a corresponding listeners from two different hostname HTTP setting configurations.  Essentially its hosting two different websites (Although has the same code base). We have a machine (VM or App) that has a code for website maintenance which we would like to use it in both the pools during our maintenance on the App servers. Which means the same website is redirected for both the websites during our maintenance. However we see a conflict error while adding same machine in both the pools.
Also we are looking for a way how can we set a maintenance mode (Static Website) for our website  hosted on App Gateway. For Ex: We can host a static website in Storage Account but how can that be redirected through Application Gateway? Any quick help is appreciated. Thanks!

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

ID: d5aa653c-11a8-ac3d-830f-0dfdde46cbb6
Version Independent ID: 4df0aed8-67fb-2fc8-d12d-72ac9bd0c093
Content: Application gateway components
Content Source: articles/application-gateway/application-gateway-components.md
Service: application-gateway
GitHub Login: @abshamsft
Microsoft Alias: absha

@mjannapureddy07 Have you seen this doc on Application Gateway Custom error pages?
If you would like a "maintenance mode", you will need to redirect the listeners to a different backend pool with the maintenance website.

Thanks for the response. I have looked at that earlier but I had a question there,
What if we see these errors during the regular functioning of Application? due to any other reason (For Ex: Application Freezes due to some thread locks etc..)

@mjannapureddy07 Application freezes would ideally be picked up by the Health Probes and traffic will no longer be routed to that instance.

@mjannapureddy07 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update kernel side load job status check

SUMMARY
The kernel sideload job check can face a race condition in a final job success task and/or the Complete message may not be the last one.
ISSUE TYPE

Enhanced Feature

Tests
Test-Hints: no-check

@lack Please let me know what do you think about this

recheck

Just recheck after merging https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/494, which includes the fix for the sanity checks.

retest

recheck

@agurenko , I think you will need to rebase your change to take the update from https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/494, then the sanity check issue should disappear

Is ssh signing not enough? Still seeing The base branch requires all commits to be signed. :(

Is ssh signing not enough? Still seeing The base branch requires all commits to be signed. :(

I suppose you have to upload your public ssh key that was used to sign.

@fredericlepied yes, of course, the key was uploaded long time ago, it's just signing wasn't enabled.

@fredericlepied yes, of course, the key was uploaded long time ago, it's just signing wasn't enabled.

It doesn't seem to be the case:

@fredericlepied yes, of course, the key was uploaded long time ago, it's just signing wasn't enabled.

It doesn't seem to be the case:

Okay, fixed now. Apologies.

@fredericlepied can we retry again? Something went wrong

@agurenko sorry, we were having some permission issues in the runner. It should be fixed now. Cheers

@betoredhat thanks, appreciate it!


pip3 install -r requirements.txt

On the line 5,
pkg-resources==0.0.0
It that a slip of pen? Thanks!

It's dumped by
pip freeze > requirements.txt

Not sure why it exists. Do you mind creating a pull request? or I can directly fix it. Thanks!

It's dumped by
pip freeze > requirements.txt

Not sure why it exists. Do you mind creating a pull request? or I can directly fix it. Thanks!

Thanks for your explanation!
Sorry that I don't know how to create a pull request.


Convert dos files to unix format

:PepeLaugh:

New rewrite files should be in unix format... also closing due to agreement on discord.


docs: link to virtual workspaces demo

Since this demo is referenced as the canonical example of this use case, make it easier to find.

/ok-to-test
/lgtm
/approve
Thanks!!!

This is a docs-only change, and our ci-docs-only config is missing e2e-sharded. That's why it's not running on this PR (even though it's required). I've opened #1466 to fix that.

/retest

docs-only PR, merging


mattermost solution review

Please enter a name for your solution (Can be used to prepare domain for you and needed to track your solution on the grid ) -> Choose a unique name for your mattermost instance (will be used in listing and deletions in the future and in having a unique url)

Disk size info is too level
we should ask for resources in form of  Silver, Gold, Platinum or whatever form that maps to underlying mapping to mru, cru and disk space

Expiration

Let's make the default 2 months or 6 month

Waiting for payment should keep showing the qrcode in case it was missed

Deployment information should be removed (I can't do anything and already paid)

Improve deployment message

Mention the deployment should take around 2 3 minutes, but might take longer (better phrasing needed @rkhamis  )

Success phrasing is wrong

Congratulations! Your own instance from mattermost deployed successfully should be you deployed a new instance (solution name) of mattermost

remove container ip info

Commit_ID db38a89e80fd13e999ce8508a9ed62b5bddac4c5 , Branch  development.


Geometric mean retruns Infinity

Plugin Name with version
2.2.10, 2.3.9
JSpreadsheet version
v10.x
Describe the bug
The geometric mean returns infinity for a table of positive integers and decimals.

Reproduction steps
1.
2.
3.
...

MCT (2).xlsx

Hi,
For me, It's normal, this product of this 1000 values is > 1.7976931348623157e+308 (Number.MAX_VALUE)
this value is max supported by your navigator. On Excel you have too an error ? on my sheet excel, i can't make a product and have error.

No, in Excel I am getting proper outcomes: 39,372/4,011 respectively. Obviously, you cannot multiply everything first and then take a root, as you get an enormous number. Maybe do the other way around -> first take a root of n-th degree, and then multiply outcomes.

Let me check it, keep you updated.


[YUNIKORN-1330] Expose REST API's

What is this PR for?
Exposing REST API's to fetch the users and groups resource usage
What type of PR is it?

[ ] - Improvement

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1330
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

@wilfred-s Patch test coverage is good.


Visualization of Aruco markers in Rviz

Hallo there!!
Is there any way to see the /aruco_markers-visualization_msgs/Marker in Rviz??
How can we set the tf messages??
Thanks!!

Hi
Currently does not publish any tf. The pose messages can be visualized in rviz i belive.
Thanks

Hi thanks for the response
Yes I have tried and visualise in RViz the /aruco/pose msg but I was wondering if there
was a way to put-visualise marker position along with camera pose

I probably should improve the library a bit. Visuallization in RViz is really useful, and i should probably add TF to the markers.
Unfortunately currently i dont have any machine configured with ROS or even linux.


page deploy is failing with 5XX

We are trying to deploy to github pages via github action and it is failing with 5XX error.  Using GitHub enterprise server 3.8.3.
  - name: Deploy to GitHub Pages
        id: deployment
        uses: actions/deploy-pages@v1
        with:
          token: ${{ github.token }}

      - name: read deploy path
        run: |
          echo "${{steps.deployment.outputs.page_url}}"

Error we are getting:
Error: Request failed with status code 500
    at createError (/runner/_work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/axios/lib/core/createError.js:16:1)
    at settle (/runner/_work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/axios/lib/core/settle.js:17:1)
    at IncomingMessage.handleStreamEnd (/runner/_work/_actions/actions/deploy-pages/v1/webpack:/deploy-pages/node_modules/axios/lib/adapters/http.js:293:1)
    at IncomingMessage.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:13[45](https://org:repo/13:46):12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Error: Failed to create deployment (status: 500) with build version 534b03edbb340cd7891ab55799cded941a935f21. Server error, is githubstatus.com reporting a Pages outage? Please re-run the deployment at a later time.

It is most likely catching this : https://github.com/actions/deploy-pages/blob/main/src/internal/deployment.js#L125
Any pointer where it may be wrong ?

Hello, thanks for reaching out.
Hard to tell what the issue could be without a support bundle. Would you mind opening a support ticket here? We will want to look at service logs to understand the issue.

Please feel free to reopen with more information (or submit a support bundle) if you're still running into this issue. Thanks!


Highlighting across apostrophe not working

Example, query term "musks" not found in "Since the start of Elon Musk’s announcement"

This is fixed in 1.6

Confirmed
"body": "Elon Musk’s top lieutenant at Tesla ... is now working at SpaceX after leaving Tesla over a strange controversy. more… The post Elon Musk moves his top lieutenant at Tesla to SpaceX after a controversy appeared first on Electrek .",


Facet searching: facets arent returned when search query is only found in attachment content

Describe the bug
The code that the facet searching uses is setup to not search inside attachments
https://github.com/apereo/openEQUELLA/blob/e5ee7d72a2c42165a65eabc9fcc30cb1b61818ea/Source/Plugins/Core/com.equella.core/src/com/tle/core/freetext/index/ItemIndex.java#L704
Once that third variable is changed to true the facet search endpoint returns the correct data. But i'm not sure why it was configured to not search through attachments (maybe it's just a performance thing?)
An Edalex client found this while they were using the search facets on the new search page in 6.6, but this could affect anyone using the search/facet rest endpoint
To Reproduce
Steps to reproduce the behaviour:

Import the attached schema and collection
Collection Definition - TEST of wizard.zip
Charlie schema.zip
Contribute an item in the collection (with the name of 'animal'), and add animal talk.txt as an attachment
Publish the item
got to http://yourequella/yourinstitution/api/search/facet?nodes=%2Fitem%2Flom%2Fgeneral%2Ftitle&q=lamb&breadth=10&showall=false in your browser
(eg. https://rc.dev.edalex.com/charlie/api/search/facet?nodes=%2Fitem%2Flom%2Fgeneral%2Ftitle&q=lamb&breadth=10&showall=false )
No data will be returned

Expected behavior
The following JSON should have been returned
{
  "results": [
    {
      "term": "animal",
      "count": 1
    }
  ]
}

Platform:

OpenEquella Version: 6.6, 2018.2, 2019.1
OS: windows 10
Browser chrome

Since this fix touched code used by hierarchies we also need to do a quick sanity test of the hierarchy feature. Just make sure the counts for a hierarchy topic make sense

So I believe this has all been done and tested. As a result, maybe it's ready to close @mrblippy or @cathfitz ?


Add internal application for adding a new parameter to the sites collection in the DB

The application added in this PR should not really be used so I did not write much documentation for it nor added it to the tests.
Please review #343 first since the changes here are first include there.

Codecov Report

Merging #344 (535afa8) into master (0137ac6) will increase coverage by 0.08%.
The diff coverage is 78.33%.

@@            Coverage Diff             @@
##           master     #344      +/-   ##
==========================================
+ Coverage   76.82%   76.90%   +0.08%
==========================================
  Files          67       67
  Lines        6398     6447      +49
==========================================
+ Hits         4915     4958      +43
- Misses       1483     1489       +6

Impacted Files
Coverage Δ

simtools/db_handler.py
74.14% <64.86%> (-0.60%)
:arrow_down:

simtools/util/names.py
85.22% <100.00%> (+2.13%)
:arrow_up:

tests/unit_tests/test_db_handler.py
94.73% <100.00%> (+0.20%)
:arrow_up:

tests/unit_tests/utils/test_names.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

The new parameter causes sim_telarray to fail, so a quick fix is necessary for this, please wait with the review.

Fixed and all tests pass, can be reviewed


Fix parseIP error when parseIP before get AddressFamily

Signed-off-by: Tom Zhao<EMAIL_ADDRESS>Fix: https://github.com/docker/libnetwork/issues/2431

@icefed thanks for fixing this issue
thinking if something like this would be cleaner
initialize AddressFamily before the loop starts
s.AddressFamily = syscall.AF_INET

and when we receive s.AddressFamily we can recompute s.Address
                case ipvsDestAttrAddressFamily:
                       s.AddressFamily = native.Uint16(attr.Value)
                       // Recompute s.Address
                       fallthrough
		case ipvsSvcAttrAddress:
			ip, err := parseIP(attr.Value, s.AddressFamily)
			if err != nil {
				return nil, err
			}
			s.Address = ip

can we also add a test case for this, so we catch it, if its 100% reproducible

@icefed thanks for fixing this issue
thinking if something like this would be cleaner
initialize AddressFamily before the loop starts
s.AddressFamily = syscall.AF_INET

and when we receive s.AddressFamily we can recompute s.Address
                case ipvsDestAttrAddressFamily:
                       s.AddressFamily = native.Uint16(attr.Value)
                       // Recompute s.Address
                       fallthrough
		case ipvsSvcAttrAddress:
			ip, err := parseIP(attr.Value, s.AddressFamily)
			if err != nil {
				return nil, err
			}
			s.Address = ip

Hi @arkodg, ipvsSvcAttrAddress Value has 16 bytes, we can not use ipvsDestAttrAddressFamily Value(2 bytes) to recompute Address. So, it will not work.

LGTM, can we also add a test case please

Sorry for miss this, I will add test later.

hi @arkodg, I added tests for ipv6 and local passed, I don't know circleci: unit-tests failed.

@icefed can you please rebase to the latest master, I've taken care of the unit-tests regression by  reverting a commit

@arkodg looks like this was rebased; CI is green now


Override or add configuration options in values input

Changes:

Add ability to override or add configuration options in default values
Delegate Kubernetes namespace creation to helm provider from Kubernetes provider
Remove fake dependency variable in favor of terraform built-in module dependency
Bump default chart version to the 2.0.3

Breaking changes:

Removes fake dependency variable mod_dependency in favor of terraform built-in module dependency injection

Signed-off-by: Ondřej Šmalec<EMAIL_ADDRESS>

Tested against running cluster. Helm chart deployed and validated


More standard resolutions in bios for arm

Would be good to add more resolutions in bios settings. Would be more convenient install and use system without video driver installed.

This is no longer needed due to the added resolutions + dynamic resolutions in the latest VirtIO GPU driver. https://mac.getutm.app/support/


how to get worker id of app service plan

I'm using "azure-mgmt-web 0.32.0".
How can I get the worker pool id of an app service plan?
I cannot find the worker pool id attribute which is associated with an app service plan when I use the following function.
web_client = WebSiteManagementClient(credentials, subscription_id)
plan = web_client.app_service_plans.get(resource_group_name, app_service_plan_name)

Hi @nohyunho
@yugangw-msft , do you know?

Hi,
"App Service Plan"(from web_client.app_service_plans.get) has "worker_tier_name" attribute.
Azure SDK for Python Documentation explains for it as follows.

worker_tier_name (str) – Target worker tier assigned to the App Service plan.

I think that attribute is the worker pool id, but it has no value.(I have checked it using python code)
Is there another method for getting the worker pool id or is it bug?
Thanks for your kindness in advance.
yunho

Hi @lmazuel, @yugangw-msft
Please, could you answer my question?

@naveedaz, I think it's more a RestAPI question than a Python, can you tell us where to find this info in the Swagger file? (and we can translate to Python). Thanks!

Hi,
In Azure Portal, app service plan has "WorkerSizeId" attribute which means worker pool id.(I checked it using chrome devtools.) But, python SDK doesn't provide that information.
Could you check it ASAP?
Thanks.

Hi @nohyunho
I just created an issue in the RestAPI repo:
https://github.com/Azure/azure-rest-api-specs/issues/1241
This will help to understand where is the issue.

@nohyunho  Given the latest azure-mgmt-web is 6.1.0. Could you help to check if this is solved?


Feature Request: Support for multiple monitor development

Basically, it would be really helpful to be able to split the editor over multiple windows, but with the option to have the windows be "sticky", in that if you click into one, it'll bring the other windows to the top as well, if they're on another monitor. That should help prevent the potential issue of having a user opening screens that they already have open in other windows, but leaving it as an option to disable if they prefer.
Also having the option to pop the terminal section out would be handy for having more code real estate, especially for users that don't have massive monitors.
I'm also 100% willing to do work on this as well and contribute if pointed in the right direction.
Thanks.

How would this differ from https://github.com/microsoft/vscode/issues/10121 ?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[FEAT] Make an UPLOAD button

Making an upload button on the site such that the user can upload their own documents and start drawing on the same uploaded document.

Your idea sounds great @shravanibhor!
I'm assigning this issue to you, If you stuck in between using images with Canvas then please do refer this Documentation from MDN.

Oops! @shravanibhor, A similar existing ISSUE have been found #87.
This one is a duplicate, So I'm closing this ISSUE.
Thank you!


Cannot find Info.plist under build//Build/...

I upgraded my React-Native project from react-native 0.58.6 to 0.59.9 using rn-diff-purge. I encountered a lot of problems and solved all except one. The project builds successfully in XCode 10.2.1 and runs on iPhone X simulator. When I run react-native run-ios it builds successfully BUT doesn't run on simulator becuase it indicates that it can't find Info.plist under build/appname/Build/... .
Info.plist DOES exist under build/Build/... but somehow it searches it under the wrong folder.
I manually copied the 'Build' folder under 'build/appname/' and the app started to run on the simulator without any problem.
But I don't think copying these files manually is a correct solution so I want to understand why my project is checking the wrong folder and how can I fix this.
React Native version: 0.59.9

@armaneker Thanks for reports. I met this before and also can reproduce 100%.
Can you try to add these lines like below in cli package? I'll make a PR to cli.

Thanks @zhongwuzw !
This worked after I replaced 'DerivedData' with 'build'.


include schema in layer name

Currently only the table name is included

Oh I just saw that the schema isn't present in the list of layers on the landing page.  Should the schema names be included there too?
Demo for {schema}.{table}

yeah, I always felt that it was cleaner to have {schema}.{table}, and can't remember why we didn't do it directly cc @bitner

@vincentsarago I'm not sure that was ever an intentional decision


Add script for notebook instance metrics

Issue #, if available:
Description of changes:  Notebook Instances do not publish any metrics to CloudWatch unlike other components like Endpoints. This prevents us from observing any metrics and in turn creating alarms on those metrics.
Thus, here we use the Unified CloudWatch Agent to publish the metrics to Cloudwatch
Testing Done
(If adding a Lifecycle Configuration, please provide exact commands or steps to run on a Notebook Instance to validate)
To test this, update the wget command as below:
wget https://raw.githubusercontent.com/imujjwal96/amazon-sagemaker-notebook-instance-lifecycle-config-samples/metrics/scripts/publish-instance-metrics/amazon-cloudwatch-agent.json

[x] Notebook Instance created successfully with the Lifecycle Configuration
[x] Notebook Instance stopped and started successfully
[x] Documentation in the script around any network access requirements
[x] Documentation in the script around any IAM permission requirements
[ ] CLI commands used to validate functionality on the instance

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @jaipreet-s
I have made the requested changes. Please review them.


[FLINK-20547][network] Fix inconsistent availability issue of LocalBufferPool

What is the purpose of the change
LocalBufferPool#checkAvailability may return wrong availability state of LocalBufferPool which may lead to the set of inconsistent availability state when LocalBufferPool#setNumBuffers is called. This patch fixes the issue.
Brief change log

Fix wrong return value of LocalBufferPool#checkAvailability.

Verifying this change
This change added tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@pnowojski Thanks for the review and comments. I have updated the PR.


Enum support seems broken

I have following schema:
enum Title {
  DR,
  MR,
  MS,
  MRS
}

type Account {
  id: Int!
}

input SignupForAccountInput {
  title: Title!
}

type Mutation {
  signupForAccount(input: SignupForAccountInput!): Account!
}

When trying to make following request, it fails:
mutation {
  signupForAccount(input: {
    title: MR
  }) {
    id
  }
}

On this code:
  public Object invokeMethod(Method method, Object o, Object... args) {
    try {
      return method.invoke(o, args);
    } catch (IllegalArgumentException | InvocationTargetException | IllegalAccessException var5) {
      throw new RuntimeException("Error when executing the method '" + method.getName() + "' is missing in " + o.getClass().getName() + " class", var5);
    }
  }

The problem is args[0] is "MR", as string, and generated method is void setTitle(Title title). It seems that mapping isn't working correctly with enum type. Couldn't find anything in Issues or in SO, so creating a new one.

Hello,
As a first reaction, your request is invalid. You have a comma after MR.
It doesn't seem related to the thrown exception, but you never knows...  :)
Then, for input type, you should use prepared queries with Bind Variables.
For more information, you can search "bind parameter" in this page: https://graphql-maven-plugin-project.graphql-java-generator.com/client.html
Etienne

@etienne-sf thanks for the response!

Updated my example, this is not a real request I'm making, it's just rest of schema is irrelevant so I didn't post it
My report is about server mode, I'm making request from external client to server generated by graphql-maven-plugin, am I posting in wrong repo?

Hello,
I confirm the issue. Which is not a surprise for you, I guess.
It's solved, but I want to add proper integration test cases.
I'll deliver a new version, with this issue corrected, in a few days.
Etienne

Thanks a lot for looking into this!

Ok, I just released a new version.
It has taken some time, as I did some refactoring, to make this part of the code cleaner.
Please, tell me if it's Ok on your side.
Etienne


Build & Run Instructions

Can you please add build and run instructions to the README?

Issue closed as it is no longer relevant


Allow updating pom's named pom_parent.xml

During review of #6248, we noticed that Dependabot special cases the pom_parent.xml name as some trick to fetch parent poms. #6248 tries to preserve that, resulting in that with that PR, Dependabot can now update any pom names, except for pom_parent.xml.
We concluded that this "magic name" is not necessary. So this PR removes the magic and instead adds the pom_parent.xml to the list of "allowed names", so repositories like https://github.com/filip26/titanium-json-ld can now get updates.
I'm hesitant to add any specs over manual testing because those specs would be exercising a special case that should completely go way after we merge #6248, since that will allow any names.

We can always revert if we get a new bug reported because of this.

This change is causing duplicate PRs to sent. Previously, PRs only seemed to be sent for top level parent poms with the versions specified and other poms that relied on the version pins in those parents wouldn't get PRs. Now, all the poms are getting their own dependabot PRs updating the top level parent poms that contain the versions - whether they use the dependencies or not. I'll get an example up soon (hopefully) and file a bug as well.

Hei @jtgrohn, sorry about this. I did not expect duplicate PRs to be created after this change, and the testing I made did not indicate that would happen. Could you provide sample manifests or a test repo where this issue can be reproduced? Thank you!

@deivid-rodriguez Here's a repo that illustrates the issue: https://github.com/jtgrohn/maven-dependabot-test. Reproduction steps are in the README

Awesome, I'll have a look later.

I think https://github.com/dependabot/dependabot-core/pull/6557 should fix this!

I think https://github.com/dependabot/dependabot-core/pull/6557 should fix this!

I agree!
dependabot-core on  main [⇡!]
➜ gh pr checkout 6557
remote: Enumerating objects: 25, done.
remote: Counting objects: 100% (25/25), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 25 (delta 12), reused 23 (delta 12), pack-reused 0
Unpacking objects: 100% (25/25), 6.67 KiB | 379.00 KiB/s, done.
From github.com:dependabot/dependabot-core
 * [new branch]          deivid-rodriguez/dont-fetch-poms-outside-configured-dir -> origin/deivid-rodriguez/dont-fetch-poms-outside-configured-dir
M	nuget/spec/fixtures/nuspecs/Microsoft.Extensions.DependencyModel.nuspec
branch 'deivid-rodriguez/dont-fetch-poms-outside-configured-dir' set up to track 'origin/deivid-rodriguez/dont-fetch-poms-outside-configured-dir'.
Switched to a new branch 'deivid-rodriguez/dont-fetch-poms-outside-configured-dir'
No such plugin: ruby

dependabot-core on  deivid-rodriguez/dont-fetch-poms-outside-configured-dir [!] took 2s
➜ bin/docker-dev-shell maven
 > image dependabot/dependabot-core-development already exists
dependabot-core-development
[dependabot-core-dev] ~/dependabot-core $ bin/dry-run.rb maven jtgrohn/maven-dependabot-test
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/jtgrohn/maven-dependabot-test/
=> parsing dependency files
=> updating 1 dependencies: com.amazonaws:aws-java-sdk-core

=== com.amazonaws:aws-java-sdk-core (1.12.389)
 => checking for updates 1/1
🌍 --> GET https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/maven-metadata.xml
🌍 <-- 200 https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/maven-metadata.xml
🌍 --> HEAD https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/1.12.396/aws-java-sdk-core-1.12.396.jar
🌍 <-- 200 https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/1.12.396/aws-java-sdk-core-1.12.396.jar
 => latest available version is 1.12.396
 => latest allowed version is 1.12.396
 => requirements to unlock: own
 => requirements update strategy:
 => updating com.amazonaws:aws-java-sdk-core from 1.12.389 to 1.12.396

    ± pom.xml
    ~~~
    12c12
    <                 <version>1.12.389</version>
    ---
    >                 <version>1.12.396</version>
    ~~~
🌍 Total requests made: '2'
[dependabot-core-dev] ~/dependabot-core $ bin/dry-run.rb maven jtgrohn/maven-dependabot-test --dir /foo
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/jtgrohn/maven-dependabot-test/foo
=> parsing dependency files
=> updating 1 dependencies: com.amazonaws:aws-java-sdk-core

=== com.amazonaws:aws-java-sdk-core ()
 => checking for updates 1/1
🌍 --> GET https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/maven-metadata.xml
🌍 <-- 200 https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/maven-metadata.xml
🌍 --> HEAD https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/1.12.396/aws-java-sdk-core-1.12.396.jar
🌍 <-- 200 https://repo.maven.apache.org/maven2/com/amazonaws/aws-java-sdk-core/1.12.396/aws-java-sdk-core-1.12.396.jar
 => latest available version is 1.12.396
    (no update needed as it's already up-to-date)
🌍 Total requests made: '2'
[dependabot-core-dev] ~/dependabot-core $ bin/dry-run.rb maven jtgrohn/maven-dependabot-test --dir /bar
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/jtgrohn/maven-dependabot-test/bar
=> parsing dependency files
=> updating 0 dependencies:
🌍 Total requests made: '0'


Updating dopamine via the app causes it to change to a user install type in trollstore

This, for some reason, prevents jailbreak apps from displaying. manually fixed by changing dopamine back to a system install via troll store and after respringing the jailbreak apps re appear.

This, for some reason, prevents jailbreak apps from displaying. manually fixed by changing dopamine back to a system install via troll store and after respringing the jailbreak apps re appear.

yup im having this problem too.

that's normal and not really an issue, just stock iOS being shit.
just run refresh in persistence helper afterwards.