WHERE CAN I HIRE THE BEST BITCOIN RECOVERY HIRE  /  ADWARE RECOVERY SPECIALIST

Website info: www.adwarerecoveryspecialist.expert
Telegram info: @ADWARE_RECOVERY_SPECIALIST
WhatsApp info: +1 (571) 541‑2918
At the intersection of technology and finance, the world of cryptocurrency has brought forth innovative possibilities alongside unique challenges. The narrative of a crypto theft nightmare, where $104,000 vanished into the digital abyss, serves as a stark reminder of the vulnerabilities inherent in this realm. Being a victim of cryptocurrency theft is like stepping into a digital horror story - the kind where cybercriminals lurk in the shadows, waiting to strike at your precious assets. In my case, the nightmare came true, and I lost a whopping $104,000 in cryptocurrency. It's enough to make any investor break out in a cold sweat. The initial shock and disbelief upon discovering the theft quickly gave way to a sense of helplessness and vulnerability. The victim faced not only a significant financial loss but also the emotional turmoil that comes with being the target of such a malicious act. Losing $104,000 in cryptocurrency goes beyond just numbers on a screen – it translates to tangible financial repercussions in the real world. The victim not only had to come to terms with the monetary loss but also navigate the emotional rollercoaster that accompanies such a violation of trust. Introducing ADWARE RECOVERY SPECIALIST - a beacon of hope amidst the treacherous realm of cryptocurrency theft. Armed with their unparalleled skills in reclaiming stolen digital assets, they brought a spark of optimism to the desperate victim's situation. As soon as ADWARE RECOVERY SPECIALIST got wind of the stolen cryptocurrency, they leaped into action, unleashing their cutting-edge tools and techniques to hunt down the thieves. With their savvy strategy and fearless dedication, they gave the victim a much-needed lifeline in their quest to reclaim what was rightfully mine. In the realm of cryptocurrency, my saga of the $104,000 theft turned around by ADWARE RECOVERY SPECIALIST stands as a testament to resilience and the power of expert intervention. As the curtains draw on this harrowing ordeal, the echoes of lessons learned reverberate loudly. Moving forward, bolstered by newfound knowledge and a commitment to robust cybersecurity measures, individuals and entities can navigate the digital asset landscape with greater confidence and vigilance. Check out the information above and get in touch with ADWARE RECOVERY SPECIALIST  right now.

 It happens to the best of us – falling into the clutches of those who aim to swindle our hard-earned digital assets. But fear not, for this tale has a twist of redemption that involves a dash of magic and a sprinkle of hope. As the cold sweat of realization trickled down your spine, you uncovered the harsh truth – your ETH had vanished into the digital abyss. Panic sets in as you scramble to figure out what happened and how to retrieve your precious crypto before it's too late. In a frenzy, you start Googling every possible solution, from shouting at your computer screen to trying to reverse the irreversible. It's a wild ride of emotions mixed with a sliver of hope that maybe, just maybe, there's a way to undo this crypto calamity. Digital Web Recovery offers some hope in the middle of the mayhem. This service is like a lifeline to people stuck in a sea of misplaced money, a beacon in the stormy sea of cryptocurrency scammers. With newfound optimism, you reach out to Digital Web Recovery, hoping against hope that they can work their magic and help you reclaim what is rightfully yours. The initial contact is like a virtual handshake, a digital pact that signals the beginning of your journey to reclaim your lost ETH. Digital Web Recovery unveils the secrets of their mystical arsenal, offering a range of services designed to navigate the treacherous waters of crypto scams. From their bag of tricks, they pull out tools and techniques to help you claw back your lost funds. The path to redemption is paved with diligence and expertise as Digital Web Recovery guides you through the intricate dance of fund recovery. website https://digitalwebrecovery.com/ With each step, you inch closer to the finish line, where your lost ETH awaits its triumphant return to your digital wallet. Tell Digital web recovery your story and get the help you need by dialing: Zohomail<EMAIL_ADDRESS>Telegram user; @digitalwebrecovery

As the world of BTC investments continues to evolve, it's crucial for regulators to step in and implement measures to protect investors. Embracing regulatory frameworks that hold scammers accountable and provide safeguards for investors can help create a more secure environment. By pushing for transparency, accountability, and investor protection, we can make BTC investments safer for everyone. Education is empowering when it comes to navigating the complexities of BTC investments. It's important to continuously educate yourself about cryptocurrencies, blockchain technology, and investment strategies. Seeking professional advice from trusted financial experts or recovery services like Digital Funds Recovery Agency can also provide valuable insights and guidance, giving you a better chance at making informed decisions and avoiding scams. When I first reached out to Digital Funds Recovery after losing a significant amount of money to a BTC investment scam, I wasn't sure what to expect. However, their initial consultation and assessment quickly put my mind at ease. Their team of experts took the time to understand my situation and gather all the necessary information to formulate a recovery plan. One of the most crucial steps in the recovery process was tracing and identifying the scammers who had defrauded me. This is where Digital Funds Recovery Agency truly excelled. Using their cutting-edge technology and extensive network, they were able to track down the individuals behind the scam and uncover important information that would later be instrumental in the recovery efforts. Once the scammers were identified, Digital Funds Recovery swiftly devised a legal framework and recovery strategies to maximize the chances of recouping my lost funds. Their team of legal experts worked tirelessly to navigate the complex world of crypto scams and ensure that all necessary legal actions were taken. From filing complaints with regulatory authorities to pursuing litigation against the scammers, Digital Funds Recovery left no stone unturned in their pursuit of justice. Through my harrowing experience, I learned the importance of conducting thorough research and due diligence before making any investment decisions. It's crucial to verify the credibility of the investment opportunity, check the background of the individuals or companies involved, and seek independent opinions from trusted sources. Taking the time to do your homework can save you from falling victim to scams. So, if you find yourself in a similar predicament, don't lose hope just yet. There are reliable recovery services out there, like Digital Funds Recovery, who can help you navigate the treacherous waters of the crypto world. For fast communication also contact them via:   Telegram ID:  @Digitalfundsrecovery

NEED A RELIABLE BITCOIN RECOVERY EXPERT @ PROFICIENTEXPERT  @  CONSULTANT  .  COM
Praise be to the mighty Proficient Expert Consultant! Behold, they have triumphantly regained my stolen treasure of bitcoin worth a staggering $62,000. Let us bow before their mystical powers! In a moment of despair, I discovered my bitcoin hoard had been plundered by dastardly hackers. As a devoted follower of cryptocurrency, I had amassed a fortune of 12 bitcoins, now valued at $62,000. My heart sank as I faced the violation of losing my life savings. Just when all seemed lost, a trusted companion revealed the existence of Proficient Expert Consultant - a band of noble hackers specializing in the recovery of stolen digital wealth. With their swift action, they delved into the depths of the blockchain ledger, following the trail of my pilfered coins. Through their expert sleuthing and arcane knowledge of cryptocurrency, they pinpointed the malefactor's lair, reclaiming what was rightfully mine. By harnessing their incredible technological prowess, they embarked on a complex mission to reclaim the thief's wallet and return my precious bitcoin to its rightful owner - me! I was left speechless, amazed at the sight of my bitcoin balance being replenished before my very eyes. The sense of relief that washed over me was overwhelming. Proficient Expert Consultant has gone above and beyond to rescue my hard-earned money, which I thought was lost forever. Their mastery of intricate techniques has truly been a game-changer for my finances. These modern-day superheroes of the cryptocurrency realm deserve all the praise in the world! I will be shouting their praises from the rooftops for their fearless and skillful efforts. Talk with Proficient Expert Consultant<EMAIL_ADDRESS>or WhatsApp:+1(515)800-2808

