Add code snippets or file sharing tools

What's the Problem?
Sometimes we need to share some brief code snippets or transfer files with others, it will be very useful if there's a transfer tools.
Solution/Idea
I used to use a website to transfer files, but i have no idear how to embed it to DevToys.
Alternatives
I have no idear.
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

DevToys Version
No response
Comments
No response

This feature would require the internet capability for the app, and is therefore probably out of scope for DevToys features.


Implement Individually Muteable Drum Stems and "Mute/Unmute All" Buttons

To allow for ease of use since we now have a lot of different stems.

Pulled and cleaned up individually into the following commits
16fc82c40e8a4e4a10db1f9f6d4647dc84168f77
42b06132cd975467e570fd0337fe652210cbc7b4


Fix: add necessary annotation to example

Description of your changes

Fixes the droplet example.
Beforehand the example failed with the following error
"creation of Droplet resource has failed: POST https://api.digitalocean.com/v2/droplets: 422 Droplet must have a name"
I have:

[x] Read and followed Crossplane's [contribution process].
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

No codechanges.
[contribution process]: https://git.io/fj2m9

Thank you for the PR, @tillepille!


Duplicate objects since chapter 3.14

Hello,
I have seen since chapter 3.14 to at least the chapter 4.3 that all objects and monsters are duplicated upon spawn.
Trying to narrow down the problem, i found it coming from the function "apply_previous_iteration" in "src\map_builders\prefab_builder\mod.rs" : the part if filter(x, y, e) {   build_data.spawn_list.push(    (idx, e.1.to_string())   ) } totally duplicate the spawn list.
When using !filter, it seems back to normal, exept if there is a sectionnal fort where items are in two copies, but i don't have a good enough grasp on the filter function to know what to do or if what i have done is the right solution.

Whoops! Thanks for reporting that. I haven't seen it on my local build, but so I probably fixed it by mistake somewhere further down the line. I'll take a look.


refactor(dexes): use the dexes API for the tracker page

(ꐦ°᷄д°᷅)
this is the same commit from #199, but merging to master instead of the feature branch, except it's also passing dex when saving/deleting captures. as i was testing #203, i created a shiny dex for /u/hiami which was the third dex for that account but every time i marked a pokemon as captured, it didnt actually mark it as captured in the db. this is cause the endpoint just picks a random dexs to create the captures for lol. but for the api to use a dex id thats being passed in, this needs to be in master.
you should just make sure that everything still works as expected (particularly users with only one dex)!

yup! its only supposed to work for single dexes for now. once this gets deployed, i can modify the api to work with multiple dexes


Add WithVolume helper in client.

Volumes in image spec is not defined very clearly, but I think the expected behavior will be similar with Docker image volume.
Docker image volume copy content from container rootfs into the host volume, and mount it back to the rootfs.
I could send a PR for this, but I'm not sure whether we want to Mount and Unmount rootfs again for this, since we've already been doing that in WithUsername and WithUserID.

What if there was a helper to export data from some given path?
Using WithVolume in this way seems a bit opinionated.

/cc @crosbymichael @stevvooe Any thoughts on this?
This is blocking @ijc 's demo I think. :)

I wonder if we can use the context that all the Opts take to only mount the rootfs once?

I think lack of volumes support is the final thing stopping the sock-shop demo from working for me (although there might be further unknown unknowns ;-)).
I'd been thinking of introducing a helper to do the full snapshotter dance (which is a bit fiddly so we may as well get it right once) to mount a given image so that the caller can amortise the mounts over multiple volumes, but leaving most of the smarts of allocating the volumes and doing the copy up in the client.
@crosbymichael hiding in the ctx is an interesting idea, although how would we know when it was safe/useful to umount?

I somehow missed @Random-Liu's note that we already do the mount umount dance for the userid stuff. Will have a look at that and a think, etc.

I'm not sure how we do it with context, was the first thing I thought of though.
We can do remounts for not and optimize later when we find a way to handle holding the mount until the end.

I suppose all the layer unpacking just happens once anyway (depending on the snapshotter?) and it's just the actual stack of mounts, which is expensive but not super bad?

BTW https://github.com/containerd/containerd/pull/1425/files#r137853982 might be relevant to any reuse/refactoring of the WithUserID code.

Shouldn't a volume just be a mount in the runc spec? What does this have to do with the snapshotter? Do these mounts need to be performed in the shim?

@stevvooe they are talking about the magic that docker does today and copies the image contents into the volume

yeah,  I think the proposed WithVolume would populate some backing storage somewhere from the image and then add the result to spec.Mounts. I'm hacking together a prototype to see how it looks.

@crosbymichael We've added helper in cri-containerd ourselves. Feel free to close this one if we don't need this in containerd. :0

We could move it into contrib/volumes if Docker and CRI need to share the same code.  Does not matter to me, we can always add it later if its general useful for people.

So, this volume behavior is kind of an OCI thing, as well, so I see no reason this shouldn't be in containerd. https://github.com/kubernetes-incubator/cri-containerd/pull/247 could totally be apart of containerd. However, that toolkit may grow, so having it elsewhere might be useful (containerd/volumes).

I'd be happy to make a PR to simply take the WithVolume from https://github.com/kubernetes-incubator/cri-containerd/pull/247 and move it here but I think we would also want to have https://github.com/kubernetes-incubator/cri-containerd/pull/261 which then implies being happy with the additional vendorings that brings in which is the transitive set required by github.com/docker/docker/pkg/chrootarchive.NewArchiver which looks to be:
github.com/docker/docker/pkg/archive
github.com/docker/docker/pkg/chrootarchive
github.com/docker/docker/pkg/fileutils
github.com/docker/docker/pkg/idtools
github.com/docker/docker/pkg/pools
github.com/docker/docker/pkg/promise
github.com/docker/docker/pkg/reexec

If all the needs rewriting/reimplementing or otherwise porting across then its a much bigger task.

@ijc We really don't want to pull in the docker dependencies for either project (don't get me started on the promise package -- submitting a PR shortly to can it). If we need the chroot behavior, it would be best to bring those over carefully. I understand that is a much bigger task, but we need to do this to hit our quality goals.
Ideally, rather than a chroot, we should be doing this in a container. We might want to see if we can make a simple client API to setup a container for running a command safely.

Wait why is promise in there... omg...

@cpuguy83 Killing it...

@cpuguy83 @ijc moby/moby#34929

