Initial commit of the density inversion test

We present here an additional test within the QARTOD module which corresponds to the QARTOD Test 13 Density Inversion Test.

This implementation can be applied to both up, down, and up&down cast situations, which can be handy in CTD profiling and trajectory profiling applications like Rosette deployment, stand-alone CTD instruments profile, glider, AUV, automated profilers (ex: Argo program), and towed instrumentation.
The test is very similar to the ARGO density inversion test and respects the QARTOD codable instructions.
QARTOD documentation suggests that flag results can only be flagged as GOOD(1) or BAD(4), ignoring the SUSPECT (3). We also provide more flexibility to the user by also providing a non-mandatory SUSPECT threshold value.
The same test could live potentially within eh ARGO module. I'll leave to the ioos_qc community the decision if it makes sense to leave it within the QARTOD module, or move it to the ARGO module.

Thanks @JessyBarrett! The CI failures were in master (fixed now) and not in this PR.
Could you please add a test that uses the density inversion tests? See the other QARTOD tests for examples. After that this looks great!

Awesome! Yes I can certainly do that!

Awesome! Yes I can certainly do that!

I think those tests should cover most the potential issues that could be encountered. I aslo found some issues with the density_inversion_test itself which were corrected. Let me, know if you find any issues with it!

I think those tests should cover most the potential issues that could be encountered. I aslo found some issues with the density_inversion_test itself which were corrected. Let me, know if you find any issues with it!

@JessyBarrette The test_density_inversion_bad_depth_value test is failing in CI and for me locally. The check is catching warnings when converting the depth so I don't think this warning will ever happen.
We could move the zinp masking outside of the with warnings... block or remove the warning check from the test... up to you!

@JessyBarrette The test_density_inversion_bad_depth_value test is failing in CI and for me locally. The check is catching warnings when converting the depth so I don't think this warning will ever happen.
We could move the zinp masking outside of the with warnings... block or remove the warning check from the test... up to you!

I dug a little deeper, I think the Warning you were trying to catch was unrelated to the None value in depths. It was coming from the usage of .astype(np.floating) which is producing:
DeprecationWarning: Converting `np.inexact` or `np.floating` to a dtype is deprecated. The current result is `float64` which is not strictly correct.     return array(a, dtype, copy=False, order=order)
The usage of .astype(np.floating) is prolific in the codebase and I will change to np.float64 in another PR!

I dug a little deeper, I think the Warning you were trying to catch was unrelated to the None value in depths. It was coming from the usage of .astype(np.floating) which is producing:
DeprecationWarning: Converting `np.inexact` or `np.floating` to a dtype is deprecated. The current result is `float64` which is not strictly correct.     return array(a, dtype, copy=False, order=order)
The usage of .astype(np.floating) is prolific in the codebase and I will change to np.float64 in another PR!

Thanks Kyle for your corrections! I was thinking of adding a warning in the density_inversion test itself when zinp is missing a value and forgot to add the warning in qartod.density_inversion_test.
Looks like you dropped that warning that's great, I guess it follows more what's been done with the other tests.  thanks again!

Thanks Kyle for your corrections! I was thinking of adding a warning in the density_inversion test itself when zinp is missing a value and forgot to add the warning in qartod.density_inversion_test.
Looks like you dropped that warning that's great, I guess it follows more what's been done with the other tests.  thanks again!


Update README.md

Added milestones
Added timings of delivery of milestones

@awmacpherson look OK? Anything to add or correct?


Allow employees to select a project when clocking in

In the clock in form, the user should be able to choose from the jobs associated with the client they are working for.

Closed in #58


Feature? make errorsWrapper and errorsTemplate empty

I have the following options:
@options =
    priorityEnabled: true
    errorClass: 'error'
    errorsWrapper: ''
    errorTemplate: ''
    errorsContainer: (ParsleyField) =>
       ParsleyField.$element.parent().next()

As I am defining the errorContainer by myself, I already have the markup I need to display the error message. So I don't need extra tags in errorsWrapper and  errorsTemplate defined. But when leaving them blank like errorsWrapper: '', the error message will not be displayed.
I suggest to make this possible. This would for sure require the dependency to a defined errorsContainer.

You can have more than one error on one field, so having an empty template seems like a bad idea.
Moreover in many places in the code, the wrapper and templates are expected to be a DOM elements.
Closing, will reopen if you can show actual problems with having those  like in your example.


"Read more" button sometimes does not show up

@Onions keeps complaining to me in SimpleX DMs that there is a bug with "Read more" where it doesn't show up. Then I told him: "Why don't you just create a ticket and help us helping you?"
 So I said sorry, I am going to create one now and here I am, creating this ticket for him.
For example, he goes to preview, and then he can't see everything because it's hidden and there isn't even that button (happens only sometimes, I think).
I just had this bug on my own profile even since my profile isn't even that long but it still seemed to want to display the button but there was no button.
Probably a race condition somewhere.
Github should really allow anon tickets, lol. Can't expect everyone to have an account on here.

caught the bug:
https://github.com/stackernews/stacker.news/assets/27162016/d11620e4-3517-4ddb-9748-4444507c7afc

This might be fixed now

Ok will let you know if it happens again within a week
Since I think it did happen frequently enough that if it doesn't happen in a week, it's probably fixed and we can close it :)
Thanks for the fix!

I think this is ultimately related to images causing the container height to change after they load. My more recent fix observes the container size for changes which I think solves this once and for all.


Add Frame.dropSparseRowsBy

Adds dropSparesRowsBy column functionality. This should make it easier for users to deal with missing values in specific columns, e.g., before grouping by those columns (as suggested by @tpetricek in #380).

Thanks for the new function. It will be very handy to use. Could you add some unit tests under Deedle.Tests\Frame.fs, similar to the current tests of Frame.dropSparseRows?

Sure, will try to do so later today.

Looks good to me! Thanks.


onionshare: fix build failure

Description of changes

change url_quote dependency since it imports from a deprecated werkzeug vesrion

add setuptools

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

[X] Tested basic functionality of all binary files (usually in ./result/bin/)

24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1469

Is this from an upstream PR? If not we should try to upstream this.


[JS] IAdaptiveCard interface has an incomplete list of allowed types for body

Target Platforms
NodeJS
SDK Version
2.9.0
Application Name
SharePoint
Problem Description
https://github.com/microsoft/AdaptiveCards/blob/main/source/nodejs/adaptivecards/src/schema.ts#L169
IAdaptiveCard.body has type (ITextBlock | IImage | IImageSet | IFactSet | IColumnSet | IContainer)[]
This is missing a IRichTextBlock element, which doesn't exist yet (issue here), and all the IInput elements.
Screenshots
No response
Card JSON
n/a

Sample Code Language
No response
Sample Code
No response

Addressing this issue is not currently on our roadmap, so closing. Please feel free to continue the conversation in this issue for future consideration.


Running the steps in python 3

Hi!
Great code and article!
Excellent idea :)!.
Just trying the code in a jupyter notebook with python 3 and i am not sure i am doing it right.
The last error i have is.

yer, I was trying to run your code step by step to understand it.
Its a brillant piece of thinking.
Whats the order to run it.
Just download the raw data set and move through each piece of code.

The order would be to sort_train and then validate as needed.


(1) Input fields for Add User should not show errors until after the user has finished typing

Steps to Repro:

got to Users
click Add

Right now, it appears with input errors without the user ever typing.

QA: LGTM


Segments

Implemented features:

Implemented click functionality for table row @Abdoul111
Segmented runs  @Abdoul111
Calculated the average speed and slope for each segment @danbin @BDW12
Stored Segments in a list to facilitate their display in the table OSMDashboard @maianh2611
Retrieved information about the start and end of segments from the URI provided by OpenTracks @serbancaia
Highlighted the corresponding segment when a user clicks on a segment row @B-Mousa
Implemented RecyclerView to enhance application performance @Abdoul111

I already reviewed it and everything works fine on my end.

Reviewed and Verified, all is working good for me.

I reviewed it on my part, and all looks good.

I reviewed it, everything works on my part.


send the same message twice

What is your Quests version / build number (do not say "latest")?
Quests 4.00-rc.4-b206

Describe the problem and how to replicate it. Any console errors to post using a pastebin?
When I ask for the id of a npc, while editing a quest by clicking on the npc, I see the message twice.
I also have this problem when a time limit before resuming the quest is set.
I just click one time

Already resolved in the latest development build (not compatible with QuestsGUI):
https://ci.codemc.io/job/PikaMug/job/Quests/


reolink 811a stream not compatible

Hello,
reolink 811a stream is not compatible ?
I use go2rtc with frigate + chrome Version 120.0.6099.129 (Build officiel) (64 bits) on Linux Debian 12
go2rtc:
streams:
clim:
- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@<IP_ADDRESS>:554/h265Preview_01_main
M

https://github.com/AlexxIT/go2rtc#source-rtsp

I have only sound

https://github.com/AlexxIT/go2rtc#codecs-madness

thank


Exception in 112.3 - URGENT

Exception seen on first starting 112.3
2020-07-07 06:56:29 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/mitemp_bt/sensor.py", line 775, in update_ble
    discover_ble_devices(config, aeskeys, whitelist)
  File "/config/custom_components/mitemp_bt/sensor.py", line 683, in discover_ble_devices
    sensors[t_i], mac, config, temp_m_data[mac]
  File "/config/custom_components/mitemp_bt/sensor.py", line 499, in calc_update_state
    entity_to_update.schedule_update_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 416, in schedule_update_ha_state
    assert self.hass is not None
AssertionError

I have dropped this code in around the culprit
            try:
                entity_to_update.schedule_update_ha_state()
            except:
                _LOGGER.debug("BPO -- Sensor %s not yet ready for update", sensor_mac)
                success = False
            success = True

