🐛 Bug Report: there is a bug whit modals

👟 Reproduction steps
Im using this whit an astro project, when i copy and paste the code from de the dos it doesn´t show as is spected
this is my code

<button class="card s-xciFPC5Srn6Q">

Nueva tienda

Crea una nueva tienda donde podras administrar tus productos y poder
    realizar registros de las mismas
    <button class="button s-yu7OS-GWNOYq">Open Modal</button> <dialog class="modal s-yu7OS-GWNOYq" id="dialog" open=""><form class="modal-form s-yu7OS-GWNOYq" method="dialog">

Modal title
 <button class="button is-text is-small is-only-icon s-yu7OS-GWNOYq" aria-label="Close modal"></button>

Modal label text.

<button class="button is-text s-yu7OS-GWNOYq">Button</button> <button class="button is-secondary s-yu7OS-GWNOYq">Button</button>

</form></dialog>
</button>

👍 Expected behavior
it should be looking like this

👎 Actual Behavior
but it looks like this

🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
Linux
🧱 Your Environment
in runnin on a wsl machine, in an astro project, i just copy it from the demo
https://github.com/appwrite/demos-for-astro
and upgraded all dependecys
but even i've seen this behavior on a codepen instance
https://codepen.io/Trongar/pen/BabyWaP
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

even, this is my package.json
{
  "name": "example-blog",
  "type": "module",
  "version": "0.0.1",
  "scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "build": "astro build",
    "preview": "astro preview",
    "astro": "astro"
  },
  "dependencies": {
<EMAIL_ADDRESS>"^0.2.0",
    "@astrojs/mdx": "^2.0.2",
    "@astrojs/rss": "^4.0.1",
    "@astrojs/sitemap": "^3.0.3",
    "@astrojs/svelte": "^5.0.2",
    "@astrojs/vercel": "^6.1.0",
    "appwrite": "^11.0.1",
    "astro": "^4.0.7",
    "nanostores": "^0.8.1",
    "sanitize-html": "^2.10.0",
    "svelte": "^4.2.8"
  },
  "devDependencies": {
    "@types/sanitize-html": "^2.9.0"
  }
}

@Trongar, thanks for creating this issue! 🙏🏼 The dialog Did you add JavaScript code to call the various show/close methods as mentioned in the docs?

Can I work on this ?


fix: upped statamic version

Hey Duncan, Thanks for this, we'll get a release out soon with this change

@benmAltDesign When are you going to release this as a new version? Would be great if you could that soon!

Hey @ceesvanegmond!
We've run into some issues during testing around the data not saving as intended, as soon as we've sorted that, we'll get it released!
Cheers!
Ben

Let me know! We could also do some testing


⚠ Bofrost.at has degraded performance

In 2389574, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2220 ms

Resolved: Bofrost.at performance has improved in 6783463.


DEC-615: Merge exhibit name into collection name_line_1, name_line_2

There don't seem to be any references to exhibit.name other than exhibition. Most objects are already using collection.name_line_1 and name_line_2.

:+1:

:+1:


Pagination bug with ng-animate

Describe the error in 1 sentence
Pagination is showing twice when transition of page change
Steps to reproduce
Inject ng-animate and use  component on page, then click to change page.
What exactly is supposed to happen
Change the active page without the flicking effect
What exactly does happens
The pagination is displayed twice between the transition
A link to a page clearly demonstrating the issue
https://plnkr.co/edit/VKBokHCb5aWOpBGMFgZA?p=preview

Your example page doesn't demonstrate the issue.
And also, I don't know a lot about the pagination directive.
Best bet is to fix it yourself (and please send a PR if you fix it).

add to your sheet style :
.pagination .waves-effect {
transition: none !important;
}


Cannot gracefully logout when "opbs" cookie is not available.

The application sends OIDC logout request to the IS, during the user logout. If the user is already logged out from one application, he will get an error saying "opbs" cookie is not available, while trying to log out from the next application. Tested this in the latest WSO2 IS 5.7.0 WUM pack<PHONE_NUMBER>178).
Also, enable below property in <IS_HOME>/repository/conf/identity/identity.xml

true

Duplicate of https://github.com/wso2/product-is/issues/4118

Closing since this is a duplicate.


Some drun tests do not need to be drun tests (misleading directory name?)

Tests below are in run-drun/ directory, but they're not run with drun or ic-ref so they either not need to be in drun/ or the test configuration is buggy and they're incorrectly skipped.

actor-creation
actor-import
aritybug
chat
control
create-then-trap
general-type-components
inter-query
issue-1938-b
issue-1938-c
issue-1938-d
issue-1938
issue-2158
issue-2319
pass-references
reference-params
scope-example-func-implicit
scope-example-func
scope-example-implicit
scope-example
self-shadow
show-in-actor
test_oneway
unavailable-constructor
unsupported-more
unsupported

Some of them have skip lines for drun and ic-ref. Others skip compilation entirely. Some of them are only type checked even though they don't have any //SKIP directives (e.g. inter-query, these seem buggy). Some of these are also interpreted but the interpreter can't really interpret canister tests so they don't do anything other than type checking.
I'm guessing over time the directory evolved into something for all canister tests (some of them only type checked, some also run). In that case perhaps we should rename it into "canisters" or something like that.
It would be good to understand why tests like inter-query are skipped even though they don't have any //SKIP directives.

Are you sure they are skipped or just don't do any printing? I think Joachim set the tests up to avoid recording empty output files (and really wanted most tests to just assert success rather than producing output to be diffed).
If you examine the ok dir, you'll see that some tests do have output for run, run-ir, and run-low (for example).

inter-query is skipped because it doesn't pass the type checker (it uses nested queries which are currently rejected but were on the roadmap for the ic).

Are you sure they are skipped or just don't do any printing?

I think they're skipped. When we run a test using IR interpreter we print [run-ir]. If it's not printed then that step is skipped as far as I can see. Relevant code: https://github.com/dfinity/motoko/blob/19889cf6dc4866bce1df93254e3e56fad197c48a/test/run.sh#L99-L107
If I'm right then in the tests listed above we skip drun and ic-ref steps. Example:
[nix-shell:~/dfinity/motoko_2/test/run-drun]$ ../run.sh -d chat.mo
chat: [tc] [run] [run-ir] [run-low]
All tests passed.

No drun-run or ic-ref-run here.
So the question is why are these tests in run-drun if they're not run in drun.

inter-query is skipped because it doesn't pass the type checker (it uses nested queries which are currently rejected but were on the roadmap for the ic).

Hm, this is a bit suprising.. So how it works is, if type checking fails we don't run any of the other steps, but if the type checker output and moc exit code is as expected (as specified in "ok" files) then that's OK (test passes). I guess that's fine, I should update my OCaml implementation. (#2684)
I still think at least the name "run-drun" is confusing because it suggests that the tests under that directory should be run under drun. If you look at the Makefile under that directory it runs the tests with ./run.sh -d *.mo *.drun. The -d says "run under drun", but many of these tests (those listed in my original message) cannot be run with drun. I just find it confusing..
I think it makes sense to organize tests based on one of these two:

Language features: if a test was added primarily to exercise e.g. arrays then it would be in a directory like "array". If we do that then perhaps this directory is fine. All of these tests use actors somehow. The name could perhaps be "actor" or something like that.

Compiler features. This means if a test was added primarily to exercise a type checking feature or code then it would be in a directory like "typecheck". It's fine if we still run the test with the interpreters, maybe with drun etc.

Currently what we have is based on how we run the tests (each directory has its own Makefile that passes different parameters to run.sh or have their own testing implementation), but there are cases where we call "run under drun" (run.sh -d) but test isn't run under drun which is what confuses me. It looks like a bug that I call run.sh -d (so the intention is running under drun) but drun step is skipped.

You are correct that the tests have evolved and the name might be misleading.
Some of the test are in here because the type system actually depends on the target to some extent and programs that aren't reject by a vanilla --check or the interpreters are actually rejected because of the target.  Either because the platform doesn't yet or never will support them.
Frankly, I'd prefer it if the language we supported was just what is supported by the platform, which would avoid a lot of this confusion.
So maybe the right way to name these directories are actually by the targeted platform:
run -> wasi
drun -> ic
check -> interpreter
Is it hard to maintain the existing semantics (such as it is) in your ocaml port?

I'm guessing over time the directory evolved into something for all canister tests (some of them only type checked, some also run). In that case perhaps we should rename it into "canisters" or something like that.

Yes, that it is. run-drun simply means “Use the IC system api” (which even affects type-checking) instead of run/, which means “use the wasi api”. Feel free to rename if you find it helpful.


 I have an application as below for performance optimization, but I am encountering errors. Which path should we follow?
pub struct Variation {
    pub id: String,
    pub size: (u32, u32),
}
pub struct VariationResult {
    pub id: String,
    pub buffer: Vec<u8>,
}

fn bulk_process( src_image: &fr::Image, variations: &Vec<Variation> ) -> Result<Vec<VariationResult>, Box<dyn Error>>
{
    let mut image_variations: Vec<VariationResult> = Vec::new();

    let mut result_buffer: Vec<u8> = Vec::new();
    let mut buf_writer = BufWriter::new( &mut result_buffer );
    let mut encoder = JpegEncoder::new_with_quality( &mut buf_writer, 100 );

    let mut resizer = fr::Resizer::new( fr::ResizeAlg::Nearest );

    for variation in variations {

        let dst_width = NonZeroU32::new( variation.size.0 ).unwrap();
        let dst_height = NonZeroU32::new( variation.size.1 ).unwrap();
        let mut dst_image = fr::Image::new(
            dst_width,
            dst_height,
            src_image.pixel_type(),
        );

        resizer.resize( &src_image.view(), &mut dst_image.view_mut() ).unwrap();

        encoder.encode(
            dst_image.buffer(),
            dst_width.get(),
            dst_height.get(),
            ColorType::Rgb8
        ).unwrap();

        let image = VariationResult {
            id: variation.id.to_string(),
            buffer: result_buffer, // ??
        };

        image_variations.push( image );
    }

    Ok( image_variations )

}

Move these lines inside of for-loop:
    let mut result_buffer: Vec<u8> = Vec::new();
    let mut buf_writer = BufWriter::new( &mut result_buffer );
    let mut encoder = JpegEncoder::new_with_quality( &mut buf_writer, 100 );

Is there a way to avoid creating new instances in the loop?

