[DPE-4977] Run integration tests against Juju 3.6

Issue
We need to soon support this charm on juju 3.6. In order to prepare, we are going to run the integration tests against juju 3.6 on a nightly schedule
Solution
First run juju 3.6 tests on PR to ensure that code is geared towards successful runs
Then use dpw to run juju 3.6 tests only on a nightly schedule

The run for 7107c2a shows that all tests (except test_backups.py on GCP) pass on either arm64 or amd64. As a result, we should run juju 3.6 tests on a nightly schedule and attempt to iteratively debug the issues preventing from fully green pipelines.


DD-6 Debugging listener triggers twice

Means that debugging is turned on-off simultaneously. Possible case where both stages has debugging listener and both stages executes it.

Just remove toggle feature, left on/off options


GetFullPath should use concatenation

From @glennc on Wednesday, January 21, 2015 3:06:32 PM
GetFullPath can concatenate instead of doing Path.Combine. This saves us from situations where Path.Combine will ignore part of the provided path if it is rooted.
Method should fail if someone is asking for a rooted file. Once this is done then GetFileInfo can also have unnecessary guard clauses removed.
// @blowdart
Copied from original issue: aspnet/FileSystem#39

Thanks for your feedback. We appreciate your letting us know about the problem you've encountered or suggestion but we are not planning to take further action on this issue because our focus has been on issues with significantly higher customer interest and issues impacting a broad number of customers.


MacOS scripting

Feature description
The hot-reload should be implemented for MacOS.
Tasks

[ ] Implement file::MacosFileWatcher
[ ] Implement script::MacosCompiler
[ ] Implement script::MacosLinker
[ ] Make sure it works as expected

I will be closing this issue as new features are now being tracked in another place.


font fixes and stopwatch widget

Thanks, Dom.  This is the first sample app from someone other than myself!  I added comments about a few minor issues above.


Add initial JHU schemas and example

Creates an initial metadata schema set for PASS at JHU.  Uses the flat metadata structure as described in the design doc
Largely reproduces existing metadata fields as-is, with the following notable exceptions:

The global schema adds a new agreements property, which enumerates the various agreement text(s) agreed upon, and the repositories they pertain to.
Adds validation for DOIs to ensure they are of the form 10.123/foo.bar.z, rather than, say doi:10.123... or http://dx.doi.org/10.123...

How to test
We should probably add tests to validate the schemas upon commit, and validate example data at some point (out of scope for this PR).  In the meantime, please focus on the high-level content of the schemas

look at the global schema jhu/global.json and the example data at  examples/jhu/full.json.  Are we happy with the property names?  Is there any opportunity to fix past mistakes?.
look at the required property of the schemas and see if it actually matches the requirements of DS, or the repositories being deposited into.  Note that:

The global schema requires title, journal-title.  Does this reflect the globally required fields for all of PASS?
The common schema doesn't claim any specific required fields of its own.
The JScholarship schema requires authors
The NIHMS schema requires journal-NLMTA-ID and ISSN.

Resolves #1 #2 and #3

This all looks correct to me and is what I was anticipating. In terms of fixing past mistakes, the variation in property name format bothers me somewhat (publicationDate, Embargo-end-date, journal-NLMTA-ID etc).  I would prefer there to be a consistent convention. I realize that will impact Deposit Services though, so I defer to @emetsger on whether it is worth fixing.

@birkland NIHMS schema should require either NLMTA OR ISSN. it doesn't require both.

@birkland how difficult it to update the schema at a later date with more consist letter case usage?  in other words, howmuch trouble would it be, if we merge this PR without making decision on whether to fix the cases and go back to fix it later?

Updating the schema is easy, coordinating with deposit services and Ember
is the hard part.  So let's merge this, and create a ticket to update the
field names later?
On Mon, Feb 18, 2019, 11:41 PM Hanh Vu<EMAIL_ADDRESS>wrote:

@birkland https://github.com/birkland how difficult it to update the
schema at a later date with more consist letter case usage? in other words,
howmuch trouble would it be, if we merge this PR without making decision on
whether to fix the cases and go back to fix it later?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OA-PASS/metadata-schemas/pull/5#issuecomment-464980140,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfm-buJXsgs2AIrWSSV1YYuZSL7c5IJks5vO4BjgaJpZM4a8B0G
.


Remove spring binder test module

This PR is used to enable the new feature of the pipeline for supporting multiple spring boot and spring cloud version compatibilities.

/azp run java - spring - tests

/azp run spring tests

/azp run java - spring - tests


Please provide a way to re-authenticate in the same request (clear AuthenticationHandler._authenticateTask)

Hello aspnet team,
Sometimes I store sensitive information in the user claims which needs to be recomputed when a user changes their password. This means that I need to call Context.Authentication.AuthenticateAsync to reissue the cookie (for example. in the case of CookieAuthenticationHandler) to do it transparently during the POST of the password change action.
However, because AuthenticationHandler<TOptions>.HandleAuthenticateOnceAsync() does a short-circuit check to check if a task is already present in _authenticateTask and simply returns, I cannot reissue the cookie. There is simply no code path that set _authenticateTask to null.
I'm forced to either:

Log the user out and ask them to re-login (to clear the cookie).
Store this info outside claims somewhere else and have to duplicate encryption/security logic which is already nice and good in CookieAuthenticationHandler.

Is there any workaround I can use to force reissuance of the authentication ticket/cookie ? It is not easy to try to inherit from the authentication middleware because the offending logic is in the base AuthenticationHandler class and I'd have to duplicate the whole thing to implement it and reimplement all auth middleware to use my new base class.

SignOut should clear the cookie, and you can call SignIn to issue a new cookie.  FYI Identity uses the OnValidateIdentity event on cookies to invalidate a cookie for a similar scenario, you should be able to do the same thing.

Or they could just assign the User on the current HttpContext.

Setting the user on the context doesn't affect anything past the current request, but that's certainly the easiest option if you just want to alter the claims for the current request.

Thanks for the tip! I was able to get it to work by calling getting the claims on a variable, then calling SignOutAsync followed immediately by a SignInAsync passing in the claims.
One little ugliness was the need to call AuthenticateAsync to get at the AuthenticateContext from which I could reach the IsPersistent property (to maintain the cookie type).
Something must have changed here, I wasn't able to get it working in RC1 before.
Thanks again!

Sure (as it has always been), but that's all they're asking for.

No, I needed to alter the persisted claims in the cookie for all future requests, not just the current request, so just updating the claims in the context wasn't enough.

Actually even calling SignOut wasn't needed.

Nope, SignOut followed by SignIn on the same request is a no-op anyways,
since both modify the cookie and the last one will win.
On Thu, May 26, 2016 at 12:48 PM, Raif Atef<EMAIL_ADDRESS>wrote:

Actually even calling SignOut wasn't needed.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/aspnet/Security/issues/847#issuecomment-221974880


Help Wanted: FXGL Trailer

At some point it would be nice to have a trailer for the framework showing off some cool features from various existing demos.

Link to FXGL 11 Trailer


Update update.sh

