Support QubitUnitary() with more than two wires

Similar to #170 & #175.
It's better for simulation to support arbitrary quantum gates with more than two wires(CSWAP for example), though impractical for plugins about quantum devices to some extent.
the source code implies that more than two wires are not allowed:
        # apply unitary operations
        if len(wires) == 1:
            U = self.expand_one(A, wires)
        elif len(wires) == 2:
            U = self.expand_two(A, wires)
        else:
            raise ValueError('This plugin supports only one- and two-qubit gates.')

and just copy the error information here:

/usr/local/lib/python3.6/dist-packages/pennylane/decorator.py in wrapper(*args, **kwargs)
151         def wrapper(*args, **kwargs):
152             """Wrapper function"""
--> 153             return qnode(*args, **kwargs)
154
155         # bind the jacobian method to the wrapped function
/usr/local/lib/python3.6/dist-packages/pennylane/qnode.py in call(self, *args, **kwargs)
455         # pylint: disable=no-member
456         args = autograd.builtins.tuple(args)  # prevents autograd boxed arguments from going through to evaluate
--> 457         return self.evaluate(args, **kwargs)  # args as one tuple
458
459     @ae.primitive
/usr/local/lib/python3.6/dist-packages/autograd/tracer.py in f_wrapped(*args, **kwargs)
46             return new_box(ans, trace, node)
47         else:
---> 48             return f_raw(*args, **kwargs)
49     f_wrapped.fun = f_raw
50     f_wrapped._is_autograd_primitive = True
/usr/local/lib/python3.6/dist-packages/pennylane/qnode.py in evaluate(self, args, **kwargs)
510             check_op(op)
511
--> 512         ret = self.device.execute(self.queue, self.ev)
513         return self.output_type(ret)
514
/usr/local/lib/python3.6/dist-packages/pennylane/_device.py in execute(self, queue, expectation)
206             self.pre_apply()
207             for operation in queue:
--> 208                 self.apply(operation.name, operation.wires, operation.parameters)
209             self.post_apply()
210
/usr/local/lib/python3.6/dist-packages/pennylane/plugins/default_qubit.py in apply(self, operation, wires, par)
324             U = self.expand_two(A, wires)
325         else:
--> 326             raise ValueError('This plugin supports only one- and two-qubit gates.')
327
328         self._state = U @ self._state
ValueError: This plugin supports only one- and two-qubit gates.

Hi @Raycosine! The reason the default.qubit plugin only supports one- and two-qubit gates is because it is designed to be a very simple and basic reference plugin, provided mostly as a guide for plugin developers (and a useful reference to run our unit tests against). As a result, it is not optimized for high performance, and only supports limited features (i.e., maximum of two-qubit operations/expectations, no mixed state simulations, etc.).
In general, we would suggest using a plugin for a specialized qubit simulator (for example, either PennyLane-Forest or PennyLane-ProjectQ) for production code.
At the same time, if you would like to submit a PR adding support for QubitUnitary for more than two wires to the default.qubit device, we'd be more than happy!

Thanks @josh146 ! It's my fault never trying those plugins lol.


not able to find device with blue

I run your Example but in scanning no device find in device list. After QR code scan also list sowing Error. device not found. Please help me out.

Hi @rajani9288, please share the below information:
Description
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
...

Frequency
Tell us the number of times you are able to reproduce the issue. It will help us to check if the issue is occurring intermittently.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
ESP Device Information:

ESP-IDF version: [e.g. 4.0]
Example referenced: [e.g. wifi_prov_mgr]
Board type: [e.g. ESP-32]

iOS information:

Device type: [e.g. iPhone/iPad]
Device model: [e.g. iPhone 7]
iOS version: [e.g. iOS8.1]
App Version: [e.g. v.2.0.8]

Provisioning information:

ESPProvision iOS SDK version: [e.g. 2.0.8] (if applicable)
Device type: [e.g. SoftAP/ BLE]
Security: [e.g. Secure/Unsecure]

ESP Device logs:
If applicable, add device logs here.
Additional context
Add any other context about the problem here.


fix forking console

Fixes WB-11880
Description
What does the PR do?
Testing
How was this PR tested?
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

@raubitsj oh interesting, so our decorator doesn't work here? do you know why?

@raubitsj oh interesting, so our decorator doesn't work here? do you know why?

yep.. the decorator was only for top level methods for the run object, this was a callback that we installed on the write method of stdout/stderr...   we might be able to do an attach from there, but it just scares me so the safe thing for now is to ignore stdout/stderr output from forked processes.

Closed in favor of consolidated https://github.com/wandb/wandb/pull/4877 which was just merged


Add field id to the exported metrics

This value in the WS XML output seems to uniquely determine individual fields, hopefully independent of language.
Next step could be creating a map from these IDs to English-based identifiers suitable for database columns etc.

Oh that's really bad. I thought the identifiers are unique, but didn't verify it across reboots / SW upgrades. If it's just memory addresses then sadly there is no point in exposing them this way. I'll then retract this PR.


HOLD for Payment [2024-05-16] [$250] Room - Room name character limit is 79 characters instead of 100

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.65-5
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4506180
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to staging.new.expensify.com
Go to FAB > Start chat.
Go to Room tab.
Try to enter more than 79 characters.

Expected Result:
The room name character limit is 100 characters.
Actual Result:
The room name character limit is 79 characters.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/f50a3d83-c19c-40bf-ba91-ae30a60b4858

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014d41cf935d9bcfd5
Upwork Job ID:<PHONE_NUMBER>519520768
Last Price Increase: 2024-04-25
Automatic offers:

eh2077 | Reviewer | 0
GandalfGwaihir | Contributor | 0

Issue OwnerCurrent Issue Owner: @isabelastisser

We think this issue might be related to the #vip-vsb.

@GandalfGwaihir 's proposal looks good to me. The root cause is clear. We can use this constant for the length limit
https://github.com/Expensify/App/blob/0b9665445c41fe5e080edd739583426087ccab79/src/CONST.ts#L1913
We can discuss the detail implementation in PR.
🎀👀🎀 C+ reviewed

That proposal works for me as well! We might want to keep a separate constant for the 99 / 100 issue, but yes can discuss.

@GandalfGwaihir is this ready for payment? Please provide an update. Thanks!

@GandalfGwaihir is this ready for payment? Please provide an update. Thanks!

@isabelastisser It's not ready yet.

✋ This PR was not deployed to staging yet because QA is ongoing.

ready for payment!

Reviewing!

The payments were processed in Upwork. This should be all set!


Fix install: add package directory

Currently, running flit install or pip install . in this repo results in a broken install. Specifically, _types.py is missing:
import xstac

---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-1-10350dece1c0> in <module>
----> 1 import xstac

~/.pyenv/versions/anaconda3-2019.10/envs/xc/lib/python3.8/site-packages/xstac.py in <module>
     10 from typing import List
     11
---> 12 from _types import TemporalDimension, HorizontalSpatialDimension, Datacube, Variable
     13
     14 __version__ = "1.0.0"

ModuleNotFoundError: No module named '_types'

I've resolved this by wrapping both xstac.py (renamed to _xstac.py) and _types.py in a package directory.

Mmm thanks.
Just an FYI, I think the _types.py stuff will eventually be removed, and we would instead use pystac: https://github.com/stac-utils/pystac/blob/13a9fad2b7de7a8cbb139395f60242e1f24b4042/pystac/extensions/datacube.py.

Just an FYI, I think the _types.py stuff will eventually be removed, and we would instead use pystac

Good to know!
Going to see now about xstac'ing some of our ocean surface zarrs. Will report back with any further findings.

Sounds good. I'm sure it will fail!
From: Charles Stern @.>
Sent: Thursday, June 24, 2021 12:35 PM
To: TomAugspurger/xstac @.>
Cc: Tom Augspurger @.>; State change @.>
Subject: Re: [TomAugspurger/xstac] Fix install: add package directory (#2)
Just an FYI, I think the _types.py stuff will eventually be removed, and we would instead use pystac
Good to know!
Going to see now about xstac'ing some of our ocean surface zarrs. Will report back with any further findings.

You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTomAugspurger%2Fxstac%2Fpull%2F2%23issuecomment-867824874&data=04|01|tom.augspurger%40microsoft.com|3e86fff7963c428e83d808d9373671a0|72f988bf86f141af91ab2d7cd011db47|1|0|637601529248104741|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=UfgIEUzFX51kAYnTj7jblf7JcbRGA5nNVETDRs09Q50%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAKAOIXS54WNA6V47J7RLNLTUNUFPANCNFSM47IJ2Q2Q&data=04|01|tom.augspurger%40microsoft.com|3e86fff7963c428e83d808d9373671a0|72f988bf86f141af91ab2d7cd011db47|1|0|637601529248114738|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=WFrFM%2BucME0dfkZi0YDVKGf7Wkby5qmGCXT%2FEONDp88%3D&reserved=0.


Question: How automatically run Bddgen after updating feature file on VS code ? at the moment after every change we have execute bddgen

Please, try watch mode.


Semantic Tokens Overlapping Support

I am currently working on a LSP implementation for a markdown like language and I want to use
semantic tokens to highlight the original text in the editor.
At the moment (<= 1.66.2), vscode does not support overlapping tokens.
This makes semantic tokens nearly impossible to use for languages like markdown, because there are many overlapping tokens.
e.g.
**bold *inner italic* outer bold**

Using TextMate and regex is also not really an option, because it takes much more effort to write a compiler/LSP + regex statements. Keeping them in sync is also difficult and for some more complex scenarios, regex cannot handle the tokenization correctly.
Is it planned to support overlapping tokens at some point? I have not found any open issues about this topic.
Thanks!

We don't have any plans to support overlapping semantic tokens, simply because the implementation cost of storing, updating and reading the tokens is not worth it. One simple solution would be for you to flatten them out on your side before returning them. e.g.:
|---------------tokenA--------------|
           |---tokenB---|
|---tokenA-|---tokenAB--|---tokenA--|

Thanks for your response.
I will try to flatten them as you mentioned and use modifiers too.


Frama-C

Frama-C is missing.

Hi. Thanks for the info. Would you mind creating a pull request for that. I'd merge it right away. 😃


RDS logs as input doesn't work

Problem
I want to use this plugin to input RDS logs from Cloudwatch which are not output in a JSON structure, however the plugin seems to only support JSON messages and i'm wondering why. I might be missing something here.
...
Steps to replicate

Export RDS logs to clodwatch
Setup input

<source>
	@type cloudwatch_logs
	tag cloudwatch
	log_group_name /aws/rds/instance/instancesrds-skyfallperf-postings/postgresql
	log_stream_name instancesrds-skyfallperf-postings
	fetch_interval 20
	use_log_stream_name_prefix true
	json_handler json
	state_file /etc/fluent/rds_state.pos
</source>

Now for every parsed log there will be the following:
2020-02-19 11:13:04 +0000 [error]: Invalid JSON encountered while parsing event.message
2020-02-19 11:13:04 +0000 [warn]: dump an error event: error_class=Yajl::ParseError error="parse error: unallowed token at this point in JSON text\n                          2020-02-18 18:50:53 UTC:<IP_ADDRESS>(47612\n                     (right here) ------^\n" location="/usr/lib/ruby/gems/2.5.0/gems/yajl-ruby-1.4.1/lib/yajl.rb:44:in `parse'" tag="cloudwatch" time=1582051853 record={:message=>"2020-02-18 18:50:53 UTC:<IP_ADDRESS>(47612):perf_skyfall_integrations@perf_skyfall_integrations:[5517]:STATEMENT:  SELECT pg_database.datname, pg_database_size(pg_database.datname) as size FROM pg_database"}

Expected Behavior or What you need to ask
I would expect messages to be parsed regardless of format within the "message" parameter coming from the cloudwatch event. Is there a specific reason why these are mandatory to be valid JSON?
...
Using Fluentd and CloudWatchLogs plugin versions

Alpine  -  v1.7.4-1.0
Kubernetes
Fluentd 1.0

/ $ fluentd --version
fluentd 1.9.2

Dependent gem versions

    && fluent-gem install fluent-plugin-prometheus -v 1.7.0 \
    && fluent-gem install fluent-plugin-elasticsearch -v 3.8.0 \
    && fluent-gem install fluent-plugin-multi-format-parser -v 1.0.0 \
    && fluent-gem install fluent-plugin-cloudwatch-logs -v 0.8.0 \

Got around this by adding an undocumented parameter to the input source.
It then became:
<source>
	@type cloudwatch_logs
	tag cloudwatch
	log_group_name /aws/rds/instance/instancesrds-skyfallperf-postings/postgresql
	log_stream_name instancesrds-skyfallperf-postings
	fetch_interval 20
	use_log_stream_name_prefix true
	json_handler json
        format /(?<message>.+)/
	state_file /etc/fluent/rds_state.pos
</source>

Noticed this after reading through the code and it can be found on the Configure STS credentials section as an example.


Support nushell

It would be great to support nushell for code highlighting and code execution

presenterm uses bat's syntax files and they don't support nushell so it's not trivial to add support for it here and we'd need to add something separate just for it. If enough people want nushell support or any other language that's not supported by bat, I think it makes sense to add it. But until then I'd like to keep this issue open.

Oh right, I'll check to add nushell syntax highlighting in bat.
But for script execution inside presenterm, it doesn't need bat ?

Yeah sorry, I forgot about half of the question. Yes, code execution is unrelated and should be straightforward to add :ok_hand:

I just added execution support in #274.

Thx, I'll check that out
It's indeed a mess to add nushell syntax highlighting in bat for now

I did a pr because it was missing something for nushell to work https://github.com/mfontanini/presenterm/pull/275
Also the way the executor works it spawn a shell script that run the code making nushell only works on linux and not platform like windows.
I'm wondering why always spawning a bash shell to do this instead of spawning the specific shell mentioned (like fish for a fish script etc...)... but supporting nushell on windows would require more investigation and work for now

For shell scripts in general the code doesn't code through an intermediate bash shell but because of some internal reasons that was not trivial to do for nutshell so I did it this way to make it work and not keep you waiting for to long. I'll do it the proper way soon.
But you do bring up a good point which is that the executor scripts we have now to execute arbitrary code snippets is not Windows friendly...

I think code execution should come with a parameter in the cli and by default it should not execute arbitrary code.
Secure by default kind of like the rust philosophy

You need to explicitly press a key binding now to execute code. Do you think that's not enough? Something I've been thinking is executable code snippets should have some visual indication so you know they're executable.
I do agree that it would be good to be able to enable/disable it, but I feel like disabling by default is a bit harsh.

You can press keys inadvertently, especcialy CTRL+E is not an unusual keybindings and you can have this bindings in other software or pree E instead of C if you wanted to CTRL+C.
Yes it may be a bit harsh to require something an option like presenterm -x demo.md to enable code execution. Security should be a priority in general, juste like the rust programming language philosophy is.
I think people should be able to run others / unknown presentation without thinking of priority by default.
And requiring -x for instance to run your own markdown file is not much of a pain to do

press E instead of C if you wanted to CTRL+C

lol not sure I buy this, those keys are very far apart. But I do agree with the general argument and this is actually the reason why I was against this change https://github.com/mfontanini/presenterm/pull/254#issuecomment-2136276413 even though I think that's a good idea. I'll make changes so that:

You need to run presenterm -x to enable code execution.
And you can override this globally in your config file so you don't have to do this every time. It's up to you: if you only ever run your own presentations you can set this and avoid having to run with -x every time.

This kind of deviated from the original issue but #276 implements what I mentioned in the comment above.

Just as an FYI I changed this in #282 so that this no longer requires an intermediate bash script.


Use System.IO.Pipelines for sending

Refactors command sending to use System.IO.Pipelines

Serializes full command into Pipe Writer, returning any Serialization Exceptions to PublishAsync
Kicks off Flush to Pipe Reader
At this point, the Command is considered "Enqueued for Sending", and no further Cancellation is possible.  A successful status is returned to the caller

There is a possibility that the Connection drops before the Pipe Reader is read and actually sends the bytes on the Network.  If so, the bytes remain in the Pipe Reader and will be sent if the Connection reconnects.  So the only way to ensure that the bytes were actually sent to the server is to perform a round-trip with PingAsync.  I believe that this behavior is similar to the Go client.
Performance
Performance is similar to WaitUntilSent=false but a little better due to some reduced allocations
Before:

Method
Iter
Mean
Error
StdDev
Gen0
Allocated

WaitUntilSentTrue
64
981.8 μs
945.78 μs
51.84 μs
1.9531
6.82 KB

WaitUntilSentFalse
64
119.6 μs
61.53 μs
3.37 μs
-
1.1 KB

WaitUntilSentTrue
512
7,139.8 μs
6,944.54 μs
380.65 μs
15.6250
52.21 KB

WaitUntilSentFalse
512
549.3 μs
851.19 μs
46.66 μs
2.9297
10.43 KB

WaitUntilSentTrue
1024
16,415.3 μs
5,228.92 μs
286.61 μs
31.2500
104.26 KB

WaitUntilSentFalse
1024
1,015.8 μs
1,783.37 μs
97.75 μs
13.6719
43.74 KB

After

Method
Iter
Mean
Error
StdDev
Allocated

PublishAsync
64
115.5 μs
68.81 μs
3.77 μs
510 B

PublishAsync
512
439.4 μs
778.86 μs
42.69 μs
535 B

PublishAsync
1024
806.7 μs
1,379.06 μs
75.59 μs
542 B

Backwards Compatibility
I aimed to make the changes as Backward Compatible as possible, but there are some considerations:

NatsPubOpts.WaitUntilSent and NatsPubOpts.ErrorHandler have been marked as Obsolete

Those were the only 2 options in NatsPubOpts
There still could be future options in NatsPubOpts, such as a per-publish CommandTimeout override.  So we probably shouldn't get rid of it

CommandTimeout was lowered from 1 minute by default to 5 seconds.  It is used to throw a Timeout exception if anything in the path of sending the command times out, including:

Connection does not enter Connected State
Cannot acquire Semaphore required to access Pipe Writer
Pipe is full and cannot Flush the last command that was enqueued

JetStream AckOpts were not in a format that matched NatsPubOpts and NatsSubOpts so I standardized those and got rid of WaitUntilSent

I just started a long running test with JS publisher and consumer just to make sure there are no regressions.

It is also useful and simplifies a lot just to use a BoundedChannel as the "Semaphore" for the pipeline writer. It saves you from having to use a Semaphore and a bunch of try/finallies to synchronize the pipe flushes. So publish commands to the channel (it can have a pretty low size), and have a worker thread pull stuff off from it and send to the PipeWriter.

It is also useful and simplifies a lot just to use a BoundedChannel instead of SemaphoreSlim to synchronize writes to the PipeWriter, since SemaphoreSlim, despite it's name, is not really a lightweight synchronization primitive

We could, but we would have to introduce another layer of memory and copying.  Right now Command Writer is writing directly to the Pipe Writer's buffers, which are the same buffers that get flushed to the Pipe Reader and sent on the wire.  Access to the Pipe Writer's buffers must be serialized.
Worse case scenario for adding a BoundedChannel<Memory<byte>> is another (Max Message Size * Bounded Channel Size) bytes of memory, and adding a copy to the Pipe Writer for every message.  It could end up being faster for highly parallel environments, would have to benchmark.  Maybe we save that for a potential future improvement though?

I'm still reviewing but wanted to try to add some flavor to all of this;

We could, but we would have to introduce another layer of memory and copying. Right now Command Writer is writing directly to the Pipe Writer's buffers, which are the same buffers that get flushed to the Pipe Reader and sent on the wire. Access to the Pipe Writer's buffers must be serialized.

At this point I probably -should- pull down the PR and look, How does SemaphoreSlim help here? Main reason I ask is that it does not, AFAIK, have FIFO behavior as a guarantee.

Worse case scenario for adding a BoundedChannel<Memory<byte>> is another (Max Message Size * Bounded Channel Size) bytes of memory, and adding a copy to the Pipe Writer for every message. It could end up being faster for highly parallel environments, would have to benchmark. Maybe we save that for a potential future improvement though?

It's possible that it was being suggested, rather than use a BoundedChannel<Memory<byte>>... but instead to use Channel<T> (in the past I've done Channel<Exception> with sentinels or Channel<int> with numbers for state... [0]) with  in a specific way to mimic a SemaphoreSlim.
Getting more specific, as a semi-contrived example, SubscribeAsync now does a TryWait, if that fails it then dumps into the state machine. but I'd have to guess that the TryWait->WaitAsync will have more interlocked/volatile operations than a ReadAsync or WaitToReadAsync on a ChannelReader. [1]
[0] - In fact, I have done so on more than one occasion to 'gate' NatsConnection and various things on disconnect/reconnect.
[1] - I've seen this myself, where WaitToReadAsync on a BoundedChannel worked better than SemaphoreSlim.


Export the original latex format in html

I'm wondering if the latex format can be saved and shown correctly when exporting to html.
Here are the examples.

ChatGPT-Sine_Formula_Explanation.json

I think we can try to include latex.js or generate the image embedded. Are you interested in submitting a PR?

The new commit is a70a8b1 feat: html enhancements: toggle width & latex rendering
There are new package requirements and some modest upgrades in this commit.
I did clone a clean repo and verified the build and functional tests.
Text from the original PR:

Added a second toggle for widescreen view
Added katex to template.html to render latex. (This is the same engine OpenAI uses.)

The default render was not very readable but after some experimentation I found a format close to the original by adding \displaystyle and \large macros to the preprocessor.
Bare css was not able to center the display math (vs. inline) because identical css is generated for both. I check the nodes on either side of the latex parent for text to determine if it is inline and apply the proper formatting.

Final PR #275


Align idpRow label to the left on mobile

It sounds like you're looking in the wrong place.  This change is for the consent screen, the default Idp is for the WAYF.
Steps to reproduce:

open consent page
go to mobile view (phone)
look at the alignment of the "something incorrect" label.  Atm, it looks like this:

After this PR it should look like this:

Ah, I must-have had something sticking in my eye.

Thanks for the steps to reproduce! I fully agree with this change.
While keeb-testing. I ran into a small inconsistance that I was unable to screenshot, but reproduced it in Photoshop. See screenshot below. The hover state on a hidden (x) button might have to be removed. But I think this is for another PR..


Module can be delayed to start loading.

Greaka at 7/19/2019 4:35:40 AM +00:00

BTW, my 3 marker packs took 10min to load yesterday
Debug module active and debugger attached ^^
Ah, and bhud has an unhandled exception when unloading the debug module

REF: https://discordapp.com/channels/531175899588984842/536970543736291346/601633233691607069

I can confirm that loading modules using tasks has not worked as expected.  The biggest problem is the amount needed to load some modules but how little time is yielded to them for them to finish their work.
I've found that the duration taken to load some modules exceeds TaskCreationOptions.LongRunning meaning tasks are not ideal for such durations.  Additionally, modules will often block other modules from loading due to not yielding enough between the module loading and the render loop of the core application.
You'll find that locking the FPS can change module load times as well as the core application is able to yield more frequently.
In tests, I've placed the LoadAsync call on its own thread and found much better performance all around.  Modules are loaded infrequently (when the application is started and when a module is enabled), so the extra overhead of a thread is no problem - even in cases where a module does not need to actually load much.

This comes down mostly to the frequency that a module yields during load.


plotjuggler: data dir arg for local routes

Support running plot juggler with local routes
$ ls /home/incognitojam/realdata
'0000000000000000|2022-03-20--15-08-07--1'
'0000000000000000|2022-03-20--15-08-07--2'
...

$ ./juggle.py --data_dir="/home/incognitojam/realdata" "0000000000000000|2022-03-20--15-08-07"

We use route and segment names in a bunch of different scripts, and I'd like to support this use case without adding this as an argument to all of them. My two thoughts are either an environment variable or prefixing the route name with the path: /home/incognitojam/realdata/0000000000000000|2022-03-20--15-08-07. @gregjhogan what do you thihk?

I would update the call to SegmentName(route_or_segment_name, allow_route_name=True) to handle route_or_segment_name being /home/incognitojam/realdata/0000000000000000|2022-03-20--15-08-07 by adding a new property named data_dir (default to None if only a route or segment name is passed in).  Then we can pass the SegmentName.data_dir value into Route() (like you did in the PR, but now it is not a new param).

Closing in favour of https://github.com/commaai/openpilot/pull/24473.


Speedup training on GPU (remove CPU bottleneck on broadcast phases)

Running against latest stable release of tensorflow (1.12) yields poor model performance for training/inference on GPU for EncodeProcessDecode-based models. It can be observed that CPU gets heavily used (and becomes the bottleneck) while GPU usage is spiky at best.
We observed that this happens because certain ops such as tf.cumsum and tf.gather were always being placed on the CPU even when allocated/running in a with tf.device("/GPU:0") block, which can be easily verified by running the session with config=tf.ConfigProto(log_device_placement=True).
The cause of this behavior is that some of these ops don't have implementations for GPU for certain data types on the latest stable release (see tensorflow/tensorflow#5445, or this comment https://github.com/tensorflow/tensorflow/issues/13164#issuecomment-332076675 related to gather_nd which also applies to cumsum per current code in https://github.com/tensorflow/tensorflow/blob/73e3215c3a2edadbf9111cca44ab3d5ca146c327/tensorflow/core/kernels/scan_ops.cc#L149 ).
The consequence of this behavior is a significant slowdown on training because tensor data has to be copied from GPU memory, processed by CPU, and copied back to GPU, during the broadcast steps which cause serious bottlenecks in the computation graph.
This fix casts the data types into something that allows these ops to run in GPU. The cast overhead is insignificant compared with the performance gain. We observed nearly 5x speedup in training with a relatively simple EncodeProcessDecode model with 6 processing steps on GPU-enabled systems.

Thank you for your PR!
We are currently working on more rigorous benchmarking of the library and this sounds potentially very relevant. We will get back to you about this soon.

#16

I signed it!

Hi, any plans to merge this Pull Request? Without this our workloads take ages and if it makes sense to you we'd love to use the mainline with this improvement.
Let us know what are the plans with this.
Thanks!

I was able to verify that the tf.cumsum op is indeed placed on the CPU, however I did not see any significant differences in actual execution time for batch size = 100 (all of the repeat ops are called with n_node or n_edge in the repeats parameter, and both have the dimension of the batch size).
I did observe a difference of about 3x for batch size = 1000, but this is far larger than the usual batch sizes we use, and still does not explain 5x speedup. It could be that this gets amplified in the back-propagation stages.
Some questions:

Could you provide some minimal working code where you observe the speed up? What size of graphs/features are you using?
Can you verify if it also happens when running in Colaboratory?
There will also be an official TF implementation of repeat that is in the process of being exposed in this PR. Although not officially part of the exposed TF API yet, this can already be imported as from tensorflow.python.ops.ragged.ragged_util import repeat, and in my benchmark seems to be much faster than any of the alternatives. Could you try to see if adding that to utils_tf and removing the previous repeat method also fixes your problem.

Thanks in advance!
Here's the snippet I used to benchmark the different versions of the function in Colaboratory with a GPU kernel (The logs for the device placement are available from the Runtime menu):
https://colab.research.google.com/drive/16PytptaaVtDONla59ybwlpR2k1KUuz3y

Hi @alvarosg
Thanks for taking a look at this. Regarding your questions on the actual speedup and batch sizes we're using, here's a little bit of context.
Training time is an important cost function for us. Our batching strategy was mostly optimized for speed. We try to make the most of the GPU, and have nvidia-smi to always report >90% usage during training, otherwise it would mean we had a bottleneck somewhere else. To achieve this we use cached tf.data.Datasets with prefetching. We also have to pick a batch size that is enough to keep all those cuda cores busy.
Our dataset is in the millions of graphs, but the main issue is that they have high variance in size (they can range from 1 node to 2k nodes or 0 to 4k edges). This variance makes it difficult to have a fixed batch size as it would need to be low enough that if the biggest graphs were all in the same batch the model training wouldn't go out-of-memory, but that batch size would be too small for efficiency. So we cut batches with dynamic sizes which are based on upper limits in the number of nodes and edges within the batch. This means that for a particular task, our batches can vary between 3 and about 400 graphs, with each batch fitting at most 10k nodes and 10k edges. We observed that this dynamic batch sizing strategy would cut training time on a particular task from 22h59m to 8h10m. The number of batches processed per second is also more stable with dynamic batching.
The ~5x speedup observed was under these circumstances, when we'd already changed the training strategy so that we were making the most of the GPU. I'd expect that with other bottlenecks still present the speedup will be less noticeable. It was also observed in TF 1.12, but at least tf.cumsum was optimized a lot for 1.13 and that could also make it less of a difference.
We'd need to do a lot of cleanup/refactoring in order to share our ingestion/training code. We're currently postponing that effort to when TF2 gets released as stable, because it'll simplify enormously that code.
I'll try to test the unreleased implementation of repeat and let you know the difference it makes.
As a last remark, I'd like to thank you for your time pursuing this and to thank your team for releasing such a great library.

We have now included GPU kernels for cumsum with integer types in tensorflow (https://github.com/tensorflow/tensorflow/commit/db3ecd34a4fd527912207e1374a905d8fd247622). This should in principle fix the issue.

. This should in principle fix the issue.
Thanks for your works! I have the same problem of speed. which version is this feature added to?

We have now included GPU kernels for cumsum with integer types in tensorflow (tensorflow/tensorflow@db3ecd3). This should in principle fix the issue.

Thanks for your works! I have the same problem of speed. which version is this feature added to?

Closing this PR for now, since now utils_tf.repeat just calls tf.repeat.
Thanks everyone!


Release 0.18.2 (previous release 0.18.1 publish process got broken)

Previous release 0.18.1 is incomplete because publishing libvcx docker image silently failed
Releasing libvcx docker image version 0.18.1, tagged docker.pkg.github.com/hyperledger/aries-vcx/libvcx:0.18.1
The push refers to repository [docker.pkg.github.com/hyperledger/aries-vcx/libvcx]
5f70bf18a086: Preparing
677317b7bb65: Preparing
958dcc0bb643: Preparing
ed93e08f5e4a: Preparing
10ce3b93143e: Preparing
250adad2e09e: Preparing
9c750d09432d: Preparing
f18998204895: Preparing
5f70bf18a086: Preparing
0a28081e49af: Preparing
3b06dff7e1f0: Preparing
32f366d666a5: Preparing
9c750d09432d: Waiting
f18998204895: Waiting
0a28081e49af: Waiting
3b06dff7e1f0: Waiting
32f366d666a5: Waiting
250adad2e09e: Waiting
10ce3b93143e: Pushed
ed93e08f5e4a: Pushed
958dcc0bb643: Pushed
5f70bf18a086: Pushed
250adad2e09e: Pushed
9c750d09432d: Pushed
f18998204895: Pushed
32f366d666a5: Layer already exists
3b06dff7e1f0: Pushed
0a28081e49af: Pushed
677317b7bb65: Pushed
received unexpected HTTP status: 500 Internal Server Error

So this release contains no changes, just to re-release artifacts.
Signed-off-by: Patrik Stas<EMAIL_ADDRESS>

Codecov Report

Merging #290 (78bb8be) into master (8f3c46b) will decrease coverage by 4.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #290      +/-   ##
==========================================
- Coverage   49.69%   45.38%   -4.31%
==========================================
  Files         151      150       -1
  Lines       19452    18559     -893
  Branches     6122     5795     -327
==========================================
- Hits         9666     8423    -1243
- Misses       5053     6073    +1020
+ Partials     4733     4063     -670

Flag
Coverage Δ

integration
?

unittests
45.38% <ø> (ø)

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

Impacted Files
Coverage Δ

libvcx/src/libindy/utils/pool.rs
14.58% <0.00%> (-52.42%)
:arrow_down:

libvcx/src/libindy/utils/anoncreds.rs
18.04% <0.00%> (-46.50%)
:arrow_down:

libvcx/src/utils/plugins.rs
0.00% <0.00%> (-33.34%)
:arrow_down:

libvcx/src/libindy/utils/ledger.rs
12.00% <0.00%> (-28.00%)
:arrow_down:

libvcx/src/utils/random.rs
75.00% <0.00%> (-25.00%)
:arrow_down:

libvcx/src/utils/devsetup.rs
40.08% <0.00%> (-23.97%)
:arrow_down:

libvcx/src/utils/devsetup_agent.rs
0.00% <0.00%> (-21.17%)
:arrow_down:

libvcx/src/init.rs
25.80% <0.00%> (-20.97%)
:arrow_down:

libvcx/src/credential_def.rs
36.72% <0.00%> (-14.74%)
:arrow_down:

libvcx/src/libindy/utils/payments.rs
39.25% <0.00%> (-12.57%)
:arrow_down:

... and 25 more

Continue to review full report at Codecov.

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


training code of MemoryLLM

Can you provide the training code of MemoryLLM?

Sorry I cannot provide training code

I'm cleaning up the training code and will opensource the training code before the end of this month

Please check the folder train


Keep going on failure?

Thanks for this tool, especially the feature powerset function is very handy!
I was wondering if there could be a mode like make -k which errors are recorded, but all runs will still be completed, and failing combinations reported at the end.

Added in 0.5.9 (#140)


Adding optional API listen address and public port options

Description
Includes the changes from #3429 and adds a dapr-public-port to expose the Metadata and Health APIs publicly.
Closes #2914
Closes #3475
Checklist

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-test


[Accessibility] Error analysis screen reader

Signed-off-by: Ruby Zhu<EMAIL_ADDRESS>
Description

This PR add screen reader description for the error analysis tree
when coming to the error analysi tree, screen reader will read "interactive chart".
when traversing each tree node, screen reader will read the condition and tooltip content, for example, in below screen shot for the selected node, screen reader will announce:
marital-status ==  Married-civ-spouse Correct (#):  9 Incorrect (#):  17 Error coverage 94.44% Error rate 65.38 %
For disabled view, screen reader will announce the text on the node

Checklist

[x] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #1663 (5b2ecb0) into main (4b15495) will decrease coverage by 13.45%.
The diff coverage is n/a.

:exclamation: Current head 5b2ecb0 differs from pull request most recent head 277e313. Consider uploading reports for the commit 277e313 to get more accurate results

@@             Coverage Diff             @@
##             main    #1663       +/-   ##
===========================================
- Coverage   89.03%   75.58%   -13.46%
===========================================
  Files         105       10       -95
  Lines        5529      258     -5271
===========================================
- Hits         4923      195     -4728
+ Misses        606       63      -543

Flag
Coverage Δ

unittests
75.58% <ø> (-13.46%)
:arrow_down:

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

Impacted Files
Coverage Δ

erroranalysis/erroranalysis/_internal/metrics.py

...onsibleai/responsibleai/serialization_utilities.py

raiwidgets/raiwidgets/explanation_constants.py

raiutils/raiutils/version.py

...eai/responsibleai/managers/data_balance_manager.py

...onsibleai/responsibleai/managers/causal_manager.py

...bleai/responsibleai/_tools/causal/causal_result.py

raiwidgets/raiwidgets/__init__.py

...is/erroranalysis/_internal/process_categoricals.py

raiutils/raiutils/models/model_utils.py

... and 85 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


💅 lint/complexity/useLiteralKeys suggests incorrect fix

Environment information
CLI:
  Version:                      1.7.1
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.11.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.6.12"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Linter:
  Recommended:                  false
  All:                          false
  Rules:                        complexity/noBannedTypes = "error"
                                complexity/noUselessTypeConstraint = "error"
                                complexity/useLiteralKeys = "error"
                                complexity/useOptionalChain = "error"
                                correctness/noPrecisionLoss = "error"
                                correctness/noUnusedVariables = "error"
                                style/noInferrableTypes = "error"
                                style/noNamespace = "error"
                                style/useAsConstAssertion = "error"
                                style/useBlockStatements = "off"
                                style/useConsistentArrayType = "error"
                                style/useConst = "off"
                                style/useForOf = "error"
                                style/useShorthandFunctionType = "error"
                                suspicious/noEmptyBlockStatements = "off"
                                suspicious/noExplicitAny = "off"
                                suspicious/noExtraNonNullAssertion = "error"
                                suspicious/noMisleadingInstantiator = "error"
                                suspicious/noUnsafeDeclarationMerging = "error"
                                suspicious/useAwait = "off"
                                suspicious/useNamespaceKeyword = "error"

Workspace:
  Open Documents:               0

Rule name
lint/complexity/useLiteralKeys
Playground link
https://biomejs.dev/playground/?lintRules=all&code=ZgBsAGEAZwBzAFsAJwBfACcAXQBbADAAXQA7AA%3D%3D
Expected result
It should suggest
flags._.[0]

Instead of
flags._[0]

Code of Conduct

[X] I agree to follow Biome's Code of Conduct

It should suggest
flags._.[0]

Are you sure about this?
This looks like an invalid syntax as reported by the TypeSCript playground. The suggested fix seems correct to me.


Error using ER in Hugo quickstart

Hello,
I a newbie with Hugo and I'm trying this theme, but I'm getting the following error
Building sites … ERROR 2018/05/29 23:25:38 Error while rendering "taxonomyTerm" in "": template: /home/emiguel/src/emiguelt/quickstart/themes/er/layouts/_default/terms.html:5:5: executing "/home/emiguel/src/emiguelt/quickstart/themes/er/layouts/_default/terms.html" at <partial "nav.html" .>: error calling partial: template: theme/partials/nav.html:1:22: executing "theme/partials/nav.html" at <len .Site.Menus.main>: error calling len: len of untyped nil
My config.toml:
baseURL = "http://example.org/"
languageCode = "en-us"
title = "My New Hugo Site"
theme = "er

Do I need to add any other source? Could you please provide a config file example.
Thanks a lot!
emiguelt

Tks a lot! It works, but then I have the following error:
 Building sites … ERROR 2018/05/30 14:12:29 Error while rendering "home" in "": template: D:\src\emiguelt\quickstart\themes\er\layouts\index.html:23:3: executing "main" at <partial "tag_cloud.h...>: error calling partial: template: theme/partials/tag_cloud.html:5:13: executing "theme/partials/tag_cloud.html" at <first $maxtags .Site...>: error calling first: both limit and seq must be provided

thanks again!
The problem was that I have the first post as draft = true, I changed it to false, and rebuilt it successfully.


multiple traceback error  (import tensorflow as tf)..... [I am using Python 3.6.5 x64)

Issue with (import tensorflow as tf)..... details of error given below [I am using Python 3.6.5 x64)
Traceback (most recent call last):
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 14, in swig_import_helper
    return importlib.import_module(mname)
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 658, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 571, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 922, in create_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
ImportError: DLL load failed: A dynamic link library (DLL) initialization routine failed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 17, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 16, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    import tensorflow as tf
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\__init__.py", line 24, in <module>
    from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\__init__.py", line 49, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 74, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 14, in swig_import_helper
    return importlib.import_module(mname)
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 658, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 571, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 922, in create_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
ImportError: DLL load failed: A dynamic link library (DLL) initialization routine failed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 17, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 16, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File "C:\Users\anilt\AppData\Local\Programs\Python\Python36\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'

Failed to load the native TensorFlow runtime.

See https://www.tensorflow.org/install/install_sources#common_installation_problems

for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It looks like it's an installation error. Did you follow the instructions? It's typically because the DLL is missing some dependency, like the right CUDA version.

It has been 30 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


feat(zoombar): enable simple slider view

Closes #1489
Summary

Enabled the simple slider view for the zoomBar
See https://github.com/carbon-design-system/carbon-charts/issues/698 for more information about the design specs

Change List (commits, features, bugs, etc)

Abstracted ZoomBarPropTypes as they are the same prop types in both components
Updated zoomBar prop model to take in a new view prop that can be slider_view or graph_view
Updated carbon charts to pick up this new feature
Updated TimeSeriesCard stories to have a slider_view and graph_view story
Updated BarChartCard to have a slider_view story, and not graph_view because it looks a bit odd with it
Default both charts to use the slider_view

Acceptance Test (how to verify the PR)

Go to with zoomBar stories for TimeSeriesCard and BarChartCard and see that both the simple_view and graph_view are still working correctly

:tada: This PR is included in version 2.109.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Release 2.0.0

Questions
Answers

Description?
Release 2.0.0

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
N/A

How to test?
N/A

Possible impacts?
N/A

@matks you can use upgrade-1.0.1.php, you can even use matks-2.0.php :)

@matks Fixed for assets


Manage reviews (title, text, author and score) and add lang option

Hi,
This pull request contains 2 features :
1/ Parse reviews (author_name, title, body and score)
2/ Add option to choose the language (hl parameter on playstore)

@sebastien-cormier Thank you for the pull request!  I'm merging it now.

@sebastien-cormier I've released gem version 0.15.0 with your changes included.

Great, thanks !
2015-11-30 19:03 GMT+01:00 Chad Remesch<EMAIL_ADDRESS>
@sebastien-cormier https://github.com/sebastien-cormier I've released
gem version 0.15.0 with your changes included.
—
Reply to this email directly or view it on GitHub
https://github.com/chadrem/market_bot/pull/45#issuecomment-160707731.


update d4mac, d4win intros, add better feedback topics

Updated intro content for d4mac, d4win
Re-worked feedback topics
Added a swarm mode tutorial link to getting started tutorial last topic on "learn more"

Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

LGTM


fix(crystal/dwarf/info): parse Data16 values

resolves crashes when raising errors on static MUSL crystal apps built on alpine:3.16

Wow, you did it! 🎉 How did you find it was this?

For reference: This was first reported in https://forum.crystal-lang.org/t/help-with-static-build/4936/9

This is a follow-up to 11399 which originally implemented DWARF 5 support. Apparently I missed this case (probably because it was never used).

Someone in Discord suggested this could go into 1.5.2. What do you think?

Wow, you did it! 🎉 How did you find it was this?

Was monkey patching the code as you recommended, which required me to look at the implementation and work out where it was raising which led me to check the standard to find the enum value - then found @straight-shoota had already added the enum so I added the case

Would love to see this is 1.5.2 too

This monkey patch can be used as a workaround currently
require "crystal/dwarf/info"

# debugging dwarf file issues
struct Crystal::DWARF::Info
  private def read_attribute_value(form, attr)
    case form
    when FORM::Addr
      case address_size
      when 4 then @io.read_bytes(UInt32)
      when 8 then @io.read_bytes(UInt64)
      else        raise "Invalid address size: #{address_size}"
      end
    when FORM::Block1
      len = @io.read_byte.not_nil!
      @io.read_fully(bytes = Bytes.new(len.to_i))
      bytes
    when FORM::Block2
      len = @io.read_bytes(UInt16)
      @io.read_fully(bytes = Bytes.new(len.to_i))
      bytes
    when FORM::Block4
      len = @io.read_bytes(UInt32)
      @io.read_fully(bytes = Bytes.new(len.to_i64))
      bytes
    when FORM::Block
      len = DWARF.read_unsigned_leb128(@io)
      @io.read_fully(bytes = Bytes.new(len))
      bytes
    when FORM::Data1
      @io.read_byte.not_nil!
    when FORM::Data2
      @io.read_bytes(UInt16)
    when FORM::Data4
      @io.read_bytes(UInt32)
    when FORM::Data8
      @io.read_bytes(UInt64)
    when FORM::Data16
      @io.read_bytes(UInt64)
      @io.read_bytes(UInt64)
    when FORM::Sdata
      DWARF.read_signed_leb128(@io)
    when FORM::Udata
      DWARF.read_unsigned_leb128(@io)
    when FORM::ImplicitConst
      attr.value
    when FORM::Exprloc
      len = DWARF.read_unsigned_leb128(@io)
      @io.read_fully(bytes = Bytes.new(len))
      bytes
    when FORM::Flag
      @io.read_byte == 1
    when FORM::FlagPresent
      true
    when FORM::SecOffset
      read_ulong
    when FORM::Ref1
      @ref_offset + @io.read_byte.not_nil!.to_u64
    when FORM::Ref2
      @ref_offset + @io.read_bytes(UInt16).to_u64
    when FORM::Ref4
      @ref_offset + @io.read_bytes(UInt32).to_u64
    when FORM::Ref8
      @ref_offset + @io.read_bytes(UInt64).to_u64
    when FORM::RefUdata
      @ref_offset + DWARF.read_unsigned_leb128(@io)
    when FORM::RefAddr
      read_ulong
    when FORM::RefSig8
      @io.read_bytes(UInt64)
    when FORM::String
      @io.gets('\0', chomp: true).to_s
    when FORM::Strp, FORM::LineStrp
      # HACK: A call to read_ulong is failing with an .ud2 / Illegal instruction: 4 error
      #       Calling with @[AlwaysInline] makes no difference.
      if @dwarf64
        @io.read_bytes(UInt64)
      else
        @io.read_bytes(UInt32)
      end
    when FORM::Indirect
      form = FORM.new(DWARF.read_unsigned_leb128(@io))
      read_attribute_value(form, attr)
    else
      raise "Unknown DW_FORM_#{form.to_s.underscore}"
    end
  end
end


Typo "3600dpi" -> "360dpi"?

Hi,
is this a little typo in ipp-everywhere.test?
Greetings
Anne

[master 619d6d95e] Fix 360dpi typo (Issue #5300)
[branch-2.2 5c7df4f0e] Fix 360dpi typo (Issue #5300)


ci(wasmcloud): run actions only if wasmcloud files change

Feature or Problem
This PR uses https://github.com/tj-actions/changed-files to ensure that we only run wasmCloud CI if there is a change to a file that would affect the wasmCloud builds or tests.
Related Issues
#3875
Release Information

Consumer Impact

Testing
When I first submitted this PR, I left out the clause to run the wasmCloud CI if the action is changed. The result of that is https://github.com/wasmCloud/wasmCloud/actions/runs/12517799771, which skipped all wasmCloud CI and finished in 30s.
Unit Test(s)

Acceptance or Integration

Manual Verification

Not sure what's going on with the lint-cc action here

@brooksmtownsend it was mad because you had a space at the front of your commit message

@brooksmtownsend asked me to merge this


Article width and author bar

How to remove author bar from articles. If i will keep it how to customize size of author bar and my article and left ,right padding.

I think you just need to copy the page-author include in your includes folder and edit it according to your tastes


How to change english to others languages

First comment: look very nice ! good job !
I will try to use it in one of my projet, but I would like to know if you could put in option the possibility to change language:
Example: The gregorian calendar in French would be:

gregorian: { monthsNames: ['Janvier', 'Février', 'Mars', 'Avril', 'Mai', 'Juin', 'Juillet', 'Août', 'Septembre', 'Octobre', 'Novembre', 'Décembre'],daysNames: ['Dim', 'Lun', 'Mar', 'Mer', 'Jeu', 'Ven', 'Sam'],
today: 'Aujourd'hui'}

The second request would be to withdraw the possibility by option to change Calandar type.
I've found the way to do it on your code, but it would be nice to have it in future version.
Thanks.
Olivier

@newargus glad to hear that! :)

I will try to use it in one of my projet, but I would like to know if you could put in option the possibility to change language:

You are right, i considered the month and day names as constant variables. but in different countries it might be changed.
I'll rework this issue into a feature request. see it soon in next update.

The second request would be to withdraw the possibility by option to change Calandar type.

As described HERE, currently you can hide calendar type switch in entire of app by setting this option in app.run:
ADMdtp.setOptions({ calType: 'gregorian', multiple: false });
Is that what you want?

Thanks. Yes, I went through your readme file without seeing this option, m'y mistake. (It work as expected! Maybe could have a little css enhancement to have today to the right).
By the way, it would be nice to have the demo site with your package. Because, i've try to understand how you have made your customized green date button without succes.

By the way, it would be nice to have the demo site with your package.

Yes, absolutely. I'm working on it. :+1:
But before that its the code you tried for:
<adm-dtp ng-model="date16" options='{format: "Date: YYYY-MM-DD  Time: (hh:mm)", default: "today"}'>
    <button class="btn btn-success btn-block" dtp-toggle >{{date16}}</button>
</adm-dtp>


mat4.perspectiveFromFieldOfView fov wrong type

https://github.com/toji/gl-matrix/blob/master/src/gl-matrix/mat4.js#L1733-L1739
 * @param {mat4} out mat4 frustum matrix will be written into
 * @param {number} fov Object containing the following values: upDegrees, downDegrees, leftDegrees, rightDegrees
 * @param {number} near Near bound of the frustum
 * @param {number} far Far bound of the frustum
 * @returns {mat4} out
 */
mat4.perspectiveFromFieldOfView = function (out, fov, near, far) {
    var upTan = Math.tan(fov.upDegrees * Math.PI/180.0),
        downTan = Math.tan(fov.downDegrees * Math.PI/180.0),
        leftTan = Math.tan(fov.leftDegrees * Math.PI/180.0),
        rightTan = Math.tan(fov.rightDegrees * Math.PI/180.0),
        xScale = 2.0 / (leftTan + rightTan),
        yScale = 2.0 / (upTan + downTan);

{number} fov Object containing the following values: upDegrees, downDegrees - number is not object =)
Need make object fov.
Same bug and in gl-matrix.d.ts =(

Fixed. Thanks for pointing that out.


nixos: systemd: split module up into multiple files

Description of changes
Currently the systemd module is quite large. It contains multiple components that could be split off into separate files.
The idea behind this refactor is to not only make the modules more readable, but it is also a step towards more reusable systemd configuration building.
This PR does introduce a new option called systemd.additionalUpstreamUserUnits. It was introduced to have systemd-tmpfiles specify its own user units, instead of systemd-user doing that for systemd-tmpfiles. I think the way these upstream units still needs a bit of work, but I intend to do that in a separate PR.
A next step is to generalize unit directory building between systemd system and systemd user. The main intention is to also reuse this for systemd in initrd (https://github.com/NixOS/nixpkgs/pull/120015). It avoids creating yet another system of unit building.
I did not ran all tests, but I did ran the systemd tests as well as applied this configuration to my own system.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/777

Unfortunately I couldn't make the build unchanged, because the order of upstreamSystemUnits and upstreamUserUnits changed (due to merging the lists). The order of those lists shouldn't affect functionality.
I ran for each of the commits to make sure they succeed:
nix-build nixos/release.nix -A tests.systemd.x86_64-linux

cc @NixOS/systemd

I would really like to see this merge. It's been helpful in my systemd-initramfs effort

@GrahamcOfBorg test systemd

Could we squash the systemd-user bits into a single commit or split it off into a new PR?  Given it adds new functionaltiy it's a bit hard to follow that it's interwoven with plain refactorings.
Apart from that LGTM

I would really like to see this merge. It's been helpful in my systemd-initramfs effort

Review approval would help :smile: :+1:

🥳 thank you all!


Add RAPIDS notebook

Apparently only the owner of the repo can request reviewers, so tagging @andyndang here.
JIRA issue: [WHY-1768]


Add Suffix to debug build

Why? To  allow developers have both debug and release builds on their device.

Legitimate request, should be easy to implement

Fixed by #114, was happy to merge that!


Ubi micro image implementation

Description
Updating existing image to ubi-micro and use of podman and buildah
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

https://github.com/dell/csm/issues/922

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] Backward compatibility is not broken

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
Powerflex rpm installation
13 scenarios (13 passed)
98 steps (98 passed)
18m43.102221192s
2023/07/20 10:38:51 Volume test finished
Powerflex helm installation
13 scenarios (13 passed)
98 steps (98 passed)
18m28.513592944s
2023/07/20 11:29:19 Volume test finished
Powerscale rpm installation
3 scenarios (3 passed)
27 steps (27 passed)
4m48.437515964s
2023/07/20 12:08:14 Volume test finished
Powerscale helm installation
3 scenarios (3 passed)
27 steps (27 passed)
5m7.737859408s
2023/07/20 12:23:42 Volume test finished
Powermax rpm installation
8 scenarios (8 passed)
74 steps (74 passed)
9m51.86078202s
2023/07/24 13:11:42 Volume test finished
Powermax helm installation
8 scenarios (8 passed)
74 steps (74 passed)
14m30.223519298s
2023/07/24 14:38:38 Volume test finished

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test

run e2e test


option to restore to original replica count after ScaledObject's deletion

Documentation for https://github.com/kedacore/keda/issues/947
Signed-off-by: Zbynek Roubalik<EMAIL_ADDRESS>

Great docs, thanks @zroubalik !


milestone 4 wrap up

Given we're already way over budget, and we have a pretty good list of apps and formats now, it's probably time to wrap up milestone 4. To do this, I will:

[x] clean up the apps list
[x] clean up the data formats list
[x] clean up the glossary
[x] write a summary of our latest tier 1 / tier 2 thinking
[x] write up which tier 2 system can sync with which tier 1 system, and in which way(s)

This shouldn't stop anyone else from doing other documentation work! Just want to make sure our documentation is at the level where we can feel confident to send the Request for Payment for it.

I think WikiSuite and Prejournal can mostly import from existing timetracker apps, and export only to Scoro. I left this underspecified in the current text. Will update as and when I find more info on that.

I'm happy to contribute to the "write a summary of our latest tier 1 / tier 2 thinking" step mentioned above.

@Angus-McAllister great! Please edit https://github.com/federatedbookkeeping/timesheets#timesheets

I was a bit doubtful of whether to use the term "the club" or the term "Tier 2", in the end I used them both which might not be optimal. Please feel free to rework the paragraph, add your diagrams, etc!

I've been reflecting on the tier naming convention, and I think we should reconsider this.  Here's why: within "the club" of federated systems, if the number of point-to-point integrations increases beyond a manageable level for one or more systems, some of them could take on a more official "proxy" role for others (as all of those in the club do for those outside it).  They would hence be in effect a different tier.  Similar to how Autonomous Systems work for routing on the Internet, there could be additional tiers for these.
Perhaps those outside the club could be called "Outer Systems" or "External Systems", those at the edge providing connectivity between External Systems and the federation could be "Gateway Members", and those acting as go-betweens be "Federation Proxy Members" (with tiering for these in particular for large-scale examples).  I'm not that precious about the exact naming; it's more that the convention should have room for expansion should it be needed.


unused import and variable

hi @nicolaichuk . I cannot merge this.  The file you change is generated from https://github.com/nicolaichuk/gdx-dragome-backend/blob/bffdb80e760f488e399313eb36f3a6fcfcbbb226/extensions/gdx-bullet/gdx-bullet/src/com/badlogic/gdx/physics/bullet/collision/btCollisionShape.java
The only classes you can change is from "gdx-bullet/src" where it have code for c++ and javascript.
Some imports are used when generating for c++ jni and there is no support yet to remove those imports when generating javascript code.  Javascript code is when you see "[;;;]" in comment code block. No documentation for this yet.


App crashes on iOS with NativeScript 4.1

App previously worked with 4.0.1, updated to 4.1 version and now it crash.
Which platform(s) does your issue occur on?

iOS
iOS 11.3
emulator and device.

Please, provide the following version numbers that your issue occurs with:

CLI: 4.1.2
Cross-platform modules: 4.1.0
Runtime(s): tns-ios 4.1.1
Plugin(s):

"dependencies": {
   "@angular/animations": "~6.0.6",
   "@angular/common": "~6.0.6",
   "@angular/compiler": "~6.0.6",
   "@angular/core": "~6.0.6",
   "@angular/forms": "~6.0.6",
   "@angular/http": "~6.0.6",
   "@angular/platform-browser": "~6.0.6",
   "@angular/platform-browser-dynamic": "~6.0.6",
   "@angular/router": "~6.0.6",
   "nativescript-angular": "~6.0.6",
   "nativescript-camera": "^4.0.2",
   "nativescript-imagepicker": "^6.0.1",
   "nativescript-iqkeyboardmanager": "^1.2.0",
   "nativescript-ngx-fonticon": "^4.1.0",
   "nativescript-plugin-firebase": "^5.2.0",
   "nativescript-social-login": "^4.0.1",
   "nativescript-sqlite": "^2.0.1",
   "nativescript-theme-core": "~1.0.4",
   "nativescript-ui-listview": "^3.5.8",
   "nativescript-ui-sidedrawer": "~4.1.0",
   "reflect-metadata": "~0.1.10",
   "rxjs": "~6.1.0",
   "rxjs-compat": "^6.2.1",
   "tns-core-modules": "4.1.0",
   "zone.js": "~0.8.26"
 },
 "devDependencies": {
   "@angular/compiler-cli": "~6.1.0-beta.3",
   "@ngtools/webpack": "6.1.0-rc.0",
   "babel-traverse": "6.26.0",
   "babel-types": "6.26.0",
   "babylon": "6.18.0",
   "codelyzer": "~4.3.0",
   "lazy": "1.0.11",
   "nativescript-dev-sass": "~1.6.0",
   "nativescript-dev-typescript": "~0.7.0",
   "nativescript-dev-webpack": "~0.14.0",
   "tns-platform-declarations": "^4.0.0",
   "tslint": "~5.10.0",
   "typescript": "~2.7.2"
 }

Please, tell us how to recreate the issue in as much detail as possible.
Just ran the app using ins run iOS --emulator, the app is installed and shows the splash screen but then it fails.
Is there any code involved?
***** Fatal JavaScript exception - application has been terminated. *****
Native stack trace:
1   0x1030be649 NativeScript::reportFatalErrorBeforeShutdown(JSC::ExecState*, JSC::Exception*, bool)
2   0x1030f1860 -[TNSRuntime executeModule:referredBy:]
3   0x10273ca53 main
4   0x107c919ed start
JavaScript stack trace:
1   __@file:///app/vendor.js:132465:25
2   __extends@file:///app/vendor.js:132466:86
3   @file:///app/vendor.js:132760:52
4   ./delegate.ios.ts@file:///app/vendor.js:132792:2
5   webpack_require@file:///app/bundle.js:76:34
6   ./app.component.ts@file:///app/bundle.js:335:33
7   webpack_require@file:///app/bundle.js:76:34
8   ./app.module.ts@file:///app/bundle.js:610:91
9   webpack_require@file:///app/bundle.js:76:34
10  ./main.ts@file:///app/bundle.js:4154:88
11  webpack_require@file:///app/bundle.js:76:34
12  checkDeferredModules@file:///app/bundle.js:45:42
13  @file:///app/bundle.js:151:38
14  anonymous@file:///app/bundle.js:152:12
15  evaluate@[native code]
16  moduleEvaluation@[native code]
17  @[native code]
18  promiseReactionJob@[native code]
19  require@[native code]
20  anonymous@file:///app/starter.js:2:8
21  evaluate@[native code]
22  moduleEvaluation@[native code]
23  @[native code]
24  promiseReactionJob@[native code]
JavaScript error:
file:///app/vendor.js:132465:25: JS ERROR TypeError: Attempted to assign to readonly property.

HI @miguelopezv,
Try to remove the platforms, node_modules and hooks folders and rebuild the app via tns run ios.
If the issue persists, please send us sample project, which can be used for debugging.

closing due to inactivity


Implement corefunc_str_snake

Go: corefunc.StrSnake(string)
TF: corefunc_str_snake
A snake_case formatting option.

Resolved in https://github.com/northwood-labs/terraform-provider-corefunc/commit/bc0fbdef24b446173f2ed699ca9b142b84df9a24 and https://github.com/northwood-labs/terraform-provider-corefunc/commit/00a31369ec4732dadb677160131b1d401dfcdd3a.


Fix(Style): Support rtl in navigation

Issue :- #524
Development

Modified css to use dir attribute selector.

Bugfix cornecut in language selector.

Bugfix language selector icon not changing side in RTL.

Bugfix more button in menu not shifting based on rtl.

Bugfix more button not reflecting rtl in small screen.

LTR

RTL

LTR

RTL

@justintemps Language selector is fixed in this :)


Create multi worker_groups by loop

Hello guys please help, How can I create multi worker_groups, if I want for example 100 worker_groups , tried to use for and for each and local variables,  but it doesn't work
worker_groups = [
    {
      name                          = "worker-group-1"
      instance_type                 = "t3.small"
      additional_userdata           = "echo foo bar"
      asg_desired_capacity          = 2
      additional_security_group_ids = [aws_security_group.worker_group_mgmt_one.id]
    },
.
.
.
.

    {
      name                          = "worker-group-N"
      instance_type                 = "t3.medium"
      additional_userdata           = "echo foo bar"
      additional_security_group_ids = [aws_security_group.worker_group_mgmt_two.id]
      asg_desired_capacity          = 1
    },
  ]

tried work with local variables like
locals {
worker_groups =     [{
      name                          = "worker-group-2"
      instance_type                 = "t3.small"
      asg_desired_capacity          = 2

  },
  {
      name                          = "worker-group-3"
      instance_type                 = "t3.medium"
      asg_desired_capacity          = 1
    }
  ]
}

And then put it in worker_groups
worker_groups = [
    {
      name                          = "worker-group-1"
      instance_type                 = "t3.small"
      additional_userdata           = "echo foo bar"
      asg_desired_capacity          = 2
      additional_security_group_ids = [aws_security_group.worker_group_mgmt_one.id]
    },

    local.worker_groups

]

but it doesn't work too

you must generate input values in correct format. This is rather generic terraform programming than something strictly related to module.
I can advise you look into some example of such generation code patterns (for example we doing some generation here https://github.com/terraform-aws-modules/terraform-aws-eks/blob/1d1a73e138683373eea90525884c9abf0d57bbbb/aws_auth.tf#L39-L61).
I am closing this issue as it is not related to this module

And then put it in worker_groups
worker_groups = [
    {
      name                          = "worker-group-1"
      instance_type                 = "t3.small"
      additional_userdata           = "echo foo bar"
      asg_desired_capacity          = 2
      additional_security_group_ids = [aws_security_group.worker_group_mgmt_one.id]
    },

    local.worker_groups

]

but it doesn't work too

because you are trying to add element which is new list (instead of map). SO you must either concat two lists or add map (instead list into list)


Allow running validators against arbitrary config objects, not just ones with names

Because the validation was happening during array merging, we could only validate entries in arrays. However, some plugins (like repositories) do not accept an array, and others (like autolinks) do not have a name property. So here I am hoisting the logic into childPluginsList
IMO, ideally we could run a validator on the entier plugin config object, but that would break backwards compatibility, so I have added "back" the logic to run on a per array entry basis. If we are OK breaking that compat, then we may want to remove the isArray special case

I'll test it and merge it.

Hi @decyjphr - I saw you merged my other changes. Thanks! Any blockers on this last one?

No blockers but this one has changes that I have not finished testing. Hope to get it done in a few days.


How to install on WP

I have an issue where I can't install this through node on the web server and I also cannot change the JavaScript code on the web server.
In this case, I have a WordPress site, and I'm only able to navigate in the WordPress site and add the plugin or add the Iframe.
How can I have the snazzy-info-window on a WordPress only site.
I know, not the most sexy question, but in this case I'm stuck in de WordPress environment.
Or is this not possible?

Nothing?


transport_connect_tls:freerdp_set_last_error_ex

Describe the bug
After upgrading from F32 to F33 started to receive Error using Remmina connecting to RDP: Check that client and server support common TLS version.
To Reproduce
Steps to reproduce the behavior:

F32 + Remmina + freerdp
upgrade to F33
try to connect to RDP

Expected behavior
Successful connection.
Screenshots
ERROR][com.freerdp.core] - transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED [0x00020008]

Application details

FreeRDP version (xfreerdp /version): freerdp-libs-2.2.0-4.fc33.x86_64
OS version connecting to (server side): win7

Environment (please complete the following information):

OS: Linux Fedora 33
Architecture: [amd64, arm]: x86_64

Sounds like a fedora bug. Check openssl policy.
As you can imagine 2.2.0 did not become a different release since fedora 32

Hi, thanks for a quick response. Yeah, makes sense. Which policies do you have in mind? Seems openssl package was bumped, but I do also have compat- installed as well.

@mbevc1 look at the cipher configuration, maybe they are too strict (and the server you are connecting to requires older ssl)

Got it, F33 restricted default policy and switching back to update-crypto-policies --set DEFAULT:FEDORA32 works as win7 seems to be still using TLS 1.0

is solved by adding: /tls-seclevel:0 /timeout:80000

Here's the solution:
https://youtu.be/lkZ5gs2-x5I?si=fPs3UJijfcdsLt1G

Here's the solution: https://youtu.be/lkZ5gs2-x5I?si=fPs3UJijfcdsLt1G

Thank u sir!


Behavior when leaf nodes mount children

I need to decide what to do when leaf nodes mount children.
Here's an example problem:

Leaf node A is focused
A renders disabled child node B
Because of this, A can no longer be in focus!

I think the implication here is that leaf nodes must always remain leaf nodes, and if that changes, then a warning should be emitted.
Another option is that focus does just move up the tree until a leaf node can be focused.

I need to think about the implication of mounting/unmounting entire pages here. There could be a situation where a page is unmounted, a pause occurs, then the new page mounts. Would the parent of this situation temporarily be a leaf node? That seems fine.
Relevant tests:
tree-updates.test.js => "disabled (leaf node child)"
Also affects focus trap children.

I think the foundational issue here is that there truly is a difference between a leaf node and a group of nodes. Right now, the library fundamentally cannot make this distinction. If the distinction were made (i.e.; two kinds of components), then empty groups could be a thing.
Empty groups really should be a thing. This requirement is actually a pretty legit reason why spatial nav algos could be preferred over the grid-like system in the lib rn.

One idea for a future major release:

three kinds of components: FocusScreen, FocusGroup, FocusNode.
current nav algo involves nested FocusGroup and FocusNode.
new algo introduced: SpatialFocusGroup. Only FocusNodes are permitted as children.

I think this would solve all of the known issues in the lib that I can think of rn, at the expense of a slightly more verbose API.


remove check that BOOTSTRAP and CONFIGURE are executable because need…

… to support program in a PATH (e.g. make) like with BUILD

this is required for the 'gitport' work since it's bootstrap step is 'make configure'


closure_state not correct

Hi! I just pulled together a few dashboard views of the Rivian integration data and started automating locking of my truck when at home. I'm noticing that closure_state doesn't always reflect closure status correctly. See track below for the last 6 hours where clearly doors have been opened but closure_state remains off. (I have also checked the raw entity results in HA to make sure it isn't an issue with my FLUX query or Grafana dashboard.

My child decided to trigger a long term test of my closure notification and auto locking feature on my trucks while out of town on a business trip.
My Rivian shows "open" and "closed" for this enclosure state fine (as pictured below).
Could you please provide a bit more context to your installation environment and entity that you are showing "off" and "on" statuses for.

Hi @tmack8001 ,
The specific sensor is binary_sensor.sulley_closure_state created by the integration. If I look at binary_sensors for specific doors, they seem to change state as expected, eg binary_sensor.sulley_door_front_left, but binary_sensor.sulley_closure_state remains unchanged.
Here is a view of the history panel showing that the front left door has been opened and closed, but sulley_closure_state stays closed/off:

In this time range, sulley_closure_state doesn't change at all, but over other periods I do see it changing, but not always when another opening changes.
I've currently worked around this by creating a group for all the Rivian doors/windows that I want to monitor. this group works as expected (with perhaps the added benefit of not tracking the rear tailgate or tonneau cover.
group:
  sulley_secure_state:
    name: Sulley Secure Status of Doors and Opennings
    entities:
      - binary_sensor.sulley_door_front_left
      - binary_sensor.sulley_door_front_right
      - binary_sensor.sulley_door_rear_left
      - binary_sensor.sulley_door_rear_right
      - binary_sensor.sulley_window_front_left
      - binary_sensor.sulley_window_front_right
      - binary_sensor.sulley_window_rear_left
      - binary_sensor.sulley_window_rear_right
      - binary_sensor.sulley_front_trunk
      - binary_sensor.sulley_gear_tunnel_right
      - binary_sensor.sulley_gear_tunnel_left


❓ Camera size

Question
Hi I have a question. I need fit camera in smaller rectangle with same ratio as full size. Now when I style camera I can get any size but it just cut preview but image is in full size.
What I tried
No response
VisionCamera Version
2.13.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey, sorry I don't understand your question. Could you maybe show screenshots?

Yes sure. So on this screenshot if I make a photo that photo would be exactly like on screenshot. But when I use this library and set for example style with width and height 80% it only cuts the full camera preview and if I make a photo the result would be much bigger (full sized). So I need to set width and height but keep the ratio of preview not only cut it visually. I just don't want to have preview of photo full screen size. I want to make the size like you can see on screenshot but keep ratio of preview.

any news?

any updates on this?

Bump

I've investigated that a bit and looks like the camera is getting weirdly scaled if <Camera> element's ratio differs from actual frame ratio. Here's a workaround that worked for me:
const [dynamicHeight, setDynamicHeight] = useState<number | string>(width);
const frameProcessor = useFrameProcessor((frame) => {
   'worklet';
   runOnJS(setDynamicHeight)('100%');
});

return <Camera
   frameProcessor={frameProcessor}
   style={{ width, height: dynamicHeight }}
   ...
/>

So basically the hack is: start with square camera component (with desired width) and as soon as 1st frame is getting processed adjust the height.

I've investigated that a bit and looks like the camera is getting weirdly scaled if <Camera> element's ratio differs from actual frame ratio. Here's a workaround that worked for me:
const [dynamicHeight, setDynamicHeight] = useState<number | string>(width);
const frameProcessor = useFrameProcessor((frame) => {
   'worklet';
   runOnJS(setDynamicHeight)('100%');
});

return <Camera
   frameProcessor={frameProcessor}
   style={{ width, height: dynamicHeight }}
   ...
/>

So basically the hack is: start with square camera component (with desired width) and as soon as 1st frame is getting processed adjust the height.

Thanks for this great solution! I use your hack in this way:
const [dynamicRatio, setDynamicRatio] = useState(1); const frameProcessor = useFrameProcessor((frame) => {   'worklet';   runOnJS(setDynamicRatio)(frame.width / frame.height); }); ... <Camera   style={{     width: desiredWidth,     height: dynamicRatio * desiredWidth,   }}   frameProcessor={frameProcessor} />

Hello everyone, are there any other solution for that besides using the frame processor? I'm facing this https://github.com/mrousavy/react-native-vision-camera/issues/1281 when trying to apply the frame processor, and the only solution for that was to downgrade the firebase dependency, which it's not a viable option for us here :(

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
Also Preview now supports resizeMode prop


Specification updates and fixes

This issue is made to gather all small fixes, improvements and other TODOs in one place before adding them to next specification revision. It will also be a place for conversation about proposed changes. After enough changes are listed (or a change significant enough to bump specification revision) we can push them all in one PR to keep version in source file synchronized with produced PDFs.
I (or anyone with permissions to edit the issue message) will periodically update the list below to have all the changes in one place. Feel free to put your suggestions in the comment.

[ ] Appendix B ( Intel TXT OS2MLE) has struct slr_table *slrt; - size of pointer should be explicitly specified
[x] Document what SLR_ET_UNUSED can be used for - https://github.com/TrenchBoot/grub/pull/13/files#r1354751740
[x] ~Change value of SLR_ET_UNSPECIFIED -  https://github.com/TrenchBoot/grub/pull/13/files#r1354869835~

That was an error on my part: https://github.com/TrenchBoot/grub/pull/13/files#r1430439851

[x] Values of TXT_VARIABLE_MTRRS_LENGTH and TPM_EVENT_INFO_LENGTH are not specified (both are 32 in implementation).
[x] Not specified whether {slr_policy_entry,slr_uefi_cfg_entry}::evt_info must include trailing \0 or it can be omitted if label fills the whole buffer.
[ ] 2.2 Acronyms doesn't expand SLRT.
[x] Meaning of SLR_POLICY_* and SLR_ET_* aren't explained.  With SLR_ET_SLRT marked as required.
[x] SLR_ET_* aren't always self-describing, they were made with Linux in mind and some names should reflect this - https://github.com/TrenchBoot/grub/pull/14#discussion_r1386836790

[x] Add entry for Multiboot2 modules.

[ ] UEFI Config Entry has "address of value" field which need to be explained/updated.  It's also not specified what kind of address is expected.
[ ] "TPM Extend Operation" section might contain off-by-one error (0..n instead of 0..n-1).
[ ] "TPM Extend Operation" section should explain that | denotes concatenation instead of bitwise OR.
[x] Description of SLR_ET_SLRT should reference "Appendix A".
[ ] Entry_n = PCR_n | EntityType_n | EventInfo_n in "Measuring the Policy" should use i for index.
[ ] Describe the format (entry point, unused cmdline) and location of MLE header (kernel_info for Linux, whatever we'll choose for Multiboot2).
[ ] mtrr_vcnt array in description of mtrr_vcnt should say mtrr_pair array instead.

A bit over half of currently listed issues was addressed in https://github.com/TrenchBoot/documentation/pull/25. The rest is planned to land in the specification together with changes specific to AMD processors.

@SergiiDmytruk I think there is no off-by-one error in "TPM Extend Operation". E_0 describes extend operation for Obj_0 and E_n - for Obj_n, not Obj_(n-1). Can we remove that from the list above?
I'm also not sure about using i for index in "Measuring the Policy". Is this just to differentiate those from names used in "TPM Extend Operation"?

I think there is no off-by-one error in "TPM Extend Operation". E_0 describes extend operation for Obj_0 and E_n - for Obj_n, not Obj_(n-1). Can we remove that from the list above?

I meant that the way it's written there are (n + 1) objects in the range [0;n] (both ends included), instead of n of them ([0;n) or [1; n]).  Same in "Measuring the policy".

I'm also not sure about using i for index in "Measuring the Policy". Is this just to differentiate those from names used in "TPM Extend Operation"?

If there is only Entry_n = ... and Entry_0, ..., Entry_n, it looks like definitions of Entry_0 through Entry_{n-1} are missing.  i usually suggests iteration, n boundary.

If there is only Entry_n = ... and Entry_0, ..., Entry_n, it looks like definitions of Entry_0 through Entry_{n-1} are missing.

But for the policy it isn't defined through Entry_{n-1}

But for the policy it isn't defined through Entry_{n-1}

How come?  Isn't M_policy a result of extending 0 and Entry_0, then extending result with Entry_1, etc. up to the last entry?

Isn't M_policy a result of extending 0 and Entry_0, then extending result with Entry_1, etc. up to the last entry?

Hmm, I understood it as concatenation of all entries (subset of their fields), but there is a different symbol for concatenation, so maybe you're right. @dpsmith @rossphilipson what are your opinions on this?

Hmm, I understood it as concatenation of all entries (subset of their fields), but there is a different symbol for concatenation, so maybe you're right.

The reason for my interpretation is definition of E() in 5.1 which is recursive when applied to an array of objects.


Added unit tests to db/tests/test_datastore

This brings coverage upto 95%

Build fails during 'pip install'. Do I need to action this?

It failed because brian deleted txrudp 0.5.0 from pypi by accident. If you bump it to 0.5.1 it should run ok.

On a side note, I'm currently adding some more stuff to this file in the PR I'm working on. You might want to rebase after I merge that.
It's a small change to Messages and added and new Cases class.

So, to clarify. I should wait till you merge then rebase and re-submit the pull request?


[SourceKit] Don’t set DisableModulesValidateSystemDependencies to true

Explanation: It appears that https://github.com/apple/llvm-project/commit/a6ebd3083dbf8aadae58f6f2a2f1071976649d56 changed the behavior of -fno-modules-validate-system-headers (aka. DisableModulesValidateSystemDependencies) in conjunction with -fmodules-validate-once-per-build-session: Before that change, -fno-modules-validate-system-headers needed to be passed for -fmodules-validate-once-per-build-session to have any effect (we were always validating system dependencies if -fno-modules-validate-once-per-build-session was not set). After the change, -fno-modules-validate-once-per-build-session causes system dependencies to never be validated, independent of the build session timestamp.
This change should have no effect on Xcode because it adds -fmodules-validate-system-headers to the compiler arguments for Swift files, which overrides SearchPathOpts.DisableModulesValidateSystemDependencies = true;
Scope: SourceKit for system modules that are modified
Risk: Low
Testing: Added test case
Issue: rdar://129046909
Reviewer:   @bnbarham on https://github.com/apple/swift/pull/74063

@swift-ci Please test


How to check if database connection is expired  in python

Hello Community,
I am connecting python with Vertica but after some time connection is getting expired, I really want that when the connection gets expired my status gets changed In mysql we have connection.is_connected() method which is true if the connection is still maintained but if it expires it gives false , Do we have a similar function in Vertica
Thanks

@I-akshay Yes, vertica-python have similar functions: connection.opened() and connection.closed() return Boolean values.
Can you tell me what's the current behavior when your connection is getting expired?

HI @sitingren
Thanks for your response, really appreciate, but it is not working
For example :
conn_info = {'host': '<IP_ADDRESS>1', 'port': 5433, 'database': 'personaldwh','user': 'username', 'password': 'username123'}
connection = vertica_python.connect(**conn_info)
cur = connection.cursor()
Now lets says i wait for 45 mins now,
cur.execute("Select 1")
This statement is throwing isssue (Connection Closed by vertica)
but when I am doing
if connection.opened():
print("Yes")
It is still showing Yes
Can you tell me what's the current behavior when your connection is getting expired?
Basically i am calling a loop from where i am running a shell command and wait for 100 mins by the time my connection is getting closed by vertica
I really appreciate if you tell me how to handle this problem

This connection.opened() function generally cannot be called to determine whether a connection to a database is valid or invalid, it does passive checking. Unfortunately, there is no function to actively determine if a connection is expired.
You can determine that a connection is expired by catching exceptions that might be thrown when an operation is attempted. select 1 is a good dummy statement to execute. So you are doing the right thing.


How to set Geolocation from the Kameleo API?

What would be the proper code syntax form to set the Geolocation for a profile from the Kameleo API?
Also, could your provide some example code?

Here is an example that you can use to set the Timezone for a profile through the API:
const createProfileRequest = BuilderForCreateProfile
    .forBaseProfile(baseProfileId)
    .setGeolocation({
        value: 'manual',
        extra: {
            latitude: 59.43984,
            longitude: 24.75815
        }
    })
    .build();
const profile = await client.createProfile({ body: createProfileRequest });

These answers are provided from the Kameleo Set Geolocation from API article.


Custom sensor config: Missing fields

Several people noticed this or had issues with custom configs.
During registration when using a custom config no warnings are shown when fields are missing or not filled, just an error upon submitting registration.

Added more warnings


OpenAI-compatible api?

It would be extremely convenient to have such api, to use a lot of existing tools.

Chatgpt-connect is limited in terms of functionalities since it does only relies of the Chatgpt webapp. For now, chatgpt-connect is more used for question-answer purpose and all the other parameters like the temperature, max-token and the others keep their default values by the chatgpt-webapp.


influxdb tries to listen on wrong address

Hello,
I am trying to run heapster on a newly created baremetal server running kubernetes 1.9.2 as described here https://github.com/kubernetes/heapster/blob/master/docs/influxdb.md
However, InfluxDB fails to start because it is trying to use a wrong address
kubectl logs monitoring-influxdb-6c4b84d695-664cl -n kube-system
[I] 2018-01-25T20:22:45Z InfluxDB starting, version unknown, branch unknown, commit unknown
[I] 2018-01-25T20:22:45Z Go version go1.8.3, GOMAXPROCS set to 4
[I] 2018-01-25T20:22:45Z Using configuration at: /etc/config.toml

 8888888           .d888<PHONE_NUMBER>b.  888888b.
   888            d88P"  888                   888  "Y88b 888  "88b
   888            888    888                   888    888 888  .88P
   888   88888b.  888888 888 888  888 888  888<PHONE_NUMBER>888K.
   888   888 "88b 888    888 888  888  Y8bd8P' 888    888 888  "Y88b
   888   888  888 888    888 888  888   X88K   888    888 888    888
   888   888  888 888    888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
 8888888 888  888 888    888  "Y88888<PHONE_NUMBER>888P"  8888888P"

run: open server: listen: listen tcp <IP_ADDRESS>:8088: bind: cannot assign requested address

I have no idea where the range 10.132 comes from...it is not the on the nodeip range or pod network range
If I edit the monitoring-influxdb deployment to just run influxd, instead of ["influxd", "--config", "/etc/config.toml"] heapster starts correclty

Oof.  Yeah, localhost should resolve to the loopback address.  Does your DNS server not respond with NXDOMAIN for localhost?  That seems strange...
Anyway, I'm closing this be.  Feel free to re-open if you disagree.


Gmail print attachment opens a new _blank window

Describe the bug
Gmail's built-in print attachment button does not work.
To Reproduce
Steps to reproduce the behavior:

Go to Gmail
Click on an email attachment like a PDF or image
In the attachment preview, click Gmail's print icon
A window opens with the title _blank and does not print

Expected behaviour
System print dialogue should be displayed.
Screenshots

Desktop

OS: macOS Mojave 10.14.3
Version: 5.0.0-beta.22 (5.0.0-beta.22.1059)

I second this one, bumped into it many times, have to open gmail in browser to do that, which is somewhat annoying :(

Pretty serious issue with almost all Google Services on Franz 5.0.0. Any update? :)

@adlk Please, another beta is out - any info about this one? :)

Agreed, really annoying for such a standard use case.

Any news regarding this? If anyone could point me in the right direction my company could try to add this feature in a pull request.