Support for symbolic links for the config file (~/.hyper.js)

[X] I am on the latest Hyper.app version

[X] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: 10.13.2 (macOS High Sierra)

Hyper.app version: 1.4.8

.hyper.js: default

The issue is reproducible in vanilla Hyper.app: Yes

Issue
I've got the default version of ~/.hyper.js, however the file is symbolically linked (.hyper.js -> dotfiles/.hyper.js). When I open Preferences in the menu, it opens in the Safari browser without ability to change it (file:///Users/kenorb/dotfiles/.hyper.js). Is there any way that Hyper can support symbolic links to the actual config file and edit that file?

It seems it worked after installing TextMate.


Add input_file_name built-in function

Is your feature request related to a problem or challenge?
It's useful to project the source input file of a data row to support file aware operations, for example for storage frameworks (https://github.com/delta-io/delta-rs/issues/850). This is a built-in function in Spark, for example, https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.functions.input_file_name.html
There was prior work before the repository split but it looks to have lost momentum:
https://github.com/apache/arrow/pull/9944
https://github.com/apache/arrow/pull/9976
https://github.com/apache/arrow/issues/18601
Based on the conversations in the prior PRs and issues it looks like there was consensus that this feature should live in datafusion as opposed to arrow, so creating an issue here.
Describe the solution you'd like
A built-in function supported for both SQL and DataFrame APIs input_file_name() that returns a string of the file from which the row was originally scanned.
Describe alternatives you've considered
No response
Additional context
No response

My "gut feeling" is that this will be a very complicated feature to implement with the existing Listing table provider.


(PE-24721) Correctly daemonize

Pass daemonize option to the correct handler. Also ensure pidfile is configured. Update services to match.
Put pidfile and logs in subdirectories so pe-bolt-server can be made owner of them.

CLA signed by all contributors.


Support for HoI4 is almost completely broken

Cannot resolve if-statement
Cannot resolve floating-point number
Cannot resolve divison template in oob file
Cannot resolve String literal

version: IntelliJ IDEA Ultimate 2022.3.2
I invalidated cache and reloaded but error still happened.

[x] HoI4 file is loaded

variable_field will be supported at 0.7.11 ((quoted) int /  (quoted) float / some_variable / root.some_variable, I guess.)
other errors seems I should buy Hoi4 and then check it manually, finally.


Black screen Before playing any video

Hi
I am using this package for list of videos which is coming in url I have one issue with this package whenever I play any video it after loading or initializing it shows me a black screen for a split seconds then starts playing the video in the url
Can you help me to fix this

https://www.loom.com/share/daf5c44f47764b489217cb1a26643b9d?sid=5abc4e41-9400-4666-99d8-e6e69dadb58c
Here is the link as you can see there is delay after the loader and video which is a back screen I played two videos here and each time it came up


hebrew and rtl language support added

Add he.yml
Heberw is a RTL(Right To Left) language wich meens that the direction of read and write is opposite from most of languages wich is LTRs.
So the html changed to support it by adding attribute dir="rtl" if it is a rtl language.

Tnx :)


Rename JUnit tests to toggle case

Overall the changes are mostly removing _ and changing the next character to uppercase. Some other transformations are as follows:

Make sure the test name starts with lowercase.
Remove backticked method names and replace symbols with words.
Remove _a_ because single characters do not toggle well and omitting still reads ok. Remove _an_ on similar named tests to make them consistent.
Make sure @Test def are on the same line for easier searching and to make consistent - only one or two.

The other thing to note is that JS vs Js is not 100% consistent. Both read fine but Js is more consistent with toggle case even if it is an abbreviation and _js_ resulted in Js. Other abbreviations may be all caps or toggle case. For the most part I changed the minimum.
The file SplittableRandom has the class SplittableRandomTest.

Should I squash the commits here?

Now or later, as you wish. But yes, they'll need to be squashed before merging.
My to-do list is fairly long these days. My estimate currently is that I'll be able to review this PR within a week.

Thank you for undertaking that work.
As it is, I don't think this PR goes far enough. The inconsistency is not just about snake_case versus camelCase, but it's more profoundly about the naming: the snake_case test methods are a relic from using the Jasmine framework, where tests were written
it("should provide foo with Int") { ... }

which was automatically translated when porting to JUnit as
@Test def should_provide_foo_with_Int(): Unit = { ... }

However, the actual JUnit naming convention for such a test, and what we would use today for a new test, would be:
@Test def foo(): Unit = { ... }

or, if foo has a problematic name like toString or clone:
@Test def testFoo(): Unit = { ... }

and sometimes if foo is overloaded, we need some more disambiguation.
If we're going to rename all test names, the point is not to have camelCase. The point is to have the above convention. Some tests are about specific "scenarios" or combination of features, and therefore have a more sentence-like method name. But the vast majority of tests should be named directly after the method they're testing.
In addition to the above, some comments:

JS should be spelled JS if in a second-or-later word, or js for the first "word", never Js. In the whole repo, the convention has been to write acronyms like that in camelCase notation.
Similarly, we write scalaJS at the beginning of a camelCase notation, or ScalaJS in the middle.
We should keep some underscores when they were clearly meant for greater separation. In particular, we should keep the _issue_1234 as is at the end of test names.

Overall, this is really a standardization effort and pretty audacious to begin with so it was clearly allot of work. What I would suggest is that less rules are better.
The @Test def foo ... and @def testEquals ... rule totally makes sense to avoid the conflict with equals for example as you point out.
Any time you camelCase, acronyms with all capitals in the middle of the phase cause a problem because the next word starts with Capital so they run together. This a case of preference. We can certainly go back through and change for example _scala_js that went to ScalaJs to ScalaJS, that is not a problem. So the rule here is that embedded acronyms should be all caps.
Another rule would be to omit single character words. They don't affect the readability that much anyway.
I would suggest that Issue2345 is just as easy to search and being at the end is plenty distinguishable. My reasoning is to not create an extra rule other than adding that to the end.
As far as bulk naming, some one my translations may not even be perfect. I think that any renaming could occur as needed when those test cases come up but trying to attack that for a whole code base would be pretty impossible.
I would suggest that we go back and change any embedded Js to JS and Ascii to ASCII and I can poke around a bit but those are the only 2 I remember. I can also do other small search and replace things like for the issue if you want to add the additional rule.
I think this is a big improvement as it makes the naming much more consistent and gives a pretty simple set of rules to content with. Also, we are very used to toggle case in Scala/Java so I think that helps to make things look more normal.

@sjrd I addressed the first review but suggested that fooBarIssue456 might be better as it would easier than having rule exceptions for using _. If you decide to go with some underscore format then I would like to go back to Scala Native and do the same so the rules are the same, as close as they can be to make it easier to contribute to both.
The second big issue that it doesn't go far enough could be addressed anytime other tests are added or modified. Basically, cleaning up as you go.

@sjrd Have you thought about this anymore?
The initial idea was to name them similar to Scala Native which I was naming in camelCase due the the JUnit port. Then if tests got shared between Scala.js and Scala Native they would have the same style. That is why I asked if you were open to the PR and there is pressure to port good bits from Scala.js along with tests.
If we do this, it will be easier for contributors to move back and forth and test names can be addressed with each PR that works on tests. Some style comments could be added to the Scala.js style guide outlining test naming. It goes a long way towards uniformity and the test names are shorter now without the underscores.

Here is the way I think about this: before, we had 2 styles of test names:

methodName (and testMethodName if necessary)
should_provide_methodName

(in both cases, with potential "qualifiers" after, for overloads or corner cases)
If we only perform a transformation into camelCase, we end up with still 2 styles of test names:

methodName
shouldProvideMethodName

We haven't actually improved anything. The shouldXyz style is still a different style, even though it does not contain underscores. The point is to get rid of one style; not to turn one style into another.
At the very least, the script should replace

shouldProvideXyz -> xyz
shouldXyz -> xyz

Ideally, when the affected lines have useless qualifiers, we could remove them as well. But the above is the minimum we should do.
Regarding the issue1234: I've really looked at the code before and after, and methodNameIssue1234 is really harder to visually parse than methodName_issue1234. It's particularly bad when the method name is a transitive verb (which is most of the time): testCloneIssue1234 reads as if it's cloning an issue. So yes, I would really like to keep the _issue1234 suffix. They help a lot in separating what is the test name and the fact that it is associated to a specific issue.
Again, the underscores per se are not the problem. It's the fact that we have several styles that is a problem.

Drive by comment: There are also two styles in linking issues:

In an additional comment
In the test name itself

I don't have a script. I used search and replace and verified each change site. There was quite a lot of hand massaging like removing _a_ and an in adjacent tests making sure they still read okay.
I can go ahead and change Issue2345 to _Issue2345 both here and in Scala Native so they are consistent.
@gzm0 I think that is a valid point - a comment at the site should be ok because if it fails you are going to look at the test anyway. I think in the ScalaNative IssuesTest the names are testIssue1234 FWIW. Those would become test_Issue1234 which I think looks okay.
I can take a few passes and remove the shouldHave and various assorted ScalaTest type names. It will get the change more in line with what you are looking for but nothing can substitute for using the Boy Scout rule when adding or changing a test and then cleaning up and renaming the other tests when people are in there making changes.
We can also do the same if porting from Scala.js to ScalaNative or visa versa. If we don't like the names, we can fix them in both places.

Example from Scala Native
[info] Starting process '/Users/eric/workspace/scala-native/unit-tests/target/scala-2.12/tests-out' on port '60516'.
[info] Test run started
[info] Test scala.scalanative.IssuesTest.test_Issue1909 started
[info] Test scala.scalanative.IssuesTest.test_Issue1516 started
[info] Test scala.scalanative.IssuesTest.test_Issue1359 started
[info] Test scala.scalanative.IssuesTest.test_Issue1239 started
[info] Test scala.scalanative.IssuesTest.test_Issue1090 started
[info] Test scala.scalanative.IssuesTest.test_Issue1155 started

If you could review org.scalajs.linker.OptimizerTest, I would like to move the _Issue... to the end of the method but not sure what the test names should be. These are the only ones like this.
Also with your permission I would like to shorten Constructor to Ctor or ctor if the test name starts with constructor.
I will still work on the Should and Must etc. and make those better.

