histone acetylation PMID:11884604, PMID:16079916, PMID:17450151

increased histone H3-K9 acetylation at rDNA during vegetative growth
increased histone H4-K12 acetylation during vegetative growth
increased histone H4-K16 acetylation during vegetative growth
increased histone H3-K14 acetylation at silent mating-type cassette during vegetative growth
increased histone H3-K14 acetylation at rDNA during vegetative growth
increased histone H4-K16 acetylation at protein coding gene during vegetative growth
increased histone H3-K9 acetylation at promoter during vegetative growth

increased histone H3-K9 acetylation at rDNA during vegetative growth FYPO:0007630
increased histone H4-K12 acetylation during vegetative growth FYPO:0007631
increased histone H4-K16 acetylation during vegetative growth FYPO:0007632
increased histone H3-K14 acetylation at silent mating-type cassette during vegetative growth FYPO:0007633
increased histone H3-K14 acetylation at rDNA during vegetative growth FYPO:0007634
increased histone H4-K16 acetylation at protein coding gene during vegetative growth FYPO:0007635
increased histone H3-K9 acetylation at promoter during vegetative growth FYPO:0007636


Subject: Pull Request: Adding withNotNull Function in Notes App

This pull request introduces the withNotNull function, an extension function that simplifies working with nullable values, into the existing codebase. The withNotNull function allows you to apply a specified lambda expression to a non-null value and return the result, or return null if the receiver value is null. This addition enhances the code's readability and safety by reducing the need for explicit null checks in various parts of the application.
Merge Request Details:
Branch: (yogesh-7:Notify:share_utils_fix)
Target Branch: (aritra-tech:Notify:master)
Changes Made
Added the withNotNull function to the project's utility library (package: com.aritra.notify.utils).
Documented the function with appropriate comments, including its purpose, parameters, return value, and usage examples.
Testing
Comprehensive unit tests have been added to validate the functionality of the withNotNull function, covering scenarios with both non-null and null receiver values.
Existing test cases have been reviewed and updated where necessary to leverage the new withNotNull function.
Documentation
Updated the project's documentation to include information about the withNotNull function, its purpose, and how to use it.
Checklist
Code compiles without errors or warnings.
New unit tests have been added, and existing tests have been reviewed and updated.
The documentation has been updated.
Code follows the project's coding standards and style guide.
Additional Notes
This feature adds a valuable utility function to simplify and enhance code safety.
Please review the code and provide feedback, so we can proceed with merging this feature into the codebase.
This pull request description includes details about the purpose of the change, the changes made, usage examples, testing, documentation updates, and a checklist for reviewers to follow. Adjust it as needed to match your specific project and review process.

Hey @yogesh-7 can you create an issue first and please raise a PR against develop not master.


Fix a static_assert, add a new one, and improve one other.

What's in this pull request?

Fix a few static_assert issues I noticed by inspection in Expr.h.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Noticed by inspection.

@swift-ci Please test.
@DougGregor Doug, can you take a look?

@swift-ci Please test.

@DougGregor Doug, can you take a look?

LGTM!

The Linux LLDB build has been broken all afternoon, and that's the only failure I see here.


npm install failing with 404 on @r35007/mock-server-cli

Hi,
just recently tried to install Mock-Server according to your instructions in readme file.
Executing
npm install -g @r35007/mock-server @r35007/mock-server-cli
results in a 404 error.
Terminal log:
node ➜ /workspace/mockServer-src $ npm install -g @r35007/mock-server @r35007/mock-server-cli
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@r35007%2fmock-server-cli - Not found
npm ERR! 404
npm ERR! 404  '@r35007/mock-server-cli@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!
Maybe, have you set the repo to private recently?
npm installs half way through and commands like mock-server are not recognized by terminal afterwards.
Happy for any feedback.
Cheers

Update to myself. Got it running in a dirty way

in terminal, execute: npm install -g @r35007/mock-server
in terminal, execute: npm view @r35007/mock-server dist.tarball, copy URL
download tarball from URL and extract contents into project folder node_modules\@r35007\mock-server\
install VS Code "Mock Server" extension
in VS Code, right click into folder explorer and select "Generate Mock Files"
in terminal, execute node server/index.js

P.S.: you are having a typo in your Mock Files
in server\index.js line 12 it says middlewares: "./middleware.js" instead of ./middlewares.js (plural s is missing)

Hi @NetDevils,

There is no separate package for mock-server-cli. The CLI is included in the package @r35007/mock-server.
If you use mock server extension, we don't want to explicitly install the mock-server package unless you want to customize the server script using node server/index.js.
Both Sorry and Thanks for pointing out the typo issue in the server\index.js file. will try to fix the extension in next release.

Thanks :)

Hi @NetDevils,
Please take the latest extension or package. I have resolved the issue. 😊

Hi @R35007,
thanks for your quick response! Much appreciated.
I have re-installed in a fresh system without global option and only mock-server package and this time cli was downloaded to the node_modules correctly. I don't know what happend the first time. It somewhat installed only half-way through.... I added a npm update to begin with, maybe my version was outdated.
All your installation guidelines (like here and here and even here) mention to execute npm install -g @r35007/mock-server @r35007/mock-server-cli, thus also the mock-server-cli package.
Reason behind why I need to have it running in node is that I use dev containers in VS Code and once I fire up the dev container I can execute mock server via container CLI, or node server/index.js. With VS Code extensions there is no command to start the mock server, other then to log into the container and execute via VS Code command pallet. Maybe you could add such a feature to the extension? If possible at all with extensions to react on terminal commands?
Right now I am also struggling to get the watcher to run.
I used mock-server --init and started the server via node server/index.js, but it is only reacting/restarting the server by changes made to .mockserverrc.js and any other file on root level. It does not watch subfolders. And even when altering the const watch = watcher.watch(mockServer.config.root); to my custom subfolder path it is not working correctly. I even added a
chokidar watcher directly, which is prompting
addDir data
File data/mydata.js has been added
add data/mydata.js

but still it does not react on changes... Could be a side effect of my dev-container, but it is working fine with your code on root level. I'm just confused. Honestly I'll give msw a shot now.

Hi @NetDevils,
Apologies for the wrong documentation. Thanks for the HeadsUp. I will update the documentation.
Reg the watcher. I am also using the chokidar watcher. If the api works for you and just the watcher is not working, try using nodemon. instead of node server.js try using nodemon server.js. This package auto restarts he server on any change in the relative file or folder. we dont need to write a scrip to restart the server.
or in the below code add your file or folder path to watch in an array
  // Restart server on change
  const watch = watcher.watch([
          mockServer.config.root,
          //... Give your file or folder path to watch here
  ]);

This will watch for the file changes.
MSW is more complex than the current package. I suggest using json-server.


Create Plan-Your-Trip page

[ ] What will weather be like?

[ ] What to bring?

[ ] What events will be occuring during the timeframe?

Other ideas:
-live cams


feat: Add support for datetime expressions

📝 Summary of Changes
Changes proposed in this pull request:

Adds a new DateTimeExpression example generator that handles date time expressions
(pact-foundation/pact-reference/issues/180)
Refactors DateTime example generator
Fixes the env var's value for logging
Refactors Date helpers
Fixes copyright headers

💁 Example
.willRespondWith(
    status: 201,
    body: [
        "start": ExampleGenerator.DateTimeExpression(expression: "@ next hour", format: dateFormat)
    ]
)

🔨 How To Test
Unit tests have been written.
Create a project where an ExampleGenerator.DateTimeExpression(format: expression: use:) is defined in a request's or response's body.
Run the test and verify the written Pact file contains the datetime generator with an expression.

Hi @surpher I created PR #85 with a change that it's a nice to have IMHO


Can not import lib after flutter pub get 6.0.1 version

Can not import lib after flutter pub get 6.0.1 version

flutter version is 2.8.1

flutter clean, delete .package pubspec.lock

flutter clean, delete .package pubspec.lock

It doesn't work for me, can't find extended_image in .pub_cache/hosted/pub.dartlang.org/

read flutter.cn first and use mirror cn
https://flutter.cn/docs/get-started/install

read flutter.cn first and use mirror cn
https://flutter.cn/docs/get-started/install

Thanks for your reply, It's work!!


Add AMP-Tube

As discussed over email, this is a Pull Request to add https://github.com/tomayac/amp-tube to the samples repository.

License ↘ 🗑


⚠ API - Lens has degraded performance

In 97550ef, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 359 ms

Resolved: API - Lens performance has improved in c504478 after 8 minutes.


test logout and login

closes #384

I am not sure how logout is supposed to work, but I don't think this url is valid for SBH3? url: http://localhost:6789/login?logout
Also, /logout is bugged in SBH3, so the usable endpoint is /do_logout for the time being. Would need to be addressed later.


cmd/go: provide advice for authors of existing packages with version v2.0+

Hi,
I was testing vgo the other day, trying to import some 3rd party dependencies that have version v2.0 or higher released on Github, but I couldn't figure out how.
Example:
Given github.com/go-chi/chi has latest version v3.3.2 released as a git tag on Github,
I'd like to import github.com/go-chi/chi/v3 in my project, develop against it and eventually vendor it via vgo vendor.
package main

import "github.com/go-chi/chi/v3"

func main() {
	_ = chi.NewRouter()
}

But since github.com/go-chi/chi didn't release a v3 module yet, I get this error:
$ vgo run main.go
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: resolving import "github.com/go-chi/chi/v3"
vgo: finding github.com/go-chi/chi (latest)
vgo: adding github.com/go-chi/chi v1.0.0
vgo: import "github.com/go-chi/chi/v3"<EMAIL_ADDRESS>open<EMAIL_ADDRESS>no such file or directory

vgo found version v1.0.0 but couldn't find "v3" subpkg. So I added an explicit version to my go.mod file and tried again:
$ cat go.mod
module github.com/VojtechVitek/vgo-test

require (
	github.com/go-chi/chi v3.3.2
)

running vgo again caused a silent side effect:
module github.com/VojtechVitek/vgo-test

require (
- 	github.com/go-chi/chi v3.3.2
+ 	github.com/go-chi/chi v0.0.0-20171222161133-e83ac2304db3
)

