Add support to display (and complete) Google Tasks

Using the existing content providers (Astrid, gTasks, etc.)

Seven years forward, some generations of "Google Tasks" changed, but unfortunately I still don't see any documentation on integration with "Google Tasks app", installed on a device. And this is what a widget is about.
Existing documentation tells about integration with remote Google Tasks service:
https://developers.google.com/tasks - but this integration should be done by some "Tasks client" app, not by a "Widget".
Since this summer we support Open Tasks client app. I that integration with Google Tasks would be a good suggestion for that app. Our widget (now called "ToDo Agenda" would show that tasks out of the box...
See #308

Me too would greatly enjoy Google Tasks integration to have both calendar and task events in a nice widget as yours. For tasks the client app I use is Tasks: Astrid To-Do List Clone (https://github.com/tasks) which I'm happy with. As the source code is available it should be possible to integrate if there's enough interest.

@jimfum Aha, so you mean that Astrid To-Do List Clone (https://github.com/tasks) is integrated with Google Tasks, and so we could try to integrate our widget with it?!
Interesting. I only don't see any info if data from this Astrid app can be accessed by our widget on an Android device...

Thanks for a quick reply. That's right. Astrid integrates with Google Tasks and also has its own widget (just tasks, no calendar). As the source code is available, we should be able to access Astrid content from your ToDo Agenda widget I"d presume.
I'm no Java developer but rather .NET. Will try to find time for this, could be an interesting challenge ;) Plus as you wrote, it may not require much of coding but rather configuring...

@jimfum

As the source code is available, we should be able to access Astrid content from your ToDo Agenda widget I'd presume

No, this could only help us understand if such possibility exists... Integration with another app means communicating with that app using channels that that app provides.
But of course in a case of an enhancement need at Astrid side we could suggest a change to it (PR)

Thanks @yvolk for explaining. I'll dig into it as an educational exercise.

Von meinem iPad gesendet

Am 19.01.2020 um 16:18 schrieb Yuri Volkov @.***>:

Closed #29.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Wrong values due to Communication problems

Hey hoo, I just saw that I got consumption and production values like 45.000w and even higher on my 5kw inverter... I did a little research and found this issue in the solarman git... https://github.com/StephanJoubert/home_assistant_solarman/pull/270
Is it possible to implement something like that?

Going through the PR, I read that someone nicked code from pysolarman5, got caught and eventually they started using pysolarmanv5
This addon already uses pysolarmanv5 v3.0.0, so it should include the idea behind the link you shared.
What they do in the component you linked to is to reconnect on any error, something not being done today - see solarman.py This was implemented by the author of pysolarmanv5, so guess this would be the expected way to use the library

Okay thanks for the explanation..
Anyway the problem is still present, as a workaround they implemented something like an plausibility check for the measured values...


Include NPM or Pythonic Dependency manager setup file.

Set up dependencies with NPM or python dependency manager.

Pushing Python dependency portion to alpha 0.2
Accepting current state for 0.1


Explore use of LogByteSizeMergePolicy for time series data use cases

Is your feature request related to a problem? Please describe.
LogByteSizeMergePolicy always merges adjacent segments together which could be helpful for cases for time series data where documents are sorted based on timestamp and segments usually don't have much overlap on timestamps. At query time, its better if the time range can be contained in lesser number of segments and other segments can be skipped by checking min/max value of timestamp field. When adjacent segments are merged, its likelihood increases significantly.
TieredMergePolicy, which is successor of LogByteSizeMergePolicy and current default merges segments more smartly and can merge non-adjacent segments too, which could be inefficient for time series data.
Describe the solution you'd like
Explore usage of LogByteSizeMergePolicy for data streams use cases where @timestamp is a mandatory field.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

There is one more mergepolicy got introduced interleaved ShuffledMergePolicy.
This was introduced for exactly opposite reason than what you are trying to achieve here and make the time series based documents shuffled for better desc order performance.
desc sort order is wide scenario on timeseries and computation heavy compare to range on time series based workload. range queries anyway are very fast due to BKDs and I would be very curious to see how much improvement we can get with this merge policy.
Will be curious to know numbers here, but definitely consider comparing sort performance along with range queries

Thanks @gashutos for taking a look. I'm currently working towards getting numbers out for comparison.
The shuffle merge policy is only applicable on force merges, which is like a final merge operation before index goes into read-only state for most of the cases. And there, as total number of segments would be less in number and bigger in size, it totally makes sense to interleave read operation on old and new segments.

range queries anyway are very fast due to BKDs and I would be very curious to see how much improvement we can get with LogByteSizeMergePolicy merge policy.

This optimization wouldn't be helpful with anything within BKD, but would help in searching across BKDs (in different segments) in a more ordered way.

I'm not seeing any improvement using LogByteSizeMergePolicy against http_logs workload. http_logs doesn't generate workload which matches real world use cases of data streams where multiple clients are ingesting in a time ordered way.
The way current logic works is, the whole corpus is segmented into chunks and each client is assigned an offset from where it starts ingesting. This makes the timestamp order randomized and LogByteSizeMergePolicy is not expected to perform any better in such scenarios. OpenSearch benchmark should also support running search concurrently with ingestion for data stream use cases.
I'm currently working on setting up such data stream locally to evaluate the improvements if any. Meanwhile, also working with opensearch-benchmark to add such capability.
Posting numbers with current logic -
Machine: r5.2xlarge
Heap: 32 GB
LogByteSizeMerge Policy
Latency (ms)

Operation Type
P50
P90
P99
P100

hourly_agg
3,092.1
3,163.6
3,215.5
3,286.4

asc_sort_timestamp
5.657
6.398
7.855
8.041

index-stats-wait-until-merges-finish
22,793.3
26,391.2
26,391.2
26,391.2

asc_sort_with_after_timestamp
16.047
22.208
23.94
25.825

index-stats-wait-until-merges-1-seg-finish
40,995.5
72,900.9
72,900.9
72,900.9

desc-sort-with-after-timestamp-after-force-merge-1-seg
217.5
283.5
312.1
325.6

force-merge-1-seg
240,011.3
240,013
240,013
240,013

scroll
587
601.9
659.7
720.4

range
7.373
7.917
10.654
54.852

index-append
175.4
267.6
476.2
10,609.1

desc_sort_with_after_timestamp
129.8
143.5
155.4
180.7

default
4.349
4.554
4.845
6.617

asc-sort-timestamp-after-force-merge-1-seg
5.784
7.524
8.455
9.358

200s-in-range
5.98
6.326
6.745
10.67

400s-in-range
3.976
4.26
4.548
6.429

term
4.542
4.794
5.236
6.076

desc_sort_timestamp
48.449
70.893
76.449
78.903

asc-sort-with-after-timestamp-after-force-merge-1-seg
37.074
43.786
47.948
60.585

desc-sort-timestamp-after-force-merge-1-seg
181.8
228.5
262.5
270.1

TieredMergePolicy

Latency (ms)

Operation Type
P50
P90
P99
P100

hourly_agg
3,003.4
3,079.4
3,132.8
3,187.5

asc_sort_timestamp
7.053
8.149
9.872
10.126

index-stats-wait-until-merges-finish
5,586.6
58,237.1
58,237.1
58,237.1

asc_sort_with_after_timestamp
18.278
21.437
24.302
48.292

index-stats-wait-until-merges-1-seg-finish
19,230.3
103,239
103,239
103,239

desc-sort-with-after-timestamp-after-force-merge-1-seg
95.924
164.9
190.2
211

force-merge-1-seg
240,010.7
240,013
240,013
240,013

scroll
598.8
612.9
671.5
682.2

range
7.636
8.312
10.476
47.232

index-append
163.2
259.5
509.5
11,028.8

desc_sort_with_after_timestamp
41.707
55.354
68.997
99.183

default
4.556
4.824
5.579
6.17

asc-sort-timestamp-after-force-merge-1-seg
6.822
7.802
9.374
9.95

200s-in-range
6.326
6.925
10.44
41.752

400s-in-range
4.201
4.522
5.238
5.66

term
5.157
5.52
6.151
7.539

desc_sort_timestamp
18.51
24.365
49.348
56.725

asc-sort-with-after-timestamp-after-force-merge-1-seg
31.552
38.305
47.129
79.136

desc-sort-timestamp-after-force-merge-1-seg
113.8
169
181.1
184

I do see some performance gain when running locally on system with following configuration -
I had to customize the http_logs workload. I'm just using one log file, index with one shard and just few operations - index-append, asc_sort_timestamp, desc_sort_timestamp;
I had to explicitly set refresh interval as 1s so that the translog doesn't grow huge and new segments are created frequently, so that merge policy can come into picture sooner. If we don't set refresh interval setting, since all searches happens after indexing is complete and force merge is complete, so it keep filling translog and segments are created much later (whe explicit force merge is triggered) and thus merge policy comes into picture much later.
workload: customized http_logs
index: logs-181998; shard count: 1; doc count: 2708746;
indexing client count: 1
benchmark machine: c4.2xlarge
data node count: 1; r5.2xlarge; heap: 32GB

With tiered merge policy
|                                                 Min Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                                Mean Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                              Median Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                                 Max Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                        50th percentile latency |      desc_sort_timestamp |     10.3268 |     ms |
|                                        90th percentile latency |      desc_sort_timestamp |     11.4483 |     ms |
|                                       100th percentile latency |      desc_sort_timestamp |     12.5894 |     ms |
|                                   50th percentile service time |      desc_sort_timestamp |     7.01704 |     ms |
|                                   90th percentile service time |      desc_sort_timestamp |     8.43393 |     ms |
|                                  100th percentile service time |      desc_sort_timestamp |     10.1131 |     ms |
|                                                     error rate |      desc_sort_timestamp |           0 |      % |
|                                                 Min Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                                Mean Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                              Median Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                                 Max Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                        50th percentile latency |       asc_sort_timestamp |     9.57576 |     ms |
|                                        90th percentile latency |       asc_sort_timestamp |     10.3733 |     ms |
|                                       100th percentile latency |       asc_sort_timestamp |     11.4519 |     ms |
|                                   50th percentile service time |       asc_sort_timestamp |      6.4471 |     ms |
|                                   90th percentile service time |       asc_sort_timestamp |     7.24644 |     ms |
|                                  100th percentile service time |       asc_sort_timestamp |      8.9884 |     ms |
|                                                     error rate |       asc_sort_timestamp |           0 |      % |

with log merge policy
|                                                 Min Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                                Mean Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                              Median Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                                 Max Throughput |      desc_sort_timestamp |        0.51 |  ops/s |
|                                        50th percentile latency |      desc_sort_timestamp |     9.71618 |     ms |
|                                        90th percentile latency |      desc_sort_timestamp |     10.8187 |     ms |
|                                       100th percentile latency |      desc_sort_timestamp |     12.6003 |     ms |
|                                   50th percentile service time |      desc_sort_timestamp |      6.6176 |     ms |
|                                   90th percentile service time |      desc_sort_timestamp |     7.80692 |     ms |
|                                  100th percentile service time |      desc_sort_timestamp |     9.29486 |     ms |
|                                                     error rate |      desc_sort_timestamp |           0 |      % |
|                                                 Min Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                                Mean Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                              Median Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                                 Max Throughput |       asc_sort_timestamp |        0.51 |  ops/s |
|                                        50th percentile latency |       asc_sort_timestamp |     8.70018 |     ms |
|                                        90th percentile latency |       asc_sort_timestamp |     9.96291 |     ms |
|                                       100th percentile latency |       asc_sort_timestamp |     10.8828 |     ms |
|                                   50th percentile service time |       asc_sort_timestamp |     5.62269 |     ms |
|                                   90th percentile service time |       asc_sort_timestamp |     6.75591 |     ms |
|                                  100th percentile service time |       asc_sort_timestamp |      8.3948 |     ms |
|                                                     error rate |       asc_sort_timestamp |           0 |      % |

If you take a segment and see values, they are very much sorted by timestamp. (nearly sorted). Just do desc order sort by timestamp on any segment and you will notice results from last chunk of docIds in segment.
Would not this be a production level scenario ? Where multiple service are pushing logs and they are pushing in chunks only. SO it might be possible skewing sort order little bit.

if you look at the timestamp difference between the 1st and the 8th client at a given time, its quite significant - https://github.com/opensearch-project/opensearch-benchmark/issues/365#issuecomment-1687282593

below is the snapshot of the segments created by both merge policies. The X axis denotes the segment, sorted by their size and Y axis represents the @timestamp field min, max value stored in BKD. We can see the delta by min & max is growing large in tiered MP. Given, the corpus is small, we didn't see much performance improvements.
Next I'm working on ingesting more documents taking care of following -

all indexing clients, should processing timestamps as close as possible.
set explicit refresh interval to values - 5s, 10s, 30s and compare the performance.
measure the write amputation for merges and compare both policies.
Compare the performance of - asc_sort_with_after_timestamp desc_sort_with_after_timestamp - - with different and more relevant search_after values. asc_sort_timestamp &desc_sort_timestamp.

@rishabhmaurya If time is really a concern, why not make the merge policy time aware?

@itiyama open to such experiments however I think the gain may not be significant for timeseries. Assuming the agents sending data from different machines don't have a significant time lag, merging adjacent segments would ensure, the overlap of timestamps across segments isn't a lot however tiered merge policy could worsen the overlaps. The timestamp based approach might be more helpful in cases when there is a significant lag between clients ingesting but that's usually not the case and we should not to optimize for such anomalies. Do you have better ideas on how you want to make use of timestamps?

Some of the outstanding items before making LogByteSizeMergePolicy default for timestamp based index -

With current testing so far, the tail segments created by LogByteSizeMergePolicy are significantly bigger than TieredMergePolicy keeping merge factor and min segment size same. This is causing increase in latency for desc sort queries when compared to TieredMergePolicy in http logs workload. AI Fix https://github.com/opensearch-project/opensearch-benchmark/issues/365 and experiment with LogByteSizeMergePolicy settings and optimize for http_logs dataset.
Check if we can improve the behavior of LogByteSizeMergePolicy to avoid very large segments in case of findForcedDeletesMerges  as discussed here https://github.com/opensearch-project/OpenSearch/pull/9992#discussion_r1334903911


Generate API keys for sensors through profile page

API keys are an alternative to logger_id for verifying the auth of the logger.


generate multiselect-tpls.js dynamically with gulp

This makes a rather large change to the existing multiselect-tpls.js, which I believe was broken and/or out of date.
I tested this, but as I don't yet have this plugin fully integrated in my project, I am not 100% sure its working as it should, but it does pick up the template that is now inlined via the gulp script.
This should resolve Issue 66

Verified that this works!

Cool, Thanks!


Adding a new version defined in a swagger file

While adding a new version, it looks like there is no way of pointing that one to a pertinent swagger file!?
Am I correct? And just wondering why that would be the case?
I would assume that APIM will allow user to point to a  corresponding version as opposed to just copy a previous version over.
Thanks.

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

ID: 25a33ff6-8ffc-ad26-d429-3170bcca9498
Version Independent ID: fcd9c088-8b17-e53b-4c93-f90f2dc5c09c
Content: Tutorial - Publish versions of your API using Azure API Management
Content Source: articles/api-management/api-management-get-started-publish-versions.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

Thank you for your feedback! We will review and update as appropriate.

Well thank you for the response, but I am still not sure how this article explains how to publish multiple versions of my API as title says.
If I have an API that has 2 versions, that means it would have 2 swagger files, each one for the different version. And I really do not see how to publish my API inside of the APIM!?
What is demonstrated here is manually clicking and creating a new version while moving existing API definition into it, how real is that scenario?

@dlepow Can you provide you insights on this?

@drazen-relias - After adding an API version (which creates the API version set), you can edit it like any other API added to API Management: add operations, edit the Open API spec, etc. See Edit and API. Let us know if this helps. Thanks


feat: 🎸 create children jobs even in case of error

fixes #949, along with #1066

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Note also that two interdependant steps mean... a cycle. Which should not exist in a DAG.

review is welcome 👋 🤗


Wrote submit-token function for codecov

This is currently working on https://codecov.io/github/kshyatt/julia?ref=master!

Dang thats cool.  Can one tag using only the web interface?

Ehh, maybe, maybe not. I'll just do it and save us having to find out!

BTW I have confirmed that this works for packages, not just base. My own CUSPARSE.jl is now sporting a codecov badge.

This is awesome, you two! Excited to try it out with partial coverage stats provided by Base.


make this a "ponyfill"

One could always manually set it up to be a polyfill, but we cannot do the reverse.
Simply looking at a file that uses objectObserve(), a new or third-party developer will know that a non-native function is being used, even if it is only an interface to the native function (when it's available). In such cases, it still communicates the additional step in the algorithm, and the developer can choose to dig deeper to find out more.

This isn't going to happen. The current polyfill exposition will stay as it is.
If using a method named like objectObserve is preferred, the developer can just assign
// See object-observe.js
var objectObserve = Object.observe;

and eventually delete the observe property from Object if the function isn't native (which is also trivial to check).


Use guaranteed-idempotent STATIC_URL variable

base.html sets the window.static_url JS variable. It used to
use {% static '' %}, but that function is not idempotent in
apache libcloud.
Use the safer STATIC_URL variable, which always contains the root
of the static file tree.
This was required for me to use Django Rest Swagger with Google Cloud Storage under Django-Storages, since in that library {% static %} is not idempotent.
Since the only use of window.static_url is in https://github.com/marcgibbons/django-rest-swagger/blob/516c5021da9b1cceb791ce4eeb8ff3d4b6dd7d09/rest_framework_swagger/static/rest_framework_swagger/swagger-ui.js#L397, seems like the dynamic logic in {% static '' %} is not required.
Happy to clean up this PR if you want to merge it.

I have a problem with STATIC_URL. Its empty  Its doesn't work for
python manage.py runserver
and for gunicorn


VB.NET is incorrectly omitted

The documentation fails to mention that *.vbproj files are supported as well.
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-pack#arguments

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

ID: a7e805a3-f2ec-b05a-d5c8-29f7a8c16a5f
Version Independent ID: 4257ec12-df6f-ec52-aad3-012e5fce8133
Content: dotnet pack command - .NET Core CLI
Content Source: docs/core/tools/dotnet-pack.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Easy enough to fix, but before that, I'll wait someone to confirm if only vbproj is missing, or fsproj is missing too.
cc: @cartermp Can you confirm if dotnet pack works for fsproj files or not?

Yes, dotnet pack works for all project files (csproj, vbproj, fsproj)

@cartermp, Thanks. Opened #18446


Query results in ResultTable if responseFormat = sql

This falls under the sql compliance work. We are moving to ResultTable, which will serve as the single tabular sql like structure to return results from all types of queries.
This is currently turned off by default. This feature can be enabled by passing responseFormat=sql in queryOptions.
PS: this is the 3rd step of the breakdown of PR https://github.com/apache/incubator-pinot/pull/4833

https://github.com/apache/incubator-pinot/issues/4450

Codecov Report

Merging #4863 into master will decrease coverage by 7.12%.
The diff coverage is 88.17%.

@@             Coverage Diff              @@
##             master    #4863      +/-   ##
============================================
- Coverage     57.64%   50.52%   -7.13%
  Complexity        4        4
============================================
  Files          1203     1203
  Lines         64685    64801     +116
  Branches       9393     9416      +23
============================================
- Hits          37289    32742    -4547
- Misses        24611    29539    +4928
+ Partials       2785     2520     -265

Impacted Files
Coverage Δ
Complexity Δ

...t/core/query/selection/SelectionOperatorUtils.java
88.92% <100%> (-6.84%)
0 <0> (ø)

...aggregation/function/AggregationFunctionUtils.java
93.75% <100%> (-1.91%)
0 <0> (ø)

...core/query/selection/SelectionOperatorService.java
95.38% <100%> (-2.73%)
0 <0> (ø)

...rator/query/AggregationGroupByOrderByOperator.java
92.5% <100%> (ø)
0 <0> (ø)
:arrow_down:

...t/core/query/reduce/SelectionDataTableReducer.java
55.17% <58.82%> (-14.4%)
0 <0> (ø)

...ot/core/query/reduce/DistinctDataTableReducer.java
79.36% <75%> (+7.27%)
0 <0> (ø)
:arrow_down:

...core/query/reduce/AggregationDataTableReducer.java
82.75% <89.65%> (-3.36%)
0 <0> (ø)

...not/core/query/reduce/GroupByDataTableReducer.java
84.18% <92.38%> (+0.85%)
0 <0> (ø)
:arrow_down:

...g/apache/pinot/sql/parsers/CalciteSqlCompiler.java
0% <0%> (-100%)
0% <0%> (ø)

...pache/pinot/core/realtime/stream/MessageBatch.java
0% <0%> (-100%)
0% <0%> (ø)

... and 274 more

Continue to review full report at Codecov.

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


Allow to add/remove, enable/disable adapters

Allow setting an option to add custom adapters or remove adapters that already exists

A problem that i have related to this one, i have kaminari in my gemfile.lock (not my gemfile) because it's required by active admin and paginates with kaminari by default (behaviour that i don't want)


Revert "helm: uniform retrieval of nested helm value"

This reverts commit 9f61556e6be584ee67e16fb96d1a02f1376e61c4.
This commit seems to be causing no-ipsec-xfrm-errors in ci-ipsec-upgrade to fail in cilium/cilium main branch ^1.

✅ a successful run against cilium/cilium main branch: https://github.com/cilium/cilium/actions/runs/8310945038

Testing was done in the below PR (which was failed previous with 0.16.2)
https://github.com/cilium/cilium/pull/31286

https://github.com/cilium/cilium-cli/pull/2427

closing in favor of https://github.com/cilium/cilium-cli/pull/2427 🥰


Retry on ciliumnode update/create

Currently, we don't retry on updates/creates for the
CiliumNode when the agent starts up.
This is suboptimal because the operator and the agent
can end up "fighting" each other since both of them create/update
the CiliumNode resource. This can cause the agent to continually
fail to start and prolong the time before a node is ready for use.
Signed-off-by: Ashray Jain<EMAIL_ADDRESS>Retry on conflicts when creating/updating CiliumNode objects on agent startup

test-me-please

Coverage decreased (-0.03%) to 36.864% when pulling 82d07eade3294e81b9cb63f846a74cca3911c017 on ashrayjain:aj/retry-cilium-node into 5a8501a9565591c1c2897ba8cf0e433429f37469 on cilium:master.

test-me-please


db:seed => Validation failed: Avatar is not attached, Time zone can't be blank

Describe the bug
While running bin/setup I am getting the error, need to populate it as well while running bin/rails db:prepare
To Reproduce
Steps to reproduce the behavior:
run bin/setup

Thanks for documenting! This is being fixed in PR #242, which should be merged in soon.

Closed via #242.


docs(modal): added a simple component modal demo

I added a button for show a modal using components. It's using the same HTML of the old modal demos.
Can we remove the $scope usage in these demos and using the $ctrl in both? Component and controller modals.

I would be fine removing $scope usage wherever possible - are you volunteering to do that cleanup? :)

Sure, I can do that.

Done, removed $scope from demo code


hyper::error::Error is not Send + Sync

hyper::error::Error is not Send + Sync thanks to solicit::http::HttpError::Other(Box<Error>). This percolates up and breaks rust-websocket.
You can catch changes of this kind using something like:
fn _assert_error_is_sync_send() {
    fn _is_sync_send<T: Sync+Send>() {}
    _is_sync_send::<Error>();
}

I filed this on solicit too. I'm not sure where the breaking change occurred.


kAppend in a LinkedList Using C++

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

This was already in work here: https://github.com/TesseractCoding/NeoAlgo/issues/5200
And a PR was made here: https://github.com/TesseractCoding/NeoAlgo/pull/5202
Unfortunately, I have to close this. If this is a mistake, let me know.


F-Droid Fennec Web Browser

Hello, good evening, I've been looking at your web page for a long time where you do the privacy tests of the different web browsers, and I was wondering if you could include the Fennec web browser from F-Droid in the list, if I'm not bad I'm wrong it's a web browser for android which is made of binaries

am maintainer of Fennec F-Droid for 2+ years: it should test the same as Firefox

Partially, since in the description of the application it says that it is made with binary numbers, while, on the contrary, Mozilla Firefox unlike Fennec is not made of binary numbers

#66


Analytics

https://github.com/igrigorik/ga-beacon

http://www.lunametrics.com/blog/2013/06/17/email-tracking-google-analytics/
https://developers.google.com/analytics/devguides/collection/protocol/v1/email
https://ga-dev-tools.appspot.com/hit-builder/

Email Open a6a2c305b860a675211e84805b335dde9acb8f8b


When deselecting ALL button, irrelevant aircraft will start to display

TTSIA; before ALL, its fine, ALL displays everyone, turning ALL off will only hide half of the aircraft. There will still be a lot of irrelevant aircraft on the scope.

wrong repository
this one instead https://github.com/vNAAATS/vatsim-NAAATS


Improved cookiecutter README template, with Meltano usage instructions

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/76
Originally created by @aaronsteers on 2021-03-31 19:51:42

The following discussion from !39 should be addressed:

[ ] @DouweM started a discussion:

It makes sense for this README to have a section with next steps for the developer who just used the template to create the tap, but I think the rest of the README should be optimized for users of the tap, like you'd expect in a typical open source project README, rather than developers/contributors of the tap.
So I'd expect Installation, Configuration, and Usage sections ahead of references to Testing and Dev Guide.
Can you base this README template on some of the better tap READMEs, or even what I ended up with in https://gitlab.com/DouweM/tap-investing including instructions on how to run with Meltano?

View 4 previous comments from the original issue on GitLab


terramap 0.6 and the 2 fix versions 0.6.1 and 0.6.2 have all the same Problem in the Screen of Minecraft

Hi,
it give a Problem on the top left of the Screen. I have your Mod and TerraMap 1 to 1 in my folder and a little bit other Decomods but in your newest Mod versions give it one big Bug what the Screen to 1/12 with a white square covered show the Picture. I hope you can fix it. Why so can I not play.

Hello, this is an intended feature, it's a minimap. You can configure it (change it's size, disable it entirely, etc), in the Terramap's config. Terramap isn't really useful on a superflat world, it is supposed to be used on a Terra121 world. That's why your minimap is blue, it is centered onto the ocean at 0 0.
Here is an example image of the minimap in action on an Earth world (the minimap on the right is from an other mod (JourneyMap)):


In the fixed-height datagrid, switch users cannot scroll up/down using keyboard commands or MacOS Switch's scroll feature

[Clarity Version]
3.1.1
[Test URL]
https://clarity.design/documentation/datagrid/fixed-height
2.1.1 Keyboard
(Level A)
https://www.w3.org/TR/WCAG21/#keyboard
[OS]
MacOS 10.15.3, Windows 10
[User Agents/Assistive Technologies]
Safari 13.0.5, Firefox 75.0, Switch
[Component]
Datagrid
[Description]
In the fixed-height datagrid, switch users cannot scroll up/down using keyboard commands or MacOS Switch's scroll feature.
[User Impact]
Switch users cannot access data that is offscreen in the fixed-height datagrid.
[Steps to Reproduce]
See the following instructions for switch usage then follow the steps below.
Windows (see Scan through keys)
https://support.microsoft.com/en-us/help/10762/windows-use-on-screen-keyboard
Mac
https://support.apple.com/en-us/HT202865

Using a switch, navigate to the datagrid with the Tab key.
Try scrolling up and down using the Up/Down arrow keys and notice that you cannot scroll the datagrid up/down.
For MacOS only:
Try activating Pointer --> Scroll Up or Scroll Down and notice that you cannot scroll the datagrid up/down.

[Recommendation]
No focusable elements exist within the Fixed-height datagrid. Without a focusable element inside the datagrid, Switch users and other users interacting with this content from the keyboard alone will be unable to scroll past the content that overflows the visible boundaries. Making the root grid element keyboard accessible with a tabindex value of "0" and managing focus with aria-activedescendant is one method of solving this issue.
...

[Reporter Email]
<EMAIL_ADDRESS>

Hi there, this is an automated message.
In an effort to dedupe and track accessibility reports consistently, this issue is being closed and tracked internally with our Accessibility team. It will still be triaged and addressed as part of ongoing work.


SpiDma Half duplex is hard to use

The signatures for write and read require self which means we have to dance around moving it. Ideally, it should be possible with &mut self.
cc: @bjoernQ I believe you implemented this initially

Yes I think we can make things much simpler this way


Add week ending and week start to grain

@mistercrunch Adding two new time grains for Presto

week_start
week_ending

Both grains use Sunday to Saturday as definition of week.

Coverage remained the same at 65.459% when pulling 48c8a9024785e61ee9339aa783d94a8b9ff9de1b on week-grain into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.

Coverage remained the same at 65.459% when pulling bad3128df9562582b6fc3c1995ddbaba196f2d61 on week-grain into f09f3d7c4b0cdb7df7b7d075e509b12a42aa878a on master.


Missing Weapons

some weapons are missing. The ones I found so far are:
zephyr blades
sword of the cosmos
molten sword
dragonkin seeker sword
guardian's spearblade

Those sound like Convergence weapons. Make sure you selected "The Convergence (mod)" in the top left dropdown

yep, already selected. the ones I listed were the only ones missing in the app that were still in the mod

btw, my mistake on zephyr blades, the missing ones are all straight swords for some reason.

Which weapons aren't showing up in that case? Can you post a screenshot including the weapon list and the filters/checkboxes?


Failed to excute  libcamera-apps

Hi,
HW: Pi4  1GB
OS:  Linux iraspberrypi 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux
When I execute libcamera-hello, I get the following error, but  qcam is working fine
terminate called after throwing an instance of 'std::runtime_error'
   what():  failed to import fd 18 Aborted

I located here,
https://github.com/raspberrypi/libcamera-apps/blob/326fdfd120a0f62b7e76f4ee8aa0c82c2bf008e6/egl_preview.cpp#L317
eglCreateImageKHR seems to be the API provided by
https://github.com/anholt/libepoxy
I'm using the libepoxy from the master branch.
Which version are you using, I can recompile it & try again，
Thanks!

Hi, thanks for the question. I'm just using the default libepoxy branch, which I assume is master, so it's not clear to me why you should get this. I've tried restricting my Pi4 to 1GB and that doesn't seem to cause any problems either. Could you perhaps paste in your /boot/config.txt just to check if there's anything untoward in there? Thanks.
There's always the option of "updating your software to the most bleeding edge version"  (use "sudo rpi-update"), but at this point I can't see any reason why that would make a difference.

Hi, I'm having a similar problem. I've built the libcamera apps on a Pi Zero W and when I try and execute any of them I get an "Illegal instruction" error. I've followed the instructions in the readme and I'm on the bleeding edge of everything.
I'm a bit stumped by this one, it seems like the application is executing an invalid cpu instruction, but all of the code been compiled on the device that it's executing on? The libcamera "cam" app runs without problems.
My boot/config looks like this:
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=vc4-fkms-v3d
gpu_mem=128
dtparam=i2c_vc=on
dtoverlay=imx290,clock-frequency=74250000
start_x=1

Hi, I'm afraid we've only ever run libcamera ourselves on a Pi 3 or 4, my apologies for not making this clearer on the instructions page. libcamera moves a lot of the processing load formerly on the Broadcom GPU onto the ARM cores, so it helps if they are reasonably capable. It may be that it optimises by default for a more powerful type of ARM processor than you have, so you could try deleting and remaking the build directory, and running cmake like this:
cmake -DENABLE_COMPILE_FLAGS_FOR_TARGET=none ..
Unfortunately, I would expect that you may encounter further problems down the line.

Thanks, that worked.
Luckily I'm using the Zero just as an interface to get to the raw data from the sensor (still picture, not video), so for now it looks like I have all I need.

I'm closing this issue because I believe the original problem is duplicated here (https://github.com/raspberrypi/libcamera-apps/issues/46), and in this one we now have unrelated Pi Zero discussions. Please refer to the aforementioned issue for any updates. If the original issue wasn't the same (caused by the use of X forwarding), please feel free to re-open a new issue. Thanks!


package.json: add missing dependencies

Are these from some experimenting you were doing?

ts-node is never used for execution and seemingly not for tests (otherwise the checks would have failed for this PR).
gulp and chai are dependencies of many other modules. I'm not sure why they aren't installed automatically. They might not be required for execution, but without having them I get a lot of type resolution errors.
When type resolution doesn't work properly all the way through the code, it adversely affects code navigation and reference search (find usages, find derived, find interface implementations, etc.), When that doesn't work properly you might miss things when making changes and possibly make mistakes and miss certain things - especially when you're not deeply familiar with the code. In other words: it affects quality and I hate to make contributions with an aftermath that needs to be addressed.
That's actually the intention behind most of these PRs: getting it clean and correct (even at a higher level than it's required to run successfully). This will allow me to make future contributions at a higher quality than when I would just switch all those checks off.
Anyway, the individual changes are correct and justified, I think.

