Convenience methods

Should the Signal API include any convenience methods? Possibilities:

Signal.isSignal -- brand check
Signal.State.prototype.update -- read/run/write
Signal.State.prototype.toReadonly -- make a computed signal out of a state signal, to drop the capability to write to it
A version of Signal.Effect that schedules itself (badly)

Would any other convenience methods be useful? The current API omits all of these on purpose, with the goal of being minimal.

peek has been there since early KO and is a simple, more efficient untrack when reading a single Signal/Computed.
signal.peek() and computed.peek() behave like .get() does when called outside a computing context, i.e. they return the current value without tracking the read.

I think wee need untrack() because there are scenarios when an entire block of operations needs to be performed and where the code doesn't have direct access to the signals. But, it might be that peek could be added as an additional API.

I have a utility that deals in a single signal and needs to peek it. Having a Signal.subtle.peek(signal) function would be great for that.

@EisenbergEffect Yes, I wasn't suggesting that peek replaces untrack. A way to completely escape a computing context is required (see effectScope discussions in Vue for example).
But sometimes all you need is reading one signal and untrack(() => this.get()) is not great DX, nor very efficient compared to peek implementation.

@jods4 untrack is not about just one signal or computed, it's about running something potentially huge ... peek() as it is in Preact is for each single signal/computed and it's an explicit user intent to not track that particular change.
Accordingly, I wouldn't mix the two use-cases or needs, untrack is fine as it is and it can be used to abstract peek already, peek as State or Computed method might be welcome but it's a different use case than untrack: peek is atomic, untrack doesn't need you to change code around a signal so I hope we cna either have both or just have untrack and provide that abstraction like I did already so that users can explicitly peek single values or untrack callbacks with potentially dozen signals in it.

@WebReflection that's exactly what I said, not sure how you understood my previous messages.
I said untrack is required and cited an example why in the context of Vue.

the DX argument is hence weak as long as the desired result is achievable and untrack allows peek to exist, if a library author wants to provide that ability ... if we go in features-creep-land this API won't ever reach the Web, which would be unfortunate, as it's already awesome as it is and it has it all behind the scene.

