Generated beta models and request builders

This pull request was automatically created by Azure Pipelines. Important Check for unexpected deletions or changes in this PR.

will be merged through #21


Our librustzcash dep needs consideration

I saw a commit message on librustzcash that said Return the network type for encoding addresses as part of the network… …parameters. and the changed code in that commit looked like something I was working with very recently.
I then noticed our repo is pointing to a week-old commit on that same repo, hardcoded as a patch in Cargo.toml.
With work happening so close to a rapidly moving library, I thought I would point this out, and see if we should adjust this setting.
For example, I'm not sure if the code I wrote a couple days ago would still be working with this update.
Feel free to close this issue if there's no problem, and/or we could use this space to discuss.

Did you test it, to see if the update effected the behavior of your regtest zingo-cli?

Did you test it, to see if the update effected the behavior of your regtest zingo-cli?

I did not.


WIP: Use common sequence name to get id from Oracle

This is a fix for https://github.com/symfony/symfony/issues/54193 by using a common sequence name for getting the ID's for Oracle databases.
This will require the user to name their sequences seq_<table_name> or SEQ_<TABLE_NAME> but at least allows you to use messenger with Oracle after properly setting up the table.

Closing this to send the pull request to the main repo.


Spevacus: Watch dotssy.com

Spevacus requests the watch of the watch_keyword dotssy\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

dotssy\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Mast in Charcoal HQ


Docs: Fancify dialog styling example

Description

How Has This Been Tested?

visually
Types of changes

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

Before:

After:

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

This is lightyears better than before. Muchos gracaias @danielchalmers !


Release 1.0.0

First Release

MathVector has included
Add operations with float vector with sse code
More efficient than normal operations

Good job🔥


Read from stream instead of a file

Hi All,
Is there any way to use this module to get the input from a stream?
I get a yaml in a http response and i'd like to convert it to an object on the file without writing it out to a file first...
Any ideas?
Thanks!

Reading from a stream is not possible. Reading from a file is also not possible. JS-YAML can work only with plain strings.

"usage: js-yaml [-h] [-v] [-c] [-t] file
Positional arguments:
file           File with YAML document(s)"
It seems to me that it waits for a file as an input. And checking in loader.js I saw something like this too. What am I missing here?

This is help string of our CLI utility. If you're going to use JS-YAML as a library, you must read "API" section of the README.

I see it now, got it! Thanks!


Support r+ mode files when uploading to table

Fixes issue #2358

I've signed it!
On 20 September 2016 at 11:18, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/pull/2360#issuecomment-248261244,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM5RysQceTu20Y4tbDRocmb2-_1gaFkks5qr7LxgaJpZM4KBdOY
.

--
skype: seb.bacon
mobile: 07790 939224
land: 01531 671074

Note that the Travis error here is a coverage failure due to this branch (correctly) not being visited.
I could remove the try/except, but then the failure mode would be an error...

@tseaver I am having a hard time remembering. The binary part in the mode is important. Is the read part important as well? Why do we not allow a or w?

@dhermes The file has to be readable for us to upload it.  rb is read-only in binary mode, r+b is read-write in binary mode.
@sebbacon LTNS!

LGTM pending Travis.

Thanks for the patch, @sebbacon !


Which method should I use if I want to do sth during class Instantiate?

Question
Hi, what should I do if I want some logic during class instantiate? For example, I want to "register" this class and initialize some class variable starts with '_'. I've tried defining my own __metaclass__ and assign it to BaseModel inherited class but it seems that __ModelMetaclass__ is the effective one. What's the correct way to do this with pydantic? Thanks.

Solved. custom metaclass works if ModelMetaclass is inherited.

Another option would be to define __init_subclass__ in a reused base class.
But if using a custom metaclass that inherits from MetaModel works for you, that's fine too!


fix GEARPUMP-186 Create 0.8.1 release

+1

Current coverage is 71.30% (diff: 100%)

No coverage report found for master at effa409.

Powered by Codecov. Last update effa409...b762fd0


Somewhat unexpected error context

ulrich@p0:/opt/gupu/new-trealla$ ./tpl -f
?- ).
Error: syntax error, mismatched parens/brackets/braces, user:1
Error: syntax error, missing operand, user:1
?- use_module(library(clpb)).
   true.
?- ).
Error: syntax error, mismatched parens/brackets/braces, library/clpb:1
Error: syntax error, missing operand, library/clpb:1

user:1 does make sense, but why library/clpb:1?

It's actually reporting (erroneously) the last file accessed.
On Thu, Mar 28, 2024 at 9:52 PM UWN @.***> wrote:

@.***:/opt/gupu/new-trealla$ ./tpl -f
?- ).
Error: syntax error, mismatched parens/brackets/braces, user:1
Error: syntax error, missing operand, user:1
?- use_module(library(clpb)).
true.
?- ).
Error: syntax error, mismatched parens/brackets/braces, library/clpb:1
Error: syntax error, missing operand, library/clpb:1
user:1 does make sense, but why library/clpb:1?
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/517, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSESNSXKJDKSDRADMXXTY2QAAZAVCNFSM6AAAAABFMUKGOWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTGMBSGY2TMMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


dora_next_event()'s delay  is too long

Here are some examples of successes and failures during my testing:

C++version, transfer 1.3 MB images, use current compiled target/debug/dora to run the project, and the delay in obtaining images is about 100ms when dora_next_event() is used. If using the directly downloaded compiled dora(v0.3.5) to run XXX.yml, the delay is 4ms (only for versions before July 19th).
In versions after July 19th, when running the official example using downloaded compiled dora, the second node cannot receive the data from the previous node due to deserialization issues. This may be caused by the mismatch between the cargo install dora cli compiled dora and the latest C++library functions. Simultaneously using current compiled target/debug/dora to run the program successfully, but the latency is still around 100ms.

So, you have to use the release version if you want to have the best latency.
Make sure to use --release when compiling dora.
If you're using the latest main branch to compile C++, you should also use dora main branch to start your dataflow.
Otherwise, use https://github.com/dora-rs/dora/tree/v0.3.5 which is tagged to 0.3.5

