PayID Server-Side Forwarding

Hi i want to suggest payID forwarding.
That means that I want to be able to store my payid of e.g. bitrue (username$bitrue.com) behind my
very own payID. So if some resolver (like XUMM) sets out a requests for gafo666_bitrue$pid.gafo666.me
it should return the address written in e.g. username$bitrue.com .
Greetings GAFO666

Hey @GAFO , that sounds like it would likely be an extension / update to the PayID Protocol. Would you want to draft a PR on our RFC repository outlining your proposal?

And thinking through this further, I'm not even sure it would require a change to the PayID Protocol.
Couldn't you set up your server at pid.gafo666.me to have a PayID of gafo666_bitrue, but just pass along the request to gafo666$bitrue.com?
Or are you asking for an easy way to set that up using this project?

Hey @GAFO , that sounds like it would likely be an extension / update to the PayID Protocol. Would you want to draft a PR on our RFC repository outlining your proposal?

Im not sure if I understand what you mean by that - should i repost my suggestion there or ?

And thinking through this further, I'm not even sure it would require a change to the PayID Protocol.
Couldn't you set up your server at pid.gafo666.me to have a PayID of gafo666_bitrue, but just pass along the request to gafo666$bitrue.com?
Or are you asking for an easy way to set that up using this project?

My goal is that the payID server itself forwards (without additional code or reverse proxys) to another payID server if it finds a payID in its db record. The goal is that this becomes generic and standardized within payID servers and the entry could look like this:
{   "payId": "gafo666_bitrue$pid.gafo666.me",   "addresses": [     {       "paymentNetwork": "XRPL",       "environment": "MAINNET",       "details": {         "address": "username$bitrue.com"          "forrwardRequest":"true"       }     }   ] }
(maybe it could be a bit more generic so the payment network and environment dont have to be set for an forwarding)
Greetings GAFO666

Yeah, I guess there are two ways you could implement this.
Server-Side Solution
The first is a "server-side" redirect. You set up your PayID server (Server A) such that, for some PayID requests, it fetches the associated address(es) not from its own database, but from another PayID server (Server B).
One way to implement that might be the schema you've described above, but from the view of the client, it doesn't actually matter if the address is stored in Server A or Server B, it just gets back an address.
A solution like this doesn't actually need to be standardized across PayID servers, because the client is completely unaware that this is happening behind the scenes.
Client-Side Solution
This type of solution would rely on the client making multiple requests. You get back something like {"address": "username$bitrue.com" "forrwardRequest":"true"} as your response from Server A, realize you had been given another PayID, and make a second request to username$bitrue.com.
This type of solution would require standardization across the PayID ecosystem, since all servers and clients would need to understand this.
This type of solution would require an RFC on the RFC repository.
Thoughts
What do you think about the pros and cons of the two types of solutions I lined up? I think a server-side only solution would probably be preferable.

I would definetly go for the server side solution so the client would not notice it but the server handles all whats happening behind the scenes. This avoids - as you said - that the client would need to make multiple requests.
That said, when I refer to "payID server" I mean the nodejs server application of payID which runs on a physical/virtual server.
So the payID server provided on this git repo should be able to store the json pattern from above and recognize the forwardRequest flag. On a client request and based on that it should automatically forward the the request with header to the entry written in the address field (another payID) and after all that happened, return the result to the client.
Greetings GAFO666

So the payID server provided on this git repo should be able to store the json pattern from above and recognize the forwardRequest flag. On a client request and based on that it should automatically forward the the request (if the flag is set to true) with header to the entry written in the address field (another payID) and after all that happened, return the result to the client.

Do you think the forwardRequest flag is necessary? What about just storing a PayID as the address:
{ "paymentNetwork": "XRPL", "environment": "MAINNET", "details": { "address": "username$bitrue.com" }}

Then we could introspect the address before sending it over to the client, and if the address was a valid PayID, just go ahead and forward the request?

(feature should be shipped by this repo, to avoid that everyone would have to implement it as described)

That makes sense, but there are other PayID server implementations out there. I think this is a reasonable feature though, and it's not necessary that every PayID server in the world supports server-side PayID forwarding, just the server that you use.

Well I personally do think the flag is necessary, otherwise the payID server application would always forward if there is another payID stored within the address field. For our scenario that its ok, But let someone else appear who solely wants to read it out without forwarding. It should be flexible enough for different needs, not just ours. But if you would say that its too complex to add another flag because of reason x then its for me personally ok as well, just thinking in multiple directions.
Regarding other payID server implementations, well its theoretically fine to be added here - for the other implementations a howto add docu would be nice, imagine someone self-implemented a server and wants its, but doesnt know how to do it in a good way. Would be a possible scenario.
Yes I would need it, thatswhy Im suggesting it, next to the "fact" that it would be a helpful feature. On that way companies could act as a payID record holder for other payID issuers by simply using your implementation in a simple way. (like in domains, someone issues .de , someone issues .com .. but all are accessible due a DNS management above it)

Agreed that this would be a useful feature. And I think documenting how to set this up for roll-your-own servers would make sense.

Well I personally do think the flag is necessary, otherwise the payID server application would always forward if there is another payID stored within the address field. For our scenario that is ok, But let someone else appear who solely wants to read it out without forwarding. It should be flexible enough for different needs, not just ours.

I agree in principle, but what would the Content-Type header response for returning a literal PayID be?
The logical answer is application/payid+json... except that right now, that is reserved for "return all addresses associated with a PayID".
So, for a potential use case where we are responding with a literal PayID, we would probably want a different Content-Type.
I'm not entirely opposed to the flag, but I would want to have a concrete reason to build it that way up front. Especially since this is server-side only functionality that is opaque to the client, if we decided we needed a flag later to support returning a literal PayID, we could always refactor it, and nobody outside the server code should really be affected.

Also, to play devil's advocate, what is the problem this feature would solve?

Agreed that this would be a useful feature. And I think documenting how to set this up for roll-your-own servers would make sense.

Well I personally do think the flag is necessary, otherwise the payID server application would always forward if there is another payID stored within the address field. For our scenario that is ok, But let someone else appear who solely wants to read it out without forwarding. It should be flexible enough for different needs, not just ours.

I agree in principle, but what would the Content-Type header response for returning a literal PayID be?
The logical answer is application/payid+json... except that right now, that is reserved for "return all addresses associated with a PayID".
So, for a potential use case where we are responding with a literal PayID, we would probably want a different Content-Type.
I'm not entirely opposed to the flag, but I would want to have a concrete reason to build it that way up front. Especially since this is server-side only functionality that is opaque to the client, if we decided we needed a flag later to support returning a literal PayID, we could always refactor it, and nobody outside the server code should really be affected.

Hm well "application/external-payid+json" would sound good to me, it describes pretty good what it is - storing external payIDs -  so its quite intuitive.
Regarding a concrete reason for the flag, well that's for if(x) scenarios, in my personal opinion its always good to be flexible enough to address different "needs" when the effort to make it possible is relatively low. (I do not know how complicated it is)

Also, to play devil's advocate, what is the problem this feature would solve?

There will be many providers for payIDs, it is a way to bring them under one hood. Imagine an provider only hosts ACH payIDs and another only XRP and BTC payIDs and another whatever asset you want to name. Then you end up with the same problem payID is trying to solve. Concluding there should be payIDs for payIDs. At least in my personal logic it sounds well put.
You could take other examples like the domains and DNS as I did above - there is .de .at .com .whatever with a list of sites running on each of them. So you put them under one hood that they are all accessible & manage them. (and lets not forget that behind each domain ending and the domains on it are IPs, even each subdomain on a domain can have a IP)  There are many examples in IT why it would make sense to implement forwarding and when it works in other standards, why wouldn't it be good in the new payID standard ?
Greetings GAFO666

If you have gafo666_bitrue$pid.gafo666.me that forwards to username$bitrue.com, what would you want the associated payId of the response to be? gafo666.me? or bitrue.com?
Why?

If you have gafo666_bitrue$pid.gafo666.me that forwards to username$bitrue.com, what would you want the associated payId of the response to be? gafo666.me? or bitrue.com?

Good question, I think it would be more logical that the end-destination would be shown as payId entry in the response because the one forwarding acts as a address book to find the end-destination. That would also make sense since the actual addresses (+ eventual tags) are maintained by the end-destination. In this particular example an exchange.
And I thought about the paymentNetwork entry in the meantime regarding forwarding and came to the conclusion that it should stay for the forwarding. And that because of the following example:
my Address book payID :  gafo666_exchanges$pid.gafo666.me
On XRPL Mainnet : username$bitrue.com
On BTC Mainnet: username$someotherexchange2
On ETH Mainnet: username$someotherexchange3
so depending on which header param is given (xrpl/btc/eth one) in the request towards 'gafo666_exchanges$pid.gafo666.me' it forwards to the right entry.
One question on my side:
Can you have more than 1 entry under the same paymentNetwork in a payID ? Didnt try that yet.
Because if thats the case you would need to choose which one is forwarded to by flag and which are not.

Can you have more than 1 entry under the same paymentNetwork in a payID ? Didnt try that yet.
Because if thats the case you would need to choose which one is forwarded to by flag and which are not.

Not currently. It's under discussion as something to consider, but right now PayID assumes a single address per paymentNetwork, environment tuple.