Hmm, seems like vgo doesn't see any v2.0+ tags? After reading some more blog posts on https://research.swtch.com (since vgo CLI help didn't seem to be very helpful / novice user friendly), I confirmed with:
$ vgo list -t github.com/go-chi/chi
github.com/go-chi/chi
	v0.9.0
	v1.0.0

Now, I might be missing something, but it's not really clear to me how can I import v2.0+ or v3.0+ of a package (should I say module?) that I don't have any control over and "is not ready yet".
Are there any guidelines for package consumers about this? Are there any guidelines for package authors? I couldn't find anything useful neither in research.swtch.com/vgo-module, nor in the accepted proposal or in the wiki.
// EDIT:
$ vgo list -t github.com/go-chi/chi/v3
github.com/go-chi/chi/v3
	v3.0.0
	v3.1.0
	v3.1.1
	v3.1.2
	v3.1.3
	v3.1.4
	v3.1.5
	v3.2.0
	v3.2.1
	v3.3.0
	v3.3.1
	v3.3.2

Ahaa, so I can list v3.0+ tags. But how do I use them in my monorepo properly?
$ vgo get github.com/go-chi/chi/v3
vgo: creating new go.mod: module github.com/VojtechVitek/vgo-test
vgo: github.com/go-chi/chi/v3 v3.3.2: missing or invalid go.mod
vgo get: missing or invalid go.mod

Quoting https://research.swtch.com/vgo-module:

We want to encourage more developers to tag releases of their packages, instead of expecting that users will just pick a commit hash that looks good to them. Tagging explicit releases makes clear what is expected to be useful to others and what is still under development. At the same time, it must still be possible—although maybe not convenient—to request specific commits.
We want to move away from invoking version control tools such as bzr, fossil, git, hg, and svn to download source code. These fragment the ecosystem: packages developed using Bazaar or Fossil, for example, are effectively unavailable to users who cannot or choose not to install these tools. The version control tools have also been a source of exciting security problems. It would be good to move them outside the security perimeter.

Can't vgo leverage the already existing v2.0+ git tags released on Github? Wouldn't it "just work" for packages that don't have any complex transitive dependencies?
I just hope that migrating monorepos from golang/dep to vgo (can we expect a migration tool, right?) will be very straight-forward. I hope we won't be blocked by some v2.0+ packages that "just work" but are not really maintained anymore and thus "not ready" for vgo.
Any guidance / feedback appreciated. Thanks!

@VojtechVitek sorry, I was away from keyboard when I sent that last message, hence it was brief.
Here is a complete example that I previously posted to #vgo on Slack. I'll close this issue because I think it answers your question but please shout if not.

Create a module using the github.com/go-chi/chi example:
$ mkdir hello
$ cd hello
$ vgo mod -init -module example.com/hello
vgo: creating new go.mod: module example.com/hello
$ cat <<EOD >hello.go
package main

import (
        "net/http"
        "github.com/go-chi/chi"
)

func main() {
        r := chi.NewRouter()
        r.Get("/", func(w http.ResponseWriter, r *http.Request) {
                w.Write([]byte("welcome"))
        })
        http.ListenAndServe(":3000", r)
}
EOD

Now because, at the time of writing, github.com/go-chi/chi:

has a major version >= 2
has not been converted to a Go (vgo) module
we want to use v3.3.2

we need to vgo get that specific version, which will be retrieved as a v0.0.0 psuedo version:
$ vgo get<EMAIL_ADDRESS>vgo: finding github.com/go-chi/chi v3.3.2
vgo: downloading github.com/go-chi/chi v0.0.0-20171222161133-e83ac2304db3

Now do a build to check all is good:
$ vgo build

And check the contents of go.mod:
$ cat go.mod
module example.com/hello

require github.com/go-chi/chi v0.0.0-20171222161133-e83ac2304db3

Hi @myitcv,
thanks for your guidance. I think I understand now - your workaround should work.

we need to vgo get that specific version, which will be retrieved as a v0.0.0 psuedo version:

This is super confusing to me and I think it will cause a lot of confusion in the Go community.
Migrating from golang/dep, I will have to start using some v.0.0.0- pseudo versions instead of v3.3.2, just because vgo can't work properly with git tags.
Well, vgo list can:
$ vgo list -t github.com/go-chi/chi/v3
github.com/go-chi/chi/v3
	v3.0.0
	v3.1.0
	v3.1.1
	v3.1.2
	v3.1.3
	v3.1.4
	v3.1.5
	v3.2.0
	v3.2.1
	v3.3.0
	v3.3.1
	v3.3.2

But other vgo command cannot. The version gets "reverted" to v.0.0.0-*, since the upstream didn't adapt to the new rules (go.mod).
Maybe there's no workaround for this from the vgo's perspective. But in that case, would it make sense to provide some guidelines for the v2.0+ pkg authors and consumers to avoid any confusion?
I'm not the only one not getting it right away, see https://github.com/go-chi/chi/issues/302.
cc @rsc

This is super confusing to me and I think it will cause a lot of confusion in the Go community.

Just to be clear, this is only required under the conditions listed in the bullet points that preceded it (reordered):

has not been converted to a Go (vgo) module
has a major version >= 2
we want to use v3.3.2

As soon as the project is converted to a module, then you're set - no pseudo-versions required. Because when chi is converted to a module, the import path becomes github.com/go-chi/chi/v3. Your example would therefore become:
package main

import (
        "net/http"
        "github.com/go-chi/chi/v3"
)

func main() {
        r := chi.NewRouter()
        r.Get("/", func(w http.ResponseWriter, r *http.Request) {
                w.Write([]byte("welcome"))
        })
        http.ListenAndServe(":3000", r)
}

and your go.mod would look like:
module example.com/hello

require github.com/go-chi/chi v3.3.2

As was observed in https://github.com/go-chi/chi/issues/302#issuecomment-367998049:

All internal references to go-chi would have to be changed to use a v3 import style.

Therefore, any "old" go (i.e. non vgo) users of the now-converted chi project would be fine so long as they use either 1.9.7 or 1.10.3.

Therefore, any "old" go (i.e. non vgo) users of the now-converted chi project would be fine so long as they use either 1.9.7 or 1.10.3.

Hmm, it's unlikely that upstream v2.0+ packages will stop supporting go 1.10 anytime soon by changing the internal import paths to "/v2" etc.
Thanks for clarification!

@VojtechVitek how many Go versions do you need to support? With 1.9.7 and 1.10.3 now out, any project supporting up to the two last Go versions (which I think is a majority) should be able to switch to Go modules soon.
The only potential problem I see is people still using old minor releases like 1.10.2. This is why I'm holding off for a few weeks before porting my v2+ projects to Go modules. I'll probably do the switch once 1.11 is out, at which point backported support will have been out for two full months.
If you need to support the latest three major Go versions, waiting until 1.11 is out should also do the trick. This obviously doesn't scale past three major Go versions, but hopefully the set of v2+ packages with that constraint is very small.

 Otherwise you will hit issues with older Go versions not being able to handle the /vX in import paths.

I'm not happy dropping support for Go <=1.10.2, <=1.9.6 and 1.8.x for a long long time. I'm talking year+, maybe until 1.12 is out.
Go was always about backwards compatibility ... and now we just break stuff because vgo can't support the existing git tags properly .. and requires new "module" notation instead :(

Are there particular cases of users not being able to upgrade bugfix/minor versions? If I was maintaining a large open-source project and a bug was reported with Go 1.9.0, my first response would be for them to try with the latest 1.9.x.
This is how I understand Go supports older versions. For example, when it is said that the last stable release recieves important bugfixes, that only concerns the latest bugfix version. I wouldn't consider 1.9.0 maintained at this point.
Having said that, I understand that it's frustrating that Go modules don't play nice with v2+ projects. Although, I'd note that this is not a breaking change. You are not forced to start using a go.mod file :)

Are there particular cases of users not being able to upgrade bugfix/minor versions?

Go 1.10.2 was released 2 months ago as a stable version. We can't just suddenly break the stable builds "just because of vgo support".
Personally, I can upgrade few monorepos and I'm done. But not everyone is that lucky.. they just want to upgrade their dependencies to the latest minor/bugfix version to get bug fixes and security patches. That's it. They don't want to worry about some "hidden" difference between Go 1.10.2 and 1.10.3 and spend hours debugging the issue.

Go 1.9.0, my first response would be for them to try with the latest 1.9.x.

Sorry, but that sounds wrong. Backward compatibility is Go's promise, one of the pillars of the language. Any version in the 1.9.x range should behave the same. Quoting from https://blog.golang.org/versioning-proposal:

We believe that the promise of compatibility made developers feel much more comfortable relying on Go for production use and is a key reason that Go is popular today

Having said that, I understand that it's frustrating that Go modules don't play nice with v2+ projects. Although, I'd note that this is not a breaking change. You are not forced to start using a go.mod file :)

Yes, we're not forced to do so.. as long as everyone in the community understands they should use v0.0.0-DATE-HASH for the time being for existing Github projects of version v2.0+. Because vgo.
Why am I bringing this up? I'm hoping someone will explain the best practices, a guideline for both package authors & consumers. I'm hoping Go will stay stable for the sake of the language and the community.

I'm hoping someone will explain the best practices, a guideline for both package authors & consumers.

As I said before, I'm also on the same boat with a couple of v2+ projects, and I too would like there to be a "best practices" or "transition guide" document published. All I am saying is that I don't consider this a breaking change - it feels like more of a temporary annoyance for part of the libs out there.

Any version in the 1.9.x range should behave the same.

Depends on what you mean by "same" :) The only promise made is backwards compatibility. There is no promise that goes forward. If your package works with 1.9.5, there's no guarantee that it will work with 1.9.1.
Of course, it is possible for packages to sasy "we support all 1.9.x versions". My point was that, in practice, most projects out there only test against the latest 1.9.x, hence 1.9.0 is in a way unsupported by much of the community.

Yes, we're not forced to do so.. as long as everyone in the community understands they should use v0.0.0-DATE-HASH for the time being for existing Github projects of version v2.0+.

This is not strictly true. As outlined above the command is actually:
vgo get<EMAIL_ADDRESS>
The command refers to a specific, released version. vgo then does the lifting required. I also note https://github.com/golang/go/issues/25898 at this point.

I'm hoping someone will explain the best practices, a guideline for both package authors & consumers. I'm hoping Go will stay stable for the sake of the language and the community.

