subscribe/unsubscribe/events

Thanks for providing enhancements and adding to your instructions. It's much appreciated.
I am currently using the subscribe method to run a function once 'connected'. I have a few questions about how to handle monitoring activity to perform subsequent operations. Ideally, I'd like to receive events from the particular market(s) my bot is operating on and check to see if my orders need to be updated whenever the market changes.
If that is not possible, I expect I will run a timer that will loop through my startAfterConnected function at a regular interval. I'm hoping you can provide more guidance on observable events.

Now you need to use a timer. But in the next version I'll try to add an event to create a new block. Subscription for the account is also in the plans, but it turned out to be more complicated than I expected. I need time to test everything.

From btsdex v0.3.1 has three types of events:

connected - works once after connecting to the blockchain;
block - it works when a new block is created in the blockchain;
account - occurs when the specified account is changed (balance change).

For example:
const BitShares = require("btsdex");

BitShares.init("wss://bitshares.openledger.info/ws");

BitShares.subscribe('connected', startAfterConnected);
BitShares.subscribe('block', callEachBlock);
BitShares.subscribe('account', changeAccount, 'trade-bot');

async function startAfterConnected() {/* is called once after connecting to the blockchain */}
async function callEachBlock(obj) {/* is called with each block created */}
async function changeAccount(array) {/* is called when you change the 'trade-bot' account */}

This is awesome. Thanks!


Add a check for deltas before saving

The auto-approval controller was not kicking in, because the PackageRevision creation timestamp kept updating. Which is odd, and probably a bug in Porch. But, we want this anyway. It will avoid saving the package revision resources if there is no delta. This should prevent the forever growing task list, hopefully.
Still testing - one concern is that if we are refreshing claims, we may be stuffing away a timestamp which means this would never find matching hashes.

This is probably still useful to have, but it is not fixing the problem yet.
What I have found is that when the package variant controller saves the Kptfile to package revision resources, the Kptfile keys (name, description, etc.) and the condition keys (type, message, etc.) are in one order, while when the specializer does it they are in a different order. Both do sort the condition arrays themselves; the issue is the field names come out in different orders.
Suspiciously, they use different versions of kyaml (13.9 in porch, 14.2 in nephio), which is what serializes that. Though I didn't immediately spot differences that would cause this.
I am trying to see if I can build a version of porch-controllers with the newer kyaml, and also with some additional instrumentation. I think there are some fixes to the way existing revisions are processed that may also contribute.

Ugh. Building porch-controllers with an updated kyaml is a nightmare, it descends into updating k8s API, kustomize api, controller-runtime, etc.
I will just add my instrumentation.
Right now, what this means is that we have to manually approve the NF packages and other packages that go through specialization. Auto-approve won't do it. But we can work around that.

This is the method that seems to re-order the conditions:
https://github.com/GoogleContainerTools/kpt/blob/main/porch/controllers/packagevariants/pkg/controllers/packagevariant/injection.go#L284
Not 100% sure but checking now.

I will have a look. We did add something to sort conditions since the tests validations need something otherwise they fail as we check the expected result.

Here is where we sort conditions.
// SortConditions returns a kptfile with sorted conditions
func (r *kptFile) SortConditions() {
r.m.RLock()
defer r.m.RUnlock()
if r.GetKptFile().Status == nil || len(r.GetKptFile().Status.Conditions) == 0 {
	return
}

sort.SliceStable(r.GetKptFile().Status.Conditions, func(i, j int) bool {
	return r.GetKptFile().Status.Conditions[i].Type < r.GetKptFile().Status.Conditions[j].Type
})

}

/hold
Still testing this, but may not be needed given #295 - may still also be helpful, but if not needed we may want to defer it.

Hi @johnbelamaric , is this still relevant/needed?

What is the status of this? We should check if it's still an issue and fix in R4.

@kispaljr looks like we still have differences in the kptfile rendering. Did the sdk fix not address this?
#295


Add capability to set working directory as a command line argument.

As it stands, running alacritty -e 'cd foo' causes Command::spawn() to fail with OS error code 2. With this feature, running alacritty -c foo runs alacritty from the working directory foo via libc::chdir, with the intended purpose of starting the shell from a specific directory. It mirrors the functionality of the -cd flag from urxvt.

Maybe you could use the safe and portable interface instead? https://doc.rust-lang.org/std/env/fn.set_current_dir.html

... didn't even see that. My bad. I'll get to work on that.

This pull request has been fixed with the suggestions of @jwilm. Let me know if there's anything else you want changed!

That's a good suggestion. Added.

Beautiful!
Would you mind squashing your commits? Ready to merge after that.

Oh, it looks like the branch needs to be rebased as well. Something that conflicts must have been merged since this was opened. Sorry about that!
I just wanted to share with you that I'm pretty excited about this feature. I'm planning to setup a launcher for i3 which first checks if the active window is Alacritty, reads the process's (or I guess the shell process's) working directory and then spawns a new instance using this flag. :smile:

@zacharied sure!
Squashing is the act of coalescing n commits into a smaller number of commits. In this case, we'd like to just have a single commit for this feature.
Rebasing is the act of changing which commit your branch started from. In this case, you started on master at some point in the past, but the master branch has advanced during the time this PR has been open. Rebasing in this case means moving your commit to "be on top of" the current master.
For more info, GitHub's knowledge base article about rebasing is a good place to start.
It's slightly complicated by the fact that you've developed directly on master. For this case, I'd be happy to do it on your behalf.

If you wouldn't mind, I'd appreciate that. I could use an example for future reference, too.

Also, I incidentally wrote a script earlier that does what you suggested!

@zacharied thought you might like to know that I've got a branch that sets _NET_WM_PID. You might care about this because it allows supports what your script does without relying on the window title. See the commit messages for details.


DB backend for zone.list because zone deletion is slow

We can change the zone list del routine to be faster.
The current one can be slow because it attempts to flush and compact on every zone.  But this part can be taken out of the loop, at the end of the delzones command.
With a large zonelist file the fflush takes some time to complete and on every zone to delete this can add up.  By doing the flush only once at the end, it should be much more performant.
We can try this can ask if that improves, but I think it will, because actual performance is really a series of small writes, and a flush after it.  (But now, flush after writing every couple of bytes, hence slow).
Task it then to split the zone_list_del routine in the initial part _mark() and a finish up part that performs the flush and compact check.  And then perform those outside the loop in remote.c delzones.

I think we may also be able to do this for addzones, by the way.


Support using ^ for line continuation

See #979 for context. ^ is currently reserved, so this is a non-breaking change.

Hmm, ^ is now allowed in command name; this is only used by the ^ command.
To make the parse rule simpler ^ should be disallowed in command names and the ^ command should be renamed first.

Note that the ^ command isn't going to be used very often and should be moved to math:pow. The only reason I had not already implemented that command was due to the existence of ^. But in light of this issue I'll go ahead and implement that as well as math:pow10 which will defer to Go's math.Pow10() and is, presumably, an optimized form for a common case.

Since ^ is allowed as a command name, this is technically a breaking change. The only code that has its behavior changed is a lone ^ invocation:
^

Since this will trigger an exception anyway (^ requires two arguments), I am going to introduce this breaking change directly.


Tests broken #3309

Closes #3309

testExportHdWalletToSeedPhrase

yep, the same for me, working on it.

@hboon the problem is that is can't read created private key, and returns an error code -25300

it works on simulator, but not for tests. Running iOS 15


[SPARK-16919] Configurable update interval for console progress bar

What changes were proposed in this pull request?
Currently the update interval for the console progress bar is hardcoded. This PR makes it configurable for users.
How was this patch tested?
Ran a long running job and with a high value of update interval, the updates were shown less frequently.

Test build #63271 has started for PR 14507 at commit 596836a.

Is this worth making another knob to configure? Just disable it if it's at all annoying?

@srowen : Our daily jobs run remotely and users see the stdout / stderr logs in case they want to dig whats going on. With current update frequency, longer job's log tend to be flooded with console progress bar updates. Turning it off was an option but then one would have to click on the UI and correlate the timestamps with ones from the log (in case there is need to debug something). Setting the frequency to a higher value would give best of both the worlds.

Hm, would a higher value make sense? 200ms is pretty low. 3 seconds?
I get it, it seems like it's easy to just add a lever to pull to solve this, but it seems like this is a poor way to timestamp things anyway, and you really just want to disable the console progress bar, and perhaps look at better logging progress some other way.

Test build #63271 has finished for PR 14507 at commit 596836a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63271/
Test PASSed.

For batch jobs running for say ~10 hours, with 3 sec frequency, there would be 18k lines from the progress bar. That sounds like a lot. In Hadoop land they used to have 3 sec but it was made configurable [0] due to the same reason. See MAPREDUCE-6242 [1]. For ad hoc use cases, people would want to have faster response (eg. Presto updates every half a sec [2]). Coming up with a static value which works for both the worlds is hard.
To be precise, we don't rely on it for debugging issues. Its more for users so that they see that things are progressing and also while eye-balling to see if there is something obvious which went wrong.
[0] : https://github.com/apache/hadoop/blob/2e1d0ff4e901b8313c8d71869735b94ed8bc40a0/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/Task.java#L784
[1] : https://issues.apache.org/jira/browse/MAPREDUCE-6242
[2] : https://github.com/prestodb/presto/blob/master/presto-cli/src/main/java/com/facebook/presto/cli/StatusPrinter.java#L96

Hive has hive.querylog.plan.progress.interval for the same purpose: https://cwiki.apache.org/confluence/display/Hive/AdminManual+Configuration . Given that its mostly used for batch, the interval is set to 1 min by default.

OK, seems reasonable to me.

Test build #63278 has started for PR 14507 at commit ab7e1e2.

Test build #63278 has finished for PR 14507 at commit ab7e1e2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63278/
Test PASSed.

Merged to master


Cocoapods + Swift results does not build

Specifically, while the scheme for the Pods and any of the Pod descendants builds, trying to build my app’s (written in Swift) schema results in “Could not build Objective-C module ‘XlsxReaderWriter’”.
The more specific error is that “‘XMLDictionary.h’ could not be found” for BRARelationship.h.
I am not using a bridging header, as "XlsxReaderWriter-swift-bridge.h” does not seem to be discoverable from the Swift project.
I’m not a CocoaPod or Xcode veteran, so if there’s something else I need to be doing, please let me know!

