issue #31 upload CI

uploaded the YML containing the CI

@flippy1989 please add assignees as described in https://help.github.com/en/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users.
Also, link to the relevant issue as described in https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue.
Please also add more details to the PR description.

The change LGTM, but I will merge after you update the PR subject and description.

@flippy1989 Please verify the issues which are fixed by this PR are linked to the PR.

@flippy1989 to enable me to re-review your PR, please respond on my comments indicating if/how you've addresses the issues I've mentioned.

yes i ran the code on successful connection and on failed connection and
twice  i got the expected results
On Sun, Apr 26, 2020, 05:03 Barak Korren<EMAIL_ADDRESS>wrote:

@ifireball commented on this pull request.
In tests/test_connections.py
https://github.com/knowabli/groot/pull/41#discussion_r415190032:

@@ -0,0 +1,9 @@
+import urllib.request
+import pytest

+SITE_LOCATION = "http://localhost:5000"
+
+def test_connection():

assert urllib.request.urlopen(SITE_LOCATION).getcode() == 200

blank lines at the end of the file are usually flagged as errors by tools
like pyflakes or pep8, other ten that it now looks like the code would
work. Did you run it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/knowabli/groot/pull/41#pullrequestreview-400448648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJKHAT25NO65ICXOQHOOZA3ROOI7TANCNFSM4LVAKJ6Q
.


Update Explain.md

Added Several C Standards & Issues on certain functions

It would be better if difference between "merge", "squash and merge" and "rebase and merge" is also linked from Github Documentation. This usually causes confusion for beginners while learning Git.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges


[cudaaligner] Mismatch in formatted alignment when running sample

Steps to reproduce:

Fetch pull request #219 changes.
Build CGA and run 'sample_cudaaligner -p'
The pairing string does not correspond to the query & target strings.

@tijyojwad reported that when setting query length to 50 and target length to 60 in the sample, then alignments come out fine. But when increasing those to 100 and 110 respectively, then the issue arises.

Hotfix merged into master and dev branches, and offending changes reverted. Closing since the multi-warp myers (which caused the bug) is being dropped in favor of banded implementation which will make up for the performance impact of the reversion.


Problem selecting payment methods

Steps to reproduce the behavior
Use external page option (because too many problems in the embed form).
• Select Credit card payment method
• Then select Paypal
• Then click on "Checkout"
• You are redirect to the Credit card landing page instead of Paypal...
Environment
PrestaShop version: <IP_ADDRESS>
Mollie module version: 4.4.3
PHP version: 7.1.26

Hi there, Anatole, how are you doing today?
Our team is already looking into this issue, we truly appreciate the following notes as well. We will keep you updated about the progress!
Thank you for your patience, and understanding.
Best regards,
Invertus Support team

Hi there, @AnatoleRozan!
Our team has checked the issue, and they have not been able to replicate it on their side. Could you share screenshots or screen recordings of the issue?
It would help us to replicate it and proceed with further investigation.
I will be looking forward to your reply.
Best regards,
Invertus Support team

Hi there @AnatoleRozan,
Our developer checked the video, but we are unable to replicate the issue. In order to resolve this, could you please provide your BO+FTP credentials to<EMAIL_ADDRESS>We will be able to investigate it further.
I will be looking forward to your reply!
Best regards,
Invertus Support team

Hi @AnatoleRozan,
Let us know once you're ready to continue with this!
For now, we will mark this issue as resolved.
--
Best regards,
Invertus Support team


Update search model to include the extra fields for Release Calendar

What
This is to update the search model to include the extra fields for the release calendar feature.
How to review
See if the changes make sense.
Who can review
Anyone except me.

Hi @rahulPalliyalil adding a general comment here: There is an attribute missing which will be needed by the releasecalendar work. This was originally agreed with Nathan as a boolean 'census' attribute, but I think it has got lost somewhere along the way. However its type has now been changed so what we need is: Zebedee will have a 'survey' attribute in it's page description for a Release. This is a string value (which is really an enumerated value), which will need to be indexed. As an enumerated value its string value does not need to be analysed, but it does need to be indexed for search purposes, and needs to be available in _source, i.e. is returned as a value in the description. Apologies if this is not clear - we can have a catchup about it you need clarification

So as discussed, leaving this as it is till the decision is made to use the survey attribute. Will update the ticket accordingly.


Highlighting breaks on delete+undo in rapid succession

tldr:

Revision 66ec6bd.

Do you have "rust-analyzer.highlighting.semanticTokens": true,? That enabels the new, completely unrelated highlighting implemenation

Do you have "rust-analyzer.highlighting.semanticTokens": true,? That enabels the new, completely unrelated highlighting implemenation

No, I haven't enabled it yet, since it forces me to start RA in a specific way, i.e. simply clicking a tick box in the settings does not work.
By the way, previously types useses in code were highlighted in the same manner as type declarations (cyan-ish green). Now only system types are highlighted that way for me, others remain white. Is this related to refactoring in the highlighting system?

Probably yeah: some tag names changed, and the old mapping was not updated

I've filed an issue https://github.com/rust-analyzer/rust-analyzer/issues/3455

@matklad, actually I've just enabled new proposed API for semantic highlighting and it still does not highlight types for me. Honestly, I couldn't even say what syntax elements were highlighted by RA and what came just from the color theme (default Dark+ with tweaked editor .background and .foreground colors):

@0x7CFE the old implementation is gone, and we should have plenty of colors now:

Please file a new issue if you still have problems.


Incomplete Code

Describe the bug
The code is written to the file and then right before it completes, it's erased to about 1/2 of its desired length.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-mmnszj
Steps to reproduce
Edit the inventory.tsx file.
Claude/Bolt outputs code.
Claude/Bold deletes half of the code.
Expected behavior
I've already described what's happening and what's expected. Full code output is being erased to half-code output with AI-side deletion.
Screen Recording / Screenshot
No response
Platform
Browser name = Firefox
Full version = 129.0
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0
performance.memory = undefined
Username = oakunion
Chat ID = 2beb59ba405d

Additional context
No response

I'm having the same issue today. I refreshed, thinking that might help, and half of the files are missing, along with previous chats in the past. I'm not too pleased with all the lost progress.

This is pretty frustrating indeed!
We're tracking this internally. You can follow https://github.com/stackblitz/bolt.new/issues/124 to get notified when we've resolved this issue.


Using MockClient.make crashes trying to encode request schema

I'm using effect-http to model an external Api that I'm calling using Client.make (which is a really cool feature!) and it works great.  But now I want to generate a mock client to write some tests with, so I've got
const AnimalAdapterClientTest = Layer.succeed(AnimalAdapterClient, MockClient.make(animalAdapterApi))

And I get an error at startup:
/Users/bste/ghq/gitlab.com/ezyvet/application/hypr/launchpad/node_modules/.pnpm/@effect+schema@0.53.1_effect@2.0.0-next.60_fast-check@3.14.0/node_modules/@effect/schema/src/Parser.ts:273
  switch (ast._tag) {
              ^
TypeError: Cannot read properties of undefined (reading '_tag')

I've had a dig through the code and it looks like in effect-http/internal/utils when we check if the request params schemas is IgnoredSchemaId the test returns false so we try to call Schema.encode.
Printing the requestSchemas to the console from the utils file, I can see params is set to Symbol(effect-http/ignore-schema-id)
{
  query: SchemaImpl {
    ast: {
      _tag: 'TypeLiteral',
      propertySignatures: [Array],
      indexSignatures: [],
      annotations: {}
    },
    [Symbol(@effect/schema/Schema)]: { From: [Function: From], To: [Function: To] }
  },
  params: Symbol(effect-http/ignore-schema-id),
  body: Symbol(effect-http/ignore-schema-id),
  headers: SchemaImpl {
    ast: {
      _tag: 'TypeLiteral',
      propertySignatures: [Array],
      indexSignatures: [],
      annotations: {}
    },
    [Symbol(@effect/schema/Schema)]: { From: [Function: From], To: [Function: To] }
  }
}

Logging out the whole imported Api object shows that IgnoredSchemaId looks fine:
[Object: null prototype] {
  default: {
    ApiGroupTypeId: Symbol(effect-http/Api/ApiGroupTypeId),
    ApiTypeId: Symbol(effect-http/Api/ApiTypeId),
    FormData: SchemaImpl {
      ast: [Object],
      [Symbol(@effect/schema/Schema)]: [Object]
    },
    IgnoredSchemaId: Symbol(effect-http/ignore-schema-id),
    ...
  }
}

but if I print out the field with console.log(Api__namespace.IgnoredSchemaId) then I get undefined.
I'm not too sure what to check next.
Versions of packages are:
effect: 2.0.0-next.60
effect-http: ^0.45.1
@effect/platform-node: ^0.37.6
@effect/schema: ^0.53.1

Hey, thanks for the report. Could you please update to 0.45.2 and try again? The mock client implementation still used a legacy version of the request encoding, I updated it to use the same as used for the real client.

Works like a charm, thanks for the quick fix! :)


SDK Support of new IUDX APIs

Does it support

async search?
subscription based data consumption?
Files download/upload
gis apis
catalogue nlp apis
ratings apis

We should be having docs of using python sdk to build apps using IUDX platform in developer docs https://docs.iudx.org.in/