gulp and chai are dependencies of many other modules. I'm not sure why they aren't installed automatically. They might not be required for execution, but without having them I get a lot of type resolution errors.

They do not appear to be dependencies of anything in GGG since they are not installed.  Considering chai is an alternative to jest, with some naming overlaps, is there a configuration problem?  Still getting familiar with the files you provided to see if there is something missing from the .njsproj (jest as tester for example).
What kind of type resolution errors does gulp resolve?
No one has raised this issue and I am not seeing issues in Visual Studio (although I have not got it configured to run tests yet).  If there are configuration issues, it would be nice to get them resolved and a reference set of solution files could be posted in the wiki (just a suggested location) for anyone wanting to develop GGG using VS.

After deleting gulp. turbo-gulp and chai from the node_modules folder, I'm seeing this after a while (takes several minutes after VS start and opening a number of files in the lib folder:

Also, after deleting the modules, and before restarting VS, I have deleted the build, bin and obj folder.

Those 'missing' deps are in the devDependencies for @bcoe/v8-coverage.  Analysis tools should not be looking at code in node_modules should they?  Sorry but it may be a config issue for whatever tool is providing that window.  If it is standard VS, please tell me how to get there.  My project still says it is happy.

Made another test: it only happens with VS 2022, not with VS 2019 - interesting..