This issue also occurs when using XlsxReaderWriter as a subproject to Swift 2.2/Xcode 7. I fixed it by first adding {$PODROOT}/XMLDictionary/XMLDictionary to the user headers for the app and adding XMLDictionary.h to the public headers under Build Phases for the Pod project.

Created a pull-request to fix, see https://github.com/renebigot/XlsxReaderWriter/pull/36

I was trying to use the framework with Swift in an OS X application and having XMLDictionary.h not found error. This link helped me to fix it.
Basically, all you need to do is:
"""
In build settings, point the Header Search Paths (if you use #include <file.h>) or User Header Search Paths (if you use #include "file.h") to the directory of the static library project. If the static library project is inside your app directory, use this:
"$(PROJECT_DIR)" (recursive enabled)
"""
Hope, it helps someone.


Add an all users option to list-domains action

Applicable spec: N/A
Overview
Provide a way of listing domains for all users per https://github.com/canonical/httprequest-lego-provider/issues/67.
Rationale
https://github.com/canonical/httprequest-lego-provider/issues/67.
Module Changes
N/A
Checklist

[x] The contributing guide was applied
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

no blocker: There are messages warning about removing some CVE from trivyignore.Can it be removed?

no blocker: There are messages warning about removing some CVE from trivyignore.Can it be removed?

I tried removing them, but trivy flagged them all, so not sure why it's saying they can be removed. I've added them back in now.


ocamlPackages.buildDunePackage: deprecate useDune2

Description of changes
I add depreciation notice for useDune2. We will remove it on 23.05 ? or next release 23.11 ?
Things done
If commit contain cmd: then it is automated but reviewed with git add -p

Will we remove dune_1 as well?

I put in draft because some package doesn't evaluate will be back soon.

Will we remove dune_1 as well?

It can be done in another sprint

I added many passthru.duneVersion = duneVersion; maybe I should put it un buildDunePackage ?

Explicitly setting duneVersion = "2"; just creates technical dept.

So new guideline are: use duneVersion only if different than default ? So using duneVersion = "1" or "3" is fine. And when we will change default version "1" and "2" will be fine ?

Seem ok to merge:
38 packages failed to build:
advi flitter glsurf ocamlPackages.cohttp-mirage ocamlPackages.conduit-mirage ocamlPackages.dns-certify ocamlPackages.dns-cli ocamlPackages.dns-client-mirage ocamlPackages.dns-mirage ocamlPackages.dns-resolver ocamlPackages.dns-server ocamlPackages.dns-stub ocamlPackages.extlib-1-7-7 ocamlPackages.git-mirage ocamlPackages.git-paf ocamlPackages.git-unix ocamlPackages.happy-eyeballs-mirage ocamlPackages.http-mirage-client ocamlPackages.irmin-git ocamlPackages.irmin-graphql ocamlPackages.irmin-http ocamlPackages.irmin-mirage-git ocamlPackages.irmin-mirage-graphql ocamlPackages.letsencrypt-mirage ocamlPackages.llvm ocamlPackages.magic-trace ocamlPackages.mimic-happy-eyeballs ocamlPackages.mirage-nat ocamlPackages.mirage-protocols ocamlPackages.mirage-stack ocamlPackages.paf ocamlPackages.paf-cohttp ocamlPackages.plotkicadsch ocamlPackages.soundtouch ocamlPackages.taglib ocamlPackages.tcpip ocamlPackages.torch spark2014

those are already broken on master. Some of this have a PR awaiting (I tested locally with the two merged and it succeeded: you don't see sail risc v on mac os)

Please keep the first commit only. The other changes might belong to a different PR if needed.

Please keep the first commit only. The other changes might belong to a different PR if needed.

done

Result of nixpkgs-review pr 225044 run on x86_64-linux 1


[BUG] Unexpected Expression

Some if expressions may not work with the current Expr implementation.
Therefore it is advised to wrap them in ().
if a==b {
    a
}

panics
Change to
if (a == b) {
   a
}

works

Please use this issue to list other unexpected Expr edge cases.


Add DOGE coin wallet to Tesla cars and pay for charging in DOGE

Feature Request
Describe the Feature Request

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

Wrong repository! I think you'll want to raise this one with Tesla!


User context not passed in _show for _users database

Expected behavior
View's _show supposed to work on admin-only databases, such as _users when accessed with admin privileges.
Current behavior
On attempt to access _show on _users database error 500 raised:
{
    "error": "case_clause",
    "reason": "{forbidden,<<\"Only administrators can view design docs in the users database.\">>}",
    "ref":<PHONE_NUMBER>
}

Possible Solution
User context need to be passed to fabric's open_doc here
Steps to Reproduce
In _users db create following two ddocs:
{
    "_id": "_design/users",
    "views": {
        "names": {
            "map": "function(doc) { emit(doc.name); }"
        }
    },
    "lists": {
        "names": "function(head, req) { var row; while (row = getRow()) { send(\"name: \" + row.key + \"\\n\"); } }"
    }
}

{
    "_id": "_design/show-function-examples",
    "shows": {
        "summary": "function(doc, req) {return '<em>' + doc.name + '</em>';}"
    }
}

Run local cluster and query with curl -u $CRED http://localhost:15984/_users/_design/show-function-examples/_show/summary/_design/users
Your Environment

Version used: 2.1.0-2f45a72cd
Browser Name and version: httpie 9.9.9
Operating System and version (desktop or mobile): Darwin Kernel Version 15.6.0

Reference issue apache/couchdb#645


Audio prompts

Allow enable/disable of audio prompts on chat.

Check the menu in the sidebar, should have 'Sound' that enables and disables audio

@ToastyStoemp That feature is only in the browser plugin.

I'm using the https://hack.chat/ URL and sometimes miss conversations because there is no prompt that a response was int he "channel" hence requesting an audio prompt.
Hope that clarifies things. If there is a chrome/firefox extention.plugin, please provide a link.

https://github.com/ToastyStoemp/Hack.Chat-Enhancement-kit

Thank you kindly :)
H
On Tue, Sep 22, 2015 at 1:34 PM, Jakob Löw<EMAIL_ADDRESS>wrote:

https://github.com/ToastyStoemp/Hack.Chat-Enhancement-kit
—
Reply to this email directly or view it on GitHub
https://github.com/AndrewBelt/hack.chat/issues/73#issuecomment-142260715
.


Fix portuguese translation

The translation file has been renamed and the translations corrected.

Thanks for your contribution, it's very appreciated.


Provide a CT command line app

OpenSSL has no command line tool for working with Signed Certificate Timestamps. It would be great to have one.
Features that I might expect:

Ability to read SignedCertificateTimestamp and SignedCertificateTimestampList data contained in a file
Print out SignedCertificateTimestamp/SignedCertificateTimestampList data in a human readable format
Submit a certificate to a CT log and receive back a SignedCertificateTimestamp
Create a "serverinfo" file given SCT data
Read a "serverinfo" file containing SCT data

@RJPercival any thoughts? I have recently found myself using hex editors to create what I needed to

The only difficulty I can foresee with any of those features is handling the JSON sent to and received from a CT log. There has understandably been little appetite for adding a JSON parser to OpenSSL (though one has been written). The submission could be assembled without a full-blown JSON parser, but decoding responses would require one. The tool could simply print the returned JSON, rather than attempting to convert it into a TLS-encoded SCT, but I'm not sure how helpful that would be, since OpenSSL wouldn't be able to do anything with it. For all of the other features, the SCT/SCTList could be TLS-encoded in PEM files, so OpenSSL could read/write them.

There has understandably been little appetite for adding a JSON parser to OpenSSL (though one has been written).

Oh - that's cool. Did someone submit that before and it was rejected? I see it has the OpenSSL licence on it. Personally I am open to its inclusion (although I haven't reviewed in detail). I don't know what others on the team think  (@richsalz, @levitte). I think the ability for us to to send submissions and be able to parse the response is something that we really should have.
@RJPercival would you be interested in taking this on?

I discussed it with @ekasper, but neither of us was enthusiastic about getting a JSON parser into OpenSSL, especially given the time constraints for getting the original CT API merged. Therefore, I stripped that code out before submitting a PR, so it's never been reviewed. It's worth revisiting now though. I agree that it would be very helpful if OpenSSL could do this.
I don't have much bandwidth for working on OpenSSL, so I can't commit to taking this on unfortunately.

I am against putting a JSON parser into the openssl runtime.  For now just treat json as the input and output format.

I'm not sure it's worth implementing the "submit to a CT log" feature in that case, since it wouldn't do anything that you can't already do with curl (if all it does is take whatever JSON you give it, connect to a CT log and print out the JSON response).

Marking as inactive to be closed at the end of 3.4 dev barring further input


Question: how to use arrays in environment variables?

environments:
  default:
    values:
    - tolerations:
      - key: kubernetes.azure.com/scalesetpriority
        operator: Equal
        value: spot
        effect: NoSchedule
      - key: pool
        operator: Equal
        value: workers
        effect: NoSchedule

releases:
- name: jaeger
  chart: jaegertracing/jaeger-operator
  labels:
    app: jaeger
  values:
  - tolerations: {{ .Environment.Values.tolerations }}

doesn't work, it appears it treats it like a string, not like an array

try something like this
  values:
  {{- toYaml .Environment.Values | nindent 2 }}

mhm, I think I tried toYaml and it said he doesnt recognize that, let me re-test though

mkay, I swear I tried this before raising this, but it didnt work. it works now. thanks.


How to register FirebaseUser, FirebaseUserProvider in admin?

Can someone help how to register the models of the package to be visible in the admin panel?
I thought It would work if i add an admins.py with the code below to the package
from django.contrib import admin
from .models import FirebaseUser, FirebaseUserProvider

admin.site.register(FirebaseUser)
admin.site.register(FirebaseUserProvider)

you can just import the models from the app and register them under an app's admin file (e.g. user/admin.py):
from drf_firebase_auth.models import FirebaseUser, FirebaseUserProvider

admin.site.register(FirebaseUser)
admin.site.register(FirebaseUserProvider)


Crave variables not randomize by default ?

Hi,
I now have Crave integrated and working in my "elaborate" UVM-SC testbench. Crave variables are being randomized subject to the Crave constraints I put in place - using the experimental API as advised - when invoking randomize(), as one would expect. It is still early going for me and I'd like to do quite a bit more exploration with using