Your question is irrelevant to the fast_image_resize crate. It is more related to the Rust language and how computer's memory works. Value of the result_buffer variable  can't be used  after it is moved into image_variations vector.
How do you want to use the same buffer to store different images at the same time? It is impossible. You must create a new  buffer to store each image.

Thank you, let me modify my question, if the encoder and the resizer holds the logic of how to process images: Is there a way to create only one instance of these two, to use in +100 resize & encode ops. in loop?

You can reuse the memory buffer that is used for dst_image.
let mut dst_buffer: Vec<u8> = Vec:new();
for variation in variations {
    ...
    let dst_buf_size = ...;
    dst_buffer.resize(dst_buf_size, 0);
    let mut dst_image = fr::Image::from_slice_u8(
       dst_width,
       dst_height,
       &mut dst_buffer,
       src_image.pixel_type(),
   ).unwrap();
   ...
}

I think that creating an instance of `JpegEncoder` is a fairly easy operation. But you may look at the `image` crate documentation. May be you can find something about how to reuse exists `JpegEncoder` instance to encode different images.

Thank you!


Sell Everywhere Bugs

When you follow the 'Launch a Metaverse Store' template, after the last steps (setting up DCL), if you exit out of the modal you are taken to the sales channel page. You should be taken to the Seller Center.

done


Priority feature

I had written code that checks if a task is already marked completed or not. If yes, when a user tries to edit the task, it says "Mark as incomplete" instead of "Mark as completed". If no, then it says "Mark as completed". That code somehow is not in your PR. Please merge my password-change branch with yours and make sure that the code is there. Then, create the PR.
Also, when I tested the branch, it looks like if a task already has a priority marked, then the modal that pops up when editing that task will not have the "Mark as Important" checked already and the test still says "Mark as important" instead of maybe "Mark as unimportant" or something like that. Also, If you leave the "Mark as important" unchecked, an important task will go back to being "unimportant".
If a task is not important, then the date and time info comes to the left side of the task box instead of staying on the right. Do we want it that way or should we have the date and time be on the right irrespective of the task being important or not?

@sagarsubedi I just went and checked and I actually had already merged main, so it should have had that code.  I can still see it on day-view.js.  Am I missing something?


error webpack build

Hello there.
I've got this error when i launch cordova run browser:
Before deploy hook started...
Checking is node modules installed...
Node modules already installed.
Starting webpack build...
Error happened when webpack build: Error: Command failed: "C:\Prj\newmultisend\node_modules\.bin\webpack.cmd"

Webpack build completed to www folder successfully!
Error happened on main chain:
Error: Error happened when webpack build: Error: Command failed: "C:\Prj\newmultisend\node_modules\.bin\webpack.cmd"

    at exec (C:\Prj\newmultisend\hooks\hookers.js:184:19)
    at ChildProcess.exithandler (child_process.js:282:5)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:557:12)
Error happened when webpack build: Error: Command failed: "C:\Prj\newmultisend\node_modules\.bin\webpack.cmd"

Win7 / node 8.11.4 / npm  4.1.2 / Cordova 8.1.2

Same error in android for me cant build anything except for IOS platform.

I checked you guys error, sorry by my mistake I forgot to put the material icons library into package.json.
Please use this release: https://github.com/caiobiodere/cordova-template-framework7-vue-webpack/releases/tag/2.0.10


Matching of empty line in JSDoc comments

Here a small reproductible case. The plugin is setup to add the content of this file at the beginning of each file :
Copyright (c) 1998, Regents of the University of California
All rights reserved.

Redistribution and use in source and binary forms, with or without...

However, subsequent use of eslint won't match the comment inserted by the plugin :
/**
 * Copyright (c) 1998, Regents of the University of California
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without...
 */

The issue seems to come from the comment matcher which always expect a trailing space on empty lines for JSDoc comments.
The matcher shouldn't assume the presence of a trailing space because most editors have a trim on save option. Moreover, the plugin comment formatter also trim trailing space when inserting comments.

Thank you for providing this example and explanation, I will work to reproduce this behavior and provide an update within the next few days.

@rubycon I've addressed this issue in v1.0.4, please let me know if you experience further issues.

Thank you very much. It fixes the issue for me!


Job Annotations Longer than 64 char are Truncated

A wrangler bug caused by serializing jobs truncated annotations to 64chars. We will need to roundtrip and pull the job out again in wrangler to make it work properly.

Similar to: https://github.com/rancher/rancher/issues/37766

Reroduce
branch: https://github.com/KevinJoiner/rancher/tree/rancher-wrangler-test

Run custom image kevinjoiner/rancher:v2.6.7-wranger-test-before
navigate to https://<SERVER_URL>/test/wrangler
verify job update fails (Failed to update job DesiredSet - Replace Wait batch/v1, Kind=Job default/wrangler-test for wrangler-test-update)

Validate
branch: https://github.com/KevinJoiner/rancher/tree/rancher-wrangler-test-after

Run custom image kevinjoiner/rancher:v2.6.7-wranger-test-after
navigate to https://<SERVER_URL>/test/wrangler
verify job update was successful (Job update was successfully applied!) .

@sowmyav27 both kevin and tucker dev-validated this, so we should be good to close. This is still tough to test since it's not in the product. We are going to think about how we might add a test around this, but it seems unlikely.


Image upload speed way too slow on phone need a hack

Fixed by setting Nginx resize image, now the image are load with 500px wide.
        location ~ /images/(.*)$ {

            set $width "-";
            set $quality "75";
            if ($arg_w != '')
            {
              set $width $arg_w;
            }
            if ($arg_q != '')
            {
              set $quality $arg_q;
            }
            image_filter resize $width -;
            image_filter_jpeg_quality $quality;
        }


bpf: introduce ctx_load_and_clear_meta()

When handling the metadata that cilium stores into skb->cb, a typical pattern is to (1) first load a field, and then (2) clear the same field.
Add a combined helper for this pattern. This helps to keep the load/store steps in sync, and reduces boilerplate code.
This also brings minor savings for the nodeport.h code that is included into bpf_xdp. For XDP the ->cb is emulated with a BPF map, and the combined helper requires only one map access.

/test

/test


Ae react prototype frontend styling

Review of the latest front end updates

@andrewebdev Went through the list now


Default display of tag groups

Is your feature request related to a problem? Please describe.
When adding tags for each marker, It's quite a hassle to have to add all the tag groups each time.
Describe the solution you'd like
I want the tag group to be the default view.
Describe alternatives you've considered
same above.

There is no tag system in our new Visualizer, so I will close this issue.


Excel.run() Operations Blocked While Data Validation Dropdown Is Open

Description:
I'm developing an Excel add-in using Office.js and I've encountered a problem when a data validation dropdown (list) is open in a cell. While the dropdown is open, all operations triggered via Excel.run() are queued and remain in a waiting state until the dropdown is closed by the user.
I would like to be able to either:

Force Excel.run() operations to execute while a dropdown is open, or
Detect when the dropdown is open and handle the interaction accordingly.

Currently, it seems that Excel enters a modal state while the dropdown is open, preventing any Office.js operations from executing until the interaction is finished. This causes delays in my add-in when users interact with cells that have data validation lists.
Steps to Reproduce:

Create a data validation dropdown in a cell (e.g., A1) using Excel's built-in data validation.
Open the dropdown in that cell.
Try to run any Excel.run() operation, such as setting a value in another cell, while the dropdown is still open.

Expected Behavior:

I expect Excel.run() operations to execute without being blocked, even when a dropdown list is open in a cell.
Alternatively, I'd like to be able to detect when the dropdown is open so that I can prevent or delay the operation until the interaction is complete.

Actual Behavior:

Excel.run() operations remain in a waiting state until the user closes the dropdown.
There’s no clear way to detect that the dropdown is open and handle this in the Office.js code.

Example Code:
Excel.run(async (context) => {
    const sheet = context.workbook.worksheets.getActiveWorksheet();
    const range = sheet.getRange("A2");

    // Open a dropdown (user interaction required)
    // While the dropdown is open, this operation is blocked
    range.values = [["New Value"]];
    await context.sync(); // This operation waits until the dropdown is closed
});

Possible Workarounds:
I've tried some workarounds, such as retrying operations after a delay or handling onSelectionChanged events, but these are not ideal because they do not solve the issue of detecting the dropdown's modal state.
Environment:

Excel: Excel 365 Desktop Version 2408
Office.js: 1.1.91
Platform: Windows

Request:

Is it possible to provide a way to force operations to execute even when a data validation dropdown is open?
Alternatively, can there be a method in Office.js to detect when a dropdown is open so that add-ins can handle this scenario better?

Hi @buzzo123,
Thank you for raising this issue. I don't believe there is an API that will solve your scenario here. I'm going to transfer this issue to the product repo (office-js) so the feature crew sees this.


Testing basic user cases.

For the moment, we would like to validate the full cycle exchange considering our user cases. So, I am moving forward with other tests.
Im trying to implement a few user cases to start to test our user cases and learn how the engine works internally:

Exchange configuration
ExchangeCore exchangeCore = ExchangeCore.builder()
.resultsConsumer(eventsProcessor)
.serializationProcessorFactory(serializationProcessorFactory)
.exchangeConfiguration(conf)
.build();

Adding users to exchange.
We are creating users in our own backoffice.  We will push the UID required mapping it with our own ID. api.submitCommandAsync (ApiAddUser.builder ()). Is working well.
We added two users UID 301 and UID 302 following your examples.

