switch windows by opening a UI with a letter combo for every window

This is neat. Let me think about this a bit, as I've been kinda standardizing on using numbers for this sort of selections out of the box (e.g., filemanager, homophones, etc).

This turns out to be a bit unusable on Windows as-is, and I'm not exactly sure how to fix it.
There's like a billion windows that are just "Windows Explorer" - from my experience, this is things like the taskbar/clock which have no title etc.

Ideas?

@timo think you'd be able to address some of the issues raised by @knausj85 here?  lmk if you wanna brainstorm / discuss

I think the time has come to close this one. :'(
We can revisit in the future & reopen.


fabric8-setup - Use the new f-m-p plugin

to integrate with docker/f8 instead of the older f8/dmp plugins.
Look at the new quickstarts how to do this.

Look at this qs for what to change
https://github.com/fabric8-quickstarts/spring-boot-camel/blob/master/pom.xml

@rawlingsj this ticket is about the forge to use the new f8 plugin


The set-output command is deprecated and will be disabled soon

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Thanks. Investigating now.

Just wanted to ask if there are any news on this. Thanks!

v1.0.3 published. If you are using v1, next time you run the workflow it will automatically use the latest version. If you have other questions, feel free to reopen this issue.

The v1.0.3 release won't fix the issue. I think https://github.com/ilharp/sign-android-release/blob/3eb1dc9466aa3e26c2877724598e56655c7ebe7c/src/main/kotlin/Main.kt#L87 this must update and update core

Investigating.

v1.0.4 published. If you are using v1, next time you run the workflow it will automatically use the latest version. If you have other questions, feel free to reopen this issue.

My pull request only fix your build action.

v1.0.4 published. If you are using v1, next time you run the workflow it will automatically use the latest version. If you have other questions, feel free to reopen this issue.

I missed that, thank you for catching and fixing.


Readonly toggle for Drives

Use case: I would like to be able to turn on the 'readonly' flag for specific drives. This would allow to insert readonly USB drives other than CDs and read-only EFI images.
-drive if=pflash,media=disk,id=drive0,file=/…/image.img,readonly=true

When would you want a readonly USB that's not a CD? And when do you want a read-only EFI image?

I thought a read only EFI image would be appropriate for OVMF. It comes with two images; an EFI and a VARS image and only the latter should be read-write as far as I know.
Another situation would be a read-only environment like a macOS installer image.


Add library links

I didn't find info how to link libraries to the jit evaluation. So we cant use "lib:xxx" in run and eval modes.

I think that maybe we will end up wanting a different syntax than this, but this pony-like syntax is okay for now. Thanks for doing this.


only log successful ARF processing in debugmode

be consistent with pattern in the rest of ARF to only log authentication results when running in debug mode

I don't know that I want to merge this.  Logging successful authentications gives admins an audit trail.

I suppose that makes sense when that's the only logging mechanism, I was thinking of cases with hosted app and the container and/or proxy provided access log in front of the app itself. Perhaps a separate logger that can be turned down when running in such deployment scenarios?

Closing without merging for the aforementioned reason.


Transpile CommonJS -> ECMAScript

Example: https://github.com/tim-kos/node-retry/pull/87/files
Not sure if this can be done with Babel?

Example #2 would be https://unpkg.com/prop-types@15.8.1?module


Proposal: revamp listen() arguments

I propose the argument (currently only port) of listen() to be revamped as follow, solves #34 & #47.
ufrontApp.listen({
    port:2987, //optional
    path:'systemd', //optional: becomes `server.listen('systemd');`
    https: { // refer to node doc
        key: "",
        cert: "",
    },
    parserLimit: '1500kb', // pass to body-parser
    staticPaths: ['.', 'files => ../uf-content'], // becomes `app.use( express.Express.serveStatic(".") );`` & `app.use( '/files', express.Express.serveStatic(js.Node.__dirname + "/../uf-content") );``
});

Maybe staticPaths can be put in ufront config

Hm...Server's listen() function is actually quite overloaded
I am not sure what is the best way to expose the listen function properly...

Cleaning up my old issues and I think this is no longer needed.


Update sbt-bloop to 1.5.2

Updates ch.epfl.scala:sbt-bloop from 1.5.0 to 1.5.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.5.0).
You might want to review and update them manually.
docs/website/yarn.lock

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-bloop" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Codecov Report

Merging #1324 (60b71cb) into main (90a26a9) will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1324      +/-   ##
==========================================
+ Coverage   60.45%   60.60%   +0.15%
==========================================
  Files          71       71
  Lines        2526     2526
  Branches       82       82
==========================================
+ Hits         1527     1531       +4
+ Misses        999      995       -4

Impacted Files
Coverage Δ

zio-http/src/main/scala/zhttp/http/Response.scala
84.28% <0.00%> (+1.42%)
:arrow_up:

...ain/scala/zhttp/service/ServerResponseWriter.scala
90.69% <0.00%> (+6.97%)
:arrow_up:

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 90a26a9...60b71cb. Read the comment docs.


INVALID_ARGUMENT: Unable to find the relevant tensor remote_handle

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tensorflow 2.15.0.post1
Custom code
Yes
OS platform and distribution
Manjaro Linux 23.1.3, Linux Ubuntu 22.04
Mobile device
No response
Python version
3.11.6
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Hello. I am using ParameterServerStrategy to train multiple workers who have different ip addresses. When I train the model on the host machine, the training is successful. But when I try to train a distributed model, this error appears: INVALID_ARGUMENT: Unable to find the relevant tensor remote_handle. Please help me.
Standalone code to reproduce the issue
import json
import os
import sys
import pathlib
from keras.preprocessing.image import ImageDataGenerator
from tensorflow import keras
from tensorflow.keras import layers
import tensorflow as tf
import splitfolders
from tensorflow.keras.applications import ResNet50
from keras.layers import  Dropout, Flatten, Dense

tf.debugging.experimental.enable_dump_debug_info(
    "./tfdbg2_logdir",
    tensor_debug_mode="FULL_HEALTH",
    circular_buffer_size=-1)

os.environ["GRPC_FAIL_FAST"] = "use_caller"
os.environ["CUDA_VISIBLE_DEVICES"] = "-1"

cluster_resolver = tf.distribute.cluster_resolver.TFConfigClusterResolver()

def dataset_fn(input_context):

    data_dir = "/home/Kompot/Distributed_calculations/archive/raw-img/"
    data_dir = pathlib.Path(data_dir)

    train_path='./output/train/'
    val_path='./output/val'
    test_path='./output/test'

    class_names=os.listdir(train_path)

    NUM_CLASSES = len(class_names)
    BATCH_SIZE = 32
    IMG_DIM = 224

    train_datagen = ImageDataGenerator(zoom_range=0.15,width_shift_range=0.2,height_shift_range=0.2,shear_range=0.15)
    train_generator = train_datagen.flow_from_directory(train_path,target_size=(IMG_DIM, IMG_DIM),batch_size=BATCH_SIZE)

    dataset = tf.data.Dataset.from_generator(
        lambda: train_generator,
        output_signature=(
            tf.TensorSpec(shape=[None, IMG_DIM, IMG_DIM, 3], dtype=tf.float32),
            tf.TensorSpec(shape=[None, NUM_CLASSES], dtype=tf.float32)
        )
    )

    dataset = dataset.shard(num_shards=input_context.num_input_pipelines, index=input_context.input_pipeline_id)

    dataset = dataset.prefetch(tf.data.experimental.AUTOTUNE)
    # dataset = dataset.shuffle(10)

    return dataset

input_dataset = tf.keras.utils.experimental.DatasetCreator(dataset_fn=dataset_fn)

print("Waiting for workers and pss to connect...")
strategy = tf.distribute.experimental.ParameterServerStrategy(cluster_resolver=cluster_resolver)

with strategy.scope():
    modelT = ResNet50(
        input_shape=(224, 224, 3),
        include_top=False,
        weights='imagenet'
    )

    for layers in modelT.layers:
        layers.trainable = False

    y = Flatten()(modelT.output)
    y = Dropout(0.5)(y)
    y = Dense(10, activation="softmax")(y)

    modelT = keras.Model(modelT.input, y)
    modelT.compile(loss="categorical_crossentropy", optimizer="adam", metrics=["accuracy"], steps_per_execution='auto')

modelT.fit(input_dataset, epochs=10, steps_per_epoch=605)

