Implement dynamic way on Windows

Thanks to @izgzhen we now have dynamic way working on Linux and OSX (#4). But Windows is still not supported. We'll track the progress here.
Presumably this is not high priority; do let me know otherwise.
There is some ongoing work in GHC on dynamic linking for Windows: https://phabricator.haskell.org/D2592

Note that gen-dll package will need to be added to make this work.
See #404 and https://phabricator.haskell.org/D3883.

@snowleopard I'm slowly merging in the rest of the stuff for dynamic way on Windows, if it's easier for you I would be fine with also doing the changes for Hadrian. If you have any preferences on how it should be done let me know. I know you wanted the tool as a Haskell program so presumably you don't need to call out to a separate program.

@Mistuke It would be great if you could also translate your changes into Hadrian! This will definitely save us a lot of time. I'm fine if the first version calls out into a separate script if that's more convenient for you. We can always rewrite it in Haskell later.
I'll be happy to review the PR and help in any other way!

Alright then :), I'll make sure to keep Hadrian in sync with the make changes.

Great, thanks! 🎉

What's the current status on this, @Mistuke ? Do we have the necessary pieces to support generating .dlls on Windows?

It's still on my list but has slipped behind some more urgent work. {{gen-dll}} solves the most urgent problem but I still need to work out some ABI issues. however the linker, I/O manager and string merging have been taking the majority of my time.

No worries, I just wanted to know whether we had everything needed for me to tackle the hadrian side or not. Just ping us when it's all there :-)

Sorry for the annoyance, but were there any updates regarding this one?

Sorry for the annoyance, but were there any updates regarding this one?

While I am not an active contributor now, I believe that since the merge of Hadrian to GHC master, related issues are tracked in https://gitlab.haskell.org/ghc/ghc/issues.

@XVilka Indeed, I keep this repository mostly for historical/documentation purposes only. If Hadrian is missing any features that are important for you (such as dynamic linking on Windows), it would be best if you open a ticket on GitLab and describe the desired functionality.


Output of the CNN network

Hello,
thanks for the code. I have 2 questions about the output of the CNN network.

Why is the output of the network a vector of 2  ? I have seen other Siamese network have a different output but never correlated to job the net has to do.
How would I then use the network for inference ?

Hi,

The output of the model is the vector of  two since, due to contrastive loss, which is a  similarity based distance metric
Right now, you can use this code starting from this line which predicts for all the images in the test dataset, If I have time I will rewrite it function for single set of signatures


Added support for Bedrock Titan Embeddings v2

Description

Added support for Bedrock Titan Embeddings v2.  This version introduces new parameters to the request body, dimensions and normalize, so added new field, titan_body_kwargs, to support.
Renamed model field to model_name to adhere to that used in parent class, BaseEmbedding.  Bumped to 0.2.0 consequently.

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

@nerdai Just requesting re-review since the review should be stale with my two additional commits.


Enterprise Vs Education

Wondering if this is off but at the bottom where the Win 10 upgrade paths are, it has a (D)owngrade mark under the Enterprise column for the Education row of Windows 10.
I just wanted to know if this is accurate and Enterprise is actually considered a downgrade from the Education edition of Windows.
Thank you

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

ID: 08436cb0-d0b6-0961-9e57-291b24d73644
Version Independent ID: 36264f52-d3ac-4e50-f8e8-b09d6b210490
Content: Windows 10 upgrade paths (Windows 10) - Windows Deployment
Content Source: windows/deployment/upgrade/windows-10-upgrade-paths.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

It is neither an upgrade nor a downgrade, but functionally since your user data is not maintained it behaves the same as a downgrade.

It is neither an upgrade nor a downgrade, but functionally since your user data is not maintained it behaves the same as a downgrade.

Interesting viewpoint, I had forgotten to look at it that way.

Interesting viewpoint, I had forgotten to look at it that way.

That is a very interesting point. Currently studying for the MD-100 and
101T so I will keep that in mind.
I appreciate the knowledge.
On Tue, Jan 19, 2021, 12:19 PM Trond B. Krokli<EMAIL_ADDRESS>wrote:

Interesting viewpoint, I had forgotten to look at it that way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8976#issuecomment-762992164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASP6ZOQIDGKIO2XC3RUGEZLS2W5JTANCNFSM4WGMSZOQ
.

That is a very interesting point. Currently studying for the MD-100 and
101T so I will keep that in mind.
I appreciate the knowledge.
On Tue, Jan 19, 2021, 12:19 PM Trond B. Krokli<EMAIL_ADDRESS>wrote:

Interesting viewpoint, I had forgotten to look at it that way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8976#issuecomment-762992164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASP6ZOQIDGKIO2XC3RUGEZLS2W5JTANCNFSM4WGMSZOQ
.

Also have a look here in this chart Education is viewed as an upgrade from Enterprise (Enterprise > Education). What I'm saying is there are no feature advantages to Education vs. Enterprise AFAIK.
https://docs.microsoft.com/en-us/windows/deployment/upgrade/windows-10-edition-upgrades

Also have a look here in this chart Education is viewed as an upgrade from Enterprise (Enterprise > Education). What I'm saying is there are no feature advantages to Education vs. Enterprise AFAIK.
https://docs.microsoft.com/en-us/windows/deployment/upgrade/windows-10-edition-upgrades


Upstream changes to fix child compiler modules

Hey, this change was suggested by @sokra and solves my issues with child compliers. I'm not sure if there is a reason it wasn't committed or upstreamed already. Getting this merged soon would be great. Thanks

I tried rewriting it but really screwed something up my bad, I tried to amend it and duplicated the commit

Than ks


Add support for configuring the build system scheduler

Add methods for changing the scheduler algorithm. Supports:
-- commandNamePriority: priority queue ordered by command name [default]
-- fifo: first in/first out queue - previous behavior
Add methods for setting the lane width of the scheduler
Add command line option for llbuild debug tool for selecting the scheduler

@swift-ci please smoke test


[CSS]: Button Alignment Main Page

When we see the main page in responsive view, the alignment of 'Become a sponsor' button is somewhat 'left' to the page
Steps to Reproduce:

Switch to Mobile view
Scroll to supporter's section
See the button

Screenshot:

Additional Context:
If you see this as a genuine issue, I would love to work on it.

Hey @sparsh-99
I understand your issue. Can you please explain a lit bit more because what I think is the button here is actually an image and its width and height are controlled from the same.
Do let me know if I am not able to understand your point

Look the margin below, you will get the idea-

Image is left-indent!!! @Yashank18

Will you please help me how can I fix this indentation myself? How can I find this file in this bid code?

Sure @sparsh-99
You will find this in Index.html only.
Under div with class="col sm-12 supporters"

Can I contribute here?

@A-GHOSH-dev yes, I think the next action would be reviewing @sparsh-99 pull request #290 and telling if the code is fine and has the intended results (resolves the problem; for this you probably also need to check out a pre- #290  commit to see the issue)

Can i work on this issue?

Is this issue still open?

Willin got work on it


Update new icon

Hey @Cap32! Thanks for contributing this logo. Could you give a bit more context to this PR. What motivated you to create this, why do you feel like we should update the logo, etc.
@Telokis what do you think about this logo change?

I'm really like this extension, and IMHO the new one is much more beautiful and modern 😃

Hey @Cap32!
Thanks for your contribution!
As @dkundel said before, It's always better to try to provide some context as to why you are making a PR.
About the logo itself, it's pretty but a bit too simple, in my opinion. There is nothing related to files and it's only about "adding". It misses the critical information.

Yeah I agree with @Telokis. I'm totally fine with a new logo :) I created this one sort of quickly :D But a bit more context in the logo would be great.
Cheers,
Dominik


Added enable method after destroy

Added method enable.
Enable can be used after destroy.
sb.enable()

Hello and thanks for your PR! I'm just wondering about use case of this method.
If you want to temporarily disable scrolling you can just use shouldScroll method and set it to true/false.
Also please make changes in source file (index.js) so I can see what changes exactly did you made. Don't need to push another compiled file :)

I apologize, I just started to discover github for myself and still did not understand what to do


e2e-tests: Improve with more docs, and cover a few more features

Improve e2e tests with a better docs, and cover a few more features.

README: Add better getting started instructions, and a few usage tips
namespaces: Add test for creating and deleting
headlampPage: Fix test to wait for page to load
headlamp.spec: Add test for pagination

Closing because I made separate PRs.


Uploading bundle: FAILED No such file

➜  app-deployment git:(master) ✗ sudo mup deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

Building Started: ./app/src

Started TaskList: Deploy app 'cloud.app' (linux)
[<IP_ADDRESS>] - Uploading bundle
[<IP_ADDRESS>] x Uploading bundle: FAILED
	No such file
Completed TaskList: Deploy app 'cloud.app' (linux)
➜  app-deployment git:(master) ✗ node -v
v0.12.1

osx

You need to do mup setup first.
On Sat, Apr 25, 2015 at 10:33 AM 蹬<EMAIL_ADDRESS>wrote:

Started TaskList: Deploy app 'cloud.app' (linux)
[<IP_ADDRESS>] - Uploading bundle
[<IP_ADDRESS>] x Uploading bundle: FAILED
No such file
Completed TaskList: Deploy app 'cloud.app' (linux)
osx + nodev0.12.1
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/393.

@arunoda

Seems like it's build error. Is it possible to build it with just using
meteor .
Hope, I need to remove some Cordova enhancement. I will do it today and
ping you.
On 2015 අප්‍රේල් 25, සෙන at පෙ.ව. 11.06 蹬<EMAIL_ADDRESS>wrote:

@arunoda https://github.com/arunoda
[image: image]
https://cloud.githubusercontent.com/assets/804455/7331746/040b0d8a-eb50-11e4-94c6-882c9785cc48.png
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/393#issuecomment-96133532.

nice.

Check now. I've released a new version.
Give it a try.
On Sat, Apr 25, 2015 at 11:24 AM 蹬<EMAIL_ADDRESS>wrote:

nice.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/393#issuecomment-96135167.


Navigating through histroy

I have created a button to go to the first/previous/next/last move, but having looked at the underlying code, I cannot work out how to navigate through the history. I also had a look at chess-console but couldn't work it out!
Do you have any simple pointers to how I can attach some code to my button that will let me move back and forth?

cm-chessboard is just the input element, it does not implement any chess rules or data storing. To hold the game data you have to use something like chess.js.

I am using chess.js. Spent all day on this trying to get it to navigate! I have built an array of fens called fenHistory to help with the navigation.
So far I have:
onClick={() => {                     board.current.setPosition(fenHistory[fenHistory-1])                   }}
That is for the "Previous move" button. I think I'm doing this all wrong, as it is not working!


add backtesting

Added first version for backtesting functionality.
The project does not generate any signals with the default parameters (always below 0.65) so it couldn't be thoroughly tested

Do you want me to update the merge request?


Case folding

I see some version of tolower being used in different places:
https://github.com/benhoyt/countwords/blob/9d81d13711e56c25068893880a648ac96d0fa92e/optimized.py#L17
https://github.com/benhoyt/countwords/blob/9d81d13711e56c25068893880a648ac96d0fa92e/simple.go#L16
https://github.com/benhoyt/countwords/blob/9d81d13711e56c25068893880a648ac96d0fa92e/simple.py#L6
I just wanted to point out, while proper unicode folding is the best option, if you are sticking to something like this, toupper is the better option:

https://stackoverflow.com/questions/11124705#65433126
https://stackoverflow.com/questions/234591#65451148
https://stackoverflow.com/questions/40250988#65452097

From my tests, it's actually the other way around. Currently simple.go takes about 1.1 seconds to run on my machine, but if I change the strings.ToLower to strings.ToUpper, it consistently takes closer to 1.4 seconds (30% slower). I believe this is because there are many more words that are already lowercase, so ToLower doesn't have to allocate a new string in that case, just scan the characters and ensure they're all lowercase already. See https://github.com/golang/go/blob/2d4042d4ab3a2021819dce91eb228daf8fa5e557/src/strings/strings.go#L593
Most words are already lowercase in the input I'm using, but also in most texts.

sorry I wasnt clear. What I meant was, by using ToLower or similar, in some situations, words that should match wont.
This will still be a problem with ToUpper as well, but to a lesser extent. However I can understand if you want to sacrifice accuracy for speed.

Ah, I see, thanks. Yeah, I think I'll leave as is for now.


cannot set css variables with styleMap

element.style.setProperty should not be used to set css variables
element.style['--variableName'] should be used instead
https://github.com/Polymer/lit-html/blob/master/src/directives/style-map.ts#L85
to reproduce just select any element i elements panel and write in the console something like
$0.style.setProperty('--width','40px');
$0.style

you will find weird 0 property with width value

sorry, it's my bug :)


Correctly parse dates for export requests

Trello card
When performing an export request, we should use 'from' and 'to', not 'from_date' and 'to_date', as these are not present in the incoming hash.
This means that export requests have never respected dates.

Looks good 👍


Ask a question

I want to webrtc secondary packaging, how to extract the webrtc ios source code

I have downloaded the Google source code to extract the ios source code of the feeling is a mess


ListView use memory abnormally in IOS, gc works incorrectly.

