some problem need help

@tkipf  Thanks for your code. Now I have some problem. I do a jupyter notebook  keras implement. However, when I run model.compile, throw a error.Can you help me? My jupyer url is https://github.com/searchlink/gcn/blob/master/keras_gcn_implement.ipynb

I have solve it!


Service Generator: feathers-memory

overview
Generated services can use feathers-memory as their models.
tasks

[x] add prompts
[x] install deps
[x] template service.json

demo

Merging this and moving onto dynamic configuration based on meta.json


Always return a location array [phab:D1851]

Created by djrenren at 2017-08-09 19:40:32:
The neovim language client chokes on a null return
from the server so be sure to always return an empty array

fromberger wrote at 2017-08-09 19:44:04:
Please add a comment somewhere in this file, documenting why it's important to return empty slices instead of nil. (You don't have to document each one, but either near one of them or maybe near the base type it would be helpful for future maintenance).

djrenren wrote at 2017-08-09 21:24:55:

Add comments explaining the non-nil slice restrictions

schroederc accepted this revision at 2017-08-09 21:31:56

fromberger accepted this revision at 2017-08-09 22:09:38

djrenren closed via commit edc243b6ef03dff103c98415cf76150480ef5284 at 2017-08-10 18:28:27


Alternative example implementation using oclif

I wanted to open an issue and explain the goods we'd get if we start using Oclif instead of coding and maintaining our own solution but it was too complicated to explain and too easy to actually implement the current behavior using Oclif. Bear with me, this implementation is an example and it's not fully replacing all the existing features.
I think I was one of the firsts to actually get excited with Ink in this project but the more I see it, the less I think we need it. Ink is cool but creating a great CLI experience is something that has been done many times in the past by different people and I think we can benefit from it. Ink is nothing else than a "view" framework for the CLI. I'm sure that, if we need it, we should be able to make it work together with Oclif. And here's my point, I don't think we'll ever need it. Have a look at all the Oclif plugins (this and especially this) and the Oclif documentation itself. Not to mention all the cool stuff we can do with Inquirer too.
So my proposal is that we get rid of React, Ink, and other stuff and we choose this path. Implementing a new command is super easy, battle-tested by Heroku and others in different operating systems, and it supports plugins for all the stuff we may need in the future. Thoughts?
I added an example implementation in the alt directory.

Yeah, I think Ink is cool too. In case it helps, the Apollo GraphQL folks have a draft PR to integrate Oclif and Ink. Although it's 2 years old 😄 https://github.com/apollographql/apollo-tooling/pull/1697

I did not have much time to look at all the changes and the CLI library, but I see you share only the advantages of the solution 😄
My question is:
Now I have just this https://github.com/asyncapi/cli/blob/master/src/help-message.tsx#L104-L143 and as a result I can build a very nice colorful help like 👇🏼 for any command

How would it work with oclif?

Everything in Oclif works with plugins, even the help: https://github.com/oclif/plugin-help. If we want to customize it, we just need to extend it or create our own plugin, and add color using something like Chalk.
And speaking about colors, I don't think what we currently have is better than this non-colored help. Just see how it looks for me:

"Commands" almost doesn't have contrast. You gotta be careful with colors, especially in the background. There's a way to make it look better with Chalk but Ink is not using Chalk properly, it seems. I had the same issue when coding the initial version of Studio. It's easy to fix (you have to call chalk.reset() first) but you can't do it with Ink.
And also something that was bothering me but didn't want to mention, is the fact that Ink is clearing up the terminal. That completely removes all the past output you had and you can't scroll up to see it. Didn't want to mention anything yet because that's probably something we can easily change with Ink.
Summarizing, if we want to create a great experience, we better rely on something battle-tested than rolling our own stuff. As I said, I love Ink but I think we're misusing it in this project. And nothing prevents us from integrating Oclif and Ink in the future.

I think we should resolve this is early, because later if we decide that we are going with oclif then more feature has to be ported. Here are some of my thoughts on the matter.

Custom Help
Oclif has options for custom help. So we can make colorful help strings, yeah but it is not consistent, maybe we choose the test with some other colors that stay consistent in different terminals. One problem with the custom help we have right now is that it is a lot of code and now again I have to change it because we are moving context command under config.
Command routing
I was checking out some multi command cli like nest-cli and they all use some kind of command parsing library like commander or such. We were building this on our own and it works fine but I guess we can push new features faster with oclif as we don't need to update the routing logic every time we add a new command.
The auto-documentation
Also, I think this could help.
And maybe we can use Ink though I don't know if it is a antipattern
We might still have ink components and then render them in the run function in oclif's command classes. Something like this -
import React from 'react';
import {Command, flags} from '@oclif/command'

import { IContext, loadContextFile } from '../../models/Context'

import {render} from 'ink'
import {list} from './components'

export default class ContextList extends Command {
  static description = 'list all saved contexts'

  static flags = {
    help: flags.help({char: 'h'}),
  }

  async run() {
    const {args, flags} = this.parse(ContextList)
    const ctx: IContext = loadContextFile()
    const response = Object.keys(ctx.store).map(c => ({ key: c, path: ctx.store[String(c)] }))
    render(<list response={response} />);
  }
}

I haven't tested this, it is just a thought.

Sorry but I don't have much time to look through the PR atm so need your help to answer these basic questions

what are we exactly fixing by using oclify? After reading comments I assume some of our code is a boilerplate that could be replaced with out-of-the-box stuff from oclify. Or is it just command routing that you do not like and that we can replace with oclify?

Ink but I think we're misusing it in this project Which part? how is this CLI different than others built with Ink?

regarding contrast issues with help text, they won't be solved by just introducing Oclif. We will have to write our own solution for that anyway. Did I get it right?
@Souvikns did you have a look at test part of the change? I think this is also important part to discuss, will it be easier to test commands or harder

I just want to make sure we do not want to switch just because there is just another cool kid on the block that we learned about.
I like oclify has CLI to do some code generation. Nice DX IMHO, but is it really a deciding factor? not really 😄

@Souvikns how much code from https://github.com/asyncapi/cli/pull/79/files you could get rid of when using oclify?

I believe we can reuse the whole thing, and just update the router and help generation part, other than that everything is reusable.

@Souvikns did you have a look at test part of the change? I think this is also important part to discuss, will it be easier to test commands or harder

Also, we have individual unit tests for the logic of the tasks, so I can tell that logic will not break. but oclif has some other way of testing. I don't know much about it. I will get back once I read about it more, maybe @fmvilas can talk about this more.
One more thing I would like to point out is that I and @magicmatatjahu were talking about improving the error handling that oclif has some interesting take on this.

I looked through the documentation and some examples and I like ocliff itself. The idea with commands as classes and static fields for flags etc is very similar to https://github.com/adonisjs/ace I think ocliff is an older project and ace was based on it - I do not know this.
As for the documentation, it's a big plus, clear with examples, but I miss the tutorial on how to write plugins from scratch.  Apparently there is a command to create a plugin structure, but exactly how to write it?
As for DI, I think we'll still be able to use it, of course if we still want 😄
I myself have an indifferent opinion about oclif and ink. I leave the decision to those who actively contribute to cli (@Souvikns
@jotamusik) and the developers themselves should decide. Switching to it and doing a review for another tool, will not be a problem for me. However, the problem is PR https://github.com/asyncapi/cli/pull/79, because if we go with ocliff there is no point in doing a review for it.

I looked through the documentation and some examples and I like ocliff itself. The idea with commands as classes and static fields for flags etc is very similar to https://github.com/adonisjs/ace I think ocliff is an older project and ace was based on it - I do not know this.
As for the documentation, it's a big plus, clear with examples, but I miss the tutorial on how to write plugins from scratch.  Apparently there is a command to create a plugin structure, but exactly how to write it?
As for DI, I think we'll still be able to use it, of course if we still want 😄
I myself have an indifferent opinion about oclif and ink. I leave the decision to those who actively contribute to cli (@Souvikns
@jotamusik) and the developers themselves should decide. Switching to it and doing a review for another tool, will not be a problem for me. However, the problem is PR https://github.com/asyncapi/cli/pull/79, because if we go with ocliff there is no point in doing a review for it.

Note: I removed a duplicate comment from @magicmatatjahu.

I myself have an indifferent opinion about oclif and ink. I leave the decision to those who actively contribute to cli (@Souvikns
@jotamusik) and the developers themselves should decide. Switching to it and doing a review for another tool, will not be a problem for me. However, the problem is PR #79, because if we go with ocliff there is no point in doing a review for it.

My vote goes to oclif, as we can port most of the code over to oclif, I think it will not take that much time.

@Souvikns thanks for looking into this 🙇🏼
I share @magicmatatjahu view and for me most important is you opinion and @jotamusik
Let us just give @jotamusik time until the end of the week to at least say folks wait, I need more time on review and then we can go forward.

I will take a look today! Thanks for waiting! 🤗

I don't see any problem, but I would like to make enphasis that the first structure of the cli, were thought in order to make changes like this easy.
So, keeping the hexagonal architecture of the project, and using Ink or oclif only as a view layer or command router, it should be achievable. But again, we need to make an effort on keep things separately, we need to segregate the view part of the cli from it's logic in order to make this change easy. 😝
I think we can do it. About the testing part of the ecuation, even if the test utils that comes with oclif don't match so well, on unit tests, we can tests the classes isolated, at the end, they are just classes with it's constructor so we can create instances in order to tests them.
I think that oclif it's a good option to make those people not confortable with react or frontend in general, feel more capable of doing things. So by my side.... Why not?? xD