Yes, anyone can build peek as untrack(() => signal.get()).
Doing so they create a closure and call a function that has to change the computing context using a stack, before calling that closure in a try/catch/finally block.
On the other hand, built-in peek on signal is basically peek() { return this.#value }.
I'm not sure that's a lot of feature creep, especially considering that most (all?) "signal" implementation for the past 10 years have exposed a peek in their core set of features.

checking internals of the polyfill, it could indeed just return the internal symbol value and avoid extra stacks. Apologies I've misread your previous comment, I've thought you preferred peek() over untrack(), my bad. Agreed having both would be nice.

Great conversation here! Thanks for the clarification @WebReflection and @jods4!
QQ: If we have peek, is there any use case for a poke as well, to set the value?

@EisenbergEffect I feel like that's a stretch too far ... or better, I don't understand the use case for it, it feels surprise prone to me as "a sneaky update nobody should notice" and that to me won't lead to better code ... .peek() is an explicit opt-out to subscription, .poke(value) as opt-out to reactivity in general feels odd (imho).
if we take previous art work around the topic, I am not sure which library exposes that to date but if they do, it's also easily an attack vector to me if these libraries land in undesired places and start poking around foreign code ... it's chaos easy to generate, while .peek() remains into the "observable field", if that makes sense.

agreed and on a second though, untrack is fine to exist and has tons of use cases already, .peek() is the "atomic untrack" within a state/computed and it's fine and has tons of use cases ... .poke(...) is dirty by design and doesn't even have its own untrack like counterpart ... I would discourage exploring that field as it can't produce anything good to me, not even libraries authors ... if it lands a .poke(...) it should land with those funny comments like "YOU_ARE_FIRED_IF_YOU_INVOKE_THIS" and while I am sure there is a single edge case that makes sense in the world about it (such as, update an object reference underneat with same shape but different reference for the GC) I think is disaster prone if exposed and, once exposed, of course libraries authors will use it then ... please let's drop this idea already 😅

untrack is fine to exist and has tons of use cases already

do we have a list of these? would be good for a "guidance" and "recommendations" section of the docs / proposal, because there are a lot of ways to shoot one's self in the foot with reactive systems.
May be of interest:

https://github.com/proposal-signals/proposal-signals/issues/74
https://github.com/proposal-signals/proposal-signals/issues/94

Thanks everyone! I was pretty sure poke was a bad idea and I couldn’t think of any use cases, but wanted to make sure I wasn’t missing something.

@NullVoxPopuli

do we have a list of these?

just the fact one can send errors or debug on Promise catch would be enough to me, as you never want to subscribe to those callbacks
fetch(remote.get()).catch(error => {
  untrack(() => {
    console.error(`Unable to fetch ${remote.get()}`, error);
  });
});

Sure thing for that specific use case .peek() would be even better but with callbacks around used to effect and compute having a way to introspect their values/invokes without subscribing is desirable.

I don't think callbacks like that are inherently subscribed too, and untrack wouldn't be needed 🤔 i am about to verify this tho in
https://github.com/NullVoxPopuli/signal-utils/pull/19

Yeah my feeling is that events/microtask queue items would have a null currentComputed by default, and just not be tracking until you go into a Computed.

my example was poorly presented ... I meant that whenever signals or computed are around and you want to:

serialize that value to send a JSON request to a REST API
react to (caught) errors that might be sync or not and store or send involved signals in there
introspect anything due debug flag enabled within the code, and maybe transpiled away in production
add A/B tests around features that should not compromise the user logic when enabled ...
stuff like this ...

I can do a quick search in Preact repo though as I am sure they had various reasons/requests/discussions aroud this topic, if that helps anyone (or users wanting to understand when untrack and peek() are desirable)
To my DOM examples based on signals, there are cases I need to retrieve a value in sync with the rest of the flow but without subscribing the whole thing to my introspection logic, so this is another use case ... libraries' authors will need, and want, a way to not subscribe for foreign data they don't understand where it comes from or how frequently it could update.

If you're fishing for peek / untrack use cases:
Very recently I wanted to capture the initial state of reactive objects, to be able to provide a "dirty" flag. This happened in a computed that "initialised" the transactional object from the currently bound object.
It's easy to understand that this computed should only be dependent on the bound object instance (if instance changes, a new transactional object is created).
Because this step read all reactive object properties to capture initial values, they became dependencies and a new transactional object would be created at each change, which is completely broken.
My solution: peek at reactive properties when capturing initial values, so that those reads are not reactive (it's intuitive as well: by definition initial values never change).
You can also dig into Vue effectScope RFC: https://github.com/vuejs/rfcs/pull/212
It's a broader API mainly targeted at ownership / lifetime outside of components, but one motivation for the design was to be able to escape the current computing context, see Detached Nested Scope.
Vue also exposes pauseTracking() and resumeTracking() as advanced apis, that serve an identical function as untrack().
I previously mentionned that Knockout has had peek since forever: https://knockoutjs.com/documentation/computed-dependency-tracking.html#controlling-dependencies-using-peek. The doc gives as an example a computed that makes an AJAX request based on a page number, while also keeping track of the selected item although the latter is not a depedency (no AJAX request if selected item changes).

Here is a userland implementation of peek (via localCopy without an effect):

https://github.com/NullVoxPopuli/signal-utils/blob/main/src/local-copy.ts#L5
Usage: https://github.com/NullVoxPopuli/signal-utils/blob/main/README.md#localcopy

@littledan We've had the request for peek() come up in several different conversations and there's a lot of precedent for it in existing libraries. Since one of our goals to performance/memory-efficiency, this seems like a reasonable thing to add to eliminate callback/closure usage in a number of common scenarios. What do you think about adding this to both State and Computed?

my 2c: explicit peek() is intentional zero side-effects by design so I hope we can make it part of the specs ... poke(value) as suggested elsewhere is undesired side-effects by design so it should likely never land in these specs.

I like the idea of adding toReadonly.
With regards to the proposal:

Signal.State.prototype.toReadonly() make a computed signal out of a state signal, to drop the capability to write to it

Implementing as a computed signal is one approach. But it involves creating an extra signal. A wrapper object that only exposes the get() method of the signal might be more efficient.  This is what Angular does. https://github.com/angular/angular/blob/17.3.12/packages/core/src/render3/reactivity/signal.ts#L83-L91 (Their interface is different... but note the readonly view is just a thin wrapper around the signal's getter.  It doesn't create a new signal)


Smart Cell text-to-image with stable diffusion anime model load exception

Environment

Elixir & Erlang/OTP versions (elixir --version):  1.15.7 erlang 26
Operating system:  Ubuntu 22.04
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc):  mix phx.server
Livebook version (use git rev-parse HEAD if running with mix):  v0.12.0-dev
Browsers that reproduce this bug (the more the merrier):  firefox 121.0
Include what is logged in the browser console:

** (ArgumentError) could not match the class name "SafetyChecker" to any of the supported models, please specify the :module and :architecture options
(bumblebee 0.4.2) lib/bumblebee.ex:369: Bumblebee.do_load_spec/4
(bumblebee 0.4.2) lib/bumblebee.ex:488: Bumblebee.load_model/2
#cell:vv7n7uo6lge4icil:22: (file)

Include what is logged to the server console:

Current behavior
Select stable diffusion (anime) model and hit evaluate and the exception above displayed after downloading a number of models from the internet.
Tried with stable diffusion model 1.4 and hit evaluate and it downloads the models and runs fine generating the test image.
Include detailed steps to reproduce error, errors and stacktraces if appropriate.
As above
Expected behavior
Expect a few ui segments to allow input of text but none displayed.  Default parameters used in the task section.

Please convert the smart cell to code and load the safety checker like this:
{:ok, safety_checker} =
  Bumblebee.load_model({:hf, repository_id, subdir: "safety_checker"},
    module: Bumblebee.Diffusion.StableDiffusion.SafetyChecker
  )

I opened a PR on the repo, because the config there is invalid. I must've been testing the model without safety checker in the past and this issue slipped through.


Linux nodeselector

Nodeselector for linux machines have been statically added to deployments objects when needed.

@paoloalba your commits are not signed, https://github.com/kedacore/keda/blob/master/CONTRIBUTING.md#i-didnt-sign-my-commit-now-what


the trait bound Cognito: Transform<<impl actix_service::ServiceFactory<ServiceRequest> as actix_service::ServiceFactory<ServiceRequest>>::Service, ServiceRequest> is not satisfied

Not familiar enough with relevant traits, getting this error when trying to integrate actix-web-middleware-cognito:
error[E0277]: the trait bound `Cognito: Transform<<impl actix_service::ServiceFactory<ServiceRequest> as actix_service::ServiceFactory<ServiceRequest>>::Service, ServiceRequest>` is not satisfied
   --> src/server/mod.rs:902:19
    |
902 |             .wrap(cognito)
    |                   ^^^^^^^ the trait `Transform<<impl actix_service::ServiceFactory<ServiceRequest> as actix_service::ServiceFactory<ServiceRequest>>::Service, ServiceRequest>` is not implemented for `Cognito`

error: aborting due to previous error

actix-web: v4.0.0-beta.5

This is because you're using the actix-web beta. They introduced breaking changes. If I have time I'll prepare a beta release too but I can promise you when that will be. :(

@k-bx I've just published a new version supporting actix-web 4.0.0-beta.5: https://crates.io/crates/actix-web-middleware-cognito/0.4.0-beta.5

Thank you!

If you ever need to use beta.6,  you can get it here


Proxy Consideration URL's

The outbound URL's for the cloud witness are not listed.  I think its pretty obvious that outbound access to storage is necessary, but are there other URL's that should be whitelisted in a proxy?
https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness#proxy-considerations-with-cloud-witness

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

ID: 7e6da99e-a148-b5ea-224d-8a4c48604945
Version Independent ID: a6a90a1f-870c-3501-ce6e-fbf52f802dfb
Content: Deploy a cloud witness for a Failover Cluster
Content Source: WindowsServerDocs/failover-clustering/deploy-cloud-witness.md
Product: windows-server
Technology: storage-failover-clustering
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Make a hook for the toArray function

Make a hook for the toArray function in mappable so we could use the extension in rest services
return response()->json($model);

Also made a change to composer requirement to not include laravel 5.2

I’ve tested and it resolved 2 problems i had for json output :+1:

mapped dates were not formatted (serializeDate)
I was forced to duplicate visible/appends
Hope, this feature will be accepted

@rickatultraware please revert changes to the composer.json and add some tests in order to merge it.


bin/registry garbage-collect /etc/docker/registry/config.yml

failed to garbage collect: failed to mark: invalid checksum digest format

@zhaochenglan can you provide details on your configuration, storage backend, registry version, and copy your registry logs?
Thanks.


Inject: Encode labels as json similar to annotations

Fixes #9605

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
If they are not already assigned, you can assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS
pilot/OWNERS
pkg/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
e71efa21d25b2cec63f14491031876889a53f7a5
link
/test e2e-mixer-no_auth

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

/test e2e-mixer-no_auth

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
e71efa21d25b2cec63f14491031876889a53f7a5
link
/test e2e-mixer-no_auth

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

/test e2e-mixer-no_auth

@mandarjog see https://github.com/istio/istio/issues/9635 - all PRs are blocked until this test is fixed.

@mandarjog as part of this PR, can you use the change from https://github.com/istio/istio/pull/9637 (which I hope will fix this issue)? that would save a cherry-pick.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
If they are not already assigned, you can assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS
pilot/OWNERS
pkg/OWNERS
samples/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

If pod labels change

In a subsequent PR, we can update metadata / restart envoy if bootstrap changes
Pilot can access all this metadata based on endpoint registry information it already has.
Label change on deployment.spec will redeploy the pod.

@mandarjog: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
3a0d1b5181d812ac7c71d4dbbf3d4dba7baa2ddd
link
/test e2e-mixer-no_auth

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [costinm]
pilot/OWNERS [costinm]
pkg/OWNERS [costinm]
samples/OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

env vars that are explicitly passed in as ISTIO_META_xx will continue to work. Since they are passed in explicitly the user is in control, so did not need to modify bootstrap.go.

Thanks for fixing @mandarjog


Installer Changes for SLS App

Requirements

Install Plugin - Pipeline Utility Steps
Updated script approvals

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


Add a software rasterizer

I don't have a strong justification for this but it would be at least useful to compare and perhaps use at small text sizes.
I also wouldn't miss using CoreGraphics for rasterization. See https://bugzilla.mozilla.org/show_bug.cgi?id=1471892

Having a software rasterizer would also help us avoid double glyph caching that comes from using CoreGraphics.

The way I think this would probably be done is to replace add_fill with a routine that simply draws the fill on CPU, probably using delta coverage like font-rs does followed by a sum pass. Then we can upload prerendered alpha tiles instead of commands to the GPU and proceed as usual.
Not sure whether using trait object or using generics would be best for this.


Implement conf-dict as Conf-class

Allows to perform deprecation behavior on config variables
Implemented deprecation behavior for #552
Remove unused config variables
Fixed some deprecation warnings to become more clear (tested locally)

I'm assuming these defaults are unused, and propose a removal of them:

"viur.capabilities" is used in renderer to provide some "additional" undocumented information about modules. Seems to be a relict of ViUR v1, never seen this in any recent project.
"viur.db.caching" is not found in either viur-core or viur-datastore anymore
The variable apiVersion was used NOWHERE.

Hello @ArneGudermann, I've renamed the "item" variables into "key", as this is also the default in the Python reference. Nevertheless, I want to keep the warning when setting config variables to values which are already configured, as a little help to keep project settings clean, as described above in my comment.

Ok I'm fine with it can you please resolve the confilcts. Then we can merged it from my site

Ok I'm fine with it can you please resolve the confilcts. Then we can merged it from my site

Never mind you already did it.


Add texture to ARSurface shader

Hello,
I am using your shader for shadows, however I would like to show a visualization of the tracked ground like the default one in ARCore. So my question is how would I add texture to the shader (with transparency)?

Hi,
For that to work you need to do two things: generate uv coordinates for the generated mesh AND modify the shader to make it sample from a texture.
To learn more about this I'd suggest reading up on uv coordinates:
https://docs.unity3d.com/ScriptReference/Mesh-uv.html
As for getting the shader to sample from a texture, I'd recommend reading up on how Unity's shaders and materials work:
https://docs.unity3d.com/Manual/Shaders.html
Best of luck


AttributeError: module

I am unable to call evaluate_model_for_folders, getting this error continuously-
AttributeError: module 'pyAudioAnalysis.audioTrainTest' has no attribute 'evaluate_model_for_folders'
I don't know why this is occurring, please help.

@tyiannak Facing the same error.


[Chore]: Configure the e2e tests to run via git webhook

The github pr concourse resource is a bit lousy at detecting new PRs and especially when there is a large number of PRs it is quite likely that it will miss some and its corresponding check will remain in the Pending state preventing us from merging the PR. The workaround is to rebase the pr or do an empty force push in order to re-trigger all checks.
We are hoping that if we configure the tests to run with a git webhook this problem will go away

Looks like a github webhook will need a server to receive the payload when the desired event occurred. Concourse cannot do this and it is not a planned feature as explained in this comment. We could write a small app to process the event and trigger the desired build, but we are not convinced it is worth the investment and are concerned that such an app will have to be exposed to the internet and might become a potential attack point. (Alothough there is a way to validate shas sent from Github and detect tampering).
Putting down for now.

I decided to give this chore one more try today, because I found this tool: https://github.com/adnanh/webhook
It is a generic server to handle github webhooks. We could deploy that as a cf app on one of our clusters and it would be available in the internet for Github to POST to. It looks like it handles the security aspect of comparing sha fingerprints. It is even available as a service on www.hookdoo.com.
However the big problem of the push approach as opposed to the concourse default pull approach is that even if we are able to filter the event down to "the label allow-e2es is set on a PR" there is still no way to make concourse run against a sha passed by our webhook server. There is no way to tell concourse "run this job against that commit that I am sending you in the request". Concourse works more like "I will run that job against the latest commit that I know about"
There is also the possibility of setting a webhook_token on the git resource which will allow GitHub to initiate the resource check (instead of the default periodic pull behaviour of concourse), but in this case there is virtually no way to pass parameters down. This means that our best shot is to trigger the run-pr-e2es job every time anyone adds or removes or modifies a label on a PR, issue, etc. And again the job will run against the latest commit in its cache, rather that against the commit associated with the event that triggered it. Needless to say that this is going to generate a lot of load for our concourse instance.
TL;DR It seems to be close to impossible to trigger the PR e2e tests actively from the GitHub side. I am closing that chore.

@kieron-dev feel free to reopen if you have some idea we did not explore.

One possibility might actually be that we deploy webhook as an app with an appropriate config that only reacts to newly added labels with the name allow-e2e and run the following script:
fly -t example pin-resource --resource main/korifi-pr --version ref:bceaf
trap EXIT "fly -t example unpin-resource --resource main/korifi-pr"
fly trigger-job --job main/run-e2es-pr

This would cause the correct PR ref to be used, but will also mean that we will have to process github events serially. In any event I think this is too ugly to pursue and we should maybe re-raise our issue with certain PRs getting dropped with the concourse team


Fix identity issuance and recovery errors.

Purpose
Unblock identity issuance and recovery.
Changes

Change accountInfo checks to handle error thrown when account does not exist.
Fixed some types.

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[ ] (If necessary) I have updated the CHANGELOG.

There is still issues with the identity provider, but it seems that it is a identity-provider-service/wallet-proxy issue. :thinking:
(Maybe the fix is to migrate to the v1 issuance)

There is still issues with the identity provider, but it seems that it is a identity-provider-service/wallet-proxy issue. 🤔 (Maybe the fix is to migrate to the v1 issuance)

It is not really in scope to migrate the issuance as well. The old issuance should still work.

There is still issues with the identity provider, but it seems that it is a identity-provider-service/wallet-proxy issue. 🤔 (Maybe the fix is to migrate to the v1 issuance)

It is not really in scope to migrate the issuance as well. The old issuance should still work.

Yes, it was an issue with the identity-provider-service. The fix are on stagenet.


Create Go and JS Supported WASM Target

could have a wasm crate in the workspace that generates a .wasm file, which could get bundled into releases as an artifact


Add coterminal angles article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

This pull request adds a fundamental description of coterminal angles.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Unable to open PE files

Hi,
I am unable to load pe files. The reason is that pe.sections[section_idx].get_data()  always returns null. But after going through pefile library, I fixed the problem by givng the virtualaddress as the parameter for get_data().
This is the fix:
self._section_text = pe.sections[section_idx].get_data(pe.sections[section_idx].VirtualAddress)
This hack works fine for me now . I don't know whether this is correct?
Thanks.
Regards,
Maggie

Hi,
I try it with several PE files an I couldn't reproduce your problem. Also, I check what was
load


Elasticuploadapp action update as per issue 624

Checklist

[ ] tests added
[ ] commits conform to the Commit message format
[ ] documentation updated

Squash commit message
Updated elasticuploadapp action API with new fallbackName parameter in /api/v1/apps/import?fileId=<fileid> to reflect the current statue in QCS.

Testing failed on having space in the filename.
Gopherciser: /api/v1/apps/import?fileId=5f171109c3f13d000127eab7&fallbackName=BDI Build Pipeline Performance Analyzer.qvf
Browser:  /api/v1/apps/import?fileId=5f17113fd0add20001ff6851&fallbackName=BDI%20Build%20Pipeline%20Performance%20Analyzer.qvf
Gopherciser leads to Failed to upload app payload: 502 <<html>\n<head><title>502 Bad Gateway</title>
Same with Kanji character:
Gopherciser:  /api/v1/apps/import?fileId=5f17125bbf63590001e436eb&fallbackName=PT1MSSD大.qvf
Browser: /api/v1/apps/import?fileId=5f171294d0add20001ff68c0&fallbackName=PT1MSSD%E5%A4%A7.qvf
Same 502 error

Tested both using a space as well as Kanji character in the URL, works now


[FLINK-29952][table-api]Append the detail of the exception when drop tamporary table.

Append the detail of the exception when drop tamporary table.
Signed-off-by: houhang<EMAIL_ADDRESS>
What is the purpose of the change
Make the exception more clear when failed to drop a temporary table in sql-client.
Brief change log

Append a reason for the failure about dropping a temporary to current ValidationException.

Verifying this change
This change added tests and can be verified as follows:

Project can build successfully.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@fsk119 Hi! This is my first time to deal with a Flink PR, I don't know whether I missed any procedure. Please give me a little tip when you get free time -.-


Fix issue getting port exposed by services

Before this fix, we were always erroring if there was more than one service.

Going to merge this since I need it for another change in the containerd-shim.


[6.x] Prevent error on key:generate command

Prevent fatal error on key:generate command and show error messsage "You must create .env file before set the application key".

The current code is fine, if not better.

@tobiasthaden that method annotated as "@return void", not string.

Historically, Laravel has treated void as "don't use the return value of this method", rather than the more strict approach of "this method never returns anything", which explains why there is code in the core that returns within methods marked as having void return type.

There is already a return on line 39. So I think string|null is fine.

@tobiasthaden +

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


[Java] Unable to read S3 files using Arrow Dataset Java API

Describe the usage question you have. Please include as many useful details as  possible.
Even though all aws credentials are set, getting below error while trying to read s3 files using Arrow Dataset Java API.
Please guide which are AWS properties needs to be set to work correctly.
java.lang.RuntimeException: When resolving region for bucket : AWS Error NETWORK_CONNECTION during HeadBucket operation: Encountered network error when sending http request
	at org.apache.arrow.dataset.file.JniWrapper.makeFileSystemDatasetFactory(Native Method)
	at org.apache.arrow.dataset.file.FileSystemDatasetFactory.createNative(FileSystemDatasetFactory.java:35)
	at org.apache.arrow.dataset.file.FileSystemDatasetFactory.<init>(FileSystemDatasetFactory.java:31)
	at com.arrow.dataset.ParquetFileToArrowReader.readS3Parquet(ParquetFileToArrowReader.java:114)
	at com.arrow.dataset.ParquetFileToArrowReader.main(ParquetFileToArrowReader.java:36)

Component(s)
Java

Could you share your code?
Or the implementation of the process https://github.com/apache/arrow/blob/apache-arrow-11.0.0/cpp/src/arrow/filesystem/s3fs.cc#L546-L577 may help you.

I am using the standard code in the Arrow java cookbook. Updated ~/.aws/credentials file is available in user directory.
Even tried setting the environment variables AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN as per the link https://cran.r-project.org/web/packages/arrow/vignettes/fs.html. But still getting same error. Any help on this highly appreciated.
String uri = "s3://bucket_name/sub-directory";
ScanOptions options = new ScanOptions( 32768);
try (
BufferAllocator allocator = new RootAllocator();
DatasetFactory datasetFactory = new FileSystemDatasetFactory(allocator, NativeMemoryPool.getDefault(), FileFormat.PARQUET, uri);
Dataset dataset = datasetFactory.finish();
Scanner scanner = dataset.newScan(options)
) {
System.out.println(StreamSupport.stream(scanner.scan().spliterator(), false).count());
} catch (Exception e) {
e.printStackTrace();
}

Does String uri = "s3://voltrondata-labs-datasets/nyc-taxi/year=2019/month=6/part-0.parquet"; work?
Are you running your program on EC2?
Does String uri = "s3://${access_key}:${secret_key}@${bucket_name}/${path}"; work?


Add tail option to log task

This pull request add an options to log task to tail log new line. Useful to follow deploy process.
Second commit add an option to specify number of line to show, this option replace current API without break it. I have added this to have consistents options.

Nice! Merged


Unexpected token '='

Hey,
Currently having an issue with favicons-webpack-plugin via  the favicons package.
Here's my error;
SyntaxError: Unexpected token =
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\node_modules\favicons\helpers-es5.js:18:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\node_modules\favicons\es5.js:11:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\lib\favicons.js:3:16)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at DependenciesBlock.loadPitch (...\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:193:17)
    at DependenciesBlock.doBuild (...\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:241:4)

However, I can't see why it's happening, as helpers-es5.js:18 is this line
var path = require('path'),
    fs = require('fs'),
    _ = require('underscore'),
    color = require('tinycolor2'),
    cheerio = require('cheerio'),
    colors = require('colors'),
    jsonxml = require('jsontoxml'),
    sizeOf = require('image-size'),
    async = require('async'),
    mkdirp = require('mkdirp'),
    Jimp = require('jimp'),
    svg2png = require('svg2png'),
    File = require('vinyl'),
    Reflect = require('harmony-reflect'),
    NRC = require('node-rest-client').Client,
    PLATFORM_OPTIONS = require('./config/platform-options.json');

I can't build on Windows, or Heroku, but OS X seems to build fine.

Hey @alexdrans, what version of Node are you running?

v4.5.0

If you're running the ES6 version (likely) then you should probably be jumping on Node 5 or 6+

Thanks for the rapid reply. Let me check whether v6.5.0 fixes it!

Yep, all working! 🎈 Thanks @haydenbleasel. Awesome module also.

@alexdrans No worries homie 👍

@haydenbleasel this is still an issue in projects that use e.g. favicons-webpack-plugin and cannot upgrade to Node 6.x. Don't you have any plans to support older versions of Node than 6?

@crisu83 If you read our docs, we compile an ES5 version of Favicons. All you need to change in Webpack Favicons is require('favicons') to require('favicons/es5').
However, Node 0.10 is only maintained until October and 0.12 until December. I suggest upgrading to v4 or v6.

@haydenbeasel I did read your docs, but I encounted this issue on Node 4.x.

I'm using favicons in my Ember.js app via the ember-cli-favicon addon and am experiencing the same issue. Everything worked fine with Node v4.3.1 until my last commit from 2 days ago.
That commit didn't change anything regarding versions, it only contained some simple modifications in an ember template and some extra rules in a less stylesheet.
Switching to Node 6 is currently not an option. I especially stick with Node 4 as that is the current, supported LTS version of Node.
Moreover, everything worked fine with this setup until my last commit, so I think it's not directly related to the version of Node.
Note: I had similar issues in the past, where the cause was apparently an es5 compilation issue: https://github.com/haydenbleasel/favicons/issues/147

FYI: ember-cli-favicons relies on broccoli-favicons, which in turn relies on the favicons library.
As you can see in the code, the broccoli-favicons library already uses the es5 version: https://github.com/davewasmer/broccoli-favicon/blob/master/index.js

Fixed by pull request https://github.com/haydenbleasel/favicons/pull/154


allCountries issue

The allCountries used to store all Country_data, but now got replaced by just the array of country names. In a few files allCountries is still being used, probably breaking code. Those items have to be replaced, preferably by smart portions of code that only load the required data, and not the entire Country_data. The allCountries is created in store-countries.js in the getters. It's then passed into mixin-general.js, making it available to all files who import mixin-general.

Some of the allCountries errors have been fixed. In the mixin-general.js there arre now 2 computed properties that can find the location based on the countrycode or countrykey. See below.
countryKeys(){ 	return Object.keys(this.countryCodes_rev) }, countryCodes(){ 	return Object.values(this.countryCodes_rev) },
Some other errors were quite difficult to transform, so I've been replacing them with a new property called allCountryData, which uses the same method but is a slight improvement ,see https://github.com/cycleplanet/cycle-planet/pull/14/commits/c9256216e1cf5d9074b06365463a95bedefab318. It would be good to have allCountryData replaced as well, as we now have to load all Country_Data still.


Perf: Make one request to npm per package name

Right now, each package from each package.json gets a request to npm to get it's metadata. This can be improved to collect package names first and then iterate over them to only do one request to npm per package regardless how many times it appears.

done, v1.0.2


Resample needs splitting and target

Module nkululeko.resample should need file only to resample, but currently it needs splitting strategy and target. Hence, the ideal minimum INI file would be the following
[DATA]
databases = ['train']
train = ./data/enterface/enterface_avi.csv
train.type = csv
train.absolute_path = False
[RESAMPLE]
sample_selection = all

Without the need other sections (EXP, MODEL, FEATS, etc.).
Btw, it will also be helpful to add an option to backup original data to the RESAMPLE section (e.g., by providing option backup_original = True) to compressed file (via nkululeko.export ?).

totally agree there should be a way to resample but keep the originals.
and i think this should be default

Module nkululeko.resample should need file only to resample, but currently it needs splitting strategy and target. Hence, the ideal minimum INI file would be the following
[DATA]
databases = ['train']
train = ./data/enterface/enterface_avi.csv
train.type = csv
train.absolute_path = False
[RESAMPLE]
sample_selection = all

Without the need other sections (EXP, MODEL, FEATS, etc.).
Module nkululeko.resample should need file only to resample, but currently it needs splitting strategy and target. Hence, the ideal minimum INI file would be the following

Actually i think that is already the case.
You don't even need that, you can simply call the resample module on some config and it should resample all in train and test split to 16 kHz. just note it's NOT necessarily the whole database, but only the train and test splits

I tested the newest main branch, it still gives me error when I don't give it [EXP] and target.
In case of missing [EXP]
Traceback (most recent call last):
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/bagus/github/nkululeko/nkululeko/resample.py", line 63, in <module>
    main(cwd) # use this if you want to state the config file path on command line
  File "/home/bagus/github/nkululeko/nkululeko/resample.py", line 31, in main
    expr = Experiment(config)
  File "/home/bagus/github/nkululeko/nkululeko/experiment.py", line 38, in __init__
    self.name = glob_conf.config["EXP"]["name"]
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/configparser.py", line 963, in __getitem__
    raise KeyError(key)
KeyError: 'EXP'

In case of missing target
(nkululeko) bagus@pc-omen:nkululeko$ python3 -m nkululeko.resample --config data/enterface/exp_resample2.ini
DEBUG resample: running results/exp_enterface_aud from config data/enterface/exp_resample2.ini, nkululeko version 0.65.5
Traceback (most recent call last):
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/bagus/github/nkululeko/nkululeko/resample.py", line 63, in <module>
    main(cwd) # use this if you want to state the config file path on command line
  File "/home/bagus/github/nkululeko/nkululeko/resample.py", line 40, in main
    expr.load_datasets()
  File "/home/bagus/github/nkululeko/nkululeko/experiment.py", line 69, in load_datasets
    data = Dataset_CSV(d)
  File "/home/bagus/github/nkululeko/nkululeko/data/dataset.py", line 31, in __init__
    self.target = glob_conf.config["DATA"]["target"]
  File "/home/bagus/miniconda3/envs/nkululeko/lib/python3.9/configparser.py", line 1257, in __getitem__
    raise KeyError(key)
KeyError: 'target'

Btw, I made a PR #74 to force resample to save as WAV file (in case the original files are not in wav, it won't be overwritten) and handle file names with spaces.

ah: i see. yes, until now every experiment needs a EXP section and a target key.
i think at least the experiment name (in the EXP section) is not optional, as we need some root directory for all processing

Thanks!
One more, Resample should also offer to convert stereo to mono (maybe by default, since the default is already back up the original data). The stereo file will make errors since the size of the acoustic feature will be twice as other (eg, in speaker embedding).
Currently, I convert mono to stereo on the feature extraction stage (after resample).

yes, makes sense.
I think the RESAMPLE module should simply get a flag
check_channels = True|False
and depending on this, convert to Mono if necessary.
I could do this later


False-positive error on variables defined in indirectly imported files

In my project, SASS files are @imported into a single styles.scss file. The file structure is like this:
/scss
|-styles/
  |-layout.scss
  |-welcome.scss
|-style.scss
|-variables.scss

style.scss file content:
# style.scss
@import "variables.scss";
@import "styles/layout.scss";
@import "styles/welcome.scss";

So all variables are declared in the variables.scss file and are used in other styles/*.scss files. Eg:
# variables.scss
$main-color: blue;

Those other files, in accordance, don't import the variables.scss file as this is already done in the main style.scss file. When I try to use any variable Syntastic reports an error 'Undefined variable', although the files compiles smoothly into a single css file. Eg:
# styles/layout.scss
body {
  color: $main-color; # <---- An error here 'Undefined variable'
}

Is it possible to avoid this error by other means than importing the variables.scss file into each styles/* file?
VIM Version: 7.4 (2013 Aug 10, compiled Nov 18 2013 23:18:36)
MacOS X (unix) version
SyntasticInfo output:
Syntastic: active mode enabled
Syntastic info for filetype: scss
Available checker(s): sass
Currently enabled checker(s): sass

what was the solution to this? Im getting same issue

@erichonkanen The solution is to do what I described above: see how syntastic calls sass, then set g:syntastic_scss_sass_args so that sass gets to see all your imports.  There is no "find my imports" switch in syntastic.

@lcd047 when I type ":g:syntastic_debug" I get an error, how do I type that into the console?

@erichonkanen :let g:syntastic_debug = 1

@lcd047 ok I did that and then saved the file and I see some stuff for a split second then it just shows
syntastic: 1961.381807: getLocList: checker scss/sass run in 0.258697s```

what do I do from here? I tried `let g:syntastic_scss_sass_args` but it says `E121: Undefined variable: g:syntastic_scss_sass_args`

thanks!

@erichonkanen Please read :h syntastic-debug.

@lcd047 ok here is the output
= ''
syntastic: 3207.520786: UpdateErrors (auto): default checkers
syntastic: 3207.521009: CacheErrors: default checkers
syntastic: 3207.521517: g:syntastic_aggregate_errors = 0
syntastic: 3207.521682: getcwd() = '/Users/eric/Projects/toast/overlord/build/client-web'
syntastic: 3207.521973: CacheErrors: Invoking checker: scss/sass
syntastic: 3207.522435: SyntasticMake: called with options: {'postprocess': ['compressWhitespace'], 'errorformat': '%E%\m%\%%(Syntax %\)%\?%trror: %m,%+C              %.%#,%C        on line %l of %f\, %.%
#,%C        on line %l of %f,%-G %\+from line %.%#,%-G %\+Use --trace for backtrace.,%W%>DEPRECATION WARNING on line %l of %f:,%+C%>  %.%#,%W%>WARNING: on line %l of %f:,%+C%>  %.%#,%W%>WARNING on line %l
 of %f: %m,%+C%>  %.%#,%W%>WARNING on line %l of %f:,%Z%m,%W%>WARNING: %m,%C         on line %l of %f\, %.%#,%C         on line %l of %f,%-G %\+from line %.%#,Syntax %trror on line %l: %m,%-G%.%#', 'makep
rg': 'sass --cache-location /var/folders/9r/gp7xyl_j0l3flcwp78j7mjcr0000gn/T//vim-syntastic-27113-lsrpsYi4 --compass --check app/styles/components/split-panel.scss'}
syntastic: 3207.794084: system: command run in 0.271330s
syntastic: 3207.796936: getLocList: checker scss/sass returned 65
syntastic: 3207.797127: getLocList: checker scss/sass run in 0.275071s```

@erichonkanen Now read my first post above.

@lcd047 sorry Im so newb, I see where it is calling sass --cache-location /var/folders/9r/gp7xyl_j0l3flcwp78j7mjcr0000gn/T//vim-syntastic-27113-lsrpsYi4 --compass --check app/styles/components/split-panel.scss'
but how do I pass in another arg? is that what you're suggesting?

@erichonkanen Like I said: you can add arguments to g:syntastic_scss_sass_args:
let g:syntastic_scss_sass_args = '--some --args'

You probably want to add this to your vimrc.

I see, so I need to basically add an import arg to import the root sass file?


[KYUUBI #5869][1.8] Add volatile to variables in KyuubiSessionImpl that may be operated by multiple threads

:mag: Description
Issue References 🔗
minor fix
Describe Your Solution 🔧
Add volatile to variables that may be operated by multiple threads.
Types of changes :bookmark:

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

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklists
📝 Author Self Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[x] Pull request title is okay.
[x] No license issues.
[x] Milestone correctly set?
[ ] Test coverage is ok
[ ] Assignees are selected.
[ ] Minimum number of approvals
[ ] No changes are requested

Be nice. Be informative.
Closes #5869 from wForget/hotfix.
Closes #5869
1169f13f5 [wforget] Add volatile to variables that may be operated by multiple threads
Authored-by: wforget<EMAIL_ADDRESS>Signed-off-by: wforget<EMAIL_ADDRESS>(cherry picked from commit 37620d40b6a98dec6889d1ffb81e57b4966c4447)

merged to 1.8


DEVEXP-62: Use ExecuteScriptMarkLogic with consistent behavior

Thank you for submitting a contribution to marklogic-community/marklogic-nifi-incubator.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a github ticket associated with this PR? Is it referenced
in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

I encountered some issues regarding the second point. Once I ran the test (even without any modification of my modifications I received some connection errors. Other tests work fine, others are producing the same issue.
I attached some screenshots with the errors.


[ZK filter] Add per-opcode decoder error metrics

Commit Message: [ZK filter] Add per-opcode decoder error metrics
Additional Description: Currently, the ZK proxy filter only emits one decoder error metric, which include all decoder errors. This PR tries to emit per-opcode decoder error metrics, which is helpful for debugging. These metrics can be turned on or off via a proto field enable_per_opcode_decoder_error_metrics.
Risk Level: Low
Testing: Unit test
Docs Changes: docs/root/configuration/listeners/network_filters/zookeeper_proxy_filter.rst
Release Notes: changelogs/current.yaml

Hi @JuniorHsu, please review this PR whenever you have a chance, thank you!


How to disable internal Attributes for component.MarkupMatches(expected);

Is there a way to exclude the Blazor internal attributes __internal_stopPropagation_<eventname> and __internal_preventDefault_<eventname> from the component.MarkupMatches(expected); without marking each occurrence with :ignore?

Maybe with a code extension here? Something like this
public static bool IsBlazorAttribute(string attributeName)
    => attributeName.StartsWith(BLAZOR_ATTR_PREFIX, StringComparison.Ordinal)
    || attributeName.StartsWith("__internal_stopPropagation_", StringComparison.Ordinal)
    || attributeName.StartsWith("__internal_preventDefault_", StringComparison.Ordinal);

Hey @samtrion
Yeah, the specific attributes Blazor adds to the markup is handled in the Htmlizer class, so something like that would need to be added there. Can you show me the component that generates the markup, then I can add a testcase and fix that going forward.

And to answer your question, yes, I think the best solution for now is to use :ignore everywhere for now. I do hope to have a new release in a few weeks, that could include this, so they at that point become redundant.
If you want to help out with a PR on this, I would appreciate it. PRs should target the DEV branch.
Without having given much thought to a solution, I think that it should actually be handled in the same way as event-handler-trackers, by changing the attribute name to have the BLAZOR_ATTR_PREFIX prefix, making it play nice with the existing comparison/diffing logic, without any additions, probably adding another specific case to the switch statement in the file: https://github.com/egil/bunit/blob/master/src/Rendering/Internal/Htmlizer.cs#L220

Will create a PR.
Use an internally created variant for now, until the next release.

Awesome, much appreciated. Be warned, the project structure in the DEV branch has changed significantly. You will find Htmlizer.cs in the bunit.web project now - https://github.com/egil/bunit/blob/dev/src/bunit.web/Rendering/Internal/Htmlizer.cs.

PR was created.
Sorry about the Spacing Disaster.

NO worries. Added my review. Ill just squash in the end.


Remove unused imports + variables

Partially addresses #349.
The remaining warnings are mostly due to unused method + parameter (I'm not sure whether it is okay to remove them).

Hi @allantl,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
http://www.lightbend.com/contribute/cla

To validate this pull request against other sbt modules, please visit this link.

CLA signed

Thank you @jvican. Glad to help!


How to configure this action in case the repo has a private URL?

Hi, I tried this action in a public repo and it works like a charm, in my case the repo is not github.com, it has a private URL in a private organization. For that reason the action is not working as expected. How do I change the repo URL? I believe it's hardcoded here.
https://github.com/jonaslagoni/gh-action-dotnet-bump/blob/c0f5c67b381362a580b70a9885206af1b20ae7af/src/utils.js#L346
✖  fatal     remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/repo.git/'

git exited with code 128

in this case, github.com should point to a private URL.

Hey @jalexispoveda, Happy to accept a PR changing this behavior adding it as an option 👍😄

Hi @jonaslagoni I believe this fixes the issue, appreciate your feedback 😃 #21

:tada: This issue has been resolved in version 0.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Hi @jonaslagoni how do I use this release in my latest version? I am not sure if this is already deployed. Here's my action but does not seem to take the parameter into account.
- name:  Automated Version Bump
        uses:  joneja09/gh-action-dotnet-bump@main
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          version-part: 'Patch'
          path-to-file: 'Mango.Web/Mango.Web.csproj'
          repository-domain: 'test'

@jalexispoveda according to your image name its not this repo, should be lagoni/gh-action-dotnet-bump@main not joneja09/gh-action-dotnet-bump@main

Not sure if I am doing something wrong but your action is not found in GitHub, here's the .yml I tried to run. https://github.com/jalexispoveda/net-6-micro/actions/runs/6714454256
I was able to find your action here. https://github.com/marketplace/actions/automated-version-bump-for-net-libraries this was maybe published by another person

@jalexispoveda you where right, here is how I use it:
      - name: 'Automated Version Bump'
        uses: 'jonaslagoni/gh-action-dotnet-bump@main'
        id: version_bump
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          skip-tag: 'true'
          skip-commit: 'true'
          path-to-file: './RustPublicAPI/RustPublicAPI.csproj'
          release-commit-message-regex: 'chore\(release\): v{{version}}'


Include features currently exclusive to CMS 4 support branch

The ability to set alternative ACS domains was submitted to the CMS 4 support branch with the intention for it to be merged up. However the mainenance has diverged the branches, so this is a cherry-pick for feature parity instead.

LGTM, and sorry for the divergence @NightJar! As you say in your other issue, it's worth getting fixed up with the retirement of SS4 soon as well, so v2 can become legacy for SSv4, and we move on in the main branch. Merging!

As you say in your other issue

As I've just noticed they weren't linked, the other issue was #61 :)


Specifying A Library Version With ~> Doesn't Work On Mac

I have the following dub.json file
{
    "name": "dungeon",
    "sourcePaths": ["."],
    "dependencies": {
        "dgame": "~>0.6.0-beta.1"
    },
    "targetType": "executable"
}

This file successfully downloads dgame on Windows and Ubuntu, but on Mac I get the following error:
$ dub upgrade
Upgrading project in /Users/Jack/Dropbox/code/dlang/dungeon_game
Error executing command upgrade:
Root package dungeon contains reference to invalid package dgame

But, this dub.json file works just fine
{
    "name": "dungeon",
    "sourcePaths": ["."],
    "dependencies": {
        "dgame": ">=0.5.0"
    },
    "targetType": "executable"
}

Using: DUB version 0.9.23, built on Apr  6 2015

There must be something wrong with your local package cache (~/.dub/packages), everything works fine for me on either 0.9.23 or master. Can you post the output of dub upgrade --vverbose? After that I'd try to run dub clean-caches to see if the metadata is the issue, or run rm -r ~/.dub/packages if that didn't help. If possible, please make a quick copy of the .dub directory before all that, so that it's possible to find the root cause if the log output doesn't help.


ci: add 3 more Python versions to unit tests

People seems to be running ucc-gen not only on Python 3.7, so bringing in more tests for those versions as well.

:tada: This PR is included in version 5.14.0 :tada:
The release is available on:

v5.14.0
GitHub release

Your semantic-release bot :package::rocket:


Updated Azure Pipelines pool

I have set up a new agent pool to be used by Azure Pipelines since the old one was removed.
This PR makes use of the new pool and restores the LOCUST_PEAK_USERS to 100 which is the original value while we investigate why 500 fails in SGX with no prefix tree.

Add a readme explaining how to setup the pipeline, there is a doc directory for this:

how to create a pool
how to link it in azure devops

Add a readme explaining how to setup the pipeline, there is a doc directory for this:
how to create a pool how to link it in azure devops

Those are msft internal instructions while Azure Pipelines is an App already installed at Organization level (https://github.com/apps/azure-pipelines)

Should we now remove the GitHub action to run virtual tests, that we recently added? The full build should now cover everything and it seems repetitive to keep both just for reducing dependency on Azure.

Makes sense to me. Thoughts @ivarprudnikov ?

I would not remove Github action just yet as it is quite fast and acts as a
fallback in a case azure pipeline gets removed or similar.
On Tue 5 Sep 2023 at 12:51, Vincenzo Mauro @.***> wrote:

@.**** commented on this pull request.
In test/test_load.py
https://github.com/microsoft/scitt-ccf-ledger/pull/150#discussion_r1315784034
:

@@ -11,7 +11,7 @@
from pyscitt.client import Client

NUM_CLAIMS = 100
-LOCUST_PEAK_USERS = 500
+LOCUST_PEAK_USERS = 100
LOCUST_USERS_SPAWN_RATE = 10
Thanks, decreased to 5
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/scitt-ccf-ledger/pull/150#discussion_r1315784034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIA7YTG6XSUMZFUWQI7RJ3XY4G23ANCNFSM6AAAAAA4LT3QBA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reason for using mixin instead of overriding use or useOnBlock?

Hey there,  I was recently asked to add support for your mod (RPGStats#29) and as I went to look for where I could mixin or listen for your item being used, I noticed that your injecting at Item.use, is there any reason for this?
It makes compatibility harder (but not impossible) so I was wondering if there was a reason behind it, as opposed to simply putting your behavior in your already existing item class

Ah, thanks for mentioning this. The scythe tools were part of my first (unreleased) mod, so I just moved everything from there without changing too much.
I'm leaving some parts of the mixin, because I want to check for NBT data, so it's compatible with Smithee, until I think of something better.
I will push a new version later tonight. I just gotta fix some other things.

Ah, thanks for mentioning this. The scythe tools were part of my first (unreleased) mod, so I just moved everything from there without changing too much.
I'm leaving some parts of the mixin, because I want to check for NBT data, so it's compatible with Smithee, until I think of something better.
I will push a new version later tonight. I just gotta fix some other things.

Alright, thanks for the explanation!

Alright, thanks for the explanation!

I pushed the update on git and uploaded a build on CF. Hope this helps :)

I pushed the update on git and uploaded a build on CF. Hope this helps :)

having some issues with jitpack but it def looks far easier (Looks like ill only need 2 files instead of 5-7 :p), thanks much!

having some issues with jitpack but it def looks far easier (Looks like ill only need 2 files instead of 5-7 :p), thanks much!

I recommend CurseMaven. That's what I use personally.

I recommend CurseMaven. That's what I use personally.


JSON logs are sometimes not recognized

Reported by @rocketraman via https://groups.google.com/d/msg/sematext-docker-agent/k_CQIEqAALM/xRvcCzOdBwAJ

Any progress on this? Thx

Yes. I think its related to handling of multi-line parsers. Fix in work (detect JSON before multi-line processor).

Or perhaps even /^\{/ would be sufficient, given I know the log source produces json. If you think the fix will be in soon (within a day or so) I'll just wait, otherwise I'll look into the pattern workaround.

Logagent-js 1.x got a fix and tested on stdin (JSON in / YAML out):
echo '{"x":1}
 {"x":2}
 {"x":3}
 {"x":4}
 {"x":5}' | bin/logagent.js --yaml

Output in YAML format:
{"x":1}
x:          1
@timestamp: Wed Jul 27 2016 21:08:53 GMT+0200 (CEST)

{"x":2}
x:          2
@timestamp: Wed Jul 27 2016 21:08:53 GMT+0200 (CEST)

2016-07-27T19:08:53.893Z terminate reason: undefined
{"x":3}
x:          3
@timestamp: Wed Jul 27 2016 21:08:53 GMT+0200 (CEST)

{"x":4}
x:          4
@timestamp: Wed Jul 27 2016 21:08:53 GMT+0200 (CEST)

{"x":5}
x:          5
@timestamp: Wed Jul 27 2016 21:08:53 GMT+0200 (CEST)

So it outputs a message object in YAML format for each JSON line. In Docker agent, this should lead to a log message in Logsene for each JSON line.
@rocketraman Because we have no details about your data please try with this image. sematext/sematext-agent-docker:dev to test LD-JSON log output from Docker containers.
We will also use it for tests (tomorrow).

I just tried the :dev image, and it is not working properly. I see this notification from docker cloud:
sematext-agent-docker-2: Container stopped with exit code 2
2016-07-27T20:06:24.956883980Z     at processImmediate [as _immediateCallback] (timers.js:523:5)

Every log message causes the container to die and restart.

I got more information from the container logs -- seems to be an issue processing the @timestamp field in my logs:
sematext-agent-docker-2 | 2016-07-27T20:14:43.291419270Z   TypeError<EMAIL_ADDRESS>is not a function
sematext-agent-docker-2 | 2016-07-27T20:14:43.291428880Z     at Object.DockerLogsene.enrichAndLog (/usr/lib/node_modules/sematext-agent-docker/lib/dockerLogsene.js:278:47)
sematext-agent-docker-2 | 2016-07-27T20:14:43.291435915Z     at /usr/lib/node_modules/sematext-agent-docker/lib/dockerLogsene.js:204:14
sematext-agent-docker-2 | 2016-07-27T20:14:43.291442709Z     at Object.LogParser.parseLine (/usr/lib/node_modules/sematext-agent-docker/node_modules/logagent-js/lib/index.js:367:11)
sematext-agent-docker-2 | 2016-07-27T20:14:43.291449560Z     at DockerLogsene.getLogObject (/usr/lib/node_modules/sematext-agent-docker/lib/dockerLogsene.js:202:19)
sematext-agent-docker-2 | 2016-07-27T20:14:43.291456325Z     at Immediate._onImmediate (/usr/lib/node_modules/sematext-agent-docker/lib/dockerLogsene.js:296:10)
sematext-agent-docker-2 | 2016-07-27T20:14:43.291462962Z     at tryOnImmediate (timers.js:543:15)
sematext-agent-docker-2 | 2016-07-27T20:14:43.291469432Z     at processImmediate [as _immediateCallback] (timers.js:523:5)
sematext-agent-docker-2 | 2016-07-27T20:14:43.296348047Z {"@timestamp":"2016-07-27T20:14:43.269+00:00","@version":1,"message":"This is a test message.","logger_name":"FooCategory","thread_name":"XNIO-2 task-7","level":"DEBUG","level_value":10000,"HOSTNAME":"backend-1"}

Thx for reporting. Going to fix. The problem is that the timestamp needs to be converted to a JavaScript date object. The agent crashed here, because it tries to call a date function on a string.

What is the right way for my logs to put the timestamp in? I see this chunk of code skips timestamp parsing if the @timestamp field is already set, but even if it didn't, it wouldn't parse my @timestamp field anyway:
https://github.com/sematext/logagent-js/blob/master/lib/index.js#L375
BTW, just as a reminder, I am using https://github.com/logstash/logstash-logback-encoder. By default this encoder uses the Logstash json format (see https://github.com/logstash/logstash-logback-encoder#standard-fields) with @timestamp but I can configure it with whatever fields I want.

The date format is fine, and can be parsed by Node.js Date() function. Anyhow we have to think about handling various date formats in JSON fields (e.g. parsing with mooment-js and special pattern definitions to convert JSON objects). Currently you could define some conversion in patterns.yml with the globalTransform function.
Patch is on its way ... https://github.com/sematext/logagent-js/commit/5b8e017580c11a411ee879418d2bb0422bb5597c

I think that change is going to ignore my timestamp and replace it with a new one because the if at line 322 only does the timestamp parsing if @timestamp does not already exist:
https://github.com/sematext/logagent-js/commit/5b8e017580c11a411ee879418d2bb0422bb5597c#diff-6d186b954a58d5bb740f73d84fe39073R332

Also your changes at line 334 and 336 seem unnecessary because you have checked your values are already Date objects.

Thanks for the input. Line 322 is to look for alternative timestamp fields. In 334 condition to overwrite was wrong.
https://github.com/sematext/logagent-js/commit/3361aa02db9cda2a53fe2e3f8c50edc7787cc985
Feel free to make a PR to logagent-js, but keep in mind it should return an object with valid @timestamp.
I made a quick run with the new sematext/sematext-agent-docker:dev image, and it works fine with Kibana Logs.  I did also check your example in logagent (note my timezone is CEST):
{"@timestamp":"2016-07-27T20:14:43.269+00:00","@version":1,"message":"This is a test message.","logger_name":"FooCategory","thread_name":"XNIO-2 task-7","level":"DEBUG","level_value":10000,"HOSTNAME":"backend-1"}
@timestamp:  Wed Jul 27 2016 22:14:43 GMT+0200 (CEST)
@version:    1
message:     This is a test message.
logger_name: FooCategory
thread_name: XNIO-2 task-7
level:       DEBUG
level_value: 10000
HOSTNAME:    backend-1

Excellent, with your latest changes it should work perfectly. Are these changes available in sematext/sematext-agent-docker:dev already?

Yes. Please pull the image again.

Funny, I wrote we will test tomorrow. It is midnight here in Germany :)

Some good news before you go to bed: it worked perfectly! Thx for staying up late :-)

Hmm well the json parsing is working but a different issue now with the dev container: I'm getting many many duplicate logs in logsene.

Ok. Please try again with latest :dev image.

@megastef  Not getting any logging output at all from :dev, except for some logs shipped counts from the agent itself.

Sorry, the right build just finished. https://hub.docker.com/r/sematext/sematext-agent-docker/builds/

Redeploying now...

Works for my Kibana JSON logs (bunyan format).

Nope, still nothing:

Please add -e SKIP_BY_IMAGE=sematext-agent-docker
docker run -d --name sematext-agent-sda --restart=always -e SPM_TOKEN=MY_SPM_TOKEN -e LOGSENE_TOKEN=MY_LOGSENE_TOKEN -e SKIP_BY_IMAGE=sematext-agent-docker -v /var/run/docker.sock:/var/run/docker.sock sematext/sematext-agent-docker:dev```

Yup, its working now!

Thanks for the feedback, it will take a few more days for a new release.

No problem, I'll stay on dev for now. Thanks a lot for fixing this up.

The "latest" Image (1.30.15) should be updated to support your JSON logs

Excellent, will give it a shot. Would like to help resolve issue #13 first though -- just in case a redeploy masks the problem.

Now running 1.30.16 and everything works fine. Thanks!


Possible mod break/interaction issue: no stats increase anything except for Strength increasing melee damage

Hello,
I need more information on what you mean - could you please clarify?
Thank you!

While the mod is enabled, the only stat that increases is melee damage. All other stats - run speed, craft speed, player reach, inventory space - stay at their starting value.
Now granted it could have been another mod doing that, but I couldn't pinpoint exactly what caused it.
Note that Comfy RPG did not have this issue, either.

I see. Thank you for this.
Could you please provide the mods that you are using? I would love to fix this.

This seems to be identical to #3 - which is now fixed.


Add support for tsc build option in watch mode

The buildMode flag works great when building project but it is not taken into account when watching (ts errors happening on root project are shown but tsc does not check referenced projects).
This commit fixes this by using TS Compiler API SolutionBuilder when buildMode is set to true.

Hi
will this pr merge anytime soon?

Great PR, I'm curious where did you learn the programming API of TypeScript as there's no official documentation for it (AFAIK). I want to learn more about the API to get a better understanding of this PR. Thanks! @fredericlb

I'll merge this PR for now and try to add some test cases to verify the options before release 0.4.0! Thanks! @fredericlb


Standardise logging

This pull request introduces a refactoring of the util.Run and util.RunSilently helpers for managing child processes.  They are now in a separate package named childminder instead of the util dumping ground.
I have also changed the implementation for running child processes to proxy all the outputs on stdout and stderr of the child process through the logrus logger to make logging from child processes (perturb.sh, terraform, ssh keygen and ssh keyscan)  consistent with the other parts of simulator.
You will notice that all output now has the same prefix.  I adjusted perturb.sh removing all the formatting as this is now handled by logrus.
N.B.  The child process logging is not proper structured logging yet as it requires further refactoring to make the output attractive in the CLI, but this is a good first step I think

This is a draft for now because AWS is refusing to delete security groups so I havent been able to verify the changes to perturb logging yet

Still to do .. ignore errors reading from the child output pipes when the file has already been closed

Still to do .. ignore errors reading from the child output pipes when the file has already been closed

This is now fixed


Multiple refunds in woocommerce

Problem:
When refunding an order from Woocommerce admin when paid with Swish, two refunds appear in Woocoomerce admin which results in the paid amount being wrong. The actual refund is sent to Swedbank Pay is correct and paid to the customer correctly, but this affects the statistics and the order list.
Cause:
From what I can tell it seems to have something with the callback to do, everything is correct until it's executed creating an extra refund order. What I can find is that the _transaction_id metadata is never set on the refund created by Woocommerce which results in the core package creating another one.
Versions:
WordPress: 5.8.4
Woocommerce: 5.9.1
Swedbank Pay Payments: 4.4.2

@noaholsson To troubleshoot this we need access to your site. You can send details to<EMAIL_ADDRESS>

@olegisk I have sent over access information to a demo site now.


There is no cloud environment matching the name "AZURECLOUD"

Hi,
with the release 0.2.6, I am getting the following error:
error: environment "" was not found: autorest/azure: There is no cloud environment matching the name "AZURECLOUD"

on running pulumi update.
Maybe releated to #123?
I cannot understand witch commit fix this issue.
Thanks

Yes, it seems related. By chance, do you define the environment config value in your stack or ARM_ENVIRONMENT env variable? If yes, what is the value?

I have not set the ARM_ENVIRONMENT variable.
Not sure if Azure Pipeline does it for me.

Which authentication method are you using? A service principal?
As a workaround, try pulumi config set azure-nextgen:environment public or set ARM_ENVIRONMENT to public. This shouldn't be required, but maybe we missed something.

Yes I am using the Azure DevOps service principal:
export ARM_CLIENT_ID="$servicePrincipalId"
export ARM_CLIENT_SECRET="$servicePrincipalKey"
export ARM_TENANT_ID="$tenantId"
export ARM_SUBSCRIPTION_ID="$( az account show --query id -o tsv )"
export AZURE_KEYVAULT_AUTH_VIA_CLI=true
export AZURE_STORAGE_KEY="..."

pulumi login azblob://"..."
pulumi stack select --create dev --secrets-provider "azurekeyvault://..."
pulumi update --yes

I think most of the time would be ARM_ENVIRONMENT=public, is it possible to have this as default, as it is on ARM?
Thanks

I think most of the time would be ARM_ENVIRONMENT=public, is it possible to have this as default, as it is on ARM?

Yes, that's our intention and that's how it works for me. Still trying to repro your problem...

Ok. Thanks
I do not think that Azure Pipeline define a ARM_ENVIRONMENT environment variable by default, that's why it is empty.
Anyway with 0.2.5 works as expected.

Okay, I got the same error with an SP.  I will work on a fix to make public the default.

Thanks


uniclust database link dead

Expected Behavior
Go to uniclust website (https://uniclust.mmseqs.com/) and click "Download" to download uniclust database from "http://wwwuser.gwdg.de/~compbiol/uniclust/current_release/"
Current Behavior
The website http://wwwuser.gwdg.de/~compbiol/uniclust/current_release/ complaint:
Access forbidden!
You don't have permission to access the requested directory. There is either no index document or the directory is read-protected.
If you think this is a server error, please contact the webmaster.
Error 403
wwwuser.gwdg.de
Steps to Reproduce (for bugs)
http://wwwuser.gwdg.de/~compbiol/uniclust/current_release/

Fixed, thanks a lot!


Still having drawing bug where masks wont actually be created once drawn

I created a new environment and did a fresh install. The red circle does disappear once I close the loop but it doesn't turn into a mask. I've drawn four here and they're just stuck with the purple dotted lines. There is no drawing related output in the terminal either.

Originally posted by @mayishazn in https://github.com/MouseLand/cellpose/issues/961#issuecomment-2456358482
Also sorry for the repeat issue. It would just be highly convenient if I could fix masks on cellpose 3 directly.

oh no, I was hoping I had found the bug! Does this happen when you start from scratch: can you delete your _seg.npy file and start labeling again and confirm it happens? can you also please export your environment conda env export > cp.yml and share it here?
It seems to happen regardless of if I'm starting from scratch or fixing masks that cyto3 found.

idk if the image type matters? These are tiffs

For the stacks are you opening them with --Zstack? In that case single stroke is off

Yes I am opening them with --Zstack. So how do I edit them then?

Ahha that's it, you have to press enter to complete the mask, or you can turn on single stroke

This works for a few masks and then it gets stuck on draw mode again.


Issues when using post_hooks with incremental materialization

When using post_hooks to an incremental model seems that we are having some issues.

{{ config(
    materialized='incremental',
    format='iceberg',
    incremental_strategy='merge',
    unique_key='user_id',
    partitioned_by=['bucket(5, user_id)', 'status'],
    schema='silver',
    table_properties={
    	'optimize_rewrite_delete_file_threshold': '2'
    },
    post_hook = [
        "ALTER TABLE {{this}} SET TBLPROPERTIES ('vacuum_max_snapshot_age_seconds'='86400');"
    ]
) }}

with data as (
SELECT
	'a' AS user_id,
	'pi_updated' AS name,
	'inactive' AS status,
	17.89 AS cost,
	1 AS quantity,
	100000000 AS quantity_big,
	current_date AS my_date,
	cast(REPLACE(cast(current_timestamp as varchar), ' UTC', '') as timestamp(3)) as now
UNION ALL
SELECT
	'b' AS user_id,
	'beta_updated_yet_another one' AS name,
	'inactive' AS status,
	3 AS cost,
	50 AS quantity,
	100000000 AS quantity_big,
	current_date AS my_date,
	cast(REPLACE(cast(current_timestamp as varchar), ' UTC', '') as timestamp(3)) as now
)

select *
from data

produce this error
Completed with 1 error and 0 warnings:
08:07:30
08:07:30  Runtime Error in model iceberg_increment (models/iceberg/iceberg_increment.sql)
08:07:30    line 1:243: no viable alternative at input '<EOF>'

looking at the query produced I see this
-- /* {"app": "dbt", "dbt_version": "1.3.0", "profile_name": "athena", "target_name": "dev", "node_id": "model.lakehouse.iceberg_increment"} */ ALTER TABLE silver.iceberg_increment SET TBLPROPERTIES ('vacuum_max_snapshot_age_seconds'='86400')

somehow we have double comments.

This should be fixed.


ser2net service should be improved to watch for 13541 port

meta-rte version

0.7.4
Affected component(s) or functionality

ser2net
Brief summary

Currently for some reason port 13541 may not exposed even if service is running without issues:
root@rte:~# systemctl status ser2net
WARNING: terminal is not fully functional
● ser2net.service - ser2net
     Loaded: loaded (/lib/systemd/system/ser2net.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-02-28 09:48:14 UTC; 5 days ago
    Process: 180 ExecStart=/usr/sbin/ser2net -c /etc/ser2net.yaml -P /run/ser2net.pid (code=exited, status=0/SUCCESS)
   Main PID: 186 (ser2net)
     CGroup: /system.slice/ser2net.service
             └─186 /usr/sbin/ser2net -c /etc/ser2net.yaml -P /run/ser2net.pid

Feb 28 09:48:14 rte systemd[1]: Starting ser2net...
Feb 28 09:48:14 rte ser2net[180]: Unable to start mdns: Operation not supported
Feb 28 09:48:14 rte ser2net[180]: Invalid port name/number: Invalid data to parameter on line 11 column 0
Feb 28 09:48:14 rte ser2net[180]: Invalid port name/number: Invalid data to parameter on line 14 column 0
Feb 28 09:48:14 rte systemd[1]: Started ser2net.
root@rte:~# cat /etc/ser2net.yaml
%YAML 1.1
---

define: &confver 1.0

# Connection to read from /dev/ttyS1
connection: &con1
  accepter: telnet, tcp, 13541
  connector: serialdev, /dev/ttyS1, 115200n81, local

# Connection to read from /dev/debug_uart_converter
connection: &con2
  accepter: telnet, tcp, 13542
  connector: serialdev, /dev/debug_uart_converter, 115200n81, local
root@rte:~# netstat -an |grep 13541
root@rte:~#

It requires restart to make things work, what should happen automatically.
How reproducible

Sometimes
How to reproduce
Steps to reproduce the behavior:

ssh to platform
check if 13541 is exposed in netstat output
restart service and check again

Expected behavior

Actual behavior

Screenshots

Additional context

There are also other minor issues with the service (thanks to @miczyg1 ):

/dev/debug_uart_converter will never be a valid devnode
Current config will be different per platform. Some will have /dev/ttyS1 as primary connection and /dev/ttyUSB0 as secondary (or empty), OR /dev/ttyUSB0 as primary connection and secondary empty

Solutions you've tried

/dev/debug_uart_converter will never be a valid devnode

It will be if you create a proper udev rule to create it.
It is especially useful (even required) where you have more than 1 ttyUSB devices to have persistent naming.

Currently for some reason port 13541 may not exposed even if service is running without issues:

I think I saw such behavior when nothing was connected. Eg. ttyUSB0 configured, ser2net does not complain even if the device is not there, but you cannot connect.

It will be if you create a proper udev rule to create it.

I guess that confirms there is a problem with meta-rte because it should deliver such rules by default.

I think I saw such behavior when nothing was connected. Eg. ttyUSB0 configured, ser2net does not complain even if the device is not there, but you cannot connect.

Yes, but in my case restarting service fixed the issue, so apparently serial is connected.

I guess that confirms there is a problem with meta-rte because it should deliver such rules by default.

It does ship the above example (2 entries, the other two have been added for this particular case) currently. There is no one universal rule here. Depends on the platform. And even more, on specific adapters used on the test stand.
I think at best right now it can be documented, at least.

I have added information about this to the documentation https://github.com/Dasharo/docs/pull/798


Fix trigonometry around sunset and sunrise

The current implementation in gsee.trigon has some problems around sunrise and sunset where PV capacities become unreasonably large. This is due to the 1/cos(solar-zenith) term and the way that timestepping is handled.
I suggest a different way to compute the 1/cos contribution that is more representative for cumulative data and can handle non-hourly input data better. The basic idea is to compute 1/cos repeatedly on a sub-timestep scale, set unreasonably large contributions to zero and then average everything. More details can be found here:
background.pdf
I attach plots made using 3h reanalysis data for the initial implementation, using my changes and the difference between both. There are arch-like structures close to the sunset/sunrise lines in individual timesteps (most visible in June and December) using the initial version which vanish in the proposed one.
Initial

New

Difference

Open questions:

The sub-timestep calculations using N=20 steps slow down the code by a factor of around 5. Maybe one should tweak this a bit or leave it for the user to define in each individual application?
In some function call, an additional variable is needed to flag data as either instantaneous (satellite, ground observation) or cumulative (most climate models, reanalysis).

Thanks @jwohland! I have added a stub to differentiate between accumulated/instantaneous.
I think it would also make sense to test what value works for N and how that affects overall runtime of the code. Also, can you differentiate between the two cases in the unit tests so that those don't fail?
I have also run black on all the main module files. See https://black.readthedocs.io/en/stable/. This auto-formats the code. Can you make sure you run that locally too on making further changes? Hound is not yet set up to account for that, but will be.


Traceback (most recent call last):
  File "/app/manage.py", line 23, in <module>
    main()
  File "/app/manage.py", line 19, in main
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 414, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 98, in wrapped
    res = handle_func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/commands/makemigrations.py", line 214, in handle
    self.write_migration_files(changes)
  File "/usr/local/lib/python3.9/site-packages/django/core/management/commands/makemigrations.py", line 255, in write_migration_files
    migration_string = writer.as_string()
  File "/usr/local/lib/python3.9/site-packages/django_migrations_formatter/__init__.py", line 44, in as_string
    content = self._format_black(content)
  File "/usr/local/lib/python3.9/site-packages/django_migrations_formatter/__init__.py", line 25, in format_black
    mode = black.Mode(
  File "<string>", line 3, in __init__
TypeError: set object expected; got list

This issue seems to be related: https://github.com/psf/black/issues/2829

I was on an old version of this library!


Tile load queue

With more layers, there are many concurrent tile downloads. Is it possible to postpone loading of a certain layer until first layer's tiles of the current view are loaded?

No, sorry. Each TextureStore has its own load queue; the TextureStores aren't aware of each other, so they can't prioritize between themselves.

How about creating layers per scene separately and timing their creation accordingly - would that be possible? Maybe I could create scenes with first layer only keeping the remaining layers in a waiting stack? The issue would be how to avoid stage running out of sync with viewer?

We've decided to make some changes to the multi-layer API. It now looks like:
var scene = viewer.createEmptyScene({ view: view });
for each layer {
  scene.createLayer({ source: source, geometry: geometry, ... });
}

With this API a layer can be added at any time (and the stage will be updated accordingly) so I suppose you could try adding the foreground layers at a later time.

Incredible work, Tiago! This API is so much better! Wow!

Would it be a good idea to add some optional identifier to the layer object to make parsing through layers of each scene easier? Right now they are just stacked in an array and selecting them by their index is not reliable, as index gets changed each time a layer is added/removed.

Why not keep a reference to the layer (returned by Scene.createLayer) instead of indexing the layer list?

blink! I think that will be enough, thanks! :)


Update required to contribution-guide.md for draw.io

Add Draw.io to section 3.1 Documentation
Also need a section for a small guide on the workflow that we've been using to create and publish diagrams

PR docs: draw.io guide #68


Should not be able to shadow special forms

So
scm> (define define +)
define
scm> (define f 5)
f

should work properly, rather than raising an error.
On a related note, unquote outside of quasiquotes should raise a different error.

Resolved by #63


can it support to merge PDF form and PDF file? utf8?

i used pdftk to merge,but it can not support utf8 characher. For me, that's a bad thing.

There have been many improvements to qpdf since this issue was opened. I'm closing this, but feel free to reopen or create a new issue if this is still a problem. There's not enough information here for me to do anything with this. Thanks.


remove!: avatar_url & username from CreateFollowupMessage

The avatar_url & username fields are ignored by discord when creating an interaction followup response.

Should I revert the changes in this PR and instead add the deprecated notices, or shall this be done in a different PR?

Should I revert the changes in this PR and instead add the deprecated notices, or shall this be done in a different PR?

Great question! We can have two PRs here: one to deprecate the fields in the latest major version (main targets 0.7.x) and another PR to remove them in the next major version on the next branch.

Codecov Report

Merging #1287 (5935b23) into main (efb6045) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1287      +/-   ##
==========================================
- Coverage   31.03%   31.03%   -0.01%
==========================================
  Files         360      360
  Lines       14241    14235       -6
==========================================
- Hits         4420     4418       -2
+ Misses       9821     9817       -4

Impacted Files
Coverage Δ

...application/interaction/create_followup_message.rs
0.00% <ø> (ø)

http/src/routing/route.rs
5.95% <0.00%> (-0.63%)
:arrow_down:

http/src/routing/route_display.rs
9.98% <0.00%> (ø)

Continue to review full report at Codecov.

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

This has conflicts, and needs updating to the latest next.

I don't know why I can't get checks to run on this.

I think it was just loading.


What Matters Most?—Correlation Aboard the Titanic: Can't compare str with int

In section WOMEN AND CHILDREN FIRST the code example for finding the correlation between Sex and Survivability gave a type error.
Error: TypeError: unsupported operand type(s) for /: 'str' and 'int'
My solution for this derived from this StackOverflow post:
df.Sex.str.get_dummies().corrwith(df.Survived/df.Survived.max())
Result:
female    0.543351
male     -0.543351
dtype: float64

@Mintri1199 - thanks for catching this! Fixed in 130531b16c19e013d4a179c0d8c41282839a4630, live now in the tutorial