SparkJava - failed to validate http methods for Static files

HI,
Need help on static files
Issue : When the application startup, the static file can be accessed with any(GET,POST, XXX) http method
Application fails in Vulnerability scan as below
identified:  - Verb tampering,   Only allow required http methods e.g. get, post.
Spark Java version : spark-core:2.7.2
Server: Jetty(9.4.14.v20181114)
is it possible to add filter or some other alternative to stop accessing the static information from CURL or POSTMAN ?
Sample reproducer
import static spark.Spark.halt;
import spark.Service;
public class ServerExample {

    public ServerExample() {
        Service service = Service.ignite().port(4568);
        service.staticFiles.externalLocation("C:\\dev");  //file attached for dev folder

        service.before((req, res) -> {
            System.out.println("Hello:" + req.headers());
        });

        service.get("/", (req, res) -> {
            if (!req.requestMethod().equalsIgnoreCase("GET")) {
                halt(401, "invalid Http method");
            }
            return null;
        });
    }
    public static void main(String[] args) {
        new ServerExample();
    }
}

reproduce issue from CURL
1.

curl -X XYZ --insecure http://localhost:4568/
Response -> <!doctype html>Welcome

curl -X XYZ --insecure http://localhost:4568/manifest.json
Response ->
{
"icons": [
{
"src": "favicon.png",
"sizes": "48x48",

The XYZ above call is invalid HTTP method.
The app should not respond to any invalid http method, adding filter "/" is not considered.
Could any help to fix this.
dev.zip

@Prashantha-AV
Hi. I think the correct behavior is to return a 405 code if the file is found, but the http method is not supported. Do you agree?


Runs fail to set up with errors in RunAllocator#getHostInfo

Error: ENOENT: no such file or directory, unlink '.../.vivaria/mp4-tasks-exports/...-ec68f8808b10190950924b13e79eeb886daa9211/metr-task-standard/setup.py'
    at unlink (node:internal/fs/promises:1066:10)
    at mayCopyFile (node:internal/fs/cp/cp:246:5)
    at copyDir (node:internal/fs/cp/cp:320:19)
    at TaskFetcher.fetchInternal (/home/nonroot/deployments/v0/server/src/docker/tasks.ts:297:5)
    at TaskFetcher.fetch (/home/nonroot/deployments/v0/server/src/docker/tasks.ts:263:7)
    at K8sHostFactory.createForTask (/home/nonroot/deployments/v0/server/src/services/K8sHostFactory.ts:16:18)
    at RunAllocator.getHostInfo (/home/nonroot/deployments/v0/server/src/RunQueue.ts:325:30)
    at _RunQueue.startRun (/home/nonroot/deployments/v0/server/src/RunQueue.ts:211:19)
    at /home/nonroot/deployments/v0/server/src/util.ts:27:7
    at AsyncSemaphore._execWithRelease (/home/nonroot/deployments/v0/shared/src/lib/AsyncSemaphore.ts:39:14)

I think we've seen these before but I expect them to become more prevalent when we're starting a bunch of runs at a time under k8s, rather than one run every six seconds.
I think the problem is race conditions between different instances of TaskFetcher. I thought of a couple of things we can do:

Make TaskFetcher#fetchInternal atomic. Have it construct the task build context directory structure in a temporary directory, then move the temporary directory to its final location. Moves are atomic (enough?) on the filesystems we use, I'm pretty sure. https://stackoverflow.com/questions/7054844/is-rename-atomic We could do the same for agent fetching. Or any other places where we construct a directory that has a particular shape. Eh I think it isn't necessary for agent fetching -- except for getOrCreateAgentRepo. I could see there being problems with multiple concurrent git inits in the same directory? But that kind of error won't happen so often because we aren't often creating new agent repos.
~When reading a task's manifest, we don't really need to construct its Docker build context.~ We can just read it out of the mp4-tasks Git repo... or uh wait, for uploaded tasks we do need to at least untar the task tarball. Fair. So maybe not this.


Documentation?

Doesn't seem to be any. Is this actively maintained?

It was shared and working, in case anyone would benefit from use. Happy to give guidance and support if you have any issues!

(Have just copied a quick example into the readme - hope that helps.)

Okay cool thanks 👍


[0.4.0] Failures stack trace is not readable

For failed workflows the old ui allows to click on a failure and display the stack trace in a readable way, for example:

The error stack trace in new view is shown js JSON and you cannot really read it as its a 10-mile long string in this display:

Maybe it will be possible to show the error stack trace in some similar view as before. Thanks.

@canvanooo If it's a failure, should we just show the stack trace at the top of the view?

@stevekinney I think so, the failure message goes in the output result, is that current behaviour? Looks like the json format isn't what is preferred and to only show the stackTrace string that's is part of the json, in a prettier format, with an expandable icon to display in a modal.

@canvanooo Right now, only the completed result goes into result. Do y'all want the failure to go in the result if the workflow has failed?

@tsurdilo I've moved this over to the UI backlog, and will close this out here.


App not responding and showing black screen(ANR)

our app shows discovery screen with a count of 150 movie posters, we implemented this using recycler view and each poster is a ImageView.
The app working fine even after loading all posters.
case 1: When i press back key here it will go oculus home exit dialog and if i select cancel again its navigate to my app but my discovery page showing black and some time then ANY dialog showing and ANR repeating number of times.
case 2: launch app -> Discovery screen shows -> recent windows -> kill my app -> launch app again
observe black screen and then ANR.
So there is a logic missing to clear my bitmaps while exiting app to oculus home or home screen.
in Android Recycler view will handle everything for us. So how to fix this in case of GVR.
The recyclerview i am adding to GVRViewSceneObject in my implementation.
ANR trace:
at java.lang.Object.wait(Native method)
  - waiting on <0x0c89a496> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:2135)
  - locked <0x0c89a496> (a java.lang.Object)
  at sun.misc.Unsafe.park(Unsafe.java:358)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:190)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:868)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1021)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1328)
  at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:232)
  at org.gearvrf.GVRTexture.getId(GVRTexture.java:162)
  at org.gearvrf.scene_objects.GVRViewSceneObject$RootViewGroup.createRenderData(GVRViewSceneObject.java:688)
  at org.gearvrf.scene_objects.GVRViewSceneObject$RootViewGroup.onLayoutReady(GVRViewSceneObject.java:623)
  - locked <0x08c4f817> (a java.lang.Object)
  at org.gearvrf.scene_objects.GVRViewSceneObject$RootViewGroup.access$400(GVRViewSceneObject.java:495)
  at org.gearvrf.scene_objects.GVRViewSceneObject$RootViewGroup$2.onGlobalLayout(GVRViewSceneObject.java:614)
  at android.view.ViewTreeObserver.dispatchOnGlobalLayout(ViewTreeObserver.java:1013)
  at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2638)
  at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1738)
  at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7745)
  at android.view.Choreographer$CallbackRecord.run(Choreographer.java:911)
  at android.view.Choreographer.doCallbacks(Choreographer.java:723)
  at android.view.Choreographer.doFrame(Choreographer.java:658)
  at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:897)
  at android.os.Handler.handleCallback(Handler.java:789)
  at android.os.Handler.dispatchMessage(Handler.java:98)
  at android.os.Looper.loop(Looper.java:164)
  at android.app.ActivityThread.main(ActivityThread.java:6938)
  at java.lang.reflect.Method.invoke(Native method)
  at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

Unfortunately, i am not authorized to share our code sample  :(
With the sample apps i did not observe the issue(sample apps load simple textures)
I can brief about our implementation:
After login the app we show discovery page which shows movie posters, the implementation done using the hetero recycler view set to discovery fragment.
We are populating data horizontally and vertically.
As of now we have 11 vertical rows and each row have 15 posters so total of 265 posters(bitmap set to ImageView) will loaded when we scroll completely.
logs:
https://drive.google.com/open?id=1Y9tNbjZGRLDRDArtfgqxwlepD7NfSWZM
https://drive.google.com/open?id=1pG_o0O9gwR49q9lZIdcoRz60he7A89li
When i select back key to go oculus home and press back to come back app ->  i can see the black screen and after while ANR dialog,
Kill app from recent windows and launch again -> again black screen and then ANR dialog.
in the attached logs please refer package name:  com.att.android.vr

@spakanati123 Are you creating all of your GVRViewSceneObjects from the GVRMain.onInit method? Can send me the /data/anr/traces.txt file from the phone? It shows complete thread dump so I could see what on the rendering thread deadlocks the Android thread.
Can you build the framework yourself? Try removing the "synchronized (mLock)" from GVRViewSO.onNewParentObject and GVRViewSO.onRemoveParentObject.

@liaxim i am not adding all my scene objects in GVRMain.init.
Initially adding only login scene object and once login success removing the loginSceneObject and then adding the SplashScreenObject.
Once splash animation over i receive a callback, in the callback removing splashSceneObject and adding Discovery sceneObject.


Updated get-testnet-tokens.md and account-creation.md

I updated the contents of the get-testnet tokens tutorial and some of the account-creation tutorial since it is referenced in the get-testnet tokens tutorial.  I was unable to get any answers from Telegram or the forums on if the edgenet was still alive, but I was unable to connect to any of the URLs or endpoints of it so I removed it from the tutorials.  I can readd it if it is still alive.  Please let me know if you would like me to make any additional changes to these tutorials.  I will begin my work on the others :)
AE Address: ak_Fowfckktub4tsPW35mfUwYSjhDxCLdEYacNeCx2qMhtSVXFLb

some of the tutorials were already updated, can you make separate PRs for any tutorial that has not been updated yet?