I'm seeing this in the log
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D8E0D8 not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D8E0D8 not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D8E00C not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D8E00C not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8DC8A9B not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8DC8A9B not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D9591A not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] BPO -- Sensor 4C65A8D9591A not yet ready for update
2020-07-07 07:28:48 DEBUG (SyncWorker_10) [custom_components.mitemp_bt.sensor] Finished. Parsed: 1563 hci events, 5 xiaomi devices.

Note I just copied a log message so I got something on the exception 😀.
HTH

Same error on my side but on 0.112.2.
And the quick fix makes it work again as well.

Apparently there is a fix in the system somewhere.  Glad I could help.


Collapsed guide navigation is not accessible

We need to update the pattern so it's similar to how we do our progressive disclosures, which adds attributes to tell assistive technologies what state it is in, expanded or not.
https://youtu.be/b5S6t_0ijY4
Seen at https://www.gov.uk/become-lorry-bus-driver

I think that the move of mainstream formats to government-frontend fixed this issue. Please reopen if that's not the case.


Feature Request: List Sharing

It would be nice to be able to create lists as a seperate item.
This would simply be a name, description and list of links.  This way you could then share this list externally.
The use case is when writing reference articles it would be nice to embed the linkding shared link which contains the external references.  The added benefit is if you have the archive.org option selected you can get a point capture of that document in case links move in future.
This could be very useful for presentations, conference links

@stonesbg One possible solution for this could be to make tags shareable, at the end of the day a tag is a list of links.

I think this is already possible:

Tag all bookmarks with a specific tag
Search for that tag
Use bulk edit to mark all bookmarks as shared
Go to the shared view, search for same tag
Copy URL and share that with external users


bug: Inconsistent image tagging in Helm chart appVersion

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Chart
dex
Version
v2.37.0
Expected Behavior
Consistent tagging between appVersion and image tag between Chart.yaml and values.yaml.
Actual Behavior
Currently, releases contain Helm charts which have Chart.yaml appVersion: "X.YY.Z". But the values.yaml tag references a different format (vX.YY.Z), also instructing users that if you don't specify anything, the appVersion is used.
We are automatically updating upstream charts with PRs which are automatically opened in our internal repos, this behavior impedes us.
Please help. Thank you.
Steps To Reproduce
No response
Additional Information
No response
Values
No response

Although this is taken care of in the deployment template here, I agree it would be easier to use the same tag as version.
I'm not entirely sure I understand how it impedes you, though.

Don't get me wrong, it ca be vX.Y.Z or X.Y.Z, but at least consistent between the Chart.yaml and index.yaml

You mean git tag and appVersion, don't you?

So probably also that would have to be unified as well.. 😅
But we are not consuming that, attribute. I'm refering to Chart.yaml and index.yaml.

I don't see how Chart.yaml and index.yaml can differ. index.yaml is created based on Chart.yaml.
When no tag is specified in values, the prefix is automatically prepended to the value of appVersion.
What we can do, is remove that automatic prefixing and use the full tag in appVersion instead.
Can't really change anything else. Not sure if this would solve your problem though.

What we can do, is remove that automatic prefixing and use the full tag in appVersion instead.

That would definitely help! 😄

Hi @sagikazarmark, do you need any help with this? I can provide a PR if you think it's worthwhile.

@nabokihms what do you think?
I'm not against the above outlined solution.

I'm ok with this change if we speak about removing the automatic v prefix.

Hi. Any news here?


typescript typings

Hello
Is there in plans to add typescript bindings to "folktale" ?

Unlikely for now, the type system implemented by TypeScript (and Flow) are not expressive enough to support most of the constructs that Folktale uses, so you'd just end up with a lot of any types, which is not very useful. Folktale was not written for a particular type system, which makes this a bit difficult too (as the features require many advanced type system techniques).
Depending on how Flow and TypeScript advance in the future I might look into this again, though.
Right now Folktale requires at the very least three type system features:

Parametric polymorphism, the ability of writing a generic type over some parameters, and then specialising that later. Maybe<a>, Either<a, b>, etc. all require this. Both Flow and TypeScript support this (some people refer to them as "generics");

Higher-Kinded polymorphism, the ability of writing a generic type that you can pass around, and yield new types. Imagine the above, but Maybe is just as valid a usage as Maybe<a>, it just results in a "type function" where the thing you're passing the type to is supposed to provide the argument for Maybe to construct a type. This is required for monads and applicatives. The type of .apply is:
apply :: forall a, b, c. (Applicative a) => (this: a<b → c>, a<b>) → a<c>

The (Applicative a) => part just says "the type variable a is constrained to be an Applicative". Since we're using an object-oriented language we could just specialise this instead:
apply :: forall b, c. (this: Maybe<b → c>, Maybe<b>) → Maybe<c>

But this still requires you to be able to write Maybe<b → c> as the type of this, which is not possible in TypeScript afaik. Flow might get higher-kinded polymorphism at some point (https://github.com/facebook/flow/issues/30) but it's not one of their priorities.

first-class tags (or some other kind of tagging/sums), basically the ability of overloading a method based on a static value, which is used by things like .matchWith, which call a function based on the tag an object has. Flow has had something like this since forever, TypeScript added this recently.

Some features use reflection or generate values. These could only be typed if we had a type system with dependent types (that is, your types are basically functions, so you can write things like sort : (Vector(len, x), (x, x -> Ord)) -> inTime(nlogn, Sorted(Vector(len, x))), which statically verifies that you've implemented a correct sort function that runs in n log n). Dependent types are still not practical.

Thanks for a great answer @robotlolita , I’ve been wondering the same thing as @djleonskennedy for a while, it’s good to have a complete explanation about this.

Understood thank you @robotlolita

Also have addition, even any typing would be handful, because now we can't use library with TS at all :(

i'm agree with @djleonskennedy

@djleonskennedy doesn't TypeScript infer any from things you haven't declared a type for, and then propagates that?

Mmh, I'll look into this over the weekend.

@robotlolita thank you

It's fine to use with typescript I'm just applying a band aid fix for now by declaring the module with any type just so I can use it with typescript.
declare module 'data.maybe' {
  const Maybe: any;
  export = Maybe;
}

@piq9117 thank you i use it now in this way

I hacked together some typings for use with the data.validation and data.maybe modules. The types should probably describe the underlying concepts such as Functor, Monad, but they are just hardcoded for now:
declare module 'data.maybe' {
    import Validation from 'data.validation';

    const Maybe: {
        fromValidation: <Success, Failure>(validation: Validation<Success, Failure>) => Maybe<Success>
        fromNullable: <T>(nullable: T | undefined | null) => Maybe<T>
        Just: <T>(t: T) => Maybe<T>
        of: <T>(t: T) => Maybe<T>
        Nothing: () => Maybe<never>
    }
    type Maybe<T> = {
        value: T
        getOrElse: (fallback: T) => T
        map: <T2>(fn: (t: T) => T2) => Maybe<T2>
        chain: <T2>(fn: (t: T) => Maybe<T2>) => Maybe<T2>
    }
    export default Maybe
}

// Applicative
declare module 'data.validation' {
    const Validation: {
        Success: <Success>(success: Success) => Validation<Success, never>
        of: <Success>(success: Success) => Validation<Success, never>
        Failure: <Failure>(failure: Failure) => Validation<never, Failure>
    }
    type Validation<Success, Failure> = {
        getOrElse: (fallback: Success) => Success
        map: <Success2>(fn: (success: Success) => Success2) => Validation<Success2, Failure>
        ap: (validation: Validation<any, any>) => Validation<any, any>
        cata: <T>(obj: {
            Success: (success: Success) => T,
            Failure: (failure: Failure) => T
        }) => T
    }
    export default Validation
}

I'm very much making it up as a go along. I've had to type Validation.ap as returning Validation<any,any>—would love help to fix this.

Also, looking around for a good FP library with support for TypeScript and Fantasy Land, I don't think there's any really strong contenders at the moment. I would love to see Folktale emerge and fill this niche :-)

@OliverJAsh With https://github.com/Microsoft/TypeScript/pull/6739 you can probably write:
type Validation<S, F> = {
  ap: <S2>(this: Function<S, S2>, validation: Validation<S, F>) => Validation<S2, F>
}

But I haven't tried it yet. I don't know if it's on the current TS version either.

Oh, wow! Thanks @robotlolita

@robotlolita That change is “included in TS 2.3](https://github.com/Microsoft/TypeScript/wiki/Roadmap#23-may-2017) which is currently out as a release candidate (RC): https://github.com/Microsoft/TypeScript/releases/tag/v2.3.0

Also, looking around for a good FP library with support for TypeScript and Fantasy Land, I don't think there's any really strong contenders at the moment. I would love to see Folktale emerge and fill this niche :-)

@OliverJAsh check out https://github.com/gcanti/fp-ts for ADT in TypeScript if you haven't already – the project seem to be moving fast.


DRILL-7242: Handle additional boundary cases and compute better estim…

…ates when popular values span multiple buckets.

@gparai could you pls review this ?

@gparai  I have addressed your review comments.  Could you pls take another look ?


Swift 3

it'd be cool to have a swift 3 version, if you have any interest to create a branch i would like to help with that.

thanks you.
Yeah, I don't have enough time to refactor code to swift 3 style.
Please make swift 3 branch and send me pull request 👍


Changed dbm to anydbm for better not-unix support

I changed the dbm import to anydbm to fix the issue on windows. At my computer it is running very well. It have to be testet on Linux and OSX too.
Like it's written in the python docs (https://docs.python.org/2/library/anydbm.html) the anydbm is a generic interface of the dbm database that is supported from the most systems. So I hope that it works well on linux and osx too.
I created a new branch so you can get the changes to test first, if you want. Maybe you could test one of the systems, because I actually haven't the possibilities.
TODO:

