Import Gist that compares with Extensions proposal

I need to integrate this old Gist that compares this proposal with @hax’s Stage-1 Extensions proposal. There are a few problems with the Gist, too.
The biggest problem is, as per the Matrix discussion from two days ago and also discussion in #8, the document focuses too much on the security use case.
I’m going to redo this document to focus more on the general frequency of bind/call and how clunky they currently are.

@acutmore left a comment on the Gist, to which I’m replying here:

// The adversary’s code.
delete Set.prototype.slice;

I think this was supposed to be delete Set.prototype.has :)

Yes, the delete Set.prototype.slice is a mistake; thanks for catching it!

There is currently no way to harden trusted code against an adversary’s mutation of Function.prototype.call or Function.prototype.bind.

This is not entirely true. It can be hardened against it just relies on being able to run code before anyone else (just like capturing any global/method before it can be modified).
// at start before other code runs:
const uncurryThis = Function.bind.bind(Function.call);
  // f => Function.call.bind(f)
  // f => (…args) => f.call(…args)

// or
const {apply} = Reflect;
const uncurryThis = f => (that, …args) => apply(f, that, args);

// then
const setHas = uncurryThis(Set.prototype.has);

// later
setHas(new Set([1]), 1); // true

It is true that guarding against Function.prototype.call mutation is possible with Function.bind.bind. This is another old mistake which I’ll need to fix.
This guard requires wrapping every global method you use in an uncurried-this, à la @ljharb’s call-bind library, which is transitively used by a ton of websites.
So the argument that I need to make is that (1) this intrinsic call-binding is just one common use case of a very commonly used pair of functions (bind and call), and (2) it is very clunky and requires lots of clunky wrapping.
I do anticipate that the biggest argument against this will be “the method-wrapping is fine; just use the pipe operator if you want a fluent notation”. I am trying to think of ways to respond to that.

to me it’s really not about the postfix part, i just need a way to syntactically change the receiver of a function - it’s just that once that exists, it’s kind of silly to force the awkward ordering of .call when we could easily have natural o.a(b) ordering.

i just need a way to syntactically change the receiver of a function

@ljharb: If the ordering isn’t that important, then people will probably say, “Why do you need syntax to change your function’s receiver? Why not just keep using Function.call or your uncurryThis/callBind wrapper?” It’s already kind of happened in that Matrix conversation, too.
The best argument against that anti-argument that I can think of is developer ergonomics. Using Function.call/uncurryThis/callBind is weird, clunky, and obscuring. o->fn(a) or whatever is more ergonomic than Function.call(fn, o) because of the ordering resembles o.fn(a).
If it weren’t for that ergonomic difference, then it’s like what @acutmore said: everything is already possible in userland without syntax. (Possible inherent performance problems with wrapped functions notwithstanding, cf. #8.)

Part of it is robustness, and part of it is ergonomics. We have indisputable evidence that the current state of things is not ergonomic; nobody uses call/bind/apply when an arrow function or unsafe call suffices.


chore(deps): upgrade jenkins-x/jx3-pipeline-catalog to version 3.6.8

from: https://github.com/jenkins-x/jx

/retest


FIROAuthCredential nullability of properties are wrong.

[REQUIRED] Step 2: Describe your environment

Xcode version: All
Firebase SDK version: 4.0+
Library version: 4.0+
Firebase Product: auth

[REQUIRED] Step 3: Describe the problem
FIROAuthCredential has incorrect nullability for IDToken and accessToken. The constructor accepts a nullable NSString * for each, but the property is implicitly nonnull.

Note: This would surface a breaking change for Swift users if it is changed.


wasm: allow using empty vm_id to indicate the current WasmVM.

Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

/lgtm deps

@lizan PTAL.

/lgtm deps

This was lost after the merge with the main branch. @moderation could you approve again? Thanks!

/lgtm deps


Add the -max_tran_rate flag to support limit the max transmission rate in the server and client sides

Features
Supported

Local Disk
:white_check_mark:

Remote Disk Server
:white_check_mark:

Remote Disk Client
:white_check_mark:

Remote Push Server
:x:

Remote Push Client
:white_check_mark:

SFTP Pull Client
:white_check_mark:

SFTP Push Client
:white_check_mark:

MinIO Pull Client
:white_check_mark:

MinIO Push Client
:white_check_mark:

File Server
:white_check_mark:


Added Nicolau Copernic to domain list

Added Nicolau Copernic to domain list
https://copernic.cat/

@TheLaance First stage of verification passed, official domain is copernic.cat as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


some question about rnn

In your RNN folder, the

rnn_on_convnet_features_multi_frame.py,

https://github.com/saebrahimi/Emotion-Recognition-RNN/blob/master/RNN/rnn_on_convnet_features_multi_frame.py#L14
your code is from rnn_multi_frame import RNN, but I can not find the rnn_multi_frame module,
I think it should be from rnn import RNN

Sorry for the missing file. We experimented with a lot of settings including concatenating successive frames into windows but simple RNN with window size 1 worked best.
I uploaded the missing file.


[Hacktoberfest]: Add content for MongoDB - Advanced Aggregation Pipelines

📝 Issue Description
Add the following content for MongoDB Advanced Aggregation Pipelines under MongoDB

Overview of MongoDB Aggregation.
Pipeline Stages.
Working with $group and $match.
Advanced Operators like $lookup, $graphLookup, $facet.
Optimization Techniques for Aggregation Pipelines.

File you will be working on: src\content\docs\mongodb\advanced-aggregation-pipelines.mdx
🎯 Expected Outcome
The expected outcome is to add a comprehensive and well-documented section under MongoDB that covers the following topics:

Overview of MongoDB Aggregation: A brief introduction to what aggregation is and why it is used in MongoDB.
Pipeline Stages: Explanation of how aggregation pipelines are structured, with examples.
Working with $group and $match: Detailed explanation of these stages and how they can be used to group and filter documents.
Advanced Operators: Explore advanced operators such as $lookup for joins, $graphLookup for recursive searches, and $facet for multiple aggregations in one query.
Optimization Techniques: Provide tips and techniques for optimizing aggregation pipelines, focusing on performance considerations in large datasets.

The content should include examples where necessary, using MongoDB queries. Ensure it provides value to both intermediate and advanced MongoDB users. Please don't make use of the AIs.
🔧 Solution Guidance (Optional)
Make use of Astro Star Light Components
📋 Steps to Reproduce

Navigate to src\content\docs\mongodb\advanced-aggregation-pipelines.mdx file in the repository.
Add content for each of the sections mentioned above.
Ensure the content is formatted properly using MDX.

🎃 Hacktoberfest Participation
✔ This issue is tagged for Hacktoberfest.
✔ PR should reference this issue and adhere to contribution guidelines.
👥 Contributors
If you are working on this issue, please comment below to let us know. Feel free to ask any questions!
Don't forget to go through the CODE OF CONDUCT and follow the CONTRIBUTING guidelines.

Thank you for contributing to Hacktoberfest and helping improve this project!

@0xSaurabhx Hi, can you assign this to me

Hey @coder-pink ,
We've assigned another issue to you once you contribute to that issue actively and get PR merged as soon as possible we will assign this issue to you.

Hey @coder-pink ,
I have assigned this issue to you let me know if your still interested in contributing. Thank you!

Yes, @rakshixh  I am free tomorrow. I'll do it.

@coder-pink Hey, any update?


Service Bus: Bulk publish does not apply metadata properties to events

Expected Behavior
When publishing events to Azure Service Bus Topic via the Dapr BulkPublishEventAsync method, the metadata properties and values should be applied to all events in the batch of events.
Actual Behavior
None of the metadata properties and values are applied to the events in the call to the BulkPublishEventAsync method.
Steps to Reproduce the Problem
using System;
using System.Collections.Generic;
using Dapr.Client;

const string PubsubName = "my-pubsub-name";
const string TopicName = "topic-a";
IReadOnlyList<object> BulkPublishData = new List<object>() {
    new { Id = "17", Amount = 10m },
    new { Id = "18", Amount = 20m },
    new { Id = "19", Amount = 30m }
};

using var client = new DaprClientBuilder().Build();

var metadata = new Dictionary<string, string>() { { "PartitionId", "RandomIDValue" } };
var res = await client.BulkPublishEventAsync(PubsubName, TopicName, BulkPublishData, metadata);

Reading events back via Dapr or viewing them in the Service Bus topic/Subscription in the Azure Portal, the events will not contain the expected metadata properties.
The issue is related to a mis-match between the way the Dapr .Net SDK handles the metadata versus how the Dapr runtime processes the passed in metadata.
The Dapr .Net SDK only packages up a single metadata map in the BulkPublishRequest object, so expects the Dapr runtime will apply the metadata to each event before writing to the Azure Service Bus Topic. See DaprClientGrpc.MakeBulkPublishRequest(....)
The logic on the runtime side, implemented in the 'components-contrib' repo ignores the metadata in the bulkPublishRequest object. Instead the logic walks through each event and processes any metadata object associated with the individual event. Refer to the 'PublishPubSubBulk' method in 'components-contrib/common/component/azure/servicebus/publisher.go'.
Release Note

RELEASE NOTE:

I'll see if I can't squeeze this into the 1.15 release. Thanks for spotting this @bely300 !


Binding  in Oni has various repercussions

Oni Version: 0.3.6
Neovim Version (Linux only):
Operating System: MacOS 10.13.5
Issue:
Pressing Enter will work when in normal mode however when you try to do anything else while in normal mode, aka Cmd + P to find a file, pressing enter to select the file will trigger the binding and thus no longer select the file.
Expected behavior:
The binding to work in relation to Vims and not while inside Oni's menus like Command Palette
Actual behavior:
The Enter binding will trigger even inside Oni's menus. I need some way of excluding Oni's menus
Steps to reproduce:
  const isNormalMode = () => oni.editors.activeEditor.mode === "normal"

  oni.input.unbind("<enter>") // Not unbinding <enter> first will undo your last change every time you press it for some reason
  oni.input.bind("<enter>", "buffer.toggle", isNormalMode)

Press C-P to being up the Command Palette
Type a name to find a file
Press Enter

I think this could be a more broad issue of how Oni deals with filters for bindings in a more user friendly way. (ie stuff like https://github.com/onivim/oni/issues/2194)
That is, its a bit confusing binding stuff and knowing what it will and won't affect. What it sounds like is that you want a "enter when in normal mode, but not when a menu is open". Which is totally possible, if you add a new filter like:
    const isMenuOpen = () => oni.menu.isMenuOpen()
    const isNormalMode = () => oni.editors.activeEditor.mode === "normal"

    oni.input.unbind("<enter>") // Not unbinding <enter> first will undo your last change every time you press it for some reason
    oni.input.bind("<enter>", "buffer.toggle", () => isNormalMode && !isMenuOpen)

...which is fine, but then enter doesn't work in the command line so you can't save that changed config. So you need to add an isCommandLine option too, and then at the end of all of it, you still don't really get anywhere since the initial unbind removed all the actions in menus and such. It gets very messy very quick since I was fixing one things and the next would break (QuickOpen, cmd mode, explorer, VCS bar etc)
I'm not sure if this is something you've thought about @bryphe but have you any ideas on how we can help this sort of issue? Its essentially a "I want to bind this here, but I don't want to change anything anywhere else mode". Or am I missing some option that would allow that to be easily achieved?

I think you nailed it right on the head @CrossR
At least in Vim, you have the noremap option which helps with mapping conflicts.
I feel like Oni should have it's own "mode" which is flagged whenever we're interacting with an Oni element.

hmmm... this is a pretty interesting case.
It could be solved by making a distinction if you are binding when focused on the editor pane or the general Oni layout, currently this is the cause for the issue. It seems that most keybindings should not have any effect when in temporary modals (e.g. Command Palette).
Other possibility, much more flexible but also more complex is to expose a command (e.g. oomap) that stores keybindings and strings (e.g. oomap <enter>, 'buffer.toggle'). This is very ad hoc though.
Just for the sake of curiosity, how do you insert line breaks and what's your use case?

I received an email about someone elses comment but I don't see it here for some reason.

hmmm... this is a pretty interesting case.
It could be solved by making a distinction if you are binding when focused on the editor pane or the general Oni layout, currently this is the cause for the issue. It seems that most keybindings should not have any effect when in temporary modals (e.g. Command Palette).
Other possibility, much more flexible but also more complex is to expose a command (e.g. oomap) that stores keybindings and strings (e.g. oomap , 'buffer.toggle'). This is very ad hoc though.
Just for the sake of curiosity, how do you insert line breaks and what's your use case?

To answer the last part, I insert line breaks while in insert mode using <CR> as per the default. I only have <CR> mapped for normal mode. If I want to insert line breaks without leaving normal mode, I use my Shift+k mapping like so:
    " Change the Shift+k function to something more useful: The opposite of doing Shift+j
    nnoremap K i<CR><Esc>^

the reason why I want to map enter is because simply faster to find buffers. I can do <CR>2<CR> in milliseconds, or <CR>mybuffername<CR>
It's quite a nice way to find buffers. I do this in regular Vim albeit less fancy with this mapping:
  " Quick Find a Buffer
  nnoremap <CR> :ls<CR>:b<Space>

But the Oni vim buffer finder is much slicker and pleasant so I wanted to replace my current method with that.

I removed because it was a not well thought comment aftet re-reading the
conversation again.
Em Qua, 15 de ago de 2018 13:30, James W Mann<EMAIL_ADDRESS>escreveu:

I received an email about someone elses comment but I don't see it here
for some reason.
hmmm... this is a pretty interesting case.
It could be solved by making a distinction if you are binding when focused
on the editor pane or the general Oni layout, currently this is the cause
for the issue. It seems that most keybindings should not have any effect
when in temporary modals (e.g. Command Palette).
Other possibility, much more flexible but also more complex is to expose a
command (e.g. oomap) that stores keybindings and strings (e.g. oomap ,
'buffer.toggle'). This is very ad hoc though.
Just for the sake of curiosity, how do you insert line breaks and what's
your use case?
To answer the last part, I insert line breaks while in insert mode using
 as per the default. I only have  mapped for normal mode. If I
want to insert line breaks without leaving normal mode, I use my Shift+k
mapping like so:
" Change the Shift+k function to something more useful: The opposite of doing Shift+j
nnoremap K i<CR><Esc>^

the reason why I want to map enter is because simply faster to find
buffers. I can do 2 in milliseconds, or mybuffername
It's quite a nice way to find buffers. I do this in regular Vim albeit
less fancy with this mapping:
" Quick Find a Buffer
nnoremap  :ls:b
But the Oni vim buffer finder is much slicker and pleasant so I wanted to
replace my current method with that.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/onivim/oni/issues/2490#issuecomment-413253769, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVNoGDIwgS9eOKycLOjdRF3go0KsqyDks5uREyngaJpZM4Vufrh
.

Oh okay, my apologies, I still thought it was worth sharing since it sort've added to the conversation and also allowed me to explain the use case behind wanting to bind <enter>


Missing optimization information on methods OnEntry and OnExit

Hey Phil,
Just installed Postsharp 2.1 from the nuget package and then installed your NullGuard package.
As I add the [EnsureNonNullAspect] aspect at either the class or method level I immediately get the following compiler warnings:
Warning 1   Missing optimization information on method 'NullGuard.PostSharp.EnsureNonNullAspect.OnEntry(PostSharp.Aspects.MethodExecutionArgs)'.
            This information is computed automatically by PostSharp.
            Make sure that assembly NullGuard.PostSharp is processed by PostSharp.
Warning 2   Missing optimization information on method 'NullGuard.PostSharp.EnsureNonNullAspect.OnExit(PostSharp.Aspects.MethodExecutionArgs)'.
            This information is computed automatically by PostSharp.
            Make sure that assembly NullGuard.PostSharp is processed by PostSharp.

It could be that this is nothing to worry about, but a) I don't like compiler warnings that I can't find the answer to anywhere on Google b) it could be something to worry about.
Any help would be most appreciated.
Cheers!
Tod.