There is absolutely nothing that requires you to make chi a module. But let's assume you elected to wait for Go 1.12 in order to convert it to a module (further assuming this is when vgo ceases to be "experimental"). In the interim, i.e. for the duration of Go 1.11 pre Go 1.12, those people using vgo (which won't be everyone because it will be opt-in) would have to follow the approach outlined above in order to use chi. When chi is made into a module, the transition would be trivial, and likely automatic (because vgo will have gained extra "fix" powers by then).
This feels like a totally satisfactory story for chi and other projects v >= 2 that choose, quite fairly, to support older versions of Go.
Just to note, vgo as a command will disappear to be "replaced" by go, driven by an environment variable for Go 1.11
/cc @rsc @bcmills in case there's anything they'd like to change/add.

Regarding:

assuming the project
has not been converted to a Go (vgo) module
has a major version >= 2
we want to use v3.3.2

And the concern:

Migrating from golang/dep, I will have to start using some v.0.0.0- pseudo versions instead of v3.3.2, just because vgo can't work properly with git tags.

I think that has changed recently in CL 124384?
Here is a snippet from the CL:

Repos written before the introduction of semantic import versioning
introduced tags like v2.0.0, v3.0.0, and so on, expecting that
(1) the import path would remain unchanged, and perhaps also
(2) there would be at most one copy of the package in a build.
We've always accommodated these by mapping them into the
v0/v1 version range, so that if you ran
go get<EMAIL_ADDRESS>
it would not complain about v8.x.x being a non-v1 version and
instead would map that version to a pseudo-version in go.mod:
require k8s.io/client-go v0.0.0-20180628043050-7d04d0e2a0a1

The pseudo-version fails to capture two important facts: first,
that this really is the v8.0.0 tag, and second, that it should be
preferred over any earlier v1 tags.
<...snip...>
This CL introduces a new version suffix +incompatible that
indicates that the tag should be considered an (incompatible)
extension of the v1 version sequence instead of part of its
own major version with its own versioned module path.
The requirement above can now be written:
require k8s.io/client-go v8.0.0+incompatible

(The +metadata suffix is a standard part of semantic versioning,
and that suffix is ignored when comparing two versions for
precedence or equality.

And here is a related snippet from the latest 'go help modules' (from tip today):

In semantic versioning, major version v0 is for initial development,
indicating no expectations of stability or backwards compatibility.
Major version v0 does not appear in the module path, because those
versions are preparation for v1.0.0, and v1 does not appear in the
module path either.
Code written before the semantic import versioning convention
was introduced may use major versions v2 and later to describe
the same set of unversioned import paths as used in v0 and v1.
To accommodate such code, if a source code repository has a
v2.0.0 or later tag for a file tree with no go.mod, the version is
considered to be part of the v1 module's available versions
and is given an +incompatible suffix when converted to a module
version, as in v2.0.0+incompatible. The +incompatible tag is also
applied to pseudo-versions derived from such versions, as in
v2.0.1-0.yyyymmddhhmmss-abcdefabcdef+incompatible.

So if I am following this particular issue, it sounds like if go-chi does not currently have have a go.mod file but is already at v3.3.2 tag, the require for your 'hello.go' example would no longer end up being a v0.0.0 pseudo-version  (which was one of the concerns raised above by @VojtechVitek), and instead would end up being a slightly friendlier:
require github.com/go-chi/chi v3.3.2+incompatible

Or in slightly more detail:
$ mkdir hello
$ cd hello
$ go mod -init -module example.com/hello

$ cat <<EOD >hello.go
package main

import (
        "net/http"
        "github.com/go-chi/chi"
)

func main() {
        r := chi.NewRouter()
        r.Get("/", func(w http.ResponseWriter, r *http.Request) {
                w.Write([]byte("welcome"))
        })
        http.ListenAndServe(":3000", r)
}
EOD

$ go get<EMAIL_ADDRESS>$ go build

And the go.mod ends up after the build as:
$ cat go.mod

module example.com/hello

require github.com/go-chi/chi v3.3.2+incompatible

Just a small remark, you even don't need to run go get<EMAIL_ADDRESS>explicitly.
The new behaviour lets you just run go build without explicit versions, the latest semver tag will be resolved automatically.
cd `mktemp -d`
go mod -init -module example.com/hello
cat <<EOD >hello.go
package main

import (
        "github.com/go-chi/chi"
)

func main() {
        _ = chi.NewRouter()
}
EOD
go build

go.mod ends up as:
$ cat go.mod
module example.com/hello

require github.com/go-chi/chi v3.3.2+incompatible

@thepudds @mwf Thanks for letting us know about the new +incompatible metadata flag! Very useful. I'm glad it's supported now.
So, as far as I understand, the github.com/go-chi/chi project needs to stick with v3.x+incompatible version for now. We can't release go.mod and thus release a new github.com/go-chi/chi/v3 import path, until we're comfortable with breaking builds for Go versions that are not aware of Go modules (pre- 1.9.7 and 1.10.3).

Hi @VojtechVitek
That sounds like a very reasonable choice for the go-chi project.
I still feel, though, that the more general original issue opened here isn't fully resolved in terms of wanting advice for maintainers of exiting v2+ project.
At the risk of writing something wildly wrong, I am going to take an initial attempt at a more comprehensive answer, and I'm hoping someone like @mwf, @myitcv, @mvdan, or @bcmills can jump in with corrections. (In general, there has been a large amount of information written about vgo/versioned modules, but it has also been evolving and tough to track the various changes and what the current advice might be).
Apologies in advance if this just ends up being noise, and this could certainly be written better and more succinctly, but in the interests of providing some grist for the mill and trying to move the ball forward, here is a rough draft:
Go 11.0 Versioned Modules: Migration and Compatibility Considerations (DRAFT)
The Go contributors are focused on providing a smooth migration from prior dependency managers and prior Go versions.
Part of the strategy is to allow for phased adoption. Different projects are expected to opt-in at different paces, and packages defined as Go 1.11 modules can be consumed by pre-1.11 Go toolsets if the proper strategies are followed.
General migration strategies for v0.x.x, v1.x.x, and v2+ projects
Some strategies for migrating to Go 1.11 modules and supporting older Go versions include:

go mod -init automatically translates the configuration from dep, glide, godep and 6 other pre-existing dependency managers into a go.mod file that produces the equivalent build.
You can use go mod -vendor to support older Go versions:

For the purpose of interoperating with older versions of Go, go mod -vendorcreates a directory named vendor in the root directory of the current module and stores there all the packages from dependency modules that are needed to support builds in the main module, with the selected versions corresponding to the go.mod file.
A go get issued by an older Go toolset will therefore use the module's vendor directory containing the proper versions of dependencies, even if that older Go toolset does not yet understand modules.

You can consider maintaining a go.mod in parallel to your prior dependency management solution and committing both sets of configuration to your repository during the transitional period.
You can consider creating a go.mod on-the-fly in CI while treating your current dependency manager as the source of truth.

Additional strategies for v2+ projects
For existing projects that are already on v2.0.0 or higher, the above strategies (such as using go mod -vender) still apply, but there are some additional considerations for v2+ projects that want to support older Go versions.
The primary issue is that v2+ projects that adopt Go 1.11 modules will update their import paths to respect semantic import versioning, with the major version now appearing within the path itself. (In contrast, this issue does not apply to a v0.x.x or v1.x.x Go 11.0 module, because semantic import versioning leaves the import paths unchanged for a v0.x.x or v1.x.x project).
For example, an older Go version such as Go 1.8 does not understand how to properly interpret a /v2 in an import statement that uses the new semantic import versioning conventions. In particular, upon seeing code containing import "example.com/foo/bar/v2", the Go 1.8 tooling would interpret the /v2 as being part of the file hierarchy.
There are currently three primary solutions for supporting older Go versions in a project on v2 or higher:

Go versions starting at 1.9.7+ and 1.10.3+ have been updated to know how to properly consume a v2+ Go 1.11 module, including how to automatically properly interpret a /v2. This means if your project is willing to restrict support to Go 1.9.7+, 1.10.3+, and 1.11+, then there is nothing else special required for a v2+ module.

Alternatively, another option is to make a v2+ Go 1.11 module compatible with the original go get behavior (e.g., to support Go 1.8) by moving or copying the project code into a /v2 subdirectory. For example, if Go 1.8 tooling sees import "example.com/foo/bar/v2", it will interpret v2 as part of the file hierarchy and then successfully find the expected files starting at bar/v2.

This approach can make sense for some authors, but some authors will prefer not to copy or move the code into a v2 subdirectory for a transitional period.

If neither approach 1. or 2. are appropriate for your v2+ project, then waiting and migrating to modules later is an entirely reasonable choice. As time goes by, Go 1.9.7 and 1.10.3 will have been out for a longer and longer period of time, which means you might be more comfortable making Go 1.9.7 and 1.10.3 required at some future date, including some projects might make the transition when Go 1.12 is released approximately 6 months after Go 1.11.

As time goes by, additional solutions might arise from the community.
If you are willing to restrict support to Go 1.9.7+, 1.10.3+, and 1.11+, the additional mechanics to release a v2+ module are as follows (using v2.0.0 as the example):

Update the go.mod file to include a /v2 at the end of the module path.
Update import paths to include /v2.
Tag the release with v2.0.0.
To avoid confusion with this approach, consider putting the v2.*.* commits on a separate v2 branch.

If you instead you have been previously releasing on master and would prefer to tag v2.0.0 on master, then consider creating a v1 branch for any future v1 bug fixes.

If instead you would like to support even older Go releases than Go 1.9.7+, 1.10.3+, the additional mechanics to release a v2+ module are:

Create a v2 directory and place a new go.mod file in that folder. The module path must end with /v2.
Copy or move the code into that v2 directory. This could be automated.
Update import paths to include /v2.
Tag the release with v2.0.0.

Finally, even if you chose not to opt-in to Go 1.11 modules now, please start using semantic versioning to tag your releases if not already doing so. This will help the overall ecosystem evolve more smoothly.

@marwan-at-work had a similar question: “Should package authors with existing v2+ versions bump the major version again when adding a module definition?”
I'm planning to discuss with @rsc when he gets back and will post some advice here.

Our conclusion was that “changing the import path” is definitely a breaking change, and authors with existing v2+ versions at non-v2+ import paths will need to change the import path when adding a module definition, so they should bump the major version again when they add the module definition.

I think that upgrading a major version only to add support for Go modules is quite severe. Major versions should be bumped for (major) changes in the library interface, not for an administrative detail like adding Go modules (which has nothing to do with the functionality of the code).
As upgrading to v3 is not desirable for me, and v1 has already been phased-out (and will not support Go modules), I'm not sure how to proceed with adding support for Go modules. I was at one point convinced that the +incompatible would come to my rescue, but it seems to be picking an older version automatically, instead of picking the latest release, why? It also seems to prefer the v0.0.0-HASH notation over v2.3.4+incompatible.
What is the advice you can give when bumping a major version is not an option, regarding releases, contents of go.mod module name and go.mod import name/version?

@tdewolff from the client perspective, you need to go get<EMAIL_ADDRESS>explicitly to get the v2.3.4+incompatible version. Otherwise, go get would fetch latest 1.x.x version instead.
@tdewolff I advice to ignore go.mod until you plan to release next major version. It's a pain, but I don't think there's any other workaround (so you don't break import paths).