It is serious, i hope official will fix it in prior.I reported in issue #36753 before, but i discover it is not final problem in the fact.
flutter doctor:
[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.14.5 18F132, locale
    zh-Hans-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
[✓] iOS tools - develop for iOS devices
[!] Android Studio (version 1.5)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    ✗ Unable to find bundled Java version.
[!] Android Studio (version 2.3)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Android Studio (version 3.2)
[!] VS Code (version 1.15.1)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

Description:

Create a listview, and add some items (anything is ok), then open xcode for debug, scroll the view up and down some times, the memory increase 500K-3MB, howerver, it is not easy to decrease for memory. Someone publish it in 2018, issue #20245, and refer to dart vm gc.
Howerver i use flutter 1.7.8-hotfix4, dart-2.4(i checked it has fixed the gc problem), the problem still occured. My app is pure flutter, not native blend flutter.

2.Create a swiper using flutter-swiper plugin, then open xcode for debug, the memory is increasing if the pages in swiper controll changes,  and with no decreasing. The memory leaks. The swiper use pageview,pagecontroller to realize.
I think anywhere using listview, pageview will result to memory cosume incorrectly, maybe it is due to gc mechanism, or listview itself not handle normally.Due to this, it is almost not possible to release some complicated app, the memory is used so terrible.

/cc @dnfield

Can you try to get a memory dump of the app and see what's taking up the space?  Run it in Xcode, and use the memory debugging features to check.
I suspect this is WAI - Skia has an internal cache which will hold on to some graphics related things up to a certain limit. We almost never flush that cache, unless there is memory pressure. I recently changed it so that the limit of the cache would be based on screen resolution, but I expect that 3MB is far below that limit (the cache previously was hard coded to 512MB, now it should typically be somewhere in at least the 10s if not 100s of MB, dependent on screen resolution).
If you need to set that cache smaller (which is not typically recommended), there's a system channel to do so.  However, it would be good to first verify which objects are taking up space.  You could also verify that Dart objects are getting collected by attaching to the observatory and looking at the heap.

Sorry, i reply to this now.It is not relevant to graphic cache directly, because i test it in almost empty example code, that only have app widget, and create a listview in body, add two or more text or image items, then scroll the listview, you can reappear my problem. You just scroll the listview up and down, xcode memory performance will change, mostly up but rarely down. You can try it as my discription.
I use flutter swiper, just show the control widget, not do something else, the memory also increase, i don't know clearly that if the plugin has some bug, i only see the plugin use pageview and timer, but the memory consume abnormally as result.

@dnfield

Is there any news?

Can you please share a sample app that causes this problem?
This could be due to many different things and it's hard to properly triage this issue as is right now.  What specific widgets you're using makes a difference here, as it could be images, or it could be something else.  We've made some memory usage improvements since this bug was originally filed, and it may be fixed now as well.

And if the problem is with images, see my comment on the other bug you linked.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now.
@zf19820621 provide please a sample app to reproduce this problem if it persists and I'll reopen it,
Thank you


HttpRequestException handling

Hello, I have been using this library and I love it. I have implemented some error handlers using your OnFailure methods.  That works great for failure responses returned from the server.  What is the strategy for handling HttpRequestExceptions which would get thrown, for example, if the users internet connection was down.
It would be nice to be able to hande that within this framework.  Please let me know if there is a way to do that, or if that is a possible future feature.

Yep, this can be done.

I've added Action<HttpRequestException> HttpRequestExceptionHandler to the HttpRequestBuilder class.
I updated the send method to catch the exception and, if an action has been defined, it will pass that exception to the action and then return null. If that action hasn't been defined, it will rethrow the exception.
I added the extension method OnHttpRequestException that will allow the action to be defined using the same fluent syntax that is the core of this library.

All this will be in the v3.0 release.

This has been deprecated in version 4 in favor of using a more comprehensive tool such as Polly.


[FEATURE] Migrate to balloon-hashing from argon2id

I plan to move to balloon hashing (with BLAKE3), instead of argon2id.
It just seems like a better, more suited hashing algorithm and I think now is a pretty good time to migrate over to it. Especially considering the new header style that is being planned (#67).

This was completed.


Types: are they exposed somewhere?

Are the types exposed in the built JS library? I'm using ES6 and cannot include TypeScript just yet. I am trying to avoid having to use anonymous objects in the API calls, say.
https://microsoft.github.io/monaco-editor/playground.html#extending-language-services-hover-provider-example
monaco.languages.registerHoverProvider('mySpecialLanguage', {
	provideHover: function(model, position) {
		return xhr('../playground.html').then(function(res) {
			return {
				range: new monaco.Range(1, 1, model.getLineCount(), model.getLineMaxColumn(model.getLineCount())),
				contents: [
					'**SOURCE**',
					{ language: 'html', value: res.responseText.substring(0, 200) }
				]
			}
		});
	}
});

I'd much rather do the below:
class QuickInfoAdapter extends monaco.languages.HoverProvider {
	provideHover(model, position, token {
	}
}

Thank you,

The *Provider are all interfaces, and you can definitely write classes for the providers, you can even write a single class that implements all providers you wish.
e.g. https://github.com/Microsoft/monaco-typescript/blob/master/src/languageFeatures.ts#L292


Test sync-over-async code in more environments

.NET is currently providing sync APIs that eventually call into an async transport layer.  We should do a lot of stress testing in different environments.  The Storage team has suggested ASP.NET, desktop, WPF, WinForms, WebForms, and anything that might play with SynchronizationContext.

This is a general purpose issue to track running our tests in more environments (in particular different/common synchronization contexts).

This may be something we could consider as part of our perf/stress push going on.

@tg-msft is this still a concern? Now that the engsys team is looking at stress testing - do you have any particular scenarios you would want us to consider?

Hi @tg-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.


Idea for "Always" registries

The UI for this thing is awesome. I have had an idea for integrating registries which are valid for when there are no results in PSRun for example searching for an app which isn't installed could suggest looking for it in winget/scoop/choco/brew/apt.
There are potentially other situations but my main use-case would be winget.
I've hacked together this proof of concept to see if you think it could work. It's a bit sketchy 😆 I just copied your file registry and hacked it until it worked. I'm also not sure if "Always" is the right term, maybe "Search" registries.
GlobalStore at the moment is hard coded to the built-in registries, so I've just added it to the list to get it to work.
https://github.com/mdgrs-mei/PowerShellRun/assets/13159458/2a6ca1e6-98dc-4242-8e86-83f201989151

Wow, thank you for the experiment! Let me look into your code.

I have actually been thinking about a similar idea. I think it's basically the same as the "Search the web in Firefox" entry in PowerToys Run. However, I personally feel that this suggestion entry is not so intuitive.
I would prefer typing "winget" to pick "Winget (PSRun)" entry for example when I want to install something, and then inside the Winget item I would want to filter the packages. So typing what I want to do is clearer to me. Does it make sense? Probably I would like to keep the simple filtering behavior until we find some other use cases. Your Winget registry is pretty useful though.

I personally feel that this suggestion entry is not so intuitive.

Same, I tried it out this way because it was easy to get it running 😆

when I want to install something, and then inside the Winget item I would want to filter the packages. So typing what I want to do is clearer to me. Does it make sense?

Yep. It would be cool to keep the realtime search feel but it would require some debouncing to make sure it's not spamming a slow resource lookup with every keystroke. Otherwise a "search on enter" experience would be fine to keep it simpler.
I haven't looked properly yet but I suspect that with a slower async preview it's actually firing off every time the item changes even when you scroll past the items which could benefit from debouncing too.
Thanks for the module I learned a lot just digging around.

I'm really happy to hear that you like the module 😄!
As for the realtime search, even if we support it in the PowerShellRun's search bar, what gives us search here is the winget module. We can't get both winget filter and PowerShellRun's filter. So "search on enter" might be better in this case.
Just like the example https://github.com/mdgrs-mei/PowerShellRun/discussions/25, you can ask for an input first and then open the TUI which doesn't look cool though.

@ShaunLawrie Are you still interested in continuing this PR? It might not be the case if the main point was the 'Always' part. In either case I might create Winget Utility entry combining this Install feature and my Upgrade example in the future.

I’m interested but it would be better if you flesh out the utility entry
style in the way that makes sense to you. The “always” thing is a bit of a
dead end because the UX is confusing.
I’m preparing for a talk so I’m tied up the next couple of weeks and
shouldn’t be procrastinating with this so I won’t have any time to work on
it 😂
On Sat, 30 Mar 2024 at 1:38 PM, mdgrs @.***> wrote:

@ShaunLawrie https://github.com/ShaunLawrie Are you still interested in
continuing this PR? It might not be the case if the main point was the
'Always' part. In either case I might create Winget Utility entry combining
this Install feature and my Upgrade example in the future.
—
Reply to this email directly, view it on GitHub
https://github.com/mdgrs-mei/PowerShellRun/pull/24#issuecomment-2027846704,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADEMYIUXZLY7FHEIYIRZRCLY2YCP7AVCNFSM6AAAAABFKTBWTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXHA2DMNZQGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok no problem! Thank you again for the PR. It was inspiring. Good luck for the talk!


feat: Targeted testing support

Resolves #104
Other targets could be integrated later on-demand.

Codecov Report

Merging #524 into master will decrease coverage by 0.17%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##           master     #524      +/-   ##
==========================================
- Coverage   99.68%   99.50%   -0.18%
==========================================
  Files          33       34       +1
  Lines        2221     2239      +18
  Branches      349      356       +7
==========================================
+ Hits         2214     2228      +14
- Misses          3        5       +2
- Partials        4        6       +2

Flag
Coverage Δ

#unittests
99.50% <91.30%> (-0.18%)
:arrow_down:

Impacted Files
Coverage Δ

src/schemathesis/runner/impl/solo.py
100.00% <ø> (ø)

src/schemathesis/runner/impl/core.py
98.54% <77.77%> (-1.46%)
:arrow_down:

src/schemathesis/cli/__init__.py
100.00% <100.00%> (ø)

src/schemathesis/runner/__init__.py
100.00% <100.00%> (ø)

src/schemathesis/runner/impl/threadpool.py
100.00% <100.00%> (ø)

src/schemathesis/runner/targeted.py
100.00% <100.00%> (ø)

src/schemathesis/_compat.py
87.50% <0.00%> (-12.50%)
:arrow_down:

src/schemathesis/cli/cassettes.py
99.11% <0.00%> (-0.01%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix broken link otelcol.exporter.loki.md

PR Description
Fix broken link in otelcol.exporter.loki.md
PR Checklist

[ ] CHANGELOG.md updated
[x] Documentation added
[ ] Tests updated
[ ] Config converters updated

@marctc I pushed a fix to your PR here. The change you proposed didn't fix the broken link. The problem was the formatting of the link reference near the bottom of the topic.


ocs2_robotic_tools folder location

Thanks for the nice library.
However, when I catkin build, the message "....            src/ocs2/ocs2_robotic_examples/ocs2_robotic_tools does not exist." is shown.
Please move the folder  "src/ocs2/ocs2_robotic_tools" to src/ocs2/ocs2_robotic_examples/ocs2_robotic_tools.

Either clean your workspace and build again or do $ catkin build --force-cmake


Warning Warning: componentWillReceiveProps has been renamed, and is not recommended for use

I,m using last stable version and get this warning.
react-dom.development.js:12050 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: ColorPicker, EditableInput

I've left a similar comment on the issue:
https://github.com/casesandberg/react-color/issues/458#issuecomment-519944281

Thanks @hlodver for sharing patch-package. It's exactly what I need.

I am also waiting for this :v, is there any clue about when they are going to update it?

same problem

Problem occurs on this file also: https://github.com/casesandberg/react-color/blob/master/src/components/common/ColorWrap.js

Has this project been abandoned?

This was fixed with https://github.com/casesandberg/react-color/pull/662 and will be released shortly as<EMAIL_ADDRESS>

Thanks @casesandberg


Make Kotlin Serialization optional/repaceable

Upgrade to v0.14, I found kotlinx-serialization-core/json becomes a dependency of dataframe-core.
If it is for processing JSON files, it should be part of the dependencies of the dataframe json module. In our backend, we use Kotlin/Spring Boot, but we do not use Kotlin Serialization as JSON serialization/deserialization.
Or it should be replaceable with the existing popular solution, not just Kotlin serialization, should be replaced with Jackson, Jakarta JSONB, Gson, etc.
When upgrading to v0.14, it will conflict with the existing Jackson config in Spring.

Thanks for reporting, we will discuss this issue inside the team and share the solution

Could you explain what breaks for your project when our library has kotlinx.serialization as implementation dependency? Is it a complaint about the size of the dataframe-core dependency or do you face a clash somewhere else in your library?
Currently, our JSON support is not yet in a separate module, but we do have plans to change the infrastructure eventually.

There is a Jackson/Kotlinx coexisting issue in Spring Boot, but Spring Boot does not provide an autoconfig for Kotlinx Serialization, when adding Kotlinx serialization JSON in dependencies, some of our endpoint exposed enum array will pick up Kotlinx as serial/deserial tools.
see: https://github.com/spring-projects/spring-boot/issues/24238#issuecomment-2380387068

Currently, our JSON support is not yet in a separate module, but we do have plans to change the https://github.com/Kotlin/dataframe/issues/100.

It is great.

There is a Jackson/Kotlinx coexisting issue in Spring Boot, but Spring Boot does not provide an autoconfig for Kotlinx Serialization, when adding Kotlinx serialization JSON in dependencies, some of our endpoint exposed enum array will pick up Kotlinx as serial/deserial tools.
see: spring-projects/spring-boot#24238 (comment)

thanks for the explanation!


Wrong peer owner "my peers" menu

There's peer Anton-1, when i check it in tray, it shows as antonmolchanov020790's, but when i go to -> my peer -> Anton-1 and check owner, it shows another account as owner - amolchanov.

it shows owner of environment

OK, misunderstood

Notice I cleaned up the issue name and applied the proper tags to enable search mechanisms. Let's adhere to standards @amol4anoff so our lives get easier. No reason to name the product, it's obvious that this is the Control Center right?

@akarasulu Ok, great!


make-boot-image: preserve file attributes

In order to make binary reproducible images, the script must preserve modification time and other properties of the files as they are copied. Both when copying out from the given directory and into the staging directory, and when copying from the staging dir to the final image.
As FAT does not have the concept of symlinks or hardlinks, we do need the copy command to follow symlinks, meaning we cannot have -d in effect, which in turn precludes using the -a option (which is "same as -dR --preserve=all"). So just add the -p flag, meaning "--preserve=mode,ownership,timestamps".

looks sensible


Compile as dynamic library?

Is there a supported set of configuration options to compile dynamic instead of static libraries?
The context here is I'm trying to write an in-process wrapper for SFrames for the Julia programming language, which will require loading the graphlab libraries at runtime.

There should be a dynamic library already available when you build inside of debug/ or release/.
I was able to get it loaded using Cxx.jl, but this is as far as I got.
addHeaderDir("/Users/chris/SFrame/oss_src", kind=C_System)
addHeaderDir("/Users/chris/SFrame/deps/local/include", kind=C_System)
Libdl.dlopen("/Users/chris/SFrame/debug/oss_src/unity/libunity_shared.dylib", Libdl.RTLD_GLOBAL)
cxxinclude("/Users/chris/SFrame/oss_src/unity/lib/gl_sarray.hpp")
cxxinclude("/Users/chris/SFrame/oss_src/unity/lib/gl_sframe.hpp")
cxxinclude("/Users/chris/SFrame/oss_src/flexible_type/flexible_type.hpp")

icxx"""
graphlab::gl_sframe a = graphlab::gl_sframe();
a["hello"] = graphlab::gl_sarray::from_sequence(0,1000);
a["world"] = 2;
a["world"] = a["world"] + 5;
std::cout << a;
"""

x = @cxxnew graphlab::gl_sarray::from_sequence(0, 500)```

Ah, great. Thanks for clarifying.


[Bug] KubeRay Deployment Failure with Large ServeZip File in Working_Dir

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
I am using KubeRay, with the image being ray_ml:2.9.0. I built a serve that is 92MB in size, and I found that when inserting it into the working_dir, the head node does not fully pull the zip file, leading to deployment failure. However, when I switch it to a smaller servezip, this problem does not occur.
Reproduction script
pass
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

This seems to be a Ray question. Would you mind opening an issue in the Ray repository and cc me in the issue? Thanks!

Close this one, and track in the Ray repository https://github.com/ray-project/ray/issues/44614.


Collapsing/expanding in types view is slow with many types

As of 2.3.2807-dev, I'm seeing delays of ~half a second for 100k types with 10 members each, any more time taken is likely from type refs or qt's painting


[To optimize the install DS ][install] Develop DS installer

*For better global communication, please give priority to using English description, thx! *
Please review https://dolphinscheduler.apache.org/en-us/docs/development/issue.html when describe an issue.
Describe the feature
1.One-click installation function ，One-key installation features, including user Settings, non-secret through, ZK installation and DS installation.
2.Single service start, stop, restart
3.Single node all services, start, stop, restart
4.Ds upgrade
5.Ds node expansion
6.DS installer update

Good idea.


All dropdown lists in settings GUI are getting out of window bounds !!

Windows Terminal version (or Windows build number)
10.0.19042.928
Other Software
No response
Steps to reproduce
Minimal steps to reproduce:
1.) Open the terminal (Not as full screen).
2.) Go to settings GUI and navigate to the appearance tab of either Powershell or Command Prompt
3.) Open any dropdown out of color-schemes, font-face, or font-weight and drag the scroll wheel to see the dropdown's getting out of window bounds.

Expected Behavior
That at least dropdown lists not go out of window bounds, upon scroll event.
Actual Behavior

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #9320 for more discussion.
/dup #9320


[Build] also run Github actions on tag pushes

We need tags to be built on Github Actions for releases.

I am now wondering if there will be a race condition. In this case both master and tag push will be triggered at the similar times. master push should not try to publish.

The releases are only done if $GITHUB_REF is a tag: https://github.com/martinbonnin/apollo-android/blob/e57f3a68841e9d4b3380df44c0946a0719682def/build.gradle.kts#L358
This ensures that only proper tags can push releases


Store and reuse expression result?

Is it possible to somehow store and reuse the result of an expression, instead of having to rewrite the same expression multiple times?

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

ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
Content: Expressions - Azure Pipelines
Content Source: docs/pipelines/process/expressions.md
Product: devops
Technology: devops-cicd
GitHub Login: @andyjlewis
Microsoft Alias: alewis

This would be super useful if possible! I find myself repeating the same expression for "on master branch, not a PR build" multiple times in most build definitions.

@sylveon Please accept our apologies for the delay in getting to this issue. It looks like you had a product question, rather than an issue with the documentation. Here are a few options where you might consider asking your question in the future:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


Extend XRFDC driver for MTS support

MTS logic and documentation included in xrfdc driver
Update xrfclk driver documentation (was outdated)
Add LMK04208 config files for 128MHz and 258MHz (useful for MTS on ZCU111)

hi @dspsandbox - thank you for this nice contribution...
could you remove the .so file?  We rebuild that as part of the sdbuild process.
we are about to release v3.0 and would like to accept this right after in a image_v3.1 branch ... at that point, we'll be able to evaluate and commit on top if we see any issue with a 2022.1 build

Codecov Report

Merging #1384 (6204053) into image_v2.8 (59515a9) will decrease coverage by 1.11%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           image_v2.8    #1384      +/-   ##
==============================================
- Coverage       46.47%   45.35%   -1.12%
==============================================
  Files              28       29       +1
  Lines            4953     5137     +184
  Branches          971     1036      +65
==============================================
+ Hits             2302     2330      +28
- Misses           2594     2748     +154
- Partials           57       59       +2

Impacted Files
Coverage Δ

pynq/utils.py
23.57% <0.00%> (-0.55%)
:arrow_down:

pynq/pl_server/hwh_parser.py
17.24% <0.00%> (-0.41%)
:arrow_down:

pynq/overlay.py
33.48% <0.00%> (-0.16%)
:arrow_down:

pynq/ps.py
100.00% <0.00%> (ø)

pynq/lib/__init__.py
100.00% <0.00%> (ø)

pynq/_3rdparty/xclbin.py
100.00% <0.00%> (ø)

pynq/pl_server/xclbin_parser.py
0.00% <0.00%> (ø)

pynq/pl_server/embedded_device.py
0.00% <0.00%> (ø)

pynq/lib/debugbridge.py
10.86% <0.00%> (ø)

pynq/pl_server/xrt_device.py
29.48% <0.00%> (+0.30%)
:arrow_up:

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Happy to hear that @schelleg,
I have just update the PR.
Best regards,
Pau


Upgrade dependencies

Codecov Report

Merging #290 (41c62b7) into main (d0094bb) will increase coverage by 0.16%.
The diff coverage is 97.50%.

@@            Coverage Diff             @@
##             main     #290      +/-   ##
==========================================
+ Coverage   63.00%   63.17%   +0.16%
==========================================
  Files          64       64
  Lines        4068     4065       -3
==========================================
+ Hits         2563     2568       +5
+ Misses       1144     1137       -7
+ Partials      361      360       -1

Impacted Files
Coverage Δ

schema/csr/csr.go
44.44% <ø> (ø)

pkg/net/coap/client.go
56.62% <80.00%> (ø)

schema/acl/acl.go
100.00% <100.00%> (ø)

schema/pstat/pstat.go
100.00% <100.00%> (ø)

client/maitenance.go
50.00% <0.00%> (ø)

client/observeDevices.go
68.05% <0.00%> (+1.63%)
:arrow_up:

client/onboardDevice.go
74.00% <0.00%> (+1.86%)
:arrow_up:

client/core/disownDevice.go
70.58% <0.00%> (+2.94%)
:arrow_up:

client/core/maintenance.go
70.37% <0.00%> (+7.40%)
:arrow_up:

client/offboardDevice.go
71.42% <0.00%> (+11.42%)
:arrow_up:

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


Add ounce-force/ozf force unit

This unit is extremely common in motor specifications in US when
specifying motor toque using the ambiguous form of oz in, it should
be ozf in to follow lbf for pound force.
I've found this unit so many times and struggled to convert it to something sane like N m or N cm.
Appreciate any comments as I've never written any Purescript.
Hopefully I should be able to run:
1 ozf in -> N cm now .

Unrelated, but README says to run spago test, but when I run it I got:
[error] Module 'Test.Main' not found! Are you including it in your build?

I had to run:
 spago -x test.dhall test

to get it happy.
❯ purs --version
0.14.4
❯ spago --version
0.20.3

Thank you very much.

Unrelated, but README says to run spago test, but when I run it I got:

fixed.


Extract apply_ip_allow_filter

This breaks up the ip allow check in HttpSM::do_http_server_open.

[approve ci fedora]

[approve ci autest]

ip_allow_is_request_forbidden belongs in IPAllow and I tried it that way - it introduced another cyclic dependency which is probably the greater of the two evils.

Test "TSVConnFD" failed with a SIGSEGV (9) on the first run.

[approve ci autest]


Make tile number location and tile rotations consistent with Blackwater Station

http://www.18xx.net/tiles/t00.htm

Make bottom right default with option for bottom left.

After implementing tiles 1-740 and realizing that blackwater station has no consistancy in how it lays out tiles we're canceling this effort and instead writing some rules for how we want to rotate tiles: https://github.com/18xx-maker/games
We will be shoring up those rules shortly. Currently almost all tiles in the 18xx-maker/games repo have been rotated according to those rules and we'll keep that consistant going forward.
Default corner for ID has shifted to lower right since one of our rules is prioritizing not placing track on side 6.


feat: add getDiagnostics function

Adds a function that can be used to retrieve all diagnostics that are present in the provided state. This PR basically addresses this discussion over on discuss.codemirror.net that was originally posted for CodeMirror 5, but since this functionality doesn't exist in the v6 as well, I figured it would be great to finally have it.
Description
What this PR does is add a new function, getDiagnostics that returns all diagnostics that are present within a provided state. To do so, it basically just takes the lintState field and iterates over the generated decorations, collecting the attached diagnostics along the way and returning them as a single array.
This can be used to attach various linters to the state and retrieve them. Users can then afterwards filter them (e.g. look at their source property) and do something with it. This can prove handy for example when you have one or more linters active that probe a file for problems and need to access them outside of the linter function in order to prevent double work.
Rationale
Normally, the action field can be used to define some actions the user can perform to fix or improve the linter error. However, sometimes the potential actions are too many or need to be fetched on-demand. Therefore, it is handy to have a function to quickly retrieve whatever the linters have found and therefore to avoid having to check the file's contents twice.
Example usecase
I've basically moved forward with this because I'm using the built-in linter function to create a custom spell checker (because I can't completely rely on the OS for doing the spell checking).
Said spell checker contains a ton of code to ensure we're spell-checking correctly (i.e. takes into account brackets and custom quote symbols). However, while functionally a spell checker is a linter, potential actions that can be taken are normally provided in a context menu and not via actions like other linters.
In order to avoid having to run the spellchecker twice over the text, one can use this function to retrieve all diagnostics currently attached to the state whenever the user requests a context menu, filter out anything whose source is my spell checker and check if there's a spelling error underneath the cursor position, and provide suggestions as applicable.
Caveats
Currently, this simply takes all diagnostics irrespective of the originating Facets, both because I'm still not comfortably proficient with the use of facets, and because normally the amount of linter errors/warnings/infos should be fairly manageable. Therefore, this PR basically rests on the range iterator being fast.
Also, one could also simply save the decorations manually in the stateField, but I felt this implementation is the least intrusive into the existing code, hence preventing potential other problems.
I tried to stick to the conventions of the repo, but please feel free to outline any potential problems with this implementation and what I can change.
Thank you for your outstanding work – CodeMirror 6 is simply amazing!

Would it work to listen to transactions with the setDiagnosticsEffect and act on the array of diagnostics they provide, instead of formulating this as a state accessor?

It would somehow work, but unnecessarily increase the complexity of the state management.
Utilizing a getDiagnostics accessor as I propose here has the benefit that it changes nothing about either my own code or the linter plugin's code. As soon as I need to actually have a look at those diagnostics, I can access the diagnostics with a single function call.
Furthermore, I am here talking of the use case of some external code taking a look at the state to see if something is in there. For purely internal code that already utilizes StateFields, the effect listener is definitely a viable option.
In the case of external code needing to take a look at the state, the getDiagnostics accessor has, in my view, some benefits:

It does not add any overhead to how the linter works.
It utilizes only what's already in the plugin, i.e. it does not increase either the amount of data stored in the linter plugin, nor of some external code one would have to write to listen to the effect.
It is very simple code-wise and keeps the state management centralized within the plugin.
It makes sense because there is already a setter for diagnostics – having no getter makes it appear that there is some intentionality behind fencing away the diagnostics (the effect listener is not the most straight forward way).

The alternative that you suggest has, if I don't misunderstand anything blatantly (please say so, if I do), several drawbacks for the use-case I'm describing:

If external code needs to look at diagnostics, one has to write an additional StateField that simply collects diagnostics as they are being set by the lint plugin and that can then be queried with view.state.field(customField). This would essentially replicate the changes I propose in this PR with an extra step.
It doubles the amount of diagnostics in the state and increases the risk of introducing bugs
Because anotherStateField has to touch the diagnostics every iteration they change, this imposes a tiny overhead over just accessing them when absolutely necessary
It decentralizes the responsibility: We have a state management in (1) the linter, (2) the custom field, (3) whatever external code needs to look at that.

Or, is there some benefit that the detour via the state effect listener has that I am not seeing here?

If people are going to call this a lot (which is a reasonable thing to do, if it is an exported function), converting the range set to an array again and again is definitely not an example of efficiency. Additionally, the diagnostic objects in the range set may hold positions that no longer correspond to their current position, or even be filtered out entirely, making this a rather error-prone interface that I'm not willing to commit to. See also #7 and #8.

Hm, I've read through #7 and #8 and now I have a few more questions.
You state here as well as in #8 that the diagnostics being returned by that accessor could be outdated if the document has in the meantime been updated and the linter did not (yet) re-run the linter sources. However, if we use an update listener, doesn't this approach have exactly the same issue, just that the (potentially outdated) diagnostics now reside in a different state field ? After all, the effect will only be fired once the sources are all done computing their set of diagnostics. Therefore, any approach in this regard would be somewhat error-prone, except you add even more code to always clean out the diagnostics array when the document changes and wait for the state effect to arrive.
I absolutely agree that the solution advocated for in #7, #8, and #9 does impose some overhead when it comes to iterating over the decoration ranges and re-converting them to diagnostics. The other way to implement this then would be to simply store the diagnostics separately of the decorations instead of attaching them to the specs. Then, returning the array of current diagnostics would add only very little overhead.
I think if the getDiagnostics accessor is properly documented, one should expect users of this to be sane enough to know that, since the linters run not synchronous to state updates, these decorations may be outdated.
Nevertheless, if you decide that it is not worth implementing it as-is, I have another proposal for you that would address the issue you describe and would prevent errors much better, regardless of whether the state management is located within the lint plugin or externalized to custom-written state fields:

Store the diagnostics array as-is in the lintState field (to ease accessing them)
Additionally, divide the diagnostics up in two levels of precision: "Maybe outdated" and "definitely corresponding to the rest of the current state", e.g. currentDiagnostics and oldDiagnostics
Whenever new diagnostics have been calculated, they are written to currentDiagnostics
When the document changes, the diagnostics are moved from currentDiagnostics to oldDiagnostics. As soon as new diagnostics have been computed, they are written to currentDiagnostics, except the state has changed again, in which case they will be directly written to oldDiagnostics
The getDiagnostics accessor receives another parameter, precise (similarly to some other interfaces that CodeMirror exposes which are also somewhat volatile). If precise is true, only currentDiagnostics is returned, even if it is just an empty array because the sources have not yet finished linting the document. If not, oldDiagnostics may also be returned while the linter computes the next batch of diagnostics.

Depending on how much you would be willing to commit to having "outdated" diagnostics stored in the state, we could also just get rid of the second array, which would make the required changes less difficult to implement and would make the accessor definitely return 100% safe diagnostics that are not outdated.
This would have the following benefits:

People do not need to have additional StateFields that do not shield them from the outdating-issue that you describe
External code has an easier way accessing diagnostics on the state
The interface is by default 100% coupled to the state and does not have possibly wrong diagnostics (but it provides the option)
Since this would include greater state management efforts, it is wise to keep that as close to the source of the diagnostics as possible.
We can also expose this API to update listeners so that those people who can use StateFields because they need to access the diagnostics only internally also can be much more certain about the precision of these diagnostics.

Would this be a compromise you're willing to settle on? Given that apparently there now have been three consecutive PRs that all address this one, single issue, I think there are definitely benefits to it, and people find it curious why there is no simple accessor.
If you're willing to give it a shot, I will implement the changes as necessary and update this PR accordingly. I would very much welcome if we could work this out :)

However, if we use an update listener, doesn't this approach have exactly the same issue, just that the (potentially outdated) diagnostics now reside in a different state field ?

Given the nature of transaction effects, the fact that this is a snapshot is be a lot more obvious in the current interface.
The approach with current and old diagnostics seems to complicate the concept without providing much benefit.
An internal iterator that runs a function over the diagnostics rangeset, passing the current position + the original object might be a simple compromise. Would that work for you?

That sounds good. How do you imagine this to be implemented?

Does attached patch look like it'd cover your use case?

Absolutely, yes!

Released in 6.1.0


System requirements update for Windows 11 and Windows Server 2022

This PR updates the system requirements article as requested by defect 417199.

Docs Build status updates of commit 1953109:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV-2017.md
:bulb:Suggestion

Details

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV.md
:bulb:Suggestion

Details

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV-2017.md

Line 29, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 46, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 60, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 73, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 81, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 91, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 104, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 115, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 126, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 137, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 145, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 156, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 165, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 173, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

dynamics-nav/System-Requirements-for-Microsoft-Dynamics-NAV.md

Line 29, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 46, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 59, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 72, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 80, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 91, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 103, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 113, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 124, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 136, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 144, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 155, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 164, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 172, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Documentation is unclear on the matter of language auto-detection.

Here https://github.com/conversationai/perspectiveapi/blob/master/2-api/methods.md#analyzecomment-request
it's said about request's languages field:

If unspecified, the API will auto-detect the comment language.

But this
{"comment":{"text":"some text"},"requestedAttributes":{"TOXICITY":{}}}

doesn't work, as well as
{"comment":{"text":"some text"},"requestedAttributes":{"TOXICITY":{}}, "languages":[]}

and
{"comment":{"text":"some text"},"requestedAttributes":{"TOXICITY":{}},"languages":["en","fr","es","de","it","pt"]}

But I do get a response with a single language:
{"comment":{"text":"some text"},"requestedAttributes":{"TOXICITY":{}}, "languages":["en"]}

What is the correct way to write a request with auto-detection?

Well, after a little bit of digging it looks like the correct way to auto-detect is
{"comment":{"text":"some text"},"requestedAttributes":{"TOXICITY":{}}}

but auto-detection sometimes fails with LANGUAGE_NOT_SUPPORTED_BY_ATTRIBUTE.
E.g "yo hamburger" is auto-detected as Turkish. But TOXICITY doesn't support Turkish... Wouldn't it be reasonable to limit the auto-detected languages to the supported ones?

Same problem here

Hi there!
We tested out the example commands, one with an empty list for languages, and one with language missing, and both work. We're in the midst of updating documentation, but here are some pointers in the meantime: One language will be detected per comment. You can either use language detection or specify a single language. Alternatively, you could make separate calls with different languages in each. Language detection won't run if you specify a language. If you specify a language that doesn't match what's in the comment, the score might not make sense. If you feel confident you know the language of your text, you'll get a better outcome to identify the language rather than run autodetection.


Zooz ZEN22 Device FW Gap

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
I have several Zooz ZEN22 dimmers and I can see on PR #1667 the supported firmware information was refactored.
During this refactoring, the support now goes FW 1.0-1.4, FW1.5-1.5, FW1.7-1.7 FW3.0-3.0., etc.
This leaves out FW1.6 which leads to an unknown manufacturer and no configurable settings within Hone Assistant.  It would appear that prior to this PR, any FW of 1.0-1.6 would have full functionality, but labels would not align.
Device information
Manufacturer: Zooz
Model name: ZEN22 (FW 1.6)
Node ID in your network: 2,4,5
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version: 0.1.45
node-zwave-js branch:
zwavejs2mqtt branch:
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
I was previously on OZW where this worked.
Attach Driver Logfile
2021-10-08T21:59:59.656Z CNTRLR « [Node 006] has switch type Down/Up
2021-10-08T21:59:59.656Z CNTRLR » [Node 006] requesting current switch state...
2021-10-08T21:59:59.670Z SERIAL » 0x01090013060226022544a4                                            (11 bytes)
2021-10-08T21:59:59.671Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id:      68
└─[MultilevelSwitchCCGet]
2021-10-08T21:59:59.676Z SERIAL « [ACK]                                                                   (0x06)
2021-10-08T21:59:59.678Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2021-10-08T21:59:59.679Z SERIAL » [ACK]                                                                   (0x06)
2021-10-08T21:59:59.680Z DRIVER « [RES] [SendData]
was sent: true
2021-10-08T21:59:59.767Z SERIAL « 0x010500134400ad                                                     (7 bytes)
2021-10-08T21:59:59.768Z SERIAL » [ACK]                                                                   (0x06)
2021-10-08T21:59:59.769Z DRIVER « [REQ] [SendData]
callback id:     68
transmit status: OK
2021-10-08T21:59:59.836Z SERIAL « 0x010b00040006052603636300d6                                        (13 bytes)
2021-10-08T21:59:59.838Z CNTRLR   [Node 006] [~] [Multilevel Switch] targetValue: undefined => 99   [Endpoint 0]
2021-10-08T21:59:59.839Z CNTRLR   [Node 006] [+] [Multilevel Switch] duration: {"value":0,"unit":"s [Endpoint 0]
econds"}
2021-10-08T21:59:59.840Z CNTRLR   [Node 006] [+] [Multilevel Switch] currentValue: 99               [Endpoint 0]
2021-10-08T21:59:59.840Z SERIAL » [ACK]                                                                   (0x06)
2021-10-08T21:59:59.842Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 99
target value:  99
duration:      0s
2021-10-08T21:59:59.848Z CNTRLR   [Node 006] [+] [Multilevel Switch] interviewComplete:  [Endpoint 0] [internal]
true
2021-10-08T21:59:59.854Z CNTRLR   [Node 006] Interviewing Configuration...
2021-10-08T21:59:59.854Z CNTRLR   [Node 006] ConfigurationCC: skipping interview because CC version is < 3 and t
here is no config file
2021-10-08T21:59:59.855Z CNTRLR   [Node 006] [+] [Configuration] interviewComplete: true [Endpoint 0] [internal]
2021-10-08T21:59:59.856Z CNTRLR   [Node 006] Interview stage completed: CommandClasses
2021-10-08T21:59:59.856Z CNTRLR   [Node 006] Interview stage completed: OverwriteConfig
2021-10-08T21:59:59.857Z CNTRLR   [Node 006] Interview completed
2021-10-08T21:59:59.858Z CNTRLR   [Node 006] The node is ready to be used

It looks like there was only one change at 1.6:
VER. 2.02 (released 4/2018)
Firmware: 1.06
Added OTA firmware updates
Added ramp rate control (slow / fast only)


Is this project still alive?

Hello everybody
I follow this project for many years and was really hopeful in early 2019, when @jprochazka set up the new adsbreceiver.net website and discourse group. I am really thankful for this piece of software but I think development has ceased and we have not heard anything from him for a long time. So I had to move on to the custom image from ADS-B Exchange but I still think adsbreceiver has potential, it just would be good to know if Joe really abandoned this project or if he will eventually come back.

The project look to be belly-up.
@jprochazka has not logged any activity on GitHub since May 14 2019.
To make things worse, https://www.adsbreceiver.net/ shows an expired certificate (valid until Dec. 31st 2019).

did you guys find any alternatrive?

@etamtlosz  Yes, the ADSBx Custom Pi Image from adsbexchange.com can be flashed on a SD card. You just need to enter your coordinates and meters above sea level and are good to go.
https://www.adsbexchange.com/how-to-feed/adsbx-custom-pi-image/
It does use tar1090 and has some nice features such as toggles to show military aircraft only.
Additionally, it is based on Raspbian Buster and does even support the RPi 4B.

My problem is that I'm using the manual install, not the SD card version. I'm running my servers on an IBM server. Until now, I didn't find any good solution to emulate raspberry HW on proxmox.

I do hope this project doesn't get abandoned in favour of a Raspberry Pi image.
My ADSB-Receiver setup runs on Armbian on a Banana Pi M2 Zero. It'll never work with a Raspberry Pi image.
In many ways the Pi clone ecosystem and Armbian innovate faster than the Raspberry Pi foundation. In the foundations defence though they put more effort into standardisation and support.
I have similar hopes to what @etamtlosz is doing. I'd like to move my setup to the big rackmount server in the house, but in the meantime it'll continue running on non-RaspberryPi hardware. It might stay that way forever though, given that I also want to put the antenna up high and the Pi may join it in an IP67 box on the mast.

If anyone figures out how to get a reliable USB connection on Proxmox that supports MLAT, please holler.
In the meantime, https://github.com/mikenye/docker-readsb/wiki/Guide-to-ADS-B-Data-Receiving,-Decoding-and-Sharing,-Leveraging-RTLSDR-and-Docker

What's wrong with MLAT on proxmox?

Clock issue. Totally unreliable. There’s a fix for virtualbox, but haven’t found anything yet for Proxmox.
https://discussions.flightaware.com/t/server-status-clock-unstable/19482/24

Seems to be abandoned, what a pity!

Seems to be abandoned, what a pity!

Yes, it does seem to be. But check out the mikenye github that I linked to above - it’s all picked up there and via docker. Super easy!

the Mike is very active on discord as well. He's answering pretty fast to any question, problem.

Can confirm, Mike is great.
I have my own little docker-compose adsb-stack comprised of all of his docker work over at https://github.com/kylegordon/adsb-stack - my work isn't 100% yet, but it's getting there

I have actually started back to work on the project after a long down time. I am currently working on getting existing items up to date and working once more. The work is being done in the phoenix branch at this time.


EE-1948 - Added JSON schemas of ArrayExperiment and ArrayAssay

Added a new folder 'schemas/' to the main directory, containing new JSON schemas for ArrayExperiment and ArrayAssay, along with the 'common' JSON schemas.
Also added a README to the new folder and some JSON datafiles that are intented to fail or pass validation based on the code on a jupyter notebook in the same folder.
See ticket: https://www.ebi.ac.uk/panda/jira/browse/EE-1948

Hi @Dona094:

README File- Apart from minor typos in the overview section everything looks good to me.

I have fixed 2-3 typos, but since you didn't mention exactly which ones you were referring to... I don't know if there are more that I didn't notice.

Just a small suggestion if the "Planning to modify the schemas section" could be simplified a bit say by explaining further with an example link of how the cross-file references are achieved as it can be slightly confusing for the first time

Added a bit more text explaining it and also added examples.
Let me know if this suffices 😄

Hi @Dona094:

README File- Apart from minor typos in the overview section everything looks good to me.

I have fixed 2-3 typos, but since you didn't mention exactly which ones you were referring to... I don't know if there are more that I didn't notice.

Just a small suggestion if the "Planning to modify the schemas section" could be simplified a bit say by explaining further with an example link of how the cross-file references are achieved as it can be slightly confusing for the first time

Added a bit more text explaining it and also added examples.
Let me know if this suffices 😄

Sorry, my bad I did not mention the specific typos. Checking now, just seeing one that is differenciate under Shared definitions which should be differentiate I think. Many thanks for the detailed section now on the Planning to modify the schemas. Really comprehensive 😊

Thanks for your review, @ainacrg!
As has been mentioned before I expect those typos to appear a lot, since I copy-pasted many parts of the text and the typo-checker was disabled 😓
I'll answer your questions individually in a minute and group all feedback to correct the schemas in new commits.


Use meaningful domain type locations/imports

Currently many "types" are in esssans.types, and we use from esssans.types import *. Apart form wanting to avoid the import *, types is also meaningless to scientists. Therefore:

Move important types to the package root (import in __init__.py), avoid import *.
More special or internal types should move to meaningful submodules.

Why would you use Filename from iotypes? Filename should be imported in the top-level __init__.py, since it is commonly used by users.

To reiterate form previous discussions:

Define where it makes sense (use your judgement), might be in local file defining providers.
types should not be exposed to users.
"Relevant" types get imported in top-level __init__.py.
Details have to be imported from their submodules.

Filename should be imported in the top-level init.py, since it is commonly used by users.

I've tried a couple of things, but I can't seem to get around having to have a long
from esssans import (
    Filename,
    SampleRun,
    BackgroundRun,
    TransmissionRun,
    EmptyBeamRun,
    WavelengthBins,
    WavelengthBands,
    CorrectForGravity,
    UncertaintyBroadcastMode,
    ReturnEvents,
    QBins,
    PixelMaskFilename,
    BackgroundSubtractedIofQ,
)

at the start of the notebook. Was that the intention?
Another thing: without the import *, if I want to inspect an intermediate result that I look up in the task graph, I now have to import that type before I can look at the data
from esssans.types import MaskedData
masked = pipeline.compute(MaskedData[SampleRun])

which degrades usability I think.
I know we don't like the import *, but I feel the aternative should not lower usability this much?

It is your choice to import *, but I don't feel we should adopt that practice in the docs?

It is your choice to import *

Sure, but that becomes very difficult if the types are scattered over many files/submodules internally.
So unless we find a better alternative, I might suggest to have, for every submodule, a single place where we put all the types (and we don't have to call it types if you think the name doesn't make sense to scientists).
This would allow you to do:
from esssans.types import *
from esssans.loki.types import *

and you would have all you need if you are working with Loki. We would then not have any types in the other files in the loki submodule.
I agree that we should leave it out of the docs :+1: , but I think you should still be able to use it because it is very convenient?

It is your choice to import *

Sure, but that becomes very difficult if the types are scattered over many files/submodules internally.
So unless we find a better alternative, I might suggest to have, for every submodule, a single place where we put all the types (and we don't have to call it types if you think the name doesn't make sense to scientists).
This would allow you to do:
from esssans.types import *
from esssans.loki.types import *

I really don't see why we need types. Can't almost all relevant bits be in the relevant module?
from esssans import *
from esssans.loki import *

Can't almost all relevant bits be in the relevant module?

In theory, yes,
But it's inconvenient if I want to inspect an interediate result which is not imported at the submodule top level, and the type is burried in e.g. esssans.loki.masking.
A user would either have to grep the source (most won't know where to find it in their conda/pip environment), or search the docs API to try and find the correct submodule?
Inspecting intermediate results will be very common in hot commissioning.

Regarding not being able to easily find the full path to a type when looking at a task graph:
I also tried adding 'fake' url to the types nodes, where you could right-click on the svg and do "copy link address", but instead of a http url it would just be the full type path that you could then paste back into your notebook and use compute on.
While being a simple fix in sciline, chrome seems to just plainly block those urls. Firefox allows them but pre-pends the local folder path which means you get file:///home/nvaytet/code/sans/jupyter/esssans.types.Filename[esssans.types.SampleRun] instead of esssans.types.Filename[esssans.types.SampleRun] :-(

The conclusion was that we will wait with this until we have more experience with more workflows. Moving to blocked.


Removed extra spaces in footer.hbs

Fixes #1480

Please rebuild travis , I think the issue was with travis itself as it stopped during npm install only.


Populate shipyard queue on resources page for solar satellites

Fixes:

#457

Remaining todo's:

[ ] When solar satellite are building, when one unit is done the actual unit count is not updated on the resources page. This does work when building units from shipyard/defense page. Check what is missing to make this work.

Will close #457 and fixes additional bugs reported in #405


Request Feature : Import/Export or Backup

Thank you for this task apps :)
Can you add an option to backup and restore in xml for exemple :)

That's already covered by #170
We'll take care of that after finishing recurring tasks.


pmd: 6.29.0 -> 6.30.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/pmd/versions.
meta.description for pmd is: "An extensible cross-language static code analyzer"
meta.homepage for pmd is: "https://pmd.github.io/"
meta.changelog for pmd is: "https://pmd.github.io/pmd-6.30.0/pmd_release_notes.html"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.30.0 with grep in /nix/store/k61i48jzvcvmihv5fbr3w686w7rf9nj8-pmd-6.30.0

directory tree listing: https://gist.github.com/02aefcf451f91a38e32e55c396709644

du listing: https://gist.github.com/2739c0ac8a0e59839286828945859d35

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

4431 total rebuild path(s)

1663 package rebuild(s)

1658 x86_64-linux rebuild(s)
1433 i686-linux rebuild(s)
440 x86_64-darwin rebuild(s)
900 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
apache-airflow
archi
avocode
aws-adfs
aws-google-auth
aws-sam-cli
awscli
awsebcli
awslogs
barman
bash-my-aws
bpftool
buildbot
buildbot-full
buildbot-ui
bumblebee
cargo-flamegraph
certbot-full
checkov
chrome-gnome-shell
chromedriver
chromium
cloud-custodian
cq-editor
credstash
crosvm
csvs-to-sqlite
deja-dup
displaylink
duplicity
duply
dvc-with-remotes
elasticsearch-curator
epiphany
feeds
freefall
geekbench
git-annex-metadata-gui
git-remote-codecommit
gnome-tour
gnome-usage
gnome3.epiphany
gnome3.geary
gnome3.gnome-applets
gnome3.gnome-calendar
gnome3.gnome-clocks
gnome3.gnome-contacts
gnome3.gnome-control-center
gnome3.gnome-initial-setup

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
NixPkgs review skipped

Maintainer pings

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

1 package built:

pmd

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

1 package built:

pmd


CPP: Deprecate PotentialBufferOverflow.ql

Deprecate PotentialBufferOverflow.ql.  Everything it does is done by OverrunWrite.ql and OverrunWriteFloat.ql together, and the latter support a much wider variety of functions.  I can't find any real world results unique to PotentialBufferOverflow.ql (https://lgtm.com/query/1401438515475863559/).
In addition, despite appearances, the claim in the qhelp that PotentialBufferOverflow.ql covers uses of vsprintf is false (because they're outside the scope of FormattingFunctionCall).  I may at some point get around to making OverrunWrite.ql support that, but we're not losing anything right now.

Is PotentialBufferOverflow referenced in a query suite?

Is PotentialBufferOverflow referenced in a query suite?

It's only in the security suite, which I've updated in this PR.  Surprisingly it was not included in samate.py.


Tracing additional information when NuGet restore fails

Tracing additional information to help diagnose NuGet restore failures.

:ship:


Graph opacity is faded when animated = True

Pretty basic setup. Pan gesture isn't enabled
<Box height={350}>
  <LineGraph
      style={styles.chart}
      points={dataPoints}
      color={colors[accentColorTheme]}
      lineThickness={2}
      animated={true}
    />
</Box>

When animated={true}

When animated={false}

Setting enablePanGesture={true} solved it for me

Facing the same issue. Did you find any solution to that?

Ah yes, that's a bug! Maybe https://github.com/margelo/react-native-graph/pull/14 fixes this?

@mrousavy Thanks for looking into this. Setting the initialIndex in that PR would fix it yeah. However, I'm not sure if initialIndex needs to be a prop. Highlighting 100% of the chart should just be a default behavior for the initial render and when there is no ongoing gesture.
The PR could be a temporary solution though. Are you planning to approve it?

@mrousavy actually this fixes it. Could you just release an update? Thanks!

The solution above technically fixes it. However, it breaks the initial fingerX position after the hold. The right fix for it is to move the check into the setFingerX callback
pathEnd.current = isActive.value ? fingerX / width : 1

I recommend you revert that solution and put this one in instead


Can't transpile code residing on network share using node module resolution

I am experiencing problems when trying to build a TypeScript project which resides on one of our network shares. I am using Windows 7.
The problem only occurs when using node module resolution and seems to be related to the mapping of network drives to UNC paths.
Suppose I have the following setup:
A drive X: mapped to \\server\projects with a folder test containing my files.
TypeScript Version:  2.0.6
Code
// module.ts
export interface A {}

// index.ts
import { A } from './Module'

// tsconfig.json
{
 "compilerOptions": {
  "target": "es2015",
  "module": "commonjs"
 }
}

Expected behavior:
No errors.
Actual behavior:
======== Resolving module './module' from 'X:/test/index.ts'. ========
Module resolution kind is not specified, using 'NodeJs'.
Loading module as file / folder, candidate module location 'X:/test/module'.
File 'X:/test/module.ts' exist - use it as a name resolution result.
Resolving real path for 'X:/test/module.ts', result 'UNC/server/projects/test/module.ts'
======== Module name './module' was successfully resolved to 'UNC/server/projects/test/module.ts''. ========
index.ts (1,24): error TS2307: Cannot find module './Module'.

Looks like a duplicate of https://github.com/Microsoft/TypeScript/issues/9552 and https://github.com/Microsoft/TypeScript/issues/11613. Should be fixed by https://github.com/Microsoft/TypeScript/pull/12020


Add touch/stylus support to side panel resizer

The draggable bar that is used to adjust the width of the side panel bar should work with touch or stylus based interactions such as on tablets, phones or convertible laptops.
Currently, it can only be dragged with a mouse.

Nice catch! I agree.

From ChatGPT 4:
To make the drag interaction of your split pane resizer component work on touch screens, you'll need to add touch event listeners in addition to the existing mouse event listeners. The primary touch events you'll want to handle are touchstart, touchmove, and touchend.
Here's how you can modify the existing code to include touch event handling:

Add Touch Event Handlers: Similar to onMouseDown, onMouseMove, and onMouseUp, create corresponding touch event handlers: onTouchStart, onTouchMove, and onTouchEnd.

Adjust Event Handling Logic: Touch events have a different structure than mouse events. For instance, the clientX position is obtained from event.touches[0].clientX in a touchmove event.

Bind and Unbind Touch Event Listeners: In the useEffect hook where you're adding and removing mouse event listeners, do the same for the touch event listeners.

Here is an example of how you might modify your component to handle touch events:
// ... (existing imports and code)

export const VZResizer = ({ side }: { side: Side }) => {
  // ... (existing useContext and useRef hooks)

  // Modify existing onMouseDown
  const onMouseDown = useCallback((event: React.MouseEvent | React.TouchEvent) => {
    event.preventDefault();
    const clientX = event instanceof MouseEvent ? event.clientX : event.touches[0].clientX;
    previousClientX.current = clientX;
    setIsDragging(true, side);
    document.body.style.cursor = 'col-resize';
  }, [setIsDragging, side]);

  // New onTouchMove handler
  const onTouchMove = useCallback((event: TouchEvent) => {
    event.preventDefault();
    const clientX = event.touches[0].clientX;
    const movementX = clientX - previousClientX.current;
    previousClientX.current = clientX;
    moveSplitPane(movementX, side);
  }, [moveSplitPane, side]);

  // ... (modify existing onMouseMove and onMouseUp to handle both mouse and touch events)

  useEffect(() => {
    if (isDragging) {
      document.addEventListener('mousemove', onMouseMove);
      document.addEventListener('mouseup', onMouseUp);
      document.addEventListener('touchmove', onTouchMove, { passive: false });
      document.addEventListener('touchend', onMouseUp);
      return () => {
        document.removeEventListener('mousemove', onMouseMove);
        document.removeEventListener('mouseup', onMouseUp);
        document.removeEventListener('touchmove', onTouchMove);
        document.removeEventListener('touchend', onMouseUp);
      };
    }
  }, [isDragging, onMouseMove, onMouseUp, onTouchMove]);

  // ... (rest of the component)
};

In this modification:

onMouseDown is now handling both mouse and touch start events.
onTouchMove is specifically handling the touch move event.
The useEffect hook is now also setting up and cleaning up touch event listeners.

With these changes, your resizer should be functional on both mouse-driven and touch-driven devices. Remember to thoroughly test on various devices to ensure compatibility and usability.


scheduled race time zone

Looks like the server manager is working in gmt even if the user isn't. Get the time zone from the user.


UML-2779: Adding new event codes for type of LPA

Purpose
https://opgtransform.atlassian.net/browse/UML-2779
Fixes UML-2779
Approach
Explain how your code addresses the purpose of the change
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the Use a Lasting Power of Attorney service
Checklist

[X] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] New event_codes have been documented on the wiki page
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] I have added welsh translation tags and updated translation files
[ ] I have run an accessibility tool on any pages I have made changes to and fixed any issues found
[ ] I have notified the Interaction Designer of any content changes so that appropriate screenshots/flow diagram changes can be made
[ ] The product team have tested these changes


Threat Intelligence playbooks with key vault to hold Client-Secret instead of Logic App SecureString

Change(s):
MDTI-Base

Create the MDTI-Base Logic App with a System-Managed Identity
Create a Key Vault with RBAC permissions, assign a user to the Key Vault Administrator role (you must provide the AzureAD Object ID for that user), and assign the MDTI-Base System-Managed Identity to the Key Vault Secrets User role
Store the Client-Secret in the Key Vault, remove the built-in Logic App SecureString Client-Secret, and create a connection to the Key Vault from MDTI-Base
Make use of the built-in Logic App Parameters menu pane for all other parameter values, rather than requiring users to modify values in the Code View

MDTI-Automated-Triage
MDTI-Data-WebComponents
MDTI-Intel-Reputation

Secure Inputs for HTTP REST and Secure Output for MDTI-Base actions

Reason for Change(s):
enable more secure Client-Secret storage and retrieval, along with better user experience via Parameters menu for non-Secret variables and not requiring template redeployment on Secret update
Version Updated:
1.0.1
Testing Completed:
Yes
Checked that the validations are passing and have addressed any issues that are present:
Yes

Hello @mr-mongo if you have repackaged the solution please upload the zip and other solution content as well

@v-prasadboke ahh, yes. sorry.
it looks like the package ZIP version should be bumped to 2.0.3? I see version 2.0.2 being available in the Content-Hub in Azure, even though i dont see that version in Microsoft Defender Threat Intelligence/Package

@v-prasadboke api version date 2017-07-01 updated to 2019-05-01

Hello @mr-mongo please fix the validation error


Advance picture flashes in negative when advance screen fades

As title, on the "wise men discover" screen, all displays correctly until after the advancement description screen. As the screen fades, the advancement image inverts colours.

The palette for the civilopedia screen is a merged palette of two PIC files. The screen fade out code uses the original colours of the default palette, unmixed with the Advance Picture palette. That's why the colours change.
I've made a solution for this.


[CORE] Statement level controls whether to use gluten

Description
Currently， spark.gluten.enable is control by spark session. Some times, gluten returns wrong results, we need to quickly fall back to the version without gluten, and statement-level control is required.

It looks useful. We need to support changing this config by respecting user's set statement at runtime. And we may also need more work to fully control Gluten's usage to align with this config.


Fvwm: add gestures and create libstroke package

This adds libstroke so that fvwm can be compiled with gesture support, as well as a flag to enable it in fvwm.
This is my first non-trivial contribution, so is largely pattern-matched from existing packages.  Feedback is welcome.

I think since libstoreke is small, just add it to fvwm is enough.
Anyway, look good to me.  OK to merge?

@iyzsong - I don't quite follow.  Are you suggesting that gestures should be enabled by default?  I'd be fine with that; I was just trying to make this as non-intrusive as possible (and figure out if I'm doing flags correctly).  Otherwise, I think it's ready to merge.

Yeah, I think the gestures option is not worth adding.
Anyway, thanks!