@sjrd I made a sincere effort to simplify the test names using the rules you describe above.
Some tests I could not decipher (lack of knowledge) so I did the best I could by replacing should and must with simpler more direct English.
Some tests inherit from traits so testTestName does not scale so they became testNameClassName such as def clearList().
Overloads add the types or sometimes the parameter name if it makes more sense. e.g. fooIndex vs fooInt
Hopefully, this is at least a large enough amount of progress in a better direction so this can be completed.

@sjrd Thanks for the review - I know that had to be really hard with so many changes. I think it should be good to go now.

Excellent. Looks good now. Could you just squash the two commits into a single commit with a clean commit message, please?


Socket.IO Redis crash from notepack.io encoding exception

Socket.IO 5.1.0 caused crash on our server. It looks like its due to an exception in the new notepack.io dependency.
Error: Number is not finite
    at _encode (./node_modules/notepack.io/lib/encode.js:93:13)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)
    at _encode (./node_modules/notepack.io/lib/encode.js:286:15)

@darrachequesne should we put try catch around msgpack.encode() and msgpack.decode functions?

@artofspeed it comes down to number types that fail isFinite. So NaN, Infinity and -Infinity. msgpack-lite supports those values.
For now I forked socket.io-redis to allow custom encoder/decoder functions and wrapped notepack.io to use msgpack-lite when it throws an error during encode/decode.

I have a PR darrachequesne/notepack#3 to discuss the best way to resolve the problem.

Closed by https://github.com/darrachequesne/notepack/pull/4.


AuroraBoot: Use a pixiecore with updated ipxe for better nic support

Is your feature request related to a problem? Please describe.

Yes. Currently I cannot netboot with your AuroraBoot build as (some) rtl based nic doesn't work with the drivers in the ipxe embedded in the official netboot/pixiecore
Describe the solution you'd like

fork pixiecore(it seems not maintained)
update the the used ipxe version and build a new pixiecore package
use that pixiecore package in AuroraBoot
For inspiration I have a pixiecore with newer drivers here:
https://github.com/HasseJohansen/netboot
https://hub.docker.com/repository/docker/hassejohansen/pixiecore
And an AuroraBoot build overriding the netboot/pixiecore dependency to the above GitHub repo with this in the bottom of go.mod:
replace go.universe.tf/netboot => github.com/hassejohansen/netboot v1.21.2
I also have a docker image for AuroraBoot with updated pixiecore here: https://hub.docker.com/repository/docker/hassejohansen/auroraboot (not optimised reg. layers etc. it is quite big)
Describe alternatives you've considered

I have considered making a PR against https://github.com/danderson/netboot/, but it seems not maintained
Additional context

Good points all around and good info, we will check this maybe we can contact the upstream maintainer to see if he is willing to work with us on this


Fix code scanning alert - Unpinned tag for a non-immutable Action in workflow

Tracking issue for:

[ ] https://github.com/ksysoev/revdial/security/code-scanning/1

fixed in #9


Create automates tests for bgg_companion_api

Tests should be created for all methods within this module for all scenarios

This is being worked on here https://github.com/JDGiardino/BGG-Companion/pull/23


feat: add an option to only log error/warning and stop logging info

Relate to Feature Request for webpack plugin : new option to disable bundle-stats logger

Released - https://github.com/relative-ci/bundle-stats/releases/tag/v2.7.0, thanks again @jimblue !


Pagination per_page gets wrong value after calling next() #1201

The Pagination max_per_page value should be carried into the next Pagination object when calling next()

fixes #1201

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

@davidism the fix should be as simple as adding max_per_page=self.max_per_page, here however not sure why I got this error when running the test with the fix.
E   AttributeError: 'SelectPagination' object has no attribute 'max_per_page'

Any suggestion?

Please squash and rebase these commits onto the 3.0.x branch:
$ git rebase --onto origin/3.0.x origin/main
$ git push -f

Please squash and rebase these commits onto the 3.0.x branch:
$ git rebase --onto origin/3.0.x origin/main
$ git push -f

Done @davidism

We are checking that version 3.1.x is incompatible with us, can this fix be released in the 3.0.x series? Thanks

It's targeted at 3.0.x, which is the current release branch. 3.1 doesn't exist yet.

Great, when can this be released in a new version of 3.0.x?

Hi @davidism, wondering what is the next step here. is there something else we should do to make progress on this PR? :) thank you

The next step is for me to find time to make a release. I can't say when that will be.

@orlandobcrra I'll work on releasing this for 3.0.5 this week or next. There's just an issue with CHANGES.rst that needs updating. Thanks!

I don't think you can just merge in 3.0.x if this was based off main, the existing commits will still have main as a parent. Regardless, I prefer to rebase rather than add intermediate merge commits. If a branch was made off the wrong base, you can change it with:
$ git rebase -i --onto origin/3.0.x origin/main
$ git push -f

Oh, that was done earlier, you just carried over the wrong change header.

@pamelafox @davidism rebase done as requested. thanks


Start highlighting and acknowledging community contributions within the ChangeLog.

Please keep an eye out for community contributions so we can highlight them going forward.
As an open source software contributor on GitHub, I really appreciate if projects acknowledge my work.
We are already starting to do that in other language repos too, which is awesome!
https://github.com/Azure/azure-sdk-for-net/releases/tag/Azure.Identity_1.4.0-beta.5
More updates to follow by looking at previous commits and retroactively apply them to the existing changelogs. See some found and listed by @antkmsft: https://github.com/Azure/azure-sdk-for-cpp/pull/1874#issuecomment-797214793

Closing this draft @ahsonkhan.  We will do this in the future.  We don't need to retrofit our Changelog as we will eventually remove the Beta entries for brevity like other languages have.


AppImage crashes under Linux

Here is the output:
09:12:26.186 › homeassistant-desktop started
09:12:26.189 › Platform: linux x64
09:12:26.369 › Checking for update
09:12:26.370 › Initialized main window
09:12:26.489 › Initialized Tray menu
09:12:26.502 › Initialized availability check
[21264:1116/091227.282662:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
[1]    21264 trace trap (core dumped)  ./Home-Assistant-Desktop-v1.5.2-linux-x86_64.AppImage
If i run it with  --no-sandbox its working fine

I'm seeing this too on Ubuntu 22.04.1.
Running it through gdb doesnt produce a useful stacktrace

This issue is fixed in last update


Add savant color light with new profile

 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.


Add license, url, python_requires, and PyPI classifiers to setup.py

Adds various metadata which can be read by PyPI and others. Should have no effect on functionality, other than making it easier to use for 3rd-parties.

Heya, any comments about this or something I should do to get it looked at/reviewed/merged?

@jaehlee @Sohl-Dickstein heya! Any thoughts on this, or would it be possible to do a quick merge?

Final bump - is there any interest in merging this?


wac-parser not checking for type declaration conflicting with previous export

The following wac:
package test:comp;

let foo = new foo:bar {};

export foo as i;

interface i {
}

causes a panic in wac-parser:
thread 'main' panicked at crates/wac-parser/src/resolution/ast.rs:355:9:
assertion failed: prev.is_none()

This is because wac-parser is not emitting an error for the type declaration conflicting with the previous export.

I have a fix for this in the overhaul of wac-parser I'm doing to migration to wac-graph.

The new error:
error: failed to resolve document

  × type declaration `i` conflicts with a previous export of the same name
   ╭─[foo.wac:7:11]
 4 │
 5 │ export foo as i;
   ·               ┬
   ·               ╰── previous export is here
 6 │
 7 │ interface i {
   ·           ┬
   ·           ╰── conflicting type declaration `i`
 8 │ }
   ╰────


Remove backslash (+ indent) from string literals

When a backspace at the end of a line of code was used as continuation character inside a string literal, an indentation at the next line would unintentionally become part of the string itself.
This commit has removed the backslash, the line break, and the indentation from those string literals. Clang-Format has taken care of splitting the literals over multiple lines properly.
It affects a QuadEdgeMeshEulerOperatorDeleteCenterVertexFunction debug message, an exception message of Versor, and various exception messages from "Numerics/Statistics".

Thanks for doing this Niels. I'd say this is a STYLE change, though: the basckslash/indent do not introduce any bug.
I know we'll need to wait for another round of CIs, but I'd be for changing the commit subject and PR prefix before merging this. Thanks.

Thanks for doing this Niels. I'd say this is a STYLE change, though: the backslash/indent do not introduce any bug.

Thanks for your suggestion Jon, but this PR does fix a few mistakes (these extra spaces are erroneously there), and it does change the behavior of the code. Because it changes debug output and exception messages. So I believe it's not just a matter of style. I think it's a bug, although I would agree that it's a very little bug. Hope it's OK to you.

Thanks for your suggestion Jon, but this PR does fix a few mistakes (these extra spaces are erroneously there), and it does change the behavior of the code. Because it changes debug output and exception messages. So I believe it's not just a matter of style. I think it's a bug, although I would agree that it's a very little bug. Hope it's OK to you.

e.g. a typo in a word that is part of a message is also erroneously there, but does not introduce a problem with a result of the software. Here the situation is the same: the exception message or debug output might be incomplete or be difficult to read, but it does not affect any computation or result. So I am sorry, but I do not consider this a bug.

@jhlegarreta So do you really really want the commit subject line to be changed from "BUG" to "STYLE"? If you insist, I will adjust the commit text (albeit "under protest", because I think a STYLE commit should not change the runtime behavior).

pull request distinguished between

That is a useful distinction.
@N-Dekker please merge when ready.

please merge when ready.

I always click the button "Ready for review" to indicate that it is ready. GitHub does not offer any other way for me to approve a PR that I submitted myself.

I clicked "ready for review" button. I was impatient 😄

I clicked "ready for review" button. I was impatient 😄

@dzenanz It isn't really the most exciting PR of the year, is it?  😸 😸


Fixing problem with accepted categories not present in current data

This should fix the problem we have seen today in the last PoC.

@saleiva @AbelVM

Thanks!


Scripts show as <node_internals> while debugging with node 11

Debug a .js file with no sourcemaps using Node 11
Hit a breakpoint
See that a new editor is opened with the script that says "read-only core module"

I will just revert https://github.com/Microsoft/vscode-chrome-debug-core/commit/b5a4d5436d3acd30369f167d48c59bcadebbcb12.

Not sure the PR fixes the bug. Here's what I did:

Build your branch
code.sh to open VS Code
Write a JS file like so and run node --inspect-brk index.js
No breakpoints are hit. I ran it a few times and certain times the breakpoints are hit but the debugger did not pause (continued execution).

node -v is v10.12.0.


[FLINK-2549] add topK operator to DataSet.

The topK operator is implemented with mapPartition() followed by reduceGroup(), each map tasks select top k elements, and transfer to singleton reduce task(no group() before reduceGroup()), and then select top k elements in reduce task.
The main part of this implementation:

An out-of-core self managed memory based PriorityQueue implementation.
Use runtime resources to build PriorityQueue for UDF. topK is not real 'native' operator actually, it contains UDF which use self managed memory based PriorityQueue to select top k elements.

This looks super impressive and very well tested.
The way that the operator is integrated into the system needs some improvement, though. The problem is mainly how the managed memory is obtained.
The MemoryManager's memory is shared among all concurrently running tasks. This implementation takes up to half the total memory, which will cause programs to crash that have other memory consumers in the same pipeline. The tests here run, because the operator is executed in isolation, with no other memory consuming operators in the test program.
Memory consumers need to be known to the Optimizer (in the program generation) to compute what maximal fraction of memory a certain consumer may request. That value is part of the Task's configuration and used by the memory consumer to obtain the right maximum amount.
Integrating operators into the optimizer's planning is a bit tedious and not as easy as it could be (we did not get around to refactoring this so far, unfortunately). Maybe we can add some tooling that would mark a UDF as MemoryConsuming and would in that case expose a Memory Allocator that returns the right amount of memory.
What we could do is the following: I will try to get to refactoring some of the Managed Memory Allocation abstractions (we need this anyways for more components) and then expose a MemoryAllocator in the runtime context, which is accessible if a user-defined function has been annotated as a memory consumer.
This may take me two weeks (I am currently in the mids of working on the streaming windows), but if you don't mind letting this rest for some days, I think that is the cleanest approach.
The other parts of the code look good, so after I finish my part, it should be a simple rebase of the TopKMapPartition function and the TopKReducer, and then this is good to merge.
What do you think?

Thanks, @StephanEwen , I'm totally agree with you about the memory allocation. Actually i tried to understand the memory allocation logic and make UDF consumer part of it, but it turns out that's not easy and break many things, it's better to leave the refactor job to someone who totally understand it, like you. I would wait for you refactor work.
BTW: It take half of the total memory as upper boundary, but i guess it does not make any different :)

