Question about counter labels and aliases

Hello,
This is a follow-up from https://github.com/G-Research/aeron/issues/1192.
We tried appending the alias parameter to our subscription requests and publication requests. This worked OK but there is a small issue when reading counter labels corresponding to subscriptions in some cases.
When reading publisher counters we get labels like:
pub_pos: ... <channel>|alias=<publisher_alias> @...
This allows us to identify the publisher easily - no ambiguity.
When reading subscription counters we get labels like:
sub_pos: ... <channel>|alias=<publisher_alias>|alias=<subscriber_alias> @...
This is still OK if both the publisher and the subscriber have registered with an alias - the subscriber alias appear last.
The difficulty we're having atm is, if only one of the subscriber/publisher is using an alias (it's difficult for us to demand all subscriptions and publications provide an alias when registering), in the second case (reading a subscription counter), we cannot tell if the alias parameter is coming from the subscriber or the publisher.
We experimented with using two separate params: pub_alias for publishers and sub_alias for subscribers. This seems to work, but want to check with you if this is OK (specially because alias is the recommended way)? Perhaps there is a way to use alias still and be able to distinguish the source (publisher or subscriber) in all cases?
Our aeron-client version (C) is: 1.23.1
Media driver version: 1.29.0
Many thanks.
/ Asiri

I don't understand how you think you have publisher alias on the subscription counter. Can you further explain?

I don't understand how you think you have publisher alias on the subscription counter. Can you further explain?

Hi Martin.
My counters scanner looks something like this:
        counters.forEach([&](int32_t counter_id, int32_t type_id, const aeron::AtomicBuffer &key_buffer, const std::string &label)         {             switch (type_id)             {                 case PUBLISHER_POSITION_TYPE_ID:                     Log.info() << "Publisher position counter label: " << label;                     return;                 case SUBSCRIBER_POSITION_TYPE_ID:                     Log.info() << "Subscribe position counter label: " << label;                     return;                 default:                     // Ignore other counters                     return;             }     }
The label printed for the publisher only has one alias set - but the one printed for the subscriber has two of them in the label. It looks like the subscriber's alias and the corresponding publisher's alias (the publication to which this subscriber is subscribed to) both appear in the label for the SUBSCRIBER_POSITION_TYPE_ID counter.
Let me revert the hack above (pub_alias and sub_alias) and double check that this is correct.
Thanks.
/ Asiri

Hi Martin.
My counters scanner looks something like this:
        counters.forEach([&](int32_t counter_id, int32_t type_id, const aeron::AtomicBuffer &key_buffer, const std::string &label)         {             switch (type_id)             {                 case PUBLISHER_POSITION_TYPE_ID:                     Log.info() << "Publisher position counter label: " << label;                     return;                 case SUBSCRIBER_POSITION_TYPE_ID:                     Log.info() << "Subscribe position counter label: " << label;                     return;                 default:                     // Ignore other counters                     return;             }     }
The label printed for the publisher only has one alias set - but the one printed for the subscriber has two of them in the label. It looks like the subscriber's alias and the corresponding publisher's alias (the publication to which this subscriber is subscribed to) both appear in the label for the SUBSCRIBER_POSITION_TYPE_ID counter.
Let me revert the hack above (pub_alias and sub_alias) and double check that this is correct.
Thanks.
/ Asiri

It looks like your subscribers are adding the alias to the publication URI. This is not something Aeron would be doing.

It looks like your subscribers are adding the alias to the publication URI. This is not something Aeron would be doing.

Sigh, you are absolutely right - totally missed that. Sorry for the noise.
/ Asiri

Sigh, you are absolutely right - totally missed that. Sorry for the noise.
/ Asiri

No worries. :-)

No worries. :-)


Fix MacOS CI build

The CI for MacOS is failing with the following error:

Run ./../.github/actions/setup-python
Version 3.9 was not found in the local cache
Version 3.9 is available for downloading
Download from "https://github.com/actions/python-versions/releases/download/3.9.19-9003651947/python-3.9.19-darwin-x64.tar.gz"
Extract downloaded archive
/usr/bin/tar xz -C /Users/runner/work/_temp/30956dbd-18a3-4d83-ab1e-c9c58f5285d3 -f /Users/runner/work/_temp/08089b6f-ddc6-49a3-b2e9-e6c68dd601a0
Execute installation script
Check if Python hostedtoolcache folder exist...
Create Python 3.9.19 folder
Copy Python binaries to hostedtoolcache folder
Create additional symlinks (Required for the UsePythonVersion Azure Pipelines task and the setup-python GitHub Action)
Upgrading pip...
Error: dyld[2930]: Library not loaded: /usr/local/opt/gettext/lib/libintl.8.dylib
  Referenced from: <64474517-EFC0-32F5-93D6-1C4BAE8783F9> /Users/runner/hostedtoolcache/Python/3.
Error: 9.19/x64/bin/python3.9
  Reason: tried: '/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/usr/local/opt/gettext/lib/libintl.8.dylib' (no such file), '/usr/local/lib/libintl.8.dylib' (no such file), '/usr/lib/libintl.8.dylib' (no such file, not in dyld cache)
./setup.sh: line 53:  2930 Abort trap: 6           ./python -m ensurepip
Error: The process '/bin/bash' failed with exit code 134

I believe this is because macOS-latest has switched over to being ARM64 (as mentioned here) and we are specifically installing an x64 version of python 3.9 in build.yml.


"MCapstone is not a function" error after manual build

After manually building the library with Grunt and Emscripten, using both capstone.min.js and capstone-x86.min.js, without adding any extra JS code:
capstone-x86_new.min.js:7 Uncaught TypeError: MCapstone is not a function
    at capstone-x86_new.min.js:7:13
(anonymous) @ capstone-x86_new.min.js:7
capstone_new.min.js:535 Uncaught TypeError: MCapstone._malloc is not a function
    at new Capstone (capstone_new.min.js:535:37)
    at main.js:7:18

Likely you are using an incompatible (newer?) Emscripten version.
Emscripten has changed a lot over the years which means quite some maintenance burden for me, so I'm not going to update the build scripts unless we have a significant reason to do so (PRs are welcome though!).
Try to use whichever Emcripten version was latest as of the date of the latest release: 2027-02-01

Using Python 3.8.10 and latest Emscripten (3.1.9).
Looks like there are no changes needed. the output JS is good, only usage is a bit different.
There were probably some changes to Emscripten usage for MODULARIZE=1 option - module usage is documented here.
cs.MCapstone.then(instance => {
    MCapstone = instance;

    // Continue normally from here
    const capstone = new cs.Capstone(cs.ARCH_X86, cs.MODE_64);
    const code = new Uint8Array([0x55, 0x31, 0xD2, 0x89, 0xE5, 0x8B, 0x45, 0x08]);
    const instructions = capstone.disasm(code, 0);
    console.log(instructions);

})

This works 🙂
I suggest updating the example in the Readme accordingly.


Issue150

Default checklist

[ ] Are there any manual checks you performed that could be automated and become part of the CI?
[ ] Are any issues relevant to the PR mentioned so that they will be automatically closed when the PR merges?

reopened so i can remove it from the closed PRs

.


Renew certificates when one is known to be OCSP revoked.

refs #328 where @frasertweedale proposed this
when checking on renewal of an MDomain, inspect known OCSP status for REVOKED answers. If found, renew MD.

I will apply the patch and test locally, and report back.

@icing
I have tested the change.  I see one issue: the actual renewal of a revoked cert doesn't take place until the next md watchdog run, which could be up to 12 hours.  If practical, the renewal should be attempted immediately.  Ideas:

wake the md watchdog, somehow?
unify the md watchdog and md ocsp watchdog, so that the ocsp handling can schedule the watchdog to run straight away again.
some other approach?

Overall, this PR works and is a big step forward.  It could be landed as-is.  In fact, there is already a delay until the OCSP response gets refreshed.  A further delay to actually trigger the renewal of a revoked cert is not ideal, but not a show-stopper.

@frasertweedale thanks for testing! I agree that waiting up to 12 hours for a renewal is not optimal.
The simplest way to shorten that is to make the 12 hours configurable.
Awakening the ACME watchdog on OCSP updates is more complicated. There is no guarantee that the ACME and OCSP watchdogs run in the same process. Execution might switch. As to making ACME and OCSP run in the same watchdog: that is of course possible but I am not sure I like to rip apart the code here.
I am leaning towards allowing admins concerned about revoke renewals to use a shorter interval.

@icing yeah, both of my suggested approaches would be intrusive and awkward changes.  Making the maximum watchdog sleep time configurable is a simple(r) change with a good impact.

Added MDCheckInterval config directive to this PR, plus documentation.


Error when running distributed MNIST example

Hi I am new to tensorflow and distributed tensorflow. I was trying to run an example from #2726
Right now I am using tensorflow 0.9 on a cluster of Raspberry Pi3, using slurm to manage the nodes in the cluster, the script is below:
#!/bin/bash
#SBATCH -N 4
#SBATCH --nodelist=piw[25-28]
node1=piw25
node2=piw26
node3=piw27
node4=piw28
#On node1:
srun -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=ps --task_index=0 &
#On node2:
srun -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=0 &
#On node3:
srun -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=1 &
#On node4:
srun -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=2
wait
And this is the error message:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, piw27:2223, localhost:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {localhost:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, piw27:2223, piw28:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc:202] Started server with target: grpc://localhost:2223
I tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc:202] Started server with target: grpc://localhost:2223
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {localhost:2223, piw27:2223, piw28:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc:202] Started server with target: grpc://localhost:2223
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, localhost:2223, piw28:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc:202] Started server with target: grpc://localhost:2223
Extracting data/train-images-idx3-ubyte.gz
Extracting data/train-labels-idx1-ubyte.gz
Extracting data/t10k-images-idx3-ubyte.gz
Extracting data/t10k-labels-idx1-ubyte.gz
Initialized!
Traceback (most recent call last):
File "mnist_yetanother.py", line 351, in
tf.app.run()
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 30, in run
sys.exit(main(sys.argv))
File "mnist_yetanother.py", line 310, in main
with sv.prepare_or_wait_for_session(server.target, config=None) as sess:
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/supervisor.py", line 684, in prepare_or_wait_for_session
init_feed_dict=self._init_feed_dict, init_fn=self._init_fn)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/session_manager.py", line 176, in prepare_session
sess.run(init_op, feed_dict=init_feed_dict)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 372, in run
run_metadata_ptr)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 636, in _run
feed_dict_string, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 708, in _do_run
target_list, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 728, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors.InvalidArgumentError: /job:worker/replica:0/task:0/cpu:0 unknown device.
[[Node: truncated_normal_2_S5 = _Recvclient_terminated=false, recv_device="/job:ps/replica:0/task:0/cpu:0", send_device="/job:worker/replica:0/task:0/cpu:0", send_device_incarnation=-8305312558883263444, tensor_name="edge_62_truncated_normal_2", tensor_type=DT_FLOAT, _device="/job:ps/replica:0/task:0/cpu:0"]]
srun: error: piw28: task 0: Exited with exit code 1
E0726 15:08:58.966743325   10814 tcp_client_posix.c:173]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': socket error: connection refused
E tensorflow/core/distributed_runtime/master.cc:202] Master init: Unavailable:
E0726 15:09:04.384147901   10819 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:09:09.463843371   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:09:18.410973793   10820 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:09:29.903416857   10814 tcp_client_posix.c:173]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': socket error: connection refused
E tensorflow/core/distributed_runtime/master.cc:202] Master init: Unavailable:
E0726 15:10:00.977546704   10814 tcp_client_posix.c:173]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': socket error: connection refused
E0726 15:10:47.956032631   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:11:48.090654174   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:13:21.260355773   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:15:21.261626939   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:17:21.263101653   10819 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:19:21.264292261   10814 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:21:21.265185108   10820 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
E0726 15:23:21.265939820   10801 tcp_client_posix.c:191]     failed to connect to 'ipv4:<IP_ADDRESS>:2223': timeout occurred
I killed the program after a while. I'm not sure why I would get "[Node: truncated_normal_2_S5 = _Recvclient_terminated=false, recv_device="/job:ps/replica:0/task:0/cpu:0", send_device="/job:worker/replica:0/task:0/cpu:0", send_device_incarnation=-8305312558883263444, tensor_name="edge_62_truncated_normal_2", tensor_type=DT_FLOAT, _device="/job:ps/replica:0/task:0/cpu:0"]" such error message. Searching online does not help too much...
Any help or advice will be greatly appreciated!

