[PR][CLOSED] Added config file to reduce the number of cibot messages for PR

 Issue by geunsik-lim
Thursday Jun 28, 2018 at 04:51 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/66

This PR is to add configuration file to enable/disable operations
that submit automatic cibot messages.
The users can configure enabling (or disabling) in ./config/config-environment.sh.
Changes proposed in this PR:

Added how to enable/disable a cibot message

Self assessment:

gbs build: okay
local test: okay
real test: okay

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/66/commits

:octocat: cibot: Thank you for posting issue #90. The person in charge will reply soon.

 Comment by git-bot-sec
Thursday Jun 28, 2018 at 04:51 GMT

If you want to monitor the current build status of your PR, Please refer to http://aaci.mooo.com//TAOS-CI/ci/standalone/ci-server/monitor.php

 Comment by git-bot-sec
Thursday Jun 28, 2018 at 04:52 GMT

:dart: cibot: @STAR has updated the pull request.


[Translation] Saviors

What kind of translation do you want to add (mark with an X, e.g. [X] Descent)?

[X] Mansions of Madness
[ ] Descent

Saviors

Translation File
Localization.Portuguese.txt

Good luck with this one, @ChinaMajesty is not answering. Spanish translation is finished and waiting from April'20

good, i opened this issue just for registering it, i worked with him on this translation, and i already accepted the fact that the author may be gone for good, i shared this file and made a video tutorial on the brazilian board game portal to teach people how they have their scenario translated, if you already have both files i will close the issue


Localization Not Integrating Sparse Map Features?

During the activity, gviz would frequently show sparse map poses. However, it was not showing sparse map features being integrated into localization. What is happening?

This issue relates to:

ISS activity: Crew-Minimal 11
Date: 2021/03/10
FSW release: 0.14.1

Could not reproduce. However, during the testing there were large areas with no sparse map features.


Prevent Startify to change working directory

Hi. Is there any way I can prevent Startify to change the current working directory when opening files from MRU list.
Example.

I always start empty vim from the project root, let's say ~/projects/repo
CWD now is ~/projects/repo
I opened some file from MRU list, let's say ~/projects/repo/src/modules/file.ts
CWD now is ~/projects/repo/src/modules/
This isn't good since I want to use some fuzzy file finder, now it will only look in ~/projects/repo/src/modules folder instead of the project root folder.

Thank you.

Hi @kuntau ,
I have just installed Startify and had the same issue as you 5 minutes ago.
The solution in https://github.com/mhinz/vim-startify/issues/387 fixes the issue on my side, I believe it should solve your issue as well

Thank you @GuillaumeDeconinck


Ecto association doesn't reset after the ID has been updated (from Changeset changes)

Elixir version
1.14.4
Database and Version
PostgreSQL 15
Ecto Versions
3.6
Database Adapter and Versions (postgrex, myxql, etc)
postgrex
Current behavior
Say in the changeset function I allow to change a foreign key:
defmodule MyApp.Transactions.Revenue do
  schema "revenues" do
    # ...
    belongs_to :wallet, Wallet
  end

  def changeset(revenue, attrs) do
    required_fields = ~w(date amount wallet_id)a
    revenue
    |> cast(attrs, required_fields)
    |> validate_required(required_fields)
  end
end

def update_revenue(%Revenue{} = revenue, attrs) do
  revenue
  |> Revenue.changeset(attrs)
  |> Repo.update()
end