If you're using the latest main branch to compile C++, you should also use dora main branch to start your dataflow.

When I use the latest main branch to compile C++, the latency is 100ms. How can I reduce the latency? Should I use --release? I'm not familar with cargo and haven't found where the dora is compiled.  Thanks!

Hi! What you should do is:

install Dora-cli latest main:
clone the Dora directory and launch cargo install . inside of it
build the cxx node api in release mode:
inside the repository go to apis/cxx/node, and launch cargo build --package dora-node-api-cxx --release


Transactions search

Cool, maybe next time we can move the transactions queries functionality to some methods in the models.

Cool, maybe next time we can move the transactions queries functionality to some methods in the models.


Video Caching Progress

How to display the video cache progress?

The VideoPlayer API does not provide ways to get a value for caching progress, therefore you can only show an indeterminate progress indicator. The VideoPresenter script has the corresponding field Loading Indicator.


React-Redux - Create a Search Filter

Hello.
The objective is to make a filter when i search the name of some work i have in an array.
By this stage i have successful render the search bar and get the input value. I also render the list of works.
App.js

import React, { Component } from 'react';
import SearchBar from '../containers/search_bar';
import WorkList from '../containers/work_list.js';

export default class App extends Component {
  render() {
    return (

        <SearchBar/>
        <WorkList/>

    );
  }
}

search_bar.js
import React, { Component } from 'react';

export default class SearchBar extends Component {

  constructor(props) {
    super(props);
    this.state = { init: '' };
    this.onInputChange = this.onInputChange.bind(this);
  }

  onInputChange(event) {
    this.setState({ init: event.target.value });
  }

  onFormSubmit(event) {
    event.preventDefault();
  }
  render() {
    return (
      <form
        onSubmit={this.onFormSubmit}
        className="input-group">
        <input
          className="form-control"
          placeholder = "Procurar Trabalho"
          onChange={this.onInputChange}
          value={this.state.init} />

          <button type="submit" className="btn btn-secondary">Pesquisar</button>

      </form>
    );
  }
}

work_list.js
import React, { Component } from 'react';
import { connect } from 'react-redux';
import { fetchWork } from '../actions/index';

class WorkList extends Component {

  renderWork() {
    return this.props.works.map((work) => {
      return (

          {work.title}

      );
    });
  }

  render() {
    return (

            Nome

          {this.renderWork() }

    );
  }
}

function mapStateToProps(state) {
  return {
    works: state.works
  }
}

export default connect(mapStateToProps)(WorkList);

My Reducers -
reducer_work.js
export default function () {
  return [
    { title: 'Mirististica' },
    { title: 'Vet' }
  ];
}

index.js
import { combineReducers } from 'redux';
import MostrarTrabalhos from './reducer_work';

const rootReducer = combineReducers({
    works : MostrarTrabalhos
});

export default rootReducer;

Thank You !

Hi,
Please file issues here related to problems in the redux-actions source code. This is more general and has to do with React and Redux, and getting your code to work.
I would recommend asking for help in http://codereview.stackexchange.com/.

Thanks


claper: init at 1.1.1

Hello,
I'm looking for using Claper webapp, sadly, it's not available in nixpkgs yet.
I have started to do something, but It's obviously not working yet.
This PR is to gather some help from the community, and in the end provide Claper in Nix.
Tasks:

[x] Initial default.nix file
[x] Fetch the source and compile it
[ ] Fetch npm stuff
[ ] Make sure we can run the service in NixOS
[ ] Provide the service module configuration

The documentation to install it is here: https://github.com/ClaperCo/Claper#installation
Further documentation: https://docs.claper.co/configuration.html
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/packaging-claperco-claper-software/23307/1


Reduce number of plugin dependencies

To make plugin more compatible with others. (protect against resolved dependencies runtime incompatibility)
For instance there are two libraries set for zipping: zip4j and ziputil (zeroturnaround). Usages of ziputil need to be replaced by zipfile from zip4j.
Pebble template engine and other non-standard deps could be even embedded under internal package in a same way as it is Gradle doing, see sshj classes under com.gradle.internal.deps.org.schmidt.sshj (?)

https://code.google.com/archive/p/jarjar/

this is because when some build script user will use AEM Plugin and other Plugin simultenously, then Gradle will negotatiate/ choose more recent version from these two which could not be runtime compatible. I have already such problem with Pebble Template Engine. Pebble helpers in 2.x  have another interface signature in 3.x which caused a problem w build with Fork Plugin containing defined Pebble 2 and AEM Plugin containing Pebble 3 defined.

try removing dependency to commons IO / e.g IOUtils.toString replace with Kotlin extension function InputStream.readText() / or buffering version input.bufferedReader().use { it.readText() }

sh gradlew dependencies --configuration=implementation

> Task :dependencies

------------------------------------------------------------
Root project - Gradle AEM Plugin
------------------------------------------------------------

implementation - Implementation only dependencies for compilation 'main' (target  (jvm)). (n)
+--- unspecified (n)
+--- org.jetbrains.kotlin:kotlin-stdlib:1.3.60 (n)
+--- org.jetbrains.kotlin:kotlin-reflect:1.3.60 (n)
+--- org.jetbrains.kotlinx:kotlinx-coroutines-core:1.2.0 (n)
+--- org.apache.commons:commons-lang3:3.4 (n)
+--- commons-io:commons-io:2.4 (n)
+--- commons-validator:commons-validator:1.6 (n)
+--- com.fasterxml.jackson.module:jackson-module-kotlin:2.10.0 (n)
+--- org.reflections:reflections:0.9.9 (n)
+--- org.apache.jackrabbit.vault:vault-cli:3.2.4 (n)
+--- org.jsoup:jsoup:1.10.3 (n)
+--- org.samba.jcifs:jcifs:1.3.18-kohsuke-1 (n)
+--- biz.aQute.bnd:biz.aQute.bnd.gradle:4.2.0 (n)
+--- org.zeroturnaround:zt-zip:1.11 (n)
+--- net.lingala.zip4j:zip4j:1.3.2 (n)
+--- org.apache.sshd:sshd-sftp:2.2.0 (n)
+--- org.apache.httpcomponents:httpclient:4.5.4 (n)
+--- org.apache.httpcomponents:httpmime:4.5.4 (n)
+--- org.osgi:org.osgi.core:6.0.0 (n)
+--- io.pebbletemplates:pebble:3.0.4 (n)
+--- com.dorkbox:Notify:3.7 (n)
+--- com.jayway.jsonpath:json-path:2.4.0 (n)
+--- org.buildobjects:jproc:2.2.3 (n)
\--- net.adamcin.oakpal:oakpal-core:1.5.1 (n)

