How to Get Started Excel Importer

Can you please provide a quick walk-through on what I need to do to get started with Excel Importer?  I am using XAF Winforms and I'm not sure what I need to do to include this in my project.  Do I use Nuget to add ExcelImporter to Project.Module, then use Nuget to add ExcelImporter.Win to Project.WinModule?  I notice that this adds a bunch of dependencies.
I'm not sure what to do after this?
Thank you for taking the time to help guide me in the right direction.

Ok. Sure enough as soon as I post this I get it figured out. Here is what I did:

Add ExcelImporter.Win to Project.WinModule.

Received compile error stating to add reference to Xpand.Persistent.BaseImpl to your front end project and set its Copy Local=true.  So I added this reference to Project.Win and voila!  It works!

yeah anything you know about XAF applies here, in addition most the registration of the platform agnostic module if exists is optional if there is a platform dependent module. The platform dependent will register the agnostic. For the rest there will be guidance as you proceed e.g. the BaseImpl case.
In any case feel free to post on anything.


class MultiProcessRecording drops various recording methods

When using DirectoryMultiProcessingAnalyzer, it's not clear why it internally uses the MultiProcessRecording class. This seems to just return a subset of methods/attrs of a passed-in Recording instance (config, detections, path etc), meaning that access to other Recording methods is lost, e.g. extract_detections_as_audio.
Rather than iterating over the list of Recording instances, generating a list of MultiProcessRecording instances, would it not be better to just return the initial list, as happens in DirectoryAnalyzer ?
I'm happy to work out a PR for this, if you think the above suggestion is a good idea.

Hi @mrichar1, apologies for the delay in responding.
The MultiProcessRecording class exists because the Pool can't pass objects, like theRecording instances, to the threads and back. The data has to be pickled or serialized. Currently, the code is passing dicts around for pooled threads.
Question: at what point do you need the extraction functionality during your analysis?
If you're trying to add the extract_ functionality as part of the multi-process, then that functionality would need to be added to the process_from_queue method. I think that was my original plan, but I never had a use case and didn't settle on an interface. Personally, I use a database as a queue and run multiple processors in single threads (usually 8 on a machine at a time).
If you're ok with those extraction functions being run in a single thread post-analysis, then this is probably an easier issue to solve. MultiProcessRecordingcould be changed to be a subclass ofRecordingBase. Again, those extract_` methods wouldn't be multi-threaded, but it would provide the interface you're looking for ... depends on your needs.
I'm happy to further discuss or review a PR if you're interested.
Joe

Hi,
Thanks for getting back to me and explaining things.
I think for my use case (and probably more generally) it would be sufficient for the class to return 'more complete' Recording instances with the extract_ methods, for these to be run separately after the multi-process.
I'm wanting to look at the recording metadata and extract audio/waveforms only for those with a high confidence interval, or just once for each species from each set of recordings. As you say, designing an interface incorporating this kind of logic into the multi-process might be awkward - while you could accept a function to call against each recording, capturing the 'results' from that function and returning them in a standard way could prove tricky!
For my use case I suspect single-thread post-analysis will be sufficient, as I'm likely to be discarding the majority of recordings anyway. Also there's nothing stopping me from using a separate Pool to do the extractions in parallel if needed.
So yes, making MultiProcessRecording a subclass of RecordingBase seems like a sensible way to do it - let me know if this is something you can do, or if it would be easier for me to try a PR for review?

This has been released as 0.12.0. Thanks for the posting the issue and sharing your use case!


Refactor

Move Latin cipher to its own module and use traits when implementing other simple cryptosystems
Consider where traits and other generics might be more appropriate for implementing other simple cryptosystems
Try to apply the principle of least functionality. Are there places where we can make the code more modular? Places where we can simplify the functionality and make it more easily testable/diagnosable when something goes wrong. i.e., reread the refactoring advice from the Rust book, 12.3

Also worth asking if the example should really be an example, or should be a separate crate.

Loosely:

There is now a ring trait bc of pull #24, which is related to this refactor.
Should probably use workspaces:

make the example a binary crate within the workspace instead
have a library crate for classical cryptosystem
in future other types of primitives can have their own crates

But that still leaves how to refactor the classical cryptosystem library as an open question, and I think this latter is what I ought to would like to do first.

This should have been linked to close with #33.


Tracking issues of iceberg-rust v0.3.0

Iceberg-rust 0.3.0
The main objective of 0.3.0 is to have a working read path (non-exhaustive list :)

[x] Scan API Added by @liurenjie1024 in https://github.com/apache/iceberg-rust/pull/129
[ ] Predicate pushdown into the Parquet reader Worked by @viirya in https://github.com/apache/iceberg-rust/pull/295
[x] Manifest pruning on using the field_summary: Skipping data on the highest level by pruning away manifests:

[x] Transforms added by @marvinlanhenke in https://github.com/apache/iceberg-rust/pull/309
[x] ManifestEvaluator added by @sdd in https://github.com/apache/iceberg-rust/pull/322

[ ] Implement todo's some of the expressions need to be implemented.
[ ] Tests port the test-suite from Python to Rust

[ ] Filter in TableScan in flight by @sdd in https://github.com/apache/iceberg-rust/pull/323

[ ] Skipping manifest-entries within a manifest based on the 102: partition struct

[x] Accessors added by @sdd in https://github.com/apache/iceberg-rust/pull/317
[x] Projection added by @marvinlanhenke in https://github.com/apache/iceberg-rust/pull/309
[ ] ExpressionEvaluator Binds the partition-spec schema to the 102: partition struct and evaluates it.
[ ] Filter in TableScan

[ ] Skip data-files using the metrics evaluator

[x] InclusiveMetricsEvaluator worked on by @sdd in https://github.com/apache/iceberg-rust/pull/347
[x] InclusiveProjection added by @sdd in https://github.com/apache/iceberg-rust/pull/322
[ ] Filter in TableScan

