integrations: Add Patreon integration

This PR adds Patreon integration. The following Patreon event triggers are handled in this PR:
members:create
members:update
members:delete
members:pledge:create
members:pledge:update
members:pledge:delete
I followed Zulip’s incoming webhook tutorial to write the code. In terms of testing, I used Json data for each of these events provided here https://github.com/zulip/zulip/issues/18321#issuecomment-838882140.
Fixes #18321.
Testing plan:
Ran testers and linters.
GIFs or screenshots:

@sudipto this all need squashing into a single commit.

Oh. I don't know how to proceed with that. Should I close this PR and create a new PR with a single commit message and description?

Hey @sudipto, I when you're selecting the integration at /devtools/integrations you don't have to scroll through the entire list. You can just open the list and then begin typing the name of the integration you're looking for. The same applies for all of those other dropdown lists too.

@Hypro999 Didn't know that. Using this for the first time. Thanks for the info.

Done.👍

Oh, and one more small suggestion (this is a personal suggestion) - maybe the delete events could use a different emoji? The tada emoji you've used for "new" events and notifications emoji for "update" events fit perfectly, but maybe for "delete" events you might want to use something else? Just an idea.

Made the changes. Should I squash the commits too?

This isn't ready for merge as this won't work until Patreon fix an issue upstream.

@sudipto we should also have a test for when we you raise UnsupportedWebhookEventType(event) so that we have 100% test coverage on your changes.

This isn't ready for merge as this won't work until Patreon fix an issue upstream.

What's the issue upstream?

Yeah thats the one @Hypro999. Hopefully shouldn't take too long as presumably it should be quite an easy fix for them to sort.

@sudipto do you have a chance to update this based on the review feedback?

@timabbott Yep. Was busy a bit. Will do it today.

@timabbott Updated. Added negative test for UnsupportedWebhookEventType(event) too.

@sudipto thanks for working on this!  I think this just needs some light editing to the formatting.

@sudipto ping -- do you have time to resolve the bit of remaining feedback here?

@timabbott sorry for the delay. I'll get it done within this week.

Great, let me know when ready!

@timabbott I am getting an error related to CodeQL but I can't understand the problem. Can you please help me out with this?

@timabbott I think this is ready.

@sudipto thanks for all your work on this!
This PR looks like it could use a little clean-up and be squashed into one commit. Would you be up for finishing it? If not, I can finish the work for you; it would be valuable to have this merged.

@prah23 you can take this up.

This work is carried forward in #22561.

Closing in favor of https://github.com/zulip/zulip/pull/28384.


[image_picker] iOS: Make the system UI to be popover instead of fullscreen to prevent crashes on iOS 14.

Description
See https://github.com/flutter/flutter/issues/67430, the crash can be prevented by this workaround: set the presentation style of the image picker to popover.
This PR also sets up some XCUITests to test the related scenarios.
Related Issues
Fixes https://github.com/flutter/flutter/issues/67430
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Hi, @cyanglaz.
I appreciating your commit.
I tried to your change on my app and was not crash on iOS14 👍
But can not get image path from imagePicker.getImage result.
Do you recognize this issue?

@teamdynamiteapp I didn't see this issue. Is it 100% reproducible or it is flaky?

@teamdynamiteapp I found a potential race condition where the image picker controller can dismiss too fast that the result is not ready yet. I updated the code to dismiss the controller after all the results are ready. Could you try again to see if it fixes your issue? (I still can't repro the issue on my local tho)
I have updated the tests to run more times so it is more likely to catch race conditions.

@cyanglaz
Thanks for your response.
I tried to your latest changes again.
Probably looks like everything ok for me 👍
I looking forward to merge this PR.

I tried this PR on iOS 14.0 flutter stable branch and it works perfectly.
However on iOS 13.6 using same iOS 11 Pro simulator it doesn't work. After selecting the image, nothing happens.

e58a38d fixed the issue. Thanks

It crashes on all iPads consistently with
'UIPopoverPresentationController (<UIPopoverPresentationController: 0x7ff884f30b30>) should have a non-nil sourceView or barButtonItem set before the presentation occurs.'

@azborovskyi Good catch. I didn't test it on iPad, will push a fix soon.
@joniaiuser It was very unlikely that merging master fixed your issue as there wasn't any changes in the image picker. Maybe the issue you saw was some sort of race condition? Could you try more times to see if it happens?

looking forward to this fix 🔥

The crash has been fixed with the latest engine. I'm going to close this PR.

Hi @cyanglaz I am grateful for your help.  The fixed engine means ios 14 update ? Can you share with us which update they fixed ?

@skyberk No, I didn't mean an iOS update. I meant the the fix is in the flutter framework. You should see the fix in master channel.

I am running latest flutter engine and its still crashing for me :/

@varun-horizon Could you share more details? It was working for me. Could you share your flutter doctor -v and your flutter run command syntax? Maybe also the stacktrace?

hey @cyanglaz thanks for fixing this. Do you know when it will be in stable?

I am running latest flutter engine and its still crashing for me too


Draco：is there a plane to build a DracoLoader?

hope Draco can be used with babylon
https://github.com/google/draco
https://github.com/mrdoob/three.js/pull/10879

I know that @bghgary was doing some experiments

@deltakosh @bghgary thanks for reply
I think there should be two widgets.one is an encoder,the other is a 'decoder'(loader)

I have been doing experiments here: https://github.com/bghgary/Babylon.js/commit/57bf92980cbb0e844219dfc1a7ba78a0a8098a96

@deltakosh glad to see that and thanks for your work. expecting this can be released asap.
i'm new to draco,i think this feature is very important to reduce downloading time. do u think so?
by the way, are you Chinese?

This is now done :)
Thanks @bghgary


No need set hostname when hostname is a IP Address.

When hostname is IP Address SSL_set_tlsext_host_name cause TLS handshake failed.
Bug #49183

/cc @brianquinlan

Assigning a reviewer here to remove this from our triage queue (the review itself should happen on the gerrit CL).

Hey @mount33
I made a comment at https://dart-review.googlesource.com/c/sdk/+/309620

@brianquinlan ping? should this PR be closed?

Hey @mount33,
I ran the script that you suggested with Dart 3.1.0 (and Dart 3.0 and Dart 2.9) and got the same output as curl i.e.
<!DOCTYPE html><meta charset="utf-8"><title><IP_ADDRESS> — The free app that makes your Internet faster.</title>
...
</path></svg>

What platform are you using, maybe the effect is platform-specific?

I tested this with Dart 3.1 on Windows and could not repro.
No need to apologize! Thank you so much for the effort!


add macos edge support

Hi, the safe storage strings were made dynamic by an earlier delayed PR.
We could include the example though.


[FEA] it is hard to get the schema when you do several workflows

🚀 Feature request

It would be great if we can better keep track of the schema, cardinality and other features. There are a better way to deal with columns than with the schema?
Motivation

I am a bit frustrated when I try to feed the schema into Transformers4Rec. I am trying to adapt the competition code from Coveo Recsys competition to Transformers4Rec.
Being a more complex example than the ones that are updated to 0.7.x nvt and that uses t4r in the examples, I am a bit lost trying to feed/create the schema to use it in t4r.
Following the competition example, it uses several workflows and then it keeps doing changes in pandas, so keeping track of the schema is really hard. Would it be possible to get the dataset statistics (cardinality, max, min, categorical or continuous) automatically without the need of being extracting it from the workflows/nvt.dataset()? So we can keep doing changes to the dataset without the limitation of extracting the schema from there.
Maybe there are actually a proper way of getting the schema but I have been a bit lost.
Your contribution

I am open to discussion and thinking a way to automatically get the schema.

From one of T4R notebooks  "Although in this tutorial we are defining the Schema manually, the next NVTabular release is going to generate the schema with appropriate types and tags automatically from the preprocessing workflow, allowing the user to set additional feaure tags if needed."
So I think it will be automated in future.

I have seen that comment, but I was not sure in what version it was commented. Because in v0.7.x I think, you can save the schema doing:
workflow.transform(dataset).to_parquet("./schema", num_partitions=1) or something similar, saves you the schema but I was getting the schema sometimes with min, max and other stats empty. Depending on if it was the first workflow or a workflow that has some previous preprocessing steps with cudf.
I wanted to emphasize the importance of getting the schema automatically as if we want to put this framework into production we cannot be hard-coding a schema if it is a requisite to train models.
Hopefully it will be automated in a near short future as I want to develop a production app with T4R.

@gaceladri you will be able to generate Schema file from NVTabular workflow yes. There is an open PR for that and will be merged soon. We will create also example to use such feature. Hope that helps.

Perfect. My concern was trying to reproduce a more complicated example that the ones that are up-to-date (v0.7.1) on the examples. I was trying to reproduce the example on the competitions repo and I was getting some troubles. The issue was, as you can see in cell [51], after transforming the workflow, @gabrielspmoreira merged a cudf dataframe with the transformed workflow, for example. So, my concern is how, after that merge, for example, we can get the schema from that data frame. Is this solved with this PR @rnyak ? Do you think a way to get the schema from there? as I was not able to get it on 0.7.1. Trying to get the schema from cell [42] that is a data frame coming from a workflow, it gave me a schema with empty statistics.

Perfect. My concern was trying to reproduce a more complicated example that the ones that are up-to-date (v0.7.1) on the examples. I was trying to reproduce the example on the competitions repo and I was getting some troubles. The issue was, as you can see in cell [51], after transforming the workflow, @gabrielspmoreira merged a cudf dataframe with the transformed workflow, for example. So, my concern is how, after that merge, for example, we can get the schema from that data frame. Is this solved with this PR @rnyak ? Do you think a way to get the schema from there? as I was not able to get it on 0.7.1. Trying to get the schema from cell [42] that is a data frame coming from a workflow, it gave me a schema with empty statistics.