Relevant log output
Epoch 1/10
2024-02-01 09:17:23.866528: W ./tensorflow/core/distributed_runtime/eager/destroy_tensor_handle_node.h:59] Ignoring an error encountered when deleting remote tensors handles: INVALID_ARGUMENT: Unable to find the relevant tensor remote_handle: Op ID: 2344, Output num: 1
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768243.863097783","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Unable to find the relevant tensor remote_handle: Op ID: 2344, Output num: 1","grpc_status":3} [type.googleapis.com/tensorflow.core.platform.ErrorSourceProto='\x08\x05']

ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:1 failed with UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768248.511244031","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768248.511239749","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768243.823390542","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768248.511244031","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768248.511239749","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
It is treated as a transient connectivity failure for now.
ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:1 failed with UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768248.511244031","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768248.511239749","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768243.823390542","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768248.511244031","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768248.511239749","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
It is treated as a transient connectivity failure for now.
ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:1 failed with UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768268.511226712","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768268.511222584","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768263.943495340","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768268.511226712","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768268.511222584","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
It is treated as a transient connectivity failure for now.
ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:1 failed with UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768268.511226712","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768268.511222584","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768263.943495340","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768268.511226712","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768268.511222584","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
It is treated as a transient connectivity failure for now.
ERROR:tensorflow: /job:worker/task:1 encountered the following error when processing closure: UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768283.943821199","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
ERROR:tensorflow: /job:worker/task:1 encountered the following error when processing closure: UnavailableError():failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768283.943821199","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
ERROR:tensorflow:Start cancelling closures due to error UnavailableError(): failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768283.943821199","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
ERROR:tensorflow:Start cancelling closures due to error UnavailableError(): failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768283.943821199","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]

ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:0 failed with CancelledError():Cancelled
Additional GRPC error information from remote target /job:worker/replica:0/task:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768284.014644991","description":"Error received from peer ipv4:<IP_ADDRESS>:2224","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Cancelled","grpc_status":1} [Op:__inference_train_function_16244]
This derived error is ignored and not reported to users.
ERROR:tensorflow:Remote function on worker /job:worker/replica:0/task:0 failed with CancelledError():Cancelled
Additional GRPC error information from remote target /job:worker/replica:0/task:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768284.014644991","description":"Error received from peer ipv4:<IP_ADDRESS>:2224","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Cancelled","grpc_status":1} [Op:__inference_train_function_16244]
This derived error is ignored and not reported to users.
Traceback (most recent call last):
  File "/home/Kompot/Distributed_calculations/./coordinator.py", line 123, in <module>
    modelT.fit(input_dataset, epochs=10, steps_per_epoch=605)
  File "/home/Kompot/Distributed_calculations/venv/lib/python3.11/site-packages/keras/src/utils/traceback_utils.py", line 70, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/usr/lib/python3.11/contextlib.py", line 144, in __exit__
    next(self.gen)
^^^^^^^^^^^^^^^^^^
tensorflow.python.framework.errors_impl.UnavailableError: failed to connect to all addresses
Additional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}
Additional GRPC error information from remote target /job:worker/replica:0/task:1 while calling /tensorflow.eager.EagerService/Enqueue:
:{"created":"@1706768283.943821199","description":"Error received from peer ipv4:<IP_ADDRESS>:8000","file":"external/com_github_grpc_grpc/src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"failed to connect to all addresses\nAdditional GRPC error information from remote target /job:ps/replica:0/task:0/device:CPU:0 while calling /tensorflow.eager.EagerService/Enqueue:\n:{"created":"@1706768288.511248869","description":"Failed to pick subchannel","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/client_channel.cc","file_line":3941,"referenced_errors":[{"created":"@1706768288.511243624","description":"failed to connect to all addresses","file":"external/com_github_grpc_grpc/src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":393,"grpc_status":14}]}","grpc_status":14} [Op:__inference_train_function_16244]
2024-02-01 09:18:06.505567: I tensorflow/core/framework/local_rendezvous.cc:421] Local rendezvous recv item cancelled. Key hash:<PHONE_NUMBER>0024848622

@iCosmos76 Kindly check that all IP addresses and ports specified in your cluster configuration are accurate and accessible across machines. Please ensure you're using the appropriate cluster resolver (e.g., tf.distribute.cluster_resolver.TFConfigClusterResolver) and that it's correctly configured with worker and parameter server addresses. Thank you!

Thank you very much for your help. Indeed, the machines I was trying to connect to were in the cloud and there is a firewall there that does not allow me to interact correctly with my local cluster members.

@iCosmos76 Could you please confirm if the issue has been resolved then?
Thank you!


why is retinanet so slow?

only 12.5 fps in the model zoo.

How fast did you expect it to be? It is naturally slower than Faster R-CNN w/ FPN and the official code (Detectron) of RetinaNet is only 8 fps.

but the yolact for instance segment has been more than 40fps which is based on retinanet, I don't know why....

They are very different in architectures, input resolutions, etc. You need to read the paper or the code for the detailed difference.

can pytorch or cuda support 8bit inference? it is deemed faster if support.

There are better or specific frameworks than pytorch for deployment. And as far as I know, INT8 quantization is not just convert all model weights to INT8 for inference.


Message is not available

Currently, the following page is not available.
http://www.chen9.info/fragment/messages/

That link is invalid and I update README.md to remove it...


Unable to find this integration listed in Home Assistant integration search?

Hi,
I previously installed this integration, by manually downloading the files to custom_components.
I've now deleted that directory, and reloaded HA.
This is HA 2023.5.3
However, if I go to Integrations, and try to search for Echonet, it doesn't seem to come up:

Is there some trick to making this integration appear in the integration search results in HA?

It’s because you deleted the directory, you to reinstall the directory and then do a search. Ideally you should use HACS to install it.

Is it a custom repository? I can't find this by searching in HACS

yeah its in HACS just hit download which overrode my manual download.

what am i missing?

make sure to click this

then search it there

Hi,
Just freshly installed HA 2023.06.2 and trying to get this integration added but I get an error. It seems like I have the same error that started this thread, but it looks like the HA interface is a little different now and I cant get this repo added.
If I go to Settings > Add-ons, then click the 3-dot button on the top right, then click Repositories and try to add this repo, I get an error saying it is not a valid add-on repository (see pic)

Is there some rookie mistake I have made?
Thanks