I was at one point convinced that the +incompatible would come to my rescue, but it seems to be picking an older version automatically, instead of picking the latest release, why? It also seems to prefer the v0.0.0-HASH notation over v2.3.4+incompatible.

The support for +incompatible versions is only for versions that predate module support, since the existing import path may have come to implicitly mean that version. For actual modules, the module path must be unique for each major version (per semantic import versioning).

"if you are adopting modules for the first time for a pre-existing repository or set of packages that have already been tagged v2.0.0 or higher before adopting modules, then the recommended best practice is to increment the major version when first adopting modules." - wiki

So I think we're okay.


Fix cyclic import of PrimitiveOp

Summary
Fix errors in https://github.com/Qiskit/qiskit-aqua/runs/1851771582.
This cyclic-dependency is introduced by https://github.com/Qiskit/qiskit-aqua/pull/1124/.
Resolves #1528.

@manoelmarques thanks!


download pretraind models

Hello,
I hope this message finds you well. I am currently working with your project and have encountered an issue with the download links. The files I expected to be in the format of mat and pth (specifically, pytorch_result2.mat for the st model and net_last.pth for net weights) are instead in the format of rpm or dbm.
Additionally, I noticed that both files seem to be the same, and they are not in the expected mat and pth formats. Could you please provide guidance on resolving this issue? It seems like there might be a discrepancy in the file formats or a potential error in the download links.
Any assistance or clarification you can provide would be greatly appreciated.
Thank you,
Elnaz

Thanks for your question. The code would be not maintained since it was released 5 years ago. I would like to give you some suggestions if I understand your question. Please provide some links you discussed. For example, "The files I expected to be in the format of mat and pth (specifically, pytorch_result2.mat for the st model and net_last.pth for net weights) are instead in the format of rpm or dbm."

Thank you for responding. I was referring to this link about that sentence: 'https://pan.baidu.com/s/1QMp22dVGJvBH45e4XPdeKw.'


qps_worker segfaults on grpc-performance-gce1 worker

$ bins/opt/qps_worker --driver_port 10000
I1208 20:36:35.542417684    7372 socket_utils_common_posix.c:148] Disabling AF_INET6 sockets because ::1 is not available.
Segmentation fault (core dumped)

distro: Ubuntu 15.10
$ uname -a
Linux grpc-performance-gce1 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Li
nux

Same command works on my goobuntu machine no problem.

Program received signal SIGSEGV, Segmentation fault.
grpc_tcp_server_add_port (s=s@entry=0xad2860, addr=0x7fffffffe050, addr_len=28)
at src/core/iomgr/tcp_server_posix.c:467
467         allocated_port = sp->port;
#0  grpc_tcp_server_add_port (s=s@entry=0xad2860, addr=0x7fffffffe050, addr_len=28)
    at src/core/iomgr/tcp_server_posix.c:467
#1  0x000000000055f316 in grpc_server_add_insecure_http2_port (server=0xadccc0, addr=<optimized out>)
    at src/core/surface/server_chttp2.c:110
#2  0x00000000005247e4 in grpc::ServerBuilder::BuildAndStart (this=this@entry=0x7fffffffe290)
    at src/cpp/server/server_builder.cc:140
#3  0x00000000004e2175 in grpc::testing::QpsWorker::QpsWorker (this=0x7fffffffe3b0, driver_port=<optimized out>)
    at test/cpp/qps/qps_worker.cc:234
#4  0x00000000004e17aa in grpc::testing::RunServer () at test/cpp/qps/worker.cc:56
#5  main (argc=2, argv=0x7fffffffe4d8) at test/cpp/qps/worker.cc:72

sp = add_socket_to_server(s, fd, addr, addr_len);
returns 0 and allocated_port = sp->port; seqfaults.

fd = grpc_create_dualstack_socket(addr, SOCK_STREAM, 0, &dsmode); returns 0

The whole story looks like grpc_ipv6_loopback_available() returns false on GCE, but we are trying to bind ::1 address. That returns fd -1, but we are failing to handle that nicely in grpc_tcp_server_add_port.

Assigned @ctiller to triage.

Actually, this seems to be failed for <IP_ADDRESS> binding as well.


Loading previous messages not working

Loading previous messages that were sent before Chatterino was open is not functional anymore, stopped working this morning when I started Chatterino. I tried reinstalling, didn't work. This feature was working as intended yesterday.

Running latest stable version, 7.3.3

This isn't a problem specific to this fork, but rather a temporary issue with the external service used to load recent messages. It seems to currently be down and loading recent messages will fail on both the fork and upstream (and on any version).

This isn't an issue with Chatterino 7.x.x as it would be occuring on upstream as well. But it is most likely the service used to fetch recent messages is currently offline


UAA unknown issuer error

When trying to connect a bosh director with UAA authentication bosh-cli complains about unknown issuer even after providing the RootCA
$ bosh2 -e bosh-dev.sys.np.covapp.io log-in --ca-cert=/Users/suren/Downloads/intermediate_chain.pem
Requesting UAA prompts:
  Performing request GET 'https://uaa.covisintrnd.com:443/login':
    Performing GET request:
      Retry: Get https://uaa.covisintrnd.com:443/login: x509: certificate signed by unknown authority

Exit code 1

However, all intermediate as well as root certificates are provided and it is verifying perfectly.
$ openssl verify -CAfile /Users/suren/Downloads/intermediate_chain.pem uaa.crt
uaa.crt: OK

@cppforlife, I think we should be using AppendCertsFromPEM instead of AddCert both here and here.

@ssurenr seems like we are not picking up all of the necessary certs. story: https://www.pivotaltracker.com/story/show/145311531

Is there any work arounds that you can suggest?

new version of cli (https://bosh.io/docs/cli-v2.html#install) should be able to use intermediate certs.


Update cloudwatch, sdk-core, ses, sns, sqs, ssm to 2.20.96

About this PR
📦 Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

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

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

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

Superseded by #2754.


Fix mesh creation for helical geometries

See #72
Add a temporary mesh to the helical mesh creation function to simplify the mesh creation procedure

Looks good to me. Can you also add this to the testing? Should be sufficient if you simply add a line to the mesh in all the test cases before create_helix function is called.

Thanks for your review, I've added a simple line geometry to the four corresponding helix test cases. I've also checked the resulting reference files and .vtk output to verify the correctness.


Allow one level of balanced parens in link urls

Fixes #21

Hi, Aria!
I think it would be better to open separate issues if the current state of things will not make it worse (not sure about that). I'm not sure that I'll have time to come up with solution to the problems in comments very soon. Would be cool to not let this issue hang around even more. But probably it's bad idea if it will make things worse for users. Anyway, you decide. I'll try to find the time, but no promises about that.

Sounds good. I think this will make things better so I'm happy to merge it as-is!
Thanks again for fixing this, and sorry for the slow response!

No problem 👍
Can you take a look at my another PR, please? I just rebased it on master.

Yes of course! Thanks for rebasing it!


Support Kubernetes 1.16 and Linkerd

Description
added "cniVersion": "0.2.0" to make it work in Kubernetes 1.16
added NET_RAW support to PodSecurityPolicy to support Linkerd proxy injection
Release Note
I have only tested this on two clusters built on Kubernetes 1.16.  It's worked for me in all cases.  Linkerd fix was tested with edge 19.9.3 (stable 2.5 does not work on Kubernetes 1.16)
I'm not sure if this is a "proper" fix, this is just what worked for me (twice).

@rajatchopra


Should hiredis dependency be in 'devDependencies'?

Hi! I'm using this package through the Bull npm package, and am getting some build warnings when requiring Bull in my app:
Unable to resolve some modules:

  "hiredis" in app/node_modules/redis-parser/lib/hiredis.js
(os.osx.x86_64)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save hiredis

(using Meteor, but I don't think that's relevant).
It seems like you're specifying your hiredis dependency as a devDependency, and then requiring it here, and thus the app fails to build, since it doesn't install dev dependencies?
Let me know if I'm off here.

The dependency is correct in the dev dependencies. You have to require it explicitly and it'll fall back to the js parser if not installed. The issue is, that the meteor build process does not check that but tries to resolve the require directly.

Gotcha, thanks for the swift reply. I'll bring the problem with the Meteor devs.
Thanks!


[network] Moved ConnectivityManager to structured logging

Overview
Using the new structured logging schema, built up some schemas to
replace all logs in ConnectivityManager.  There were a couple logs added, and reworded.  In addition, some dead code was removed from the logging file.
Tracing logs in the main execution loop were also moved so it was easier to read :)

/land

:broken_heart: Test Failed - commit-workflow

/land

:broken_heart: Test Failed - commit-workflow

:exclamation: Invalid command

Bors help and documentation

Bors is a Github App used to manage merging of PRs in order to ensure that CI is always green. It does so by maintaining a Merge Queue. Once a PR reaches the head of the Merge Queue it is rebased on top of the latest version of the PR's base-branch (generally master) and then triggers CI. If CI comes back green the PR is then merged into the base-branch. Regardless of the outcome, the next PR is the queue is then processed.
General