If revenue had a wallet preloaded (which we can't know as all we know is that we receive a revenue struct with preloaded assocs or not) and the ID has been changed, after a successful update the association will not match with the ID.
Can't we reset the associations as we know from the Changeset that the IDs have changed (present in :changes)?
If not, I wonder how this problem is solved. It must be pretty common because as an example, I imagine a user may select the wallet through a combo box for the revenue, and so we receive a wallet ID in a form or absinthe request. Assuming the wallet will never be preloaded is dangerous and error-prone (and I opened this issue because what happened to me is that the wallet was preloaded - and didn't match with the ID which led to bugs - because the code for my real case is more complex than the example code shown, as it uses transactions for example).
We should know the source of truth in this case from :changes.
Expected behavior
Expected the association to reset to not-loaded

This is “expected”. Ecto never loads and reloads data behind the scenes for associations, Because while it works in some cases, it also leads to surprising and often slow behavior in others. You can chose to preload the association again by calling Repo.preload with the force option.

What do you think about something like this? (quickly wrote it down, it would be adapted to make it reusable)
  def changeset(revenue, attrs) do
    required_fields = ~w(date amount wallet_id)a
    revenue
    |> cast(attrs, required_fields)
    |> validate_required(required_fields)
    |> unload_assocs()
  end

  defp unload_assocs(changeset) do
    if changed?(changeset, :wallet_id) do
      unload_assoc(changeset, :wallet_id) # unfortunately I'm not aware of such a function (to set to `NotLoaded`)
    else
      changeset
    end
  end

I see. Now that you proposed that, I actually changed my mind: I think on update we can see if any of the foreign key changed and, if so, unload the association.

Would it be surprising for users if some associations were updated and not others?  For example would we update the has_* associations if the :references field was changed? Similarly for :through associations I think there would be inconsistencies with the intermediate structs.

I think this applies only to belongs_to, no? The other associations cannot be updated by definition but I guess your point is precisely that inconsistency?

In my perspective this is only for belongs_to where we have a foreign key and a nested struct.
By the lack of this proposal, all the nested structs which may turn stale due to a change of the foreign key should be forcefully preloaded after each Repo update.

the context need to be aware of the fields being casted in order to preload with force true after an update, because the context doesn't know if a nested assoc was loaded or not (which leads to error-prone code as a change in the schema might require to change the context and vice versa because of coupling).
we might preload too much and so we may do so conditionally using assoc_loaded?, which requires then a lot of code.

My guess is that most codebases using Ecto do not have this check because in most cases the nested struct is not loaded when passed to the context update_ function, but it is only thus by chance and it is wrong to assume that it is not loaded, so for robust code each Repo update should check if an assoc should be forcefully preloaded or not.
I'll leave space to others:) just wanted to highlight that this would be really nice to have as it avoids a lot of bloat that otherwise would be needed.

Yeah I was mostly questioning if it would be surprising for users if it worked for belongs_to but not for the following situations:
has_{one,many}
schema "a" do
  field :referenced_field
  has_{one,many} :b, B, references: :referenced_field
end

If :b is preloaded and :referenced_field is updated then the preload is also not valid anymore.
many_to_many
schema "a" do
  field :referenced_field
  many_to_many :b, B, join_keys: [a_field: :referenced_field, ...]
end

Similar thing here except it's even more complicated than the has variant because changing :referenced_field might invalidate some of the preloads or all of them or none of them.
through
schema "a" do
  belongs_to :b_id, B
  has_one, :c, through: [:b, :c]
end

schema "b" do
  field :referenced:field
  has_one, :c, C, references: :referenced_field
end

If you are doing an update where a.c is already preloaded and a.b_id doesn't change but b.referenced_field changes then a.c is not valid anymore and it is hard to detect because none of the fields changed on a. I'm not 100% sure if this kind of nested update is allowed and I'm a bit short on time to look. Apologies if that's the case.

Maybe I can make my point more clearly:
If we are concerned about discrepancies between preloads and the "regular" fields that define them, I'm not sure I understand what is special about foreign keys in this case. You are allowed to preload on both sides of the relationship, so both sides can equally be out of sync.
And if we agree with this then we have extra complications when dealing with through associations due to nested updates (assuming they are allowed, I think they are but can't remember 100%).

if it leads to an inconsistency between loaded belongs_to and has_{one,many} and other cases, this could be clarified in the docs, that we handle one case and not the others. If it is then documented,  the developers are now informed, and they do not have to handle the most common case themselves (see next point).

what are truly the alternatives? My guess is that most codebases using Ecto do something like below, even when foreign keys might have changed:

def update_foo(foo, attrs) do
  foo
  |> Foo.changeset(attrs)
  |> Repo.update()
end

It's wrong to me eyes. Now we need a convention in the application that after the Repo update call, we need to call the function (which could be a new Elixir library) reload_changed_assocs. This function will check whether A. a foreign key has changed, B. the nested struct is loaded, and if both conditions are true, call Repo preload with force true. It would need to be always called to avoid the added cognition load: if I add a foreign key in the cast, I have to remember to add that function for every Repo update call on that changeset int he application. As it needs to be always called, it should be in Ecto.

@greg-rychlewski a possible counter argument is that I am almost sure belongs to already has special logic in a couple places. If you do employee |> put_assoc(:company, company), doesn't it automatically set the company_id in employee? This doesn't happen on has_*, since there is no field to set?

Ah ok if it’s already setting the foreign key like that then it would be pretty consistent to unset the association when it changes.
Probably there will still be some confusion for people not acquainted with that behaviour but it seems like it could be explained pretty reasonably.

THANK YOU! Any recommended way I can test this before release?
And I just noticed the recent addition of Ecto.reset_fields/2, which also avoids me in some places some force reloads, and instead just let me unload the stale associations.
With these 2 new features I feel much more confident using Ecto! This updates makes a huge difference for me as this prevents possible bugs and unnecessary forced preloads, and consequently helps the Elixir codebases to be a little safer for free for all developers; that's always a win!
<3

We're happy it helps :).
If you wanted to try it out before release you could change your ecto dependency in mix.exs to refrence this repo:
{:ecto, git: "https://github.com/elixir-ecto/ecto.git"}


cmd/go: git remote did not send all necessary objects

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

$ go version
go version go1.20.2 darwin/arm64

Does this issue reproduce with the latest release?
Yes - inconsistently
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/x/Library/Caches/go-build"
GOENV="/Users/x/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/x/dev/go/pkg/mod"
GONOPROXY="git-codecommit.ap-southeast-2.amazonaws.com,x"
GONOSUMDB="git-codecommit.ap-southeast-2.amazonaws.com,x"
GOOS="darwin"
GOPATH="/Users/x/dev/go"
GOPRIVATE="git-codecommit.ap-southeast-2.amazonaws.com,x"
GOPROXY="https://proxy.golang.org/,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.2"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/x/dev/x/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/fx/gdzg_qkn6y79r0cjz5d87j140000gn/T/go-build35198489=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Seems very similar to old issue #31399
Getting inconsistent results when running go get command on a CodeCommit git repo. In the form of:
go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/x.git@<branch>
The command fails inconsistently with
fatal: bad object <some commit>
error: https://git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/x did not send all necessary objects

Using the local machine, switching the branch name sometimes got it to work. However, using our CICD pipeline the command seems to always fail no matter the branch.
It doesn't fail ever with go version 1.19 - so there doesn't appear to be a problem with the repository.
EDIT: also noting that the commit hash that it complains about is different on different branches that we try it on
What did you expect to see?
The command successfully completes which is the case when switching back to v1.19
What did you see instead?
did not send all necessary objects

Can you show us the output of the go get -x command?  Thanks.

Logs from CICD failing on to different branches. Note repo name is updated for privacy.

    Resolving deltas:   0% (0/19)
Resolving deltas:   5% (1/19)
Resolving deltas:  10% (2/19)
Resolving deltas:  15% (3/19)
Resolving deltas:  21% (4/19)
Resolving deltas:  26% (5/19)
Resolving deltas:  31% (6/19)
Resolving deltas:  36% (7/19)
Resolving deltas:  42% (8/19)
Resolving deltas:  47% (9/19)
Resolving deltas:  52% (10/19)
Resolving deltas:  57% (11/19)
Resolving deltas:  63% (12/19)
Resolving deltas:  68% (13/19)
Resolving deltas:  73% (14/19)
Resolving deltas:  78% (15/19)
Resolving deltas:  84% (16/19)
Resolving deltas:  89% (17/19)
Resolving deltas:  94% (18/19)
Resolving deltas: 100% (19/19)
Resolving deltas: 100% (19/19), completed with 9 local objects.
    fatal: bad object f0ebb4c0f54266993d23750fb76899b1fc29a9f7
    error: https://git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib did not send all necessary objects

[Container] 2023/03/14 06:06:00 Command did not exit successfully if [[ -z "${LIB_BRANCH}" ]]; then
  echo "LIB_BRANCH not set using version from go.mod"
else
  echo "LIB_BRANCH is set, getting HEAD from ${LIB_BRANCH} branch"
  go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@test
  go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@${LIB_BRANCH}
fi exit status 1
[Container] 2023/03/14 06:06:00 Phase complete: BUILD State: FAILED
[Container] 2023/03/14 06:06:00 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: if [[ -z "${LIB_BRANCH}" ]]; then
  echo "LIB_BRANCH not set using version from go.mod"
else
  echo "LIB_BRANCH is set, getting HEAD from ${LIB_BRANCH} branch"
  go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@test
  go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@${LIB_BRANCH}
fi. Reason: exit status 1
[Container] 2023/03/14 06:06:00 Entering phase POST_BUILD
[Container] 2023/03/14 06:06:00 Phase complete: POST_BUILD State: SUCCEEDED
[Container] 2023/03/14 06:06:00 Phase context status code:  Message:
[Container] 2023/03/14 06:06:00 Expanding base directory path: dist
[Container] 2023/03/14 06:06:00 Assembling file list
[Container] 2023/03/14 06:06:00 Expanding dist
[Container] 2023/03/14 06:06:00 Skipping invalid file path dist
[Container] 2023/03/14 06:06:00 Phase complete: UPLOAD_ARTIFACTS State: FAILED
[Container] 2023/03/14 06:06:00 Phase context status code: CLIENT_ERROR Message: no matching base directory path found for dist

That's a git error, I don't think there's anything go can do about it

@seankhliao maybe so, but why does it only happen with v1.20 then? Is the git command changed?

the git commands go runs are in the log you posted, perhaps it was your git version that changed and not go?

 LOTS MORE OF THIS ...
# get https://sum.golang.org/tile/8/0/x063/780
# get https://sum.golang.org/tile/8/0/x063/780: 200 OK (0.002s)
go: warning<EMAIL_ADDRESS>retracted by module author: Retract older versions as only latest is to be depended upon
go: to switch to the latest unretracted version, run:
    go get github.com/microcosm-cc/bluemonday@latest
go: downgraded git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git v1.40.8 => v0.0.0-20230314054121-ce7d2348aba5

[Container] 2023/03/14 06:12:29 Running command rm -rf "dist"

[Container] 2023/03/14 06:12:29 Running command cp -r "eb-template" "dist"

[Container] 2023/03/14 06:12:29 Running command env GOOS=linux GOARCH=amd64 GOFLAGS=-mod=mod go build -o "dist/bin/server"

[Container] 2023/03/14 06:12:47 Running command go mod edit -replace git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git=../app.lib

[Container] 2023/03/14 06:12:48 Running command echo -n ${CODEBUILD_RESOLVED_SOURCE_VERSION} > dist/commithash

[Container] 2023/03/14 06:12:48 Phase complete: BUILD State: SUCCEEDED
[Container] 2023/03/14 06:12:48 Phase context status code:  Message:
[Container] 2023/03/14 06:12:48 Entering phase POST_BUILD
[Container] 2023/03/14 06:12:48 Phase complete: POST_BUILD State: SUCCEEDED
[Container] 2023/03/14 06:12:48 Phase context status code:  Message:
[Container] 2023/03/14 06:12:48 Expanding base directory path: dist
[Container] 2023/03/14 06:12:48 Assembling file list
[Container] 2023/03/14 06:12:48 Expanding dist
[Container] 2023/03/14 06:12:48 Expanding file paths for base directory dist
[Container] 2023/03/14 06:12:48 Assembling file list
[Container] 2023/03/14 06:12:48 Expanding **/*
[Container] 2023/03/14 06:12:48 Found 7 file(s)
[Container] 2023/03/14 06:12:49 Phase complete: UPLOAD_ARTIFACTS State: SUCCEEDED
[Container] 2023/03/14 06:12:49 Phase context status code:  Message:

Here the git commands filtered
# v1.19 working
git tag -l
git ls-remote -q origin
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa --
git fetch -f --depth=1 origin refs/heads/develop:refs/heads/develop
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' refs/heads/develop --
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' refs/tags/v1.40.8 --
git cat-file blob 6e3bf57c2081bac0acfbf4e0b0d12a1c4e83a4ad:go.mod
git cat-file blob 6e3bf57c2081bac0acfbf4e0b0d12a1c4e83a4ad:go.mod
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa --
git for-each-ref --format %(refname) refs/tags --merged ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa
git fetch -f origin 'refs/heads/*:refs/heads/*' 'refs/tags/*:refs/tags/*'
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' ce7d2348aba5 --
git cat-file blob ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa:go.mod
git cat-file blob 6e3bf57c2081bac0acfbf4e0b0d12a1c4e83a4ad:go.mod
git cat-file blob ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa:go.mod
git cat-file blob ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa:go.mod
git -c core.autocrlf=input -c core.eol=lf archive --format=zip --prefix=prefix/ ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa
git cat-file blob ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa:go.mod
git cat-file blob ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa:go.mod

# v1.20 failing
git tag -l
git ls-remote -q origin
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa --
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' refs/tags/v1.40.8 --
git cat-file blob 6e3bf57c2081bac0acfbf4e0b0d12a1c4e83a4ad:go.mod
git cat-file blob 6e3bf57c2081bac0acfbf4e0b0d12a1c4e83a4ad:go.mod
git -c log.showsignature=false log --no-decorate -n1 '--format=format:%H %ct %D' ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa --
git for-each-ref --format %(refname) refs/tags --merged ce7d2348aba5ab2c9d39ee9ab12a1f20bed0e5aa
git fetch -f origin 'refs/heads/*:refs/heads/*' 'refs/tags/*:refs/tags/*'
go: git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@develop: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /go/pkg/mod/cache/vcs/86cbb66aa0091673f15a828b4042911b3c116cded9ab998b7ab8e0e42f6164a2: exit status 1:

I believe this may be related to local corruption of the caches somehow and will reopen if not

After more investigation, I have ruled out any existing broken cache causing the problem. I have run go clean -modcache before all the tests I've run and can consistently get it to fail on my machine with v1.20.2. If I run the go get command with the @develop branch (fails) and then with the @test branch (works) the @develop command will then work correctly until I clean the module cache again. On the CICD pipeline - same result
It's like the git folder it is setting up the first time it is run is missing some information with v1.20
Here is a diff. Note the missing objects/pack files and shallow file in the broken one...
 Any more info / tests I can provide?

Running v1.19.7 vs v1.20.2
go clean -modcache
go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/app.lib.git@develop >> goget.log 2>&1

goget-v1.19.log - working fine
goget-v1.20.2..log - fails
There must be something in the structure of the folder that it creates for the repo so that it is different and fails for 1.20.2... anyone got any ideas?

Hello! I had a similar issue with git a few weeks ago and found this blog post, hope it helps! I've ran into this error a few times now in unrelated projects.

Thanks @dingeldeiner, I can't run git gc it on the AWS CodeCommit repo so not sure that it helps me. If I run gc on my local copy (not the go mods dirs) it doesn't present any issues to be fixed. If I clone --bare the entire repo I also don't have any issues. I don't understand how it can be a git issue when it all works fine with version 1.19?
'

@jpduckwo Hello, I have also encountered the same problem, have you already solved it?

Hi @ywooer, no, we have just stuck with 1.19. I was waiting to see if anyone else reported having the same issue. I did some combing through the logs to try and find out what was happening differently on 1.20.2 and the furthest I got was the way Go initialises the folder before pulling the code.  Do you see the exact same symptoms?

@jpduckwo Yes, I tried go get -x with 1.19 and 1.20, and I saw the same logs with your's. In addition, I found go get xxx@tag work fine, but go get xxx@commitId not.

Hi, update from my side. We tested further with v1.21:

Created a new CodeCommit repository and tried with that - no luck
Tried a cut down version of the git history and tags (last month, latest tag only) - no luck
Tried to use the commitId instead of the branch - no luck
Tag worked but we didn't want the CI to have any write access to create a tag for the develop HEAD in the build process

So overall this issue is still there, and the process works fine with 1.19
As a permanent workaround for the issue we changed the build process to git clone the repo into a new folder and do a go mod edit -replace <repo>=<local folder> before the build.
It would be great if this was fixed one day -  I'm pretty sure it's something to do with the folder structure that go get sets up before it does the clone. Maybe it's the local git version of CodeCommit that doesn't like this new way.

I think waitingforinfo tag isn't applicable here any more

@gopherbot please remove label WaitingForInfo

cc @bcmills @matloob

@jpduckwo, what Git server implementation is being used to serve the repo? (Is it the mainline git server, something based on JGit, some other implementation..?)
The reason I ask is because the last time we saw this kind of error (in #31399) it was due to a JGit implementation bug. If CodeCommit is using an outdated or buggy Git implementation, that should be fixed on the CodeCommit side, not worked around on the Go side.
(#56881 leads me to believe that there is a bug in Go's Git handling, but that bug does not manifest as a did not send all necessary objects error from the git command itself.)

Hey @bcmill, thanks for your reply. I will reach out to AWS to see if they can divulge the git server version that CodeCommit uses.
I have said this several times already, but just reiterating that this all works with version 1.19 perfectly fine. Was there some git work-around that was removed in 1.20+? Something has changed in Go that caused this break. However, I do agree that Go shouldn't have to work around any buggy server issues. But also, I've not heard of, or experienced any issues with other tooling used with CodeCommit, and I've been using it for 7 years.

@ywooer Just checking if your issue was also with CodeCommit?

AWS came back and said that CodeCommit is using a custom git server underneath the hood - not JGit just FYI

Hello! I had a similar issue with git a few weeks ago and found this blog post, hope it helps! I've ran into this error a few times now in unrelated projects.

Thank You dingeldeiner, it is Worked for me.

Hello! I had a similar issue with git a few weeks ago and found this blog post, hope it helps! I've ran into this error a few times now in unrelated projects.

Thank you


[xc7/fasm2v] Add support for more tile types

Those are not supported right now (maybe not only them):

[LR]IOI3
[LR]IOI3_SING
[LR]IOI3_TBYTESRC
[LR]IOI3_TBYTETERM
HCLK_IOI3

I'd rather have issues for particular black boxes (e.g. #909) than via tile type.


add roam citekey option to frontend

Follow up to #1728. Wasn't aware I need to add the roam cite key option to the front end. Seems fairly straightforward but would appreciate a quick sanity check. Also I only speak english so I added non-translated options to the locale files.

Only the english locale must be committed. The translations are handled through Crowdin and checking them in here may mess up their workflow.

thanks! fixed.

The translations will roll in in 10 minutes or so and then I'll cut a new release.

(sorry for the lack of due diligence earlier)

all good thanks for being so open to PRs.


Successful celery beat tasks with a duration below a threshold fails with "duration exceeded"

How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.39.2
Steps to Reproduce
Using sentry with django and celery integrations, and automatic instrumentation for celery beat. We have ~40 cron jobs, most of which are working fine.
Our very short-running tasks (< 100ms) are consistently failing with "duration exceeded". The timeout is at default 30 minutes.
The same task will sporadically fail monitoring anytime there is no work to do, and it exits immediately. And it succeeds whenever there is work, and the task runs for longer. I am unsure about the exact threshold.
Example monitors:
https://hoopit.sentry.io/crons/logtasksprune_requestsprune_requests_task/?environment=production&project=248915&statsPeriod=14d
https://hoopit.sentry.io/crons/expensestasksclean_up_unconnected_expense_files/?environment=production&project=248915&statsPeriod=14d
https://hoopit.sentry.io/crons/poststasksclean_up_unconnected_post_images_task/?environment=production&project=248915&statsPeriod=14d
https://hoopit.sentry.io/crons/covid_registertasksprune_users/?environment=production&project=248915&statsPeriod=14d
I have confirmed tasks to be successful, and still fail in the monitor.

Expected Result
When the task completes, the cron monitor should be successful.
Actual Result
When the task completes, the cron monitor is not updated. It eventually fails with "duration exceeded"

Hey @ezet, thanks for the report. As the first step I'd verify whether the SDK sends check ins for the crons -- do you have the option to initialize the SDK with debug=True, trigger one of the short cron jobs that has the issue, and see what the debug logs look like? You should see that the SDK sends an event to the server. If that's not the case, something's wrong with the SDK; otherwise we'll need to investigate further on the server side.

Bumping ticket as I'm also experiencing this. Will look into collecting data via the debug=True option in the next few days


Jupyter Book

Detailed config sections after getting started
Reference pointers for complete documentation on both config files
Copyright year change on build release
Add links to example configurations in complete documentation
Add presentation content  wherever applicable

Closed in #45


"Permission Denied" on first install

I get this error after having pulled down your application from your Ubuntu repository:
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.1.8
https://github.com/micahflee/torbrowser-launcher
Initializing Tor Browser Launcher
Importing keys
gpg: chiave 63FEE659: "Erinn Clark<EMAIL_ADDRESS>non cambiata
gpg: Numero totale esaminato: 1
gpg:              non modificate: 1
gpg: chiave 93298290: "Tor Browser Developers (signing key<EMAIL_ADDRESS>non cambiata
gpg: Numero totale esaminato: 1
gpg:              non modificate: 1
Starting launcher dialog
LATEST VERSION 4.5a3
Checked for update within 24 hours, skipping
Latest version of TBB is installed, launching
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in <module>
    torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 69, in main
    app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 118, in __init__
    self.start_launcher()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 152, in start_launcher
    self.run(False)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 637, in run
    subprocess.call([self.common.paths['tbb']['start'], '-allow-remote'] + self.url_list)
  File "/usr/lib/python2.7/subprocess.py", line 522, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
    raise child_exception
OSError: [Errno 13] Permission Denied

If I try to execute it as root (and I shouldn't) I get:
No protocol specified
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.1.8
https://github.com/micahflee/torbrowser-launcher
Initializing Tor Browser Launcher
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in <module>
    torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 54, in main
    common = Common(tor_browser_launcher_version)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/common.py", line 52, in __init__
    self.build_paths()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/common.py", line 101, in build_paths
    self.set_gui('error', _("{0} is not writable").format(homedir), [], False)
AttributeError: Common instance has no attribute 'set_gui'

I had same issue. I resolved it by running:
torbrowser-launcher --settings

then checking "check for updates next launch" and relaunching tor. I suspect tor got midway through its update cycle, then bailed because of permissions, leaving a nonfunctional application.

I haven't been able to reproduce. But I believe with the recent patches this issue shouldn't happen anymore, anyway.


keepdims option for sum, std, sem, var, mean etc.

I often find myself writing code such as
let mu = Arr.mean ~axis:0 x |> Arr.squeeze ~axis:[|axis|]
let stdev = Arr.std ~axis:0 x |> Arr.squeeze ~axis:[|0|]

It will be useful to have a keepdims option as in numpy sum, which automatically squeezes out the dimension we sum over if keepdims is set false.
In numpy, keepdims is false by default. For backward compatibility, it is probably best to make true the default of keepdims in Owl if we make these changes. Such changes should be straightforward to incorporate into Owl's Ndarray and Algodiff modules. After the proposed changes we will be able to write
let mu = Arr.mean ~axis:0 ~keepdims:false x

@ryanrhymes  @mseri  @ghennequin  @jzstark  thoughts?

This sounds like a welcome change to me.
At this stage I think we should not be too worried about backward compatibility, and think more about having an ergonomic and consistent API before we draft a stable release.
I personally think keepdims:true is more convenient, but we need to test the repercussions of such change very carefully.

a minor thing: keepdims should probably be keep_dims for general consistency with how distinct words are separated

I agree, it looks like a very good addition to current function parameters. No need to be backward compatibility as Marcello said. :)

In my original post I completely messed up what I wanted to say.
The default of keepdims is false in numpy  (I said it's true in the original post) and for backward compatibility, it's best to have keep_dims as true in Owl.
We squeeze the dimension if keep_dims is set to false (I said we squeeze it out if set to true in the original post).
I agree with @mseri that keep_dims:true is probably more convenient as will be backward compatible (unless that's not what you meant to say @mseri ?)

I meant that backward compatibility is not a priority and I would not worry about that.
I find the most convenient default is the one that squeezes out the dimensions. Now I am not sure which one of them it is

@mseri argh okay so I guess we disagree then, I find the not squeezing out the dimension a more convenient default, and is how I've coded it up in the new PR #531. But I also don't really have a strong opinion about this, happy to change it back if others feel the same @ryanrhymes @ghennequin ?

If there isn't a clear consensus or preference, it probably makes sense to go by whatever numpy does by default, so people's expectations are met.

As @tachukao, I find that not squeezing is my most frequent use case, but I'm not too fussed either.

I am really neutral on this.


Possible missing feature in default project set up Visual Studio Preview 2019 .NET Core 2.2

Hi, I am setting up a new project using Visual Studio Preview 2019 with .NET Core 2.2.
I'm not too sure if it affects, but I used to have another project which has a dynamic 'active' navbar when that particular view is chosen.
I have been searching for the code that was controlling the dynamic navbar in the old project and likewise in the new project but I can't seem to find any settings for it. Could you please point me to the right direction? Thank you!

The ASP.NET Core templates can be found here ...
https://github.com/aspnet/AspNetCore/tree/master/src/ProjectTemplates
If you want to see the code for an older template, set the branch to an older release. It defaults to master which is where the engineers are doing work currently for the upcoming release.


Debuging recipes

Is it possible to RELOAD recipes from xml files somehow ingame? If no, how hard would it be to enable sth like that?
Reason is debugging of custom recipes.
Thanks, Darai.

there is.  '/advRocketry reloadRecipies' should do the trick


update nlohmann_json to version 3.4.0

I just released JSON for Modern C++ 3.4.0, see https://github.com/nlohmann/json/releases/tag/v3.4.0. Could you please update the package nlohmann_json?

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.41

Thanks a lot!


Dependency upgrades

Coverage remained the same at 68.246% when pulling 6db8c867e4d4c2bdf00e45bb594a9a69d71315f6 on feature/dependency-upgrades into 325ef0c6d08ce817c65bd86510e2613779ee9f11 on master.


fix: type issues in verifier's code

Fixes #1268

Codecov Report

Merging #1272 (c3d9f20) into master (9dae00e) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c3d9f20 differs from pull request most recent head 80e6c37. Consider uploading reports for the commit 80e6c37 to get more accurate results

Additional details and impacted files

Flag
Coverage Δ

packit-e2e
73.99% <ø> (ø)

testsuite
10.66% <ø> (ø)

unittests
1.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@mdrocco against which pyright version are you testing, because if it is the current released one we should have seen those errors the CI or not?

Not yet, verifier's code is ignored in the current pyproject.toml.

Not yet, verifier's code is ignored in the current pyproject.toml.

 However, type checking is failing on the issue about asynchronous callbacks that I fixed in the past, although I do not see that issue reported in my local setup (with the same pyright version). I suspect pyright might be misbehaving, but please could someone more knowledgeable than me take a look? @stefanberger @aplanas

On my machine with python 3.9.14 your branch passes all tests just fine.
On my machine with python 3.6.8 I get the following errors reported by latest pyright:
/home/stefanb/keylime/keylime/agentstates.py
  /home/stefanb/keylime/keylime/agentstates.py:31:16 - error: Expected no arguments to "TPMClockInfo" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/agentstates.py:110:30 - error: Expected no arguments to "TPMClockInfo" constructor (reportGeneralTypeIssues)
/home/stefanb/keylime/keylime/cloud_verifier_tornado.py
  /home/stefanb/keylime/keylime/cloud_verifier_tornado.py:20:32 - error: "NoResultFound" is unknown import symbol (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/cloud_verifier_tornado.py:1318:80 - error: Argument of type "() -> Coroutine[Any, Any, None]" cannot be assigned to parameter "callback" of type "(...) -> None" in function "call_later"
    Type "() -> Coroutine[Any, Any, None]" cannot be assigned to type "(...) -> None"
      Function return type "Coroutine[Any, Any, None]" is incompatible with type "None"
        Type cannot be assigned to type "None" (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/cloud_verifier_tornado.py:1354:72 - error: Argument of type "() -> Coroutine[Any, Any, None]" cannot be assigned to parameter "callback" of type "(...) -> None" in function "call_later"
    Type "() -> Coroutine[Any, Any, None]" cannot be assigned to type "(...) -> None"
      Function return type "Coroutine[Any, Any, None]" is incompatible with type "None"
        Type cannot be assigned to type "None" (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/cloud_verifier_tornado.py:1382:72 - error: Argument of type "() -> Coroutine[Any, Any, None]" cannot be assigned to parameter "callback" of type "(...) -> None" in function "call_later"
    Type "() -> Coroutine[Any, Any, None]" cannot be assigned to type "(...) -> None"
      Function return type "Coroutine[Any, Any, None]" is incompatible with type "None"
        Type cannot be assigned to type "None" (reportGeneralTypeIssues)
/home/stefanb/keylime/keylime/registrar_common.py
  /home/stefanb/keylime/keylime/registrar_common.py:14:32 - error: "NoResultFound" is unknown import symbol (reportGeneralTypeIssues)
/home/stefanb/keylime/keylime/tenant.py
  /home/stefanb/keylime/keylime/tenant.py:559:23 - error: Object of type "None" is not subscriptable (reportOptionalSubscript)
  /home/stefanb/keylime/keylime/tenant.py:560:46 - error: "get" is not a known member of "None" (reportOptionalMemberAccess)
/home/stefanb/keylime/keylime/da/attest.py
  /home/stefanb/keylime/keylime/da/attest.py:50:33 - error: Cannot access member "fromisoformat" for type "Type[datetime]"
    Member "fromisoformat" is unknown (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/da/attest.py:57:35 - error: Cannot access member "fromisoformat" for type "Type[datetime]"
    Member "fromisoformat" is unknown (reportGeneralTypeIssues)
/home/stefanb/keylime/keylime/db/keylime_db.py
  /home/stefanb/keylime/keylime/db/keylime_db.py:90:16 - error: Expression of type "MockConnection" cannot be assigned to return type "Engine"
    "MockConnection" is incompatible with "Engine" (reportGeneralTypeIssues)
/home/stefanb/keylime/keylime/ima/ima_dm.py
  /home/stefanb/keylime/keylime/ima/ima_dm.py:362:36 - error: Expected no arguments to "DeviceState" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:827:16 - error: Expected no arguments to "VerityAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:831:16 - error: Expected no arguments to "CacheAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:835:16 - error: Expected no arguments to "CryptAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:839:16 - error: Expected no arguments to "IntegrityAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:843:16 - error: Expected no arguments to "LinearAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:847:16 - error: Expected no arguments to "MirrorAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:851:16 - error: Expected no arguments to "SnapshotAttributes" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:855:27 - error: Expected no arguments to "Target" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:866:36 - error: Expected no arguments to "DeviceMetaData" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:870:16 - error: Expected no arguments to "LoadEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:875:16 - error: Expected no arguments to "ResumeEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:880:16 - error: Expected no arguments to "RemoveEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:884:16 - error: Expected no arguments to "RenameEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:889:16 - error: Expected no arguments to "ClearEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:893:16 - error: Expected no arguments to "UpdateEvent" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:928:39 - error: Expected no arguments to "DeviceMetaDataMinimal" constructor (reportGeneralTypeIssues)
  /home/stefanb/keylime/keylime/ima/ima_dm.py:945:38 - error: Expected no arguments to "MirrorDevice" constructor (reportGeneralTypeIssues)

That's a lot more issue than what the test machine is reporting with python 3.9 and my guess it comes from how pyright behaves with the underlying python version. Maybe we need a minimum python version.

@stefanberger I am not clear of what you are proposing by the "minimum python version", do you mean it as a general requirement for Keylime or limited to type (and code quality) checking?

I mean that we would require a minimum python version for style checking. because it seemed odd that no errors are reported on more recent version of python while pyright on older versions reports lots of errors.

I'm fine with requiring a specific version for type checking. It seems like it would be hairy to get it right for all of them since python itself sees differences.

I'm fine with requiring a specific version for type checking. It seems like it would be hairy to get it right for all of them since python itself sees differences.

Since the problems are not widespread maybe this would suffice:
                pending = tornado.ioloop.IOLoop.current().call_later(
                    interval, invoke_get_quote, agent, runtime_policy, False, timeout=timeout  # type: ignore  ; due to python <3.9
                )

I am not sure about the <3.9 comment though, it could be <3.8 also.

# type: ignore  ; due to python <3.9

I agree. I would agree also on pinning the most up to date Python (3.11) for type checking tests in the CI, but running the rest of the tests in the different supported Python version (>=3.6). There is no gain in running pyright in 3.6..=3.11, and fix failures old Python

Safe to ignore: add # pylint: disable=too-many-ancestors in the line 14 of setup.py.
To learn more check this: https://pylint.pycqa.org/en/latest/user_guide/messages/refactor/too-many-ancestors.html
But the tl;dr is that keylime_build is inheriting from build_py and pylint found (not sure where) other classes inheriting from the same base class, and decides that 8 is too much and 7 is OK

pyright issue: https://github.com/microsoft/pyright/issues/4574

Now the issue is here: https://github.com/RobertCraigie/pyright-python/issues/145

The pyright/nodeenv issue may be intermittent. Maybe give this branch another push...

You could squash the two topmost patches since they cancel each other out. Otherwise LGTM.

All tests are passing now, LGTM

@stefanberger why don't we just "squash and merge" the whole thing?

I rebased and squashed

thanks @kkaarreell for pointing this out.


Add documentation for Security rule CA5361 (DoNotSetSwitch) in FxCopAnalyzers

Rule implementation: https://github.com/dotnet/roslyn-analyzers/blob/master/src/Microsoft.NetCore.Analyzers/Core/Security/DoNotSetSwitch.cs#L23

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

ID: f1295961-36c4-75a0-f50a-c5d86159746c
Version Independent ID: 3d4bba1e-0d05-f577-3b78-65dd6ab10635
Content: Security Warnings - Visual Studio
Content Source: docs/code-quality/security-warnings.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @gewarren
Microsoft Alias: gewarren

Bootsrapped: https://github.com/paulomorgado/MicrosoftDocs-visualstudio-docs/tree/paulomorgado/ca5361


[feature request] Allow setting preferences for the remote when creating PR

When working off a fork and creating a pull request, it appears the default list for both the selection for the remote to submit the PR to and the selection to push the local branch to uses alphabetical sort for the defaults.
It would be nice to be able to configure through the settings, or change the default behaviour so that I can select the upstream as the default remote for creating the PR, and the origin as the default remote for pushing the branch.
Using the upstream for the target (if it exists as a remote), and origin for the branch might also make sense as defaults given the common Git naming conventions for remotes.
Thanks for considering this!

I'd like to +1 this feature request. Our fork of a public repository is for internal use only, so I don't want to push something upstream, ever. Still, since this is the only forked repo I work with, I keep accidentally selecting upstream/main as the target branch, which just clutters up the PRs of the public repo with personal edits.

We have githubPullRequests.createDefaultBaseBranch, which I think will solve your case!


Update app-only-auth-powershell-v2.md

Converted the note to a purple box note.  Added PS example for updating from earlier version of the module.

Docs Build status updates of commit 5ce0cc0:
:clock10: Full build: the average full build time is 17 min(s) 32 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5ce0cc0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


feat(linter): no constant condition

feat: #258

Thank you! We'll implement the rest when we have CFG.


Try converting class to a record

See if this breaks basic systemtest

I think it is still the same issue as in #23189

Seems to work now 🎉

Great, no need for testing this in this PR anymore, closing.

🎉


u-accordian - name and provide a type for items

import type { AccordianItems } from '@nuxtlabs/ui'

const items:AccordianItems = [
...

Is this in the edge? how do i import it?
import type { AccordianItem } from '@nuxthq/ui'

?


Unable to read credentials from keychain (corrupted?)

I had a problem upgrading from 1.7.3 to 1.8.0 but I think it's a MacOS issue for some reason. [SYSTEM: 2020 MBP 13" Ventura 13.4.1 running Python 3.11.2]. Here's what I'm seeing from the CLI (the GUI doesn't work either):
$ maestral stop
Stopping Maestral...        [OK]
$ maestral start
Starting Maestral...        [OK]
! Could not load auth token. Can't get password from keychain: (-50, 'Unknown Error')
$ maestral resume

Could not load auth token
Can't get password from keychain: (-50, 'Unknown Error')
$ maestral auth status

Email:         <EMAIL>
Account type:  Basic
Dropbox ID:    dbid:<VALID_DB_ID>

$ maestral auth link
! Could not load auth token. Can't get password from keychain: (-50, 'Unknown Error')
$ maestral auth unlink
? Are you sure you want unlink your account? Yes
Stopping Maestral...        [OK]
! Could not load auth token. Can't get password from keychain: (-50, 'Unknown Error')
$ maestral start
Starting Maestral...        [OK]
! Could not load auth token. Can't get password from keychain: (-50, 'Unknown Error')
$ maestral status

Account      <EMAIL> (Basic)
Usage        60.5% of 13.7 GB used
Status       Paused

Could not load auth token
Can't get password from keychain: (-50, 'Unknown Error')

I thought something may have been wrong with 1.8.0 and rolled it back to 1.7.3, but nope, the error persists. Has anyone else seen this? A quick search doesn't reveal anyone else getting the "-50" keychain error. Everything worked fine for the past year until today. If this is an unknown problem, is there a way to "reinstall" cleanly? Thanks.

UPDATE: I was eventually able to unlink then relink, blew away my dropbox folder and resyncing everything now:
$ maestral auth unlink
? Are you sure you want unlink your account? Yes
Stopping Maestral...        [OK]
✓ Credentials removed
✓ Unlinked Maestral.
$
$ mv dropbox dropbox.backup
$
$ maestral auth link
- Linking new account for 'maestral' config
- Retrieving auth code from Dropbox
? How would you like to you link your account? Open Dropbox website
? Enter the auth code: ww7dcDaS0mErand0HashB11fogGwlDUrfEgB0avAlBo
✓ Credentials written
✓ Linked to <EMAIL>
$
$ maestral start
Starting Maestral...        [OK]
? Please choose a local Dropbox folder: ~/dropbox
? Would you like sync all folders? Yes
✓ Setup completed. Starting sync.

Closing for now but leaving this for posterity in case any other Mac users run into this. (I'm unsure how the unlink got working.)

Another odd thing happened last night when I re-authed and sync my stuff into a new folder: the original timestamps aren't preserved in the new folder as they were in the original folder that was synced before unlinking, similar to the scenario raised by this bug:
$ ls -l dropbox.backup
total 71824
-rw-r--r--@    1 wescpy  staff  21258336 Mar 29 14:47 1 day.pdf
drwxr-xr-x@   44 wescpy  staff      1408 Apr 19 22:29 1 julio RAFTING FIGO sarapiqui pm/
drwxr-xr-x@    8 wescpy  staff       256 Apr 19 22:29 2013rcpts/
drwxr-xr-x@    3 wescpy  staff        96 Apr 19 22:28 Apps/
-rw-r--r--@    1 wescpy  staff      1268 Oct  3  2009 Getting Started.rtf
drwxr-xr-x@    5 wescpy  staff       160 Apr 19 22:28 Photos/
drwxr-xr-x@   14 wescpy  staff       448 Apr 19 23:09 Public/
drwxr-xr-x@    3 wescpy  staff        96 Apr 19 23:09 Sent files/
drwxr-xr-x@ 1412 wescpy  staff     45184 Aug 16 11:34 backup/
-rw-r--r--@    1 wescpy  staff  15496025 Jan  4  2019 intro_to_cloud-60c-1.pdf
-rw-r--r--@    1 wescpy  staff      5504 Jan 13  2020 mbpRepair-proof.pdf
drwxr-xr-x@    7 wescpy  staff       224 Apr 19 23:09 tmp/

$ ls -l dropbox.backup
total 71824
-rw-r--r--@    1 wescpy  staff  21258336 Aug 16 22:03 1 day.pdf
drwxr-xr-x@   44 wescpy  staff      1408 Aug 16 20:41 1 julio RAFTING FIGO sarapiqui pm/
drwxr-xr-x@    8 wescpy  staff       256 Aug 16 20:41 2013rcpts/
drwxr-xr-x@    3 wescpy  staff        96 Aug 16 20:40 Apps/
-rw-r--r--@    1 wescpy  staff      1268 Aug 16 20:38 Getting Started.rtf
drwxr-xr-x@    5 wescpy  staff       160 Aug 16 20:39 Photos/
drwxr-xr-x@   14 wescpy  staff       448 Aug 16 21:02 Public/
drwxr-xr-x@    3 wescpy  staff        96 Aug 16 21:02 Sent files/
drwxr-xr-x@ 1416 wescpy  staff     45312 Aug 16 22:05 backup/
-rw-r--r--@    1 wescpy  staff  15496025 Aug 16 20:59 intro_to_cloud-60c-1.pdf
-rw-r--r--@    1 wescpy  staff      5504 Aug 16 21:04 mbpRepair-proof.pdf
drwxr-xr-x@    7 wescpy  staff       224 Aug 16 21:02 tmp/

I just checked my Dropbox, and it appears the original timestamps are still there. Hopefully the local timestamps don't flow "upstream" as that'll "corrupt" everything (which would be a shame).


Modpacks are not launching for me

Pls fix it

... sigh
This is the Solder Repository and is not an issue tracker for the launcher. Also 'pls fix it' is not a good way to get someone to help you.
http://www.technicpack.net/help
https://github.com/TechnicPack/TechnicLauncher

@skwerlman such a polite answer to that.... :+1:

I, unfortunately, have had lots of practice.

@skwerlman Now only if the @DriftingTheater or a Technic Dev would close these issues...


[WIP] ci: Move everything to balenaCI

Change-type: patch
Signed-off-by: Robert Günzler<EMAIL_ADDRESS>Connects-to: https://github.com/balena-io/resin-concourse/pull/408
Connects-to: https://github.com/balena-io/ci-images/pull/27
Connects-to: https://github.com/balena-io/scripts/pull/63
Connects-to: https://github.com/balena-io-modules/detectorist/pull/27

@balena-ci 	retest

[ ] update https://github.com/balena-io/ci-images/pull/27
[ ] add balena-engine plugin to https://github.com/balena-io-modules/detectorist
[ ] remove reference to wip build image https://github.com/balena-io/balena-concourse/pull/408/commits/c06a30653928a819a71399354a83816333d4b252
[ ] remove detectorist workaround https://github.com/balena-io/scripts/pull/63/commits/3f6d8e5e4da746c4af261de5534a0fd66fc4acf9

@balena-ci retest

@balena-ci retest

@balena-ci retest

@balena-ci retest

@balena-ci retest

@balena-ci retest


Tweego crashing on launch

Describe the bug
Very shortly (not even 10 frames) after running tweego.exe, the program closes itself.
Desktop (please complete the following information):

Tweego Version 2.1.1
Win 10 22H2 compilation 19045.2130

Additional context
I've tried rebooting the system, running as admin and other compability settings (win 8, 7, etc.), but no results.  I've also tried the x86 version and no luck.

First.  You do realize that Tweego is a command-line application, yes?  It doesn't create a window, you run it from a shell—e.g., included with Windows: cmd.exe, PowerShell.
I don't know what frames is supposed to represent in the context of executing a command-line application, but I'll assume it means quickly.

Ah I see. I'm really new to all this stuff so thank you for clearing this out!


Cached properties error with named tuples.

Hello there. Currently there's no way to use cached properties with namedTuples (or other immutable classes implemented the same way)
Trace:
AttributeError                            Traceback (most recent call last)
<ipython-input-3-7deeb8fbc12c> in <module>
----> 1 r.undirected

~/.local/share/virtualenvs/myvenv/lib/python3.7/site-packages/cached_property.py in __get__(self, obj, cls)
     33             return self._wrap_in_coroutine(obj)
     34
---> 35         value = obj.__dict__[self.func.__name__] = self.func(obj)
     36         return value
     37

AttributeError: 'MyClass' object has no attribute '__dict__'

Reproduced in https://github.com/Qu4tro/cachedproperty_immutable_classes
There was a change in python 3.5.1 and NamedTuple no longer has the __dict__ attribute. More information here: https://stackoverflow.com/a/34166617
I totally understand why it's failing, so my question is:

Are you interested in supporting this use-case?
If yes - Any implementation ideas flying around?
If not - Maybe a small note on the README would be useful.

Lmk what you think.

As a workaround, use dataclass instead of namedtuple:
from cached_property import cached_property
from dataclasses import dataclass

@dataclass(frozen=True)
class A:
    x: int
    @cached_property
    def foo(self)  -> int:
        print('A.foo called')
        return self.x + 10

a = A(1)
a.foo  # 'A.foo called'
a.foo

Yeah, it's also useful outside of this library because functools.cached_property also doesn't work with NamedTuples.
If anyone is here finding for suggestions, I've also been using functools.lru_cache for a while now, without a problem. I've kinda described it here: https://github.com/pydanny/cached-property/pull/137#issuecomment-526369393 .


Issue With Life and Destruction, A Pure Heart, and A Blank Mind

On the wiki, it says that, to do A Pure Heart, you need to complete Life and Destruction. It also says you need to complete A Blank Mind before Life and Destruction.
The issue arises when you look at the actual quest guide using /quests. First off, the quest point requirement for Life and Destruction is different than it is on the wiki. (Wiki=100, Quest Log=130).
The next issue is that the Quest Log says you need to complete A Pure Heart before you can start Life and Destruction, when according to the wiki, you should need A Blank Mind for it.
The other issue is that the wiki says you need Life and Destruction for A Pure Heart, but in the Quest Log, that's not a prerequisite for it.

Yeah the wiki wasnt updated after the reboot. When I originally wrote the quests it was A Blank Mind > A Pure Heart > Life and Destruction, but due to issues Life and Destruction ended up being released first. With the reboot I corrected it back to the right order, but the wiki was never updated to match.

Closing this because I assume it's been updated? The quest lore changes will make this easier to see.


docs: feature-request: add aliases for short codes and add new format mode

It would be great if for every rule that has a page in the documentation you could go to it not only by its full name (unused-import: https://beta.ruff.rs/docs/rules/unused-import/ ) but also by its short code (F401: https://beta.ruff.rs/docs/rules/F401/).
This would make it easier to find best practice examples for this bug.
Also, I suggest adding a separate formatting mode based on text (e.g., call it text_links). In which a link to such pages would be given next to the short error code. For example, it could look like this:
web/currency/models.py:1:1: I001 (https://beta.ruff.rs/docs/rules/I001/) [*] Import block is un-sorted or un-formatted
web/currency/models.py:10:7: N818 (https://beta.ruff.rs/docs/rules/N818/) Exception name `CurrencyNotFound` should be named with an Error suffix
web/currency/models.py:20:121: E501 (https://beta.ruff.rs/docs/rules/E501/) Line too long (152 > 120 characters)

Or, for example, add a separate setting to enable link display mode, which will add links for formatting modes: text, grouped
This would make it a lot easier to find "how to do it better" examples and links to the original rules from the linters (which are on the rules pages) and would speed up the process of correcting mistakes.
PS: In option format there is no groupped in the default values.

You actually can link to these on the main page via anchors, like https://beta.ruff.rs/docs/rules#F401, but it's not ideal. However, we do want to move towards using the human-readable names everywhere eventually, so I'm not likely to prioritize this personally.

Long names are great too, but they will take up a lot of space in the links (if implemented) within the error.
I saw this idea in the linter ShellCheck for Visual Studio Code, when hovering over the error in the IDE - a link is displayed (in the example it is SC2086 on the right) and when you click on it we get to the page: https://www.shellcheck.net/wiki/SC2086

This is very handy: if you don't know what is the right fix, go to the documentation for the rule and see examples.
PS: or make a subdomain with short links that will redirect to long links. For example: https://r.ruff.rs/F401 will redirect to https://beta.ruff.rs/docs/rules/unused-import/

It would be nice to include those links in the LSP.

One thing we could do: add a Cloudflare Worker to redirect /rules/F401 to /rules/unused-import.

That would be wonderful!
After that, someone can embed links in the error log to go directly from the console to the rule description


Moved .anything to .all and added .any

WIth the newest version old routes were broken. Specifically the ones using PathComponent.anything.
The way it was working before and broken now was:
[PathComponent.anything, "test1", "test2"]
With the newest update it is assumed that .anything is exclusively used at the end of an route as the last element, without any further paths after that.
This PR includes necessary changes to re-add the previous behavior by introducing a new type. The new type is called .anything whereas the current .anything is renamed to .catchall, to prevent confusion.
There should be no performance difference since the tree is parsed as with other components and I don't see a reason why we should not have the option to use .anything in different places other than the end.

Hmm... what's the difference between .anything and .parameter in this case? Could this concept of anything be implemented by just doing .parameter("*")?

From discussion in slack:
From the standpoint of this package anything and parameter are the same to the router. But from the perspective of a user of Vapor, caring or not about the value in that route is important.
We determined something like this might make sense:
// matches /version/:/info
router.get("version", any, "info") { ... }
// matches /users/*
router.get("users", all) { ... }

any: a discarded parameter
all: currently any, a catchall. no params should be after this

@tanner0101 Alright, now we should have it. ;)
The documentation is in the other repo, right? Like that will be added there.

See the top right where it says 100%: https://api.vapor.codes/routing/latest/Routing/index.html
If this PR were merged as is, that would become 99% 😱

@tanner0101 man, you are making me a better programmer :D I work too on projects where every minute is equal to money and so you slack off a little ;)
now it should be !

The basic routing docs don't include anything about any/all so we should be good there. Vapor's docs will, so perfect time for this change. Thanks again @proggeramlug. I will fix Vapor after I tag this. 👍


Add product edit endpoint

Hey @jeroen-hso!
Thanks for submitting this PR. Would you mind adding a test for this? otherwise, I'll add it once I have the time.
Thanks!!

@ahinkle my first integration test! I have applied your change request

Thanks


Feat: Display dzcode roadmap

Description

Display dzcode roadmap on the landing page

Type of change

New feature (non-breaking change which adds functionality)

Really cool feature @ZibanPirate although the text is black in dark mode, I dunno if you noticed


Python extension throwing various errors after VS Code update to 1.56.1

Environment data

VS Code version: 1.56.1
Extension version (available under the Extensions sidebar): v2021.5.829140558
OS and version: Windows 10 Pro ; Version	10.0.19042 Build 19042
Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.7.6 64-bit (but the same error can be replicated with any installed distribution)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: N/A
Relevant/affected Python-related VS Code extensions and their versions: N/A
Value of the python.languageServer setting: Microsoft (or any other)

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
When starting a new debug session the first breakpoint in previously working program should be hit without any warnings or errors.
Actual behaviour
The breakpoint is hit, but there are errors in the debug output even before the script 'initializes'. Reloading the window, changing Python environment or reinstalling Python, Jupyter and other affected extensions solves nothing.
Steps to reproduce:

Update VS Code in Win 10 to 1.56.1.
Set a breakpoint in a Python script.
Start debugging session - breakpoint is hit but a bunch of errors get written to the output before the main Python file even launches.

Temporary solution
The only way to get rid of these errors is to revert to previous version of the Python extension (v2021.4.765268190).
Logs

Output log, pop-up error message, debug output

Output log
User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'PythonPyTorchProfiler'
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - control'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'RunByLine - experiment'
Python interpreter path: C:\ProgramData\Anaconda3\python.exe
Starting Microsoft Python language server.
Python interpreter path: C:\Program Files (x86)\Python37-32\python.exe
Starting Microsoft Python language server.
Python interpreter path: C:\ProgramData\Anaconda3\python.exe

Pop-up message
Cannot activate the 'Python' extension because it depends on the 'Jupyter' extension, which is not loaded. Would you like to reload the window to load the extension?

Downloading https://pvsc.azureedge.net/python-language-server-stable/Python-Language-Server-win-x<IP_ADDRESS>.nupkg...
Language server download failed
Error: connect ETIMEDOUT <IP_ADDRESS>:443

pydev debugger: critical: unable to get real case for file. Details:
filename: src
drive:
parts: ['src']
(please create a ticket in the tracker to address this).

Debugger output
pydev debugger: critical: unable to get real case for file. Details:
filename: src
drive:
parts: ['src']
(please create a ticket in the tracker to address this).
Traceback (most recent call last):
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 221, in _get_path_with_real_case
    return _resolve_listing(drive, iter(parts))
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 184, in _resolve_listing
    dir_contents = cache[resolved_lower] = os.listdir(resolved)
FileNotFoundError: [WinError 3] The system cannot find the path specified: ''

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 226, in _get_path_with_real_case
    return _resolve_listing(drive, iter(parts))
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 184, in _resolve_listing
    dir_contents = cache[resolved_lower] = os.listdir(resolved)
FileNotFoundError: [WinError 3] The system cannot find the path specified: ''
pydev debugger: critical: unable to get real case for file. Details:
filename: src
drive:
parts: ['src']
(please create a ticket in the tracker to address this).
Traceback (most recent call last):
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 221, in _get_path_with_real_case
    return _resolve_listing(drive, iter(parts))
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 184, in _resolve_listing
    dir_contents = cache[resolved_lower] = os.listdir(resolved)
FileNotFoundError: [WinError 3] The system cannot find the path specified: ''

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 226, in _get_path_with_real_case
    return _resolve_listing(drive, iter(parts))
  File "c:\...\.vscode\extensions\ms-python.python-2021.5.829140558\pythonFiles\lib\python\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 184, in _resolve_listing
    dir_contents = cache[resolved_lower] = os.listdir(resolved)
FileNotFoundError: [WinError 3] The system cannot find the path specified: ''

@joyceerhl This looks like a case of Jupyter failing to start. I am assuming this is fixed in the Jupyter extension?

Yes this looks like a duplicate of https://github.com/microsoft/vscode-python/issues/16209. The resolution is to upgrade to v2021.6.832593372 of the Jupyter extension.

Closing as a dupe of #16209, please let us know if upgrading to v2021.6.832593372 doesn't work for you. Thanks and sorry for the trouble!

Solved with the new Python extension update - thanks for the help @joyceerhl! The new language server works great as well.


Update anatomy.mdx

Fixed a typo (BEST CONTRIBUTION EVER! 😅)
What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
The shortest typo fix ever... :)

Thanks a lot! all contributions are important! hope to see more :)

Thanks @manucorporat !  😅
Just started getting into it ..  will probalbly get to more more meaningful contributions down the road 😊


Content for home page

This issue will be used to collect content for the home page and link to the working content doc:
https://docs.google.com/document/d/1OIzZK-eRhMDoPr3BRZrn7HJN4r_i_5VXqSZ0P3jS66M/edit#

Closing as we aren't going back to the doc for editing any longer


No servers available for the provided ReadPreference, yet again

As @saghm asked me to do in #279 , I'm creating a new issue to discuss the problem of getting an authenticated connection to a remote MongoDB service.
The MongoDB service I'm trying to connect to is a MongoDB Atlas.
The cluster has this characteristics:

Instance size: M0 Sandbox (General)
Type: Replica Set - 3 nodes
MongoDB version: 4.0.9

The authentication mechanism used is through db.auth("user", "password").
Here is the code:
let mut options = ClientOptions::new();
options.read_preference = Some(ReadPreference::new(ReadMode::Primary, None));
let connection_string = "mongodb://<mongodb-connection-string>";
// Tried connect_with_uri_and_options too.
let client = Client::connect(connection_string, 27017)
    .expect("Could not parse Database Url");
let db = client.db("admin");
db.auth("<my-username>", "<my-password>").expect("Could not authenticate to DB");

Note: I have tried various connection strings: including/not username and password, including/not all replica addresses, including/not db to connect, including/not ClientOptions and other attempts. All having the same error: No servers available for the provided ReadPreference
Any help, tips, suggestions, useful slaps in the face are welcome!

Hi @jjgumucio! Thanks for bearing with me with regards to opening a new issue for this.
 This method is used only for connections where you don't need any custom configuration and just want to pass a hostname and port. I'd expect it to work if you used with_uri though, so this might not be the issue given that you mention you've tried that.
I also notice that you're using a 4.0+ server, which defaults to SCRAM-SHA-256 authentication. Unfortunately, this hasn't been implemented yet in this driver, which still only supports SCRAM-SHA-1. I'm actually not completely sure if this will cause an issue or not; the server expects that the driver will specify with authentication mechanisms it supports, but this also hasn't been added either. If it turns out this is the issue, I should be able to add the necessary functionality for the driver to specify this relatively easily.
The final thing that I can think of is that Atlas requires that the driver connections with SSL, which it doesn't look like you're doing here. You'll need to add the ssl feature to your mongodb dependency in your Cargo.toml (if you haven't already) and then create the ClientOptions instance with ClientOptions::with_unauthenticated_ssl (apologies for the link directly to the code; I still haven't figured out how to get docs.rs to show the documentation for optional features yet).

Thanks for the insights @saghm!
I will try the ssl connection option and removing the mongodb:// protocol specification.
I will come back with any progress or new info I get.
Thanks again!

Are there any updates on this? I'm also getting this error only that mine occurs after around 20h of uptime from within R2d2. I do not call db.auth() or run with SSL. I don't have anything specific yet, will try to debug it next week or so.

If you're not using auth or running against Atlas, my guess is that the issue you're having is not caused by the same thing (unless it's due to putting mongodb:// in front of the host without using with_uri.
As for r2d2, are you using r2d2-mongodb? We don't use r2d2 in this crate currently, and we aren't affiliated at all with the r2d2-mongodb crate.

I'm not putting mongodb:// in the host address or using r2d2-mongodb. The r2d2 implementation I have is a very basic one so I don't think it's r2d2 related. I was wondering if there was a known bug that might have caused this with Mongo 4. I'll keep you updated.

I think a workable example with connection to atlas including write and read would be extremely helpful.

@jjgumucio please check your cargo.toml has this line
mongodb = {version="0.3.12",features = ["ssl"]}
here is the reference :https://medium.com/@shnarazk/connecting-mongodb-atlas-from-rust-programs-65e4cbcbd964

@davyzhang Thanks for the tip man!
Will check later and come back with the news

Ok, did the test again and had the  {version="0.3.12",features = ["ssl"]} added to my .toml file and I get the same error.
I think It can be something about MongoDB Atlas?
Thanks for all the input

I actually wraped all the connection code to a function which is used to unify the local and altas connection method. This setup works fine the the default settings of atlas free tier replica.
use mongodb::{Client, ClientOptions, ThreadedClient};
pub fn new_mongo_conn(uri: &str, user: &str, key: &str) -> mongodb::Client {
    if user!="" {
        debug!("connect to atlas,{},{},{}",&uri,&user,&key);
        let opts = ClientOptions::with_unauthenticated_ssl(None, false);
        // opts.read_preference = Some(ReadPreference::new(ReadMode::Primary, None));
        let clnt = Client::with_uri_and_options(&uri, opts).expect("connect to mongodb error");
        clnt.db("admin").auth(user, key).expect("wrong user or key");
        clnt
    } else {
        debug!("connect to local");
        Client::with_uri(&uri).expect("connect to local mongodb error")
    }
}```

Thanks again @davyzhang!
I tried running your function like this:
 let db_url = "mongodb://development-tvmgi.mongodb.net/test?retryWrites=true";     let mongo_client = new_mongo_conn(db_url, "<DB-USER>", "<DB-PASSWORD");
And using the full database url including the user and password:
 let db_url = "mongodb://<DB-USER>:<DB-PASSWORD>@development-tvmgi.mongodb.net/test?retryWrites=true";     let mongo_client = new_mongo_conn(db_url, "<DB-USER>", "<DB-PASSWORD");
But I still get the same error:

thread 'main' panicked at 'wrong user or key: OperationError("No servers available for the provided
ReadPreference.")', src/libcore/result.rs:999:5

Firstly, your connection string is not in an atlas replica form, you can find it under altas connection section.
Notice: you should use the old format which marked as 3.4 or earlier.

looks like
mongodb://xxxxx.mongodb.net:27017,xxxx.mongodb.net:27017,xxx.mongodb.net:27017/yourdbname?replicaSet=Cluster0-shard-0

Secondly, please try to change the db "test" to your real db name like "admin" or some db that exists for later authoriaztion.
Like this
let db_url = "mongodb://xxxxx.mongodb.net:27017,xxxx.mongodb.net:27017,xxx.mongodb.net:27017/product?replicaSet=Cluster0-shard-0";

@davyzhang MY MAN!
That worked! Thank you very MUCH sir!
I can continue the project now...


CKAN mods not showing

I open CKAN, and no mods show up. I've tried running as admin, restarting my computer and even reinstalling the program entirely but nothing pops up even after all that. Has anybody else had this issue? How do I fix it?

We need the info in the issue template to answer questions like that. Please fill it out.

You selected the Replaceable filter. Switch it to All or Compatible.

that was simple, thanks!


Request to add https://tamilblasters.casa/ as provider

Hello, a small request to add https://tamilblasters.casa/ as provider. They have a large and very updates database of Indian and English Content.
Someone has already made a scraper ( addon linked attached below)
https://github.com/mhdzumair/tamilblasters_streamio_addon
But would love to download via RD

So thebeastlt I didn't know there is a duplicate issue but can u please add it bro?
I just love using torrentio for my hollywood stuff best addon there is on the market all because of you but for Indian content it would be amazing if u did add it man I know u have other addons in your mind but please consider this one also thank you.

Is this issue being worked on?

Is this issue being worked on?

Use this addon, they have now added real debrid and seedr support
https://github.com/mhdzumair/tamilblasters_stremio_addon

https://www.1tamilblasters.tel/
is the new link

I think https://github.com/mhdzumair/MediaFusion addon fills this request well and has much more Indian content, so I consider it a better alternative than adding it to Torrentio


[bug] Enforce snapshot expire will not expire all snapshots

Purpose

This PR closes #1167
Tests

No.
API and Format

No.
Documentation

No.

Test failed due to:
ConfigOptionsDocsCompletenessITCase.testCompleteness:65->compareDocumentedAndExistingOptions:209 Documentation is outdated, please regenerate it according to the instructions in paimon-docs/README.md.

Test failed due to:
ConfigOptionsDocsCompletenessITCase.testCompleteness:65->compareDocumentedAndExistingOptions:209 Documentation is outdated, please regenerate it according to the instructions in paimon-docs/README.md.

@JingsongLi Done generating docs.

Can you rebase latest master?


Add ansible.aws collection

Signed-off-by: Paul Belanger<EMAIL_ADDRESS>

Pull-request updated, HEAD is now 66c4548b314862adc70f971c496f63bd2e0f7fcb


stats.pusher.com - transfering data from hang in web browser (firefox)

Hi,
when on the landing page (or most other pages eg setting or orders/history) it seems the browser hangs trying to access stats.pusher.com. Thus the pages always look as if they are "loading" - browser session never completes load. Any ideas here? Is this because i have a free pusher account?
thanks

Same here

Same

For me it was because of uBlock Origin 1.15.24 in Firefox Add-ons.
Disabling uBlock Origin helps.

Has anybody fixed this problem?


Nested groups and sections

Thank you for the great tool! I love it! I noticed that the group and section features don't support nesting. It would be great to have that functionality so that more structure could be provided entries!

It would indeed be useful that a section would at least be able to wrap groups until the endSection tag.
Otherwise there need to be a logical user indication that this feature is purposefully left out.
I just spent 5 min puzzling why it wasn't working as I expected it to.
While I agree that it could be broken up into different pages, I do also see the benefits of having 2-3 sections on the same sheet for correlated data to easier view events related to each other.
Another approach is ofc to use the tags, but a section is a bit more logical to find visually in the text, rather than relying on tags.

I also struggled until realising, that nesting is not working.
In my case I have three main sections and each section may have several groups. Separation in multiple pages would not be beneficial.

It was quite surprising to me that groups can't be put inside sections.  They're visually different levels of hierarchy so it's quite intuitive that it would work.  I don't see a problem with confusion as long as the colors of the groups are distinct from the containing section.


Fix alt+bspace since alt+bspace is equal to alt+ctrl+h.

In my terminal, they are not the same.
BSPACE: "\u007F"
ALT-BSPACE: "\e\u007F"
CTRL-H: "\b"
CTRL-ALT-H "\e\b"

Wired, @junegunn do you use xxd command to find it. And according to https://www.physics.udel.edu/~watson/scen103/ascii.html bspace should equal to ctrl+h as well.

Here is my xxd output when type alt+bspace
 xxd
^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H^[^H
00000000: 1b08 1b08 1b08 1b08 1b08 1b08 1b08 1b08  ................

#!/usr/bin/env ruby
# frozen_string_literal: true

require 'io/console'

loop do
  chars = $stdin.getch + (begin
                            $stdin.read_nonblock(1024)
                          rescue StandardError
                            ''
                          end)
  break if [3, 4, 26].map(&:chr).include?(chars)

  p chars
end

What I got
> Alt+Backspace
"\e\b"
"\e\b"
"\e\b"

> Ctrl+H or Backspace
"\u007F"
"\u007F"
"\u007F"
"\u007F"
"\u007F"

This is your backspace key, right?

Sure 🤣
Related: https://github.com/microsoft/terminal/issues/5957#issuecomment-630659076

gg, but by right alt+ctrl+h and alt+bspace should have the same effect according to my trial.


When creating a ZosEndpoint, field endpointType is not documented and its purpose is unclear

What is the link to the document from the "main" branch?
https://www.ibm.com/docs/en/cloud-paks/z-modernization-stack/2023.1?topic=interface-importing-operator-collection
Which section(s) is the issue in?
Define a z/OS endpoint.
What needs fixing?
Explain the purpose of field endpointType and maybe give some suggestions for suitable values for this field.
The description below the field currently states: 'ZosEndpointType defines the valid ZosEndpoint Types' but this is not very helpful.
Additional context
I've raised this as a doc issue but if field endpointType is not required then we should delete it from the product.
I created an endpoint and left endpointType blank. This worked fine. Also, when I then looked at the defined endpoint, the endpointType did not appear anywhere on the panel. If this field does serve a purpose, I would have expected to see a blank field that I could possible edit to set a value for it.

Closing this here as I had raised it against the wrong category. Now raised as https://github.ibm.com/IBM-Z-and-Cloud-Modernization-Stack/zoscb/issues/2286 .


Error on Build - package androidx.anottation

Hi guys.
I follow the installation guide and i'm with this error on build:
https://imgur.com/a/nOphw4M
I was checking some issues and i found that's similar with this one:
https://github.com/rt2zz/react-native-contacts/issues/395
Thanks for helping.

If i change all androidx imports to not androidx, like:
// import androidx.annotation.NonNull;
// import androidx.core.app.ActivityCompat;
import android.support.annotation.NonNull;
import android.support.v4.app.ActivityCompat;
The error changes to:
https://imgur.com/a/u8fzkuB

I solved it.
I change all androidx import, as i said here:

If i change all androidx imports to not androidx, like:
// import androidx.annotation.NonNull;
// import androidx.core.app.ActivityCompat;
import android.support.annotation.NonNull;
import android.support.v4.app.ActivityCompat;
The error changes to:
https://imgur.com/a/u8fzkuB

Then i run: react-native link
Thats it.

in the future please share errors as text so others can find via search

Hi there! The whole react-native community will be struggling with the AndroidX transition for a while.
The community came up with a tool called jetifier that offers forwards compatibility from non-AndroidX apps to libraries (like this one) that have implemented AndroidX, by "reverse-jetifying" the source with a call to npx jetify -r so you can use the AndroidX version of the library in your non-AndroidX app, until you migrate.
I've tested it on this module and it appears to work (I use react-native-contacts in my app, I'm not just the jetifier maintainer).
I encourage you to migrate to AndroidX, but until then this can help.
When you do migrate to AndroidX you have the opposite problem with other libraries at which point you'd use jetifier in the forward direction with a call to npx jetify.
Please help spread the word so your fellow developers don't get stuck - app development is hard enough. Cheers!


Reorganize notebook sections

Merge after #232
In general, to me, the organizational structure of the light_curve_generator notebook feels hard to follow because of the section levels, names, and numbers. In particular, it would be easier to explain the new bulk-run script (#215) if the light-curve collection (serial) sections were grouped together and described as 2 main steps: define the sample, then call the archives. This PR suggests that we reorganize to the following new outline.
New outline

Make Multi-Wavelength Light Curves Using Archival Data

Learning Goals
Introduction

Input
Output
Imports

Collect Light Curves

\1. Define the sample  ("\" is only here to prevent an auto-format to "a.")

1.1 Build your own sample
1.2 Write out your sample to disk
1.3 Load the sample table from disk

\2. Query the archives

2.1 NASA-HEASARC: FERMI & Beppo SAX
2.2 IRSA: ZTF
2.3 NASA-IRSA: WISE
2.4 NASA-MAST: Pan-STARRS
2.5 NASA-MAST: TESS, Kepler and K2
2.6 NASA-MAST: Hubble Catalog of Variables (HCV)
2.7 Gaia
2.8 IceCube neutrinos

Make plots of luminosity as a function of time
Bulk Runs: Collect light curves using parallel processing
About This Notebook

Authors
Acknowledgements
References

Current outline, for reference

Make Multi-Wavelength Light Curves Using Archival Data

Learning Goals
Introduction:
Input:
Output:
Imports:
Authors:
Acknowledgements:
\1. Define the sample
\2. Find light curves for these targets in NASA catalogs

2.1 HEASARC: FERMI & Beppo SAX
2.2 IRSA: ZTF
2.3 IRSA: WISE
2.4 MAST: Pan-STARRS
2.5 MAST: TESS, Kepler and K2
2.6 MAST: Hubble Catalog of Variables (HCV)

\3. Find light curves for these targets in relevant, non-NASA catalogs

3.1 Gaia
3.3 IceCube neutrinos

\4. Parallel processing the archive calls
\5. Make plots of luminosity as a function of time
References

Thanks, I fixed the IceCube section heading.
This did not take much time and it was easier to communicate with a PR than trying to talk about first. Gathering the main code steps under one section makes the other documentation I'm working on easier. The other changes here make the notebook more clear to my eye so I figured I'd propose them, but I'm not particularly  attached to them.


Is it possible to get the text of the response instead of its value?

I would like to use the text of a response instead of the value assigned to use it in the title of a next question.
Example:
Why did you respond {textquestion1} in the previous question?
Thanks :)

@fred433 Here is the example for jQuery version:
http://plnkr.co/edit/Xb2X8EOkz8lMrbuvOBE0?p=preview
Thank you,
Andrew

There is no followup for a long time. I am closing the issue.


Add ability to listen for when a keyboard shortcut has been released

Description

This PR adds an optional parameter for a second callback to be provided when registering a shortcut. This callback will be called when the registered shortcut has been released.
Motivation and Context

I'm currently implementing push-to-talk functionality in our app and needed a way to know when the shortcut has been released in order to mute the person's microphone again. This technically could've been solved in app, but it's both cleaner and beneficial to the community if it were implemented as part of the library :)
How Has This Been Tested?

Works well in our app. I've added a test for the functionality as well, but currently it looks like the test suite is failing elsewhere.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] 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.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hey, thanks for your PR ! I'll merge this now and will publish a new version soon (still need to figure out #112 before publishing a new release) .


configurable name for CreateAt/UpdateAt

In most other orms like Gorm/Eloquote, the default names for auto timestamp/datetime fields are CreatedAt/UpdatedAt/DeletedAt.
We have to be compatible with current database structure, so hope it could be configurable

@littlexiang Please update and use the master branch of gf, and have a try.


Changing power-law distribution alpha and constant

Hi,
I am trying to change the power-law distribution alpha and constant values to introduce random indels, but I keep getting the following error for values other than the default values of alpha = 2.0 and constant = 0.5:
Introducing random INDELs based on the following parameters:

indel_count = 300
ins_del_ratio = 1
indel_size_powerlaw_alpha = 3.0
indel_size_powerlaw_constant = 1.0
Argument "9.42357754532298e" isn't numeric in numeric ge (>=) at simuG/simuG.pl line 1242.

I was hoping you could look into it!
Another note, the manual mentions that the power-law-fitted indel size distribution is p = C * (size) ** (alpha) but referring to the simuG script (line 1616) I realized the distribution is actually set to be p = C * (size) ** (-alpha). Maybe this is a typo?
Best,
Meera

Hi Meera,
Thank you very much for reporting this issue!
This problem is triggered when the calculated probability gets really small and Perl switches to use exponential notation to denote numeric numbers. In this case, the character '-' will be unexpectedly introduced and therefore breaks the code. This issue has been fixed with the latest commit now. Also, I've corrected the typos in the Manual as well. Please let me know if you encounter any further problems.
Best,
Jia-Xing

Hi Jia-Xing,
Thank you so much for your quick response! It works perfectly now!
Best,
Meera


feat(source): Support BSD header format with host and IP

:tada: This PR is included in version 1.70.0-develop.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.70.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


mkFlake: update to new fup outputsBuilder

following changes from here: https://github.com/gytis-ivaskevicius/flake-utils-plus/pull/59

Also adds the feature that digga users can write their own checks or do their own logic for package exporting, which will get merged with what digga does by default.
But this would make it impossible to remove checks.

Would it make sense at this occasion to add checks foe the different categories of other arguments that sould get merged? Just to make sure we don't break anything unadvertedly in the future.

Definitely would, I'll write up something for that soon.

bors try

bors r+


Error: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.nfc.Tag.hasTech(int)' on a null object reference

Hi, when i try to write an nfc tag on android, the following error occurs:
I´m working with the latest version
 [Error: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.nfc.Tag.hasTech(int)' on a null object reference JS:     android.nfc.tech.Ndef.get(Ndef.java:146) JS:     com.tns.Runtime.callJSMethodNative(Native Method) JS:     com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1203) JS:     com.tns.Runtime.callJSMethodImpl(Runtime.java:1083) JS:     com.tns.Runtime.callJSMethod(Runtime.java:1070) JS:     com.tns.Runtime.callJSMethod(Runtime.java:1050) JS:     com.tns.Runtime.callJSMethod(Runtime.java:1042) JS:     com.tns.gen.org.nativescript.widgets.Async_CompleteCallback.onComplete(Async_CompleteCallback.java:20) JS:     org.nativescript.widgets.Async$Http$HttpRequestTask.onPostExecute(Async.java:573) JS:     org.nativescript.widgets.Async$Http$1$1.run(Async.java:304) JS:     android.os.Handler.handleCallback(Handler.java:789) JS:     android.os.Handler.dispatchMessage(Handler.java:98) JS:     android.os.Looper.loop(Looper.java:180) JS:     android.app.ActivityThread.main(ActivityThread.java:6950) JS:     java.lang.reflect.Method.invo...

Any progress on this issue? I get the same error.

I've got the same problem with Nativescript 6.0.0.

Interestingly I can't reproduce this.. how do you trigger it exactly?
Looking at the stacktrace you could try and guard this line; only run that bit of code if tag is not null. You can go into node_modules/nativescript-nfc and give it a go.

I'm just going to assume the aforementioned issue is the problem on your end, and publish 4.0.2 in a bit.

So.. I quickly created a new project just to test the writing here (when an empty tag is discovered it should write a string to it). However, I still get this error.
I've also tried to guard the line @EddyVerbruggen mentioned earlier (thanks for your input, btw), but this part of the code is not executed, since I only try to write on empty tags, I guess.
I used Nativescript 6.0.0 and tested on Android 9.

@Fatfrido Thx for the repo. Indeed, when writing a tag I can reproduce this error.

@Fatfrido Should be much better with 4.0.3.

@EddyVerbruggen thanks for the quick fix mate. You are awesome :D

@EddyVerbruggen thanks for the fix!


[WIP] Make type_check.argname private

Jenkins, test this please.

Jenkins, test this please.

Jenkins CI test (for commit ed1081c37e9a76502496f038dd4dbf1455c44c8d, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit ed1081c37e9a76502496f038dd4dbf1455c44c8d, target branch master) succeeded!

LGTM