I'll close this, feel free to reopen if only non-update tutorials are adjusted

@thepiwo so I did all this work for nothing?  If there were PRs already submitted before mine 15 days ago, why weren't they merged prior?  Was mine included?  Spending time on these when they didn't need to be updated.  Feel cheated.

Sorry I don't know how to answer this, I tried to merge in the order they did come in, once they were finalized and reviewed. Also I tried not to merge similar changes on the same tutorial, if it worked fine prior.
Please don't feel cheated, if you find this behavior unfair please contact the organizers of the bounty program to find an agreement. I do just overlook the content of this repository and am not involved with the bounty program.


Duplicated Max Threads setting on Import Screen

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Go to Import Screen and you will see:

Expected behavior
Only one setting for threads

This bug has been addressed in the make-open-source pull request.


proposed extensions to IAO:'document part' and IAO:'textual entity'

Hello,
The attached patch file contains proposed extensions to the IAO:'document part' and IAO:'textual entity' sub-hierarchies. This work resulted from an examination of section headings in articles in the PubMed Central Open Access subset. New classes for document parts (and accompanying textual entity classes where applicable) include:

abbreviations section
author information section
author summary section
availability section
case report section
conclusion section
conflict of interest section
consent section
ethical approval section
figures section
funding source declaration section
future directions section
genome announcement section
keywords section
materials section
notes section
patients section
pre-publication history section
related work section
requirements section
statistical analysis section
study limitations section
tables section

Also included in the patch are several alternative term suggestions for some previously defined classes:

acknowledgements section
author contributions section
supplementary material to a document
methods section
results section
introduction to a publication about an investigation
discussion section of a publication about an investigation

All proposed classes include a definition, example of usage, editor preferred term, label, and term editor. Some also contain alternative terms. I hope you find that these suggestions meet the criteria for inclusion in the IAO. Please let me know if any changes are necessary.
Best,
Bill Baumgartner
proposed_extenstions_to_document_part_and_textual_entity.patch.txt

I second the request.

I will send a note to the developer list asking if there are any comments or objections, and in two weeks, assuming there are none, I will add these definitions.

Here is the note: https://groups.google.com/d/msg/information-ontology/IyYWAov71ZI/2QAjn2BUAQAJ
If you are interested in become an IAO committer, please contact me with your github id and I will add you.

No objection. It's good to have these terms in IAO.

Seems fine to me.

Sounds good to me. Will there be some pattern for annotation properties, e.g. definitions etc? It would be good to homogenised this part of the ontology as this would be a significant addition.

Thanks for moving this forward Alan. I'm not sure if I need to be a
committer at this stage, however if you feel that is appropriate my github
id is bill-baumgartner.
Regarding the question about a pattern for annotation properties, I tried
to be consistent with other classes in the IAO. If there are things that
are missing or need to be revised please let me know and I would be happy
to address them.
Best,
Bill
On Mon, Oct 17, 2016 at 9:50 AM, Melanie Courtot<EMAIL_ADDRESS>wrote:

Sounds good to me. Will there be some pattern for annotation properties,
e.g. definitions etc? It would be good to homogenised this part of the
ontology as this would be a significant addition.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/information-artifact-ontology/IAO/issues/183#issuecomment-254247950,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG4gOrZNT6dm9w8-GdFfK4jI0g1o_oB0ks5q05k4gaJpZM4HjHNL
.

Hi Bill,
I added you to the group. You can take advantage of it when you see fit.
The WIP of merging is in the branch merge-document-parts. Next step is to assign IAO purls. I have some script to do that, and I'll get to it asap.
I had a question. All (most?) of the terms come in pairs: section and textual entity. I was wondering what your rational the duplication was. What do you see as differentiating the section from the textual entity?
Arguably there shouldn't be a hard line, and some of the existing definitions of document parts have the flavor of textual entity definitions.
One way to think about the question is: If the textual entity is one part of the section, what are the other parts? Perhaps adding something along those lines would help with better distinguishing the two.
One way to handle this would be to defined a document part as anything that is part of a document - a defined class. Then, textual entities might be also classified as document parts, but one wouldn't need to assert that they were subclasses of both, something we try to avoid.
Alan

Couldn't this issue also be closed, considering the fact that these new terms are in the current release (e.g. see here) and https://github.com/information-artifact-ontology/IAO/issues/187 having been closed?

All request terms have been added.


Creators should only be linked to Flickr user IDs; not Wikidata entities

Nobody has said anything about this on the Commons side, so I'm going to merge this.


Can not detect Edge on windows 10 and windows 10 mobile

Desktop User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Phone User-Agent: Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; Microsoft; Lumia 650) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Mobile Safari/537.36 Edge/14.14263

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Maven suggested dependency does not match the one used within the example code

[Enter feedback here]
Basically, the suggested Maven dependency is not the one that is used in the example code.

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

ID: 13994f3e-a96a-8804-4deb-7e0adad7f479
Version Independent ID: e087d8ce-bf3a-f12c-41dc-3ea924c6f089
Content: How to work with the GPT-35-Turbo and GPT-4 models - Azure OpenAI Service
Content Source: articles/ai-services/openai/how-to/chatgpt.md
Service: cognitive-services
Sub-service: openai
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

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

@mrbullwinkle
Could you please review add comments on this, update as appropriate.

@barryyosil
Thank you for bringing this to our attention.
I've delegated this to content author @mrbullwinkle, who will review it and offer their insightful opinions.

Thanks for reporting this issue. We have fixed the issue, as well as updated the quickstart code to the latest package: https://central.sonatype.com/artifact/com.azure/azure-ai-openai/1.0.0-beta.10
The change is merged internally and will go-live in the public docs later today.

#please-close


[Bug] New Helmet client-side TypeError with external template file

Describe the bug
When using Helmet on the client side only, with an external template file, it is throwing an error as soon as you add more then one tag to the <Helmet />. This was not an issue before the new helmet update.
<Helmet>
  <title>{this.props.title ? this.props.title : '404 Error'} - Nano JSX</title>
  {/* Helmet crashing, when using an external template file, and adding more then one tag to the helmet */}
  <meta name="description" content="Nano-JSX application" />
</Helmet>

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')
Pointing to this line of code:
for (let r = 0; r < e.attributes.length; r++)

Just to demonstrate I created a repo.

The issue is the jsx-runtime.
Use:
"jsx": "react",
"jsxFactory": "h",
"jsxFragmentFactory": "Fragment",

And don't use children as a props like here: <Layout children={page} title="About" />
Do <Layout title="About">{page}</Layout> instead.

Why is the runtime the issue? When I use those options my VS Code is freaking out and every line of code is red:
TS2304: Cannot find name 'h'.