I think (but I'm not certain) that the chroot is only because the same code is also used in Docker to  handle untrusted tar streams. In this case are handling a tar stream which we are creating locally, which I think rules out the attacks which the use of chroot is trying to combat (symlinks to ../../../ outside the root, maybe certain classes of hardlink attack etc). I think (but again am not certain) that this is true even though the input filesystem which we are tarring up is not itself necessarily trusted.
Might this sort of functionality fit into continuity?

Correct this is for handling untrusted tar streams, mainly when exploding a tar from an image.
However, I think it's wise to not trust even already existing images/container FS.
Providing a helper to do this in a container would be great, however this seems like it might be a bit hairy to do.

Might this sort of functionality fit into continuity?

This is where we want this functionality to land.
The symlink attacks seem to be the main vector. With containerd, this all runs client-side, so dropping using an untrusted user would mitigate some of the risk but I am not sure how realistic that is for CRI and docker.
Besides chroot, is there something missing in the containerd helpers that prevents you from using those packages over the docker ones?

dropping using an untrusted user would mitigate some of the risk but I am not sure how realistic that is for CRI and docker

Would that prevent it from doing any chown or chmod it might need to do (e.g. since the files need to end up being root owned)?

Besides chroot, is there something missing in the containerd helpers that prevents you from using those packages over the docker ones?

I thought containerd was entirely lacking functionality to copy one arbitrary subtree to somewhere else, have I missed something?

Besides chroot, is there something missing in the containerd helpers that prevents you from using those packages over the docker ones?

I thought containerd was entirely lacking functionality to copy one arbitrary subtree to somewhere else, have I missed something?

The goal here is to bring containerd to feature parity. If there is something that is missing, let's work to add it.

Sorry, I thought you were saying there was some (non-chroot based) file tree copying functionality somewhere in containerd which I had missed. That tree copy helper is the functionality which is required but not (AFAIK) already present. With that we can can use the existing functionality to mount a ro snapshot and copy the path underlying the volume to the backing store on the client side.
The copier would need to preserve xattrs and perms and all that sort of stuff but doesn't particularly need to be chroot (or containerd) based if it is carefully written IMHO, which basically means it should never try to dereference a symlink under any circumstance and should be happy to copy apparently dangling symlinks as is.

@ijc Ok, that seems reasonable. Let's add that to containerd and avoid the moby dependencies before we get too far along.

@stevvooe I was looking at continuity for this and was wondering what you think about adding a Copyable interface containing a Copy(srcroot, dstroot string) error type method (or just add such a method to Resource). The idea would be that each Resource can then implement the correct logic for duplicating that type of object (perhaps with a common helper for ownership/perms/xattrs).
With that a caller can then iterate over the result of BuildManifest(ctx) (sorted using ByPath) and duplicate each resource in turn. Maybe we would want to add a Manifest.Copy(ctx, dst) style helper to save users the effort.
WDYT? (maybe we should take this to an issue on continuity or at least to a non-closed issue on this repo?)

@ijc Throw together a small proposal issue with the interface changes and we can work from there. On first pass, it looks reasonable.

@stevvooe: https://github.com/containerd/continuity/issues/95


Colorpicker Positioning

Is there a way to position the color-picker pop-up?
It worked fine previously when in 2.0 when my .input-group-addon is placed before my .form-control input element, not after like in your examples.
What I see now: https://jsfiddle.net/DTcHh/8258/ (2.1 the pop-up is outside the form)
What it was before: https://jsfiddle.net/DTcHh/8259/ (2.0 the pop-up is inside the form. Preferred solution)

It looks like there's an option provided to adjust the alignment of the color picker :)
Try adjusting your fiddle to the following:
 $(function () {
     $('.cp').colorpicker({align:'left'});
 });

@ASeeto, great, thanks


Batch decoding with vLLM

https://vllm.readthedocs.io/en/latest/

Hey, this issue seems interesting! How can i get started with it?

Hi. Can I work on this?

How do I go about getting assigned, starting, working and finishing an issue so that I may get credit for it?
Thank you

Hi! Can I also please work on this issues? Thank you!

Hi, just have one question, when doing parallel sampling, should we combine the test_llm_vm.py with the parallel sampling for more efficiency? Thank you!


update ICU version handling

Summary of changes
This pull request includes following updates:
o update autotools to make ICU version test selectable (>= v60)
o change preprocessor lable (ICU6x)
o select correct ICU unorm functions based on given preprocessor flag
Description
Since AX_COMPARE_VERSION macro isn't available on all plattforms, i have choosen to use a simple bash string comparison. Not as flexible, but does the trick.

It looks good to  me.


Update cats-effect to 3.1.0

Updates org.typelevel:cats-effect from 2.5.0 to 3.1.0.
GitHub Release Notes - Version Diff
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!

Applied Migrations

github:typelevel/cats-effect/v3_0_0?sha=series/3.x

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-major, scalafix-migrations

Nope. Built into CE3.


Error: There was no response from the game server

"Help i get the error 'Error: There was no response from the game server' eventhough i am running 'YgoMasterClient.exe' from the correct location (usually: Steam\steamapps\common\Yu-Gi-Oh!  Master Duel\YgoMaster\YgoMasterClient.exe) "

Can confirm this was my issue as well. For those who may not know how to set this up.
In the host machine (machine which you will be running the server from):
In Windows, search for the program "Windows Defender Firewall". Click on "Advanced Settings" in the left-hand panel. This opens up a window called "Windows Defender Firewall with Advanced Security". From here, click on "Inbound Rules" on the left-hand panel. And click on "New Rule..." in "Actions" panel (right-hand side).
Go through the "New Inbound Rule Wizard". I used the "Port" option with TCP. The port, by default, is 4989. Restart the ygomaster server. After this I was able to connect to the server via LAN from another machine.


[formMixin] It is not possible to load a referenceList without having a load action.

In our case we need to load a referenceList from the server for our criteria and we don't have data to load.
In result we have to implement a empty loadAction:
function load() {
    return new Promise(function(resolve) {
        resolve();
    });
}

@durandx you can use Promise.resolve(yourData)

@durandx
I think you can use the props hasLoad on the form in order to disable load
https://github.com/KleeGroup/focus-components/blob/develop/src/common/form/index.js#L69
If this does not solve the issue, please reopen it.


Compile error while trying to install Material UI

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
After installation of Material-ui - on April 23rd, using the available file on site, I'm can't run my application. I'm using React 18.0.
I've already asked a question on Stackoverflow:
https://stackoverflow.com/questions/71975875/react-dependency-conflict-version-18-0-with-material-ui?noredirect=1#comment127183243_71975875
Compiled Errors:
Compiled with problems:
ERROR in ./src/components/NavBar.js 6:0-48
Module not found: Error: Can't resolve '@material-ui/core/ToolBar' in '/home/flavio/CashFlowBr/cashflowbr/src/components'
ERROR in ./src/components/NavBar.js 12:35-41
export 'AppBar' (imported as 'AppBar') was not found in '@material-ui/core/AppBar' (possible exports: appBarClasses, default, getAppBarUtilityClass)
`import React from 'react';
import {AppBar} from '@material-ui/core/AppBar';
import ToolBar from '@material-ui/core/ToolBar';
import Typografy from '@material-ui/core/Typography';
const NavBar = () => {
return(

CashFlowBR - Sistema de Gerenciamento Financeiro

)
}
export default NavBar;`
Expected behavior 🤔
I Should have a NavBar at the top of my application.
Steps to reproduce 🕹
Steps:

Context 🔦
No response
Your environment 🌎
flavio@flavio-X555LF:~/CashFlowBr/cashflowbr$ npm install @mui/material @emotion/react @emotion/styled
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@emotion/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@material-ui/core
npm ERR!       @material-ui/core@"next" from the root project
npm ERR!     1 more (@emotion/styled)
npm ERR!   1 more (@emotion/styled)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"next" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/flavio/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/flavio/.npm/_logs/2022-04-23T20_54_38_425Z-debug-0.log
flavio@flavio-X555LF:~/CashFlowBr/cashflowbr$
Order ID 💳 (optional)
No response

What version of Material UI did you use?
@material-ui/core is v4 which does not work with React 18.

@material-ui/core  is v4 so it is not working in react 18
to use @material-ui/core shift to lesser versions of react


Fix that SA1625 ignores empty xml elements

Fixes #1876.

Current coverage is 79.40%

Merging #1890 into stabilization will not affect coverage as of 612a764

@@            stabilization   #1890   diff @@
=============================================
  Files                 558     558
  Stmts               34824   34837    +13
  Branches             9645    9650     +5
  Methods                 0
=============================================
+ Hit                 27653   27662     +9
- Partial              5630    5633     +3
- Missed               1541    1542     +1

Review entire Coverage Diff as of 612a764

Powered by Codecov. Updated on successful CI builds.

:+1:

:+1:


Warning when building a package using the plugin with Swift 5.9.

In adding Swift 5.9 to the CI for swift-protobuf, we noticed some warning coming from the plugin compile:
https://github.com/apple/swift-protobuf/actions/runs/6249612455/job/16966661520?pr=1459
/__w/swift-protobuf/swift-protobuf/main/.build/checkouts/swift-docc-plugin/Plugins/Swift-DocC Convert/Symbolic Links/SharedPackagePluginExtensions/PackageExtensions.swift:31:17: warning: switch covers known cases, but 'TargetDependency' may have additional unknown values
                switch dependency {
                ^
/__w/swift-protobuf/swift-protobuf/main/.build/checkouts/swift-docc-plugin/Plugins/Swift-DocC Convert/Symbolic Links/SharedPackagePluginExtensions/PackageExtensions.swift:31:17: note: handle unknown values using "@unknown default"
                switch dependency {
                ^
[1/1] Compiling plugin Swift-DocC
/__w/swift-protobuf/swift-protobuf/main/.build/checkouts/swift-docc-plugin/Plugins/Swift-DocC Preview/Symbolic Links/SharedPackagePluginExtensions/PackageExtensions.swift:31:17: warning: switch covers known cases, but 'TargetDependency' may have additional unknown values
                switch dependency {
                ^
/__w/swift-protobuf/swift-protobuf/main/.build/checkouts/swift-docc-plugin/Plugins/Swift-DocC Preview/Symbolic Links/SharedPackagePluginExtensions/PackageExtensions.swift:31:17: note: handle unknown values using "@unknown default"
                switch dependency {
                ^

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[x] This issue hasn't been addressed in an existing GitHub issue.

Expected behavior
Clean compile.
Actual behavior
Warning generated.
Steps to Reproduce
Simply doing a build should produce the warnings.
Swift-DocC Plugin Version Information
Swift-DocC plugin version: 1.3.0
Swift Compiler version: 5.9

This looks like it was already fixed by adding @unknown default here.


Adding Media Services Event Grid schema

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-libraries-for-java

Automation for azure-sdk-for-node

@jonpayne from the description what I understand is - this model represents the schema of event that media-services internally send to event grid when it is enabled. From customers point of view, the way they use is, they use event grid data plane to retrieve the event in string/json format and then uses this model to deserialize the string to POJO. is my understanding correct?

@anuchandy This is the schema for the events Media Services will send to customers, via Azure Event Grid. The documentation for these events is here:
https://docs.microsoft.com/en-us/azure/media-services/latest/media-services-event-schemas?toc=%2Fazure%2Fevent-grid%2Ftoc.json
@kalyanaj can provide more details.

@anuchandy , to answer your previous question:  Yes, customers can create an event subscription in EventGrid to subscribe to these events (e.g. an Azure Function can be the destination of this event subscription). Once the event JSON is received there, it can be deserialized into an "EventGridEvent", and the Data portion of the EventGridEvent can be deserialized using the new model that @jonpayne has added in this PR.


Stickers!

Look into what it would take to get stickers, or small business card size things printed with some basic info to hand out.

Sticker and business card design is done, and the order for printing them is ready for pick up.

PDFs of designs sent for printing:
sticker
"business" card


Api dosent work.

The API endpoints no longer respond.
i checked thepiratebay.org and it still works.
maybe need to change base url?

Could you explain a bit more?


Make pagination sections configurable

As mentioned in the where docs from hugo with regards to mainSections comparing against .Site.Params.mainSections allows the users to configure it on the config.toml like so:
[params]
  mainSections = ["blog", "docs"]

Nicely spotted. :)  I totally agree that we should change this, in order to make the theme more flexible and better follow the Hugo guidelines. Before merging this request, we should also update the exampleSite toml and the ReadMe.

Nice @lxndrblz !
thanks for amending the work and merging so fast! <3


Deduplication causes a lot of Full GCs

Describe the bug
2019/02/14 Added
In our experiments, we found that enabling deduplication causes a lot of Full GCs in Brokers, which
seems to cause session expiration from ZooKeepers and finally shutdown.
2019/02/07 Original report of unexpected Broker shutdown
We have seen unexpected Broker shutdown.

There were LedgerFencedExceptions for a lot of ledgers:

01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] WARN  o.a.bookkeeper.client.PendingAddOp   - Fencing exception on write: L9104171 E28233 on xxx.xx.xx.xx:3181
01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] ERROR o.a.bookkeeper.client.LedgerHandle   - Closing ledger 9104171 due to LedgerFencedException: Ledger has been fenced off. Some other client must have opened it to read
01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] WARN  o.a.bookkeeper.client.PendingAddOp   - Fencing exception on write: L9104171 E28234 on xxx.xx.xx.xx:3181
01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] ERROR o.a.bookkeeper.client.LedgerHandle   - Closing ledger 9104171 due to LedgerFencedException: Ledger has been fenced off. Some other client must have opened it to read
01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] WARN  o.a.bookkeeper.client.PendingAddOp   - Fencing exception on write: L9104171 E28235 on xxx.xx.xx.xx:3181
01:47:09.430 [BookKeeperClientWorker-OrderedExecutor-43-0] ERROR o.a.bookkeeper.client.LedgerHandle   - Closing ledger 9104171 due to LedgerFencedException: Ledger has been fenced off. Some other client must have opened it to read
...

There were a lot of "Failed to create producer: Producer with name geo-replicator".

01:47:09.907 [pulsar-io-21-31] ERROR o.a.pulsar.client.impl.ProducerImpl  - [persistent://<topicname>] [pulsar.repl.<localcluster>] Failed to create producer: Producer with name 'pulsar.repl.<localcluster>' is already connected to topic

Finally, Broker suddenly stopped with

01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] ERROR o.a.p.z.ZooKeeperSessionWatcher      - ZooKeeper session already expired, invoking shutdown