For me Ink is not a problem, but if this makes easy the way to introduce commands and help people to feel more comfortable in the project, I don't have any problem. I don't have an opinion, the project was started with Ink, it wasn't a business requirement.
I see this, as a chance to make a clean start (obviously recycling some code base), and be sure that we are on the same page 😋

So how should we proceed?

@Souvikns I think this is a priority now before other things are added. Only thing that makes me think is https://github.com/asyncapi/cli/pull/79. I guess we should merge it first, right?

@Souvikns I think this is a priority now before other things are added. Only thing that makes me think is #79. I guess we should merge it first, right?

I think we shouldn't merge #79 but merge the changes from branch https://github.com/asyncapi/cli/tree/context-patch where the context service is fixed, in #79 I was updating the command routes which is mostly ink logic and which is not needed as we are going with oclif.
I had created a clean oclif install in my forked branch, but I think doing this we have to add all the previous code and it would take time, rather we add oclif in the existing codebase and made the necessary changes.

open to suggestions.

we add oclif in the existing codebase and made the necessary changes.

👍🏼
Looks like you know better what are the next steps. Go ahead 🚀

@derberg I think this can be closed. @Souvikns I didn't code these tests myself, they're generated automatically by Oclif when you use their CLI: https://oclif.io/docs/generator_commands.


bash-completion: 2.10 -> 2.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/scop/bash-completion/releases.
meta.description for bash-completion is: "Programmable completion for the bash shell"
meta.homepage for bash-completion is: "https://github.com/scop/bash-completion"
meta.changelog for bash-completion is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.11 with grep in /nix/store/b2y7qdcgw1v8r12gsza12494a940yfr6-bash-completion-2.11

directory tree listing: https://gist.github.com/6234caeed10c2d1b852ea30b42dbebd5

du listing: https://gist.github.com/3a89ec506ef1c03cb984a60cda8424d9

Rebuild report (if merged into master) (click to expand)

13585 total rebuild path(s)

4660 package rebuild(s)

4641 x86_64-linux rebuild(s)
4116 i686-linux rebuild(s)
821 x86_64-darwin rebuild(s)
4007 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
AusweisApp2
DisnixWebService
EmptyEpsilon
MIDIVisualizer
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL_Pango
SDL_gfx
SDL_gpu
SDL_image
SDL_mixer
SDL_net
SDL_sound
SDL_stretch
SDL_ttf
Sylk
_1password-gui
_20kly
_90secondportraits
abbaye-des-morts
abcde
abiword
acoustidFingerprinter
adapta-gtk-theme
adementary-theme
adom
adoptopenjdk-icedtea-web
adwaita-qt
aegisub
aerc
aesop
afew
agda
agdaPackages.agda
agdaPackages.agda-categories
agdaPackages.agda-prelude
agdaPackages.cubical
agdaPackages.generic
agdaPackages.iowa-stdlib
agdaPackages.standard-library
agenda
agg
ahoviewer
airstrike
airtame

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b2y7qdcgw1v8r12gsza12494a940yfr6-bash-completion-2.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bash-completion https://github.com/r-ryantm/nixpkgs/archive/59e213b70ecb936de8640da0d6a2e329613c4f2d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b2y7qdcgw1v8r12gsza12494a940yfr6-bash-completion-2.11
ls -la /nix/store/b2y7qdcgw1v8r12gsza12494a940yfr6-bash-completion-2.11/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @peti @xfix for testing.

Seems to work, and this time there weren't changes to pkg-config.


Jupyter Notebook Activity Top Commit Button Click to TypeError

The Commit Button on top of the Run button, click will produce:

It seems like fixed already


don't use makefile :)

would anyone be offended if i moved the stuff in makefile into the npm scripts?

i prefer no makefile for open source projects just so we have the lowest barrier to contribution possible. i always use makefiles in my personal projects though...


bug: IntegerSchema returns null for negative values for some locales

NumberFormat.getInstance().parse(Integer.toString(-1)) always throws exception in the following locales: ar· ·ckb· ·he· ·ks· ·pa_Arab· ·ur· ·fa· ·ps· ·uz_Arab· ·eo· ·et· ·fi· ·fo· ·gsw· ·ksh· ·lt· ·nb· ·nn· ·rm· ·se· ·sv· (see https://bugs.openjdk.java.net/browse/JDK-8189097)
This means that schemas with negative enum values will replace these with null if swagger parser is used on a computer with one of the special locales, making development hard for e.g. Norwegian or Finnish developers.
I've created a small pull request which fixes the problem at #4178

I support that this needs to be fixed asap! Thank you @jhannes !


Request: Retain Prompt

Awesome stuff. It would be nice if Ask AI or Ask with Context retained the prompt and not just the result - helpful when I go back to remember what I asked for and why I have the block of text.
Example output of /ask How do I jumpstart a car?

How do I jumpstart a car?

Turn off the ignition and remove the key from the car.
Connect the positive terminal of the battery to the red jumper cable.
Connect the other end of the jumper cable to the other red battery terminal on the other car.
[et cetera]

Closed with  #d136b85


Readme Update for FSDP

Updating Readme to  indicate flash attention support for LLama2 70b with FSDP. This improves performance as well as memory footprint
What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@regisss please review this readme change and merge this change when we transition to Synapse 1.16.0. We have tested this change on G2 with Synapse 1.16.0, this gives a small boost in performance.

@regisss This is for 1.16; it does not work properly for 1.15

@regisss Can we merge this now?


pacaur emits errors when no xdg config

This doesn't seem to be causing any problems, but on my first run pacaur included this error:
/home/nick/code/pacaur/pacaur: line 56: /etc/xdg/pacaur/config: No such file or directory.
Is this a required file?
If not, it should be as simple as changing line 56 to be:
[[ -f "$configdir/config" ]] && source "$configdir/config"

This is the default, system wide config file which is installed by default when installed with the PKGBUILD.
It looks like you cloned the repo and execute pacaur from it. Any reason not to install it?

Only that I'm still learning arch and haven't used the AUR much. What is the recommended way to install?

Welcome to Arch then!
You'll need to familiarize yourself with the manual installation process with makepkg first. This is important as you might run into issues in your Arch career that require manual intervention. And because it's always better to understand what pacaur is doing rather than using it blindly.
In a nutshell, download the tarball or cower, extract and run makepkg to compile, install dependencies and install cower system wide. Repeat the process with pacaur's tarball, after which you'll be able to run pacaur from the regular command line to install other AUR packages.
I'd also strongly advise to have a look at pacman and makepkg man page, as well as pacaur man page. Hope you enjoy your Arch journey!

@rmarquis : Just went through with this, thanks for the instructions!


Switch from npmcdn to unpkg

npmcdn has switched to unpkg (https://twitter.com/mjackson/status/770424625754939394), so I've updated the homepage to use the new URL.

Merge conflicts here, and there are bad merge commits included as well. New PR incoming.


DevTools: Add Movement Flags DevTools Plugin.

Background: I created this tool to assist my Hallowed Sepulchre plugin (in progress) and I thought it might be useful to others.
This plugin highlights the tile the player is currently hovering over and displays the movement flags above it. The movement flags can be useful for pathfinding and other debugging purposes.

@Nightfirecat FYI, I addressed your feedback on this PR. I marked all all conversations as resolved and pushed the appropriate changes - I'm not sure why it still says "Changes Requested".


[main_chain] ready joint doesn't trigger it's children ready

when a joint is saved, it should trigger all it's children ready along the path.

it's possible that we need a global timely re-check to execute the function


GeneratedPluginRegistrant is different on android and ios

I'm using custom .flutter-plugins-mobile since I have desktop specific modules which obviously fail to build on mobile
settings.gradle
- def pluginsFile = new File(flutterProjectRoot.toFile(), '.flutter-plugins')
+ def pluginsFile = new File(flutterProjectRoot.toFile(), '.flutter-plugins-mobile')

this works as expected on android
Podfile
-  plugin_pods = parse_KV_file('../.flutter-plugins')
+  plugin_pods = parse_KV_file('../.flutter-plugins-mobile')

this don't.
GeneratedPluginRegistrant.m contains imports of modules not included in .flutter-plugins-mobile
flutter --version
Flutter 1.9.6-pre.6 • channel unknown • unknown source
Framework • revision ba78486ecb (2 days ago) • 2019-08-26 20:52:41 +0300
Engine • revision 00b72a1475
Tools • Dart 2.5.0

Channel is master, just with this #39195 diff (waiting to be merged), so it has nothing to do with plugin registrant generation :)

.symlinks/plugins contains valid plugins though


Is there a way to run a task once the same day and every consequent day at the specified time.

Is there a way to run a task once the same day and every consequent day at the specified time? I have been struggling to make this library work for my use case with not luck. I want to schedule a job to run everyday at 8pm. How should I construct my JobRequest.Builder object for this usecase? I found the example in the FAQ "How can I run a job at a specific time once a day?" concussing. I would hight appreciate any suggestions :)
Currently, my code looks like that:
   `Calendar calendar = Calendar.getInstance();
    calendar.set(Calendar.HOUR_OF_DAY, 20);
    calendar.set(Calendar.MINUTE, 0);

    int hour = calendar.get(Calendar.HOUR_OF_DAY);
    int minute = calendar.get(Calendar.MINUTE);

    long startMs = TimeUnit.MINUTES.toMillis(60 - minute) + TimeUnit.HOURS.toMillis((24 - hour) % 24);
    long endMs = startMs + TimeUnit.MINUTES.toMillis(5);

    int jobId = new JobRequest.Builder(TAG)
            .setExecutionWindow(startMs, endMs)
            .setPersisted(true)
            .setUpdateCurrent(updateCurrent)
            .build()
            .schedule();`

The console output:
jobInfo success, request{id=11, tag=job_demo_tag}, start 05:00:00, end 05:05:00, reschedule count 0

The output tells me, that you've scheduled the job in 5 hours. That looks good to me. I'm sorry, but what you're asking is unrelated to the library itself and should be asked elsewhere, e.g. at Stackoverflow.

Thank you for your comment. If the question is out of the scope of the library that is fine. I will close the ticket now. Thanks! :)