I think the relevant part of the message is 'Error: /job:worker/replica:0/task:0/cpu:0 unknown device.' Could you include mnist_yetanother.py as well to make sure you are setting up the cluster spec correctly?

Hi @michaelisard thank you for your reply, I used exactly the same code as in #2726, so the setup of cluster spec remains the same. Although I did try to hard code the assignment of the node into the code, still the same error.

Looking at your log output (and slightly unjumbling it), it appears that the ClusterSpec is appropriately configured:
# Presumably worker 2:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, piw27:2223, localhost:2223}
# Presumably the PS:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {localhost:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, piw27:2223, piw28:2223}
# [...]
# Presumably worker 0:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {localhost:2223, piw27:2223, piw28:2223}
# Presumably worker 1:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {piw25:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {piw26:2223, localhost:2223, piw28:2223}

However, the error you are seeing appears to be a result of misconfiguration: one worker is making a request to the process that it believes is worker 0, but the receiving process does not have the appropriate device (and so presumbly is actually a different worker).
How is your DNS configured for the cluster? Is it possible that one of the hosts has a different mapping for piw26 than the others (or than the cluster manager)?

Hi @mrry the cluster is set up to use /etc/hosts for hostname resolution within the cluster. We switched to use the IP addresses of the nodes and we ran into the same error. I'm skeptical if the error message is caused by

tensorflow.python.framework.errors.InvalidArgumentError: /job:worker/replica:0/task:0/cpu:0 unknown device.
[[Node: truncated_normal_2_S5 = _Recvclient_terminated=false, recv_device="/job:ps/replica:0/task:0/cpu:0", send_device="/job:worker/replica:0/task:0/cpu:0", send_device_incarnation=-8305312558883263444, tensor_name="edge_62_truncated_normal_2", tensor_type=DT_FLOAT, _device="/job:ps/replica:0/task:0/cpu:0"]]

Something related to truncated_normal as the input argument?
Thank you for your reply!

Do you have the ability to recompile from source? I can think of a small patch that would make it easier to diagnose the problem.
(I don't think it's related to the particular use of truncated_normal, and it still seems like an address misconfiguration to me, although using IP addresses rules out DNS misconfiguration.)

@mrry inspired us to check if the tasks are running on the designated nodes. We now changed the way of assigning the nodes, and now it's working! thanks a lot!!!
The script is shown below:
#!/bin/bash
#SBATCH -N 4
#SBATCH --nodelist=piw[25-28]
node1=piw25
node2=piw26
node3=piw27
node4=piw28
On node1:
srun --nodelist=piw25 -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=ps --task_index=0 &
On node2:
srun --nodelist=piw26 -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=0 &
On node3:
srun --nodelist=piw27 -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=1 &
On node4:
srun --nodelist=piw28 -N 1 -n 1 python mnist_yetanother.py
--ps_hosts=$node1:2223
--worker_hosts=$node2:2223,$node3:2223,$node4:2223
--job_name=worker --task_index=2
wait

Glad to hear it! So - just for my understanding - was the problem that Slurm was assigning some tasks to the same nodes? (or assigning them in a non-deterministic order?)

I don't think this is caused by slurm assigning tasks to the same nodes. As long as the tasks are specified to each node specifically they can run correctly. I have run into the situation where some tasks assigned to the same node, I will try to post that error message later, different from what I post here.

When I accidentally tried to assign several tasks to the same node, I got the following error message:
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job ps -> {<IP_ADDRESS>:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_channel.cc:206] Initialize HostPortsGrpcChannelCache for job worker -> {<IP_ADDRESS>:2223, <IP_ADDRESS>:2223, localhost:2223}
I tensorflow/core/distributed_runtime/rpc/grpc_server_lib.cc:202] Started server with target: grpc://localhost:2223
E0727 11:38:35.762428930   22857 tcp_server_posix.c:284]     bind addr=[::]:2223: Address already in use
srun: error: piw25: task 0: Segmentation fault
E0727 11:38:35.762761220   22857 server_chttp2.c:119]        No address added out of total 1 resolved
E0727 11:38:37.724595086   21952 tcp_server_posix.c:284]     bind addr=[::]:2223: Address already in use
srun: error: piw27: task 0: Segmentation fault
E0727 11:38:37.725087528   21952 server_chttp2.c:119]        No address added out of total 1 resolved
E0727 11:38:37.822318646   23426 tcp_server_posix.c:284]     bind addr=[::]:2223: Address already in use
E0727 11:38:37.822415468   23426 server_chttp2.c:119]        No address added out of total 1 resolved
srun: error: piw26: task 0: Segmentation fault
slurmstepd: error: *** STEP 626.1 CANCELLED AT 2016-07-27T11:40:22 *** on piw28
srun: got SIGCONT
slurmstepd: error: *** JOB 626 CANCELLED AT 2016-07-27T11:40:22 *** on piw25
srun: Job step aborted: Waiting up to 2 seconds for job step to finish.
So it told me the address that I tried to access is already in use.

so I have the same problem, but with different port, anyone has solve it?


Need to record video in the background

Hi, I'm building an app in which images are shown and the camera records the facial expressions the person does as a reaction to those pictures. Since the stimuli (the pictures) should occupy the full screen of the device, there is no place for any controls (i.e. record button and the like). So video recording shall start, then images are shown, then video stops recording.
I managed to do that in a UWP project with UWP apis and I am trying now to do it in Xamarin Forms to make it work on Android and iOS.
Is there a way to do that with your plugin out of the box?
Otherwise, do you think it is worth modifying this plugin, or what I am trying to do is so different I would do better starting all over again coding my own plugin?
Thank you so much,
Federico

Not possible with this plugin

Thank you!
Any other plugin you'll recommend for this? Otherwise any other clue for me to pursue?


Verbose output as Json

for server side Job would be nice to have the verbose output as JSON

Verbose output is intentionally non-structured, and it can change without notice. What information from verbose output are you interested in?

interested in the input/output stats
input: 8 mesh primitives (122320 triangles, 228842 vertices); 8 draw calls (8 instances, 122320 triangles)
output: 4 mesh primitives (122150 triangles, 228752 vertices); 4 draw calls (4 instances, 122150 triangles)