Closing (this is ancient). You can reopen if you ever care to.


hotspot, coldspot, and anomaly analysis

Hotspots -- areas with consistently high values
Use CDB_GetSpatialHotspot() function
Description: Find clusters with consistently high values. These are areas that are spatially correlated with the places around it. The smaller the significance value, the more robust the correlation.
Anomalies -- places with values that stand out from those around them
Use CDB_GetSpatialOutliers() function
Description: Find areas which stand out compared to their neighbors. These are places that are spatially anti-correlated with the places around it. Anomalies are hotspots situated next to cold spots, or vice versa.
Coldspots -- areas with consistently low values
Use CDB_GetSpatialColdspots() function
Description: Find clusters with consistently low values. These are areas that are spatially correlated with the places around it. The smaller the significance value, the more robust the correlation.
cc @andrewxhill

Very interesting one for making morans more accesible. cc/ @rochoa @javisantana

Looking good. In the Builder Interface, I would suggest we add the verbal
nouns,
Hotspot Detection
Coldspot Detection
Anomaly Detection
On Tue, Jun 21, 2016 at 10:37 AM Sergio Álvarez Leiva <
<EMAIL_ADDRESS>wrote:

Very interesting one for making morans more accesible. cc/ @rochoa
https://github.com/rochoa @javisantana https://github.com/javisantana
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/8016#issuecomment-227460055,
or mute the thread
https://github.com/notifications/unsubscribe/AAWmU2xjlx90aOG5Nlq7TrWqAH_MyuAtks5qN_cjgaJpZM4I6zKf
.

Btw, each of the functions above has a ...Local() version (e.g., this one) that accepts a denominator as well as a numerator.

Duplicated! Already being implemented!


fix(collapse):Fix child positions on group expand

What
Closes #145
Description
Fix positioning of child nodes when a collapsed group is expanded.
Type of change

[x] Bugfix

Surge
https://uncollapse-fix.surge.sh

There seems to be a small bug with the group anchor point when an edge exists:

Thanks @jenny-s51. Fixed now.


Fix express merge params behavior

Merge automatically express params when using Platform Express and Express.Router.
Express.js:

Preserve the req.params values from the parent router. If the parent and the child have conflicting param names, the child’s value take precedence.

:tada: This PR is included in version 6.0.0-beta.7 :tada:
The release is available on:

v6.0.0-beta.7
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0-rc.1 :tada:
The release is available on:

v6.0.0-rc.1
GitHub release

Your semantic-release bot :package::rocket:


fix: handle parsing & primary error properly

If we respond with a empty message with Content-Type: 'text/html', the browser will throw error stating as This page isn’t working losing the original error page.
Now we respond with 500 status code and Internal Server Error as the response when there is a parse error or when there is no fallback provided for primary fragment.

This is a very old bug and it was introduced when we started supporting fallbacks and I noticed after we started the Opentracing instrumentation, so Thanks to @lmineiro  😄

👍

:+1:


[wip] Add sql calls for bookkeeper

Hey @ShahanaFarooqui this is just a draft pr.  The balance sheet graph is not styled at all and there is more work to do there.
I am particularly interested to see what you think of the way I make the sql calls, parse them, and store the sql statements.
I added balanceSheet to AppContext with sendRequestToSetStore(appCtx.setBalanceSheet, 'post', '/cln/call', { 'method': 'sql', 'params': [BalanceSheetSQL] });
and would add appCtx.setSatsFlow for the satsFlow chart.
AppContext.setBalanceSheetHandlerI() transforms this response payload:/
^*** Actually i need to do this outside the context since i want to pass conditions to the sql such as timestamp filters.  I may do something similar to how the withdraw call is made in use-http.ts
{"rows":[
  ["1671x1x0","IRATEBOUNCE-.1-1-gb0b5904-modded",1000000000,"44a2c35d3850764fd7a1be2c416571bb5ae68d6856c567edd0a2ad5847be602f"],
  ["1786x1x0","IRATEBOUNCE-.1-1-gb0b5904-modded",1000000000,"b892ea8a75388a254090a2f8426c9ba1d62e1b8f86700cc68a6f67101c98b827"],
  ["1779x1x0","IRATEBOUNCE-.1-1-gb0b5904-modded",1000000000,"f4dfa00f30e5ac51a80f6929ad7b77720f71bdb579387649a387c61203c3f31a"],
  [null,null,296999502000,"wallet"]
],"isLoading":false,"error":null}