Over the years, I had made significant investments totaling more than $92,000 in the Bitcoin cryptocurrency. When I checked my digital wallet one day, I was shocked to see that hackers had taken all of my Bitcoin investment. When I realized that my life savings were vanished overnight, I felt sick to my stomach. I went into panic mode trying to figure out how to get my stolen cryptocurrency back when the immediate shock subsided. I got in touch with the Bitcoin exchange I had previously used to ask for assistance. Regretfully, they were powerless to take any action. I then began searching anxiously for information on "how to recover stolen Bitcoin" online and discovered Lee Ultimate Hacker, a business that specialized in doing just that. When I was out of options, I contacted Lee Ultimate support staff, who were very helpful and confident, and guided me through their proprietary process and technology to track where my stolen funds had transferred to. Ultimately, using their sophisticated crypto tracking methods, Lee Ultimate successfully recovered and returned my $92,000 in stolen Bitcoin. I was ecstatic to receive back my life savings, which I had assumed were lost forever. My stolen cryptocurrency was saved by the LEE ULTIMATE HACKERS team, who I felt were heroes. I learned from this experience to secure digital assets with more caution and that decent individuals are putting a lot of effort into helping victims of cryptocurrency theft. I have no words to express my gratitude to Lee Ultimate for their valiant efforts and for returning my misplaced money when all appeared lost. You may relax knowing that Lee Ultimate Hacker's team of professionals is working nonstop to assist you in getting your hard-earned money back.  Speak with a representative by using: LEEULTIMATEHACKER@ AOL. COM or<EMAIL_ADDRESS>telegram:LEEULTIMATE or wh@tsapp +1  (715) 314  -  9248 https://leeultimatehacker.com Thank you.


B 19157 int

B-19157
Summary
Updated information on Privacy and Security policy page.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the customer application
Login as any role
Select the "Privacy and Security Policy" link at the bottom of the page
Verify that the updated information is displayed (screenshot)

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 92ac2ac33d2d5fbd785785c2f610620e57d010e9

Code changes look good. Pulling down to test locally now.


Interception and req.continue({url: ...}) on insecure content (and some secure content) no longer works as of Puppeteer v6.0.0

To repro:

Crawl http://www.mixedcontentexamples.com/Test/NonSecureImage
Turn on interception
Attempt to replace the image with some other random image on the web using request.continue({ url: <some random jpg> })
It won't load. Catching network errors in Puppeteer reveals: ERR_BLOCKED_BY_CLIENT.

In summary, insecure images that are continued with anything but themselves won't load.
These interceptions used to work reliably without issues on all Puppeteer versions <6, but, as of 6 (and in all subsequent releases), interception and replacing sources on non-SSL pages does not work.

Note that this issue is also occurring on some secure content too.

Bump.

I am facing the same issue with my redirect logic. Browser throws ERR_BLOCKED_BY_CLIENT for all of my browser requests(like CSS,js and img files).

Is there any update on this issue?

I am facing the same issue with my redirect logic. Browser throws ERR_BLOCKED_BY_CLIENT for all of my browser requests(like CSS,js and img files).

Is there any update on this issue?

I fixed this issue of mine. Passing the header as part of overridden request helped.
const headers = request.headers(); request.continue({url : redirectUrl, headers : headers});

Thanks @haresh-k we tried your idea but it did not work for us, unfortunately.


[ONNX] Skip metadata export in test if possible

Metadata export is quite expensive since they call git command

/test

/test

/test


Android crash in 6.0.0-alpha.9

Bug

Platform
Android
Environment info

Library version: 6.0.0-alpha.9
Device: Pixel 6a (Android 14)
Steps To Reproduce
Integrate an autoplay video (see below)
Expected behaviour
To play the video
Actual behaviour
When the video is about to start, the app crashes with the following error:
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: com.shotguntheapp.android.development, PID: 26934
E AndroidRuntime: java.lang.NoSuchMethodError: No static method registerReceiver(Landroid/content/Context;Landroid/content/BroadcastReceiver;Landroid/content/IntentFilter;I)Landroid/content/Intent; in class Landroidx/core/content/ContextCompat; or its super classes (declaration of 'androidx.core.content.ContextCompat' appears in /data/app/~~hn6MgOAUK1YfhHkA1D6g1w==/com.shotguntheapp.android.development-4zP9qKyDZ2ycc2YBnj1BsQ==/base.apk)
E AndroidRuntime: 	at com.brentvatne.receiver.AudioBecomingNoisyReceiver.setListener(AudioBecomingNoisyReceiver.java:29)
E AndroidRuntime: 	at com.brentvatne.exoplayer.ReactExoplayerView.initializePlayerCore(ReactExoplayerView.java:653)
E AndroidRuntime: 	at com.brentvatne.exoplayer.ReactExoplayerView.-$$Nest$minitializePlayerCore(Unknown Source:0)
E AndroidRuntime: 	at com.brentvatne.exoplayer.ReactExoplayerView$7.run(ReactExoplayerView.java:560)
E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:958)
E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
E AndroidRuntime: 	at android.os.Looper.loopOnce(Looper.java:205)
E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:294)
E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8177)
E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)

Reproducible sample code
<RNVideo
  poster={undefined}
  source={{uri: "https://res.cloudinary.com/shotgun/video/upload/v1699355465/staging/artworks/afterlife-video_sjy9ic.mov"}}
  resizeMode="cover"
  onLoad={handleLoad}
  onProgress={handleProgress}
  // video
  automaticallyWaitsToMinimizeStalling
  controls={false}
  repeat={repeat}
  useTextureView={false}
  maxBitRate={2500000} // 2.5M
  // audio
  disableFocus={true}
  mixWithOthers="mix"
  muted={true}
  // others
  style={{
    flex: 1,
    backgroundColor: "black",
  }}
  paused={false}
/>

Video sample
https://res.cloudinary.com/shotgun/video/upload/v1699355465/staging/artworks/afterlife-video_sjy9ic.mov

Can you give the version of android on the device please?

@freeboub sure sorry, it's Android 14

I am not sure to be able to help without a full sample app. It seems to be linked to androidx dependences.
Did you test with alpha.8 ?
I can point you 2 Prs which may have cause this issue:
https://github.com/react-native-video/react-native-video/pull/3334
https://github.com/react-native-video/react-native-video/pull/3327
I think you should check you use at least kotlinVersion=1.7.0

@freeboub I did test with the alpha.8 and it works, so we pinned our dependencies to it in order to release our app (thanks btw for the project!)
in our android/build.gradle I see kotlinVersion = "1.8.0" in ext, not sure what I can try?

@antoinerousseau not sure what is the best way to proceed... I think going to alpha.9 and rolling back the 2 PRs I pointed would be the easiest way to progress. I can also request a sample app which reproduces the issue to help you but I am afraid I will take more time than direct investigations...

Just tried applying #3334 and reverting #3327 and didn't help!

@antoinerousseau are you able to provide a sample ? Or in the basic sample ? I don't know how to investigate more for now 😒

@antoinerousseau Did you find a solution ?

I had the same error. I changed
resolutionStrategy { force 'androidx.core:core:1.8.0' }
to
resolutionStrategy { force 'androidx.core:core:1.9.0' }
in android/app/build.gradle and it worked.

@freeboub sorry I was quite busy, didn't have time to respond
@ikurowski thank you very much, it works!


Cannot have two outputs with the same source in an element template