Additional context
Broker OS: CentOS Linux release 7.6.1810
Broker version: 2.1.1

@nkurihar fencing means there are other brokers taking over the ownership of topics. those brokers which took over the ownership has opened the topics and fenced the old ledgers.
by looking into the description here, it seems to be reasonable to me. I think it is somehow related to zookeeper session expired. when zookeeper session expired happened, the load manager has discovered the broker disappeared from zookeeper and topic bundles are re-assigned to other brokers, those brokers fenced the topics, hence the original broker will see LedgerFencedException and Producer will fail to create.
I think the exception should be self-recovered. did it self-recover? @nkurihar

@sijie Thanks for your help!

I think the exception should be self-recovered. did it self-recover?

No.
After ZK session expired, Broker becoame down.
01:47:09.961 [pulsar-ordered-OrderedExecutor-4-0-SendThread(zk101.pulsar.xxx.xx:2181)] WARN  org.apache.zookeeper.ClientCnxn      - Unable to reconnect to ZooKeeper service, session 0x3048c994034e22a has expired
01:47:09.961 [pulsar-ordered-OrderedExecutor-4-0-SendThread(zk101.pulsar.xxx.xx:2181)] INFO  org.apache.zookeeper.ClientCnxn      - Unable to reconnect to ZooKeeper service, session 0x3048c994034e22a has expired, closing socket connection
01:47:09.961 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.zookeeper.ZooKeeperDataCache   - [State:CLOSED sessionid:0x3048c994034e22a local:/xx.xx.xx.xx:37204 remoteserver:zk101.pulsar.xxx.xx/xx.xx.xx.xx:2181 lastZxid:171918958881 xid:7602221 sent:7602223 recv:8325363 queuedpkts:73 pendingresp:0 queuedevents:1] Received ZooKeeper watch event: WatchedEvent state:Expired type:None path:null
01:47:09.961 [pulsar-ordered-OrderedExecutor-4-0-EventThread] WARN  o.a.p.zookeeper.LocalZooKeeperCache  - Lost connection from local ZK. Invalidating the whole cache.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.z.ZooKeeperChildrenCache       - [State:CLOSED sessionid:0x3048c994034e22a local:xx.xx.xx.xx/xx.xx.xx.xx:37204 remoteserver:zk101.pulsar.xxx.xx/xx.xx.xx.xx:2181 lastZxid:171918958881 xid:7602221 sent:7602223 recv:8325363 queuedpkts:73 pendingresp:0 queuedevents:1] Received ZooKeeper watch event: WatchedEvent state:Expired type:None path:null
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] WARN  o.a.p.zookeeper.LocalZooKeeperCache  - Lost connection from local ZK. Invalidating the whole cache.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.z.ZooKeeperChildrenCache       - [State:CLOSED sessionid:0x3048c994034e22a local:xx.xx.xx.xx/xx.xx.xx.xx:37204 remoteserver:zk101.pulsar.xxx.xx/xx.xx.xx.xx:2181 lastZxid:171918958881 xid:7602221 sent:7602223 recv:8325363 queuedpkts:73 pendingresp:0 queuedevents:1] Received ZooKeeper watch event: WatchedEvent state:Expired type:None path:null
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] WARN  o.a.p.zookeeper.LocalZooKeeperCache  - Lost connection from local ZK. Invalidating the whole cache.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.zookeeper.ZooKeeperDataCache   - [State:CLOSED sessionid:0x3048c994034e22a local:xx.xx.xx.xx/xx.xx.xx.xx:37204 remoteserver:zk101.pulsar.xxx.xx/xx.xx.xx.xx:2181 lastZxid:171918958881 xid:7602221 sent:7602223 recv:8325363 queuedpkts:73 pendingresp:0 queuedevents:1] Received ZooKeeper watch event: WatchedEvent state:Expired type:None path:null
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] WARN  o.a.p.zookeeper.LocalZooKeeperCache  - Lost connection from local ZK. Invalidating the whole cache.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.zookeeper.ZooKeeperDataCache   - [State:CLOSED sessionid:0x3048c994034e22a local:xx.xx.xx.xx/xx.xx.xx.xx:37204 remoteserver:zk101.pulsar.xxx.xx/xx.xx.xx.xx:2181 lastZxid:171918958881 xid:7602221 sent:7602223 recv:8325363 queuedpkts:73 pendingresp:0 queuedevents:1] Received ZooKeeper watch event: WatchedEvent state:Expired type:None path:null
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] WARN  o.a.p.zookeeper.LocalZooKeeperCache  - Lost connection from local ZK. Invalidating the whole cache.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] ERROR o.a.b.zookeeper.ZooKeeperWatcherBase - ZooKeeper client connection to the ZooKeeper server has expired!
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.b.zookeeper.ZooKeeperClient      - ZooKeeper session 3048c994034e22a is expired from zk100.pulsar.xxx.xx,zk101.pulsar.xxx.xx,zk102.pulsar.xxx.xx,zk103.pulsar.xxx.xx,zk104.pulsar.xxx.xx.
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.z.ZooKeeperSessionWatcher      - Received zookeeper notification, eventType=None, eventState=Expired
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] ERROR o.a.p.z.ZooKeeperSessionWatcher      - ZooKeeper session already expired, invoking shutdown
01:47:09.963 [pulsar-zk-session-watcher-5-1] INFO  o.a.p.z.ZooKeeperSessionWatcher      - ZooKeeperSessionWatcher interrupted
01:47:09.963 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO  o.a.p.b.MessagingServiceShutdownHook - Invoking Runtime.halt(-1)
01:47:09.964 [ZKC-connect-executor-0] INFO  o.a.b.zookeeper.ZooKeeperClient      - Reconnecting zookeeper zk100.pulsar.xxx.xx,zk101.pulsar.xxx.xx,zk102.pulsar.xxx.xx,zk103.pulsar.xxx.xx,zk104.pulsar.xxx.xx.
01:47:09.966 [ZKC-connect-executor-0] INFO  org.apache.zookeeper.ZooKeeper       - Initiating client connection, connectString=zk100.pulsar.xxx.xx,zk101.pulsar.xxx.xx,zk102.pulsar.xxx.xx,zk103.pulsar.xxx.xx,zk104.pulsar.xxx.xx sessionTimeout=30000 watcher=org.apache.bookkeeper.zookeeper.ZooKeeperWatcherBase@1c7f3bee

(Broker became down and not self-recovered)

@nkurihar :

After ZK session expired, Broker become down.

this is current behavior. broker shutdown itself when the zookeeper session is expired. my question was "does the broker became down affect the clients?".
there is a plan on improve the logic on handling zookeeper session expires. /cc @merlimat @ivankelly

@sijie

"does the broker became down affect the clients?".

No.
Clients successfully reconnected to another Brokers.
We are now investigating ZK logs and found a lot of ZK session expiration.
(if we find more details, we will add)

there is a plan on improve the logic on handling zookeeper session expires.

Sounds great!

We found that producing from a particular topic causes Broker's frequent GCs, and finally ZK session will be disconnected.
 Thus the backlog is always full and messages are discarded
every time by the policy: "consumer_backlog_eviction"

Disabling deduplication seems to suppress GCs.
We will investigate more detail.

We kept producing messages for 4 hours and memory usage of broker became as follow:
Deduplication disabled : 50G
Deduplication enabled: 99G(Reached 99G and full GC occured)

If deduplication is disabled, memory usage remained at 50G all the time. On the other hand, if deduplication is enabled, memory usage gradually increased from 50G to 99G.
■memory settings
-Xms96g -Xmx96g -XX:MaxDirectMemorySize=96g
■deduplication settings
brokerDeduplicationMaxNumberOfProducers=10000
brokerDeduplicationEntriesInterval=1000
brokerDeduplicationProducerInactivityTimeoutMinutes=360
■the number of partition
8
(We used a partitioned topic for test)
■Rate
20,000msg/s(2,500msg/s per internal topic)
■Message size
200byte
■Execution time
4hours

@hrsakai can you share a jmap histo:live of the process with dedup turned on?

@merlimat
Here are outouts of jmap -histo.
jmap-histo.txt
jmap-histo-live.txt
Specs of this broker is different from those of a broker in the above test.
So, memory settings of this broker is different:
-Xms3g -Xmx3g

Full GC log (caused by jmap histo:live)
2019-02-14T21:02:53.684+0900: 38477.063: [Full GC (Heap Inspection Initiated GC)  1222M->125M(3072M), 2.4529610 secs]
   [Eden: 61.0M(1416.0M)->0.0B(1536.0M) Survivors: 120.0M->0.0B Heap: 1222.8M(3072.0M)->125.7M(3072.0M)], [Metaspace: 74890K->74877K(1118208K)]
 [Times: user=1.41 sys=0.00, real=2.45 secs]

@hrsakai is this on a single topic? The histogram points to there being a lot of entries in the ManagedCursorContainer. There should only be one managed cursor for deduplication for each topic. So either something is triggering the creation and destruction of the dedupe cursors in a loop, or something about having any dedupe cursor at all is causing bad behaviour from the other cursors.
Can you try enabling debug logging for org.apache.pulsar.broker.service.persistent.MessageDeduplication?
If that doesn't yield info, then we'll have to do a heap dump.

@ivankelly
At this time, I produced messages to a partitioned topic (16 partitions).
And There are 4 producers, 0 consumer and 1 subscription.

Can you try enabling debug logging for org.apache.pulsar.broker.service.persistent.MessageDeduplication?