This payload is a little weird in that rows is a multidimensional array [][].  I have to parse out the inner array to get the actual Account object.  I do this in bookkeeper-transform.ts/transformToBalanceSheet().  I take the response DTO and turn it into the Account domain model.  I append a percentage field in this process.
/**
 * Onchain wallet or Channel
 */
export type Account = {
  short_channel_id: string,
  remote_alias: string
  balance: number,
  percentage: string,
  account: string,
};

I am storing bookkeeper sql commands in bookkeeper-sql.ts.
BalanceSheetRoot.tsx reads appCtx.balanceSheet and passes to the graph and table.
See above strikethrough
What do you think?

I need to change my approach, i cant do everything i wanted in sql due to the limited  functions available from the cln sql rpc.  Will have to process the rows in code

So closing this for now


Adding a "refresh timer" to the scope

Adding a method to restart the timeout timer to keep a toast visible longer.

A toast is an alert, to say something, for me, it doesn't make sense to restart the timer.
If an user needs to read it, they can hover it so it doesn't go away.

My use case is uploading multiple files. Instead of opening a screen full of toasts to announce that each uploaded successfully, I'm showing one toast and if it's still visible when the next file finishes, I'm updating the message and resetting the timer.

I get you. I will think about that.

Do you know of any other way to accomplish what I'm trying? Currently, the toast continues to update until it times out and then another one immediately pops up with a new timer. It works okay, but the flicker when it has to pop a new toast is just a bit ugly.

I would make a permanent toast for the time being and after all upload finishes, kill the toast.

Yes that would sort of work. Except then if there were only a few small files, the toast would disappear too quickly.

I want this option, but having a method in the current scope is just one step, To access it you need to myToast.scope.refreshTimer() and I don't really like that API.
Also, I need tests.

I agree about having to go through the scope property to refresh the timer.
To be consistent with the rest of the API, it should probably go through the service like toastr.refreshTimer(toast) unless you want a shorter method name. Maybe toastr.extend(toast)? Or toastr.prolong(toast)?

Perhaps just "restart"?

Could that give the impression it affects more than just the timer?

You are right. Then refreshTimeout or simply refresh ?

I'll just keep refreshTimeout for maximum clarity.
Another topic: Tests are in toastr_spec.js but I haven't figured out how to run them locally.

For the tests, you need to run testem. I need to swap that for karma.
So for today:
$ npm install -g testem
$ testem -f config/testem.json

The tests will watch any change that comes from $ gulp.

Nice work on that, but we would need a few more tests cases where the toast is not there (long gone) and one where the toast was just gone one millisecond ago.

Will do.

Are the tests sufficient? Are there any other test cases needed?

Probably yes. Will double check tomorrow and release this weekend :)

Thanks, I merged this. I will make a release.


Specify to use 2.x branch for Carthage users

With master starting to work towards 3.x it's better for external users to use 2.x until we have a better idea for what the 3.x API will look like.
@spotify/objc-dev @cerihughes

Codecov Report

Merging #304 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #304      +/-   ##
==========================================
+ Coverage   93.56%   93.58%   +0.01%
==========================================
  Files          74       74
  Lines        5096     5096
==========================================
+ Hits         4768     4769       +1
+ Misses        328      327       -1

Impacted Files
Coverage Δ

sources/HUBUtilities.h
72.91% <0%> (+1.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Default number of workers: Look at the affinity mask instead of the number of CPUs?

Hi,
I was looking for a thread pool, and found this repo. Thanks for working on this.
I was browsing the dependencies and saw that you use num_cpus to decide how many worker threads to use by default:
let num_threads = self.num_threads.unwrap_or_else(num_cpus::get);

Would it not be better to look into the affinity mask to get this default? The system may have 64 cores, but have the process pinned to, e.g. 4 cores. This would cause contention.
I found this crate, which might help (disclaimer, I've not used it and I'm not sure how portable it is):
https://crates.io/crates/core_affinity
Thanks

from what i understand, num_cpus::get uses the affinity mask whereas num_cpus::get_physical returns the unpinned physical number of cores. i might be wrong though....

Good idea.
If you are using a SGE managed cluster you can use my latest crate son of grid engine.
You can use get_pinned_threadpool() for a correctly pinned pool there.
I think the pinning should not be the default, but an option with the builder.


Update zio-sbt-website to 0.0.0+83-40726325-SNAPSHOT

Updates dev.zio:zio-sbt-website from 0.0.0+80-e5b408eb-SNAPSHOT to 0.0.0+83-40726325-SNAPSHOT.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-sbt-website" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "dev.zio", artifactId = "zio-sbt-website" }
}]

labels: sbt-plugin-update, early-semver-build-metadata, semver-spec-build-metadata, commit-count:1

Superseded by #314.


Removes SnapKit from EmptyDataSet

I found a TODO in EmptyDataSetView regarding NSLayoutConstraint not working as SnapKit. Turns out you'd to do two things:

Set translatesAutoresizingMaskIntoConstraints to false to let UIKit know don't use auto resizing masks.
Set constraints on stackView instead of contentView.

I also removed SnapKit from PodFile for EmptyDataSetView target.

I think we can also remove SnapKit from Bento target but didn't remove it in this PR to keep this PR specific.


Branch 2

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: decadehew sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


bin/brew: allow GITHUB_ACTIONS_HOMEBREW_SELF_HOSTED

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

We're migrating to this.

Review period skipped due to critical label.

@Bo98 can we remove the one we migrate away from? May warrant adding a TODO here?

Yes


Migrating to Typescript

See also https://github.com/treasure-data/digdag/pull/1641#issuecomment-932850649 for details.

Can I work on it?

Sure, no problem at all. I appreciate your help as usual 👍

@szyn
Which plan is better do you think?

Gradually migrate

steps

Make all the codes valid typescript syntax without resolving type errors and lint errors
Gradually collect type errors and lint errors by many small PRs.
When all the type errors and lint errors are resolved, add type check step and lint step into CI.

pros

can avoid conflicts
each PRs will be small and easier to review
other contributors can help migration
some progress will be commited even if I stop commit for some reason

Migrate in single PR

steps

Make syntax, type, format and coding style valid at one PR and check them on CI

pros

can avoid committing half done codes
you will review PR only 1 time
can avoid half done migration even if I stop migration for some reason

Thank you, I feel that 2 is simple and better for me. What do you think?

I think each of them is good.
I'll try latter one.

@szyn
I found that fixing all the typing error in reliable way is extremely hard.
()

So I will add some any, that is unclear type and some ts-ignore, that make type checker skip codes.
Do you agree it?

Yes, I agree with it. And also it looks good to me for the approach you suggested. Thank you for letting me know 👍


What is the deadline of this homework?

@Mosaddeq107 I believe that it's on next week's Monday. @laserlab Am I correct?

Yes, that is correct

Thank you for clarifying Prof. @laserlab


doc updates; enforced stricter guidelines on API flow

wrote docs; only need to add internal hyperlinks now
following a stricter guideline on what defines a "valid" maestro instance:

initialized instance: all fields are Some(_)
uninitialized instance: all fields are None
invalid instance: instances that don't fit above 2 definitions

Added more code on provably preventing maestro instances from turning bad.

Since no major code has been edited, this has not been rigorously hardware tested yet.
Planning on performing hardware tests this coming week.


URL shortening service doesn't redirect immediately.

The short URL's generated by the program (using hec.su) will not redirect to the target URL directly. Instead, it has a 10s countdown before redirecting. FBI does not work with this, which makes the program rather useless.
Screenshot of the page

Was fixed in #22. Mind pushing a new release so people don't have to compile for themselves?


Programmatically load next/previous video in a playlist

Feature Request
Describe your idea
Thanks for the addition of new features that using playlist.

Load next/previous vedio when use playlist

I can't found next or prev button when using playlist ( This feature is already provided by YouTube API V3. ). or get current video number, and the total number of videos to changing vedio.

Sign with google to use YouTube Premium (remove ads, play private viedos)  I found solution !!!!!!! here

I don't know it's possible. for using YouTube Premium sign in Google and choose account before playing video to playing private viedos (or playlists) and remove ads. I tried get an access token using OAuth2.0 to use the permission. However, it is not compatible with the 'YouTubePlayerView' library provided by youtube.

Get total time of current viedo.

Expected behavior and realization

private lateinit var player: YouTubePlayer
                     :
youTubePlayerView.initialize(API_KEY, this@MainActivity)

playbtn.setOnClickListener {
            player.play()
        }
pausebtn.setOnClickListener {
            player.pause()
        }

prevbtn.setOnClickListener {
           if(player.hasPrevious){
                    player.previous()
            }
        }
nextbtn.setOnClickListener {
           if(player.hasNext){
                    player.next()
            }
        }
                :

override fun onInitializationSuccess(
        p0: YouTubePlayer.Provider?,
        p1: YouTubePlayer?,
        p2: Boolean
    ) {
        /** add listeners to YouTubePlayer instance **/
        p1?.setPlayerStateChangeListener(playerStateChangeListener);
        p1?.setPlaybackEventListener(playbackEventListener);

        if (!p2) {
            p1?.cuePlaylist(PlayList_ID);
        }
        player = p1!!
    }

This will be available in version 12.1.0 which releases sometimes this week.

i want after end of video next video will play automatic


Documentation question: Lighthouses

Some questions on lighthouses.

