Go: Attachment type should represent data with an io.Reader

Currently the WriteAttachment function expects a byte slice, which unnecessarily requires the writer to materialize the attachment. Also, we currently have symmetry between the Write* and Parse* functions - they accept/return the same types.
To solve the problem with WriteAttachment, it would be most natural to have the data field of the Attachment type valued with a reader instead of a byte slice. However, to maintain the current symmetry it would become required to add some instructions to the ParseAttachment function (which would presumably return an attachment reader backed by the underlying input reader) that the value of the "data" field must be consumed prior to reading the next record (previously the parse call itself would consume it). This isn't required for other record types, so introduces a bit of new mental overhead.
This will be a breaking change to the SDK, but hopefully not a difficult one to navigate for anyone using attachment support.

Thinking about this in a little more detail, my impulse is,

Remove the public ParseAttachment function
Change the Data field of the Attachment type to be an io.Reader
Add to the LexerOptions an optional func(*Attachment) error callback
Add support for mirroring that in the reader configuration (will require some notion of reader options)
In the lexer, if a callback is supplied, use that to stream-handle attachments. Otherwise discard the appropriate number of bytes.
Change the Writer to also handle stream writes of attachment content using the new Reader-valued data field.

The complication with this is CRCs. I do not think there is a reasonable way for us to represent the CRC in the Attachment type while also converting the Data field to a reader. The reasons are,

On the write side, when supplying an io.Reader as data, the computed CRC to write to the file is not known until your reader has been traversed. It can't be supplied up-front to the WriteAttachment function.
On the read side, if you are supplying an onAttachment callback, that function is going to do something with the attachment content (e.g copy to remote storage) before it reaches the CRC. If you care about CRC validation you would ideally want to roll back your callback's operation if the CRC you compute after traversing the content fails to verify.

The solution to the first of these issues seems simple - just remove the CRC from the attachment type and have the writer handle it for the user transparently. However, the second issue is more of a gap. Taking the example of wanting to write attachments to remote storage, you would want to supply some kind of attachment callback like this:
func(a *Attachment) error {
   writer, err := NewCloudStorageWriter("attachments-bucket", "path derived from a.Name")
   if err != nil {
     return err
   }

  _, err = io.Copy(writer, a.Data)
  if err != nil {
    return err
  }

  err = writer.Close()
  if err != nil {
    return err
  }

  return nil
}

However, in this example writer.Close() is going to finalize your write to storage. If you care about CRCs, and the CRC failed to verify after you read a.Data, you would not want that to happen. And if the Attachment type no longer has the CRC attached to it, you are no longer in position to act on the attachment's stated CRC from within this callback. The lexer would need to consume that CRC after the callback is called. It could then do a validation and throw the error, but by that point you already wrote junk data to storage - it's too late.
One solution I see is to add to the attachment type a couple of methods, ParseCRC and ComputedCRC. The behavior of ParseCRC would be to read the attachment up to the CRC field and return the value of the field. The behavior of ComputedCRC would return a CRC computed from the initial fields and the consumed portion of the Data field. Users would need to avoid calling either function until they have done whatever they intend to do with a.Data, since the ParseCRC method will throw unconsumed data away and the ComputedCRC method would return an incorrect CRC until Data has been traversed. The callback for a user who wants to handle CRCs would then be this:
func(a *Attachment) error {
   writer, err := NewCloudStorageWriter("attachments-bucket", "path derived from a.Name")
   if err != nil {
     return err
   }

  _, err = io.Copy(writer, a.Data)
  if err != nil {
    return err
  }

  if a.ParseCRC() != a.ComputedCRC() {
    return ErrCRCMismatch
  }

  err = writer.Close()
  if err != nil {
    return err
  }

  return nil
}

the lexer that is invoking the callback can be in charge of ensuring that all bytes in the record are consumed whether or not the ParseCRC function is called. It already needs to do this to support theoretical addition of fields to the end of the record in a backward compatible way.
To support this, I think the eventual structure of the Attachment type becomes roughly this:
type Attachment struct {
	LogTime    uint64
	CreateTime uint64
	Name       string
	MediaType  string

	// CRC computing limit reader limited to length of the attachment data and initialized with crc of preceding fields
	Data crcReader

	// backing reader of Data, comprising Data portion + rest of record
	r io.Reader

	// CRC read off the end of r, zero until Data has been consumed
	parsedCRC uint32

	// has the CRC after Data been read yet
	crcParsed bool
}

func parseAttachment(r io.Reader) *Attachment {
	// read initial fields, return an attachment with data portion backed by CRC
	// reader initialized at CRC of initial fields
}

func (a *Attachment) ComputedCRC() uint32 {
	return a.Data.Checksum()
}

func (a *Attachment) ParseCRC() (uint32, error) {
	if a.crcParsed {
		return a.parsedCRC, nil
	}

	// discard any remaining bytes of data
	io.Copy(io.Discard, a.Data)

	crc, err := readUint32(a.r)
	if err != nil {
		return 0, err
	}
	a.crcParsed = true
	return crc, nil
}

I think that addresses the second of the original two issues, but it complicates the first one because writers should not need to care about supplying a crcReader for the Data portion - they just need an io.Reader. I think that can probably be addressed by changing splitting the current Attachment into two types: Attachment for writing (what we have today minus CRC) and AttachmentReader for reading (the thing described above). The signature of the callback for stream processing of attachments would then be func(*AttachmentReader) error.


List

@yongchand I did something wrong with your master branch. I re-uploaded this in my own branch. Sorry for that.

@kjhman21 Totally fine. Though a better PR title might be helpful to users?

@yongchand thanks! Updated.


I´m trying to generate nswag documentation with studio and command line and nswag tries to crash my laptop

As you can see, when I´m trying to execute nswag to generate some documentation of the simpliest web api, nswag is trying to crash my laptop.
In the screen shot you can see what im saying. .NET Host process are multiplying like a virus!!!
ApiNswag.zip
I left the project and i´m using it in my company apis with an older version and im trying to migrate from .net6 to .net8 and your library crashes and is not a clear migration manual from v13 to v14.
This is very dissapointing

This might be due to recursive building. Do you have "nobuild": true in your nswag file to make sure nswag doesn't invoke itself?

Hi it worked but this is a serious bug. The memory of my laptop collapsed.

I'm glad it worked! Despite the appearances, this is not really a bug. There are quite a number of differences between NSwag 13 and 14 and you need to adapt the config files in consequence. There is a thread on top of the issues that details the difference, but the information is sadly scattered.
It's all a bit disappointing, but personally I stand by NSwag, since it's much better than that horrible Kiota.

Hello, experienced the same on macos. Could you attach doc with breaking changes for others and place, there I should add nobuild? I have several options: aspNetCoreToOpenApi, openApiToCSharpClient

You may want to have a look at https://github.com/RicoSuter/NSwag/issues/4865


Homepage tweak - Fundraisng image

We still have layout issues with the homepage but as a minimum before going live can we please move the fundraising image so we don't cut faces out please. Also have the same issue on the fundraising page
Thanks

Sorted


Got an internal_error after auth Gitlab

version : latest, 0.7
I follow the official installation guide to build the drone server.
Run docker using the following variables

#!/bin/bash
docker run -d
--dns {MY_OWN}
-e DRONE_GITLAB=true
-e DRONE_GITLAB_CLIENT={FROM_GITLAB}
-e DRONE_GITLAB_SECRET={FROM_GITLAB}
-e DRONE_GITLAB_SKIP_VERIFY=true
-e DRONE_GITLAB_URL=https://{PRIVATE_GITLAB}.com
-e DRONE_SECRET=0
-e DRONE_OPEN=true
-e DRONE_ADMIN={USER_NAME}
-v /var/lib/drone:/var/lib/drone
-P
--restart=always
--name=drone_latest
drone/drone:latest

And I can login my Gitlab successfully, but after I press the green access button.

It show me an interal_error

Here is my log:
eddler.Targets: column [user_remote] not found in struct
meddler.Targets: column [user_access] not found in struct
meddler.Targets: column [user_name] not found in struct
meddler.Targets: column [user_gravatar] not found in struct
meddler.Targets: column [user_syncing] not found in struct
meddler.Targets: column [user_created] not found in struct
meddler.Targets: column [user_updated] not found in struct
meddler.Targets: column [user_synced] not found in struct
meddler.Targets: column [user_access_expires] not found in struct
meddler.WriteTargets: column [user_remote] not found in struct
meddler.WriteTargets: column [user_access] not found in struct
meddler.WriteTargets: column [user_name] not found in struct
meddler.WriteTargets: column [user_gravatar] not found in struct
meddler.WriteTargets: column [user_syncing] not found in struct
meddler.WriteTargets: column [user_created] not found in struct
meddler.WriteTargets: column [user_updated] not found in struct
meddler.WriteTargets: column [user_synced] not found in struct
meddler.WriteTargets: column [user_access_expires] not found in struct
time="2017-07-07T01:24:23Z" level=error msg="cannot update bob.li. meddler.Update: DB error in Exec: no such column: user_expiry"
meddler.Targets: column [user_remote] not found in struct
meddler.Targets: column [user_access] not found in struct
meddler.Targets: column [user_name] not found in struct
meddler.Targets: column [user_gravatar] not found in struct
meddler.Targets: column [user_syncing] not found in struct
meddler.Targets: column [user_created] not found in struct
meddler.Targets: column [user_updated] not found in struct
meddler.Targets: column [user_synced] not found in struct
meddler.Targets: column [user_access_expires] not found in struct
meddler.WriteTargets: column [user_remote] not found in struct
meddler.WriteTargets: column [user_access] not found in struct
meddler.WriteTargets: column [user_name] not found in struct
meddler.WriteTargets: column [user_gravatar] not found in struct
meddler.WriteTargets: column [user_syncing] not found in struct
meddler.WriteTargets: column [user_created] not found in struct
meddler.WriteTargets: column [user_updated] not found in struct
meddler.WriteTargets: column [user_synced] not found in struct
meddler.WriteTargets: column [user_access_expires] not found in struct
time="2017-07-07T01:31:43Z" level=error msg="cannot update bob.li. meddler.Update: DB error in Exec: no such column: user_expiry"

Please use gitter.im/drone/drone for support

@bradrydzewski perhaps it would be beneficial to add a CONTRIBUTING.md file so that potential contributors know what is expected? https://help.github.com/articles/setting-guidelines-for-repository-contributors/
I'd be happy to make a PR if that would help.

@davecozz can you take a look at our issue template?

Ah, I see you have some instructions in there already. A big yellow banner might help weed out a little more noise but if people are already ignoring instructions, who knows.  ¯\_(ツ)_/¯


Problem with model graphsage