A commnon pattern for addon with mutiple subaddons, is to keep teh sub addons in subdirecories
With this patch update,.sh will operate o every toc file in the tree
Check  [(https://github.com/alarofrunetotem/ItemLevelDisplay] for this patttern

Thanks for reporting this, although your PR was a bit of a mess so I just fixed it myself.


[Feature] Expose Ray --logging-level parameter

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Ray allows to set up logging level on start, as in ray --logging-level error start .... However, kuberay doesn't allow setting this option, as it is not a ray start parameter, but ray parameter. The feature request is to allow setting this parameter (and maybe the --logging-format one too) in RayCluster and RayService.
Use case
I would like to reduce the clutter in my cluster logs, as the default logging level is info. Some messages can be filtered, but there is a lot of multiline ones (e.g. autoscaler dumps info every 5 seconds).
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Can we discuss this issue before CRD transferred and freezed as v1?
I can provided MR, if there is interest in it.
Will it be more convenient to have some explicit configuration in nodeTemplate, like rayInitParams, оr just add this with some env variables?


add cancellation tokens

Adding async Tasks CancellationTokens
Fixes to some of the IntegrationTests

Hi,
Thanks for the PR. But this does not really add the cancellation to requests.

You should pass CancellationToken all the way to HttpClient methods.
Also you don't need to use code:

using (var registration = cancellationToken.Register(cancellationToken.ThrowIfCancellationRequested))
{
}

Just pass the token to HttpClient.

Public API signatures for example looks like this:
public async Task<IList<Group>> SearchAsync(string search, CancellationToken cancellationToken)
This is a bit hard to use because you need to construct the cancellation token every time. We should provide methods like this:
public async Task<IList<Group>> SearchAsync(string search, CancellationToken cancellationToken = default)

using of = default requires C# 7.1.

Hi,
Thanks for comming  back :)
I have to say that I agree only with passing the cancelation token to the http request
@ cancellationToken.Register - it will throw cancelation requested exception on execution time which is needed since we are not passing the cancellation token to the http request.
@having default value, cancellation token in most cases is autogenerated by the .net framework and you don't need do construct a new cancelation token every time in case when used in synchronous context you can simply use CancellationToken.None...

Hi,
Thanks for the PR.
As I said in previous review we should use   public async Task<IList<Group>> SearchAsync(string search, CancellationToken cancellationToken = default) (C# 7.1 syntax)   to simplify calling of the public methods needing CancellationToken, it's inconvenient for the library User to pass CancellationToken or CancellationToken.None if you just don't care about cancellation.
Also you should not call cancellationToken.ThrowIfCancellationRequested(); in every method, just do it deeper inside, I think GitLabApiRequestor class is a good fit for that.


compile environment

Hi, rayanelleuch. Are these code running in Linux environment or Windows environment?

Hey,
I only tried on linux. I cannot really say for windows.
But I will probably delete this repository soon.
Google released the code for this paper in
https://github.com/tensorflow/models/tree/master/object_detection
So the repository is not really relevant any more.
On Tue, Aug 15, 2017 at 2:29 PM, xzha8059<EMAIL_ADDRESS>wrote:

Hi, rayanelleuch. Are these code running in Linux environment or Windows
environment?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rayanelleuch/Speed-accuracy-trade-offs-for-modern-convolutional-object-detectors/issues/4,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJsHBH3dlMunvTbsyKFC4d1L12_yLq95ks5sYSzMgaJpZM4O3M_f
.

Thanks for your reply.


What is the difference between InternConvertedInternLMAttention and InternLMAttention?

InternLMAttention is used in huggingface: https://huggingface.co/internlm/internlm-chat-7b/blob/main/modeling_internlm.py#L257
InternConvertedInternLMAttention  is used in this repo: https://github.com/InternLM/InternLM-XComposer/blob/main/huggingface/internlm-xcomposer/modeling_InternLM.py#L732
I set intern_converted_llm to false and found that the results were all wrong. What is the difference between InternConvertedInternLMAttention and InternLMAttention?

Hi, set the intern_converted_llm to False will not load the bias of the linear layers in the attention layer, the code will be cleaned in the future update.

@LightDXY I fixed this bug, but it's still wrong.


iOS embedder corrupts the scene if its Paint() method is not called

To fix https://github.com/flutter/flutter/issues/69552 we changed the engine to always Preroll all layers even if they may be culled. (See https://github.com/flutter/engine/pull/22336)
As a result, layers may now be Prerolled even if they won't eventually be painted on a given scene.
The iOS embedder was not expecting this behavior and so it can leave visible pieces of its embedded view on the screen after it is scrolled away. (See https://github.com/flutter/flutter/issues/76097) Note that the Android embedder does not have this same issue, so this is a design issue with the way we manage the iOS embedder.
A work-around was added to always Paint all layers in a sub-tree that contains a PlatformViewLayer. (See https://github.com/flutter/engine/pull/25824)
If the iOS embedder is taught to not make assumptions about Paint() being called, then the work-around mentioned above can be deleted.

@flar Thanks for the summary. Does submitFrame always get called in this situation?

@flar Thanks for the summary. Does submitFrame always get called in this situation?

I'm not sure what goes on in the embedder, I'm just looking at it from an Engine "flow" layers perspective.
The conditions under which this happens is when a parent Clip layer realizes that it isn't visible on the screen (maybe because it is nested inside another clip with no intersection, or maybe it was placed just off-screen). In that case the Clip used to make the decision on behalf of its children that it won't bother to preroll them and we'd also end up not calling their Paint().
We now preroll all children because that was faulty logic. The clip might believe it's children won't be painted, but we have other reasons to paint things that end up calling the Paint() methods anyway. So, now we Preroll all children even if they are not visible.
As a result we will always call PlatformViewLayer::Preroll() any time it is in a scene even if it isn't visible.
And in cases like the test case in the associated issue, we don't then follow that up with a call to PlatformViewLayer::Paint() and we end up with stale pieces of the embedded view on the screen.
The Android embedder is fine in this case. It will not carve out any pieces of the screen if we call its Preroll and don't call its Paint().
I think what is happening is that whatever calls we make to the embedder in the Preroll() method have the iOS embedder think "OK, so I'm going to appear on screen, I'll make note of that. For simplicity I'll leave the previous bounds/area that we last appeared in still active and assume that the Paint() call will fix that". In the Paint() method it revises the concept of where and how much of it appears and updates that data. The problem is that if we don't actually call the Paint() method (as in the case of being clipped out) then we are left with the stale data.
@chinmaygarde and I briefly looked at the code that computes what is visible and thought that perhaps if we simply invalidated it in the Preroll flow that we would end up with a potentially expensive situation where it recomputes the exact same visible portion on every frame, but that may have been a mistake assumption. In the end, since calling the Paint() method fixed the problem we decided to just work out a way to have the layers always call Paint() on a PlatformViewLayer as the simplest solution. If someone can figure out how to have Preroll not enable a stale "viewport" or whatever it computes, then that would be a more targeted solution. And possibly, if correcting the viewport data is expensive, have a way to mark it as "stale" without destroying it and then the Paint() method can mark it "current" after reevaluating the contextual data. If it's not expensive to recompute, then perhaps the Preroll() method should clear it out so that we don't leave a hole punched in the app if we don't end up calling Paint()?

Also, what's the desired behavior in this situation? If paint is not called, should the platform view not be displayed? Or should the platform view keep the same composition behavior (position, size, clips etc)?

If Paint() was not called, it shouldn't paint. The fact that its painting may happen somewhere else in the frame cycle (i.e. not directly inside the Layer::Paint() call) is incidental. Preroll just gathers data and doesn't imply that a layer will paint. Paint() is the method that implies "now go ahead and show yourself" - so if we don't call Paint() on a given frame, then don't paint anything...

No action is needed at this point

No action is needed at this point

A performance-sapping workaround can now be removed:
https://github.com/flutter/engine/blob/387f6f3c5fdba18f547e2d403169286702e18867/flow/layers/layer.h#L228


Add us_state_abbreviation_transformation

Thanks for the neat PR! Like I mentioned in other comments, I'm a bit concerned about the coverage of the changes. Please take a look at https://github.com/GEM-benchmark/NL-Augmenter/pull/181, which seems to be an earlier PR with broader coverage. If you believe you two's are similar enough, I'd strongly encourage you to create another PR if you'd like!

Hi @tongshuangwu , many thanks for your constructive comments.

Adding expanders/shorthands for other countries, province, or even other kinds of terms.
This is a good point! We will work on expanding the scope to other countries and states. We will save the mapping into a separate json file as you recommended.
Have you considered doing the other way around, i.e. abbrev -> full form?
Yes, in the current version, if an abbreviation of a state is detected, it will be converted to the full name.

I believe this transformer is different from  #181 since we also include abbreviation -> full name, and it will have a broader scope of worldwide countries and states.

@sebastianGehrmann

Looking great now, thanks!

@RoyRin , Thank you very much for your valuable comments. I addressed them in my latest PR: https://github.com/GEM-benchmark/NL-Augmenter/pull/281. Thanks!


Add WithTraceInfo that returns the logger with trace ID from the request

Add a helper method to lager that returns a logger with trace information parsed from the request. We are planning to use this method across the components so it would be nice for logger to have it.

@mariash some thoughts:
❓Are you sure that this is the place to put this logic?
This logic seems very specific to an individual use-case for lager with zipkin in Cloud Foundry. Maybe it would be better to include it in a separate dependency that uses lager to emit the log line.
❓Are you intending to support more headers?
Word on the grapevine is that there may be more headers to support down the line, and if that's the case it would be nice if this method was setup to handle that right now.
❓Is everything that's going to be doing tracing happening in the context of an HTTP request?
It seems feasible that somewhere you may want to set trace-id or span-id properties that aren't contained in an http.Request. If so, it would be nice to make the input more generic and provide helper functions that do some of the trace ID / span ID extraction from http.Request.

@ctlong
❓Are you sure that this is the place to put this logic?
We thought it would be nice to have it here, since we will use this method in every request handler across different components. We can make a separate package that extends lager logger if there is a preference to not mix this into this package. I see the point that it is more specific to CF than other methods.
❓Are you intending to support more headers?
No we don't intend to support more headers.
❓Is everything that's going to be doing tracing happening in the context of an HTTP request?
So far I have not seen a use case for the request context. We usually have an http handler, that sets up logger session and then this logger is being passed in to other methods. If we happen to need it in the future we can modify the method to look up in the context and then in the header.

I am closing this PR, I think it makes sense to have this in a separate package since this is very CF specific method


Query with a list of fragments is not generated properly

Setup
query PeopleQuery {
      people {
            ...PeopleFragment
      }
}

fragment PeopleFragment {
     id
     name
     lastName
}

The people node returns a type called PeopleInformation
Expected
The expected should be to have a list of PeopleFragment. Just as it is in the iOS version of this library
Actual
The generated class acts as if no fragment was used.  PeopleQuery.Data will contain something similar to this:
...
final @NotNull List<PeopleInformation> peopleInformation
...

Thus making the type PeopleQuery.PeopleInformation instead of using fragment

I was doing operation on the outer element and not the inner, thus I could not see the fragments, the generated class works fine! 👍


precompiled linux binary or even better provide some binary Repos

Hi there!
I would be very glad if there would be a binary build for linux would be provided or even better provide some packages or repos for biggest distributions (openSuSE, Ubuntu (via PPA), RedHat, Fedora, anyone I am missing :) )

I have tried to compile litecoin on Fedora 13, but openssl from the repo is missing edcsa, and it doesn't honor my custom location.


Revert BluedogDB-v1.7.1 compat change

This reverts commit 026defc567c50b4801b253ae9ff6ad0082eccdcc.
That commit was the bot picking up on https://github.com/CobaltWolf/Bluedog-Design-Bureau/commit/4f345c1727f6988df9a474b5f8e3ab0eed0bf1bb. Since the VERSION is updated for a new release, the compat update from CobaltWolf/Bluedog-Design-Bureau#1040 is no longer available.
This should be merged after KSP-CKAN/NetKAN#8434.

The PR is merged and the commits are here:

https://github.com/KSP-CKAN/CKAN-meta/commit/e709dac46e8e022ae34f6743275a8c40b22f8244
https://github.com/KSP-CKAN/CKAN-meta/commit/e6bfc4a0bf5aa28ab99739cf89b38f095d9f179f


Remove address from PeerId

I propose that we move PeerId::address into Peer struct

A few concerns from my side:

Address is not used by Iroha for identifying peers. Iroha uses only the public key.
Address is a relative, environment-dependent value. Peer A and peer B can see address of peer C differently. And these values are stored in blockchain.

Thus, it is slightly confusing from UX perspective, because users have to provide the address via sumeragi.trusted_peers config and peer Register/Unregister instructions.

Implemented in #5176


DCR: Add Complete LUIS Endpoint as overload param for LuisRecognizer

Proposed change
Add LUIS Endpoints as an overload constructor param for the LuisRecognizer classes. A complete LUIS endpoint contains all of the necessary information for the bot to call LUIS. A LUIS endpoint can be obtained from visiting the portal. Calling a couple Authoring APIs can also yield the necessary information to construct a endpoint.
Example endpoint with LuisRecognizer-necessary information identified (e.g. <Endpoint>)

https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/########-####-####-####-############?subscription-key=################################&q=

<Endpoint>/luis/v2.0/apps/<AppID>?subscription-key=<Subscription-Key>&q=

Customer Impact
By having endpoint be a supported param for constructing a LuisRecognizer, developers using flat-formats for storing their LUIS information do not need to separate each required param for a LuisRecognizer.
E.g. a .env file can now look like this:
LUIS_WEATHER_ENDPOINT=https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/<AppId>?subscription-key=<SubscriptionKey>&q=

And appsettings.json can look like this:
{
  "LuisWeatherEndpoint": "https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/<AppId>?subscription-key=<SubscriptionKey>&q="
}

Instead of
LUIS_WEATHER_ENDPOINT=
LUIS_WEATHER_APP_ID=
LUIS_WEATHER_SUBSCRIPTION_KEY=

And
{
  "LuisWeatherEndpoint": "https://westus.api.cognitive.microsoft.com",
  "LuisWeatherAppId": "<AppId>",
  "LuisWeatherSubscriptionKey": "<SubscriptionKey>"
}

To construct a new LuisRecognizer in Node.js, one could use the following line:
const recognizer = new LuisRecognizer(process.env.LUIS_WEATHER_ENDPOINT);

Instead of
const recognizer = new LuisRecognizer({
  applicationId: process.env.LUIS_WEATHER_APP_ID,
  endpoint: process.env.LUIS_WEATHER_ENDPOINT,
  endpointKey: process.env.LUIS_WEATHER_SUBSCRIPTION_KEY
});

Tracking Status
Dotnet SDK

[x] PR
[ ] Merged

Javascript SDK

[ ] PR
[ ] Merged

Java SDK

[ ] PR
[ ] Merged

~Python SDK~ (botbuilder-ai Not yet implemented)

~[ ] PR~
~[ ] Merged~

[dcr]

Note the C# implementation actually adds the overload to a class called LuisApplication in addition to the LuisRecognizer class. In the TypeScript this is just an interface so we should add the code directly into the LuisRecognizer constructor.

assigning to @stevengum
This https://github.com/Microsoft/botbuilder-dotnet/pull/1378 is approved and waiting on your PR for JavaScript.


Fix permissions denied error in Apache Virtual Host configuration

This introduces a bug where no-where will offer http-auth when http-auth enabled


TSiLiHit and TS3Hit GetEnergy()=0

The energies are fine in the fragment tree but I've never managed to get energies out of the analysis tree in this version of GRSISort.
I thought it might be something to do with Copy operators or setting the address so I tried doing an overhaul of the SiLi, SiLiData and SiLiHis (and s3 equivalent) to bring them up to scratch with Copy operators etc but as I didnt fix this problem that's sat on my fork un-pulled
Charge is fine, all the extra data members I want are fine, but the GetEnergy looks like it isnt finding a calibration
/tig/midtig02_data/tiguser/SPICETestAnalysis/SPICETestAugust2015/run35661_000.mid
/tig/midtig02_data/tiguser/SPICETestAnalysis/CalibrationFile.cal

My guess is that this is related to #558. Are you seeing the same problem? If you don’t set the address, and therefore the channel, the code can’t find the proper calibration.

On Oct 28, 2015, at 7:23 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
The energies are fine in the fragment tree but I've never managed to get energies our of the analysis tree in this version of GRSISort.
I thought it might be something to do with Copy operators or setting the address so I tried doing an overhaul of the SiLi, SiLiData and SiLiHis (and s3 equivalent) to bring them up to scratch with Copy operators etc but as I didnt fix this problem that's sat on my fork un-pulled
Charge is fine, all the extra data members I want are fine, but the GetEnergy looks like it isnt finding a calibration
/tig/midtig02_data/tiguser/SPICETestAnalysis/SPICETestAugust2015/run35661_000.mid
/tig/midtig02_data/tiguser/SPICETestAnalysis/CalibrationFile.cal
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559.

I thought that, but I tried setting the addresses for SiLi S3 (I didnt try fixing tigress) and it had no effect.
Also the issue of #558, the Tigress works fine and gives energies when loaded directly from the command line (or just after analysis tree sort) but in these situations SiLi and S3 still give 0

Ok I’ll try downloading your files and see if I can find the bug. My internet here is slow, so It might take me a bit.

On Oct 28, 2015, at 9:56 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
I thought that, but I tried setting the addresses for SiLi S3 (I didnt try fixing tigress) and it had no effect.
Also the issue of #558 https://github.com/GRIFFINCollaboration/GRSISort/issues/558, the Tigress works fine and gives energies when loaded directly from the command line (or just after analysis tree sort) but in these situations SiLi and S3 still give 0
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152069177.

So it's going to take me 4 hours to download the Midas file, and it's already getting pretty late. I'll give this a shot tomorrow and let you know if I find anything. (Hotel Internet is Terrific)

I haven't had a chance to confirm this yet but it might be that the energy flag is not being written to file as zero for these classes. If you set energy during build this could be the problem. One does not need to set the energy during the build portion. I thought in forced the flag to zero, but this might be bypassed. I'll check in a bit, just thought I'd let you know if you want to look at it.

On Oct 28, 2015, at 9:56 PM, jsmallcombe<EMAIL_ADDRESS>wrote:
I thought that, but I tried setting the addresses for SiLi S3 (I didnt try fixing tigress) and it had no effect.
Also the issue of #558, the Tigress works fine and gives energies when loaded directly from the command line (or just after analysis tree sort) but in these situations SiLi and S3 still give 0
—
Reply to this email directly or view it on GitHub.

So I'm fairly confident this is the problem. The TGRSIDetectorHIt streamer is not being called for all TGRSIDetectorHIt. I'm trying to decide how to solve this, but the easy one is to put our own streamer function into each Hit class, and have it call TGRSIDetectorHit::Streamer() before writing. I will try this with S3, if it works I'll push my work and we can add the rest later.

So it turns out my streamer fix is not the way to go here. The streamers are not called when the events are written to a tree. The easy fix is probably to remov the SetEnergy, SetDetector, SetTime statements from the building of the hit. I will try to come up with a way to force this flag to be set to 0 even if you do something like setting the flags to true during the build process.

We could add a ResetFlags function that resets all bits to zero and call that one before filling the event into the tree in the TAnalysisTreeBuilder?

Yes that would work.

On Oct 29, 2015, at 10:19 AM, Vinzenz Bildstein<EMAIL_ADDRESS>wrote:
We could add a ResetFlags function that resets all bits to zero and call that one before filling the event into the tree in the TAnalysisTreeBuilder?
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152233248.

We could put a TGRSIDetector virtual function, but would still have to define that function in each derived class as it would have to know how many hits to loop through. We may also have to define a default virtual version in TDetector that does nothing in order to get it to work with the TGRSIDetectors.

On Oct 29, 2015, at 10:21 AM, Ryan Dunlop<EMAIL_ADDRESS>wrote:
Yes that would work.

On Oct 29, 2015, at 10:19 AM, Vinzenz Bildstein<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
We could add a ResetFlags function that resets all bits to zero and call that one before filling the event into the tree in the TAnalysisTreeBuilder?
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152233248.

The energies and times weren't set in the hit construction, but it looks like there's some redundancy in the data making and that the detector was. I've tried removing this for the S3 and will see if it helps (this Spice data still takes an age to sort, so we won't know for about 20 minutes...). Would this also affect the energies?

This change did nothing (although I'll leave it in, because it's entirely redundant). So currently, no energies, times or detectors are set in the hit construction.
Worth nothing that GetTime() returns non-zero values.

So on my fork (I have just sent a pull request) I cleaned up both sili and s3 so they set almost nothing themselves, everything was set by passing a fragment to the base TGRSIDetectorHit class.
They are both (sili particularly) simple detectors so I am trying to make them as generic as possible (To shift the blame onto TGRSIDetector).

Ok I have a few minutes to look again. I think when I looked at get time I was getting a non zero but clearly wrong number.

On Oct 29, 2015, at 11:18 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
So on my fork (I have just sent a pull request) I cleaned up both sili and s3 so they set almost nothing themselves, everything was set by passing a fragment to the base TGRSIDetectorHit class.
They are both (sili particularly) simple detectors so I am trying to make them as generic as possible (To shift the blame onto TGRSIDetector).
—
Reply to this email directly or view it on GitHub.

Is there anything special about the spice mnemonincs?

On Oct 29, 2015, at 11:18 AM, jsmallcombe<EMAIL_ADDRESS>wrote:
So on my fork (I have just sent a pull request) I cleaned up both sili and s3 so they set almost nothing themselves, everything was set by passing a fragment to the base TGRSIDetectorHit class.
They are both (sili particularly) simple detectors so I am trying to make them as generic as possible (To shift the blame onto TGRSIDetector).
—
Reply to this email directly or view it on GitHub.

It uses the subsystem to setup the analysis tree (i.e. "SPI" and "SPE" are treated differently in the analysis tree). The segments are also treated differently, because they have up to 120 channels.

So it seems that the flag for energy is definitely being set somewhere. It is being written to file as a non-zero. investigating further…

On Oct 29, 2015, at 11:32 AM, jhenderson88<EMAIL_ADDRESS>wrote:
It uses the subsystem to setup the analysis tree (i.e. "SPI" and "SPE" are treated differently in the analysis tree). The segments are also treated differently, because they have up to 120 channels.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152258694.

I think I found it. It was a bug in TGRSIDetectorHit. We never noticed it before because we did not make a call that you guys did. Our TGRSIDetectorHit::SetPosition was setting the energy flag…because that makes sense. The Sili and S3 were setting the position. which was setting the energy flag in the file. I’m very glad you found this because it may have caused bugs in our stuff.
You do not need to set position ahead of time, but we can figure that out later.

On Oct 29, 2015, at 11:32 AM, jhenderson88<EMAIL_ADDRESS>wrote:
It uses the subsystem to setup the analysis tree (i.e. "SPI" and "SPE" are treated differently in the analysis tree). The segments are also treated differently, because they have up to 120 channels.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152258694.

Actually this bug didn’t affect us at all because its only called during the SetPosition(TVector3) call which we never use. It’s still good that this popped up.

On Oct 29, 2015, at 11:32 AM, jhenderson88<EMAIL_ADDRESS>wrote:
It uses the subsystem to setup the analysis tree (i.e. "SPI" and "SPE" are treated differently in the analysis tree). The segments are also treated differently, because they have up to 120 channels.
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/issues/559#issuecomment-152258694.

Reopen, per discussion,


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in 606c118.


Add JournalPageSheet for Foundry VTT v10.279

To Change
JournalPageSheet
Kind of Change
Add
Additional Info
No response

resolved by #2119


fileWrite appends in end "NUL" simbol

fileWrite appends in end "NUL" simbol
code:
fileWrite("test.txt","test")

I'm unable to reproduce this (running on the latest master version) using a simple E2:
fileWrite("test.txt", "Hello World")

Inspecting the bytes of the written data/e2files/test.txt:

Hex ASCII
48
65
6C
6C
6F
20
57
6F
72
6C
64

Char
H
e
l
l
o

W
o
r
l
d

All good, there is no null terminator at the end.
/unable-to-reproduce

@OriaOriginal Before reporting issues, please, make sure that server is running on the 'latest' version of Wire from GitHub. You can check your Wire version by using wireversion console command.

Maybe there could be a miscalculation or rounding issue in the ReadData

I'll try


feat: common components

ACs:

[x] https://github.com/zolotokrylin/svelboost/pull/1#issuecomment-871380711

https://github.com/amplify-labs/factor-app/issues/1

[ ] @georgeciubotaru within this PR please implement Chromatic:

@zolotokrylin Invite me to this new Chromatic Storybook so I can review the components in future. Thx

@markholdex https://www.chromatic.com/builds?appId=60dc698bd6a4f60039a51ae4

Components look good. Although, the Metamask pop-up fonts didn't match in the Live preview everything was good in the rendered version.


Auto detect first day of the week

Might I suggest to repurpose this PR for your component? For a bit less than half the world, the week starts on another day than sunday.
https://github.com/julienr114/vue-calendar-heatmap/pull/14
https://www.timeanddate.com/calendar/days/first-day-of-the-week.html

It would be great if this could be fixed


directory upload not working

Current behavior:
Directory upload is apparently currently not working, when uploading a directory we get the flowing console out and nothing gets uploaded :
before folder/Screenshot_2022-04-08_10-35-37.png fileupload2.js:61:21
Screenshot_2022-04-08_10-35-37.png  fileupload2.js:558:13

Uncaught TypeError: right-hand side of 'in' should be an object, got undefined
    queueFileForDirectUpload https://gdcc.github.io/dvwebloader/src/js/fileupload2.js:559
    onchange https://gdcc.github.io/dvwebloader/src/js/fileupload2.js:62

Expected behavior :
No error/files uploaded
Reproducing steps :
Use Dvwebloader to upload a directory

With a quick look at the code, I think this can happen if you click select directory before the call to check the dataset for existing files completes. I'll fix that but a workaround is probably just to delay clicking select folder - either for a few seconds or watching in the console for the call to Dataverse to complete.

This should be fixed. The Select a Directory button is disabled until the query to get Dataset info is complete, and it is removed once you've chosen the directory.

Thank you,
I indeed fixed it, however it turns out the underlying issue was a missing api token.
Now thanks to your fix the error is clearly pointing to that.


package and distribute via setup.cfg

Hey!
Overview
Latest version of setuptools come with setup.cfg configuration. This pull request introduce this new pratices.
Benefits

keep pipenv up-to-date with the latest python packaging best practices
decreases setup.py verbosity
extract configuration of python code
improve version management

Changes introduced

introduce latest best practices for python packaging
extract version number from package meta or from configuration file (final install or develop install)
manage requirements based on python version with more pythonic way
manage publish and upload via Makefile
dynamicaly generate Makefile helping message

Bye!

Do you want I squash my commits?

@4383 if you wouldn't mind squashing, that would be great. This is a PR I'm going to delegate to Kenneth because he's probably got an opinion. Thanks for taking the time to put this together!

@nateprewitt commits squashed!

fixing conflict introduced by v8.3.0

Not happening — requires modern setuptools, which people don't always have. I don't consider this best practice (yet), but we'll get there, hopefully within the next year.


Memory Leak

Hi,
I'm facing memory leak issues when querying the Windows Event Log through this lib.
I'm new to Golang so properly I'm just doing something wrong. I found the issues #27 and #3 and maybe there is still a memory issue around.
I created a little code snip you can execute which shows the issue: https://github.com/nook24/wmi_windows_eventlog/blob/main/main.go
This Code is running on Windows Server 2016

Even if the numbers are different from what Task Manager reports the memory usage is rising in Task Manager as well.

We are also having same issue and now we are testing it. Anybody else having the same problem?

We are also having same issue and now we are testing it. Anybody else having the same problem?

In my case, it was due to wrong syscall usage. We use WMI heavily and it's good so far.

In my case, it was due to wrong syscall usage. We use WMI heavily and it's good so far.

What do you mean by wrong syscall usage? We are using WMI a lot, and it looks like that the memory leak does only happen when querying the Windows Event Log.
Do you also query the Windows Event Log and if yes, how does your implementation differ from my I posted above?
My current workaround for this is to use PowerShell and not WMI to get the Job done, but I din't like this: https://github.com/it-novum/openitcockpit-agent-go/blob/main/checks/eventlog_windows.go#L90-L117

I mean, we have a lot of syscalls in the app and one of them was causing our memory leak. In your case, I wouldn't know. But we also have a lot of wmi calls and we don't have any memory leak at the moment, so maybe this package is not the reason.
Fyi, we use syscalls to collect event logs. Using wmi would be slower and would use more resources. I would suggest you to drop wmi calls for events.
For perfmon, I would also suggest syscalls.

I found this on another thread @nook24 https://github.com/influxdata/telegraf/issues/6807#issuecomment-590256733. Does this help?

NOTE: This project is no longer being actively maintained.
We recommend you refer to this fork: https://github.com/yusufpapurcu/wmi


Dynamic number of Module list columns

Is your feature request related to a problem? Please describe.
When you open the /modules of Cyclops UI, you will see modules listed as cards in three columns regardless of the size of the screen. It would be more readable if the number of columns was dynamic based on the size of the screen. On large screens, the cards are too wide, while on narrower screens, they are squeezed in.
Wider screen:

Narrow screen:

Describe the solution you'd like
Make the number of columns dynamic based on the screen width

How does this look ?

Hey @Tapasvi48, looks good! Can you open a PR for it?

hey i have linked the pr for the issue please check it


Symlink Error in Shared Server

Laravel Version: 5.3.*
Voyager Version: 0.11.6
PHP Version:5.6.4
Database Driver & Version:

Description:
my app is in production and i cant create symlink in my shared hosting. I have tried php artsian storage:link and works fine in local development environment but not in production sever.
error: symlink(): no such file or directory
can  i do anything so that i can directly upload my files in public folder instead of storage\app folder
I have tried making disk in config/filesystems.php as
'voyager' => [
	        'driver' => 'local',
	        'root' => public_path('storage'),
	        'url' => env('APP_URL').'/storage',
	        'visibility' => 'public',
        ],

this too works in at local server and not in production server

This issue does not relate to voyager.
See: https://github.com/the-control-group/voyager/issues/898


Error When Using colorBlend + Imagick

When trying to use the colorBlend adjustment I get the following error when loading the page:
Error

Call to undefined method Imagine\Imagick\Imagick::setImageClipMask()

[...]/craft/plugins/imager/services/ImagerService.php(1290)

This is the line it's referring to.
I am testing locally with PHP V7.1.1 + Imagick V3.4.3RC4 (compiled with ImageMagick V7.0.4-6),
and was using the sample code for the color blend:
{% set transformedImage = craft.imager.transformImage(image, { width: 500, effects: { colorBlend: ['rgb(255, 153, 51)', 0.5] } }) %}

It seems that the colorBlend adjustment is the only one that causes and error, I've tested the rest without issue.
Anyone else experience this? Any thoughts as to what could be causing the error?

I think ImageMagick v7 deprecated quite a few things, and I haven't really tested it yet since none of the distros I use come with it installed. If you don't need ImageMagic v7, I suggest compiling against the latest version of v6.

Ahh, yeah, I believe you're right. Thanks for the quick response!


role assignment: drop default group name when --scope is provided

Fix #6178
This could become a general pattern that I can move the code to core, but so far only role assignment commands have such a ask, hence I am holding on that.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

By present-day security standards, --resource-group should be dropped, needless to say its default value configured via az configure (https://github.com/Azure/azure-cli/issues/24753).


Resource Audit not available with Reader Roles

Resource Audit for Privileged Access Groups is not available with the standard security reader and global reader roles.
what roles are required to satisfy least privilege access and be able to use resource audit for Privileged Access Groups?

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

ID: dc32d928-d9e6-3270-3da1-002f2d0fa125
Version Independent ID: 98cb3ede-b0ad-ee32-7aa7-0399bbbcf15f
Content: View audit report for privileged access group assignments in Privileged Identity Management (PIM) - Azure AD
Content Source: articles/active-directory/privileged-identity-management/groups-audit.md
Service: active-directory
Sub-service: pim
GitHub Login: @curtand
Microsoft Alias: curtand

@ChrisSidebotham
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for pointing this out. I made a pull request to add the role requirements. https://github.com/MicrosoftDocs/azure-docs-pr/pull/186167
CC @curtand
As noted in the related PIM audit document, access to audit history requires either a Global Administrator or Privileged Role Administrator role.

@MarileeTurscak-MSFT
I have submitted on MSFT StackOverflow - pretty sure its a bug if you look at this document PIM - Least Privilege by task then audit reports should on require Security Reader, which currently does not work.


So I noticed if I sign in with the anticheat bypass on and then turn it off, the game still continues to work.

Is this intentional, or is the anticheat still being bypassed? I would like to know because I don't want my account to be banned.

The Anti-cheat driver can not work on wine at all, and it's still not clear why user can still log in but anyway that's the current situation.


Docker container does not start, fail with below message

Digest: sha256:c7926b18f6d6e22a2a31b4e60c2f5f055c2ca3c61d6530f29ef52bda787981a2
Status: Downloaded newer image for marcelstoer/nodemcu-build:latest
fatal: Not a git repository (or any parent up to mount point /opt/nodemcu-firmware)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
cp: cannot stat 'tools/esp-open-sdk.tar.gz': No such file or directory
Docker Version:
Docker version 1.12.0-rc2, build 906eacd, experimental

Looks like you cloned it to the wrong folder. See https://github.com/marcelstoer/docker-nodemcu-build#clone-the-nodemcu-firmware-repository


react-native 0.62.0 - Animated: useNativeDriver

I have gone through these following points

[x] Check latest documentation: https://docs.nativebase.io/
[x] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
node, npm, react-native, react and native-base version, expo version if used, xcode version
node: v12.14.1
npm: 6.14.4
react-native: 0.62.0
native-base: 2.13.12
Expected behaviour
Actual behaviour
Get some warning in react-native console since react-native 0.62.0.
 WARN     Animated: "useNativeDriver" was not specified. This is a required option and must be explicitly set to "true" or "false".
Steps to reproduce
Just run a react-native app and use some components with animation without specify useNativeDriver, like <Toast>.
Is the bug present in both iOS and Android or in any one of them?
Both iOS and Android.
Any other additional info which would help us debug the issue quicker.

Same here :)

Same here. Please fix this issue

Same <Item> with floatingLabel
<Form>
    <Item floatingLabel>
        Username
        <Input />
    </Item>
    <Item floatingLabel last>
        Password
        <Input />
    </Item>
</Form>

for toast replace ~\node_modules\native-base\dist\src\basic\ToastContainer.js by this code https://pastebin.com/mDfeg13E
or you can add useNativeDriver manually, just search animated.timing on nativebase module
sory for my bad english

This would make a great first contribution for somebody to create a Pull Request for. It will mostly be a matter of finding all instances of Animated.timing or Animated.spring and adding useNativeDriver: false
Ideally useNativeDriver: true should be used for performance, but to match the current implementation of this library and avoid any headaches with working out which values can/cannot be natively driven and any elements that might have both native and JS driven animations it'll be safest just to throw useNativeDriver: false on all instances.

Same error here!

I have same error.

Created a PR for this per @levibuzolic comments above: https://github.com/GeekyAnts/NativeBase/pull/3136
Currently using my fork to avoid the yellow warnings until they merge or fix and it's working fine for me now:
"dependencies: {
...
"native-base": "https://github.com/dansokol/NativeBase.git",
...
}

Created a PR for this per @levibuzolic comments above: #3136
Currently using my fork to avoid the yellow warnings until they merge or fix and it's working fine for me now:
"dependencies: {
...
"native-base": "https://github.com/dansokol/NativeBase.git",
...
}

