wiby clean command

At the moment, wiby test creates a branch called wiby-[dep name] in the dependent repos. There is nothing to clean this up - running a new wiby test will fail if the branch already exists.
wiby test should not fail on existing branch - but that is a separate, larger problem (I'll create a separate issue), but in the meantime - deleting the wiby-wiby branch manually on wiby-test/* repos is a hassle during development.
wiby clean should take the following options:

--all - remove all wiby-* branches (by default only remove the current branch, based on the naming as proposed in #78)
--dry-run - show the branches that would be removed

alternative: do the dry-run by default and ask the user to confirm the action? With an optional --force to skip the confirmation?
bonus points: what if the branches contain commits other than ones made by wiby?

I"ll have a look at this if you are not already doing so?

I'm almost done with this.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Json cleanup

This PR is intended to have minimal behavioral change.  It renames the existing isObject member function of Json::Value to isObjectorNull since this is what that member function actually checks.  Then it adds a new isObject that only checks if the value has object type, and changes as many isObjectorNull back to isObject as possible.  Ditto for isArray.
Reviewers should concentrate on the 3rd commit ensuring that no change from isXxxorNull back to isXxx is incorrect, and that no opportunities to do so have been missed.
The rationale is that it makes the code easier to read because it was very easy to forget that isObject answers to true to a null value.
As the 3rd commit touches many parts of rippled, please feel free to suggest other reviewers, and limit yourself to just those parts of rippled you feel comfortable (or are interested in) reviewing.  Thanks.

Jenkins Build Summary
Built from this commit
Built at 20180208 - 00:51:32
Test Results

Build Type
Result
Status

coverage
1000 cases, 0 failed, t: 575s
PASS :white_check_mark:

clang.debug.unity
1000 cases, 0 failed, t: 449s
PASS :white_check_mark:

gcc.debug.unity
1000 cases, 0 failed, t: 395s
PASS :white_check_mark:

clang.debug.nounity
998 cases, 0 failed, t: 838s
PASS :white_check_mark:

gcc.debug.nounity
998 cases, 0 failed, t: 780s
PASS :white_check_mark:

clang.release.unity
999 cases, 0 failed, t: 476s
PASS :white_check_mark:

gcc.release.unity
999 cases, 0 failed, t: 514s
PASS :white_check_mark:

cherry-picked https://github.com/scottschurr/rippled/commit/ac351ce6d8fccf43462dbc182cde6a9a22721a3c

Rebased to 0.90.0-rc2.

Rebased to 0.90.0-rc3.

Codecov Report

Merging #2377 into develop will decrease coverage by 0.02%.
The diff coverage is 90%.

@@             Coverage Diff             @@
##           develop    #2377      +/-   ##
===========================================
- Coverage     70.3%   70.27%   -0.03%
===========================================
  Files          703      703
  Lines        53671    53375     -296
===========================================
- Hits         37733    37510     -223
+ Misses       15938    15865      -73

Impacted Files
Coverage Δ

src/ripple/json/json_value.h
93.93% <ø> (ø)
:arrow_up:

src/ripple/rpc/handlers/Subscribe.cpp
92.63% <100%> (ø)
:arrow_up:

src/ripple/rpc/handlers/GatewayBalances.cpp
85.71% <100%> (ø)
:arrow_up:

src/ripple/app/misc/impl/ValidatorList.cpp
84.39% <100%> (-0.06%)
:arrow_down:

src/ripple/rpc/impl/TransactionSign.cpp
89.96% <100%> (+0.28%)
:arrow_up:

src/ripple/app/main/Application.cpp
58.24% <100%> (-0.24%)
:arrow_down:

src/ripple/json/impl/json_value.cpp
77.33% <100%> (+1.23%)
:arrow_up:

src/ripple/app/misc/impl/AccountTxPaging.cpp
89.42% <100%> (ø)
:arrow_up:

src/ripple/net/impl/RPCErr.cpp
100% <100%> (ø)
:arrow_up:

src/ripple/json/impl/json_reader.cpp
67.21% <100%> (-0.16%)
:arrow_down:

... and 128 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5807ce2...d129543. Read the comment docs.

cherry-picked Scott's 2150fd1fd581a1a5a1ffa34483b5e3157daa454a

Merged in 1a245234f


feat: Added "Scale dataplane to zero" workflow to the documentation

Documented the "Scale data plane to zero" workflow to allow the customers to save money and compute time. It's mainly focussed in AWS but should be provider agnostic.
Signed-off-by: Juan Manuel Parrilla Madrid<EMAIL_ADDRESS>Which issue(s) this PR fixes
Fixes #HOSTEDCP-576
Checklist

[X] Subject and description added to both, commit and PR.
[X] Relevant issues have been referenced.
[X] This change includes docs.
[ ] This change includes unit tests.

Thanks Juan! Let's please retitle the PR title and desc to remove any reference to hibernation. This is just about how scaling down and draining works.

/hold

lgtm

/approve
/lgtm

/unhold


Employee Attrition Dataset and basic structure

I'll add more detailed instructions in asap

Hi @AjayKhalsa thanks for the contribution. Please add data source/credit in the readme.md either in data or exercise folders (or both). Perhaps once you are done with the first pass of the structures, comment here and we can merge it so others can contribute to this folder.

@gimseng I made a basic structure, check it out. I'm thinking they can add their model's description in the readme provided in the solution folder but what should be its structure?  Also, many contributors will make PR's using the same models so would we merge the best model?

@AjayKhalsa Could you link or provide documentations on the data in the readme.md of the data folder?
If the data is publicly available online, please provide a link for a detailed description of the data.
If its not public, but it is fine for us to use, please provide a detailed documentations, either uploading them or copied and pasted more detailed descriptions in the readme.md
Sorry to insist on this, but I just want to make sure we won't get into trouble due to privacy concerning data. Furthermore, it is important to understand where the data is from, the quality of data collection and limitations of the data.

@gimseng  The dataset was a part of this competition https://www.kaggle.com/c/summeranalytics2020
If it doesn't seem appropriate I can just replace it with the original IBM Employee Dataset which is openly available

I think for safer side we should just use IBM's dataset, i'll replace it

@AjayKhalsa Thanks ! Sure, I'm agnostic of the source, as long as its properly documented somewhere that we can link to and provide credit for. I've cleaned up the exercise and solution readme a bit further. We could merge it as soon as you have finished the data source/credit part of the 'data' folder. Thanks !

@gimseng  I updated the dataset you can merge it now, if we need to make any changes we can do it directly.

@AjayKhalsa Great! I shall merge now.


Expose more APIs from the crate?

Generally dealing with different types of debug information, in particular DWARF vs PDB, and then parsing different types of attributes in different formats into meaningful structures is quite painful.
It looks like ddbug solved most of these issues providing a consistent higher-level interface on top of lower-level gimli, object and pdb APIs, but doesn't expose them in the API (https://docs.rs/ddbug/0.2.0/ddbug/struct.File.html is opaque and allows only printing it out).
I wonder if it would make sense to either extract these APIs into a separate crate or expose them in the API of the library part of this one?
I understand these are subject to breaking changes over time, but having such starting point would be still much nicer than trying to reimplement all of it myself.

The current API exposed by this crate was only provided for the purpose of testing ddbug itself.
I think it makes a lot of sense to expose more APIs. Part of my motivation in writing ddbug was to get a some experience in what is useful for those APIs. The current APIs are probably a bit too focused on the needs of ddbug, but they can evolve. In the short term it's probably easier if they remain in this crate (or at least in this git repo as part of a workspace), but long term I'd be fine with moving them to a separate crate.
The DWARF support suffers from needing to load too much into memory, and my recent focus has been on reducing this, but there's still more to go. There's probably a few other issues that I don't recall right now.
The PDB support is currently quite poor, and I've actually disabled it for now while I focus on the DWARF. Part of the problem is that the pdb crate is incomplete.
Is this something you want to work on doing? Or do you want me to make a start on it, and then we can fixes issues as they arise? I can't promise when I'll get time to do it though.

The PDB support is currently quite poor, and I've actually disabled it for now while I focus on the DWARF.

I didn't know about this though, but still, I guess it's okay for a start?

The DWARF support suffers from needing to load too much into memory, and my recent focus has been on reducing this, but there's still more to go.

Same - I suppose this can be split into functions instead of fields so that it could be retrieved on-demand (or maybe even lazily stored inside of the structure), but having a nice ground helps.

Or do you want me to make a start on it, and then we can fixes issues as they arise?

As mentioned above, I think just exposing what is available now would be a good start as I've actually started reimplementing something very similar for my own purposes, but then realised that ddbug must have solves most of these issues already, and indeed, found a rich hidden API :)
I don't know how much I would be able to help as this is for yet another side-project I have in the back of my head, and I'm already feeling guilty for all the OSS projects I don't have much time to contribute to anymore, so don't want to make promises, but would be certainly happy to help whenever possible :)

I didn't know about this though, but still, I guess it's okay for a start?

The PDB support currently only has type information, not symbol information. Depends what you need.

Same - I suppose this can be split into functions instead of fields so that it could be retrieved on-demand (or maybe even lazily stored inside of the structure), but having a nice ground helps.

The idea is that we parse as little as possible initially, and instead refer to functions/types etc by their DIE offset, and then parse the rest of the fields when needed. I think this is mostly done, but it is still using too much memory for the file I was testing on (libxul.so). Not sure if there is more that can be done while keeping all the functionality. It'll be a decent starting point for normal sized files anyway.

The PDB support currently only has type information, not symbol information. Depends what you need.

For start I would want function and type information, you're saying that former is not available, right?

and then parse the rest of the fields when needed. I think this is mostly done, but it is still using too much memory

Ah interesting. Libs I'm interested in are usually much smaller, so initially this shouldn't be an issue, but still interesting to tackle in future.

I've split out a ddbug_parser crate (still in this repo). See if that fits your needs, and let me know any issues you find. I'll probably do a few more cleanups in the coming days. I've avoided the panopticon dependency in ddbug_parser, so I'll be able to publish it to crates.io once things settle.

For start I would want function and type information, you're saying that former is not available, right?

I think it only had public symbols for functions. It's been a while since I've checked and it's currently disabled. I'll have a look at enabling it again sometime.

Sorry, I'll need few more days to get back to this and try that crate out. Thanks for extracting the APIs though, much appreciated!

Going to close this as done. Feel free to reopen or create new issues if needed.

It looks like ddbug_parser hasn't been updated in a while, and trying to use version from Github results in various errors due to relative crate paths in Cargo.toml.
Could you please publish a new version?

That's going to require a moria update first. I've hacked it locally (hence the relative crate paths). Looks like moria was never published at all, and someone else has squatted the name on crates.io. I'm not really interested in maintaining moria. I'm happy to merge any patches that get this working for you.

I deleted the moria support and published to crates.io.


Typo on website

On your website you say:
"WICH contain other elements,"
Have a good day;
Stephen.

Bump..
Great work though!

np.  Have a great day.
On Tue, Sep 22, 2015 at 10:38 AM Romanos<EMAIL_ADDRESS>wrote:

Bump..
Great work though!
—
Reply to this email directly or view it on GitHub
https://github.com/pixxelfactory/jInvertScroll/issues/11#issuecomment-142358576
.


Encode view state in URL

Encode the view state in URL for easy sharing

This probably only makes sense if the data is shared as well.
If the (pre-processed) tuple data is hosted somewhere, then sharing could be possible like this:
https://asgerf.github.io/codeql-flamegraph-viewer/?source=https://github.com/esbena/tuple-counts/tuples-123abc.tuples&focus=42


Create time_zone_conversion.py

hello there!
I would love to contribute the code for time zone conversion in python
I am making a contribution after a very long time so apologies if I made a PR to a wrong branch.
hope it gets merged :)
Pull Request Template
script name -
Brief about script
Issue no.(must) -
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me.
[x] One Change in one Pull Request
[ ] My file is in proper folder (Name of folder should be in lowercase with no space in between) (E.g. meet_schedular)
[ ] I am following clean code and Documentation and my code is well linted with flake8.
[ ] I have added README.md and requirements.txt (Include version numbers too e.g. pandas==0.0.1) with my script
[ ] I have used REPO README TEAMPLATE (Necessary)
[ ] Just including required dependencies in requirements.txt (Don't include Python version too)

If issue was not assigned to you Please don't make a PR. It will marked as invalid.

Please raise a issue of script first, this is duplicate of #731


TemplateMonad in Prop?

@gmalecha and I are running into issues into universe inconsistencies which go away when we put TemplateMonad _ in Prop.
Can we revisit the decision to put it in Prop?
AFAIK, there are two disadvantages of  (TemplateMonad _):Prop.
(1) (TemplateMonad _):Prop  prevents us from writing Gallina programs that inspect template programs (of type TemplateMonad _))  to, e.g., transform them to other programs.
(2) (TemplateMonad _):Prop  prevents us from running template programs after extraction: After extraction, anything of type TemplateMonad _ gets erased instead of being extracted to a function that can natively run in OCaml.
I don't know any use case for (1), so I will ignore it for now. If others have non-contrived use cases in mind, please post here.
(2) is important for efficiency and below I describe a workaround that @gmalecha and I came up with.
First, some operations in TemplateMonad _ cannot be implemented after extraction to OCaml. In particular, operations that take arguments that are parametric over any type (their signature begins with forall {A:Type@{t}}, A ->) are unrealizable in OCaml. As an example, consider tmQuote:forall {A:Type@{t}}, A  -> TemplateMonad Ast.term
Consider the case when A:=nat->nat. In the OCaml interpreter that runs
template programs without extraction, the second argument of tmQuote will be a Term.Constr representing the AST of a gallina function. However, after extraction, the argument would be an OCaml function of type Nat->Nat, where Nat is the OCaml datatype extracted from the Gallina nat.  In OCaml, it is impossible to get the internal representation of an OCaml function.
Similarly, tmPrint cannot be implemented to run after extraction.
In many applications, there is a workaround for tmQuote. In my applications, instead of tmQuote,  I used tmQuoteConstant: kername -> bool -> TemplateMonad constant_entry , or tmQuoteInductive which are implementable.
The upshot of the above discussion is that the full TemplateMonad type does not make sense anyway for extraction. So, can we then have inductive definitions, say TemplateMonad and InType.TemplateMonad, such that
(TemplateMonad _):Prop and (InType.TemplateMonad _):Type?
If we want to write programs that we wish to run both ways, we can write them against an interface, say TMInstance which can be instantiated both by
TemplateMonad and InType.TemplateMonad, as shown in this PR.
This PR is just to start a discussion and is not ready to be merged: it does not even build.