@gaceladri for now whatever you do out of an NVTabular workflow will not generate any new/updated schema. Meaning that after that merge, for example, we are not able to get the schema from that data frame unless you do the operations with NVTabular.  You can try to do the merge with NVTabular and test the new schema file maybe? As I wrote above there is an open PR to generate a proper schema, it is not merged yet, but it will be soon.

Hi @gaceladri. As @rnyak mentioned, NVTabular will be able to generate soon a schema compatible with Transformers4Rec. But the schema will correspond exactly to the columns that were output by NVtabular in the parquet files. That means that no other further transformation outside the NVTabular preprocessing workflow will be considered.
You can create your schema manually for Transformers4Rec, so that it matches the columns of your final parquet files. You have two options for that:

Create a protobuf text file like this in a text editor and use Schema().from_json(path) to load it
Instantiate a Schema object and define the schema by code like this example

s = schema.Schema(
        [
            schema.ColumnSchema.create_continuous("con_1"),
            schema.ColumnSchema.create_continuous("con_2_int", is_float=False),
            schema.ColumnSchema.create_categorical("cat_1", 1000),
            schema.ColumnSchema.create_categorical(
                "cat_2", 100, value_count=schema.ValueCount(1, 20)
            ),
        ]
    )

Regarding the task of porting our solution for the Coveo Data Challenge to the new API, I have to say that the solution code used an old internal version of the library before our refactory to create the released PyTorch API.
Furthermore, there are some missing building blocks in the current API that might prevent you to build the exact same architecture used for the competition easily, for example:

Having multiple input sequences (user clicks features and user search events features)
Using  pre-trained embeddings (e.g. the image and text embeddings provided in the dataset) as an input features
Having a post-fusion context added to the Transformers output. But maybe you can create some custom building blocks for those.

We plan to work in the future in an example for the PyTorch API based on the Coveo solution, including its missing building blocks.
Although you could try implementing the missing building blocks, if you are just doing an exercise of reimplementing that architecture with the Transformers4Rec PyTorch API, I would recommend you to focus on the interaction sequence tower (ignoring the search events tower, which is secondary). You can find in the paper reproducibility script a good example on how to use the PyTorch API low-level building blocks to build custom architectures similar to the one for our Coveo dataset solution.

Thank for your answers @gabrielspmoreira & @rnyak . Looking forward to see that PR and to find a solution when you have different source dataframes and merging them into one would crash the memory.


What we heard report

As a public user I want to be notified when the engagement period is over (closed) with the results of the survey so that I can learn about what were the outcomes.

Update cron job to look for published engagements with end dates in the past, Update engagement status to close and send email to users that have answered the survey with a link to the results.

@marieanik we need a template for the "What we heard" email

Hey team! Please add your planning poker estimate with ZenHub @djnunez-aot @jadmsaadaot @saravanpa-aot @VineetBala-AOT


Consider mentioning in the README.md that this plugin will also apply to min-height and max-height

As the issue title explains, I wasn't able to find out if this plugin would apply the same calc() solution to min-height and max-height properties. After searching the repo, I was able to find a test for max-height. But I still needed to know about min-height. So I tested it myself and confirmed that it does apply. I think it would be helpful to mention this in the readme so that other users can potentially save time and effort. Thanks for the great plugin.

Thanks for the issue. Added an example to README for min and max height.
But I think it was clear that the plugin will be applied to any property with vh or vw as units.


⚠ Bofrost.be has degraded performance

In e843a96, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1905 ms

Resolved: Bofrost.be performance has improved in 89451c2 after 27 minutes.


Bump minor version

In order to be pulled in as a dependency for rust-lang/rust#55553, could you please bump the minor version and publish it?
Thanks for your help.

We need to bump to 1.1.1f anyway, so I'll cut a release tonight.

We need to bump to 1.1.1f anyway, so I'll cut a release tonight.

Great! Much appreciated.


Deprecate signTxBytes

We want to be able to remove signTxBytes. For that we need to be sure that tx serialization/deserialization roundtrips for finalized transactions.
After the change we should be able to modify the finalized tx as CTL data and serialize it back.

Closed by #573


Day of the week effect for EpiNow2

https://github.com/epiforecasts/nowcasting.example/blob/7cb3cb40e02c64521de0b366c3c74505e7f10856/inst/reports/est_trunc_epinow2.Rmd#L192
In this example there is little evidence of a day of the week effect. To improve performance here it would make sense to not use one but likely want to note it is in general a good idea for data by report date.

Scratch this. As the data is simulated from reported cases there is plenty of evidence for a dow effect.


Fix for #897

Fix for #897
os.homedir was added in Node v2.3.0, fallback values of process.env.HOME and process.env.USERPROFILE works for POSIX and Windows

This looks good to me, but I'd like a second person to test this on Windows (I assume you did?) just to be sure (and to ensure there are no lurking second bugs hiding behind the one you fixed).

Works on my windows

Yes, I checked both os.homedir! and process.env.USERPROFILE. Windows is my main platform, although I do tests and builds on a virtual Ubuntu machine.


[call_tf] Fix multi-platform lowering

call_tf has per-platform lowering because the lowering
of the called TF function may depend on the platform. When
doing multi-platform lowering this means that we lower
call_tf several times and wrap the lowerings with a
conditional. This results in an assertion failure
in add_to_call_tf_concrete_function_list, because we
are attempting to add the same function multiple times.
Here we remove the assertion (afaik, it is Ok to add
multiple functions with the same name, because all
we care about is the index of the called function in
the list). We also reuse the existing function if
we are adding an identical one.
We add tests for call_tf with multi-platform lowering

@maxwillzq PTAL

@superbobry PTAL


dupe icons on status update

Can you elaborate on what this is about?

@orta @ashfurrow this is on the live auction view the icons related to the bid status we're duplicate and overlapping one another. I don't have a screen shot because we weren't testing on my device.

This happens when a state changes on a live lot, this should be fixed now 👍


🐞 Replace Moment by date-fns

Description 📄

Moment.js is deprecated and no longer being maintained by their owners (more information here). Its own documentation recommend the usage of another date library, and cites the date-fns as one alternative.
The date-fns is a great and well-maintained library and as a similar API. Because of that, this PR replaces the moment by the date-fns and refactor some code for a better reading experience.

[x] Replace the moment by date-fns.
[x] Change variable names to become more readable.

This PR also closes the issue #543, opened by @frgiovanna.
Platforms 📲

[ ] Web
[ ] Mobile

Type of change 🔍

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

How Has This Been Tested? 🧪

[Enter the tips to test this PR]

[x] Unit Test
[x] Snapshot Test

Checklist: 🔍

[x] My code follows the contribution guide of this project Contributing Guide
[ ] Layout matches design prototype: FIGMA
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@rafaelcoleta  I've looked at all the code! Everything is OK for me to merge


all: support Go1.9 with type alias Buffer instead of strings.Builder

strings.Builder was introduced in Go1.10 but this package
uses it for efficiency.
Luckily we've got type aliases, build constraints as well
as in Go1.12, we have the gcflag "-lang" that we can
use to test out compiler versions.
This change adds a Buffer type in syntax, which is:

type Buffer = bytes.Buffer on Go1.9 and below
type Buffer = strings.Builder on Go1.10 and above

I verified the builds by doing
go test -v -gcflags="-lang=go1.9 ./...
go test -v -gcflags="-lang=go1.10 ./...

Fixes #1

/cc @rsc

Thanks for the CL; I decided to just use bytes.Buffer instead of needing build tags, though.

Cool, although perhaps please document the usage of "bytes.Buffer to preserve Go1.9 compatibility"  I am progressively seeing folks submit CLs to replace bytes.Buffer, just as we had initially here :)

I hope that by the time someone cares enough to send me a CL about this package, strings.Builder will be OK to use. We should not need to keep Go 1.9 around for much longer I hope!

In deed! Thanks for rolling out this package otherwise.

Note that using -gcflags=-lang=go1.9 has no effect on library usage. You have to run a different toolchain (the actual Go 1.9).


REST API Specification

I want to port this functionality to Python;
Is there a Swagger or some API Endpoint specifications highlighting what are the API Request-Response parameters ?

Second this (not Python, though). Can we please get the API specification?

Second this (not Python, though). Can we please get the API specification?


Request: allow disabling of Red Canary banner on binary execution

When executing the created binary, a massive Red Canary banner is output every time, taking up well over half my screen on a large monitor. It would be nice if we could have the option during binary creation to disable this to save screen space on execution.

@Marshall-Hallenbeck How does that look to you? Pull-request linked.

@rc-grey Looks great, thanks! Just tested it as well.


Undefined method color? for TTY::Screen::Class

