Do not silently use _spf.DOMAIN.EXT

Since f838afb94a23f47c79e9eea2cd3a45827b62e1b1, the gem prioritizes a query to _spf.DOMAIN.EXT instead of using a query to the requested domain itself. This produces invalid results in case a domain publishes SPF records on both _spf.DOMAIN.EXT as well as DOMAIN.EXT.
In general, the only valid SPF record for a domain is in the TXT record of the domain itself. Nowhere in the spec (as far as I'm aware) does it specify that the _spf.DOMAIN.EXT record should be used in preference (or is even valid without explicit rules) rather than the record of the domain itself. Per the RFC, if _spf.DOMAIN.EXT is to be used, it has to be referenced on the domain itself via e.g. an include or redirect rule.
Thus, the automatic check for _spf.#{domain} in SPF::Query.query should preferably be removed completely there since it produced incorrect results for some domain. It even contradicts the examples from the README.md for e.g. facebook.com.
If it is not possible to remove this check for any reason, it should at least be de-prioritized from the check of the passed domain itself and controlled via a flag.
I'd be happy to provide a pull request to remove or deprioritize this check for _spf.DOMAIN.EXT.

RFC7208 does in fact mention _spf and it is commonly used. It used to be that certain domains would only provide a _spf.DOMAIN SPF record. Now, domains such as google.com provide a top-level SPF record which includes _spf.google.com. I think this can be fixed by querying DOMAIN first, then falling back to _spf.google.com if no TXT record containing spf=v1 is found.

Could you point me to the exact location in RFC 7208 where they state to implicitly fallback to (or even to prefer) _spf.DOMAIN for queries?
From my understanding, the authors of RFC 7208 just use the (indeed common) _spf label throughout in various examples to show how you may include or redirect certain parts of the spec from central locations or how to use macros to build lookups. Section 4.8 specifically talks about macro expansion and the ability to generate legal hostnames containing the _spf label.
Instead, RFC 7208 specifically states that the SPF record has to be published at the exact owner name it belongs to.
Specifically in section 3:

Each SPF record is placed in the DNS tree at the owner name it
pertains to, not in a subdomain under the owner name.  This is
similar to how SRV records [RFC2782] are done.

and later more explicitly in section 4.1:

<domain> - the domain that provides the sought-after authorization
information; initially, the domain portion of the
"MAIL FROM" or "HELO" identity.

and section 4.4:

In accordance with how the records are published (see Section 3
above), a DNS query needs to be made for the <domain> name, querying
for type TXT only.

Nowhere (according to my understanding) does RFC 7208 or any of its predecessors such as RFC 4408) specify to implicitly add the _spf label to a domain query. As such, I still believe that it is entirely wrong to consider a fallback to _spf.DOMAIN, regardless of the fallback's priority.
With that being said, it is indeed quite common to publish some parts of a final SPF policy on a hostname like _spf.example.com. This (partial) policy must however be used in an redirect or include rule for the actual SPF record (except for the rare case that someone might actually want to send email from an address such as jane@_spf.example.com). Thus, for this policy to be used, you would usually publish an SPF policy such as
v=spf1 include:_spf.example.com ~all

as a TXT record on the example.com domain.
Again, if I'm wrong, I'm eager to revise my understanding of the RFCs here. I just have not found any mention of such an implicit fallback.
In the case of Planio (the organisation sponsoring my initial pull request in #11), we publish our own primary SPF policy at TXT plan.io. This policy is a superset of _spf.plan.io where we publish some hosts which are allowed to send mail for our main service.  On our main domain however, we allow additional services such as newsletter services which send mails on behalf of the plan.io domain. These newsletter services however are not relevant to our main service and will never send mail on behalf of our customer domains (hence are not included in _spf.plan.io).
With the current lookup rules in the spf-query gem, you would wrongly check TXT _spf.plan.io instead of TXT plan.io and thus would deny newsletter mails from the plan.io domain from being received.

I have the same experience @meineerde is describing with the domain pwc.com. Parsing _spf.pwc.com first misses the
includes on pwc.com, thus missing the important _spf.google.com.


Avoid fragmentation

Hello, i have same lib - https://github.com/anton-dutov/iata-rs
May collaborate on, to get one better lib?

Anton, thanks for your interest in my project. I took a look at what you are doing and maybe there are some philosophical differences in terms of objective? It appears your library is trying to interpret the data in the fields, while mine is just providing it to consumers unmodified. That's intentional, it turns out the data in the fields is anything but standard and interpreting it properly for all airlines worldwide was far out of scope from what I was trying to do -- my library intentionally leaves interpretation up to the API consumer.
Further, it appears your library attempts to serialize boarding pass data too -- given the only place this might be useful that I can think of is in the context of an airline itself (these records after all represent data stored in a passenger reservation system), I intentionally excluded serialization.
I've also noticed that my library seems to focus primarily on completeness, surfacing fields that I don't necessary know how to interpret, whereas you're focusing on interpretation.
I'm not sure how to true these up, other than to suggest maybe you utilizing my library to parse the BCBP data then have your library provide the field interpretations? Looking forward to your thoughts, and pardon the delay in getting back to you.

To be clear, I'm more than happy to collaborate in any way we decide makes sense.

FUY: Your impl(and tests) merged to my crate, some fields renamed to compatibility, documentation in progress, we planned two paradigm

Raw (Zero cost) mapping RawBcbp<'a> from &str based on your code
Complete structures to read/build BCBP data

@anton-dutov very cool, and serendipitous timing, I just re-wrote it to use Nom. Glad you're getting some use out of it :)

If there's anything I can do to make it easier for you to integrate feel free to let me know!

@martinmroz
Ops, now i dropped nom to avoid unnecessary deps, and switched to your idea with scanner =)
Main issue with integration, is different naming, i use my crate in most internal project, and follow some naming rules to keep short field names, by example
from_city_airport_code -> source(origin) airport -> src_airport
to_city_airport_code -> destination airport -> dst_airport
passenger -> pax
etc.
Why you not use parsing as view (my goal)?
struct BCBP<'a> {
name:  &'a str, // No alloc, slice of source &src[2 .. 22]
};
...
let bcbp_src = "M1ALBA/JESSIKA.....";
let bcbp = BCBP::from_str(&bcbp_src)?; // Structured view of bcbp_src
P/S
I think you were a little hurried with crate stabilisation

@anton-dutov haha, that's all fair. This is one of my personal project, I just have a general approach of packaging/releasing my personal project in case someone might find them of value.
Re: renaming fields, yah you're right, that's probably a bit more idiomatic, I was following the names set out in the BCBP reference document.
The new version I just released drops basically all unnecessary allocations and is effectively the same size as just using sub-string references. Using ArrayString<[u8;N]> should be the same size as keeping around the original input string plus the parsed sub-string references. True, I'll end up copying the data once but these blobs are just a few hundred bytes, which doesn't seem crazy.

I think you were a little hurried with crate stabilisation

How so! If there's something I could do differently let me know!


feat: logging v2

Issue #, if available: #965
Description of changes:

abstract logging module with slf4j
log4j implementation
logback implementation

Checklist

[x] Meet tenets criteria
[ ] Update tests
[ ] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist
Breaking change => v2
RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2@8586bf6). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##             v2    #1435   +/-   ##
=====================================
  Coverage      ?   84.70%
  Complexity    ?      507
=====================================
  Files         ?       59
  Lines         ?     1896
  Branches      ?      211
=====================================
  Hits          ?     1606
  Misses        ?      216
  Partials      ?       74

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

@scottgerring @msailes @mriccia it starts to have a good shape. It's quite well tested (unit and one e2e successfully migrated). I still need to test on Lambda and verify a few things, also want to see if we can improve more (removing dependencies). Already found a slf4j binding option to avoid service loader, will investigate more.
But, you can already start to look at it, as it's quite big...

Pushed to queue! I've asked for some initial feedback on #1402 before I continue on it also ;)

@jeromevdl looking today based on current state 💪


Invalid cross-device link OSError

Using Linux, having installed SillyTavern-Extras "vanilla" with a python virtual environment, and running silero-api-server through SillyTavern-Extras with the following command:
/path-to-the-python-venv/bin/python /path-to/SillyTavern-Extras/server.py --enable-modules=caption,summarize,classify,silero-tts,chromadb
with all requirements fulfilled, and the python venv on the same partition as SillyTavern-Extras, results in the following error message before a crash:

Traceback (most recent call last):
File "/path-to/SillyTavern-Extras/server.py", line 252, in
tts_service.generate_samples()
File /path-to-venv/lib/python3.11/site-packages/silero_api_server/tts.py", line 127, in generate_samples
os.rename(audio, f"{self.sample_path}/{name}")
OSError: [Errno 18] Invalid cross-device link: 'test.wav' -> '/path-to/SillyTavern-Extras/tts_samples/en_0.wav'

My attempt: replacing "os.rename" with "shutil.move" which failed, returning the error
"NameError: name 'shutil' is not defined" as I did not import shutil and am not sure how to do so, and if that would fix the issue anyway.
What can I do to fix this issue and make TTS work? Thank you.
Edit: It seems like the issue isn't with silero-api-server but with SillyTavern-Extras: Simply following the silero-api-server recommandations and doing python -m silero_api_server instead of passing through SillyTavernExtras, will work.

I had some raw windows pathing in there.  This should be fixed as of version 0.2.9


Array#any? is not equal to !Array#empty?

It seems that .any? method is hugely misused in ruby community. Taking into consideration that performance impact could be very big, It would be really useful to have some kind of performance lint for this purpose.

While we're on performance you know that !Array#empty? is slower than unless Array#empty? :wink:

The problem is that you can really distinguish a proper usage of something.any? from an improper one. Someone really might not care about nil elements in their collection...


fixed the breakpoint issue on tablets

Issue Title:
resolves issue: #130
Type of change ☑
What sort of change have you made:

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

Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

How Has This Been Tested? ⚙
tested using the responsive developer tool in firefox
Video of the fixed issue
https://github.com/singodiyashubham87/Draw-it-out/assets/32983571/67c97091-3e0c-4617-9289-b20f3e212550

@Stiffpixels Kindly resolve the conflicts.