(n) - Not resolved (configuration is not meant to be resolved)

e.g needed to avoid
dependencies {
    "implementation"("com.cognifide.gradle:aem-plugin:9.2.1")
    constraints {
        "implementation"("com.google.guava:guava:23.0") {
            because("version from gradle-aem-plugin breaks robot framework")
        }
    }

as of guava is very often incompatible between each version

org.reflections to be removed as of it uses old guava / 15.

guava removed by removing reflections, jackrabbit removed by removing vault and oakpal dependencies in 13.0.0;
TODO:

remove commons-io and commons-lang3
jarjar: pebble, sshd, jcifs/smb


Can't see clipboard in combination with other library

keyboard.press_and_release('ctrl+a')
keyboard.send('ctrl+c')
pyclip.paste(text=True)

If I open notepad and click ctrl+v I'll see the text. But pyclip does not see.

Sorry, can't reproduce using notepad. Seems to work for me.

I take it back. I was able to reproduce it, but intermittently. The reason for this is that the application takes some time to receive the keystrokes and change the clipboard. If you add a small sleep between send('ctrl+c') and pyclip.paste(text=True) this becomes more reliable.
So, in essence, the problem is you're accessing the keyboard before the contents actually change.


Login module not specified in JAAS config - kafka-manager-<IP_ADDRESS>

Hi
I am running Kafka with SASL_PLAINTEXT.   I have configed Kafka-manager to use this and provided a jaas file with the correct options (well options that work for all other consumers) - but when starting kafka-manager I get the error "Login module not specified in JAAS config"
The consumers & offsets are not visible in the UI.
version   kafka-manager-<IP_ADDRESS>
jaas file:
KafkaClient {
   com.sun.security.auth.module.Krb5LoginModule required
   useKeyTab=true
   keyTab="/etc/security/keytabs/kafka.service.keytab"
   storeKey=true
   useTicketCache=false
   serviceName="kafka"
   principal="XXXXXXX";
};

2018-10-29 22:20:20,650 - [ERROR] - from kafka.manager.actor.cluster.KafkaStateActor in kafka-manager-system-akka.actor.default-dispatcher-2
KafkaTopicOffsetGetter exception
org.apache.kafka.common.KafkaException: Failed to construct kafka consumer
	at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:793) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:644) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:624) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter$$anonfun$run$7$$anonfun$apply$10$$anonfun$apply$mcV$sp$14.apply(KafkaStateActor.scala:1490) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter$$anonfun$run$7$$anonfun$apply$10$$anonfun$apply$mcV$sp$14.apply(KafkaStateActor.scala:1468) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at scala.collection.Iterator$class.foreach(Iterator.scala:891) ~[org.scala-lang.scala-library-2.11.12.jar:na]
	at scala.collection.AbstractIterator.foreach(Iterator.scala:1334) ~[org.scala-lang.scala-library-2.11.12.jar:na]
	at scala.collection.MapLike$DefaultKeySet.foreach(MapLike.scala:174) ~[org.scala-lang.scala-library-2.11.12.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter$$anonfun$run$7$$anonfun$apply$10.apply$mcV$sp(KafkaStateActor.scala:1468) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at scala.util.control.Breaks.breakable(Breaks.scala:38) ~[org.scala-lang.scala-library-2.11.12.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter$$anonfun$run$7.apply(KafkaStateActor.scala:1467) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter$$anonfun$run$7.apply(KafkaStateActor.scala:1436) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at scala.Option.fold(Option.scala:158) ~[org.scala-lang.scala-library-2.11.12.jar:na]
	at kafka.manager.actor.cluster.KafkaStateActor$KafkaTopicOffsetGetter.run(KafkaStateActor.scala:1436) ~[kafka-manager.kafka-manager-<IP_ADDRESS>-sans-externalized.jar:na]
	at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191]

Caused by: java.lang.IllegalArgumentException: Login module not specified in JAAS config
	at org.apache.kafka.common.security.JaasConfig.<init>(JaasConfig.java:66) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.common.security.JaasContext.load(JaasContext.java:90) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.common.security.JaasContext.loadClientContext(JaasContext.java:84) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:119) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.common.network.ChannelBuilders.clientChannelBuilder(ChannelBuilders.java:65) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.clients.ClientUtils.createChannelBuilder(ClientUtils.java:88) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:710) ~[org.apache.kafka.kafka-clients-1.1.0.jar:na]
	... 14 common frames omitted

Same problem here, any solution?

Hi,
I was having the same problem, but I managed to resolve the error, at least in my config.
Basically the JAAS Config from the UI expect a JAAS file content (KafkaClient Section), not a path to the jaas file.

@doddys
thanks a lot, and I have a question that the create/delete topic feature is
ok ?
doddys<EMAIL_ADDRESS>于2019年2月4日周一 下午3:34写道：

Hi,
I was having the same problem, but I managed to resolve the error, at
least in my config.
Basically the JAAS Config from the UI expect a JAAS file content
(KafkaClient Section), not a path to the jaas file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yahoo/kafka-manager/issues/577#issuecomment-460154170,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEI0tzb5FxCO5ahCcb3-kH2veUGEr_2vks5vJ-JtgaJpZM4YAspY
.

Hi,
I was having the same problem, but I managed to resolve the error, at least in my config.
Basically the JAAS Config from the UI expect a JAAS file content (KafkaClient Section), not a path to the jaas file.