more complex constraints
layered constraints (i.e. hierarchical across "has-a" class object relationships)
overriding constraints (i.e. across "is-a" class object relationships)
using crave vectors, arrays
etc.

Two issues I am finding thus far I would like to report here:

Crave vectors: using a crave vector yields an internal error, which has since been reproduced and confirmed by Thilo. I have pasted the error down belo for completeness

Crave variables are only randomized when there are explicit active constraints on them, meaning constraints that I have coded. In other words, a crave variable that is not subject to a written constraint does not get randomized at all and instead holds its initial/current value. This is surprising and not aligned with the behavior of SystemVerilog rand variables, where each rand variable gets randomized by default within its type domain. Is this a bug or a Crave "feature"? That is, is this intended behavior?
If it were then this would not set the stage well for a constrained random approach towards targeting coverage closure where stimulus attributes are minimally constrained early on - letting the power of randomness as loose as possible - until remaining coverage holes need be targeted in a more directed manner with increasing constraints.

Regards - Hans
[cmd.00c4 5m:19s] In file included from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/../ir/visitor/metaSMTNodeVisitor.hpp:37:0,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/FactoryMetaSMT.hpp:31,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/VariableSolver.hpp:35,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/VariableGenerator.hpp:30,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/Generator.hpp:33,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/ConstrainedRandom.hpp:36,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/include/vcn_uvmf/sc/src/vcn_test.h:52,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/include/vcn_uvmf/sc/vcn_uvmf:37,
[cmd.00c4 5m:19s]                  from /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/vidcore/cdefe/src/verif/uvmf_sc_tb_package/ltb/sc_main.cpp:30:
[cmd.00c4 5m:19s] /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/../ir/visitor/../../frontend/RandomBase.hpp: In instantiation of 'void crave::__rand_vec_base1<T1, T2>::gen_values(unsigned int) [with T1 = sc_dt::sc_uint<64>; T2 = sc_dt::sc_uint<64>]':
[cmd.00c4 5m:19s] /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/vidcore/cdefe/src/verif/uvmf_sc_tb_package/ltb/sc_main.cpp:465:1:   required from here
[cmd.00c4 5m:19s] /local_vol1_nobackup/user/hvdschoot/projects/vcn5_0_5342109/out.er/linux_3.10.0_64/common/pub/crave/include/crave/backend/../ir/visitor/../../frontend/RandomBase.hpp:163:28: error: 'crave::randv<sc_dt::sc_uint<64> > r' has incomplete type
[cmd.00c4 5m:19s]      static randv r(NULL);

I think this issue can be closed


Rule search

This update shows you missed rules as you type.
The search starts from after any previously found rule's completion, and finds the next longest completion from the smallest amount of key buffer context. Backspaces and buffer reset are handled.
The st_on_missed_rule callback function has a weak attribute so that the user can override it. By default it just prints the rule to the console.
To test this, add #define SEQUENCE_TRANSFORM_MISSED_RULES to your layout's config.h file, and SRC += sequence_transform/key_stack.c to your rules.mk file.