Hi, @StephanEwen , is there any progress of Managed Memory Allocation abstractions for UDF? Not only about TopK operator, i think it's also very important for users or DSLs to build more robust and efficient applications. For example, in Table API queries, as the data schema is predictable during each phase of processing, we does not need to create real Row object, just store the binary data in self managed memory, and use the offset to read Row fields. So all the intermediate data is store as binary on self managed memory, no need to create lots of Row object and its fields object anymore, which should be more robust, memory-efficient, and with better performance.

@ChengXiangLi Sorry for letting you wait, I have not forgotten about this pull request.
There are two things in your comment:

Exposing Managed Memory to UDFs (this pull request), which is much more convenient than going through the implementation of a deeply integrated operator.

Efficiency for APIs like the Table API. The Table API works on managed memory already, since it sits on top of Flinks join/sort/etc. What you are hinting at is to have a lower level interface where functions gets the memory segments, rather than the row objects, and directly works on the memory segments. That has been a long which of mine as well, but that involves having a separate type of functions that support working with memory segments. Plus more, to handle records that are too large to fit into individual segments.

I am still onto point (1). I aimed a bit too high with how I wanted to abstract that, but will continue.
I would love to see point (2) at some point. If you are eager in driving point (2), I'd be very happy. We should probably have a chat and get this designed, as it involves quite a few things (exposing other abstractions, spanning records, etc).


Tags

This completes and extends work originally performed by @taskboy3000 in #24.
New:

Adds a few basic tests checking for tag-file creation
Tag-detail pages' filenames no longer subject to URI encoding (allowing for use of UTF8 in tags)
Adds tags.tt to the files created by plerdall --init
Adds basic documentation
Minor tweaks and adjustments

Ship it!
Looks reasonable and it's a lovely feature.  Looks like you are using UTF-8 when reading blog source so emojis may work that way?  shrug emjoi