Test on Linux
Test on OSX

Unfortunately anydbm has been renamed dbm in Python3 (Python 2’s dbm has been renamed dbm.ndbm) which is why your PR fails on all Python3 versions. You can use that trick to fix it.
Travis tests on Linux by the way.

Thank you for the hint. I completely didn't see that it's renamed in Python3.
I will fix it as soon I get the time and let you know when it's done.

Good! You can amend the one commit in this pull request and do a forced push to the same branch – hotfix/wp-windows-dbm-issue – and GitHub will magically bring it all together.

@kizetsu: ping, any updates on this? Thanks.


CQ5: Preserve license information

RO-Crate requires license to be set on the top level Dataset (and optionally on other files). See https://www.researchobject.org/ro-crate/1.1/contextual-entities.html#licensing-access-control-and-copyright
When selecting a corresponding License in Zenodo there may need to be matching by @id and/or it's name as they have a fixed list accessible from the API https://developers.zenodo.org/#licenses
A full list of known open source licenses is available in https://spdx.org/licenses  and in machine-readable format in https://github.com/spdx/license-list-data -- however these assume URIs like http://spdx.org/licenses/Apache-2.0 but RO-Crate at best has https://spdx.org/licenses/Apache-2.0.html (note the subtle difference) as that is what is presented in browser.
More commonly licenses in RO-Crate may have the upstream URI like https://www.apache.org/licenses/LICENSE-2.0  or one of the Creative Commons licenses licenses.

May be tricky because licenses that exist can have multiple URIs. SPDX list is bigger list than what is in Zenodo (~300). Perhaps manual testing on the few most common tests but some heuristics still needed here as there is no full mapping.
Zenodo have a list of URIs but it's not spdx so it is not automatic. May want to explore how Zenodo have done codemeta.json support in its github integration

Part-done but you have to be very specific. Main focus now is on ro-crate-inveniordm