Balance. We are managing deposit and withdrawal into the our own backoffice. We need to maintain syncronized the balance in real-time considering trades and deposit-withdrawals. We are mapping it to the api function api.submitCommandAsync (ApiAdjustUserBalance.builder (). Is working well.

Currency and Symbol definition:
I would like to define once currency pair to start. So, we are defining BTC-USD using CoreSymbolSpecification as follow:

public static final int SYMBOL_EXCHANGE_FEE = 9340;
public static final int COIN_XBT = 3762; // satoshi, 1E-8
public static final int COIN_USD = 840;
public static final CoreSymbolSpecification SYMBOLSPECFEE_XBT_USD = CoreSymbolSpecification.builder ()
.symbolId (SYMBOL_EXCHANGE_FEE)
.type (SymbolType.CURRENCY_EXCHANGE_PAIR)
.baseCurrency (COIN_XBT) // base = satoshi
.baseScaleK (1_000_000) // 1 lot = 1M satoshi (0.01 BTC)
.quoteCurrency (COIN_USD) // quote = usd
.quoteScaleK (1) // 1 step = 1 usd
.takerFee (0) // taker fee 0 usd per 1 lot
.makerFee (0) // maker fee 0 usd per 1 lot
.build ();
Is this configuration right? I don´t understood so good how baseScale should be configured.
I need to add different FIAT currencies. For ARS (Argentinian pesos) and USD (American Dolares) to be exchanged for BTC and USDT (Tether).
Could I configure the takerFee and makerFee as porcentual? I need to charge 0,25% for each transaction as commission.

Place an order Limit GTC.
We are having problems placing orders.

Our JSON definition:
"type":"OE",
"data": {
"uid":301,
"orderId":<PHONE_NUMBER>534,
"price": 9344,
"size": 1,
"symbol": "9340",
"type": "GTC",
"action": "BID"
We tried two ways to do it.
a) With RiskEngine enabled (default config) but is not working.
matching_1 | 2020-05-19 20: 04: 06.741 WARN 1 --- [Thread-R1_0] e.core2.core.processors.RiskEngine:<PHONE_NUMBER>534 risk result = RISK_NSF uid = 301: Can not place OrderCommand (command = PLACE_ORDER, orderId =<PHONE_NUMBER>534, symbol = 9340, price = 9344, size = 1, reserveBidPrice = 9344, action = BID, orderType = GTC, uid = 301, timestamp = 0, userCookie = 0, eventsGroup = 4, serviceFlags = 1, resultCode = NEW, matcherEvent = null, marketData = null)
matching_1 | 2020-05-19 20: 04: 06.747 WARN 1 --- [Thread-R1_0] e.core2.core.processors.RiskEngine:<PHONE_NUMBER>534 accounts: {3762 = 1, 840 = 20}
matching_1 | Command result: IEventsHandler.ApiCommandResult (command = [ADD o3432342343534 s9340 u301 B: GTC: 9344: 1], resultCode = RISK_NSF, seq = 6)
b) With RiskEngine disabled. We are having compilation problem.
We are using your latest version (0.5.0) and we added the configuration with corresponding dependencies.
OrdersProcessingConfiguration.NO_RISK_PROCESSING. I have the follow message as compilation result:
cannot find symbol
[ERROR] symbol: variable NO_RISK_PROCESSING
[ERROR] location: class exchange.core2.core.common.config.OrdersProcessingConfiguration
At the moment we can’t move forward because of these conflicts, I would really appreciate if you can help me to figure out how to fix it!. I don’t sure if must post it as issue on Git because could be only problems in my side.
Thank a lot for your support!

Hello,
Exchange core operates in integers. We know that for BTC smallest integer piece is 1 satoshi, and for USD is 1 cent. So you normally represent balances in satoshi and cents, not in USD or plain Bitcoin.
Then for order book you need to specify the lot size (baseScaleK). If it is 1M like in example above - then every time you say "size": 1 - that means the order size is 1M satoshi, or 0.01 BTC.  So maybe you want to make it smaller.
Similar to the Price: quoteScaleK=1 means price step is 1 cent. So when you send price=9344 - that actually means 9344 * 1 = price is 93.44 USD for 1 lot (size: 1).
In your case core risk engine returns NSF because you have only = 20 cents on the acccount when trying to buy for 9344 price steps (whic is 1 cent, so it 93.44 USD).
For OrdersProcessingConfiguration.NO_RISK_PROCESSING - I need to check, maybe you need to re-import libraries.


Inconsistency in calling "toString" for a ProxyObject

Consider an implementation like this:
import java.util.function.Supplier;

import org.graalvm.polyglot.proxy.ProxyObject;

public class Foo implements ProxyObject {
    @Override
    public Object getMemberKeys() {
        return null;
    }

    @Override
    public boolean hasMember(String key) {
        return key.equals("toString");
    }

    @Override
    public void putMember(String key, Value value) {
        throw new UnsupportedOperationException();
    }

    @Override
    public Object getMember(String name) {
        if (name.equals("toString")) {
            return (Supplier<String>) () -> toString();
        }

        throw new UnsupportedOperationException();
    }

    @Override
    public String toString() {
        return "foo";
    }
}

Using an instance of this type (call it foo) inside JavaScript like so:
console.log(foo);            // outputs "foo"
console.log(foo.toString()); // outputs "foo"
console.log(foo + 'bar');    // outputs "{}bar"

Yields different results. In the first two cases, toString is gotten via getMember and then called. But in the third case, toString is not requested and actually some internal implementation is called which returns {} (because getMemberKeys returns null).
I believe this is a bug and it shouldn't work like that.
Another thing that is somewhat related - Nashorn had a getDefaultValue method that one could override for use in one's own proxies - which could be used to handle cases like foo + 5 (where foo is a Nashron proxy-thingy). Is there such an ability in Graal JS?

Hi,
thanks for your report. This is actually a duplicate of #246 that has already been resolved by https://github.com/graalvm/graaljs/commit/1a407cdcfb1a59e10e6fc1612fe820cea7a84412
The fix will be available in GraalVM 20.1.0, scheduled to be published next week.
Best,
Christian


Fix missing link in docs for icons

Issue Resolved / Feature Added
Fix missing links in docs
Enact-DCO-1.0-Signed-off-by: Stephen Choi<EMAIL_ADDRESS>

All fixed


Harmonise Castle Core and Windsor

Adding missing xml documentation to NuGets and including the documentation in the solution

[wrote similar comment in Castle Core PR]
Windsor 4.1.0 already has XML files for each target framework, the new .NET tooling must automatically generate them, however not sure what is different with Castle Core which also didn't specify the DocumentationFile element.

Yip we can close this.

I did bring the docs into the solution in the other PR anyway. I will double check those also.


List of issues to revisit at the end of merging dev branch

I will use this ticket as a notepad of issues that have been pointed out during the series of PRs into the dev branch, that I intend to return to do (or at least discuss) later, once all of my fork has been merged over. Each bullet point can be broken out as a separate issue later (or just do it).

[ ] All new plugins lack test coverage
[ ] Add an entry in circle.yml that checks that js/impress.js does in fact contain the output of build.js (Check that developer remembered to do node build.js before git commit.)
[ ] Change gc.addCallback to gc.pushCallback
** Btw, gc library could be refactored so that the different types of objects pushed go into the same stack, and are iterated together in teardown, not separately by type.
[ ] Create a ticket for introducing jsdoc for API / code documentation
[ ] Move to uglify-es to support ES6 for minified impress.min.js compilation

I was thinking about something like this. Thanks for creating it!

I have edited the comment to convert to checkboxes and add some inline code markup, hope you don't mind.

Create a ticket for introducing jsdoc for API / code documentation

To that point, we should probably take some care to not tell what the code does internally in the form of comments. I see the value of that for plugin documentation.
You might also be interested in checking out doclets.io.


Implement DirectAssetPath for Release Assets Links

This change set adds support for the direct_asset_path API field for Release Assets Links, see the API documentation here:

https://docs.gitlab.com/ee/api/releases/#create-a-release
https://docs.gitlab.com/ee/api/releases/links.html#create-a-release-link

@svanharmelen do you mind giving this a review and creating a release? We require this in order to unblock 17.0 deprecations. Thanks a bunch!


Quick fix on some json rpc result returning parts

Change summary:

Quick fix on some Json-Rpc result returning parts

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/1053

Thanks for the fast review. Now merging.. @liayoo


Dynamics 365 services configuration

Hi, thanks for building this great thing! Is there any plan to do some automation for Dynamics 365 services in Office 365 subscription? Something along the same lines with this? https://docs.microsoft.com/en-us/powershell/dynamics365/customer-engagement/overview?view=dynamics365ce-ps

@shurick81 being very transparent here, this is not something we currently have on our radars, putting current priority on other workloads. However, it is definitively something we should be looking at in the future. If something from the community wants to take a stab at it, the team and I would be more than happy to review and integrate with the code base.


Additional Accessibility Roles and States

Summary
Assistive technologies use the accessibility role of a component to tell the disabled user what the component is, and provide hints about how to use it. Many important roles do not have analog AccessibilityTraits on iOS. This PR adds many critical roles, such as editabletext, checkbox, menu, and switch to name a few.
Accessibility states are used to convey the current state of a component. This PR adds several critical states such as checked, unchecked, on and off.
Changelog
[general] [change] - Adds critical accessibility roles and states.
Test Plan

Added examples using all new roles. Ensure that both TalkBack on Android and VoiceOver on iOS properly identify the components using the new roles when touched. Add examples of new states, and ensure that state changes speak when the components are double tapped on both iOS and Android.

I didn't use a comma for eventual localization concerns (this whole chunk of code needs a rethink to allow for role and state descriptions to be localized).

Thanks all for the great feedback. We're working on a final set of changes to add native iOS switch support, as well as make some of the suggested code cleanups recommended by @ikenwoo
I expect to have another revision posted by end of day.

@ikenwoo could you please take another quick look to ensure we've adequately addressed your comments? Also, would love your feedback on how we can correctly support localization of the role and state description strings in iOS.
Thanks for all the  great feedback!

Can someone help me understand the purpose of DeprecatedViewAccessibility.js and DeprecatedViewPropTypes.js. these are causing me problems when converting accessibilityStates from an array of strings to an object. Several components, including Button and touchableWithoutFeedback explicitly declare accessibilityStates as an array of deprecated types.
Can we safely remove DeprecatedAccessibility altogether and simply use the definitions in ViewAccessibility instead?

these are causing me problems when converting accessibilityStates from an array of strings to an object

@marcmulcahy I don't think that's necessary for this PR (as mentioned here) or a change that has been requested yet. Changing the accessibilityStates API is something for a later patch if @jessebeach and others on the RN team think it sounds like a good idea and we have a migration/deprecation plan.

OK, I was under the impression that this change was under consideration for this PR, and have the iOS implementation done, and am working on the Android implementation.
What outstanding issues remain on this PR for us to address?

What's the status of this PR? It is fairly large and I realize there is additional work for the future but is the current iteration shippable or are there still certain actions that need to be taken?

To resolve conflicts, is it acceptable to simply rebase this code on top of master and force push this branch?

Yep, that’s the preferred way to do it.