Use Kotlin vararg to combine solo and batch APIs in FhirEngine and Database

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straighforward changes).
Fixes #404
Description
Use Kotlin vararg to combine solo and batch APIs in FhirEngine and Database.
Alternative(s) considered
NA
Type
Code health
Checklist

[x] I have read and acknowledge the Code of conduct
[x] I have read How to Contribute
[x] I have read the Developer's guide
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally
[x] I have built and run the reference app(s) to verify my change fixes the issue and/or does not break the reference app(s)

Thanks @deepankarb! Sorry I had auto merge on. Will I corporate the proposed change in a follow-up.


Fix paths for installed package

This PR fixes the README and adds a new function examples_dir to account for the fact that KROME is now a registered package.

Pull Request Test Coverage Report for Build 574527831

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 88.889%

Totals

Change from base Build 572021054:
1.4%

Covered Lines:
8

Relevant Lines:
9

💛  - Coveralls

Pull Request Test Coverage Report for Build 574527831

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 88.889%

Totals

Change from base Build 572021054:
1.4%

Covered Lines:
8

Relevant Lines:
9

💛  - Coveralls

@Cczernik @mweislev It would be great if you can both have a look at this PR and make sure you understand and agree with what is being changed (and of course please check for errors ;-)).

Pull Request Test Coverage Report for Build 574558214
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 88.889%

Totals

Change from base Build 572021054:
1.4%

Covered Lines:
8

Relevant Lines:
9

💛  - Coveralls


Writing problem

Hi,
I'm using your library to communicate with influx. I met a problem when I'm writing data : all the data is not inserted like excepted. Here's the scenario : I have two list of Points, each have the same size of 742400. I'm doing this in a sequential way : I insert the points from the first list then the points from the second. For the first list, no problem all the points are inserted but for the second, only 74240 points are inserted. Some points from the lists share the same timestamp but using a tag and not field, the points are not overwritten. Here the way to build the list of points and the way to add into influx :
def map2points
      (
        m : scala.collection.mutable.Map[String, List[Double]], // matrix of points
        channels : Array[String],
        awsKey : String,
        startime : Long,
        frequency : Double
      ) : List[Point] = {
      m.foldLeft(List[Point]()) { case (acc, (key, values)) =>
        val timed_points : List[Point] = values.zipWithIndex map { case (v, i) =>
          val ts = startime + (math round ((10e6 / frequency) * i)).toLong
          Point("titi",ts)
            .addTag("channel",key)
            .addField("value", v)
        }
        timed_points ++ acc
      }
    }
  }

val t4 = System.currentTimeMillis
assert(points.size == 742400)
Logger.info("Insertion status =  " + Await.result(database.bulkWrite(points, precision = Precision.MICROSECONDS), 10.seconds))
val t5 = System.currentTimeMillis

Which I find weird, the boolean returned by the bulkWrite function is true even all the points are not inserted. Do you have an idea why all the points are not inserted ? Maybe I use the library in a wrong way ?

I fixed my error,  there are some points with the same timestamp and the same tag. It's the reason why some points were not inserted into influx.

Glad you could solve this!


ng-leave removes the item when transition of a child element is finished

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] other (Please do not submit support requests here (see above))

Current behavior:

ng-leave removes item too early, when some of the child elements finishes its transition
Expected / new behavior:

Items are not removed before ng-leave transition is finished.
Minimal reproduction of the problem with instructions:

Demo: https://plnkr.co/edit/pwDJA6s6ZJvfeJKiRjWk?p=preview
In the first list items are removed only after child transition is finished, so it works as expected.
In the second list items are removed a bit earlier so that child transition ends before ng-leave transition which leads to termination of ng-leave transition and removes the item.
Here is a workaround for this particular problem: https://plnkr.co/edit/0Xwe0JWfx5wmVRfDJi2i?p=preview
It cancels transition of child element, but it have to work without such hacks.
AngularJS version: 1.6.6

Browser: [Chromium 60 | Chrome 60 | Firefox 55]

Anything else:

I'm not sure how it works exactly, but transition time should probably be determined only on the item ng-leave is applied on, not anything else.