Waiting for merge)

in ***\node_modules\native-base\dist\src\basic\Item.js search on 'animated.timing' and add  'useNativeDriver: false' to every callback function, this gonna hide the warning, (if u add useNativeDriver: true, you gonna face an error tell you that nativeDriver do not support Top (bla bala)), sorry for my bad english.

I got the warning using any of the input labeled from NativeBase. I saw that it was merged but still got the warning after the update. Does anyone know if it must make any configuration manually?

I only updated the "src" directory.
Wasn't sure if I should be committing to the "dist" directory as well.  Think it will be in the next update that compiles the src directory and updates the "dist" directory.

Would be great to have the latest release soon

same yellow warning here :(

Any update on this issue @akhil-geekyants ?

Waiting for this

@astrahov

Same <Item> with floatingLabel
<Form>
    <Item floatingLabel>
        Username
        <Input />
    </Item>
    <Item floatingLabel last>
        Password
        <Input />
    </Item>
</Form>

in ***\node_modules\native-base\dist\src\basic\Item.js search on 'animated.timing' and add 'useNativeDriver: false'  ex: _reactNative.Animated.timing(this.state.opacAnim,{toValue:0.7,duration:150, useNativeDriver: false}).start();}}

@levibuzolic it looks like there is a PR waiting for this to be rolled out.  Can we please get this merged?