This project's Merge Queue can be found here.
This project requires PRs to be Reviewed and Approved before they can be queued for merging.
Before PR's can be merged they must be configured with "Allow edits from maintainers" enabled. This is needed for Bors to be able to update PR's in-place so that Github can properly recognize and mark them as "merged" once they've been merged into the upstream branch.

Commands
Bors actions can be triggered by posting a comment which includes a line of the form /<action>.

Command
Action
Description

Land
land, merge
attempt to land or merge a PR

Canary
canary, try
canary a PR by performing all checks without merging

Cancel
cancel, stop
stop an in-progress land

Cherry Pick
cherry-pick <target>
cherry-pick a PR into <target> branch

Priority
priority
set the priority level for a PR (high, normal, low)

Help
help, h
show this help message

Options
Options for Pull Requests are configured through the application of labels.

          Option
Description

Indicates that the PR is high-priority. When queued the PR will be placed at the head of the merge queue.

Indicates that the PR is low-priority. When queued the PR will be placed at the back of the merge queue.

Before merging the PR will be squashed down to a single commit, only retaining the commit message of the first commit in the PR.

/land

:broken_heart: Test Failed - commit-workflow

💔 Test Failed - commit-workflow

This failed for some docker linting issue, so I've rebased and trying again

/land

:broken_heart: Test Failed - commit-workflow

Canceled the /land as I need to get a fix for lint-docker in for this to (maybe) based on the history land.

/land
and back in the queue

:exclamation: Land has been canceled due to this PR being updated with new commits. Please issue another Land command if you want to requeue this PR.

/land


[BUG] cloud hosted docker downloads empty icons from my icons folder, and takes forever to load

Environment
Other (Specify below)
System
ubuntu server 20.04
Version
2.1.1
Describe the problem
after loading my dashboard the first time my browser receives empty icon files and takes quite a long time to load, and all statuschecks stop functioning, restarting my container makes me able to load my dashboard proberly once and then it stops working again.  have tried going through the trouble shooting and other issues that could be related and nothing really seems like it is the same problem as mine.

i have been spending a few hours trying to get this to work. and have gotten nowhere.
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

just noticed if i let the page load it eventually gets the icons more than 2 minuttes later.


cmf pack isn't solving the package root for the working directory

Every command that works on a specific package should automatically solve the package root from the current directory, so we don't have to move to the package root to run a simple command. If the command works at a repository level, it should solve that location automatically.
pack isn't doing that so it needs fixing. We should also review the other commands.

Fixed by https://github.com/criticalmanufacturing/cli/pull/411.


How to save the dice explainer object to file?

Hi, I'm trying to write the dice_ml object to a file and I'm getting the follow error:
backend = 'TF'+tf.__version__[0]
dice_model = dice_ml.Model(model=model, backend=backend)

exp = dice_ml.Dice(d, dice_model)

from joblib import load, dump

with open("explainer_dice.joblib", "wb") as f:
    dump(exp, f, compress="lz4")

TypeError: cannot pickle '_thread.RLock' object

Hi @PJarbas,
This might be because of logger in the explainer. Could you share the exact code that you are trying to run and which fails in the explainer? Maybe, we can make the dice explainer pickleable.
Regards,

I'm tryin to run the simple code from the docs
import dice_ml
from dice_ml.utils import helpers # helper functions

# Tensorflow libraries
import tensorflow as tf
from tensorflow import keras
from joblib import load, dump

# http://interpret.ml/DiCE/notebooks/DiCE_with_advanced_options.html

dataset = helpers.load_adult_income_dataset()

d = dice_ml.Data(dataframe=dataset, continuous_features=['age', 'hours_per_week'], outcome_name='income')

train, _ = d.split_data(d.normalize_data(d.one_hot_encoded_data))
X_train = train.loc[:, train.columns != 'income']
y_train = train.loc[:, train.columns == 'income']

ann_model = keras.Sequential()
ann_model.add(keras.layers.Dense(20, input_shape=(X_train.shape[1],), kernel_regularizer=keras.regularizers.l1(0.001), activation=tf.nn.relu))
ann_model.add(keras.layers.Dense(1, activation=tf.nn.sigmoid))

ann_model.compile(loss='binary_crossentropy', optimizer=tf.keras.optimizers.Adam(0.01), metrics=['accuracy'])
ann_model.fit(X_train, y_train, validation_split=0.20, epochs=2, verbose=0, class_weight={0:1,1:2})
# the training will take some time for 100 epochs.

backend = 'TF'+tf.__version__[0] # TF1
model = dice_ml.Model(model=ann_model, backend=backend)

exp = dice_ml.Dice(d, model)

with open("explainer_dice.joblib", "wb") as f:
    dump(exp, f, compress="lz4")

and I'm getting the same error
TypeError: can't pickle _thread.RLock objects

Hi @PJarbas, thanks for bringing this up! We haven't thought about saving dice object earlier.
So DiCE explainer object takes in a data and a model object as parameters. Your error is perhaps due to how TensorFlow saves and loads .h5 models, which I don't think we can address. Check out this issue: https://github.com/matterport/Mask_RCNN/issues/1126 which talks about similar problems.
However, I just verified and you can pickle/unpickle DiCE's data object and PyTorch model object just fine. So you can pickle DiCE explainer if you are using PyTorch models.

ok, thanks for the feedback


runnable module description

Added a module description. Added batch description.

The check error (linting) is not related to this PR:

./scripts/check_pydantic.sh .
./scripts/lint_imports.sh
poetry run ruff .
[ "langchain_community" = "" ] || poetry run ruff format langchain_community --diff
966 files already formatted
[ "langchain_community" = "" ] || poetry run ruff --select I langchain_community
[ "langchain_community" = "" ] || mkdir -p .mypy_cache && poetry run mypy langchain_community --cache-dir .mypy_cache
langchain_community/utilities/requests.py:144: note: Maybe you forgot to use "await"?
langchain_community/utilities/requests.py:144: note: Error code "misc" not covered by "type: ignore" comment
langchain_community/vectorstores/thirdai_neuraldb.py:29: error: Function is missing a type annotation  [no-untyped-def]
Found 1 error in 1 file (checked 966 source files)
make: *** [Makefile:50: lint_package] Error 1
Error: Process completed with exit code 2.

@baskaryan  PR is ready for review

@baskaryan  Thanks!


[EDIT] I.14 Swap Gate Incorrect Truth Table

Feature details
In the Multi-qubit gate reference table, SWAP|11> is given as |10> but it should be |11>.
Additional information
No response

Closing as has been updated in the live site.


How to pass an order after checkout

Hello there
we are using the pro version, and it is going well so far,
but we can't find to validate a cart into order after setting a carrier & address.

Hello there
we are using the pro version, and it is going well so far, but we can't find to validate a cart into order after setting a carrier & address.

Hello,
thank you.
Yes we do not have any a separate API for validateOrder, because it should happen within payment APIs and payment modules. However, if you just want to call API to place order, you can use bankwire or paybycheck endpoints.

Well let me explain the case,
the current PrestaShop store doesn't have any online payment solution, all payments are made on delivery.
we followed the documentation  :
1- create a cart
2- set address
3- set carrier
4- how we can submit now?
we see that there is an API under Admin API there is create order API, but I don't believe that's for users.

Well let me explain the case, the current PrestaShop store doesn't have any online payment solution, all payments are made on delivery. we followed the documentation : 1- create a cart 2- set address 3- set carrier 4- how we can submit now? we see that there is an API under Admin API there is create order API, but I don't believe that's for users.

No you should not use the Admin API, that's for accepting orders from outside of the system, you are correct it's not for users. As I said it should be done through a payment module, you can simply have an API to to just call validateOrder method, or we can simply add support for COD module, so you can do your payments through COD module.

It will be awesome if we have COD support, in meantime, I will try to create some API to call validateOrder.

It will be awesome if we have COD support, in meantime, I will try to create some API to call validateOrder.

I added COD support to v2.4.4 version. You can check it.

Thanks buddy 😚
is it included in the pro version?

Thanks buddy 😚 is it included in the pro version?

welcome ;) We will add it soon.

Pro version is also updated.
So, I close this issue.


Label is throwing an exception