运行如下命令时报错：
python2 -m tf_euler --data_dir cnet --max_id 40012 --model graphsage --model_dir graphsage --batch_size 256 --learning_rate 0.01 --num_epochs 10  --dim 256  --mode train --log_steps 100 --aggregator mean
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0123 02:46:48.594172  3304 graph_builder.cc:59] Load Done: cnet/CausalNet.dat
I0123 02:46:50.339694  3304 graph_builder.cc:109] Done: build all sampler
I0123 02:46:50.339740  3304 graph_builder.cc:112] Graph build finish
WARNING:tensorflow:From /home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/layers.py:77: init (from tensorflow.python.ops.init_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.initializers.variance_scaling instead with distribution=uniform to get equivalentbehavior.
INFO:tensorflow:Create CheckpointSaverHook.
INFO:tensorflow:Graph was finalized.
INFO:tensorflow:Restoring parameters from graphsage/model.ckpt-0
INFO:tensorflow:Running local_init_op.
INFO:tensorflow:Done running local_init_op.
INFO:tensorflow:Saving checkpoints for 0 into graphsage/model.ckpt.
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/main.py", line 28, in
tf.app.run(run_loop.main)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 125, in run
_sys.exit(main(argv))
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line340, in main
run_local(flags_obj, run_network_embedding)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line303, in run_local
run(flags_obj, master='', is_chief=True)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line292, in run_network_embedding
run_train(model, flags_obj, master, is_chief)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line139, in run_train
sess.run(train_op)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 671, in run
run_metadata=run_metadata)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1156, in run
run_metadata=run_metadata)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1255, in run
raise six.reraise(*original_exc_info)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1240, in run
return self._sess.run(*args, **kwargs)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1312, in run
run_metadata=run_metadata)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/training/monitored_session.py", line 1076, in run
return self._sess.run(*args, **kwargs)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 929, in run
run_metadata_ptr)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1152, in _run
feed_dict_tensor, options, run_metadata)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1328, in _do_run
run_metadata)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1348, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Reshape cannot infer the missing input size for an empty tensor unless all specified input sizes are non-zero
[[node graphsage_1/sageencoder_1/Reshape_7 (defined at /home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/encoders.py:125)  = Reshape[T=DT_FLOAT, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](graphsage_1/sageencoder_1/GetDenseFeature_1, graphsage_1/sageencoder_2/Reshape_7/shape)]]
Caused by op u'graphsage_1/sageencoder_1/Reshape_7', defined at:
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/main.py", line 28, in
tf.app.run(run_loop.main)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 125, in run
_sys.exit(main(argv))
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line340, in main
run_local(flags_obj, run_network_embedding)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line303, in run_local
run(flags_obj, master='', is_chief=True)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line292, in run_network_embedding
run_train(model, flags_obj, master, is_chief)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/run_loop.py", line107, in run_train
_, loss, metric_name, metric = model(source)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/layers.py", line 62, in call
outputs = self.call(inputs)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/models/base.py", line 99, in call
embedding = self.target_encoder(src)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/models/graphsage.py", line 58, in target_encoder
return self._target_encoder(inputs)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/layers.py", line 62, in call
outputs = self.call(inputs)
File "/home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/encoders.py", line125, in call
h = aggregator((hidden[hop], tf.reshape(hidden[hop + 1], neigh_shape)))
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 6482, in reshape
"Reshape", tensor=tensor, shape=shape, name=name)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/util/deprecation.py", line 488, in new_func
return func(*args, **kwargs)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 3274, in create_op
op_def=op_def)
File "/home/zyli/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1770, in init
self._traceback = tf_stack.extract_stack()
InvalidArgumentError (see above for traceback): Reshape cannot infer the missing input size for an empty tensor unless all specified input sizes are non-zero
[[node graphsage_1/sageencoder_1/Reshape_7 (defined at /home/zyli/.local/lib/python2.7/site-packages/tf_euler/python/encoders.py:125)  = Reshape[T=DT_FLOAT, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:CPU:0"](graphsage_1/sageencoder_1/GetDenseFeature_1, graphsage_1/sageencoder_2/Reshape_7/shape)]]
应该是encoders.py:125报错，cannot infer the missing input size for an empty tensor unless all specified input sizes are non-zero. 我对tensorflow不熟悉，请问该怎么修复？

@yangsiran 已经解决

@eecrazy model为graphsage的时候需要指定--feature_idx和--feature_dim这两个选项，不然特征取出来就是空的了。

这两个必须得指定吗？我没有用到任何特征，只是学习图中节点之间的关系，请问如何解决？

@pxiuqin Could you please tell me how did you resolve that? I get the same error:
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
mod_name, _Error)
File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details
import(mod_name)  # Do not catch exceptions initializing package
File "/home/leshekha/euler/tf_euler/init.py", line 21, in
from tf_euler.python import encoders
File "/home/leshekha/euler/tf_euler/python/encoders.py", line 23, in
from tf_euler.python import euler_ops
File "/home/leshekha/euler/tf_euler/python/euler_ops/init.py", line 20, in
from tf_euler.python.euler_ops.base import *
File "/home/leshekha/euler/tf_euler/python/euler_ops/base.py", line 31, in
_LIB_OP = tf.load_op_library(_LIB_PATH)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/load_library.py", line 60, in load_op_library
lib_handle = py_tf.TF_LoadLibrary(library_filename)
tensorflow.python.framework.errors_impl.NotFoundError: /data/home/leshekha/euler/tf_euler/python/euler_ops/libtf_euler.so: undefined symbol: _ZN10tensorflow14kernel_factory17OpKernelRegistrar12InitInternalEPKNS_9KernelDefEN4absl11string_viewESt10unique_ptrINS0_15OpKernelFactoryESt14default_deleteIS8_EE
I have Tensorflow version, '1.12.0'.

@yangsiran 已经解决

怎么解决的呢？


create new chunks bug

please relight only chunks which already exist
at the moment new chunks will be created
example
https://imgur.com/a/3kkfB8w

This was an issue in the area-based cleaning solution. It now checks that the chunk exists prior to cleaning, and for very large areas, queries the region files directly to select chunks that exist.


push.on('notification') i

Expected Behaviour
push.on('notification') event should fire
Actual Behaviour
push.on('notification') event is not firing now. It was working fine few days ago
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
iOS 12
Cordova CLI version and cordova platform version
cordova --version: 8.1.2
cordova platform version iOS: 4.5.5

Plugin version
cordova plugin version | grep phonegap-plugin-push: 2.2.3

Sample Push Data Payload
{
"to" : "ftcxcaKmMHI:ZG8CxGYk5rlWPyAJOQwgxfeebDSO7svbzp2T3qnJ44vavDkLa_evceuivtuRrZqVIY1M6BTOyQ0EueUvUcGTzglktYEAmRSJw2U_CcS_VbWvLwrFZ1soBp37axV1Q0qTq4tj3-ugl",
"collapse_key" : "type_a",
"notification" : {
"body" : "Body of Your Notification in Data",
"title": "Title of Your Notification in Title"
},
"data" : {
"body" : "Body of Your Notification in Data",
"title": "Title of Your Notification in Title"
}
}
Sample Code that illustrates the problem
push.on('notification', function (data) {         console.log('inside notification');         console.log(data);         alert('Notification');     });
Logs taken while reproducing problem
2018-12-06 17:33:06.331954+0500 AppName[745:98238] Push Plugin VoIP missing or false 2018-12-06 17:33:06.332186+0500 AppName[745:98345] Push Plugin register called 2018-12-06 17:33:06.332208+0500 AppName[745:98345] PushPlugin.register: setting badge to false 2018-12-06 17:33:06.332218+0500 AppName[745:98345] PushPlugin.register: clear badge is set to 0 2018-12-06 17:33:06.332228+0500 AppName[745:98345] PushPlugin.register: better button setup 2018-12-06 17:33:06.333242+0500 AppName[745:98345] FCM Sender ID 96XXXXXXX 2018-12-06 17:33:06.333272+0500 AppName[745:98345] Using FCM Notification 2018-12-06 17:33:06.333415+0500 AppName[745:98345] Using FCM Sandbox 2018-12-06 17:33:06.360459+0500 AppName[745:98238] FCM Registration Token: ftcxcaKmMHI:ZG8CxGYk5rlWPyAJOQwgxfeebDSO7svbzp2T3qnJ44vavDkLa_evceuivtuRrZqVIY1M6BTOyQ0EueUvUcGTzglktYEAmRSJw2U_CcS_VbWvLwrFZ1soBp37axV1Q0qTq4tj3-ugl 2018-12-06 17:33:06.368695+0500 AppName[745:98238] Push Plugin register success: <a2a04961 ed6b1883 182f3d0a f580eca0 60b26c7b 996c9d1f 376f692c 45asdfd> 2018-12-06 17:33:06.417329+0500 AppName[745:98345] 4.13.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add [FIRApp configure]; (FirebaseApp.configure() in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8. 2018-12-06 17:33:06.462873+0500 AppName[745:98342] 4.13.0 - [Firebase/Analytics][I-ACS023007] Firebase Analytics v.40200000 started 2018-12-06 17:33:06.463116+0500 AppName[745:98342] 4.13.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)

@karigarweb if it was working and then it stopped working I'm not sure what to tell you. Everything I see in your logs looks okay.

Everything is working great now. I removed and re-installed the iOS platform along with few plugins. That simply got everything fixed and push notifications are working like charm again.
Thanks for looking into this though @macdonst


Ignore Comments in Makefiles starting with #

Some existing Makefiles in CodeOcean still have a trailing #exit in recipes, which we need to ignore.
This MR is based on #118.

@mpass99 I rebased my changes on the latest main branch. However, there are now some repeated e2e-failures, which are also present in main. These might be unrelated to the changes in this branch and might need further investigation (a new ticket?).

Sorry. I was so used to the pipeline failing because of Trivy that I overlooked the e2e tests failing in #127. It should be fixed with #129

Great, thanks for having a look there! I'll rebase (and merge) after #129 is done.

After several retries, the pipeline for this MR turned green. I'll proceed with merging now as all errors observed are not related in any way with the Java tests.


:sparkles: Allow passing rendering user-defined texts to Pagination

... so users preferring a different translation or something like "1/10" can do that.

Word of warning: My development setup for this repo leaves room for improvement - not sure this all works as it should. I never worked on a library bundling Astro components.

Hey @boredland, thanks for submitting this pull request! I've been quite occupied lately but I'll try and take a look at it soon 😊 Thanks for your patience!


Few factorio servers. Specify config filename on start server.

Hello, Bisa!
Please add parameter "config file path/filename", like
factorio start config_X

this is already established in the init script config line 25
SERVER_SETTINGS=${FACTORIO_PATH}/data/server-settings.json
you can overide this easily


HCAP-1049 | HCAP-1030 | Add restful web api to interact with post-hire-status

Create api endpoint to create post-hire-status with tests
Create api endpoint to get post-hire-status for a given participant with tests.

One console.dir but otherwise this looks fine.

@dbayly-freshworks Done


Add podspec

I just started playing with your classes (thanks for them), but this adds a podspec, per your issue #1.

Thanks @chunkerchunker !
In the next day or so I’ll review and pull.   Then I’ll push the library to CocoaPods trunk and update the readme


Frontend-bundle.js in production mode

Hi,
I developed a DIVI extension and used the "Yarn zip" command to get the final version.
But Divi still seems to want to access the old frontend-bundle.js. This creates a Time Out error after 20 seconds.
I don't understand why it doesn't use the frontend-bundle.min.js.
Can you help me solve this problem?

Edit :
In Visual Builder mode, It always tries to access development mode scripts

Regards,
Fabien

Hi,
I solve my problem.
In the wp-config.php file, my extension was still in debug mode.
define( 'Extension_DEBUG', true);


[FEATURE] Automatically rebalance CSI components

Is your feature request related to a problem? Please describe (👍 if you like this request)
While testing Longhorn HA in a two node cluster, I noticed that after failing node1, all CSI sidecar components ran on node2 indefinitely, even after node1 came back. This makes sense and is a natural consequence of using deployments for these components. The scheduler honors the preferredDuringSchedulingIgnoredDuringExecution anti-affinity baked into each deployment when scheduling pods to ensure that they end up on different nodes. However, once node1 goes down, the scheduler has no choice but to put all pods on node2. Kubernetes does not have any built-in functionality to rebalance them later.
In a two node cluster, this has obvious consequences. It takes time for the cluster to recognize that all CSI sidecar pods are down and to spin them up an another node after node failure. In a three or more node cluster, the impact is likely limited. When one node goes down, the CSI sidecar pods are spread across the other two nodes. In the future, two nodes have to go down to cause an effect.
Describe the solution you'd like
We should evaluate the following options:

Use requiredDuringSchedulingIgnoredDuringExecution instead. There is absolutely no reason to run multiple identical sidecars on the same node. Instead of allowing this to happen, we could live with a CSI sidecar scheduling failure while a node is down. When the node comes back up, the scheduler can put the CSI sidecar back on it, maintaining redundancy. However, users of one and two node clusters will see permanent scheduling failures unless we provide them a way to reduce the number of replicas in their CSI sidecar deployments.
The kubernetes-sigs/descheduler will automatically evict pods (based on a policy) that no longer meet scheduling constraints. However, it seems to be intended to be installed once, for an entire cluster, in the kube-system namespace. We could make suggestions about its use, but probably not deploy it into clusters ourselves.
The driver deployer controller could periodically evict CSI sidecar pods when they are doubled up on nodes. This isn't as slick as relying on some pre-existing Kubernetes functionality, but it would be pretty easy to implement ourselves.

has anybody a working descheduler config to fix that for the time beeing?
The default descheduler config does not remove the pods...


Support LLVM toolset with MSVC

The -T LLVM argument with a Visual Studio generator will allow using the clang-cl compiler from LLVM instead of the regular MSVC compilers. It would be good to expose this somehow.

Second this, my particular project doesn't build on msvc, only clang-cl.


Handle Infura archive error

Problem
When using the default Infura mainnet endpoint, you get the latest 128 blocks of Ethereum state. Given a block production rate of about 13 seconds, that is about 27 minutes of full mainnet state. This means when you run ganache and fork off of mainnet you will get an error when trying to retrieve block state created 27 minutes prior to when you started.
As an example,

Alex is running ganache-cli with the -f flag set to an Infura mainnet websocket url
Alex runs tests against ganache-cli deploying a contract in block 1
13 seconds later the block height is 2
30 minutes later the block height is 138
When Alex attempts to run a test accessing the full state from block 1 an error to the tune of project ID does not have access to archive state will be thrown by Infura

Based on the Infura docs on archive data:

Because of the way account and contract storage works in Ethereum, this means that only an archive node can serve API request for certain RPC methods older than 128 blocks.

Solutions
So far I see 2 ways to handle this:

Keep your testing within 128 blocks (and restart ganache-cli after 128 blocks so you don't accidentally exceed this when testing)
Spin up another ganache with shared state before the first expires and switch to it (basically, keep the state around in ganache that would otherwise get pruned and make the request for state use this cache instead of making the json rpc request to infura)
Require users to design tests such that they don't retrieve state after 128 blocks (not sure that this would exactly solve it, probably more nuance here)

Proposal
I propose we start with solution 1 and explore 2 in the future because it is very reasonable for testing to exceed 27 minutes

To flesh this out a bit more, what we want is:

Alex uses a url for godmode ganache
Alex awaits godmode ganache starting at the top of a test suite
The tests run
If an error occurs in the tests, a request is made to shut down godmode ganache before the process exits
If the tests finish without error, a request is made to shut down godmode ganache before the process exits

This requires a few components:

API endpoints to start and stop godmode ganache running
An interface in the godmode library (or elsewhere?) to allow users to make requests to the endpoint above
Documentation and examples on the proper start up/clean up usage and docs on how to handle the archive error (or do we watch for the archive error and reset for them? then include a response message that says state was reset?)


Increase batch-size

H100 - 80Go

That would only work for the models that take a specific input shape, right? Which would be all the torchvision ones and some of the torchbenchmark ones that are tailored to ImageNet, but probably not the transformers.

Some bench do not respond correctly to a batch size some others get capped :/

it looks like it works for BERT

$ milabench run --select resnet50-fp16
resnet50-fp16.D0 {'train_rate': 1533.6431689370127}
resnet50-fp16.D0 {'loss': 3454.33203125}
resnet50-fp16.D0 {'train_rate': 1531.1626484374933}
resnet50-fp16.D0 {'loss': 3454.321533203125}
resnet50-fp16.D0 {'train_rate': 1534.0157980552508}
resnet50-fp16.D0 {'loss': 3454.314453125}
resnet50-fp16.D0 {'train_rate': 1531.498356458543}
resnet50-fp16.D0 {'loss': 3454.307373046875}
resnet50-fp16.D0 {'train_rate': 1532.2061841481632}
resnet50-fp16.D0 {'loss': 3454.299072265625}
resnet50-fp16.D0 {'gpudata': {'0': {'memory': [81088.75, 81920.0], 'load': 0.99, 'temperature': 65}}}
resnet50-fp16.D0 {'train_rate': 1530.9698631203746}
resnet50-fp16.D0 End: 2023-03-17 16:58:21.227849
[DONE] Reports directory: /home/mila/delaunap/results/runs/bumufisa.2023-03-17_16:55:32.950114

$ export MILABENCH_GPU_MEM_LIMIT=12000
$ milabench run --select resnet50-fp16
resnet50-fp16.D0 {'gpudata': {'0': {'memory': [10654.75, 81920.0], 'load': 0.98, 'temperature': 66}}}
resnet50-fp16.D0 {'loss': 3443.430419921875}
resnet50-fp16.D0 End: 2023-03-17 17:04:15.206755
[DONE] Reports directory: /home/mila/delaunap/results/runs/juvulato.2023-03-17_17:01:53.067144

Some weird behavior happening right now on  on a few bench I have not even touched

bench
AUTO Batch
Batch Size
(perf +%)
Memory Usage
Memory (x)

bert
191.54
432
1.22
75630.75
11.40

convnext_large
216.07
400
0.84
80518.75
2.83

dlrm
288079.13

0.91
3850.75
1.00

efficientnet_b0
210.94
1664
0.82
49816.75
5.74

efficientnet_b4
234.28
680
0.89
81076.75
4.63

efficientnet_b7
268.4
288
1.07
80798.75
6.91

hf_reformer
33.54
200
1.04
78492.75
17.20

hf_t5
22.18
24
1.03
66270.75
2.83

learning_to_paint
6286.53

1.20
3390.75
1.00

ppo
1660.48

0.99
2198.75
1.00

regnet_y_128gf
51.06
88
1.03
76202.75
4.11

resnet152
7548.9
?
13.58
4716.75
1.56

resnet50-fp16
1530.8
952

81088.75

resnet50-fp32
664.86
864
2.55
77172.75
8.25

soft_actor_critic
30147.53

0.97
1444.75
1.00

speech_transformer
221.84

1.00
2828.75
1.00

squeezenet1_1
235.47
4096
0.91
22810.75
4.38

stargan
651.17

1.00
3598.75
1.00

super_slomo
47.47
288
1.04
11762.75
1.48

td3
28672.73

1.00
2200.75
1.00

vit_l_32
2785.82
?
4.85
10250.75
1.05

So there is two important options

MILABENCH_GPU_MEM_LIMIT to artificially limit a GPU memory capacity
MILABENCH_FIXED_BATCH to disable the batch size computation

I am doing a re-run with MILABENCH_GPU_MEM_LIMIT =40000 to see how performance change

I will try to see if the batch finding logic works on the CI as well

Implemented in https://github.com/mila-iqia/milabench/pull/177


Update damage_critter.py

@DudeMcDude
EventObjDamage in tpdp misses a dispatcher, I think I would need this first, to get some testing going.

Added.  Hopefully I covered everything for damage_critter.

Updated; Subdual damage TBD, I ran out of time.
It is working, damage is dealt twice and has same amount.
stubs:
*gameSystems->GetAnim().PushGoalHitByWeapon(attacker, tgt);
*tgt.sound_play_friendly_fire(?) - I don't know what arg to pass
*Set last hit


Register Clock as implementing IClock

I found "Pandora.ServiceNotFoundException: No service for type dotless.Core.Abstractions.IClock could be found" in my logs. I believe it occurred when trying to construct a CachedCssResponse as the IResponse for a HandlerImpl requested by LessCssHttpHandler in ProcessRequest.

Thanks. merged

Thank you for your work on a great project. I was happy to be able to help a bit.

@Tigraine by the way, I've changed the branching model a bit during the last year -- if you pull something in, could you please pull it to the develop branch instead of master? Master builds also get pushed to nuget.org if there's a suitable new version tag available.

Oh I didn't see that - sorry Lauri. I'll keep that in mind in the future.

No worries, it was my bad for not documenting it anywhere. :)

I've got the same problem.
Any plans to release this fix ?
Thanks


multiple pseudo selectors

is there a way to do this w/ ::before and ::after on the same line to save writing display: "block" twice?
":hover": {
    "::before": {
      display: "block"
    },
    "::after": {
      display: "block"
    }
  }

as far as I can tell, there's no way to do this.


Please precise dependencies

I don't even know what to install

No, i mean dependencies like clang, ninja...

They are not dependencies of cutekit, it depends on your project

Closed due to inactivity


InvalidOperationException: Cannot find the fallback endpoint specified by route values: { page: /_Host, area: }

InvalidOperationException: Cannot find the fallback endpoint specified by route values: { page: /_Host, area: }

Is this from a sample or your own application? Is there any more details or steps you can provided? Thanks


DimensionData: Adding in new methods/tests for backups

Added in ability to add clients to a target
Added in ability to list backup info for a target
Added in positive tests

I'm unhappy with how the classes for backups objects are directly defined here instead of in the common library.  I'm going to make this change as well.

Added negative tests around the info call if backups don't exist.
Moved the classes to common where the classes for the node exist.
Added a bunch of docs on the classes themselves.

the additional changes look great. thanks @jadunham1 merging.


Chylli/dist zilla6

Codecov Report

Merging #17 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   86.57%   86.66%   +0.08%
==========================================
  Files           6        6
  Lines         529      525       -4
  Branches      112      112
==========================================
- Hits          458      455       -3
+ Misses         32       31       -1
  Partials       39       39

Impacted Files
Coverage Δ

lib/HTML/FormBuilder/FieldSet.pm
98.18% <ø> (-0.04%)
:x:

lib/HTML/FormBuilder/Base.pm
96.87% <ø> (ø)
:white_check_mark:

lib/HTML/FormBuilder/Validation.pm
87.33% <ø> (-0.09%)
:x:

lib/HTML/FormBuilder/Select.pm
82.75% <ø> (ø)
:white_check_mark:

lib/HTML/FormBuilder.pm
84.41% <100%> (+0.54%)
:white_check_mark:

lib/HTML/FormBuilder/Field.pm
80.95% <100%> (-0.18%)
:x:

Continue to review full report at Codecov.

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


'react-native upgrade' command still remains the old version.

🐛 Bug Report
The blog(http://facebook.github.io/react-native/blog/) says that the 0.59.0 released, and announced the the new upgrade way using 'react-native upgrade'.
But when I ran the command, the older version of the command result shown.
Is it a just bug or the new way did not applied the new way to the react-native-cli server?

JYs-MBP:0.58.6 jyk$ react-native upgradeYou should consider using the new upgrade tool based on Git. It makes upgrades easier by resolving most conflicts automatically.
To use it:- Go back to the old version of React Native- Run "npm install -g react-native-git-upgrade"
Run "react-native-git-upgrade"See https://facebook.github.io/react-native/docs/upgrading.htmlUpgrading project to react-native v0.58.6
Check out the release notes and breaking changes: https://github.com/facebook/react-native/releases/tag/v0.58.0
Upgrading project to react-native v0.58.6
Check out the release notes and breaking changes: https://github.com/facebook/react-native/releases/tag/v0.58.0

Environment

React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 8.11 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.10.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 23, 24, 25, 26, 27, 28
Build Tools: 27.0.3, 28.0.2, 28.0.3
System Images: android-26 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.58.6 => 0.58.6
npmGlobalPackages:
react-native-git-upgrade: 0.2.7

Copying here additional details from #23867 by @pistou:
🐛 Bug Report
I'm trying to upgrade my projet to 0.59 as it released, but it tries to upgrade to 0.58.6, which is my current react-native version.
$~ > react-native info

  React Native Environment Info:
    System:
      OS: Windows 10
      CPU: (8) x64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
      Memory: 8.01 GB / 15.90 GB
    Binaries:
      Yarn: 1.13.0 - D:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.1.0 - C:\Program Files\nodejs\npm.CMD

$~ > react-native --version
react-native-cli: 2.0.1
react-native: 0.58.6

$~ > react-native upgrade
You should consider using the new upgrade tool based on Git. It makes upgrades easier by resolving most conflicts automatically.
To use it:
- Go back to the old version of React Native
- Run "npm install -g react-native-git-upgrade"
- Run "react-native-git-upgrade"
See https://facebook.github.io/react-native/docs/upgrading.html
Upgrading project to react-native v0.58.6
Check out the release notes and breaking changes: https://github.com/facebook/react-native/releases/tag/v0.58.0
Successfully upgraded this project to react-native v0.58.6

$~ > react-native --version
react-native-cli: 2.0.1
react-native: 0.58.6

I tried to uninstall and reinstall react-native-cli just in case but didn't change much.

New upgrade is a part of RN 0.59. If you upgrade from 0.58 it's not there yet.

👋 there - so, it's a bit of a misunderstanding happening here 😅
Basically, the new upgrade command is usable from 0.59, so when you upgrade to it it's still not available. We are fixing the blogpost to be more clear on it :)
To upgrade to 0.59 we recommend using the rn-diff-purge repo.

Thanks! 😄

@JYeop @pistou thank you for submitting these issues. We're getting the blog post updated to be clearer.

👋 there - so, it's a bit of a misunderstanding happening here 😅
Basically, the new upgrade command is usable from 0.59, so when you upgrade to it it's still not available. We are fixing the blogpost to be more clear on it :)
To upgrade to 0.59 we recommend using the rn-diff-purge repo.

I should point out that the official upgrade documentation page (https://facebook.github.io/react-native/docs/upgrading.html#content) still shows relies pretty heavily on react-native upgrade, though it does seem to use rn-diff-purge as a reference.

that's because from 0.59 the CLI command upgrade actually uses rn-diff-purge under the surface AFAIK

@kelset got it! TBH it's about time they started paying attention to the upgrade process.

Documentation of previous versions also shows react-native upgrade method only.

@shubhnik you can find previous versions of the upgrade guide by browsing through the source file's history at https://github.com/facebook/react-native-website/commits/master/docs/upgrading.md
Would you mind opening an issue over at https://github.com/facebook/react-native-website to request these past instructions get added to the upgrading guide? That guide is unversioned, so it will show the same content regardless of which version you select at the top. We'll need to modify the guide to account for past versions. If you can send a PR, that would be even better.

So how does one actually upgrade from 0.58.6?

You can use the CLI as a standalone, e.g.: npx @react-native-community/cli upgrade will do


Drawer Translation Safari bug

Hi, I found small bug with drawer. On safari 11.00

Please reopen if you still have this issue, I cannot reproduce.


Check if pins are valid for output in python script

Check if pins are valid for output in python script

Pins are checked if they available for input, not output


Allow a dict to be passed in to initalize Tags

The implementation of Tags has limitations due to the use of
kwargs for initialization. This change adds the ability to
initialize Tags using a dict.
@kaarolch @brandonshough @tomdeblende @tamas7 does this match the use cases for the issues filed on this behavior?

This change should help with related issues #462, #684, and #691.


How to create Homography dataset?

I want to do this for a field hockey game but can't understand how the homography dataset is prepared, are there any tools available for the same? any help is appreciated, Thanks

Hey, I used the macOS application called RectLabel : https://apps.apple.com/fr/app/rectlabel/id1210181730?l=en-GB&mt=12


Log verbose mode

Clear and concise description of the problem
During development there are times when it is essential to see all of the console log and error messages.  I tried many things and none seem to work in all cases: large outputTruncateLength, using json reporter.  At one point I found it necessary to redirect the npm debug package from process.stdout because it uses process.stderr was suppressed.
I'm glad so much is being done to clean up the output, but I do see an ongoing need, from now on, to by-pass this in the early stages development.
Suggested solution
Add a verbose-log cli option that ensures messages to process.stdout and process.stderr always pass-through.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Why does maximum truncated output not work?  What is the logic here?

Do you have a reproduction? I don't understand your problem.

It is just stderr.. Stdout seams to always print everything.  I tend to rely on the debug package which uses stderr as its default output stream.  But I get into situations under vitest where the stderr is truncated even if I set a large outputTruncateLength value.  The only work-around I have is to change code to use stdout.  Sometimes that is easy, but it is not always.

It is just stderr.. Stdout seams to always print everything. I tend to rely on the debug package which uses stderr as its default output stream. But I get into situations under vitest where the stderr is truncated even if I set a large outputTruncateLength value. The only work-around I have is to change code to use stdout. Sometimes that is easy, but it is not always.

A lot of words but no code. Please, give me something to run

import {test} from 'vitest'

/** <code>
vitest run --outputTruncateLength 9999 tests/stderr.test.js  # ends at: ,99986,9998
vitest run --outputTruncateLength 9999999 tests/stderr.test.js  # ends at: ,99986,9998
</code>*/
test('stderr', async function() {
  for(let i = 0; i <= 100000; i++) {
    process.stderr.write(i + ',')
  }
})

// Copy and paste the for loop in the node cli, it ends in: 99999,100000,true

// process.stdout is also truncated

Vitest doesn't truncate anything written via process.stderr/process.stdout. This is Node.js behavior as far as I understand.


Class 'Input' not found

When I'm using the paginate() function, the SearchBuilder tries to call the Input facade, but this one was removed here

10x fixed in v0.1.9


Move documentation away from README

This PR moves the documentation we had in README.md into separate files in docs/.
It also converts the examples into YAML, as per #181.

Will there be a followup pr converting the SQLite and Postgres example to YAML as well?


editing ones profile doesn't work

auth issues.

I think we fixed the underlying auth issues. Works for me now.


[DOCFIX] update docs on fuse test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17773/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.JournalShutdownIntegrationTest.multiMasterJournalStopIntegration
Test FAILed.

Merged build finished. Test FAILed.


Question : Performance

I have a question which will need a short reply. Actually, want to know that before implementing in my app.
How much time in seconds does it take to mix an H.264 dash video (say it's 50mb) and an AAC dash audio(say it's 8mb)?

How would I know the performance of your target device? Test it!
Pratim Majumder<EMAIL_ADDRESS>schrieb am So., 5. Aug. 2018,
19:09:

I have a question which will need a short reply. Actually, want to know
that before implementing in my app.
How much time in seconds does it take to mix an H.264 dash video (say
it's 50mb) and an AAC dash audio(say it's 8mb)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sannies/mp4parser/issues/325, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKUD0W0o7fCZxgzxMW6yID6Razt1qdeks5uNybTgaJpZM4VvdQs
.


PARTIAL: [otbn] Update spec to allow mulqacc to set flags

PARTIAL: This will fail CI because it needs some corresponding RTL changes
The bn.mulqacc.wo and bn.mulqacc.so instructions now set M, L and Z
flags in a specified flag group. We needed a little bit of shuffling
in the encoding to make this fit.
The changes are as follows:

There's now a flag group field at bit 31 (the same as other
instructions that take a flag group)

The wb field, which chooses between the three writeback modes,
has moved from bits 31-30 to bits 30-29 and has been split into two
parts: so and wb0. so is just set for bn.mulqacc.so (just like
the top bit of wb). If so is not set, then wb0 selects
between bn.mulqacc and bn.mulqacc.wo. If so is set, wb0 selects
the destination halfword.

@imphil Just pushed the required RTL changes to this PR also, please review

Once reviewed we're going to merge this into one commit (so we don't have a commit that breaks the smoke test). Left it as two for now to ease the review process


[Request] - Allow additional Commands to be ran within specific Language Settings

I know that with the work on Unibeautify this may seem not needed.
However, until then a way to make HTML work inside PHP would be to allow me to set an additional Beautifier to run when PHP is triggered.
So in the settings of PHP there would just be another setting [text field] for additional commands to run.  From there I can just paste in "Atom Beautify: Beautify Language Html"
Or something to that affect.
This could also be used for other commands that other devs need,

Please subscribe to https://github.com/Unibeautify/unibeautify/issues/29 and https://github.com/Glavin001/atom-beautify/issues/1174 😃 .
Unfortunately, it is unlikely to be included in the current version of Atom-Beautify, as I am focusing as much of my attention on Unibeautify as possible. @szeck87 is working on upgrading Atom-Beautify to using Unibeautify, such as with this PR https://github.com/Glavin001/atom-beautify/pull/1935 .
While this means it will take more time for this feature to exist in Atom-Beautify, Unibeautify will have much better support overall and great new features coming. Please be patient and keep these ideas coming! Thank you for your interest in Atom-Beautify and Unibeautify!

Sign up for Unibeautify CI: https://goo.gl/jmM4QN
Help improve Atom-Beautify by completing the quick questionnaire: https://goo.gl/iEHBNr

Closing as a duplicate of https://github.com/Unibeautify/unibeautify/issues/29 and https://github.com/Glavin001/atom-beautify/issues/457 and https://github.com/Glavin001/atom-beautify/issues/1185 and others. Please subscribe to those and 👍 to show your interest!


Add range and values queries

Range provides an efficient way of getting just some values in the range.
Values provides a handy way of iterating through all things in the object.
This also renames value and values functions to get and get_conflicts respectively (along with their _at counterparts). I think this also helps to make the intent of the functions clearer.

I like put and get but agree on the multivalue naming stuff. I think my preference would be to flip it. get returns all the values and get_winner returns a single value. winner being intended to evoke things like "last write wins" as a hint that really there may be may values.

Nice, I agree that the conflicts wording should probably be avoided. I've gone with a hybrid: get_winner and get_all. This also leaves the get name free should we want to effectively alias or rename one of them later.

I suspect that 99% of users really want get_winner vs get_all and I generally like it when the "golden path" of the api has the simplest most terse api names.  I suggests to a new user whos just learning what to use, and for someone willing to flip through multiple values - they can deal with 4 extra characters in the method name.   So my vote would still be get and get_all

Don't want to turn this into bikeshedding, but if you want my opinion, I'm with @orionz and would also prefer get and get_all. My concern with get_winner is that I feel it introduces unnecessary cognitive overhead for someone who doesn't know or care about CRDTs (winning what? who is the loser?).

That's fine, changed the winner variants to be plain get :)


Custom inputButtonBackground for different states?

Is it possible to add a custom drawable for different states?
In "selector_bg_send.xml" I see:
    <item android:drawable="@drawable/mask" android:state_enabled="false" />
 <item android:drawable="@drawable/mask_active" android:state_enabled="true" />
But we are only able to set a static custom drawable using "app:inputButtonBackground".
I'd like to simply change the colour of the default purple background when it is active to blue.
Thanks for your help, love ChatKit!

Ah after reading more about Drawable Resources I figured it out - sorry!

Hello @delta9 !
Now, in version 0.2.0 you can change default shape colors of "submit" button via inputButtonDefaultBgColor for normal state, inputButtonDefaultBgPressedColor  for pressed and inputButtonDefaultBgDisabledColor attributes.
You can also check out other new attributes here
Best regards, Alexander.

Hey Alexander,
Thank you so much for the quick updates, v0.2 looks amazing.
Have a lovely weekend!
Kind regards,
Melvin


Fix/bert ft onnx

We were doing a boolean array indexing to find the [CLS] index which isnt supported by ONNX and causes and invalid model to be generated.
Also, we were using fake random number data to generate the tensors which means that tokens like [CLS] where unlikely to be generated.  The fix for this is to stop generating numbers and use fake sentence and run them through the vectorizers

I tested this with an LSTM classifier, CNN-BiLSTM-CRF and a BERT fine-tuned model.  All seem to work with this configuration


Terminal Text Color Not Displayed

Hi, I really like this package. Is there any way to display the text color on the terminal-panel? For example, when I run make in terminal, there will be colored text indicating whether there is a warning or error.  But that color is not displayed in atom, which makes it very hard to see the output.

Detection if the terminal supports ANSI colors can be a bit spotty. I've gone to great lengths to emulate it but may have missed some cases. Could you detail how your make and your environment detects ANSI support?

For this particular issue, I'm using sphinx-docs.  The make command invokes sphinx-build command, which gives colored output.


How to get the  detail timing by python script?

Steps to reproduce the problem:
I didn't find the api to get  the  detail timing  .  for example : client conn established、 server conn initiated、server conn tcp handshake and so on
Any other comments? What have you tried so far?
System information

If you wish to inspect the timestamps, you can find the relative attributes in client and server connections here:
https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/connections.py
So, given a flow f intercepted e.g. by a script, you can access those fields in f.client_conn and f.server_conn objects. Does this help?

@madt1m thank you  very much~


Add docs for csi-driver-spiffe v0.6.0

Also adds security documentation and other improvements for csi-driver-spiffe docs in general

Gonna unhold since v0.6.0 is already out. Thanks for the review! 😁
/unhold


Presentation: Add an option to apply content modifiers to nested content

Closes https://github.com/iTwin/itwinjs-core/issues/3786
imodel-native: https://github.com/iTwin/imodel-native/tree/presentation/content-modifiers-on-nested-content

/azp run


Ensogl loader default options are outdated

The defaults in ensogl config options in loader groups are set to:
"wasmUrl": {
          "value": "pkg.wasm",
          "description": "The URL of the WASM pkg file generated by ensogl-pack.",
          "primary": false
        },
        "jsUrl": {
          "value": "pkg.js",
          "description": "The URL of the JS pkg file generated by ensogl-pack.",
          "primary": false
        },
        "assetsUrl": {
          "value": "assets",
          "description": "The URL of the dynamic assets directory.",
          "primary": false
        },

This is no longer true as assetsUrl should have dynamic-assets. We need to check and fix values of  wasmUrl (either pkg.wasm or pkg-opt.wasm).

@mwu-tow did you change assetsUrl to dynamic-assets? I think you've been chasing that, right? If so, the EnsoGL pack should be fixed as well.

@wdanilo I don't think I touched it, pinging @kazcw?


There is SQL injection in your source code

The vulnerability affects http://<IP_ADDRESS>/eyoucms/index.php , tid
URL encoded POST input tid was set to 1À§À¢%2527%2522
Use BurpSuite

已修复


Add Cost tracker to device

Describe the feature
I don't know if this is possible, but it would be great to add the 'cost trackers' to the device they relate to. This would simplify adding them to an area as well as marking them visible when navigating via the device rather than just the octopus integration.
Expected behaviour
The battery notes integration does this:

Use Case
Cost Tracker will always (?) be associated with a single device, so this just makes the link more explicit and a nicer user experience.
Confirmation

[X] By submitting this feature request, you agree that you have read the documentation and confirmed it does not already exist
[X] I am willing/able to help contribute to the solution of this feature

Hello and thanks for the feedback. I'm sure it's possible, but not sure if it's a quick addition. I'll add it to the list, but not sure when I'll get to it. Happy for someone to submit a pull request with the change.

This was a quick fix by the looks of it and will be available in the next release

This should be completed as part of https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v13.3.0


Do release 1.0.4 to enable clients without any assumed URL suffixes

All, can you please help do a 1.0.4 release that includes PR #25 work and would allow usage of the library with an upcoming plugin for CloudStack (out-of-band management plugin for nested-CloudStack environments). /cc @rafaelweingartner
Thanks,
Rohit

Would not you like to add the client timeout in this next version as well?

@rafaelweingartner I would prefer to have such an option, let me see if I'm able to find time to send a PR today. Otherwise, for my use-case PR#25 is much needed.

@rafaelweingartner okay I've sent a new PR that will adds a mechanism to override/specify a custom connection timeout, please review -- https://github.com/Autonomiccs/apache-cloudstack-java-client/pull/27
If you're happy with the change, please merge this and do a 1.0.4 release. Thanks!

Sure, I only had a comment on PR #27
Also, I will edit this issue to reflect the changes on these new PRs you created.
The release process is automatically executed by Jenkins, and the release notes is also generated automatically from PRs and issues closed.


Cooldown on automations to avoid triggering in that time again

Description:
Ability to pause an automation for a given time, so its not trigger within that timerange again (cooldown). This would have been made before with

condition: template
value_template: >-
{{ ((as_timestamp(now()) - as_timestamp(states.automation.entity_id.attributes.last_triggered))) > 3600 }}

This is a lot of code and not good for the config. The entity name of the automation had to be changed also every time.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#
Example entry for configuration.yaml (if applicable):
automation:
  - alias: 'automation'
    # Set a cooldown for 30 seconds
    cooldown: '00:00:30'
    trigger:
    condition:
    action:

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Can someone have a look at 292-294 if this changes are ok and dont break anything else?
The internal entity self._last_triggered is normally a datetime.datetime object (from utcnow() ). But when its loaded from the recorder (previous state)  its pulled with the function: state.attributes.get('last_triggered') as string @def async_added_to_hass(self). This seems a bit inconsistent to me and breaks my PR

This looks like a valuable use case, if somewhat of an edge case. Testing needed means you should build some tests, like triggering an automation twice in quick succession and making sure the cooldown worked!
On the code part do you need cooldown_till as an attribute? Seems if cooldown is checked before last_triggered is updated you could just check last_triggered+cooldown. One big problem is I don't see where cooldown_till is reset to none (another thing testing could check)
I'd also recommend adding a log entry or somesuch on line 356 when an automation is skipped because of a cooldown.

I don't like the name. Maybe trigger_after?

No go on this? This is a huge miss in homeassistant, and like stated, causes a lot of grief with extra code that isn't needed.  Every decent automation platform has cooldowns.

I would be open to a PR contributing this functionality. In this case the author closed it's PR.


Request to expand the definition of DOORS syndrome

On behalf of the ClinGen Hearing Loss and Epilepsy Gene Curation Expert Panels, I am requesting an expanded definition of DOORS syndrome (MONDO:0009079).
Expanded Textual definition
DOORS syndrome (also known as DOOR syndrome) is a multiple congenital anomalies-intellectual disability syndrome characterized by sensorineural hearing los (deafness), onychodystrophy, osteodystrophy, mild to profound intellectual disability, and seizures. Isolated seizure disorders and isolated hearing loss have also been reported in individuals as a proposed spectrum of DOORS syndrome.
ClinGen joint Hearing Loss and Epilepsy Expert Panels evidence summary
Autosomal recessive TBC1D24-related syndromes show marked phenotypic pleiotropy, with multi-system involvement and severity spectrum ranging from isolated deafness, to benign myoclonic epilepsy restricted to childhood with complete seizure control and normal intellect, to early-onset epileptic encephalopathy with severe developmental delay and early death. There is no distinct phenotypic correlation with pathogenic variant type or location yet, but patterns are emerging (Balestrini 2016). Sensorineural hearing loss is a key feature of DOORS syndrome, which is characterized by deafness, onychodystrophy, osteodystrophy, mental retardation, and seizures (Campeau 2014). Isolated seizure disorders without any reported deafness have also been seen (Balestrini 2015). In contrast, two of the families reported to have nonsyndromic hearing loss caused by variants in TBC1D24 were shown to have no history of seizures (Rehman 2014). Further, two independent reports identified the same variant in TBC1D24 to be segregating in an autosomal dominant manner with nonsyndromic hearing loss (Azaiez 2014, Zhang 2014). Currently there is not enough evidence to treat nonsyndromic hearing loss or isolated seizures as distinct conditions, especially because those affected with DOORS syndrome have both hearing loss and seizure phenotypes.
References
PMIDs: 25769375, 26371875, 25557349, 24291220, 24729539, 24729547
@ahamosh @Orphanet @pnrobinson @nicolevasilevsky @cmungall @mellybelly

sensorineural hearing los (deafness), should likely be sensorineural hearing loss (deafness),


Using new end point for extracting text from assets demo

[pr-server]
View this change on PR Server

[pr-server]
View this change on PR Server


Update azure-storage-blob to 12.25.3

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.azure", artifactId = "azure-storage-blob" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.azure", artifactId = "azure-storage-blob" }
}]

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