Yeah, i also struggled on this, finally it is working, even i was passing the jaas file path, after changing to content it started working. Thanks

@doddys thanks a lot, and I have a question that the create/delete topic feature is ok ? doddys<EMAIL_ADDRESS>于2019年2月4日周一 下午3:34写道：
…

Yes I am able to create and delete topic. I am using kafka user keytab.

@doddys  I'm getting the same error. Can you please share your jaas.conf file?

@maldo91 I use content likes below, seems work, no error in application log
org.apache.kafka.common.security.plain.PlainLoginModule required username="xxx" password="xxxx";

@yantzu Are you OK with the list of consumers ?

good news (at least for me), it is working :-)
Great, thanks for the job

I ran in to the same issue as OP and finally got this working by entering the sasl.jaas.config value directly in the UI when creating a cluster. Has anybody else noticed that Kafka Manager then keeps printing out the SASL password in plaintext to the console repeatedly?
2019-09-23 15:44:21,573 - [INFO] k.m.a.c.KafkaStateActor - SASL Mechanism =SASL_MECHANISM_SCRAM512
2019-09-23 15:44:21,573 - [INFO] k.m.a.c.KafkaStateActor - SASL JAAS config=org.apache.kafka.common.security.scram.ScramLoginModule required username="superuser" password="***";

Any way to avoid this?

@doddys thanks a lot, and I have a question that the create/delete topic feature is ok ? doddys<EMAIL_ADDRESS>于2019年2月4日周一 下午3:34写道：
…

Yes I am able to create and delete topic. I am using kafka user keytab.
hi doddys ,how to confiig  JAAS file content for user  keytab ？

Hi, guys, I solved this problem by login to zookeeper by zkCli.sh and delete our kafka-manager config stored in zookeeper. I misconfigured the Java JAAS Config when I add a new cluster in GUI(by setting it to a path, yet it requires just a string java JAAS config, not a file containing it), so I cannot restart the CMAK, so I delete the config for the cluster in zookeeper, and restart CMAK, and add the cluster again. Now it's all fine.
Hope this help.

Hi,
I was having the same problem, but I managed to resolve the error, at least in my config.
Basically the JAAS Config from the UI expect a JAAS file content (KafkaClient Section), not a path to the jaas file.

Yeah, i also struggled on this, finally it is working, even i was passing the jaas file path, after changing to content it started working. Thanks
can you share you "SASL JAAS Config (only applies to SASL based security)" on UI ?

it is not working for me, can any one please provide complete steps?

Hi,
I'm experiencing same issue(Caused by: java.lang.IllegalArgumentException: Login module control flag not specified in JAAS config). Have placed jass.conf file in jmeter/bin and file path is mentioned in kafkaSchemaSampler.
jaas.conf file below:
JMeter {
com.sun.security.auth.module.Krb5LoginModule required
doNotPrompt=false
useKeyTab=false
debug=true
storeKey=false;
};
KafkaClient {
org.apache.kafka.common.security.plain.PlainLoginModule required
username="xxxxxxx"
password="xxxxx";
};
Can someone share steps followed in resolving this issue please?
Thanks


CreateEventActivity should be finished after creating a new Event.

Is it a ?

[x] Bug Report

[ ] Feature Request

[ ] Chore

Bug Report
Actual Behaviour
After creation of Event is successful, the CreateEventActivity still remains open.
Expected Behaviour
It's not a bug but i think it's not standard for it to remain active. In most of the standard applications, the create activities are finished after successful creation.
Not a major issue hence can be labelled later
Steps to reproduce it
Create an event using the CreateEventActivity
Would you like to work on the issue?
Yes.

Could I try this issue? Thanks!

Yeah, please go ahead.

@leeyh20 What's the status of this issue?

@iamareebjamal Sorry for the late PR, was a bit stuck somewhere. I have created the PR!


graphite-cli: mark unfree

Version 1 has no published source and doesn't specify a license.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

It looks like the repo has been archived, with a message about no longer being open source: https://github.com/withgraphite/graphite-cli
It looks like they also have a blog post about launching, but they don't say anything about going closed-source: https://graphite.dev/blog/launch

If you want we can stick with the old version. Please package it using fetchYarnDeps and remove it from nodePackages in that case.
Anyway, what's currently packaged is unfree so this should be merged before such a change is made.

I actually don't use this anymore, so I'd be happy to do whatever other people would prefer.  Marking it unfree as you're doing in this PR seems like it makes sense.


Saved snippets not Loading at all

Describe the bug
I have logged in via Google Auth on Chrome and all my saved snippets never load. I see the Sidebar and Avatar Menu, but no content at all.
To Reproduce
Just log in.
Expected behavior
Load and show my folders, list of snippets.
Screenshots

Desktop (please complete the following information):

OS: macOS Monterey v12.3.1
Browser: Chrome
Version: Version 100.0.4896.127 (Official Build) (arm64)

Update: It finally loaded, but took an extremely long time (roughly 45-50 min).


[Mondrian] Implement viewer for Mondrian files

This commit implements custom editor which provides graphical view of Mondrian JSON allocation traces (.tracealloc.json).
Issue: #395
Draft: #452
ONE-vscode-DCO-1.0-Signed-off-by: Alexander Moiseev<EMAIL_ADDRESS>Notes
Currently implemented features:

JSON input data parsing
round-robin colorized memory blocks output
ability to scale horizontally/vertically
switching between memory segments.

More features such as model trim, mouse hover info, rulers, more coloring modes etc. will be added in new PRs, #395 description contains feature roadmap.
Example data:
example.tracealloc.json.txt (remove .txt extension for plugin to properly detect .json)
Screenshots
Scaled up memory zone view:

Model "bird's eye" overview:

Light theme support:

Could you also add json file into, e.g., res/sample? Thanks.