Can you have more than 1 entry under the same paymentNetwork in a payID ? Didnt try that yet.
Because if thats the case you would need to choose which one is forwarded to by flag and which are not.

Not currently. It's under discussion as something to consider, but right now PayID assumes a single address per paymentNetwork, environment tuple.

Ah okey - well would be an interesting feature as well, but then it would require a selection on the user-side I would assume.
(lets save that for another thread tho ;) )
Greetings GAFO666


added nodeServer.js file for backend

I just added the nodeServer.js file for the backend.
Also move the unused solidity file into a folder.

Need a little update first


Add endpoint_private_access and endpoint_public_access options to vpc_config

I'm submitting a...

[x] feature request

What is the current behavior?
Currently there is no way to set the endpoint_private_access and endpoint_public_access options inside the vpc_config block.
https://www.terraform.io/docs/providers/aws/r/eks_cluster.html#endpoint_private_access
Are you able to fix this problem and submit a PR? Link here if you have already.
I can submit a PR, haven't done so yet though.

Done: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/314


fix: Using in filter within not filter

What kind of change does this PR introduce?
This PR removes the bug preventing users from using in filter within not filter.
related to https://github.com/supabase/postgrest-dart/issues/36
What is the current behavior?
supabase.from('users').select().not('id', 'in', ['foo', 'bar']).execute();

Results in failed to parse filter (not.in.[])" (line 1, column 8) error.
What is the new behavior?
Using in filter within not is supported.

Lgtm!!! thank you @dshukertjr


Updated iOS Radio button & checkbox documentation.

Ticket: https://thumbtack.atlassian.net/browse/DS-989
WHY:
Updates in radio button and checkbox iOS feature set and API require corresponding updates in documentation.
WHAT:
Updated docs to reflect Thumbprint changes:

Dropped error state for checkbox & radio buttons (not in use nor expected to be in use in the future)
Renamed labeled versions of the controls to LabeledRadio and LabeledCheckbox
Radio is now equivalent to Checkbox, just the graphical control.
LabeledRadio is feature equivalent to LabeledCheckbox, specifically it allows for leading/trailing content placement.

TESTING:
Best I can tell the syntax of the changes is correct. Unaware of how to test the fully functional pages.

I was already looking at the formatted results but there were some links that wouldn't work from GitHub.


[FEATURE]  Support non-disruptive volume-related setting updates

Will existing deployments be migrated to the new default priority class on the fly? I am not sure if this is possible.

In the current implementation, it's not possible. However, we should improve this part to have the following support to prevent any interruption for running volumes.

When changing any volume-related Pod configuration (ex: IM pod, share manager pod, upcoming object storage/s3gw pod) like priority class, the change will only take effect when doing volume upgrade or volume reattachement.

Extra info from @PhanLe1010

cc @shuo-wu @derekbit @c3y1huang
Originally posted by @innobead in https://github.com/longhorn/longhorn/issues/6528#issuecomment-1822414466

To me, it sounds like the issue description and @PhanLe1010's suggestion are different.

The issue description implies a kind of lazy update. We will allow a setting (like priority-class) to be changed at any time, but we won't actually change the configuration of the running pods (like the instance-manager pods) until they are restarted "naturally".
@PhanLe1010's comment implies that we will simply refuse to allow the setting change unless all volumes are safely detached.