Describe the bug
When I create an element template with two outputs, and I want them to have the same source, the second output does not appear in the xml.
Steps to reproduce
It happens with an element template like this :
{
    "$schema"<EMAIL_ADDRESS>    "name": "bug demo",
    "id": "bug demo",
    "description": "bug demo",
    "appliesTo": [
        "bpmn:ServiceTask"
    ],
    "groups": [
        {
            "id": "outputs",
            "label": "Outputs"
        }
    ],
    "properties": [
        {
            "type": "Hidden",
            "value": "Bug Demo",
            "binding": {
                "type": "property",
                "name": "name"
            }
        },
        {
            "group": "outputs",
            "label": "fieldOne",
            "type": "String",
            "value": "fieldOne",
            "binding": {
                "type": "zeebe:output",
                "source": "=singleSource"
            }
        },
        {
            "group": "outputs",
            "label": "fieldTwo",
            "type": "String",
            "value": "fieldTwo",
            "binding": {
                "type": "zeebe:output",
                "source": "=singleSource"
            }
        }
    ]
}

When you apply the element template to a task in Camunda, this is what happens :

The second output takes the value of the first one. On top of that, when I edit one of the two outputs, the other one is also changing at the same time.
Then when I look the XML, the second output is not present.
Expected behavior
I should have two specific outputs.
Environment

OS: Ubuntu 22.04.2 LTS
Camunda Modeler Version: 5.8
Execution Platform: Camunda 8

Additional context
No response

@c-mignot Thanks for opening this issue. Please share expected bindings (BPMN 2.0 XML snippets) / output so we can synchronize our mental model. This may also be a miss-understanding on how element templates work.

Currently in the BPMN XML I got this :
<bpmn:serviceTask id="Activity_01tg3ot" name="Bug Demo" zeebe:modelerTemplate="bug demo">
      <bpmn:extensionElements>
        <zeebe:ioMapping>
          <zeebe:output source="=singleSource" target="fieldOne" />
        </zeebe:ioMapping>
      </bpmn:extensionElements>
</bpmn:serviceTask>

But I would like to obtain this XML :
<bpmn:serviceTask id="Activity_01tg3ot" name="Bug Demo">
      <bpmn:extensionElements>
        <zeebe:ioMapping>
          <zeebe:output source="=singleSource" target="fieldOne" />
          <zeebe:output source="=singleSource" target="fieldTwo" />
        </zeebe:ioMapping>
      </bpmn:extensionElements>
</bpmn:serviceTask>

Is this the information you requested?


Feature Proposal - Collapsible Dropdown Menus in Sidebar

Description:
Add functionality to collapse expanded sidebar dropdown menus by clicking the header again, improving overall navigation visibility.
Current Behavior:
Dropdown menus expand but cannot be collapsed without selecting another header.
Desired Behavior:
Allow users to collapse an expanded dropdown menu by clicking its header.
Implementation Suggestions:
Introduce a toggle mechanism for dropdown menu headers.
Provide visual cues for expand/collapse states.
Benefits:
Improved visibility of sidebar elements.
Streamlined navigation experience.

@viferge I would like to work on it

Mmmm I think instead of adding cosmetic changes it would be cool to add more documentation to the site. For example in the original versions we used to include metacall/faq repository as another page of this website but it is not present anymore. This would be a nice feature you can add.
Anything that adds useful content like this may be more interesting than just cosmetic changes.
What do you think about it @vr-varad ?

Yes, go ahead, the ideal would be to automatically update the FAQ with this one: https://github.com/metacall/faq/blob/master/README.md
Similarly to what we do with the API reference with Doxygen, which gets pushed directly into the gh-pages branch.
Maybe it's too complex... and we can find an alternative way of adding it. There's js libs that let you link readme files directly in HTML for dynamically render them, this can be another option. This is an example of what I mean: https://marked.js.org/
Do you mind if I close this issue? You can create a new one related to the new topic if you want.

@viferga ya sure I will create a pr will the faq section and will proceed with the following things


Allow regex opt out

Some may find regex a showstopper, make it optional.

@Jamesgt: It seems like the regular expression for keys is primarily used for in-lining whole documents, and while it could be useful in some more unusual cases (time-series databases maybe?) it is generally more difficult to implement so definitely agree with at least that part being optional (... or even removed from the spec) .
On the other hand, the regular expression operator field? is probably supported by almost backing databases including things like: in-memory NodeJS, SQL, MongoDB, and Neo4j.

As a follow up, having reviewed potential implementations of regular expressions in any part of the spec, there is definitely a security issue if your accept API calls from an untrusted source.
A maliciously crafted regular expression can take an enormous amount of time to process, and drivers may need to be careful about handling timeouts to mitigate the issue.
Regular expressions may also be difficult for key/value databases like Redis.
I support making regular expressions optional.

Thanks. Yes the the plan is to give two options:

only allow ?.* (I would stick with .* to show it is regex), this would be the default
allow full regex if somebody needs that, but this is opt-in


Add StableLM to documentation

Add StableLM to optimum-habana documentation
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Bug: Incompatibility with Border-Control