glTF-Validator (https://github.com/KhronosGroup/glTF-Validator) can produce the following report as a JSON:
{
    "uri": "nyra.glb",
    "mimeType": "model/gltf-binary",
    "validatorVersion": "2.0.0-dev.3.0",
    "issues": {
        "numErrors": 0,
        "numWarnings": 0,
        "numInfos": 0,
        "numHints": 0,
        "messages": [],
        "truncated": false
    },
    "info": {
        "version": "2.0",
        "generator": "gltfpack 0.14",
        "extensionsUsed": [
            "KHR_mesh_quantization"
        ],
        "extensionsRequired": [
            "KHR_mesh_quantization"
        ],
        "animationCount": 0,
        "materialCount": 1,
        "hasMorphTargets": false,
        "hasSkins": false,
        "hasTextures": false,
        "hasDefaultScene": true,
        "drawCallCount": 1,
        "totalVertexCount": 15019,
        "totalTriangleCount": 27892,
        "maxUVs": 0,
        "maxInfluences": 0,
        "maxAttributes": 2
    }
}

So one option is to run the validator after gltfpack if this information is required... I could also add a command-line argument to output a JSON report with some of this information.

(I am assuming just the output information is of interest here)

would nice to have this as commandline argument ( validator  would need node as runtime )

Ok - this isn't too difficult. What's the full set of data that you need for server-side processing?

this is good! maybe a commandline flag -stats  if its not to difficult than all  stats gltfpack provide


Add services conformance tests to ciliume2e

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests

Notes:

bypassing and merging - relevant tests passed, ACN PR failed due to ongoing AZP issue


Add total seconds played key

As seen here there is now a total_seconds_played in the returned JSON

To think you literally made a commit an hour ago for exactly this xD


Logout trigger for NPCs

@Logout trigger When NPCs (mounts) are logged out of the session in any way, i.e. mounted or minimised, they will log out (disconnect) but will not trigger.

Since it's a particular situation on a particular NPC, should we really use the @logout trigger?
I mean, we disconnect the mount when we climb on it to avoid it take damage and maybe more reason. If the purpose is really explicitly for this situation, could we use something like @Dismounted and place it directly on the dismount method? Juste after the @dismont for player.

Belirli bir NPC'deki belirli bir durum söz konusu olduğundan, @logout tetikleyicisini gerçekten kullanmalı mıyız?
Yani, üzerine tırmandığımızda hasar görmesini önlemek için montajı ayırıyoruz ve belki de daha fazla sebep. Eğer amaç gerçekten bu durum için açıkça belirtilmişse, şöyle bir şey kullanabilir miyiz?@Dismountedve onu doğrudan dismount yöntemine yerleştirin? Juste'den hemen sonra@Dismontoyuncu için.

In fact, a mount can be logged out not only when it is mounted but also when we directly .xdisconnect it to the mount. Previously, this trigger was not triggered when a mount was disconnected with .xdisconnect.

Since it's a particular situation on a particular NPC, should we really use the @logout trigger?
I mean, we disconnect the mount when we climb on it to avoid it take damage and maybe more reason. If the purpose is really explicitly for this situation, could we use something like @Dismounted and place it directly on the dismount method? Juste after the @Dismont for player.

In fact, a mount can be logged out not only when it is mounted but also when we directly .xdisconnect it to the mount. Previously, this trigger was not triggered when a mount was disconnected with .xdisconnect.
It also disconnects when the mount is shrink.

That's interesting. Do you have any use cases in mind?


[Map] DM-GMCMuseumB

Hash: 1552c4a981095292d9a19899592a958d959004c1
Current name: DM-GMCMuseumB
In the readme for an identical version of this map, the author's name is   {CBGB}Asha'man, Chris Barnett
Whether this means Chris Barnett was also  {CBGB}Asha'man  or that a Chris Barnett original was modified by  {CBGB}Asha'man is unclear - possibly the former I would think as the map is copyright to Chris Barnett.
Player Count = 6-8

Updated author and player count.


improve openssl speed

Hi,
I've found a way to make openssl key generation faster.
According to this post on Stackexchange
linux - Diffie Hellman parameters still calculating after 24 hours - Information Security Stack Exchange
it makes no difference regarding security.

If you want faster DH key generation, please use 2048 bits keys.


Add support for customer-supplied encryption keys

This fixes #1037

Coverage decreased (-0.1%) to 85.347% when pulling 0a2e63f871e9d1ec8b065a8bf51cb429d57e3942 on mziccard:storage-encryption-key into c929ee1fc4f6ee001e96a60f01a48a72523b4882 on GoogleCloudPlatform:master.

/cc @lesv
(I'll add some more tests to avoid this coverage drop)

LGTM - Thanks for this!  Ping and I'll read the additional tests.

Coverage decreased (-0.08%) to 84.985% when pulling b0b6aa09415bb927554c9a7ea6c42b3d22ea39ef on mziccard:storage-encryption-key into 4d5a86c8fd6b91b45d043c5eef0efff51f604b62 on GoogleCloudPlatform:master.

@lesv I rebased on top of master and added more coverage.

LOL - coveralls says it decreased.

LGTM


Why doesn't try-catch help catch the exception when the app is run from within a JAR?

 Below is the fat JAR task config in my build.gradle file.
task shadowJarBotService (type: ShadowJar) {
    zip64 true
    archiveFileName = 'my-bot-service.jar'
    manifest.attributes["Main-Class"] = "myBot.Service"
    project.configurations.shadow.setTransitive(true);
    configurations = [project.configurations.shadow]
    from sourceSets.test.output
    from sourceSets.test.resources
    from sourceSets.main.output
    from sourceSets.main.resources

}

The code to return a relevant message to the return context.client().chatPostMessage(...) call is a simple try-catch block that works well if I do not run my service through a JAR, but through a Gradle run task configuration.
Reproducible in:
implementation("com.slack.api:bolt-socket-mode:1.36.1")
implementation("javax.websocket:javax.websocket-api:1.1")
implementation("org.glassfish.tyrus.bundles:tyrus-standalone-client:1.19")
implementation("org.slf4j:slf4j-simple:1.7.36")

The Slack SDK version
|    +--- com.slack.api:slack-api-client:1.1.0 -> 1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1
+--- com.slack.api:bolt-socket-mode:1.36.1
|    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    +--- com.slack.api:slack-app-backend:1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    |    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    \--- com.slack.api:bolt:1.36.1
|         +--- com.slack.api:slack-api-model:1.36.1 (*)
|         +--- com.slack.api:slack-api-client:1.36.1 (*)
|         +--- com.slack.api:slack-app-backend:1.36.1 (*)
+--- com.slack.api:bolt-socket-mode:1.36.1 (n)
|    +--- com.slack.api:slack-api-client:1.1.0 -> 1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1
+--- com.slack.api:bolt-socket-mode:1.36.1
|    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    +--- com.slack.api:slack-app-backend:1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    |    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    \--- com.slack.api:bolt:1.36.1
|         +--- com.slack.api:slack-api-model:1.36.1 (*)
|         +--- com.slack.api:slack-api-client:1.36.1 (*)
|         +--- com.slack.api:slack-app-backend:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.1.0 -> 1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1
+--- com.slack.api:bolt-socket-mode:1.36.1
|    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    +--- com.slack.api:slack-app-backend:1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    |    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    \--- com.slack.api:bolt:1.36.1
|         +--- com.slack.api:slack-api-model:1.36.1 (*)
|         +--- com.slack.api:slack-api-client:1.36.1 (*)
|         +--- com.slack.api:slack-app-backend:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.1.0 -> 1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1
+--- com.slack.api:bolt-socket-mode:1.36.1
|    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    +--- com.slack.api:slack-app-backend:1.36.1
|    |    +--- com.slack.api:slack-api-model:1.36.1 (*)
|    |    +--- com.slack.api:slack-api-client:1.36.1 (*)
|    \--- com.slack.api:bolt:1.36.1
|         +--- com.slack.api:slack-api-model:1.36.1 (*)
|         +--- com.slack.api:slack-api-client:1.36.1 (*)
|         +--- com.slack.api:slack-app-backend:1.36.1 (*)

Java Runtime version
openjdk version "11.0.17" 2022-10-18 LTS

OS info
ProductName: macOS
ProductVersion: 14.1.1
BuildVersion: 23B81
Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000

For this issue, I tried some Google search and came across this answer https://stackoverflow.com/a/26288190. So I thought of opening this question here in this forum.

Hi @akshayamaldhure, thanks for asking the question.
I've never heard of this type of issues. With the given information so far, I don't think this SDK can be the cause of the issue. So, we may not be able to help you out for this question. If you observe a behavior difference (or misbehavior if you call it so) only when running your code as part of a uber jar file, please consider asking for a help to the project maintainers with a minimum repro steps.
Hope you'll figure the cause out soon!

@seratch I believe you right, because what I get during the debug process is not an exception but an error, which is not supposed to caught using the try-catch block with an Exception e declaration. Sorry about confusion. I'll get to the bottom of this. Thank you for the quick response.


Please update your instructions

https://learn.microsoft.com/en-us/office/dev/add-ins/quickstarts/excel-custom-functions-quickstart?tabs=excel-windows
Here is telling yo office And the second step doesn't work:
Choose a project type: Excel Custom Functions Add-in project . In my computer it provides no option Excel Custom Functions Add-in project. Trying alternatively Choose a project type="Office Add-in Task Pane project", script type="javascript", name="My custom functions add-in", officeClientApp="Excel". Installing.. .
cd "My office add-in", npm run build.
And npm run start:web -- --document https://<myTenantUser>.sharepoint.com/:x:/s/<mysite>/<myExcelUrl>?e=8...g
After it i upload my own test addins and try excel function =CONTOSO.GETSTARCOUNT("OfficeDev", "Excel-Custom-Functions") on b1-cell. It doesn't work.
Commonly please check all of tutorials, because big part of them are obsolete and almost impossible to learn from them.

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

ID: 4bac6469-78a6-dae9-e6c4-497c953a1576
Version Independent ID: d860aff2-60ad-c008-2d10-b046f3198f44
Content: Custom functions quick start - Office Add-ins
Content Source: docs/quickstarts/excel-custom-functions-quickstart.md
Product: excel
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Thanks for reporting this @ivose. I'm sorry to hear you're having issues with the quickstart.
@alison-mk, could you please investigate?

Hi @ivose, thank you for submitting an issue. We recently updated and renamed the custom functions projects in Yo Office. If you are using Excel on Windows, choose the project type Excel Custom Functions using a Shared Runtime and then follow the existing directions. Here is a screenshot:

I will update the custom functions quick start and tutorial with the new guidance in PR #3656. This issue will close automatically when that PR is merged.
If you are using Excel on Mac, the Yo Office custom functions projects may not work at this time. I have encountered some bugs with the Mac project that I need to investigate further internally.
Alison


CLIProvider does not supply a command for PowerShell scripts

It seems CliProviderImpl is unable to detect whether we are running on PowerShell and only supply the .sh and bat variants.
See:
https://github.com/wildfly-extras/prospero/blob/7256b85a074f963df6a1c9593ec6258616aabb3b/prospero-cli/src/main/java/org/wildfly/prospero/cli/spi/CliProviderImpl.java#L35C1-L38

Fixed by https://github.com/wildfly-extras/prospero/pull/389


micro_ros_diagnostics: 0.2.0-4 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository micro_ros_diagnostics to 0.2.0-4:

upstream repository: https://github.com/micro-ROS/micro_ros_diagnostics.git
release repository: https://github.com/ros2-gbp/micro_ros_diagnostics-release.git
distro file: foxy/distribution.yaml
bloom version: 0.10.7
previous version for package: 0.2.0-3

Holding for Foxy sync


Move the sql run query inside the library

additional branch created for it but will not add as I don't want third party dependencies in my library


Native Notebooks - Share restart + interrupt kernel

Today the Jupyter extension supports restart and interrupt kernel. This functionality is not yet available to other extensions that build on top of us. (Julia, .NET)
Tracking the discussion and work items related to enable both of these for partners.

Restart is a duplicate of https://github.com/microsoft/vscode/issues/118783


Open watched object in the Scene Explorer when you click on it

That would make the watchlist very useful. Of course it can only be opened when it is not a simple type like int or byte.

Does this already work?


grpc for exec

not consider GetExitCode temporarily
Signed-off-by: Yao Zengzeng<EMAIL_ADDRESS>

Same with attach. It's better to pass the attach error message (except of io.EOF) out of goroutines and return the error.

This patch is really a good job! Except that exit is broken. Will merge this once fixed.
$ kubectl exec -it busybox -- /bin/sh
# ls
bin   dev  home  lib64	mnt  proc  run	 srv  tmp  var
boot  etc  lib	 media	opt  root  sbin  sys  usr
# exit
error: error executing remote command: error executing command in container: rpc error: code = 1 desc = "context canceled"

      After the execution of "exit", the output will end and stream will be cloesd, but input is still blocked for reading from stdin.When it get some input and put it into closed stream,the bug showed above will come up.
     Indeed, when we get error  either from input or output,we could return.Otherwise we would get  error unneeded.

lgtm


Slide Alert from top.

Currently, the alert messages slide in from the side. Since the default location of a messages is the top center, I would prefer the default animation to be: slide in from top. Since this is done using CSS, this can't easily be changed.
Could you take a look at this, @paviro?

Yes but probably not before Friday. Having my finals the next two days.

Am 05.04.2016 um 10:07 schrieb Michael Teeuw<EMAIL_ADDRESS>Currently, the alert messages slide in from the side. Since the default location of a messages is the top center, I would prefer the default animation to be: slide in from top. Since this is done using CSS, this can't easily be changed.
Could you take a look at this, @paviro?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

No worries! Good luck with your finals! :)

Thanks! :)

Am 05.04.2016 um 11:45 schrieb Michael Teeuw<EMAIL_ADDRESS>No worries! Good luck with your finals! :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


[fix][broker] Fix RoaringBitmap.contains can't check value 65535

Motivation
https://github.com/RoaringBitmap/RoaringBitmap/issues/623
ConcurrentBitmapSortedLongPairSet and Bucket use this method.
Modifications

Upgrade RoaringBitmap version to 0.9.44, this issue be fixed by PR (https://github.com/RoaringBitmap/RoaringBitmap/pull/624)
Add test for RoaringBitmap.contains

Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Interesting, ConcurrentBitmapSortedLongPairSet also used the same method.

RoaringBitmap/RoaringBitmap#623

Yeah, I'm not sure if our usage is wrong

Codecov Report

Merging #20176 (e28b882) into master (35e9897) will increase coverage by 35.24%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #20176       +/-   ##
=============================================
+ Coverage     37.64%   72.89%   +35.24%
- Complexity    12522    31963    +19441
=============================================
  Files          1691     1868      +177
  Lines        128933   138594     +9661
  Branches      14061    15246     +1185
=============================================
+ Hits          48540   101026    +52486
+ Misses        74070    29531    -44539
- Partials       6323     8037     +1714

Flag
Coverage Δ

inttests
24.14% <ø> (-0.02%)
:arrow_down:

systests
24.77% <ø> (-0.10%)
:arrow_down:

unittests
72.20% <ø> (+39.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1431 files with indirect coverage changes

Merging...

@coderzc Please update the PR description with the impact of this bug.
Here's my version of describing the impact:
MessageRedeliveryController uses the RoaringBitmap under the covers to track entryIds to redeliver.
The bug in RoaringBitmap (that has now been fixed) caused at least the case that the bit index 65535 couldn't be set.
The consequence of this would be that a message that should be redelivered doesn't get delivered and this could get Key_Shared subscriptions to get stuck. This could impact also other subscription types and cause a backlog to build up.
This bug was introduced in 2.10.2 with #17804 since that's when MessageRedeliveryController switched to use the RoaringBitmap based datastructure.
@codelipenghui @coderzc Is this the correct interpretation?

@lhotari Yes, looks good to me. Thanks.

As discussed on the mailing list https://lists.apache.org/thread/w4jzk27qhtosgsz7l9bmhf1t7o9mxjhp, there is no plan to release 2.9.6, so I am going to remove the release/2.9.6 label


1.3: Support ph element within index terms

Proposal 13092

Since keyword and other elements were already allowed in DITA 1.2, are any changes actually needed to support ph? cc @robander

I think "support" will be transform specific, given that index support varies by format. Pretty sure the main incentive for this was to have styling, such as <b> or <sup>, carry through to the index (without affecting sort order). Main test target then would be PDF.

As @keberlein pointed out in Slack - main styling concerns leading to this change are <sub> and <sup>

Need to check if current processing retains keyword formatting. If it's retained currently, then e.g. sub should already go through correctly; if current processing ignores keyword, then this is a completely new functional feature.

Tested develop code and e.g. <sup> and <sub> work in index output. Closing as implemented.


Ability to omit files containing sensitive data in assessmentUnit archive(s)

Is your feature request related to a problem? Please describe.
Some of the files collected by the collector may contain sensitive data e.g. passwords.  These should not be uploaded to TA without being redacted.
Describe the solution you'd like
Plugin should declare the config files being collected, and whether or not those files have been redacted in the assessmentUnit.metadata.json file
The default behaviour should be that final zip archive does not include the collected files unless plugin declares that they do not contain sensitive data.  The reason for having those files in the plugin is (1) for debugging purposes if the recommendations.json does not produce expected results (2) potential future capability to evaluation new rules without having to collect new data.  A "--includeSensitiveFiles" command line option to override this behaviour for the run command.
Describe alternatives you've considered
We already have redaction capability in the SDK but sometimes it's not easy to guarantee that you know all the places that need to be redacted.
Additional context
Add any other context or screenshots about the feature request here.

Following on from further discussions with Aaron, this is the plan to tackle this:

Add an method to the interface that must be implemented for env.json

This method will be containsSensitiveData
It should default to true (people have to explicitly override it)

When this value is set to true then the .zip file will not be generated
When a zip file is not generated it should print out a message explaining why, aka: sensitive data has been included so an uploadable archive has not been generated.

@paulbarr @johnbuckley @transformationAdvisor-sdk
I've created a pull request for master. Please review. I will still need to pull this into v0.5.5 branch and do some sanity testing there as well.
I've also created labels for the releases (v0.5.5 and v0.6.0) and started to add labels to the issues. I can't remember anymore which fixes are in which release and is spending a bit too much time going through pull requests.

@jianfeng, for 0.6.0, can you think of a simple pattern for the inclusion of the migration files? If there's a simple pattern, I could implement it. If not, maybe you'll need to take over to finish this part. Thanks.

@jianfeng The 0.5.5 branch is ready to go. You may want to do some sanity tests before creating the release and pushing it to maven. The earlier we get it to Aaron's hands and let him do some tests the better.

fix was delivered in both 0.5.5 and 0.6.0 release.


allow for running w/ multiple gpus and provide an example

          And i need use mult gpus, I don't see something like pmap in code. Need a example that how to train use mult gpus.

Originally posted by @Nightbringers in https://github.com/lowrollr/turbozero/issues/8#issuecomment-1925039705

added with #12


CTE Query Optimization

Hello,
I use your package for profiling and I find it great ! Thank's for your contribution.
I use Snwoflake for the compute part and I noticed (tested) a potential optimization
What is currently being done
A "column_profiles" CTE that performs a union all for each column and reads from the source table (DB.SCHEMA.TABLE) .
When analyzing the snowflake profile query, it performs as many table scans as there are columns. for large volumes, the small warehouse is not enough and returns a memory error.
We can optimize a little by adding a first cte to read the source table in full and then reference this cte for each column, that will force snowflake to read the table only once, mount it in memory and then use it.
I have metrics, we divide by 3/4 the amount of I/O , There is also the number of partitions, In my case
Before

After

PS : The notion of cache in the original runtime doesn't matter since I disabled the session cache
ALTER SESSION SET USE_CACHED_RESULT = FALSE;
I also restarted the warehouses between each execution (using several warehouses on different time intervals). I can't explain myself but I think it's a common cache due to union all.
On the execution times, there is not a big difference but I have tests on large tables where the first query does not succeed because of the number of columns (1000) and the size of the table
I remain at your disposal in case of more information
Snippet code

@belaidcherfa Wow, this is awesome! Thanks for all the work you've put into researching this ❤ I have totally overlooked the performance part and I really appreciate your help.
Implementing this is straightforward. Do you want to have a crack at it and create a PR? I can also do it, no problem.

I'm excited to see what other Snowflake optimizations you come up with! 💯


Crash with error message

Hey!
I get an error message when the program crashing, i need to restart it manually. Crashing everyday, min. 1-2 times when use.
goroutine 50 [running]:
github.com/teacat/chaturbate-dvr/chaturbate.(*Manager).CreateChannel.func1()
        /mnt/c/Users/yamiodymel/go/src/github.com/teacat/chaturbate-dvr/chaturbate/manager.go:121 +0xe5
created by github.com/teacat/chaturbate-dvr/chaturbate.(*Manager).CreateChannel in goroutine 1
        /mnt/c/Users/yamiodymel/go/src/github.com/teacat/chaturbate-dvr/chaturbate/manager.go:117 +0x2d5

Need any more info about usage?

Is it randomly crashing? There should be an error message explaining why it crashed (few lines before the lines you pasted). Can you paste it?
Try copying chaturbate-dvr.exe to a new/empty folder and opening it. It might be caused by an odd channel making it crash.

I dont see anything else in cmd window.
Randomly, i dont do anything when crash. I have been using it for a week and added 18 channels.
Channel example:
{
        "Username": "VALIDCHANNELNAME",
        "FilenamePattern": "d:/videos/chaturbate/{{.Username}}/{{.Username}}_{{.Year}}_{{.Month}}_{{.Day}}-{{.Hour}}_{{.Minute}}_{{.Second}}",
        "Framerate": 30,
        "Resolution": 2160,
        "ResolutionFallback": "down",
        "SplitDuration": 0,
        "SplitFilesize": 0,
        "Interval": 1
    }


Division by zero

Division by zero triggers a crash, uxn returns zero on division by zero.

Good catch! Fixed in 0.1.1.

Thanks for the patch to the opcode test :)
On 10/28/23, Remko Tronçon @.***> wrote:

Good catch! Fixed in 0.1.1.
--
Reply to this email directly or view it on GitHub:
https://github.com/remko/uxn.wasm/issues/1#issuecomment-1783728288
You are receiving this because you authored the thread.
Message ID: @.***>


Nixpkgs nomination proposal

Lack of feedback/help from the rest of the team. Meanwhile I added the most important things to the github issue.


Staging

Description

Checklist:

[ ] Automated checks are passing locally.
[ ] CHANGELOG updated if change is worth telling users about.

General testing

[ ] Test without javascript
[ ] Test on small screen

Accessibility testing

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable css - does content make sense and appear in a logical order?
[ ] Passes automated checker (automated in build or manual)

Pull Request Test Coverage Report for Build 6341

0 of 0   changed or added relevant lines in 0 files are covered.
327 unchanged lines in 14 files lost coverage.
Overall coverage decreased (-4.0%) to 90.303%

Files with Coverage Reduction
New Missed Lines
%

psd-web/app/models/team.rb
1
74.51%

shared-web/app/helpers/shared/web/login_helper.rb
1
92.31%

shared-web/app/helpers/shared/web/user_management_helper.rb
1
80.0%

psd-web/test/controllers/investigations_controller_test.rb
2
98.79%

shared-web/app/clients/shared/web/keycloak_client.rb
2
83.59%

psd-web/app/helpers/documents_helper.rb
5
28.95%

psd-web/app/helpers/products_helper.rb
7
75.0%

psd-web/test/controllers/investigations/corrective_actions_controller_test.rb
10
47.37%

psd-web/app/controllers/concerns/corrective_actions_concern.rb
11
56.0%

psd-web/test/controllers/investigations/products_controller_test.rb
17
41.38%

Totals

Change from base Build 6344:
-4.0%

Covered Lines:
5476

Relevant Lines:
6064

💛  - Coveralls


Use jcenter(), not mavenCentral() for Gradle build

jcenter() is faster than mavenCentral() and will use https://
(I'm not sure what the corresponding change to pom.xml would be.)

@dexX7
p.s. I did a checkout, build and test on Mac OS X Yosemite. The tests all passed!
One little nit is that the Gradle build didn't seem to notice if I move or change (touch) the libbitcoinconsensus.dylib file. I also discovered that it works if the dylib is in project root or in src/main/resources

One little nit is that the Gradle build didn't seem to notice if I move or change (touch) the libbitcoinconsensus.dylib file. I also discovered that it works if the dylib is in project root or in src/main/resources

That's interesting. I tested it on Ubuntu and this doesn't work for me. Could it be that libbitcoinconsensus is available as system library on your system? When using make install on Ubuntu, then the library is installed and available globally, so this would be my guess. Or OS X is a bit smarter here..
I was also wondering how we should handle this in general. I'm currently hosting the lib for Travis, but I don't really like it. As alternative I tested to download the offical Bitcoin release from bitcoin.org, but this comes at the cost of more traffic. It can be cached though.
Ideally the lib would be shipped with this project, but that adds a lot of more risk/responsibility in my opinon. What do you think?

I'm not sure what the corresponding change to pom.xml would be.

See #3. Depending on where the whole project is going, I'm wondering whether we should maintain the synchronization, or drop mvn instead.

Could it be that libbitcoinconsensus is available as system library on your system?

I'm pretty sure that's not the case (I did a global search just in case) I also moved it from projectRoot to a different directory and the test failed.

Or OS X is a bit smarter here..

I suspect it is a platform difference.

Ideally the lib would be shipped with this project, but that adds a lot of more risk/responsibility in my opinion. What do you think?

It would be nice if the libs for the major platforms were inside the jar. I think we can delay the decision about how to do that until later, though. We may also want to talk to the Bitcoin Core developers to find out what they recommend.

I'm wondering whether we should maintain the synchronization, or drop mvn instead.

We should drop one or the other, it seems like extra work to maintain both. My vote is to drop mvn and stick with Gradle, of course. Did you pick up both build files from a JNA sample?

It would be nice if the libs for the major platforms were inside the jar. I think we can delay the decision about how to do that until later, though.

Yup, I agree. Sounds good to me!

Did you pick up both build files from a JNA sample?

Sort of. I looked at an example for JNA and then searched for the dependency. I created the project via mvn archetype:generate and Gradle init, with some manual adjustments.


Define a new variable header type for environment information

The IGVM_VHT_ENVIRONMENT_INFO_PARAMETER defines a bitfield that permits the hosting environment to describe certain behaviors so the VM can conform.  The only currently defined behavior indicates whether the default state of memory is assigned (private) or unassigned (shared) so the VM knows whether it must request page state changes before using any memory.  Other behaviors will be defined in the future.

works around #19 with not intra-link doc comments and no unstable gate on the enum type.


Not able to create balancer service with no portRules/by passing empty portRule list.

Rancher Version: latest cattle build from lbrefactormetadata from https://github.com/alena1108/cattle.git
Try to create a balancer service with no portRules/by passing empty portRule list.
API errors out with following error:
    def _error(self, text):
>       raise ApiError(self._unmarshall(text))
E       ApiError: (ApiError(...), "MissingRequired : None\n{'status': 422, 'code': u'MissingRequired', 'links': {}, 'detail': None, 'actions': {}, 'fieldName': u'portRules', 'message': None, 'type': u'error', 'id': u'5e4d3688-b576-47fa-8d0d-47fa0a91efaf'}")

Tested with build from master:
Able to create LB service with no targets by passing empty lbConfig parameter/ by having empty array for "portRules" in launchConfig.


⚠ Samsung has degraded performance

In 96ae19d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2411 ms

Resolved: Samsung performance has improved in 77beb29.


Add support to allow parameters to be database-agnostic

In reference to https://github.com/beekeeper-studio/beekeeper-studio/issues/1353
Adding support to enable detecting parameters without being tied to specific database type.
identify('select * from my_table where ? = :foo and $1 = $2', { enableCrossDBParameters: true })

Closing this in favor of work done in #78 as that allows for more customizability for end users.


Deploying Agora via Azure Developer CLI using WSL Ubuntu Distro

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
<!--- A link to the Jumpstart scenario you are working on. --->
Describe the issue or the bug
I'm running the Azd up command from a WSL Ubuntu environment: the command hangs and shows Logging to Azure
To Reproduce

Screenshots

At this step it should be installing the Az PowerShell module, which can take some time. Did it ever recover from this?

it did install the AZ Pwsh module and the continued on.
Luca

From: Dale Kirby @.>
Sent: Monday 11 September 2023 15:17
To: microsoft/azure_arc @.>
Cc: Author @.***>
Subject: Re: [microsoft/azure_arc] Deploying Agora via Azure Developer CLI using WSL Ubuntu Distro (Issue #2105)
At this step it should be installing the Az PowerShell module, which can take some time. Did it ever recover from this?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azure_arc/issues/2105#issuecomment-1713983669 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKDQXCA3QAW75MR4ZQJWOCLXZ4MQ7BFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TOOJYGQZTQMRUG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSGQYTEMRVGEZDFAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOBYHAYTQNRQGM4YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2TOOJYGQZTQMRUG6TXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Great, so it sounds like your issue is resolved. Can we close this?

@LucaOtto any updates?


Format on save is breaking .csproj file in VS Code projects

Perhaps I can modify a setting, but in the event anyone else has an issue, when opening and adding code directly to a .NET Core .csproj file, on save the formatting breaks and during dotnet restore the following error is thrown as it adds hard returns and spaces around portions of code.
C:\Program Files\dotnet\sdk\1.0.1\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\Microsoft.NET.Sdk.Publish.targets(90,5): error MSB4184: The expression "[System.IO.Path]::GetFullPath(C:\test\obj\Debug\ [C:\test\test.csproj]
C:\Program Files\dotnet\sdk\1.0.1\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\Microsoft.NET.Sdk.Publish.targets(90,5): error MSB4184: netcoreapp1.1 [C:\test\test.csproj]
C:\Program Files\dotnet\sdk\1.0.1\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\Microsoft.NET.Sdk.Publish.targets(90,5): error MSB4184: \PubTmp)" cannot be evaluated. Illegal characters in path. Parameter name: path [C:\test\test.csproj]

I also am facing the same issue.
Is there any solution for this?

I also am facing the same issue. Is there any solution for this?

Turn off code formatting. It looks like csproj files are whitespace sensitive. When you're formatting:
net6.0
gets replaced with:

net6.0

and this seems to be a problem here.

Having this problem still.


Actually use RUN_MODE in config.ini for what I think it is used for.

Pardon me if I'm wrong but apparently RUN_MODE in config is not even being parsed. Which results in the issue #3611. This PR hopefully fixes it.

Completely missed the typo. Anyone can try this patch out and see if #3611 is fixed?


stomach fibrosis

Please add:
stomach fibrosis
DEF: invasion of fibrous connective tissue into the stomach, often resulting from inflammation or injury
SYN: gastric fibrosis
J:139032
Thanks
Anna

stomach fibrosis   MP:0014159


Feature: electronic payments with Mollie or (S)(K)(U?)ARIO

Paying in cash is silly! We want to pay digitally!
However payment fees at iDeal/Mollie are relatively high, so maybe we should use a micropayment service like (S)KUARIO (which the university uses as well for printing). Or use a wallet-like system (or debit system like Thalia will use soon™)

We can just pull the payments app from concrexit in here and that's it

Please implement SKUARIO, so I can use group budgets to spent on tostis.
/cc @wkuijltjes


entrypoint: handle jq error

Rename the tmp conf file only when jq has worked, otherwise the config file is empty.

I had pushed an old commit with 'cp' instead of 'mv'. The branch is now uptodate.
I had a situation with a syntax error in the conf leading with a temporary file created but empty.
More precisely, there was a comment in which would still be accepted by the app but not jq.
Do we want to flag that and exit?  That's a possibility.

we should check for comments in the ".conf" files ahead of parsing them and either exit or strip them to the end of the line.

Right, I think the syntax should be validated (just a simple 'jq' read may be enough) but I would notify and exit rather than trying to handle any possible syntax error.


Purchase status modification

In the Admin Dashboard, the Purchases card, all of the purchases except for the rejected and delivered ones are listed. Below them is a row of buttons:

When one of them is pressed (e.g. ready for pickup), the following message is displayed:

And then, if you click on "edit status", you will not see the selected status, and instead, "pending" will take its place:

The icon used for the pending button is archive.

*insert "but.. why?" gif*
It is not intuitive that "pending" would mean "leave it in its current state, ready for pickup"

@aabounegm because it wouldn't mean that? It means get the purchase back into pending state. In case they mistakenly marked the purchase as ready

oh. so how to cancel editing then?

@aabounegm Well, pretty much refresh the page. Yeah, it sucks, I have an idea for something else, but don't care too much about it now

Implemented in #60


[realtime-cards] fix bug in mf version

Tests failing coz Metaflow is still not published 🤷 https://github.com/Netflix/metaflow/actions/runs/7493205983


LDAP Start TLS

Is there a hidden option to enable LDAP Start TLS?
If yes could you add it to the docs?

We are including new parameters to enable LDAP connection with TLS or SSL in the upcoming version 1.3.3.
The parameters are the following:


Audit shows '[ERROR ] Problem occurred trying to invalidate hash cach for azurefs'

I am not sure if this has been logged already so on a safer side logging a new ticket.
[root@ip-10-249-71-213 ~]# hubble hubble.audit
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
[ERROR ] Problem occurred trying to invalidate hash cach for azurefs
Traceback (most recent call last):
File "/opt/hubble/hubble-libs/hubblestack/extmods/fileserver/azurefs.py", line 268, in update
shutil.rmtree(hash_cachedir)
File "shutil.py", line 239, in rmtree
File "shutil.py", line 237, in rmtree
OSError: [Errno 2] No such file or directory: '/var/cache/hubble/azurefs/hashes'
{'Compliance': '97%',
'Controlled': [{'CIS-1.1.8': 'AMI does not have this partition, will fix in hubble'},
{'CIS-1.1.3': 'AMI does not have this partition, will fix in hubble'},
{'CIS-1.1.5': 'AMI does not have this partition, will fix in hubble'},
{'CIS-1.1.4': 'AMI does not have this partition, will fix in hubble'},
{'CIS-1.1.9': 'AMI does not have this partition, will fix in hubble'},
{'CIS-5.2.15': 'Disabling it as per sos ticket 1307'},
{'CIS-<IP_ADDRESS>': 'Needs investigation spartans/hubble#4'},
{'CIS-<IP_ADDRESS>': 'We do not use syslog-ng in Image factory'},
{'CIS-1.1.10': 'AMI does not have this partition, will fix in hubble'},
{'CIS-<IP_ADDRESS>': 'We do not use chrony in AMI factory, we use ntpd'},
{'CIS-1.3.2': 'We use Hubble'},
{'CIS-1.1.14': 'AMI does not have this partition, will fix in hubble'},
{'CIS-<IP_ADDRESS>': 'We do not use syslog-ng in Image factory'},
{'CIS-4.2.4': 'Logged bug as sos 1441'},
{'CIS-2.2.15': 'Bug in Hubble - spartans/hubble#1'},
{'CIS-3.3.1': 'Seems bug in Hubble - spartans/hubble#5'},
{'CIS-3.3.2': 'Seems bug in Hubble - spartans/hubble#5'}],
'Failure': [{'CIS-5.2.16': 'Ensure SSH warning banner is configured'},
{'CIS-5.2.1': 'Ensure permissions on /etc/ssh/sshd_config are configured'},
{'CIS-5.2.12': 'Ensure only approved MAC algorithms are used'},
{'CIS-6.2.6': 'Ensure root PATH Integrity'}],
'Success': [{'CIS-2.2.5': 'Ensure DHCP Server is not enabled'},
{'CIS-2.3.1': 'Ensure NIS Client is not installed'},
{'CIS-2.3.2': 'Ensure rsh client is not installed'},
{'CIS-2.3.3': 'Ensure talk client is not installed'},
{'CIS-2.3.4': 'Ensure telnet client is not installed'},
{'CIS-2.3.5': 'Ensure LDAP client is not installed'},
{'CIS-2.2.3': 'Ensure Avahi Server is not enabled'},
{'CIS-2.2.4': 'Ensure CUPS is not enabled'},
{'CIS-2.1.9': 'Ensure tftp server is not enabled'},
{'CIS-2.2.2': 'Ensure X Window System is not installed'},
{'CIS-2.2.9': 'Ensure FTP Server is not enabled'},
{'CIS-1.5.4': 'Ensure prelink is disabled'},
{'CIS-2.2.6': 'Ensure LDAP server is not enabled'},
{'CIS-2.1.6': 'Ensure rsh server is not enabled'},
{'CIS-2.1.7': 'Ensure talk server is not enabled'},
{'CIS-3.6.1': 'Ensure iptables is installed'},
{'CIS-2.1.8': 'Ensure telnet server is not enabled'},
{'CIS-2.2.16': 'Ensure NIS Server is not enabled'},
{'CIS-1.3.1': 'Ensure AIDE is installed'},
{'CIS-3.4.1': 'Ensure TCP Wrappers is installed'},
{'CIS-2.1.11': 'Ensure xinetd is not enabled'},
{'CIS-5.2.2': 'Ensure SSH Protocol is set to 2'},
{'CIS-5.3.4': 'Ensure password hashing algorithm is SHA-512'},
{'CIS-5.3.3': 'Ensure password reuse is limited'},
{'CIS-5.2.7': 'Ensure SSH HostbasedAuthentication is disabled'},
{'CIS-5.3.1': 'Ensure password creation requirements are configured'},
{'CIS-5.2.5': 'Ensure SSH MaxAuthTries is set to 4 or less'},
{'CIS-5.2.9': 'Ensure SSH PermitEmptyPasswords is disabled'},
{'CIS-1.4.2': 'Ensure authentication required for single user mode'},
{'CIS-1.4.3': 'Ensure interactive boot is not enabled'},
{'CIS-1.5.1': 'Ensure core dumps are restricted'},
{'CIS-5.2.6': 'Ensure SSH IgnoreRhosts is enabled'},
{'CIS-5.3.2': 'Ensure lockout for failed password attempts is configured'},
{'CIS-5.2.14': 'Ensure SSH LoginGraceTime is set to one minute or less'},
{'CIS-6.2.3': 'Ensure no legacy "+" entries exist in /etc/shadow'},
{'CIS-6.2.2': 'Ensure no legacy "+" entries exist in /etc/passwd'},
{'CIS-5.2.10': 'Ensure SSH PermitUserEnvironment is disabled'},
{'CIS-6.2.4': 'Ensure no legacy "+" entries exist in /etc/group'},
{'CIS-5.2.13': 'Ensure SSH Idle Timeout Interval is configured'},
{'CIS-5.2.8': 'Ensure SSH root login is disabled'},
{'CIS-3.4.2': 'Ensure /etc/hosts.allow is configured'},
{'CIS-3.4.3': 'Ensure /etc/hosts.deny is configured'},
{'CIS-<IP_ADDRESS>': 'Ensure message of the day is configured properly'},
{'CIS-<IP_ADDRESS>': 'Ensure password expiration is 90 days or less'},
{'CIS-<IP_ADDRESS>': 'Ensure rsyslog default file permissions configured'},
{'CIS-<IP_ADDRESS>': 'Ensure password expiration warning days is 7 or more'},
{'CIS-<IP_ADDRESS>': 'Ensure minimum days between password changes is 7 or more'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of hfs filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of FAT filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of squashfs filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of udf filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of cramfs filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of freevxfs filesystems is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of jffs2 filesystems is disabled'},
{'CIS-3.6.2': 'Ensure default deny firewall policy'},
{'CIS-3.6.3': 'Ensure loopback traffic is configured'},
{'CIS-1.2.3': 'Ensure gpgcheck is globally activated'},
{'CIS-<IP_ADDRESS>': 'Ensure mounting of hfsplus filesystems is disabled'},
{'CIS-5.2.4': 'Ensure SSH X11 forwarding is disabled'},
{'CIS-<IP_ADDRESS>': 'Ensure ntp is configured'},
{'CIS-<IP_ADDRESS>': 'Ensure inactive password lock is 30 days or less'},
{'CIS-5.5': 'Ensure access to the su command is restricted'},
{'CIS-5.4.4': 'Ensure default user umask is 027 or more restrictive'},
{'CIS-5.2.3': 'Ensure SSH LogLevel is set to INFO'},
{'CIS-1.1.15': 'Ensure nodev option set on /dev/shm partition'},
{'CIS-1.1.17': 'Ensure noexec option set on /dev/shm partition'},
{'CIS-1.1.16': 'Ensure nosuid option set on /dev/shm partition'},
{'CIS-1.1.19': 'Disable Automounting'},
{'CIS-2.2.7': 'Ensure NFS and RPC are not enabled'},
{'CIS-<IP_ADDRESS>': 'Ensure rsyslog Service is enabled'},
{'CIS-2.2.8': 'Ensure DNS Server is not enabled'},
{'CIS-2.1.2': 'Ensure daytime services are not enabled'},
{'CIS-2.1.3': 'Ensure discard services are not enabled'},
{'CIS-5.1.1': 'Ensure cron daemon is enabled'},
{'CIS-2.1.1': 'Ensure chargen services are not enabled'},
{'CIS-2.1.10': 'Ensure rsync service is not enabled'},
{'CIS-2.1.4': 'Ensure echo services are not enabled'},
{'CIS-2.1.5': 'Ensure time services are not enabled'},
{'CIS-2.2.14': 'Ensure SNMP Server is not enabled'},
{'CIS-2.2.11': 'Ensure IMAP and POP3 server is not enabled'},
{'CIS-2.2.10': 'Ensure HTTP server is not enabled'},
{'CIS-2.2.13': 'Ensure HTTP Proxy Server is not enabled'},
{'CIS-2.2.12': 'Ensure Samba is not enabled'},
{'CIS-6.1.9': 'Ensure permissions on /etc/gshadow- are configured'},
{'CIS-6.1.8': 'Ensure permissions on /etc/group- are configured'},
{'CIS-1.4.1': 'Ensure permissions on bootloader config are configured'},
{'CIS-3.4.4': 'Ensure permissions on /etc/hosts.allow are configured'},
{'CIS-5.1.2': 'Ensure permissions on /etc/crontab are configured'},
{'CIS-3.4.5': 'Ensure permissions on /etc/hosts.deny are configured'},
{'CIS-6.1.3': 'Ensure permissions on /etc/shadow are configured'},
{'CIS-5.1.5': 'Ensure permissions on /etc/cron.weekly are configured'},
{'CIS-5.1.4': 'Ensure permissions on /etc/cron.daily are configured'},
{'CIS-5.1.7': 'Ensure permissions on /etc/cron.d are configured'},
{'CIS-5.1.6': 'Ensure permissions on /etc/cron.monthly are configured'},
{'CIS-5.1.3': 'Ensure permissions on /etc/cron.hourly are configured'},
{'CIS-<IP_ADDRESS>': 'Ensure permissions on /etc/issue are configured'},
{'CIS-6.1.6': 'Ensure permissions on /etc/passwd- are configured'},
{'CIS-6.1.7': 'Ensure permissions on /etc/shadow- are configured'},
{'CIS-6.1.4': 'Ensure permissions on /etc/group are configured'},
{'CIS-6.1.5': 'Ensure permissions on /etc/gshadow are configured'},
{'CIS-6.1.2': 'Ensure permissions on /etc/passwd are configured'},
{'CIS-5.1.8': 'Ensure at/cron is restricted to authorized users'},
{'CIS-4.2.3': 'Ensure rsyslog or syslog-ng is installed'},
{'CIS-6.2.1': 'Ensure password fields are not empty'},
{'CIS-6.2.5': 'Ensure root is the only UID 0 account'},
{'CIS-5.2.11': 'Ensure only approved ciphers are used'},
{'CIS-6.2.9': 'Ensure users own their home directories'},
{'CIS-6.2.8': "Ensure users' home directories permissions are 750 or more restrictive"},
{'CIS-1.1.18': 'Ensure sticky bit is set on all world-writable directories'},
{'CIS-5.4.2': 'Ensure system accounts are non-login'},
{'CIS-5.4.3': 'Ensure default group for the root account is GID 0'},
{'CIS-6.1.10': 'Ensure no world writable files exist'},
{'CIS-6.1.11': 'Ensure no unowned files or directories exist'},
{'CIS-6.1.12': 'Ensure no ungrouped files or directories exist'},
{'CIS-3.2.4': 'Ensure suspicious packets are logged'},
{'CIS-3.2.5': 'Ensure broadcast ICMP requests are ignored'},
{'CIS-3.2.6': 'Ensure bogus ICMP responses are ignored'},
{'CIS-3.2.7': 'Ensure Reverse Path Filtering is enabled'},
{'CIS-3.2.1': 'Ensure source routed packets are not accepted'},
{'CIS-3.2.2': 'Ensure ICMP redirects are not accepted'},
{'CIS-3.2.3': 'Ensure secure ICMP redirects are not accepted'},
{'CIS-3.1.2': 'Ensure packet redirect sending is disabled'},
{'CIS-3.1.1': 'Ensure IP forwarding is disabled'},
{'CIS-3.2.8': 'Ensure TCP SYN Cookies is enabled'},
{'CIS-1.5.3': 'Ensure address space layout randomization (ASLR) is enabled'}]}

It has not been reported. I'll look into it.

I fixed it in #251. It's a false positive that you can ignore for now, I think.


speakol

Domain(s) to be blocked:

rd.speakol.com

Who?

Speakol is a MENA region-focused content discovery & recommendation platform. It provides Premium Native Ads to the most relevant audience.

Based in Egypt.
Functions like Taboola
Found where?
https://m.khaleejtimes.com/news/dubai-coin-cryptocurrency-was-never-approved-by-any-official-authority

Thank you for this Nainar @bnainar.
What are we looking at here?  I don't understand.

On the screenshot(left column),where it says "paid content".i think 🤔

@StevenBlack, it's like Taboola. In the screenshot, from below paid
content, those "reactions" are provided by the news website itself
On Sun, May 30, 2021, 21:57 Steven Black @.***> wrote:

Thank you for this Nainar @bnainar https://github.com/bnainar.
What are we looking at here? I don't understand.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StevenBlack/hosts/issues/1672#issuecomment-851025865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIRHCGEH6MH52UAZ3GVCFTTQJRP3ANCNFSM45YOILLA
.

@bnainar it's actually cdn.speakol.com according to AdGuard,which already took care of it for me 😄
Test it,post results please 👍

Steve @StevenBlack no doubt it belongs here,so i made one easy copy/paste for ya 😉 :
<IP_ADDRESS> mc.speakol.com
<IP_ADDRESS> rd.speakol.com
<IP_ADDRESS> inline.speakol.com
<IP_ADDRESS> pixel.speakol.com
<IP_ADDRESS> cdn.speakol.com
<IP_ADDRESS> recommendation.speakol.com
<IP_ADDRESS> crawler.speakol.com
<IP_ADDRESS> ads.speakol.com
<IP_ADDRESS> plugins.speakol.com
<IP_ADDRESS> publishers.speakol.com
<IP_ADDRESS> www.speakol.com
<IP_ADDRESS> speakol.com
<IP_ADDRESS> cstorage.speakol.com
<IP_ADDRESS> pstorage.speakol.com
<IP_ADDRESS> api.speakol.com
<IP_ADDRESS> analytics.speakol.com
<IP_ADDRESS> alert.speakol.com
<IP_ADDRESS> dev.speakol.com
<IP_ADDRESS> dev.publishers.speakol.com

How did you find this many domains? I was checking my DNS logs, but only
found rd subdomain. Curious about your methodology, @dnmTX
On Mon, May 31, 2021, 02:27 dnmTX @.***> wrote:

Steve @StevenBlack https://github.com/StevenBlack no doubt it belongs
here,so i made one easy copy/paste for ya 😉 :
<IP_ADDRESS> mc.speakol.com
<IP_ADDRESS> rd.speakol.com
<IP_ADDRESS> inline.speakol.com
<IP_ADDRESS> pixel.speakol.com
<IP_ADDRESS> cdn.speakol.com
<IP_ADDRESS> recommendation.speakol.com
<IP_ADDRESS> crawler.speakol.com
<IP_ADDRESS> ads.speakol.com
<IP_ADDRESS> plugins.speakol.com
<IP_ADDRESS> publishers.speakol.com
<IP_ADDRESS> www.speakol.com
<IP_ADDRESS> speakol.com
<IP_ADDRESS> cstorage.speakol.com
<IP_ADDRESS> pstorage.speakol.com
<IP_ADDRESS> api.speakol.com
<IP_ADDRESS> analytics.speakol.com
<IP_ADDRESS> alert.speakol.com
<IP_ADDRESS> dev.speakol.com
<IP_ADDRESS> dev.publishers.speakol.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/StevenBlack/hosts/issues/1672#issuecomment-851060182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIRHCDIWCC2O444RTPZSB3TQKREZANCNFSM45YOILLA
.

How did you find this many domains?

@bnainar the rest are just additional(not employed in that specific websites),but concidering the nature of the domain,mine as well add the rest.Might save you looking that paid content somewhere else 😉

Thanks everybody!  This is added in commit a6d995d94d56c7d4f10fd915c13b37943dcf5f6c.
Closing.

@StevenBlack, why are you creating a new release just for this domain? Or is this a periodic thing that you do? Also what's the update on other new issues

Please read the release notes @bnainar.


New version: IDRIX.DirHash 1.24.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/110118&drop=dogfoodAlpha

False-positive? I'm not sure what to do with that info :/

Manual Validation failed with:

2:46:14 PM:  > 2023-06-19 14:46:13.215 [FAIL] Installer failed security check. Url: https://github.com/idrassi/DirHash/releases/download/DirHash_1.24.0/DirHash-1.24.0-x64.zip Result: 0x80004005

@stephengillie
I'm the author of DirHash and I would like to query about the cause of the failed security check because the error 0x80004005 indicated in your comment translates to "Unspecified error" which is not very specific.
I have run a check on VirtusTotal for the exe file inside DirHash-1.24.0-x64.zip and no issues were found: https://www.virustotal.com/gui/file/d02ecc173f4427c407fa140750021bbfb34124b5af7f3f418b8b8beae543acf8?nocache=1
Also, the exe file inside the zip is digitally signed using a valid EV code signing certificate from GlobalSign.
Could it be that the check is failing because it is a zip file and not an exe file?
Thank you for your help.

@wingetbot run

@ItzLevvie any updates on this?

@stephengillie I'm the author of DirHash and I would like to query about the cause of the failed security check because the error 0x80004005 indicated in your comment translates to "Unspecified error" which is not very specific.
I have run a check on VirtusTotal for the exe file inside DirHash-1.24.0-x64.zip and no issues were found: https://www.virustotal.com/gui/file/d02ecc173f4427c407fa140750021bbfb34124b5af7f3f418b8b8beae543acf8?nocache=1
Also, the exe file inside the zip is digitally signed using a valid EV code signing certificate from GlobalSign.
Could it be that the check is failing because it is a zip file and not an exe file?
Thank you for your help.

This must have been a false positive. It passed the Defender scan. Thanks for your patience and understanding.


chore: add 3.3 to test matrix

Codecov Report
Patch and project coverage have no change.

Comparison is base (e4a674c) 34.00% compared to head (5b1ade6) 34.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #973   +/-   ##
=======================================
  Coverage   34.00%   34.00%
=======================================
  Files         100      100
  Lines       11896    11896
=======================================
  Hits         4045     4045
  Misses       7458     7458
  Partials      393      393

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Release the scoring scripts?

Hi, thanks a lot for this great work which quite inspires me!
I wonder if it is possible to release the scoring scripts to reproduce any results (e.g., Table 2.) in your paper?
Looking forward to your reply!

Looking into this, will get back to you soon. Do I understand correctly that you are interested in evaluation scripts, where let's say, you have output of model A and want to compare it with the ground truth / gold labels?

Please have a look at the script that runs the LXMERT evaluation on VALSE. Hope it helps.

Hi, I had a question about the following portion of the LXMERT script, where test_sentences contains [caption, foil]:
`inputs = lxmert_tokenizer(
test_sentences,
padding="max_length",
max_length=30,  # 20
truncation=True,
return_token_type_ids=True,
return_attention_mask=True,
add_special_tokens=True,
return_tensors="pt"
)
output_lxmert = lxmert_base(
input_ids=inputs.input_ids,
attention_mask=inputs.attention_mask,
visual_feats=features,
visual_pos=normalized_boxes,
token_type_ids=inputs.token_type_ids,
return_dict=True,
output_attentions=False,
)
m = torch.nn.Softmax(dim=1)
output = m(output_lxmert['cross_relationship_score'])
cross_score = output_lxmert['cross_relationship_score']
out_dict = {}
out_dict['lxmert'] = {'caption': 0, 'foil': 0} # 0 is not detected, 1 is detected
out_dict['lxmert']['caption'] = output[0, 1].item() # probability of fitting should be close to 1 for captions
out_dict['lxmert']['foil'] = output[1, 0].item() # probability of fitting, should be close to 0 for foils`
Specifically, my question regards the last few lines. My understanding is that each row of the output variable will contain a probability for that caption being [incorrect, correct]. So shouldn't we then be accessing output[0,1] and output[1,1], as we are interested in the probability of caption and foil, respectively? I am concerned that accessing output [1,0] for foil, we are basically assuming that the "incorrectness probability" of foil is its likelihood score. Since LXMERT seems to often put this incorrectness number pretty low and the likelihood higher, this approach seems to assure that the foil will get a low score regardless. Does that make sense?
And if so, I was also thinking that perhaps one should be doing the softmax along dimension 0, i.e. the positive likelihood scores should add up to 1 so that we can use that as a classification output score. But that is a less important issue.
Thanks!

Related to this, the MMSHAP implementation of a very similar task actually accesses the second column of each LXMERT output score, which seem to match what I am saying: https://github.com/Heidelberg-NLP/MM-SHAP/blob/main/mm-shap_lxmert_dataset.py#L262 (line 262)

Hi @skshvl ,
Thanks for pointing this out! Indeed, either this line of code or its description in the comment is wrong  (it should say: should be close to 1 for foils, and not 0). I'm editing the line right now.
However, for computing the tables in the paper, I've used the script lines starting here and not the output dictionaries that we've been talking about above, so the accessed values and results are correct.


Makefile: Use a POSIX-compatible test ('==' -> '=')

With dash 0.5.7:
# make docs
/bin/sh: 1: test: 1.3.3: unexpected operator
/bin/sh: 1: test: 1.3.3: unexpected operator
/bin/sh: 1: test: 1.3.3: unexpected operator
Makefile:47: *** cannot build output//oci-runtime-spec.pdf without either pandoc or docker.  Stop.
# command -V test
test is a shell builtin

POSIX defines = for string comparison; the == form is a Bashism.
SHELL was added in f3fdf03 (Makefile: prefer bash, 2016-05-25, #455) to avoid these "unexpected operator" errors, but there's no reason to require Bash when we can make the comparison's POSIX compliant.
This PR is an alternative to #534.

carried to #547


chore: tweak log level for some error message

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

Project coverage is 71.83%. Comparing base (8d42e56) to head (8aa8568).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #199   +/-   ##
========================================
  Coverage    71.83%   71.83%
========================================
  Files           25       25
  Lines         6735     6735
========================================
  Hits          4838     4838
  Misses        1897     1897

Flag
Coverage Δ

unittests
71.83% <ø> (ø)

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

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


Add request builder

This could look something like this for a GET request:
    let result: Response = Request::get("http://yourdomain.xyz/your/path")
        .set_header("Authorization", "Bearer <token here>")
        .send()
        .await?

and maybe something like this for a POST:
    let result: Response = Request::get("http://yourdomain.xyz/your/path")
        .set_header("Authorization", "Bearer <token here>")
        .body("<body string>")
        .send()
        .await?

If anybody who sees this issue has features they think would be nice, whilst not being completely bloat, please do let me know as i am actively working on this


kubefirst: 2.4.10 -> 2.4.17

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubefirst/kubefirst/releases.
meta.description for kubefirst is: Tool to create instant GitOps platforms that integrate some of the best tools in cloud native from scratch
meta.homepage for kubefirst is: https://github.com/kubefirst/kubefirst/
meta.changelog for kubefirst is: https://github.com/kubefirst/kubefirst/releases/tag/v2.4.16
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.16 with grep in /nix/store/l6wk94gkskac088ry09yr63m3mnhbkjc-kubefirst-2.4.16
found 2.4.16 in filename of file in /nix/store/l6wk94gkskac088ry09yr63m3mnhbkjc-kubefirst-2.4.16

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kubefirst

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/112498a9fa5a0dda218714e16cd17c5a5287d4d7#kubefirst

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubefirst

Maintainer pings
cc @qjoly for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubefirst/kubefirst/releases.
meta.description for kubefirst is: Tool to create instant GitOps platforms that integrate some of the best tools in cloud native from scratch
meta.homepage for kubefirst is: https://github.com/kubefirst/kubefirst/
meta.changelog for kubefirst is: https://github.com/kubefirst/kubefirst/releases/tag/v2.4.17
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.17 with grep in /nix/store/k1brmr43ikd7pich557vnsm5vl8naq0i-kubefirst-2.4.17
found 2.4.17 in filename of file in /nix/store/k1brmr43ikd7pich557vnsm5vl8naq0i-kubefirst-2.4.17

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

kubefirst

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/14f0757fcc72194dc61185e7fa6c5c757c5d5dc9#kubefirst

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubefirst

Maintainer pings
cc @qjoly for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


DEP 4 branch dev requirements

Issue https://github.com/silverstripeltd/product-issues/issues/531
This PR's a bit different from the other recipe pull-requests that it targets the next-minor branch, rather than the current-minor
Looks like what happened is this wasn't merged up correctly during the 4.10 CMS release, so this is fixing that.

Nope, it's a loose caret requirement so it'll just grab a stable version.  We only need to upgrade references to branches.


Unreliable results while FAMD model is returned from a function.

Hi,
I did notice that when you return the FAMD transform object from a function, the next results are sometimes unreliable. The following code snippet elucidates the issue :
import prince
import pandas as pd
from sklearn import linear_model
cv_train = pd.read_csv('cv_training3.csv')
famd = prince.FAMD(
    n_components=25,
    n_iter=10,
    copy=True,
    check_input=True,
    engine='auto',
    random_state=42)
x_cols = [col for col in cv_train.columns if col != 'LogSalePrice']
print(x_cols)

X = cv_train[x_cols]
famd_model = famd.fit(X)
transformed_X = famd_model.transform(X)

my_model = linear_model.LinearRegression()
my_model.fit(transformed_X, cv_train['LogSalePrice'].values.ravel())

cv_validation = pd.read_csv('cv_validation3.csv')

old_predictions = my_model.predict(transformed_X)
print(old_predictions.mean())

new_X = cv_validation[x_cols]

new_transformed_X = famd_model.transform(new_X)

new_predictions = my_model.predict(new_transformed_X)
print(new_predictions.mean())

We have the following output :
['MSSubClass', 'LogGrLivArea', 'MSZoning']
12.030180212569563
-2158687260190.6848

Now consider the following code snippet :
import pandas as pd
import prince
from sklearn import linear_model

def get_trained_model_and_transform(X, Y, num_components=25, num_iter=20):
    famd = prince.FAMD(
        n_components=num_components,
        n_iter=num_iter,
        copy=True,
        check_input=True,
        engine='auto',
        random_state=42)

    famd_model = famd.fit(X)
    transformed_X = famd_model.transform(X)

    my_model = linear_model.LinearRegression()

    my_model.fit(transformed_X,Y)

    return (my_model, famd_model)

cv_train = pd.read_csv('cv_training3.csv')

x_cols = [col for col in cv_train.columns if col != 'LogSalePrice']
print(x_cols)

X = cv_train[x_cols]

(my_model, famd_model) = get_trained_model_and_transform(X,
                                                         cv_train['LogSalePrice'].values.ravel())

cv_validation = pd.read_csv('cv_validation3.csv')
transformed_X = famd_model.transform(X)
old_predictions = my_model.predict(transformed_X)
print(old_predictions.mean())

new_X = cv_validation[x_cols]

new_transformed_X = famd_model.transform(new_X)

new_predictions = my_model.predict(new_transformed_X)
print(new_predictions.mean()
)

The output is the following :
['MSSubClass', 'LogGrLivArea', 'MSZoning']
12.0300579767497
11.946205619238583

The only difference between the 2 snippets, is that we have wrapped the transform and model building to a function in the second whereas we have not done that in the first (and the results are drastically different).
I am attaching the input data files here as well. Feel free to let me know if you need more information.
NOTE : For the sake of ease of testing, I have included both these snippets as two scripts (script1.py and script2.py ) in the attached folder. I have added a screenshot of the output on my mac terminal as well.
However, I also tested these two scripts on an online python interface (https://repl.it/languages/python3) and they look to be giving identical outputs. I am using the production version of prince module for these scripts and had to change my matplotlib backend to Agg on my mac to get this working on my mac. Would that be the reason for the different result ?
data.zip
Thanks

Are you sure? I just ran this and the second snippet returned the same output as the first one. By the way you can tell GitHub to use Python highlighting by using ````python` at the top of your snippet.

Hi @MaxHalford ,
I have updated my previous comment to include another example. However, as I have updated in my previous comment, there is an interesting observation :
Testing  these two scripts on an online python interface (https://repl.it/languages/python3) and gave dentical outputs. I am using the production version of prince module for these scripts and had to change my matplotlib backend to Agg on my mac to get this working on my mac. Would that be the reason for the different result ?

I just took a look and it seems that the parameter for the number of iterations, n_iter, is set to 10 in script1.py and to 20 in script2.py. It seems that this is the cause of the difference between both scripts.

@babinu-uthup-4JESUS any news?


Incorrect enum identifier in example

the typedef enum identifier should be WifiConfig_Secuirity instead of GPIO_OutputMode;
typedef enum {
WifiConfig_Security_Unknown = 0,
WifiConfig_Security_Open = 1,
WifiConfig_Security_Wpa2_Psk = 2
} GPIO_OutputMode;

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

ID: a13d196b-4cd8-12b9-a8a0-08e020307fe2
Version Independent ID: ac4fe98d-804e-9b52-8fa6-55915610256a
Content: WifiConfig_Security enumeration - Azure Sphere
Content Source: AzureSphere/articles/reference/applibs-reference/applibs-wificonfig/enum-wificonfig-security.md
Product: azure-sphere
GitHub Login: @esalc
Microsoft Alias: azurespheredocs

@ninosarmiento
Thanks for the feedback! We are currently investigating and will update you shortly.

@ninosarmiento Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@pennyo can you have a look at this? Thank you!

Good catch! We'll fix this in the next update of the documentation.

Fixed in today's 19.05 documentation release. Closing this issue.


add missing images for K8s Policy paper

Signed-off-by: Jim Bugwadia<EMAIL_ADDRESS>I had missed moving the images folder! Added and re-generated the PDF.

Hi @PushkarJ and @savitharaghunathan - apologies I missed this in the prior PR!

/lgtm

/lgtm


[Python] remove debug with wrong syntax

Couldn't compile devel with python 3 otherwise.

It looks like this was unintentionnaly added in #808