Deleting, Renaming or moving a folder while running a terminal task is not working

Deleting, Removing or moving a folder which can effect the app running in the terminal causes this actions to stay in loading state and not performing the action.
For example for me this occurs in my React projects like this:
`| -> src/folder/File.jsx`

the app is running in the terminal
try to rename this folder
it's not going to work. It will be in loading state until you kill your terminal.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.70.0 (user setup)
OS Version: Windows 10

Steps to Reproduce:

Create a React app.
Run the development npm script.
Try to rename, delete or move a folder that has JSX files inside itself.
As you can see it will be in loading state until you stop the terminal task.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

i have updated the VS Code version but the issue still remains. I guess it has something to do with permissions. Even in Windows explorer you can't delete a folder which has been running in another application.

Thank you

As you suggest above, this is not an issue unique to VS Code and is related to file system permissions and management, so don't think we can action this


feat: allow for AnalogJS builder to be used with Angular adapter

This allows the @analogjs/platform:vite builder to be used in addition to the @angular-devkit/build-angular:application builder for Firebase App Hosting deployments.
cc: @jamesdaniels

Honestly, we could probably drop enforcement of the application builder now that we have the environment variable. WDYT @sjjj986 @Yuangwang?

Even better

Honestly, we could probably drop enforcement of the application builder now that we have the environment variable. WDYT @sjjj986 @Yuangwang?

Sorry for the delay, just getting around to this now. What environment variable are you referring to?


[RFC] ansible role for falco

https://github.com/juju4/ansible-falco/
If I can have feedback to on my rules work in progress, would be great too
https://github.com/juju4/ansible-falco/blob/master/templates/falco_rules_w_exceptions.yaml.j2
Thanks

I haven't used ansible much, but that looks very useful and I'd be happy to make any necessary changes to support this work.
Wrt the rule changes, I'd suggest rebasing against dev so you pick up all the changes since 0.2.0. When comparing to the ruleset in 0.2.0, here are some suggestions:

I like the ability to make a bunch of rules container-sensitive or not depending on falco_dontwatch_containers. I'd suggest putting that in a self-contained macro, though, so you don't have to sprinkle it amongst the other rules. Something like