@Stiffpixels Kindly resolve the conflicts.

done

@singodiyashubham87 please merge it

@Stiffpixels, I don't have privileges to Merge PR.
Please wait for some time, Admin (@singodiyashubham87) will Merge this once he's available.

@Stiffpixels Thanks for contributing, Keep up the spirit :)


Doesn't work with autofill

If something autofills a form, for instance: https://privacy.com/ filling a credit card field, the mask doesn't show until you click the field and hit a key. Small bug really. This library is awesome, using it on react.jobs now :D Thanks for all the work.

Thanks a lot @zackify!
I tested with LastPass and Chrome auto-fill and it seems to be formatting correctly. As long as React onChange event is triggered after the extension auto-fills the field, the input should be formatted. Privacy.com extension maybe for some reason not causing the onChange event to trigger?

I will try to debug this more. Just didn't have time today so I made the
issue. Will check if onChange is firing or not and I guess it would really
be the extension doing something weird.
On Wed, Aug 10, 2016 at 22:19 M.K. Safi<EMAIL_ADDRESS>wrote:

Thanks a lot @zackify https://github.com/zackify!
I tested with LastPass and Chrome auto-fill and it seems to be formatting
correctly. As long as React onChange event is triggered after the
extension auto-fills the field, the input should be formatted. Privacy.com
extension maybe for some reason not causing the onChange event to trigger?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/msafi/text-mask/issues/129#issuecomment-239058166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbacB2sdSngkkthAstp0xKpVKczsRR6ks5qeobCgaJpZM4JhQuc
.

@zackify Yeah, if the Privacy.com extension is grabbing the input element and setting value to it directly, it would cause this, and if that's the case I don't know what can be done on our side about it...
I'll close this issue for now but feel free to reopen.
Oh, and thank you guys for tweeting about this! 😄

No problem. It's a really awesome library!
On Wed, Aug 10, 2016 at 22:28 M.K. Safi<EMAIL_ADDRESS>wrote:

@zackify https://github.com/zackify Yeah, if the Privacy.com extension
is grabbing the input element and setting value to it directly, it would
cause this, and if that's the case I don't know what can be done on our
side about it...
I'll close this issue for now but feel free to reopen.
Oh, and thank you guys for tweeting about this! 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/msafi/text-mask/issues/129#issuecomment-239058904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbacCcIt33vDxE41Fvs9HYZMgJS1QLMks5qeoiwgaJpZM4JhQuc
.


distinctUntilChanged should set prev value with keySelector even at the first time

Description:
distinctUntilChanged should set prev value with keySelector even at the first time
Related issue (if exists):
https://github.com/ReactiveX/rxjs/issues/6012

Thank you, @preda7or!


add upload_results as a config option

Problem
What is the problem this work solves, including
closes #190
Solution
What I/we did to solve this problem