@ai-moiseev Thanks for your work!
I am trying to understand the whole flow. (based on https://github.com/Samsung/ONE/issues/8743)

vscode runs onecc to request memory measurement for backend Z.
onecc calls some tool defined in backend Z.
some tool defined in backend Z produces memory measurement result in format of X.
onecc produces the result in json format in this PR.
vscode renders the json.

Some part of step 1 (onecc param), step 2, 3, and 4 are not a scope of ONE-vscode but a scope of ONE.
And, step 5 (this PR, in scope of ONE-vscode) is meaningful only if step 1, 2, 3, and 4 are defined and implemented.
If there's discussion in ONE repo regarding those steps, could you let us know?

@llFreetimell As you know, there was a discussion here: https://github.com/Samsung/ONE/issues/8723
It was stated that support for memory allocation format handling is outside of ONE's scope :( So I've decided to provide implementation in backend and ONE-vscode and to continue discussion on this topic.
My ONE's proposal initially included JSON file processing and conversion into SVG format, but with introduction of custom editor/viewer in ONE-vscode, we only need to add onecc compile option. I'll prepare PR for it and try to get it merged :-)

@ai-moiseev
I think there was some gap of approach between our opinions.
What I have been thought was https://github.com/Samsung/ONE-vscode/pull/483#issuecomment-1109210443.
What you've though was (I guess)

support for memory allocation format handling is outside of ONE's scope

I am OK with your way. I guess that we can have short-term and long-term approach:

short term: introduce mondrian map of backend in ONE-vscode and backend (not ONE)
long term: check introduction of mondrian to ONE (ONE is a bridge between ONE-vscode and backends)

to align with https://github.com/Samsung/ONE/issues/8743

In this view, I am OK with this PR. :-) Let me know your opinion.

I would be helpful to have a explanation of schema of json as, e.g., README.md file. Could you write one in, e.g., src/mondrian?

I would be helpful to have a explanation of schema of json as, e.g., README.md file. Could you write one in, e.g., src/mondrian?

I've added data format specification in json-schema format.