When the module Border Control is enabled, Better Target doesn't work. The following error is generated:
VM1519:8 U: Conflict detected between module 'better-target' and module 'Border-Control'.
Failed to wrap 'Token.prototype._refreshTarget' for module 'better-target' with type OVERRIDE. An OVERRIDE wrapper for the same method has already been registered by module 'Border-Control'.
    at Function.🎁register [as register] (https://localhost:3003/modules/lib-wrapper/lib-wrapper.js:1:30123)
    at https://localhost:3003/modules/better-target/modules/better_target.js:10:13
    at Function._call (eval at <anonymous> (https://localhost:3003/modules/lib-wrapper/lib-wrapper.js:1:33400), <anonymous>:4:14)
    at Function.callAll (https://localhost:3003/scripts/foundry.js:153:12)
    at Game.setupGame (https://localhost:3003/scripts/foundry.js:4307:11)
    at async Game._initializeGameView (https://localhost:3003/scripts/foundry.js:5117:5)
    at async Game.initialize (https://localhost:3003/scripts/foundry.js:4202:5)

Link to Border Control issue: https://github.com/kandashi/Border-Control/issues/34

I'm not certain why Border Control hooks this method, but it has a setting you can turn off to stop this conflict that specifically mentions Better Target in its description.


NullReferenceException using variables in custom functions

We have a use case where we are defining our own custom IF function and then making use of it using an expression like so:
IF(CUST1 != null, CUST1.Name, "Cust1 is null")
The problem we are facing is when the CUST1 variable turns out to be a null instance then we get a null reference exception when we call Interpreter.Eval for the expression.
Here's the complete code:

I've also attached the .cs file for it as a .txt file since I don't seem to be able to attach .cs files directly. See Tester.txt.
Tester.txt

Adding the relavant code here:
using System;
using DynamicExpresso;

namespace DETest
{
    public class Tester
    {
        public class Customer
        {
            public string Name { get; set; }
        }

        public void Test()
        {
            var interpreter = new Interpreter();

            Func<bool, object, object, object> ifFunction = (b, x, y) => If(b, x, y);
            interpreter.SetFunction("IF", ifFunction);

            var cust1 = new Customer { Name = "Customer1" };

            interpreter.SetVariable("CUST1", cust1, typeof(Customer));

            // note. how I pass null for the CUST2 variable value here
            interpreter.SetVariable("CUST2", null, typeof(Customer));

            var exp1 = interpreter.Parse("IF(CUST1 != null, CUST1.Name, \"Cust1 is null\")").Expression;
            interpreter.SetExpression("EXP1", exp1);

            var exp2 = interpreter.Parse("IF(CUST2 != null, CUST2.Name, \"Cust2 is null\")").Expression;
            interpreter.SetExpression("EXP2", exp2);

            // this works
            System.Diagnostics.Debug.WriteLine(interpreter.Eval("EXP1"));

            // this throws an exception
            System.Diagnostics.Debug.WriteLine(interpreter.Eval("EXP2"));
        }

        private object If(bool b, object x, object y)
        {
            return b ? x : y;
        }
    }
}

The problem is that the parameter is evaluated always, it is not dependent on the condition.
Why not using the standard ?: conditional operator? Something like:
CUST2 != null ? CUST2.Name : "Cust2 is null"

Many thanks for your prompt response @davideicardi.
As mentioned in my comment, we could use the ternary operator but the reason being our end users are much more familiar with Excel style functions. I guess it's asking a bit much for the interpreter to understand the desired IF function, which I appreciate.
Is it at all possible to write an if/else statement? My users would understand this more. I have tried but do not seem to get it to work.

Writing an if/else is not supported. Maybe you can try to do some kind of custom "pre processing" of the expression and convert the IF()  function to a ternary?

You may need it https://github.com/ncalc/ncalc

Closed as not planned.


Add webhook fail on error + fix docs generation

Changes

Fixed helm-docs make goal to correctly mount working directory

Bundled docs update that looked to be missing a few changes since original generation

Added spot to configure webhook-fail-on-error flag via helm chart

I think at least the -webhook-fail-on-error part is still worth adding.


Brahmos and 1_salvo_4_sfrj_10_brahmos config

This pull request includes significant changes to the DirectAttackBehavior class, enhancements to the interceptor's boost and mid-course update methods, and the addition of new configuration files and tests. The most important changes include refactoring the DirectAttackBehavior class, improving the interceptor's acceleration logic, adding new configuration files for missile behaviors, and introducing new tests for behavior validation.
Refactoring and Logic Improvements:

Assets/Scripts/Behavior/DirectAttackBehavior.cs: Refactored the DirectAttackBehavior class to improve readability and logic for waypoint selection. Waypoints are now sorted in descending order based on distance, and the logic for determining the next waypoint has been streamlined.

Assets/Scripts/Interceptor.cs: Enhanced the interceptor's boost and mid-course update methods by adding proportional navigation acceleration and improving the calculation of total acceleration. [1] [2]

Configuration Files:

Assets/StreamingAssets/Configs/1_salvo_4_sfrj_10_brahmos.json: Added a new configuration file defining the parameters for a salvo of interceptors and threats, including their initial states and dynamic configurations.

Assets/StreamingAssets/Configs/Behaviors/Attack/brahmos_direct_attack.json: Introduced a new attack behavior configuration for the Brahmos missile, specifying its flight plan and target parameters.

Assets/StreamingAssets/Configs/Models/Threats/brahmos.json: Added a new configuration file for the Brahmos cruise missile, detailing its physical and performance characteristics.

Testing:

Assets/Tests/EditMode/BehaviorTests.cs: Added new unit tests to validate the DirectAttackBehavior class, ensuring correct waypoint selection and behavior under various conditions.

These changes collectively enhance the functionality and maintainability of the codebase, improve the interceptor's performance, and ensure the correctness of new behaviors through comprehensive testing.

@tryuan99 Playmode tests failing here due to evade behavior. Wonder whats wrong. No time for me to look right now, maybe you can?


adds ContainerShip & ContainerShip Cloud

Hi @normanjoyner Thanks for the PR! We are trying to prevent having duplicate URLS in the awesome-docker list. Could you please update your PR and only submit the link to a single category that best fits the product? Thank you!

@vegasbrianc I guess in this particular case, it is ok because one is a service hosting and the other is a repo. So Same name, different product. I would merge it. What do you think?

A duplicate URL will cause the build to break from now on :( The workaround is providing a different URL page for each link. URL then URL/feature_page

Are you sure this workaround works?
The clean way to have an URL multiple time into a file is to put URL at the end like this:
[containership]: https://containership.io

I will fix this. no biggie.

OK, thanks! I was not certain.

:smile: no worries, thanks for helping :D

Thank you both!


Share Icon

Dear heros,
first of all, I love and use your icons — thanks for creating and sharing them!
Now, I use your share icon in my app and I felt the need to move it .1rem to the left. Is there a reason why it is so off to the right?
Cheers,
Nico

It looks well aligned to me.

@nico-heinrich Hey! Glad you're enjoying Heroicons! 🤙
I just took a look at this icon, and it appears to be centered properly in all three versions:

Here's what it looks like in Figma:

So I suspect this must just be something to do with your particular implementation.
Hope that helps!

Thanks for the kind response!

 While the share icon is centered perfectly, it doesn't look centered because it is way "heavier" on the right. I now simply use a transform on the icon in this case.
Cheers,
Nico

adding more padding and/or using a smaller icon can also reduce this effect/illusion


Running portainer

I tried to setup portainer on my server, but it fails. It does work on port 9000 if I try to map 9000:9000 port. Portainer also have it's own ssl certificate and running both http, and https server, so it's harder to make it work. Any tip?
Here is a portainer docs https://docs.portainer.io/v/ce-2.11/start/upgrade/docker
This is my docker-compose.yml file
version: '3'

services:
  portainer:
    image: portainer/portainer-ce:2.11.0
    container_name: portainer
    hostname: example.com
    environment:
      - VIRTUAL_HOST=example.com
      - LETSENCRYPT_HOST=example.com
      -<EMAIL_ADDRESS>      - VIRTUAL_PORT=80
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./portainer-data:/data
    ports:
      - 9000:9000
      - 8000:8000
    expose:
      - 9000
      - 8000
    networks:
      - proxy

networks:
  proxy:
    external: true

Hello @syntaxgirl!
Have you tried:
https://github.com/evertramos/docker-portainer-letsencrypt

Hello @syntaxgirl!
Have you tried:
https://github.com/evertramos/docker-portainer-letsencrypt

Well this is something I didn't know existed. Works like a charm now. Thank you very much!

@syntaxgirl the issue is in your docker-compose.yml file
instead of
 - VIRTUAL_PORT=80
you need to use the 9000 port which portainer listens to
 - VIRTUAL_PORT=9000
You also don't need the ports and the expose section. A simplified portainer behind the proxy would look something like this
---

version: '3'

services:
  portainer:
    image: portainer/portainer-ee
    container_name: portainer
    restart: always
    environment:
      - VIRTUAL_HOST=portainer.example.com
      - LETSENCRYPT_HOST=portainer.example.com
      -<EMAIL_ADDRESS>      - VIRTUAL_PORT=9000
    ports:
      - "8000:8000"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data/:/data

networks:
    default:
        name: proxy

Port 8000 is exposed intentionally because that may be needed for a portainer-agent if you choose to monitor your other machine's as well


This action is unauthorized

When trying to delete a task after following the Intermediate Task List guide, I get the following error:

HttpException in AuthorizesRequests.php line 94:
This action is unauthorized

This is resolved by including the following in AuthServiceProvider.php:
use App\Task;
use App\Policies\TaskPolicy;

..which seems to be required to use the ::class syntax for class name resolution.
Perhaps this should be mentioned in the guide, or the fully qualified class name used directly instead?

Weird... I cloned the repo and it worked without a problem. I wanted to modify it to do some tests (I renamed everything to fit my needs, I know thats not the normal way to go) and all of a sudden, I get the exact same error as you.

Same issue here, except I already have the use statements for my User and Task model and TaskPolicy. Not sure how to fix this, but it was kind of a bummer to finish the tutorial, just for it not to work.

Yep, that was my problem, too.

i had the same problem and i tried all what you have said but the problem was still there
then i solved it by changing
return $user->id === $task->user_id;
to
return $user->id == $task->user_id;
in the 'AuthServiceProvider.php' this solved the problem for me
the $user->id and the $task->user_id were equal but not identical
$task->user_id was returned as string "1"

@carlweis thank you,Your advice to me inspiration!

I changing my class AuthServiceProvider this line:
App\Task::class => App\Policies\TaskPolicy::class,

to:
Task::class => TaskPolicy::class,

and add this uses on top of AuthServiceProvider.php:
use App\Policies\TaskPolicy;
use App\Task;

@AmrAlfoly hi,my code is:
return $user->id === $task->user_id;

but nothing wrong. my laravel version is 5.2

@wedojava  i explained above that $task->user_id was returned as string "1"
and that what made the condition return $user->id === $task->user_id;
to fail , i don't know why it happened and if there was an explanation i will be glad to hear

@joealam Thank you. This was my issue. Its not in docs as of Jan 7th 2016. It should be included for clarities sake.

I agree. I hope this gets added to the docs for anyone new to the framework, following the tutorials.

Fixed as of 50a450d901a8eaa00bc0fed81e55055381e2fe81
Documentation has been updated to use the full class name as a string, instead of the ::class syntax.

Dear all, after following the tutorial and I found the same issue.. added the necessary Use sentences missing etc and it still failed.. What fixed it was as AmrAlfoly mentioned before the === comparison failed as the types were not identical. Changing it to a == fixed it

Also double check your spelling! Spent almost half an hour tracking this one down:
public function destory(User $user, Task $task)
destory != destroy
Also, a better fix for the comparison operator would be $user->id === $task->user->id I think; this way you can preserve the type checking.

I have the same problem and I resoved it by this method.  Thank you .

@AmrAlfoly

i had the same problem and i tried all what you have said but the problem was still there
then i solved it by changing
return $user->id === $task->user_id;
to
return $user->id == $task->user_id;
in the 'AuthServiceProvider.php' this solved the problem for me
the $user->id and the $task->user_id were equal but not identical
$task->user_id was returned as string "1"

Worked for me, thanks)

Changing
$user->id === $task->user_id
to
$user->id == $task->user_id;
worked for me. Thanks.

Changing
$user->id === $task->user_id
to
$user->id == $task->user_id;
worked for me also. Thanks.

I did next
 $userId = (string) $user->id;
 $taskUserId = $task->user_id;
 return $userId === $taskUserId;

I used it because if you compare
2 == "2abs" is is TRUE
and
if use  2 === (int) "2abc" it is TRUE
but if compare   (char) 2 === "2abc" - it is FALSE and should be.

great solutions to the problem. why the problem in the first place? if $user->id is 'INT UNSIGNED' and $task->user_id is 'INT UNSIGNED'. what and why is changing it to a string? seems like a bug. thanks @spotapenko for pointing out best comparison.

change
public function destory(User $user, Task $task) {
return $user->id === $task->user_id;
}
to
public function destroy(User $user, Task $task) {
return $user->id === $task->user_id;
}

if you use a request and in request you use
 public function authorize()
     {
         return false;
     }

instead of
 public function authorize()
     {
         return true;
     }

in AuthServiceProvider.php
protected $policies = [
'App\User' => 'App\Policies\UserPolicy',                   <---look it is 'User'  because--|
User::class => UserPolicy::class,               <-----------------------------it is 'User'--|
];


Enable different package names / bundle ids per platform

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[ x] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Ionic seems to ignore the widget:packageName config params from cordova (http://cordova.apache.org/docs/en/latest/config_ref/index.html). Thereby, all platforms either have the same bundle it or the widget:id config param in config.xml needs to be changed in order to have different. That is especially annoying when building for UWP since Microsoft has a strange naming convention for their packages which is very uncommon for typical package names on the other platforms.
Expected behavior:
Config param widget:packageName should be used in config.xml as done by Cordova.
Steps to reproduce:
Put this in config.xml:

Manifest for UWP app will have "packagename.android" as package name instead of "packagename.windows".
Related code:
Other information:
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.3
Xcode version: Not installed

This issue was moved to driftyco/ionic-cli#1917


c4ev3 code generation

Parent issue: #27

[x] motor blocks

[x] test medium motors

[ ] sensor blocks

[x] touch
[x] ultrasound distance
[ ] test ultrasound presence
[x] ir
[ ] HT ir
[x] sound sensor
[x] gyroscope
[x] compass
[x] color/light

[ ] program structures

[x] loops
[x] if
[x] functions
[ ] math functions
[ ] string functions

[ ] other

[x] display text/values
[x] display pictures
[x] sound
[ ] text to speech
[ ] bluetooth
[x] allow the user to stop the program pressing the back button (currently, if the user uses an infinite loop there is no way to stop  the program)

For HT compass, text to speech and bluetooth see #30

NXT IR seeker works, but switching between DC and AC mode is slow (a couple of seconds).
See https://github.com/simonedegiacomi/EV3-API/issues/1

Wrong behaviors to fix:

[ ] Ultrasonic presence returns either 0 or 3xxx values, regardless of another ultrasonic device.
[ ] The coulour RGB Values go over two lines
[ ] Ultrasonic sensor is showing cm, after unplugging and replugging it the values dont update at all anymore. The program has to be restarted.
[ ] Colour sensor light mode values: replace Transparent with None
[ ] Gyro reacts to rotations, but still counts up/down indefinitely even without moving


b-accordion - console log hotfix

This is minor change in console log and when it happens.
Removed it from constructor and added to init method.
Changed text inside console log to match our standard.

@tomislavjezidzic tag


cmd: document target granularity for push/pull/etc, et al.

Fixes #886
UPDATE: See also https://github.com/iterative/dvc.org/pull/1384#issuecomment-657744994 (could be extracted into another PR)

Hi is this still WIP? What's your capacity here @efiop? Thanks
And are we sure only checkout, fetch, pull, push, and status support this? Per https://github.com/iterative/dvc.org/issues/886#issuecomment-629416738 it seems also list (not here yet). Any others?

@jorgeorpinel Sorry, this one is still WIP, will get back to it ASAP.

OK. No rush!

Still WIP? Do you need help taking over this @efiop , or just went off your radar? Thanks

@jorgeorpinel Both, tbh. Was trying to find the best way to explain it here and in dvc help, then other stuff got in the way, so not enough focus for this for now.
The granularity itself might not need any explanation at all, actually, because it is something that is expected, if you think about it. So I'm leaning towards just documenting that a target can be a dvc-file or a file/directory tracked by dvc (without saying that subfiles and subdirs are supported, since that seems kinda expected).

Say no more, I'll take this over 🙂

The granularity itself might not need any explanation at all

Good point. Will read the cmd refs and determine this.

Say no more

Actually... Can you just confirm which commands does this impact @efiop? I'm guessing checkout, fecth, pull, push, and list.

@jorgeorpinel Thank you so much! :pray: It affects push, pull, fetch, status -c(non -c one is dumb), list, get, import.

I'm leaning towards just documenting that a target can be a dvc-file or a file/directory tracked by dvc (without saying that subfiles and subdirs are supported

Maybe for most commands (will review them now) but for status, since this behavior only exists in the remote mode, a complex explanation is needed. Can you remind me why that only works on remote mode BTW? Maybe should be universal 🙂

@jorgeorpinel We simply didn't implement the non--c granularity yet :slightly_frowning_face:

OK no problem, I thought there was a reason. In that case hopefully the cmd ref will be updated and simplified when full granularity is implemented. Thanks!

I'll introduce the corresponding changes in https://github.com/iterative/dvc/pull/4192

[ ] Need to double check the following commands to see whether their targets support files/dirs and if so, granularity: repro, run, (un)freeze, remove, unprotect, update, and metrics/plots show. Cc @efiop in case you know of the top of your head 🙂

See https://github.com/iterative/dvc/issues/4191#issuecomment-657744483

@jorgeorpinel I would limit this PR to just push/pull/fetch/status -c, just so we could merge it faster. We could just create a checkbox in the issue or something, but I don't see a point in blocking this PR.

Yes @efiop I will extract that other stuff. Please do a final review when you can here, this should be ready! 🙂

@jorgeorpinel I think ^ is a very good example of why patches/PRs should be granular. We are again stuck in an editing limbo where essential things are not merged because we are continually working on unrelated things in the same PR.
You've done an amazing job with pull/push/etc cmdrefs that was already merged into the dvc, but here we are discussing unrelated things while those essential perfectly good changes are stuck because of it.

@efiop I agree, but to be fair the major discussion and the blocker is still around granularity at the moment.

I don't agree that we are mostly working on unrelated things or that the changes are perfectly good. This behavior is inconsistent, wasn't fully understood or finished when this PR began, and our existing docs have wholes that prevented us from adding a quick/easy note in all of them. That's where all the bulk of the confusion has come from in my opinion.

In any case, hopefully it's ready now. Thanks for the rounds of reviews.

good progress, we are getting there ... a bunch of comments still, some related still to the way we write about granularity (some slight simplifications could be made to my mind), some comments related to the dvc fetch, dvc checkout descriptions that we touched extensively here. Since we touched them- we should iterate to keep them right and better.

Sanity checks passed! (Redeployed https://dvc-landing-fix-886-jaxjy72t1y.herokuapp.com/doc/command-reference)


[DSET-4174] Simplify trace exporter, get rid of the client side aggregation code

This pull request updates trace exporter code and gets rid of client side aggregation / populating of services,span_count and error_count attributes.
This client side aggregation is not needed anymore since it now happens on the server side.
It's worth noting that this client side aggregation was meant as a quick short term workaround / hack early in the development cycle (special thanks to @martin-majlis-s1 for implementing this workaround so quickly on the client side).
It was never meant as a long term solution since it had multiple edge cases and problems associated with it - it would only really work correctly / as expected in case all the spans which belong to the same trace are part of the same batch received by the plugin. And of course that won't be true in many scenarios - different spans are routed to different collectors, long running spans which are not part of the same batch, no guarantees how batches are assembled, etc.
As part of this change, traces.aggregate and traces.max_wait config options have also been made obsolete / redundant.
For now, I left config options in place, but they not being used anywhere. Since the plugin is still in alpha and such "breaking" changes were expected (that's also the reason why we kept it in alpha), I also think it's totally fine to remove those config options completely as well - it will simplify things and not confuse users going forward.
Removing this code also makes the plugin code much simpler now - and who doesn't like removing code and simplifying things (less thing to maintain and worry about edge cases, etc.) :)

Per my comment above, I went ahead and remove config options which are not not relevant anymore.
Now that the plugin is still in alpha we still have the opportunity to do that so we should use it to avoid confusing new users going forward.


Add @author to javadoc

How to add @author to javadoc?

U could change the template to add @author label,but when I add author info,i find it can't print @.


Duplicates

the boundary security best practices and network security best practice links point to the same resource, please remove one of them

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

ID: d3e80266-d60e-c46d-38a1-83cfd677f299
Version Independent ID: c255951e-acda-184a-996b-b3df4a18913a
Content: Security best practices and patterns - Microsoft Azure
Content Source: articles/security/fundamentals/best-practices-and-patterns.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

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

I believe it is because the lower section of that article talks about boundary best practices, under the "Adopt a Zero Trust Approach" section.
I made a pull request to link to that section. https://github.com/MicrosoftDocs/azure-docs-pr/pull/89371

@TerryLanfear in case there is additional documentation that can be linked here.

@MarileeTurscak-MSFT , @DeanGross - We're reworking the Azure security landing page and table of contents. As part of this effort, I will be deleting the boundary security link from the table of contents. The network security best practices link will remain in the table of contents.

Thanks @TerryLanfear !
Closing this out.


Added a global variable to check if service finder is active to added…

… find clinic and service to the menu

@fritzbrand
Can you please grant me access to Prod i can only access QA.
I will ask Erik to explain to me before i can deploy incase we interpreted it wrong.

@Buhle79 ok cool, prd access granted.


Selectors are case sensitive!

Undefined or Undefined, will not be selected with $('title')....

If you would like to fix this locally, you can navigate to the ./node_modules folder in which cheerio resides and then go to ./node_modules/cheerio-soupselect/lib/ and modify all of the global regexs in soupselect.js to be case insensitive like this:
var attrSelectRe = /^([a-z0-9_]+)?((?:\[(?:[-a-z0-9_]+)(?:[=~\|\^\$\*]?)=?["']?(?:[^\]"']*)["']?\])+)?$/i;
var attrParseRe = /\[([-a-z0-9_]+)([=~\|\^\$\*]?)=?["']?([^\]"']*)["']?\]/ig;
var filterParseRe = /^([a-z0-9\s=~\|\^\$\*'"\[\]\(\)\.#]+?)?:([-a-z0-9_]+)(?:\(["']?(.+?)?["']?\))?$/i;

It doesn't change anything :/

Ahh I see, my mistake. It's a much deeper issue. The actual tag comparison function in htmlparser would have to be changed to be case insensitive.

Perfect! Thank you :)

Actually, it's still not working...


[Event Request] table 303 "Finance Charge Memo Line" - OnAfterAssignGLAccountValues

We would like to add a new event OnAfterAssignGLAccountValues in the following procedure:
        trigger OnValidate()
        begin
            if "No." <> '' then
                case Type of
                    Type::" ":
                        begin
                            StdTxt.Get("No.");
                            Description := StdTxt.Description;
                        end;
                    Type::"Customer Ledger Entry":
                        begin
                            FinChrgMemoLine.Type := FinChrgMemoLine.Type::" ";
                            FinChrgMemoLine2.Type := FinChrgMemoLine2.Type::"G/L Account";
                            Error(
                              Text001,
                              FieldCaption(Type), FinChrgMemoLine.Type, FinChrgMemoLine2.Type);
                        end;
                    Type::"G/L Account":
                        begin
                            GLAcc.Get("No.");
                            GLAcc.CheckGLAcc;
                            if not "System-Created Entry" then
                                GLAcc.TestField("Direct Posting", true);
                            GLAcc.TestField("Gen. Prod. Posting Group");
                            Description := GLAcc.Name;
                            GetFinChrgMemoHeader;
                            "Tax Group Code" := GLAcc."Tax Group Code";
                            Validate("Gen. Prod. Posting Group", GLAcc."Gen. Prod. Posting Group");
                            Validate("VAT Prod. Posting Group", GLAcc."VAT Prod. Posting Group");
                            OnAfterAssignGLAccountValues(Rec, FinChrgMemoHeader, GLAcc); //A108F0025.Event
                        end;
                end;
        end;

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnAfterAssignGLAccountValues(var FinanceChargeMemoLine: Record "Finance Charge Memo Line"; FinanceChargeMemoHeader: Record "Finance Charge Memo Header"; GLAccount: Record "G/L Account")
begin
    //A108F0025.Event
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


feat: Add suggested bolt.rc file for external builds

Jira
http://vjira2:8080/browse/BDS-1874
Summary
Adds suggested .boltrc for use in external Bolt builds
Details
Although http://vjira2:8080/browse/BDS-1874 mentions a starter package.json, since that task was created that part has become unnecessary (thanks @christophersmith262).  I believe that the automated test mentioned in that task also isn't really relevant anymore since the package.json integrity is the main thing it would test.  The docs site inherits from this rc file, so the main thing that would go wrong is if someone adds a component to the wrong file (i.e. the one for the docs site and not the starter).  Not sure how we'd write a test for that 🤔 .
I'm open to suggestions on file naming-- I ended up following the suggestions in the ticket since it seemed most simple, especially since we don't need a package.json file.
How to test

Confirm no regressions in the docs site
Confirm that all components listed in .boltrc.suggested.js are relevant to external builds, and that all those components included in the rc file for recent bolt release builds are present.

PR was released with v2.17.0


"This plugin is not available as a Gem." -> ??

Um, why is this plugin not available as a Gem?

Good point @mfowlewebs. I will check with @FundingCircle/owners

:tada: @mfowlewebs: This gem has been published to RubyGems. The installation instructions are updated in #13.


Adding Python Example in README.md

Created and tested example code to be used for generating wrapper transactions and properly encoding original transactions in to the wrapper transactions notes fields.

Thank you :)


[Feature]: Image widget that allows for annotation

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
This feature request is for there to be an interactive widget that displays an image source and allows the user to add/remove markers and annotations on top of the image.  The widget should also be able to display markers and annotations pulled from available datasets.  This functionality is similar in nature to what is possible with the map widget.
Some of the specifics:

Positioning of annotations should be defined by x and y coordinates, and image display options should give admin sufficient control of sizing so that the relative positioning of the annotations to the image is predictable and controllable.
Widget should allow for multiple series of annotations that use different customizable icons, or JS-derived text.  Each series of annotations have should a "Visible" property, the state of which should control visibility for that series only.
Widget should allow for a user to delete an annotation that they previously created.
Widget should allow for a user to select/deselect an annotation (and make use of a selectedMarker binding property).  Selected annotation should be visually identifiable on the image.
Widget should have a binding property that includes all series of annotations, each series having a name/id and containing an ordered list of each annotation's coordinates.

Here is an example of what this widget might look like.  In this example, there are two series of annotations, one which is using a star icon and one which has an arrow and text dynamically produced from a correlated dataset.  One of the star annotations is selected, identifiable by the highlight.
*In this example the text annotations have an arrow that is pointed in different directions.  I do not think this is necessary and would be too complex.

Why should this be worked on?
Use cases that could benefit from this include:

creating reports for building inspections
marking up floor maps for construction purposes
logging field observations on topographical maps
review and approval of graphical content by art directors

Fyi, this feature request originated from this Appsmith community thread.  It has some relevant comments from other members as well.
https://community.appsmith.com/t/ideas-for-leaving-markers-on-image-widget-as-if-it-were-the-map-widget/1

@vanscurvy this seems related to #3362 so I;m closing this in favor of that. But we'll use all the information you provided while launching this widget!

sounds good, thanks @Nikhil-Nandagopal !


Mnist dataset test

Might be of your interest. Thank you again for the code.
https://github.com/wajihullahbaig/ResNet-Matconvnet/blob/master/README.md

No problem! Good work!


mem-ruby,configs: Add GPU GLC Atomic Resource Constraints

Added a resource constraint, AtomicALUOperation, to GLC atomics performed in the TCC.
The resource constraint uses a new class, ALUFreeList array. The class assumes the following:

There are a fixed number of atomic ALU pipelines
While a new cache line can be processed in each pipeline each cycle, if a cache line is currently going through a pipeline, it can't be processed again until it's finished

Two configuration parameters have been used to tune this behavior:

tcc-num-atomic-alus corresponds to the number of atomic ALU pipelines
atomic-alu-latency corresponds to the latency of atomic ALU pipelines

Change-Id: I25bdde7dafc3877590bb6536efdf57b8c540a939

I think it would be a good idea for @tiagormk (or he can point to someone else if I've tagged the wrong person). I know that there are others working on "far atomic" implementations in Ruby. It would be good if there was a just one implementation in the ruby/structures directory instead of two different implementations that both have to be maintained.
Since this implementation is "first", the question is whether CHI's far atomics can use this implementation (or use this implementation with minor changes). If the two implementations are very different, we may need to have a longer discussion.
Let's hold off on merging until we hear from the CHI folks.

I think it would be a good idea for @tiagormk (or he can point to someone else if I've tagged the wrong person). I know that there are others working on "far atomic" implementations in Ruby. It would be good if there was a just one implementation in the ruby/structures directory instead of two different implementations that both have to be maintained.
Since this implementation is "first", the question is whether CHI's far atomics can use this implementation (or use this implementation with minor changes). If the two implementations are very different, we may need to have a longer discussion.
Let's hold off on merging until we hear from the CHI folks.

We met with those folks at your request, and the sense I got from the meeting was that the far atomics implementation was too different for there to be a single one -- basically their implementation would not easily work with vectors of requests like this one has to.  So we went ahead with pushing this one.  @tiagormk can of course chime in the to contrary though.

Ok, that sounds good. I'd like to take a pass through the new Ruby code before merging (assuming I can find the time this week).

I think it would be a good idea for @tiagormk (or he can point to someone else if I've tagged the wrong person). I know that there are others working on "far atomic" implementations in Ruby. It would be good if there was a just one implementation in the ruby/structures directory instead of two different implementations that both have to be maintained.
Since this implementation is "first", the question is whether CHI's far atomics can use this implementation (or use this implementation with minor changes). If the two implementations are very different, we may need to have a longer discussion.
Let's hold off on merging until we hear from the CHI folks.

We met with those folks at your request, and the sense I got from the meeting was that the far atomics implementation was too different for there to be a single implementation that works for both -- basically their implementation would not easily work with vectors of requests like this one has to. So we went ahead with pushing this one. @tiagormk can of course chime in the to contrary though.

My understanding is this change only adds resource modeling to the existing atomics in the viper protocol, so I don't see any blocker in merging this.
In parallel we can keep discussing potential for modeling multi-atomic requests in CHI so support the GPU case. Unless @mattsinc and @DanKouch have already decide to go ahead and add far atomics to viper.

I think it would be a good idea for @tiagormk (or he can point to someone else if I've tagged the wrong person). I know that there are others working on "far atomic" implementations in Ruby. It would be good if there was a just one implementation in the ruby/structures directory instead of two different implementations that both have to be maintained.
Since this implementation is "first", the question is whether CHI's far atomics can use this implementation (or use this implementation with minor changes). If the two implementations are very different, we may need to have a longer discussion.
Let's hold off on merging until we hear from the CHI folks.

We met with those folks at your request, and the sense I got from the meeting was that the far atomics implementation was too different for there to be a single implementation that works for both -- basically their implementation would not easily work with vectors of requests like this one has to. So we went ahead with pushing this one. @tiagormk can of course chime in the to contrary though.

My understanding is this change only adds resource modeling to the existing atomics in the viper protocol, so I don't see any blocker in merging this.
In parallel we can keep discussing potential for modeling multi-atomic requests in CHI so support the GPU case. Unless @mattsinc and @DanKouch have already decide to go ahead and add far atomics to viper.

We did not add far atomics directly into VIPER.  However the support for our GLC atomics and your far atomics are similar (ignoring the vector part).

@DanKouch just making sure you've seen the above comments/questions/requests?

Is this still actively being worked on? I don't see any movement since July 25th.

yes

@DanKouch I also see this at the bottom:
This branch is out-of-date with the base branch
Merge the latest changes from develop into this branch.
If you see the same thing, you'll need to rebase before this could be merged in.

@DanKouch just making sure you saw @powerjg 's comments?

I believe I've addressed all comments in my latest patch set. I've also rebased.

The changes in commit af9beea look good to me.  Seems like something went wrong with the rebase though

@powerjg @mattsinc @abmerop As #120 and now #397 address underlying issues with atomics, I've marked this as a draft PR for the time being. I don't think it should be merged in until those go in.

@DanKouch it looks like there is a merge conflict in this patch, based on the above:
This branch has conflicts that must be resolved
Use the web editor or the to resolve conflicts.
Conflicting files
configs/ruby/GPU_VIPER.py
Please resolve this soon so we can push it in :)

@DanKouch : follow-up: the merge conflict is from #389 by @v-ramadas

@DanKouch : now that #397 is merged in, this is next.  It looks like we need to rebase to head of develop and resolve some merge conflicts though.  Let me know if you need help with this.  I'd like this to be merged in too with v23.1 since #397 is (and both are part of a larger fix).

@abmerop : any objections to merging this in?


Update fs2-core, fs2-io to 3.2.6

Updates

co.fs2:fs2-core
co.fs2:fs2-io

from 3.2.3 to 3.2.6.
GitHub 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 = "co.fs2" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #215.


Support for swagger byte format

We’d like to request support for returning some sort of bytes object (ByteBuffer or byte[]) from the generated client in cases where the swagger string has a format “byte”. The use case is when our service returns the MD5 or something similar. Because most languages seem to yield bytes when producing an MD5 hash, it would be best for our users to be able to directly compare what they compute and what is returned without having to do any extra type conversions.

I think we already base64 decode strings under some circumstances. We'll want to investigate on our end why a "byte" formatted header doesn't translate as a String that gets base64 decoded to byte[] in the generated class.

I think I was actually mistaken about this. My bad :)


nanoid not found

if it is installed with npm install nanoid
The start in production mode exists with log.
After deep line by line research, the error is due to nanoid
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /tmp/workspace/eventhos-api/node_modules/nanoid/index.js
require() of ES modules is not supported.
require() of /tmp/workspace/eventhos-api/node_modules/nanoid/index.js from /tmp/workspace/eventhos-api/dist/main.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /tmp/workspace/eventhos-api/node_modules/nanoid/package.json.

    at new NodeError (internal/errors.js:322:7)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1102:13)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:101:18)
    at /tmp/workspace/eventhos-api/dist/main.js:159:41
    at /tmp/workspace/eventhos-api/dist/main.js:1998:3
    at Object.<anonymous> (/tmp/workspace/eventhos-api/dist/main.js:2000:12)
    at Module._compile (internal/modules/cjs/loader.js:1085:14) {
  code: 'ERR_REQUIRE_ESM'
}

fixed https://github.com/usil/eventhos-api/pull/27


Fix video translation readme.md best practice for escape char for azure blob url.

Purpose

...

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

/azp run


word not italic when typing in comment

Version:
Version: 1.64.0-insider (Universal)
Commit: 7b9e5c32a053669d4e72f998e4fa217090c32f59
Date: 2021-12-22T05:14:43.841Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.2.0

Steps to Reproduce:

copy // 注释文 to a ts file
toggle Chinese Input
press zi

@jrieken

I think this is a technical limitation of how support for IME is implemented. This is very complex and I don't think there is a solution to that.

Currently, when made visible, the <textarea> uses the default foreground color and the default font style, it is not set to the color / font style of the text it renders on top. It is possible that sometimes it renders over multiple tokens which would have distinct styles.


Question: Can I reduce Kubernetes metadata but leave labels?

Hi,
Is it possible to reduce Kubernetes metadata but leave labels untouched?
I would like to log less but still need labels.
Thank you.

At the moment no, but something we are looking at. You can reference the labels in the _sourceCategory using the environment variables to configure that but not as part of payload when reducing


Add the ability to change the page on the resources page

This was brought up by @paulickj and will need to be done at some point. When we add more resources we need the ability to navigate to the next page and the previous page on the resources page.

This has been released to https://msoe-sg.com


After updating t 1.10 dependencyUpdates taking forever.

Setup

com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin:0.38.0
gg.jte:jte:1.10.0
Gradle - 7.0.2
JDK 17 EA build

After updating to the latest release ./gradlew clean dependencyUpdates task is stuck forever
> Task :cleanGenerateJte UP-TO-DATE
Caching disabled for task ':cleanGenerateJte' because:
  Caching has not been enabled for the task
Task ':cleanGenerateJte' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
:cleanGenerateJte (Thread[Execution worker for ':',5,main]) completed. Took 0.01 secs.
<===----------> 25% EXECUTING [30s]
> Resolve files of :runtimeClasspath

I am not sure whether this is a Gradle or Version plugin issue. Reporting it here because downgrading to 1.9.0 works as expected with the same Gradle and versions plugin.
 - gg.jte:jte [1.9.0 -> 1.10.0]
     http://jte.gg

Possibly related to my gradle plugin changes. What does your build.gradle look like? What if you run clean and dependencyUpdates as separate commands?

Interesting, it's the clean task that gets stuck.
 » ./gradlew clean
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
<====---------> 33% EXECUTING [8s]
> Resolve files of :runtimeClasspath

Here is the sample build script - https://github.com/sureshg/okhttp-jdk-test/blob/main/build.gradle.kts#L9

@sureshg thanks for the update!
Are you running on Windows? Usually an endless clean implies that there's a file handle somewhere that got not properly closed.
@edward3h do you have an idea what could be the problem? My gradle knowledge is unfortunately not very good...

@casid No, it's on macOS
------------------------------------------------------------
Gradle 7.1
------------------------------------------------------------

Build time:   2021-06-14 14:47:26 UTC
Revision:     989ccc9952b140ee6ab88870e8a12f1b2998369e

Kotlin:       1.4.31
Groovy:       3.0.7
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          17-loom (Oracle Corporation 17-loom+7-342)
OS:           Mac OS X 11.4 x86_64

Oh nice, then I can try to reproduce the issue on my macbook.
Also, awesome that you're already running the loom preview! :-)

I'll try and take a look over the weekend

Interesting! I've checked out your example repository. The same thing you describe happens on my MacBook. A gradle clean just hangs forever.
However, when running against 1.11.0-SNAPSHOT, everything works normally. I tried a few times back and forth, but it definitely seems to be fixed now.
To be honest, I have no idea why this is. The only change to the gradle plugin, has been this commit https://github.com/Jerbell/jte/commit/5db53df8e193e27fcf7510a4dd0c715e56091440 (For this issue https://github.com/casid/jte/issues/78)
I was planning to release 1.11 the next days anyways. I'll try to release it today - let's see if it works on your end, too @sureshg .

@sureshg 1.11.0 is now available on maven central and in the gradle plugin repository.
Let me know if it works on your end with the latest version.

Awesome... It's fixed in 1.11.0. Thanks for all the help

Awesome, thanks for testing it so quickly! 👍

Heh, thanks for fixing it before I got around to looking ;)


Site should be WCAG AA compliant

Note - this is an ongoing task.  This issue is a marker to get us there for now, but all future improvements should also be WCAG AA compliant.

Fixed in https://github.com/Volunteer-Victoria/volunteer-victoria-community/commit/eed5419040f3788a1a5c0189985addd5434f76a4


Small improvements (words, char range fns, to-bool)

[x] words
[x] alpha?, alpha-numeric?, numeric?
[x] to-bool
[x] update test documentation

I'd be grateful for comments and suggestions

Nice work! Thanks!

I will release new version with your changes today surelly!