added a key `upload_results in the config file
check config file settings before calling post_and_open_file, to prevent excessive uploads to S3 as well as to avoid opening multiple browser tabs unnecessarily

the action takes place when:

If upload_results is present in config data, it uses whatever value is specified: this allows the user to disable the opening of tabs automatically if they wish.
Or
If upload_results is missing in config data, we check number_of_packings and only upload/post if it is less than 1.

with @mogres
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Steps to Verify:

Pack a local recipe with or without the "upload_results" option in the config file

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (b6fc051) 98.52% compared to head (89e9297) 98.52%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #191   +/-   ##
=======================================
  Coverage   98.52%   98.52%
=======================================
  Files          16       16
  Lines         476      476
=======================================
  Hits          469      469
  Misses          7        7

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


Update my_deployment.yaml

Fixese the issue we were working on

Fixese the issue we were working on

Thank you!


Table of contents for manual.md

Added TOC directly in SUMMARY.md, so the readers see the important sections in the sidebar.

Forgot that it should be done on master. Rolling back.

Forgot that it should be done on master. Rolling back.


workflowcheck not working

Expected Behavior
Workflowcheck should find the deadlock here. But it doesn't.
Non-deterministic is not found either. (I personally think this will not result in a non-deterministic error since historyMatch process does not match things not recorded in the command/event. And I think these sleep or print will not go into the command/event.

	// try some bad thing here
	logger.Debug("before sleep")
	// time.Sleep(1 * time.Microsecond)
	time.Sleep(2 * time.Second)
	now := time.Now()
	fmt.Printf("Now: %v\n", now)
	logger.Debug("after sleep")

Actual Behavior
when time is 1*ms, everything goes well. The flow is successfully completed.
when time is 1s, deadlock happens, and the flow failed.
But workflow checks don't show errors here.
Steps to Reproduce the Problem

Specifications

Version:
│   go.temporal.io/api v1.7.1-0.20220223032354-6e6fe738916a // indirect
│   go.temporal.io/sdk v1.14.0 // indirect
Platform: macos

Can you give the full code file and the full workflowcheck command you are running? We even have tests in workflowcheck that confirm things like time.Sleep and fmt.Printf are both non-deterministic.

https://github.com/gingercat-maki/temporal-demo

This works for me. You have to make sure that you check the package where you are calling RegisterWorkflow. This entrypoint is the only way that the static analyzer knows your function is a workflow and not just some other code (we can't just assume every function signature containing workflow.Context as the first parameter is a workflow).
When I run:
workflowcheck ./app/worker

I get:
tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function time.Sleep
  time.Sleep is non-deterministic, reason: declared non-deterministic
/tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function time.Now
  time.Now is non-deterministic, reason: declared non-deterministic
/tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function fmt.Printf
  fmt.Printf is non-deterministic, reason: accesses non-deterministic var os.Stdout
/tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function github.com/luci/go-render/render.Render
  github.com/luci/go-render/render.Render is non-deterministic, reason: calls non-deterministic function (*github.com/luci/go-render/render.traverseState).render
    (*github.com/luci/go-render/render.traverseState).render is non-deterministic, reason: calls non-deterministic function (reflect.Value).MapIndex
      (reflect.Value).MapIndex is non-deterministic, reason: calls non-deterministic function (reflect.Value).assignTo
        (reflect.Value).assignTo is non-deterministic, reason: calls non-deterministic function reflect.makeMethodValue
          reflect.makeMethodValue is non-deterministic, reason: calls non-deterministic function reflect.funcLayout
            reflect.funcLayout is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
              (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
                (*sync.Map).dirtyLocked is non-deterministic, reason: iterates over map
        (reflect.Value).assignTo is non-deterministic, reason: calls non-deterministic function reflect.valueInterface
          reflect.valueInterface is non-deterministic, reason: calls non-deterministic function reflect.makeMethodValue
            reflect.makeMethodValue is non-deterministic, reason: calls non-deterministic function reflect.funcLayout
    (*github.com/luci/go-render/render.traverseState).render is non-deterministic, reason: calls non-deterministic function github.com/luci/go-render/render.writeType
      github.com/luci/go-render/render.writeType is non-deterministic, reason: calls non-deterministic function reflect.SliceOf
        reflect.SliceOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
          (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
        reflect.SliceOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
          (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
      github.com/luci/go-render/render.writeType is non-deterministic, reason: calls non-deterministic function reflect.MapOf
        reflect.MapOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
          (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
        reflect.MapOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
          (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
        reflect.MapOf is non-deterministic, reason: calls non-deterministic function reflect.bucketOf
          reflect.bucketOf is non-deterministic, reason: calls non-deterministic function reflect.PointerTo
            reflect.PointerTo is non-deterministic, reason: calls non-deterministic function (*reflect.rtype).ptrTo
              (*reflect.rtype).ptrTo is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
                (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
              (*reflect.rtype).ptrTo is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
                (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
/tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function go.temporal.io/sdk/workflow.AwaitWithTimeout
  go.temporal.io/sdk/workflow.AwaitWithTimeout is non-deterministic, reason: calls non-deterministic function go.temporal.io/sdk/internal.AwaitWithTimeout
    go.temporal.io/sdk/internal.AwaitWithTimeout is non-deterministic, reason: calls non-deterministic function (*go.temporal.io/sdk/internal.coroutineState).yield
      (*go.temporal.io/sdk/internal.coroutineState).yield is non-deterministic, reason: sends to channel
      (*go.temporal.io/sdk/internal.coroutineState).yield is non-deterministic, reason: calls non-deterministic function (*go.temporal.io/sdk/internal.coroutineState).initialYield
        (*go.temporal.io/sdk/internal.coroutineState).initialYield is non-deterministic, reason: receives from channel
/tmp/workflowcheck-test/temporal-demo/app/worker/main.go:24:2: approval-workflow-demo-go.ExpenseApprovalWorkflow is non-deterministic, reason: calls non-deterministic function approval-workflow-demo-go.createSubmitSelector
  approval-workflow-demo-go.createSubmitSelector is non-deterministic, reason: calls non-deterministic function github.com/luci/go-render/render.Render
    github.com/luci/go-render/render.Render is non-deterministic, reason: calls non-deterministic function (*github.com/luci/go-render/render.traverseState).render
      (*github.com/luci/go-render/render.traverseState).render is non-deterministic, reason: calls non-deterministic function (reflect.Value).MapIndex
        (reflect.Value).MapIndex is non-deterministic, reason: calls non-deterministic function (reflect.Value).assignTo
          (reflect.Value).assignTo is non-deterministic, reason: calls non-deterministic function reflect.makeMethodValue
            reflect.makeMethodValue is non-deterministic, reason: calls non-deterministic function reflect.funcLayout
              reflect.funcLayout is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
                (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
                  (*sync.Map).dirtyLocked is non-deterministic, reason: iterates over map
          (reflect.Value).assignTo is non-deterministic, reason: calls non-deterministic function reflect.valueInterface
            reflect.valueInterface is non-deterministic, reason: calls non-deterministic function reflect.makeMethodValue
              reflect.makeMethodValue is non-deterministic, reason: calls non-deterministic function reflect.funcLayout
      (*github.com/luci/go-render/render.traverseState).render is non-deterministic, reason: calls non-deterministic function github.com/luci/go-render/render.writeType
        github.com/luci/go-render/render.writeType is non-deterministic, reason: calls non-deterministic function reflect.SliceOf
          reflect.SliceOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
            (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
          reflect.SliceOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
            (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
        github.com/luci/go-render/render.writeType is non-deterministic, reason: calls non-deterministic function reflect.MapOf
          reflect.MapOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
            (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
          reflect.MapOf is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
            (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
          reflect.MapOf is non-deterministic, reason: calls non-deterministic function reflect.bucketOf
            reflect.bucketOf is non-deterministic, reason: calls non-deterministic function reflect.PointerTo
              reflect.PointerTo is non-deterministic, reason: calls non-deterministic function (*reflect.rtype).ptrTo
                (*reflect.rtype).ptrTo is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
                  (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked
                (*reflect.rtype).ptrTo is non-deterministic, reason: calls non-deterministic function (*sync.Map).LoadOrStore
                  (*sync.Map).LoadOrStore is non-deterministic, reason: calls non-deterministic function (*sync.Map).dirtyLocked

I see. I just  workflowcheck workflow.go

Another question here is, the workers and workflows actually run to completion without errors, and why is that?

I personally don't think these print or sleep should cause non-deterministic errors. They are actually not in events and not seen by the workflow history.

Another question here is, the workers and workflows actually run to completion without errors, and why is that?

Because there are no errors during run I am guessing. We can't tell you use non-deterministic code at runtime, we can only check deadlocks.

I personally don't think these print or sleep should cause non-deterministic errors. They are actually not in events and not seen by the workflow history.

Maybe "non-deterministic" may not be the right phrasing, maybe "outside of the Temporal-controlled runtime". But it is very important for Temporal that nothing use Golang goroutines or the Go timing/sleeping system. Workflow code is expected to run until all coroutines are yielded in a couple of milliseconds. This is important to worker scaling and replaying. See https://docs.temporal.io/application-development-guide#workflow-logic-requirements.

Yeah, I know. I just read the source code of go-SDK and find the logic of temporal non-deterministic error which seems to be a different logic. But I think "outside of the Temporal-controlled runtime" really causes less confusion and really helpful.


NT_HYBRID Find mode

Experimental implementation of feature #392 as per https://github.com/ROCmSoftwarePlatform/MIOpen/issues/392#issuecomment-678797885, that is basically HYBRID mode that skips untuned Solvers.
Smoke tested on Radeon VII, ROCm 3.5. Shows performance/behavior as expected.
TODO:

rigorous testing

How to smoke test:

Clean user-find-db & run some config in NORMAL Find mode using the driver, collect logs at level 5.

The config should not be listed in the system find-db, for example: ./bin/MIOpenDriver conv -x 10 -y 5 -W 341 -H 79 -c 32 -n 3 -k 32 -p 0 -q 0 -u 2 -v 2 -l 1 -j 1 -g 1 -F 0 (note -n 3)

Clean user-find-db, run the same config in the HYBRID mode, collect log.
Run the same config in the same mode (do not clean find-db), collect log.
Clean user-find-db, run the same config in the new NT_HYBRID mode, collect log
Run the same config in the same mode (do not clean find-db), collect log.
Compare logs ;)

CI tests passed.

Wall time is better on unknown configs (~2.8 times less than normal Find and Hybrid, ~1.8 times better than FastHybrid), which is good.
The GPU performance of this is significantly worse, however. Some untuned Solvers actually have good performance with default configs, so those shoud not be disabled. Specifically, ConvOclBwdWrW2<1>, ConvBinWinogradRxSf2x3 and maybe more.
I am working on this.

After investigating logs, I've ended up enabling back untuned configs for

ConvOclBwdWrW2<1>
ConvAsm3x3U
ConvAsmBwdWrW1x1
ConvBinWinogradRxSf2x3

Now this mode has ~5% GPU perf drop but ~2.5X total wall time acceleration (BUILD_DEV=on). Topmost comment updated accordingly.
R is ready for review & merging. It is NFC provided that NT_HYBRID mode is not activated, so it should be safe to merge it.
However we need to test this with real frameworks and decide whether to keep it, fix it, or remove this now mode from the library.
/cc @daniellowell

-20%

Perf drop? Does that mean it got 20% faster, or slower?

Perf drop? Does that mean it got 20% faster, or slower?

Of course, slower. Fixed.

This is really good analysis. I think we need a phased approach. 5% is acceptable, but 20% is way too much, even for a fallback solution.

@daniellowell (originated from https://github.com/ROCmSoftwarePlatform/MIOpen/issues/410#issuecomment-685797615)

First get the PR merge that implements the reduced set of solvers so that we have the dynamic Find...

The design of this intermediate Dynamic Find does not match the design of NT_HYBRID, so I will prepare different PR with different DYNAMIC_HYBRID mode. This experimental PR is ready for testing, approval or rejection.


CT200 Raw Scan result Successfully connected to gateway. Found UUID: None

I'm hoping to add my Bosch CT200 Thermostat in Home Assistant.
As a first step I conducted to Raw Scan to verify if I can connect and retrieve the settings.
The Raw Scan executes and lists a successful connection to the gateway but the resulting JSON file does not contain any information outside of "not found" for all entry's.
To conduct the raw scan I followed the "Trace File of Communication with Bosch Device (Dev Raw Scan)" document.
I have build a fresh Docker container Ubuntu 22.04.
Next steps:

apt install software-properties-common
add-apt-repository ppa:deadsnakes/ppa
apt install python3.9 python3.9-venv
apt install python3-pip
Followed by:
cd ~
mkdir bosch
cd bosch
python3.9 -m venv venv
source venv/bin/activate
pip3 install wheel
pip3.9 install bosch-thermostat-client

Bosch CT200 Main Firmware version: 03.12.00
Bosch CT200 Hardware version: 10
To Reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Version

HA version? Not yet applicable
HA Bosch component version? CT200 firmware 03.12.00
Python Bosch HTTP client version? Latest version, installed today

** Debug SCAN **
** IMPORTANT **
Go to Developer tools in Home Assistant, choose Service tab and choose bosch.debug_scan
Download file to your computer and upload it somewhere eg. https://jsonblob.com/
Additional context
Result of "bosch_cli scan --host=101118168 --token=******** --password=******* --protocol=XMPP --device=EASYCONTROL"
(venv) root@eecc4ea70ec1:/bosch# bosch_cli scan --host=101118168 --token=***** --password=**** --protocol=XMPP --device=EASYCONTROL 2023-01-06 16:05:20 INFO (MainThread) [bosch_thermostat_client.connectors.xmpp] Msg exception for /gateway/uuid 2023-01-06 16:05:20 INFO (MainThread) [bosch_thermostat_client.connectors.xmpp] Msg exception for /system/interfaces 2023-01-06 16:05:20 INFO (MainThread) [bosch_thermostat_client.connectors.xmpp] Msg exception for /gateway/versionFirmware 2023-01-06 16:05:20 INFO (MainThread) [bosch_thermostat_client.connectors.xmpp] Msg exception for /gateway/productID 2023-01-06 16:05:20 INFO (MainThread) [bosch_thermostat_client.connectors.xmpp] Msg exception for /gateway/DateTime 2023-01-06 16:05:20 ERROR (MainThread) [bosch_thermostat_client.gateway.easycontrol] Couldn't find device model. Got product ID: None Traceback (most recent call last):   File "/bosch/venv/bin/bosch_cli", line 8, in <module>     sys.exit(cli())   File "/bosch/venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__     return self.main(*args, **kwargs)   File "/bosch/venv/lib/python3.9/site-packages/click/core.py", line 1055, in main     rv = self.invoke(ctx)   File "/bosch/venv/lib/python3.9/site-packages/click/core.py", line 1657, in invoke     return _process_result(sub_ctx.command.invoke(sub_ctx))   File "/bosch/venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke     return ctx.invoke(self.callback, **ctx.params)   File "/bosch/venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke     return __callback(*args, **kwargs)   File "/bosch/venv/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func     return f(get_current_context(), *args, **kwargs)   File "/bosch/venv/lib/python3.9/site-packages/bosch_thermostat_client/bosch_cli.py", line 86, in wrapper     return asyncio.run(f(*args, **kwargs))   File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run     return loop.run_until_complete(main)   File "/usr/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete     return future.result()   File "/bosch/venv/lib/python3.9/site-packages/bosch_thermostat_client/bosch_cli.py", line 241, in scan     connected = True if ignore_unknown else await gateway.check_connection()   File "/bosch/venv/lib/python3.9/site-packages/bosch_thermostat_client/gateway/base.py", line 323, in check_connection     await self.initialize()   File "/bosch/venv/lib/python3.9/site-packages/bosch_thermostat_client/gateway/base.py", line 92, in initialize     raise UnknownDevice("Your device is unknown %s" % json.dumps(self._device)) bosch_thermostat_client.exceptions.UnknownDevice: Your device is unknown null
On Screen Result of "bosch_cli scan -i --host=101118168 --token=******** --password=******* --protocol=XMPP --device=EASYCONTROL"
(venv) root@eecc4ea70ec1:/bosch# bosch_cli scan -i --host=101118168 --token=**** --password=***** --protocol=XMPP --device=EASYCONTROL 2023-01-06 16:13:31 INFO (MainThread) [bosch_thermostat_client.bosch_cli] Running scan 2023-01-06 16:13:31 INFO (MainThread) [bosch_thermostat_client.bosch_cli] Successfully connected to gateway.

Hi, got a similar issue with a CT200. I'm not so experienced with debugging, but I got this as a result. I know that my password is longer than the advised 8 characters, but from the error I can not see that would cause the issue.
2023-01-14 06:51:08.209 INFO (MainThread) [custom_components.bosch] Setting up Bosch component version 0.20.0.
2023-01-14 06:51:08.209 DEBUG (MainThread) [custom_components.bosch] Initializing Bosch integration.
2023-01-14 06:51:08.212 DEBUG (MainThread) [custom_components.bosch] Checking connection to Bosch gateway as 101427230.
2023-01-14 06:51:09.124 ERROR (MainThread) [bosch_thermostat_client.gateway.easycontrol] Couldn't find device model. Got product ID: None
2023-01-14 06:51:09.127 ERROR (MainThread) [custom_components.bosch] Your device is unknown null

Hi Edward,
I linked my Bosch thermostat with undermentioned guide. This works great.
https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/wiki/Home-Assistant-Installation-Guide
Marc

Hi Stijn, aha thanks for the URL. Just tested and the developer API works for me too!
So it might be related to the endpoint Pavel is using in his bosch_cli toolset. I'm going to put in some time tomorrow (Sunday) to see if changing the endpoint is changing it to work . . .

Changing the password from 20+ characters to only 8 did the trick after all. Everything is working now!

Changing the password from 20+ characters to only 8 did the trick after all. Everything is working now!

I wonder how you managed to do that? Using identity-myprofile.bosch.com requires a minimum length of 10 characters . . .

I did change it from the app on my phone. No specific restrictions encountered.
Verzonden vanuit Outlook voor iOShttps://aka.ms/o0ukef

Van: EdwardVoermans @.>
Verzonden: Monday, January 16, 2023 10:44:59 AM
Aan: bosch-thermostat/home-assistant-bosch-custom-component @.>
CC: StijnV @.>; Manual @.>
Onderwerp: Re: [bosch-thermostat/home-assistant-bosch-custom-component] CT200 Raw Scan result Successfully connected to gateway. Found UUID: None (Issue #251)
Changing the password from 20+ characters to only 8 did the trick after all. Everything is working now!
I wonder how you managed to do that? Using identity-myprofile.bosch.com requires a minimum length of 10 characters . . .
—
Reply to this email directly, view it on GitHubhttps://github.com/bosch-thermostat/home-assistant-bosch-custom-component/issues/251#issuecomment-1383764405, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJL3F6EC3IZWHHAOXSYXQ3WSUKBXANCNFSM6AAAAAATTFVSJA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I did change it from the app on my phone. No specific restrictions encountered.
Then I can only guess that Bosch changed their pwd policy overnight. Just tried the EasyControl app (v. 4.0.0) and getting the (new) requirements 0...9 AZ !$#% >10
I'm starting to feel like a dog chasing his own tail . . .

I use 4.0.0 already for one month and that was no issue. I’m running the app on iOS.
Verzonden vanuit Outlook voor iOShttps://aka.ms/o0ukef

Van: EdwardVoermans @.>
Verzonden: Monday, January 16, 2023 11:26:11 AM
Aan: bosch-thermostat/home-assistant-bosch-custom-component @.>
CC: StijnV @.>; Manual @.>
Onderwerp: Re: [bosch-thermostat/home-assistant-bosch-custom-component] CT200 Raw Scan result Successfully connected to gateway. Found UUID: None (Issue #251)
I did change it from the app on my phone. No specific restrictions encountered.
Then I can only guess that Bosch changed their pwd policy overnight. Just tried the EasyControl app (v. 4.0.0) and getting the (new) requirements 0...9 AZ !$#% >10
I'm starting to feel like a dog chasing his own tail . . .
—
Reply to this email directly, view it on GitHubhttps://github.com/bosch-thermostat/home-assistant-bosch-custom-component/issues/251#issuecomment-1383824303, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJL3F6WG7WMHMPISFYZLTTWSUO4HANCNFSM6AAAAAATTFVSJA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I use 4.0.0 already for one month and that was no issue. I’m running the app on iOS.
So am I. Is your Bosch account also already migrated to a SingleKey ID (https://www.bosch-digital.com/bosch-id/)?
My account is of the new type . . .


How to add and drop index into postgresql database

See e.g. https://github.com/vapor/fluent/issues/540#issuecomment-404547784 on how to either of these.


[Question]How to define async function in Go?

Is it possible to define an async function in Go that return Promise in JS ?

PromiseResolver can be used to create and resolve a promise in Go.

PromiseResolver can be used to create and resolve a promise in Go.

NewPromiseResolver(ctx) need ctx, and ctx created after v8.NewContext(iso, global), so ctx need global
NewPromiseResolver(ctx) called before global.Set(FuncName, GoFunc),  so global need ctx

that is a dilemma, I could not figure how to solve it.
Could you kindly give an example?

The documentation has an example that uses PromiseResolver: https://pkg.go.dev/rogchap.com/v8go#example-FunctionTemplate-Fetch

NewPromiseResolver(ctx) called before global.Set(FuncName, GoFunc)

I'm not sure why that is the case.  You don't need the promise resolver to define the async function, you just need it to create the promise to return from an async function such that it can be resolved from Go code.  As such, you would typically use NewPromiseResolver when that function that is exposed to JS is called, so that a different promise is returned each time.

Thanks so much! @dylanahsmith
info.Context() solve my problem.


chore: lint PR titles

should work after merging to main
https://stackoverflow.com/questions/76058442/pull-request-target-github-action-not-triggering


[skip ci] Adds document to fix #14

Fixes #14
@psyking841 Code review is appreciated.

@shawnzhu
Thanks for the heads up. The instruction for adding ssl connection looks good to me. I am currently using this and it works.


existing namespaces are reported as missing

Issue Type: Bug
I was working on an existing project when VSC suddenly reported more than 1k problems. All of them are related to missing namespaces and follow-up problems. The code however is perfectly fine, the namespaces are there and the application compiles and runs without any issues. Coding in VSC however, is impossible in this state.
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:46:01.075Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Extensions (4)

Extension
Author (truncated)
Version

unity-code-snippets
kle
1.3.0

csharp
ms-
1.24.4

powershell
ms-
2021.12.0

unity-debug
Uni
3.0.2

/needsMoreInfo
You should at least provide language and code sample that causes problem.
Is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

Hi there! It is a unity project in C#. Most of the "non-standard" namespaces (= everything but System.*  and UnityEngine.*) are affected. After some research and trial and error regeneration the project files in Unity did the trick.


Gwh apidocs 1606 ima i os android

IMA plugins for iOS and Android

Looks good, after you add the ios ima sdk link you can just merge it without more changes. (no other page should link to these IMA pages so should be ok to publish?)

Publishing the IMA files renamed to be excluded from build -- pending a technical fix so we can make them visible.


Im running the tensorflow version of your code, while i try to train dcan model i get this below error.

libcublas.so.9.0: cannot open shared object file: No such file or directory
Im running tf 1.12

You need to use correct cuda version for each version of the tensorflow / pytorch.

You need to use correct cuda version for each version of the tensorflow / pytorch.

Hello thankyou for the reply i changed my cuda toolkit to 9.0, but now im having a different error!
E:\NITK\DCAN\hover_net-tensorflow-final\src>python train.py --gpu='0'
[256, 256] [256, 256]
Traceback (most recent call last):
File "train.py", line 272, in
trainer.run()
File "train.py", line 252, in run
self.run_once(opt, sess_init=init_weights, save_dir=self.save_dir)
File "train.py", line 174, in run_once
train_datagen = self.get_datagen(opt['train_batch_size'], mode='train')
File "train.py", line 162, in get_datagen
nr_procs=nr_procs)
File "E:\NITK\DCAN\hover_net-tensorflow-final\src\loader\loader.py", line 73, in train_generator
ds = PrefetchDataZMQ(ds, nr_procs)
File "E:\Anaconda Nav\envs\hovernet_tf\lib\site-packages\tensorpack\dataflow\parallel.py", line 285, in init
super(PrefetchDataZMQ, self).init()
File "E:\Anaconda Nav\envs\hovernet_tf\lib\site-packages\tensorpack\dataflow\parallel.py", line 91, in init
assert os.name != 'nt', "ZMQ IPC doesn't support windows!"
AssertionError: ZMQ IPC doesn't support windows!

Hello thankyou for the reply i changed my cuda toolkit to 9.0, but now im having a different error!
E:\NITK\DCAN\hover_net-tensorflow-final\src>python train.py --gpu='0'
[256, 256] [256, 256]
Traceback (most recent call last):
File "train.py", line 272, in
trainer.run()
File "train.py", line 252, in run
self.run_once(opt, sess_init=init_weights, save_dir=self.save_dir)
File "train.py", line 174, in run_once
train_datagen = self.get_datagen(opt['train_batch_size'], mode='train')
File "train.py", line 162, in get_datagen
nr_procs=nr_procs)
File "E:\NITK\DCAN\hover_net-tensorflow-final\src\loader\loader.py", line 73, in train_generator
ds = PrefetchDataZMQ(ds, nr_procs)
File "E:\Anaconda Nav\envs\hovernet_tf\lib\site-packages\tensorpack\dataflow\parallel.py", line 285, in init
super(PrefetchDataZMQ, self).init()
File "E:\Anaconda Nav\envs\hovernet_tf\lib\site-packages\tensorpack\dataflow\parallel.py", line 91, in init
assert os.name != 'nt', "ZMQ IPC doesn't support windows!"
AssertionError: ZMQ IPC doesn't support windows!

Okay i got it thankyou! had to comment the line in loader.py

Okay i got it thankyou! had to comment the line in loader.py


Flickering in multiview video

Hello,
Thank you for your wonderful work. The problem is when I am trying to generate a video from novel views , I can see a lot of flickering. Is this behavior expected when generating the novel views. Can you please share your view on it?
Thank you

Hi, thanks for trying our codes.
The reason for causing the problem is two-fold.
First, 16 views are not enough to train a NeRF with stable renderings, especially for hash-grid-based NeRF. Using the MLP-based NeuS could relieve this problem due to its smoothness constraints in the MLP network.
Second, the generated views are not strictly multiview consistent and some inconsistency still remains. In this case, you may generate multiple times and select the one with the strongest multiview consistency to improve the quality.

Thank you for your answer. I am actually not doing 3D reconstruction but generating more than 16 views with varying azimuth and elevation. Though it is generating the object, but i can see the flickering between the frames. You can see in the attached video. Can we expect this to be happened if we generate more than 16 views or is it just a mistake from my side?

SyncDreamer is designed to generate 16 views of fixed viewpoints and cannot generate other views.


Replace warning message with info message.

Fix: #220

Codecov Report

Merging #221 (70b7418) into main (ee1e7c5) will decrease coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #221      +/-   ##
==========================================
- Coverage   92.15%   91.94%   -0.22%
==========================================
  Files          74       74
  Lines        2831     2831
  Branches      453      453
==========================================
- Hits         2609     2603       -6
- Misses        222      228       +6

Impacted Files
Coverage Δ

src/functions/function-command/create-function.ts
79.31% <100.00%> (ø)

src/util/platform.ts
88.23% <0.00%> (-11.77%)
:arrow_down:

src/cli/cmdCli.ts
50.00% <0.00%> (-4.29%)
:arrow_down:

src/util/watch.ts
93.33% <0.00%> (-3.34%)
:arrow_down:

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 ee1e7c5...70b7418. Read the comment docs.


Add Client.Timeout to allow limiting total exchange duration

This change allows limiting the duration of the complete dial, write, read cycle, as opposed to controlling them individually.

Can you make the changes as sketched above? Then this is ready to be merged.

Yes, I'll be updating the PR in the next day. Thanks for the feedback!

I've just pushed up a revised commit that integrates the suggested changes.


Complexity calculation has problems with my mod data, branch 20005

Data repo is here: https://github.com/UncleGus/OneLifeData7.git
I put a try/catch around this.reduceValueByTools(actor, target) in Complexity.js and had it console out the actor name and target name, to identify the transitions causing problems.
Bronze Chunk - from anvil
Bronze Chunks - 5
Bronze Chunk - just pulled
Bronze Chunks - 9
Bronze Chunk - from anvil
Bronze Chunks - 4
Bronze Chunk - from anvil
Bronze Chunks - 5
Bronze Chunk - just pulled
Bronze Chunks - 9
Bronze Chunk
Bronze Chunks - 9
Bronze Chunk - just pulled
Bronze Chunks - 9
Bronze Chunk - just pulled
Bronze Chunk - just pulled
Bronze Chunk
Bronze Chunks - 9
Bronze Chunk
Bronze Chunks - 8
Bronze Chunk
Bronze Chunks - 8
Bronze Chunk - just pulled
Bronze Chunks - 8
Bronze Chunk - just pulled
Bronze Chunks - 8
Bronze Chunk
Bronze Chunks - 9
Bronze Chunk
Bronze Chunks - 8
Bronze Chunk
Bronze Chunks - 8
Bronze Chunk - just pulled
Bronze Chunks - 8
Bronze Chunk - just pulled
Bronze Chunks - 9
Bronze Chunk
Bronze Chunks - 9
Bronze Chunk
Bronze Chunks - 9
Bronze Chunk - just pulled
Bronze Chunks - 8
Bronze Chunk
Bronze Chunks - 8
Crowned Captured Horse
Full Monolith
Bronze Chisel - just pulled
Bronze Pick
Bronze Chisel - just pulled
Blunt Bronze Pick
Bronze Pick
Empty Cistern - just built
Bronze Chisel
Blunt Bronze Pick
Copper Hammer - forged
Copper Hammer Head - forged
Copper Hammer - forged
Copper Hammer Head - forged
Copper Hammer - forged
Copper Hammer Head - forged
Copper Hammer - forged
Gold Ingot
Bronze Chisel - just pulled
Bronze Ax
Bronze Chisel - just pulled
Blunt Bronze Froe
Copper Chisel - forged,just pulled
Blunt Bronze Froe

And it's still running :P

There is probably a bug with how tools reduce complexity, they are reducing it too much.


HDDS-2301. Write path: Reduce read contention in rocksDB.

https://issues.apache.org/jira/browse/HDDS-2301
This change introduces 'mkdir -p' behaviour in these 2 OM Requests:

create directory and
create (file)

The idea is to avoid iteration of the key table when creating new files with a path. Without the patch,  during file create - checking the existence of each parent directory requires a slow DB iterator. With the patch, this check becomes a point lookup which can be accelerated by the bloom filters in RocksDB.
This patch is a work-in-progress and the following functionality is broken:

interoperability with S3
ACLs (setting correct ACLs for the parent directories created in the path)
rename

Soliciting early feedback.

I think you should write a design document discuss this before this patch is checked in. Thanks

Please do not commit this patch with out a proper design trade-off discussion. Thanks

First of all, the mkdir -p is does not match the object store semantics of Ozone.
there is no notion of a path, where sub-components exists. There is only one component from the API perspecitve.

Question : what happens when I list a bucket using listkeys? are these keys visible ?

@supratimdeka @anuengineer is this change superseded by #498?  If so, can this be closed?

https://github.com/apache/hadoop-ozone/pull/498 makes this change obsolete. closing this PR.


OAuth2Client server value gets truncated to just the base URL

I thought this would work (notice the value of "server"):
const client = new OAuth2Client({
  clientId: 'id',
  clientSecret: 'secret',
  server: 'https://api.schwabapi.com/v1/oauth',
});

export async function getAuthorizeUri() {
  return client.authorizationCode.getAuthorizeUri({
    redirectUri: schwabRedirectUri,
    scope: ['readonly'],
  });
}

But then getAuthorizeUri() returns https://api.schwabapi.com/authorize?client_id=id&response_type=code&redirect_uri=________&scope=readonly, where the URL is missing /v1/oauth.
It should instead return https://api.schwabapi.com/v1/oauth/authorize?client_id=id&response_type=code&redirect_uri=________&scope=readonly.
A workaround would be for me to prepend /v1/oauth to the values for authorizationEndpoint and tokenEndpoint, but it would be convenient to just leave them appended to "server".
Am I misunderstanding something?
Thanks!

To use https://api.schwabapi.com/v1/oauth/ as a base url and an authorize endpoint directly below it, use:
{
  server: 'https://api.schwabapi.com/v1/oauth/',
  authorizationEndpoint: 'authorize'
}

By default authorizationEndpoint is /authorize, and the standard rules for expanding relative urls are applied, like:
new URL(relative, base);

Ah, yes!
Makes sense!
I'm curious:
https://github.com/badgateway/oauth2-client?tab=readme-ov-file#usage has defaults with preceding slashes:
  tokenEndpoint: '/token',
  authorizationEndpoint: '/authorize',

Any thoughts on making those defaults not have preceding slashes and instructing in the docs that the "server" should end in a slash?
The Oauth2 flows I've seen are always at a path like /v1/oauth/..., and I wonder if that's the case for most other people too, in which case it seems like default endpoints would be more convenient without the preceding slash.
I'm no expert, so it's just food for thought.
In any case, your suggestion works for me, so I'm all set.
Thanks!

It's a fair point. Something to consider for a future BC break version. Also perhaps something that can be clarified in the docs.
I'm hoping more people will simply use the discovery document. Way better to just let the server tell the client where everything can be found!

Thanks for that issue/thread ! Microsoft (Azure) provides endpoints under https://login.microsoftonline.com/{tenand-id-kinda-uuid}/oauth2/v2.0/, and I couldn't figure why after setting server URI to https://login.microsoftonline.com/{tenand-id-kinda-uuid} and token endpoint to /oauth2/v2.0/token I constantly had a 404 error on https://login.microsoftonline.com/token
Looks like using the OIDC discovery endpoint works, but you still have to pay attention to the trailing/leading slashs
✅ This works well (trailing slash on server and no leading slash on  discoveryEndpoint)
server: https://login.microsoftonline.com/{tenant-id}/,
discoveryEndpoint: 'v2.0/.well-known/openid-configuration',

❎❗Does not work (because of the lack of trailing slash on server)
- server: https://login.microsoftonline.com/{tenant-id}/,
+ server: https://login.microsoftonline.com/{tenant-id},
discoveryEndpoint: 'v2.0/.well-known/openid-configuration',

❎❗Does not work (because of the leading slash on discoveryEndpoint)
server: https://login.microsoftonline.com/{tenant-id}/,
- discoveryEndpoint: 'v2.0/.well-known/openid-configuration',
+ discoveryEndpoint: '/v2.0/.well-known/openid-configuration',


OAC_DCMapper(DublinCoreMapper)

Fetcher dependency: None

Some general links to know:

Development contribution process
"CIC all tasks" list view
"CIC current sprint" status view

Specific to this mapper:

List of collections, by mapper type: https://registry.cdlib.org/?mapper_type=oac_dc
Endpoint: 543 published collections; endpoints are collection specific

Rikolti MVP project board cheat sheet:

Please @ CDL developers liberally, in the comments.
When picking up an "issue," please indicate:

a) Assignees: self assign;
b) Sprint: select the current sprint cycle;
c) Date started: indicate the start date -- see right side fields

CIC developers will likely need to create PRs (and possibly additional issues). When doing so, please also indicate the following:

a) Repository: Rikolti;
b) Milestone: "4 CIC work" (these details are required in order for them to surface in the Rikolti MVP project board); and
c) link the PR to the associated issue.

When requesting review, please:

a) include a comment & @ CDL developers; and
b) Date delivered: indicate the date delivered (field on the right)

Note: Please also see issues #358 and #359 & explore the possibility to combine these. This may or may not be possible.


Updating kubeadm docs with KDD info

Description

Fixes #963
I've pulled info from the KDD page and fit it in here, so we can represent how to bring up a kubeadm cluster with Calico using either etcd or KDD.
I also tried to make it fairly clear at the start that the cluster will need to have been initialized with --pod-network-cidr=<IP_ADDRESS>/16.
I did not pull over anything about policy only, or user supplied networking, but can if we feel it belongs here.
Todos

[ ] Tests
[x] Documentation
[ ] Release note

Release Note

None required

Thanks @caseydavenport and @emanic , I've addressed the feedback so far, let me know if we still need some tweaking.

@caseydavenport @emanic I've reworded the section about --pod-network-cidr and I think it's getting the point across better, but it might still need improvement, WDYT?

I would just ask if you could squash your commits, that would be great.

The build failure is a side-effect of htmlproofer not handling partially published releases - the doc references v2.6 github objects that don't exist yet. For now, this will require that a maintainer override the UTs and accept the PR.

I've trimmed out the about section and trimmed down the requirements section, and brought this up to date with master to resolve the conflicts, I think we're good for another round.


Join groups/communities

Closes #621

Screwed up the base branch here...

@lucaslcode: I'm sorry, the frontend here is a new low...

For now user membership in communities will be done in a background job (the task exists, triggering it is awaiting the bg PR). An idempotent job will just make it easier to guarantee we don't miss any edge cases (user move/created, community added/removed, community bounds changed, etc), since this inclusion is impossible to guarantee in the database (I believe).

do you need to add logic to the user changing their location which adds them to relevant communities?

Probably a good idea on top of the job.

If I change location, am I still in the previous community?

Yes, but you can leave the group manually.

If a new community is added where I am, am I added automatically?

Yes. Will be added by the background job.


Remove old "ide-configs"

We now have .editorconfig

.editorconfig does not support all the settings specific for Intellij, like preferred member order while reformatting (constructor/fields/methods) and other small tweaks, but it provides the basic criteria of acceptance.
-1 to removing it as such preferences are preferred when using IntelliJ

@gastaldi Are the ide-settings compatible with the .editorconfig ones?  Do they, used together, arrive at the correct result?
We need checkstyle validating the build, else this is all for naught. :)

Yes, Intellij generated the .editorconfig from the ide settings from this
XML, they are best if used together.
Em 20 de mar de 2017 22:23, "Andrew Lee Rubinger"<EMAIL_ADDRESS>escreveu:
@gastaldi https://github.com/gastaldi Are the ide-settings compatible
with the .editorconfig ones? Do they, used together, arrive at the correct
result?
We need checkstyle validating the build, else this is all for naught. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/redhat-kontinuity/catapult/issues/190#issuecomment-287948507,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADTdROy-9L330clHwul7x8q8pW7vAWHks5rnyalgaJpZM4Mh6yZ
.

Closing per @gastaldi comments


chore(deps): [release-1.3] bump @backstage/plugin-techdocs-backend to 1.10.13

https://issues.redhat.com/browse/RHIDP-4114
https://issues.redhat.com/browse/RHIDP-4115

/assign @nickboldt
for approval
/assign @JessicaJHee @04kash
for lgtm

we can't update without moving up to a higher backstage version


Tests fail on Windows laptop

Using the latest commit (https://github.com/camunda/camunda-bpm-process-test-coverage/commit/568dea90102837d451c891965d36379b9d94c46c) and import the project into Spring Tool Suite, the tests didn't run successfully.
The errors running the tests in the IDE (don't appear in maven build):
org.camunda.bpm.extension.process_test_coverage.rules.AggregatedCoverageTestRunStateTest$SecondNested
java.lang.AssertionError: Class coverage can only be calculated if all tests deploy the same BPMN resources. expected:<[ProcessDefinitionEntity[process-test-coverage:1:104], ProcessDefinitionEntity[super-process-test-coverage-single-branch:1:105]]> but was:<[ProcessDefinitionEntity[process-test-coverage:1:904], ProcessDefinitionEntity[super-process-test-coverage:1:905]]>

testPathAAndSuperPathA(org.camunda.bpm.extension.process_test_coverage.rules.AggregatedCoverageTestRunStateTest$SecondNested)
java.lang.NullPointerException
	at org.camunda.bpm.extension.process_test_coverage.model.MethodCoverage.addCoveredElement(MethodCoverage.java:63)
	at org.camunda.bpm.extension.process_test_coverage.model.ClassCoverage.addCoveredElement(ClassCoverage.java:31)
	at org.camunda.bpm.extension.process_test_coverage.junit.rules.DefaultCoverageTestRunState.addCoveredElement(DefaultCoverageTestRunState.java:57)
	at org.camunda.bpm.extension.process_test_coverage.listeners.FlowNodeHistoryEventHandler.handleEvent(FlowNodeHistoryEventHandler.java:52)
	at org.camunda.bpm.engine.impl.history.parser.HistoryExecutionListener.notify(HistoryExecutionListener.java:58)
...

mvn clean package results on my laptop to:
Results :

Failed tests:   org.camunda.bpm.extension.process_test_coverage.rules.AggregatedCoverageTestRunStateTest: No coverage information was found for target/process-test-coverage//aggregated_report/coverage/super-process-test-coverage-single-branch.html
  org.camunda.bpm.extension.process_test_coverage.rules.MultipleDeploymentsForClassTest: No coverage information was found for target/process-test-coverage//org.camunda.bpm.extension.process_test_coverage.rules.MultipleDeploymentsForClassTest/super-process-test-coverage-single-branch.html

Tests run: 46, Failures: 2, Errors: 0, Skipped: 1

The probels seems to be Windows-related, as the build pass on the CI (using Linux).
The maven issues depend on the regex created here: https://github.com/camunda/camunda-bpm-process-test-coverage/blob/master/test/src/test/java/org/camunda/bpm/extension/process_test_coverage/rules/AggregatedCoverageTestRunStateTest.java#L34
and evaluated here: https://github.com/camunda/camunda-bpm-process-test-coverage/blob/master/test/src/test/java/org/camunda/bpm/extension/process_test_coverage/rules/AggregatedCoverageTestRunStateTest.java#L91-L95
Maybe I will have a look into them later, but it would be nice if the authors could confirm that they use Linux computers. And if any voluteers could confirm my issues on either Mac or Windows laptops.

I found some hints.
I disabled the failing tests on my branch and run the build locally on my Windows laptop.
The percentage generation from this build contains a special character on windows:

With Notepad++ and special characters displayed:

When you use the prepackaged version (0.3.2), you will get only linefeeds and some other special character:

In HEX, the upper one is a0, and the lower one is c2 a0.

I setup a matrix build running on Windows too and it runs successfully. Any ideas?

Yeah, it could have been some file encoding problem (CP1252 vs. UTF-8 vs ....).
Thank you for clarifying this, @zambrovski
I will close the issue now.


Small edits to the paper; also trying out fast cholesky decomposition.

There was a mere conflict, so I moved ms.tex to ms_EA.tex.  I also saved a PDF of an older version of the paper for comparison to the new version.

Great. I fixed it and merged.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter pylontech for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.pylontech
   -

:thumbsup: No errors found
WARNINGS:

[ ] :eyes: [W522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

This issue has been replaced by new isse #5
This issue can be closed.
your
ioBroker Check and Service Bot


Add support to read avro messages encoded with Confluent's kafkaavroserializer

I have avro messages encoded with kafkaavroserializer. I am not able to read them to elasticsearch using kafka input plugin.
I did classpath the kafka avro decoder (the entire serializer jars along with its dependencies) too. But I got an error that said that the plugin was not found.
do you happen to know this error or issue? do you have any thoughts to overcome this issue?

@Kargreat  Have you tried using the avro codec described in the following link? https://github.com/logstash-plugins/logstash-codec-avro/blob/master/DEVELOPER.md
Also check out https://github.com/logstash-plugins/logstash-codec-avro/blob/master/lib/logstash/codecs/avro.rb#L13-L17 to see how the schema is communicated.

@joekiller: I did read those posts and tried using logstadh-codec-avro in my input plugin. But those are for codecs that use binary decoder.
Also I went through their gits too. But they are different as we need to enhance the consumer with a different class. That corresponds to ruby-Kafka of yours.
Please let me know if you have any clarifications or queries.

Okay I'll try to give this a more detailed look.
On Jul 8, 2015 1:10 PM, "Kargreat"<EMAIL_ADDRESS>wrote:

@joekiller https://github.com/joekiller: I did read those posts and
tried using logstadh-codec-avro in my input plugin. But those are for
codecs that use binary decoder.
Also I went through their gits too. But they are different as we need to
enhance the consumer with a different class. That corresponds to ruby-Kafka
of yours.
Please let me know if you have any clarifications or queries.
—
Reply to this email directly or view it on GitHub
https://github.com/logstash-plugins/logstash-input-kafka/issues/37#issuecomment-119666532
.

@Kargreat is this the serializer? https://github.com/confluentinc/schema-registry/blob/master/avro-serializer/src/main/java/io/confluent/kafka/serializers/KafkaAvroSerializer.java
This is not a regular Avro serialized message

@talevy: That is correct! That is the reason we need a consumer with a different decoder (the one for the KafkaAvroSerializer). The implementation can be found out: http://docs.confluent.io/1.0/schema-registry/docs/serializer-formatter.html & the KafkaAvroDecoder can be found at https://github.com/confluentinc/schema-registry/blob/master/avro-serializer/src/main/java/io/confluent/kafka/serializers/KafkaAvroDecoder.java.
@joekiller: the links i have pasted should give you further more information.

@Kargreat cool! that is what I thought. This is a special serialization format with a subset of the message being the contents in Avro. A new codec with this implementation is needed beyond what the existing avro-codec can support

@Tal: Will it be possible to enhance the codec to read values using the other decoder?

It is technically a separate serialization format, so would warrant a separate codec plugin.

If you have a customer deserializer, isn't that what the configuration / input/ kafka / decoder_class attribute is for?
When I set my decoder class to the Java class we use, I get an error that the class cannot be found, regardless of where I put the class, in the logstash main directory, or the logstash lib or bin directory.  I've also put the jar file that contains the class file in all of those locations.
Can you please tell me after I've defined that class, how to use it in the logstash environment?  What I'm trying to accomplish is to read avro data from kafka with a customized deserializer via logstash to elasticsearch.
Thanks for your help.

In addition to the config changes, you'd need to add it to the classpath and start LS with your custom serializer.
input {
decoder_class => "com.mycomp.etl.avro.schema.kafka.RawLog2KafkaSerializer"
...
}

Logstash environment:
CLASSPATH=$CLASSPATH:/path/to/serializer.jar
bin/logstash -f <config_path>

I'll add this information to the docs
@ilene-gorman since you posted this on https://discuss.elastic.co/t/provide-custom-kafka-message-decoder-to-logstash/1780/3 lets follow up there.

Finally RTFM'd this (http://docs.confluent.io/1.0/schema-registry/docs/serializer-formatter.html) and it seems pretty trivial to slip into jruby-kafka. I think I'll just pack Avro with the gem.

okay reading this more I think @talevy is correct that it just needs a codec. The input runs the raw message through the decoder prior to any mutations.
      @codec.decode("#{message_and_metadata.message}") do |event|
        decorate(event)
        if @decorate_events
          event['kafka'] = {'msg_size' => message_and_metadata.message.size,
                            'topic' => message_and_metadata.topic,
                            'consumer_group' => @group_id,
                            'partition' => message_and_metadata.partition,
                            'key' => message_and_metadata.key}
        end
        output_queue << event

The kafka plugin is just delivering raw binary by default via the decoder_class settings.
  # The serializer class for messages. The default decoder takes a byte[] and returns the same byte[]
  config :decoder_class, :validate => :string, :default => 'kafka.serializer.DefaultDecoder'

So if I make a codec that does the Kafka Avro Decoder, should be good to go.

hey everyone, here is a community plugin for the confluent serialization format: https://github.com/revpoint/logstash-codec-avro_schema_registry

That is so cool and thanks a lot!
Sent from my iPad

On Mar 17, 2016, at 10:33 PM, Tal Levy<EMAIL_ADDRESS>wrote:
hey everyone, here is a community plugin for the confluent serialization format: https://github.com/revpoint/logstash-codec-avro_schema_registry
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

The newest changes in the plugin broke https://github.com/revpoint/logstash-codec-avro_schema_registry with this error:
←[31mAn unexpected error occurred! {:error=>#<ArgumentError: negative length -290656 given>,
:backtrace=>["org/jruby/ext/stringio/StringIO.java:829:in read'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:106:in `read'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:93:in `read_bytes'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:99:in `read_string'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:299:in `read_data'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:384:in `read_record'",
"org/jruby/RubyArray.java:1613:in `each'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:382:in `read_record'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:310:in `read_data'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/avro-1.8.0/lib/avro/io.rb:275:in `read'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/local_gems/607c8166/logstash-codec-avro_schema_registry-0.9.0/lib/logstash/codecs/avro_schema_registry.rb:83:in `decode'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/logstash-input-kafka-3.0.0.beta7/lib/logstash/inputs/kafka.rb:160:in `thread_runner'",
"file:/C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/jruby/lib/jruby.jar!/jruby/java/java_ext/java.lang.rb:12:in `each'",
"C:/Users/jchoinski/Downloads/logstash-5.0.0-alpha2/logstash-5.0.0-alpha2/vendor/bundle/jruby/1.9/gems/logstash-input-kafka-3.0.0.beta7/lib/logstash/inputs/kafka.rb:159:in `thread_runner'"], :level=>:fatal}←[0m
How can I test what is being passed to the codec? That seems to be where it is breaking.
Thanks,
Juliusz

thanks for the update @juliuszc. Personally, I haven't tried this plugin recently, so I am not sure exactly as to the issue. I will try this out next week and see what's up

It turns out that the plugin was working fine and the two cooperate well together. I didn't realize that the default serializer was changed in the the new version and so I had to change from the string deserializer to the byte array deserializer. Sorry for the erroneous complaint.

@juliuszc thanks for the update and solution!

Hi I was wondering if this plugin will work for logstash-2.2
I build the gem and installed it. One thing I was wondering is this correct syntax?
codec => { avro_schema_registry => { endpoint => "/home/t/logstash-2.2.2/etc/Payment.avsc" } }

@stecino is something not working with that syntax?

@stecino and @talevy I thinks perhaps endpoint should be the URL to the schema registry service where the avro schema has been uploaded.
Ref: http://www.rubydoc.info/gems/logstash-codec-avro_schema_registry/0.9.0/LogStash/Codecs/AvroSchemaRegistry

Hi @talevy @ph and @ryananguiano, I wonder why does encoder isn't implement?, is there any technical issue about that?. My team really need encoder to sync from Kafka to HDFS, could you guide me how to implement that?
Thanks in advance

The easiest way is to write directly using the index API after decoding separately!
Sent from my iPhone

On Apr 20, 2017, at 10:55 AM, Vu Nguyen Duy<EMAIL_ADDRESS>wrote:
Hi @talevy @ph and @ryananguiano, I wonder why does encoder isn't implement?, is there any technical issue about that?. My team really need encoder to sync from Kafka to HDFS, could you guide me how to implement that?
Thanks in advance
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @Kargreat , sorry for my bad, I don't understand, could you please guide me in more detail?

@juliuszc the package has been updated for logstash 5

Any chance that the logstash-codec-avro_schema_registry will be also able to encode soon? Or do you know if somebody tried that already?

@tichomir that project is not maintained by the Elastic organization. It does not seem like the encode is implemented yet

@tichomir @CBR09, I have modified  revpoint's logstash-codec-avro_schema_registry to add a basic encoder:
https://github.com/revpoint/logstash-codec-avro_schema_registry/pull/4

Just updated the encode method. Still needs to be tested.
https://github.com/revpoint/logstash-codec-avro_schema_registry/pull/5

hey everyone, here is a community plugin for the confluent serialization format: https://github.com/revpoint/logstash-codec-avro_schema_registry

thanks a lot.
do you know how to install this plugin when we use docker and docker-compose?

hey everyone, here is a community plugin for the confluent serialization format: https://github.com/revpoint/logstash-codec-avro_schema_registry

thanks a lot. do you know how to install this plugin when we use docker and docker-compose?

Just run commands from plugin documentation in Dockerfile


fix(material/select): flicker if opened from inside a focus handler

Fixes that the select was closing and reopening if it's opened from inside a focus handler on click. Also avoids a bit of work in the open and close methods.
Fixes #28280.

Hi @crisbeto I’m the creator of #28280 . Thank you so much for the prompt action on fixing it.
May I ask when this change will be released?

It'll be in the patch release next week.


fixed_typo #13576

Summary
fixes #13576
This PR fixes the typo reported in #13576
Details and comments
All details can be found in the above linked issue

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.002%) to 88.949%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
1
92.98%