No differences in Settings >> Text Editor >> Javascript/TypeScript

Made another test: it only happens with VS 2022, not with VS 2019 - interesting..

Okay, I have recreated on VS 2022.  Need to figure out the cause.  It is not something missing from package.json.

This seems to be a new 'feature' of VS 2022.  Haven't found a specific issue opened for it but did find these instructions to get rid of the errors.
Check "only report diagnostics for files opened in the editor" in Tools -> Options -> Text Editor -> JavaScript/TypeScript -> Project -> General

Using excludes in tsconfig.json does not seem to stop the search for more tsconfig files.  btw, the tsconfig you sent has node-modules  instead of node_modules in the excludes.

That option already existed in VS 2019...

That option already existed in VS 2019...

Agreed.  The doc indicates there was a bit of change in the ts/js tooling for 2022.  I saw that suggestion on an MS VS page (which I can't find anymore) and in the community pages.  I suggested it because it got rid of the extra errors for me.

That option already existed in VS 2019...

Agreed. The doc indicates there was a bit of change in the ts/js tooling for 2022. I saw that suggestion on an MS VS page (which I can't find anymore) and in the community pages. I suggested it because it got rid of the extra errors for me.

Probably only as long as you don't open the code files?
Meanwhile I tried something else:
I started from a package.json with all module dependencies being empty. From there, I only added those that are required to compile the code and I ended up with this:
  "devDependencies": {
    "@types/html-to-text": "^8.0.1",
    "@types/json-stable-stringify": "^1.0.33",
    "@types/libqp": "^1.1.1",
    "@types/marked": "^4.0.1",
    "@types/nodemailer": "^6.4.4",
    "@types/rfc2047": "^2.0.1",
    "typescript": "^4.5.4"
  },
  "dependencies": {
    "@octokit/auth-app": "^3.6.1",
    "@octokit/rest": "^18.12.0",
    "commander": "^8.3.0",
    "dugite": "^1.104.0",
    "html-to-text": "^8.1.0",
    "libqp": "^1.1.0",
    "marked": "^4.0.8",
    "nodemailer": "^6.7.2",
    "rfc2047": "^3.0.1"
  },
  "engines": {
    "node": ">= 16.0.0"
  }

=> No more errors in VS 2022!
Of course it's lacking the modules for running the tests now. But at least it's a clean starting point..

The errors appear after adding
    "jest": "^27.4.5",
    "ts-jest": "^27.1.2",

to the dev-dependencies

Probably only as long as you don't open the code files?

I get some 'errors' when opening files but not the 40+ errors related to the deps you identified.  The errors relate to ggg files and not deps.  Are you saying there was no change for you with that option?

Probably only as long as you don't open the code files?

I get some 'errors' when opening files but not the 40+ errors related to the deps you identified. The errors relate to ggg files and not deps. Are you saying there was no change for you with that option?

I haven't tried that option yet. The concern that I have regarding that option is that it might also affect code navigation and reference search. I can try that, but it's interesting that it's "jest" which is causing all this.

I haven't tried that option yet. The concern that I have regarding that option is that it might also affect code navigation and reference search.

Not seeing any issue.

it's interesting that it's "jest" which is causing all this.

Sorry I do not see the relation to "jest".  It is just a package with lots of deps.  The errors are only on packages which have a tsconfig file.  There are a couple of packages with a tsconfig that do not get errors, just to make sure we are confused.

Sorry I do not see the relation to "jest".

See above. With this dependency set, there aren't any errors: https://github.com/gitgitgadget/gitgitgadget/pull/822#issuecomment-1001814751
The errors are only appearing after adding
 "jest": "^27.4.5",
 "ts-jest": "^27.1.2",

to package.json
(of course you need to delete bin,obj, build, and node_modules when testing this)

We don't need to go crazy about VS issues, though.
We can just stick to VS 2019 for now, and in one or a few months they might have addressed this in VS 2022 anyway :-)

Okay.  @dscho can comment on the use of ts-node but the rest of this seems moot.  Need to look at the more minimal deps/devdeps you identified.

Okay. @dscho can comment on the use of ts-node

From my understanding, ts-node is obsolete, because the pre-transpiled output is used for execution rather than jit'ed ts files.
Otherwise, yes - I'll use VS 2019 and avoid further headache..

@dscho can comment on the use of ts-node

I use this for running manual tests via ts-node script/misc-helper.ts [...]...

Ah alright, understood. Closed it anyway and for the VS2022 problem: somebody else will get sufficiently annoyed by this sooner or later and get it fixed by MS.


Compatibility with PyTorch 0.4.1

On newest PyTorch PackedSequence takes in *args so the current constructor calls don't work anymore (although it shouldn't really be constructed from user land). This patch fixes that.
Also see the relevant https://github.com/pytorch/pytorch/pull/9864 that adds support for this on master. However, that patch isn't making into the new release we (the PyTorch team) are preparing so this change will be needed for the upcoming released PyTorch.