The broker outputed a lot of logs as follow:
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Taking snapshot of sequence ids map
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Stored new deduplication snapshot at 790835:45361
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Taking snapshot of sequence ids map
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Stored new deduplication snapshot at 790835:45362
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Taking snapshot of sequence ids map
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-3-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-3] Stored new deduplication snapshot at 790835:45363
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-1-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-5] Taking snapshot of sequence ids map
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-1-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-5] Stored new deduplication snapshot at 790833:57439
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-1-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-9] Taking snapshot of sequence ids map
08:33:16.719 [bookkeeper-ml-workers-OrderedExecutor-1-0] DEBUG o.a.p.b.s.p.MessageDeduplication     - [persistent://XXXXX/global/deduplication/p-topic2-partition-9] Stored new deduplication snapshot at 790831:57486
.
.

brokerDeduplicationEntriesInterval is 1 on this broker. This may be affecting.
However,  this issue occurs even if brokerDeduplicationEntriesInterval is default value(1000).

what is the publication rate to this topic?

@ivankelly
It is about 20000〜40000msg/s.
(5000〜10000msg/producer)

The histograms you sent only show 2.4GB and 131MB of objects respectively. Did you take them when the bad behaviour was happening?
How long does it take to grow from 50G to 99G.

@ivankelly
The broker I took histograms is different from the broker grow from 50G to 99G.
heap size of the broker I took histograms is only 3G.
But, it seems that same problem is happening.

How long does it take to grow from 50G to 99G.

it take about 4hours.

@hrsakai I think #3612 should be fixing this. I was able to reproduce the behavior locally (with a smaller heap).

@merlimat
Thanks for fix. I will try to test again with that code.

As @hrsakai pointed out, the fix was ineffective because applied on a code path that's not being used.
The problem is that that while the cursor is set as "inactive" in the beginning, a periodic check is flipping back the state to "active":
https://github.com/apache/pulsar/blob/43380523c5269c152f61b2aa8f7b70281c770d1d/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedLedgerImpl.java#L878-L885
Working on a fix.

Updated #3612 with correct fix


Fixed #8065 -- Allowed QuerySet.in_bulk() to accept no arguments.

Modified in_bulk() to return all objects in the queryset when called
with no arguments.

buildbot, add to whitelist.

Please squash commits and uncheck "Patch needs improvement" on the ticket when you update the pull request, thanks!

Thanks for the feedback! I will get to it later this week

Hi Bryan, any plan to return to this soon or should we close it for now?

Hi,  sorry about the delay. I'll finish it this weekend.
On Dec 24, 2015 4:54 PM, "Tim Graham"<EMAIL_ADDRESS>wrote:

Hi Bryan, any plan to return to this soon or should we close it for now?
—
Reply to this email directly or view it on GitHub
https://github.com/django/django/pull/5514#issuecomment-167162124.

merged in 62ca2dea04489bdb23df1c7815439287c6d44630, thanks!


Feature/refatory api

refatoring api calls and export models from a single file to simplife some code

i mada changes to keep search lyrics static

Thank you for the PR 😀


ISR does not seem to work

Brief Description of the Bug
When using the App directory, calling revalidateTag will delete all entries with the specified tag. When the user browses a page that was tagged with the tag, the page is rebuilt during the request, causing a delay for the user. I would have expected the page to be rebuilt in the background after the request has been served, as happens when using the built-in CacheHandler.
Severity
Major
Frequency of Occurrence
Always
Steps to Reproduce

Navigate to a page '/test' with tag 'xyz'
call revalidateTag('xyz') in an api endpoint - this deletes the cache entries for the tag
Browse to '/test' - the page is rebuilt inline rather than in the background

Expected vs. Actual Behavior
I would expect the page to be rebuilt in the background and the user who initiated the request to be served the stale content.
Environment:

OS: MacOS
Node.js version: v20.10.0
@neshca/cache-handler version: 1.0.5
next version: 14.1.0

Attempted Solutions or Workarounds

Looked into how the stock CacheHandler works - it seems that we would need to replicate the behaviour in FetchCache and FileSystemCache?
Referenced https://github.com/sst/open-next/blob/ff37de235e653e3aecdbb31168ab411add2d0330/packages/open-next/src/adapters/cache.ts#L81 - but it's unclear whether the approach used there would improve the situation - as they appear to use a custom revalidation system.

Impact of the Bug
We would like to containerize our app, building on a remote CI environment using a shared cache, and have ready-to-run testable Containers as built output - and this is a blocker for us

@joshudev hello!

When the user browses a page that was tagged with the tag, the page is rebuilt during the request, causing a delay for the user.

This behavior is not a bug. Native Next.js cache works the same. It makes sense to me because on-demand revalidation is a manual process.
It is also worth mentioning that pages from the Pages Router are updated synchronously on res.revalidate(pathname), and CacheHandler can not alter this. As a result, such pages are always fresh after revalidation. I think that the App Router pages inherit this aspect of on-demand revalidation.
I'm converting this issue to discussion.


OBSDATA-5211 At Brokers emit a single metric that tells total CPU consumed by all components include Brokers/Indexers/Historicals

OBSDATA-5211 At Brokers emit a single metric that tells total CPU consumed by all components include Brokers/Indexers/Historicals
Description
OBSDATA-5211 At Brokers emit a single metric that tells total CPU consumed by all components include Brokers/Indexers/Historicals
This PR has:

[x ] been self-reviewed.
[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x ] been tested in a test Druid cluster.

closing

reopen


[ISSUE #378] downstream broadcast msg asynchronously

[ISSUE #378]  In eventmesh-runtime, add a threadpool , make the downstreaming of broadcast msg asynchronously.

Codecov Report

Merging #379 (4218b4f) into develop (60b9b33) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             develop    #379   +/-   ##
=========================================
  Coverage       5.57%   5.57%
  Complexity        85      85
=========================================
  Files            118     118
  Lines           5292    5292
  Branches         357     357
=========================================
  Hits             295     295
  Misses          4955    4955
  Partials          42      42

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 60b9b33...4218b4f. Read the comment docs.


Broken URLs

Hey guys,
I've read a lot of documentation on both WP and Roots but can't get my head around this. The URLs to linked files are not correct. n.b. a clean install of wp and roots, running on wamp ( htaccess is okay and rewrites working).
Example, the url is:
/ema_wp/js/libs/modernizr-2.0.6.min.js
When it should be
/ema_wp/WP-CONTENT/THEMES/ROOTS/js/libs/modernizr-2.0.6.min.js
Why is this happening?
Thanks,
Lehel

I found out the problem. mod_rewrite was disabled in apache. Wamp default is disabled.
"Users of XAMPP (Windows): Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line)."
from: http://codex.wordpress.org/Using_Permalinks
Hope somebody else finds this helpfull.
Best regards and happy coding,
Lehel


[WIP] Write a Deepspeed Distributed Learning Class DeepspeedTorchDistributor

What changes were proposed in this pull request?
Implemented a distributed learning class meant for deepspeed workloads using the torch.distributed.run command. Also made some tests for some of the functions. Need to add tests for the distributed workloads in the create_torchrun_command.
Why are the changes needed?
Special commands are needed for deepspeed workloads. This class makes it easier to run the deepspeed applications without ever needing to touch the terminal. If a user needs to use the torch.distributed.run launcher, this class will let them do that. This class also has a very similar API and workflow to the TorchDistributor class, where you simply create an instance and then invoke distributor.run(...).
Checklist

[x] creates deepspeed command
[x] can support running a python file in a distributed fashion
[ ] supports distributed training with a function
[ ] cleans up any temporary files it made
[ ] unit tests

@HyukjinKwon if you could take a pass of this PR, that would be awesome!

Merged to master.
Please create a followup to address my last round review comments - that contains nontrivial changes to make.

Ok, will do!


DocData: Fix serialization of Variant default values

Co-authored-by: Bojidar Marinov<EMAIL_ADDRESS>

Cherry-picked for 3.2.1.


events_to_raster should provide option to not shift timestamp of first event to 0

Currently, when converting a list of events to a raster, using ChipFactory.events_to_raster, the timestamps will be aligned automatically such that the time of the first event is 0. This can be useful when the timestamps start with a high value and we only care about the timings after the first event.
However, often the timestamper is reset before recording events and hence the time of the first event can be of interested. I suggest providing the option of not aligning timestamps, in order to preserve this information.

Implementation done, but still needs unit testing


Fix timeouts in multi process checkpoint test

2ms is too low for the session timeout. We were getting warnings saying
session timeout [2] is less than connection timeout [15000]
@LuQQiu @cheng-chang I think this could be the cause of the flaky test failures you've seen

Merged build finished. Test PASSed.

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

alluxio-bot, merge this please


Add an isTyping bool

It would be helpful to know if text is actively being typed. For example I use a queue system for successive messages but don't want to auto-dequeue if typing is in progress.
I personally just added public bool IsTyping { get; private set; } to the TextTyper and toggle it from appropriate locations.
Anyway, thanks for this lib. I was looking for something that handles colors and more critically, wrapping. So far this works well!

Good call - thanks for submitting the issue. I added the Property. For now it just checks to see if the coroutine is assigned, so that I don't have to remember to flag it.


Add opt-in support for post 1.0 Sign-extension operators

Some use cases, such as Grain and AS need Sign-extension operators, which is newly introduced feature in 1.1 specification.
invalid function (105/323): invalid instruction 0xc0

Sorry, this is duplicate of #66 . Let me close this issue.


Added ConnectionCallBackFunc to options

Connection call back function called when client connected to channel. Function receive channel name

What does this accomplish?
What will be the use case for this feature?
Why only a method for new clients connected? What about disconnect clients? New channells and everething else?


Review readme 00 Boilerplate

Not assigned

Assigned to @linuxonrails

@rocioghermoso  waiting confirmation to merge the PR ...


DocValue false and Stored false fields are attempting to be created on index time

https://github.com/lucidworks/spark-solr/blob/43a49fba9e673d8f6e75cec5b59d02ab3a68f0f3/src/main/scala/com/lucidworks/spark/util/SolrQuerySupport.scala#L345-L347
When attempting to index into fields that are non-stored and non-docvalues, spark attempts to create the fields before indexing them. The fields exist already so they should be skipped over.
In addition...
https://github.com/lucidworks/spark-solr/blob/43a49fba9e673d8f6e75cec5b59d02ab3a68f0f3/src/main/scala/com/lucidworks/spark/util/SolrQuerySupport.scala#L271
Dynamic fields aren't being filtered out for indexing.

@thejerrybao Finally got time to fix this issue. Can you check out https://github.com/lucidworks/spark-solr/pull/227 ?
 fieldDefinitionsFromSchema.filterKeys(k => if (skipDynamicExtensions) !k.startsWith("*_") && !k.endsWith("_*") else true).foreach {

The above line skips fields *_s, etc.. from the schema. We do filter out dynamic field names here
https://github.com/lucidworks/spark-solr/blob/43a49fba9e673d8f6e75cec5b59d02ab3a68f0f3/src/main/scala/com/lucidworks/spark/SolrRelation.scala#L657
I have added a test here https://github.com/lucidworks/spark-solr/pull/227/files#diff-56e75c0dfecd9c6ad7c312bfdb924e60R74
Could you please take a look and let me know if I am not missing something here that you think is a bug?

@kiranchitturi awesome thanks for the fix! Looks great to me.
In regards to the dynamic field names, in my testing (several weeks ago), I found that they weren't being filtered out. Maybe a test to see if they're filtered out would help?

@thejerrybao Thanks for getting back!
I have added dynamic field names to the test here https://github.com/lucidworks/spark-solr/pull/227/files#diff-56e75c0dfecd9c6ad7c312bfdb924e60R74
In the test fields a_s, s_a are being filtered out as they match *_s and s_* patterns in dynamic names. Was there any particular dynamic field that was not filtered out in your test?

hmm yeah. I was thinking one wouldn't use those as field names in a document while indexing to Solr

@kiranchitturi Could I get a 3.5.5 release to use the fix? :)

@thejerrybao 3.5.5 fix has been out http://repo1.maven.org/maven2/com/lucidworks/spark/spark-solr/3.5.5/. I forgot to update the README

Ah okay thanks @kiranchitturi; didnt check the maven repo and only looked at the tags here haha.

my bad there. I did the release but forgot to push the tags


Enable C++11/14 for RecastDemo in Travis/Appveyor

Stemmed from discussions on #160
Apparently this is difficult with Travis' ancient setup.
http://genbattle.bitbucket.org/blog/2016/01/17/c++-travis-ci/
We'll also need to determine which Appveyor environments we can use as well.  We're currently compiling back to VS2010, which has a weird half-implementation of C++11.  I think this will really come down to "lets build VS2010 until we can't."
The rationale for using 11/14 is that they give us performance and code clarity gains out of the box.  These come with the drawbacks that they only work on platforms with modern compilers.  Where RecastDemo is mainly going to run on Windows, OSX, or Linux, this is not an issue, and we should be fully taking advantage of new C++ features where it makes sense.
This however, is not the case for Recast and Detour itself.  We're not 100% certain that modern game platforms are running with modern compilers, so we really have to assume they're not.  Things definitely are moving in the right direction in the industry, but I can't speak for every user of Recast having access to a modern C++ toolchain.

It might be useful to set up a build matrix for travis, one with -std=c++98 that would build only Recast and Detour and another one with latest C++11/14 features building RecastDemo too.
This will allow to take advantage of latest C++ improvements in RecastDemo while being notified if some C++11 code slips into R&D.

I've decided I strongly dislike Travis. They just really don't care about C++. I may look into getting our own build machine on Azure or something...

got any particular issue ? I use travis for https://travis-ci.org/TrinityCore/TrinityCore and it works very good after the initial painful apt-get setup (installing up-to-date tools that support C++11 and such).
I'd like to help if you need to set it up

I was trying to get clang 3.8 and GCC 5 working, but Travis' environment is just so out of date... I've been having a nightmare in this branch: https://github.com/hymerman/recastnavigation/tree/cpp11
Last time I tried, Travis had clang 3.4 which failed for weird reasons (found an example build: https://travis-ci.org/hymerman/recastnavigation/jobs/97120714). I see TrinityCore is using clang 3.5 on Travis - that's still quite old but maybe it'll work for us (it is C++14 complete)... GCC is just stuck at 4.8 forever it seems.
The objective here is to get the core libraries building with C++03 and C++11/14, and to build the demo under C++11/14. Looks like we can accomplish this with a build matrix using GCC 4.8 for just the core libraries, and clang 3.5 for everything in C++14 mode. I'll give that a try next :)
I'm still annoyed with Travis though - we've spent a lot of time trying to get it to do what we want, it would be way easier to do if we were just hosting CI ourselves! Ugh.
(thanks jackpoz, btw :) )

After changing the Ubuntu distro to 14.04 (which I see you did already) installing an updated compiler version comes down to "Install gcc X on Ubuntu 14.04" (which I know is still going to be painful to setup with travis, speaking for experience).
If it can help I'll link what we used for a while to add new repos https://github.com/TrinityCore/TrinityCore/blob/a6f6bb4fccb6c0a5123ef7fd553cf12b6a31db1f/.travis.yml#L12 , useful when the current repos don't have the tool versions required.
Build matrix let you define env variables that you can use to execute different apt-get commands depending on which job you are running at the moment. The resulting .travis.yml will look ugly and unreadable but that seems to be a common thing among all *.yml files :) Maybe start with 1 single job, that's still going to require enough effort to get it to work.
TrinityCore is using clang 3.5 as lowest supported compiler on purpose, it was also a requirement to keep using travis when llvm.org disabled their apt-get repo for a few days last June(which ofc broke all our builds)

I've come around on this over the years and don't think it's a terribly useful change.  While C++ > 03 will come with some conveniences in RecastDemo, the current code is working and the overhead of keeping the demo and library code separate and consistent is probably not worth the benefits we'd get from allowing newer C++ versions.


Remove the service and the conf files of the RPM

We need to stop and remove the gogs service and the conf file that come
with the RPM. Otherwise, the module will not work. See
https://github.com/Siteminds/puppet-gogs/issues/28

Hi,
What do I need to do to get my PR accepted?

Sorry... I've been @ home with a pneumonia last week...


Add constants, shutdown method, init_always function to reinit

This PR adds the constants from default_store.c, a shutdown method, which ends the netsnmp-session and adds init_always which inits the library every time, not just once.

I did the renameing


Update README.md

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Did you look at the other 3 PRs? :)

Did you look at the other 3 PRs? :)