From: marcmulcahy<EMAIL_ADDRESS>Sent: Wednesday, April 24, 2019 6:17:22 PM
To: facebook/react-native
Cc: Christoph Nakazawa; Manual
Subject: Re: [facebook/react-native] Additional Accessibility Roles and States (#24095)
To resolve conflicts, is it acceptable to simply rebase this code on top of master and force push this branch?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/pull/24095#issuecomment-486338551, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAADIKGOUUINRG3IIYO3XUTPSCI2FANCNFSM4HAK7TLA.

@cpojer  It'd be awesome to have this PR and other accessibility improvements into 0.60, such as:

Extended accessibility actions https://github.com/facebook/react-native/pull/24190,
AccessibilityInfo updates https://github.com/facebook/react-native/pull/23839, https://github.com/facebook/react-native/pull/23913.
removal of accessibilityComponentType and accessibilityTraits props https://github.com/facebook/react-native/pull/24344

(I'm also working to submit another a11y PR implementing onAccessibilityFocus & onAccessibilityBlur)

I've got the current code rebased, as well as an implementation which converts accessibilityStates from a list of strings to an object:
<accessibilityStates={['checked', 'collapsed']}> to
<accessibilityStates={{'checked" true, "expanded": false}}>
Should I include that in this PR, or should we consider that as a separate PR?

Let’s do that in a follow-up, this PR is already pretty big.

From: marcmulcahy<EMAIL_ADDRESS>Sent: Wednesday, April 24, 2019 6:55:56 PM
To: facebook/react-native
Cc: Christoph Nakazawa; Mention
Subject: Re: [facebook/react-native] Additional Accessibility Roles and States (#24095)
I've got the current code rebased, as well as an implementation which converts accessibilityStates from a list of strings to an object:
<accessibilityStates={['checked', 'collapsed']}> to
<accessibilityStates={{'checked" true, "expanded": false}}>
Should I include that in this PR, or should we consider that as a separate PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/pull/24095#issuecomment-486358753, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAADIKCFZ4OXM6FAW2WLDWDPSCNKZANCNFSM4HAK7TLA.

OK to delete the a11y-roles-states branch in my fork? Will the code and conversation history be preserved?

Yeah, go ahead!

@marcmulcahy are you planning to make a documentation PR with those updates? (https://github.com/facebook/react-native-website) Please let me know if you need any help on it.

@marcmulcahy @elucaswork After merging I got an internal test failure that a <Button disabled={true} /> was still clickable on Android. Is this something you could look into and send a fix for? I would prefer not to revert this PR.
If you can verify that this is still working as expected, then it may be an issue with our e2e framework, in which case I can look into it.

@cpojer Sure, we'll take a look. I don't think we touched any non-a11y paths, but we'll double check.

@elucaswork Happy to do that, but would like some feedback on #24608 first, as it changes the a11y states API, and is probably close to where we want the API to land longer term.

Thanks Marc,
the failure definitely bisected to a change in this PR but it’s unclear to me whether the behavior actually changed or the test framework needs a change.

From: marcmulcahy<EMAIL_ADDRESS>Sent: Thursday, April 25, 2019 6:39:34 PM
To: facebook/react-native
Cc: Christoph Nakazawa; Mention
Subject: Re: [facebook/react-native] Additional Accessibility Roles and States (#24095)
@elucasworkhttps://github.com/elucaswork Happy to do that, but would like some feedback on #24608https://github.com/facebook/react-native/pull/24608 first, as it changes the a11y states API, and is probably close to where we want the API to land longer term.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/pull/24095#issuecomment-486768205, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAADIKFMUMMOMT4L6O6HUS3PSHUFNANCNFSM4HAK7TLA.

@cpojer Is there a set of tests in the public repo we should be using, or is it as simple as creating a disabled button that shouldn't be clickable on Android?

It should be enough to check whether it works or not on master, yes!

From: marcmulcahy<EMAIL_ADDRESS>Sent: Thursday, April 25, 2019 7:04:07 PM
To: facebook/react-native
Cc: Christoph Nakazawa; Mention
Subject: Re: [facebook/react-native] Additional Accessibility Roles and States (#24095)
@cpojerhttps://github.com/cpojer Is there a set of tests in the public repo we should be using, or is it as simple as creating a disabled button that shouldn't be clickable on Android?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/pull/24095#issuecomment-486777179, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAADIKB4LBHWSRTAXUSLT5DPSHXBPANCNFSM4HAK7TLA.

@cpojer  We were unable to reproduce the problem when we did the following:

OPen RNTester
Select Button module
Attempt to click the disabled button

The button doesn't appear to click either with or without this patch applied.
Happy to troubleshoot this if you can help us re-create the failing test.

Thank you so much! Can you confirm that the disabled state also works correctly on other elements?
I’ll check the internal test again tomorrow and see if we need to fix something up or if it’s the test.

From: marcmulcahy<EMAIL_ADDRESS>Sent: Thursday, April 25, 2019 9:23:42 PM
To: facebook/react-native
Cc: Christoph Nakazawa; Mention
Subject: Re: [facebook/react-native] Additional Accessibility Roles and States (#24095)
@cpojerhttps://github.com/cpojer We were unable to reproduce the problem when we did the following:

OPen RNTester
Select Button module
Attempt to click the disabled button

The button doesn't appear to click either with or without this patch applied.
Happy to troubleshoot this if you can help us re-create the failing test.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/pull/24095#issuecomment-486823477, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAADIKEPSUF2U7TBS44UKUDPSIHM5ANCNFSM4HAK7TLA.

@cpojer We have the test of disabled TouchableOpacity in AccessibilityExamples.js. Cannot repro the problem.

PR to add additional a11y roles and states to the documentation is here:
https://github.com/facebook/react-native-website/pull/912


repFilter() implementation

Implemented repFilter()
Unit tests for repFilter()

WIP; requires fixes for non-passing tests


Release version with support for ES 1.2.4

The version on maven.org seems out of date in comparison to master. Any chance this might be updated?
Thank you.

I've never deployed to maven.org, that's the metrics reporter by the Elasticsearch team which only works over HTTP.
However, I noticed that my maven repo is down. I'll work on getting it back online this evening and update the documentation. Once that's done I'll get the library updated to work with newer versions of Elasticsearch.
Thanks for the using the library! :)

Thank you very much.

The maven repo is back up, please refer to the wiki for more details on how to add the repo to your Maven/Gradle builds.
I've also updated the library to work with Elasticsearch 1.3.9. Please refer to the version compatibility page for more info.
There's an issue with getting it to work with 1.4.4 which I'm investigating.

On my end it looks like the repo is returning a 404.

Not on my end? You're using this URL? -> http://viridiansoftware.com/maven/content/repositories/releases/

It was returning a 404 then I checked again later in the evening and was working fine. Looks good on my end now. Thank you.

No problem :)


React/redux Task Search

:partyparrot:
@tpetr @wolfd @Calvinp

You can delete DateEntry since you pulled out the only place where it was used.
If #1119 is merged before this, you can also delete DropDown - otherwise that PR can do it.

@Calvinp Deleted DateEntry. I'll hold off on DropDown for now.

BOSMM2NGH0JG3QD:app cpomerantz$ eslint controllers/TaskSearch.es6 views/taskSearch.jsx components/taskSearch/* components/common/formItems/ReduxSelect.jsx
...
✖ 82 problems (82 errors, 0 warnings)

Found another file you can delete: LinkedFormItem

If anyone here see any reason why these should two branches not be united, speak now or forever hold thy peace.


Feature: speed up transaction

This PR

Adds a speedUpTransaction method to be able to speed up transactions
Fixes cancelTransaction update since it wasn't working correctly

Codecov Report

Merging #172 into develop will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           develop   #172   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           23     23
  Lines         1499   1512   +13
  Branches       210    210
======================================
+ Hits          1499   1512   +13

Impacted Files
Coverage Δ

src/transaction/TransactionController.ts
100% <100%> (ø)
:arrow_up:

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 2771853...6c5d573. Read the comment docs.


[QUERY] How best to use the apimanagement portion of this sdk

Query/Question
Hi, thanks for this lib, having something higher-level to use than the raw REST API seems great.
I am wondering how best to use the apimanagement portion of this sdk.
Is the main entry point to construct an ApiManagementManager?
If so, from where do I get an AzureTokenCredentials? (per: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/apimanagement/mgmt-v2019_01_01/src/main/java/com/microsoft/azure/management/apimanagement/v2019_01_01/implementation/ApiManagementManager.java#L163)
Or, a RestClient? (per: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/apimanagement/mgmt-v2019_01_01/src/main/java/com/microsoft/azure/management/apimanagement/v2019_01_01/implementation/ApiManagementManager.java#L178)
I imagine this stuff is documented somewhere, but I haven't found it, so a pointer to relevant documentation would be great.
In the mean time, I have found a workaround, constructing an ApiManagementClientImpl out of a TokenCredentials I was able to make out of a SaS token I made on the portal inside our APIM resource. However, this doesn't feel quite right, because I am operating exclusively on objects (inner/impl) from inside the implementation folder and not touching any of the higher-level interfaces outside that directory.
Why is this not a Bug or a feature Request?
Things are working, but the best usage is merely unclear.
Setup (please complete the following information if applicable):

OS: Ubuntu
IDE : Emacs
Version of the Library used:

com.microsoft.azure.apimanagement.v2019_01_01/azure-mgmt-apimanagement "1.0.0-beta-1"

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

@harold you can take a look at this link for how to construct the AzureTokenCredentials: https://github.com/Azure/azure-libraries-for-java/blob/master/AUTH.md#using-applicationtokencredentials

@horold I'll close this issue. Feel free to re-open the issue if you have more concerns. Thanks.

Thanks, that is a very helpful link. I appreciate that.
I will look into the service principal method.
Take care.


JVM crash after device is disconnected when capture in progress

Hello Team, the issue which i am going to describe here  is specific to LINUX OS.
I am running the example sample WebcamPanelExample.java
After a long analysis for many hours and debugging the code, i have gathered the below details, as the scenario is not throwing any type of exception to know what is happening.
Go to the method in getImageBytes() in the file WebcamDefaultDevice.java
The following code snippet grabber.nextFrame() which is a native call to the library from java is silently crashing the application in the below scenario, i have tried with many alternatives like calling the above example in a thread with Thread.UncaughtExceptionHandler etc, even it is not showing any stack trace to me regarding the crash.
Please find the scenario where it is getting crashed.
Plug in the USB camera in to any one of the active USB port, now run the above example and observe the video displayed in a frame, now just simply un-plug the USB camera with out closing the video frame, then the JVM exits/crashes silently without throwing any exception in JAVA.
Here what i have observed was, on LINUX whenever the user disconnects the connected USB camera while it is streaming image byte data to the native library then it might be running in to exception and simply shutting down the parent application as well when the parent hits the snippet grabber.nextFrame().
I have fixed this issue in one of the alternative way specific to LINUX
boolean flag = false;
Pointer<Byte> image = null;
if(grabber.getVideoDevices().get().asArrayList().size() > 0)
{
           DeviceList list = grabber.getVideoDevices().get();
           for (Device device : list.asArrayList())
           {
                      if(device != null && device.getNameStr().contains(name))
                        {
                                    flag = true;
                                    break;
                         }
           }
           if(flag)
           {
                     grabber.nextFrame();
                     image = grabber.getImage();
           }
}

The issue is due to that java is still accessing the  grabber.nextFrame() even in the absence of camera which is disconnected from the machine.
As of now i am preventing the JAVA to access that code in the absence of a specific connected device with which it started interacting.
I have tried with many alternatives to capture the exception, but dint find anything except a blank log, it would be better if the native LIBRARY throws some message to the Java side with which JVM is interacting instead of silently crashing the whole application.
Regards
RAGHU

This issue should be already solved, thus I'm closing this ticket.


  This is less than a second but does bounce the page.  Tried to add the classes required by slick to initialize slider and didn't work.  Is there a way that you can have the slider load horizontally first so that the page does not bounce

Try lazyloading.

Lazyloading's the right answer. A hack I've used in the past is to toggle visibility using the init callback.

.slick-frame {
  visibility: hidden;
}

$slickFrame.on('init', function () {
  $slickFrame.css({visibility: 'visible'});
});
$slickFrame.slick();

Don't use display: none, Slick won't be given a height value for the slides if'n you do.

@nominalaeon thanks for the solution, it did the trick ;) Although it's not the most stylish solution as there is a blank space when the page loads (in the place where carousel will appear). Would be nice to have a preload with the spinner as default feature. Actually, ideally would be to see it in the core version of the plugin ;)

You can also do this in pure CSS using the .slick-initialized class.
.slick-frame {
    visibility: hidden;
}
.slick-frame.slick-initialized {
    visibility: visible;
}

@rphelan did the trick for me!  I spent HOURS trying other hacks to delay loading with js timers, etc.  Thanks a bunch.

@rphelan thanks a ton, probably would have spent hours, before figuring out which approach is best.
Your solutions further tweaked.
.slick-frame {
background: #fff url('../img/carousel-loader/ajax-loader.gif') center center no-repeat;
height: 300px;
overflow: hidden;

& > .generic-item-wrap-class {
    visibility: hidden;
}

&.slick-initialized {
    background: none;
    height: auto;
    overflow: auto;

    & > .generic-item-wrap-class {
        visibility: visible;
    }
}

}

Thanks! @rphelan's fix worked for me, replacing .slick-frame with the class of my carousel.

@rphelan's fix also worked for me. Simple and effective. Another thing to note is to look in the stack of how the script is loading on the waterfall in the network tab or if it's combined with other scripts in any fashion.

for those who are still looking to solve this (and using slick slider on getwid blocks like I do), I've managed to solve my problems with this:
.top-slider {
	animation-name: fade;
  animation-duration: 3s;
	will-change: transform, opacity;
}
@keyframes fade {
  from {
    opacity: 0!important;
    height: 0!important;
    overflow: hidden;
    position: absolute!important;
    display: none!important;
  }
  to {opacity: 1!important;
    height: auto; overflow:
    visible; position:
    relative!important;
    display: block!important;
  }
}

note:

top-slider is a class that I added to my parent wrapper, change it to yours.
you can remove the "!important" rule if you don't need them.


Intel RealSense Viewer crashing, Windows not detecting FRAMOS camera

Required Info

Camera Model
FRAMOS Depth Camera D455e

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Windows 11

Platform
PC

SDK Version
librealsense 2.54.2 RELEASE

Issue Description
Intel RealSense Viewer / Depth Quality Tool has crashed with the following error message:
Unhandled exception escaping from a worker thread!
Error type: Unknown error (-529697949)!

I've downloaded all of the necessary software to enable the FRAMOS Depth camera D455e on my Windows 11.
Downloaded the following below from this site: https://www.framos.com/en/industrial-depth-cameras#downloads
SOFTWARE PACKAGE: Windows (Downloaded)
FIRMWARE: D455e Firmware | Changelog
Also let desktop apps access my camera:

This is my setup to connect the FRAMOS camera to my laptop.

![image (https://github.com/IntelRealSense/librealsense/assets/143027159/2c7bb632-bf3c-4732-b134-517ad8fdd808)
 (This is what's powering the FRAMOS camera).

However, when all of this is done.
If I open my device manager, it does not detect/list the RealSense camera:

...and it also crashes after opening Intel RealSense Viewer with the following error message after I try to add a source and select 'platform camera':
Unhandled exception escaping from a worker thread!
Error type: Unknown error (-529697949)!

Hi @jeannettemayogallegos  Intel are unable to provide technical support for the FRAMOS 'e' range of industrial cameras unfortunately as they are not Intel products and FRAMOS are the appropriate channel to provide support for their cameras.  Please visit their support page at the link below and click the 'Contact Us' button.
https://www.framos.com/en/resources/support
Before you go there though, I recommend first checking the camera privacy settings in Windows to ensure that pernission for the camera hardware to be accessed and permission for applications to access the camera are both set to On.  Instructions for doing socan be found at https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789


feat: case insensitivity option

Fixes #459 by adding a setting to each custom rule which toggles case sensitivity

thank you for the pull request. I am currently thinking of not merging this one because it would add another setting. instead, I would directly implement #456. #456 also fixes your issue right?

Yeah, that would work. Thanks!


MDATP Evaluation Lab permissions

Hello,
I'm the lead trainer for an MSSP, and I've been working to provide training to my teams.  As part of that, I would like to be able to leverage the built-in Evaluation Lab abs Simulations/Tutorials to get folks some hands-on experience with the platform.
According to the documentation ([https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/evaluation-lab]), in order for users to access the lab, they need to have the "Manage Security Settings" enabled in their role.

However, regardless of the configurations of my custom user roles, user cannot even see the "Evaluation and Tutorial" section in the console unless they're assigned the default "Microsoft Defender ATP administrator (default)" role, which then gives them access to EVERYTHING.  Even enabling all of the permissions available for a custom role does not work.

Is there some other permission somewhere that I need to be looking at for this?  Obviously, I can't give all my users platform admin rights.
Thank you.

@dismembered3po. Which article are you referring to?

Most likely this page:

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

ID: 12e5744d-46dd-7f90-e42e-70caf9dd56d2
Version Independent ID: 1a627400-9585-e482-3820-e58f6c172a87
Content: Microsoft Defender ATP evaluation lab - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/evaluation-lab.md
Product: w10
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Yeah, it's
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/evaluation-lab
For whatever reason it didn't show as a link, and for some reason, it's not letting me add it as a link from my mobile at thus point, either.

Fair enough, thanks for confirming. We will just have to wait for someone familiar with the topic, like the document author or the MS Docs technical writers (or possibly other experienced users of the technology) to reply and suggest what needs to be done here.
Please also note that the primary purpose of this repository is to improve the documentation by suggesting improvement changes to the document pages.

@illfated
Fair enough.  I'd be satisfied with either figuring out what I'm missing or with the documentation being updated to reflect what's what.

Very well. I would like to take this small opportunity to explain why your URL did not show up as a link in your main post. Here on GitHub, the URLs do not need to be enclosed in brackets to show up as clickable links, you simply post them as they are (use the Preview feature of a post to see when any URL can be read as a clickable link). I don't know whether you are going to use GitHub for other purposes than posting issues you find, but it may come in handy to read about Git Flavored MarkDown (GFM) to see what you can do when editing a post or comment to add practical code blocks or URLs when adding content examples and references.

2 conditions must be met for each user to see eval lab:

Sufficient role (‘ViewData’ for RO, ‘Managed security settings’ for RW \ full access)
Must have access to All machine groups, if the tenant has enabled RBAC V2 and created at least a single machine group.

My guess is condition 2 is not met.

@mjcaparas  Thanks for the info here.  I'll take another shot at this.

@mjcaparas Yep.  That certainly worked better.
I think the documentation should include the information about the device groups, as well.


rattler-build tar error in windows-latest CI

name: CI

on:
  push

jobs:
  test:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - uses: mamba-org/setup-micromamba@v1
        with:
          environment-name: test
          create-args: rattler-build=0.6.0
          init-shell: powershell
      - run: rattler-build build -r conda.recipe/recipe.yaml
        shell: powershell

with conda.recipe/recipe.yaml:
# yaml-language-server: $schema=https://raw.githubusercontent.com/prefix-dev/recipe-format/main/schema.json
context:
  name: polarify
  version: 0.1.3

source:
  - url: https://github.com/quantco/polarify/archive/refs/tags/v${{ version }}.tar.gz
    sha256: 93441164c23b764d72c8a66d14b11d5bbd353ed6112ccf3b35efda2a98f9df02

outputs:
  - package:
      name: ${{ name }}
      version: ${{ version }}
    build:
      noarch: python
      script:
        - python -m pip install . --no-deps --ignore-installed -vv --no-build-isolation --disable-pip-version-check
    requirements:
      host:
        - python >=3.9
        - pip
        - hatchling
      run:
        - python >=3.9
        - polars >=0.14.24,<0.20
    test:
      requires:
        - pip
      commands:
        - pip check
      imports:
        - polarify

about:
  homepage: https://github.com/quantco/polarify
  license: BSD-3-Clause

Has the CI error:
No target platform specified, using current platform
Found variants:

polarify-0.1.3-pyh4616a5c_0
╭─────────────────┬─────────╮
│ Variant         ┆ Version │
╞═════════════════╪═════════╡
│ target_platform ┆ noarch  │
╰─────────────────┴─────────╯

Fetching source from URL: https://github.com/quantco/polarify/archive/refs/tags/v0.1.3.tar.gz
Validated SHA256 values of the downloaded file!
Error:   × Failed to extract archive: Failed to extract archive: D:\a\ci-test\ci-
  │ test\output\src_cache\v0.1.3_93441164.tar.gz.
  │ Stdout:
  │ Stderr: /usr/bin/tar: Cannot connect to D: resolve failed
  │

Error: Process completed with exit code 1.

See also https://github.com/pavelzw/ci-test/actions/runs/7151774641/job/19476405561

I added a test but couldn't reproduce this so far: #412

Can you reproduce it with the ci workflow that I've described?

This should be fixed with new archive write and read changes. Feel free to reopen if you can still reproduce it. cc: @pavelzw

Seems to work, thanks @swarnimarun!


Provide a mechanism that allows the package to be un-managed

Provide a mechanism that allows the package to be managed

@dylanratcliffe FYI


BUG: E5108 Error executing lua .../are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:2: module 'nui.line' not found

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
NVIM v0.10.0-dev Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 Run "nvim -V1 -v" for more info
Also tested the behaviour with builds from source (even v0.9.5 release did not work, not even with deleted caches).
Operating System / Version
Windows 10 with WSL2 Ubuntu 22.04 LTS - using bash
Describe the Bug
Whenever a neotree command is entered, a traceback is shown instead of the UI that should open. This makes the plugin unusable. As I had to use the "unstable" 0.10 version of neovim (ubuntu/debian packages are outdated by a mile and I now use the "unstable" build) this might be a problem on neovims side, but due to me being extremely new to neovim (I was trying to follow this tutorial series on how to setup neovim), I can't figure out, what exactly is going wrong...
Screenshots, Traceback
E5108: Error executing lua ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:2: module 'nui.line' not found:
        no field package.preload['nui.line']
cache_loader: module nui.line not found
cache_loader_lib: module nui.line not found
        no file './nui/line.lua'
        no file '/usr/share/luajit-2.1.0-beta3/nui/line.lua'
        no file '/usr/local/share/lua/5.1/nui/line.lua'
        no file '/usr/local/share/lua/5.1/nui/line/init.lua'
        no file '/usr/share/lua/5.1/nui/line.lua'
        no file '/usr/share/lua/5.1/nui/line/init.lua'
        no file './nui/line.so'
        no file '/usr/local/lib/lua/5.1/nui/line.so'
        no file '/usr/lib/x86_64-linux-gnu/lua/5.1/nui/line.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file './nui.so'
        no file '/usr/local/lib/lua/5.1/nui.so'
        no file '/usr/lib/x86_64-linux-gnu/lua/5.1/nui.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        ...are/nvim/lazy/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:2: in main chunk
        [C]: in function 'require'
        ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:4: in main chunk
        [C]: in function 'require'
        ...nvim/lazy/neo-tree.nvim/lua/neo-tree/sources/manager.lua:6: in main chunk
        [C]: in function 'require'
        ...re/nvim/lazy/neo-tree.nvim/lua/neo-tree/command/init.lua:3: in main chunk
        [C]: in function 'require'
        [string ":lua"]:1: in main chunk

Steps to Reproduce

Install Neovim with the PPA sources (unstable) for Ubuntu (otherwise too old for most plugins)
Create Linked init.lua in ~/.config/nvim
Install neotree via lazy
Try to execute any neotree command

Expected Behavior
Neotree commands should not throw traceback, but rather open the usual "UI".
Your Configuration
-- Set tabs to 4 spaces
vim.cmd("set expandtab")
vim.cmd("set tabstop=4")
vim.cmd("set softtabstop=4")
vim.cmd("set shiftwidth=4")

-- Set Leader
vim.g.mapleader = " "

-- Packet-Manager - lazy
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({
        "git",
        "clone",
        "--filter=blob:none",
        "https://github.com/folke/lazy.nvim.git",
        "--branch=stable", -- latest stable release
        lazypath,
    })
end
vim.opt.rtp:prepend(lazypath)

local plugins = {
    {
        "catppuccin/nvim",
        name = "catppuccin",
        priority = 1000
    },
    {
        "nvim-telescope/telescope.nvim",
        tag = '0.1.5',
        dependencies = { "nvim-lua/plenary.nvim" }
    },
    {
        "nvim-treesitter/nvim-treesitter",
        build = ":TSUpdate"
    },
    {
        "nvim-neo-tree/neo-tree.nvim",
        branch = "v3.x",
        depenedencies = {
            "nvim-lua/plenary.nvim",
            "nvim-tree/nvim-web-devicons",
            "MunifTanjim/nui.nvim"
        }
    }
}
local opts = {}

require("lazy").setup(plugins, opts)

-- Theming
require("catppuccin").setup()
vim.cmd.colorscheme "catppuccin"

-- Telescope
local t_builtin = require("telescope.builtin")
vim.keymap.set('n', '<C-p>', t_builtin.find_files, {})
vim.keymap.set('n', '<leader>fg', t_builtin.live_grep, {})

-- Tree Sitter
local ts_config = require("nvim-treesitter.configs")
ts_config.setup({
    ensure_installed = {
        "lua",
        "c",
        "cpp",
        "python",
        "go",
        "java",
        "zig",
        "rust",
        "cmake"
    },
    highlight = { enable = true },
    indent = { enable = true }
})

-- Neo Tree
vim.keymap.set('n', '<C-n>', ':Neotree filesystem reveal left<CR>', {})

Sorry for wasting anyones time... I found a typo in my config - therefore it did not install the dependencies... :/

Sorry for wasting anyones time... I found a typo in my config - therefore it did not install the dependencies... :/

For what it's worth, you saved me time, because you made me realise I was wasting my own time as well :D


Kill unnecessary SMPP protocols and factories

We currently have six SMPP protocols and factories (two layers, three variants of each) and we only really need one.

This is general cleanup work to make #965 less messy.

:+1:


Feature/add basic website

In this pr, I am trying to build a basic leaderboard website following these requirements:
Create an npm project with webpack.
Write plain HTML markup with minimum styling
Basic UI
Use ES6 modules, with import and export.

I really think this should be optional @Strangeal


Reword changelog entries

Improve the text for the changelog files.

I added one commit with some polishing, feel free to squash it or just pick what you want.

Thanks!


Operation cannot be fulfilled on validatingwebhookconfigurations "istio-validator-istio-system"

Bug Description
As part of Kyma installation, we install Istio in our managed k8s clusters. For quite some time we get alerts that are fired because of errors in the istiod pods.
Currently I could reproduce the issue with Istio 1.16.1 on a kubernetes-1.25.4 cluster on GCP.
There were similar issues already reported, but somehow it did not get solved, acknowledged or prioritised. The errors we get are:
2023-01-25T15:57:37.606056Z	error	validationController	Failed to update validatingwebhookconfiguration istio-validator-istio-system (failurePolicy=Fail, resourceVersion=131167): Operation cannot be fulfilled on validatingwebhookconfigurations.admissionregistration.k8s.io "istio-validator-istio-system": the object has been modified; please apply your changes to the latest version and try again
2023-01-25T15:57:37.606156Z	error	klog	Operation cannot be fulfilled on validatingwebhookconfigurations.admissionregistration.k8s.io "istio-validator-istio-system": the object has been modified; please apply your changes to the latest version and try again

Issue happens on our multi-AZ (multi-node) k8s clusters where have istiod deployment scaled to 2.
You can easily reproduce it, by installing Istio via istioctl, scale the istiod deployment with replicas=2 and reinstall Istio with istioctl. Problem appears to be related to concurrency when both pods are starting and trying to update validatingwebhookconfigurations, a race issue.
https://github.com/istio/istio/blob/f6d7bf648e571a6a523210d97bde8b489250354b/pkg/webhooks/validation/controller/controller.go#L434
This issue is not critical and may be considered with medium priority, but we think you should prioritise it and fix it. Many thanks in advance.
Version
❯ istioctl version
1.16.1

❯ kubectl version --short
Client Version: v1.25.2
Kustomize Version: v4.5.7
Server Version: v1.25.4

Additional Information
No response

Do you get an error log or genuine  issue in the system?
Software that is behaving correct has errors; as far as I know Istio is tolerant to these errors so this seems at worst a poor logging scope (error instead of warning)? Is that accurate

To your first question: no. This is just an error log in the istiod pod logs that is triggering alerts.
We may assume that if it is concurrency issue, it is not really critical since the resource being applied it is the same in the end. In the end it is more or less poor logging scope. You can evaluate if it could be more dangerous in certain cases if applied at the same time from two+ pods.
You should at least keep an eye on this one and prioritise it in your backlog.


Support iOS short task execution

iOS supports running short tasks in a way that gives them a little extra time to complete if the app moves out of the foreground.
iOS Docs:
https://developer.apple.com/library/archive/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/BackgroundExecution/BackgroundExecution.html
Flutter should support the ability to schedule tasks on the Dart side in a way that they will take advantage of this iOS feature. This can either be built into Flutter or built as a plugin.

CC @xster @dnfield


2FYH

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
2FYH

Source
Vaaran Bhai Gurdas Ji

Page
23

Line
rwm cMdu nwau lYˆidAW; iqMin hiqAw qy hoie inrwly [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

Correction:
rwm cMdu ≠ rwmcMdu
lYˆidAW ≠ lYNidAW
Proof:
Vaaran Bhai Gurdaas Ji | November 2011 | Shamsher Singh Ashok | SGPC, Sri Amritsar
Image:


[QUERY] Microsoft.Azure.WebJobs.Host.Storage vs Microsoft.Azure.WebJobs.Extensions.Storage.Blobs

Query/Question
I'm super keen to start using the Microsoft.Azure.WebJobs.Extensions.Storage.Blobs and Microsoft.Azure.WebJobs.Extensions.Storage.Queues packages as they natively support Azure Identity, which would allow us to have credential-less WebJobs.
I'm confused about the feature parity between Microsoft.Azure.WebJobs.Host.Storage and Microsoft.Azure.WebJobs.Extensions.Storage.Blobs.
I understand the new packages provide for a ready-to-use replacement for blob/queue bindings and triggers, but I'm not sure about the hosting aspect.
Microsoft.Azure.WebJobs.Host.Storage has a .AddAzureStorageCoreServices() method which "makes the Runtime itself use storage for its internal operations".
Unfortunately, this method uses the v11 SDK, which only supports authentication to the storage account via a connection string.
Do the new .AddAzureStorageBlobs() and .AddAzureStorageQueues() methods provide the same capability?
I found this piece of test code which calls boths methods: https://github.com/Azure/azure-sdk-for-net/blob/d263f23aa3a28ff4fc4366b8dee144d4c0c3ab10/sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Scenario.Tests/tests/BlobBindingEndToEndTests.cs#L704-L714
A few questions to try and summarise my confusion:

What benefits does calling .AddAzureStorageCoreServices() have?
What do we risk losing if we decide not to call it in our WebJobs?

/cc @pakrym as he seems to be the one working on these integrations.
Environment:

Name and version of the Library package used:

Microsoft.Azure.WebJobs.Extensions v4.0.1
Azure.Storage.Blobs v12.8.0

Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): App Service using .NET 5
IDE and version: VS 2019 v16.9.1

Thank you for your feedback.  Tagging and routing to the team best able to assist.

@mderriey There's still work pending to support Azure Identity end to end in functions. Please see https://github.com/Azure/azure-functions-host/issues/6423#issuecomment-773659251 for more details.

Please re-open if you have further questions.


1Password Fails to Register

Version(s) affected
N/A
Description
While implementing the web-auth/webauthn-lib lib on a custom PHP application, we ran into 1Password not being able to generate passkeys and noticed the demo is affected as well. From our testing, if pubKeyCredParams is empty, 1Password is unable to generate passkeys. Once we added algorithms, it works. Since 1Password is quite popular, it's probably worth revisiting if a default algorithm list should be included by default, instead of being empty. Or at least providing documentation that it's likely required for some services, such as 1Password.
How to reproduce

Have the 1Password extension installed (tested with Chrome and Firefox)
Navigate to https://webauthn.spomky-labs.com/register
Fill out form and press Register
Click on Save when 1Password asks to save the passkey

The following should appear in the console.
Port Opener: passkey-save-prompt/1qcm68e received error: "create-passkey-failed"
The screenshot below is what the dialog should look like.

Possible Solution
As mentioned in the description, supported algorithms should likely be included by default.
Additional Context
No response

Looking a bit further into this, https://developer.mozilla.org/en-US/docs/Web/API/CredentialsContainer/create#pubkeycredparams is a required property, and is an array of algorithms supported by the RP.
Here's the options coming from the demo:
{
    "rp": {
        "name": "demo",
        "id": "webauthn.spomky-labs.com"
    },
    "user": {
        "name": "gborsHd4mEMyyf89IFck7pG4buc8eYhjBOp36AJnmCg",
        "id": "MDFIUVAzSFpDQllFUUI0SDY2Rko2OFdYTTU",
        "displayName": "gborsHd4mEMyyf89IFck7pG4buc8eYhjBOp36AJnmCg"
    },
    "challenge": "5aU_Bx1J58fBNrgZUEjxvW1qhMJrt0s378DllM1Vji8",
    "pubKeyCredParams": [],
    "authenticatorSelection": {
        "requireResidentKey": false,
        "userVerification": "preferred",
        "residentKey": "preferred"
    },
    "attestation": "none",
    "extensions": {
        "uvm": true
    },
    "status": "ok",
    "errorMessage": ""
}

This appears that the RP in this case doesn't support any algorithms. So in this case, I feel like 1Password's implementation is correct.

Hi,
Many thanks for your feedback. That's really interesting 🤔. As per spec, when the algorithm list is missing, default algs that are namely ES256 and RS256 should be used.

I must have missed that earlier when I was reviewing the spec. But I agree. So in this case, 1Password isn't following the spec properly.  In the meantime, I don't know if it's worth updating the demo to include algos so it at least functions for people seeing if the lib works with 1Password.

I don't know if it's worth updating the demo to include algos so it at least functions for people seeing if the lib works with 1Password.

Indeed. I then it is a good idea to set a curated list of algs.


Code before the workers are not showing in the Low-Code view in VS Code, including the workers

Description:

In Ballerina Low-Code view in VS Code, the code before the workers are not showing in the graphical view, including the workers.

Steps to reproduce:
See this code.
import ballerina/io;

public function main() {

    future<int> futureResult0 = start foo();
    int|error unionResult0 = wait futureResult0;

    int a = 3;
    io:println("In function worker");

    worker A {
        io:println("In worker A");
    }

    @strand {
        thread: "any"
    }
    worker B {
        io:println("In worker B");
    }

    future<int> futureResult = start foo();
    int|error unionResult = wait futureResult;

    io:println("In function worker");
    int b = 3;
    io:println("function end");
}

function foo() returns int {
    return 4;
}

Affected Versions:
Plugin version: v3.0.0
Ballerina 2201.0.2 (Swan Lake)
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

The fix is available in https://github.com/wso2/ballerina-plugin-vscode/releases/download/v3.0.1-preview-m18/ballerina.vsix


Release 20180528 runtime error: TypeError: cannot use a string pattern on a bytes-like object

When I'm using the latest (20180528) release I get this error:
Traceback (most recent call last):
  File "dnstwist.py", line 990, in <module>
    main()
  File "dnstwist.py", line 845, in main
    dfuzz.generate()
  File "dnstwist.py", line 483, in generate
    self.__filter_domains()
  File "dnstwist.py", line 275, in __filter_domains
    if self.__validate_domain(d['domain-name']) and d['domain-name'] not in seen:
  File "dnstwist.py", line 266, in __validate_domain
    return allowed.match(domain.encode('idna'))
TypeError: cannot use a string pattern on a bytes-like object

Executing: python dnstwist.py amazon.com
I am using a dedicated virtual environment with requirements.txt installed according to the README.
Python version is 3.6. I also tried in a venv with Python 3.4, it equally fails.

Same environments ran successfully once I checked out tag v1.02.

Could you please try with Python 2.7?

It does work with Python 2.7.

Same issue for me - with Python 3.6. it does not work because of the error mentioned above. Would be great to have it fixed... :-)
Thank you!

I'm going to convert the code to Python 3 but can't give any estimate at the moment.


How to run the mongodb chart as statefulset / prevent pvc from being deleted

I would like to run a simple mongodb instance in my stack but I want to prevent the pvc from being removed when I run helm delete --purge on the release and instead be used again if the same release is deployed.
helm/charts/incubator/orientdb works exactly as I want to, using statefulset instead of deployment. Can I do the same with mongodb. If not, why not?
I'm not interested in extra complexity / load by having multiple replicas, unless you convince me somehow to do so (I saw that replicaSet.enabled: true makes the nodes use statefulsets). For larger scale production the db would probably not be located in the same cluster for us anyways.
If this is not possible to configure, can I make something in my own chart to prevent the pvc from being removed on helm delete? I know it's possible to provide your own pvc to the mongodb chart. But how can I create a template for a pvc to prevent it from being deleted? Statefulset should be used on the actual service, not only for the volume, no?
I'm quite new to helm, so I might have missed something.
Oh, I also didn't find a "question" issue type. So if this is the wrong place for questions, please direct me to the right place.
Thanks for any advice on this!

Hi @dargolith
The MongoDB chart supports to be installed as a statefulset (indeed three statefulsets: one for primary nodes, one for secondary nodes, and one for arbiter nodes). To do so, you need to ensure the replicaSet.enabled parameter is set totrue.
You can find more information in the link below:

https://github.com/helm/charts/tree/master/stable/mongodb#replication

can I make something in my own chart to prevent the pvc from being removed on helm delete?

If you're using a statefulset which uses volumeClaimTemplates, the helm delete command won't remove the generated PVCs.

@juan131 Thanks for your answer! However, as I wrote I'm not interested in the extra complexity, maintenance, increased load, increased cloud storage that replica-sets offer.
In the case I need high availability, I would run a dedicated mongodb cluster, or use some serverless cloud db.
I rather want something that can be included in my application stack for earlier stages of use cases (PoCs, Demos, Early pilots, etc). But even in those cases, I want to prevent accidental loss of data in the case someone wanted to re-deploy (delete / install) the chart.
When reading guidelines for when to use statefulset and when to use deployments, a database service very much sounds like it should use statefulset as default.
I understand the convenience of cleaning up all resources in the case of testing and what not. I would be perfectly fine with an option to use statefulset instead. Even though I would recommend using statefulset as default I'd be happy if I had configure it.
Is there some reasoning behind the choice?

Pull request now available: https://github.com/helm/charts/pull/18669


Added corporations and empires to the mix.

I added some corporation and empire namegen stuff. Hope someone finds them useful!

W00t! Thanks!

Bonus output from the military unit generator:
General's South Blazing Fury
Queen's Supreme Rejects
Emperor's Own 169th Battalion
General's Jolly 668th Shock Troops
Star King's Celestials Regiment
Governor's Supreme Executioners
Chancellor's Crimson Deathbringers
Star King's Excellers Hussars
The Temple's Celestials 430th Defenders
Governor's First and Last Carabiniers


App shutting down on opening

Is there supposed to be an application or command window running when i run the exe? I dont know if it even works bc i click the exe and theres only a brief second of an app trying to open but closes again. Dont see any processes running either. On w11

Is there supposed to be an application or command window running when i run the exe? I dont know if it even works bc i click the exe and theres only a brief second of an app trying to open but closes again. Dont see any processes running either. On w11

It should open a console window with the phrase "Process: Blacklist_DX11_game". You must leave the window open for the application to find and fix your running instance of Splinter Cell Blacklist. If it's not staying open then I would recommend trying to install the Microsoft .NET 7 runtimes onto your system. You should be able to download the different runtime versions from Microsoft's website: https://dotnet.microsoft.com/en-us/download/dotnet/7.0

Got it to stay open. Forgot to mention I'm using it for SC conviction. Works incredibly well


nit: fix typo

minor typo

Considering the comments in https://github.com/cloudflare/workers-sdk/issues/2762 I'm going to close this, I believe that the code comment is actually correct and that the implementation is incorrect, if that turns out to not be the case it would be trivial to reopen or recreate this PR.

Let's just merge this as it accurately describe what the code does right now; and then look at whether we need to fix the behaviour afterwards.


HAAR-1033: ⬆ update to spring boot 3.0.0

HAAR-1033: ⬆ update to spring boot 3.0.0
HAAR-1033: ⬆ update java version used in circleci
HAAR-1033: ⬆ update java version used in circleci
HAAR-1033: ⬆ update java version used in circleci
SDI-477: ⬆ Bump versions and remove pinning
SDI-477: ⬆ Change to a major version upgrade

Closing in preference to having a spring-boot-3.0.0 branch

actually https://github.com/ministryofjustice/dps-gradle-spring-boot/pull/226


AppHub Android support?

The description for this repo mentions Android, however the instructions for creating a new build do not mention Android, nor do the quick start instructions (but there are Java instructions for Configuration (Native SDKs) article). There is a separate branch marked android that hasn't been touched in months.
I can't find any announcements or discussion indicating either way.
Apologies for the loose interpretation of "issue", but I am choosing to place this here as it will be indexed by Google and is likely to get a response that will help others answer the same question.

Thanks for creating the issue!
We currently don't support Android, and the docs still have the vestiges of
our work in progress. We recommend that developers who wish to do
instant Android updates use the fantastic Microsoft CodePush service.
Sorry for the confusion-- we will keep this issue updated with our progress
on AppHub Android support.
On Friday, August 5, 2016, greenatwork<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

The description for this repo https://github.com/AppHubPlatform/apphub
mentions Android, however the instructions for creating a new build
http://docs.apphub.io/v1.0/docs/apphub-cli do not mention Android, nor
do the quick start http://docs.apphub.io/ instructions (but there are Java
instructions for Configuration (Native SDKs) article). There is a separate
branch marked android
https://github.com/AppHubPlatform/apphub/tree/android that hasn't been
touched in months.
I can't find any announcements or discussion indicating either way.
Apologies for the loose interpretation of "issue", but I am choosing to
place this here as it will be indexed by Google and is likely to get a
response that will help others answer the same question.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AppHubPlatform/apphub/issues/29, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWDP908miuPXGnSGh_HjMuSVNRM0Muwks5qc1qngaJpZM4Jdzz7
.

--
Matt (mobile)

Thanks for getting back to me so quickly. This clarifies things perfectly, thanks.

I suggest removing the mention of Android from the issue description until such time as it is supported.

"repo description", even. Sorry.

This mislead me, too. What a bummer...

+1

+1

@arbesfeld, there's now a handful of devs here complaining that they were mislead into thinking that AppHub would work for Android. It is definitely a worthwhile use of your time to at least remove the /Android from the GitHub repo description so that you're no longer making an outright false claim about AppHub's platform support; that will take you 15 seconds and may save several developers from wasting hours implementing a solution that won't work. (That's leaving aside the fact that you're currently falsely marketing a commercial product; while it looks to me like it's ended up that way simply because you moved on to other things before implementing Android support, rather than through any dishonest intent, you still have an ethical duty to remove that false marketing, in my view.)


⚠ Bofrost.de has degraded performance

In 15dd35c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1357 ms

Resolved: Bofrost.de performance has improved in 7bab80a.


Rework date parsing

This addresses #169 and reworks date parsing.
Alternative implementation of #175.

Hi @evpaassen, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

I would suggest much more unit-tests when shortening the code like this.

But the tests cover almost all the cases. I also made sure all cases from the original method are supported. The main thing is that we don't need to parse the timezone suffix manually as this is already supported by SimpleDateFormat.
This code is actually close to the original, and doesn't refactor between methods.

have to admit I like the shortened version most. @evpaassen for future PR I would appreciate if you add comments and thoughts to a given PR before we break down to competitions. Since both of these PR reference the same issue and there is only a small difference between them.

there is one huge difference... https://github.com/OfficeDev/ews-java-api/pull/176 does not fix issue https://github.com/OfficeDev/ews-java-api/issues/169 since it does not implement fixes for the recurring appointments.

I leave it up to you how you handle this. Maybe another solution could be if @evpaassen creates a PR on your PR @ahaarrestad.

@serious6 Let's have this clear. This is not about competition, or credits or anything. Sometimes it's just easier to explain a different concept with an example. I'm just trying to be helpful here.
@ahaarrestad The tests are of course heavily inspired by your tests, as those were looking quite nice. I took one test from yours and adjusted it to verify every pattern supported by the old and new parsing code.

there is one huge difference... #176 does not fix issue #169 since it does not implement fixes for the recurring appointments.

Doesn't it? It should be fixed by f7a7c52. testStartDateWithTimeZone() and testStartDateWithTimeZoneWithColon() seem to verify it's fixed, not?

Your fix won't handle the actual problem that occurs if the recurring appointment contains different timezones in the string. Thus my change from the old parsing to the reworked one.

@serious6 your call on how to continue https://github.com/OfficeDev/ews-java-api/pull/175 vs https://github.com/OfficeDev/ews-java-api/pull/176

OK, I reworked it a little bit again. I guess I misunderstood the original issue a little bit. It should fix #169 now, though.
It contains an additional fix for date-only parsing when the date string has no timezone. The library should then assume UTC instead of local timezone. This bug was fixed for date-time string already in #6.

@evpaassen, @ahaarrestad  hi I aprreciate both of your contributions and encourage on this topic. Thanks for that in advance.
For solving this kind of problem we ran in yesterday maybe @ahaarrestad can provide a test which underlines the expected behavior for the recurring appointment problem, since he pointed out that this PR does not include the fix for this problem. After the integration is done or disproved maybe we can have a merge on @evpaassen PR because it contains the "easier"-implementation for the parsing methods. I dont think it is usefull to merge both of the PR. What do you think of this?

I'll close my pr with refs to this one.

@evpaassen are you finished with this? Thanks for the refactoring. I think it´s even better now.

Yes, I'm finished now.

Thanks for the contribution @evpaassen , @ahaarrestad
Merged with 21c7b0dacc9fb7ac5eb65fe8ee24adb544f9f52e

@ahaarrestad Thank you very much for your collaboration on fixing this issue. I really appreciate it.

@evpaassen and @ahaarrestad great to see us fixing issues as well as making the API and testability better.  I was a bit late to the party, but I've added a couple of comments anyway that we can possibly address as a follow up.


Update to Laravel 9 please?

Could you update it to laravel 9 please?

Any workarounds?

@goyote @AbdelzaherMuhammed It's just a my fork of this library, you should replace this for official or fork it


Merging "whitespacey" tests

There are three different tests: space-after-comma, trailing-whitespace and perl-nbsp. They kinda do the same: read lines in a file, check for stuff, consider exceptions. space-after-comma.t is the coolest (great job, @coke and @zoffixznet) doing stuff asynchronously, using promises.
Could we maybe graft the other two into the first and refactor so that we can easily check for regexen + exceptions in a single file?

Sidenote: when you tag people with @username, you're forcefully subscribing them to all the notifications on that particular Issue. If you need to solicit a response from a person, then sure, tag them, but it's somewhat antisocial to force them to read notifications they're not interested in—especially since some Issues have a lot of content the user needs to read in full before figuring out why notification came up in the first place.

Besides kudos for that program, since you have created the main test I refer to, I kinda do need a response from you. It's your test, after all.

you have created the main test [...] It's your test, after all.

I think what you're seeing is me fixing the typo in the filename, which make me show up as the first commit in history for the current file, but history for previous filename name shows it was [Coke] who created it.

If someone wants to try to combine these files, that's fine, we can theoretically run everything faster,  but I'm not going to spend cycles on it.

I do have to spend cycles around here anyway, so I might as well do it here if it's OK with everyone.

I have been having a look at this today, including trailing-whitespace.t inside space-after-comma.t. Ultimately managed to make it work, but the problem is that the former is processing the file with --doc, while the latter works with it in raw fashion. That, and the fact that it's doing a single test per file are both problems, but the latter is doable.
Several options here: First one is to just not process the file using perl6 --doc, for which I fail to see a good reason. Second is to take that one out of the triad and just merge trailing-whitespace and perl-nbsp.
Thirds of course is to forget the whole thing and just close the issue while there are 272 other things to do.


/ignore still showing the ignored players messages

Describe the bug
Putting someone on your /ignore list doesn't stop you from seeing their messages.
To Reproduce
Steps to reproduce the behavior:

/ignore someone
Still see their chat

Expected behavior
Not able to see their chat.
Screenshots

Username:
Oryso
Server name (all applicable):
Orion
Logs:
Not sure if needed, if so let me know.

Use [P] to hide messages from a player while in the same server as them

fowarded this to tracker to see if a global /ignore is possible, but workarounds with [P] menu are needed for now


Add kumo blades that are a part of a Chassis

The recommended way of doing that in netbox is to create a parent device that supports bays (the chassis) and consumes Rack space. Then the blade servers are of 0U height that are assigned the bay in the parent device.

I have registered the chassis and a node that we have access to. Rest of the blades will be registered when I figure out #12


Bug: canonical URL metadata value is [object Object]

Project
ngx-meta
What happened?
Provided a default canonical URL as a URL object*. Then, provided a canonical URL in some page's route metadata as a URL object.
The result is the page setting canonical URL metadata elements to [object Object] instead of the one in the route.

*A bit weird use case to have a default canonical URL. But the same bug may appear in other scenarios due to the code causing it.

Version
1.0.0-alpha.47
Minimal reproduction
Set a default canonical URL using a URL object
NgxMetaCoreModule.forRoot({
  defaults: { canonicalUrl: new URL('https://example.org')} satisfies GlobalMetadata,
}),

Then, set a canonical URL using a URL object too
const routes: Routes = [
  // ...
  {
     path: 'example',
     component: ExamplePageComponent,
     data: {
       meta: { canonicalUrl: new URL('https://example.org/example') }
     } satisfies NgxMetadataRouteData<GlobalMetadata>
  },
  // ...
]

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The issue lies in the MetadataResolver. It merges objects if a default is provided and another one is provided too (either in route or as service call argument). But here merging objects is not the right strategy.
This object merging was intended for metadata objects like image. So that you can specify some image default and overwrite it later. Either fully or partially.
Maybe solution could go towards a flag in resolverOptions that each metadata manager sets?


[Feature Request] Cart Weight Configuration

It would be nice to be able to configure the empty weight for all the carts.
Pulling a crafting station should be harder than pulling an empty cart, and as it stands they're too light and tend to tip over very easily, the increase in weight would most likely help with stability.

https://valheim.thunderstore.io/package/Azumatt/HaulersHelper/


SOLR-17525 backport to 9.x

https://issues.apache.org/jira/browse/SOLR-17525
Backport to satisfy gradle

So @malliaridis , I started the backporting, you see the cherry picked commit and some gradle changes that should be what we want for 9.x.
I'm waiting for the gradle checks to run and be green.
You additional validation would be really helpful to close this story :)
Thanks!

I've looked into the gradle changes and they look good so far. Only one note, there is a checksum file langchain4j-0.35.0.jar.sha1 that is being removed when running gradlew updateLicenses. So you may want to commit the removal as well.
Additionally, 9x workflows sometimes stuck during compilation and take up to 6h to be interrupted at the end. So you may want to restart the action if it takes more than 30 minutes on the same gradle task.


Adds sshkernel.magics to distrubuted packages

Hi,
I added a fix for #23, which adds the magics module to the distributed packages.

@baflo Thank you! I'll check it soon.


MOD: add setOutput for the logger

Add SetOuput function for the logger, related issue: https://github.com/sirupsen/logrus/issues/501

@sirupsen can you review this pull request? Or any suggestions?

Yes would absolutely love to see this added. At the moment this makes Logrus not a direct replacement for the stdlib log, which does have this functionality.
:+1:

@driskell Fixed, thanks for your review.

Hi @dmathieu - Do you know if there's anything that would stop this being merged? Would be great to see it added so there is additional API compatibility with stdlib. Also thanks for your hard work on logrus - I'm looking forward to using it :+1: 😃

This method is available since commit 0c03a05a and pr #682