crates/accelerate/src/two_qubit_decompose.rs
1
92.13%

crates/accelerate/src/unitary_synthesis.rs
1
92.2%

crates/qasm2/src/parse.rs
12
97.15%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.002%

Covered Lines:
79425

Relevant Lines:
89293

💛  - Coveralls


Write-Host statements, file redirections in a finally block intermittently fail quietly on Windows

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
The problem isn't easy to reproduce, and I see it on Windows only - it may be specific to aborting a Read-Host call.
It may take several tries, suggesting some non-deterministic timing is at play, relating to when the finally block executes in relation to stopping the script.
Related: #19988
# Save to a file and run on *Windows*:
# Repeatedly run the following and press Ctrl-C when prompted.
# Then make sure that:
#   (a) 'Aborted.' prints
#   and (b) that file temp:/$PID.txt exists.

  Get-Date > temp:/$PID.txt
}

Expected behavior
Aborted. should print.
Running Get-Content temp:/$PID.txt afterwards should print the timestamp when Ctrl-C was pressed.
Actual behavior
Intermittently, Aborted. doesn't print.
More often, file temp:/$PID.txt isn't created.
The failure is always quiet.
Error details
No response
Environment data
PowerShell 7.4.0-preview.4 on Windows 11 22H2 (ARM64)