so?


Appearance of the edited cell with the date data type

System information:

Operating system: Ubuntu 20.04
DBeaver version: <IP_ADDRESS>202051448, <IP_ADDRESS>205011839

Describe the problem you're observing:
The appearance of the edited cell with the date data type is different from cells with other data types.
https://user-images.githubusercontent.com/9607501/167280542-3c5e2c41-39e0-4001-b671-f2269b58adeb.mp4

Hello, I'd like to work on this issue.

Hello, I'd like to work on this issue. 😃

It seems that this problem is due to the fact that date or time types do not have a method like Text.selectAll() that can be called directly.
So my idea is to add a similar method to the CustomTimeEditor for all selecting the contents of a cell of the date type.
It seems that the issue is solved through it.
https://user-images.githubusercontent.com/58755868/170281984-b3220282-5025-471c-8172-3b75c8578c33.mp4

This issue is still unresolved, the cell borders are still displayed differently.
Operating system: Ubuntu 20.04.4 LTS
DBeaver version: <IP_ADDRESS>206051253
https://user-images.githubusercontent.com/9607501/174433678-d1c5e360-bbd7-4f26-95c1-47142f1021ba.mp4


Use A tags instead of buttons for sidebar

Using buttons means that you can't do things like middle click a chat to open it in a new tab. Anything that changes the URL should be an A tag, not a button.
I'd also encourage you to make the settings page accessible as an actual page, not just as a modal dialog.

Good idea! As for the settings modal, I'm actively considering it!


Use external cluster for postsubmit as well

@kyessenov Sorry about this. You need to do it for every new node.

rebuild manager/presubmit

Jenkins job manager/presubmit passed


add explicit versions to POM

Codecov Report

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

@@            Coverage Diff            @@
##             master     #603   +/-   ##
=========================================
  Coverage     73.43%   73.43%
  Complexity      783      783
=========================================
  Files            54       54
  Lines          3851     3851
  Branches        482      482
=========================================
  Hits           2828     2828
  Misses          822      822
  Partials        201      201

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86385fa...ed89ed7. Read the comment docs.


Rdm 10196 develop

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RDM-10196
Change description
Improve readiness checks
Does this PR introduce a breaking change? (check one with "x")
[X] Yes
[ ] No

Reopening this pull request as it is closed automatically.

Reopening this pull request as it is closed automatically.


ECS structuring

Great project! It expands a lot the vision of what kind of interactive experiences can be done on the web with Three.js.
Do you have thoughts about structuring with ECS pattern, using a lib like ECSY ?
Here is an ECSY example project also using typescript and physics: https://github.com/macaco-maluco/thermal-runway

Interesting. Is that basically the Unity philosophy of "everything's an object within a scene with components attached to it"?
Would it maybe reduce the size of my character class and make it easier to navigate? Since it would just be an entity with components attached to it...?
On the other hand it seems like I'd be a slave to a strict project structure. Maybe that's a good thing but it's a bit scary.
Maybe after 0.4 is released, I'll look into this. But it seems like a lot of work. And there's some custom systems and philosophies in sketchbook (like character states), and I'm not entirely sure how they'll fit with the ESC pattern.
I'm putting this in the research phase, since I'm not that educated on how a ESC project looks like. I'll have to look into it more. 🙂