Oh. Maybe my comment was not complete enough. 😹
What I am curious is the meaning of each key and value.
E.g., If I want to write json in an editor,
I have to understand the meaning of "segments", or "size", "allocations", "offset" and so on.
Since this repo is public, anyone who access this repo also needs to understand the meaning of those keys and values.
So could you write down the meaning in README.md ?
If this explanation requires some backend knowledge, you may want to discuss this in other repo.
{
  "schema_version": 1,
  "segments": [
    {
      "name": "Segment1",
      "size": 32768,
      "allocations": [
        { "offset": 0, "size": 8192, "alive_from": 0, "alive_till": 8, "origin": "Node1" },
....

@hyunsik-yoon I've updated README.md and added text description of all fields, PTAL :) This format is intended to be as backend agnostic as possible (although it's usage limited to backends with memory scheduling; not all backends have precise cycle or timing control, so there's abstract 'lifetime' attribute, which can be relative, which is useful for luci-micro backend).

@ai-moiseev Thanks for the README.md.
I tried to write down some suggestion or question of my UI experience.
Some could be done in this PR or in next PR, depending on your opinion. :-)

Some people may not know what this json file is. So , when they click the json file, how about showing some title like Memory map over time and some description on top of graph?
After opening json file, right-bottom area shows memory, cycle, and segment. I guess memory here means total memory required through whole times? If so, how about using Total memory label?

When I select segment 2, memory is 16384 and I am not sure why. From the graph, it has one segment of 8K size. So would 8K be right for memory? (So does segment 1)

I guess X axis would be time (cycle??) and Y axis would be offset but I am not sure. How about showing the meaning of X and Y axis?
When I maximize the size of vscode to full screen and click the json file, initial graph is shown in small top left area. Maybe when user clicks json, how about fitting the graph to screen size?
Some button like 'Fit to screen size' would provide good usability.
In the json file, segment 1 has 24 cycles and segment 2 has 32 cycles. When I enlarge segment 1 to fit all cycle in width of screen and then select segment 2, segment 2 also shows 24 cycles in screen. So I fit 32 cycles of segment 2 to the width of screen. Then I select segment 1 again and found that graph is now shrunken and I had to enlarge again. I hope zoom level of each segment should be kept separately.
zooming granularity of '+' and '-' seems kinda large, I guess.

@hyunsik-yoon Thank you for a feedback! Yes, explanation UI elements are definitely needed (I planned to add rulers on top and the right and label them as 'time' and 'memory'.
Fit to screen buttons are planned (for X and Y axes) as well as ability to remember zoom and position for each memory segment (I wanted to implement submodel view functionality first and make sure these two features will not conflict with each other).
Zooming step can easily be adjusted :) (now it's 1.0, but could be anything). I'll send update to this PR which will speed it down 2x shortly.
Thank you again for your notes! I would like to quote you in parent issue to keep track of things to implement.

Some part of step 1 (onecc param), step 2, 3, and 4 are not a scope of ONE-vscode but a scope of ONE.
And, step 5 (this PR, in scope of ONE-vscode) is meaningful only if step 1, 2, 3, and 4 are defined and implemented.
If there's discussion in ONE repo regarding those steps, could you let us know?

@hyunsik-yoon I've created PR which adds save-allocations option to onecc codegen which should provide a bridge between ONE-vscode, ONE and backends with allocation trace export support.


TypeError in Samples

Hi,
I am having some problems loading the samples in this project. Let's use the 'rules.html' as an example, though they are all behaving the same way for me.
So occasionally, the page will load successfully and the states appear on the map. But then, if I refresh the page, it fails to load completely. If I open the console in the browser, I see there is a TypeError of:
'modules.d3Layer is not a constructor'
This is how it behaves the majority of the time, but every so often, it will work again.
I have tried this on Chrome and Firefox and I have run both local copies and the ones you have hosted. All result in the same behaviour.
Do you have any ideas what could be happening?
Thanks in advance!

sorry for the extremely belated reply, but i made some changes/updates in november/december of 2014 which should have resolved these errors.
if you could confirm, that'd be swell.


3d-DNA makes my assembly fragmentary?

Hi,
I started with my assembly .fasta (contig number: 260, legnth: 500 mb, N50:  7.3 mb), but after 3d-DNA, I got .FINAL.fasta (contig number:  5,520, legnth: 500 mb, N50:  0.3 mb). And I used the defaul pipeline:
run-asm-pipeline.sh -m diploid -i 15000 -r 2 ./assembly.fasta ./aligned/merged_nodups.txt
I have no idea how I could optimize my result. I am not sure which step I have something wrong.
Please give me some advise, and how could I let my assembly more chromosome-level?
Thank you.

Hello Yang-Tui,
Please consult the Genome Assembly Cookbook, see dnazoo.org/methods. There are also a lot of relevant discussions on the forum (dnazoo.org/forum = aidenlab.org/forum.html)
Thanks,
Olga


Installation Errors

I've been trying to get started with this but having issues getting it installed. When I run this in Windows cmd
yarn create shopify-pipeline name-of-your-project
I get this error.
Installing shopify-pipeline. This could take a while.
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: spawn yarnpkg ENOENT
    at exports._errnoException (util.js:1020:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:197:32)
    at onErrorNT (internal/child_process.js:376:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
error Command failed.
Exit code: 1

Has anyone experienced this or know what the issue may be?

What version of node are you using? What version of yarn?

Thanks for the reply. I'm using
Node: v8.9.4
Yarn: 1.3.2
OS is Windows 10.

I'd definitely try with a different version of node (do you have NVM?).
Might be totally unrelated, but I had a similar issue on Slate a while back. Reverting to node v6.12.1 LTS fixed the issue.


Render as many lines as space allows before ellipsing

I have a fixed sized container with two Text widgets in a column. The first text should take up as much space as needed to render it fully and the second text should render as many lines as the remaining space allows before getting ellipsed.
      new Container(
          padding: new EdgeInsets.all(15.0),
          width: 150.0,
          height: 110.0,
          color: Colors.red,
          child: new Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              new Text(
                'I take up as much space as possible.',
                style: const TextStyle(fontWeight: FontWeight.bold),
              ),
              child: new Text(
                'The space I have is very limited. I get ellipsed.',
                overflow: TextOverflow.ellipsis,
              ),
            ],
          ),
        ),

The second text always gets ellipsed after one line even when there is space to render more lines. There is no way (short of knowing beforehand how many lines the second text can render) to have the text render as many lines as possible before ellipsing.

The ParagraphConstraints class probably needs to be extended to take a maxHeight parameter to make this work.

One work-around (that may break in unexpected ways if for example emojis are used):
        new Container(
          padding: new EdgeInsets.all(15.0),
          width: 150.0,
          height: 110.0,
          color: Colors.red,
          child: new Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              new Text(
                'I take up as much space as possible.',
                style: const TextStyle(fontWeight: FontWeight.bold),
              ),
              new Expanded(
                child: new LayoutBuilder(
                    builder: (BuildContext context, BoxConstraints constraints) {
                      print(constraints);
                  return new Text(
                    'The space I have is very limited. I get ellipsed.',
                    overflow: TextOverflow.ellipsis,
                    maxLines: (constraints.maxHeight / Theme.of(context).textTheme.body1.fontSize).floor(),
                  );
                }),
              ),
            ],
          ),
        ),

Here's a more complicated example that demonstrates the workaround (https://github.com/flutter/flutter/issues/15465#issuecomment-372499251):
https://gist.github.com/HansMuller/21f2e7b93d8f05c0ebd2617906ced5a6
The layout of each fixed-height NewsCard is a column of paragraphs like this:
[A title that fills 1-3 lines]
[A description that fills the remaining vertical space]
[A footer that occupies 1 line]
The description's text is wrapped in a LayoutBuilder that computes a value for Text.maxLines based on the font size and the available height. A slightly better version of the code would also factor in the TextStyle's height and the current MediaQueryData.textScaleFactor.
The overall layout is handled programmatically  with CustomMultiChildLayout.
In this screenshot second card's title overflows the 3-line limit and the description ("An equally long description...") is limited to 3 lines because that's all that will fit.

Same demo, with the card's height increased from 176 to 200. Now the description fits; no ellipsis.

Ran into this issue too....

https://docs.flutter.io/flutter/widgets/RichText-class.html is a possible solution?

@goderbauer thank you for the workaround

You can simply use Text(maxLines: 2, overflow: TextOverflow.ellipsis) to set how many lines should render before ellipsing.

@Hixie @goderbauer I am not sure if you considered this before: this is a major accessibility issue.
This is because when you design layout, you usually work with textScaleFactor = 1. However, as the textScaleFactor can be arbitrarily set by the user, this is a major problem.
If I define maxLines: 3 in my layout because that fits within the height given the font size, the whole layout will break when textScaleFactor = 2 for example. In this case, the max line should automatically be changed to 1, however, this is not possible.

So we are left with:

Either an ugly layout that always draws the ellipse after the first line
A layout that breaks when accessibility settings are used
Using @goderbauer's workaround from above, which will break when trying to work with intrinsics

@goderbauer also I think the issue title should be:

Text always Ellipsized After First Line using implicit maxLines

Combining some reading from other issues with similar issues and stackoverflow, I managed to get a more reliable workaround. I ran some resize tests and got more reliable results.
@creativecreatorormaybenot - does this work any better for your edge cases?
@override
  Widget build(BuildContext context) {
    return Flexible(
      child: LayoutBuilder(builder: (context, constraints) {
        final TextStyle style = Theme.of(context).textTheme.bodyText2!;

        //use a text painter to calculate the height taking into account text scale factor.
        //could be moved to a extension method or similar
        final Size size = (TextPainter(
                text: TextSpan(text: notes, style: style),
                maxLines: 1,
                textScaleFactor: MediaQuery.of(context).textScaleFactor,
                textDirection: TextDirection.ltr)
              ..layout())
            .size;

        //lets not return 0 max lines or less
        final maxLines = max(1, (constraints.biggest.height / size.height).floor());

        return Text(
          'some really really long text',
          style: style,
          overflow: TextOverflow.ellipsis,
          maxLines: maxLines,
        );
      }),
    );
  }

The weird thing is that TextOverflow.clip and TextOverflow.fade work, but not TextOverflow.ellipsis.
Any idea how to fix this in the SDK?
I'm a newbie so that I can not go deep into the problem.


Adding additional V3 test coverage

Coverage increased (+1.5%) to 59.124% when pulling 3e6ae9efe03cb667b9d7f818726a3bf64c6225f0 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+1.5%) to 59.124% when pulling 3e6ae9efe03cb667b9d7f818726a3bf64c6225f0 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+6.6%) to 64.286% when pulling 179b42447cfbde25ebf04d1d8c23e89b79faa374 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+6.6%) to 64.286% when pulling 179b42447cfbde25ebf04d1d8c23e89b79faa374 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+14.5%) to 72.143% when pulling 7249c89cdda9d7f42873e1871df565fa6769dd9b on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+20.9%) to 78.571% when pulling 25a4b6c1ac35b060f86177299fda2383bc0eb227 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+20.9%) to 78.571% when pulling 25a4b6c1ac35b060f86177299fda2383bc0eb227 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+20.9%) to 78.571% when pulling 25a4b6c1ac35b060f86177299fda2383bc0eb227 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+20.9%) to 78.571% when pulling 25a4b6c1ac35b060f86177299fda2383bc0eb227 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+20.9%) to 78.571% when pulling 25a4b6c1ac35b060f86177299fda2383bc0eb227 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+27.8%) to 85.507% when pulling 8a21aa36a37e353bb3a283413ad8e8bc8d4308a2 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.