Nice to have (that's related to the above):

[ ] Implement skipping based on sequence number skip DELETE manifests that contain unrelated delete files.

Catalog integration:

[ ] Catalog support

[ ] REST Catalog: First stab by @liurenjie1024 in https://github.com/apache/iceberg-rust/pull/78

[ ] @Fokko will follow up with IT tests

[ ] Glue Catalog Added by @marvinlanhenke in:

[ ] https://github.com/apache/iceberg-rust/pull/294
[ ] https://github.com/apache/iceberg-rust/pull/304
[ ] https://github.com/apache/iceberg-rust/pull/314

[ ] SQL Catalog Worked on by @JanKaul in https://github.com/apache/iceberg-rust/pull/229
[ ] Hive Catalog Added by @Xuanwo.

[ ] Do we want similar IT tests as in PyIceberg?

For the release after that, I think the commit path is going to be important.
Iceberg-rust 0.4.0 and beyond
Nice to have for the 0.3.0 release, but not required. Of course, open for debate.

[ ] Support for Positional Deletes Entails matching the deletes to the datafiles based on the statistics.
[ ] Support for Equality Deletes Entails putting the delete files in the right order to apply them in the right sequence.

Commit path
The commit path entails writing a new metadata JSON.

[ ] Applying updates to the metadata Updating the metadata is important both for writing a new version of the JSON in case of a non-REST catalog, but also to keep an up-to-date version in memory. It is very much recommended to re-use the Updates/Requirement objects provided by the REST catalog protocol.

[ ] REST Catalog serialize the updates and requirements into JSON which is dispatched to the REST catalog.
[ ] Other catalogs For the other catalogs, instead of dispatching the updates/requirements to the catalog. There are additional steps:

[ ] Logic to validate the requirements against the metadata, to detect commit conflicts.
[ ] Writing a new version of the metadata.json.
[ ] Provide locking mechanisms within the commit (Glue, Hive, SQL, ..)

[ ] Update table properties Sets properties on the table. Probably the best to start with since it doesn't require a complicated API.
[ ] Schema evolution API to update the schema, and produce new metadata.
[ ] Partition spec evolution API to update the partition spec, and produce new metadata.
[ ] Sort order evolution API to update the schema, and produce new metadata.

Metadata tables
Metadata tables are used to inspect the table. Having these tables also allows easy implementation of the maintenance procedures since you can easily list all the snapshots, and expire the ones that are older than a certain threshold.
Write support
Most of the work in write support is around generating the correct Iceberg metadata. Some decisions can be made, for example first supporting only FastAppends, and only V2 metadata.

[ ] Commit semantics

[ ] MergeAppend appends new manifest list entries to existing manifest files. Reduces the amount of metadata produced, but takes some more time to commit since existing metadata has to be rewritten, and retries are also more costly.
[ ] FastAppend Generates a new manifest per commit, which allows fast commits, but generates more metadata in the long run.

[ ] Snapshot generation manipulation of data within a table is done by appending snapshots to the metadata JSON.

[ ] APPEND Only data files were added and no files were removed.
[ ] REPLACE Data and delete files were added and removed without changing table data; i.e., compaction, changing the data file format, or relocating data files.
[ ] OVERWRITE Data and delete files were added and removed in a logical overwrite operation.
[ ] DELETE Data files were removed and their contents logically deleted and/or delete files were added to delete rows.

[ ] Add files to add existing Parquet files to a table.

[ ] Name mapping in case the files don't have field-IDs set.

[ ] Metrics collection There are two situations:

[ ] Collect metrics when writing This is done with the Java API where during writing the upper, lower bound are tracked and the number of null- and nan records are counted.
[ ] Collect metrics from footer When an existing file is added, the footer of the Parquet file is opened to reconstruct all the metrics needed for Iceberg.

@Fokko thanks for your effort here

Thanks for putting this together @Fokko! It's great to have this clarity on where we're heading. Let's go! 🙌

Hi, @Fokko About the read projection part, currently we can convert parquet files into arrow streams, but there are some limitations: it only support primitive types, and schema evolution is not supported yet. Our discussion is in this issue: https://github.com/apache/iceberg-rust/issues/244

About the glue, hive, rest catalogs, I think we already have integrations:
https://github.com/apache/iceberg-rust/blob/2018ffc87625bdff939aac791784d8eabc4eda38/crates/catalog/glue/tests/glue_catalog_test.rs
https://github.com/apache/iceberg-rust/blob/ffd76eb41594416b366a17cdbc85112c68c01a17/crates/catalog/hms/tests/hms_catalog_test.rs
https://github.com/apache/iceberg-rust/blob/d6703df40b24477d0a5a36939746bb1b36cc6933/crates/catalog/rest/tests/rest_catalog_test.rs

Also as we discussed in this doc, do you mind to add datafusion integration, python binding, wasm binding into futures?

Hi, @Fokko About the read projection part, currently we can convert parquet files into arrow streams, but there are some limitations: it only support primitive types, and schema evolution is not supported yet. Our discussion is in this issue: https://github.com/apache/iceberg-rust/issues/244 And here is the first step of projection by @viirya : https://github.com/apache/iceberg-rust/pull/245

Thanks for the context, I've just added this to the list.

About the glue, hive, rest catalogs, I think we already have integrations:

Ah yes, I forgot to check those marks, thanks!

Also as we discussed in this doc, do you mind to add datafusion integration, python binding, wasm binding into futures?

Certainly! Great suggestions! I'm less familiar on some of these topics (like Datafusion), feel free to edit the post if you feel something is missing.

Certainly! Great suggestions! I'm less familiar on some of these topics (like Datafusion), feel free to edit the post if you feel something is missing.

...for Datafusion I have provided a basic design proposal and implementation for some of the datafustion traits, like catalog & schema provider; Perhaps we can also move forward on this: #324

Certainly! Great suggestions! I'm less familiar on some of these topics (like Datafusion), feel free to edit the post if you feel something is missing.

...for Datafusion I have provided a basic design proposal and implementation for some of the datafustion traits, like catalog & schema provider; Perhaps we can also move forward on this: #324

Yeah, I'll take a review later.

Hi, most of the issues in our 0.3 milestone have been closed. I plan to clean up the remaining issues and initiate the release process. Any ideas or comments?

@Xuanwo Thanks for driving this. It would be good to get everything that we have on main out to the users 👍

I have created https://github.com/apache/iceberg-rust/issues/543 to track the release process, please let me know if you think anything missed.


[AMQP Python] Message settlement

Issue
implement the amqp protocol section 3.4, This is the feature required by service bus received message settlement (complete/defer/deadletter/abandon)

references

uamqp implementation details:

python

message.py: https://github.com/Azure/azure-uamqp-python/blob/master/uamqp/message.py#L484-L573
receiver.py: https://github.com/Azure/azure-uamqp-python/blob/master/uamqp/receiver.py#L190-L219

cython

message_receiver.pyx: https://github.com/Azure/azure-uamqp-python/blob/master/src/message_receiver.pyx#L73-L109
c_message_receiver.pxd: https://github.com/Azure/azure-uamqp-python/blob/master/src/vendor/inc/c_message_receiver.pxd#L33

c

message_receiver.c: https://github.com/Azure/azure-uamqp-python/blob/master/src/vendor/azure-uamqp-c/src/message_receiver.c#L537
link.c https://github.com/Azure/azure-uamqp-python/blob/master/src/vendor/azure-uamqp-c/src/link.c#L1707
link.c https://github.com/Azure/azure-uamqp-python/blob/master/src/vendor/azure-uamqp-c/src/link.c#L161

done with release of service bus 7.10.0


Fix broken packs.download action

We didn't propagate verifyssl argument to the _clone_repo method.

On a related note - I will work up on hooking up pylint in our lint process. This error would get caught by pytlint.

@kirilstrax Are we already working on some end to end tests for packs actions?

LGTM

@Kami : it's already done, available in "tests" pack and afaik works on build (https://github.com/StackStorm/st2/tree/master/contrib/tests > test_packs_pack.*)
If I understand correctly (and clone repo is part of packs.install from repo), then it should be tested by "test_packs_install_multiple_packs_from_repo" step of that workflow

The test needs to be added back  I yanked it out when the whitespace issue was causing failures.  Either way, this would not have caught the verifyssl bug since we don't use it.

@DoriftoShoes Sorry, can you please clarify it - we don't use what?

Maybe I missed the context of this PR.  Was the action completely broken?

@DoriftoShoes Yeah, "packs.download" was completely broken which means each packs.install and packs.download action would fail.

@kirilstrax Thanks. I had a look at those tests and yeah, you are right, those tests should have caught that bug.
I'll bug @DoriftoShoes and make sure those tests hooked up again :P


Paypal checkout popup not working properly

I am trying to integrate Paypal using Braintree PayPalClient-Side Implementation, when i click on the Button it open the popup window, show this on mobile screen
https://developer.paypal.com/demo/checkout/#/pattern/client

Yikes, thanks for the report. Looking into this right away.

This should now be resolved -- please clear your browser cache and try once more. Thanks again for the report.


Possible to make this into a full fledge http server with multi threading?

Nice work! How do u show the remote ip address of the client?

https://manpages.debian.org/unstable/liburing-dev/io_uring_enter.2.en.html#IORING_OP_ACCEPT should expose the source route of inbound


Stack overflow for mutually recursive type aliases

To reproduce, add these type aliases to a roc program, or the repl:
Tool : [X, FromJob Job]
Job : [Job Tool (List Job)]

For example:
  The rockin’ roc repl
────────────────────────

Enter an expression, or :help, or :q to quit.

» Tool : [X, FromJob Job]
… Job : [Job Tool (List Job)]
… {}

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
Abort trap: 6

I think this is a duplicate of https://github.com/roc-lang/roc/issues/3216


Enable short_open_tags

@bparees Would be nice to have it enabled as 5.5 does. PTAL

would it make sense for this to be configurable?

@remicollet any idea why we changed the default on this in 5.6?

No idea if (and why) this have changed from previous image, but short tags are deprecated and discouraged for year, especially because of conflict with <?xml tag.
I really think we should keep them disabled by default.

Notice: short tags are also disabled by default in RHEL since PHP 5.3 (php53 in RHEL-5 or php in RHEL-6)

thanks @remicollet
@spinolacastro with that in mind, i think we'd only want to accept this if you instead make it a configurable option (via env var like the other options) that defaults off.

Thanks, i'll make the changes.
2016-04-29 10:25 GMT-03:00 Ben Parees<EMAIL_ADDRESS>
thanks @remicollet https://github.com/remicollet
@spinolacastro https://github.com/spinolacastro with that in mind, i
think we'd only want to accept this if you instead make it a configurable
option (via env var like the other options) that defaults off.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/openshift/s2i-php/pull/95#issuecomment-215710202

@bparees PTAL

@spinolacastro please add this to the readmes for 5.5 and 5.6:
https://github.com/openshift/s2i-php/blob/master/5.6/README.md#environment-variables
https://github.com/openshift/s2i-php/blob/master/5.5/README.md#environment-variables

@bparees done

lgtm [test]


Final filenames not showing up

All but the last menu will show content! I run the "geturl" method, find any library (such as "angularjs"), navigate to the proper version, and the menu after that is a list of blank items. When I pick one at random it will insert //cdnjs.cloudflare.com/ajax/libs/angular.js/1.4.0-beta.4/[object Object]. Thoughts?

This is now resolved.


Formatter bug in if else brackets

I have noticed following bug in if .. else conditional statement
after first bracket is pointer and press enter formatter creates close bracket
this case works
if(key1 && kay2 == value2 || boo3 || boo4){
  trace(key1)
}

this does't
if(key1 && kay2 == value2 ||
   boo3 ||
   boo4){
   trace(key1)
}

see gif anim.

@elsass: Seem this is in ASCompletion formatter.

Yes the detection of matching closing brace could be improved - it doesn't get far enough to understand that it's an if statement.

Seems to not be reproducible anymore.


Please add a LICENSE file

According to http://wiki.ros.org/axis_camera, axis_camera is under the BSD license, which says

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Alas, there are multiple variants of the BSD license out there and it's not obvious to me which one applies. Could you add a copy of the license with copyright notice on top to the axis_camera repo to save distributors from having to figure it out?
Even better if individual source files have a short notice [1] so the license information is easy to track down even out of context.
Thanks,
Jonathan
[1] like this one: https://go.googlesource.com/go/+/master/src/go/ast/ast.go
// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

Fixed by https://github.com/CreativeEntropy/axis_camera/commit/38280e45c00cf4c5364ecdbb5fed72155d7bc66d.


[bug] : increase padding of components in light mode

#issue : 8

increase some padding of components in light mode

/attempt #8

please  explane me that how to setup this project  and dependicieses

how i setup this project locally in my machine  please explane me


Destiny 2 Banning Virtual Input

Don't use these macros. Keep your account safe.
For any new viewers of this repository, I don't recommend you use these AHK macros. AHK in specific is very easy to detect with virtual input anyways. Bungie now announced they are banning virtual input. This includes macros. If you do use macros in this game, I recommend custom XML ones, or SendKeys method in C#.
Example of SendKeys method:
SendKeys.Send("{Enter}")
Using timers to pair with this in WinForms is very useful.
Custom XML macros could be Razer Synapse Macro Module etc.

Hi, thanks for letting me know about the announcement. I didn't notice that as it's been a while since I played Destiny 2.
By the way, that's kind of surprising Bungie is finally making a move for macros. (which was quite unlikely)
I will add a note and link to this issue in the front of README.

Completely understandable. The only reason why Bungie is targeting macros now is because players are getting XP too fast with it. It's seen as more of a cheat than a utility nowadays. Your macros are written very good! I have just seen new people viewing this repo lately and want them to stay safe.

Don't use these macros. Keep your account safe.

Bungie now announced they are banning virtual input. This includes macros. If you do use macros in this game, I recommend custom XML ones, or SendKeys method in C#.

Example of SendKeys method: SendKeys.Send("{Enter}") Using timers to pair with this in WinForms is very useful.
Custom XML macros could be Razer Synapse Macro Module etc.

I have seen no mention of Bungie banning virtual input.  Where did you see

@potatoexploder can you post the news / update that Bungie said they are banning the use of virtual input? I can't seem to find it anywhere.


"shift" and "unshift" naming conflict with Stylus bif

Stylus has "shift" and "unshift" built-in functions for working with lists. Jeet should avoid overriding it.
(Specifically, I am facing the problem of kouto-swiss "linear-gradient" mixin being broken because of this...)

@teohhanhui I don't see why we can't shorten that some more. j- or jt-.

Clarity. It's only 4 characters anyway (one of the benefits of having a
short name).
On Thu, 19 Feb 2015 09:12 oliverbenns<EMAIL_ADDRESS>wrote:

@teohhanhui https://github.com/teohhanhui I don't see why we can't
shorten that some more. j- or jt-.
—
Reply to this email directly or view it on GitHub
https://github.com/mojotech/jeet/issues/381#issuecomment-74982739.

@teohhanhui the more I think about your suggestion the more I like it.
Have every method prefixed with jeet- and then simply alias any non-conflicting API methods.
Feel free to open a PR. If not I can sort this. Want 6.2/7 out soon!

You'd also need to update the website of course. How would you handle the Youtube videos? Add an annotation?

I don't know exactly how namespaces works, is not possible to customize it with a variable?
Like @oliverbenns, I suggest a short name like j or j-. It may be a short name, but when you're writing it lots of times, it may get in the way.

Inclined to agree with it being j-. In Tenerife atm but am a bit bored of being permanently drunk so will work on this now.


How to use golang to implement python's tf.train.Example().serializetostring.

I'm trying to  using the python training model, deploy services with golang. However, the following problems arise when using golang for prediction.
predict with python:
    def predict_np(self):
        predict_fn = self.get_predict_fn(self.np_path)
        inputs = np.array([[6.4, 3.2, 4.5, 1.5], [6.4, 3.2, 4.5, 1.5]])
        for item in inputs:
            examples = []
            feature = {"your_input": tf.train.Feature(float_list=tf.train.FloatList(value=item))}
            example = tf.train.Example(features=tf.train.Features(feature=feature))
            examples.append(example.SerializeToString())
            print(type(example.SerializeToString()))
            predictions = predict_fn({"inputs": examples})
            print(predictions)

it works ok.
predict with golang
package main

import (
	"fmt"
	tg "github.com/galeone/tfgo"
	"github.com/gogo/protobuf/proto"
	tf "github.com/tensorflow/tensorflow/tensorflow/go"
	"github.com/tensorflow/tensorflow/tensorflow/go/core/example"
	"loadEstimator/train"
)

func main() {
	data := [][]float32{{6.4, 3.2, 4.5, 1.5}, {6.4, 3.2, 4.5, 1.5}}
	columnsName := []string{"a", "b", "c", "d"}
	for _, item := range data {
		// npData:numpy data like in python {"inputs":[6.4,3.2,4.5,1.5]}
		npData := make(map[string][]float32)
		npData["your_input"] = item
		predictNP(npData)
	}

}

func loadModeSavedPB(path string) (model *tg.Model) {
	model = tg.LoadModel(path, []string{"serve"}, nil)
	return
}

func predictNP(data map[string][]float32) {
	pdModePath := "./static/1"
	model := loadModeSavedPB(pdModePath)
	sequence := sequenceNP(data)
	fmt.Println(sequence)
	fakeInput, _ := tf.NewTensor([]string{sequence})
	results := model.Exec([]tf.Output{
		model.Op("dnn/head/Tile", 0),
	}, map[tf.Output]*tf.Tensor{
		model.Op("input_example_tensor", 0): fakeInput,
	})
	predictions := results[0].Value().([][]float32)
	fmt.Println(predictions)
}

func sequenceNP(featureInfo map[string][]float32) (seq string) {
	feature := make(map[string]*example.Feature)
	for k, v := range featureInfo {
		valFormat := train.Float32ToFeature(v)
		feature[k] = valFormat
	}
	Features := example.Features{Feature: feature}
	myExample := example.Example{Features: &Features}
	seq = proto.MarshalTextString(&myExample)
	return
}

package train

import "github.com/tensorflow/tensorflow/tensorflow/go/core/example"
func Float32ToFeature(value []float32) (exampleFeature *example.Feature) {
	floatList := example.FloatList{Value: value}
	featureFloatList := example.Feature_FloatList{FloatList: &floatList}
	exampleFeature = &example.Feature{Kind: &featureFloatList}
	return
}

There is an error
2019-11-12 11:42:05.021196: W tensorflow/core/framework/op_kernel.cc:1401] OP_REQUIRES failed at example_parsing_ops.cc:144 : Invalid argument: Could not parse example input, value: 'features: <
  feature: <
    key: "your_input"
    value: <
      float_list: <
        value: 6.4
        value: 3.2
        value: 4.5
        value: 1.5
      >
    >
  >
>
'
panic: Could not parse example input, value: 'features: <
  feature: <
    key: "your_input"
    value: <
      float_list: <
        value: 6.4
        value: 3.2
        value: 4.5
        value: 1.5
      >
    >
  >
>
'
	 [[{{node ParseExample/ParseExample}}]]

i'm using proto.MarshalTextString(&myExample)  in golang,and using
example = tf.train.Example(features=tf.train.Features(feature=feature)) examples.append(example.SerializeToString())
in python.
I am not sure whether serialization in these two languages is equivalent, and if not, how can I implement SerializeToString in golang? pls

i'm sorry,in fact,i need use seq,err = proto.Marshal(&myExample)
i got []byte in golang is
[10 36 10 34 10 10 121 111 117 114 95 105 110 112 117 116 18 20 18 18 10 16 205 204 204 64 205 204 76 64 0 0 144 64 0 0 192 63]
but got
b'\n$\n"\n\nyour_input\x12\x14\x12\x12\n\x10\xcd\xcc\xcc@\xcd\xccL@\x00\x00\x90@\x00\x00\xc0?' in python
then golang panic
2019-11-12 15:50:31.436302: I tensorflow/cc/saved_model/reader.cc:31] Reading SavedModel from: ./static/1
2019-11-12 15:50:31.440917: I tensorflow/cc/saved_model/reader.cc:54] Reading meta graph with tags { serve }
2019-11-12 15:50:31.442798: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.2 AVX AVX2 FMA
2019-11-12 15:50:31.445938: I tensorflow/cc/saved_model/loader.cc:182] Restoring SavedModel bundle.
2019-11-12 15:50:31.461115: I tensorflow/cc/saved_model/loader.cc:132] Running initialization op on SavedModel bundle.
2019-11-12 15:50:31.465338: I tensorflow/cc/saved_model/loader.cc:285] SavedModel load for tags { serve }; Status: success. Took 29047 microseconds.
panic: Expects arg[0] to be string but uint8 is provided

goroutine 1 [running]:
github.com/galeone/tfgo.(*Model).Exec(0xc00000e028, 0xc0000b1c50, 0x1, 0x1, 0xc0000b1cb8, 0x0, 0x2, 0x400cd3f)
	/Users/wqq/go/src/github.com/galeone/tfgo/model.go:74 +0xd1
main.predictNP(0xc00008c6f0)
	/Users/wqq/go/src/loadEstimator/main.go:46 +0x34a
main.main()
	/Users/wqq/go/src/loadEstimator/main.go:19 +0x27f

So I think byte is different in golang and python

i sloved

@atlantiswqq  how does sloved it ,i got the same error ! thank you very much

@atlantiswqq

@atlantiswqq

https://github.com/galeone/tfgo#train-with-tfestimator-serve-in-go, tfgo might help you.

ping @atlantiswqq id love to know as well how you fixed it

In fact, I have added this serialization operation into . In the source code of TensorFlow, I saw several Protobuf files, and I compiled them into the go version. I also wrote some methods to help you serialize the data in the form of array and dictionary.
@roffe @gao8954

@atlantiswqq do you have any writeup or similar on how to reproduce & build a image trainer in Go?

@atlantiswqq do you have any writeup or similar on how to reproduce & build a image trainer in Go?

I don't recommend you use go for training, I just use go to train some models of natural language


Line Break configuration

Currently, the line break is mandatory and we should specify "lf" or "ctrf".
Would it be possible to have an 'auto' option for lineBreak or even the possibility to disable completely the check?

Technically it can't.


feat(button): dark theme colors

Description

Scope

[x] Minor: New Feature

going to merge.. can make any color fixes in a follow-up pr


pg_wire: executing queries with field descriptor using pg protocol cause panic

Describe the bug
Queries that use pg protocol and involve any field descriptor (e.g. using PostgreSQL client of different languages) will panic the entire RisingWave frontend.
cursor.execute("select (2, '%s');", ("2333333",))

# or any other type
cursor.execute("select (2, %s);", (2333333,))