Guys.. this is impacting everyone using latest ReactNative .. it would be helpful to all if admin can rollout the fix soon ...

Go Team .. It impacting everyone using latest ReactNative ... Can you help us by making the latest release available please

same warning... :(
don't want to downgrade rn version
plz fix it asap

is there any quick solution for this?

@damasofc downgrade .net below 0.62
Or the admins could merge the PR and deploy @levibuzolic

Hi ! any news on this ?

I've been using patch-package to keep the changes until the PR merges. I highly recommend it as the tool keeps the changes whenever a new version is released and an issue was never reconciled in the new version. Nice band-aid until admins merge the PR.

Any news on this?????????????

Same here, any news?

Any update

same here, any updates for this fix ?

for now on

Created a PR for this per @levibuzolic comments above: #3136
Currently using my fork to avoid the yellow warnings until they merge or fix and it's working fine for me now:
"dependencies: {
...
"native-base": "https://github.com/dansokol/NativeBase.git",
...
}

Waiting for merge)

Currently using this fork until the update rolls out.

https://github.com/dansokol/NativeBase.git PR working for me as well

Any luck on this? Any chance of getting a new npm version rolled out by this week?

I'm also waiting for a fix, any news ?

same warning -_- , I'm waiting updates for fix this

Facing same issue from a long time and still no update from native-base developers yet.
We will have to wait till they officially fix it, or they do merge the existing PR for the fix.
Meanwhile use workaround to avoid irritating yellow warnings of useNativeDriver.
Do addition of following lines in your App.js file.
import {YellowBox} from 'react-native';