Prevent serialization errors in SKVRecord

SKVRecord should have a serialization cursor that prevents re-serializing fields, which could break the storage payload

Currently the fieldCursor variable of the SKVRecord is used for both serialization and deserialization. There should be a separate serialization cursor that tracks which field has been serialized last, in order to prevent errors when the user could be both serializing and deserializing from the same SKVRecord. (src/k2/dto/SKVRecord.h .cpp)

The record write path in k23si_client.h should use the serialization cursor to verify that all fields have been serialized


PostgreSQL connector

[x] ReadFile
[x] WriteFile
[x] ManageFile
[x] QueryFile
[ ] Planner
[ ] integration tests
[ ] demoable environment

How about splitting the Planner point? Like:
[] Shifted Read
[] Core Planner (Map)
[] MapFuncCore  (Basic)
[] Sort
[] Filter
[] Join
[] Reduce
[] MapFuncCore (remaining)
I'm not sure what else :)


Feature/jwt token authentication

New feature implementation
Implemented feature

Implementation description
There were too many unsigned commits in this pr https://github.com/open-rmf/rmf_visualization/pull/9
Refer to it for the discussions
This is an identical pr with commits cherry-picked and signed from the other pr.
Design doc:

Yup, it's the same pr


cmd/go: go.work: go build requires versioned replace directive when replacing a used module with a local path

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

$ go version
go version go1.18.5 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
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/mlaventure/.cache/go-build"
GOENV="/home/mlaventure/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/mlaventure/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/mlaventure/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.5"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/mlaventure/tmp/go/workspace/realdeal/go.mod"
GOWORK="/home/mlaventure/tmp/go/workspace/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2178506260=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Given the following workspace structure:
~/tmp/go/workspace $ tree
.
├── fubar
│   ├── fubar.go
│   └── go.mod
├── go.work
└── realdeal
    ├── go.mod
    ├── realdeal
    └── realdeal.go

2 directories, 6 files

With the following go.work:
~/tmp/go/workspace $ cat go.work
go 1.18

use ./fubar
use ./realdeal

replace github.com/foo/fubar   => ./fubar

Build realdeal which depends on fubar:
~/tmp/go/workspace/realdeal $ go build .

What did you expect to see?
Nothing, the build should succeed
What did you see instead?
go: workspace module github.com/foo/fubar is replaced at all versions in the go.work file. To fix, remove the replacement from the go.work file or specify the version at which to replace the module.

Found workaround
The only way I've found to fix this is to update the go.work to be as follow:
~/tmp/go/workspace $ cat go.work
go 1.18

use ./fubar
use ./realdeal

replace github.com/foo/fubar v0.0.0-00010101000000-000000000000 => ./fubar