And I have no idea what I'm doing wrong. I linked the QuartzCore framework, imported it and then declared my label as so:  @IBOutlet weak var songNameLabel: MarqueeLabel!
then added the following properties in viewDidLoad
songNameLabel.type = .Continuous
songNameLabel.scrollDuration = 8.0
songNameLabel.fadeLength = 15.0
but the app crashes and it shows an error at songNameLabel.type = .Continuous :(
Any ideas?

Hmm, what's the execption? Is there any other info you can pull from the debugger?
On Sat, Apr 25, 2015 at 8:33 PM, Cyril Zakka<EMAIL_ADDRESS>wrote:

And I have no idea what I'm doing wrong. I linked the QuartzCore framework, imported it and then declared my label as so:  @IBOutlet weak var songNameLabel: MarqueeLabel!
then added the following properties in viewDidLoad
songNameLabel.type = .Continuous
songNameLabel.scrollDuration = 8.0
songNameLabel.fadeLength = 15.0
but the app crashes and it shows an error at songNameLabel.type = .Continuous :(
Any ideas?
Reply to this email directly or view it on GitHub:
https://github.com/cbpowell/MarqueeLabel-Swift/issues/4

log just says (lldb)

Well that's not a lot to go on, but are you sure your songNameLabel is an instance of MarqueeLabel? Check in Interface Builder to make sure you've set the Custom Class value to MarqueeLabel:

It would immediately crash upon reaching the songNameLabel.type = .Continuous line if it's still a normal UILabel, as UILabel obviously doesn't have that property.

Thanks 😊 Forgot I'd declared them in IB


error MSB4030: "1" is an invalid value for the "Optimize" parameter of the "Csc" task.

Hello,
Please clarify what fix or change I need to apply for the following.
Ubuntu 16.04 xenial x86_64
I have installed the following
ii  dotnet-host                                2.1.5-1                                      amd64        Microsoft .NET Core Host - 2.1.5
ii  dotnet-hostfxr-2.0.9                       2.0.9-1                                      amd64        Microsoft .NET Core Host FX Resolver - 2.0.9 2.0.9
ii  dotnet-hostfxr-2.1                         2.1.5-1                                      amd64        Microsoft .NET Core Host FX Resolver - 2.1.5 2.1.5
ii  dotnet-hosting-2.0.9                       2.0.9-1                                      amd64        Microsoft .NET Core 2.0.9 Linux Server Hosting
ii  dotnet-runtime-2.0.9                       2.0.9-1                                      amd64        Microsoft .NET Core Runtime - 2.0.9 Microsoft.NETCore.App 2.0.9
ii  dotnet-runtime-2.1                         2.1.5-1                                      amd64        Microsoft .NET Core Runtime - 2.1.5 Microsoft.NETCore.App 2.1.5
ii  dotnet-runtime-deps-2.1                    2.1.5-1                                      amd64        dotnet-runtime-deps-2.1 2.1.5
ii  dotnet-sdk-2.1                             2.1.403-1                                    amd64        Microsoft .NET Core SDK 2.1.403
tony is standard user
tony@ubuntu1604:~/sandbox/app$ dotnet publish -c Release -r linux-x64
Microsoft (R) Build Engine version 15.8.169+g1ccb72aefa for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
Restore completed in 55.81 ms for /home/tony/sandbox/app/app.csproj.
/usr/share/dotnet/sdk/2.1.403/Roslyn/Microsoft.CSharp.Core.targets(91,10): error MSB4030: "1" is an invalid value for the "Optimize" parameter of the "Csc" task. The "Optimize" parameter is of type "System.Boolean". [/home/tony/sandbox/app/app.csproj]
tony@ubuntu1604:~/sandbox/app$
app.csproj looks like :

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <AssemblyName>mssqlsmoapp</AssemblyName>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.Extensions.CommandLineUtils" Version="1.1.1" />
    <PackageReference Include="Microsoft.SqlServer.SqlManagementObjects" Version="140.17235.0" />
    <PackageReference Include="Newtonsoft.Json" Version="11.0.2" />
    <PackageReference Include="NLog.Extensions.Logging" Version="1.0.1" />
    <PackageReference Include="System.Data.SqlClient" Version="4.4.3" />
  </ItemGroup>
</Project>

I can reproduce the error message when I set the environment variable Optimize to 1:
$ export Optimize=1
$ dotnet publish -c Release -r linux-x64
Microsoft (R) Build Engine version <IP_ADDRESS>536 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restoring packages for /home/svick/coreapp/coreapp.csproj...
  Generating MSBuild file /home/svick/coreapp/obj/coreapp.csproj.nuget.g.props.
  Generating MSBuild file /home/svick/coreapp/obj/coreapp.csproj.nuget.g.targets.
  Restore completed in 721.48 ms for /home/svick/coreapp/coreapp.csproj.
/usr/share/dotnet/sdk/2.1.105/Roslyn/Microsoft.CSharp.Core.targets(123,10): error MSB4030: "1" is an invalid value for the "Optimize" parameter of the "Csc" task. The "Optimize" parameter is of type "System.Boolean". [/home/svick/coreapp/coreapp.csproj]
$ export Optimize=
$ dotnet publish -c Release -r linux-x64
Microsoft (R) Build Engine version <IP_ADDRESS>536 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 99.88 ms for /home/svick/coreapp/coreapp.csproj.
  coreapp -> /home/svick/coreapp/bin/Release/netcoreapp2.0/linux-x64/mssqlsmoapp.dll
  coreapp -> /home/svick/coreapp/bin/Release/netcoreapp2.0/linux-x64/publish/

Is it possible that you have the environment variable Optimize set? What does echo $Optimize print?

tony@ubuntu1604:~/sandbox/tsm/tdp/agents/sqlonlinux/mssqlsmoapp$ echo $Optimize
tony@ubuntu1604:~/sandbox/tsm/tdp/agents/sqlonlinux/mssqlsmoapp$

Actually i have an OPTIMIZE env var.
tony@ubuntu1604:~/sandbox/tsm/tdp/agents/sqlonlinux/mssqlsmoapp$ echo $OPTIMIZE
1
If i open a new terminal and make sure i dont have that OPTIMIZE the dotnet publish completes OK w/o error. Inside the diag build log it shows Optimize = true
I have to mention that it works nice on Suse but not on Ubuntu.
It looks specific to dotnet core on Ubuntu 16.04 xenial.

Did you try to set OPTIMIZE to true? Does that work on Ubuntu?

I unset the OPTIMIZE .
OPTIMIZE= dotnet publish ...
that way it calls dotnet w/o OPTIMIZE set at all. Other idea ?

@iga1976 with OPTIMIZE unset, do you still see the issue?
If you do, you can either track down where it comes from (from the logs), or you can try it on a brand new machine/VM from scratch. It seems like your machine is misconfigured or something.


new group: Zerotolerance

host location
http://zhuobnfsddn2myfxxdqtpxk367dqnntjf3kq7mrzdgienfxjyllq4rqd.onion/
group name
zerotolerance
group information
No response
host
v3 (onion)
parser
No response

closing this as I haven't seen it online in quite some time. will look again if it crops back up!


MacOS development migrations fail

This is a (multiple allowed):

[x] bug

Version of project-template-cakephp: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

What you did
during
./bin/build app:install DB_NAME="app",PROJECT_NAME="My Project",PROJECT_VERSION="v1.0.0"

received
(...)
 [Qobo\Cakephp\Migration] Running ./bin/cake migrations migrate -p 'Search' --connection='test'
Exception: Module `Users` does not exist. in [/Users/swank/projects/david/project-template-cakephp/vendor/qobo/cakephp-utils/src/Module/ModuleRegistry.php, line 122]
2020-08-02 22:55:05 Error: [Qobo\Utils\Module\Exception\MissingModuleException] Module `Users` does not exist. in /Users/swank/projects/david/project-template-cakephp/vendor/qobo/cakephp-utils/src/Module/ModuleRegistry.php on line 122
Stack Trace:
#0 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Core/ObjectRegistry.php(94): Qobo\Utils\Module\ModuleRegistry->_throwMissingClassError('Users', NULL)
#1 /Users/swank/projects/david/project-template-cakephp/vendor/qobo/cakephp-utils/src/Module/ModuleRegistry.php(77): Cake\Core\ObjectRegistry->load('Users', Array)
#2 /Users/swank/projects/david/project-template-cakephp/src/Model/Table/UsersTable.php(42): Qobo\Utils\Module\ModuleRegistry::getModule('Users')
#3 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Table.php(299): App\Model\Table\UsersTable->initialize(Array)
#4 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Locator/TableLocator.php(293): Cake\ORM\Table->__construct(Array)
#5 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Locator/TableLocator.php(249): Cake\ORM\Locator\TableLocator->_create(Array)
#6 /Users/swank/projects/david/project-template-cakephp/vendor/cakedc/users/src/Controller/Traits/CustomUsersTableTrait.php(36): Cake\ORM\Locator\TableLocator->get('Users')
#7 /Users/swank/projects/david/project-template-cakephp/vendor/qobo/cakephp-search/src/Model/Table/SavedSearchesTable.php(49): Search\Model\Table\SavedSearchesTable->getUsersTable()
#8 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Table.php(299): Search\Model\Table\SavedSearchesTable->initialize(Array)
#9 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Locator/TableLocator.php(293): Cake\ORM\Table->__construct(Array)
#10 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/Locator/TableLocator.php(249): Cake\ORM\Locator\TableLocator->_create(Array)
#11 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/ORM/TableRegistry.php(148): Cake\ORM\Locator\TableLocator->get('Search.SavedSea...', Array)
#12 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/TableFinderTrait.php(168): Cake\ORM\TableRegistry::get('Search.SavedSea...')
#13 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/TableFinderTrait.php(111): Migrations\Command\Dump->fetchTableName('Search.SavedSea...', 'Search')
#14 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/TableFinderTrait.php(58): Migrations\Command\Dump->getTableNames('Search')
#15 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/Command/Dump.php(92): Migrations\Command\Dump->getTablesToBake(Object(Cake\Database\Schema\Collection), Array)
#16 /Users/swank/projects/david/project-template-cakephp/vendor/symfony/console/Command/Command.php(255): Migrations\Command\Dump->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#17 /Users/swank/projects/david/project-template-cakephp/vendor/symfony/console/Application.php(987): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#18 /Users/swank/projects/david/project-template-cakephp/vendor/symfony/console/Application.php(255): Symfony\Component\Console\Application->doRunCommand(Object(Migrations\Command\Dump), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#19 /Users/swank/projects/david/project-template-cakephp/vendor/symfony/console/Application.php(148): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#20 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/Shell/MigrationsShell.php(108): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#21 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/Shell.php(531): Migrations\Shell\MigrationsShell->main('migrations', 'dump')
#22 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/Shell/MigrationsShell.php(169): Cake\Console\Shell->runCommand(Array, true, Array)
#23 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/ShellDispatcher.php(229): Migrations\Shell\MigrationsShell->runCommand(Array, true, Array)
#24 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/ShellDispatcher.php(181): Cake\Console\ShellDispatcher->_dispatch(Array)
#25 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/Shell.php(418): Cake\Console\ShellDispatcher->dispatch(Array)
#26 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/Shell/MigrationsShell.php(128): Cake\Console\Shell->dispatchShell('migrations dump...')
#27 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/Shell.php(531): Migrations\Shell\MigrationsShell->main('migrations', 'migrate')
#28 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/migrations/src/Shell/MigrationsShell.php(169): Cake\Console\Shell->runCommand(Array, true, Array)
#29 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/CommandRunner.php(384): Migrations\Shell\MigrationsShell->runCommand(Array, true)
#30 /Users/swank/projects/david/project-template-cakephp/vendor/cakephp/cakephp/src/Console/CommandRunner.php(162): Cake\Console\CommandRunner->runShell(Object(Migrations\Shell\MigrationsShell), Array)
#31 /Users/swank/projects/david/project-template-cakephp/bin/cake.php(12): Cake\Console\CommandRunner->run(Array)
#32 {main}

 [Qobo\Cakephp\Migration]  Last command failed to run
 [Qobo\Cakephp\Migration]  Exit code 1
 [error]  Failed to do app:install

What happened
Not sure
What you expected to happen
completed application install

tag v50.3.0 has a very similar error, but with the "Things" module.

tag v50.2.3 no longer has these errors.
Perhaps this is related to the accompanying downgrade of the cakephp-csv-migrations module to v36.2.1.


Upgrade xstream for CVE-2022-41966 and CVE-2022-40151

It seems that we should upgrade xstream to 1.4.20 to prevent exposing CVE-2022-41966 and CVE-2022-40151 CVEs indirectly.

@tkobayas @mariofusco could you please review this PR?

Fixed by https://github.com/mvel/mvel/commit/5149868113d725038af94b1b241368af95af1054


Updated ru translations

Hello! I did the following:

makemessages -l ru
corrected and added ru translations
compilemessages

Did you do everything right?

I'll check everything thoroughly this week

Спасибо!


rm Raft related code

rename some function and variables name that was related to Raft.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #581   +/-   ##
=======================================
  Coverage   20.38%   20.38%
=======================================
  Files          29       29
  Lines        1678     1678
=======================================
  Hits          342      342
  Misses       1293     1293
  Partials       43       43

👍


Latest release crashed 10 minutes into the bot's runtime

To reproduce, download ashscan master, delete ChatSharp.dll from packages/net45 and replace the reference with latest ChatSharp.
Attached is the portion of the log file
<EMAIL_ADDRESS>PRIVMSG ##TopChat :I'm a newbie
<EMAIL_ADDRESS>PRIVMSG ##TopChat :You?
<EMAIL_ADDRESS>PRIVMSG ##TopChat :Did a whois on AntiSpam
:card.freenode.net PONG card.freenode.net :card.freenode.net
<EMAIL_ADDRESS>PRIVMSG ##TopChat :How long you been around?
:card.freenode.net PONG card.freenode.net :card.freenode.net
:card.freenode.net PONG card.freenode.net :card.freenode.net
:drug!Elite14636@gateway/shell/elitebnc/x-qrqpjozwqohdlroj PRIVMSG ##TopChat :Dax_: a newbie eh?
:card.freenode.net PONG card.freenode.net :card.freenode.net
<EMAIL_ADDRESS>PRIVMSG ##TopChat :brb
<EMAIL_ADDRESS>QUIT :Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )
:drug!Elite14636@gateway/shell/elitebnc/x-qrqpjozwqohdlroj PRIVMSG ##TopChat :why did you whois AntiSpam
:drug!Elite14636@gateway/shell/elitebnc/x-qrqpjozwqohdlroj PRIVMSG ##TopChat :why does it matter how long i been around
:card.freenode.net PONG card.freenode.net :card.freenode.net
:drug!Elite14636@gateway/shell/elitebnc/x-qrqpjozwqohdlroj PRIVMSG ##TopChat :<.<
:card.freenode.net PONG card.freenode.net :card.freenode.net
<EMAIL_ADDRESS>PRIVMSG ##TopChat :Was just asking
<EMAIL_ADDRESS>PRIVMSG ##TopChat :Getting to know the place
<EMAIL_ADDRESS>JOIN ##TopChat
Default Critical: 0 : The service threw an unhandled exception System.InvalidOperationException: That channel already exists in this collection.
at ChatSharp.ChannelCollection.Add (ChatSharp.IrcChannel channel) [0x00000] in :0
at ChatSharp.Handlers.ChannelHandlers.HandleJoin (ChatSharp.IrcClient client, ChatSharp.IrcMessage message) [0x00000] in :0
at ChatSharp.IrcClient.HandleMessage (System.String rawMessage) [0x00000] in :0
at ChatSharp.IrcClient.DataRecieved (IAsyncResult result) [0x00000] in :0

@SirCmpwn This is really killing us. This bug was introduced by the last changeset that you committed to the master. Did you test it? IMO you should commit new advancements to a branch and run your bots a few days with it before merging it into master. And merge it by creating a PR and have some people review it.

https://github.com/SirCmpwn/ChatSharp#development--contributing

I understand that. All I am saying is. We need to find a way stop faulty commits from finding their way into master.

I'm not convinced that this is faulty. I've been running this version of ChatSharp since it was written without any problems.

And I can't diagnose it without debug symbols, by the way.

You need the PDB? Or you need the crash dump?

I need a stack trace with line numbers and file names.

Also. Join your bot in ##chat on freenode. I can almost guarantee it will crash.

My bot runs on 11 channels on 4 different networks. I'm sure it's fine.

Here is the stack trace from last night's crash
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Where[TSource](IEnumerable1 source, Func2 predica
te)
at Ashscan.Bot.IrcController.<>c__DisplayClass2b.b__26(IrcCh
annel channel, IrcUser user) in c:\Dev\ashscan\ashscan\Projects\ashscan.Bot\IrcC
ontroller.cs:line 213
at System.Linq.Enumerable.d__313.MoveNext()    at System.Linq.Buffer1..ctor(IEnumerable1 source)    at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
at Ashscan.Bot.IrcController.GetChannelUsers(String channelName) in c:\Dev\as
hscan\ashscan\Projects\ashscan.Bot\IrcController.cs:line 209
at ExploitFinder.AddinBootstrapper.b__0(String channel) in c:\Dev\ashsca
n\ashscan\Projects\ExploitFinder\AddinBootstrapper.cs:line 79
at ExploitFinder.AggregateHostExploitFinder.<>c__DisplayClass2.b__0() in
c:\Dev\ashscan\ashscan\Projects\ExploitFinder\AggregateHostExploitFinder.cs:lin
e 46
at ExploitChecker.AbusiveNickExploitFinder.Run(IUserInfo user, Func1 voicedN icks) in c:\Dev\ashscan\ashscan\Projects\ExploitFinder\AbusiveNickExploitChecker .cs:line 36    at ExploitFinder.AggregateHostExploitFinder.Run(IUserInfo user, String channe l) in c:\Dev\ashscan\ashscan\Projects\ExploitFinder\AggregateHostExploitFinder.c s:line 46    at ExploitFinder.AddinBootstrapper.HandleJoin(String channel, IUserInfo user)  in c:\Dev\ashscan\ashscan\Projects\ExploitFinder\AddinBootstrapper.cs:line 93    at ExploitFinder.AddinBootstrapper.<Run>b__3(Tuple2 j) in c:\Dev\ashscan\ash
scan\Projects\ExploitFinder\AddinBootstrapper.cs:line 85
at System.Reactive.AnonymousSafeObserver1.OnNext(T value)    at System.Reactive.Linq.ObservableImpl.Select2._.OnNext(TSource value)
at System.Reactive.Subjects.Subject1.OnNext(T value)    at System.Reactive.Linq.ObservableImpl.FromEventPattern.Impl2.<>c__DisplayCl
ass4.b__1(Object sender, TEventArgs eventArgs)
at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
at ChatSharp.IrcClient.OnUserJoinedChannel(ChannelUserEventArgs e) in c:\Dev
temp\ChatSharp-master\ChatSharp\IrcClient.cs:line 454
at ChatSharp.Handlers.ChannelHandlers.HandleJoin(IrcClient client, IrcMessage
message) in c:\Dev\temp\ChatSharp-master\ChatSharp\Handlers\ChannelHandlers.cs:
line 17
at ChatSharp.IrcClient.HandleMessage(String rawMessage) in c:\Dev\temp\ChatSh
arp-master\ChatSharp\IrcClient.cs:line 280
at ChatSharp.IrcClient.DataRecieved(IAsyncResult result) in c:\Dev\temp\ChatS
harp-master\ChatSharp\IrcClient.cs:line 270
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionCo
ntext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr u
serToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Stopping the IrcExploitChecker service
The IrcExploitChecker service has stopped.

I had accidentally hit the close button

Here is the stack trace
Critical: 0 : The service threw an unhandled exception,
System.InvalidOperationException: That channel already exists in this collection.   at ChatSharp.ChannelCollection.Add(IrcChannel channel) in c:\Dev\temp\ChatSha
rp-master\ChatSharp\ChannelCollection.cs:line 29
at ChatSharp.Handlers.ChannelHandlers.HandleJoin(IrcClient client, IrcMessage message) in c:\Dev\temp\ChatSharp-master\ChatSharp\Handlers\ChannelHandlers.cs: line 13
at ChatSharp.IrcClient.HandleMessage(String rawMessage) in c:\Dev\temp\ChatSharp-master\ChatSharp\IrcClient.cs:line 280
at ChatSharp.IrcClient.DataRecieved(IAsyncResult result) in c:\Dev\temp\ChatSharp-master\ChatSharp\IrcClient.cs:line 270
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)   at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr u
serToken)   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