Coverage increased (+27.8%) to 85.507% when pulling 8a21aa36a37e353bb3a283413ad8e8bc8d4308a2 on v3-coverage into 2aab97244056d1b014811f723fbc124842d1b4d7 on v3-sdk-updates.


Unit test

Workflow seems to be working as expected https://github.com/kubeslice/kubeslice-monitoring/pull/30/checks. So merging this to master.


[WIP]Feat: modernize testing

Gonna have to split this up into smaller chunks and take a different approach. There are some good changes in this PR so I'm gonna open a couple of PR based on this one.


Fix 404 Error Handling

404 error handling was returning [Object object] on the command line. This PR fixes the error handling to return appropriate data to the user and on the command line.

Pull Request Test Coverage Report for Build 2083

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

Totals

Change from base Build 2078:
0.0%

Covered Lines:
2047

Relevant Lines:
2705

💛  - Coveralls


Added Simple Microservices Javaspringboot with MongoDB

@knockcat Thanks Befor dear

@knockcat Hello sir, why this repo has exclude label in hacktober

I forget to add the hacktober-accepted tag , now I am adding but please let me know if it still show this after some time.

hacktoberfest update every 15 min, but after 1 hour my PR not change from "Exclude to Waiting"
Maybe I got wrong step

but you can check my new PR, I was added new project structure for Microservices Java Spring


Voxpopuli text column "raw_text" HF dataset card shows empty string.

When pseudo-labelling the Voxpopuli dataset the "raw_text" (needed for option  --text_column_name) may be an empty string for some examples - see HF dataset model card here for an empty "raw_text" example.
Question: how do I check which text name ("raw_text" or "normalized_text") was used when creating the pseudo-labelled datasets on HF, such as https://huggingface.co/datasets/distil-whisper/voxpopuli ?

Closing and moving the above information to https://github.com/huggingface/distil-whisper/issues/97.


[Model] Fix Phi-3.5-vision-instruct 'num_crops' issue

This PR changes phi3v to load num_crops config from image processor config.
FIX #7718
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Does version 3.0 of the model still work with the new default? Also, please update the supported models page with version 3.5 of the model.

Now that there is direct multi-image support, is that possible in vllm?  There's still an assert against it no?

Does version 3.0 of the model still work with the new default?
Didn't mean to change the default value. I reverted it back. The right value will be loaded from the image_preprocessor config.

I tested locally, both versions pass the tests. I didn't add both models in the test to save CI cost.

Also, please update the supported models page with version 3.5 of the model.
Done.


code action kind set to empty string