Visuals
No response

What if we replace Read-Host with another code?

I just run into this issue yesterday and spent some time narrowing down the cause because of the extra complexity resulting from nested try-catch-finally blocks and what not.
It appers that not only Write-Host and file redirections are affected, but any command might not be executed in the finally block:
$global:try = 'N'
$global:finally1 = 'N'
$global:finally2 = 'N'
try {
        $global:try = 'Y'
        Read-Host 'Press Ctrl-C now'
} finally {
        $global:finally1 = 'Y'
        Start-Sleep -Milliseconds 100
        $global:finally2 = 'Y'
}

Results of running this script and pressing Ctrl-C when requested:
> .\finally-vs-read-host.ps1
Press Ctrl-C now:
> "$try $finally1 $finally2"
Y Y N

I.e. if running the commands in the finally block following the aborted Read-Host takes some time, then even simple variable assignment might not be executed.
Interestingly, it appears that in case of nested try-finally blocks after a short time interval the outer finally block(s) are executed properly, e.g. running:
$global:try = 'N'
$global:finally1 = 'N'
$global:finally2 = 'N'
try {
        $global:try = 'Y'
        try { Read-Host 'Press Ctrl-C now' }
        finally { Start-Sleep -Milliseconds 100 }
} finally {
        $global:finally1 = 'Y'
        Start-Sleep -Milliseconds 100
        $global:finally2 = 'Y'
}