componentDidMount() {
    YellowBox.ignoreWarnings(['Animated: `useNativeDriver`']);
}

Hi, how can i fix this issue?
Animated: `useNativeDriver` was not specified. This is a required option and must be explicitly set to `true` or `false`
    in Item (at connectStyle.js:392)

            <Form>
                <Item floatingLabel>
                <Input placeholder="Username" />
                </Item>
            </Form>

When are they going to merge it into the release?

merge it please...

Hi all,
Even if the urge to do so is very high, please refrain from posting "me too" comments.
The PR is available and merged (see message above from 8 May by @AdrianoCahete ), so it will eventually be released according to the release schedule. Until then, there is only a very slight annoyance, namely a yellow spot in development mode (it will not appear in production), but other than that everything works as designed. Further more, for those who absolutely need to remove this yellow spot from their development experience, there are various fixes posted in this Fred.
Cheers and have fun, Remi.

@Remigius2011 it's been 3 months since this PR was merged and there has been no new releases for quite a while. If you are bothered by the "me too" comments maybe ask someone you know to release a new version that contains this fix.

It is still an issue in React native 0.63.0

@Remigius2011 when is the expected time for the new release?

I have forked the repo to fix this issue.
npm i @codler/native-base

Version 2.13.13 was just released and contains the fix for this issue.

@darrylyoung thanks!! Tested and working.

Tks God, tks team!!! You are amazing!

I'm still receiving the issue after updating to 2.13.13 (also using Expo 38).

Still an issue
- node_modules/react-native/Libraries/Animated/src/AnimatedImplementation.js:365:6 in result.start
- node_modules/native-base/dist/src/basic/ToastContainer.js:1:3656 in onPanResponderRelease

Also have the issue with Toast. Same as above

Recieving the following when closing toast:
Animated: useNativeDriver was not specified. This is a required option and must be explicitly set to true or false
react-native: 0.62.2
react-base: 2.13.13

Recieving the following when closing manually toast:
Animated: useNativeDriver was not specified. This is a required option and must be explicitly set to true or false
react-native: 0.62.2
react-base: 2.13.13

I'm getting the same warning.
react-native: 0.62.2
native-base: 2.13.13

Also have the issue with Toast. Same as above
"native-base": "^2.13.13",
"react-native": "0.62.2",

  useEffect(() => {
    LogBox.ignoreLogs(['Animated: `useNativeDriver` was not specified.']);
    return () => {};
  }, []);

I found a very strange bug in Toast. When the toast is shown, the yellow warning also comes up for "useNativeDriver" although I am already on 2.13.13. After the toast is closed, I cannot click the buttons shown or covered by the toast area. Now, I replaced the Toast with RN Alert .. ugly but working now.

I have the same problem and resolved temporary with https://github.com/GeekyAnts/NativeBase/pull/3200, however in the last version 2.13.14 it was already fixed!

Upgrade to "native-base": "^2.13.14",  this solved the problem

Upgrade to "native-base": "^2.13.14", this solved the problem

Not for me it didn't...

Upgrade to "native-base": "^2.13.14", this solved the problem
Not for me as well...

Add to your project the following import
import { YellowBox } from 'react-native';
YellowBox.ignoreWarnings([
'Animated: useNativeDriver was not specified.',
]);

Hello Im also still facing issue with nativeDriver for the deck swiper.

Just added PR #3278 to fix this issue in the DeckSwiper, Fab, and ToastContainer components.

Is it already published on npm ? Im using 2.13.14 and im having that issue with FAB.

I have gone through these following points

[x]  Check latest documentation: https://docs.nativebase.io/
[x]  Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x]  Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x]  Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
node, npm, react-native, react and native-base version, expo version if used, xcode version
node: v12.14.1
npm: 6.14.4
react-native: 0.62.0
native-base: 2.13.12
Expected behaviour
Actual behaviour
Get some warning in react-native console since react-native 0.62.0.
 WARN Animated: "useNativeDriver" was not specified. This is a required option and must be explicitly set to "true" or "false".
Steps to reproduce
Just run a react-native app and use some components with animation without specify useNativeDriver, like <Toast>.
Is the bug present in both iOS and Android or in any one of them?
Both iOS and Android.
Any other additional info which would help us debug the issue quicker.