Superseded by #1080.


thin_lto feature support

I may be missing something but other toolchains seem to support thin_lto or other forms of LTO (https://github.com/tensorflow/tensorflow/blob/1843f39c11e42751837c62acfb74e1fe697353ef/third_party/toolchains/clang6/CROSSTOOL.tpl#L402 for example) -- it would be lovely to support that here. Or perhaps I'm mistaken: can someone suggest how I might enable LTO/pgo in general?

In general, this project is now lagging behind https://source.bazel.build/bazel/+/master:tools/cpp/unix_cc_toolchain_config.bzl.
Maybe I should also try to just use that rule directly without copy pasting code from there.
I am going to repurpose this issue towards that.

Thanks @siddharthab !

ThinLTO has now made it to @bazel_tools//tools/cpp:unix_cc_toolchain_config.bzl in bazel 1.0. So we can now refactor our code to depend on the rule there for this as well as other features.

The standard @bazel_tools//tools/cpp:unix_cc_toolchain_config.bzl also supports more platforms, such as ARM (Android). There's an LLVM distribution for armv7a, yet this toolchain doesn't support it purely because of the lack of config, which already exists in Bazel. Would be great to reuse the main config and get all that!


Feature/Receive file

Hi @Seven-Y-Q-Guo,
i change your PR a little and create a new one.
can you review this pull request?
Thanks

Hi @Seven-Y-Q-Guo, i change your PR a little and create a new one. can you review this pull request?
Thanks

Hi @parvardegr it's good idea to decouple the logic for DOM into single file, well done.
I'm fine with your refactor, just want to mention the typo issue are still happening on README.

Hi @Seven-Y-Q-Guo, i change your PR a little and create a new one. can you review this pull request?
Thanks

Hi @parvardegr it's good idea to decouple the logic for DOM into single file, well done. I'm fine with your refactor, just want to mention the typo issues are still happening on README.

Thanks for the review,
i'm gonna add you as a collaborator because you've done very much for this repository.
you can Squash and merge bug fixes pull requests, but for new features it's good to let me check them too.

Sure, many thanks!
Will let you know for sure in case of any new features.


Replace next participant icon

Right now this uses the same study browser icon:

Probably this one will work

Or this one

Closed via https://github.com/revisit-studies/study/commit/f16bd78aa43d9d10fe843e65a09435a1f8338c41


Add a Logistic regression cost function code in DATA SCIENCE PROJECT folder

Logistic Regression Cost function is "error" representation of the model. It shows how the model predicts compared to the actual values. As it is the error representation, we need to minimize it.

Please assign me this issue


[feat] make it limited for now

Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

https://github.com/dogecoin/dogecoin/issues/2003#issuecomment-847304810

Limiting the supply has been discussed many times.
[1] #1674 (recent issue)
[2] https://www.reddit.com/r/dogecoindev/comments/la1hk3/continuation_of_1674/

To promote myself, I wrote about economic impact of deflation : https://github.com/dogecoin/dogecoin/issues/1963#issuecomment-843617890
If you want to see other issue/discuss about limiting the supply : https://github.com/dogecoin/dogecoin/issues?q=is%3Aissue++is%3Aclosed+supply+limit+


pecdm::provision is not idempotent due to aws_key_pair attempted recreation

Describe the Bug
pecdm::provision is not idempotent - running the plan again on an already provisioned aws infra (albeit with reaped instances) causes the following error:
% bolt plan run pecdm::provision --params @params.json
Starting: plan pecdm::provision
Input Puppet Enterprise console password now or accept default. [puppetlabs]:
Starting: plan pecdm::subplans::provision
Starting: task terraform::initialize on localhost
Finished: task terraform::initialize with 0 failures in 0.17 sec
Starting infrastructure provisioning for a standard deployment of Puppet Enterprise
Starting: plan terraform::apply
Starting: task terraform::apply on localhost
Finished: task terraform::apply with 1 failure in 34.67 sec
Finished: plan terraform::apply in 34.68 sec
Finished: plan pecdm::subplans::provision in 35.76 sec
Finished: plan pecdm::provision in 39.71 sec
Failed on localhost:

  Error: Error import KeyPair: InvalidKeyPair.Duplicate: The keypair 'pe_adm_14e8e3' already exists.
  	status code: 400, request id: 257c2dd5-8d06-4e8c-902b-0dbe086c6f67

    with module.instances.aws_key_pair.pe_adm,
    on modules/instances/main.tf line 54, in resource "aws_key_pair" "pe_adm":
    54: resource "aws_key_pair" "pe_adm" {

Failed on 1 target: localhost
Ran on 1 target

Expected Behavior
I expect this plan to run the terraform apply again and have it create anything that currently does not exist.
Steps to Reproduce
Create params.json:
{
    "project"        : "jr-ape",
    "version"        : "2021.7.1",
    "architecture"   : "standard",
    "cluster_profile": "development",
    "provider"       : "aws",
    "cloud_region"   : "ap-southeast-2",
    "firewall_allow" : [ "<IP_ADDRESS>/32" ],
    "ssh_pub_key_file" : "/Users/jesse/.ssh/id_rsa.pub",
    "extra_terraform_vars" : {
    "tags" : {
      "lifetime" : "2d",
      "department" : "PS",
      "created_by"<EMAIL_ADDRESS>    }
  }
}

Sign in to aws with aws sso login
Execute the plan as per above: bolt plan run pecdm::provision --params @params.json
Delete the created ec2 instances.
Execute the plan again: bolt plan run pecdm::provision --params @params.json
Environment

Terraform v1.3.4 on darwin_amd64
macOS 12.6.1

Additional Context
Looks like aws_key_pair resource state is not being added to tfstate. I see there is this issue https://github.com/hashicorp/terraform-provider-aws/issues/1092 about aws_key_pair not being able to be idempotent unless you hack the tfstate file by adding in the public_key if it's not there already.
I also tried just deleting the key pair and running the provision plan again, but then it creates a second pe server instance (same name) and then goes on to pass invalid parameters to peadm::deploy (passing undef to primary_host)...
...
Starting: plan peadm::install
Finished: plan peadm::install in 0.03 sec
Finished: plan pecdm::subplans::deploy in 0.08 sec
Finished: plan pecdm::provision in 52.36 sec
peadm::install: parameter 'primary_host' expects a Peadm::SingleTargetSpec = Variant[Pattern[/\A[^[:space:],]+\z/], Object[{name => 'Target', attributes => {'uri' => {type => Optional[String[1]], kind => given_or_derived}, 'name' => {type => Optional[String[1]], kind => given_or_derived}, 'safe_name' => {type => Optional[String[1]], kind => given_or_derived}, 'target_alias' => {type => Optional[Variant[String[1], Array[String[1]]]], kind => given_or_derived}, 'config' => {type => Optional[Hash[String[1], Data]], kind => given_or_derived}, 'vars' => {type => Optional[Hash[String[1], Data]], kind => given_or_derived}, 'facts' => {type => Optional[Hash[String[1], Data]], kind => given_or_derived}, 'features' => {type => Optional[Array[String[1]]], kind => given_or_derived}, 'plugin_hooks' => {type => Optional[Hash[String[1], Data]], kind => given_or_derived}, 'resources' => {type => Optional[Hash[String[1], ResourceInstance]], kind => given_or_derived}}, functions => {'host' => Callable[[0, 0], Optional[String]], 'password' => Callable[[0, 0], Optional[String[1]]], 'port' => Callable[[0, 0], Optional[Integer]], 'protocol' => Callable[[0, 0], Optional[String[1]]], 'transport' => Callable[[0, 0], String[1]], 'transport_config' => Callable[[0, 0], Hash[String[1], Data]], 'user' => Callable[[0, 0], Optional[String[1]]]}}], Array[Peadm::SingleTargetSpec, 1, 1]] value, got Undef
  (file: /Users/jesse/src/puppet/tf/puppetlabs-pecdm/plans/subplans/deploy.pp, line: 70, column: 3)

I'm pretty sure this is only happening in relation to #99 and I don't think there's much else to be done to make this more resilient.


Maybe a better App description

XIASL
Cross-platform IDE for working with ACPI tables (assembled/disassembled). Smooth and efficient editing environment, tens to hundreds of thousands of lines of code can be edited with ease.
Feature highlights

Cross-platform: Linux, Windows and macOS (32 and 64 bit) are supported
Multilingual support (currently implemented: Chinese and English)
Supports Tabs
Uses Labels for highlighting elements (red = scope, orange = device, blue = method)
Shows indent edit lines
Connects brackets visually
Supports code folding
Restores last opened file(s)
Automatically extracts ACPI tables on start (under Windows and Mac)
Automatically converts files from .aml to .dsl
Humanized search function, supporting simple regular expressions
Search box supports history list and input auto-complete
Drag and drop support
Unlimited levels of revocation and recovery
And more…

Readme has been updated, thanks a lot.
https://github.com/ic005k/Xiasl#readme


[AutoPR resources/resource-manager] Add api version 2019-07-01 for features

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7454

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5935


LSNBLDR-500; improve generation of folder names

FYI conversion scripts were added in SAK-30389 PR #1879


Fix okta verify mapping

Fixed the mapping for device names. Now when users are asked to use MFA to log in, they will see an accurate dropdown list of each verification method they have. Push, call, and sms notifications are filtered from the list because we do not currently support them.

Coverage increased (+0.08%) to 54.846% when pulling 8844ea30a71d17a1fd349ab3b5d474095e411a67 on fix_okta_verify_mapping into 49142b4bb4f099bdb9dbef6f62279a895656ae30 on master.


[CWC Code Snippet] Add AI enhancements

[!WARNING]
Blocked by

https://github.com/carbon-design-system/carbon/issues/15470

Closing as not planned for now. We can re-open if this gets prioritized in a future phase.


feat(config): Make MaximumNumberOfResults and MaximumNumberOfEvents configurable

Summary

#466
Checklist

[X] Tested and/or added tests to validate that the changes work as intended, if applicable.
[X] Updated documentation in README.md, if applicable.

@TwiN When you get a chance could you review this please? This looks so awesome and I think it will really benefit Gatus!

@TwiN how does the process of PR work in this project? Who should resolve conversations, the one asking or the one answering? You don't have contributing guidelines in this repo so it's not clear.

Hey lovely @TwiN is there any chance you could review this sir? It would be amazing if we could get this feature as we absolutely love Gatus!!! <3

What exactly is an event in this context? What's the difference to a result?

Reviving.. is this still planned?

Any update on this ? Gatus does so many things, so it's a bit disappointing not to be able to configure the data retention period...

Looks like there's a couple of merge conflicts due to how long it has been.
I've always been holding back about this, mostly because the way the information is displayed would provide a bad user experience.
Right now, you have to go one page at a time on the dashboard, which is 20 results each. If there were 1000 results, you'd have to click 50 times to get to the last page.
Either way, since this has been requested so many times, we may as well give it a shot.
P.S. due to how many code changes have been made, it may not be possible to easily resolve the conflicts in this PR


Exception thrown while converting foreign characters

https://github.com/jamesmishra/mysqldump-to-csv/blob/24301dfa739c13025844ed3ff5a8abe093ced6cc/mysqldump_to_csv.py#L104
I changed this line to: for line in fileinput.input(openhook=fileinput.hook_encoded("iso-8859-1")):
Converted it with no issues after changing it.

Slightly more precise repro:
python mysqldump-to-csv/mysqldump_to_csv.py <enwiki-latest-categorylinks.sql

blows up with:
Traceback (most recent call last):
  File "/home/ciro/down/wiki/mysqldump-to-csv/mysqldump_to_csv.py", line 114, in <module>
    main()
  File "/home/ciro/down/wiki/mysqldump-to-csv/mysqldump_to_csv.py", line 104, in main
    for line in fileinput.input():
  File "/usr/lib/python3.11/fileinput.py", line 251, in __next__
    line = self._readline()
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/fileinput.py", line 372, in _readline
    return self._readline()
           ^^^^^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdc in position 1980: invalid continuation byte

The likely reason is that that file contains binary data on the third column, it's a dumpsterfire:
INSERT INTO `categorylinks` VALUES (10,'Redirects_from_moves','*..2NN:,@2.FBHRP:D6^A^W^Aܽ<DC>^L','2014-10-26 04:50:23','','uca-default-u-kn','page'),

Your solution makes it now blow up. I wonder if the output will be correct though. given that the file contains:
/*!40101 SET character_set_client = utf8 */;

so it is likely meant to be utf8.


[CONTENT] Smart contract example - Flow

We should have a page /smart-contract-examples/flow giving a lightweight tutorial for minting a Flow smart contract on NFT.Storage.
Let's make a simple example that:

[ ] Gives an intro to Flow
[ ] Gives an example of minting an Flow smart contract for a PFP on Flow and NFT.Storage

Alternatively, we can leverage @jochasinga 's Flowwow tutorial here, though the goal of this page would be to have a really simple single smart contract example, and we can potentially use Flowwow better in the /tutorials section.
Note for the community: If you are interested in helping out, please do comment below!
Note for whoever tackles: Flow does have a metadata spec but metadata is kept on-chain

I can tackle this shortly after the AVAX tuturial.


Introduce gradient token type

We've introduced basic gradient support previously by using just a string: linear-gradient(...) and we've received feature requests to extend that to other gradient types such as radial or conic.
Issues where this is requested:

https://github.com/six7/figma-tokens/issues/858
https://github.com/six7/figma-tokens/issues/441

Instead of just adding more of these hacky solutions, we should introduce a new token type for gradients.
The W3C DTCG has outlined in their draft how these gradient tokens should look like:  https://tr.designtokens.org/format/#gradient
These would look like this:
{
  "blue-to-red": {
    "$type": "gradient",
    "$value": [
      {
        "color": "#0000ff",
        "position": 0
      },
      {
        "color": "#ff0000",
        "position": 1
      }
    ]
  }
}

Note
As this draft is still evolving and currently doesn't show any support of these additional gradient types, I consider this issue currently being blocked as we don't want to move forward until a decision has been made.

Is this still in process?

Wondering the same. I see that it is marked as blocked... Is there any way to see why it is blocked?

Wondering the same. I see that it is marked as blocked... Is there any way to see why it is blocked?

It says in the note at the bottom

https://github.com/design-tokens/community-group/issues/101 Seems to be in consensus on the need of a gradient types.
These discussions seem to be a year ago though, and considering almost no progress is being made on that standard in the area I'd argue that the value of adding support for the css style gradient types for radial etc. outweigh the value of getting it according to standard the first time.
I love the idea of following a standard.. but sometimes you have to balance that against that Radial gradients are common and this is a severely limiting factor. Implementing a "for the time being" solution by adding the other types to the existing solution in the meanwhile seems resonable to me.

This request has been moved to our new feedback tool. Go check out https://tokensstudio.featurebase.app/ to create a free account. You can upvote and comment on existing posts, make a new request, and subscribe to be notified when requests move into our roadmap.

Added to Featurebase Roadmap : 🪙 Expand token types


info() result auto_compaction property

Background
In the api docs it lists the response object as (in .ts form):
/** Response object for `info()` */
interface Response {
    /** the name of the database, and also the unique identifier for the database */
    db_name: string;
    /** the total number of non-deleted documents in the database */
    doc_count: number;
    /** the sequence number of the database. It starts at 0 and gets incremented
      * every time a document is added or modified. */
    update_seq: number
}

it also states:

There are also some details you can use for debugging. These are unofficial and may change at any time

Thus far I have represented these as a special case interface for advanced use:
/** Response object for `info()` */
interface ResponseDebug extends Response {
    /** (IndexedDB) either `'base64'` or `'binary'` */
    idb_attachment_format: string;
    /** (WebSQL) true if the SQLite Plugin is being used */
    sqlite_plugin: string;
    /** (WebSQL) either `'UTF-8'` or `'UTF-16'`. */
    websql_encoding: string
}

the result of info() can therefore be "normally" treated as a Response object, and optionally cast to a ResponseDebug to access the extra properties in advanced usage.
Question
In the tests 'db.info should give auto_compaction = ... (ref. pouchdb/pouchdb#2744)' in test.basics.js there is also an auto_compaction property.
Should this be considered:

"debug info and subject to change" (i.e. for advanced use only and put on ResponseDebug); or
a property that is commonly used by any developer and therefore put on Response?

Yeah, I think we forgot to document the auto_compaction property on the info object.
In general, you will have a tough time formalizing those keys, because they vary wildly among different *ouch implementations (check out the difference between PouchDB Server, CouchDB 1.x, CouchDB 2.x, Cloudant, and Couchbase Sync Gateway sometime)...
I dunno what the standard is for such cases in TypeScript, but maybe you could just have an object that's a Map<String,Object> called params or something?

@nolanlawson I don't actually know if I can do that, but I will look into it.
It could also be the case that we build up a set of different info response objects that have keys based on the underlying, and then the end user can cast to the right object.
As with all ts I could just return the info as any - it would all still be valid, but adding the most common properties to the returned object's interface helps people using the d.ts feel their way through the code by following the intellisense.
I'll leave the auto_compaction on the ResponseDebug interface as it doesn't seem to be commonly used, also as per IRC earlier @marten-de-vries and yourself seem to say the same thing:

[19:00:31] <Freenode:#pouchdb:commandoline> I consider auto_compaction to be a ResponseDebug property - simply because CouchDB doesn't support it and it's not specifically listed in our documentation.

Closed for now - e3d87cac seems to match what @nolanlawson  and @marten-de-vries are saying, and the d.ts now allows the tests to be written.


Support Advanced search provide multiple field suggestions

Feature
As we are building Advanced Search we would like users to select an attribute in an entity and provide suggestions for those attributes.
Example:

user clicks advanced search
User selects column attribute
Backend should provide suggestions for column attribute

Describe the task

API will be changed to
http://localhost:8585/api/v1/search/suggest?q=sa&index=table_search_index&field=service_suggest
new parameter field is added and can be passed to limit the search for a field
Table will have

column_suggest for columns
database_suggest for database
schema_suggest for schema
service_suggest for service

Topic will have

service_suggest for service

Dashboard will have

chart_suggest for charts
service_suggest for service

Pipeline will have

task_suggest for pipeline
service_suggest for service

MlModel we are not adding anything right cc @pmbrull which attributes make sense to add here for advanced search

Apart from these, we should show

owner and we should enable user & team components here
tags we should enable tags and glossary_search

cc @Sachin-chaurasiya

@Sachin-chaurasiya content also changed from table-suggest to metadata-suggest

metadata-suggest

@harshach, Should I make this change on the same PR, so the suggestion won't break on UI.

yes please


Cannot create a Partial type in a one-liner

TypeScript Version:  3.4.5; 3.7.0-dev.20190829

Search Terms:
Partial, Generic, inconsistent,
Code
interface MyMap {
	field: string;
}

function someGenericFunction<T extends MyMap>(input: T) {
	let y: Partial<T>;

	// falsely not allowed:
	// ts(2322): Type '{ field: ''; }'is not assignable to type 'Partial<T>'.
	y = { field: '', };

	// similar, but allowed
	y = {};
	y.field = '';

	// correctly not allowed
	y.anything = ''; // anything is not defined in MyMap type
	y = {
		field: '',
		anything: 123, // anything is not defined in MyMap type
	}
}

Expected behavior:
Should be able to create the generic in a one-liner .
Actual behavior:
Can be done in two lines, not in one line.
Playground Link:
http://www.typescriptlang.org/play/#code/JYOwLgpgTgZghgYwgAgLIE9VwA7IN4CwAUAJAzAQA2AJgFzIDOYUoA5gNzEC+xxMAriARhgAexCNRAWwgBxCCGjAEAMUHCxIADwAVZBAAekENQZpMOAHwAKUNn5h6OgJT5iJShDDJ09AApwUCJwlLqWnETuAPRRyPCUDFToyCCi3iGUogDuEHTI0bFgDNYATADMJSXOTujYKADkeHEUNPT19ezIXPXAZqnpDAzArCBwAEaeyGCiU7UNAUHAIWH1AHT5pMkAvPjNVHntADRdEQWMwFL8lIHHYw7IGdm57tv4XBEk6Kvk+8g77adIqQYsgEKIoFAIMJKMl+g9KJkctQXqs4CB0GAABZsP7IAHIEE-Gh4tEY7EgVj1ZDUUQQPppfQGXreUCzOrmLDYF64wikMgtA71Q7uEikrFsegARnKx0JApJ6PFFKpNLpKQZhmZyFZYDmHJw7h4RCNQA
Related Issues:
#28470

Duplicate of #13442
Note that T may be resolved with a type like
interface SomeoneElsesMap extends MyMap {
  field: "It's *my* map now";
}

So you can't safely assign {field: ""} to Partial<T>.  For that matter, you can't safely do the assignment y.field = "", but for whatever reason that's allowed by the compiler.

Okay, I see I did not do enough search in the issue history. This issue has a lot of history being closed as duplicate. In fact, item #23015 seems to be exactly the same.
It's still a bug though, as it does not work like expected. Or it should accept both cases, or neither. But I understand that it would be a very breaking change in both cases.


Overall Design Elements

I assume we are looking at this for a better site than (SQL Saturday)[https://www.sqlsaturday.com/]. With that in mind, perhaps we need a list of the items to deal with? This list likely needs to be on the wiki, but a discussion here first would be good.

main site for listing events

list of upcoming events
search for events by various means (location, name, status, etc.)
feed of upcoming events
global sponsors (logo, text, link)
submission for a new event
general about/faq/support/etc.

individual sites/pages for each event

data managed by an organiser (description, date, location, etc.
Code of Conduct - ??? do we allow customisations/additions ???
T&C - ??? customisations/additions???
email features to contact speakers/attendees/volunteers
schedule of sessions with locations
support for multiple days (pre-cons/post-conts, day of) -- ??? Multiple day events???
attendee registration
cart for adding pre/post con and lunch
integration with payment options
feed for mobile apps   -- ??? do we add a mobile app to the project (??separate project??)
sponsor list
networking/who is attending
support for speaker uploads (?? zip only??, ??separate PPT/code??)
ical
support for online platforms (separate urls)
map app support - one thing I find hard from SQLSat is easily getting directions day of
news/updates from organisers
volunteer requests/opportunities
evals
list of speakers, links to some bio/speaking cv/site/etc.
build a schedule?

Admin side

approve/decline sessions
manage waitlist
manage refunds (easy link to payment sites)
produce badges/speedpass/tickets
manage sponsor invoices/AR features
manage indididual registrations
graphing for data elements
social media promotion (scheduling)
email promotion (scheduling)
todo list
burndown of milestones to events, ical integration?
reminders for groups (speakers, organizers, etc.)
templates for emails and social media promotions (token by event?)

One thing that's been mentioned in other issues, is the ability to reach out to attendees that checked in at the site. Do we want to consider allowing this kind of functionality especially with a bar code like Rob Volk and others were working to use.
I've also wondered if we need to start embracing virtual/digital aspects of events. We've proven over the past several months that these types of events can happen. Allowing for remote attendance has also been highlighted as an accessibility issue. I understand that may bring up questions like closed captioning as well.
I'm not saying we have to have the answers today, but I would like it if we could decide if remote options are something we'd like to plan for in the future.


[Feature] Anonymous User Tracking

🔹 Jira Ticket(s)

MOB-8655
MOB-8652

✏ Description

This pull request merges anonymous user tracking (AUT) code into main branch..

Hi all - https://github.com/Iterable/iterable-swift-sdk/releases/tag/6.6.0-beta1 claims to contain anonymous user support, but it actually doesn't contain much new in comparison to the previous release. Looks like maybe this PR needs to be merged first?


iD Editor and data processing

Changelog:

Improve operation logging
Add analysis results to scenario page
Misc improvements

[x] Implement server component
[ ] Fork and modify iD Editor

Fork of iD should be in the making. Tested the branch and changes look good.


Looking for demo_multi_sensor_fusion localization data for apollo 3.5

Hi, I am following the MSF localization instruction and from the instruction it requires localization data for apollo3.5:
-"In the downloaded data, you can find a folder named apollo3.5."
However I can only found the download link for localization data of apollo2.5, I am wondering if you can kindly point out where I can download the localization data for apollo3.5.

Hi, The link to the corresponding dataset had been broken.
Temporary Solution: please contact Yao Zhou<EMAIL_ADDRESS>to request the dataset.  Requests need contain the following:
Email address and affiliation (business or school)
Application purpose

Thank you!

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions. Thanks!

@natashadsouza Could anyone please provide me a localization dataset for apollo 3.5. Eagerly looking for that.
From,
South korea


Better Threat/Wildfire Dashboard user information

I noticed that the wildfire dashboard was putting "unknown" for the user when the wildfire logs were for SMTP traffic and contained the email sender and recipient fields.
I've changed the pan:threat source so it captures the recipient or sender in the user field if src_user or dest_user are null as follows:
[pan:threat]
EVAL-user                           = coalesce(src_user,dest_user,recipient,sender,"unknown")

this makes the wildfire dashboard more accurate.
cheers

Added to Add-on 3.7.0


multiple usage of same collection parameter in extended query

I wanna to execute native query like below:
select user_name from user where user_id in(:userIds) and age > 35
union
select user_name from user where user_id in(:userIds) and age < 20

but it throw an error like this: java.lang.IllegalStateException: Bound parameter count does not match parameters in SQL statement

The Postgres driver uses $1, $2, $n notation for parameters. This is likely a Spring Data issue. Can you attach the actual SQL query or  run the native query using plain R2DBC API?

May be you are right. I found something wrong under package org.springframework.data.r2dbc.core.

Indeed, Spring Data R2DBC renders a SQL statement that does not match the bindings:
select user_name from user where user_id in($1, $2, $3) and age > 35
union
select user_name from user where user_id in($4, $5, $6) and age < 20

while binding only positions $1, $2 and $3.

I filed spring-projects/spring-data-r2dbc#310 to address the issue in Spring Data R2DBC.


Is it possible to integrate golangci-lint?

Gometalinter is already integrated.
Gometalinter is deprecated.
The author recommends switching to golangci-lint.

Sure, just needs a PR I guess.

I'll send a PR this weekend.


YouTube Music Support

Google Music is being deprecated in favour of Youtube Music:

https://www.digitaltrends.com/music/what-happens-to-google-play-music-youtube-music/
https://www.androidcentral.com/youtube-music-being-default-music-app-great-news-play-music-users

TODO:

[x] keyboard shortcuts should work on Youtube Music if opened

shipped in v1.7.0

[ ] there should be an option to default to Youtube Music (for users who want to migrate sooner)

waiting for Google to sunset Google Music

Do I get this right? YouTube Music is included with a YouTube Premium subscription?

Correct.


[WIP] Use the centos.org repo for scl packages

This repo seems to be updated more frequently than the copr repo and contains more recent packages.
This will also allow us to pull PostgreSQL 9.5, which the other repo did not have.

After adding this repo, we are pulling additional nodejs packages that we were not getting before.  Specifically nodejs010-libuv.x86_64 and nodejs010-runtime.x86_64
These show up as a dependency of nodejs only after adding the repo.
Before:
[root@localhost ~]# repoquery --requires --resolve nodejs | sort
bash-0:4.2.46-19.el7.x86_64
ca-certificates-0:2015.2.6-70.1.el7_2.noarch
glibc-0:2.17-105.el7.i686
glibc-0:2.17-106.el7_2.6.x86_64
libgcc-0:4.8.5-4.el7.x86_64
libstdc++-0:4.8.5-4.el7.x86_64
libuv-1:0.10.34-2.el7.x86_64
openssl-libs-1:1.0.1e-51.el7_2.4.x86_64
zlib-0:1.2.7-15.el7.x86_64

After:
[root@localhost anaconda]# repoquery --requires --resolve nodejs | sort
bash-0:4.2.46-19.el7.x86_64
ca-certificates-0:2015.2.6-70.1.el7_2.noarch
glibc-0:2.17-105.el7.i686
glibc-0:2.17-106.el7_2.6.x86_64
libgcc-0:4.8.5-4.el7.x86_64
libstdc++-0:4.8.5-4.el7.x86_64
libuv-1:0.10.34-2.el7.x86_64
nodejs010-libuv-1:0.10.30-1.el7.x86_64
openssl-libs-1:1.0.1e-51.el7_2.4.x86_64
zlib-0:1.2.7-15.el7.x86_64

This addition seems to be the cause of some messages being printed when a login shell is started:
Can't read /etc/scl/conf/v8314, v8314 is probably not installed.
I'm not familiar enough with the significance of these packages to know if this is indicative on a larger issue or if it can be safely ignored
@jrafanie @simaishi ?

@miq-bot add_label wip, core

Wha?  So epel's nodejs (non) has nodejs010 (scl) as a depedency?! This is weird @bdunne @simaishi

This might be being caused by installing the repo file in the packages section rather than adding it in the post like the other repos here https://github.com/ManageIQ/manageiq-appliance-build/blob/master/kickstarts/partials/post/repos.ks.erb

Looks like the nodejs010 packages being installed won't be a problem. I will just remove the call to enable here in a follow up which will remove the error message at login.

The errors on login will be fixed when https://github.com/ManageIQ/manageiq-appliance/pull/75 is merged

@miq-bot add_label enhancement, darga/no

👍 LGTM