Thanks for that (and for all the amazing work you guys are doing)!


[AIRFLOW-899] Tasks in SCHEDULED state should be white in the UI instead of black

Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-899

Tasks in SCHEDULED state should be white in the UI instead of black
Testing Done:

Spun up a webserver

@artwr @bolkedebruin @criccomini

LGTM


First load of the GHPRI view leave it empty for ~3 seconds

We could make it much snappier by immediately rendering the sections:
https://github.com/microsoft/vscode-pull-request-github/assets/22350/3324ecdc-4054-4691-a5ef-70d6085ef320

Hi @joaomoreno, my machine can consistently load this in under 1 sec. It looks like you're using VS-Code in the browser which is honestly notoriously slow, would definitely recommend using the desktop version if not already. Also, my VS Code can take up to 3/4 secs to load this extension, but this is because I have just booted VS code or because I have a lot of RAM Usage from the docker containers I always have running on my machine. Point being, just because it's a little slow to load, doesn't mean its an issue with the code (even though there may be room for optimization).

@joaomoreno this delay is actually coming from the AsyncDataTree. When refreshing a node that has children, the node itself is not rendered until the children are all fetched:
https://github.com/microsoft/vscode/blob/9b8e5929399fe620b61e84dbafa81989d5893817/src/vs/base/browser/ui/tree/asyncDataTree.ts#L835-L877