Not to worry worked it out eventually. Needed to properly install HACS (I used this guide https://www.makeuseof.com/home-assistant-install-hacs-custom-addons/) then via HACS could get ECHONETLite Platform installed.


Fix 404 error returned when calling \version\api

Currently when quorum invokes tessera endpoint /version/api, a 404 error is returned, causing quorum to use the default api version "1.0".

User error...


IPv6 address is represented by /128, not by /32

Hi,
In the IPv6 section, the doc states: "If you want to specify an IP CIDR range for a single address, apply the /32 bit mask. If you say the IPv6 address 2607:fb90:b27a:6f69:f8d5:dea0:fb39:74a and wanted to exclude that single address as a range, you would use 2607:fb90:b27a:6f69:f8d5:dea0:fb39:74a/32."
Actually, a single IPv6 address is represented by /128, not by /32. /32 is a huge range.

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

ID: 74b164a7-31c5-7cb3-c8e2-7533d375bd43
Version Independent ID: 11399252-d935-2cba-a414-a44e51e67007
Content: Location condition in Azure Active Directory Conditional Access
Content Source: articles/active-directory/conditional-access/location-condition.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@andresm53
Thanks for your feedback! We will investigate and update as appropriate.

Hi, why this was closed? I don't see that the content has been fixed. @MicrosoftGuyJFlo @SaurabhSharma-MSFT @MarileeTurscak-MSFT


Added support for creating Timestamps from Date objects

#675 675
Added static factory method to Timestamp that takes a JavaScript Date object as input
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @chafey, are you still interested in working on this? It'd be a really helpful change.

I am but super busy - my feelings won't be hurt if someone else does it

With #686 (which contains Timestamp changes for using Date object) being merged this PR can be closed.


Goals for 2015

This is just a task tracker for the next couple of weeks for my own sanity, as well as to set a (somewhat lofty) goal for myself.  Before 2015 ends, I would like to finish:

[ ] Clean up my fork of GXUI

Note: this is mostly because upstream is now unmaintained.  I'm not terribly interested in switching UI libraries, especially when GXUI has gotten me this far, so maintaining a fork seems like my best option.
[ ] Ideally, add tests and clean up anything related to the editor

[ ] Add tests to vidar
[ ] Add a key binding to run arbitrary commands

Most of our commands are currently bound to keys.  Make sure that the commands exist primarily via this "arbitrary command" system, since you should be able to do anything (even commands without key bindings) via the command box.

[x] Add find/replace logic

[ ] Ideally, include regexp

[x] Add per-package TOC

This should relate more closely to a project hierarchy.  Maybe the project view should contain a tree, including packages ... and when a project is selected, a TOC is displayed.  Per-file view would be a separate tab, in this case.

[x] Polish filesystem notifications

Right now, files changing on disk will occasionally cause the editor to crash.  This should be looked in to.

[x] File/Edit/View menu
[x] Go Imports / Fmt on write
[ ] Polish code completions

[ ] Detect gocode
[ ] Install gocode at user's prompt
[x] Filter while typing
[ ] Trigger on certain events

[x] Typing "."
[ ] Pausing for some amount of time (200ms?)

Should this just be a delay for any other trigger?

[ ] When only one completion is available, prompt in-line (i.e. as highlighted text on the same line as is being typed on)

Whelp.  Yay for shooting for the moon and not even escaping the atmosphere.
I'm getting closer.  gxui is a hard nut to crack and I severely underestimated how long it would take me to fully grok that codebase.  But now I'm fixing bugs here and there.

Hey there.
I just stumbled across your project. It looks great.
While I might not be able to maintain GXUI, I can still find time to try and help answer any questions you might have. That said, it looks like you've grasped most it already.
I might also be able to find some time to accept pull requests for simple fixes too.
Cheers,
Ben

@ben-clayton Alright, thanks for the offer.  Yeah, I've mostly figured out gxui's basic internals by now, but I'm sure I'll hit other things that I'll want to change here and there.
Some of my changes probably don't make sense as a more general library, but things like changing the offsets of code editor lines to match the tab size, when encountering tab characters, I'll make PRs for.

@ben-clayton Oh, and since I haven't mentioned it before: thanks for making gxui in the first place!  In spite of my "hard nut to crack" whining, actually making use of the library has been a breeze.  In under six months and barely more than 6k lines (counting comments and whitespace), I have a working, semi-stable editor, mostly thanks to gxui.
In case anyone ever starts actually using this editor, you deserve far more credit than I do for its existence.  Whether you want it or not.

Two things are making me close this issue:

The advent of go 1.8 and the plugin package has put a lot of focus on cleaning up the command/hook/plugin architecture, which has put off much of these goals.
The direction of vidar has changed slightly.  Tests are gradually being added as individual components are cleaned up.  There are thoughts about potentially switching to shiny in the future, which would mean cleaning up my gxui fork wouldn't be all that useful.  Things like that.


Task creation - include zipping and base-64 of code in cli tool

exh tasks create has a --code option which expects a base64-encoded string containing the zip file that includes the content of the task. The base64 encoding and zipping is up to the user today.
Would be more convenient if the cli tool is able to detect that a directory is being passed along, and the cli tool then does the zipping and base-64 encoding.

Note: base-64 encoding is done already, just the zipping needs to be done


Dashboard for viewing statistics

Find a suitable react dashboard/charting framework
Display statistics collected in GoodDollar/GoodServer#97
Display anonymized transaction data collected

@sirpy  where should this dashboard be? Do we have any kind of admin panel or it should be a part of GoodDAPP?

Probably we need a standalone app for that
On Mon, Oct 21, 2019, 4:07 PM NordWhale<EMAIL_ADDRESS>wrote:

@sirpy https://github.com/sirpy where should this dashboard be? Do we
have any kind of admin panel or it should be a part of GoodDAPP?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoodDollar/GoodDAPP/issues/727?email_source=notifications&email_token=AAFD252SVJGSEUVT2PT3NYLQPWSRDA5CNFSM4JBXNB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB2ICDQ#issuecomment-544506126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFD25ZAOFPHO77RDRKTAALQPWSRDANCNFSM4JBXNB3A
.


update solanapy

Upgrade solana library to typed version
Needed to handle the breaking changes introduced in solana-py 0.26

@michaelhly FYI


fix this

in version 0.12

Fixed in v0.13

Can you send me that file?

god damn, you are right :sweat_smile:

The problem was that I did not push that fix earlier and missed in the release.
After this gets fixed, if for some reason the app is not able to determine the bitrate for the file, it will display the result


HIVE_CANNOT_OPEN_SPLIT NoSuchKey Error when ingesting iceberg data in parallel

I'm using awswrangler==3.4.2 wr.athena.to_iceberg to ingest ~100 text files from S3 into an Iceberg table using parallel lambdas
wr.athena.to_iceberg(
    df=df,
    database=database,
    table=table_name,
    partition_cols=partition_cols,
    table_location=s3_location,
    temp_path=f"s3://{bucket}/{database}/temp/{table_name}",
    keep_files=False,
)

but I've encountered
[ERROR] QueryFailed: HIVE_CANNOT_OPEN_SPLIT: Error opening Hive split s3://bucket/prefix/temp/events/03a20c57ae9642378ad1f829f390613a.snappy.parquet (offset=0, length=504731): io.trino.hdfs.s3.TrinoS3FileSystem$UnrecoverableS3OperationException: com.amazonaws.services.s3.model.AmazonS3Exception: The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: EKWQ310403FNNWKV; S3 Extended Request ID: qIu8bN3U+alq/s

The file mentioned as NoSuchKey actually exists and I can see it in S3, albeit with a deleted marker associated with it.

Anyone has hints of what may be going wrong?

I found in the implementation that after upserting the rows, it deletes the whole folder and not just the respective file
if keep_files is False:
    s3.delete_objects(
        path=temp_path or wg_config.s3_output,  # type: ignore[arg-type]
        boto3_session=boto3_session,
        s3_additional_kwargs=s3_additional_kwargs,
    )

so that may explain.. but what would be the best practice here?

The fact that you are using parallel lambdas makes me think that there might be a race condition between them where an object is deleted by one while the other still requires it. You might want to have separate temporary prefixes to avoid this or preserve the files with keep_files=True

It looks to me Iceberg is not very robust wrt parallel writing; keep_files=True leads to duplication upon subsequent loads so I tried appending the nano timestamp to the temporary path so it's unique but now I have ICEBERG_COMMIT_ERROR error due to this

how did you overcome the above error for parallel lambdas ?

@B161851 , at first I tried invoking the ingestion lambdas synchronously in a sequence for backfill but then that's too slow. I ended up using a crawler to create a glue table over the raw data and use sql insert into... iceberg which is quicker.

@khoatrandata  can you post that code snippet, as I am tried to followed you above answer but I couldn't make it.  Can it possible  to write to the iceberg table using the lambda ?.


add missing assert

cc @wilzbach
I've no idea why the GH UI seems determined thatκόσμε is difference though... that wasn't part of what I changed.

You didn't target upstream phobos. You opened the PR against your fork.


viofs: when will it be included?

When will viofs be included as a signed driver in the virtio-win iso?

Duplicate of #126


fix: set-cookie headers overriding instead of appending

This PR does the following:

Appends headers when they are for set-cookie, instead of overriding the existing value.
Adds a test for the fix.

This change fixes a bug where multiple set-cookie headers would result in only the final one being applied. With this change, they are all applied and included.
fixes #293

Hey @james-elicx  and @dario-piotrowicz , This PR is working perfectly fine. However, when I modified the build configuration to use "npx @cloudflare/next-on-pages@1", it started utilizing the latest version 1.0.2 of next-on-pages, but I'm still encountering the same cookie error. Any idea why?


Add files via upload

@AndreLui1996 Sorry. But we alread have an implementation in Ruby.  But you can refactor this version.


Section 3: Movement and Collisions

This PR updates the movement and collisions section of the tutorial to match the previous sections.

@defreez I think this PR is ready to be reviewed. I walked through section 3 and it seemed to work with no issues. (The first time I ran it, there was a warning about a wrong ID in the map.tscn scene, but I think it fixed itself.)

There are conflicts with 01 and 02 on this branch that we will need to resolve before we can merge.

Conflicts should be resolved now.

@thompsop1sou Feel free to merge when you are ready


Reason for calling puppet.logout() in puppet.stop()?

https://github.com/wechaty/puppet/blob/b5c101ccdc664907b62993b636e2b37eaa39436d/src/mixins/login-mixin.ts#L46-L51
We noticed that in login-mixin, the stop() method calls logout(). Could you explain the reason for this behavior?
As far as I understand, if we stop a puppet, when we restart it, the session should remain and we don't need to login again. So there is no need to call logout() in stop().

The reason for calling puppet.logout() in puppet.stop() is that, the Wechaty program need to maintain the state of the Chatbot session status of whether it is logged in or not.
When the Wechaty has been stopped, the puppet system can not garantee the login state will not be changed before next wechaty start, which means that if the Wechaty do not emit the logout event to the program, the program will be highly possible in an incorrect state.
That's the reason we decided to emit the logout event when we calling stop.
In the current design, when the Wechaty start, it will either emit the login event if the bot has the logged in status, or it will emit scan event if the bot account need to be scanned to logged in.
The above design will make sure the Chatbot program can maintain a correct log in status of the bot state.
I hope it can answer your question, please feel free to let me know if you have more questions.

OK. So if my understanding is right, the puppet should not override the logout method of puppet? Where should we put the actual puppet logout implementation?

So if my understanding is right, the puppet should not override the logout method of puppet?

Your understanding is partial correct.
A puppet provider implementation can override the logout method as long as it calls the super.logout() for chain the base implementation.

Where should we put the actual puppet logout implementation?

I hope the above comment also answer this question.

So stop() calling logout() is for wechaty state maintenance. For puppet implementation we should add this just like puppet.logout()?
if (!this.isLoggedIn) {
      log.verbose(PRE, 'logout() do nothing')
      return
    }

Where do you want to our this code block into?
Please provide more information to help me understand your design.

OK. As you know we are trying to merge v0.41 puppet-whatsapp to main. When upgrading wechaty version to 1.x, we found that puppet.stop() calls puppet.logout(). It caused two problems.

Whatsapp client has already been destroyed in stop process and logout will throw an error when trying to call methods on whatsapp client.
We don't really want to logout. Calling logout() will clear the session and next time we have to scan QR to login. This is not what we want to do in stop()

Thanks for the detailed description.
I think your two points are very valuable and should be considered.
I'll think about it and update back to you soon.

After some time of thinking about this situation, I think we should stop calling logout() inside the stop() by just emit a logout event from the puppet.
Changing by this, the problems 1 & 2 that you have described will be solved, and the logout & login/scan state changes during the puppet start/stop can be managed correctly.
Please feel free to let me know what you think, and we can create a PR to solve those problems after we have the agreement.


Rename id to serial_number

Floating the idea that we rename the daemon supplied id to be it's serial_number. There are too many things called id and it was confusing me. I think the idea of a serial number, that's separate from the id's we allocate in the system, is helpful.

Closing this as it'll need to be rewritten to use the new migration style.


Highlight reference for info on consuming secrets via API

Added more information to highlight the presence of risks and best practices when consuming secrets through the API
Fixes #252

Can you submit this to the 1.0.x stream and we can merge it forward?

updated, @ryanjbaxter should I open a new Pull Request to 1.0.x branch and close this one ?

Yes

Closed via 04f59cf


uncaught error when selecting cluster permissions in 'add cluster memember' dialog

Setup

Rancher version: v2.6-ba4347297ef8984f629650979a1b3a470592f4da-head
Browser type & version: chrome Version 93.0.4577.82 (Official Build) (x86_64)

Describe the bug
When changing the cluster permission radio buttons in the 'add cluster member' dialog, an uncaught exception occurs.
    at ClusterPermissionsEditor.vue:188
    at d (runtime.js:45)
    at Generator._invoke (runtime.js:274)
    at Generator.O.forEach.t.<computed> [as next] (runtime.js:97)
    at r (asyncToGenerator.js:3)
    at l (asyncToGenerator.js:25)```

To Reproduce
running dev tools:

click on an active cluster
3 dots > edit config
click member roles
click add
change to owner

Result
Uncaught exception
Expected Result
No uncaught exception
Screenshots

Additional context

Detailed Description

Context

Pass - verified fixed in v2.6-223ec88b70d87cecee8fdbe8d98e30cf004b25d9-head


Persistence

Would love a cookie to save the order of both lists upon refresh.

This is out of dragula's scope, but you can perfectly do this around dragula, just by querying the DOM and creating the cookie.


2.4: Unexpected inference of generic

TypeScript 2.4
{
    type Left<L, A> = { value: L };
    type Right<L, A> = { value: A };
    type Either<L, A> = Left<L, A> | Right<L, A>;
    const eitherLeft = <L, A>(l: L): Either<L, A> => ({ value: l })
    const eitherRight = <L, A>(a: A): Either<L, A> => ({ value: a })

    const fn1 = (): Either<string, number> => eitherRight(1); // no error
    const fn2 = (): Promise<Either<string, number>> => Promise.resolve(eitherRight(1)); // error
}

The full error:
Type 'Promise<Either<string | number, number>>' is not assignable to type 'Promise<Either<string, number>>'.
  Type 'Either<string | number, number>' is not assignable to type 'Either<string, number>'.
    Type 'Left<string | number, number>' is not assignable to type 'Either<string, number>'.
      Type 'Left<string | number, number>' is not assignable to type 'Right<string, number>'.
        Types of property 'value' are incompatible.
          Type 'string | number' is not assignable to type 'number'.
            Type 'string' is not assignable to type 'number'.

I would not expect this code to error.
fn2’s eitherRight call is inferred to have generics <string | number, number>:

The first generic infers string from the return type of fn2
The second generic infers number from its argument

What I don't understand is where the first generic infers number from?

make it
type Left = { left: L; }
type Right = { right: R; }

https://github.com/aleksey-bykov/basic/blob/master/either.ts

Thanks, but I still don't understand why inference is working this way. It feels like a bug to me.

you started screwing things up by using the same property value both for left and right cases, if the properties were named differently you would not see it (like in my example), the reason for this problem is that type script has structural typing it means that out of 2 different declaration of value (in Left and in Right) it needs to make 1 that would fit both (in Either) which is value: L | R

scondly in the latest typescript unresolved type parameters in the right side are assisted from the declarations on the left side, i am not an expert in how it works in details, but it looks like because there is an unresolved type parameter on the right side (L which is {}) the inference mechanism is looking for the best candidate for it on the left side (string as declared), but because of what's in point 1 above it is also number hence you get string | number which typescript use to satisfy the left side expectation

i might as well be wrong about it, long story short - mind structural typing

@aleksey-bykov Thanks for that explanation.
It's still odd that it works if you remove the Promise, e.g.
    const fn1 = (): Either<string, number> => eitherRight(1); // no error

And it seems to infer the generics correctly:

But no when you wrap it in Promise:
    const fn2 = (): Promise<Either<string, number>> => Promise.resolve(eitherRight(1)); // error

i see what you mean, have no idea, although it's clear that the left side has something to do with it because as you see:
const fn1 = () => eitherRight(1); //  is () => { value: {}; } | { value: number; }
const fn2 = () => Promise.resolve(eitherRight(1)); // is () => Promise<{ value: {}; } | { value: number;  }>

there were some special typing rules specifically targeting Promise and interfaces alike, might be a consequences of this: https://github.com/Microsoft/TypeScript/pull/15104

You are running into the limits of what type inference can figure out. In the call Promise.resolve(eitherRight(1)), the compiler ends up inferring from the type Either<string, number> | Promise<Either<string, number>> (the contextual type for the eitherRight(1) argument) to the type Either<L, A> (the return type of eitherRight).  However, when the union type Either is put into another union type, we "flatten" the resulting type to Left<string, number> | Right<string, number> | Promise<Either<string, number>>. That in turn causes us to no longer "see" that we're inferring from an Either to an Either, and so we infer from each constituent in the source to each constituent in the target which ends up confusing the L and A inferences. Ideally, inference involving union types should pick a "best match" constituent and then ignore inferences from the others, but it's not clear what the algorithm for doing that would be.
In other words: It's complicated.

@ahejlsberg Appreciate the insight, because it's good to know when I'm working with a constraint of the system, and why that is. :-)

Is it possible to throw an error/warning when inference may be falling short, like it is here? I'm happy to provide type annotations, but I don't want bad inference to cause silent errors in my code.

Can't reproduce this in TypeScript 2.4.1

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Unable to update to 7.4.0 in a net 4.8 project

Nuget says the package doesn't contain any assembly reference compatible with netframework version 4.8. Previous version of mapster installed fine.

Mapster only targets .NET 6 and newer starting with v7.4.0. It's theoretically possible to target netstandard2.0 again, but some code will have to be rewritten since there are some features being used now that are not available in netstandard2.0. PR's are welcome for this one.

Thanks for the clarification on what happened @andrerav. I just recently converted from Automapper to Mapster so kind of a bummer to see this change of direction. I have a few more questions if that's okay.

This wasn't only a breaking change but a major EOL scenario. Does the project follow semantic versioning?
Do you think only a small percentage of users need netstandard 2.0 support? In other words, would a PR to bring back its support be worthwhile?
Would a PR with conditional compilation directives  https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation be a good solution?

Agree with @Jojoshua . Why do you drop the support of netstandard2.0? This is a huge break change as you drop the support for NFX which is still in maintenance, especially for a widely-use libs like this.

some code will have to be rewritten since there are some features being used now that are not available in netstandard2.0

With conditional compilation, it's originally easy to keep a fallback block for netstandard2.0. But now we have to wait for a total PR process until the next version release.

Hi @Jojoshua,

Thanks for the clarification on what happened @andrerav. I just recently converted from Automapper to Mapster so kind of a bummer to see this change of direction. I have a few more questions if that's okay.

I can definitely understand that :)

This wasn't only a breaking change but a major EOL scenario. Does the project follow semantic versioning?

That is the intention, but I agree that this is an example of breaking with that.

Do you think only a small percentage of users need netstandard 2.0 support? In other words, would a PR to bring back its support be worthwhile?

I don't have any data on that outside of issues being reported here. As far as I can tell, there is this issue and #527 that have reported the end of support for .NET Framework as problematic.

Would a PR with conditional compilation directives  https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation be a good solution?

Mapster already uses preprocessor directives numerous places (albeit some are redundant now). PR's with preprocessor directives will be as welcome as any other PR :)

Agree with @Jojoshua . Why do you drop the support of netstandard2.0? This is a huge break change as you drop the support for NFX which is still in maintenance, especially for widely-use libs like Mapster.

some code will have to be rewritten since there are some features being used now that are not available in netstandard2.0

With conditional compilation, it's originally easy to keep a fallback block for netstandard2.0. But now we have to wait for a total PR process until the next version release.

Hi @LeaFrock,
.netstandard2.0 was dropped as a compromise related to maintainability of this project. I don't principally mind adding it back in and have already signaled that PR's are welcome for this. But the final decision can only be made when we see the scale of the required change to make this happen, and how it might affect future maintainability.
With regards to preprocessor directives, we already have many of those in Mapster. So I have no qualms accepting more PR's with that. The bigger question is how it will affect future maintainability/complexity.

Hey @andrerav , I really don't know if this will work for you but here's my attempt at adding this support back https://github.com/MapsterMapper/Mapster/pull/655

@andrerav  @Jojoshua  @LeaFrock  Hello
With minor changes it is possible to release separate assemblies target to net 4.8 (4.7.2)
If this is an acceptable compromise, then I can open an PR with this solution.

Let's add this back and get a valid PR.


download page is broken

on your site download page is broken.
http://www.ppi.io/downloads/

Doesn't look broken now? Has this been fixed, @dragoonis ?

Closed :)


not finishing the installation

This section gives an error, not finishing the installation...
`
Install Webmin
RUN echo root:password | chpasswd &&
echo "Acquire::GzipIndexes "false"; Acquire::CompressionTypes::Order:: "gz";" >/etc/apt/apt.conf.d/docker-gzip-indexes &&
update-locale LANG=C.UTF-8 &&
echo deb https://download.webmin.com/download/repository sarge contrib >> /etc/apt/sources.list &&
wget http://www.webmin.com/jcameron-key.asc &&
apt-key add jcameron-key.asc &&
apt-get update &&
apt-get install -y webmin &&
apt-get clean &&
echo "$(cat /etc/webmin/webmin.acl) docker" > /etc/webmin/webmin.acl`

I have the same problem. I am ubuntu server 20.04.6. Webmin and docker are installed and working well. Anyone have a solution?

What is the error you get during install. Ive done multiple installs using the url option and the release package.
The latest one is
https://github.com/dave-lang/webmin-docker/releases/download/0.4.0/docker.wbm.gz.

What is the error you get during install. Ive done multiple installs using the url option and the release package.
The latest one is https://github.com/dave-lang/webmin-docker/releases/download/0.4.0/docker.wbm.gz.
Try using either the file upload or Http URL method from https://webmin.com/docs/modules/webmin-configuration/#installing

I have tried to install the module too, and the error I get is "Not a vaild Perl module"
The logs :
Downloading https://github.com/dave-lang/webmin-docker/releases/download/0.4.2/docker.wbm.gz ..
Downloading https://objects.githubusercontent.com/github-production-release-asset-2e65be/661591323/cd631556-def8-4e2b-b899-48a4d04ab290?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=releaseassetproduction%2F20240602%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240602T203006Z&X-Amz-Expires=300&X-Amz-Signature=647e70e104857e6e4d1701edc53bd781634c80a4aa29b578724a00420e04500c&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=661591323&response-content-disposition=attachment%3B%20filename%3Ddocker.wbm.gz&response-content-type=application%2Foctet-stream (3.32 KiB) ..
     Received 1 KiB (30 %)
     Received 1.34 KiB (40 %)
     Received 2.34 KiB (70 %)
     Received 2.69 KiB (80 %)
     Received 3.32 KiB (100 %)
.. download complete.

Failed to install module : Not a valid Perl module

Thanks for at confirming the install works :)
I'm going to close this - the docker script works for testing & the install package seems to be fine.


Semantic highlighting regressions from the switch from ClangSymbolKind to lsSymbolKind

The switch from ClangSymbolKind to lsSymbolKind brought with it a couple of semantic highlighting regressions:

Local variables and parameter variables are no longer distinguished. lsSymbolKind does actually have separate Variable and Parameter entries, but they have the same numerical value. Proposed solution: give Parameter a distinct numerical value.

Template parameters and typedefs are no longer distinguished, they both use lsSymbolKind::TypeParameter. Proposed solution: introduce lsSymbolKind::TypeAlias, and use it for typedefs.

Proposed fixes in #470.
I made one additional change: I changed the symbol kind of non-type template parameters from Parameter to TypeParameter. The rationale for this is that I think non-type template parameters have more in common with type template parameters, than with function parameters.

J'espère aussi

The rationale for this is that I think non-type template parameters have more in common with type template parameters, than with function parameters.

LG.


Added overview article for Aiven Console

What changed, and why it matters
Added an overview article for the Aiven console and included information on the new console header changes.
Resolves #1429

LGTM


Echo popups in mobile view offset out of screen

Setup

Browsers and versions: Firefox mobile
MediaWiki version: 1.30
Pivot version: latest
Extension version (if connected to the issue): Echo

Issue
With the pivot theme the Echo extension popups are strangely offset to be partially out of the screen to the left when viewing the site in a mobile phone. This makes them effectively not usable.

What version of Echo are you using?

Latest development master from the github repository.

You should checkout branch REL1_30, but that is broken too. Echo is a serious pain point for all custom skins. The developers kept changing code as if the extension is in continuous development without any regards for any skin but Vector. If you rotate the mobile device, the drops realign correctly and are readable. Vertical, not so much because the left position is set to a negative number in the element.
I won't have time to look at this (my every 6 month task to FIX it) until early next week. Then I have to walk the fine line of will it break 1.27 version by fixing 1.30 version.

Echo is a serious pain point for all custom skins.

without words. I believe to remember that they send out some info a fortnight or so ago about changes ... :|

My main issue with this group is they don’t care. All they do is say well it’s not really developed for any other skin but vector and end of discussion.

Closing


[iOS] Application Rate limit exceeding

🐛 Bug Report
Hello.
I have bug with Rate Limiting.
Most of the time I see rate limit exceeding but I don't understand why.
I use only react-native-fbsdk-next(sdk) for my ios application. I don't use any FB API's at all.
DAU is max 2500 users a day.
What is the endpoint gr:get:Application?
Why does it use so often?

To Reproduce
I see how "call count usage rate" increased every time when I start my app.
Expected Behavior
Limit use is not exceeding
Code Example
I install the sdk according the docs.
I checked it on 11.1.0, 11.2.0 and 11.2.1 versions
There are only two place where I use the sdk.
to init in AppDelegate.mm and track event in analytics.js
That's it!
AppDelegate.mm
`

(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
self.moduleName = @"app";
self.initialProps = @{};
[[FBSDKApplicationDelegate sharedInstance] application:application
didFinishLaunchingWithOptions:launchOptions];
[super application:application didFinishLaunchingWithOptions:launchOptions];
center.delegate = self;
return YES;
}

(BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
if ([[FBSDKApplicationDelegate sharedInstance] application:app openURL:url options:options]) {
return YES;
}
if ([RCTLinkingManager application:app openURL:url options:options]) {
return YES;
}
return NO;
}
`

analytics.js
`
import { AppEventsLogger } from 'react-native-fbsdk-next';
export const trackEvent = (event) => AppEventsLogger.logEvent(event);
`
-->
Environment

Please Help!

Unfortunately I don't think we can be much help here. This is a pretty thin wrapper over the underlying facebook-ios-sdk and facebook-android-sdk
You might post directly on those repos or try on stackoverflow, or inspect your project even more closely
This module just wraps the APIs and translates the javascript calls you make into the corresponding native ones, and as such you are in control of the rate you call things and the underlying SDKs make the calls to the cloud services. So nothing about this question will result in a change to the module and as such is not really an issue here

Okay, thanks anyway


Handle user refreshes

Task/Issue URL: https://app.asana.com/0/1204920898013511/1208572901396836/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5213  👈
#5187
#5172
#5171
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CrisBarreiro and the rest of your teammates on  Graphite


Camera for iOS is not working in inside webview

I tried to access the iOS camera within webview. but it's not working as expected. It's working fine in the Safari browser in iOS, Chrome browser in Android, and android webview. However, nothing happens inside webview in iOS. I granted required permissions like camera or audio, however, it still does not work.

The same issue

On iOS-Devices camera access works only in native Safari and not in other Browsers (Chrome,...) or Apps that use an UIWebView or WKWebView. This is not a restriction of this component but of the limited WebRTC support by Apple.
This is still not resolved on iOS 14, if you want to stay updated on this topic, please refer to this thread.

@SimonBellucci So we don't have access to getUserMedia in Web View, but why does the docs say we can use NSCameraUsageDescription ? I was just wondering is there a way to open camera in IOS in web view?

the same issue here

iOS 14.3 Supported
https://developer.apple.com/forums/thread/88052
Hope this will help!

https://user-images.githubusercontent.com/8758774/107483768-567ff600-6ba3-11eb-95e5-fd826340f9ab.mp4
For me the camera opens up if I pass in the prop mediaPlaybackRequiresUserAction={false}.  The camera is still open in the background so if you point it to a QR code, it scans it.

Attachment_1612945361.mp4
For me the camera opens up if I pass in the prop mediaPlaybackRequiresUserAction={false}.  The camera is still open in the background so if you point it to a QR code, it scans it.
Edit: Adding the prop allowsInlineMediaPlayback and removing the mediaPlaybackRequiresUserAction prop seems to have fixed it.

Can you please show the code because i am doing all the things but not working

Attachment_1612945361.mp4
For me the camera opens up if I pass in the prop mediaPlaybackRequiresUserAction={false}.  The camera is still open in the background so if you point it to a QR code, it scans it.
Edit: Adding the prop allowsInlineMediaPlayback and removing the mediaPlaybackRequiresUserAction prop seems to have fixed it.

Can you please show the code because i am doing all the things but not working

Just add the props
allowInlineMediaPlayback={true}
mediaPlaybackRequiresUserAction={false}

On iOS it doesn't work on older iOS versions so I just listen to URL change events and open up a scanner using react-native-barcode-scanner on the correct URL.

Attachment_1612945361.mp4
For me the camera opens up if I pass in the prop mediaPlaybackRequiresUserAction={false}.  The camera is still open in the background so if you point it to a QR code, it scans it.
Edit: Adding the prop allowsInlineMediaPlayback and removing the mediaPlaybackRequiresUserAction prop seems to have fixed it.

Can you please show the code because i am doing all the things but not working

Just add the props
allowInlineMediaPlayback={true}
mediaPlaybackRequiresUserAction={false}

On iOS it doesn't work on older iOS versions so I just listen to URL change events and open up a scanner using react-native-barcode-scanner on the correct URL.

Okay then how you send scanned data to web?

Camera does not work as simple Web View for IOS, please help:

Attachment_1612945361.mp4
For me the camera opens up if I pass in the prop mediaPlaybackRequiresUserAction={false}.  The camera is still open in the background so if you point it to a QR code, it scans it.
Edit: Adding the prop allowsInlineMediaPlayback and removing the mediaPlaybackRequiresUserAction prop seems to have fixed it.

Can you please show the code because i am doing all the things but not working

Just add the props
allowInlineMediaPlayback={true}
mediaPlaybackRequiresUserAction={false}

On iOS it doesn't work on older iOS versions so I just listen to URL change events and open up a scanner using react-native-barcode-scanner on the correct URL.

Could you display  how to do this for us? Please i need to do this in two times during execution webview, one time with QR scanner and other with barcode scanner. Please helpme.

Dont work here too. IOS 14

Hello.
I need to show the camera within a web but, using the WKWebView configuration that you mention, a modal view is opened with the camera.
Any solution for this problem?
Thank you.

hey guys, finally it works fine in IOS >= 14.6

hey guys, finally it works fine in IOS >= 14.6

What about the previous iOS versions? Is there a workaround?

We are currently facing a similar problem, but not quite the same as the one reported here.
With allowInlineMediaPlayback enabled and mediaPlaybackRequiresUserAction disabled (this one was a problem on Android), after we ask for camera access on iOS, the camera simply does not load.
After we restart the app, the user is prompted with the webview's request to access the camera (not the SO one, but the one the browser does). And it works.
We would like to know why we need to restart the app in order to work.

hi, @anhvoduy. It is on iOS only. But the camera works after the app is restarted.
I've created a new issue, as it seems to be working properly after the reset, which was not the case here.
To Reproduce:

Render the webview.
Send a postMessage to ask native code to request camera permission.
Grant permission.
Webview's getMediaDevices() fail.

Here is the configuration:

Up, does anyone have a solution please?

My use case is described on the linked issue. It happens when you grant the app level permission with the webview already created. The webview is unable to even access the list of media devices.

Thanks for clarifying, I understand now. That's indeed different form what I'm trying to do. I hope you'll find a solution and the issue gets resolved.

hey guys, finally it works fine in IOS >= 14.6

Worked for me, thanks

@muskan6898  I am facing the same issue in Andriod
I had given permission as well before calling and I am getting error as getusermedia error not readable error
"react-native-webview": "13.2.2",

<WebView onLoadStart={()=>{console.log("Start")}}

userAgent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36"
source={{
uri: '',
}}
originWhitelist={['*']}
sharedCookiesEnabled={true}
allowsInlineMediaPlayback
javaScriptEnabled
scalesPageToFit
allowInlineMediaPlayback={true}
mediaPlaybackRequiresUserAction={false}
bounces={true}
startInLoadingState
javaScriptEnabledAndroid
geolocationEnabled={true}
useWebkit
/>


Add component setup and dimension hints

Just some small additions which I missed at first.

I think you should specify that the actual pixel size depends on the grid size, as seen here
https://github.com/dattn/dnd-grid/blob/master/src/demo.vue#L81

So,
gridSize: {
  w: 101
}

and
position: {
  w: 2
}

results in 202 pixels?

Yes.
The position property, represents the position in the virtual grid.
And the size of one cell in this grid is defined with the gridSize property.

Please see my latest commit.

Looks good to me

Thank you for the pull request.
All Pull request should go to the develop branch, because my master branch represents the latest released version :)


fix finding existing containers

when looking for containers to clean up the name was truncated in the docker ps command.  using --no-trunc avoids truncations and allows the name to be found.

@gdams I thought you've moved all the docker code over to openjdk docker, or does some still remain here?

This is the docker based build rather than the docker images that we create


Add client-config validation route

GET : /api/v1/config/validate
With 2 possible parameters:

url: url of hosted config (like on github/gitlab/web server, watever)
file: file name of configuration file hosted in config directory on host (require --client-config-directory parameter)

See: https://eagain.net/articles/go-dynamic-json/

https://github.com/Jeffail/gabs


Add undefined behaviour sanitizer

While Valgrind is pretty cool, there can't be too many tools checking for potential undefined behaviour. We could add the undefined behaviour sanitizer to the Debug mode:

[x] Don't use it with MinGW since it is not supported.
[x] Use it with GCC on Linux.
[ ] Use it with Clang.

Unfortunately, in order to properly link the undefined behaviour dependencies with Clang, we have to make sure that Clang uses its own linker instead of ld. Help welcome if anyones knows how to do that with CMake.

http://stackoverflow.com/questions/1867745/cmake-use-a-custom-linker ?(2nd answer esp.)

Yeah, I read that one, but actually finding where the correct linker is is a difficult task by itself: apparently, there was something called llvm-ld until Clang 3.2, then they dropped it and it appears that something called lld exists nowadays. Not sure how to make CMake find it without giving a raw path.
The Clang page about ub-chan isn't really helpful either as it doesn't tell how we can link things:

Make sure to use clang++ (not ld) as a linker, so that your executable is linked with proper UBSan runtime libraries.

Try cooking the path

Haha, I've not the slightest idea what that's supposed to mean :D

Not sure how to make CMake find it without giving a raw path.

Try cooking it.

I...

Apparently thee problem comes from LLVM, so there isn't much we can do about it right now. It should be fixed in a near future though. Classing the issue as future until it works out-of-the-box with Travis.


Hyprland freezes after a random amount of time

Hyprland Version
Hyprland, built from branch  at commit 4ef684f6153c167afd6e84c01a814f46d9f287ae  (). Tag: ?  flags: (if any) debug
Bug or Regression?
Bug
Description
Hyprland freezes after a while of use could be like 1 minute to 6 hours, I think it's related to NVIDIA? The reason why I think this is because of the fact if I'm watching netflix and screensharing on discord it will freeze for a moment and then unfreeze.
Freezing meaning: My whole computer freezes no input and audio is still playing
How to reproduce
I would have no clue how to reproduce this because it's just simply random it seems but it might be related to #2742
Crash reports, logs, images, videos
hyprlandCrashReport120065.txt

Same issue here, also on Nvidia. My audio stops too though. Complete lock up

What version of nvidia are you using? I was using open driver and now that I'm not it doesn't crash anymore

Using dkms, with Nvidia patch.
Was crashing on regular proprietary without the patch as well

Same issue here, also on Nvidia. My audio stops too though. Complete lock up

What version of nvidia are you using? I was using open driver and now that I'm not it doesn't crash anymore

Update is that they still happen sadly

NVIDIA GeForce GTX 1660

isn't this dupe of https://github.com/hyprwm/Hyprland/issues/2742 ?

Same for me, using an rtx 3060TI
It seems a bit different than #2742 because i can't even move cursor
Everything on screen freezes, sound is still playing though

maybe it's due to software cursors, but that doesn't make much sense either
still OP didn't report the mouse thing so you might want to open a separate issue

maybe it's due to software cursors, but that doesn't make much sense either
still OP didn't report the mouse thing so you might want to open a separate issue

The mouse won't move at all when frozen yeah

is it still happening on latest build tough?

is it still happening on latest build tough?

I switched to latest git version yesterday, and haven't noticed any freeze since, but I have only used the computer for like 3 hours today so it might not be representative

It just happened once more so it's not fixed

please move to the main thread (https://github.com/hyprwm/Hyprland/issues/2742)

with or without mouse moving? if mouse stuck please move to the main thread (#2742) otherwise create a new issue

This thread is for without the mousing being able to mowe

still happening or magically went away?

still happening or magically went away?

Didn't happen to me since my last message.
I'm pretty sure it was some kind of OOM and it may not be related to hyprland.
I was playing a lot of modded minecraft at the time and I noticed that after closing the game window, the java process stayed here, taking ~12go of ram. I believe the freeze happened when I :

played mc for a couple hours
then closed the game
and then started a memory consuming process later

This kind of checks out as it didn't happen a single time since I stopped playing.

still happening or magically went away?

I updated my nvidia drivers and it went away, but maybe an update to hyprland fixed it too? I don't really know but it's fixed for me now.

closing then. Nvidia stuff

Same issue here.

I'm using an AMD Laptop and having this problem also.


Understand and fix rever ("news" workflow)

Background
@ggarrett13 originally set up the rever tool for both tudat and tudatpy. Rever is a tool to manage release versioning, based on the news workflow where each contributor maintains a changelog. An (unfinished) page on the tudat developer docs gives info and reference about this.
Latest updates
The news workflow has not been used by contributors until now. Following the last developer meeting, it was decided to start releasing versions of tudat and tudatpy in a sound manner. The rever tool could greatly help in this direction.
What has been done
I have tried using rever both on tudat and tudatpy, but after some debugging the tool still outputs errors. It seems that a version was released through rever.
Issues

The tool produces errors that I have not been able to solve
In general, despite the documentation, I have not been able to fully understand the functioning of rever and the news workflow

For both points, some help from @ggarrett13 would be greatly appreciated.
Note 1
If the issues are too difficult to be solved, we can also decide to release software versions manually (i.e., via Github and git tags), as I see no problem with that. However, if we manage to understand rever and get it to work, the project would be improved as keeping track of the software development over time (through the rever-generated changelog) would be easier.
Note 2
Until a decision is not made on this, no changelog nor guidelines on what to do when developing software will be released (see minutes on Slack from last tudat developer meeting).

Output from rever (on tudatpy):
tudat-multidoc) foggionni@mac-foggionni tudatpy % rever 0.6.0
<unknown>:1: DeprecationWarning: invalid escape sequence \s
Activity 'authors' has already been completed!
Activity 'changelog' has already been completed!
Activity 'push_tag' has already been completed!
Activity 'tag' has already been completed!
Activity 'version_bump' has already been completed!
activity-start:forge:starting activity forge
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
From https://github.com/FilippoOggionni/tudatpy-feedstock
 * branch            master     -> FETCH_HEAD
Already up to date.
From https://github.com/tudat-team/tudatpy-feedstock
 * branch            master     -> FETCH_HEAD
Already up to date.
fatal: A branch named '0.6.0' already exists.
activity-error:forge:activity failed with exception:
Traceback (most recent call last):
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/rever/activity.xsh", line 83, in __call__
    self.func(*args, **kwargs)
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/rever/activities/forge.xsh", line 248, in _func
    git checkout -b $VERSION master or git checkout $VERSION
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/xonsh/built_ins.py", line 202, in subproc_captured_hiddenobject
    return xonsh.procs.specs.run_subproc(cmds, captured="hiddenobject", envs=envs)
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/xonsh/procs/__amalgam__.py", line 3585, in run_subproc
    command.end()
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/xonsh/procs/__amalgam__.py", line 928, in end
    self._end(tee_output=tee_output)
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/xonsh/procs/__amalgam__.py", line 947, in _end
    self._raise_subproc_error()
  File "/Users/foggionni/opt/miniconda3/envs/tudat-multidoc/lib/python3.8/site-packages/xonsh/procs/__amalgam__.py", line 1069, in _raise_subproc_error
    raise subprocess.CalledProcessError(rtn, spec.args, output=self.output)
subprocess.CalledProcessError: Command '['git', 'checkout', '-b', '0.6.0', 'master']' returned non-zero exit status 128.
rewinding to 340c22a885f98236bd379b46d99c89e81b6c7df6

Still forming a solution to this such that tudat and tudatpy can release simultaneously. Managed to get the rerendering automated via GitHub workflows, a step in the right direction.

Currently fixing the email addresses in tudats commit history so that the authors feature of rever works. Many commits had<EMAIL_ADDRESS>for multiple users, and only one person can map to an email. Lot's of fun.

Anonymous emails have been resolved, git history has been modified with some interesting by products:

This branch is 3744 commits ahead of Tudat:master.


Help with calling curl commands

New to rust here and was hoping someone could offer some guidance...
All I'm trying to do is make a couple of curl requests via Firebase's rest API. I'm trying to POST and PUT.
As stated in the firebase docs linked above, a curl POST is as simple as:
curl -X POST -d '{"user_id" : "jack", "text" : "Ahoy!"}'
'https://[PROJECT_ID].firebaseio.com/message_list.json'

And a PUT is just:
curl -X PUT -d '{ "first": "Jack", "last": "Sparrow" }'
'https://[PROJECT_ID].firebaseio.com/users/jack/name.json'

Following the docs I tried doing this, but had no luck. Any suggestions?
let mut data = "this is the body".as_bytes();
let mut easy = Easy::new();
easy.url("https://[PROJECT_ID].firebaseio.com/users/jack/name.json").unwrap();
easy.post(true).unwrap();
easy.post_field_size(data.len() as u64).unwrap();

let mut transfer = easy.transfer();
transfer.read_function(|buf| {
        Ok(data.read(buf).unwrap_or(0))
    }).unwrap();
transfer.perform().unwrap();

Extra: What if I wanted to post a json like such?
let mut test_data = format!(r#"{{"url": "{}", "category": "{}"}}"#, "https://google.com", "category");

I might recommend the verbose setting to help debug curl itneractions, and you may also want to try post_fields_copy which I've had some better luck with in the past. You'll also want to use write_function on the transfer() to read the response.
Does that help track this down? (new examples for this repo would be very much appreciated!
For PUT I think you'd do most of the above and then set custom_request

I'm going to close this since I believe it's all covered.


Support the Retry-After header in PollLastOperation as per the OSB spec

The response for PollLastOperation  MAY also include the Retry-After HTTP header. This header will indicate how long the Platform SHOULD wait before polling again and is intended to prevent unnecessary, and premature, calls to the last_operation endpoint. It is RECOMMENDED that the header include a duration rather than a timestamp.

This was added in v2.15 of the spec, this library currently only supports the OSB spec up to v2.14. There will be a concerted effort to bring this library fully in line with v2.15, similiar to https://github.com/kubernetes-sigs/go-open-service-broker-client/issues/144.

Part of #161

@jberkhahn @mszostok Can we close this issue in favour of #161?

Sure.


Incompatible with glimmer

On a fresh install of glimmer, (ember init -b @glimmer/blueprint), upon running ember serve, I encounter the following error:
app.import is not yet implemented for GlimmerApp
Error: app.import is not yet implemented for GlimmerApp
The error only occurs after running ember install ember-redux
ember-cli: 2.14.0-beta.2
node: 6.10.3
os: darwin x86

This addon only supports ember - I think other people are spiking on a glimmer-redux addon if you want to checkout the glimmer channel on slack

I just published glimmer redux if you are still interested
https://github.com/glimmer-redux/glimmer-redux


Add edk2 plugin

Hi, we've been working to create a plugin for Ceedling which makes testing EDK2 projects easy. It would be really neat if this could be pulled into the main Ceedling project. At the moment we have it working for our internal EDK2 projects, but clearly it needs 'cleaning-up'. Feedback on how to improve the plugin from a high level would be greatly appreciated. Primary focus is on overall flow and the edk2.rake plugin file.
High Level Plugin Overview:
EDK2 build process is incredibly challenging due to high level of modularity and build magic. This plugin will automatically parse an EDK2 module's (.inf) build descriptor files, gather the include paths, and create the AutoGen(.c/.h) build files. The end result is to create the AutoGen files and a user.yml file which contains the necessary include paths for the module being unit tested.
The overall plugin flow is as follows:

Invoke ceedling test:mod[path/to/edk2module.inf]
Ceedling starts and enters EDK2 plugin.
Plugin parses the edk2module.inf and the files it references.
Plugin creates user.yml (in same dir as project.yml) and AutoGen files (+other EDK2 support files) are placed in the Ceedling build directory
Plugin 're-invokes' ceedling test:all which uses previously created user.yml for test files and include paths.
Test completes and reports pass/error

Still Need:

Examples with Open Source Edk2 project, we have internal examples, but code is sensitive so can't expose them.
Documentation (working on it).
Meet Ceedling coding standards.

Current concerns:

Plugin starts a subprocess to invoke Ceedling after setting up the user.yml. This is pretty hacky, but I couldn't find a cleaner way; performing modifications to the @ceedling[:configuration] seemed worse (and I couldn't get it working).
Need unit tests/integration tests. I'm not a Rake or Ruby expert, guidance on the best practices here would be appreciated.
We want to be able to make changes to the plugin, it would be preferable if the plugin could be a submodule of the /plugins folder and we will maintain the plugin in our repo. Understandable if this is not preferred, we're flexible.
There is a python support tool for generating EDK2 build magic files, it would be challenging to rewrite this as Ruby.

Feel free to ask any questions, I understand that the quality of the code and documentation is mediocre at the moment, but before we start polishing I wanted to make sure we're not headed down a bad path.
Thanks,
Erich

I am sorry this PR has lingered open for so long, @Erich-McMillan. Thank you for all this work. EDK2 is new to me. It's incredible how many significant and useful projects like EDK2 are out there that developers in one area (like me) may never encounter in another.
This plugin submission was developed for the previous major version of Ceedling, 0.3x.x. A major revamp that is 1.0.0 is nearing release. So much has changed that this plugin submission will no longer conform, and the core plugin structure itself will be revamped in a future major release. 0.3x.x will not be supported much longer.
I hope and suspect that changes to Ceedling for 1.0.0 will support the answers to the open questions you have.
However, ultimately, I suspect that EDK2 support would work best as a plugin project external to Ceedling. Ceedling can support plugins external to itself. All of Ceedling's built-in plugins support general purpose developer needs. EDK2 seems a very domain specific project. I don't think it fits the (unstated) criteria for a built-in plugin in addition to no longer matching Ceedling's structure.


apple syscall touches registers for no reason

In syscall.c, _start, or somewhere else? It uses same code as Linux unless I'm mistaken, right?

OS X uses the stack for syscalls iirc

I think that's true for i386, though I can't test since I don't have an i386 box right now - I'll try to grab one - in the case of x86_64 though I'm fairly sure it uses the same ABI for system calls as Linux (System V w/ AMD64 support).  Maybe I'm mistaken though? I know general function calls pass parameters either in GP registers and/or stack though - and reserves stack space if you use GP registers (I think?).

More info: https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/LowLevelABI/140-x86-64_Function_Calling_Conventions/x86_64.html#//apple_ref/doc/uid/TP40005035-SW1

I'm in the process of improving processor configuration at build time (and adding preliminary mips support) so even if it only applies to x86, it still matters here as I'm actually able to build/run 32-bit lib43 on OS X now.

Okay cool - was just curious :)

i386 syscall prologue probably be changed to pop eax?

Agreed.  Will also need to make sure OS X sys calls using i386 ABI don't add the 2 << 30 offset we add to 64-bit - it's only used for 64-bit sys calls

grr, i386 is broken on OS X. Try the latest master with -DCPU=i386

Fun! Do you want to fix it, or do you want me to submit a pull req to?

I'm not sure what exactly is breaking (I already fixed the _start), it does make it to syscall() before it hangs.
I'm in the middle of moving syscalls from C to assembly (now that the arch stuff is more fleshed out) so you shouldn't pull req just yet if it comes to that.

Sounds good - I'll have a look and then need to run some errands - but I'll check out where things are this evening and can submit pull req to fix it then unless you already have it taken care of if that works?
Oh also let me know if you have any issues w/ arm pull req - I can fix merge conflicts once you update stuff on that one if you'd prefer as well - thanks.

After my updates today (especially with mips support), the arm pull request will hopefully just need to be syscall and crt0 _start asm blobs (besides the div stuff).
You should take a look at my updates to CMakeLists, as I did change it a bit for sanity.

Yeah - I figured as much - that's a good thing! The div stuff I'm going to do in separate commit in day or two because I want to optimize it so it isn't slow/crappy and it handles all the corner cases, for now just planning to send pull req for armv7+
Yeah I saw that - it's a lot cleaner now and it's going to be easier to support multiple architectures which will be nice.
Cool - I'll hold off on making any more pull reqs for now then and just wait for you to finish your refactoring.  Could you just let me know over this or twitter once you're done so I know when I'm good to go?  Thanks!

Fixed by e07c45de562cd550c1cbd0b6820c66bbebee19ec


Separates the Aurelius Tests from the main Test Project

This allows to run the main test project without having the TMS Aurelius library

:+1: