Feedback button on the Results page

[ ] To investigate the design options of 'Give us feedback'
[ ] To check the design of the Beta Feedback Report form

To check Beta Feedback Report form.
Does it include everything? @richardofsussex @Vino-S
It seems it does, I think it could be adjusted a little bit to make it more consistent with the FreeBMD2 design.

To discuss in the next Scrum:

[ ] design options of 'Give us feedback'. We decided to consider visual design options to attract users rather then using long text descriptions (example in the screenshot). There is not enough extra space for text descriptions on the results page.

[ ] design and structure of the Feedback Report form (on Beta). It would be better to make it consistent with the design style of FreeBMD2.

Postpone until phase 5.


Extend vue.js small variant filter form with remaining tabs

Is your feature request related to a problem? Please describe.
The current vue.js implementation of the variant filter form is only done for frequency and genotype filter, all other settings are default. The data model exists, only the other forms need to be put into vue components and data-binded to the data model.
Describe the solution you'd like
All the form should be made available, including (quick) presets.
Describe alternatives you've considered
None.

Resolution Proposal
Simply create one component per tab, more if necessary.
Affected Components
VarFish Server
Affected Modules/Files
variants/vueapp
Required Architectural Changes
None
Required Database Changes
None
Backport Possible?
No
Resolution Sketch

[ ] Prioritization
[ ] Variants & Effects
[ ] Quality
[ ] Clinvar, HGMD & dbSNP
[ ] Gene Lists & Regions
[ ] Flags & Comments
[ ] Configure Downloads
[ ] Miscellaneous
[ ] Filter Import / Export

Note: not porting over features from #739.


Fix memory leak

Without this I got up to 12gb of memory used when transcribing a 2hr audio file with base.en.

Nice find! Testing this out


Fillafter animation

Hi, i'm using your library and it's great , but i was wondering if there was a possibility to animate color filling

@diabloo Can you describe in more details what do you mean?

i have a colored svg , i use :
pathView.useNaturalColors();
pathView.setFillAfter(true)
i want to know if it's possible to fill with an animation like in this library but i want to achive this with the natural colors.
ps :sorry for my english

No worries , your English is perfect.
It is not possible unfortunately.
This effect is beautiful but will change the course of this library.
But I think you can easily use the library that you pointed. Seems legit 👍


Optimize Lightning-Qubit's probs(wires) using bitshift implementation

Before submitting
Please complete the following checklist when submitting a PR:

[x] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[x] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[x] Ensure that the test suite passes, by running make test.

[x] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[x] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
probs is central in circuit simulation measurements.
Description of the Change:
Implement probs(wires) using bitshift implementation akin to the gate kernels in Lightning-Qubit. This does away with the NDpermuter dependency, which is removed.
Benefits:
Enable on-the-fly diagonalization.
Faster execution.
The following benchmarks are performed on ISAIC's AMD EPYC-Milan Processor using a single core/thread. The times are obtained averaging the computation of probs(target) 5 times, where target includes a single wire. The speed-ups are uniform across all possible targets, and hence we show target={0} and the average speed-up across all targets below.

The situation is more ambiguous when comparing w.r.t. the number of targets. The following shows timings for targets = {0..ntargets-1} and the conclusions are:

The generic implementation is only faster for 1 target;
The templated (specialized) implementation is faster for 1-4 targets, which is a range where many probs(Hermitian) would be requested (since at some point Hermitian becomes too large to represent as a matrix).

Possible Drawbacks:
Related GitHub Issues:
[sc-65198]

I think it looks good for now. We could maybe come back to this in the future and try to remove the usage of macros.

100% agree, I wish the compiler would be smarter optimizing the generic implementation. Or maybe there is a smarter way to write it to help the compiler ...


See more content link on home page wraps too early on Chrome Android

Describe the bug
On Chrome on Android 12, the "Other news items" and "See more projects" links wrap onto two lines even though there is sufficient space to display the link on a single line.
To reproduce
Steps to reproduce the behavior:

On Android 12 using Chrome, go to the Index page
Scroll down to the "Other news items" and "See more projects" links
Notice how the links appear on two lines when there's enough space to not have to wrap.

Expected behavior
The link should appear on a single line if there's enough space.
Screenshots

Technical details
Smartphone / tablet

Device: Google Pixel 3
OS: Android 12
Browser Chrome

Depends on #232

@jhung  Still open ?

I will fix it


Net 5 support and serializers exported to own projects

new: net 5 support
new: api refactored to support nullables
new: all serializers exported to specific projects
new: system text json serializer added as default
new: protobuf serializer now uses recyclable memory streams
closes #25 #26

Any feedback on this?

Looking!

There's a lot to unpack there! I think most changes are simply good. I have more... semantic doubts about nullables. What is the practical use case for storing nulls in a cache?

dupe of #30


Sentence-casing at import

Better BibTeX FAQ explains that titles are automatically converted into sentence-case when importing items. Then, when exporting to Bib(La)TeX, some characters are protected via braces. I have two questions about this:

Is automatic sentence-casing currently supposed to be working without requiring me to do anything? Because I just can't get it to work even with a clean new profile in Zotero to prevent potential clashes with other settings. I set the corresponding setting to convert unconditionally (even if the title is guessed to already be in sentence-case), yet whenever I try to import an item from Firefox via the Zotero Connector the title is copied as is without getting sentence-cased.
For items with sentence-cased titles, export puts braces as intended. However, it does this not only for the title field but also for things like booktitle, publisher, series, etc. Is this intended? If I were to write a Bib(La)TeX entry by hand, I would not put braces in, say, a conference proceedings title since this does not get sentence-cased according to APA. In the end, should every single field be in sentence-case in Zotero for the braces to be inserted properly (as I would do by hand)?

If these are bugs, I can make a bug report in the proper format but I am not sure whether I am experiencing the intended behavior or not.
Thank you.

Better BibTeX FAQ explains that titles are automatically converted into sentence-case when importing items.

When importing with BBT, yes.

1. Is automatic sentence-casing currently supposed to be working without requiring me to do anything ... yet whenever I try to import an item from Firefox via the Zotero Connector the title is copied as is without getting sentence-cased.

This is the key bit. When you are importing using the connector, BBT only gets involved when the page you're scraping offers bibtex. If it offers anything else (which is usually the case), BBT doesn't get called by Zotero.
The reason BBT sentence-cases titles is because bibtex says that titles should be in Title Case, and Zotero expects sentence-case. There is no such standard for all other non-bibtex data that gets collected by the connector, so the assumption by most translators (even the Zotero bibtex translators) is that the scraped data is already sentence-cased.

2. For items with sentence-cased titles, export puts braces as intended. However, it does this not only for the title field but also for things like booktitle, publisher, series, etc. Is this intended?

Yes, but for different reasons:

booktitle and series are title-type fields, and are subject to bib(la)tex case meddling for non-english items
publisher is a literal-list field; since Zotero has only a single field for publisher, I treat the Zotero publisher field as if it is a list-of-one with a single literal name (and the last part is why it gets the braces). If I would not do that, Rowman and Littlefield would be treated as two publishing houses involved with that reference.

If I were to write a Bib(La)TeX entry by hand, I would not put braces in, say, a conference proceedings title since this does not get sentence-cased according to APA.

If the title is in sentence case in Zotero, you'll get no braces, so that should work out fine. If you have capitals in Zotero, those would be brace protected, but you'd want that regardless of whether the style sentence-cases or not.

In the end, should every single field be in sentence-case in Zotero for the braces to be inserted properly (as I would do by hand)?

Yes. Zotero expects everything to be in sentence case, and BBT works from that assumption. You can turn of brace-protection if you want, but it then becomes style-dependent whether bibliographies rendered by Zotero itself or by bib(la) tex come out the same.
You can right-click a field in Zotero and Zotero will sentence-case for you, but this transformation is imperfect, you always need to check the results.

Thank you very much for the detailed reply! You cleared up all my confusion.

My pleasure


Typo in README

I think there is a typo in README which mentions Ubuntu 16.06. But, I think it meant to say Ubuntu 16.04 actually.

Fixed the typo and removed install instructions on the README in favor of having them only on the docs site here:
http://caffe2.ai/docs/getting-started.html?platform=ubuntu&configuration=compile
Thanks!


Relax TMF destination requirements

Marked as P1 since it would impact all certification scenarios with ML-EID as destination due to the strict rules in #1653

The above is a work around, but not a real fix (it still violates section 10.6.2 of the Thread Spec)
After a message M triggered address resolution because the destination address was an ML-EID, M has to be changed in two spots before sending it:

Change the MAC80154 address to short address obtained from the address resolution (as it is currently done)
Replace the IPv6 address (ML-EID) by the RLOC.
With the above changes the fix in #1653, is valid.

One should also consider not using the ML-EID as source address, because this triggers Address resolution in the receiver before it can reply to the originator's request

@thcu-gp , The aim of address resolution is to find mesh destination for routing in thread network. And taking the nexthop to the mesh destination as the mac dest address.
The IPv6 destination address in IP header should not be changed during delivery.
I agree that CoAP source address should avoid to take ML-EID as source address, that's what #1732 does.
Thanks.

@jwhui , not sure if the rules here are still too strict. We don't know if the other stack implementations would also to explicitly specify RLOC as source address for TMF when possible.

An application should only use ML-EID addresses (RLOCs are for Thread internal use).
So if a (Thread) CoAP message is sent by an application it will have an ML-EID source address.
Since this is not allowed by Thread (section 10.6.2), there is an impasse. Either

block those (as done in #1653), but this breaks functionality
Replace ML-EID by RLOC

@librasungirl I disagree, the aim of the address resolution if to find an RLOC (This is an IP feature), having received an RLOC, allows you to use a short address on the MAC layer (call this a bonus). Said differently, since we cannot route (IP-layer) ML-EIDs, we have to switch to RLOCs. The fact that communication between routers uses 6lowpan meshing is irrelevant.

@thcu-gp
We may add interfaces to dispatch the CoAP message to Application process if it shares the Thread Management port(:MM) with TMF in core in the future (as in 10.6.3).
But currently OT core only processes TMF CoAP message which meets the stricter rules in this PR (also meet with the rules in 10.6.2), and simply drops CoAP messages which doesn't meet the rules.
Yes, we cannot route ML-EIDs. But we are not 'switching to RLOCs' via replacing ML-EID with RLOC in IP layer. Instead,  6LowPAN Mesh Header would be added for routing in mesh if the destination is not the direct neighbor. (<IP_ADDRESS>).
Lower layer should not modify the IP header,  but only forward the IP packet (if routable) or drop it (if not routable)
@jwhui ,  just as @thcu-gp points out, if the CoAP message has ML-EID as both source and dest address, it doesn't meet with TMF addressing rules in 10.6.2. Then it should be all right for OT stack to not process such CoAP message.

The changes in #1653 are compliant with 10.6.2, the changes in #1733 would allow ML-EIDs
Currently (on our local setup) the ThreadTestHarness test 9.2.4 fails because ML-EIDs are used as the source and destination of a MGMT_GET_ACTIVE.req. The problem lies not in filter, but in the fact that ML-EIDs are used in the first place.
How should an application (only aware of ML-EIDs) use the following OpenThread API call?
ThreadError otDatasetSendMgmtActiveGet(uint8_t aTlvTypesLength, uint8_t *aTlvTypes, otIp6Address *aAddress);

If it uses an ML-EID for aAddress, it would never retrieve the dataset, because the CoAP messages would be dropped.

The changes in #1653 are more strict than what Thread 1.1 Section 10.6.2 specifies.  The changes in #1653 requires the IPv6 source address to be an RLOC or ALOC.  However, Thread 1.1 Section 10.6.2 does not require the IPv6 source address to be RLOC/ALOC if the destination address is an RLOC/ALOC or link-local address.

A TMF CoAP message sent to the Thread Management UDP port (:MM) MUST comply with at least one of these addressing rules:

The IPv6 source address is an RLOC or ALOC.
The IPv6 destination address is an RLOC or ALOC. The IPv6 destination address is a Link-Local address.
Some of the individual TMF Message definitions will also impose specific, stricter rules for addressing.

Note the "at least one of these" wording above.
For background, the rules in Section 10.6.2 were defined with the goal of allowing an application protocol to utilize the same :MM port.  This implies that any "application" wishing to send/receive TMF messages on the :MM port must be aware of RLOC/ALOC addresses.  See SPEC-498 for more discussion around this.
We can argue whether or not Section 10.6.2 should be made more strict, but this needs to happen within the Thread Group.

Thanks @thcu-gp for pointing out the test issues.
The issue is because that when the dst is ML-EID, according to the select source rules, either RLOC or ML-EID would be selected as source. And OT core would drop the received CoAP message with ML-EID as source.
I will submit a separate PR to explicitly specify RLOC as the source address for CoAP client messages in core to fix the issue.
Additionally, we may need to confirm with other stack vendors to ensure they don't take ML-EID as both source and dest for certification tests. Let's discuss this within ThreadGroup. Thanks.

#1743 is submitted to specify RLOC as source for CoAP client messages in core

Rebase to master to solve the conflict

I missed the 'at least one' @jwhui is correct
An application using the OpenThread API, doesn't need to be aware of RLOCs, as long as it can count on the OpenThread stack to use an RLOC as a source addresses in TMF CoAP messages triggered by using the API

Roll back to the rules in specification.


Prefix Entity-Ids with "Tesla" or VIN

Is your feature request related to a problem? Please describe.
Most entity-ids have prefixes to identify them easily, but the entities from the Tesla integration don't.
When I want to use the battery percentage in an automation, the Entity-Id for my Pixel Watch is sensor.google_pixel_watch_battery_level while for my Tesla it's sensor.battery
For example, this is how it looks when I have the battery percentage of my Tesla and my Pixel Watch in Grafana:

This makes the Tesla entities hard to identify.
Describe the solution you'd like
Prefix the entities, for example tesla_battery or <VIN>_battery
Describe alternatives you've considered
Live with it
Additional context

I'm sorry but I searched through all issues and couldn't find this

@alandtse I'm new to python but I decided to take a look into the code. This part of code in custom_components\tesla_custom\base.py looks like it is responsible for the name and it looks like it works as expected

I think what may be happening is the display_name is the empty string now. This may not have been the case before so more people are seeing a blank. You can tell by enabling debug logging and seeing the response to teslajsonpy.

I had the same problem but now fixed it. I wake up my car via app. Then removed the Integration and re-added it. Now all entites have a prefix.


TS errors from node_modules

Just got TS errors from swr in node_moduels when I run our yarn tsc script

But I have skipLibCheck to true in tsconfig.json, why is node_modules still getting checked?
swr version: 1.2.1
yarn version: 1.22.17
typescript version: 3.7.3

It's cause by TypeScript, upgrading it may be the only solution 😅


Can I use this library for face recognition?

Thanks to the author for developing a great plugin.
I'm planning to make a face recognition feature with react-native-vision-camera's realtime frame processing.
After looking through the documentation to find this plugin developed by the author, I looked through the react-native-fast-opencv documentation but did not find an api for face recognition.
So how would I import a trained file like haarcascade_frontalface_default for face recognition via react-native-fast-opencv?
Thanks!

Hi @shuo-hiwintech, unfortunately face detection is currently not supported by the library. In such cases, it is possible to write your own code in C++ using such functionality.
Instructions are available here: https://lukaszkurantdev.github.io/react-native-fast-opencv/customized


[App] Fixing Sigterm Handler causing thread lock which caused KeyboardInterrupt to hang

What does this PR do?
Multiprocessing runtime was configured to call terminate on the work process twice
        except KeyboardInterrupt:
            self.terminate()
            raise
        finally:
            self.terminate()

The second terminate would cancel the first sigterm handler call but cancellation of a handler wouldn't release the thread lock causing the second sigterm handler to be on a deadlock
Note: We still have issues with uvloop overriding the signal handlers. But that's a different issue

Fixes #<issue_number>
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @borda

Late to the party, but great catch @hhsecond!

Late to the party, but great catch @hhsecond!


⚠ ClamAV has degraded performance

In afc3ee3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 104 ms

Resolved: ClamAV performance has improved in 11e06f0 after 16 minutes.


Server Side Pagination

Describe the bug
Control panel eager loads every single user account, I tested with 40,000 users and it renders the Role package CRUD unusable.
To Reproduce

Add 10s of thousands of user accounts.
Visit the UI

Expected behavior
To load designated number of page items from the backend not everything.

Make a or for a fix.

Make a or for a fix.


Security problem for server-side usage scenario.

This issue was originally filed by<EMAIL_ADDRESS>
It seems like there is security problem when both scenarios "client/server side" used together.
There is web/packages link that points to the ../packages/ directory. However the ../packages/ directory can store both client and server side libraries. This means that server-side libraries can be accessed as client libraries through browser. It is security flaw because server side libraries can be downloaded if user will know path, for example I can download server-side library by entering the following URI in the browser: http://<IP_ADDRESS>:3030/I:/project/test/web/packages/rikulo_commons/util.dart. The provided as example URI can be actually any URI to any file.
What version of the product are you using? On what operating system?
Dart VM version: 0.5.3 ...(Wed May 01...), Windows 7

This issue has been moved to dart-lang/pub#542.


[C++][Parquet] Add support for arrow::ArrayStatistics: boolean

Describe the enhancement requested
Subissue of #43549
For types of https://github.com/apache/arrow/blob/d88dd19ea83aee37a4da69bdbc688f5e342fb455/cpp/src/parquet/arrow/reader_internal.cc#L835-L836

Boolean

Component(s)
C++, Parquet

Issue resolved by pull request 44009
https://github.com/apache/arrow/pull/44009


Keypad Middle Key (non numlocked numberic centre key 5) producing "unknown"

I am trying to create a BRIEF (Basic Reconfiurable Interactive Editting Facility) Keymap I would like the middle cursor (numeric 5) keypad key to produce a code I can use in keymap, but instead its producing "unknown".
In BRIEF the non numlocked numberic centre key 5, centres the window on the current line.
So an appropriate key name code would be ideal, maybe just "Centre", or "CursorCentre" ? after KeyCode.PageDown, 'cursorPageDown' keycode.

I am fetting KeyCode 12 being converted to KeyCode 0
 [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Numpad5, keyCode: 12, key: Clear
[2022-02-16 23:22:50.079] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Numpad5, keyCode: 0 ('unknown')
[2022-02-16 23:22:50.079] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.

ideally the ScanCode is assigned correctly and a new KeyCode.Clear is created and assigned.

The keyboard code is a bit crazy and could really do with recoding for efficiency and simplification. All the obvious changes to the  keymap result in 'unknown' still. @alexdima I think it really needs someone who knows this area well to solve this and maybe rewrite the keyboard code for efficicncies sake.

I pulled the pull request https://github.com/microsoft/vscode/pull/143324 as it does not actually work yet.
The patch/pull request is not actually resulting in a key binding to it. I am getting 'No keybinding entries' :-
[2022-02-18 05:19:28.451] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Numpad5, keyCode: 12, key: Clear
[2022-02-18 05:19:28.452] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Numpad5, keyCode: 105 ('Clear')
[2022-02-18 05:19:28.459] [renderer1] [info] [KeybindingService]: | Resolving Clear
[2022-02-18 05:19:28.459] [renderer1] [info] [KeybindingService]: \ No keybinding entries.

This is hapening despite having the following in keybindings.json :-
// Place your key bindings in this file to override the defaults
[
	{
		"key": "Clear",
		"command": "center-editor-window.center",
		"when": "editorTextFocus"
	}
]

@alexdima If you could still look into this please.

[2022-02-18 10:08:24.247] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Numpad5, keyCode: 12, key: Clear
[2022-02-18 10:08:24.248] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Numpad5, keyCode: 126 ('Clear')
[2022-02-18 10:08:24.256] [renderer1] [info] [KeybindingService]: | Resolving Clear
[2022-02-18 10:08:24.257] [renderer1] [info] [KeybindingService]: \ No keybinding entries.

No change I think the key code is being generated from my patch :-
https://github.com/AaronNGray/vscode/blob/main/src/vs/base/common/keyCodes.ts#L572

Using the main branch, the following worked for me:
{ "key": "clear", "command": "actions.find" }

Still getting "No keybinding entries".
[2022-02-18 10:21:01.046] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: Numpad5, keyCode: 12, key: Clear
[2022-02-18 10:21:01.051] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Numpad5, keyCode: 126 ('Clear')
[2022-02-18 10:21:01.051] [renderer1] [info] [KeybindingService]: | Resolving Clear
[2022-02-18 10:21:01.052] [renderer1] [info] [KeybindingService]: \ No keybinding entries.

This is from main branch

I tried moving it to alt+F11 and thats not working either.

Not sure what might be causing the difference we are seeing. Could please try to kill and restart yarn watch (the compilation task)? Changing const enums (such as in this case with KeyCode.MAX_VALUE) does not propagate correctly through our gulp-tsb builder and requires a restart to regenerate the JS files with inlined values.

Yes I noticed that. I am just installing from scratch.

I have another keyboard related issue if I may pass it by you, I am trying to do a BRIEF Editor keymapping. the funny thing about brief is it has HOME to goto the beginning of the line, HOME HOME to the top of the current window, then HOME HOME HOME to goto the top of the document. END behaves simularly, end of line, bottom of window, and end of document.
I can see I can get HOME HOME, but not HOME HOME HOME. Shall I do a separate Feature Request ?

Yes, we already have a feature request for longer chords -- https://github.com/microsoft/vscode/issues/6966.
But I don't think chords would be the best way to tackle this because with chords you cannot dispatch both variants home and home home. One of them will win depending on their order and if it is the chord (home home), it will never fall back to home (see also discussion in https://github.com/microsoft/vscode/issues/140226).
In the core editor, we also have something similar with home, where first pressing home moves the cursor to the position before the first non whitespace character on the line, then pressing home again takes it to the first character on the line. Similarly, home on wrapped lines first moves the cursor to the start of the wrapped line, then a subsequent home moves the cursor to the start of the logical line. This is not implemented with chords, but rather by looking at the current state. If home is pressed and the cursor is in the middle of a line, it moves to the first non whitespace character. If home is pressed and the cursor is already at the first non whitespace character, it moves to the first character.

The first HOME moves to the beginning of the line, follow that by a second HOME and it goes to the top of the window, follow that by a third HOME and it will got to the top of the document. SO what your saying is the HOME HOME HOME binding will override the others and they will not be done in sequence as they are matched ?

So it has to be done with a new conditional function. Is there any command history at all that could be examined, for previous HOME commands ?

Given:
[
    { "key": "home", "command": "cursorBeginningOfLine" },
    { "key": "home home", "command": "cursorBeginningOfWindow" },
]

When you press home the first time, the keybinding system will enter chord mode and will print "Home pressed. Waiting for second part of chord...". If home is pressed again within 5 seconds, then cursorBeginningOfWindow is invoked. If nothing is pressed within 5 seconds, nothing happens.

there any command history at all that could be examined, for previous HOME commands ?

My suggestion was to look at the cursor state and determine based on it what to do. If the cursor is at the start of the line and the user presses home once, it is very likely they wanted to move to the top of the window. However, if you wish to build up a history, you can do so, but it would need to be something done in your extension.

Thank you for your help !

To verify, you must use a keyboard with numpad keys and turn off numlock, and press the numpad 5. It will be identified as Clear.


Cleanup lazybeforeunveil example to use jQuery

In addition to that, fix the ajax loading example

How is giving an example using jQuery instead of simple native DOM is an helpful PR?
I love jQuery but still, you want as much de-coupling between this script and jQuery


fix(forge): add coverage to test setUp

Motivation
Improve forge coverage reporting of functions called during test setUp. This allows initializer functions, but not ctors, called during setUp (ex: https://github.com/foundry-rs/foundry/issues/4553) to be covered.
Solution
The TestSetup is extended to include coverage info. The setUp coverage is then merged with HitMaps generated by test runners.
Consider the coverage reporting of the CounterTest:test_Increment test generated by forge init. Prior to this change, we see that Counter.setNumber isn't covered because it's only called during setUp:

With this patch, we get full test coverage in Counter.sol:

@Evalir Thanks for the review. PR's been rebased and I've added a visual description of this change.


Exception due to unicode on testnet

On testnet network, cardano-db-sync at tags/5.0.0 in extended mode, is throwing exceptions at block 1816809 due to unicode parsing/handling issues.  It cannot sync past this block.
[db-sync-node:Info:234667] [2020-09-19 14:23:20.41 UTC] Starting chainSyncClient
[db-sync-node:Info:234667] [2020-09-19 14:23:20.48 UTC] Cardano.Db tip is at slot 6061839, block 1816809
[db-sync-node:Info:234672] [2020-09-19 14:23:20.48 UTC] Running DB thread
[db-sync-node:Info:234672] [2020-09-19 14:23:20.65 UTC] Rolling back to slot 6061839, hash 98414d12d1d1f05210dea6ce4082e1bcbbcfdf56343fd1cb44a8778c4c9ea57a
[db-sync-node:Info:234672] [2020-09-19 14:23:20.66 UTC] Deleting blocks numbered: []
[db-sync-node:Error:234672] [2020-09-19 14:23:21.03 UTC] runDBThread: DbInsertException "TxMetadata" (SqlError {sqlState = "22P05", sqlExecStatus = FatalError, sqlErrorMsg = "unsupported Unicode escape sequence", sqlErrorDetail = "\\u0000 cannot be converted to text.", sqlErrorHint = ""})
[db-sync-node:Error:234667] [2020-09-19 14:23:21.05 UTC] ChainSyncWithBlocksPtcl: DbInsertException "TxMetadata" (SqlError {sqlState = "22P05", sqlExecStatus = FatalError, sqlErrorMsg = "unsupported Unicode escape sequence", sqlErrorDetail = "\\u0000 cannot be converted to text.", sqlErrorHint = ""})
[db-sync-node.Subscription:Error:234663] [2020-09-19 14:23:21.05 UTC] [String "Application Exception: LocalAddress {getFilePath = \"/run/cardano-node/node.socket\"} DbInsertException \"TxMetadata\" (SqlError {sqlState = \"22P05\", sqlExecStatus = FatalError, sqlErrorMsg = \"unsupported Unicode escape sequence\", sqlErrorDetail = \"\\\\u0000 cannot be converted to text.\", sqlErrorHint = \"\"})",String "SubscriptionTrace"]
[db-sync-node.ErrorPolicy:Error:4] [2020-09-19 14:23:21.05 UTC] [String "ErrorPolicyUnhandledApplicationException (DbInsertException \"TxMetadata\" (SqlError {sqlState = \"22P05\", sqlExecStatus = FatalError, sqlErrorMsg = \"unsupported Unicode escape sequence\", sqlErrorDetail = \"\\\\u0000 cannot be converted to text.\", sqlErrorHint = \"\"}))",String "ErrorPolicyTrace",String "LocalAddress {getFilePath = \"/run/cardano-node/node.socket\"}"]

@johnalotoski How do I connect to that testnet?

This is HUGE pain in the neck.
The tx metedata that is being inserted is
(1,S "\NUL\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX\ETX")

which is being encoded as JSON:
"\u0000\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003"

which of course is not valid UTF8 and hence the database rejects it.
Even worse, the above is encoded as UTF8 by the Haskell Text library as shown, but PostgreSQL then rejects it.

The string in question is decoded to UTF8 by the Haskell Text library and then passed to Postgres which throws an SqlError exception. I have tried catching this exception but catching the exception does not seem to work.
I can catch and log the exception:
[db-sync-node:Warning:37] [2020-09-21 00:26:18.77 UTC] insertTxMetadata: Failed to insert (1,S "\NUL...\ETX")
SqlError {sqlState = "22P05", sqlExecStatus = FatalError, sqlErrorMsg
 = "unsupported Unicode escape sequence", sqlErrorDetail = "\\u0000 cannot be converted to text.", sqlErrorHint = ""}

but then there is a second excpetion:
[db-sync-node:Error:37] [2020-09-21 00:26:18.77 UTC] runDBThread: SqlError {sqlState = "25P02", sqlExecStatus = FatalError, sqlErrorMsg = "current transaction is aborted, commands ignored until end of transaction
 block", sqlErrorDetail = "", sqlErrorHint = ""}

This suggests that I need to more fully validate the JSON before insertion.

We can store invalid UTF8 in PostgreSQL, but only as bytea data not as the jsonb and if we go for the former Postgres's JSON query support will not be avaiable.

I have tried a manual UTF8 decode:
decodeUtf8IO :: ByteString -> IO (Either Text.UnicodeException Text)
decodeUtf8IO = try . evaluate . Text.decodeUtf8With Text.strictDecode

and that too has the same problem.

From: https://stackoverflow.com/questions/31671634/handling-unicode-sequences-in-postgresql

A null byte isn't legal in a PostgreSQL string. Neither is a zero code point.

Currently think is is due to the way Haskell/Persistent serializes this to send to postgres. Currently trying to validate this theory.

:facepalm: Aeson.encode already escapes the NUL char to \u0000 which Persistent then rejects.
Coming up with a neat fix for this is not going to be easy.

I was looking into this and it seems these properties hold:

"\u0000\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003\u0003" is pretty valid as UTF-8, since UTF-8 does allow \u0000 to be represented directly.
\u0000 is not allowed for jsonb because it cannot be converted to text.

The only temporary solution to encode it to a JSON, and then to Text and then detect the bad character sequence and reject the JSON object it if contains the bad sequence.

Couldn't you store two columns? the bytea, and the JSON when it doesn't contain the non-text character, so that anyone is free to use whatever they need.

@erikd The \u0000 restriction is clearly stated here, along with all the other rules that Postgres follows. Bottom line: there are rejections and transformations going on.
To avoid a leaky abstraction, the exact values (as given by the user) must be stored. This roughly means either a blob (= no structure in the DB) or JSON string values that somehow preserve the original meaning: for instance base64-encoded string values in the DB (so recovering the structure at the expense of extra processing in the application in order to translate from base64 to the actual value).

The temporary workaround fix (simply dropping metadata objects that cannot be inserted in Postgres) has been merged to master.

This how it looks now with temp fix:
[db-sync-node:Info:37] [2020-09-22 10:19:09.66 UTC] insertShelleyBlock: epoch 84, slot 6060000, block 1816721, hash 3ec15354c53deae4eb26a206cc3185f799e80bd09393f279bce7e53a7d633144
[db-sync-node:Warning:37] [2020-09-22 10:19:24.08 UTC] insertTxMetadata: dropped due to a Unicode NUL character.
[db-sync-node:Warning:37] [2020-09-22 10:19:24.08 UTC] insertTxMetadata: dropped due to a Unicode NUL character.
[db-sync-node:Warning:37] [2020-09-22 10:19:24.10 UTC] insertTxMetadata: dropped due to a Unicode NUL character.
[db-sync-node:Warning:37] [2020-09-22 10:19:24.10 UTC] insertTxMetadata: dropped due to a Unicode NUL character.
[db-sync-node:Info:37] [2020-09-22 10:19:24.93 UTC] insertShelleyBlock: epoch 84, slot 6065000, block 1816973, hash 0ab0dd5c36c6eb480b8bbd05508be952c5ed8597a4e422af25bd80a905a9368d

Whether docker is repaired, and what is the repaired version

Its not fixed, but 5.0.x has a workaround that avoids this issue by dropping tx_metadata containing the Unicode NUL character.

Closing.


[Question] Does this show everyone's Optifine Capes?

-- Question - not an issue --
If another user in the Minecraft server I'm in has an Optifine donator cape also will I be able to see there cap?

Yes you SHOULD also see their optifine cape. If this is not the case feel free to report it, but that is the intended behaviour.

Thank you, was the only thing I was missing after switching to Neoforge!
Any chance you can release it on Modrinth? Would be great for the Modrinth app plus easy to follow updates as they come.

No problem just submitted the mod to modrinth for REVIEW. It will probably take some time for it to show up, but it should be available under when it is published:
https://modrinth.com/mod/showmyoptifinecape


can we expand all rows using accordion?

node, npm, react-native, react and native-base version
node - v9.1.0
npm - v5.5.1
react: "16.3.1",
react-native: "^0.55.4",
native-base: "^2.6.1",
Expected behaviour
1] i am using native base accordion  and  want to expand all the rows at the same time , can we have expand all property?
2] i have tried to modifiy the Accordion component file from node modules  but changes made in the file does not reflect, so is their any way to modify accordion functionality??
Actual behaviour
we dont have property for  accordion link expand all
Steps to reproduce should include code snippet and screenshot
Is the bug present in both iOS and Android or in any one of them?
ios and android both
Any other additional info which would help us debug the issue quicker.

i have tried to modifiy the Accordion component file from node modules but changes made in the file does not reflect

to get this working, go through https://github.com/GeekyAnts/NativeBase/blob/master/CONTRIBUTING.md#3-development-environment
This point being important here, In NativeBase's package.json, modify main from dist/src/index.js to src/index.js before you start with the development.

Thank you for the link i will go through the documentation

You can make this change initially, to find the code reflecting in your app

In NativeBase's package.json, modify main from dist/src/index.js to src/index.js before you start with the development.

yes i modified main from dist/src/index.js to src/index.js and now i can modify the component , Thankyou so much for the quick response

any other help needed here?

Closing this due to inactivity

Hi,
I've implemented the feature in the PR https://github.com/GeekyAnts/NativeBase/pull/2632

Hi, I tried expanded={[1,2]}, but it doesn't work for me. My React naive version is 0.60 and my native base version is 2.13.8. Any update?


Request body: empty "content" not recognized as an error

A Request Body Object is defined by a "content" attribute that specifies the possible media types. But what if no media types are specified? The OpenAPI spec doesn't say anything about this situation. But clearly the intention is that at least one media type must be defined. This clarification is likely to appear in the next version of the spec.
Accordingly, an empty "content" attribute for a Request Body Object should be reported as an error.

Thanks @kerrykimbrough  Closed by merged Pr #1649


⚠ otzivi-tut has degraded performance

In 9fe361c, otzivi-tut (https://отзывы-тут.рф/) experienced degraded performance:

HTTP code: 200
Response time: 7645 ms

Resolved: otzivi-tut performance has improved in 424ad56.


Template reactivity?

I have a problem with ReactiveState's reactivity:
client.js:
State.modify('Variables', (state = {a:0,b:0}) => {
let actionType=Action.type();
if (actionType=="INCR_A") {
state.a+=1;
} else if (actionType=="INCR_B") {
state.b+=1;
}
console.debug("State should be now: %o",state);
return state;
});
main.html:
<button dispatch="INCR_A">Increase variable A</button>
<button dispatch="INCR_B">Increase variable B</button>

Variable A: {{Variables.a}}

Variable B: {{Variables.b}}

...and the displayed values don't change at all - but the console.debugged do. Why?
I've put the code in here

I've just made a test with your code and it's working fine:
https://github.com/worona/meteorflux/blob/30012bb2522a0823cf69e02be60eacdb1dc421fb/packages/blaze-utils/tests/reactive-state-blaze-helpers-tests.js#L645-L671
so I have no idea what may be wrong. My only guess is to put {{Variables.a}} inside a template.
Testing in Blaze is difficult, that's one of the reasons Meteor is ditching Blaze.


useQueries data typed as unknown when using skipToken and TypeScript 5.4.5

Describe the bug
Noticed this when I attempted to update TypeScript as a prerequisite to update the Angular adapter to Angular 18 as the type test failed.
Your minimal, reproducible example
https://www.typescriptlang.org/play/?ts=5.3.3#code/JYWwDg9gTgLgBAbzgVwM4FMCKz1QJ4A0KG2uw6qRqA1sGACoTXoB2cAvnAGZQQhwByAAIwAhi1RiAxtQD0UdKKkwAtAEcc+AQChtUiBPgbceAEoVkAGxio4AXmJZN5VAAoE2uHGNQXALjgAbU8vRBDQ7008AGl0PADAgQB3YBgACwBlWgYmVgEAXQJw0J88ADEWAIBZUXSAOihxABM+VwBKOAA+OAAGOoBWOAB+OBo6RmY2APb7boAFXhBgDAaKCEsAN3RXfraiiPZ9uELtdjbdWVk4JtrROGW4FmQQACNcOAAfFBYm9C5gFjoJpwFLpOD0PBgdAZKS+MDwfp1ADMyKIL2Q8GQLGoLAgSTYoLS4Mh0NhdARdQALAM9AZJNdbvZIiZzKgrDZAj18nUbmJtJcIl4AHpDXT6QzM-Cs9lMtBOEzuEKlWLxILJVKZbITPInLylCrVWppBrNVodbp9QYjMY5SZwaYdOzzRbLdCrVDrLY7Panc78q68u4PJ6vd5fLG-f6A4GEuAvCBgiFQmFwinUwbNOCIlFI2kSwMAJiZpWl1h5t39grgIu0QA
Steps to reproduce
On the TS playground:
Notice both data from useQueries and data2 from useQuery are correctly typed number | undefined.
Switch the TypeScript version to 5.4.5
Notice data from useQueries is now typed as unknown, data2 from useQuery is still correctly typed.
Expected behavior
useQueries data should not be typed as unknown
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

Tanstack Query adapter
react-query
TanStack Query version
5.40.0
TypeScript version
5.4.5
Additional context
The Vue adapter has an equivalent type test which also fails, I suspect it's a problem for every framework.

Yeah seems like we need to take a look at the useQueries types which are super complex :/

The playground does not show the bug anymore since the useQueries type inference was improved 🎉 Thank you @gwansikk


Initial version of nanoFramework.Hardware.Esp32

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


MatchMS benchmarking seems to be wrong

I think you might be using an inefficient implementation of MatchMS also in this line .
MatchMS is very fast when used correctly, but your pre-print says 25 seconds per comparison!  My best guess is that you are using the .matrix syntax but not passing in multiple spectra.  You might try .pair(s1,s2) or even better is to use .matrix on two lists of spectra.  @florian-huber might be able to give some advice.

Hi,
I believe there may have been a misinterpretation of our data. In our tests, we found that MatchMS required approximately 25 seconds to calculate the spectral similarity for 1 million spectral pairs. This equates to about 25 microseconds per spectral pair. I agreed that MatchMS operates at a high speed.
Our findings are consistent with your benchmark results. Here is the figure of your benchmark result for reference:

According to your results, MatchMS also requires around 20-30 seconds to process 1 million spectral pairs.
The .matrix function calls the .pair function in a loop to compute the result, their speed should be similar. Therefore, their processing speeds should be comparable. You can refer to the source code here for more details:  [link to the code]

Sorry for the false alarm! My bad.  I misunderstood that section of the paper.

@YuanyueLi that should be correct.
For the cosine score in matchms we only implemented an optimized pair() method (which could probably be further optimized when used through the `matrix() method).


Export typo

(redacted)

I think that's actually a legitimate problem with lua_clonefunction which should not have had the LUA_API define in the implementation. The rules for declspecs are annoyingly complicated so this is probably okay for DLL export but may not be okay for some other specifiers, so it feels good to be consistent.


Performance Guidance

Some things already mentioned in various docs. Would be nice to have one doc dedicated to all the perf tips.
Some ideas:

Tracking vs no-tracking (per query, per type, etc.)
FromSql for complex queries
INotifyPropertyChanged
Key generation: sequence vs identity
How using .Include really works and its perf implication
Batching (configuring sizes, networking conditions, etc)

Any progress on this? In particular looking for SQLite+UWP perf tips.

@bartlannoeye the perf issues in UWP/SQLite are bugs that we're working with the .NET Native team to address. Unfortunately there isn't really any way to work around them.

Putting this on the backlog. A lot of the perf guidance from EF6 doesn't really apply to EF Core and I'm not sure how much we need to document here. I think it probably makes sense to wait a bit longer and see what kind of things aren't obvious to most folks, and then document these.

@divega a Short perf doc would be beneficial and would surely grow as customers contributed their perf findings. https://github.com/aspnet/Docs/pull/964 has a short EF perf section. It would be better to move that section to this repo and the ASP.NET Core perf doc could point to it.

@Rick-Anderson The short EF section I read in the PR seems like a good start of a page on the EF Core side. I posted some comment that hopefully can make it better.
There a few things remaining here that of course also have value, although at this point I think I would leave the "Key generation: sequence vs identity" part out.

Consult https://docs.microsoft.com/en-us/ef/ef6/fundamentals/performance/perf-whitepaper

Consult https://docs.microsoft.com/en-us/ef/ef6/fundamentals/performance/perf-whitepaper

But isn't Rowan correct

A lot of the perf guidance from EF6 doesn't really apply to EF Core

@Rick-Anderson yeah, this should be reviewed case-by-case, lots of things are relevant, some probably aren't... This is one of the major docs tasks on my plate.


Ensure multiple queue processors don't run duplicate jobs

Right now queuedjobs seems to rely on only 1 copy of the worker process running. If you have multiple workers running—e.g. for scaling, or because you have more than 1 server and it's easier to configure them the same—race conditions can lead to a single job being executed more than once.
It would be better if the queuedjobs module guarded against this. Presumably this would involve updating the status from the non-running state to the running state in a single command:
UPDATE "QueuedJobDescriptor" SET "JobStatus" = 'Running'
WHERE "JobStatus" IN ('New', 'Waiting') AND "ID" = $jobID

If this command didn't affect any rows, then we know someone else as handled the job and we can exit without running the job.
I guess this goes in here? https://github.com/silverstripe-australia/silverstripe-queuedjobs/blob/master/code/services/QueuedJobService.php#L395

Given that the first execution of job code happens in QueuedJobService::initialiseJob(), it's probably the best point to do the explicit update-mark-running/row-count-check at that point

:+1:
I haven't found any other way to do this that is reliable without doing database specific custom queries.

@stojg could you use database locks? Something like this: https://github.com/silverstripe-elliot/silverstripe-queuedjobs/commit/f52fdbe6fd9e85fe6378cba9246216f6f1865189

Affected rows pull request: https://github.com/silverstripe-australia/silverstripe-queuedjobs/pull/32

@silverstripe-elliot the solution proposed in #32 is more hacky, but at least it will work across all databases. I'm looking at you, MariaDB/Galera :-)
This might not solve the problem in 100% though :-) I haven't really researched how atomic are the UPDATE queries and how isolated they are (across all databases we support), but there is a possibility that the "affectedRows" method is not race-proof.

I raised this ticket originally and #32 is certainly the kind of fix that I had in mind. I'm happy to close this now that it's been #32 has been merged.


HUGE SECURITY RISK: Returning everything when undefined is passed

This is reproduced in Prisma 1 and I have posted this issue there. I know this is not a Prisma 1 repo but the Prisma 1 repo is abandoned and I assume you reuse/rewrite Prisma 2 based on 1 so this huge security bug that might also be reproduced in Prisma 2 (I haven't use Prisma 2 so I can't test it for you). So I am bringing you the attention of this security bug and hopefully you can either fix it in Prisma 2 or confirm that this security risk is not present in Prisma 2.
Describe the bug
Return all when undefined is passed. Using Yoga, this step is not reproduced in Playground, however. Maybe it is a Yoga's problem, maybe it is Prisma's, but this is a huge security risk.
To Reproduce
Steps to reproduce the behavior:
return await ctx.db.query.users(
      {
        where: {
          user: {
            id: *undefined*,
          },
        },
      },
      `{ password leakedInformationHere}`
    );

Expected behavior
It shouldn't return anything.
Versions (please complete the following information):

Connector: Postgres
Prisma Server: 1.34.0
prisma CLI: 1.34.0
Yoga: 1.18.3

Additional context
Cross-posting to Prisma 2 too because prisma1 is abandoned.

Hi, I have been playing with prisma 2, but I didn't encounter it yet. Moreover prisma 2 doesn't even have a playground anymore. Let's test it and see if this is reproduced in the current version as well.


LTI Advantage for .Net framework

Hello,
We are looking to update our code to LTI Advantage from 1.1 and noticed that it is built in .net core. Our project is in .net framework. Any suggestions?

LtiAdvantage library targets netstandard2.0 but does indeed have a dependency on Microsoft.AspNetCore.  I think that dependency can/should be moved to separate project...perhaps LtiAdvantage.AspNetCore?  This came up in https://github.com/LtiLibrary/LtiAdvantage/pull/14#issuecomment-719869286
I've considered looking into that myself but am a bit swamped at the moment.

Just merged #23 and #17. Closing this one.


Option to rename VCF samples in BAFFromShardedVCF

Adds Array[String]? replacement_snp_vcf_sample_ids input to Module00c. When specified and using the snp_vcfs input to generate BAF, each vcf will be reheadered with the given sample IDs. This is useful when sample IDs have been reformatted for gatk-sv but the the vcfs have been already been generated with original IDs.
Note that the length and order of replacement_snp_vcf_sample_ids must exactly match that in the vcfs (or header file if provided), and also that they may be different from the samples input (e.g. when the batch samples are a subset of those in the vcf, or the vcf samples are in a different order).

Closing in favor of a simpler solution. I will open a new PR.


String interpolation

This is so very, very badly needed right now. I'm extremely tired of having to use printfmt and string::format for formatting strings. I'm desperate for some interpolation so I can finally destroy both of those.
A basic example of what interpolation might look like:
print("Hi, my name is :(name)")
String interpolation would have access to variables anywhere. Global, local, subscripts, etc. Do whatever you like, but with a couple rules:
No nested interpolation
No lambdas (Why would you do this?)
No escape characters (Any attempts to escape will show the value as-is)
The interpreter will initially make a best guess at determining how to print a string version of whatever is being sent. Eventually, the ability to have format specifiers may be added, as well as using the to_s function of a value when that machinery is finally working.

Kicking the can down to the next release. This release only has two weeks left, and I can't do a good interpolation in that timeframe.


pull request for e2e test at 11/09/2016 09:45:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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


Create newsletter guidelines

We can create a new document that covers OSPONews guidelines to let the community know what can be included in the newsletter

Related PR for this: https://github.com/todogroup/ospology/pull/2


Create File Structure On Front End Using Atomic Design: FE

One of the biggest challenges with React Applications is maintaining organization. I suggest we adopt atomic design for our front end.
Article On Atomic Design<EMAIL_ADDRESS>Sample Atomic Design Repo: https://github.com/AKIRA-MIYAKE/applicational-atomic-design-for-nextjs
To me its a very well organized way to structure reusable components. Very open to other suggestions as well.

I really like the idea. I was trying to match the article example with the one in the GitHub repo to see how it translated and it was a little hard to see but overall I get the idea and I like or organization behind it. I'll continue to look to see if there any other ways organize.

Sounds like a good way to stay organized!


[ALLUXIO-111]

https://alluxio.atlassian.net/browse/ALLUXIO-111
add final in alluxio/worker/block/BlockMasterSync.java

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17532/
Test PASSed.

Hi @zyyseu  this PR is not to address:
https://alluxio.atlassian.net/browse/ALLUXIO-111
I think it is for the new contributor issues in https://github.com/Alluxio/new-contributor-tasks/issues/, right? You can simply change the title to be [SMALLFIX] Add final in alluxio/worker/block/BlockMasterSync.java and remove the link to JIRA (ALLUXIO-111) in the description.


Missing binomial functions

Binomial distribution functions were lost when GSL was removed, and need to be added back.

Binomial related functions have been added, please check {this doc}.

Thanks Liang.  (Owl's binomial_pdf is about 2X faster than GSL's on larger integers.)


changing the polling frequency for the h100 hub doesn't have any effect on paired T110 contact sensors

If I open a window in my room (with T110 contact sensor) or my door (also T110 contact sensor) I want all the lights in my room to turn off. So far the automation is working very good. The only problem is the delay of the sensors connected to the H100 Hub. The delay is mostly 20 to 30 seconds. Changing the polling time of the H100 Hub in the Tapo integration configuration from 30 to 3s also results in no changes in the reaction time for the T110 sensors. The Report interval of both contact sensors stays steadily at 16s (displayed in HA). And the real reaction time stays at 30s.
I need a low reaction time of under 2 seconds for the contact sensor on my door because otherwise HA doesn't even register any change of state if I leave my room.
Is there any setting which directly modifies the polling time for the T110 sensors?
For others reading this and having the same problem:
My workaround so far is to have the official Tapo App change one led in my room to a specific color as soon as the T110 registers a change and then use the rgb color change of this lamp (with reduced polling time to 3s in the HA Tapo Integration) as a trigger for my automation. The polling time change works for the L530 leds in my case.
I don't know if you need any logs for this, because there shouldn't be much to see other than the polling time of the contact sensors not changing.
If you're reading this, thank you for your time and support.

I'm not sure this is the right place to comment ,I am experiencing the exact same issue, I'm using the T110 sensor to activate a seen when my door opens and I also need a 2 second reaction time.
Thank you for the effort you put into this product.

Same here - any workaround?

Same here.
I also receive a lot of "became unavailable" status for all T110 and T100. When I check the HA logs I find this API error:
_This error originated from a custom integration.
Logger: custom_components.tapo.coordinators
Source: helpers/update_coordinator.py:332
Integration: TP-Link Tapo (documentation, issues)
First occurred: 9:26:17 AM (30 occurrences)
Last logged: 10:06:39 AM
Error fetching tapo data: Error communication with API: [Errno 104] Connection reset by peer
Error fetching tapo data: Unexpected exception:
Error fetching tapo data: Error communication with API: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]_

Same here - any workaround?

I described my workaround (using a Tapo Lamp colour change) in my original post. You can use that if you can.

My problem is that I am using the Tapo sensor to activate a light from another system :(

@petretiandrea any idea where it would be in the code? I can try to fix.

My problem is that I am using the Tapo sensor to activate a light from another system :(

I understand. Sorry for assuming your light manufacturer. 😂
That is unfortunate then. I just wish the Tapo Hub Events would trigger as reliable as with the stock Tapo App. But I know about the technical issues with this.

The problem is the same of buttons https://github.com/petretiandrea/home-assistant-tapo-p100/issues/556. There is no event stream for sensor, but only polling. Polling too frequently means making DOS to your hub. Actually I don't have an alternative way of polling.

Gotcha
I haven't check the other issue as I am not in front of my computer, but where can we change the default settings? I think it is set to 16s right? I tried to change through console and it didn't work
Happy to test with a sort time as I don't have many devices anyway, so it should not impact the performance or DDoS the device

@petretiandrea I get what you are saying! In my case is kind of critical since I am using motion and contact sensors for alarm system.
If i set a high refresh interval (say >5 seconds) It could be the case of the door opening and quickly closing before the 5 seconds elapsed and the HA won't know that the door was opened, hence alarm will not be triggered.
If i set the refresh interval too low (say <3 seconds) I frequently get sensor states "unavailable" possibly because i am "DoS" the hub.
Since there is no solution yet, do you have anything to propose? I found that around 4 seconds is pretty reliable for me, but i still think it's kind of high for alarm purposes.

@ninosnicolaou how did you change the interval?

@ninosnicolaou how did you change the interval?

oh!
I actually was trying to change the sensor settings, which is limited to 16s, let me try, thanks!

I "fixed" my issue. So I removed all my sensors from TP-Link Tapo integration and managed to get them into the Matter (beta) integration. Basically in Tapo App (due to a recent update) I am able to add H100 hub in HomeKit (as i bridge i think, natively supported by Tapo). Now in iOS Home app I have the H100 as a bridge.
I then tried Matter (Beta) HASS integration and using the iOS companion app I was able to add the H100 in HASS as well. Now the response is instant (like truly instant) and since I am not using this integration I am not polling the H100 continuously, all the timeouts and sensors being unavailable is no longer a problem.
However, i still use this integration to be able to have the hub.siren entity (and trigger in case of alarm) since it's not supported in Matter (Beta) integration.

@ninosnicolaou do the smart buttons work in the Matter Beta integration (single tap/double tap/rotate cw/rotate ccw)? And if the do, do they work in HomeKit and HA?

@ninosnicolaou do the smart buttons work in the Matter Beta integration (single tap/double tap/rotate cw/rotate ccw)? And if the do, do they work in HomeKit and HA?

Homekit: Doesn't work (not supported by Tapo yet)
Homeassistant: No controls/entities available, so no, they don't work

I then tried Matter (Beta) HASS integration and using the iOS companion app I was able to add the H100 in HASS as well. Now the response is instant (like truly instant) and since I am not using this integration I am not polling the H100 continuously, all the timeouts and sensors being unavailable is no longer a problem.

Agreed - I've now done this as well and the response is instant with a T100 motion sensor changing stated to 'Detected'
What's frustrating me though, is that it doesn't seem to Clear the occupancy until 1 minute later.
Looking at the Tapo IOS app, it is constantly maintains the 'detected' state as detected every 4 seconds (update interval) but there doesn't appear to be an update anywhere to change it to Clear. Nothing I do reduces this to less than a minute. I tried changing the refresh time in the tapo integraton, but that doesn't change anything either.
So it appears that the Tapo T100 or the Hub only update/report the Clear status 1 minute after the last Detected event.
@ninosnicolaou does it update your contact sensors to both Open and Closed instantly? Or do you think my problem just motion sensor specific?

Mine as well keeps the same state for 1 minute. But this was the case with Tapo integration as well. I think it's a hassio thing to be honest. Also I think you misunderstood the concept of motion sensors, they are not like contact sensors (no instant on/off state)
Homeassistant has 2 types of "motion sensors" in my understanding.

Motion entity
Occupancy entity

Take a look at these.
I am also new to hassio so take everything with a grain of salt!

Mine as well keeps the same state for 1 minute. But this was the case with Tapo integration as well. I think it's a hassio thing to be honest. Also I think you misunderstood the concept of motion sensors, they are not like contact sensors (no instant on/off state)
Homeassistant has 2 types of "motion sensors" in my understanding.

Motion entity
Occupancy entity

Take a look at these. I am also new to hassio so take everything with a grain of salt!

No problem. Yes I realise they may not work exactly the same as contact sensors. I would have thought though, seeing as the Tapo app shows a 'Detected' log every 4 seconds, that it also knows when it is not in the 'Detected' state and so that info should be available to users.
FYI using the Tapo integration they are seen as a Motion entity (with the battery and report interval entities), but using Matter they are an Occupancy entity only. Aside from that they appear to operate essentially the same, but with Matter I get the 'Detected' state faster.

@doenau
You can chance occupancy with motion and vice versa


Adds Effect.RunScript, Effect.Icon, Effect.HideIcon

Adds Effect.RunScript, Effect.Icon, Effect.HideIcon

Superseded by https://github.com/nwn-dotnet/Anvil/pull/366


python310Packages.hahomematic: 1.3.1 -> 1.4.0

Description of changes
https://github.com/danielperna84/hahomematic/releases/tag/1.4.0

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)
[ ] 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

[ ] 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.

Result of nixpkgs-review pr 173428 run on x86_64-linux 1

2 packages built:

python310Packages.hahomematic
python39Packages.hahomematic


what am i doing wrong

hi love this - when i use it - it is closing after reaching 100 but also closing whole app - what am i doing wrong please?
public void doProgressDialog() {
ProgressDialog progressDialog = new ProgressDialog(this);
// Set horizontal progress bar style.
progressDialog.setProgressStyle(ProgressDialog.STYLE_HORIZONTAL);
// Set progress dialog message.
progressDialog.setMessage("This is a horizontal progress dialog.");
// The maxima progress value.
progressDialog.setMax(100);
// Whether progress dialog can be canceled or not.
progressDialog.setCancelable(true);
// Popup the progress dialog.
progressDialog.show();
// Create a new thread object.
Thread thread = new Thread(new Runnable() {
		@Override
		public void run() {
			int i = 0;
			// Update progress bar every 0.3 second.
			while (i < 100) {
				try {
					Thread.sleep(30);
					// Update the progress value.
					progressDialog.incrementProgressBy(1);
					// Update the secondary progress value.
					progressDialog.incrementSecondaryProgressBy(5);
					i++;
				} catch (Exception ex) {
					ex.printStackTrace();
				}
			}
			// Close and delete the dialog when the progress bar is finished
			progressDialog.dismiss();
		}
	});

	// Start the thread.
	thread.start();

}

Hi. You are trying access progressDialog from the background thread. You cannot access UI elements from the background thread in Android. This is causing the crash in your case.
Use Handler to access progressDialog from your thread.
This StackOverflow post might help:
https://stackoverflow.com/questions/11123621/running-code-in-main-thread-from-another-thread


Default legend background transparent

Shouldn't the default legend background be transparent? It's not really intuitive to see that as soon as you're using a non-white background, which will certainly happen on a lot of pages out there.

Nice catch! Just pushed the change here: 2cf8fc64e3e62592d92b0fd6950c7fb753a7f527
Thanks!


feat: implement storage for OTLP histogram

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This patch adds OTLP histogram data type support, which was left blank in our initial release.
The implementation has been following Prometheus histogram table format:

A %metric%_bucket table including le tag that stores bucket upper limit, and greptime_value for bucket count
A %metric%_sum table storing sum of samples
A %metric%_count table storing count of samples.

By its Prometheus compatibility, we hope to be able to use prometheus quantile functions on this table.
Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

maybe this will help:
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/prometheusexporter/collector.go#L97

Updated. PTAL @yuanbohan @fengjiachun @waynexia


A bug appear during runtime

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize
return torch.UntypedStorage(obj.nbytes(), device=torch.device(location))
RuntimeError: CUDA error: out of memory
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports:
Process Process-97:
Traceback (most recent call last):
File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap
Self. run()
File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run
Self_ Target (* self. args, * * self. kwargs)
File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect
A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath)
File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2
V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device
RuntimeError: CUDA error: out of memory

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports: Process Process-97: Traceback (most recent call last): File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap Self. run() File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run Self_ Target (* self. args, * * self. kwargs) File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath) File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2 V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device RuntimeError: CUDA error: out of memory

Hi, thank you for your interest. Since we are extracting features from the original problem, this could happen as the problem sizes become too large. One possible solution is to try on presolved instances where redundant columns are removed.

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports: Process Process-97: Traceback (most recent call last): File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap Self. run() File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run Self_ Target (* self. args, * * self. kwargs) File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath) File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2 V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device RuntimeError: CUDA error: out of memory

Hi, thank you for your interest. Since we are extracting features from the original problem, this could happen as the problem sizes become too large. One possible solution is to try on presolved instances where redundant columns are removed.

Thank you. Based on the information you provided, I have resolved the problem I encountered.

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports: Process Process-97: Traceback (most recent call last): File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap Self. run() File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run Self_ Target (* self. args, * * self. kwargs) File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath) File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2 V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device RuntimeError: CUDA error: out of memory

Hi, thank you for your interest. Since we are extracting features from the original problem, this could happen as the problem sizes become too large. One possible solution is to try on presolved instances where redundant columns are removed.

Thank you. Based on the information you provided, I have resolved the problem I encountered.

Hello， have you replicated this work? I don't know how to get primal gap to plot Figure about time and average primal gap, could you give me some help?

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports: Process Process-97: Traceback (most recent call last): File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap Self. run() File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run Self_ Target (* self. args, * * self. kwargs) File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath) File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2 V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device RuntimeError: CUDA error: out of memory

Hi, thank you for your interest. Since we are extracting features from the original problem, this could happen as the problem sizes become too large. One possible solution is to try on presolved instances where redundant columns are removed.

Thank you. Based on the information you provided, I have resolved the problem I encountered.

Hello， have you replicated this work? I don't know how to get primal gap to plot Figure about time and average primal gap, could you give me some help?

Hello. For some reasons, I have not replicated this work and have instead moved on to other work.  I regret that I couldn't be of help to you.

Hello, thank you for your excellent work. I hope to replicate your work, so I ran the code and found the following error when running Python trainPredictModel. py.
/anaconda3/envs/gurobi/lib/python3.8/site-packages/torch/serialization.py", line 185, in _cuda_deserialize return torch.UntypedStorage(obj.nbytes(), device=torch.device(location)) RuntimeError: CUDA error: out of memory Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi, thank you very much for your comment. This issue can be solved by reducing the size of batch in L30 of trainPredictModel.py. Please feel free to contact if you have any other concerns.

hello，I also encountered 'RuntimeError: CUDA error: out of memory', but it did not appear during the training process, but during the call to gurobi. py. Here are some detailed error reports: Process Process-97: Traceback (most recent call last): File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 315, in_ Bootstrap Self. run() File "/home/cc/anaconde3/envs/pytest/lib/python3.8/multiprocessing/process. py", line 108, in run Self_ Target (* self. args, * * self. kwargs) File "/home/cc/code/Predict and Search-MILP_method main/globi. py", line 82, in collect A2, v Map2, v_ Nodes2, c_ Nodes2, b_ Vars2=get_ A_ New2 (filepath) File "/home/cc/code/Predict and Search-MILP_method main/helper. py", line 467, in get_ A_ New2 V_ Nodes=torch. as_ Tensor (v_nodes, dtype=torch. float32). to (device) # Variable nodes # TODO device RuntimeError: CUDA error: out of memory

Hi, thank you for your interest. Since we are extracting features from the original problem, this could happen as the problem sizes become too large. One possible solution is to try on presolved instances where redundant columns are removed.

Thank you. Based on the information you provided, I have resolved the problem I encountered.

Hello， have you replicated this work? I don't know how to get primal gap to plot Figure about time and average primal gap, could you give me some help?

Hello. For some reasons, I have not replicated this work and have instead moved on to other work. I regret that I couldn't be of help to you.

OK, whatever,  thank you, bro.


[BUG] Cannot Sysprep after using Optimize-Offline

Describe the bug
Unable to run Sysprep when using any version of Optimize-Offline above <IP_ADDRESS>. Using <IP_ADDRESS>, I can successfully Sysprep and capture the image but the newer versions produce an error.
Screenshots

Please complete the following information:

Image Name: Windows 10 Pro
Image Build: 18363

Log files
setupact.log

This is an issue that occurs with a mismatch with the 'spopk.dll' file in the 'C:\Windows\System32' directory.
According to the Microsoft forums, this seems to be an issue with specific builds of 1903-1909.
Note that Optimize-Offline does not touch any of these types of files in the 'C:\Windows\System32' directory.

I have tried the fixes mentioned in the post and it doesn't work. Replacing the "spopk.dl"l still causes the same issue.
I performed an experiment and used the same Image Build using both <IP_ADDRESS> and <IP_ADDRESS>. With <IP_ADDRESS> I get a sysprep failure but when using <IP_ADDRESS> sysprep works.

Hi,
I had this issue a couple of times and each time I resolved it successfully by replacing and copying the "spopk.dll" from the host machine to the live environment! It will work (100%)! Take ownership of the relevant file before that. You can even copy the .dll file from the lower Windows version!

Yes, what Alexusson said seems to correct this issue.
Optimize-Offline has never removed files from the System32 directory.

That's so weird, I've tried replacing the file and it never works. I'll have to try it again and see.

Had the same issue with my 1909 optimize-offline image.
I tried the same as Alexusson and it worked, BUT... it didn't work when i used ver1909 spopk.dll from my host machine...
I then used the spopk.dll file from a 1809 win2019 server i had, and then it worked.


[AVM Question/Feedback]: Peerings fail with a missing feature, but the feature appears registered

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
When specifying peerings, I am getting an error that the Microsoft.Network/AllowMultiplePeeringLinksBetweenVnets feature isn't registered.
However, when I run Get-AzProviderFeature -ProviderNamespace Microsoft.Network -FeatureName AllowMultiplePeeringLinksBetweenVnets, the state shows as Registered for the subscription where the error applies.
What can I do to resolve this issue?

OK, interesting. I checked on the remote side and the feature was not registered there. Even though the Terraform error clearly indicated that the subscription ID where it said the feature wasn't registered was the local side.
I went ahead and registered the feature on the remote side and then re-ran Terraform.
I am no longer getting that error, but now there's a different error, on both peerings:
│ --------------------------------------------------------------------------------
│ RESPONSE 400: 400 Bad Request
│ ERROR CODE: LocalAndRemoteSpaceMustContainEitherIpv4orIpv6Prefix
│ --------------------------------------------------------------------------------
│ {
│   "error": {
│     "code": "LocalAndRemoteSpaceMustContainEitherIpv4orIpv6Prefix",
│     "message": "Cannot create or update peering /subscriptions/fca9eaf6-728a-4252-9e2d-aa2532c82614/resourceGroups/network-demo-rg-cnc-01/providers/Microsoft.Network/virtualNetworks/hub-demo-vnet-cnc-01/virtualNetworkPeerings/hub-to-identity. Both Local and Remote Address Space in a Virtual Network Peering must contain either atleast one IPv4 in both or IPv6 prefix in both. Peered Spaces are, Local Address Space:  and Remote Address Space: ",
│     "details": []
│   }
│ }
│ --------------------------------------------------------------------------------

(I have also tried manually creating the peerings and that works.)

Let me check on this, we added a capability to register features for preview features. All our examples work successfully, so would be useful to see your Terraform code to be able to reproduce.

@SvenAelterman ERROR CODE: LocalAndRemoteSpaceMustContainEitherIpv4orIpv6Prefix. How did you resolve this error?

@SvenAelterman ERROR CODE: LocalAndRemoteSpaceMustContainEitherIpv4orIpv6Prefix. How did you resolve this error?

This should have been fixed in v0.4.0


feat: override Module#_compile

Hook into the jest module loading mechanisms for the Module#_compile functionality provided by Node. Fixes #10069.
Summary
Provides a consistent experience when interacting with uncommon features that load modules. See #10069.
Test plan
See unit tests.
This is probably incomplete; some of the edge cases of the semantics aren't clear to me, such as what should happen with the isolated registry when the require call happens outside the context of the isolateModules call.

I've glanced over this without giving it a detailed review yet. Let's talk about the general approach first. IIUC you are making sure that the explicitly compiled module does not collide with a really existing file path by loading it in an isolated registry context? I think to avoid edge cases like the one you already predicted, a better approach would be having a code path that does not mutate the runtime state in the first place, which we can then use for _compile.

Yeah I started with that approach, but realized that it wouldn't support certain cyclic module reference patterns like RegularModule.js -> ModuleWithSideEffects.js -> RegularModule.js. I suppose that might be out of scope for _compile'd source, but it might also be a feature that folks use? Moreover, it might be expected that loading ModuleWithSideEffects.js would load a new copy of the module in an isolated registry so that it doesn't interfere with the real modules, but the opposite might also be true. Seems probably best to require manual use of isolateModules, but that still doesn't help inform the original problem with requireing the module that was directly _compile'd. Thoughts?

I would try to be like Node as much as possible. In Node,
x.js
---
module.exports = { a: 42 };
const module2 = new module.constructor.Module();
module2._compile("module.exports = require('./x.js')", "y.js");
console.log(module.exports);
console.log(module2.exports);
console.log(module.exports === module2.exports);

prints
{ a: 42 }
{ a: 42 }
true

So the compiled y module does get the same x module that was compiling it, just as it would with normal cyclic requires, and just as it would with cyclic requires in Jest. We want to achieve the same here.
Does a naive implementation with the approach not yield that behavior? I would think it does, since cyclic requires in Jest do behave the same as cyclic requires in Node.

I would try to be like Node as much as possible.

I'm on board with that! I think I had a bad assumption about Node's default behavior and had been assuming that the new Module would end up linked from require.cache somehow. I definitely don't need that functionality, though, so I'll push the naive implementation. I do wonder if we'd like to support any manual modifications of the registry to support a pattern equivalent to:
import { Module } from 'module';

const m = new Module();
require.cache = id;
m._compile(fs.readFileSync(id, 'utf-8'), id);

So that if id referenced x.js that m.exports would equal { value: 'something' } in this example:
// x.js
require('./y');

// y.js
// This would mutate a new copy of x.js in the ModuleRegistry, rather than
// getting a reference to the x.js that loaded y.js.
require('./x.js').value = 'something';

The only implementation detail I'm a little hung up on is the Module's filename property, which is null by default in Node, but can't be null in order to support the jest runtime's require functionality (and the current implementation of _execModule). The quick & dirty solution is to pass in a Proxy, I think, but that's not great. I could refactor the whole code path to support an alternate filename parameter?

Ready for review minus the appropriate tests for verifying test environment. Would love some guidance there - not sure how to control testEnvironment here.

Regarding require.cache modifications, the last discussion on that I've seen is in https://github.com/facebook/jest/issues/9916


Pad IO Frame

Is there a way to take an output design GDS file that has your standard cells and place them in a frame with the pin pads drawn out and all your IOs connected to the Pin Pads? I haven't found an easy way to do it with siliconcompiler. Ideally i'd want something like this https://cdn.discordapp.com/attachments/1167882703052480624/1170631727010566144/image.png?ex=6562f941&is=65508441&hm=b51d7a8d3e084e556cd18d89587fcc87b53ad220c105e2c942ec6e1f1a8829b9& with all the pads drawn out and the frame.

I'm not sure I follow. You want to be able to take an GDS and place it inside another GDS?

Sorry I wrote that off, I just want to be able to output the standard cells connected to drawn out pads so basically like as if my digital cells were placed into a frame with pads.

I'm sorry, but I'm still not sure I follow. The picture does not help clarify anything for me. Maybe if you can clarify the usecase

ok, is there a way in the python script to generate bond ponds, in the picture i provided you can see those big pads surrounding the chip. I'll like a way to generate that in silicon compiler after my design is finished compiling.

you can see here, the frame surrounding the cells, with IO bond pads

@ryancor Are you asking if SiliconCompiler supports the caravelf flow? Padring design depends on the process and padring library. Take a look at zerosoc for an example of a padring design using siliconcompiler.
https://github.com/siliconcompiler/zerosoc


converter: improve pack performance by fifo

In the previous convert implementation, the builder (nydus-image) would
dump the blob and bootstrap, and then the converter would pack the two
files into a tar format, which has a performance loss, this patch solves this
problem by introducing fifo file.
The converter creates a fifo file, the builder will write the blob and
bootstrap data to the fifo as the writer side, then the converter read
from the fifo and write directly to content store for faster conversion.
Related PR: https://github.com/dragonflyoss/image-service/pull/415
Signed-off-by: Yan Song<EMAIL_ADDRESS>

Codecov Report

Merging #44 (396d2d6) into main (6112f67) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #44   +/-   ##
=======================================
  Coverage   35.09%   35.09%
=======================================
  Files          18       18
  Lines        1288     1288
=======================================
  Hits          452      452
  Misses        765      765
  Partials       71       71

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 6112f67...396d2d6. Read the comment docs.

Wait for this PR https://github.com/dragonflyoss/image-service/pull/415 to be merged then pass the CI testing.


Native library-only aars always show up as unused

Build scan link

Plugin version
0.56
Gradle version
6.6
Android Gradle Plugin (AGP) version
4.0.1
Describe the bug
Similar to proguard-only artifacts, aars that contain only native library files always are reported as unused
To Reproduce
Steps to reproduce the behavior:
Example aar https://amazon-chime-sdk-android.s3.amazonaws.com/media/0.6.1/amazon-chime-sdk-media-0.6.1.tar.gz
Expected behavior
Unsure if the plugin should try to detect loading native libraries in the aar, but at least not suggesting their removal would be a good start
Additional context

The library associated with the above link is amazon chime https://github.com/aws/amazon-chime-sdk-android

It might be challenging to determine if libraries such as these are in fact "unused", so I may have to treat them like libraries that include service loaders -- that is, never call them unused.
I'm considering enhancing the reporting so that "whitelisted" dependencies are listed for a human to double-check.

@ZacSweers To save me from learning how to use this SDK, can you provide a snippet of sample code that ought to indicate "this is used"? I'd like to write a(n accurate) failing test to get started.

Here's how it loads them https://github.com/aws/amazon-chime-sdk-android/blob/b43e22c435eab388ac1258669b0011c29c747fda/amazon-chime-sdk/src/main/java/com/amazonaws/services/chime/sdk/meetings/internal/audio/AudioClientFactory.kt#L18-L19


webservice: search vs. freeSearch vs. attributeSearch

For the webservice, I often get the different search types confused:

search as in GET /Human/search/1234
freeSearch as in GET /Human/isFreeSearchSupported
attributeSearch as in GET /Human/attributeSearch/CCR5

Would anyone else find it helpful if we updated the endpoints to make it easier to distinguish between the search types? Here are three sets of alternatives that I find easier to understand:
A

GET /Human/identifierSearch/1234
GET /Human/isIdentifierSearchSupported => true
GET /Human/attributeSearch/CCR5

Note that since BridgeDb is primarily about identifiers, one could argue that search is better than identifierSearch.
B
Webservice could accept a new query parameter named field with a default value of Identifier:

GET /Human/search/1234 (equiv. to /Human/search/1234?field=Identifier)
GET /Human/isSearchSupported => true (equiv. to /Human/isSearchSupported?field=Identifier)
GET /Human/search/CCR5?field=Symbol
GET /Human/isSearchSupported?field=Symbol (optional new endpoint)

C

GET /Human/identifier/1234
GET /Human/searchFields/identifier => true
GET /Human/symbol/CCR5
GET /Human/searchFields/symbol => true (optional new endpoint)

Not sure about desired capitalization: search_fields vs. searchFields or identifier vs. Identifier, symbol vs. Symbol. Some people recommend not using capital letters in webservice endpoints.

If we changed anything, we'd obviously need to add redirects for backwards compatibility.

Making a change like this is only worthwhile if there's a general consensus that doing so would make the webservice easier to understand. Any opinions from @egonw, @AlexanderPico, @AlasdairGray, anyone else?

Closing for lack of interest.


Can't resolve to value outside the bounds

Current behavior
Not permitted to resolve a numeric-range question to a value outside of the bounds even if bound(s) is/are open.
## Expected/desired behavior
Expected behavior
If the left bound is open, should be allowed to resolve to a value < left bound. If the right bound is open, should be allowed to resolve to a value > right bound.

Spec here.

@lsabor adding you a second assignee to do the BE part of supporting unknown resolution values as discussed on a call

Ready for testing on dev

lgtm


Only start haptic manager if feature is supported

Fixes #637
During creation of the internal video streaming manager, a check was added to ensure the module supports spatial data before creating the haptic manager. Subsequent calls to the haptic manager are surrounded with checks to see if the manager is null or not.

Codecov Report

Merging #639 into release/4.4.0-rc1 will decrease coverage by 0.01%.
The diff coverage is 0%.

@@                   Coverage Diff                   @@
##             release/4.4.0-rc1     #639      +/-   ##
=======================================================
- Coverage                41.28%   41.27%   -0.02%
  Complexity                2641     2641
=======================================================
  Files                      360      360
  Lines                    15709    15713       +4
  Branches                  1652     1655       +3
=======================================================
  Hits                      6486     6486
- Misses                    8936     8940       +4
  Partials                   287      287

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/smartdevicelink/proxy/SdlProxyBase.java
5.44% <0%> (-0.01%)
6 <0> (ø)

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 59fcaf3...d495b0c. Read the comment docs.