What role does the Lighthouse perform in the network? Is it purely for discovery?
Does it "only" know about the hosts that have spoken to it?
Do the Lighthouses talk to each other to share the rest of the nodes in the network?
If you have two lighthouses (A and B), with nodes (1,2,3) talking to lighthouse A, and nodes (4,5,6) talking to lighthouse B. Can node 1 talk to node 4? Does node 1 need to know about both lighthouse A and B? Does node 4 as well?

Discovery (private and routable ips for other clients) and to facilitate NAT hole punching (signaling, port learning)
Yes
No, this is by design. Want to avoid cross contamination in the event of a single compromised lighthouse.
All client nodes must share at least 1 common lighthouse to be able to learn about each other and communicate.

The role of the lighthouse currently is to facilitate discovery among client nodes. It may expand in the future (as a traffic reflector) but we don't have any firm plans at the moment.

what happened if all client share more than 1 common lighthouse, how 2 nebula client nodes decide the traffic/routing stuff?


vm with 2 interface ip address in same subnet

This is OS system stack issue, if want to configure the same subnet ip in two different interfaces, need to configure one interface policy route and iptables rules
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.interface.arp_announce = 2
net.ipv4.conf.interface.arp_filter = 1


Animations

Update the readme file

hi @christianbiring1   can you be more specific about whats wrong with my deployement ? as you can see from this link the deployement seems to be succesfull https://yayoamigo.github.io/mobile-template/

hi @christianbiring1 can you be more specific about whats wrong with my deployement ? as you can see from this link the deployement seems to be succesfull https://yayoamigo.github.io/mobile-template/

if you can check very well your commit history and the time. I think you would agree with me that you deployed the page after I have reviewed your PR, right?

@christianbiring1 actually no, I just added the link to the README file, the page was already deployed before your review. So please be thorough :)


New function: capturePage

To capture the whole page with rendered height, width defined by viewport. Also some small formatting cleanup.

Hi thank you for this contribution


How to use this library with the React

Describe the bug
I'd like to use this library with the React library in the electron js. I've setup the electron js with the React and I've installed this library in my project. I've tried with few approaches to load custom electron title bar in the app but it doesn't show the custom title bar when electron js app starts. Here's my attempt to load custom title bar:
CustomTitlebar.js
import React, { useEffect } from 'react';
import { Titlebar, Color } from 'custom-electron-titlebar';

/**
 *
 * @returns customized window title bar
 */
const CustomTitlebar = ({children}) => {
  const loadCustomTitlebar = async () => {
    const customTitlebar = new Titlebar();
    customTitlebar.updateBackground(Color.fromHex('#d8d8d8'));
    customTitlebar.setHorizontalAlignment = 'center';
    customTitlebar.updateTitle = 'Home - Hisab';
    return customTitlebar;
  };

  useEffect(() => {
    window.addEventListener('DOMContentLoaded', loadCustomTitlebar);
    // Clean up above functions on unmount
    return () =>  {
      window.removeEventListener('DOMContentLoaded', loadCustomTitlebar);
    }
  }, []);
  return (

{children}

  );
};
export { CustomTitlebar };

App.js
import React from 'react';
import { CustomTitlebar } from './components';

const App = () => {
  return (
    <CustomTitlebar>

Welcome to the Hisab!

    </CustomTitlebar>
  )
}

export default App;

I've also make frame: false and titleBarStyle: 'hidden' in my main process. But still the custom title bar doesn't show up when the app loads up.
Expected behavior
Must show customized title bar when the app loads up.
Screenshots

Desktop (please complete the following information):

OS: mac/windows
Electron version 12.0.0
Node Version 14.15.4

Same issue here, but I think this is related to electron itself

I haven't tried to do anything with this in React, but my gut feel is that you're going to need useLayoutEffect() at the very least.  maybe that'll get it going?

Pretty sure it doesn't have to do with any hooks, since react app injects itself into a div in the template that has the id "root", before and after that it doesn't change anything of the index.html template, and I've tried adding it inside of the head tag and in the body but nothing happens.

@ericblade I had tried with that as well (using useLayoutEffect) but it didn't work. However, if I try using as a normal function then it loads the custom title bar. Like this:
customTitlebar.js
import React from 'react';
import { Titlebar, Color } from 'custom-electron-titlebar';

const customTitlebar = () => {
  const customTitlebar = new Titlebar();
  customTitlebar.updateBackground(Color.fromHex('#d8d8d8'));
  customTitlebar.setHorizontalAlignment = 'center';
  customTitlebar.updateTitle = 'Home - Hisab';
  return customTitlebar;
};
export { customTitlebar };

App.js
import React from 'react';
import { customTitlebar } from './components';

const App = () => {
  customTitlebar();
  return (

Welcome!

  )
}

export default App;

@raviSussol does it work as intended? Or is something not working?

@system32uwu No it works fine (without any issue) but I don't think this is the correct way using in React app. To be honest, I was wondering that I would use in the context so that I can share the custom title bar in every new child windows when they get opened.

Ok, so, i'm thinking about it a little bit right now.. and.. I think that you're actually closer to correct than you think.  Somewhere in your React app, probably in your index.js (or .jsx or .ts or .tsx or whatever) you're going to have a call to ReactDOM.render(, document.getElementById('root')) or something very similar to that.
As custom-electron-titlebar lives outside the part of the DOM that React is going to be monitoring, you should probably load it right about at that same spot.

@ericblade I had tried with that as well (using useLayoutEffect) but it didn't work. However, if I try using as a normal function then it loads the custom title bar. Like this:
customTitlebar.js
import React from 'react';
import { Titlebar, Color } from 'custom-electron-titlebar';

const customTitlebar = () => {
  const customTitlebar = new Titlebar();
  customTitlebar.updateBackground(Color.fromHex('#d8d8d8'));
  customTitlebar.setHorizontalAlignment = 'center';
  customTitlebar.updateTitle = 'Home - Hisab';
  return customTitlebar;
};
export { customTitlebar };

App.js
import React from 'react';
import { customTitlebar } from './components';

const App = () => {
  customTitlebar();
  return (

Welcome!

  )
}

export default App;

If I do that I get the following error:
Uncaught ReferenceError: require is not defined
    at Object.electron (index.js:60900)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/menubar.js (index.js:18452)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/titlebar.js (index.js:19654)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/index.js (index.js:17562)

Which makes sense, since this should be used only in the main process, aren't you using webpack btw?

@raviSussol
If I do that I get the following error:
Uncaught ReferenceError: require is not defined
    at Object.electron (index.js:60900)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/menubar.js (index.js:18452)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/titlebar.js (index.js:19654)
    at __webpack_require__ (index.js:790)
    at fn (index.js:101)
    at Object../node_modules/custom-electron-titlebar/lib/index.js (index.js:17562)

Which makes sense, since this should be used only in the main process, aren't you using webpack?

Nevermind, I got it working with this options when creating the main window, in webPreferences:
webPreferences: {
      nodeIntegration: true,
      nodeIntegrationInSubFrames:true,
      nodeIntegrationInWorker:true,
      enableRemoteModule: true,
      contextIsolation:false
    }

@system32uwu Glad that you resolve it 👍 The error you'd noticed at first for me was to set following contrainsts in the webPreferences:
- nodeIntegration: true
- contextIsolation: false
- enableRemoteModule: true

They are enough to resolve your issue. But according to the latest electron js pattern or in the latest electron version those settings are anti-pattern. Making node integration to true leads you to the security vulnerabilities as all node APIs become accessible from the renderer process which you might want to restrict/control based on your requirement only. In the latest version of the electron js contextIsolation comes with false by default to improve other security risks more details in here. So these things you may want to consider before setting above preferences for custom title bar in your app. I think this custom titlebar library may need to update along with the latest version of the electron to cope with these new changes. So I'm also not thinking to use it in my project for now (unless someone would update this library or make the React friendly - which would be awesome).

Agree, I tried making my own title bar but there's no way to make it work without enabling nodeIntegration and disabling contextIsolation, I followed this.

So I'm also not thinking to use it in my project for now (unless someone would update this library or make the React friendly

I've proposed some ideas for updating to the newer architecture patterns, but I really don't have time to rebuild an entire library :) maybe if i hit the ballmer curve one day though lol
as for making it "React friendly" i think that's not really something you can do -- the entire point of it is to be outside of the React shadow DOM.  You don't want it being inside React.

So I'm also not thinking to use it in my project for now (unless someone would update this library or make the React friendly

I've proposed some ideas for updating to the newer architecture patterns, but I really don't have time to rebuild an entire library :) maybe if i hit the ballmer curve one day though lol
as for making it "React friendly" i think that's not really something you can do -- the entire point of it is to be outside of the React shadow DOM. You don't want it being inside React. I think having it inside the shadow dom would be kind of pointless. (you may convince me otherwise, though :))

He talked about using the state to change the title of the window and other props, so I guess that's a good point, but maybe that can be solved using a simple

The simplest, but possibly somewhat questionable way to sync document title to the CET title, would be to setInterval(() => titleBar.updateTitle(), 1000) or something.
The probably best way to do it, that I can think of, though, would be to use a MutationObserver, as (at least in Chrome) the title element changes whenever you set the document.title via code, and document.title changes if you change the title element.
const observer = new MutationObserver((rec) => titleBar.updateTitle());
observer.observe(document.querySelector('title'));

Assuming that works cross browser, that's probably the best way to do that.. in fact, now that i've written it, i'm going to go put it into my app :-)  Might be nice to add an option to CET to do that automatically.


[1.3.6-prepare][Feature-5062][*] Create/Edit/Delete Worker Group in Web UI #5113

pr: #5113
issue: #5062

i think we have some differences of opinion on this feature
so we can put this feature on the next version.

After testing, this pr will not cause any performance problems, so I decide to reopen this pr. Because submitting this pr is not an easy task, I don’t plan to submit it again later. So I can have more time to solve many problems of DolphinScheduler.

@dailidong @lenboo @gaojun2048 @CalvinKirs
I made optimization to reduce the database and zookeeper queries by ServerNodeManager, which is evolved from ZooKeeperNodeManager. Please review, thanks a lot.
ServerNodeManager:

WorkerNodeInfoAndGroupDbSyncTask: Schedule worker node info (heartbeat info) and worker group db sync task every 10s
WorkerGroupNodeListener & MasterNodeListener: Listen worker group node and master node and sync nodes

+1

+1
Why test coverage in SonarCloud Code Analysis is 0%?

The unit test is disabled.

+1
Why test coverage in SonarCloud Code Analysis is 0%?

The unit test is skipped.

ok

I add a new commit to replace worker address input with multiple-select as follow:

I add a new commit to replace worker address input with multiple-select as follow:

good job !


Implement get_network_instances

Ref: https://github.com/napalm-automation/napalm-base/pull/136

Coverage decreased (-0.03%) to 86.332% when pulling f5430ce8dbe6f95261e17f238b53a0346b5e40c2 on mirceaulinic:IMPL-NW-INST into 2fcee2831c1e03c3d7a970884ec45a7e1246e76a on napalm-automation:develop.


maybe bootstrap shouldn't overwrite db data?

Right now, data in the bootstrap will overwrite corresponding data in the database. This is really useful for development and quick iteration when we don't know what the data structure will look like, but has become a bit of an issue with the actual sites.
Since we're currently specifying ALL layout-level components in the site bootstraps (because kiln doesn't have a UI around editing layouts directly, or creating/choosing layouts for pages), any user-added stuff in the layouts (sidebar components, etc) get wiped out every time we deploy our code to the servers.
Should we change it so that the db takes precedence over the bootstrap files? Or should we make kiln UI stuff a higher priority. It's definitely weird that we have actual, production data in our bootstraps, and that seems like an unintended consequence of over-relying on them during development.

That would match our original plan around an import.js script: Don't import if the data in question already exist. So, likewise, don't bootstrap if any data already exists or similar data already exists?