Yes, emoji work as tags, in my testing (though there's no formal testing at this time for that case).


Feature buildtest rt --all to report useful fields

You are on the right track. Good job!

Thank you!!


Cannot access package name or class name separately from type declaration

Right now, the qualified name string (JavaParserTypeAdapter.getQualifiedName()) separates packages and classes with ..
{packageName}.{packageName}.{outerClassName}.{innerClassName}.{innerClassName}
This doesn't let us access the namespace separately from the class name. There should be public methods such as getPackageName() and getClassName() to allow access to these separately.
We need this to represent the type of a node in a specific way for our application, so we want access to the constituent parts in order to format them the way we need.

I'm working on a PR to add getPackageName() and getClassName() to any place that also uses getQualifiedName().

Looking forward to the PR!


CB-8051 [webOS] Fixes webOS SmartTV detection

Improved detection method, as used by EnyoJS.

In general, I prefer for people to git rebase instead of git merge. The two tracking branch merges in this PR are noise that no one should see.

The order of webos in the grunt was just mimicking the order it was in the compile task above it (which oddly did have the webos entry this task was missing). As for the merge/rebase stuff, thanks for the information. I'll do my best to follow that format; definitely prettier, heh


Fixed bug causing $.proxies.baseUrl to be ignored in JS proxy

Fixed bug causing $.proxies.baseUrl to be ignored when requests are sent
by the JS proxy

Nice!


cluster: fix NACK when using STATIC Service with PASSTRHROUGH

Fixes https://github.com/istio/istio/issues/39736

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
117f47d99a0cea358fb10dac93feaee12024fa84
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

https://github.com/istio/istio/pull/39757 seems similar issue but very different solutions... do we need both @ramaraochavali ?

@howardjohn I thought about setting clusterLoadAssignments to nil while fixing it in other PR. But I think this seems a config issue - for service entries with Resolution as STATIC/DNS - some one is setting PASSTHROUGH Load balancer. By removing the cluster load assignments, we are allowing this cluster to route traffic to any IP that client chooses which I felt incorrect. So I went with ignoring DR and setting default LB model. If some one wants PASSTHROUGH why not set resolution None.  This happened in this case probably because of wildcard host in DR - So I am bit concerned about allowing any IP traffic with STATIC/STRICT_DNS. WDYT?

I added more comments to other PR. Please see if that makes sense. I have put hold on both the PRs so that we can discuss.

@howardjohn I thought about setting clusterLoadAssignments to nil while fixing it in other PR. But I think this seems a config issue - for service entries with Resolution as STATIC/DNS - some one is setting PASSTHROUGH Load balancer. By removing the cluster load assignments, we are allowing this cluster to route traffic to any IP that client chooses which I felt incorrect. So I went with ignoring DR and setting default LB model. If some one wants PASSTHROUGH why not set resolution None. This happened in this case probably because of wildcard host in DR - So I am bit concerned about allowing any IP traffic with STATIC/STRICT_DNS. WDYT?

STATIC is essentially what a standard ClusterIP service is. So by that logic we should not have PASSTHROUGH for these services either it would seem, which I think would negate all use cases?
I do agree it's a strange usage - I think the docs for PASSTHROUGH have quite a few caveats listed

STATIC is essentially what a standard ClusterIP service is. So by that logic we should not have PASSTHROUGH for these services either it would seem, which I think would negate all use cases?

The only difference I can think is ServiceEntry has "Resolution" type None which users can use. However for ClusterIP service there is no such option - unless we ask customers to create headless for usecases like pod->pod with subsets as I mentioned [here](3 minutes ago)
I do agree it is grey area. I think the reason I think we should not support for STATIC/DNS is right now the cluster is Nack - so no one would have used. But for K8s, people would have already used it as I mentioned in the comment. So I think we should continue to support it.

STATIC is essentially what a standard ClusterIP service is. So by that logic we should not have PASSTHROUGH for these services either it would seem, which I think would negate all use cases?

The only difference I can think is ServiceEntry has "Resolution" type None which users can use. However for ClusterIP service there is no such option - unless we ask customers to create headless for usecases like pod->pod with subsets as I mentioned [here](3 minutes ago)
I do agree it is grey area. I think the reason I think we should not support for STATIC/DNS is right now the cluster is Nack - so no one would have used. But for K8s, people would have already used it as I mentioned in the comment. So I think we should continue to support it.

Headless vs ClusterIP is the same as NONE vs STATIC/DNS, IMO. And we do have conversion logic between those (used in MCP, for example). I am pretty against having different logic for the two cases

I am fine with this fix. My only reservation is about user unknowingly allowing a PASSTHROUGH access for DNS/STATIC type of SE. But if you think that is user's problem - Let us move forward with this.


masking on tensor.data?

Hi,
I noticed that you were masking out the padded tensor by assigning value to tensor.data.
attn.data.masked_fill_(attn_mask, -float('inf'))

Is this correct?
Based on the discussion here, shouldn't we assign values to tensor itself, instead of tensor.data? In this way, the history of the gradient can be tracked.

Maybe you are right. However, even if I change that like what you say. I can't run into meaningful results. The generated text of beam search is wrong. And the accuracy is not a reliable indicator. So do you have right generated text?

I didn't actually run the code. I was just curious about the implementation and notice this potential issue.
Just curious. When assigning values to the Variable itself, have you tried assigned it to 0, instead of -float('inf')?

It is wrong to assign 0 because a softmax layer is following. If you assign that position to 0, then you would get exp(0)=1 in the masked position. But it should be float('-inf') which leads exp(flaot('-inf')=0.

Hello @chihyaoma, thanks again for the notice. with the newest api, I have avoided to manipluate on the data itself. Please take a look.
Hello @ZiJianZhao , thanks for explanation!
Thanks,
Yu-Hsiang


Make fast build CMake option, Fix Travis Linux/Mac builds, Add AppVeyer Windows build

Closing. Abandoned.


Feature request for Explorer panel

I tried to adjust indentation of the explorer panel in vscode. But with the configuration files I didnt had any luck. In current setting when with huge file structures, I find it hard to differentiate between folders and files since the indentation level of folders and files in it is so small for me. It would be so nice if this can be taken into account for next configuration settings.

/findDuplicates


missing project target for macOS

I tried building ASN1Decoder with carthage but there is only a single iOS target setup and so it fails for macOS. It should have two targets and two schemes.
(see https://github.com/Alamofire/Alamofire for an example)

Fixed! Thanks for the hint!


Update MD file on new branch 2017-12-07_09-40-19

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

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.


[Enhancement] (nereids)implement showDatabaseIdCommand in nereids

showDatabaseId command is supported in legacy planner but not in nereids(new doris fe planner). you need implement the following showDatabaseId command in nereids:
unsupportedshowDatabaseIdStatement
SHOW DATABASE databaseId=INTEGER_VALUE

pick it


refactor: Add From conversion from ExtensionId to ExtensionSet

This case comes up too often to keep writing out ExtensionSet::singleton

Can you replace the current usages with it?
It may come handy to replace explicit ExtensionSet parameters with impl Into<ExtensionSet> in places like
FunctionType::with_extension_delta.

Good point! I'll update the PR


Remove remove-six-compat (UP016)

See discussion in #2049.

In which PR?

(Let's rebase it, I'd like this to be a separate PR.)

:-( it was and will be useful for me in the future (we can drop Py2 next year)

@spaceone - Sorry about that :( I recommend using pyupgrade for this check. I felt like the implementation in Ruff was complex and under-tested since it's a rarely-run rule.


Hide updateState() from end user API

AbstractVersionableEntity exposes updateState() as public. Even though, it has the method marked @Internal, there is a great risk of misusing the API via end users.
The reason for exposure is documented in AbstractVersionableEntityTest.haveUpdateStatePackagePrivate() as
@Disabled // The `updateState` method was made public to be accessible from `testutil-server`

Test utilities should update entities via reflection. Please hide the method and update test utilities.

@armiol, FYI.

@vlad-lubenskyi, can this issue be closed, assuming #784 is merged?


Real-time doesnt work in managed package

Hi,
I have deployeed DLRS to a managed package and then set up the rollups and configured them to run realtime / user basis. Trigger is already deployed (shows as hidden).
Roll up is active and Set to run in real time (trigger is deployed by package)
When I set this up in a different Org that installed the trigger directly, it DOES work in real time but not via the packaging ?
ISSUE:
Trigger doesnt fire on user / real time or system / real time basis - only works on full calculate or schedule calculate basis.
Howe can we get this to run in real-time ?
Rgds, Dave

Curious why you are trying to put DLRS inside of a managed package vs. installing it separately?  You can call DLRS rollups from your own code/triggers instead of trying to package the DLRS generated triggers inside your namespace.

Thanks for your comment @JimBTek - for clarity, we need to install the DLRS directly into Target Org (as a pre-requisite for package install) before we can install our package due to dependency. When both packages are installed, we are still setting up each rollup and activating them, but the program doesnt ask us to "manage child trigger" anymore. I assume that is because it is already deployed - it just shows as "hidden". Does that help explain ?

@DaveT-CTS is this still an active item for you?

Hi, Yes it is unfortunately. We have had to create flows to manage around this but not ideal.

I'd be open to spending some time on it if you'd still like to try and make it work.

Cool, do you have any additional details? I don't get a lot of where it might have broken down looking at what you have above.
I'm trying to imagine where it would have problems but nothing obvious stands out. Do you know if it works correctly in the namespaced development environments and only fails when packaged and installed?
I might have to use a sacrificial namespace to build and test this.

We had removed (commented out the code) in the packaged namespace so that we could deploy without the DLRS dependency because of the issue. I will have to look into adding it back temporarily but can also provide some more details from a test org we have deployed this into. Let me come back to you.

Hi again (sorry - whats your first name?)
I have deployed this into a test org that we user and want to provide you with a user login and some more info - whats your email so I can assign user login to you?

DLRS real-time trigger documentation issue.docx
I added this document to show what I am doing


ClusterReset is renamed and moved out from JedisCluster

Ah you may want to also resolve conflict too.

@HeartSaVioR I do agree! Please check #1673 for 2.10.

Merged into master.


Enables more carping of diems with new --carpe-diem flag

Unburden yourself from the yoke of backwards compatibility with the new --carpe-diem flag. Press save and a major version bump will automatically be performed for you.

Cool stuff! This is why I love open source

Likewise! All human struggle and effort in the technical realm has ultimately enabled us to created this.

I also like that I submit this PR on a Friday night, and that it gets merged within an hour. 🤘


Create question_10

I did import pickle, within the function
Yes, I tested it
However, this is only the first part


Fix graveler to work with empty key

Allow empty key ("" / not nil) to be kept in Graveler. It fix issues related to import of directory marker into the root.
Note that this change upgrade Graveler's pebble implementation.
Fix #3588
Fix #4909

I have some concerns about backward compatibility, how can we make sure old sstables are respected?

Run latest release of lakeFS, uploaded, committed changes. Run the above version and it works. Assumed we had to read sstable with commit metadata.

Also - consider adding the empty directory marker to our esti import test to cover the bug fix.

Will add soon - thanks.


Talks level only displayed on schedule but not inside individual listing

On the schedule, on top of each talk, we display the level (which I assume is Python level and not domain level). But when you click into the talk to see more details, you no longer see the level of the talk. I think both the Python and domain level should be listed before the Abstract.

done :)


Fix TADA_HarmonizeSynonyms issue

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

Comparison is base (7e0aaeb) 48.76% compared to head (f7ff138) 46.48%.

:exclamation: Current head f7ff138 differs from pull request most recent head a309db7. Consider uploading reports for the commit a309db7 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #395      +/-   ##
===========================================
- Coverage    48.76%   46.48%   -2.29%
===========================================
  Files           14       14
  Lines         3006     3014       +8
===========================================
- Hits          1466     1401      -65
- Misses        1540     1613      +73

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

I was able to run the WIDNR example (had to substitute the site id provided in line 4 in TADA_DataRetrieval() as object 'run_details' was not found) and with your changes, the number of rows with non-NA values in TADA.ResultMeasureValue was the same in the harmonized and non-harmonized data sets.


Mask Initialization Issue: Extra Digit Added During Initialization

Describe the bug
During the initialization of the input mask, an extra digit is being added. Specifically, when the mask is configured as 7-999-999 and the initial input value is 7-7__-___, after initialization, the value becomes 7-77_-___. This behavior is unexpected and seems to indicate a problem in the mask initialization process.
To Reproduce
Steps to reproduce the behavior:

Configure the input mask with the following settings:const maskConfig = {
    mask: '7-999-999',
 };

Initialize the mask with an initial value of 7-7__-___.
Observe the value after initialization, which changes to 7-77_-___.
Expected behavior
The value should remain 7-7__-___ after mask initialization.

If your mask includes fixed digit 7, I'm pretty sure you should set value of your input field without it in mind i.e. if you want the result to be 7-123-456, you should set your value to 123456.
I believe this is intended behavior.


Business Continuity - OpenBaton

Hello,
Is there any Business Continuity mechanism for OpenBaton itself? Is there any way to scale or make redundant for network deployments?
BR.
Onur

Hi, I answer you reusing an answer of my colleague on our Gitter channel.
We are not providing any specific setup for Business Continuity or High Availability out of the box. But regarding HA, we know for sure that every main component can horizontally scale (NFVO, all VNFMs, all Plugins) and the non-OB components (MariaDB, rabbitmq) provide some clustered solution for that purpose.
If you need more info please write to<EMAIL_ADDRESS>or use the Gitter channel https://gitter.im/openbaton/NFVO.
BR,
Marcello


.NET sdk provision should enable LTS + Latest stable when they do not match

we should be able to provision LTS and also latest stable SDK when we have the 7, 9, 11 releases of .NET SDK. Doing so allows us to let users get deeper into latest C# and all good tech in there without breaking any previous work.

@mavasani am I capturing it correctly?


feat: Create a screenShotWasTaken notifier

Description
Create a callback that is executed each time a screenshot is taken whether or not screenshot support is blocked

v1.0.0-beta.2


Issues when adding more numbers and items are disappearing when random scrolling

Hi , Scroll is not working when adding more numbers to wheel. And also after some random scrolling items are disappearing suddenly(Please refer the below screen shot).

Hello, did you find a fix for the scroll bug?


bots: Fix unit tests not running in Vagrant.

test-bots would not run in Vagrant, displaying
the error "ValueError: no such test method in <class
'bots_test_lib.BotTestCase'>: runTest" This was due to
the BotTestCase class inheriting from the TestCase
class, even though it was not a unit test on its own.
This commit removes the inheritance of TestCase and
specifies test_define as the runTest method in
TestDefineBot.

Automated message from Dropbox CLA bot
@derAnfaenger, it looks like you've already signed the Dropbox CLA. Thanks!

This now enables me to run the test-bots in my local environment using python 2.7.9 (debian stable).

I appended a commit to simplify the sample test case, since it gets only executed successfully in Vagrant with this commit.

Make sense; merged, thanks @derAnfaenger!  Let's chat about how to further simplify the test framework tomorrow.


Access token from Okta too long

Background
On 8/22, we saw a group of users at a very large organization get a 500 every time they tried to log in.
After much investigation, we determined that it wasn't Akamai or the WAF blocking these requests; the access_token from Okta wasn't being sent in full so SimpleReport couldn't parse it. These users were part of so many distinct facilities (40+) that the bearer_token became untenably long (8000+ characters) and SpringBoot blocked the full header from being sent as part of the request.
Further testing uncovered the server:max-http-header-size configuration field, which allows you to set a maximum header size. At this point, that works for environments without Akamai enabled - the full bearer token is indeed being sent from Okta. However, our frontend still isn't parsing that token correctly; the working theory is that the access_token isn't being set in local storage by the time we attempt to read it.
Action requested
The single action requested for this ticket is to fix the asynchronous issues in app.tsx and index.tsx such that we're not caught in a reloading loop for these extra-long bearer tokens.
Acceptance Criteria
Users with many facilities assigned (40+ distinct Okta groups) are able to log in and use SimpleReport.
Additional context
Current work for this ticket is stored in https://github.com/CDCgov/prime-simplereport/tree/emma/big-org-problmes.
@emmastephenson has her Okta Preview groups configured in both test and pentest to trigger the issue if you need a tester.
The two breakpoints we appear to be looping through on the frontend are:
https://github.com/CDCgov/prime-simplereport/blob/79a8ed76b4e8bdfc236df6cbc9e1f8e759f74035/frontend/src/index.tsx#L88-L88
https://github.com/CDCgov/prime-simplereport/blob/79a8ed76b4e8bdfc236df6cbc9e1f8e759f74035/frontend/src/app/App.tsx#L72-L72
When debugging it's clear that the access_token is being set, but it's evidently not being picked up by the localstorage call in app.tsx. This triggers our error handler in index.tsx, causing the loop.

We need to add some content to our support/onboarding documents letting users know that there's a cap on the number of facilities any user can be assigned to.
We need to either figure out how to get the bearer token to pass through unscathed or change how we're doing authentication.

https://www.simplereport.gov/app/#id_token=eyJraWQiOiJFQ2hKcDFWNTBhSldmdURlNE04MUV1cWN2dD[…]i1kNWU0ZjQwYzg3NWYiLCJTUi1QUk9ELVRFTkFOVDpUWC1BY2hpZXZlL
^ This link will demonstrate the breakage!

Another NB that this will still not completely unblock the headers, because Akamai restricts the length on top of our Spring restrictions. So we'll need to chat with CDC about changing those restrictions in Akamai before the fix works in deployed environments.

Closing because this is an outlying use case. Will re-open if it becomes an issue.


Standard AWS SSO logins dont work when this extension is installed

When attempting to login to aws using aws sso login I get the following error message. This extension assumes that the user will only use assume to perform logins. In some situations I need to use the AWS CLI to login via SSO

@wayne-folkes which situations require the AWS CLI for SSO? Ideally I can help you migrate those use cases to use the Granted CLI, as unfortunately the login flow has to be initiated by Granted for the browser extension to be able to detect the code.
Have you tried the Granted credential process recipe?

@wayne-folkes which situations require the AWS CLI for SSO? Ideally I can help you migrate those use cases to use the Granted CLI, as unfortunately the login flow has to be initiated by Granted for the browser extension to be able to detect the code. The AWS CLI doesn’t have the same browser extension communication feature that Granted has.
Have you tried the Granted credential process recipe?

Yes. After submitting this issue I created a profile that uses the credential process and that worked. My use case was that I am using a Juypter Notebook inside of VS and I need to have my credentials created inside of the notebook so I can make my API calls.

Fantastic to hear. I’ll close this but feel free to open a new issue if you encounter a use case in future that requires you to use the regular AWS CLI for the SSO login flow.

@chrnorm it doesn't involve the AWS CLI, but another case where this issue is encountered is when using Granted headless (DefaultBrowser=STDOUT) on a remote server. So I think the core of this issue is still valid -- the extension currently only works if local Granted is the exclusive thing you are ever authorizing through the device code flow.
Even if it can't prevent phishing entirely, I think a mode of the extension where it automated the button clicks for verified Granted codes but still left them clickable in other cases would be helpful. By automating the common case, the un-automated cases would be left to feel atypical, and users would be less conditioned to click through them without paying attention.


[BUG] Page becomes slow/unresponsive after plugin adding/editing/removing

Description
On django-cms projects with a large number of sub-sites, editing/adding/removing/changing position on plugins freezes the browser for around a minute. On some devices the page crashes or becomes unresponsive indefinitely. We identified this to be caused by diff-dom library struggling with large amounts of html elements when trying to refresh the page's toolbar content. After a plugin is added or modified or removed, the page fetches new html data, then using diff-dom it creates a diff and applies it to the old toolbar html elements. However, the diff creation process takes unusually long when the toolbar contents contain a large amount of html elements. In our case, we have a django-cms project with 382 sites in it, and this process takes about 50 seconds. Increasing the number of sites increases the time exponentially.
We have a fix for this and will create a pull request shortly. If it's up to django-cms' standards, you can accept it, otherwise, feel free to suggest changes or add any of your own.
Steps to reproduce

Create a django-cms project with 400 sub-sites.
Create a page in any of the sites and add any plugin to it. We commonly tested this using the text plugin.
Confirm that after the plugin is added, the page stays greyed-out and unresponsive for around a minute. On some devices, the browser may crash.

Expected behaviour
Refreshing the content after plugin addition should not take more than a few seconds.
Actual behaviour
Adding a plugin on pages of projects with large amount of sites freezes the page for around a minute on some devices, or crashes the browser on others.
Additional information (CMS/Python/Django versions)
django-cms version 3.7.4
django version 2.2.17

Hi @nichoski I see you are using release 3.7.4, do you think you could also try to upgrade to 3.9.0rc2 to test? (and then maybe send a PR for this version if you are working on one?)

@goutnet Unfortunately we don't have the option to upgrade the project's django-cms version to 3.9. Could this be backported in to a 3.7.x branch? Here is the pull request to develop:
https://github.com/django-cms/django-cms/pull/7070


Combine allele frequencies between exomes and genomes and support a single FAF

By special request from Heidi: "A critical use of gnomAD by the clinical community is to rule out pathogenicity using allele frequency. However, groups need to have an FAF from the combined exomes and genomes to enable this."

Just to confirm, this will be v4 exome numbers combined with v3.1 genomes?

Will discuss in Council meeting on Feb 23, but the idea is to combine v3 genome AFs with v4 exome AFs into a single number. Will need to discuss any other scientific or QC considerations before simply mashing numbers together.
Also relevant: is v4 officially exomes+genomes, or just exomes? Has implications for QC pipeline.

Need to figure out whether to do this as a separate step after running frequency code individually on exomes and the existing genome frequency table -- but in theory this should be straightforward. Maybe 1 week?

v4 is officially both exomes and genomes.


Fix: swapped variable names within kubeinit_okd_dependencies

Swaps the variables within kubeinit_okd_dependencies. Client was given the Installer's URL, and vice versa.

@Bilal-io thanks a lot for this fix, there is a small nit in the commit message, the change looks good to me.
http://docs.kubeinit.com/contributing.html#linting-commits

@ccamacho is this better?

hi @Bilal-io it's the commit message (the title) not in the PR, you just need to amend it and force push it 👍  thanks again.

@Bilal-io almost perfect, but Fix needs to be lowercase and it should be good to go.

Hmm I think it went back to the old commit title.
Instead of:
Update main.yml
The commit's title should be:
fix: swapped variable names within kubeinit_okd_dependencies
(The pull request can have any name)
This is because the changelog is rendered automatically, based on the commit's category

git commit --amend didn't seem to work either.
Can you abandon this PR? I will recreate it.

Sure thing 👍


State vector simulator faced with non-unitary operations

Right now, the state vector simulator will stochastically choose a path when it encounters a non-unitary operation (measure, reset, noise). You can get into deep trouble if you e.g. put in a measure operation and then expect to have a state vector that means anything in isolation.
@Strilanc has said: "I regret calling it simulate instead of e.g. sample_final_state_vector. Exactly this kind of ambiguity."
Some of the pauli expectation functions do checking that you don't have any measurements which will likely mess them up in a major way.

should we have a method or toggle that will only do pure state dynamics. We can tell people to use this and not shoot themselves in the foot unless they know what they're doing and want a statistical sampling of possible state vectors
should we have a method that starts as state vector but will expand into a density matrix if you do a non-unitary operation? This might make sense in the context of #3240 where you want to do a long pure-state simulation and then reset/deallocate a bunch of qubits
should everyone just use quimb which never has any of these problems?

Talked offline, it seems there are a few things we could do.

Remove prng from simulators and pass them into the functions that are nondeterministic. This way it is explicit whether the operation you're doing is pure or not. Effort: small, but backwards incompatible.
Refactor Operation to come in a hierarchy e.g. Operation > ChannelOperation > MixtureOperation > UnitaryOperation > StabilizerOperation, and have e..g. StateVectorSimulator.simulate_pure only allow Circuit[UnitaryOperation]. Effort: large, value TBD.
Allowing DensityMatrixSimulator to use SV or possibly even stabilizer first and promote to DM as necessary seems like a good optimization and I don't see much in the way of it. It's largely independent of everything else here, should be its own issue. Effort: medium.

xref https://github.com/quantumlib/Cirq/issues/1740

Proposal in cirq cync:

simulate should still work for non-unitary operations
Possibly add a field into the result returned
Go ahead with #1740 to add sample_final_state_vector()

Not high-priority since this only affects certain use cases of specifically instantiation simulator and calling simulate() with non-unitaries.

@mpharrigan For item 2 in your list, would you want that to be a special simulator used only by the mux module (e.g. final_state_vector, final_density_matrix, etc, or should DensityMatrixSimulator itself be endowed with this functionality?

I'm not sure. I was just brainstorming.

@mpharrigan I created an implementation https://github.com/quantumlib/Cirq/pull/4488 for item 2, but it was decided in cirq sync that there are not any big real-world use cases for this feature, and so this is not worth the cognitive overhead. So I closed the PR. If there is a real-world use case then I can reopen.

Sorry for leading you astray. Thanks for opening the PR anyway.

What's the most current design proposal? Could it potentially introduce backward-incompatible changes?

If i'm reading this correctly, the proposal was

simulate should still work for non-unitary operations
Possibly add a field into the result returned
Go ahead with #1740 to add sample_final_state_vector()

(1) is a no-op
(2) was tried by @daxfohl but then it was nixed
(3) is captured by #1740
so maybe this issue is redundant?

Closing this for now per comment above, but please feel free to reopen if you think that's a mistake!


Add RBAC feature for Migration (v2v).

To be used together with the v2v PR: https://github.com/ManageIQ/miq_v2v_ui_plugin/pull/417
Problem: to make Migration work API access is needed. For that API other features need to be enabled. I don't know what those features are. This is something that probably needs to be documented so that the users don't get confused.
Before

After

Ping @mzazrivec, @dclarizio, @h-kataria : I usually review these so I don't know whom to ask to review this one ;-) Can you take a look, please?


eos_design/Network_services ospf vlan interface authentication message-digest missing command

Issue Summary
In eos_design - Network services tenant interfaces configuration of ospf authentication with message-digest, the output configuration for vlan (svi) interfaces is missing "ip ospf authentication message-digest"
YML example :
TENANT_A:
  vrfs:
    BLUE:
      ospf:
        enabled: true
        process_id: 400
        bfd: true
        redistribute_bgp:
          enabled: true
        nodes:
          - s1-leaf1
          - s1-leaf2
      svis:
        104:
          name: ospf_test
          tags: [ DC1_LEAF1 ]
          nodes:
            s1-leaf1:
              ip_address: <IP_ADDRESS>/29
            s1-leaf2:
              ip_address: <IP_ADDRESS>/29
          ospf:
            enabled: true
            point_to_point: false
            area: <IP_ADDRESS>
            authentication: message-digest
            message_digest_keys:
              - id: 1
                hash_algorithm: md5
                key: SDGASHERASEGRWH

Resulting configuration  on s1-leaf1:
interface Vlan104
   description ospf_test
   shutdown
   vrf BLUE
   ip address <IP_ADDRESS>/29
   ip ospf area <IP_ADDRESS>
   ip ospf message-digest-key 1 md5 7 SDGASHERASEGRWH

The expected output configuration would be :

interface Vlan104
   description ospf_test
   shutdown
   vrf BLUE
   ip address <IP_ADDRESS>/29
   ip ospf area <IP_ADDRESS>
   ip ospf authentication message-digest
   ip ospf message-digest-key 1 md5 7 SDGASHERASEGRWH

### Which component(s) of AVD impacted

eos_designs

### How do you run AVD ?

Ansible CLI (with virtual-env or native python)

### Steps to reproduce

_No response_

### Relevant log output

_No response_

### Contributing Guide

- [X] I agree to follow this project's Code of Conduct

I will submit a PR to fix this

PR #2727 has been open with proposed fix


Move to TypeScript / TSDX

The question is how we want to handle the input typings for amounts and decimals. With the current typings only native BigInt and jsbi instances will be accepted in a TS project and all other libraries will have to convert to string or cast. The options as I see it are:

Provide typings for a subset of the most popular BigInt / BigNumber implementations
Standardise around native BigInt only
Accept any

Let me know if there's another alternative though.

Just remembered this issue: https://github.com/aragon/token-amount/issues/3
I think it could make sens to skip this now, and go directly for BigInt-enabled environments (i.e. return a BigInt from value()).
Also I don’t think we need JSBI anymore, even if we decide to keep targeting <ES2020 environments for a bit, since TS can transpile BigInt.

Just remembered this issue: #3
I think it could make sens to skip this now, and go directly for BigInt-enabled environments (i.e. return a BigInt from value()).
Also I don’t think we need JSBI anymore, even if we decide to keep targeting <ES2020 environments for a bit, since TS can transpile BigInt.

Thanks for the suggestions! I've made the original set of changes and will address the removal of JSBI in a separate improvement.


發生問題

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce
OS Version: Microsoft Windows NT 10.0.22000.0
IntPtr Length: 8
x64: True
Date: 2021/10/18 上午 02:24:14
Exception:
System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. 系統找不到指定的檔案。
File name: 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
at Wox.Infrastructure.Storage.JsonStorage1..ctor()    at Wox.Infrastructure.Storage.WoxJsonStorage1..ctor()
at PowerLauncher.ViewModel.SettingWindowViewModel..ctor()
at PowerLauncher.App.<>c__DisplayClass13_0.b__0()
at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
at System.Windows.Application.OnStartup(StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1_0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
✔ Expected Behavior
repaire
❌ Actual Behavior
back to specific time point
Other Software
No response

Could you attach a full bug report file?
Right-click on the tray icon and click Report Bug. Then drag-and-drop the generated file into the GitHub comment to upload it. Thanks!

after update to the latest version, no more problem.


Dequeue more alerts in a single batch.

Current coverage is 36.78% (diff: 0.00%)

Merging #259 into develop will not change coverage

@@            develop       #259   diff @@
==========================================
  Files           261        261
  Lines         14234      14234
  Methods           0          0
  Messages          0          0
  Branches       2395       2395
==========================================
  Hits           5236       5236
  Misses         8274       8274
  Partials        724        724

Powered by Codecov. Last update 1145339...1a47a28


Displaying authentication code does not work in other languages

Looking at this commit, the logic for displaying the authentication code will not work on pages that use other languages.  We have devs working internationally using the tool, but once we required these authentication codes in Azure it breaks for our international colleagues.
Essentially there is german output saying that you need to enter the authentication code displayed and the console doesn't display the code.  If you run the application using the GUI mode, it is there on the page.

Attached is the HTML page of a German authentication page, if that helps.  I've tried to clear out as much identifying information as I can.
german-2fa-response.html.txt

I'm sorry for the lack of clear "when I do X, Y happens" sort of helpful details!
We have a wrapper application that sits on top of aws-azure-login to store valid AWS accounts and provide some helpful CLI prompts and configuration that makes using the tool easier in our company's environment.
Unfortunately that, along side the fact that I can't use the German pages personally makes it hard for me to give you the exact arguments that we're using for the tool.

What makes it hard for me is that I don't know where the German setting comes from. I'm one of the persons affected by that.
I'm trying to change my OS to English to see if that changes the flow.

Release v3.6.1 which should fix the issue. Kindly let me know :)
Thanks to @guerda


Not working

Ran a combat last night and it was not taking off arrows or bolts.  I checked configuration but it only has magic ammo option.  Is there something I need to do or check?
Thanks!
Gib

Are you on dnd v 3.x if so there was new update released last night to fix compatibility

Also the module only automates the recovery of ammo. Consumption is handled by core

Not core but dnd 5e items have a missing code base.  Apparently after you
buy a bow and put it on your character you have to edit it and click
details and choose arrows as the consumed resource with a count of 1.  Big
oversight in the SRD programmers part.  Took me several hours researching
why my bow attacks were not consuming ammo! :(
Anyway thanks for your replies on your mod, much appreciated!!
On Thu, Mar 21, 2024 at 9:09 PM Nekro Darkmoon @.***>
wrote:

Also the module only automates the recovery of ammo. Consumption is
handled by core
—
Reply to this email directly, view it on GitHub
https://github.com/NekroDarkmoon/ammo-tracker-fvtt/issues/19#issuecomment-2014183218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHGTWKIDHNUA7TEHHGLORSLYZOHE7AVCNFSM6AAAAABFCQWQAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJUGE4DGMRRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Refactor Manual

We really need to refactor the manual so that we have separate sections describing our samplers/optimizers and their configurations.  I'm thinking a chapter after "Introduction" called something like "Algorithms" with details on HMC, adaptation, optimization, and potential pitfalls in practice, which would leave the configuration doc in the "Commands" chapter much cleaner.
I assign myself since I know the most about the samplers.

absorbed into #2103


fasd:2: fork failed: resource temporarily unavailable

Is there any solution for it?

I don't think it's related to fzf. Google will probably give you some pointers.

@SharkIng
I had the same problem and I found I define a function which is the example from the fzf project.
v() {
# local file
# file="$(fasd -Rfl "$1" | fzf -1 -0 --no-sort +m)" && vi "${file}" || return 1
}
And I also have an alias defined as
alias v="fasd -e vim"
which is an example from the fasd project.
The problem was solved by removing either of them.
I guess the same name caused some recursive calls which run out of the process resource.


PPO Algorithm Convergence Issue: Ladder Degradation Problem

I customized an environment and trained it with the PPO algorithm，Why does my strategy suddenly collapse as the model is trained？
Is this a problem with my environment? Or is it a common problem in reinforcement learning? How do I fix it？Thank you for your teaching and look forward to receiving a response。

Hi, thanks for reaching out. This can be many several reasons off the top of my head, but I cannot say much unless I know more about the task you want to train on. I know it's been a few weeks since you've posted this but if you still have questions on this, feel free to email me!


Set up Condor article publishing process

We have a series of articles in Markdown format on the Condor Knowledge base.
We need to find a way to surface these articles in a pretty, easily readable format.
We need to decide which article go where; Some articles are more high-level, not as techy, and would be suited to the Condor Portal. others are more technical, probably not very good as Condor POrtal content.
There should be three possible destinations for these articles:

A single "Condor Info " area where all the KB content is formatted and presented nicely. This could probably be a Github Pages space connected to the condor-info repo. In this way, whenever an article is merged to the main branch (which means it has been successfully reviewed) then it will immediately be published to this site. and all articles will live there without exceptions
Some articles will be suitable for the COndor Portal. We shoudl have a process for importing/copying these articles across to the Condor Portal, ensuring they look well in the Condor Portal and no images or headings are lost.
Same thing applies for the dev Portal. We only recently acquired the ability to modify the Dev Portal in this way, but this is a giant leap forward in terms of the liveness we can present to the public and the specificity of the information we can present.


How often does a instance run?

I have read and re-read this and it constantly refers to 'on its next run' or 'The next time autoscale checks' -- but I cannot find out how often it checks or if that is a setting.

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

ID: 88ba1a56-69ec-94c0-8874-78a178a7440e
Version Independent ID: 23ba7799-c21c-be1a-f352-06b025a94f93
Content: Best practices for autoscale
Content Source: articles/azure-monitor/platform/autoscale-best-practices.md
Service: azure-monitor
Sub-service: autoscale
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

@joeruder autoscale runs every minute for VMSS, App Service Plans, ADX, API Mgmt. Every minute, tries to find the active profile, evaluates all rules in the profile (including min/max counts) and decides if an action is required.
The only exception is Azure Cloud Services, autoscale runs every 5min.

Thank you very much.
Would anybody happen to have a link I can use to show my coworker?

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

Do you mean link to documentation?
I dont believe we have this info documented publically. adding @anirudhcavale to confirm.
@anirudhcavale if doc doesnt exist, can we add this as a doc-enhancement request to our backlog?

I don't believe there is documentation. I will add something to our backlog to update.
#please-close


Don't terminate interpreter on read error

Steps to reproduce the issue
Please forgive my bad SystemVerilog syntax, I'm just experimenting.
$ cat half_adder.v
module half_adder;
    function ha(input a, b, output y, carry);
        y = a ^ b
        carry = a & b
    endfunction

    initial begin
        y, carry = ha(0, 0)

        $display("ha(0, 0): %0d, %0d", y, carry);
    end

    // abc
endmodule

$ yosys

yosys> read -sv half_adder.v
1. Executing Verilog-2005 frontend: half_adder.v
Parsing SystemVerilog input from `half_adder.v' to AST representation.
half_adder.v:4: ERROR: syntax error, unexpected TOK_ID

$

Expected behavior
In most REPL's, when you try to load program code into the interpreter, and the code fails to parse, then the interpreter displays an error message but then resumes prompting for further commands. For example, this is a common workflow when actively debugging your program.
Actual behavior
yosys terminates the REPL. This requires the user to manually relaunch the yosys interpreter each time a parse error is introduced in their code.

I totally agree with this enhancement or "request". Quitting every time when an error occurs for me is a huge limitation to the tool


Where is new declaration (.d.ts) file? (typescript import error)

Could not find a declaration file for module '@metamask/detect-provider'. <EMAIL_ADDRESS>implicitly has an 'any' type. Try npm install @types/metamask__detect-provider if it exists or add a new declaration (.d.ts) file containing declare module '@metamask/detect-provider';ts(7016)

Thanks, we'll ship type definitions with the next version!

When it comes out, I will apply it immediately. Thanks

We shipped types via #18 in 1.2.0.


Load configuration from external file

I will try to explain myself the best I could.
The thing is, I want to load the configuration variables that are in the different environments files, from an external file, and not in compilation time.
For what?
If we have that possibility, we can do configuration changes without change any code, deploy, or build anything.
I've made a solution for my actual company, and I'd like to share it here, and see posible alternatives. We are using docker, dcos and consul.
Here is the solution:
/assets/config.tpl.json
{
  "production": ##production##,
  "DYNAMIC_VAR": ##DYNAMIC_VAR##
}

This template, is use to replace the values and generate the file which the website reads before load.
/assets/config.json
{
  "production": false,
  "DYNAMIC_VAR": "DYNAMIC_VAR_VALUE"
}

This file is only used for development in localhost
.angular-cli.json
"environmentSource": "environments/environment.ts",
"environments": {
    "dev":  "environments/environment.ts",
    "prod": "environments/environment.ts"
}

environments/environment.ts
function loadJSON(filePath) {
  const json = loadTextFileAjaxSync(filePath, "application/json");
  return JSON.parse(json);
}

function loadTextFileAjaxSync(filePath, mimeType) {
  const xmlhttp = new XMLHttpRequest();
  xmlhttp.open("GET", filePath, false);
  if (mimeType != null) {
    if (xmlhttp.overrideMimeType) {
      xmlhttp.overrideMimeType(mimeType);
    }
  }
  xmlhttp.send();
  if (xmlhttp.status == 200) {
    return xmlhttp.responseText;
  }
  else {
    return null;
  }
}

export const environment = loadJSON('/assets/config.json');

package.json
"scripts": {
    "build": "ng build --prod --aot=false",
  },

Dockerfile
...

RUN curl -o /tmp/envconsul_${ENVCONSUL_VERSION}_linux_amd64.zip https://releases.hashicorp.com/envconsul/${ENVCONSUL_VERSION}/envconsul_${ENVCONSUL_VERSION}_linux_amd64.zip

RUN cd /tmp && \
    unzip envconsul_${ENVCONSUL_VERSION}_linux_amd64.zip && \
    mv envconsul /bin/envconsul && \
    rm -rf /tmp/*

...

COPY script/templates/nginx_default.tpl /etc/nginx/sites-available/default
COPY script/entrypoint.sh /entrypoint.sh
COPY script/replace_and_run.sh /replace_and_run.sh
RUN chmod +x /entrypoint.sh
RUN chmod +x /replace_and_run.sh
RUN npm run build && rm -rf /var/www/html/* && cp -R /tmp/app/dist/* /var/www/html/ && rm -rf /tmp/*

ENTRYPOINT ["bash", "/entrypoint.sh"]
CMD ["nginx", "-g", "daemon off;"]

/script/entrypoint.sh
#!/usr/bin/env bash

set -e

/bin/envconsul -pristine -consul ${ENVCONSUL_HOST} -prefix ${ENVCONSUL_PREFIX_ENV}${ENVCONSUL_PREFIX_SERVICE} /replace_and_run.sh "$@"

This read from consul the environments variables
/script/replace_and_run.sh
#!/usr/bin/env bash

set -e

cp /var/www/html/assets/config.tpl.json /var/www/html/assets/config.json

unset IFS
for var in $(compgen -e); do
    sed -i 's~##'"$var"'##~"'"${!var}"'"~g' /var/www/html/assets/config.json
done

exec "$@"

This replace the variables in the template and generates the final file with the config.
The thing is, now, we can modify an endpoint for example, without do anything, just go to consul, change the variable, and it automatically restart de service and with a reload in the website, we see the changes.
I'm here to clarify the doubts, because it's a complex issue...
Thanks to everybody interested!
BR

Heya, I have to close and link to https://github.com/angular/angular-cli/issues/3855 here, in order to keep discussion on this topic on the same FAQ labelled issue.
I appreciate the alternative solution here, it's similar to mine in https://github.com/angular/angular-cli/issues/3855#issuecomment-301864970 but a bit more specific to your setup.

Thanks works wonderfully yet i added some extra code cause i dont wanna to add all the properties:
`let finalEnviron:any =
{  production: false
};
function loadJSON(filePath) {
const json = loadTextFileAjaxSync(filePath, "application/json");
return JSON.parse(json);
}
function loadTextFileAjaxSync(filePath, mimeType) {
const xmlhttp = new XMLHttpRequest();
xmlhttp.open("GET", filePath, false);
if (mimeType != null) {
if (xmlhttp.overrideMimeType) {
xmlhttp.overrideMimeType(mimeType);
}
}
xmlhttp.send();
if (xmlhttp.status == 200) {
return xmlhttp.responseText;
}
else {
return null;
}
}
function loadVars(finalEnviron){
let environ =  loadJSON('/assets/config.json');
for (let key in environ) {
let item = environ[key];
finalEnviron[key] = item;
console.log(key);
}
return finalEnviron;
}
export const environment = loadVars(finalEnviron);`

these solutions not works with aot mode.


Issues with Mask Filling

I encountered the following errors when trying to run the lm_mask_fill.py script.
  File "../../data_construction/neg_mask_regen/lm_mask_fill.py", line 175, in <module>
    main()
  File "../../data_construction/neg_mask_regen/lm_mask_fill.py", line 164, in main
    new_summary = bart.fill_mask(inputs, topk=args.topk, beam=5, match_source_len=False)
  File "/export/home/cliff_summ/data/fairseqs/fairseq/models/bart/hub_interface.py", line 196, in fill_mask
    batch_hypos = self.generate(batch_tokens, **generate_kwargs)
  File "/export/home/cliff_summ/data/fairseqs/fairseq/models/bart/hub_interface.py", line 105, in generate
    return super().generate(
  File "/export/home/cliff_summ/data/fairseqs/fairseq/hub_utils.py", line 171, in generate
    translations = self.task.inference_step(
  File "/export/home/cliff_summ/data/fairseqs/fairseq/tasks/fairseq_task.py", line 450, in inference_step
    return generator.generate(
  File "/root/miniconda3/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 26, in decorate_context
    return func(*args, **kwargs)
  File "/export/home/cliff_summ/data/fairseqs/fairseq/sequence_generator.py", line 176, in generate
    return self._generate(sample, **kwargs)
  File "/export/home/cliff_summ/data/fairseqs/fairseq/sequence_generator.py", line 341, in _generate
    lprobs, tokens, scores = self._prefix_tokens(
  File "/export/home/cliff_summ/data/fairseqs/fairseq/sequence_generator.py", line 547, in _prefix_tokens
    prefix_lprobs = lprobs.gather(-1, prefix_toks.unsqueeze(-1))
RuntimeError: Size does not match at dimension 0 expected index [120, 1] to be smaller than src [100, 50265] apart from dimension 1```

Just had time to look into the problem. The underlying issue was incidentally fixed when I was working on another project.
Please go to <site-packpages>/fairseq/hub_utils.py and check the code starting from Line 167:
        results = []
        for batch in self._build_batches(tokenized_sentences, skip_invalid_size_inputs):
            batch = utils.apply_to_sample(lambda t: t.to(self.device), batch)
            translations = self.task.inference_step(
                generator, self.models, batch, **inference_step_args
            )
            for id, hypos in zip(batch["id"].tolist(), translations):
                results.append((id, hypos))

Change to:
        results = []
        sid = 0
        for batch in self._build_batches(tokenized_sentences, skip_invalid_size_inputs):
            batch = utils.apply_to_sample(lambda t: t.to(self.device), batch)
            batch_size = batch["net_input"]["src_tokens"].size(0)
            if "prefix_tokens" in inference_step_args:
                batch_inference_step_args = copy.copy(inference_step_args)
                batch_inference_step_args["prefix_tokens"] = inference_step_args["prefix_tokens"][sid:sid + batch_size]
                sid += batch_size
            else:
                batch_inference_step_args = inference_step_args
            translations = self.task.inference_step(
                generator, self.models, batch, **batch_inference_step_args
            )
            for id, hypos in zip(batch["id"].tolist(), translations):
                results.append((id, hypos))


add --nocapture for build-scripts

Problem
Directly output the output of build-script to stdout/stderr.
I do this because sometimes the error log is very large, which can easily exceed 4GB of cargo memory usage
But sometimes I only need the error header quickly and terminate when I see the required error But for the current cargo, I need to wait for its output to be completed before outputting it uniformly, which may take a very long time
Proposed Solution
No response
Notes
No response

But sometimes I only need the error header quickly and terminate when I see the required error

Did you mean terminating manually by yourself, or Cargo terminates when build script exits with non-zero code?

I do this because sometimes the error log is very large, which can easily exceed 4GB of cargo memory usage

An alternative way to deal with high memory usage is Cargo parses build script directives while streaming the output, instead of capturing it and parsing it after build script execution. (See the code here)

Did you mean terminating manually by yourself, or Cargo terminates when build script exits with non-zero code?

Yes, I mean manually terminate it

If I'm understanding this, a single build scripts output is over 4GB? What is the situation leading to that?

I use the lalrpop library to build a complex language parser, which outputs an extremely large state table when I make modifications that cause conflicts


Delay in ListWheelScrollView drag when inside ListView

While working on an update to my app I noticed a delay was occurring between the time when I started physically dragging a ListWheelScrollView widget and when the widget would actually start scrolling. The list wheel was inside a widget that could also be scrolled. There seemed to be a competition occurring between the 2 scroll widgets. After a certain amount of slop the gesture arena would award the winner to the list wheel and the list wheel would then jump to catch up to my finger.
A gist demonstrating the issue:
https://gist.github.com/tlarsen7572/6ad0bda849f14470bfb4de3f762f3b5e
flutter analyze:
Analyzing sandbox...
No issues found! (ran in 3.7s)

flutter doctor -v
[✓] Flutter (Channel dev, v0.7.5, on Mac OS X 10.13.6 17G65, locale en-US)
    • Flutter version 0.7.5 at /Users/tlarsen/flutter
    • Framework revision eab5cd9853 (5 days ago), 2018-08-30 14:47:04 -0700
    • Engine revision dc7b5eb89d
    • Dart version 2.1.0-dev.3.0.flutter-760a9690c2

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/tlarsen/Library/Android/sdk
    • Android NDK at /Users/tlarsen/Library/Android/sdk/ndk-bundle
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2018.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 27.1.3
    • Dart plugin version 182.4129.13

[✓] Connected devices (1 available)
    • iPhone X • DA6C168F-2B61-476C-9E89-EE9AE3C97438 • ios • iOS 11.4 (simulator)

• No issues found!

I found that this delay is hardly noticeable with a release build on a device
but quite noticeable in the emulator especially when the log window of the IDE is open.

Still persists.
Flutter master v1.16.3-pre.56. Android 10 emulator

Hi @tlarsendataguy, Looks like the link to the code sample you shared no longer exists, I tried to reproduce this issue with the below code sample and it seems to work fine. The ListWheelScrollView scroll along with the pointer. Let us know if you are still seeing any delay.
output

Desktop
Android

code sample
import 'package:flutter/gestures.dart';
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        scrollBehavior: MyCustomScrollBehavior(),
        theme: ThemeData.dark().copyWith(
          scaffoldBackgroundColor: darkBlue,
        ),
        debugShowCheckedModeBanner: false,
        home: MyWidget());
  }
}

class MyCustomScrollBehavior extends MaterialScrollBehavior {
  @override
  Set<PointerDeviceKind> get dragDevices => {
        PointerDeviceKind.touch,
        PointerDeviceKind.mouse,
      };
}

class MyWidget extends StatefulWidget {
  @override
  State<MyWidget> createState() => _MyWidgetState();
}

class _MyWidgetState extends State<MyWidget> {
  final GlobalKey<FormState> _formKey = GlobalKey<FormState>();

  final TextEditingController controller = TextEditingController();

  @override
  Widget build(BuildContext context) {
    int length = Colors.accents.length;
    return Scaffold(
      body: ListWheelScrollView(itemExtent: 120, children: [
        for (int i = 0; i < length; i++)
          Padding(
            padding: const EdgeInsets.all(8.0),
            child: Container(
              decoration: BoxDecoration(
                  color: Colors.accents[i],
                  borderRadius: BorderRadius.circular(10)),
            ),
          )
      ]),
    );
  }
}


Fix: [Deribit] NumberFormatException while parsing stop market orders from json #3932

Fixes issue #3932

deribit fix: handle non-numeric marker values in order.price

I'd rather see price be defined as a String and then have a custom getter. Otherwise you're throwing away info that may be useful like if price was set to market.

Sure, i've changed it to a custom getter instead. It makes sense to keep the original value.


Tune Down own sanitisation: Only encode a subset of URI-encoding

Pull Request Test Coverage Report for Build 572321151

15 of 18 (83.33%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 88.991%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/producer/producer.ts
4
5
80.0%

src/activity/activity.ts
2
4
50.0%

Totals

Change from base Build 572246785:
0.2%

Covered Lines:
257

Relevant Lines:
274

💛  - Coveralls


Step 6 incorrect and should be removed

For step 6 in the article:
"Step 6 - Remove and delete the Microsoft 365 license from a former employee"
This is incorrect to remove licensing from a user before deletion, this will cause both Litigation hold and Compliance Retention policies to fail.  They require licensing to be intact upon deletion so an inactive mailbox can be created:
https://docs.microsoft.com/en-us/microsoft-365/compliance/create-and-manage-inactive-mailboxes?view=o365-worldwide#create-an-inactive-mailbox
Furthermore even if Litigation hold or Compliance Retention policies are not in use, there is no benefit to removing a license since it is still reclaimed anyways when the account is deleted.
Thanks
Sam
[Enter feedback here]

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

ID: 4e366b9c-0d35-83c6-f509-1774dd351504
Version Independent ID: 702f2dc1-46f8-508a-68bc-b5d033c56a9a
Content: Remove a former employee - Overview - Microsoft 365 admin
Content Source: microsoft-365/admin/add-users/remove-former-employee.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@ssmiller60 Thank you for your feedback. I have added a statement in the document stating that if the mailbox is to be preserved for compliance or legal reason it must be assigned an Exchange Online Plan 2 license (or an Exchange Online Plan 1 license with an Exchange Online Archiving add-on license) so that a hold can be applied to the mailbox before it's deleted. After the user account is deleted, any Exchange Online license associated with the user account will be available to assign to a new user.
This can be tracked via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/7693
Once the author approves, the document will be live.
Thanks
Sri

Thanks Sri that's better than what was there before, but why is removing
the license even mentioned for the process, there is no reason to do it at
all?
Sam
On Sun, Feb 13, 2022, 7:52 PM Sriraman M S @.***> wrote:

@ssmiller60 https://github.com/ssmiller60 Thank you for your feedback.
I have added a statement in the document stating that if the mailbox is to
be preserved for compliance or legal reason it must be assigned an Exchange
Online Plan 2 license (or an Exchange Online Plan 1 license with an
Exchange Online Archiving add-on license) so that a hold can be applied to
the mailbox before it's deleted. After the user account is deleted, any
Exchange Online license associated with the user account will be available
to assign to a new user.
This can be tracked via PR##7693
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/7693
Once the author approves, the document will be live.
Thanks
Sri
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7664#issuecomment-1038506249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATMY74YRFVCYYCIDRC7YYXDU3BG5RANCNFSM5OAZBQDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@ssmiller60 Thank you for the response. I think the removal of licenses is required if the organization wants to convert it to a shared mailbox (Step 3) and release the license for re-use.
Hope this helps!
Thanks
Sri

@ssmiller60 The license cannot be removed from Step 3 as steps 4 & 5 need the license intact. While the scope is smaller, I can confirm these are the correct steps in order to remove a former employee.
CC: @kwekuako
Thanks
Sri

Thanks! Seems like even more reasons to not mention license removal.
Looking forward to your response.
Sam
On Tue, Feb 15, 2022, 3:36 AM Sriraman M S @.***> wrote:

@ssmiller60 https://github.com/ssmiller60 The license cannot be removed
from Step 3 as steps 4 & 5 need the license intact. While the scope is
smaller, I can confirm these are the correct steps in order to remove a
former employee.
CC: @kwekuako https://github.com/kwekuako
Thanks
Sri
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7664#issuecomment-1040000401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATMY746WBYCYQHIY22SZQZTU3IGCRANCNFSM5OAZBQDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@ssmiller60  Thank you for the response. The idea behind converting these shared mailboxes is also to ensure that there are no licenses assigned to them and the license can instead be reused with a new hire. While I agree with you that not all organizations will use this approach, this is a feature available in Microsoft 365 so that they don't have to pay for a terminated employee's mailbox.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @ssmiller60 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Create an event page...

.. to display events to which we participates (talks, workshops, etc), with links to resources (slides, etc). It could be a way to keep track of them.
We could store the information in a YAML file in the _data folder, and display them as a table on a dedicated page linked on the header.
What do you think?

this sounds perfect!

RDA talk
BCC talk

SSI all fellows Nov 2019

Talks:

Talk at Turing
Talk at Manchester
Talk at SSI
Talk CW20: Yo

Online shout outs:

Turing Research in focus: TBA
OSUM: Samuel

podcast: https://www.podbean.com/media/share/pb-b6k74-f1f4bd
blogs:

program launch: https://www.software.ac.uk/blog/2019-11-22-supercharge-your-open-project-leadership-training
on mentoring: https://www.software.ac.uk/blog/2020-10-09-key-skills-know-mentoring
eosc: https://www.eosc-life.eu/news/4-projects-awarded-funding-within-first-training-open-call/ and https://www.eosc-life.eu/news/training-open-science-for-eosc-life-ris/
galaxy: https://galaxyproject.eu/posts/2020/12/22/ols/

preprint: https://osf.io/k3bfn/

podcast: https://www.podbean.com/media/share/pb-b6k74-f1f4bd
blogs:

program launch: https://www.software.ac.uk/blog/2019-11-22-supercharge-your-open-project-leadership-training
on mentoring: https://www.software.ac.uk/blog/2020-10-09-key-skills-know-mentoring
eosc: https://www.eosc-life.eu/news/4-projects-awarded-funding-within-first-training-open-call/ and https://www.eosc-life.eu/news/training-open-science-for-eosc-life-ris/
galaxy: https://galaxyproject.eu/posts/2020/12/22/ols/

preprint: https://osf.io/k3bfn/

The event page is created but empty: https://github.com/open-life-science/open-life-science.github.io/blob/main/events.md
The event should be stored in the _data/events.yaml file