always (well, maybe not always, but 25 consecutive times) resulted in:
> "$try $finally1 $finally2"
Y Y Y

All the above with PowerShell 7.3.6 on Windows 10.0.19044.

I'd like to revisit that code snippet with the nested try-finally blocks from my previous post to demonstrate that the inner finally block is only partially executed, but despite this the outer one is executed properly, even with a longer delay.
$global:try = 'N'
$global:nested_finally1 = 'N'
$global:nested_finally2 = 'N'
$global:finally1 = 'N'
$global:finally2 = 'N'
try {
        $global:try = 'Y'
        try {
                Read-Host 'Press Ctrl-C now'
        } finally {
                $global:nested_finally1 = 'Y'
                Start-Sleep -Milliseconds 100
                $global:nested_finally2 = 'Y'
        }
} finally {
        $global:finally1 = 'Y'
        Start-Sleep -Seconds 1    # Longer delay
        $global:finally2 = 'Y'
}

The results:
> .\PS-finally-vs-read-host.ps1
Press Ctrl-C now:
> "$try $nested_finally1 $nested_finally2 $finally1 $finally2"
Y Y N Y Y

When I removed the 100ms sleep from the inner finally block, then the values of the variables were Y Y Y Y N, indicating that this time it's the other way around, i.e. after the inner finally block was fully executed the outer was executed only partially.
I find this behavior quite bizarre, TBH.  Anyway, I'll use this "nested try-finally block with a noop delay" trick as a workaround for the time being, because a hard coded 100ms delay after each Read-Host call hurts much less than the inconsistent state resulting from a partially executed cleanup.