To reproduce this. connect to network and join a channel, then command the bot to Part it, and a few seconds later rejoin the same channel. I just tried this and it crashed.


On the proposed ccompiler.has_flag method

There is an ongoing discussion that was triggered by a proposed patch to distutils.

The patch consists in adding a new has_flag function to distutils' ccompiler, aside of has_function to detect whether the compiler supports certain compilation flag. It is similar to cmake's CHECK_CXX_COMPILER_FLAG.

Detecting whether a compiler support such a flag is crucial for extension authors who need e.g. C++11 support in their code, so as to be able to output meaningful error messages when not available, or to use such a flag optionally when it improves performance. This becomes crucial since we have new flavors of the C++ programming language every 3 years (C++11/14/17).

This is obviously a backward compatible change since it is a new method, although it triggered a discussion on whether one should allow incremental improvements to distutils.
Here are links to the top-most messages of two threads:

About the proposed feature:  https://mail.python.org/pipermail/distutils-sig/2016-August/029469.html
What is the official position on distutils: https://mail.python.org/pipermail/distutils-sig/2016-August/029595.html

My proposal is the following:

add the patch to distutils.ccompiler. Incremental improvement is good! More reasons to adopt more recent python versions.
optionally add it to ccompiler via setuptools for earlier versions of python.

ping @jaraco

I have no objections, and my opinion is that if someone is willing to propose the changes via a pull request and address the ramifications of those changes to stability, it will be accepted.


Implement full authentication for "caching_sha2_password"

When SSL is enabled and the fast authentication phase fails, "caching_sha2_password" has a full authentication phase.
Currently, SSL has supported, should support full authentication of "caching_sha2_password" to better support for MySQL 8.x.

It should be support now, I will add unit tests for MySQL 8.x

It has supported in bc3dc8025023b066ebe097da7a26ffa9b1464464.