@harridu was asking for the former in the Rancher Users Slack (https://rancher-users.slack.com/archives/CC2UQM49Y/p1700549015471709) and in https://github.com/longhorn/longhorn/issues/6528#issuecomment-1688736579.
Unless I am misunderstanding here, we must decide which of these two paths we will take.

Your understanding is correct, so this is why I said there is an extra info from Phan.
The goal here is to have lazy update to make settings eventually effective without interrupting any running volumes.
If there are any obstacles to prevent achieving this, we should at least have a validation to disallow applying the above settings when there are still running volumes.

Assigned to @mantissahz because currently he is working on a related issue, https://github.com/longhorn/longhorn/issues/6528. This issue will be appropriate to handle by me together.

@mantissahz Where we are?

@innobead
I am testing not to delete pods for modifying the setting like guaranteed-instance-manager-cpu if there are volumes attached and start to prepare the LEP.

Test steps related to upgrade from v1.5.x need to wait https://github.com/longhorn/longhorn/issues/7642 reslove first.

Need to verify all danger zone settings worked as expected.

Verified pass on longhorn master (longhorn-manager a78c2a)
Below danger zone settings will only update to instance-manager pod after volume detached.  (Fresh installed master-head and upgrade from v1.5.x to master-head)

priority-class
taint-toleration
system-managed-components-node-selector
storage-network


Add mean for sparse matrices

Takeover #3085.

Jenkins, test this please.

Jenkins CI test (for commit 18f0014ce5e1c18a6b43051e71e7556001e13221, target branch master) succeeded!

LGTM.


Move config file format to YAML

Updates the config to use YAML rather than a weird properties format
that is actually JSON but allows comments through the removal of lines
starting with #

@radai-rosenblatt Any chance I get some eyes on this?


inputs in nixosModule is not available for external flake

nix build "github:ratson/bug-report/flakelight-nixos-module?dir=flake2#nixosConfigurations.vm2.config.system.build.vm"

gives
error: attribute 'inputs'' missing

While the following is working,
nix build "github:ratson/bug-report/flakelight-nixos-module?dir=flake1#nixosConfigurations.vm1.config.system.build.vm"

Source code in https://github.com/ratson/bug-report/tree/flakelight-nixos-module
@accelbread Would you check if usage in flake2/flake.nix is correct?
FYR, here is a copy of it,
{
  inputs = {
    nixpkgs.url = "nixpkgs/nixos-unstable";
    flake1.url = "path:../flake1";
  };
  outputs = { nixpkgs, flake1, ... }@inputs:
    let
      system = "x86_64-linux";
    in
    {
      nixosConfigurations.vm2 = nixpkgs.lib.nixosSystem {
        inherit system;

        modules = [
          flake1.nixosModules.default
        ];
      };

      packages.${system}.hello2 = flake1.packages.${system}.hello1;
    };
}

There is test.sh script in the repo to run locally to verify the bug.

Sorry for delay have been busy.
The inputs' arg is provided by flakelight, so is not available in second flake. The args to modules come from the nixosSystem as well, so inputs' in a module refers to the inputs of the flake defining the system, not the one that defined the module.
If you want to use packages from another flake, I'd recommend having the module use the package from the pkgs arg, and having the second flake's system use the first's overlay.

@accelbread Should the inputs' be provided to flake1.nixosModules.default with flake1's inputs?
Or is there a way to refer to flake1's inputs in `flale1.nixosModules

To better illustrate the problem, I updated flake1 to include vm2,
https://github.com/ratson/bug-report/blob/flakelight-nixos-module/flake1/flake.nix#L13-L19
      nixosConfigurations.vm2 = nixpkgs.lib.nixosSystem {
        inherit system;

        modules = [
          self.nixosModules.default
        ];
      };

It is strange that nix build ./flake1#nixosConfigurations.vm1.config.system.build.vm works, while nix build ./flake1#nixosConfigurations.vm2.config.system.build.vm fails.
Here is the vm1 code,
https://github.com/ratson/bug-report/blob/flakelight-nixos-module/flake1/nix/nixos/vm1.nix
{ inputs, ... }:

{
  system = "x86_64-linux";

  modules = [
    inputs.self.nixosModules.default
  ];
}

if you change vm2 too not call nixosSystem explicitly, it will work:
      nixosConfigurations.vm2 = {
        inherit system;

        modules = [
          self.nixosModules.default
        ];
      };

If you don't call it, flakelight can propagate inputs and etc. to the nixos invocation since it calls it. If you call it yourself, flakelight can't add its stuff. You can call it yourself and add the flakelight stuff by adding config.propogationModule to your modules. Can see here: https://github.com/nix-community/flakelight/blob/2a96b83bf6ffad4b8a15afe19e883ca1a1720d88/API_GUIDE.md?plain=1#L965-L977

self.nixosModules.default should propagate inputs and moduleArgs for outputs, so non-flakelight users could use it.
I don't know if it can be generically implemented or not, here is a working example,
https://github.com/ratson/bug-report/blob/d0034228e83bb99f30bb60ea905bc2ee262ec364/flake1/flake.nix#L21-L29

Yeah the problem with that approach is that the parameters are no longer named, and the parameter names affect how modules are passed args. A module with { ... }@args will only get specialArgs, not regular args. Additionally, can't tell if a parameter is meant to be for the NixOS module system or meant to be handled by wrapper.
In order to use host flake module args, you'd have to capture them.
Something like the following works:
nixosModules = { inputs, ... }: {
  default = { pkgs, ... }: {
    environment.systemPackages = [
      inputs.self.packages.${pkgs.system}.hello1
    ];
  };
};

That way inputs in the default module is captured from defining flake rather than NixOS module args.
To autoLoad that would have to use nix/nixosModules.nix. Can't use its own file by default. Or could have a nix/nixosModules.nix that autoloads nix/nixosModules/ but calls it first with moduleArgs allowing:
{ inputs, ... }: { pkgs, ... }: {
 environment.systemPackages = [
   inputs.self.packages.${pkgs.system}.hello1
 ];
};

However, can't do the above automatically since given a function, we don't know if flakelight should call it or not. We could perhaps try calling it and seeing if result is a function, and if so it needs to be called else not. This could cause an evaluation failure though if its not meant to be called, and we passed the wrong args. Theres also no way to catch hard errors. For bundlers we use a similar trick where we wrap the function, capturing moduleArgs, and when called it figures out if the function is nested, and passes args accordingly, but this works since it has the real args. That might potentially work here as well, as long as we can use lib.setFunctionArgs to have the same args on wrapped function. Thought that would mean turning every exported module into a functor, which I'm not sure is a good idea.

@accelbread Thanks for pointing out the lib.setFunctionArgs function, didn't know that.
I have generalized the wrapper code to be,
https://github.com/ratson/bug-report/blob/f9e2bd01f644756953f10443343e10934cdac367/flake1/flake.nix#L29-L34
      nixosModules.wrapped =
        let
          f = lib.toFunction import ./nix/nixosModules/_default.nix;
          g = args: f (args // { inherit inputs; });
        in
        lib.setFunctionArgs g (lib.functionArgs f);

You'll also need to filter out inputs, so that if their nixpkgs modules don't have an inputs arg it would still work, like follows:
      nixosModules.wrapped =
        let
          f = lib.toFunction import ./nix/nixosModules/_default.nix;
          g = args: f (args // { inherit inputs; });
        in
        lib.setFunctionArgs g (lib.removeAttrs (lib.functionArgs f) ["inputs"]);

How I'd do modules that need moduleArgs from defining flake is set nix/nixosModules/default.nix to:
{ lib, flakelight, moduleArgs, ... }:
lib.mapAttrs (_: v: v moduleArgs) (flakelight.importDir ./.)

If you have that, then your module files are functions returning modules, for example nix/nixosModules/_default.nix for nixosModules.default could be:
{ inputs, moduleArgs, ... }:
{ pkgs, config, ... }: {
  environment.systemPackages = [ inputs.self.packages.${pkgs.system}.hello1 ];
}

Right now, I am putting all modules requires inputs in flake.nix as suggested,
nixosModules = { inputs, ... }: {
  default = { pkgs, ... }: {
    environment.systemPackages = [
      inputs.self.packages.${pkgs.system}.hello1
    ];
  };
};

@accelbread Do you think it is possible to utilize file extension convention, e.g. ./nixosModules/[name].functor.nix to support the file content like
{ inputs, ... }: { pkgs, ... }: {
 environment.systemPackages = [
   inputs.self.packages.${pkgs.system}.hello1
 ];
}

Or provide such functionality via extra flakelight module?

Yeah, a folder name could be used. A flakelight module could add a nixosModulesFn option or something, which would automstically work with autoloading.


Update package.json description (fix #541)

Fixes #541.

@papb thanks for contributing. The thing is, that sequelize-typescript currently aren't working with the latest beta release of sequelize@5. This is because of this #529. Can you also mention this in the readme? Then I can accept your PR. Thank you :)

@RobinBuschmann - Thanks for the feedback. I've updated the readme now. Let me know what you think about it.

👍


⚠ Bofrost.de has degraded performance

In 143592a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1750 ms

Resolved: Bofrost.de performance has improved in 650a633.


Fix Blazor E2E tests and remove obsolete BindMethods code

See commits for details

The debug version of the .js files does exist on my machine after building. Did something change with this recently? Or is there some other reason why it needs to be hardcoded as Release now?

The debug version of the .js files does exist on my machine after building. Did something change with this recently? Or is there some other reason why it needs to be hardcoded as Release now?

I have no idea what changed. I have been unable to run the client-side E2E tests since I got back from Spain.
The Debug folder is created when you build but it's not checked in. I don't know what the current state is supposed to be because honestly, this all seems unacceptable.

I'm removing the hardcoding to unblock this. Now you'll get an error if you try to build a one of these projects without having the appropriate JS files present. I think this is an improvement to the current state because it now fails noisily instead of silently.

I don't know what the current state is supposed to be because honestly, this all seems unacceptable.

Totally agree - there are multiple problems with the build currently. For me, not running the E2E tests in CI is the worst of them.

Now you'll get an error if you try to build a one of these projects without having the appropriate JS files present. I think this is an improvement to the current state because it now fails noisily instead of silently.

Good, I agree that's an improvement!

The Debug js files aren't checked in so we'll have to find out if this breaks people's workflow or not, but I still see it as an improvement.

Note that this breaks build --all but it was broken already (invalid build output due to silent failure).


Gulp task executes dependencies and stops without error

Hi,
I'm running into a strange issue:
I've got a gulp task 'release' that depends on many subtasks, and when I run it, half of the time it executes everything up to the 'build' task dependency, but not the release task, and finishes without starting "release" without an error.
I start gulp with an npm script release "gulp release".
What were you expecting to happen?
I am expecting the gulp task 'release' to start, and possibly fail.
What actually happened?
The gulp task 'build' (which is the last to run, and that takes 3µs to run, because it only wraps other dependencies) finishes properly, and the process exits.
Please post a sample of your gulpfile (preferably reduced to just the bit that's not working)
I haven't pasted all the tasks, but it shows the structure of my gulpfiles, I presume the bug comes from the gulp task build being really fast.
Dependency tasks may return streams, or promises (some are sync and don't return anything).
const gulp = require('gulp')
const builder = require('electron-builder')
const jetpack = require('fs-jetpack')

const shouldPublish = process.env.GH_TOKEN && !process.env.NO_PUBLISH

gulp.task('build-packaging-resources', [
  'build-dmg-background',
  'build-fileIcon',
  'build-setupIcon',
  'build-appIcon',
  'build-logo',
  'build-plist'
])

gulp.task('build', [
  'build-js',
  'build-scss',
  'copy',
  'build-resources',
  'finalize'
])

gulp.task('clean-releases', (callback) => jetpack.dirAsync('./releases', { empty: true }))

gulp.task('release', [
  'clean-releases',
  ...(process.env.NO_REBUILD ? [] : [ 'build', 'build-packaging-resources' ]),
  ...(shouldPublish ? [ 'push-changelog' ] : [])
], () =>
  builder.build({
    publish: shouldPublish ? 'always' : 'never',
    ia32: true,
    x64: true
  }))

What version of gulp are you using?
gulp 3.9.1
What versions of npm and node are you using?
node 7.5.0
npm 4.2.0
If anyone has an idea ?

This is not a support forum. Support questions should be directed to StackOverflow.

I may not have found how to reproduce it (and yes this is a bad bug report, I'm sorry).
Gulp doesn't execute the task it has been asked to execute without throwing an error. How is this not a bug?

Are you missing a callback or not returning a stream?

Hi,
I've checked every gulp subtask, there are four cases:

some are sync and don't return anything
some are async and they return a promise (or may throw an error instead of rejecting the promise)
some return streams
some don't have a function, and are just wrappers around other gulp tasks (such as 'build')

What's strange is that it happens half of the time, and when it does it finishes with exit code 0 without logging any error, and just finishes before starting the 'release' task which was called.

It's almost certainly a problem with your code - post on stack overflow with a code example (feel free to post a link here) and post back here if it does turn out to be a bug :)


Improve Message Coding table headers

We're seeing people interpret the dashboard as showing the total number of messages received in each dataset, and the fraction of WS/NC being interpreted as representative of the analysis dataset. These interpretations, however, are incorrect because the dashboard actually shows the number of unique messages and the fraction of those unique messages.
We could start to resolve this by renaming the table headers to e.g. "Unique Texts" rather than "Messages" etc. We might also add a description underneath the table that explains those columns and what can and cannot be inferred from them.

@as2388 please send me some of the inference and description you would like to appear on the table, I would like to add to them on my descriptions.


Successful job deletion

Was just wondering if this driver deletes successful jobs once they are complete? Currently this doesn't seem to be the case as my success list grows to a massive value (over 1 million)
From what I've researched this is meant to be the default behaviour as shown here https://discuss.hangfire.io/t/how-to-configure-the-retention-time-of-job/34

Thank you for your feedback. Planned to be fixed in next version.

What would this involve from an implementation perspective? Would it be possible for me to fork a copy and get started on it?

@lukasroberts I'm not sure yet regarding what exactly need to be fixed - need to investigate this. If you can take a look on this it would be very helpful for sure, so feel free to do that :-)

After some investigation, it appears that the ExpirationManager does indeed fire but only at application startup. after this it does not run anymore. What would be the best approach to make this the case?

it might be helpful to check how it's implemented for SQL Server storage.
just check references where is ExpirationManager called in that storage and ensure it's called in same place for Mongo :-)

I couldn't notice any difference and i think it is actually running fine after logging the expiration manager


Patch 8

Fix some minor details in old cmdlets.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsHybridApplicationEndpoint.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsImConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsPushNotificationConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsPushNotificationConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsPushNotificationConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsImConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsPushNotificationConfiguration.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Feature]: Translate the values still in English in the Spanish and French translation files

Feature Summary
Some of the Spanish and French translation files (es.json and f.json) still have English text for several strings. We should translate all such strings into their respective languages.
Detailed Description
To do this, look in src/translations/es.json and src/translations/fr.json for any strings still written in English and translate them into Spanish or French (to match the respective file).

Hey
In french i haven't seen much to fix, so I 'll let a spanish speaking person handle it,
I've notice one piece of text in english though, which is :
noJackWithQueen": "You cannot use a Jack while your opponent has a Queen". -> Vous ne pouvez pas jouer un Valet car votre adversaire a une Reine.
And a small mistake here :
"strongest": "le plus for" --> "le plus fort" (whith a T at the end)


Create test.py

@NimaSarajpoor
This was a successful experiment. It shows how one can co-author with someone in github realm. Next time, try to do it on your local machine rather than on github web


Can't create new Angular project with angular-cli

I've installed @angular/cli version 1.6.3 and then did:
ng new frontend --routing
cd frontend
ng build

I got an error saying main.ts and polyfills.ts are not included in tsconfig.json .
I've seen two issues on the matter, one was about ts placed in the wrong place, the other was closed as a duplicate of the first. This is clearly not the same case - I did not create any ts files, and all I need to do is run that series of commands and get the exact same behavior. This happens on several of our development machines (all with Windows 10)

Versions
Angular CLI: 1.6.3
Node: 8.9.3
OS: win32 x64
Angular: 5.1.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.6.3
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.3
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Repro steps

    ng new frontend --routing
    cd frontend
    ng build

Observed behavior
The following errors:
ERROR in d:/chelem/ShalevItzkovitz/Interactions/frontend/src/main.ts
Module build failed: Error: d:\chelem\ShalevItzkovitz\Interactions\frontend\src\main.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
    at AngularCompilerPlugin.getCompiledFile (d:\chelem\ShalevItzkovitz\Interactions\frontend\node_modules\@ngtools\webpack\src\angular_compiler_plugin.js:653:23)
    at plugin.done.then (d:\chelem\ShalevItzkovitz\Interactions\frontend\node_modules\@ngtools\webpack\src\loader.js:467:39)
    at <anonymous> @ multi ./src/main.ts

ERROR in d:/chelem/ShalevItzkovitz/Interactions/frontend/src/polyfills.ts
Module build failed: Error: d:\chelem\ShalevItzkovitz\Interactions\frontend\src\polyfills.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
    at AngularCompilerPlugin.getCompiledFile (d:\chelem\ShalevItzkovitz\Interactions\frontendnode_modules\@ngtools\webpack\src\angular_compiler_plugin.js:653:23)
    at plugin.done.then (d:\chelem\ShalevItzkovitz\Interactions\frontend\node_modules\@ngtoolswebpack\src\loader.js:467:39)
    at <anonymous> @ multi ./src/polyfills.ts

Desired behavior
ng new should create a project that can be built and served.

I had this bug today, running with –preserve-symlinks worked but without it would not build. I was running with from windows cmd. I think there is still a problem.

I was having this same bug for a couple hours. I found out that I was in the wrong working directory.
my directory: ~/My Documents/Github/MyProject/client
correct directory: ~/Documents/Github/MyProject/client


DEPRECATION WARNING: Initialization autoloaded the constant BadgeLabelHelper

What Ruby, Rails and RSpec versions are you using?
Ruby version: 2.7.0
Rails version: <IP_ADDRESS>
RSpec version: 3.9.0
Observed behaviour
When I run rspec I get this warning:
DEPRECATION WARNING: Initialization autoloaded the constant BadgeLabelHelper.

Being able to do this is deprecated. Autoloading during initialization is going
to be an error condition in future versions of Rails.

Reloading does not reboot the application, and therefore code executed during
initialization does not run again. So, if you reload BadgeLabelHelper, for example,
the expected changes won't be reflected in that stale Module object.

This autoloaded constant has been unloaded.

Please, check the "Autoloading and Reloading Constants" guide for solutions.

I saw this similar closed issue, but in this case it doesn't seem to be related to my code since I'm not using this constant BadgeLabelHelper
The tests run just fine.

Let's try to track this down. Use this (I hope it still works), replace annoying with Initialization autoloaded the constant BadgeLabelHelper.
In Pry's REPL that pops up see caller and post the backtrace here with the code from files from yoyr Rails init phase.

Its the same problem, but its likely the helper is being autoloaded as helper :badge_label in a controller or view etc. Debug your initialisation to find whats causing it.

There is no presence of badge_label nor BadgeLabel or BadgeLabelHelper in my project. Tried also the script for debugging what @JonRowe linked but couldn't get anything useful out of it unfortunatelly. I'm using ruby 3.0.0p0 and Rails 6.1.1.

This is still a rails issue, we do not do any auto loading in RSpec, we just boot your Rails app. Somewhere in your application code or dependencies you are using this helper, its not a constant within RSpec. If this file is not present within your app then remove any engines and gems in use until it goes away.

I am having the exact same error message, and nowhere in my code do I have a reference to this BadgeHelper.
This is on a fresh Rails project with 1 controller, and 1 model and this error still pops up when using rspec-rails
Does't happen for example with minitest

Actually the only gem I can find that uses the BadgeLabelHelper seems to be twitter-bootstrap-rails

until twitter-bootstrap-rails gem will fix it - the solution could be to add config/initializers/twitter_bootstrap_rails.rb with
gem_dir = Gem::Specification.find_by_name("twitter-bootstrap-rails").gem_dir
require "#{gem_dir}/app/helpers/badge_label_helper"


Download enhancements

This pull request adds two options to the download feature:

an option to create folder hierarchy as mentioned in #39 (passed to function as boolean createFolders) &
an option to skip download if the file already exists in the same path (passed to function as boolean skipIfExists).

Furthermore, the CLI download command has been updated with two flags to represent those options, respectively --folders and --skip.

Hi fwicht thanks for the pull request!
I tested it out locally and looks good to me. Merging!


added option to generate 3d transforms, updated test and readme

Thank you for the PR!
I'm not sure I like the commas logic... it is confusing IMO because there are some CSS properties that accept multiple values separated by commas, whereas here it means something else entirely. But more than that, I'm not sure I like the idea of reusing the translate option for two different transform functions. I think a more explicit translate3d option would be clearer. Ideally the user shouldn't have to read the documentation to know how the plugin works, you know?
Also, I think if we want to add 3D transforms to this plugin, we should add all of the 1-axis transform functions before adding multiple-axis transforms:

translateZ
scaleZ (is it any different from scale?)
rotateX
rotateY
rotateZ (is it any different from rotate?)

I think we can add all of the above without adding any option, for instance by generating translateZ utilities for all the translate values, rotateX and rotateY utilities for all the rotate values, etc. We already do it for the 2D translate and scale functions. Or perhaps we could have a new 3dtransforms boolean option that controls whether the above are generated or not (in an effort to constrain the filesize if someone is sure not to use 3D transforms and doesn't use PurgeCSS)?
Other useful 3D transform utilities would be transform-style, perspective, perspective-origin, and backface-visibility.
What do you think?

I've been thinking about this some more, and I think a new 3d option is the right approach. I created an issue here: #5
Once that's done then we can tackle more complex transforms like this PR does with translate3d().

@magicspon That said, I changed my mind about the commas logic; I think it's a pretty good idea since commas are never accepted in a translate() anyway. It would be better if only two values generated translate([value-1], [value-2]) instead of translate3d([value-1], [value-2], 0), though. And the same logic should be applied to scale.

Closing to prefer issue #6. Thank you for the PR though, appreciate it!

@benface heyo. sorry about the radio silence, been mega busy with work. Issue #6 sounds good to be.  Nice one.


Insufficient information for topic

Describe the issue
Documentation introduces a very important topic Content Scene arrays with NO information about their purpose, usage, or location.
Feature area
Information about Content Scene
Existing doc link
https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/SceneSystem/SceneSystemGettingStarted.html
Additional context
Add any other context about the problem here.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


if the MediaData textScaleFactor is bigger than 1.0, then the datepicker will overflower

_Originally posted by @CaiJingLong in
https://github.com/flutter/flutter/issues/20171#issuecomment-431284368
flutter doctor -v
flutter doctor -v
[✓] Flutter (Channel dev, v0.10.0, on Mac OS X 10.13.6 17G65, locale zh-Hans-CN)
    • Flutter version 0.10.0 at /Users/caijinglong/Library/Flutter/flutter
    • Framework revision d954ae6850 (10 days ago), 2018-10-09 16:21:06 -0400
    • Engine revision bf377896ff
    • Dart version 2.1.0-dev.6.0.flutter-a50dfd6698

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.2)
    • Android SDK at /Users/caijinglong/Library/Android/sdk/
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.2
    • ANDROID_HOME = /Users/caijinglong/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 28.0.2
    • Dart plugin version 181.5616
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] VS Code (version 1.27.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.19.0

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Please add the output of flutter doctor -v.

Duplicate of #20171

Duplicate of #20171


promises

Would you consider using https://github.com/WhoopInc/supertest-as-promised rather than supertest, so we can chain more easily and don't have to call done()?

Honestly I'm not a fan of promise. However, you can still use supertest-as-promised by adding it to your local bootstrap. You won't be able to override request though so you would have to define it using some other name.


No Notification when sending a new page in Chrome

The task was added to inbox indeed but didn't got notification to confirm it.
I've turned on the option.
I was using latest Chrome
Chrome is up to date
Version 110.0.5481.100 (Official Build) (arm64)

and was sending a youtube link to TickTick: https://www.youtube.com/watch?v=SV2crCB-uw4
Also reproduced on other webpages

Hi, thanks for your feedback!
Did you have any kind of "do not disturb" / focus mode activated on your OS? The extension uses your OS' notification system, so it will be impacted by these types of settings.

Stale / no response


Add font selection?

It would be ideal to have a font selection option in the preferences.
Also what is the Unicode compatibility on Unicode complaint systems?

As you can see, right now ssheven only uses Monaco; I believe it is the only monospace font that is available for sure on every Mac running 7/8/9.
Font detection/selection and a new prefereces field is probably not too hard to implement, but not a priority to me, so it will be a while before I can address it.


Request for official 1.2 release with dedup

I've found the dedup capability pretty essential for practical work.
Though I've built my own jar, I think it's pretty intimidating for the average potential user wanting RDF out of spreadsheets, so I would advocate for a formal 1.2 release.

v1.2 was finally released today.


Improved end-of-file handling in LIS Bratseth scheme

Description
Added graceful handing of unexpected End-Of-File in sfcobs and preobs files used by LIS Bratseth scheme.  When encountered, LIS will stop trying to read the file in question, put a warning in the lislog file, and write an alert file.
Also modified code to skip unnecessary repeat of LIS precip analysis 15 minutes after start of LIS run.  Not only does this save time, it avoids redundant warnings and alerts for EOF cases.

Actually, hold on.  I need to check LIS behavior when started at 0600Z or 1800Z.

I believe this is ready.


Failed to import - domhandler

Failing module

GitHub: https://github.com/cheeriojs/cheerio, https://github.com/fb55/domhandler
npm: https://www.npmjs.com/package/cheerio, https://www.npmjs.com/package/domhandler

import juice from<EMAIL_ADDRESS>juice.inlineContent("", "");

Error message
After execution I got this:
cheerio.js:2 Uncaught TypeError: Br.Document is not a constructor
    at Object.Ht [as default] (cheerio.js:2:5249)
    at Object.ot [as load] (cheerio.js:4:1748)
    at cheerio.js:4:2287
    at cheerio.js:2:1161
    at cheerio.js:4:2416

Additional info
In my thought above Br.Document should be resolved, but for some reason Br became default exported class member, other exported member was lost.

esm.sh version: 64
Browser version: Windows Google Chrome 97.0.4692.99 (Official Build) (64-bit)

thanks, i will look into it

fixed in v65


Report

create a acc.txt file in which give your username and pass is this manner "username:password"

pls report my fake account...its spreading a bad word about me @chathure_deepak


add simstore table access via slice

Today, I got annoyed today that I could not do
steps = storage.steps[:100] in some test code using simstore.
This adds handling of slices in the __getitem__ logic.
It behaves as a list would do (so an empty list on an empty slice, a list with a single item for slices like [4:5], a single item with int and a TypeError if it is not an int or slice)
It should also leverage batched loading, if I understood the code correctly
One assumption that I added is that the name of objects can only be strings (for _name_to_uuid), I don't know if this is currently an assumption/requirement, but all tests seem to pass on this.
This code is python > .3.6 (f strings) and the tests are python > 3.7 (leverages dict order)

Thanks -- I've also noticed this as a minor annoyance (usually I'm too busy with whatever I'm working on and just use list(storage.steps)[start:end], because hacks like that are obvious to me -- that kind of hack is often NOT obvious to our users, and we shouldn't expect them to know it -- so this is a very useful improvement.)

Yeah, that would be a solution if I actually could load all the steps (100_000) on my local machine in a reasonable time, I can't :laughing:
My hack around was to write something like
stop = 100:
steps = []
for i, e in storage.steps:
    steps.append(e)
    if i > stop:
        break

Which was not great xD
With d1c8609, I actually test the correct code path. I also tested that this works (and hits the code) on the "Simstore and CLI" minitutorial.

@dwhswenson please have another look, thanks for catching the wrong code!

also, I would like to know if:

One assumption that I added is that the name of objects can only be strings (for _name_to_uuid), I don't know if this is currently an assumption/requirement, but all tests seem to pass on this.

Is a reasonable assumption to enforce

One assumption that I added is that the name of objects can only be strings (for _name_to_uuid), I don't know if this is currently an assumption/requirement, but all tests seem to pass on this.

I think this should be the case, although it looks like SimStore isn't raising an error if you try to save an object with a non-string name. The StorableNamedObject.named method allows non-string names. As long as the name attribute is something that SimStore can turn into a JSON string, it will be saved in SimStore. (netcdfplus does catch this error on saving, because it doesn't treat the name attribute as part of the JSON that is generated.)
PR coming to make this explicitly required.


Rename NOC_I_5_NoiseWalk.pde to NOC_I_6_NoiseWalk.pde

When going through the introduction examples I got an error when opening this file: "The file NOC_I_5_NoiseWalker.pde needs to be inside a sketch folder named NOC_I_5_NoiseWalker." The file or the folder should be renamed I think.

Thank you for this!


Error in 'az ad sp update --set appRoleAssignmentRequired=true'

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ad sp update
Errors:
The command failed with an unexpected error. Here is the traceback:
'GraphClient' object has no attribute 'service_principals'
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 718, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/role/commands.py", line 54, in graph_err_handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 240, in handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 452, in cached_put
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 446, in _put_operation
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/role/custom.py", line 988, in patch_service_principal
AttributeError: 'GraphClient' object has no attribute 'service_principals'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az ad sp update --id $app.appId --set appRoleAssignmentRequired=true

Expected Behavior
Environment Summary
Windows-10-10.0.22000-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0

Extensions:
ad 0.1.0
azure-devops 0.25.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

@jiasli for awareness

Duplicate of #22777


Issue on Robotium Calculator Test Sample

From<EMAIL_ADDRESS>on January 28, 2013 01:05:40
Hi Guys,
I just read Robotium today and tried to execute the sample TestAPKProject. I'm always getting an error when running the script. Please advise what I missed. I already read some of the issue regarding this but didn't saw any answer.
Test Project: https://code.google.com/p/robotium/wiki/RobotiumTutorials/TestAPKProject Console Logs:
[2013-01-28 16:56:33 - TestProject] ------------------------------
[2013-01-28 16:56:33 - TestProject] Android Launch!
[2013-01-28 16:56:33 - TestProject] adb is running normally.
[2013-01-28 16:56:33 - TestProject] Performing android.test.InstrumentationTestRunner JUnit launch
[2013-01-28 16:56:33 - TestProject] Automatic Target Mode: using device 'HT11WT217015'
[2013-01-28 16:56:33 - TestProject] Uploading TestProject.apk onto device 'HT11WT217015'
[2013-01-28 16:56:33 - TestProject] Installing TestProject.apk...
[2013-01-28 16:56:35 - TestProject] Success!
[2013-01-28 16:56:35 - TestProject] Launching instrumentation android.test.InstrumentationTestRunner on HT11WT217015
[2013-01-28 16:56:36 - TestProject] Test run failed: Instrumentation run failed due to 'Process crashed.'
Please see attached files.
Thanks,
Robert
Attachment: TestApk.java logcat.log
Original issue: http://code.google.com/p/robotium/issues/detail?id=384

From<EMAIL_ADDRESS>on January 28, 2013 02:25:51
you are on emulator ?

From<EMAIL_ADDRESS>on January 28, 2013 03:02:11
I'm directly connected to a device.

From<EMAIL_ADDRESS>on January 28, 2013 03:19:16
Robert, I've saw your .java, probably you made some changes in code, not sure it is the reason of crash, can you please run the code without any changes ?
Can you share your environment details ?

From<EMAIL_ADDRESS>on January 28, 2013 03:59:47
Yes, I did some changes to try to make it work. I had the same issue with
the original script. I'm running it on windows 7. What environment details
you need? I really appreciate your time and effort.

From<EMAIL_ADDRESS>on January 28, 2013 04:16:28

Please try to run original script
java-version, device, android sdk version etc....

From<EMAIL_ADDRESS>on January 28, 2013 04:51:32
I just tried the original script and still have the same issue.
Using java 1.6, Android 2.3.3, robotium 3.4.1, device=htc inspire

From<EMAIL_ADDRESS>on January 28, 2013 22:18:30
What issue have you experienced with the original script?

From<EMAIL_ADDRESS>on January 28, 2013 23:27:41
It seems no issue, can you please re-run ensuring followings,

Clear app data from settings>applications>....
Make sure AUT calculator app is properly installed on device, before running test project. ?

let me know about outcomes,

From<EMAIL_ADDRESS>on February 04, 2013 01:55:52
Will open if new information is given.
Status: Invalid
Owner<EMAIL_ADDRESS>


Mesh Placement Behavior in ifcLoader and Manual Mesh Creation

Describe the bug 📝
Hello,
I wanted to ask about a behavior I’ve observed when working with meshes using the library. So far, I have been creating my meshes via ifcLoader.load, and everything has been working as expected. However, today, I conducted an experiment and manually created a mesh using a method from a sibling repository, as demonstrated in this example: web-ifc-three.ts#L26.
The issue I noticed is that the meshes generated through these two approaches do not appear in the same positions within my scene. To ensure consistency, I’ve set COORDINATE_TO_ORIGIN to true in both scenarios. Additionally, for ifcLoader.load, I pass the coordinate parameter as false. Despite these settings, the placement discrepancy persists.
Note that when COORDINATE_TO_ORIGIN set the false on both, they appear exactly same on same location as expected.
Since the precise positioning of the models is critical for my use case, I would like to understand what might be causing this difference. Are there additional factors or settings I might be overlooking that could impact mesh placement?
I greatly appreciate your support and insights on this matter.
Thank you in advance!
Best regards,
Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
System:
    OS: macOS 14.7.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 175.95 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v18.19.0/bin/npm
  Browsers:
    Chrome: 131.0.6778.86
    Edge: 131.0.2903.70
    Firefox: 132.0.2
    Safari: 17.6

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

I wanted to share some further observations to aid in the investigation. I noticed that the coordination matrices obtained from fragmentsGroup and directly from web-ifc are not matching. However, when these matrices are applied to the corresponding 3D objects (meshes), the objects are brought to the exact same location in the scene.
This suggests that there might be a discrepancy in the mesh creation process, which is somehow compensated for in the coordinationMatrix. I couldn’t identify any code in the repository that explicitly handles this adjustment, which leaves me at a bit of a loss in terms of where to focus my investigation.
From web-ifc >

1   0   0   0
0   1   0   0
0   0   1   0
48.8318280384837   0.1524   19.4187064561144   1

From fragmentsGroup.coordinationMatrix >

1   0   0   0
0   1   0   0
0   0   1   0
-2.215953884857178   -2.076200008392334   27.88630140649414   1

Here is my ifc file if you would like to try out yourself. https://drive.google.com/file/d/1kXqb-5_7z05Trn655KQG7WmQBNoAH94E/view?usp=sharing
I’d really appreciate any insights or guidance on this topic.
Thank you!

I might have an idea about what’s happening here. Could it be that the coordination matrix depends on how the IFC model is traversed? For example, using StreamAllMeshes vs. StreamAllMeshesWithTypes might result in different coordination matrices. However, applying the matrix to the object still places it in the correct location. Could you please confirm if this is the case?
Also, perhaps I should tag @beachtom, as I believe he might be able to provide valuable input on this matter.

So _coordinationMatrix is only used when coordinating to Origin - and yes it could depend on the order of the objects - the matrix is generated based on the first object that is found that needs coordinating - then all others are done related to that object - so you if you change the order of the objects then yes the matrix will change

Thanks @beachtom!


Is this project still maintained?

What happened?
I still use this package and still running on prod now, but I'm now a little worried that the project might be unmaintained. last PR over 7 months ago. and no new release for more than one year.
this is a cool project I hope this project still continue

Contribute please.


Redirect for https://mi.docs.wso2.com/en/latest/install-and-setup/install/installing-mi-dashboard page not working

Description
$subject
Steps to reproduce

The steps to be followed to reproduce the issue.

Affected version(s)

The versions that are affected by the issue.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Closing as fixed.


Please add News subscription

Hi there :)
I'm guessing this is a duplicate of one of these:
#869, #3774, #5249, #5406
If not, could you please elaborate?

There's also an existing RSS feed of the News section that can be subscribed to: https://caniuse.com/feed/
Closing this issue for now, will re-open if more info is provided.


Create index.md

Created new index page

closing here, this should be in the fork -- sorted it out last night!


nix: fix closure bloat on nix

The conditional preventing closure bloat unfortunately didn't apply for
the nix attribute, which is at 2.3.10 (not 2.4.*, what this did check
for).
Motivation for this change
Don't pull in x86 binaries when cross-compiling a whole NixOS.
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] 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.

Note nixUnstable currently doesn't cross-compile either. There seem to be some issues with the recent markdown additions.
However, I see this orthogonal to that PR.


Extend the db-to-pb profile code to include selectors

Summary
Extends the MergeDatabaseGetIntoProfiles and MergeDatabaseListIntoProfiles
functions to include selectors. These will be useful later when we extend the
profile handlers.

Extend the ProfileRow interface for selectors
Add selectors to profile in MergeDatabaseListIntoProfiles
MergeDatabaseGetIntoProfiles includes selectors

Related: #3723
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
as part of a larger branch. We'll be able to add tests when we extend the Profile service
and extend the handlers.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.095% (-0.001%) from 53.096%
when pulling b43d38bc1f97430ed641bd94c8bdebff0c678e16 on jhrozek:selectors_handlers
into 9a2ccaae156c3477620fe3d018baa6b1d477385e on stacklok:main.


[Issue-2025] Sorting the token list to buy

Related issue(s)

#2025

Is your feature request related to a problem(s)? Please describe.

Fetch data online

Describe the solution you'd like

Fetch data online

Describe alternatives you've considered

No

Additional context

No

🚀 Deployed on https://pr-2083--sw-web-runner.netlify.app


Add Pull Request Badge app

Hello 👋
I've noticed that wildfly is heavily leveraging the redhat issue tracker and most pull requests add a link to the related issue. You might be interested in the GitHub App I wrote to automate this process https://pullrequestbadge.com.
If a pull request title or the branch name starts with an issue prefix e.g. WFLY-123, the Pull Request Badge GitHub App does automatically insert a badge to the pull request descriptions based on the config provided in this pull request.
Pull Request Badge is always free for public repositories. If you have any questions please let me know.
Setup steps

Go to the GitHub Marketplace listing
Choose the free plan and follow the instructions.
Merge this pull request 😉

Obviously, please feel free to close this pull request if you're not interested in using the app.

Hello, stefanbuck. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

This is ok to test

Thanks for pointing this out to us! At this point I don't think this is a great fit for our project, as there are benefits to having the links in the PR description, plus our overall environment is complex enough that we need a large benefit to add more element.s But we'll keep this in mind for the future.


Still have multiple definitions when including Stan headers in several source files

Summary:
There are many linker errors when trying to build a shared object out of compiled Stan programs, as in R packages that use the rstanarm build process, which currently glues all the C++ files together before compiling to avoid this problem. This was only partially fixed in #311 .
Description:
There are many linker errors when trying to build a shared object out of compiled Stan programs, as in R packages that use the rstanarm build process, which currently glues all the C++ files together before compiling to avoid this problem. This was only partially fixed in #311 .
Reproducible Steps:
Try to build rstanarm without this workaround.
Current Output:
linker_errors.txt
Expected Output:
Successful package build
Additional Information:
Current Version:
v2.12.0

@bgoodri, can you spell out instructions on how to reproduce? Bob and I are going to talk about this tomorrow. (It takes me a while figuring out what I need and how to call it, so if you have instructions, that would be really useful.)

https://github.com/stan-dev/stan/issues/1149#issuecomment-192535899

@bgoodri, I verified this issue. It's not in math anymore. It's in Stan and RStan. I'll create new issues there.


Unable to read key/secret from AWS S3 instance profiles

Laravel Version: v5.4.19
PHP Version: 7.1

Description:
My S3 config looks like this:
        's3' => [
            'driver' => 's3',
            // 'key'    => null, // provided by instance profile
            // 'secret' => null, // provided by instance profile
            'region' => env('S3_REGION'),
            'bucket' => env('S3_BUCKET'),
        ],

I verified that region and bucket are correct. "league/flysystem-aws-s3-v3": "^1.0" is installed. However, I get this error when trying to access S3 (upload a file):
ErrorException in FilesystemManager.php line 207:
Undefined index: key

Reading https://github.com/laravel/framework/pull/9558 I thought Laravel can get key/secret from the instance profile. Am I doing it wrong or is there a bug?

You can't comment the config keys, they must exist, you can use environment variable to set those keys though.


[All] Removed METAPOD dependency

Cmake was still looking for metapod. Apparently the dependency should have been removed with pull request #490, but the removal was not complete.

I've already fixed this issue in the future release. I will close this PR.
Anyway, thank you for the contribution.


Fix argument bug in networks.go

noticed this when i rebased, sorry

Thank you! I still haven't had time to open this in my editor and fully check it, but I will soon!


Front page articles with initial seeding

Now it hopefully passes the critical eye of the reviewer. And adds also video. :]


Doesn't seem to break Copilot

Hi,
i think Luasnip is breaking Copilot after the first expansion. Quick example i'd reproduce with Go:

blank main.go
package main
start typing func  copilot will suggest a whole main function -> tab to expand
go above new main func
start typing type -> normally Copilot would suggest type Person struct { ... when Luasnip is installed, it doesn't.
Copilot seems to stop working.

Regards

Phuhh, I have no idea how luasnip might break copilot... Maybe open an issue on the plugins github, they might have more ideas how to troubleshoot this.

Hm,
one instance it also broke for me was when expanding via tab (mapped in nvim-cmp). It then literally returned the snippet and not the pre-filled (?) snippet copilot send. Not sure how the internals work ofc. Was just something i wanted to note XD.
Yeah, at first i thought it's some setting, but i removed all luasnip related settings from my config and it still broke. Only after uninstalling Luasnip it worked again.
Regards

i figured out it also breaks using vsnip. must be indeed a problem with the copilot plugin i guess.


Bibtex Label Generation fails on titles with " character

This line causes citation entries whose title has a " character to crash. You can verify this by running the following in your console and observing the error:
var str = '"Bugs": a never ending story';
str.match(/^(?:(?:the|a|an)\s+)?([^@{}"=,\\\s]+)/i)[1]

Fair enough lol, didn't think of that. Something like this then?
str.split(/\W+/).find(word => word.length && !['the', 'a', 'an'].includes(word))

Probably a lot more readable too.

(Apologies - just realized my original link was broken - fixed now.)
Thanks so much for the quick response. That solution does feel much more readable and would certainly solve my use case. 👍


Dropdown menu in kanban is not well-rendered

Info:

OS: MacOS

Logseq ver: 0.8.9

Plugin ver: 1.3.8

Theme name: none

[x] ⚠ Do i have issue with DISABLED my custom.css?

Description:
If a block is searched within a kanban board, the dropdown menu is cut.
To Reproduce:
Create a kanban template and search for a block with [[...]]
Expected behavior:
The dropdown menu is drawn on top of everything else and it is not cut.
Maybe a higher z-index would fix?
Screenshots

fixed


Add logic to Spider

The Spider should spider the website as normal. The Spider should provide the same configuration options as spidr. All HTML pages should be converted to Page classes and outputted. All other files should be outputted as static content.

Although, need some way of identifying blog posts via a path prefix or regexp, and mapping those to a custom output path.


import pyabsa hangs when running on docker

Description
When importing pyabsa running on a docker, the execution hangs.
Debugging
The code hangs in pyabsa/utils/file_utils.py:312
Probably due to a third-party package called findfile which searches for a local version but never times out.
Setup

PyABSA 1.9.6
Docker version 20.10.8, build 3967b7d
Python 3.9

Files to reproduce
Dockerfile
FROM python:3.9-slim-buster

COPY test.py .

RUN apt-get update && apt-get -y install git
RUN pip install pyabsa==1.9.5

CMD ["python test.py"]

test.py
import pyabsa

pyabsa.check_dataset()

You may try
FROM python:3.9-slim-buster

COPY test.py .

RUN apt-get update && apt-get -y install git
RUN pip install findfile==1.7.7
RUN pip install pyabsa==1.9.5

CMD ["python test.py"]

which uses the updated version of findfile.

Thank you for your response @yangheng95 !
We have managed to resolve this issue by setting the WORKDIR of the dockerfile to something other than the root path as I wrote in the issue.
cwd is not root in runtime, and the code doesn't hang, so it's good enough for me.


dev_as_references.json is from V1?

It seems the dev_as_references.json is for the V1? Do you have the file from V2?

there is no similair item for V2


Some browsers do not support  tag

I have some books which contain xml tags specified like this:
<?xml version="1.1"?>

At the present, I'm getting around this by patching the code to replace "1.1" with "1.0".  I think eventually we'll deal with this at the time we acquire the books from the publishers, either by asking them to package them with strictly "1.0", or by replacing the version number before we process the books and put them online.
So, I'm not sure whether you want to patch readium to make this change, or leave it as an issue for content providers.  If you're leaving it to content providers, you may want to trap the error and log it to the console, so that users will better understand what is going on.  I think that, without some sort of patch, the code simply fails without any diagnostics.

We ran into this issue too, specifically with Firefox, which was not loading certain books.
We ran the EpubCheck validator on our collection, which returned this error for the books in question (file info snipped):
ERROR(HTM-001): ... : Any publication resource that is an XML-based media type must be a valid XML 1.0 document. XML version found: 1.1.
In our case the books were EPUB version 2.  According to OPF 2.0 spec: "An XML Document is a complete and valid XML document as defined in XML 1.0 (Fourth Edition) (http://www.w3.org/TR/2006/REC-xml-20060816/)."
We didn't have the option of going back to the vendor to have the EPUBs corrected, so we did it ourselves.  After clearing this error the books loaded.
I've asked the department that does the outsourcing for the books that going forward they require vendor delivered EPUBs to pass EpubCheck without errors before we declare them acceptable.
When I was debugging, I did see console errors that hinted at the problem.  Shortly before all console messages stopped, Firefox reported "XML declaration not well-formed" for what I believe was the OPF file.  I agree Readium could enhance this error message.  In fact, it seemed to fail to process the exception.  The final console error was "TypeError: e is undefined" in a file I can't identify because I am looking at a screenshot of the console output, but it is definitely a readium file.  Note that we are using a Sep 2, 2015 version of master, which is far behind HEAD now.

What I ended up doing was patching the zipReader -- at the point where the file contents have been extracted from the zip file, replace any 1.1 declarations with 1.0 declarations.  We will be asking our publishers to send us files with the declaration as 1.0; but a number of my test files were using 1.1 and this was the quickest way to get past this particular issue.  If you're interested, I can post the code that I modified.

Yes I would like to see the code, just to learn more about Readium.  We don't actually need it, though, because we fixed the declarations in our EPUBs.  Maybe this is an option for you as well?  That way you won't need to deal with patches that would be overwritten or even possibly invalidated when updating Readium from upstream.
It turned out to be very easy.  First unzip, then edit, then re-package.  Here's what I wrote in our internal wiki about re-packaging:

Zip 3.0 by Info-ZIP is available on Mac OS X on the command-line.
Following instructions from Epub Format Construction Guide - HXA7241 - 2007:
    zip -X0 EpubGuide-hxa7241.epub mimetype
    zip -Xur9D EpubGuide-hxa7241.epub *

The flags being used (see http://www.info-zip.org/mans/zip.html):

-9: maximum compression

-D | --no-dir-entries: do not create entries in the zip archive for directories.

-u | --update: replace (update) an existing entry in the zip archive if it had been modified more recently.

-r | --recurse-paths: travel the directory structure recursively.

-X | --no-extra: do not save extra file attributes.

We tested the correctness of this method in various ways:

Round-trip zipping and unzipping an exploded EPUB from our website and checking that files/directories are binary identical.

Opening the resulting EPUB file in Adobe Digital Editions and testing page turning, font size change, TOC, bookmarking, and full-screen mode.

Validating EPUB file using [epubcheck](https://github.com/IDPF/epubcheck).  No errors were introduced by the zipping process.

So that's an option you might want to consider.
Please do feel free to post the code though, as I would be curious to see it.

Thank you for this bug report. I am able to reproduce on Windows 10 with Edge, Internet Explorer, Firefox (only Chrome works with version="1.1" in package.opf).

Fixed in the feature/DOMParser branch(es), here are the pull requests (all ReadiumJS repositories are affected):
https://github.com/readium/readium-cfi-js/pull/45
https://github.com/readium/readium-shared-js/pull/252
https://github.com/readium/readium-js/pull/134
https://github.com/readium/readium-js-viewer/pull/483

Live demonstration of the XML v1.1 fix:
http://readium-html.surge.sh/?epub=https%3A%2F%2Fcdn.rawgit.com%2Freadium%2Freadium-js-viewer%2Ffeature%2FDOMParser%2Fepub_content%2Faccessible_epub_3&goto={"idref"%3A"id-id2442754"}
OPF package:
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/package.opf#L1
EPUB3 Navigation Document (TOC):
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/bk01-toc.xhtml#L1
EPUB3 XHTML Content Document:
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/index.xhtml#L1

Do you need me to verify the fix, or are you just publishing the test cases in case anyone is interested?
From: Daniel Weck<EMAIL_ADDRESS>Sent: Monday, February 08, 2016 2:38 PM
To: readium/readium-js-viewer<EMAIL_ADDRESS>Cc: Robert Hanson<EMAIL_ADDRESS>Subject: Re: [readium-js-viewer] Some browsers do not support  tag (#467)
Live demonstration of the XML v1.1 fix:
http://readium-html.surge.sh/?epub=https%3A%2F%2Fcdn.rawgit.com%2Freadium%2Freadium-js-viewer%2Ffeature%2FDOMParser%2Fepub_content%2Faccessible_epub_3&goto={"idref"%3A"id-id2442754"}
OPF package:
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/package.opf#L1
EPUB3 Navigation Document (TOC):
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/bk01-toc.xhtml#L1
EPUB3 XHTML Content Documents:
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/index.xhtml#L1
https://github.com/readium/readium-js-viewer/blob/feature/DOMParser/epub_content/accessible_epub_3/EPUB/ch01.xhtml#L1
—
Reply to this email directly or view it on GitHubhttps://github.com/readium/readium-js-viewer/issues/467#issuecomment-181524020.

I would appreciate if you could test the "live demo" link in your browsers, thanks! :)
Make sure to open the TOC to see if it all works fine there too.

We just ran into this same issue. Is the plan to merge this as a permanent work around or should I fix it on our own readium branch?

The feature/DOMParser branches (see comment above:  https://github.com/readium/readium-js-viewer/issues/467#issuecomment-180095555 ) implement support for non-XML HTML too, so maybe you only need the XML 1.1 fix?
At any rate, I personally wouldn't mind seeing this merged to the develop branch, but as this was originally implemented to demonstrate the feasibility of EPUB3.1 with relaxed XML serialisation rules (which hasn't happened), I understand why there isn't a strong case to introduce (potentially) disruptive changes to an already complex codebase.
If there is strong evidence that the XML1.1 fix is needed (as now seems to be the case), perhaps we should consider extracting the fix in its own PR? (I have to take a look at the code though...it's been a while)

PS: the XML1.1 fix basically boils down to XmlParse.preprocess()
https://github.com/readium/readium-cfi-js/pull/45/files#diff-9909b258b32fb35ba81727d9da6faaceR34

We have tracked down that our problem book slipped through very early before we forced everything through EPUB check. I'll just go ahead and implement a 1.1 fix in our branch.
The issue is always "it works in iBooks", so failing EPUB check does not mean a whole lot to the authors it seems.

@matwood could you please let us know where in your fork's code you patched the XML 1.1 issue? (I am asking because XmlParse.preprocess() is specific to the feature/DOMParser branch ... I remember having to extract and centralize this code in order to fix all occurrences of XML parsing, e.g. spine item HTML documents, navdoc, etc.)

@danielweck Here is the fix I put in place on BiblioLabs fork.
https://github.com/bibliolabs/readium-js/commit/b5b765b2026f7449cf678d20ce23e59d5f3e2154
I added some better logging since cross browser error handling is hard with the parse function. If you want I can cherry pick it into the readium branch.


Updating the cfml.tmLanguage file with the last version by jcberquist

Updating the cfml.tmLanguage file with the last version by jcberquist before he switch to using the sublime-syntax type.

Thanks a lot!


master maven build failure

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:03 min
[INFO] Finished at: 2017-04-07T10:29:37+02:00
[INFO] Final Memory: 174M/1143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java (install-agent-module) on project hawkular-wildfly-agent-example-jndi: An exception occured while executing the Java class. null: InvocationTargetException: wildflyHome = /home/extanb/Documents/adnovum/IdeaProjects/hawkular-agent/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-example-jndi/../../../hawkular/dist/target/hawkular-1.0.0.Alpha8/hawkular-1.0.0.Alpha8 is not readable and existing directory -> [Help 1]
Its looking for a project "hawkular" which is not in git. The only checkouts I have are "hawkular-apm" and "hawkular-metrics". A hawkular Alpha version would not be acceptable in production. What should I do ?

This is using profile "dev"

Switched off "dev", had problems with "Example Custom Agent"(ECA) when building from parent, but ECA built OK on its own and then parent build could proceed

@maccloud42 note that the the Hawkular WildFly Agent and Hawkualr Java Agent use JIRA for bug reports: https://issues.jboss.org/projects/HWKAGENT/issues


move everything to the CLD2 namespace, update gemspec

Move everything to the CLD2 namespace. Update the gemspec. Remove original forks specific things like build status.
/cc @jcheatham @grosser
Risks

None.

why can our stuff not be merged into the original ?
would it make sense to keep the namespace to be able to rebase more easily ?

The authors of the original were unresponsive for ~8 months.  We are continually seeing tickets about incorrect language detection, so I was hoping we could get this going so it is easier to maintain/expand.
As far as the namespacing, we could keep the original.  I changed it because it makes more sense to me and is then not ambiguous about what is coming from where.  That was mostly just my personal preference.

Did you try reaching out to the cld2 owners ?
On Wed, Aug 19, 2015 at 1:57 PM, Craig Day<EMAIL_ADDRESS>wrote:

The authors of the original were unresponsive for ~8 months. We are
continually seeing tickets about incorrect language detection, so I was
hoping we could get this going so it is easier to maintain/expand.
As far as the namespacing, we could keep the original. I changed it
because it makes more sense to me and is then not ambiguous about what is
coming from where. That was mostly just my personal preference.
—
Reply to this email directly or view it on GitHub
https://github.com/zendesk/cld2/pull/1#issuecomment-132781405.

sent an email to the cld and cld2 owners ...
On Wed, Aug 19, 2015 at 2:00 PM, Michael Grosser<EMAIL_ADDRESS>wrote:

Did you try reaching out to the cld2 owners ?
On Wed, Aug 19, 2015 at 1:57 PM, Craig Day<EMAIL_ADDRESS>wrote:

The authors of the original were unresponsive for ~8 months. We are
continually seeing tickets about incorrect language detection, so I was
hoping we could get this going so it is easier to maintain/expand.
As far as the namespacing, we could keep the original. I changed it
because it makes more sense to me and is then not ambiguous about what is
coming from where. That was mostly just my personal preference.
—
Reply to this email directly or view it on GitHub
https://github.com/zendesk/cld2/pull/1#issuecomment-132781405.

I pinged them a few times on the PR I originally made
https://github.com/BanjoInc/cld2/pull/1
I also sent an email to the owners in the gemspec, no response.  Maybe I'll
send another one.
On Wed, Aug 19, 2015 at 2:00 PM, Michael Grosser<EMAIL_ADDRESS>wrote:

Did you try reaching out to the cld2 owners ?
On Wed, Aug 19, 2015 at 1:57 PM, Craig Day<EMAIL_ADDRESS>wrote:

The authors of the original were unresponsive for ~8 months. We are
continually seeing tickets about incorrect language detection, so I was
hoping we could get this going so it is easier to maintain/expand.
As far as the namespacing, we could keep the original. I changed it
because it makes more sense to me and is then not ambiguous about what is
coming from where. That was mostly just my personal preference.
—
Reply to this email directly or view it on GitHub
https://github.com/zendesk/cld2/pull/1#issuecomment-132781405.

—
Reply to this email directly or view it on GitHub
https://github.com/zendesk/cld2/pull/1#issuecomment-132782120.

--
Craig Day
Sustaining Engineer
Zendesk http://zendesk.com
Skype: zendesk.cday

Oh... you beat me to it. I guess I won't send them another one.

if that does not work out, I'd still prefer to keep the namespace/code as close as possible and go with cld3 or something like that :D


BUG: menu item fires onTouchTap if diabled

Problem description
When clicking a menu item that is disabled onTouchTap is fired anyways.
 alert("what")} />
Versions

Material-UI: 0.18.X (latest)
React: 15.5
Browser: chrome latest

Duplicate of #7471.

yes, it seems i created the item twice. i could not find it so i thought i forgot to submit it :D

:)


Missing v0.5.1 tag for alibi-explainer

The latest release has a default image version of  v0.5.1 for alibi-explainer. That tag doesn't seem to exist yet: https://console.cloud.google.com/gcr/images/kfserving/GLOBAL/alibi-explainer?gcrImageListsize=30

hmm looks like the build for some reason failed
https://console.cloud.google.com/cloud-build/builds;region=global/04ddc7db-24af-474f-8f65-1eb1bcee4c99?authuser=1&project=kfserving

it actually timed out possibly related to https://github.com/kubeflow/kfserving/pull/1395


Update Data Manipulation code

Update Data Manipulation code.

Resolves https://github.com/VolkovLabs/volkovlabs-form-panel/issues/211


Bug/#745bis

The map center after the double-tap zoom-in animation now matches the end of the animation.

It seems to me there is still a little shift at the end of the animation. Could this be a rounding problem? Otherwise it is much better than before.

I saw that little shift too. May be a rounding problem. I'd need to understand more about View animation in order to try to fix it.

@monsieurtanuki is this ready to merge?

I think this should not be merged until the shift-issue is resolved. Not sure what causes the shift though.

Sometimes there is still a tiny little shift, but it is much better than before and doesn't always occur.
I think the remaining issue is neglectable for now and thus the issue can be closed. Maybe in the future that issue could be fully resolved, but I don't know how. It is interesting though, that the issue didn't occur in previous versions of osmdroid.


Disable on Dev

What would be the best way to disable this on dev (or only use it on prod)? Would it make sense to add a config variable for this?

The better approach would be to check allowed environments in: https://github.com/webbingbrasil/filament-2fa/blob/6ad5f82daad92d161c974c592532a4902bdfa504/src/FilamentTwoFactor.php#L39
That way we just skip the challenge step and everything else would continue working normally, I think a configuration property with allowed environments would be great.
would you like to do a PR?


Communicate "Migration Done!" when it wasn't done - from your docs

If you provide wrong path to the file, you get an error, but anyways runMigration resolve the promise successfully, and you get an info, that everything went fine...
{ Error: Cannot find module './migrations/add-dog-ct'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:20:18)
at run (/Users/oskarkaminski/Documents/projects/ace-website/node_modules/contentful-migration/built/bin/cli.js:40:29)
at Object. (/Users/oskarkaminski/Documents/projects/ace-website/db/runMigrations.js:10:1)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:279:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:752:3) code: 'MODULE_NOT_FOUND' }
Migration Done!

This issue had no activity for some time now, please feel free to create a new one if you still have the issue


Hybrid Connectors - Does not handle the data of ipv6 Client

When my ipv6 client send data to my connectors, this one timeout and in my log, i have the next message : 'connection is timeout without communication, the remote ip is ... && port is ...'

Me too! Pls fix this issue!

i see, ipv6 support ～_～

so far, dose pomelo support ipv6?

Facing the same issue.
[2020-04-06 12:40:42.227] [WARN] pomelo - [/home/info/slots_gameserver/node_modules/pomelo/lib/connectors/hybrid/switcher.js] connection is timeout without communication, the remote ip is ::ffff:<IP_ADDRESS> && port is 23868

Facing the same issue.
[2020-04-06 12:40:42.227] [WARN] pomelo - [/home/info/slots_gameserver/node_modules/pomelo/lib/connectors/hybrid/switcher.js] connection is timeout without communication, the remote ip is ::ffff:<IP_ADDRESS> && port is 23868

I had resolved this issue. you can add my wechat: liuweichang9000

Facing the same issue.
[2020-04-06 12:40:42.227] [WARN] pomelo - [/home/info/slots_gameserver/node_modules/pomelo/lib/connectors/hybrid/switcher.js] connection is timeout without communication, the remote ip is ::ffff:<IP_ADDRESS> && port is 23868

I had resolved this issue. you can add my wechat: liuweichang9000

If its possible will you let us know over here. As it will help others also in the community.


License ?

Hello, under what license is this project released under ? I would like to study it to learn from it. It looks to be pretty awesome. Thank you.

I've added the MIT license. Thanks for pointing out the lack of license!