Large Word LM Training

Hi, I noticed that the large_word_lm model in the folder example/rnn/ has been modified recently. However, the perplexity increases at this version. Could anyone explain the differences between two versions?
Moreover, I ran the codes on p3.8xlarge instance and found that the validation process takes much more time than before. Why is it? Previously the whole validation takes only about 10 minutes, but now it's more than 2 hours.
Thanks.

For questions, please submit on MXNet discussion forum (https://discuss.mxnet.io), where it will get a wider audience and allow other to learn as well.
I'm closing this issue now in favor of the discussion forum issue you will file, please feel free to re-open if closed in error.
Thanks!
@sandeep-krishnamurthy please close this issue


House Robber 3

Pull Request Template
Description
Solution to the House Robber 3 question on leetcode.
Interesting Tree DP problem
Problem: Find the maximum possible sum of non-adjacent nodes
Approach: Recursive memorized DP approach used to solve.
Topic: Binary Tree, DP
Level: Medium
Put check marks:
Have you made changes in README file ?

[X] Added problem & solution under correct topic.
[X] Specified Space & Time complexity.
[X] Specified difficulty level, tag & Note(if any).

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[X] Test A: Passes all test on the website
[X] Test B: Checked on custom corner cases as well

Make sure all below guidelines are followed else PR will get Reject:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code so that it is easy to understand
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] Any dependent changes have been merged and published in downstream modules

Not looking good

Umm sorry, what else do you want me to improve upon?
What is not good? @GouravRusiya30


Patch CVE-2023-41910 in lldpd package (#6205 cherry-pick)

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[X] The toolchain has been rebuilt successfully (or no changes were made to it)
[X] The toolchain/worker package manifests are up-to-date
[X] Any updated packages successfully build (or no packages were changed)
[X] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[X] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[X] All package sources are available
[X] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[X] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[X] All source files have up-to-date hashes in the *.signatures.json files
[X] sudo make go-tidy-all and sudo make go-test-coverage pass
[X] Documentation has been updated to match any changes to the build system
[X] Ready to merge

Summary

Cherry-pick of #6205 into the fast-track branch.
Change Log

Patched CVE from the title.

Does this affect the toolchain?

No.
Associated issues

#6205

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2023-41910

Test Methodology

Relying on testing for #6205.

Skipping PR check - the package built correctly and had no tests to run. The check failed for unrelated reasons and I'll be debugging the issue.


docs (label_replace): illustrate use of named capturing group

Illustrate use of named capturing group syntax available from https://github.com/google/re2/wiki/Syntax and their usage in the replacement field
Signed-off-by: Guillaume Berche<EMAIL_ADDRESS>

Thank you for your pull request.
Our documentation is not meant as a replacement for re2 syntax and I feel like dropping such an example would be more confusing for users. In addition, for the very vast majority of usecases, named groups are not needed since label replace deals with simple replacements.

thanks for your review. The proposed changed does not aim at duplicating RE2 syntax, but to rather confirm that named groups can be accessed by $name. I had to guess it as only indexed group reference such as $1 were documented.
I've added a commit to remove the example and only keep the description refinement.

We have discussed this during our bug scrub. We found out that it is confusing that this pull request does not explain how to do capturing groups. Maybe the sentence should be moved to a dedicated example showing the usage of named capturing groups, WDYT?

We have discussed this during our bug scrub. We found out that it is confusing that this pull request does not explain how to do capturing groups. Maybe the sentence should be moved to a dedicated example showing the usage of named capturing groups, WDYT?

Thanks @roidelapluie the original change at https://github.com/prometheus/prometheus/pull/11404/commits/ea40c15fe9d69273281bda41ab3e300087156ec8 explained usage of named group by comparing it with syntax without named group.
Is it what what expected during the bug scrub ?

Can we maybe split the named capture group into a second exemple with the explanation?

Can you please review https://github.com/prometheus/prometheus/pull/11404/commits/60b380da70213975bfd343be64f5b89b03e2c944 ?
Feel free to squash / edit as needed if this can be faster or more productive.

Thanks!


feat(temporary-shipping-address): add instruction on how to do it

This PR add documentation on how to set up temporary shipping address in checkout

Added page


Fix failing IE6 test

It was a false positive. Our “location” parsing uses an A tag, which doesn’t always work the way the real location parsing does.

@jashkenas: I think after this, we're good to ship a v1.2.1.

Fantastic. Thanks @jridgewell!


Issue in user tests with _.some()

Hi,
In your tests you implement the following function:
async function format(user) {
    const formated = user;
    // delete password
    delete formated.password;
    // get users from database
    const dbUser = (await User.findOne({ email: user.email })).transform();
    // remove null and undefined properties
    return omitBy(dbUser, isNil);
}

then you use it in _.some() to check if an object is included in res.body:
const bran = format(dbUsers.branStark);
const john = format(dbUsers.jonSnow);

const includesBranStark = some(res.body, bran);
const includesjonSnow = some(res.body, john);

Since format() is an async function, it returns a Promise, and when used as a predicate in _.some(), it will always return true, which makes the test incorrect.

That's right, I forgot to await the Promise. Do you want to submit a PR?

Opening for hacktoberfest.


feat(Download Private files): Accesible private files via token

Download private file via token as query string. "t" as the token.
sample url: ....../private/files/FB-DE-00037_Abschnitt_6.docx?t=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzZWNyZXQiOiI1YjMzZmFmMjFkYzczNGEiLCJ1c2VyX2lkIjoicm9uZWwuY2FicmVyYUBuZXdtYXRpay5jb20iLCJrZXkiOiJlY2FlZmYwOGYyMGY4ZjMiLCJleHAiOjE1NTY4NTM3NzN9.EPiwB5S2hb7vIVrWrlsmqmff3n7K8pGtPzXBi5HKsVw
https://github.com/newmatik/next/issues/461

you want so hard to change this validate_jwt :)

@kickapoo its not much that I changed actually, just token be a parameter so the function be reusable. The other function is used as the token is not on the headers, and the other is using the others. Thats the only change I made.

Closing PR. Approaching this at endpoints. Solution is to replicate the functions called at the endpoint.


Show the right version link for users.

Type of Issue

[x] Documentation incomplete

Introduction to the issue
I think the link in README.md still points to old version of the extension, the update last time is 2021.6.11 and the version is 1.0.1. We should update the doc so users can use the right version.
And also the link in update notification is also the old version URL, should update it too.