AT+MQTTPUBRAW, The length of data that can be sent cannot exceed 1024

AT+MQTTPUBRAW=,<"topic">,,,
: length of MQTT message, max length is 1024 by default. Users can change the max length limitation by setting
MQTT_BUFFER_SIZE_BYTE in make menuconfig.
I set MQTT_BUFFER_SIZE_BYTE to 2048 in make menuconfig,  But
"
AT+MQTTPUBRAW=0,"/devices/my-device/state",1025,2,0
ERROR
"
, somebody know why ? thank you.

@radianceltd Hi, it looks like work well, please try to update esp-at.

It works now, thank you .


Adding QuadratureEigenstate

Context:
Adding the quadrature eigenstate
Description of the Change:
Adding triple, state and tests

I've noticed a bug:
q0 = QuadratureEigenstate([0], x=0, phi=0);
np.linalg.norm(q0.fock(100))
#  1.7818953913923246

it depends on hbar, so probably there's a missing or extra one

@ziofil regarding the hbar, if we remove the hbar^-1/4 from c then the fock amplitudes no longer depends on the value of hbar. Do you think that is the right solution?


set bytecheck crate root when using reexported derive macro

Fixes #343 depends on https://github.com/rkyv/bytecheck/pull/30
This reexports bytecheck and adds #[check_bytes(crate = "::rkyv::bytecheck")] to derived archive types, when #[archive_attr(derive(CheckBytes))] is used.
It does not work for #[archive(as = "Self")], then the user must add this manually. Edit: actually, you can just change your import to use rkyv::{CheckBytes, bytecheck}.  I still think it's convenient though?
There is some low potential for conflict for existing users, as it will add this attribute even for those not using the reexported macro, as there is no way (that I know of) to determine that exactly. I can't think of a normal situation where this would cause issues, but this is technically a breaking change. (if someone is deriving a type also called CheckBytes from a crate other than bytecheck, this will break their code)
bytecheck is removed as a dependency from rkyv_test, in order to test this (and it's no longer necessary to depend on it directly).

Having a way to default to rkyv's re-exported bytecheck is a good idea, but I think parsing the arguments to archive_attr(derive(...)) is a little too magical. Since bytecheck is already integrated so tightly with rkyv, I would prefer a separate attribute. That way, you know that exactly what you pass to archive_attr gets applied to the generated type.
Could we add a new argument to the archive attribute that does all of this at once? Something like #[archive(check_bytes)], which would add #[derive(::rkyv::bytecheck::CheckBytes)] #[check_bytes(crate = "::rkyv::bytecheck")]. I think that would have better ergonomics than what we have right now anyway. Compare:
// old
#[derive(Archive)]
#[archive_attr(derive(CheckBytes))]
struct Foo { ... }

to
// new
#[derive(Archive)]
#[archive(check_bytes)]
struct Foo { ... }

I think that's an ergonomics improvement even in the simplest case, and it would be a huge ergonomics improvement in more complex cases with custom paths and such.

That's a much better idea, thanks. I also added a commit to fix compatibility with bytecheck::Error's added Send + Sync bounds, so that the tests would compile.

I think we'll need to separate the bytecheck version bump into a separate PR. I'd like to do that upgrade when rkyv bumps to 0.8. Since the rest of these changes are semver-compatible with rkyv 0.7, we can ship them sooner.

Fixed. I'll make a new PR with the send sync change.

Thanks for the PR and the patience!


typo: Microsoft.AzureStack

concurency -> concurrency
subcription -> subscription
inclided -> included
regstration -> registration

Can one of the admins verify this patch?


[Bug] fileExtension incorrect if file has no extension

Is there an existing issue for this?

[X] I have searched the existing issues

Have you updated FilePond and its plugins?

[X] I have updated FilePond and its plugins

Describe the bug
I'm finding that if I upload a file that has no extension (i.e., no "dot-something" at the end of the file name), when I use the fileExtension getter on the item, I get the full filename rather than an empty string.  I'm working around it by comparing the results of fileExtension and filename, and if they're the same, proceed assuming there is actually is no extension.
Reproduction
I make a filepond instance like this:
const pond = FilePond.create(inputElement, {
  allowMultiple: true,
  instantUpload: true,
  allowRevert: true,
  allowRemove: false,
  allowReorder: true,
  dropOnPage: true,
  dropOnElement: false,
  maxParallelUploads: 10,
  server: {
    process: './do_file_upload.php',
    fetch: null,
    revert: './do_file_revert.php',
  }
});

then I catch the submit button click event for the form that the file input element is in, use pond.getfiles() to get the file list, and loop through looking at item.fileExtension among other things.  If there is a file in the list without an extension, the results of item.filenameWithoutExtension and item.fileExtension are the same, and equal to the name of the uploaded file.
Environment
- Device: HP DL380 G8
- OS: Ubuntu 22.04.1 LTS
- Browser: Chrome 104.0.5112.101 on Win 10 19044.1889

this is something I'm picking up in v5 of filepond

Thanks!
From: Rik @.>
Sent: Sunday, September 18, 2022 11:46 PM
To: pqina/filepond @.>
Cc: aabenraa @.>; Author @.>
Subject: Re: [pqina/filepond] [Bug] fileExtension incorrect if file has no extension (Issue #857)
this is something I'm picking up in v5 of filepond
—
Reply to this email directly, view it on GitHub https://github.com/pqina/filepond/issues/857#issuecomment-1250629579 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A2SMHQELIBVWJTE6JQS7XA3V7AD4LANCNFSM562ZIP3A .
You are receiving this because you authored the thread.Message ID: @.***>


NFT burn only works for minters and not holders

Description
Currently the nft burn functionality only works for the minter. Holders of the nft are not allowed to burn.
Is this PR related with an open issue?
Related to Issue https://github.com/nevermined-io/internal/issues/200
Types of changes

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

Checklist:

[ ] Follows the code style of this project.
[x] Tests Cover Changes
[ ] Documentation

Funny gif

this was just a test to trigger the bug. resolved in contracts 2.0


Acknowledging PReLU Operator

This does sound like a nag but there is the operator PReLU that was neither implemented nor presented in the Roadmap for PyTorch DirectML.
Please acknowledge (or even better, implement) it. Thank you.

Hi and thank you for the request, we will consider this for an upcoming release of pytorch-directml, and will update this thread when more information is available.

Hi @ffleader1, we have added float32 support to PReLU in torch-directml-0.1.13.dev221216. Please give it a shot and let us know if you face any other issues.


Only auto-refresh table if table visible

Is your feature request related to a problem? Please describe.
I want to reduce useless database calls, and I believe the auto-refresh function keeps auto-refreshing even if the table isn't currently visible.
Describe the solution you'd like
Only auto-refresh if table visible. (Or make a setting for this.)
Describe alternatives you've considered
N/A
Additional context
N/A

Well, when auto-refresh is off, the DBeaver process costs 0Mbps passively, with it on, it's above zero, and remains that way, even when looking away from the table.


Fix warnings in Github Actions

Describe the Problem
Refer to this issue https://github.com/dtcenter/METplus/issues/1863
Expected Behavior
see issue https://github.com/dtcenter/METplus/issues/1863
Environment
Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop)
2. OS: (e.g. RedHat Linux, MacOS)
3. Software version number(s)
To Reproduce
Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)