Maybe. It would make development more difficult though (since you'd have to kill the db to change those values, or update them manually). As I wrote that I realized how weird it is that we have actual production data in our bootstrap, which I don't like.
On the other hand, most of us are simply using the in-memory db for local development anyways, so killing the db every time is already happening. Hmm...

Perhaps a preference in the bootstrap itself as to whether it run based on either:

Whether data already exists
The current environment
?

Dane rightly gave me the stink-eye on env-decedent behavior, so scratch that.

After much slack chit-chat, it's clear that bootstrap, since it was a temporary measure, just needs to be retired. I'll push hard for the UX path on layout data and we'll go from there.

I think that's the best way forward. The bootstrap is really nice for local development and testing with specific data, but we shouldn't be using it as a crutch for populating the database with real data.


feat: add more label format for esl-select; fix select dropdown focus

:tada: This PR is included in version 2.0.0-beta.15 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Duplicate exports

Issue: Duplicate exports when the same loader instance is invoked on > 1 jupyter cell.
version: 1.4.0
e.g.
cell 1

loader = CorpusLoader(".")
loader

cell 2

loader

Click 'Export' button -> this exports the Corpus twice.

I can replicate this in v1.4.0, but I'm not able to replicate this in 1.5.0, which was just released. Please add another issue if any similar bug occurs using 1.5


Change SortResult to be arbitrary data

SortResult is opaque data from an application perspective and should be defined as UserDefinedValue (or a new OpaqueData type that would accept anything since it's not actually user defined).
See discussion in https://github.com/elastic/elasticsearch/pull/81583
This should be a breaking change in 8.0 (the above PR targets 8.1).

This is causing issues in https://github.com/elastic/elasticsearch-java/issues/66 and will have to target 7.x as well since it's now a bugfix.


[Question] Why is this not working?

Question
When clicked on a Enchantment Table, nothing happens
Plugin Version
latest
Additional Information

@aieuo ?

Please use the contains operator as comparison string or use {block.name} variable.
I'm sorry for the late reply.

Ok thanks


Unable to run unit test in Angular 5 - ng test

While running ng test, I am getting error
"Uncaught TypeError: Zone.__load_patch is not a function".
I checked the source code in the debugger console in chrome, it is showing error ../zone.js/dist/async-test.js_global. It was worked earlier but now seems some of the dependencies got upgraded.
Dev Dependencies version:
@Angular/cli: 1.2.7,
@angular/compiler-cli:~5.2.0,
@types/jasmine:2.5.38,
@types/jasminenewd:~2.0.2,
@types/node:~6.0.60,
karma:~1.4.1,
karma-chrome-launcher:~2.1.1,
Karma-cli: ~1.0.1,
karma-jasmine: ~1.1.0,
ts-node: ^3.3.0,
talent: ~4.5.0
Dependencies:
zone. js: ^0.8.4

It seems your environment is not correct, please provide a reproduce repo.

Thank You. It worked 2 weeks back. I did not change anything in the code base. I created another sample project event that project also worked for me.  After launched chrome browser I checked the developer console I am getting error in "Uncaught TypeError: Zone.__load is not a function at zone-testing.js" and cause is from test.js. Could you please let me know any version compatibility  issue


Add ServiceCreateResponse.warnings

Add ServiceCreateResponse.warnings nullable field.

Codecov Report

Merging #799 into master will decrease coverage by 11.93%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             master     #799       +/-   ##
=============================================
- Coverage     66.01%   54.07%   -11.94%
+ Complexity      713      542      -171
=============================================
  Files           162      162
  Lines          3057     3057
  Branches        349      349
=============================================
- Hits           2018     1653      -365
- Misses          884     1261      +377
+ Partials        155      143       -12

@davidxia I fixed the indentation and squashed the commits.
All tests are failing due to some strange issue: 'The command "./.travis.sh install_docker" failed and exited with 100 during ."

Don't worry about the test failures. It's caused by https://github.com/spotify/docker-client/pulls


Linux kernels 2024-02-01

linux_6_7: 6.7.2 -> 6.7.3
linux_6_6: 6.6.14 -> 6.6.15
linux_6_1: 6.1.75 -> 6.1.76
linux-rt_5_10: 5.10.204-rt100 -> 5.10.209-rt101
linux-rt_6_1: 6.1.73-rt22 -> 6.1.75-rt23
linux_latest-libre: 19482 -> 19489

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Dupe https://github.com/NixOS/nixpkgs/pull/285502

Stupid github search, I checked before opening.


bump up version to 2.3.1

Bumping up version for backward compatible rails 5.2 fixes

@fimmtiu @daniel-almeida was a bit unsure on what semantic version to bump it to. I think it should just be a minor bump as were just fixing some 5.2 bugs and it should be backwards compatible to work with 5.1

@fimmtiu here's also green CI on 5.2 in case curious https://buildkite.com/clio/clio-app-tests-rails-next/builds/43276


Add state schema validation utilities.

This PR proposes two utilities to let applications "self-validate" their expected state schema upon creation.

Interesting, on create why wouldnt it be what the app has defined?

Suppose the App creation is delegated to a client (trusted or not). Given a known TEAL source code this check will prevent clients to instantiate (mistakenly or intentionally) an App with a wrong state schema, different from the expected, and than discovering it later (e.g. on first assignment of a variable that exceeds the state preallocation).

Closing for now, im not sure it'll be used enough to warrant adding it to the public api


support GHC 8.2

This compiles successfully with the hackage versions of distributed-process albeit with some warnings regarding deprecated finally and catch due to a deprecated module.

There are now three different pull requests effectively requesting GHC 8.2 support. The oldest is from September.
This minor update would allow our distributed-process project to support GHC 8.2.

Merged. Sorry, support is very limited at the moment, but I'm trying to get back to it as best I can.


Add support for count statistics listing DNS records or zones

Adding support for count statistics over httpRequestsAdaptiveGroups while listing zones or DNS records
Description
This change allows to quickly verify usage of zones or DNS records from flarectl.  Behind the scenes, it calls GraphQL API for counting httpRequestsAdaptiveGroups and adds an extra column if --with-days-stats nbDays argument is specified
Has your change been tested?
Change has been tested with token privileged for multi-account and multi-zone setup mixing various Cloudflare plans.
Types of changes
What sort of change does your code introduce/modify?

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

flarectl: adding support for showing access statistics

thank you for the time you've taken to submit this PR. unfortunately, we're not extending flarectl at the moment. we will be evaluating options for a CLI tool in the future and i'll be sure to add this to the list of requests.
thanks again!


Spring cloud security 1.1.x - Resource Server Token relay

Spring Boot 1.3.2.Release / Spring Cloud Security 1.1.0.M4
My problem is similar to the one explained in #85 . I have a resource server that is supposed to call other micro services by relaying the same JWT token.
I tried Dave's suggestions as below,
String token = ((OAuth2AuthenticationDetails)SecurityContextHolder.getContext().getAuthentication().getDetails()).getTokenValue()
restTemplate.getOAuth2ClientContext().setAccessToken(new DefaultOAuth2AccessToken(token))
This works fine. At the same time, the older EnableOAuth2Resource annotation under Spring Cloud Security 1.0.x also works well with the JWT token relay.
Is there a specific reason this token relay feature was not carried over with Spring Cloud Security 1.1.x version and EnableResourceServer annotation?
Is there a better way to relay the JWT token for all outgoing calls using RestTemplate like adding a filter instead of adding the couple of lines before every call using RestTemplate?

I think maybe it was just lost in the move. The code that sets up the relay for OAuth2RestTemplates is this:
		@Bean
		@Scope(value = "request", proxyMode = ScopedProxyMode.INTERFACES)
		public OAuth2ClientContext oauth2ClientContext() {
			DefaultOAuth2ClientContext context = new DefaultOAuth2ClientContext(
					accessTokenRequest);
			Authentication principal = SecurityContextHolder.getContext()
					.getAuthentication();
			if (principal instanceof OAuth2Authentication) {
				OAuth2Authentication authentication = (OAuth2Authentication) principal;
				Object details = authentication.getDetails();
				if (details instanceof OAuth2AuthenticationDetails) {
					OAuth2AuthenticationDetails oauthsDetails = (OAuth2AuthenticationDetails) details;
					String token = oauthsDetails.getTokenValue();
					context.setAccessToken(new DefaultOAuth2AccessToken(token));
				}
			}
			return context;
		}

You could try that in your own app and verify that it works as you needed.

It's also possible we decided to duck the issue of what do do about refresh tokens. You can see that expired access tokens will not work with the code above.

Actually, I was confused (as usual). That code is not for a resource server (obviously). The resource server might actually work out of the box if you used a UserInfoTokenServices (see discussion here and in the linked stack overflow question: https://github.com/spring-cloud/spring-cloud-security/issues/85).
I think we need a clean sweep here anyway, and at least some clear documentation on what works and what doesn't and why.

hi.
i think i have pretty much the same problem, but i am not using jwt.
i try to get a token relay ready from Service A -> B, where i have multiple problems:

Getting a OAuth2RestTemplate with @LoadBalanced@Autowired Oauth2RestTemplate rt is not possible, failing with the no qualified bean... exception. Leaving that out the normal userInfoRestTemplate Bean looks to be created as it succeeds in getting the userinfo from auth server.

Creating an own RestTemplate, like:
`@SpringBootApplication
@EnableAutoConfiguration
@EnableDiscoveryClient
@EnableHystrix
@EnableResourceServer
public class MicroserviceTwoApplication {
public static void main(String[] args) {
SpringApplication.run(MicroserviceTwoApplication.class, args);
}
@LoadBalanced
@Bean
public OAuth2RestTemplate loadBalancedOauth2RestTemplate(
OAuth2ProtectedResourceDetails resource,
OAuth2ClientContext oauth2Context) {
return new OAuth2RestTemplate(resource, oauth2Context);
}

}`
works, but i need toreconfigure the user-info-uri to a Eureka Service id (here "auth-server"), but using this template in a @Component just created to execute a Method as HystrixCommand fails with:

java.lang.IllegalStateException:
No thread-bound request found: Are you referring to request attributes outside of an actual web >request, or processing a request outside of the originally receiving thread? If you are actually >operating within a web request and still receive this message, your code is probably running outside >of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or >RequestContextFilter to expose the current request.
the documentation about the exact same use case here http://cloud.spring.io/spring-cloud-security/spring-cloud-security.html is completely out of date.

do you have any hint or sample project to look at for resolving this issue?

currently it works by setting:
@HystrixCommand(fallbackMethod = "getFallBackMessage", commandProperties = {
@HystrixProperty(name = "execution.isolation.strategy", value = "SEMAPHORE") })
but as this is a not recommended configuration i'd liketo have a real solution to this problem.

That's perfectly normal for using Hystrix and Spring Security (nothing actually to do with this project at the minute). There's a strategy in Spring Cloud Netflix that you can use to carry the security context over to Hystrix: https://github.com/spring-cloud/spring-cloud-netflix/blob/master/spring-cloud-netflix-core/src/main/java/org/springframework/cloud/netflix/hystrix/security/SecurityContextConcurrencyStrategy.java.

But with camden snapshot build the documented setting this via hystrix.shareSecurityContext is not working on my side. Any further doc or tip on how to enable this strategy?

That's a spring-cloud-netflix feature. If it isn't working for you please tryt and find out why and report issues there if you find anything.


Any tips for controlling volume with Siri?

I'm not sure if my naming conventions are breaking things but I have a rough time getting Siri to do anything with the TV volume.
It's inconsistent in that "set TV volume to 10" will work once and then not work the next ten times you try it!
Sometimes 10% works other times it doesn't
Sometimes "dim" works where "set" one, so I can say "Dim volume to 10%" and it'll work - other times Homepod gets mixed up with it's own volume and no matter what you say it won't change volume.
I'd have thought whatever you named the TV + volume, would have made it clear you want to control the light slider, but then I also guess it sees it as light and not a volume slider unfortunately.
Any tips or workarounds?

Hi,
as far as i know there is no native way to set the volume of a TV in HomeKit per Siri. Apple just does not provide such functionality. Using this plugin you can enable the volume as slider, in that case as you say volume can be adjusted using a light bulb. This in theory should work, but you have to name the light bulb in a way that it is understandable for Siri. If you keep your TV name there in most cases it will be hard for Siri to understand that, so i would recommend setting the name to simply words like "Television volume".

Yeah I tried "TV volume" and "Television Volume" but none of them work consistently unfortunately. Shame...not sure why that isn't a native part of the TV feature in Homekit, especially when it knows what a TV is!

I mean when the TV is on then you will have a hard time changing the volume with Siri, if the you are using Siri in the same room. This is because the noise from the TV is of course confusing Siri. Maybe that is your issue here?

Nah, even with the Homepod right next to the TV it does an excellent job of ignoring the TV and listening to me. It's not being confused by what it hears, it just doens't understand "TV Volume" consistently for whatever reason.

On 27 May 2020, at 17:16, Marcin<EMAIL_ADDRESS>wrote:
I mean when the TV is on then you will have a hard time changing the volume with Siri, if the you are using Siri in the same room. This is because the noise from the TV is of course confusing Siri. Maybe that is your issue here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/merdok/homebridge-webos-tv/issues/246#issuecomment-634775326, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQYP2A6NHBJ7CMCXJOUV3RTU4FHANCNFSM4NMEYIEA.

I mean i cannot control the volume of my tv neither on my Echo Alexa or Siri on my iPhone when i am in the same room as the TV. This is pretty much impossible, that is why normally when you talk to Alexa for example and music is playing then Alexa first dims the music down or there is no way she cannot understand you. My guess is that the problem lies on your Homepod beieng next to your TV.

Marcin, this has NOTHING to do with it - it's irrelevant if the TV is muted or not, or if I speak to command directly into my iPhone. As i've just said the "hearing" of what i'm saying is not the issues - it's that Siri doesn't properly comprehend the device name or type for whatever reason and does different things.
For the record I contract everything in my house from HomePod with the TV on with not a single problem, that's why it has 8 microphones and beam forming.

On 27 May 2020, at 17:25, Marcin<EMAIL_ADDRESS>wrote:
I mean i cannot control the volume of my tv neither on my Echo Alexa or Siri on my iPhone when i am in the same room as the TV. This is pretty much impossible, that is why normally when you talk to Alexa for example and music is playing then Alexa first dims the music down or there is no way she cannot understand you. My guess is that the problem lies on your Homepod beieng next to your TV.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/merdok/homebridge-webos-tv/issues/246#issuecomment-634780760, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQYP6Q2W64HI7YTB7BU53RTU5I5ANCNFSM4NMEYIEA.

Anyway, it seem that the issue is not related to the plugin itself, just how HomeKit handles TVs. there is unfortunately nothing more from my side that i can do except providing the additional light bulb to control the volume...


implement draft shipit

During debugging sessions, it's sometimes useful to prod the tarballs that will be uploaded to the draft server to verify that all the information is there. We should write a feature flag like --dump to dump the build context and chart tarball out to the local filesystem.

this may actually be a nice feature called draft ship or draft shipit.

Thinking through the general use case, this does not make sense because a docker build and a helm install chart/ already will prove the same thing. I think we need to come around a solid use case like "I need to know what caused my build to fail" and write tooling around that.


MCPE world crashing MCEdit (using source version with new-features)

As reported here, user has a 143mb world file that's lagging in game (I confirmed the lag in both Android and Win10).
Upon loading in MCEdit, the console spams the following error message:
Traceback (most recent call last):
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 3865, in workOnChunk
   for _ in faceInfoCalculator:
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 3847, in calcFacesForChunkRenderer
   for _ in calc:
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 389, in calcFaces
   for _ in self.renderer.chunkCalculator.calcFacesForChunkRenderer(self):
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 858, in calcFacesForChunkRenderer
   for _ in self.calcHighDetailFaces(cr, blockRenderers):
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 1014, in calcHighDetailFaces       areaBlocks = self.getAreaBlocks(chunk, neighboringChunks)
 File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\renderer.py", line 897, in getAreaBlocks       :nb_fxd.Blocks.shape[2]]
ValueError: could not broadcast input array from shape (1,16,256) into shape (1,16,128)
for most of the chunks then eventually crashes with the following error:
mcedit.main MCEdit exited with errors.
[   ERROR][                   root.py:939]:MCEdit version Unified v<IP_ADDRESS> %s Minecraft 1.8-1.11.2 | PE 0.11
Traceback (most recent call last):
  File "mcedit.py", line 1002, in <module>
    main(sys.argv)
  File "mcedit.py", line 936, in main
    MCEdit.main()
  File "mcedit.py", line 814, in main
    rootwidget.run()
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\root.py", line 168, in run
    self.run_modal(None)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\root.py", line 233, in run_modal
    self.gl_draw_all(self, (0, 0))
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\widget.py", line 766, in gl_draw_all
    subwidget.gl_draw_all(root, suboffset)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\widget.py", line 766, in gl_draw_all
    subwidget.gl_draw_all(root, suboffset)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\widget.py", line 766, in gl_draw_all
    subwidget.gl_draw_all(root, suboffset)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\widget.py", line 766, in gl_draw_all
    subwidget.gl_draw_all(root, suboffset)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\widget.py", line 763, in gl_draw_all
    self.gl_draw_self(root, offset)
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\openglwidgets.py", line 22, in gl_draw_self
    self.gl_draw_viewport()
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\albow\openglwidgets.py", line 28, in gl_draw_viewport
    self.gl_draw()
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\viewports\camera.py", line 1891, in gl_draw
    self.render()
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\viewports\camera.py", line 1913, in render
    self.updateBlockFaceUnderCursor()
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\viewports\camera.py", line 345, in updateBlockFaceUnderCursor
    100, config.settings.viewMode.get())
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\raycaster.py", line 93, in firstBlock
    block = level.blockAt(*i[0])
  File "C:\Users\gbove\Desktop\mcedit\MCEdit-Unified\pymclevel\infiniteworld.py", line 536, in blockAt
    return ch.Blocks[xInChunk, zInChunk, y]
IndexError: index 140 is out of bounds for axis 2 with size 128
Full MCEdit log can be found here. World file could be found in the reddit link posted above, but here's a direct link for your convenience.
Admittedly, the crashing seems to be related to an issue with the world itself, but the errors generated and hard crashed seemed to warrant further investigation. I've confirmed the issue in both windows and linux running MCEdit from source using new-features.

Fixed the crash, now trying to find the cause for the repeating warning! Thanks for the submission :)

Fixed both the crash and the warnings, maps from 1.0 should work well now! Now we'll need to fix 1.1 maps :P


Eclipse RDF4j queries are not returning results for 2.3.2 version

For Eclipse RDF4j with version above 2.2 , queries are not returning any results. If there is a time delay between the executions (Debug mode execution) of RDF4j statements, then query results are returned. Otherwise No.

Hi,
Could you please provide a little more information, thanks.

E.g is it still an issue with  2.4.6 or 2.5.1 ?
Are you using an embedded NativeStore / MemStore, or a client-server setup with e.g. RDF4J server or OntoText GraphDB ?
Could you provide an example query and/or a code snippet ?

Issue exists while upgrading from 2.2 to version 2.3.2 or above
Blazegraph is deployed in an external server and we are using SPARQL Repository connection to access it
-Below is a sample query to fetch all projects for a user
prefix projects: <http://www.sample.com/test/projects/>    prefix users:<http://www.sample.com/test/users/>  SELECT DISTINCT ?projects 	   WHERE{ 		?a projects:hasName ?projects ;  	      projects:hasUser users:1234 . 	 }

Thanks, is it Blazegraph 2.1.5 (which was released fairly recently) or the older version 2.1.4 ?
(I don't think that will make much difference, since they both seem to be using a very old Sesame 2.7 version, but one never knows...)

What is the resolution for the above issue

I'm not sure I understand what the actual issue is. Let me try and summarize: you use an Rdf4j SPARQLRepository to access a remote Blazegraph server and query it. If you use rdf4j 2.2, this works as expected. However, if you use rdf4j 2.3 or newer, this does not work. Did I understand that correctly?
What exactly are you seeing when it doesn't work as expected? Do you get an empty result? Does the query time out? Do you see any error messages, or anything in the rdf4j logs or in the Blazegraph server logs? Is this only for a specific query (do some queries work, and some queries not)?

I have ran a local blazegraph server (2.1.5) and have tried to query it through a SPARQLRepository (rdf4j 2.5.2). This worked as expected. The only thing I can think of is a syntax error in the data response that Blazegraph sends back (since rdf4j 2.2 our parsers have become better at detecting syntax errors). If that is the case, though, there should be an error to indicate this in the rdf4j logs.  Fixing it will involve configuring the Rio parser to be more forgiving.

I'm still facing this issue. Debugged into RDF4j framework code. Finally found out the piece of code which is causing the issue.
package org.eclipse.rdf4j.http.client; private void autoCloseRunnable(QueryResult<?> result, Runnable runner) { 		synchronized (executing) { 			executing.add(result); 		} 		executor.execute(() -> { 			try { 				runner.run(); 			} finally { 				synchronized (executing) { 					executing.remove(result); 				} 			} 		}); 	}
If there is a little time delay in execution of these lines, results are parsed correctly. otherwise it simply returns an empty array. Its surprising to see such an issue. All this time I thought blazegraph is not returning the results. But it is the parsing that is causing the issue!
Please fix it and let us know.

@lindamthomas07 the code you quoted is the part of the BackgroundResultExecutor, which executes processing of the server's query result in a separate thread. While it's possible there is a timing issue in play here, I'm having a hard time seeing it, or reproducing the problem.
Can you construct a minimal working example that demonstrates the problem and post/attach it here? If possible this example should include a sample of the data you're trying to query, the query you're trying to execute, and the actual code you use to run the query and process its result.

Closing for now as this is not reproducible with the available information. If you can provide additional details so that we can reproduce the problem we can re-open.


Improve load balancer's health check

Is your feature request related to a problem? Please describe.
The health check in the load balancer needs to consider both node state and consensus state.
Describe the solution you'd like
A clear and concise description of what you want to happen.
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.

Updated load balancer's health checking with '/health_check returns true'.

Updated load balancer's health checking with '/health_check returns true'.


Could you add the new property on Route objects, which can show if the route is replaced or pushed?

What problem does this feature solve?
I wanted to record the history of router in 'router.beforeEach' method to display the breadcrumbs, but I didn't find any information about if the route will be replaced or pushed. It's easy to make mistakes.
What does the proposed API look like?
A new boolean property called 'route.replaced'.

this is already on our roadmap and tracked in a ticket (and maybe even an issue)


enhancment: About page ui done

Description
Added basic UI for about page, added url_launcher and expandable dependencies required for opening this repo in the browser and UI respectively. The data on the page is not final and just placholder. contributors can work on it if they want too.
Fixes #28
Flutter Channel:

[x] I have used the Flutter Beta channel on my local machine

Type of Change:

Code
User Interface

Code/Quality Assurance Only

New feature (non-breaking change which adds functionality pre-approved by mentors)

How Has This Been Tested?
On my physical device
Screenshot

Current UI

Checklist:
Delete irrelevant options.

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas

Code/Quality Assurance Only

[x] My changes generate no new warnings

@Techno-Disaster I know you did it somewhere (on the issue I think), but its good to have visual proof on the PR as well (e.g.: screenshots/gifs). Can you add that to your description?

@Techno-Disaster I know you did it somewhere (on the issue I think), but its good to have visual proof on the PR as well (e.g.: screenshots/gifs). Can you add that to your description?

@isabelcosta i have it under screenshot dropdown :thinking: i did not want to make you guys scroll through the long screenshot so i put it in a dropdown :)

@bartekpacia updated with requested changes

@Techno-Disaster I know you did it somewhere (on the issue I think), but its good to have visual proof on the PR as well (e.g.: screenshots/gifs). Can you add that to your description?

@isabelcosta i have it under screenshot dropdown 🤔 i did not want to make you guys scroll through the long screenshot so i put it in a dropdown :)