Code actions can have a kind which is an empty string.
Received response 'textDocument/codeAction - (283)' in 5ms.
Result: [
  {
    "title": "Change visibility to pub(crate)",
    "kind": "",
    ...

I think if the kind is not known it should not be set. For example emacs lsp-ui will by default filter code actions, and it will ignore kind nil, but will filter out kind "" (https://github.com/emacs-lsp/lsp-ui/issues/443).

Hmm, looking at https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textDocument_codeAction shows an empty kind
/**
 * A set of predefined code action kinds.
 */
export namespace CodeActionKind {

	/**
	 * Empty kind.
	 */
	export const Empty: CodeActionKind = '';

So I was probably wrong and I'm thinking this is not a rust-analyzer bug (though I really don't know anything about the LSP protocol).

Yeah, I think this works as intended


Create Kruskals_Algorithm.py

Title :
Kruskal's algorithm
Issue no :
Solves #74
Description
Kruskal's algorithm is a minimum spanning tree algorithm that finds the smallest set of edges that connects all vertices in a graph without forming cycles. Adding this to the "Graphs" folder.
Checklist

[x] I have read and agree to abide by the Code of Conduct
[x] I have read and followed the Contributing Guidelines

Please review and suggest changes.
Thanks.

Great job!
Thank you for contributing. Do give this repository a star if you feel like ✨


Nested defaultdict loses its default factory

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
Pydantic fails to properly construct the defaultdict when it is nested into another defaultdict.
After the model construction, the outer dict will have the correct default_factory, but the inner one will have its factory set to None.
Example Code
from collections import defaultdict
from typing import DefaultDict
from pydantic import BaseModel

class TestModel(BaseModel):
    d: DefaultDict[int, DefaultDict[int, int]]

model = TestModel(d=defaultdict(lambda: defaultdict(int)))
parsed = TestModel.parse_raw(model.json())
print(parsed.d[1])     # defaultdict(None, {})
print(parsed.d[1][2])  # KeyError: 2

Python, Pydantic & OS Version
pydantic version: 1.9.1
            pydantic compiled: True
                 install path: /Users/abc/PycharmProjects/Pybugtic/resources/venv/lib/python3.9/site-packages/pydantic
               python version: 3.9.5 (default, Jul  9 2022, 23:20:38)  [Clang 13.1.6 (clang-13<IP_ADDRESS>.5)]
                     platform: macOS-12.3-arm64-arm-64bit
     optional deps. installed: ['typing-extensions']

Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

A possible workaround is to add a validator like this:
class TestModel(BaseModel):
    d: DefaultDict[int, DefaultDict[int, int]]

    @validator("d")
    def dd(cls, value):
        value.default_factory = lambda: defaultdict(int)
        return value

I believe this is fixed by #4516 and will be fixed in v2.

Resolved in #5744


Re-enable LDC testing + small improvement to the docs action

Note: the end goal is to drop DMD. But we better ensure we have at least 2 compilers that can compile and run our code successfully.

So are we good to go ?

Needed by #691

looks good to me. Debugging is also good.  However, I haven't tested it on the Windows version.


Kustomize 3.8.2 is not creating the Namespace with the namePrefix

Bug Report
Using Kustomize 3.8.2 I'm facing this issue as reported here
/snap/bin/kustomize build config/default | kubectl apply -f -
namespace/system created
customresourcedefinition.apiextensions.k8s.io/tenants.capsule.clastix.io created
clusterrole.rbac.authorization.k8s.io/capsule-proxy-role created
clusterrole.rbac.authorization.k8s.io/capsule-metrics-reader created
clusterrolebinding.rbac.authorization.k8s.io/capsule-manager-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/capsule-proxy-rolebinding created
mutatingwebhookconfiguration.admissionregistration.k8s.io/capsule-mutating-webhook-configuration created
validatingwebhookconfiguration.admissionregistration.k8s.io/capsule-validating-webhook-configuration created
Error from server (NotFound): error when creating "STDIN": namespaces "capsule-system" not found
Error from server (NotFound): error when creating "STDIN": namespaces "capsule-system" not found
Error from server (NotFound): error when creating "STDIN": namespaces "capsule-system" not found
Error from server (NotFound): error when creating "STDIN": namespaces "capsule-system" not found
Error from server (NotFound): error when creating "STDIN": namespaces "capsule-system" not found

kustomize is not creating the expected namespace with the prefix (for this OS project, capsule-system) but just system
What did you do?
Using<EMAIL_ADDRESS>What did you expect to see?
Despite any version, able to install the scaffolded Operator using make deploy
What did you see instead? Under which circumstances?
I cannot install my scaffolded Operator using<EMAIL_ADDRESS>Environment
Operator type:
/language go
Kubernetes cluster type:
N.R.
$ operator-sdk version
operator-sdk version: "v0.19.2", commit: "4282ce9acdef6d7a1e9f90832db4dc5a212ae850", kubernetes version: "v1.18.2", go version: "go1.13.10 linux/amd64"

$ go version (if language is Go)
go version go1.13.8 linux/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:47:40Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-30T20:19:45Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution
Informing with version pinning to 3.8.1 is mandatory, but that would be awkward! :)
Additional context
N.R.

Ok, it seems this is an expected side-effect.

HI @prometherion,
if you check the Makefile https://github.com/clastix/capsule/blob/master/Makefile#L106 it specifies the Kustomize version that is supported/tests with the project. However, you should not find issues with a lower upper version since it theoretically has no breaking changes.
could you please confirm that you just see that issue when you are using this version?

I was able to use kustomize without any issue until 3.8.1 and just the 3.8.2 seems to break it.
The issue is that version has been published on snap today, so probably nothing to do on Operator SDK side, but just reporting this in case other people would face the same issue due to PATH precedence.

From kustomize 3.8.1 to 3.8.2 should not have breaking changes. I think it shows a bug with could you please raise it there or in kubebuilder(upstream)?
And then, I think we can agree to close this one. WDYT?

@camilamacedo86 Reading https://github.com/kubernetes-sigs/kustomize/pull/2742, it seems like this change was the bugfix.
@prometherion If you'd like to use kustomize 3.8.2+, you can also update the Namespace name in config/manager/manager.yaml to the full name (and probably bump the kustomize version in the scaffolded Makefile).
I'll close this since the currently supported kustomize version is 3.5.4 and manually updating the Namespace name in the kustomize base seems to be a working solution as well.

Shows that we need to check that with upstream. Tracked: https://github.com/kubernetes-sigs/kubebuilder/issues/1657
We need to upgrade the dep to solve tech debts and investigate this scenario.

ddfff

@camilamacedo86 Reading kubernetes-sigs/kustomize#2742, it seems like this change was the bugfix.
@prometherion If you'd like to use kustomize 3.8.2+, you can also update the Namespace name in config/manager/manager.yaml to the full name (and probably bump the kustomize version in the scaffolded Makefile).
I'll close this since the currently supported kustomize version is 3.5.4 and manually updating the Namespace name in the kustomize base seems to be a working solution as well.

@joelanford  How would one update the config/manager/manager.yaml file exactly? What is the full name? Is it the metadata.namespace:? And if so what should I write there?


Issues with JSON Schema format while compiling Schema in AJV

Hi,
Converted JSON schema is given to AJV to validate user input. There are some issues with the schema generated using sequelize-json-schema while compiling it with AJV.
for example:
{
"incidentID": 0,
"errorCode": 1254,
"description": "unknown format "int32" is used in schema at path "#/properties/id""
}
where do we use this format? is there any plans to remove it?
FYI:
https://stackoverflow.com/questions/44878192/convert-sequelize-model-to-json-schema-for-user-input-validation
Regards,
Sandeep

format is swagger extension to JSON Schema, int32 is defined here https://github.com/OAI/OpenAPI-Specification/blob/master//versions/2.0.md#data-types . If your tool doesn't support swagger extensions, it probably should just ignore it.

Ah, well, ajv supports its own format values https://www.npmjs.com/package/ajv#formats , and not all of them are compatible with swagger's definition. Honestly I do not know what to do here, neither swagger nor ajv are standard.


it is no working on 2019-06-20-raspbian-buster

it is no working on 2019-06-20-raspbian-buster

yes