Yes, it’s like Unity in the sense that Components (MonoBehavior) can be shared between Entities (GameObjects) but there is a difference: behavior is defined in Systems, not in the Component itself.
It's much more similar to the new Unity DOTS, where data and operations/behavior are separated.
Components holds only data
Entity has components
Systems operate on entity's components
A System can specify a combination of Components it needs, then it filters and cache only Entities that have this combination to iterate them, implement the operation/behavior and transform the data in Components.
ECS favors reuse by composability over inheritance, it helps not to mix things that could be reused and to keep the operations focused and clean.
Some ECS libs in C++ (and also Unity DOTS in combination with Burst compiler) claims it improves even performance if used correctly, I don’t think it’s the case for JS but the overhead seems to be minimal looking at ECSY benchmarks.
In the long run, for medium to big complexity projects, I believe it helps with organization, reusability and maintainability.
As a reference for a future restructuration or experiment, Mozilla Hubs is large Three.js/Aframe application that is experimenting a migration to ECSY:
https://github.com/mozilla/hubs/compare/feature/ecsy-integration
https://github.com/mozilla/hubs/compare/ecsy-simple-entity-api
(I don't know if it goes further now with some sad recent Mozilla events)


autobump issue tracker

cannot get version

freetds, linux runner cannot get version, https://github.com/Homebrew/homebrew-core/pull/167534
mikutter, linux runner cannot get version, https://github.com/Homebrew/homebrew-core/pull/167452

weird versioning

luajit https://github.com/Homebrew/homebrew-core/pull/169535

macos dependency issue

organize-tool, needs macos-tags, https://github.com/Homebrew/homebrew-core/pull/168089

formula dependency issue

certbot, needs runner to have augeas before the bump, https://github.com/Homebrew/homebrew-core/pull/168249
mesa, some resource issue, https://github.com/Homebrew/homebrew-core/pull/169383

python issue

nicotine-plus, https://github.com/Homebrew/homebrew-core/pull/171198

weird release url

jdtls, cannot be autobumped, https://github.com/Homebrew/homebrew-core/pull/167889
selenium-server, weird release flow (patch version update use the same minor version release), https://github.com/Homebrew/homebrew-core/pull/167536

https://github.com/Homebrew/homebrew-core/pull/197977 (vttest cannot be autobumped)

https://github.com/Homebrew/homebrew-core/pull/200109 (resource issue)

https://github.com/Homebrew/homebrew-core/pull/200132 (cannot run with linux runner)


Fix typo in theme.go

Just something I ran into while grepping the theme --help output for environment 😹

Thanks!


Iron Router infinity reloads with polymer.

It seems that importing polymer elements by <link rel="import" href="bower_components/xxx/xxx.html"> will let the iron router infinity reload some times. For example, https://piet.cn// (Must use double / to show this problem.)

@ThaumRystra Thank you, thank you, thank you! I had the same issue here: http://goo.gl/fL6JIK and your findings really helped. Thank you so flipping much!

@SylarRuby awesome, so does this solve #1323?

Yes it has. Im very happy.
On Thursday, 23 April 2015, Stefan Zermatten<EMAIL_ADDRESS>wrote:

@SylarRuby https://github.com/SylarRuby awesome, so does this solve
#1323 https://github.com/iron-meteor/iron-router/issues/1323?
—
Reply to this email directly or view it on GitHub
https://github.com/iron-meteor/iron-router/issues/1052#issuecomment-95573257
.

It's surprise to see more discuss here. I've already figured it out but forgotten to tell you what the problem is. Sorry for my fault.
Here's more detail about this issue.
If you try to include some .htmls which didn't exist, you will get the infinite loop. Solution is simply delete the <link> tag which imports a missing html. But it shouldn't be a infinite loop, I guess.
I'm no longer using iron:router for routing now, since meteorhacks:flow-layout might be a simple and clear solution for my app. Still, iron:router is a wonderful router solution. Also, I learned a lot in dealing with these bugs, and now I am able to play well with Meteor. Thank you @cmather for your hard work in making a easy-to-learn and powerful router solution!


chore: Upadate version to 0.0.14-rc-1

Upadate version to 0.0.14-rc-1 as a 1st release candidate

Can one of the admins verify this patch?

[test]


Direct Line JS: Backoff on 429, stop on 404, and relax on 400

We should implement backoff and error handling logic correctly.

429, we will backoff
404 (bot is gone), we will stop
400 (something wrong on client request), we will backoff

Check the following:

Start conversation (startConversation)

Poll by REST API (pollingGetActivity)
Web Socket connection

Get stream URL (reconnectToConversation)
Upgrade call (observableWebSocket)

Post activity (postActivity)

Tracking this issue on #124 (uber-bug on "resume conversation story").


How to write listen/accept loop

Looking into the book it suggest the following way to build accept loop:
async fn accept_loop(addr: impl ToSocketAddrs) -> Result<()> {
    let listener = TcpListener::bind(addr).await?;
    let mut incoming = listener.incoming();
    while let Some(stream) = incoming.next().await {
        let stream = stream?;
        println!("Accepting from: {}", stream.peer_addr()?);
        let _handle = task::spawn(connection_loop(stream)); // 1
    }
    Ok(())
}

This can crash quickly:
$ cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/example-server`
Error: Too many open files (os error 24)
$

So what we're going to start from this:
pub async fn accept_loop(addr: impl ToSocketAddrs) -> Result<()> {
    use std::io::ErrorKind::*;
    let listener = TcpListener::bind(addr).await?;
    let mut incoming = listener.incoming();
    while let Some(stream) = incoming.next().await {
        let stream = match stream {
            Ok(stream) => stream,
            Err(e) => match e.kind() {
                // These errors that are per-connection.
                // Which basically means that if we get this error from
                // `accept()` system call it means next connection might be
                // ready to be accepted.
                | ConnectionRefused
                | ConnectionAborted
                | ConnectionReset
                => continue,
                // All other errors will incur a timeout before next
                // `accept()` is performed.  The timeout is useful to handle
                // resource exhaustion errors like ENFILE and EMFILE.
                // Otherwise, could enter into tight loop.
                _ => {
                    warn!("Error {}. Sleeping 100ms to retry.", e);
                    task::sleep(Duration::from_millis(100)).await;
                    continue;
                }
            },
        };
        spawn_and_log_error(connection_loop(stream));
    }
    Ok(())
}

(note that there is no fatal error in the accept loop, and if there are on any platforms, we should break a loop and proceed with graceful shutdown instead of returning on error)
This is just to show the problem. What really has to be done for a production listener is at least the following (from most important to least important):

Retry on an error as above (and I'm pretty sure this works on Linux, but I don't have confidence for that on all platforms)
Limit on the number of simultaneous connections
Listener shutdown (I don't see the tutorial to implement the shutdown of the listener itself, it looks like it shuts down only broker if the listener is gone). Maybe implement #653.

While I can figure out all of that stuff myself. I'd like that we have some default solution for the ecosystem, and add it to the book.
I've already tried to make that abstraction for the tokio. It works nicely for the world of futures 0.1. But I'm looking for ways to redo the same for async-std world.
What do you think? Can some similar abstraction be incorporated into the async-std itself? Or a separate crate? Should it just be a snippet in the book? Or a combination of them?

@tailhook thanks for taking your time to go through this in detail. I agree that we should have better controls for this. As a general theme though, async-std tries to mimic std's behavior as closely as possible. I think for example https://github.com/async-rs/async-std/issues/653 is exactly the kind of change that we should make to async-std.
However, the tk-listen logic should probably indeed be a separate crate. I think for the purposes of the example we should probably keep it simple, but then mention at the end of the tutorial that if running something in production a listen-like wrapper should be used for security and correctness.

Add a book section in #666. Let me know if this is not what you were talking about.
I also want to fix the tutorial example of the accept loop to be less crashy, but I'll make a separate PR for that.


Colors of files/Directories missing when using lsd and tmux

Expected behavior
lsd output should include coloring the files/directories when using tmux.
Actual behavior
when running lsd and tmux, only the attributes of the files/directories are colored except the leading d in case of a directory. The names of the files/directories are white.

That was my mistake, I had not set the proper TERM.
Set properly, I have all the colors on my tmux panes.
Apologies!


docs: supporting non-root users

Since the introduction of Jupyter Notebooks the necessity of accessing
files by non-root users became evident, now we add all non-root REANA
users to root group so we can access files and directories
(closes #149).

Thanks for the input, comments addressed :)


corrected abstract class usage and logging prefix

fixes https://github.com/DivanteLtd/vue-storefront-api/issues/497

i'll redo it


hello, Cloud you please code a strategy that use different time frame RSI and CCI. Because I have already earn much money by this way. Thank you!

Sorry, this isn't directly related to the RSI with Alert indicator.


Inovelli VZW31 - Param 99 - Unable to set effect to Clear(255)

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
According the config database param 99 byte 4 is supposed to support a clear option of 255. This option does not appear in the zwavejs ui. I also cannot set 255 via a service call to  zwave_js.set_config_parameter.
https://devices.zwave-js.io/?jumpTo=0x031e:0x0015:0x0001:0.3

service: zwave_js.set_config_parameter
data:
  endpoint: 0
  bitmask: "0xff000000"
  parameter: "99"
  value: "255"
target:
  entity_id: light.driveway_light

Error:
Failed to call service zwave_js.set_config_parameter. Node(node_id=70) - InvalidNewValue: Must provide a value for 70-112-0-99-4278190080 that represents a valid state key or label from {"0": "Off", "1": "Solid", "2": "Fast Blink", "3": "Slow Blink", "4": "Pulse", "5": "Chase", "6": "Open/Close", "7": "Small to Big", "8": "Aurora", "9": "Slow Fall", "10": "Medium Fall", "11": "Fast Fall", "12": "Slow Rise", "13": "Medium Rise", "14": "Fast Rise", "15": "Medium Blink", "16": "Slow Chase", "17": "Fast Chase", "18": "Slow Siren", "19": "Fast Siren"}

Device information
Manufacturer:
Model name:
Node ID in your network:
How are you using node-zwave-js?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
zwave-js-ui: 8.21.2
zwave-js: 11.6.0
NOTE: I think I selected the correct option for "How are you using node-zwave-js?". I'm using the HA addon for zwave-js-ui and zwave-js integration.
Home Assistant 2023.7.3
Supervisor 2023.07.1
Frontend 20230705.1 - latest
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
Device is added with S2.
In the UI when I select debug info here param 99 effect. Notice 255 or clear is missing.
{
      "id": "70-112-0-99-4278190080",
      "nodeId": 70,
      "toUpdate": false,
      "commandClass": 112,
      "commandClassName": "Configuration",
      "endpoint": 0,
      "property": 99,
      "propertyName": "All LED Strip Effect - Effect",
      "propertyKey":<PHONE_NUMBER>,
      "type": "number",
      "readable": true,
      "writeable": true,
      "label": "All LED Strip Effect - Effect",
      "default": 0,
      "stateless": false,
      "commandClassVersion": 4,
      "min": 0,
      "max": 19,
      "list": true,
      "allowManualEntry": false,
      "states": [
        {
          "text": "Off",
          "value": 0
        },
        {
          "text": "Solid",
          "value": 1
        },
        {
          "text": "Fast Blink",
          "value": 2
        },
        {
          "text": "Slow Blink",
          "value": 3
        },
        {
          "text": "Pulse",
          "value": 4
        },
        {
          "text": "Chase",
          "value": 5
        },
        {
          "text": "Open/Close",
          "value": 6
        },
        {
          "text": "Small to Big",
          "value": 7
        },
        {
          "text": "Aurora",
          "value": 8
        },
        {
          "text": "Slow Fall",
          "value": 9
        },
        {
          "text": "Medium Fall",
          "value": 10
        },
        {
          "text": "Fast Fall",
          "value": 11
        },
        {
          "text": "Slow Rise",
          "value": 12
        },
        {
          "text": "Medium Rise",
          "value": 13
        },
        {
          "text": "Fast Rise",
          "value": 14
        },
        {
          "text": "Medium Blink",
          "value": 15
        },
        {
          "text": "Slow Chase",
          "value": 16
        },
        {
          "text": "Fast Chase",
          "value": 17
        },
        {
          "text": "Slow Siren",
          "value": 18
        },
        {
          "text": "Fast Siren",
          "value": 19
        }
      ],
      "value": 0,
      "lastUpdate":<PHONE_NUMBER>783,
      "newValue": 0
    },

Are you on the latest addon version?
Even if you are, I'm a bit confused why that option is missing. There weren't any changes for that configuration file after being added.

Doh. I had a custom template. I removed it refreshed the values. All good now.


Upgrade nightly wheels to ROCm5.3

Dependent on PR https://github.com/pytorch/pytorch/pull/89101

@malfet ROCm wheel build CI jobs passed

@malfet @kit1980 Is it a requirement to rebase if the PR UI shows that the branch is out-of-date? It looks like it does that very frequently, forcing a rebase and rerun of all CI jobs :/
Also, in the latest runs, only ROCm CI job failing is https://github.com/pytorch/audio/actions/runs/3634116978/jobs/6131885610, but it seems to be a flaky connection timeout error.
Can we please merge this PR?

@jithunnair-amd no need to rebase, I just need to start land internally


Prevent rerender caused by changes in action sheet provider

On our android app, when opening an action sheet, everything inside will be rerendered twice. This PR can decrease once.

found better solution


Use EventEmitter.errorMonitor instead of overwritting emitter.emit

This the right way to silently listen for the error event. Note it's available since v12.16.0.

Fixed in b8dabf9bbd64c71ed702064bb78123a70e7c069c


Game "One Piece: Treasure Cruise" crashes on startup.

Title. The game crashes during its loading screen. Any idea what's causing this or if there's a workaround?

Added logcat log. "com.namcobandaigames" should refer to the game I believe
logcat.txt


edvart imports isort but doesn't install it

Steps to reproduce:

install edvart in fresh environment
import edvart

Hi @NevoleMarek,
thanks for reporting this! #181 fixes the issue and we will release a patch version right after it's merged.


Remove unneccessary AppsandFeaturesEntries * manifests/l/LightZoneProject/LightZone/4.2.4/LightZoneProject.LightZone.installer.yaml

Microsoft Reviewers: Open in CodeFlow

URL:
Invalid URI: The hostname could not be parsed.
(Automated message - build 899)


Decimal 0.691 is not accurate even after the fix for issue #777

Your JSON dictionary:
{
  "quantity": 0.691
}

Your model:
struct Repo: Mappable {
  var quantity: NSDecimalNumber?

  init(_ map: Map) {
    quantity <- (map["quantity"], NSDecimalNumberTransform())
  }
}

What you did:
let repo = Mapper<Repo>().map(myJSONDictionary)

What you expected:
I exepected something like:
Repo(quantity: 0.691)

What you got:
Repo(quantity: 0.6909999999999999)  // expected the quantity is 0.691

Unfortunately this is not caused by this library. After some investigation I have found that NSJSONSerialization will decode numbers as doubles before falling back on NSDecimalNumber when the value is too large to fit into the Double type, as described here: http://stackoverflow.com/a/39553617
Essentially the first step from converting JSON data to a Swift Dictionary [String: Any] introduces the Double type, and this is then passed into this library to map. From there it is converting Double to NSDecimalNumber, but the precision is already lost.
The result is that if you require precision you should encode your numbers as Strings in JSON.
let jsonString = "{\"quantity\": 0.691}"
let data = jsonString.data(using: .utf8)!
let json = (try? JSONSerialization.jsonObject(with: data, options: [])) as? [String: Any]
let value = json!["quantity"]!

print("\(type(of: value)) \(value)")
// prints __NSCFNumber 0.6909999999999999

Using a String to hold the JSON number, and using your example to map the model into an object instead yields:
let jsonString = "{\"quantity\": \"0.691\"}"
let repo = Mapper<Repo>().map(JSONString: jsonString)
let value = repo!.quantity!

print("\(type(of: value)) \(value)")
// prints NSDecimalNumber 0.691

Thanks @Jake000 . Wonderful explanation! The limitation is actually in the JSON data type definition. Number in JSON is defined as double-precision floating-point.
If I want to code a workaround for my case, and the decimal number is always 3-decimal place or less. How can I add the 3-decimal place rounding from Double to NSDecimalNumber in my own NSDecimalNumberTransform()?
MyNSDecimalNumberTransform.swift
     open func transformFromJSON(_ value: Any?) -> NSDecimalNumber? {
          if let string = value as? String {
              return NSDecimalNumber(string: string)
          }
          if let double = value as? Double {
  		} else if let number = value as? NSNumber {
  			return NSDecimalNumber(decimal: number.decimalValue)
  		} else if let double = value as? Double {
              return NSDecimalNumber(floatLiteral: double)
          }
          return nil

The best solution would be to use Strings to hold numbers in JSON.
Using the previous example, the first option would be much more preferable to the second as it will be decoded as a String which can be converted lossless to a decimal number.
{ "quantity": "0.691" }

{ "quantity": 0.691 }

If you are not able to change the incoming JSON (eg. it is from a service you do not own) then you can always round the result to 3 decimal places.
extension NSDecimalNumber {
    func rounded(places: Int) -> NSDecimalNumber {
        var decimalValue = self.decimalValue
        var result: Decimal = 0
        NSDecimalRound(&result, &decimalValue, places, .plain)
        return NSDecimalNumber(decimal: result)
    }
}

let jsonString = "{\"quantity\": 0.691}"
let data = jsonString.data(using: .utf8)!
let json = (try? JSONSerialization.jsonObject(with: data, options: [])) as? [String: Any]
let value = json!["quantity"] as! Double
let decimal = NSDecimalNumber(value: value)
let rounded = decimal.rounded(places: 3)

print("\(type(of: rounded)) \(rounded)")
// prints NSDecimalNumber 0.691

You can wrap this up in your own transform by subclassing the existing:
open class RoundedDecimalNumberTransform: NSDecimalNumberTransform {
    open override func transformFromJSON(_ value: Any?) -> NSDecimalNumber? {
        return super.transformFromJSON(value)?.rounded(places: 3)
    }
}

Thanks @Jake000 !!

I made my own DecimalNumbertransform function like this. I'm not good at Swift. Just to share what I did to workaround my own problem.
import Foundation
import ObjectMapper

open class MyDecimalNumberTransform: TransformType {
    public typealias Object = NSDecimalNumber
    public typealias JSON = String

    public init() {}

    public func transformFromJSON(_ value: Any?) -> NSDecimalNumber? {
        if let string = value as? String {
            return NSDecimalNumber(string: string)
        } else if let number = value as? NSNumber {
            let handler = NSDecimalNumberHandler(roundingMode: .plain, scale: 3, raiseOnExactness: false, raiseOnOverflow: false, raiseOnUnderflow: false, raiseOnDivideByZero: false)
            return NSDecimalNumber(decimal: number.decimalValue).rounding(accordingToBehavior: handler)
        } else if let double = value as? Double {
            return NSDecimalNumber(floatLiteral: double)
        }
        return nil
    }

    public func transformToJSON(_ value: NSDecimalNumber?) -> String? {
        guard let value = value else { return nil }
        return value.description
    }
}

Mapping in the model like
struct Repo: Mappable {
  var quantity: NSDecimalNumber?

  init(_ map: Map) {
    quantity <- (map["quantity"], MyDecimalNumberTransform())
  }
}


Requiring -i for 'mbed export'

This should fix #410. It requires the -i argument for mbed export.

LGTM

Y'all are quick! :smile:


[WelcomeUX] Walk-through: ATA does not work on Linux

Testing #18091

It works on Linux and OSX. Hovers also don't work on Linux. This looks like the TypeScript extension decided to not handle the resource.

It turns out that if there is a folder open with TypeScript files, but no tsconfig.json, these files will count against the default project and get that into TypeScript mode, disabling ATA for all JavaScript files/resources.

Still in:

VSCode Version: Code - Insiders 1.19.0-insider (dc84f454ea245a1131e28557de1204b8cd1cc320, 2017-11-30T06:07:29.674Z)
OS Version: Darwin x64 16.7.0


Add background color for table rows in both tables

This branch will be merged by a new name called "feature/INT-618_table-row-background"


pull secrets option display mismatch when creating workload

Expect: Show only Kind: Registry
Actual: All Secrets

I have opened a ticket to the upstream. https://github.com/rancher/dashboard/issues/6725

The pr to fix this issue has been merged, the next version will include this fix

Fixed by v0.2.12-rc1.


Fetch Refactor: Final cleanup of remaining rest-hooks

Problem statement
As a report stream developer I want to replace all instances of usage of rest-hooks with react query based hooks. Though most of the work has already been completed, this final ticket is to:

Discover any remaining dependencies/occurrences of rest-hooks in the code base
Fix those dependencies/occurrences over to react-query
Remove rest-hooks as a dependency of the project

This will allow us to completely move over to react-query with no more dependency on rest-hooks.
Notes
Remove all remaining traces of rest-hooks

testing
packages
helper files

Check anything else we may have missed
Acceptance criteria

[ ] Discover any remaining dependencies/occurrences of rest-hooks in the code base
[ ] Fix those dependencies/occurrences and replace with necessary react-query code
[ ] Remove rest-hooks as a dependency of the project
[ ] Check that when the rest-hooks package is removed from the app, everything still works as normal

To do
Check:

[ ] testing
[ ] packages
[ ] helper files
[ ] components
[ ] Check anything else we may have missed

@jpandersen87 @stephenkao Is this issue still valid as written?
It seems a little old and sparse, so checking to see if it is ready for team refinement this week.

did you all already transition all of the rest hooks based api calls to react query?

I think @jpandersen87 can speak more to this.  The work to remove the rest-hooks package is still valid, but it looks like Joseph's draft branch is removing a lot of references to the package exports from our code -- so depending on what comes out of that, this ticket may be redundant.  Maybe let's slap a needs-info label on it and close if it turns out to be covered?  What do you think @jpandersen87?

This is more like a parent ticket to the ones that I have been doing to update fetching hooks to react-query.

my intention with this ticket was as a final cleanup - once the application is fully functioning with react query, all of the remaining cruft around rest hooks (testing, helpers, types, etc.) can be removed. I evidently didn't take the time to catalog where all of that stuff was, though

@jpandersen87 So is your current work covering everything in this ticket and the concerns mentioned by Doug above?
I am just trying to figure out if we need this ticket anymore, or if we need to rewrite it.

This is blocked by all of the other hook replacement tickets. Search "hooks" with tech-debt label to see them.

@KeithNava followup and possibly refactor as a cleanup ticket


Add local service tests

There is no longer a local auth service but instead a provider plugin feathers-authentication-local which is fully tested.


fix: correct make cmd for creating cilium cluster

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

/azp CNI Load Test

/azp run CNI Load Test


fix some allocation in prognostic edmf implicit solver

Purpose

This brings down the difference in allocation between implicit and explicit prognostic edmf from several orders of magnitude to 10. I'm not sure where the factor 10 is, and we can look at it further. Turns back on implicit_diffusion in the performance job config. Part of #2818
To-do

Content

[ ] I have read and checked the items on the review checklist.

hmm the allocation still increases by several orders of magnitude in the buildkite job. I'll take a look tomorrow.

Now the allocation is back to 10x increase. It also fixes some gpu errors, but there is one remaining. I'll look at it in the next PR.

So, in summary, this adds implicit diffusion, which drastically increases allocations, and then the code changes reduce the allocations, but the result is that it's still 10x the current allocations? If I've got that right, then feel free to merge!

Yes, it's hard to say how much the increase was before, as the job kept failing. After I fixed something it was 10000x, so it was more than that. And now after this PR it is 10x.

Also, you may want to rebase after the inlining has landed!
Sounds good!

I think some of these issues will be upgraded in julia 1.11


Multiple instantiated exported Arrays in Resources share the same instance

Godot version
3.4.4.stable
System information
Windows 10 version 10.0.19044
Issue description
What doesn't work:
Arrays that were instantiated in a resource using export var array = [] share the same array instance if there are multiple instantiated arrays
Using export var array :Array does not result in this behaviour
Dictionaries are not affected
Expected:
Different array variables should have different instances
Steps to reproduce
Code taken from the minimal reproduction project, simply run it to get the result
TEST.gd
extends Node2D

var res = preload("res://CustomResource.gd")

func _ready():
	var a = res.new()
	a.array1.append("2137")
	print("array1 = ", a.array1)
	print("array2 = ", a.array2)
        print("no_export array = ", a.no_export_array)

CustomResource.gd
extends Resource

export var array1 = []
export var array2 = []

var no_export_array = []

Console  output
array1 = [2137]
array2 = [2137]
no_export array = []

Minimal reproduction project
ResourceExportArrayMinProject.zip

Related to https://github.com/godotengine/godot/issues/20436.


AVRO Schemas with more than one level of recursion are not correctly published in the schema registry.

Describe the bug
Having three Avro schemas i.e A,B,C where C contains B, B contains A,  each nested reference is using "subject" as field to solve the reference and a schema definition where we have three of them defined using schemaLookupStrategy:RecordNameStrategy.
The provisioning is failing when processing C because A is not defined in the schema B. Seems like is not posible to resolve the schema A once it reads B from C, but it can resolve it when reads B directly
To Reproduce

Create three nested scehmas like in the descirption
Create a specmesh definition where the three of them are published and with RecordNameStrategy
Execut the client
It will file when parsing one of the schemas

Expected behavior
Be able to resolve all the nested references
Actual behaviour
It can resolve reference when a nested schema  use a schema with nested references
Version info

What version of SpecMesh is affected? 0.9.4 and 0.12.1
What OS are you on? mac

Additional context
The iteration of the schemas is not recursive so is only processing the first schema properly and the parse method is breaking here https://github.com/specmesh/specmesh-build/blob/main/kafka/src/main/java/io/specmesh/kafka/provision/schema/SchemaReaders.java#L98

@aivaldi can you please provide example spec and schemas please?


Revise Vector.zip error handling

This task is automatically imported from the old Task Issue Board and it was originally created by Radosław Waśko.
Original issue is here.

Our Table.zip implementation has a nice keep_unmatched : Boolean | Report_Unmatched functionality that allows to specify what to do if zipped tables have differing row counts.
Vector.zip blindly truncates to the shorter of the two vectors.
It may be good to align its API with the Table one. We usually do not do warnings in the most primitive types like Vector, but we could probably Report_Unmatched as a dataflow error. If keep_unmatched=True we can do the longer vector and pad with Nothings.
We need to revise if we should keep the current behaviour as default or change it. I think it may be safer to default to throwing a dataflow error if the lengths do not match (usually when zipping we do expect length to match) and only allow the user explicitly tell that they expect the lengths may differ and explicitly say what should happen in that case (by setting True/False the users specifies if we keep the longer vector and pad or truncate to the shorter one).

Will replace with a new issue


Add cookstyle linting as default

Description
This modifies the default config.json in a generated cookbook to include cookstyle linting in the build cookbook.
Issues Resolved
Fixes #1146
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Closing this PR to re-open because of unsigned commit.


[GWS] gws/portlets

Coverage decreased (-0.1%) to 80.178% when pulling 0e16d67d1d0f43362153c69576787aff07d6ce22 on tany:gws-portlet into 7a3752a0e5df54d37142749e627552892d1b3b4e on shirasagi:dev/gws.

Coverage decreased (-0.08%) to 80.212% when pulling 30e52c58a71006e7f390ebd03635567c2aa7bed3 on tany:gws-portlet into 7a3752a0e5df54d37142749e627552892d1b3b4e on shirasagi:dev/gws.


Missing git tag for 0.10.1 release

It would be nice to keep PyPI releases and git tags in sync :)

There is nothing new in that version. I even think it is the same git tag as v0.10.0

nope, 0.10.0 and 0.10.1 on pypi have different code (apart from the fact that 1 is a wheel and 2 is a tar.gz).
example difference:
0.10.1 - load_grammar.py

def load_grammar(grammar, source, re_, global_keep_all_tokens):
    return GrammarLoader(re_, global_keep_all_tokens).load_grammar(grammar, source)

0.10.0 - load_grammar.py

def load_grammar(grammar, source, re_):
    return GrammarLoader(re_).load_grammar(grammar, source)

See the changes in file sizes:

0.10.1 was uploaded because it was a wheel.
There should be no difference in functionality.
But you're right, I dropped the ball on this. They should be kept in sync.


Review Dependency Injection patterns for Migrations Commands and RevEng

We use different patterns of DI in Migrations Commands and RevEng. Review to see if we can re-use the patterns from the rest of the stack.

See #1751

Changes for better dependency injection for RevEng checked in with PR https://github.com/aspnet/EntityFramework/pull/2623


Manual segmentation of 3 missing M0 missing lesion mask

Opening this issue thanks to a comment from @leelisae regarding some missing lesion mask at M0.
Related issue #96
On it now with the following config file:
FILES_LESION:
- sub-edm161_ses-M0_PSIR.nii.gz
- sub-mon015_ses-M0_PSIR.nii.gz
- sub-mon052_ses-M0_PSIR.nii.gz
- sub-mon164_ses-M0_PSIR.nii.gz

Running the following code to perform manual segmentation of MS lesions:
python manual_correction.py -path-img ~/tmp_romane/ms_lesion_agnostic/data/canproco  -config ~/Desktop/manual_seg_lesion_missing_canproco.yaml  -path-label ~/tmp_romane/ms_lesion_agnostic/data/canproco/derivatives/labels  -suffix-files-lesion _lesion-manual -fsleyes-dr="-40,70"

I think that the mask for sub-mon052_ses-M0_PSIR.nii.gz should be deleted and the image added to the exclude file. I think that the spots that look like lesions are actually some artifacts.
GIF TO ADD

The subject sub-mon052_ses-M0 had already been added to the exclude.yml file: here.  Therefore, the mask is empty.
All segmentations were pushed to branch plb/segment_missing_4_lesion_seg
@jcohenadad Could you review the 3 segmentations before I send them to @leelisae ?
Also, @leelisae do you take into account the exclude.yml file when doing your computations ? We reference all the files which are problematic and which we don't use in our work. Usually the segmentations files are empty for them.

@jcohenadad Could you review the 3 segmentations before I send them to @leelisae ?

I cannot because of https://github.com/neuropoly/data-management/issues/321
If you'd like me to review ASAP send me the files via email/slack

Here are the 3 manually segmented segmentation file:  manual_segs.zip

hum... i don't seem to have M0:

and git pull does not work https://github.com/neuropoly/data-management/issues/321 (@namgo )
can you email me the files?

Great job @plbenveniste ! Here are my modifications (I only edited two subjects, but I modified the three JSON files to record the fact that I have reviewed the three segmentations): manual_segs.zip

Thanks a lot @jcohenadad !
Segmentations done and added to branch plb/segment_missing_4_lesion_seg.
PR was created and waiting for review.

@plbenveniste

Also, @leelisae do you take into account the exclude.yml file when doing your computations ? We reference all the files which are problematic and which we don't use in our work. Usually the segmentations files are empty for them.

Where can I find the exclude.yml file? I assumed that I could use all lesion mask files that are provided.

Here it is: exclude.yml (it's stored in this repo).


List available cloud regions

https://cockroachlabs.atlassian.net/browse/DOC-5794
List of available regions.

This change is


feat: add 8.2 config and supported elements

Undefined Task (related to https://github.com/camunda/camunda-modeler/issues/3230)
DataStore/DataObject (https://github.com/camunda/camunda-modeler/issues/3277)

Not sure what's happening with the CI but when running the tests locally there were two errors that needed fixing (cf. https://github.com/camunda/bpmnlint-plugin-camunda-compat/pull/59/commits/3d53c20e77363d4523daf3bff91b81039a615392, https://github.com/camunda/bpmnlint-plugin-camunda-compat/pull/59/commits/d11ef4bd0c0585de0b24c6786f2b5ec366764e49). I remember this happening before but I'm not sure why. Did the tests run successfully on your machine?

It did run successfully on mine (also linux, same as CI)


[Feature] OwnCloud Import

It would be nice to be able to import directly from an ownCloud folder.

Please see https://github.com/electerious/Lychee/issues/387 and https://github.com/electerious/Lychee/issues/346.


[HUDI-1294][WIP] Adding inline read for Hfile log blocks

What is the purpose of the pull request

Adding inline read for Hfile log blocks

Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Closing in favor of https://github.com/apache/hudi/pull/3762