Hello,
I have a code complaining as soon as I call prompt = TTY::Prompt.new.
Here is the trace:
avril14th@avril14th:~/src/white2$ rake admin:organization:create
rake aborted!
NoMethodError: undefined method `color?' for TTY::Screen:Class
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/pastel-0.5.2/lib/pastel/color.rb:24:in `block in initialize'
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/pastel-0.5.2/lib/pastel/color.rb:24:in `fetch'
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/pastel-0.5.2/lib/pastel/color.rb:24:in `initialize'
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/pastel-0.5.2/lib/pastel.rb:32:in `new'
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/pastel-0.5.2/lib/pastel.rb:32:in `new'
/home/avril14th/.rvm/gems/ruby-2.2.3/gems/tty-prompt-0.3.0/lib/tty/prompt.rb:57:in `initialize'
/home/avril14th/src/white2/lib/tasks/admin.rake:9:in `new'
/home/avril14th/src/white2/lib/tasks/admin.rake:9:in `block (3 levels) in <top (required)>'

I use tty-prompt 0.30 in a Rails 4.2.5 app.

Closed. Moved question to proper repository (https://github.com/peter-murach/pastel/issues/12)

Moved to proper repository (https://github.com/peter-murach/pastel/issues/12).

Hi Olivier, sorry for this frustrating start. My bad, I have specified pastel dependencies wrongly by only restricting versions to minor instead of patch level. And virtually couple days ago I have released new tty-screen dep v0.5.0 which I thought will be fine but pastel specified v0.4 only which got happily upgraded - duhhh. I have rectified that and released pastel v0.5.3 that has the fixed dependencies versions. Please install again and all should be fine - it is for me.

Hey @peter-murach, no worries. :) Your gems are so cool man. Thank you so much. Cheers.


Utilising Node Clustering to scale Server Side Rendering

We're running this package under heavy load in production and Node's Server Side Rendering cannot keep up to the number of requests coming in. We're experiencing "request pile-up" as React's RenderToString function blocks Node's event loop from handling more requests. Our server's response times are terrible when SSR is enabled.
I found an article from AirBnB describing the exact same problem (and their solution):
https://medium.com/airbnb-engineering/operationalizing-node-js-for-server-side-rendering-c5ba718acfc9
I'm wonder if this package has some configuration (that I may have missed) to enable Node Clustering and/or some type of load balancing

Thanks for contacting us. We're closing this issue as this doesn't align with our long-term plans in this area. You can read more details about our vision for this area at https://github.com/aspnet/AspNetCore/issues/12890.


Should be able to gather confd rendered templates from a running calico/node

[arguably a calicoctl issue since it's related to the calicoctl node diags, but I suspect a solution would require a change in calicoctl and in calico/node.]
Expected Behavior
It would be useful if we had a supported mechanism for gathering the confd-rendered bird templates from a running calico/node.
Current Behavior
We don't have a way other than exec-ing in to the container.
Possible Solution
Perhaps have a trigger event that causes each template to be written out to the logs.
Context
It makes diagnosing anything IPIP/BGP related quite difficult.
Your Environment
We should be able to do this across most supported orchestrators.

I think you can simply do this with a docker cp command: https://docs.docker.com/engine/reference/commandline/cp/


Create tests for AGlobeAwareDefaultPawn

These tests would be the first iteration and need to test base functionality.
Of particular interest are the FlyToXXXX functions, which are time-based. Ideally, we would be able to run time-based tests, but not wait in real time. (maybe override game time inside the test)
Piggyback on the new testing framework introduced in #1109
Relates to latest rework in this class in #1120

Might be some useful testing code in this old draft PR, #548

@kring , do you think this is good enough to call done from your latest PR? #1149
(introduction of Source/CesiumRuntime/Private/Tests/GlobeAwareDefaultPawn.spec.cpp)

I only added one test for the very specific issue I ran into. I think it may be worthwhile to add some more general tests of the functionality.


Add support for reading TDatime

Should this be linked in with
https://github.com/scikit-hep/uproot4/blob/c1c95c0ad6b6f1fe830ed7187a71420d5fff913b/src/uproot/_util.py#L814-L839
which convert ROOT's "datime" integers into Python datetime objects?

Should this be linked in with

For sure, but in what way? Modify during read, or in Model.postprocess or add as a method?

For sure, but in what way? Modify during read, or in Model.postprocess or add as a method?

The canonical way would be to add a src/behaviors/TDatime.py containing a TDatime class and have this Model_TDatime inherit from that behavior. The behavior would then define a
    def to_datetime(self):
        return uproot._util.code_to_datetime(self._members["fDatime"])

method for Model_TDatime to inherit.
That's how the methods are usually named: histograms have to_numpy(), to_hist() (methods, not properties, to allow for future parameterization). The goal is not to rewrite the functionality of ROOT in Uproot, but to export objects to their Python equivalents (which generally provide the functionality of ROOT by themselves; for instance, datetime has all the methods for getting year, day, hours, isoformat, etc.).

scikit-hep-testdata 0.4.6 is now available. Tests that are looking for uproot-issue-407.root should find it.

Could someone trigger the tests? I believe this is ready.

Sorry, I didn't realize that it was being held up.


Implement StringValue func for each type.

Clouse due to this fix: https://github.com/Mitu217/tamate/pull/100


Corrupted vocab index when running the transformer script

Description
Running the default command and script for transformer training results in a warning of corrupted index, which is misleading for users (whether the script still works) and should be fixed.
Error Message
2019-10-21 04:21:20,809 - root - Namespace(average_checkpoint=False, average_start=5, batch_size=2700, beam_size=4, bleu='13a', bucket_ratio=0.0, bucket_scheme='exp', dataset='WMT2014BPE', dropout=0.1, epochs=30, epsilon=0.1, full=False, gpus='0,1,2,3,4,5,6,7', hidden_size=2048, log_interval=1, lp_alpha=0.6, lp_k=5, lr=2.0, magnitude=3.0, num_accumulated=16, num_averages=5, num_buckets=20, num_heads=8, num_layers=6, num_units=512, optimizer='adam', save_dir='transformer_en_de_u512', scaled=True, src_lang='en', src_max_len=-1, test_batch_size=256, tgt_lang='de', tgt_max_len=-1, warmup_steps=4000.0)
/home/ubuntu/benchmark/gluon-nlp/src/gluonnlp/vocab/vocab.py:582: UserWarning: Detected a corrupted index in the deserialize vocabulary. For versions before GluonNLP v0.7 the index is corrupted by specifying the same token for different special purposes, for example eos_token == padding_token. Deserializing the vocabulary nevertheless.
  'Detected a corrupted index in the deserialize vocabulary. '

To Reproduce
MXNET_GPU_MEM_POOL_TYPE=Round python train_transformer.py --dataset WMT2014BPE                           --src_lang en --tgt_lang de --batch_size 2700                           --optimizer adam --num_accumulated 16 --lr 2.0 --warmup_steps 4000                           --save_dir transformer_en_de_u512 --epochs 30 --gpus 0,1,2,3,4,5,6,7 --scaled                           --average_start 5 --num_buckets 20 --bucket_scheme exp --bleu 13a --log_interval 1
All Logs will be saved to transformer_en_de_u512/train_transformer.log

Steps to reproduce
(Paste the commands you ran that produced the error.)

run the command above

What have you tried to solve it?

Environment
gluonnlp commit = 76ca4d7

Running assert 1 == src_vocab.token_to_idx[src_vocab.idx_to_token[1]] you will get an assertionerror. The loaded vocabulary does not exhibit the properties of a gluonnlp.Vocab.
That's why the warning is printed.

@szhengac shall we change the downloaded vocab?

I remember that the vocab in wmt14en-de does not specify the eos and pad tokens.

Changing the downloaded vocab will change the indices mapping, as there is currently one invalid token at the beginning of the idx_to_token. So the embedding weights in the model files also need an update.


Bug fixed in cn-cbor library

When encoding cn_cbor structure before writing any chunk of bytes into
buffer, library ensures that there is enough space to write current
chunk. It is done by the following inequality: offset+length >= size.
If inequality is true, then library decides that there is no enough space.
However, if offset+length == size then there is still enough space to
write a chunk of size length.

This same change is also in #25 and the same problem also fixed by #49.


chore(main): release 1.34.0

:robot: I have created a release beep boop
1.34.0 (2024-09-18)
Features

add option to scalar ui (7fa1ec9)
add utils to presentation layer and update crud handler (7d23bdb)

Bug Fixes

check if object has no key and imrove type SearchModel (1751b1f)

Styles

remove linebreak style (2a84db9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Andesite-Lab/Core/releases/tag/v1.34.0 :sunflower:


DoublyLinkedList.java

improved code with insertion at the end , beginning ,and at any position . Also I have added code for deletion the first and last node.

PR Checklist:

[ ] My submission is formatted according to the guidelines in the contributing guide
[ ] My addition is on refer on the language README.md file
[ ] My addition does not have a spelling problem
[ ] My submission has a proper and user-friendly description of the algorithm
[ ] My submission has the time complexity of the algorithm
[ ] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hi @himanshu-hiware,
This algorithm is duplicated please check this pull request #125, and if you have enhancement for it, you could open a new pull request.


[rag eval] add claims counters

update claim counter page to have 2 sections w/ 3 counters each:

statistical claims

total claims
false claims
unique tables

inferred claims

total claims
false claims
unsubstantiated claims

thanks for the review!


Geometric demo does not work until click

http://elementqueries.com/demos/geometric.html

The error is on this line:
height: eval("scrollWidth")px;
It initially evaluates as 0 until you click in the body somewhere, or resize the window.

Hi @alokinsoft! Thanks for pointing this out :D
This seems to be something that has happened when we added EQCSS.throttle()
For now, this demo can be fixed by adding:
EQCSS.domReady(function(){
  EQCSS.apply();
});

It's supposed to run EQCSS.throttle() now instead but it seems to be running the first time perhaps before it should… I'll keep investigating, but I'll fix the demos right away!


Update README.md

Fix what is probably a spelling in the documentation

Sorry for taking so long, merged.


[beta][UI][UX] the modal for "completed challenges"

[beta] the modal for "completed challenges"
Also needs a Night Mode "refresh", should be more vibrant, the pop-up window needs to differentiate itself form the html page
Without Modal:

With Modal:

Example for a refreshed Night Mode version for the modal:

@tommygebru Not sure exactly what you mean... are you suggesting the night mode modal should look like the photo directly above? ☝
The issue with that, is it is too bright, and does not really fit with the night mode theme. In fact, this was very recently changed from exactly this to what it is now: #12558 / #12556

@no-stack-dub-sack Here is one that looks nice i think 👍

@tommygebru hmmm, let's ask some other folks what they think. I'm ok with going with whatever everyone seems to think is the right move. I think the white check looks nice, but the purpley-grey does not seem to match any of the other nightmode colors...
@systimotic you were one of the reviewers for the above mentioned PR that changed the style of the  nightmode modal to what it currently is - what do you think?

@no-stack-dub-sack
If you are curious about the background change, it would make more sense if you checkout #12953
also I put in a PR for the design-style-guide here to reflect the more "vibrant" night mode
https://github.com/freeCodeCamp/design-style-guide/pull/14
I think that this night mode will be more engaging to the campers
as far as a high-contrast color pallete, I believe the best solution comes in the form of a chrome extension and i also made an issue for that as well #12955

@tommygebru Cool, yeah, I just checked out #12953 and I'm not sure I would prefer these colors. However, I'm not a designer or a pro UX guy by any means, so once some other opinions get registered, we can see where it goes!

I (personally) like the proposed modal provided by @tommygebru above but I would change the white check to a very light grey since night mode is supposed to be "less bright" overall. Also, I would recommend we connect any of the recent issues related to high-contrast to https://github.com/freeCodeCamp/freeCodeCamp/issues/8845 for use in a high-contrast mode for all of freeCodeCamp, not just the editor. There would then be two modes: high-contrast and night-mode. Thoughts on this @tommygebru ?

@dhcodes thanks for sharing, I think its great that FCC is willing to design a high-contrast mode, however I found a greater solution with a Google Accessibility extension that will change any webpage on a browser to a custom color scheme to help all visually impaired or sensitive users.
High Contrast - https://chrome.google.com/webstore/detail/high-contrast/djcfdncoelnlbldjfhinnjlhdjlikmph?hl=en
Perhaps we should include this as a button next to Night Mode's button on Freecodecamp?

@raisedadead If there is a concern that the colors do not deserve a branch or pagination on Freecodecamp's design-style-guide. Then I purpose at the very least we should expand on either Freecodecamps Primary or Secondary color palette to include Thunder.
Also - I have not seen Freecodecamp utilize all of Freecodecamps colors in Primary nor Secondary and I am curious if we will remove some colors from both pages.
As for the white icon on the modal, I think it should stay, it is a very minimal amount of white color, and matches the rest of the Night Mode color scheme, white is for fonts and characters.

I think we can discuss more about adding the existing colors to the site's UI in ways that it enhances the UX which I can see this issue aims to address beautifully.
Sorry if I missed it, what is Thunder again?

Yes- Thunder is a new color proposal
I will make a new pull request to add it as a primary color to the design style guide
Also - Thunder shares a familiar color pathway to Freecodecamps gitter community

@tommygebru @dhcodes @raisedadead I think what all of these discussions (#12953, #12852, #8845, etc.) really suggest, is that we desperately need a standardization of night mode colors somewhere, whether it be a part of the style guide or not. And to decide on high-contrast mode.
My only issue would with the above proposed modal would be that the Thunder color doesn't match any of the other current night mode colors, so if we did adopt it, perhaps we should adopt it in other places as well as in @tommygebru's suggestion from here, which adopts it in the background as well.

Even though I've gotten used to and really like the current night mode color palette, I can see how it might also be seen as monotone. So if it does get changed, I think it's important that it remains distinguishably freeCodeCamp.
As for high contrast mode, I really like the idea of the of the Chrome Extension because it is so customizable, but I believe (and I could be wrong) that we are trying to do all of this as independent of things like browser extensions as possible in order to really keep with accessibility principles, because then any users who need high contrast mode that don't prefer Chrome would be out of luck. So in this case, while I love the extension, I think a built in mode is ultimately the better solution. Perhaps a wiki mention for this particular extension so that campers are aware of it's existence?
All in all I see three major points here, and perhaps we can come up with some way to get a larger discussion going to decide on what should be decided and how:

Nightmode color palette changes and standardization
3rd mode - high contrast mode
How and where to dictate and standardize both for future contributors

Again, thanks @tommygebru for your critical thinking on all of this! Looking forward to seeing what we can all come up with!

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (115/100 (114%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60274 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx5P-0003ec-Te
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:19:00 -0400
Received: from o10.sgmail.github.com ([<IP_ADDRESS>]:44718)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx5H-0001z4-FS
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:18:51 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=/eHgkkwlHH8xqAcBkfWR5rt9zHU=; b=Iag6re5moJFnm1Px
7qgQatBkWg6MdASzJ5Y564SZZTCUrqDcH20vLoFJ7ZqR08qFdV/EKkopkmcX+Jv/
5O0J0Ap+kbAVOD5f9uEcDCK/Jt0jXCxrV+toEcASZlWgmg3ykMIGdCpkg77rQrOF
qM6ksUdGi3uqnu5ctAgGnRORpzE=
Received: by filter0464p1las1.sendgrid.net with SMTP id filter0464p1las1-1653-59AA06FA-1
2017-09-02 01:18:50.207497109 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id ulj8JjCUR1K5evb7yVGVLA
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:18:50.181 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:18:50 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] [beta][UI][UX] the modal for
"completed challenges" (#12952)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa0642bc68d_1cb5f3ff80b451c381544ab";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCjUx56jSpUWqODtBzTvYP7vcsNhQks5seKxCgaJpZM4Lw15J
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: 83UmH9Yz2HjU1qKK7JE10vR6ZA73mzRCr3l9ny8S/eHd6XYQ4KlWqezSliHGvRPbvruTP9gCjIh0tc
GCWMzYNdFszwiE/WtET8PDImR0VxaK1+0s2t5fSIax+8exXSNE9hRa7KDexsCeuoNdC1/iNbPCROPK
wip+S/+Q8ZEsedspnTBkfKyeRoZQyl8k5HA1DKGpkb8SUrRB4/Jpt7z711rX6kLu/JW3aKJk/hlBkI
g=
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx5H-0001z4-FS
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=1.586, required 10, AWL -3.12, BAYES_00 -1.90,
HTML_IMAGE_ONLY_24 1.62, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
PYZOR_CHECK 6.50, SPF_PASS -0.00, T_RP_MATCHES_RCVD -0.01,
URIBL_BLOCKED 0.00)
X-Spam-Level: *
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_59aa0642bc68d_1cb5f3ff80b451c381544ab
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #12952.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/12952#event-1232190142
----==_mimepart_59aa0642bc68d_1cb5f3ff80b451c381544ab
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #12952.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Closed #12952."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/12952#event-1232190142"}}}
----==_mimepart_59aa0642bc68d_1cb5f3ff80b451c381544ab--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (117/100 (117%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mail-oi0-f42.google.com ([<IP_ADDRESS>]:33836)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx62-003t9x-Vv
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:49:50 +0530
Received: by mail-oi0-f42.google.com with SMTP id w10so13913875oie.1
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:19:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature:date
:from:reply-to:to:cc:message-id:in-reply-to:references:subject
:mime-version:content-transfer-encoding:precedence:list-id
:list-archive:list-post:list-unsubscribe;
bh=NetV9NJQRstMKtkD1TRoAFxIuYyyqvYy15DUrlVV1pM=;
b=D1duW5uF0Od4VcAyTG3Mc5Rh0AlbobB/nH1tqE+C2SKucv6kdP/VYVzji/HWKTL1M0
XIjWJ82OAEAf8CDs4dSPJp8fBGVU7uH8EIOeo9gikCaPaBMJh70udT7GXltjM14o1YaD
wsvGSVNxFyyHweujDaPdmlTJSCq8icStJdXr4DSLeEFTRXLOyeHjBUy9qBIuPKT3r/OI
2DtxeLHupxEI6C7uahCRfiTzNuH4iK40qemNdXVwLU08/Vy09fOy5Lti9y7JId0i341E
uuW577X4Rzg5VPc/1IyVGLwLvLftYzIDyBWgtRxvD9aVpICu9B4o1nvl0oU9gD/a53ZZ
t4ow==
X-Gm-Message-State: AHPjjUjscCgx+oEOyAd+CV7rycPACiHeeAVvKwcbBeq8aVOvA4JlrbmM
6mxtQZYMUPGgxTsZ3WO8euRhqNz0pWqI2HlXkRjnCQ==
X-Received: by <IP_ADDRESS> with SMTP id q123mr3398924oic.16.1504315136452;
Fri, 01 Sep 2017 18:18:56 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1354135ofe;
Fri, 1 Sep 2017 18:18:55 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb7uJRFvJOB1TLWz/vrbmZSoMt9cZ6XsAVTLRtvExKQL4R4F9gSmVAmNqfGdpcKIMN6lYWKj
X-Received: by <IP_ADDRESS> with SMTP id t124mr3423194iod.158.1504315135748;
Fri, 01 Sep 2017 18:18:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504315135; cv=none;
d=google.com; s=arc-20160816;
b=Z7qkw45Y4RlDiYrO4DsRfOBk49W6xSPJbnEc2IFvoG2VwVWoAxOKJtOW3wx2vG1LkF
JHkqm2KUdZGVLoUWF9gnhnxVh37Q+YrBE3zBE51SSFI6QU/cq62rvSpi9bqG/96MjKT6
evN8ZtoWujf6qQ0WYMCkuJwMvd2UZZJQAb+pXoGRAv1xhkdKuHdw6wd+BTuBWT+e9ZSL
j6ULSF23/vgtsVRpI+yLL+dy1FYpIQZitoXtMZw/vkfS4D2gvMjdXt8YCCm8rWsiSSNt
5PUm55UJp8fC6KPmVkpRibztzXgLGY/sC3VmeHeFCwT249zBNszpBp9YxmqJI8e9unH3
D80A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:dkim-signature:arc-authentication-results;
bh=NetV9NJQRstMKtkD1TRoAFxIuYyyqvYy15DUrlVV1pM=;
b=t/mmy7KAfMsOzDi/IaPKOJnqvoxVVeMzp2lGYg1REGn8pA2qcJEqnxu/H7LBWVMzcc
wkhlIg1rXRPxFPuXt0pHI9/PJ8VGrACelkcC+p3dYyvqe7tmTKhBqkdZHzVlhuYM79Ls
mQMuDTAFF4NvwjorYER21o5gZZ05Az9OU8CKMUOq1fN2YTxJ9cSM2g/+zYqJyHAMauJr
juQ3l09zZHYMBH7cPgMDwCyF7aU7mHV5gWZu7nYXRMrL0SRCev7qAWe0FImsQnuAvSpp
XuVoLs/LzLGnHv8kuhIPR8ymxb4vy/hLJ/pKqQzfrBepOuUy5Tj/kkqedBhq77j2m0U4
yVBw==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=i8mRY98X;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=hTrEhJBH;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from o1.sgmail.github.com (o1.sgmail.github.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id c6si1385324ite.56.2<IP_ADDRESS>.18.55
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:18:55 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=i8mRY98X;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=hTrEhJBH;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=wGusbfb5vkUS2H44Ad0vMGtCivo=; b=i8mRY98X0eG4IYT/
GUIkJfKj741+tnYZ8do/ERl0V4ruxs8AfW55w9129I1qTa5XxL+d9m4lv7Vk3tt3
NXIiKUYR0BaMl7ouDxr7xlb6ZJ9uNpHtyATXUt/IUlCX4O6/cgeVC+URrC6H/RZF
rs7Da6soiAkzQzfttlTSR+uVawA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.info;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe:x-feedback-id;
s=smtpapi; bh=wGusbfb5vkUS2H44Ad0vMGtCivo=; b=hTrEhJBHH7hwaSh/yv
jKq9qgz0qri2OlZdOYJyumT6kCSUV9FeN5RY1rw4534btQBDx0yK37x4PU+hOTOG
SWzES5Un/KhhxYdNUq8kwDgDXi12mV/NhNpwYY9pqqSPJQFXIkt2Hv3Dpfqpm7nq
0zb8smoetatBVHdGi1A6G32Is=
Received: by filter0968p1mdw1.sendgrid.net with SMTP id filter0968p1mdw1-30823-59AA06FF-28
2017-09-02 01:18:55.646307324 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0025p1mdw1.sendgrid.net (SG) with ESMTP id rcQGIpQoRkygaji4qzFR7A
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:18:55.673 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:18:55 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] [beta][UI][UX] the modal for
"completed challenges" (#12952)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa064b2beb7_1cb5f3ff80b451c381766f";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: pawan-mehta
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AM9SCJv47LHXtoHtM0zWQ4PY0JT8UNBrks5seKxLgaJpZM4Lw15J
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: OpfRgdkK9YQWPKIAgM5UQUoN56mCdWNmGtfFv0Mnvk0phsIPlUB+xDE8WzY6c2Wx/YFPPmebmEOyvv
cBsZ0GLxq+S8DIxLIJacuHSgK+1R0gqQUwEIspewm9kRDDF7OjdjctKvyLDHsRkf5LSX4Z6O+UxQim
fFwUR7UDB2ilEBzaJGclrYCr4/Ye7Tfzrebc0rx4SMOIYMZK7km0c9fMkTu/vTRwu1aUzuXZQBmR1/
s=
X-Feedback-ID: 848413:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:SG
X-Spam-Status: No, score=1.7
X-Spam-Score: 17
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "server14.hostingraja.in",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Closed #12952. -- You are receiving this because you are subscribed
to this thread. Reply to this email directly or view it on GitHub: https://github.com/freeCodeCamp/freeCodeCamp/issues/12952#event-1232190142
[...]
Content analysis details:   (1.7 points, 5.0 required)
pts rule name              description

0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: sendgrid.info]
0.5 RCVD_IN_SORBS_SPAM     RBL: SORBS: sender is a spam source
[<IP_ADDRESS> listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
[<IP_ADDRESS> listed in wl.mailspike.net]
0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
domains are different
0.0 T_SPF_HELO_TEMPERROR   SPF: test of HELO record failed (temperror)
-0.0 SPF_PASS               SPF: sender matches SPF record
0.0 HTML_MESSAGE           BODY: HTML included in message
1.3 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO
----==_mimepart_59aa064b2beb7_1cb5f3ff80b451c381766f
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #12952.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/12952#event-1232190142
----==_mimepart_59aa064b2beb7_1cb5f3ff80b451c381766f
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #12952.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_59aa064b2beb7_1cb5f3ff80b451c381766f--


could use right-now for high performance timing

will choose the best method for node / browser
https://github.com/hughsk/right-now

Interesting didn't know about performance.now. +new Date is a shim I assume.
Thanks for the tip.


feat(gateway): improve error handling

closes https://axelarnetwork.atlassian.net/browse/AXE-6040
currently waiting on auth-verifier tests

Codecov Report
Attention: Patch coverage is 97.10983% with 5 lines in your changes missing coverage. Please review.

Project coverage is 98.97%. Comparing base (d330956) to head (72ef054).

Files with missing lines
Patch %
Lines

contracts/axelar-gateway/src/auth.rs
89.13%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   98.48%   98.97%   +0.48%
==========================================
  Files          24       23       -1
  Lines        1788     1858      +70
==========================================
+ Hits         1761     1839      +78
+ Misses         27       19       -8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Liveness and Readiness Probes do not exist in Helm chart templates

Currently the KEDA Helm chart does not implement the liveness and readiness probes that are seen in the vanilla KEDA YAMLs. Any plans to support this in the Helm chart for v2 final?

Thanks for submitting the PR @jasondemps1!


Fix return type

Changed return type of create_loop_state from None to LoopState. Moved function to end of file so LoopState class is already defined when using type annotation.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

@@           Coverage Diff           @@
##           develop     #24   +/-   ##
=======================================
  Coverage     81.6%   81.6%
=======================================
  Files           59      59
  Lines         1392    1392
  Branches       138     138
=======================================
  Hits          1136    1136
  Misses         226     226
  Partials        30      30

Impacted Files
Coverage Δ

emukit/core/loop/loop_state.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


arch: arc: fix the bug in _firq_enter

If firq is a nest interrupt, _firq_enter will do
some operations to get the sp of interruptted stack to
make sure the firq and normal firq share the same interrupt
stack. In these operations, push and pop are required to free
some regs.

In ARC, pop reg ==> sp=sp-4; *sp= b; The original codes have bug
which will crash the interruptted stack's content. This commit fixes
this bug

Signed-off-by: Wayne Ren<EMAIL_ADDRESS>Fixes #19363

Hi @abrodkin
Thanks for your feedback. It can be optimized as you said.
I will make a force push later
Thanks
Wayne
From: Alexey Brodkin<EMAIL_ADDRESS>Sent: 2019年9月27日 15:32
To: zephyrproject-rtos/zephyr<EMAIL_ADDRESS>Cc: Wayne Ren<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [zephyrproject-rtos/zephyr] arch: arc: fix the bug in _firq_enter (#19364)
@abrodkin approved this pull request.
I'd simplify commit message as the first bullet makes not that much sense in the context of the fix.
Here we just recover semantics of push/pop operations. Well with one significant difference - we're dealing with special ARC "Auxiliary" (AUX) registers which are located in a completely different address space and so normal load/store instructions (LD, ST and essentially POP/PUSH which are just aliases for LD.AB a, [SP,+4]/ST.AW c,[SP,-4]). And so we use special AUX load/store (LR/SR) instructions and we need to decrement SP before storing as well as increment SP after loading.

In arch/arc/core/fast_irq.Shttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zephyrproject-2Drtos_zephyr_pull_19364-23discussion-5Fr328941790&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=4Vrxz309sfdFpUSh2zDpilykSQBb1ZjPraiDgftH43A&s=7mIA-FkOxMHpmty7ciZjxddgQN2k1bvSK4bis7o_2Fc&e=:

  st ilink, [sp, -4]

  lr ilink, [_ARC_V2_USER_SP]

  /* push _ARC_V2_USER_SP  */

  st ilink, [sp, -8]

  /* sp here is the sp of interrupted context */

  sr sp, [_ARC_V2_USER_SP]

While we're at it one other question: don't we want to modify SP value as well? I mean do exactly what PUSH would do as you mention in the commit message: sp=sp-4; *sp= b;?
Indeed that's only required if we may switch to another process right in this IRQ handler and later return to interrupted context. And in any case that will add clarity and simplify understanding... especially if we use macros for saving/restoring of AUX regs similarly to Linux' PUSHAX()/POPAX(), see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arc/include/asm/entry.h#n37https://urldefense.proofpoint.com/v2/url?u=https-3A__git.kernel.org_pub_scm_linux_kernel_git_torvalds_linux.git_tree_arch_arc_include_asm_entry.h-23n37&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=4Vrxz309sfdFpUSh2zDpilykSQBb1ZjPraiDgftH43A&s=9nyS-aP9_3VafZZp03s6bMXWcCzh15uxWTvD9TMTm-A&e=.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zephyrproject-2Drtos_zephyr_pull_19364-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DABIH2O6AKZBRKHGR34HMODDQLWZG7A5CNFSM4I2JUWSKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCGEGF6I-23pullrequestreview-2D294150905&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=4Vrxz309sfdFpUSh2zDpilykSQBb1ZjPraiDgftH43A&s=geIuH8aWxO5fGB1M_MXUaCAbZK9O7wSUSjR8hhrvO8Q&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABIH2O64QA5RG75C4VOHZ2DQLWZG7ANCNFSM4I2JUWSA&d=DwMCaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=uIRv5OnfaYG5_34mbrNlSdByDrbpAfi15TvQ5YKDOG8&m=4Vrxz309sfdFpUSh2zDpilykSQBb1ZjPraiDgftH43A&s=CrmNd8R1ZvPCuj-9hXVSU-oQbk6y3KKzumikIwtE5bQ&e=.


Slug command

README says to create a pull request against the development branch, but no such branch exist. So I picked master.

I'll update the README after this to point merge requests against master ... thanks!
I see that the Laravel 5.1 way of declaring command arguments and options is different, but I assume the "old" way works still. I may eventually need to branch out a 5.x and 5.1 version, I guess ... but don't worry about that for now.
However, can you please write a test for this as well? Happy to merge after that!

Sorry I never merged this earlier.  It's a good suggestion!
Any chance I can get you to resubmit the merge against the new 4.0 branch?  And add a test, please!

I tried to. But I had some problems installing the framework. I don't do PHP anymore. I could write something up without running it, but obviously I cannot guarantee it will work.


feat: make component generation work in annotation-less mode

@iocanel I do have a question regarding the co-existence of both annotations and properties: which takes the priority if both are present and, possibly, contradictory?

which takes the priority if both are present and, possibly, contradictory?

@metacosm @iocanel @aureamunoz @geoand
Can we follow the rules of SpringBoot, Spring where parameters of an annotation can only be changed using application.properties|yaml file ?
Spring Example:
@SpringBootApplication
--> Name defined using the following field
spring.application.name=my-spring-application

Component Example
@ComponentApplication
--> Name of application overriding what we calculate -> artifactId or gradle description
dekorate.component.name=my-fruit-client
dekorate.component.exposeservice=true

Remarks:

That means that we will not pass additional parameters to the Java Annotation !!
@CompositeApplication should be renamed to @ComponentApplication

which takes the priority if both are present and, possibly, contradictory?

@metacosm @iocanel @aureamunoz @geoand
Can we follow the rules of SpringBoot, Spring where parameters of an annotation can only be changed using application.properties|yaml file ?
Spring Example:
@SpringBootApplication
--> Name defined using the following field
spring.application.name=my-spring-application

Not sure I understand, can you explain a little more please?

Not sure I understand, can you explain a little more please?

This is simple. We currently for the @CompositeApplication annotation allows to change the fields name and exposeService, DeploymentMode, ... within the annotation
@CompositeApplication(
    name = "fruit-client-sb",
    exposeService = true
)

I propose as Spring is doing for many of their annotations, that we only provide an empty annotation and that we use the application.properties|yaml file to override the parameters calculated or to add additional infos.
Example
@CompositeApplication // Empty Java Annotation
--> what we calculate or let the user to modify the fields within the file
dekorate:
   component:
     name: my-favorite-app // user is changing the name
     exposervice: false // default is true
     env:
     - name: "foo"
        value: "bar"

We could also imagine to completely remove the @ServiceCatalog, @Link annotations as they will be calculated/created by the tools such as kreate and most of the developers will never need to create them manually
Example
@Link(
    name = "link-to-fruit-backend",
    componentName = "fruit-client-sb",
    kind = Kind.Env,
    envVars = @Env(
        name = "ENDPOINT_BACKEND",
        value = "http://fruit-backend-sb:8080/api/fruits"
    )
)

could be replaced by what the tool will add to the application.properties file
dekorate:
    link:
      name: "link-to-fruit-backend"
      componentName: "fruit-client-sb"
      kind: env
      env:
        - name: "ENDPOINT_BACKEND"
           value: "http://fruit-backend-sb:8080/api/fruits"

Thanks for the explanation.
I haven't really followed the discussions closely, but I don't see why the ability to configure via annotations should be removed for some of the functionality and be properties only.
Also, in my opinion @metacosm properties should take precedence over annotations

Also, in my opinion @metacosm properties should take precedence over annotations

Based on my examples, this is the rule that implicitly I suggest too ;-) (properties should take precedence over annotations)

I agree as well that properties should take the precedence over annotations since it allows for overriding things without having to re-build the project (and it allows for non-Java, third-party tools to more easily interact with ap4k).

Yes, I agree also with all exposed arguments about priority of properties.

Generally, externalized configuration takes precedence over what's
configured in code.
And we should do the same.
On Fri, Jun 14, 2019, 10:26 Aurea Muñoz Hernández<EMAIL_ADDRESS>wrote:

Yes, I agree also with all exposed arguments about priority of properties.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ap4k/ap4k/pull/229?email_source=notifications&email_token=AADCEWFJRQPU3FFT3CKRNVLP2NBYVA5CNFSM4HX43DBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXV6WBY#issuecomment-502000391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADCEWDBO5MECQG63WAXYS3P2NBYVANCNFSM4HX43DBA
.

To be clear, though, I don't agree with @cmoulliard's approach of having only empty annotations, just that externalized configuration should be prioritized.

Yeah, that's the way I see it as well

@iocanel I do have a question regarding the co-existence of both annotations and properties: which takes the priority if both are present and, possibly, contradictory?

There are no guarantees regarding annotation processor order.
To deal with this we do have ordering for Handlers and Decorators.


Cannot access Shared Drive - Failed to get file: googleapi: Error 404: File not found: XYZ123., notFound

I can list files and folders in My Drive using gdrive list and get info using gdrive info XZY123, but running gdrive info XZY123 on a file or folder located in Shared Drive produces error: Failed to get file: googleapi: Error 404: File not found: XYZ123., notFound

any solutions ?

drives.list is a separate method from files.list
ref: https://developers.google.com/drive/api/v3/reference/drives/list
It does not appear as though this method has been implemented yet in this project.

hitting this as well.  so frustrating, this looked like an awesome utility.

Another vote for this issue, downloading from a shared location is exactly what I need to do, but can't.  Haven't found any good workarounds.

I really need this feature to collect data from workspace admin shared folder.
I just loved this app. Without this function, its just a user tool. With this feature it can have lots of server utilities.

+1 on this

+1

Also would benefit greatly from this. I posted a workaround using a helper Google App Script here, but not ideal.

+1


Question on Project

Hello,
My question is regarding our project. I have a large paper that I have been working on for the entire semester and would like to use that for the project. Being that I'm not at all familiar with GitHub I didn't know if a paper would be an acceptable project to use. Also given that I'm near the end of the semester my paper is nearly done. Are small changes ok for this assignment?

Finally answered this question.


Add a system check to verify that Pillow / Wand has JPEG / PNG / GIF support compiled in

(moved from https://github.com/torchbox/wagtaildemo/issues/12)
It's easy to miss the fact that libjpeg/zlib should be installed prior to installing Pillow, and this will result in a build of Pillow without JPEG/PNG support, and hard-to-identify issues with images not displaying.
We should add a system check on server startup to warn if the image library in use (Pillow or Wand) is missing support for these formats.

Quick question, by server startup do you just mean on runserver start up only, or also a hook into gunicorn / uwsgi / mod_wsgi? By the look of the closed issue, it looks like runserver only, but wanted to check before diving in.

@FlipperPA That's a good point... I was imagining that we'd use Django's system check framework https://docs.djangoproject.com/en/1.8/topics/checks/ for this, to display a warning on the console - but that's not so useful for server-level issues like this, where everything might be perfectly fine in development and only be broken on the live server, where those warnings won't be seen. (Since we've mostly seen this coming up in the context of new users installing wagtaildemo, I hadn't considered the case of live server deployments at all. But catching the issue there is just as important, if not more...)
Perhaps, then, it would be more appropriate to display a warning bar on the admin homepage when the user is logged in as a superuser.

I've implemented the first half of this in #1718 - this adds the system check, but doesn't yet display a message on the admin dashboard.

Pillow 3.x makes it hard to get this wrong now - at this point I don't think it's worth the trouble of prettifying the error message.


docker-machine: not found   Persistent couch db

-----host machine-------
$ ./hello
...........
{
    "message": "hello"
}
$  vagrant ssh

------vm environment    intend to setup a persistant couch db------
$ export OW_DB=Cloudant
$ export OW_DB_USERNAME=admin
$ export OW_DB_PASSWORD=password
$ export OW_DB_PROTOCOL=https
$ export OW_DB_HOST=http
$ export OW_DB_PORT=6000
ansible-playbook setup.yml

PLAY [localhost] **************************************************************

TASK [setup] ******************************************************************

Thursday 16 June 2016  10:42:16 +0000 (0:00:00.038)       0:00:00.038 *********

ok: [localhost]

TASK [find the ip of docker-machine] ******************************************

Thursday 16 June 2016  10:42:19 +0000 (0:00:03.213)       0:00:03.251 *********

fatal: [localhost -> localhost]: FAILED! => {"changed": true, "cmd": "\"docker-
achine\" \"ip\" \"whisk\"", "delta": "0:00:00.003987", "end": "2016-06-16 10:42
19.515486", "failed": true, "rc": 127, "start": "2016-06-16 10:42:19.511499", "
tderr": "/bin/sh: 1: docker-machine: not found", "stdout": "", "stdout_lines":
], "warnings": []}
...ignoring

TASK [set_fact] ***************************************************************

Thursday 16 June 2016  10:42:19 +0000 (0:00:00.203)       0:00:03.454 *********

ok: [localhost]

TASK [gen hosts for docker-machine] *******************************************

Thursday 16 June 2016  10:42:19 +0000 (0:00:00.042)       0:00:03.497 *********

skipping: [localhost]

TASK [prepare db_local.ini] ***************************************************

Thursday 16 June 2016  10:42:19 +0000 (0:00:00.032)       0:00:03.529 *********

ok: [localhost -> localhost]

PLAY RECAP ********************************************************************

localhost                  : ok=4    changed=0    unreachable=0    failed=0

Thursday 16 June 2016  10:42:19 +0000 (0:00:00.367)       0:00:03.897 *********

===============================================================================

setup ------------------------------------------------------------------- 3.21s
prepare db_local.ini ---------------------------------------------------- 0.37s
find the ip of docker-machine ------------------------------------------- 0.20s
set_fact ---------------------------------------------------------------- 0.04s
gen hosts for docker-machine -------------------------------------------- 0.03s

the issue can be reproduced on Ephemeral CouchDB case

What exactly is the issue you experience?

fatal: [localhost -> localhost]: FAILED! => {"changed": true, "cmd": ""docker-
achine" "ip" "whisk"", "delta": "0:00:00.003987", "end": "2016-06-16 10:42
19.515486", "failed": true, "rc": 127, "start": "2016-06-16 10:42:19.511499", "
tderr": "/bin/sh: 1: docker-machine: not found", "stdout": "", "stdout_lines":
], "warnings": []}
...ignoring
not sure this means the command failed to execute sth?

@lfzCarlosC
setup.yml is used to covered all environments (local, mac, etc). If you use docker-machine, setup will try to find the ip of the docker-machine and fill it in ansible hosts for you. But if you dont use docker-machine, the step is still executed cause setup.yml is not bind to a specific ansible env. In this case, you have this error (cause you don't have docker-machine in your dev env). Ansible will stop if any non-zero is returned, so in order to tell ansible go forward, we have to skip the "fatal" error.
Hope that I can give you a enough explanation. This error message is still very annoying, i agree with you

btw, i"m not sure if your env variables are correct :)
------vm environment    intend to setup a persistant couch db------
$ export OW_DB=Cloudant
$ export OW_DB_USERNAME=admin
$ export OW_DB_PASSWORD=password
$ export OW_DB_PROTOCOL=https
$ export OW_DB_HOST=http
$ export OW_DB_PORT=6000

I tested and found if I change the port to 5984, it work well

I change it to
$ export OW_DB=couchdb
$ export OW_DB_USERNAME=admin
$ export OW_DB_PASSWORD=password
$ export OW_DB_PROTOCOL=https
$ export OW_DB_HOST=http
$ export OW_DB_PORT=5984
the same issue happens,but then I execute installing DB command(couchdb.sh, initDB.sh...) and couchDB can be created successfully.

Issue being the "fatal error" mentioned above? As @lehoanganh mentioned, this is an expected "error" currently and skipped for a reason. You can ignore it for the moment, if you're not using a docker-machine based setup.

ok,thanks

@lehoanganh given this seems to be a recurring issue -- do we have a github issue to track and eliminate this?

@mbehrendt let's use this issue to track. a pull is opened: https://github.com/openwhisk/openwhisk/pull/686
It also fixes the issue that setup.yml does not work at the 1. run (you have experienced it ;) )

https://github.com/openwhisk/openwhisk/pull/688 is merged. Issue closed.


fix: text element should be rendered correctly when pasted  to a version before measurements change

After merging #6187 , If you try pasting the text element from new version (which has text measurements change) to an older version (which doesn't have the changes) - The text element turns blank unless edited or refreshed as the baseline isn't introduced (baseline was removed in #6187)
Try pasting this element to https://excalidraw-joczb93fv-excalidraw.vercel.app/ (one commit before #6187 merge)
{"type":"excalidraw/clipboard","elements":[{"id":"iTklLxWPoTs2CFuWImre4","type":"text","x":-4840.892271069522,"y":2854.26437412141,"width":146.71995544433594,"height":33.6,"angle":0,"strokeColor":"#d9480f","backgroundColor":"transparent","fillStyle":"solid","strokeWidth":1,"strokeStyle":"solid","roughness":1,"opacity":100,"groupIds":[],"roundness":null,"seed":1793203390,"version":13,"versionNonce":21200510,"isDeleted":false,"boundElements":null,"updated":1679050766538,"link":null,"locked":false,"text":"Hello World","fontSize":28,"fontFamily":1,"textAlign":"center","verticalAlign":"top","containerId":null,"originalText":"Hello World"}],"files":{}}

This however doesn't happen for containers since we are redrawing bounding box once pasted. So with this fix I am redrawing the bounding box for all text elements (irrespective of whether its a regular text element or text container) and once this fix is pulled into older version it will started working when you try pasting a text element from new version to your version.  Redrawing bounding box makes sure that baseline is introduced.

This is not needed any more


[Marker.io] (mobile) space between image text (commercial sector) and video  should be increased a bit on sectors

Steps to reproduce:

go to commercial sector section
notice the space between text and video below it
compare with figma

Actual result: space is very less
Expected result: it should be bit more..same as that of figma

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://kensway.webflow.io/sectors
Issue details: Open in Marker.io
Device typemobileBrowserChrome Mobile <IP_ADDRESS>Screen Size412 x 892OSAndroid 11.0.0Viewport Size412 x 812Pixel<EMAIL_ADDRESS>
🤖 Marker.io bot - 💬 Vinod commented:

working now

Reply here

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


build: use more stable saucelabs karma launcher

Switches to a custom Saucelabs launcher that:

Runs the official selenium webdriver API (selenium-webdriver instead of wd)
No longer uses an unnecessary heartbeat (fixes: https://github.com/karma-runner/karma-sauce-launcher/issues/136)
Removes unnecessary startConnect logic. Code is more simple, and predictable (even though we are limited with the karma API for launchers)
is actively maintained and can be customized to match our needs.

NOTE: There are various PRs to improve the saucelabs launcher, but none of these has been merged since months. I don't think it's worth bothering more about this, a simple launcher is easier to maintain and also can be customized for our needs. https://github.com/DevVersion/karma-sauce-launcher
@jelbourn @josephperrott  I'm fine moving the repository to another place. Running it under my name feels a bit odd. Having in the material repository might limit the use-cases. e.g. we could use the simpler version for flex-layout and angular/angular etc.

I think it might be best if we have you create a fork that is pushed to npm and depend on it there.  I think its best as this would establish a precedent of relying on a specific github SHA, which I don't know that we always want to do.  Its @jelbourn's call though so I will defer to him.

I've chatted with @jelbourn yesterday about this, and we will be trying to push the changes upstream to official karma-sauce-launcher.

@web-padawan Not too sure about accurate stability measurements, but I assume that this should run more stable because the heartbeat that might slow-down the Selenium server has been removed, and also other issues with the heartbeat have been resolved.
You can read more in the repository that is shared in the PR description. Closing this PR as we will try to upstream the changes.


Viewport/PrimaryWindow resize handler Issue

Currently, DearPyGui (DPG) itself has an viewport (or primary window) resize handler issue (see DPG Issue 1896), that is, the resize handler only works when increasing the size of viewport or primary window and doesn't work when decreasing the size. This will dramatically worsen the user experience of DearBagPlayer when resizing the window. Still looking for an alternative way to implement the viewport resize handler properly.

Just found a solution: use non-primary window with resize callback that can set the viewport size. Posted here.
Will fix it in DearBagPlayer soon.

Fixed in DearBagPlayer 0.2.2


only record per state change processing times for streaming pipelines

only record per state change processing times for streaming pipelines and not for batch pipelines

@tudorm

from @tudorm: https://screenshot.googleplex.com/6AfiyxSbgB3BDHX

@jrmccluskey mind taking a look?

Might also try to loop in someone with a Java background to give a quick check before merging

Might also try to loop in someone with a Java background to give a quick check before merging

@m-trieu mind taking a look?

Ack taking a look


Linter gives invalid inline event handler warning for auto-binding-dart

Given:
<template is="auto-binding-dart">
  <button on-tap="{{buttonTap}}">Tap me!</button>
</template>
You will get a warning about inline event handlers not being supported on templates, only on polymer elements. However, auto-binding-dart is a polymer element. We need to check for an is tag to see if it is in fact a polymer element before throwing this warning.

This issue has been moved to dart-lang/polymer-dart#441.


Cannot be killed after running for a while on Linux 6.1.113 or 6.6.57

I tried Linux kernel 6.1.113, 6.1.112, 6.6.56, 6.6.57 on NixOS 24.05 with arRPC 3.5.0 and Node.js 20.17 (actually the bug also exists on arRPC 3.4.0 and Node.js 20.15; it may be present in other versions as well).
I found that in Linux 6.1.113 or 6.6.57, after running arRPC for a while (usually more than 10 minutes; longer time has higher probability of triggering the bug), it cannot be killed, even with kill -9. This causes the computer to be stuck at shutting down, which is pretty bad. This bug is not present in Linux 6.1.112 or 6.6.56.
It is hard to tweak the kernel version on distros other than NixOS, so I didn't try on other distros. Maybe I can try on Gentoo, though I have never used Gentoo.
I guess this may be a kernel bug or a Node.js bug, but I haven't met with other new bugs with other applications after upgrading the kernel.

I had this Issue since a few days, but just had time to investigate.
For what it's worth, I'm using the home manager services.arrpc.enable, but that's just a simple systemd-unit wrapper.
When someone whats to dig deeper:
I currently updated my nixos-unstable (main) channel to rev: 807e9154dcb16384b1b765ebe9cd2bba2ac287fd but it was also present in rev: 32e940c7c420600ef0d1ef396dc63b04ee9cad37.
My current kernel is 6.6.58
Since the arRPC package in nixpkgs is still on 3.4.0 I also think this is not a recent change to arRPC.
Funny thing tho, that you also use NixOS. So I think is may have something to do with Nix's version of node. Maybe they use the wrong one for building the arRPC package now by accident because they changed the default or whatever? But i'm not firm in digging in the nixpkgs repo/source.
For illustrative purposes, here the messages after shutdown:

the second line  appears one more time after some (unmeasured) delay
And yes, that PID did corresponded to "node arrpc".
I (independently) also tried killing the process (also -9) but it did not respond to any of those.

So I think is may have something to do with Nix's version of node. Maybe they use the wrong one for building the arRPC package now by accident because they changed the default or whatever? But i'm not firm in digging in the nixpkgs repo/source.

I have already investigated that. The answer is that it is probably not the problem of Node. I tried the same arRPC from exactly the same rev of nixpkgs on different Linux kernel version (so exactly the same Node and the same arRPC), and the result is different.

Funny thing tho, that you also use NixOS.

I think it's just because NixOS is the only popular distro with which you can end up with a very new patch version of an old kernel. Other distros either tend to use the newest kernel/LTS kernel or tend to use an old kernel version. This is why I wanted to see whether I can reproduce this bug on Gentoo: I can control the kernel version on Gentoo. However, Gentoo is a painful distro to set up, and I have never touched Gentoo before, and I don't have enough time recently for that. If you know a better distro that I can use to test this bug, please suggest.

Not reproduced on Arch Linux VM with Linux 6.6.58.

this made my computer reload every 15 or so minutes
this is the relevant part of journalctl
nov. 02 11:55:48 vivobook14 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
nov. 02 11:55:48 vivobook14 kernel:       Not tainted 6.6.58 #1-NixOS
nov. 02 11:55:48 vivobook14 kernel: INFO: task node:2261 blocked for more than 245 seconds.

it was repeating this every few minutes untill it reaches the point where the kernel decides to force reboot if i read the journals correctly

OK, I think this is not a bug of arRPC. My npm install command for a totally irrelevant project got stuck too.

Reproducing example:
import { readdir, readFile } from "fs/promises";
let i = 0;
setInterval(async () => {
  console.log(i++);
  (await readdir("/proc")).forEach(pid => +pid > 0 && readFile(`/proc/${pid}/cmdline`, "utf8"));
}, 5000);

Not a bug of arRPC. Closing.


Update to version 2.0.0 of ed25519_dalek

Feature or Problem
Closes: https://github.com/wasmCloud/nkeys/issues/20
I have little context on the internals of this crate so I mostly just followed the compiler errors. It should definitely be reviewed for accuracy. Feel free to close this if you prefer to do the upgrade from scratch.
The unit tests are currently failing. I'll need to circle back to that.
Related Issues

Release Information
next
Consumer Impact
Resolves RUSTSEC-2022-0093
Testing

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin
[ ] x86_64-windows

Tested on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin
[ ] x86_64-windows

Unit Test(s)
Existing tests.
Acceptance or Integration
Existing tests.
Manual Verification
None

@jszwedko Thanks for the work here! I'd love to get rid of the use of the hazmat apis if we can. Do you mind if I hack around with what you've started with here and commit on top?

I was able to get rid of the dependency on hazmat but still getting failure in tests. Digging into that now


XHR for remote resources

https://github.com/jscad/OpenJSCAD.org/commit/4a05755d0107491a18ca4eb1d613cf7fcc2d2014 broke remote URLs

fixed in #275


[Fix #9015] Update Lint/EmptyBlock to allow for empty lambdas.

Update Lint/EmptyBlock to allow for empty lambdas. Fixes #9015.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

This looks like a reasonable change to me if an example for lambda do(\n)end and -> {} to good cases are added.

@koic sounds good I’ll add one!

@koic updated!

It may be better to have this as a configuration option enabled by default. Not sure about that, though, as I guess empty lambdas are relatively common.

I found a bunch of them in rails/rails as well as my work repo. I don't think that this is an uncommon pattern.

If you want it to be an option though I'll fix it up in the morning!

Yeah, I've also seen -> {} and lambda {} than -> { nil } and lambda { nil }. IMHO, these one-liner lambda empty blocks {} can be allowed by configuration default.

Fine by me. Probably we need a cop for empty lamba with a nil in it too. :-)

@bbatsov @koic updated to add AllowEmptyLambdas configuration, default on. Also updated the documentation examples a bit further.

Looks good to me. Thanks!


Dynamic Memory Allocation

Select the Day of Content
Day 9
What information is missing?
Introduction to Dynamic Memory Allocation
@subhadipbhowmik kindly assign

@subhadipbhowmik kindly assign


Fix broken link

The link is not relative (it is absolute) and does not work on docs.

@AndKjell,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Does jaxopt.LBFGS required double precision?

The PyTorch implementation of LBFGS requires double precision (please refer to this issue).
jaxopt.ScipyMinimize uses double precision by default.
Does jaxopt.LBFGS require double precision?

No it uses the same precision as the parameters.

Thanks Mathieu.
jaxopt.ScipyMinimize says:

Note that some methods relying on FORTRAN code, such as the L-BFGS-B solver for scipy.optimize.minimize, require casting to float64.

Can I assume that this does not hold for jaxopt.LBFGS and that there should not be very large differences in the result of a jaxopt.LBFGS optimization if I use simple or double precision parameters?

jaxopt.ScipyMinimize is a wrapper around SciPy, which uses a FORTRAN implementation for LBFGS-B. The FORTRAN code uses double precision.
jaxopt.LBFGS is a pure implementation in JAX, which supports any dtype.

Thanks @mblondel

Thanks @mblondel


give command usage as part of help command

i would like if, e.g., ;help topic gave all possible invocations of the topic command along with what each one means

This will be much easier now that the refactoring is underway (and now that the hard parts of the framework changes are much easier)


reformatting field names according to data warehouse

possibly create a macro that reformats nested fields as they come in from Stitch so that we don't have to rewrite models just to accommodate minor syntax differences
for example:
creative__id (double underscore that is redshift-specific) vs. creative['id'] (single bracket that calls a subfield; snowflake-specific)

Bigquery syntax would be creative.id here. We were going to create a PR for just BigQuery, but would be keen to discuss how this might be implemented in a more database agnostic way.

{% macro nested_field(field, subfields) %}

    {{ adapter_macro('facebook_ads.nested_field', field, subfields) }}

{% endmacro %}

{% macro default__nested_field(field, subfields) %}

{{field}}__{{ subfields|join('__') }}

{% endmacro %}

{% macro bigquery__nested_field(field, subfields) %}

{{field}}.{{ subfields|join('.') }}

{% endmacro %}

{% macro snowflake__nested_field(field, subfields) %}

{{field ~ "['" ~ subfields|join("']['") ~ "']" }}

{%- endmacro %}

{{ nested_field('creative',['id']) }} would compile to:

creative.id on BigQuery
creative['id'] on Snowflake
creative__id everywhere else

Issue closed to prepare for Repository Archival


ING-2

@Nasr-Ladib : Thanks for your contribution! The author(s) have been notified to review your proposed change.


How to run watir in GitHub actions

Not able to initialize browser itself.

You can look at the code in this repo to see how we do it: https://github.com/watir/watir/tree/main/.github
Let us know if you have additional questions or a reproducible issue we can investigate.

You can look at the code in this repo to see how we do it: https://github.com/watir/watir/tree/main/.github

Based on this, I created the following workflow file:
name: workflow

on:
  push:
  workflow_dispatch:

jobs:
  run_workflow:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - uses: ruby/setup-ruby@v1
      with:
          ruby-version: '3.0'

    - name: Setup Chrome
      run: |
        wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
        echo "deb http://dl.google.com/linux/chrome/deb/ stable main" | sudo tee -a /etc/apt/sources.list.d/google-chrome.list
        sudo apt-get update -qqy
        sudo apt-get -qqy install google-chrome-stable
        sudo rm /etc/apt/sources.list.d/google-chrome.list

    - name: Run Script
      run: |
        bundle
        ruby script.rb

Finally, on running browser = Watir::Browser.new I get the following error:
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)```