Part done, supports SPDX URIs only.
In future this package will become a wrapper for ro-crate-inveniordm (see #23) and so this is superseded by the outstanding license issue there: https://github.com/ResearchObject/ro-crate-inveniordm/issues/3


Kuberenetes pod -> docker container

Describe the bug
Started a docker container via docker compose, and pod in kuberntes. Trying to connect from pod to container using DNS *.orb.local and container IP, but connection fails
curl: (1) Received HTTP/0.9 when not allowed, is gRPC connection
To Reproduce
No response
Expected behavior
No response
Diagnostic report (REQUIRED)
No response
Screenshots and additional context (optional)
No response

@slinorb GRPC is HTTP2-only.

I figured out the problem. I had docker-compose with host: localhost and that's why it didn't work.


chore(travis): all configuration for full integration e2e test

Coverage remained the same at 42.564% when pulling 8a4359c40fc3ad2a63fe89c8697b0264bdc72270 on travis-back into 12e3db9069efb5959d53400cc2eb0596c9358775 on zenika-dev.

Coverage remained the same at 42.592% when pulling ebe06ae40a2eb03da7f68d7cb345c558609943dc on travis-back into eaeb5c87d26d439b031732af063a27c93869a3b7 on zenika-dev.

Coverage remained the same at 42.592% when pulling ebe06ae40a2eb03da7f68d7cb345c558609943dc on travis-back into eaeb5c87d26d439b031732af063a27c93869a3b7 on zenika-dev.


I hope the speed will be improved in the future.

It's a very pretty plugin.
However, when I ran it, the speed was too slow while typing in editor mode (&reading view).
The reason for the slowness seems to be due to its use with background plugins.
I hope the speed will be improved in the future.

Can you elaborate? I haven't run into this issue myself. Do you know what "background plugins" might be causing the issue?

Can you elaborate? I haven't run into this issue myself. Do you know what "background plugins" might be causing the issue?

https://github.com/samuelsong70/obsidian-dynamic-background
I am using this plugin.
However, it is very slow when used together.

I just released 1.2.3, which should improve the performance of the editor as the number of usages of the card icons goes up. If you continue to experience performance issues, please provide a Vault with the relevant plugins causing issues, any necessary files that would produce issues, and reproduction steps for it.


scrolling not work in android default browser

hi
scrolling not work in android default browser and android webview

Hey @davisbra - do you have a sample repo to reproduce that behavior? For me it works fine.

I test your demo app (https://demo.app-framework.com/)in Samsung galaxy A5 default browser ( not chrome or other browser) and HTC one M7  default browser not scrolling(scrolling down) in any pages of demo app.
(in chrome browser it works fine)

We solved it like that.
In node_modules/app-framework/client/app.js
here
mixins.preventOverscroll = {
  created: function () {
    // No native application (Overscroll disallowed by Cordova for native Apps)
    if (!window.cordova) {

replace with
var iOS = !!navigator.platform && /iPad|iPhone|iPod/.test(navigator.platform)
mixins.preventOverscroll = {
  created: function () {
    // No native application (Overscroll disallowed by Cordova for native Apps)
    if (!window.cordova && iOS) {


[BUG] "Kerberos TGT Request Using RC4 Encryption" using non-CIM field "Account_Name"

Describe the bug
The rule "Kerberos TGT Request Using RC4 Encryption" in 4.16.0 uses the non-CIM field "Account_Name" rather than the standard field "user".  This doesn't appear to have been the case as recently as 4.14.0; our allowlisting in the macro kerberos_tgt_request_using_rc4_encryption_filter used the field "user" and operated as expected, breaking only during an upgrade performed today.
Expected behavior
The field "user" should be utilized in order to ensure queries looking for that CIM field in the notable index find Notables related to this rule.
App Version:

ESCU: 4.16.0

This detection does not operate against a datamodel but instead against the raw Windows event logs hence, it is not using a CIM field. Can you give me an example of what you believe the "fixed" query should look like?

@iso-rgomez : thank you for raising the issue! this search has been updated to use the xml format logs since the issue was created! Closing this issue as it is old now! Please feel free to open a new issue if the updated query has issues!


flowschema for openshift controller manager

Traffic from openshift controller mnager is as important as kcm.

See https://github.com/openshift/cluster-kube-apiserver-operator/pull/966 for more details.

/lgtm


Fixes robinrodricks/FluentFTP#861 For Windows Server IIS, the space a…

Fixes #861 For Windows Server IIS, the space at the beginning of the file name is excluded

May I know how you managed to test this? I am trying to create unit tests for this library and it would be really helpful!

This time, I used Hyper-V and the evaluation version of Windows Server for verification.
(The acquisition source URL is as described in the above comment.)
Evaluation versions of Windows Server are distributed in VHD and iso formats.
I built them on Hyper-V on my local PC and tested them.
Unfortunately, it's set manually, not automatically ...:sweat_smile:
If you want to do a Unit Test, I think you should prepare something that is easy to build an environment like Docker,
or use the CICD service that Windows Server can use.
But ... old Windows Server (especially 2008/2012 ...) machine images seem difficult to use from these.
Taking AppVayor as an example, the oldest Windows Server seems to be Windows Server 2012 R2.
https://www.appveyor.com/docs/windows-images-software/
GitHub Actions seems to be the oldest Windows Server is Windows Server 2016.
https://github.com/actions/virtual-environments#available-environments
I don't currently have a good idea to solve these problems.

Released now!
https://www.nuget.org/packages/FluentFTP/37.0.4


Add fallocate and sparse support in whisper-create.py

Coverage remained the same at 89.022% when pulling a955f3b918059925e75af0001324506c0131a5ee on szibis:whisper_create_sparse into 876f2eb966a3f3a26923601cfc6495b9ae742e94 on graphite-project:master.

Test rerun magically fixed the strange pypy issue. Any objections to merging that?


Feature: Support RetryStrategy/InstanceGroups

Note: Some modifications are made to Hyper parameter tuning, this is normal as Hyper parameter tuning consists of training jobs.
Description of changes:
generator.yaml - commented out shapes. Added late initialize to ResourceConfig.InstanceCount and it's HPO equivalent.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/hold

/unhold

missing handling TrainingJobDefinitions.ResourceConfig.InstanceCount in HPO

ACK, I've been trying to test that but I keep getting credential errors on sagemaker.

/hold
Merge this after #177. Also still need to debug TrainingJobDefinitions.ResourceConfig.InstanceCount.

/unhold
TrainingJobDefinitions.ResourceConfig.InstanceCount works

/ok-to-test
looks ok, do you want to merge 177 first?

\hold

/lgtm


Question regarding evaluation function (minor bug?)

Hello,
i think there might be a bug in the evaluation code or I might missunderstand something: In the evaluation function, first, the tuple is [x,y,z,label,score]. However, for creating the pred_dict, it is referenced as [x,y,z,score,label]. Why is the label used as score here?
https://github.com/DeepMicroscopy/MIDOGpp/blob/c2726b1f40a1bfe4f0acce9c7f1d186eec12e914/evaluation.py#L86-L94

Hey Fabian.
Thanks for that. We'll look into it.
Best,
Marc

Dear Fabian,
Yes, this was indeed a bug in our evaluation code which influenced the mAP calculation. Thank you for brining this to our attention. We have made the necessary code changes and will prepare an addendum for our manuscript. Fortunately, all evaluations in the manuscript were based on the F1 score, which was not affected by the bug.
Kind regards,
Frauke

Thank you for the response!
Sorry for the problem it may have caused! Luckily, your mAP results should get even better with the change.
Best, Fabian


Add 'port' to the options passed to the loadPackage function

I'm currently looking into verdaccio as a local npm registry, and by default it runs on port 4873. Currently this package does grab the port from what registry-url returns, but doesn't pass it on to the actual get request.
I went for minimal code changes, but I guess to make absolutely sure it doesn't change for existing users, you could pass undefined if given a standard port (80 or 443).
Thanks for the libraries, zeit is awesome!

Great addition, thank you! :)


[skip ci][ci skip] Directly run installer script

The Problem/Issue/Bug:
The current instructions on how to use the installer script all relay on downloading the script which can make troubles in case of changes in the master which then are ignored locally.
How this PR Solves The Problem:
The new instruction directly passes the script to bash via pipe and avoids issues with deprecated and incompatible locally saved scripts.
Manual Testing Instructions:
Follow the instructions changed by this PR to check if it works.
Automated Testing Overview:
None
Related Issue Link(s):
Release/Deployment notes:

Not ready yet, the script is not intended to be run with sudo.

Should be ready now see https://github.com/drud/ddev/pull/4023#discussion_r924799957

BTW, no need to put [skip ci] on docs PRs any more because the test setup determines whether to run if docs only.

BTW, no need to put [skip ci] on docs PRs any more because the test setup determines whether to run if docs only.

Interesting, it's still mentioned in the docs, will remove it...


Fix Other Metagames of the Month

@TheImmortal

Well, considering the bug reports I'm getting, it's probably worth merging now.


fix(gateway): remove useless version param from identity payload

Removes the defunct version param from the identify payload

I believe this is a breaking change, but it doesn't affect much either so it should target 0.4

I believe this is a breaking change, but it doesn't affect much either so it should target 0.4

The model crate has a different semver policy when relating to API mappings, but since this really doesn't affect anything it may as well go on 0.4.

The model crate has a different semver policy when relating to API mappings, but since this really doesn't affect anything it may as well go on 0.4.


Module Resolution : exclude dev-dependencies from module resolution

Feature request
What is the expected behavior?
I have :
server/
  a.js
  node_modules/
    module2/
client/
  node_modules/
   module2/

The webpack of server/ has the resolve.modules set to
 [        path.resolve(__dirname, '../..'),
        './node_modules',
        '../client/node_modules',
      ]

When in a.js module2 is required/imported webpack checks server/node_modules (following resolve.modules rules) and thinks "module2 exists in server/node_modules so NO need to look in client/node_modules". But actually module2 is a dev-dependencies in server/ and a regular dependency in client/ therefore I expect module2 to be resolved from client/node_modules NOT from server/node_modules. Otherwise my app crash if I npm prune --production before executing my compiled server code.
What is motivation or use case for adding/changing the behavior?
I do SSR so I need to load properly client_modules from the server.
How should this be implemented in your opinion?
If module1 is required and is in node_modules and in package.json's dev-dependencies then ignore it and try to resolve it from somewhere else (following usual rules of module resolution ofc).
Are you willing to work on this yourself?
no

The official node_modules resolving rules don't differ between dev and normal dependencies. In fact many people even have modules processed by webpack as dev deps as their are only needed during building and not when the server actually runs.
You could write a resolving plugin to make it work like you want to, but to be honest: Don't do such weird resolving like getting modules from another packages node_modules.

Closing due to inactivity. Thanks!


rxjs error in nuxt3

Describe the bug
[nuxt] [request error] [unhandled] [500] Cannot find module './internal/Observable'                                                                                17:34:59
Require stack:
- D:\code\github\vitesse-nuxt3-main\rxjs
  at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
  at Module._load (node:internal/modules/cjs/loader:920:27)
  at Module.require (node:internal/modules/cjs/loader:1141:19)
  at require (node:internal/modules/cjs/helpers:110:18)
  at D:\code\github\vitesse-nuxt3-main\rxjs:17:20
  at ViteNodeRunner.directRequest (/D:/code/github/vitesse-nuxt3-main/node_modules/.pnpm/vite-node@0.30.1_@types+node@18.14.0/node_modules/vite-node/dist/client.mjs:331:11)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async ViteNodeRunner.cachedRequest (/D:/code/github/vitesse-nuxt3-main/node_modules/.pnpm/vite-node@0.30.1_@types+node@18.14.0/node_modules/vite-node/dist/client.mjs:171:14)
  at async ViteNodeRunner.dependencyRequest (/D:/code/github/vitesse-nuxt3-main/node_modules/.pnpm/vite-node@0.30.1_@types+node@18.14.0/node_modules/vite-node/dist/client.mjs:220:14)
  at async D:\code\github\vitesse-nuxt3-main\node_modules\.pnpm\@vueuse+rxjs@10.1.2_rxjs@7.8.1_vue@3.2.47\node_modules\@vueuse\rxjs\index.mjs:1:31

Reproduction
https://github.com/transtone/vitesse-nuxt3
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 9.87 GB / 31.86 GB
  Binaries:
    Node: 18.15.0 - D:\bin\nodejs\node.EXE
    Yarn: 1.22.19 - D:\bin\nodejs-bin\yarn.CMD
    npm: 9.6.5 - D:\bin\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.963.0), Chromium (112.0.1722.68)
    Internet Explorer: 11.0.22621.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Reproduction is up to date.

It's a rxjs loading problem. add this in nuxt.config.js
build: {
    transpile: ['rxjs']
},

https://nuxt.com/docs/guide/concepts/esm#transpiling-libraries


Fix a test issue discovered in PR #2482

Description
Fix a test issue  in HTTPJwtKeyByOpenIdConnectAuthenticatorTest  discovered in PR #2482 ,

Category Test fix
Why these changes are required?
Fix the  "testExp" test
What is the old behavior before changes and new behavior after changes?
The "testExp" test was missing the "Bearer" auth-scheme in the request, so the token expiration test was not actually being executed

Issues Resolved
Thi is a follow-up PR no Issue has been opened
Is this a backport?
No
Testing
unit testing
Check List

[  ] New functionality includes testing
[  ] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2501 (5e649a6) into main (08e21dd) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2501      +/-   ##
============================================
- Coverage     61.20%   61.20%   -0.01%
+ Complexity     3326     3323       -3
============================================
  Files           260      260
  Lines         18497    18499       +2
  Branches       3268     3268
============================================
  Hits          11322    11322
  Misses         5578     5578
- Partials       1597     1599       +2

Impacted Files
Coverage Δ

...ic/auth/http/jwt/AbstractHTTPJwtAuthenticator.java
55.29% <100.00%> (+0.53%)
:arrow_up:

...azon/dlic/auth/http/jwt/keybyoidc/JwtVerifier.java
86.04% <100.00%> (+0.33%)
:arrow_up:

...search/security/transport/SecurityInterceptor.java
75.38% <0.00%> (-0.77%)
:arrow_down:

...ensearch/security/compliance/ComplianceConfig.java
82.63% <0.00%> (-0.70%)
:arrow_down:

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


Modal component

This adds a modal component & docs, that looks like this:

I tried to follow what notifications is doing, but also leave it up to the user what to put inside modal (in this example, I use a card to make a nice material-looking modal.)

Really cool - I will play around with this tonight/tomorrow.

@konsumer Thank you for the contribution :)

@konsumer has been released as part of v0.9.0


Fix indexing in KeyValueIndexed database

This PR fixes the indexing in KeyValueIndexed database.

Will refactor this a little bit more.


Added 'touch_id' endpoint

Change list
Added 'appium/simulator/touch_id' endpoint to AppiumCommands.cs
Types of changes
What types of changes are you proposing/introducing to .NET client?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

##Details
Touch ID is a feature in Apple products (see https://support.apple.com/en-ca/HT201371). This endpoint simulates the behaviour.

I fixed it. Looks like it was a tab issue.


Seemingly Stuck during Mass Deploy

Specifically it seems that it works for a few minutes, and then all threads just stall - They never exit, they just stop working. Need to debug, but not sure how.

Alternatively, ldgallery could be at fault, it's very slow to unpack and such and may be holding stuff up?


Error: anable to solve the linear assignment of a cost_matrix with nan values

Hi everybody and thank you for your contributions.
As reported below, if the following cost_matrix contains nan values, the linear_sum_assignment function crashes.
cost_matrix
[[0.70001    0.70001    0.70001    0.70001   ]
 [0.03333333 0.70001    0.70001    0.70001   ]
 [       nan        nan        nan        nan]]

    indices = linear_sum_assignment(cost_matrix)
  File "/usr/local/lib/python3.7/dist-packages/scipy/optimize/_lsap.py", line 100, in linear_sum_assignment
    return _lsap_module.calculate_assignment(cost_matrix)
ValueError: matrix contains invalid numeric entries

scipy version 1.7.0

Raising a ValueError is the intended behaviour. A nan value in the input usually means something has gone wrong, so we want to catch this.

Can we close this then?

Yes :)


Chinese Input Broken on iOS device

On iOS device user is unable to input Chinese characters into TextInput.
Actual vs. Expected behavior images here

Note: It seems like TextInput is grabbing input text before user has a chance to select correct characters.

Hand-writing Chinese characters into Kivy app on iOS device DOES work.  Behavior images attached in Google user group.

When entering Chinese via hand-writing, back-spacing strokes doesn't work. (This makes more sense if you know how to use hand-written entry)

WORKAROUND:  If the user installs the 搜狗/Sougou keyboard, Mandarin-pinyin input is not a problem in kivy app.


Switch to argparse for the graph_transitions command

This was added in Django 1.8, and optparse (the old way) was removed in 1.10.
This switch removes support for Django 1.7, which as of Django 1.9's
release is no longer a supported Django version.
Fixes https://github.com/kmmbvnr/django-fsm/issues/146.

RuntimeError: failed to execute ['dot', '-Tpng', '-O', '/tmp/tmpJ93GKj'], make sure the Graphviz executables are on your systems' path

Regarding tests: should be monkeypath graphviz.render, or install dot / graphviz?

No needs to drop support for django 1.6/py26, just use getattr(BaseCommand, 'option_list',[])

Regarding tests: should be monkeypath graphviz.render, or install dot / graphviz?
Obviously none of these. The unit test should call management command without outputfile argument.

Travis broken, no activity from OP

For reference: tt was adopted and merged in https://github.com/kmmbvnr/django-fsm/pull/155.


Option to disable player unit frame pulse effect when in cities

When you're in cities the default unit frames will start pulsating in a yellow color which is a bit annoying, would be awesome if you could find a way to get rid of that 👍
Here's a visual of it:

That's an indicator when the character is resting, there's also one but red when character is in combat! This is default features and they are intended to work this way. Might add an option to remove this but that's low priority for now :)

No problem :), I made a little digging myself and found the commands to hide the glow effects, you can use them for later in case you wanna implement them. I've tested them ingame by putting /script infront and then copy paste the commands and they seem to be doing the job! :p
PlayerStatusTexture:Hide()
PlayerRestGlow:Hide()
PlayerStatusGlow:Hide()
PlayerAttackGlow:Hide()
I havn't seen the combat glow effect before though, but hopefully the last command takes care of that?
I found the commands here: https://forums.wowace.com/showthread.php?t=20156

@Cruzix Implemented in next patch 👍

Any chance you can make this feature disable pet combat glow as well? 😄 ❤  you can see it happening on this screenshot

@Cruzix Yes I will, just forgot about it, should be an easy fix 👍


fatal: refusing to merge unrelated histories

Syncing new commits...
From https://gitee.com/OpenHarmony/docs

branch                master     -> FETCH_HEAD
fatal: refusing to merge unrelated histories
ERROR:  exit 128
New commits could not be pulled.
Try running in test mode to verify your action input. If that does not help, please open an issue.
Resetting git config to previous settings.
Reset Complete
Error: The process '/usr/bin/sh' failed with exit code 128

Test mode is passed.

Please try searching closed issues. This error message comes up a lot.


Always immediately refresh offscreen items when running actions

SWS/S&M: Unselect offscreen items
SWS/S&M: Toolbar - Toggle offscreen item selection

It previously required "SWS/S&M: Toggle toolbars auto refresh enable" to be disabled for the offscreen items to be refreshed synchronously.
Otherwise the refresh would be done through the global toolbar refresh timer. This made the above actions potentially use out-of-date data when used as part of a custom action or a script.
Fixes #1325.

:white_check_mark: Build sws 334-master completed (commit https://github.com/reaper-oss/sws/commit/7404d65ad6 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-refresh-offscreen-items-on-action-7404d65a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-refresh-offscreen-items-on-action-7404d65a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x86.pdb
build/sws-<IP_ADDRESS>-Windows-x86-refresh-offscreen-items-on-action-7404d65a.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-refresh-offscreen-items-on-action-7404d65a.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/BuildUtils/SWS_Template.ReaperLangPack
build/BuildUtils/whatsnew.html
build/reaper_sws-x64.pdb
build/sws-<IP_ADDRESS>-Windows-x64-refresh-offscreen-items-on-action-7404d65a.exe

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-refresh-offscreen-items-on-action-7404d65a.tar.xz


docs: v3 to new docs compatibility

copied docs to correct location
added config file for compatibility

Codecov Report

:exclamation: No coverage uploaded for pull request base (v3@5e37b14). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@          Coverage Diff          @@
##             v3    #4890   +/-   ##
=====================================
  Coverage      ?   96.36%
=====================================
  Files         ?       45
  Lines         ?     2281
  Branches      ?      640
=====================================
  Hits          ?     2198
  Misses        ?       80
  Partials      ?        3

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

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


[v3] Middleware: Before and After

I don't know if anyone has brought this up before, or if I'm missing something fundamental about how middleware operates, has anyone considered before and after scenarios?
What I mean is middleware that runs before the router, and middleware that runs after, so in essence, two separate stacks. This would make the app have in total three middleware stacks (including the route).
How do people deal with this normally?

I think this point has been discussed here https://github.com/slimphp/Slim/pull/1264

Thanks for the pointer @lalop, it's kind of what I mean...
The middleware I would want implemented would be a standard type to avoid the attachment to one specific framework, but what I mean is to have more than one queue to make it so that I can ensure a specific outcome after a route has dispatched.

Before and after...
@designermonkey
https://gist.github.com/geggleto/7249ed53920c8b1618d3
Or am I not understanding what you mean.

No, I mean two stacks that Slim runs. So I add middleware to a stack that I know runs before the router, and I add middleware to a different stack that I know runs after the router. The middleware is all the same format, I am talking about having two distinct stacks that I can add to.
// From the App::run method

        // Traverse middleware stack
        try {
            $response = $this->callMiddlewareStack($request, $response);
        } catch (SlimException $e) {
            $response = $e->getResponse();
        } catch (Exception $e) {
            $errorHandler = $this->container->get('errorHandler');
            $response = $errorHandler($request, $response, $e);
        }

So the app tries to run the middleware stack, and the router (via App::__invoke middleware) is the last item to run. I am talking about another stack of middleware to run after that first stack:
        // Traverse middleware stacks
        try {
            $response = $this->callBeforeMiddlewareStack($request, $response);
            $response = $this->callAfterMiddlewareStack($request, $response);
        } catch (SlimException $e) {
            $response = $e->getResponse();
        } catch (Exception $e) {
            $errorHandler = $this->container->get('errorHandler');
            $response = $errorHandler($request, $response, $e);
        }

What do you mean by after the router exactly.
Are you talking about middleware that runs after the route callable has been called ?

How do you want to use the second stack? Can you not just do it like this?
$middleware = function ($request, $response, $next) {
  // before
  $newResponse = $next($request, $response);
  // after
  return $newResponse;
};

Or do you want the second stack so you can first call the first global stack, then the router stack and finally the second global stack?

I think this sort of thing is already possible and I don't think you need another stack.
Granted the details are in how you write the middleware so it is not very readable.
Ordering I think goes the same way, Last in first executed. So even if you intermixed before and after middlewares it executes as intended.
//Before
$middleware = function ($request, $response, $next) {
  //Do Stuff here
  $newResponse = $next($request, $response);
  return $newResponse;
};

//after
$middleware = function ($request, $response, $next) {
  $newResponse = $next($request, $response);
  // after
  // do stuff here
  return $newResponse;
};

-1. You already have the ability to run code before and after the application.

@codeguy can you explain how then? How do I modify the response after the router has run?

Each middleware, when invoked, is provided a Request object, a Response object, and a reference to the next middleware. The middleware may manipulate the Request and Response objects before and after it invokes the next middleware.
function (Request $req, Response $res, callable $next) {
    // Add attribute BEFORE next middleware
    $req = $req->withAttribute('foo', 'bar');

    // Invoke next middleware and fetch response
    $res = $next($req, $res);

    // Update response AFTER middleware
    $res = $res->withStatus(400);

    // Return a response to upstream middleware
    return $res;
}

Yes, I get that, but as the Slim router is the last middleware to be queued up in the stack, I cannot manipulate the response object after the router has called a route and run it's callable.
Ahhhhh, lightbulb moment. I see.


undefined method 'id' for nil:NilClass when include null none primary key association

create_join_table :members, :articles, {id: false} do |t|
  t.integer :article_id
  t.string :polymorphicable_type
  t.integer :polymorphicable_id
end

class MemberArticles < ApplicationRecord
   belongs_to :article
   belongs_to :polymophicable, polymorphic: true
end
class ArticleRecourse < JSONAPI::Resource
  has_many :members, always_include_linkable_data: true
end

I want serialize articles polymorphic data througth join_table associated
when i use  always_include_linkable_data: true or direct serialize members model also throw this exception.
should each resource model entity at least have _primary_key or id method? it is jsonapi-resources convention? If true, Maybe write in documents

You have a typo in always_include_linkable_data . It should be always_include_linkage_data. I don't know if that's just in your example, or in the actual failing code. Also ArticleRecourse => ArticleResource.
I need to see your models and resources for Articles, Members, and ArticleMembers to gain a better idea of how you have this setup.


Woodpecker SSH push

Is the key even loaded in the second configuration ? (Examples below)
If the format really is invalid in the first example, what format should the private key be and does it need to be parsed somehow ?

Environment 1:
Secret has been set ssh_key, with rsa or ed key same result.
I also tried to change the line endings of the keys with sed, no luck.
sed ':b;N;$!bb;s/\n/\\n/g'

.woodpecker.yml

pipeline:
  publish:
    image: appleboy/drone-git-push
    settings:
      branch: main
      remote: git@github.com:<removed>
      force: false
      commit: true
      commit_message: "Drone build ${DRONE_COMMIT_SHA:0:7}"
      author_name: "John Doe"
      author_email<EMAIL_ADDRESS>      ssh_key:
        from_secret: ssh_key

Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.
Load key "/root/.ssh/id_rsa": invalid format
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Environment 2:
Same as in Environment 1 just without the definition of the secret name.
.woodpecker.yml

pipeline:
...
...
      author_email<EMAIL_ADDRESS>      #ssh_key:
      # from_secret: ssh_key

Host key verification failed.
fatal: Could not read from remote repository.

Had the same issue.
Make sure the secret ends with an newline (\n)
https://serverfault.com/a/960647

Had the same issue. Make sure the secret ends with an newline (\n)
https://serverfault.com/a/960647

I tried that, still the same issue /n unix file ending should be fine right ?

Recreated everything including new keys on GitHub, Environment 1 is now working.


RHEL | XRDP | KDE session slowness

Hi Team,
We have been using XRDP 0.9.16 on our 1000+ Linux RHEL machines.
Facing KDE Session freeze issue.
could you please let us know below details.

Is there any bandwidth to use KDE session on one machine
Any configuration changes needed to handle sever load on XRDP session
Does this issue has fix on any latest version of XRDP version , if yes what changes done from your end.
KDE freeze issue is not permanent issue but still when the issue occurs need to kill the session manually and starts the new one - this makes hard to user KDE on xrdp

Any help/suggestion would be appreciated.
Thanks.

Hi @AbinayaSandhiyaM
We've not had any such problems reported.
When the freeze happens, are you able to use a tool like iftop to see whether bandwidth is definitely an issue?

Hi Matt,
Thanks for your quick response!
As per our understanding there are users who all are using XRDP with KDE session facing freeze issue when the server loads goes high.
Now the problem is not able to reuse the same session even server load gets fixed.
Restarting the xrdp service/kill the old xrdp process would help to solve the issue but still we would like to know the solution for this xrdp reconnection without restart/kill the session.

I still don't quite understand your problem here.
Can you be clearer on what "server load goes high" means? Are you running out of CPU, memory, or network bandwidth?
You might also want to check your system logs when the problem occurs. If you're running out of memory, the Linux OOM killer will almost certainly be terminating some of your KDE processes which won't be good.
Your version of RHEL may allow you to set per-user limits on resource usage to prevent this happening, but I don't know anything about that. You can look that up as well as I can.

No further input - closing


Remove Template 9 Upload question?

As an analyst
I want Template 9s to no longer be uploaded as it is not of use to us
So that it's not extra work for the applicant and analyst
Description:
We may decide to not use Template 9 anymore, to be determined.  If so then we need to remove it from the form
Acceptance Criteria:
{Page Name}
Screen
[wireframe 1]
[wireframe 2]

[ ] .

Page Behaviours

[ ] .
[ ] .
[ ] .

Validations

[ ] .
[ ] .
[ ] .

Actions

[ ] .
[ ] .
[ ] .

Not included:

.
.

Implementation Details

DB:

.
.

Middleware:

.
.

Frontend:

.
.

Tests:

.
.

Documentation:

.
.

Closing this ticket as we don't plan to remove template 9


Added the new body model

Pull Request
Description:
The last body model had holes when inferring the body model. Changed it with a new model  trained on 1.4k manually verified datasets.
Changes Made:

Changed the link of the download to the new model
Changed spacing to 5 isometric according to new model

Related Issues:
-None
Testing Done:
Tested the model. Screenshot below
Screenshots or GIFs (if applicable):

Reviewer Checklist:

[ ] Code is clean and follows the team's coding standards.
[ ] Tests have been added or updated to cover the changes.
[ ] Documentation has been updated or added if necessary.
[ ] The code builds and runs without errors.
[ ] The changes have been tested on relevant environments or browsers.
[ ] Any relevant dependencies have been updated.
[ ] The changes have been reviewed for security implications.

Additional Notes:
Reviewer(s): @[mention reviewers here]
Assignee: @[mention assignee here]
Labels: [List any labels that apply to this PR, such as bug, feature, enhancement, etc.]
Milestone: [Specify the milestone if applicable.]
Linked Pull Requests:
None

Hi @mprires !
I am interested in which datasets were used in the training.
Could you share more details about them (e.g., publicly available, annotations)?
Thanks in advance and looking forward to your reply.

Hi @Joon-Jung,
Thanks for reaching out. We are using our in-house datasets for training and currently they are not open-source. We are negotiating with the concerned parties to make it open source. But I can't give you a concrete answer until June.
Cheers,
Lalith

Hi Lalith (@LalithShiyam),
Thank you for your prompt response. It's unfortunate that the dataset is not yet publicly available.
I look forward to good news in the near future. Thank you very much!
Best regards,
Joon


QE : Access Control : Implement no SSH daemons

Dependant on https://github.com/test-network-function/cnf-certification-test/pull/1219

I do not see how the SSH daemon is supposed to be running in the second test case. Have you tried that this works?

I am waiting for the implementation to be merged at first.


[REEF-421] Fix Ambiguous subplan in NetworkService

This pull request addressed the issue by

Removing @inject and @parameters of a constructor in NetworkService.

JIRA: REEF-421

This looks good, I'll merge it.


prioritize PNPPOWERSHELL_DISABLETELEMETRY" over telemetry file presence

Type

[X] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
Works around #1247 by allowing easier disabling of Telemetry
What is in this Pull Request ?
change the telemetry disabling logic to allow using the PNPPOWERSHELL_DISABLETELEMETRY OR .pnppowershelltelemetry file instead or requiring both to disable telemetry.

Thanks @gbordier!


Scroll Container doesn't behave correctly when both bars are visible.

Godot version
v4.1.3.stable.official [f06b6836a] (Pretty much every version since 3.x)
System information
Windows 10 - Compatibility+
Issue description
When a scroll container only has a vertical or horizontal bar, they work fine. They act pretty much how you'd expect. But when both bars are visible at the same time, content overlap with the bars. This is especially visible when the bars are transparent, but even when the bars are opaque you can see content out of the margin you'd expect, notably at the bottom right which should be an empty square but sometimes has content visible.
This can be a trivial graphical glitch in some cases, but in others it makes using scroll containers a chore.
Steps to reproduce
Putting any content in a scroll container that has both bars visible.
Minimal reproduction project
N/A

Gonna need some screenshots for this.

Ok so I've been messing around with ScrollContainer to get the perfect screenshots to illustrate my point and the problem is definitely more complicated than I thought. But I definitely think the content should be clipped before it reaches the bars.
In this screenshot you see a dark grey background with a scrollcontainer with a custom theme (I just made the bars opaque and easier to see). I just added a red ColorRect with Container Sizing set to Fill to illustrate where content would be.

Here is the same scene but with both scrollbars set to Always Visible. It actually looks like you'd expect

But if the content is bigger than the ScrollContainer, by setting the ColorRect's custom min size for example, It looks wrong. Note here that this is a fairly common scenario and that the ScrollContainer's Clip Content is turned on.

If nothing else, Clip Content should clip anything under the scrollbars so you don't get anything in the corner there.

You used a few more settings than I expected. Could you provide an example project demonstrating all this? Thanks for your work looking into this.

Yeah I thought this was a very common scenario but the more I fiddled with it, the more I realized how specific to the settings I like this is. Sorry about that.
Anyway here is a small project that should showcase this.
ScrollBar.zip


📝 Address and document Data Platform DNS hierarchy

Currently scattered across Cloud and Modernisation Platforms, we should probably go all in on Modernisation Platform as that is looking like the likely home for our estate.

We should look to use PDNS, that does require using static egress IP address as they use a allow list for resolution.


Generate error

When I run the demo https://www.animationgpt.net/enUS/demo, it seems generate error.

Our online server has expired, you can deploy it locally according to the tutorial.


[ADP-2377] Add DB abstraction

This pull request adds an abstraction DB which represents a storage facility for a Haskell value. It generalizes Store with a readDB function for reading parts of the data (as opposed to the entirety of the data). The operations for reading a part are specified through a type constructor, which is typically implemented as GADT.
This pull request introduces the abstraction and implements a DB for the TxSet type. An implementation of a DB for the TxWalletsHistory is planned for a future pull request — this will move the transaction storage partially back to disk.
This pull request is part of the new architecture for the database layer.
Issue number
ADP-2377

bors r+

bors r+

bors retry

bors r+

bors r+

bors try

bors try

bors ping

bors r+


issue on mongo seeding when user already exist

//seed.js
const users = [
    {
      name: "alireza",
      email<EMAIL_ADDRESS>      password: "$2a$10$bd9GpPt7oP6LrqcIKYvnRuLjNmMjJnSsgcVI8vye8X61ECHqCT7G2",
    },
  ];

users.forEach(async (user) => {
    await prisma.user.upsert({
      where: { email: user.email },
      update: {},
      create: {
        name: user.name,
        email: user.email,
        password:
          "$2a$10$bd9GpPt7oP6LrqcIKYvnRuLjNmMjJnSsgcVI8vye8X61ECHqCT7G2",
      },
    });
  });

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v18.16.0

OS
windows

Prisma Client
4.13.0

Query Engine
1e7af066ee9cb95cf3a403c78d9aab3e6b04f37a

Database
mongodb

Logs
prisma:client:libraryEngine:loader Searching for Query Engine Library in D:\WORK\agp-express\node_modules\.prisma\client
prisma:client:libraryEngine:loader loadEngine using D:\WORK\agp-express\node_modules\.prisma\client\query_engine-windows.dll.node
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client%

@mkalireza-ir is there an error message? How does it look like when it crashes? (is that all in this issue already?)

Ping @kordkheili, any information to add that would help us reproduce this?

Hi @kordkheili, since we got no reply with information that could help us reproducing this issue, we're closing this issue.
Should you or another user bump into the same problem and provide a reproduction, we will consider reopening this issue. Thanks!


Change EcmaScript levels to a single flag "ecma"

Separating out the discussion from https://github.com/jshint/jshint/issues/1137#issuecomment-19694125 although I've changed 'eslevel' to 'ecma'
This would allow the current flags to be folded into one:

es3 -> ecma: 3
es5 -> ecma: 5
esnext -> ecma: 6? or 'next'
moz -> ecma: 'moz'

merging to #2124


image.animation - extra properties

Useful for player protos, etc., if fixed tint color is required:
      apply_runtime_tint = false,

No idea what this one does, unless it prevents frame skipping?
          max_advance = 1,

Another one that I have no clue about:
      apply_projection = false,

line_length - rows
Either num rows or cols (line_width) are specified, and the other dimension is calculated by dividing frame_count by that value.

run_mode = "forward-then-backward",

flags = {  "mask" }

This might be too specific to bother about:
stripes = {
              {
                filename = "__base__/graphics/entity/worm/worm-attack-01.png",
                height_in_frames = 8,
                width_in_frames = 8
              },
              {
                filename = "__base__/graphics/entity/worm/worm-attack-02.png",
                height_in_frames = 8,
                width_in_frames = 8
              }
            },


Underscored text inside of escaped parens is not italic

Code examples speak louder than words:
http://demo.showdownjs.com/#!/\(**This should be bold**\)

\(_This should be italic (but is not)_\)%0A%0A(This%20is%20italic)%0A%0A%5C(This%20is%20also%20italic%5C)
\(**This should be bold**\)
\(_This should be italic (but is not)_\)
(_This **is** italic_)
\(*This is also italic*\)

Background: Gitbook automatically escapes parens on export. This causes my local Showdown renderer to not make my text inside of those parens italic. Looks like a bug to me.

I will look into it


missing GraphQL features support

Playing around with the GraphQL API, I've noticed some core features are not supported.
While those features are not deal-breakers, supporting them could be useful.
Missing support for variables
GraphQL query variables can't even be provided as the GraphQL endpoint is using HTTP GET gateway.
Fragments support missing
Take for example the following basic query:
{
    organization(organization_id: "231c2397-f3b6-4d74-bf2b-e0490f49394c", time:<PHONE_NUMBER>286) {
        resources {
            plans {
                aggregated_usage {
                    windows {
                        summary
                    }
                }
            }
        },
        spaces {
            resources {
                plans {
                    aggregated_usage {
                        windows {
                            summary
                        }
                    }
                }
            }
        }
    }
}

This query executes successfully and returns the expected response.
Now let's add a fragment:
{
    organization(organization_id: "231c2397-f3b6-4d74-bf2b-e0490f49394c", time:<PHONE_NUMBER>286) {
        resources {
          ...resourceSummaryDrillDown
        },
        spaces {
            resources {
                ...resourceSummaryDrillDown
            }
        }
    }
}

fragment resourceSummaryDrillDown on Resource {
  plans {
      aggregated_usage {
          windows {
              summary
          }
      }
  }
}

This time we're greeted with the following error:
{
    "message": "Graphql query error - Unknown type \"Resource\".",
    "statusCode": 400,
    "error": "query",
    "reason": "Unknown type \"Resource\".",
    "noretry": true,
    "nobreaker": true
}

@iDaN5x Thanks for reporting the issue.
We would like to add support for this feature, but at the moment it is not ranked high in our backlog. Unfortunately it would take some time until we get to GraphQL improvements.
Do you care to file a PR?

I've explored the sources for the project and found the "bug" causing the described issue -
It appears that GraphQL types are automatically generated from abacus schemas via lib/utils/schema/src/graph.js.
The GraphQL type naming retains the same capitalization as the abacus scheme; i.e. "resource" remains "resource", and not "Resource" as the API suggests.
Now we two options:

Apply "upperFirst" to the type name, so that GraphQL types' naming fits API.
Update the API documentation to reflect correct type names.

Both options are easy fixes, so just let me know about the favorable option.

Capitalizing seems like a better idea

See PR #801 for naming convention issue.
Regarding the variable support:
We have a few options for how to introduce variable support:

Query remains in URI path, while variables are supplied as JSON object in the request body.
This option minimizes the changes that has to be made to the code.
Query is moved alongside variables to request body.
While this is the GQL recommended way, it breaks existing API.
Make sure both options above are supported.
This requires the biggest change and is not beneficial enough.

I believe the first option is the best one at the moment.
Let me know what should be done and I'll start implementation.

I like option 2, but I don't get why it would break the API. Can you provide an example?

With option 2 selected, the GQL endpoint will no receive the query in the request body instead of URL.
To correctly support providing data in the request body, the HTTP method needs to be changed to POST. This change breaks the current GQL API, but confines with the recommended GraphQL API gateway.
Here is an example of a query with the new proposed GraphQL API:
POST /v1/metering/aggregated/usage/graph HTTP/1.1
Content-Type: application/json
{
  "query": "
    OrganizationUsageSummary($orgId: String!, timestamp: Int!) {
      organization(organization_id: $orgId, time: $timestamp) {
        resources {
          ...resourceSummaryDrillDown
        },
        spaces {
          resources {
            ...resourceSummaryDrillDown
          }
        }
      }
    }

    fragment resourceSummaryDrillDown on Resource {
      plans {
        aggregated_usage {
          windows {
            summary
          }
        }
      }
    }
  ",
  "variables": {
    "orgId": "231c2397-f3b6-4d74-bf2b-e0490f49394c",
    "timestamp":<PHONE_NUMBER>286
  }
}

The advantage of this:
A consumer of the API can save his complex queries in a *.graphql file, and load it into the request without using string replacements to inject variables. This allows the developer to then use GraphQL related tools & IDE support.

I see.
We released 1.0 and plan to fix a few things and craft 1.1 soon. The change from get to post can get into 2.0 branch. WDYT?


Proposal
https://github.com/heartcombo/devise/blob/main/lib/devise/rails/routes.rb#L406
# (Non edited snipped to help understand)
def devise_registration(mapping, controllers) #:nodoc:
        path_names = {
          new: mapping.path_names[:sign_up],
          edit: mapping.path_names[:edit],
          cancel: mapping.path_names[:cancel]
        }

        options = {
          only: [:new, :create, :edit, :update, :destroy],
          path: mapping.path_names[:registration],
          path_names: path_names,
          controller: controllers[:registrations]
        }

        resource :registration, options do
          get :cancel
        end
      end

Either fix the gem so that the create/update match the route of mapping.path_names[:sign_up] and mapping.path_names[:edit] or add extra path_names to configure the create/update path names.
Another solution would be to extract non-related registration actions to a new controller like "profile controller"
I'm actually suprised nobody ever came up with this. Am I doing something wrong?

Hey! Sorry I'm a bit confused here since you can set any path name for "user/edit" as well with e.g edit: "change" so your full route will look like
edit_user_registration GET    /registration/change(.:format)                             devise/registrations#edit

so all the route names are customizable.

Hey! Sorry I'm a bit confused here since you can set any path name for "user/edit" as well with e.g edit: "change" so your full route will look like
edit_user_registration GET    /registration/change(.:format)                             devise/registrations#edit

so all the route names are customizable.

Hi,
I haven't re-checked in a while, but what you are saying is already demonstrated and it's saying the POST routes targets the root.


Added descriptions to the pipeline parameters.

All parameters needing descriptions across: A2T, I2I, I2V, T2I, and Upscale have had their descriptions added.

@EAsuperstar one thing that you also have to do which I forgot to mention in the bounty description is to regenerate the OpenAPI spec and Golang bindings. You can checkout the Main Readme and Runner Reademe for a guide on how to do this.


Add A Wide Memo Column

Just realized I didn't provide a description!! :/
This adds an option to make the memo column wider, and to do so it shrinks the payee and category columns. The option is set in "Options" in the extensions list.
I did this following my research for the comment on the Trello board about adjustable columns

I think this is a good idea, but it becomes extremely difficult given the way we need to manage the setting for it (presumable it's in the options page). I'm thinking in terms of the way it sacrifices the payee and category columns.
This is just constructive thoughts on how we can figure out a better overall solution.

Fair enough - I've added a card now, to see what others think.
https://trello.com/c/V4WAROrZ/65-make-memo-column-wider

This last change (main.css) is actually the update for the color blind fix

I pulled the colour blind mode changes in manually (b05b115812b18596d4b6f92b91f00be686576903), but I think we'll leave the column changes for a bit to get some feedback from the community. I know it's much more complicated but from a user perspective I'd rather have the option, "Adjustable columns" and then you click and drag to adjust. What do you reckon?
In the future it's much easier for me to merge if we keep each pull request to one feature, but I'm really excited for this one.
I also fixed up the inspector colours so they match the grid as they looked like this:
Instead of like this:
.
Thank you again! :+1:

That's great! :smile:
I'm going to close this pull request now then, and if wide memo gains enough traction I'll open it again.


HuggingFacePipeline not working

System Info
langchain==0.0.219
Who can help?
@hwchase17
@agola11

Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction

from langchain import HuggingFacePipeline
mod = HuggingFacePipeline(model_id="tiiuae/falcon-7b-instruct", task="text-generation")

Traceback (most recent call last):
File "", line 1, in
File "/home/guillem.garcia/miniconda3/envs/rene/lib/python3.10/site-packages/langchain/load/serializable.py", line 74, in init
super().init(**kwargs)
File "pydantic/main.py", line 341, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 1 validation error for HuggingFacePipeline
task
extra fields not permitted (type=value_error.extra)
Expected behavior
I expect it to work. When I instance a Pipeline with falcon using hugginface it works.
Also, Is there a way to deactivate pydantic? It makes it impossible to modify anything or make langchain compatible with our code

@GuillemGSubies I think there's a mistake in your code, it should be:
mod = HuggingFacePipeline.from_model_id(model_id="tiiuae/falcon-7b-instruct", task="text-generation")
You have to use the from_model_id method, the constructor doesn't expect a task parameter.

Indeed, thank you very much


Support for .NET Core

We should add support for .NET Core (https://www.microsoft.com/net/core), the new high-performance, cross-platform .NET runtime, and eventually transition to it as the main build target. This will allow P# to work on any operating system and device that .NET Core supports out of the box. This is more of a longer term task, does not require immediate action.

The core P compiler targeting P# is being ported to .NET Core. We should evaluate what it will take to support .NET Core in P#. As the lead developer on the new P compiler, I would be glad to help with this.

@alexreinking My understand was that the P compiler will emit P# code and stop at that. In that sense, while it is useful for P# to support .NET code, it is not a blocker. Is this correct? Please feel free to take the first stab at this. The P# team can get involved as we get a better sense of the work involved.

Yes, it is not a blocked to finishing the compiler work. But, the full benefit of porting the compiler over to .NET Core will not be realized until the runtime is also .NET Core.  Cross-platform is a big deal in my team in Azure.   Our C# code base targets .NET Core.

@shazqadeer I just added support for .NET Core/Standard (tested it in both Windows and Linux).

The production runtime is fully ported.
The tester currently works only in sequential mode (no portfolio or parallel testing) because it needs quite a bit of work to change the WCF dependency (which we need for spawning multiple testing processes) which is not supported in .NET Core.
The rewriter/compiler (from the high level P# syntax to the C# library version) is not ported yet because of some missing APIs in .NET Core (which should be available soon'ish though).

Great milestone, congrats!  Moving to .NET Core is very important going forward since we want to make P# and RSM a compelling option for both first-party and third-party cloud services.
From: Pantazis Deligiannis<EMAIL_ADDRESS>Sent: Monday, July 30, 2018 5:12 AM
To: p-org/PSharp<EMAIL_ADDRESS>Cc: Shaz Qadeer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [p-org/PSharp] Support for .NET Core (#117)
@shazqadeerhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshazqadeer&data=02|01|qadeer%40microsoft.com|be63c8c4ceab4a1d688908d5f615a471|72f988bf86f141af91ab2d7cd011db47|1|0|636685495173571604&sdata=EI7ZUyVJfPPeUptzCWA7kN3b5jTjql1uv8yzZnGRBsA%3D&reserved=0 I just added support for .NET Core/Standard (tested it in both Windows and Linux).

The production runtime is fully ported.
The tester currently works only in sequential mode (no portfolio or parallel testing) because it needs quite a bit of work to change the WCF dependency (which we need for spawning multiple testing processes) which is not supported in .NET Core.
The rewriter/compiler (from the high level P# syntax to the C# library version) is not ported yet because of some missing APIs in .NET Core (which should be available soon'ish though).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fp-org%2FPSharp%2Fissues%2F117%23issuecomment-408842395&data=02|01|qadeer%40microsoft.com|be63c8c4ceab4a1d688908d5f615a471|72f988bf86f141af91ab2d7cd011db47|1|0|636685495173581609&sdata=YoAtpFuIkKGSTdAubtr1kyPEYVS7%2BJnD734TART2LgA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHURFrL5XyAI6PWJOutdLUoMzgiaqstRks5uLvgKgaJpZM4L3INR&data=02|01|qadeer%40microsoft.com|be63c8c4ceab4a1d688908d5f615a471|72f988bf86f141af91ab2d7cd011db47|1|0|636685495173581609&sdata=ziB3S1fg93oVgHYnE0U3ilczivODzyROgZgse9WSEgU%3D&reserved=0.

This is great news! The P# backend is coming along nicely, and it will be great to break the dependency on Windows-specific libraries.

Azure Blockchain team is considering taking a dependency on P#.  Our production and test environment needs to be on .NET Core.  Based on the original post by @pdeligia, my understanding is that P# already satisfies our requirement because we can run PSharpTester on .NET Core in sequential mode.  That would be fine for us. But I just wanted to confirm.

That is correct. We should be able to support the parallel mode in the tester by the time your team gets warmed up. The missing part that might take time is the high level syntax.
Akash
Sent from my iPhone

On 11-Aug-2018, at 5:04 AM, Shaz Qadeer<EMAIL_ADDRESS>wrote:
Azure Blockchain team is considering taking a dependency on P#. Our production and test environment needs to be on .NET Core.  Based on the original post by @pdeligia, my understanding is that P# already satisfies our requirement because we can run PSharpTester on .NET Core in sequential mode. That would be fine for us. But I just wanted to confirm.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the clarification.  High level syntax is not a big deal.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Akash Lal<EMAIL_ADDRESS>Sent: Friday, August 10, 2018 7:45:29 PM
To: p-org/PSharp
Cc: Shaz Qadeer; Mention
Subject: Re: [p-org/PSharp] Support for .NET Core (#117)
That is correct. We should be able to support the parallel mode in the tester by the time your team gets warmed up. The missing part that might take time is the high level syntax.
Akash
Sent from my iPhone

On 11-Aug-2018, at 5:04 AM, Shaz Qadeer<EMAIL_ADDRESS>wrote:
Azure Blockchain team is considering taking a dependency on P#. Our production and test environment needs to be on .NET Core. Based on the original post by @pdeligia, my understanding is that P# already satisfies our requirement because we can run PSharpTester on .NET Core in sequential mode. That would be fine for us. But I just wanted to confirm.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fp-org%2FPSharp%2Fissues%2F117%23issuecomment-412245831&data=02|01|qadeer%40microsoft.com|606223695ccc4fe6e8d508d5ff3480a5|72f988bf86f141af91ab2d7cd011db47|1|0|636695523315891078&sdata=CtTOcJ9v8%2FwN0XLW1z16mXqDMpcPMd3Yv3WoV%2FWUp4I%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHURFvIPNYGMWVBnZoVwq4Q6t-DjUq7zks5uPkVJgaJpZM4L3INR&data=02|01|qadeer%40microsoft.com|606223695ccc4fe6e8d508d5ff3480a5|72f988bf86f141af91ab2d7cd011db47|1|0|636695523315891078&sdata=Wis0lf%2FEoHeaGXqf8HNFsnJswCZUa%2FPSsWPnso9IqNs%3D&reserved=0.


STM32 UART: Request RX data flush on async_rx_enable

When enabling async RX the first time after boot, there is an additional byte received with the first RX_DATA_RDY event, which seems to be caused by the RX data not being flushed before enabling the UART RX DMA.
Adding a request to flush the RX data register before enabling the RX DMA, solves the issue.
To recreate the issue, connect the RX and TX UART pins on a b_u585i_iot02a board, and use the following overlay:
/*
 * Pins 2 and 3 must be connected to each other on the STMOD+1 connector to
 * loopback RX/TX.
 */

/ {
	aliases {
		test-uart = &usart2;
	};
};

&gpioh {
	misc_fixed_usart2 {
		gpio-hog;
		gpios = <13 GPIO_ACTIVE_HIGH>;
		output-high;
	};
};

&gpdma1 {
	status = "okay";
};

&usart2 {
	pinctrl-0 = <&usart2_tx_pa2 &usart2_rx_pa3 &usart2_rts_pa1 &usart2_cts_pa0>;
	pinctrl-names = "default";
	current-speed = <115200>;
	/* hw-flow-control; */

	dmas = <&gpdma1 0 27 STM32_DMA_PERIPH_TX
		&gpdma1 1 26 STM32_DMA_PERIPH_RX>;
	dma-names = "tx", "rx";

	status = "okay";
};

and add the following Kconfig options:
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y

Then build and run this application:
#include <stdio.h>
#include <string.h>
#include <zephyr/kernel.h>
#include <zephyr/drivers/uart.h>

static const struct device *uart = DEVICE_DT_GET(DT_ALIAS(test_uart));
static uint8_t rx_buf1[16];
static uint8_t rx_buf2[16];
static uint8_t rx_buf3[16];
static size_t rx_buf3_len;

static void uart_async_event_handler(const struct device *dev,
				     struct uart_event *evt, void *user_data)
{
	switch (evt->type) {
	case UART_RX_BUF_REQUEST:
		uart_rx_buf_rsp(uart, rx_buf2, sizeof(rx_buf2));
		break;

	case UART_RX_RDY:
		rx_buf3_len = evt->data.rx.len;
		memcpy(rx_buf3, &evt->data.rx.buf[evt->data.rx.offset], evt->data.rx.len);
		break;

	default:
		break;
	}
}

int main(void)
{
	uint8_t data[] = {1,2,3,4};

	uart_callback_set(uart, uart_async_event_handler, NULL);
	uart_rx_enable(uart, rx_buf1, sizeof(rx_buf1), 30000);
	uart_tx(uart, data, sizeof(data), 1000);
	k_msleep(100);
	printf("Transmitted: %u\n", sizeof(data));
	printf("Received: %u\n", rx_buf3_len);
	return 0;
}

You will see the following output without this PR
*** Booting Zephyr OS build zephyr-v3.5.0-1188-g97654a5e092e ***
Transmitted: 4
Received: 5

Compared to this if the fix in this PR is added
*** Booting Zephyr OS build zephyr-v3.5.0-1188-g97654a5e092e ***
Transmitted: 4
Received: 4

Thanks @bjarki-trackunit. Can you have a look to https://github.com/zephyrproject-rtos/zephyr/pull/65320 ?

Very interesting, I haven't noticed this issue. I got the one additional byte only if any transfer happens before enabling the async transfer. Maybe it is chip dependent problem.


[TASK] Wall model for IPDA

Description of task
Wall model with 4 states describing the x and y coordinates of the end points
Suggested Workflow
No response
Specifications
No response
Contacts
No response
Code Quality

[ ] Every function in header files are documented (inputs/returns/exceptions)
[ ] The project has automated tests that cover MOST of the functions and branches in functions (pytest/gtest)
[ ] The code is documented on the wiki (provide link)

Will be added in vortex-sensorfusion instead

Will be added in vortex-sensorfusion instead


Deployment list gets wiped out if an IDE window is opened or closed

This is especially frustrating with long-running deployments like Flex, that disappear from the list and there is no indication of when they're finished, or the exit status. There is also no exception thrown or error logged anywhere. The Application Servers window only goes green for a bit. This is happening on Linux.
To reproduce, open or close an IDE window in another project with a populated deployment list. I only tried to open projects in the same window, although it might also be reproducible by opening in a new window.

I'm able to reproduce this on window close. It may be related to the logic we have that we have that cleans up running deployments when the IDE is closed and it not being smart enough to know that there is still another IDE window open (and the deployments created with window A get wiped out even if a new window B is closed).

Just reproduced this. We really need to fix it.