You're absolutely right, I didn't think of tmQuote and the like which are indeed not implementable after extraction. Maybe we should even restrict the module type to reflect only those commands that we know how to extract. Note, in MTac2 they used axioms to avoid problems with universes but I feel your proposed solution would be simpler.

One thing that we might work out is to only provide quoting during elaboration at a tactic. This is easily done with the limited Prop interface and @aa755 and I believe that it is pretty much everything that you would need.
In the style of MetaOcaml, you could expose syntax such as .< e >. (probably need to pick different syntax) that runs tmQuote on e at elaboration time and includes the result in the term (@yforster told me this is possible now with template-coq in "tactics"). That would allow you to write things such as: let cNat := .< nat >. in ... or let cId := .< fun (x : nat) => x >. in ... which you could then splice into terms appropriately. In, e.g. deriving, this often seems to just convert a command like Run TemplateProgram deriveFoo nat. into Run TemplateProgram deriveFoo .<nat>..Note for example, that you can/should only be able to quote closed terms, i.e. fun x : nat => .< x >. could technically elaborate to fun x : nat => Rel 1, but probably shouldn't.
Having true anti-quoting would be even greater, i.e. the ability to do something like: let cNat := .< nat >. in .< fun (x : .~ cNat) => x >., but that could be added post-facto if desired. For this model, you would need to desugar these into functions, i.e. the in-clause from above would become (fun z : constr => tLambda (..., z) (tRel 1))) cNat.

@aa755 @mattam82 What's the verdict on this? Is it just pending fixing the build error?

Well, yes at least. I didn’t look very closely at the interfaces, but we
can refine them later if need be.
Le mar. 2 oct. 2018 à 22:00, Gregory Malecha<EMAIL_ADDRESS>a
écrit :

@aa755 https://github.com/aa755 @mattam82 https://github.com/mattam82
What's the verdict on this? Is it just pending fixing the build error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Template-Coq/template-coq/pull/68#issuecomment-426409756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGARW6nWopjDafYjfVQZ0Jybu3g09Xsks5ug8XAgaJpZM4WqBvB
.

If you guys are up for doing a once-over and putting any comments here, I'd be happy to fix the plug-in.

@gmalecha I think you can just go ahead and fix it, the proposed change is ok to me.


<EMAIL_ADDRESS><EMAIL_ADDRESS>- tracing-subscriber 0.3 compatibility + Error impls

This PR takes #12 and #13 and packages them up into a release branch:

Updates tracing-subscriber to v3 in tracing-distributed (#12)
Updates arguments passed to trace::Event in tracing-distributed (#12, #13)
Updates tracing-honeycomb to accept tracing-distributed v0.3 or v0.4 (both are compatible)
Implements Error trait for TraceCtxError and ParseSpanIdError (#13)
Implements Display trait for TraceCtxError
Bumps tracing-subscriber to v0.4.0 (breaking)
Bumps tracing-honeycomb to v0.4.3 (additive)

A general release plan taking preroll and our apps into account is in the comments.

My plan:

Release<EMAIL_ADDRESS>(breaking)
Release<EMAIL_ADDRESS>(additive)
PR + release<EMAIL_ADDRESS>(breaking, beta)
Deploy<EMAIL_ADDRESS>to an internal service, iterate until the service is happy
PR + release<EMAIL_ADDRESS>

I don't know how yet, but I'm sure it's a command in cargo and I'm confident that as an owner I'll have the appropriate permissions. I'll try it out today and we'll see!

For checking what gets zipped, have a look at cargo package.
When ready cargo publish does the job. Needs a token for the used registry (e.g. crates.io).

Published<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Cheers!


Callback result safety

Please, add some kind of a check for callback result, because I just miss to call return in my callback and it gave me an error kind of:
(node:16) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'getBufferAsync' of undefined
    at jimp__default.default.read.then.then.img (/srv/app/node_modules/gulp-jimp-wrapper/dist/index.js:35:24)
    at <anonymous>

The first thing I thought about it was that there is something wrong with the package, but, fortunately, there was not. After a little debugging I found out the reason was my own inaccuracy. It's not fatal, but I just would appreciate it if you add some checks and a more understandable exception for that.
Thank you for your time in advance.

Yes you're right, it's better to have some meaningful error messages.
I'll work on it.

Try the new version. :nerd_face:
const processImage = async (img, cb, MIMEType) => {
  const res = await jimp.read(img.contents).then(cb)
  if (!(res instanceof jimp)) {
    throw new Error(
      'Jimp instance must be returned from the callback argument.'
    )
  }
  return res.getBufferAsync(MIMEType)
}

Works for me. Thank you


Middleware provider toolbar disappeared (Regression)

The toolbar on the providers show action it's gone.

Now is not showing:

I'm not sure if this is only happening on Middleware, other areas could have similar issues.
@miq-bot  add_label bug

It seems its already  solved ..


Just a question (Neoforge: 21.1.50  Minecraft: 1.21.1 Fluid Tank: 21.1.0) (No recipes for fluid tanks)

For the fluid tanks if the recipe's are not shown, shouldn't I still be able to create the fluid tanks anyway? As of right now I'm not able to create the fluid tanks unless I get the items from creative mode.
You most likely know of this already, but just thought you'd like to know anyway.

I'll check. It's not intended. Vanilla material tanks should be able to be crafted in survival.

I can craft the tank in my environment.

Wood
Stone

I think there is a log file named fluidtank-debug.log in log dir. Could you find and upload the file? It has the information of loaded recipes. I attach the file in my env.
fluidtank-debug.log

Here is the debug log most recently: https://gist.github.com/DatrixTheHybridShadowWolf/34ad0922f31d299768c211c5bb3b029a

It seems the fabric API conflicts with recipe condition. I add conditions for all platforms into just one file, and the fabric API might load the condition for fabric, but fails as it runs on Forge. Other recipes, such as fluidtank:reservoir_wood are loaded correctly as they don't use conditions.
{
  "fabric:load_conditions": [
    {
      "condition": "fabric:tags_populated",
      "registry": "minecraft:item",
      "values": [
        "c:gems/emerald"
      ]
    }
  ],
  "type": "fluidtank:crafting_grade_up",
  "forge:condition": {
    "type": "forge:and",
    "values": [
      {
        "type": "forge:not",
        "value": {
          "type": "forge:tag_empty",
          "tag": "forge:gems/emerald"
        }
      }
    ]
  },
  "neoforge:conditions": [
    {
      "type": "neoforge:not",
      "value": {
        "type": "neoforge:tag_empty",
        "tag": "c:gems/emerald"
      }
    }
  ],
  "sub_item": {
    "fabric:type": "fluidtank:ignore_unknown_tag_ingredient",
    "type": "fluidtank:ignore_unknown_tag_ingredient",
    "values": [
      {
        "tag": "c:gems/emerald"
      },
      {
        "tag": "forge:gems/emerald"
      }
    ]
  },
  "tier": "EMERALD"
}

Thanks for the quick response and explaining it to me. I appreciate that.

Try v21.1.3

It now works. Thank you!


node.js 12  依赖编译不过去 node.js8版本可以 能否支持一下

/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:21:40: error: no matching member function for call to 'ToString'
String::Utf8Value str(args[0]->ToString());
~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:42:97: error: no matching member function for call to 'ToString'
String::Utf8Value messageType((node->Get(String::NewFromUtf8(isolate, "messageType")))->ToString());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:42:58: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value messageType((node->Get(String::NewFromUtf8(isolate, "messageType")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:42:46: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value messageType((node->Get(String::NewFromUtf8(isolate, "messageType")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:44:87: error: no matching member function for call to 'ToString'
String::Utf8Value type((node->Get(String::NewFromUtf8(isolate, "type")))->ToString());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:44:55: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value type((node->Get(String::NewFromUtf8(isolate, "type")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:44:43: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value type((node->Get(String::NewFromUtf8(isolate, "type")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:45:87: error: no matching member function for call to 'ToString'
String::Utf8Value name((node->Get(String::NewFromUtf8(isolate, "name")))->ToString());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:45:55: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value name((node->Get(String::NewFromUtf8(isolate, "name")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:45:43: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value name((node->Get(String::NewFromUtf8(isolate, "name")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:46:91: error: no matching member function for call to 'ToString'
String::Utf8Value status((node->Get(String::NewFromUtf8(isolate, "status")))->ToString());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:46:57: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value status((node->Get(String::NewFromUtf8(isolate, "status")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:46:45: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value status((node->Get(String::NewFromUtf8(isolate, "status")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:47:87: error: no matching member function for call to 'ToString'
String::Utf8Value data((node->Get(String::NewFromUtf8(isolate, "data")))->ToString());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2572:44: note: candidate function not viable: requires single argument 'context', but no arguments were provided
V8_WARN_UNUSED_RESULT MaybeLocal ToString(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2588:31: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
Local ToString(Isolate* isolate) const);
^
../src/nodecat.cc:47:55: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value data((node->Get(String::NewFromUtf8(isolate, "data")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:47:43: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
String::Utf8Value data((node->Get(String::NewFromUtf8(isolate, "data")))->ToString());
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:48:99: error: too few arguments to function call, single argument 'context' was not specified
double begin = node->Get(String::NewFromUtf8(isolate, "beginTimestamp"))->NumberValue();
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2608:3: note: 'NumberValue' declared here
V8_WARN_UNUSED_RESULT Maybe NumberValue(Local context) const;
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:351:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT attribute((warn_unused_result))
^
../src/nodecat.cc:48:46: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
double begin = node->Get(String::NewFromUtf8(isolate, "beginTimestamp"))->NumberValue();
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:48:34: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
double begin = node->Get(String::NewFromUtf8(isolate, "beginTimestamp"))->NumberValue();
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:49:95: error: too few arguments to function call, single argument 'context' was not specified
double end = node->Get(String::NewFromUtf8(isolate, "endTimestamp"))->NumberValue();
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2608:3: note: 'NumberValue' declared here
V8_WARN_UNUSED_RESULT Maybe NumberValue(Local context) const;
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:351:31: note: expanded from macro 'V8_WARN_UNUSED_RESULT'
#define V8_WARN_UNUSED_RESULT attribute((warn_unused_result))
^
../src/nodecat.cc:49:44: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
double end = node->Get(String::NewFromUtf8(isolate, "endTimestamp"))->NumberValue();
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:49:32: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
double end = node->Get(String::NewFromUtf8(isolate, "endTimestamp"))->NumberValue();
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:58:13: error: use of undeclared identifier 'Handle'
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
../src/nodecat.cc:58:20: error: 'Array' does not refer to a value
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3845:17: note: declared here
class V8_EXPORT Array : public Object {
^
../src/nodecat.cc:58:27: error: use of undeclared identifier 'children'
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
../src/nodecat.cc:58:38: error: use of undeclared identifier 'Handle'
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
../src/nodecat.cc:58:45: error: 'Array' does not refer to a value
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3845:17: note: declared here
class V8_EXPORT Array : public Object {
^
../src/nodecat.cc:58:76: warning: 'NewFromUtf8' is deprecated: Use maybe version [-Wdeprecated-declarations]
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:2934:10: note: 'NewFromUtf8' has been explicitly marked deprecated here
static V8_DEPRECATED(
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:58:64: warning: 'Get' is deprecated: Use maybe version [-Wdeprecated-declarations]
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3457:3: note: 'Get' has been explicitly marked deprecated here
V8_DEPRECATED("Use maybe version", Local Get(Local key));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8config.h:311:29: note: expanded from macro 'V8_DEPRECATED'
declarator attribute((deprecated(message)))
^
../src/nodecat.cc:58:53: error: no member named 'Cast' in the global namespace
Handle children = Handle::Cast(node->Get(String::NewFromUtf8(isolate, "children")));
~~^
../src/nodecat.cc:59:25: error: use of undeclared identifier 'children'
int count = children->Length();
^
../src/nodecat.cc:61:40: error: use of undeclared identifier 'Handle'
InnerSendNode(isolate, Handle::Cast(children->Get(i)));
^
../src/nodecat.cc:61:47: error: 'Object' does not refer to a value
InnerSendNode(isolate, Handle::Cast(children->Get(i)));
^
/Users/qizhang/.node-gyp/12.13.1/include/node/v8.h:3400:17: note: declared here
class V8_EXPORT Object : public Value {
^
../src/nodecat.cc:61:56: error: no member named 'Cast' in the global namespace
InnerSendNode(isolate, Handle::Cast(children->Get(i)));
~~^
../src/nodecat.cc:61:61: error: use of undeclared identifier 'children'
InnerSendNode(isolate, Handle::Cast(children->Get(i)));
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
17 warnings and 20 errors generated.
make: *** [Release/obj.target/nodecat/src/nodecat.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/cnpm/node_modules/_node-gyp@3.8.0@node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.7.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/cnpm/node_modules/npminstall<EMAIL_ADDRESS>"rebuild"
gyp ERR! cwd /Users/qizhang/Workplace/sardine/SardineIMServer/node_modules/@dp-cat_client@3.1.2@@dp-cat/client
gyp ERR! node -v v12.13.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
[npminstall:runscript:error]<EMAIL_ADDRESS>has binding.gyp file, run "node-gyp rebuild" error: Error [RunScriptError]: Run "sh -c node-gyp rebuild" error, exit code 1
at ChildProcess. (/usr/local/lib/node_modules/cnpm/node_modules/_runscript@1.4.0@runscript/index.js:96:21)
at ChildProcess.emit (events.js:210:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
name: 'RunScriptError',
stdio: [Object]
}

我看到日志node已经修复了node 12的版本，但是版本还是3.1.2 npm市场的版本还是老的代码，请发布一下3.1.2+到npm市场吧

应该没问题的，可以编译过去，我这里成功了


fix kernel name of cupyx.scipy.ndimage.interpolation.map_coordinates

fixed a mistake caused by copy-and-paste

LGTM. Thanks!


Fix retain cycle between BuiltInBuildSystemAdapter and BuiltInBuildSystemAdapterDelegate

This was causing memory leaks.

@swift-ci Please test

@swift-ci Please test Windows


Enable CoreOS Install to Disk

Should we make /dev/sda a talk option that defaults to sda?

I originally had that support when I made these adjustments months ago. Trying to remember why I backed it out. Should be trivial to support.

Perhaps because iPXE enumerates devices with inconsistent orders?

Maybe we should support wwid instead of udev names if someone is configuring it?

Looking now to see if the coreos-install binary will take those as arguments

It just takes any blockdev path that is accessible. The checks are done using lsblk so the user can specify any path for input. /dev/sda will be the best default and users can use catalog details to refine their path more.

awesome

:+1:

+1

Relies on https://github.com/RackHD/on-tasks/pull/77


localStorage access is unguarded

Even with isSaveState: false, it gets "DOMException: Failed to read the 'localStorage' property from 'Window': Access is denied for this document" when storage is disabled in the browser settings.
All usage of localStorage should be wrapped in a try-catch.

Are you trying to run this dev tool in a headless browser or in node? This tool is not suppose to be shipped into production, but just be a browser based tool for you to edit curves in. So no need to run this when not developing in client side.

I just thought I would report this issue since this demo doesn't work for me. I can pan the view, but no curve is displayed:

My actual use case is a little outside the library's immediate scope, and I expect to fork it to achieve what I want (although the API could be generalized to support this). Rather than doing animation, I want to control a mouse acceleration curve for a head tracking system. So instead of time, the input axis is head speed, and then the output axis is pointer speed.
I'd like to present a simpler UI to users, ultimately, but first I need to understand the range of curves that works well.
And I may leave a full curve editor in as an advanced option, if it's not too much trouble to maintain. We'll see.
And I could roll my own curve editor but this one looks very nice and polished, and even fits the color scheme of my app :)


Make picker in the middle of big screen,not bottom.

It will be more friendly on big screen.

This picker is designed for mobile browser exactly.


weston: 7.0.0 -> 8.0.0

Announcement:
https://lists.freedesktop.org/archives/wayland-devel/2020-January/041147.html

Motivation for this change
Things done

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

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

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/january-2020-in-nixos/5771/1


Failed to load ibdesignable from path (null) via cocoapods

via cocoapods  install  EAColourfulProgressView
xcode tip error: Failed to load ibdesignable from path (null)
I missed something？
Please check or make one 'storyboard' demo via cocoapods  to make sure it's work
THX

This has been fixed with the latest beta version of Cocoapods, take a look at my answer here.
I'm closing this issue, you can open a new one as enhancement for your "nice to have" suggestion.
Thanks.


KWYG link/mention

Mention KWYG as project on the website
-> Maybe a good topic for landing page.

[ ] English translation


Knuu rate limiter

Overview
Currently large Knuu tests are limited by the kubernetes global rate limiter. In order to enable larger knuu tests, knuu needs to be able to gracefully handle rate limiting.
Options

Add an internal ratelimiter to the knuu k8 controller that throttles requests to keep under the global rate limit
Add retry mechanisms with a timeout for requests that fail due to rate limiting.
Some combination

Considerations
Option 2 is probably the most simple and low touch. For this option we wouldn't need to even care about what the rate limit is, we just need to have a k8 request timeout variable and/or k8 max retry variable that is used around the k8 client set calls.
This could then naively just be applied around all calls as a POC to verify this works.
A step 2 could then be to create some extractions, either as option 1 or something similar that allows for a single interface for managing the retry logic.
Testing
If we go with option 1, the ratelimiter itself can be thoroughly unit tested.
In all cases, the k8 mocking can be used to mock requests returning the ratelimit error to ensure the error is handled gracefully.

Ah, we should just use this: https://pkg.go.dev/k8s.io/client-go/util/retry#OnError
example from chatgpt
package k8s

import (
	"context"
	"time"

	"github.com/sirupsen/logrus"
	appv1 "k8s.io/api/apps/v1"
	v1 "k8s.io/api/core/v1"
	apierrs "k8s.io/apimachinery/pkg/api/errors"
	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
	"k8s.io/client-go/util/retry"
)

const maxRetries = 3
const retryDelay = 1 * time.Second

func (c *Client) GetDaemonSet(ctx context.Context, name string) (*appv1.DaemonSet, error) {
	var ds *appv1.DaemonSet
	err := retry.OnError(
		retry.DefaultBackoff,
		func(err error) bool {
			apiErr, ok := err.(apierrs.APIStatus)
			if !ok {
				return false // Not a Kubernetes API error
			}
			// Retry only if rate limit exceeded error
			return apiErr.Status().Reason == metav1.StatusReasonTooManyRequests
		},
		func() error {
			var err error
			ds, err = c.clientset.AppsV1().DaemonSets(c.namespace).Get(ctx, name, metav1.GetOptions{})
			return err
		},
	)
	if err != nil {
		return nil, ErrGettingDaemonset.WithParams(name).Wrap(err)
	}
	return ds, nil
}


Extended settings

Implemented 3 more settings for the extension:
1. local file extension:
specifies the file extension for downloaded scripts. Because in escript you can define types, it is more like typescript then like js. So this gives the possibillity to save scripts as .ts files.
2. default fetch-type for method scripts in tree-view
this defines the default fetch type for the methods of an entity. It can be:
None - always ask    (as it is in default - vscode always asks)
Only method names    (fetch method names without asking)
Full scripts    (fetch full scripts without asking)
3. auto fetch single files
if true, always downloads script without asking for (see warning in settings)

Thank you for your contribution!


fixed typo

/cc @rpetrusha

Interesting, @mairaw. I could have sworn I fixed this before you went on vacation.

I see the fix in CAPS. Maybe it was only done there?

Quite possibly. I thought I fixed it in CAPS only after it was fixed here. But I don't see a PR.


Update README.md

Hi,
This small PR adds a button to get your app on F-Droid and changes the one for Google Play 👍

Thanks!


Extension fails to initialize when basicSsl plugin is used

Modifying the following server properties makes the extension broken:

server.https set to true
server.port changed

Workaround, check if mode === 'test' to opt-out the plugin

Any https configuration in server seems to affect this. Also there are similar reports scattered across other issues
https://github.com/vitest-dev/vscode/issues/196#issuecomment-1961315170
https://github.com/vitest-dev/vscode/issues/146#issuecomment-1646884873
I researched it a bit and it seems that multiple parts are at play here. I may be mistaken in any of them though
tldr
The issue looks very similar to https://github.com/vitest-dev/vitest/pull/4855/files but extension currently has no way to know whether api is secure or not
vitest part
It all starts with the fact that dev server in configureServer hook of VitestPlugin will inherit https settings from config.server.https
https://github.com/vitest-dev/vitest/blob/a51467af718513f704128171d20cd54b33b1262a/packages/vitest/src/node/vite-plugin.ts#L43
I suspect that related code of how settings are inherit will be in the vite source itself, cause I wasn't able to understand where it gets passed in vitest code
This https-configured server then gets saved in vitest context
https://github.com/vitest-dev/vitest/blob/b9d1a97599566fc07089d9f92d9388193a3dcf19/packages/vitest/src/node/plugins/index.ts#L224
And then when the api setup is called
https://github.com/vitest-dev/vitest/blob/b9d1a97599566fc07089d9f92d9388193a3dcf19/packages/vitest/src/node/plugins/index.ts#L226
it takes the server from the context
https://github.com/vitest-dev/vitest/blob/b8140fcadc114fd2d05ca997da4f7aa4e226417d/packages/vitest/src/api/setup.ts#L27
and configures websocket connection upgrade
But then does not respect this https in the logs here
https://github.com/vitest-dev/vitest/blob/ffa358517eb6a5ae6c975495d9ac3a05bfd9939f/packages/vitest/src/node/logger.ts#L101
vscode extension part
Extension run vitest api to get the config via executing it with cli api args
https://github.com/vitest-dev/vscode/blob/d62ca01494a29d7af5d98a609c7b347249bed1b1/src/pure/watch/vitestConfig.ts#L64
and then assumes that it's a non-secure url
https://github.com/vitest-dev/vscode/blob/d62ca01494a29d7af5d98a609c7b347249bed1b1/src/pure/watch/vitestConfig.ts#L11
which is not true and this is why connection just fails
additional challenge is if https is configured with a self-signed certificate just using wss:// is not enough, it's also needed to properly configure websocket client to ignore this
new WebSocketConstructor(url, { rejectUnauthorized: false }))
https://github.com/vitest-dev/vscode/blob/d62ca01494a29d7af5d98a609c7b347249bed1b1/src/pure/watch/ws-client.ts#L121
results
I was able to make this work by explicitly using wss:// protocol and rejectUnauthorized: false. But I currently don't see any trivial how extension can understand whether it needs to use secure or non-secure url because it needs it to get the config (which could theoretically contain this information, not sure if does, though)
possible solutions
force non-secure for vitest api
The fact that vite config https settings are leaking for vitest api/ui seems kinda counterintuitive for me and wonder if it should be the case. What problems may arise if vitest api will be made non-secure all the time?
allow to opt out of secure vitest api
Something like vitest --api --https=false which extension can take advantage of.
try both wss and ws (and maybe even rejectUnauthorized: false)
Just try multiple variants of connecting and see which one works. This looks like a last resort for me.
All of those may be related to the idea of splitting vitest api for different usecases https://github.com/vitest-dev/vitest/issues/3138
cc @sheremet-va

This is fixed in pre-release 0.5.0 and higher. Note that the extension now requires Vitest 1.4.0 or higher.
We no longer start any server.


docs: Integrate GraphQL API with Appsmith - How to Guide

Closes #215
Add a How to Guide which shows how to build a  "World Explorer" application on Appsmith with data from a GraphQL API.

This looks good @secure-crypto . Thanks for working on this

Hey @vihar @cokoghenun Thank you for giving me the opportunity to contribute. I have learned a lot and definitely looking forward to contribute more here in appsmith.


Support passing build variants from cli

This allows passing the variant from the cli to match conda build.
Eg  boa build recipe --python=3.11

Thanks!


[spigot] ItemBuildrer lore improvements

Right now the only options in ItemBuilder are setLore(List<Component>), I would like you to implement an option for single-component building.

Update: I am gonna be creating an additional branch for this, also I think the lore editing needs a little addition.
with permission of course, I would like to add a few options to the lore system @liorsl

What would you like to add?

What would you like to add?

Direct approach to add lore lines with components as well.
And I think this is a good time to add my lore editor and connect it with this system.

Your LoreEditor could be a nice addition to CocoaBeans but I think should have its own PR since it will require more work.
You are good to go on both

Great, but as a reminder you will need to make the system support two modes:

With native Kyori, so you have ItemMeta#lore methods
Without native Kyori, so you will have to translate the lore to legacy

I am not sure if this is done in the existing setLore code, but it should be there as well if we are already working on that

Great, but as a reminder you will need to make the system support two modes:

With native Kyori, so you have ItemMeta#lore methods
Without native Kyori, so you will have to translate the lore to legacy

I am not sure if this is done in the existing setLore code, but it should be there as well if we are already working on that

There is a part of it working.
Also, I stumbled upon a weird code that was set in the MetaData system.
apparently, @ikfir used a wrong approach to the MetaData of item lore, as he did not notice you could not add lore lines to existing lore in MetaData class, please allow me to edit Kfir's code and fix this issue immediately

Go ahead


Update node.js version to 20; update CI dependencies to remove warnings

This PR completes #219 and fixes #220 .

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/setup-python@v4, ./action. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

CI shows many notes about node16, I think It's from https://github.com/jurplel/install-qt-action/blob/master/action/action.yml#L79

CI shows many notes about node16, I think It's from https://github.com/jurplel/install-qt-action/blob/master/action/action.yml#L79

Fixed.

@jurplel

Thanks for the ping!

@jurplel Any plans to merge this in to v3 branch & release 3.3.1?

Will do

It looks like the failure is because the installed tools are not in the path in some conditions. Compare the outputs of stage "Test installed tools" for the workflow case "test (ubuntu-22.04, false, true, true, cached)": successful master:

Path: /home/runner/work/install-qt-action/Qt/Tools/QtInstallerFramework/4.6/bin:/home/runner/work/install-qt-action/Qt/Tools/QtCreator/libexec/qtcreator/clang/bin:/home/runner/work/install-qt-action/Qt/Tools/QtCreator/lib/Qt/bin:/home/runner/work/install-qt-action/Qt/Tools/QtCreator/bin:/opt/hostedtoolcache/Python/3.11.8/x64/bin:/opt/hostedtoolcache/Python/3.11.8/x64:/opt/hostedtoolcache/node/20.11.0/x64/bin:/snap/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

and failing branch v3:

Path: /opt/hostedtoolcache/Python/3.11.8/x64/bin:/opt/hostedtoolcache/Python/3.11.8/x64:/opt/hostedtoolcache/node/20.11.0/x64/bin:/snap/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin


Vignette

We'll also need a vignette for release that includes (at least) a couple examples of using the API wrapper.
Minimally, it should show how to use it:

[x] asynchronously (and synchronously)
[x] for initiating file downloads (and not)
[x] memoised (and not)

Closed in #7402203


Workbox integration

This adds the new workbox via its webpack plugin. this will also solve the problem of deplying to firebase and ziet

Oh Google !!!.
Too many confusing project. There is also https://github.com/GoogleChrome/sw-toolbox

@thangngoc89 fixed the dependencies
Perf comparison:
workbox: https://www.webpagetest.org/result/170605_2H_362c8443b400bff29b75760a28e82559/
sw-precache: https://www.webpagetest.org/result/170605_F6_32caa4a783cd74f4907fb833e6d3785e/

@prateekbh how SW library affects website first load?
Workbox demo has 15 request and sw-precache has 16 requests. Is that request reduced from SW file (i.e. some importScripts)? If so, how that improves first load?

Workbox demo has 15 request and sw-precache has 16 requests.
@NekR my bad, it was compared to an older version of master. I'll re fetch the results and post them

Please ignore previous results
Site with Workbox: https://www.webpagetest.org/result/170605_0T_e8021fc6664f38f5e73314b4e83fbdac/
Site with sw-precache:
https://www.webpagetest.org/result/170605_R6_8a8ea7f8d4619615ae4d5bf83f9577c3/

Extra request is the workbox-sw.prod.v1.0.1.js as an import script

@prateekbh I see workbox test works faster. I'm curious why, how it affects web app loading?

I actually re-run workbox test and it's now slower than your sw-precache test: https://www.webpagetest.org/result/170605_C8_869cec21eaa583078007bec25ed287b1/
This seems pretty random to me :-)

@NekR yes its acting pretty random, once i ran and the interactive time went beyond 4s  😞
and next run took it too 400 ms 😛

@developit can you check if this works for you on windows, so that we can move to workbox

also I guess "Preact CLI tests" PR has.travis.yml without which this is failing

We'll need to update this for the webpack changes.

@developit fixed now 😃

@prateekbh just asking - how do you do runtime caching with workbox?

@rkostrzewski here's how https://workboxjs.org/reference-docs/latest/module-workbox-sw.html

@prateekbh yeah but that's what should be placed inside SW, right? Can I pass some options via loader options? I couldn't see anything in the docs, neither on the repo about usage with webpack-plugin :cry:

yeah but that's what should be placed inside SW, right?

Even current implementation works on navigateFallback, so i am not changing that approach

Can I pass some options via loader options

Yes, webpack plugin takes all the options that is taken by workbox-build.
P.S. post this pr I'll add the capability of adding custom service worker which will make the entire thing super flexible

@developit can you please test this on windows, to be just doubly sure about it and then we can talk about the plan of this and one more PR that'll give super flexibility for service workers in preact-cli.

Closing this for now to keep the PR queue clean. Will reopen when its in bettershape

with workbox v3 alpha out now maybe we can reopen this issue?

@bodaz i am in favor of beta and then going ahead

Just a ping, Workbox is now at v3.4.1.


Attach to process

Is there a way to make ttyd not start a new process for each connection but attach all clients to one single instance/process ?
( -o doesn't solve this as I need to allow multiple connections)

It's possible, but you need other tools like tmux, see "Sharing single process with multiple clients" in Example Usage.


agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented using version 2.2.1

Summary
I am implementing Spark Expectations using version 2.2.1 and DBR 15 ( Spark 3.5 ) in a shared cluster. I am facing an issue in implementing with query dq check and sharing my error log below.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://github.com/nike-na-edea/na-edai-cia/blob/r360/na_inventory/qa/cvrg_dq_check/mkurr3/products/na_inventory/spark/python/src/etl/gold/coverage_dq_test.py#L97'
Run 'Line 238' to execute spark expectations
See below error

SparkExpectationsMiscException: error occurred while processing spark expectations error occurred while executing func_process error occurred while running expectations error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/actions.py:346, in SparkExpectationsActions.agg_query_dq_detailed_result(_context, _dq_rule, df, querydq_output, _source_dq_status, _target_dq_status)
    330     for _key, _querydq_query in sub_key_value.items():
    331         querydq_output.append(
    332             (
    333                 _context.get_run_id,
    334                 _dq_rule["product_id"],
    335                 _dq_rule["table_name"],
    336                 _dq_rule["rule"],
    337                 _key,
    338                 _query_prefix,
    339                 dict(
    340                     [
    341                         (
    342                             _key,
    343                             _context.spark.sql(
    344                                 _dq_rule["expectation" + "_" + _key]
    345                             )
--> 346                             .toJSON()
    347                             .collect(),
    348                         )
    349                     ]
    350                 ),
    351                 _context.get_run_date,
    352             )
    353         )
    355 if SparkExpectationsActions.match_parentheses(_dq_rule["expectation"]):
File /databricks/spark/python/pyspark/sql/connect/dataframe.py:2425, in DataFrame.toJSON(self, use_unicode)
   2424 def toJSON(self, use_unicode: bool = True) -> "RDD[str]":
-> 2425     raise PySparkNotImplementedError(
   2426         error_class="NOT_IMPLEMENTED",
   2427         message_parameters={"feature": "toJSON()"},
   2428     )
PySparkNotImplementedError: [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/actions.py:551, in SparkExpectationsActions.run_dq_rules(_context, df, expectations, rule_type, _source_dq_enabled, _target_dq_enabled)
    544 dq_start_time = datetime.strftime(
    545     current_date, "%Y-%m-%d %H:%M:%S"
    546 )
    548 (
    549     _querydq_output_list,
    550     _agg_query_dq_output_tuple,
--> 551 ) = SparkExpectationsActions.agg_query_dq_detailed_result(
    552     _context,
    553     rule,
    554     df,
    555     querydq_output,
    556     _source_dq_status=_source_dq_enabled,
    557     _target_dq_status=_target_dq_enabled,
    558 )
    559 current_date = datetime.now()
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/actions.py:438, in SparkExpectationsActions.agg_query_dq_detailed_result(_context, _dq_rule, df, querydq_output, _source_dq_status, _target_dq_status)
    437 except Exception as e:
--> 438     raise SparkExpectationsMiscException(
    439         f"error occurred while running agg_query_dq_detailed_result {e}"
    440     )
SparkExpectationsMiscException: error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/regulate_flow.py:96, in SparkExpectationsRegulateFlow.execute_dq_process.<locals>.func_process(df, _rule_type, row_dq_flag, source_agg_dq_flag, final_agg_dq_flag, source_query_dq_flag, final_query_dq_flag, error_count, output_count)
     92 _log.info(
     93     "The data quality dataframe is getting created for expectations"
     94 )
---> 96 _df_dq: DataFrame = _actions.run_dq_rules(
     97     _context,
     98     df,
     99     expectations,
    100     _running_rule_type_name,
    101     _source_dq_enabled=(
    102         source_query_dq_flag is True or source_agg_dq_flag is True
    103     ),
    104     _target_dq_enabled=(
    105         final_query_dq_flag is True or final_agg_dq_flag is True
    106     ),
    107 )
    109 _log.info("The data quality dataframe is created for expectations")
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/actions.py:643, in SparkExpectationsActions.run_dq_rules(_context, df, expectations, rule_type, _source_dq_enabled, _target_dq_enabled)
    642 except Exception as e:
--> 643     raise SparkExpectationsMiscException(
    644         f"error occurred while running expectations {e}"
    645     )
SparkExpectationsMiscException: error occurred while running expectations error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/core/expectations.py:503, in SparkExpectations.with_expectations.<locals>._except.<locals>.wrapper(*args, **kwargs)
    491 # In this steps source query data quality expectations runs on raw_data
    492 # returns:
    493 #        _source_query_dq_df: applied data quality dataframe,
    494 #        _dq_source_query_results: source query dq results in dictionary
    495 #        _: place holder for error data at row level
    496 #        status: status of the execution
    498 (
    499     _source_query_dq_df,
    500     _dq_source_query_results,
    501     _,
    502     status,
--> 503 ) = func_process(
    504     _df,
    505     self._context.get_query_dq_rule_type_name,
    506     source_query_dq_flag=True,
    507 )
    508 self._context.set_source_query_dq_status(status)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/utils/regulate_flow.py:165, in SparkExpectationsRegulateFlow.execute_dq_process.<locals>.func_process(df, _rule_type, row_dq_flag, source_agg_dq_flag, final_agg_dq_flag, source_query_dq_flag, final_query_dq_flag, error_count, output_count)
    164 except Exception as e:
--> 165     raise SparkExpectationsMiscException(
    166         f"error occurred while executing func_process {e}"
    167     )
SparkExpectationsMiscException: error occurred while executing func_process error occurred while running expectations error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/sinks/utils/collect_statistics.py:33, in SparkExpectationsCollectStatistics.collect_stats_on_success_failure.<locals>.decorator.<locals>.wrapper(*args, **kwargs)
     31 self._context.set_dq_start_time()
---> 33 result = func(*args, **kwargs)
     35 self._context.set_dq_run_status("Passed")
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/core/expectations.py:644, in SparkExpectations.with_expectations.<locals>._except.<locals>.wrapper(*args, **kwargs)
    643 except Exception as e:
--> 644     raise SparkExpectationsMiscException(
    645         f"error occurred while processing spark expectations {e}"
    646     )
SparkExpectationsMiscException: error occurred while processing spark expectations error occurred while executing func_process error occurred while running expectations error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/notifications/push/spark_expectations_notify.py:42, in SparkExpectationsNotify.notify_on_start_completion_failure.<locals>.decorator.<locals>.wrapper(*args, **kwargs)
     40 try:
     41     # self._context.set_dq_start_time()
---> 42     result = func(*args, **kwargs)
     44     if self._context.get_notification_on_completion is True:
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/sinks/utils/collect_statistics.py:45, in SparkExpectationsCollectStatistics.collect_stats_on_success_failure.<locals>.decorator.<locals>.wrapper(*args, **kwargs)
     44     self._writer.write_error_stats()
---> 45     raise SparkExpectationsMiscException(e)
     46 return result
SparkExpectationsMiscException: error occurred while processing spark expectations error occurred while executing func_process error occurred while running expectations error occurred while running agg_query_dq_detailed_result [NOT_IMPLEMENTED] toJSON() is not implemented.

During handling of the above exception, another exception occurred:
SparkExpectationsMiscException            Traceback (most recent call last)
File <command-459549117545118>, line 6
      3 source_df_dict = {'cods_digital_read_df': cods_digital_read_df}
      4 rules_df = spark.table('development.na_nda_dq.dq_rules')
----> 6 execute_spark_expectations(spark, writer, 'published_domain.inventory_coverage.coverage_open_demand_supply_digital_v', se_conf, source_df_dict, rules_df)
File <command-459549117542216>, line 73, in execute_spark_expectations(spark, writer, target_table, se_conf, df_dict, rules_df)
     70         df_dict[i].createOrReplaceTempView(i)
     71     return df_dict[list(df_dict.keys())[-1]]
---> 73 loc_build()
File /local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.11/site-packages/spark_expectations/notifications/push/spark_expectations_notify.py:53, in SparkExpectationsNotify.notify_on_start_completion_failure.<locals>.decorator.<locals>.wrapper(*args, **kwargs)
     51         _on_failure(e)
     52     # self._context.set_dq_end_time()
---> 53     raise SparkExpectationsMiscException(e)
     54 return result

**Expected behavior**
Below is my rule and my expectations are basic data quality check with count > 0 and should return True.
**Rule:**
%sql
insert into table development.na_nda_dq.dq_rules(
    product_id, table_name, rule_type, rule,
    column_name, expectation, action_if_failed, tag,
    description, enable_for_source_dq_validation, enable_for_target_dq_validation,
    is_active, enable_error_drop_alert, error_drop_threshold, query_dq_delimiter, enable_querydq_custom_output
    )
values (
    'na_inventory', 'published_domain.inventory_coverage.coverage_open_demand_supply_digital_v', 'query_dq', 'dsamd_count',
    '*', "( ({source_f1}) )>0@source_f1@select count(*) from cods_digital_read_df", 'ignore', 'validity',
    'source count checks from coverage_open_demand_supply_digital_v view', true, false,
    true, false, 0, '@', true
    );

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
spark-expectation-log-DBR15.txt

Thanks for highlighting this. Rootcause of this is related to the implementation of this line:
https://github.com/Nike-Inc/spark-expectations/blob/9500ed9ab4328ddf37c49cdb3063c71d6a37584e/spark_expectations/utils/actions.py#L346
And the problem particularly exists when using Spark connect.
Error is raised by connect code: see here for reference.
Solution would be for us to remove the need for toJSON. We're going to have to add a test for this specifically.


Handling of Secp256k1 signature malleability

TL;DR: Do we want the following to be an invariant of signature.Equal: It returns true for two signatures which are both valid for a given public key and message pair. If we want this to be an invariant we have to mildly adapt the equality implementation for secp256k1.
Secp256k1's signing algorithm is ecdsa. In ecdsa, the signature is of the form (r,s). However anyone given a valid signature on a message can produce a second valid signature (r, -s). So both of these signatures are valid, but have different byte representations.
Currently we load secp256k1 signatures directly from its bytes, and then check equality by checking if the byte representations are equal. However two valid signatures may not be considered equal currently. I think it may be easiest for future functionality to consider these as equal. This is also related to #1664. As far as I can tell, the downsides of this are that we've deviated slightly from the standard, but I'm unsure of how important that is in this case, and that decoding bytes to signature takes a bit more time. The upside is its one less attack / bug vector to be concerned about in downstream usage.
Other alternatives are to adapt the verify method to reject an ecdsa signature whose s is not in canonical form, or to have all validators force convert all s parameters into canonical form. (Canonical as being the smaller value within the finite field)
Of course, this only needs to be changed if this malleability is an issue. (I.e. Perhaps if a certain signature hash is expected)
/cc @ebuchman

Closing in favor of https://github.com/tendermint/tendermint/issues/1958


Problem creating table when using erlcloud_ddb2:configure/3

Hi,
I'm able to create a ddb2 table fine when I use configure/2, but when I add a specific region and use configure/3 I get the following:
{error,{http_error,400,"Bad Request",
<<"\nInvalidHttpRequestThe HTTP request is invalid. Reason: Unable to parse requesta97d3fa3-a837-4eef-94be-291fee27de75">>}}
Just to be clear, configure/3 returns 'ok'; it's the subsequent create_table request which returns the HTTP error.
Many thanks.

-module(ddb2_create_table_ireland).
-export([test/1]).
-define(HOSTNAME, "ec2.eu-west-1.amazonaws.com").
test([AWSKey, AWSSecretKey]) ->
ssl:start(),
erlcloud:start(),
%% ok=erlcloud_ddb2:configure(AWSKey, AWSSecretKey) %% WORKS :-)
ok=erlcloud_ddb2:configure(AWSKey, AWSSecretKey, ?HOSTNAME), %% DOESN'T WORK :-(
Resp=erlcloud_ddb2:create_table(
<<"Thread">>,
[{<<"ForumName">>, s},
{<<"Subject">>, s},
{<<"LastPostDateTime">>, s}],
{<<"ForumName">>, <<"Subject">>},
5,
5,
[{local_secondary_indexes,
[{<<"LastPostIndex">>, <<"LastPostDateTime">>, keys_only}]},
{global_secondary_indexes, [
{<<"SubjectTimeIndex">>, {<<"Subject">>, <<"LastPostDateTime">>}, all, 10, 10}
]}
]),
io:format("~p~n", [Resp]).

Looks like you are trying to make ddb requests to ec2. Try "dynamodb.eu-west-1.amazonaws.com"

That's great; thank you very much.
On 28 April 2015 at 20:37, Ransom Richardson<EMAIL_ADDRESS>wrote:

Closed #153 https://github.com/gleber/erlcloud/issues/153.
—
Reply to this email directly or view it on GitHub
https://github.com/gleber/erlcloud/issues/153#event-292340034.


Clicking the extension icon shows a narrow version of the options page

Gosh darn it, that’s what 350px was for.


changed compile to implementation (android)

It'd be awesome to have this merged. New React Native projects fail to build on Android because of it.

@yamill
Please merge it

@yamill Can you please merge this pull request? We need it since last updates. Thanks

do it please

@yamill Is this PR going to be merged?

@yamill Please merge this pr. This is affecting lot of users using this library and everyone need to apply patches as a workaround.


Starting an application from a github repository is very slow

Describe the bug
When opening a github repository using the url pattern, it takes a very long time before showing the preview. It seems it has nothing to do with the bundler used:

With Vite https://stackblitz.com/github/marmelab/react-admin/tree/master/examples/simple?file=README.md
With Webpack https://stackblitz.com/github/marmelab/bug-slayer?file=README.md

Opening the console shows many errors similar to Could not find source file: 'stackblitz:/HERE_GO_SOME_FILES_OF_OUR_PROJECT'. as mentioned in https://github.com/stackblitz/core/issues/3095 and #1515.
The fix mentioned in #1515 does not work anymore.
Link to the blitz that caused the error
https://stackblitz.com/github/marmelab/react-admin/tree/master/examples/simple?file=README.md
Steps to reproduce

Open https://stackblitz.com/github/marmelab/react-admin/tree/master/examples/simple
Notice it takes a very long time to show the preview
Open the devtool
Notice all the errors

Expected behavior
It should boot as quickly as before
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 128
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 193652072,
  "usedJSHeapSize": 176146888,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 134daa3c

Additional context
No response

Any updates on this bug? It seems that many people suffer from it.

Sorry to insist, but this issue is now the second most upvoted issue in this repo and has still received no feedback.

Bump, please consider this issue as it's a major bug.


There are now two different LICENSE files in the repo

Make it so there's only one LICENSE, preferably in the .txt format, and make corresponding changes to setup.py, pyproject.toml, and other files before publishing to TestPyPi.

PR #10 resolved this issue.


support OffsetArray write

021ca76: support OffsetArray write by loop over axes instead of hardcoded 1:length (closes #46)
4eab922: @propagate_inbounds are added for all getindex/setindex! function. I also see two unnecessary getindex methods, I don't know why they exist, so you might want to double-check it.

Does this PR work with AxisArrays? I know there's the name clash between Base.axes and AxisArrays.axes that this might trigger if both are imported, i.e.
using AxisArrays
using TiffImages

TiffImages.load("...") # error?

I have a long term project to lift OMETIFF.jl (which relies on AxisArrays) onto TiffImages so I want to make sure the two are compatible.

Codecov Report

Merging #47 (388428b) into master (06e06db) will increase coverage by 0.18%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
+ Coverage   89.54%   89.72%   +0.18%
==========================================
  Files          12       12
  Lines         545      545
==========================================
+ Hits          488      489       +1
+ Misses         57       56       -1

Impacted Files
Coverage Δ

src/types/dense.jl
97.05% <100.00%> (ø)

src/types/common.jl
58.82% <0.00%> (+5.88%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 06e06db...388428b. Read the comment docs.

AxisArray.axes is a new function and won't override the Base.axes behavior, the only issue is symbol conflict, which can be easily solved by using import and not using.
For 388428b I believe there can be smarter AxisArray support, but no I don't see any issue with it yet.

Ah, yeah. The symbol conflict is exactly what I'm concerned about. I have lots of code that has using AxisArrays so I would prefer to avoid conflicting with that. Can we avoid the symbol error by explicitly using Base.axes in this PR?

Can we avoid the symbol error by explicitly using Base.axes in this PR?

Yes, the following also works:
using AxisArrays
using Base: axes

Can we avoid the symbol error by explicitly using Base.axes in this PR?

Yes, the following also works:
using AxisArrays
using Base: axes

If you add the using Base: axes to this PR, I'll be happy to merge and tag a new release.

If you add the using Base: axes to this PR

Ha, AxisArrays is only used as a test dependency so it wouldn't affect the TiffImages functionalities at all.
Do you mean that I need to add using Base: axes in src/? I don't think we need to do so unless we're actually using AxisArrays inside TiffImages.

Does this PR work with AxisArrays? I know there's the name clash between Base.axes and AxisArrays.axes that this might trigger if both are imported, i.e.
using AxisArrays
using TiffImages

TiffImages.load("...") # error?

That's what I was asking initially. So what you're saying is that if we don't use AxisArrays inside of TiffImages then there shouldn't be any problems with the above code? Because then I'm ready to sign off on this, sorry for the confusion.
We could also remove the AxisArrays tests since they aren't revelant.

So what you're saying is that if we don't use AxisArrays inside of TiffImages then there shouldn't be any problems with the above code?

Yes, there won't be any problems with the codes. When we want to use AxisArrays inside TiffImages, then we can safely avoid the symbolic conflict with import AxisArrays instead of using AxisArrays. (or with explicit using Base: axes).

We could also remove the AxisArrays tests since they aren't relevant.

I'd be happier if we get more test cases (even if they're not very much relevant) 😆


Feature/sslproxy

Support for sslproxy provider including a parser + tests for
Updated #51

Coverage increased (+1.3%) to 63.494% when pulling 8f02c87582ad218aec741b5ef4eb3fbc94afd05d on feature/sslproxy into dd2cf266bb4005387f173a7647d46b1b6484db7d on master.


Added transform options to browserify gulp task

Just throwing this out there as some users might require some tweaking for whatever reason.
This could be extended to be declared in the config and have separate options for dev/prod
here's an example if a user wanted babel to ignore scripts in the bower_components directory:
{ 'name':babelify, 'options':{'ignore':['bower_components']}}

Actually, would it be more appropriate to move my fork with cordova support to its own repo, and refork this so branch names match up?

This looks good, thanks for the PR! :+1:
I'm not entirely sure I follow your question, but I see no problem with this PR/branch names. Merging!

@StrikeForceZero let me know if you want your Cordova fork featured in the README, could start a new  resources section since there's also a Yeoman fork as well.

Fine by me :+1:

@StrikeForceZero cool, added a link to the README in ff12b0b2824599497964773b1c9ad175ea0ee057


Integration with Qibo

Hello @rabrie and @padiro,
I forked this repo and created a functioning version of the code integration with the Qibo package for circuit generation and optimization.
Would you guys be interested in merging this into your main branch?
You can review the changes I made. Also, if this is not in the interest of the project, feel free to just close this PR.
In any case, thanks for the nice package.
PS: I also replaced the use of the built-in random package with default_rng from numpy because it is slightly faster for large sequence_numbers and increased sequence_length.

Hi Renato,
this is great, thanks for providing you qibo integration code.
I'll have a look at it soon an will let you know about the merge status.
Btw., I also saw your really nice robust shallow shadows paper comming out recently, huge congrats!
Best,
Raphael

Von: Renato Mello @.>
Gesendet: Montag, 16. September 2024 08:28
An: rabrie/mGST @.>
Cc: Raphael @.>; Mention @.>
Betreff: [rabrie/mGST] Integration with Qibo (PR #11)
Hello @rabriehttps://github.com/rabrie and @padirohttps://github.com/padiro,
I forked this repo and created a functioning version of the code integration with the Qibo package for circuit generation and optimization.
Would you guys be interested in merging this into your main branch?
You can review the changes I made. Also, if this is not in the interest of the project, feel free to just close this PR.
In any case, thanks for the nice package.

You can view, comment on, or merge this pull request online at:
https://github.com/rabrie/mGST/pull/11
Commit Summary

520fc47https://github.com/rabrie/mGST/pull/11/commits/520fc4793781d4a309e6622299d97dba6c8c62e6 qibo implementation
91cbfa2https://github.com/rabrie/mGST/pull/11/commits/91cbfa25ad306801b7edb116c76d56eed8456fbc attempt at exampple
08e9354https://github.com/rabrie/mGST/pull/11/commits/08e9354936ccd381d4e56b961d4dd163fb1220d4 missing quote
faf9acehttps://github.com/rabrie/mGST/pull/11/commits/faf9ace2fced68ed6cd600e160e920cf7cb34608 fix small bugs
4d6fb0bhttps://github.com/rabrie/mGST/pull/11/commits/4d6fb0b8cb5201a493954356bd9155beaa48d238 replace Qibo mentions

File Changes
(6 fileshttps://github.com/rabrie/mGST/pull/11/files)

M pyproject.tomlhttps://github.com/rabrie/mGST/pull/11/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711 (3)
M src/mGST/additional_fns.pyhttps://github.com/rabrie/mGST/pull/11/files#diff-0f2ab6aa1165d6e846ec3558ca26a301178547b61657c8ba5699420841ace78e (8)
M src/mGST/algorithm.pyhttps://github.com/rabrie/mGST/pull/11/files#diff-da88fc99dfa658675bb1d194bbe6a096ef76f5c0b37c0b14b0d3af31f4087b32 (12)
A src/mGST/qibo_interface.pyhttps://github.com/rabrie/mGST/pull/11/files#diff-f4e155fd1b31f89123f39a2e7bc87fa7ea225f0f994725bd4685bd021d0b9e40 (308)
M src/mGST/reporting/reporting.pyhttps://github.com/rabrie/mGST/pull/11/files#diff-9e629602c115d2f09839367a86455beeea07290204141e7061c9e86570e535ee (4)
A tutorials/qibo_interface.ipynbhttps://github.com/rabrie/mGST/pull/11/files#diff-9f28802a25d66914b6df3d2b589e26c7af834e3951a4df596e32ee92aecc4b3d (170)

Patch Links:

https://github.com/rabrie/mGST/pull/11.patch
https://github.com/rabrie/mGST/pull/11.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/rabrie/mGST/pull/11, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMX6X3QH4B6236EQGDHQXU3ZWZ3B3AVCNFSM6AAAAABOITNWUWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDONRQHE2TGNY.
You are receiving this because you were mentioned.Message ID: @.***>


config: CNF installation (3.1?) Limit cnf_setup to only one CNF

Description
Remove the ability of users to run cnf-testsuite cnf_setup {../testsuite.yml} multiple times.
Issues:
Refs: #2095 #2120
How has this been tested:

[x] Covered by existing integration testing
[x] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[x] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[x] Kind cluster

[ ] Have not tested

Types of changes:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:
Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] No updates required.

Code Review

[ ] Does the test handle fatal exceptions, ie. rescue block

Issue

[ ] Tasks in issue are checked off

I have some problems with this one, the main issue is that it would be easiest to implement this change after the rest of the #2120 epic is already done. With #2120 finished we could leverage the ability of setting up multiple CNFs as one, as currently some tests (/spec/5g/ran_spec.cr) rely on setting up two CNFs. There is a hack around this, and that is to use the Helm.install function directly, followed up by KubectlClient::Get.resource_wait_for_install, which is not exactly pretty.


TE-2694 Update for OEP-18, etc.

Refactor dependency management to comply with OEP-18 (both for this repo and the generated apps)
Update pinned dependencies
Update isort configuration to match edx-platform and recent changes to the edX Python style guide
Make isort show what changes it would make, not just report that changes are needed

@robrap @adeelkhan Do either of you want to attempt starting a new app from this before I merge?  Or should I merge it as is, and just make any incremental improvements after the next app is built from it?

@jmbowman: I had so many issues with virtual environments that I really don't want to spend the time.  On my wish list would be a docker container and instructions on how to run and test everything within the container in a way that will just work for everyone. :)

@robrap I'll create a separate ticket to try adding a container-based development option to the cookiecutter.

@jmbowman: That would be great.  Thanks.

Does the cookie-cutter already have tests to run itself and then run some scripts within the newly created repo and ensure that all goes well?  If not, that would be nice.  Not sure how often this changes and whether it is worth it, but it would be nice to know that all is well before the next person tries to use it. :)

There are already tests that generate an app and do some sanity checks on the output, and those are run in Travis.  The Docker work is captured in TE-2701.

@jmbowman:  Great. Thanks and thanks.


Investigate metrics for code quality

The most valuable contribution would be a system for identifying things like code complexity and code smells in Python and displaying them on developers' machines on-demand for individual files or for the entire code base. A tool that only identifies PEP-8 compliance is not needed.
A web platform that integrates with Travis-CI and/or Github would also be valuable.
Exit criteria:

a set of notes on metrics worth using and tools that compute them
a short presentation elaborating on the notes

@mwatts15 you asked me to look into this, please elaborate, I would like to make a pull request.


set of DEVON_IDE_HOME needs some path canonisation

Category: Bug
Severity: Low
Expected behaviour: Calling "devon help java" should output only one line for value of DEVON_IDE_HOME.
Actual/current behaviour:
Currently I get:

DEVON_IDE_HOME variable set to /sw/devon-ide-scripts-3.0.0-beta2devcon/scripts/command/../..
...
DEVON_IDE_HOME variable set to /sw/devon-ide-ide-scripts-3.0.0-beta2/scripts/command/../../scripts/command/../..

Steps to reproduce:
run "devon help java"
Comments:
The two output variable values result in the same path - so this isn't a functional issue - but it would be easier to read, if the relative parts of the path would be resolved, e.g with help of
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
as described on
https://stackoverflow.com/questions/59895/get-the-source-directory-of-a-bash-script-from-within-the-script-itself
The output of the variable is generated at the end of "functions", which is called twice (from commands/help and commands/java).
environment - macOS, devon-ide-scripts-3.0.0-beta2

Strange bug. However, I assume that this is already fixed some days ago and I just need to push out a new release (3.0.0-beta3). On my MacOS machine I can not reproduce this problem.

Fixed.


Support id token from external provider to access apiserver from proxy

Consider we have an open id provider (e.g. github), we need a way to use the id token from the provider to access multiple managed clusters if they use the same id provider.
/cc @yue9944882 @xuezhaojun

With IdPConfig we are able to configure Managed Cluster's OCP oauth config to connect to a central IDP server running on the hub cluster.  The oauth config in OCP allows for browser based automatic login but does nothing for allowing the IDP issued token to be used when connecting to the Managed Cluster's kube api server.  Effectively we are looking for a solution that would allow for a user to pass a bearer token populated with an IDP issued token on requests to a Managed Cluster's kube api server.  On the Managed Cluster the reciever of the request would need to verify the authenticity of the bearer token with a pre-defined IDP server (configured on each Managed Cluster via either by custom config or utilizing the existing OCP oauth config).  Once the bearer token has been verified and the user-info has been retrieved from the IDP server the reciever on the Managed cluster should lookup an existing user by the username provided by the IDP token in the OCP cluster.  Once the user has been found the request should utilize user-impersonation to execute the request against the kube api server on the Managed Cluster and return the result to the user.
This is a good example of the functionality we are looking for:
https://www.jetstack.io/blog/kube-oidc-proxy/
Here is the existing code related to the article above:
https://github.com/jetstack/kube-oidc-proxy

I'm not yet convinced that this work needs to be integrated into the reverse proxy service.  If the reverse proxy service is capable of calling multiple service end-points on the managed cluster then it would make more sense to create a new proxy service that would run on the Managed Clusters that the reverse proxy could target.  That way a user could either use the reverse proxy and target the kube-oidc-proxy service on the Managed Cluster or they could target the kube-oidc-proxy service on the managed cluster directly without going through the reverse proxy.  My only concern about forcing all communications through the reverse proxy would be the performance hit.  Obviously if there is a firewall between the hub and the Managed Cluster then it would be necessary to go through the reverse proxy, otherwise the user may elect to communicate directly with the managed cluster via the kube-oidc-proxy service.


Fix transparency and remove original RNTester

This PR fixes the transparent NavBar issue and removes the original RNTester

@AnshG714 , can you attach a screenshot this version?

@stealthanthrax


Use escape key to exit editing

The escape key can now be used to exit edit mode. In writing a todo, this will also cancel the new todo.

Marking as draft since I just noticed a critical bug, if you are renaming a todo and escape then it will delete it. Don't know how I didn't think of that.

Marking as draft since I just noticed a critical bug, if you are renaming a todo and escape then it will delete it. Don't know how I didn't think of that.

Fixed!

@Piturnah I like the enhancement. When I try editing and pressing esc it has the same effect as pressing enter and saves the edited text.

Yeah, that is the functionality I intended - but I do agree that it may feel more intuitive to have it cancel the edit you made. If the maintainer agrees then I'd be happy to give a go implementing this.


Logo proposal to UNIVERSALE

Hi, I'm a graphic designer and I like to collaborate with open source projects. I was seeing and I found this issues. I would like to design a logo for your Project. I will be happy to collaborate with you :)

Yeah I had opened that issue a long time ago when I started the project. Changed the name later and designed the current logo myself. Just a beginner and tried my hand at designing using gimp. Yeah sure I would be open to suggestion of a new logo.
Also if you're into UI/UX I would be glad to collaborate with you because this web-app needs some serious design improvements haha.
I would be spreading the word about it soon, just need to make some minor improvements.

That's great, of course, I'd like to help you :), I'll start with some sketches for the logo :)

Hello sir :), here is my proposal, I hope you like it.

Amazing logos @ggabogarcia !! Firstly I feel I am pretty sure that the github README hero image should contain the logo in the fourth row i.e. universale, so if you could please fork the repo and replace the hero image in the resources folder with this image with the proper size and resolution.
Secondly, for the primary logo I like the one in the second row  and the one in the third row(second one from the left). What do you think @finbargiusti @ggabogarcia , which one would you guys prefer?

I agree with you @vendantpuri and I believe the 2nd logo from the left 3rd row is the best.

If I understood correctly, will this be the winner?

Yes, and I think for a favicon the 2nd from the left in the 3rd row won. Keep it up

@ggabogarcia Yes that one would be the one to be put as the hero image in the README. So,
Fork the repo and replace the hero.png in the resources folder with that logo of the appropriate size and resolution.
For the favicon:
Place the image below in the root of the repo(real-size) by replacing univer-sale.png

Submit a pull request once this is done and I shall merge it.

@vedantpuri I sent a message to your mail sir :)


[REVIEW] Alafia-Ojo

GitHub Profile Link
https://github.com/Alafia-Ojo

Some more content in the profile readme would be appreciated :)


WIP: make pages archivable

Currently not working because of missing requirements.txt. Something went wrong on rebasing. I will figure that out tomorrow.
TODOs until this can be merged into develop:

[x] rebase correctly so so that the development environment functions correctly again (thanks to @timoludwig)
[x] make it possible to revert archiving in tree view
[x] listing of all archived pages
[x] adjust translations

I have finalized the basic functionalities for archiving pages so that this PR can be merged. The confirmation popups should also be used for other features if appropriate.
The question of how to deal with child pages will be dealt with later (especially during development of the API). I have summarised the previous considerations here: https://github.com/Integreat/cms-django/issues/132