MAC OS Brightness BUG When using BGFX

I tested it on Ubuntu and Mac respectively, and only Mac has this bug.
When I run the bgfx program, there is a bug in the system's brightness adjustment function.
When I adjust the brightness, the system's brightness progress bar changed, but the actual brightness of the monitor does not change (or changes after an unspecified delay).
After I exited the bgfx program, the value of the system brightness progress bar did not match the actual brightness of the monitor.
I need to adjust the brightness again, and then the monitor brightness can match the brightness value in the system settings.
MAC OS Version is 14.2.1 (23C71)

maybe it's not a bug.
it's fixed when i change BGFX_RESET_NONE to BGFX_RESET_VSYNC.
it seems  i must use BGFX_RESET_VSYNC on macos/metal


Extract quickstarts banner into its own component

Promissed refactoring :)
Looks much cleaner, good thinking @lucasgarfield ! :+1:

/retest

/retest

/retest


[BUG] Server Crash

Describe the bug
When generating new chunks the server crashes
To Reproduce
I was flying around a on a server, then the server crashed
Expected behavior
The Server not crashing
crash-2021-09-17_12.23.31-server.txt

The Server no crashing
Fair assumption. 😁

Sadly I could not reproduce your crash in on my personal server instance. In 20 minutes I flew in different directions, teleported and so on, but could not get a crash like you. Was the crash right when you started exploring, or at some seemingly random time?
Since you have quite a lot of mods that mix into the part of the code please try removing mods. When I know what mod causes you issue I can fix it preceisely. Otherwise I may add some form of general failsafe, but that might result in some chests just not replacing.