if you are facing "caching_sha2_password" error during connectivity of your mysql database using python ,
go through this
https://www.youtube.com/watch?v=YNq-EuQEJos


Fix Validate of Image with tag containing latest

Catlin throws error when the image with tag stable-2.12-latest
comes which is still valid. Replacing the check from Contains to
EqualFold so that it throws error iff tag latest comes.
Signed-off-by: vinamra28<EMAIL_ADDRESS>

/lgtm

/lgtm
/approve


docs(pie-docs): DSW-424 add iconography code page

"pie-docs": minor
[Added] - Iconography code examples page
[Added] - TSX support to Prism js

I leave some comments here Jamie, let me know once these changes are made, so I can take a second look, thanks!

Table of content that exists in Overview is too long, and unnecessary to show every section, I advise to keep the main titles for now (Our packages, Vanilla, React, Vue, Web Components). I’m benchmarking some solutions to show the table of content in a way that doesn’t take so much space on the main container, once I have a solution for table of content we’ll show every section in it.
The code snippet doesn’t need a shadow, so please remove the shadow, the radius of div.code-toolbar should be 12px, the radius of the container pre.language-sh doesn’t match the parent (should be 11px)
The bottom right corner of the copy button should have 12px radius

Thanks @nazanin!
Let's create a separate ticket to address style concerns regarding the code canvas and copy buttons as these are not new and out of scope for this work.
I've pushed a shortened contents table 👍


Load Compressed Tensors Models with run_compressed=False

SUMMARY:
Load Compressed Tensors Models with run_compressed=False
TEST PLAN:
Made tests to check that run_compressed=False (new pathway) do not have any Compressed Linear
Made tests to check that run_compressed=True (AutoModelForCausalLM pathway) has Compressed Linear.

@dsikka
sure thing

Dont need this no more, closing this pr


feat(DataGrid): Add padding to the first cell

This is not needed that much anymore because of the increased default cell paddings.


Release/1.9.0

Let's wait for tests to pass before doing a release.

Yes, lets do that. I created an issue for this, we can pick it up later


Tracking issues of opendalfs 0.1 release

This issue is used to track the progress of opendalfs 0.1 release. Welcome to join in the developmenet by leaving your comments here.

In 0.1 release, we might not cover all supported service. We will provide memory, fs, s3, azblob, gcs, oss at least.
In 0.1 release, we will only have blocking API first. Async API is on our plan.

Tasks

[x] Figure out all fsspec APIs that need to implement (maybe refer to s3fs and ossfs)
[ ] Implement OpendalFileSystem APIs

[ ] fsid
[ ] mkdir
[ ] mkdirs
[ ] rmdir
[ ] ls
[ ] info
[ ] rm_file
[ ] _open
[ ] created
[ ] modified

[ ] Implement OpendalBufferedFile APIs

[ ] _upload_chunk
[ ] _initiate_upload
[ ] _fetch_range

[x] Figure out how to perform releases

I expect to have a package for every different service.

[ ] Figure out how to do test on different service
[ ] Add docs for service.

cc @wey-gu and @BeautyyuYanli, are there any features you'd like included in our initial release?

I think no need to have a package for every different service, since the opendal has all in one package

Some methods have already been implemented in the abstract class. Others we can implement them by opendal-python or directly rust binding. Maybe the package will not depend on opendal-python, but becomes a new Python binding.

I think no need to have a package for every different service, since the opendal has all in one package

Hi, thanks for joining the discussion first.
Please allow me to provide some context before going deeper:

the opendal rust core have all services in a single crate (the package in Rust). Users can enable only the services they need, rather than importing unnecessary ones.
The python binding for OpenDAL has opted to include as many services as possible. However, this decision has not been well-received by the community because it results in a very large python package. Users are required to install the entire huge package even if they only need access to S3.

To further complicate matters, some services require additional dynamic libraries to function. For instance, sqlite requires libsqlite, while hdfs needs both libhdfs and libjvm. We must decide whether to discontinue support for these services or require all users to install the necessary libraries.

In opendalfs, I plan to separate various services into distinct packages, allowing users to selectively install the services they need, such as with pip install opendalfs[s3, azblob]. The implementation details are still being researched; however, I personally believe this is the better approach.

Maybe the package will not depend on opendal-python, but becomes a new Python binding.

I believe we can directly build from opendal rust to better align with fsspec's behavior without additional abstraction.

I have establish the project layout. Adding a service should be as easy as add a simple config: https://github.com/fsspec/opendalfs/pull/11

@BeautyyuYanli, I have updated the API that we need to implement and added place holders for them, welcome to take a look.

I would like to add to your list:

decide on async or blocking API (this might already be done)
pick a protocol string, and think about how users should express the inner protocol. For example, "opendal://gdrive/shared_folder/path/file" might be a reasonable way to refer to a path which is to be handled by DAL, but resides in gdrive (or s3, or ...). Or you could introduce separate protocols for each, like "dal_gdrive", or you might want to "register" your implementation to overwrite the known protocols in fsspec, such that "gdrive" refers to DAL's implementation for the rest of the session.

Hello! I would like to contribute to this project.
I have experience with Python and C++, but I am not yet familiar with Rust. I am very willing to learn it for this project.
I am still a beginner in open source. @Xuanwo Could you please assign me some simple and basic tasks to familiarize me with the whole process? I could get started and learn from them.
Thanks to @wey-gu for the guidance!

Hello! I would like to contribute to this project.
I have experience with Python and C++, but I am not yet familiar with Rust. I am very willing to learn it for this project.
I am still a beginner in open source. @Xuanwo Could you please assign me some simple and basic tasks to familiarize me with the whole process? I could get started and learn from them.
Thanks to @wey-gu for the guidance!

Hi, @dongshunyao, nice to meet you! I think we can start with implementing info or mkdir like we do for ls.

Hello! I would like to contribute to this project.
I have experience with Python and C++, but I am not yet familiar with Rust. I am very willing to learn it for this project.
I am still a beginner in open source. @Xuanwo Could you please assign me some simple and basic tasks to familiarize me with the whole process? I could get started and learn from them.
Thanks to @wey-gu for the guidance!

Hi, @dongshunyao, nice to meet you! I think we can start with implementing info or mkdir like we do for ls.

Thank you! I prefer to implement mkdir first. Should I write it in Rust like fs.rs#L18 and in Python like fs.py#L39, and complete the corresponding tests?

Thank you! I prefer to implement mkdir first. Should I write it in Rust like fs.rs#L18 and in Python like fs.py#L39, and complete the corresponding tests?

Exactly!

Thank you! I prefer to implement mkdir first. Should I write it in Rust like fs.rs#L18 and in Python like fs.py#L39, and complete the corresponding tests?

Exactly!

Hi! I am so sorry for the delay in this PR https://github.com/fsspec/opendalfs/pull/18, which was caused by my health reasons and some unexpected situations. I implemented the info because this PR https://github.com/fsspec/opendalfs/pull/17 implemented the mkdir. Please feel free to look it over and comment. Thank you!


Some OCP-4.3 test fails

/kind bug
What happened:
Running ocp-4.3 lane, 11 tests failed
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/2950/pull-kubevirt-e2e-ocp-4.3/1217032227049705472
What you expected to happen:
All test should pass
How to reproduce it (as minimally and precisely as possible):
Run /test pull-kubevirt-e2e-ocp-4.3 on empty PR (once #2950) is merged
Anything else we need to know?:
Use prow to run it or locally (#2950 must be included)
export KUBEVIRT_PROVIDER=ocp-4.3
make cluster-up && make cluster-sync && make functest

Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/cc @rmohr
fyi, thanks


consumerVersionSelectors errors are not propagating to the user

When: failIfNoPactsFound: false
Expected behaviour: no error
Actual result:
Failures:

1) Failed to load pact - No pacts found matching the given consumer version selectors in pact broker '

// {"name":"Error","message":"Verfication failed","stack":"Error: Verfication failed\n    at /....

When wrongly using consumerVersionSelectors together the error I see this.
By using branch & latest together with deployedOrReleased, the only way to see the error is from the Rust logs
const opts: VerifierOptions = {
        logLevel: "info",
        pactBrokerUrl: PACT_BROKER_BASE_URL,
        pactBrokerToken: PACT_BROKER_TOKEN,
        publishVerificationResult: isStageTest(STAGE),
        provider: pkg.config.pactParticipantName,
        providerVersion: pkg.version,
        providerBranch: BRANCH_NAME,
        consumerVersionSelectors: [
            {
                branch: "mainx",
                latest: true,
                deployedOrReleased: true,
            },
        ],
        failIfNoPactsFound: false,
        providerBaseUrl: apiUrl,
        changeOrigin: true,
        requestFilter,

2023-12-20T12:17:32.559427Z  INFO ThreadId(11) pact_verifier::pact_broker: error response for pacts for verification: failed validation - ["consumerVersionSelectors: cannot specify the fields branch/latest with the field deployedOrReleased (at index 0)"]
2023-12-20T12:17:32.561122Z ERROR ThreadId(11) pact_verifier: No pacts found matching the given consumer version selectors in pact broker 'https://skyai.pactflow.io/': failed validation - ["consumerVersionSelectors: cannot specify the fields branch/latest with the field deployedOrReleased (at index 0)"]
2023-12-20T12:17:32.562776Z ERROR ThreadId(11) pact_verifier: Failed to load pact - No pacts found matching the given consumer version selectors in pact broker '<REDACTED>'
2023-12-20T12:17:32.563719Z  WARN ThreadId(11) pact_matching::metrics:

By using branch together with deployedOrReleased,
2023-12-20T12:19:00.414088Z  INFO ThreadId(11) pact_verifier::pact_broker: error response for pacts for verification: failed validation - ["consumerVersionSelectors: cannot specify the field branch with the field deployedOrReleased (at index 0)"]
2023-12-20T12:19:00.414601Z ERROR ThreadId(11) pact_verifier: No pacts found matching the given consumer version selectors in pact broker '<REDACTED>': failed validation - ["consumerVersionSelectors: cannot specify the field branch with the field deployedOrReleased (at index 0)"]

Thanks for posting this, much appreciated.


add: fenced code block formatting for svelte

closes #58

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @basaran! This is in 0.11.2 (just publishing on CI now).