WARN Animated: "useNativeDriver" was not specified. This is a required option and must be explicitly set to "true" or "false"`.
############## Solution ##############
->  where use Animated.timing fuction then add useNativeDriver = true  <-
like:  Animated.timing(this.animatedValue, {
toValue: 0,
duration: popupDuration,
useNativeDriver: true
}),

WARN Animated: "useNativeDriver" was not specified. This is a required option and must be explicitly set to "true" or "false"`.
############## Solution ##############
-> where use Animated.timing fuction then add useNativeDriver = true <-
like: Animated.timing(this.animatedValue, {
toValue: 0,
duration: popupDuration,
useNativeDriver: true
}),

WARN Animated: "useNativeDriver" was not specified. This is a required option and must be explicitly set to "true" or "false"`.
############## Solution ##############
-> where use Animated.timing fuction then add useNativeDriver = true <-
like: Animated.timing(this.animatedValue, {
toValue: 0,
duration: popupDuration,
useNativeDriver: true
}),

I don't repro as of
"native-base": "^2.15.2",

Release notes confirm this was an intended fix: https://github.com/GeekyAnts/NativeBase/releases/tag/v2.15.2

Yes, this should be closed as it was fixed in #3278 and released in 2.15.2.


Is it worth considering supporting rails 5 with Spin?

Is it worth considering supporting rails 7 with Spin?


Fix bulk export of relationships with caveats

The structs change made the export not properly copy the caveats

Updated


Terminal doesn't use custom bash profile when debugging

redirected here from closed issue https://github.com/microsoft/vscode/issues/80434
The bug appeared after one of few last updates.
When integrated terminal starts it uses custom profile (as expected),
but after python script is started it loads profile from ~/.bashrc
In my settings.json I have the following settings:
"terminal.integrated.shellArgs.osx": [
   "--rcfile", "/Volumes/DISK/projs/TechStuff/settings/profile"
],
"terminal.integrated.env.osx": {"HISTFILE":"/dev/null"},
"terminal.integrated.setLocaleVariables": false,

Environment data
Version: 1.38.0
Commit: 3db7e09f3b61f915d03bbfa58e258d6eee843f35
Date: 2019-09-03T21:47:00.464Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.7.0
Expected behaviour
using custom profile (environment)
Actual behaviour
using standard profile (environment), after starting python script
Steps to reproduce:

Assign custom profile to integrated terminal settings.(and restart maybe)
Open page(tab) with any python script and open integrated terminal.
(You can put string like   echo 'bashrc loaded'  in profile file  to see it loads)
Check profile - it is cutom.
Debug python script (F5 or Debug  -> Start Debugging) - it loads bashrc profile instead of custom
Check which profile is loaded (can use printenv command if you set different env. variables or check echo print as mentioned above) - standard profile loaded.

Hello @KV34 👋 Thank you for reaching out.
Sadly I could not reproduce your issue in the following environment:

OS: macOS Mojave 10.14.6
VS Code version: 1.38.0
Python extension version: 2019.9.34911

Could you please provide some extra info, namely:

Which version of the Python extension for VS Code you have
Which shell you are using
Whether it happens no matter which shell you are using (bash, zsh, sh...)
Whether the custom profile is loaded properly when you open new terminals (+ icon next to the terminal dropdown):

Thanks!

I use the Windows 10 and I have the same issue. Details of the issue in my environment are reported in the microsoft/vscode#80434.

Hello kimadeline, Thanks for quick reply.
There is no effect when you run from context menu.
Try from main menu:  Debug->Start Debugging

my versions:

I'm using bash
will try with custom profile later
when new terminals created it loads properly

Thank you for the clarification @KV34, I could reproduce your issue when debugging the script instead of just running it 👍

I have the same issue on win10.
I find the debug terminal does not load the arguments given in terminal.integrated.shellArgs.windows, while the terminal launched with ctrl+` load them.
For example, my settings.json is given as
{
    ...
    "terminal.integrated.shell.windows": "D:\\Program Files\\Git\\bin\\bash.exe",
    "terminal.integrated.shellArgs.windows": ["-l", "-i"]
    ...
}