I am not surprised , I also could not reproduce it after flying in one direction on a server for many hours. Guess it is a pretty extreme edge case.
Also, this is my modpack after I have ripped out half of the mods. Did that the other day when I sent it to you, more reasonable to test things.  haha
In my mind, general failsafe that logs when and where it happens may help track down who is at fault as well as let me know it has happened somewhere and I can go replace the chest by hand

Oh yeah! It is that pack, now that you mention it!
I have added general error handling in 1.4.0. If chest replacement fails for whatever case, you will get a message in the server console like:
[LootCrates] Error while replacing a chest in the world <> at <> with loot table <>
If you have another problem or a suspect, what may cause it, always feel free to open another issue. 😊


added filter for collapsible code blocks

Added filter "collapse_code.py" for HTML documents.

Will search document and add <div> with HTML5 <details> and <summary> tags around all CodeBlocks.
The <summary> block contains an onclick javascript event that will toggle innerHTML between "Show code" and "Hide code".

before:
print("test")

after (text toggle via javascript not working here):

 Show code
print("test")

Looks great, thanks!


added Fetchable behavior

https://github.com/riesenia/cakephp-fetchable

Full stop is missing at the end.
As for your plugin:

missing tests

thanks... good point. i'll update and let you know

Hi @ADmad - no problem... I don't force you to use it :) Just pointing out differences - you have fetchEntity method available (of course you can add additional one in addition to custom finder to your model, but this means extra writing) plus you have one extra check that even prevents cache engine to be hit.
As I write in README, it's "Relevant for tables that contain moderate number of rows and are used commonly in many parts of application". I don't say, that this is a common case, but I used it a lot before, so I made it a public package so it can maybe serve someone else.
Btw @dereuromark issues you pointed out are fixed.

OK
@ADmad shall we merge this?

@segy Since you are using return type hints you should specify the PHP version constraint in your composer.json https://github.com/riesenia/cakephp-fetchable/blob/master/src/Model/Behavior/FetchableBehavior.php#L89
@dereuromark I am fine with merging after the issue I pointed out if fixed. There will probably be others who find this useful :)

I agree.

ping @segy Can we proceed here?

hi. sorry for the delay. i added the php constraint.