Hi,
thanks for the report.
I think the problem is that our transitionend event listener does not work correctly when the event is coming from a child element. (https://github.com/angular/angular.js/blob/3651e42e49ded7d410fd1cbd46f717056000afd4/src/ngAnimate/animateCss.js#L804-L829) I think we should simply ignore all of the event in this case. I'll work on a test case and PR.

Here's a plunker with a fix: https://plnkr.co/edit/nKU8lkiwVI6kphL99G6J?p=preview
And here's the PR https://github.com/angular/angular.js/pull/16214

Looks good, thank you.

Fix will be in the 1.6.7 release (commit https://github.com/angular/angular.js/commit/1391e99c7f73795180b792af21ad4402f96e225d)


[BUG] Issue getting annotations with the sdk

Running
dict_task = my_project.get_task(123)
print(dict_task)

gives me the following dict. Notice that the value of annotations_results is a string. It should be a list of dicts. I cant easily convert it because the keys inside the dict there don't have quotes. I think something is wrong on the sdk end. If I am doing something wrong here please give me a hint on how to proceed.
{
   "id":123,
   "predictions":[

   ],
   "annotations":[
      {
         "id":23,
         "created_username":" email, 1",
         "created_ago":"50\\xa0minutes",
         "completed_by":{
            "id":1,
            "first_name":"",
            "last_name":"",
            "avatar":"None",
            "email":"email",
            "initials":"st"
         },
         "result":[
            {
               "id":"Xm01aKoKq_",
               "type":"rectanglelabels",
               "value":{
                  "x":24.429657794676807,
                  "y":26.61596958174905,
                  "width":14.068441064638783,
                  "height":17.49049429657795,
                  "rotation":0,
                  "rectanglelabels":[
                     "ball"
                  ]
               },
               "origin":"manual",
               "to_name":"image",
               "from_name":"label",
               "image_rotation":0,
               "original_width":640,
               "original_height":480
            }
         ],
         "was_cancelled":false,
         "ground_truth":false,
         "created_at":"2024-03-12T19:46:33.835626Z",
         "updated_at":"2024-03-12T19:46:33.835636Z",
         "draft_created_at":"None",
         "lead_time":5.427,
         "import_id":"None",
         "last_action":"None",
         "task":1490,
         "project":21,
         "updated_by":1,
         "parent_prediction":"None",
         "parent_annotation":"None",
         "last_created_by":"None"
      }
   ],
   "drafts":[

   ],
   "annotators":[
      1
   ],
   "inner_id":2,
   "cancelled_annotations":0,
   "total_annotations":1,
   "total_predictions":0,
   "completed_at":"2024-03-12T19:46:33.835626Z",
   "annotations_results":"[{id:Xm01aKoKq_, type:rectanglelabels, value:{x:24.43, y:26.62, width:14.07, height:17.49, rotation:0, rectanglelabels:[ball]}, origin:manual, to_name:image, from_name:label, image_rotation:0, original_width:640, original_height:480}]",
   "predictions_results":"",
   "predictions_score":"None",
   "file_upload":"None",
   "storage_filename":"0005584.png",
   "annotations_ids":"23",
   "predictions_model_versions":"",
   "avg_lead_time":5.427,
   "draft_exists":false,
   "updated_by":[
      {
         "user_id":1
      }
   ],
   "data":{
      "image":"<myurl>/tasks/123/presign/?fileuri=czM6Ly9kZ3Bzd2dhemdkandhbXNsdGZhdXp1LzAwMDU1ODQucG5n"
   },
   "meta":{

   },
   "created_at":"2024-03-12T19:46:04.287715Z",
   "updated_at":"2024-03-12T19:46:33.927086Z",
   "is_labeled":true,
   "overlap":1,
   "comment_count":0,
   "unresolved_comment_count":0,
   "last_comment_updated_at":"None",
   "project":21,
   "comment_authors":[

   ]
}

same here, but I think "predictions_results" and "annotations_results" are two duplicated keys, am I right? @makseq
Because we can still get the final result from "predictions" and "annotations"


Chat warnings should say they are automatic, and possibly advertise tf2bd

A clear and concise description of what the problem is.

The program will function better with more people using it, and aware of its existence even if they are not using it. Some players are also under the impression the warnings are just binds or are fake to votekick randoms (especially when its a human player being kicked)

Describe the solution you'd like

Have an option to say something along the lines of "| Message was automatically sent by tf2 bot detector https://botdetector.tf" to the end of every automatic message sent, should be toggleable. Maybe not have any advertisement and just say its an automatic message?

Describe alternatives you've considered

I have not thought of any alternatives that are not annoying.

Additional context

No additional context needed/

this will probably be irrelevant when #70 is resolved but it could still be relevant as far as a default is concerned


implement TransactionType enum to replace hardcoded byte values

This PR implements an in-code TODO by adding a TransactionType enum to replace the hardcoded byte values.
The TransactionType enum constant names are based off existing implementations:
https://github.com/ArkEcosystem/ark-ts/blob/master/src/model/Transaction.ts
https://github.com/ArkEcosystem/ark-go/blob/master/core/transaction.go
It uses a UPPERCASE_UNDERSCORE instead of UPPERCASEUNDERSCORE naming convention since that is more in line with the Kotlin language style guide

Great work!


HTML refuses to load with Engine is not defined 404 error

Godot version
3.5.2-stable
System information
Manjaro XCFE, Intel core i3 11 generation.
Issue description
When I test my html5 game on neocities, an error message appears.
Project runs fine on localhost.
caught ReferenceError: Engine is not defined
at (index):143:16
to load resource: the server responded with a status of 404 ()
This is the line of code that the error is coming from the console.
const GODOT_CONFIG = {"args":[],"canvasResizePolicy":2,"executable":"My html game","experimentalVK":false,"fileSizes":{"My html game.pck":5257072,"My html game.wasm":13793958},"focusCanvas":true,"gdnativeLibs":[]};
var engine = new Engine(GODOT_CONFIG);
Using the GLES 2 renderer.
Steps to reproduce
Opening site on chromium causes the error under the GLES 2 renderer.
On Firefox there's a forbidden page.
Using the GLES 3 renderer it causes a forbidden page on chromium.
Minimal reproduction project
N/A
Project is just a test picture with a sound on screen.

Closing per the above comment.


Webm player shows unknown address

After updating to the latest dashchan webm plugin, attempting to play a webm shows an error: "unknown address".

Try to install test version. Open updating window, click on Dashchan, choose "Test" and install it. Does this solve a problem?
What device do you have?

Test version still shows the same error. I am running on an LG V10 (T-Mobile, USA), stock rom.

Can you make a log like it told here (in the bottom)?


feat(webpack): write debug index for webpack build

BREAKING CHANGE: This writes a debug index designed for builds using webpack and closure-webpack-plugin. Projects must be updated to use webpack in the build, and index options must be updated to include a debugJs path to the debug bundle generated by webpack.

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


wip: add support for mv cols with lucene index

wip PR for adding support for MV cols with lucene index
addresses: https://github.com/apache/pinot/issues/10975

Codecov Report

Merging #11000 (0205485) into master (3c92b32) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master   #11000     +/-   ##
=========================================
  Coverage    0.11%    0.11%
=========================================
  Files        2189     2137     -52
  Lines      117997   115502   -2495
  Branches    17852    17566    -286
=========================================
  Hits          137      137
+ Misses     117840   115345   -2495
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
?

integration1temurin17
?

integration1temurin20
?

integration2temurin11
?

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
?

unittests2temurin11
?

unittests2temurin17
?

unittests2temurin20
0.11% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ime/impl/invertedindex/NativeMutableTextIndex.java
0.00% <0.00%> (ø)

...me/impl/invertedindex/RealtimeLuceneTextIndex.java
0.00% <0.00%> (ø)

...ot/segment/spi/index/mutable/MutableTextIndex.java
0.00% <0.00%> (ø)

... and 131 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update notification banner and global nav

Summary
This PR adds the 9.0 announce blog to the notification banner, and updates the global nav to align with mm.com.
@cwarnermm – Feel free to adjust the footer links and I'll mirror the changes on mm.com. Will add more reviewers once we're zipped up.
Thank you!

@emdecr - Let's apply the 2 header updates proposed via x:

Let's update the Academy link to point to: https://academy.mattermost.com/
Let's update the Release Notes link to: https://docs.mattermost.com/guides/changelogs.html

And just to confirm, the dev docs site footer is far simpler than the docs footer intentionally?

@cwarnermm Yep – I don't think there's ever been a footer mirror (of docs/mm.com) on this site since I've been here.

@nat-gunner For review - nav changes for 9.0 - TY!

@emdecr - phew! For a moment I thought I was mis-remembering one! :)


Best practice for updating dependent state across different branches of the state tree?

In the Reducer docs it says:
Sometimes state fields depend on one another and more consideration is required, but in our case we can easily split updating todos into a separate function..

I'd like to know how to handle that specific use case. To give an example, say I have a form with multiple data fields. I have another component elsewhere that should react to changes in form, e.g change state based on whether the form data is valid, or compute values from different inputs to the form and display them.
While I believe I can have different reducers (which handle different slices of the state tree) listen to the same action and update themselves, the "reactive" state would not have access to the other branches of the state tree that it needs in order to compute itself.
One solution I've thought of is to have the "reacting" process happen by using subscribe to listen to changes in the state tree, compute whether or not a relevant change was made, then dispatch a new action to update the dependent fields. However, this publishing blast might have to become very generic, so that all reducers that care about it will be able to use the payload it comes with.
I'm new to Redux, so I'm not sure if there is an adopted pattern for this type of thing. I'd appreciate any advice or pointers in the right direction. Thanks.

Sorry, the other option I've discovered is using a custom rootReducer. Technically, this reducer wouldn't have to be at the root; it could just be the Lowest Common Ancestor of the parts of the state tree that are dependent on each other.

If the data can be computed from a “lesser” state, don't hold it in the state. Use memoized selectors as described in Computing Derived Data.
If it cannot, indeed, use a single reducer that may (if desired) pass additional parameters to the reducers or use their results:
function something(state = {}, action) {
  let a = a(state.a, action);
  let b = b(state.b, action, a); // note: b depends on a for computation
  return { a, b };
}

Thanks @gaearon for that snippet. I've quickly ran into this issue myself when attempting to port a widget over to redux and have spent sometime trying to find a community sanctioned solution. Perhaps this is something that can be more prominent within the documentation as I'd imagine it's rather common to have dependent state.
It also appears that it would be trivial to pass the entire state tree as a optional third parameter within the innards of the  combineReducers method. Doing so would facilitate this very issue though I'm not experienced enough with redux to have any sense as to whether it would be  a good or bad idea. Thoughts?

It's got its own section in the docs, so I think it's pretty prominent personally. :smile:
You don't have to use combineReducers if you don't want to. It's a useful utility, but not a requirement. Perhaps redux-actions is more your style?

If the data can be computed from a “lesser” state, don't hold it in the state.

It's got its own section in the docs, so I think it's pretty prominent personally.

Ok, I think it finally clicked for me. Thanks!

"If the data can be computed from a “lesser” state, don't hold it in the state."
What if the data can only be computed from a "lesser" state combined with the payload of an action?

When you need different parts of the state tree to resolve the effects of single action that cannot be handled in a mutually exclusive way in each branch, use reduce-reducers to combine the reducer produced by combineReducer with your cross-cutting reducer:
export default reduceReducers(
  combineReducers({
    router: routerReducer,
    customers,
    stats,
    dates,
    filters,
    ui
  }),
  // cross-cutting concerns because here `state` is the whole state tree
  (state, action) => {
    switch (action.type) {
     const customers = state.customers;
     const filters = state.filters;
     // ... do stuff
    }
  }
);

@neverfox Thank you for that! exactly what I was looking. Do you know any other way of either accessing the root state from the combined reducer or re-architecturing something?

@imton
For your particular example I'm not sure why don't want to let different reducers to handle the same actions. That's pretty much the point of using Redux. Please see https://gist.github.com/imton/cf6f40578524ddd085dd#gistcomment-1656424.
I don't think “cross-cutting” reducers are generally a good idea. They break encapsulation of individual reducers. It's hard to change internal state shape because some other code outside reducers might rely on it.
On the opposite, we recommend not relying on the state shape anywhere except reducers themselves. Even components can avoid relying on the state shape if you export "selectors" (functions that query the state) from the same files as reducers. Check out shopping-cart example in the repo for this approach.

To be clear, I was only suggesting the cross-cutting reducer for cases that aren't mutually exclusive, viz. cannot just be handled by separate reducers responding to the same action. For example, an action comes in and it needs to take some data from one branch of the tree (normally handled by reducer A) and some data from another (normally handled by reducer B) and derive some new state data from them both (perhaps to be stored in another state branch C). If there's a way to do this short of refactoring the state shape (which isn't always feasible or desirable), then I'm certainly open to suggestions, because that kind of situation comes up a lot.

For computing derived data we suggest using selectors rather than storing it in the state tree.
http://redux.js.org/docs/recipes/ComputingDerivedData.html

Which is great and useful, until it needs to be part of state.

What do you mean by "needs"? Can you describe a specific scenario you're referring to?

This thread has been helpful, but I'm still a tiny bit uncertain. If I have a column of checkboxes, and a list of results based on which boxes are checked. When a user checks a box I want to save that in selectedFilters (to display later) but I also want to filter the results based on the new list of selected filters.
// filters oriented reducer
case FILTER_SELECTED:
    return newArrayOfSelectedFilters(action.filter);

// results oriented reducer
case FILTER_SELECTED:
    return filterResultsBasedOnSelectedFilters(>>>new_list_of_selected_filters<<<);

There is enough data to perform the filtering in isolation by passing in the old filters with the new filter, but then I would be merging the filters in two different places.
Which of the techniques previously described here best fits this scenario?
Thanks!

@gaearon, curious to hear your thoughts on the following scenario...
As you enter chars in a password field, we run the following validation rules against the password state property:

Are there 3 or more consecutive characters?
Is there a space in the password?
Is the username part of the password?

If any of the above is true, we show a page level error with a corresponding specific page level error message and, depending on which error, we may show a field level error message.
So I'll have 3 reducers, 1 each for username and password, to simply hold the strings values, and 1 for notification, which handles the page level error notification message and type:
// reducers/notifcation.js
import { ENTER_PASSWORD } from "../../actions/CreateAccount/types";
import strings from "../../../../example/CreateAccount/strings_EN";

const DEFAULT_STATE = {
  type: '',
  message: ''
};

export default (state = DEFAULT_STATE, action) => {
  const { value: password, type } = action;

  if (type === ENTER_PASSWORD) {
    const errors = strings.errors.password;
    let message;

    if (password.length <= 3) {
      message = errors.tooShort;
    } else if (password.indexOf(username) !== -1) {
      message = errors.containsUsername;
    } else if (password.indexOf(' ') !== -1) {
      message = errors.containsSpace;
    }

    if (message) {
      return {
        message,
        type: 'error'
      };
    }
  }
  return DEFAULT_STATE;
};

So in this case, the notification reducer needs to know about the username and password. We can access the password since we're concerned with the ENTER_PASSWORD action type which includes it, but, as it's currently organized, I wouldn't get username and password together. In theory I should also be checking for a ENTER_USERNAME action type to make sure that if they've already entered a password and then return to the username field and modify the username, then I check to make sure that the password does not contain the updated username... But we can skip that for now.
Thoughts?
One solution would be to group username and password together as credentials, and merge our ENTER_PASSWORD and ENTER_USERNAME action types into a single ENTER_CREDENTIALS dispatch, but for shits and giggles, let's say that that's not feasible in this situation.

Please take a look at redux-form and how it handles scenarios like this. In general, it's better to ask questions on StackOverflow than here. I'm currently unable to give long answers because I'm busy.

I created https://github.com/ryo33/combine-section-reducers.
It solves this in a way like combineReducers' one.

Maybe know something about this? @gaearon
Thanks!

@gaearon The discussion with @neverfox stopped abruptly, but I think I know what he meant - I came across the same problem:
Let's say we have a root reducer composed using combineReducers with state branches: chat and ui. Inside of the chat-specific reducer we need to react to an action (e.g. received fresh msgs from server) in a way depending on a state from ui part (e.g. append the fresh msgs only if the end of the msgs list is in the viewport - that info is kept in the ui part ). We cannot acces state from ui branch inside the chat branch - therefore it's impossible to use a selector.
The first solution that came to my mind was to do the conditional part in a dedicated thunk and from that place dispatch one of two dedicated actions. This however introduces several additional creations and therefore quite badly obfuscates what's going on.
For this reason I find @neverfox's solution the cleanest one, although, as you said, it breaks encapsulation. Do you have other opinion/solution on this matter after stating the problem as I did above?

@jalooc : The Redux FAQ discusses this issue, at http://redux.js.org/docs/FAQ.html#reducers-share-state.
Basically, the main options are "pass more data in the action" or "write reducer logic that knows to grab from A and pass to B".  I definitely feel that @neverfox's approach is the best way to handle it if you opt for the reducer-centric approach.
I'm also in the middle of writing up a new set of docs on structuring reducers, over at #1784 .  One of the new pages specifically addresses this concept - "Beyond combineReducers".
I'd definitely be interested in further feedback on the draft doc page and this topic in general.

Whatever people say here. I highly suspect the problems people usually do face are only when they architect their state in a non ideal way. If there is a lot of dependency among your branches in the state tree it itself might be an indication of duplicated data and can use 'lesser' / 'leaner' state.  React+Redux platform is giving you immense power in your hands and highly deterministic UI updates. Those who haven't suffered the problems of weird UI updates and loops of 2 way bindings probably will not understand this. When there is a lot of power in your hands inherently means you can easily shoot yourself in the foot too which will be a nightmare and feel every one's pain too. Once you get the state architecture part right everything else will become easy. So basically you need to spend more time in state architecture but you can reap benefits all throughout after that.  Also I think it is highly suggested to use lean state, and usual recomputation and first see if you have performance issues. Very important. Only use the reselect approach if you see performance issues from recomputation (yes it can be applied incrementally, right @gaearon ?). I did take the approach and noticed that the recomputing did not affect at all which I was fearing will surely happen but it never did, on the other hand I am able to sort items at every key press and it feels like it is blazingly fast. People many a times tend to think too much about the steps of recomputation but please never forget today's average processors can perform hundreds and thousands of sorts in fraction of a second. True story.

Has anyone considered this approach? What are the pitfalls?
const combinedReducers = combineReducers({
  dog: dogReducer,
  cat: catReducer
})

const stateInjectedReducers = (state, action) => {
  return {
    ...state,
    frog : frogReducer(state.bar, action, state) // frogReducer depends on cat state
  }
}

export default reduceReducers(combinedReducers, stateInjectedReducers)

It's cheap and easy but appeals to me because it means I won't be having to rewrite stateInjectedReducers for any new reducers that need injecting with state from elsewhere.

@funwithtriangles : yup, perfectly good approach!  In fact, I talk about that in http://redux.js.org/docs/recipes/reducers/BeyondCombineReducers.html , and my blog post at http://blog.isquaredsoftware.com/2017/01/practical-redux-part-7-forms-editing-reducers/ .

@markerikson glad to know I wasn't doing anything too crazy! :) The irony is that after coming up with that approach I decided that my dog, cat and frog state slices were too intertwined to be separate reducers and merged them into one! 😛

Just curious is it bad practice to simply have multiple reducers respect the same action and then trigger their own respective changes in their own state trees? I also think its possible if you have to do this, it might be an indicator you have structured your state tree incorrectly but for purposes lets say you have two different states
const combinedReducers = combineReducers({
  a: aReducer,
  b: bReducer
})

And you wanted to trigger a state change in both state trees from one dispatch. Is it bad practice to simply have in both reducers respect the same action? Inevitably, the dispatch goes through the whole combinedReducers anyways and it ends up making the state change in both trees. The only issue is that you have to dig through and see if certain actions are trigger changes in different state trees (but we can use a naming convention to help handle that).

@augbog That's totally fine and is a common thing to do in Redux, but isn't really related to what is being described above. This issue is about reducers having access to the state from other branches of the state tree.

@augbog : that's absolutely an intended use case for Redux!  For more info, see my blog post The Tao of Redux, Part 1 - Implementation and Intent.

Another angle - Use a selector at the root of your state tree to derive the particular data you need by calling selectors from sub-branches of the state to get necessary data, then return the data shape you require:
const selector = state => {
    const x = someSelectorForA(state.a);
    const y = someSelectorForB(state.b);
    return compute(x,y);
}

Your reducers remain encapsulated, no race-conditions, and the selector is doing the grunt work.   Can lead to some nice recursive patterns.

Whenever I have been tempted to reach across branches of the state tree, it usually is when I should be using a selector. I try really hard to follow these principles:

State tree should not contain anything which is derived from anything else in the state tree.
Selectors should be used to compute derived data.

As far as forms are concerned, to me you have 2 things that belong in the store:

Validation rules
Data from user input (text, blur, other events)
Then you use a selector to compute whether #2 follows the rules defined in #1. There's no reason to reach across the state tree in a reducer.

I've sometimes thought, "Doesn't it seem like whether a form is valid or not should be reflected in the application state? It seems like a major thing to keep track of." But still, it violoates the principle that state should be the single source of truth. If there is a bug where validity is computed incorrectly, your state will be internally inconsistent. That should be impossible.
Selectors are perfectly good places to store derived data, even if the results are major. Use a memoized selector as @gaearon suggested, because the computed state may have many interested subscribers.
And if your reducer needs the contextual information of derived data in order to interpret an action correctly, you can just include that with the action when you dispatch it.

An alternative to this problem, is using redux-thunk. The solution is to use intermediate actions, to fire more context-aware actions based on the current state.
function incrementIfOdd() {
  return (dispatch, getState) => {
    const { counter } = getState();

    if (counter % 2 === 0) {
      return;
    }

    dispatch(increment());
  };
}

Using this solution, both actions and reducers stay dumb, and the logic moves to an intermediate layer which does the extra checks and deductions based on user interaction and current state.

@funwithtriangles Your solution is very elegant but frog isn't part of your state shape, so combinereducer is complaining about an unknown key after having it initialized.
I personnally ended up doing something hacky (I'm using immutable state) :
const combinedReducers = combineReducers({
  dog: dogReducer,
  cat: catReducer,
  frog: state => state || defaultFrogState
})

const stateInjectedReducers = (state, action) => {
  return state.set('frog', state.get('frog'), action, state);
}

export default reduceReducers(combinedReducers, stateInjectedReducers)

Do you have a better approach ?

It's got its own section in the docs, so I think it's pretty prominent personally.
The link with this quote is broken, but I believe it refers to this: https://redux.js.org/docs/recipes/ComputingDerivedData.html

Yep, that's where it's moved to.

If you don't mind writing more boilerplate to link dependent state you can try:
https://github.com/mileschristian/redux-named-reducers


Single VM: Ensure no ciao network artifacts are left behind

Ensure that no ciao network artifacts are left behind when all instances have been deleted.
Note: Similar logic needs to be in place for storage other artifacts.
This will help catch regressions of the type https://github.com/01org/ciao/issues/768
Signed-off-by: Manohar Castelino<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 65.862% when pulling c6f383cd1e6b0c829ef2abaf9f3fc7d41995a0c7 on mcastelino:single_vm_tls_fix into 7b087d20eae80de66b12af19376e4d79a2060845 on 01org:master.

One other issue with these checks is that it prevents us from moving verify.sh into the BAT tests as these checks will only work on SingleVM.  I'm not saying that we shouldn't merge this, but I'm just pointing out that we can no longer make verify.sh a BAT test unless we can detect inside the BAT test that we're running on SingleVM.  Any idea how best to do this?

@markdryan all review comments addressed. Also verify.sh is also re-entrant w.r.t events. Hence the event clearing.

Coverage decreased (-0.03%) to 65.818% when pulling 56e97dc4c68a6dc833cdbde2a4a643187f75e9d5 on mcastelino:single_vm_tls_fix into f7770fc714c1d583b5f512bf6de6083d402364aa on 01org:master.

BTW, I entered a new bug #792 to cover the fact that we can't actually tell what an event is when it arrives and to which instance it pertains.  Knowing this information would make the use of the event log more secure.  I doubt this will get fixed in time for this PR though.  We can update the verify.sh at a later stage.

@markdryan fixed the retry issue.

Coverage decreased (-0.005%) to 65.928% when pulling 9b27831335a45d132a2b8f962ae43e15b4c493f1 on mcastelino:single_vm_tls_fix into 3c0cf66e6c5611c82d7f6c93694d02b94641f0c5 on 01org:master.


@howardjohn what happened - did it merge and cause conflicts somewhere else?  or did this PR not actually merge?

it merged to master but could not he automatically backportdd to the 1.4
branch so we will have to manually cherrypick
On Wed, Oct 16, 2019, 7:57 PM Gregory Hanson<EMAIL_ADDRESS>wrote:

@howardjohn https://github.com/howardjohn what happened - did it merge
and cause conflicts somewhere else? or did this PR not actually merge?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/17621?email_source=notifications&email_token=AAEYGXIIQUNNOFZ33TA4SPLQO7IDPA5CNFSM4I5TIU52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBOSLIQ#issuecomment-542975394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXK5KT543RB23OVCKFDQO7IDPANCNFSM4I5TIU5Q
.

I'm not sure where the merge conflict is coming from:
$ git checkout -b cherrypick-17621 upstream/release-1.4
Branch cherrypick-17621 set up to track remote branch release-1.4 from upstream.
Switched to a new branch 'cherrypick-17621'
$ git cherry-pick 9cdfdd80f9167ee8862bde016d98b8cbfded6539
[cherrypick-17621 3c00e0e94] Implement auto mTLS via Envoy transport_socket_match. (#17621)
 Date: Wed Oct 16 22:48:15 2019 -0400
 19 files changed, 472 insertions(+), 226 deletions(-)
 create mode 100644 tests/integration/security/mtls/main_test.go
 create mode 100644 tests/integration/security/mtls/strict_test.go
 rename tests/integration/security/{ => mtls}/testdata/global-mtls-on-no-dr.yaml (100%)
$ make build
Building with your local toolchain.
mkdir -p /Users/gihanson/go/out/logs
STATIC=0 GOOS=darwin GOARCH=amd64 LDFLAGS='-extldflags -static -s -w' common/scripts/gobuild.sh /Users/gihanson/go/out/darwin_amd64/release/ ./istioctl/cmd/istioctl ./pilot/cmd/pilot-discovery ./pilot/cmd/pilot-agent ./sidecar-injector/cmd/sidecar-injector ./mixer/cmd/mixs ./mixer/cmd/mixc ./mixer/tools/mixgen ./galley/cmd/galley ./security/cmd/node_agent ./security/cmd/node_agent_k8s ./security/cmd/istio_ca ./security/tools/sdsclient ./pkg/test/echo/cmd/client ./pkg/test/echo/cmd/server ./mixer/test/policybackend ./tools/hyperistio ./tools/istio-iptables

real	0m23.068s
user	1m49.006s
sys	0m25.209s

I dont get any merge errors and builds fine


Add fei.txt

Add fei.txt

@Isaac25silva I am sorry for a delay with processing your request.
Pull request merged. Thank you!


Inspector shorthand 'all' is unable to use unless it is called directly like 'Matchers.all'

I tried using inspector shorthand to test list member type as below.
result shouldBe a [List[_]]
all (result) shouldBe a [Product]

Noted that Intellij IDEA traced this 'all' source to MustMatchers.all
When being tested, the letter line threw the following
ResultOfCollectedAny(AllCollected, List(Product(0,Fish Oil), Product(1,Butterfly))) was not an instance of models.Product, but an instance of org.scalatest.MustMatchers$ResultOfCollectedAny (ProductSpec.scala:25)

which is not presented if I call these instead
result shouldBe a [List[_]]
Matchers.all (result) shouldBe a [Product]

Is this a bug? Or these inspector shorthands are supposed to be used like the letter example? I use scalatestplus-play v.1.5.1

Found the culprit. Since I previously used org.scalatestplus.play.PlaySpec which extends MustMatchers by default, calling all from MustMatchers crashed my specs. But Matchers.all don't
I found this bug along with 'mustBe' bug which couldn't checking type like
result mustBe a [List[_]]

since this line will throw similar exception.
Fix : Do not use MustMatchers. Use Matchers instead. Also if you use scalatestplus.play, do not use PlaySpec or its derivative. Just copied PlaySpec traits to be extended in your own AbstractSpec while extending Matchers instead of MustMatchers.


⚠ Secret Website 3 has degraded performance

In fa4d807, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2820 ms

Resolved: Secret Website 3 performance has improved in d78839c.


Not all non-ephemeral messages are sync messages

now that we have the request and unavailable message types, we can't refer to all non-ephemeral messages as sync messages.

good eye


#18474 Reset UI settings improvements

Actions were moved to the Help menu:

Reset UI settings
Clear History

The planned option to clear log files wasn't implemented because it depends on #18205.
Acceptance criteria:

[x] The .plugins folder is deleted completely from the .metadata folder of the DBeaver workspace after resetting UI settings
[ ] The query manager is empty after clearing it
[x] Task run statistics is empty after clearing it

It's available only in PRO products.

verified


Too many disks = no graph

When analyzing servers with a lot of disks the diskbusy graph area gets all filled up with the disk names and shows no graphic. Splitting the disks into separate graphs like diskbusy1, diskbusy3, etc, was a nice idea, but the amount of disks seem to be too high.
Maybe, I don't know if its possible, adding a scrollbar on the side so we can scroll up and down from the names and graph areas would prevent this behavior.

thanks

This seems to be an issue with JFreeChart - there is no option to truncate the legend. The only solution I have found it to make the chart bigger. Obviously this is limited to your resolution in the GUI. You can set the size in a custom report but I am not sure you could make it big enough to show hundreds of disks.
A custom report may be the best option. With that you could just select the disks you want via multiple <field> elements.

Thanks for the reply Hunter.
Perhaps you could reduce the amount of disks per single report and split them into separate reports, like diskbusy1, diskbusy2 etc..

It may be possible to do this but it would require a lot more preprocessing since the charting engine doesn't have generic 'splitting' kind of filter on it. I would have to do it manually (ie one chart xml for disks 0-24, one for disks 25-50, etc). Not sure if that helps or not.
It may be easier to use the disk grouping feature of NMON and filter out the data at collection time.


Proposal: new config support for limiting mediatypes

Add support for new section in the config that allows end-users to limit the types of mediaTypes allowed to be pushed (both manifest config mediaType and layer mediaType).
See suggested new configMediaTypes and layerMediaTypes subsections under validation.manifests section below. Note: the top-level validation section is already defined in the docs.
Example use case - allow in the registry only artifacts representing "bananas" and "oranges" (completely made up):
validation:
  manifests:
    configMediaTypes:
      allow:
        - application\/vnd\.fruits\.(banana|orange)\.config\.v1\+json
    layerMediaTypes:
      allow:
        - application\/vnd\.fruits\.(banana|orange)\.(peel|edible)\.layer\.v1\+tar

which would cause the registry to accept the following values for manifest mediaType (i.e.  config.mediaType):
application/vnd.fruits.banana.config.v1+json
application/vnd.fruits.orange.config.v1+json

and accept the following values for layer mediaType (i.e. layers[x].mediaType):
application/vnd.fruits.banana.peel.layer.v1+tar
application/vnd.fruits.banana.edible.layer.v1+tar
application/vnd.fruits.orange.peel.layer.v1+tar
application/vnd.fruits.orange.edible.layer.v1+tar

A deny section would also be defined which works in the inverse of allow (similar to what's already in place for URL validation).
By default, if nothing specified, all mediaTypes should be accepted by the registry (such is the case today).
I'm guessing this is somehow already possible via some custom middleware or shim, but I think it might be good to expand more on manifest filtering features anyway. Let me know if I'm missing something. I'm happy to implement this. Thanks!

At the point that mediaTypes are added to index configs as well (in the OCI spec and in this project), we can add a similar section validation.indexes:
validation:
  indexes:
    configMediaTypes:
      allow:
        - application\/vnd\.fruits\.(banana|orange)\.index\.v1\+json


CoverageData db corrupted with repeated runs

When running pytest, the plugin uses the CoverageData object held in memory from pytes_cov plugin. This seems to read fine and match the report from the pytest_cov plugin.
However, when running the git-py-coverage standalone script the CoverageData object seems to only load once from .coverage file. The second time seems to load with less information. Third/fourth time the .coverage DB might not even load at all.
Suspect the issue is the CoverageData object is not closing up the SQLite connection correctly when it goes out of scope. Is there something we need to do manually to close this out? Method on the CoverageData object? Such that the file can be opened and reopened without corrupting.

Fixed in c4e420e72d7cba70a1b7c81d8eac3bc8cb0d0076


Shouldn't the logo of the organization be changed?

Hello,
I noticed that the logo of the organization kmonad still did not change, it still have the default empty logo. I think the KM in the main logo of the software should be the logo of the organization or even the whole logo. Anyway, I think it should be changed since the software already have a logo.
Thanks for the time.

David seems to be a tad inactive [not uncommon btw] atm and I don't think anyone else has the appropriate permissions so that's probably why it hasn't been done.

transparent logo image is here

No, the current Logo is the better one, because it is oversimplified.
(Context: https://www.youtube.com/watch?v=LoYP2mEJDJs )

Sorry, what?  @MySurmise
this is the current org logo - the default github one.
this is the actual logo, which the org is yet to change to

@david-janssen Reminder of this issue.  Not urgent, of course, I just remembered it.

Wahay, it is done. Thanks for the reminder.

Nice!  :+1:


Change: Use std::popcount for VMA_COUNT_BITS_SET in C++20

VMA_COUNT_BITS_SET is not optimized anymore by default and I don't think the user should themselves provide a optimization manually, especially when this isn't noted in the changelog (or in the docs?) and the stdlib provides a simple to use implementation.
I think it's appropriate to automatically use std::popcount if C++20 is available, as it will include its own optimized implementation from the compiler, which will probably be more optimized than VmaCountBitsSet. Additionally, if the project is built with AVX or SSE4 flags enabled, the stdlib automatically uses __popcnt() or __builtin_popcount() (or at least I observed this with MSVC).
And I think any built-in optimization is welcome.
Also, should this change be reflected in the documentation for VmaCountBitsSet?
https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator/blob/42be483bd5c6605e789e011aac684e0b95d05359/include/vk_mem_alloc.h#L3166-L3176

Thank you for this suggestion. I added usage of std::popcount, although differently than you proposed in the pull request.

Next time a review or comment before closing would've been nice, so that a PR submitter can adapt and fix any issues, and that stuff like this doesn't look like one is stealing code. Would've thought that most larger projects, especially something coming from AMD, would share the same FOSS concepts. In the end I was the one with the idea and initial implementation, but as this is such a small change I'm not gonna be too annoyed, however I'm just concerned in general that this might happen with other contributions.
Apart from that, I actually personally prefer my solution because it doesn't waste a function call in debug, doesn't unnecessarily include the <bit> header if another custom implementation was already defined, and better shows that it's using std::popcount instead of the custom implementation. But I guess you do you, you don't seem to answer any other PRs after they got closed or merged anyway.

I'm sorry, you are right, I could have left the ticket open. It was closed automatically as I typed "Closes #251" in the commit message. Please note the commit mentions this ticket number, so anyone looking at the commit history can find out it was your idea. I didn't intent to look like I stole it.

Thank you for acknowledging this and sorry if I might've sounded a bit aggressive, was just a bit confused and surprised. I don't quite care as this change is minimal. Although I've also thought that in these cases a "Co-authored-by" in the commit metadata could be a solution, but I'm not asking for anything and I'll just leave this as it is now.


Changing selenium version

Describe your changes :

Changed selenium version to 4.1.1

Type of change :

[x] Improvement

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
@darth-coder00 @shahsank3t

@kshinde2512 Can we link the open ticket for version change here?

Issue for this PR
#2909


semicolons

There should not be a semicolon between the option clause and the rest of the select statement.  The option clause is a part of the select just like from or where.  Once we removed the semicolon before option, these examples started to work.

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

ID: 17d712c8-87f2-7203-6dd9-5f23a60cdfc2
Version Independent ID: 536de496-f292-b661-7da7-350d59ec331f
Content: Cardinality Estimation (SQL Server) - SQL Server
Content Source: docs/relational-databases/performance/cardinality-estimation-sql-server.md
Product: sql
Technology: performance
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

@ecklesweb Thank you for bringing this to our attention. I have submitted a PR, #9796, to correct this. https://github.com/MicrosoftDocs/sql-docs-pr/pull/9796. It should be live tomorrow morning. Please let me know if you need anything further, or if I can proceed with closing out this Git Issue. Thanks!

Thanks for this fix Julie (PR 9796).  We can now Close this Issue 1895.
@julieMSFT @ecklesweb

Hi Gene, I was waiting to see if the customer responded. I will close open issues after giving the customer some time to respond.
Thank you,
Julie
From: Gene Milener<EMAIL_ADDRESS>Sent: Wednesday, April 10, 2019 10:40 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Julie Rasnick<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] semicolons (#1895)
Closed #1895https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034988757&sdata=vXU2IoXRgC9p7Eeg4lxdNEnzqKAHS2Lr%2BVE%2BmuUgL%2B8%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895%23event-2266863455&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034988757&sdata=tzHKswBql%2FvHkj9WJaesaYf93YpNGdOEgUEqhEQlqb0%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAqqgekcsRekRErjE-KrswtWSRp_dbW6Uks5vfiHxgaJpZM4clG6h&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034998769&sdata=s%2Fi1Zexm7Tvxmfc9WYIhVaP1R2D8VV07b0%2Fvs%2BPYm60%3D&reserved=0.

Looks good to me.
From: julieMSFT<EMAIL_ADDRESS>Sent: Wednesday, April 10, 2019 1:42 PM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: ecklesweb<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] semicolons (#1895)
Hi Gene, I was waiting to see if the customer responded. I will close open issues after giving the customer some time to respond.
Thank you,
Julie
From: Gene Milener<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Sent: Wednesday, April 10, 2019 10:40 AM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Julie Rasnick<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Mention<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [MicrosoftDocs/sql-docs] semicolons (#1895)
Closed #1895<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034988757&sdata=vXU2IoXRgC9p7Eeg4lxdNEnzqKAHS2Lr%2BVE%2BmuUgL%2B8%3D&reserved=0 &data=02%7C01%7CJulie.Rasnick%40microsoft.com%7C5dc30c1a03594196e17a08d6bddb8f86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636905148034988757&sdata=vXU2IoXRgC9p7Eeg4lxdNEnzqKAHS2Lr%2BVE%2BmuUgL%2B8%3D&reserved=0>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895%23event-2266863455 https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F1895%23event-2266863455&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034988757&sdata=tzHKswBql%2FvHkj9WJaesaYf93YpNGdOEgUEqhEQlqb0%3D&reserved=0 &data=02%7C01%7CJulie.Rasnick%40microsoft.com%7C5dc30c1a03594196e17a08d6bddb8f86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636905148034988757&sdata=tzHKswBql%2FvHkj9WJaesaYf93YpNGdOEgUEqhEQlqb0%3D&reserved=0>, or mute the thread<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAqqgekcsRekRErjE-KrswtWSRp_dbW6Uks5vfiHxgaJpZM4clG6h https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAqqgekcsRekRErjE-KrswtWSRp_dbW6Uks5vfiHxgaJpZM4clG6h&data=02|01|Julie.Rasnick%40microsoft.com|5dc30c1a03594196e17a08d6bddb8f86|72f988bf86f141af91ab2d7cd011db47|1|0|636905148034998769&sdata=s%2Fi1Zexm7Tvxmfc9WYIhVaP1R2D8VV07b0%2Fvs%2BPYm60%3D&reserved=0 &data=02%7C01%7CJulie.Rasnick%40microsoft.com%7C5dc30c1a03594196e17a08d6bddb8f86%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636905148034998769&sdata=s%2Fi1Zexm7Tvxmfc9WYIhVaP1R2D8VV07b0%2Fvs%2BPYm60%3D&reserved=0>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/sql-docs/issues/1895#issuecomment-481790823 , or mute the thread https://github.com/notifications/unsubscribe-auth/AvKakT4QYLbT9ZyhwTZ74ovxUf3FjR-Bks5vfiJ1gaJpZM4clG6h .  https://github.com/notifications/beacon/AvKakSRrSoCZp9yvwl9dsfcNxhgCIPO3ks5vfiJ1gaJpZM4clG6h.gif


Well-defined API errors

It would be great to have a schema for API errors, or at least some pre-defined codes that are easily machine-readable.
Detecting which error happened can ease robust programming a lot.
For example, I might want to explicitly handle accessing a node that does not exist, retry on a connection error, and fail hard on a syntax error in the query.

Have you seen this list of error codes?
https://www.graph.cool/docs/reference/simple-api/error-management-aecou7haj9/

Thanks a lot for bringing this up @ejoebstl. Typed errors is definitely something we'd love to support at some point in the future as soon as this becomes officially part of the GraphQL spec. Check the following issue to track the progress in the GraphQL spec: https://github.com/facebook/graphql/issues/135
Until then working with the API error codes as @kbrandwijk pointed out is the way to go.
Any other suggestions are more than welcome!


Make Codesandbox with latest VTU more visible for reporting issues

#1417 points out there is some friction in reporting an issue. We should have a link to a codesandbox that people can use to repro their problem easily. Maybe we can include this in the issue template.

I like the idea, how do we change the issue template for VTU?

I have no idea, probably need to ask someone to do it. We can change the GH default here, though: https://github.com/vuejs/vue-test-utils/blob/dev/.github/ISSUE_TEMPLATE.md
Let's ping someone in core.

I have realized CSB may not be ideal; you cannot access node_modules or the original git repo, it seems, which is very annoying for debugging more complex issues.

We have updated the PR issues template to use the built-in GH one.


Unordered processing of workers in subChain

The subChain extension generates chains with unordered processing:
val chain = rootChain<Context> {
    subChain<Context, SubContext> {
        worker("") { delay(1000); println("1") }
        worker("") { delay(100); println("2") }
    }
}

prints 2, then 1. So the workers run in parallel, while the expected behavior is 1 then 2

Fixed in ver. 0.5.5


not able to send utxo and dvm dfi to another dvm and evm address

What happened:
I want to send utxo dfi to another dvm address and also tried to send dvm dfi to a erc55 evm address. after hitting the send button the password prompt normally shows off. the send button gets grey after hitting but nothing else happens.
What you expected to happen:
Sending should work normal.
How to reproduce it (as minimally and precisely as possible):

use a wallet address with utxo dfi

try to send dfi to another dvm address

use a wallet address with token dfi

try to send dfi to a evm or erc55 address

Anything else we need to know?:
Android 13
Defichain Light Wallet 2.28.0
TestNet

It worked now, password prompt was there and i'm was able to send funds. But the password prompt seems in general very flaky. Please recheck. Thanks

The issue did not happened again, all is working very smoothly. Don't know if we had an issue with the testnet this morning. Maybe a lot of people switched the node to version 4.0.0 stable. This was maybe the cause of this problem.

Not happened anymore


Proxy Error

I've no idea why but whenever I want to go to "My Modules" section it get the following error as response (in the hidden AJAX call).
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /module.

Reason: Error reading from remote server

Apache Server at modules.zendframework.com Port 80

I've no idea how to debug this but I would like to add my module to the index.

Reference #353

Unable to reproduce at the moment, closing.
@stevleibelt
If you still see this issue, please re-open!

@localheinz
Still the same, did a check on chromium v40.x
Console Log:
 GET http://zfmodules.com/module 500 (Internal Server Error)jquery-1.11.2.min.js:4 m.ajaxTransport.sendjquery-1.11.2.min.js:4 m.extend.ajaxjquery-1.11.2.min.js:4 m.fn.loaduser:176 (anonymous function)

When I reload the page itself (meaning the chosen tab is switched back to "Registered Modules", I could find the following error in the Network Log:
Warning: array_filter(): An error occurred while invoking the filter callback in /var/www/modules/module/ZfModule/src/ZfModule/Controller/IndexController.php on line 148

@stevleibelt thanks! But maybe this is another issue, it is not a proxy error now :weary:

@gianarb you are true. It is always hard to decide if reopen an existing (but technically not fitting) defect or create a new one and refer to the the existing one.
Thanks for the work so far :+1:

Thanks for this bug reporting! :+1:

maybe this is a fatal error when the rate limit is reached for github?

Yes for me this is the problem.. :+1: @stevleibelt sorry what's your repositories number? Thanks

@gianarb I only have around 52 repositories :-/

maybe the limit is 30

I have 43 repos and "My modules" page is working.

Perfect thanks! The number of repo is not the problem..
Gianluca Arbezzano
Il 24/feb/2015 18:42 "Witold Wasiczko"<EMAIL_ADDRESS>ha
scritto:

I have 43 repos and "My modules" page is working.
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/modules.zendframework.com/issues/197#issuecomment-75806087
.


Update transferring-a-repository.md

Why:

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

This pull request is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!

Privasi-data-org#2387
Pada tanggal Sel, 29 Des 2020 00.29, Janice<EMAIL_ADDRESS>menulis:

Closed #2387 https://github.com/github/docs/pull/2387.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/2387#event-4152627112, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIBHHVGTYZHNKTSVHN4PLLSXC553ANCNFSM4VLY3DJQ
.


Feature/Twilio-Appointment-Reminders

Description
• Built state management using API Context for TwilioForm Component.
• Created an onSubmit function in the APIContext folder that has an API that connects FE to BE using a POST request that sends messages. Later, this function is imported to the TwilioForm Component so it can submit the form after clicking the button "Send".
• Created an onHandleChange function in the TwilioForm component to handle event target values inside the input, and text area.
• Built validation form using YUP for the form in the TwilioForm Component.  YUP is used as a schema builder validation for objects.  Also, created a state variable called twilioError that is a boolean set as False, and when there is a catch error in the API data, twilioError will be set as True and will show that there is an error in the TwilioForm showing a design error with a pink color.
TrelloCards Link - https://trello.com/c/jvrpDyg1/62-as-a-groomer-i-will-like-to-send-sms-to-customers-to-remind-him-her-about-appointments
Type

[ ] This is a bugfix.
[ ] This is a new feature.
[x] This is part of a feature.

Organization

[x] Have you linked this pull request to a Trello card?
[x] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[ ] Is this a work in progress?
[x] Is this ready to be reviewed?
[x] Have you added two reviewers to this pull request?

No, the URL is good! thanks, Aaron, and Kim!


Add support for the Aqara vibration sensor (Model DJT11LM)

As discussed here:
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/748#issuecomment-418842352
This payload will need to be mapped:
    {
        "config": {
            "battery": null,
            "on": true,
            "reachable": true,
            "temperature": 0
        },
        "ep": 1,
        "etag": "010f388f53a1178a50b280aa6752ee54",
        "manufacturername": "LUMI",
        "mode": 1,
        "modelid": "lumi.vibration.aq1",
        "name": "lumi.vibration.aq1 (2)",
        "state": {
            "buttonevent": 1009,
            "lastupdated": "2018-09-05T18:40:04"
        },
        "type": "ZHASwitch",
        "uniqueid": "00:15:8d:00:02:a8:ad:09-01-0101"
    }

Up to you  how you want to map the shake, drop and tilt buttonevent :)

Merged into master


Install on Debian

Hello dear Team,
Could it be possible to install the same as way below and get an install-master folder ? Currently empty
wget https://codeload.github.com/wintercms/install/zip/master -O wintercms.zip
Wish you all the best to come
Best regards

You can try install by download release version. Here is latest https://github.com/wintercms/winter/archive/refs/tags/v1.1.2.zip

Hello, thanks for this reply,
I'm feeling sorry because I'm a non-technical user,
this is the way I used to install in the past with an install.php file inside the folder, similar to the one below, I'm hoping it could be done soon.
https://codeload.github.com/octobercms/install/zip/master
Cordially


Send shadowsocks handshake with payload if available

I am not sure if it makes sense

Codecov Report

Merging #1292 (b0d4be7) into master (c278db5) will decrease coverage by 0.26%.
The diff coverage is 0.00%.

:exclamation: Current head b0d4be7 differs from pull request most recent head 543c799. Consider uploading reports for the commit 543c799 to get more accurate results

@@            Coverage Diff             @@
##           master    #1292      +/-   ##
==========================================
- Coverage   44.64%   44.38%   -0.27%
==========================================
  Files         485      476       -9
  Lines       29524    29427      -97
==========================================
- Hits        13182    13060     -122
- Misses      14939    14950      +11
- Partials     1403     1417      +14

Impacted Files
Coverage Δ

proxy/shadowsocks/client.go
1.00% <0.00%> (-0.03%)
:arrow_down:

app/proxyman/outbound/errors.generated.go
0.00% <0.00%> (-100.00%)
:arrow_down:

transport/internet/udp/dispatcher.go
64.76% <0.00%> (-12.39%)
:arrow_down:

common/task/task.go
88.88% <0.00%> (-7.41%)
:arrow_down:

common/drain/drainer.go
65.51% <0.00%> (-6.90%)
:arrow_down:

common/buf/reader.go
82.35% <0.00%> (-5.89%)
:arrow_down:

testing/servers/tcp/tcp.go
81.81% <0.00%> (-5.46%)
:arrow_down:

app/proxyman/outbound/handler.go
38.05% <0.00%> (-4.48%)
:arrow_down:

transport/internet/udp/hub.go
73.61% <0.00%> (-4.17%)
:arrow_down:

proxy/freedom/freedom.go
45.00% <0.00%> (-4.00%)
:arrow_down:

... and 18 more

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 c278db5...543c799. Read the comment docs.


Dropbox Wrapper = body not working well with multiple selection

Hello.
I updated the library to version 1.0.29 (I was using 1.0.27) to take advantage of an issue that was reported to be fixed but got another issue. Basically, when we have dropboxWrapper='body' and we are using multiple selections, once we start selecting the options we can't any longer close the dropdown (we can even see the arrow switching):

Hope we can have this fixed asap. Thank you and continue the amazing work you're doing with this library.

Please share your page URL.

Hi team,
I worked with @gnbm, and I'ld like to share the sample for this.
https://jsfiddle.net/joaoMFerreira/4g0s7unx/25/
I found out that the issue was replicated every time we destroy and initialize the same select, we are doing this because we need to update some parameters, and there isn't a method for that.
Apart from it I found out that the click listeners are not removed by the destroy() method. After I remove them by hand our issue was solved.
Not related with this repo, but I discover what I think is a typo on the popover, there is written "destory" where the events are removed.
Hope this helps to found the solution.
Thank you for the waiting and support.

Hi team,
I worked with @gnbm, and I'ld like to share the sample for this.
https://jsfiddle.net/joaoMFerreira/4g0s7unx/25/
I found out that the issue was replicated every time we destroy and initialize the same select, we are doing this because we need to update some parameters, and there isn't a method for that.
Apart from it I found out that the click listeners are not removed by the destroy() method. After I remove them by hand our issue was solved.
Not related with this repo, but I discover what I think is a typo on the popover, there is written "destory" where the events are removed.
Hope this helps to found the solution.
Thank you for the waiting and support.

@JoaoFerreira-FrontEnd I think this could be the reason. I will check and fix it. Thanks for sharing it.

@gnbm This issue has been fixed in the release v1.0.30


adding mmz sepolia key handover task

Description
Adding the Mode, Metal, and Zora Key Handover task.
Additional context
The checks for the SignFromJson.s.sol file have been omitted

After my meeting I'll looking into fixing that new error


Plagiarism checks: Fix an issue with team exercises

Checklist
General

[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I strictly followed the server coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Motivation and Context
Team participations are wrongly filtered since #7766
This PR tries to fix that

Steps for Testing

Create team exercises (programming, text, modeling)
Add at least 2 teams and submit 2 similar solutions
Run the plagiarism checks and make sure it works properly

Please also double check that nothing breaks for individual exercises in courses and exams
Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review
Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Summary by CodeRabbit

New Features

Enhanced plagiarism detection with new filtering criteria based on minimum score and student roles.

Refactor

Replaced AuthorizationCheckService with PlagiarismService for better authorization checks and plagiarism detection across various services.

Tests

Updated tests to reflect changes in service dependencies and logic.

I tried to test on TS3 with a programming exercise involving two teams, each consisting of two members. When I pressed the "Detect Plagiarism" button, I received the following error:

On TS5 it is impossible to start programming exercises - Artemis returns 500 errors caused by GitLab

Hey @jakubriegel
Since you already have test setup somewhere, could you try to rerun it based on the latest commit?