When launched with ctrl+`, the terminal is a login shell ("-l" works), and loads the profile.
When debugging, the arguments "-l" and "-i" are missing.
My "hacky" solution is to manually source the profile in ~/.bashrc
source "/d/Program Files/Git/etc/profile"

The bug is more than just the bashrc file. On Windows, I have my default terminal set to WSL bash, but for some projects I want to override it and use the regular Windows terminal. I can't even start the debugger, because it tries to execute python.exe in linux bash, which clearly does not work.

I appear to be running into the same issue:
"terminal.integrated.shellArgs.linux": [
    "-l"
],

is being ignored by the Python Debug Console (I don't get some custom env vars in my .profile). Regular terminal instances, "Run Python File In Terminal", and tasks of type "shell" are in contrast, seem OK. Note: I have terminal.integrated.inheritEnv set to false.

Hello everyone, feel free to 👍 the original issue to bump up its priority.
Thank you!

Hi, I had the same problem in my Mac, but I fixed it by following the solution provided by Tyriar in a similar closed issue.
In a nutshell, my custom variables and settings were stored in my .bash_profile. The fix was to move everything to .bashrc and then just have 1 line in my .bash_profile:
source ~/.bashrc
Check also this interesting discussion on why this works and the priority of loading profiles.

is this issue resolved? I'm encountering the same issue on Windows when trying to debug remotely on Linux.
this issue is very important for debugging.

I can confirm I am experiencing this on a Mac too and it also happens when debugging a test from the Test Explorer:
Integrated terminal:

Test Explorer Debugger session:

VSCode version:
Version: 1.76.1 (Universal)
Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b
Date: 2023-03-08T16:32:09.831Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.3.0
Sandboxed: Yes

hello，since debugpy run as command
 /usr/bin/env /home/xxxxx/anaconda3/envs/yyyyy/bin/python /usr/local/xxxxx/.vscode-server/extensions/ms-python.debugpy-2024.4.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 34811 -- /home/xxxxx/zzzzz.py
which means it use vscode-server process's environment varible，and vscode-server not refresh its environment even if ~/.bashrc changed, until restart vscode-server in remote server.
for kill vscode-srever process, you have two method:

kill -9 $(ps aux | grep vscode-server | grep $USER | grep -v grep | awk '{print $2}'), from https://code.visualstudio.com/docs/remote/troubleshooting
You can also change your user environment via .bashrc and run the "Kill VS Code Server on Host" command, and reconnect, to start a new instance of the server with the new environment
from: https://github.com/microsoft/vscode/issues/155255


Support uploading and tailoring user's avatar image

See: https://forum.casbin.com/t/91
In future, Casbin-forum will use Casdoor as authentication and user management, so I think we will manage the user avatar in the scope of Casdoor.
For where to store the uploaded avatar image, we can use this: https://github.com/qor/oss to provide support for multiple OSS providers.

Working on this.

Project in my branch has been deployed at https://door-hk.chromium.link.
Click "My Account - Upload Avatar" to tailoring and uploading an avatar.

Hi @hsluoyz
Is this issue open?
I am new to casbin and want to contribute to it. Currently, I am going through the codebase. Can you please provide me with some resources to understand how to start with this issue?

Fixed by: https://github.com/casbin/casdoor/issues/18


refactor: Remove legacy deployer

Removes the legacy deployer. Account contracts are now "deployed" by directly calling the constructor. This means that account contracts are by default privately deployed and cannot execute public function calls.
Note that this will break once we require fee payment for every action. In order to allow an account contract to pay for its own deployment, we'll have to supply a FeePayload along with it, so the constructor can act as another entrypoint. Note that we cannot just have the entrypoint call the constructor because the entrypoint validates the call via an authwit, and this validation requires the contract to have been initialized.
Pending: publicly deploy the account when needed (eg public authwit check).
Builds on #4775

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 8307dadd and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
54,212
214,436
855,332

l1_rollup_calldata_gas
259,868
1,019,924
4,060,124

l1_rollup_execution_gas
354,054
1,139,372
4,281,525

l2_block_processing_time_in_ms
1,277 (-2%)
4,791 (-2%)
19,091 (-5%)

note_successful_decrypting_time_in_ms
223 (-3%)
607 (-1%)
2,207 (-6%)

note_trial_decrypting_time_in_ms
47.2 (-8%)
47.1 (-2%)
189 (-12%)

l2_block_building_time_in_ms
21,491
85,293 (+1%)
346,732 (-4%)

l2_block_rollup_simulation_time_in_ms
16,067
63,760
260,856 (-5%)

l2_block_public_tx_process_time_in_ms
5,390
21,432 (+1%)
85,545 (-4%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,886 (-1%)
31,823

note_history_successful_decrypting_time_in_ms
1,411
2,755

note_history_trial_decrypting_time_in_ms
170
218 (-14%)

node_database_size_in_bytes
19,124,304
36,274,256 (-1%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
338
44,664
27,457

private-kernel-ordering
214 (-1%)
45,777
14,627

base-rollup
1,746 (-2%)
175,344
933

root-rollup
83.4 (-1%)
4,192
825

private-kernel-inner
446
73,099
27,457

public-kernel-app-logic
276 (-1%)
32,254
25,379

merge-rollup
7.84 (-2%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts

tx_size_in_bytes
18,431

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
3,221
1,509 (-1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.0335 (+1%)
662 (-1%)


Fix React 18 FunctionalComponent bug

What's been changed

Wrapped WizardProps in Wizard.tsx with React.PropsWithChildren

Why is this needed?
One recent change in React 18 has been an update to the FunctionComponent or FC types as they have now had the optional children property removed (Source).

Thanks! I bumped against the same issue in another project

https://github.com/devrnt/react-use-wizard/releases/tag/v2.1.3

v2.1.3


Adding ability to hide node param from UI

This feature adds the ability for node params to mark themselves as hidden from the UI.
This is required for nodes which don't have static API credentials, but rather have session context tokens or otherwise that are dependent and change when the chatbot is embedded, and should not be set in the UI.
These params can still be targeted and passed a value through chatflowConfig options. In addition, the i info button continues to show these parameters inside of NodeInfoDialog so that developers know they exist.

There is a node in development and unfortunately not publicly available at this time. However, I will share what I can to give you an idea of why it's required and how it works.
We have an Enterprise application that is able to provide data in multiple ways, and would like a node to help with this. This application has a complicated sign-on infrastructure including single sign-on and federated authentication for N users, however once a user has authenticated they're given a unique session (or token) ID. This ID has a lifetime of the session, but is never fixed.
All of the data provided by the node is always in the context of the session. If user A signs on and uses the chat, they get different data than user B despite using the exact same chatflow. This is because the session ID is different between them, and injected at embed-time.
This is accomplished in multiple ways. First, the parameter itself in the node is marked as hidden like this:
{
    label: 'Application Session ID',
    name: 'ourApplicationSessionId',
    type: 'string',
    description: 'The ID of the session that should be used for accessing data from the application.',
    placeholder: 'Session ID',
    optional: true,
    hidden: true
},

The user never sees this part in the UI, nor do they need to care about it. For the embedded case it's obvious: the example embed code in EmbedChat has been augmented with something like:
chatflowConfig: {
    ourApplicationSessionId: window.getApplicationSessionId()
}

This addresses the embedding. However, for the case where they're using Flowise directly it requires something like:
incomingInput.overrideConfig.ourApplicationSessionId = ourSessionId
The next phase could be to extend Flowise with N users instead of just 1, but that's a much bigger feature.

thanks for the detail explanation! another thing I can think of is ssomething like OAuth2 scopes, where you want to get the specified scopes from the node on UI but dont want to display it out on UI.


fix: upgrade cookie to avoid CVE-2024-47764

using<EMAIL_ADDRESS>will flag a security warning about CVE-2024-47764

Thanks!


Layout expressions: Extend with more functionality

In the layout expressions project we have intentionally set the bar fairly low, in order to get to a basic implementation faster. As planned for the first release, layout expressions can only be used to evaluate to a boolean value. On the backend, only the hidden and required properties for layout components will be evaluated, while the frontend will evaluate other properties like readOnly and various properties in the edit properties for groups.
This issue tracks extensions to these expressions we've thought of, but won't necessarily arrive in the first version. These tasks should probably be extracted to separate issues when/if we start working on them, if the efforts to implement them are large enough.

[x] Recursive layout expressions

Passing an expression as an argument to an expression can be useful for more advanced logic. If we're implementing this, adding functions for and and or (both with any amount of arguments) is a given. An example of a recursive expression:
{
  "hidden": ["and",
    ["component", "some-other-component"],
    ["or",
      ["dataModel", "MyModel.Path"],
      ["dataModel", "MyModel.Alternative.Path"],
      ["dataModel", "MyModel.Third.Alternative.Path"],
    ]
  ]
}

[x] Expressions returning strings/non-booleans

We could also use expressions for conditionally swap out labels/texts in textResourceBindings, etc. If we do, there should probably also be function(s) to map known data model (etc) values to the appropriate text resource keys, handle the default case if no mapping is valid, etc. We should also implement functions like concat, toUpperCase, etc, for simple string manipulations. There would also be a use-case for the most basic function (possibly even implicit) where an argument is return verbatim (i.e. a lookup function):
{
  "textResourceBindings": {
    "title": "myTitle",
    "description": ["dataModel", "MyModel.Description"]
  }
}

[ ] Using expressions for values/calculations

We could possibly replace existing implementations for calculations with layout expressions as well. Care needs to be taken to ensure we don't restrict functionality in a way that makes it impossible to implement existing calculations that are already implemented in some apps - we'd like for a frictionless upgrade path to make use of layout expressions instead of RuleHandler.js.
Careful thought should go into designing this in a way that makes it easy (or at least possible) to implement calculations for rows in a repeating group (respecting potentially hidden/filtered rows). See discussion on Slack here. It should also be possible to implement a function for counting the number of rows in a repeating group.
One advantage to using expressions for calculation is automatic API support and possibly valdation to avoid client-side tampering (if implemented on the backend).
Example for a sum implementation:
{
  "id": "total",
  "type": "Input",
  "readOnly": true,
  "value": ["sum",
    ["component", "value1"],
    ["component", "value2"],
    ["component", "value3"]
  ]
}

Or concatenating strings to present a full name:
{
  "id": "fullName",
  "type": "Input",
  "readOnly": true,
  "value": ["concat",
    ["component", "lastName"],
    ", ",
    ["component", "firstName"]
  ]
}

[x] Using expressions for custom validations Moved to #726

This requires both validation (a boolean, in principle) and a validation message (a string, which could perform a lookup in text resources). We would also have to support soft validations. Consider if we should use a prefix like *WARNING* like we do today, or implement this using a custom not-just-string data type.

[ ] More argument types: Shadow fields

When we have an implementation for shadow fields, we should support lookup up those values.

[ ] Expression re-use

Large expressions should be possible to re-use. Either by separating them out to definitions (similar to a structure like in JsonSchema) and referencing them from there, or by implementing functions to directly reference other expressions:
{
  "id": "dependsOnSomethingElse",
  "type": "Input",
  "hidden": ["isHidden", ["component", "someOtherComponent"]]
}

Or, more generically:
{
  "id": "dependsOnSomethingElse",
  "type": "Input",
  "hidden": [
    "equals",
    ["getProperty", ["component", "someOtherComponent"], "hidden"],
    true
  ]
}

[ ] Hiding an entire row in a repeating group

A likely need/want is to use layout expressions to hide an entire repeating group row, possibly based on some data within it. This type of dynamic should be placed on the group component, and would in effect hide all components inside that row. It is an outstanding question if this should lead to the entire row being deleted when submitting the data, if this should not happen, or if it should be configurable.
See discussion on Slack

[ ] New function: contains (and support for lists/arrays, with a list function)

A much-discussed need is a function that allows you to check if a value is in a list of values. This is needed to assert if a certain checkbox has been checked, but as long as #273 is unsolved, this would also require support for comma-separated values. An alternative is creating a temporary function for this exact case (inCheckboxValue or inCommaSeparatedList).
See discussion on Slack

[ ] New function: in

Shortcut function similar to equals, but compares the first argument against multiple others to check if the first argument matches either one of them.
See discussion on Slack

[ ] New function: text

Function used to look up a text resource key, resolving to the value of it. This is not really that relevant for backend code, so perhaps we could limit this so it's only possible to use it in frontend-evaluated expressions.

[ ] New function: language

Function used to look up the current language (nb, en, etc).

It is important that the "hidden"-parameter also allows expressions like "contains" and "notContains" in addition to the existing "equals" and "notEquals". Please make sure that null-values can be allowed so you can add a new row to a repeating group without it disappearing. Every field in the new row is null until you write and save something there.

Very relevant:

https://github.com/Altinn/app-frontend-react/issues/1105#issuecomment-1536240868

All of the functionality described above has now been moved into more detailed issues, which are meant to be bite-sized so that we can start implementing them.

#389
#726
#1176
#1177
#1178
#1179


Incremental feature flags rollout

Task/Issue URL: https://app.asana.com/0/72649045549333/1204971805879942/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3355   👈

This comment was auto-generated by Graphite.


[FIX] Use vue event instead of addEventListener to fix ssr bug

Hi,
I had an issue when using SSR.
Element in a  component would always display the placeholder.
The problem came from a race condition where this.$el.getAttribute('src') !== this.srcPlaceholder would always be equal when the load event is called.
So instead of adding a js event, i used the vue method inside the render function which solved the issue.

Hi, this PR is not ok.

From one side, the package.json shouldn't be changed
From the other, the IntersectionObserver listener must be on the mounted hook, otherwise wouldn't be initiated

Closing the issue, fixed it in 2a6e8e0. Thanks a lot for the contribution!


Update Java test assertions to reflect name change

Summary

Resolves #422
Use Cases

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Bump :-) @pivotal-david-osullivan


tests: drivers: Fix adc labels in sensors test

Fix the labels used in io-channels to be consistent in whole tests/drivers/build_all/sensor/adc.dtsi file.

@teburd Could you take a look please?


inadsense Quarto extension

Link to suggestion
https://github.com/jskherman/inadsense
Targeted section
Extensions
Describe your suggestion

This extension provides shortcode support for including ad units into Quarto html documents on a website or blog.

Checklist

[X] checked if your suggestion is not already listed in Awesome Quarto list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

@jskherman I have found your Quarto extension on GitHub. Is it ok for me to include it here, in particular, is it stable?


workaround for hanging rig-pump communication (with WW pump)

This will reboot the rig if hanging rig-pump communication is detected.
This pull request also improves logging, has more robust killing of reset.py if it hangs.
The root cause of this issue is discussed here https://github.com/oskarpearson/mmeowlink/issues/60

This code runs on my rig now. Installs fine and I did some tests that the scripts work. Feel free to test and improve. I will report later if there are no downsides, so that it can be merged to dev.

@PieterGit here the pump log you requested:
Settings refreshError, retrying
Starting pump-loop at Thu Apr 20 23:52:21 CEST 2017:
2017-04-20 23:52:22,722 DEBUG Import spi_serial
2017-04-20 23:52:22,725 DEBUG spi_serial not installed. Assuming not using spidev
2017-04-20 23:52:22,726 DEBUG Import oref0_subg_ww_radio_parameters
2017-04-20 23:52:22,765 DEBUG Parsing ./pump.ini
2017-04-20 23:52:22,769 DEBUG Serial device (port) for pump is: /dev/ttyACM0
2017-04-20 23:52:22,770 DEBUG env RFSPY_RTSCTS=0
2017-04-20 23:52:22,770 DEBUG excuting ['oref0-subg-ww-radio-parameters', '/dev/ttyACM0']
+ echo

+ echo The CC111x is located at /dev/ttyACM0
The CC111x is located at /dev/ttyACM0
+ cd /home/pi/src/subg_rfspy/tools
+ case "$2" in
+ ./change_setting.py /dev/ttyACM0 0x06 0x00
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0C 0x59
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0D 0x66
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0E 0x33
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0F 0x62
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x10 0x1A
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x11 0x13
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x09 0x24
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0A 0x2E
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0B 0x38
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ exit 0
2017-04-20 23:52:28,856 DEBUG script exited with 0
2017-04-20 23:52:28,856 DEBUG sleeping for 0.5 seconds
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"868.630", 5, -63  Listening: ........No pump comms detected from other rigs

is that the log part you mean?

here with error:
Starting pump-loop at Fri Apr 21 00:30:05 CEST 2017:
Traceback (most recent call last):
  File "/usr/local/bin/mmeowlink-any-pump-comms.py", line 15, in <module>
    app.run(None)
  File "/usr/local/lib/python2.7/dist-packages/decocare/helpers/cli.py", line 113, in run
    self.prelude(args)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/cli/any_pump_comms_app.py", line 28, in prelude
    super(AnyPumpCommsApp, self).prelude(args)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/cli/base_mmeowlink_app.py", line 26, in prelude
    self.link = link = LinkBuilder().build(args.radio_type, port)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/link_builder.py", line 16, in build
    return SubgRfspyLink(port)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/subg_rfspy_link.py", line 55, in __init__
    self.open()
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/serial_interface.py", line 32, in open
    self.check_setup()
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/subg_rfspy_link.py", line 72, in check_setup
    self.serial_rf_spy.sync()
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/serial_rf_spy.py", line 121, in sync
    raise CommsException("Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?")
mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
2017-04-21 00:30:08,010 DEBUG Import spi_serial
2017-04-21 00:30:08,013 DEBUG spi_serial not installed. Assuming not using spidev
2017-04-21 00:30:08,013 DEBUG Import oref0_subg_ww_radio_parameters
2017-04-21 00:30:08,054 DEBUG Parsing ./pump.ini
2017-04-21 00:30:08,058 DEBUG Serial device (port) for pump is: /dev/ttyACM0
2017-04-21 00:30:08,059 DEBUG env RFSPY_RTSCTS=0
2017-04-21 00:30:08,060 DEBUG excuting ['oref0-subg-ww-radio-parameters', '/dev/ttyACM0']
+ echo

+ echo The CC111x is located at /dev/ttyACM0
The CC111x is located at /dev/ttyACM0
+ cd /home/pi/src/subg_rfspy/tools
+ case "$2" in
+ ./change_setting.py /dev/ttyACM0 0x06 0x00
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0C 0x59
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0D 0x66
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0E 0x33
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0F 0x62
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x10 0x1A
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x11 0x13
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x09 0x24
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0A 0x2E
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ ./change_setting.py /dev/ttyACM0 0x0B 0x38
RileyLink OK
Version: subg_rfspy 0.9
SUCCESS
+ sleep 0.5
+ exit 0
2017-04-21 00:30:14,209 DEBUG script exited with 0
2017-04-21 00:30:14,209 DEBUG sleeping for 0.5 seconds
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"868.558", 5, -77  Listening: ...........

Fixed the merge conflict.  Is this ready to merge to dev and be tested by more folks?

yes, it's ready to go to dev. i have been running for more than a week on this branch


How to disable double click event on pargraph

Hi JiHong, like the title, i want to disable double click event to prevent some actions unexpected. How can i do that? Thanks

@crying2812 Where do you want to prevent double click?
There are currently no settings for double click.
Register the event yourself like this:
const instance = suneditor.create(..);

instance.onload = (core) => {
  const wysiwygArea = core.options.iframe ? core._ww : core.context.element.wysiwyg;
  const toolbar = core.context.element.toolbar;
  const modal = core.context.dialog.modalArea;

  wysiwygArea.addEventListener('dblclick', (event) => {
    //
  });
}

Thanks for quick response, i want to prevent double click on each paragaph, i will try your way first :D

I tried your way but sadly it's not working, is there other way to bind custom event listener ?

@crying2812 It may not be possible if you are trying to block the range selection by double click.
It is not blocked by event.preventDefault().


feat: create publish workflow

Work in progress - I'll let you know when this is good for review

Note for future ref: discussion on #16.
@danjohnson95 @ianlandsman what's left on this? I'd love to get the notifier actually running on my macbook 😉

I'd also love to get this running on my MacBook, but we can't publish in a CI environment until https://github.com/NativePHP/electron/pull/74#issuecomment-1792973094 is approved and merged 😞

@danjohnson95 good news! It's merged now 😄

Excellent! I've bumped the composer file to point to the specific commit because it hasn't been tagged yet.
This should be everything required to build in CI for macOS, upload to GitHub Releases, and automatically roll out the update to existing users.
Once this is merged in, I'll keep an eye on the pipeline to see if it works as intended and I may need to raise a separate PR to fix any potential issues.

@ianlandsman looks like something you need to fix: https://github.com/UserScape/larajobs-desktop/actions/runs/7352162872/job/20016515689#step:8:167

Sorry for the delay, not totally clear what that error is but there was an agreement to agree to in the apple dev console so I did that.

@danjohnson95 any idea what's going wrong in the logs here: https://github.com/UserScape/larajobs-desktop/actions/runs/7352162872/job/20671888416#step:8:135?


Blazor "bind" has been broken in preview 6 daily builds since May 30

Describe the bug
Binding using the "bind" keyword has been broken in the preview 6 daily builds since May 30.  Using the @bind syntax works, but I can't find anything suggesting this should be the case
To Reproduce
Using current preview 6 daily (as below)
dotnet new blazorserverside
edit counter.razor as follows ...
@page "/counter"
<input type="text" @bind=A />

<input type="text" bind="@B" />

<input type="text" value="@C" />

Current value of A is @A

Current value of B is @B

Current value of C is @C

@code {
    string A="A";
    string B="B";
    string C="C";
}

dotnet run
navigate to counter page
change the values of the three textboxes
Expected behavior
strings A B and C all get updated when the bound textbox is updated
Actual behavior
Only A (the @bind syntax) works correctly
Additional context
dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.0.100-preview6-012135
Commit:    19761f8a5c
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.18362
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview6-012135\
Host (useful for support):
Version: 3.0.0-preview6-27730-01
Commit:  63abc77da6
.NET Core SDKs installed:
3.0.100-preview6-012135 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.0.0-preview6-19279-08 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.0.0-preview6-27729-07 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview6-27730-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview6-27730-01 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Hi @glent1 - this is part of the directive attributes work that's shipping in 3.0 preview 6 / VS 16.2-preview 2. You can read more about this here https://github.com/aspnet/AspNetCore/issues/6364
Thanks for reaching out, this was a good reminder to me to update the issue with more details.

Excellent - thanks for taking the time to reply.  I guess if I'd known that they were called "directives", I'd have had more luck searching for the change!

No worries, we made up the term to explain the new feature!


Check for Powershell files

Currently ansible-review will fail if we run the standard flake8 check on powershell files. As there is no standard set right now for how to handle PS scripts I am proposing we just have a blanket ignore for these files.
Open for suggestions on improvements but this is what I have come up with.

Hi Jordan,
This is how I would do it.
Add a PythonCode and a PowershellCode subclass of Code.
In classify, if it ends with  .py, make it PythonCode, if it ends with .ps1, make it PowershellCode
Then examples/standards.py will need code_passes_flake8 to change types: ['code'] to types: ['pythoncode'].
This will make people's existing standards break unless I also change the review method to run checks against all subclasses (so types['code'] will run PythonCode and PowershellCode checks) - but if you update this PR accordingly, I will make the accommodating backward compatibiliity fix.
The benefit of doing it this way is that you (or others) can add PS checking functionality if you later so desire.

I've made those changes you have suggested, let me know if there is anything else you need from me or if I did it incorrectly.

👍


Implement test list for BuildServerBuildSystem

Currently, we don’t support syntactic test discovery from BuildServerBuildSystem because BuildServerBuildSystem does not implement testFiles and addTestFilesDidChangeCallback. We would probably need to design a BSP request/notification to implement these methods.
rdar://126493405

Duplicate of https://github.com/swiftlang/sourcekit-lsp/issues/1173


[DO NOT MERGE] Remove root detailed guide paths

Detailed guides are now available under guidance/ and moving
away from root paths.
This is part of our multi-step plan to achieve this.

This should be changed to be a rake task in the same way as https://github.com/alphagov/panopticon/pull/282.

Count of both this rake task and the reslug rake task are off. Can't figure out why.

I've pushed a fix, it's due to "undocumented behaviour" (I'm being kind) in Mongoid.


[WIP] Feature: x-condition

DO NOT MERGE. Work in progress.
I have a service that, among other things, responds with links (defined as separate properties of an object) dependent upon what the caller is allowed to do.
I would love to be able to populate my links and take advantage of the way this package can build up an object with x-variable, x-template, and my default values. But, since I often don't need all of the links, I find myself either:

Populating all the links and then manually deleting the ones I don't need
Manually creating the links

I would love another property like x-variable or x-template. I've named it x-condition. The idea is that I could give it a string in my OpenAPI document, the same way we do with x-variable. Then when I call populate, set that corresponding property in params to true or false to determine if the populate function will build it out.
The pull request right now consists of potential tests for the new feature.

Upon further thought, x-condition would be even more useful if I could set the corresponding property to something truthy instead of just explicitly true.
My use case for this is populating schemas like:
{
    "description": "Date-time of cache (If not provided, data is from live source)",
    "type": "object",
    "x-condition": "date_time_cached",
    "required": [
        "data_time"
    ],
    "properties": {
        "date_time": {
            "type": "string",
            "format": "date-time",
            "x-variable": "date_time_cached"
        }
    },
    "example": {
        "date_time": {
            "date_time_cached": "2017-03-30T08:46:16.000Z"
        }
    }
}

Then, I could set both x-condition and x-variable to the same property, and fill in an entire (potentially complex) object if the property is truthy.
If I thought I might want to populate this schema using a falsy x-variable, I could still do it by using a different property name for x-condition.

I've thought about this for about a week now. It's a delicate balance to decide what functionality should be coded vs configured. I generally prefer code over configuration due to it's flexibility, but most code also requires some level of configuration. For example, a function takes parameters. The input parameters are that function's configuration.
So, to keep it short, I'm leaning toward adding this functionality in.

Okay. Cool.
I don't have any strong opinions about it.
On one hand, it means an extra check for every recursive iteration of populate. On the other hand, that pattern I described of creating and then deleting links seems pretty popular. So, I thought the idea was worth pitching.
It's definitely not a blocking issue, just an ease-of-use thing.

This functionality was worked into the master branch.