I added user token symbol insertion in the rule sequence/transform strings.
I reviewed my code and I can't seem to find a bug, but I'm getting random corruption in the console...
(this could be a console lag issue where it doesn't get the next utf8 byte fast enough so gives up and prints garbage...)
Can you guys please test on your end?

typing first by hand with my ruleset crashes the keyboard, probably because of rs@ -> rst rule and f* -> first, will investigate this later if you wont

Removed the utf8 code. Pretty stable now. I think this is ready for merging.


Fixes bug that causes load to not work when there is not a weather event

Checks for null weather event in the GameState.

Need to include save file in PR? But other than that LGTM

Nah, that is just for one the save file changes in a formatting way and even then is just to show what changed and shouldn't matter / crash


feat: Clean up just files

@HikariKnight
Good start here, this does the split we talked about which should make the actual cleanup treatment like ublue-os/config got easier.

yes it should.


Alternative PR: Adding default key within controller.root

It looks like the wrapper for controller.get doesn’t work like it
should what wasn’t covered by tests!
There is no time to work on it now - I am 3 hours behind my day plan -
so I stop it now. Please merge one of the three PRs and open another
issue about right implementation of the wrapper.

https://github.com/tessel/t2-cli/pull/498
https://github.com/tessel/t2-cli/pull/501

also fixes https://github.com/tessel/t2-cli/issues/497
:smile:

@johnnyman727

It was fixed here.
[...] this PR does not solve the problem so I will close it.

well, the PR does solve MY problem as well as my other alternative suggested PR. You didn't give a suggestion HOW you would solve the existing problem - and this isn't fair enough.
(ok, you just remember the reason you hold against... about https://github.com/tessel/t2-cli/issues/455 - I didn't know about BUT the mentioned argument about doesn't match today: The wrapper fixes this .. NOT the removing of default: ... )
Your arguments are not enough to explain why no default should be in the global --key option (commands without key ignores a default) OR why the root command shouldn't override the global --key option also with a default AND finally your arguments doesn't explain why it shouldn't be handled within controller.root (closed PR) when all other solutions doesn't match. What do you want from me ?
The situation is very very easy: The problem exist - show me a better solution than one of my three suggestions. One from you would be fair enough...
The issue exists !

@johnnyman727

It was fixed here.
[...] this PR does not solve the problem so I will close it.

well, the PR does solve MY problem as well as my other alternative suggested PR. You didn't give a suggestion HOW you would solve the existing problem - and this isn't fair enough.
(ok, you just remember the reason you hold against... about https://github.com/tessel/t2-cli/issues/455 - I didn't know about BUT the mentioned argument about doesn't match today: The wrapper fixes this .. NOT the removing of default: ... )
Your arguments are not enough to explain why no default should be in the global --key option (commands without key ignores a default) OR why the root command shouldn't override the global --key option also with a default AND finally your arguments doesn't explain why it shouldn't be handled within controller.root (closed PR) when all other solutions doesn't match. What do you want from me ?
The situation is very very easy: The problem exist - show me a better solution than one of my three suggestions. One from you would be fair enough...
The issue exists !

Hi @Student007, I suggested a solution here in my comments above. To reiterate, I think we should check if someone is attempting to use t2 root and does not have valid SSH keys in the designated key path (either provided or the default) and present an error if that's the case.

Hi @Student007, I suggested a solution here in my comments above. To reiterate, I think we should check if someone is attempting to use t2 root and does not have valid SSH keys in the designated key path (either provided or the default) and present an error if that's the case.

@johnnyman727

The resolution for this issue should actually be a better error message that explains that you'll need an SSH key for t2 root.

your "resolution" was better error msg but keys are there as you have seen by testing yourself:

@Student007 yes, the CLI isn't currently designed to use two Tessels for anything. We should actually have an overarching issue to fix that at some point. But as it is, we have never tested the code with two Tessels attached (because, historically, we just haven't had very many Tessels).

I don't think this is an issue with t2 root.

however all three provided PR solve the problem - if you think it is a deeper thing (I don't belief) then it is a new issue (what can override the current PRs after merged one). I like to work with t2 rootand the problem is solved properly with all three PR. I will not dive into your additional problems more as I did (because there is no more time)
[x] default key is present at ~/.tessel/id_rsa
[x] Both Tessels are provisioned !
[!] the ONLY valid solution is (as for all other commands) t2 root also should default to the default key if it is not set by --key
lets begin a cleaner discussion here https://github.com/tessel/t2-cli/issues/497 (think you got what I mean and I got you like I should do a much deeper dive into the problems of the cli when working with multiple tessels - but it is not the time for games like this ! Excuse me!).

[!] the ONLY valid solution is (as for all other commands) t2 root also should default to the default key if it is not set by --key

@Student007 perhaps I don't understand the issue you are trying to tackle because the above case is true. The CLI does use a default path without having to explicitly call setDefaultKey. You can check this for yourself by printing out whether Tessel .isProvisioned and the key path here.


Grid2 Doesn't use css gap? Why?

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Css Gap is the best css feature ever. I can't understand why the shiny new Mui Grid2 would choose an old hacky technique for spacing?
Can we opt into this? This is a showstopper for me.
Examples 🌈
.
Motivation 🔦
.

Related to #34510, https://github.com/mui/material-ui/pull/35104#issuecomment-1312475844

Related to #34510, #35104 (comment)

@oliviertassinari This issue is not related to those. The way we want the Grid component to work cannot be applied using CSS gap.
@httpete Here is the demo of why using gap does not work for the current API: https://codesandbox.io/s/poc-grid-gap-e1nq9l?file=/index.js
For the Grid item, you will need to know how many items are in a row, so that you can do this:
<div
  className="item"
  css={{
    width: "calc((100% - $gap * $(amount of items - 1)) / 3)",
    background: "tomato",
    color: "#fff"
  }}
>
  half
</div>

You can't mix gap with width in percentage.

@siriwatknp Right, great point.
So @httpete you can subscribe to #9513 for a version of the Grid that uses the gap instead of the negative margin. It would need to use CSS grid, over CSS flexbox.

No it wouldn’t, css gap works fine with flex box, been using it for years.On Nov 14, 2022, at 7:19 PM, Olivier Tassinari @.***> wrote:
@siriwatknp Right, great point.
So @httpete you can subscribe to #9513 for a version of the Grid that uses the CSS gap instead of the negative margin. It would need to use CSS grid, over CSS flexbox.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

css gap works fine with flex box

@httpete True, but it's not the problem.

No it wouldn’t, css gap works fine with flex box, been using it for years.

gap works with flexbox but it does not work for the Grid component API.


Honor the Translator contract

The Illuminate\Contracts\Translation\Translator interface has no get() method. It works with Illuminate\Translation\Translator (where get() method exists), but with a custom Translator implementation, it breaks here.

I was going to report the same issue


add a blog

@huan
hope check please,thanks

You need to fix the following linting problem first:
https://github.com/wechaty/wechaty.js.org/pull/621/checks?check_run_id=1548216326#step:5:24

Congratulations! It seems that your commits passed the CLA.
However, you need to fix the following linting problem in this PR so that we can merge it:
https://github.com/wechaty/wechaty.js.org/pull/621/checks?check_run_id=1548216326#step:5:24

@huan thank you for your reminder. It's  fixed now

You can find the CI result at the bottom of this PR like the following screenshot:

We need to make it green before we can continue processing this PR which means it passed the check.

@iTingle  Thank you very much for your contribution!

You've invited iTingle to Wechaty! They'll be receiving an email shortly. They can also visit https://github.com/wechaty to accept the invitation.

I have invited you to join our Wechaty GitHub Organization, please accept it by following the above message.
And we also have a WeChat room for contributors only which can discuss Wechaty at a deep level, you are welcome to join and if you are interested please contact @lijiarui to ask for an invitation.
Cheers!

@iTingle  Thank you very much for your contribution!

You've invited iTingle to Wechaty! They'll be receiving an email shortly. They can also visit https://github.com/wechaty to accept the invitation.

I have invited you to join our Wechaty GitHub Organization, please accept it by following the above message.
And we also have a WeChat room for contributors only which can discuss Wechaty at a deep level, you are welcome to join and if you are interested please contact @lijiarui to ask for an invitation.
Cheers!


expiresAt in Seconds not Milliseconds

JWT expiration timestamp should be set in seconds. In the current implementation getCurrentTime uses date's getTime method which is in milliseconds.
Is there any reason for this i'm overlooking? Happy to send a PR to fix.
Thanks!

I don't quite remember the reasoning behind. But maybe @erichonkanen can shine some light. I do know there's been a bit of confusion around that so anything that improves that is welcome, although a change like this would be a breaking change, I'd have no problem with that.

I hear you on the confusion - did quite a bit of double checking before bringing the issue up!
According to the draft it's suppose to be in seconds. Also i'm finding most libraries are using the seconds - surprised more haven't ran into an issue actually.
However with that all said it is a breaking change!
I'll get a PR together and send it over.

originally it was set up to support either seconds or milliseconds depending on what the backend server used...

@erichonkanen any specific reasons on why the default implementation is in milliseconds?

To be honest no... it probably should have defaulted to seconds but I wasn't sure if e.g. node backends use seconds like python does

@digia let me know if you're still interested in putting a PR together for this

@jpadilla Yes! Was waiting for the test issue to be sorted out.
Should be able to work on it later today!

Fixed here: https://github.com/jpadilla/ember-simple-auth-token/pull/141

Yes, fix pr is sent.

Closed by #141


Questions

Hello,
How do you configure and operate gopnik for multiple RenderPools? (I guess it's the term)
What I wish to objectively achieve is: have two options of OSM styles - a custom and the original - want both cached and my applications should reach one or another, depending on it's needs.
Thanks in advance

I guess, @orofarne could help you with that question.


Installing via Helm reports ElasticSearch discovery errors

Hi! We are trying to test Amundsen using the helm templates to deploy. We referenced the README at https://github.com/amundsen-io/amundsen/tree/master/amundsen-kube-helm, but ran into issues with the ElasticSearch cluster.
Expected Behavior
We took the following steps:
Download the Amundsen helm templates:
$ git clone git@github.com:plaid/amundsen.git
$ cp -r newmundsen/amundsen-kube-helm/ amundsen/

Configure dependencies
$ helm repo add elasticsearch https://kubernetes-charts.storage.googleapis.com
$ helm dependency update ./templates/helm/

installing, with no modifications to values.yml
$ helm upgrade --install amundsen ./templates/helm --values templates/helm/values.yaml --kube-context=<ctx>   --namespace=<ns>
Release "amundsen" does not exist. Installing it now.
NAME: amundsen
LAST DEPLOYED: Tue Dec  1 18:28:31 2020
NAMESPACE: <ns>
STATUS: deployed
REVISION: 1

Current Behavior
Some of the pods start up:
$ kubectl -n <ns> get pods | grep amundsen
amundsen-elasticsearch-client-58996dd768-tsfbs   0/1     Running   0          6m26s
amundsen-elasticsearch-data-0                    1/1     Running   0          6m26s
amundsen-elasticsearch-master-0                  1/1     Running   0          6m26s
amundsen-frontend-79d647b9cf-n86gm               1/1     Running   0          6m26s
amundsen-metadata-6466556944-ntg2q               1/1     Running   0          6m26s
amundsen-search-b77655576-9nbvf                  1/1     Running   0          6m26s

but, with logging errors:
elasticsearch-client
...
$ kubectl -n <ns> logs amundsen-elasticsearch-client-58996dd768-tsfbs

[2020-12-02T02:35:42,911][WARN ][o.e.d.z.ZenDiscovery     ] [amundsen-elasticsearch-client-58996dd768-tsfbs] not enough master nodes discovered during pinging (found [[]], but needed [1]), pinging again
[2020-12-02T02:35:43,071][WARN ][r.suppressed             ] [amundsen-elasticsearch-client-58996dd768-tsfbs] path: /_cluster/health, params: {}
org.elasticsearch.discovery.MasterNotDiscoveredException: null
	at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$4.onTimeout(TransportMasterNodeAction.java:262) [elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:322) [elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:249) [elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:564) [elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-6.8.2.jar:6.8.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:835) [?:?]
[2020-12-02T02:35:45,912][WARN ][o.e.d.z.ZenDiscovery     ] [amundsen-elasticsearch-client-58996dd768-tsfbs] not enough master nodes discovered during pinging (found [[]], but needed [1]), pinging again

amundsen-elasticsearch-master-0
...
[2020-12-02T02:28:56,749][INFO ][o.e.p.PluginsService     ] [amundsen-elasticsearch-master-0] no plugins loaded
[2020-12-02T02:29:02,051][INFO ][o.e.d.DiscoveryModule    ] [amundsen-elasticsearch-master-0] using discovery type [zen] and host providers [settings]
[2020-12-02T02:29:03,350][INFO ][o.e.n.Node               ] [amundsen-elasticsearch-master-0] initialized
[2020-12-02T02:29:03,350][INFO ][o.e.n.Node               ] [amundsen-elasticsearch-master-0] starting ...
[2020-12-02T02:29:03,673][INFO ][o.e.t.TransportService   ] [amundsen-elasticsearch-master-0] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
[2020-12-02T02:29:03,730][INFO ][o.e.b.BootstrapChecks    ] [amundsen-elasticsearch-master-0] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2020-12-02T02:29:03,784][WARN ][o.e.d.z.UnicastZenPing   ] [amundsen-elasticsearch-master-0] failed to resolve host [amundsen-elasticsearch-discovery]
java.net.UnknownHostException: amundsen-elasticsearch-discovery: Name or service not known
	at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
	at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:929) ~[?:?]
	at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1515) ~[?:?]
	at java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:848) ~[?:?]
	at java.net.InetAddress.getAllByName0(InetAddress.java:1505) ~[?:?]
	at java.net.InetAddress.getAllByName(InetAddress.java:1364) ~[?:?]
	at java.net.InetAddress.getAllByName(InetAddress.java:1298) ~[?:?]
	at org.elasticsearch.transport.TcpTransport.parse(TcpTransport.java:536) ~[elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.transport.TcpTransport.addressesFromString(TcpTransport.java:489) ~[elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.transport.TransportService.addressesFromString(TransportService.java:743) ~[elasticsearch-6.8.2.jar:6.8.2]
	at org.elasticsearch.discovery.zen.UnicastZenPing.lambda$resolveHostsLists$0(UnicastZenPing.java:189) ~[elasticsearch-6.8.2.jar:6.8.2]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-6.8.2.jar:6.8.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:835) [?:?]
[2020-12-02T02:29:06,852][INFO ][o.e.c.s.MasterService    ] [amundsen-elasticsearch-master-0] zen-disco-elected-as-master ([0] nodes joined), reason: new_master {amundsen-elasticsearch-master-0}{HaWRmNmrRI-AhuHfNw-rrg}{TkGCWhNwRPajFSZgYlGeag}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}
[2020-12-02T02:29:06,856][INFO ][o.e.c.s.ClusterApplierService] [amundsen-elasticsearch-master-0] new_master {amundsen-elasticsearch-master-0}{HaWRmNmrRI-AhuHfNw-rrg}{TkGCWhNwRPajFSZgYlGeag}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}, reason: apply cluster state (from master [master {amundsen-elasticsearch-master-0}{HaWRmNmrRI-AhuHfNw-rrg}{TkGCWhNwRPajFSZgYlGeag}{<IP_ADDRESS>}{<IP_ADDRESS>:9300} committed version [1] source [zen-disco-elected-as-master ([0] nodes joined)]])
[2020-12-02T02:29:06,867][INFO ][o.e.h.n.Netty4HttpServerTransport] [amundsen-elasticsearch-master-0] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
[2020-12-02T02:29:06,867][INFO ][o.e.n.Node               ] [amundsen-elasticsearch-master-0] started

We are able to hit the frontend, where we can see that the search does seem to be failing

Version info
Amundsen Master from 12/1/2020
$ helm version
version.BuildInfo{Version:"v3.2.0", GitCommit:"e11b7ce3b12db2941e90399e874513fbd24bcb71", GitTreeState:"clean", GoVersion:"go1.13.10"}

We did not modify the elasticsearch version, so we think we should be using 1.32.0
Context
We're trying to test it out, but aren't sure how to debug helm->ES issues
Your Environment
The k8s cluster was built about a year ago (late 2019 / early 2020)