@Techno-Disaster which dropdown?
you can also resize the image in markdown -> https://stackoverflow.com/questions/14675913/changing-image-size-in-markdown
Let me know where I can find the image.

Screenshot
Current UI

This one. in the PR body?

@Techno-Disaster i did not notice the dropdown! I just discovered this feature with your example 🤩 I thought it was not there. Sorry, you can make dropdown in your comment if you wish. But it should be more clear, I bet some people will also think its not there, so I don't know if using dropdown is the best option here for the PR body image, its easily missed

@Techno-Disaster i did not notice the dropdown! I just discovered this feature with your example  I thought it was not there. Sorry, you can make dropdown in your comment if you wish. But it should be more clear, I bet some people will also think its not there, so I don't know if using dropdown is the best option here for the PR body image, its easily missed

i agree, will put the screenshot directly from the next time. i have put a screenshot in the comments for now. will update PR body too.

noice

nine -  nine :smiley:

This screen seems fine @Techno-Disaster , but the content has to be reviewed in the future cc @anitab-org/content-team

yes ofc. thanks for the review


SIL: update for LLVM iplist/ilist changes

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Update SIL to deal with the behaviour of iplist/ilist changing to avoid UB.
NFC.

@swift-ci please test

CC: @dexonsmith @gottesmm

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - f8098379e510ffc06b739b5e4ed30d8636573857
Test requested by - @compnerd

This one looks like it is going to be relatively nasty.

Just based on my experience of messing with this sort of thing ; )

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - f8098379e510ffc06b739b5e4ed30d8636573857
Test requested by - @compnerd

@gottesmm never would've guessed this is going to be nasty!  The worst part of it is that this is one of two parallel sets of major restructuring :-(.  I need to look into a similarly nasty one involving GraphTraits still.  That may actually be worse than this.

This time with more testing.  This definitely works, as with this an other patches, I finally have tests passing on Linux again.

Okay, this is now the first in a series of patches for dealing with iplist changes on the LLVM side.  I don't really know what the best way forward is, but having the patches just sit around probably isn't the best.  @gottesmm ideas on how to deal with this?

@bob-wilson Is I think using your patch as a starting point for the next merge.

I've got a smaller set of patches almost ready to go. Some of the changes here, such as switching to use lists with a parent pointer, are orthogonal to making things work with the ilist changes. We could consider some of those, but first we should just do the minimal thing to make the code work.

I think we can close this now, since master-next has been working with the ilist changes for a while.


validationValue called when displaying the form

Unless I missed something, the validationValue function is called on elements when:

the form is displayed
a validationEvent occurs

So in the doc:

// This is an optional method that lets you hook into the validation event

should be more:

// This is an optional method that lets you hook into the validation process, which occurs at form startup and upon a validation event

My second remark is that I need to distinguish between the startup call and the other ones. The reason is that I perform async validation and I don't want this to occur at startup time, because it takes time and I am sure my initial data is correct.
Did you think about that? Are you sure validating at startup is required? If it is, maybe there could be a template argument saying "please don't validate at startup"? Or a validationValue boolean argument saying "this call is the startup call"?
While we discuss this, can you think of a workaround to detect the startup call inside validationValue?

I definitely support getting rid of the validation on startup, in most cases it is just a burden. We can support that behavior more elegantly with a method on the form block to validate containing elements that can run be manually on startup (or whenever else we need to validate).


Regression with XIB3 handling in Xib2Nib