@wxharry Thanks! You are so welcomed to improve the documents of hypercrx, and maybe you would like to begin this work after this new feature(#301) is merged.

My pleasure. Maybe I can start with replacing the old links.


Use correct ID for OS X message when writing BLE characteristic with response

When using the OS X XPC API to write a BLE characteristic, you must use the ID 66 in both cases: when expecting a response, and also without response. This PR corrects that problem.

Reminder this PR needs review. Thank you!

Pinging @moogle19 or @hasty please review. Thank you!

Is this true on all versions of OS X? They've changed it in the past between versions.

Hi @hasty it is for sure true for OS X Yosemite and newer. Not sure about older OS X versions that that.

OK, works for me.


Create a webcomponents guide tailored to usage with Elm

gampleman suggested on discourse to add a focused webcomponents how-to specifically for Elm. I really like this
https://discourse.elm-lang.org/t/improved-documentation-for-flags-ports-and-custom-elements/5552/5

[x] Look for good concise tutorials for the specific parts we actually need from the spec, maybe they're out there

[ ] Also mention that extending builtin elements is a problem because of Safari https://bugs.webkit.org/show_bug.cgi?id=182671 which kind of has a polyfill https://github.com/ungap/custom-elements-builtin

Mentioned in https://discourse.elm-lang.org/t/why-im-stepping-away-from-elm/5587/8

[ ] Is this within scope for the repo?
[ ] Do the thing?
[ ] Review?

Still no nice tutorials out there that I can find with my google foo.

Suggestion: Extended built-ins cannot be used from Elm since the vdom library doesn't support it

Suggestion:
I think it'd read better if there was a newline after the first sentence.
You can also trim that sentence down so people will get a clear understanding of what they are reading more quickly. For example.
Current:

This document is meant to be a practical usage guide to the various web components specs with the goal to provide you with the necessary tools to interop with web APIs that are not yet covered by Elm's core packages. The reason this guide exists is that most tutorials and documentation on web components just dump all the specs and some basic usage examples on you assuming that you already know the intricate details of why specific parts of the spec exist in the first place and what use case they try to solve. This situation can be daunting even for experienced web developers and even more so for newcomers. We aim to be as concise as possible while also providing sufficient information to get you up and running in no time.

Alternative:

This is a practical guide to the somewhat confusing web component specs.

Most documentation on web components show the spec and a basic usage example, assuming that you already know the intricate details of why specific parts of the spec exist in the first place and what use case they try to solve. This situation can be daunting even for experienced web developers and even more so for newcomers.

This document tries to be as concise as possible, while also providing enough information to get you up and running.

Generally, I'd go through and try to tighten things up. Can any words be dropped? Can any sentences become bulleted lists? Are the places where a paragraph can be broken up? I personally think all these things make for easier reading in online documentation.

Suggestion: I do think the beginning portion is a little too long, specificay regarding things like the history of import and require.

https://github.com/elm/virtual-dom/issues/156


i18n(ko-KR): update integrations-reference.mdx

Description (required)

update integrations-reference.mdx
#9081

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
reference/integrations-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Missing commands for dynamodb-table-copy-utilities in ./bin

The table copy util readme contains the following steps:

npm install
Run commands in ./bin

After running npm install a bin directory is not created nor do I see any code with implementation for the command line client in the repository.
I see references in the Nanny lib for /opt/dynamodb-tablecopy/DynamoDBTableCopyUtilities/bin/copy_table but cannot find any relevant implementation.
Is the complete source for the command line client supposed to be contained in this repo or have I overlooked something?

TableCopyUtilities is currently a set of NodeJS scripts that you can execute from a command line environment with node installed.  The command 'npm install' is simply gathering the dependencies for the scripts, but the bin directory is should already exist.  After installing the dependencies, you should be able to execute a command like ./bin/copy_table [args ...]

Thanks, but I do not see a bin directory currently checked in to the repository.

Sorry about that, we just noticed this oversight.  Thanks for pointing this out!  We just pushed the bin directory so it should be there now.  Closing the issue, but feel free to reopen if you have any other concerns.

Thanks @raymolin!


Failed assertion: line 4264 pos 14: 'owner._debugCurrentBuildTarget == this': is not true.

@Vivekbhatia-bit
can you provide your flutter doctor -v and your flutter run -v

@Vivekbhatia-bit
can you provide your flutter doctor -v and your flutter run -v

Hi @Vivekbhatia-bit
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Hi @Vivekbhatia-bit
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Bump lit-helpers to support lit@3

Hi, anything I can do to get this released to support Lit 3?

A PR moving ^2.0.0 listings to ^2.0.0 || ^3.0.0 would be a great start.
Any thoughts you’d have on a testing path for both versions would be great to hear as well!

When we can expect you will merge this PR and we get updates.
Thanks


node first_auth not working correctly

I'm still somewhat new to these, but this is my 3rd basic MM build and for some reason I'm having issues with getting this module up and running this time around.
I have it running just fine on another setup, as well I have the MMM-NowPlayingOnSpotify module up and running just fine, though I seem to be running into the issue at the Get Auth stage.
I initially thought it may have been the Client ID being used in 2 other MM modules. So I started fresh with installing the module and creating a new app within the Spotify Dev Dashboard. Everything goes smoothly until I go to the Get Auth stage. When I run that per the instructions I get the error:
/MagicMirror/modules/MMM-Spotify $ node first_auth.js
internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module 'request'
Require stack:
- /home/pi/MagicMirror/modules/MMM-Spotify/Spotify.js
- /home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:746:27)
    at Module.require (internal/modules/cjs/loader.js:974:19)
    at require (internal/modules/cjs/helpers.js:92:18)
    at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Spotify/Spotify.js:9:17)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:14)
    at Module.require (internal/modules/cjs/loader.js:974:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/pi/MagicMirror/modules/MMM-Spotify/Spotify.js',
    '/home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js'
  ]
}

Interesting. Can you try installing the missing module manually:
npm install request

That did the trick! Thank you for the quick response on this! @skuethe #

I am re-opening this issue, as this needs some code adjustments, so other people don't run into this issue in the future :)
Will then close it with a PR.


printColor(...) doesn't respect print type constants

# _HUD_PRINTCENTER, _HUD_PRINTCONSOLE, _HUD_PRINTNOTIFY, _HUD_PRINTTALK

printColor(array(_HUD_PRINTCONSOLE, vec(0,255,0), "what1"))
printColor(_HUD_PRINTCONSOLE,vec(255,0,0), "what2")
print(_HUD_PRINTCONSOLE, "what3")

I'm not entirely sure how all of those constants should work, as console print is the only one I use.

do these other places even support color?

Unlikely, but console should be fixed.

well, it's not easy. if you introduce a number parameter, you break everyone's code that puts a number there.

Ideally, those constants would have a special type that's not used for anything else, but that wasn't thought of either in the original implementation, so if you introduce that type now, you'd break code that stores those constants in a number variable

Warning! Decimal values are for reference only! The actual value may be different between two Garry's Mod versions.
Why not slap that warning everywhere haha.

It does, however there's an issue that if someone originally used a number as the first argument to printColor it would now be interpreted as a print type.

Honestly, if you're using print color, for the default color what's the point?
In my time running a few servers, most who've asked me for help wanted _HUD_PRINTCONSOLE to print to color in the console, they asked me how I could work around it and I said you can't really.
I see why for backwards compatibility but honestly this train of thinking could result in us constantly thinking that for every change. I've seen it happen, a lot has changed and if your contraption breaks because of a print statement you need to recode it anyways.

printColor in console would be MsgC

What should the new function be called?

printColorC maybe


Fixing postprocess() interface in README template.

:rocket: What
This PR corrects a small interface definition in the README template. Instead of referencing postprocess(request) we now reference postprocess(response) in alignment with eg truss.model_wrapper (see code).

:computer: How
Editing a jinja template to correct some templated text.

:microscope: Testing
Looked for details on where this template might be used, but couldn't find any! git grep throughout the codebase only surfaced readme_generator and truss_handle references. Maybe this is auto-generated for user trusses?

The change looks good, but you need to update some tests truss/tests/test_truss_handle.py::test_readme_generation**.


How do I associate .ps1 files with the Powershell executable?

How do I associate .ps1 files with the Powershell executable?
I installed Powershell from the Microsoft Store, and when I double click on .ps1 files, the "Select an app to open this .ps1 file" context menu appears, but I don't see Powershell as an option on it
Originally posted by @TechPro424 in https://github.com/PowerShell/PowerShell/discussions/19870

I tried looking into this as I alsi have installed PowerShell from the store too (& the preview version) but neither of them can be picked in the picker as part of the Default App settings page either. I think this is something with how PowerShell gets registered on install and this will need further investigation


Feature/perlcritic compliance

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
if you change the schema you must patch the test databases as well, see Updating the schema
the PR must not fail unit testing

Description
Relax constraint at a global level to allow mapper to pass. Refactor some parsers to make them fully compliant.
Use case
perlcritic is failing but cannot waste time at the moment to make it pass the test on the mapper. We have to focus at the moment on getting the thing done. This introduces a temporary relaxation at a global level which prevent to disable critic at file level so that it's more likely we don't forget to address the issue at a later stage.
At the same time, it fixes some critics on various parsers and make them pass the critic.
Benefits
One step closer to having the full test suit pass.
Possible Drawbacks
We have to remember to address the temporarily disabled critic.
Testing
Have you added/modified unit tests to test the changes?
No
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?
Yes, except the usual apache bookkeeping and pod failures.

@magaliruffier This is now properly addressed. Species name had to be promoted to required argument and be provided during the test.

Sorry spoke too early, the arrayexpress test fails, reverting to previous commit.

Something strange happens here, github doesn't pick my changes to the parser.

Finally github's showing the diffs with the updates on my remote branch.

@avullo Where are we at with this?

I have addressed @magaliruffier comments and, even if there's no other reviewer, Mark should be the most likely one. His remaining concern is addressed by the PR itself, as he's asked to create a separate one instead of me introducing perlcritic related changes to other modules in the feature/basic_mapper PR.

I approve but please attend to the conflict


upgrade intel19 container

Intel just released version 19.1 as part of parallel studio 2020.  See if this fixes the silent install bug.  If so, then consider moving the intel CI testing to intel 19 instead of intel 17

The bug is still there in the latest intel parallel studio 2020.1.  So, specifying the components in the silent config file does not work.  At the suggestion of someone on Intel Developer Zone, I also tried specifying the components on the command line with the --components option to install.sh.  But, this did not work either. I also tried using the _online customizable version of the intel PS tarball but this did not work.
What did work was to just remove the unwanted directories from /opt/intel.   A PR is coming soon and then this issue can be closed


initial version more mobile friendly version

ionic based demo

@corinnekrych want to give it a spin?

RHMAP-2057

:eyes:

@edewit as discussed:
+1 for the new design (maybe change navigation bar color from black to red to fit with ios/android style)
some issue with data structure:

at creation "created" field should appear when lookin in data browser
at update, no id field should be added to data structure when looking in remote data browser

+1
it works nicely now1
ready to merge


Make semantic validations optional

I use this library to convert CSV data to STIX formatted input. Sometimes the CSV file contains semantically invalid data (for example valid_from > valid_until). In this case the library raise a ValueError.
I think it would be better if semantic validation can be switched off (maybe with a warning message) with a global or local flag.
At least I'd like to suppress the following exception types: ValueError, InvalidValueError, AttributeError.
In the CTI platform I have to ingest STIX data, there is an option the accept non-compliant objects. So I would like to defer this decision from development time to application operation time.
What do you think?