This bug is discovered because in certain circumstances, my RisingWave receives such a query from unknown sources:
Since for now RisingWave only supports very limited types of field descriptors, we may need to work around to trace the error to certain position. When I managed to trace it, it originates from pg_wire. The token that exactly causes this error (in the above query) seems to be "(2 "
thread 'tokio-runtime-worker' panicked at 'called `Option::unwrap()` on a `None` value', /Users/kiven/risingwave/src/utils/pgwire/src/pg_protocol.rs:332:55
stack backtrace:
   0: rust_begin_unwind
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panicking.rs:142:14
   2: core::panicking::panic
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panicking.rs:48:5
   3: core::option::Option<T>::unwrap
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/option.rs:775:21
   4: pgwire::pg_protocol::PgProtocol<S,SM>::process_parse_msg::{{closure}}::{{closure}}
             at ./src/utils/pgwire/src/pg_protocol.rs:332:35
   5: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/ops/function.rs:301:13
   6: core::option::Option<T>::map
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/option.rs:929:29
   7: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/iter/adapters/map.rs:103:9
   8: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/iter/adapters/map.rs:103:9
   9: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter_nested::SpecFromIterNested<T,I>>::from_iter
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/alloc/src/vec/spec_from_iter_nested.rs:26:32
  10: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/alloc/src/vec/spec_from_iter.rs:33:9
  11: <alloc::vec::Vec<T> as core::iter::traits::collect::FromIterator<T>>::from_iter
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/alloc/src/vec/mod.rs:2648:9
  12: core::iter::traits::iterator::Iterator::collect
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/iter/traits/iterator.rs:1836:9
  13: pgwire::pg_protocol::PgProtocol<S,SM>::process_parse_msg::{{closure}}
             at ./src/utils/pgwire/src/pg_protocol.rs:326:17
  14: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  15: pgwire::pg_protocol::PgProtocol<S,SM>::do_process_inner::{{closure}}
             at ./src/utils/pgwire/src/pg_protocol.rs:168:61
  16: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  17: pgwire::pg_protocol::PgProtocol<S,SM>::do_process::{{closure}}
             at ./src/utils/pgwire/src/pg_protocol.rs:104:38
  18: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  19: pgwire::pg_protocol::PgProtocol<S,SM>::process::{{closure}}
             at ./src/utils/pgwire/src/pg_protocol.rs:100:26
  20: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  21: pgwire::pg_server::pg_serve::{{closure}}::{{closure}}
             at ./src/utils/pgwire/src/pg_server.rs:94:46
  22: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/future/mod.rs:91:19
  23: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.35/src/instrument.rs:272:9
  24: tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:165:17
  25: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/loom/std/unsafe_cell.rs:14:9
  26: tokio::runtime::task::core::CoreStage<T>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:155:13
  27: tokio::runtime::task::harness::poll_future::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:480:19
  28: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panic/unwind_safe.rs:271:9
  29: std::panicking::try::do_call
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:492:40
  30: ___rust_try
  31: std::panicking::try
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:456:19
  32: std::panic::catch_unwind
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panic.rs:137:14
  33: tokio::runtime::task::harness::poll_future
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:468:18
  34: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:104:27
  35: tokio::runtime::task::harness::Harness<T,S>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:57:15
  36: tokio::runtime::task::raw::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:144:5
  37: tokio::runtime::task::raw::RawTask::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:84:18
  38: tokio::runtime::task::LocalNotified<S>::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/mod.rs:381:9
  39: tokio::runtime::thread_pool::worker::Context::run_task::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:435:13
  40: tokio::coop::with_budget::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/coop.rs:102:9
  41: std::thread::local::LocalKey<T>::try_with
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/thread/local.rs:445:16
  42: std::thread::local::LocalKey<T>::with
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/thread/local.rs:421:9
  43: tokio::coop::with_budget
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/coop.rs:95:5
  44: tokio::coop::budget
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/coop.rs:72:5
  45: tokio::runtime::thread_pool::worker::Context::run_task
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:434:9
  46: tokio::runtime::thread_pool::worker::Context::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:401:24
  47: tokio::runtime::thread_pool::worker::run::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:386:17
  48: tokio::macros::scoped_tls::ScopedKey<T>::set
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/macros/scoped_tls.rs:61:9
  49: tokio::runtime::thread_pool::worker::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:383:5
  50: tokio::runtime::thread_pool::worker::Launch::launch::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/thread_pool/worker.rs:362:45
  51: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/task.rs:42:21
  52: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.35/src/instrument.rs:272:9
  53: tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:165:17
  54: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/loom/std/unsafe_cell.rs:14:9
  55: tokio::runtime::task::core::CoreStage<T>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/core.rs:155:13
  56: tokio::runtime::task::harness::poll_future::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:480:19
  57: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/core/src/panic/unwind_safe.rs:271:9
  58: std::panicking::try::do_call
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:492:40
  59: ___rust_try
  60: std::panicking::try
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panicking.rs:456:19
  61: std::panic::catch_unwind
             at /rustc/9067d5277d10f0f32a49ec9c125a33828e26a32b/library/std/src/panic.rs:137:14
  62: tokio::runtime::task::harness::poll_future
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:468:18
  63: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:104:27
  64: tokio::runtime::task::harness::Harness<T,S>::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/harness.rs:57:15
  65: tokio::runtime::task::raw::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:144:5
  66: tokio::runtime::task::raw::RawTask::poll
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/raw.rs:84:18
  67: tokio::runtime::task::UnownedTask<S>::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/task/mod.rs:418:9
  68: tokio::runtime::blocking::pool::Task::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:91:9
  69: tokio::runtime::blocking::pool::Inner::run
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:325:17
  70: tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
             at /Users/kiven/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.20.1/src/runtime/blocking/pool.rs:300:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Thu Aug 25 11:23:14 UTC 2022 [risedev]: Program exited with 134

To Reproduce
Install psycopg package and its binary dependency, a PostgreSQL client in Python.
pip3 install psycopg psycopg_c

Start either a minimum or a full cluster.
risedev d
risedev d full

Execute the following command as Python script, or in Python console:
import psycopg