macro: consider_containers
{% if falco_dontwatch_containers %}
condition: not container
{% else %>
condition: evt.num>0
{% end %}
...
rule: XXX
condition: consider_containers and ...

Some of the exceptions you have related to pathnames with /etc in the middle should be unnecessary now that https://github.com/draios/sysdig/pull/623 and https://github.com/draios/falco/pull/95/ are fixed.
The other additions of innocuous programs are all welcome. If you'd like to submit a PR with those additions I'd be happy to fold them in.

Glad to see falco is useful for you!

Thanks, I'm doing rebasing and testing before a pull request.
In the few additions, I'm including, there is python usage like apt/rpm (ansible usage), kitchen-test and lxd/lxcfs containers.

Hi, not sure if you got around to rebasing or not, but we'd like to send some end-of-year gifts to everyone who contributed to falco this year. If you'd like some schwag, could you send me your email address? I didn't see it on your profile. You can send it to<EMAIL_ADDRESS>Thanks!

By the way, I tested the ansible role you created and it worked great. If you want to deploy a new version to ansible galaxy that's compatible with 0.9.0, please do! I've added a reference to your role to our wiki. I'll close this issue as the role is working.


fix: error on graphql multiple queries

Description
fixes #3605
~Draft: This needs to also come with a way to make graphql return a partially successful response. Effectively this change is doing bad things where an error could be returned for a mutation but also in the same request commit a separate mutation.~
As it turns out, our GraphQL implmentation already returns errors and results at the same time making the response accurate to the database changes being committed or rolled back.

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[ ] Chore (non-breaking change which does not add functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Change to the templates directory (does not affect core functionality)
[ ] Change to the examples directory (does not affect core functionality)
[ ] This change requires a documentation update

Checklist:

[x] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

If I understand this correctly, this now runs every operation in a separate transaction. To me this kind of defeats the purpose of transactions. If two mutations are issued in one request, I would expect them to either both succeed or both fail.

Another issue I found with this approach: At the point where the resolvers run, there may already be a transactionID in the request, most likely cause for that is operations running from authentication (i.e. a findByID for the user), but there could be any number of things (plugins adding express middleware, etc. etc.).
In my opinion the "proper fix" for this would be to do this via an express middleware. The first thing in the middleware stack should be to start a transaction and the last step should be to commit it / roll it back. But I am unsure how to handle this when just using local operations.

@diesieben07,
Thanks for taking the time to review, but I don't think we agree on this.

If I understand this correctly, this now runs every operation in a separate transaction. To me this kind of defeats the purpose of transactions. If two mutations are issued in one request, I would expect them to either both succeed or both fail.

Payload's GraphQL response allows for multiple queries and mutations and the results for each can be returned independently. Why shouldn't it work this way?

In my opinion the "proper fix" for this would be to do this via an express middleware. The first thing in the middleware stack should be to start a transaction and the last step should be to commit it / roll it back. But I am unsure how to handle this when just using local operations.

I just went down this rabbit hole and spent about half my day on it. It was not working as I wanted and I've reverted back to how I started making the change instead. When a request has middleware such as the findByID for login, that transaction will have finished and committed before the graphQL handler is called. Then with this change we're splitting the req out so that each query/mutation is done in isolation of one another, finally the full response is returned with data and errors if any.
I've added another test case for multiple transactions to describe this functionality and prevent future regressions.

Payload's GraphQL response allows for multiple queries and mutations and the results for each can be returned independently. Why shouldn't it work this way?

After thinking about this more, I have come around to this way of doing this. This also makes my other suggestion moot, because this way requires separate transactions per operation.
The only thing I am concerned about now is the null-safe operators you added in your latest commit. How would such a situation ever occur if not for two operations racing to commit/abort the same transaction? If these null-safe operators are still necessary, then to me that means there is still a race somewhere, right?

The only thing I am concerned about now is the null-safe operators you added in your latest commit. How would such a situation ever occur if not for two operations racing to commit/abort the same transaction? If these null-safe operators are still necessary, then to me that means there is still a race somewhere, right?

This is a good question. I don't know that it is necessary given the other changes. I thought I had seen somebody on Discord report an error with mongodb trying to end session, not with graphql or it was a single mutation, can't recall. I will remove them and reassess if any new issues are reported.


Turn UI font size to too large then can't change it back.

Lapce Version
0.3.0 (1)
System information
macOS 14.0 (23A344) M1 Pro
Description
I typed 1323 in ui font size and the UI font refreshed to large size. Then I typed any number, it didn't refresh. When I change the number and reopen lapce, the font is also too large, and the UI font size display 1.

I fond that it's because ui's refreshing time is strange. I wanna type 13, when I type the first number 1, it started to refresh. And my ui turned to too small.


Implementation of optical (Flicker) TAN

Hello everyone,
right now I have a running implementation for rendering Flicker Tans, i will open a pull request soon, but before I wish to have some Feedback how to do it. Right now I implemented it with an animated SVG, which should be a good compromise for both Backend and Frontend usage (I think). There is no JS or CSS involved in the implementation, I used only the animate-tag from SVG for the flickering. Therefore I used this composer dependency php-svg. I have not checked this repo for anything security wise, it was just the first I found and simple to use. I think another option would be using .gif files. A html canvas with some JS Code for the painting did not seem like a good option for me.
I think reimplementing of the features would not be a big issue, due to the low complexity of the resulting svg - but of course I would only do it if you think I/we should prevent 3rd party dependencies or not.
Here is the code of an example svg. I cannot embed it here (as far as I know) because github disabled user generated svgs because of XXS vulnerabilities, also SVG File attachments are not allowed for the same reason :(. Just copy the following content to a .svg file, save it and open it with your browser. It should work out of the box and your TAN Generator will give you a TAN for some dummy data (Transfer to Kontonr: 123456789 with amount of 0,01€). There is no JS code inside (as you can see), so don't worry about the XXS here. If your TAN Generator is bigger or smaller, just change the width (and height) ONLY in the first line of the svg. It will rescale then to your new given dimensions.
<svg xmlns="http://www.w3.org/2000/svg" width="280" height="140" viewBox="0 0 210 105" preserveAspectRatio="none">
    <rect x="0" y="0" width="210" height="105" rx="7.5" ry="7.5" style="fill: black"></rect>
    <polygon points="25,18 32,5 18,5" style="fill: grey"></polygon>
    <polygon points="185,18 192,5 178,5" style="fill: grey"></polygon>
    <rect x="10" y="20" width="30" height="75">
        <animate attributeName="fill" calcMode="discrete" repeatCount="indefinite" values="white;black;white"
                 keyframes="0;0.5;1" dur="0.1s"></animate>
    </rect>
    <rect x="50" y="20" width="30" height="75">
        <animate attributeName="fill" calcMode="discrete" repeatCount="indefinite" dur="4s"
                 values="white;black;white;white;white;white;black;black;white;black;black;white;white;white;black;white;white;black;black;white;black;white;black;white;black;white;white;white;black;white;black;white;black;black;black;white;white;white;white;black"
                 keyframes="0;0.025;0.05;0.075;0.1;0.125;0.15;0.175;0.2;0.225;0.25;0.275;0.3;0.325;0.35;0.375;0.4;0.425;0.45;0.475;0.5;0.525;0.55;0.575;0.6;0.625;0.65;0.675;0.7;0.725;0.75;0.775;0.8;0.825;0.85;0.875;0.9;0.925;0.95;0.975;1"></animate>
    </rect>
    <rect x="90" y="20" width="30" height="75">
        <animate attributeName="fill" calcMode="discrete" repeatCount="indefinite" dur="4s"
                 values="white;black;white;white;black;black;black;black;white;black;black;black;black;black;white;black;black;black;white;black;black;white;white;black;black;white;white;black;black;black;black;white;black;white;black;white;black;white;white;black"
                 keyframes="0;0.025;0.05;0.075;0.1;0.125;0.15;0.175;0.2;0.225;0.25;0.275;0.3;0.325;0.35;0.375;0.4;0.425;0.45;0.475;0.5;0.525;0.55;0.575;0.6;0.625;0.65;0.675;0.7;0.725;0.75;0.775;0.8;0.825;0.85;0.875;0.9;0.925;0.95;0.975;1"></animate>
    </rect>
    <rect x="130" y="20" width="30" height="75">
        <animate attributeName="fill" calcMode="discrete" repeatCount="indefinite" dur="4s"
                 values="white;black;white;white;black;black;white;black;white;black;white;black;white;black;black;white;white;black;black;black;white;black;white;white;black;white;white;black;white;black;black;black;white;black;black;black;black;black;white;black"
                 keyframes="0;0.025;0.05;0.075;0.1;0.125;0.15;0.175;0.2;0.225;0.25;0.275;0.3;0.325;0.35;0.375;0.4;0.425;0.45;0.475;0.5;0.525;0.55;0.575;0.6;0.625;0.65;0.675;0.7;0.725;0.75;0.775;0.8;0.825;0.85;0.875;0.9;0.925;0.95;0.975;1"></animate>
    </rect>
    <rect x="170" y="20" width="30" height="75">
        <animate attributeName="fill" calcMode="discrete" repeatCount="indefinite" dur="4s"
                 values="white;black;white;white;black;black;black;black;black;white;black;black;black;white;black;black;black;black;black;black;black;black;black;black;white;black;white;white;black;black;black;black;white;black;black;black;black;black;black;black"
                 keyframes="0;0.025;0.05;0.075;0.1;0.125;0.15;0.175;0.2;0.225;0.25;0.275;0.3;0.325;0.35;0.375;0.4;0.425;0.45;0.475;0.5;0.525;0.55;0.575;0.6;0.625;0.65;0.675;0.7;0.725;0.75;0.775;0.8;0.825;0.85;0.875;0.9;0.925;0.95;0.975;1"></animate>
    </rect>
</svg>

Would appreciate some feedback from the Maintainers / Contributors and everyone else.  @nemiah

Hi,
is there any possibility to implement flicker version 1.3.*?
Our Sparkassen doesn't support 1.4 and don't want to implement it.

Sure its possible, not sure how fast tho. If you want to do it yourself let me know I could give you some pointers.


Tiles are overlapping and can't be moved

Describe the bug
Below is a screenshot of how the problem map looks like for me on Firefox. The tiles are overlapping and I can't move them so they don't overlap (or to organize them). One also can't increase the tile size so the full text can be seen.

To Reproduce

Go to https://ameliorate.app/Prototyperspective/CarsAreHarmfulToSociety
If the debate is not deleted but still there (please save it) the tiles are overlapping

Expected behavior
Being able to drag them around with the mouse (click, hold and drag). Being able to change the tile size by dragging a side of the tile. Or it arranging etc things automatically.
Additional context
I think the full map view is not a good view mode for problem maps but is useful to have to get the full picture. Other view modes that e.g. only show a few layers at a time or the current branch would be good to add. This issue is about the full-map-view. If it's not a bug but a missing feature the issue could be moved but it seems like they are intended to be movable or can be moved but not there.
Technical ideas
No response

Looks like I've got a few things that are scaling with the browser's default font size, but the layout calculation does not. The layout currently works on default font size of 16. Can fix this

Separately - there is #196 for manually moving nodes around, but functioning automatic layout is priority over that.
And I just posted over on reddit about changing node size but I'll post it here for context as well:

My intention was to keep node text small and concise so they can be quickly glanced at to understand high-level concepts. To this end, nodes are fixed size, and extra explanatory text can be included in the node's notes. This is open to discussion. It probably requires some practice for wording/sentence-fragmenting, but I've always been able to word nodes such that their concept fits in the current node's size.

That makes sense. Seems like I have another font size configured in Firefox then. I also think automatic layout is a priority and ideally only that needs to be used. However, I think some changes to it would probably be good so things are less condensed and better to see – here's one main thing: I think those addresses nodes would be good to only show when hovering over a line (or when having some setting enabled)...it's too much text and too much elements.

I think those addresses nodes would be good to only show when hovering over a line (or when having some setting enabled)

I think this is a good idea, and it's actually in #478 too

@prototyperspective I merged a fix, let me know if the issue still persists.

@keyserj Great, no it's solved now as moving the tiles around is what the other issue is about, thanks. However

the other issue currently has the title "Ability to turn off automatic layout" and I think something about enabling moving tiles would be good to add such as "Ability to turn off automatic layout and move nodes"
The tiles of the connections still overlap – but it would be better to have a separate issue for that. Maybe the best solution for that is to not display info on them until hovering over the line. Is there already an issue about these tiles overlapping with (or being underneath) other tiles? The screenshots show what I mean. I think if these are shown the nodes would need to move so these can be fully seen and aren't underneath or above any other element.

 |

"Ability to turn off automatic layout and move nodes"

Yeah that's a little more explicit - renamed

The tiles of the connections still overlap

Thanks for the screenshots. A while ago I made the decision for the layout to ignore edge overlap. I think that, when a diagram gets bigger, trying to avoid the overlap results in the diagram being a lot more spread out. This is something that I'm open to reconsidering, but there's usually only one type of edge that could be between any two node types, so I don't think seeing the edge info is that big of a deal (you can also click on the edge to get it to come to the front, if you really need to see it).
Because of this, I'm also a fan of the "don't display edge details without hovering" idea.


Implement PatchMutation::ApplyToLocalView

Suggestion: Do you want to merge this to held_acks_master and port the new version of the code directly from Android?

Answering Sebastian's question (well; summarizing from an offline discussion): This PR is pretty minimal, and missing quite a lot. It's just got the stuff required to proceed with local serialization, and otherwise has large holes in the implementation. So we're going to have to take a second pass at this later to fill the rest in, at which point, (I hope) all the held write acks stuff should be done.
That said, it's largely ported from android (rather than ios) so is mostly following Sebastian's suggestion already.


Unable to return array from contract

Hi,
I have a simple contract which returns few arrays. Works fine in the online solidity compiler. But after deploying it to the chain and invoking it from the app.js its giving the following error.
Have found a bug related to this https://github.com/eris-ltd/eris-db.js/issues/27
Any particular reason why this error is occurring?
My contract is like:
function getMarket() constant returns(uint[], uint[], uint[], uint[]) {
    uint[] memory optionIDs = new uint[](20);
    uint[] memory strikes_ = new uint[](20);
    uint[] memory positions_ = new uint[](20);
    uint[] memory cashes = new uint[](20);
    uint z = 0;
      for (uint i=0; i<10; i++) {
        optionIDs[i] = i;
        strikes_[i] = i+10;
        positions_[i] = i+100;
        cashes[i] = i+50;
        z++;
      }
    return (optionIDs, strikes_, positions_, cashes);
  }

Error is:
[JSON RPC 2.0 Error] Message Id: 1, (INTERNAL_ERROR) - Error when transacting: Memory out of bounds
[Error: Error when transacting: Memory out of bounds]
Error callback from sendTransaction

/home/azureuser/.eris/apps/test/app.js:50
    if (error) { throw error; }
                       ^
Error: Error when transacting: Memory out of bounds
    at /home/azureuser/.eris/apps/test/node_modules/eris-contracts/node_modules/eris-db/lib/rpc/http.js:79:22
    at httpRequest.onreadystatechange (/home/azureuser/.eris/apps/test/node_modules/eris-contracts/node_modules/eris-db/lib/rpc/http.js:103:17)
    at dispatchEvent (/home/azureuser/.eris/apps/test/node_modules/eris-contracts/node_modules/eris-db/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:572:25)
    at setState (/home/azureuser/.eris/apps/test/node_modules/eris-contracts/node_modules/eris-db/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:14)
    at IncomingMessage.<anonymous> (/home/azureuser/.eris/apps/test/node_modules/eris-contracts/node_modules/eris-db/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:431:13)
    at IncomingMessage.EventEmitter.emit (events.js:117:20)
    at _stream_readable.js:920:16
    at process._tickCallback (node.js:415:13)

Eris version :  0.11.4
go version xgcc (Ubuntu 4.9.3-0ubuntu4) 4.9.3 linux/amd64

Sorry for the delay @somak12, I have looked into this issue and it relates to how solidity stores the array length. I'm going to consolidate this ticket into https://github.com/hyperledger/burrow/issues/413.
I have a fix in hand, please see there for further discussion.

I was a bit hasty to close this. I'm going to verify that your code works. Would you mind if I used it to make test case in monax/cli?

@somak12 so having looked into this, the initialisation-time dynamic memory arrays (size is a parameter you pass the constructor at runtime) are not yet supported by the EVM. The issue there is that  As you correctly point out on remix (browser solidity) it does work, and I am told this is implemented as something as a work-around in web3 that uses internal knowledge of then state to allow for dynamic array returns.
The problem is that when you make a CALL you have to specify the return position and size in memory, see here: https://github.com/ethereum/solidity/issues/164. So there is not a general solution in Solidity. However there is a proposal to provide a mechanism in Ethereum to do this more efficiently via two new opcodes see: https://github.com/ethereum/EIPs/pull/211
In the meantime, the following will work (will return the arrays) (I have been trying this against #607):
    function getMarket() constant returns(uint[20], uint[20], uint[20], uint[20]){
        uint[20] memory optionIDs;
        uint[20] memory strikes_;
        uint[20] memory positions_;
        uint[20] memory cashes;
        uint z = 0;
          for (uint i=0; i<10; i++) {
            optionIDs[i] = i;
            strikes_[i] = i+10;
            positions_[i] = i+100;
            cashes[i] = i+50;
            z++;
          }
        return (optionIDs, strikes_, positions_, cashes);
      }

If you want to use dynamic arrays internally (as in without returning those values) then you will be able to do so after #607 is merged.

:)


Host Timeout on OSX

local platform: OSX 10.10.5
Docker version 1.12.2, build bb80604
docker-machine version 0.8.2, build e18a919

I'm trying to get ADOP running in my personal AWS instance using the quickstart guide but I keep getting the error bellow.
I've run it about 6 different times. A few times from master, a few times from the tagged branch 0.2.2. I've tried it in different regions.
Any help would be appreciated.
      ###    ########   #######  ########
     ## ##   ##     ## ##     ## ##     ##
    ##   ##  ##     ## ##     ## ##     ##
   ##     ## ##     ## ##     ## ########
   ######### ##     ## ##     ## ##
   ##     ## ##     ## ##     ## ##
   ##     ## ########   #######  ##

Your AWS parameters file already exists, deleting it...
Creating a new AWS variables file...
Running pre-create checks...
Creating machine...
(sa-adop) Launching instance...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": dial tcp <IP_ADDRESS>:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

Hi @acn-adammclark , is there's any chance that you have blocked 2376 port in your network? I've seen this error often and all those times it was related to blocked port unfortunately.

@anton-kasperovich that was the issue. Thanks for the help. Now to figure out why nginx never comes online.

Well I've waited for nearly 35 minutes for nginx to respond. Is this expected?

No, it is not expected, usually it's take about ~2 minutes in total of sleep statements to have running NGINX. I've heard about some random errors which people can't reproduce, they've just re-created ADOP stack and everything worked perfectly fine. Is it your case too? Can you please re-create and check?

I figured it out. You have to change the security policy before quickstart gets around to testing for services. Port 80 isnt accepting incoming connecitons with the default policy docker sets up.
I'll provide a PR to update the quickstart guide.

@acn-adammclark Can you please share the steps that you followed to fix this issue? We are facing the same issue.

@arunamat The default security group that docker-machine creates doesn't have open ports that support ADOP.
Take step 7 of the instructions
Update the docker-machine security group in the AWS console to permit inbound http traffic on port 80 (from the machine(s) from which you want to have access only), also UDP on 25826 and 12201 from <IP_ADDRESS>/32.

and go into AWS console and update the ports after step 4 before step 5 while the images are being downloaded.


Fix java validatesdistrolesscontainer dataflow workflow

This PR fixes #33244 by adding the required gradle properties to the workflow configuration.
See: https://github.com/apache/beam/actions/runs/12063013249/job/33637565011

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

assign set of reviewers


When will the next part of tutorial be up?

Read the previous part, but now I'm confused how to integrate both immutable and flux.

I'm working on it hard and it's close to the final version. I guess on next week sometime.

@mahulst It's published: http://blog.risingstack.com/the-react-js-way-flux-architecture-with-immutable-js/  ;)


Start Server using adb

Just found this Docker image -> https://hub.docker.com/r/tracer0tong/android-emulator/
I'm super keen to combine this with the Drozer Docker image over docker-compose.
Current issue I'm having is not being able to start the server without a gui on the Android emulator.
Obviously exposing MainActivity.startServer() over a broadcast receiver for all builds is bad security practise, so could we possibly get a build option that exposes this server? or has it automatically start?

Hi @JoelPagliuca at the moment we don't have a build that meets your requirements. However, you are free to modify drozer-agent to suit your needs.
PRs are most welcome.
Alternatively if you're pressed for time, I can think of a very hacky way of solving this:

Launch the Activity using pm
Use /bin/input to generate a touch event to launch the server.

I thought I'd end up going down this path.
Thanks for getting back to me, might see a PR from me in the future

Hey @JoelPagliuca, I revisited this issue and it turns out there is a way to launch the server. The following command should help you launch the server:
am startservice -n com.mwr.dz/.services.ServerService -c com.mwr.dz.START_EMBEDDED

Ah too easy, I'll switch to that then. Thanks mate

Hey, I'm looking at doing the above for a jenkins job -  I apologise if this is an obvious question - but how can i get around this?
$  adb shell am startservice -n com.mwr.dz/.services.ServerService -c com.mwr.dz.START_EMBEDDED
Starting service: Intent { cat=[com.mwr.dz.START_EMBEDDED] cmp=com.mwr.dz/.services.ServerService }
Error: Requires permission not exported from uid 10087


Issue with sourcing spacemacs.vim

I get this when I try to source spacemacs. What am I doing wrong?

Read step 3 of readme carefully.
The source command should be inside the file .ideavimrc

I have. But unfortunately nothing happens when I hit any keys with vim mode active


Feature: Experimental css prop hash

This PR changes how the css prop is hashed, switching from a JSON hash of the styles to a JSON hash of the current stack.

Can you change the base branch to canary?


Ease Eclipse integration

If these cause problems with any other environment, feel free to revert.

This should be fine. But IntelliJ is much better Scala IDE than Eclipse...


Feature Request: Resume session

A USSD session may be timed out or may end abruptly without a user completing a flow.
In my use case, we have a user fill out a form, we tried to limit the number of inputs so that the user can complete the session in one go.
But not every user is fast enough to respond to these prompts especially those on feature phones(torchlight + radio only). These people always suffer timed-out sessions because they switch the input method and the typical press 1-3 or more times to input a single letter.
I manually implemented a buggy solution which involved using:

a middleware to intercept the request to decide whether the previous session is still valid(not expired)
using a separate cache to store the compound key of the phone_number and session
an event listener and handler which fires when the cache is written to. It checks the key of the write operation. Keys with certain prefixes like __preserved__ are stored permanently
The middleware checks and attempts to reconstruct the previous session(if it exists), populate the record with the previous data, determines the last complete state, modifies the __init__ and __active__ keys and finally displays a state which prompts the user to resume from the last step or start a fresh session

This implementation was so buggy and hacky(messing with internal records etc).
A cleaner, baked-in, easy-to-opt-in solution will be a great feature to have.
A much simpler approach is to let provide something like a State Machine config.This will allow the USSD machine to know where to resume automatically.  See Spatie's Laravel Model state  for inspiration
Please do consider this issue ... I'm ready to share further details as needed though I may not be able to send a PR at the moment because I spend less time behind my computer these days.

Hi @Parables,
Thanks for the suggestion. This feature will be added and released in v3.0.0

Why closed as completed when it hasn't been implemented.
Please reopen the issue until the feature has been added, tested and released before closing it as complete.


⚠ globalcontext_make_atom is not safe

globalcontext_make_atom doesn't do any check and might return an invalid atom [1], so it will be changed to [2].
The reason is that globalcontext_make_atom may alloc memory (and it might fail in doing so), hence we need to handle it.
See also PR #1443
Handling this situation might complicate our codebase, so I suggest using some different approaches:

globalcontext_existing_term_from_atom_string when we just need to compare a term against an ATOM_STR (question: should we rename this function to globalcontext_make_existing_atom?)
interop_kv_get_value and interop_kv_get_value_default for fetching a value using an ATOM_STR as a key
making atoms in advance, such as at the beginning of a function (when they are going to be used 100% of times), so in case of failure an early return is enough (I did a macro for that [3])
adding most common ones to defaultatoms.def
adding platform atoms to platform_defaultatoms.def when it doens't make sense to save few bytes of memory and they are frequently used (this might apply to emscripten)

Further evolution:

defaultatoms located in src/libAtomVM/defaultatoms.def will be managed using gperf in the future (and therefore kept outside of the dynamic atom table in RAM), so it will be quite cheap adding new libAtomVM atoms there, since they will be located on flash memory. Also code generated with gperf is very efficient!
I'm trying to understand how to add some verification code that makes sure that atom strings such as "\x9" "foo" will raise some kind of error (I'd love a build time error).

[1]:
417 static inline term globalcontext_make_atom(GlobalContext *glb, AtomString string)
418 {
419     int global_atom_index = globalcontext_insert_atom(glb, string);
420     return term_from_atom_index(global_atom_index);
421 }

[2]:
--- a/src/libAtomVM/globalcontext.h
+++ b/src/libAtomVM/globalcontext.h
@@ -412,11 +412,15 @@ static inline bool globalcontext_is_term_equal_to_atom_string(GlobalContext *glo
  *          global context.
  * @param glb pointer to the global context
  * @param string an AtomString
- * @return an atom term formed from the supplied atom string.
+ * @return an atom term formed from the supplied atom string, or an invalid term
  */
 static inline term globalcontext_make_atom(GlobalContext *glb, AtomString string)
 {
     int global_atom_index = globalcontext_insert_atom(glb, string);
+    if (UNLIKELY(global_atom_index < 0)) {
+        return term_invalid_term();
+    }
+
     return term_from_atom_index(global_atom_index);
 }

[3]:
#define REQUIRE_ATOM(name, lenstr, str, glb) \
    term name = globalcontext_make_atom(glb, lenstr str); \
    if (UNLIKELY(term_is_invalid_term(name))) { \
        RAISE_ERROR(OUT_OF_MEMORY_ATOM); \
    }

How to use it:
-static const char *const embedded_atom = "\x8" "embedded";
-
 static term nif_code_ensure_loaded(Context *ctx, int argc, term argv[])
 {
     UNUSED(argc);

+    REQUIRE_ATOM(embedded_atom, "\x8", "embedded", ctx->global);
+
     term module_atom = argv[0];
     if (UNLIKELY(!term_is_atom(module_atom))) {
         RAISE_ERROR(BADARG_ATOM);
@@ -4876,7 +4876,7 @@ static term nif_code_ensure_loaded(Context *ctx, int argc, term argv[])

     if (UNLIKELY(!found_module)) {
         term_put_tuple_element(result, 0, ERROR_ATOM);
-        term_put_tuple_element(result, 1, globalcontext_make_atom(ctx->global, embedded_atom));
+        term_put_tuple_element(result, 1, embedded_atom);
     } else {
         term_put_tuple_element(result, 0, MODULE_ATOM);
         term_put_tuple_element(result, 1, module_atom);

While we are resolving this issue #1444 should also be fixed.

globalcontext_existing_term_from_atom_string when we just need to compare a term against an ATOM_STR (question: should we rename this function to globalcontext_make_existing_atom?)

This would help make the use of this function a lot more clear in my opinion.

Some time ago we had discussed (in the Telegram chat) removing platform_defaultatoms entirely and delaying the creation of these atoms until a driver needs them, but this issue seems to complicate that slightly. Should we still be trying to migrate away from using platform_defaultatoms?


Numeric Patterns added

Fixes Issues #594 #600 #601 #602 #603 #689 #690 #691 #694 #695

@aryashah2k 10 patterns added

Class names updated

@aryashah2k are the files OK to be merged?


Set up CI build to check for broken links

Implemented in https://github.com/dtolnay/rust-faq/commit/49de8ea49cede8cb35b57e17d50a589323452470.


Change structure of generated package

@akorobeinikov Is it ready for review or should it be marked as draft?

@akorobeinikov Is it ready for review or should it be marked as draft?

Convert to draft

move to ote

move to ote


not picking up checkboxes

I have a funky spreadsheet where yes/no fields are in the form of check-marks.  The tool isn't picking up the checkmarks in the OCR.  The result is blank results in the table.

Tabula focuses on extracting text, so unfortunately extracting non-text features like checkboxes isn't part of the expected behavior for the moment.


Document IAM actions needed to create, update, and delete the template

I gleaned these actions using the IAM Access Analyser to generate a policy for a CloudFormation service role that I granted admin. I then hand tuned the list, removed the admin policy and redeployed a stack using it.
I have scanned all the branches and tried to be thorough but I don’t have high confidence that I will have caught all the possible template parameter combinations that might cause additional IAM actions to be required. I am tempted to put a BETA label on this in the docs section to signal that it is likely incomplete.
I’ve cherry-picked f2005a737acbe42f9cf9295fe83ec0d8e93fc7b4 from https://github.com/buildkite/elastic-ci-stack-for-aws/pull/913 which adds AUTO_EXPAND to the list of capabilities this requires.

TODO

[x] Add integration test which consumes these policies and deploys and deletes a stack using a service role with these policies

Fixes #924
cc https://github.com/buildkite/docs/issues/1136
cc #904

I really wanted to launch a separate stack with the service role so that the step could be marked as soft fail while the new role is in testing 🤔 but the launch.sh wasn’t obviously parameterisable.


feature-request: pause extension like chrome plugin manager

VSCode Version: 1.1.1
OS Version: oxs 10.11.4

In china, install extension is very slowly, sometime i want to pause one extension at some project

sometime i want to pause one extension at some project

what do you mean by pausing? pausing the download/install?

@jrieken I mean inactive extension, like this in chrome plugin manager

From the snapshot, I suppose what @builden wants is enabling/disabling installed extensions.

Duplicate of #2882


Add support for loading protobuf metadata [phab:D1533]

Created by zarko at 2017-04-17 20:36:19:
This diff adds the ProtobufMetadataLoader class.
This class translates protoc's GeneratedCodeInfo to
Kythe metadata.
I expect to have to hack on the (file) path-handling code
a little more depending on the results we get back from
our various build systems.

jrtom commented inline (context lost during migration) at 2017-04-17 21:52:47:
name should not be capitalized, i.e., s/Lookup/lookup

jrtom commented inline (context lost during migration) at 2017-04-17 21:52:47:
Unless you have specific plans to create instances of this class in a way that you're currently not, I would just change the constructor to take a CompilationUnit, and change the vnameLookup from a Function to a Map.
If you do plan to have instances of this class that use non-Map-based Functions internally, consider either

adding a constructor that takes a CompilationUnit
changing the lookupVName...() method to return a ProtobufMetadataLoader instance directly (unless you expect to use lookupVNameFromCompilationUnit() in some other context than creating an instance).

jrtom commented inline (context lost during migration) at 2017-04-17 21:52:47:
Does it make sense to continue if there's no contextVName?  You're going to end up setting the corpus to the empty string in that case.

jrtom commented inline (context lost during migration) at 2017-04-17 21:52:47:
It looks like the only part of the VName that's ever used (at the moment, at least) is the corpus.  Would it make more sense to just map to that directly?

jrtom commented inline (context lost during migration) at 2017-04-17 21:52:47:
constant for "protobuf"?

zarko wrote at 2017-04-18 19:13:19:

Address comments.

zarko commented inline (context lost during migration) at 2017-04-18 19:31:04:
It would not. More data can be attached by the extractor.

jrtom wrote at 2017-04-18 21:27:03:
LGTM.  Up to you whether you want to wait for fromberger or schroederc to weigh in.


linux_zen: 5.8.1 -> 5.8.7

Motivation for this change
Closes #96933
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review 1

35 packages failed to build:
- linuxPackages_zen.amdgpu-pro
- linuxPackages_zen.anbox
- linuxPackages_zen.ati_drivers_x11
- linuxPackages_zen.batman_adv
- linuxPackages_zen.can-isotp
- linuxPackages_zen.chipsec
- linuxPackages_zen.cryptodev
- linuxPackages_zen.ena
- linuxPackages_zen.exfat-nofuse
- linuxPackages_zen.ixgbevf
- linuxPackages_zen.lttng-modules
- linuxPackages_zen.mwprocapture
- linuxPackages_zen.mxu11x0
- linuxPackages_zen.ndiswrapper
- linuxPackages_zen.netatop
- linuxPackages_zen.nvidia_x11_legacy304
- linuxPackages_zen.nvidia_x11_legacy340
- linuxPackages_zen.nvidia_x11_legacy390
- linuxPackages_zen.nvidiabl
- linuxPackages_zen.openafs
- linuxPackages_zen.openafs_1_8
- linuxPackages_zen.phc-intel
- linuxPackages_zen.r8168
- linuxPackages_zen.rtl8723bs
- linuxPackages_zen.rtl8812au
- linuxPackages_zen.rtl8814au
- linuxPackages_zen.rtl8821au
- linuxPackages_zen.rtl8821cu
- linuxPackages_zen.rtl88x2bu
- linuxPackages_zen.rtl88xxau-aircrack
- linuxPackages_zen.rtlwifi_new
- linuxPackages_zen.sch_cake
- linuxPackages_zen.tbs
- linuxPackages_zen.virtualbox
- linuxPackages_zen.virtualboxGuestAdditions

42 packages built:
- linuxPackages_zen.acpi_call
- linuxPackages_zen.asus-wmi-sensors
- linuxPackages_zen.bbswitch
- linuxPackages_zen.bcc
- linuxPackages_zen.bpftrace
- linuxPackages_zen.broadcom_sta
- linuxPackages_zen.cpupower
- linuxPackages_zen.ddcci-driver
- linuxPackages_zen.digimend
- linuxPackages_zen.dpdk
- linuxPackages_zen.evdi
- linuxPackages_zen.facetimehd
- linuxPackages_zen.fwts-efi-runtime
- linuxPackages_zen.hyperv-daemons
- linuxPackages_zen.intel-speed-select
- linuxPackages_zen.it87
- linuxPackages_zen.jool
- linuxPackages_zen.kernel
- linuxPackages_zen.mba6x_bl
- linuxPackages_zen.nvidia_x11
- linuxPackages_zen.oci-seccomp-bpf-hook
- linuxPackages_zen.openrazer
- linuxPackages_zen.perf
- linuxPackages_zen.ply
- linuxPackages_zen.r8125
- linuxPackages_zen.rtl8192eu
- linuxPackages_zen.rtl8821ce
- linuxPackages_zen.sysdig
- linuxPackages_zen.systemtap
- linuxPackages_zen.tmon
- linuxPackages_zen.tp_smapi
- linuxPackages_zen.turbostat
- linuxPackages_zen.tuxedo-keyboard
- linuxPackages_zen.usbip
- linuxPackages_zen.v4l2loopback
- linuxPackages_zen.v86d
- linuxPackages_zen.vhba
- linuxPackages_zen.x86_energy_perf_policy
- linuxPackages_zen.xpadneo
- linuxPackages_zen.zenpower
- linuxPackages_zen.zfs
- linuxPackages_zen.zfsUnstable

If you have a build setup where review builds make sense, could you check that the failures are already present before the bump?

Is there a trivial way of doing that?
The build failures all sound like out-of-tree modules that I wouldn't expect to be compatible with 5.8 yet though. (The popular ones (ZFS and Nvidia) both work however).
Perhaps we should declare which ABIs each module are compatible with so that nobody even attempts to build them for incompatible kernels.

Is there a trivial way of doing that?

Hmm. A more efficient way is to take the list, replace the start-of-line with «nix-build --no-out-link '' -A », the end-of-line with « >> /tmp/zen-paths.log» and see if there is any output file in the log.
A more tooling-friendly is probably nix-reviewing a change that sets preUnpack to «true».

The build failures all sound like out-of-tree modules that I wouldn't expect to be compatible with 5.8 yet though. (The popular ones (ZFS and Nvidia) both work however).

Ah, makes sense

Perhaps we should declare which ABIs each module are compatible with so that nobody even attempts to build them for incompatible kernels.

Well, you often do not know in advance if the next release will contain breaking API changes for free but out-of-tree modules.

I couldn't get anything decent working ad-hoc but I think most of these were broken before too.
https://github.com/Mic92/nixpkgs-review/issues/85 should cover this use-case though.

Well, you often do not know in advance if the next release will contain breaking API changes for free but out-of-tree modules.

I meant a blocklist that gets amended when a new ABI becomes incompatible. E.g. no longer works on 5.8 -> mark as broken for >=5.8.
Though it seems like many of the packages were already marked as broken. Not sure why nixpkgs-review tried to build them and reported them as failures when they were known to be bad before and after.
cc @Mic92


Enhancement: Default alt text option

Is your proposal related to a problem?
With ImageBlock there is an alt text field (or decorative image option). If an image has been uploaded most of the times the alt text related to one image is most of the time the same.
Describe the solution you'd like
Add an optional default alt text field to the uploaded images
Describe alternatives you've considered
If once the alt text has been filled for one image, that alt text should be copied every time when that image will be used
Working on this
I would like to work on this issue, but I would like to consult with somebody, who has knowledge from the source code.
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Thanks for the suggestion @locika! I believe the 'description' field on the image is supposed to serve this purpose.
@Chiemezuo @Stormheg @thibaudcolas - I was under the impression that the description field on the image model was meant to prefill the 'alt text' field of ImageBlock when an image was selected, but now I see that feature wasn't implemented as part of #11791. Is that an intended feature that was left out due to lack of time, or was there a deliberate decision not to include it (perhaps to encourage editors to write contextual alt text instead of relying on the generic description)? Can you clarify please?

@gasman yes pre-filling the contextual alt text from the description field was originally part of the GSoC project, but we had to drop it.
Our original plan was to have a button next to the description field that copies over the description field of an image into the contextual alt text field.
If I recall correctly, the issue with this approach was a technical one. We couldn't get this button to function. @Chiemezuo did I recall this correctly? Anything to add?

Hi @gasman I'll add some things to what @Stormheg mentioned, but it was completely spot on.
We wanted a "suggestion UI" (A box to display the 'description' and possibly anything else e.g AI-generated suggestions). The idea was that clicking an item on the Suggestion UI would then fill the alt text field with either the generic description or the suggestion. The first version of this was to have a button to copy things over, but the solution was more technical than anticipated and couldn't be fixed within the remaining amount of time I had for the project.
The problem had something to do with the complete Image model data not being available when rendering happens in the editing interface. Something along the lines of Telepath not giving the properties that would be needed to make this happen, in one go.

Thanks @Stormheg and @Chiemezuo for the extra detail!
Yep, I see that we currently don't pass the description as part of the result from the chooser modal, so that would need to be added (in ImageChosenResponseMixin). For consistency we'd probably also want to include it in the bundle of data that a pre-populated AdminChooserWidget can access (in get_value_data_from_instance), and the widget's state as used when duplicating the block (getStateFromHtml), although I don't think that's strictly necessary since we're only using the description at the moment that a new image is picked.
In the absence of a full suggestion UI, would prepopulating the alt text field with the image description be considered a useful first step? I may well have a go at picking that up myself if so...

It potentially could be. However, there might be a tendency for content editors to rely a bit too much on the generic descriptions if it's pre-filled. For some, having to erase the pre-filled data to replace with something else might be an annoyance. Perhaps if this were done when the editor clicks a button instead of automatically, that might be a tad better.
What do you think?
cc @thibaudcolas

I really like the automatic prefill one gets when choosing an image in Draftail. I think that is a better UX than a button to copy in the info from default_alt_text. For sites with well curated image libraries, the description is probably pretty good and the main decision is wether or not to use 'is decorative' in this context. But even if the user needs to change the text, it is useful to have the image's description available right at the point where they are editing to act as context.

For sites where implementers know their existing "Description" fields are correctly used as part of their strategy to manage alt text, then I think pre-filling the alt text field like we currently do with rich text is good? And yeah it’s probably a good improvement for all sites until we can create our ideal UI for this.
The ideal UI is documented in RFC 97 in the "Proposed alt flow" diagram. We felt it important to encourage the user to make a decision about alt text in the context where the image is used, so the plan was:

Pre-fill the alt text field with the description if the image was just uploaded within a chooser on the current page.
Empty alt text field with a button for the user to "use the description as alt text" if the image was selected from the pre-existing library (see ATAG B.2.3.3 Save for Reuse)

The "use this text" button is also a better pattern in a world where alt text options are proposed by generative AI, here is what we had designed, with the idea that the same pattern could be reused for AI-free websites but with a single "use this" option:

Anyway, for now, if we pre-fill with default_alt_text it’s probably a win for adoption of the contextual alt text feature, even if there is a risk of the field ending up with the image’s title. Consistency with the rich text experience clearly a win too.


Finding out the server capabilities

Is there a way to find out whether a server has registered the workspace/didChangeWatchedFiles capability.
I thought I could add a onRequest call to catch this but then realised this was overriding the onRequest call setup internally.

Actually there is no easy way to find this out right now. The best would be to offer a getFeature method for the watched file feature which we then could inspect.


Block Crawler Grant Application

Project Abstract

We built an open source high-performance ETL framework for blockchain data designed to process blockchain data and transform it into useful datasets in the easiest way possible. We will configure it for free to collect any dataset for you.

Block Crawler creates datasets from blockchains and provides it to those who are building applications. Its high-performance, open-source ETL framework is designed to process massive amounts of blockchain data and transform it into useful datasets in the easiest and most expedient way possible. With Block Crawler, anyone can extract any blockchain data from EVM RPC APIs like Ethereum, Polygon, and more, transform it into desired datasets, and persist it into databases to support data access requests on historical and real-time data. Furthermore, the Block Crawler's modular components can be combined with dataset specific components to cater to the unique requirements of every user.
Whether a blockchain looking to improve data availability or a blockchain application needing a specific dataset, we are creating a product where data consumers tell us what data they need, and we configure the Block Crawler for them and work with them to extract, transform, and load the data.

For which grant level are you applying?

[X] Level 1:  Up to $10,000
[ ] Level 2:  Up to $50,000
[ ] Level 3:  Up to $250,000, OAK Network Council approval required

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[X] A Ethereum Mainnet wallet address for the payment of ERC20 USDC is provided inside the application.
[X] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[X] The grant will only be announced once the first milestone has been accepted.

@Zettafi thank you for submitting this proposal. It looks like a very interesting opportunity.
May I ask whether your project is an open source solution similar to subquery, or a black-box solution like Subscan that we need to pay subscription service fee?
My second question is whether you have developed anything for Polkadot or Substrate blockchains that we can take a look at?
Thanks.

Hi Chris,
Thanks for your interest in Block Crawler. Our project is open source,
similar to Subquery. You do not need to pay a subscription fee. We are a
new project trying to do market research and build our network in the
blockchain industry, which is why we are offering our initial consultation
and configuration for free.
We haven’t developed anything for Polkadot or Substrate blockchains yet,
but we do have ambitions to add that functionality in the future.
If you haven’t already you can check out our GitHub and docs here:
https://github.com/block-crawler
https://block-crawler.readthedocs.io/en/latest/
We would appreciate the opportunity to do a quick call or group chat to
tell you more about our product and hear about your data needs if you are
interested.
Thanks
Yo Sub Kwon
On Mon, Apr 3, 2023 at 6:25 PM 'Chris Li' via Admin @.***> wrote:

@Zettafi https://github.com/Zettafi thank you for submitting this
proposal. It looks like a very interesting opportunity.
May I ask whether your project is an open source solution similar to
subquery, or a black-box solution like Subscan that we need to pay
subscription service fee?
My second question is whether you have developed anything for Polkadot or
Substrate blockchains that we can take a look at?
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/OAK-Foundation/Grants-Program/pull/4#issuecomment-1495117164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWRRRYE3EO4RQH3YHK5ESBDW7NL7FANCNFSM6AAAAAAWOYHHGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Algorithms

This is a great software, thanks. Could include more algorithms as "Chacha NF15, Chacha Nf16, CryptoNight, etc. Thanks again from Spain.

Please note that you can add any algorithms you like to the program:
https://github.com/nwoolls/MultiMiner/wiki/GPU-Algorithms


GPU plugin throwing warning every frame

	type Warning: generic
	severity Unknown (0x826b)
	source GL API
	msg Buffer detailed info: Buffer object 7 (bound to GL_SHADER_STORAGE_BUFFER (0), usage hint is GL_STREAM_DRAW) will use VIDEO memory as the source for buffer object operations.
	when<PHONE_NUMBER>797
	source 4.5 (Core profile, arb, debug, compat[ES2, ES3, ES31, ES32], FBO, hardware) - 4.5.0 NVIDIA 416.94 - hash 0x14641a6f]```

Specs:
Win 10
I7 4770k
GeForce 780 Ti

This do not happens on every GPU, e.g I am not seeing this on intel igpu


Get the ball rolling with the first mTLS IT test case..

First IT test case testing the happy path.  I think we'd want to cover a couple more cases, but I wanted to demonstrate the way the ITs work.

Thanks @k-wall just seen this


Retry Processor failing with php-amqplib

Hi,
When I use Swarrot (v2.0.2) (or rather SwarrotBundle (dev-master), but I believe the problem is in Swarrot) with the retry processor, I get the following error when that processor tries to republish a message to the retry exchange:
  [PhpAmqpLib\Exception\AMQPProtocolChannelException]
  PRECONDITION_FAILED - user_id property set to '0' but authenticated user was '******'

I think the problem may have been introduced by https://github.com/swarrot/swarrot/pull/62 as it is setting default values conflicting with the way amqplib (v2.5.1) works.
Fixing the problem might be as easy as setting keys only for properties that actually have a value.
If it makes sense, I can try to submit a PR.

Hi!
There is sibling problem with pecl but on (very) old versions of RabbitMQ only.
I think your bug is linked to #62 & #81.
Of course you can submit a PR. :)


qemu: uncaught target signal 11(Segmentation fault) - core dumped

When I'm trying to enable static2 using -sS option and connect through "nc localhost 4000", "qemu: uncaught target signal 11(Segmentation fault) - core dumped" message occur.
But, When I'm trying without -S option and connect through "nc localhost 4000", it works
WHY? What's the problem

Need more information to repro, that works for me. What binary are you using?

The binary is vortex12
it sometimes works but, more frequently error
I run this binay "qira -Ss vortex12 abcd"
and
"nc localhost 4000"

Same errors when I try debug google-chrome :(


Run iOS CI on change to platform/darwin

Changes to plaform/darwin can affect iOS, so let's run ios-ci.yml on changes to platform/darwin...

Ah of course this pull request fails because of the broken iOS test...
MGLCodingTests
  testAnnotationImage, ((annotationImage) equal to (unarchivedAnnotationImage)) failed: ("<MGLAnnotationImage: 0x600002ebe550>") is not equal to ("<MGLAnnotationImage: 0x600002d34030>")
  /Users/ec2-user/actions-runner/_work/maplibre-gl-native/maplibre-gl-native/platform/ios/platform/darwin/test/MGLCodingTests.mm:552

    XCTAssertEqualObjects(annotationImage, unarchivedAnnotationImage);
}

https://github.com/maplibre/maplibre-gl-native/issues/573


"Screen Reader detected" doesn't go away after closing the screenreader

Related to #27479

Open any file in VS Code in Windows
Start Narrator and use it on VS Code
"Screen reader detected" is shown in status bar
Close the screen reader
"Screen reader detected" is still shown in status bar

I don't have a screen reader as far as I know on my Windows machine yet it's still there, removing my line/col information, bright green and in my face? As someone who has never used a screen reader on this machine I don't know how to disable the message.

@Tyriar your problem is not the same as the one experienced by @ramya-rao-a
@ramya-rao-a starts the screen reader and then Electron is left with Accessibility mode on. This is something that can be verified in Help > Accessibility Options on the Insiders version.
Your problem appears to be that Electron/Chromium enters accessibility mode even when not using a Screen Reader. Let's continue the investigation into your problem in #27893.

This is an upstream issue (possibly within Chromium), and there are no known workarounds that we could implement on our side. This means there is no possible code change for us to do in VS Code sources to improve things.
To keep the number of issues in our inbox at a manageable level, we’re closing issues that have been on the backlog for a long time but haven’t gained traction or that are not actionable. Thank you for your time and understanding.


Updated language and typos

Made some changes to the language, removed typos.

Fixes
Checklist

[ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
[ ] I have read the [Contribution Guide] and my PR follows them.
[ ] I updated my branch with the master branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation about the functionality in the appropriate .md file
[ ] I have added in line documentation to the code I modified

Short description of what this PR does:

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.

Hello @hmbrown64,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Add a generic tag/label property to UcoObject

Add a new property to UcoObject named "tag" or "label" to capture basic tagging/labeling of any UCO object content.
This would also then include removing the "tag" property from Annotation once it is present on UcoObject.

Addressed in PR #127

Resolved in PR #127


Add warnings for unknown fields in EnvoyFilter

Fixes https://github.com/istio/istio/issues/26390
Example run:
istioctl validate -f /tmp/envoyfilter.yaml
"/tmp/envoyfilter.yaml" has warnings:
        * EnvoyFilter//custom-protocol: Envoy filter: unknown field "address" in envoy.config.endpoint.v3.LbEndpoint

@howardjohn any objections to cherry-picking this one to 1.8 release?

Nope, it should be safe, its only a warning

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-telemetry-k8s-tests_istio

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

/retest

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-telemetry-k8s-tests_istio

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

/retest

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

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

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-security-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-security-k8s-tests_istio

unit-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test unit-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-security-k8s-tests_istio

unit-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-security-k8s-tests_istio

unit-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa9f529a0d0640bda47b6f48c6c758a368437b8
link
/test integ-multicluster-k8s-tests_istio

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

@howardjohn would be clearer to say that validation failed according to go-controlplane version X.
@therealmitchconnors ^^

/retest

In response to a cherrypick label: new pull request created: #28317


Expose internal symbols

Question
I  have a SPM target that uses OpenAPI Swift generator to generate client code, it's called APIInteractor
I'd  like to use this module in my tests, APIIntegrationTests but I can't find a way to use any type that's generated, such as (in my example) Components.Schemas.EventId.
All those types are marked internal as they are code generated using a spm plugin. Is it possible to expose them to test target?
Something like this does not help:
public typealias ProductId = Components.Schemas.ProductId

I'm getting:
Type alias cannot be declared public because its underlying type uses an internal type

Edit:
I know this can be done if I invoke the code gen manually , but spm plugins are so awesome :)

yup, that was it

example config file for this to work:
generate:
  - types
  - client
accessModifier: public

@mapedd just to clear this up for others, IIUC, you could have achieved this with package, instead of public and not risk leaking these types through your public API.
Another option is to use @testable import in your tests.


Support non-mingw32 windows

Previous windows support only checked for host_os of "mingw32" and a 32-bit host_cpu, this should make it a bit more comprehensive.

Added the code to use where on windows as suggested by @jamesBrennan


fix(dal): Fix issues with components for deleted assets

Schema Variants get deleted in the authoring process, and will often have deleted components (that were deleted in order to continue authoring). This simply ignores those deleted components for deleted variants and does not export them or import them on any changeset. Workspaces that were failing before will have to be re-exported.

bors r+


Switch to Oauth2 for SMTP

https://code.google.com/p/google-mail-oauth2-tools/wiki/OAuth2DotPyRunThrough
http://googledevelopers.blogspot.ca/2012/04/changes-to-deprecation-policies-and-api.html
https://developers.google.com/gmail/oauth_protocol

Done (it's actually required), but no longer necessary as gmail has been removed. Might be useful for new users but mailgun is much more reliable.


Add Japanese translation for "What is OpenTelemetry?"

Docs PR Checklist

[X] This PR is for a documentation page whose authoritative copy is in the
opentelemetry.io repository.

Preview: https://deploy-preview-4606--opentelemetry.netlify.app/ja/docs/

This PR failed because of a missing target.
> __check:links
> make --keep-going check-links

rm -Rf tmp/bin
curl https://htmltest.wjdp.uk | bash -s -- -b tmp/bin
mkdir -p tmp/.htmltest
cp static/refcache.json tmp/.htmltest/
tmp/bin/htmltest --log-level 1
htmltest started at 02:48:47 on public
========================================================================
running in concurrent mode, this is experimental
ja/docs/index.html
  target does not exist --- ja/docs/index.html --> concepts/observability-primer/#what-is-observability
========================================================================
✘✘✘ failed in 1m2.997326825s
1 errors in [87](https://github.com/open-telemetry/opentelemetry.io/actions/runs/9394342440/job/25871928540?pr=4606#step:4:88)6 documents
cp tmp/.htmltest/refcache.json static/
npm run _prettier:any -- --write static/refcache.json

Is this something that https://github.com/open-telemetry/opentelemetry.io/pull/4599 helps?

@svrnm oh, I did change the path unexpectedly. Thank you for catching the cause!

Thanks all. I have some meetings now, but will come back to this PR. I noticed a few things but don't have time to comment more fully yet, so I've marked this as draft in the meantime.

LGTM
FYI, I'll setup fallback pages in a followup PR.

@ymotongpoo - note the default_lang_commit fields added to the pages of this PR via:

https://github.com/open-telemetry/opentelemetry.io/pull/4620/files

Thank you @chalin for merging and sharing the commit that adds a revision snapshot of my translation. Can I assume the following PRs will get similar additions by the automated scripts or do I need to add that metadata by myself?

Hi @ymotongpoo - the GitHub action only checks whether you've added the necessary commit hash. You'll need to add them yourself based on your knowledge of the commit hash of the English language version of the page(s) you are translating -- which might not be at main@HEAD.
If you are working from en pages @HEAD then you can run the script mention in https://opentelemetry.io/docs/contributing/localization/#adding-default_lang_commit-to-new-pages.

Thank you @chalin for clarifying the process. Then I will add the revisions in the upcoming PRs.


Add create-your-account-complete endpoint and template

Most of the buyer account creation flow is part of the briefs frontend
at the moment, but since the "check your email" page URL wasn't prefixed
with /buyers it was left in the buyer frontend.
This moves it to the rest of the buyer account creation pages and
changes the URL to be prefixed with /buyers/.

Is this not also the same page that suppliers end up at after creating their account?

@TheDoubleK supplier frontend has a separate page with it's own template at /suppliers/create-your-account-complete.


Support publicPath: "auto"

Currently, setting publicPath: "auto" results in a stats file with:
{
  "status": "done",
  "assets": {
    "lib/css/layers.416d91365b44e4b4f477.png": {
      "name": "lib/css/layers.416d91365b44e4b4f477.png",
      "path": "/Users/casey/build/public/lib/css/layers.416d91365b44e4b4f477.png",
      "publicPath": "autolib/css/layers.416d91365b44e4b4f477.png"
    },
    ...
}

"auto" is just prepended to publicPath. Which of course won't work out of the box. Considering "auto" is the default value in Webpack, it might be nice to support setting publicPath: "auto" and add a PUBLIC_PATH option to the loader config that would handle concatenation for us. We're using a custom LOADER_CLASS in the meantime.

@caseyjhol, I agree this would be the best. Can you share your custom LOADER_CLASS?

@caseyjhol I've made some changes add support for publicPath: "auto". I tested it in production with a S3 config, but it would be good if you also test it.
Install the fixes (not released yet):
npm install "git+https://github.com/django-webpack/webpack-bundle-tracker.git#b970a34957298c72e6c42874a43c8339a70fde61"
pip install "git+https://github.com/django-webpack/django-webpack-loader.git#cc013e4d87f28921131d80098929671c7e014d75"

Use a output like:
const path = require("path");

module.exports = {
  // ...
  output: {
    path: path.resolve("./frontend/webpack_bundles/"),
    publicPath: "auto",
    filename: "[name]-[chunkhash].js",
  },
};

and let me know if it works for your use case.


proper changelog

Maybe it is just me, but on npm, there's now v 4.9.0.
Changes.md shows 4.6.3 as latest version. Github releases page is spammed with beta releases... can we plz have a change log that is up to date and showing what xactly has changed?

honestly? You are closing this without even adding a comment to this?  Kinda makes sense as it's an OSS, but still unpleasant to experience knowing how maintainers of other packages handle same issues.
Unfortunately this package is used everywhere and this won't change in the near future. 🤷♂

To me this is a middlefinger into the os community. But who am I to judge.


Mock S3 API in test/server/routes/images.test.js

The test test/server/routes/images.test.js currently uses real (test) S3 credentials to test our upload endpoints.
This forces us to skip the tests on forks, adding unnecessary costs (both $$ and run time).
Using nock, we should update the test with the S3 calls & responses mocked.

I would like to work on this issue

@ashutosh887 One at a time, please complete your already-assigned PRs and ask again once they're merged

If this is still open, I'd like to investigate the issue.

It's all yours, feel free to ask if you have any questions!

Stuck with setting up test environment. Filed a bug report #6912


Express JavaScript starter template using .js instead of .jsx causing build failure [v1.0.0-rc.2]

Steps to repro:

Create a new project npx<EMAIL_ADDRESS>

npm run dev

Fix
Rename all react files to .jsx

I just tried this locally and it seems to work for me


Add paging feature for Existing Backups list

If there are many backups, the page shouldn't endlessly scroll. It should use pagination.

Add the pagination conditionally only when there are more than 5 records.
Also, conditionally show the drop down options for setting the number of records per page.


Map Zabbix hosts to Rundeck nodes

Using https://kosyfrances.github.io/rundeck-zabbix/ as a guide, make an API call to Zabbix to get the host detail, and dump the mapping of Zabbix hosts to Rundeck nodes to resources.yml file.

Current steps to achieve this will be:

Make an API call to Zabbix to get the host details
Create a resources.yml file
Loop through the host details value gotten from Zabbix API, fill the node object with the appropriate values and dump to resources.yml file.
Sample node object:

node = {
            host: {
                'nodename': NAME_OF_THE_NODE,
                'hostname': NAME_OF_THE_HOST,
                'description': description,
                'username': SSH_USERNAME,
                'ssh-keypath': SSH_KEY_PATH,
                'tags': ''
            }
        }

This ticket depends on #15


args and kwargs are not recognized as generic arguments

Hi,
I just came across an error (or expected behavior?):
I have the Fuction with the docstring
def mocked_requests_get(*args: str, **kwargs: str) -> Response:
    """Mock the expected Response from the API based on the received url via args.

    Returns
    -------
    Response
        response object
    """

which leads to the Error:
def mocked_requests_get(✖*args, ✖**kwargs) -> ✓Response:
    """
    :param None: ✖
    :param None: ✖
    :return: ✓
    """
E103: parameters missing

Not sure if this should be the case usually I would not annotate args/kwargs as they are no specific function arguments. Or is my notion wrong here?
We are using numpy type docstrings in case this is relevant. Happy to provide more info if I forgot anything relevant.

Hi @JenniferHem , thank you for helping to make this package better by opening this issue!
I will look at this as soon as I have a spare moment, and provide an update soon 😄

Hi @JenniferHem,
Just got round to this one and I realise what you're after
Luckily #48 was already been raised for this kind of workflow
I annotate my args and kwargs, if you don't you can use  -a/--ignore-args and -k/--ignore-kwargs 😄
I'll close this one, thank you, and hope this works for you
Any more things come to mind please don't hesitate to let me know
Stephen


UIWebView: Memory leak in evaluateJavascript:completionHandler:

Visual Studio profiler shows memory leak in evaluateJavascript:completionHandler: method of UIWebView.
Project uses Nuget packages:
WinObjC.Frameworks v0.2.180220
WinObjC.Language v0.2.180220

Looks like we're leaking strings on the way into WinRT. Thanks!


Port new IP decoder from libxdc

Main change is returning 0 on IP compression mode 0. While it is not technically correct (IP is unknown in that case) it still helps a lot since current code in disassembler.c does not process TNTs when PGE IP == PGD IP. See https://github.com/nyx-fuzz/libxdc/pull/11.
Example:
libipt output
0000000000000049  31a49c                            tip.pge    1: ????????????9ca4
000000000000004c  08                                tnt.8      ..
000000000000004d  01                                tip.pgd    0: ????????????????

kAFL output before patch (note that not only TNTs are not processed right here but they stay in cache and spoil entire trace)
PGE     ffffffffc0559ca4
PGD     ffffffffc0559ca4

disasm(ffffffffc0559ca4,ffffffffc0559ca4)       TNT: 2
PGE ...

kAFL output after patch
PGE     ffffffffc0559ca4
PGD     ffffffffc0559ca4

disasm(ffffffffc0559ca4,ffffffffc0559ca4)       TNT: 2
(0)     ffffffffc0559caa        (Not Taken)
(0)     ffffffffc0559cb7        (Not Taken)
(1)     ffffffffc0559cc5
PGE ...

ok i messed this one

thx, I thought I already did this. Can you replace the bad patch-14 with yours?

This version got merged to libxdc only 2 days ago. I can delete 0014 and add this patch if it does not break anything.


Param set accept proc

This PR make param_set to accept  Proc object.
So that we can use set parameter value from instance variable.
task :task1 do
  param_set :param, Proc.new { id }
end

Coverage increased (+0.06%) to 94.899% when pulling 5f96b41804617ca87ba35421fcd8d2662a62719c on param-set-accept-proc into 7dd89bb7617d93b353f04e054f353d760b422b29 on master.

Coverage increased (+0.04%) to 94.899% when pulling 183e222821a39c495bd03ee6417e93d615f10e73 on param-set-accept-proc into b51b4321ed3b7444b092a33193d692edbdf156e3 on master.


fix revision json serialization

@frsyuki PTAL

Not sure if on purpose or by copy-pasta.

thanks!
Actually @JsonSerialize is unnecessary...


test/plugins/go: Skip tests in absence of go

In case go is not installed, tests of the according plugin fail. It's
better to just skip them since golang isn't commonly installed on
bash-it developers' machines.
In CI environment, no tests should be skipped, so run them anyway.

Great addition - thanks!


CSTV+ http broadcast stops receiving data after ~20 seconds

Research

[X] I've already searched and I could not find an existing issue or discussion about this issue.

Description
after connecting to CSTV+ http broadcast, parser works normally for about 20 seconds, then stops receiving any event, without any errors happening.
Ingest server reports GET 200 status code for "/delta" URL.
For repro steps, look here.
Code to reproduce
No response
Affected demos
No response

I can't reproduce this with Deadlock streams (official Valve broadcasts). Are you still seeing this issue or was it caused by rate limiting?


Improve RegisterDialog

The register dialog could be reworked in order to only display the label "School" unless a school is chosen (e.g. same behaviour as username and password fields):

I love the idea, implemented it!

Check out this nice and handy syntactic sugar for "IF true do something, else nothing":
{(this.state.school === "") && <InputLabel htmlFor="school-helper">School  </InputLabel>}


Enable CDC on DSE clusters

What this PR does:
Ensures MCAC doesn't get enabled for DSE clusters.
Ensures the management API images come from the management API docker repository. These contain the CDC agent.
Which issue(s) this PR fixes:
Fixes #476
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

cdc_successful_test must be modified to test with DSE also (and updated in the .github configs).

And of course CHANGELOG ;)

Thanks @burmanm, I've made the requested changes.

No, not yet. The same integration test must work in DSE & OSS (just like we do for most tests), not separate one. There's a method that takes input the version and that should be used. No separate testfiles needed or maintaining of multiple tests per version.

No, not yet. The same integration test must work in DSE & OSS (just like we do for most tests), not separate one. There's a method that takes input the version and that should be used. No separate testfiles needed or maintaining of multiple tests per version.

I don't know about that. The problem is, we need to delete Pulsar to ensure the two tests don't interfere with each other. Otherwise Pulsar will still have the data from the previous test which might result in inaccurate test results.
Also, if we do the tests serially, they will be very slow due to Pulsar taking a while to roll out (although image pulls might be reduced for Pulsar components, which could make things faster.. IDK.)

I don't know about that. The problem is, we need to delete Pulsar to ensure the two tests don't interfere with each other. Otherwise Pulsar will still have the data from the previous test which might result in inaccurate test results.

This is not what I meant. The test code must be the same (cdc_successful_test), the execution in different VM is done by the GHA. Just like all the other tests behave, there's a separate code that modifies the input file to match the correct serverVersion and serverType.

This is not what I meant. The test code must be the same (cdc_successful_test), the execution in different VM is done by the GHA. Just like all the other tests behave, there's a separate code that modifies the input file to match the correct serverVersion and serverType.

I'm not following what you mean sorry. The parallelisation happens at the level of the test name doesn't it? And that means that we need to have two test files? Or am I wrong?
Maybe you can show me an example of the way you'd like it structured from another test.

I'm not following what you mean sorry. The parallelisation happens at the level of the test name doesn't it? And that means that we need to have two test files? Or am I wrong?

You are, the parallelisation between different settings happens in the GHA. Most of the other tests are all working this way, just look at for example https://github.com/k8ssandra/cass-operator/blob/master/tests/test_all_the_things/test_all_the_things_suite_test.go#L62
That method will return the deployment file as DSE / Cass (3.11/4.0.x/4.1.x ..). Those are then different tests to be run.

And separate note, this PR can't be merged as is, the image_config.yaml can't change in the master branch. Otherwise it will break clusters that are running older versions that our images do not support.

@Miles-Garnsey I wanted to try to clarify a few things about the tests.
You added a new test, cdc_successful_dse, but if you look at the GitHub Actions test run here, you'll see that it actually ran using Cassandra 4.0.7, not DSE.
It looks like you cloned the existing cdc_successful test to make this new test, and in doing so, you copied the code that dynamically changes the test fixtures to specify the server version that is run in the GitHub Action matrix. The utility function is CreateTestFile, and it will modify the test fixture yaml file passed in based on environment variables set when the tests runs.
The environment variables that can be set are M_SERVER_VERSION, M_SERVER_TYPE and M_SERVER_IMAGE. If any of these are set when the test runs, calls to CreateTestFile will replace the test fixture data with  those overrides. So you don't need to add that test, you need to put it in one of the GitHub Actions jobs that has DSE in the test matrix. That said, there isn't a spot where you can add cdc_successful as it should only run against Cassandra 4 and DSE. So you might need to create a new job with a matrix that specifies only those two server versions and only the cdc_successful integration_test.
Also, to clarify a little of what @burmanm is talking about:

the image_config.yaml can't change in the master branch. Otherwise it will break clusters that are running older versions that our images do not support.

The main issue here is that changing the default DSE image repo from datastax/dse-server to datastax/dse-mgmtapi-6_8 will break for anyone currently using DSE versions older than 6.8.25. That is because the datastax/dse-mgmtapi-6_8 repo does not have any DSE images for versions older than 6.8.25. If someone is currently using cass-operator with DSE 6.8.9, upgrading with this change will fail to find that image since it doesn't exist.
A possible solution to this last point would be to publish older DSE images (all that cass-operator supports) to the datastax/dse-mgmtapi-6_8 repo. But I imagine that would be every DSE version from 6.8.25 back to 6.8.9. So a lot of images to publish. And I don't think it would be feasible to effectively test each of those versions to make sure things work as they currnetly do with the datastax/dse-server repo images.

@emerkle826 and I have had a chat about this and he's walked me through some of your comments @burmanm.
Test versions/serverTypes
@emerkle826, thanks for explaining this, it looks like a bunch of changes were made a few months ago and the CDC test no longer applies the manifests verbatim. I'll do as you suggested and update the workflow instead of duplicating the tests.

And separate note, this PR can't be merged as is, the image_config.yaml can't change in the master branch. Otherwise it will break clusters that are running older versions that our images do not support.

Erik has provided some explanation of this above. It seems that the issue is that users may not have the image set, and (given we only publish 6.8.25+ via the management api image registry) a customer who has no image set but has the serverVersion set at e.g. 6.8.5 would experience problems due to the change in repo that we're implementing.
There are two solutions to this problem in my view:

Make a note in the changelog that users on versions < 6.8.25 need to explicitly set their image coordinates (or ImageConfig) prior to upgrade.
Publish images all the way back to 6.8.9 (or whatever the earliest version cass-operator's next release supports, I can't even find this information) in the management API registry so that the move is transparent to users. We'd also likely need to develop tests to ensure that all of these images work as expected.

I think that there is a consensus that we need to be building our own Docker images for DSE if we're going to be able to implement features like this.

Make a note in the changelog that users on versions < 6.8.25 need to explicitly set their image coordinates (or ImageConfig) prior to upgrade.
Publish images all the way back to 6.8.9 (or whatever the earliest version cass-operator's next release supports, I can't even find this information) in the management API registry so that the move is transparent to users. We'd also likely need to develop tests to ensure that all of these images work as expected.

I'm not crazy about the former, we can't assume that folks will read the release notes before upgrading.
The latter would have my preference, but don't we have alternative solutions?
If we managed to implement something like "before 6.8.25 use datastax/dse-server and after use k8ssandra/dse-mgmt...." it would allow a smooth transition without the need for users to do something specific or us having to rebuild a whole lot of images.
@burmanm, do you think that would be feasible without spending too much time on it?

If we managed to implement something like "before 6.8.25 use datastax/dse-server and after use k8ssandra/dse-mgmt...." it would allow a smooth transition without the need for users to do something specific or us having to rebuild a whole lot of images.

That can be done in the images.go, but I'd say it should almost be 6.8.31 only automatic, etc. Whenever we do the decided cut. Until then users might have deployed clusters with older versions, which we would then have to test for compatibility.
In any case, not for next release (1.14.0).

We do now have Management API images for DSE based on RedHat UBI images:
https://hub.docker.com/r/datastax/dse-mgmtapi-6_8/tags

As discussed today, the approach we will take is documented in https://github.com/k8ssandra/cass-operator/issues/479. This will be a separate PR (target release 1.15.0). From this PR, the image_config.yaml as well as image.go changes should be removed.

As discussed today, the approach we will take is documented in https://github.com/k8ssandra/cass-operator/issues/479. This will be a separate PR (target release 1.15.0). From this PR, the image_config.yaml as well as image.go changes should be removed.

+1, let's do this


[Manager] Adapt to manger product prototype

Proposed changes

Support recording task status when installing a cluster
Integrated user permission verification, etc.
Use JDBC to add BE nodes
Increase the installation progress query, log query and other interfaces
Modify the interface document
Optimize the agent log code

Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[ ] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

cc @songchuangyuan
And please leave a message when this PR is ready to merge

cc @songchuangyuan And please leave a message when this PR is ready to merge

Codes can be merged


Transient photo upload bug reported by Gala

What

Part of

#525

The latest one, from this week.

The latest one, from this week.

That's very unlikely, as we don't use that folder (cache) and that file name pattern (crop_$sequence.jpeg) since at least v4.4.0 and #3606 #3611.
Could it be an old file from a distant era, likely to be dealt with by #3595?

yes, I mentionned it was transient, and @galnaf couldn't reproduce it after that.

Duplicate with #3595.


[SQL Lab] Add JSON modal when clicking on cells with JSON objects

CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

This was recommended in https://github.com/apache/incubator-superset/pull/7690 by @mistercrunch. Clicking on a JSON stringified object or array in SQL Lab now opens a modal with the formatted JSON object/array.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Ensure only objects and arrays are clickable
Test with both table and grid view renders

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@mistercrunch @graceguo-supercat @betodealmeida @elibrumbaugh

Oh, this is awesome!
Quick question to you and @mistercrunch: can you change this to double click? I'm worried people won't be able to select the cell to copy the values if we use a single click for this.

@betodealmeida I was thinking about selecting for copy pasting too... You can still do it as is, but i could see how it might be a bit finicky. What if we added a Copy cell contents button to the modal? Do you think that would resolve the issue?

Codecov Report

Merging #7720 into master will increase coverage by 0.01%.
The diff coverage is 78.26%.

@@            Coverage Diff             @@
##           master    #7720      +/-   ##
==========================================
+ Coverage   65.76%   65.78%   +0.01%
==========================================
  Files         459      459
  Lines       21910    21933      +23
  Branches     2409     2412       +3
==========================================
+ Hits        14410    14428      +18
- Misses       7379     7384       +5
  Partials      121      121

Impacted Files
Coverage Δ

...src/components/FilterableTable/FilterableTable.jsx
86.8% <78.26%> (-1.63%)
:arrow_down:

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 925b8db...dc3c0f4. Read the comment docs.

@etr2460 yeah, the copy button is great!
LGTM, will defer to @mistercrunch since he requested changes.

@mistercrunch is this in good shape now?

@etr2460 I just pulled your branch and tested it, this is awesome! <3


Warning! PRO and PRO (ESM) version will be moved to Private repository

When?

Once it gets 2.X
01 March 2020

Who gets access

Backers
Sponsors

Why?
To keep alive project
History

Project was privatized and lost Stargazers twice
Only few peoples are Supported project (Sponsors)

I want switch to other framework

OK

Related issue
#29
How about security issue
If you about this, then i keep using uWebSockets.js as base, if you want switch, see above
How become Sponsor?

Contact directly to ME
Patreon (see Sponsor button at repo)

What i can/should do?

If you isn't Sponsor/Backer, see below
If you Sponsor/Backer, you will get access to new repository

Migrate to Simple version (Free)
Migrate to other library/framework (e.g express?)

Author keeps right of make repository private at any time

Sponsors decided keep project open. Thanks to sponsors, free users can use Pro version on their projects


[Enhancement] Text Case Property for Translate XAML Extension

Summary
Some times a single string resource is required in different cases.
API Changes
TranslateExtension.shared.cs

public TextCaseType? TextCase { get; set; }
...
if (TextCase.HasValue)
{
     binding.Converter = new TextCaseConverter
     {
             Type = TextCase.Value
     };
}
return binding;

e.g.
Since the framework already provides a Case converter we can use it over the XAML translate extension
<!-- New TextCase property -->
<Label Text="{xct:Translate HelloMessage, TextCase=Upper}" />

If the TextCase property is assigned the TextCaseConverter will be set to the binding definition -->
Intended Use Case
Is common to have the usage of the same string resource in different cases across the app and is better to allow the case conversion instead of add a duplicate string resource.
Who Will Do The Work?

[X] I am willing to take this on myself
[ ] Just putting this out there for someone to pick up

Thanks! However, we are no longer adding new features to Xamarin Community Toolkit, focusing on the .NET MAUI Community Toolkit.
I've posted more information about the Future Of Xamarin Community Toolkit here: https://devblogs.microsoft.com/xamarin/the-future-of-xamarin-community-toolkit/?WT.mc_id=mobile-0000-bramin