I wrote to the wrong repo. Sorry.

The library is supposed to the model STIX library others can learn from.
Suppressing those exception types would allow a large swath of invalid
content.
We suggested for your purposes that you fork the repo and catch those errors yourself.

Fair enough. Thanks, I will do it.


Nerf the fridge explosion resistance

About the PR

Nerfs the fridges explosion resistance. I keep seeing nuke ops. Even on salamander. Bringing over a fridge RIGHT next to the nuke. And the fridge just tanks it all.
Right now you need 4 NUKES RIGHT NEXT TO THE FRIDGE before it even breaks.
The fridge is being abused. Nuke ops should be trying to run away from the nuke before the explodes or die in glory. Not get in a fridge. Crew should be trying their best to escape.
At least take the fridge further away so that the damage does not effect them.
I don't care that's an Indiana jones reference. It is being abused
You can still survive a c4 right ontop of it and get minimal damage.
Btw unrelated this will be my 100th ever merged pr if it gets merged before anything else
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: The fridge's explosion resistance has been nerfed significantly, It's no longer able to survive nukes at point blank range of the nuke.

Now disposals bins will be used instead of fridges since i think they never fixed that?

Now disposals bins will be used instead of fridges since i think they never fixed that?

Nope it's been fixed

i'm pretty sure this just makes it unable to tank anything at all from earlier testing

50% damage reduction is better than 99% so find a better one if you want it back.

since vasilis said it takes 4 nukes 96% should be good

since vasilis said it takes 4 nukes 96% should be good

It can tank a c4 right on it

since vasilis said it takes 4 nukes 96% should be good

It can tank a c4 right on it

yes so, in what situation would one use a fridge against c-4?

since vasilis said it takes 4 nukes 96% should be good

It can tank a c4 right on it

yes so, in what situation would one use a fridge against c-4?

To... Escape a c4?

ah yes the realest scenario

be pro
see a c4 ticking somewhere
break into the kitchen
steal the freezer and crit the chef
bring the freezer to the c4
hop in seconds before it explodes (300s timer)

ah yes the realest scenario

be pro
see a c4 ticking somewhere
break into the kitchen
steal the freezer and crit the chef
bring the freezer to the c4
hop in seconds before it explodes (300s timer)

yeah i even spoke about this on the PR that added the explosion resistance, there's no reasonable scenario where you would use a fridge against c-4
a fridge would only protect you against bombs if you literally just carried a fridge with you all the time, and it's otherwise weak to everything else so any potential enemy could still just destroy it
and even if there was a fridge next to you and someone tried to bomb you, just running away would actually be better than hiding in the fridge
a fridge would only reasonably be used to protect against a syndicate bomb, if you somehow happen to realise a syndicate bomb with less than 10 seconds left (so you can't run away) is next to you and you are next to a fridge getting to which would be faster than running away

Surely the core of the issue is that bringing a freezer to the epicenter of a nuclear blast with the explicit intention of hiding inside of it is NRP behavior?

 Or if it does make it like from really far away of the nuke
It's still relatively strong but not too strong for people to choose to go into the fridge instead of running away
I was under the assumption that 50% was fine from 99%. If you think I'm wrong at least make sure the fridge can't be abused when making a new value.

Surely the core of the issue is that bringing a freezer to the epicenter of a nuclear blast with the explicit intention of hiding inside of it is NRP behavior?

why would it be? surviving past roundend, which normally happens together with nuclear explosions, has no gameplay incentive (or "win"-incentive), meaning there are only RP reasons why you would do it

Surely the core of the issue is that bringing a freezer to the epicenter of a nuclear blast with the explicit intention of hiding inside of it is NRP behavior?

why would it be? surviving past roundend, which normally happens together with nuclear explosions, has no gameplay incentive (or "win"-incentive), meaning there are only RP reasons why you would do it

Typically if you want to do that in-character you should get on your nukie shuttle/the cargo shuttle and GTFO. No sane spessman of ANY FACTION would reasonably think in-universe "let's steal a temperature insulated steel box and put it next to a device designed to irreversibly vaporize everything that exists within a several mile radius, it'll be fine".

If you wanna figure out a new blast resistance number make sure it's
1.  Or if it does make it like from really far away of the nuke

2. It's still relatively strong but not too strong for people to choose to go into the fridge instead of running away
   I was under the assumption that 50% was fine from 99%. If you think I'm wrong at least make sure the fridge can't be abused when making a new value.

surviving a nuclear blast was the intent, and even though i would agree on having it only survive nukes at a distance, that would be pretty hard to do well due to how explosion intensity works: 1) surviving will be easy on large stations and very hard on small stations 2) it will depend on where exactly you hide and will be highly unreliable due to that
either way, i think 95% or 96% resistance should work well for requiring it to be at a distance or behind walls

Surely the core of the issue is that bringing a freezer to the epicenter of a nuclear blast with the explicit intention of hiding inside of it is NRP behavior?

why would it be? surviving past roundend, which normally happens together with nuclear explosions, has no gameplay incentive (or "win"-incentive), meaning there are only RP reasons why you would do it

Typically if you want to do that in-character you should get on your nukie shuttle/the cargo shuttle and GTFO. No sane spessman of ANY FACTION would reasonably think in-universe "let's steal a temperature insulated steel box and put it next to a device designed to irreversibly vaporize everything that exists within a several mile radius, it'll be fine".

it's a reference since indiana jones did think that and it worked, and things aren't supposed to require to make perfect sense in-universe, else we'd not have half of the content we do

why does it matter balance wise if you survive a nuclear blast? it's a neat reference and the round ends anyways

why does it matter balance wise if you survive a nuclear blast? it's a neat reference and the round ends anyways

it doesn't, hence the discussion here revolves around it mattering realism-wise

My problem was that nukies were using it to survive the blast instead of running away back to their ship. This nerfed significantly
I know it's a reference to Indiana jones and I found it funny. But at the point where the joke is just abused I had to put an end to it... I literally saw it in like every nuke ops round

Bikeshedding here is pointless.


More than once the same filter?

Hi, is there an easy way to have two external filters for the same column? Atm from what I understood with filter_container_id you can only have 1..

Thanks for your reply. I followed a different solution. I just move around the filter by changing the div's css as a temporary solution.. Does the job so I am happy atm..

Actually,  you can give a try to the initMultipleColumns, you can use it for a single colum too, just provide different containers ids and cross your fingers. But you should know that is no state saving support for those filters. Read docs for usage sample
https://github.com/vedmack/yadcf/blob/master/lab/jquery.dataTables.yadcf.js#L255


Added rabbitmq-delayed-message-exchange plugin support to create delay messages.

@s3rius Please take a look


QuickSwitch is unusable without mouse (defeats the purpose of quick switching!)

Bug description:
The QuickSwitch feature/modal/overlay is present for power users (in my understanding, those who like to use without mouse) to quickly navigate between different services. On my mac, when I open this with Cmd+S, the focus is not on the text box that is used to filter the services. As I type any characters, the list doesn't get filtered. I am forced to use the mouse to click into the text box, start typing, and once the shortlisted choices are present, I am forced to use the mouse again to click on a selection / service.
Steps to reproduce:

Setup a few services in Ferdi
Open the QuickSwitch overlay
Start typing
See error

Expected behavior

Once the overlay pops up, any typing should filter the available services. The up/down arrow keys without modifiers should be used to traverse the shortlisted options, and enter press should go to that service.
Screenshots

Environment:

Operating System:

Ferdi Version:

Server:

Debug information:

Duplicate of #322.
This is a known bug which we unfortunately cannot fix: Electron does not allow Ferdi to focus the box if the focus is currently inside a webview. If you find a way to do this, please let us know, but we already tried many suggestions in related electron issues.
Related:
https://github.com/electron/electron/issues/17882
https://github.com/getferdi/ferdi/issues/68#issuecomment-534146281
https://github.com/getferdi/ferdi/blob/1fea645b0b94e52a31158d47d0ad921110dfa95e/src/features/quickSwitch/Component.js#L232-L235


[Feature]: Support codesandbox to provide interactive examples

Package Scope
docs

[x] Add to an existing package
[ ] New package

Package name:
Overview

Describe the solution you'd like

Additional context

@minsoo-web How about making Pull Request for adding codesandbox embed in documentation
Let's make our documentation like Panda CSS. Can I assign you with me?

Of course. It is my pleasure. I will do my best 🚀🚀🚀

How about like this case ?
https://polaris.shopify.com/components/typography/text

ref https://github.com/codesandbox/sandpack

@minsoo-web Could I assign you for v2 docs soon?
@sonsurim We need someone have no experience for this library to see how difficulty to onboard with this. Could you be the one to see it objectively?

@minsoo-web Could I assign you for v2 docs soon?

Of course, I'll work on it

@sonsurim We need someone have no experience for this library to see how difficulty to onboard with this. Could you be the one to see it objectively?

@manudeli
Sure, that's great, I'll see it out and leave a comment!

@manudeli I was just wondering, Can I see it when it's done?

@manudeli I was just wondering, Could I see it when it's done?

I guess it's done, v2 will be release until at least in March, After then We need to do this work(codesandbox for interactive examples) in v2

reference
https://github.com/TanStack/query/blob/main/.codesandbox/ci.json

@manudeli
I'd like to ask for your opinion, the docs of @chara-ui/react, which I'm using as a reference, are provided as a library called react-live. I'm impressed that you can add scope, so that you can modify only the code blocks you need without separate function declarations and import syntax.
However, I think the import syntax is necessary information for the user, and the function declaration and use-case should also show the entire code. I'd love to hear your thoughts on whether using react-live or sandpack is the right way to go!

@minsoo-web This issue is important. share plan please if you can

@kangju2000 @minsoo-web Make and share plan to implement this feature on https://suspensive.org/ please

The differences in markdown rules on react.dev are as follows:

Import Sandpack component at the top
Pass dependencies as component props (on react.dev, these are written in code blocks)

@manudeli @minsoo-web
While searching for references, I came across a plugin called remark-sandpack
On react.dev, they compile MDX directly, but since Suspensive uses Nextra, we can attach the remark plugin.
If you use the plugin, here's how to do it:
Register remark plugin
next.config.js
// eslint-disable-next-line @typescript-eslint/no-var-requires, import/order
const { remarkSandpack } = require('remark-sandpack')

// eslint-disable-next-line @typescript-eslint/no-var-requires, @typescript-eslint/no-unsafe-assignment, import/order
const withNextra = require('nextra')({
  theme: 'nextra-theme-docs',
  themeConfig: './theme.config.tsx',
  defaultShowCopyCode: true,
+  mdxOptions: {
+    remarkPlugins: [remarkSandpack],
+  },
})

/** @type {import('next').NextConfig} */
module.exports = withNextra({
  i18n: {
    locales: ['en', 'ko'],
    defaultLocale: 'en',
  },
})

Usage
import { Sandpack } from '@/components'

<Sandpack
  customSetup={{
    dependencies: {
      '@suspensive/react': 'latest',
      '@suspensive/react-query': 'latest',
      '@tanstack/react-query': '^4.0.0',
    },
  }}
>

```js /App.tsx
import Example from './Example'
import { QueryClient, QueryClientProvider } from '@tanstack/react-query'
const queryClient = new QueryClient()

export default function App() {
  return (
    <QueryClientProvider client={queryClient}>
      <Example />
    </QueryClientProvider>
  )
}

import { wrap } from '@suspensive/react'
import { useSuspenseQuery } from '@suspensive/react-query'
import { api } from './api'

export default wrap
  .ErrorBoundaryGroup({ blockOutside: false })
  .ErrorBoundary({ fallback: ({ error }) => <>{error.message}</> })
  .Suspense({ fallback: <>loading...</>, clientOnly: true })
  .on(() => {
    const query = useSuspenseQuery({
      queryKey: ['key'],
      queryFn: () => api.text(),
    })
    return <>{query.data.text}</>
  })

export const api = {
  text: async () => {
    await new Promise((resolve) => setTimeout(resolve, 1000))
    return { text: 'Hello, Suspensive!' }
  },
}

```
Result
2024-06-<IP_ADDRESS>.mov
How about using this instead of implementing it ourselves?

Wow.........!!!!!!!!! So much coooo! Could you make Pull Request too?

@kangju2000
Could you make playgrounds of Suspensive 1 page by 1 page or 1 feature by 1 feaure please?

[ ] @suspensive/react

[ ] Migrating to v2
[ ] <Suspense />
[x] <ErrorBoundary />
[x] <ErrorBoundaryGroup />
[ ] <Delay />
[ ] <SuspensiveProvider />
[ ] <DevMode />
[ ] wrap

[ ] @suspensive/react-query

[ ] Migrating to v2
[x] useSuspenseQuery
[x] useSuspenseQueries
[x] useSuspenseInfiniteQuery
[x] queryOptions
[ ] <SuspenseQuery />
[ ] <SuspenseQueries />
[ ] <SuspenseInfiniteQuery />
[ ] <QueryErrorBoundary />

[ ] @suspensive/react-await

[ ] <Await />

[ ] @suspensive/react-image

[ ] <Image />


Improving the index.html file

I would like to work on improving the index.html making it engaging for the users and make it more expressive. I would like to add features in it and make it more expressive.

I would like to work on this issue,  please assign this issue to me under GSSoC'23.

I have good hold on HTML, I can make it really optimized. Please assign me this issue.


User agent sniffer looks only for "Firefox", not "Mozilla"

Mozilla based off-brand browser users are told that MathJax isn't supported by their browser.  I had to go into about:config and set general.useragent.compatMode.firefox to true for MathJax to render.  Shouldn't "Mozilla/5.0" be good enough?

The browser detection does not use the userAgent to identify Firefox,
but rather other identifying characteristics.  The problem is more
likely the version number rather than the Firefox detection itself,
since MathJax will give that message if the version is less than 3.0
(the earliest Firefox version that is supported).  So if your off-
brand browser version is less than that, that is probably the problem.
Can you say what browser you are using, and send me the userAgent
string that it usually produces?  I will see whether there is
something more that I can suggest.
As for "Mozilla/5.0", that is not good enough, because many browsers
identify as this (e.g., IE, Safari, Chrome in addition to Firefox), so
this does not really tell us anything.
Davide
On Oct 14, 2011, at 11:01 PM, wdkrnls wrote:

Mozilla based off-brand browser users are told that MathJax isn't
supported by their browser.  I had to go into about:config and set
general.useragent.compatMode.firefox to true for MathJax to render.
Shouldn't "Mozilla/5.0" be good enough?
--
Reply to this email directly or view it on GitHub:
https://github.com/mathjax/MathJax/issues/177

I am using Conkeror with XULRunner 7.0.  I was able to get around the issue with an about:config setting, but by default my user agent is:
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 conkeror/1.0pre

Thanks for the data.  It looks like MathJax will identify the browser as Firefox, but pick up the 1.0pre as the version number.
Can you use the debugging console to view the navigator object and tell me if there is a productSub value, and if so, what that is?  (One way would be to type javascript:alert(navigator.productSub) in the the URL location area at the top of the browser, but recent versions of Firefox don't allow that, so I'm not sure if Conkeror will or not.)
Davide

Typing the javascript:alert(navigator.productSub) into Conkeror's address bar returned 20110927.

OK, thanks.  I can probably have MathJax use that to determine a more accurate version.
Davide

This does not fix the issue on Debian (either stable or sid).
I am using xulrunner 8.0 but the Gecko string is still at 20100101:
Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 conkeror/1.0pre (Debian-1.0~~pre+git1111292307-~nightly1)

@dudebout:
OK, I've tried another approach.  See if my v2.0-candidate works better for you now.
Davide

This does use the correct buildID of my xulrunner.
This however does not give me the correct version since the case after your commit does not include 8.0.
It does allow my browser to load MathJax.
By the way, the version of my xulrunner is included in my user agent I think: the rv:8.0 part.

OK, thanks for checking.  There is very little in MathJax that depends on the version number.  For Firefox, it is basically only a test for 3.5 or above (which was when web-fonts were added), so things should still work for you.  The conversion to version number form buildID is approximate anyway, since that doesn't really tell you the Gecko version.  I'll add the 8.0, though.
Davide

Sounds good

I won't write a unit test for this issue since this is about a browser Conkeror on which the testsuite is not executed. I think it's enough if two users can confirm the fix.

Please note that the build date is now frozen following https://bugzilla.mozilla.org/show_bug.cgi?id=591537 as an intermediate step to have it removed in the future: https://bugzilla.mozilla.org/show_bug.cgi?id=572661


OpenFeign makes new spring-boot-docker-compose module to run service creation twice

Describe the bug
Running spring-boot-docker-compose dependency alongside spring-cloud-starter-openfeign makes docker-compose service creation to run twice. It produces The bean 'jdbcConnectionDetailsForXXXXDb1' could not be registered. A bean with that name has already been defined and overriding is disabled.
Sample
demo1.zip

Propably fixed in https://github.com/spring-cloud/spring-cloud-openfeign/pull/398

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Hi @OlgaMaciaszek, I had the same problem here. How can I use the 2022.0.4-SNAPSHOT? It's not published in Maven Central.

Hello @merorafael, you'll need to add  https://repo.spring.io/snapshot and https://repo.spring.io/ui/native/milestone to repositories in your build file.

I've tested against 2022.0.4-SNAPSHOT and Docker Lifecycle is started only once. Issue doesn't appear. @merorafael example pom attached if you want to check
spring-cloud-snapshot-test.txt


[#158791033] Bump stemcells to force NTP changes to apply.

What
This is being done to force the changes in https://github.com/alphagov/paas-bootstrap/pull/171 to apply (they only
take effect the next time the VMs are recreated.
This includes a bunch of ubuntu trusty updates. Nothing specifically
significant.
How to review
Code review is probably enough. I've already tested this in my dev environment.
Before merging
Ensure that https://github.com/alphagov/paas-bootstrap/pull/171 has been merged and applied in all persistent environments.
Who can review
Not me.

I've now merged and applied alphagov/paas-bootstrap#171, so this is good to go.


catalog-backend: fix sticky refresh state references

Co-authored-by: Fredrik Adelöw<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Replaces #15111 with this proposed fix. It's on top of the catalog storage refactor in #15143.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Reassigned to @jhaals


Add updateProfileOnSubmit prop for contentAccess component

This will be used mainly when there is a non logged in, but identified user being passed in that we dont want to be able to update the profile but rather pre pop the form and allow for them to easily submit data to the access route.

 Add ability to ask IdX contextual based questions.

 Adjust user flow for Identity-X form gating to avoid double-form for anonymous users


Why the Range operator won't work with one bound?

I'm trying to do a search on a DateTime field that's earlier than a defined value (like 01/01/2020), using RangeDateTime(). But for the sytax to work, I was forced to provide both Lt() and Gt(), which is unnecessary.  In fact, the Atlas Range operator requires only one bound (see an official example here), i.e., providing either the lower or upper is sufficient.
I believe having one bound will also solve another of my problems, which occurs when the DateTime field's value is null.  To get the null value document,
SearchBuilders<Entity>.Search.RangeDateTime(x => x.DeletionDate).Lt(DateTime.MinValue)
Note: null is less than 1 base on the mongosh output:   null < 1   (true)
Is there is way to use RangeDateTime with only one bound?
Thx.

This was an oversight in building the driver extension.  I'll look into adding this feature in a subsequent version.  (1.1.0 is largely finalized at this point, so it will probably be in 1.1.1 or 1.2.0.)