cc @javamonkey79
But I would suggest to use a managed ES service instead of creating one yourself. It is a bit complicated to build/operate one (https://github.com/pires/kubernetes-elasticsearch-cluster)

another thing worth mentioning once your current issue is solved is to make sure ES is within 6.x(we test 6.7).

Thanks for the reply @feng-tao , I also tried with
helm repo add elasticsearch https://helm.elastic.co/

but seem to have the same issue. By managed ES service, do you mean something like AWS managed ElasticSearch? I will try that as well.
To do that, is it correct to change enabled to false here:
elasticsearch:
  # elasticsearch.enabled -- set this to false, if you want to provide your own ES instance.
  enabled: false

and then  modify teh search service here
  ##
  ## search.elasticsearchEndpoint -- The name of the service hosting elasticsearch on your cluster, if you bring your own. You should only need to change this, if you don't use the version in this chart.
  ##
  elasticsearchEndpoint:

to point to an ES URL?
elasticsearchEndpoint: https://<cluster>.us-east-1.es.amazonaws.com

@AustinBGibbons we run ES in our chart and not standalone. This is all we have in our values file, to make it work:
elasticsearch:
  client:
    serviceType: LoadBalancer
    serviceAnnotations:
      external-dns.alpha.kubernetes.io/hostname: amundsen-elasticsearch-someenvironment.some-account-name.accounts.my-company.com
      service.beta.kubernetes.io/aws-load-balancer-internal: <IP_ADDRESS>/0
      service.beta.kubernetes.io/aws-load-balancer-type: nlb

I checked my shell history, and we did not have to do this:
$ helm repo add elasticsearch https://kubernetes-charts.storage.googleapis.com
$ helm dependency update ./templates/helm/

The thing that sticks out to me, is this:
$ helm version
version.BuildInfo{Version:"v3.2.0", GitCommit:"e11b7ce3b12db2941e90399e874513fbd24bcb71", GitTreeState:"clean", GoVersion:"go1.13.10"}

Per the readme, here is the helm prerequisite:
Helm 2.14+
However, that "+" is a little misleading. I think it should be:
Helm [2,3)
tl;dr; this chart needs to be on helm v2 even better v2.14. I suspect that with helm 3 it is not pulling the right ES dependent chart, or, in the wrong order. I think your choices are to:

Try with helm 2 (I understand this may not be possible for you)
Try with a managed instance - it looks like you have made correct assumptions in your previous comment
Try to narrow down which ES chart helm 3 is installing, and try to get it to the right version; if that is already they case, then there is likely some unexpected config; based on your original log post, it looks like the amundsen-elasticsearch-discovery is either not being created, or being created out of order; I'm not sure.
Try updating your values file, to create a loadbalanced client as I shared above, it might be why the discovery service isn't coming up.

Thanks for the reply @javamonkey79 , yeah unfortunately we're locked into helm 3.x - I am also getting errors with the frontend service trying to communicate with the metadata service as well as some AUTH configurations I don't understand, so perhaps it's just incompatible - I am a helm newbie so not sure how to say for sure. I will experiment restarting from scratch on helm 3, thanks!
(frontend -> metadata errors when hitting the landing page, fwiw)
2020-12-02T16:05:43+0000.541 [ERROR] v0.current_user:47 (9:MainThread) - Encountered exception: AUTH_USER_METHOD is not configured
Traceback (most recent call last):
  File "/app/amundsen_application/api/v0.py", line 28, in current_user
    raise Exception('AUTH_USER_METHOD is not configured')
Exception: AUTH_USER_METHOD is not configured
2020-12-02T16:05:43+0000.551 [ERROR] v0.get_bookmark:517 (8:MainThread) - Encountered exception: AUTH_USER_METHOD is not configured
Traceback (most recent call last):
  File "/app/amundsen_application/api/metadata/v0.py", line 491, in get_bookmark
    raise Exception('AUTH_USER_METHOD is not configured')
Exception: AUTH_USER_METHOD is not configured
2020-12-02T16:05:43+0000.560 [DEBUG] connectionpool._new_conn:205 (10:MainThread) - Starting new HTTP connection (1): amundsen-metadata:5002
2020-12-02T16:05:43+0000.979 [DEBUG] connectionpool._new_conn:205 (11:MainThread) - Starting new HTTP connection (1): amundsen-metadata:5002
2020-12-02T16:05:44+0000.404 [DEBUG] connectionpool._new_conn:205 (9:MainThread) - Starting new HTTP connection (1): amundsen-metadata:5002
2020-12-02T16:05:46+0000.565 [ERROR] v0.get_tags:363 (10:MainThread) - Encountered exception: HTTPConnectionPool(host='amundsen-metadata', port=5002): Max retries exceeded with url: /tags/ (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fad64b839d0>, 'Connection to amundsen-metadata timed out. (connect timeout=3)'))
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 159, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw)
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
    raise err
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
    sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 354, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.7/http/client.py", line 1277, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1323, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1272, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.7/http/client.py", line 1032, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.7/http/client.py", line 972, in send
    self.connect()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 181, in connect
    conn = self._new_conn()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 164, in _new_conn
    (self.host, self.timeout))
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPConnection object at 0x7fad64b57c10>, 'Connection to amundsen-metadata timed out. (connect timeout=3)')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 638, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 399, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='amundsen-metadata', port=5002): Max retries exceeded with url: /popular_tables/?limit=4 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fad64b57c10>, 'Connection to amundsen-metadata timed out. (connect timeout=3)'))
During handling of the above exception, another exception occurred:

...

Thanks for the update @AustinBGibbons, best of luck.
@feng-tao I would vote that this issue be closed on account of the helm 2 vs 3 issue and that we put up a story to move to helm 3. My team and I won't be able to work on it until at least Q1, if at all, but, there may be others who are interested in doing the work.

sg

@AustinBGibbons is your Neo4j pod up and alive? Do you have data loaded into it as per step 6 in https://www.amundsen.io/amundsen/installation/#bootstrap-a-default-version-of-amundsen-using-docker
Also, as long as you haven’t configured authentication the AUTH_USER_METHOD is expected.
2020-12-02T16:05:46+0000.565 [ERROR] v0.get_tags:363 ... in https://github.com/amundsen-io/amundsen/issues/830#issuecomment-737409848 on the metadata service looks to me like your main issue

For the record we’re happily using helm 3 here - and have been since https://github.com/amundsen-io/amundsen/pull/373 (although not on latest Amundsen chart version, but something around chart version 1.1’ish)
Another indication of the same (see issue title): https://github.com/amundsen-io/amundsen/issues/486
Longer term we should switch to official ES chart mentioned first in https://github.com/amundsen-io/amundsen/issues/830#issuecomment-737320815 - the old chart, even the whole helm stable repo is deprecated. It AFAIK was even taken down in November but has been put back up because it broke to much for people. See October 26th post and later on https://helm.sh/blog/

I think all of this was configuration specific to our k8s setup, so going to close this out, thank you!


web server 文件下发

local function read_file( path )
local filename = www .. path
local file = io.open(filename, 'rb')
if file then
local value = file:read('*all')
io.close(file)
res_header["Content-Type"] = mimetypes.guess(filename or '')
return value, header
end
end
https://github.com/hyd998877/skynet_webserver.git
在web server上添加了个文件处理，作为web服务器，如果同时下发几个100k文件，速度非常慢，这是什么原回呢，@云风，是否可以解决下

有没有分析数据看卡在哪里？
ps. 你用 filename = www ..  path 有安全问题。攻击者在 path 里加几个 .. 你就完蛋了。

我分析了下，是不是在send_socket这儿，
发送文件，第一次s->high.head == NULL && s->low.head == NULL的时候
write不能一次写完，则进入了send_list的逻辑
这时socket线程只有一个，又同时并发多个文件，一个文件在多次调用send_list的时候，造成了抢占
不知道是不是这个原因，如果有空，可以使用https://github.com/hyd998877/skynet_webserver.git这个例子测试一下
恢常感谢指出的安全问题

使用ab作并发测试，并未发现skynet写的webserver与nginx本身有特别大的差别。

有没有实际数据证明问题在上面？
才几个 100K  文件，IO 量这么小，不会在底层 IO 处理上有问题。