Use import { h } from nano-jsx/lib/core` on every page for now.


[SPARK-13543][SQL] Support for specifying compression codec for Parquet/ORC via option()

What changes were proposed in this pull request?
This PR adds the support to specify compression codecs for both ORC and Parquet.
How was this patch tested?
unittests within IDE and code style tests with dev/run_tests.

Test build #52305 has started for PR 11464 at commit a96e510.

retest this please

Test build #52306 has started for PR 11464 at commit d107d50.

cc @rxin

Test build #52307 has started for PR 11464 at commit 9c53d10.

How does this relate to https://github.com/apache/spark/pull/11408?

Test build #52305 has finished for PR 11464 at commit a96e510.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52305/
Test FAILed.

@rxin I think I should change the codec names to lower cases here.

Test build #52306 has finished for PR 11464 at commit d107d50.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52306/
Test PASSed.

Test build #52307 has finished for PR 11464 at commit 9c53d10.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52307/
Test PASSed.

Merged build finished. Test PASSed.

Test build #52312 has started for PR 11464 at commit 12e7275.

I will handle the consistent stuff in a new PR based on https://github.com/apache/spark/pull/11464.

Test build #52312 has finished for PR 11464 at commit 12e7275.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52312/
Test PASSed.

@rxin Could you maybe merge this first before dealing with consistent compression name stuff if it looks good?

There is a conflict. Maybe just make stuff consistent here?

@rxin Sure.

Test build #52349 has started for PR 11464 at commit baf7a63.

Test build #52349 has finished for PR 11464 at commit baf7a63.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52349/
Test FAILed.

Test build #52360 has started for PR 11464 at commit 4e212b1.

Hm.. This will not explicitly set uncompressed or none for JSON, CSV and TEXT. Let me correct them and add some tests.

Test build #52368 has started for PR 11464 at commit 2817c9a.

@rxin I think this is ready to be reviewed.

Test build #52360 has finished for PR 11464 at commit 4e212b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52360/
Test PASSed.

Test build #52368 has finished for PR 11464 at commit 2817c9a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52368/
Test FAILed.

retest this please

Test build #52378 has started for PR 11464 at commit 2817c9a.

@davies can you help review this? Thanks.

LGTM

Test build #52384 has started for PR 11464 at commit d2ace37.

test this please

Test build #52385 has started for PR 11464 at commit e4d4cfb.

Test build #52378 has finished for PR 11464 at commit 2817c9a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52378/
Test PASSed.

Test build #52385 has finished for PR 11464 at commit e4d4cfb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52385/
Test PASSed.

Merged build finished. Test PASSed.

Test build #52384 has finished for PR 11464 at commit d2ace37.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52384/
Test PASSed.

Thanks - merging this in master.

Changes like this should probably also update the programming guide.


assume IAM role for running nightly release tests

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1037  👈
#1025
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jlewitt1 and the rest of your teammates on  Graphite


MB-8159 see additional destination addresses on review page

Description
Add secondary destination address to the review page for the shipment card types of HHG and NTSR.
Reviewer Notes
I didn't add the secondary destination address to the PPM or NTSS Shipment types since it didn't look like they had a destination address in the first place.
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make client_run
make server_run
make storybook

HHG unsubmitted should have a secondary destination address.
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - Denial of Service
Package css-what
Patched in >=5.0.1
Dependency of react-scripts
Path react-scripts > html-webpack-plugin > pretty-error > renderkid > css-select > css-what
More info https://npmjs.com/advisories/1754
high - Regular Expression Denial of Service
Package trim-newlines
Patched in >=3.0.1 <4.0.0 || >=4.0.1
Dependency of node-sass
Path node-sass > meow > trim-newlines
More info https://npmjs.com/advisories/1753
high - Denial of Service
Package css-what
Patched in >=5.0.1
Dependency of react-scripts
Path react-scripts > @svgr/webpack > @svgr/plugin-svgo > svgo > css-select > css-what
More info https://npmjs.com/advisories/1754
high - Denial of Service
Package css-what
Patched in >=5.0.1
Dependency of react-scripts
Path react-scripts > optimize-css-assets-webpack-plugin > cssnano > cssnano-preset-default > postcss-svgo > svgo > css-select > css-what
More info https://npmjs.com/advisories/1754
high - Regular Expression Denial of Service
Package normalize-url
Patched in >=4.5.1 <5.0.0 || >=5.3.1 <6.0.0 || >=6.0.1
Dependency of react-scripts
Path react-scripts > mini-css-extract-plugin > normalize-url
More info https://npmjs.com/advisories/1755
high - Regular Expression Denial of Service
Package normalize-url
Patched in >=4.5.1 <5.0.0 || >=5.3.1 <6.0.0 || >=6.0.1
Dependency of react-scripts
Path react-scripts > optimize-css-assets-webpack-plugin > cssnano > cssnano-preset-default > postcss-normalize-url > normalize-url
More info https://npmjs.com/advisories/1755
6 high vulnerabilities and 0 critical vulnerabilities found

Messages

:book:
:link: MB-8159

  Generated by :no_entry_sign: dangerJS against a9bba0af86f5ac79c7e8760c6145f6dbf4b3dd4d

Visually looks great! You are correct that PPM and NTS should not have a second destination, but NTS-R actually does have a destination, and so does need the secondary destination added. Sorry, should have called that out in the ticket!


Fix file name of the requirements.txt file

Hi, I fixed a typo of the requirements.txt file.
Closes #1

Thank you for your contribution.


Rive file with nested arboard is freezing after loading

Description
Rive file with nested arboard is freezing after loading only in Rive iOS package. In React library and Rive editor is working properly.
Provide a Repro
https://github.com/Ursula-AI/rive-ios-nested-artboard-bug
Source .riv/.rev file

.rev file: https://github.com/Ursula-AI/rive-ios-nested-artboard-bug/blob/51bca87c0d995f33e19e59d989508cf9d42dd759/Rive iOS Nested Arboard Bug/Files/ball_test.rev
.riv file: https://github.com/Ursula-AI/rive-ios-nested-artboard-bug/blob/51bca87c0d995f33e19e59d989508cf9d42dd759/Rive iOS Nested Arboard Bug/Rive iOS Nested Arboard Bug/ball_test.riv

Expected behavior
Nested artboards working just like a normal artboard without freezing.
Screenshots
Video recordings on Rive and iOS Preview:
https://github.com/Ursula-AI/rive-ios-nested-artboard-bug/tree/51bca87c0d995f33e19e59d989508cf9d42dd759/Rive iOS Nested Arboard Bug/Files
Device & Versions

Device: iOS Simulator, iPhone 13
iOS version: 17.4

It may be related to this?
https://github.com/rive-app/rive-ios/pull/112
https://github.com/rive-app/rive-ios/pull/113

Wow that was fast @mjtalbot! Thank you very much 🙇🏻♂
Now I noticed some other bug: exposed inputs from nested artboards are not working.
I've updated the repository with a new Rive file that has a state machine with both nested input and normal input.

Do I need to open a new issue?


IRotationWatcher.aidl is not found in Device.java

public void registerRotationWatcher(IRotationWatcher rotationWatcher, int displayId) {
serviceManager.getWindowManager().registerRotationWatcher(rotationWatcher, displayId);
}
cant find irotation watcher

How do you build?

public Device(Options options) {
displayId = options.getDisplayId();
DisplayInfo displayInfo = serviceManager.getDisplayManager().getDisplayInfo(displayId);
if (displayInfo == null) {
int[] displayIds = serviceManager.getDisplayManager().getDisplayIds();
throw new InvalidDisplayIdException(displayId, displayIds);
}

i am trying to merg your project with mine i have already made a modified Screen Capture Grafika Example to stream but it only work with the latest version of mobiles have capture feature your is working without it so this is the last exception i am having.

aganin that is a java file which was missing i have not coppied it thanx Succeeded

but run time assert exception

Hi,
Please stop spamming the issue tracker with problems on your own project/build/fork.
Thank you.

its to rude to live person spam you could have told me that in activity i cant perform it. this can only work with shell app. hugs


Immutable is not Immutable

Simple test:

var p = { name: "Daniel" };
var i = Immutable(p);

i.name = "Daniel Alves"; // should not be changed but has changed at all

** Probably reason**
The Object.freeze is inside the node checking if.
function makeImmutable(obj, bannedMethods) {
    // Tag it so we can quickly tell it's immutable later.
    addImmutabilityTag(obj);

    if (process.env.NODE_ENV !== "production") {
      // Make all mutating methods throw exceptions.
      for (var index in bannedMethods) {
        if (bannedMethods.hasOwnProperty(index)) {
          banProperty(obj, bannedMethods[index]);
        }
      }

      // Freeze it and return it.
      Object.freeze(obj);
    }

I made a pull request to this.

But I think it's intentional, isn't it? Objects are frozen only in development mode. Because in production it will result in performance issues.

@smashercosmo I think the issue is that it is not freezing in non-node environments (like a browser).
@danfma Is that right?

From the project description:

In the development build, objects are frozen. (Note that Safari is relatively slow to iterate over frozen objects.) The development build also overrides unsupported methods (methods that ordinarily mutate the underlying data structure) to throw helpful exceptions.

The production (minified) build does neither of these, which significantly improves performance.

So if you use the main /src/seamless-immutable.js it just works and respects your NODE_ENV setting if you run it in node. If you run it in a browser you can either use the same file if you have a build environment where you have configured it or you can use the /seamless-immutable.development.js or /seamless-immutable.production.js directly which requires no setup of NODE_ENV.

If you want to use the default /src/seamless-immutable.js and configure your build to set the correct mode then do as they suggest in React: https://facebook.github.io/react/downloads.html#npm (check the note for npm). It works in the same way for seamless-immutable.

Yep, this is working as intended. Thanks to all who responded explaining why this works the way it does!


Get features from all targets

Closes #2568
Closes #2567
Introduced changes

Fixed features support for optimized compilation
Changed the starknet artifacts loading logic so they work with custom test targets.
Artifacts are now loaded from all test targets
Artifacts are now compiled to casm concurrently
Refactored the scarb-api crate

Checklist

[x] Linked relevant issue
[x] Updated relevant documentation
[x] Added relevant tests
[x] Performed self-review of the code
[x] Added changes to CHANGELOG.md

The docs on how this work needs to be updated in #2627


near call is using deprecated functionCall method

near call is currently using deprecated version of account.functionCall method that uses positional arguments. We should update this in near-cli that passes an object for args.

related to https://github.com/near/near-cli/issues/760#issuecomment-852195475

related to #760 (comment)

ahh nice, was submitting this based on an issue raised in our telegram dev support channel. Didn't see that this was already created. Thanks @volovyk-s !


Metamodel 133

Hi,
This is a fix for METAMODEL-133 issue for supporting multiple joins. Please review.

My 5 cents:

I like the approach you've taken here with the compound from items array.
But shouldn't we rather then take a step further and delete the "leftItem" and "rightItem" and let the array replace them.
Similarly I would expect an array for the "on items" then. And then delete the "leftOn" and "rightOn" fields.
Then you would no longer need "_isCompoundJoin" - it would always be a (compound) join if there is an array available.

Alternative approach is to keep FromItem as it is and just apply the nested FromItem structure when parsing the query. That would retain 100% backwards compatibility and only do something in the query parsing layer to fix the issue. Might also be an option.

Hi,
I looked into the points you mentioned above. Below are my thoughts.

We actually need "leftItem" and "rightItem" as we even use it in compound from items ultimately, since it's the only way to represent join.

"on items" are indeed array of select items and for each from item we need them seperately since there might be other operations than "=".

I didn't try about nested from items but it needs code change more than this. Moreover with this approach we are using existing code which is both unit tested and time tested.

This doesn't cause any api changes either as there is no change in signature of any public method.

And any idea why travis ci build failed. It ran perfectly fine while I unit tested it. Could it be because of other PRs pending?

But it is possible to do multiple joins using the existing API, it's just a bit cumbersome IMO and it has no query parser support. Here is an example:
SELECT COUNT(*) FROM
 (table1 INNER JOIN table2 ON table1.key1 = table2.key2) a
 INNER JOIN table3 ON a.key2 = table3.key3

Table table1 = ...
Table table2 = ...
Table table3 = ...

FromItem joinPart1 = new FromItem(table1);
FromItem joinPart2 = new FromItem(table2);
FromItem joinPart3 = new FromItem(table3);
SelectItem key1 = new SelectItem(table1.getColumnByName("key"))
SelectItem key2 = new SelectItem(table1.getColumnByName("key"))
SelectItem key3 = new SelectItem(table1.getColumnByName("key"))

FromItem join1 = new FromItem(JoinType.INNER, joinPart1, joinPart2, new SelectItem[] {key1}, new SelectItem[] {key2});
join1.setAlias("a");

SelectItem key2inJoin1 = new SelectItem(key2, join1);

FromItem join2 = new FromItem(JoinType.INNER, join1, joinPart3, new SelectItem[] {key2inJoin1}, new SelectItem[] {key3});

Query q = new Query();
q.selectCount();
q.from(join2);

Very cumbersome in deed ... We very much need parsing here AND probably also some more convenience constructors.

And sorry no I don't know why Travis failed ... Seemed to happen in the elasticsearch module which normally works fine. Can you try a local build?

But if we use multiple joins as above wouldn't it cause problem in case let's say there is a column with name "key2" in both table1 and table2?

It's a bit beyond my memory actually... Let me say it like this: I think it works because I am not aware of any bugs in that regard :-)

Hi,
I have used recursion as you suggested. And yes there was very less code change :) Please review

The reason I'm passing array+instance of from item is, the instance is we know for sure right side item. If we just pass set(including right side item), there will be n square combinations we need to check. Or am I wrong?

Done with my review. Only minor remarks really. The only one that I am a little bit concerned with is the parenthesis hiding approach. This seems to maybe be too destructive.

Hi,
the reason for removing alias for onSelectItem(side Alias) is let's say we have a query like below:
Query query = context.parse("Select a.col2 from A a INNER JOIN B b ON a.col1 = b.col2 INNER JOIN C c ON a.col3 = c.col3");
If we parse it by replacing sideAlias of select Item then it gets translated as below:
"SELECT a.col2 from A a INNER JOIN B b on a.col1 = b.col2 INNER JOIN C c ON b.col3 = c.col3"
which is wrong and results in SQLException

And the reason I put that condition for only leftFromItem is since we parse from left to right, only left from item can have composite join. Can you think of a scenario where even rightFromItem can be composite. Is so I will add that also.

The right item way is also possible because anyone can build such a query programmatically. In our use of MetaModel we mostly do that and don't use the parser. A bit cumbersome, but allows different components to influence the query plan that we have as a kind application of the visitor pattern.

I don't think I understand what you're saying about the side alias... I honestly also cannot remember all the nitty gritty details ... Just feel that it's a bit dangerous to throw that alias away - it could be referred to elsewhere I guess.

We are definitely not getting rid of alias. Instead we are using the select item as is. i.e. select item column name or expression along with its alias. In the unit test case you can see all aliases present.

And I have done that change of passing entire set and with push it today.

OK I'm gonna go with my gut feeling that this probably works better than before, although I think there are still uncovered corner cases. More tests could maybe reveal that but on the other hand, if it is better than before then what's the problem :-P
+1 from me.

I'll merge it in.


Token Theme

First time doing this. Or using GitHub haha. Feel free to message me in the Discord chat if something is wrong. I would be happy to fix it! I plan to add other systems as well. Appreciate all the hard work done for this app. Makes my RP3 far more functional. Just wanted to share how I have mine setup.
Cheers!

First time doing this. Or using GitHub haha. Feel free to message me in the Discord chat if something is wrong. I would be happy to fix it! I plan to add other systems as well. Appreciate all the hard work done for this app. Makes my RP3 far more functional. Just wanted to share how I have mine setup.
Cheers!

Hello very classy, did you add 2 themes? I see retrograde and token.


Getting TextEcoder is not defined error for NextJs multi-page Application

Describe the issue:
I have been trying to integrate the Asgardeo for NextJs multi-page application.  It compiled without any errors. Getting the following error when loading the application.
TextEcoder is not defined
How to reproduce:

Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

asgardeo-auth-react-sdk was supposed to use with SPAs. Hence, certain operations would need the code to be run on the browser.
As far as i see, you might have to use the https://github.com/asgardeo/asgardeo-auth-js-sdk and create a util to access the SDK functions. There you can check if the code is running on the browser and only then run the SDK code.
ex: utils/asgardeo.js
import { AsgardeoAuthClient } from "@asgardeo/auth-js";

const store = <read this https://github.com/asgardeo/asgardeo-auth-js-sdk#arguments>;

const auth = new AsgardeoAuthClient(store);

const isBrowser = typeof window !== "undefined"

const auth = isBrowser
    ? auth.initialize({
        signInRedirectURL: "http://localhost:3000/sign-in",
        signOutRedirectURL: "http://localhost:3000/dashboard",
        clientID: "client ID",
        serverOrigin: "https://api.asgardeo.io/t/<org_name>"
    })
    : {}

export const isAuthenticated = () => {

    if (!isBrowser) {
        return;
    }

    await auth.isAuthenticated();
}

export const getAuthCode = () => {

    if (!isBrowser) {
        return
    }

    auth.getAuthorizationURL(config).then((url)=>{
        window.location.href = url;
    })
    .catch((error)=>{
        console.error(error);
    });
}

export const getToken = (authorizationCode, sessionState) => {

    if (!isBrowser) {
        return
    }

    auth.requestAccessToken(authorizationCode, sessionState)
        .then((response) => {
            return response;
    })
    .catch((error) => {
        console.error(error);
    });
}

ex: login.jsx
import React from "react"
import { getToken } from<EMAIL_ADDRESS>
const LoginPage = () => {

  useEffect(() => {
       getToken
           .then((response) => {
               // handle reponse
           })
           .catch((error) => {
               // handle error
           });
  }, [ // watch for auth code and session state params ]);

  return
Authenticating. Please wait...

}

export default LoginPage;

ex: pages/home.js
import React from "react"
import { isAuthenticated,  getAuthCode } from<EMAIL_ADDRESS>
const HomePage = () => {

    if (!isAuthenticated()) {
        getAuthCode();
        return
Redirecting to login page...

    }

    return (
        <Router>
            <Home path="/home/">
        </Router>
    )
}

export default HomePage;

asgardeo-auth-react-sdk was supposed to use with SPAs. Hence, certain operations would need the code to be run on the browser.
As far as i see, you might have to use the https://github.com/asgardeo/asgardeo-auth-js-sdk and create a util to access the SDK functions. There you can check if the code is running on the browser and only then run the SDK code then.
@suganyasuven Could you try out the following and see if it works.
NOTE: Untested Code
ex: utils/asgardeo.js
import { AsgardeoAuthClient } from "@asgardeo/auth-js";

const store = <read this https://github.com/asgardeo/asgardeo-auth-js-sdk#arguments>;

const auth = new AsgardeoAuthClient(store);

const isBrowser = typeof window !== "undefined"

const auth = isBrowser
    ? auth.initialize({
        signInRedirectURL: "http://localhost:3000/sign-in",
        signOutRedirectURL: "http://localhost:3000/dashboard",
        clientID: "client ID",
        serverOrigin: "https://api.asgardeo.io/t/<org_name>"
    })
    : {}

export const isAuthenticated = () => {

    if (!isBrowser) {
        return;
    }

    await auth.isAuthenticated();
}

export const getAuthCode = () => {

    if (!isBrowser) {
        return
    }

    auth.getAuthorizationURL(config).then((url)=>{
        window.location.href = url;
    })
    .catch((error)=>{
        console.error(error);
    });
}

export const getToken = (authorizationCode, sessionState) => {

    if (!isBrowser) {
        return
    }

    auth.requestAccessToken(authorizationCode, sessionState)
        .then((response) => {
            return response;
    })
    .catch((error) => {
        console.error(error);
    });
}

ex: login.jsx
import React from "react"
import { getToken } from<EMAIL_ADDRESS>
const LoginPage = () => {

  useEffect(() => {
       getToken
           .then((response) => {
               // handle reponse
           })
           .catch((error) => {
               // handle error
           });
  }, [ // watch for auth code and session state params ]);

  return
Authenticating. Please wait...

}

export default LoginPage;

ex: pages/home.js
import React from "react"
import { isAuthenticated,  getAuthCode } from<EMAIL_ADDRESS>
const HomePage = () => {

    if (!isAuthenticated()) {
        getAuthCode();
        return
Redirecting to login page...

    }

    return (
        <Router>
            <Home path="/home/">
        </Router>
    )
}

export default HomePage;

Getting the same issue.

Example of where this fails
https://github.com/LSFLK/MedicinesforLK/runs/7485585913?check_suite_focus=true
import { AsgardeoSPAClient } from "@asgardeo/auth-spa";

This import is throwing the error for us.

Bumping this issue. We are running into a similar issue with the error Crypto is undefined. This throws when trying to run jest tests.
Is there a workaround for this? Thanks!

Hi Nipuna,
Are you still experiencing the error mentioned? If so, please feel free to open a new issue with additional details. This will help us investigate and address the problem effectively.
Closing the current issue for now as OP seems to have got the problem solved.


CSS syntax error in tag 'style amp-custom'

BUG
I'm using the theme hexo-theme-suka and I was added the generator_amp part to the theme's file  (themes/suka/layout/_partial/head/index.ejs)'s first line
But when I was trying to test my blog via https://validator.ampproject.org , I got this error
- CSS syntax error in tag 'style amp-custom' - incomplete declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 290

- CSS syntax error in tag 'style amp-custom' - invalid declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 309

- CSS syntax error in tag 'style amp-custom' - incomplete declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 317

- CSS syntax error in tag 'style amp-custom' - invalid declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 337

- CSS syntax error in tag 'style amp-custom' - incomplete declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 378

- CSS syntax error in tag 'style amp-custom' - invalid declaration.AUTHOR_STYLESHEET_PROBLEM line 1744, column 392

This is the error part.
#hexo-amp-id-1{color:#DB4D6D;}#hexo-amp-id-2{color:#DB4D6D;}#hexo-amp-id-3{color:#DB4D6D;}#hexo-amp-id-4{color:#DB4D6D;}#hexo-amp-id-5{color:#DB4D6D;}#hexo-amp-id-6{background-color:black;color:white;text-decoration:none;padding:4px 6px;font-family:-apple-system, BlinkMacSystemFont, "San Francisco", "Helvetica Neue", Helvetica, Ubuntu, Roboto, Noto, "Segoe UI", Arial, sans-serif;font-size:12px;font-weight:bold;line-height:1.2;display:inline-block;border-radius:3px}#hexo-amp-id-7{display:inline-block;padding:2px 3px}#hexo-amp-id-8{height:12px;width:auto;position:relative;vertical-align:middle;top:-2px;fill:white}#hexo-amp-id-9{display:inline-block;padding:2px 3px}

the problem is  I could't find how is this part comes from, and how to fix it
(exclude the first minus sign)
- "San Francisco", "Helvetica Neue", Helvetica, Ubuntu, Roboto, Noto, "Segoe UI&quot

the is Example HTML file to this full page
Environment Info
OS version

OSX 10.14

Node version(node -v)
v12.11.1

Your site _config.yml
generator_amp:
  templateDir:  amp-template
  assetDistDir: amp-dist
  logo:
    path:   sample/sample-logo.png
    width:  600
    height: 60
  substituteTitleImage:
    path:   sample/sample-substituteTitleImage.png
    width:  1024
    height: 800
  warningLog: true   # To display warning, please set true.
  generateAmpPath: amp/archives/:abbrlink/

Plugin version(npm ls --depth 0)
<EMAIL_ADDRESS>/Users/edisonjwa/Documents/git/Hexo-CI
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

After testing only if there exist headers this part will comes out
if post with out context
https://gist.github.com/EdisonJwa/81ac75c2fc9298b4ea119b7a20b044f6

Are fonts used in the content embedded in your articles, such as iframes ?
The font specification may not be converted successfully with the hexa-generator-amp plug-in, and ; may have changed to &quot.

Are fonts used in the content embedded in your articles, such as iframes ? Also If you delete an iframe or embedded CSS, will the error disappear ?
The font specification may not be converted successfully with the hexa-generator-amp plug-in, and ; may have changed to &quot.

Yes that's it. So it's there any way to fix it?

@EdisonJwa
I visited your site.
https://www.wevg.org/archives/pair-locking-your-iphone/
The source code for the button is probably the source of the problem.

In the source code, double quotes are the reference characters.  Please check if the reference character " is in the template or in the article, and replace code to the ".  That will solve it.

Although it is possible to deal with bugs as a plug-in, this is a rare case.


Minor Issue -- Atlas.dll being put in Assets/Meatkit/Managed rather than Assets/Managed

With Meatkit v2 launching as official release, the Atlas UnityPackage is now a bit outdated. The user will need to move the dll manually from the original managed folder to the new one, but with no errors in the logs in regards to it, it's easy to miss the issue. The plugin being in this old folder location results in maps being unable to be built due to the "missing Atlas plugin" error.

Interesting. I tested with the OtherLoader package and Unity was smart enough to recognize the folder had moved but the Atlas package doesn't show the same behaviour. Not sure why, but I'll get a fix out for it ASAP.


validate specific resources, fragment selectors

see here: https://www.w3.org/TR/annotation-model/#specific-resources

fixed by https://github.com/falafeljan/validate-web-annotation/commit/a26d821dd1df0d0cb350af30ca31854e4363acf8, which adds preliminary support for validating specific resources. lacks validation for specific official selectors (CSS selector, SVG selector, etc.).


Removed const from OAHashMap iterator value

Removed const from OAHashMap iterator value to allows to mutate the value while iterating over it.

Thanks!

Cherry-picked for 3.2.2.


[WFCORE-5266] Upgrade WildFly OpenSSL to 2.1.3.Final

https://issues.redhat.com/browse/WFCORE-5266
https://github.com/wildfly-security/wildfly-openssl/compare/2.1.2.Final...2.1.3.Final
    Release Notes - WildFly OpenSSL - Version 2.1.3.Final

        Bug

[WFSSL-63] -         Unable to build WildFly SSL on Fedora 33

[WFSSL-65] -         Issues with wildfly openssl and client certificates when used on the client side with Jetty

        Task

[WFSSL-66] -         Add a new GitHub workflow to trigger CI for pull requests

[WFSSL-67] -         Refactor some tests in ClientSessionTestBase to make use of the EchoRunnable test class and ensure that tests wait for threads to finish to avoid hangs

[WFSSL-68] -         Release WildFly OpenSSL 2.1.3.Final

@fjuma thanks


Bugfix/gpio control installscript

Hi
I installed a Raspbian lite system and could reproduce the issue with the gpio_control install script.
The issue is caused by a strange behaviour when the script is executed.
It asks for the root-user password instead of using the sudoer password of the 'pi' user. As the root password in not set, it cannot authenticate.
I changed the script in such a way that one execute it now using sudo ./install.sh . It required some additional changes to the script, as execution as sudo results in 'wrong' ownerships and pathes. Using the variable SUDO_USER I could find a way how to circumvent the issues.

Thanks for the PR, I think this should help many users.


NLogWrapper methods with activityid

I was hoping to use ActivityID when logging each of my application. I am aggregating all my log messages in logentries or loggy. Having activityid will make is easier to search for all the messages with a specific activity id.
NLogWrapper does define methods with activityid but most of them are not implemented.
It will be helpful to have at least one method implemented so it can help folks who are not familiar with NLog.
Is it better to add "ActivityID" as a property for the logEvent.Properties or should we just concatenate the activityid with the message body? I am leaning towards the first option as it will allow me to use a custom layout renders and pass this value separately.
One of the methods is taking in activityId but ignoring it.
This method should either implement the code to pass activityId or throw NotImplementedException as the other methods are doing.
    public void Info(object message, Guid? activityId)
    {
        this._log.Info(message);
    }

Good catch - let me update the wrapper; agree that it's better to add the activity ID as a property to have more structured for stores like loggly.

We've merged in @mabsimms's changes. Please let us know if you find anything else!


TD-82 TD-83 Show positions and make trades

Implemented changes for TD-82 and TD-83.

Everything looks like its working fine. One thing I noticed is that you can have a negative quantity of stock.

Im not sure if this is right, otherwise the trades execute correctly as I can see them on Alpaca as well

Everything looks like its working fine. One thing I noticed is that you can have a negative quantity of stock.

Im not sure if this is right, otherwise the trades execute correctly as I can see them on Alpaca as well

That's intended behavior.  It's common to represent shorting a stock as negative quantity


⚠ ClamAV has degraded performance

In 8e735a8, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 483 ms

Resolved: ClamAV performance has improved in b9237e2.


Script will not install on Firefox (106.0.4) with Greasemonkey (4.11)

Generates the following error:
User script download failed
Ignoring @match pattern http*://e-hentai.org/* because: Error: @match: Invalid protocol (http*:) specified.

Should now be fixed with update https://github.com/Meldo-Megimi/EH-Page-Scrobbler/commit/561d657fe4c07163154dc1aef8161ad932aef58d

Yes, it can install now. Thanks.


Rancher agent  does not use proxy environment in callback to  rancher

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Import existing cluster into Rancher - with a proxy between that cluster and Rancher. Add to the agent yaml the required HTTP_PROXY, HTTPS_PROXY, NO_PROXY envs
Expected : Rancher cluster/node can contact Rancher and import is successful
Result:
Rancher agent wss calls fail, log
time="2019-12-19T09:39:08Z" level=info msg="Connecting to wss://rancher.foobar.com with token $token"
time="2019-12-19T09:39:08Z" level=info msg="Connecting to proxy" url="wss://rancher.foobar.com/v3/connect/register"
time="2019-12-19T09:39:18Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp :443: i/o timeout"
time="2019-12-19T09:39:18Z" level=error msg="Remotedialer proxy error" error="dial tcp $IP_OF_RANCHER:443: i/o timeout"
Other details that may be helpful:
This is the same issue as rancher/rancher#24681 and rancher/rancher#22750 , sorry for opening a new one, but those are probably not clear enough.
The problem is in remotedialer/client.go line 26
dialer = &websocket.Dialer{HandshakeTimeout:HandshakeTimeOut}
should read instead
dialer = &websocket.Dialer{HandshakeTimeout:HandshakeTimeOut,Proxy: http.ProxyFromEnvironment}
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
2.3.3 single install

gz#13523

Re opening this issue for validation.

rancher/rancher:v2.3-head
rancher/rancher:master-head

Created Rancher behind proxy
Created nodedriver ec2 cluster
Created imported cluster -- adding proxy vars to agent YAMLs before importing.
Rancher server, nodedriver cluster, and imported cluster are all using the proxy, with traffic seen crossing the proxy through logs.

rancher/rancher:v2.3-head 6eecc2c8b
Re-validated this issue w/ the following scenario:

Rancher not behind proxy
Get import yaml from registration command
Modify yaml to include proxy vars for both agents:

- name: HTTP_PROXY
  value: "url:port"
- name: HTTPS_PROXY
  value: "url:port"
- name: NO_PROXY
  value: "localhost,<IP_ADDRESS>,<IP_ADDRESS>"

Cluster registers w/ traffic going through proxy
Deployed workload in imported cluster

https://github.com/rancher/docs/issues/2286

This bug also still exists in the latest release 2.4.3

It appears that this issue was only partially fixed:
The agent now uses the proxy environment variables during the initial websocket connection but then Rancher re-applies the agent YAML and the environment variables get lost : https://github.com/rancher/rancher/issues/25412

Using this issue to track agent not respecting proxy env vars, closing https://github.com/rancher/rancher/issues/25412
gz#13333

Using this issue to track agent not respecting proxy env vars, closing https://github.com/rancher/rancher/issues/25412
gz#13333

Testing is dependent on UI (#31023), but backend is complete.

currently blocked by https://github.com/rancher/rancher/issues/31258 (unable to test backend)

tested the backend, and is still failing to properly deploy downstream cluster behind proxy
Steps to reproduce (least amount of steps as possible):

deploy rancher v2.5-head (3e96d7f)
deploy a downstream cluster
update agentEnvVars using v3 api (I set proxy settings HTTP_PROXY, HTTPS_PROXY, NO_PROXY

Result:

this cluster and any subsequent clusters will have an error related to spec.template.spec.containers[0].env
API is clearing the agentEnvVars set, and resetting with an empty name and the schema type

@slickwarren The correct format for an envVar is as follows, and agentEnvVars can be successfully set via the API in this format in my testing on v2.5-head (03b8153): {"name":"HTTP_PROXY","value":"http://<IP_ADDRESS>:80"}
However, these do not propagate to the imported cluster cluster-agent YAML, due to a variable naming mismatch in
https://github.com/rancher/rancher/pull/31024/commits/cd7f89a449c9c8678eaf8bc3c35d9031139740ff These are passed to the template as AgentEnvVars but the template references AgentEnvVar

@axeal About the variable naming mismatch, I fixed it later in #31124, which was tested in v2.5-head for issue https://github.com/rancher/rancher/issues/31126.  Do you still see the issue?

@kinarashah I just tested again with v2.5-head (96dc206) and observe the agentEnvVars are still not propogated to the cattle-cluster-agent in the registration YAML.
Steps to reproduce (least amount of steps as possible):

Deploy a Rancher v2.5-head (96dc206) instance
Create an imported cluster
Edit imported cluster via API to add an agentEnvVars {"name":"HTTP_PROXY","value":"http://<IP_ADDRESS>:80"}
View registration YAML for the imported cluster

Result:

No HTTP_PROXY env variable present on the cluster-register container of the cluster-agent Deployment.

I am now able to use proxy environment correctly (see repro details from this ticket) on v2.5-head( 96dc206)  and master-head (dbf1838).  I did notice that, on 2.5-head, the yaml from the registration command did not include the env vars set through v3 api, so i manually added them. However on master-head, they were there but missing " around the values (all other env values had these).  I added them to each value before running kubectl apply -f <registration>.yaml
cc @kinarashah not sure if this is expected or not, but not blocking this ticket since the current process isn't expecting the manually added values to be in the downloaded yaml.

reopening: the missing quotes in the env vars was validated to work, but we do expect these to be added automatically to the yaml if they exist on the rancher server. Reopening because the build for 2.5-head failed, will validate that they are added as soon as the build is ready

verified that running the registration cmd as-is (after adding agentEnvVars via v3 api) is working as well. The yaml now includes those variables

tested on  master-head (dbf1838) and 2.5-head (b4be2b22879d85f268dff655206b8e515d803142).

Edit imported cluster via API to add an agentEnvVars {"name":"HTTP_PROXY","value":"http://<IP_ADDRESS>:80"}

How do you do this step?

verified that running the registration cmd as-is (after adding agentEnvVars via v3 api) is working as well. The yaml now includes those variables   tested on master-head (dbf1838) and 2.5-head (b4be2b2).

Hi - can you attach the whole yaml file please?


Ruby unicorn web server is completely broken on WSL

To repro:
install ruby
gem install unicorn

create a rackup.ru file with the contents:
class HelloWorld
  def call(env)
    [200, {"Content-Type" => "text/html"}, ["Hello World!"]]
  end
end

run HelloWorld.new

run unicorn
This is due to socket options, also reported here: https://github.com/Microsoft/WSL/issues/1982#issuecomment-412730481 and<EMAIL_ADDRESS>

per @bitcrazed ping @tara-raj

This is due to socket options, also reported here: #1982 (comment)

No strace or rest or ISSUE_TEMPLATE.md but I'll take your word for it.


chore(release): v1.0.0 🎉

:robot: I have created a release beep boop
1.0.0 (2023-07-18)
Features

init: init based on whodis-react-storage-browser (c865419)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/whodisio/whodis-react-storage-native/releases/tag/v1.0.0 :sunflower:


ModuleNotFoundError installing package with setuptools_scm

Describe the bug

When I try to install cutlet I get this error:
 ERROR: Command errored out with exit status 1:
    command: /tmp/tmpw195j32y/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-db8tw4n5/cutlet/setup.py'"'"'; __file__='"'"'/tmp/pip-install-db8tw4n5/cutlet/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-rwdkx6tl
        cwd: /tmp/pip-install-db8tw4n5/cutlet/
   Complete output (5 lines):
   Traceback (most recent call last):
     File "<string>", line 1, in <module>
     File "/tmp/pip-install-db8tw4n5/cutlet/setup.py", line 7, in <module>
       import setuptools_scm
   ModuleNotFoundError: No module named 'setuptools_scm'
   ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

How to reproduce

This should reproduce the error:
pipx install cutlet

I'm on Linux but I don't think platform is relevant so I'll omit verbose output, let me know if it would actually help.
Expected behavior

cutlet should have installed without issue.

I maintain this package, so I'd like to make sure it works. I'm not sure if I'm doing something wrong and should change it or if this is an issue with pipx.
To clarify why I'm importing setuptools_scm, if it's not present the package is installed as version 0.0.0, which can cause issues. Importing makes sure that the package is present rather than building a package with a bogus version. setuptools-scm is specified in setup_requires, so I'm not sure if there's something else I should do here.

One workaround would be to use PEP 517, i.e. adding a pyproject.toml containing the following:
[build-system]
requires = ["setuptools", "wheel"]
build-backend = "setuptools.build_meta"

This will make pipx (the pip process underneath, to be exact) correctly set up a build environment that contains setuptools-scm. You can read more about the file here.

Great, thank you, that makes sense. I'll try adding it and report back.

Hm, using the above (plus a little extra) I was able to get setup working, but then pipx doesn't find the package script that's specified in scripts in setup.py. Any idea where I can specify a script? I do not want to specify an entry point, I already have a working command line script.
I tried looking for an explanation of that but it's hard to find guides that aren't dependent on poetry...

Found the part of the docs where it makes it clear that I need to use entry_points.
https://pipxproject.github.io/pipx/how-pipx-works/#developing-for-pipx
This is kind of frustrating if I already have working scripts, though luckily in this case it wasn't a big change. Thanks for the quick reply on the initial report.

scripts are platform-specific and don’t work well on Windows, so it’s better to use it instead anyway 🙂

fyi https://github.com/iterative/shtab uses setuptools_scm without needing pyproject.toml


ZR300 Data Sync Question

Hi,
I am working with the ZR300 camera and using this ROS driver and I have a question about the data synchronization.
Specifically I am interested in using the color, depth and IMU sensors.
Are the timestamps from the ROS messages of these sensors recorded with respect to the same clock on the device? I am referring to the timestamps reported in the header fields of the topics:
/camera/color/image_raw
/camera/depth/image_raw
/camera/imu/data_raw
Otherwise, how is the synchronization done?
Thanks

Hello @baloothebear,
The sensors are synchronized to the same reference clock.  See the ZR300 datasheet for more information.
Regards,
Jesus
Intel Customer Support

[Please Ignore - RealSense system comment]


fix headers setter

This needs to be merged in master!

I created this ...
https://github.com/nerzh/Action-Cable-Swift


Revert "Make is_typescript_5_or_greater config_setting public"

Reverts aspect-build/rules_ts#389
CLA needs to be signed before merge.

Nvm. I just signed CLA. Required company approval.


Settings Option

Hi
I love to work on the settings page, pls assign this to me

can i work on this one?

Assigned to you make sure you follow code conventions and quality of code 🙃

I would recommend the contributor of this issue to fetch upstream and resolve conflicts before creating a new Pull Request.

hi @pranjalkatiyar  you have 5 more days then this issue will be assigned to someone else

Oky i m working on it
On Tue, Mar 15, 2022, 10:48 AM LakhanKumawat ᵖ⁺ @.***>
wrote:

hi @pranjalkatiyar https://github.com/pranjalkatiyar you have 5 more
days then this issue will be assigned to someone else
—
Reply to this email directly, view it on GitHub
https://github.com/Lakhankumawat/smart-home-app/issues/14#issuecomment-1067574210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKIVMA4ZM5WLXJAJLLQPC3VAAMS5ANCNFSM5PUIZ72Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

You are overtime with your issue , 1 more day and then it will be assigned to someone else .

/assign

/assign


Use pytest and parametrization to reorganize tests.

Prior to this we had tests that just ran the same method over and over again with different inputs. That made the true test count wildly inaccurate, and more importantly, made it more difficult to see which input was causing any particular test failure since one failed test could have had many individual assertions in it. This cleans things up and fixes #3

:+1:

ok :+1:


better error checking for uploading on top of a file (trying to treat it as a directory)

If I upload a file:
% skicka upload foo /foo

And then do this silly thing:
% skicka upload foo /foo/foo

(Trying to treat /foo as a folder rather than a file), skicka goes into exponential backoff mode, retrying a bunch of files before failing: "2014/12/02 10:12:29 exponential backoff: slept for error googleapi: Error 400: Parent is not a folder")
We should notice earlier on if the target "folder" is actually a regular file on Drive and issue a reasonable error message in this case.

Likely related, doing
% skicka upload dir /file

where dir is a local directory and /file is an existing file on Drive also goes into exponential backoff and retry mode...


TypeError When using encode

When I try to encode my file with this code:
from youbit import Encoder
with Encoder('C:/myfile.txt') as encoder:
    path = encoder.encode('C:/mydirectory/')  # Saves output in 'C:/mydirectory'. Defaults to current working directory.
    print(path)

which is one of the examples mentioned, I get this error:
TypeError: unsupported operand type(s) for /: 'str' and 'str'
Solution is in line 198 in "yb.py"
You need to change
output = directory / ("YOUBIT-" + self.metadata["filename"])
to:
output = directory +"/"+ ("YOUBIT-" + self.metadata["filename"])

Fixed in f1daab7.
Note that this change is not yet on PyPi.


Not all commands function as expected in remote powershell

For example: Get-ExchangeCertificate will not return the services assigned to the certificates, or any detailed information about the certificate.
In comparison, running the same command in the Exchange Management Shell will return the services.
The documentation should be updated to reflect which commandlets are not supported, or have limited support in a remote powershell session as this affects runinng code in environments such as Visual Code, or the ISE.  There should not be unexpected behaviour by running the same commandlet in a different session.   This should be computer science, not computer science fiction.

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

ID: 36b57b66-2364-0e9d-e627-5eeb77238675
Version Independent ID: 78fd7932-06f9-37c7-8928-250b3884d89e
Content: Connect to Exchange servers using remote PowerShell
Content Source: exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md
Service: exchange-powershell
Product: exchange-server-itpro
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

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


Rewrite and optimize EvalCtx::addNulls method

This change rewrites the EvalCtx::addNulls() implementation to ensure
all cases are covered for generating a valid output vector.
Additionally adds an optimization where it wraps complex vectors
in a dictionary instead of copying them for cases where they are
not mutable or need to be resize.
Test Plan:
Verified that all tests pass

a bunch of unit test failures are due to the expectation that the output would be flat instead of a dictionary encoded. Will fix all and send an update soon

Fixed unit tests: modified tests that relied on the output to be a non-encoded (dictionary or constant) complex vector.


Having trouble with Keypad control using JSON

PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
I'm trying to set the time limited access for keypad permissions, however, I get the following results:
v9.0 - it never seems to work at all, commandResultJson reports configNotReady
v9.01 - I can change all the parameters I try apart from allowedUntil, commandResultJson reports invalidAllowedUntil
Example JSON used :
{ "action": "add", "code": "589472", "name": "Test", "timeLimited": "1", "allowedFrom": "2024-04-12 10:00:00", "allowedUntil": "2034-04-12 10:00:00", "allowedWeekdays": [ "wed", "thu", "fri" ], "allowedFromTime": "08:00", "allowedUntilTime": "16:00" }
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

TO REPRODUCE
Steps to reproduce the behavior:
Set json topics as above example and check the time limited access settings on the lock
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
allowedUntil time is correctly set
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)

Already fixed in master and discussed earlier (among others) in https://github.com/technyon/nuki_hub/issues/469 and https://github.com/technyon/nuki_hub/pull/502.
Update to 9.02 beta or wait for release.

Apologies, my search criteria must have been too narrowly defined. Thanks for the update


Add TechCity Blog

This is a blog on the topic of top tech cities of India and how India is becoming a giant hub for international companies. If you wanna get a job in tech fields, these cities provide the best value in the entire India.

should I make another pull request after making changes?

No you don't need to make another PR just do changes what I said and new changes automatically reflects over here.

@kishanrajput23 I hope everything is okay with my blog now, please let me know if you find anything to change..

Please approve the PR otherwise..

@kishanrajput23 Please check now

@kishanrajput23 I worked on it and I think it's working fine, Please let me know if any changes required

Thanks for merging my PR..
But why it isn't showing here?


Skip TestExecStartFails on windows

While #16738 and #16598 are fixed 👻, skip this test on windows :sweat: :cold_sweat:.
We should not get used to merge PRs with red builds (or at some point we might miss some errors). I don't really like doing a skip this test, so feel free to close it if you don't agree on that :stuck_out_tongue_closed_eyes:.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Is someone working on fixing those tests already? I'm ok with skipping them, just worried that we forget to fix and re-enable them

Is someone working on fixing those tests already? I'm ok with skipping them, just worried that we forget to fix and re-enable them

Yeah completely agree but… 😖 😷

I'll make that a "lgtm" from me; merging with red builds isn't good either.

I'm looking into what caused this to start failing.

@cpuguy83 cool, guess I can close this one then ? :sweat_smile:

We'll see.

merging sick of the crap can we open an issue about this tho

LGTM

@jfrazelle there is 2 issues open on it :wink:

oh perfect should we add a third.. idk
On Tue, Oct 6, 2015 at 1:56 PM, Vincent Demeester<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle there is 2 issues open on it [image:
:wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16752#issuecomment-145997611.

(im kidding)
On Tue, Oct 6, 2015 at 1:57 PM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

oh perfect should we add a third.. idk
On Tue, Oct 6, 2015 at 1:56 PM, Vincent Demeester <
<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle there is 2 issues open on it [image:
:wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16752#issuecomment-145997611.

(pllease dont add a third)
On Tue, Oct 6, 2015 at 1:57 PM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

(im kidding)
On Tue, Oct 6, 2015 at 1:57 PM, Jessie Frazelle<EMAIL_ADDRESS>wrote:

oh perfect should we add a third.. idk
On Tue, Oct 6, 2015 at 1:56 PM, Vincent Demeester <
<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle there is 2 issues open on it [image:
:wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16752#issuecomment-145997611.

oh shoot, I added a third


values: remove unnecessary cast

can't remove it, enum types are a bit janky. mypy doesn't know if it wants to enforce the base enum type, or the union of all the brand enum classes. Says it expects list[Platforms] which is the enum base, but this passes mypy perfectly fine:
TEST: dict[str, Platform] = {'hi': HYUNDAI.GENESIS_G70, 'test': TOYOTA.TOYOTA_COROLLA}


If screen locked with a timer (set up in the app), bring user back to the screen where he was

Currently, if app locked with timer, when user opens it again he sees main screen. Would be better to open the screen, where user was before screen was locked.

It is not possible to unlock the screen with a fingerprint after locking the screen.
video_2019-09-24_11-20-19.zip


Updating SlideGroup visibility management to support multiple Slide additions/removals

Summary
The SlideGroup hides un-presented Slides to prevent tabbing/accessibility issues. When the SlideGroup is animated, it synchronizes the hiding and showing with the presentation animations to keep things looking nice.
The current implementation assumes that the animations will complete before other content is added/removed, but that may not always be the case. In some cases, Slides are not being revealed appropriately, causing the SlideGroup to appear blank with no recourse for correction.
I updated the visibility logic to show/hide Slides based on the currently presenting/removing component and support closely repeated updates

Functional verification complete.  No new issues identified.
IE 11- backwards navigation is choppy but I confirmed that this is consistent with the previous code.


fork_schedule API endpoint wrong path

Teku implemented the fork_schedule endpoint at /eth/v1/config/spec/fork_schedule however its path in the API is /eth/v1/config/fork_schedule i.e. without the /spec directory.

sorry about that! I've got a fix for that path building and up for approval now.


Document the job.delayGC operator setting

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

Project coverage is 78.12%. Comparing base (fa23a9b) to head (1d71c52).
Report is 40 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #791      +/-   ##
==========================================
- Coverage   79.09%   78.12%   -0.97%
==========================================
  Files          51       55       +4
  Lines        5109     4078    -1031
==========================================
- Hits         4041     3186     -855
+ Misses        882      697     -185
- Partials      186      195       +9

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

/lgtm


Added NCache Live in Customers & Partners section in README.md

NCache Live by Alachisoft is a web application which lets user use NCache without installing and setting up it in their environment. There is a pre-configured environment present for user. All he need to do is to access the website and start using NCache API. We have used Try .NET to make execution of code snippets and editing them possible.

I have done the PR and waiting for response or approval. The only change I have made is in Customers and Partners section of README.md file.

@LadyNaggaga Thank you for your response. I have made the changes as per your requirements. Please review them.

I just wanted to follow up on this PR. I have made the required changes and waiting for this PR to get reviewed and merged so that others can see the power of Try .NET with the help of NCache Live.

Thanks, @Aussama-Ul-Islam!


Line breaks on Windows

In Windows, the log file entries are all on one line. I assume it doesn't have line breaks that are readable in Windows? Or is there another option to set?

I assume it's this line: https://github.com/darrylwest/simple-node-logger/blob/master/lib/FileAppender.js#L40
For Notepad support (Windows standard), this should be \r\n.

fixed with latest version...


Crash app update to react native 0.74.1

When I use the component in my application with React Native 0.72.0, it works perfectly. However, after updating to React Native 0.74.1, the view where I use the component crashes without any error message.

same here, only crashes in production


Ticker Functions Only Fired Once

Currently the way add_ticker is implemented causes all ticker events to be treated as one shots and not execute repeatedly. The function added to the delegate is expected to return either true or false. If false then the function will not be called again. Is it possible to address this issue with the way add_ticker is currently implemented?

I think it will be enough to manage the return value here: https://github.com/20tab/UnrealEnginePython/blob/master/Source/UnrealEnginePython/Public/PythonDelegate.cpp#L22
I will work on it tomorrow

Ok, i investigated it. Basically we need a way to instruct UPythonDelegate (before being mapped to a ticker) to respect a specific signature (and this is easy), but the UPythonDelegate::ProcessEvent function must be extended to support a return value

Now add_ticker() expects a callable taing a deltatime as argument and returning a boolean.
add_ticker() returns a FDelegateHandle python object that you can pass to the new ue.remove_ticker() to destroy ticker. Let me know how it works for you


Do not proxy images

closes #336

Coverage increased (+0.03%) to 69.549% when pulling 4c1383239a4f74f534cc69bca27036d6110899e4 on no-proxy-getmap into 9754ff3a3319a24869131c9d99e471728724ab17 on master.


[Feature Request] Retrieve SoC

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
To decide whether or not to start or stop charging, it would be helpful to know the state of charge (SoC). If I am not mistaken, the chargingpoint should technically be able to retrieve this information from the electric vehicle.
Describe the solution you'd like
Provide SoC sensor
Describe alternatives you've considered
No alternative in mind
Additional context
Part of a bigger picture: dynamic charging based on a.o. energy prices, PV yield, planned trips

Hi Thijs,
State of Charge of a battery is currently only possible with DC (fast) chargers (at large scale).
There is a protocol available to read the SoC for AC chargers, the ISO-15118 interface.
This has to be implemented both in the charging station as well as the car. A few cars currently have this implemented ,but hardly any charging station is ready for this.
Our new controller is coming out this year, which is ISO-15118 prepared, but it is not yet operational.


1.5 Tracking API usage and other usage like disk space [Optional]

This is useful to Cloud Admin as measuring usage across different instances may
become important to performance management.

Tracking API usage and other usage like disk space (and displaying this in admin
interface)

ckan-multisite has all requests going through a single HTTP router, so the access logs for all the sites can be aggregated or reported on really easily. I've opened a ticket to revisit this when we have some code to show: https://github.com/boxkite/ckan-multisite/issues/4

Great!  We may also want to look at 18F's http://analytics.usa.gov for inspiration.  Since we have full access logs, it doesn't directly apply, but once some instances "graduate" to their own dedicated open data installations, it may still be a way to aggregate high-level analytics.


Bug in version resolution when a transitive dependency is used as a direct dependency

Description:
When a transitive dependency (previous compilation) has become a direct dependency (this compilation), the resolution engine picks the latest minor version from the repos disregarding the version locked in the Dependencies.toml. This affects some unrelated dependencies also to update to the latest minor version which is not expected.
Steps to Reproduce

Create a package with the following imports and build with slbeta3:

import ballerina/http as _;
import ballerina/sql as _;

This will lock the following versions of the dependencies:
sql - 1.0.0
http - 2.0.0

Now import the ballerina/log package (this is already locked in the Dependencies.toml) as a transitive depenency:

import ballerina/http as _;
import ballerina/log as _;
import ballerina/sql as _;

Rebuild the package and check the Dependencies.toml. The sql package version should have updated to 1.2.0
Affected Versions
At least SL beta 6

This is caused due to the following implementation:
https://github.com/ballerina-platform/ballerina-lang/blob/ccdf46753fad4439be95e982c09586fa5a0dc4d3/compiler/ballerina-lang/src/main/java/io/ballerina/projects/internal/ResolutionEngine.java#L172-L185
The packageLocking mode updated at L185 is a reference that is used as the default value for dependencies. So when the condition at L179 evaluates to true for ballerina/log package,the packageLockingMode is updated affecting the rest of the iterations.
AFAIU, creation of packgeLockingMode should be done within the for loop.


Output multiple artifacts per primer, similar to Cutadapt's demultiplexing method

Addition Description
It would be useful to bin reads by primer prior to primer removal. I'd like to separate a single FASTQ-based artifact (containing several different primers) into multiple output artifacts by primer; each output artifact would be characterized by a single primer. This would be helpful for meta-analyses in which sequences with multiple primers/variable regions may be found in a single QIIME artifact.
This is possible with native Cutadapt (as of v4.5) using steps to demultiplex, but not in the QIIME 2 plugin as its inputs are restricted to specific semantic types.
Current Behavior

The QIIME 2 plugin performs a similar function with qiime cutadapt demux (based on adapter sequence), but generates only a single output for demultiplexed sequences. It also requires an input artifact of type MultiplexedSingleEndBarcodeInSequence and does not accept SampleData[Single/PairedEndSequencesWithQuality].
qiime cutadapt trim could technically perform this by running the command once per primer (pair), but that is quite inefficient.

Proposed Behavior

q2-cutadapt would take as input 1) a FASTQ artifact of SampleData[Single/PairedEndSequencesWithQuality], which contains N different primer sequences among its many reads, and 2) a tab-separated metadata file containing the N primer names and corresponding primer sequences.
As output, it would generate N artifacts of SampleData[Single/PairedEndSequencesWithQuality]; each output artifact would contain reads of the same primer sequence. There would also be an output artifact (also SampleData[Single/PairedEndSequencesWithQuality]) of sequences that did not have any of the N primer names.

Questions

Does QIIME 2 allow for variable numbers of output artifacts? I suppose that would be a blocker to implementation.

References

Cutadapt manual, "Demultiplexing"
QIIME 2 docs, qiime cutadapt trim-paired

This is totally possible now with Collection[...] as an output. Is this something you would be interested in working on @lina-kim?

Great to know, thanks @ebolyen! Yes, I would be more than happy to work on it. Is Collection[...] a semantic type found in q2-types / the base QIIME 2 installation? I'm not seeing much documentation for it on first glance.

Perfect, thanks for the resources @gregcaporaso! I'll check them out and get back to you with any questions.


⚠ Bofrost.lu has degraded performance

In 2e8367f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1134 ms

Resolved: Bofrost.lu performance has improved in face9aa.


remove second level logic and use all the categories to build category tree

1. Why is this change necessary?
category will not be complete loaded in the navigation flyout, just first and second level
2. What does this change do, exactly?
remove first, second level logic, load all the categories to build navigation tree
3. Describe each step to reproduce the issue or behaviour.
create a third level category in backend, go to shop frontend, hover over the navigation and the third level category will not be displayed in the flyout
4. Please link to the relevant issues (if any).
https://github.com/shopware/platform/issues/102
https://issues.shopware.com/issues/NEXT-4311
5. Which documentation changes (if any) need to be made because of this PR?
no
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

Hi @ieslei,
thanks for the pull request.
Your changes would solve the problem, but systems with several thousand categories in the storefront would collapse.
By flyout you mean the desktop view of the categories when I mouse over, right?
The offcanvas menu should simply load the category levels via Ajax. The flyout on top of desktop should only show the first two levels.


Fraudulent Transactions Detection

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Fraudulent Transactions Detection
:red_circle: Aim : Develop a model for predicting fraudulent transactions for a financial company and use insights from the model to develop an actionable plan.
:red_circle: Dataset : https://www.kaggle.com/datasets/miznaaroob/fraudulent-transactions-data
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Full name : Tanish Khandelwal
GitHub Profile Link : https://github.com/tknishh
Email ID<EMAIL_ADDRESS>Hey @abhisheks008 , I would really like to contribute on this project.
Please allow me.

Assigned to you @tknishh. Go ahead.

@tknishh updates please.

@abhisheks008 Done with the model, finalizing Readme.md file. Will PR by tonight or tomorrow.

Fair enough, keep posting updates here @tknishh

@abhisheks008 I've created PR please review and please mention if any changes are required.


Support for Multiple Screenshots in One Pass

This pull request supports the ability to create multiple screenshots at consistent intervals, saving time when creating video thumbs for players.
It also addresses a couple of compatibility issues with ffmpeg 2.8.4 and resolves all open specs.

@RLovelett What do you think of the release candidate? I bumped the version to 2.0.0 following semantic versioning, or at least, that was the intent.
If this looks good, I will cut the tag and get set up at rubygems to publish.

I think it's a good start. I think there are still a few others that I'd like to see you merge. They'd make it easier for you to administrate this gem (they help with gem building and releasing and CI stuff) but this seems to be a drop in replacement for my forked gem (with regard to to the ffprobe stuff).


Use lowercased version of path extension

It would solve the problem, that appears if image was saved with  format in upper case

Looks good to me – thank you!


Update dropwizard-forms, ... to 1.3.27

Updates

io.dropwizard:dropwizard-forms
io.dropwizard:dropwizard-testing

from 1.3.26 to 1.3.27.
GitHub Release Notes - Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.dropwizard" } ]

labels: library-update, semver-patch

Codecov Report

Merging #825 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #825   +/-   ##
=======================================
  Coverage   82.80%   82.80%
=======================================
  Files          73       73
  Lines        5404     5404
  Branches      146      146
=======================================
  Hits         4475     4475
  Misses        929      929

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 24ebc25...772c9b6. Read the comment docs.


python312Packages.ltpycld2: normalize pname

Description of changes
part of #245383
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

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

2 packages failed to build:

libretranslate (python311Packages.libretranslate)
libretranslate.dist (python311Packages.libretranslate.dist)

4 packages built:

python311Packages.ltpycld2
python311Packages.ltpycld2.dist
python312Packages.ltpycld2
python312Packages.ltpycld2.dist