conn = psycopg.connect("dbname=dev user=root host=<IP_ADDRESS> port=
with conn.cursor() as cur:
      cur.execute("select (2, '%s');", ("2333333",))
      results = cur.fetchall()
print(results)
conn.close()

Expected behavior
Python script output:
(2, 2333333)

RisingWave work as expected.
Additional context
Actually when I first discovered this problem, it came from a periodic SQL from an unknown source (suspected some periodic check of pg client?) I located this SQL because my RisingWave running on M1 crashes periodically because of it.
Note that this is not the original SQL looks like, the "$" token implies this SQL has been through some parser processing, but not completed. Before the parser processing completes, the RisingWave frontend will crash.
select
	TABLE_NAME as VIEW_NAME,
	null as VIEW_TYPE_OWNER,
	null as VIEW_TYPE,
case when TABLE_TYPE = 'VIEW' then 'N' else 'Y' end as IS_SYSTEM_VIEW
from INFORMATION_SCHEMA.TABLES
	where TABLE_SCHEMA = $1 and TABLE_TYPE in ('VIEW', 'SYSTEM VIEW')
	order by TABLE_NAME asc;

I cannot find further information about such a query. When I reproduce this issue, since RisingWave only supports varchar field descriptor now, and does not recognize the type of descriptors effectively, I did some changes to bypass the type check.
Navigate to `pg_field_descriptors.rs'
impl TypeOid {
    // TODO: support more type.
    pub fn as_type(oid: i32) -> Result<TypeOid, String> {
        tracing::error!(oid);
        match oid {
            #
            0 => Ok(TypeOid::Varchar),
            1043 => Ok(TypeOid::Varchar),
            _ => {
                tracing::error!("unsupported typeoid: {}", oid);
                todo!()
            },
        }
    }

Note that this code change is only to help locate the exact problem. When I first discovered this problem, it came from a periodic SQL from an unknown source (suspected some periodic check of pg client?)
select
	TABLE_NAME as VIEW_NAME,
	null as VIEW_TYPE_OWNER,
	null as VIEW_TYPE,
case when TABLE_TYPE = 'VIEW' then 'N' else 'Y' end as IS_SYSTEM_VIEW
from INFORMATION_SCHEMA.TABLES
	where TABLE_SCHEMA = $1 and TABLE_TYPE in ('VIEW', 'SYSTEM VIEW')
	order by TABLE_NAME asc;

The SQL above will not execute in a command line (SQL parser shows error because a query cannot have $ token as plain literal). The "$" token seems to be a query transform made by the PG client when processing field descriptors.

Have you test this in postgresql? 🤔

Have you tried this in Postgresql ? 🤔

I find it also can't work in Postgresql14 .
Traceback (most recent call last):
  File "test.py", line 7, in <module>
    cur.execute("select (2, '%s');", ("2333333",))
  File "/Users/ze/Library/Python/3.8/lib/python/site-packages/psycopg/cursor.py", line 560, in execute
    raise ex.with_traceback(None)
psycopg.errors.IndeterminateDatatype: could not determine data type of parameter $1

I find it also can't work in Postgresql14 . It will reports the error like below:
Traceback (most recent call last):
  File "test.py", line 7, in <module>
    cur.execute("select (2, '%s');", ("2333333",))
  File "/Users/ze/Library/Python/3.8/lib/python/site-packages/psycopg/cursor.py", line 560, in execute
    raise ex.with_traceback(None)
psycopg.errors.IndeterminateDatatype: could not determine data type of parameter $1

That is one part of the problem only. Through debugging, I found that RisingWave doesn't recognize the descriptor type as well.
I added "Additional Context" to this issue to describe why it takes a workaround to locate the initial problem.
For this psycopg.errors.IndeterminateDatatype, I think I can later come up with a SQL that exposes the issue while still running normally on PG 14.

The typeOid do not support all type is a known issue. And it is left to be easy implemented.

The reason is for now our "extended query mode with params" is too simple.
Here is our parser to process statement with params.It's only support the format like ("select $1,$2,$3")..
sql.split(&[' ', ',', ';'])
                    .skip(1)
                    .into_iter()
                    .take_while(|x| !x.is_empty())
                    .map(|x| {
                        // NOTE: Assume all output are generic params.
                        let str = x.strip_prefix('$').unwrap();
                        // NOTE: Assume all generic are valid.
                        let v: i32 = str.parse().unwrap();
                        assert!(v.is_positive());
                        v
                    })
                    .map(|x| {
                        // NOTE Make sure the type_description include all generic parameter
                        // description we needed.
                        assert!(((x - 1) as usize) < types.len());
                        PgFieldDescriptor::new(String::new(), types[(x - 1) as usize].to_owned())
                    })
                    .collect()

It's time to rethink a parser to process more complex statement with params.

The reason is for now our "extended query mode with params" is too simple. Here is our parser to process statement with params.It's only support the format like ("select $1,$2,$3")..
sql.split(&[' ', ',', ';'])
                    .skip(1)
                    .into_iter()
                    .take_while(|x| !x.is_empty())
                    .map(|x| {
                        // NOTE: Assume all output are generic params.
                        let str = x.strip_prefix('$').unwrap();
                        // NOTE: Assume all generic are valid.
                        let v: i32 = str.parse().unwrap();
                        assert!(v.is_positive());
                        v
                    })
                    .map(|x| {
                        // NOTE Make sure the type_description include all generic parameter
                        // description we needed.
                        assert!(((x - 1) as usize) < types.len());
                        PgFieldDescriptor::new(String::new(), types[(x - 1) as usize].to_owned())
                    })
                    .collect()

It's time to rethink a parser to process more complex statement with params.

maybe we can use regex to improve it?

Another is re-use sqlparser, but I doubt it is too heavy

I'll take a time to investigate it🤔

So the problem should be parsing ${0..9} as index, not relates to select (2, '%s');.
Where is the period SQL comes from? Maybe it's good to add it as our ci tests...

So the problem should be parsing ${0..9} as index, nothing relates to select (2, '%s');.

Yes. select (2,'%s') will be convert to select (2,'$1') and we can't parse this statement.

I suspect there's something deeper.

So the problem should be parsing ${0..9} as index, nothing relates to select (2, '%s');.
Where is the period SQL comes from? Maybe it's good to add it as our ci tests...

Still trying to locate its source. Are there any logs to track a SQL executor's detail?

change Level::ERROR to Level::TRACE , then you can see the real sql run through the pgwire.
https://github.com/singularity-data/risingwave/blob/2cdbb117c10fab12890b006232690be771fbf6e4/src/utils/runtime/src/lib.rs#L40

Okay it seems to be the IntelliJ IDEA's DB Navigator plugin...
https://github.com/withrocks/idea-database-navigator/blob/b18aa57af01707a62b6d91001a5e594a2df217ce/src/com/dci/intellij/dbn/database/postgres/postgres_metadata_interface.xml#L73

I think this issue can be closed by #4900 ? @BowenXiao1999 @KivenChen

I think this issue can be closed by #4900 ? @BowenXiao1999 @KivenChen

Yes. But actually the feature is missed in our engine. @ZENOTME  you can close this and provide the link to what's missed in pgwire.

Missing feature tracking in #3676


Provide asynchronous tracking support

I would like to have asynchronous methods that do not block the program that uses the tracker.

How is this coming?  Seems like a no-brainer that I wouldn't want my app to be waiting on the tracker to complete.


ALL connectors - Getting in touch with Chris Holdgraf

hey everybody - in case you'd like get in touch you can ping me on here, or send an email to<EMAIL_ADDRESS>

If it's easier for you @choldgraf it's trivial to set up a Gitter room for this repo for faster response.

I'll use whatever works best for others.

Hi @dsten/instructors (esp @cboettig ) - a few people mentioned some confusion about the Table object that was created for the course. There's isn't any documentation out there on how to use it, so I wrote a quick reference guide on how to do things with a Table. It's modeled after the "10 minutes to pandas" tutorial, though it doesn't assume anything Pandas-specific.
Link: 10 minutes to tables
It's still in an incomplete state (in particular, I haven't figured out I/O or pivot tables yet) but should have lots of useful information. It might change if the datascience API changes, so feel free to tell me if something breaks or if you think something should be added/changed.
Note - this works using the latest dev version of the datascience repository...it may break on earlier versions...
Feel free to ping others about this if they'd be interested

There is also the datascience API documentation at
http://data8.org/datascience/ — this should be linked to in the README in
the datascience repo but isn't. The tutorial isn't written as of yet but
the reference section is helpful.
On Wed, Dec 16, 2015 at 2:17 PM Chris Holdgraf<EMAIL_ADDRESS>wrote:

Hi @dsten/instructors https://github.com/orgs/dsten/teams/instructors
(esp @cboettig https://github.com/cboettig ) - a few people mentioned
some confusion about the Table object that was created for the course.
There's isn't any documentation out there on how to use it, so I wrote a
quick reference guide on how to do things with a Table. It's modeled after
the "10 minutes to pandas" tutorial, though it doesn't assume anything
Pandas-specific.
Link: 10 minutes to tables
https://github.com/choldgraf/write-ups/blob/master/misc/10_min_to_tables.ipynb
It's still in an incomplete state (in particular, I haven't figured out
I/O or pivot tables yet) but should have lots of useful information. It
might change if the datascience API changes, so feel free to tell me if
something breaks or if you think something should be added/changed.
Note - this works using the latest dev version of the datascience
repository...it may break on earlier versions...
Feel free to ping others about this if they'd be interested
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165264144
.

@choldgraf @SamLau95 Thanks, this is quite helpful.
Yes, the official documentation is quite handy too, but it's rather terse.  For instance, Table.where is documented as:
Table.where(column_or_label, value=None)[source]
Return a Table of rows for which the column is value or a non-zero value.

Which could leave some of us a bit confused on the use of inequalities & when to use a column or a label.  Of course this one covered quite nicely in the textbook, but the docs might benefit from some minimal examples showing the different use cases?

And there are several tutorial notebooks.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Wed, Dec 16, 2015 at 2:53 PM, Sam Lau<EMAIL_ADDRESS>wrote:

There is also the datascience API documentation at
http://data8.org/datascience/ — this should be linked to in the README in
the datascience repo but isn't. The tutorial isn't written as of yet but
the reference section is helpful.
On Wed, Dec 16, 2015 at 2:17 PM Chris Holdgraf<EMAIL_ADDRESS>wrote:

Hi @dsten/instructors https://github.com/orgs/dsten/teams/instructors
(esp @cboettig https://github.com/cboettig ) - a few people mentioned
some confusion about the Table object that was created for the course.
There's isn't any documentation out there on how to use it, so I wrote a
quick reference guide on how to do things with a Table. It's modeled
after
the "10 minutes to pandas" tutorial, though it doesn't assume anything
Pandas-specific.
Link: 10 minutes to tables
<
https://github.com/choldgraf/write-ups/blob/master/misc/10_min_to_tables.ipynb
It's still in an incomplete state (in particular, I haven't figured out
I/O or pivot tables yet) but should have lots of useful information. It
might change if the datascience API changes, so feel free to tell me if
something breaks or if you think something should be added/changed.
Note - this works using the latest dev version of the datascience
repository...it may break on earlier versions...
Feel free to ping others about this if they'd be interested
—
Reply to this email directly or view it on GitHub
<
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165264144
.

—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165273879
.

Thanks for the link @SamLau95, I'm going to add it to the top of the 10 minutes notebook. @cboettig and I spent some time trying to find comprehensive and quick tutorials but couldn't find one, which is why I wrote this. Apologies if it's replicating something else that's out there, but I am more than happy to contribute to the main repository if people find it useful.

No, this is very helpful — writing a full tutorial is at the top of our
TODO list but no one has taken it on yet.
https://github.com/dsten/datascience/issues/150
On Wed, Dec 16, 2015 at 5:00 PM Chris Holdgraf<EMAIL_ADDRESS>wrote:

Thanks for the link @SamLau95 https://github.com/SamLau95, I'm going to
add it to the top of the 10 minutes notebook. @cboettig
https://github.com/cboettig and I spent some time trying to find
comprehensive and quick tutorials but couldn't find one, which is why I
wrote this. Apologies if it's replicating something else that's out there,
but I am more than happy to contribute to the main repository if people
find it useful.
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165304363
.

Cool. Well, let me know if there's a way I can change the formatting of this document to either be complimentary to a full tutorial or to contribute material to the tutorial itself.

If you make changes to the tutorial.rst file they'll automatically get pulled onto the online docs when it gets merged into master.
Alternatively, you can keep working on the notebook and I can pull in the text into the file. Let me know what you'd prefer.

ah ok cool - I'll take a look at the .rst file and see how easy it would be
to transfer over what's there now for a tutorial. Maybe I'll keep
developing the notebook, and then we can decide when it's good enough and
I'll transfer to the text file. Sounds good?
On Wed, Dec 16, 2015 at 10:06 PM, Sam Lau<EMAIL_ADDRESS>wrote:

If you make changes to the tutorial.rst
https://github.com/dsten/datascience/blob/master/docs/tutorial.rst file
they'll automatically get pulled onto the online docs when it gets merged
into master.
Alternatively, you can keep working on the notebook and I can pull in the
text into the file. Let me know what you'd prefer.
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165350078
.

Yup, great. Thanks!
On Thu, Dec 17, 2015, 9:27 AM Chris Holdgraf<EMAIL_ADDRESS>wrote:

ah ok cool - I'll take a look at the .rst file and see how easy it would be
to transfer over what's there now for a tutorial. Maybe I'll keep
developing the notebook, and then we can decide when it's good enough and
I'll transfer to the text file. Sounds good?
On Wed, Dec 16, 2015 at 10:06 PM, Sam Lau<EMAIL_ADDRESS>wrote:

If you make changes to the tutorial.rst
https://github.com/dsten/datascience/blob/master/docs/tutorial.rst
file
they'll automatically get pulled onto the online docs when it gets merged
into master.
Alternatively, you can keep working on the notebook and I can pull in the
text into the file. Let me know what you'd prefer.
—
Reply to this email directly or view it on GitHub
<
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165350078
.

—
Reply to this email directly or view it on GitHub
https://github.com/dsten/connector-instructors/issues/1#issuecomment-165521364
.


[ci-skip] Add note in the README to refer to user's version for available methods

Lot of people assume that all methods in the README on master branch are available. Examples are #496 and #505. Add a small note upfront saying that they should refer to README of their version and not the master branch.
Closes https://github.com/stympy/faker/issues/496 and https://github.com/stympy/faker/issues/505

+1


[SPARK-5214][Core] Add EventLoop and change DAGScheduler to an EventLoop

This PR adds a simple EventLoop and use it to replace Actor in DAGScheduler. EventLoop is a general class to support that posting events in multiple threads and handling events in a single event thread.

cc @rxin

Test build #25466 has started for   PR 4016 at commit 3b2e59c.

This patch merges cleanly.

Test build #25468 has started for   PR 4016 at commit 1f73eac.

This patch merges cleanly.

Test build #25466 has finished for   PR 4016 at commit 3b2e59c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class EventLoop[E](name: String) extends Logging

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25466/
Test PASSed.

Test build #25468 has finished for   PR 4016 at commit 1f73eac.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class EventLoop[E](name: String) extends Logging

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25468/
Test FAILed.

Jenkins, retest this please.

Test build #25469 has started for   PR 4016 at commit 1f73eac.

This patch merges cleanly.

Test build #25469 has finished for   PR 4016 at commit 1f73eac.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class EventLoop[E](name: String) extends Logging

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25469/
Test PASSed.

Looks pretty good to me. Since it is an important component, might be worth getting more pairs of eyes to look at it.
cc @aarondav, @kayousterhout, @markhamstra

Yes, of course, we can do this -- it's more-or-less going back to what we had before: https://github.com/apache/spark/commit/2539c0674501432fb62073577db6da52a26db850
I'm not seeing a lot of discussion about why we are considering this and the broader replacement of Akka.  Is there some more discussion or motivation than what appears in the two JIRAs, SPARK-5124 and SPARK-5214?

We are not removing Akka or considering removing Akka yet. It is just building it in a way that we can remove the dependency if we want to in the future. If we do consider, we will definitely have a broader discussion. If we ever do that, it'd be for making networking easier (both debugging and deployment), and enabling our users to use Akka (using Akka, especially a different version of it for an app on top of Spark is a mess right now. Spark not depending on Akka will make it easier for applications on top of Spark to use Akka).

BTW I'm not sure why we ever did https://github.com/apache/spark/commit/2539c0674501432fb62073577db6da52a26db850 in the first place, other than making things more Scala-y.

I hope that this is the beginning of a long, drawn-out series of commits that Akka-ize and de-Akka-ize various components of Spark, followed by the short but bloody Holy Akka Crusades, ultimately resulting in a complete rewrite of Spark in Erlang.

Test build #25526 has started for   PR 4016 at commit 227bf33.

This patch merges cleanly.

FWIW My memory is that the original motivation for Akkaifying the DAGScheduler was consolidation: better not to have many redundant event loop implementations in the Spark code base.

On Jan 14, 2015, at 12:14 AM, Aaron Davidson<EMAIL_ADDRESS>wrote:
I hope that this is the beginning of a long, drawn-out series of commits that Akka-ize and de-Akka-ize various components of Spark, followed by the short but bloody Holy Akka Crusades, ultimately resulting in a complete rewrite of Spark in Erlang.
—
Reply to this email directly or view it on GitHub.

Test build #25529 has started for   PR 4016 at commit 460f7b3.

This patch merges cleanly.

Ok now we have a single EventLoop implementation :)

This seems simpler to me than understanding the relationship between actors and supervisors, as well as restart strategies, but I am not sure it's a sufficient improvement in that regard to warrant refactoring this rather fundamental piece of Spark code.
The benefit of removing the sole usage of Supervisors from Spark core is offset by the fact that we still use Actors for the sake of event loops everywhere else. Perhaps converting the rest into event loops would be easier than making them properly hierarchical actors with supervisors, thus making this the first in a set of eventual rewrites, but that is a higher level discussion that should be had.

Test build #25534 has started for   PR 4016 at commit 5cfac83.

This patch merges cleanly.

Test build #25526 has finished for   PR 4016 at commit 227bf33.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25526/
Test FAILed.

Test build #25529 has finished for   PR 4016 at commit 460f7b3.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25529/
Test FAILed.

Test build #25534 has finished for   PR 4016 at commit 5cfac83.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25534/
Test PASSed.

LGTM, code-wise. You might run the unit tests many times locally to try to find race conditions. For similar situations, I've used something like
echo START: `date` > run_log; while sbt/sbt 'core/test-only *EventLoopSuite'; do echo SUCCESS: `date` >> run_log; done; echo FAILED: `date` >> run_log

and just let it run for a while.

echo START: date > run_log; while sbt/sbt 'core/test-only *EventLoopSuite'; do echo SUCCESS: date >> run_log; done; echo FAILED: date >> run_log

Cool. Ran it 10 minutes in my machine and it was sucessful.

Test build #25630 has started for   PR 4016 at commit aefa1ce.

This patch merges cleanly.

Test build #25630 has finished for   PR 4016 at commit aefa1ce.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25630/
Test PASSed.

I think if we have a stated goal of moving away from akka (which would eventually move all of our event loops into this structure) then it makes some sense to do it incrementally. For me this is the main long term goal here, but not something we've really discussed much as a project. So maybe we keep this on ice and try to get some consensus on that goal, and if we do all want to go that direction, we can consider this as part of an incremental roll out.

Thanks. Merging in master.


Moves request error handling to user api request

The idea behind this refactor is to extract error cases that were inside the ApiRequest type (namely as the ActionInappropriate and PayloadParseError constructors).
Now this error cases are handled by the userApiRequest that returns an Either ApiRequestError ApiRequest.
The type ApiRequestError has a function inside the error module that converts this type into an HTTP response. This function is used in the postgrest function making the app function slightly simpler as well.

Thank you!


Bower archiver seems down / malfunctioning

 Issue by addyosmani
Thursday Oct 30, 2014 at 13:24 GMT
Originally opened as https://github.com/Polymer/polymer-dev/issues/125

After a few tries I was able to reproduce this locally. The output is ~ 22 bytes and doesn't contain the expected set of elements.
https://bowerarchiver.appspot.com/archive?paper-elements=Polymer/paper-elements

cc @ebidel in case this is a known issue.

Working for me and this is very old. Closing.


Add character:  to font:

Character :
Font :

Hey @manishdhakad12, I am interested in this issue, please assign it to me


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1091 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit d050d77:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-05-25-11-44-04 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update MD file on new branch 2017-30-13_02-11-20

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Can someone give me the previous injector and dll

This version has some problems.

Sir, I have a link to the old file here. You can open it and find the 13.24 version R3sk.
https://github.com/R3nzTheCodeGOD/R3nzSkin/releases

thanks

i forgot you could see the previews versions and their files haha.

Looks like the problem persists.


Sync numpy changes

ISTM the core Checker is basically the same (maybe numpy vs np in the namespace?), but the scaffolding did diverge somewhat.

Run on a numpy documentation, see what breaks.

[ ] skipdict instead of a skiplist : not needed, simpler with a full name instead of a name:method dict

https://github.com/numpy/numpy/pull/21962 for the POC numpy run.


textColor in the ArcGauge

hello, thanks for this good work of yours, but I can't find a way to change the text color of the value inside an ArcGauge.
I'm using a black background which makes the value not visible to the user.
thanks for your time

hello, thanks for this good work of yours, but I can't find a way to change the text color of the value inside an ArcGauge.
I'm using a black background which makes the value not visible to the user.
thanks for your time

Hi sorry for late response
currently for some unknow for me reason i forgot to set option to change text color
in future release I will fix this issue
I will remain this issue open

Hi
in new release 0.3.0
u have option to set you custom value color
Best Regards
Gruzer


Enable toggling of timeline streams using a Dart C API method (to be used in release builds)

Add a new Dart C API method that allows toggling of the following timeline streams in the VM
V(API, "dart:api")
V(Compiler, "dart:compiler")
V(CompilerVerbose, "dart:compiler.verbose")
V(Dart, "dart:dart")
V(Debugger, "dart:debugger")
V(Embedder, "dart:embedder")
V(GC, "dart:gc")
V(Isolate, "dart:isolate")
V(VM, "dart:vm")

This API method would provide functionality similar to the 'setVMTimelineFlags' rpc method supported in the service protocol.
In this model the embedder would always have 'systrace_timeline' enabled by default in the release build but all the streams would be disabled and it could then toggle the individual streams at runtime to collect timeline traces.

/cc @rmacnak-google @bkonyi @xster @dnfield

Also cc @christianedwardpadilla.

In this model the embedder would always have 'systrace_timeline' enabled by default in the release build

This might be an implementation detail, but the desired capabilities are:

Be able to take a release build locally or on CI, and run it with a VM flag before the VM starts to globally enable timeline traces for the process
Be able to take a release build (in production). There is no awareness of whether the traces will be toggled on during the process but depending on user actions, the traces will be turned on and off through the above APIs.

The 2 scenarios currently have no overlap. So there's some flexibility in terms of the API design.

https://dart-review.googlesource.com/c/sdk/+/219860


Smoketest: search tests are failing

All 4 search tests are timing out for me:

Search
** Timeout!
Error: Element not found: div[id="workbench.view.search"].search-view .search-widget .search-container .monaco-inputbox input

Has this selector been updated?

Are you sure you ran the tests from the latest release/1.30 and built them? Should be fixed already: https://github.com/Microsoft/vscode/blob/release/1.30/test/smoke/src/areas/search/search.ts#L10


infinite loading and other issue

so ive used this for a while and ive seen 2 issues, one has just recently arisen where out of nowhere, whenever I went into the site,  it would put me into an infinite loading screen, I am on chromebook if that helps but like I said this just started happening (I never used it on any other device) so yeah. The other issue was that sometimes, the messages wouldnt update and you would have to reload the site, this happens consistently when using gifs and sometimes when not.

Hello, thanks for creating this issue. The website is currently hosted on a very cheap VPS and it has run out of storage. Hence the Infinite loading.
I am not sure about the messages not updating, could you please elaborate

The website is now working as intended


Updating all the icons of tools according to the theme

Update all the icons of the tool which is being used according to the rest of the icons which are there from previous versions.

Icons to be changed :-

Import project
Download pdf
Close project
Cut
Copy
Paste
Select all
Equations
Images
Tables
Date
Link
Tab space
Increase size
Decrease size
Increase Indentation
Decrease Indentation
Resize image
Voice typing
Cloud sync
User Guide
Linux
Windows
Tutorial
Keyboard shortcuts
Check for updates
About Udaan PE

Steps to proceed further :-

We already have icons on resources folder which are in white color
You have to change that color to #050441 hex value using LunaPic Editor , after uploading the white icon go to "Adjust" in LunaPic and select "Replace Color" and then put the given hex value there
After that go to the Canva Nishant Canva logo editor
Copy above logo and then Paste it in your own canva project
Upload that color changes icon and place it properly in the center and after that add elements to give shadow effect with shadow color #bdbebe
After that download the created icon
The upload it to LunaPic again
After uploading go to edit and transparant background and click on white color which is in background
Now resize the image by going to Edit -> Resize Image and then resize that image 512 x 512 px format
Your icon is ready now
Replace that to the resource folder properly with same name as previous

Abhinav == From icon number 1 to 6
Saanvi == From icon number 7 to 12
Aayush == From icon number 13 to 18
Nishant == Remaining

Completed by @AayushGupta69 and @saanvibehele at commits :- a2a88b06fea0f2321881a20c3b7f43441a90b49c, 30fc92335cbfdad098c9f7221d51f9fad3bf7368


docs: cleanup value_string reference

Short description of the changes
Updates the note about in and not-in to reference value instead of value_string (which is deprecated)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (58f54fc) 81.01% compared to head (1e23b3f) 81.01%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #409   +/-   ##
=======================================
  Coverage   81.01%   81.01%
=======================================
  Files          62       62
  Lines        4840     4840
=======================================
  Hits         3921     3921
  Misses        763      763
  Partials      156      156

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Rails 6.1 compatibility

Adds an override to ActiveRecord update method to set the dynamic attributes, since update_attributes methods are deprecated in Rails 6.1.

Hi! Thanks for your PR! Unfortunately, I haven't maintained this gem in 11 years though and I'm not using it anymore.
That being said, it's fine with me to merge this, although I don't think I will be able to release a new version because of this. Please let me know if this is ok. If you like I can also make you a collaborator, so you can push changes yourself.

Thanks for your fast reply!
We have been using this gem for several years 👏 . Now we are upgrading our application and we need this fix to keep it working as it was.
Actually, we've already discussed/planned to replace the gem in the future after the upgrade, so it's not a big problem to use the fork we've created in meantime 🙂 👍 .


Minor Cleanups and added draft of design doc

Design doc that covers the difference between GISCUP 2019 and 2020.
Fixed some formatting.
Setup .gitignore for IntelliJ

Pull Requests to wrong repository. Closing.


Merge to live 2022-05-18

No detected changes to .json files in the root

OPS passed, this can merge.


Add ability to avoid rendering MessageTemplate

Does this issue relate to a new feature or an existing bug?

[ ] Bug
[x] New Feature

It would be great to be able to disable the rendering of MessageTemplate in ElasticsearchJsonFormatter the same way we can avoid to render the message see here

Merged


Some trouble with fmriprep-docker

The following command gives me the error  below. Any insights would be great to have.
See 'docker run --help'.
Could not detect memory capacity of Docker container.
Do you have permission to run docker?

OK, fix was just to repull the image (the app was probably not added to the docker group. Thanks @effigies  .


#58 Test app

a test for better coverage

Current coverage is 95.57% (diff: 100%)

Merging #251 into master will increase coverage by 0.19%

@@             master       #251   diff @@
==========================================
  Files            54         54
  Lines          1667       1673     +6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1590       1599     +9
+ Misses           77         74     -3
  Partials          0          0

Powered by Codecov. Last update f096a17...c1eb392

Sorry,  I did not realize I crated a branch from another branch and not from master. It's just couple of lines, is it OK if I make another pull request?

sure no problem. If the branch would be created from master we would also avoid this conflict ;) Dont worry about it know, just remember for the future ;) Please fix the conflict so we can merge it.

There is still TODO.


Pre poc

Update ETT -> 3.0.1
DSW prefix
PoC DSW link on pre-considerations page

As I understood the<EMAIL_ADDRESS>way of presentation would be better?
https://korbinib.github.io/pages/support_00_planning_considerations


Is HHVM actually supported?

The PHP version of WhichBrowser for use on a server. Fully compatible with PHP 5.4 or higher, including PHP 7 and HHVM.

Numerous projects are starting to drop HHVM support (at least newer releases of HHVM) because of it as it's moving towards supporting Hack
https://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html
I question this as there's no testing on travis, so is it more it just incidentally works, rather than supported?
It might be worth removing the "and HHVM" part from the readme :)

I just noticed https://github.com/WhichBrowser/Parser-PHP/commit/04c0680870d24fadfab0fe156156b5f9eaa784e1
Will do a PR to update the README


[Joy][Select] Does not re-render Options when changing text

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/charming-haibt-77i9q0?file=/demo.tsx
Steps:

Click on the button many time flipping the state --> which updates the text within the Options
E.g. you should see "Dog" and "❤ Dog", alternating, in the Select
You will see that it does NOT get reflected in the Select component
However, clicking the Select will immediately refresh the displayed element and open the menu

Current behavior 😯
Clicking the button does not update the text in the Select component.

Expected behavior 🤔
Clicking the button should toggle between "DOG" and "❤ Dog" (or any other animal)

Context 🔦
In my application, state is mutated and options will change (in text, not key or quantity), but it's not reflected in the UI.
First mentioned in https://github.com/mui/material-ui/pull/35946#issuecomment-1543239322, not necessarily related.
The workaround currently is to revert to Joy Alpha-75 and fix the version in the package.json.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 18.15.0 - C:\p\apps\nodejs\node.EXE
    Yarn: Not Found
    npm: 9.5.0 - C:\p\apps\nodejs\npm.CMD
  Browsers:
    Chrome: 113.0.5672.93
    Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.35)
  npmPackages:
    @emotion/react: ^11.11.0 => 11.11.0
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-alpha.125
    @mui/core-downloads-tracker:  5.13.0
    @mui/icons-material: ^5.11.16 => 5.11.16
    @mui/joy: 5.0.0-alpha.75 => 5.0.0-alpha.75
    @mui/material:  5.13.0
    @mui/private-theming:  5.12.3
    @mui/styled-engine:  5.12.3
    @mui/system:  5.12.3
    @mui/types:  7.2.4
    @mui/utils:  5.12.3
    @types/react: ^18.2.6 => 18.2.6
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.0.4 => 5.0.4

I'm picking this up

@enricoros I've updated code to re-render Select when options in below sandbox, can you try and let me know if it is according to your expectations.
https://codesandbox.io/s/great-breeze-2xc1wc?file=/demo.tsx

@sai6855 this seems exactly according to expectations! Good job in fixing it!

@sai6855 Thanks a lot!


I18n

refers to #75
uses next-intl
locale auto-detected from user's browser by default
supported locales (in this PR):

en-US (fallback)
fi

locale used for number formatting
locale used for currency symbol positioning
changed locale is stored into a cookie
URL paths are not changed so old shared URLs keep working
easy to add a new locale:

create new file messages/LOCALE.json
add locale to src/i18n.ts

@iqqmuT This is so amazing! Let me review and test everything and let's get it merged! Internationalization is the # 1 asked feature for Spliit 🤩


feat: Webhook

For Data Pipelines there is often a requirement that systems external to Optimus expect notification/nudge upon job state change. This helps people trigger external routines.
HTTP webhooks are supported.
On Events:

Job Fail
Job Success
SLA Miss

Metrics Tracked :

webhook request failures count
webhook request success count

Can we add documentation in this pr or next for this feature.


Shared metric vs. specific metrics

Hi all,
Got a question related to data modelling... in our system we have several metrics that measure time. For example, we measure the time it takes to load a video player and we also measure the time it takes for the video to start playing. The former exists only in 'player load' events, while the later exists only in 'play started' events (=we never have both metrics together).
One way to model it is to create two metrics, one for each, and another approach is to have a single metric that changes its meaning according to the event type.
I'm wondering whether there are performance implications to this decision, will a shared metric take less space/be more efficient than multiple metrics?
Thanks,
Eran

@erankor it sounds either approach produces same number of rows if i understand correctly. less rows, better performance.

Thanks @kaijianding, yes, the number of rows will be the same.


[Question] Is Osiris all in all already have inbuilt protection from pattern scanning by VAC?

If not, then is DLL virtualization protection required? I usually use VMProtect for this hide my dlls. But please recommend any software that are better than VMProtect.

No not needed and never will be implemented. There are better ways to prevent VAC from working. Check the other Repos.

Technically you won't need too. You can still use VMProtect if you want too. Check here for more details: https://github.com/BohanRen/Osiris/blob/master/Osiris/AntiDetection.cpp

hmm @VuBrian22 it is possible to remove PE Header at injection time, where the injector already opened the DLL you can remove the header upfront. But this doesn't protect from signature scans!

Yeah ig @0xE232FE ,however signatures of the cheat i don't think are rlly a big problem. The signatures of a potentially detected injector are a big problem. Reference: https://github.com/danielkrupinski/Osiris/issues/681#issuecomment-544263343

@VuBrian22, if you're getting VACed from an injector try making your own or heavily modify an open source injector

@VuBrian22 Can you recommend me any open source injector? I used the CSGO injector made by T-800 on MPGH, I'm kinda afraid to use Extreme Injector since its a popular injector to use.

i don't know why this discussions come up every time. osiris is a really good base, it's fantastic. thanks @danielkrupinski ... every source that is available public will get detectet sooner or later. Don't compile and inject without modifying the whole sourcecode. Second big part is, don't use public injectors like Extreme Injector. Make your own, if you can't ... DarthTon Xenos Injector is a really good base. Same thing here, modify whole sourcecode befor you even think about inject something.
Finally: Watch the code and how this injectors work. It took me a long time to understand what they do.
A simple loadlibrary injection is done fast. There are many examples out there. I personally prefer manual mapping. Cause i think it is cleaner. What i do:
Get Base Adresses / Handles of csgo.exe, check if following dll's are loaded: client_panorama.dll, engine.dll, After that inject, otherwise csgo maybe crashs. A sleep or timeout is not a good choice.
After that, stream your dll directly to memory. Map dll from memory. Erase PE-Header. Done.
I do this since 2015 without any detections. My skills are not really good, im no developer, just trying to understand what the professionall devs do ;)

I'm keen on learning, can you please give me some information or souce how
to modiy the source code, or modify an existing injector?
On Wed, Oct 30, 2019, 10:27 PM steel4me<EMAIL_ADDRESS>wrote:

i don't know why this discussions come up every time. osiris is a really
good base, it's fantastic. thanks @danielkrupinski
https://github.com/danielkrupinski ... every source that is available
public will get detectet sooner or later. Don't compile and inject
without modifying the whole sourcecode. Second big part is, don't use
public injectors like Extreme Injector. Make your own, if you can't ...
DarthTon Xenos Injector is a really good base. Same thing here, modify
whole sourcecode befor you even think about inject something.
Finally: Watch the code and how this injectors work. It took me a long
time to understand what they do.
A simple loadlibrary injection is done fast. There are many examples out
there. I personally prefer manual mapping. Cause i think it is cleaner.
What i do:
Get Base Adresses / Handles of csgo.exe, check if following dll's are
loaded: client_panorama.dll, engine.dll, After that inject, otherwise csgo
maybe crashs. A sleep or timeout is not a good choice.
After that, stream your dll directly to memory. Map dll from memory. Erase
PE-Header. Done.
I do this since 2015 without any detections. My skills are not really
good, im no developer, just trying to understand what the professionall
devs do ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielkrupinski/Osiris/issues/678?email_source=notifications&email_token=AK7PVCH2676BUJUNGRKP2HDQRGKWFA5CNFSM4JCEC6SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECUMMFA#issuecomment-547931668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7PVCFKJPXPR7WVGVYOL7DQRGKWFANCNFSM4JCEC6SA
.

I'm keen on learning, can you please give me some information or souce how to modiy the source code, or modify an existing injector?
…
On Wed, Oct 30, 2019, 10:27 PM steel4me @.***> wrote: i don't know why this discussions come up every time. osiris is a really good base, it's fantastic. thanks @danielkrupinski https://github.com/danielkrupinski ... every source that is available public will get detectet sooner or later. Don't compile and inject without modifying the whole sourcecode. Second big part is, don't use public injectors like Extreme Injector. Make your own, if you can't ... DarthTon Xenos Injector is a really good base. Same thing here, modify whole sourcecode befor you even think about inject something. Finally: Watch the code and how this injectors work. It took me a long time to understand what they do. A simple loadlibrary injection is done fast. There are many examples out there. I personally prefer manual mapping. Cause i think it is cleaner. What i do: Get Base Adresses / Handles of csgo.exe, check if following dll's are loaded: client_panorama.dll, engine.dll, After that inject, otherwise csgo maybe crashs. A sleep or timeout is not a good choice. After that, stream your dll directly to memory. Map dll from memory. Erase PE-Header. Done. I do this since 2015 without any detections. My skills are not really good, im no developer, just trying to understand what the professionall devs do ;) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#678?email_source=notifications&email_token=AK7PVCH2676BUJUNGRKP2HDQRGKWFA5CNFSM4JCEC6SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECUMMFA#issuecomment-547931668>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK7PVCFKJPXPR7WVGVYOL7DQRGKWFANCNFSM4JCEC6SA .

That is your part now, you got so many informations. May the force be with you.


Univariate regression

Add univariate regression model from alan-turing-institute/sktime in order to provide predictions from the model.

This is resolved in:
817e236261cc1f28db5df7f908e12ed56c017d25


Cask 'pycharm' definition is invalid: Bad header line: parse failed

$ brew-cask search pycharm
==> Exact match
pycharm
==> Partial matches
pycharm-ce   pycharm-edu

$ brew-cask install pycharm
Error: Cask 'pycharm' definition is invalid: Bad header line: parse failed

any hint on how to fix this?!

I had a similar issue with a different package. brew doctor reported this:
Warning: You have external commands with conflicting names.

Found command `brew-cask` in following places:
    /usr/local/bin/brew-cask
    /usr/local/Library/Taps/caskroom/homebrew-cask/cmd/brew-cask.rb

I removed the first one (rm /usr/local/bin/brew-cask) and things seem to work now.

Run:
brew update; brew cleanup; brew cask cleanup
brew uninstall --force brew-cask; brew update

and retry.

Also, do this.

brew cask list
Error: Cask 'atom' definition is invalid: Bad header line: parse failed

It seems the same problem

It seems the same problem

It is, we know the cause. It’s not a bug, it’s an update to how we do things. Just run what @adityadalal924 said, and it’ll be fine. Details here.

@vitorgalvao We're might get a lot of issues about this because of the combination of moving to tap cmd and the cask header update (if people don't read).
Here's a copy pastable reply:

This error is not a bug, it's caused by an update to how homebrew-cask works. Details can be found here.
To fix the issue, please run:
brew update; brew cleanup; brew cask cleanup
brew uninstall --force brew-cask; brew update

If you are still having problems, open an issue with the appropriate template

Good call. Added as a textexpander snippet.

top, thx!

brew uninstall --force brew-cask; brew update and install package again! :+1:

very good way!!!

samdeMBP:~ sam$ brew update; brew cleanup; brew cask cleanup; brew uninstall --force brew-cask; brew update
Already up-to-date.
Error: Could not link phinze/cask manpages to:
/usr/local/share/man/man1/brew-cask.1
Please delete these files and run brew tap --repair.
Warning: Skipping phinze/cask/brew-cask: most recent version 0.60.0 not installed
Warning: Skipping docker-compose: most recent version 1.5.2 not installed
Warning: Skipping docker-machine: most recent version 0.5.4 not installed
Warning: Skipping go: most recent version 1.5.2 not installed
Warning: Skipping libgpg-error: most recent version 1.21 not installed
Warning: Skipping openssl: most recent version 1.0.2e not installed
Warning: Skipping pkg-config: most recent version 0.29 not installed
Warning: Skipping scons: most recent version 2.4.1 not installed
Warning: Skipping sqlite: most recent version 3.9.2 not installed
Warning: Skipping subversion: most recent version 1.9.2 not installed
Warning: Skipping wget: most recent version 1.17.1 not installed
Warning: Skipping xz: most recent version 5.2.2 not installed
Removing: /Library/Caches/Homebrew/docker-compose-1.5.1.el_capitan.bottle.tar.gz... (876K)
Removing: /Library/Caches/Homebrew/docker-compose-1.5.1.tar.gz... (184K)
Removing: /Library/Caches/Homebrew/docker-machine-0.5.1.el_capitan.bottle.tar.gz... (39M)
Removing: /Library/Caches/Homebrew/dockertoolbox-1.8.1.pkg.incomplete... (16K)
Removing: /Library/Caches/Homebrew/go-1.5.1.el_capitan.bottle.tar.gz... (66M)
Removing: /Library/Caches/Homebrew/go-1.5.1.tar.gz... (11M)
Removing: /Users/sam/Library/Logs/Homebrew/docker-compose... (9 files, 100K)
Removing: /Users/sam/Library/Logs/Homebrew/go... (4 files, 220K)
==> Removing dead symlinks
Nothing to do
==> Removing cached downloads
Nothing to do
Uninstalling brew-cask... (2634 files, 10M)
Already up-to-date.
samdeMBP:~ sam$ brew cask list
baiducloud   betterzip	  flash	       qqmusic	    virtualbox	 xiami

@huguiqi You also have the old cask tap installed. Run
$ brew untap phinze/cask; brew untap caskroom/cask; brew update
Also locking this issue. Please open up a new one if there are any further problems.


OnClick not working right after swipe

Hello.
Except for the following situations, the onClick event of the swipe item is ignored.
1.Click the item about 1 second after swipe
2. Double-click the item after swipe
[Development/test environment]
react: 16.13.1,
react-slick: 0.27.10,
mobile: android for chrome85

@SungYoun i had the same issue as u and figured out that it has been fixed in this commit https://github.com/akiran/react-slick/commit/f958da53d1f25e29bb43b5b7ad222621342092d8
Just upgrade the package and it shall be fine.


Use two-step dispatch to SyntaxVisitor.vistImpl

SyntaxRewriter has had a problem with stack allocation space for a while because cases in a switch statement don’t share stack space in debug builds (rdar://55929175). We started seeing this issue with SyntaxVisitor as well now. Use the same approach to fix the problem:
To circumvent this problem, make calling the specific visitation function a two-step process: First determine the function to call in this function and return a reference to it, then call it. This way, the stack frame that determines the correct visitation function will be popped of the stack before the function is being called, making the switch's stack space transient instead of having it linger in the call stack.
And to make the entire approach look sane, allow 4 arguments on the same line for SyntaxVisitor instead of the 3 that we allow in all other files.

@swift-ci Please test

@swift-ci Please test

@swift-ci please test Windows