Hello,
Commit 94e8f2bc2b7116f55b94bd271a7d94dd4dc21e60 introduced an issue where a number of attributes in a version 3 xib are no longer handled.
This can be seen by opening the Bezier Paths screen in WOCCatalog (screen should have a white background instead of black).
If I make this change:
diff --git a/tools/vsimporter/xib2nib/XIBObject.cpp b/tools/vsimporter/xib2nib/XIBObject.cpp
index 63b87e0..8779b15 100644
--- a/tools/vsimporter/xib2nib/XIBObject.cpp
+++ b/tools/vsimporter/xib2nib/XIBObject.cpp
@@ -274,7 +274,7 @@ void XIBObject::ScanStoryObjects(pugi::xml_node node) {
     _converter = NULL;
     _id = getAttrAndHandle("id");
     _className = node.name();
-    _isStory = IsStoryboardConversion();
+    _isStory = true;

     //  Go through all child nodes
     for (pugi::xml_node curNode : _node.children()) {

the attributes are handled again (Xib2Nib effectively treats the Xib3 format as a storyboard). But this might cause issues with the fix addressed by 94e8f2bc2b7116f55b94bd271a7d94dd4dc21e60.

fixed in latest release


Add dataloader

Create a dataloader based on this suggested notebook:

it uses tfrecord for efficiency on TPU (in particular wrt multiprocessing)
data is downloaded using img2dataset (based on my ongoing PR branch)
format is webp which seems very advantageous (see my benchmark below)

Related to webp format, here is relevant data I'm adding to img2dataset README:

This is now supported


refactor: icon to icons for alerts component

SUMMARY
This pr changes the removes the old icon component from alert component
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


Fixing link from the API to the guide

Not sure exactly how things are set up, but https://jorgecarleitao.github.io/arrow2/ seems to be an old version of the guide, with the link to the IO docs broken. I see that in the README that https://jorgecarleitao.github.io/arrow2/main/guide/ seems to be the latest version of the guide, so using it in the API docs.

gh-pages seems deprecated for a while. We can migrate to GitHub-actions instead: https://github.blog/2022-08-10-github-pages-now-uses-actions-by-default/

Obrigado, @datapythonista 🙇


Fix japanese bug

close: #48

@PhongTaKiai Could you upload the video? I want to check the bug.

@mafreud before
https://github.com/ailab-dev/app_buy_sell/assets/117698659/b2313cfc-8121-4372-8642-c0c7f06c97d1
fixed:
https://github.com/ailab-dev/app_buy_sell/assets/117698659/6993d5a5-de53-4269-be5f-72ed913da68b

@PhongTaKiai Why don't you use useEffect to set initial value to textEditingController?

@mafreud user profile fetch data from firebase but useEffect run first and did not update after fetching


Bug(Docs): A small error in the online documentation

Thanks for building this gorgeous chart, really love it!
One-line summary
There is a small error in the online documentation
Details:
The configure docs on radar chart now is like this:
splitLine: {
    show: { // <- this should be `lineStyle`
        color: ['#ccc'],
        width: 1,
        type: 'solid',
        shadowBlur: ...,
        shadowColor: ...,
        shadowOffsetX: 0,
        shadowOffsetY: 0,
        opacity: ...,
    },
},

In fact, it should be
splitLine: {
    show: true,
    lineStyle: {
        color: ['#ccc'],
        width: 1,
        type: 'solid',
        shadowBlur: ...,
        shadowColor: ...,
        shadowOffsetX: 0,
        shadowOffsetY: 0,
        opacity: ...,
    },
},

so it should be lineStyle, instead of show

Thanks! And glad to hear you love it:)


Cargo-size can't show fireware size on stm32g4

I use example of embassy. When I run cargo size, it all show zero.

And when I run cargo size -- -A, it show that it don't have .text and .data.

It looks like rust target was not set.


Add start fail modal in get-started-screen.tsx

Resolve the issue #92

looks good so far, the words are correct. Only one UX problem, it spins for a long time after pressing "Explore wallet", I think it should go directly to zero balances for both wallets, and not initialize the breez-sdk

yes, remove it for explore wallet, but show a zero balance for it even though it is not initialized yet

in explore wallet, when I click on "receive" it should pop up a modal at the bottom giving the user the option to log in.
That is no longer showing up, I think it needs to show up, and give them the start button.

yes. Here is the blink receive screen in "explore wallet" mode:

@islandbitcoin implemented the changes. Please test it out

@islandbitcoin implemented the changes. Please test it out

Almost there! one more thing you missed, lets make it the "start" button instead of the blink "login/create account" button".
You can also just send them back to the start screen if that is a better UX flow.

@islandbitcoin How should I change wordings on the bottom modal?

No changes to the wording. Just make the button take the user back to the start screen

this looks great! Approved


Deserialization causing System.ExecutionEngineException on Windows Phone 8.1 application

This exception is thrown after serializing a big Json file to a Dictionary object and causes the application to crash. It's a collection of links and informations about them.
It was an attempt to deserialize this json to this object type.
Does works on a desktop program, but not on mobile.

I am running into this problem on a Windows 10 phone, did you find a solution?

I ran into this problem spontaneously in an application where the code is otherwise in wide use and without problems.  But yes, specifically the symptom occurred when calling Deserialize on Newtonsoft.Json v<IP_ADDRESS>13
Turned out to be indicative of a corrupted .NET framework on the machine.  Running a repair on the .NET framework made the problem go away.


create cfncluster fails at computefleet

Hi.  I've created a modified ubuntu AMI for cfncluster based on ami-f2bf5492.  The custom AMI specifies a 12GB root device and I've included the following cluster parameters in my cfncluster:
base_os = ubuntu1404
master_root_volume_size = 12
compute_root_volume_size = 12
Everything else is defaulted (include 2 compute nodes)
When I first created the cluster it was successful based on some trivial tests.  I then deleted the cluster and a day later creating the same custom cluster failed at create ComputeFleet (which I assume is creating the compute nodes.  I noticed from the ec2 console that the two compute nodes were being initialized; then one completed; and just when the second one completed I received failure and rollback.  My wag is that it was a timeout associated with starting one of the compute nodes.  Anyway, while writing this post, I attempted to create the custom cluster and all worked well.  I'll try using the --norollback and check out the running instances.  Any other ideas or suggestions?  I'll attach the call stack of the failed issue.
aws_cfncluster_fail.txt
tia.
cheers, roy

Launch the cluster with the --norollback option and then look at the
/var/log/cfn-init.log file on a ComputeFleet instance for errors during the
bootstrapping.
On Monday, August 15, 2016, rollinroy<EMAIL_ADDRESS>wrote:

Hi. I've created a modified ubuntu AMI for cfncluster based on
ami-f2bf5492. The custom AMI specifies a 12GB root device and I've included
the following cluster parameters in my cfncluster:
base_os = ubuntu1404
master_root_volume_size = 12
compute_root_volume_size = 12
Everything else is defaulted (include 2 compute nodes)
When I first created the cluster it was successful based on some trivial
tests. I then deleted the cluster and a day later creating the same custom
cluster failed at create ComputeFleet (which I assume is creating the
compute nodes. I noticed from the ec2 console that the two compute nodes
were being initialized; then one completed; and just when the second one
completed I received failure and rollback. My wag is that it was a timeout
associated with starting one of the compute nodes. Anyway, while writing
this post, I attempted to create the custom cluster and all worked well.
I'll try using the --norollback and check out the running instances. Any
other ideas or suggestions? I'll attach the call stack of the failed issue.
aws_cfncluster_fail.txt
https://github.com/awslabs/cfncluster/files/419630/aws_cfncluster_fail.txt
tia.
cheers, roy
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/cfncluster/issues/127, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUVikLDKUXi9a_n2C7jWOkBNYSNZEB6ks5qgVRbgaJpZM4JlERg
.

I encountered this same issue today. Creating the cluster with the same template.

Just to update. It failed several times the other day, but when I tried again it worked. And I tried CfnCluster 1.3.1 and didn't reproduce this issue. So I thought it might be a glitch on AWS.

Can you please post your account number, region and cluster name. This is
not expected behavior and I would like to see if there is something we
explain.
On Tuesday, August 30, 2016, yuanzhou<EMAIL_ADDRESS>wrote:

Just to update. It failed several times the other day, but when I tried
again it worked. And I tried CfnCluster 1.3.1 and didn't reproduce this
issue. So I thought it might be a glitch on AWS.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/cfncluster/issues/127#issuecomment-243435245,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUViutbJ4WuEKY5oT8cQyMd5KJ_Pv-1ks5qlC1zgaJpZM4JlERg
.

@dougalb I deleted the failed cluster and recreated it. So I can't post the account number and cluster name. Sorry about that. But I did encounter this unexpected behavior several times with 1.2 the other day. I was using the same JOSN template via CloudFormation, which worked without any problem before. Then it failed several times and rolled back the cluster creation. I tried again before I went home that day, and the last try worked, surprisingly.
So far I don't see this creation issue with 1.3

Please just post your region and account number. I can find the rest.
When you say using the same template, are you using a custom CloudFormation
template?
On Tue, Aug 30, 2016 at 1:04 PM, yuanzhou<EMAIL_ADDRESS>wrote:

@dougalb https://github.com/dougalb I deleted the failed cluster and
recreated it. So I can't post the account number and cluster name. Sorry
about that. But I did encounter this unexpected behavior several times with
1.2 the other day. I was using the same JOSN template via CloudFormation,
which worked without any problem before. Then it failed several times and
rolled back the cluster creation. I tried again before I went home that
day, and the last try worked, surprisingly.
So far I don't see this creation issue with 1.3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/cfncluster/issues/127#issuecomment-243562000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUViidWBLMKAY1R8CQl_sk1sBfU8n1sks5qlIzngaJpZM4JlERg
.

@dougalb
region: us-east-1
account:<PHONE_NUMBER>61

The template I used was the one generated by CfnCluster, and I saved it into a JSON template file. The I uploaded the form via CloudFormation and specified parameters.

Okay, so that is not something we test today and not something we typically support. The issue you are having is likely related to the fact that you are trying to launch two stacks that both have the same value for EBSVolumeId. The second MasterServer is trying to attach the volume and it will fail.
You would see this in your logs, if you launch with --norollback and look at the /var/log/cfn-init.log.
I would avoid creating your own templates and rather use the one already hosted in S3, which is here: https://s3.amazonaws.com/us-east-1-cfncluster/templates/cfncluster-1.3.1.cfn.json
In addition, you must be very specific about what parameters you are copying between stacks.