单机测试时，有较为明显的差距
以下为skynet webserver:
Server Software:
Server Hostname:        <IP_ADDRESS>
Server Port:            9080
Document Path:          /b_about.png
Document Length:        694194 bytes
Concurrency Level:      20
Time taken for tests:   0.973 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      694262000 bytes
HTML transferred:       694194000 bytes
Requests per second:    1028.11 [#/sec] (mean)
Time per request:       19.453 [ms] (mean)
Time per request:       0.973 [ms] (mean, across all concurrent requests)
Transfer rate:          697048.95 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:     5   19   5.6     19      42
Waiting:        2   17   5.0     17      40
Total:          6   19   5.6     19      43
Percentage of the requests served within a certain time (ms)
50%     19
66%     21
75%     22
80%     23
90%     27
95%     30
98%     34
99%     36
100%     43 (longest request)
以下为nginx
Server Software:        nginx/1.4.6
Server Hostname:        <IP_ADDRESS>
Server Port:            9080
Document Path:          /b_about.png
Document Length:        694194 bytes
Concurrency Level:      20
Time taken for tests:   0.094 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      694440000 bytes
HTML transferred:       694194000 bytes
Requests per second:    10673.50 [#/sec] (mean)
Time per request:       1.874 [ms] (mean)
Time per request:       0.094 [ms] (mean, across all concurrent requests)
Transfer rate:          7238382.56 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:     1    2   0.8      2       7
Waiting:        0    0   0.4      0       4
Total:          1    2   0.8      2       7
Percentage of the requests served within a certain time (ms)
50%      2
66%      2
75%      2
80%      2
90%      2
95%      3
98%      6
99%      6
100%      7 (longest request)

10倍不是差距么？？
2016-06-22 18:04 GMT+08:00 zxfishhack<EMAIL_ADDRESS>
单机测试时，有较为明显的差距
以下为skynet webserver:
Server Software:
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.973 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694262000 bytes
HTML transferred: 694194000 bytes
Requests per second: 1028.11 #/sec http://mean
Time per request: 19.453 ms http://mean
Time per request: 0.973 ms
http://mean, across all concurrent requests
Transfer rate: 697048.95 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 5 19 5.6 19 42
Waiting: 2 17 5.0 17 40
Total: 6 19 5.6 19 43
Percentage of the requests served within a certain time (ms)
50% 19
66% 21
75% 22
80% 23
90% 27
95% 30
98% 34
99% 36
100% 43 (longest request)
以下为nginx
Server Software: nginx/1.4.6
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.094 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694440000 bytes
HTML transferred: 694194000 bytes
Requests per second: 10673.50 #/sec http://mean
Time per request: 1.874 ms http://mean
Time per request: 0.094 ms
http://mean, across all concurrent requests
Transfer rate: 7238382.56 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 1 2 0.8 2 7
Waiting: 0 0 0.4 0 4
Total: 1 2 0.8 2 7
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 2
95% 3
98% 6
99% 6
100% 7 (longest request)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudwu/skynet/issues/522#issuecomment-227699445, or mute
the thread
https://github.com/notifications/unsubscribe/ABXoJm9w6OtCXaN3GafCW4MaDjXicqJ8ks5qOQisgaJpZM4I7YrM
.

你不能这么算 nginx  用的是aio 处理静态文件 你用的是 lua 自带IO系统 不慢才怪
2016-06-22 18:52 GMT+08:00 哈蟆<EMAIL_ADDRESS>
10倍不是差距么？？
2016-06-22 18:04 GMT+08:00 zxfishhack<EMAIL_ADDRESS>
单机测试时，有较为明显的差距
以下为skynet webserver:
Server Software:
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.973 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694262000 bytes
HTML transferred: 694194000 bytes
Requests per second: 1028.11 #/sec http://mean
Time per request: 19.453 ms http://mean
Time per request: 0.973 ms
http://mean, across all concurrent requests
Transfer rate: 697048.95 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 5 19 5.6 19 42
Waiting: 2 17 5.0 17 40
Total: 6 19 5.6 19 43
Percentage of the requests served within a certain time (ms)
50% 19
66% 21
75% 22
80% 23
90% 27
95% 30
98% 34
99% 36
100% 43 (longest request)
以下为nginx
Server Software: nginx/1.4.6
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.094 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694440000 bytes
HTML transferred: 694194000 bytes
Requests per second: 10673.50 #/sec http://mean
Time per request: 1.874 ms http://mean
Time per request: 0.094 ms
http://mean, across all concurrent requests
Transfer rate: 7238382.56 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 1 2 0.8 2 7
Waiting: 0 0 0.4 0 4
Total: 1 2 0.8 2 7
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 2
95% 3
98% 6
99% 6
100% 7 (longest request)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudwu/skynet/issues/522#issuecomment-227699445,
or mute the thread
https://github.com/notifications/unsubscribe/ABXoJm9w6OtCXaN3GafCW4MaDjXicqJ8ks5qOQisgaJpZM4I7YrM
.

你应该把相同文件的请求缓存住(只要文件时间戳没有发生变化) 你这样同时对一个文件多次请求导致多次读取 如果不慢就没天理了
2016-06-22 18:54 GMT+08:00 哈蟆<EMAIL_ADDRESS>
你不能这么算 nginx  用的是aio 处理静态文件 你用的是 lua 自带IO系统 不慢才怪
2016-06-22 18:52 GMT+08:00 哈蟆<EMAIL_ADDRESS>
10倍不是差距么？？
2016-06-22 18:04 GMT+08:00 zxfishhack<EMAIL_ADDRESS>
单机测试时，有较为明显的差距
以下为skynet webserver:
Server Software:
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.973 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694262000 bytes
HTML transferred: 694194000 bytes
Requests per second: 1028.11 #/sec http://mean
Time per request: 19.453 ms http://mean
Time per request: 0.973 ms
http://mean, across all concurrent requests
Transfer rate: 697048.95 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 5 19 5.6 19 42
Waiting: 2 17 5.0 17 40
Total: 6 19 5.6 19 43
Percentage of the requests served within a certain time (ms)
50% 19
66% 21
75% 22
80% 23
90% 27
95% 30
98% 34
99% 36
100% 43 (longest request)
以下为nginx
Server Software: nginx/1.4.6
Server Hostname: <IP_ADDRESS>
Server Port: 9080
Document Path: /b_about.png
Document Length: 694194 bytes
Concurrency Level: 20
Time taken for tests: 0.094 seconds
Complete requests: 1000
Failed requests: 0
Total transferred: 694440000 bytes
HTML transferred: 694194000 bytes
Requests per second: 10673.50 #/sec http://mean
Time per request: 1.874 ms http://mean
Time per request: 0.094 ms
http://mean, across all concurrent requests
Transfer rate: 7238382.56 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.1 0 1
Processing: 1 2 0.8 2 7
Waiting: 0 0 0.4 0 4
Total: 1 2 0.8 2 7
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 2
95% 3
98% 6
99% 6
100% 7 (longest request)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudwu/skynet/issues/522#issuecomment-227699445,
or mute the thread
https://github.com/notifications/unsubscribe/ABXoJm9w6OtCXaN3GafCW4MaDjXicqJ8ks5qOQisgaJpZM4I7YrM
.

此服务器的信息与node.js的基本网页文件服务器的性能差不多了
Server Software:        NodeJs(v4.2.6)
Server Hostname:        <IP_ADDRESS>
Server Port:            9080
Document Path:          /b_about.png
Document Length:        694194 bytes
Concurrency Level:      20
Time taken for tests:   0.944 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      694342000 bytes
HTML transferred:       694194000 bytes
Requests per second:    1059.49 [#/sec] (mean)
Time per request:       18.877 [ms] (mean)
Time per request:       0.944 [ms] (mean, across all concurrent requests)
Transfer rate:          718409.19 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:     7   19   2.7     18      43
Waiting:        7   18   2.7     18      43
Total:          8   19   2.8     18      43
Percentage of the requests served within a certain time (ms)
50%     18
66%     19
75%     20
80%     20
90%     22
95%     23
98%     26
99%     29
100%     43 (longest request)
正如firedtoad所言，要提高性能，需要增加缓存策略和aio读取。

如果是细微的优化很有很多可以做的。不过我觉得不在极端需求下意义不大。
除了 cache 住文件，skynet 层面可以不用 socket.write 去写字符串（那样会多拷贝一次内存，从 lua 到 skynet socket 层）；你可以把文件读到一个 C buffer 里，然后用 socket.write 写 lightuserdata + len （这样可以减少一次内存拷贝）。
这个 C buffer 由 malloc 分配即可，skynet socket 层会调用 free 。
更极端的优化可以自定义 buffer 的分配释放，用引用计数来管理 buffer 。这样把同一个文件发到多个 socket 可以更快（减少更多的内存拷贝）。这个技术有个用 skynet 做视频广播的同学用过。方法是使用 socket_server_userobject https://github.com/cloudwu/skynet/blob/master/skynet-src/socket_server.h#L64 这个 C API 。


italicize block quotes in descriptions

these files have markdown block quotes (>>) but I guess they don't render for some reason? is it because they just go into a table? Any thoughts on how to fix?

for example see: https://elotroalex.github.io/litai/litai/i02/
We were imagining Poe's quote at the end would be italicized


rename-service-fabric to scalecube

MICROSERVICES
ScaleCube provides a low latency Reactive Microservices library peer-to-peer service registry and discovery based on gossip protocol no single point-of-failure or bottlenecks.
CLUSTER
Cluster provides a fault-tolerant decentralized peer-to-peer based cluster membership service with no single point of failure or single point of bottleneck. It does this using gossip protocol and an scalable and efficient failure detection algorithm.
TRANSPORT
The Transport module is communication layer of nodes and service. its main goal is to deal with managing message exchange
http://scalecube.io/
http://scalecube.io/services.html

Seems that are some conflicts that prevent automatic merge of your pull request.
If you don't mind I can add the modifications manually. Just tell me, thank you!

sure i dont mind


fix: event record scheme error

Please answer these questions before submitting a pull request

Why submit this pull request?

[x] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

Bugfix

Description
#468

Backport patches

Why need to backport?

Source branch

Related commits and pull requests

Target branch

Codecov Report

Merging #469 (46b2fb7) into master (0bdd24b) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #469      +/-   ##
==========================================
- Coverage   37.04%   37.02%   -0.03%
==========================================
  Files          47       46       -1
  Lines        3841     3841
==========================================
- Hits         1423     1422       -1
- Misses       2233     2234       +1
  Partials      185      185

Impacted Files
Coverage Δ

pkg/ingress/controller.go
0.00% <0.00%> (ø)

test/e2e/e2e.go

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 0bdd24b...46b2fb7. Read the comment docs.


Mock $httpBackend.flush() method never return/exit if custom $exceptionHandler use $http

If a module customize $exceptionHandler like this:
angular.module("myModule", [])
    .factory("$exceptionHandler", ["$http", function ($http) {
        return function (exception, cause) {
            $http.post("myserver/logger/service", exception);
        };
    }]);

With a generic controller's unit test like this:
it('Should call my service', inject(function($httpBackend, $controller) {
    $httpBackend.expectGET('myserver/resources/myresource');
    var ctrl = $controller('mycontroller');

    $httpBackend.flush();

    // ISSUE: code never called if $exceptionHandler POST isn't mocked

    expect(ctrl.someProperty).toBe('somevalue');

}));

The test excecution enter the flush method and never exit causing the browser to halt on a javascript function and Karma stop responding (I need to kill the process!)
If I mock the $http.post("myserver/logger/service", exception) then work as expected.
The main problem is that the code halt on flush method without any visible exception or error, and since logger and exception handling are aspect not focused on controller testing to find out the fail reason is very hard.

Recently I met the very same problem!
For me the error happened when the $httpBackend throws a synchronous error. For example, when the xhr.open call throws (because of a malformed url, or adblock intercepting the call on firefox), the generated exception cannot be caught and will propagate to the $exceptionHandler.
If the $exceptionHandler issues another $http call which will also cause the $httpBackend to fail while flushing, then it will cycle forever.
So, I think your example hangs because the $httpBackend throws a synchronous error, and the $exceptionHandler then tries to start a new $http request, causing a cycle.
I think the main problem is that, it cannot be caught if the $httpBackend throws, and will propagate to the $exceptionHandler every time. Wrapping the $http call in try-catch has no effect, because the flush gets called later. Maybe the $httpBackend should catch the errors itself and trigger some kind of rejection instead.

I just ran into this same issue using Angular 1.2.28


Add extra spacing between multi level sidebar headings

Fixes https://github.com/hydephp/hydefront/issues/45

A live preview is being deployed!Please note that it may take a few seconds for GitHub Pages to build and deploy. The preview will be removed in a few days.


chore: Add sample deployments to examples

To begin using the rails-app-operator, it's good to start with the basics and deploy a small website. This will help you understand how the rails operator works.
I propose to add instructions to learn how it could be verified.

I'll leave this open for today in case you want to make any tweaks. Otherwise, I'll merge it tomorrow.

Otherwise, I'll merge it tomorrow.

Apparently when I said "tomorrow", I meant "7 months from now" 🙃


Move Pageboy to correct category

Pageboy was incorrectly in the Activity Indicator section instead of general UI
Project URL
https://github.com/MerrickSapsford/Pageboy
Description
Move Pageboy to general UI
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

:no_entry_sign:
Found 1 link issue

Link issue by awesome_bot

Line
Status
Link

2447
503
http://www.teehanlax.com/tools/iphone/

  Generated by :no_entry_sign: Danger

@MerrickSapsford Thank you for contributing to awesome-ios🙌🏻


Separate report between assets and underwriting

From Vicky Morley,
It would be useful to separate in the report between categories of assets and underwriting / product (e.g. savings and liabilities).
From Rothesay,
It might make sense to split the sector filter into asset and liability side of the balance sheet.

If firm type is insurance then add extra level of headings and split assets and liabilities

implemented (in the separate branch, not pushed, waiting for merge of refactor pull request)


GD-268: C# - Add AssertDictionary to verify Godot.Collections.Dictionary

A Task is not a bug or feature request
Description
Add assert to verify Godot.Collections.Dictionary and c# Map objects
Acceptance criteria

AssertDictionary(IDictionary)
AssertThat(<Godot.Collections.Dictionary>) must use AssertDictionary

https://github.com/MikeSchulze/gdUnit3Mono/pull/7


Fix hint pr comments

Change branches in add_anon_tree
Fix get_dist function
Add log_and_raise_error in _IItemDistance__find_updated_dist
Use itertools.product in __find_dist_between_files
Remove tempfile import from consts
Add IdCounter

And add IdCounter

Thanks a lot :)


Unexpected error on model_output_collect <- f.robyn()

Issue
When we try to execute the model, at the end of the first iteration we find the following error:

Apparently the issue is on the class of the data we are trying to run, because the error says "x is not a data.table or data.frame" but we are not sure about that.
Looking forward on reading your comments.
Environment
R 4.0.3

are you using the simulated data? have you changed any setting?

I'm running with my company data. I didn't any settings.
According to Facebook Office in Mexico, there is a new version of the code which we are testing at this moment.
It looks like the new code is running fine.


Glue for functions and closures

Maybe not relevant right now, but this new roc glue has an issue with generating types from my version of RocType.roc. It hits:
thread 'main' panicked at 'assertion failed: layout.has_varying_stack_size(&env.layout_cache.interner, arena)', crates/glue/src/types.rs:1531:13
Or if the debug_assert! is commented out, it hits:
thread 'main' panicked at 'called Option::unwrap()on aNone value', crates/glue/src/types.rs:1052:58

Please wait to merge this, tomorrow I'm going to check my commits to see if I didn't leave any temporary changes that I have forgotten, and then we're good to go!

I'm done reviewing my changes. There is still an issue with the gen_dev  tests on cargo test --locked --release --package test_gen --no-default-features --features gen-dev, I changed exposed_to_host.values to the new exposed_to_host.top_level_values and now 336 of the gen_dev tests fail.

Alright, all checks passed, this PR has my blessing :)


NoSuchMethodError for asserting two objects since 3.20.0 version

Describe the bug
Since 3.20.0 version there are an error when you are trying to assert two objects.

assertj core version: since org.assertj:assertj-core:3.20.0 and newer
java version: openjdk-17.0.2
os (if relevant): MacOS 12.2.1 (but probably not relevant)

Test case reproducing the bug
Try to assert
Obj1 = actualAddress;
Obj2 = expectedAddress;

SoftAssertions assertion = new SoftAssertions();
table.asMaps().forEach(map -> {
    if (isNotBlank(actualAddress.toString())) {
        String expectedAddress = map.get("address");
        assertion.assertThat(actualAddress)
                .as(String.format("invalid address for %s", actualAddress))
                .isEqualTo(convertedAddress)

Error:
java.lang.NoSuchMethodError: ‘org.assertj.core.api.ObjectAssert
org.assertj.core.api.SoftAssertions.assertThat(java.lang.Object)'

Hi @topsycreed, what version were you using before?
Could you enhance your example to make it reproducible?

Hey @scordio It's working for org.assertj:assertj-core:3.19.0, give me some time to get an example

@scordio we were able to fix that issue with migrating to a new version of the library 'org.assertj:assertj-core:3.23.1', thanks!

Cool, thanks for the feedback, @topsycreed!


Error

'gm' is not available on the command line

Run npm install gm within the bot's root directory.


boinc: add headless option

Description of changes
Added headless option and packages entry. Switches config flag --disable-manager and omits X/GUI related libs
Closes: #242314

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[x] Fits CONTRIBUTING.md.

Can the services.boinc.package option be set to boinc-headless? If so, I suggest adding this as an example for that option.

Yes it can, that's a good idea.
I'll fix the lib.optionalString and edit the services module when I get back to my machine


expand shortcut guide

Description of the new feature / enhancement
Power toys adds lots of new shortcuts that use the windows key.  Since powertoys should be able to know all the shortcuts it adds shouldn't the shortcut guide be able to display them?
Scenario when this would be used?
When you don't remember all the shortcuts for everything
Supporting information
No response

/dup #890


Getting "Invalid regular expression //" error while compiling

What version of Ajv are you using? Does the issue happen if you use the latest version?
Ajv version: 8.16.0
Ajv options object
    const ajv = new Ajv({ allErrors: true })

JSON Schema
    const schema: JSONSchemaType<jsonBodyType> = {
      "type": "object",
      "properties": {
        "description": {
          "type": "string",
          "pattern": /^{(\\"[a-zA-Z]+\\":\\"[a-zA-Z0-9/_,. &|$#*?\\n():%'!-]+\\")(,\\"[a-zA-Z]+\\":\\"[a-zA-Z0-9/_,. &|$#*?\\n():%'!-]+\\")*}$/.toString().slice(1, -1)
        },
      },
      "required": ["description"],
    }

Sample data
    {"description":"{\"en\":\"Unlock Samsung devices effortlessly with our FRP removal service. Bypass factory reset protection on the
    latest models and Android versions. Take back control of your device now!\\n\\nQuickly check if your device is supported\"}"}

Your code
    const validate = ajv.compile(schema);
    validate(data);

Validation result, data AFTER validation, error messages
    node_modules\ajv\dist\core.js (23:38) @ defaultRegExp ⨯ SyntaxError: Invalid regular expression: /^{(\\"[a-zA-Z]+\\":\\"[a-zA-Z0-
    9/_,. &|$#*?\\n():%'!-]+\\")(,\\"[a-zA-Z]+\\":\\"[a-zA-Z0-9/_,. &|$#*?\\n():%'!-]+\\")*}$/u: Lone quantifier brackets

What results did you expect?
I expected the regex to be valid and the data to match it like in the RegExr website

Are you going to resolve the issue?
I don't know yet, I hope the ajv team resolves it

Hi there, there is something wrong with your regex and it is quite complicated so debugging it is difficult. It also doesn't help that you are using a non standard way to construct the regex. Please follow the instructions here - https://ajv.js.org/json-schema.html#pattern.
Basically AJV will take the string passed to pattern and pass it into new RegExp(your_pattern_string, "u"). So try constructing your regex using new RegExp with the "u" second param. If you can get that to succeed, then your schema will work with the same string. If you have trouble figuring out what's wrong, try starting with a simpler regex and build up to what you need, bit by bit.


amplify pull & push always add "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true to aws-exports.js

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.17.6
Amplify CLI Version
7.6.4
What operating system are you using?
Mac
Amplify Categories
auth, function, api, hosting
Amplify Commands
pull, push
Describe the bug
When running amplify pull or amplify push, they always generate the   aws-exports.js containing "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true.
Even if we delete the aws-exports.js file, the freshly generated file will contain "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true.
It started happening after using amplify mock for the first time. However, amplify mock is not running when the push or pull is executed. (Also, amplify mock  is not reverting the content of  aws-exports.js when terminating, however, that's another glitch.)
Expected behavior
When running amplify pull or amplify push, they should generate the   aws-exports.js containing only the cloud-related config.
Reproduction steps

Run amplify mock
Terminate amplify mock
Run amplify push
Run amplify pull
Assert  "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true in aws-exports.js

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
Workaround: manually remove "aws_appsync_dangerously_connect_to_http_endpoint_for_testing": true from aws-exports.js before starting the app in dev or building the app locally (e.g. for Ionic app version)

Closing as duplicate of #9338


Fetch a specific batch size

Tensorflow works better when all the training batches are of the same size. While creating reader via make_batch_reader and converting the dataset to tensorflow dataset via make_petastorm_dataset, there is no way to specify the batch size. The batches retrieved via make_batch_reader is dependent on parquet rowgroups.
Is there a way to specify a batch size and only retrieve those number of records from S3 in one go?

Do you think rebatching technique described in #359 work in your case?

Ohh, it does. Thank you.


minDate weird behaviour

Hi there,
thanks for providing this very good looking calendar. Appreciated.
While using the code below, the UI allows selecting a date after the 5th Jan 2024, instead of 5 Dec 2023 as instructed.
Am I doing something wrong?
Cheers
<input id="calbox" class="w3-input" onenter="() => dt_cal.open();"  type="text">
<script id="cal_1" type="text/javascript">
    var dt_cal = MCDatepicker.create({
        el: '#calbox',
        minDate: new Date(2023, 12, 5)
    });
</script>

This behaviour is due to how JavaScript handles months, January starts as 0, so December is 11. This confused me when I started, just substrat 1 from your month number and all will be well.
https://www.w3schools.com/jsref/jsref_getmonth.asp

Definitely shows my lack of JS knowledge...
Cheers mate, appreciated.


Upgrade to go v1.13.1

Closed in favor of bumping to go 1.13.9 in this PR https://github.com/rancher/cli/pull/271


FR: support anti-aliasing

Is your feature request related to a problem? Please describe.
The current display (for me) is harder on the eyes. After expanding, I found the fonts are not aliased:

On the left is a windows-native emacs (R, ESS) console, on the right is the same emacs (R, ESS) using WSLg.
Describe the solution you'd like
I'd like to be able to configure/use antialiases fonts (or some mechanism to get the same effect).
Describe alternatives you've considered
None.

@r2evans try fontconfig. Most distros have this package include already.

This isn't a font anti-aliasing issue.
This is an issue with desktops that aren't scaled at 100%, and Wayland RDP is statically configured for 100%; you're witnessing RDP scaling from Windows.
See issue #3 and look for mentions of WESTON_RDP_DISABLE_HI_DPI_SCALING=true

Thanks @Diablo-D3, I think that makes sense. Windows apps (not wsl) in general still glitch frequently changing between hires and not-hires monitors, so it's not surprising that MS's implementation for WSLg is falling prey to the same issues.

By the way, you might want to also look for scaling options on https://github.com/microsoft/wslg/wiki/WSLg-Configuration-Options-for-Debugging

I'm facing this issue. All WSLg apps have antialiasing issues:

I tried to put the following to the .wslgconfig file:
[system-distro-env]
WESTON_RDP_HI_DPI_SCALING=true
WESTON_RDP_FRACTIONAL_HI_DPI_SCALING=true
;100 to 500
WESTON_RDP_DEBUG_DESKTOP_SCALING_FACTOR=200

But it didn't help at all, nothing changed.
My monitor scale is 200%.

@speller I'm having the same issue. I tried exactly what you have. My monitor scale is also 200% Did you ever get a fix?

@pjjanas Unfortunately, no updates. Luckily, that was a monitor that I'm working on rarely. I'm usually using a 4K monitor with a scale of 150% and everything looks good there. No idea why it is not a priority for devs. It's a constant pain in eyes to work with windows which have serious antialiasing issues.


Correcting the typo 'model' to 'magpie'

Ah, I missed that. Thanks!

I assume this is non-controversial, so I'm gonna merge it myself @kaplun


How to reproduce the same cell pattern around different indexes?

I asked the same question on stackoverflow, but it seems like it won't be answered.
I need some way of address the cell's neghbours depending their relative position. As I understand the order is not determined even in the safe variants of neighbor traversal.
Is there any way to have local coordinates in h3o?
The only relevant thing I found is the Direction enum, but it is used for other thing.
P.S. Feel free to remove the issue if it is a wrong place to ask this.

There is a set of functions for working with local coordinates, called LocalIJ. In C they are called cellToLocalIj and localIjToCell. In Rust I believe you need to use the LocalIJ type. These functions give you local I, J coordinates for some cell. (Note that the origin or anchor cell probably won't be at 0,0 in this coordinate space.) You can then apply a translation to those coordinates to draw your pattern.

Is there any good description of how to address specific cells? I found some here, but I can't make sense of it.

What is the origin and how it is different from the anchor?
Why there are only i and j, but no k?

For more context here is an example of what pattern I am talking about:

In Rust h3o I believe you need to use the LocalIJ type.

Yup that's right.
To get the LocalIJ coordinate of a given CellIndex, use to_local_ij and specify your anchor:
let local_ij = cell_index.to_local_ij(anchor);

To get a CellIndex from a LocalIJ coordinate, use a TryFrom:
let cell_index = CellIndex::try_from(local_ij);

How do I choose anchor?

What is the origin and how it is different from the anchor?

They are the same in this context, that's two different way to call the same thing.
In your SO question you said:

I want to encode a local cell pattern to draw it around a given index.

The origin/anchor in this case is the index you want to draw around.

Why there are only i and j, but no k?

The i of IJ is i - k and the j of IJ is j - k, that's why k doesn't appear in IJ compared to IJK.
As to why IJ is exposed insted of IJK, @isaacbrodsky would probably know better than me.

So, if I understand your use case correctly, the code you need could look like this:
fn transpose_pattern(src: CellIndex, dst: CellIndex, pattern: &[CellIndex]) -> Vec<CellIndex> {
    // Compute translation offset.
    let src_coord = src.to_local_ij(src).expect("src coord");
    let dst_coord = dst.to_local_ij(dst).expect("dst coord");
    let i_offset = dst_coord.i() - src_coord.i();
    let j_offset = dst_coord.j() - src_coord.j();

    // Transpose the pattern from src to dst.
    pattern
        .iter()
        .copied()
        .map(|cell| {
            // Compute the local IJ coordinate wrt original center cell.
            let src_ij = cell.to_local_ij(src).expect("local IJ");
            // Apply translation and re-anchor at destination center cell.
            let dst_ij = LocalIJ::new_unchecked(dst, src_ij.i() + i_offset, src_ij.j() + j_offset);
            // Convert back to cell index.
            CellIndex::try_from(dst_ij).expect("dst cell")
        })
        .collect::<Vec<_>>()
}

With:

src: the original index around which the pattern was drawn
dst: the new index around which you want to draw the pattern
pattern: the cells that compose your pattern

⚠ Note that those conversions between cells and IJ coordinate can fail when the cell index is too far away from the anchor/is on the other side of a pentagon.
So depending how large your pattern are/their location, this may not work.
⚠ Also, the LocalIJ::new_unchecked I use in this snippet is currently a non-publicly exposed method (you can still call it but it's not part of the public API yet). Currently you can only build a LocalIJ from a CellIndex (to avoid crafting invalid LocalIJ).
I do plan to have a public method for that, but I've postponed it until now since I didn't have a use case for it.
There is little work to do beforehand, but I can probably cobble up something this week 🙂 (meanwhile, you can use this hidden method).

Thank you for the snippet!
As I understand this can only move patterns until local coordinates are valid.  I am ok with the restriction on the size of the pattern. Is there a way to reconstruct the pattern in dst without restricting the distance between patterns?
For example, to remember LocalIJ  coordinates and reproduce them around the dst index.

is there a way to reconstruct the pattern in dst without restricting the distance between patterns?

The snippet does that, it's not limited by the distance between src and dst.
Pattern could be stored as a struct like that:
struct Pattern {
    anchor: CellIndex,
    pattern: Vec<(i32, i32)>,
}

Where the pattern field is a list of CoordIJ (maybe I should expose this type as well, meanwhile a tuple of i32 will do the trick), one for each cell.
Then you could have an API like that:
impl Pattern {
    pub fn new(anchor: CellIndex, pattern: &[CellIndex]) -> Self {
        Self {
            anchor,
            pattern: pattern
                .iter()
                .map(|&cell| {
                    let coord = cell.to_local_ij(anchor).expect("local IJ");
                    (coord.i(), coord.j())
                })
                .collect(),
        }
    }

    pub fn draw(&self, anchor: CellIndex) -> Vec<CellIndex> {
        // Compute translation offset.
        let src_coord = self.anchor.to_local_ij(self.anchor).expect("src coord");
        let dst_coord = anchor.to_local_ij(anchor).expect("dst coord");
        let i_offset = dst_coord.i() - src_coord.i();
        let j_offset = dst_coord.j() - src_coord.j();

        self.pattern
            .iter()
            .copied()
            .map(|coord| {
                let dst_coord =
                    LocalIJ::new_unchecked(anchor, coord.0 + i_offset, coord.1 + j_offset);
                // Convert back to cell index.
                CellIndex::try_from(dst_coord).expect("dst cell")
            })
            .collect::<Vec<_>>()
    }
}

The new encode/remember the pattern in coordinates.
The draw project them around the new anchor/destination.

It works!!! Thank you so much


Cannot sign/notarize macOS arm64 builds

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:

6.0.0-beta.54

Electron Version:

11.0.3

Operating System:

macOS 11.0.1

Last Known Working Electron Forge version::

None

Expected Behavior

Building for macOS with --arch=arm64 should allow signing and notarizing.
Actual Behavior

I am able to build with --arch=arm64, but I do not seem to be able to sign and notarize the arm version.
To Reproduce

Additional Information
<!--
Add any other context about the problem here.

For example:
* Console output when you run your `electron-forge` command with the environment variable
  `DEBUG=electron-forge:*`. (Instructions on how to do so
  [here](https://www.npmjs.com/package/debug#usage)). Please include the stack trace if
  one exists.
* Command line arguments you are passing to `electron-forge` (e.g.,
  `electron-forge make --not-a-real-flag`)
* The `config.forge` data in `package.json` or `forge.config.js` in use
* A failing minimal testcase (with a link to the code) or detailed steps to reproduce the problem.
  Using `electron-forge init` is a good starting point, if that is not the source of your problem.

I do not seem to be able to sign and notarize the arm version.

It would help to know what error messages you're getting.
I'm not convinced this is a problem with Electron Forge itself. Probably a bug in electron-osx-sign. Can you paste the (redacted) output when you pull down this branch of electron-quick-start, edit packager.js with your appropriate osxSign and osxNotarize options, then run:
npm install
npm run package:macos

@malept I get a successful verified and signed, the issue seems to be notarization:
Electron Packager failed to run:

Failed to upload app to Apple's notarization servers

2020-12-04 14:28:00.190 altool[86493:2438502] CFURLRequestSetHTTPCookieStorageAcceptPolicy_block_invoke: no longer implemented and should not be called
2020-12-04 14:28:01.593 altool[86493:2438487] *** Error: Unable to notarize app.
2020-12-04 14:28:01.593 altool[86493:2438487] *** Error: code -1011 (Failed to authenticate for session: (
    "Error Domain=ITunesConnectionAuthenticationErrorDomain Code=-22938 \"Sign in with the app-specific password you generated. If you forgot the app-specific password or need to create a new one, go to appleid.apple.com\" UserInfo={NSLocalizedRecoverySuggestion=Sign in with the app-specific password you generated. If you forgot the app-specific password or need to create a new one, go to appleid.apple.com, NSLocalizedDescription=Sign in with the app-specific password you generated. If you forgot the app-specific password or need to create a new one, go to appleid.apple.com, NSLocalizedFailureReason=App Store operation failed.}"
) Unable to upload your app for notarization.)

Definitely not a problem with Forge itself, then. The error seems to indicate that you're not sending or using the correct password.

@malept I am though. It works for the x64 build and fails on the arm64 build using the same password. Do we need a new password per arch?

Do we need a new password per arch?

No idea.

I am though.

Forge itself doesn't have any code specific to notarization, so it's not a bug in Forge. It may be a bug in electron-notarize, but I'd be surprised if that were the case. Given what you're saying, it may just be some Apple app notarization guideline.

I created a new password and notarization worked. I guess they look at x64 and arm64 as two separate apps, each needing a password 🤷

@malept false alarm. The new password works on your test repo, but when I try to use it with my actual app, the build just hangs for 5 hours trying to notarize, and eventually fails, but I don't get any meaningful errors. Any ideas?

No, sorry.

Same issue here


Replace 'less' with 'fewer'

Proposed changes
Sorry for the pedantry, but I think "typo" is a count noun, so it reads better to use "fewer" instead of "less".

Thanks for making our docs better! Let's ship it 🚀