Projects and Milestone

[ ] Select Organization level Project for support of the current coordinated release
[ ] Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
[ ] Select Milestone as the next bugfix version

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of main_<Version>.
Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
[ ] Fix the bug and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into main_<Version>.
Pull request: bugfix <Issue Number> main_<Version> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Organization level software support Project for the current coordinated release
Select: Milestone as the next bugfix version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the development branch.
Branch name:  bugfix_<Issue Number>_development_<Description>
Pull request: bugfix <Issue Number> development <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Close this issue.

Why am I getting this with just a blank template and nothing filled in?
On Wed, Oct 12, 2022 at 3:07 PM bikegeek @.***> wrote:

Replace italics below with details for this issue.
Describe the Problem
Provide a clear and concise description of the bug here.
Expected Behavior
Provide a clear and concise description of what you expected to happen
here.
Environment
Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop)
2. OS: (e.g. RedHat Linux, MacOS)
3. Software version number(s)
To Reproduce
Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata Assignee

Select engineer(s) or no engineer required
Select scientist(s) or no scientist required

Labels

Select component(s)
Select priority
Select requestor(s)

Projects and Milestone

Select Organization level Project for support of the current
coordinated release
Select Repository level Project for development toward the next
official release or add alert: NEED PROJECT ASSIGNMENT label
Select Milestone as the next bugfix version

Define Related Issue(s)
Consider the impact to the other METplus components.

METplus https://github.com/dtcenter/METplus/issues/new/choose, MET
https://github.com/dtcenter/MET/issues/new/choose, METdataio
https://github.com/dtcenter/METdataio/issues/new/choose, METviewer
https://github.com/dtcenter/METviewer/issues/new/choose, METexpress
https://github.com/dtcenter/METexpress/issues/new/choose, METcalcpy
https://github.com/dtcenter/METcalcpy/issues/new/choose, METplotpy
https://github.com/dtcenter/METplotpy/issues/new/choose

Bugfix Checklist
See the METplus Workflow
https://metplus.readthedocs.io/en/latest/Contributors_Guide/github_workflow.html
for details.

Complete the issue definition above, including the Time Estimate
and Funding Source.
Fork this repository or create a branch of main_.
Branch name: bugfix_main_
Fix the bug and test your changes.
Add/update log messages for easier debugging.
Add/update unit tests.
Add/update documentation.
Push local changes to GitHub.
Submit a pull request to merge into main_.
Pull request: bugfix  main_
Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Organization level software support Project for the
current coordinated release
Select: Milestone as the next bugfix version
Iterate until the reviewer(s) accept and merge your changes.
Delete your fork or branch.
Complete the steps above to fix the bug on the development branch.
Branch name: bugfix_development
Pull request: bugfix  development
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next
official release
Select: Milestone as the next official version
Close this issue.

—
Reply to this email directly, view it on GitHub
https://github.com/dtcenter/METexpress/issues/99, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG6HZOUZ7SNDHQRRM4CU2L3WC4SBPANCNFSM6AAAAAARDVEOOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Bonny Strong
NOAA/GSL and CIRA
office:<PHONE_NUMBER> or home:<PHONE_NUMBER>


don't fail when wineboot fails

fixes #1372

bors cancel

bors r+

bors cancel
bors r+

bors is dead now... will have to fix, see #1249


Update AboutMe page and Add portfolio placeholder

Fix #4

Codecov Report

Merging #14 (7ef3571) into master (210e61a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 210e61a...7ef3571. Read the comment docs.