This is not needed if a workspace is not used. It also seems to contradict the example from the documentation (https://go.dev/ref/mod#workspaces):
replace (
    golang.org/x/net v1.2.3 => example.com/fork/net v1.4.5
    golang.org/x/net => example.com/fork/net v1.4.5
    golang.org/x/net v1.2.3 => ./fork/net
    golang.org/x/net => ./fork/net
)

CC @bcmills, @matloob.

replace modules also cause problems with go mod tidy
go: downloading mydomain.com/module v0.0.0-00010101000000-000000000000
github.com/acct/testcmd imports
        mydomain.com/module: unrecognized import path "mydomain.com/module": https fetch: Get "https://mydomain.com/module?go-get=1": ...

@dmitshur @bcmills  Is there any progress in this? I also have similar problem, when I trying to migrate existing project to use go workspace. It seems replace in go.work is not available to me too. I cannot run go mod tidy

Same problem for me.
I presume this could be getting caused by the fact that I'm specifying the same local module in the use directive as in the replace directive, which I suspect is not intended behavior, but considering Go keeps trying to remotely fetch workspace modules during build rather than respecting the go.work, I was hoping the replace would solve the situation.
Frankly I'm surprised, most of the go tooling is generally high quality, but go.work seems quite error prone...

In general we would expect modules that are included in a workspace to not also require a replace directive in the go.work file. Can you explain more about the circumstance that led you to that arrangement?

The reason I was looking to do this was to handle an environment where I cannot directly connect to the upstream git repo. I'm seeing go execute git ls-remote -q origin ... (which fails in my environment) for the modules referenced with use but not with replace.
I can remove the use and only have a replace, which works, but only for libraries where I'm not running a go build.

don't know where you came up w/ that long versioning string, fyi: v0.0.0 also works to satisfy go work complaints.
use ./cmd/fubar
replace github.com/foo/fubar v0.0.0 => ./cmd/fubar

it should automatically resolve your remote module github.com/foo/fubar to the local version available at ./cmd/fubar.

It appears to do that by running git ls-remote -q origin ... which requires access to the remote git server.

@bcmills Please check this issue. I think it's related.
https://github.com/golang/go/issues/50750
go.work should support replace, when we think about monorepo situation. Placing replace on all of the modules of microservices in a monorepo is not ideal case i think.

I am having the same problems in 1.19.  Once I put in go.work everything goes haywire.

Replace works in go.mod but can cause problems elsewhere in the workspace (Goland Issues suggestions to create a workspace)
go.work - using use block causes go work sync to issue errors about missing versions for modules in the use clause.   Using the long version number, a new number, or using v.0.0.0 will still generate the same errors
Replace in go.work sort of solves some problems but the versioning issue remains if any module is an indirect requirement in another module.

Thinking about trying the latest go to see if the behavior changes.

The reason I was looking to do this was to handle an environment where I cannot directly connect to the upstream git repo. I'm seeing go execute git ls-remote -q origin ... (which fails in my environment) for the modules referenced with use but not with replace.

As said above, since the beginning of go workspaces, and at least up to current Go 1.21.5 ;
Tree structure :
./module-a/go.mod
./module-a/module-a.go

./main-project/go.mod
./main-project/main.go
./main-project/go.work

CONTENT of module-A (no dependencies) :
$ cat module-a/go.mod
module gitlab.unpublished.private/modules/module-a.git

go 1.21.5
----8<----8<----8<----8<----8<----8<----8<----8<----8<
$ cat module-a/module-a.go
package module_a

import "fmt"

func ModuleA() {
	fmt.Println("ModuleA()")
}

CONTENT of mains-project (depends on moduleA) :
$ cat main-project/go.mod
module main-project

go 1.21.5

require (
	gitlab.unpublished.private/modules/module-a.git v0.9.9
)
----8<----8<----8<----8<----8<----8<----8<----8<----8<
$ cat main-project/main.go
package main

import "fmt"
import "gitlab.unpublished.private/modules/module-a.git"

func main() {
	fmt.Println("main project")
	module_a.ModuleA()
}
$ cat main-project/go.work
----8<----8<----8<----8<----8<----8<----8<----8<----8<
go 1.21.5

use (
	.
	../module-a
)

So, they are manually-crafted files, and the repos/gitlab doesn't event exists, go.mod.sum are missing, the v0.9.9 doesn't really exists, etc etc... but it reflects the SAME PROBLEM than really existing private git-cloned repos.
Inside ./main-project/, upon try to go build -v or go run -v, I encounter :
$ go build -v .
# cd /Users/folays/go/pkg/mod; git ls-remote https://gitlab.unpublished.private/modules/module-a
fatal: unable to access 'https://gitlab.unpublished.private/modules/module-a/': Could not resolve host: gitlab.unpublished.private
# cd /Users/folays/go/pkg/mod; git ls-remote git+ssh://gitlab.unpublished.private/modules/module-a
ssh: Could not resolve hostname gitlab.unpublished.private: nodename nor servname provided, or not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
# cd /Users/folays/go/pkg/mod; git ls-remote ssh://gitlab.unpublished.private/modules/module-a
ssh: Could not resolve hostname gitlab.unpublished.private: nodename nor servname provided, or not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

So the full text above is not really interesting. The MAIN POINT is that go it trying to git ls-remote unjoignable repos, which in real scenarios, I would myself git clone with my own means, and which I would only be able to git pull / push with my own means.
I would also like to specify, in aim to alleviate unneedy discussions, that for a real scenarios, my $HOME/.gitconfig would alias insteadOf = https://gitlab.unpublished.private/ to [url<EMAIL_ADDRESS>So, for the described scenario above, using only go.work's use ../PATH-to-immediate-dependency, Go WILL NOT build the main module, because it wants to git ls-remote the dep.
This WONT happen for even-dummy-er testbed scenarios where you would omit this from main-project/go.mod :
require (
	gitlab.unpublished.private/modules/module-a.git v0.9.9
)

Indeed, if you only use local-only never-git-pushed tagless/unversionned dependencies, the problem would not occur.
If for some reasons (which seems valid to me), your main-project has go.mod containing requiring versioned dependencies (because, from time to time, you want to publish a new version of main-project to your org), then only using use ../PATH directives from go.work without replace directives won't work at all.
----8<----8<----8<----8<----8<----8<----8<----8<
I severely miss a simple method to having this workflow working seamlessly :

fetch all org-private Go modules for which I may want to modify some of their code

some of them having dependencies on some others

fetch the org-private main-project which is use those dependencies
having anybody able to just go get https://org-private/url/to/the/main-project.git
having a local, private git-uncommited go.work which would just use . and use ../EACH/DEPENDENCIES and use ../EACH/SUBDEPENDENCIES

I mean, all the above works seamlessly, except for me, the dev, which needs to constantly jungle with some go.work, use, and replace directives.
This just doesn't work seamlessly, go.work use ../each-dependency does not suffice, I need to add replace everywhere, and when I finally want to commit everything I may have modified, I have to JUNGLE BACK to remove those replace directive for making the tools able to find and fill the go.mod files with coherent requires ... vVERSION before git push'ing everything.
----8<----8<----8<----8<----8<----8<----8<----8<
To me, it feels like the go.work stuff has been made with a majority of its usage being in spirit of using a "monorepo", but there is lot of juggling needing to be done to use it in a lot of cases.
Googling around on "go.work", "git ls-remote", "use", "ignored", "without replace", etc... yields a lot of results of confused people which seems to have a bad time figuring out a workflow which would suits to them.
I would just like a simple way to :

locally fetch (OUTSIDE of Go handling) every go repos I may be willing to modify locally (on which I have authority to git push),
have Go finds them the local directories to where I fetched them, with go.work
being able to LOCALLY git-commit new versioned versions of dependencies which I modify
being able to LOCALLY git-commit a new version of the main project, using the modified dependencies, WITHOUT FORCING ME beforehand to push the deps, WITHOUT TRYING to git ls-remote them at any time, since they are ALL POINTED BY go work's use directives
when I'm satisfied on all the work done locally, I myself git push everything to the remote (sub dependencies, dependencies, main project).

That's just hard in Go, having to constantly jungle with replaces directives.
I cannot seem to have a fixed-once-figured-out-do-not-constantly-modify-replaces set of go.mod/go.work files where I would just git clone everything I need, modify my .go files locally, then update the dependencies in go.mod, and git push everything.
No, Go is willing to git ls-remote constantly, OR requires me to have some replace directives in go.* files, which then would prevent go.mod to contains coherent requires DEPENDENCY vVERSION versions, which would make those go.mod (and the whole project/dependencies) unpublishable without first juggling with the go.* directives, to make the Go tool produce coherent go.mod vVERSION requires.

I'd like to chime in too with the same issue and an additional potential bug (not sure if I should open a separate issue for that though). I felt it's most appropriate in this issue, but it's certainly also related to #50750 .
FTR we're using Go 1.21.
In our monorepo we gitignored go.work until recently. We made the switch because updating a dependent module was very cumbersome.
Imagine the following repo structure:
.
├── go.work                     # gitignored so just local
├── lib
│   ├── go.mod
│   └── lib.go
├── moduletwo               # depends on lib
│   ├── go.mod
│   └── moduletwo.go
├── README.md
└── test
    └── moduleone           # depends on lib
        ├── go.mod
        └── moduleone.go

A local Go workspace enabled us to efficiently make updates to multiple modules in one change and test them without having to update versions. Push to CI/CD however, requires an update to the versions (e.g. if module lib has an update the other modules depending on it need an updated version). This requires a separate commit just to update the revision in go.mod and making sure we don't need to rebase after that, since otherwise commit hashes change.
To avoid this, we decided to add go.work (not go.work.sum) to the repo. This seems to work only in some cases. In one module we encountered issues like these:
# linux CI runner
cmd/cmd.go:9:2<EMAIL_ADDRESS>invalid version: unknown revision 9ed56a5b95df

# windows CI runner
path\cli\root.go:26:2<EMAIL_ADDRESS>invalid version: git ls-remote -q origin in C:\Windows\system32\config\systemprofile\go\pkg\mod\cache\vcs\927cbc5a0bf57c000feeddfdd18d1586382b2a626237337481dc6f6b33425a3a: exit status 128:
	Unhandled Exception: System.ComponentModel.Win32Exception: The directory name is invalid

Removing go.work for this change in CI fixed the issue.
To get around this I tried to use replace directives just as outlined in this issue. A commited go.work plus each go.mod containing replace directives to replace the modules in the same folder structure with one above.
Repository with demo: https://github.com/mweibel/gomodreplace/tree/fail (please note, this is only a partial reproduction because we have an additional issue in our monorepo due to the fact that we are on an on-premise GitLab instance without a go module proxy in front).
The issue with this approach is visible when running go vet ./...:
$ go vet ./...
conflicting replacements found for<EMAIL_ADDRESS>in workspace modules defined by /tmp/gomodreplace/moduletwo/go.mod and /tmp/gomodreplace/test/moduleone/go.mod

Because moduletwo replaces lib as ../lib and moduleone replaces lib as ../../lib, go vet errors.
"Fixed" monorepo structure in main branch: https://github.com/mweibel/gomodreplace
This works because both moduleone and moduletwo replace lib in the same way.
I certainly might be doing something wrong and would love to get some help/documentation if that's the case.
Thank you!

There are a couple of solutions we could consider here:

We could allow the replace directive as long as it names the same directory as what is in the use directive, so that the workspace module is “replaced with itself” but all prior versions are also replaced with what is in the workspace (so replace github.com/foo/fubar => ./fubar is allowed but must be a no-op).
We could define that wildcard replace directives don't apply to the version of the module that is injected via the workspace (so replace github.com/foo/fubar => ./fubar is allowed but does not apply to the workspace module).

Truly, this behavior makes go.work useless in a mono repo, and contradicts the documentation.  Spent half the day trying to use the feature as documented, and getting progressively more frustrated.  Found this thread and realized I should just abandon the effort, and go back to a maze of replace directives in the individual modules.
Could we at least ask for something in the documentation that clarifies what's required to make workspaces functional?  That is to say, at least describe the behavior as it is to save this kind of frustration for others?

@rselph-tibco Could you clarify what part of the documentation is inaccurate? I'd like to correct it to clarify that this isn't supported. Workspaces were not built to support modules that can't be built outside a workspace context.

@rselph-tibco Okay, I can see a documentation problem: we should more clearly document that a workspace module can not be replaced using a replace directive in a go.work file (replacing at specific versions is supported for the purposes of tweaking the dependency graph, but should almost never need to be used. blanket replaces that apply to all versions are explicitly disallowed). The reason for this is that it's not clear what the behavior should be if a workspace module (which is at the root at the module graph) is replaced with a different module. (There is an analogue to this in single module mode: There is also weird behavior in a single-module context if that module replaces itself. We don't report an error in that case but we probably should.)
So I can add a line to the modules reference explicitly clarifying that workspaces can not be replaced using wildcard replaces.
But I don't think that solves your core problem: "handling [modules] reasonably in more complex situations such as a mono-repo". I might still be misunderstanding this, so bear with me, but it seems to me that the main case I've seen in this bug for replacing a workspace module in a go.work file is to circumvent fetching the module when it appears as a dependency of other workspace modules. My understanding of when this would happen (please correct me if I'm wrong here) is because the module is not able to be fetched either using git or a local module proxy. If that is the case the module would not be buildable outside of a workspace context (unless it replaces all of its dependencies!). Does that sound right to you?

One use case I have—which I think is similar to the one @rselph-tibco described—is when I have a series of modules that depend on each other, and I want to test a change to a module and those that depend on it locally, before pushing everything to a central Git server.
It'd be useful in that case to check out the module and a handful of packages that depend on it into a "workspace," and enforce that everything in that workspace should always use the local copy, without having to edit X individual go.mod files.
Using the present system, I've missed a file when adding my replace directives, and wondered why my change seemingly had no effect.  I've also frequently forgotten to remove the temporary "replace" directive before pushing up my changes.  Having a mechanism (go.work replace or otherwise) that took precedence over go.mod would make this workflow much easier and less error-prone.

@dpifke After you push your modules to a central git server, is it possible to build the modules individually outside of a workspace? That is, are the modules able to be downloaded from git or a private proxy? If so, then your use case falls squarely under the set of use cases that go.work is meant to support. Your workspace should work without needing to replace any of the workspace modules. If the modules do work individually after pushing your changes, but you still need replace directives I'd like to know what issues you're running into.

My point is that I want  go.work to work before I push my changes to the central Git server.
I want to use workspaces as follows::

I have workspace1 with a fix for bug1 in my module, which has been submitted as a PR to Github.  There's a lengthy and contentious PR review, and I want to start working on a fix for bug2 in parallel.
I create a new workspace2, and do some local development which can't be merged until after the fix for bug1 lands.
I want to ensure the bug2 fix doesn't break any of a handful of downstream modules that import my package, possibly indirectly.
Right now, that means downloading each downstream module and editing its go.mod to point at my module in workspace2, then running its test suite.
I'd prefer to just download the downstream users of my module into workspace2, and have go.work handle the replacement for me—no copying-and-pasting of replace clauses into a bunch of separate go.mod files individually.

Maybe the fix for bug2 is experimental, and if it turns out to break downstream users, I plan to go back to the drawing board.  In that case, I don't want it to ever be published in Git at all, because someone might accidentally pick a rejected work-in-progress!

@dpifke If I understand your use case directly it should work. What doesn't work is replacing the workspace modules (the modules that are used in your workspace, but you shouldn't need to do that.


Fix typo in UART Arduino IOP

Fixed bug and created PR for the issue discussed here:
URGENT: UART Arduino IOP - Typos & help fixing it
https://groups.google.com/forum/#!topic/pynq_project/rgXq6egbmuI

@shohei  Thanks for this PR. However, the 2 files need more changes, and the bsp for arduino has to be updated. I will close this PR and reopen a different PR.


Can't import Bestiary 3 - Pig (Familiar)

Can't import statblock:
Pig (Familiar)      CR 1/3
XP 135
Male pig (Pathfinder RPG Ultimate Magic 113)
N Small animal
Init +1; Senses low-light vision, scent; Perception +5
Defense
AC 13, touch 12, flat-footed 12 (+1 Dex, +1 natural, +1 size)
hp 6 (1d8+2)
Fort +6, Ref +3, Will +1
Offense
Speed 30 ft.
Melee bite +1 (1d4)
Statistics
Str 11, Dex 12, Con 15, Int 2, Wis 13, Cha 4
Base Atk +0; CMB -1; CMD 10 (14 vs. trip)
Feats Great Fortitude
Skills Perception +5
Ecology
Environment any
Organization solitary, pair, or herd (3-12)
Treasure none
Special Abilities
Low-Light Vision See twice as far as a human in dim light, distinguishing color and detail.
Scent (Ex) Detect opponents within 15+ ft. by sense of smell.

Used your latest module that was available as of this afternoon at about 2:30pm.  I used Hero Lab to produce this statblock. For greater accuracy, you might want to use one of the online resources. Hero Lab can truncate some of the text. All the other statblocks from Bestiary 3 imported -- a total of more than 86% imported!


cannot reproduce results on PACS

I run your code on PACS to reproduce your results in Table 6. I run three times, the results are:

Best val 0.965909, corresponding test 0.68847 - best test: 0.787732, best epoch: 18

Best val 0.967532, corresponding test 0.771698 - best test: 0.782642, best epoch: 25

Best val 0.962662, corresponding test 0.750573 - best test: 0.780606, best epoch: 17

The average result is 73.69, which is significantly lower than your results (80.85) in Table 6 for Res18.
I guess I may be wrong somewhere. How to reproduce results?
My environment is:

pytorch=1.1.0, torchvision=0.3.0.

If I do not use ImageNet pretrain model, I run the code for three times, the results are:

Best val 0.683442, corresponding test 0.443879 - best test: 0.471367, best epoch: 26

Best val 0.683442, corresponding test 0.370832 - best test: 0.404174, best epoch: 28

Best val 0.678571, corresponding test 0.382795 - best test: 0.484856, best epoch: 28

I am looking forward to your reply.

Hi, could you run the code using my latest environment? please see #2
If you want to train your network without pretrained model, you may need other techniques which are not in the scope of this paper.


Create a compatibility layer to handle older hive metastores

Version 2.2.0 of hive metastore client worked with a wide range of server versions, but we have to upgrade it for java 11 support. Hence we add a compatibility library which proxies a number of calls to achieve compatibility with older versions.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10901/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10902/
Test PASSed.

@gpang PTAL. Tested this on metastore 2.2 and 2.3, with java 11 as well.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10908/
Test PASSed.

@gpang PTAL, comments addressed

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10914/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10916/
Test PASSed.

alluxio-bot, merge this please


Bump main dependencies

Bumps

@deck.gl/* (8.9.6)
@emotion/*
@mui/*

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1950

Relevant Lines:
2514

💛  - Coveralls


redraw of scrolling text inside GNU screen w/ caption is horribly slow

Please fill out the below information:
Version 1809 (OS Build 17763.195)

Summary
I updated to win10 ver 1809 today (previously ran 1803), and one of the first things i noticed is that when within using GNU screen the redraw is noticeably slower, when using caption value in .screenrc.

Environment
Here's the contents of an example $HOME/.screenrc:

caption always '%{= kw}[ %{y}%H%{-} ][ %= %-Lw%{+b M}%n%f* %t%{-}%+LW %= ][ %{r}%l%{-} ][ %{c}%c%{-} ]'

This is a pretty basic setting for screen to draw a floating "status bar" on the bottom showing what screen is selected, and is discussed on https://lizdenys.com/journal/articles/understanding-gnu-screens-captions.html
After i updated to 1809, i noticed that when launching GNU screen from within WSL (triggered via bash.exe), and doing something that requires the screen to re-draw scrolling text, the refresh rate is pretty slow (e.g. doing something like ls -l /usr/bin takes several seconds instead of being near instance when not using that setting in screen.
I've also tried resetting my environment entirely (wiping out all bash shell settings files e.g. $HOME/.bashrc and $HOME/.bash_profile).  I narrowed it down to that captions always line being the culprit.  I was first noticed how painful running ps auxwww was on a remote linux system :-(

What you're doing and what's happening:
generating output that exceeds the size of the window, resulting in scrolling behaviour.  the redraw of the text from scrolling, results in a rate that makes me think i'm back on my first 486 computer

$ echo "caption always '%{= kw}[ %{y}%H%{-} ][ %= %-Lw%{+b M}%n%f* %t%{-}%+LW %= ][ %{r}%l%{-} ][ %{c}%c%{-} ]'" > .screenrc
$ screen
[... inside new screen ...]
$ ls -l /usr/bin

What's wrong / what should be happening instead:
time to perform a simple "dir" (via ls -l /usr/bin) takes ~20 seconds inside GNU screen

this same listing takes only a second and a half when not using GNU screen at all (or not using that captions always line in $HOME/.screenrc) .
whether or not using a screen multiplexer like GNU screen should not affect the refresh time, at least it didn't before i upgraded to win10 ver 1809 today.

Strace of the failing command, if applicable:
not applicable, running the ls comand using time reports nearly identical values:

outside of screen:
real    0m1.240s
user    0m0.016s
sys     0m0.063s

inside screen:
real    0m0.069s
user    0m0.000s
sys     0m0.063s

Which makes it seem that the comand isn't what's running any slower (in fact it reports it ran faster?) but the drawing the scrolling text is what's in-fact impacted.

Wrong GitHub, you want to file with Console: https://github.com/Microsoft/Console/issues/

#2772


PaginatedDataTable should support zoomable.

When I look at the data in a PaginatedDataTable, it is difficult to see all the content. So, I want to be able to zoom in and out of the PaginatedDataTable. Case of DataTable, I can do it because it has a defined width and height but PaginatedDataTable is built differently and I cannot intervene further.
Thanks for your attention!

@svsno1
Can you provide  a sample use case showing the issue and a proposal as what would you like to add to the widget which will help to resolve your issue ?
Thanks.


Brush up Azarim and effect

I assume the +2 potency is included in the effect that can be applied to another weapon at level 11?


Post release automated changes for compute releases

Post release automated changes for azure-arm-compute

/check-enforcer override

/check-enforcer evaluate


Make result map downloadable

 Issue by dleehr
Thursday Mar 06, 2014 at 20:33 GMT
Originally opened as https://github.com/NESCent/dplace/issues/45

Preferrably export as vector image.  Initially will see what's possible with OpenLayers, and may investigate other providers if needed

 Comment by stefelisabeth
Saturday Nov 01, 2014 at 13:26 GMT

I can do this if the map is still going to be SVG, since I've already done this for the trees.

 Comment by dleehr
Monday Nov 03, 2014 at 14:11 GMT

Yeah, this issue was created long before switching to jVectorMap (SVG) maps, so I didn't know how the download would work. Now that the maps are SVG, it should be similar to what you've done for the trees.

Done


[Feature Request] Change database store engine to InnoDB

Need to change database store engine MyISAM to InnoDB for default installation.
Benefits: Support foreign keys and will better for safe data store.

Closed by PR #80


Added quicksort in cpp

Implemented the quicksort in the cpp

Fixed the issue

Thanks for your contribution!

PR has been merged under Hacktoberfest!

Happy contribution!


Add collection of internet points

new optional features
opt-in
Must not allow tracking

Alternatively, any risks must be documented and communicated to users

Increment some number on each report
Add /report to see number of points

Absolute number of reports
Tell in which percentile of reporters the user is

AC:
-Add new / endpoint to opt in to point collection
- On call without argument explains risks to user
- On call + add adds user ID to DB with "0" in collected
- On recall + delete removes user from that DB
- Add endpoint where number of points can be seen
- same endpoint, but once opted in

Add new DB

userid + number of reports

Add new logic to add reports on

Should be relatively straightforward

Add new changelog message

Implemented in 1.2.0


How to update correctly?

I am trying to update a boolean value "archiviert" of a record by clicking on a button. I tried to follow the docs; please see my minimal example below. PostgREST backend is updating properly, but the returned data is not put into data. As far as I understand supabase-cache-helpers, it should be updated automatically by matching cache keys? I also tried to wrap update()-call with mutate()-call. Then it is reflecting changes in data, but it's fetching the updated record again (additional GET request), which is unnecessary.
import { useQuery, useUpdateMutation } from '@supabase-cache-helpers/postgrest-swr'
import { client } from '../../lib/client'

export default function Page() {
  const { data, mutate } = useQuery(
    client
      .from('bn')
      .select('id,kurzname,archiviert')
      .eq('id', 2)
      .single(),
    {
      revalidateOnFocus: false,
      revalidateOnReconnect: false,
    }
  )

  const { trigger: update } = useUpdateMutation(
    client.from('bn'),
    ['id'],
    'id,kurzname,archiviert',
    {
      onSuccess: () => console.log('Success!'),
    }
  );

  return (

      {JSON.stringify(data)}

      <button onClick={() => {
        update({
          id: 2,
          archiviert: !data.archiviert
        })
      }}>Toggle "archiviert"</button>

  )
}

Hey! are you on the latest version? And did you disable all automatic revalidation mechanisms?
you should even be able to pass null here. cache helpers will scan the cache and build the select statement automatically.
  const { trigger: update } = useUpdateMutation(
    client.from('bn'),
    ['id'],
    null, // can be null
    {
      onSuccess: () => console.log('Success!'),
    }
  );

I use @supabase-cache-helpers/postgrest-swr version 1.1.6. Any revalidation is disabled:
revalidateOnFocus: false,
revalidateOnReconnect: false,
revalidateIfStale: false

If I use update(...) only, only PATCH request is sent to PostgREST, but response is empty and doesn't contain the updated data. If I use mutate(update(...)), PATCH request is sent und GET request with updated data follows immediately. Couldn't find out how to have a single PATCH request with updated data as response.

hey @vrilcode,
can you share a bit of code or a repro?
you can find a working example in demos/swr (deployed here). Note that there is an extra GET request, but it's from useSubscriptionQuery.

Please see below. Unfortunately I don't have a repo. Test table is called "table" and consists just of two columns "id" (serial) and "value" (text). One row with "id" = 1 should be updated.
import { useQuery, useUpdateMutation } from '@supabase-cache-helpers/postgrest-swr'
import { client } from '../../lib/client'

export default function Page() {
  const { data, mutate } = useQuery(
    client
      .from('table')
      .select('id,value')
      .eq('id', 1)
      .single(),
    {
      revalidateOnFocus: false,
      revalidateOnReconnect: false,
      revalidateIfStale: false
    }
  )

  const { trigger: update } = useUpdateMutation(
    client.from('table'),
    ['id'],
    null,
    {
      onSuccess: () => console.log('Success!'),
    }
  );

  return (

      {JSON.stringify(data)}

      <button onClick={async () => {
        await mutate(update({
          id: 1,
          val: `Test ${Date.now()}`
        }))
      }}>Update value</button>

  )
}

closing this, please reopen if you still have problems :)


Go-TFE 1.0

Hi!
In a few days, HashiCorp will be releasing a major version for the Go API client for Terraform Cloud.
I am reaching out for mainly two reasons.
First to give your team heads up that this release will contain breaking changes. We are aware that your project relies on our client and we will not want you to be caught by surprise if you decide to upgrade :)
But I also wanted to check if you'd be interested in trying out our beta version prior to the official release of 1.0. We'd love to have your feedback to find out if you were able to use this version smoothly. This pre-release version will be available very soon. Would you be able to try it out next week?
Best,
Luces

Hi @uturunku1 .  It seems this project isn't very active at the moment.  May I ask, are there any plans from HCP to provide a supported / official CLI?  It's a missing piece that many of us could use in our CI systems, etc :)

Hi All, I've missed the notification about this thread. I will have a look into the new changes and plan a new build.


rustdoc docs not rendering correctly

I'm using firefox 69.0 on linux. I would expect the below image to be syntax highlighted and the # lines hidden. When I build and open the docs locally, they render correctly.

Where is that image from? It looks fine on https://docs.rs/serde/1.0.101/serde/de/trait.DeserializeSeed.html.

Ah, it's https://docs.serde.rs/serde/de/trait.DeserializeSeed.html. Let me take a look.

Sorry, should have specified that as well.

Should be fixed now. Thanks for catching this! Apparently the beta compiler does not support 2018 edition documentation in a 2015 edition crate so we need to build docs.serde.rs with nightly.

All good on my end. Thanks for fixing this so fast!


provided the code of pascal's triangle in cpp

@Chitresh-code can you check the code once, i hope you are ok with it

@awsmdeep everything is alright with your PR.


Cannot find context with specified id

hi,
i'm new in devloping and  i keep get this message error in brackets,
"Cannot find context with specified id"
any one can help me please ?

Where you see the message? Is an alert or you see in the console?
Can you reproduce with Debug \ Reload Without Extensions?

it's keep appear in the console, when i reloaded without Extensions its disappear.
thanks,

Closing as extension problem.


docs: add missing mount bpf fs on minikube GSG

Fixes: 413191ba399e ("doc: New quick install guide")
Signed-off-by: André Martins<EMAIL_ADDRESS>

Seeing that we're about to revert this commit, I'm un-labelling for backports.


Refactor commands and IO for testability and test

Please verify this on hardware, it shouldn't have changed any behaviour, just made it more pluggable/testable.
(side-note: I think this might also make the WX visualiser easier to implement... just drop everything that isn't pixel data and you should be able to run Inky.Command functions on it. :))

I've left some commented code in commands.ex just to show what it was before and what it is now.

Approved out of band, merging.


Add sponsorship for Clerk.com

Related Issues

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Description
Fixes # (issue)
N/A – Adding Clerk.com sponsorship
Screenshots/Recordings

Added tests?

[ ] Yes
[x] No, because they aren't needed

Added to documentation?

[x] README
[x] Documentation
[ ] No Documentation Needed

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

cc @darkmatter18 ☝


Connect example fails with "TypeError: ConnectionError is not a function"

To reproduce:
elasticsearch = require("elasticsearch-odm");
elasticsearch.connect("test-index");

Unhandled rejection TypeError: ConnectionError is not a constructor
    at createIndex (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/index.js:84:44)
    at /home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/index.js:62:14
    at bound (domain.js:280:14)
    at runBound (domain.js:293:12)
    at tryCatcher (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/promise.js:503:31)
    at Promise._settlePromiseAt (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/promise.js:577:18)
    at Promise._settlePromises (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/promise.js:693:14)
    at Async._drainQueue (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/dan/Projects/kasra2/web-app/node_modules/elasticsearch-odm/node_modules/bluebird/js/main/async.js:15:14)
    at tryOnImmediate (timers.js:543:15)
    at processImmediate [as _immediateCallback] (timers.js:523:5)

Elasticsearch server info:
$ curl 'localhost:9200'
{
  "name" : "Human Torch",
  "cluster_name" : "elasticsearch",
  "version" : {
    "number" : "2.3.4",
    "build_hash" : "e455fd0c13dceca8dbbdbb1665d068ae55dabe3f",
    "build_timestamp" : "2016-06-30T11:24:31Z",
    "build_snapshot" : false,
    "lucene_version" : "5.5.0"
  },
  "tagline" : "You Know, for Search"
}

Checked on Node v6.3 and v4.3.
Observations

The index did not already exist, but if something is wrong with the ES server, this isn't the place to troubleshoot that
Filling out an options object for the connect call produces the same result
Logging ConnectionError from index.js, just after the requires, shows that it is undefined

Wait, maybe this doesn't actually support Elasticsearch v2? I see that there is a fork at https://github.com/bloublou2014/elasticsearch-odm with a bunch of activity on a es-2.x branch. Hopefully that merges back in when it is ready :)

Hello, Yes branch works with ES2.x, and has been updated (test & code).
Issue #4 request help but zackiles has not answered yet. if still no answer within a week i will publish a elasticsearch-odm-es2 to npm.

Sorry for delay, it's been merged now!


Cannot launch Android App (Crashes/Stops responding.)

Summary
Mattermost Android App crashes on launch.
Environment Information

Device Name: HTC One Max
OS Version: Android 4.4.2
Mattermost App Version: 1.2.0
Mattermost Server Version: (N/A, cannot launch app.)

Steps to reproduce
When I try to launch the app, it crashes. I have used the Android Feedback tool to submit logs.
Expected behavior
App launches successfully.
Observed behavior
Cannot open app.
Possible fixes
Unk, App crashes on launch.

@ellomdian does this happen repeatedly? can you share your android version? is a custom rom? is your device rooted?

Enahum -

Yes, I have not been able to launch the app successfully since install.
4.4.2
Verizon Stock ROM, Rooted/Unlocked (personal VPN app requires Root)

On Mon, Sep 18, 2017 at 8:20 PM, enahum<EMAIL_ADDRESS>wrote:

@ellomdian https://github.com/ellomdian does this happen repeatedly?
can you share your android version? is a custom rom? is your device rooted?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattermost/mattermost-mobile/issues/897#issuecomment-330408892,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeakJ94xKQ-u20vci-3H5r5UWAVNiKNWks5sjyThgaJpZM4PUtAy
.

--
"Physics isn't a religion. If it were, we'd have a much easier time raising
money."
Leon Lederman
"But how is one to make a scientist understand that there is something
unalterably deranged about differential calculus, quantum theory, or the
obscene and so inanely liturgical ordeals of the precession of the
equinoxes."

Have you been able to run the app in a non-rooted phone? sadly I don't think we are going to look into this as it seems is totally related to the phone being rooted.

enahum -
Unfortunately, I only have one phone.
I'm sorry to hear that. While it doesn't significantly impact me as I am
investigating Mattermost simply as a proof of concept, I can assure you
that as your app gains more visibility, you are going to run into these
sort of issues more and more frequently. If the dev community hears that
your app fails simply because a phone is rooted - I'm still on the stock
Retail ROM - it's not going to be great.
I'd love to hear the technical explanation of why the phone being rooted
has anything to do with the environment that the app is running in, or why
the ability to run at even higher than stock Android permissions would
break it, but since I'm not actively contributing to the project it's
really none of my concern.
Good luck moving forward, and you may close my report as a known-issue with
rooted devices.
On Tue, Sep 19, 2017 at 11:23 AM, enahum<EMAIL_ADDRESS>wrote:

Have you been able to run the app in a non-rooted phone? sadly I don't
think we are going to look into this as it seems is totally related to the
phone being rooted.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattermost/mattermost-mobile/issues/897#issuecomment-330611358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeakJ_-t5f9BCf91B7uIEsndeQ-cGGYCks5sj_iAgaJpZM4PUtAy
.

--
"Physics isn't a religion. If it were, we'd have a much easier time raising
money."
Leon Lederman
"But how is one to make a scientist understand that there is something
unalterably deranged about differential calculus, quantum theory, or the
obscene and so inanely liturgical ordeals of the precession of the
equinoxes."

I have the same issue with Android 4.4.4. After looking on logs - seems that problem is in:
E/AndroidRuntime( 2979): java.lang.NoClassDefFoundError: android.content.RestrictionsManager
E/AndroidRuntime( 2979): 	at com.mattermost.rnbeta.NotificationsLifecycleFacade.LoadManagedConfig(NotificationsLifecycleFacade.java:169)

@enahum As far as I know android.content.RestrictionsManager was added in API 21 (Lollipop SDK 5.0). So app will be crashing on everything lower than SDK 5.0.

Well yes our app needs at least API 23.
Closing this issue

@enahum in this case mattermost-mobile/android/app/build.gradle should be updated with correct minSdkVersion, don't you think?


Rannacher-Turek has wrong reference element

Describe the mistake
The Rannacher-Turek element shows a wrong reference element (triangle, tetrahedron) in the web interface and is not listed in the element list on quadrilaterals.
Additional context
See https://defelement.com/elements/rannacher-turek.html and https://defelement.com/lists/references/ .

Thanks for reporting this. It should be fixed now that the website has had time to rebuild


LPDID: Setting Windows with Monthly Data

LPDID currently requires that date variable inputs (tname and gname) be in the format YYYYMM if one is using monthly data. This seems to cause some weirdness with setting the pre- and post-windows when one has monthly data spanning more than a year. In particular, with dates in the YYYYMM format (e.g., 202312 and 202401) the jump from  December of one calendar year to January of the next is obviously not 1. If I set my pre- and post-window to values less than (minus and plus) 12, there's no problem: the command runs. But setting them to something like plus/minus 20 (again, in terms of months) and LPDID will not run and I get an error message like the one displayed below. On the other hand, if I set it to something large enough to cover the jump from one calendar year to the next (e.g., 96) the command runs and produces coefficients for all 96 leads and lags (I have about 28 years of data).
Is there something I'm missing here, or is this an known issue? Or just something that will persist until datetime formats are supported?

Thanks for reporting - looks like another bug! What is it that you are re-running? Is it running one of etable / summary / tidy / vcov post estimation that alters the model output? Could you provide a reproducible example with the df_het example data set?

It occurs when I run iplot (In my original message I had put "iplot" in angle brackets, and I just now noticed that doing so suppressed that bit of text...a key piece of information! Sorry about that!).
I will come up with a reproducible example using the df_het data set. Thank you!

url = "https://raw.githubusercontent.com/py-econometrics/pyfixest/master/pyfixest/did/data/df_het.csv"
df_het = pd.read_csv(url)
fit = pf.lpdid(
    df_het,
    yname="dep_var",
    idname="unit",
    tname="year",
    gname="g",
    vcov={"CRV1": "state"},
    pre_window=-20,
    post_window=20,
    att=False
)
fit.tidy().head()
fit.iplot(figsize= [1200, 400], coord_flip=False).show()
fit.tidy().head()
fit.iplot(figsize= [1200, 400], coord_flip=False).show()

The first tidy() call, produces the following output

The second tidy() call, after running iplot(), produces

The second iplot() call, generates the following error:

AttributeError: 'DataFrame' object has no attribute 'dtype'"

Thanks @escherpf , I can reproduce this. The second evaluation of
fit.tidy().head()
fit.iplot(figsize= [1200, 400], coord_flip=False).show()

produces
AttributeError: 'DataFrame' object has no attribute 'dtype'

As a matter of fact, it seems that calling iplot() twice seems to trigger the error:
fit = pf.lpdid(
    df_het,
    yname="dep_var",
    idname="unit",
    tname="year",
    gname="g",
    vcov={"CRV1": "state"},
    pre_window=-20,
    post_window=20,
    att=False
)
fit.iplot(figsize= [1200, 400], coord_flip=False).show()
fit.iplot(figsize= [1200, 400], coord_flip=False).show()

I'll take a look at this in the next days.

As a matter of fact, it seems that calling iplot() twice seems to trigger the error:

That's correct. Calling iplot changes the index of LPDID object, which is what appears to be causing the error on the second iplot call.
Thank you @s3alfisc !

The iplot error does not occur with did2s:
fit = pf.did2s(
    df_het,
    yname="dep_var",
    first_stage="~ 0 | unit + year",
    second_stage="~i(rel_year, ref=-1.0)",
    treatment="treat",
    cluster="state",
)
fit.iplot(figsize= [1200, 400], coord_flip=False).show()
fit.iplot(figsize= [1200, 400], coord_flip=False).show()

The issue with iplot() and reindexing should be solved after merging #754, was an easy fix =)

Currently doing some research on how the leading did libraries handle missing data.

did allows only numeric input: link

Btw I need to add the name of the required input data type for tname, gname, etc to the docs:

Made some changes in this PR: https://github.com/py-econometrics/pyfixest/pull/756 . Could you check if these make sense for you @escherpf?


Unhandled NSURLErrorCancelled errors on semi-valid HTTPS connections.

I get the same behavior (and the same fix solves it) as #1431 if I connect to an HTTPS API whose certificate is otherwise valid but for which the domain is different (our test server). Adding in the default handler manually resolves the issue.  v2.3.1
I would expect the default handler to still be in effect in such a scenario and can't figure out why it wouldn't be called.
Thoughts?

So what is the way to check if the NSURLErrorCancelled error was actually an unhanded kSecTrustResultRecoverableTrustFailure?


Perform regression testing of the Carbon for ibm.com v1.17.0 release - Prod QA testing

User Story

As a [user role below]:
DDS engineering lead and Offering Manager

I need to:
ensure the changes included in the v1.17.0 release do not adversely affect the existing code

so that I can:
ensure the quality of the ibm.com adopter experience is maintained

Additional information

Contents of the v1.17.0 release
The regression testing is scheduled from Mar 15 - 23.  At least 2 rounds of regression testing should be performed during these dates.
React (Storybook)
React (NextJS)
Vanilla (Storybook) - Limited testing of the Tier 1 browsers
Web Components Storybook

Acceptance criteria

[ ] All regression tests are executed
[ ] Defects are created

40 - 45 % of the regression testing is finished.

80% of regression testing is finished.  Need another 1/2 to finish the rest of the testing.  Regression should be finished by tomorrow morning US.  All patch worthy bugs will be finished by EOD March 17.  New RC will be created EOD tomorrow.

Round 1 of Regression testing is finished.  Patch will be cut about 2 ET by Ignacio today.  Praveen will begin the second round of regression testing in the morning India time.

Second round of regression testing is finished.  A critical accessibility bug was found in the React Locale Modal.  Another RC will be cut later today after the fix is done.  Praveen will begin regression testing Tuesday AM in India.

Kenny worked with Ram regarding the new Sev 1 issue.  It was closed.  Additional round of testing was not needed.

Regression testing is finished with no additional bugs to fix.  Moving forward with publishing the release.


Add ability to check database roles configuration

Ticket
n/a
Changes

Add "check" option to role manager lambda function
Add check-database-roles.sh script to call role manager with "check" option
Add make infra-check-database-roles target
Add cluster_id output to database module
Add db app and migrator access to role manager lambda function
Update set-up-database.md instructions to check database roles at the end of setup

Other changes

Print role manager's logs when running create-or-update-database-roles.sh

Context for reviewers
Another developer experience thing similar to https://github.com/navapbc/template-infra/pull/415, this change allows someone to check that the database is properly configured without having to spin up the service layer. This change updates the role manager lambda function to have a "check" mode that logs in to the database as the "migrator" and "app" users (to make sure that IAM auth works), and attempts to perform queries that on the database to check that they have proper privileges. Specifically, the migrator user checks the search path to make sure that new tables are created in the right schema rather than public, it creates a table, then the app user writes something to that table, then the migrator user drops the table. This should improve the first time developer setup experience, and should also help with maintenance e.g. if someone needs to refactor the database code, they can do so and have some confidence that their changes won't break things.
Testing
Development and testing done in this platform-test PR: https://github.com/navapbc/platform-test/pull/40

Resolved conflicts, switched to new using new split policies (rather than the old policy that will be deleted), and retested (see platform-test PR for evidence of testing)


Add instructions to the README for adding tests.

Took me a couple of minutes to figure this out.

The general trend we have is to move docs out of README's to Guides/Tutorials but I merged this in since it can help others in the meantime :) Thanks


Update Migration-web-parts-migrationAPI.md

corrected Typo

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Update typo in computed_fields.md

Change Summary
Fix a small typo in the docs for computed field
Related issue number
N/A
Checklist

[n/a] Unit tests for the changes exist
[x ] Tests pass on CI and coverage remains at 100%
[ x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @dmontagu

Thank you!


Add aggregation operators added in MongoDB 3.4

This adds almost all new aggregation operators introduced in MongoDB 3.4 to the aggregation builder. Still missing:

[ ] $collStats: I'm not sure what a smart API would be, but most likely I'd make the signature something like collStats(bool $latencyStats, bool $latencyHistograms, bool $histograms) and construct the expression from the three bools given.
[ ] $switch: this would require using different names for case, then and default as those are reserved words. Only when using PHP 7 can we use these words as method names. One option would be to add other methods and mark them as deprecated from the outset.

$switch: this would require using different names for case, then and default as those are reserved words. Only when using PHP 7 can we use these words as method names. One option would be to add other methods and mark them as deprecated from the outset.

I'm curious if you could get around this by documenting those methods and having PHP < 7 handle them via __call(). Is the reserved word validation only when defining them as methods in PHP 5.x source, or also when invoking the names?

I'm curious if you could get around this by documenting those methods and having PHP < 7 handle them via __call(). Is the reserved word validation only when defining them as methods in PHP 5.x source, or also when invoking the names?

That is a very clever idea, and it seems to work: https://3v4l.org/GdgJs. I'm wondering whether it would make sense to extract the logic to a trait and conditionally implement this using __call for PHP 5.6 and just straight-up declare the methods for PHP 7.

@jmikola @malarzm Added the $collStats pipeline stage that I missed in the other pull request (I thought it was just an operator, don't know why) and also included a minor refactoring to use $this as return type in the docblock. This makes code completion more useful in ODM where we extend the Expr class and add our own methods.

@malarzm will clean up coding style in a separate pull request, there are a few more instances where it's wrong.


Auto-pickle parameters on modelify calls

Description
When you run 'modelify' command for some pipeline relying on parameters you get " Dataset 'parameters' is not persisted currently." error. The issue seems similar to #158

Hello @Mercurrent,
thank you for the bug report. You are right that it is the same error, and I will fix it soon (within weeks). The current workarounds are:

use pipeline_ml_factory to automatically save your model after training. this is the recommended way to save kedro pipelines as model in kedro-mlflow. I'd be glad to help if needed.
If you really want  to use the modelify command, write your parameter in a yaml file, and call it from the catalog.yml instead of parameters.yml, e.g.:

Current:
# parameters.yml*
my_param: 1

# pipeline.py
def create_pipeline(**kwargs):
    Pipeline([
        node(func=your_func, inputs="params:my_param", outputs="final_data")
    ])

Workaround:
# catalog.yml
my_param:
    type: yaml.YAMLDataSet
    filepath: /path/to/my_param.yml

# /path/to/my_param.yml
1 # no prefix, it is a dataset

# pipeline.py
def create_pipeline(**kwargs):
    Pipeline([
        node(func=your_func, inputs="my_param", outputs="final_data") # remove "params:"
    ])


[T4A3][W13-B2] Bernard Koh

Ready for Review

@bernardified
Some comments added. Please ack & close the PR after reading comments.


[Draft] Security Incident schema

Proposal for an updated Security Incidents event class using the new Finding Info object
It includes the following:
Security Incident (Create, Update, Close)
The Security Incident event class has the following goals:

Ability to model incidents that describe one or more security findings
Ability to consolidate multiple findings into a higher level Incident construct that can convey a broader attack campaign
Ability to capture the state and progression of an incident
Ability to assign an incident to a user, and capture comments

As per discussion I have no problem with the principle of having multiple findings grouped together. However reading security_incidents, I see that remediations must go through cis_csc name. Whilst I have great respect for CIS, remediation recommendations can come from MANY other places than CIS, I think we should find a better name here.
I am even more worried that this is a 'consensus' within OCSF, I don't think this is right to 'alienate' the all schema ONLY on CIS here.

Closing in favor of https://github.com/ocsf/ocsf-schema/pull/903


Housekeeping

Starting with the most benign changes before I move on to API updates.

Updated .gitignore.
Updated bindgen version.
Addressed clippy lints.
Added traits and #[non_exhaustive] to enums affected by lints.

Better?

Better?

Yep! Will merge after the .gitignore question is resolved.


Add customizable tweens to modcharting

Add FlxEase tweens as an available option for each modchart tween function.
Default values for each function are set to what they were before.
(please ignore the massive switch case, i couldn't find a better way lmfao)

Made them optionable, forgot about that. Old modcharts don't break now.

please resolve the conflicts.

what is even happening in this pr

I dont feel like this is ever getting merged without da conflicts gone. Remake a pull on master again or smth


Why not quote Illuminate\Redis\RedisManager directly here?

What do you mean by "quote"?

Sorry  I've got the wrong idea


Create Targeting Class

In file bot/Unit_Classes/baseClassGround.py
https://github.com/FredNoonienSingh/HarstemsAunt-SC2-AI/blob/328405150cd57751ab98019e4ed1ba7be4e68277/bot/Unit_Classes/baseClassGround.py#L93

Targets should be picked based on on:

distance
Prio based on UnitTypeId
DPS
Position


Spyder editor issue: when graphic backend is changed to automatic, plot will not show unless editor is closed

Problem Description
Hello, I'm using the editor for Spyder 3.2.8 to graph plots for a class. I need them to appear in a separate window. It was recently updated from 3.1.4, and now the graphs appear inline when I run the file. I researched how to change it with Tools>Preferences>iPython console>graphics. But even setting it to automatic (or any of the other options) and restarting Spyder causes the console to continue "connecting to the server" without ever connecting. When I run the code, the graph does appear in another window but only when I close Spyder entirely, andI can't view it for long since it closes along with it.
For some context, I am mainly using a conda created environment to do this, but the same result occur inside and outside the environment.
I really need the plots to appear in a seperate window so I can enlarge them since the graph comes out too small when saving it as a PNG (or using Snipping tool). Any help is appreciated.
What steps will reproduce the problem?

I really need the plots to appear in a seperate window so I can enlarge them since the graph comes out too small when saving it as a PNG (or using Snipping tool).

This is entirely unnecessary, and far better done just by using matplotlib's savefig command (or an equivalent in any other half-decent plotting package.
Nevertheless, this appears to be a duplicate of #6452 and is an upstream problem, not anything with Spyder , and can likely be fixed by a simple conda install ipykernal Please try that,
along with the steps listed in the Spyder Troubleshooting Guide, specifically the Basic First Aid and Emergency CPR sections, which resolve the great majority of Spyder installation issues.

Closed due to lack of response as a likely duplicate. If you can provide more information, and you're sure it is not a duplicate, please reopen and do so. Thanks.


Robcohen/docs

Added readthedocs for consistency across repos.
https://docs.cardano.org/projects/ouroboros-network/en/latest/

Please give all PRs a proper title instead of just accepting the branch name.

This PR refers to a private version network design doc.  Hopefully, by the end of the week we will have a public version.

@robcohen shall we translate our technical documentation, which is written in a pdf format to markdown? If so can somebody help us with that?


Fixes/styles in stringpool

Fixes an issue where the style data for strings was read incorrectly. The header contains the offsets of all style data; the code incorrectly assumed the style data could just be read sequentially from the start of the style data section.
https://justanapplication.wordpress.com/tag/androidstyledstrings/ has the nitty gritty details.

@bartsaintgermain  can you review & approve?


Feature Request: Total Hour for vehicle just like Total Distance

Hello Anton,
Request you for the feature for maintain the vehicle Total Hour just like as Total Distance option available right now in server.
This will help us for the vehicle that have the Total Hour instead of Odometer.
Thanks.

Working off the ACC signal? Does not guarantee that engine is running though. May need to be a configurable option as some trackers could use a GPIO port or a separate flag for if engine is running.

Yes, that would be nice idea.

Some trackers report "Ignition".  That could be used.  Yes, someone could have the key turned all the way without the engine running, but most won't as the battery would be depleted quick.  It's like GPS computed mileage... "close enough".

Here is some thoughts about this feature.
Before implementing server side engine hours accumulator based on ignition we need to standardize a attribute.
I believe KEY_HOURS is for that.
From the server side it is simpler use milliseconds (just subtract unix time), but we have number of protocols already used this attribute.

Aplicom
Astra
Continental
Gl200Text
GoSafe
Gps103
Mta6
Mxt
Suntech
Vtfms
Xirgo

Looks like most of them mean that as hours, I think it is not enough precise to accumulating. Also we already have engine hours in reports and it is in milliseconds. I think it is better make it consistent.
@tananaev what do you think? Or may be better add another attribute for that?

I think we should convert it to milliseconds, even if devices report in much lower precision. If device reports it, we shouldn't override it.

Looks like here is small issue https://github.com/traccar/traccar/blob/master/src/org/traccar/protocol/GoSafeProtocolDecoder.java#L111
There must be hours[1] and hours[2]. It is OK, i'll fix it but...
there is a test
https://github.com/traccar/traccar/blob/master/test/org/traccar/protocol/GoSafeProtocolDecoderTest.java#L14
with COT:65;20 where 20 do not match documentation

Engine hour, time format: <Hour>-<Minute>-<Second>
Range: 0-0-0~99999-0-0

How will we treat it? Like hours with omitted minutes and seconds, or seconds without hours and minutes?

I think we can assume that it's hours and then fix if there is an issue.

OK.
Can't find documentation for GTCAN packets in GL200, could you please check this value units https://github.com/traccar/traccar/blob/master/src/org/traccar/protocol/Gl200TextProtocolDecoder.java#L602
Looks like hours, but better recheck if you have the documentation.

Just checked documentation and it says h (hours).

Thanks

I have find out hours units in three other protocols. Mxt and Suntech report in minutes, that means that we can't just assume that it is usually hours.
I could not find documentation (or it is for other versions) for the rest of protocols (not ticked)
Could you please check in your archives? Gps103 called "odb" and Xirgo variant called "new" in code.

For Xirgo I haven't found specific documentation for the format, but in one of the Xirgo documents I found ObdTotEngHours is in hours, so I'm assuming that it's the case for all their protocols.
With GPS103 it's worse. There is no information about units:

And it might be even not engine hours but something like "trip time" ...
What about others: Aplicom, Astra, Continental, Vtfms?

I think it's better to go with assumption that it's hours and then fix it as we go.

Just not to create separate discussion in web repo...
We have three places where we will use engine hours, we need to decide how to format and convert it.

Now we have durationFormatter that represent it as 0 h 0 m in reports, I think it is also applicable to State panel.
We have Charts, do not think it is good if it will be in milliseconds, it will be logically to convert hours in hours :) (float) for Charts.
We have Maintenances, where it will be second by popularity attribute to use (I suppose). I think a periods will be rather big (1000 h or so) and also it is logically to ask users enter hours, not minutes or seconds.
May be in future we will add a way to reset hours (like totalDistance) value is also should be entered in hours.

My suggestion is to format hours as 0 h 0 m but convert as floating point hours for CustomNumberField and Charts.

I agree with suggestion.


Disabling Next button at the end of Self-Analysis

Describe the bug
As we reach the end of the covid self-analysis,  the next button can be disabled/on clicking the next button a pop-up for pls submit should appear.
Expected behavior
The next button is disabled.
Screenshots (optional)

@pranjay-poddar  please assign me this issue


Weird coloring and @apply issues in SCSS files (or in Vue SFCs)

Here's my repo, you can see that I have src/stylesheets/scrollbar.scss that is imported within a root.scss file in the same directory, and I import that root in my nuxt.config.js > css. When I tried using Windi classes (with @apply), it didn't work in those files (you can check blame to see how I switched to variables instead). This only happens for external SCSS files. I tried some methods, putting that directory in includes of windi.config.js but no luck there either.
There's also another issue with @apply in both external files and in SFC style tags. They're not colored, which makes it look like it's not a part of the code. I don't think it's because of my VSC theme (I use Dracula) because, before the switch from Tailwind's official extension, they were all colored with no problems.

You see that the coloring of @apply is missing and all classes look weird. You can see here how it was when using Tailwind's extension).
🌟 One idea!
One thing I always cried about Tailwind's extension is that it wasn't able to sort classes in @apply. It's not important but it'd be amazing to see this in Windi's extension! If this is possible, I can create a different issue for this!

can you try to add following in your VS Code Editor Settings
  "windicss.includeLanguages": {
    "scss": "css",
  },

can you try to add following in your VS Code Editor Settings
  "windicss.includeLanguages": {
    "scss": "css",
  },

Nope, didn't work.

Yep, it looks fine in SFCs <style> tags and it's now working in my .scss files too. I can use classes but seems like colours are still missing from there. Is it supposed to be like this?

@eggsy if you talk about issue in functionality of actual usage it might be wrong repo to have this issue. If you are talking about bug in VS Code Extension it is correct. Not sure what you mean?

ok, so maybe please open for the second part an additional issue. It confused me sorry

/cc @voorjaar not sure if that is indented, but it seems .scss files are not quite working yet

@eggsy you checked the includeLanguages setting?
example:
"windicss.includeLanguages": {
  "ruest": "html", // css, js
  "svelte": {
    "type": "css"
  },
  "javascriptreact": {
    "type": "js",
    "patterns": ["@apply\s+\S+$", "..." ],
  },
}

@alexanderniebuhr didn't fix it. I don't know if that's the right config though, it says javascriptreact all I'm trying to achieve is get @applys coloured in .scss files.

It's just an example config, cause that setting supports more stuff

v0.16.6 should fix all problems, try it please.

Welp, they work as expected now! Even in commented lines, they are highlighted (might be a bug of my theme or I don't know but sure!). It'd be great if that's fixed in the next patch though 😅.

just going to close since there was no much activity lately, if some issue still exists please reopen a new issue


Screens missing "elastic" effect in iOS

I installed the conference app in my iPhone 6 and the schedule page does have the "elastic" effect when you pull down on the screen and it slowly scrolls back to the top. The rest of the pages do not behave like that. Is this something I need to add to each page to achieve this effect? Or is this a bug?
Ionic 1 does have that on every screen out of the box.
What am I missing?

@gigocabrera So this is actually on purpose right now to only work with scrollable pages. There's an open issue here on whether or not to add it for all pages: https://github.com/driftyco/ionic/issues/5275
Please add any feedback you have to that issue. Thanks for bringing this up!! :smile:


Get Exchange details

Hello,
I love this wrapper but it seems like the development has stopped a few years back and I would really like if you could add new EOD endpoints such as https://eodhistoricaldata.com/financial-apis/exchanges-api-trading-hours-and-holidays/ to your wrapper!
I hope you like the idea :-)
Simon

Definitely, we'll add new endpoints soon. Thanks Simon.

Definitely, we'll add new endpoints soon. Thanks Simon.

Okay, @Degn. Mentioned endpoint is handled.
Thanks

Okay, @Degn. Mentioned endpoint is handled.
Thanks


libxml2 should be compiled with "-O2"

The vendored libxml2 is being compiled with no optimization. This causes slow performance in some cases, e.g. #2020
This is caused by CFLAGS being set by default to -fPIC by process_recipe in ext/nokogiri/extconf.rb. When libxml2 is configured with any CFLAGS set, then it is compiled without optimization.
This issue is to ensure that libxml2 is compile with -O2 which appears to be the default in libxml2's configure script for gcc.
Final challenge: MiniPortile (and so process_recipe) requires that environment variables be passed as configure_options which means that later applications of, e.g. CFLAGS=something may override earlier applications. I think we should clean this up along the way, because it's making some things (like this) harder.

libxml2 should probably also be compiled with -g, which is also the default and being overridden by the vendored library build process.


Set 'language' value as code_type for literal blocks with force_highlighting

Currently a literalinclude such as:
.. literalinclude:: ../../rips/examples/AppInfo.py
:language: python
.. does not pass the python parameter into the resulting markdown code. This change fixes this.

Thanks :)


Notifications appearing as Alerts on Ubuntu 14.04 LTS

Apologies in advance if this is a duplicate.
This is more about the aesthetics of the notifications (functionally, no problems). Even when I try to create them manually with new Notification("abc"), I get an alert box instead of the notification one.
This does not seem like an OS issue as $ notify-send abc xyz and other applications give notifications as expected.

This is a duplicate of #465.


Error on a slow start

Description of your problem
What steps will reproduce the problem?

start spyder on a new winpython on a slow PC

I get this error:

then the Terminal is just a black window and a blinking cursor. starting new Terminal didn't provide a working Terminal

What is the expected output?

This is actually a winpty failure report

@stonebig, could you please post the contents of the spyder_terminal_err.log and out files?

well, I don't find any "spyder_terminal_err.log".

You need to set in a terminal this environment variable:
SPYDER_DEV=True

then start Spyder from that terminal.

ok,  I tried, but failed to reproduce the error so far.

tries to activate a new terminal fail:

It seems that for some reason the terminal size got values lesser or equal than zero. Is it working now @stonebig?

The server is down according to your screenshot, can we observe the log file once again?

no, I would have to restart spyder. by the way I can't relaunch a spyder-notebook either.
log file didn't change, trying to see if it improves by closing spyder

@stonebig How much memory do you have on that PC?

hi @andfoy ,
This pc is a win10-64 bit, intel core Duo cpu P7450, 4go Ram, spinning disk occupied at 90%,
When I launch spyder, I suppose that more than 50% of the time is spent per the anti-virus.
It's ram/cpu/disk outdated, advantage being that what works on it works everywhere.
small question : how will co-exist spyder-terminal and win-tornado-terminals ?

@stonebig win-tornado-terminals is a fork of spyder-terminal that operates only on Windows. I guess it will be compatible with the Jupyter Notebook/Jupyterlab framework

@stonebig Does PR #106 fixes your problem?

Hi @andfoy , the error didn't appear at this morning slow-start try.
Yet it didn't appeared since a week (maybe I did a super-extra slow start that day, or other fixes did help).
the fix won't arm in any case. please merge

@stonebig I'm glad to hear that the error does not appear anymore, however, does Spyder-terminal works under that setup?

yes, I just forgot to mention it.